WO2025017585A1 - System and method for monitoring policy and charging control rules - Google Patents

Abstract

The present disclosure discloses a system and method (300) for monitoring of one or more policy and charging control (PCC) rules in a network. The method initializes (302), by a processing unit (112), a policy hit counter of each rule of a set of predefined PCC policy rules with a counting value. The method (300) allows determining (304), by the processing unit (112), whether the at least one executed policy rule exists in a memory (110). The method (300) allows incrementing (306), by the processing unit (112), a counting value of the policy hit counter against the policy rule by 1 if the at least one executed policy rule exists and generates an updated counting value. The method (300) allows transmitting the updated set of PCC policy rules and the counting value of the policy hit counter to a service management platform (SMP) to assess the performance of the PCC policy rules.

Description

SYSTEM AND METHOD FOR MONITORING POLICY AND CHARGING CONTROL RULES

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 dress protection, belonging to Jio Platforms Limited (JPL) 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.

TECHNICAL FIELD

[002] The present disclosure relates to wireless cellular communications, and specifically to a system and method to identify a number of times a particular policy is hit within an application to identify underutilized or overutilized policies.

DEFINITIONS

[003] The term PCF as used herein, refers to a Policy Control Function. The PCF is a key component of the 5G architecture and plays a crucial role in enforcing policy decisions related to Quality of Service (QoS), traffic management, and network resource allocation.

[004] The term PCRF as used herein, refers to a Policy and Charging Rules Function. The PCRF plays a central role in controlling and enforcing policies related to network resource allocation, quality of service (QoS), and charging for subscriber sessions.

[005] The term PGW as used herein, refers to a Packet Data Network Gateway. The PGW serves as a gateway that connects the mobile network to external packet data networks, such as the Internet or private corporate networks. [006] The term RPC as used herein, refers to Remote Procedure Call. The RPC is a protocol that allows an application to execute a procedure (subroutine) on a different address space (commonly on another physical machine) as if it were a local procedure call, without the programmer explicitly coding for this interaction.

[007] The term OCS as used herein, refers to an Online Charging System. The OCS allows real-time charging, rating, and billing of various services in a 5G network.

BACKGROUND

