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 DETERMINING A POSITIONING METHOD FOR A UE 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 DETERMINING A POSITIONING METHOD FOR A UE IN A NETWORK
FIELD OF THE DISCLOSURE
[0001] Embodiments of the present disclosure generally relate to wireless communication. More particularly, embodiments of the present disclosure relate to determining a positioning method 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] Positioning functionality provides a means to determine the geographic position and/or velocity of a mobile device or a user equipment (UE), based on measuring radio signals. The position information may be requested by and reported to a client (e.g., an application) associated with the UE, or by a client within or attached to the core network. The position information shall be reported in standard formats, such as those for cell-based or geographical co-ordinates, together with the estimated errors (uncertainty) of the position and velocity of the UE and, if available, the positioning method (or the list of the methods) used to obtain the position estimate. The uncertainty of the position information is dependent on the method used, the position of the UE within the coverage area and the activity of the UE. Several design options of the NG-RAN (Next Generation Radio Access Network) system (e.g., size of cell, adaptive antenna technique, pathloss estimation, timing accuracy) shall allow a network operator to choose a suitable and cost-effective UE positioning method for their market.
[0005] The NG-RAN may utilise one or more positioning methods in order to determine the position of a UE. Positioning the UE involves two main steps: signal measurements; and position estimate and optional velocity computation based on the measurements. The signal measurements may be made by the UE or by the serving enhanced 4G eNodeB (ng-eNB) or gNodeB (gNB). The basic signals measured for terrestrial position methods are typically the LTE (Long-Term Evolution) or NR (New Radio) radio transmissions; however, other methods may make use of other transmissions such as general radio navigation signals including those from Global Navigation Satellites Systems (GNSSs). The positioning function should not be limited to a single method or measurement. That is, it should be capable of utilising other standard methods and measurements, as such methods and measurements are available and appropriate, to meet the required service needs of the location service client. This additional information could consist of readily

available Evolved-UMTS Terrestrial Radio Access Network (E-UTRAN) or NG-RAN measurements. E-UTRAN is the air interface in an LTE cellular network. Further, E-UTRAN governs the base station.
[0006] In the 5G positioning framework, the location management function (LMF) is a central entity to estimate UE position based on assistance/measurements from next-generation (NG)-RAN and UE through the access and mobility management function (AMF). The Location Management Function (LMF) is the network entity in the 5G Core Network (5GC) supporting the following functionality:
- Supports location determination for a UE.
- Obtains downlink location measurements or a location estimate from the UE
- Obtains uplink location measurements from the NG RAN
- Obtains non-UE associated assistance data from the NG RAN.
[0007] During the UE positioning process, the LMF first identifies the positioning methods and invokes the positioning tasks in the UEs and the related base stations in the NG-RAN. Then, the LMF collects the positioning measurements from the corresponding terminals and determines a final position estimation result for location services.
[0008] The 5G positioning methods, in general, are derived from timing, angular, power-based techniques, and their combinations. The standard positioning methods supported for NG-RAN access are:
network-assisted GNSS methods
observed time difference of arrival (OTDOA) positioning based on LTE
signals
enhanced cell ID (E-CID) methods based on LTE signals
WLAN positioning
Bluetooth positioning
terrestrial beacon system (TBS) positioning

sensor-based methods such as, barometric Pressure Sensor and motion sensor
NR enhanced cell ID methods (NR E-CID) based on NR signals Multi-Round Trip Time Positioning (Multi-RTT based on NR signals) Downlink Angle-of-Departure (DL-AoD) based on NR signals Downlink Time Difference of Arrival (DL-TDOA) based on NR signals Uplink Time Difference of Arrival (UL-TDOA) based on NR signals Uplink Angle-of-Arrival (UL-AoA), including A-AoA and Z-AoA based on NR signals.
[0009] These positioning methods may be supported in UE-based, UE-assisted/LMF-based, and NG-RAN node assisted versions. For example, GNSS based positioning method is supported by UE based and LMF based versions, but not supported by NG-RAN node assisted versions. Also, E-CID positioning method is supported by NG-RAN node assisted versions but is not supported by UE based versions.
[0010] Whenever LMF receives a location determination request, it uses Quality of Service (QoS) information to check the availability of positioning methods. But, if any defined positioning method is not supported by UE or gNB, then LMF gives a failure response. The existing solutions fail to provide at least a low-level accuracy positioning if no positioning method is supported.
[0011] Thus, there exists an imperative need in the art to provide a fallback mechanism that provides at least a low accuracy positioning method if there is any kind of failure UE or gNB, which the present disclosure aims to address.
SUMMARY
[0012] 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.
[0013] An aspect of the present disclosure may relate to a method for determining a positioning of a User Equipment (UE) in a network. The method comprises loading, by a loading unit at a location server, a plurality of positioning methods. The plurality of positioning methods comprises at least a primary positioning method and a set of fall-back positioning methods. The method further comprises receiving, by a transceiver unit at the location server, a location request associated with a service from the UE. The location request relates to determining a location of the UE. Furthermore, the method comprises selecting, by an execution unit at the location server, a first positioning method from the plurality of positioning methods based on the location request. The method further comprises selecting, by the execution unit at the location server, a fall-back positioning method from the set of fall-back positioning methods, in an event the first positioning method is associated with a non-supported status. Further, the method comprises repeating, by the execution unit, for one or more remaining fall-back positioning methods from the set of fall-back positioning methods, selection of a next fall-back positioning method in an event the selected fall-back positioning method is associated with a non-supported status. The method further comprises selecting, by the execution unit at the location server, a cell identifier (Cell-ID) based positioning method in an event each of the selected fall-back positioning methods from the set of fall-back positioning methods is associated with a non-supported status.
[0014] In an exemplary aspect of the present disclosure, each of the plurality of positioning methods is based on one of a service identifier (Service ID) associated with the service and a quality of service (QoS) information associated with the location request.
[0015] In an exemplary aspect of the present disclosure, post the receiving of the location request associated with the service from the UE, the method comprises

