FORM 2
THE PATENTS ACT, 1970 (39 OF 1970) & THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
“METHOD AND SYSTEM FOR MANAGING OPERATIONAL PARAMETERS OF ONE OR MORE NETWORK FUNCTIONS
(NFs)”
We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.
The following specification particularly describes the invention and the manner in which it is to be performed.

METHOD AND SYSTEM FOR MANAGING OPERATIONAL PARAMETERS OF ONE OR MORE NETWORK FUNCTIONS (NFs)
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 managing operational parameters of one or more Network Functions (NFs).
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] Real time or historical alarms, counters and infra-metric meta-data can be fetched / exported from NFV Platform Data Analytics (NPDA). The unique aspect in this feature is centrally maintaining the Virtual Network Function (VNF/VNFC) or Container Network Function (CNF/CNFC) related FCAPS (fault, configuration, accounting, performance, and security) data and making it available for near real time searching. As may be known, the VNF may refer to software applications that deliver network functions such as directory services, routers, firewalls, load balancers, etc. The CNF may be a component or a software service that fulfils certain network functionalities while adhering to cloud-native design principles without requiring any hardware or appliance to house it. For fetching Meta data, parameter name and parameter type are one of the parameters. However, in traditional systems to fetch VNF/VNFC or CNF/CNFC FCAPS data, many systems were involved and near real time fetching is not at all possible.
[0005] Thus, there exists an imperative need in the art to develop methods and systems to NPDA offers a lot of flexibility in fetching the CNF/CNFC or VNF/VNFC FCAPs data.
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 managing operational parameters of one or more Network Functions (NFs). The method comprises receiving, by a transceiver unit, a request to exchange a set of data

relating to one or more operational parameters of at least one NF, wherein the set of data comprises fault, configuration, accounting, performance and security (FCAPS) data relating to the at least one NF. The method further comprises exchanging, by the transceiver unit, in response to the received request, the set of data relating to the at least one NF, with a database, wherein the database is configured to store at least one or more sets of data related to one or more NFs. The method further comprises providing, by a processing unit, a message to indicate that the exchange of the set of data between the transceiver unit and the database has occurred.
[0008] In an exemplary aspect of the present disclosure, the request to exchange the set of data is indicative of at least one of transmitting the set of data and retrieving the set of data. Further, for exchanging the set of data, the method further comprises one of transmitting, by the transceiver unit, the set of data relating to the at least one NF, to the database; and retrieving, by the transceiver unit, the set of data relating to the at least one NF, from the database.
[0009] In another exemplary aspect of the present disclosure, the at least one NF is selected from at least one of container network function (CNF), and virtual network function (VNF).
[0010] In another exemplary aspect of the present disclosure, the method further comprises receiving, by the transceiver unit, from an operations, administration, and management (OAM) module, in response to the received request, a set of details related to the at least one NF. Also, the method further comprises storing, by a storage unit, the received set of details relating to the at least one NF, in the database.
[0011] In another exemplary aspect of the present disclosure, the set of details related to the at least one network function (NF) comprises at least one of a registration activity, and a de-registration activity of the at least one NF.

[0012] In another exemplary aspect of the present disclosure, the request is received by at least one of a command line interface (CLI) and a User Interface (UI), wherein the UI is part of a load balancer (LB) module.
5 [0013] Another aspect of the present disclosure may relate to a system for
managing operational parameters of one or more Network Functions (NFs). The system comprises a transceiver unit and a processing unit connected to each other. The transceiver unit is configured to receive a request to exchange a set of data relating to one or more operational parameters of at least one network function
10 (NF), wherein the set of data comprises fault, configuration, accounting,
performance and security (FCAPS) data relating to the at least one NF. The transceiver unit is further configured to in response to the received request, exchange the set of data relating to at least one network function, with a database, wherein the database is configured to store at least one or more sets of data related
15 to one or more network functions (NFs). The processing unit is configured to
provide a message to indicate that the exchange of the set of data between the transceiver unit and the database has occurred.
[0014] Yet another aspect of the present disclosure may relate to a non-transitory
20 computer readable storage medium storing one or more instructions for managing
operational parameters of one or more Network Functions (NFs), the one or more
instructions include executable code which, when executed by one or more units of
a system, causes the one or more units to perform certain functions. The one or
more instructions when executed causes a transceiver unit of the system to receive
25 a request to exchange a set of data relating to one or more operational parameters
of at least one network function (NF), wherein the set of data comprises fault,
configuration, accounting, performance and security (FCAPS) data relating to the
at least one NF. The one or more instructions when executed further causes the
transceiver unit of the system to in response to the received request, exchange the
30 set of data relating to at least one network function, with a database, wherein the
database is configured to store at least one or more sets of data related to one or
5

