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 UPDATING POLICIES RELATING TO NETWORK FUNCTIONS IN NETWORK
ENVIRONMENT”
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 UPDATING POLICIES RELATING TO NETWORK FUNCTIONS IN NETWORK ENVIRONMENT
FIELD OF THE DISCLOSURE
[0001] Embodiments of the present disclosure generally relate to the field of network management. More particularly, embodiments of the present disclosure relate to updating policies relating to network functions (NFs) in a network environment.
BACKGROUND
[0002] The following description of 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 be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of 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 antilog 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] NFV Platform Decision Analytics (NPDA) provides threshold / hysteresis-based policy evaluation support of Virtual Network Function (VNF) / Container Network Function (CNF) load. This policy computation result becomes the gating criteria for further scale-in/scale-out/healing action that may be taken. NPDA comes up with dynamic update/enrichment of the policies defined for a VNF/VNFC or CNF/CNFC through the UI and those updated policy rules can then be applied for computation of the resources load. However, in the current existing solutions, NPDA does not offer dynamic modification and enrichment of threshold-based policies.
[0005] Thus, there exists an imperative need in the art to develop methods and systems to provide a solution for on-the-fly policy modification and application over NPDA for decision making of the instances capacity for deducing many network anomalies in real-time.
OBJECTS OF THE DISCLOSURE
[0006] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
[0007] It is an object of the present disclosure to provide a system and a method for dynamic enrichment of threshold-based policies.
[0008] It is another object of the present disclosure to provide a solution for on-the-fly policy modification and application over NFV Platform Decision Analytics

(NPDA) for decision making of the instances capacity for deducing many network anomalies in real-time.
[0009] It is yet another object of the present disclosure for dynamic enrichment/modification of threshold-based policy and application of the same in evaluation of a resources load in terms of CPU, RAM, Bandwidth, KPI, counter and alarms of a Virtual Network Function (VNF) / Container Network Function (CNF).
[0010] Yet another object of the present disclosure for dynamic decision-making support by accommodating the enrichment/modification in the policies results in more informed decisions for resource orchestration.
SUMMARY
[0011] 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.
[0012] An aspect of the present disclosure may relate to a method for updating policies relating to network functions (NFs) in a network environment. The method comprises receiving, by a transceiver unit, at a network function virtualization platform decision analytics (NPDA) module, a request for updating at least a policy relating to at least a network function (NF). The method further comprises updating, by a processing unit, at the NPDA module, the policy to create at least an updated policy, based on the received request. The method further comprises storing, by a storage unit, at a database, the updated policy in association with at least the network function. The method further comprises receiving, by the transceiver unit,

at the NPDA module, an error event for at least the network function. The method further comprises receiving, by the transceiver unit, at the NPDA module, a resource load utilization of at least the network function. The method further comprises evaluating, by the processing unit, at the NPDA module, based on the received resource load utilization for at least the network function, a hysteresis attribute of errors for at least a parameter of at least the network function, and validity of the error event for at least the network function.
[0013] In an exemplary aspect of the present disclosure, the policy relates to the parameter of the network function. The received request comprises a set of revisions for the policy.
[0014] In an exemplary aspect of the present disclosure, the parameter of the network function is selected from a group consisting of thresholds of resource utilizations of one or more central processing units (CPUs), one or more random memory access (RAM), bandwidths, key performance indicators (KPIs), counter values, alarm values, and combinations thereof.
[0015] In an exemplary aspect of the present disclosure, the error event relates to the parameter of the network function.
[0016] In an exemplary aspect of the present disclosure, in response to the error event of the network function being valid, the method comprises performing, by the processing unit, at an execution module, one or more corrective actions to negate the error event.
[0017] In an exemplary aspect of the present disclosure, the resource load utilization is based on the updated policy.

[0018] In an exemplary aspect of the present disclosure, the method comprises evaluating, by the processing unit at the NPDA module, validity of the error event based on the hysteresis attribute of errors for the parameter, and wherein the error event is valid when a count of successful breach conditions is equal to, or greater than a threshold value defined in the policy.
[0019] In an exemplary aspect of the present disclosure, the one or more corrective actions comprise at least one of a healing action, a scale-in action, and a scale-out action.
[0020] In an exemplary aspect of the present disclosure, the received request for updating the policy is received, by the processing unit, at the NPDA module, from at least one of a command line interface (CLI), and a user interface (UI).
[0021] Another aspect of the present disclosure may relate to a system for updating policies relating to network functions (NFs) in a network environment. The system comprises a transceiver unit configured to receive, at a network function virtualization platform decision analytics (NPDA) module, a request for updating at least a policy relating to at least a network function (NF). The system further comprises a processing unit configured to update, at the NPDA module, the policy to create at least an updated policy, based on the received request. The system further comprises a storage unit configured to store, at a database, the updated policy in association with at least the network function. The transceiver unit of the system is further configured to receive, at the NPDA module, an error event for at least the network function. transceiver unit of the system is further configured to receive, at the NPDA module, a resource load utilization of at least the network function. The processing unit of the system is configured to evaluate, at the NPDA module, based on the received resource load utilization for at least the network function, a hysteresis attribute of errors for at least a parameter of at least the network function, and validity of the error event for at least the network function.