[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, and not as admissions of prior art.

[009] Typically, policy rules in a Policy and Charging Rules Function (PCRF)/Policy Control Function (PCF) application are used to control and manage behaviour of network resources and services based on specific conditions and criteria. However, there is no mechanism available to identify and keep a track of a number of times a particular policy has been used within the application thereby leading to overutilization/underutilization of the policies.

[0010] There is therefore a need in the art to provide an improved mechanism to analyse policy hit counts in real-time or near-real-time to make informed decisions for policy optimization.

OBJECTS OF THE PRESENT DISCLOSURE

[0011] It is an object of the present disclosure to identify a number of times a particular policy is hit within an application to identify underutilized or over utilized policies. [0012] It is an object of the present disclosure to identify and analyse policy hit counts in real-time or near-real-time to make informed decisions regarding policy optimization.

[0013] It is an object of the present disclosure to implement a policy execution tracking to track a count of execution of policy rules to determine when and how these are applied within the application.

[0014] It is an object of the present disclosure to monitor policy hit counts and compare expected counts with actual counts to verify and ensure that policies are being correctly enforced and applied as intended.

[0015] It is an object of the present disclosure to use policy hit counters to identify underlying causes of issues within the application and to determine an occurrence of a significant difference between expected counts and actual counts, to identify a problem or an issue that needs attention or investigation.

[0016] It is an object of the present disclosure to track the policy hit count, to assess performance and effectiveness of the policies, and determine which policies are frequently triggered or executed.

SUMMARY

[0017] The present disclosure discloses a system for monitoring one or more policy and charging control (PCC) rules in a network. The system includes a memory configured to store a set of predefined PCC policy rules and a processing unit. The processing unit is configured to initialize a policy hit counter of each rule of the set of predefined PCC policy rules with a counting value. The processing unit is configured to communicate with a cluster of policy and charging rules functions (PCRFs)/ policy control functions (PCFs) to monitor an execution of at least one policy rule by each PCRF/PCF. The processing unit is configured to communicate with the memory to determine whether the at least one executed policy rule exists in the memory. If the executed at least one policy rule exists in the memory, the processing unit is configured to increment a counting value of the policy hit counter against the policy rule by 1 and generate an updated counting value. If the executed at least one policy rule does not exist in the memory, the processing unit is configured to update the set of predefined PCC policy rules with the executed at least one policy rule and set a counting value of the policy hit counter against the executed policy rule to 1. The processing unit is configured to transmit the updated set of PCC policy rules and the counting value of the policy hit counter to a service management platform (SMP).

[0018] In an embodiment, the processing unit is configured to generate at least one policy hit counter map based upon the generated updated counting value corresponding to each policy rule.

[0019] In an embodiment, the system further includes a display unit configured to display the at least one generated policy hit counter map.

[0020] In an embodiment, the system is configured to perform data replication to update the policy hit counter map corresponding to each policy rule executed on each PCRF/PCF of the cluster of PCRFs/PCFs.

[0021] In an embodiment, the data replication is performed using remote procedure call (RPC). The RPC is a communication protocol used in networked environments that allows an application to cause a procedure (subroutine) to execute in another address space (e.g., another physical machine). For example, the RPC may be used to synchronize the state and data between two servers or between the nodes/PCRFs/PCFs.

[0022] In an embodiment, the system further includes an interfacing unit configured to receive a request from an operator for setting/resetting the counter value corresponding to a specific policy rule or the updated set of PCC policy rules.

[0023] In an embodiment, the system is configured to receive the request by employing a command-line interface (CLI) or a graphical user interface (GUI). [0024] In an embodiment, the set of predefined PCC policy rules may include a rule name, a service identifier, one or more service data flow (SDF) filters, precedence, gate status (open/closed), Quality of Service (QoS) parameters, charging key (rating group), and various charging parameters.

[0025] The present disclosure discloses a method for monitoring one or more policy and charging control (PCC) rules in a network. The method includes storing, in a memory, a set of predefined PCC policy rules. The method includes initializing, by a processing unit, a policy hit counter of each rule of the set of predefined PCC policy rules with a counting value. The method includes monitoring, by the processing unit, an execution of at least one policy rule by each policy and charging rules function (PCRF)/ policy control function (PCF). The method includes determining, by the processing unit, whether the at least one executed policy rule exists in the memory. The method includes incrementing, by the processing unit, a counting value of the policy hit counter against the policy rule by 1 if the at least one executed policy rule exists in the memory and generating an updated counting value. The method includes updating, by the processing unit, the set of predefined PCC policy rules with the at least one executed policy rule and setting a counting value of the policy hit counter against the executed policy rule to 1 if the executed policy rule does not exist in the memory. The method includes transmitting, by the processing unit, the updated set of PCC policy rules and the counting value of the policy hit counter to a service management platform (SMP).

[0026] In an embodiment, the method allows the processing unit configured to generate at least one policy hit counter map based upon the generated updated counting value corresponding to each policy rule.

[0027] In an embodiment, the method allows a display unit configured to display the at least one generated policy hit counter map.

[0028] In an embodiment, the method is configured to perform data replication to update the policy hit counter map corresponding to each policy rule executed on each PCRF/PCF of the cluster of PCRFs/PCFs. [0029] In an embodiment, the data replication is performed using a remote procedure call (RPC).

[0030] In an embodiment, the method allows an interfacing unit configured to receive a request from an operator for setting/resetting the counter value corresponding to a specific policy rule or the updated set of PCC policy rules.

[0031] In an embodiment, the method allows the interfacing unit configured to receive the request by employing a command-line interface (CLI) or a graphical user interface (GUI).

[0032] The present disclosure discloses a user equipment (UE) communicatively coupled with a network. The coupling comprises steps of receiving, by the network, a connection request from the UE. The coupling comprises steps of sending, by the network, an acknowledgment of the connection request to the UE. The coupling comprises steps of transmitting a plurality of signals in response to the connection request, wherein monitoring of the one or more policy and charging control (PCC) rules in the network is performed by a method for monitoring one or more policy and charging control (PCC) rules in a network. The method includes storing, in a memory, a set of predefined PCC policy rules. The method includes initializing, by a processing unit, a policy hit counter of each rule of the set of predefined PCC policy rules with a counting value. The method includes monitoring, by the processing unit, an execution of at least one policy rule by each policy and charging rules function (PCRF)/ policy control function (PCF). The method includes determining, by the processing unit, whether the at least one executed policy rule exists in the memory. The method includes incrementing, by the processing unit, a counting value of the policy hit counter against the policy rule by 1 if the at least one executed policy rule exists in the memory and generating an updated counting value. The method includes updating, by the processing unit, the set of predefined PCC policy rules with the at least one executed policy rule and setting a counting value of the policy hit counter against the executed policy rule to 1 if the executed policy rule does not exist in the memory. The method includes transmitting, by the processing unit, the updated set of PCC policy rules and the counting value of the policy hit counter to a service management platform (SMP).

[0033] The present disclosure discloses a network function for monitoring one or more policy and charging control (PCC) rules in a network. The network function includes a memory configured to store a set of predefined PCC policy rules and a processing unit. The processing unit is configured to initialize a policy hit counter of each rule of the set of predefined PCC policy rules with a counting value. The processing unit is configured to monitor an execution of at least one policy rule by the PCRF/PCF. The processing unit is configured to determine whether the at least one executed policy exists in the memory. If the executed at least one policy rule exists in the memory, the processing unit is configured to increment a counting value of the policy hit counter against the policy rule by 1. If the executed at least one policy rule does not exist in the memory, the processing unit is configured to update the set of predefined PCC policy rules with the executed at least one policy rule and set a counting value of the policy hit counter against the executed policy rule to 1. The processing unit is configured to transmit the updated set of PCC policy rules and the counting value of the policy hit counter to a service management platform (SMP).

[0034] The present disclosure discloses a computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to store a set of predefined PCC policy rules in a memory. The one or more processors are configured to initialize a policy hit counter of each rule of the set of predefined PCC policy rules with a counting value. The one or more processors are configured to monitor an execution of at least one policy rule by the PCRF/PCF. The one or more processors are configured to determine whether the at least one executed policy exists in the memory. If the executed at least one policy rule exists in the memory. The one or more processors are configured to increment a counting value of the policy hit counter against the policy rule by 1. If the executed at least one policy rule does not exist in the memory, the one or more processors are configured to update the set of predefined PCC policy rules with the executed at least one policy rule and set a counting value of the policy hit counter against the executed policy rule to 1. The one or more processors are configured to transmit the updated set of PCC policy rules and the counting value of the policy hit counter to a service management platform (SMP).

BRIEF DESCRIPTION OF THE DRAWINGS

[0035] 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.

[0036] The diagrams are for illustration only, which thus is not a limitation of the present disclosure, and wherein:

[0037] FIG. 1A illustrates an exemplary network architecture for implementing a system for monitoring one or more policy and charging control (PCC) rules in a network, in accordance with an embodiment of the present disclosure.

[0038] FIG. IB illustrates another exemplary network architecture of the system connected with a cluster of policy and charging rules functions (PCRFs)/ policy control functions (PCFs), in accordance with an embodiment of the present disclosure.

[0039] FIG. 2 illustrates an exemplary representation of a system architecture in an active, standby, and spare mode, in accordance with an embodiment of the present disclosure. [0040] FIG. 3 illustrates an exemplary flowchart illustrating various steps of a method for monitoring the one or more PCC rules in the network, in accordance with an embodiment of the present disclosure.

[0041] FIG. 4 illustrates an exemplary block diagram of a computer system in which or with which embodiments of the present disclosure may be implemented.

[0042] FIG. 5 illustrates an exemplary flow diagram of a method for monitoring the one or more PCC rules in the network, in accordance with an embodiment of the present disclosure.

[0043] The foregoing shall be more apparent from the following more detailed description of the disclosure.

LIST OF REFERENCE NUMERALS

100A, 100B - Network Architecture

102-1 - 102-N - Users

104-1 - 104-N - User Equipments (UEs)

106 - Network

108 - System

110 - Memory

112 - Processing Unit

114 - Display Unit

116 - Interfacing Unit

120-1, 120-2...120-N - Policy and Charging Rules Functions (PCRFs)/ Policy Control Functions (PCFs)

200 - System architecture

202, 204, 206 - Network Functions

208, 218 - Databases

210 - Packet Data Network Gateway (PGW)

212, 214, 216 - Policy Hit Count Management Module

222 - Command-Line Interface (CLI) 224 - Service Management Platform (SMP)

300 - Flow diagram

410 - External Storage Device

420 - Bus

430 - Main Memory

440 - Read Only Memory

450 - Mass Storage Device

460 - Communication Port

470 - Processor

500 - Flow diagram

DETAILED DESCRIPTION

[0044] 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 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 which like reference numerals refer to the same parts throughout the different drawings.

[0045] 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 disclosure as set forth.

[0046] 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.

[0047] 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 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.

[0048] 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 like the term “comprising” as an open transition word without precluding any additional or other elements.

[0049] 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 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.

[0050] The terminology used herein is to describe particular embodiments only and is not intended to be limiting the disclosure. As used herein, the singular 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 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 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 departing from the scope of the invention as defined herein. [0051] 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 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, 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 person skilled in the art for implementation of the features of the present disclosure.

[0052] 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 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 the system according to the present disclosure. More specifically, the processor is a hardware processor.

[0053] 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 technologies. In the field of wireless data communications, the dynamic 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.

[0054] Radio Access Technology (RAT) refers to the technology used by mobile devices/ user equipment (UE) to connect to a cellular network. It refers to the specific protocol and standards that govern the way devices communicate with base stations, which are responsible for providing the wireless connection. Further, each RAT has its own set of protocols and standards for communication, which define the frequency bands, modulation techniques, and other parameters used for transmitting and receiving data. Examples of RATs include GSM (Global System for Mobile Communications), CDMA (Code Division Multiple Access), UMTS (Universal Mobile Telecommunications System), LTE (Long-Term Evolution), and 5G. The choice of RAT depends on a variety of factors, including the network infrastructure, the available spectrum, and the mobile device's/device's capabilities. Mobile devices often support multiple RATs, allowing them to connect to different types of networks and provide optimal performance based on the available network resources.

[0055] 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 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.

[0056] In a 3rd Generation Partnership Project (3GPP) standard, Policy and Charging Rules Function (PCRF)/Policy Control Function (PCF) application is responsible for policy control and charging in a telecommunications network. It enforces policies that govern various aspects of network behaviour, service quality, and charging. These policies are defined in the form of rules/policy.

[0057] The policy rules in the PCRF/PCF are used to control and manage the behaviour of network resources, and services based on specific conditions and criteria. These policy rules enable operators to dynamically allocate and manage network resources, enforce quality of service (QoS) policies, and implement charging and billing mechanisms.

[0058] In an embodiment, a policy and charging control (PCC) rule represents a set of information that enables detection of a service data flow and provides parameters for policy control and/or charging control. The PCC rule may be predefined or dynamically provisioned at establishment and during the lifetime of an Internet Protocol Connectivity Access Network (IP-CAN) session. The latter is referred to as a dynamic PCC rule.

[0059] In an embodiment, the present disclosure enables the PCC rule with a policy hit counter metric. The policy hit counter metric enables the identification of execution of policies by keeping track of the number of times a particular policy has been hit within the application.

[0060] By analyzing policy hit counts in real-time or near-real-time, informed decisions regarding policy optimization may be made. The policy hit counts may be used to identify underutilized or overutilized policies and adjust to improve resource allocation, performance, or compliance. As may be appreciated, the policy hit count monitoring is a critical aspect of the policy management. In an embodiment, the policy optimization may include tailoring PCC rules based on user behaviour analytics derived from policy hit count. For example, if the policy hit count for a specific PCC rule belonging to bandwidth exceeds a user-defined value, it shows a user frequently engages in high-bandwidth activities at certain times. As a result, pre-emptively more bandwidths may be allocated during those periods. In another embodiment, the policy optimization may include adjusting user policies in real-time to manage network congestion. For example, if the policy hit count for a specific PCC rule belonging to high usage in a cell area exceeds the user-defined value, data speeds for users may be reduced to relieve congestion in the network.

[0061] In an embodiment, the disclosure facilitates to keep a track of the count of policies being executed and allows display of the policy hit counter in a command line interface (CLI)/a graphical user interface (GUI).

[0062] In an embodiment, the disclosed system and method enable the PCRF/PCF application to reset the policy hit counters. The ability to reset the policy hit counters offer flexibility and control and facilitates to address discrepancies when required. Resetting the policy hit counters may be beneficial in scenarios where a policy needs to be re-evaluated or when a clean state is required. Display and reset of the policy hit counters are available for all the interfaces involved in the application.

[0063] In an embodiment, the policy hit count monitoring, and associated features of display and reset may contribute to effective policy management, ensuring that policies are aligned with objectives, compliant with regulations and requirements, and deliver desired outcomes.

[0064] The various embodiments throughout the disclosure will be explained in more detail with reference to FIG. 1A - FIG. 5.

[0065] FIG. 1A illustrates an exemplary network architecture (100 A) for implementing a system (108) for monitoring one or more policy and charging control (PCC) rules in a network (106), in accordance with an embodiment of the present disclosure.

[0066] Referring to FIG. 1A, the exemplary network architecture (100 A) includes one or more computing devices or user equipments (104-1, 104-2...104- N) associated 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 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 A, however any number of the user equipments (104) may be included without departing from the scope of the ongoing description.

[0067] In an embodiment, the user equipment (104) includes smart devices operating in a smart environment, for example, an Internet of Things (loT) 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, 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. 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.

[0068] In an embodiment, the user equipment (104) includes, 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 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) includes, but is not limited to, any electrical, electronic, electromechanical, or an equipment, or a combination of one or more of the above 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 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.

