FORM 2
THE PATENTS ACT, 1970 (39 OF 1970) & THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
“METHOD AND SYSTEM FOR MANAGING ACCESS FOR A USER EQUIPMENT IN A NETWORK”
We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.
The following specification particularly describes the invention and the manner in which it is to be performed.

METHOD AND SYSTEM FOR MANAGING ACCESS FOR A USER EQUIPMENT IN A NETWORK
FIELD OF DISCLOSURE
[0001] Embodiments of the present disclosure generally relate to wireless communication networks. More particularly, embodiments of the present disclosure relate to managing access for a User Equipment (UE) in a network.
BACKGROUND
[0002] The following description of the related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section is used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of the prior art.
[0003] Wireless communication technology has rapidly evolved over the past few decades, with each generation bringing significant improvements and advancements. The first generation of wireless communication technology was based on analog technology and offered only voice services. However, with the advent of the second generation (2G) technology, digital communication and data services became possible, and text messaging was introduced. 3G technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth generation (4G) technology revolutionized wireless communication with faster data speeds, better network coverage, and improved security. Currently, the fifth generation (5G) technology is being deployed, promising even faster data speeds, low latency, and the ability to connect multiple devices simultaneously. With each generation, wireless communication

technology has become more advanced, sophisticated, and capable of delivering more services to its users.
[0004] Telecommunication in the modern world has brought magnificent positive changes into human society. From entertainment to shopping and providing medical facilities, mobile phones have changed the way humans live in society. But there are many situations when the government directs barring of services in an area. There are many regions in the world, wherein due to high instability in the society, barring directions come swiftly and frequently and therefore there was a need to develop a mechanism to effectively manage barring requirements. Further, barring requirements may arise from other factors as well such as changing of telecom circles. A Policy Control Function (PCF) is required to support a regulatory requirement and prevent unauthorized communication within the restricted or barred areas. This regulatory requirement aims to enforce restrictions on services based on specific geographical areas. There is a need to manage barring requirements in high end fast speed networks such as 5G network wherein certain subscribers are needed to be restricted from accessing services based on their location and barring status.
[0005] Thus, there exists an imperative need in the art to manage barring requirements effectively via dedicated Session Management Function (SMF) and Tracking Area Identity (TAI) of a UE.
SUMMARY
[0006] This section is provided to introduce certain aspects of the present disclosure in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter.

[0007] An aspect of the present disclosure may relate to a method for managing access for a User Equipment (UE) in a network. The method comprises receiving, by a processing unit, at a Policy Control Function (PCF) from the UE, a message request comprising a set of message parameters. The set of message parameters comprises at least one of a geo location parameter associated with the UE, a Session management Function (SMF) instance Identifier (ID) associated with the message request, a User Plane Function (UPF) instance associated with the message request, a message type parameter associated with the message request, and a Tracking Area Identity (TAI) parameter associated with the UE. The method further comprises identifying, by the processing unit at the PCF, a location area status of the UE based on the geo location parameter. The location area status indicates one of a barred area and a non-barred area. Furthermore, the method comprises identifying, by the processing unit at the PCF, a dedicated SMF based on the geo location parameter. The method further comprises determining, by the processing unit at the PCF, an attachment status of the UE with the dedicated SMF. The method further comprises identifying, by the processing unit at PCF, a target message type associated with the message type parameter based on the attachment status, wherein the target message is one of a create request message and an update request message. Furthermore, the method comprises identifying, by the processing unit at the PCF, one of a target Tracking Area Identity (TAI) associated with the Tracking Area Identity (TAI) parameter and a target SMF-instance-Id, based on the target message type. The method further comprises creating, by the processing unit, at the PCF, a policy decision to manage access for the UE, based on the determined attachment status and one of the target TAI and the target SMF-Instance-Id in the message request.
[0008] In an exemplary aspect of the present disclosure, the location area status is identified at the PCF, based on a predefined list of location areas associated with the geo location parameter, wherein each location area of the predefined list of location areas is at least one of: a barred location area and a non- barred location area.

[0009] In an exemplary aspect of the present disclosure, the barred location area is identified by the processing unit, at the PCF, in an event of a geo location associated with the geo location parameter being identified as one of the barred location area based on a comparison of the geo location parameter and the predefined list of location areas. The barred location area is associated with specific network policies.
[0010] In an exemplary aspect of the present disclosure, the non-barred location area is an area with unrestricted service access in the network.
[0011] In an exemplary aspect of the present disclosure, the determining the attachment status of the UE with the dedicated SMF further comprises checking a session management data stored within the SMF to confirm if the UE is currently attached or unattached. Furthermore, the determining the attachment status of the UE with the dedicated SMF further comprises performing a real-time query session with the dedicated SMF to verify the current attachment status of the UE.
[0012] In an exemplary aspect of the present disclosure, the creating the policy decision further comprises rejecting a new session establishment request from the dedicated SMF or releasing of an existing session if the UE is in the barring location area and unattached to the dedicated SMF and a UPF.
[0013] In an exemplary aspect of the present disclosure, the creating the policy decision further comprises rejecting a new session establishment request from the dedicated SMF or releasing of an existing session if the UE is in the non-barring location area and attached to the dedicated SMF and a UPF.
[0014] In an exemplary aspect of the present disclosure, the method further comprises discarding, by the processing unit at the PCF, the message request in an event when the target message type is the create request message. Furthermore, the method comprises initiating monitoring, by the processing unit at the PCF, of the

message request in an event when the target message type is the update request message.
[0015] Another aspect of the present disclosure may relate to a system for managing access for a User Equipment (UE) in a network. The system comprises at least a processing unit. The processing unit is configured to receive, at a Policy Control Function (PCF) from the UE, a message request comprising a set of message parameters. The set of message parameters comprises at least one of one of a geo location parameter associated with the UE, a Session management Function (SMF) Identifier associated with the message request, a User Plane Function (UPF) instance associated with the message request a message type parameter associated with the message request, and a Tracking Area Identity (TAI) parameter associated with the UE. The processing unit is further configured to identify, at the PCF, a location area status based on the geo location parameter, wherein the location area status is one of a barred area and a non-barred area. Furthermore, the processing unit is configured to identify, at the PCF, a dedicated SMF based on the geo location parameter. The processing unit is further configured to determine, at the PCF, an attachment status of the UE with the dedicated SMF. The processing unit is further configured to identify, at PCF, a target message type associated with the message type parameter based on the attachment status, wherein the target message is one of a create request message and an update request message. The processing unit is furthermore configured to identify, at the PCF, one of: a target Tracking Area Identity (TAI) associated with the Tracking Area Identity (TAI) parameter and a target SMF-instance-Id, based on the target message type. The processing unit is further configured to create, at the PCF, a policy decision to manage access for the UE, based on the determined attachment status and one of the target TAI and the target SMF-Instance-Id in the message request.
[0016] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for managing access for a User Equipment (UE) in a network, the instructions include executable code which,