[0022] Another aspect of the present disclosure may relate to a non-transitory
computer-readable storage medium storing instruction for updating policies relating
to network functions (NFs) in a network environment, the storage unit comprising
5 executable code which, when executed by one or more units of a system, causes a
transceiver unit to receive, at a network function virtualization platform decision analytics (NPDA) module, a request for updating at least a policy relating to at least a network function (NF). Further, the executable code which, when executed, causes a processing unit to update, at the NPDA module, the policy to create at least
10 an updated policy, based on the received request. Further, the executable code
which, when executed, causes a storage unit to store, at a database, the updated policy in association with at least the network function. Further, the executable code which, when executed, causes the transceiver unit to receive, at the NPDA module, an error event for at least the network function. Further, the executable code which,
15 when executed, causes the transceiver unit to receive, at the NPDA module, a
resource load utilization of at least the network function. Further, the executable code which, when executed, causes the processing unit configured to evaluate, at the NPDA module, based on the received resource load utilization for at least the network function, a hysteresis attribute of errors for at least a parameter of at least
20 the network function, and validity of the error event for at least the network
function.
DESCRIPTION OF DRAWINGS
25
[0023] 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,
30 emphasis instead being placed upon clearly illustrating the principles of the present
7

disclosure. Some drawings may indicate the components using block diagrams and
may not represent the internal circuitry of each component. It will be appreciated
by those skilled in the art that disclosure of such drawings includes disclosure of
electrical components, electronic components or circuitry commonly used to
5 implement such components.
[0024] 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. 10
[0025] 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.
15 [0026] FIG. 3 illustrates an exemplary block diagram of a system [300] for
updating policies relating to network functions (NFs) in a network environment, in accordance with exemplary implementations of the present disclosure.
[0027] FIG. 4 illustrates an exemplary method [400] flow diagram for updating
20 policies relating to network functions in the network environment, in accordance
with the exemplary embodiments of the present disclosure.
[0028] FIG. 5 illustrates another exemplary block diagram of system [500] for
updating policies relating to network functions in the network environment, in
25 accordance with exemplary embodiments of the present disclosure.
[0029] FIG. 6 illustrates another exemplary method [600] flow diagram indicating the process for updating policies relating to the network functions in the network environment, in accordance with exemplary embodiments of the present disclosure. 30
8

[0030] FIG. 7 illustrates an exemplary block diagram of Network Function Virtualization (NFV) Platform Decision Analytics (NPDA) having various interfaces associated with NPDA, in accordance with exemplary embodiments of the present disclosure. 5
[0031] The foregoing shall be more apparent from the following more detailed description of the disclosure.
10 DETAILED DESCRIPTION
[0032] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that
15 embodiments of the present disclosure may be practiced without these specific
details. Several features described hereafter can each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the problems discussed above. Some of the problems discussed above might not be
20 fully addressed by any of the features described herein. Example embodiments of
the present disclosure are described below, as illustrated in various drawings in which like reference numerals refer to the same parts throughout the different drawings.
25 [0033] The ensuing description provides exemplary embodiments only, and is not
intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and
9

arrangement of elements without departing from the spirit and scope of the disclosure as set forth.
[0034] It should be noted that the terms "mobile device", "user equipment", "user
5 device", “communication device”, “device” and similar terms are used
interchangeably for the purpose of describing the disclosure. These terms are not
intended to limit the scope of the disclosure or imply any specific functionality or
limitations on the described embodiments. The use of these terms is solely for
convenience and clarity of description. The disclosure is not limited to any
10 particular type of device or equipment, and it should be understood that other
equivalent terms or variations thereof may be used interchangeably without departing from the scope of the disclosure as defined herein.
[0035] Specific details are given in the following description to provide a thorough
15 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, networks, processes, and other
components may be shown as components in block diagram form in order not to
obscure the embodiments in unnecessary detail. In other instances, well-known
20 circuits, processes, algorithms, structures, and techniques may be shown without
unnecessary detail in order to avoid obscuring the embodiments.
[0036] 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 can 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
10

[0037] 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 similar
10 to the term “comprising” as an open transition word without precluding any
additional or other elements.
[0038] As used herein, an “electronic device”, or “portable electronic device”, or “user device” or “communication device” or “user equipment” or “device” refers
15 to any electrical, electronic, electromechanical and computing device. The user
device is capable of receiving and/or transmitting one or parameters, performing function/s, communicating with other user devices and transmitting data to the other user devices. The user equipment may have a processor, a display, a memory, a battery and an input-means such as a hard keypad and/or a soft keypad. The user
20 equipment may be capable of operating on any radio access technology including
but not limited to IP-enabled communication, Zig Bee, Bluetooth, Bluetooth Low Energy, Near Field Communication, Z-Wave, Wi-Fi, Wi-Fi direct, etc. For instance, the user equipment may include, but not limited to, a mobile phone, smartphone, virtual reality (VR) devices, augmented reality (AR) devices, laptop,
25 a general-purpose computer, desktop, personal digital assistant, tablet computer,
mainframe computer, or any other device as may be obvious to a person skilled in the art for implementation of the features of the present disclosure.
[0039] Further, the user device and/or a system as described herein to implement
30 technical features as disclosed in the present disclosure may also comprise
11

