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 HANDLING LOCATION REQUESTS IN A WIRELESS COMMUNICATION
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 HANDLING LOCATION REQUESTS IN A WIRELESS COMMUNICATION NETWORK
TECHNICAL FIELD
[0001] Embodiments of the present disclosure generally relate to network performance management systems. More particularly, embodiments of the present disclosure relate to handling location requests in a wireless communication 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] Moreover, the 5G core networks are based on service-based architecture (SBA) that is centered around network function (NF) services. In said Service-Based Architecture (SBA), a set of interconnected Network Functions (NFs) delivers the control plane functionality and common data repositories of the 5G network, where each NF is authorized to access the services of other NFs. Particularly, each NF can register itself and its supported services to a Network Repository Function (NRF), which is further used by other NFs for the discovery of NF instances and their services. The NRF therefore supports functions related to 1) maintaining the profiles of the available network function (NF) instances and their supported services in the 5G core network, 2) allowing NF instances to discover other NF instances in the 5G core network, and 3) allowing the NF instances to track the status of other NF instances. Also, Gateway Mobile Location Centre (GMLC) is a network entity in the 5G Core Network (5GC) supporting Location Services (LCS). Within the 5GC, the GMLC offers services to access and mobility management function (AMF) and Network Exposure Function (NEF) via Ngmlc service-based interface. In addition, a ProvideLocation service operation is invoked by a NF service consumer, (e.g., NEF, GMLC, etc.), towards the GMLC to request location information for a target UE.
[0005] In existing systems, in an event where the 5G-GMLC (or referred herein as GMLC) receives a location request from a Lawful Interception Management (LIM) client, the GMLC fetches an access token for the AMF from the NRF to cater to the location request. As the GMLC receives multiple location requests, which further leads to fetching of various access tokens from the NRF, more latency is added in the network.
[0006] Thus, there exists an imperative need in the art to provide an efficient and effective system and method to handle location requests in wireless communication

networks and overcome the limitations of the existing technologies, which the present disclosure aims to address.
SUMMARY
[0007] 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.
[0008] An aspect of the present disclosure may relate to a method for handling location requests in a wireless communication network. The method comprises transmitting, by a transceiver unit connected to at least a gateway mobile location centre (GMLC), an access token request to a network repository function (NRF). The method further comprises receiving, by the transceiver unit at the GMLC, a first access token from the NRF, in response to the access token request. Furthermore, the method comprises storing, by a storage unit connected at least to the transceiver unit, at a token database connected at least to the GMLC, the received first access token. The method further comprises determining, by a processing unit connected at least to the token database, at a predefined frequency of time, a status of the stored first access token. The status comprises one of an expired status and an active status. In response to the status of the stored first access token being the active status, the method comprises accessing, by the processing unit, the stored first access token in response to a location request from the GMLC.
[0009] In an exemplary aspect of the present disclosure, the location request is received by the GMLC and relates to retrieval of location data of a user equipment (UE).

[0010] In an exemplary aspect of the present disclosure, the first access token relates to a set of configurations that facilitate the GMLC to establish a connection with an access and mobility management function (AMF).
[0011] In an exemplary aspect of the present disclosure, in response to the status of the stored first access token being the expired status, the method comprises transmitting, by the transceiver unit, an access token request to the NRF. Further, the method comprises receiving, by the transceiver unit at the GMLC, a second access token from the NRF, in response to the access token request. Furthermore, the method comprises storing, by a storage unit, at the token database, the received second access token. The received second access token is re-written on the first access token.
[0012] In an exemplary aspect of the present disclosure, the GMLC is a 5G-GMLC.
[0013] In an exemplary aspect of the present disclosure, the step of transmitting, by the transceiver unit, the access token request to the NRF occurs at startup of the GMLC.
[0014] In an exemplary aspect of the present disclosure, the location request is received from a Lawful Interception Management (LIM) client.
[0015] Another aspect of the present disclosure may relate to a system for handling location requests in a wireless communication network. The system comprises a transceiver unit connected to at least a gateway mobile location centre (GMLC). The transceiver unit is configured to transmit an access token request to a network repository function (NRF). The transceiver unit is further configured to receive a first access token from the NRF, in response to the access token request. The system further comprises a storage unit connected at least to the transceiver unit. The storage unit is configured to store, at a token database connected at least to the GMLC, the received first access token. Furthermore, the system comprises a

