FORM 2
THE PATENTS ACT, 1970
THE PATENTS RULES, 2003
COMPLETE SPECIFICATION
NETWORK
APPLICANT
of Office-101, Saffron, Nr JO PLATFORMS LIMITED._
380006, Gujarat, India; Nationality: India
The following specification particularly describes
the invention and the manner in which
it is to be performed

RESERVATION OF RIGHTS
[0001] A portion of the disclosure of this patent document contains material,
which is subject to intellectual property rights such as but are not limited to, copyright, design, trademark, integrated circuit (IC) layout design, and/or trade dress protection, belonging to Jio Platforms Limited (JPL) or its affiliates (hereinafter referred as owner). The owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all rights whatsoever. All rights to such intellectual property are fully reserved by the owner.
FIELD OF INVENTION
[0002] The embodiments of the present disclosure generally relate to
throttling services in a communications network. More particularly, the present disclosure relates to a system and method for throttling services associated with users in a network.
DEFINITION
[0003] As used in the present disclosure, the following terms are generally
intended to have the meaning as set forth below, except to the extent that the context
in which they are used to indicate otherwise.
[0004] A policy control function (PCF) provides policy rules for control
plane functions. This includes network slicing, roaming, and mobility management.
[0005] A policy and charging rules function (PCRF) is a policy decision
point for subscriber data flows in the network. Using inputs from other network
nodes, the PCRF will formulate rules which control how traffic flows (required
QoS, restrictions, throttling, blocking, billing, etc.) over the network down to
individual subscriber granularity.
[0006] A deep packet inspection (DPI) is a method of examining and
managing network traffic. It is a form of packet filtering that locates, identifies,

classifies, and reroutes or blocks packets with specific data or code payloads that
conventional packet filtering, which examines only packet headers, cannot detect.
[0007] A session management function (SMF) establishes, modifies, and
terminates, the PDU sessions established between the UE and the UPF in the
network.
[0008] A charging function (CHF) is deployed to the network side to
complete the billing function. The CHF supports the online charging, offline
charging, and convergent charging models.
[0009] A binding support function (BSF) maintains and provides the user
identity, the data network name (DNN), UE addresses, and the PCF address for the
PDU session. The PCF registers a new session binding information in the BSF and
obtains a unique BSF binding ID for the existing PDU session.
[0010] A network repository function (NRF) is the network node(s)
repository (database). The NRF implements registration and discovery of various
other 5G network services, either in a local or a remote network. The NRF also
provides a service for requesting OAuth2 access tokens.
[0011] An application function (AF) is a functional entity responsible for
handling service-specific aspects and application-related policies. It plays a crucial
role in enabling the delivery of various services and applications over the network.
[0012] An access and mobility management function (AMF) is a functional
entity responsible for registration management, connection management,
reachability management, mobility management and various function relating to
security and access management and authorization.
[0013] An online charging system (OCS) is a system allowing a
communications service provider to charge their customers, in real time, based on
service usage.
[0014] A packet data network gateway (PGW) is a server/system within a
mobile network that provides connectivity between the user's device such as a cell
phone and other networks such as internet.
[0015] A network management station (NMS) is a server that runs a network
management application. Network elements communicate with the NMS to relay

management and control information. The NMS also enables network data analysis and reporting.
[0016] A subscriber profile repository (SPR) is a system for storing and
managing subscriber-specific policy control data as defined under the 3GPP standard.
[0017] A Sd interface is to support Application Detection and Control
(ADC) rule handling, usage monitoring control of traffic detection function (TDF) sessions and of detected applications. The Sd interface supports reporting of the start and the stop of a detected application’s traffic and transfer of service data flow descriptions for detected applications.
[0018] A N7 interface triggers session management policies towards a
session management function (SMF).
[0019] A N28 interface supports the key charging and quota handling
scenarios.
[0020] A N15 interface is between the Policy Control Function (PCF) and
the Access and Mobility Management Functions (AMF) in the case of a non-roaming scenario, or the Visited PCF (vPCF) and Access and Mobility Management Functions (AMF) in case of a roaming scenario.
[0021] A Rx interface enables transport of application-level session
information from P-CSCF to PCRF.
[0022] The Gx interface connects the PCRF with policy enforcement points.
The serving GPRS support node (SGSN), gateway GPRS support node (GGSN), and PDN Gateway are all considered as enforcement points, supported by the Gx interface.
[0023] A Sy interface connects the PCRF and OCS. It enables the transfer
of subscriber spending information from the OCS to PCRF. This allows the PCRF to make policy decisions based on spending limits. The interface uses Diameter and supports initial and intermediate requests to get policy counter statuses and subscribe to status change notifications. It also supports final requests to unsubscribe from all notifications.