[0069] Referring to FIG. 1A, the user equipment (104) communicates with the system (108) through the network (106). In an embodiment, the network (106) includes at least one of a Fifth Generation (5G) network, 6G network, or the like. The network (106) enables the user equipment (104) to communicate with other devices in the network architecture (100A) and/or with the system (108). The network (106) includes a wireless card or some other transceiver connection to facilitate this communication. In another embodiment, the network (106) is implemented as, or include any of a variety of different communication 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.

[0070] FIG. IB illustrates another exemplary network architecture (100B) of the system connected with a cluster of policy and charging rules functions (PCRFs)/ policy control functions (PCFs), in accordance with an embodiment of the present disclosure.

[0071] As illustrated in FIG. IB, the network architecture (100B) includes the cluster of PCRFs/ PCFs (120-1), (120-2)... (120-N). The PCFs/PCRFs enforce policies and rules related to network resource usage, quality of service, and charging. The PCFs/PCRFs ensure an efficient allocation of network resources, enforces quality of service policies, and facilitate dynamic charging based on service usage. In an aspect, the system (108) may be embedded within a network function (for example, a PCRF or a PCF).

[0072] As shown in FIG. IB, the system (108) includes a memory (110), a processing unit (112), a service management platform (SMP) (shown in FIG. 2), a display (114), and an interfacing unit (116).

