FORM 2
THE PATENTS ACT, 1970
(39 of 1970)
THE PATENTS RULES, 2003
COMPLETE
SPECIFICATION
(See section 10; rule 13)
TITLE OF THE INVENTION
SYSTEM AND METHOD FOR MANAGING POLICIES ACROSS MULTIPLE CLUSTERS IN
WIRELESS NETWORK
APPLICANT
JIO PLATFORMS LIMITED
of Office-101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad -
380006, Gujarat, India; Nationality : India
The following specification particularly describes
the invention and the manner in which
it is to be performed
2
RESERVATION OF RIGHTS
[001] 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
5 dress protection, belonging to JIO PLATFORMS LIMITED or its affiliates (herein
after 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.
10 TECHNICAL FIELD
[002] The present disclosure relates to a field of wireless networks, and
specifically to a system and a method for managing policies across multiple clusters
in a wireless network.
DEFINITION
15 [003] 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.
[004] The expression ‘policy synchronization’ used hereinafter in the
specification refers to a process of ensuring that the policies or rules applied to a
20 system or network are consistent across different nodes or clusters. This involves
harmonizing the configuration of policies so that they are uniformly applied and
enforced across multiple entities.
[005] The expression ‘Remote Procedure Call (RPC)’ used hereinafter in
the specification refers to a protocol that enables a program running on one
25 computer to execute code on a remote system as if it were a local function or
procedure call. In simpler terms, RPC allows a program to invoke procedures or functions on another computer across a network, making it appear as if the function
is executing locally.
[006] The expression ‘Policy Control Function (PCF)’ used hereinafter in
the specification refers to a component within telecommunications networks,
5 particularly in the context of 5G networks. It's responsible for managing and
enforcing policies related to various aspects of network operation, such as Quality
of Service (QoS), charging, access control, and network resource allocation.
[007] These definitions are in addition to those expressed in the art.
BACKGROUND
10 [008] 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,
15 and not as admissions of prior art.
[009] In general, a Policy Control Function (PCF) node in a wireless
network provides the following functions: policy rules for application and service
data flow detection, gating, Quality of Service (QoS), and flow-based charging to
a Session Management Function (SMF) node, Access and Mobility Management
20 related policies to an Access and Mobility Management Function (AMF) node,
service configurations, policy configurations, and session viewer appear
underneath.
[0010] Traditionally, when there are updates or modifications to policies or
rules, such as security protocols, access permissions, or operational guidelines, each
25 PCF cluster would require manual configuration. This manual configuration
process is time-consuming and prone to errors, especially as the number of clusters
and policies increases.
4
[0011] Without synchronization, administrators would have to individually
configure each policy in every cluster. This not only consumes time but also
increases the likelihood of inconsistencies and errors between clusters.
Additionally, it imposes additional administrative overhead, as administrators must
5 manage and maintain policies across multiple clusters separately.
[0012] There is, therefore, a need in the art to improve the state of
configuring policies by enhancing the process of configuring policies within a
cluster. This involves centralizing the configuration and synchronization of policies
within a single cluster. This approach allows changes to be made once and applied
10 across all clusters, reducing the requirement for manual intervention in each cluster.
SUMMARY OF THE PRESENT DISCLOSURE
[0013] The present disclosure relates to a method for managing policies
across a plurality of Policy Control Function (PCF) nodes in a network. A method
for managing policies across a plurality of Policy Control Function (PCF) clusters
15 in a network. Each PCF cluster includes a source PCF node and one or more target
PCF nodes. The method includes configuring, by a processing unit, a set of policies
of the source PCF node associated with a first PCF cluster of the network. The
method includes receiving, a receiving unit, a policy synchronization request.
Based on the policy synchronization request, the method includes retrieving, by the
20 processing unit and from a database, details of the policies associated with one or
more target PCF nodes in the network. Based on the retrieved details of the one or
more target PCF nodes, the method includes, synchronizing, by the processing unit,
the set of policies associated with the one or more target PCF nodes in accordance
with the set of configured policies of the source PCF node.
25 [0014] In an embodiment, based on the policy synchronization request, the
method includes selecting, by the processing unit, a type of policy synchronization,
wherein the type of policy synchronization comprises an intra-cluster policy
synchronization and an inter-cluster policy synchronization.
5
[0015] In an embodiment, the one or more target PCF nodes are associated
with one of the first PCF cluster and a second PCF cluster.
[0016] Upon selecting the intra-cluster policy synchronization, the method
includes retrieving details of a first target PCF node associated with the first PCF
5 cluster by the processing unit and from the database.
[0017] Upon selecting the inter-cluster policy synchronization, the method
includes retrieving, by the processing unit and from the database, details of a second
target PCF node associated with the second PCF cluster.
[0018] Based on the selection of one of the inter-cluster policy
10 synchronization and the intra-cluster policy synchronization, the method includes
synchronizing, by the processing engine, the set of configured policies to one of the
first target PCF node and the second target PCF node.
[0019] In an aspect, the method includes verifying, by the processing unit,
the set of policies according to a set of defined parameters. The set of defined
15 parameters includes data rate limits, priority levels, and charging rules.
[0020] In an embodiment, the inter-cluster policy synchronization includes
performing synchronization in PCF nodes of a plurality of PCF clusters deployed
within the network, and wherein the intra-cluster policy synchronization includes
performing synchronization in PCF nodes of a same PCF cluster.
20 [0021] In an embodiment, a step of synchronizing the set of policies
comprising replacing existing policies associated with the first target PCF node and
the second target PCF node with the set of configured policies of the source PCF
node.
[0022] In an embodiment, the method further includes performing a Remote
25 Procedure Call (RPC) for synchronizing the set of policies to the first target PCF
node or the second target PCF node.
6
[0023] The present disclosure relates to a system for managing policies
across a plurality of Policy Control Function (PCF) clusters in a network. Each PCF
cluster comprises a source PCF node and one or more target PCF nodes. The system
includes a receiving unit, a memory, and a processing unit. The receiving unit is
5 configured to receive a policy synchronization request. The memory is coupled to
the processing unit. The memory includes computer-implemented instructions to
configure the processing unit to configure a set of policies of the source PCF node
associated with a first PCF cluster of the network. Based on the policy
synchronization request, the processing unit is configured to retrieve, from a
10 database, details of the policies associated with one or more target PCF nodes in
the network. Based on the retrieved details of the policies associated with each
target PCF node, the processing unit is configured to synchronize the set of policies
associated with the one or more target PCF nodes in accordance with the set of
configured policies of the source PCF node.
15 [0024] In an embodiment, the processing unit is further configured to, based
on the policy synchronization request, select a type of policy synchronization,
wherein the type of policy synchronization comprises an intra-cluster policy
synchronization and an inter-cluster policy synchronization.
[0025] In an embodiment, the one or more target PCF nodes are associated
20 with one of the first PCF cluster and a second PCF cluster.
[0026] Upon selecting the intra-cluster policy synchronization, the
processing unit is further configured to retrieve, from the database, details of a first
target PCF node associated with the first PCF cluster.
[0027] Upon selecting the inter-cluster policy synchronization, the
25 processing unit is further configured to retrieve, from the database, details of a
second target PCF node associated with the second PCF cluster.
[0028] Based on the selection of one of the inter-cluster policy
synchronization and the intra-cluster policy synchronization, the processing unit is
7
further configured to synchronize the set of policies to one of the first target PCF
node and the second target PCF node.
[0029] In an embodiment, the processing unit is further configured to upon
configuration, verify the set of policies according to a set of defined parameters,
5 wherein the set of defined parameters includes data rate limits, priority levels, and
charging rules.
[0030] In an embodiment, to synchronize the set of policies, the processing
unit is further configured to replace existing policies associated with the first target
PCF node and the second target PCF node with the set of configured policies of the
10 source PCF node.
[0031] In an embodiment, the processing unit is further configured to
perform a Remote Procedure Call (RPC) to synchronize the set of policies to the
first target PCF node or the second target PCF node.
[0032] In an embodiment, the present disclosure discloses a user equipment
15 is communicatively coupled with a system. The coupling comprises steps of
receiving a connection request from the system, sending an acknowledgment of the
connection request to the system, and transmitting a plurality of signals in response
to the connection request, wherein the system is configured to manage policies
across a plurality of Policy Control Function (PCF) clusters in a network.
20 [0033] The foregoing summary is illustrative only and is not intended to be
in any way limiting. In addition to the illustrative aspects, embodiments, and
features described above, ffurther aspects, embodiments, and features will become
apparent by reference to the drawings and the following detailed description.
OBJECTS OF THE PRESENT DISCLOSURE
25 [0034] It is an object of the present disclosure to provide a system and a
method to configure one or more policies in one cluster.
8
[0035] It is an object of the present disclosure to synchronize the
configuration of one or more policies so that the synchronized configurations are
uniformly applied and enforced across multiple entities.
[0036] It is an object of the present disclosure to significantly reduce the
5 time and effort required to implement policy changes across multiple clusters.
[0037] It is an object of the present disclosure to push one or more policies
from one cluster to others and ensure consistency in policy configuration
throughout a super-core, thereby reducing the risk of errors or inconsistencies that
may occur when configuring one or more policies individually in each cluster.
10 [0038] It is an object of the present disclosure to perform any updates,
modifications, or troubleshooting in one place, making it easier to maintain and
manage policies across the super-core.
[0039] It is an object of the present disclosure to easily scale the policy
management process without adding excessive overhead.
15 BRIEF DESCRIPTION OF THE DRAWINGS
[0040] 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
20 specification, the description is applicable to any one of the similar components
having the same first reference label irrespective of the second reference label.
[0041] The diagrams are for illustration only, which thus is not a limitation
of the present disclosure, and wherein:
[0042] FIG. 1 illustrates an exemplary network architecture for
25 implementing a system for managing policies across a plurality of Policy Control
9
Function (PCF) clusters in a network, in accordance with an embodiment of the
present disclosure.
[0043] FIG. 2 illustrates an exemplary block diagram of the system (“policy
synchronization system”), in accordance with an embodiment of the present
5 disclosure.
[0044] FIG. 3 illustrates an exemplary flow diagram followed by the policy
synchronization system, in accordance with an embodiment of the present
disclosure.
[0045] FIG. 4 illustrates an exemplary flow chart of a method for
10 synchronizing policies across the plurality of PCF clusters, in accordance with an
embodiment of the present disclosure.
[0046] FIG. 5 illustrates an exemplary computer system in which or with
which embodiments of the present disclosure may be implemented.
[0047] FIG. 6 illustrates an exemplary flow diagram of a policy
15 synchronization method for managing policies across the plurality of PCF clusters
in the network, in accordance with an embodiment of the present disclosure.
LIST OF REFERENCE NUMERALS
100 – Network architecture
102-1, 102-2…102-N – Users
20 104-1, 104-2…104-N – User Equipments
106 – Network
108 – System
200 – Block diagram
202 – Receiving Unit
25 204 – Memory
206 – Interface(s)
208 – Processing unit
10
210 – Database
212 – Synchronization engine
214 – Other engine(s)
300 – Flow diagram
5 400 – Flow chart
500 – Computer system
510 – External Storage Device
520 – Bus
530 – Main Memory
10 540 – Read Only Memory
550 – Mass Storage Device
560 – Communication Port
570 – Processor
DETAILED DESCRIPTION OF DISCLOSURE
15 [0048] 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
20 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
fully addressed by any of the features described herein. Example embodiments of
the present disclosure are described below, as illustrated in various drawings in
25 which like reference numerals refer to the same parts throughout the different
drawings.
[0049] 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
11
skilled in the art with an enabling description for implementing an exemplary
embodiment. It should be understood that various changes may be made in the
function and arrangement of elements without departing from the spirit and scope
of the disclosure as set forth.
5 [0050] 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
10 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.
[0051] Also, it is noted that individual embodiments may be described as a
process that is depicted as a flowchart, a flow diagram, a data flow diagram, a
15 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
20 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.
[0052] The word “exemplary” and/or “demonstrative” is used herein to
mean serving as an example, instance, or illustration. For the avoidance of doubt,
25 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
12
“includes,” “has,” “contains,” and other similar words are used in either the detailed
description or the claims, such terms are intended to be inclusive like the term
“comprising” as an open transition word without precluding any additional or other
elements.
5 [0053] 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 disclosure. Thus, the appearances of the
phrases “in one embodiment” or “in an embodiment” in various places throughout
10 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.
[0054] The terminology used herein is to describe particular embodiments
only and is not intended to be limiting the disclosure. As used herein, the singular
15 forms “a”, “an”, and “the” are intended to include the plural forms as well, unless
the context 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
20 features, integers, steps, operations, elements, components, and/or groups thereof.
As used herein, the term “and/or” includes any combinations of one or more of the
associated listed items. It should be noted that the terms “mobile device”, “user
equipment”, “user device”, “communication device”, “device” and similar terms
are used interchangeably for the purpose of describing the invention. These terms
25 are not intended to limit the scope of the invention 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 invention is not limited to
any particular type of device or equipment, and it should be understood that other
equivalent terms or variations thereof may be used interchangeably without
30 departing from the scope of the invention as defined herein.
13
[0055] As used herein, an “electronic device”, or “portable electronic
device”, or “user device” or “communication device” or “user equipment” or
“device” refers to any electrical, electronic, electromechanical, and computing
device. The user device is capable of receiving and/or transmitting one or
5 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 equipment may be capable of operating on any radio
access technology including but not limited to IP-enabled communication, Zig Bee,
10 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, a general-purpose computer, desktop, personal digital assistant,
tablet computer, mainframe computer, or any other device as may be obvious to a
15 person skilled in the art for implementation of the features of the present disclosure.
[0056] Further, the user device may also comprise a “processor” or
“processing unit” includes 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
20 processor, a plurality of microprocessors, one or more microprocessors in
association with a 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
25 the system according to the present disclosure. More specifically, the processor is
a hardware processor.
[0057] As portable electronic devices and wireless technologies continue to
improve and grow in popularity, the advancing wireless technologies for data
transfer are also expected to evolve and replace the older generations of
30 technologies. In the field of wireless data communications, the dynamic
14
advancement of various generations of cellular technology are also seen. The
development, in this respect, has been incremental in the order of second generation
(2G), third generation (3G), fourth generation (4G), and now fifth generation (5G),
and more such generations are expected to continue in the forthcoming time.
5 [0058] While considerable emphasis has been placed herein on the
components and component parts of the preferred embodiments, it will be
appreciated that many embodiments can be made and that many changes can be
made in the preferred embodiments without departing from the principles of the
disclosure. These and other changes in the preferred embodiment as well as other
10 embodiments of the disclosure will be apparent to those skilled in the art from the
disclosure herein, whereby it is to be distinctly understood that the foregoing
descriptive matter is to be interpreted merely as illustrative of the disclosure and
not as a limitation.
[0059] Previously, when there were new policy or rule changes, it was
15 necessary to configure them individually in each PCF cluster. However, to
streamline this process and save time, we can now configure the policy in just one
cluster. Once the configuration is successfully verified, the policy can be pushed to
the remaining clusters within the same super-core. This can be accomplished using
either a CLI command or the SMP GUI. Each instance or cluster would need to be
20 configured individually without synchronization, leading to inconsistencies, errors,
and additional administrative overhead.
[0060] The present disclosure configures one or more policies or instances
in one cluster. Multiple clusters form a super-core. Once the configuration is
successfully verified, the policy may be pushed to the remaining clusters within the
25 same network (super-core). This may be accomplished using either a CommandLine Interface (CLI) or a Service Management Platform (SMP) Graphical User
Interface (GUI). In an aspect, the SMP typically refers to a centralized system or
solution designed to manage and optimize the delivery of services within an
organization.
15
[0061] The various embodiments of the present disclosure will be explained
in detail with reference to FIGS. 1 to 6.
[0062] FIG. 1 illustrates an exemplary network architecture (100) for
implementing a system (108) for managing policies across a plurality of Policy
5 Control Function (PCF) clusters in a network, in accordance with an embodiment
of the present disclosure. Each PCF cluster comprises a source PCF node and one
or more target PCF nodes.
[0063] Referring to FIG. 1, the network architecture (100) may include one
or more computing devices or user equipments (104-1, 104-2…104-N) associated
10 with one or more users (102-1, 102-2…102-N) in an environment. A person of
ordinary skill in the art will understand that one or more users (102-1, 102-2…102-
N) may be individually referred to as the user (102) and collectively referred to as
the users (102). Similarly, a person of ordinary skill in the art will understand that
one or more user equipments (104-1, 104-2…104-N) may be individually referred
15 to as the user equipment (104) and collectively referred to as the user equipment
(104). A person of ordinary skill in the art will appreciate that the terms “computing
device(s)” and “user equipment” may be used interchangeably throughout the
disclosure. Although three user equipments (104) are depicted in FIG. 1, however
any number of the user equipments (104) may be included without departing from
20 the scope of the ongoing description.
[0064] In an embodiment, the user equipment (104) may include smart
devices operating in a smart environment, for example, an Internet of Things (IoT)
system. In such an embodiment, the user equipment (104) may include, but is not
limited to, smart phones, smart watches, smart sensors (e.g., mechanical, thermal,
25 electrical, magnetic, etc.), networked appliances, networked peripheral devices,
networked lighting system, communication devices, networked vehicle accessories,
networked vehicular devices, smart accessories, tablets, smart television (TV),
computers, smart security system, smart home system, other devices for monitoring
or interacting with or for the users (102) and/or entities, or any combination thereof.
16
A person of ordinary skill in the art will appreciate that the user equipment (104)
may include, but is not limited to, intelligent, multi-sensing, network-connected
devices, that can integrate seamlessly with each other and/or with a central server
or a cloud-computing system or any other device that is network-connected.
5 [0065] In an embodiment, the user equipment (104) may include, but is not
limited to, a handheld wireless communication device (e.g., a mobile phone, a smart
phone, a phablet device, and so on), a wearable computer device(e.g., a headmounted display computer device, a head-mounted camera device, a wristwatch
computer device, and so on), a Global Positioning System (GPS) device, a laptop
10 computer, a tablet computer, or another type of portable computer, a media playing
device, a portable gaming system, and/or any other type of computer device with
wireless communication capabilities, and the like. In an embodiment, the user
equipment (104) may include, but is not limited to, any electrical, electronic,
electro-mechanical, or an equipment, or a combination of one or more of the above
15 devices such as virtual reality (VR) devices, augmented reality (AR) devices,
laptop, a general-purpose computer, desktop, personal digital assistant, tablet
computer, mainframe computer, or any other computing device, wherein the user
equipment (104) may include one or more in-built or externally coupled accessories
including, but not limited to, a visual aid device such as a camera, an audio aid, a
20 microphone, a keyboard, and input devices for receiving input from the user (102)
or the entity such as touch pad, touch enabled screen, electronic pen, and the like.
A person of ordinary skill in the art will appreciate that the user equipment (104)
may not be restricted to the mentioned devices and various other devices may be
used.
25 [0066] Referring to FIG. 1, the user equipment (104) may communicate
with the system (108) (also referred to as “a policy synchronization system”)
through a network (106). In an aspect, the user equipment is communicatively
coupled with a system. The coupling comprises steps of receiving a connection
request from the system, sending an acknowledgment of the connection request to
30 the system, and transmitting a plurality of signals in response to the connection
17
request, wherein the system is configured to manage policies across the plurality of
PCF clusters in the network. The system (108) may centralize and streamline the
management of policies across multiple instances or clusters. The policy
synchronization system (108) may define and configure policies in a single source
5 and then propagate them to other entities within the super-core, thereby eliminating
the need to configure policies individually in each instance or cluster. This
significantly reduces the time and effort required for policy deployment, updates,
and maintenance.
[0067] By synchronizing the policies, the policy synchronization system
10 (108) may ensure consistent and uniform policy enforcement across the super-core,
thereby minimizing the risk of configuration errors, policy discrepancies, and
inconsistent behaviour across different components. The policy synchronization
system (108) may promote a standardized approach to policy management.
Additionally, the flexibility to propagate policies through CLI (Command Line
15 Interface) commands and GUI (Graphical User Interface) interfaces for policy
propagation may offer adaptability to different management preferences. CLI
commands allow administrators to automate policy propagation tasks by scripting
repetitive actions. This is particularly beneficial in large-scale deployments where
manual configuration becomes impractical. Automation through CLI commands
20 improves efficiency and reduces the risk of human error. GUI interfaces provide a
user-friendly way to interact with the policy synchronization system, especially for
less experienced administrators or those who prefer visual representations. GUI
interfaces typically offer intuitive controls, visual feedback, and guided workflows,
making it easier to define, configure, and propagate policies. By offering both CLI
25 commands and GUI interfaces caters to different management preferences within
an organization. Some administrators may prefer the flexibility and power of CLI
for advanced configuration tasks, while others may find GUI interfaces more
accessible for day-to-day operations. Providing both options ensures that all
administrators can work efficiently according to their preferences. The policy
18
synchronization system (108) simplifies and optimizes the management of policies
across the super-core.
[0068] In an embodiment, the network (106) may include at least one of a
Fifth Generation (5G) network, 6G network, or the like. The network (106) may
5 enable the user equipment (104) to communicate with other devices in the network
architecture (100) and/or with the policy synchronization 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 technologies
10 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.
[0069] Although FIG. 1 shows exemplary components of the network
architecture (100), in other embodiments, the network architecture (100) may
15 include fewer components, different components, differently arranged components,
or additional functional components than depicted in FIG. 1. Additionally, or
alternatively, one or more components of the network architecture (100) may
perform functions described as being performed by one or more other components
of the network architecture (100).
20 [0070] FIG. 2 illustrates an exemplary block diagram (200) of the policy
synchronization system (108), in accordance with an embodiment of the present
disclosure.
[0071] As shown in FIG. 2, the system (108) includes a receiving unit (202),
a memory (204), and a processing unit (208). The receiving unit (202) is configured
25 to receive a policy synchronization request. In an aspect, the receiving unit (202) is
configured to receive the request from the user. In another aspect, the receiving unit
(202) is configured to receive a set of instructions from the user for configuring a
set of policies associated with the PCF. The receiving unit (202) is configured to
set up communication channels through which synchronization requests may be
19
received. In an example, the policy synchronization request includes a plurality of
information, such as details of the source node from where policy changes originate
and details of the target nodes or clusters that need updates. Further, the policy
synchronization request may include timestamps or details of tracking the versions
5 of the policies, suggesting when changes were made and ensuring updates are
applied in sequence. For example, the policy synchronization request may include
one or more modified policies, including parameters and conditions, to clarify the
scope of synchronization.
[0072] The memory (204) is coupled to the processing unit (208). The
10 memory (204) includes computer-implemented instructions to configure the
processing unit (208) to manage policies across the plurality of PCF clusters. The
memory (204) 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 network
15 service. The memory (204) 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.
[0073] The processing unit (208) may include one or more engines selected
20 from any of a synchronization engine (212) and other engine(s) (214).
[0074] In an aspect, the plurality of PCF clusters includes a first PCF cluster
and a second PCF cluster. Each PCF cluster comprises a source PCF node and one
or more target PCF nodes. PCF nodes are network elements responsible for
managing and enforcing policies related to Quality of Service (QoS), access
25 control, and charging within a telecommunications network. They ensure that
network resources are allocated efficiently, traffic is prioritized according to service
requirements, and users are authenticated and authorized appropriately. PCF nodes
also handle charging functions, determining how subscribers are billed based on
their usage of network services. The source PCF node refers to a specific node
20
within a telecommunications network where initial policy configurations or updates
originate. This node serves as the point of origin for defining, modifying, or
synchronizing policies that govern various aspects such as Quality of Service
(QoS), access control, and charging rules across the network. Changes made at the
5 source PCF node are propagated to other nodes or clusters within the network to
ensure consistency and uniformity in policy enforcement and management. The one
or more target PCF nodes are designated nodes within the telecommunications
network that receive and implement policies configured or updated at the source
PCF node. These nodes are recipients of policy synchronization requests and
10 adjustments, ensuring that all nodes within the network ecosystem operate under
the same set of policies. The first PCF cluster includes a first source PCF and one
or more first target PCF nodes. The first source PCF node acts as a primary
authority for initiating, managing, and distributing policy configurations and
updates across the cluster. The first source PCF node defines policies related to
15 Quality of Service (QoS), access control, charging, and network management. The
one or more first target PCF nodes receive these policies and enforce them locally
within their respective network segments or regions. In similar manner, the second
PCF cluster includes a second source PCF and one or more second target PCF
nodes. The second source PCF node acts as a primary authority for initiating,
20 managing, and distributing policy configurations and updates across the cluster.
The second source PCF node defines policies related to Quality of Service (QoS),
access control, charging, and network management. The one or more second target
PCF nodes receive these policies and enforce them locally within their respective
network segments or regions. The processing unit (208) is able to configure the set
25 of policies of the source PCF node associated with the first PCF cluster of the
network (106).
[0075] In an embodiment, the processing unit (208) is further configured to
verify the set of policies according to a set of defined parameters upon
configuration. In an aspect, the processing unit (208) checks if the configured set
30 of policies aligns with the specified standards or requirements by mapping the
21
configured set of policies with the set of defined parameters. For example, for each
policy, the processing unit checks if it meets the defined parameters (may be
defined by network operators). This evaluation involves comparing the content of
each policy against the criteria specified in the parameters. In an example, the set
5 of defined parameters includes data rate limits, priority levels, and charging rules.
The synchronization engine (212) may initially define and configure desired
policies or rules in a single instance or cluster (for example, the first PCF cluster).
The policies may be configured a Command-Line Interface (CLI) or a Service
Management Platform (SMP) Graphical User Interface (GUI). In an aspect, the
10 system is configured to use CLI commands to retrieve the configured policies from
the database. This may involve commands specific to the policy management
module or subsystem. Furthermore, the system is configured to verify that the
parameters of the configured policy, such as QoS settings, access control rules, or
charging policies, are correctly configured according to the desired requirements.
15 The system is configured to configure policies that may be verified and tested in a
source instance or cluster to ensure their correctness and effectiveness. The
verification of the configured policies may ensure that the policies are functional
and aligned with the intended objectives. Once the policies are successfully
verified, the policies may be propagated or pushed to the other instances or clusters
20 within the super-core. This may be done through various means such as, for
example, CLI commands and GUIs. The propagated policies may replace the
existing ones in a target instance or cluster.
[0076] In operation, in an embodiment, the processing unit (208) is
configured to receive the policy synchronization request pertaining to a set of
25 policies. In an embodiment, the set of policies includes various policy rules that are
essential for managing and enforcing policies related to quality of service (QoS),
charging, and access control. The policy rules may be divided into the following
categories, however, it should be appreciated that these policy rules are illustrative
and not exhaustive, and are not limited to any particular rule:
22
 Policy Control Rules: These rules govern the QoS and other policy-related
aspects of the network services provided to the users. These rules may
include:
o QoS Policy Rules: define the QoS parameters such as latency, jitter,
5 bandwidth, and priority for different types of traffic. They ensure
that critical applications like VoIP, video conferencing, etc. receive
the appropriate network resources.
o Access Control Rules: determine which users or devices can access
certain network resources or services, ensuring security and
10 compliance with operator policies.
o Application Detection Rules: identify specific applications and
apply appropriate policies to them. This helps in optimizing the
network performance for high-priority applications.
 Charging Rules: These rules define how different services and usage
15 patterns are charged. These rules may include:
o Online Charging Rules: enable real-time charging of services,
ensuring that users are billed accurately as they consume resources.
o Offline Charging Rules: allow for post-paid billing, where usage
data is collected and processed later for billing purposes. This
20 includes gathering data on data usage, call duration, and other
metrics.
o Service-Specific Charging Rules: define different charging models
for various services (e.g., data, voice, SMS, streaming), allowing
operators to implement flexible billing strategies.
25  Traffic Steering Rules: These rules help in directing traffic to the
appropriate network resources based on policies. These rules may include:
o Traffic Routing Rules: specify how traffic should be routed through
the network to optimize performance and resource utilization. For
example, traffic can be directed through specific network slices that
30 are optimized for certain applications.
23
o Load Balancing Rules: distribute traffic evenly across the network
to prevent congestion and ensure efficient use of network resources.
[0077] Further, the set of policies is configured in a source PCF node
associated with a PCF cluster of the wireless network. In examples, the set of
5 policies are configured based by accessing the source PCF node. In examples, the
PCF mode may be accessed through a management interface, a console, a command
line interface, or a web-based management graphical user interface using
administrator credentials. Post access, the policies may configured, tested and
saved. In examples, if there are cluster of PCF modes, the configured policies may
10 be synchronized among the cluster of nodes. Further, upon configuring the set of
policies, the configured set of policies in the source PCF node is verified. Based on
the policy synchronization request, details of one or more target PCF nodes in the
wireless network are retrieved from a database (210). In an example, the details
retrieved from the database regarding policies associated with target PCF nodes
15 include various headers such as policy definitions, policy parameters, policy
associations details, and policy versions and timestamps. The policy definitions
describe the objectives and scope of each policy such as Quality of Service (QoS)
policies prioritizing traffic types, and access Control policies defining user access
rules. Policy parameters specify QoS parameters for bandwidth and latency and
20 access control parameters like authentication methods. Policy versions and
timestamps indicate modification history, such as Version 1.2 updated on May 15,
2023. In an example, the policy association details include details of policies that
are applied to specific PCF nodes, such as node A with QoS and Access Control
policies and node B with QoS and Billing policies, ensuring consistent policy
25 application across the network. In an embodiment, for example, the operator wants
to update a specific policy rule (e.g., maximum data usage policy rule) using the
CLI or GUI, he/she can select the specific policy rule belonging to the maximum
data usage policy rule and reset its counter value to ‘0’. In an example, the policy
versions may indicate a version of the configured policies 2.0 having a set of
30 configured policies. In an aspect, the nodes having version less than 2.0 may be
24
configured to employ the set of configured policies. For example, the database
(210) may be an external database. In another example, the database (210) may be
integrated into the system (108). In an embodiment, the one or more target PCF
nodes may be associated with the same PCF cluster which comprises the source
5 PCF node. In another embodiment, the one or more target PCF nodes may be
associated with a PCF cluster different from the PCF cluster which comprises the
source PCF node.
[0078] In an embodiment, the verified set of policies, which is configured
in the source PCF node, is synchronized to the one or more target PCF nodes based
10 on the retrieved details of the one or more target PCF nodes. In examples, the
synchronization is performed using configuration management tools. In
implementations, the configuration management tools may include command line
interface or graphical user interface options to manage configurations and
synchronizing them across the one or more target PCF nodes.
15 [0079] Based on the retrieved details of the policies associated with each
target PCF node, the processing unit (208) is configured to synchronize the set of
policies associated with the one or more target PCF nodes in accordance with the
set of configured policies of the source PCF node. In an aspect, the one or more
target PCF nodes are associated with one of the first PCF cluster and the second
20 PCF cluster. In an aspect, the set of configured policies comprises specific rules and
guidelines that dictate how network resources are managed, services are delivered,
and users are billed. The set of configured policies may be made according to the
request made by the operator. In an aspect, the set of configured policies may
include QoS policies, access control policies, charging and billing policies, or
25 security policies.
[0080] In an embodiment, the processing unit (208) is further configured to,
based on the policy synchronization request, select a type of policy synchronization,
wherein the type of policy synchronization comprises an intra-cluster policy
synchronization and an inter-cluster policy synchronization. For example, the
25
selection of the intra-cluster policy synchronization and the inter-cluster policy
synchronization is performed on the basis of the received request. For example, the
user and network operator may be able to provide a selection of the type of policy
synchronization. Based on the selection of one of the inter-cluster policy
5 synchronization and the intra-cluster policy synchronization, the processing unit
(208) is further configured to synchronize the set of policies to one of the first target
PCF node and the second target PCF node.
[0081] Upon selecting the intra-cluster policy synchronization, the
processing unit (208) is further configured to retrieve, from the database (210),
10 details of a first target PCF node associated with the first PCF cluster.
[0082] Upon selecting the inter-cluster policy synchronization, the
processing unit (208) is further configured to retrieve, from the database (210),
details of a second target PCF node associated with the second PCF cluster.
[0083] In an embodiment, to synchronize the set of policies, the processing
15 unit (208) is further configured to replace existing policies associated with the first
target PCF node and the second target PCF node with the set of configured policies
of the source PCF node.
[0084] In an embodiment, the processing unit (208) is further configured to
perform a remote procedure call (RPC) to synchronize the set of policies to the first
20 target PCF node or the second target PCF node. RPC allows the system to invoke
procedures or functions on a remote server as if they were local calls. The system
initiates an RPC by making a procedure call, which is transmitted over the network
to the server. Upon receipt, the server receives the request, executes the procedure,
and returns the result to the client. The client then receives the response and resumes
25 execution based on the outcome of the remote procedure call. RPC abstracts away
the complexities of network communication, enabling transparent communication
between distributed processes. The RPC is a communication protocol used in
networked environments that allows the application to cause a procedure
(subroutine) to execute in another address space (e.g., another physical machine).
26
For example, the RPC may be used to synchronize/replicate a state and data
between two servers or between the nodes/PCRFs/PCFs.
[0085] In an aspect, the processing unit (208) may be implemented as one
or more microprocessors, microcomputers, microcontrollers, edge or fog
5 microcontrollers, digital signal processors, central processing units, logic
circuitries, and/or any devices that process data based on operational instructions.
Among other capabilities, the processing unit (208) may be configured to fetch and
execute computer-readable instructions stored in a memory (204) of the policy
synchronization system (108). In an embodiment, the policy synchronization
10 system (108) may include an interface(s) (206). The interface(s) (206) may include
a variety of interfaces, for example, interfaces for data input and output devices,
referred to as I/O devices, storage devices, and the like. The interface(s) (206) may
facilitate communication of the policy synchronization system (108). The
interface(s) (206) may also provide a communication pathway for one or more
15 components of the policy synchronization system (108).
[0086] The processing unit/engine(s) (208) may be implemented as a
combination of hardware and programming (for example, programmable
instructions) to implement one or more functionalities of the processing unit (208).
In the examples described herein, such combinations of hardware and programming
20 may be implemented in several different ways. For example, the programming for
the processing unit (208) may be processor-executable instructions stored on a nontransitory machine-readable storage medium and the hardware for the processing
unit (208) may comprise a processing resource (for example, one or more
processors), to execute such instructions. In the present examples, the machine25 readable storage medium may store instructions that, when executed by the
processing resource, implement the processing unit (208). In such examples, the
policy synchronization system (108) 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
27
accessible to the system (108) and the processing resource. In other examples, the
processing unit (208) may be implemented by an electronic circuitry.
[0087] In an embodiment, the database (210) may comprise data that may
be either stored or generated as a result of functionalities implemented by any of
5 the components of the processing unit (208) or the policy synchronization system
(108).
[0088] In an embodiment, the system (108) may include a display unit (216)
for displaying updated/replicated policies of the one or more target PCF node.
[0089] In an overall aspect, the present system is configured to invoke the
10 Policy Sync procedure when the following actions or prior requirements are met:
 Policy Configuration: Initially, the desired policies or rules are defined and
configured in a single instance or cluster. The policies are configured using
CLI or SMP GUI.
 Verification: The configured policies are verified and tested in the source
15 instance or cluster to ensure their correctness and effectiveness. This step
ensures that the policies are functional and aligned with the intended
objectives.
[0090] In an aspect, the present system is configured to employ the
following steps:
20  Propagation: Once the policies are successfully verified, they are
propagated or pushed to the other instances (PCF nodes) or clusters within
the network. This can be done through various means such as CLI
commands, GUIs. The propagated policies replace the existing ones in the
target instances or clusters.
25  Inter-cluster sync policy for PCF: Inter-cluster synchronization focuses on
achieving synchronization between different PCF clusters deployed within
28
the network. Upon selecting inter-cluster policy synchronization, the
processing unit (208) retrieves specific details, from the database (210),
regarding a second target PCF node associated with the second PCF cluster.
In an aspect, the specific details may include a second target PCF node
5 identifier or a set of installed policies of the second target PCF node. The
second target PCF node identifier is a unique identifier that distinguishes
the second target PCF node within the second PCF cluster. The set of
installed policies is a list or configuration details of policies currently
installed and operational on the second target PCF node within the second
10 PCF cluster. This is necessary to ensure consistent policy enforcement and
coordination across clusters. The inter-cluster sync policy is achieved by
following steps:
 Retrieve the cluster details, including information about each
cluster in the network (super-core) from the database.
15  For each cluster: Retrieve the node details, including
information about each node within the cluster.
 For each node: Send a policy sync request to the node.
Retrieve the configured policy from the database and
populate it in the memory of the respective policy type.
20  Perform RPC to write the rule/policy data to the nodes of
same cluster.
 Display policy in CLI/SMP GUI.
 After processing all nodes within a cluster, check if there are
any remaining clusters.
25  If there are more clusters, repeat the process for the next
cluster.
29
 Once all clusters have been processed, the inter-cluster sync
policy is completed.
 Intra-cluster sync policy for PCF: Intra-cluster synchronization focuses on
achieving synchronization within a specific PCF cluster. This is important
5 to ensure consistent policy enforcement among the PCF instances within
the same cluster. Intra-cluster sync policy is performed by following steps:
 Retrieve the cluster details, including information about the
target cluster.
 For a target cluster: Retrieve the node details, including
10 information about each node within the cluster.
 For each node: Retrieve configured rule/policy from
database and populate it in memory of respective policytype.
 Perform RPC to write the rule/policy data to the nodes of the
15 same cluster.
 Display policy in CLI/ SMP GUI.
 After processing all nodes within the target cluster, the intracluster sync policy is complete.
[0091] Although FIG. 2 shows an exemplary block diagram (200) of the
20 policy synchronization system (108), in other embodiments, the policy
synchronization system (108) may include fewer components, different
components, differently arranged components, or additional functional components
than depicted in FIG. 2. Additionally, or alternatively, one or more components of
the policy synchronization system (108) may perform functions described as being
25 performed by one or more other components of the policy synchronization system
(108).
30
[0092] FIG. 3 illustrates an exemplary flow diagram (300) followed by the
policy synchronization system (108), in accordance with an embodiment of the
present disclosure.
[0093] Referring to FIG. 3, a policy synchronization request is initiated
5 from the GUI but formatted in the style of the CLI, indicating a flexible approach
to initiating requests. This request is sent to a Policy Synchronization Module
(PSM) at step (302). Upon receiving the synchronization request, the PSM defines
and configures the desired policies or rules in a single instance (a single Policy
Control Function, PCF) or a PCF cluster. These configured policies then undergo a
10 verification process to ensure they function correctly and align with the intended
objectives.
[0094] Once successfully verified, the policies are propagated or pushed to
other instances or clusters within the network. The propagated policies replace the
existing ones in the target instance or cluster and are then stored in the database at
15 step (304). This process ensures consistency and alignment of policies across the
network, enabling effective management and enforcement of network policies.
[0095] FIG. 4 illustrates an exemplary flow chart of a method (400) for
synchronizing policies across the plurality of PCF clusters, in accordance with an
embodiment of the present disclosure.
20 [0096] At step (402), the method (400) was initiated. At step (402), the
policy synchronization method includes defining and configuring the desired
policies or rules in the single instance (source node) or cluster using CLI or SMP
GUI. The method may include verifying and testing the configured policies in the
source instance or cluster to ensure their correctness and effectiveness. Once the
25 policies are successfully verified, the policies may be propagated or pushed to the
other instances or clusters within the super-core. The propagated policies may
replace the existing ones in the target instances or clusters.
31
[0097] At step (404), a user may be able to select a type of sync policy
synchronization. The policy synchronization may be of two types, namely an intercluster policy synchronization and an intra-cluster policy synchronization.
[0098] After selecting the inter-cluster policy synchronization, at step (406),
5 the system is configured to retrieve cluster details from the database. Inter-cluster
policy synchronization is configured to focus on achieving synchronization
between different clusters deployed within a network. The inter-cluster policy
synchronization may be necessary to ensure consistent policy enforcement and
coordination across the clusters. At step (408), the system is configured to retrieve
10 details of each node for each cluster. The inter-cluster policy synchronization may
be achieved by retrieving cluster details including information about each cluster in
the super-core from the database (210). For each cluster, the node details include
information about each node within the cluster that may be retrieved.
[0099] After selecting the intra-cluster policy synchronization, at step (410),
15 the system is configured to retrieve a policy from the database for the active node
(in an example, the active mode is the source node) of the first PCF cluster. The
system is configured to replicate the retrieved policy to other nodes within the
cluster. Intra-cluster policy synchronization may focus on achieving
synchronization within a specific cluster, to ensure consistent policy enforcement
20 among the instances within the same cluster.
[00100] The intra-cluster policy synchronization may be achieved by
retrieving the cluster details including information about the target cluster. For the
target cluster, the node details including information about each node within the
cluster may be retrieved.
25 [00101] For each node, the configured rule/policy may be retrieved from the
database and populated in the local cache of the respective policy type. RPC may
be performed to write the rule/policy data to the nodes of the same cluster, and the
policy may be displayed in the GUI (at step 414). After processing all nodes within
the target cluster, the intra-cluster policy synchronization may be completed.
32
[00102] In an overall aspect, for each node, a policy synchronization request
may be sent, the configured policy may be retrieved from the database (210) and
populated in a local cache of respective policy-type, Remote Procedure Call (RPC)
may be performed to write the rule/policy data to the nodes of same cluster, and the
5 policy may be displayed in the GUI. For example, the policy synchronization
request may pertain to a set of policies, and the set of policies may be defined and/
or configured in a source PCF node associated with a PCF cluster of the wireless
network. Further, the configured set of policies in the source PCF node may be
verified. Upon successful verification of the configured set of policies and based on
10 the policy synchronization request, details of one or more target PCF nodes in the
wireless network may be retrieved from a database (210). In an example, the one
or more target PCF nodes may be associated with the PCF cluster, which comprises
the source PCF node. In another example, the one or more target PCF nodes may
be associated with a PCF cluster which is different from the PCF cluster which
15 comprises the source PCF node. Furthermore, based on the retrieved details of the
one or more target PCF nodes, the verified set of policies, configured in the source
PCF node, may be synchronized to the one or more target PCF nodes.
[00103] After processing all nodes within the cluster, the method may check
if there are any remaining clusters. If there are more clusters, the node details
20 including information about each node within the cluster may be retrieved and the
process may be repeated for each node. Once all clusters have been processed, the
inter-cluster policy synchronization may be complete.
[00104] FIG. 5 illustrates an exemplary computer system (500) in which or
with which embodiments of the present disclosure may be implemented.
25 [00105] As shown in FIG. 5, the computer system (500) may include an
external storage device (510), a bus (520), a main memory (530), a read only
memory (540), a mass storage device (550), a communication port (560), and a
processor (570). A person skilled in the art will appreciate that the computer system
(500) may include more than one processor (570) and communication ports (560).
33
Processor (570) may include various modules associated with embodiments of the
present disclosure.
[00106] In an embodiment, the communication port (560) may be any of an
RS-232 port for use with a modem-based dialup connection, a 10/100 Ethernet port,
5 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 (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 (500) connects.
[00107] In an embodiment, the memory (530) may be Random Access
10 Memory (RAM), or any other dynamic storage device commonly known in the art.
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).
15 [00108] In an embodiment, the mass storage (550) may be any current or
future mass storage solution, which may be used to store information and/or
instructions. Exemplary mass storage solutions include, but are not limited to,
Parallel Advanced Technology Attachment (PATA) or Serial Advanced
Technology Attachment (SATA) hard disk drives or solid-state drives (internal or
20 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 (e.g., SATA arrays).
[00109] In an embodiment, the bus (520) communicatively couples the
processor(s) (570) with the other memory, storage and communication blocks. The
25 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 (500).
34
[00110] 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 (500). Other
operator and administrative interfaces may be provided through network
5 connections connected through the communication port (560). The components
described above are meant only to exemplify various possibilities. In no way should
the aforementioned exemplary computer system (500) limit the scope of the present
disclosure.
[00111] FIG. 6 illustrates an exemplary flow diagram (600) of a policy
10 synchronization method for managing policies across the plurality of PCF clusters
in the network, in accordance with an embodiment of the present disclosure. At step
602, a set of policies, associated with a first PCF cluster of the network (106), is
configured by the processing unit (208) in the source PCF node. The first PCF
cluster may comprise a set of PCF nodes from the plurality of PCF nodes. In an
15 embodiment, the set of policies includes various policy rules that are essential for
managing and enforcing policies related to quality of service (QoS), charging, and
access control.
[00112] At step 604, a policy synchronization request pertaining to the set of
policies may be received by the processing unit (208). In an example, the policy
20 synchronization request includes a plurality of information, such as details of the
source node from where policy changes originate and details of the target nodes or
clusters that need updates. Further, the policy synchronization request may include
timestamps or details of tracking the versions of the policies, suggesting when
changes were made and ensuring updates are applied in sequence. For example, the
25 policy synchronization request may include one or more modified policies,
including parameters and conditions, to clarify the scope of synchronization.
[00113] At step 606, based on the policy synchronization request, details of
one or more target PCF nodes in the network (106) are retrieved by the processing
35
unit (208) and from the database (210). The one or more target PCF nodes may be
associated with one of the first PCF cluster and a second PCF cluster.
[00114] At step 608, based on the retrieved details of the one or more target
PCF nodes, the set of policies synchronized by the processing unit (208) with the
5 one or more target PCF nodes.
[00115] In an embodiment, the method includes a step of, based on the policy
synchronization request, selecting, by the processing engine, a type of policy
synchronization, wherein the type of policy synchronization comprise an intracluster policy synchronization and an inter-cluster policy synchronization. For
10 example, the selection of the intra-cluster policy synchronization and the intercluster policy synchronization is performed on the basis of the received request. For
example, the user and network operator may be able to provide a selection of the
type of policy synchronization.
[00116] In an embodiment, upon selecting the intra-cluster policy
15 synchronization, the method comprises retrieving, by the processing engine and
from the database, details of a first target PCF node associated with the first PCF
cluster.
[00117] In an embodiment, upon selecting the inter-cluster policy
synchronization, the method includes a step of retrieving, by the processing engine
20 and from the database, details of a second target PCF node associated with the
second PCF cluster. Upon selecting inter-cluster policy synchronization, the
processing unit (208) retrieves specific details, from the database (210), regarding
a second target PCF node associated with the second PCF cluster. In an aspect, the
specific details may include a second target PCF node identifier or a set of installed
25 policies of the second target PCF node. The second target PCF node identifier is a
unique identifier that distinguishes the second target PCF node within the second
PCF cluster. The set of installed policies is a list or configuration details of policies
currently installed and operational on the second target PCF node within the second
PCF cluster.
36
[00118] In an embodiment, based on the selection of one of the inter-cluster
policy synchronization and the intra-cluster policy synchronization, the method
comprises synchronizing, by the processing engine, the set of policies to one of the
first target PCF node and the second target PCF node.
5 [00119] In an embodiment, upon configuration, the method includes a step
of verifying, by the processing engine, the set of policies. In an aspect, the
processing unit (208) checks if the configured set of policies aligns with the
specified standards or requirements by mapping the configured set of policies with
the set of defined parameters. For example, for each policy, the processing unit
10 checks if it meets the defined parameters (may be defined by network operators).
This evaluation involves comparing the content of each policy against the criteria
specified in the parameters.
[00120] In an embodiment, the inter-cluster policy synchronization
comprises performing synchronization in PCF nodes of a plurality of PCF clusters
15 deployed within the network, and wherein the intra-cluster policy synchronization
comprises performing synchronization in PCF nodes of same PCF cluster. The
inter-cluster policy synchronization involves synchronizing policies across the PCF
nodes located in multiple PCF clusters deployed within the network, ensuring the
process ensures that policies are uniformly applied and managed across different
20 clusters, facilitating consistent network-wide policy enforcement and operational
alignment. The intra-cluster policy synchronization focuses on synchronizing
policies within PCF nodes that belong to the same PCF cluster. The intra-cluster
policy synchronization ensures policies are applied consistently and efficiently to
meet specific cluster-level operational requirements and objectives.
25 [00121] In an embodiment, the step of synchronizing the set of policies
comprises replacing existing policies associated with each of the first target PCF
node and the second target PCF node with the set of configured policies.
[00122] In an embodiment, the method includes a step of performing a
Remote Procedure Call (RPC) for synchronizing the set of policies to the first target
37
PCF node or the second target PCF node. RPC allows the system to invoke
procedures or functions on a remote server as if they were local calls. The system
initiates an RPC by making a procedure call, which is transmitted over the network
to the server. Upon receipt, the server receives the request, executes the procedure,
5 and returns the result to the client. The client then receives the response and resumes
execution based on the outcome of the remote procedure call. RPC abstracts away
the complexities of network communication, enabling transparent communication
between distributed processes.
[00123] The present disclosure provides technical advancement related to
10 synchronizing the configured policies. This advancement addresses existing
solutions' limitations by streamlining policy management across multiple PCF
clusters. The disclosure involves configuring and synchronizing the policies across
the clusters, which offers significant improvements in significantly reducing the
time and effort required for policy deployment, updates, and maintenance. By
15 automatically synchronizing configured policies, the disclosed invention ensures
consistent policy enforcement and coordination across clusters.
[00124] While the foregoing describes various embodiments of the present
disclosure, other and further embodiments of the present disclosure may be devised
without departing from the basic scope thereof. The scope of the present disclosure
20 is determined by the claims that follow. The present disclosure 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 present disclosure when
combined with information and knowledge available to the person having ordinary
skill in the art.
25 ADVANTAGES OF THE PRESENT DISCLOSURE
[00125] The present disclosure provides a system and a method to configure
one or more policies in one cluster.
38
[00126] The present disclosure synchronizes the configuration of one or
more policies so that the synchronized configurations are uniformly applied and
enforced across multiple entities.
[00127] The present disclosure significantly reduces the time and effort
5 required to implement policy changes across multiple clusters.
[00128] The present disclosure pushes one or more policies from one cluster
to another and ensures consistency in policy configuration throughout a super-core,
thereby reducing the risk of errors or inconsistencies that may occur when
configuring one or more policies individually in each cluster.
10 [00129] The present disclosure performs any updates, modifications, or
troubleshooting in one place, making it easier to maintain and manage policies
across the super-core.
[00130] The present disclosure easily scales the policy management process
without adding excessive overhead.
15
39
We Claim:
1. A method (600) for managing policies across a plurality of Policy Control
Function (PCF) clusters in a network (106), wherein each PCF cluster comprises a
source PCF node and one or more target PCF nodes, the method (600) comprising:
5 configuring (602), by a processing unit (208), a set of policies of the
source PCF node associated with a first PCF cluster of the network (106);
receiving (604), a receiving unit, a policy synchronization request;
based on the policy synchronization request, retrieving (606), by the
processing unit (208) and from a database (210), details of the policies
10 associated with the one or more target PCF nodes in the network (106); and
based on the retrieved details of the one or more target PCF nodes,
synchronizing (608), by the processing unit (208), the set of policies
associated with the one or more target PCF nodes in accordance with the set
of configured policies of the source PCF node.
15
2. The method (600) as claimed in claim 1, further comprising:
based on the policy synchronization request, selecting, by the processing unit
(208), a type of policy synchronization, wherein the type of policy synchronization
comprises an intra-cluster policy synchronization and an inter-cluster policy
20 synchronization.
3. The method (600) as claimed in claim 2, wherein the one or more target
PCF nodes are associated with one of the first PCF cluster and a second PCF cluster.
25 4. The method (600) as claimed in claim 3, wherein, upon selecting the intracluster policy synchronization, the method (600) further comprising:
retrieving, by the processing unit (208) and from the database (210),
details of a first target PCF node associated with the first PCF cluster.
40
5. The method (600) as claimed in claim 3, wherein, upon selecting the intercluster policy synchronization, the method further comprising:
retrieving, by the processing unit (208) and from the database (210),
details of a second target PCF node associated with the second PCF cluster.
5
6. The method (600) as claimed in claim 4, wherein, based on the selection of
one of the inter-cluster policy synchronization and the intra-cluster policy
synchronization, the method further comprising synchronizing, by the processing
unit (208), the set of configured policies to one of the first target PCF node and the
10 second target PCF node.
7. The method (600) as claimed in claim 5, further comprising verifying, by
the processing unit (208), the set of policies according to a set of defined
parameters, wherein the set of defined parameters includes data rate limits, priority
15 levels, and charging rules.
8. The method (600) as claimed in claim 2, wherein the inter-cluster policy
synchronization includes performing synchronization in PCF nodes of a plurality
of PCF clusters deployed within the network (106), and wherein the intra-cluster
20 policy synchronization includes performing synchronization in PCF nodes of a
same PCF cluster.
9. The method (600) as claimed in claim 4, wherein a step of synchronizing
the set of policies comprising replacing existing policies associated with the first
25 target PCF node and the second target PCF node with the set of configured policies
of the source PCF node.
10. The method (600) as claimed in claim 4, wherein the method further
comprising performing a Remote Procedure Call (RPC) for synchronizing the set
30 of policies to the first target PCF node or the second target PCF node.
41
11. A system (108) for managing policies across a plurality of Policy Control
Function (PCF) clusters in a network (106), wherein each PCF cluster comprises a
source PCF node and one or more target PCF nodes, the system (108) comprising:
a receiving unit (202) configured to receive a policy synchronization
5 request; and
a memory (204) coupled to a processing unit (208), wherein the
memory (204) includes computer-implemented instructions to configure the
processing unit (208) to:
configure a set of policies of the source PCF node associated
10 with a first PCF cluster of the network (106);
based on the policy synchronization request, retrieve, from a
database (210), details of the policies associated with the one or more
target PCF nodes in the network (106); and
based on the retrieved details of the policies associated with
15 each target PCF node, synchronize the set of policies associated with
the one or more target PCF nodes in accordance with the set of
configured policies of the source PCF node.
12. The system (108) as claimed in claim 11, wherein the processing unit (208)
20 is further configured to:
based on the policy synchronization request, select a type of policy
synchronization, wherein the type of policy synchronization comprises an
intra-cluster policy synchronization and an inter-cluster policy
synchronization.
25
13. The system (108) as claimed in claim 11, wherein the one or more target
PCF nodes are associated with one of the first PCF cluster and a second PCF cluster.
14. The system (108) as claimed in claim 12, wherein, upon selecting the intra30 cluster policy synchronization, the processing unit (208) is further configured to:
42
retrieve, from the database (210), details of a first target PCF node
associated with the first PCF cluster.
15. The system (108) as claimed in claim 12, wherein, upon selecting the inter5 cluster policy synchronization, the processing unit (208) is further configured to:
retrieve, from the database (210), details of a second target PCF
node associated with the second PCF cluster.
16. The system (108) as claimed in claim 14, wherein, based on the selection of
10 one of the inter-cluster policy synchronization and the intra-cluster policy
synchronization, the processing unit (208) is further configured to:
synchronize the set of policies to one of the first target PCF node
and the second target PCF node.
15 17. The system (108) as claimed in claim 11, wherein the processing unit (208)
is further configured to:
upon configuration, verify the set of policies according to a set of
defined parameters, wherein the set of defined parameters includes data rate
limits, priority levels, and charging rules.
20
18. The system (108) as claimed in claim 14, wherein, to synchronize the set of
policies, the processing unit (208) is further configured to replace existing policies
associated with the first target PCF node and the second target PCF node with the
set of configured policies of the source PCF node.
25
19. The system (108) as claimed in claim 14, wherein the processing unit (208)
is further configured to perform a Remote Procedure Call (RPC) to synchronize the
set of policies to the first target PCF node or the second target PCF node.
30 20. A user equipment (104) communicatively coupled with a system (108), the
coupling comprises steps of:
43
receiving a connection request from the system (108);
sending an acknowledgment of the connection request to the system (108);
transmitting a plurality of signals in response to the connection request,
wherein the system (108) is configured to manage policies across a plurality of
5 Policy Control Function (PCF) clusters in a network (106), as claimed in claim 11.