BACKGROUND OF THE INVENTION
[0024] 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.
[0025] In the telecommunication network, policy and charging rules
function (PCRF) is the network node designated in real-time to determine policy rules in a multimedia network. The PCRF may provide application detection and control (ADC) rules to the deep packet inspection (DPI) through Sd interface. The ADC rules are used to provide and apply the detection, enforcement actions and applicable charging parameters for the specified application traffic.
[0026] The ADC rule are selected based on various information such as
information obtained from the PGW via the Gx reference point, e.g. request type, subscriber/device related information, location information; information obtained from the subscriber profile repository (SPR), information obtained from the deep packet inspection (DPI), information obtained from the bearer binding and event reporting function (BBERF), and information obtained from the application function (AF), and own PCRF pre-configured information etc. However, there is no ADC rule decision taken between DPI and PCRF, based on the request received from online charging system (OCS).
[0027] There is, therefore, a need in the art to provide a system and a method
that can mitigate the problems associated with the prior arts.
SUMMARY
[0028] In an exemplary embodiment, a method for throttling a plurality of
services associated with a plurality of users in a network is described. The method comprises receiving, by a policy control function (PCF) and a policy and charging rules function (PCRF), a first message along with policy counter IDs (PCIDs) from an online charging system (OCS) or charging function (CHF) over a first interface.

The first message is a spending limit control notification or a spending-status-
notification-request (SNR). The method comprises initiating, by the PCF and the
PCRF, a second message towards a packet data network gateway (PGW) or a
session management function (SMF) over a second interface based on PCIDs. The
second message is re-authorization request (RAR) or session management (SM)
policy control update notification. The method comprises sending, by the PCF and
the PCRF, a third message with a plurality of updated application detection and
control (ADC) rules to a deep packet inspection (DPI) over a third interface.
[0029] In some embodiments, on receiving the SNR from the OCS or CHF,
adding, by the PCF and the PCRF, a configurable flag in a command line interface (CLI) or an element management system (EMS) to send the RAR on the third interface. On receiving the SNR along with PCIDs from the OCS/CHS, setting, by the PCF and the PCRF, the configurable flag to true. On detecting that the configurable flag is true, updating, by the PCF and the PCRF, a plurality of ADC rules.
[0030] In some embodiments, the first interface a Sy interface or a N28
interface, the second interface is a Gx interface or a N7 interface, and the third interface is Sd interface.
[0031] In some embodiments, the PCF and the PCRF are configured with
the policy such that a plurality of policy identities (IDs) function as trigger/conditions.
[0032] In some embodiments, on receiving at least one of the plurality of
policy IDs, performing, by the PCF and the PCRF, at least one of plurality of actions. The plurality of actions comprises installing or activating and/or removing or deactivating a plurality of dynamic or predefined ADC rules.
[0033] In some embodiments, when a Rx session bound with a plurality of
sessions corresponding to the second interface is running, sending, by the PCF and the PCRF, an abort diameter messages for the Rx session.
[0034] In some embodiments, the configurable flag is configurable during
runtime.

[0035] In another exemplary embodiment, a system for throttling a plurality
of services associated with a plurality of users in a network is described. The system
comprises a policy control function (PCF) and a policy and charging rules function
(PCRF). The PCF and the PCRF comprises a receiving unit configured to receive a
first message along with policy counter IDs (PCIDs) from online charging system
(OCS) or charging function (CHF) over a first interface. The first message is a
spending limit control notification or a spending notification request (SNR). An
initiating unit is configured to initiate a second message towards a packet data
network gateway (PGW) or a session management function (SMF) over a second
interface based on PCIDs. The second message is re-authorization request (RAR)
or session management (SM) policy control update notification. A sending unit is
configured to send a third message with a plurality of updated ADC rules to a deep
packet inspection (DPI) over a third interface. The third message is a RAR message.
[0036] In some embodiments, on receiving the SNR from the OCS/CHF, an
adding unit is configured to add a configurable flag in a command line interface (CLI) or an element management system (EMS) to send the RAR message on the third interface. On receiving the SNR along with PCIDs from the OCS/CHS (408), a processing unit is configured to set the configurable flag to true. On detecting that the configurable flag is true, the processing unit configured to update a plurality of ADC rules.
[0037] In some embodiments, the first interface a Sy interface or a N28
interface, the second interface is a Gx interface or a N7 interface, and the third interface is Sd interface.
[0038] In some embodiments, the PCF and the PCRF are configured with
the policy such that a plurality of policy identities (IDs) function as trigger/conditions.
[0039] In some embodiments, on receiving at least one of the plurality of
policy IDs, the PCF and the PCRF are configured to perform at least one of the plurality of actions. The plurality of actions comprises installing or activating and/or removing or deactivating a plurality of dynamic or predefined ADC rules.