more network functions (NFs). The one or more instructions when executed further causes a processing unit of the system to provide a message to indicate that the exchange of the set of data between the transceiver unit and the database has occurred. 5
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. 10
[0016] It is an object of the present disclosure to provide a system and a method for managing operational parameters of one or more Network Functions (NFs).
[0017] It is an object of the present disclosure to provide a system and a method for
15 maintenance of FCAPS data of at least one of a VNF and CNF component.
[0018] It is another object of the present disclosure to provide a solution NPDA that offers a lot of flexibility in fetching the CNF/CNFC or VNF/VNFC FCAPs data.
20 [0019] It is yet another object of the present disclosure for real time / historical
alarm, counter and infra-metric Meta data for a particular NF deployed in cloud or virtual environment can be fetch with near real-time searching support.
[0020] Yet another object of the present disclosure is export feature provided for
25 the alarm / counter/ infra-metric queried data. This feature adds a valuable input in
detecting any loopholes occurring in the network and thus helps in better management of the network infrastructure.
BRIEF DESCRIPTION OF THE DRAWINGS
30
6

[0021] 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,
5 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
10 drawings includes disclosure of electrical components or circuitry commonly used
to implement such components.
[0022] FIG. 1 illustrates an exemplary block diagram representation of management and orchestration (MANO)architecture. 15
[0023] 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.
20 [0024] FIG. 3 illustrates an exemplary block diagram of a system for managing
operational parameters of one or more Network Functions (NFs), in accordance with exemplary implementations of the present disclosure.
[0025] FIG. 4 illustrates an exemplary block diagram of a network environment
25 with a system for managing operational parameters of one or more Network
Functions (NFs), in accordance with exemplary implementations of the present disclosure.
[0026] FIG. 5 illustrates an exemplary block diagram of a network function
30 virtualisation (NFV) platform decision analytics (NPDA) module for managing
7