processing unit connected at least to the token database. The processing unit is configured to determine, at a predefined frequency of time, a status of the stored first access token. The status comprises one of an expired status and an active status. In response to the status of the stored first access token being the active status, the processing unit is configured to access the stored first access token in response to a location request from the GMLC.
[0016] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for handling location requests in a wireless communication network, the instructions include executable code which, when executed by one or more units of a system, cause a transceiver unit of the system, connected to at least a gateway mobile location centre (GMLC), to transmit an access token request to a network repository function (NRF). The instructions, when executed by the system further causes the transceiver unit at the GMLC to receive a first access token from the NRF, in response to the access token request. The instructions, when executed by the system further causes a storage unit, connected at least to the transceiver unit, to store, at a token database connected at least to the GMLC, the received first access token. The instructions, when executed by the system further causes a processing unit connected at least to the token database, to determine, at a predefined frequency of time, a status of the stored first access token. The status comprises one of an expired status and an active status. The instructions, when executed by the system further causes the processing unit to access the stored first access token in response to a location request from the GMLC in response to the status of the stored first access token being the active status.
OBJECTS OF THE INVENTION
[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 for handling location requests in wireless communication networks based on pre-configuration or storage of access token(s).
5 [0019] It is another object of the present disclosure to provide a solution to reduce
latency in the network.
[0020] It is yet another object of the present disclosure to provide a solution to pre-configure or store access token in database. 10
DESCRIPTION OF THE DRAWINGS
[0021] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods
15 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
20 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 drawings includes disclosure of electrical components or circuitry commonly used to implement such components.
25 [0022] FIG. 1 illustrates an exemplary block diagram representation of 5th
generation core (5GC) network architecture.
[0023] 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
30 exemplary implementation of the present disclosure.
7

[0024] FIG. 3 illustrates an exemplary block diagram of a system for handling location requests in a wireless communication network, in accordance with exemplary implementations of the present disclosure.
5 [0025] FIG. 4 illustrates a process flow diagram for handling location requests in
the wireless communication network, in accordance with exemplary implementations of the present disclosure.
[0026] FIG. 5 illustrates a method flow diagram for handling location requests in
10 the wireless communication network, in accordance with exemplary
implementations of the present disclosure.
[0027] The foregoing shall be more apparent from the following more detailed description of the disclosure. 15
DETAILED DESCRIPTION
[0028] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of
20 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 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
25 problems discussed above.
[0029] 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
30 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
8

arrangement of elements without departing from the spirit and scope of the disclosure as set forth.
[0030] Specific details are given in the following description to provide a thorough
5 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, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail.
10
[0031] 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 may be performed in parallel or
15 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.
[0032] The word “exemplary” and/or “demonstrative” is used herein to mean
20 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
25 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.
30
9

[0033] As used herein, a “processing unit” or “processor” or “operating processor”
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
5 of microprocessors, one or more microprocessors in association with a (Digital
Signal Processing) DSP core, a controller, a microcontroller, Application Specific
Integrated Circuits, Field Programmable Gate Array circuits, any other type of
integrated circuits, etc. The processor may perform signal coding data processing,
input/output processing, and/or any other functionality that enables the working of
10 the system according to the present disclosure. More specifically, the processor or
processing unit is a hardware processor.
[0034] 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”,
15 “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 user equipment/device may include, but is not limited to, a mobile phone, smart phone, laptop, a general-purpose computer, desktop, personal digital assistant,
20 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 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.
25
[0035] As used herein, “storage unit” or “memory unit” refers to a machine or computer-readable medium including any mechanism for storing information in a form readable by a computer or similar machine. For example, a computer-readable medium includes read-only memory (“ROM”), random access memory (“RAM”),
30 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
10

that may be required by one or more units of the system to perform their respective functions.
[0036] As used herein “interface” or “user interface” refers to a shared boundary
5 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 communication or interaction of one or more modules or one or more units with each other, which also includes the methods, functions, or procedures that may be called.
10
[0037] All modules, units, components used herein, unless explicitly excluded 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
15 microprocessors in association with a DSP core, a controller, a microcontroller,
Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.
[0038] As used herein the transceiver unit include at least one receiver and at least
20 one transmitter configured respectively for receiving and transmitting data, signals,
information or a combination thereof between units/components within the system and/or connected with the system.
[0039] As discussed in the background section, the current known solutions have
25 several shortcomings. The present disclosure aims to overcome the above-
mentioned and other existing problems in this field of technology by providing a method and system of handling location requests in a wireless communication network.
30 [0040] FIG. 1 illustrates an exemplary block diagram representation of 5th
generation core (5GC) network architecture, in accordance with exemplary
11

implementation of the present disclosure. As shown in FIG. 1, the 5GC network
architecture [100] 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],
5 an Authentication Server Function (AUSF) [112], a Network Slice Specific
Authentication and Authorization Function (NSSAAF) [114], a Network Slice
Selection Function (NSSF) [116], a Network Exposure Function (NEF) [118], a
Network Repository Function (NRF) [120], a Policy Control Function (PCF) [122],
a Unified Data Management (UDM) [124], an application function (AF) [126], a
10 User Plane Function (UPF) [128], a data network (DN) [130], a gateway mobile
location centre (GMLC) [140], a Location Client Service (LCS) [142], 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.
15 [0041] 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 wireless communication.
20
[0042] 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 procedures like handovers and paging.
25
[0043] 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 (UPF) for data forwarding and handles IP address allocation and QoS enforcement.
30
12