when executed by one or more units of a system, cause a processing unit of the system to receive, at a Policy Control Function (PCF) from the UE, a message request comprising a set of message parameters, wherein the set of message parameters comprises at least one of one of a geo location parameter associated with the UE, a Session management Function (SMF) Identifier associated with the message request, a User Plane Function (UPF) instance associated with the message request a message type parameter associated with the message request, and a Tracking Area Identity (TAI) parameter associated with the UE. The instructions when executed by the system further cause the processing unit to identify, at the PCF, a location area status based on the geo location parameter, wherein the location area status is one of a barred area and a non-barred area. The instructions when executed by the system further cause the processing unit to identify, at the PCF, a dedicated SMF based on the geo location parameter. The instructions when executed by the system further cause the processing unit to determine, at the PCF, an attachment status of the UE with the dedicated SMF. The instructions when executed by the system further cause the processing unit to identify, at PCF, a target message type associated with the message type parameter based on the attachment status. The target message is one of a create request message and an update request message. The instructions when executed by the system further cause the processing unit to identify, at the PCF, one of: a target Tracking Area Identity (TAI) associated with the Tracking Area Identity (TAI) parameter and a target SMF-instance-Id, based on the target message type. The instructions when executed by the system further cause the processing unit to create, at the PCF, a policy decision to manage access for the UE, based on the determined attachment status and one of the target TAI and the target SMF-Instance-Id in the message request.
OBJECTS OF THE DISCLOSURE
[0017] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.

[0018] It is an object of the present disclosure to provide a system and a method managing barring requirement effectively via dedicated Session Management Function (SMF) and Tracking Area Identity (TAI) of a UE.
[0019] It is another object of the present disclosure to provide a solution to managing barring requirements effectively via dedicated combination of Session Management Function (SMF) and User Plane Function (UPF).
[0020] It is yet another object of the present disclosure to allocate resources efficiently based on the specific needs of the areas, ensuring that resources are optimized for both barred and non-barred subscribers via the dedicated combination of Session Management Function (SMF) and User Plane Function (UPF) to prevent resource wastage and enhances overall network efficiency.
[0021] It is yet another object of the present disclosure to provide flexible network architecture by deploying the dedicated combination of Session Management Function (SMF) and User Plane Function (UPF) to tailor specific requirements of diverse geographical location and varied subscriber needs.
[0022] It is yet another object of the present disclosure to ensure policy compliance by monitoring the subscribers based on SMF-Instance-Id and TAI combination to ensure that subscribers adhere to network policies and restrictions and maintain regulatory compliance and service quality standards.
DESCRIPTION OF THE DRAWINGS
[0023] 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. Also, the embodiments shown in the figures are not to be construed as
limiting the disclosure, but the possible variants of the method and system
according to the disclosure are illustrated herein to highlight the advantages of the
disclosure. It will be appreciated by those skilled in the art that disclosure of such
5 drawings includes disclosure of electrical components or circuitry commonly used
to implement such components.
[0024] FIG. 1A illustrates an exemplary block diagram representation of 5th generation core (5GC) network architecture.
10
[0025] FIG. 1B illustrates an exemplary system architecture depicting communication between a Policy Control Function (PCF), a Policy and Charging Rules Function (PCRF) and one or more network functions, in accordance with exemplary implementations of the present disclosure.
15
[0026] FIG. 2 illustrates an exemplary block diagram of a computing device upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure.
20 [0027] FIG. 3 illustrates an exemplary block diagram of a system for managing
access for a User Equipment (UE) in a network, in accordance with exemplary implementations of the present disclosure.
[0028] FIG. 4 illustrates a method flow diagram for managing access for the User
25 Equipment (UE) in a network, in accordance with exemplary implementations of
the present disclosure.
[0029] FIG. 5 illustrates an exemplary method for managing access of the UE in a
non-barring location area, in accordance with exemplary implementations of the
30 present disclosure.
9

[0030] FIG. 6 illustrates an exemplary method for managing access of the UE in a barring location area, in accordance with exemplary implementations of the present disclosure.
5 [0031] The foregoing shall be more apparent from the following more detailed
description of the disclosure.
DETAILED DESCRIPTION
10 [0032] 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 may each be used independently of one
15 another or with any combination of other features. An individual feature may not
address any of the problems discussed above or might address only some of the problems discussed above.
[0033] The ensuing description provides exemplary embodiments only, and is not
20 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
25 disclosure as set forth.
[0034] 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
30 specific details. For example, circuits, systems, processes, and other components
10

may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail.
[0035] Also, it is noted that individual embodiments may be described as a process
5 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 may 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
10 included in a figure.
[0036] 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
15 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
20 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.
[0037] As used herein, a “processing unit” or “processor” or “operating processor”
25 includes one or more processors, wherein processor refers to any logic circuitry for
processing instructions. A processor may be a general-purpose processor, a special
purpose processor, a conventional processor, a digital signal processor, a plurality
of microprocessors, one or more microprocessors in association with a (Digital
Signal Processing) DSP core, a controller, a microcontroller, Application Specific
30 Integrated Circuits, Field Programmable Gate Array circuits, any other type of
integrated circuits, etc. The processor may perform signal coding data processing,
11

input/output processing, and/or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor or processing unit is a hardware processor.
5 [0038] As used herein, “a user equipment”, “a user device”, “a smart-user-device”,
“a smart-device”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless communication device”, “a mobile communication device”, “a communication device” may be any electrical, electronic and/or computing device or equipment, capable of implementing the features of the present disclosure. The
10 user equipment/device may include, but is not limited to, a mobile phone, smart
phone, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, wearable device or any other computing device which is capable of implementing the features of the present disclosure. Also, the user device may contain at least one input means configured to receive an input from at least one of
15 a transceiver unit, a processing unit, a storage unit, a detection unit and any other
such unit(s) which are required to implement the features of the present disclosure.
[0039] As used herein, “storage unit” or “memory unit” refers to a machine or computer-readable medium including any mechanism for storing information in a
20 form readable by a computer or similar machine. For example, a computer-readable
medium includes read-only memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical storage media, flash memory devices or other types of machine-accessible storage media. The storage unit stores at least the data that may be required by one or more units of the system to perform their respective
25 functions.
[0040] As used herein “interface” or “user interface” refers to a shared boundary
across which two or more separate components of a system exchange information
or data. The interface may also be referred to a set of rules or protocols that define
30 communication or interaction of one or more modules or one or more units with
12

