FORM 2
THE PATENTS ACT, 1970 (39 of 1970) THE PATENTS RULES, 2003
COMPLETE SPECIFICATION
SYSTEM AND METHOD FOR APPLYING POLICY RULE CHANGE IN COMMUNICATION
NETWORK
APPLICANT
of Office-101, Saffron, Nr..JIO PLATFORMS LIMITED.-—
380006, Gujarat, India; Nationality : India
The following specification particularly describes
the invention and the manner in which
it is to be performed

RESERVATION OF RIGHTS
[0001] A portion of the disclosure of this patent document contains material
which is subject to intellectual property rights such as, but are not limited to, copyright, design, trademark, Integrated Circuit (IC) layout design, and/or trade dress protection, belonging to Jio Platforms Limited (JPL) or its affiliates (hereinafter referred as owner). The owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all rights whatsoever. All rights to such intellectual property are fully reserved by the owner.
TECHNICAL FIELD
[0002] The present disclosure relates to wireless cellular communications,
and specifically to a system and method for applying a policy rule change in a communication network.
DEFINITIONS
[0003] As used in the present disclosure, the following terms are generally
intended to have the meaning as set forth below, except to the extent that the context in which they are used to indicate otherwise.
[0004] A policy control function (PCF) provides policy rules for control
plane functions. The control plane functions include network slicing, roaming and mobility management.
[0005] A session management function (SMF) establishes, modifies, and
terminates sessions established between user equipments (UEs) and the user plane function (UPF) in the network.

[0006] An access and mobility management function (AMF) performs
access authentication and authorization, mobility management.
[0007] A Rx interface is used to exchange flow-based charging control
information between a policy and charging rules function (CRF) and the application function (AF). The Rx interface enables transport of application-level session information from a proxy call session control function (P-CSCF) to a policy and charging rules function (PCRF). The information includes IP filter information to identify the service data flow for policy control and/or differentiated charging, media/application bandwidth requirements for quality of service (QoS) control.
[0008] A Sd interface supports application detection and control (ADC) rule
handling, usage monitoring control of traffic detection function (TDF) sessions and of detected applications and reporting of the start and the stop of a detected application's traffic and transfer of service data flow descriptions for detected applications.
BACKGROUND
[0009] 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.
[0010] In prevalent situations, when a subscriber plans to install a particular
rule on the basis of specific conditions, and the rule is already installed previously for that subscriber, then a removal rule is defined explicitly along with a new rule, which is inefficient and time-consuming.

[0011] Therefore, there is a need in the art to provide an improved
mechanism that provides enhancement at a policy control function (PCF) which allows a user to define a smaller number of rules using a customized rule engine and facilitate automatic removal of previously installed rules if conditions of the already installed rules do not match.
SUMMARY
[0012] In an exemplary embodiment, a method for applying policy rule
change in a network is described. The method comprises receiving, by a policy control function (PCF), a request for policy rule creation or updation from at least one of plurality network nodes. The method further comprises determining, by the PCF, the one of plurality of network nodes from which the request is received and forwarding, by the PCF, the received request towards a rule engine corresponding to the determined one of plurality of network nodes. The method further comprises checking, by the rule engine corresponding to the determined one of the plurality of network nodes, all of plurality of policy rules for the received request based on a plurality of conditions and based on the checking, applying, by the rule engine corresponding to the determined one of the plurality of network nodes, at least one of plurality of actions.
[0013] In some embodiments, the plurality of actions includes installing or
removing the plurality of policy rules.
[0014] In some embodiments, the plurality of network nodes comprises a
plurality of network functions (NFs) and a plurality of network interfaces, wherein the plurality of network functions (NFs) includes a session management function (SMF), and an access management function (AMF), and wherein the plurality of network interfaces includes a Rx interface and a Sd interface.
[0015] In some embodiments, the method further comprises on detecting an
exclusive rule is triggered at priority, evaluating, by the rule engine, the exclusive

rule and controlling, by the rule engine, evaluation of subsequent policy rules. The method further comprises applying, by the rule engine, one of plurality of actions corresponding to the exclusive rule. on detecting one of plurality of actions is applied due to triggering of the exclusive rule at priority, keeping, by the rule engine, the applied action in force up to a point when the exclusive rule is triggered at priority.
[0016] In some embodiments, on detecting the plurality policy rules are not
matched with the plurality of conditions, performing, by the PCF, a defined action according to a standard.
[0017] In some embodiments, the method further comprises on detecting
two of plurality of policy rules are matching the plurality of conditions, evaluating, by the rule engine, the two of plurality of policy rules and creating, by the rule engine, a new policy rule to prevent modification of an existing policy rule.
[0018] In some embodiments, the method further comprises on detecting
previously installed policy rules do not match with the plurality of conditions, removing, by the rule engine, the previously installed policy rules.
[0019] In some embodiments, for an update request from the Rx interface,
on detecting no delta changes in existing rules, sending, by the rule engine of the Rx interface, no update to the SMF. The method further comprises sending, by the rule engine of the Rx interface, a success response on the Rx interface. On detecting the delta changes in the existing rules, sending, by the rule engine of the Rx interface, the delta changes towards the SMF.
[0020] In some embodiments, on detecting the rules are not installed for a
subscriber and a policy rule removal action is configured in the rule engine, the PCF is configured to do not send the policy rule removal action to the SMF.

[0021] In some embodiments, the rule engine is configured with rule names
and the plurality of conditions. The plurality of conditions is defined as a plurality of attributes to match using a plurality of operators and plurality of corresponding actions. The plurality of attributes includes service operation, a generic public subscription identifier (GPSI), a subscription permanent identifier (SUPI), an internet protocol (IP), a medium access control (MAC), a data network name (DNN), slice, policy control identities (PCIDS) and location details. The location details include a public land mobile network (PLMN) and a plurality of tracking area codes (TACs).
[0022] In some embodiments, the plurality of conditions further comprises
a rule priority, a rule exclusivity.
[0023] In another exemplary embodiment, a system for applying policy rule
change in a network, the system comprising a policy control function (PCF). The PCF comprises a receiving unit configured to receive a request for policy rule creation or updation from at least one of plurality network nodes. A processing unit configured to determine the one of plurality of network nodes from which the request is received and forward the received request towards a rule engine corresponding to the determined one of plurality of network nodes. The rule engine corresponding to the determined one of the plurality of network nodes configured to check all of plurality of policy rules for the received request based on a plurality of conditions and based on the checking, apply at least one of plurality of actions.
[0024] In some embodiments, the plurality of actions includes installing or
removing a plurality of policies.
[0025] In some embodiments, the plurality of network nodes comprises a
plurality of network functions (NFs) and a plurality of network interfaces, wherein the plurality of network functions (NFs) includes a session management function