[0044] 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 service-based interfaces. 5
[0045] 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.
10 [0046] 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.
15 [0047] 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.
[0048] The Network Exposure Function (NEF) [118] is a network function that
20 exposes capabilities and services of the 5G network to external applications,
enabling integration with third-party services and applications.
[0049] The Network Repository Function (NRF) [120] is a network function that
acts as a central repository for information about available network functions and
25 services. It facilitates the discovery and dynamic registration of network functions.
[0050] The Policy Control Function (PCF) [122] is a network function responsible for policy control decisions, such as QoS, charging, and access control, based on subscriber information and network policies. 30
13

[0051] The Unified Data Management (UDM) [124] is a network function that centralizes the management of subscriber data, including authentication, authorization, and subscription information.
5 [0052] 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.
[0053] The User Plane Function (UPF) [128] is a network function responsible for
10 handling user data traffic, including packet routing, forwarding, and QoS
enforcement.
[0054] The Data Network (DN) [130] refers to a network that provides data
services to user equipment (UE) in a telecommunications system. The data services
15 may include but are not limited to Internet services, private data network related
services.
[0055] The gateway mobile location centre (GMLC) [140] is a first network in the
5G network architecture [100] which is accessed by an external location
20 application. The GMLC [140] is responsible for performing registration,
authorization and requests routing information and receive request for UE location information. The GMLC is connected to AMF [106] over NL2 interface.
[0056] The location client service (LCS) [142] is used to facilitate information
25 exchange related to as user equipment (UE) location within the network elements.
It uses various interfaces such as but not limited to NLs, NLg and NLh interfaces to interact with the AMF [106] and UDM [124].
[0057] The 5GC network architecture also comprises a plurality of interfaces for
30 connecting the network functions with a network entity for performing the network
functions. The NSSF [116] is connected with the network entity via the interface
14

