FORM 2
THE PATENTS ACT, 1970
THE PATENTS RULES, 2003
COMPLETE SPECIFICATION
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, 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.
TECHNICAL FIELD
[0002] The present disclosure generally relates to a means to improve efficiency of operation of a communication network. In particular, the present disclosure relates to a system and a method for implementing barring policies on subscribers/users of a network.
BACKGROUND OF THE INVENTION
[0003] The following description of related art may be 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.
[0004] Wireless communication technology has rapidly evolved over the past few decades. The first generation of wireless communication technology was analog technology that offered only voice services. Further, when the second-generation (2G) technology was introduced, text messaging and data services became possible. The 3G technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth generation

(4G) technology revolutionized the wireless communication with faster data speeds, improved network coverage, and security. Currently, the fifth generation (5G) technology is being deployed, with even faster data speeds, low latency, and the ability to connect multiple devices simultaneously. The third generation partnership project (3GPP) involves handling of an evolved packet core (EPC) and a fifth-generation core (5GC) interworking.
[0005] Regulatory barring policy may be implemented by sending a location change information to a network function, such as a converged policy control function (PCF) from a session management function (SMF) through an update message. Based on the information received in the update message, the policy control function may install barring policies and remove non-barring policies on the running sessions based on the predefined policy engine configuration. However, this may increase incoming traffic at the network function, particularly if subscribers are detached-attached from the SMF to get new policies from the converged PCF. Further, this may result in increased network traffic since a number of SMF node counts is always high as compared to a number of centralized converged PCF nodes in the network. Furthermore, the load on the network function may be exacerbated when subscribers detach-attach from the SMF by manual commands. The high traffic may overload the converged PCF and the network.
[0006] There is, therefore, a requirement in the art to provide a system and a method implement barring policy for the subscribers without overloading the network due to increased traffic.
DEFINITION
[0007] 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.
[0008] The term DPI as used herein, refers to a deep packet inspection. The

DPI provides a real-time network visibility and real-time application awareness from the core to the edge and across all layers and nodes within the network.
[0009] The term SMF as used herein, refers to a session management function. The SMF is responsible for establishing, maintaining, and terminating user sessions in the 5G core network.
[0010] The term CHF as used herein, refers to a charging function. The CHF is deployed to the network side to complete the billing function.
[0011] The term BSF as used herein, refers to a binding support function. The BSF allows policy control function (PCF) to register, update, and remove the binding information from it, and allows network function (NF) consumers to discover the selected PCF.
[0012] The term NRF as used herein, refers to a network repository function. The NRF works as a centralized repository for all the 5G network functions (NFs) in the operator’s network.
[0013] The term AMF as used herein, refers to an access and mobility management function. The AMF manages the control plane of the 5G network, which is responsible for signalling and network management.
[0014] The term PCF as used herein, refers to a policy control function. The PCF provides policies for control plane functions. This includes network slicing, roaming and mobility management.
[0015] The term PCRF as used herein, refers to a policy and charging rules function. The PCRF is a node designated in real-time to determine policies in a multimedia network.

[0016] The term AF as used herein, refers to an application function. The AF plays a key role in traffic management and QoS assignments, through interaction with the policy elements.
[0017] The term OCS as used herein, refers to an online charging system. The OCS is a system allowing a communications service provider to charge their customers, in real time, based on service usage.
[0018] The term PGW as used herein, refers to a packet data network gateway. The PGW acts as the interface between the LTE network and other packet data networks.
[0019] The term NMS as used herein, refers to a network management system. The NMS is a server that runs a network management application. Network elements communicate with the NMS to relay management and control information.
[0020] The term SPR as used herein, refers to a subscriber profile repository. The SPR is a logical database which contains subscriber related information related to policy and charging control.
[0021] The term PGW-C as used herein, refers to a packet data network gateway control plane. The PGW-C is responsible for controlling the data plane functionality of the PGW.
[0022] The term ‘Gx’ as used herein, refers to a Gx Interface that acts as a reference point between the PCRF and a Policy and Charging Enforcement Function (PCEF) in Long-Term Evolution (LTE) networks used to exchange policy and charging rules.
[0023] The term converged PCF as used herein, refers to a combination of the

PCF and the PCRF into a single entity. This convergence streamlines policy control, session management, and charging functions, eliminating the need for separate entities, and simplifying network architecture. By integrating policy control and charging rules, the converged PCF facilitates dynamic policy enforcement, real¬time charging, and seamless subscriber management, enabling efficient resource utilization and enhanced service delivery in the network.
[0024] The term barring policies as used herein, refers to the barring policies are essential rules and regulations set by network operators to manage access to network resources efficiently. These policies ensure fair usage of network capacity, prioritize critical services, and maintain network security. Through access control, Quality of Service (QoS) management, traffic control, and security enforcement, barring policies enable operators to optimize network performance, safeguard against potential threats, and deliver a reliable and high-quality user experience.
OBJECTS OF THE INVENTION
[0025] An object of the present invention is to provide a system and a method
for implementing a plurality of barring policies on the subscribers of the network.
[0026] Another object of the present invention is to provide the system and the method for implementing the plurality of barring policies on the subscribers without a requirement of external triggers.
[0027] Another object of the present invention is to provide the system and the method for implementing the plurality of barring policies on the subscribers without providing additional overloading traffic to the peer nodes and the network.
SUMMARY
[0028] In an exemplary embodiment, the present invention discloses a method for implementing a plurality of barring policies on a user equipment (UE) in a network. The method comprising receiving, by a processing engine, a tracking area