checking, by a processing unit at the location server, an availability of at least one of the service ID and the QoS information in the received location request.
[0016] In an exemplary aspect of the present disclosure, the first positioning method is the primary positioning method, in an event the location request comprises the Service ID.
[0017] In an exemplary aspect of the present disclosure, the location server is a location management function (LMF).
[0018] In an exemplary aspect of the present disclosure, prior to the selecting, by the execution unit, the first positioning method from the plurality of positioning methods, the method comprises determining, by the execution unit, one of a supported status and the non-supported status, associated with the first positioning method, wherein the supported status refers to the first positioning method being supported by at least one of the UE and a base station, and the non-supported status refers to the first positioning method being not supported by the UE and the base station.
[0019] In an exemplary aspect of the present disclosure, prior to the selecting, by the execution unit at the location server, the fall-back positioning method from the set of fall-back positioning methods, the method comprises determining, one of a supported status and the non-supported status, associated with the fall-back positioning method, wherein the supported status refers to the fall-back positioning method being supported by at least one of the UE and a base station, and the non¬supported status refers to the fall-back positioning method being not supported by the UE and the base station.
[0020] In an exemplary aspect of the present disclosure, the Cell ID identifies a base station associated with the UE.

[0021] Another aspect of the present disclosure may relate to a system for determining a positioning of a User Equipment (UE) in a network. The system comprises a location server. The location server comprises a loading unit, configured to load a plurality of positioning methods. The plurality of positioning methods comprises at least a primary positioning method and a set of fall-back positioning methods. The location server further comprises a transceiver unit connected to at least the loading unit. The transceiver unit is configured to receive a location request associated with a service from the UE. The location request relates to determining a location of the UE. The location server further comprises an execution unit connected to at least the transceiver unit. The execution unit is configured to select a first positioning method from the plurality of positioning methods based on the location request. The execution unit is further configured to select a fall-back positioning method from the set of fall-back positioning methods, in an event the first positioning method is associated with a non-supported status. Furthermore, the execution unit is configured to repeat for one or more remaining fall-back positioning methods from the set of fall-back positioning methods, selection of a next fall-back positioning method in an event the selected fall-back positioning method is associated with the non-supported status. The execution unit is further configured to select, a cell identifier (Cell-ID) in an event each of the selected fall-back positioning methods from the set of fall-back positioning methods is a non-supported positioning method.
[0022] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for determining a positioning of 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 loading unit of a location server to load a plurality of positioning methods, wherein the plurality of positioning methods comprises at least a primary positioning method and a set of fall-back positioning methods. The instructions when executed by the system further cause a transceiver unit of the location server connected at least to the loading unit to receive, a location request associated with a service from

the UE, wherein the location request relates to determining a location of the UE.
The instructions when executed by the system further cause an execution unit of the
location server connected to at least the transceiver unit to select a first positioning
method from the plurality of positioning methods based on the location request. The
5 instructions when executed by the system further cause the execution unit to select
a fall-back positioning method from the set of fall-back positioning methods, in an
event the first positioning method is associated with a non-supported status. The
instructions when executed by the system further cause the execution unit to repeat
for one or more remaining fall-back positioning methods from the set of fall-back
10 positioning methods, selection of a next fall-back positioning method in an event
the selected fall-back positioning method is associated with the non-supported
status. The instructions when executed by the system further cause the execution
unit to select, a cell identifier (Cell-ID) in an event each of the selected fall-back
positioning methods from the set of fall-back positioning methods is a non-
15 supported positioning method.
OBJECTS OF THE DISCLOSURE
[0023] Some of the objects of the present disclosure, which at least one
20 embodiment disclosed herein satisfies are listed herein below.
[0024] It is an object of the present disclosure to provide a system and a method for determining at least a positioning method of a User Equipment (UE) in a network.
25 [0025] It is yet another object of the present disclosure to determine location of the
UE by using Quality of Service (QoS) information to check the availability of positioning methods.
[0026] It is yet another object of the present disclosure to perform a fall-back
30 positioning method if the defined positioning method is not supported by the UE or
base station or the location server.
9

DESCRIPTION OF THE DRAWINGS
[0027] The accompanying drawings, which are incorporated herein, and constitute
a part of this disclosure, illustrate exemplary embodiments of the disclosed methods
5 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
10 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.
15 [0028] FIG. 1 illustrates an exemplary block diagram representation of 5th
generation core (5GC) network architecture.
[0029] 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
20 exemplary implementation of the present disclosure.
[0030] FIG. 3 illustrates an exemplary block diagram of a system for determining a positioning of a User Equipment (UE) in a network, in accordance with exemplary implementations of the present disclosure. 25
[0031] FIG. 4 illustrates a method flow diagram for determining a positioning of a User Equipment (UE) in a network, in accordance with exemplary implementations of the present disclosure.
10

[0032] FIG. 5 illustrates an exemplary method flow for determining a position of a UE in a network using a positioning method, in accordance with exemplary implementations of the present disclosure.
5 [0033] The foregoing shall be more apparent from the following more detailed
description of the disclosure.
DETAILED DESCRIPTION
10 [0034] 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.
[0035] 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.
[0036] 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
11

may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail.
[0037] 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.
[0038] 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.
[0039] 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,
12

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 [0040] 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.
[0041] 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.
[0042] 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
13

each other, which also includes the methods, functions, or procedures that may be called.
[0043] 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.
[0044] 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.
[0045] 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 determining a positioning of a User Equipment (UE) in a
network.
[0046] FIG. 1 illustrates an exemplary block diagram representation of 5th generation core (5GC) network architecture, in accordance with exemplary
25 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], an Authentication Server Function (AUSF) [112], a Network Slice Specific
30 Authentication and Authorization Function (NSSAAF) [114], a Network Slice
Selection Function (NSSF) [116], a Network Exposure Function (NEF) [118], a
14

Network Repository Function (NRF) [120], a Policy Control Function (PCF) [122],
a Unified Data Management (UDM) [124], an application function (AF) [126], a
User Plane Function (UPF) [128], a data network (DN) [130], a gateway mobile
location centre (GMLC) [140],a location client service (LCS) [142] and a Location
5 Management Function (LMF) [144], 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.
[0047] The Radio Access Network (RAN) [104] is the part of a mobile
10 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.
15 [0048] 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.
20 [0049] 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.
25 [0050] 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.
15