each other, which also includes the methods, functions, or procedures that may be called.
[0041] All modules, units, components used herein, unless explicitly excluded
5 herein, may be software modules or hardware processors, the processors being a
general-purpose processor, a special purpose processor, a conventional processor,
a digital signal processor (DSP), a plurality of microprocessors, one or more
microprocessors in association with a DSP core, a controller, a microcontroller,
Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array
10 circuits (FPGA), any other type of integrated circuits, etc.
[0042] As used herein the transceiver unit include at least one receiver and at least
one transmitter configured respectively for receiving and transmitting data, signals,
information or a combination thereof between units/components within the system
15 and/or connected with the system.
[0043] As discussed in the background section, the current known solutions have
several shortcomings. The present disclosure aims to overcome the above-
mentioned and other existing problems in this field of technology by providing
20 method and system of managing access for a User Equipment (UE) in a network.
[0044] FIG. 1A illustrates an exemplary block diagram representation of 5th generation core (5GC) network architecture [100A], in accordance with exemplary implementation of the present disclosure. As shown in FIG. 1A, the 5GC network
25 architecture [100A] includes a user equipment (UE) [102], a radio access network
(RAN) [104], an access and mobility management function (AMF) [106], a Session Management Function (SMF) [108], a Service Communication Proxy (SCP) [110], an Authentication Server Function (AUSF) [112], a Network Slice Specific Authentication and Authorization Function (NSSAAF) [114], a Network Slice
30 Selection Function (NSSF) [116], a Network Exposure Function (NEF) [118], a
Network Repository Function (NRF) [120], a Policy Control Function (PCF) [122],
13

a Unified Data Management (UDM) [124], an application function (AF) [126], a User Plane Function (UPF) [128], a data network (DN) [130], wherein all the components are assumed to be connected to each other in a manner as obvious to the person skilled in the art for implementing features of the present disclosure. 5
[0045] The Radio Access Network (RAN) [104] is the part of a mobile
telecommunications system that connects user equipment (UE) [102] to the core
network (CN) and provides access to different types of networks (e.g., 5G network).
It consists of radio base stations and the radio access technologies that enable
10 wireless communication.
[0046] The Access and Mobility Management Function (AMF) [106] is a 5G core
network function responsible for managing access and mobility aspects, such as UE
registration, connection, and reachability. It also handles mobility management
15 procedures like handovers and paging.
[0047] The Session Management Function (SMF) [108] is a 5G core network
function responsible for managing session-related aspects, such as establishing,
modifying, and releasing sessions. It coordinates with the User Plane Function
20 (UPF) for data forwarding and handles IP address allocation and QoS enforcement.
[0048] The Service Communication Proxy (SCP) [110] is a network function in the
5G core network that facilitates communication between other network functions
by providing a secure and efficient messaging service. It acts as a mediator for
25 service-based interfaces.
[0049] The Authentication Server Function (AUSF) [112] is a network function in the 5G core responsible for authenticating UEs during registration and providing security services. It generates and verifies authentication vectors and tokens. 30
14

[0050] The Network Slice Specific Authentication and Authorization Function (NSSAAF) [114] is a network function that provides authentication and authorization services specific to network slices. It ensures that UEs can access only the slices for which they are authorized. 5
[0051] The Network Slice Selection Function (NSSF) [116] is a network function responsible for selecting the appropriate network slice for a UE based on factors such as subscription, requested services, and network policies.
10 [0052] The Network Exposure Function (NEF) [118] is a network function that
exposes capabilities and services of the 5G network to external applications, enabling integration with third-party services and applications.
[0053] The Network Repository Function (NRF) [120] is a network function that
15 acts as a central repository for information about available network functions and
services. It facilitates the discovery and dynamic registration of network functions.
[0054] The Policy Control Function (PCF) [122] is a network function responsible
for policy control decisions, such as QoS, charging, and access control, based on
20 subscriber information and network policies.
[0055] The Unified Data Management (UDM) [124] is a network function that centralizes the management of subscriber data, including authentication, authorization, and subscription information. 25
[0056] The Application Function (AF) [126] is a network function that represents external applications interfacing with the 5G core network to access network capabilities and services.
15

[0057] The User Plane Function (UPF) [128] is a network function responsible for handling user data traffic, including packet routing, forwarding, and QoS enforcement.
5 [0058] The Data Network (DN) [130] refers to a network that provides data
services to user equipment (UE) in a telecommunications system. The data services may include but are not limited to Internet services, private data network related services.
10 [0059] Referring to FIG. 1B, an exemplary system architecture [100B] depicting
communication between a Policy Control Function (PCF) [122], a Policy and Charging Rules Function (PCRF) [122A] and one or more network functions, in accordance with exemplary implementations of the present disclosure is shown. The exemplary system architecture [100B] includes the PCF [122], and the PCRF
15 [122A]. Generally, the PCRF [122A] is a node that operates in real time to
determine policy rules in a network. The PCRF [122A] is configured to define and monitor quality of service (QoS) policies based on user profiles to ensure that users receive a quality of service that matches their subscription. The PCF [122] and the PCRF [122A] are in communication with the one or more network functions. The
20 one or more network functions include but may not be limited to a Deep packet
inspection unit (DPI) [132], the SMF [108], a charging function (CHF) [134], a Binding Support Function (BSF) [136], and the NRF [120]. Also, the one or more network functions include the AMF [106], the AF [126], an Online Charging System (OCS) [138], a Packet Data Network Gateway (PGW) [140], a Network
25 Management System (NMS) [142] and a Subscription Profile Repository (SPR)
[144]. The DPI unit [132] is configured to perform a method of examining content of data packets as they pass by a checkpoint on the network. In addition, the CHF [134] is a network function that exists in control plane in a 5G core network. The CHF [134] is responsible for charging in 5G core network supporting both online
30 and offline charging. The CHF [134] may interacts with the SMF [108] during
active user session to perform online charging. Generally, the BSF [136] enables
16

the PCF [122] to register, update and remove binding information from the PCF [122] or the PCRF [122A].
[0060] Further, in general, the OCS [138] enables fixed, mobile, and data network
5 carriers to charge fee for voice, data, and multimedia services in real time. In
addition, the PGW [140] acts as an interface between the 5G network and external
data network. The NMS [142] identifies, configures, monitors, updates and
troubleshoots network devices (both wired and wireless). Also, the SPR [144]
contains subscriber (e.g. user) related information (such as charging and policy
10 control). The SPR [144] provides the subscriber related information to the PCF
[122] and the PCRF [122A].
[0061] FIG. 2 illustrates an exemplary block diagram of a computing device [200] upon which the features of the present disclosure may be implemented in
15 accordance with exemplary implementation of the present disclosure. In an
implementation, the computing device [200] may also implement a method for managing access for a User Equipment (UE) in a network, utilising the system. In another implementation, the computing device [200] itself implements the method for managing access for a User Equipment (UE) in a network, using one or more
20 units configured within the computing device [200], wherein said one or more units
are capable of implementing the features as disclosed in the present disclosure.
[0062] The computing device [200] may include a bus [202] or other communication mechanism for communicating information, and a hardware
25 processor [204] coupled with bus [202] for processing information. The hardware
processor [204] may be, for example, a general-purpose microprocessor. The computing device [200] may also include a main memory [206], such as a random-access memory (RAM), or other dynamic storage device, coupled to the bus [202] for storing information and instructions to be executed by the processor [204]. The
30 main memory [206] also may be used for storing temporary variables or other
intermediate information during execution of the instructions to be executed by the
17