denoted as (Nnssf) interface in the figure. The NEF [118] is connected with the
network entity via the interface denoted as (Nnef) interface in the figure. The NRF
[120] is connected with the network entity via the interface denoted as (Nnrf)
interface in the figure. The PCF [122] is connected with the network entity via the
5 interface denoted as (Npcf) interface in the figure. The UDM [124] is connected
with the network entity via the interface denoted as (Nudm) interface in the figure. The AF [126] is connected with the network entity via the interface denoted as (Naf) interface in the figure. The NSSAAF [114] is connected with the network entity via the interface denoted as (Nnssaaf) interface in the figure. The AUSF [112] is
10 connected with the network entity via the interface denoted as (Nausf) interface in
the figure. The AMF [106] is connected with the network entity via the interface denoted as (Namf) interface in the figure. The SMF [108] is connected with the network entity via the interface denoted as (Nsmf) interface in the figure. The SMF [108] is connected with the UPF [128] via the interface denoted as (N4) interface
15 in the figure. The UPF [128] is connected with the RAN [104] via the interface
denoted as (N3) interface in the figure. The UPF [128] is connected with the DN [130] via the interface denoted as (N6) interface in the figure. The RAN [104] is connected with the AMF [106] via the interface denoted as (N2). The AMF [106] is connected with the RAN [104] via the interface denoted as (N1). The UPF [128]
20 is connected with other UPF [128] via the interface denoted as (N9). The interfaces
such as Nnssf, Nnef, Nnrf, Npcf, Nudm, Naf, Nnssaaf, Nausf, Namf, Nsmf, N9, N6, N4, N3, N2, and N1 can be referred to as a communication channel between one or more functions or modules for enabling exchange of data or information between such functions or modules, and network entities.
25
[0058] FIG. 2 illustrates an exemplary block diagram of a computing device [200] upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure. In an implementation, the computing device [200] may also implement a method for
30 handling location requests in a wireless communication network, utilising the
system. In another implementation, the computing device [200] itself implements
15

the method for handling location requests in a wireless communication network, using one or more 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. 5
[0059] The computing device [200] may include a bus [202] or other communication mechanism for communicating information, and a hardware processor [204] coupled with bus [202] for processing information. The hardware processor [204] may be, for example, a general-purpose microprocessor. The
10 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 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
15 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 (ROM) [208] or other static storage device coupled to the bus [202] for storing static
20 information and instructions for the processor [204].
[0060] 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 instructions. The computing device [200] may be coupled via the bus [202] to a
25 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 bus [202] for communicating information and command selections to the processor
30 [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
16

information and command selections to the processor [204], and for controlling cursor movement on the display [212]. This input device typically has two degrees 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. 5
[0061] The computing device [200] may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware 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.
10 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 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
15 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.
20 [0062] 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 integrated services digital network (ISDN) card, cable modem, satellite modem, or
25 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 implementation, the communication interface [218] sends and receives electrical,
30 electromagnetic or optical signals that carry digital data streams representing
various types of information.
17

[0063] The computing device [200] can send messages and receive data, including
program code, through the network(s), the network link [220] and the
communication interface [218]. In the Internet example, a server [230] might
5 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, and/or stored in the storage device [210], or other non-volatile storage for later execution.
10
[0064] 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] (as shown in FIG. 2). It is further noted that the computing device [200] is able to perform the steps of a method [400] (as shown in FIG. 4).
15
[0065] Referring to FIG. 3, an exemplary block diagram of a system [300] for handling location requests in a wireless communication network is shown, in accordance with the exemplary implementations of the present disclosure. The system [300] comprises at least one transceiver unit [302], at least one storage unit
20 [304], and at least one processing unit [306]. 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 FIG. 3, all units shown within the system [300] 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 units or the system
25 [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 as a UE). In
30 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/
18

network entity and partly in the user device. The system [300] is configured for handling location requests in the wireless communication network, with the help of the interconnection between the components/units of the system [300].
5 [0066] FIG. 4 illustrates a process flow diagram [400] for handling location
requests in the wireless communication network, in accordance with exemplary implementations of the present disclosure. Further, the system [300] is intended to be read in conjunction with the process flow diagram [400] as shown in FIG. 4.
10 [0067] The system [300] comprises the transceiver unit [302] connected to at least
a gateway mobile location centre (GMLC) [402]. The transceiver unit [302] is configured to transmit an access token request to a network repository function (NRF) [120] via Nnrf_AccessToken service offered by the NRF. In one implementation, the GMLC [402] is a 5G-GMLC. In general, Gateway Mobile
15 Location Centre (GMLC) is the network entity in the 5G Core Network (5GC) that
supports Location Services (LCS). Within the 5GC, the GMLC [402] may offer the location services to the AMF [106] and the NEF [118] via a Ngmlc service-based interface. The step of transmitting the access token request to the NRF [120] occurs at startup of the GMLC [402]. The access token request includes but may not be
20 limited to a scope parameter, a NF Instance ID of a NF service consumer, a NF
Instance ID of a NF service producer, a NF type of NF service consumer, a NF type of NF service producer, and a Public Land Mobile Network (PLMN) ID.
[0068] The scope parameter herein may refer to the name of the NF that the NF
25 service consumer is trying to access. The NF Instance ID of the NF service
consumer refers to an identifier of the instance of a network function (NF)
requesting the access token. The NF Instance ID of the NF service producer refers
to an identifier of the instance of the NF providing the access token. In one example,
the NF Instance ID may be included where the access token request is for a specific
30 NF service producer requesting services offered by the consumer (i.e., GMLC).
19