a “processor” or “processing unit”, wherein processor refers to any logic circuitry
for processing instructions. The 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
5 Digital Signal Processor (DSP) core, a controller, a microcontroller, Application
Specific Integrated Circuits, Field Programmable Gate Array circuits, any other
type of integrated circuits, etc. The processor may perform signal coding data
processing, input/output processing, and/or any other functionality that enables the
working of the system according to the present disclosure. More specifically, the
10 processor is a hardware processor.
[0040] 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
15 communication device” may be any electrical, electronic and/or computing device
or equipment, capable of implementing the features of the present disclosure. The user equipment/device may include, but is not limited to, a mobile phone, smart phone, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, wearable device or any other computing device which is capable
20 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 at least one of a transceiver unit, a processing unit, a storage unit, a detection unit and any other such unit(s) which are required to implement the features of the present disclosure.
25 [0041] As used herein, “storage unit” or “memory unit” refers to a machine or
computer-readable medium including any mechanism for storing information in a form readable by a computer or similar machine. For example, a computer-readable medium includes read-only memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical storage media, flash memory devices or other
30 types of machine-accessible storage media. The storage unit stores at least the data
12

that may be required by one or more units of the system to perform their respective functions.
[0042] As used herein “interface” or “user interface” refers to a shared boundary
5 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 called.
10
[0043] All modules, units, components used herein, unless explicitly excluded herein, may be software modules or hardware processors, the processors being a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more
15 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.
[0044] As used herein the transceiver unit includes at least one receiver and at least
20 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.
[0045] As discussed in the background section, the current known solutions have
25 several shortcomings. The present disclosure aims to overcome the above-
mentioned and other existing problems in this field of technology for updating
policies relating to network functions (NFs) in a network environment by providing
systems and methods for updating policies by way of dynamic enrichment of
threshold-based policies. The present disclosure is implemented with the help of
30 various components of a management and orchestration (MANO) architecture.
13

[0046] 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]
5 is developed for managing telecom cloud infrastructure automatically, managing
design or deployment design, managing instantiation of a network node(s) etc. The 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
10 MANO architecture [100] is used to auto-instantiate the VNFs into the
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) [212] component.
15
[0047] 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 platform foundation services module [106], a platform core services module [108] and a platform resource
20 adapters and utilities module [112], wherein all the 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.
[0048] The NFV and SDN design function module [104] further comprises a VNF
25 lifecycle manager (compute) [1042]; a VNF catalogue [1044]; a network 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
30 lifecycle manager (compute) [1042] will manage the overall flow of incoming/
outgoing requests during interaction with the user. The VNF lifecycle manager
14

(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 VNFs (also CNFs in
5 some cases). The network services catalogue [1046] stores the information of the
services that need to be run. The network slicing and service 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 logical and physical
10 inventory of the VNFs. Just like the VNF lifecycle manager (compute) [1042], the
CNF lifecycle manager [1052] is similarly used for the CNFs lifecycle management.
[0049] The platforms foundation services module [106] further comprises a
15 microservices elastic load balancer [1062]; an identify & access manager [1064]; a
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
20 (CLI) [1066] is used to provide commands to execute certain processes 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
25 programming interface (API) hits to the corresponding services.
[0050] 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
30 monitoring manager [1090]; a release management (mgmt.) repository [1092]; a
15

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 micro service auditor [1104]; and a
platform operations, administration and maintenance manager [1106]. The NFV
5 infrastructure monitoring manager [1082] monitors the infrastructure part of the
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 performance manager [1086] is responsible for manging the performance counters. The policy execution engine (PEEGN) [1088] is responsible for all the managing
10 the policies. The capacity monitoring manager (CPM) [1090] is responsible for
sending the request to the PEEGN [1088]. The release management (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
15 analytics (NPDA) [1096] helps in deciding the priority of using the network
resources. It is further noted that the policy execution engine (PEEGN) [1088], the configuration manager & (GCT) [1094] and the (NPDA) [1096] work together. The platform NoSQL DB [1098] is a database for storing all the inventory (both physical and logical) as well as the metadata of the VNFs and CNF. The platform schedulers
20 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 of server failure. The micro service auditor [1104] audits the microservices. For e.g., in a hypothetical case, instances not being
25 instantiated by the MANO architecture [100] using the network resources then the
micro service 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 the MANO platform [100]. The platform operations, administration and maintenance manager [1106] is used for newer instances that
30 are spawning.
16

[0051] The platform resource adapters and utilities module [112] further comprises
a platform external API adaptor and gateway [1122]; a generic decoder and indexer
(XML, CSV, JSON) [1124]; a docker swarm adaptor [1126]; an OpenStack API
5 adapter [1128]; and a NFV gateway [1130]. The platform external 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] is the interface
10 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].
15 [0052] The present disclosure can be implemented on a computing device [200] as
shown in FIG. 2. The computing device [200] implements the present disclosure in accordance with the MANO architecture (as shown in FIG. 1). FIG. 2 illustrates an exemplary block diagram of the computing device [200] upon which the features of the present disclosure may be implemented in accordance with exemplary
20 implementation of the present disclosure. In an implementation, the computing
device [200] may also implement a method [400] (as shown in FIG. 4) and a method [600] (as shown in FIG. 6) for updating policies relating to network functions (NFs) in a network environment utilising a system [300] (as shown in FIG. 3) and a system [500] (as shown in FIG. 5), both having a network function
25 virtualization platform decision analytics (NPDA) module/ platform [312] (as
shown in FIG. 3 and FIG. 7). In another implementation, the computing device [200] itself implements the method [400] and the method [600] for updating policies relating to the network functions (NFs) in the network environment in a communication network using one or more units configured within the computing
30 device [200], wherein said one or more units can implement the features as
disclosed in the present disclosure.
17