(SMF), an access management function (AMF), and wherein the plurality of network interfaces includes a Rx interface and a Sd interface.
[0026] In some embodiments, on detecting an exclusive rule is triggered at
priority, the rule engine is configured to evaluate the exclusive rule, control evaluation of subsequent policy rules and apply one of plurality of actions corresponding to the exclusive rule. On detecting one of plurality of actions is applied due to triggering of the exclusive rule at priority, the rule engine is configured to keep the applied action in force up to a point when the exclusive rule is triggered at priority.
[0027] In some embodiments, on detecting the plurality policy rules are not
matched with the plurality of conditions, the PCF is configured to perform a defined action according to a standard.
[0028] In some embodiments, on detecting two of plurality of policy rules
are matching the plurality of conditions, the rule engine is configured to evaluate the two of plurality of policy rules and create a new policy rule to prevent modification of an existing policy rule.
[0029] In some embodiments, on detecting previously installed policy rules
do not match with the plurality of conditions, the rule engine is configured to remove the previously installed policy rules.
[0030] In some embodiments, for an update request from the Rx interface,
on detecting no delta changes in existing rules, the rule engine of the Rx engine is configured to send no update to the SMF and send a success response on the Rx interface. On detecting delta changes in the existing rules, the rule engine of the Rx interface is configured to send the delta changes towards the SMF.

[0031] In some embodiments, on detecting the rules are not installed for a
subscriber and a policy rule removal action is configured in the rule engine, the PCF is configured to do not send the policy rule removal action to the SMF.
[0032] In some embodiments, the rule engine is configured with rule names
and the plurality of conditions. The plurality of conditions is defined as a plurality of attributes to match using a plurality of operators and plurality of corresponding actions. The plurality of attributes includes service operation, a generic public subscription identifier (GPSI), a subscription permanent identifier (SUPI), an internet protocol (IP), a medium access control (MAC), a data network name (DNN), slice, policy control identities (PCIDS) and location details. The location details include a public land mobile network (PLMN) and a plurality of tracking area codes (TACs).
[0033] In some embodiments, the plurality of conditions further comprises
a rule priority, a rule exclusivity.
[0034] In some embodiments, a user equipment is communicatively
coupled with a system. The coupling comprises steps of receiving, by the system, a connection request and sending, by the system, an acknowledgment of the connection request to the UE. The coupling further comprises transmitting a plurality of signals in response to the connection request. The system is configured for applying policy rule change in a network.
[0035] The foregoing general description of the illustrative embodiments
and the following detailed description thereof are merely exemplary aspects of the teachings of this disclosure, and are not restrictive.
OBJECTS OF THE PRESENT DISCLOSURE
[0036] It is an object of the present disclosure to apply a policy rule change
in a communication network.

[0037] It is an object of the present disclosure to efficiently manage network
resources by allocating and controlling a maximum data transfer rate.
[0038] It is an object of the present disclosure to facilitate a policy control
function (PCF) to remove previously installed rules on its own, if conditions of the already installed rules do not match. This helps to avoid a need to explicitly define a removal action in a policy engine.
[0039] It is an object of the present disclosure to provision the rules with
mutual exclusive flag true if only a specific rule is to be pushed to Session Management Function (SMF) and ignore other rules which match the condition.
[0040] It is an object of the present disclosure to facilitate the PCF to not
send remove rules to the SMF, if the rules are not installed for the subscriber, and if policy rule removal is configured in the policy engine.
[0041] It is an object of the present disclosure to use the policy engine to
evaluate conditions of both policies, if the two policies have matching conditions. An operator can create a new policy with action removal to avoid policy modification of an existing rule.
[0042] It is an object of the present disclosure to send a no update
notification towards SMF, and a success response on Rx, when Rx trigger is received, and there is no delta change to send in update notification.
[0043] It is an object of the present disclosure to provide different attributes
and operator choices for different interfaces such as Media Based Rules (Rx), Session Management (SM) policy, Access and Mobility (AM) policy, Application Detection and Control (ADC) rules (Sd).
BRIEF DESCRIPTION OF THE DRAWINGS

[0044] In the figures, similar components and/or features may have the
same reference label. Further, various components of the same type may be distinguished by following the reference label with a second label that distinguishes among the similar components. If only the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label.
[0045] The diagrams are for illustration only, which thus is not a limitation
of the present disclosure, and wherein:
[0046] FIG. 1 illustrates an example network architecture for implementing
a system, in accordance with an embodiment of the present disclosure.
[0047] FIG. 2A illustrates an exemplary representation of a policy control
function (PCF) connected to various network nodes to apply policy rule change, in accordance with an embodiment of the disclosure.
[0048] FIG. 2B illustrates an exemplary representation of the system for
applying the policy rule change in a network, in accordance with an embodiment of the disclosure.
[0049] FIG. 2C illustrates an exemplary representation of the PCF
connected to various network nodes, in accordance with an embodiment of the disclosure.
[0050] FIG. 3 illustrates an exemplary flowchart for applying the policy rule
change in a communication network, in accordance with an embodiment of the disclosure.
[0051] FIG. 4 illustrates an exemplary flowchart for applying the policy rule
change in a communication network, in accordance with an embodiment of the disclosure.

[0052] FIG. 5 illustrates an exemplary computer system in which or with
which embodiments of the present disclosure may be implemented.
DETAILED DESCRIPTION
[0053] In the following description, for the purposes of explanation, various
specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features. An individual feature may not address all of the problems discussed above or might address only some of the problems discussed above. Some of the problems discussed above might not be fully addressed by any of the features described herein.
[0054] The ensuing description provides exemplary embodiments only, and
is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the invention as set forth.
[0055] Specific details are given in the following description to provide a
thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, 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 circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.

[0056] 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 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. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination can correspond to a return of the function to the calling function or the main function.
[0057] The word “exemplary” and/or “demonstrative” is used herein to
mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and/or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive—in a manner similar to the term “comprising” as an open transition word—without precluding any additional or other elements.
[0058] Reference throughout this specification to “one embodiment” or “an
embodiment” or “an instance” or “one instance” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0059] The terminology used herein is for the purpose of describing
particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. As used herein, the term “and/or” includes any and all combinations of one or more of the associated listed items.
[0060] Typically, a policy control function (PCF) provides policy rules for
control plane functions, such as network slicing, roaming, and mobility management. The policy rules support the new 5G quality of service (QoS) policy and charging control function. The policy rules manage policies, services, subscriptions, quotas, and bearer resources. These policies are created in real-time based on a subscriber profile.
[0061] The disclosed system and method facilitate to provide an
enhancement at the PCF, which allows a user to define a smaller number of rules using a customized rule engine. The PCF facilitates the removal of previously installed rules on its own if they do not match the already installed rules and conditions. The user may create different rules as per requirements with different attributes and operator choices for different network functions and network interfaces such as media-based rules (Rx interface), a session management function (SMF), an access and mobility management function (AMF), application detection and control (ADC) rules (Sd interface). In an aspect, media-based rules are implemented and managed through the Rx interface. The Rx interface facilitates the exchange of policy and charging information related to media-based rules between the network functions. The media-based rules are used to manage and control traffic based on the type of media or content being accessed or transmitted