code (TAC) information related to the UE. Accessing, by the processing engine, a session table information associated with one or more sessions between the UE and the network. Matching, by the processing engine, the received TAC information with the accessed session table information. Determining, by the processing engine, at least one session from the one or more sessions having the matched session table information with the TAC information and implementing, by a converged policy control function (PCF), the plurality of barring policies on the UE for the at least one determined session.
[0029] In some embodiments, the method further comprising transmitting, by the converged PCF, at least one re-authorization request (RAR) message for the at least one determined session to a packet data network gateway control plane (PGW-C).
[0030] In some embodiments, the method further comprising transmitting, by the converged PCF, at least one notify request message for the at least one determined session to a session management function (SMF).
[0031] In some embodiments, the method further comprising receiving, by the converged PCF, at least one re-authorization answer (RAA) message from the PGW-C.
[0032] In some embodiments, the method further comprising receiving, by the converged PCF, at least one response message from the SMF.
[0033] In some embodiments, the at least one RAR message is transmitted by the PCF in a controlled manner with a transaction per second (TPS) rate limiting mechanism.
[0034] In some embodiments, the at least one notify request message is transmitted by the converged PCF in the controlled manner with the TPS rate

limiting mechanism.
[0035] In some embodiments, the converged PCF includes the PCF and a policy charging rules function (PCRF).
[0036] In some embodiments, the session table information includes the TAC information associated with each session of the one or more sessions between the UE and the network.
[0037] In an exemplary embodiment, the present invention discloses a system for implementing a plurality of barring policies on a user equipment (UE) in a network. The system comprising a processing engine and a memory coupled to the processing engine. The memory includes instructions to configure the processing engine to receive a tracking area code (TAC) information related to the UE, access a session table information associated with one or more sessions between the UE and the network, and match the received TAC information with the accessed session table information. The processing engine further configured to determine at least one session from the one or more sessions having the matched session table information with the TAC information. Implement, by a converged policy control function (PCF), the plurality of barring policies on the UE for the at least one determined session.
[0038] In some embodiments, the system is configured to transmit, by the converged PCF, at least one re-authorization request (RAR) message for the at least one determined session to a packet data network gateway control plane (PGW-C). [0039] In some embodiments, the system is configured to transmit, by the converged PCF, at least one notify request message for the at least one determined session to a session management function (SMF).
[0040] In some embodiments, the system is configured to receive, by the converged PCF, at least one re-authorization answer (RAA) message from the

PGW-C.
[0041] In some embodiments, the system is configured to receive, by the converged PCF, at least one response message from the SMF.
[0042] In some embodiments, the at least one RAR message is transmitted by the converged PCF in a controlled manner with a transaction per second (TPS) rate limiting mechanism.
[0043] In some embodiments, the at least one notify request message is transmitted by the converged PCF in the controlled manner with the TPS rate limiting mechanism.
[0044] In some embodiments, the converged PCF includes the PCF and a policy charging rules function (PCRF).
[0045] In some embodiments, the session table information includes the TAC information associated with each session of the one or more sessions between the UE and the network.
[0046] In another exemplary embodiment, the present invention discloses a user equipment (UE) communicatively coupled with a network. The coupling comprises steps of receiving, by the network, a connection request from the UE, sending, by the network, an acknowledgment of the connection request to the UE and transmitting a plurality of signals in response to the connection request. A plurality of barring policies are implemented on the UE by a method. The method comprising receiving, by a processing engine, a tracking area code (TAC) information related to the UE. Accessing, by the processing engine, a session table information associated with one or more sessions between the UE and the network. Matching, by the processing engine, the received TAC information with the accessed session table information. Determining, by the processing engine, at least

one session from the one or more sessions having the matched session table information with the TAC information and implementing, by a converged policy control function (PCF), the plurality of barring policies on the UE for the at least one determined session.
[0047] 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.
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 in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure of such drawings includes the disclosure of electrical components, electronic components or circuitry commonly used to implement such components.
[0049] FIG. 1 illustrates an exemplary network architecture in which or with which embodiments of the present disclosure may be implemented, in accordance with embodiments of the present disclosure.
[0050] FIG. 2 illustrates an exemplary block diagram of a system for implementing a plurality of barring policies on a user equipment (UE) in a network, in accordance with embodiments of the present disclosure.
[0051] FIG. 3 illustrates an exemplary schematic diagram of the system architecture of the system for implementing the plurality of barring policies on the

UE in the network, in accordance with embodiments of the present disclosure.
[0052] FIG. 4 illustrates a schematic flow diagram depicting operation of the system for implementing the plurality of barring policies on the UE in the network, in accordance with embodiments of the present disclosure.
[0053] FIG. 5 illustrates an exemplary computer system in which or with which the system may be implemented, in accordance with an embodiment of the present disclosure.
[0054] FIG. 6 illustrates an exemplary flow diagram of a method for implementing the plurality of barring policies on the UE in the network, in accordance with embodiments of the present disclosure.
LIST OF REFERENCE NUMERALS
100 - Network architecture
102-1, 102-2…102-N - A plurality of users
104-1, 104-2….104-N - A plurality of computing devices
106 - Network
112 - Centralized server
200 - System
202 - A plurality of processor(s)
204 - Memory
206 - A plurality of interface(s)
210 - Processing engine

220 - Database
300 - Schematic diagram of system architecture
302 - Deep Packet Inspection (DPI)
304 – Session Management Function (SMF)
306 – Charging Function (CHF)
308 – Bootstrap Function (BSF)
310 - Network Resource Function (NRF)
312 – Application Function (AF)
314 – Subscriber Profile Repository (SPR)
316 – Network Management System (NMS)
318 – Packet Data Network Gateway (PGW)
320 – Online Charging Systems (OCS)
322 – Access and Mobility Management Function (AMF)
324 – Policy Control Function (PCF) and Policy and Charging Rules Function (PCRF)
400 - Flow Diagram
402 - Session management function (SMF)
404 - Packet data network gateway control plane (PGW-C)
406 – PCF and PCRF
500 - A computer system

510 - External storage device 520 - Bus
530 - Main memory 540 - Read only memory 550 - Mass storage device 560 - Communication port(s) 570 – Processor 600 – Flow diagram
DETAILED DESCRIPTION
[0055] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features. An individual feature may not address 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 of the features described herein.
[0056] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.