[0053] 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
5 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, 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
10 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 that is customized to perform the operations specified in the instructions. The computing device [200] further includes a read only memory
15 (ROM) [208] or other static storage device coupled to the bus [202] for storing static
information and instructions for the processor [204].
[0054] 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
20 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 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
25 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 information and command selections to the processor [204], and for controlling cursor movement on the display [212]. The input device typically has two degrees
18

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.
[0055] The computing device [200] may implement the techniques described
5 herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware
and/or program logic which in combination with the computing device [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 computing device [200] in response to the processor [204] executing one or more
10 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 instructions contained in the main memory [206] causes the processor [204] to perform the process steps described herein. In alternative implementations of the present
15 disclosure, hard-wired circuitry may be used in place of or in combination with
software instructions.
[0056] The computing device [200] also may include a communication interface
[218] coupled to the bus [202]. The communication interface [218] provides a two-
20 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
25 local area network (LAN) card to provide a data communication connection to a
compatible LAN. Wireless links may also be implemented. In any such
implementation, the communication interface [218] sends and receives electrical,
electromagnetic or optical signals that carry digital data streams representing
various types of information.
30
19

[0057] 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
5 ISP [226], 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], or other non-volatile storage for later execution.
10 [0058] The present disclosure is implemented by the system [300] (as shown in
FIG. 3). The system [300] may be implemented using the computing device [200] (as shown in FIG. 2). In an implementation, the computing device [200] may be connected to the system [300] to perform the present disclosure.
15 [0059] Referring to FIG. 3, an exemplary block diagram of the system [300] for
updating policies relating to the network functions (NFs) in the communication network, is shown, in accordance with the exemplary implementations of the present disclosure. The system [300] comprises at least one network function virtualization platform decision analytics (NPDA) module [312]. The NPDA
20 module [312] further comprises at least one transceiver unit [302]; at least one
processing unit [304], at least one storage unit [306] comprising at least one data base [3062] and at least one execution module [314]. The system [300] is connected to the one or more network functions (NFs) for updating policies. Also, all of the components/ units of the system [300] are assumed to be connected to each other
25 unless otherwise indicated below. As shown in the FIG.3, all 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 number of said units, as required to implement the features of the present disclosure. In an
30 implementation, the system [300] may reside in a server or a network entity. In
20

another implementation, the system [300] may reside partly in the server/ network entity.
[0060] The system [300] is configured for updating policies relating to network
5 functions (NFs) in the network environment, with the help of the interconnection
between the components/units of the system [300]. The “policy”/ “policies” may refer to a set of rules or guidelines that govern the behaviour and management of the network functions (NFs) within the network environment.
10 [0061] The transceiver unit [302] is configured to receive, at a network function
virtualization platform decision analytics (NPDA) module [312], a request for updating at least a policy relating to at least a network function (NF).
[0062] The processing unit [304] is configured to update, at the NPDA module
15 [312], the policy to create at least an updated policy, based on the received request.
[0063] The storage unit [306] is configured to store, at a database [3062], the updated policy in association with at least the network function.
20 [0064] The transceiver unit [302] is further configured to receive, at the NPDA
module [312], an error event for at least the network function. The transceiver unit [302] is further configured to receive, at the NPDA module [312], a resource load utilization of at least the network function.
25 [0065] The processing unit [304] is further configured to evaluate, at the NPDA
module [312], based on the received resource load utilization for at least the network function, a hysteresis attribute of errors for at least a parameter of at least the network function, and validity of the error event for at least the network function.
30
21