[0051] 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.
5 [0052] 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.
10 [0053] 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.
[0054] The Network Exposure Function (NEF) [118] is a network function that
15 exposes capabilities and services of the 5G network to external applications,
enabling integration with third-party services and applications.
[0055] The Network Repository Function (NRF) [120] is a network function that
acts as a central repository for information about available network functions and
20 services. It facilitates the discovery and dynamic registration of network functions.
[0056] 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. 25
[0057] The Unified Data Management (UDM) [124] is a network function that centralizes the management of subscriber data, including authentication, authorization, and subscription information.
16

[0058] 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.
5 [0059] The User Plane Function (UPF) [128] is a network function responsible for
handling user data traffic, including packet routing, forwarding, and QoS enforcement.
[0060] The Data Network (DN) [130] refers to a network that provides data
10 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.
[0061] The gateway mobile location centre (GMLC) [140] is a first network in the
15 5G network architecture [100] which is accessed by an external location
application. The GMLC [140] is responsible for performing registration, authorization and requests routing information.
[0062] The location client service (LCS) [142] is used to facilitate information
20 exchange related to a 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].
[0063] In the 5G positioning framework, the Location Management Function
25 (LMF) [144] is a central entity to estimate UE position based on
assistance/measurements from next-generation (NG)-RAN and UE through the access and mobility management function (AMF).
[0064] Further, the functional architecture of the network (such as but not limited
30 to 5G) core is flexibly designed to adopt implementation changes. The one or more
network nodes [303] in the network within the control plane enable cross-domain
17

interactions allowing other authorized network functions (third-party) to access
their services. The network is designed as an interconnected system of Network
Functions (NFs) [also known as fifth generation communication network (5GCN)
network function NF)] that communicate through the one or more interfaces [308]
5 (i.e., service-based interfaces or reference point interfaces). The Network Functions
(NF(s)) within the 5G control plane will use service-based interfaces for their
interactions. The user plane function (UPF) [128], and radio interactions shall use
the reference point interfaces. Each NF exposes specific functionality and provides
services to other NFs. Therefore, any communication or routing between NFs or
10 between the network nodes and NFs takes place through these interfaces. Interfaces
are self-contained software modules that are reusable independently of each other and can be thought of as micro services. Further, as shown in the FIG. 1, the following service-based interfaces are defined:
15 Namf: Service-based interface exhibited by AMF [106].
Nsmf: Service-based interface exhibited by SMF [108].
Nnef: Service-based interface exhibited by NEF [118].
Npcf: Service-based interface exhibited by PCF [122].
Nudm: Service-based interface exhibited by UDM [124].
20 Naf: Service-based interface exhibited by AF [126].
Nnrf: Service-based interface exhibited by NRF [120].
Nnssf: Service-based interface exhibited by NSSF [116].
Nausf: Service-based interface exhibited by AUSF [112].
Nnssaaf: Service-based interface exhibited by NSSAAF [114].
25 Nlmf: Service-based interface exhibited by LMF [144]
Nscp: Service-based interface exhibited by SCP [110].
[0065] Further, the 5G System Architecture as shown in FIG. 1, contains the
following reference points:
30 N1: Reference point between the UE [102] and the AMF [106].
N2: Reference point between the RAN [104] and the AMF [106].
18

N3: Reference point between the RAN [104] and the UPF [128]. N4: Reference point between the SMF [108] and the UPF [128]. N6: Reference point between the UPF [128] and a Data Network.
5 [0066] Further, FIG. 1 also shows some reference points to support Location
Servicer, such as:
Le: Reference point between a GMLC [140] and a LCS Client [142]. NLg: Reference point between a GMLC [140] and an AMF [106]. NLh: Reference point between an GMLC [140] and UDM [124]
10
[0067] 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
15 determining a positioning of a User Equipment (UE) in a network utilising the
system. In another implementation, the computing device [200] itself implements the method for determining a positioning of a User Equipment (UE) in a 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
20 present disclosure.
[0068] 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
25 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 main memory [206] also may be used for storing temporary variables or other
30 intermediate information during execution of the instructions to be executed by the
processor [204]. Such instructions, when stored in non-transitory storage media
19

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
5 information and instructions for the processor [204].
[0069] 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
10 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
15 [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]. 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
20 the device to specify positions in a plane.
[0070] 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
25 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 instructions may be read into the main memory [206] from another storage medium,
30 such as the storage device [210]. Execution of the sequences of instructions
contained in the main memory [206] causes the processor [204] to perform the
20

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 [0071] 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
10 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,
15 electromagnetic or optical signals that carry digital data streams representing
various types of information.
[0072] The computing device [200] can send messages and receive data, including program code, through the network(s), the network link [220] and the
20 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, and/or stored in the storage device [210], or other non-volatile storage for later
25 execution.
[0073] 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
30 perform the steps of a method [400] (as shown in FIG. 4).
21

[0074] Referring to FIG. 3, an exemplary block diagram of a system [300] for
determining a positioning of a User Equipment (UE) in a network is shown, in
accordance with the exemplary implementations of the present disclosure. The
system [300] comprises at least one location server [300]. The location server [300]
5 comprises at least one loading unit [302], at least one transceiver unit [304], at least
one execution unit [306] and at least one processing unit [308]. 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 FIG. 3 all units shown within
the system should also be assumed to be connected to each other. Also, in FIG. 3
10 only a few units are shown, however, the system [300] may comprise multiple such
units or the system [300] may comprise any such number of said units, as required to implement the features of the present disclosure. In an implementation, the system [300] may reside in a server or a network entity.
15 [0075] The system [300] is configured for determining a position of a User
Equipment (UE) in a network, with the help of the interconnection between the components/units of the system [300]. The positioning of the UE in the network may be determined using several positioning methods. The positioning methods, in general, are derived from timing, angular, power-based techniques, and their
20 combinations. Some of the standard positioning methods in 5G network supported
for NG-RAN access are: network-assisted GNSS methods
observed time difference of arrival (OTDOA) positioning based on LTE signals Downlink Time Difference of Arrival (DL-TDOA) based on NR signals
25
[0076] The OTDOA positioning method makes use of the measured timing of downlink signals received from multiple transmission points (TPs), comprising eNBs, ng-eNBs and PRS-only TPs, at the UE. The UE measures the timing of the received signals using assistance data received from the positioning server, and the
30 resulting measurements are used to locate the UE in relation to the neighbouring
TPs. Further, network-assisted GNSS methods make use of UEs that are equipped
22

