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 IMPLEMENTING QUOTA MANAGEMENT IN A 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

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 enable service providers to control and manage usage of network resources. More particularly, the present disclosure relates to a system and a method for implementing a quota management in a policy and charging rules function (PCRF)/policy control function (PCF) architecture for one or more network services provided by a network.
DEFINITION
[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 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.
[005] 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.
[006] The term PCEF as used herein, refers to a Policy and Charging
Enforcement Function. The PCEF plays a central role in enforcing policy control and charging rules for subscriber sessions, ensuring that service usage is managed according to operator-defined policies and that subscribers are correctly charged for their usage.
[007] The term QCI as used herein, refers to a Quality of Service Class
Identifier. The QCI prioritizes traffic and allocates network resources accordingly. The QCI is used to differentiate between various types of traffic, such as voice, video, and data, and to ensure that each type of traffic receives the appropriate level of service.
[008] The term APN-AMBR as used herein, refers to an Access Point
Name-Aggregated Maximum Bit Rate. The APN-AMBR controls the maximum combined uplink and downlink data rate allowed for a specific user device within a particular APN (Access Point Name) context.
[009] The term CCR-U as used herein, refers to Credit-Control Update.
The CCR-U messages are part of the charging and policy control procedures, facilitating real-time credit control and charging interactions between network elements, such as the Policy Control Function (PCF) and an Online Charging System (OCS).
[0010] The term PGW as used herein, refers to a packet data network
gateway. The PGW acts as the interface between the LTE network and other packet data networks.
BACKGROUND
[0011] The following description of related art is intended to provide

background information pertaining to the field of the disclosure. This section may include certain embodiments 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.
[0012] Wireless communication technology has rapidly evolved over the
past few decades. The first generation of wireless communication technology was analog technology that offered only voice services. Further, when the second-generation (2G) technology was introduced, text messaging and data services became possible. The 3G technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth generation (4G) technology revolutionized the wireless communication with faster data speeds, improved network coverage, and security. Fifth generation (5G) and advanced-generation technology are being deployed, with even faster data speeds, low latency, and the ability to connect multiple devices simultaneously.
[0013] As mobile networks continue to grow, users are increasingly
concerned about the quality and performance of their network connections. Conventionally, there is no limit on availability of network resources to users of the network. This may lead to excessive used of the network resources by the users of the network leading to reduced Quality of service (QoS), unfair usage, and abuse of the network resources.
[0014] There is therefore a need for an improved system and a method that
may overcome the disadvantages of the prior art and that may provide a policy and charging control on the available network resources, by defining network availability quotas for the subscribers.
OBJECTS OF THE PRESENT DISCLOSURE
[0015] It is an object of the present disclosure to enable service providers to

control and manage usage of network resources.
[0016] It is an object of the present disclosure to provide a system and a
method for implementing a quota management in a policy and charging rules function (PCRF)/policy control function (PCF) architecture for one or more network services provided by a network.
[0017] It is an object of the present disclosure to allow network operators to
set limits on various parameters such as data volume, time, or quality of service, thus ensuring fair usage and preventing abuse of network resources.
[0018] It is an object of the present disclosure to implement the quota
management in the PCRF/PCF using Quality of Service (QoS) class identifier (QCI) and Access Point Name-Aggregated Maximum Bit Rate (APN-AMBR).
[0019] It is an object of the present disclosure to configure the QCI and
APN-AMBR values in the PCRF/PCF so as to enable the service providers to manage data usage of the subscribers.
[0020] It is an object of the present disclosure to enable the PCRF/PCF
perform policy and charging control when the subscriber initiates a session, based on defined quotas.
SUMMARY
[0021] In an exemplary embodiment, the present invention discloses a
system for implementing a quota management in a policy and charging rules function (PCRF)/policy control function (PCF) architecture for one or more network services provided by a network. The system comprises a processing unit and a memory coupled to the processing unit. The memory includes instructions when executed configures the processing unit to receive a request from a user equipment (UE). The instructions refer to any set of instructions or algorithms

designed to be executed by a computer. These instructions are typically in the form of software programs or applications that dictate the operations a computer system should perform. The processing unit is configured to extract one or more parameters from the received request. The processing unit is configured to determine a type of quota applicable for the UE based on the one or more extracted parameters. The processing unit is configured to identify if the type of determined quota meets at least one pre-defined criteria. In response to the identification, the processing unit is configured to perform at least one operation associated with the network service based on the type of determined quota. The processing unit is configured to communicate a response message to the UE based on the at least one performed operation.
[0022] In some embodiments, the one or more extracted parameters include
at least one of a location of the UE, a data usage of the UE, and a policy rule associated with the UE.
[0023] In some embodiments, the type of determined quota includes at least
one of a pooled quotas and a single quota.
[0024] In some embodiments, the at least one pre-defined criteria include
identifying if the type of determined quota is at least a valid and a non-exhausted quota.
[0025] In some embodiments, the at least one operation associated with the
network service includes at least one of a real-time monitoring of the data usage of the UE, updating a set of policy rules for the UE, and updating the applicable quota for the UE.
[0026] In some embodiments, the system is further configured to retrieve
details of the pooled quota based on a terminal wireless access node identifier (TWAN ID).
[0027] In some embodiments, the single quota includes at least one of a

volume based quota, a time based quota and a combined time and volume based quota.
[0028] In an exemplary embodiment, the present invention discloses a
method for implementing a quota management in a policy and charging rules function (PCRF)/policy control function (PCF) architecture for one or more network services provided by a network. The method comprising receiving a request from a user equipment (UE) and extracting one or more parameters from the received request. The method comprising determining, by the PCRF/PCF, a type of quota applicable for the UE based on the one or more extracted parameters. The method comprising identifying if the type of determined quota meets at least one pre-defined criteria. The method comprising responsive to the identification, performing at least one operation associated with the network service based on the type of determined quota. The method comprising communicating a response message to the UE based on the at least one performed operation.
[0029] In some embodiments, the one or more extracted parameters include
at least one of a location of the UE, a data usage of the UE, and a policy rule associated with the UE.
[0030] In some embodiments, the type of determined quota includes at least
one of a pooled quotas and a single quota.
[0031] In some embodiments, the at least one pre-defined criteria include
identifying if the type of determined quota is at least a valid and a non-exhausted quota.
[0032] In some embodiments, the at least one operation associated with the
network service includes at least one of a real-time monitoring of the data usage of the UE, updating a set of policy rules for the UE, and updating the applicable quota for the UE.
[0033] In some embodiments, the method further comprising retrieving

details of the pooled quota based on a terminal wireless access node identifier (TWAN ID).
[0034] In some embodiments, the single quota includes at least one of a
volume based quota, a time based quota and a combined time and volume based quota.
[0035] In an exemplary embodiment, the present invention 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, sending, by the network, an acknowledgment of the connection request to the UE and transmitting a plurality of signals in response to the connection request. A quota management in a policy and charging rules function (PCRF)/policy control function (PCF) architecture for one or more network services provided by the network is implemented by a method comprising receiving a request from the UE and extracting one or more parameters from the received request. The method comprising determining a type of quota applicable for the UE based on the one or more extracted parameters. The method comprising identifying if the type of determined quota meets at least one pre-defined criteria. The method comprising responsive to the identification, performing at least one operation associated with the network service based on the type of determined quota. The method comprising communicating a response message to the UE based on the at least one performed operation.
BRIEF DESCRIPTION OF THE DRAWINGS
[0036] The accompanying drawings, which are incorporated herein, and
constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each

component. It will be appreciated by those skilled in the art that disclosure of such drawings includes the disclosure of electrical components, electronic components or circuitry commonly used to implement such components.
[0037] FIG. 1A illustrates an exemplary network architecture in which or
with which embodiments of the present disclosure may be implemented.
[0038] FIG. 1B illustrates a block diagram of a system for implementing a
quota management in a policy and charging rules function (PCRF)/policy control function (PCF) architecture for one or more network services provided by a network, in accordance with an embodiment of the disclosure.
[0039] FIG. 2 illustrates an exemplary flowchart representing quota
management to control and manage usage of network resources, in accordance with an embodiment of the disclosure.
[0040] FIG. 3 illustrates an exemplary block diagram of a computer system
in which or with which embodiments of the present disclosure may be implemented.
[0041] FIG. 4 illustrates an exemplary flow diagram of a method for
implementing the quota management in the PCRF/PCF architecture for one or more network services provided by the network, in accordance with an embodiment of the disclosure.
[0042] The foregoing shall be more apparent from the following more
detailed description of the disclosure.
LIST OF REFERENCE NUMERALS
100A – Network architecture
102-1, 102-2…102-N – A plurality of users
104-1, 104-2…104-N – A plurality of computing devices

106 – Network
108 – System
100B – Block diagram
110 – Database
112 – Policy and charging rules function (PCRF) / Policy control function (PCF)
114 – Quota Management Module
116 – Processing unit
118 – Memory
120 – Interfacing Unit
122 – Graphical user interface (GUI)
200 – Flow chart
300 – A computer system
310 – External Storage Device
320 – Bus
330 – Main Memory
340 – Read Only Memory
350 – Mass Storage Device
360 – Communication Port
370 – Processor
400 – Flow diagram
DETAILED DESCRIPTION
[0043] 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.
[0044] 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.
[0045] 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.
[0046] 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.

[0047] 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 embodiment or design described herein as “exemplary” and/or “demonstrative” is not necessarily to be construed as preferred or advantageous over other embodiments 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.
[0048] 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.
[0049] 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.
[0050] 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.
[0051] 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 instructions refer to any set of instructions or algorithms designed to be executed by a computer. These instructions are typically in the form of software programs or applications that dictate the operations a computer system should perform. 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.
[0052] 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.
[0053] 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.
[0054] 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.
[0055] 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 embodiments of network behaviour, service quality, and charging. These policies are defined in the form of rules/policy.
[0056] 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.
[0057] 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.

[0058] In a 3rd Generation Partnership Project (3GPP) PCRF/PCF
architecture, quota management is an important embodiment that enables service providers to control and manage usage of network resources by individual subscribers. The concept of quota management allows operators to set limits on usage of various parameters such as data volume, time, or QoS, ensuring fair usage and preventing abuse of the network resources. In the PCRF/PCF architecture, the quota management is typically implemented using the QoS class identifier (QCI) and Access Point Name-Aggregated Maximum Bit Rate (APN-AMBR).
[0059] By configuring the QCI and the APN-AMBR values in the
PCRF/PCF, service providers may manage data usage of the subscribers effectively. When a subscriber initiates a session, the PCRF/PCF may perform policy and charging control based on defined quotas. If the subscriber exceeds the allocated quota, the PCRF/PCF may apply appropriate actions, such as throttling data rate and the like.
[0060] The disclosed system and method provide a comprehensive and an
enhanced approach to working of the PCRF/PCF application by providing more flexibility to define and manage quota. The disclosed system and method handle both pooled and single quotas, manages different types of quotas, applies appropriate usage monitoring, deducts granted units, handles redirect rules, and includes error handling mechanisms.
[0061] The various embodiments throughout the disclosure will be
explained in more detail with reference to FIG. 1- FIG. 4.
[0062] FIG. 1A illustrates an exemplary network architecture (100A) in
which or with which embodiments of the present disclosure may be implemented.
[0063] As illustrated in FIG. 1A, one or more computing devices (104-1,
104-2…104-N) are connected to a system (108) through a network (106). A person

of ordinary skill in the art will understand that the one or more computing devices
(104-1, 104-2…104-N) are collectively referred as computing devices (104) and
individually referred as a computing device 104. One or more users (102-1, 102-
2…102-N) provide one or more requests to the system (108). A person of ordinary
5 skill in the art will understand that the one or more users (102-1, 102-2…102-N)
may be collectively referred as users (102) and individually referred as a user (102). Further, the computing devices (104) also be referred as a user equipment (UE) (104) or as UEs (104) throughout the disclosure.
10 [0064] In an embodiment, the computing device (104) includes, but not be
limited to, a mobile, a laptop, etc. Further, the computing device (104) includes one or more in-built or externally coupled accessories including, but not limited to, a visual aid device such as a camera, audio aid, microphone, or keyboard. Furthermore, the computing device (104) includes a mobile phone, smartphone,
15 virtual reality (VR) devices, augmented reality (AR) devices, a laptop, a general-
purpose computer, a desktop, a personal digital assistant, a tablet computer, and a mainframe computer. Additionally, input devices for receiving input from the user (102) such as a touchpad, touch-enabled screen, electronic pen, and the like may be used.
20
[0065] In an embodiment, the network (106) includes, by way of example
but not limitation, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, waves,
25 voltage or current levels, some combination thereof, or so forth. The network (106)
also includes, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN),
30 a cable network, a cellular network, a satellite network, a fiber optic network, or
some combination thereof. The UE (104) may be communicatively coupled with
17