[0066] In an exemplary aspect of the present disclosure, the policy relates to the
parameter of the network function. It is to be noted that the received request
comprises a set of revisions for the policy. In general, network function (NF) is
functional building block within a network infrastructure that processes and
5 transmits data packets implemented by a network device(s).
[0067] In an exemplary aspect of the present disclosure, the error event relates to the parameter of the network function. The error event is indicative of the occurrence in the network function when something goes wrong causing the
10 network function to behave unexpectedly due to an unexpected parameter. The
parameter of the network function may be a value(s) that control behaviour and performance of the network function. In an example, the parameter may be bandwidth, latency, packet size, jitter, error rate, throughput, connection timeout, and the like. In an exemplary aspect of the present disclosure, in response to the
15 error event of the network function being valid, the processing unit [304] is further
configured to perform, at an execution module [314], one or more corrective actions to negate the error event.
[0068] In an exemplary aspect of the present disclosure, the resource load
20 utilization is based on the updated policy. In general, the resource load utilization
is a measure of how effectively a system’s resources (such as CPU, memory, network bandwidth, etc.) are being used compared to their total capacity.
[0069] In an exemplary aspect of the present disclosure, the parameter of the
25 network function is selected from a group consisting of thresholds of resource
utilizations of one or more central processing units (CPUs), one or more random memory access (RAM), bandwidths, key performance indicators (KPIs), counter values, alarm values, and combinations thereof.
22

[0070] In an exemplary aspect of the present disclosure, the processing unit [304]
is configured to: evaluate, at the NPDA module [312], validity of the error event
based on the hysteresis attribute of errors for the parameter. The error event is valid
when a count of successful breach conditions is equal to, or greater than a threshold
5 value defined in the policy.
[0071] In an exemplary aspect of the present disclosure, the one or more corrective actions comprise at least one of a healing action, a scale-in action, and a scale-out action. In general, healing action refers to automated processes that detect and
10 correct issues within a system. For example, if a server becomes unresponsive, a
healing action might automatically restart the server, replace it with a new instance or reroute traffic to healthy instances. Further, the scale-in action includes reducing number of resources, or instances in a system. In addition, the scale-out action refers to a process of adding more resources or instances to handle increased demand. For
15 example, if traffic to a web application spikes, scaling out would involve adding
more servers or instances to distribute load.
[0072] In an exemplary aspect of the present disclosure, the received request for
updating the policy is received, by the processing unit [304], at the NPDA module
20 [312], from at least one of a command line interface (CLI) [308], and a user
interface (UI) [310]. In general, the command line interface (CLI) [308] is an interface for interacting with a computer program by inputting lines of text called command-lines.
25 [0073] Referring to FIG. 4, an exemplary method flow diagram [400] for updating
policies relating to network functions (NFs) in a network environment, in accordance with exemplary implementations of the present disclosure is shown. In an implementation the method [400] is performed by the system [300] (as shown in FIG. 3). In another implementation, the method [400] is performed by the system
30 [500] (as shown in FIG. 5). Further, in an implementation, the system [300] may
23

be present in a server device to implement the features of the present disclosure. Furthermore, in an implementation, the system [500] may be present in a server device to implement the features of the present disclosure. Also, as shown in FIG. 4, the method [400] starts at step [402]. 5
[0074] At step [404], the method [400] comprises receiving, by a transceiver unit [302], at a network function virtualization platform decision analytics (NPDA) module [312], a request for updating at least a policy relating to at least a network function (NF). 10
[0075] At step [406], the method [400] further comprises updating, by a processing unit [304], at the NPDA module [312], the policy to create at least an updated policy, based on the received request.
15 [0076] At step [408], the method [400] further comprises storing, by a storage unit
[306], at a database [3062], the updated policy in association with at least the network function.
[0077] At step [410], the method [400] further comprises receiving, by the
20 transceiver unit [302], at the NPDA module [312], an error event for at least the
network function.
[0078] At step [412], the method [400] further comprises receiving, by the
transceiver unit [302], at the NPDA module [312], a resource load utilization of at
25 least the network function.
[0079] At step [414], the method [400] further comprises evaluating, by the
processing unit [304], at the NPDA module [312], based on the received resource
load utilization for at least the network function, a hysteresis attribute of errors for
30 at least a parameter of at least the network function, and validity of the error event
24

for at least the network function. In an exemplary aspect of the present disclosure,
the policy relates to the parameter of the network function. The received request
comprises a set of revisions for the policy. In an exemplary aspect of the present
disclosure, the received request for updating the policy is received, by the
5 processing unit [304], at the NPDA module [312], from at least one of a command
line interface (CLI) [308], and a user interface (UI) [310].
[0080] In an exemplary aspect of the present disclosure, the parameter of the
network function is selected from a group consisting of thresholds of resource
10 utilizations of one or more central processing units (CPUs), one or more random
memory access (RAM), bandwidths, key performance indicators (KPIs), counter values, alarm values, and combinations thereof.
[0081] In an exemplary aspect of the present disclosure, the error event relates to
15 the parameter of the network function. In an exemplary aspect of the present
disclosure, in response to the error event of the network function being valid, the
method [400] comprises performing, by the processing unit [304], at an execution
module [314], one or more corrective actions to negate the error event. In an
exemplary aspect of the present disclosure, the resource load utilization is based on
20 the updated policy.
[0082] In an exemplary aspect of the present disclosure, the method [400]
comprises evaluating, by the processing unit [304] at the NPDA module [312],
validity of the error event based on the hysteresis attribute of errors for the
25 parameter, and wherein the error event is valid when a count of successful breach
conditions is equal to, or greater than a threshold value defined in the policy.
[0083] In an exemplary aspect of the present disclosure, the one or more corrective
actions comprise at least one of a healing action, a scale-in action, and a scale-out
30 action.
25

