FORM 2
THE PATENTS ACT, 1970 (39 of 1970) THE PATENTS RULES, 2003
COMPLETE SPECIFICATION
(See section 10; rule 13)
TITLE OF THE INVENTION
METHOD AND SYSTEM FOR MANAGING THROTTLING OPERATIONS 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
[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, belong¬ing 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.
FIELD OF THE INVENTION
[0002] The present technology relates to wireless cellular communications. More par-ticularly, the present technology relates to a method and a system for managing throt-tling operations in a network.
BACKGROUND ART
[0003] The following description of related art is intended to provide background in-formation 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. How¬ever, it should be appreciated that this section be used only to enhance the understand¬ing of the reader with respect to the present disclosure, and not as admissions of prior art.
[0004] A demand for efficient bandwidth management and control in telecommunica¬tions networks has never been more critical. As the digital landscape evolves and con¬nectivity becomes increasingly integral to daily life, service providers are constantly

challenged to optimize network resources while ensuring fair and equitable distribution among subscribers. In particular, bandwidth management and control, for the subscrib¬ers in specific geographic areas, is crucial for ensuring efficient data transfer and net¬work performance. The bandwidth management and control aspect become increas¬ingly pertinent as the demand for a high-speed internet and data-intensive applications continues to grow. In today’s digital age, the subscribers expect reliable and fast inter¬net connectivity for various activities such as streaming, gaming, remote work, and more. However, network congestion, growing demands, limited infrastructure, and di¬verse user needs can lead to slow internet speed, latency, and service interruptions, affecting user experience and satisfaction.
[0005] Conventionally available techniques for bandwidth management and control solutions aim to address these challenges by allocating and prioritizing bandwidth ef-fectively among subscribers within a specific geographic area. Some of the existing techniques that provide bandwidth management include, for example, a Quality of Ser¬vice (QoS), traffic shaping, bandwidth throttling, dynamic bandwidth allocation, and the like. However, these currently available techniques for managing bandwidth allo¬cation are inefficient as successful bandwidth management during peak usage times or unexpected spikes is not possible using the currently available techniques. Moreover, these conventional techniques may not always adapt effectively to changing network conditions and can lead to dissatisfaction among subscribers if not implemented trans¬parently or fairly. By way of an example, when a user moves to service area locations where the bandwidth available on a control plane is low, serving the user with commit¬ted data rate/bit rate may not be possible or may impact data rate of other devices. Hence, there is a need to manage the data transfer rate.
[0006] There is therefore a need in the art to provide an improved mechanism that modulated data transfer rate for the subscribers.

OBJECT OF THE INVENTION
[0007] A primary object of the embodiments of the present invention is to provide a method and a system for managing throttling operations in a network.
[0008] Another object of the embodiments of the present invention is to efficiently manage network resources by allocating and controlling maximum data transfer rate.
[0009] Another object of the embodiments of the present invention is to prevent net-work congestion/outages and provide smoother overall network experience to users (e.g., subscribers).
[0010] Another object of the embodiments of the present invention is to forgo re-at-taching to a network when a user comes out of a throttled location to experience normal data transfer rate.
[0011] Another object of the embodiments of the present invention is to avoid affecting other network services, such as audio calls, video calls, and the like, during the throt¬tling operation to avoid dissatisfaction among the users.
[0012] These and other objectives and advantages of the embodiments of the present invention will become readily apparent from the following detailed description taken in conjunction with the accompanying drawings.
SUMMARY OF THE INVENTION
[0013] In an embodiment, a method for managing throttling operations in a network is disclosed. The method includes receiving, by a first Network Function (NF) from a second NF, one of a SM policy create request or a SM policy update request comprising

a user location details corresponding to a user equipment (UE) associated with a user. The method includes processing, by the first NF, the user location details to determine whether the user location details correspond to a throttle location details or a non-throt¬tle location details. The method includes transferring, by the first NF, one of the throttle location details or the non-throttle location details to a third NF to generate one of a set of throttle Access Point Name (APN) Aggerate Maximum Bit Rate (AMBR) values or a set of non- throttle APN AMBR values corresponding to the throttle location details or the non-throttle location details, respectively. The method includes receiving, by the first NF, one of the set of throttle APN AMBR values or the set of non- throttle APN AMBR values from the third NF, in response to generating. The method includes send¬ing, by the first NF to the second NF, the set of throttle APN AMBR values or the set of non- throttle APN AMBR values for managing the throttling operations correspond¬ing to the UE.
[0014] In some embodiments, the method further includes setting, by the third NF, at least one of a user location and a plurality of SM create attributes based on the throttle location details corresponding to the UE. The method further includes evaluating, by the third NF, a policy based on matching of a plurality of network conditions with the plurality of SM create attributes in response to setting. The method further includes generating, by the third NF, a SM create policy answer comprising the set of throttle APN AMBR values based on the evaluation. The method further includes sending, by the third NF, the SM create policy answer comprising the set of throttle APN AMBR values to the third NF.
[0015] In some embodiments, the method further includes setting, by the third NF, at least one of a user location and a plurality of SM update attributes based on the non-throttle location details corresponding to the UE. The method further includes evaluat¬ing, by the third NF, a policy based on matching of the plurality of network conditions with the plurality of SM update attributes in response to setting. The method further

includes generating, the third NF, a SM update policy answer comprising the set of non-throttle APN AMBR values based on the evaluation. The method further includes sending, by the third NF, the SM update policy answer comprising the set of non-throt¬tle APN AMBR values to the third NF.
[0016] In some embodiments, the method further includes applying, by the second NF, a first set of rules along with the set of throttle APN AMBR values for implementing a pre-defined data transfer rate on the UE based on the throttle location details when the user moves into a throttle location from a non-throttle location.
[0017] In some embodiments, the method further includes applying, by the second NF, a second set of rules along with the set of non-throttle APN AMBR values for imple¬menting a normal data transfer rate on the UE based on the non- throttle location details, when the user moves into the non-throttle location from the throttle location.
[0018] In another embodiment, a system for managing throttling operations in a net-work is disclosed. The system includes a memory and a processing engine communi-catively coupled to the processing engine. The processing engine is configured to re-ceive, by a first Network Function (NF)from a second NF, one of a SM policy create request or a SM policy update request comprising a user location details corresponding to a user equipment (UE) associated with a user. The processing engine is configured to process, by the first NF, the user location details to determine whether the user loca¬tion details correspond to a throttle location details or a non-throttle location details. The processing engine is configured to transfer, by the first NF, one of the throttle location details or the non-throttle location details to a third NF to generate one of a set of throttle Access Point Name (APN) Aggerate Maximum Bit Rate (AMBR) values or a set of non- throttle APN AMBR values corresponding to the throttle location details or the non-throttle location details, respectively. The processing engine is configured to receive, by the first NF, one of the set of throttle APN AMBR values or the set of

non- throttle APN AMBR values from the third NF, in response to generating. The
processing engine is configured to send, by the first NF to the second NF, the set of
throttle APN AMBR values or the set of non- throttle APN AMBR values for managing
the throttling operations corresponding to the UE.
5
[0019] In some embodiment, the processing engine is further configured to set, by the
third NF, at least one of a user location and a plurality of SM create attributes based on
the throttle location details corresponding to the UE. The processing engine is further
configured to evaluate, by the third NF, a policy based on matching of a plurality of
10 network conditions with the plurality of SM create attributes in response to setting. The
processing engine is further configured to generate, by the third NF, a SM create policy
answer comprising the set of throttle APN AMBR values based on the evaluation. The
processing engine is further configured to send, by the third NF, the SM create policy
answer comprising the set of throttle APN AMBR values to the third NF.
15
[0020] In some embodiments, the processing engine is further configured to set, by the
third NF, at least one of a user location and a plurality of SM update attributes based on the non-throttle location details corresponding to the UE. The processing engine is further configured to evaluate, by the third NF, a policy based on matching of the plu-20 rality of network conditions with the plurality of SM update attributes in response to setting. The processing engine is further configured to generate, the third NF, a SM update policy answer comprising the set of non-throttle APN AMBR values based on the evaluation. The processing engine is further configured to send, by the third NF, the SM update policy answer comprising the set of non-throttle APN AMBR values to 25 the third NF.
[0021] In some embodiments, the processing engine is further configured to apply, by the second NF, a first set of rules along with the set of throttle APN AMBR values for implementing a pre-defined data transfer rate on the UE based on the throttle location 30 details when the user moves into a throttle location from a non-throttle location.
7

[0022] In some embodiments, the processing engine is further configured to applying, by the second NF, a second set of rules along with the set of non-throttle APN AMBR values for implementing a normal data transfer rate on the UE based on the non- throttle 5 location details, when the user moves into the non-throttle location from the throttle location.
[0023] In yet another embodiment, a user equipment (UE) communicatively coupled to a system. The UE is configured to send a user location details associated with the 10 UE to the system. The user location details correspond to one of a throttle location details and a non-throttle location details. The UE is configured to receive data at one of a pre-defined data transfer rate or a normal data transfer rate from the system in response to sending the user location details.
15 [0024] Other objects and advantages of the present disclosure will be more apparent from the following description, which is not intended to limit the scope of the present disclosure.
20 BRIEF DESCRIPTION OF THE DRAWINGS
[0025] The accompanying drawings, which are incorporated herein, and con-
stitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts through¬out the different drawings. Components in the drawings are not necessarily to scale,
25 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 elec¬trical components, electronic components or circuitry commonly used to implement
30 such components.
8

[0026] FIG. 1A illustrates an exemplary architecture configured for managing throt¬tling operations in a network, in accordance with an embodiment of a present disclo¬sure. 5
[0027] FIG. 1B illustrates an exemplary block diagram of a system configured for man¬aging throttling operations in a network, in accordance with an embodiment of the pre¬sent disclosure.
10 [0028] FIG. 2 illustrates a detailed exemplary flowchart of a method of managing throt-tling operations in a network, in accordance with an embodiment of the present disclo¬sure.
[0029] FIG. 3 illustrates a flow diagram of a method for managing throttling operations 15 in a network, in accordance with an embodiment of the present disclosure.
[0030] FIG. 4 illustrates an exemplary block diagram of a computer system in which or with which embodiments of the present disclosure may be implemented, in accord¬ance with an embodiment of the present disclosure. 20
[0031] Although the specific features of the present invention are shown in some draw¬ings and not in others. This is done for convenience only as each feature may be com¬bined with any or all of the other features in accordance with the present invention.
LIST OF REFERENCE NUMERALS 25 100A – Network architecture 102 – User Equipment (UE) 104 – Radio Access Network 106 – A User Plane Function (UPF) 108 – A Destination Number (DN)
9

110 – A Network Slice Selection Function (NSSF)
112 – An Authentication Server Function (AUSF)
114 – A Unified Data Management (UDM)
116 – An access and mobility management function (AMF) 5 118 – A session management function (SMF)
120 – A policy Control function (PCF)
122 – An Application Function (AF)
100B – An exemplary Block Diagram
124 – A system 10 126 – A repository
400 – Computer system
410 – External Storage Device
420 – Bus
430 – Main Memory 15 440 – Read Only Memory
450 – Mass Storage Device
460 – Communication Port
470 – Processor
20 DETAILED DESCRIPTION OF THE EMBODIMENTS
[0032] In the following detailed description, a reference is made to the accompanying drawings that form a part hereof, and in which the specific embodiments that may be practiced is shown by way of illustration. These embodiments are described in suffi-25 cient detail to enable those skilled in the art to practice the embodiments and it is to be understood that other changes may be made without departing from the scope of the embodiments. The following detailed description is therefore not to be taken in a lim¬iting sense.
10

[0033] 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 5 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 prob¬lems discussed above might not be fully addressed by any of the features described herein.
10
[0034] The ensuing description provides exemplary embodiments only, and is not in-tended 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
15 understood that various changes may be made in the function and arrangement of ele-ments without departing from the spirit and scope of the invention as set forth.
[0035] 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
20 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
25 obscuring the embodiments.
[0036] Also, it is noted that individual embodiments may be described as a process which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure dia¬gram, or a block diagram. Although a flowchart may describe the operations as a se-30 quential process, many of the operations can be performed in parallel or concurrently.
11

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 corre-5 spond to a return of the function to the calling function or the main function.
[0037] 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 de-10 scribed herein as “exemplary” and/or “demonstrative” is not necessarily to be con¬strued 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 15 terms are intended to be inclusive in a manner similar to the term “comprising” as an open transition word without precluding any additional or other elements.
[0038] Reference throughout this specification to “one embodiment” or “an embodi-ment” or “an instance” or “one instance” means that a particular feature, structure, or
20 characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one
25 or more embodiments.
[0039] The terminology used herein is for the purpose of describing particular embod¬iments only and is not intended to be limiting of the invention. As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, 30 unless the context clearly indicates otherwise. It will be further understood that the
12

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 5 term “and/or” includes any and all combinations of one or more of the associated listed items.
[0040] The various embodiments of the present technology provide a system and a method for managing throttling operations in a network. In particular, the present tech-10 nology provides the system and the method that performs a throttling operation on Ac¬cess Point Name (APN) Aggregate Maximum Bit Rate (AMBR) values, when a user moves into a Tracking Area Location (TAL) (i.e., a throttle location). The present tech¬nology facilitates to efficiently manage network resources by allocating and controlling maximum data transfer rate. The present technology facilitates to prevent network con-15 gestion/outages and provides a smooth overall network experience. The present tech¬nology facilitates re-attaching to the network when the user comes out of the throttled location to experience a normal data transfer rate (e.g., a basic data transfer rate appli¬cable to a user equipment (UE) of the user). The present technology facilitates ensuring that network services like audio calls or video calls are not affected due to throttling 20 (also known as bandwidth throttling). The system and method use a tracking mecha¬nism, which constantly monitors a location of the user and associated policy rules. When the user moves into a specific Tracking Area Location (TAL), where throttling is enforced by an operational requirement, then the system may modify the APN AMBR values associated with the UE of the user without affecting other network ser-25 vices. Further, no re-attaching service to the network may be required to throttle or throttle back session rules corresponding to the UE.
[0041] FIG. 1A illustrates an exemplary architecture 100A configured for
managing throttling operations in a network, in accordance with an embodiment of the present disclosure. For example, the network may correspond to a Fourth Generation
13

(4G) core access network, a Fifth Generation (5G) core access network, a Sixth Generation (6G) core access network, advanced generation network and the like. As will be appreciated, for ease of explanation, the 5G core access network is used. The 5G core access network may include an access network (AN) connected to a 5G core 5 network. The AN may include a Next Generation Radio Access Network (NG-RAN, also referred to as RAN) and/or a non-3rd Generation Partnership Project (non-3GPP) AN. For example, the 5G core network may be connected to one or more the access networks, e.g., the NG-RAN and/or the non-3GPP AN. The 5G core network may include one or more functional elements or network functions and one or more 10 interfaces may be used for communication between the functional elements and/or the network elements.
[0042] In an example, a network function may be a processing function in a
network, which may have a functional behavior and/or interface. The network
15 functions may be implemented as the network elements on dedicated hardware and/or network nodes, or as software instances running on dedicated hardware and/or shared hardware, or as virtual functions instantiated on a suitable platform. In an example, an access and mobility management function (AMF) 116 may provide transport for session management (SM) messages between a UE 102 and a session management
20 function (SMF) 118, transparent proxy for routing the SM messages, an access authentication, an access authorization, providing transport for the SM messages between the UE 102 and the SMF 118, a security anchor function (SEAF), interaction with an authentication server function (AUSF) 112 and the UE 102, receiving intermediate keys established as a result of the UE 102 authentication procedure,
25 receiving a security context management (SCM) from the SEAF for deriving keys specific to the AN, etc.
[0043] In an example, the AMF 116 may support a non-3GPP access network
over an N2 interface with a non-3GPP interworking function (N3IWF), a non-access
14

stratum (NAS) signaling with the UE 102 over the N3IWF, an authentication, a mobility management, authentication of UEs (e.g., the UE 102) connected over the N3IWF, and individual security context states of the UE 102 connected via the non-3GPP AN or via both the non-3GPP AN or the NG-RAN, coordinated resource 5 management contexts in effect over the NG-RAN and the non-3GPP AN, configuration management (CM) management context for the UE 102 for connectivity over the non-3GPP AN, and so on. In an example, the AMF 116 may include one or more AMFs. The AMFs may include some AMFs that serve a given area and/or network slice.
10 [0044] In an example, the SMF 118 may include one or more of the following
functions: SM details (e.g., a session establishment, a modification, and a release, including tunnel maintenance between a user plane function (UPF) 106 and a unified data management (UDM) 114, the UE 102 IP address allocation and management (including optional authorization), a selection and a control of the UPF 106,
15 configuring traffic steering at the UPF 106 to route traffic to appropriate destinations, terminating interfaces to policy control functions, controlling part of a policy enforcement and a Quality of Services (QoS), a lawful interception (for SM events and interfaces to lawful intercept systems), terminating SM part of non-access stratum (NAS) messages, a downlink data notification, initiating AN-specific SM information,
20 sending to a radio access network (RAN) 104 through a N2 via the AMF 116, determining a sub-system controller (SSC) mode of a session, roaming functions, handling local enforcement to apply QoS service level agreements (SLAs) related to a virtual public land mobile network (VPLMN), charging data collection and charging interfaces related the VPLMN, a lawful interception (in VPLMN, for the SM events
25 and interfaces to the lawful intercept systems), supporting interaction with an external destination number (DN) 108 to transport signaling to a packet data unit (PDU) session authorization/authentication by the DN 108, and so on.
[0045] In an example, the UPF 106 may include one or more of the following
15

functions: anchor points for an intra/inter Radio Access Technology (RAT) movement (as applicable), external PDU session points interconnected to the DN 108, a packet routing and forwarding, a packet inspection and user plane components for a policy rule enforcement, a lawful interception (i.e. a user plane acquisition), a traffic usage 5 reporting, an uplink classifier to support routing traffic flows for data networks, branch points to support multi-homed PDU sessions, QoS handling for the user plane, an uplink traffic validation, a transport level packet marking in an uplink and a downlink, a downlink packet buffering, downlink data notification triggers, etc.
10 [0046] In an example, the UE 102 IP address management may include
allocation and release of the UE 102 IP addresses and/or updates of allocated internet protocol (IP) addresses. The UE 102 may set the requested PDU type during the PDU session setup procedure based on its IP stack capabilities and/or configuration. In an example, the SMF 118 may select a PDU type for a PDU session. In an example, if the
15 SMF 118 receives a request that the PDU type be set to an IP, the SMF 118 may select the PDU type to be an Internet Protocol version 4 (IPv4) or an Internet Protocol version 6 (IPv6) based on a Data Network Name (DNN) configuration and/or an operator policy. In an example, the SMF 118 may provide a cause value to the UE 102 to indicate whether other IP versions are supported on the DNN. In an example, if the SMF 118
20 receives a request that the PDU type be the IPv4 or the IPv6, and the requested IP version is supported by the DNN, the SMF 118 may select the requested PDU type.
[0047] In an example, a Policy Control Function (PCF) 120 may support a
unified policy framework to control network behavior, provide policy rules for control
25 plane functions to execute policy rules, implement a front end to an access policy decision related subscription information in a User Data Repository (UDR), and so on. A network exposure function (NEF) may provide a means to securely expose services and capabilities provided by 3GPP network functions, translate between information exchanged with an Application Function (AF) 122 and an information exchanged with
30 internal network functions, receive information from other network functions, and so
16

on. The PCF 120 includes one or more processors and memory storing instructions that, when executed by the one or more processors perform steps of setting at least one of a user location and a set of SM create attributes based on the user location details and transferring to a Policy Control Function-Symmetrical Multiprocessing (PCF-5 SMP) and sending to the SMF 118, a SM create policy answer with a set of throttle Access Point Name (APN) Aggregate Maximum Bit Rate (AMBR) values, upon the user moving into the throttle location. The SMF 118 includes one or more processors and memory storing instructions that, when executed by the one or more processors perform the steps of sending to the PCF 120, a session management (SM) policy create
10 request and providing a user location details (i.e., a throttle location details) including a set of throttle APN AMBR values, and when a user moves into a non-throttle location and sending to the PCF 120 a SM policy update request including updated location details (i.e., a non-throttle location details) with a set of non-throttle APN AMBR values associated with the UE 102 of the user when the user moves into the non-throttle
15 location.
[0048] In an example, a network repository function (NRF) may support a
service discovery function that may receive network function discovery requests from network function instances, provide information to the network function instances
20 about discovered network function instances (to be discovered), and maintain information about available network function instances and their supported services, among other things. In an example, a Network Slice Selection Function (NSSF) 110 may select a set of network slice instances for serving the UE 102 and may determine an allowed Network Slice Selection Assistance Information (NSSAI). In an example,
25 the NSSF 110 may determine the AMFs (e.g., one or more AMFs of the AMF 116) to be used to serve the UE 102 and/or, based on the configuration, determine a list of the AMFs by querying the NRF.
[0049] In an example, data stored in the UDR can include at least one of a user
17

subscription data, including at least subscription identifiers, security credentials, an
access and mobile related subscription data, a session related subscription data, a policy
data, and the like. In an example, the AUSF 112 may support an authentication server
function.
5
[0050] In an example, the AF 122 may interact with a 3GPP core network to
provide services. In an example, based on an operator deployment, an application
functionality may be trusted by an operator to interact directly with related network
functionality. In an embodiment, AFs that the operator does not allow direct access to
10 the network functions may interact with the relevant network functions using an
external exposure framework (e.g., via the NEF).
[0051] In an example, a control plane interface between the (R)AN 104 ((R)AN
may refer to the AN or the RAN) and the 5G core network may support connecting a
15 number of different types of ANs for untrusted access to the 5G core network via control plane protocols. In an example, the NAS protocol may be used for both the NF-RAN and the non-3GPP access network. In an example, the control plane interface between the (R)AN 104 and the 5G core network may support decoupling between the AMF 116 and other functions (such as the SMF 118) that may need to control the
20 services supported by the AN (e.g., control of user plane resources in the AN for the PDU session). In an example, the 5G core network may provide a policy information from the PCF 120 to the UE 102. In an example, the policy information may include an access network discovery and selection policies, routing policies (i.e., User-Defined Routing Selection Policies (URSPs)) corresponding to the UE 102, sub-System
25 Controller (SSC) mode selection policies (sscmscsps), network slice selection policies (NSSPs), DNN selection policies, non-seamless offload policies, and the like. In an example, a registration manager may be used to register or de-register the UE 102 in the network and establish a user context in the network. A connection management may be used to establish and release signaling connections between the UE 102 and
30 the AMF 116.
18

[0052] In an example, the UE 102 may register on the network to receive a
service requesting registration. In an example, the UE 102 may periodically update its registration on the network in order to maintain reachability (periodic registration 5 update), or update on the move (e.g., mobile registration update), or update its capabilities or renegotiate protocol parameters.
[0053] According to an embodiment, the system and the method provide an
operational feature that aims to enforce restrictions on APN AMBR values that are used
10 to limit the maximum data transfer rate for a subscriber (i.e., the user) based on specific geographical areas. When a user moves to service area locations where bandwidth available on a control plane is low, then the PCF 120 may take an appropriate action to throttle the bandwidth of the user. Throttling the bandwidth of the user facilitates the management of network resources and ensures fair usage among subscribers. When the
15 user comes out of the throttled area, the PCF 120 may push back normal non-throttle APN AMBR values.
[0054] According to an embodiment, the system and the method use a tracking
mechanism, which constantly monitors the user's location and associated policy rules.
20 When the user moves into the specific TAL (i.e., the throttle location), where throttling is to be enforced by an operational requirement, then the PCF 120 may modify the APN AMBR values without affecting other network services. Further, no re-attach to the network may be required to throttle or throttle back session rules. In an embodiment, examples of the policy rules may include, but are not limited to, a location-based
25 throttling rule, a real-time session throttling rule, a time-based access restriction rule, and the like. By way of an example, when the location-based throttling rule including a policy for reducing an internet speed is applied on a certain TAL area, then when the user enters the TAL area (i.e., a throttle location), then an internet speed may be reduced to 2 Megabits per second (Mbps). By way of another example, when the real-19

time session throttling rule associated with a policy for internet usage limit for a session is applied on a certain TAL area, then if the internet usage of the UE 102 associated with the user exceeds a current session limit, (e.g., 1 Gigabyte), then the internet speed for the UE 102 is reduced for 1 Mbps. By way of an example, when the time-based 5 access restriction rule including a policy for limiting video streaming service bandwidth between 8 PM and 10 PM daily is applied on a certain TAL area, then the video streaming service bandwidth for all UEs in the TAL area may be reduced to 3 Mbps for all the UEs.
10 [0055] In an embodiment, in order to perform one or more operations discussed
above for managing the throttling operation in the network (e.g., the 5G core access network), the UE 102 may be in communication with the (R)AN 104. Further, the UE 102 may interact with the AMF 116 via an interface N1 or through the (R)AN 104 via an interface N2 and vice versa. Further, the UPF 106 may interact with the AMF 116
15 via an interface N3 or through the (R)AN 104 and vice versa. One or more UPFs may interact with each other via an interface N9. Further, the DN 108 may interact with the UPF 106 via an interface N6 and vice versa. The UPF 106 may interact with the SMF 118 via an interface N4 and vice versa. The SMF 118 may interact with the AMF 116 via an interface N11 and with the PCF 120 via an interface N7 and vice versa. The
20 SMF 118 may further interact with the UDM 114 via an interface N10 and vice versa. The PCF 120 may interact with the AMF 116 via an interface N15 and with the AF 122 via an interface N5 and vice versa. One or more AMFs may interact with each other via an interface N14. The UDM 114 may interact with the AMF 116 via an interface N8 and with the AUSF 112 via an interface N13 and vice versa. The AUSF
25 112 may interact with the AMF 116 via an interface N12 and vice versa. The NSSF 110 may interact with the AMF 116 via an interface N22 and vice versa. A technique for managing the throttling operations is further explained in detail in conjunction with FIGS. 1A – 3. In examples, the N1 Interface may be between the UE and the AMF 116 and may handle communication related to access and mobility management. The
20

N7 interface connects the SMF 118 to the PCF 120 and allows the SMF 118 and the PCF 120 to exchange control plane signaling messages. The N10 interface may connects the UDM 114 and the SMF 118 and facilitates policy control and session management. The N11 interface links the AMF 116 and the SMF 118 and is used for 5 communication between the AMF 116 and the SMF 118. In aspects, the N12 interface is between the AMF 116 and the AUSF 112 and handles authentication-related tasks. The N13 Interface connects the UDM 114 and the AUSF 112 and is used in authentication and security functions. The N15 Interface is used in roaming and non-roaming scenarios.
10
[0056] In a non-roaming scenario, the N15 interface links the PCF 120 and the
AMF 116. In a roaming scenario, the N15 interface connects the Visited PCF (vPCF) in the visited network to the AMF 116 in the home network. The N22 Interface is between the SMF 118 and the NSSF 110 and supports network slicing and slice
15 selection.
[0057] FIG. 1B illustrates an exemplary block diagram 100B of a system 124
configured for managing throttling operations in a network, in accordance with an embodiment of the present invention. FIG. 1B is explained in conjunction with FIG.
20 1A. The disclosed system 124 facilitates efficient management of network resources by allocating and controlling maximum data transfer rate, prevent network congestion/outages, and providing a smooth overall network experience. Further, the disclosed system 124 avoids a re-attach to the network when the user comes out of the throttled location to experience a normal data transfer rate. Furthermore, the disclosed
25 system 124 ensures that other network services like audio calls or video calls are not affected during the throttling operation.
[0058] In particular, the system 124 is configured for enforcing the throttling
operation by modifying the APN AMBR values corresponding to a UE (e.g., the UE
21

102). The system 124 includes the AMF 116. The AMF 116 is configured to continuously communicate with the UE 102 via the interface N1. In other words, the AMF 116 continuously monitors a user location of the UE 102 associated with the user. Further, based on the monitoring, the AMF 116 is configured to retrieve a user location 5 details associated with the UE 102. The user location details may include, geographical coordinates, a cell identified (ID), a cell sector, a service area, a tracking area, a network identifier, location-based services, and the like. Further, the AMF 116 may send the user location details to the SMF 118 via the interface N11. Upon receiving the user location details, the SMF 118 is configured to send one of the SM policy create request 10 or the SM policy update request including the user location details corresponding to the UE 102 to the PCF 120 via the interface N7.
[0059] Further, the PCF 120 may process the user location details to determine
whether the user location details correspond to the throttle location details or the non-15 throttle location details. For determining, the PCF 120 is configured to access a repository 126 (e.g., the UDR). Further, the PCF 120 is configured to transfer one of the throttle location details or the non-throttle location details to a Policy Control Function Symmetrical multiprocessing (PCF-SMP). In some embodiments, the PCF-SMP may be implemented within the PCF 120. The throttle location details, or the non-20 throttle location details may be transferred to the PCF-SMP to generate one of the set of APN AMBR values or the set of non- throttle APN AMBR values corresponding to the throttle location details or the non-throttle location details, respectively. Further, the PCF 120 may receive the of the set of throttle APN AMBR values or the set of non-throttle APN AMBR values from the PCF-SMP, in response to generating. The PCF 25 120 may then send the set of throttle APN AMBR values or the set of non- throttle APN AMBR values to the SMF 118 for managing the throttling operations corresponding to the UE 102 via the AMF 116.
[0060] In one embodiment, when the SMF 118 receives the set of throttle APN
22

AMBR values, the SMF 118 is configured to apply a first set of rules along with the set of throttle APN AMBR values for implementing a pre-defined data transfer rate (e.g., a reduced data transfer rate, such as 1-10 Megabit per second (Mbps)) on the UE 102 based on the throttle location details when the user moves into the throttle location 5 from the non-throttle location. As will be appreciated, the throttle location refers to a location where a data transfer rate, i.e., the pre-defined data transfer rate (e.g., the bandwidth or an internet speed) is intentionally reduced or limited by an Internet Service Provider (IPS). Further, the non-throttle location refers a location where the data transfer rate is not intentionally restricted by the IPS. In case of the non-throttle 10 location, the data transfer rate corresponds to a normal data transfer rate.
[0061] The first set of rules may include, limiting amount of data, the user
associated with the UE 102 can consume at high speeds once the user exceeds a certain data threshold, e.g., 70%, reducing a data transfer rate if the user exceeds a predefined 15 data limit (2 Gigabyte (GB)) within a certain period (1 day), giving higher priority to real-time applications like voice calls or video conferencing than non-real-time applications like file downloads or software updates, and the like. In another embodiment, when the SMF 118 receives the set of non-throttle APN AMBR values, the SMF 118 is configured to apply a second set of rules along with the set of non-20 throttle APN AMBR values for implementing a normal data transfer rate, i.e., the basic data transfer rate (e.g., 150 Mbps) on the UE 102 based on the non-throttle location details when the user moves into the non-throttle location from the throttle location. The second set of rules may include a standard service level, a latency requirement, a service restoration time, a coverage obligation, and the like. This is further depicted 25 and explained in FIG. 2 and FIG. 3.
[0062] FIG. 2 illustrates a detailed exemplary flowchart 200 for managing
throttling operations in a network, in accordance with an embodiment of the present disclosure. FIG. 2 is explained in conjunction with FIG. 1A and 1B.
23

[0063] In one embodiment, when the user moves into the TAL, i.e., a throttling
location 204, a throttling of the APN AMBR values is carried out using below mentioned steps. 5
[0064] Initially, at step 206, the PCF 120 receives the SM policy create request
corresponding to a UE (same as the UE 102) from the SMF 116. The SM policy create request may include the user location details. The user location details may include, the geographical coordinates, the cell identified (ID), a cell sector, a service area, a tracking
10 area, a network identifier, location-based services, and the like. Further, the PCF 120 may process the user location details to determine the user location details may correspond to the throttle location details. In particular, in some embodiments, the SM policy create request received from the SMF 116 includes the throttle location details. Further, the PCF 120 transfers the throttle location details to a PCF-SMP 202. At step
15 208, the PCF-SMP 202 is configured to set at least one a user location (i.e., a current throttle location), and a plurality of SM create attributes based on the throttle location details corresponding to the UE 102. Examples of the plurality of SM create attributes includes, but are not limited to, a bandwidth allocation, a throttle trigger, a throttle severity, and a throttle bypass.
20
[0065] Further, at step 210, the PCF-SMP 202 evaluates a policy based on
matching of a plurality of network conditions with the plurality of SM create attributes in response to setting. Example of the policy may include an access network discovery and selection policy, a routing policy (i.e., the URSP) corresponding to the UE 102, an
25 SSC mode selection policy (sscmscsp), a NSSP, a DNN selection policy, a non-seamless offload policy, and the like. Examples of the plurality of network conditions includes, but are not limited to, congested networks, weather conditions, geographical challenges, network outages, network load balancing, security threats, and roaming. In addition, based on evaluation of the policy, at step 210, the SM create policy answer
24

including the set of throttle APN AMBR values may be send to the PCF 120. For example, the set of throttle APN AMBR values include a basic data plan with a downlink AMBR value of 1 Mbps, and an Uplink AMBR value of 2 Mbps, a fair usage policy with a downlink AMBR value of 3 Mbps during peak hours, 10 Mbps during 5 off-peak hours and an uplink AMBR value of 1 Mbps during peak hours, 5 Mbps during off-peak hours, and the like. At step 212, the PCF 120 sends the SM create policy answer including the set of throttle APN AMBR values to the SMF 116. The SMF 116 may apply the first set of rules along with the set of throttle APN AMBR values for implementing the pre-defined data transfer rate (e.g., 1-10 Mbps) on the UE 102. 10
[0066] In one embodiment, when the user moves into a non-throttling location
214, a throttling of the APN AMBR values is not carried and below mentioned steps are performed.
15 [0067] Initially, at step 216, the PCF 120 receives the SM policy update request
corresponding to the UE 102 from the SMF 116. The SM policy update request may include the user location details. Further, the PCF 120 may process the user location details to determine the user location details may correspond to the non-throttle location details. In particular, in some embodiments, the SM policy update request received
20 from the SMF 116 includes the non-throttle location details. Further, the PCF 120 may transfer the non-throttle location details to the PCF-SMP 202. At step 218, the PCF-SMP 202 is configured to set at least one of a user location (i.e., a current non-throttle location) and a plurality of SM update attributes based on the non-throttle location details corresponding to the UE 102. Example of the plurality of SM update attributes
25 may include, but are not limited to, a handover success rate, a session continuity, a service priority handling, a cell load balancing, and a location-based service optimization. Further, at step 220, the PCF-SMP 202 evaluates a policy based on matching of the plurality of network conditions with the plurality of SM update attributes in response to setting. In addition, based on evaluation of the policy, at step
25

220, the SM update policy answer including the set of non-throttle APN AMBR values may be send to the PCF 120. For example, the set of non-throttle APN AMBR values include a premium data plan with a downlink AMBR value of 100 Mbps, and an Uplink AMBR value of 100 Mbps, a fair usage policy with a downlink AMBR value of 50 5 Mbps during peak hours, 100 Mbps during off-peak hours and an uplink AMBR value of 10 Mbps during peak hours, and the like. At step 222, the PCF 120 may send the SM update policy answer including the set of non-throttle APN AMBR values to the SMF 116. The SMF 116 may apply the second set of rules along with the set of non-throttle APN AMBR values for implementing the normal data transfer rate (e.g., 500 10 Mbps) on the UE 102.
[0068] FIG. 3 illustrates a flow diagram 300 of a method for managing
throttling operations in a network, in accordance with an embodiment of the present invention. FIG. 3 is explained in conjunction with FIGS. 1A – 2. At step 302, one of
15 the SM policy create request or the SM policy update request including the user location details may be received by a first Network Function (i.e., the PCF 120) from a second NF (i.e., the SMF 116). The SM policy create request or the SM policy update request may be received corresponding to a UE (same as the UE 102) associated with the user. Further, at step 304, the user location details may be processed by the PCF
20 120 to determine whether the user location details correspond to the throttle location details or the non-throttle location details. Further, at step 306, one of the throttle location details or the non-throttle location details may be sent by the PCF 120 to a third NF (i.e., the PCF-SMP 202). The throttle location details or the non-throttle location details may be sent to generate one of the set of throttle APN AMBR values
25 or the set of non- throttle APN AMBR values corresponding to the throttle location details or the non-throttle location details, respectively. Further, at step 308, one of the set of throttle APN AMBR values or the set of non- throttle APN AMBR values may be received by the PCF 120 from the PCF-SMP 202, in response to generating. Furthermore, at step 310, the set of throttle APN AMBR values or the set of non-26

throttle APN AMBR values may be send by the PCF 120 to the SMF 116 for managing the throttling operations corresponding to the UE 102.
[0069] In particular, in one embodiment, when the user location details are
5 determined to the throttle location details, then the PCF-SMP 202 is configured to set at least one of the user location (i.e., the current throttle location) and the plurality of SM create attributes based on the throttle location details corresponding to the UE 102. In other words, based on the throttle location details (e.g., details including the geographical coordinates), the PCF-SMP 202 may determine and set the user location.
10 Once this is set, based on the geographical coordinates, the PCF-SMP 202 may determine and set the plurality of SM create attributes (e.g., the bandwidth allocation) for the UE 102. In particular, when the user moves from the non-throttle location to the throttle location, the PCF-SMP 202 may determine and set the user location and the plurality of SM create attributes corresponding to the UE 102 of the user. Further, the
15 PCF-SMP 202 evaluates the policy based on matching of the plurality of network conditions with the plurality of SM create attributes in response to setting. In other words, the PCF-SMP 202 is configured to evaluate and determine which policy (e.g., the routing policy) needs to be applied based on the throttle location details. For this, the PCF-SMP 202 matches the plurality of network conditions (e.g., the congested
20 network and the weather condition) with the plurality of SM create attributes (e.g., the bandwidth allocation). In addition, the PCF-SMP 202 may send the SM create policy answer including the set of throttle APN AMBR values to the PCF 120. Further, the PCF 120 may send the SM create policy answer including the set of throttle APN AMBR values to the SMF 116. The SMF 116 may apply the first set of rules along
25 with the set of throttle APN AMBR values for implementing the pre-defined data transfer rate (e.g., 1-10 Mbps) on the UE 102.
[0070] In another embodiment, when the user location details are determined
to be the non-throttling location details, the PCF-SMP 202 may be configured to set at
27

least one of the user location (i.e., the current non-throttle location) and the plurality of SM update attributes based on the non-throttle location details corresponding to the UE 102. In other words, based on the non-throttle location details (e.g., details including the geographical coordinates), the PCF-SMP 202 may determine and set the user 5 location. Once this is set, based on the geographical coordinates, the PCF-SMP 202 may determine and set the plurality of SM update attributes (e.g., the bandwidth allocation) for the UE 102. In particular, when the user moves out from the throttle location to the non-throttle location, the PCF-SMP 202 may determine and set the user location and the plurality of SM update attributes corresponding to the UE of the user.
10 Further, the PCF-SMP 202 may evaluate the policy based on matching of the plurality of network conditions with the plurality of SM update attributes in response to setting. In other words, the PCF-SMP 202 is configured to evaluate and determine which policy (e.g., the routing policy) needs be applied based on the non-throttle location details. For this, the PCF-SMP 202 matches the plurality of network conditions (e.g., the
15 congested network) with the plurality of SM update attributes (e.g., the bandwidth allocation). In addition, based on evaluation of the policy, the SM update policy answer including the set of non-throttle APN AMBR values may be send by the PCF-SMP 202 to the PCF 120. Further, the PCF 120 may send the SM update policy answer including the set of non-throttle APN AMBR values to the SMF 116. The SMF 116 may apply
20 the second set of rules along with the set of non-throttle APN AMBR values for implementing the normal data transfer rate (e.g., 50 Mbps) on the UE 102.
[0071] According to one embodiment of the present invention, when the user moves out of the throttle location, the PCF 120 provides the first set of rules to be applied for 25 implementation of the normal data transfer rate.
[0072] According to one embodiment of the present invention, when the user moves from the non-throttle location to the throttle location, the SMF 116 send the SM policy
28

create request and the PCF 120 provides flexibility to apply the set of throttle APN AMBR values according to a service area without affecting one or more other services.
[0073] According to one embodiment of the present invention, when the user moves
5 from the throttle location to the non-throttle location, the SMF 116 sends the SM policy
update request, and the PCF 120 provides flexibility to the set of non-throttle APN
AMBR values according to a service area without affecting one or more other services.
[0074] FIG.4 illustrates an exemplary block diagram of a computer system 400 in 10 which or with which embodiments of the present disclosure may be implemented, ac¬cording to an embodiment of the present disclosure. As shown in FIG. 4, the computer system 400 may include an external storage device 410, a bus 420, a main memory 430, a read-only memory 440, a mass storage device 450, communication port(s) 460, and a processor 470. A person skilled in the art will appreciate that the computer system 15 400 may include more than one processor and communication ports. The processor 470 may include various modules associated with embodiments of the present disclosure. The communication port(s) 460 may be any of an RS-232 port for use with a modem-based dialup connection, a 10/100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or other existing or future ports. The com-20 munication port(s) 460 may be chosen depending on a network, such a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system 400 connects.
[0075] The main memory 430 may be random access memory (RAM), or any other 25 dynamic storage device commonly known in the art. The read-only memory 440 may be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chips for storing static information e.g., start-up or Basic Input/Out¬put System (BIOS) instructions for the processor 470.
29

[0076] The mass storage device 450 may be any current or future mass storage solu¬tion, which can be used to store information and/or instructions. Exemplary mass stor¬age device 450 includes, but is not limited to, Parallel Advanced Technology Attach¬ment (PATA) or Serial Advanced Technology Attachment (SATA) hard disk drives or 5 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.
[0077] The bus 420 communicatively couples the processor 470 with the other 10 memory, storage, and communication blocks. The bus 420 may be, e.g., a Peripheral Component Interconnect (PCI)/PCI Extended (PCI-X) bus, Small Computer System Interface (SCSI), Universal Serial Bus (USB), or the like, for connecting expansion cards, drives, and other subsystems as well as other buses, such a front side bus (FSB), which connects the processor 470 to the computer system. 15
[0078] Optionally, operator and administrative interfaces, e.g., a display, keyboard, joystick, and a cursor control device, may also be coupled to the bus 420 to support direct operator interaction with the computer system. Other operator and administrative interfaces can be provided through network connections connected through the com-20 munication port(s) 460. Components described above are meant only to exemplify var¬ious possibilities. In no way should the aforementioned exemplary computer system limit the scope of the present disclosure.
[0079] While the foregoing describes various embodiments of the invention,
25 other and further embodiments of the invention may be devised without departing from the basic scope thereof. The scope of the invention is determined by the claims that follow. The invention is not limited to the described embodiments, versions or examples, which are included to enable a person having ordinary skill in the art to make and use the invention when combined with information and knowledge available to the
30

person having ordinary skill in the art.
[0080] Although the embodiments of the present invention are described with various specific embodiments, it will be obvious for a person skilled in the art to practice the 5 embodiments of the present invention with modifications.
[0081] The present disclosure provides technical advancement related to throttling op-erations in the network (i.e., the telecommunication network). This advancement ad¬dresses the limitations of existing solutions by applying APN AMBR values based on 10 the user location details. The disclosure involves generating the SM create policy an¬swer including the set of throttle APN AMBR values or the SM update policy answer including the set of non-throttle APN AMBR values based on the evaluation of the policy. This may enable efficient management of the network resources by allocating and controlling maximum data transfer rate. Further, the present disclosure allows re-15 attaching the UE to the network when the user comes out of the throttled location to experience the normal data transfer rate. As a result, the present disclosure helps pre¬vent dissatisfaction among the users as other network services such as, audio calls, video calls, and the like, are not affected during the throttling operation.
20
ADVANTAGES OF THE PRESENT DISCLOSURE
[0082] The present disclosure provides a system and a method that performs a throt¬tling operation on APN AMBR values, when a user moves into a throttle service area 25 location (i.e., the throttle location).
[0083] The present disclosure provides a system and a method that efficiently manage network resources by allocating and controlling maximum data transfer rate.
31

[0084] The present disclosure provides a system and a method that prevent network congestion/outages and provide smoother overall network experience to users (e.g., subscribers).
5 [0085] The present disclosure provides a system and a method that forgo re-attaching to a network when a user comes out of a throttled location to experience normal data transfer rate.
[0086] The present disclosure provides a system and a method that does not affect other 10 network services such as, audio calls, video calls, and the like, during the throttling operation to avoid dissatisfaction among the users.
32

We Claim:
1. A method (300) for managing throttling operations in a network, the method (300) comprising:
receiving (302), by a first Network Function (NF) from a second NF, one of a SM policy create request or a SM policy update request comprising a user location details corresponding to a user equipment (UE) associated with a user;
processing (304), by the first NF, the user location details to determine whether the user location details correspond to a throttle location details or a non-throttle location details;
transferring (306), by the first NF, one of the throttle location details or the non-throttle location details to a third NF to generate one of a set of throttle Access Point Name (APN) Aggerate Maximum Bit Rate (AMBR) values or a set of non- throttle APN AMBR values corresponding to the throttle location details or the non-throttle location details, respectively;
receiving (308), by the first NF, one of the set of throttle APN AMBR values or the set of non- throttle APN AMBR values from the third NF, in re-sponse to generating; and
sending (310), by the first NF to the second NF, the set of throttle APN AMBR values or the set of non- throttle APN AMBR values for managing the throttling operations corresponding to the UE (102).
2. The method (300) as claimed in claim 1, further comprising:
setting, by the third NF, at least one of a user location and a plurality of SM create attributes based on the throttle location details corresponding to the UE (102);

evaluating, by the third NF, a policy based on matching of a plurality of network conditions with the plurality of SM create attributes in response to set¬ting;
generating, by the third NF, a SM create policy answer comprising the set of throttle APN AMBR values based on the evaluation; and
sending, by the third NF, the SM create policy answer comprising the set of throttle APN AMBR values to the first NF.
3. The method (300) as claimed in claim 1, further comprising:
setting, by the third NF, at least one of a user location and a plurality of SM update attributes based on the non-throttle location details corresponding to the UE (102);
evaluating, by the third NF, a policy based on matching of the plurality of network conditions with the plurality of SM update attributes in response to setting;
generating, the third NF, a SM update policy answer comprising the set of non-throttle APN AMBR values based on the evaluation; and
sending, by the third NF, the SM update policy answer comprising the set of non-throttle APN AMBR values to the first NF.
4. The method (300) as claimed in claim 1, further comprising:
applying, by the second NF, a first set of rules along with the set of throttle APN AMBR values for implementing a pre-defined data transfer rate on the UE (102) based on the throttle location details when the user moves into a throttle lo¬cation from a non-throttle location.
5. The method (300) as claimed in claim 4, further comprising:
applying, by the second NF, a second set of rules along with the set of non-throttle APN AMBR values for implementing a normal data transfer rate on the UE

(102) based on the non-throttle location details when the user moves into the non-throttle location from the throttle location.
6. A system (124) for managing throttling operations in a network, the system (124) comprising:
a memory; and
a processing engine communicatively coupled to the memory, config-ured to:
receive (302), by a first Network Function (NF) from a second NF, one of a SM policy create request or a SM policy update request comprising a user location details corresponding to a user equipment (UE) (102) associated with a user;
process (304), by the first NF, the user location details to deter-mine whether the user location details correspond to a throttle location details or a non-throttle location details;
transfer (306), by the first NF, one of the throttle location details or the non-throttle location details to a third NF to generate one of a set of throttle Access Point Name (APN) Aggerate Maximum Bit Rate (AMBR) values or a set of non- throttle APN AMBR values correspond¬ing to the throttle location details or the non-throttle location details, respectively;
receive (308), by the first NF, one of the set of throttle APN AMBR values or the set of non- throttle APN AMBR values from the third NF, in response to generating; and
send (310), by the first NF to the second NF the set of throttle APN AMBR values or the set of non- throttle APN AMBR values for managing the throttling operations corresponding to the UE (102).

7. The system (124) as claimed in claim 6, wherein the processing engine is further
configured to:
set, by the third NF, at least one of a user location and a plurality of SM create attributes based on the throttle location details corresponding to the UE (102);
evaluate, by the third NF, a policy based on matching of a plurality of network conditions with the plurality of SM create attributes in response to set¬ting;
generate, by the third NF, a SM create policy answer comprising the set of throttle APN AMBR values based on the evaluation; and
send, by the third NF, the SM create policy answer comprising the set of throttle APN AMBR values to the first NF.
8. The system (124) as claimed in claim 6, wherein the processing engine is further
configured to:
set, by the third NF, at least one of a user location and a plurality of SM update attributes based on the non-throttle location details corresponding to the UE (102);
evaluate, by the third NF, a policy based on matching of the plurality of network conditions with the plurality of SM update attributes in response to setting;
generate, the third NF, a SM update policy answer comprising the set of non-throttle APN AMBR values based on the evaluation; and
send, by the third NF, the SM update policy answer comprising the set of non-throttle APN AMBR values to the first NF.
9. The system (124) as claimed in claim 6, wherein the processing engine is further
configured to:

apply, by the second NF, a first set of rules along with the set of throttle APN AMBR values for implementing a pre-defined data transfer rate on the UE (102) based on the throttle location details when the user moves into a throt¬tle location from a non-throttle location.
10. The system (124) as claimed in claim 9, wherein the processing engine is further
configured to:
apply, by the second NF, a second set of rules along with the set of non-throttle APN AMBR values for implementing a normal data transfer rate on the UE (102) based on the non-throttle location details when the user moves into the non-throttle location from the throttle location.
11. A user equipment (UE) (102) communicatively coupled to a system (124),
wherein the UE (102) is configured to:
send a user location details associated with the UE (102) to the system (124), wherein the user location details correspond to one of a throttle location details and a non-throttle location details; and
receiving data at one of a pre-defined data transfer rate or a normal data transfer rate from the system (124), in response to sending the user location details.