[0040] In some embodiments, when a Rx session bound with a plurality of
sessions corresponding to the second interface is running, the sending unit is configured to send an abort diameter messages for the Rx session.
[0041] In some embodiments, the configurable flag is configurable during
runtime.
[0042] In some embodiments, a user equipment user equipment
communicatively coupled with a system is described. The coupling comprises steps
of receiving, by the system, a connection request and sending, by the system, an
acknowledgment of the connection request to the UE. The UE is transmitting a
plurality of signals in response to the connection request. The system is configured
for throttling a plurality of services associated with a plurality of users in a network.
[0043] The foregoing general description of the illustrative embodiments
and the following detailed description thereof are merely exemplary aspects of the teachings of this disclosure and are not restrictive.
OBJECTS OF THE INVENTION
[0044] Some of the objects of the present disclosure, which at least one
embodiment herein satisfies are as listed herein below.
[0045] An object of the present disclosure is to provide a system and a
method for throttling service associated with the user in a network.
[0046] Another object of the present disclosure is to achieve efficient
resource utilization at the deep packet inspection (DPI).
[0047] Another object of the present disclosure is to provide a system and a
method that is economical and easy to implement.
BRIEF DESCRIPTION OF DRAWINGS
[0048] The accompanying drawings, which are incorporated herein, and
constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems 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,
5 or circuitry commonly used to implement such components.
[0049] FIG. 1 illustrates an example network architecture 100 for
implementing a proposed system 108, in accordance with an embodiment of the
present disclosure.
[0050] FIG. 2A illustrates an example block diagram 200A of a proposed
10 system 108, in accordance with an embodiment of the present disclosure.
[0051] FIG. 2B illustrates an example block diagram 200B of a PCF/PCRF,
in accordance with an embodiment of the present disclosure.
[0052] FIG. 3 illustrates an exemplary representation of connection diagram
300 of PCF or PCRF with other network elements through a corresponding
15 interface, in accordance with some embodiments of the present disclosure.
[0053] FIG. 4A illustrates an exemplary representation of flow diagram
400A representing method for throttling service associated with the user in a
network, in accordance with some embodiments of the present disclosure.
[0054] FIG. 4B illustrates an exemplary representation of flow 400B
20 representing method for throttling service associated with the user in a network, in
accordance with other embodiments of the present disclosure.
[0055] FIG. 5 illustrates an example computer system 500 in which or with
which the embodiments of the present disclosure may be implemented.
[0056] The foregoing shall be more apparent from the following more
25 detailed description of the disclosure.
DETAILED DESCRIPTION
[0057] In the following description, for explanation, various specific details
are outlined in order to provide a thorough understanding of embodiments of the
30 present disclosure. It will be apparent, however, that embodiments of the present
disclosure may be practiced without these specific details. Several features
9

described hereafter can each be used independently of one another or with any
combination of other features. An individual feature may not address all of the
problems discussed above or might address only some of the problems discussed
above. Some of the problems discussed above might not be fully addressed by any
5 of the features described herein.
[0058] 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
10 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.
[0059] Specific details are given in the following description to provide a
thorough understanding of the embodiments. However, it will be understood by one
15 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
20 unnecessary detail to avoid obscuring the embodiments.
[0060] 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
25 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
30 function or the main function.
10

[0061] The word “exemplary” and/or “demonstrative” is used herein to
mean serving as an example, instance, or illustration. For the avoidance of doubt,
the subject matter disclosed herein is not limited by such examples. In addition, any
aspect or design described herein as “exemplary” and/or “demonstrative” is not
5 necessarily to be construed as preferred or advantageous over other aspects or
designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive like the term
10 “comprising” as an open transition word without precluding any additional or other
elements.
[0062] 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
15 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.
20 [0063] 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
25 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.
30 [0064] Embodiments herein relate to systems and methods for throttling
service associated with the user in a network. In a telecommunication network,
11