with radio receivers capable of receiving GNSS signals. Examples of GNSS include
GPS, Modernized GPS, Galileo, GLONASS, Space Based Augmentation Systems
(SBAS), Quasi Zenith Satellite System (QZSS), and BeiDou Navigation Satellite
System (BDS). In this concept, different GNSSs (e.g. GPS, Galileo, etc.) can be
5 used separately or in combination to determine the location of a UE. Further, in the
Downlink Time Difference of Arrival (DL-TDoA) positioning method, the UE may measure the downlink reference signal time reference of the received signals from a base station. The UE position may be calculated by calculating the position of the UE from the position of the base station based on the time difference of arrival. 10
[0077] In an exemplary implementation, the location server [300] shown in FIG. 3
is a Location Management Function (LMF). The LMF manages the support of
different location services for UEs, including positioning of UEs and delivery of
assistance data to UEs. The LMF may interact with the serving gNB or serving ng-
15 eNB for a UE in order to obtain position measurements for the UE, including uplink
measurements made by an NG-RAN and downlink measurements made by the UE
that were provided to an NG-RAN as part of other functions such as for support of
handover. The LMF may interact with a UE in order to deliver assistance data if
requested for a particular location service, or to obtain a location estimate if that
20 was requested. The LMF may interact with multiple NG-RAN nodes to provide
assistance data information for broadcasting. The assistance data information for
broadcast may optionally be segmented and/or ciphered by the LMF. The LMF may
also interact with AMFs to provide ciphering key data information to the AMF. For
positioning of a target UE, the LMF decides on the position methods to be used,
25 based on factors that may include such as, the LCS Client type, the required QoS,
UE positioning capabilities, gNB positioning capabilities and ng-eNB positioning
capabilities. The LMF then invokes these positioning methods in the UE, serving
gNB and/or serving ng-eNB. The positioning methods may yield a location estimate
for UE-based position methods and/or positioning measurements for UE-assisted
30 and network-based position methods. The LMF may combine all the received
results and determine a single location estimate for the target UE (hybrid
23

positioning). Additional information like accuracy of the location estimate and velocity may also be determined. The LMF may interact with the AMF to provide (updated) UE positioning capability to AMF and to receive stored UE positioning capability from AMF. 5
[0078] The location server [300] comprises a loading unit [302], configured to load
a plurality of positioning methods. The plurality of positioning methods comprises
at least a primary positioning method and a set of fall-back positioning methods.
The plurality of positioning methods comprises but may not be limited to a network-
10 assisted Global navigation satellite system (GNSS) method, a Wireless Local Area
Network (WLAN) positioning, terrestrial beacon system (TBS) positioning, sensor
based positioning methods like barometric Pressure Sensor and motion sensor,
Downlink Angle-of-Departure (DL-AoD) based on New Radio (NR) signals,
Downlink Time Difference of Arrival (DL-TDOA) based on NR signals, and the
15 like. In the GNSS positioning method, different GNSSs (e.g. GPS, Galileo, etc.)
may be used separately or in combination to determine the location of the UE. The
WLAN positioning refers to the use of the WLAN measurements (AP identifiers
and the like) and databases to determine the location of the UE. The TBS consists
of a network of ground-based transmitters, broadcasting signals only for positioning
20 purposes. The UE may measure the received TBS signals to calculate its location
or to send measurements to the positioning server for position calculation. The
barometric pressure sensor-based positioning method refers to the UE measuring
barometric pressure to calculate the vertical component of its location or to send
measurements to the positioning server for position calculation. The DL-AoD
25 positioning method refers to the UE measuring the downlink positioning reference
signals- reference signal receiver power of the received signals, received from the
location server [300], and the measurements are used along with other configuration
information to locate the UE. The DL-TDOA refers to the UE measuring the
downlink reference signal time reference of the received signals, the resulting
30 measurements are used along with other configuration information to locate the UE.
24

[0079] Each of the plurality of positioning methods is based on at least one of a
service identifier (Service ID) associated with the service and a quality of service
(QoS) information associated with the location request. The QoS describes the
quality of service requested, such as the accuracy of the positioning measurement
5 and the response time of the positioning operation.
[0080] The location server [300] further comprises a transceiver unit [304] connected to at least the loading unit [302]. The transceiver unit [304] is configured to receive a location request associated with a service from the UE. The location
10 request relates to determining a location of the UE. Post receiving the location
request associated with the service from the UE, the processing unit [308] is configured to check an availability of at least one of the service ID and the QoS information in the received location request. Based on the availability of service ID in the location request, the processing unit [304] may select an appropriate
15 positioning method. The Service Identity indicates which Mobile Originated
Location Request (MO-LR) service of the LCS Client is requested by the UE. Further, the LCS Client is an entity that interacts with GMLC for the purpose of obtaining location information for the UE. Further, the LCS Client may reside in the UE. Whenever location server [300] receives a location request for determining
20 a location in the form of an INPUT data (which is a type of JSON (JavaScript Object
Notation) format), the location server [300] checks in JSON, for parameters named - LcsServiceType, if it is available then it will assign its value to the parameter Service ID. The LcsServiceType is a parameter that defines the LCS Service Type of the current positioning request. So, we can say that Service ID is derived from
25 LcsServiceType contained in the INPUT JSON. Further, for each Service ID in the
location server [300], there is defined a set of positioning methods. For example, for Service ID value of 64, a primary positioning method is defined as Uplink Enhanced Cell ID (UL_ECID) based positioning method and a fall-back positioning method is described as Cell-ID (Cell Identifier) based positioning
30 method. Similarly, for Service ID value of 65, the primary method defined is Cell-
ID based positioning method. The UL_ECID positioning refers to techniques which
25