the network (106). The communicative coupling comprises receiving, from the UE (104), a connection request by the network (106), sending an acknowledgment of the connection request to the UE (104), and transmitting a plurality of signals in response to the connection request. 5
[0066] FIG. 1B illustrates a block diagram of a system (108) for
implementing a quota management in the PCRF/PCF (112) architecture for one or more network services provided by the network (106), in accordance with an embodiment of the disclosure.
10
[0067] As shown in FIG. 1B, the system (108) includes a database (110), a
network function (PCRF/PCF) (112), a quota management module (114), a processing unit (116), a memory (118), an interfacing unit (120) and a graphical user interface (GUI) (122). In an embodiment, the database (110) is configured to
15 store a plurality of subscriber/user profiles, and a set of predefined policy rules. In
an example, the set of predefined policy rules includes a rule name, a service identifier, one or more service data flow (SDF) filters, precedence, gate status (open/closed), the QoS parameters, charging key (rating group), and various charging parameters. In an example, each subscriber profile includes subscriber
20 information, a valid quota, a policy information, and the like. In another example,
the subscriber profile includes at least one of access management (AM) subscription, session management function (SMF) subscription, or short message service (SMS) subscription.
25 [0068] In an embodiment, the network function (PCRF/PCF) (112) via the
processing unit (116) and the quota management module (114) is configured to receive a request such as CCR-U (Credit-Control Update) from the UE (104). In an embodiment, the request may include at least one of a network service usage monitoring information and a network service used volume related to the UE (104).
30 A policy and charging control is performed on the UE (104) corresponding to the
received request. In an example, when the UE (104) sends the request to the
18