session management function (SMF) or packet network data gateway (PGW) sends
a creation request to PCF or PCRF. The PCF or PCRF evaluates policy rules and
assigns ADC rule. Further, PCRF sends ADC rule to DPI through Sd interface.
[0065] In an embodiment, when bandwidth utilization for the user is greater
5 than a predefined threshold or allocated bandwidth utilization, then online charging
system (OCS) sends a notification along with policy counter IDs (PCIDs) in the spending limit control notification/ spending status notification request (SNR) messages over an interface such as N28/Sy reference point. When the SNR notification is transmitted from the OCS or charging function (CHF) to the policy
10 control function (PCF) or policy and charging rules function (PCRF) over the
interface such as Sy and N28 reference point, the PCRF initiates a re-auth request (RAR)/SM policy control update notification message towards the PGW/SMF over Gx/N7 reference point based on the policy counter IDs. In case when any Rx session is running which is linked with the same Gx sessions, PCRF can send abort diameter
15 messages for those Rx session based on policy implementation.
[0066] By configuring the PCF or PCRF application to send re-auth request
(RAR) diameter messages based on policy counter IDs (PCIDs) received in the spending limit control notification/SNR messages over interface such as N28/Sy reference point, quality of service (QoS) parameters can be improved or controlled
20 in user plane.
[0067] In order to configure PCF or PCRF to send RAR diameter messages,
a configurable flag (also referred to as “isToSendSdRARonSNR default Value-false”) is added in a command line interface (CLI)/ element management system (EMS) to send RAR on Sd interface when SNR is received. The configurable flag
25 is configurable during runtime. In an embodiment, upon receipt of policy counter
IDs (PCIDs) received in the spending limit control notification/SNR messages, PCRF may set the flag to true. When the configurable flag is true, then PCF or PCRF sends a RAR message to a data packet inspection (DPI) with the updated ADC rules.
30 [0068] The PCF or PCRF can be configured with the policy such that policy
IDs function as trigger and accordingly, action such as sending SAR diameter
12

message with the updated ADC rules (dynamic/predefined) can be activated/installed OR removed/deactivated when the corresponding trigger is received.
[0069] The various embodiments throughout the disclosure will be
5 explained in more detail with reference to FIGs. 1-5.
[0070] FIG. 1 illustrates an example network architecture 100 for
implementing a proposed system 108, in accordance with an embodiment of the present disclosure.
[0071] As illustrated in FIG. 1, one or more computing devices 104-1, 104-
10 2…104-N) may be connected to a proposed 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 may be collectively referred as computing devices
104 and individually referred as a computing device 104. One or more users 102-1,
102-2…102-N may provide one or more requests to the system 108. A person of
15 ordinary 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 may also be referred as a user equipment (UE) 104 or as UEs 104 throughout the disclosure.
[0072] In an embodiment, the computing device 104 may include, but not
20 be limited to, a mobile, a laptop, etc. Further, the computing device 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, audio aid, microphone, or keyboard.
Furthermore, the computing device 104 may include a mobile phone, smartphone,
virtual reality (VR) devices, augmented reality (AR) devices, a laptop, a general-
25 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.
[0073] In an embodiment, the network 106 may include, by way of example
30 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,
13

or a combination thereof, etc. one or more messages, packets, signals, waves,
voltage or current levels, some combination thereof, or so forth. The network 106
may also include, by way of example but not limitation, one or more of a wireless
network, a wired network, an internet, an intranet, a public network, a private
5 network, a packet-switched network, a circuit-switched network, an ad hoc
network, an infrastructure network, a Public-Switched Telephone Network (PSTN),
a cable network, a cellular network, a satellite network, a fiber optic network, or
some combination thereof.
[0074] In an embodiment, the user equipment (104) is communicatively
10 coupled with the system (108). The system (108) may receive a connection request
from the UE (104). The system (108) may send an acknowledgment of the connection request to the UE (104). The UE (104) may transmit a plurality of signals in response to the connection request. The system (108) may configure for throttling a plurality of services associated with a plurality of users in the network
15 (106).
[0075] FIG. 2A illustrates an example block diagram 200A of a proposed
system 108, in accordance with an embodiment of the present disclosure.
[0076] Referring to FIG. 2A, in an embodiment, the system 108 may include
one or more processor(s) 202. The one or more processor(s) 202 may be
20 implemented as one or more microprocessors, microcomputers, microcontrollers,
digital signal processors, central processing units, logic circuitries, and/or any devices that process data based on operational instructions. Among other capabilities, the one or more processor(s) 202 may be configured to fetch and execute computer-readable instructions stored in a memory 204 of the system 108.
25 The memory 204 may be configured to store one or more computer-readable
instructions or routines in a non-transitory computer readable storage medium, which may be fetched and executed to create or share data packets over a network service. The memory 204 may comprise any non-transitory storage device including, for example, volatile memory such as random-access memory (RAM),
30 or non-volatile memory such as erasable programmable read only memory
(EPROM), flash memory, and the like.
14

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