use additional UE measurements and/or NG-RAN radio resource and other
measurements to improve the UE location estimate. In the Cell-ID positioning
method, the position of the UE is estimated with the knowledge of its serving ng-
eNB, gNB and cell. The information about the serving ng-eNB, gNB and cell may
5 be obtained by paging, registration, or other methods.
[0081] The location server [300] further comprises an execution unit [306] connected to at least the transceiver unit [304]. The execution unit [306] is configured to select a first positioning method from the plurality of positioning
10 methods based on the location request. The first positioning method is the primary
positioning method, in an event the location request comprises the Service ID. However, prior to selecting the first positioning method, the execution unit [306] is configured to determine one of a supported status and the non-supported status, associated with the first positioning method. The supported status refers to the first
15 positioning method being supported by at least one of the UE and a base station,
and the non-supported status refers to the first positioning method being not supported by at least one of the UE and the base station. The positioning methods may be supported in UE-based, UE-assisted/LMF-based, and NG-RAN node assisted versions. For example, GNSS based positioning method is supported by
20 UE based and LMF based versions, but not supported by NG-RAN node assisted
versions. Also, E-CID positioning method is supported by NG-RAN node assisted versions but is not supported by UE based versions. Enhanced Cell ID (E-CID) positioning refers to techniques which use additional UE measurements and/or NG-RAN radio resource and other measurements to improve the UE location estimate.
25
[0082] The execution unit [306] is further configured to select a fall-back positioning method from the set of fall-back positioning methods, in an event the first positioning method is associated with a non-supported status. A fall-back positioning method is selected when the primary method is not supported by both
30 UE and base station or there is any failure response from UE or base station when
primary method is selected. For instance, if the first positioning method is the
26

OTDOA positioning method, then since this is not supported by the UE as well as
the NG-RAN node, the OTDOA is a non-supported positioning method. The fall¬
back positioning method refers to an alternate positioning method. The fall-back
positioning method may be applicable in case the first positioning method is not
5 supported by the UE and the base station. In an instance, the set of fall-back
positioning may comprise but may not be limited to the network-assisted GNSS method, the TBS positioning, the sensor-based positioning methods, the WLAN positioning method, the DL-TDOA positioning method, and the like. Further, prior to selecting of the fall-back positioning method, the execution unit [306] is
10 configured to determine one of a supported status and the non-supported status,
associated with the fall-back positioning method. The supported status refers to the fall-back positioning method being supported by at least one of the UE and a base station, and the non-supported status refers to the fall-back positioning method being not supported by the UE and the base station.
15
[0083] The execution unit [306] is further configured to repeat for one or more remaining fall-back positioning methods from the set of fall-back positioning methods, selection of a next fall-back positioning method in an event the selected fall-back positioning method is associated with the non-supported status. To repeat
20 the one or more remaining fall-back positioning methods, the execution unit [306]
may monitor the UE and the base station for the non-supported status. In an implementation of the present disclosure, if the UE or the base station supports the selected fall-back positioning method, the execution unit [306] may not repeat the selection of the one or more remaining fall-back positioning methods. In another
25 implementation, if the UE and the base station does not support the selected fall-
back positioning methods, the execution unit [306] may further repeat the selection of a positioning method from the one or more remaining fall-back positioning methods.
30 [0084] Furthermore, the execution unit [306] is configured to select, a cell identifier
(Cell-ID) based positioning method, in an event each of the selected fall-back
27

positioning methods from the set of fall-back positioning methods is a non¬
supported positioning method. In the Cell-ID positioning method, the position of
the UE is estimated with the knowledge of its serving base station and cell. The
information about the serving base station and cell may be obtained by paging,
5 registration, or other methods. The Cell-ID may be stored as the last fall-back
positioning method to provide at least a lowest accuracy location of the UE. Cell-ID is a unique code or synchronization sequence assigned to each cell (base station) in a network to exclusively identify the cell. It helps mobile stations scan for and select the appropriate base stations to establish connections.
10
[0085] Referring to FIG. 4, an exemplary method flow diagram [400] for determining a positioning of a User Equipment (UE) in a network, in accordance with exemplary implementations of the present disclosure is shown. The positioning of the UE in the network may be determined using several positioning
15 methods. The positioning methods, in general, are derived from timing, angular,
power-based techniques, and their combinations. Some of the standard positioning methods in 5G network supported for NG-RAN access are: network-assisted GNSS methods observed time difference of arrival (OTDOA) positioning based on LTE signals
20 Downlink Time Difference of Arrival (DL-TDOA) based on NR signals
[0086] As an example, in the Downlink Time Difference of Arrival (TDoA)
positioning method, the UE may measure the downlink reference signal time
reference of the received signals from a base station. The UE position may be
25 calculated by calculating the position of the UE from the position of the base station
based on the time difference of arrival.
[0087] In an implementation the method [400] is performed by the system [300].
Further, in an implementation, the system [300] may be present in a server device
30 to implement the features of the present disclosure. Also, as shown in FIG. 4, the
method [400] starts at step [402].
28

[0088] At step [404], the method comprises loading, by a loading unit [302] at a
location server [300], a plurality of positioning methods. The location server [300]
is a Location Management Function (LMF) [144] as shown in FIG. 1. The LMF
5 [144] manages the support of different location services for target UEs, including
positioning of UEs and delivery of assistance data to UEs. The LMF [144] may
interact with the serving gNB or serving ng-eNB for a target UE in order to obtain
position measurements for the UE, including uplink measurements made by an NG-
RAN and downlink measurements made by the UE that were provided to an NG-
10 RAN as part of other functions such as for support of handover. The LMF [144]
may interact with a UE in order to deliver assistance data if requested for a
particular location service, or to obtain a location estimate if that was requested.
The LMF [144] may interact with multiple NG-RAN nodes to provide assistance
data information for broadcasting. The assistance data information for broadcast
15 may optionally be segmented and/or ciphered by the LMF [144]. The LMF [144]
may also interact with AMF [106] to provide ciphering key data information to the
AMF [106]. For positioning of a UE, the LMF [144] decides on the position
methods to be used, based on factors that may include the LCS Client type, the
required QoS, UE positioning capabilities, gNB positioning capabilities and ng-
20 eNB positioning capabilities. The LMF [144] then invokes these positioning
methods in the UE, serving gNB and/or serving ng-eNB. The positioning methods
may yield a location estimate for UE-based position methods and/or positioning
measurements for UE-assisted and network-based position methods. The LMF
[144] may combine all the received results and determine a single location estimate
25 for the target UE (hybrid positioning). Additional information like accuracy of the
location estimate and velocity may also be determined. The LMF [144] may interact
with the AMF [106] to provide (updated) UE positioning capability to AMF [106]
and to receive stored UE positioning capability from AMF [106]. The plurality of
positioning methods comprises at least a primary positioning method and a set of
30 fall-back positioning methods. The plurality of positioning methods includes but
may not be limited to a network-assisted Global navigation satellite system (GNSS)
29

