Virtual positioning reference unit for positioning

Abstract

Aspects presented herein may enable a network entity (e.g., a location server, LMF, etc.) to generate and configure virtual anchors and / or virtual positioning reference units (VPRUs) for UEs for UE-based positioning. In one aspect, a network entity receives an indication to perform UE-based positioning for a UE. The network entity configures assistance data for the UE including a list of virtual anchors and a list of VPRUs for UE-based positioning. The network entity sends assistance data including a virtual anchor list and a VPRU list. The network entity may generate a virtual anchor list based on a location offset for each physical anchor in a set of physical anchors. The network entity may generate a VPRU list based on the at least one physical PRU.

Description

[0001] Cross-references to related applications

[0002] This application claims the benefit of U.S. Non-Provisional Patent Application Serial No. 18 / 180,782, entitled “VIRTUAL POSITIONING REFERENCE UNIT FOR POSITIONING”, filed on March 8, 2023, the entire contents of which are expressly incorporated herein by reference. Technical Field

[0003] This disclosure relates in general to communication systems, and more specifically to wireless communication including virtual positioning reference units. Background Technology

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that enable communication with multiple users by sharing available system resources. Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0005] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the city, country, region, and even global levels. An example telecommunications standard is 5G New Radio (NR). 5G NR is part of the Continuous Evolution of Mobile Broadband (CEM) program issued by the 3rd Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)), and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. Furthermore, these improvements can also be applied to other multiple access technologies and telecommunications standards that adopt them. Summary of the Invention

[0006] The following is a simplified overview of one or more aspects to provide a basic understanding of these aspects. This invention is not a comprehensive overview of all conceived aspects. It neither identifies key or essential elements of all aspects nor describes the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed descriptions that follow.

[0007] In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus receives an indication to perform a UE-based positioning for a user equipment (UE). The apparatus configures the UE with assistance data including a list of virtual anchors and a list of virtual positioning reference units (VPRUs) for the UE-based positioning. The apparatus transmits the assistance data including the list of virtual anchors and the list of VPRUs.

[0008] In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus transmits an indication to perform a UE-based positioning to a network entity. The apparatus receives assistance data including a list of virtual anchors and a list of VPRUs for the UE-based positioning from the network entity. The apparatus performs the UE-based positioning using at least one virtual anchor and at least one VPRU in the assistance data.

[0009] To the accomplishment of the foregoing and related aspects, one or more aspects can include the features recited in the following description and illustrated in the accompanying drawings. These features are indicative of the various ways in which one or more aspects can be implemented. However, various aspects can be embodied in many different forms and should not be construed as limited to the aspects set forth herein; rather, these aspects are provided so that this disclosure will be thorough and complete, and fully convey the scope of one or more aspects. Accordingly, the aspects are not intended to limit the scope of one or more aspects to the aspects described, which are merely examples. BRIEF DESCRIPTION OF DRAWINGS

[0010] Figure 1 is a diagram illustrating an example of a wireless communications system and an access network.

[0011] Figure 2A is a diagram illustrating an example of a first frame in accordance with various aspects of the disclosure.

[0012] Figure 2B is a diagram illustrating an example of a downlink (DL) channel within a subframe in accordance with various aspects of the disclosure.

[0013] Figure 2C is a diagram illustrating an example of a second frame in accordance with various aspects of the disclosure.

[0014] Figure 2D is a diagram illustrating an example of an uplink (UL) channel within a subframe in accordance with various aspects of the disclosure.

[0015] Figure 3 is a diagram illustrating an example of a base station and user equipment (UE) in an access network.

[0016] Figure 4 is a diagram illustrating an example of UE positioning based on reference signal measurements.

[0017] Figure 5 is a diagram illustrating an example of global navigation satellite system (GNSS) positioning in accordance with various aspects of the disclosure.

[0018] Figure 6 is a diagram illustrating an example of real-time kinematic (RTK) positioning according to various aspects of the present disclosure.

[0019] Figure 7 is a diagram illustrating an example positioning reference unit (PRU) according to various aspects of the present disclosure.

[0020] Figure 8 is a diagram illustrating an example of generating a virtual anchor or a real location of a physical anchor according to various aspects of the present disclosure.

[0021] Figure 9 is a diagram illustrating an example of creating a virtual PRU (VPRU) based on a set of physical PRUs according to various aspects of the present disclosure.

[0022] Figure 10 is a diagram illustrating an example of creating a VPRU based on a set of physical PRUs according to various aspects of the present disclosure.

[0023] Figure 11 is a diagram illustrating an example of generating a virtual PRU base station based on one or more physical PRU base stations according to various aspects of the present disclosure.

[0024] Figure 12 is a diagram illustrating an example of pre-assigning a location of a virtual reference station (VRS) according to various aspects of the present disclosure.

[0025] Figure 13 is a diagram illustrating an example of generating VRS measurements, assistance data, and / or correction data according to various aspects of the present disclosure.

[0026] Figure 14 is a communication flow illustrating an example of a network entity configuring a virtual anchor and a VPRU for a UE according to various aspects of the present disclosure.

[0027] Figure 15 is a communication flow illustrating an example of information that can be included in an assistance data request and assistance data that can enable a network entity to more efficiently configure a virtual anchor and / or a VPRU for a UE according to various aspects of the present disclosure.

[0028] Figure 16 is a flow diagram of a method of wireless communication.

[0029] Figure 17 is a flow diagram of a method of wireless communication.

[0030] Figure 18 is a diagram illustrating an example of a hardware implementation for an example apparatus and / or network entity.

[0031] Figure 19 is a flowchart of a method of wireless communication.

[0032] Figure 20 is a flowchart of a method of wireless communication.

[0033] Figure 21 is a diagram of an example illustrating an example network entity in hardware implementation. DETAILED DESCRIPTION

[0034] Aspects presented herein can enable a UE to achieve high accuracy positioning without knowing the locations of certain network nodes, such as positioning reference units (PRUs) and transmission reception points (TRPs). Aspects presented herein can enable a UE to perform positioning (e.g., UE-based positioning) using virtual PRUs (VPRUs) and / or virtual anchors, such that the PRUs / anchors can provide measurements, reference signals, assistance data, and / or correction data to the UE without disclosing their actual locations. In one aspect of the disclosure, a VPRU can indicate that there is no physical PRU (PPRU) located at the claimed location of the VPRU, where measurements, assistance data, and / or correction data can be virtually generated for the UE based on VPRU and / or PPRU information / measurement. Thus, the network can generate a VPRU or virtual reference station for a UE at any location. Measurements, assistance data, and / or correction data from a VPRU can be based on measurements of one or more physical PRUs and / or based on network resolution / tracking of various error source values.

[0035] By enabling UEs to perform positioning using virtual anchors (e.g., TRPs / satellites), a carrier operator (e.g., an operator of a location server, location management function (LMF), non-terrestrial network (NTN), etc.) can avoid releasing / providing accurate or true locations of its network nodes, such as anchor base stations and / or anchor satellites, thereby maintaining privacy and security of these network nodes. Additionally, for mobile anchors, such as mobile UEs associated with sidelink positioning or low earth orbit (LEO) satellites associated with NTNs, locations of these mobile anchors can be difficult to estimate and share with UEs in real-time. Thus, using virtual anchors can be more suitable and convenient for UEs to perform positioning. Aspects presented herein can enable ground truth locations of anchors to be protected with noise. Similarly, by enabling UEs to perform positioning using VPRUs, a carrier operator or PRU can also avoid releasing / providing accurate or true ground locations of PRUs, thereby maintaining privacy and security of PRUs. Locations of VPRUs can be pre-assigned (e.g., which can be more suitable for NTNs) or generated based on a location of a target UE (e.g., generated VPRU is close to the target UE). Aspects presented herein can enable UEs to achieve high accuracy positioning by enabling UEs to cancel out common anchor location errors (e.g., using correction data from PRUs). Furthermore, while physical PRUs can not be able to receive measurements and / or signals from the same set of anchors as a UE, using VPRUs can enable measurements from VPRUs to be associated with one or more common anchors of a UE. In other words, using virtual PRUs can guarantee measurements are from common anchors.

[0036] The detailed description set forth below, in connection with the appended drawings, is a description of various configurations and does not represent the only configurations in which the concepts described herein can be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form, in order to avoid obscuring such concepts.

[0037] Several aspects of telecommunication systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as “elements”). These elements can be implemented with electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the particular application and design constraints imposed on the overall system.

[0038] As an example, an element, or any portion of an element, or any combination of elements can be implemented as a “processing system” that includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on a chip (SoC), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure. One or more processors in the processing system can execute software. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination of

[0039] Accordingly, in one or more example aspects, implementations, and / or use cases, the described features can be implemented in hardware, software, or any combination thereof. If implemented in software, the functions can be stored on or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. Storage media can be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise a random-access memory (RAM), a read-only memory (ROM), an electrically erasable programmable ROM (EEPROM), compact disk ROM (CD-ROM), diskette, a hard disk drive, magnetic tape, other magnetic media, a flash memory or other solid-state memory, or any other medium that can be used to store desired computer executable code in the form of instructions or data structures and that can be accessed by a computer.

[0040] While aspects, implementations, and / or use cases described herein can be described in the context of 5G NR technology, aspects, implementations, and / or use cases described herein can be applicable to any suitable wireless communication system. For example, aspects, implementations, and / or use cases described herein can be applicable to Ultra-Mobility Technology (UMT), Ultra-Reliable Low-Latency Communication (URLLC), Vehicle-to-Everything (V2X), and / or other suitable technologies. Although aspects, implementations, and / or use cases described herein can be described in the context of specific examples, alternative or different aspects, implementations, and / or use cases can be produced. The aspects, implementations, and / or use cases described herein can be implemented in any of a variety of platforms, devices, systems, form factors, and packaging arrangements. For example, aspects, implementations, and / or use cases described herein can be realized in integrated chip implementations and other non-module-component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, artificial intelligence (AI)-enabled devices, etc.). Although some examples can or can not be specifically directed to use cases or applications, a wide range of applicability of described examples can result. Aspects, implementations, and / or use cases can range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregate, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more techniques described herein. In some practical settings, devices incorporating aspects and features described can also include additional components and features to enable and practice claimed and described aspects. For example, transmission and reception of wireless signals necessarily includes a variety of components, hardware, and software (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). Techniques described herein can be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregate or disaggregate components, end-user devices, etc. of varying sizes, shapes, and constitutions.

[0041] Deployments of communication systems, such as 5G NR systems, can be arranged in a variety of ways with various components or constituent parts. In a 5G NR system or network, a network node, network entity, mobility element of a network, radio access network (RAN) node, core network node, network element, or network equipment, such as a base station (BS) or one or more units (or one or more components) performing base station functionality (such as a Node B (NB), an evolved NB (eNB), a NR BS, a 5G NB, an access point (AP), a transmission reception point (TRP), or a cell, etc.) can be implemented in an aggregated or disaggregated architecture. For example, a BS, such as a Node B (NB), an evolved NB (eNB), a NR BS, a 5G NB, an access point (AP), a transmission reception point (TRP), or a cell, etc. can be implemented as an aggregated base station (also referred to as a standalone BS or a monolithic BS) or a disaggregated base station.

[0042] A disaggregated base station can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A disaggregated base station can be configured to utilize a protocol stack that is distributed, physically or logically, between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU can be implemented within a RAN node, and one or more DUs can be co-located with the CU, or alternatively, can be geographically or virtually distributed in one or more other RAN nodes. The DUs can be implemented to be in communication with one or more RUs. Each of the CU, DU, and RU can be implemented as virtual units, a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0043] Base station operations or network designs can take into account the disaggregated nature of base station functionality. For example, a disaggregated base station can be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (such as network configurations initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also referred to as a cloud radio access network (C-RAN)). Disaggregation can include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which can enable flexibility in network design. The various units of a disaggregated base station or disaggregated RAN architecture can be configured for wired or wireless communication with at least one other unit.

[0044] Figure 1 FIG. 1 is a diagram 100 illustrating an example of a wireless communications system and an access network. The illustrated wireless communications system includes a disaggregated base station architecture. The disaggregated base station architecture can include one or more CUs 110 that can communicate directly with a core network 120 via a backhaul link, or indirectly with the core network 120 through one or more disaggregated base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 125 via an E2 link, or a non-RT RIC 115 associated with a service management and orchestration (SMO) framework 105, or both. The CUs 110 can communicate with one or more DUs 130 via respective fronthaul links, such as an Fl interface. The DUs 130 can communicate with one or more RUs 140 via respective front-haul links. The RUs 140 can communicate with respective UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 can be simultaneously served by multiple RUs 140.

[0045] Each of the units (i.e., CU 110, DU 130, RU 140, and near-RT RIC 125, non-RT RIC 115, and SMO framework 105) can include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller providing instructions to the communication interfaces of these units, can be configured to communicate with one or more of the other units via the transmission medium. For example, the units can include a wired interface configured to receive signals from or transmit signals to one or more of the other units over a wired transmission medium. Additionally, the units can include a wireless interface that can include a receiver, a transmitter, or a transceiver (such as an RF transceiver) configured to receive and / or transmit signals to one or more of the other units over a wireless transmission medium.

[0046] In some aspects, CU 110 can host one or more higher layer control functions. Such control functions can include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by CU 110. CU 110 can be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some implementations, CU 110 can be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, CU-UP units can communicate bi-directionally with CU-CP units via an interface, such as an El interface. CU 110 can be implemented to communicate with DU 130 as needed for network control and signaling.

[0047] DU 130 can correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 140. In some aspects, DU 130 can host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.), depending at least in part on a function split, such as those defined by 3GPP. In some aspects, DU 130 can further host one or more low PHY layers. Each layer (or module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 110.

[0048] Lower-layer functionality can be implemented by one or more RU 140s. In some deployments, an RU140 controlled by a DU 130 may correspond to a logical node that hosts RF processing functions or low-PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, or both, based at least in part on functional decomposition (such as lower-layer functional decomposition). In such architectures, the RU 140 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some specific implementations, the real-time and non-real-time aspects of communication with the control plane and user plane of the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration enables the DU130 and CU 110 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0049] SMO framework 105 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, SMO framework 105 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, SMO framework 105 can be configured to interact with a cloud computing platform such as Open Cloud (O-Cloud) 190 to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface such as the O2 interface. Such virtualized network elements may include, but are not limited to, CU 110, DU 130, RU 140, and near-RT RIC 125. In some implementations, SMO framework 105 can communicate with the hardware aspects of the 4G RAN (such as Open eNB (O-eNB) 111) via the O1 interface. Additionally, in some implementations, SMO framework 105 can communicate directly with one or more RU 140s via the O1 interface. SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of SMO framework 105.

[0050] The non-RT RIC 115 can be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence (Al) / machine learning (ML) (Al / ML) workflows including model training and updating, or policy-based steering of applications / features in the near-RT RIC 125. The non-RT RIC 115 can be coupled to, or in communication with, the near-RT RIC 125, such as via an Al interface. The near-RT RIC 125 can be configured to include logical functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions via an interface, such as via an E2 interface, that connects one or more CUs 110, one or more DUs 130, or both, and an O-eNB with the near-RT RIC 125.

[0051] In some implementations, to generate Al / ML models to be deployed in the near-RT RIC 125, the non-RT RIC 115 can receive parameters or external enrichment information from an external server. Such information can be utilized by the near-RT RIC 125 and can be received at the SMO framework 105 or the non-RT RIC 115 from non-network data sources or from network functions. In some examples, the non-RT RIC 115 or the near-RT RIC 125 can be configured to tune RAN behavior or performance. For example, the non-RT RIC 115 can monitor long-term trends and patterns of performance and employ Al / ML models to perform corrective actions via the SMO framework 105, such as via reconfiguration of Ol, or via creation of RAN management policies, such as Al policies.

[0052] At least one of the CU 110, the DU 130, and the RU 140 can be referred to as a base station 102. Thus, the base station 102 can include one or more of the CU 110, the DU 130, and the RU 140 (each component is indicated with a dashed line to represent that each component can or can not be included in the base station 102). The base station 102 provides wireless access to the core network 120 for the UEs 104. A base station 102 can include a macro cell (high power cellular base station) and / or a small cell (low power cellular base station). Small cells include femto cells, pico cells, and micro cells. A network that includes both small cells and macro cells can be known as a heterogeneous network. A heterogeneous network can also include home evolved node Bs (eNBs) (HeNBs), which can provide service to a restricted group known as a closed subscriber group (CSG). The communication links 120 between the RUs 140 and the UEs 104 can include uplink (UL) (also known as reverse link) transmissions from a UE 104 to a RU 140 and / or downlink (DL) (also known as forward link) transmissions from a RU 140 to a UE 104. The communication links 120 can use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication links 120 can be through one or more carriers. The base station 102 / UE 104 can use spectrum up to Y MHz (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, etc.) bandwidth per carrier allocated in a carrier aggregation of up to a total of Yx MHz (x component carriers) in some cases. The carriers can or can not be adjacent to each other. The allocation of carriers can be asymmetric about the DL and UL (e.g., more or less carriers can be allocated for DL than for UL). The component carriers can include a primary component carrier and one or more secondary component carriers. A primary component carrier can be referred to as a primary cell (PCell) and a secondary component carrier can be referred to as a secondary cell (SCell).