operational parameters of one or more Network Functions (NFs), in accordance with exemplary implementations of the present disclosure.
[0027] FIG. 6 illustrates a method flow diagram for managing operational
5 parameters of one or more Network Functions (NFs), 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. 10
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
15 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
20 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
25 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.
30 [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
8

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. 5
[0032] It should be noted that the terms "first", "second", "primary", "secondary", "target" and the like, herein do not denote any order, ranking, quantity, or importance, but rather are used to distinguish one element from another.
10 [0033] 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
15 is terminated when its operations are completed but could have additional steps not
included in a figure.
[0034] The word “exemplary” and/or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the
20 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
25 “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.
30 [0035] As used herein, a “processing unit” or “processor” or “operating processor”
includes one or more processors, wherein processor refers to any logic circuitry for
9

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
5 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.
10
[0036] 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
15 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
20 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.
[0037] As used herein, “storage unit” or “memory unit” refers to a machine or computer-readable medium including any mechanism for storing information in a
25 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
30 functions.
10

[0038] 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
5 each other, which also includes the methods, functions, or procedures that may be
called.
[0039] All modules, units, components used herein, unless explicitly excluded herein, may be software modules or hardware processors, the processors being a
10 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.
15
[0040] 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.
20
[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 managing operational parameters of one or more Network
25 Functions (NFs).
[0042] FIG. 1 illustrates an exemplary block diagram representation of a
management and orchestration (MANO) architecture [100], in accordance with
exemplary implementation of the present disclosure. The MANO architecture [100]
30 is developed for managing telecom cloud infrastructure automatically, managing
design or deployment design, managing instantiation of a network node(s) etc. The
11

MANO architecture [100] deploys the network node(s) in the form of Virtual
Network Function (VNF) and Cloud-native/ Container Network Function (CNF).
The system may comprise one or more components of the MANO architecture. The
MANO architecture [100] is used to auto-instantiate the VNFs into the
5 corresponding environment of the present disclosure so that it could help in
onboarding other vendor(s) CNFs and VNFs to the platform. In an implementation, the system comprises a NFV Platform Decision Analytics (NPDA) [1096] component.
10 [0043] As shown in FIG. 1, the MANO architecture [100] comprises a user
interface layer, a network function virtualization (NFV) and software defined network (SDN) design function module [104]; a platforms foundation services module [106], a platform core services module [108] and a platform resource adapters and utilities module [112], wherein all the components are assumed to be
15 connected to each other in a manner as obvious to the person skilled in the art for
implementing features of the present disclosure.
[0044] The NFV and SDN design function module [104] further comprises a VNF lifecycle manager (compute) [1042]; a VNF catalogue [1044]; a network
20 services catalogue [1046]; a network slicing and service chaining manager [1048];
a physical and virtual resource manager [1050] and a CNF lifecycle manager [1052]. The VNF lifecycle manager (compute) [1042] is responsible for on which server of the communication network the microservice will be instantiated. The VNF lifecycle manager (compute) [1042] will manage the overall flow of
25 incoming/ outgoing requests during interaction with the user. The VNF lifecycle
manager (compute) [1042] is responsible for determining which sequence to be followed for executing the process. For e.g. in an AMF network function of the communication network (such as a 5G network), sequence for execution of processes P1 and P2 etc. The VNF catalogue [1044] stores the metadata of all the
30 VNFs (also CNFs in some cases). The network services catalogue [1046] stores
the information of the services that need to be run. The network slicing and service
12

chaining manager [1048] manages the slicing (an ordered and connected sequence
of network service/ network functions (NFs)) that must be applied to a specific
networked data packet. The physical and virtual resource manager [1050] stores
the logical and physical inventory of the VNFs. Just like the VNF lifecycle manager
5 (compute) [1042], the CNF lifecycle manager [1052] is similarly used for the
CNFs lifecycle management.
[0045] The platforms foundation services module [106] further comprises a microservices elastic load balancer [1062]; an identify & access manager [1064]; a
10 command line interface (CLI) [1066]; a central logging manager [1068]; and an
event routing manager [1070]. The microservices elastic load balancer [1062] is used for maintaining the load balancing of the request for the services. The identify & access manager [1064] is used for logging purposes. The command line interface (CLI) [1066] is used to provide commands to execute certain processes
15 which requires changes during the run time. The central logging manager [1068]
is responsible for keeping the logs of every services. Theses logs are generated by the MANO platform [100]. These logs are used for debugging purposes. The event routing manager [1070] is responsible for routing the events i.e., the application programming interface (API) hits to the corresponding services.
20
[0046] The platforms core services module [108] further comprises NFV infrastructure monitoring manager [1082]; an assure manager [1084]; a performance manager [1086]; a policy execution engine [1088]; a capacity monitoring manager [1090]; a release management (mgmt.) repository [1092]; a
25 configuration manager & (GCT) [1094]; an NFV platform decision analytics
[1096]; a platform NoSQL DB [1098]; a platform schedulers and cron jobs [1100]; a VNF backup & upgrade manager [1102]; a microservice auditor [1104]; and a platform operations, administration and maintenance manager [1106]. The NFV infrastructure monitoring manager [1082] monitors the infrastructure part of the
30 NFs. For e.g., any metrics such as CPU utilization by the VNF. The assure manager
[1084] is responsible for supervising the alarms the vendor is generating. The
13

performance manager [1086] is responsible for manging the performance
counters. The policy execution engine (PEGN) [1088] is responsible for all the
managing the policies. The capacity monitoring manager (CPM) [1090] is
responsible for sending the request to the PEGN [1090]. The release management
5 (mgmt.) repository (RMR) [1092] is responsible for managing the releases and
the images of all the vendor network node. The configuration manager & (GCT) [1094] manages the configuration and GCT of all the vendors. The NFV platform decision analytics (NPDA) [1096] helps in deciding the priority of using the network resources. It is further noted that the policy execution engine (PEGN)
10 [1088], the configuration manager & (GCT) [1094] and the (NPDA) [1096] work
together. The platform NoSQL DB [1098] is a platform database for storing all the inventory (both physical and logical) as well as the metadata of the VNFs and CNF. It may be noted that the platform NoSQL DB [1098] may be just a narrow implementation of the present disclosure, and any other kind of structure for the
15 database may be implemented for the platform database such as relational or non-
relational database. The platform schedulers and cron jobs [1100] schedules the task such as but not limited to triggering of an event, traverse the network graph etc. The VNF backup & upgrade manager [1102] takes backup of the images, binaries of the VNFs and the CNFs and produces those backups on demand in case
20 of server failure. The microservice auditor [1104] audits the microservices. For
e.g., in a hypothetical case, instances not being instantiated by the MANO architecture [100] using the network resources then the microservice auditor [1104] audits and informs the same so that resources can be released for services running in the MANO architecture [100], thereby assuring the services only run on
25 the MANO platform [100]. The platform operations, administration and
maintenance manager [1106] is used for newer instances that are spawning.
[0047] The platform resource adapters and utilities module [112] further
comprises a platform external API adaptor and gateway [1122]; a generic decoder
30 and indexer (XML, CSV, JSON) [1124]; a docker swarm adaptor [1126]; an
OpenStack API adapter [1128]; and a NFV gateway [1130]. The platform external
14

API adaptor and gateway [1122] is responsible for handling the external services
(to the MANO platform [100]) that requires the network resources. The generic
decoder and indexer (XML, CSV, JSON) [1124] gets directly the data of the
vendor system in the XML, CSV, JSON format. The docker swarm adaptor [1126]
5 is the interface provided between the telecom cloud and the MANO architecture
[100] for communication. The OpenStack API adapter [1128]; is used to connect with the virtual machines (VMs). The NFV gateway [1130] is responsible for providing the path to each services going to/incoming from the MANO architecture [100].
10
[0048] FIG. 2 illustrates an exemplary block diagram of a computing device [200] upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure. The present disclosure can be implemented on a computing device [200] as shown in FIG. 2.
15 The computing device [200] implements the present disclosure in accordance with
the MANO architecture (as shown in FIG. 1). In an implementation, the computing device [200] may also implement a method for managing operational parameters of one or more Network Functions (NFs) utilising the system [300]. In another implementation, the computing device [200] itself implements the method for
20 managing operational parameters of the one or more Network Functions (NFs)
using one or more units configured within the computing device [200], wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.
25 [0049] 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-
30 access memory (RAM), or other dynamic storage device, coupled to the bus [202]
for storing information and instructions to be executed by the processor [204]. The
15

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-
5 purpose machine 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].
10 [0050] 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 cathode ray tube (CRT), Liquid crystal Display (LCD), Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for
15 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 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
20 information and command selections to the processor [204], and for controlling
cursor movement on the display [212]. The 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.
25 [0051] 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 device [200] to be a special-purpose machine. According to one implementation, the techniques herein are performed by the
30 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
16

instructions may be read into the main memory [206] from another storage medium,
such as the storage device [210]. Execution of the sequences of instructions
contained in the main memory [206] causes the processor [204] to perform the
process steps described herein. In alternative implementations of the present
5 disclosure, hard-wired circuitry may be used in place of or in combination with
software instructions.
[0052] The computing device [200] also may include a communication interface
[218] coupled to the bus [202]. The communication interface [218] provides a two-
10 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, the communication interface [218] may be a
15 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 receives electrical,
electromagnetic or optical signals that carry digital data streams representing
various types of information.
20
[0053] The computing device [200] can send messages and receive data, including
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
25 ISP [226], the local network [222], a 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], or other non-volatile storage for later execution.
30 [0054] Referring to FIG. 3, an exemplary block diagram of a system [300] for
managing operational parameters of one or more Network Functions (NFs), is
17