method, a Wireless Local Area Network (WLAN) positioning, terrestrial beacon
system (TBS) positioning, sensor based positioning methods like barometric
Pressure Sensor and motion sensor, Downlink Angle-of-Departure (DL-AoD)
based on New Radio (NR) signals, Downlink Time Difference of Arrival (DL-
5 TDOA) based on NR signals, and the like.
[0089] Next, at step [406], the method comprises receiving, by a transceiver unit [304] at the location server [300], a location request associated with a service from the UE. The location request relates to determining a location of the UE. Post the
10 receiving of the location request associated with the service from the UE, the
method comprises checking, by a processing unit [308] at the location server [300], an availability of at least one of the service ID and a Quality of Service (QoS) information in the received location request. Each of the plurality of positioning methods is based on one of the service identifier (Service ID) associated with the
15 service and a quality of service (QoS) information associated with the location
request. The QoS associated with the location request may include the quality of service requested, such as the accuracy of the positioning measurement and the response time of the positioning operation. Based on the availability of the Service ID, the processing unit [304] may select an appropriate positioning method.
20
[0090] Whenever location server [300] receives a location request for determining a location in the form of an INPUT data (which is a type of JSON format). The location server [300] checks in JSON, for parameters named - LcsServiceType, if it is available then it will assign its value to a parameter Service ID. So, we can say
25 that Service ID is derived from LcsServiceType contained in the INPUT JSON,
Further, for each Service ID in the location server [300], there is defined a set of positioning method. For example, for Service ID value of 64, a primary positioning method is defined as Uplink Enhanced Cell-ID (UL_ECID) and for Service ID value of 65, the primary method defined is Cell Identifier (Cell-ID).
30
30

[0091] Further, at step [408], the method comprises selecting, by an execution unit
[306] at the location server [300], a first positioning method from the plurality of
positioning methods based on the location request. The first positioning method is
the primary positioning method, in an event the location request comprises the
5 Service ID. However, prior to selecting, by the execution unit [306], the first
positioning method from the plurality of positioning methods, the method comprises determining, by the execution unit [306], one of a supported status and the non-supported status, associated with the first positioning method. The supported status refers to the first positioning method being supported by at least
10 one of the UE and a base station. The non-supported status refers to the first
positioning method being not supported by the UE and the base station. The positioning methods may be supported in UE-based, UE-assisted/LMF-based, and NG-RAN node assisted versions. For example, GNSS based positioning method is supported by UE based and LMF based versions, but not supported by NG-RAN
15 node assisted versions. Also, E-CID positioning method is supported by NG-RAN
node assisted versions but is not supported by UE based versions.
[0092] Further, at step [410], the method comprises selecting, by the execution unit [306] at the location server [300], a fall-back positioning method from the set of
20 fall-back positioning methods, in an event the first positioning method is associated
with a non-supported status. A fall-back positioning method is selected when the primary method is not supported by both UE and base station or there is any failure response from UE or base station when primary method is selected. For instance, if the first positioning method is the OTDOA positioning method, then since this is
25 not supported by the UE as well as the NG-RAN node, the OTDOA is a non-
supported positioning method. The fall-back positioning method refers to an alternate positioning method. The fall-back positioning method may be applicable in case the first positioning method is not supported by the UE and the base station. In an instance, the set of fall-back positioning comprises but may not be limited to
30 the network-assisted GNSS method, the TBS positioning, the sensor-based
positioning methods, the WLAN positioning method, the DL-TDOA positioning
31

method, and the like. In the GNSS positioning method, different GNSSs (e.g. GPS,
Galileo, etc.) may be used separately or in combination to determine the location of
the UE. The WLAN positioning refers to the use of the WLAN measurements (AP
identifiers and the like) and databases to determine the location of the UE. The TBS
5 consists of a network of ground-based transmitters, broadcasting signals only for
positioning purposes. The UE may measure the received TBS signals to calculate its location or to send measurements to the positioning server for position calculation. The barometric pressure sensor-based positioning method refers to the UE measuring barometric pressure to calculate the vertical component of its
10 location or to send measurements to the positioning server for position calculation.
The DL-AoD positioning method refers to the UE measuring the downlink positioning reference signals- reference signal receiver power of the received signals, received from the location server [300], and the measurements are used along with other configuration information to locate the UE. The DL-TDOA refers
15 to the UE measuring the downlink reference signal time reference of the received
signals, the resulting measurements are used along with other configuration information to locate the UE.
[0093] Further, prior to selecting of the fall-back positioning method, the execution
20 unit [306] is configured to determine one of a supported status and the non-
supported status, associated with the fall-back positioning method. The supported status refers to the fall-back positioning method being supported by at least one of the UE and a base station, and the non-supported status refers to the fall-back positioning method being not supported by the UE and the base station. 25
[0094] Next, at step [412], the method encompasses repeating, by the execution
unit [306], for one or more remaining fall-back positioning methods from the set of
fall-back positioning methods, selection of a next fall-back positioning method in
an event the selected fall-back positioning method is associated with a non-
30 supported status.
32

[0095] To repeat the one or more remaining fall-back positioning methods, the
execution unit [306] may monitor the UE and the base station for the non-supported
status. In an implementation of the present disclosure, if the UE or the base station
supports the selected fall-back positioning method, the execution unit [306] may
5 not repeat the selection of the one or more remaining fall-back positioning methods.
In another implementation, if the UE and the base station do not support the selected fall-back positioning methods, the execution unit [306] may further repeat the selection of a positioning method from the one or more remaining fall-back positioning methods.
10
[0096] Further, at step [414], the method comprises selecting, by the execution unit [306] at the location server [300], a cell identifier (Cell-ID) based positioning method in an event each of the selected fall-back positioning methods from the set of fall-back positioning methods is associated with a non-supported status. The
15 Cell-ID refers to a unique identity associated with the base station and a cell within
the base station in a geographical area. The Cell-ID may be stored as the last fall-back positioning method to provide at least a lowest accuracy location of the UE. The position of the UE may be estimated with the knowledge of its serving base station and the Cell-ID. The information about the serving base station and the cell
20 may be obtained by paging, registration, or other methods.
[0097] Thereafter, the method terminates at step [416].
[0098] Referring to FIG. 5, an exemplary method flow [500] for determining a
25 position of a User Equipment (UE) in a network using a positioning method, is
shown.
[0099] The location server [300] may be a Location Management Function (LMF)
[144] as shown in FIG. 1. In the 5th Generation core network, the LMF [144]
30 manages the support of different location services for UEs, including positioning of
UEs and delivery of assistance data to UEs. The LMF [144] may interact with the
33