[0084] Thereafter, the method [400] terminates at step [412].
[0085] Referring to FIG. 5, an exemplary block diagram of a system [500] for
5 updating policies relating to network function(s) [such as virtual network function
(VNF)/ container network functions (CNF)] [502] in a network environment is
shown, in accordance with the exemplary embodiments of the present disclosure.
FIG. 6 illustrates another exemplary method [600] flow diagram indicating the
process for updating policies relating to the network function(s) [502] in the
10 network environment, in accordance with exemplary embodiments of the present
disclosure. FIG. 5 and FIG. 6 have been explained in conjunction with each other.
[0086] The present disclosure may be implemented by the system [500] having the computing device [200] (as shown in FIG. 2). In an implementation, the computing
15 device [200] may be connected to the system [500] to perform updating policies
relating to network function(s) [502] in the network environment. In another implementation of the present disclosure, the system [500] is configured to perform dynamic enrichment of threshold-based policies relating to the NFs [502], in accordance with exemplary embodiments of the present disclosure. Further, the
20 system [500] comprises various components of MANO architecture (as shown in
FIG. 1) in implementation of the present disclosure. The system [500] comprises at least one communication unit [504], at least one storage unit [306] and at least one processing unit [304] (as shown in FIG. 3). The at least one processing unit [304] may further comprises at least one network function virtualization (NFV)
25 platform decision analytics (NPDA)/ NFV platform decision analytics (NPDA)/
NPDA module [312] connected to at least one network functions (NFs) [502] and at least one connectivity management platform/ capacity manager microservice (CMP) [506] and at least one physical and virtual infrastructure manager (PVIM) [508]. Also, all of the components/ units of the system [500] are assumed to be
30 connected to each other unless otherwise indicated below. Also, in FIG. 2 only a
few units are shown, however, the system [500] may comprise multiple such units
26

or the system [500] may comprise any such numbers of said units, as required to implement the features of the present disclosure. In another implementation, the system [500] may reside in a server or a network entity. In yet another implementation, the system [200] may reside partly in the server/ network entity. 5
[0087] The system [500] is further configured for dynamic enrichment of threshold-based policies, with the help of the interconnection between the components/units of the system [500].
10 [0088] A communication unit [504], is configured to receive at least one of a policy
evaluation request and a restoration request. In an implementation, a user interface (UI) [310] (as shown in FIG. 3) is configured to receive the at least one of a policy evaluation request and the restoration request. In an event, the request is received at the UI [310], the request may be sent to a load balancer (LB) [602] (as shown in
15 FIG. 6) that may forward the request to the NPDA module [312]. In another
implementation, a command line interface (CLI) [308] (as shown in FIG. 3) is configured to receive the at least one of a policy evaluation request and the restoration request.
20 [0089] Further, a processing unit [304], is configured to update the at least one of
a policy evaluation request and a restoration request. The processing unit [304] comprises at least one of a Virtual Network Function (VNF) (not shown); Container Network Function (CNF) (not shown); Operations, administration, and management (OAM) node [610] (as shown in FIG. 6) and NFV Platform Decision
25 Analytics (NPDA) [312].
[0090] Furthermore, the storage unit [306], is configured to store the at least one of a policy evaluation request and a restoration request. In an exemplary implementation, the storage unit [306] may be a non-relational database [612] (as
27

shown in FIG. 6) but the present disclosure is not limited thereto. For e.g., a non-relational database may be a NoSQL database.
[0091] Next, the processing unit [304], is configured to evaluate one or more
5 resource load parameters of a network component based on the updated at least one
of a policy evaluation request and a restoration request. The one or more resource load parameters comprises at least one of CPU, RAM, Bandwidth, KPI, counter and alarms but the present disclosure is not limited thereto.
10 [0092] Now, the processing unit [304], is configured to determine a resource
threshold based on the one or more resource load parameters. In a preferred implementation, NPDA [312] is configured to evaluate resource load of at least one of the Virtual Network Function (VNF) and the Container Network Function (CNF) based on the updated policy on receive a trigger for resource threshold from the
15 Capacity Manager Microservice (CMP) [506] and receive an alarm enrichment
request from the Physical and Virtual Infrastructure Manager (PVIM) [508].
[0093] The NFV Platform Decision Analytics (NPDA) module [312] is configured to receive at least one of a resource threshold based evaluation policy and a
20 restoration policy that may be enriched for at least one of a Virtual Network
Function (VNF)/ Container Network Function (CNF) i.e. network functions (NFs) through a user interface (UI) [310] at the NPDA module [312] via the load balance (LB) [602]. In another implementation, the request for modification/ enrichment may be received through command line interface (CLI) [308] at the NPDA [312].
25
[0094] On receiving the request, the NPDA module [312] is configured to store the updated policy against the respective at least one of the VNF/VNFC and CNF/CNFC within the non-relational database [612].
28