PCRF/PCF (112), it typically seeks updates on current quota usage or requests
authorization for additional service based on the available quotas. This message
triggers evaluations by the PCRF/PCF (112) to determine if the request aligns with
defined policies and if the subscriber/user (102) has sufficient quota remaining.
5 Notifications generated in response to these requests, such as quota warnings or
renewal confirmations, are essential for keeping the subscribers/users informed about their usage status and enabling them to manage their resources effectively to avoid service disruptions or plan upgrades as needed.
10 [0069] In an embodiment, the processing unit (116) is configured to extract
one or more parameters from the received request. In an embodiment, the quota management relies on user-related parameters to tailor data allocation and policy enforcement according to individual subscriber/user characteristics and usage patterns. These parameters include subscription plans, service classes, user profiles,
15 data usage patterns, quota usage history, quality of service requirements, subscriber
behaviour, policy preferences and policy rules associated with the UE (104), and a location of the UE (104). The policy rule associated with the UE (104) encompasses guidelines and parameters that dictate how the network resources and services are managed and allocated for the UE (104). These rules are managed by PCRF/PCF
20 (112) and ensures efficient network operation and optimizing user experience. They
define QoS parameters such as prioritization of traffic types based on latency and reliability needs, regulate access control to network resources based on subscriber/user (102) authentication and service plans, and manage bandwidth allocation to maintain fair distribution and optimize network performance during
25 varying usage scenarios. Additionally, these rules govern billing and charging
mechanisms, ensuring transparent and fair usage policies, while also enforcing stringent security measures to protect subscriber/user (102) data and network integrity. In an embodiment, the extraction process involves a structured process to retrieve critical information essential for the policy and quota management. For
30 example, the received request is parsed to decode its format and locate the data
fields containing relevant details such as the UE’s location, the data usage metrics,
19

and the associated policy rules. These parameters provide insights into the UE’s current session status and adherence to allocated quotas. Once identified, the parameters undergo validation to ensure accuracy and alignment with predefined policies. 5
[0070] In an embodiment, the processing unit (116) is configured to
determine a type of quota applicable for the UE (104) based on the one or more extracted parameters. In an embodiment, the one or more extracted parameters are evaluated against predefined quota types, encompassing data limits, transaction
10 thresholds, and time-based usage constraints. By applying policy rules and the QCI
and APN-AMBR settings, it is determined if the UE’s current usage aligns with allocated quotas. Further, dynamic adjustments may be triggered based on this assessment, including bandwidth throttling or service restrictions if quotas are exceeded. The type of quota may include, a data quota, a time-based quota, a
15 transaction quota, speed quota, fair usage policies, and a service-specific quota. The
data quota specifies the maximum amount of data the subscriber/user (102) can consume within a defined period, while time-based quota restrict access duration to services. The transaction quota regulates the number of interactions the subscriber/user (102) can initiate, and speed quota manages maximum data transfer
20 rates. The fair usage policies aim to distribute resources equitably among the users,
and service-specific quota tailor limits to particular applications or services. In an embodiment, the type of determined quota includes at least one of a pooled quotas and a single quota. In an embodiment, the pooled quota refer to a shared or collective data allowance that is allocated to a group of users, rather than to
25 individual users. With pooled quota, subscribers within a group, such as a family
plan or a corporate account, draw from a common pool of data, minutes, or other resources. This approach allows for more flexible usage patterns, as individual users can utilize varying amounts of data while staying within the overall pool limit. In an embodiment, the single quota refers to an individual data allowance allocated to
30 a specific user or subscriber account. The single quota is dedicated to a single user
and is associated with their subscription plan or service agreement. Thus, the
20