serving gNB or serving ng-eNB for a UE in order to obtain position measurements
for the UE, including uplink measurements made by an NG-RAN and downlink
measurements made by the UE that were provided to an NG-RAN as part of other
functions such as for support of handover. In an implementation of the present
5 disclosure, the location server [300] may store the plurality of positioning methods
for every service identifier (Service ID).
[0100] At step 1, the AMF [106] may forward a location request initiated by a UE, to the location server [300]. The location request is associated with a service at the
10 UE. 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. The location request relates to determining a location of the UE. Further, the location server [300] checks for an availability of
15 at least one of a Service ID and a QoS information in the received location request.
The QoS may describe quality of service requested, such as the accuracy of the positioning measurement and the response time of the positioning operation. Whenever location server [300] receives a location request for determining a location in the form of an INPUT data (which is a type of JSON), the location server
20 [300] checks in JSON, for parameters named - LcsServiceType, if it is available
then it will assign its value to a parameter Service ID. So, we can say that Service ID is derived from LcsServiceType contained in the INPUT JSON, Further, for each Service ID in the location server [300], there is defined a set of positioning method. For example, for Service ID value of 64, a primary positioning method is
25 defined as Uplink Enhanced Cell ID (UL_ECID) and for Service ID value of 65,
the primary method defined is Cell Identifier (Cell-ID).
[0101] At step 2, based on the Service ID in the location request, the first
positioning method may be selected by the location server [300]. The first
30 positioning method is the primary positioning method. However, prior to selecting
the first positioning method, the location server [300] may determine one of a
34

supported status and the non-supported status associated with the first positioning
method. The supported status refers to the first positioning method being supported
by at least one of the UE and a base station, and the non-supported status refers to
the first positioning method being not supported by the UE and the base station.
5 The positioning methods may be supported in UE-based, UE-assisted/LMF-based,
and NG-RAN node assisted versions. For example, GNSS based positioning method is supported by UE based and LMF based versions, but not supported by NG-RAN node assisted versions. Also, E-CID positioning method is supported by NG-RAN node assisted versions but is not supported by UE based versions.
10
[0102] At step 3, if the first positioning method is associated with a non-supported status, the AMF [106] may send an error response to the location server [300]. The error response may indicate an issue in retrieving the location of the UE. In another embodiment, if the first positioning method has a supported status, the AMF [106]
15 may perform positioning measurements and/or location computation requested of
the UE as per the location request.
[0103] At step 4, in the event the error response is received, the location server
[300] selects a first fall-back positioning method from the set of fall-back
20 positioning methods. The error response may include a failure cause. The first fall-
back positioning method refers to a first alternate positioning method. The first fall¬
back positioning method may be applicable in case the first positioning method is
not supported by the UE and the base station or there is any failure response from
UE or base station when primary method is selected. In an instance, the set of fall-
25 back positioning methods may comprise but may not be limited to the network-
assisted GNSS method, the TBS positioning, the sensor-based positioning methods,
the WLAN positioning method, the DL-TDOA positioning method, and the like.
Further, prior to selecting the first fall-back positioning method, the location server
[300] may determine one of a supported status and a non-supported status,
30 associated with the first fall-back positioning method. The supported status refers
to the first fall-back positioning method being supported by at least one of the UE
35

and a base station, and the non-supported status refers to the first fall-back
positioning method being not supported by the UE and the base station. In an
exemplary implementation, for Service ID value of 64, a first positioning method
is defined as Uplink Enhanced Cell ID (UL_ECID) and the first fall-back
5 positioning method is described as network-assisted GNSS method.
[0104] At step 5, if neither the UE nor the base station support the first fall-back positioning method, the AMF [106] may send an error response to the location server [300].
10
[0105] At step 6, the location server [300] may further select a second fall-back positioning method to retrieve the location of the UE. Further, for the second fall-back positioning method, the location server [300] may check one of the supported status and the non-supported status, associated with the second fall-back positioning
15 method. Continuing with the above cited exemplary implementation, for Service
ID value of 64, the first positioning method is defined as Uplink Enhanced Cell ID (UL_ECID) and the first fall-back positioning method is described as network-assisted GNSS method and the second fall-back positioning method is described as Cell-ID based positioning method.
20
[0106] At step 7, if the location server [300] again receives an error response for the second fall-back positioning method, the location server [300] may select next fall-back positioning method from the remaining fall-back positioning methods. This is repeated for every error response received from the AMF [106], until there
25 is no remaining fall-back positioning method. Thereafter, the location server [300]
provides the location or positioning of the UE using the Cell-ID based positioning method. The Cell-ID may be stored as the last fall-back positioning method to provide at least a lowest accuracy location of the UE.
30 [0107] The present disclosure further discloses a non-transitory computer readable
storage medium storing instruction for determining a positioning of a User
36

Equipment (UE) in a network, the instructions include executable code which, when executed by one or more units of a system, cause a loading unit [302] of a location server [300] to load a plurality of positioning methods. The plurality of positioning methods comprises at least a primary positioning method and a set of fall-back positioning methods. The instructions when executed by the system further cause a transceiver unit [304] of the location server [300] connected at least to the loading unit [302] to receive, a location request associated with a service from the UE, wherein the location request relates to determining a location of the UE. The instructions when executed by the system further cause an execution unit [306] of the location server [300] connected to at least the transceiver unit [304] to select a first positioning method from the plurality of positioning methods based on the location request. The instructions when executed by the system further cause the execution unit [306] to select a fall-back positioning method from the set of fall¬back positioning methods, in an event the first positioning method is associated with a non-supported status. The instructions when executed by the system further cause the execution unit [306] to repeat for one or more remaining fall-back positioning methods from the set of fall-back positioning methods, selection of a next fall-back positioning method in an event the selected fall-back positioning method is associated with the non-supported status. The instructions when executed by the system further cause the execution unit [306] to select, a cell identifier (Cell-ID) based positioning method, in an event each of the selected fall-back positioning methods from the set of fall-back positioning methods is a non-supported positioning method.
[0108] As is evident from the above, the present disclosure provides a technically advanced solution for determining a positioning of a User Equipment (UE) in a network. The present disclosure determines if the primary positioning method as configured in the system is not supported by the UE and the base station, then instead of sending an error or a failure response, the present disclosure uses a fall-back mechanism to select a fall-back positioning method from a set of fall-back positioning methods. If the selected fall-back positioning method is not supported