shown, in accordance with the exemplary implementations of the present disclosure.
[0055] Further, FIG. 4 illustrates an exemplary block diagram of a network
5 environment [400] with a system [300] for managing operational parameters of one
or more Network Functions (NFs), in accordance with exemplary implementations of the present disclosure.
[0056] In one example, the system [300] may be implemented as NPDA [1096]. In
10 such cases, a NPDA module may be responsible for performing the functions of the
NPDA [1096]. This has been depicted in FIG. 5. FIG. 5 illustrates an exemplary
block diagram of a network function virtualisation (NFV) platform decision
analytics (NPDA) module [502] for managing operational parameters of one or
more Network Functions (NFs), in accordance with exemplary implementations of
15 the present disclosure.
[0057] It may be noted that FIG. 3, FIG. 4, and FIG. 5 have been explained simultaneously, and may be read in conjunction with each other.
20 [0058] In one example, the system [300] may be in communication with other
network entities/components within the network, as depicted in FIG. 4. Further, it may be noted that some of the entities as depicted in FIG. 4 and have not been depicted in FIG. 3 are explained in the foregoing description. It may be further noted that any other network entities/components may also be in communication with the
25 system [300], which may not be depicted in FIG.4, as may also be understood to a
person skilled in the art.
[0059] As depicted in FIG.3, the system [300] may comprise at least one
transceiver unit [302], at least one processing unit [304], and at least one storage
30 unit [306]. Also, all of the components/ units of the system [300] are assumed to be
connected to each other unless otherwise indicated below. As shown in FIG. 3, all
18

units shown within the system [300] should also be assumed to be connected to
each other. Also, in FIG. 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
5 disclosure. Further, in an implementation, the system [300] may be present in a user
device/ user equipment to implement the features of the present disclosure. The
system [300] 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 [300] may reside in a server or a network entity. In yet
10 another implementation, the system [300] may reside partly in the server/ network
entity and partly in the user device.
[0060] The system [300] is configured for managing operational parameters of the
one or more NFs, with the help of the interconnection between the
15 components/units of the system [300].
[0061] As would be understood, the one or more NFs may refer to different network
functions present in the 5G core network such as network repository function
(NRF), Authentication and Security Function (AUSF), etc., or preferably a
20 container network function (CNF), and a virtual network function (VNF).
[0062] Further, in other implementations of the present disclosure, the at least one
network function (NF) may be selected from at least one of container network
function (CNF), and virtual network function (VNF). As used herein, the VNF may
25 refer to software applications that deliver network functions such as directory
services, routers, firewalls, load balancers, etc. The CNF may be a component or a software service that fulfils certain network functionalities while adhering to cloud-native design principles without requiring any hardware or appliance to house it.
30 [0063] Further, the operational parameters may be referred to as the parameters that
may be used during an operation of exchanging operation such as during exchange
19

of data. The management of operational parameters may be management of the exchange of the data and controlling the entities through which the data may be exchanged.
5 [0064] In operation, the transceiver unit [302] receives a request to exchange a set
of data relating to one or more operational parameters of at least one network
function (NF). It may be noted that the set of data comprises fault, configuration,
accounting, performance and security (FCAPS) data relating to the at least one NF.
As would be understood to a person skilled in the art, the request to exchange the
10 set of data may be received in the form of a message, a query or a command.
[0065] The set of data or the FCAPS data may comprise information such as fault information, configuration information, accounting information, performance information, security information, etc. The fault information may refer to the
15 information about network devices for problems and appropriate actions to be
taken, fault logs, alarms, etc. The configuration information may refer to the information associated with configuration files, software versions, changes to system hardware, OS version, updates, etc. The accounting information may refer to the information associated with costs, bills, charges, etc. The performance
20 information may refer to the information associated with health, performance
thresholds, throughput, network response times, packet loss rates, link utilization, percentage utilization, error rates, etc. The security information may refer to the information associated with network firewalls, intrusion detection systems, security policies, etc.
25
[0066] It may be noted that in certain implementations of the present disclosure, the request may be received by at least one of a command line interface (CLI) [408] and a User Interface (UI) [402], wherein the UI [402] is part of a load balancer (LB) module [404]. The request being received from the CLI [408] has been depicted by
30 step [416] as provided in the FIG. 4. The command line interface (CLI) [408] may
refer to a text-based interface on which user inputs certain commands for interacting
20