[0073] The memory (110) is configured to store a set of predefined PCC policy rules. In an example, the set of predefined PCC policy rules may include a rule name, a service identifier, one or more service data flow (SDF) filters, precedence, gate status (open/closed), Quality of Service (QoS) parameters, charging key (rating group), and various charging parameters. The memory/repository (110) can be for example, a random access memory (RAM), a memory buffer, a hard drive, a database, an erasable programmable read only memory (EPROM), an electrically erasable programmable read only memory (EEPROM), a read only memory (ROM), a flash memory, a hard disk, a floppy disk, cloud storage, and/or so forth.

[0074] In an embodiment, the PCC policy rules are essential for managing and enforcing policies related to quality of service (QoS), charging, and access control. The PCC policy rules may be divided into the following categories, however, it should be appreciated that these PCC policy rules are illustrative and not exhaustive, and are not limited to any particular rule:

• 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, 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 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 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 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.

• 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 are optimized for certain applications. o Load Balancing Rules: distribute traffic evenly across the network to prevent congestion and ensure efficient use of network resources.

[0075] The processing unit (112) is configured to initialize each rule of the set of predefined PCC policy rules (also referred as policy rules) with a counting value. In an example, the counting value is set to ‘O’. The processing unit (112) is configured to communicate with the cluster of PCRFs/PCFs to detect an execution of at least one PCC policy rule by each PCRF/PCF. The processing unit (112) is configured to detect the execution of the at least PCC policy rule by continuously monitoring an event related to a session. For example, the event may include a session establishment request, session termination request, etc. If at least one policy rule is executed on any PCRF/PCF, the processing unit (112) is configured to communicate with the memory (110) to determine whether the at least one executed policy rule exists in the memory (110). For example, for determining the existence of the at least on executed policy rule, the processing unit (112) is configured to map/match the at least one executed PCC policy rule with the set of predefined PCC policy rules stored in the memory (110). If the executed at least one policy rule exists in the memory (110), the processing unit (112) is configured to increment a counting value against the policy rule by 1 and generate an updated counting value (for example, after one execution, the updated counting value become 2 for the executed rule policy). If the executed at least one policy rule does not exist in the memory (110), the processing unit (112) is configured to set a counting value against the executed policy rule to 1 after adding the policy rule name in the set of predefined PCC policy rules. In an example, the processing unit (112) is configured to generate at least one policy hit counter map based upon the generated updated counting value corresponding to each policy rule. The processing unit (112) disclosed herein may be general-purpose processors, Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), and/or the like. The processing unit (112) may be configured to retrieve data from and/or write data to the memory/repository (110).

[0076] The processing unit (112) is commutatively coupled to the SMP (224). The processing unit (112) is configured to transmit the updated set of PCC policy rules and the generated policy hit counter maps to the SMP. The SMP is configured to analyze the received updated set of PCC policy rules and the generated policy hit counter maps to identify the problems. For example, if there is a significant difference between the expected and actual counts, it could indicate a problem or an issue that needs attention or investigation for the one or more PCC policy rules. [0077] The display (114) is configured to receive the at least one generated policy hit counter map from the processing unit (112) and displays the received policy hit counter map. In an embodiment, the policy hit counter map represents a map data structure to store the count against each PCC policy rule name. For example, if a PCC policy rule is hit or executed for 5 times, its corresponding counter value will be set to ‘5’. Each time the PCC policy rule is hit or executed; its corresponding counter value will be incremented by ‘ 1’ . In an embodiment, the policy hit counter map captures the counter values of all the PCC policy rules that may help in assessing the performance and effectiveness of the PCC policy rules.

[0078] The interfacing unit (116) is configured to receive a request from an operator for setting/resetting the counter value corresponding to a specific policy rule or the updated set of PCC policy rules. For example, the interfacing unit (116) is configured to receive the request by employing a command-line interface (CLI) or a graphical user interface (GUI). In an embodiment, for example, the operator wants to update a specific PCC policy rule (e.g., maximum data usage policy rule) using the CLI or GUI, he/she can select the specific PCC policy rule belonging to the maximum data usage policy rule and reset its counter value to ‘O’.

[0079] In an aspect, the system (108) is configured to perform data replication to update the policy hit counter map corresponding to each policy rule executed on each PCRF/PCF of the cluster of PCRFs/PCFs. In an example, a plurality of nodes is connected to each PCRF/PCF. The system may be installed with the cluster of PCRFs/PCFs or with each PCRF/PCF. Therefore, to generate an accurate data each system installed with each PCRF/PCF is configured to update its data with each other. In an embodiment, the data replication is performed using remote procedure call (RPC). 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). For example, the RPC may be used to synchronize/replicate a state and data between two servers or between the nodes/PCRFs/PCFs. [0080] FIG. 2 illustrates an exemplary representation of a system architecture (200) in an active, standby, and spare mode, in accordance with an embodiment of the disclosure.