over the network. The media-based rules include differentiating policies and treatment for various media types such as video streaming, voice calls, messaging services, etc. In an aspect, application detection and control (ADC) rules are implemented and managed through the Sd interface. So, the Sd interface facilitates the exchange of information related to application detection and control rules between the network functions. The ADC rules are used to identify and manage traffic from specific applications. The ADC rules allows network operators to apply different policies, such as QoS enforcement, traffic shaping, or charging rules, based on the type of application being used by subscribers.
[0062] The disclosed system and method facilitate to provide a policy rule
change in the communication network. The PCF may provide a rule engine-based
approach. The rule engine may accept conditions using multiple parameters. The
rule engine is configured to work with rule names and rule conditions. In an aspect,
rule names refer to specific configurations or settings that govern how traffic is
managed and controlled for subscribers. The rule names typically follow a
structured naming convention within the system, allowing operators to easily
identify and manage rules across their network infrastructure. In an aspect, the rule
names may comprise, but not limited to, quality of service rules, access control
rules, charging rules, roaming rules, application-based rules, time-based rules,
emergency service rules, etc. For example, rule name "Gold Service VoIP"
indicating a rule that prioritizes VoIP traffic for subscribers with a gold service tier,
ensuring high-quality voice communication. The rule conditions are defined as a
plurality of attributes to match using a plurality of operators and corresponding
actions. The plurality of operators includes AND, OR, NOT, =, !=, <, <=, >, >=,
equal (eq), not equal (neq), gt, lt, range, within range and wildcards. The plurality
of attributes includes service operation/ subscription permanent identifier (SUPI)/
subscriber concealed identifier (SUCI)/internet protocol (IP)/media access control
(MAC)/data network name (DNN)/slice/policy counter identifiers
(PCIDs)/location details (e.g., public land mobile network (PLMN)/tracking area codes (TACs) (attribute details of attributes and http2 headers) to take actions. The

actions may include installing or removing policy rules. The actions may further
include an accept user or a reject user. For example, condition for the AMF =
(((TAC) or (IP) or (SUPI)) and ((Action 1) or (Action 2))); Action 1 = install policy
rules and Action 2 = remove policy rules. Condition for Rx interface = (((MAC) or
5 (SUPI) or (IP) or (SUCI)) and ((Action 1) or (Action 2))).
[0063] In an embodiment, the PCF may receive a request from a session
management function (SMF), access and mobility management function (AMF), Rx, and Sd interface. Further, corresponding actions may be taken based on the defined rules, and a policy may be installed or removed.
10 [0064] In an embodiment, if the user (e.g., operator) wants to install a
specific rule, then an option may be provided in the rule engine to install that particular rule with the help of a mutual exclusive flag set as true. The rule engine may discard all rules that matched and install those rules that are kept true.
[0065] In an embodiment, the policy changes may be defined at the PCF
15 using a command line interface (CLI), and a service management portal (SMP) user
interface. The rule engine may configure with a rule name and rule conditions. The
rule conditions are defined as attributes to match using operators such as AND/ OR/
NOT, and corresponding actions. The attribute values to match may use other
operators such as =, !=, <, <=, >, >=, eq, neq, gt, lt, range, within range, wildcards
20 etc., as per requirement. Further, a separate rule engine for the SMF, the AMF, the
Rx and the Sd may be provided.
[0066] FIG. 1 illustrates an example network architecture (100) for
implementing a system (108), in accordance with an embodiment of the present disclosure.
25 [0067] As illustrated in FIG. 1, one or more computing devices (104-1, 104-
2…104-N) may be connected to the system (108) through a network (106). A person of ordinary skill in the art will understand that the one or more computing
15

devices (104-1, 104-2…104-N) may be collectively referred as computing devices
(104) and individually referred as a computing device (104). One or more users
(102-1, 102-2…102-N) may provide one or more requests to the system (108). A
person of ordinary skill in the art will understand that the one or more users (102-
5 1, 102-2…102-N) may be collectively referred as users (102) and individually
referred as a user (102). Further, the computing devices (104) may also be referred
as a user equipment (UE) (104) or as UEs (104) throughout the disclosure.
[0068] In an embodiment, the computing device (104) may include, but not
be limited to, a mobile, a laptop, etc. Further, the computing device (104) may
10 include one or more in-built or externally coupled accessories including, but not
limited to, a visual aid device such as a camera, audio aid, microphone, or keyboard. Furthermore, the computing device (104) may include a mobile phone, smartphone, virtual reality (VR) devices, augmented reality (AR) devices, a laptop, a general-purpose computer, a desktop, a personal digital assistant, a tablet computer, and a
15 mainframe computer. Additionally, input devices for receiving input from the user
(102) such as a touchpad, touch-enabled screen, electronic pen, and the like may be used.
[0069] In an embodiment, the network (106) may include at least one of a
Fifth Generation (5G) network, Sixth Generation (6G) network, or the like. The
20 network (106) may enable the user equipment (104) to communicate with other
devices in the network architecture (100) and/or with the system (108). The network (106) may include a wireless card or some other transceiver connection to facilitate this communication. In another embodiment, the network (106) may be implemented as, or include any of a variety of different communication
25 technologies such as a wide area network (WAN), a local area network (LAN), a
wireless network, a mobile network, a Virtual Private Network (VPN), the Internet, the Public Switched Telephone Network (PSTN), or the like.
16

[0070] In an embodiment, the network (106) may include, by way of
example but not limitation, at least a portion of one or more networks having one
or more nodes that transmit, receive, forward, generate, buffer, store, route, switch,
process, or a combination thereof, etc. one or more messages, packets, signals,
5 waves, voltage or current levels, some combination thereof, or so forth. The
network (106) may also include, by way of example but not limitation, one or more
of a wireless network, a wired network, an internet, an intranet, a public network, a
private network, a packet-switched network, a circuit-switched network, an ad hoc
network, an infrastructure network, a Public-Switched Telephone Network (PSTN),
10 a cable network, a cellular network, a satellite network, a fiber optic network, or
some combination thereof.
[0071] In an embodiment, the user equipment (104) is communicatively
coupled with the system (108). The system (108) may receive a connection request
from the UE (104). The system (108) may send an acknowledgment of the
15 connection request to the UE (104). The UE (104) may transmit a plurality of
signals in response to the connection request. The system (108) may be configured for applying policy rule changes in a network.
[001] FIG. 2A illustrates an exemplary representation (200A) of a PCF
(202) connected to various network nodes to apply the policy rule change, in
20 accordance with an embodiment of the disclosure. Implementation of the disclosed
system and method is dependent upon an architecture of the PCF (202) for enhancing the functioning of PCF functions.
[0072] As shown in the FIG. 2A, the PCF (202) may communicate with a
plurality of network nodes through a plurality of interfaces. The plurality of network
25 nodes includes a plurality of network functions and a plurality of network
interfaces. The plurality of network functions include a deep packet inspection (DPI) (206), a session management function (SMF) (208), a charging function (CHF) (210), a binding support function (BSF) (212), a network repository function
17

(NRF) (214), an access management function (AMF) (204), an application function
(AF) (216), an element management system (EMS) (220), a command line interface
(CLI)/a service management portal (SMP) (224), an adaptive troubleshooting
operations and management (ATOM)/vProbe (218), and a subscription profile
5 repository (SPR) (222). The AMF (204) may communicate with the PCF (202) via
a N15 interface. The DPI (206) may communicate with the PCF (202) via a Sd
interface. The SMF (208) may communicate with the PCF (202) via a N7 interface.
The CHF (210) may communicate with the PCF (202) via a N28 interface. The BSF
(212) may communicate with the PCF (202) via a Nbsf interface. The NRF (214)
10 may communicate with the PCF (202) via a Nnrf interface. The AF (216) may
communicate with the PCF (202) via a Rx interface.
[0073] FIG. 2B illustrates an exemplary representation (200B) of the system
(108) for applying the policy rule change in the network (106), in accordance with an embodiment of the disclosure.
15 [0074] Referring to FIG. 2B, in an embodiment, the system (108) may
include one or more processor(s) (201). The one or more processor(s) (201) may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, logic circuitries, and/or any devices that process data based on operational instructions. Among other
20 capabilities, the one or more processor(s) (201) may be configured to fetch and
execute computer-readable instructions stored in a memory (203) of the system (108). The memory (203) may be configured to store one or more computer-readable instructions or routines in a non-transitory computer readable storage medium, which may be fetched and executed to create or share data packets over a
25 network service. The memory (203) may comprise any non-transitory storage
device including, for example, volatile memory such as random-access memory (RAM), or non-volatile memory such as erasable programmable read only memory (EPROM), flash memory, and the like.
18

[0075] In an embodiment, the system (108) may include an interface(s)
(205). The interface(s) (205) may comprise a variety of interfaces, for example,
interfaces for data input and output devices (I/O), storage devices, and the like. The
interface(s) (205) may facilitate communication through the system (108). The
5 interface(s) (205) may also provide a communication pathway for one or more
components of the system (108). Examples of such components include, but are not limited to, processing engine(s) (207) and a database (209). Further, the processing engine(s) (207) may include one or more engine(s) such as, but not limited to, an input/output engine, an identification engine and an optimization engine.
10 [0076] In an embodiment, the processing engine(s) (207) may be
implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine(s) (207). In examples described herein, such combinations of hardware and programming may be implemented in several different ways. For
15 example, the programming for the processing engine(s) (207) may be processor-
executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processing engine(s) (207) may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the machine-readable storage medium may
20 store instructions that, when executed by the processing resource, implement the
processing engine(s) (207). In such examples, the system may comprise the machine-readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine-readable storage medium may be separate but accessible to the system and the processing resource. In other
25 examples, the processing engine(s) (207) may be implemented by electronic
circuitry.
[0077] In an embodiment, the database (209) includes data that may be
either stored or generated as a result of functionalities implemented by any of the components of the processor (201) or the processing engines (207). In an
19

embodiment, the database (209) may be separate from the system (108). In an embodiment, the database (209) may be indicative of including, but not limited to, a relational database, a distributed database, a cloud-based database, or the like.
[0078] In an embodiment, the system includes the policy control function
5 (PCF) (202). The processing engine(s) (208) is directed towards enhancement in
the functioning of policy control function (PCF) (202).
[0079] FIG. 2C illustrates an exemplary representation (200C) of the PCF
(202) connected to various network nodes, in accordance with an embodiment of the disclosure.
10 [0080] In an aspect, the network nodes may comprise the plurality of
network functions (NFs), and network interfaces. The plurality of network functions includes the SMF (208), the AMF (204). The network interfaces include a Rx interface (236) and a Sd interface (238). Each of the network functions and the network interfaces include a rule engine. The SMF (208) comprises a SMF rule
15 engine (208-2). The AMF 204 comprises an AMF rule engine (204-2). The Rx
interface (236) comprises a Rx rule engine (236-2). The Sd interface comprises a Sd rule engine (238-2).
[0081] The PCF (202) comprises a receiving unit (232) configured to
receive a request from one of the network nodes for policy rule creation or updation.
20 The request may comprise policy rule creation or policy rule updation. The request
from the SMF comprises request for session establishment and control, quality of service (QoS), traffic steering and management, data session, session binding, security management, privacy policy, service continuity, handover policies. The request from the AMF comprises request for resource allocation, Quality of Service
25 (QoS), charging rules, access control, mobility management, security, etc. The
request from Rx interface comprises request for quality of service, charging rules, traffic management, service data flow handling. The request from the Sd interface
20

comprises request for application awareness, service differentiation, traffic steering, quality of service, charging rules.
[0082] In an aspect, policy rules corresponding to access and mobility
management function (AMF) comprises, but not limited to, access control policy
5 rules (e.g., access authentication, access priority, etc.), mobility management policy
rules (e.g., handover, session continuity, etc.), resource allocation policy rules (e.g.,
radio resource management, load balancing, etc.), QoS management policy rules
(e.g., QoS differentiation, QoS adjustment), security management policy rules (e.g.,
access security, authentication, encryption, privacy regulations, etc.) and handover
10 policies.
[0083] In an aspect, policy rules corresponding to session management
function (SMF) comprises, but not limited to, session establishment and control
policy rules (e.g., session setup policies, session duration, etc.), quality of service
(QoS) management (e.g., QoS policies, QoS adjustment, etc.), traffic steering and
15 management (e.g., traffic prioritization, policy on traffic offloading, etc.), policy
enforcement for data management (e.g., data session policies, session binding and release), security and privacy policies (e.g., security management and privacy policies, etc.), service continuity and handover policies (e.g., handover management, etc.).
20 [0084] In an aspect, policy rules corresponding to the Rx interface
comprises, but not limited to, quality of service (e.g., bandwidth, traffic, etc.), charging rules (e.g., billing, etc.), traffic management, service data flow handling, etc.
[0085] In an aspect, policy rules corresponding to Sd interface comprises,
25 but not limited to, application awareness (e.g., application specific policies), service
differentiation, traffic steering (e.g., steering traffic to appropriate bearers or
21

network paths for specific applications, etc.), quality of service (e.g., bandwidth, latency, packet loss thresholds tailored, etc.) and charging rules, etc.
[0086] The PCF (202) comprises a processing unit (234) configured to
determine the one of plurality of network nodes from which the request is received
5 and forward the received request towards a rule engine corresponding to the
determined one of plurality of network nodes. In an aspect, determining of one of
plurality of network nodes from which the request is received includes analyzing
information within headers or payloads of the request. The headers contain source
and destination IP addresses. These addresses can provide information about the
10 originating network nodes (e.g., base station, core network element, network
function, etc.) of the request. The received request is forwarded to the rule engine corresponding to the network node from which the request is received.
[0087] The rule engine corresponding to the determined one of the plurality
of network nodes is configured to check all of plurality of policy rules for the
15 received request based on a plurality of conditions and apply at least one of plurality
of actions. The plurality of actions includes installing or removing a plurality of policies. In an aspect, installing of the plurality of policies comprises steps such as defining of policy rules, policy configuration, policy rule validation, policy rules activations. The policy configuration comprises accessing the configuration
20 interface provided by the policy management systems, inputting policy rules via the
configuration interface. The configured policies are validated to ensure that the polices are aligned with network capabilities, regulatory requirements, and operational constraints, etc. In an aspect, removing of plurality polices comprises steps such as identifying policy rules to be removed. A request to remove the
25 identified policy rules is submitted to the PCF management interface. Performing
validation of policy removal to verify that removing the policy rules will not negatively impact network operations, services, or compliance requirements. Performing deactivation of policy rules includes removing or disabling the rules from the active policy configuration.
22

[0088] In an aspect, the rule engine is configured with rule names and the
plurality of conditions. The plurality of conditions is defined as a plurality of
attributes to match using a plurality of operators and plurality of corresponding
actions. The plurality of operators includes AND, OR, NOT, =, !=, <, <=, >, >=,
5 equal (eq), not equal (neq), gt, lt, range, within range and wildcards. The plurality
of attributes includes service operation, a generic public subscription identifier (GPSI), a subscription permanent identifier (SUPI), an internet protocol (IP), a medium access control (MAC), a data network name (DNN), slice, policy control identities (PCIDS) and location details. The location details include a public land
10 mobile network (PLMN) and a plurality of tracking area codes (TACs). The
plurality of conditions further comprises a rule priority, a rule exclusivity. In an aspect, the plurality of operators are symbols or words that define the relationship between two or more expressions or conditions. The operators allow user to combine conditions and manipulate logical values (true or false). The operators are
15 used in programming, databases, and search queries to perform logical operations
and comparisons. The operators such as the “AND” operator returns true if both operands are true. The “OR” operator returns true if at least one of the operands is true. The “NOT" operator returns the opposite Boolean value of the operand; if true, it returns false, and vice versa. The “Equal” operator checks if two values are equal.
20 The “Not Equal” operator checks if two values are not equal. The “Greater Than
(>)” operator checks if one value is greater than another. The “Less than (<)” operator checks if one value is less than another. The “Greater Than or Equal To (>=)” operator checks if one value is greater than or equal to another. The “Less than or Equal to (<=)” operator checks if one value is less than or equal to another.
25 The wildcard * is commonly used as a placeholder or a wildcard character in
various contexts. Its exact functionality depends on the specific context in which it is used.
[0089] In an embodiment, on detecting an exclusive rule is triggered at
priority, the rule engine is configured to evaluate the exclusive rule and control
30 evaluation of subsequent policy rules. The rule engine is configured to apply one
23

of plurality of actions corresponding to the exclusive rule. On detecting one of the
plurality of actions is applied due to triggering of the exclusive rule at priority, the
rule engine is configured to keep the applied action in force up to a point when the
exclusive rule is triggered at priority. In an aspect, the exclusive rules refer to
5 policies or conditions that are mutually exclusive or cannot coexist simultaneously.
These rules are implemented to ensure that conflicting policies or actions are prevented from occurring concurrently. For example, a subscriber might have exclusive policies that define whether they can access certain types of content, or services based on their subscription plan. In an aspect, exclusive rule is triggered at
10 priority based on real-time network parameters, subscriber behavior, or service
demands. For example, when a user enters a restricted area (e.g., a military zone) while traveling, the restriction rule (e.g., prohibiting video calling, video streaming, etc.) is triggered with high priority due to security constraints. In this scenario, the exclusive rules are the restriction rules. Upon detecting the triggering of restriction
15 rules with high priority, the rule engine is configured to take actions such as
applying restrictions on service usage (e.g., video calling, video streaming) for the user in the restricted area. Furthermore, these restrictions remain in force until the user leaves the restricted area.
[0090] In an embodiment, on detecting the plurality policy rules are not
20 matched with the plurality of conditions, the PCF (202) is configured to perform a
defined action according to a standard. In one example, a user (e.g., subscriber) opts
for a premium service plan that includes streaming services. However, when the
user is in geographical regions where access to applications or services is restricted
due to regulatory requirements, they are unable to use the streaming services. This
25 restriction is enforced according to standard regulatory requirements, despite the
user subscribing to a premium service plan.
[0091] In an embodiment, on detecting that two of plurality of policy rules
are matching the plurality of conditions, the rule engine is configured to evaluate the two of plurality of policy rules and create a new policy rule to prevent
24

modification of an existing policy rule. In one example, for condition 1, opting for
subscription plan 1 provides 20 GB of data with an additional 2 GB offered for free,
while opting for subscription plan 2 provides 50 GB of data with an additional 5
GB offered. If the user (e.g., subscriber) chooses a 60 GB data plan, both conditions
5 1 and 2 are satisfied for the offers. In such cases, the rule engine creates a new offer
to prevent modification of the existing offers.
[0092] In an embodiment, on detecting previously installed policy rules do
not match with the plurality of conditions, the rule engine is configured to remove the previously installed policy rules. In one example, a subscriber switches their
10 SIM card from a 4G to a 5G network. The policy rules previously installed for the
4G SIM card no longer matches the current conditions. Therefore, the rule engine removes the previously installed 4G SIM card policy rules. In an embodiment, for an update request from the Rx interface (236), on detecting no delta changes in existing rules, the rule engine of the Rx interface is configured to send no update to
15 the SMF (208) and send a success response on the Rx interface (236). On detecting
delta changes in the existing rules, the rule engine of the Rx interface (236) is configured to send the delta changes towards the SMF (208). In an aspect, policy rules are defined based on various factors (e.g., subscriber profiles, service plans, network conditions, and regulatory requirements, etc). The rules dictate how
20 different types of traffic should be handled, prioritized, or restricted within the
network. The PCF is responsible for making policy decisions based on the defined rules. The PCF evaluates subscriber-specific information and network conditions to determine the appropriate policies to apply to subscriber sessions. The PCF monitors subscriber traffic and ensures that the defined policies are applied
25 correctly. In an aspect, delta changes in the policy rules refer to incremental updates
or modifications made to existing policy rules rather than complete replacements. In an aspect, on receiving update request from the Rx interface, the Rx rule engine determines policies to be updated. The policy changes are required due to changes in subscriber’s service plan, location, or network conditions, regulatory
30 requirements, etc. The Rx rule engine sends only part of changes required to the
25

policy rules. For example, when the subscriber updates their SIM card from a 4G
network to a 5G network, the Rx rule engine sends information about the SIM card
change from 4G to 5G network via the PCF to the SMF. In another example, the
mobile operator decides to upgrade the Quality of Service (QoS) for a user group
5 subscribed to a premium data service plan. The Rx interface sends the upgrade
request to the PCF. The PCF sends the received upgrade request to the Rx rule
engine that generates a policy delta specifying the QoS improvements (e.g., higher
bandwidth allocation or lower latency requirements). This delta changes are then
be communicated to SMF via the Rx interface. The SMF adjusts its session
10 management procedures to enforce these updated policies for all sessions initiated
by users in that group.
[0093] In an embodiment, on detecting the rules are not installed for a
subscriber, and a policy rule removal action is configured in the rule engine, the PCF (202) is configured to not send the policy rule removal action to the SMF
15 (208). In an aspect, the policy rule removal action refers to the process of removing
or deleting a policy rule that governs how certain traffic is managed within the network. The policy rule removal action is performed due to changes in changes in service configuration, error corrections, compliance, and legal requirements. In one example, if a user is a new subscriber to the network, all the policies applied are
20 new. The rule engine organizes the policy rule removal action. Therefore, the PCF
does not send the policy rule removal action because all the policies are new to the user.
[0094] FIG. 3 illustrates an exemplary flowchart of a method (300) for
applying the policy rule change in a communication network, in accordance with
25 an embodiment of the disclosure.
[0095] The method comprises the plurality of network nodes. The plurality
of network nodes comprises the SMF (208), the AMF (204), the Rx interface (236), the Sd interface (238). Each of the plurality of network nodes comprises a rule
26

engine. For example, the SMF rule engine (208-2) is for the SMF (208), the AMF
rule engine (204-2) is for the AMF (204), the Rx rule engine (236-2) is for the Rx
interface (236) and the Sd rule engine (238-2) is for the Sd interface (238). The
plurality of network nodes and their corresponding rule engines are in
5 communication with the PCF (202).
[0096] As illustrated in FIG. 3, a series of execution steps that are used for
the rule engines of the plurality of network nodes.
[0097] The PCF (202) may receive a request from one of the network nodes
(e.g., SMF (208), AMF (204), Rx interface (236), Sd interface (238)). The PCF
10 (202) may determine the network node from which the request is received. The PCF
(202) may send the received request to the corresponding rule engine of the network node.
[0098] At step (311), on receiving a request from the Sd interface (238), the
PCF (202) sends the request to the Sd rule engine (238-2). The Sd rule engine (238-
15 2) processes the request. The Sd rule engine (238-2) determines whether the rules
are matched with the conditions for the received request.
[0099] At step (312), on detecting that rules match with the conditions, the
Sd rule engine (238-2) may install the rule.
[00100] At step (314), on detecting that rules do not match with the
20 conditions, the Sd rule engine (238-2) may remove the rule.
[00101] At step (315), on receiving a request from the Rx interface (236), the
PCF (202) sends the request to the Rx rule engine (236-2). The Rx rule engine (236-2) processes the request. The Rx rule engine (236-2) determines whether delta changes occur in the existing rules.
27

[00102] At step (316), on detecting no delta changes in existing rules, the Rx
rule engine (236-2) is configured to do not send the update request towards the SMF (208).
[00103] At step (318), the Rx rule engine (236-2) may install a new rule.
5 [00104] At step (320), on detecting the delta changes in the existing rules, the
Rx rule engine (236-2) may send the delta changes to the SMF (208).
[00105] At step (321), on receiving a request from the SMF (208), the PCF
(202) sends the request to the SMF rule engine (208-2). The SMF rule engine (208-
2) processes the request. The SMF rule engine (208-2) determines whether the rules
10 are matched with the conditions for the received request.
[00106] At step (322), on detecting that rules match with the conditions, the
SMF rule engine (208-2) may install the rule.
[00107] At step (324), on detecting that rules do not match with the
conditions, the SMF rule engine (208-2) may remove the rule.
15 [00108] At step (326), the SMF rule engine (208-2) may not push the rule.
[00109] At step (327), on receiving a request from the AMF (204), the PCF
(202) sends the request to the AMF rule engine (204-2). The AMF rule engine (204-2) processes the request. The AMF rule engine (204-2) determines whether the rules are matched with the conditions for the received request.
20 [00110] At step (328), on detecting that rules match with the conditions, the
AMF rule engine (204-2) may install the rule.
[00111] At step (330), on detecting that rules do not match with the
conditions, the AMF rule engine (204-2) may remove the rule.
28

[00112] At step (332), the AMF rule engine (204-2) may not push the rule.
[00113] In an embodiment, an operator may create actions, rules etc., as part
of configuration for plurality of cases using a PCF command line interface (CLI) or
service management portal-user interface (SMP-UI). These configuration changes
5 may be done at runtime by the operator without impacting system functions.
[00114] In an embodiment, each message received at the PCF (202) may be
checked for a corresponding interface of the network nodes and accordingly, may
be forwarded towards the rule engine to apply the policies. The message may
forward through various rules defined in the engine as per a plurality of conditions,
10 a rule priority, and a rule exclusivity. All rules may be checked, and all
corresponding actions may be applied unless following conditions are met:
• The exclusive rule is triggered at priority, which, if matches, do not
allow subsequent rules to be evaluated.
• If the rule action is defined, further rules evaluation is controlled, and
15 no action is taken till the rules applied are in force.
[00115] In case no rule matches the conditions, a default action as per
standard may be performed by the PCF (202).
[00116] The rule engine may remove rules that were installed previously if
the condition does not match with the request.
20 [00117] In case of the Rx interface (236), if delta changes are done in a
dynamic rule definition, then delta changes may be sent towards the SMF (208) instead of full dynamic rule definition. For example, for an update request from the Rx interface (236), on detecting no delta changes in the existing rules, the rule engine of the Rx interface (236) is configured to send no update to the SMF (208)
25 and send a success response on the Rx interface (236). On detecting the delta
29

changes in the existing rules, the rule engine of the Rx interface (236) is configured to send the delta changes towards the SMF (208).
[00118] FIG. 4 illustrates an exemplary flowchart (400) for applying the
policy rule change in a communication network, in accordance with an embodiment
5 of the disclosure.
[00119] At step (402), receiving, by the policy control function (PCF) (202),
a request for policy rule creation or updation from at least one of plurality network
nodes. The plurality of network nodes includes a plurality of network functions and
a plurality of network interfaces. The network functions (NFs) include the session
10 management function (SMF) (208), and the access management function (AMF)
(204). The network interfaces include the Rx interface (236) and the Sd interface (238).
[00120] At step (404), determining, by the PCF (202), the one of plurality of
network nodes from which the request is received.
15 [00121] At step (406), forwarding, by the PCF (202), the request towards a
rule engine corresponding to the determined one of plurality of network nodes.
[00122] At step (408), checking, by the rule engine corresponding to the
determined one of plurality of network nodes, all of plurality of policy rules for the received request based on a plurality of conditions. The plurality of conditions is
20 defined as a plurality of attributes to match using a plurality of operators and
plurality of corresponding actions. The plurality of operators includes AND, OR, NOT, =, !=, <, <=, >, >=, equal (eq), not equal (neq), gt, lt, range, within range and wildcards. The plurality of attributes includes service operation, a generic public subscription identifier (GPSI), a subscription permanent identifier (SUPI), an
25 internet protocol (IP), a medium access control (MAC), a data network name
(DNN), slice, policy control identities (PCIDS) and location details. The location details include a public land mobile network (PLMN) and a plurality of tracking
30

area codes (TACs). The plurality of conditions further comprises a rule priority, a rule exclusivity.
[00123] At step (410), based on the checking, applying, by the rule engine
corresponding to the determined one of plurality of network nodes, at least one of plurality of actions. The plurality of actions includes installing or removing the plurality of policy rules.
[00124] FIG. 5 illustrates an exemplary computer system (500) in which or
with which embodiments of the present disclosure may be implemented.
[00125] As shown in FIG. 5, the computer system may include an external
storage device (510), a bus (520), a main memory (530), a read-only memory (540), a mass storage device (550), communication port(s) (560), and a processor (570). A person skilled in the art will appreciate that the computer system may include more than one processor and communication ports. The processor (570) may include various modules associated with embodiments of the present disclosure. The communication port(s) (560) may be any of an RS-232 port for use with a modem-based dialup connection, a 10/100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or other existing or future ports. The communication port(s) (560) may be chosen depending on a network, such a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system connects.
[00126] The main memory (530) may be random access memory (RAM), or
any other dynamic storage device commonly known in the art. The read-only memory (540) may be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chips for storing static information e.g., start-up or Basic Input/Output System (BIOS) instructions for the processor (570). The mass storage device (550) may be any current or future mass storage solution, which can be used to store information and/or instructions. Exemplary

mass storage device (550) includes, but is not limited to, Parallel Advanced Technology Attachment (PATA) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and/or Firewire interfaces), one or more optical discs, Redundant Array of Independent Disks (RAID) storage, e.g., an array of disks.
[00127] The bus (520) communicatively couples the processor (570) with the
other memory, storage, and communication blocks. The bus (520) may be, e.g., a Peripheral Component Interconnect (PCI)/PCI Extended (PCI-X) bus, Small Computer System Interface (SCSI), Universal Serial Bus (USB), or the like, for connecting expansion cards, drives, and other subsystems as well as other buses, such a front side bus (FSB), which connects the processor (570) to the computer system.
[00128] Optionally, operator and administrative interfaces, e.g., a display,
keyboard, joystick, and a cursor control device, may also be coupled to the bus (520) to support direct operator interaction with the computer system. Other operator and administrative interfaces can be provided through network connections connected through the communication port(s) (560). Components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system limit the scope of the present disclosure.
[00129] While the foregoing describes various embodiments of the
invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof. The scope of the invention is determined by the claims that follow. The invention is not limited to the described embodiments, versions or examples, which are included to enable a person having ordinary skill in the art to make and use the invention when combined with information and knowledge available to the person having ordinary skill in the art.