with a software of the computing devices such as the computer's operating system.
It may be noted that in order to communicate with the CLI [408], the NPDA module
[502] may comprise an interface used for facilitating communication between the
NPDA module [502] and the CLI [408], which may be for example, the NPDA_CL
5 [512] interface. The NPDA_CL [512] interface may be used to execute fetch
operation/ export operation on the NPDA module [502] using the CLI [408]. The permitted operations may be predefined at the NPDA module [502], and the permitted operations may be executed, and the configuration changes may be done using such interface. The LB module [404] may be a device or a service that sits
10 between the one component such as a user and another component such as a server
group. The LB module [404] acts as an invisible facilitator and ensures that all resource servers are used equally, and the traffic is managed between the servers. In an example, the LB module [404] may be a messaging bus which queues the messages or the request for management of the load/traffic.
15
[0067] The receiving of the request to exchange the set of data has been depicted by step [412] and step [414] in the FIG. 4. The UI [402] performs the step [412], where the UI [402] may fetch or export the request or a query. It may be noted that in order to perform the step [412], the NPDA module [502] may comprise an
20 interface for fetching/exporting the request, which may be for example, the
NPDA_UI [504] interface as depicted in FIG.5. The NPDA_UI [504] interface may be used to fetch and export a real time or historical data of alarms, counters and infra-metric data (part of data mentioned as FCAPS data) from the NPDA module [502] for the VNF or VNFC and the CNF or CNFC. Further, the fetched set of data
25 can be showed/provided over the UI [402], or if export functionality is performed,
then the data can be exported from the UI [402] after receiving inputs from the UE. Further, in case the LB module [404] may be utilised for load management, and then accordingly, at step [414], the LB module [404] may forward the request/response. It may be noted that in order to perform the step [414], the NPDA
30 module [502] may comprise an interface which may be used for forwarding the
request or response, which may be for example, the NPDA_LB [506] interface as
21

depicted in FIG.5. The NPDA_LB [506] interface may be used to distribute all incoming/outgoing requests/responses to balance the load/traffic equally in the NPDA module [502].
5 [0068] In another example, the transceiver unit [302] is also configured to receive,
from an operations, administration, and management (OAM) module [406], a set of details related to the at least one network function (NF), in response to the received request. Further, the storage unit [302] may be configured to store the received set of details relating to the at least one network function, in the database [410].
10
[0069] The receiving or exchanging the set of details from the OAM module [406] is depicted by step [420] as provided in the FIG. 4. In order to execute the step [420] the NPDA module [502] comprises an interface for enabling the communication between the NPDA module [502] and the OAM module [406]. The
15 interface may be for example an NPDA_OA [510] interface. The NPDA_OA [510]
interface may be a central connecting point of NPDA and the OAM module [406]. The NPDA module [502] registers/deregisters/reregisters themselves using this interface. The central server thus receives IP, port, Path, Component Broadcast Context, Subscribe Component Type etc. for the NPDA module [502]. On
20 successful registration, web socket connection may be established between the
central server and the NPDA instance (using interface client). The interfaces may be used for broadcasting a registration information to the microservice instances that are subscribed, and also provide data broadcast in which microservice can circulate data among their instances. This enables microservices manage HA (high
25 availability) using data broadcast. This interface may also be used to send FCAPS
request to respective microservice instances and consolidates all the microservice FCAPS responses and send the consolidated response to EMS.
[0070] As would be understood, the OAM module [406] may be a component
30 responsible for performance of processes and functions that may be used in
22

provisioning and managing a network or element within a network, i.e., used for operation, administration and management of the network elements.
[0071] In one of the implementations of the present disclosure, the set of details
5 may comprise information associated with at least one of a registration activity, and
a de-registration activity of a network function. The registration activity may refer
to the registration of the at least one network function and the de-registration
activity may refer to the registration of a network function. It may be noted that in
another implementation of the present disclosure, the set of details may also
10 comprise a reregistration activity for registering again of the network function.
[0072] Returning to the present example, after the request is received, then the
transceiver unit [302], in response to the received request, exchanges the set of data
relating to at least one network function, with a database [410]. Further, it may be
15 noted the database [410] is configured to store at least one or more sets of data
related to one or more network functions (NFs).
[0073] In some implementations of the present disclosure, the request to exchange the set of data may be indicative of at least one of transmitting the set of data, and
20 retrieving the set of data. In other words, the exchange of the set of data may be
either transmitting or retrieving the set of data. It may be further noted that in some other implementations of the present disclosure, the transceiver unit [302] may either transmit or retrieve the set of data relating to the at least one network function, to or from the database [410].
25
[0074] The exchange of the set of data with the database [410] has been depicted by step [418] as provided in the FIG. 4. The database [410] may be used for storing/fetching of the FCAPS data such as alarm, counters, or infra-metric data while using the system [300] or the NPDA module [502]. It may be noted that in
30 order to perform the step [418], the NPDA module [502] may comprise an interface
which may be used for storing and fetching the FCAPS data to and from the
23