[0057] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.
[0058] 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 diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination can correspond to a return of the function to the calling function or the main function.
[0059] The word “exemplary” and/or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and/or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive—in a manner similar to the term “comprising” as an open transition word—without precluding

any additional or other elements.
[0060] Reference throughout this specification to “one embodiment” or “an embodiment” or “an instance” or “one instance” means that a particular feature, 5 structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present disclosure. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” or “in some embodiments” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or 10 characteristics may be combined in any suitable manner in one or more embodiments.
[0061] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used
15 herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one
20 or more other features, integers, steps, operations, elements, components, and/or groups thereof. As used herein, the term “and/or” includes any and all combinations of one or more of the associated listed items.
[0062] Regulatory barring policy may be implemented by sending a location 25 change information to a network function, such as a converged policy control function (PCF) from a session management function (SMF) through an update message. The barring policies are essential rules and regulations set by network operators to manage access to network resources efficiently. These policies ensure fair usage of network capacity, prioritize critical services, and maintain network 30 security. Through access control, Quality of Service (QoS) management, traffic control, and security enforcement, barring policies enable operators to optimize
15

network performance, safeguard against potential threats, and deliver a reliable and high-quality user experience. Based on the information received in the update message, the policy control function may install barring policies and remove non-barring policies on the running sessions based on the predefined policy engine 5 configuration. However, this may increase incoming traffic at the network function, particularly if subscribers are detached-attached from the SMF to get new policies from the converged PCF. Further, this may result in increased network traffic since a number of SMF node counts is always high as compared to a number of centralized converged PCF node in the network. Furthermore, the load on the
10 network function may be exacerbated when subscribers detach-attach from the SMF by manual commands. The high traffic may overload the converged PCF and the network. There is, therefore, a requirement in the art to provide a system and a method implement barring policy for the subscribers without overloading the network due to increased traffic. The converged PCF refers to a combination of the
15 PCF and the PCRF into a single entity. This convergence streamlines policy control, session management, and charging functions, eliminating the need for separate entities, and simplifying network architecture. By integrating policy control and charging policies, the converged PCF facilitates dynamic policy enforcement, real¬time charging, and seamless subscriber management, enabling efficient resource
20 utilization and enhanced service delivery in the network.
[0063] The present disclosure provides an improved system and method for implementing a plurality of barring policies on the subscribers without a requirement of external triggers. Further, the disclosed system and method 25 implements the plurality of barring policies on the subscribers without providing additional overloading traffic to the peer nodes and the network.
[0064] The various embodiments of the present disclosure will be explained in detail with reference to FIGs. 1 – 6. 30
[0065] FIG. 1 illustrates an exemplary network architecture (100) in which or
16

with which embodiments of the present disclosure may be implemented. Referring to FIG. 1, the network architecture (100) may include one or more computing devices or user equipment (104-1, 104-2…104-N) associated with one or more subscribers/users (102-1, 102-2…102-N) in an environment. A person of ordinary 5 skill in the art will understand that one or more subscribers (102-1, 102-2…102-N) may be individually referred to as the subscriber (102) or user (102) and collectively referred to as the subscribers (102) or users (102). Similarly, a person of ordinary skill in the art will understand that one or more user equipment (104-1, 104-2…104-N) may be individually referred to as the user equipment (104) and collectively 10 referred to as the user equipment (104). A person of ordinary skill in the art will appreciate that the terms “computing device(s)” and “user equipment” may be used interchangeably throughout the disclosure. Although three user equipment (104) are depicted in FIG. 1, however any number of the user equipment (104) may be included without departing from the scope of the ongoing description. 15
[0066] In some embodiments, the user equipment (104) may include, but is not limited to, a handheld wireless communication device (e.g., a mobile phone, a smart phone, a phablet device, and so on), a wearable computer device(e.g., a head-mounted display computer device, a head-mounted camera device, a wristwatch 20 computer device, and so on), a Global Positioning System (GPS) device, a laptop computer, a tablet computer, or another type of portable computer, a media playing device, a portable gaming system, and/or any other type of computer device with wireless communication capabilities, and the like. In some embodiments, the user equipment 104 may include, but is not limited to, any electrical, electronic, electro-25 mechanical, or an equipment, or a combination of one or more of the above devices such as virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other computing device. The user equipment (104) may include one or more in-built or externally coupled accessories including, but 30 not limited to, a visual aid device such as a camera, an audio aid, a microphone, a keyboard, and input devices for receiving input from the subscriber (102) or the
17

entity such as touch pad, touch enabled screen, electronic pen, and the like. A person of ordinary skill in the art will appreciate that the user equipment (UE) (104) may not be restricted to the mentioned devices and various other devices may be used. The UE (104) may be communicatively coupled with the network (106), the 5 coupling comprises steps of receiving, by the network (106), a connection request from the UE (104), sending, by the network (106), an acknowledgment of the connection request to the UE (104) and transmitting a plurality of signals in response to the connection request.
10 [0067] Referring to FIG. 1, the user equipment (104) may communicate with a system (200), for example, a system for implementing a plurality of barring policies on the UE in the network (106). The plurality of barring policies encompass various aspects such as access control, Quality of Service (QoS) management, traffic prioritization, and security enforcement. In some embodiments, the network (106)
15 may include at least one of a Fifth Generation (5G) network, 6G network, or the like. The network (106) may enable the user equipment 104 to communicate with other devices in the network architecture (100) and/or with the system (200). The network (106) may include a wireless card or some other transceiver connection to facilitate this communication. In another embodiment, the network (106) may be
20 implemented as, or include any of a variety of different communication technologies such as a wide area network (WAN), a local area network (LAN), a wireless network, a mobile network, a Virtual Private Network (VPN), the Internet, the Public Switched Telephone Network (PSTN), or the like.
25 [0068] In another exemplary embodiment, the centralized server 112 may include or comprise, by way of example but not limitation, one or more of: a stand-alone server, a server blade, a server rack, a bank of servers, a server farm, hardware supporting a part of a cloud service or system, a home server, hardware running a virtualized server, one or more processors executing code to function as a server,
30 one or more machines performing server-side functionality as described herein, at least a portion of any of the above, some combination thereof.
18