[0080] In an embodiment, the system 108 may include a policy control
function (PCF) or a policy charging rules and function (PCRF) 212.
[0081] In case, when bandwidth utilization for the user is greater than a
predefined threshold, then the online charging system (OCS) sends a notification
5 along with policy counter IDs (PCIDs) in the spending limit control
notification/SNR messages over interface such as N28/Sy reference point. When a spending-status-notification-request (SNR) notification is received from the online charging system (OCS) or charging function (CHF) over the interface such as Sy and N28 reference point, the PCF/PCRF 212 initiates a re-authorization request
10 (RAR)/SM policy control update notification message towards the PGW/SMF over
Gx/N7 reference point. By configuring the PCF or PCRF 212 application to send RAR diameter messages based on policy counter IDs (PCIDs) received in the spending limit control notification/SNR messages over interface such as N28/Sy reference point, quality of service (QoS) parameters can be improved or controlled
15 in user plane.
[0082] Although FIG. 2A shows exemplary components of the system 108,
in other embodiments, the system 108 may include fewer components, different components, differently arranged components, or additional functional components than depicted in FIG. 2A. Additionally, or alternatively, one or more components of
20 the system 108 may perform functions described as being performed by one or more
other components of the system 108.
[0083] FIG. 2B illustrates an example block diagram 200B of the
PCF/PCRF 212, in accordance with an embodiment of the present disclosure.
[0084] The PCF/PCRF 212 comprises a receiving unit 214, an initiating unit
25 216, an adding unit 218, a processing unit 220 and a sending unit 222.
[0085] The receiving unit 214 is configured to receive a first message (e.g.,
a spending limit control notification or a spending-status-notification-request (SNR)) along with policy counter IDs (PCIDs) from online charging system (OCS) or charging function (CHF) over a first interface (e.g., Sy interface or a N28
30 interface).
16

[0086] The initiating unit 216 is configured to initiate a second message
(e.g., re-authorization request (RAR) or session management (SM) policy control
update notification) towards a packet data network gateway (PGW) or a session
management function (SMF) over a second interface (e.g., Gx interface or a N7
5 interface) based on PCIDs.
[0087] The sending unit 222 is configured to send a third message (e.g.,
RAR message) with a plurality of updated application detection and control (ADC)
rules to a deep packet inspection (DPI) over a third interface (e.g., Sd interface).
[0088] On receiving the SNR from the OCS/CHF, the adding unit 218 is
10 configured to add a configurable flag in a command line interface (CLI) or an
element management system (EMS) to send the RAR message on the Sd interface.
[0089] On receiving the SNR message along with PCIDs from the
OCS/CHS, the processing unit 220 is configured to set the configurable flag to true.
[0090] On detecting that the configurable flag is true, the processing unit
15 220 is configured to update a plurality of application detection and control (ADC)
rules. The configurable flag is configurable during runtime.
[0091] In an embodiment, the PCF and the PCRF 212 are configured with
the policy such that a plurality of policy identities (IDs) act as trigger/conditions. On receiving one of the plurality of policy IDs, the PCF and the PCRF 212 is
20 configured to perform at least one of plurality of actions. The plurality of actions
comprises installing or activating and/or removing or deactivating a plurality of dynamic or predefined ADC rules. Further, when a Rx session bound with the same Gx/N7 reference point sessions is running, the PCF and the PCRF 212 is configured to send abort diameter messages for the same Rx session based on policy
25 implementation.
[0092] FIG. 3 illustrates an exemplary representation of connection diagram
300 of PCF or PCRF with other network elements connected through a corresponding interface, in accordance with some embodiments of the present disclosure.
30 [0093] As shown in the FIG. 3, the PCF and the PCRF 302 may
communicate with a plurality of network functions through a plurality of interfaces.
17