[0069] The NF type of the NF service consumer refers to a type of the NF
requesting the access token. The NF type of the NF service producer refers to a type
of the NF providing the access token. The access token request may additionally
include a NF set ID of the NF service producer, where the access token request is
5 not for a specific NF service producer.
[0070] The transceiver unit [302] is further configured to receive a first access
token from the NRF [120], in response to the access token request. The first access
token relates to a set of configurations that facilitate the GMLC [402] to establish a
10 connection with an access and mobility management function (AMF) [106]. The
first access token includes but may not be limited to a requested access token and a token type of the first access token.
[0071] The system [300] further comprises a storage unit [304] connected at least
15 to the transceiver unit [302]. The storage unit [304] is configured to store, at a token
database [406] connected at least to the GMLC [402], the received first access token.
[0072] The system [300] further comprises a processing unit [306] connected at
20 least to the token database [406]. The processing unit [306] is configured to
determine, at a predefined frequency of time, a status of the stored first access token.
The status comprises one of an expired status and an active status. In one
implementation, when the first access token is stored in the token database [406],
the processing unit [306] is configured to implement a timer. In some examples, the
25 timer may be configured by a system operator or a network operator. For example,
the system operator may implement the timer of 5 minutes. Then, as soon as the
first access token is received, the processing unit [306] is configured to start the
timer. The timer may record a remaining time of the active status of the first access
token.
30
20

[0073] The predefined frequency of time to determine the status of the first access token (i.e., to implement the timer) by the GMLC [402] may be defined by the system operator or the network operator. In response to determining the status of the stored first access token being the active status, the processing unit [306] is configured to access the stored first access token in response to a location request from the GMLC [402]. The location request is received by the GMLC [402] and relates to retrieval of location data of a user equipment (UE). The location request is received from a Lawful Interception Management (LIM) client. The LIM client [504] acts as a component within the LIM, wherein external networks or network operators or network providers are required to collect and provide location information of its consumers for a lawful security process based on lawful requests.
[0074] In an implementation, if the remaining time of the timer for the first access token is more than 0 when the transceiver unit [302] of the GMLC [402] queries the token database [406], the processing unit [306] may send the status as the active status. If the status of the first access token is the active status and the GMLC [402] receives the location request, the GMLC [402] may use the already stored access token to communicate with the AMF [106] rather than requesting for a new access token from the LIM [404] for every location request at the GMLC [402]. In an implementation, when the LIM [404] requires a location and sends the location request to the GMLC [402], the location may include the stored access token. The access token may serve as a proof of the GMLC’s [402] authorization to access the location requested in the location request.
[0075] In response to the status of the stored first access token being the expired status, the transceiver unit [302] is configured to transmit an access token request to the NRF [120] and receive a second access token from the NRF [120], in response to the access token request. In case the remaining time of the first access token in the timer is 0 when the GMLC [402] queries the token database [406], the processing unit [306] may send the status as the expired status. Further, the storage unit [304] is configured to store, at the token database [406], the received second