[00130] The present disclosure provides technical advancement related to
policy rule changes in the communication network. This advancement addresses the limitations of existing solutions by allowing the user to define a smaller number of rules at the PCF using customized rule engine. The disclosure involves removing by the PCF the previously installed rules on its own, if already installed rules condition doesn’t match with the conditions, which offer significant improvements by providing more flexibility and control over control plane flows for making policy rule changes.
ADVANTAGES OF THE PRESENT DISCLOSURE
[00131] The present disclosure facilitates to efficiently manage network
resources by allocating and controlling maximum data transfer rate.
[00132] The present disclosure facilitates a policy control function (PCF) to
remove previously installed rules on its own, if conditions of the already installed rules do not match. This helps to avoid a need to explicitly define a removal action in a policy engine.
[00133] The present disclosure facilitates to provision the rules with mutual
exclusive flag true if only a specific rule is to be pushed to a session management function (SMF) and ignore other rules which match the condition.
[00134] The present disclosure facilitates the PCF to not send remove rules
to the SMF, if the rules are not installed for the subscriber, and if policy rule removal is configured in the policy engine.
[00135] The present disclosure facilitates to use the policy engine to evaluate
conditions of both policies, if the two policies have matching conditions. An operator can create a new policy with action removal to avoid policy modification of an existing rule.