The plurality of network functions include a deep packet inspection (DPI) 308, a
session management function (SMF) 310, a charging function (CHF) 312, a binding
support function (BSF) 314, a network repository function (NRF) 316, an access
management function (AMF) 304, an application function (AF) 306, an online
5 charging system (OCS) 318, a packet data network (PDN) gateway (PGW) 320, a
network management system (NMS) 322, and a subscription profile repository (SPR) 324.
[0094] The AMF 304 may communicate with the PCF and the PCRF 302
via a N15 interface. The DPI 308 may communicate with the PCF and the PCRF
10 302 via a Sd interface. The SMF 310 may communicate with the PCF and the PCRF
302 via a N7 interface. The CHF 312 may communicate with the PCF and the PCRF 302 via a N28 interface. The BSF 314 may communicate with the PCF and the PCRF 302 via a Nbsf interface. The NRF 316 may communicate with the PCF and the PCRF 302 via a Nnrf interface. The AF 306 may communicate with the PCF
15 and the PCRF 302 via a Rx interface. The PGW 320 may communicate with the
PCF and the PCRF 302 via a Gx interface. The OCS 318 may communicate with the PCF and the PCRF 302 via a Sy interface.
[0095] FIG. 4A illustrates an exemplary representation of flow diagram
400A representing systems and methods for throttling service associated with the
20 user in a network, in accordance with some embodiments of the present disclosure.
[0096] At step 411, a session management function (SMF)/ a PDN gateway
(PGW) 402 may send session management (SM) policy control create request or a credit control request (CCR-I) to a policy control function (PCF)+policy and charging rules function (PCRF) 404.
25 [0097] At step 412, the PCF+PCRF 404 may send a traffic detection
function (TDF) session request to a deep packet inspection (DPI) 406.
[0098] At step 413, a 201 created/ a clear channel assessment (CCA) may
send to the PCF+PCRF 404. In an aspect, the “201 created” indicates that the request was successfully fulfilled and resulted in one or possibly multiple new
30 resources being created.
18

[0099] At step 414, the DPI 406 may send a TDF session answer (TSA) to
the PCF+PCRF 404.
[00100] At step 415, an online charging system (OCS) 408 may send a
spending limit control notification service operation request/a session notification
5 request along with policy counter IDs (PCIDs) over a first interface (e.g., N28/Sy
interface).
[00101] At step 416, the OCS/CHF may send a spending limit control
notification service operation response/session notification answer (SNA) to the PCF+PCRF.
10 [00102] At step 417, when the spending limit control notification service
operation request/ the spending notification request (SNR) is transmitted from the online charging system (OCS) or charging function (CHF) 408 to the PCF+PCRF 404 over the first interface (e.g., Sy and N28 interface), the PCRF 404 may initiate a re-authorization request (RAR)/SM policy control update notification message
15 towards the PGW/SMF over a second interface (e.g., Gx/N7 interface). In case,
when any Rx session is running which is linked with the same Gx sessions, the
PCRF 404 may send abort diameter messages for those Rx session based on policy
implementation.
[00103] At step 418, the SMF/PGW may send SM policy control update
20 notification response/Re-Auth Answer (RAA) to the PCF+PCRF 404.
[00104] At step 419, the PCF+PCRF 404 may send the RAR (Re-Auth-
Request) with the updated ADC rules to the DPI 406.
[00105] At step 420, the DPI 406 may send Re-Auth-Answer (RAR) to the
PCF+PCRF 404.
25 [00106] In an embodiment, by configuring the PCF+PCRF 404 to send RAR
diameter messages based on policy counter IDs (PCIDs) received in the spending
limit control notification/SNR messages over the first interface (e.g., N28/Sy
interface). The QoS parameters can be improved or controlled in a user plane.
[00107] In order to configure the PCF+PCRF 404 to send RAR diameter
30 messages, a configurable flag (also referred to as “isToSendSdRARonSNR default
Value-false”) is added in CLI/EMS to send RAR on Sd if SNR is received. The
19