subscriber/user has a predetermined limit on the amount of data they can consume
within a given period, such as a billing cycle. Once the subscriber/user exhausts
their allocated quota, they may face additional charges, experience throttling of data
speeds, or have their access to data services restricted until the start of the next
5 billing cycle.
[0071] In an embodiment, the processing unit (116) is configured to identify
if the type of determined quota meets at least one pre-defined criteria. In an
embodiment, the at least one pre-defined criteria includes identifying if the type of
10 determined quota is at least a valid and a non-exhausted quota. In an embodiment,
the valid and non-exhausted quota refers to a data allowance that is currently available for usage by the UE (104) and has not yet been fully utilized or depleted.
[0072] In an embodiment, the processing unit (116) is configured to perform
15 at least one operation associated with the network service based on the type of
determined quota. The at least one operation that is associated with the network
service includes at least one of a real-time monitoring of the data usage of the UE
(104), updating a set of policy rules for the UE (104), and updating the applicable
quota for the UE (104). For example, the at least one operation includes throttling
20 of the data by reducing the data speed for the subscriber/user or blocking access to
data services until the start of the next billing cycle or until the subscriber/user
purchases an additional data. In an embodiment, updating the set of policy rules for
the UE (104) involves assessing current policy parameters, identifying necessary
updates based on evolving subscriber/user (102) needs, network enhancements, and
25 regulatory changes.
[0073] In an embodiment, the processing unit (116) is configured to
communicate a response message to the UE (104) based on the at least one
performed operation. In an embodiment, the response message may include a
30 notification informing the subscriber/user (102) about a status of the applicable
quota. For example, if a valid applicable pooled quota is found and not exhausted,
21

the quota management module (114) calculates the used volume unit from the
received request and adjusts the pooled quota accordingly. In an embodiment, if the
valid applicable pooled quota is exhausted or not found, the quota management
module (114) sends a redirect rule in an answer message to redirect the subscriber
5 to a predefined rule fetched from the database (110). Further, the quota management
module (114) is configured to add an updated usage monitoring information to the answer message. The response message may be communicated to the UE (104) by the processing unit (116) of the system (108) that is implementing the quota management in the PCRF/PCF (112). The response message communicates
10 regarding the status of the applicable quota and involves sending a comprehensive
and user-friendly notification that informs the subscriber/user (102) about the current usage and any relevant actions taken. The response message is structured to clearly convey details such as remaining data allowances, time periods for usage, or any adjustments made due to quota management operations. The response
15 message may be communicated through short message service (SMS), application
notifications, email, or direct display on a UE interface.
[0074] In an embodiment, when the received request is for Multi-Radio
Operator (MRO), the quota management module (114) is configured to send a
20 session release request answer (RAR) message to a Policy and Charging
Enforcement Function (PCEF). For example, in the MRO scenario, where the subscriber’s connectivity spans across multiple operators, the quota management module (114) sends the RAR message to the PCEF when necessary. This action is typically triggered when the subscriber’s data quota is exhausted or when policy
25 rules dictate the termination of a session due to specific conditions, such as fair
usage policies or network congestion management. The RAR message informs the PCEF to release the session, potentially limiting or terminating the subscriber’s access to data services according to the operator’s policies and the subscriber’s subscription plan.
30
[0075] In an embodiment, for the pooled quota request, the quota
22

management module (114) is configured to retrieve a valid applicable pooled quota
based on a terminal wireless access node identifier (TWAN ID). The TWAN ID is
associated with an access point or node through which a wireless terminal (Wi-Fi
access points, LTE base stations, or other wireless network devices) connects to the
5 network (106).
[0076] In an embodiment, for the single quota request, the quota
management module (114) is configured to check for a valid applicable quota for a subscriber profile corresponding to the subscriber fetched from the database (110).
10 If the valid applicable quota is found and not exhausted, the quota management
module (114) populates an answer message with an information based on the applicable quota and the received usage monitoring information. In an embodiment, the quota management module (114) is configured to check for another valid quota in the database if the valid applicable quota is exhausted or not found. In an
15 embodiment, the quota management module (114) is configured to allocate a new
quota and remove an old rule name from the database if another valid quota is found in the database. If no valid quota is found in the database, the quota management module (114) is configured to send a redirect rule in the answer message to be installed and remove a provisioned rule from the database (110).
20
[0077] In an embodiment, for the single quota request, the quota
management module (114) is further configured to determine a type of the single quota request. In an example, the single quota request is a time-based quota request, a volume-based quota request, or a combined quota request. For the time-based
25 quota request, the quota management module (114) is configured to determine a
credit-control time (CCTime) and if the CCTime is greater than or equal to a CCTime in the quota stored in the database, the quota management module (114) considers the quota is exhausted. If the CCTime is less than the CCTime in the quota stored in the database (110), the quota management module (114) is
30 configured to calculate and update a remaining CCTime. The quota management
module (114) is configured to and update and add monitoring information to the
23