access token. The received second access token is re-written on the first access token.
[0076] Referring to FIG. 4, when the GMLC [402] starts up, the GMLC [402] may fetch the access token request from the Lawful Interception Management (LIM) [504]. In an implementation, the GMLC [402] is a 5G-GMLC. The GMLC [402] may be for 6th generation or any other future generations of the network. The access token request includes but may not be limited to a scope parameter, a NF Instance ID of a NF service consumer, a NF Instance ID of a NF service producer, a NF type of NF service consumer, a NF type of NF service producer, and a Public Land Mobile Network (PLMN) ID.
[0077] The LIM [404] may provide an access token based on the access token request to the GMLC [402]. The GMLC [402] may store the access token in the token database [406]. The GMLC [402] may be configured to query the token database [406] at pre-defined frequency of time to check the status of the stored access token. The status may be one of the active status or the expired status.
[0078] In an implementation, if the status of the access token is the active status and the GMLC [402] receives the location request, the GMLC [402] may use the stored access token to communicate with the AMF [106] rather than requesting an access token from the LIM [404] for every location request at the GMLC [402].
[0079] In another implementation, if the status of the access token is the expired status, the GMLC [402] may send a second access token request to the LIM [404]. In an embodiment, the GMLC [402] may receive a second access token from the NRF [120], in response to the access token request.
[0080] Referring to FIG. 5, an exemplary method flow diagram [500] for handling location requests in the wireless communication network, in accordance with

exemplary implementations of the present disclosure is shown. In an implementation, the method [500] is performed by the system [300].
[0081] The method [500] starts at step [502].
[0082] At step [504], the method comprises transmitting, by the transceiver unit [302] connected to at least the gateway mobile location centre (GMLC) [402], the access token request to the network repository function (NRF) [120]. The GMLC [402] is a 5G-GMLC [402]. In an implementation of the present disclosure, the Gateway Mobile Location Centre (GMLC) [402] is the network entity in the 5G Core Network (5GC) that may support Location Services (LCS). Within, the 5GC, the GMLC [402] may offer the location services to the AMF [106] and the NEF [118] via a Ngmlc service-based interface. The step of transmitting, by the transceiver unit [302], the access token request to the NRF [120] occurs at startup of the GMLC [402].
[0083] At step [506], the method comprises receiving, by the transceiver unit [302] at the GMLC [402], the first access token from the NRF [120], in response to the access token request. The first access token relates to a set of configurations that facilitate the GMLC [402] to establish a connection with the access and mobility management function (AMF) [106].
[0084] Further at step [508], the method comprises storing, by a storage unit [304] connected at least to the transceiver unit [302], at the token database [406] connected at least to the GMLC [402], the received first access token.
[0085] Further at step [510], the method comprises determining, by the processing unit [306] connected at least to the token database [406], at a predefined frequency of time, the status of the stored first access token. The status comprises one of an expired status and an active status.

[0086] Further at step [512], in response to the status of the stored first access token being the active status, the method comprises accessing, by the processing unit [306], the stored first access token in response to a location request from the GMLC [402]. The location request is received by the GMLC [402] and relates to retrieval of location data of a user equipment (UE).
[0087] The method [500] terminates at step [514].
[0088] The present disclosure further discloses a non-transitory computer readable storage medium storing instructions for handling location requests in a wireless communication network, the instructions include executable code which, when executed by one or more units of the system [300], causes the transceiver unit [302] of the system [300], connected to at least the gateway mobile location centre (GMLC) [402] to transmit an access token request to the network repository function (NRF) [120]. The instructions when executed by the system [300] further cause the transceiver unit [302] to receive a first access token from the NRF [120], in response to the access token request. The instructions when executed by the system [300] further causes the storage unit [304], connected at least to the transceiver unit [302], to store, at the token database [406] connected at least to the GMLC [402], the received first access token. The instructions when executed by the system [300] further causes the processing unit [306] connected at least to the token database [406], to determine, at the predefined frequency of time, the status of the stored first access token. The status comprises one of an expired status and an active status. The instructions when executed by the system [300] further causes the processing unit [306] to access the stored first access token in response to the location request from the GMLC [402] in response to the status of the stored first access token being the active status.
[0089] As is evident from the above, the present disclosure provides a technically advanced solution for handling location requests in a wireless communication network. The present disclosure provides a system and a method for handling