[0053] Certain UEs 104 can communicate with each other using device-to-device (D2D) communication link 158. The D2D communication link 158 can use the DL / UL WWAN spectrum. The D2D communication link 158 can use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). D2D communication can be through a variety of wireless D2D communications systems, such as for example LTE, NR, or an Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard based

[0054] The wireless communications system can also include a Wi-Fi AP 150 in communication with UEs 104 (also referred to as Wi-Fi stations (STAs)) via communication links 154, e.g., in a 5 GHz unlicensed frequency spectrum or the like. When communicating in an unlicensed frequency spectrum, the UEs 104 / AP 150 can perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available.

[0055] The electromagnetic spectrum is often subdivided based on frequency / wavelength into various classes, bands, channels, etc. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz - 7. 125 GHz) and FR2 (24.25 GHz - 52.6 GHz). Despite a portion of FR1 being greater than 6 GHz, FR1 is often referred to (interchangeably) as a “Sub-6 GHz” band in various documents and articles. A similar naming convention occurs with regard to FR2, which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz - 300 GHz) which is designated as a “millimeter wave” band by the International Telecommunications Union (ITU).

[0056] The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified operating bands for these mid-band frequencies as frequency range designation FR3 (7. 125 GHz - 24.25 GHz). Bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and thus can effectively extend features of FR1 and / or FR2 to mid-band frequencies. Moreover, higher frequency bands are currently being explored to extend 5G NR operations beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR2-2 (52.6 GHz - 71 GHz), FR4 (71 GHz - 114.25 GHz), and FR5 (114.25 GHz - 300 GHz). Each of these higher bands fall within the EHF band.

[0057] With the above in mind, unless specifically stated otherwise, if the term “Sub-6 GHz” or the like is used herein, this can broadly represent frequencies that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. Further, unless specifically stated otherwise, if the term “millimeter wave” or the like is used herein, this can broadly represent frequencies that can include mid-band frequencies, can be within FR2, FR4, FR2-2, and / or FR5, or can be within the EHF band.

[0058] The base stations 102 and the UEs 104 can each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. The base stations 102 can transmit to UEs 104 in one or more transmit directions using beamforming. The UEs 104 can receive from the base stations 102 in one or more receive directions using beamforming. The UEs 104 can also transmit to the base stations 102 in one or more transmit directions using beamforming. The base stations 102 can receive from the UEs 104 in one or more receive directions using beamforming. The base station 102 / UE 104 can perform beam training to determine the best receive and transmit directions for each of the base station 102 / UE 104. The transmit and receive directions for the base station 102 can or can not be the same. The transmit and receive directions for the UE 104 can or can not be the same.

[0059] The base stations 102 can include and / or be referred to as gNBs, NodeBs, eNBs, access points, base transceiver stations, radio base stations, radio transceiver, transceiver functions, basic service sets (BSSs), extended service sets (ESSs), TRPs, network nodes, network entities, network equipment, or some other suitable terminology. The base stations 102 can be implemented as integrated access and backhaul (IAB) nodes, relay nodes, sidelink nodes, aggregated (monolithic) base stations with baseband units (BBUs) including CUs and DUs and RUs, or as disaggregated base stations including one or more of CUs, DUs, and / or RUs. Collections of base stations that can include disaggregated and / or aggregated base stations can be referred to as next generation (NG) RANs (NG-RANs).

[0060] The core network 120 can include an access and mobility management function (AMF) 161, a session management function (SMF) 162, a user plane function (UPF) 163, a unified data management (UDM) 164, one or more location servers 168, and other functional entities. The AMF 161 is the control node that processes the signaling between the UEs 104 and the core network 120. The AMF 161 supports registration management, connection management, mobility management, and other functions. The SMF 162 supports session management and other functions. The UPF 163 supports packet routing, packet forwarding, and other functions. The UDM 164 supports generation of authentication and key agreement (AKA) credentials, user identification handling, access authorization, and subscription management. The one or more location servers 168 are illustrated as including a gateway mobile location center (GMLC) 165 and a location management function (LMF) 166. However, generally speaking, the one or more location servers 168 can include one or more location / determination servers, which can include one or more of a GMLC 165, an LMF 166, a position determination entity (PDE), a serving mobile location center (SMLC), a mobile positioning center (MPC), and the like. The GMLC 165 and the LMF 166 support UE location services. The GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. The LMF 166 receives measurements and assistance information from the NG-RAN and the UE 104 via the AMF 161 to compute a location of the UE 104. The NG-RAN can utilize one or more positioning methods to determine the location of the UE 104. Positioning the UE 104 can involve signal measurements, position estimation, and optional velocity calculations based on these measurements. The signal measurements can be made by the UE 104 and / or the base stations 102 serving the UE 104. The measured signals can be based on one or more of a satellite positioning system (SPS) 170 (e.g., Global Navigation Satellite System (GNSS), Global Positioning System (GPS), Non-Terrestrial Network (NTN), or other satellite positioning / location system), LTE signals, Wireless Local Area Network (WLAN) signals, Bluetooth signals, Terrestrial Beacon System (TBS), sensor-based information (e.g., barometric pressure sensors, motion sensors), NR Enhanced Cell ID (NR E-CID) methods, NR signals (e.g., multi-round trip time (multi-RTT), DL angle of departure (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle of arrival (UL-AoA) positioning), and / or other systems / signals / sensors.

[0061] Examples of a UE 104 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, or any other similar functional device. Some of the UEs 104 can be referred to as IoT devices (e.g., a parking meter, gas pump, toaster, vehicle, heart monitor, etc.). The UE 104 can also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. In some scenarios, the term UE can also apply to one or more companion devices, such as in a device constellation arrangement. One or more of these devices can collectively or individually access a network and / or access the network separately.

[0062] Referring again to Figure 1 In certain aspects, the UE 104 can include a positioning component 198 that can be configured to transmit, to a network entity, an indication to perform UE-based positioning; receive, from the network entity, assistance data including a list of virtual anchors and a list of VPRUs for UE-based positioning; and perform UE-based positioning using at least one virtual anchor and at least one VPRU in the assistance data.

[0063] In certain aspects, the base station 102 can have a virtual anchor and reference station configuration component 199 that can be configured to receive an indication to perform UE-based positioning for a UE; configure assistance data for the UE including a list of virtual anchors and a list of virtual positioning reference units (VPRUs) for UE-based positioning; and transmit, to the UE, the assistance data including the list of virtual anchors and the list of VPRUs.

[0064] Figure 2A FIG. 200 is a diagram 200 illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B FIG. 230 is a diagram 230 illustrating an example of DL channels within a 5G NR subframe. Figure 2C FIG. 250 is a diagram 250 illustrating an example of a second subframe within a 5G NR frame structure. Figure 2Dis a diagram 280 illustrating an example of UL channels within the 5G NR subframe. The 5G NR frame structure can be frequency-division duplexed (FDD) where pairs of subcarriers are dedicated for DL or UL subframes, or can be time-division duplexed (TDD) where the same set of subcarriers is used for both DL and UL subframes. In the examples provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (with mostly DL), where D is DL, U is UL, and F is flexible that can be used between DL / UL, and subframe 3 is configured with slot format 1 (with all UL). While subframes 3, 4 are shown with slot formats 1, 28, respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0, 1 are all DL, UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols. UEs are configured with the slot format by a received slot format indicator (SFI) (dynamically through DL control information (DCI) or semi-statically / statically through radio resource control (RRC) signaling). Note that the following description applies also to 5G NR frame structures that are TDD. Figure 2A 、 Figure 2C In the examples provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (with mostly DL), where D is DL, U is UL, and F is flexible that can be used between DL / UL, and subframe 3 is configured with slot format 1 (with all UL). While subframes 3, 4 are shown with slot formats 1, 28, respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0, 1 are all DL, UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols. UEs are configured with the slot format by a received slot format indicator (SFI) (dynamically through DL control information (DCI) or semi-statically / statically through radio resource control (RRC) signaling). Note that the following description applies also to 5G NR frame structures that are TDD.

[0065] Figures 2A-2D The frame structure is illustrated, and aspects of the present disclosure can be applicable to other wireless communication technologies that can have different frame structures and / or different channels. One frame (10 ms) can be divided into 10 equally sized subframes (1 ms). Each subframe can include one or more time slots. A subframe can also include mini-slots, which can include 7, 4, or 2 symbols. Each slot can include 14 or 12 symbols depending on whether a cyclic prefix (CP) is normal or extended. For a normal CP, each slot can include 14 symbols, and for an extended CP, each slot can include 12 symbols. Symbols on the DL can be CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbols. Symbols on the UL can be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (for power limited scenarios; limited to single stream transmission). The number of slots within a subframe is dependent on the CP and the numerology. The numerology defines the subcarrier spacing (SCS) (see TABLE 1). The symbol length / duration can scale with 1 / SCS.

[0066]

[0067] Table 1: Numerology, SCS, and CP

[0068] For normal CP (14 symbols / slot), different numerologies μ0to 4allow for 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, numerology 2allows for 4 slots per subframe. Thus, for normal CP and numerology μ, there are 14 symbols / slot and 2 μ slots / subframe. The subcarrier spacing can equal 2 μ * 15 kHz, where μ is the numerology 0 to 4. Thus, the subcarrier spacing for numerology μ = 0 is 15 kHz, and the subcarrier spacing for numerology μ = 4 is 240 kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figures 2A-2D An example of normal CP with 14 symbols per slot and numerology μ = 2 with 4 slots per subframe is provided. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μβ. Within a frame collection, there can be one or more different bandwidth parts (BWPs) that are frequency division multiplexed (see Figure 2B ). Each BWP can have a particular numerology and CP (normal or extended).

[0069] A resource grid can be used to represent the frame structure. Each time slot includes a resource block (RB) (also referred to as a physical RB (PRB)) that extends 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0070] As illustrated in Figure 2A , some of the REs carry reference (pilot) signals (RS) for the UE. The RS can include demodulation RS (DM-RS) (indicated as R for one particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RS) for channel estimation at the UE. The RS can also include beam measurement RS (BRS), beam refinement RS (BRRS), and phase tracking RS (PT-RS).

[0071] Figure 2BExamples of various DL channels are illustrated. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within one BWP can be referred to as a control resource set (CORESET). A UE is configured to monitor PDCCH search space (e.g., common search space, UE-specific search space) for PDCCH candidates during PDCCH monitoring occasions on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs can be located at higher and / or lower frequencies of the channel bandwidth. A primary synchronization signal (PSS) can be within symbol 2 of particular subframes of a frame. The PSS is used by a UE 104 to determine subframe / symbol timing and physical layer identity. A secondary synchronization signal (SSS) can be within symbol 4 of particular subframes of a frame. The SSS is used by a UE to determine physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine a physical cell identifier (PCI). Based on the PCI, the UE can determine the locations of DM-RS. The physical broadcast channel (PBCH), which carries a master information block (MIB) that provides system bandwidth and scheduling information, can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also referred to as SS block (SSB)). The MIB provides a number of RBs in the system bandwidth and a system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information such as system information blocks (SIBs), and paging messages.

[0072] As Figure 2C illustrated, some of the REs carry DM-RS (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE can transmit DM-RS for channel estimation at the base station. The UE can transmit DM-RS for the physical uplink control channel (PUCCH) and the physical uplink shared channel (PUSCH). The UE can transmit DM-RS for PUSCH in the first one or two symbols of a slot. The UE can transmit DM-RS for PUCCH in different configurations depending on whether short or long PUCCH is transmitted and depending on the particular PUCCH format used. The UE can transmit a sounding reference signal (SRS). The SRS can be transmitted in the last symbol of a slot. The SRS can have a comb-structure, and a UE can transmit SRS on one of the combs. The SRS can be used by a base station for channel quality estimation to enable frequency-dependent scheduling for the UL.

[0073] Figure 2DExamples of various UL channels within a subframe of a frame are illustrated. The PUCCH can be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), and hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data, and can additionally be used to carry buffer status reports (BSRs), power headroom reports (PHRs), and / or UCI.

[0074] Figure 3 is a block diagram of the base station 310 and the UE 350 communicating in an access network. In the DL, Internet Protocol (IP) packets can be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIBs), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter radio access technology (RAT) mobility, and measurement configuration and reporting for UEs; PDCP layer functionality associated with header compression / decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the transfer of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0075] The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1, which includes a physical (PHY) layer, can include error detection on the transport channels, forward error correction (FEC) coding / decoding of the transport channels, interleaving, rate matching, mapping to physical channels, modulation / demodulation of physical channels, and MIMO antenna processing. The TX processor 316 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols can then be split into parallel streams. Each stream can then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams if multiple spatial streams are

[0076] At the UE 350, each receiver 354Rx receives a signal through its respective antenna 352. Each receiver 354Rx recovers information modulated onto an RF carrier and provides the information to the receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, they can be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 310. These soft decisions can be based on channel estimates computed by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the base station 310 on the physical channel. The data and control signals are then provided to the controller / processor 359, which implements layer 3 and layer 2 functionality.

[0077] The controller / processor 359 can be associated with a memory 360 that stores program codes and data. The memory 360 can be referred to as a computer-readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets from the EPC 190. The controller / processor 359 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.

[0078] Similar to the functionality described in connection with the DL transmission by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression / decompression, and security (ciphering, deciphering, integrity protection, integrity verification); RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0079] Channel estimates derived by the channel estimator 358 from a reference signal or feedback transmitted by the base station 310 can be used by the TX processor 368 to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the TX processor 368 can be provided to different antenna 352 via separate transmitters 354. Each transmitter 354 can modulate an RF carrier with a respective spatial stream for transmission.

[0080] The UL transmission is processed at the base station 310 in a manner similar to that described in connection with the receiver function at the UE 350. Each receiver 318 receives a signal through its respective antenna 320. Each receiver 318 recovers information modulated onto an RF carrier and provides the information to a RX processor 370.

[0081] The controller / processor 375 can be associated with a memory 376 that stores program codes and data. The memory 376 can be referred to as a computer-readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets from the EPC 190. The controller / processor 375 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.

[0082] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 can be configured to perform aspects related to positioning component 198 of FIG. 2. Figure 1 At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 can be configured to perform aspects related to positioning component 198 of FIG. 2.

[0083] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 can be configured to perform aspects related to positioning component 198 of FIG. 2. Figure 1 At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 can be configured to perform aspects related to positioning component 198 of FIG. 2.

[0084] Figure 4 FIG. 4 is a diagram 400 illustrating an example of reference signal measurement based UE positioning (which can also be referred to as “network-based positioning”) in accordance with various aspects of the present disclosure. A UE 404 can transmit an UL-SRS 412 at a time T SRS_TX and receive a DL positioning reference signal (PRS) (DL-PRS) 410 at a time T PRS_RX The TRP 406 can receive the UL-SRS 412 at a time T SRS_RX and transmit the DL-PRS 410 at a time T PRS_TX The UE 404 can receive the DL-PRS 410 before transmitting the UL-SRS 412, or can transmit the UL-SRS 412 before receiving the DL-PRS 410. In both cases, a positioning server (e.g., location server 168) or the UE 404 can determine an RTT 414 based on ||T SRS_RX – T PRS_TX | | T SRS_TX – T PRS_RX ||. Thus, multi-RTT positioning can utilize UE Rx-Tx time difference measurements (i.e., |T SRS_TX – T PRS_RX |) and DL-PRS reference signal received power (RSRP) (DL-PRS-RSRP) of downlink signals received from multiple TRPs 402, 406 and measured by the UE 404, and measured TRP Rx-Tx time difference measurements (i.e., |T SRS_RX – T PRS_TX|) and UL-SRS-RSRP. The UE 404 measures the UE Rx-Tx time difference measurements (and optionally the DL-PRS-RSRP of the received signals) using assistance data received from the location server, and the TRPs 402, 406 measure the gNB Rx-Tx time difference measurements (and optionally the UL-SRS-RSRP of the transmitted signals) using assistance data received from the location server. These measurements can be used at the location server or the UE 404 to determine RTTs, which are used to estimate the location of the UE 404. Other methods for determining RTTs are possible, such as for example using DL-TDOA and / or UL-TDOA measurements.

[0085] PRS can be defined for network-based positioning (e.g., NR positioning) to enable a UE to detect and measure more neighbor transmission and reception points (TRPs) with support for multiple configurations to enable various deployments (e.g., indoor, outdoor, sub-6, mmW, etc.). To support PRS beam operations, beam sweeping can also be configured for PRS. UL positioning reference signals can be based on sounding reference signals (SRS) with enhancements / adjustments for positioning purposes. In some examples, UL-PRS can be referred to as “SRS for positioning,” and new information elements (IEs) can be configured for SRS for positioning in RRC signaling.