[00136] The present disclosure facilitates to send a no update notification
towards SMF, and a success response on Rx, when Rx trigger is received, and there is no delta change to send in update notification.
[00137] The present disclosure facilitates to provide different attributes and
operator choices for different interfaces such as media-based rules (Rx), session management (SM) policy, access and mobility (AM) policy, application detection and control (ADC) rules (Sd).

WE CLAIM:
1. A method (400) for applying policy rule change in a network (106), the
method comprising:
receiving (402), by a policy control function (PCF) (202), a request for policy rule creation or updation from at least one of plurality network nodes;
determining (404), by the PCF (202), the one of plurality of network nodes from which the request is received;
forwarding (406), by the PCF (202), the received request towards a rule engine corresponding to the determined one of plurality of network nodes;
checking (408), by the rule engine corresponding to the determined one of the plurality of network nodes, all of plurality of policy rules for the received request based on a plurality of conditions; and
based on the checking, applying (410), by the rule engine corresponding to the determined one of the plurality of network nodes, at least one of plurality of actions.
2. The method (400) as claimed in claim 1, wherein the plurality of actions includes installing or removing the plurality of policy rules.
3. The method (400) as claimed in claim 1, wherein the plurality of network nodes comprises a plurality of network functions (NFs) and a plurality of network interfaces, wherein the plurality of network functions (NFs) includes a session management function (SMF) (208), an access management function (AMF) (204), and wherein the plurality of network interfaces includes a Rx interface (236) and a Sd interface (238).
4. The method (400) as claimed in claim 1, further comprising:

