System and method for determining user equipment location in network

Abstract

A method for determining the location of a user equipment (UE) in a network is disclosed. A location management function (LMF) receives a location determination request containing New Radio Cell Global Identity (NR-CGI) information from an access and mobility management function (AMF). Using the NR-CGI information, the LMF identifies random access network (RAN) vendor associated with the UE and requests the vendor to provide multiple measurement parameters. Based on these parameters and at least one pre-configured algorithm from the RAN vendor, the LMF selects at least one algorithm from a set of available algorithms. Using the selected algorithm(s), the LMF calculates and determines the location of the UE.

Description

SYSTEM AND METHOD FOR DETERMINING USER EQUIPMENT LOCATION IN NETWORKRESERVATION OF RIGHTS

[0001] A portion of the disclosure of this patent document contains material, which is subject to intellectual property rights such as, but are not limited to, copyright, design, trademark, Integrated Circuit (IC) layout design, and / or trade dress protection, belonging to Jio Platforms Limited (JPL) or its affiliates (hereinafter referred as owner). The owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all rights whatsoever. All rights to such intellectual property are fully reserved by the owner.TECHNICAL FIELD

[0002] The present disclosure relates generally to the field of communication systems. More particularly, the present disclosure relates to systems and methods for determining location of a user equipment (UE) in a network.DEFINITION

[0003] As used in the present disclosure, the following terms are generally intended to have the meaning as set forth below, except to the extent that the context in which they are used to indicate otherwise.

[0004] The term “Location-Based Services (LBS)” refers to services that use real-time geographical data from the user equipment (UE) or GPS (Global Positioning System) to provide information, entertainment, or utilities to users based on their location.

[0005] The term “Location management Function (LMF)” refers to a function in mobile communication networks (e.g., 4G, 5G), that is responsible for gathering and processing location-related measurements to determine the geographical position of theUE (such as smartphones, loT devices, or vehicles). The LMF plays a critical role in positioning systems that provide services like navigation, asset tracking, emergency location services, and other location-based services (LBS).

[0006] The term “Random Access Network (RAN)” refers to part of network that connects the UE to the network, enabling wireless communication. The RAN is responsible for the radio communication between the UE and the base stations (also known as Node Bs in 4G LTE and gNBs in 5G), and facilitates the transmission of voice, data, and control signals to and from the network's core elements.

[0007] The term “RAN vendors” refers to companies that supply equipment and solutions for the Radio Access Network (RAN), the critical infrastructure that connects the UE (e.g., smartphones, loT devices) to the network in mobile communication systems (e.g., 4G (LTE) and 5G).

[0008] The term “Uplink” refers to a communication path from the UE (e.g., mobile phone, loT device) to the base station (e.g., eNodeB in LTE or gNodeB in 5G).

[0009] The term “Uplink Enhanced Cell Identifier (UL-ECID)” refers to a positioning method used in the networks to determine the location of the UE based on uplink transmission in combination with the Cell ID of the serving cell.

[0010] The term “Reference Signal Received Power (RSRP) refers to a key metric used in the networks to measure the strength of the received signal at the UE from the cell tower (e.g., eNodeB in LTE or gNodeB in 5G NR). RSRP is a critical parameter for evaluating the signal quality and determining the coverage and performance of the radio access network.

[0011] The term “Reference Signal Received Quality (RSRQ)” refers to a key metric used in the networks to assess the quality of the received signal, specifically how the Reference Signal (RS) is affected by noise and interference.

[0012] The term “Timing Advance (TA)” refers to a parameter used in cellular networks, to synchronize the transmission timing of the UE (e.g., a mobile phone or loT device) with the base station (eNodeB or gNodeB). The Timing Advance (TA) compensates for the propagation delay that occurs as the signal travels from the UE to the base station.

[0013] The term “Angle of Arrival (AoA) refers to a technique used in wireless communication systems to determine the direction from which a signal is received at the receiver (usually a base station or access point) relative to a reference direction, typically expressed in degrees. The AoA is used in wireless networks for positioning, beamforming, and location-based services. The AOA helps to improve the performance of the network by identifying the direction of incoming signals and allowing the network to adjust accordingly.

[0014] The term “Mobile Terminated Location Request (MTLR)” refers to a location request initiated by the network to determine the location of the UE. It is called 'mobile terminated' because the location request is processed by the mobile device (UE), meaning that the network requests the UE's location, and the UE must respond to the request with its current location information. In MTLR, the network initiates the request, and the mobile device (UE) provides the location information in response.

[0015] The term “Network Initiated Location Request (NILR)” refers to a location request initiated by the network itself, where the network requests the location of the UE, and the UE responds with its current location. NILR allows the network to directly request location information from the UE without requiring the UE to initiate the request. In NILR, the network sends the request to the UE, and the location information is typically obtained either through location services on the device.

[0016] The term “New Radio Positioning Protocol A (NRPPa) refers to a protocol that enables location- based services (LBS) and location tracking for the UE)within the network. The NRPPa protocol defines the procedures and signaling mechanisms that enable the network and UE to exchange information for accurately determining the location of the UE.

[0017] The term “NR Cell Global Identity (NR-CGI) refers to an identifier to uniquely identify a cell within the network. The NR-CGI is used for cell-level identification in NR networks and plays a critical role in managing mobility, handover, and location-based services (LBS).

[0018] The term “Time Division Duplex (TDD) refers to a communication technique used in wireless networks to manage the uplink and downlink transmission by sharing the same frequency band but allocating different time slots for sending and receiving signals. It is one of the duplexing methods used to enable communication between the UE and the base station.

[0019] The term “Frequency Division Duplex (FDD)” refers to a duplexing technique used in wireless communication systems, allows for simultaneous transmission and reception of data by utilizing two separate frequency bands — one for uplink (transmission from the UE to the base station) and one for downlink (transmission from the base station to the UE). The FDD provides two distinct channels: one for uplink and one for downlink. These channels operate simultaneously but at different frequencies, with a guard band separating them to avoid interference.

[0020] The term “Absolute Radio Frequency Channel Number (ARFCN)” refers to a standard identifier used to specify a particular frequency channel in mobile cellular networks. The ARFCN is a numerical representation of the frequency on which the mobile network operates for either the uplink (mobile to base station) or downlink (base station to mobile). The ARFCN is part of the system's frequency planning and enables the radio network to allocate and track specific frequencies for communication between mobile devices (User Equipment, or UE) and the base stations.

[0021] The term “Access and Mobility Management Function (AMF) refers to a network function responsible for handling access control, mobility management, session management, and several other key tasks related to user equipment (UE) connectivity and mobility in networks.

[0022] The term “Location Services Client (LCS) refers to a component or application within the network or device that requests location-based services (LBS) from the network. The LCS is responsible for initiating location requests and receiving location information from the network, based on the capabilities of the underlying network infrastructure and positioning methods. The LCS client may be a user device, an application, or a service that consumes location data for a variety of purposes, such as navigation, tracking, or geo-fencing.BACKGROUND

[0023] The following description of 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 be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.

[0024] A Location Measurement Function (LMF) is a key component in wireless communication networks for positioning and location-based services. A plurality of Random Access Network (RAN) vendors are deployed at different locations. An Uplink Enhanced Cell ID (UL-ECID) method is used to calculate the location of users or user equipments (UEs) based on measurements, such as signal strength, time of arrival, and other radio metrics reported by the RAN vendors in one of Mobile Terminated Link Report (MTLR) and Network Initiated Link Report (NFLR). The UL-ECID method estimates a UE's position using the Cell ID from aUniversal Mobile Telecommunications Service (UMTS) Terrestrial Radio Access Network (UTRAN) along with RAN measurements. The LMF processes these RAN measurements to calculate the UE’s location.

[0025] The UU-ECID method determines the UE's location based on information from multiple cells or radio access points. However, the UL-ECID method relies on signal measurements from nearby cells, and signals can be reflected, obstructed, or diffused. These factors significantly reduce the accuracy of the position calculation, as the signal may not accurately reflect the correct location of the device, leading to larger location errors. Further, the location calculation is based on RAN measurements like signal strength or time of arrival, which environmental factors, interference, or network congestion can impact. These errors can degrade positioning accuracy. For example, multipath effects, interference, and fading can cause inaccuracies in the reported signal strength, leading to incorrect position calculations. Additionally, out-of-range measurements can further compromise accuracy. The LMF may mistakenly interpret the location based on erroneous signal reflections, resulting in inaccurate or inconsistent positioning data. The LMF also depends heavily on the measurements provided by the RAN, which can introduce delays due to transmission and processing times for the measurement signals.

[0026] There is a need for a system and a method to address the challenges of inaccuracies in the location determination of the UEs in the network.OBJECTIVES

[0027] Some of the objectives of the present disclosure, which at least one embodiment herein satisfies, are as follows:

[0028] An objective of the present disclosure is to provide a system and a method for determining location of a plurality of user equipments (UEs) in a network.

[0029] Another objective of the present disclosure is to calculate the location of the UEs based on different measurement combinations of Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Timing Advance (TA) and Angle of Arrival (AoA) received from different RAN vendors in New Radio (NR) Positioning Protocol for Access (NRPPa) request.

[0030] Yet another objective of the present disclosure is to provide the location, upon determining whether one of the measurement values (e.g., RSRP) is out-of-range or invalid based on valid measurement values (e.g., RSRQ, TA, AoA) and ignore the out-of-range or invalid measurement value.

[0031] Yet another objective of the present disclosure is to provide an accurate location of a target subscriber (i.e., the UE) by selecting different algorithms based on the parameters received in the measurements from the RAN end and pre-configuration at the LMF end.

[0032] Yet another objective of the present disclosure is to determine cell type based on NR Absolute Radio Frequency Channel Number (ARFCN) value received in location response.

[0033] Other objectives and advantages of the present disclosure will be more apparent from the following description, which is not intended to limit the scope of the present disclosure.SUMMARY

[0034] In an exemplary embodiment, a method for determining user equipment (UE) location in a network is described. The method comprises receiving, by a first network function, a location determination request for at least one UE from a second network function. The method comprises extracting, by the first network function, at least one parameter from the received location determination request. The methodcomprises determining, by the first network function, a network node of the at least one UE based on the at least one extracted parameter. The method comprises requesting, by the first network function, the determined network node to provide one or more measurement parameters. The method comprises receiving, by the first network function, a response comprising the one or more measurement parameters from the determined network node. The method comprises selecting, by the first network function, at least one algorithm from a plurality of algorithms based on at least one of at least one condition and the one or more received measurement parameters. The method comprises determining, by the first network function, the location of the at least one UE based on the at least one selected algorithm.

[0035] In some embodiments, the first network function is a location management function (LMF). The second network function is an access and mobility management function (AMF). The network node is a radio access network (RAN) node.

[0036] In some embodiments, the at least one extracted parameter comprises, but not limited to, a New Radio Cell Global Identity (NR-CGI), a tracking area identifier (ID), an International Mobile Subscriber Identity (IMSI), a temporary identifier, and a subscription identifier. The one or more received measurement parameters comprise a reference signal received power (RSRP), a reference signal received quality (RSRQ), a timing advance (TA) and an angle of arrival (AoA).

[0037] In some embodiments, the at least one condition comprises one or more of: a priority condition of each of the one or more received measurement parameters, a range condition of each of the one or more received measurement parameters, and a pre-configured algorithm condition of the determined network node.

[0038] In some embodiments, the pre-configured algorithm condition comprises preconfiguring an algorithm from the plurality of algorithms for eachnetwork node based on the one or more received measurement parameters corresponding to each network node.

[0039] In some embodiments, the range condition comprises detecting whether at least one measurement parameter of the one or more received measurement parameters is out of range or invalid based on a predefined range. The range condition comprises, upon detecting that the at least one measurement parameter of the one or more received measurement parameters is out of range or invalid based on the predefined range, determining, by the first network function, the location of the at least one UE based on one or more remaining valid measurement parameters.

[0040] In some embodiments, the priority condition comprises selecting the at least one algorithm based on a priority of each of the one or more received measurement parameters and a preconfigured algorithm of the determined network node.

[0041] In some embodiments, the first network function is configured to perform an integrity check on the determined location of the at least one UE. The integrity check is performed based on at least one of, but not limited to, a multi-round trip time (multi-RTT), a downlink angle of departure (DL-AoD), a DL-time difference of arrival (DL-TDoA), an uplink- TDoA (UL-TDoA), and an UL-AoA.

[0042] In another exemplary embodiment, a system for determining user equipment (UE) location in a network is disclosed. The system comprises a first network function. The first network function comprises a processing engine and a memory coupled to the processing engine. The processing engine comprises a receiving unit configured to receive a location determination request for at least one UE from a second network function. An extraction unit configured to extract at least one parameter from the received location determination request. A determining unit configured to determine a network node of the at least one UE based on the at least oneextracted parameters. A requesting unit configured to request the determined network node to provide one or more measurement parameters. The receiving unit configured to receive a response comprising the one or more measurement parameters from the determined network node. A selecting unit configured to select at least one algorithm from a plurality of algorithms based on at least one of at least one condition and the one or more received measurement parameters. The determining unit configured to determine the location of the at least one UE based on the at least one selected algorithm.

[0043] In yet another exemplary embodiment, a user equipment (UE) communicatively coupled with a system. The coupling comprises steps of receiving, by the system, a connection request from the UE, sending, by the system, an acknowledgment of the connection request to the UE and transmitting a plurality of signals in response to the connection request. The system is configured to determine user equipment (UE) location in a network. The system comprises a first network function. The first network function comprises a processing engine and a memory coupled to the processing engine. The processing engine comprises a receiving unit configured to receive a location determination request for at least one UE from a second network function. An extraction unit configured to extract at least one parameter from the received location determination request. A determining unit configured to determine a network node of the at least one UE based on the at least one extracted parameters. A requesting unit configured to request the determined network node to provide one or more measurement parameters. The receiving unit configured to receive a response comprising the one or more measurement parameters from the determined network node. A selecting unit configured to select at least one algorithm from a plurality of algorithms based on at least one of at least one condition and the one or more received measurement parameters. The determining unit configured to determine the location of the at least one UE based on the at least one selected algorithm.