[0081] In an aspect, the system is configured to be employed in a plurality of network functions (202), (204), (206). As shown in FIG. 2, the plurality of network functions (202), (204), (206) is connected to various databases (208, 218). In an embodiment, the network functions may include functions related to bandwidth allocation, charging and billing, session management, congestion management, etc. The system is configured to receive a traffic from a packet data network gateway/online charging system (PGW/OCS) (210). The PGW serves as a gateway that connects the mobile network to external packet data networks, such as the Internet or private corporate networks and the OCS allows real-time charging, rating, and billing of various services in the network. The system is configured to detect an execution of the policy rule by examining the received traffic. In an aspect, the system may also be referred to the policy hit count management modules (212), (214), (216). Each policy hit count management module (212), (214), (216) communicates with the CLI (222) and the SMP (224).

[0082] The disclosed system and method enable policy execution tracking by maintaining a track of the count of execution of policy rules to determine when and how they are applied within the application. Further, a compliance verification is performed by monitoring policy hit counts. This ensures that policies are being correctly enforced and applied as intended. By comparing expected counts with actual counts, compliance with regulations and requirements may be verified. Also, the disclosed system and method perform a root cause analysis. This analysis uses policy hit counters along with application logs to help identify underlying causes of issues within the application. If there is a significant difference between the expected and actual counts, it may indicate a problem or an issue that needs attention or investigation. Furthermore, the disclosed system and method facilitate the tracking and evaluate the performance and effectiveness of the policies. This may help to determine which policies are frequently triggered or executed, providing insights into their impact on the application.

[0083] The disclosed system and method are dependent upon the PCRF/PCF architecture and business needs for enhancing the PCRF/PCF functions.

[0084] FIG. 3 illustrates an exemplary flowchart illustrating various steps of a method (300) for monitoring the one or more policy and charging control (PCC) rules in the network, in accordance with an embodiment of the disclosure.

[0085] At step (302), the system stores a set of predefined PCC policy rules in the memory (110). In an example, the set of predefined PCC policy rules may include a rule name, a service identifier, one or more service data flow (SDF) filters, precedence, gate status (open/closed), Quality of Service (QoS) parameters, charging key (rating group), and various charging parameters. At step (302), each rule of the set of predefined PCC policy rules is initialized with a counting value (e.g., ‘0’). Furthermore, the system detects an execution of at least one policy rule by each PCRF/ PCF.

[0086] At step (304), the system determines whether the at least one executed policy/PCC rule exists in the memory (110). In an embodiment, the memory (110) may store the policy/PCC rule name in a data structure, or a policy hit counter map.

[0087] If yes, at step (306), the system fetches the policy/PCC rule name from the memory (110) and increments a counting value against the policy/PCC rule by 1 and generates an updated counting value.

[0088] If no, at step (308), the system adds the executed policy/PCC rule name to the set of predefined PCC policy rules and sets a counting value against the executed policy/PCC rule to 1. [0089] At step (310), the system updates the policy hit counter map based upon the generated updated counting value corresponding to each policy/PCC rule. In an example, the system updates the maps periodically.

[0090] At step (312), the system displays the updated policy hit counter map on a command-line interface (CLI), a service management platform (SMP) or an element management system (EMS).

[0091] At step (314), the system receives a request from an operator for setting/resetting the counter value corresponding to a specific policy/PCC rule or the updated set of PCC policy rules through the command-line interface (CLI), the service management platform (SMP) or the element management system (EMS).

[0092] Step (316) includes termination of the method (300).

[0093] As illustrated, the following steps are followed for the tracking the execution of one or more PCC rules.

1. Initialization: During the application boot-up process, it initializes a map data structure to store a count against each PCC rule name. At this stage, the count for each predefined policy rule is set to ‘0’ in a map.

2. New Rule Creation: If a new rule is created, it updates the map by setting the count to ‘ 1’ for newly added PCC rule or policy. This ensures that the count is initialized for the new rule.

3. Rule Hit and Count Increment: When an existing rule is hit or executed, it increments the count against corresponding policy or rule name in the map. This allows for tracking a number of times a rule has been triggered or executed.

4. Replication and Map Update: Since the PCRF/PCF application operates in a cluster environment with multiple nodes, the data replication is performed using Replication and Clustering (RPC). When replication occurs, the module updates the policy hit counter map with the updated data received from the replication process. This ensures consistency and synchronization of the policy hit count across the cluster nodes.

[0094] The PCRF/PCF application supports displaying the count of policies for interfaces involved in the application and reset the count of executed policies. The functionality of displaying and resting the count executed policies may be accessed through the CLI or GUI from the SMP/Element Management System (EMS)). These functionalities provide visibility into the policy hit counts and offer control to reset the counts when necessary. In addition, the counters available on the GUI (EMS) may be dumped and used for root cause analysis if any issue arises. In an embodiment, the EMS provides interfaces to manage individual network elements within the network. In an embodiment, the SMP manages, orchestrates, and optimizes the services offered in the network (e.g., 5G/6G network).

[0095] FIG. 4 illustrates an exemplary computer system (400) in which or with which embodiments of the present disclosure may be implemented. As shown in FIG. 4, the computer system may include an external storage device (410), a bus (420), a main memory (430), a read-only memory (440), a mass storage device (450), communication port(s) (460), and a processor (470). A person skilled in the art will appreciate that the computer system may include more than one processor and communication ports. The processor (470) may include various modules associated with embodiments of the present disclosure. The communication port(s) (460) 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) (460) 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.

[0096] The main memory (430) may be random access memory (RAM), or any other dynamic storage device commonly known in the art. The read-only memory (440) 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 (470). The mass storage device (450) may be any current or future mass storage solution, which can be used to store information and/or instructions. Exemplary mass storage device (450) 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.