by both the UE and the base station, then the fall-back mechanism selects the next fall-back positioning method iteratively, until all the fall-back positioning methods are exhausted. The present disclosure further provides the location of the UE even when each of the fall-back positioning method fails, by performing a fall-back on the Cell-ID based positioning method for the lowest accuracy positioning. This way, the present disclosure provides a solution to determine positioning of the UE even when no defined positioning method is supported.
[0109] 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.

We Claim:
1. A method [400] for determining a positioning method for a user equipment (UE) in a network, the method comprising:
- loading, by a loading unit [302] at a location server [300], a plurality of positioning methods, wherein the plurality of positioning methods comprises at least a primary positioning method and a set of fall-back positioning methods;
- receiving, by a transceiver unit [304] at the location server [300], a location request associated with a service from the UE, wherein the location request relates to determining a location of the UE;
- selecting, by an execution unit [306] at the location server [300], a first positioning method from the plurality of positioning methods based on the location request;
- selecting, by the execution unit [306] at the location server [300], a fall-back positioning method from the set of fall-back positioning methods, in an event the first positioning method is associated with a non-supported status;
- repeating, by the execution unit [306], for one or more remaining fall-back positioning methods from the set of fall-back positioning methods, selection of a next fall-back positioning method in an event the selected fall-back positioning method is associated with a non-supported status;
- selecting, by the execution unit [306] at the location server [300], a cell identifier (Cell-ID) based positioning method in an event each of the selected fall-back positioning methods from the set of fall-back positioning methods is associated with a non-supported status.
2. The method [400] as claimed in claim 1, wherein each of the plurality of positioning methods is based on one of a Service identifier (Service ID)

associated with the service and a quality of service (QoS) information associated with the location request.
3. The method [400] as claimed in claim 2, wherein post the receiving of the
location request associated with the service from the UE, the method
comprises:
- checking, by a processing unit [308] at the location server [300], an
availability of at least one of the Service ID and the QoS information in
the received location request.
4. The method [400] as claimed in claim 2, wherein the first positioning method is the primary positioning method, in an event the location request comprises the Service ID.
5. The method [400] as claimed in claim 1, wherein the location server [300] is a location management function (LMF).
6. The method [400] as claimed in claim 1, wherein prior to the selecting, by the execution unit [306], the first positioning method from the plurality of positioning methods, the method comprises:
- determining, by the execution unit [306], one of a supported status and
the non-supported status, associated with the first positioning method,
wherein the supported status refers to the first positioning method being
supported by at least one of the UE and a base station, and the non¬
supported status refers to the first positioning method being not
supported by the UE and the base station.
7. The method [400] as claimed in claim 1, wherein prior to the selecting, by
the execution unit [306] at the location server [300], the fall-back
positioning method from the set of fall-back positioning methods, the
method comprises:

- determining, one of a supported status and the non-supported status,
associated with the fall-back positioning method, wherein the supported
status refers to the fall-back positioning method being supported by at
least one of the UE and a base station, and the non-supported status
refers to the fall-back positioning method being not supported by the UE
and the base station.
8. The method [400] as claimed in claim 6, wherein the Cell-ID identifies a base station associated with the UE.
9. A system [300] for determining a positioning method for a user equipment (UE) in a network, the system comprising:
- a location server [300], wherein the location server [300] comprises:
- a loading unit [302], configured to load a plurality of positioning methods, wherein the plurality of positioning methods comprises at least a primary positioning method and a set of fall-back positioning methods;
- a transceiver unit [304] connected to at least the loading unit [302], the transceiver unit [304] configured to receive, a location request associated with a service from the UE, wherein the location request relates to determining a location of the UE;
- an execution unit [306] connected to at least the transceiver unit [304],
the execution unit [306] configured to:
- select a first positioning method from the plurality of positioning methods based on the location request;
- select a fall-back positioning method from the set of fall-back positioning methods, in an event the first positioning method is associated with a non-supported status;
- repeat for one or more remaining fall-back positioning methods from the set of fall-back positioning methods, selection of a next

fall-back positioning method in an event the selected fall-back positioning method is associated with the non-supported status; - select, a cell identifier (Cell-ID) in an event each of the selected fall-back positioning methods from the set of fall-back positioning methods is a non-supported positioning method.
10. The system [300] as claimed in claim 9, wherein each of the plurality of positioning methods is based on at least one of a service identifier (Service ID) associated with the service and a quality of service (QoS) information associated with the location request.
11. The system [300] as claimed in claim 10, wherein post receiving the location request associated with the service from the UE, the system comprises a processing unit [308] configured to:
- check an availability of at least one of the Service ID and the QoS information in the received location request.
12. The system [300] as claimed in claim 10, wherein the first positioning method is the primary positioning method, in an event the location request comprises the Service ID.
13. The system [300] as claimed in claim 9, wherein the location server [300] is a location management function (LMF).
14. The system [300] as claimed in claim 9, wherein prior to the selecting, the first positioning method, the execution unit [306] is configured to: determine one of a supported status and the non-supported status, associated with the first positioning method, wherein the supported status refers to the first positioning method being supported by at least one of the UE and a base station, and the non-supported status refers to the first positioning method being not supported by the UE and the base station.

15. The system [300] as claimed in claim 9, wherein prior to the selecting, the
fall-back positioning method, the execution unit [306] is configured to:
determine one of a supported status and the non-supported status, associated with the fall-back positioning method, wherein the supported status refers to the fall-back positioning method being supported by at least one of the UE and a base station, and the non¬supported status refers to the fall-back positioning method being not supported by the UE and the base station.
16. The system [300] as claimed in claim 9, wherein the Cell-ID identifies a
base station associated with the UE.