answer message. In an embodiment, for the volume-based quota request, the quota
management module (114) is configured to calculate the used volume unit, adjust
the quota volume, and add the usage monitoring information to the answer message.
In an embodiment, for the combined quota request, the quota management module
5 (114) is configured to calculate a remaining CCTime, update the remaining volume,
and add the usage monitoring information to the answer message.
[0078] In an embodiment, the present disclosure is configured to deal with
several scenarios, such as Credit-Control Request (CCR) Non-Customer
10 Acquisition Form (Non-CAF), and usage report event-trigger in a Credit-Control
Request Update (CCR -U). The CCR Non-CAF refers to a CCR message with a non-CAF attribute. In the context of Policy and Charging Control (PCC) systems, the CCR message is used for credit control and to request authorization for service usage. The Non-CAF attribute in the CCR message may specify an action to be
15 taken by the PCRF/PCF when the credit check fails, or the user's account balance
is insufficient. When the credit check fails or the user's account balance is insufficient, the PCRF may respond with a redirect rule in the answer message. In an embodiment, the answer message may include a credit control answer (CCA) message.
20
[0079] In an embodiment, pre-provisioning of quotas is typically required
for the quota management. The pre-provisioning refers to a process of configuring and defining quotas in the system before they are utilized by the subscribers. It involves defining the quota rules, specifying the quota types, setting the thresholds
25 (duration), and associating the quotas with the appropriate subscriber profiles or
services. In an embodiment, in the present disclosure, the PCRF/PCF supports pre-provisioning of the quota through Command Line Interface (CLI)/Subscriber Management Platform (SMP) Graphical User Interface (GUI) (122). In an embodiment, the pre-provisioning of the quota includes quota creation, or quota
30 deletion. In an embodiment, the SMP GUI (122) is configured receive the updated
subscriber profiles and the usage monitoring information from the quota
24

management module (114). The SMP GUI (122) is further configured to analyse the received updated subscriber profiles and the usage monitoring information to optimize a plurality of network elements.
5 [0080] In an embodiment, the quota management module (114) is
configured to remove the quota from the subscriber profile and update the subscriber profile in the database if the quota is exhausted.
[0081] In an embodiment, the system further includes an interfacing unit
10 (120) commutatively coupled to the network function (112) and configured to
receive at least one input from an operator.
[0082] In an embodiment, the present disclosure provides a dynamic
provisioning of new quotas based on various factors such as subscriber behaviour,
15 policy changes, or network conditions. This flexibility allows for real-time
adaptation and allocation of the quotas to meet changing demands. In an embodiment, the present disclosure provides a Location-Based Quotas. The system (108) handles location-based quotas by considering the subscriber’s geographical location, and applying relevant rules and limitations based on predefined regions.
20 This ensures proper enforcement of location-specific quotas. The present disclosure
provides redirect Rule Handling by incorporating handling of redirect rules when a quota is exhausted or not applicable. The present disclosure provides an integration of redirect rule handling within the system (108), focusing on scenarios where quotas are either exhausted or not applicable. For example, when the quotas are
25 exhausted, the system (108) employs redirect rules to manage user interactions
effectively. For instance, the users exceeding bandwidth limits may be redirected to informative pages offering upgrade options or support contacts. Conversely, in instances where the quotas do not apply, such as for premium services, redirect rules can guide users to tailored content or enhanced features. These rules may be
30 implemented using the PCF and a packet data network gateway (PGW) where the
rules may get notified and then may get incorporated onto a user end. The policy
25

may get selected at the PCF and may get enforced at the PGW and then may further get reflected at the user end.
[0083] FIG. 2 illustrates an exemplary flowchart (200) representing quota
5 management to control and manage usage of network resources, in accordance with
an embodiment of the disclosure.
[0084] At step 202: In an embodiment, the system (108) receives a request
such as CCR-U (Credit-Control Update) from a UE (104). The CCR-U messages
10 are part of the charging and policy control procedures, facilitating real-time credit
control and charging interactions between network elements, such as the PCF and the OCS.
[0085] At step 204: In an embodiment, the system (108) is configured to
15 check if the received CCR-U (Credit-Control Update) is for the MRO case, or for
USAGE MONITORING. In an embodiment, the USAGE MONITORING provides a track of consumption of network resources, services, or applications by the subscriber.
20 [0086] At step 205: In an embodiment, if the CCR-U is not for the MRO
case, the system (108) proceeds the session considering it as a case of USAGE REPORT. The system (108) determines whether the request is for a pooled quota or a single quota.
25 [0087] At step 206: In an embodiment, if the CCR-U is for the MRO case,
the system (108) sends a session RAR message to the PCEF to release the session of the UE (104).
[0088] At step 208: In an embodiment, the system (108) may perform a
30 single quota management. In an embodiment, if the request is not for a pooled
quota, the system (108) may check for an individual quota from the subscriber
26

profile. In an embodiment, the system (108) may check if the single quota is valid and not exhausted.
[0089] At step 210: In an embodiment, the system (108) determines a type
5 of the single quota request when the step 208 is affirmative. The type of the single
quota request includes a time-based quota request, a volume-based quota request, or a combined quota request.
[0090] At step 212: In an embodiment, the system (108) determines if the
10 individual/single quota is exhausted or not found. The system checks for another
valid quota in the stack. If found, it may allocate the new quota and remove the old rule name or rule base name.
[0091] At step 214: In an embodiment, for time-based quotas, the system
15 (108) determine Credit-Control Time (CCT) for the subscriber/user (102). If the
CCT is greater than or equal to the CCT in the quota, the quota is considered exhausted. Otherwise, the remaining CCT is calculated and updated, and usage monitoring information is added to the answer (step 220).
20 [0092] At step 216: In an embodiment, for volume-based quotas, the system
(108) calculates the used volume unit, adjusts the quota volume, and adds the usage monitoring information to the answer message (step 220).
[0093] At step 218: In an embodiment, for time and volume-based quotas,
25 the system (108) calculates the remaining CCT, updates the remaining volume, and
adds the appropriate usage monitoring information to the answer message (step
220). If a valid quota is found and it is not exhausted, the system (108) populates
the answer message with an appropriate information based on the applicable quota,
and the received usage monitoring information. In an embodiment, the CCT
30 represents a time duration (in seconds) for which the user is granted a specific
service or resource.
27