processor [204]. Such instructions, when stored in non-transitory storage media
accessible to the processor [204], render the computing device [200] into a special-
purpose machine that is customized to perform the operations specified in the
instructions. The computing device [200] further includes a read only memory
5 (ROM) [208] or other static storage device coupled to the bus [202] for storing static
information and instructions for the processor [204].
[0063] A storage device [210], such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus [202] for storing information and
10 instructions. The computing device [200] may be coupled via the bus [202] to a
display [212], such as a cathode ray tube (CRT), Liquid crystal Display (LCD), Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for displaying information to a computer user. An input device [214], including alphanumeric and other keys, touch screen input means, etc. may be coupled to the
15 bus [202] for communicating information and command selections to the processor
[204]. Another type of user input device may be a cursor controller [216], such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor [204], and for controlling cursor movement on the display [212]. The input device typically has two degrees
20 of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow
the device to specify positions in a plane.
[0064] The computing device [200] may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware
25 and/or program logic which in combination with the computing device [200] causes
or programs the computing device [200] to be a special-purpose machine. According to one implementation, the techniques herein are performed by the computing device [200] in response to the processor [204] executing one or more sequences of one or more instructions contained in the main memory [206]. Such
30 instructions may be read into the main memory [206] from another storage medium,
such as the storage device [210]. Execution of the sequences of instructions
18

contained in the main memory [206] causes the processor [204] to perform the process steps described herein. In alternative implementations of the present disclosure, hard-wired circuitry may be used in place of or in combination with software instructions. 5
[0065] The computing device [200] also may include a communication interface [218] coupled to the bus [202]. The communication interface [218] provides a two-way data communication coupling to a network link [220] that is connected to a local network [222]. For example, the communication interface [218] may be an
10 integrated services digital network (ISDN) card, cable modem, satellite modem, or
a modem to provide a data communication connection to a corresponding type of telephone line. As another example, the communication interface [218] may be a local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links may also be implemented. In any such
15 implementation, the communication interface [218] sends and receives electrical,
electromagnetic or optical signals that carry digital data streams representing various types of information.
[0066] The computing device [200] can send messages and receive data, including
20 program code, through the network(s), the network link [220] and the
communication interface [218]. In the Internet example, a server [230] might
transmit a requested code for an application program through the Internet [228], the
ISP [226], the local network [222], the host [224] and the communication interface
[218]. The received code may be executed by the processor [204] as it is received,
25 and/or stored in the storage device [210], or other non-volatile storage for later
execution.
[0067] The present disclosure is implemented by a system [300] (as shown in FIG.
3). In an implementation, the system [300] may include the computing device [200]
30 (as shown in FIG. 2). It is further noted that the computing device [200] may
perform the steps of a method [400] (as shown in FIG. 4).
19

[0068] Referring to FIG. 3, an exemplary block diagram of a system [300] for
managing access for the User Equipment (UE) [102] in a network, is shown, in
accordance with the exemplary implementations of the present disclosure. The
5 system [300] comprises at least one processing unit [302]. Also, all of the
components/ units of the system [300] are assumed to be connected to each other unless otherwise indicated below. As shown in the figures all units shown within the system should also be assumed to be connected to each other. Also, in FIG. 3 only a few units are shown, however, the system [300] may comprise multiple such
10 units or the system [300] may comprise any such numbers of said units, as required
to implement the features of the present disclosure. Further, in an implementation, the system [300] may be present in a user device to implement the features of the present disclosure. The system [300] may be a part of the user device / or may be independent of but in communication with the user device (may also referred herein
15 as a UE). In another implementation, the system [300] may reside in a server or a
network entity. In yet another implementation, the system [300] may reside partly in the server/ network entity and partly in the user device. The system [300] is configured for managing access for a User Equipment (UE) in a network, with the help of the interconnection between the components/units of the system [300]. In
20 an implementation of the present disclosure, the network may be a 5th Generation
core network. In another implementation, the network may be a 4th Generation network, a 6th Generation network, or any other future generations of network.
[0069] The system comprises at least a processing unit [302]. The processing unit
25 [302] is configured to receive, at a Policy Control Function (PCF [122]) from the
UE [102], a message request comprising a set of message parameters. In one
implementation, the message request may be a Session Management (SM) message
request that refers to establishment of a new session in a dedicated SMF. In another
implementation, the message request may be a Session Management (SM) update
30 message. In an embodiment, the SM update message may be an update request for
releasing a previous session for the UE [102]. In another embodiment, the SM
20

update message request refers to release of an existing session in the dedicated
SMF. The message request may be received from the UE [102] at multiple instances
of time. The set of message parameters comprises at least one of one of a geo
location parameter associated with the UE [102], a Session management Function
5 (SMF) Identifier associated with the message request, a User Plane Function (UPF)
instance associated with the message request, a message type parameter associated with the message request, and a Tracking Area Identity (TAI) parameter associated with the UE [102]. In general, the SMF identifier uniquely identifies the SMF within the network to route and manage signals between network functions. In
10 addition, User Plane Function (UPF) instance in 5G core network is a specific
operational unit of a User Plane Function (UPF) [128]. The UPF [128] is configured to handle and process user data traffic in the 5G core network. Each UPF instance is designed to manage and forward user data packets between the user equipment (UE) [102] and external networks.
15
[0070] The geo location parameter refers to longitudinal and latitudinal position of the UE [102] at a specific time. For example, the geolocation parameters associated with the UE [102] may be 1441000, 23450000 which refers to 14°41.000 North and 23°45.000 East. The message type parameter includes parameters such as a create
20 message, an update message, and the like. The TAI refers to an identifier assigned
to a specific geographical area for tracking and managing the location of the UE [102].
[0071] The processing unit [302] is further configured to identify, at the PCF [122],
25 a location area status based on the geo location parameter. The location area status
is one of a barred area and a non-barred area. In general, barred area refers to a
segment or portion of a network that has restricted access or is intentionally kept
off-limits to certain users or devices. The non-barred area refers to parts of a
network that do not have access restrictions or are open to users and devices under
30 normal conditions. Generally, a non-barred area allows for open communication
and access. Further, the location area status is identified at the PCF [122], based on
21