location requests in the wireless communication network based on pre-configuration or storage of access token(s). The present disclosure further provides a solution that can reduce latency in the network that may have occurred due to fetching access tokens from the NRF multiple times for the AMF to cater multiple provide location requests. The present disclosure further provides a solution that can pre-configure or store access token to communicate with AMF rather than fetching access token for the AMF from NRF in every provided location request coming at GMLC. Further, the present disclosure provides a solution that can exclude get access token request from NRF to communicate with AMF in every location request.
[0090] 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.
[0091] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various the 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 for handling location requests in a wireless communication
network, the method comprising:
- transmitting, by a transceiver unit [302] connected to at least a gateway mobile location centre (GMLC) [402], an access token request to a network repository function (NRF) [120];
- receiving, by the transceiver unit [302] at the GMLC [402], a first access token from the NRF [120], in response to the access token request;
- storing, by a storage unit [304] connected at least to the transceiver unit [302], at a token database [406] connected at least to the GMLC [402], the received first access token; and
- determining, by a processing unit [306] connected at least to the token database [406], at a predefined frequency of time, a status of the stored first access token, wherein the status comprises one of an expired status and an active status;
wherein, in response to the status of the stored first access token being the active status, the method comprises:
- accessing, by the processing unit [306], the stored first access token in response to a location request from the GMLC [402].
2. The method as claimed in claim 1, wherein the location request is received by the GMLC [402] and relates to retrieval of location data of a user equipment (UE).
3. The method as claimed in claim 1, wherein the first access token relates to a set of configurations that facilitate the GMLC [402] to establish a connectivity with an access and mobility management function (AMF) [106].

4. The method as claimed in claim 1, wherein, in response to the status of the
stored first access token being the expired status, the method comprises:
- transmitting, by the transceiver unit [302], an access token request to the NRF [120];
- receiving, by the transceiver unit [302] at the GMLC [402], a second access token from the NRF [120], in response to the access token request; and
- storing, by a storage unit [304], at the token database [406], the received second access token, wherein the received second access token is re-written on the first access token.

5. The method as claimed in claim 1, wherein the GMLC [402] is a 5G-GMLC.
6. The method as claimed in claim 1, wherein the step of transmitting, by the transceiver unit [302], the access token request to the NRF [120] occurs at startup of the GMLC [402].
7. The method as claimed in claim 1, wherein the location request is received from a lawful interception management (LIM) client [504].
8. A system for handling location requests in a wireless communication network, the system comprising:
- a transceiver unit [302] connected to at least a gateway mobile
location centre (GMLC) [402], the transceiver unit [302] configured
to:
- transmit an access token request to a network repository function (NRF) [120]; and

- receive a first access token from the NRF [120], in response
to the access token request;
- a storage unit [304] connected at least to the transceiver unit [302], the storage unit [304] configured to store, at a token database [406] connected at least to the GMLC [402], the received first access token; and
- a processing unit [306] connected at least to the token database [406], the processing unit [306] configured to:
- determine, at a predefined frequency of time, a status of the
stored first access token, wherein the status comprises one of
an expired status and an active status, and
wherein, in response to the status of the stored first access token being the active status,
- access the stored first access token in response to a location request from the GMLC [402].
9. The system as claimed in claim 8, wherein the location request is received by the GMLC [402], and relates to retrieval of location data of a user equipment (UE).
10. The system as claimed in claim 8, wherein the first access token relates to a set of configurations that facilitate the GMLC [402] to establish a connectivity with an access and mobility management function (AMF) [106].
11. The system as claimed in claim 8, wherein, in response to the status of the stored first access token being the expired status:
- the transceiver unit [302] is configured to:
- transmit an access token request to the NRF [120]; and

- receive a second access token from the NRF [120], in response to the access token request; and - the storage unit [304] is configured to store, at the token database [406], the received second access token, wherein the received second access token is re-written on the first access token.
12. The system as claimed in claim 8, wherein the GMLC [402] is a 5G-GMLC.
13. The system as claimed in claim 8, wherein the step of transmitting the access token request to the NRF [120] occurs at startup of the GMLC [402].
14. The system as claimed in claim 8, wherein the location request is received from a lawful interception management (LIM) client [504].