[0086] DL PRS-RSRP can be defined as the linear average of the power contributions (in [W]) of resource elements carrying the antenna ports of DL PRS reference signals configured for RSRP measurement over the considered measurement frequency bandwidth. In some examples, for FR1, the reference point for DL PRS-RSRP can be the UE’s antenna connectors. For FR2, DL PRS-RSRP can be measured based on the combined signal from the antenna elements corresponding to a given receiver branch. For FR1 and FR2, if the UE uses receiver diversity, the reported DL PRS-RSRP value can not be lower than the corresponding DL PRS-RSRP of any of the individual receiver branches. Similarly, UL SRS-RSRP can be defined as the linear average of the power contributions (in [W]) of resource elements carrying sounding reference signals (SRS). UL SRS-RSRP can be measured over the configured resource elements in the configured measurement occasions over the considered measurement frequency bandwidth. In some examples, for FR1, the reference point for UL SRS-RSRP can be the base station’s (e.g., gNB’s) antenna connectors. For FR2, UL SRS-RSRP can be measured based on the combined signal from the antenna elements corresponding to a given receiver branch. For FR1 and FR2, if the base station uses receiver diversity, the reported UL SRS-RSRP value can not be lower than the corresponding UL SRS-RSRP of any of the individual receiver branches.

[0087] PRS-path RSRP (PRS-RSRPP) can be defined as the linear average of the power of the channel response at the i-th path delay of resource elements carrying DL PRS signals configured for measurement, where the DL PRS-RSRPP of the 1st path delay is the power contribution corresponding to the first detected path in time. In some examples, a PRS path phase measurement can refer to a phase associated with the i-th path of the channel derived using PRS resources.

[0088] DL-AoD positioning can utilize measured DL-PRS-RSRP of downlink signals received at the UE 404 from multiple TRPs 402, 406. The UE 404 measures the DL-PRS-RSRP of the received signals using assistance data received from a positioning server, and the resulting measurements are used along with the azimuth angle of departure (A-AoD), zenith angle of departure (Z-AoD), and other configuration information to position the UE 404 relative to the neighboring TRPs 402, 406.

[0089] DL-TDOA positioning can utilize the DL Reference Signal Time Difference (RSTD) (and optionally DL-PRS-RSRP) of downlink signals received at the UE 404 from multiple TRPs 402, 406. The UE 404 measures the DL RSTD (and optionally DL-PRS-RSRP) of the received signals using assistance data received from a positioning server, and the resulting measurements are used, along with other configuration information, to position the UE 404 relative to the neighboring TRPs 402, 406.

[0090] UL-TDOA positioning can utilize the UL Relative Time of Arrival (RTOA) (and optionally UL-SRS-RSRP) of uplink signals sent from the UE 404 at multiple TRPs 402, 406. The TRPs 402, 406 measure the UL-RTOA (and optionally UL-SRS-RSRP) of the received signals using assistance data received from a positioning server, and the resulting measurements are used, along with other configuration information, to estimate the location of the UE 404.

[0091] UL-AoA positioning can utilize the measured Azimuth of Arrival (A-AoA) and Zenith of Arrival (Z-AoA) of uplink signals sent from the UE 404 at multiple TRPs 402, 406. The TRPs 402, 406 measure the A-AoA and Z-AoA of the received signals using assistance data received from a positioning server, and the resulting measurements are used, along with other configuration information, to estimate the location of the UE 404. For the purposes of this disclosure, positioning operations in which the UE provides measurements to a base station / positioning entity / server for use in computing the UE’s location can be described as “UE-assisted,” “UE-assisted positioning,” and / or “UE-assisted position computation,” while positioning operations in which the UE measures and computes its own location can be described as “UE-based,” “UE-based positioning,” and / or “UE-based position computation.”

[0092] Additional positioning methods can be used to estimate the location of the UE 404, such as, for example, UE-side UL-AoD and / or DL-AoA. It should be noted that data / measurement from various techniques can be combined in various ways to increase accuracy, determine and / or enhance certainty, supplement / complement measurements, and / or replace / provide missing information. For example, some UE positioning mechanisms can be radio access technology (RAT)-dependent (e.g., the positioning of the UE is based on the RAT), such as downlink positioning (e.g., measurements of Observed Time Difference of Arrival (OTDOA)), uplink positioning (e.g., measurements of Uplink Time Difference of Arrival (UTDOA)), and / or combined DL and UL based positioning (e.g., measurements of RTT with respect to neighboring cells), etc. Some wireless communications systems can also support an Enhanced Cell ID (E-CID) positioning procedure based on Radio Resource Management (RRM) measurements. On the other hand, some UE positioning mechanisms can be RAT-independent (e.g., the positioning of the UE is not dependent on the RAT), such as Enhanced GNSS, and / or WLAN, Bluetooth, Terrestrial Beacon System (TBS) based positioning techniques, and / or sensor (e.g., barometric pressure sensor, motion sensor) based positioning techniques, etc. Some UE positioning mechanisms can be based on a hybrid model, where multiple positioning methods are used, which can include both RAT-dependent and RAT-independent positioning techniques (e.g., GNSS with OTDOA hybrid positioning).

[0093] Note that the terms “positioning reference signal” and “PRS” generally refer to specific reference signals used for positioning in NR and LTE systems. However, as used herein, the terms “positioning reference signal” and “PRS” can also refer to any type of reference signal that can be used for positioning, such as but not limited to: PRS as defined in LTE and NR, TRS, PTRS, CRS, CSI-RS, DMRS, PSS, SSS, SSB, SRS, UL-PRS, etc. Furthermore, the terms “positioning reference signal” and “PRS” can refer to downlink or uplink positioning reference signals, unless otherwise indicated by the context. To further distinguish between types of PRS, downlink positioning reference signals can be referred to as “DL PRS,” and uplink positioning reference signals (e.g., SRS, PTRS for positioning) can be referred to as “UL-PRS.” Furthermore, for signals that can be transmitted in both uplink and downlink (e.g., DMRS, PTRS), these signals can be prepended with “UL” or “DL” to distinguish the direction. For example, “UL-DMRS” can be distinguished from “DL-DMRS.”

[0094] Devices (e.g., UEs) equipped with global navigation satellite system (GNSS) receivers, which can include global positioning system (GPS) receivers, can determine their position based on GNSS positioning. GNSS is a network of satellites that broadcast timing and orbital information used for navigation and positioning measurements. GNSS can include multiple sets of satellites, known as constellations, that broadcast signals (which can be referred to as GNSS signals) to control stations and users of the GNSS. Based on the broadcast signals, users can be able to determine their position (e.g., via a trilateration process). For the purposes of the present disclosure, a device (e.g., a UE) equipped with a GNSS receiver or capable of receiving GNSS signals can be referred to as a GNSS device, and a device capable of transmitting GNSS signals, such as a satellite, can be referred to as a space vehicle (SV).

[0095] Figure 5 FIG. 500 is a diagram 500 illustrating an example of GNSS positioning in accordance with various aspects of the present disclosure. A GNSS device 506 can estimate its position and time based at least in part on data (e.g., GNSS signals 504) received from multiple space vehicles (SVs) 502, where each SV 502 can carry a record of its position and time and can transmit that data (e.g., record) to the GNSS device 506. Each SV 502 can also include a clock that is synchronized with other clocks of the SVs and with ground clocks. If the SV 502 detects a divergence from the time maintained on the ground, the SV 502 can correct for it. The GNSS device 506 can also include a clock, but the clock of the GNSS device 506 can not be as stable and accurate as the clocks of each SV 502.

[0096] Because the speed of a radio wave can be constant and independent of satellite speed, the time delay between when a SV 502 transmits a GNSS signal 504 and when the GNSS device 506 receives the GNSS signal 504 can be proportional to the distance from the SV 502 to the GNSS device 506. In some examples, the GNSS device 506 can use a minimum of four SVs to calculate / estimate one or more unknowns associated with a position (e.g., three position coordinates and a clock bias from satellite time, etc.).

[0097] Each SV 502 can continuously broadcast a GNSS signal 504 (e.g., a carrier with modulation), which can include a pseudo-random code (e.g., a sequence of ones and zeros) known to GNSS device 506, and can also include a message that includes a time of transmission and the SV’s position at that time. In other words, each GNSS signal 504 can carry two types of information: time and a carrier (e.g., a modulated waveform with an input signal to be transmitted electromagnetically). Based on the GNSS signal 504 received from each SV 502, GNSS device 506 can measure a time of arrival (ToA) of the GNSS signal 504 and calculate a time of flight (ToF) of the GNSS signal 504. Then, based on the ToF, GNSS device 506 can calculate its three-dimensional position and clock bias, and GNSS device 506 can determine its position on Earth. For example, the position of GNSS device 506 can be converted into latitude, longitude, and altitude relative to an ellipsoidal Earth model. These coordinates can be displayed on a mobile map display, for example, or recorded or used by some other system, such as a vehicle guidance system.

[0098] While the distance between a GNSS device and a SV can be estimated based on the time it takes for a GNSS signal to arrive at the GNSS device, the sequence of the signal of the SV can be delayed relative to the sequence of the GNSS device. Thus, in some examples, a delay can be applied to the sequence of the GNSS device so that the two sequences are aligned. For example, to estimate the delay, the GNSS device can align a pseudo-random binary sequence included in the SV signal with an internally generated pseudo-random binary sequence. Since the GNSS signal of the SV takes time to arrive at the GNSS device, the sequence of the SV can be delayed relative to the sequence of the GNSS device. By gradually delaying the sequence of the GNSS device, the two sequences can eventually align.

[0099] The accuracy of GNSS-based positioning can depend on various factors, such as satellite geometry, signal blockage, atmospheric conditions, and / or receiver design features / quality, among others. For example, a GNSS receiver used by a smartphone or smartwatch can have lower accuracy compared to a GNSS receiver used by a vehicle and surveying equipment. To improve the accuracy of GNSS positioning (e.g., from meters to centimeters), real-time kinematic (RTK) techniques or mechanisms (which can be collectively referred to as an RTK engine hereinafter) can be used for a positioning device (e.g., a UE, surveying equipment, automotive GNSS system, etc.). For example, an RTK engine can enable a positioning device to use correction information from a base station to mitigate one or more error sources in GNSS receiver pseudo-range (PR) and carrier-phase (CP) measurements, which can include satellite orbit errors, satellite clock errors, and / or atmospheric errors, among others. Thus, the positioning device can achieve better accuracy.

[0100] Figure 6 is a diagram 600 illustrating an example of RTK positioning in accordance with various aspects of the present disclosure. In one example, at least two receivers can be used in association with RTK positioning, where at least one of the receivers can be fixed, which can be referred to as a base station 602 or RTK base station, and at least one other receiver can be mobile (e.g., can move from time to time), which can be referred to as a rover station or rover station device 604 (e.g., GNSS / GPS receiver, UE, rover station, etc.). In other words, an RTK system can include at least a base station and a rover station, where the base station can be a fixed receiver whose location is known.

[0101] The range between the SVs 606 (e.g., GNSS / GPS satellites) and the rover station device 604 or between the SVs 606 and the base station 602 can be calculated by determining the number of carrier cycles between the SVs 606 and the rover station device 604 or the base station 602 and multiplying that number by the carrier wavelength 612 of the carrier 610 (e.g., carrier signal) transmitted by the SVs 606. For example, if the SVs 606 transmit a carrier 610 with a wavelength 612 of ten (10) meters and the rover station device 604 receives the carrier 610 and determines that there are five hundred (500) carrier cycles between the SVs 606 and the rover station device 604, then the rover station device 604 can calculate the distance between the SVs 606 and the rover station device 604 by multiplying the number of determined carrier cycles (e.g., 500) by the carrier wavelength 612 (e.g., 10 meters), which can be five thousand meters (e.g., 500 x 10 = 5000). Similarly, the base station 602 can also receive the carrier 610 from the SVs 606 and determine the range of that carrier from the satellites 606 based on the wavelength 612 of the carrier 610 and the number of carrier cycles between the base station 602 and the SVs 606. The rover station device 604 and / or the base station 602 can calculate the range (e.g., distance) between the rover station device 604 / base station 602 and multiple (e.g., four or more) SVs (e.g., SVs 606 and SVs 608) to determine their geographic location (e.g., their location on the earth).

[0102] During RTK positioning, the rover device 604 (e.g., UE, client device, etc.) can undergo a “ambiguity resolution” process to determine the number of carrier cycles between the SVs 606 and the rover device 604. In other words, when the rover device 604 receives a carrier from the SVs 606, the rover device 604 can take time to calculate how many carrier cycles exist between the SVs 606 and the rover device 604. In some examples, GNSS receivers with more complex or high-end antennas / hardware (such as car-level antennas) can be able to resolve ambiguities in a relatively short amount of time (e.g., within seconds), while GNSS receivers with less complex or low-end antennas / hardware (such as antennas used for mobile phones and / or smart watches) can take a longer amount of time (e.g., 10-30 minutes or more) to resolve ambiguities. In some examples, ambiguities can also be referred to as “integer ambiguities.” In some examples, the process by which a GNSS receiver resolves ambiguities can be referred to as convergence, and the amount of time it takes for a device to resolve ambiguities can be referred to as convergence time.

[0103] In some scenarios, the ranges computed by the rover device 604 can include errors due to SV clock and ephemeris, as well as ionospheric and tropospheric delays, among other things. Additionally, because the rover device 604 is more likely to be mobile, the quality of the signals / carriers received from each SV can change as the rover device moves from one location to another. For example, if the rover device 604 moves from an open sky area to an area with buildings, the signals from one or more SVs 606 / 608 can be blocked / reflected by the buildings. Thus, the ranges computed by the rover device 604 can start to drift and can include errors.

[0104] On the other hand, since the base stations 602 are likely to be stationary, have known locations, and can be equipped with more complex and high-end GNSS receivers, the base stations 602 can be able to maintain accurate calculations of ranges as compared to the rover device 604. For example, the base stations 602 can be located at sites (e.g., open sky areas) with minimal environmental influences (such as interference and multipath). As such, under RTK positioning, since the base stations 602 can already know their locations (e.g., via pre-measurements), the base stations 602 can perform measurements on the SVs to obtain reference receiver measurements (e.g., to estimate the differences between the base stations and the SVs). The base stations 602 can then subtract the geometric distances between the base station locations to the SV locations from the reference receiver measurements to obtain reference corrections (e.g., based on the differences or errors). The base stations 602 can generate correction data 614 (or correction signals) based on the obtained reference corrections and transmit the correction data 614 to the rover device 604 to help the rover device 604 correct for errors. For example, since the rover device 604 can typically be configured to be located near the base stations 602 (e.g., within 6 miles, 12 miles, etc.), the rover device 604 is likely to encounter similar errors (e.g., similar ionospheric and tropospheric delays, etc.) as the base stations 602. Thus, the rover device 604 can use the correction data 614 from the base stations 602 to improve and speed up its own positioning calculations from the GNSS constellation to achieve centimeter precision. In other words, a base station can be configured to remain at a fixed / known location and transmit correction data to one or more rover devices, and the one or more rover devices can use the correction data to increase the precision of their positioning and the speed of error correction. Thus, the rover device 604 can use algorithms that incorporate ambiguity resolution and differential corrections to determine its position. The positioning accuracy that the rover device 604 can achieve can depend on its distance from the base stations 602 and the accuracy of the differential corrections (e.g., correction data 614).

[0105] In some examples, software or applications that accept positioning-related measurements from GNSS chipsets and / or sensors to estimate a device’s position, velocity, and / or altitude can be referred to as a positioning engine. Further, a positioning engine that is capable of achieving a particular level of high accuracy (e.g., centimeter / demeter level accuracy) and / or latency can be referred to as a precise positioning engine (PPE). For example, a positioning engine that is capable of performing RTK (e.g., receiving or processing correction data associated with RTK) can be considered a PPE.

[0106] The accuracy of network-based positioning can depend on various factors, such as the capabilities of the UE, the location of the UE, the number of transmission reception points (TRPs), and the like. For example, a lower-end UE (or UE with lower capabilities) can have lower transmit / receive capabilities and / or measurement capabilities compared to a higher-end UE (or UE with higher capabilities). Thus, the lower-end UE can provide lower accuracy for network-based positioning compared to the higher-end UE.

[0107] To improve the accuracy of network-based positioning, a positioning reference unit (PRU) can be used to assist a positioning device (e.g., a UE, surveying equipment, automotive GNSS system, and the like) to perform positioning. The PRU can be similar to an RTK base station. For example, a positioning engine can enable the positioning device to use measurements or correction information from the PRU to mitigate one or more error sources in the measurements of the positioning device. Thus, better accuracy can be achieved by the positioning device.

[0108] In some examples, the PRU can refer to a device with a known location that is capable of performing positioning measurements (e.g., RSTD, RSRP, UE Rx-Tx time difference measurements, and the like) and reporting these measurements to a location server (e.g., LMF). For example, the PRU can be a UE or a TRP with a known location. Additionally, the PRU can transmit SRS to enable one or more TRPs to measure and report UL positioning measurements (e.g., RTOA, UL-AoA, base station Rx-Tx time difference, and the like) from the PRU at the known location. The location server can compare the PRU measurements to expected measurements at the known PRU location to determine correction information for other nearby target devices. The DL and / or UL position measurements of the other target devices can then be corrected based on the correction information.