[0095] Further, the NPDA module [312] is configured to evaluate the at least one the VNF/VNFC and the CNF/CNFC resource load based on the updated policy as and when the trigger for resource threshold may be received, via an Event routing manager (ERM) [616] from at least one of the Capacity Manager Microservice (CMP) [506] and the alarm enrichment request may be received from the Physical and Virtual Infrastructure Manager (PVIM) [508].
[0096] Furthermore, the NPDA module [312] is configured to perform at least one of a scale-in operation, scale-out operation and healing operations to its adjacent micro service Policy Execution Engine (PEEGN) [614] in an event the hysteresis-based evaluation of the defined policy is true.
[0097] FIG. 7 illustrates an exemplary block diagram of Network Function Virtualization (NFV) Platform Decision Analytics (NPDA) module [312] having various interfaces associated with NPDA module [312], in accordance with exemplary embodiments of the present disclosure. The NPDA module [312] have the following interfaces:
- A NPDA_UI interface [3122] is used to create/ modify/ delete/ view threshold based policies for a network function such as a virtual network function (VNF) or (VNFC), container network function (CNF) or (CNFC). The resources alarms, counters and infra-metric data related policies are defined through the NPDA_UI interface [3122].
- A NPDA_CL interface [3124] is used to create/ modify/ delete/ view VNF/ VNFC or CNF/ CNFC threshold policies at the NPDA module [312] using the NPDA_CL interface [3124]. Permitted operations will be pre-define at the NPDA [312] and are eventually executed using this interface. In addition, configuration changes can be done using this interface.
- A NPDA_LB interface [3126] is used to distribute all incoming/outgoing request to balance load equally in the NPDA module [312] service.

- A NPDA_OAM interface [3128] is a central connecting point of the NPDA module [312]. The NPDA module [312] register/ deregister/ reregister themselves using this interface. The central server thus receives IP, port, Path, Component Broadcast Context, Subscribe Component Type etc. for the NPDA module [312]. On successful registration, web socket connection is established between central server and the NPDA instance (using interface client). This interface server broadcast registration information to the subscribed micro service instances and provide data broadcast in which micro service can circulate data among their instances. That is how micro services manage HA (high availability) using data broadcast. This interface also sends Fault, Configuration, Accounting, Performance and Security (FCAPS) request to respective micro service instances and consolidates all the micro service FCAPS responses and send the consolidated response to Element Management System (EMS).
- A NPDA_EM interface [3130] is used to route the event between all the micro services. It follows a subscription and notification model based on the events that are publish to it. Each micro service registers its standard platform events with the interface. For each event, there can be multiple subscribers. Whenever the event of interest is received, the notification is sent by this interface to the subscribers informing them of the said event.
- A NPDA_CP interface [3132] is used for notification of VNF/ CNF/ VNFC/ CNFC instance resources load to the NPDA module [312]. Using the reported load, the NPDA module [312] evaluates the policy defined for the respective VNF/ VNFC or CNF/ CNFC. Based on the evaluation appropriate actions such as scale-in/scale-out operations can be suggested further by the NPDA module [312].
- A NPDA_PVIM interface [3134] is used for notification of VNF/ CNF/ VNFC/ CNFC instances resources alarms to the NPDA module [312]. Using the reported alarms, the NPDA module [312] evaluates the policy defined for the respective VNF/ VNFC or CNF/ CNFC. Based on the evaluation

appropriate actions such as healing can suggest further by the NPDA module [312].
- A NPDA_NS [3136] interface used to store all the data in the non-relational database [612]. In addition, any operations that needs to perform on database will be done using this interface.
- A NPDA_PS interface [3138] is used for closed loop automation i.e. NPDA informed the decisions such as scale-in/scale-out/healing of a VNF/VNFC or CNF/CNFC whenever the gating criteria is true which usually happens when there is a breach in the reported load at the NPDA module [312].
[0098] Another aspect of the present disclosure may relate to a non-transitory computer-readable storage medium storing instruction for updating policies relating to network functions (NFs) in a network environment, the storage unit comprising executable code which, when executed by one or more units of a system [300], causes a transceiver unit [302] to receive, at a network function virtualization platform decision analytics (NPDA) module [312], a request for updating at least a policy relating to at least a network function (NF). Further, the executable code which, when executed, causes a processing unit [304] to update, at the NPDA module [312], the policy to create at least an updated policy, based on the received request. Further, the executable code which, when executed, causes a storage unit [306] to store, at a database [3062], the updated policy in association with at least the network function. Further, the executable code which, when executed, causes the transceiver unit [302] to receive, at the NPDA module [312], an error event for at least the network function. Further, the executable code which, when executed, causes the transceiver unit [302] to receive, at the NPDA module [312], a resource load utilization of at least the network function. Further, the executable code which, when executed, causes the processing unit [304] configured to evaluate, at the NPDA module [312], based on the received resource load utilization for at least the network function, a hysteresis attribute of errors for at least a parameter of at least