[0094] At step 222: In an embodiment, the system (108) sends a CCR U
response message to the subscriber.
[0095] At step 224: In an embodiment, in case of a pooled quota, the
5 applicable pooled quota is retrieved based on the TWAN ID.
[0096] At step 226: In an embodiment, it is determined if the retrieved
pooled quota is valid and not exhausted.
10 [0097] At step 228: In an embodiment, when it is determined that the
retrieved pooled quota is valid and not exhausted, the used volume unit is calculated from the received CCR-U, and the pooled quota is adjusted accordingly.
[0098] At step 230: In an embodiment, when it is determined that the
15 retrieved pooled quota is not valid and is exhausted, the system (108) sends a
redirect rule in an answer message to redirect the subscriber to a predefined rule. In
an embodiment, if no valid quota is available in the stack, the system sends a
redirect rule in the answer message to be installed and an already provisioned rule
to be removed. In an embodiment, in both pooled and single quota cases, if the
20 quota is exhausted, the system removes the quota from the subscriber profile and
update the profile in the database.
[0099] At step 232: In an embodiment, the system (108) sends the CCR U
response message to the subscriber and the quota management is performed (step
25 234). Further, the PCRF/PCF may add updated usage monitoring information to the
answer messages and set the last granted unit in a diameter session object in a local cache.
[00100] The disclosed system (108) and method facilitate flexible handling
30 of individual quotas by iterating through a list of quotas, and selecting an applicable
quota based on certain criteria (e.g., quota in use, validity, location-based). This
28

flexibility may allow for customization, and adaptation to different scenarios and
business requirements. Further, the disclosed system (108) and method effectively
manages an allocation of the resources based on different quota types (time-based,
volume-based, or combined), and their associated parameters. This ensures that the
5 allocated quotas are utilized appropriately and within defined constraints.
Furthermore, the disclosed system and method handles scenarios where current quota is exhausted or are not assigned. This is done by looking for alternative non-location-based quotas in a stack (e.g., default quota). This dynamic quota allocation ensures that the subscriber is provided with an appropriate quota for usage, even if
10 the original quota is no longer available. In addition, the disclosed system and
method facilitates to provide rule management. In cases where no quota is assigned or exhausted, rule installation and removal is managed by adding redirect rules to answer messages and removing previously provisioned rules. This ensures that the appropriate charging rules are enforced for the subscriber's usage. Also, handling
15 of redirect rules is provided when a quota is exhausted or not applicable. It sends
predefined redirect rules to apply specific charging rules.
[00101] FIG. 3 illustrates an exemplary computer system (300) in which or
with which embodiments of the present disclosure may be implemented. As shown
20 in FIG. 3, the computer system (300) may include an external storage device (310),
a bus (320), a main memory (330), a read-only memory (340), a mass storage device (350), communication port(s) (360), and a processor (370). A person skilled in the art will appreciate that the computer system (300) may include more than one processor and communication ports. The processor (370) may include various
25 modules associated with embodiments of the present disclosure. The
communication port(s) (360) 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) (360) may be chosen depending on a network, such a Local
30 Area Network (LAN), Wide Area Network (WAN), or any network to which the
computer system connects.
29

[00102] The main memory (330) may be random access memory (RAM), or
any other dynamic storage device commonly known in the art. The read-only
memory (340) may be any static storage device(s) e.g., but not limited to, a
5 Programmable Read Only Memory (PROM) chips for storing static information
e.g., start-up or Basic Input/Output System (BIOS) instructions for the processor
(370). The mass storage device 350 may be any current or future mass storage
solution, which can be used to store information and/or instructions. Exemplary
mass storage device (350) includes, but is not limited to, Parallel Advanced
10 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.
15 [00103] The bus (320) communicatively couples the processor (370) with the
other memory, storage, and communication blocks. The bus (320) 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,
20 such a front side bus (FSB), which connects the processor (370) to the computer
system.
[00104] Optionally, operator and administrative interfaces, e.g., a display,
keyboard, joystick, and a cursor control device, may also be coupled to the bus
25 (320) 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) (360). 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
30 disclosure.
30

[00105] FIG. 4 illustrates an exemplary flow diagram of the method (400) for
implementing the quota management in the PCRF/PCF (112) architecture for one
or more network services provided by the network (106), in accordance with an
embodiment of the disclosure. The network services include a range of advanced
5 functionalities designed to enhance communication, enable efficient resource
sharing, and provide access to distributed resources at unprecedented speeds and capacities by the network. These services may include calling services, providing internet, barring services, audio-video calls etc but not limited to these.
10 [00106] At step 402: The method (400) includes receiving a request such as
CCR-U from the UE (104). A policy and charging control is performed on the UE (104) corresponding to the received request. In an example, when the UE (104) sends the request to the PCRF/PCF (112), it typically seeks updates on current quota usage or requests authorization for additional service based on the available quotas.
15 This message triggers evaluations by the PCRF/PCF (112) to determine if the
request aligns with defined policies and if the subscriber/user (102) has sufficient quota remaining. Notifications generated in response to these requests, such as quota warnings or renewal confirmations, are essential for keeping the subscribers/users informed about their usage status and enabling them to manage
20 their resources effectively to avoid service disruptions or plan upgrades as needed.
[00107] At step 404: The method (400) includes extracting one or more
parameters from the received request. The one or more extracted parameters may include at least one of a location of the UE (104), a data usage of the UE (104), and
25 a policy rule associated with the UE (104). The policy rule associated with the UE
(104) encompasses guidelines and parameters that dictate how the network resources and services are managed and allocated for the UE (104). These rules are managed by PCRF/PCF (112) and ensures efficient network operation and optimizing user experience. They define QoS parameters such as prioritization of
30 traffic types based on latency and reliability needs, regulate access control to
network resources based on subscriber/user (102) authentication and service plans,
31