configurable flag is configurable during runtime. In an embodiment, upon receipt
of policy counter IDs (PCIDs) received in the spending limit control
notification/SNR messages, the flag is set to true. When the configurable flag is
true, then PCF+PCRF 404 may send RAR diameter message to DPI with the
5 updated ADC rules.
[00108] The PCF+PCRF 404 can be configured with the policy such that
policy IDs function as trigger and accordingly, action such as sending SAR diameter message with the updated ADC rules can be activated/deactivated when the corresponding trigger is received.
10 [00109] FIG. 4B illustrates an exemplary representation of flow 400B
representing method for throttling service associated with the user in a network, in accordance with some embodiments of the present disclosure.
[00110] At step 432, receiving, by the policy control function (PCF) and the
policy and charging rules function (PCRF) 404, a first message along with policy
15 counter IDs (PCIDs) from an online charging system (OCS) or charging function
(CHF) 408 over a first interface. The first message is a spending limit control
notification or a spending-status-notification-request (SNR). The first interface a Sy
interface or a N28 interface.
[00111] At step 434, initiating, by the PCF and the PCRF 404, a second
20 message towards the packet data network gateway (PGW) or the session
management function (SMF) 402 over a second interface based on PCIDs. The second message is re-authorization request (RAR) or session management (SM) policy control update notification. The second interface is a Gx interface or a N7 interface.
25 [00112] At step 436, sending, by the PCF and the PCRF 404, a third message
with a plurality of updated ADC rules to the deep packet inspection (DPI) 406 over a third interface. The third interface is Sd interface.
[00113] Further, the PCF and the PCRF 404 are configured with the policy
such that a plurality of policy identities (IDs) function as trigger/conditions. On
30 receiving at least one of the plurality of policy IDs, the PCF and the PCRF 404 are
configured to perform at least one of a plurality of actions. The plurality of actions
20

comprises installing or activating and/or removing or deactivating a plurality of
dynamic or predefined ADC rules. When a Rx session bound with a plurality of
sessions corresponding to the second interface is running, the PCF and the PCRF
404 are configured to send an abort diameter messages for the Rx session.
[00114] FIG. 5 illustrates an example computer system 500 in which or with
which the embodiments of the present disclosure may be implemented.
[00115] As shown in FIG. 5, the computer system 500 may include an
external storage device 510, a bus 520, a main memory 530, a read-only memory 540, a mass storage device 550, a communication port(s) 560, and a processor 570. A person skilled in the art will appreciate that the computer system 500 may include more than one processor and communication ports. The processor 570 may include various modules associated with embodiments of the present disclosure. The communication port(s) 560 may be any of an RS-232 port for use with a modem-based dialup connection, a 10/100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or other existing or future ports. The communication ports(s) 560 may be chosen depending on a network, such as a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system 500 connects.
[00116] In an embodiment, the main memory 530 may be Random Access
Memory (RAM), or any other dynamic storage device commonly known in the art. The read-only memory 540 may be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chip for storing static information e.g., start-up or basic input/output system (BIOS) instructions for the processor 570. The mass storage device 550 may be any current or future mass storage solution, which can be used to store information and/or instructions. Exemplary mass storage solutions include, but are not limited to, Parallel Advanced Technology Attachment (PATA) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and/or Firewire interfaces).
[00117] In an embodiment, the bus 520 may communicatively couple the
processor(s) 570 with the other memory, storage, and communication blocks. The