a predefined list of location areas associated with the geo location parameter. The
predefined list of location areas may be maintained by an authority or a network
operator. The PCF [122] may query the predefined list of location areas to identify
the location area status. Each location area of the predefined list of location areas is
5 at least one of a barred location area and a non- barred location area. The barred
location area is identified by the processing unit [302], at the PCF [122], in an event of a geo location associated with the geo location parameter being identified as one of the barred location area based on a comparison of the geo location parameter and the predefined list of location areas. For instance, in a state ABC, the predefined list
10 of location areas comprises- city X (geo location- 1335000, 4532000 to 1620000,
4945000)- barred area, city P (geo location- 0936000, 1215000 to 1155000, 1738000)- non-barred area, city Z (0155000, 3738000 to 0855000, 4429000)- non-barred area. The geo location parameter in the message request is 1430000, 4731000, which is located in city X which is in the barred location area. The barred
15 location area is associated with specific network policies. The barred location area
refers to a geographical location where specific network policies apply. The non-barred location area is an area with unrestricted service access in the network. The non-barred location area refers to a geographical location where specific network policies do not apply.
20
[0072] The processing unit [302] is configured to identify, at the PCF [122], a dedicated SMF based on the geo location parameter. The dedicated SMF refers to a specific SMF assigned to each location area to allow management of users in the barred area and the non-barred area. The dedicated SMF may have a separate
25 configuration for the barred location area from the dedicated SMF for the non-
barred location area. In an implementation of the present disclosure, if the geo location parameter of the UE [102] is located in the barred area, the dedicated SMF may be associated with the barred location area. In another implementation, if the geo location parameter of the UE [102] is located in the non-barred area, the
30 dedicated SMF may be associated with the non-barred location area.
22

[0073] The processing unit [302] is further configured to determine, at the PCF
[122], an attachment status of the UE [102] with the dedicated SMF. To determine
the attachment status of the UE [102] with the dedicated SMF, the processing unit
[302] is further configured to check a session management data stored within the
5 dedicated SMF to confirm if the UE [102] is currently attached or unattached and
perform a real-time query session with the dedicated SMF to verify the current
attachment status of the UE [102]. The session management data includes but may
not be limited to the geo location parameter, the SMF identifier, the TAI, a Quality
of Service (QoS) data, an internet protocol (IP) address associated with the UE
10 [102], and the like. The real time query session refers to a dynamic query to the
dedicated SMF to obtain an update on the attachment status of the UE [102] with the dedicated SMF. The processing unit [302] may perform the real time query on demand of a system operator.
15 [0074] The processing unit [302] is further configured to identify, at PCF [122], a
target message type associated with the message type parameter based on the attachment status. The target message type refers to a message type received at a particular instance of time. The target message type may be received on-demand from the UE [102]. The target message type may be identified based on time of
20 receiving, network traffic, priority, and the like. The target message is one of the
create request message and the update request message. The create message request refers to establishment of a new session in the dedicated SMF. The update message request refers to release of an existing session in the dedicated SMF.
25 [0075] The processing unit [302] is configured to identify, at the PCF [122], one of
a target Tracking Area Identity (TAI) associated with the Tracking Area Identity (TAI) parameter and a target SMF-instance-Id, based on the target message type. In an implementation of the present disclosure, if the location status of the UE [102] is the non-barred area, the processing unit [302] may identify the target TAI
30 associated with the TAI parameter. Whereas, if the location status of the UE [102]
is the barred area, the processing unit [302] may identify the SMF-instance-Id.
23

[0076] The processing unit [302] is furthermore configured to create, at the PCF
[122], a policy decision to manage access for the UE [102], based on the determined
attachment status and one of the target TAI and the target SMF-instance-Id in the
5 message request. The policy decision refers to making a decision for rejecting or
accepting the message request. To create the policy decision, the PCF [122] may evaluate and compare one of the target TAI with the TAI parameter and the target SMF-instance-Id with the dedicated SMF. To create the policy decision, the processing unit [302] is further configured to reject a new session establishment
10 request from the dedicated SMF or release of an existing session if the UE [102] is
in the barring location area and unattached to the dedicated SMF and the UPF [128]. The UPF [122] may have a separate configuration for the barred location area from the UPF [122] for the non-barred location area. In an embodiment, the dedicated SMF and the UPF [122] may operate separately. In another embodiment, the
15 dedicated SMF and the UPF [122] may be configured to operate in a combination.
The operation of the dedicated SMF and the UPF [122] in combination may allow to apply specific set of policies for the barred area and the non-barred area. In an implementation of the present disclosure, to reject the new session establishment request or release of the existing session, if the UE [102] is in the barring location
20 area, the PCF [122] may compare the target SMF-Instance-Id with the dedicated
SMF. If the target SMF-instance-Id is same as the dedicated SMF, the update request message may be accepted and the PCF [122] may release the existing session. In another embodiment, if the target SMF-instance-Id is not same as the dedicated SMF, the update request message may be rejected.
25
[0077] To create the policy decision, the processing unit [302] is further configured to reject a new session establishment request from the dedicated SMF or release of an existing session if the UE [102] is in the non-barring location area and attached to the dedicated SMF and the UPF [122]. In an implementation of the present
30 disclosure, to reject the new session establishment request or release of the existing
session, if the UE [102] is in the non-barring location area, the PCF [122] may
24

compare the target TAI with the TAI parameter. If the target TAI is same as the
TAI parameter, the update request message may be accepted and the PCF [122]
may release the existing session. In another embodiment, if the target SMF-
instance-Id is not same as the dedicated SMF, the update request message may be
5 rejected.
[0078] The processing unit [302] is further configured to discard, at the PCF [122],
the message request in an event when the target message type is the create request
message and initiate monitoring, at the PCF [122], the message request in an event
10 when the target message type is the update request message.
[0079] Referring to FIG. 4, an exemplary method flow diagram [400] for managing access for a User Equipment (UE) in a network, in accordance with exemplary implementations of the present disclosure is shown. In an implementation the
15 method [400] is performed by the system [300]. Further, in an implementation, the
system [300] may be present in a server device to implement the features of the present disclosure. In an implementation of the present disclosure, the network may be a 5th Generation core network. In another implementation, the network may be a 4th Generation network, a 6th Generation network, or any other future generations
20 of network. Also, as shown in FIG. 4, the method [400] starts at step [402].
[0080] At step [404], the method comprises receiving, by a processing unit [302], at a Policy Control Function (PCF [122]) from the UE [102], a message request comprising a set of message parameters. The message request may be a Session
25 Management (SM) update message. The set of message parameters comprises at
least one of a geo location parameter associated with the UE [102], a Session management Function (SMF) instance Identifier (ID) associated with the message request, a User Plane Function (UPF) instance associated with the message request, a message type parameter associated with the message request, and a Tracking Area
30 Identity (TAI) parameter associated with the UE [102]. The geo location parameter
refers to longitudinal and latitudinal position of the UE [102] at a specific time. For
25