[0069] Although FIG. 1 shows exemplary components of the network architecture (100), in other embodiments, the network architecture (100) may include fewer components, different components, differently arranged components, or additional functional components than depicted in FIG. 1. Additionally, or 5 alternatively, one or more components of the network architecture (100) may perform functions described as being performed by one or more other components of the network architecture (100).
[0070] FIG. 2 illustrates an exemplary block diagram of the system (200) for 10 implementing a plurality of barring policies on the (UE) (104) in the network (106), in accordance with embodiments of the present disclosure.
[0071] The system (200) may include one or more processors (202) and a memory (204) communicably coupled to the one or more processors (202). The one
15 or more processor(s) (202) may be implemented as one or more microprocessors, microcomputers, microcontrollers, edge or fog microcontrollers, digital signal processors, central processing units, logic circuitries, and/or any devices that process data based on operational instructions. Among other capabilities, one or more processor(s) (202) may be configured to fetch and execute computer-readable
20 instructions stored in a memory (204) of the system (200). 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 include any non-transitory storage device including, for example, volatile
25 memory such as Random-Access Memory (RAM), or non-volatile memory such as Erasable Programmable Read-Only Memory (EPROM), flash memory, and the like.
[0072] In some embodiments, the system (200) may include an interface(s)
30 (206). The interface(s) (206) may include a variety of interfaces, for example,
interfaces for data input and output devices, referred to as I/O devices, storage
19

devices, and the like. The interface(s) (206) may facilitate communication of the system (200). The interface(s) (206) may also provide a communication pathway for one or more components of the system (200). Examples of such components include, but are not limited to, processing unit/engine(s) (210) and a database (220). 5
[0073] The processing unit/engine(s) (210) 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) (210). In examples described herein, such combinations of hardware and
10 programming may be implemented in several different ways. For example, the programming for the processing engine(s) (210) may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processing engine(s) (210) may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present
15 examples, the machine-readable storage medium may store instructions that, when executed by the processing resource, implement the processing engine(s) (210). In such examples, the system (200) may include 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
20 (200) and the processing resource. In other examples, the processing engine(s) (210) may be implemented by an electronic circuitry.
[0074] In an embodiment, the processing engine (210) is configured to receive a tracking area code (TAC) information related to the UE (104). The TAC serves as
25 a unique identifier for a specific tracking area, which encompasses one or more cells or base stations. The TAC aids in routing incoming calls and messages to the appropriate base station within its designated geographical area. When the processing engine (210) receives the TAC information related to the UE (104), it gains insight into the UE’s current location and the tracking area it belongs to.
30
[0075] In an embodiment, the processing engine (210) is configured to access
20

a session table information associated with one or more sessions between the UE (104) and the network (106). The one or more sessions between the UE (104) and the network (106) represent the periods during which the UE (104), such as a mobile device, is actively connected to and communicating with the network (106). These 5 sessions are essential for providing services to the UE (104) and facilitating communication between the UE (102) and network elements (e.g., gNodeB). The session table information associated with sessions between the UE (104) and the network (106) includes session identifiers, the UE details like identifier and location, network components involved, session parameters such as Quality of
10 service (QoS) settings and security, session state, and historical data. The session table information associated with one or more sessions between the UE (104) and the network (106) typically involves interacting with network management systems (NMS) or utilizing network protocols. These systems and protocols facilitate the retrieval of relevant data related to the session table information. The NMS,
15 including element management systems (EMS) and subscriber management systems, offer graphical or command-line interfaces for querying real-time and historical session data. Alternatively, standardized protocols like Simple Network Management Protocol (SNMP) or Network Configuration Protocol (NETCONF) enable administrators to communicate with network elements directly to access the
20 session information.
[0076] In an embodiment, the processing engine (210) is configured to match the received TAC information with the accessed session table information. The matching of the TAC information with the session table information involves
25 correlating the TAC information associated with the UE (104) to the relevant session information stored in the network’s session table. In an embodiment, the session table information includes the TAC information associated with each session of the one or more sessions between the UE (104) and the network (106). By accessing session table data, typically containing details like session identifiers,
30 UE information, and session parameters, administrators can extract the TAC value linked to the UE’s current location or connection. The session parameters
21