[0109] Figure 7is a diagram 700 illustrating an example PRU in accordance with various aspects of the present disclosure. A UE 702 can be configured to measure a first PRS (PRS1) transmitted from a first TRP 708 and a second PRS (PRS2) transmitted from a second TRP 710. The PRU 704 can also be configured to measure the first PRS transmitted from the first TRP 708 and the second PRS transmitted from the second TRP 710. The PRU 704 can then provide its measurements, assistance data, and / or correction data to other UEs (e.g., UEs in the vicinity of the PRU 704, such as the UE 702) to assist the other UEs in achieving high accuracy positioning. For example, a positioning engine 706 (which can be located at the UE 702 or at a location server) can receive raw measurements (e.g., for the first PRS and the second PRS) from the UE 702 and measurement / correction data from the PRU 704, and the positioning engine 706 can apply or fuse the measurement / correction data from the PRU 704 to the raw measurements from the UE 702 to mitigate / remove errors in the raw measurements.

[0110] The PRU 704 can be used for both terrestrial network (NT) based positioning and non-terrestrial network (NTN) based positioning. In some scenarios, a UE can have the ability to communicate with a server or another UE via an NTN. An NTN can refer to a network or network segment that uses at least one airborne device (e.g., an aircraft) or a satellite (e.g., a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a highly elliptical orbit (HEO) satellite, and / or a high-altitude pseudo-satellite (HAPS), etc.) for communication (e.g., transmitting data or receiving data). For example, an NTN can support direct communication between a UE (e.g., a handset, a mobile phone, etc.) and a satellite (e.g., a LEO satellite or a GEO satellite, etc.), where the UE can transmit data (e.g., a text message and / or a voice service, etc.) to another UE via the satellite. For purposes of the present disclosure, an NTN can include only NTN cells, or a mix of NTN cells and terrestrial cells. Thus, for positioning operations associated with an NTN, the positioning operations can involve NTN cells without terrestrial cells, a mix of NTN and terrestrial cells, and / or involve a hybrid solution of NTN cells, terrestrial cells, GNSS satellites, and / or other terrestrial-based positioning reference points (such as WiFi, Bluetooth, etc.). In some examples, a gateway associated with an NTN can be configured to work like a PRU.

[0111] In one example, the NTN architecture can be configured to be transparent payload based. For example, a data network (e.g., a 5G Core (5GC) network) can be connected to a base station (e.g., a network entity, gNB) via a communication interface (e.g., a Next Generation (NG) interface). The base station can be located on the ground and connected to an NTN gateway, where the NTN gateway can be connected to an NTN payload (e.g., a network node on board a satellite, an unmanned aircraft system (UAS), or a HAPS, etc.) via a feeder link. The NTN gateway can refer to a node in the network that behaves as a relay between the satellite and the UE, as the link budget can be limited between the satellite and the UE. The NTN gateway can have better Tx power or larger antenna to communicate with the satellite compared to the UE. The NTN payload can be connected to the UE via a service link (e.g., using a UE-UTRAN (Uu) interface). Under the transparent payload NTN architecture, the base station can be a ground station and the NTN payload (e.g., a satellite) can work like a relay, where the NTN payload can provide radio frequency filtering, frequency conversion, and / or amplification for data / payload received from the base station via the NTN gateway and relay / transmit the data / payload to the UE. Thus, the waveform or signal relayed / repeated by the NTN payload can remain unchanged.

[0112] The PRU 704 can be stationary or mobile, and the PRU 704 can be any device with the capability to measure reference signals and / or transmit reference signals. For example, the PRU 704 can be a UE / TRP / RSU that is capable of transmitting reference signals to and / or receiving reference signals from other devices, etc. The PRU can greatly improve the accuracy of difference-based positioning because it is capable of measuring reference signals transmitted from multiple devices (e.g., TRPs). For the purposes of the present disclosure, difference-based positioning can refer to any positioning method / mechanism that involves measuring a difference between two receive (Rx) nodes. For example, difference-based positioning can include double difference (DD)-time difference of arrival (TDoA) (DD-TDoA), DD-round trip time (RTT) (DD-RTT), single difference RTT (D-RTT), (same Tx, different Rx), D / DD-AoD, D / DD-AoA, D / DD-carrier phase, etc.

[0113] A PRU (e.g., PRU 704) can transfer its measurements, assistance data, and / or correction data to a location server (e.g., LMF) or to a UE (e.g., via a sidelink (SL) or via a location server). For example, for UE-based positioning (where a UE is configured to determine its own position), the UE can be designated to receive measurements, assistance data, and / or correction data from a PRU, and the UE can also be designated to know the locations of the PRU and TRPs (e.g., for computing its position). The UE can use the correction data to compensate (e.g., cancel) various types of errors, such as TRP / UE group delay, synchronization error across TRPs, initial Tx / Rx carrier phase bias, and / or anchor position error, among others. In some examples, anchor position error cancellation can not be accurate if the PRU and the UE are far apart from each other. For the purposes of this disclosure, a device that transmits a reference signal and / or receives a reference signal during positioning of a UE can be referred to as an anchor. For example, an anchor can be a stationary TRP that transmits PRS to a UE on a Uu link, an anchor can be a mobile UE that transmits a reference signal to another UE on a sidelink (e.g., during sidelink positioning), or an anchor can be a satellite associated with an NTN that transmits GNSS signals to a UE, among others.

[0114] While a PRU can improve the accuracy of UE-based positioning of a UE, the UE can be designated to know the locations of the PRU and the corresponding anchor (e.g., TRP, satellite, etc.) to determine / estimate its position. In some scenarios or regions, there can be privacy concerns or regulations regarding sharing anchor and / or PRU location information. For example, an operator of a network (e.g., an NT and NTN) can be very concerned about revealing the locations of its TRPs, gateways, and / or PRUs. When a PRU is a UE, the UE can also be designated to follow certain privacy protocols to protect the privacy of its user.

[0115] Aspects presented herein can enable a UE to achieve high-accuracy positioning without knowing the locations of certain network nodes, such as PRUs and TRPs. Aspects presented herein can enable a UE to perform positioning (e.g., UE-based positioning) using a virtual PRU (VPRU) and / or a virtual anchor, such that a PRU / anchor can provide measurements, reference signals, assistance data, and / or correction data to a UE without disclosing their actual locations. In one aspect of the disclosure, a VPRU can indicate that there is no physical PRU (PPRU) located at the claimed location of the VPRU, where measurements, assistance data, and / or correction data can be virtually generated for the UE based on VPRU and / or PPRU information / measurement. Thus, a network can generate a VPRU or virtual reference station for a UE at any location. Measurements, assistance data, and / or correction data from a VPRU can be based on measurements of one or more physical PRUs and / or based on network resolution / tracking of various error source values.

[0116] By enabling a UE to perform positioning using a virtual anchor (e.g., TRP / satellite), a carrier operator (e.g., operator of a location server, LMF, NTN, etc.) can avoid releasing / providing accurate or true locations of its network nodes, such as anchor base stations and / or anchor satellites, thereby maintaining privacy and security of these network nodes. Additionally, for mobile anchors, such as mobile UEs associated with sidelink positioning or LEO satellites associated with an NTN, locations of these mobile anchors can be difficult to estimate and share with a UE in real-time. Thus, using a virtual anchor can be more suitable and convenient for a UE to perform positioning. Aspects presented herein can enable a ground truth location of an anchor to be protected with noise, where if a UE uses noisy anchor location information without a PRU, positioning accuracy can be reduced. Similarly, by enabling a UE to perform positioning using a VPRU, a carrier operator or PRU can also avoid releasing / providing accurate or true ground locations of a PRU, thereby maintaining privacy and security of the PRU. Locations of a VPRU can be pre-assigned (e.g., which can be more suitable for an NTN) or generated based on a location of a target UE (e.g., a generated VPRU is proximate to a target UE). Aspects presented herein can enable a UE to achieve high accuracy positioning by enabling the UE to cancel out common anchor location errors (e.g., using correction data from a PRU). Furthermore, while a physical PRU can not be able to receive measurements and / or signals from the same set of anchors as a UE, using a VPRU can enable measurements from the VPRU to be associated with one or more common anchors of the UE. In other words, using a virtual PRU can guarantee measurements from common anchors.

[0117] In one aspect of the disclosure, a network can generate a virtual anchor (e.g., virtual TRP, virtual UE, or virtual satellite, etc.) by applying a distance / vector offset (which can also be referred to as noise or error) to an actual location (which can also be referred to as a ground truth location) of an anchor. Generally, for UE-based positioning, a location server can transmit accurate locations of anchors (e.g., TRPs, UEs, and / or satellites, etc.) participating in positioning to a target UE (e.g., a UE whose location is to be determined), such as via assistance data. However, by using a virtual anchor, the network can instead transmit noisy / virtual anchor locations to the UE.

[0118] Figure 8 is a diagram 800 illustrating examples of generating a virtual anchor or protecting a true location of a physical anchor in accordance with various aspects of the disclosure. In one example, as shown at 802, a physical anchor (e.g., TRP) can be located at a ground location, which can be referred to as a ground truth location. For a mobile anchor (e.g., UE, satellite, etc.), the ground truth location can correspond to a current location of the anchor (which can be in the sky / space for a satellite).

[0119] As shown at 804, to generate the virtual anchor (or to protect the ground truth location of the physical anchor), the network can apply an anchor location error to the ground truth location of the physical anchor such that a virtual anchor is generated at a virtual location, which can be referred to as a noisy anchor location. In other words, the noisy anchor location of the virtual anchor can be equal to the ground truth location of the physical anchor plus the anchor location error (e.g., noisy anchor location = ground truth location + anchor location error). For example, the anchor location error can correspond to a distance / vector offset that sets the virtual anchor X meters / km away from the physical anchor in a particular direction. In another example, the anchor location error can correspond to a coordinate offset that sets the virtual anchor at a specified latitude and longitude of a geographic coordinate system. In some examples, based on privacy specifications, the mean and / or variance of the anchor location error can be configured to vary. For example, the anchor location error can follow certain types of distributions for privacy protection (e.g., Laplacian distribution, truncated Gaussian distribution, etc.). In some examples, the anchor location error can be applied to multiple physical anchors to generate multiple virtual anchors. In other examples, different anchor location errors can be applied to different physical anchors.

[0120] After generating the virtual anchor, the network can configure the UE to perform positioning with the virtual anchor based on the noisy anchor location of the virtual anchor (and also based on the VPRU discussed below). For example, the network can provide the UE with a list of virtual anchors with their noisy anchor locations via assistance data such that the UE can perform positioning with one or more of the virtual anchors in the list of virtual anchors based on their noisy anchor locations. In some examples, a new virtual anchor location information element (IE) can be added to the assistance data for certain positioning schemes, such as UE-based positioning with a double difference (DD)-based scheme. Since the UE can not know that the anchor is a virtual anchor, the virtual anchor location IE can indicate to the UE that certain anchors are virtual anchors. For the virtual anchors, the UE can send reference signals (e.g., SRS) to the virtual anchors and / or receive reference signals (e.g., PRS) from the virtual anchors, where the signals would be sent from and received by the corresponding physical anchors. In other words, the UE can treat the virtual anchors as physical anchors.

[0121] In one aspect of the disclosure, the network can generate a virtual PRU (VPRU) or a set of VPRUs based on one or more physical PRUs, where the physical PRUs can be configured to receive reference signals from one or more anchors and / or send reference signals to one or more anchors. The physical PRUs can then send their measurements for the one or more anchors to a server, such as a location server or LMF. Based on the measurements from the one or more physical PRUs, the server can generate one or more VPRUs that can be used to assist a UE in positioning.

[0122] Figure 9 and Figure 10FIGS. 900 and 1000 are diagrams 900 and 1000 illustrating examples of creating a VPRU based on a set of physical PRUs, in accordance with various aspects of the present disclosure. As Figure 9 As shown by diagram 900, a given area 902 can have a set of physical PRUs, which can include a first physical PRU 904, a second physical PRU 906, a third physical PRU 908, and up to an Nth physical PRU 910, etc. The set of physical PRUs can be configured to measure / receive reference signals transmitted from one or more anchors and / or transmit reference signals to one or more anchors. For example, the set of physical PRUs can measure PRS transmitted from a first TRP 912 and a second TRP 914 and / or transmit SRS to the first TRP 912 and the second TRP 914.

[0123] Then, as shown at 916, the set of physical PRUs can transmit their measurements to a server 918 (e.g., a network entity such as a location server or LMF). In some examples, the measurements can include TDoA of PRS transmitted from the first TRP 912 and the second TRP 914, RTT between the PRUs and the TRPs, AoA of PRS, and / or carrier phase of PRS, etc. The server 918 can also collect uplink (UL) measurements (e.g., for measuring reference signals transmitted from the set of physical PRUs) from the first TRP 912 and the second TRP 914.

[0124] As Figure 10As shown in diagram 1000, when UE 920 performs UE-based positioning in a given area 902 and is configured to measure PRS transmitted from first TRP 912 and second TRP 914, server 918 can generate a VPRU 922 at a virtual location near UE 920, such as shown at 924. Server 918 can also compute / estimate a set of measurements, assistance data, and / or correction data for VPRU 922 based on measurements from the set of PRUs, first TRP 912, and / or second TRP 914, etc. For example, based on TDoA measurements from first physical PRU 904 and third physical PRU 908 for PRS transmitted from first TRP 912 and second TRP 914, server 918 can estimate a TDoA measurement for a PRU (e.g., a virtual PRU) located between first physical PRU 904 and third physical PRU 908 (e.g., the TDoA measurement can be closer to first physical PRU 904 if VPRU 922 is set closer to first physical PRU 904, and the TDoA measurement can be closer to third physical PRU 908 if VPRU 922 is set closer to third physical PRU 908, etc.). In one example, the measurements for VPRU 922 can be based on geometric interpolation between measurements from the set of physical PRUs (e.g., based on distances from VPRU 922 to physical PRUs 904, 906, 908, 910, etc.). In another example, measurements from the set of physical PRUs can be used to estimate errors (e.g., synchronization errors, set delays, etc.). The estimated errors can then be added to error-free virtual measurements for VPRU 922 (e.g., ground truth based on VPRU location and anchor locations including location errors). As an illustration, server 918 can estimate an RSTD error between first TRP 912 and second TRP 914 based on third physical PRU 908, and then server 918 can add the estimated RSTD error to error-free RSTD measurements for VPRU 922. Similarly, server 918 can estimate an RSTD error between first TRP 912 and second TRP 914 based on first physical PRU 904, and server 918 can add the estimated RSTD to error-free RSTD measurements for VPRU. Server 918 can then send the generated measurements, assistance data, and / or correction data associated with VPRU 922 (and the virtual location of VPRU 922) to UE 920. Based on the measurements, assistance data, correction data, and / or location of VPRU 922, UE 920 (or a positioning engine of the UE) can compute / estimate its position as described in connection with Figure 7 diagram 1000, server 918 can generate a VPRU 922 at a virtual location near UE 920, such as shown at 924. Server 918 can also compute / estimate a set of measurements, assistance data, and / or correction data for VPRU 922 based on measurements from the set of PRUs, first TRP 912, and / or second TRP 914, etc. For example, based on TDoA measurements from first physical PRU 904 and third physical PRU 908 for PRS transmitted from first TRP 912 and second TRP 914, server 918 can estimate a TDoA measurement for a PRU (e.g., a virtual PRU) located between first physical PRU 904 and third physical PRU 908 (e.g., the TDoA measurement can be closer to first physical PRU 904 if VPRU 922 is set closer to first physical PRU 904, and the TDoA measurement can be closer to third physical PRU 908 if VPRU 922 is set closer to third physical PRU 908, etc.). In one example, the measurements for VPRU 922 can be based on geometric interpolation between measurements from the set of physical PRUs (e.g., based on distances from VPRU 922 to physical PRUs 904, 906, 908, 910, etc.). In another example, measurements from the set of physical PRUs can be used to estimate errors (e.g., synchronization errors, set delays, etc.). The estimated errors can then be added to error-free virtual measurements for VPRU 922 (e.g., ground truth based on VPRU location and anchor locations including location errors). As an illustration, server 918 can estimate an RSTD error between first TRP 912 and second TRP 914 based on third physical PRU 908, and then server 918 can add the estimated RSTD error to error-free RSTD measurements for VPRU 922. Similarly, server 918 can estimate an RSTD error between first TRP 912 and second TRP 914 based on first physical PRU 904, and server 918 can add the estimated RSTD to error-free RSTD measurements for VPRU. Server 918 can then send the generated measurements, assistance data, and / or correction data associated with VPRU 922 (and the virtual location of VPRU 922) to UE 920. Based on the measurements, assistance data, correction data, and / or location of VPRU 922, UE 920 (or a positioning engine of the UE) can compute / estimate its position as described in connection with

[0125] Figure 11 is a diagram 1100 illustrating an example of generating a virtual PRU base station for NTN-based positioning based on one or more physical PRU base stations, in accordance with various aspects of the present disclosure. Similar to generating a VPRU based on a set of physical PRUs, a virtual PRU base station can be generated by an NTN network based on a set of physical PRU base stations associated with the NTN. For example, a set of physical PRU base stations that can include a first physical PRU base station, a second physical PRU base station, a third physical PRU base station, and up to an Nth physical PRU base station, etc. can be configured to measure / receive positioning reference signals transmitted from one or more satellites. The set of physical PRU base stations can then transmit their positioning reference signal measurements or positioning reference signal observation data for the one or more satellites to an LMF.