example, the geolocation parameters associated with the UE [102] may be 1441000,
23450000 which refers to 14°41.000 North and 23°45.000 East. The message type
parameter includes parameters such as a create message, an update message, a
delete message, and the like. The TAI refers to an identifier assigned to a specific
5 geographical area for tracking and managing the location of the UE [102].
[0081] Next at step [406], the method comprises identifying, by the processing unit
[302] at the PCF [122], a location area status of the UE [102] based on the geo
location parameter. The location area status indicates one of a barred area and a
10 non-barred area. In general, barred area refers to a segment or portion of a network
that has restricted access or is intentionally kept off-limits to certain users or
devices. The non-barred area refers to parts of a network that do not have access
restrictions or are open to users and devices under normal conditions. Generally, a
non-barred area allows for open communication and access. The location area status
15 is identified at the PCF [122], based on a predefined list of location areas associated
with the geo location parameter. The predefined list of location may be maintained
by an authority or a network operator. The PCF [122] may query the predefined list
of location areas to identify the location area status. Each location area of the
predefined list of location areas is at least one of: a barred location area and a non-
20 barred location area. The barred location area is identified by the processing unit
[302], at the PCF [122], in an event of a geo location associated with the geo
location parameter being identified as one of the barred location area based on a
comparison of the geo location parameter and the predefined list of location areas.
For instance, in a state ABC, the predefined list of location comprises- city X (geo
25 location- 1335000, 4532000 to 1620000, 4945000)- barred area, city P (geo
location- 0936000, 1215000 to 1155000, 1738000)- non-barred area, city Z
(0155000, 3738000 to 0855000, 4429000)- non-barred area. The geo location
parameter in the message request is 1430000, 4731000, which is located in city X
which is in the barred location area. The barred location area is associated with
30 specific network policies. The non-barred location area is an area with unrestricted
26

service access in the network. The non-barred location area refers to a geographical location where specific network policies do not apply.
[0082] Next at step [408], the method comprises identifying, by the processing unit
5 [302] at the PCF [122], a dedicated SMF based on the geo location parameter. The
dedicated SMF refers to a combination of the SMF and the UPF instance, assigned to each location area to allow for management of users in the barred area and the non-barred area by applying specific set of policies for the barred area and the non-barred area through the dedicated SMF and the UPF instance. The dedicated SMF
10 for the barred location area may be different from the dedicated SMF for the non-
barred location area. In an implementation of the present disclosure, if the geo location parameter of the UE [102] is located in the barred area, the dedicated SMF may be associated with the barred location area. In another implementation, if the geo location parameter of the UE [102] is located in the non-barred area, the
15 dedicated SMF may be associated with the non-barred location area.
[0083] Next at step [410], the method comprises determining, by the processing unit [302] at the PCF [122], an attachment status of the UE [102] with the dedicated SMF. The determining the attachment status of the UE [102] with the dedicated
20 SMF further comprises checking a session management data stored within the SMF
to confirm if the UE [102] is currently attached or unattached and performing a real¬time query session with the dedicated SMF to verify the current attachment status of the UE [102]. The session management data includes but may not be limited to the geo location parameter, the SMF identifier, the TAI, a Quality of Service (QoS)
25 data, an internet protocol (IP) address associated with the UE [102], and the like.
The real time query session refers to a dynamic query to the dedicated SMF to obtain an update on the attachment status of the UE [102] with the dedicated SMF. The processing unit [302] may perform the real time query on demand of a system operator.
30
27

[0084] Next at step [412], the method comprises identifying, by the processing unit
[302] at PCF [122], a target message type associated with the message type
parameter based on the attachment status. The target message type refers to a
message type received at a particular instance of time. The target message type
5 maybe received on-demand from the UE [102]. The target message type may be
identified based of time of receiving, network traffic, priority, and the like. The
target message is one of a create request message and an update request message.
The create message request refers to establishment of a new session in the dedicated
SMF. The update message request refers to release of an existing session in the
10 dedicated SMF.
[0085] Next at step [414], the method comprises identifying, by the processing unit [302] at the PCF [122], one of a target Tracking Area Identity (TAI) associated with the Tracking Area Identity (TAI) parameter and a target SMF-instance-Id, based on
15 the target message type. In an implementation of the present disclosure, if the
location status of the UE [102] is the non-barred area, the processing unit [302] may identify the target TAI associated with the TAI parameter. Whereas, if the location status of the UE [102] is the barred area, the processing unit [302] may identify the SMF-instance-Id.
20
[0086] Next at step [416], the method comprises creating, by the processing unit [302], at the PCF [122], a policy decision to manage access for the UE [102], based on the determined attachment status and one of the target TAI and the target SMF-instance-Id in the message request. The policy decision refers to making a decision
25 for rejecting or accepting the message request. To create the policy decision, the
PCF [122] may evaluate and compare one of the target TAI with the TAI parameter and the target SMF-instance-Id with the dedicated SMF. The creating the policy decision further comprises rejecting a new session establishment request from the dedicated SMF or releasing of an existing session if the UE [102] is in the barring
30 location area and unattached to the dedicated SMF and a UPF [122]. The UPF [122]
may have a separate configuration for the barred location area from the UPF for the
28

non-barred location area. In an embodiment, the dedicated SMF and the UPF [122]
may operate separately. In another embodiment, the dedicated SMF and the UPF
[122] may be configured to operate in a combination. The operation of the dedicated
SMF and the UPF in combination may allow to apply specific set of policies for the
5 barred area and the non-barred area. The creating the policy decision further
comprises rejecting a new session establishment request from the dedicated SMF or releasing of an existing session if the UE [102] is in the non-barring location area and attached to the dedicated SMF and the UPF [122]. In an implementation of the present disclosure, to reject the new session establishment request or release of the
10 existing session, if the UE [102] is in the barring location area, the PCF [122] may
compare the target SMF-Instance-Id with the dedicated SMF. If the target SMF-instance-Id is same as the dedicated SMF, the update request message may be accepted and the PCF [122] may release the existing session. In another embodiment, if the target SMF-instance-Id is not same as the dedicated SMF, the
15 update request message may be rejected.
[0087] The method further comprises discarding, by the processing unit [302] at
the PCF [122], the message request in an event when the target message type is the
create request message. Furthermore, the method comprises initiating monitoring,
20 by the processing unit [302] at the PCF [122], of the message request in an event
when the target message type is the update request message.
[0088] The method terminates at step [418].
25 [0089] Referring to FIG. 5, an exemplary method [500] for managing access of the
UE [102] in a non-barring location area, in accordance with exemplary implementations of the present disclosure is shown. The exemplary method [500] starts at step [502].
30 [0090] At step [504], based on the message request from the UE [102], the PCF
[122] may identify if the location area status of the UE [102] is the non-barred area.
29