encompass various details defining the characteristics and context of a communication session between UE (104) and the network (106). For example, session identifiers, UE information like International Mobile Subscriber Identity (IMSI) and International Mobile Equipment Identity (IMEI), session type (e.g., 5 voice call or data session) etc. Further, by comparing the received TAC information with entries in the session table allows for identifying/determining the matching sessions between the UE (104) and the network (106).
[0077] In an embodiment, the processing engine (210) is configured to
10 determine the at least one session from the one or more sessions having the matched session table information with the TAC information. The at least one session is determined by comparing the TAC information with entries in the session table having the corresponding stored TAC information and identifying the at least one session from the matching sessions between the UE (104) and the network (106).
15
[0078] In an embodiment, the processing engine (210) is configured to implement, by a converged policy and control function (PCF), the plurality of barring policies on the UE (104) for the at least one determined session. The plurality of barring policies encompass various aspects such as access control,
20 Quality of Service (QoS) management, traffic prioritization, and security enforcement. The plurality of barring policies are implemented on the UE (104) for the determined at least one session involves configuring the converged PCF to enforce various restrictions or limitations on the UE’s access to network services provided by the network (106). This is achieved by defining policies within the
25 converged PCF based on the session parameters (e.g., the session identifiers, the UE information like the IMSI and the IMEI, the session type, and the subscriber profiles (e.g., the service plans, the billing information, the service preferences, the roaming settings, the privacy settings etc.,). These policies are then applied to the UE for the at least one determined session for controlling the UE’s access to specific
30 services, limiting data usage, or enforcing the QoS restrictions. For example, when a session is initiated, the converged PCF first evaluates session parameters like
22

subscriber information, session type, requested services, and network conditions. Based on this evaluation, it selects relevant policies from a policy and charging rules function (PCRF), covering access control, QoS, charging, and service restrictions. Once selected, the converged PCF configures these policies for 5 enforcement, defining how each policy should be applied to the session. It then communicates these configured policies to network elements responsible for enforcement, such as a policy enforcement function (PEF), a session management function (SMF) and a Packet Data Network Gateway Control Plane (PGW-C). These network elements enforce the policies, ensuring that subscribers adhere to
10 network policies and receive the appropriate level of service. In some embodiments, the barring policies are implemented on the TAC information by an operator. In some embodiments, the operator uses a plurality of manual commands from a command line interface (CLI) to implement the barring policies on the TAC information.
15
[0079] In an embodiment, the processing engine (210) is configured to transmit, by the converged PCF, at least one re-authorization request (RAR) message for the at least one determined session to the PGW-C. The RAR message includes information about the session, such as session identifiers, subscriber
20 profiles, and any updated policy parameters or authorization rules. The RAR is a Diameter credit control command. The RAR is sent by the converged PCF to the PGW-C using a push procedure that allows the converged PCF to push updated PCC rules and event triggers dynamically to the PGW-C. The converged PCF initiates the RAR message transmission to the PGW-C when changes in
25 subscription status, service parameters, or network policies necessitate a re-verification of the session’s authorization status. Upon receiving the RAR message, the PGW-C processes the request, verifies the session’s authorization status based on the provided information, and responds accordingly.
30 [0080] In an embodiment, the processing engine (210) is configured to transmit, by the converged PCF, at least one notify request message for the at least
23

one determined session to the SMF. In an embodiment, the notify request message is a ‘Npcf_SMPolicyControl_UpdateNotify’ request. This request is typically sent from the converged PCF to the SMF to notify it of the updates or changes related to the policy control for the at least one determined session. The message contains 5 information about the update or event triggering the notification, such as changes in QoS parameters, policy enforcement decisions, or session state transitions. It allows the SMF to stay informed about relevant changes in the policy control and take appropriate actions as necessary. In some embodiments, the converged PCF transmits the notify request message to the SMF using the Hypertext Transfer 10 Protocol version 2 (HTTP2) interface.
[0081] In an embodiment, the processing engine (210) is configured to receive, by the converged PCF, the at least one re-authorization answer (RAA) message from the PGW-C (404) after sending the RAR message. The RAA message serves
15 as a response to the RAR message and contains information regarding the outcome of the re-authorization process for the at least one determined session. In an embodiment, the outcome may include confirmation or rejection of requested changes to QoS parameters, or updates to session-related policies, for the at least one determined session.
20
[0082] In an embodiment, the processing engine (210) is configured to receive, by the converged PCF, the at least one response message from the SMF. In an embodiment, the at least one response message includes a ‘Npcf_SMPolicyControl_UpdateNotify’ response. This response is a message sent
25 by the SMF (402) in response to the Npcf_SMPolicyControl_UpdateNotify’ request to the converged PCF. This response acknowledges the receipt of the update notification and may include additional information confirming the successful processing of the notification.
30 [0083] In an embodiment, the at least one RAR message and the at least one notify request message is transmitted by the converged PCF in a controlled manner
24

with a transaction per second (TPS) rate limiting mechanism. The TPS rate limiting mechanism regulates the rate at which RAR messages are sent the PGW-C to ensure network stability and prevent overload. By controlling the TPS rate, the converged PCF manages the flow of RAR messages, balancing the need for timely 5 communication with the network’s capacity constraints. Further, the examples of the TPS rate limiting mechanism includes traffic shaping techniques, congestion control measures, priority queuing, and feedback mechanisms. In some embodiments, the converged PCF transmits the RAR message to the PGW-C using a diameter protocol.
10
[0084] FIG. 3 illustrates an exemplary schematic diagram of the system architecture (300) of the system for implementing the plurality of barring policies on the UE (104) in the network (106), in accordance with embodiments of the present disclosure.
15
[0085] As shown in the FIG. 3, the converged PCF (PCF+PCRF) (324) may communicate with a plurality of network functions through a plurality of interfaces. This interconnected network enables an efficient implementation and enforcement of policy and charging rules across the network. The plurality of network functions
20 include a deep packet inspection (DPI) (302), a session management function (SMF) (304), a charging function (CHF) (306), a binding support function (BSF) (308), a network repository function (NRF) (310), an application function (AF) (312), a subscription profile repository (SPR) (314), a network management system (NMS) (316), a packet data network (PDN) gateway (PGW) (318), an online
25 charging system (OCS) (320), and an access management function (AMF) (322).
[0086] The AMF (322) may communicate with the converged PCF (324) via a N15 interface. The DPI (302) may communicate with the converged PCF (324) via a Sd interface. The DPI (302) is critical for analysing network traffic in real-time, 30 providing detailed information about data flows, which helps the converged PCF (324) in making informed policy decisions. The SMF (304) may communicate with
25

the converged PCF (324) via a N7 interface. The SMF (304) is responsible for session establishment, modification, and release, and its interaction with the converged PCF (324) ensures that policies are enforced throughout the lifecycle of a session. The CHF (306) may communicate with the converged PCF (324) via a 5 N28 interface. The CHF (306) handles the charging data records (CDRs) and interacts with the converged PCF (324) to apply charging policies based on usage data, ensuring accurate billing, and charging mechanisms.
[0087] The BSF (308) may communicate with the converged PCF (324) via a
10 Nbsf interface. The BSF (308) manages the bindings of user sessions and internet protocol IP addresses, which is crucial for maintaining session continuity and enforcing policies related to user identity and session binding. The NRF (310) may communicate with the converged PCF (324) via a Nnrf interface. The NRF (310) provides a repository of network functions and their services, enabling the
15 converged PCF (324) to discover and interact with other network entities dynamically. The AF (312) may communicate with the converged PCF (324) via a Rx interface. The AF (312) provides application-level information and requirements, enabling the converged PCF (324) to apply application-specific policies that enhance the quality of experience for end-users. The PGW (318) may
20 communicate with the converged PCF (324) via a Gx interface. The PGW (318) acts as a gateway to external packet data networks, and its interaction with the converged PCF (324) is essential for enforcing policies related to data traffic management and QoS. The OCS (320) may communicate with the converged PCF (324) via a Sy interface. The OCS (320) is responsible for real-time charging and
25 credit control, interacting with the converged PCF (324) to ensure that usage policies are aligned with the user’s credit status and account balance.
[0088] FIG. 4 illustrates a schematic flow diagram depicting operation of the system (200) for implementing the plurality of barring policies on the UE (104) in 30 the network (106), in accordance with embodiments of the present disclosure.
[0089] In an embodiment, the system (200) may be implemented when the
26

converged PCF (PCF+PCRF) (406) includes all Gx and Session Management Function (SMF) session information with tracking area code details. The Gx interface is used for provisioning and removal of PCC rules from the PCRF to the PCEF and the transmission of traffic plane events from the PCEF to the PCRF. The 5 PCC rules in telecommunications networks are sets of policies that govern various aspects of network resource usage, Quality of Service (QoS), and charging for subscribers. Enforced by the PCRF, these rules dictate how network resources are allocated, how subscribers are billed for their usage, and how different types of traffic are treated to ensure a seamless and efficient user experience. PCC rules 10 encompass parameters such as QoS parameters, charging policies, access control, traffic steering, and policy enforcement, playing a crucial role in optimizing network performance, managing network resources, and delivering high-quality services to subscribers.
15 [0090] In some embodiments, manual commands may be input to the system (200) via by a user of the system (200) via the CLI. The commands may relate to implementation of barring policies based on parameters. In some embodiments, the parameters may include the TAC information.
20 [0091] At 408, the converged PCF (406) may be configured to transmit the RAR messages to a packet data network gateway control plane (PGW-C) in Diameter protocol. In an embodiment, the RAR message includes the charging rules to be installed and the charging rules to be removed. The Diameter protocol provides authentication, authorization, and accounting (AAA) messaging services
25 for network access and data mobility applications in 3G, IP Multimedia Systems (IMS), and LTE/4G networks.
[0092] At 410, the converged PCF (406) transmits a session management (SM)
policy control update notify request message for the determined the session to the
30 SMF (402). The converged PCF (406) transmits a
Npcf_SMPolicyControl_UpdateNotify request message to the SMF (402). The
27

Npcf_SMPolicyControl_UpdateNotify request message update and/or delete the PCC rule(s) packet data unit (PDU) session related policy context at the SMF (402) and Policy Control Request Trigger information.
5 [0093] At step 412, the converged PCF (406) receives the RAA message from the PGW-C (404). The result-code for the RAA message is 2001 with indication Diameter_Success that indicates that the diameter request (RAR) is executed successfully.
10 [0094] At step 414, the converged PCF (406) receives a response message from the SMF (402). The converged PCF (406) receives a Npcf_SMPolicyControl_UpdateNotify response message from the SMF (402) in a 200OK status code indicating that the Npcf_SMPolicyControl_UpdateNotify request message has succeeded.
15
[0095] The converged PCF (406) implements the barring policies on the UE (104) for the determined session after receiving the response message from the SMF (402). In some embodiments, a predetermined number of RAR messages may be sent in groups. Further, SM policy control may update and notify messages on
20 HTTP2 interfaces for the sessions that have the mentioned TAC information saved in their respective session tables. For sessions that already have updated policies pertaining to barring policies, the PCF+PCRF (406) may not send notification messages to the PGW / SMF.
25 [0096] Furthermore, the converged PCF (406) may transmit the notifications in a controlled manner. Specifically, the converged PCF (406) may utilize a rate limiting mechanism so that any peer nodes do not get overloaded due to transmission of the notification messages. Thus, the system 200 provides a means that facilitates the converged PCF (406) to implement barring policies for particular
30 areas without use of external triggers. Further, the converged PCF (406) may push new barring policies by implementing the constant rate control mechanism in a
28

controlled manner, such that peer nodes can serve the request and overload situations do not occur.
[0097] FIG. 5 illustrates an exemplary computer system (500) in which or with 5 which embodiments of the present disclosure may be implemented. 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
10 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 fibre, a serial port, a parallel port, or other existing or future ports. The communication ports(s)
15 (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.
[0098] In some embodiments, the main memory (530) may be Random Access
20 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
25 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).
30
[0099] In some embodiments, the bus (520) may communicatively couple the
29

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), USB, or the like, for connecting expansion cards, drives, and other subsystems as well as other buses, 5 such a front side bus (FSB), which connects the processor (570) to the computer system (500).
[0100] In another embodiment, operator and administrative interfaces, e.g., a display, keyboard, and cursor control device may also be coupled to the bus (520)
10 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
15 disclosure.
[0101] FIG. 6 illustrates an exemplary flow diagram of a method (600) for implementing the plurality of barring policies on the UE (104) in the network (106).
20 [0102] At step 602: The method (600) comprising receiving (602), by the processing engine (210), the TAC information related to the UE (104). The TAC serves as a unique identifier for a specific tracking area, which encompasses one or more cells or base stations. The TAC aids in routing incoming calls and messages to the appropriate base station within its designated geographical area. When the
25 processing engine (210) receives the TAC information related to the UE (104), it gains insight into the UE’s current location and the tracking area it belongs to.
[0103] At step 604: The method (600) comprising accessing, by the processing
engine (210), the session table information associated with the one or more sessions
30 between the UE (104) and the network (106). The one or more sessions between
the UE (104) and the network (106) represent the periods during which the UE
30