database [410]. Further, in order to exchange the set of data between the database
[410] and the system [300] or the NPDA module [502], the system [300] or the
NPDA module [502] may additionally comprise an interface used for exchanging
the set of data, for example, the interface may be an NPDA_NS [508] interface. The
5 NPDA_NS [508] interface may be used to store all the data in the database, for
example, the platform NoSql database [1098], additionally, any operations that needs to be perform on the database [410] may be done using this interface.
[0075] The database [410] may refer to a collection of structured data which may
10 be controlled by a database management system, the data for which may be stored
in the storage unit [306]. As provided above, the database [410] may be connected
with various network functions and may accordingly store the set of details of
various network functions, accordingly, the database [410] may contain one or more
sets of data. The database [410] may utilized different techniques for structuring the
15 data, for example, the database [410] may be in form of a relational database
structure, and may also be preferably in form of non-relational database such as the platform NoSQL DB [1098].
[0076] Continuing further, after the set of data is exchanged, then the processing
20 unit [304] is configured to provide a message to indicate that the exchange of the
set of data between the transceiver unit [302] and the database [410] has occurred.
As would be obvious to a person skilled in the art, the message may be in form of
a notification, an HTML status code, and may also be in any other form of indicative
actions already known for providing indication. The message may be sent after it
25 has been determined that exchange of the set of data is successful i.e., no errors or
faults were raised during the exchange of the set of data.
[0077] Referring to FIG. 6, an exemplary method flow diagram [600] for managing
operational parameters of one or more Network Functions (NFs), in accordance
30 with exemplary implementations of the present disclosure is shown. In an
implementation the method [600] is performed by the system [300]. Further, in an
24

implementation, the system [300] may be present in a server device to implement the features of the present disclosure. Also, as shown in FIG. 6, the method [600] starts at step [602].
5 [0078] As would be understood, the one or more NFs may refer to different network
functions present in the 5G core network such as network repository function (NRF), Authentication and Security Function (AUSF), etc., or preferably a container network function (CNF), and a virtual network function (VNF).
10 [0079] Further, in other implementations of the present disclosure, the at least one
network function (NF) may be selected from at least one of container network function (CNF), and virtual network function (VNF). As used herein, the VNF may refer to software applications that deliver network functions such as directory services, routers, firewalls, load balancers, etc. The CNF may be a component or a
15 software service that fulfils certain network functionalities while adhering to cloud-
native design principles without requiring any hardware or appliance to house it.
[0080] Further, the operational parameters may be referred to as the parameters that
may be used during an operation of exchanging operation such as during exchange
20 of data. The management of operational parameters may be management of the
exchange of the data and controlling the entities through which the data may be exchanged.
[0081] In operation, for managing operational parameters of the one or more NFs,
25 at step [604], the method [600] comprises receiving, by a transceiver unit [302], a
request to exchange a set of data relating to one or more operational parameters of at least one NF, wherein the set of data comprises fault, configuration, accounting, performance and security (FCAPS) data relating to the at least one NF.
25

[0082] As would be understood to a person skilled in the art, the request to exchange the set of data may be received in the form of a message, a query or a command.
5 [0083] The set of data or the FCAPS data may comprise information such as fault
information, configuration information, accounting information, performance information, security information, etc. The fault information may refer to the information about network devices for problems and appropriate actions to be taken, fault logs, alarms, etc. The configuration information may refer to the
10 information associated with configuration files, software versions, changes to
system hardware, OS version, updates, etc. The accounting information may refer to the information associated with costs, bills, charges, etc., The performance information may refer to the information associated with health, performance thresholds, throughput, network response times, packet loss rates, link utilization,
15 percentage utilization, error rates, etc. The security information may refer to the
information associated with network firewalls, intrusion detection systems, security policies, etc.
[0084] It may be noted that in certain implementations of the present disclosure,
20 the request may be received by at least one of a command line interface (CLI) [408]
and a User Interface (UI) [402], wherein the UI [402] is part of a load balancer (LB)
module [404]. The command line interface (CLI) [408] may refer to a text-based
interface on which user inputs certain commands for interacting with a software of
the computing devices such as the computer's operating system. It may be noted
25 that in order to communicate with the CLI [408], the NPDA module [502] may
comprise an interface used for facilitating communication between the NPDA
module [502] and the CLI [408], which may be for example, the NPDA_CL [512]
interface. The NPDA_CL [512] interface may be used to execute fetch operation/
export operation on the NPDA module [502] using the CLI [408]. The NPDA_CL
30 [512] interface may also refer to a text-based protocol used for sending commands
and receiving responses in structures format. It may be understood that the text-
26

based protocols may be such as secure shell (SSH), telnet, simple network
management platform, or other CLI specific protocols. The permitted operations
may be predefined at the NPDA module [502], and the permitted operations may
be executed, and the configuration changes may be done using such interface. The
5 LB module [404] may be a device or a service that sits between the one component
such as a user and another component such as a server group. The LB module [404]
acts as an invisible facilitator and ensures that all resource servers are used equally,
and the traffic is managed between the servers. In an example, the LB module [404]
may be a messaging bus which queues the messages or the request for management
10 of the load/traffic.
[0085] It may be noted that, the NPDA module [502] may comprise an interface for fetching/exporting the request, which may be for example, the NPDA_UI [504] interface. The NPDA_UI [504] interface may be used to fetch and export a real time
15 or historical data of alarms, counters and infra-metric data (part of data mentioned
as FCAPS data) from the NPDA module [502] for the VNF or VNFC and the CNF or CNFC. Further, the fetched set of data can be showed/provided over the UI [402], or if export functionality is performed, then the data can be exported from the UI [402] after receiving inputs from the UE. Further, in case the LB module [404] may
20 be utilised for load management, and then accordingly, the LB module [404] may
forward the request/response. It may be noted that, the NPDA module [502] may comprise an interface which may be used for forwarding the request or response, which may be for example, the NPDA_LB [506] interface. The NPDA_LB [506] interface may be used to distribute all incoming/outgoing requests/responses to
25 balance the load/traffic equally in the NPDA module [502].
[0086] Continuing further, at step [606], the method [600] comprises exchanging,
by the transceiver unit [302], in response to the received request, the set of data
relating to the at least one NF, with a database [410], wherein the database [410] is
30 configured to store at least one or more sets of data related to one or more NFs.
27