on detecting an exclusive rule is triggered at priority, evaluating, by the rule engine, the exclusive rule;
controlling, by the rule engine, evaluation of subsequent policy rules; and
applying, by the rule engine, one of plurality of actions corresponding to the exclusive rule, wherein on detecting, the one of plurality of actions is applied due to triggering of the exclusive rule at priority, keeping, by the rule engine, the applied action in force upto a point when the exclusive rule is triggered at priority.
5. The method (400) as claimed in claim 1, further comprising on detecting
the plurality of policy rules are not matched with the plurality of conditions,
performing, by the PCF (202), a defined action according to a standard.
6. The method (400) as claimed in claim 1, further comprising:
on detecting that two of plurality of policy rules are matching the plurality of conditions, evaluating, by the rule engine, the two of plurality of policy rules; and
creating, by the rule engine, a new policy rule to prevent modification of an existing policy rule.
7. The method (400) as claimed in claim 1 further comprising on detecting previously installed policy rules do not match with the plurality of conditions, removing, by the rule engine, the previously installed policy rules.
8. The method (400) as claimed in claim 3, further comprising:
for an update request from the Rx interface (236):
on detecting no delta changes in existing rules, sending, by the rule engine of the Rx interface (236), no update to the SMF (208); and

sending, by the rule engine of the Rx interface (236), a success response on the Rx interface (236), wherein on detecting the delta changes in the existing rules, sending, by the rule engine of the Rx interface (236), the delta changes towards the SMF (208).
9. The method (400) as claimed in claim 3, further comprising on detecting that the rules are not installed for a subscriber and a policy rule removal action is configured in the rule engine, the PCF (202) is configured to do not send the policy rule removal action to the SMF (208).
10. The method (400) as claimed in claim 1, further comprising:
the rule engine is configured with rule names and the plurality of conditions, wherein the plurality of conditions is defined as a plurality of attributes to match using a plurality of operators and the plurality of corresponding actions, wherein:
the plurality of attributes includes service operation, a generic public subscription identifier (GPSI), a subscription permanent identifier (SUPI), an internet protocol (IP), a medium access control (MAC), a data network name (DNN), slice, policy control identities (PCIDS) and location details, wherein the location details include a public land mobile network (PLMN) and a plurality of tracking area codes (TACs).
11. The method (400) as claimed in claim 1, wherein the plurality of conditions further comprises a rule priority, a rule exclusivity.
12. A system (108) for applying policy rule change in a network (106), the system comprising a policy control function (PCF) (202), the PCF (202) comprising:
a receiving unit (232) configured to receive a request for policy rule creation or updation from at least one of plurality network nodes;