[0126] The LMF can then generate a virtual PRU base station at a virtual location proximate to the UE when the UE is configured to estimate its location. The LMF can also operate / compute a set of positioning reference signal measurements / observations for the virtual PRU base station. Thus, the UE can determine its location using the positioning reference signal measurements / observations for the virtual PRU base station without needing to know the ground truth locations or the physical PRU base stations.

[0127] Using virtual PRU base stations can reduce the total number of physical PRU base stations deployed in an area. For example, a physical PRU base station can provide a service coverage radius of approximately 20 km to 30 km. If the distance between two physical PRU base stations is approximately 50 km apart, and each physical PRU base station only serves UEs in the vicinity, then over 4000 PRU base stations can be designated to cover the continental United States.

[0128] On the other hand, when using virtual PRU base stations, the distance between two physical PRU base stations can be configured to be further apart, such as between 100 km to 200 km, because a virtual PRU base station can be generated for a UE based on the location of the UE. In other words, the UE can not be designated to be located in the vicinity of a physical PRU base station in order to receive corresponding correction data from the physical PRU base station. The LMF can collect data from the physical PRU base stations, estimate the spatial distribution of the relevant errors for the virtual PRU base station, and send corrections to the UE based on the virtual PRU base station. Such a configuration can significantly reduce the density of physical PRU base stations to be deployed (e.g., only 400 PRU base stations can be designated to cover the continental United States instead of 4000 PRU base stations). This can also improve the positioning performance at the client (e.g., UE) side.

[0129] In some examples, to have the LMF generate a virtual PRU base station close to the UE and compute the positioning reference signal observations for the virtual PRU base station, the PRU server can be designated to know the location of the UE (e.g., the true location or an estimated location). The LMF can fix the carrier phase ambiguity between the physical PRU base stations and compute the error for each physical PRU base station. Then, the LMF can interpolate the estimated PRU base station error to the location of the virtual PRU base station. The processing of the PRU correction data at the UE can be the same as for the physical based PRU base station. For example, the LMF can provide the UE with semi-synthetic positioning reference signal observations (e.g., observed from the virtual PRU base station). In response, the UE can compute a virtual baseline from the UE to the virtual PRU base station and the UE can determine its location using the virtual baseline and the PRU correction data.

[0130] As discussed in connection with Figures 9-11 For a VPRU or virtual RTK base station (hereinafter collectively referred to as “virtual reference station” or “VRS”) that provides helpful / useful measurements, assistance data, and / or correction data to a UE, the virtual location of the VRS can be configured to be as close as possible to the actual or estimated location of the UE. In some examples, for optimal public anchor error cancellation, a short baseline (e.g., a threshold distance) between the UE and the PRU (or VRS) can be designated or defined. For example, the ratio between the range from the anchor to the UE and the range from the PRU to the UE (e.g., ratio = anchor-UE range / PRU-UE range) can be configured to exceed or maintain a certain ratio threshold (which can be a large value). If the anchor is a GNSS satellite, the ratio can be about 20000 km / 1 km. In other words, if the range between the GNSS satellite and the UE is about 20000 km, the distance between the UE and the PRU / VPRU can be designated to be within 1 km.

[0131] In one aspect of the disclosure, the location of a VRS (e.g., VPRU, virtual PRU base station, etc.) can be pre-assigned by the network to a list of locations or can be based on a pre-defined rule. In some examples, such configuration can be more suitable for NTN.

[0132] Figure 12is a diagram 1200 illustrating an example of pre-assigning locations of VRSs according to various aspects of the present disclosure. In one example, a network can generate a grid of X meters (m) or kilometers (km) over the Earth, where the grid size can be predefined (e.g., 1 m, 2 m, 5 m, etc. for indoor applications; and 5 km, 10 km, 50 km, etc. for outdoor applications). The network can then associate each intersection on the grid with an identifier (ID). For example, as shown at 1202, a first intersection on the grid can be associated with a first ID (e.g., ID N), a second intersection on the grid can be associated with a second ID (e.g., ID L), and a third intersection on the grid can be associated with a third ID (e.g., ID N), and so on. The IDs and their corresponding locations can then be used by the network to assign VRSs. For example, the network can generate a VPRU or virtual PRU base station at each intersection.

[0133] The grid information can also be pre-programmed to the UE or sent to the UE upon request (e.g., in response to an assistance data request). Based on the grid information, the UE can request differential services (e.g., positioning services) from the network to directly use a particular VRS. For example, if the UE is close to the intersection with ID N, the UE can request the network to provide the VPRU at that intersection based on the corresponding ID (e.g., the UE can indicate ID N to the network). On the other hand, if the UE does not request a particular VRS, the network can provide a VRS that the network believes is close (or closest) to the UE.

[0134] In another aspect of the present disclosure, the locations of the VRSs can be generated based on a location of the UE (or a mobile station device). This can be more suitable for TN. For example, based on a coarse estimate of the location of the UE, a network server (e.g., a location server or LMF) can determine a VRS location that is as close as possible to the coarse estimate. In one example, the coarse estimate of the location of the UE can be determined based on a serving cell ID of the UE, a serving beam ID of the UE, an enhanced cell ID (ECID) of the UE, a previous estimated location of the UE, a location reported by the UE, and / or a RAN-independent location estimate. In another example, the UE can transmit a differential-based positioning request to the network server with its coarse / previous location for a VRS. For example, the UE can transmit its coarse location to the network server, and the network server can generate a VRS for the UE based on the coarse location of the UE.

[0135] In another example, the coarse estimate of the location of the UE can be determined based on a sidelink (SL) zone ID associated with the UE. For example, in some network implementations, if a sidelink zone configuration (sl-ZoneConfig) is configured, the UE can use the following formula to determine the identity of the zone (i.e., zone ID) in which it is located:

[0136] x1 = Floor(x / L) Mod 64;

[0137] y1 = Floor(y / L) Mod 64;

[0138] Zone_id = y1*64 + x1.

[0139] L can indicate a value of a sidelink zone length (sl-ZoneLength) and can be included in a sidelink zone configuration (sl-ZoneConfig). In other words, the sidelink zone configuration can define the sidelink zone length. In some examples, the sidelink zone length can be configured to be 5 meters, 10 meters, 20 meters, 30 meters, 40 meters, or 50 meters long, which can be a suitable / reasonable range for SL-based positioning. x can indicate a geodesic distance in longitude between a current location of the UE and a geographic coordinate (0, 0) according to a World Geodetic System (e.g., WGS84 model) and is expressed in meters. y is a geodesic distance in latitude between the current location of the UE and the geographic coordinate (0, 0) according to the World Geodetic System and is also expressed in meters. Thus, the zone ID of the UE can be computed using the current location of the UE and the geographic coordinate. In some examples, an initial location of the UE (which can be coarse) can be estimated by the UE with assistance from the network.

[0140] For cellular-based positioning (e.g., terrestrial network-based positioning), the range between the anchor and the UE (e.g., between a TRP and a UE) can be much smaller compared to GNSS or non-terrestrial network scenarios (e.g., between a satellite and a UE). Thus, multiple iterations of double difference (DD) and VRS can be specified such that the location of the UE can gradually converge to a final position estimate. In each iteration, the VRS position can be different. For example, based on an initial coarse location of the UE, the network can generate a VPRU at a first position that is close to the coarse location of the UE. Then, based on subsequent measurements from the UE, the network can have a better estimate of the current / actual location of the UE and the network can generate another VPRU that is close to the current estimated location of the UE. The network can continue to repeat this process / iteration until certain conditions are met, such as when the final position estimate of the UE reaches a certain accuracy threshold. For example, the exit condition for the iteration can be covariance-based, delta-based (e.g., |L_(i-1)-L L_(i)|), or ratio-based (e.g., ratio of anchor-UE range / PRU-UE range), etc.

[0141] As combined with Figures 9-11As discussed, after the server generates a VRS (e.g., VPRU, virtual PRU base station, etc.), the server may also generate measurement, auxiliary data, and / or correction data associated with the VRS (hereinafter referred to as "virtual / VRS measurement, auxiliary data, and / or correction data"), enabling client devices (e.g., UE, mobile station equipment, etc.) to use the generated measurement, auxiliary data, and / or correction data to assist in their positioning (as if the VRS were an actual physical unit / device). In another aspect of this disclosure, the network or server may generate VRS measurement, auxiliary data, and / or correction data for the VRS based on the VRS's location, noisy anchor locations (e.g., virtual anchor locations), and error source estimation.

[0142] Figure 13 Figure 1300 illustrates examples of generating VRS measurements, auxiliary data, and / or correction data according to various aspects of this disclosure. In one example, UE 1302 may be configured to perform UE-based positioning (e.g., the UE is determining its own location), such as difference-based positioning, and UE 1302 may transmit a positioning request to network entity 1304, which may be a location server or LMF.

[0143] In response, network entity 1304 may provide auxiliary data to UE 1302, which includes a set of virtual anchors that UE 1302 can use for positioning (e.g., as combined with...). Figure 8 (as described) and at least one VRS (e.g., as in combination) Figure 9 and Figure 10 (As described). For example, based on auxiliary data, UE 1302 may select a first virtual anchor 1308 (VAnchor1) with a corresponding noisy anchor position (e.g., a first virtual anchor position), a second virtual anchor 1310 (VAnchor2) with a corresponding noisy anchor position (e.g., a second virtual anchor position), and a VRS 1306 configured to be close to UE 1302 (e.g., at a virtual VRS position).

[0144] In one example, to generate VRS measurement, auxiliary data, and / or correction data for VRS1306, network entity 1304 may determine each measurement, auxiliary data, and / or correction data based on the location of VRS1306, the noisy anchor positions of the first virtual anchor 1308 and the second virtual anchor 1310, and error source estimation (which may also be referred to as error source estimation). (As combined...) Figure 8As discussed, the noisy anchor position of a virtual anchor can be based on applying anchor position errors to a ground truth position of a physical anchor (e.g., a physical anchor position with inherent errors and uncertainties). The error source estimates can include one or more error sources, such as anchor clock bias (e.g., NTN satellite clock), hardware group delay (e.g., delay at TRP), atmospheric effects (e.g., ionospheric and / or tropospheric delays for NTN), non-line-of-sight (NLOS) effects (if applicable), and / or other applicable effects, such as earth rotation effects (e.g., Sagnac effect), tidal effects, nutation, relativity, etc.