(104), such as a mobile device, is actively connected to and communicating with the network (106). The session table information associated with sessions between the UE (104) and the network (106) includes session identifiers, the UE details like identifier and location, public land mobile network (PLMN) information, network 5 components involved, session parameters such as QoS settings and security, session state, and historical data. The session table information associated with one or more sessions between the UE (104) and the network (106) typically involves interacting with network management systems (NMS) or utilizing network protocols. These systems and protocols facilitate the retrieval of relevant data related to the session
10 table information. The NMS, including the EMS and the subscriber management systems, offer graphical or command-line interfaces for querying real-time and historical session data. Alternatively, standardized protocols like simple network management protocol (SNMP) or network configuration protocol (NETCONF) enable administrators to communicate with network elements directly to access the
15 session information. In an embodiment, as per the movement of the UE (104), location change event triggers are received at the converged PCF (406) from the SMF (402). Thus, as per the location of the UE (104) the rules are sent in response. In an embodiment, the session table, and the headers of the session table both are based on the standards.
20
[0104] At step 606: The method (600) comprising matching, by the processing engine (210), the received TAC information with the accessed session table information. In an embodiment, the session table information includes the TAC information associated with each session of the one or more sessions between the
25 UE (104) and the network (106). The matching of the TAC information with the session table information involves correlating the TAC information associated with the UE (104) to the relevant session information stored in the network’s session table. By accessing session table data, typically containing details like session identifiers, UE information, and session parameters, administrators can extract the
30 TAC value linked to the UE’s current location or connection. The session parameters encompass various details defining the characteristics and context of a
31