The location area status may be identified based on the geo location parameter in
the message request. In an embodiment, if the location area status of the UE [102]
is the non-barred area, the exemplary method [500] may proceed to step [506]. In
an embodiment, if the location area status of the UE [102] is the barred area, the
5 PCF [122] may continue to operate in normal course.
[0091] At step [506], the PCF [122] may identify if the UE [102] is attached to the
dedicated SMF. If the UE [102] is attached to the dedicated SMF, the step may
proceed to step [510], whereas if the UE [102] is not attached to the dedicated SMF,
10 the step may not proceed to step [508], where the PCF [122] may continue to
function in normal course.
[0092] At step [510], the PCF [122] may check if the message request received
from the UE [102] is the SMF create request message or the SMF update request
15 message.
[0093] If the message request is the SMF create request message, the method may
proceed to step [512] where the PCF [122] may reject the new session establishment
request from the dedicated SMF. If the message request is the SMF update request
20 message, the exemplary method [500] may proceed to step [514], where the PCF
[122] may check if the target TAI is same as a TAI barred.
[0094] If the target TAI is same as the TAI barred, then the exemplary method [500] may proceed to step [518] and the PCF [122] may continue to update the policy
25 decisions. If the target TAI is not same as the TAI barred, the exemplary method
[500] may process to step [516] and the PCF [122] may reject the update message request. In an embodiment, the dedicated SMF may operate in combination with the UPF [122]. The dedicated SMF and the UPF [122] may be separately configured for each location area to allow for management of users in the barred area and the
30 non-barred area by applying specific set of policies for the barred area and the non-
barred area through the combination of the dedicated SMF and the UPF [122]. The
30

dedicated SMF for the barred location area may be different from the dedicated SMF for the non-barred location area.
[0095] Referring to FIG. 6, an exemplary method [600] for managing access of a
5 UE [102] in a barring location area, in accordance with exemplary implementations
of the present disclosure is shown. The exemplary method [600] starts at step [602].
[0096] At step [604], based on the message request, the PCF [122] may identify if the location area status of the UE [102] is the barred area. The location area status
10 may be identified based on the geo location parameter in the message request. In an
embodiment, if the location area status of the UE [102] is the barred area, the exemplary method [600] may proceed to step [606]. If the location area status of the UE [102] is the non-barred area, the exemplary method [600] may proceed to step [605], where the PCF [122] may continue to function in normal course.
15
[0097] At step [606], the PCF [122] may identify if the UE [102] is attached to the dedicated SMF or not. If the dedicated SMF is attached to the UE [102], the exemplary method [600] may proceed to step [608] and the PCF [122] may not take any action. The PCF [122] may continue to operate in normal course of action. If
20 the dedicated SMF is not attached to the UE [102], the PCF [122] needs to take
action, the exemplary method [600] proceeds to step [610].
[0098] At step [610], the PCF [122] may check if the message request received
from the UE [102] is the SMF create request message or the SMF update request
25 message.
[0099] If the message request is the SMF create request message, the exemplary
method [600] may proceed to step [612] where the PCF [122] may reject the new
establishment request from the dedicated SMF. If the message request is the SMF
30 update request message, the exemplary method [600] may proceed to step [614]. At
31

step [614], the PCF [122] may check if the target SMF-instance-Id is same as the dedicated SMF.
[0100] If the target SMF-instance-Id is same as the dedicated SMF, then the
5 exemplary method [600] may proceed to step [6518] where the PCF [122] may
continue to update the policy decisions in the SMF. If the target SMF-instance-Id is not same as the dedicated SMF, the exemplary method [600] may proceed to step [616]. In an embodiment, the dedicated SMF may operate in combination with the UPF [122]. The dedicated SMF and the UPF [122] may be separately configured
10 for each location area to allow for management of users in the barred area and the
non-barred area by applying specific set of policies for the barred area and the non-barred area through the combination of the dedicated SMF and the UPF [122]. The dedicated SMF for the barred location area may be different from the dedicated SMF for the non-barred location area.
15
[0101] At step [616], the PCF [122] may reject the SMF update request.
[0102] The present disclosure further discloses a non-transitory computer readable storage medium storing instructions for managing access for a User Equipment
20 (UE) [102] in a network, the instructions include executable code which, when
executed by one or more units of a system, cause a processing unit [302] of the system to receive, at a Policy Control Function (PCF) [122] from the UE [102], a message request comprising a set of message parameters, wherein the set of message parameters comprises at least one of one of a geo location parameter
25 associated with the UE [102], a Session management Function (SMF) Identifier
associated with the message request, a User Plane Function (UPF) instance associated with the message request a message type parameter associated with the message request, and a Tracking Area Identity (TAI) parameter associated with the UE [102]. The instructions when executed by the system further cause the
30 processing unit [302] to identify, at the PCF [122], a location area status based on
the geo location parameter, wherein the location area status is one of a barred area
32

and a non-barred area. The instructions when executed by the system further cause the processing unit [302] to identify, at the PCF [122], a dedicated SMF based on the geo location parameter. The instructions when executed by the system further cause the processing unit [302] to determine, at the PCF [122], an attachment status of the UE [102] with the dedicated SMF. The instructions when executed by the system further cause the processing unit [302] to identify, at PCF [122], a target message type associated with the message type parameter based on the attachment status. The target message is one of a create request message and an update request message. The instructions when executed by the system further cause the processing unit [302] to identify, at the PCF [122], one of a target Tracking Area Identity (TAI) associated with the Tracking Area Identity (TAI) parameter and a target SMF-instance-Id, based on the target message type. The instructions when executed by the system further cause the processing unit [302] to create, at the PCF [122], a policy decision to manage access for the UE [102], based on the determined attachment status and one of the target TAI and the target SMF-Instance-Id in the message request.
[0103] As is evident from the above, the present disclosure provides a technically advanced solution for managing access for a User Equipment (UE) in a network. The present solution provides a system and a method managing barring requirement effectively via dedicated Session Management Function (SMF) and Tracking Area Identity (TAI) of a UE. The present disclosure further provides a solution to managing barring requirements effectively via dedicated combination of Session Management Function (SMF) and User Plane Function (UPF) [122]. Furthermore, the present disclosure may allocate resources efficiently based on the specific needs of the areas, ensuring that resources are optimized for both barred and non-barred subscribers via the dedicated combination of Session Management Function (SMF) and User Plane Function (UPF) [122] to prevent resource wastage and enhances overall network efficiency. The present disclosure further allows to have a flexible network architecture by deploying the dedicated combination of Session Management Function (SMF) and User Plane Function (UPF) [122] to tailor