[0145] In one aspect, the estimation and tracking of these error sources can be performed at the network entity 1304 or at a PRU (e.g., a physical PRU used to generate a VPRU, as described in connection with Figure 9 and 10 If the estimation and tracking of error sources are performed by the network entity 1304, multiple physical PRUs can be configured to make measurements and report raw measurements or corrections to the network entity 1304, such as described in connection with Figure 9 On the other hand, if the estimation and tracking of error sources are performed by the PRUs, the network entity 1304 can disseminate the error estimates to the PRUs. In other words, each PRU can track its own estimated error sources and provide them to the network entity 1304 based on demand (e.g., after being requested by the network entity 1304).

[0146] In one example, as shown at 1312, the network entity 1304 can broadcast the tracked / estimated error sources based on an observation space representation (OSR) format or a state space representation (SSR) format, where the OSR format can cover all error source(s) using one field / value and the SSR format can estimate and broadcast each error source.

[0147] In another example, as shown at 1314, a VRS measurement of the VRS 1306 can be calculated based on ranges between the virtual anchors and the VRS 1306 and the error sources. For example, the network entity 1304 can calculate a virtual received signal time difference (RSTD) of a signal transmitted from the first virtual anchor 1308 to the VRS 1306 and a signal transmitted from the second virtual anchor 1310 to the VRS 1306 by subtracting the range between the second virtual anchor 1310 and the VRS 1306 (VAnchor2toVRS) from the range between the first virtual anchor 1308 and the VRS 1306 (VAnchorltoVRS) and adding the estimated error sources: sample virtual RSTD = range VAnchor1toVRS - range VAnchor2toVRS+ estimate error sources. Since anchor position errors can be eliminated after the UE 1302 or the positioning engine performs differential measurements between the UE 1302 and the VRS 1306, aspects presented herein can enable the UE 1302 to perform UE-based positioning using virtual anchors and VPRUs. Thus, the network entity 1304 can avoid disclosing live ground positions of physical anchors and PRUs, thereby protecting the privacy and integrity of the physical anchors and PRUs.

[0148] Figure 14 is a communication flow 1400 illustrating an example of a network entity configuring virtual anchors and VPRUs for a UE in accordance with various aspects of the present disclosure. The numbering associated with the communication flow 1400 does not specify a particular timing order and is only used as a reference for the communication flow 1400.

[0149] At 1420, the UE 1402 can transmit an indication to perform UE-based positioning to a network entity 1404 (e.g., location server, LMF, etc.). The UE 1402 can transmit the indication to the network entity 1404 directly or via another network node (e.g., serving base station). UE-based positioning can include at least one difference-based positioning method, such as DD-TDoA, DD-RTT, single-difference RTT, D / DD-AoD, D / DD-AoA, D / DD-carrier phase, etc. In some examples, the indication can be transmitted via an assistance data request message and / or via a capability report. In some implementations, the UE can not be able to decide on a positioning scheme (e.g., UE-based positioning or UE-assisted positioning), where such decisions are made by the network entity (e.g., LMF). However, the UE can report its capabilities to the network entity / server, and the UE and network entity / server can negotiate with each other to confirm whether the positioning is UE-based or UE-assisted.

[0150] At 1422, in response to the UE 1402’s indication to perform UE-based positioning, the network entity 1404 can configure assistance data 1406 for the UE 1402, where the assistance data 1406 can include a list of virtual anchors 1408 and a list of VPRUs 1410 for UE-based positioning, such as described in connection with Figures 8-11 and Figure 13 .

[0151] At 1424, the network entity 1404 can transmit the assistance data 1406 including the list of virtual anchors 1408 and the list of VPRUs 1410 to the UE 1402.

[0152] In one example, as shown at 1428, the network entity 1404 can generate the list of virtual anchors 1408 based on a position / vector offset (e.g., anchor position error) for each physical anchor in a set of physical anchors, such as described in connection with Figure 8 .

[0153] In another example, as shown at 1430, the network entity 1404 can generate a list of VPRUs 1410 based on the at least one physical PRU, where each VPRU can be associated with a corresponding virtual location, such as described in connection with Figures 9-11 described.

[0154] In another example, the network entity 1404 can select the list of VPRUs 1410 based on the corresponding virtual locations of each VPRU and the estimated location of the UE 1402, such as described in connection with Figure 10 and Figure 11 described.

[0155] In another example, a ratio between a first approximate distance from the estimated location of the UE 1402 to the list of virtual anchors 1408 and a second approximate distance from the estimated location of the UE to the list of VPRUs 1410 can be configured to exceed a ratio threshold, such as described in connection with Figure 10 and Figure 11 described.

[0156] In another example, as described in connection with Figure 12 each VPRU in the list of VPRUs 1410 can be pre-assigned or pre-configured. For example, the virtual location of each VPRU can correspond to an intersection of a grid covering a particular area.

[0157] In another example, as described in connection with Figures 10-12 each VPRU in the list of VPRUs 1410 can be generated based on the estimated location of the UE 1402. In some implementations, the network entity 1404 can determine the estimated location of the UE 1402 based on a serving cell ID associated with the UE 1402, a serving beam ID associated with the UE 1402, an enhanced cell ID (ECID) associated with the UE 1402, a previous location estimate of the UE 1402, a location reported by the UE 1402, a SL area ID associated with the UE 1402, and / or a radio access network (RAN)-independent location estimate of the UE 1402.

[0158] In another example, as shown at 1432, the UE 1402 can send a request to the network entity 1404 to use a suitable or preferred VPRU (or multiple suitable or preferred VPRUs). In response, the network entity 1404 can configure the assistance data 1406 to include the suitable or preferred VPRU(s) in the list of VPRUs 1410 based on the request.

[0159] In another example, as shown at 1434, the UE 1402 can indicate to the network entity 1404 to use a designated VPRU (such as the VPRU 1412) for positioning. In response to the indicated VPRU, at 1436, the network entity 1404 can generate a set of measurements or correction data for the VPRU 1412 based on the virtual location of the VPRU 1412 and the virtual locations of one or more virtual anchors. At 1438, the network entity 1404 can send the set of measurements or correction data associated with the VPRU 1412 to the UE 1402, such as described in connection with Figure 13 In one example, the indication sent by the UE 1402 at 1434 and 1432 can be the same. In another example, the network entity 1438 can send the set of measurements or correction data for the VPRU 1412 via the assistance data 1406 if the network entity 1404 knows that the UE 1402 is using the VPRU 1412. In another example, the network entity 1404 can generate a set of measurements or correction data for each VPRU in the VPRU list 1410 (e.g., based on the virtual location of each VPRU in the VPRU list 1410 and the virtual anchor list 1408), and the network entity 1404 can send the set of measurements or correction data to the UE for UE-based positioning based on which VPRU is used by the UE 1402.

[0160] In one example, as described in connection with Figure 13 the set of measurements or correction data can be generated based on one or more error sources, such as anchor clock bias, group delay, atmospheric effects or delays, non-line-of-sight (NLOS) effects, and / or at least one environmental effect. The network entity 1404 can estimate or track the one or more error sources based on raw measurements received from a set of physical PRUs.

[0161] In another example, the network entity 1404 can broadcast the one or more error sources to a plurality of UEs (including the UE 1402) based on an observation space representation (OSR) format or a state space representation (SSR) format.

[0162] At 1426, based on the assistance data 1406, the UE 1402 can perform UE-based positioning using at least one virtual anchor and / or at least one VPRU, such as described in connection with Figure 7 , Figure 10 and Figure 13

[0163] ​In another aspect of this disclosure, for networks (e.g., location servers, LMFs, etc.) that configure virtual anchors and / or VRS for the UE, certain information can be specified to be included in the auxiliary data request from the UE and / or in the auxiliary data from the network. In one example, when the UE transmits an auxiliary data request to the network (e.g., LMF), such as combining... Figure 14 As described in 1420, ancillary data requests may include the UE’s location (e.g., rough location, estimated location, or exact location) and / or a list of observable anchors.

[0164] Including the UE's location in the auxiliary data request can be beneficial, as it allows the network to provide a VRS as close to the UE as possible. However, for UE-based positioning, if the client (consumer) is the UE itself, the UE may not be specified to report its location. In other words, the network may not be specified to know the UE's location. In some scenarios, the network may not know the UE's current or historical location for UE-based positioning. Therefore, to reduce / minimize the range between the UE and the VRS, the UE can be specified to provide / add its location information to the network for high-accuracy VRS-based positioning. Location estimation can be based on previous location estimates using the same positioning method, other RAN-independent methods, serving cells, etc., such as combining... Figure 12 As described.

[0165] It can also be beneficial for the UE to include a list of observable anchors (e.g., anchors that can be detected / observed by the UE) in its auxiliary data request, as this allows the network to configure more appropriate virtual anchor correction data / measurements for the UE. For example, based on the PRS reception at the UE (e.g., the signal-to-noise ratio (SNR) and / or reference signal received power (RSRP) for the received PRS measurement), the UE can observe a subset of anchors (e.g., anchors with good link quality or link quality above a quality threshold). The UE can then transmit information associated with these observable anchors to the network.

[0166] In some scenarios, because the network can generate VRS with customized VRS measurement / calibration data at virtual locations, such as combining Figure 13 As described, customized VRS measurement / correction data can be more accurate if both the UE and the VRS (e.g., VPRU) share measurements with the anchors. Furthermore, the aspects presented herein enable the UE to establish a bidirectional communication link with the location server (e.g., VRS) compared to most GNSS RTK / PPP systems which use a unidirectional communication link (broadcasting correction data). In some examples, to conserve resources and achieve better positioning performance, the UE can request VRS measurements with a set of anchors observed by the UE. The network can then generate customized VRS measurements based on the UE's request, instead of VRS measurements with all anchors.

[0167] When a network (e.g., LMF) transmits assistance data to a UE, such as described in connection with 1424 of FIG. 14, the assistance data can include a virtual anchor group and / or PRU type field / indication. For example, a virtual anchor group ID can be added in the assistance data for UE-based positioning, where each virtual anchor group ID can be associated with (or contain) a set of noisy anchor locations (e.g., live on-ground locations + anchor location errors). Such a configuration can be suitable for roaming scenarios, where this anchor group information (e.g., virtual anchor group ID + noisy anchor locations) can be shared / synchronized across network nodes that support difference-based positioning (e.g., single and double difference) and VRS. Thus, when a UE enters a new area and / or moves / hands over to a different network (e.g., another LMF), the UE can transmit its virtual anchor group ID to the network in an assistance data request. The network can then know the noisy anchor locations and generate VRS measurements / corrections for the VRS used by the UE. Figure 14

[0168] In some scenarios, it can be beneficial for the network to indicate to the UE whether a PRU is a VPRU or a physical PRU, such as by including a PRU type field in the assistance data for the UE. For example, a bit field or integer field can be used to indicate whether a PRU in a PRU list is a VPRU or a physical PRU. Since in some cases a UE can be designated to establish a direct connection (e.g., SL connection, Uu connection, etc.) with a PRU, if the UE knows that a VPRU is a virtual device, the UE can avoid attempting to establish a connection with it. On the other hand, if the assistance data indicates that a PRU is a physical PRU, the UE can know that it is able to establish a SL / Uu connection with the PRU to offload communication traffic.

[0169] Figure 15 is an example of a communication flow 1500 that illustrates information that can be included in an assistance data request and assistance data that can enable a network entity to more efficiently configure virtual anchors and / or VPRUs for a UE in accordance with various aspects of the present disclosure. The numbering associated with communication flow 1500 does not specify a particular timing order and is merely used as a reference for communication flow 1500.

[0170] At 1510, the UE 1502 can send an assistance data request 1506 to a network entity 1504 (e.g., location server, LMF, etc.) to perform UE-based positioning. As shown at 1512, the assistance data request 1506 can include location information for the UE 1502 and / or a list of anchors observed by the UE 1502. The UE-based positioning can be associated with at least one difference-based positioning method.

[0171] ​In one example, as shown at 1520, UE 1502 can obtain its location information prior to sending the assistance data request 1506. For example, UE 1502 can estimate its location based on a service ID associated with UE 1502, a serving beam ID associated with UE 1502, an ECID associated with UE 1502, a previous location estimate of UE 1502, a SL area ID associated with UE 1502, and / or a RAN-independent location estimate of UE 1502, etc.

[0172] At 1514, based on the assistance data request 1506, network entity 1504 can generate and send assistance data 1508 to UE 1502 for UE-based positioning. As shown at 1516, the assistance data 1508 can include a list of virtual anchors and a list of PRUs, which can include a set of VPRUs. Network entity 1504 can select the list of virtual anchors and the list of PRUs based on the location information of UE 1502 or / and a list of anchors observed by UE 1502.

[0173] In one example, as shown at 1516, the assistance data 1508 can also include an indication of whether each PRU in the list of PRUs is a physical PRU or a VPRU. Based on the indication, if a PRU is indicated as a VPRU, UE 1502 can refrain from establishing a direct connection with the PRU in the list of PRUs, or if a PRU is indicated as a physical PRU, UE can enable to establish a direct connection with the PRU in the list of PRUs.

[0174] In another example, the list of virtual anchors can be associated with at least one group ID, such as a virtual anchor group ID. In one example, network entity 1404 can generate anchor group information including an association between a set of different virtual anchor groups and their corresponding group IDs, and network entity 1404 can send the anchor group information of one or more network nodes (e.g., network nodes capable of supporting at least one differential-based positioning method using at least one VPRU) to the one or more network nodes. In another example, network entity 1404 can also send at least one group ID (e.g., to a base station) in response to a UE being handed over to the base station.

[0175] As discussed in connection with Figures 8-11 Each virtual anchor in the list of virtual anchors can correspond to a physical anchor with a location / vector offset, and each VPRU in the set of VPRUs can be generated based on at least one physical PRU (each VPRU in the set of VPRUs is also associated with a virtual location).

[0176] At 1518, UE 1502 can perform UE-based positioning using at least one virtual anchor and at least one VPRU in the assistance data 1508, such as discussed in connection with Figure 9 ,Figure 10 , Figure 13 and Figure 14 As described. In some examples, UE 1502 can also receive a set of measurement or correction data for the group of VPRUs from network entity 1504 based on the virtual location and virtual anchor list of each VPRU in the group, such as combining Figure 14 As described in 1436 and 1438.

[0177] Figure 16 This is a flowchart 1600 of a wireless communication method. The method can be performed by a UE (e.g., UE 104, 404, 702, 920, 1302, 1402, 1502; GNSS device 506; rover device 604; device 1804). This method enables the UE to perform UE-based positioning using virtual anchors and / or virtual PRUs.

[0178] At point 1602, the UE can send an instruction to the network entity to perform UE-based positioning, such as combining... Figure 14 As described. For example, such as Figure 14 As shown at 1420, UE 1402 can send an instruction to network entity 1404 to perform UE-based positioning. The component for sending the instruction may be, for example... Figure 18 The positioning component 198, application processor 1806, cellular baseband processor 1824 and / or transceiver 1822 of the device 1804 are executed.

[0179] In one example, UE-based positioning can be associated with at least one difference-based positioning method.

[0180] At point 1604, the UE can receive auxiliary data from the network entity, including a virtual anchor list and a VPRU list for UE-based positioning, such as combining... Figure 14 and Figure 15 As described. For example, such as Figure 14 As shown at 1420, UE 1402 can receive auxiliary data 1406 from network entity 1404, wherein auxiliary data 1406 may include a virtual anchor list 1408 and a VPRU list 1410 for UE-based positioning. The component for receiving auxiliary data may be, for example... Figure 18 The positioning component 198, application processor 1806, cellular baseband processor 1824 and / or transceiver 1822 of the device 1804 are executed.

[0181] In one example, each virtual anchor in the list of virtual anchors can correspond to a physical anchor with a position / vector offset.

[0182] In another example, each VPRU in the VPRU list is generated based on at least one Physical Positioning Reference Unit (PPRU), wherein each VPRU in the VPRU list can be associated with a corresponding virtual location in a set of virtual locations.

[0183] At 1610, the UE can use at least one virtual anchor and at least one VPRU from the auxiliary data to perform UE-based positioning, such as combining... Figure 14 As described. For example, such as Figure 14 As shown at 1426, UE 1402 can use at least one virtual anchor and / or at least one VPRU to perform UE-based positioning. The components used to perform UE-based positioning may be, for example... Figure 18 The positioning component 198, application processor 1806, cellular baseband processor 1824 and / or transceiver 1822 of the device 1804 are executed.

[0184] In one example, the UE may send a request to a network entity for the use of a suitable or preferred VPRU, and based on that request, receive auxiliary data including suitable or preferred VPRUs from a VPRU list, such as combining... Figure 14 As described. For example, such as Figure 14 As shown at 1432, UE 1402 may send an indication of a suitable or preferred VPRU to network entity 1404, and network entity 1404 may include the suitable or preferred VPRU in auxiliary data 1406. The components for sending the request and / or for receiving the auxiliary data may be, for example, Figure 18 The positioning component 198, application processor 1806, cellular baseband processor 1824 and / or transceiver 1822 of the device 1804 are executed.

[0185] In another example, the UE can receive a set of measurement or correction data for the VPRU list from a network entity based on the virtual location and virtual anchor list of each VPRU in the VPRU list, such as combining... Figure 17 As described. For example, such as Figure 14 As shown in 1438, UE 1402 can receive a set of measurement or calibration data from VPRU 1412 from network entity 1404. The component used to transmit the indication can be, for example... Figure 14 The positioning component 198, application processor 1806, cellular baseband processor 1824, and / or transceiver 1822 of the device 1804 perform this. In one example, the UE may further perform UE-based positioning based on this set of measurement or correction data.

[0186] Figure 18is a flowchart 1700 of a method of wireless communication. The method can be performed by a UE (e.g., the UE 104, 404, 702, 920, 1302, 1402, 1502; the GNSS device 506; the flow station device 604; the apparatus 1804). The method can enable the UE to perform UE-based positioning with virtual anchors and / or virtual PRUs.

[0187] At 1702, the UE can transmit, to a network entity, an indication to perform UE-based positioning, such as described in connection with Figure 14 At 1704, the UE can receive, from the network entity, assistance data including a list of virtual anchors and a list of VPRUs for UE-based positioning, such as described in connection with Figure 15 At 1704, the UE can receive, from the network entity, assistance data including a list of virtual anchors and a list of VPRUs for UE-based positioning, such as described in connection with Figure 14 The means for transmitting the indication can be executed by, for example, the positioning component 198, the application processor 1806, the cellular baseband processor 1824, and / or the transceiver 1822 of the apparatus 1804 in

[0188] In one example, the UE-based positioning can be associated with at least one difference-based positioning method.

[0189] At 1704, the UE can receive, from the network entity, assistance data including a list of virtual anchors and a list of VPRUs for UE-based positioning, such as described in connection with Figure 18 At 1704, the UE can receive, from the network entity, assistance data including a list of virtual anchors and a list of VPRUs for UE-based positioning, such as described in connection with Figure 14 At 1704, the UE can receive, from the network entity, assistance data including a list of virtual anchors and a list of VPRUs for UE-based positioning, such as described in connection with Figure 14 The means for receiving the assistance data can be executed by, for example, the positioning component 198, the application processor 1806, the cellular baseband processor 1824, and / or the transceiver 1822 of the apparatus 1804 in Figure 18 The means for receiving the assistance data can be executed by, for example, the positioning component 198, the application processor 1806, the cellular baseband processor 1824, and / or the transceiver 1822 of the apparatus 1804 in

[0190] In one example, each virtual anchor in the list of virtual anchors can correspond to a physical anchor with a position / vector offset.

[0191] In another example, each VPRU in the list of VPRUs is generated based on at least one physical positioning reference unit (PPRU), where each VPRU in the list of VPRUs can be associated with a corresponding virtual position in a set of virtual positions.

[0192] At 1710, the UE can perform UE-based positioning using at least one virtual anchor and at least one VPRU in the assistance data, such as described in connection with Figure 14 At 1710, the UE can perform UE-based positioning using at least one virtual anchor and at least one VPRU in the assistance data, such as described in connection with Figure 14As shown at 1426, UE 1402 can use at least one virtual anchor and / or at least one VPRU to perform UE-based positioning. The components used to perform UE-based positioning may be, for example... Figure 18 The positioning component 198, application processor 1806, cellular baseband processor 1824 and / or transceiver 1822 of the device 1804 are executed.

[0193] In one example, at 1706, the UE may send a request to the network entity for the use of a suitable or preferred VPRU, and based on that request, receive auxiliary data including suitable or preferred VPRUs from the VPRU list, such as combining... Figure 18 As described. For example, such as Figure 3 As shown at 1432, UE 1402 may send an indication of a suitable or preferred VPRU to network entity 1404, and network entity 1404 may include the suitable or preferred VPRU in auxiliary data 1406. The components for sending the request and / or for receiving the auxiliary data may be, for example, Figure 19 The positioning component 198, application processor 1806, cellular baseband processor 1824 and / or transceiver 1822 of the device 1804 are executed.

[0194] In another example, at 1708, the UE can receive a set of measurement or correction data for the VPRU list from a network entity based on the virtual location and virtual anchor list of each VPRU in the VPRU list, such as combining... Figure 14 As described. For example, such as Figure 14 As shown in 1438, UE 1402 can receive a set of measurement or calibration data from VPRU 1412 from network entity 1404. The component used to transmit the indication can be, for example... Figure 21 The positioning component 198, application processor 1806, cellular baseband processor 1824, and / or transceiver 1822 of the device 1804 perform this. In one example, the UE may further perform UE-based positioning based on this set of measurement or correction data.

[0195] Figure 14is a diagram 1800 that illustrates an example of a hardware implementation for an apparatus 1804. The apparatus 1804 can be a UE, a component of a UE, or can implement UE functionality. In some aspects, the apparatus 1804 can include a cellular baseband processor 1824 (also referred to as a modem) coupled with one or more transceivers 1822 (e.g., cellular RF transceivers). The cellular baseband processor 1824 can include on-chip memory 1824'. In some aspects, the apparatus 1804 can further include one or more Subscriber Identity Modules (SIM) cards 1820, and an application processor 1806 coupled with a secure digital (SD) card 1808 and a screen 1810. The application processor 1806 can include on-chip memory 1806'. In some aspects, the apparatus 1804 can further include a Bluetooth module 1812, a WLAN module 1814, a SPS module 1816 (e.g., a GNSS module), one or more sensor modules 1818 (e.g., a barometric pressure sensor / altimeter; a motion sensor such as an inertial measurement unit (IMU), a gyroscope, and / or an accelerometer; a light detection and ranging (LIDAR), a radio detection and ranging (RADAR), a sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technology for positioning), an additional memory module 1826, a power source 1830, and / or a camera 1832. The Bluetooth module 1812, the WLAN module 1814, and the SPS module 1816 can include on-chip transceivers (TRXs) (or in some cases, just receivers (RXs)). The Bluetooth module 1812, the WLAN module 1814, and the SPS module 1816 can include their own dedicated antennas and / or communicate using the antennas 1880. The cellular baseband processor 1824 communicates with the UE 104 and / or with a RU associated with the network entity 1802 via the one or more antennas 1880 through the transceiver 1822. The cellular baseband processor 1824 and the application processor 1806 can each include computer-readable media / memory 1824', 1806', respectively. The additional memory module 1826 can also be considered a computer-readable medium / memory. Each computer-readable medium / memory 1824', 1806', 1826 can be non-transitory. The cellular baseband processor 1824 and the application processor 1806 each are responsible for general processing, including the execution of software stored on the computer-readable media / memory. The software, when executed by the cellular baseband processor 1824 / application processor 1806, causes the cellular baseband processor 1824 / application processor 1806 to perform the various functions described supra. The computer-readable media / memory can also be used for storing data that is manipulated by the cellular baseband processor 1824 / application processor 1806 when executing software.The cellular baseband processor 1824 / application processor 1806 can be a component of the UE 350 and can include the memory 360 and / or at least one of the TX processor 368, the RX processor 356, and the controller / processor 359. In one configuration, the apparatus 1804 can be a processor chip (modem and / or application) and only include the cellular baseband processor 1824 and / or the application processor 1806, while in another configuration, the apparatus 1804 can be an entire UE (e.g., see FIG. 3.1) and include the additional modules of the UE 350. Figure 14

[0196] As discussed above, the positioning component 198 can be configured to transmit, to a network entity, an indication to perform UE-based positioning. The positioning component 198 can also be configured to receive, from the network entity, assistance data including a list of virtual anchors and a list of VPRUs for UE-based positioning. The positioning component 198 can also be configured to perform UE-based positioning using at least one virtual anchor and at least one VPRU in the assistance data. The positioning component 198 can be within the cellular baseband processor 1824, the application processor 1806, or both the cellular baseband processor 1824 and the application processor 1806. The positioning component 198 can be one or more hardware components specifically configured to carry out the described processes / algorithms, implemented by one or more processors configured to perform the described processes / algorithms, stored within a computer-readable medium for implementation by one or more processors, or some combination thereof. As shown, the apparatus 1804 can include various components configured for various functions. In one configuration, the apparatus 1804 (and in particular the cellular baseband processor 1824 and / or the application processor 1806) can include means for transmitting, to a network entity, an indication to perform UE-based positioning. The apparatus 1804 can also include means for receiving, from the network entity, assistance data including a list of virtual anchors and a list of VPRUs for UE-based positioning. The apparatus 1804 can also include means for performing UE-based positioning using at least one virtual anchor and at least one VPRU in the assistance data.

[0197] In one configuration, the UE-based positioning can be associated with at least one difference-based positioning method.

[0198] In another configuration, each virtual anchor in the list of virtual anchors can correspond to a physical anchor with a position / vector offset.

[0199] In another configuration, each VPRU in the list of VPRUs is generated based on at least one PPRU, where each VPRU in the list of VPRUs can be associated with a corresponding virtual position in a set of virtual positions.

[0200] ​In another configuration, the apparatus 1804 can further include means for receiving, from the network entity, a set of measurement or correction data for the list of VPRUs based on the virtual location of each VPRU in the list of VPRUs and the list of virtual anchors. In some implementations, the apparatus 1804 can further include means for performing UE-based positioning based further on the set of measurement or correction data.

[0201] In another configuration, the apparatus 1804 can further include means for receiving, from the network entity, a set of measurement or correction data for the list of VPRUs based on the virtual location of each VPRU in the list of VPRUs and the list of virtual anchors. In some implementations, the apparatus 1804 can further include means for performing UE-based positioning based further on the set of measurement or correction data.

[0202] The means can be a positioning component 198 of the apparatus 1804 configured to perform the functions recited by the means. As described above, the apparatus 1804 can include the TX processor 368, the RX processor 356, and the controller / processor 359. Accordingly, in one configuration, the means can be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to perform the functions recited by the means.

[0203] Figure 21 is a flow diagram of a method of wireless communication. The method can be performed by a network entity (e.g., the base station 102; the server 918; the network entity 1304, 1404, 1504, 2102). The method can enable the network entity to generate and configure virtual anchors and / or VPRUs for a UE for UE-based positioning.

[0204] At 1902, the network entity can receive an indication to perform UE-based positioning for a UE, such as described in connection with Figure 14 At 1904, the network entity can generate a list of virtual anchors for the UE, such as described in connection with Figure 14 As shown in 1420 of FIG. 14, the network entity 1404 can receive, from the UE 1402, an indication to perform UE-based positioning. Means for receiving the indication can be performed by, for example, the RU processor 2142 and / or the transceiver 2146 of the network entity 2102 in FIG. 21. Figure 21 The means for receiving the indication can be performed by, for example, the RU processor 2142 and / or the transceiver 2146 of the network entity 2102 in FIG. 21.

[0205] In one example, the UE-based positioning can be associated with at least one difference-based positioning method.

[0206] At 1908, the network entity can configure, for the UE, assistance data including a list of virtual anchors and a list of VPRUs for UE-based positioning, such as described in connection with Figure 8 At 1910, the network entity can transmit the assistance data to the UE, such as described in connection with Figure 14As shown at 1422, network entity 1404 can configure auxiliary data 1406 for UE 1402, wherein auxiliary data 1406 includes a virtual anchor list 1408 and a VPRU list 1410 for UE-based positioning. The components for configuring the auxiliary data can be, for example... Figure 14 The virtual anchor and reference station configuration component 199, RU processor 2142 and / or transceiver 2146 of the network entity 2102 are executed.

[0207] At point 1910, the network entity can send auxiliary data to the UE, including a virtual anchor list and a VPRU list, such as combining... Figure 21 As described. For example, such as Figures 9-11 As shown at 1424, network entity 1404 can send auxiliary data 1406, including virtual anchor list 1408 and VPRU list 1410, to UE 1402. The component for sending the auxiliary data can be, for example... Figure 14 The virtual anchor and reference station configuration component 199, RU processor 2142 and / or transceiver 2146 of the network entity 2102 are executed.

[0208] In one example, a network entity can generate a list of virtual anchors based on the position / vector offset of each physical anchor in a set of physical anchors, such as combining... Figure 14 and Figure 21 As described. For example, such as Figure 13 As shown at 1428, network entity 1404 can generate a virtual anchor list 1408 based on the position / vector offset of each physical anchor in a set of physical anchors. The component used to generate the virtual anchor list can be, for example, Figure 14 The virtual anchor and reference station configuration component 199, RU processor 2142 and / or transceiver 2146 of the network entity 2102 are executed.

[0209] In another example, a network entity may generate a list of VPRUs based on at least one physical location reference unit, wherein each VPRU in the list may be associated with a corresponding virtual location in a set of virtual locations, such as combining... Figure 14 and Figure 21 As described. For example, such as Figure 20 As shown at 1430, network entity 1404 can generate a VPRU list 1410 based on at least one physical PRU, wherein each VPRU can be associated with a corresponding virtual location. The component used to generate the VPRU list can be, for example... Figure 14 The virtual anchor and reference station configuration component 199, RU processor 2142 and / or transceiver 2146 of the network entity 2102 are executed.

[0210] In another example, a network entity may select a list of VPRUs for UE-based positioning based on the corresponding virtual location of each VPRU and the estimated location of the UE. In some implementations, the ratio between a first approximate distance from the estimated location of the UE to the virtual anchor list and a second approximate distance from the estimated location of the UE to the VPRU list may exceed a ratio threshold.

[0211] In another example, the virtual location corresponding to each VPRU in the VPRU list can be pre-assigned or pre-configured. In some implementations, the virtual location of each VPRU may correspond to the intersection of a grid covering a specific area.

[0212] In another example, a network entity may receive a request from a UE to use a suitable or preferred VPRU, and the network entity may configure auxiliary data to include a suitable or preferred VPRU from the VPRU list based on the request.

[0213] In another example, the corresponding virtual location for each VPRU in the VPRU list can be generated based on the estimated location of the UE. In some implementations, network entities may determine the estimated location of the UE based on at least one of the following: the serving cell ID associated with the UE, the serving beam ID associated with the UE, the ECID associated with the UE, the previous location estimate of the UE, the location reported by the UE, the SL area ID associated with the UE, or the RAN-independent location estimate of the UE.

[0214] In another example, a network entity can generate a set of measurement or correction data for the VPRU list based on the virtual location and virtual anchor list of each VPRU in the VPRU list, and the network entity can send this set of measurement or correction data to the UE for UE-based positioning, such as combining... Figure 14 and Figure 21 As described. For example, such as Figure 14 As shown in 1436, network entity 1404 can generate a set of measurement or calibration data for VPRU 1412 based on the virtual location of VPRU 1412 and the virtual locations of one or more virtual anchors. The component used to generate the set of measurement or calibration data can be, for example... Figure 14 The virtual anchor and reference station configuration component 199, RU processor 2142 and / or transceiver 2146 of the network entity 2102 are executed.

[0215] In one example, the set of measurement or correction data may be further generated based on one or more error sources, including at least one of the following: anchor clock bias, group delay, atmospheric effects or delay, non-line-of-sight (NLOS) effects, or at least one environmental effect. In some implementations, network entities may estimate or track one or more error sources based on raw measurements received from a set of physical PRUs. In some implementations, network entities may broadcast one or more error sources based on OSR or SSR formats.

[0216] Figure 21 This is a flowchart 2000 of a wireless communication method. This method can be performed by a network entity (e.g., base station 102; server 918; network entities 1304, 1404, 1504, 2102). This method enables the network entity to generate and configure virtual anchors and / or VPRUs for UE-based positioning.

[0217] At 2002, network entities can receive instructions to perform UE-based positioning for the UE, such as combining Figure 14 As described. For example, such as Figure 14 As shown at 1420, network entity 1404 can receive an instruction from UE 1402 to perform UE-based positioning. The component for receiving the instruction may be, for example... Figure 21 The virtual anchor and reference station configuration component 199, RU processor 2142 and / or transceiver 2146 of the network entity 2102 are executed.

[0218] In one example, UE-based positioning can be associated with at least one difference-based positioning method.

[0219] In 2008, network entities could configure auxiliary data for UEs, including virtual anchor lists and VPRU lists for UE-based positioning, such as combining... Figure 8 As described. For example, such as Figure 14 As shown at 1422, network entity 1404 can configure auxiliary data 1406 for UE 1402, wherein auxiliary data 1406 includes a virtual anchor list 1408 and a VPRU list 1410 for UE-based positioning. The components for configuring the auxiliary data can be, for example... Figure 14 The virtual anchor and reference station configuration component 199, RU processor 2142 and / or transceiver 2146 of the network entity 2102 are executed.

[0220] In 2010, network entities could send auxiliary data to the UE, including virtual anchor lists and VPRU lists, such as combining... Figure 21 As described. For example, such as Figures 9-11As shown at 1424, network entity 1404 can send auxiliary data 1406, including virtual anchor list 1408 and VPRU list 1410, to UE 1402. The component for sending the auxiliary data can be, for example... Figure 14 The virtual anchor and reference station configuration component 199, RU processor 2142 and / or transceiver 2146 of the network entity 2102 are executed.

[0221] In one example, at 2004, a network entity can generate a list of virtual anchors based on the position / vector offset of each physical anchor in a set of physical anchors, such as combining... Figure 14 and Figure 21 As described. For example, such as Figure 13 As shown at 1428, network entity 1404 can generate a virtual anchor list 1408 based on the position / vector offset of each physical anchor in a set of physical anchors. The component used to generate the virtual anchor list can be, for example, Figure 14 The virtual anchor and reference station configuration component 199, RU processor 2142 and / or transceiver 2146 of the network entity 2102 are executed.

[0222] In another example, at 2006, a network entity may generate a list of VPRUs based on at least one physical location reference unit, wherein each VPRU in the list may be associated with a corresponding virtual location in a set of virtual locations, such as combining... Figure 14 and Figure 21 As described. For example, such as Figure 21 As shown at 1430, network entity 1404 can generate a VPRU list 1410 based on at least one physical PRU, wherein each VPRU can be associated with a corresponding virtual location. The component used to generate the VPRU list can be, for example... ​ The virtual anchor and reference station configuration component 199, RU processor 2142 and / or transceiver 2146 of the network entity 2102 are executed.

[0223] In one example, a network entity may select a list of VPRUs for UE-based positioning based on the corresponding virtual location of each VPRU and the estimated location of the UE. In some implementations, the ratio between a first approximate distance from the estimated location of the UE to the virtual anchor list and a second approximate distance from the estimated location of the UE to the VPRU list may exceed a ratio threshold.

[0224] In another example, the virtual location corresponding to each VPRU in the VPRU list can be pre-assigned or pre-configured. In some implementations, the virtual location of each VPRU may correspond to the intersection of a grid covering a specific area.

[0225] In another example, a network entity may receive a request from a UE to use a suitable or preferred VPRU, and the network entity may configure auxiliary data to include a suitable or preferred VPRU from the VPRU list based on the request.

[0226] In another example, the corresponding virtual location for each VPRU in the VPRU list can be generated based on the estimated location of the UE. In some implementations, network entities may determine the estimated location of the UE based on at least one of the following: the serving cell ID associated with the UE, the serving beam ID associated with the UE, the ECID associated with the UE, the previous location estimate of the UE, the location reported by the UE, the SL area ID associated with the UE, or the RAN-independent location estimate of the UE.

[0227] In another example, at 2012, a network entity can generate a set of measurement or correction data for the VPRU list based on the virtual location and virtual anchor list of each VPRU in the VPRU list, and the network entity can send this set of measurement or correction data to the UE for UE-based positioning, such as combining... ​ and ​ As described. For example, such as ​ As shown in 1436, network entity 1404 can generate a set of measurement or calibration data for VPRU 1412 based on the virtual location of VPRU 1412 and the virtual locations of one or more virtual anchors. The component used to generate the set of measurement or calibration data can be, for example... ​ The virtual anchor and reference station configuration component 199, RU processor 2142 and / or transceiver 2146 of the network entity 2102 are executed.

[0228] In one example, the set of measurement or correction data may be further generated based on one or more error sources, including at least one of the following: anchor clock bias, group delay, atmospheric effects or delay, non-line-of-sight (NLOS) effects, or at least one environmental effect. In some implementations, network entities may estimate or track one or more error sources based on raw measurements received from a set of physical PRUs. In some implementations, network entities may broadcast one or more error sources based on an observation space representation (OSR) format or a state space representation (SSR) format.

[0229] ​is a diagram 2100 that is an example of a hardware implementation for an example network entity 2102. The network entity 2102 can be a BS, a component of a BS, or can implement BS functionality. The network entity 2102 can include at least one of a CU 2110, a DU 2130, or a RU 2140. For example, depending on the layer functionality handled by the virtual anchor and reference station configuration component 199, the network entity 2102 can include the CU 2110; both the CU 2110 and the DU 2130; each of the CU 2110, the DU 2130, and the RU 2140; the DU 2130; both the DU 2130 and the RU 2140; or the RU 2140. The CU 2110 can include a CU processor 2112. The CU processor 2112 can include on-chip memory 2112'. In some aspects, the CU 2110 can also include an additional memory module 2114 and a communication interface 2118. The CU 2110 communicates with the DU 2130 over a backhaul link, such as an Fl interface. The DU 2130 can include a DU processor 2132. The DU processor 2132 can include on-chip memory 2132'. In some aspects, the DU 2130 can also include an additional memory module 2134 and a communication interface 2138. The DU 2130 communicates with the RU 2140 over a front-haul link. The RU 2140 can include a RU processor 2142. The RU processor 2142 can include on-chip memory 2142'. In some aspects, the RU 2140 can also include an additional memory module 2144, one or more transceivers 2146, antennas 2180, and a communication interface 2148. The RU 2140 communicates with the UE 104. The on-chip memories 2112', 2132', 2142' and the additional memory modules 2114, 2134, 2144 can each be considered a computer- readable medium / memory. Each computer-readable medium / memory can be non-transitory. Each of the processors 2112, 2132, 2142 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory. The software, when executed by the corresponding processor, causes the processor to perform the various functions described supra. The computer-readable medium / memory can also be used for storing data that is manipulated by the processor when executing software.

[0230] As discussed above, the virtual anchor and reference station configuration component 199 can be configured to receive an indication to perform UE-based positioning for a UE. The virtual anchor and reference station configuration component 199 can also be configured to configure the UE with assistance data including a list of virtual anchors and a list of VPRUs for UE-based positioning. The virtual anchor and reference station configuration component 199 can also be configured to transmit the assistance data including the list of virtual anchors and the list of VPRUs to the UE. The virtual anchor and reference station configuration component 199 can be within one or more processors of one or more of the CU 2110, the DU 2130, and the RU 2140. The virtual anchor and reference station configuration component 199 can be one or more hardware components specifically configured to perform the described processes / algorithms, implemented by one or more processors configured to perform the described processes / algorithms, stored within a computer-readable medium for implementation by one or more processors, or some combination thereof. The network entity 2102 can include a variety of components configured for various functions. In one configuration, the network entity 2102 can include means for receiving an indication to perform UE-based positioning for a UE. The network entity 2102 can also include means for configuring the UE with assistance data including a list of virtual anchors and a list of VPRUs for UE-based positioning. The network entity 2102 can also include means for transmitting the assistance data including the list of virtual anchors and the list of VPRUs to the UE.

[0231] In one configuration, the UE-based positioning can be associated with at least one difference-based positioning method.

[0232] In another configuration, the network entity 2102 can also include means for generating the list of virtual anchors based on a position / vector offset of each physical anchor in a set of physical anchors.

[0233] In another configuration, the network entity 2102 can also include means for generating the list of VPRUs based on at least one physical positioning reference unit, where each VPRU in the list of VPRUs can be associated with a corresponding virtual position in a set of virtual positions.

[0234] In another configuration, the network entity 2102 can also include means for selecting the list of VPRUs for UE-based positioning based on the corresponding virtual position of each VPRU and an estimated position of the UE. In some implementations, a ratio between a first approximate distance from the estimated position of the UE to the list of virtual anchors and a second approximate distance from the estimated position of the UE to the list of VPRUs can exceed a ratio threshold.

[0235] In another configuration, the corresponding virtual position of each VPRU in the list of VPRUs can be pre-assigned or pre-configured. In some implementations, the virtual position of each VPRU can correspond to an intersection of a grid covering a particular area.

[0236] In another configuration, the network entity 2102 can also include means for receiving, from a UE, a request to use a suitable or preferred VPRU, and means for configuring the assistance data to include a suitable or preferred VPRU in the VPRU list based on the request.

[0237] In another configuration, a corresponding virtual location for each VPRU in the VPRU list can be generated based on an estimated location of the UE. In some implementations, the network entity 2102 can also include means for determining the estimated location of the UE based on at least one of: a serving cell ID associated with the UE, a serving beam ID associated with the UE, an ECID associated with the UE, a previous location estimate of the UE, a location reported by the UE, a SL area ID associated with the UE, or a RAN-independent location estimate of the UE.

[0238] In another configuration, the network entity 2102 can also include means for generating a set of measurement or correction data for the VPRU list based on the virtual locations for each VPRU in the VPRU list and the list of virtual anchors, and means for transmitting the set of measurement or correction data to the UE for use in positioning of the UE.

[0239] In another configuration, the set of measurement or correction data can be further generated based on one or more error sources including at least one of: anchor clock bias, group delay, atmospheric effects or delays, NLOS effects, or at least one environmental effect. In some implementations, the network entity 2102 can also include means for estimating or tracking the one or more error sources based on raw measurements received from a set of physical PRUs. In some implementations, the network entity 2102 can also include means for broadcasting the one or more error sources based on an OSR format or an SSR format.

[0240] The means can be a virtual anchor and reference station configuration component 199 of the network entity 2102 configured to perform the functions recited by the means. As described above, the network entity 2102 can include the TX processor 316, the RX processor 370, and the controller / processor 375. In one configuration, the means can therefore be the TX processor 316, the RX processor 370, and / or the controller / processor 375 configured to perform the functions recited by the means.

[0241] It should be understood that the particular order or hierarchy of steps in the processes / flow diagrams disclosed are merely examples. It should be appreciated that a particular order or hierarchy of steps in the processes / flow diagrams can be re-arranged based on design choices. Furthermore, some steps can be optional. The accompanying method claims present elements of the various steps in a sample order, and are not limited to the specific order or hierarchy presented.

[0242] The preceding description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein can be applied to other aspects. Thus, the claims are not to be limited to the aspects described herein, but are to be given the full scope defined by the language of the claims. References to singular include plural unless otherwise noted herein. References to “if” include “when” unless otherwise noted herein. That is, any forms of words that convey the idea of possibility or contingency, such as “if,” “when,” and “while,” are not intended to imply that the future occurrence of anything is certain. Rather, the words are simply used to convey an idea of possibility or contingency. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects. Unless specifically stated otherwise, the term “some” refers to one or more. Combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of the group consisting of A, B, and C,” “one or more of the group consisting of A, B, and C,” and “A, B, and / or C” include the entire group of A, B, and / or C and any combination thereof. Specifically, combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of the group consisting of A, B, and C,” “one or more of the group consisting of A, B, and C,” and “A, B, and / or C” can be A only, B only, C only, A and B, A and C, B and C, or A and B and C, where any such combination can contain one or more members. A set shall be interpreted as including a single element that can serve multiple purposes in the application. Accordingly, a set of Xs can include one or more Xs. If a first device receives data or sends data to a second device, the data can be received / sent directly between the first device and the second device, or indirectly through a set of devices between the first device and the second device. A device configured to “output” data (such as a transmission, signal, or message) may, for example, send the data with a transceiver, or can transfer the data to a device that sends the data. A device configured to “obtain” data (such as a transmission, signal, or message) may, for example, receive the data with a transceiver, or can obtain the data from a device that receives the data. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims.Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly identified in the claims. A phrase such as “a means for” can not be a substitute for the word “a component” or “a device.” Thus, no claim element can be construed as a means plus function unless the element is expressly recited using the phrase “means for” and there is no disclaimer of such claim element.

[0243] As used herein, the phrase “based on” shall not be construed as a surrender of information, condition, factor, or the like that is not part of the set. In other words, the phrase “based on A” (where A can be information, condition, factor, or the like) shall be interpreted as “based, at least in part, on A” unless specifically stated otherwise.

[0244] The following aspects are merely exemplary and can be combined with other aspects or teachings described herein without limitation.

[0245] Aspect 1 is a method of wireless communication at a network entity, the method comprising: receiving an indication to perform a UE-based positioning for a UE; configuring assistance data for the UE comprising a list of virtual anchors and a list of VPRUs for the UE-based positioning; and transmitting the assistance data comprising the list of virtual anchors and the list of VPRUs to the UE.

[0246] Aspect 2 is the method of aspect 1, further comprising: generating the list of virtual anchors based on a location offset of each physical anchor in a set of physical anchors.

[0247] Aspect 3 is the method of aspect 1 or 2, further comprising: generating the list of VPRUs based on at least one physical positioning reference unit (PPRU), wherein each VPRU in the list of VPRUs is associated with a corresponding virtual location in a set of virtual locations.

[0248] Aspect 4 is the method of aspect 3, further comprising: selecting the list of VPRUs for the UE-based positioning based on the corresponding virtual location of each VPRU and an estimated location of the UE.

[0249] Aspect 5 is the method of aspect 4, wherein a ratio between a first approximate distance from the estimated location of the UE to the list of virtual anchors and a second approximate distance from the estimated location of the UE to the list of VPRUs exceeds a ratio threshold.

[0250] Aspect 6 is the method of aspect 3, wherein the corresponding virtual location of each VPRU in the list of VPRUs is pre-assigned or pre-configured.

[0251] Aspect 7 is the method of aspect 6, wherein the virtual position of each VPRU corresponds to an intersection of a grid covering a particular area.

[0252] Aspect 8 is the method of aspect 3, further comprising: receiving a request from the UE to use a suitable VPRU; and configuring the assistance data to include the suitable VPRU of the list of VPRUs based on the request.

[0253] Aspect 9 is the method of aspect 3, wherein the corresponding virtual position of each VPRU of the list of VPRUs is generated based on an estimated position of the UE.

[0254] Aspect 10 is the method of aspect 9, further comprising: determining the estimated position of the UE based on at least one of: a serving cell ID associated with the UE, a serving beam ID associated with the UE, an ECID associated with the UE, a previous position estimate of the UE, a position reported by the UE, a SL area ID associated with the UE, or a RAN-independent position estimate of the UE.

[0255] Aspect 11 is the method of any of aspects 1-10, further comprising: generating a set of measurement or correction data for the list of VPRUs based on a virtual position of each VPRU of the list of VPRUs and the list of virtual anchors; and transmitting the set of measurement or the correction data to the UE for use in the UE-based positioning.

[0256] Aspect 12 is the method of aspect 11, wherein the set of measurement or the correction data is further generated based on one or more error sources, including at least one of: an anchor clock bias, a group delay, an atmospheric effect or delay, an NLOS effect, or at least one environmental effect.

[0257] Aspect 13 is the method of aspect 12, further comprising: estimating or tracking the one or more error sources based on raw measurements received from a set of physical PRUs.

[0258] Aspect 14 is the method of aspect 12, further comprising: broadcasting the one or more error sources based on an OSR format or an SSR format.

[0259] Aspect 15 is the method of any of aspects 1-14, wherein the network entity is a location server or an LMF, and wherein the indication is received from the UE or a base station serving the UE.

[0260] Aspect 16 is the method of any one of aspects 1-15, wherein the UE-based positioning is associated with at least one differential-based positioning method.

[0261] Aspect 17 is an apparatus for wireless communication at a network entity, comprising a memory; and at least one processor coupled to the memory and configured to implement any of aspects 1-16 based at least in part on information stored in the memory.

[0262] Aspect 18 is the apparatus of aspect 17, further comprising at least one of a transceiver or an antenna coupled to the at least one processor.

[0263] Aspect 19 is an apparatus for wireless communication, comprising means for implementing any of aspects 1-16.

[0264] Aspect 20 is a computer-readable medium (for example, a non-transitory computer- readable medium) storing computer executable code, where the code when executed by a processor causes the processor to implement any of aspects 1-16.

[0265] Aspect 21 is a method of wireless communication at a UE, comprising sending an indication to a network entity to perform UE-based positioning; receiving assistance data from the network entity including a list of virtual anchors and a list of VPRUs for the UE-based positioning; and performing the UE-based positioning using at least one virtual anchor and at least one VPRU in the assistance data.

[0266] Aspect 22 is the method of aspect 21, wherein each virtual anchor in the list of virtual anchors corresponds to a physical anchor with a location offset.

[0267] Aspect 23 is the method of aspect 21 or 22, wherein each VPRU in the list of VPRUs is generated based on at least one physical positioning reference unit, wherein each VPRU in the list of VPRUs is associated with a corresponding virtual location in a set of virtual locations.

[0268] Aspect 24 is the method of any of aspects 21-23, further comprising sending a request to the network entity to use a suitable VPRU; and receiving the assistance data including the suitable VPRU in the list of VPRUs based on the request.

[0269] Aspect 25 is the method of any of aspects 21 to 24, further comprising: receiving, from the network entity, a set of measurement or correction data for the list of VPRUs based on a virtual location of each VPRU in the list of VPRUs and the list of virtual anchors.

[0270] Aspect 26 is the method of aspect 25, further comprising: performing the UE-based positioning further based on the set of measurement or correction data.

[0271] Aspect 27 is the method of any of aspects 21 to 26, wherein the UE-based positioning is associated with at least one difference-based positioning method.

[0272] Aspect 28 is an apparatus for wireless communication at a UE, comprising: a memory; and at least one processor coupled to the memory and configured to implement any of aspects 21 to 27 based at least in part on information stored in the memory.

[0273] Aspect 29 is the apparatus of aspect 28, further comprising: at least one of a transceiver or an antenna coupled to the at least one processor.

[0274] Aspect 30 is an apparatus for wireless communication, comprising: means for implementing any of aspects 21 to 27.

[0275] Aspect 31 is a computer-readable medium (for example, a non-transitory computer- readable medium) storing computer executable code, where the code when executed by a processor causes the processor to implement any of aspects 21 to 27.

Claims

1. An apparatus for wireless communication at a network entity, the apparatus comprising: a transceiver; a memory; and at least one processor coupled to the transceiver and the memory and configured to: receive, via the transceiver, an indication to perform a user equipment (UE)-based positioning for a UE; configure the UE with assistance data including a list of virtual anchors and a list of virtual positioning reference units (VPRUs) for the UE-based positioning; and transmit, via the transceiver, the assistance data including the list of virtual anchors and the list of VPRUs.

2. The apparatus of claim 1, wherein the at least one processor is further configured to: generate the list of virtual anchors based on a location offset of each physical anchor in a set of physical anchors.

3. The apparatus of claim 1, wherein the at least one processor is further configured to: generate the list of VPRUs based on at least one physical positioning reference unit (PPRU), wherein each VPRU in the list of VPRUs is associated with a corresponding virtual location in a set of virtual locations.

4. The apparatus of claim 3, wherein the at least one processor is further configured to: select the list of VPRUs for the UE-based positioning based on the corresponding virtual location of each VPRU and an estimated location of the UE.

5. The apparatus of claim 4, wherein a ratio between a first approximate distance from the estimated location of the UE to the list of virtual anchors and a second approximate distance from the estimated location of the UE to the list of VPRUs exceeds a ratio threshold.

6. The apparatus of claim 3, wherein the corresponding virtual location of each VPRU in the list of VPRUs is pre-assigned or pre-configured.

7. The apparatus of claim 6, wherein the virtual location of each VPRU corresponds to an intersection of a grid covering a particular area.

8. The apparatus of claim 3, wherein the at least one processor is further configured to: receive a request to use a suitable VPRU; and configure the assistance data to include the suitable VPRU in the list of VPRUs based on the request.

9. The apparatus of claim 3, wherein the corresponding virtual location of each VPRU in the list of VPRUs is generated based on an estimated location of the UE.

10. The apparatus of claim 9, wherein the at least one processor is further configured to: determine the estimated location of the UE based on at least one of: a serving cell identification (ID) associated with the UE, a serving beam ID associated with the UE, an enhanced cell ID (ECID) associated with the UE, a previous location estimate of the UE, a location reported by the UE, a sidelink (SL) zone ID associated with the UE, or a radio access network (RAN)-independent location estimate of the UE. ​ 11. The apparatus of claim 1, wherein the at least one processor is further configured to: generate a set of measurement or correction data for the list of VPRUs based on a virtual position of each VPRU in the list of VPRUs and the list of virtual anchors; and send the set of measurements or the correction data for use in the UE-based positioning.

12. The apparatus of claim 11, wherein the set of measurements or the correction data is further generated based on one or more error sources comprising at least one of: an anchor clock bias, a group delay, an atmospheric effect or delay, a non-line-of-sight (NLOS) effect, or at least one environmental effect.

13. The apparatus of claim 12, wherein the at least one processor is further configured to: estimate or track the one or more error sources based on raw measurements received from a set of physical PRUs.

14. The apparatus of claim 12, wherein the at least one processor is further configured to: broadcast the one or more error sources based on an observation space representation (OSR) format or a state space representation (SSR) format.

15. A method of wireless communication at a network entity, the method comprising: receiving an indication to perform UE-based positioning for a user equipment (UE); configuring the UE with assistance data comprising a list of virtual anchors and a list of virtual positioning reference units (VPRUs) for the UE-based positioning; and sending the assistance data comprising the list of virtual anchors and the list of VPRUs.

16. The method of claim 15, further comprising: generating the list of virtual anchors based on a position offset of each physical anchor in a set of physical anchors.

17. The method of claim 15, further comprising: generating the list of VPRUs based on at least one physical positioning reference unit (PPRU), wherein each VPRU in the list of VPRUs is associated with a corresponding virtual position in a set of virtual positions.

18. The method of claim 17, further comprising: selecting the list of VPRUs for the UE-based positioning based on the corresponding virtual position of each VPRU and an estimated position of the UE.

19. The method of claim 17, further comprising: receiving a request to use a suitable VPRU; and configuring the assistance data to include the suitable VPRU in the list of VPRUs based on the request.

20. The method of claim 15, further comprising: generating a set of measurement or correction data for the list of VPRUs based on a virtual position of each VPRU in the list of VPRUs and the list of virtual anchors; and sending the set of measurements or the correction data for use in the UE-based positioning.

21. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: a transceiver; a memory; and a processor configured to: ​ ​ at least one processor coupled to the transceiver and the memory, and configured to: transmit, via the transceiver, an indication to perform UE-based positioning to a network entity; receive, via the transceiver, assistance data from the network entity including a list of virtual anchors and a list of virtual positioning reference units (VPRUs) for the UE-based positioning; and perform the UE-based positioning using at least one virtual anchor and at least one VPRU in the assistance data.

22. The apparatus of claim 21, wherein each virtual anchor in the list of virtual anchors corresponds to a physical anchor with a location offset.

23. The apparatus of claim 21, wherein each VPRU in the list of VPRUs is generated based on at least one physical positioning reference unit (PPRU), wherein each VPRU in the list of VPRUs is associated with a corresponding virtual location in a set of virtual locations.

24. The apparatus of claim 21, wherein the at least one processor is further configured to: transmit, to the network entity, a request to use a suitable VPRU; and receive, based on the request, the assistance data including the suitable VPRU in the list of VPRUs.

25. The apparatus of claim 21, wherein the at least one processor is further configured to: receive, from the network entity, a set of measurement or correction data for the list of VPRUs based on a virtual location of each VPRU in the list of VPRUs and the list of virtual anchors.

26. The apparatus of claim 25, wherein the at least one processor is further configured to: perform the UE-based positioning further based on the set of measurements or the correction data.

27. A method of wireless communication at a user equipment (UE), the method comprising: transmitting, to a network entity, an indication to perform UE-based positioning; receiving, from the network entity, assistance data including a list of virtual anchors and a list of virtual positioning reference units (VPRUs) for the UE-based positioning; and performing the UE-based positioning using at least one virtual anchor and at least one VPRU in the assistance data.

28. The method of claim 27, wherein each virtual anchor in the list of virtual anchors corresponds to a physical anchor with a location offset.

29. The method of claim 27, wherein each VPRU in the list of VPRUs is generated based on at least one physical positioning reference unit (PPRU), wherein each VPRU in the list of VPRUs is associated with a corresponding virtual location in a set of virtual locations.

30. The method of claim 27, further comprising: transmitting, to the network entity, a request to use a suitable VPRU; and receiving, based on the request, the assistance data including the suitable VPRU in the list of VPRUs.

31. The method of claim 27, further comprising: ​ receive, from the network entity, a set of measurement or correction data for the list of VPRUs based on the virtual location of each VPRU in the list of VPRUs and the list of virtual anchors.

32. The method of claim 31, further comprising: performing the UE-based positioning further based on the set of measurements or the correction data.

Images