the network function, and validity of the error event for at least the network function.
[0099] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various components/units can be implemented interchangeably. While specific embodiments may disclose a particular functionality of these units for clarity, it is recognized that various configurations and combinations thereof are within the scope of the disclosure. The functionality of specific units as disclosed in the disclosure should not be construed as limiting the scope of the present disclosure. Consequently, alternative arrangements and substitutions of units, provided they achieve the intended functionality described herein, are considered to be encompassed within the scope of the present disclosure.
[0100] As is evident from the above, the present disclosure provides a technically advanced solution for updating policies relating to network functions (NFs). The present disclosure thus provides a dynamic enrichment of threshold-based policies of the network functions (NFs). The present disclosure provides to provide a solution for on-the-fly policy modification and application over the NPDA module [312] for decision making of the instances capacity for deducing many network anomalies in real-time.
[0101] 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 updating policies relating to network functions (NFs) in
a network environment, the method [400] comprising:
- receiving, by a transceiver unit [302], at a network function virtualization platform decision analytics (NPDA) module [312], a request for updating at least a policy relating to at least a network function (NF);
- updating, by a processing unit [304], at the NPDA module [312], the policy to create at least an updated policy, based on the received request;
- storing, by a storage unit [306], at a database [3062], the updated policy in association with at least the network function;
- receiving, by the transceiver unit [302], at the NPDA module [312], an error event for at least the network function;
- receiving, by the transceiver unit [302], at the NPDA module [312], a resource load utilization of at least the network function; and
- evaluating, by the processing unit [304], at the NPDA module [312], based on the received resource load utilization for at least the network function, a hysteresis attribute of errors for at least a parameter of at least the network function, and validity of the error event for at least the network function.

2. The method [400] as claimed in claim 1, wherein the policy relates to the parameter of the network function, and wherein the received request comprises a set of revisions for the policy.
3. The method [400] as claimed in claim 1, wherein the parameter of the network function is selected from a group consisting of thresholds of resource utilizations of one or more central processing units (CPUs), one or more random memory access (RAM), bandwidths, key performance indicators (KPIs), counter values, alarm values, and combinations thereof.

4. The method [400] as claimed in claim 1, wherein the error event relates to the parameter of the network function. 5. The method [400] as claimed in claim 1, wherein, in response to the error event of the network function being valid, the method [400] comprises:
performing, by the processing unit [304], at an execution module [314], one or more corrective actions to negate the error event.
6. The method [400] as claimed in claim 1, wherein the resource load utilization is based on the updated policy.
7. The method [400] as claimed in claim 1, wherein the method [400] comprises: evaluating, by the processing unit [304] at the NPDA module [312], validity of the error event based on the hysteresis attribute of errors for the parameter, and wherein the error event is valid when a count of successful breach conditions is equal to, or greater than a threshold value defined in the policy.
8. The method [400] as claimed in claim 5, wherein the one or more corrective actions comprise at least one of a healing action, a scale-in action, and a scale-out action.
9. The method [400] as claimed in claim 1, wherein the received request for updating the policy is received, by the processing unit [304], at the NPDA module [312], from at least one of a command line interface (CLI) [308], and a user interface (UI) [310].
10. A system [300] for updating policies relating to network functions (NFs) in a network environment, the system [300] comprising: a transceiver unit [302] configured to:
- receive, at a network function virtualization platform decision
analytics (NPDA) module [312], a request for updating at least
a policy relating to at least a network function (NF);
a processing unit [304] configured to:
- update, at the NPDA module [312], the policy to create at least
an updated policy, based on the received request;

a storage unit [306] configured to:
- store, at a database [3062], the updated policy in association
with at least the network function;
the transceiver unit [302] configured to:
- receive, at the NPDA module [312], an error event for at least the network function;
- receive, at the NPDA module [312], a resource load utilization of at least the network function;
the processing unit [304] configured to:
- evaluate, at the NPDA module [312], based on the received
resource load utilization for at least the network function, a
hysteresis attribute of errors for at least a parameter of at least
the network function, and validity of the error event for at least
the network function.
11. The system [300] as claimed in claim 10, wherein the policy relates to the parameter of the network function, and wherein the received request comprises a set of revisions for the policy.
12. The system [300] as claimed in claim 10, wherein the error event relates to the parameter of the network function.
13. The system [300] as claimed in claim 10, wherein, in response to the error event of the network function being valid, the processing unit [304] is further configured to:
perform, at an execution module [314], one or more corrective actions to negate the error event.
14. The system [300] as claimed in claim 10, wherein the resource load utilization is based on the updated policy.
15. The system [300] as claimed in claim 10, wherein the parameter of the network function is selected from a group consisting of thresholds of resource utilizations of one or more central processing units (CPUs), one or

more random memory access (RAM), bandwidths, key performance indicators (KPIs), counter values, alarm values, and combinations thereof.
16. The system [300] as claimed in claim 10, wherein the processing unit [304] is configured to: evaluate, at the NPDA module [312], validity of the error event based on the hysteresis attribute of errors for the parameter, and wherein the error event is valid when a count of successful breach conditions is equal to, or greater than a threshold value defined in the policy.
17. The system [300] as claimed in claim 13, wherein the one or more corrective actions comprise at least one of a healing action, a scale-in action, and a scale-out action.
18. The system [300] as claimed in claim 10, wherein the received request for updating the policy is received, by the processing unit [304], at the NPDA module [312], from at least one of a command line interface (CLI) [308], and a user interface (UI) [310].