specific requirements of diverse geographical location and varied subscriber needs. The present disclosure ensures policy compliance by monitoring the subscribers based on SMF-Instance-Id and TAI combination to ensure that subscribers adhere to network policies and restrictions and maintain regulatory compliance and service quality standards.
[0104] While considerable emphasis has been placed herein on the disclosed implementations, it will be appreciated that many implementations can be made and that many changes can be made to the implementations without departing from the principles of the present disclosure. These and other changes in the implementations of the present disclosure will be apparent to those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.
[0105] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various components/units can be implemented interchangeably. While specific embodiments may disclose a particular functionality of these units for clarity, it is recognized that various configurations and combinations thereof are within the scope of the disclosure. The functionality of specific units as disclosed in the disclosure should not be construed as limiting the scope of the present disclosure. Consequently, alternative arrangements and substitutions of units, provided they achieve the intended functionality described herein, are considered to be encompassed within the scope of the present disclosure.

We Claim:
1. A method [400] for managing access for a User Equipment (UE) [102] in a network, the method [400] comprising:
- receiving, by a processing unit [302], at a Policy Control Function (PCF) [122] from the UE[102], a message request comprising a set of message parameters, wherein the set of message parameters comprises at least one of a geo location parameter associated with the UE [102], a Session management Function (SMF) instance Identifier (ID) associated with the message request, a User Plane Function (UPF) instance associated with the message request, a message type parameter associated with the message request, and a Tracking Area Identity (TAI) parameter associated with the UE [102];
- identifying, by the processing unit [302] at the PCF [122], a location area status of the UE [102] based on the geo location parameter, wherein the location area status indicates one of a barred area and a non-barred area;
- identifying, by the processing unit [302] at the PCF [122], a dedicated SMF based on the geo location parameter;
- determining, by the processing unit [302] at the PCF [122], an attachment status of the UE [102] with the dedicated SMF;
- identifying, by the processing unit [302] at PCF [122], a target message type associated with the message type parameter based on the attachment status, wherein the target message is one of a create request message and an update request message;
- identifying, by the processing unit [302] at the PCF [122], one of: a target Tracking Area Identity (TAI) associated with the Tracking Area Identity (TAI) parameter and a target SMF instance ID, based on the target message type; and
- creating, by the processing unit [302], at the PCF [122], a policy decision to manage access for the UE [102], based on the determined attachment status

and one of the target TAI and the target SMF-Instance-Id in the message request.
2. The method [400] as claimed in claim 1, wherein the location area status is identified at the PCF [122], based on a predefined list of location areas associated with the geo location parameter, wherein each location area of the predefined list of location areas is at least one of: a barred location area and a non- barred location area.
3. The method [400] as claimed in claimed 2, wherein the barred location area is identified by the processing unit [302], at the PCF [122], in an event of a geo location associated with the geo location parameter being identified as one of the barred location area based on a comparison of the geo location parameter and the predefined list of location areas, wherein the barred location area is associated with specific network policies.
4. The method [400] as claimed in claim 2, wherein the non-barred location area is an area with unrestricted service access in the network.
5. The method [400] as claimed in claim 1, wherein determining the attachment status of the UE [102] with the dedicated SMF further comprises:

- checking a session management data stored within the SMF to confirm if the UE [102] is currently attached or unattached; and
- performing a real-time query session with the dedicated SMF to verify the current attachment status of the UE [102].
6. The method [400] as claimed in claim 1, wherein creating the policy decision
further comprises:
- rejecting a new session establishment request from the dedicated SMF or
releasing of an existing session if the UE [102] is in the barring location
area and unattached to the dedicated SMF and a UPF [122].

7. The method [400] as claimed in claim 1, wherein creating the policy decision
further comprises:
- rejecting a new session establishment request from the dedicated SMF or
releasing of an existing session if the UE [102] is in the non-barring
location area and attached to the dedicated SMF and a UPF [122].
8. The method [400] as claimed in claim 1, wherein the method [400] further
comprises:
- discarding, by the processing unit [302] at the PCF [122], the message request in an event when the target message type is the create request message, and
- initiating monitoring, by the processing unit [302] at the PCF [122], of the message request in an event when the target message type is the update request message.
9. A system [300] to manage access for a User Equipment (UE) [102] in a network,
the system comprises:
at least a processing unit [302], wherein the processing unit [302] is configured to:
• receive, at a Policy Control Function (PCF) [122] from the UE [102], a message request comprising a set of message parameters, wherein the set of message parameters comprises at least one of one of a geo location parameter associated with the UE [102], a Session management Function (SMF) Identifier associated with the message request, a User Plane Function (UPF) instance associated with the message request a message type parameter associated with the message request, and a Tracking Area Identity (TAI) parameter associated with the UE[102];
• identify, at the PCF [122], a location area status based on the geo location parameter, wherein the location area status is one of a barred area and a non-barred area;

• identify, at the PCF [122], a dedicated SMF based on the geo location parameter;
• determine, at the PCF [122], an attachment status of the UE [102] with the dedicated SMF;
• identify, at PCF [122], a target message type associated with the message type parameter based on the attachment status, wherein the target message is one of a create request message and an update request message;
• identify, at the PCF [122], one of: a target Tracking Area Identity (TAI) associated with the Tracking Area Identity (TAI) parameter and a target SMF instance ID, based on the target message type; and
• create, at the PCF [122], a policy decision to manage access for the UE [102], based on the determined attachment status and one of the target TAI and the target SMF-Instance-Id in the message request.

10. The system [300] as claimed in claim 9, wherein the location area status is identified at the PCF [122], based on a predefined list of location areas associated with the geo location parameter, wherein each location area of the predefined list of location areas is at least one of: a barred location area and a non- barred location area.
11. The system [300] as claimed in claim 10, wherein the barred location area is identified by the processing unit [302], at the PCF [122], in an event of a geo location associated with the geo location parameter being identified as one of the barred location area based on a comparison of the geo location parameter and the predefined list of location areas, wherein the barred location area is associated with specific network policies.
12. The system [300] as claimed in claim 10, wherein the non-barred location area is an area with unrestricted service access in the network.

13. The system [300] as claimed in claim 9, wherein to determine the attachment
status of the UE [102] with the dedicated SMF, the processing unit [302] is further
configured to:
check a session management data stored within the SMF to confirm if the UE [102] is currently attached or unattached; and
perform a real-time query session with the dedicated SMF to verify the current attachment status of the UE [102].
14. The system [300] as claimed in claim 9, wherein to create the policy decision, the
processing unit [302] is further configured to:
- reject a new session establishment request from the dedicated SMF or
release of an existing session if the UE [102] is in the barring location area
and unattached to the dedicated SMF and the UPF instance.
15. The system [300] as claimed in claim 9, wherein to create the policy decision, the
processing unit [302] is further configured to:
- reject a new session establishment request from the dedicated SMF or
release of an existing session if the UE [102] is in the non-barring location
area and attached to the dedicated SMF and the UPF instance.
16. The system [300] as claimed in claim 9, wherein the system further comprises the
processing unit [302] configured to:
- discard, at the PCF [122], the message request in an event when the target message type is the create request message, and
- initiate monitor, at the PCF [122], the message request in an event when the target message type is the update request message.