[0097] The bus (420) communicatively couples the processor (470) with the other memory, storage, and communication blocks. The bus (420) 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 (470) to the computer system.

[0098] Optionally, operator and administrative interfaces, e.g., a display, keyboard, joystick, and a cursor control device, may also be coupled to the bus (420) 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) (460). 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.

[0099] FIG. 5 illustrates an exemplary flow diagram of a method (500) for monitoring the one or more policy and charging control (PCC) rules in the network, in accordance with an embodiment of the present disclosure.

[00100] At step (502), the method (500) stores a set of predefined PCC policy rules in a memory (110). The set of predefined PCC policy rules may include a rule name, a service identifier, one or more service data flow (SDF) filters, precedence, gate status (open/closed), Quality of Service (QoS) parameters, charging key (rating group), and various charging parameters.

[00101] At step (504), the method (500) initializes, by a processing unit (112), a policy hit counter of each rule of the set of predefined PCC policy rules (also referred as policy rules) with a counting value (e.g. ‘0’).

[00102] At step (506), the method (500) monitors, by the processing unit (112), an execution of at least one policy rule by each policy and charging rules function (PCRF)/ policy control function (PCF). The processing unit (112) is configured to detect the execution of the at least PCC policy rule by continuously monitoring an event related to a session. For example, the event may include a session establishment request, session termination request, etc.

[00103] At step (508), the method (500) determines, by the processing unit (112), whether the at least one executed policy rule exists in the memory (110). For example, for determining the existence of the at least on executed policy rule, the processing unit (112) is configured to map/match the at least one executed PCC policy rule with the set of predefined PCC policy rules stored in the memory (110).

[00104] At step (510), the method (500) increments, by the processing unit (112), a counting value of the policy hit counter against the policy rule by 1 if the at least one executed policy rule exists in the memory (110) and generates an updated counting value.

[00105] At step (512), the method (500) updates, by the processing unit (112), the set of predefined PCC policy rules with the at least one executed policy rule and setting a counting value of the policy hit counter against the executed policy rule to 1 if the executed policy rule does not exist in the memory (110).

[00106] At step (514), the method (500) transmits, by the processing unit (112), the updated set of PCC policy rules and the counting value of the policy hit counter to a service management platform (SMP). In an embodiment, the policy hit counter may allow the SMP to identify the problems. If there is a significant difference between the expected and actual counts, it could indicate a problem or an issue that needs attention or investigation for the one or more PCC policy rules.

[00107] In an exemplary embodiment, the present disclosure discloses a user equipment (UE) communicatively coupled with a network. The coupling comprises steps of receiving, by the network, a connection request from the UE. The coupling comprises steps of sending, by the network, an acknowledgment of the connection request to the UE. The coupling comprises steps of transmitting a plurality of signals in response to the connection request, wherein monitoring of the one or more policy and charging control (PCC) rules in the network is performed by a method for monitoring one or more policy and charging control (PCC) rules in a network. The method includes storing, in a memory, a set of predefined PCC policy rules. The method includes initializing, by a processing unit, a policy hit counter of each rule of the set of predefined PCC policy rules with a counting value. The method includes monitoring, by the processing unit, an execution of at least one policy rule by each policy and charging rules function (PCRF)/ policy control function (PCF). The method includes determining, by the processing unit, whether the at least one executed policy rule exists in the memory. The method includes incrementing, by the processing unit, a counting value of the policy hit counter against the policy rule by 1 if the at least one executed policy rule exists in the memory and generating an updated counting value. The method includes updating, by the processing unit, the set of predefined PCC policy rules with the at least one executed policy rule and setting a counting value of the policy hit counter against the executed policy rule to 1 if the executed policy rule does not exist in the memory. The method includes transmitting, by the processing unit, the updated set of PCC policy rules and the counting value of the policy hit counter to a service management platform (SMP).

[00108] The present disclosure discloses a system for monitoring one or more policy and charging control (PCC) rules in a network. The system includes a memory (110) configured to store a set of predefined PCC policy rules and a processing unit (112). The processing unit (112) is configured to initialize a policy hit counter of each rule of the set of predefined PCC policy rules with a counting value. The processing unit (112) is configured to communicate with a cluster of policy and charging rules functions (PCRFs)/ policy control functions (PCFs) to monitor an execution of at least one policy rule by each PCRF/PCF. The processing unit (112) is configured to communicate with the memory (110) to determine whether the at least one executed policy rule exists in the memory (110). If the executed at least one policy rule exists in the memory (110), the processing unit (112) is configured to increment a counting value of the policy hit counter against the policy rule by 1 and generate an updated counting value. If the executed at least one policy rule does not exist in the memory (110), the processing unit (112) is configured to update the set of predefined PCC policy rules with the executed at least one policy rule and set a counting value of the policy hit counter against the executed policy rule to 1. The processing unit (112) is configured to transmit the updated set of PCC policy rules and the counting value of the policy hit counter to a service management platform (SMP).

[00109] In an embodiment, the processing unit (112) configured to generate at least one policy hit counter map based upon the generated updated counting value corresponding to each policy rule.

[00110] In an embodiment, the system further includes a display (114) configured to display the at least one generated policy hit counter map.

[00111] In an embodiment, the system is configured to perform data replication to update the policy hit counter map corresponding to each policy rule executed on each PCRF/PCF of the cluster of PCRFs/PCFs.

[00112] In an embodiment, the data replication is performed using remote procedure call (RPC). The RPC is a communication protocol used in networked environments that allows an application to cause a procedure (subroutine) to execute in another address space (e.g., another physical machine). For example, the RPC may be used to synchronize the state and data between two servers or between the nodes/PCRFs/PCFs.

[00113] In an embodiment, the system further includes an interfacing unit configured to receive a request from an operator for setting/resetting the counter value corresponding to a specific policy rule or the updated set of PCC policy rules.

[00114] In an embodiment, the system is configured to receive the request by employing a command-line interface (CLI) or a graphical user interface (GUI).