[0087] In some implementations of the present disclosure, the request to exchange
the set of data may be indicative of at least one of transmitting the set of data and
retrieving the set of data. In other words, the exchange of the set of data may be
either transmitting or retrieving the set of data. It may be further noted that in some
5 other implementations of the present disclosure, the method may comprise either
transmitting or retrieving, by the transceiver unit [302], the set of data relating to the at least one network function, either to or from the database [410].
[0088] The database [410] may be used for storing/fetching of the FCAPS data such
10 as alarm, counters, or infra-metric data while using the system [300] or the NPDA
module [502]. It may be noted that in order to perform the step [418], the NPDA module [502] may comprise an interface which may be used for storing and fetching the FCAPS data to and from the database [410]. Further, in order to exchange the set of data between the database [410] and the system [300] or the NPDA module
15 [502], the system [300] or the NPDA module [502] may additionally comprise an
interface used for exchanging the set of data, for example, the interface may be an NPDA_NS [508] interface. The NPDA_NS [508] interface may be used to store all the data in the platform NoSql database [1098], additionally, any operations that needs to be perform on the database [410] may be done using this interface.
20
[0089] The database [410] may refer to a collection of structured data which may be controlled by a database management system, the data for which may be stored in the storage unit [306]. As provided above, the database [410] may be connected with various network functions and may accordingly store the set of details of
25 various network functions, accordingly, the database [410] may contain one or more
sets of data. The database [410] may utilized different techniques for structuring the data, for example, the database [410] may be in form of a relational database structure and may also be preferably in form of non-relational database such as the platform NoSQL DB [1098].
30
28

[0090] In another example, the method further comprises receiving, by the
transceiver unit [302], from an operations, administration, and management (OAM)
module [406], in response to the received request, a set of details related to the at
least one NF. Further, the method [600] also comprises storing, by a storage unit
5 [306], the received set of details relating to the at least one NF, in the database [410].
[0091] In order to receive or exchange the set of details from the OAM module [406], the NPDA module [502] comprises an interface for enabling the communication between the NPDA module [502] and the OAM module [406]. The
10 interface may be for example an NPDA_OA [510] interface. The NPDA_OA [510]
interface may be a central connecting point of NPDA and the OAM module [406]. The NPDA module [502] registers/deregisters/reregisters themselves using this interface. The central server thus receives IP, port, Path, Component Broadcast Context, Subscribe Component Type etc. for the NPDA module [502]. On
15 successful registration, web socket connection may be established between the
central server and the NPDA instance (using interface client). The interfaces may be used for broadcasting a registration information to the microservice instances that are subscribed, and also provide data broadcast in which microservice can circulate data among their instances. This enables microservices manage HA (high
20 availability) using data broadcast. This interface may also be used to send FCAPS
request to respective microservice instances and consolidates all the microservice FCAPS responses and send the consolidated response to an element management systems (EMS) such as network management systems or the MANO architecture system as provided above.
25
[0092] As would be understood, the OAM module [406] may be a component responsible for performance of processes and functions that may be used in provisioning and managing a network or element within a network, i.e., used for operation, administration and management of the network elements.
30
29

[0093] In one of the implementations of the present disclosure, the set of details
may comprise information associated with at least one of a registration activity, and
a de-registration activity of a network function. The registration activity may refer
to the registration of the at least one network function and the de-registration
5 activity may refer to the registration of a network function. It may be noted that in
another implementation of the present disclosure, the set of details may also comprise a reregistration activity for registering again of the network function.
[0094] Continuing further, at step [608], the method [600] involves providing, by a
10 processing unit [304], a message to indicate that the exchange of the set of data
between the transceiver unit [302] and the database [410] has occurred.
[0095] As would be obvious to a person skilled in the art, the message may be in
the form of a notification, an HTML status code, and may also be in any other form
15 of indicative actions already known for providing indication. The message may be
sent after it has been determined that exchange of the set of data is successful i.e., no errors or faults were raised during the exchange of the set of data.
[0096] Thereafter, at step [610], the method [600] is terminated.
20
[0097] The present disclosure further discloses a non-transitory computer readable storage medium storing one or more instructions for managing operational parameters of one or more Network Functions (NFs), the one or more instructions include executable code which, when executed by one or more units of a system
25 [300], causes the one or more units to perform certain functions. The one or more
instructions when executed causes a transceiver unit [302] of the system [300] to receive a request to exchange a set of data relating to one or more operational parameters of at least one network function (NF), wherein the set of data comprises fault, configuration, accounting, performance and security (FCAPS) data relating
30 to the at least one NF. The one or more instructions when executed further causes
the transceiver unit [302] of the system [300] to in response to the received request,
30