and manage bandwidth allocation to maintain fair distribution and optimize
network performance during varying usage scenarios. Additionally, these rules
govern billing and charging mechanisms, ensuring transparent and fair usage
policies, while also enforcing stringent security measures to protect subscriber/user
5 (102) data and the network integrity. In an embodiment, the extraction process
involves a structured process to retrieve critical information essential for the policy
and quota management. For example, the received request is parsed to decode its
format and locate specific data fields containing relevant details like the UE’s
location, data usage metrics, and associated policy rules. These parameters provide
10 insights into the UE’s current session status and adherence to allocated quotas. Once
identified, the parameters undergo validation to ensure accuracy and alignment with predefined policies.
[00108] At step 406: The method (400) includes determining a type of quota
15 applicable for the UE (104) based on the one or more extracted parameters. In an
embodiment, the one or more extracted parameters are evaluated against predefined quota types, encompassing data limits, transaction thresholds, and time-based usage constraints. By applying policy rules and the QCI and APN-AMBR settings, it is determined if the UE’s current usage aligns with allocated quotas. Further, dynamic
20 adjustments may be triggered based on this assessment, including bandwidth
throttling or service restrictions if quotas are exceeded. The type of quota may include, a data quota, a time-based quota, a transaction quota, speed quota, fair usage policies, service-specific quota. The data quota specifies the maximum amount of data a subscriber/user (102) can consume within a defined period, while
25 time-based quota restricts access duration to services. The transaction quota
regulates the number of interactions a subscriber/user (102) can initiate, and speed constraints manage maximum data transfer rates. The fair usage policies aim to distribute resources equitably among users, and service-specific quota tailor limits to particular applications or services. In an embodiment, the type of determined
30 quota includes at least one of a pooled quota and a single quota. In an embodiment,
the pooled quota refers to a shared or collective data allowance that is allocated to
32

a group of users, rather than to individual users. In an embodiment, the single quota
refers to an individual data allowance allocated to a specific user or subscriber
account. The single quota is dedicated to a single user and is associated with their
subscription plan or service agreement. Thus, the subscriber/user (102) has a
5 predetermined limit on the amount of data they can consume within a given period,
such as a billing cycle. Once the user exhausts their allocated quota, they may face additional charges, experience throttling of data speeds, or have their access to data services restricted until the start of the next billing cycle.
10 [00109] At step 408: The method (400) includes identifying if the type of
determined quota meets at least one pre-defined criteria. In an embodiment, the at least one pre-defined criteria includes identifying if the type of determined quota is at least a valid and a non-exhausted quota. In an embodiment, the valid and non-exhausted quota refers to a data allowance that is currently available for usage by
15 the UE (104) and has not yet been fully utilized or depleted.
[00110] At step 410: The method (400) includes responsive to the
identification, performing at least one operation associated with the network service based on the type of determined quota. In an embodiment, the at least one operation
20 associated with the network service includes at least one of a real-time monitoring
of the data usage of the UE (104), updating a set of policy rules for the UE (104), and updating the applicable quota for the UE (104). For example, the at least one operation includes throttling of the data by reducing the data speed for the subscriber/user and blocking access to data services until the start of the next billing
25 cycle or until the subscriber purchases additional data. In an embodiment, updating
the set of policy rules for the UE (104) involves assessing current policy parameters, identifying necessary updates based on evolving subscriber/user (102) needs, network enhancements, and regulatory changes.
30 [00111] At step 412: The method (400) includes communicating a response
message to the UE (104) based on the at least one performed operation. In an
33

embodiment, the response message include a notification for informing the subscriber/user (102) about a status of the applicable quota. The response message may be communicated to the UE (104) by the processing unit (116) of the system (108) that is implementing the quota management in the PCRF/PCF (112). The response message communicates regarding the status of the applicable quota and involves sending a comprehensive and user-friendly notification that informs the subscriber/user (102) about the current usage and any relevant actions taken. The response message is structured to clearly convey details such as remaining data allowances, time periods for usage, or any adjustments made due to quota management operations. The response message may be communicated through short message service (SMS), application notifications, email, or direct display on a UE interface.
[00112] In an embodiment, the method (400) further comprising retrieving
details of the pooled quota based on a terminal wireless access node identifier (TWAN ID). In an embodiment, the details of the pooled quota are retrieved by initiating a query specifying the TWAN ID to identify the terminal or access node within the network (106). The PCRF/PCF (112) retrieves pertinent policy rules and quota information associated with the identified TWAN ID, including data usage limits, time-based quotas, and the QoS parameters. This information is processed to calculate remaining quota balances and assess usage patterns, ensuring compliance with subscribed service plans and network policies. The results are formatted into the response message, which may include current quota status, usage thresholds, and recommendations for optimizing usage or managing quotas effectively.
[00113] In an embodiment, the single quota includes at least one of a volume
based quota, a time based quota and a combined time and volume based quota. In an embodiment, for the time-based quota request, a credit-control time (CCTime) is determined and if the CCTime is greater than or equal to a CCTime in the quota stored in the database, the quota management module (114) considers the quota is

exhausted. If the CCTime is less than the CCTime in the quota stored in the database (110), the quota management module (114) is configured to calculate and update a remaining CCTime. The quota management module (114) is configured to update and add monitoring information to the answer message. In an embodiment, for the volume-based quota request, the quota management module (114) is configured to calculate the used volume unit, adjust the quota volume, and add the usage monitoring information to the answer message. In an embodiment, for the combined quota request, the quota management module (114) is configured to calculate a remaining CCTime, update the remaining volume, and add the usage monitoring information to the answer message.
[00114] In an exemplary embodiment, the present disclosure discloses 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. A quota management for one or more network services provided by the network (106) is implemented by a method (400) comprising receiving a request from the UE (104), extracting one or more parameters from the received request, and determining a type of quota applicable for the UE (104) based on the one or more extracted parameters. The method (400) comprising identifying if the type of determined quota meets at least one pre¬defined criteria. The method (400) comprising responsive to the identification, performing at least one operation associated with the network service based on the type of determined quota. The method (400) further comprising communicating a response message to the UE (104) based on the at least one performed operation.
[00115] Conventionally, quota management is typically implemented using
the QoS (Quality of Service) class identifier (QCI) and the APN-AMBR (Access Point Name-Aggregated Maximum Bit Rate). By configuring the QCI and APN-AMBR values in the PCRF/PCF, service providers can manage the data usage of