bus 520 may be, e.g. a Peripheral Component Interconnect PCI) / PCI Extended (PCI-X) bus, Small Computer System Interface (SCSI), Universal Serial Bus (USB), or the like, for connecting expansion cards, drives, and other subsystems as well as other buses, such a front side bus (FSB), which connects the processor 570 to the computer system 500.
[00118] In another embodiment, operator and administrative interfaces, e.g.,
a display, keyboard, and cursor control device may also be coupled to the bus 520 to support direct operator interaction with the computer system 500. Other operator and administrative interfaces can be provided through network connections connected through the communication port(s) 560. Components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system 500 limit the scope of the present disclosure.
[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 provides a system and a method for throttling
service associated with the user in a network.
[00121] The present disclosure provides a system and a method to achieve
efficient resource utilization at the deep packet inspection (DPI).
[00122] The present disclosure provides a system and a method to provide a
system and a method that is economical and easy to implement.

WE CLAIM:
1. A method (400B) for throttling a plurality of services associated with a
plurality of users in a network (106), the method comprising:
receiving, by a policy control function (PCF) and a policy and charging rules function (PCRF) (212, 404), a first message along with policy counter IDs (PCIDs) from an online charging system (OCS) or charging function (CHF) (408) over a first interface, wherein the first message is a spending limit control notification or a spending notification request (SNR);
initiating, by the PCF and the PCRF (212, 404), a second message towards a packet data network gateway (PGW) or a session management function (SMF) (402) over a second interface based on PCIDs, wherein the second message is a re-authorization request (RAR) or a session management (SM) policy control update notification; and
sending, by the PCF and the PCRF (212, 404), a third message with a plurality of updated application detection and control (ADC) rules to a deep packet inspection (DPI) (406) over a third interface, wherein the third message is a RAR message.
2. The method as claimed in claim 1 further comprising:
on receiving the SNR from the OCS or CHF (408), adding, by the PCF and the PCRF (212, 404), a configurable flag in a command line interface (CLI) or an element management system (EMS) to send the RAR on the third interface, wherein
on receiving the SNR along with the PCIDs from the OCS or the CHS (408), setting, by the PCF and the PCRF (212, 404), the configurable flag to true; and
on detecting that the configurable flag is true, updating, by the PCF and the PCRF (212, 404), a plurality of ADC rules.

3. The method (400B) as claimed in claim 1, wherein the first interface a Sy interface or a N28 interface, the second interface is a Gx interface or a N7 interface, and the third interface is Sd interface.
4. The method (400B) as claimed in claim 1, wherein
the PCF and the PCRF (212, 404) are configured with the policy such that a plurality of policy identities (IDs) function as trigger/conditions.
5. The method (400B) as claimed in claim 4, wherein on receiving at least one of the plurality of policy IDs, performing, by the PCF and the PCRF (212, 404), at least one of plurality of actions, wherein the plurality of actions comprises installing or activating and/or removing or deactivating a plurality of dynamic or predefined ADC rules.
6. The method (400B) as claimed in claim 1 further comprising:
when a Rx session bound with a plurality of sessions corresponding to the second interface is running, sending, by the PCF and the PCRF (212, 404), an abort diameter messages for the Rx session.
7. The method (400B) as claimed in claim 2, wherein
the configurable flag is configurable during runtime.
8. A system (108) for throttling a plurality of services associated with a
plurality of users in a network (106), the system comprising a policy control
function (PCF) and a policy and charging rules function (PCRF) (212, 404),
the PCF and the PCRF (212, 404) comprising:
a receiving unit (214) configured to receive a first message along with policy counter IDs (PCIDs) from online charging system (OCS) or charging function (CHF) (408) over a first interface, wherein the first message is a spending limit control notification or a spending notification request (SNR);

an initiating unit (216) configured to initiate a second message towards a packet data network gateway (PGW) or a session management function (SMF) (402) over a second interface based on PCIDs, wherein the second message is a re-authorization request (RAR) or a session management (SM) policy control update notification; and
a sending unit (222) configured to send a third message with a plurality of updated application detection and control (ADC) rules to a deep packet inspection (DPI) over a third interface, wherein the third message is a RAR message.
9. The system as claimed in claim 8, further comprising:
on receiving the SNR from the OCS or the CHF (408), an adding unit (218) is configured to add a configurable flag in a command line interface (CLI) or an element management system (EMS) to send the RAR message on the third interface, wherein
on receiving the SNR along with the PCIDs from the OCS or the CHS (408), a processing unit (220) is configured to set the configurable flag to true; and
on detecting that the configurable flag is true, the processing unit (220) configured to update a plurality of ADC rules.
10. The system (108) claimed as in claim 8, wherein
the first interface a Sy interface or a N28 interface, the second interface is a Gx interface or a N7 interface, and the third interface is Sd interface.
11. The system (108) as claimed in claim 8, wherein
the PCF and the PCRF (212, 404) are configured with the policy such that a plurality of policy identities (IDs) function as trigger/conditions.
12. The system (108) as claimed in claim 11, wherein

on receiving at least one of the plurality of policy IDs, the PCF and the PCRF (212, 404) are configured to perform at least one of plurality of actions, wherein the plurality of actions comprises installing or activating and/or removing or deactivating a plurality of dynamic or predefined ADC rules.
13. The system (108) claimed as in claim 8, wherein
when a Rx session bound with a plurality of sessions corresponding to the second interface is running, the sending unit (222) is configured to send an abort diameter messages for the Rx session.
14. The system (108) claimed as in claim 9, wherein
the configurable flag is configurable during runtime.
15. A user equipment (UE) (104) communicatively coupled with a system
(108), the coupling comprises steps of:
receiving, by the system (108), a connection request;
sending, by the system (108), an acknowledgment of the connection request to the UE (104); and
transmitting a plurality of signals in response to the connection request, wherein the system (108) is configured for throttling a plurality of services associated with a plurality of users in a network (106) as claimed in claim 8.