[0044] In yet another exemplary embodiment, a computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to execute a method for determining user equipment (UE) location in a network is disclosed. The method comprises receiving, by a first network function, a location determination request for at least one UE from a second network function. The method comprises extracting, by the first network function, at least one parameter from the received location determination request. The method comprises determining, by the first network function, a network node of the at least one UE based on the at least one extracted parameter. The method comprises requesting, by the first network function, the determined network node to provide one or more measurement parameters. The method comprises receiving, by the first network function, a response comprising the one or more measurement parameters from the determined network node. The method comprises selecting, by the first network function, at least one algorithm from a plurality of algorithms based on at least one of at least one condition and the one or more received measurement parameters. The method comprises determining, by the first network function, the location of the at least one UE based on the at least one selected algorithm.BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWING

[0045] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure ofelectrical components, electronic components or circuitry commonly used to implement such components.

[0046] FIG. 1 illustrates an exemplary network architecture of a system for determining user equipment (UE) location in a network, in accordance with an embodiment of the present disclosure.

[0047] FIG. 2 illustrates an exemplary block diagram of the system for determining UE location in the network, in accordance with an embodiment of the present disclosure.

[0048] FIG. 3 illustrates an exemplary network architecture for positioning of a user equipment (UE) in the network, in accordance with an embodiment of the present disclosure.

[0049] FIG. 4 illustrates an exemplary flow diagram for positioning of the UE in the network, in accordance with an embodiment of the present disclosure.

[0050] FIG. 5 illustrates an exemplary flow diagram of a method for determining UE location in the network, in accordance with an embodiment of the present disclosure.

[0051] FIG. 6 illustrates an exemplary block diagram of a computer system in which or with which embodiments of the present disclosure may be implemented.

[0052] The foregoing shall be more apparent from the following more detailed description of the disclosure.LIST OF REFERENCE NUMERALS100 Network Architecture102 Plurality of Users104 Plurality of User Equipments (UEs)106 Network108 System110 Base Station(s) 200 Block Diagram202 Processor(s)204 Memory206 Interface(s)208 Processing Engine 210 Database212 Receiving Unit214 Extraction Unit216 Determining Unit218 Requesting Unit 220 Selecting Unit222 Execution Unit300 Network Architecture302 Location Management Function (LMF)304 Location Services (LCS) Client306 Gateway Mobile Location Cente308 Equipment Identity Register (EIR)310 Authentication Server Function (AUSF)312 Unified Data Management (UDM) 314 Access and Mobility Management Function (AMF)318 User Plane Function (UPF)320 Data network (DN)322 Session Management Function (SMF)324 Policy Control Function (PCF) 326 Network Slice Selection Function (NSSF)328 Short Message Service Function (SMSF)330 Network Data Analytics Function (NWDAF)332 Charging Function - Policy Control (CHF-PC)334 Network Exposure Function (NEF) 336 Binding Support Function (BSF)338 Diameter Routing Agent (DRA)340 Signaling Transfer Point (STP)400 Flow Diagram500 Flow Diagram600 Computer System610 External Storage Device620 Bus630 Main Memory640 Read-Only Memory650 Mass Storage Device660 Communication Ports670 ProcessorDETAILED DESCRIPTION

[0053] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the problems discussed above. Some of the problems discussed above might not be fully addressed by any of the features described herein. Example embodiments of the present disclosure are described below, as illustrated in various drawings in which like reference numerals refer to the same parts throughout the different drawings.

[0054] 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 theart with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.

[0055] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.

[0056] Also, it is noted that individual embodiments may be described as a process that is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination can correspond to a return of the function to the calling function or the main function.

[0057] The word “exemplary” and / or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and / or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,”and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive like the term “comprising” as an open transition word without precluding any additional or other elements.

[0058] Reference throughout this specification to “one embodiment” or “an embodiment” or “an instance” or “one instance” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present disclosure. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0059] The terminology used herein is to describe particular embodiments only and is not intended to be limiting the disclosure. As used herein, the singular forms “a”, “an”, and “the” are intended to include the plural forms as well, unless the context indicates otherwise. It will be further understood that the terms “comprises” and / or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. As used herein, the term “and / or” includes any combinations of one or more of the associated listed items. It should be noted that the terms “mobile device”, “user equipment”, “user device”, “communication device”, “device” and similar terms are used interchangeably for the purpose of describing the invention. These terms are not intended to limit the scope of the invention or imply any specific functionality or limitations on the described embodiments. The use of these terms is solely for convenience and clarity of description. The invention is not limited to any particular type of device or equipment, and it should be understood that otherequivalent terms or variations thereof may be used interchangeably without departing from the scope of the invention as defined herein.

[0060] While considerable emphasis has been placed herein on the components and component parts of the preferred embodiments, it will be appreciated that many embodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred embodiment as well as other embodiments of the disclosure will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter is to be interpreted merely as illustrative of the disclosure and not as a limitation.