[00115] In an embodiment, the set of predefined PCC policy rules may include a rule name, a service identifier, one or more service data flow (SDF) filters, precedence, gate status (open/closed), Quality of Service (QoS) parameters, charging key (rating group), and various charging parameters.

[00116] The present disclosure discloses a method for monitoring one or more policy and charging control (PCC) rules in a network. The method includes storing, in a memory (110), a set of predefined PCC policy rules. The method includes initializing, by a processing unit (112), a policy hit counter of each rule of the set of predefined PCC policy rules with a counting value. The method includes monitoring, by the processing unit (112), an execution of at least one policy rule by each policy and charging rules function (PCRF)/ policy control function (PCF). The method includes determining, by the processing unit (112), whether the at least one executed policy rule exists in the memory (110). The method includes incrementing, by the processing unit (112), a counting value of the policy hit counter against the policy rule by 1 if the at least one executed policy rule exists in the memory (110) and generating an updated counting value. The method includes updating, by the processing unit (112), the set of predefined PCC policy rules with the at least one executed policy rule and setting a counting value of the policy hit counter against the executed policy rule to 1 if the executed policy rule does not exist in the memory (110). The method includes transmitting, by the processing unit (112), the updated set of PCC policy rules and the counting value of the policy hit counter to a service management platform (SMP). [00117] In an embodiment, the method allows the processing unit (112) configured to generate at least one policy hit counter map based upon the generated updated counting value corresponding to each policy rule.

[00118] In an embodiment, the method allows a display (114) configured to display the at least one generated policy hit counter map.

[00119] In an embodiment, the method is configured to perform data replication to update the policy hit counter map corresponding to each policy rule executed on each PCRF/PCF of the cluster of PCRFs/PCFs.

[00120] In an embodiment, the data replication is performed using a remote procedure call (RPC).

[00121] In an embodiment, the method allows an interfacing unit (116) configured to receive a request from an operator for setting/resetting the counter value corresponding to a specific policy rule or the updated set of PCC policy rules.

[00122] In an embodiment, the method allows the interfacing unit (116) configured to receive the request by employing a command-line interface (CLI) or a graphical user interface (GUI).

[00123] The present disclosure discloses a network function for monitoring one or more policy and charging control (PCC) rules in a network. The network function includes a memory (110) configured to store a set of predefined PCC policy rules and a processing unit (112). The processing unit (112) is configured to initialize a policy hit counter of each rule of the set of predefined PCC policy rules with a counting value. The processing unit (112) is configured to monitor an execution of at least one policy rule by the PCRF/PCF. The processing unit (112) is configured to determine whether the at least one executed policy exists in the memory (110). If the executed at least one policy rule exists in the memory (110), the processing unit (112) is configured to increment a counting value of the policy hit counter against the policy rule by 1. If the executed at least one policy rule does not exist in the memory (110), the processing unit (112) is configured to update the set of predefined PCC policy rules with the executed at least one policy rule and set a counting value of the policy hit counter against the executed policy rule to 1. The processing unit (112) is configured to transmit the updated set of PCC policy rules and the counting value of the policy hit counter to a service management platform (SMP).

[00124] The present system is configured to track the count of execution of policy rules to determine when and how they are applied within the system. In 5G network, PCRF is crucial for session establishment or modification. For successful dual connectivity, PCRF needs to support various network functions. With the fast advances of 5G standardization, the present disclosure may be applicable to in various use cases where the policy hit counts monitoring is required to ensures that policies are being correctly enforced and applied as intended. By comparing the expected counts with the actual counts, the system/operator is able to verify compliance with regulations and requirements. Further, it can be used in various system for root cause analysis to identify underlying cause of issues within the system. If there is a significant difference between the expected and actual counts, it could indicate a problem or an issue that needs attention or investigation. Implementing a robust mechanism for policy optimization helps in maintaining the integrity of the application and provides a seamless user experience even in challenging network conditions.

[00125] The method and system of the present disclosure may be implemented in a number of ways. For example, the methods and systems of the present disclosure may be implemented by software, hardware, firmware, or any combination of software, hardware, and firmware. The above-described order for the steps of the method is for illustration only, and the steps of the method of the present disclosure are not limited to the order specifically described above unless specifically stated otherwise. Further, in some embodiments, the present disclosure may also be embodied as programs recorded in a recording medium, the programs including machine-readable instructions for implementing the methods according to the present disclosure. Thus, the present disclosure also covers a recording medium storing a program for executing the method according to the present disclosure.

[00126] The present disclosure provides technical advancement related to monitoring the PCC policy rules in the network. This advancement addresses the limitations of existing solutions that do not analyze policy hit counts in real-time or near-real-time. The disclosure involves monitoring the policy hit counter to identify execution of the PCC policy rules by keeping a track of the number of times a particular policy has been hit within the application, which offer significant improvements in assessing the performance and effectiveness of the policies.

[00127] While considerable emphasis has been placed herein on 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 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 implemented merely as illustrative of the disclosure and not as a limitation.

ADVANTAGES OF THE INVENTION

[00128] The present disclosure identifies a number of times a particular policy is hit within an application to identify underutilized or over utilized policies.

[00129] The present disclosure identifies, and analyses policy hit counts in real-time or near-real-time to make informed decisions regarding policy optimization.

[00130] The present disclosure implements a policy execution tracking to track a count of execution of policy rules to determine when and how these are applied within the application. [00131] The present disclosure monitors policy hit counts and compares expected counts with actual counts to verify and ensure that policies are being correctly enforced and applied as intended.

[00132] The present disclosure uses policy hit counters to identify underlying causes of issues within the application.

[00133] The present disclosure determines an occurrence of a significant difference between expected counts and actual counts, to identify a problem or an issue that needs attention or investigation.

[00134] The present disclosure tracks the policy hit count, to assess performance and effectiveness of the policies, and determine which policies are frequently triggered or executed.

Claims

CLAIMS We Claim:

1. A system (108) for monitoring one or more policy and charging control (PCC) rules in a network, said system (108) comprising: a memory (110) configured to store a set of predefined PCC policy rules; and a processing unit (112) configured to: initialize a policy hit counter of each rule of said set of predefined PCC policy rules with a counting value; communicate with a cluster of policy and charging rules functions (PCRFs)/ policy control functions (PCFs) to monitor an execution of at least one policy rule by each PCRF/PCF; communicate with said memory (110) to determine whether said at least one executed policy rule exists in said memory (110); if said executed at least one policy rule exists in said memory (110), increment said counting value of the policy hit counter against said policy rule by 1 and generate an updated counting value; if said executed at least one policy rule does not exist in said memory (110), update said set of predefined PCC policy rules with said executed at least one policy rule and set the counting value of the policy hit counter against said executed policy rule to 1 ; and transmit said updated set of PCC policy rules and said counting value of the policy hit counter to a service management platform (SMP).

2. The system (108) as claimed in claim 1, said processing unit (112) is configured to generate at least one policy hit counter map based upon said generated updated counting value corresponding to each policy rule.

3. The system (108) as claimed in claim 2, further includes a display (114) configured to display said at least one generated policy hit counter map.

4. The system (108) as claimed in claim 2, is configured to perform data replication to update said policy hit counter map corresponding to each policy rule executed on each PCRF/PCF of said cluster of PCRFs/PCFs.

5. The system (108) as claimed in claim 4, wherein said data replication is performed using a remote procedure call (RPC).

6. The system (108) as claimed in claim 1, further includes an interfacing unit (116) configured to receive a request from an operator for setting/resetting said counter value corresponding to a specific policy rule or said updated set of PCC policy rules.

7. The system (108) as claimed in claim 6, the interfacing unit (116) is configured to receive said request by employing a command-line interface (CLI) or a graphical user interface (GUI).

8. The system (108) as claimed in claim 1 , wherein said set of predefined PCC policy rules includes a rule name, a service identifier, one or more service data flow (SDF) filters, precedence, gate status (open/closed), quality of service (QoS) parameters, charging key, and charging parameters.

9. A method (500) for monitoring one or more policy and charging control (PCC) rules in a network, said method comprising: storing (502), in a memory (110), a set of predefined PCC policy rules; initializing (504), by a processing unit (112), a policy hit counter of each rule of said set of predefined PCC policy rules with a counting value; monitoring (506), by said processing unit (112), an execution of at least one policy rule by each policy and charging rules function (PCRF)/ policy control function (PCF); determining (508), by said processing unit (112), whether said at least one executed policy rule exists in said memory (110); incrementing (510), by said processing unit (112), said counting value of the policy hit counter against said policy rule by 1 if said at least one executed policy rule exists in said memory (110) and generating an updated counting value; updating (512), by said processing unit (112), said set of predefined PCC policy rules with said at least one executed policy rule and setting said counting value of the policy hit counter against said executed policy rule to 1 if said executed policy rule does not exist in said memory (110); and transmitting (514), by said processing unit (112), said updated set of PCC policy rules and said counting value of the policy hit counter to a service management platform (SMP).

10. The method (500) as claimed in claim 9, further comprising generating, by said processing unit (112), at least one policy hit counter map based upon said generated updated counting value corresponding to each policy rule.

11. The method (500) as claimed in claim 10, further comprising displaying, by includes a display (114), said at least one generated policy hit counter map.

12. The method (500) as claimed in claim 10, further comprising performing data replication to update said policy hit counter map corresponding to each policy rule executed on each PCRF/PCF of said cluster of PCRFs/PCFs.

13. The method (500) as claimed in claim 12, wherein said data replication is performed using a remote procedure call (RPC).

14. The method (500) as claimed in claim 9, further comprising receiving, by an interfacing unit (116), a request from an operator for setting/resetting said counter value corresponding to a specific policy rule or said updated set of PCC policy rules.

15. The method (500) as claimed in claim 14, further comprising receiving, by the interfacing unit (116), said request by employing a command-line interface (CLI) or a graphical user interface (GUI).

16. A user equipment (UE) (104) communicatively coupled with a network (106), the coupling comprises steps of: receiving, by the network (106), a connection request from the UE (104); sending, by the network (106), an acknowledgment of the connection request to the UE (104); and transmitting a plurality of signals in response to the connection request, wherein monitoring of the one or more policy and charging control (PCC) rules in the network (106) is performed by a method (500) as claimed in claim 9.

17. A network function for monitoring one or more policy and charging control (PCC) rules in a network, said network function comprising: a memory (110) configured to store a set of predefined PCC policy rules; and a processing unit (112) configured to: initialize a policy hit counter of each rule of said set of predefined PCC policy rules with a counting value; monitor an execution of at least one policy rule by said PCRF/PCF; determine whether said at least one executed policy exists in said memory (110); if said executed at least one policy rule exists in said memory (110), increment said counting value of the policy hit counter against said policy rule by 1 ; if said executed at least one policy rule does not exist in said memory (110), update said set of predefined PCC policy rules with said executed at least one policy rule and set said counting value of the policy hit counter against said executed policy rule to 1 ; and transmit said updated set of PCC policy rules and said counting value of the policy hit counter to a service management platform (SMP).

18. A computer program product comprising a non-transitory computer- readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to: store, in a memory (110), a set of predefined PCC policy rules; initialize, by a processing unit (112), a policy hit counter of each rule of said set of predefined PCC policy rules with a counting value; monitor, by said processing unit (112), an execution of at least one policy rule by each policy and charging rules function (PCRF)/ policy control function (PCF); determine, by said processing unit (112), whether said at least one executed policy rule exists in said memory (110); increment, by said processing unit (112), said counting value of the policy hit counter against said policy rule by 1 if said at least one executed policy rule exists in said memory (110) and generates an updated counting value; update, by said processing unit (112), said set of predefined PCC policy rules with said at least one executed policy rule and set said counting value of the policy hit counter against said executed policy rule to 1 if said executed policy rule does not exist in said memory (110); and transmit, by said processing unit (112), said updated set of PCC policy rules and said counting value of the policy hit counter to a service management platform (SMP).