communication session between UE (104) and the network (106). For example, session identifiers, UE information like IMSI and IMEI, session type (e.g., voice call or data session) etc. Further, by comparing the TAC information with entries in the session table having the corresponding stored TAC information allows for 5 identifying/determining the matching sessions between the UE (104) and the network (106).
[0105] At step 608: The method (600) comprising determining (608), by the processing engine (210), the at least one session from the one or more sessions
10 having the matched session table information with the TAC information. The at least one session is determined by comparing the TAC information with entries in the session table having the corresponding stored TAC information and identifying the at least one session from the matching sessions between the UE (104) and the network (106). In an embodiment, the at least one session is determined from the
15 one or more sessions having the matched session table information with the PLMN information.
[0106] At step 610: The method (600) comprising implementing (610), by the converged PCF (406), the plurality of barring policies on the UE (104) for the at
20 least one determined session. In an embodiment, as per the movement of the UE (104), location change event triggers are received at the converged PCF (406) from the SMF (402). Thus, as per the location of the UE (104) the rules are sent in response. In an embodiment, the converged PCF is a combination of the PCF and the PCRF into a single entity. This convergence streamlines policy control, session
25 management, and charging functions, eliminating the need for separate entities, and simplifying network architecture. By integrating policy control and charging rules, the converged PCF facilitates dynamic policy enforcement, real-time charging, and seamless subscriber management, enabling efficient resource utilization and enhanced service delivery in the network. The converged PCF (406) caters to policy
30 control requirements in 4G and 5G networks. It provides a unified platform for configuring and managing policy decisions based on various network parameters,
32