[0061] A Location Measurement Function (LMF) in a wireless communication network processes data from multiple Radio Access Network (RAN) vendors deployed in different locations to calculate the position of User Equipments (UEs). One method used for location estimation is the Uplink Enhanced Cell ID (UL-ECID) method, which calculates the location of UEs based on measurements such as signal strength, time of arrival, and other radio metrics reported by RAN vendors. These measurements are collected through either Mobile Terminated Location Reports (MTLR) or Network Initiated Location Reports (NILR). The UL-ECID method estimates the UE's position using the Cell ID from the Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN) and RAN measurements. The RAN measurements are processed to calculate the UE's location based on information from multiple cells or radio access points. However, the accuracy of the UL-ECID method can be affected by factors (e.g., signal reflection, obstruction, or diffusion that can introduce significant errors in the location calculation. This leads to more significant location errors.

[0062] Furthermore, the RAN measurements (e.g., signal strength and time of arrival) used for location calculation are susceptible to environmental factors,interference, or network congestion and degrade positioning accuracy. For example, multipath effects, interference, and fading can distort signal strength, causing inaccuracies in the calculated position. Additionally, measurements taken from cells outside the UE's coverage area may compromise accuracy. The LMF might misinterpret the location due to inaccurate signal reflections, resulting in unreliable or incorrect positioning data. Additionally, the LMF is highly dependent on the measurements from the RAN, and any delays in transmitting or processing these measurement signals can further affect the precision and timeliness of the location calculation.

[0063] There is a need for a system and a method to address the challenges of inaccuracies in the location determination of the UEs in the network.

[0064] The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by providing a system and a method for determining location of a user equipment (UE) in a network. The present disclosure provides an enhanced UL-ECID position method to calculate the location of one of the UEs based on measurement parameters (e.g., a reference signal received power (RSRP), a reference signal received quality (RSRQ), a timing advance (TA) and an angle of arrival (AoA)) reported by the RAN. A location management function (LMF) receives a location determination request corresponding to the UE from an access and mobility management function (AMF). The LMF determines a random access network (RAN) vendor by extracting a New Radio Cell Global Identity (NR- CGI) from the location determination request. The LMF then sends a New Radio Positioning Protocol A (NRPPa) request to the determined RAN vendor. Upon receiving the NRPPa request, the determined RAN vendor sends one or more measurement parameter values (i.e., RSRP, RSRQ, TA and AoA) in an NRPPa response to the LMF.

[0065] The LMF is preconfigured with a plurality of positioning algorithms. Upon receiving the NRPPa response from the determined RAN vendor, the LMFcalculates location based on different combinations of measurement parameters received in the NRPPa response and the plurality of positioning algorithms. Thereafter, the LMF sends the calculated location to the AMF. Further, the LMF may ignore the measurement parameter value which is out of range or invalid and calculate the location based on the remaining measurement values received from the RAN.

[0066] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings.

[0067] FIG. 1 illustrates an exemplary network architecture (100) of a system (108) for determining user equipment (UE) location in a network (106), in accordance with an embodiment of the present disclosure.

[0068] As illustrated in FIG. 1, the network architecture (100) may include one or more computing devices or UEs (104-1, 104-2... 104-N) associated with one or more users (102-1, 102-2... 102-N) in an environment. A person of ordinary skill in the art will understand that one or more users (102-1, 102-2... 102-N) may be individually referred to as the user (102) and collectively referred to as the users (102). Similarly, a person of ordinary skill in the art will understand that one or more UEs (104-1, 104- 2... 104-N) may be individually referred to as the UE (104) and collectively referred to as the UEs (104). A person of ordinary skill in the art will appreciate that the terms “computing device(s)” and “user equipment” may be used interchangeably throughout the disclosure. Although three UEs (104) are depicted in FIG. 1, however, any number of the UEs (104) may be included without departing from the scope of the ongoing description.

[0069] In an embodiment, the UE (104) may include smart devices operating in a smart environment, for example, an Internet of Things (loT) system. In such an embodiment, the UE (104) may include, but is not limited to, smart phones, smart watches, smart sensors (e.g., a mechanical sensor, a thermal sensor, an electrical sensor,a magnetic sensor, etc.), networked appliances, networked peripheral devices, networked lighting system, communication devices, networked vehicle accessories, networked vehicular devices, smart accessories, tablets, smart televisions (TVs), computers, smart security systems, smart home systems, other devices for monitoring or interacting with or for the user (102) and / or entities, or any combination thereof. A person of ordinary skill in the art will appreciate that the UE (104) may include, but is not limited to, intelligent, multi-sensing, network-connected devices, that can integrate seamlessly with each other and / or with a central server or a cloud-computing system or any other device that is network-connected.

[0070] In an embodiment, the UE (104) may include, but is not limited to, a handheld wireless communication device (e.g., a mobile phone, a smart phone, a phablet device, and so on), a wearable computer device (e.g., a head-mounted display computer device, a head-mounted camera device, a wristwatch computer device, and so on), a Global Positioning System (GPS) device, a laptop computer, a tablet computer, or another type of portable computer, a media playing device, a portable gaming system, and / or any other type of computer device with wireless communication capabilities, and the like. In an embodiment, the UE (104) may include, but is not limited to, any electrical, electronic, electro-mechanical, or an equipment, or a combination of one or more of the above devices such as virtual reality (VR) devices, augmented reality (AR) devices, a laptop, a general-purpose computer, a desktop, a personal digital assistant, a tablet computer, a mainframe computer, or any other computing device. Further, theUE (104) may include one or more in-built or externally coupled accessories including, but not limited to, a visual aid device such as a camera, an audio aid, a microphone, a keyboard, and input devices for receiving input from the user (102) or an entity such as a touch pad, a touch enabled screen, an electronic pen, and the like. A person of ordinary skill in the art will appreciate that the UE (104) may not be restricted to the mentioned devices and various other devices may be used.

[0071] In an embodiment, the network (106) may include at least one of the 4G network, the 5G network, the 6G network, or the like. The network (106) may enable the UE (104) to communicate with other devices in the network architecture (100) and / or with the system (108). The network (106) may include a wireless card or some other transceiver connection to facilitate this communication. In another embodiment, the network (106) may be implemented as, or include any of a variety of different communication technologies such as a wide area network (WAN), a local area network (LAN), a wireless network, a mobile network, a Virtual Private Network (VPN), an internet, an intranet, a public network, a private network, a packet-switched network, a circuit- switched network, an ad hoc network, an infrastructure network, a Public- Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof. In another embodiment, the network 106 includes, by way of example but not limitation, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, or so forth.

[0072] The network architecture (100) comprises a plurality of base stations (110-1, 110-2... .110-N). A person of ordinary skill in the art will understand that one or more base stations (110-1, 110-2... 110-N) may be individually referred to as the base station (110) and collectively referred to as the base station (110). The base station (110) may be a network infrastructure that provides wireless access to one or more terminals associated therewith. The base station may have coverage defined to be a predetermined geographic area based on the distance over which a signal may be transmitted. In an aspect, the base station (110) may be referred to as radio access network (RAN) node. The base station (110) may be, but not be limited to, wireless access point, NodeB, evolved NodeB (eNodeB), 5G node or next generation NodeB (gNB), wireless point, transmission / reception point (TRP), and the like. In anembodiment, the base station (110) may include one or more operational units that enable telecommunication between two or more UEs (104). In an embodiment, the one or more operational units may include, but not be limited to, transceivers, baseband unit (BBU), (remote radio unit - RRU), antenna, mobile switching centres, radio network control units, one or more processors associated thereto, and a plurality of network entities or any custom built functions executing one or more processorexecutable instructions, but not limited thereto. Each base station (110) of the plurality of base stations (110) includes a load capacity value associated therewith, and the plurality of base stations (110) may be associated with a geographical area. In an embodiment, the geographical area may indicate the signal coverage of the set of base stations (110). The network (106) may be formed by the plurality of base stations (110) communicatively coupled to enable telecommunication exchanges between one or more UEs (104).

[0073] In FIG. 1, the UE (104) may communicate with the system (108) through the network (106). In particular, the UE (104) may be communicatively coupled with the network (106). The coupling includes steps of receiving, by the network (106), a connection request from the UE (104). Upon receiving the connection request, the coupling includes steps of sending, by the network (106), an acknowledgment of the connection request to the UE (104). Further, the coupling includes steps of transmitting a plurality of signals in response to the connection request. The plurality of signals is responsible for establishing communication of the UE (104) with the system (108) to determine the location of the UE (104) in the network (106), as explained in detail in FIGs. 2-6.

[0074] Although FIG. 1 shows exemplary components of the network architecture (100), in other embodiments, the network architecture (100) may include fewer components, different components, differently arranged components, or additional functional components than depicted in FIG. 1. Additionally, oralternatively, one or more components of the network architecture (100) may perform functions described as being performed by one or more other components of the network architecture (100).

[0075] FIG. 2 illustrates an exemplary block diagram (200) of the system (108) for determining UE location in the network (106), in accordance with an embodiment of the present disclosure. FIG. 2 is explained in conjunction with FIG. 1.

[0076] In an embodiment, the system (108) may include one or more processor(s) (202). The one or more processor(s) (202) may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, logic circuitries, and / or any devices that process data based on operational instructions. Among other capabilities, the one or more processor(s) (202) may be configured to fetch and execute computer-readable instructions stored in a memory (204) of the system (108). The memory (204) may be configured to store one or more computer-readable instructions or routines in a non-transitory computer readable storage medium, which may be fetched and executed to create or share data packets over a network service. The memory (204) may include any non-transitory storage device including, for example, volatile memory such as a Random-Access Memory (RAM), or a non-volatile memory such as an Erasable Programmable Read Only Memory (EPROM), a flash memory, and the like.

[0077] In an embodiment, the system (108) may include an interface(s) (206). The interface(s) (206) may include a variety of interfaces, for example, interfaces for data input and output devices (I / O), storage devices, and the like. The interface(s) (206) may facilitate communication through the system (108). The interface(s) (206) may also provide a communication pathway for one or more components of the system (108).

[0078] The system (108) is configured to determine UE location in the network(106).

[0079] In an aspect, the system (108) may be embedded in a first network function. In another aspect, the system (108) may be part of the first network function. The first network function is a location management function (LMF) (i.e., LMF (302) as shown in FIG. 3). In an aspect, the LMF is a network function responsible for performing positioning procedures and generating accurate location estimates for UEs.

[0080] In an aspect, the first network function (i.e., LMF) comprises the processing engine (208). The processing engine (208) comprises a receiving unit (212), an extraction unit (214), a determining unit (216), a requesting unit (218), a selecting unit (220), and an execution unit (222).

[0081] The receiving unit (212) is configured to receive a location determination request for at least one UE (104) from a second network function. In an aspect, the LMF receives the location determination request (e.g., location determination request comprising New Radio Cell Global Identity (NR-CGI), as shown in FIG. 4) for the at least one UE from the second network function, which is an access and mobility management function (AMF) (i.e., AMF (314), as shown in FIG. 3). The AMF is responsible for mobility management, registration, UE context handling, and interaction with other core functions. When the AMF identifies a need to obtain the UE’s location, such as for emergency services, regulatory requirements, loT tracking, handover optimization, or application-level services, the AMF generates a location determination request comprising one or more parameters, such as UE identifiers. The AMF then sends the location determination request for the at least one UE to the LMF.

[0082] The extraction unit (214) is configured to extract at least one parameter from the received location determination request. In an aspect, upon receiving the location determination request from the AMF, the LMF is configured to extract the atleast one parameter from the location determination request. The at least one extracted parameter comprises, but is not limited to, a New Radio Cell Global Identity (NR- CGI), a tracking area identifier (ID), an International Mobile Subscriber Identity (IMSI), a temporary identifier, and a subscription identifier.

[0083] In an aspect, the NR-CGI refers to a globally unique identifier used to identify a cell within a public land mobile network (PLMN). The NR-CGI is composed of a PLMN identifier and an NR cell identifier (NR cell ID). The PLMN identifier comprises a mobile country code (MCC) and a mobile network code (MNC), which identify the operator’s network. The NR cell ID refers to a unique cell-level identifier assigned to the base station. The NR-CGI allows the network to uniquely reference the cell serving or detecting the UE for operations, such as mobility management, measurement reporting, handover, and location determination.

[0084] In an aspect, the tracking area identifier refers to a hierarchical network identifier that designates a tracking area, which is a group of cells used for managing UE mobility in idle mode. The tracking area identifier consists of the PLMN identifier (MCC + MNC) and a tracking area code (TAC), which identifies the specific tracking area within the operator’s network. The TAI is used by the network to perform mobility-related functions, such as paging, tracking area updates, and registration management. When the UE moves between cells belonging to different TAIs, the UE initiates a tracking area update procedure.

[0085] In an aspect, the international mobile subscriber identity (IMSI) refers to a permanent, globally unique identifier associated with a subscriber’s subscriber identity module (SIM) or subscription. The IMSI consists of the MCC, the MNC, and a mobile subscriber identification number (MSIN). The IMSI is primarily used for authenticating the subscriber, authorizing network access, and linking the UE to subscription data in a home subscriber server (HSS) or a unified data management (UDM).

[0086] In an aspect, the temporary identifier refers to a network-assigned identity allocated to the UE to protect the subscriber’s permanent identity (e.g., international mobile subscriber identity (IMSI), subscription permanent identifier (SUPI)). The temporary identifier enables the network to identify the UE during signaling procedures (e.g., paging, mobility management, session establishment) without exposing the permanent subscriber identity. The temporary identifier may be updated or reallocated by the network to enhance privacy and security.

[0087] In an aspect, the subscription identifier (SUPI) refers to an identifier that uniquely identifies the subscriber’s account or subscription within the operator’s network infrastructure. The subscription identifier may take the form of an IMSI-based SUPI or a network access identifier (NAI)-based SUPI.

[0088] Upon performing the extraction of the at least one parameter, the determining unit (216) is configured to determine a network node (110) of the at least one UE (104) based on the at least one extracted parameter. In an aspect, the LMF determines the network node of the UE based on one extracted parameter (e.g., NR- CGI, tracking area ID, IMSI, temporary identifier and subscription identifier). The LMF uses the NR-CGI to directly identify the specific NR cell and the corresponding base station (e.g., gNB) to which the UE is attached. The LMF may further use a tracking area ID to determine a set of base stations operating within the identified tracking area. Additionally, the LMF may employ subscriber-related identifiers, such as the IMSI, the temporary identifier (e.g., globally unique temporary identifier (GUTI) or temporary mobile subscriber identity (TMSI)), and the subscription identifier, to retrieve UE context from the AMF or a Unified Data Management (UDM). The retrieved context includes serving cell information that enables the LMF to map the UE to the correct base station. By using any combination of the NR-CGI, the tracking area identifier, the IMSI, the temporary identifier, and the subscription identifier, the LMF accurately determines the base station (110) currently serving the UE (104).

[0089] In an aspect, the network node (110) is a radio access network (RAN) node. The RAN node refers to a network entity configured to provide radio access functionality within the network. The RAN node performs wireless communication with one or more user equipment (UEs) through standardized radio interfaces, facilitating the transfer of both user-plane and control-plane data between the UEs and the network. The RAN node may correspond to a base station. The base station may be a next-generation NodeB (gNB) in 5G New Radio (NR), an evolved NodeB (eNB) in LTE, or any similar radio base station technology capable of supporting cellular access. The RAN node may maintain identifiers, such as cell identifiers, tracking area identifiers, and system information, which are broadcast or communicated to UEs to enable network access. The RAN node acts as the access point through which the UE attaches to the network and maintains continuous connectivity, thereby serving as the primary point of interaction between the UEs and the network. The RAN node (e.g., base station) helps in determining the location of the UE by providing radio-level measurements, signaling support, and network information required by the LMF. For example, the UE (104-1) may correspond to the RAN node (e.g., Base station 110-2).

[0090] Upon determining the RAN node of the UE (104), the requesting unit (218) is configured to request the determined network node to provide one or more measurement parameters. In an aspect, the LMF may send a request (e.g., new radio provisioning protocol A (NRPPa) request, as shown in FIG. 4) to the determined network node (e.g., base station) to obtain one or more measurement parameters that are required for calculating and validating the location of the UE (104). In an aspect, the Location Management Function (LMF) communicates with the base station (gNB) using the NRPPa protocol (NR Positioning Protocol A) for obtaining positioning- related information. When the LMF requires UE measurements for determining the UE’s location, the LMF sends an NRPPa Request to the RAN node (e.g., base station such as gNB). The NRPPa request may include parameters such as the UE identifier, the required positioning method (e.g., AoA, TDoA, RTT), measurement configuration,reporting requirements, or timing constraints. Upon receiving the NRPPa request, the base station performs the requested measurement actions on the associated UE and returns the results to the LMF using an NRPPa response. In an aspect, an NRPPa interface between the LMF and the RAN node enables standardized, secure, and realtime exchange of positioning information between the LMF and the RAN node.

[0091] Upon requesting the one or more measurement parameters from the determined node, the receiving unit (212) is configured to receive the response (e.g., NRPPa response, as shown in FIG. 4) comprising the one or more measurement parameters from the determined network node. In an aspect, upon receiving the request (e.g., NRPPa request) for the measurement parameters from the LMF, the RAN node (e.g., base station) sends the response (e.g., NRPPa response) to the LMF, comprising one or more measurement parameters. By requesting the measurement parameters from the determined RAN node (i.e., serving base station of the UE), the LMF ensures that accurate and real-time measurements are received directly from the network node to which the UE is connected. These measurements are then processed by the LMF to compute the UE’s geographical location or to verify the integrity and consistency of the previously estimated location.

[0092] In an aspect, the one or more received measurement parameters comprise a reference signal received power (RSRP), a reference signal received quality (RSRQ), a timing advance (TA) and an angle of arrival (AoA). In an aspect, the RSRP represents the average received power of specific reference signals transmitted by the base station. The RSRP is measured at the UE to determine signal strength and cell selection / reselection performance. The RSRP is calculated by averaging the linear power of all resource elements (REs) carrying the reference signal within a serving or neighboring cell. Higher RSRP indicates stronger downlink coverage and better link stability. RSRP is used for cell selection, mobility decisions, and various positioning algorithms. In an aspect, the RSRQ represents the quality of the received referencesignal by combining the signal strength (RSRP) and the overall received signal power. The RSRQ reflects the level of interference and noise present in a cell’s coverage area. Lower RSRQ values indicate higher interference or reduced channel quality. RSRQ is used in mobility management, handover triggering, and cell-edge performance evaluation, as well as in network-assisted positioning. In an aspect, the TA refers to a time-based measurement indicating the adjusting value applied by the UE to its uplink transmission timing so that the uplink signals arrive at the base station in synchronized time alignment. TA is derived from the round-trip propagation delay between the UE and the base station. The TA value effectively represents the physical distance between the UE and the cell site, with each TA step corresponding to a defined propagation distance. The TA is used in uplink time synchronization and in network-based positioning. In an aspect, the AoA is the estimated direction or angle from which a UE’s uplink signal arrives at the antenna array of the base station. The AoA is determined using beamforming, antenna array processing, or phase-difference calculations across multiple antenna elements. AoA provides directional spatial information about the location of the UE relative to the receiving cell. The AoA is used in network-based positioning (e.g., AoA methods), beam management and beam selection, interference mitigation, and handover optimization.

[0093] In an aspect, the LMF is configured with a plurality of algorithms to determine the location of the UE. The plurality of algorithms (e.g., Algo 1, Algo 2, Algo 3 and so on) is designed to determine the location of the UE using one or more measurement parameters and one or more conditions. Further, the plurality of algorithms may operate independently or in combination based on the measurement parameters and required location accuracy.

[0094] The selecting unit (220) is configured to select at least one algorithm from the plurality of algorithms based on at least one of at least one condition and the one or more received measurement parameters. The selecting unit (220) is configuredto select one algorithm based on one condition, measurement parameters, or a combination of both (e.g., the condition and the measurement parameters). In an aspect, the plurality of algorithm is stored in the database (210).

[0095] In an aspect, the at least one condition comprises one or more of a priority condition of each of the one or more received measurement parameters, a range condition of each of the one or more received measurement parameters, and a preconfigured algorithm condition of the determined network node. In an aspect, the selecting unit (220) is configured to apply at least one condition or a combination of conditions, depending on the availability, reliability or characteristics of the received measurement parameters. By enabling the selection of conditions, the LMF provides a flexible and adaptive mechanism for choosing the most suitable algorithm or validating the measurement parameters for accurate location determination.

[0096] In an aspect, the pre-configured algorithm condition refers to an algorithm whose logic, parameters, thresholds, and operational rules are established in advance by the network operator or according to standard specifications. The algorithm is stored within the LMF and is directly invoked when the corresponding event, request, or condition occurs. In the pre-configured algorithm condition, the determining unit is configured to preconfigure an algorithm from the plurality of algorithms for each network node based on the one or more received measurement parameters corresponding to each network node.

[0097] In an aspect, the pre-configuration is performed based on the type, capability, and nature of the one or more measurement parameters that are expected to be received from the respective network node. Each network node may support different positioning measurement techniques (e.g., TDoA, AoA, RTT, RSRP), and therefore, the determining unit pre-associates or pre-maps a specific algorithm with each network node in accordance with the measurement parameters that the network node provides. Thus, when measurement parameters are later received from a particularnetwork node, the determining unit quickly identifies and invokes the pre-configured algorithm corresponding to that network node without performing dynamic algorithm selection. This improves processing efficiency and ensures that the determining unit uses an algorithm that is most suitable for the measurement parameters provided by the network node.

[0098] For example, three different RAN nodes in the network, i.e., gNB-A, gNB-B, gNB-C. The preconfigured algorithm comprises Algo 1 as tracking area-based algorithm, Algo 2 as angle-based algorithm, and Algo 3 as signal-strength-based algorithm. The determining unit pre-configures algorithms for each node, such as for gNB-A, the determining unit pre- configures the Algo 1, i.e., Tracking area based algorithm because gNB-A provides tracking area (TA) measurements. For gNB-B, the determining unit pre- configures the Algo 2, i.e., angle-based algorithm because gNB- B provides AoA / AoD measurements. For gNB-C, the determining unit pre-configures Algo 3, i.e., signal-strength- based algorithm because gNB-C provides RSRP / RSRQ measurements. If the LMF receives measurement parameters (e.g., TA from gNB-A), then the LMF automatically invokes the pre-configured tracking area based algorithm. If the LMF receives AoD / AoA from gNB-B, then the LMF invokes the angle-based algorithm. If the LMF receives RSRP from gNB-C, then the LMF triggers the signalstrength-based algorithm. The location of the UE is determined using the algorithm that best matches the measurement parameters of the corresponding network node, without requiring real-time algorithm selection or decision-making.

[0099] In an aspect, the priority condition refers to a condition that assigns a higher or lower priority level to an action or entity based on specific parameters or triggers. The priority condition may depend on factors, such as urgency, importance, system load, timing requirements, network state, or predefined policies. In the priority condition, the selecting unit is configured to perform selection of the at least one algorithm based on a priority of the one or more received measurement parameters anda pre- configured algorithm of the determined network node. In an aspect, in response to receiving the one or more measurement parameters from the determined network node, the selecting unit is configured to apply the priority condition for selecting at least one algorithm to be executed for determining the location of the UE. The priority condition is based on the priority assigned to each of the one or more received measurement parameters, and the pre-configured algorithm associated with the determined network node. Each measurement parameter may be assigned a different priority level depending on its accuracy, reliability, or suitability for a particular positioning scenario. Similarly, LMF may store one or more pre-configured algorithms optimized for specific types of measurements. Upon applying the priority condition, the selecting unit evaluates which measurement parameters have the highest priority and identifies the corresponding algorithm best suited to utilize those high-priority measurements. The selecting unit then selects the at least one algorithm that satisfies both the measurement-priority condition and the pre-configured algorithm condition of the network node.

[0100] For example, the priority assigned to measurement parameters, such as TA - high priority, AoA - Medium Priority, and RSRP - low priority. The selecting unit evaluates the priority of the received parameters. As TA has highest priority, the selecting unit selects the preconfigured algorithm having the TA for determining the UE’s location. Accordingly, the selecting unit ensures that the most reliable measurement parameter and the most suitable preconfigured algorithm available, thereby improving accuracy and efficiency of the UE location determination process.

[0101] In an aspect, the range condition is a condition that evaluates whether a given input lies within a permitted interval (e.g., between a minimum threshold and a maximum threshold). If the measurement or parameter stays inside this interval, it is considered valid or within range. If the measurement or parameter falls outside the expected range, it may be flagged as invalid, abnormal, or trigger another action. Forexample, for signal strength (e.g., RSRP) to be considered reliable, the RSRP may need to be between -120 dBm and -60 dBm. The timing advance value may be validated against a range condition to ensure consistency with the UE’s estimated distance from the cell.

[0102] In the range condition, the determining unit (216) is configured to detect whether at least one measurement parameter of the one or more received measurement parameters is out of range or invalid based on a predefined range. The predefined range refers to a pre-established interval associated with at least one measurement parameter, the interval being configured in advance and comprising at least one of a minimum threshold value and a maximum threshold value, such that a value of the measurement parameter is determined to satisfy or violate the predefined range based on whether the value falls within or outside the interval. Each measurement parameter is compared with a corresponding predefined range to determine whether the measurement parameter is out of range or invalid. Upon determining that the measurement parameter is out of range, the measurement parameter is considered invalid and not used to determine the location of the UE. The location of the UE is determined based on the valid measurement parameters (i.e., parameters within the predefined range).

[0103] If the determining unit (216) detects that at least one measurement parameter falls outside the predefined range, or is otherwise identified as invalid, the determining unit (216) is configured to disregard the at least one invalid measurement parameter. Further, upon detecting that the at least one measurement parameter of the one or more received measurement parameters is out of range or invalid based on the predefined range, the determining unit (216) is configured to determine the location of the at least one UE based on one or more remaining valid measurement parameters. Even though one measurement was invalid, the determining unit (216) still determines a reliable and accurate UE location based on the valid parameters. By excluding the out-of-range or invalid measurement parameter(s), the determining unit (216) ensuresthat erroneous or unrealistic measurements do not adversely impact the accuracy or integrity of the final location determination of the at least one UE (104).

[0104] For example, measurements received from the RAN node for UE positioning may include RSRP = -82 dBm, AoA = 205°, and Timing Advance (TA) = 12.5 ps. The predefined valid ranges may include RSRP range: -140 dBm to -40 dBm, AoA range: 0° to 180°, and TA range: 0 ps to 20 ps. The determining unit performs a range- validity check for each parameter, i.e., RSRP = -82 dBm is valid (within -140 to -40 dBm), AoA = 205° is invalid (outside the 0°-180° range), and TA = 12.5 ps is valid (within 0-20 ps). Based on the validity check, the determining unit (216) flags the AoA measurement as invalid. The determining unit (216) then determines the UE’s location using only the valid measurement parameters, i.e., RSRP and TA.

[0105] Upon performing the selection of the algorithm, the determining unit (216) is configured to determine the location of the at least one UE based on the at least one selected algorithm. In an aspect, the determining unit (216) determines the location of the UE based on the selected algorithm. For example, for gNB-B, a pre-configured mapping indicates that gNB-B supports angle-based measurements (e.g., AoA), while signal-strength parameters (e.g., RSRP) and timing parameters (e.g., TA) are treated as supplementary inputs. Accordingly, the pre-configured algorithm for gNB-B is the angle-based positioning algorithm.

[0106] If an AoA measurement is received from the RAN node for the UE (e.g.,AoA = 75°), then even if other conditions, such as a priority condition (e.g., RSRP having higher priority) or a range condition (e.g., TA within a valid range) exist, the selecting unit (220) selects the pre-configured algorithm condition because gNB-B has an angle-based algorithm predefined in the mapping table. Thus, the selected condition is the pre-configured algorithm condition, and the selected algorithm is the angle- based positioning algorithm. The determining unit (216) then determines the UE’s locationprimarily using AoA, while RSRP and TA may be utilized for refinement or error bounding.

[0107] In an aspect, the execution unit (222) is configured to perform an integrity check on the determined location of the at least one UE (104). The integrity check is performed based on at least one of, but not limited to, a multi-round trip time (multi-RTT), a downlink angle of departure (DL-AoD), a DL-time difference of arrival (DL-TDoA), an uplink- TDoA (UL-TDoA), and a UL-AoA.

[0108] In an aspect, the Round-Trip Time (RTT) refers to a time-based measurement representing the total propagation duration of a signal transmitted from the base station to the user equipment (UE) and a corresponding response signal returned from the UE to the base station, the RTT being indicative of a distance between the base station and the UE.

[0109] In an aspect, multi-RTT refers to a timing-based measurement technique in which multiple round-trip signal exchanges (e.g., reference signals, synchronization signals) occur between the UE and one or more network nodes (e.g., base station). Each round trip involves transmitting a signal from the base station to the UE and receiving the corresponding response from the UE. The measured time interval reflects the propagation delay between the UE and the serving or neighboring cells. By performing multiple RTT measurements either sequentially or concurrently, the network enhances the accuracy and reliability of distance estimation, reduces the impact of fading or interference, and improves the precision of positioning calculations.

[0110] In an aspect, the Angle of Departure (AoD) refers to the angular direction at which a radio signal leaves a transmitting antenna (i.e., base station (gNB / eNB)) toward the user equipment (UE). The AoD comprises at least one of an azimuth angle or an elevation angle associated with the departing radio signal. In an1 aspect, the DL- AoD represents the angle at which a downlink signal leaves the transmit antenna array of the serving or neighboring base station. The DL-AoD is determined based on the beam direction or the antenna radiation pattern used for transmitting reference signals, such as channel state information-reference signal (CSI-RS) or synchronization signal block (SSB). As the UE receives the signal arriving from a known transmission direction, the network infers the spatial relationship between the UE and the cell. DL-AoD is used in advanced positioning, beam management, and spatial filtering operations in multi-antenna (MIMO) deployments.

[0111] In an aspect, the Direction of Arrival (DoA) refers to an angular parameter representative of the direction from which a radio signal, transmitted by the user equipment (UE), is received at the base station. The DoA comprises at least one of the azimuth component or the elevation component determined based on the spatial characteristics of the received signal across an antenna array. In an aspect, the DL- TDoA is the relative time difference at which the UE receives downlink reference signals transmitted from two or more synchronized base stations. As each cell transmits its reference signal at a known time, the UE measures the difference in arrival times and reports the measured differences to the network. The measured time differences correspond to varying propagation distances from the UE to multiple cell sites, enabling multilateration-based positioning of the UE. DL-TDoA is widely used in Observed Time Difference of Arrival (OTDOA) positioning methods.

[0112] In an aspect, multilateration-based positioning refers to a positioning technique that determines the location of the UE by measuring its distance or timebased measurements (e.g., RTT, TDoA) from multiple known reference points. Each reference node provides a respective measurement comprising at least one of a roundtrip time (RTT), a time-difference of arrival (TDoA), or any equivalent rangeindicative metric. The multilateration process determines the UE location by computing an intersection region of a plurality of geometric loci derived from therespective measurements. Each geometric locus represents a predefined distance boundary relative to the corresponding reference node. For example, if the UE distance from Cell A is 500 m, from Cell B is 600 m, and from Cell C is 550 m, multilateration uses these ranges to determine the unique point where all three distance boundaries meet.

[0113] In an aspect, the Observed Time Difference of Arrival (OTDOA) refers to a downlink positioning technique in which the user equipment (UE) determines a plurality of time-difference measurements representing respective differences in arrival times of positioning reference signals transmitted from a serving cell and one or more neighbouring cells. Each time-difference measurement constitutes a range-difference constraint defining a corresponding hyperbolic locus, and the UE location is determined by computing an intersection region of the plurality of range-difference constraints.

[0114] In an aspect, the UL-TDoA refers to timing differences observed by multiple base stations when receiving the UE’s uplink reference signals (e.g., SRS). As the UE transmits at a specific time, each receiving base station measures the arrival time of the uplink signal. Comparing the time stamps across different cells yields differences in propagation delay, allowing the network to estimate the UE’s location using multilateration or hybrid positioning algorithms. UL-TDoA is less affected by clock drift on the UE side since the measurements are performed at the network.

[0115] In an aspect, the UL-AoA refers to the direction or angle from which the UE’s uplink signal arrives at the antenna array of the receiving base station. AoA is calculated by evaluating phase differences, amplitude variations, or time differences across multiple antennas in the array. UL-AoA provides directional spatial information about the UE’s relative position to the receiving cell. The UL-AoA is used in UL- ECID, multi-cell positioning, beam selection, interference mitigation, and networkbased triangulation methods.

[0116] The execution unit (222) is configured to verify whether the determined location of the UE is accurate, reliable, and consistent with the one or more measurements obtained from the serving and neighboring network nodes (e.g., base stations). After the location of the UE, the execution unit (222) is configured to crossvalidate the location using the measurement parameters. Each measurement provides an independent indicator of the UE’s physical position relative to network’s antenna sites. The integrity check is performed to ensure that the reported location is not corrupted, measurement anomalies or spoofing attempts are detected, errors in the location computation are identified, and only trustworthy location information is forwarded to higher-level applications.

[0117] In the integrity check, the execution unit (222) is configured to verify whether the measured value of the parameter is consistent with the determined (x, y) location of the UE. If the parameter deviates beyond an acceptable threshold, the execution unit (222) may raise the location integrity alarm or recompute the location. For example, the multi-RTT gives the propagation delay between the UE and the cell. For the determined location at coordinates (x, y), the execution unit computes the expected RTT based on geometric distance. If |RTT_measured - RTT_expected| > threshold, then the determined location is inconsistent. If the UE’s computed angular direction from the gNB does not match the DL-AoD (within beamwidth tolerance), the location is inconsistent. In an aspect, the beamwidth tolerance refers to the acceptable range within which this deviation occurs without degrading system performance. For example, UL-AoA measured at the base station (e.g., gNB-B) = -17°. Computed direction from UE to the base station (e.g., gNB-B) = -16.5°. If the difference between the measured direction and the computed direction < 1°, then the direction (i.e., measured UL-AoA) is PASS. The difference between the measured direction and the computed direction is 0.5° (i.e., -17 - (-16.5) = -0.5; |— 0.5| = 0.5°). Since the difference is less than 1°, the direction check (i.e., measured UL-AoA) is considered a PASS.

[0118] After performing the integrity check, the first network function (i.e., LMF) sends the determined location of the UE to the second network function (i.e., AMF).

[0119] FIG. 3 illustrates another exemplary network architecture (300) for positioning of the UE (104) in the network (106), in accordance with an embodiment of the present disclosure.

[0120] The network architecture (300) comprises a Location Management Function (LMF) (302), a Location Services (LCS) Client (304), a Gateway Mobile Location Center (GMLC) (306), an Equipment Identity Register (EIR) (308), an Authentication Server Function (AUSF) (310), a Unified Data Management (UDM) (312), an Access and Mobility Management Function (AMF) (314), a random access network (RAN) Next Generation Node B (gNB) (110), a User Plane Function (UPF) (318), a data network (DN) (320), a Session Management Function (SMF) (322), a Network Exposure Function (NEF) (334), a Policy Control Function (PCF) (324), a Network Slice Selection Function (NSSF) (326), a Short Message Service Function (SMSF) (328), a Network Data Analytics Function (NWDAF) (330), a Charging Function - Policy Control (CHF-PC) (332), a Signaling Transfer Point (STP) (340), a Diameter Routing Agent (DRA) (338), and a Binding Support Function (BSF) (336).

[0121] In one aspect, the network architecture (300) may include a fifthgeneration (5G) core (5GC) network. The network architecture (300) may include advanced generations (e.g., 6G and so on).

[0122] In an aspect, the LMF (302) is a core network function responsible for managing the location of the UE to support services (e.g., mobility management, handovers, and location-based services). The LMF (302) tracks and updates the geographical location of the UE (e.g., mobile devices) within the network, such as the network (106). The LMF (302) monitors the UE's position as the UE moves acrossdifferent areas and cells within the network. The LMF (302) supports location-based services (e.g., real-time location sharing, navigation, or emergency services), ensuring that the location of the UE is accurately known and managed.

[0123] In an aspect, the LCS Client (304) refers to a device or application that requests and uses location-based services provided by the network. The LCS client (304) interacts with the network to obtain the geographical location of the UE for various services. The LCS client (304) requests location data, such as the geographical position of the UE from the network.

[0124] In an aspect, the Gateway Mobile Location Center (GMLC) (306) is a network element in the telecommunication network to support the Location-Based Services (LBS). The GMLC (306) is an interface between the mobile network and external Location-Based Services (LBS) providers (e.g., emergency services, navigation applications, or asset tracking systems). The GMLC (306) handles requests for location information and ensures that the GMLC (306) is securely relayed to the requesting service.

[0125] In an aspect, the Equipment Identity Register (EIR) (308) is a network element in the telecommunication networks that manages and tracks the identity of mobile devices (user equipment, or UE) based on their unique identifiers, such as International Mobile Equipment Identity (IMEI) number. The EIR (308) helps ensure network security, prevent fraud, and maintain the integrity of the network.

[0126] In an aspect, the Authentication Server Function (AUSF) (310) is a network element that handles the authentication of the UE when the UE tries to access the network. The AUSF (310) plays a vital role in ensuring network security by verifying the identity of users and protecting the integrity of the network. The AUSF (310) communicates with the Access and Mobility Management Function (AMF) (314) and the Unified Data Management (UDM) (312) to perform the authentication process.The AUSF (310) verifies the identity of the UE based on credentials (e.g., Subscription Permanent Identifier (SUPI) or Subscription Concealed Identifier (SUCI) stored in the UDM (312). In an aspect, the SUPI is an identifier in the network used to identify a subscriber (i.e., a user or UE). The SUPI is an essential element in the authentication and identification processes within the network. The SUPI serves as the permanent, globally unique identity of a subscriber. The AUSF (310) uses the SUPI to identify the UE when the UE attempts to connect to the network or during authentication procedures. The network operator typically assigns the SUPI and stays the same throughout the subscriber’s time in the network, making the SUPI a long-term identifier. In an aspect, the SUCI is a privacy-enhanced version of the SUPI used in the network. The SUCI is generated by encrypting the SUPI to protect the subscriber’s identity and prevent the SUCI from being exposed during communication between the UE and the network.

[0127] In an aspect, the Unified Data Management (UDM) (312) is a network element responsible for managing user-related data and subscription information and subscriber authentication, authorization, mobility management, and other critical services. By storing and processing user profiles, the UDM (312) ensures secure and efficient access to network services while facilitating subscriber management and service delivery.

[0128] In an aspect, the Access and Mobility Management Function (AMF) (314) is a network element responsible for handling access management and mobility management. The AMF (314) interacts with other network elements to ensure secure and seamless connection, mobility, and session management for the UE in a 5G network. The AMF (314) handles initial access requests from the UE when the UE first tries to connect to the network. The AMF (314) tracks the UE’s location as the UE moves across different network cells or regions. The AMF (314) handles location updates and handover management when the UE moves from one cell to another,ensuring continuous connectivity without service interruptions. The AMF (314) works with the Session Management Function (SMF) (322) and the User Plane Function (UPF) (318) to handle the session continuity when the UE moves between different network slices or access points. The AMF (314) handles the authentication of the UE during the registration process, working with the AUSF (310) to validate the user's identity and credentials (such as SUPI or SUCI). Once the authentication is successful, the AMF (314) allows the UE to access network services.

[0129] In an aspect, the Next Generation Node B (gNB) (110) is the 5G base station in the RAN of the network. The gNB (110) serves as an access point between the UE and the 5G core network. The gNB (110) provides wireless communication, manages radio resources, and ensures the connection between the UE and the rest of the network.

[0130] In an aspect, the User Plane Function (UPF) (318) is a network element in the 5G core network that is responsible for managing the user plane traffic, i.e., the actual data (such as internet browsing, video streaming, etc.) that is transmitted between the UE and the internet or other network services. The UPF (318) performs functions (e.g., packet forwarding, traffic management, NAT (Network Address Translation), mobility anchoring, and QoS management) to ensure efficient and secure data transmission. The UPF (318) works with other network elements (e.g., the SMF (322), AMF (314), and PCF (324)) to seamlessly handle the user data, support network slicing, and facilitate advanced features in the network.

[0131] In an aspect, the Data Network (DN) (320) refers to external networks that provide services and applications to users (via UE) through the network. The networks can be public or private and include services such as the Internet, enterprise networks, cloud services, or any other network where the user data might be sent or received. The DN (320) provides external resources, including services (e.g., web browsing, cloud applications, loT services, or any form of internet access) that the UEcan access. The DN (320) is connected to the network via the UPF (318), which routes data between the UE (104) and the DN (320). The UPF (318) facilitates the connection between the UE (104) and the DN (320), enabling user data flow. The DN (320) can vary based on the use case (public or private), and its integration with the network enables high-performance, secure, and efficient communication for users accessing external services.

[0132] In an aspect, the Session Management Function (SMF) (322) is a network element responsible for managing user sessions. The SMF (322) ensures that the UE has the appropriate resources, connectivity, and quality of service (QoS) to maintain data sessions while connecting to the network. The SMF (322) interacts with other network elements / functions to manage session setup, modification, and release, as well as ensure proper routing of data between the UPF (318) and the UE (104).

[0133] In an aspect, the Network Exposure Function (NEF) (334) is a network element that provides a secure interface for exposing network capabilities and services to external entities (e.g., third-party applications or service providers). The NEF (334) acts as a gateway to allow authorized applications to access network data and capabilities while ensuring the security and privacy of the network and the users.

[0134] In an aspect, the Policy Control Function (PCF) (324) is a network element that manages policy and charging control. The PCF (324) ensures the appropriate Quality of Service (QoS) and traffic management for users and services based on dynamic policies set by the network operator. The PCF (324) is responsible for providing real-time decisions on how network resources should be allocated, how traffic should be prioritized, and how services should be delivered based on various criteria like application type, user preferences, or network conditions.

[0135] In an aspect, the Network Slice Selection Function (NSSF) (326) is a network element responsible for selecting the appropriate network slice for a user or aservice based on their specific requirements. A network slice is a logically isolated, customized virtual network tailored to meet specific service needs, such as low-latency communications, high bandwidth, or massive connectivity for loT devices. The NSSF (326) ensures that each user or service is connected to the correct network slice based on a plurality of factors, such as application requirements, user preferences, and network capabilities.

[0136] In an aspect, the Short Message Service Function (SMSF) (328) is a network element responsible for managing and delivering Short Message Service (SMS) in the 5G environment. The SMSF (328) handles SMS operations to ensure the correct delivery of text messages between users, applications, and networks. The SMSF (328) provides interoperability for SMS across different generations of telecommunication network technologies. The SMSF (328) is responsible for SMS routing, interworking with legacy Short Message Service Centers (SMSCs), session management, and SMS storage when the recipient is unavailable. The SMSF (328) ensures SMS continuity, even for roaming users, and supports SMS over IP, providing a seamless messaging experience in the network.

[0137] In an aspect, the Network Data Analytics Function (NWDAF) (330) is a network element responsible for collecting, analyzing, and providing insights based on network data to optimize network operations, improve performance, and enable data-driven decision-making. The NWDAF (330) performs network management and enhances the network's overall efficiency by supporting key functions (e.g., traffic management, quality of service (QoS), network slice optimization, and predictive maintenance).

[0138] In an aspect, the Charging Function - Policy Control (CHF-PC) (332) is a network element used in charging and policy control. The CHF-PC (332) is responsible for enforcing charging rules and ensuring that network services, such as data usage, voice, and SMS, are billed correctly while also applying policy rules thatgovern how network resources are allocated. The CHF is responsible for handling both the charging and policy control aspects of the network. The CHF-PC (332) ensures that the PCF and the CHF work together to apply consistent and synchronized rules for both quality of service (QoS) and billing.

[0139] In an aspect, the Signaling Transfer Point (STP) (340) is a network element in a Signaling System 7 (SS7) and the network responsible for routing signaling messages between different network elements. The STP (340) is an intermediary that efficiently routes signaling messages to the correct destination based on the signaling protocol and routing tables. The STP (340) forwards signaling messages between the network nodes (e.g., Mobile Switching Centers (MSCs), Home Location Registers (HLRs), the SMSCs and the GMSC. The STP (340) also routes signaling messages between the network elements / functions (e.g., the AMF (314), the SMF (322), and the UPF (318)). Further, the STP (340) is responsible for routing signaling messages, ensuring interoperability between different network elements, and performing functions (e.g., protocol conversion, security, and load balancing). The STP (340) routes signaling messages between the network functions and provides interoperability with legacy systems. By enabling efficient signaling, the STP (340) ensures seamless connectivity, mobility, and communication across different generations of mobile networks.

[0140] In an aspect, the Diameter Routing Agent (DRA) (338) is a network element that routes Diameter signaling messages between network functions, enabling authentication, authorization, accounting, charging, and policy control. Diameter is a protocol for authentication, authorization, accounting (AAA), and policy control in various network services. The DRA (338) ensures efficient message routing between the network functions and legacy systems, helping to maintain interoperability across network generations and supporting scalable, reliable network operations.

[0141] In an aspect, the Binding Support Function (BSF) (336) is a network element used in management of user bindings for mobility and session management. The BSF (336) ensures that the user equipment’s identity and context are properly handled as the UEs move across different network slices or access points in the network. The BSF (336) manages user bindings between a user’s identity and their current context regarding mobility, session management, and network access. The BSF (336) supports mobility management, session continuity, and seamless handovers between different network access points or slices by maintaining accurate and up-to- date binding information. TheBSF (336) ensures that the network functions (e.g., AMF (314), SMF (322), PCF (324), and UPF (318)) can efficiently handle the user’s session and provide consistent service quality as the user moves across the network.

[0142] An NL7 interface is an interface that enables the communication between the LMF (302) and other location-related functions for location services in an Internet protocol (IP) Multimedia Subsystem (IMS). In an aspect, the IMS is an architecture for delivering multimedia services over the IP networks. The IMS is a framework that enables the integration and delivery of services such as voice, video, messaging, and data through the Internet Protocol (IP).

[0143] An NL1 interface is an interface used between the LMF (302) and the AMF (314). The NL1 manages user mobility and authentication during the registration and handover processes. The NL1 interface allows the LMF (302) and the AMF (314) to handle location and mobility management and ensures a smooth user experience as the UE moves through the network and maintains its active session.

[0144] A NL2 interface is a communication interface between the GMLC (306) and the AMF (314) in the network to support the location-based services (LBS) to provide location information for emergency services, tracking, and other locationdependent services. The NL2 interface enables the exchange of information for session establishment, mobility management, QoS enforcement, and bearer resource control.The NL2 interface ensures a smooth user experience during mobility events, maintains consistent session quality, and efficiently manages the network’s resources as users move through different cells or network slices.

[0145] A NL6 interface is an interface between the GMLC (306) and the UDM (312). The NL6 interface communicates the location data when location-based services or subscriber-related information is required for delivering accurate location data. When a location request is made (e.g., an emergency call or a location-based service query), the GMLC (306) may need to authenticate and authorize the UE. The UDM (312) stores the subscriber’s profile and authentication data, including subscription information, credentials, and access rights. The NL6 interface allows the GMLC (306) to query the UDM (312) to validate the subscriber and ensure they are authorized for the requested location service.

[0146] A NL17 interface is an interface between the EIR (308) and the AMF (314) for managing the security and integrity of the UE attempting to access the network. When the UE tries to connect to the network, the AMF (314) communicates with the EIR (308) via the NL17 interface to verify the IMEI of the UE. The NL17 interface helps in maintaining network security by facilitating communication between the EIR (308) and the AMF (314) to authenticate devices, ensuring that only authorized and non-compromised UEs can access the network. This helps prevent fraud and unauthorized access while ensuring the integrity of the network.

[0147] A N12 interface is an interface between the AUSF (310) and the AMF (314) used for the authentication and security procedures during the initial registration and mobility management of the UE in the network. In an aspect, the AMF (314) sends an authentication request to the AUSF (310) via the N12 interface, which then communicates with the UDM (312) to verify the credentials (e.g., IMSI) and check if the UE is authorized to access the network. The N12 interface ensures that only authorized users or UEs are granted access to the network and supports the exchangeof vital authentication information during the UE’s registration or mobility management process. The N12 interface helps ensure a robust and secure network by coordinating the authentication procedure and providing a secure mechanism for validating user identity.

[0148] A N13 interface is an interface between the AUSF (310) and the UDM (312) used for the authentication process of the UE and ensures that the UE trying to connect to the network is legitimate and authorized to access services. The N13 interface supports the AUSF (310) in retrieving authentication data necessary for verifying the identity of the UE from the UDM (312) to ensure secure and authenticated access to the network. By facilitating the exchange of sensitive subscriber information and authentication vectors, the N13 interface helps to maintain the overall security and integrity of the network.

[0149] A N8 interface is an interface between the UDM (312) and the AMF (314) responsible for supporting network procedures (e.g., subscriber management, authentication, and service access). The N8 interface facilitates communication between the AMF (314) and the UDM (312) to retrieve or update the subscriber's profile during registration, authentication, or mobility management procedures.

[0150] An N14 interface is an interface used by the AMF (314) for coordinating session management and mobility management, enabling these two core network functions to work together in supporting the user's session, particularly during handovers or mobility events. The N14 interface facilitates the exchange of information required for session management, mobility management, and bearer resource management. It ensures that user sessions are maintained without interruption, even as the user moves across different areas of the network. Additionally, the N14 interface supports the enforcement of QoS and policy rules, ensuring seamless session continuity and high-quality service delivery.

[0151] An N1 interface is an interface between the AMF (314) and the UE (104) responsible for handling registration, authentication, mobility management, and session management functions between the UE (104) and the network (106). Through the N1 interface, the AMF (314) ensures the UE's connectivity, handles user session continuity, and enables efficient mobility management as the UE (104) moves within the network.

[0152] A N2 interface is an interface between the AMF (314) and the RAN gNB (gNodeB) (110) used for supporting mobility management, session management, and radio resource control between the AMF (314) and the RAN gNB (110), ensuring seamless connectivity and user experience as the UE moves across the network.

[0153] A N3 interface is an interface between the RAN gNB (gNodeB) (110) and the UPF (318) responsible for handling the data traffic (user plane traffic) between the UE and the network. The N3 interface facilitates the transfer of user data, ensuring that data flows efficiently between the radio access network (RAN) and the network. The N3 interface supports the routing and forwarding of user traffic, bearer resource management, and the enforcement of QoS policies. The N3 interface ensures that user data is delivered efficiently and with high service quality from the UE to its destination, whether within the network or externally. By handling data tunneling and forwarding, the N3 interface helps maintain a continuous and high-quality user experience during data transmission.

[0154] A N6 interface is an interface between the UPF (318) and the DN (320) that facilitates the transfer of user data between the Network and external data networks (e.g., the internet, private servers, or application networks). In an operative aspect, the UPF receives user data from the gNB (via the N3 interface) and forwards the received user data through the N6 interface to the DN (320).

[0155] A N4 interface is an interface between the SMF (322) and the UPF (318) for managing user sessions and handling user plane data for optimal user experience in traffic routing, session management, and quality of service (QoS) enforcement. The N4 interface allows the SMF (322) to control the data path and session parameters for users, ensuring that traffic flows efficiently through the network and that user sessions are maintained with the appropriate resources.

[0156] A N16 interface is an interface used by the SMF (322) for service data flow (SDF) management. The N16 interface is responsible for the interaction between the SMF (322) and the application functions (AFs), such as service platforms or applications that require session management and data flow control. The N16 interface enables the SMF (322) to enforce application-specific policies, manage QoS requirements, and dynamically adjust session parameters based on the service or application the user is accessing. By allowing the AF to provide policy information, the N16 interface ensures that user sessions are optimized for the specific needs of each service, leading to a more tailored and efficient user experience.

[0157] A Ni l interface is an interface between the AMF (314) and the SMF (322) for managing session establishment, modification, and termination, as well as handling mobility management and user authentication across the network. The Ni l interface allows the AMF (314) to manage the UE’s mobility, ensure correct bearer allocation, and communicate with the SMF (322) for session-related activities (e.g., session establishment, modification, and release). The Ni l interface ensures that user sessions are properly managed and that QoS policies are enforced throughout the session, enhancing the overall user experience in the network.

[0158] A N10 interface is an interface between the UDM (312) and the SMF (322) for managing subscription data and session information related to user services, such as retrieving subscriber profiles and policy information and ensuring that the session is established and maintained according to the subscriber's preferences andnetwork policies. The N10 interface facilitates the exchange of subscriber profile information between the SMF (322) and the UDM (312). The SMF (322) retrieves user profile data from the UDM (312), such as the subscriber’s service preferences, QoS requirements, or subscription details, to properly manage sessions and bearers.

[0159] A N15 interface is an interface between the PCF (324) and the AMF (314) responsible for enabling the AMF (314) to interact with the PCF (324) for policy control and decision-making related to mobility management and session management for the UE. The N15 interface helps the AMF (314), and the PCF (324) to enforce the QoS policies and ensure that the appropriate policies are applied to the users' sessions based on their behavior, subscription, and network conditions.

[0160] A N22 interface is an interface between the AMF (314) and the NSSF (326) that enables the AMF (314) to interact with the NSSF (326) to obtain information about network slice selection for a particular UE or session. This interaction ensures that the appropriate network slice is selected for the UE based on subscription, service requirements, and network conditions.

[0161] A N21 interface is an interface between the UDM (312) and the SMSF (328) that enables the SMSF (328) to interact with the UDM (312) to manage Short Message Service (SMS) functionality, particularly for storing, retrieving, and processing subscriber-related data and settings related to SMS services. The N21 interface enables the SMSF (328) to access and manage subscriber information related to SMS services. Through the N21 interface, the SMSF (328) can retrieve the necessary subscriber profiles, manage SMS service activation and deactivation, handle message routing, and ensure that SMS services are properly authorized and authenticated. The N21 interface ensures that SMS functionality is properly aligned with the network policies and subscriber preferences, enabling effective SMS message handling for users in the network.

[0162] A N20 interface is an interface between the SMSF (328) and the AMF (314) for effective management of SMS services. The N20 interface facilitates the exchange of information related to SMS delivery, mobility management, and session management. Through the N20 interface, the AMF (314) and SMSF (328) ensure that SMS messages are delivered correctly, even when the UE is moving between cells or undergoing other mobility events. The N20 interface helps maintain the integrity of SMS services by ensuring that mobility context, delivery status, and subscriber preferences are communicated between the two functions to provide seamless SMS service.

[0163] A N23 interface is an interface between the PCF (324) and the NWDAF (330), enabling the PCF (324) to incorporate real-time network data and analytics into its policy control decisions. The PCF (324) is responsible for enforcing policy decisions within the network, such as Quality of Service (QoS), service prioritization, and charging rules. The NWDAF (330) gathers and analyzes network data to provide insights on network conditions, user behavior, and performance. The N23 interface allows the PCF (324) to request and receive network data from the NWDAF (330) to inform its policy decisions. By leveraging insights provided by the NWDAF (330), the PCF (324) can dynamically adjust policies to optimize network performance, service quality, and resource utilization. The N23 interface helps ensure that policies are context-aware and responsive to changing network conditions, enhancing overall user experience and network efficiency.

[0164] A N34 interface is an interface between the NWDAF (330) and the NSSF (326) that facilitates the exchange of data related to network slicing and network performance analytics. By providing detailed network analytics (including slice performance, traffic forecasting, and load balancing data), the NWDAF (330) ensures that the NSSF (326) can select an appropriate network slice for each UE or networkservice. This improves network efficiency, enhances quality of service (QoS), and helps balance network resources to meet varying demands in the network.

[0165] A N40 interface is an interface between the SMF (322) and the CHF- PC (332) for enabling accurate charging and policy enforcement in the network. The N40 allows for the real-time exchange of charging data, policy control decisions, and service usage reports. By using the N40 interface, the SMF (322) and CHF-PC (332) work together to ensure that users are billed appropriately for their network usage and that network policies are adhered to during the lifecycle of a user session.

[0166] A N28 interface is an interface between the PCF (324) and the CHF-PC (332) that facilitates the exchange of charging and policy control information, ensuring that policy decisions made by the PCF (324) are aligned with charging rules managed by the CHF-PC (332). The N28 interface ensures that quality of service (QoS), traffic management, and charging policies are enforced consistently across the network. By enabling the PCF (324) and CHF-PC (332) to exchange policy decisions and charging rules, the N28 interface ensures that service usage is accurately billed in real time, according to the policies applied by the PCF (324). The N28 interface facilitates the exchange of charging data and real-time updates, ensures that users are billed correctly for the services consumed, and that quality of service (QoS) levels is maintained across the network.

[0167] A N52 interface is an interface between the UDM (312) and the NEF (334) that enables the UDM (312) to expose relevant subscriber data and authentication information to other network functions or external applications via the NEF (334). The NEF (334) acts as an intermediary allowing controlled and secure data access from network functions like the UDM (312). The N52 interface is used for providing subscriber-related data (e.g., authentication details, subscription information, and other user-related data) to third-party services or applications that require such data forcertain functionalities (e.g., network slicing, quality of service enforcement, or policy decisions).

[0168] A N29 interface is an interface between the SMF (322) and the NEF (334) for providing session-related information and policy decisions from the SMF (322) to external network entities and third-party applications via the NEF (334). The N29 interface facilitates the exchange of relevant data about user sessions, service usage, and network conditions in a controlled and secure manner. Further, the N29 interface allows third-party applications or network services to interact with network functions in a way that aligns with operator policies and ensures privacy and security.

[0169] An interface between the NEF (334) and the BSF (336) used for binding and authentication purposes, facilitating the interaction between the NEF (334) and BSF (336) to expose relevant binding and user context information to third-party services or applications securely. The interface between the NEF (334) and the BSF (336) acts as an intermediary between the NEF (334) and the BSF (336) such that the NEF (334) exposes the binding data from the BSF (336) to authorized external services while ensuring security, privacy, and policy enforcement. The interface between the NEF (334) and the BSF (336) is useful for location-based services, mobility management, authentication, authorization of external applications, and network slice management.

[0170] A N51 interface is an interface between the AMF (314) and the NEF (334) that enables the AMF (314) to expose mobility management and authentication data to external applications or services via the NEF (334). The N51 interface supports location-based services, authentication services, network slice management, and policy enforcement. By facilitating the secure and controlled exposure of mobility data, authentication context, and policy information, the N51 interface enables third-party applications to interact with the network. Further, the N51 ensures that sensitive network data is shared only with authorized entities and is used in compliance withprivacy and security policies, helping to deliver a wide range of services while maintaining network integrity and user privacy.

[0171] A SGd interface is an interface between the SMSF (328) and the DRA (338) that supports SMS routing, message delivery, and policy enforcement within the network. By using Diameter signaling, the SGd interface allows the SMSF (328) to interact with the DRA (338) for functions (e.g., user profile retrieval, SMS routing decisions, charging, and accounting). The SGd interface enables the network to deliver SMS services efficiently and securely, ensuring correct message routing, billing, and policy enforcement. Further, the SGd interface manages network resources and ensures that SMS traffic is processed according to operator-defined rules and subscriber preferences.

[0172] A signaling transport (SIGTRAN) interface / protocol is an interface between the SMSF (328) and the STP (340) for facilitating signaling related to the Short Message Service (SMS) within the network and for routing and transferring SMS-related signaling messages across different parts of the network and the SS7 networks. The SIGTRAN facilitates the routing of SMS messages, user profile handling, delivery confirmation, and charging through Diameter and SS7-based signaling adapted for IP transport.

[0173] A Gy, Sy interface is a signaling interface used between the CHF-PC (332) and the DRA (338) for managing charging and policy control operations related to user sessions and data flows. The Gy, Sy interface ensures that Diameter signaling for charging, policy enforcement, and QoS is efficiently routed between the CHF-PC (332) and other network components (e.g., policy and Charging Rules Function (PCRF), home subscriber server (HSS), and billing systems. By handling the interactions between the CHF-PC (332) and the DRA (338), the Gy, Sy interface enables the effective application of charging rules and policy enforcement in the network. In an aspect, the PCRF is a network element that manages policy control andcharging rules and ensures that the correct policies for service quality, bandwidth allocation, and charging are applied to user sessions and data traffic. In an aspect, the HSS is a central database in telecommunications networks, storing subscriber profiles and authentication information. The HSS manages and stores key data about subscribers, such as their service subscriptions, preferences, and authentication credentials, and provides this data to other network elements (e.g., the PCRF and IMS).

[0174] In an aspect, a Sd interface is an interface between the PCF (324) and the DRA (338) responsible for ensuring that policy decisions made by the PCF are properly enforced and charging information is accurately routed and exchanged between various network components (e.g., PCRF, CHF (Charging Function), and billing systems).

[0175] In an aspect, a primary Rx interface is an interface between the PCF (324) and the BSF (336) for managing policy control and binding information related to user data sessions and mobility management. The primary Rx interface enables the PCF (324) to access and utilize binding information provided by the BSF (336) for efficient policy enforcement. Further, the primary Rx interface supports seamless session continuity, ensures consistent QoS, and enables effective mobility management. The PCF (324) uses the binding data to enforce policies dynamically based on a user's location, network conditions, and session state.

[0176] In an aspect, a secondary Rx interface is an interface between the DRA (338) and the BSF (336) for the Diameter-based signaling in the network. The DRA (338) facilitates the routing of Diameter messages related to binding information stored and managed by the BSF (336). The diameter messages ensure policy enforcement, session continuity, and mobility management in the network. The secondary Rx interface between the DRA (338) and the BSF (336) ensures that charging rules and quality of service (QoS) policies are applied consistently and accurately to usersessions by enabling the necessary information exchange between the DRA (338) and BSF (336).

[0177] In an aspect, the Le interface is an interface between the GMLC (306) and the LCS Client (304) used to exchange location-related information. The GMLC (306) handles location-based services (LBS), while the LCS Client (304) typically refers to the application or entity that requests location services for the users. The Le interface between the GMLC (306) and the LCS Client (304) allows the LCS Client (304) to request location data from the GMLC (306), which processes the request and returns the relevant location information. The Le interface supports various service types, privacy controls, and location accuracy requirements, ensuring that location data is provided securely and in accordance with the user’s permissions.

[0178] Although FIG. 3 shows exemplary components of the network architecture (300), in other embodiments, the network architecture (300) may include fewer components, different components, differently arranged components, or additional functional components than depicted in FIG. 3. Additionally, or alternatively, one or more components of the network architecture (300) may perform functions described as being performed by one or more other components of the network architecture (300).

[0179] FIG. 4 illustrates an exemplary flow diagram (400) for positioning of the UE (104) in the network (106), in accordance with an embodiment of the present disclosure.

[0180] As shown in FIG. 4, the AMF (314) may send a location determination request to determine the UE's location towards the LMF (302). The location determination request comprises a new radio (NR) Cell Global Identity (NR-CGI) value of the RAN.

[0181] In an aspect, the NR Cell Global Identity (NR-CGI) is a unique identifier assigned to a specific New Radio (NR) cell in the RAN. The NR-CGI varies based on the RAN vendor and the specific implementation of the network (106). It is given to each cell of the RAN (gNB). The NR-CGI comprises a public land mobile network (PLMN) identifier (ID) (PLMN-ID) and an NR Cell Identity (NCI). In an embodiment, the NCI is 36 bits.

[0182] In one aspect, the Public Land Mobile Network (PLMN) refers to a mobile telecommunications network that provides wireless communication services (e.g., voice, data, and messaging) to the UEs within a specific geographic area. The PLMN is operated by a mobile network operator (MNO) and may cover a country, region, or global area. Every PLMN is uniquely identified by its PLMN Identifier (PLMN-ID), which consists of a Mobile Country Code (MCC) and a Mobile Network Code (MNC). The MCC identifies the country, while the MNC identifies the specific operator within that country. The NR Cell Identity (NCI) is a globally unique identifier assigned to each NR cell within a specific PLMN. The NCI is used for mobility management, handover, and resource management within the RAN. The NCI enables network elements to identify and manage cells efficiently, ensuring continuity of services and optimizing user experience in the network.

[0183] Upon receiving the location request from the AMF (314), the LMF (302) extracts the NR-CGI value associated with the RAN. Based on the extracted NR- CGI from the location request, the LMF (302) determines a RAN vendor corresponding to the NR-CGI value. In an aspect, the plurality of RAN vendors may comprise a RAN vendor 1 , a RAN vendor 2, a RAN vendor 3. In an example, the LMF (302) determines the RAN vendor (e.g., RAN vendor 1) based on the extracted NR-CGI.

[0184] In an aspect, the RAN vendor is a company that designs, manufactures, and supplies equipment and solutions for the RAN in the telecommunication networks. The RAN vendors provide the necessary infrastructure for wireless communicationbetween the UEs and the network (which includes base stations, antennas, radio controllers, and other essential components).

[0185] Upon determining the RAN vendor, the LMF (302) sends a New Radio (NR) Positioning Protocol (NRPPa) request towards the determined RAN vendor. In an aspect, for each RAN vendor, the NRPPa algorithm is preconfigured. In an aspect, the NRPPa is responsible for managing signaling and data transmission between the UE (104) and the base station (Next Generation NodeB (gNB) in the network (106). The NRPPa encapsulates higher-layer data (e.g., Radio Resource Control (RRC)) messages into a format and delivers between the UE and the gNB. The NRPPa provides functionalities (e.g., data encapsulation, error handling, Quality of Service (QoS) management, and control-user plane separation) to ensure optimal performance in the network (106).

[0186] Upon receiving the NRPPa request from the LMF (302), the determinedRAN (110) provides one or more measurement parameters. The one or more measurement parameters may include, but not limited to, a received signal reference power (RSRP), a reference signal received quality (RSRQ), a timing advance (TA), and an angle of arrival (AoA). In an aspect, the RSRP measures a signal strength of a Reference Signal received by the UE from the base station (e.g., eNodeB in LTE or gNB in 5G). The RSRP is the power of the reference signals spread over full bandwidth and narrowband. In an aspect, the RSRQ is a measurement used to assess the quality of the reference signal from the base station. The RSRQ determines the quality of the wireless communication. In an aspect, the TA is used to synchronize the transmission of signals between the UE and the base station (e.g., eNodeB / gNB). The TA is a time required for signals to travel from the UE to the base station. The TA is essential for maintaining proper communication and avoiding interference with other devices. In an aspect, the AoA refers to a direction from which a signal arrives at a receiver (e.g., base station). The AoA is used for determining the location of the UE.

[0187] In an operative aspect, each of a plurality of RAN vendors sends one or more measurement parameter values. Upon receiving the NRPPa request from the LMF, the RAN Vendorl may send the RSRP and the TA, the RAN Vendor2 may send the RSRP, the TA and the AoA and the RAN vendor 3 may send RSRQ only. In an example, the LMF may send the NRPPa request to the RAN vendor 1. The RAN vendor 1 sends the RSRP and the TA to the LMF.

[0188] The determined RAN vendor (110) may send the measurement parameter value in a NRPPa response to the LMF (302). Upon receiving the measurement parameter values in the NRPPa response from the RAN vendor (110), the LMF (302) determines the location of the UE based on the received measurement values. The LMF (302) uses different algorithms for different RANs, which may be referred to as positioning algorithms. In an aspect, the positioning algorithm is a mathematical or computational method used to determine the location of a device (e.g., UE (i.e., a mobile phone)) based on signals received from different sources (e.g., GPS satellites, base stations, or local sensors). Positioning algorithms are widely used in location-based services (LBS), navigation, tracking, and indoor positioning systems (IPS).

[0189] The LMF (302) preconfigures the plurality of RAN vendors with a plurality of algorithms (e.g., Algo 1, Algo 2, Algo 3 and so on). In an example, the Algo 1 is a combination of all measurement parameters (e.g., RSRP + RSRQ + TA + AoA). The Algo 2 is a combination of RSRP + RSRQ + TA. The Algo 3 is a combination of RSRP + RSRQ. The Algo 4 is a combination of RSRP + TA. The Algo 5 is a combination of RSRQ + TA. The Algo 6 is only RSRP, the Algo 7 is only RSRQ, the Algo 8 is only TA, the Algo 9 is AoA. The Algo 10 is a combination of RSRP + RSRQ + AoA. The Algo 11 is a combination of RSRP + AoA. The Algo 12 is a combination of RSRQ + AoA. The Algo 13 is a combination of RSRP + TA + AoA and so on.

[0190] In an example, the RAN vendor 1 is configured with the Algo 4 as the RAN Vendorl provides the RSRP and the TA. The RAN Vendor 2 is configured with the Algo 13 as the RAN vendor 2 provides the RSRP, the TA and the AoA. The RAN vendor 3 is configured with the Algo 7 as the RAN vendor 3 provides RSRQ only. The LMF (302) determines the location corresponding to the UE (i.e., target subscriber) based on the measurement parameters received from the determined RAN vendor and the algorithm pre-configured for the determined RAN vendor at the LMF (302). The LMF (302) may select one of the preconfigured algorithms to provide an accurate location of the UE (e.g., target subscriber). In an example, the LMF (302) receives the RSRP and the TA from the RAN vendor 1. Based on the received RSRP and the TA, the LMF (302) selects the algorithm (i.e., Algo 4 combination of RSRP + TA). Based on the selected algorithm (i.e., Algo 4), the LMF (302) determines the location of the UE. The LMF (302) may send the determined location to the AMF (314).

[0191] In an aspect, the LMF (302) is configured to select one algorithm either based on parameters received in the response (i.e., NRPPa) from the determined RAN vendor or based on the preconfigured algorithm for the determined RAN vendor or based on both criteria together.

[0192] In another aspect, the algorithm is selected based on priority. For example, if the parameters received in the response (i.e., NRPPa) from the determined RAN vendor have more priority than the preconfigured algorithm for the determined RAN vendor, then the algorithm selection for location determination is based on the parameters received in the response (i.e., NRPPa) from the determined RAN vendor.

[0193] In an aspect, if any measurement parameter value (i.e., reported value of RSRP, RSRQ, TA, AoA) is out of range or invalid, the LMF (302) may ignore out of range or invalid measurement parameter value and provide location based on remaining valid measurements. In an example, the LMF (302) receives the measurement parameter values for the RSRP and the TA for the RAN vendor 1. Thepreconfigured algorithm for the RAN vendor 1 is Algo 4 (i.e., RSRP+TA). The LMF (302) determines location based on the Algo 4. In another example, if the TA value is out of range or invalid, the LMF (302) determines the location based on the Algo 4 (i.e., ignoring the TA value in Algo 4) or by selecting the Algo 6 (i.e., RSRP only).

[0194] In an aspect, the LMF (302) compares the received measurement parameter value with a predefined range of the measurement parameter to determine whether the received measurement parameter value is valid or invalid or (within the predefined range or out of the predefined range). If the received measurement parameter value is less than the predefined range or within the predefined range, then the received measurement parameter is valid. If the received measurement parameter value is more than the predefined range or not within the predefined range, then the received measurement parameter value is invalid or out of range. In an example, the predefined range value of the RSRP ranges from -140 dBm to -44 dBm. If the received measurement value of RSRP is -85 dBm, then the measurement value of RSRP is valid. If the received measurement value of RSRP is -150 dBm, then the received measurement value of RSRP is invalid or out of range. In an aspect, the predefined ranges of the measurement parameters can be stored in the database.

[0195] In an aspect, the positioning algorithm may develop for a time division duplexing (TDD) and frequency division duplexing (FDD) cells. In an aspect, the TDD cell refers to a cell in the network that uses Time Division Duplexing (TDD) as its method of transmission. The TDD is a technique used in cellular networks, where the same frequency band is used for uplink (from UE to base station) and downlink (from base station to UE) transmission but occurs at different times. The TDD is achieved by dividing time into different slots, alternating between uplink and downlink transmission within the time slots. In an aspect, an FDD cell refers to a cell in the network that uses Frequency Division Duplexing (FDD) as its method of operation for managing uplink (transmission from the UE to the base station) and downlink(transmission from the base station to the UE) communications. In the FDD, the two communication directions (uplink and downlink) occur simultaneously but on different frequency bands.

[0196] In one aspect, the LMF (302) may determine a cell type based on an NR Absolute Radio Frequency Channel Number (ARFCN) value received in the NRRPa response from the RAN. The cell type is determined by identifying whether the cell operates in the FDD or TDD mode and a specific frequency band the cell belongs to.

[0197] In an aspect, the ARFCN is a unique identifier used in the networks to refer to specific radio frequency channels. The ARFCN manages frequencies within the broader spectrum allocated to the network. The ARFCNs are used for network planning, spectrum management, and ensuring interference-free communication between the base stations and the UEs. In an aspect, an ARFCN range may vary for different TDD / FDD bands. In FDD, the uplink and downlink frequencies are paired, with one frequency used for transmission from the mobile device (uplink) and another for transmission from the base station (downlink). Each FDD band has a specific range of the ARFCN values, and the ARFCN values correspond to the uplink and downlink frequency ranges. In an aspect, in TDD, the uplink and the downlink share the same frequency band, but the uplink and downlink are separated by time (i.e., uplink and downlink directions use the same frequency but at different times (time slots)). For TDD, the ARFCN refers to a single frequency used for both uplink and downlink communication.

[0198] FIG. 5 illustrates an exemplary flow diagram (500) of a method for determining UE location in the network (106), in accordance with an embodiment of the present disclosure.

[0199] At step (502), the method (500) includes receiving, by the first network function (302), a location determination request for at least one UE (104) from a secondnetwork function. In an aspect, the first network function (302) is a location management function (LMF). The second network function (314) is an access and mobility management function (AMF). In an aspect, the AMF triggers the location determination request (e.g., location determination request comprising NR-CGI) towards the LMF when the AMF requires the UE’s location for mobility, service or regulatory procedures.

[0200] At step (504), the method (500) includes extracting, by the first network function (302), at least one parameter from the received location determination request. In an aspect, the at least one extracted parameter comprises, but not limited to, a New Radio Cell Global Identity (NR-CGI), a tracking area identifier (ID), an International Mobile Subscriber Identity (IMSI), a temporary identifier, and a subscription identifier. In an aspect, the extraction of the parameters (e.g., NR-CGI, tracking area ID, IMSI, temporary identifier and subscription identifier) enables the first network function to uniquely identify the UE. Accordingly, the extracted parameters operate as inputs for subsequent stages of the UE location determination process.

[0201] At step (506), the method (500) includes determining, by the first network function (302), a network node (110) of the at least one UE (104) based on the at least one extracted parameter. The network node (110) is a radio access network (RAN) node (e.g., base station). In an aspect, the extracted parameters, such as the NR- CGI or the tracking area identifier, enable the first network function (302) to identify the specific RAN node serving the UE. Determining the serving RAN node allows the first network function (302) to establish the UE’s current point of attachment. This determination further facilitates initiation of an appropriate positioning procedure. The identified RAN node also operates as the source for acquiring measurement information required for UE location computation. The first network function (302) is thereby enabled to correlate the received request with network configuration data andsubscriber-related information. In another aspect, the extraction supports authorization, capability verification, and selection of a suitable positioning algorithm.

[0202] At step (508), the method (500) includes requesting, by the first network function (302), the determined network node (110) to provide one or more measurement parameters. The one or more received measurement parameters comprises a reference signal received power (RSRP), a reference signal received quality (RSRQ), a timing advance (TA) and an angle of arrival (AoA). The first network function (e.g., LMF (302)) may send the NRPPa request for measurement parameters to the RAN node (110). The measurement parameters enable the first network function (302) to assess the UE’s radio environment and derive positioning- related information. The requested parameters further support the selection and execution of an appropriate positioning algorithm. The measurement data obtained from the network node is subsequently utilized to compute or refine the UE’s estimated location.

[0203] At step (510), the method (500) includes receiving, by the first network function (302), a response comprising the one or more measurement parameters from the determined network node. The first network function (302) receives the response (e.g., NRPPa response) from the determined network node (110). The response comprises the measurement parameters, including the RSRP, the RSRQ, the TA, and the AoA.

[0204] At step (512), the method (500) includes selecting, by the first network function (302), at least one algorithm from a plurality of algorithms based on at least one of at least one condition and the one or more received measurement parameters. In an aspect, the at least one condition comprises one or more of a priority condition of each of the one or more received measurement parameters, a range condition of each of the one or more received measurement parameters, and a pre-configured algorithm condition of the determined network node (110). In an aspect, the pre-configuredalgorithm condition comprises preconfiguring an algorithm from the plurality of algorithms for each network node based on the one or more received measurement parameters corresponding to each network node. In an aspect, the range condition comprises detecting whether at least one measurement parameter of the one or more received measurement parameters is out of range or invalid based on a predefined range. Upon detecting that the at least one measurement parameter of the one or more received measurement parameters is out of range or invalid based on the predefined range, the first network function, the location of the at least one UE based on one or more remaining valid measurement parameters. The priority condition comprises selecting the at least one algorithm based on a priority of each of the one or more received measurement parameters and a preconfigured algorithm of the determined network node.

[0205] In an aspect, the selection process evaluates multiple conditions, including the priority condition that defines the relative importance of each measurement parameter, the range condition that verifies whether each parameter lies within an acceptable operational threshold, and the pre-configured algorithm condition associated with the determined network node. The first network function (302) applies one of the conditions to identify the most suitable algorithm for the current positioning scenario. In another aspect, the selection may prioritize parameters such as RSRP, TA, or AoA based on their availability and validity. The pre-configured condition ensures that algorithms are automatically preferred when applicable. The selection outcome determines the algorithm that will be executed for determining the UE’s location.

[0206] At step (514), the method (500) includes determining (514), by the first network function (302), the location of the at least one UE (104) based on the at least one selected algorithm. In an aspect, the first network function (302) is configured to determine the location of the at least one UE (104) based on the algorithm selected during the algorithm-selection process. In an aspect, the selected algorithm utilizes thevalidated measurement parameters, such as RSRP, RSRQ, TA, or AoA, to determine the UE’s position. The first network function (302) processes the parameters in accordance with the mathematical or procedural steps defined by the chosen algorithm. The resulting computation yields an estimated geographical location or position estimate of the UE (104). This determination forms the final step of the positioning workflow initiated in response to the location determination request.

[0207] In an aspect, the first network function (302) is configured to perform an integrity check on the determined location of the at least one UE (104). The integrity check is performed based on at least one of, but not limited to, a mutli-round trip time (multi-RTT), a downlink angle of departure (DL-AoD), a DL-time difference of arrival (DL-TDoA), a uplink-TDoA (UL-TDoA), and a UL-AoA. In an aspect, the first network function (302) is configured to perform an integrity check on the determined location of the at least one UE (104) to ensure that the determined location of the UE is reliable and within acceptable accuracy thresholds. In an aspect, the integrity check is carried out using one or more additional measurement parameters, such as multiround trip time (multi-RTT), downlink angle of departure (DL-AoD), downlink time difference of arrival (DL-TDoA), uplink TDoA (UL-TDoA), and uplink angle of arrival (UL-AoA), that may be independently obtained from the determined RAN node. The parameters serve as verification indicators that allow the first network function to confirm whether the initially determined location is consistent with the UE’s observed radio characteristics. For example, the multi-RTT measurement may be used to validate distance-related estimates, while DL-AoD and UL-AoA measurements may be used to verify the directionality of the UE’s position relative to the RAN node. Similarly, DL-TDoA and UL-TDoA provide timing-based consistency checks across multiple signal paths. Based on these checks, the first network function (302) may mark the location estimate as valid, adjust the estimate, or initiate a re-computation if inconsistencies or anomalies are detected.

[0208] After performing the integrity check, the first network function (i.e., LMF (302)) sends the determined location of the UE (104) to the second network function (i.e., AMF (314)).

[0209] FIG. 6 illustrates an exemplary block diagram of a computer system (600) in which or with which embodiments of the present disclosure may be implemented.

[0210] As shown in FIG. 6, the computer system (600) may include an external storage device (610), a bus (620), a main memory (630), a read-only memory (640), a mass storage device (650), communication port(s) (660), and a processor (670). A person skilled in the art will appreciate that the computer system may include more than one processor and communication ports. The processor (670) may include various modules associated with embodiments of the present disclosure. The communication port(s) (660) may be any of an RS-232 port for use with a modem-based dialup connection, a 10 / 100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or other existing or future ports. The communication port(s) (660) may be chosen depending on a network, such a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system connects.

[0211] The main memory (630) may be random access memory (RAM), or any other dynamic storage device commonly known in the art. The read-only memory (640) may be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chips for storing static information e.g., start-up or Basic Input / Output System (BIOS) instructions for the processor (670). The mass storage device (650) may be any current or future mass storage solution, which can be used to store information and / or instructions. Exemplary mass storage device (650) includes, but is not limited to, Parallel Advanced Technology Attachment (PATA) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and / or Firewireinterfaces), one or more optical discs, Redundant Array of Independent Disks (RAID) storage, e.g., an array of disks.

[0212] The bus (620) communicatively couples the processor (670) with the other memory, storage, and communication blocks. The bus (620) may be, e.g., a Peripheral Component Interconnect (PCI) / PCI Extended (PCI-X) bus, Small Computer System Interface (SCSI), Universal Serial Bus (USB), or the like, for connecting expansion cards, drives, and other subsystems as well as other buses, such a front side bus (FSB), which connects the processor (670) to the computer system.

[0213] Optionally, operator and administrative interfaces, e.g., a display, keyboard, joystick, and a cursor control device, may also be coupled to the bus (620) to support direct operator interaction with the computer system. Other operator and administrative interfaces can be provided through network connections connected through the communication port(s) (660). Components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system limit the scope of the present disclosure.

[0214] In an exemplary embodiment, the present disclosure discloses a computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform a method for determining user equipment (UE) location in a network is disclosed. The method comprises receiving, by a first network function, a location determination request for at least one UE from a second network function. The method comprises extracting, by the first network function, at least one parameter from the received location determination request. The method comprises determining, by the first network function, a network node of the at least one UE based on the at least one extracted parameter. The method comprises requesting, by the first network function, the determined network node to provide one or more measurement parameters. The method comprises receiving, by the first network function, a responsecomprising the one or more measurement parameters from the determined network node. The method comprises selecting, by the first network function, at least one algorithm from a plurality of algorithms based on at least one of at least one condition and the one or more received measurement parameters. The method comprises determining, by the first network function, the location of the at least one UE based on the at least one selected algorithm.

[0215] The present disclosure provides significant technical enhancements by employing a positioning algorithm configured to determine the location of a UE based on measurements reported by RAN vendor nodes. Conventional methods, such as the UL-ECID technique, determine the UE’s location using information from multiple cells or radio access points. However, UL-ECID relies heavily on signal measurements from nearby cells, wherein such signals may be reflected, obstructed, or diffused. These propagation effects substantially degrade the accuracy of the position calculation, as the received signal may not accurately represent the true location of the device, thereby resulting in increased location errors.

[0216] In contrast, the present disclosure determines the UE location by discarding measurement values that fall outside an acceptable range and, based on the remaining valid measurement values received from the RAN vendor nodes, computes an accurate location of a target UE (or subscriber). The LMF selects an appropriate positioning algorithm based on parameters received from the RAN side and preconfigured settings at the LMF. The positioning algorithm is applicable for both TDD and FDD cells. Furthermore, a cell type is determined based on an NR-ARFCN value.

[0217] While the foregoing describes various embodiments of the invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof. The scope of the invention is determined by the claims that follow. The invention is not limited to the described embodiments, versions or examples, which are included to enable a person having ordinary skill in the art to makeand use the invention when combined with information and knowledge available to the person having ordinary skill in the art.

[0218] The method and system of the present disclosure may be implemented in a number of ways. For example, the methods and systems of the present disclosure may be implemented by software, hardware, firmware, or any combination of software, hardware, and firmware. The above-described order for the steps of the method is for illustration only, and the steps of the method of the present disclosure are not limited to the order specifically described above unless specifically stated otherwise. Further, in some embodiments, the present disclosure may also be embodied as programs recorded in a recording medium, the programs including machine-readable instructions for implementing the methods according to the present disclosure. Thus, the present disclosure also covers a recording medium storing a program for executing the method according to the present disclosure.

[0219] While considerable emphasis has been placed herein on the preferred embodiments, it will be appreciated that many embodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred embodiments of the disclosure will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter to be implemented merely as illustrative of the disclosure and not as limitation.ADVANTAGES OF THE PRESENT DISCLOSURE

[0220] The present disclosure provides a method and a system for determining location of a user equipment (UE) corresponding to a particular random-access network (RAN) vendor in a network.

[0221] The present disclosure employs a positioning algorithm to calculate the location of the UE based on the measurements (e.g., RSRP, RSRQ, TA, AoA) reported by the RAN vendor nodes.

[0222] The present disclosure calculates the location by ignoring the measurement values that are out of range and based on the remaining measurement values received from the RAN vendor nodes.

[0223] The present disclosure provides accurate location of a target UE (or subscriber) by selecting different algorithms based on the parameters received from the RAN end and pre-configurations at the LMF end.

[0224] The present disclosure employs the positioning algorithm for TDD andFDD cells. A cell type is determined based on the NR ARFCN value.

Claims

CLAIMS1. A method (500) for determining user equipment (UE) location in a network (106), the method (500) comprising: receiving (502), by a first network function (302), a location determination request for at least one UE (104) from a second network function (314); extracting (504), by the first network function (302), at least one parameter from the received location determination request; determining (506), by the first network function (302), a network node (110) of the at least one UE (104) based on the at least one extracted parameter; requesting (508), by the first network function (302), the determined network node (110) to provide one or more measurement parameters; receiving (510), by the first network function (302), a response comprising the one or more measurement parameters from the determined network node (110); selecting (512), by the first network function (302), at least one algorithm from a plurality of algorithms based on at least one of at least one condition and the one or more received measurement parameters; and determining (514), by the first network function (302), the location of the at least one UE (104) based on the at least one selected algorithm.

2. The method (500) as claimed in claim 1, wherein the first network function (302) is a location management function (LMF), wherein the second network function (314) is an access and mobility management function (AMF), and wherein the network node (110) is a radio access network (RAN) node.

3. The method (500) as claimed in claim 1, wherein the at least one extracted parameter comprises, but not limited to, a New Radio Cell Global Identity (NR-CGI), a tracking area identifier (ID), an International Mobile Subscriber Identity (IMSI), a temporary identifier, and a subscription identifier, and wherein the one or more received measurement parameters comprises a reference signal received power (RSRP), a reference signal received quality (RSRQ), a timing advance (TA) and an angle of arrival (AoA).

4. The method (500) as claimed in claim 1, wherein the at least one condition comprises one or more of: a priority condition of each of the one or more received measurement parameters, a range condition of each of the one or more received measurement parameters, and a pre-configured algorithm condition of the determined network node (110).

5. The method (500) as claimed in claim 4, wherein the pre-configured algorithm condition comprises: preconfiguring an algorithm from the plurality of algorithms for each network node based on the one or more received measurement parameters corresponding to each network node.

6. The method (500) as claimed in claim 4, wherein the range condition comprises: detecting whether at least one measurement parameter of the one or more received measurement parameters is out of range or invalid based on a predefined range; and upon detecting that the at least one measurement parameter of the one or more received measurement parameters is out of range or invalid based on the predefined range, determining, by the first network function (302), thelocation of the at least one UE (104) based on one or more remaining valid measurement parameters.

7. The method (500) as claimed in claim 4, wherein the priority condition comprises: selecting the at least one algorithm based on a priority of each of the one or more received measurement parameters and a preconfigured algorithm of the determined network node.

8. The method (500) as claimed in claim 1, wherein the first network function is configured to perform an integrity check on the determined location of the at least one UE, and wherein the integrity check is performed based on at least one of, but not limited to, a mutli-round trip time (multi-RTT), a downlink angle of departure (DL-AoD), a DL-time difference of arrival (DL-TDoA), a uplink- TDoA (UL-TDoA), and a UL-AoA.

9. A system (108) for determining user equipment (UE) location in a network (106), the system (108) comprising a first network function (302), the first network function (302) comprising: a processing engine (208); a memory (204) coupled to the processing engine (208), wherein the processing engine (208) comprising: a receiving unit (212) configured to receive a location determination request for at least one UE (104) from a second network function (314); an extraction unit (214) configured to extract at least one parameter from the received location determination request;a determining unit (216) configured to determine a network node of the at least one UE (104) based on the at least one extracted parameters; a requesting unit (218) configured to request the determined network node to provide one or more measurement parameters; the receiving unit (212) configured to receive a response comprising the one or more measurement parameters from the determined network node; a selecting unit (220) configured to select at least one algorithm from a plurality of algorithms based on at least one of at least one condition and the one or more received measurement parameters; and the determining unit (216) configured to determine the location of the at least one UE based on the at least one selected algorithm.

10. The system (108) as claimed in claim 9, wherein the first network function (302) is a location management function (LMF), wherein the second network function (314) is an access and mobility management function (AMF), and wherein the network node (110) is a radio access network (RAN) node.

11. The system (108) as claimed in claim 9, wherein the at least one extracted parameter comprises, but not limited to, a New Radio Cell Global Identity (NR-CGI), a tracking area identifier (ID), an International Mobile Subscriber Identity (IMSI), a temporary identifier, and a subscription identifier, and wherein the one or more received measurement parameters comprise a reference signal received power (RSRP), a reference signal received quality (RSRQ), a timing advance (TA) and an angle of arrival (AoA).

12. The system (108) as claimed in claim 9, wherein the at least one condition comprises one or more of: a priority condition of each of the one or morereceived measurement parameters, a range condition of each of the one or more received measurement parameters, and a pre-configured algorithm condition of the determined network node.

13. The system (108) as claimed in claim 12, wherein the pre-configured algorithm condition comprises: the determining unit (216) configured to preconfigure an algorithm from the plurality of algorithms for each network node based on the one or more received measurement parameters corresponding to each network node.

14. The system (108) as claimed in claim 12, wherein the range condition comprises: the determining unit (216) is configured to detect whether at least one measurement parameter of the one or more received measurement parameters is out of range or invalid based on a predefined range; and upon detecting that the at least one measurement parameter of the one or more received measurement parameter is out of range or invalid based on the predefined range, the determining unit (216) is configured to determine the location of the at least one UE (104) based on one or more remaining valid measurement parameters.

15. The system (108) as claimed in claim 12, wherein the priority condition comprises: the selecting unit (220) is configured to perform selection of the at least one algorithm based on a priority of the one or more received measurement parameters and a pre-configured algorithm of the determined network node.

16. The system (108) as claimed in claim 9, wherein an execution unit (222) is configured to perform an integrity check on the determined location of the atleast one UE, and wherein the integrity check is performed based on at least one of, but not limited to, a mutli-round trip time (multi-RTT), a downlink angle of departure (DL-AoD), a DL-time difference of arrival (DL-TDoA), a uplink- TDoA (UL-TDoA), and a UL-AoA.

17. A user equipment (UE) (104) communicatively coupled with a system (108), the coupling comprises steps of: receiving, by the system (108), a connection request from the UE (104); sending, by the system (108), an acknowledgment of the connection request to the UE (104); and transmitting a plurality of signals in response to the connection request, wherein the system (108) is configured to determine user equipment (UE) location in a network (106) as claimed in claim 9.

18. A computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to execute a method (500) for determining user equipment (UE) location in a network (106), the method (500) comprising: receiving (502), by a first network function (302), a location determination request for at least one UE (104) from a second network function (314); extracting (504), by the first network function (302), at least one parameter from the received location determination request; determining (506), by the first network function (302), a network node (110) of the at least one UE (104) based on the at least one extracted parameter;requesting (508), by the first network function (302), the determined network node (110) to provide one or more measurement parameters; receiving (510), by the first network function (302), a response comprising the one or more measurement parameters from the determined network node ( 110) ; selecting (512), by the first network function (302), at least one algorithm from a plurality of algorithms based on at least one of at least one condition and the one or more received measurement parameters; and determining (514), by the first network function (302), the location of the at least one UE (104) based on the at least one selected algorithm.

Images