exchange the set of data relating to at least one network function, with a database
[410], wherein the database [410] is configured to store at least one or more sets of
data related to one or more network functions (NFs). The one or more instructions
when executed further causes a processing unit [304] of the system [300] to provide
5 a message to indicate that the exchange of the set of data between the transceiver
unit [302] and the database [410] has occurred.
[0098] As is evident from the above, the present disclosure provides a technically advanced solution for managing operational parameters of one or more Network
10 Functions (NFs). The present solution provides a solution where NPDA offers a lot
of flexibility in fetching the CNF/CNFC or VNF/VNFC FCAPs data. Also, the present invention offers for real time / historical alarm, counter and infra-metric Meta data for a particular NF deployed in cloud or virtual environment can be fetch with near real-time searching support. The present invention comprises an export
15 feature provided for the alarm / counter/ infra-metric queried data. This feature adds
a valuable input in detecting any loopholes occurring in the network and thus helps in better management of the network infrastructure.
[0099] While considerable emphasis has been placed herein on the disclosed
20 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
25 and non-limiting.
[0100] 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
30 particular functionality of these units for clarity, it is recognized that various
configurations and combinations thereof are within the scope of the disclosure. The
31

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.

We Claim:
1. A method for managing operational parameters of one or more Network
Functions (NFs), the method comprising:
- receiving, by a transceiver unit [302], a request to exchange a set of data relating to one or more operational parameters of at least one NF, wherein the set of data comprises fault, configuration, accounting, performance and security (FCAPS) data relating to the at least one NF;
- exchanging, by the transceiver unit [302], in response to the received request, the set of data relating to the at least one NF, with a database [410], wherein the database [410] is configured to store at least one or more sets of data related to one or more NFs; and
- providing, by a processing unit [304], a message to indicate that the exchange of the set of data between the transceiver unit [302] and the database [410] has occurred.
2. The method as claimed in claim 1, wherein:
the request to exchange the set of data is indicative of at least one of transmitting the set of data and retrieving the set of data; and
for exchanging the set of data, the method further comprises one of:
- transmitting, by the transceiver unit [302], the set of data relating to the at least one NF, to the database [410]; and
- retrieving, by the transceiver unit [302], the set of data relating to the at least one NF, from the database [410].
3. The method as claimed in claim 1, wherein the at least one NF is selected
from at least one of container network function (CNF), and virtual network
function (VNF).

4. The method as claimed in claim 1, further comprising:
- receiving, by the transceiver unit [302], from an operations, administration, and management (OAM) module [406], in response to the received request, a set of details related to the at least one NF; and
- storing, by a storage unit [306], the received set of details relating to the at least one NF, in the database [410].

5. The method as claimed in claim 4, wherein the set of details related to the at least one network function (NF) comprises at least one of a registration activity, and a de-registration activity of the at least one network function (NF).
6. The method as claimed in claim 1, wherein the request is received by at least one of a command line interface (CLI) [408] and a User Interface (UI) [402], wherein the UI [402] is part of a load balancer (LB) module [404].
7. A system [300] for managing operational parameters of one or more Network Functions (NFs), the system [300] comprising:
- a transceiver unit [302], wherein the transceiver unit [302] is
configured to:
o receive a request to exchange a set of data relating to one or more operational parameters of at least one network function (NF), wherein the set of data comprises fault, configuration, accounting, performance and security (FCAPS) data relating to the at least one NF;
o in response to the received request, exchange the set of data relating to at least one network function, with a database [410], wherein the database [410] is configured to store at least one or more sets of data related to one or more network functions (NFs); and

- a processing unit [304] connected at least to the transceiver unit [302], wherein the processing unit [304] is configured to provide a message to indicate that the exchange of the set of data between the transceiver unit [302] and the database [410] has occurred.
8. The system [300] as claimed in claim 7, wherein:
the request to exchange the set of data is indicative of at least one of transmitting the set of data, and retrieving the set of data; and the transceiver unit [302] is further configured to one of:
- transmit the set of data relating to the at least one network function, to the database [410]; and
- retrieve the set of data relating to the at least one network function, from the database [410].
9. The system [300] as claimed in claim 7, wherein the at least one network
function (NF) is selected from at least one of container network function
(CNF), and virtual network function (VNF).
10. The system [300] as claimed in claim 7, wherein the transceiver unit [302] is further configured to receive, from an operations, administration, and management (OAM) module [406], in response to the received request, a set of details related to the at least one network function (NF); and wherein the system [300] further comprises a storage unit [306] connected at least to the transceiver unit [302], wherein the storage unit [306] is configured to store the received set of details relating to the at least one network function, in the database [410].
11. The system [300] as claimed in claim 10, wherein the set of details
related to the at least one network function (NF) comprises at least one of a

registration activity, and a de-registration activity of the at least one network function (NF).
12. The system [300] as claimed in claim 7, wherein the request is
received by at least one of a command line interface (CLI) [408] and a User Interface (UI) [402], wherein the UI [402] is part of a load balancer (LB) module [404].