user subscriptions, and usage to deliver the policies to the UE (104). The plurality of barring policies are implemented on the UE (104) for the determined at least one session involves configuring the converged PCF (406) to enforce various restrictions or limitations on the UE’s access to network services provided by the network (106). This is achieved by defining policies within the converged PCF (406) based on the session parameters (e.g., the session identifiers, the UE information like the IMSI and the IMEI, the session type, and the subscriber profiles (e.g., the service plans, the billing information, the service preferences, the roaming settings, the privacy settings etc.,). These policies are then applied to the UE for the at least one determined session for controlling the UE’s access to specific services, limiting data usage, or enforcing the QoS restrictions. For example, when a session is initiated, the converged PCF (406) first evaluates session parameters like subscriber information, session type, requested services, and network conditions. Based on this evaluation, it selects relevant policies from the PCRF, covering access control, QoS, charging, and service restrictions. Once selected, the converged PCF (406) configures these policies for enforcement, defining how each policy should be applied to the session. It then communicates these configured policies to network elements responsible for enforcement, such as the PEF, the SMF (402) and the PGW-C (404). These network elements enforce the policies, ensuring that subscribers adhere to network policies and receive the appropriate level of service. In some embodiments, the barring policies are implemented on the TAC information by an operator. In some embodiments, the operator uses a plurality of manual commands from the CLI to implement the barring policies on the TAC information.
[0107] In an embodiment, the method (600) further comprising transmitting, by the converged PCF (406), the at least one RAR message for the at least one determined session to the PGW-C (404). The converged PCF (406) initiates the RAR message transmission to the PGW-C when changes in subscription status, service parameters, or network policies necessitate a re-verification of the session’s authorization status. Upon receiving the RAR message, the PGW-C processes the

request, verifies the session’s authorization status based on the provided information, and responds accordingly.
[0108] In an embodiment, the method (600) further comprising transmitting, by the converged PCF (406), at least one notify request message for the at least one determined session to the SMF (402). In an embodiment, the notify request message is a ‘Npcf_SMPolicyControl_UpdateNotify’ request. The message contains information about the update or event triggering the notification, such as changes in QoS parameters, policy enforcement decisions, or session state transitions. It allows the SMF (402) to stay informed about relevant changes in the policy control and take appropriate actions as necessary. In some embodiments, the converged PCF (406) transmits the notify request message to the SMF (402) using the HTTP2 interface.
[0109] In an embodiment, the method (600) further comprising receiving, by the converged PCF (406), the at least one RAA message from the PGW-C (404) after sending the RAR message. The RAA message serves as a response to the RAR message and contains information regarding the outcome of the re-authorization process for the at least one determined session.
[0110] In an embodiment, the method (600) further comprising receiving, by the converged PCF (406), the at least one response message from the SMF (402). In an embodiment, the at least one response message includes a ‘Npcf_SMPolicyControl_UpdateNotify’ response. This response acknowledges the receipt of the update notification and may include additional information confirming the successful processing of the notification.
[0111] In an embodiment, the at least one RAR message and the at least one notify request message is transmitted by the converged PCF (406) in a controlled manner with the TPS rate limiting mechanism. The TPS rate limiting mechanism regulates the rate at which RAR messages are sent the PGW-C (404) to ensure

network stability and prevent overload. By controlling the TPS rate, the converged PCF (406) manages the flow of RAR messages, balancing the need for timely communication with the network’s capacity constraints. Further, the examples of the TPS rate limiting mechanism includes traffic shaping techniques, congestion control measures, priority queuing, and feedback mechanisms. In some embodiments, the converged PCF (406) transmits the RAR message to the PGW-C (404) using the diameter protocol.
[0112] The present disclosure provides technical advancement related to managing performance of the network. This advancement addresses the limitations of existing solutions by providing an improved system and method for implementing barring policies on the subscribers/users of the network. The present disclosure provides implementation of barring policies on the subscribers/users without a requirement of the external triggers and without providing additional overloading traffic to the peer nodes and the network. Thus, the present disclosure optimize the network performance, and support a seamless user experience by effectively implementing the barring policies on the subscribers/users of the network.
[0113] 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 to be implemented merely as illustrative of the disclosure and not as limitation.
ADVANTAGES OF INVENTION
[0114] The present invention provides a system and a method for
implementing a plurality of barring policies on the subscribers of the network.

[0115] The present invention provides the system and the method for implementing the plurality of barring policies on the subscribers without a requirement of external triggers.
[0116] The present invention provides the system and the method for implementing the plurality of barring policies on the subscribers without providing additional overloading traffic to the peer nodes and the network.

We Claim:
1. A method (600) for implementing a plurality of barring policies on a user
equipment (UE) (104) in a network (106), the method (600) comprising:
receiving (602), by a processing engine (210), a tracking area code (TAC) information related to the UE (104);
accessing (604), by the processing engine (210), a session table information associated with one or more sessions between the UE (104) and the network (106);
matching (606), by the processing engine (210), the received TAC information with the accessed session table information;
determining (608), by the processing engine (210), at least one session from the one or more sessions having the matched session table information with the TAC information; and
implementing (610), by a converged policy control function (PCF) (406), the plurality of barring policies on the UE (104) for the at least one determined session.
2. The method (600) as claimed in claim 1, further comprising transmitting, by the converged PCF (406), at least one re-authorization request (RAR) message for the at least one determined session to a packet data network gateway control plane (PGW-C) (404).
3. The method (600) as claimed in claim 1, further comprising transmitting, by the converged PCF (406), at least one notify request message for the at least one determined session to a session management function (SMF) (402).

4. The method (600) as claimed in claim 1, further comprising receiving, by the converged PCF (406), at least one re-authorization answer (RAA) message from the PGW-C (404).
5. The method (600) as claimed in claim 1, further comprising receiving, by the converged PCF (406), at least one response message from the SMF (402).
6. The method (600) as claimed in claim 2, wherein the at least one RAR message is transmitted by the converged PCF (406) in a controlled manner with a transaction per second (TPS) rate limiting mechanism.
7. The method (600) as claimed in claim 3, wherein the at least one notify request message is transmitted by the converged PCF (406) in the controlled manner with the TPS rate limiting mechanism.
8. The system (200) as claimed in claim 1, wherein the converged PCF (406) includes the PCF and a policy charging rules function (PCRF).
9. The method (600) as claimed in claim 1, wherein the session table information includes the TAC information associated with each session of the one or more sessions between the UE (104) and the network (106).
10. A system (200) for implementing a plurality of barring policies on a user equipment (UE) (104) in a network (106), the system (200) comprising:
a processing engine (210);
a memory (204) coupled to the processing engine (210), wherein the memory (204) includes instructions to configure the processing engine (210) to:
receive a tracking area code (TAC) information related to the UE (104);

access a session table information associated with one or more sessions between the UE (104) and the network (106);
match the received TAC information with the accessed session table information;
determine at least one session from the one or more sessions having the matched session table information with the TAC information; and
implement, by a converged policy control function (PCF) (406), the plurality of barring policies on the UE (104) for the at least one determined session.
11. The system (200) as claimed in claim 10, further configured to transmit, by the converged PCF (406), at least one re-authorization request (RAR) message for the at least one determined session to a packet data network gateway control plane (PGW-C) (404).
12. The system (200) as claimed in claim 10, further configured to transmit, by the converged PCF (406), at least one notify request message for the at least one determined session to a session management function (SMF) (402).
13. The system (200) as claimed in claim 10, further configured to receive, by the converged PCF (406), at least one re-authorization answer (RAA) message from the PGW-C (404).
14. The system (200) as claimed in claim 10, further configured to receive, by the converged PCF (406), at least one response message from the SMF (402).
15. The system (200) as claimed in claim 11, wherein the at least one RAR message is transmitted by the converged PCF (406) in a controlled manner with a transaction per second (TPS) rate limiting mechanism.

16. The system (200) as claimed in claim 12, wherein the at least one notify request message is transmitted by the converged PCF (406) in the controlled manner with the TPS rate limiting mechanism.
17. The system (200) as claimed in claim 10, wherein the converged PCF (406) includes the PCF and a policy charging rules function (PCRF).
18. The system (200) as claimed in claim 10, wherein the session table information includes the TAC information associated with each session of the one or more sessions between the UE (104) and the network (106).
19. A user equipment (UE) (104) communicatively coupled with a network (106), the coupling comprises steps of:
receiving, by the network (106), a connection request from the UE (104);
sending, by the network (106), an acknowledgment of the connection request to the UE (104); and
transmitting a plurality of signals in response to the connection request, wherein a plurality of barring policies are implemented on the UE (104) by a method (600) as claimed in claim 1.