a processing unit (234) configured to:
determine the one of plurality of network nodes from which the request is received; and
forward the received request towards a rule engine corresponding to the determined one of plurality of network nodes; and
the rule engine corresponding to the determined one of the plurality of network nodes configured to:
check all of plurality of policy rules for the received request based on a plurality of conditions; and
based on the checking, apply at least one of plurality of actions, wherein the plurality of actions includes installing or removing a plurality of policies.
13. The system (108) claimed as in claim 12, wherein the plurality of actions includes installing or removing a plurality of policies.
14. The system (108) claimed as in claim 12, wherein the plurality of network nodes comprises a plurality of network functions (NFs) and a plurality of network interfaces, wherein the plurality of network functions (NFs) includes a session management function (SMF) (208), an access management function (AMF) (204), and wherein the plurality of network interfaces includes a Rx interface (236) and a Sd interface (238).
15. The system (108) claimed as in claim 12, further comprising:
on detecting an exclusive rule is triggered at priority, the rule engine is configured to:
evaluate the exclusive rule;
control evaluation of subsequent policy rules; and
apply one of plurality of actions corresponding to the exclusive rule, wherein on detecting, the one of plurality of actions is applied due to

triggering of the exclusive rule at priority, the rule engine is configured to keep the applied action in force up to a point when the exclusive rule is triggered at priority.
16. The system (108) claimed as in claim 12, wherein on detecting the plurality of policy rules are not matched with the plurality of conditions, the PCF (202) is configured to perform a defined action according to a standard.
17. The system (108) as claimed in claim 12, further comprising:
on detecting that two of plurality of policy rules are matching the
plurality of conditions, the rule engine is configured to: evaluate the two of plurality of policy rules; and create a new policy rule to prevent modification of an existing policy
rule.
18. The system (108) as claimed in claim 12, further comprising: on detecting previously installed policy rules do not match with the plurality of conditions, the rule engine is configured to remove the previously installed policy rules.
19. The system (108) as claimed in claim 14, further comprising:
for an update request from the Rx interface (236),
on detecting no delta changes in existing rules, the rule engine of the
Rx interface (236) is configured to:
send no update to the SMF (208); and
send a success response on the Rx interface (236), wherein
on detecting the delta changes in the existing rules, the rule engine
of the Rx interface (236) is configured to send the delta changes towards the
SMF (208).

20. The system (108) as claimed in claim 14, further comprising on detecting that the rules are not installed for a subscriber and a policy rule removal action is configured in the rule engine, the PCF (202) is configured to do not send the policy rule removal action to the SMF (208).
21. The system (108) as claimed in claim 12, further comprising:
the rule engine is configured with rule names and the plurality of conditions, wherein the plurality of conditions is defined as a plurality of attributes to match using a plurality of operators and the plurality of corresponding actions, wherein
the plurality of attributes includes service operation, a generic public subscription identifier (GPSI), a subscription permanent identifier (SUPI), an internet protocol (IP), a medium access control (MAC), a data network name (DNN), slice, policy control identities (PCIDS) and location details, wherein the location details include a public land mobile network (PLMN) and a plurality of tracking area codes (TACs).
22. The system (108) as claimed in claim 12, wherein the plurality of conditions further comprises a rule priority, a rule exclusivity.
23. A user equipment (104) communicatively coupled with a system (108), the coupling comprises steps of:
receiving, by the system (108), a connection request;
sending, by the system (108), an acknowledgment of the connection request to the user equipment (104); and
transmitting a plurality of signals in response to the connection request, wherein the system (108) is configured for applying policy rule change in a network as claimed in claim 12.