subscribers effectively. When a subscriber initiates a session, the PCRF/PCF performs policy and charging control based on the defined quotas. If the subscriber exceeds the allocated quota, the PCRF/PCF can apply appropriate actions, such as throttling the data rate etc. However, the present disclosure provides an enhancement in at PCRF/PCF which will provide more flexibility to PCRF/PCF while managing quota. Quota management in the Policy and Charging Rules Function (PCRF) is a versatile capability that finds applications in various use cases within telecommunication networks.
[00116] The present system may be employed in performing data usage
control, quality of service (QoS) differentiation and fair usage policies. Quota management is closely tied to charging and billing systems. By using the present system, the PCRF tracks and reports usage against allocated quotas, ensuring that subscribers are billed accurately for their consumption of network resources. The system may be applicable for applying policies and quotas for subscribers roaming on other networks, ensuring that policies and quotas are consistently applied to subscribers regardless of their location. In 5G network, PCRF is crucial for session establishment or modification. With the fast advances of 5G standardization, the present disclosure may be applicable to in various use cases where the policy quota monitoring is required to ensures that policies are being correctly enforced and applied as intended. Further, it can be used in various system for root cause analysis to identify underlying cause of issues within the system. Implementing a robust mechanism for quota management helps in maintaining the integrity of the application and provides a seamless user experience even in challenging network conditions.
[00117] 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.
[00118] The present disclosure provides technical advancement related to
managing performance of the network. The PCRF/PCF leveraging the QCI and
APN-AMBR for quota management offers robust capabilities to
telecommunications providers. By configuring QCI values to prioritize different types of traffic and setting APN-AMBR limits to control maximum data rates per subscriber session, PCRF/PCF ensures efficient resource allocation and network congestion management. The present disclosure enables real-time policy enforcement based on allocated quotas, allowing providers to dynamically adjust service parameters and apply necessary actions, such as throttling data speeds, to maintain service quality and adhere to fair usage policies. Thus, the present disclosure optimize network performance, and support a seamless user experience by effectively managing subscriber data usage within predefined limits.
[00119] 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

[00120] The present disclosure enables service providers to control and
manage usage of network resources.
[00121] The present disclosure provides a system and a method for
implementing a quota management in a policy and charging rules function (PCRF)/policy control function (PCF) for one or more network services provided by a network.
[00122] The present disclosure allows network operators to set limits on
various parameters such as data volume, time, or quality of service, thus ensuring fair usage and preventing abuse of network resources.
[00123] The present disclosure implements quota management in the
PCRF/PCF using Quality of Service (QoS) class identifier (QCI) and Access Point Name-Aggregated Maximum Bit Rate (APN-AMBR).
[00124] The present disclosure configures the QCI and APN-AMBR values
in the PCRF/PCF so as to enable the service providers to manage data usage of the subscribers.
[00125] The present disclosure enables the PCRF/PCF to perform policy and
charging control when the subscriber initiates a session, based on defined quotas.

WE CLAIM:
1. A system (108) for implementing a quota management in a policy and
charging rules function (PCRF)/policy control function (PCF) (112)
architecture for one or more network services provided by a network (106),
the system (108) comprising:
a processing unit (116);
a memory (118) coupled to the processing unit (116), wherein the memory (118) includes instructions when executed configure the processing unit (116) to:
receive a request from a user equipment (UE) (104);
extract one or more parameters from the received request;
determine a type of quota applicable for the UE (104) based on the one or more extracted parameters;
identify if the type of determined quota meets at least one pre-defined criteria;
responsive to the identification, perform at least one operation associated with the network service based on the type of determined quota; and
communicate a response message to the UE (104) based on the at least one performed operation.
2. The system (108) as claimed in claim 1, wherein the one or more extracted parameters include at least one of a location of the UE (104), a data usage of the UE (104), and a policy rule associated with the UE (104).
3. The system (108) as claimed in claim 1, wherein the type of determined quota includes at least one of a pooled quotas and a single quota.

4. The system (108) as claimed in claim 1, wherein the at least one pre-defined criteria includes identifying if the type of determined quota is at least a valid and a non-exhausted quota.
5. The system (108) as claimed in claim 1, wherein the at least one operation associated with the network service includes at least one of a real-time monitoring of the data usage of the UE (104), updating a set of policy rules for the UE (104), and updating the applicable quota for the UE (104).
6. The system (108) as claimed in claim 3, further configured to retrieve details of the pooled quota based on a terminal wireless access node identifier (TWAN ID).
7. The system (108) as claimed in claim 3, wherein the single quota includes at least one of a volume based quota, a time based quota and a combined time and volume based quota.
8. A method (400) for implementing a quota management in a policy and charging rules function (PCRF)/policy control function (PCF) (112) architecture for one or more network services provided by a network (106), the method (400) comprising:
receiving (402) a request from a user equipment (UE) (104);
extracting (404) one or more parameters from the received request;
determining (406), by the PCF/PCRF (112), a type of quota applicable for the UE (104) based on the one or more extracted parameters;
identifying (408) if the type of determined quota meets at least one pre-defined criteria;
responsive to the identification, performing (410) at least one operation associated with the network service based on the type of determined quota; and

communicating (412) a response message to the UE (104) based on the at least one performed operation.
9. The method (400) as claimed in claim 8, wherein the one or more extracted parameters include at least one of a location of the UE (104), a data usage of the UE (104), and a policy rule associated with the UE (104).
10. The method (400) as claimed in claim 8, wherein the type of determined quota includes at least one of a pooled quotas and a single quota.
11. The method (400) as claimed in claim 8, wherein the at least one pre-defined criteria includes identifying if the type of determined quota is at least a valid and a non-exhausted quota.
12. The method (400) as claimed in claim 8, wherein the at least one operation associated with the network service includes at least one of a real-time monitoring of the data usage of the UE (104), updating a set of policy rules for the UE (104), and updating the applicable quota for the UE (104).
13. The method (400) as claimed in claim 10, further comprising retrieving details of the pooled quota based on a terminal wireless access node identifier (TWAN ID).
14. The method (400) as claimed in claim 10, wherein the single quota includes at least one of a volume based quota, a time based quota and a combined time and volume based quota.
15. 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 a quota management in a policy and charging rules function (PCRF)/policy control function (PCF) (112) architecture for one or more network services provided by the network (106) is implemented by a method (400) as claimed in claim 8.