DISTANCE-BASED PRIORITY FOR UPLINK AND DOWNLINK POSITIONING RESOURCES

Abstract

Various techniques for wireless communications are disclosed. In an aspect, a user equipment (UE) may receive, from a network entity, first information identifying a positioning reference signal (PRS) source. The UE may receive, from a base station, second information identifying a voice reference signal (SRS) source. The UE may select, from the PRS sources identified by the first information, a PRS source that satisfies PRS-SRS proximity requirements in relation to at least one SRS source identified by the second information. The UE may use the selected PRS source to perform at least one UE Rx-Tx measurement. In another aspect, the network entity may transmit, to the UE, first information identifying the PRS source. The network entity may transmit, to the UE, second information specifying a plurality of PRS sources to be used by the UE to perform at least one UE Rx-Tx measurement.

Description

Description PRIORITIZATION OF UPLINK AND DOWNLINK POSITIONING SOURCES BASED ON PROXIMITY CROSS REFERENCE WITH RELATED APPLICATIONS This Patent Application claims priority to Indian Patent Application No. 202021045013, titled “PRIORITIZATION OF PROXIMITY BASED UPLINK AND DOWNLINK POSITIONING SOURCES, filed October 15, 2020, which is assigned to the assignee and is expressly incorporated herein by reference in its entirety. Invention Engineering Field The disclosure aspects generally relate to wireless positioning. Background of the Invention Wireless communication systems have evolved through various generations, including first-generation (1G) analog wireless telephone services, second-generation (2G) digital wireless telephone services (including 2.5G and 2.75G interim networks), third-generation (3G) high-speed data, Internet-enabled wireless services, and fourth-generation (4G) services (e.g., Long Term Evolution (LTE) or WiMax). There are currently many types of wireless communication systems in use, including mobile and personal communication services (PCS) systems. Examples of well-known cellular systems include the advanced analog cellular telephone system (AMPS), and digital cellular systems based on code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), the Global System for Mobile communications (GSM), and so on. The fifth-generation (5G) wireless standard, referred to as New Radio (NR), requires higher data transfer rates, a greater number of connections, and better coverage, among other improvements. The 5G standard, developed by the Next Generation Mobile Networks Alliance, is designed to deliver data rates of several tens of megabits per second for each of tens of thousands of users, with 1 gigabit per second for dozens of workers on an office floor. Several hundred thousand simultaneous connections must be supported to support large sensor deployments. As a result, the spectral efficiency of 5G mobile communications must be significantly improved compared to the current 4G standard. Furthermore, signaling efficiency must be improved and latency must be substantially reduced compared to the current standard. Brief Description of the Invention The following presents a simplified summary relating to one or more of the aspects disclosed herein. Accordingly, the following summary should not be construed as a comprehensive overview relating to all of the aspects contemplated, and the following summary should not be relied upon to identify key or critical elements relating to all of the aspects contemplated or to delineate the scope relating to any particular aspect. Therefore, the following summary has the sole purpose of presenting certain concepts relating to one or more aspects relating to the mechanisms disclosed herein in a simplified form to precede the detailed description presented below. In an aspect, a method of wireless communication performed by a user equipment (UE) includes receiving, from a network entity, first information identifying a positioning reference signal (PRS) source; receiving, from a base station, second information identifying a voice reference signal (SRS) source; selecting, from the PRS sources identified by the first information, a PRS source that satisfies PRS-SRS proximity requirements in relation to at least one SRS source identified by the second information; and using the selected PRS source to perform at least one UE Rx-Tx measurement. In an aspect, a wireless communication method performed by a network entity includes transmitting, to a user equipment (UE), first information identifying a positioning reference signal (PRS) source; and transmitting, to the UE, second information specifying a plurality of PRS sources to be used by the UE at least to perform UE Rx-Tx measurements. In an aspect, a user equipment (UE) includes memory; at least one transceiver; and at least one processor communicatively coupled to the memory and at least one transceiver, the at least one processor being configured to: receive, via the at least one transceiver, from a network entity, first information identifying a positioning reference signal (PRS) source; receive, via the at least one transceiver, from a base station, second information identifying a voice reference signal (SRS) source; select, from the PRS sources identified by the first information, a PRS source that satisfies PRS-SRS proximity requirements in relation to the at least one SRS source identified by the second information; and use the selected PRS source to perform UE Rx-Tx measurements. In an aspect, the network entity includes a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and at least one transceiver, the at least one processor being configured to: transmit, via the at least one transceiver, to a user equipment (UE), first information identifying a positioning reference signal (PRS) source; and transmit, via the at least one transceiver, to the UE, second information specifying a plurality of PRS sources to be used by the UE at least to perform UE Rx-Tx measurements. The objects and other advantages relating to the aspects disclosed herein will be apparent to those skilled in the art from the accompanying drawings and descriptions. Short Description of Image The accompanying figures are provided to assist in the description of examples of one or more aspects of the subject matter disclosed and are provided solely for illustrative purposes and not as a limitation thereof: Figure 1 illustrates an exemplary wireless communication system, based on various aspects. Figures 2A and 2B illustrate examples of wireless network structures, based on various aspects. Figures 3A, 3B, and 3C are simplified block diagrams of some example aspects of components that may be used in user equipment (UE), base stations, and network entities, respectively, and configured to support communications as taught herein. Figures 4A and 4B are diagrams depicting examples of frame structures and channels within a frame structure, based on the disclosure aspects. Figure 5 shows an example scenario where the PRS opportunity has a different period than the SRS opportunity. Figure 6 illustrates the proximity-based priority matching method of UL and DL positioning sources based on the disclosure aspects. Figure 7A, Figure 7B, Figure 7C, Figure 7D, and Figs 7E is a flowchart showing a portion of an example process relating to proximity-based prioritization of uplink and downlink position sources in accordance with an aspect of the present disclosure. Figure 8 is a flowchart in another example process related to determining the priority of uplink and downlink sources based on proximity based on the disclosure aspects. Complete Description of the Invention Aspects of the disclosure are presented in the following description and related figures, referring to various examples provided for illustrative purposes. Alternative aspects may be designed without departing from the scope of the disclosure. In addition, well-known elements of the disclosure will not be described in detail or will be omitted so as not to obscure the details of the relevant disclosure. To overcome the technical disadvantages of the conventional systems and methods described above, a mechanism by which the bandwidth used by the user equipment (UE) for the positioning reference signal (PRS) can be dynamically adjusted, e.g., in response to environmental conditions, is presented. For example, the receiving UE can indicate the environmental conditions in which the UE operates to the sending entity, and in response the sending entity can adjust the PRS bandwidth. The terms "equivalent" and "example" are used herein to mean serving as examples, instances, or illustrations. Any aspect described herein as equivalent or exemplary should not be construed as preferable or more advantageous than any other aspect. Similarly, the term "aspect of the disclosure" does not require that all aspects of the disclosure include the features, advantages, or modes of operation discussed. Those skilled in the art will appreciate that the information and signals described below can be represented using any of a variety of different technologies and techniques. For example, the data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the description below can be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof, depending in part on the particular application, in part on the desired design, in part on the appropriate technology, and so on. Further, many aspects are described in terms of sequences of actions to be performed by, for example, elements of a computing device. It will be noted that the various actions described herein may be performed by particular circuits (for example, application-specific integrated circuits (ASICs)), by program instructions executed by one or more processors, or by a combination of both. In addition, the sequences of actions described herein may be considered to be embodied entirely in any form of non-transitory computer-readable storage medium that has stored therein a suitable set of computer instructions that, upon execution, will cause or instruct the processors of the device to perform the functions described herein. Thus, various aspects of the disclosure may be embodied in several different forms, all of which are considered to be within the scope of the claimed subject matter.Additionally, for each aspect described herein, the corresponding form of each such aspect may be described herein as, for example, the logic configured to perform the described actions. As used herein, the terms user equipment (UE) and base station are not intended to be specific or limited to a particular radio access technology (RAT), unless otherwise stated. In general, a UE can be any wireless communications device (e.g., a mobile phone, router, tablet computer, laptop computer, tracking device, wearable device (e.g., smart watch, glasses, augmented reality (AR) / virtual reality (VR) headset, etc.), vehicle (e.g., a car, motorcycle, bicycle, etc.), Internet of Things (IoT) device, etc.) used by a user to communicate over a wireless communications network. A UE may be mobile or may (e.g., at certain times) be stationary, and may communicate with a radio access network (RAN).As used herein, the term UE may be referred to interchangeably as access terminal or AT, client device, wireless device, subscriber device, subscriber terminal, and subscriber station, user terminal (UT), mobile device, mobile terminal, mobile station, or variations thereof. Generally, a UE can communicate with the core network via the RAN, and through the core network, the UE can connect to external networks such as the Internet and to other UEs. Of course, other mechanisms for connecting to the core network, to the Internet, or to both are also possible for a UE, such as a wired access network, a wireless local area network (WLAN) (for example, based on IEEE 802.11, and so on) and so on. A base station can operate according to one of several RATs in communication with the UE depending on the network in which it is used, and may be referred to as an access point (AP), network node, NodeB, evolved NodeB (eNB), next generation eNB (ngeNB), New Radio (NR) Node B (also referred to as gNB or gNodeB), etc. The base station may be used primarily to support wireless access by the UE, including supporting data, voice, signaling connections, or various combinations thereof for supported UEs. In some systems the base station may provide pure edge node signaling functions while in other systems it may provide additional control functions, network management functions, or both. The communication link over which the UE can send signals to the base station is called an uplink channel (UL) (for example, a reverse traffic channel, a reverse control channel, an access channel, etc.).The communication link through which the base station can send signals to the UE is called the downlink channel (DL) or forward link (for example, numbering channel, control channel, broadcast channel, forward traffic channel, and so on). As used herein, the term traffic channel (TCH) can refer to either the uplink / backward or downlink / forward traffic channel. The term base station may refer to a single physical transmit-receive point (TRP) or to multiple physical TRPs that may or may not be co-located. For example, where the term base station refers to a single physical TRP, the physical TRP may be the base station antennas corresponding to the base station's cell (or multiple cell sectors). Where the term base station refers to multiple co-located physical TRPs, the physical TRP may be the antenna array (for example, as in a multiple-input multiple-output (MIMO) system or where the base station uses beamforming) of the base station. Where the term base station refers to multiple non-co-located physical TRPs, the physical TRP may be a distributed antenna system (DAS) (a network of spatially separated antennas connected to a common source via a transport medium) or a remote control.radio head (RRH) (a remote base station connected to a serving base station). Alternatively, a non-colocated physical TRP may be a serving base station that receives measurement reports from the UE and a neighboring base station whose reference radio frequency (RF) signal (or simply the reference signal) is measured by the UE. Since a TRP is the point from which a base station transmits and receives wireless signals, as used herein, references to transmission from or reception at a base station should be understood as referring to a particular TRP of the base station. In some implementations that support UE positioning, the base station may not support wireless access by the UE (for example, it may not support data, voice, signaling connections, or any combination thereof for the UE), but instead may send reference signals to the UE for measurement by the UE, may receive and measure signals transmitted by the UE, or both. Such a base station may be referred to as a positioning beacon (for example, when transmitting signals to the UE), as a location measurement unit (for example, when receiving and measuring signals from the UE), or both. RF signals consist of electromagnetic waves of a specific frequency that carry information through space between a transmitter and a receiver. As used herein, a transmitter may send a single RF signal or multiple RF signals to a receiver. However, a receiver may receive multiple “RF signals” corresponding to each transmitted RF signal due to the propagation characteristics of RF signals over multipath channels. The same RF signal transmitted on different paths between a transmitter and a receiver may be referred to as a multipath RF signal. As used herein, an RF signal may also be referred to as a wireless signal or simply a signal where it is clear from the context that the term “signal” refers to either a wireless signal or an RF signal. Figure 1 illustrates an exemplary wireless communication system 100 based on various aspects. The wireless communication system 100 (which may also be referred to as a wireless wide area network (WWAN)) may include a plurality of base stations 102 and a plurality of UEs 104. The base stations 102 may include macro cell base stations (high power mobile base stations), small cell base stations (low power mobile base stations), or both. In aspects, the macro cell base stations may include eNBs, ng-eNBs, or both, wherein the wireless communication system 100 corresponds to an LTE network, or gNBs wherein the wireless communication system 100 corresponds to an NR network, or a combination of both, and the small cell base stations may include femto cells, pico cells, micro cells, and so on. Base stations 102 may collectively form a radio access network (RAN) and interface with a core network 108 (for example, an evolved packet core (EPC) or a 5G core (5GC)) via a backhaul link 110, and via the core network 108 to one or more location servers 112 (which may be part of the core network 108 or may be external to the core network 108).In addition to other functions, the base stations 102 may perform functions related to one or more of user data transfer, radio channel encoding and decoding, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), cell interference intercoordination, connection setup and release, load balancing, distribution for nonaccess stratum (NAS) messages, NAS node election, synchronization, RAN sharing, broadcast multimedia multicast services (MBMS), subscriber and equipment tracking, RAN information management (RIM), numbering, positioning, and sending of alert messages. The base stations 102 may communicate with each other directly or indirectly (e.g., via EPC / 5GC) via the backhaul link 114, which may be wired or wireless. The base station 102 may communicate wirelessly with the UE 104. Each base station 102 may provide communication coverage for each of the geographic coverage areas 116. In an aspect, one or more cells may be supported by the base station 102 within each geographic coverage area 116. A cell is a logical communication entity used for communication with the base station (for example, over some frequency resource, referred to as a carrier frequency, component carrier, carrier, band, or the like), and may be associated with an identifier (for example, physical cell identifier (PCI), virtual cell identifier (VCI), cell global identifier (CGI)) to distinguish cells operating over the same or different carrier frequencies.In some cases, different cells may be configured according to different protocol types (e.g., machine-type communication (MTC), narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB), or others) that may provide access for different types of UEs. Since cells are supported by specific base stations, the term cell may refer to either or both the logical communication entity and the base station that supports it, depending on the context. In addition, since the TRP is typically the physical transmission point of the cell, the terms cell and TRP may be used interchangeably. In some cases, the term cell may also refer to the geographic coverage area of ​​a base station (e.g., sector), to the extent that carrier frequencies can be detected and used for communication within some portion of the geographic coverage area 116. While neighboring macro cell base stations 102's geographic coverage areas 116 may partially overlap (for example, in handover areas), some geographic coverage areas 116 may substantially overlap with larger geographic coverage areas 116. For example, a small cell base station 102' may have a coverage area of ​​116' that substantially overlaps with the geographic coverage areas 116 of one or more macro cell base stations 102. A network that includes both small cell base stations and macro cells may be known as a heterogeneous network. A heterogeneous network may also include a home eNB (HeNB), which may provide services to a limited group known as a closed subscriber group (CSG). The communication link 118 between the base station 102 and the UE 104 may include an uplink transmission (also referred to as a reverse link) from the UE 104 to the base station 102, a downlink transmission (also referred to as a forward link) from the base station 102 to the UE 104, or both. The communication link 118 may utilize MIMO antenna technology, including spatial multiplexing, beamforming, transmit diversity, or any combination thereof. The communication link 118 may be over one or more carrier frequencies. The allocation of carriers may be asymmetric with respect to the downlink and uplink (for example, more or fewer carriers may be allocated to the downlink than to the uplink). The wireless communication system 100 may further include a wireless local area network (WLAN) access point (AP) 120 in communication with a WLAN station (STA) 122 over a communication link 124 in an unlicensed frequency spectrum (for example, 5 GHz). When communicating in the unlicensed frequency spectrum, the WLAN STA 122, WLAN AP 120, or any combination thereof may perform a free channel assessment (CCA) or listen-before-talk (LBT) procedure before communicating to determine whether a channel is available. The small cell base station 102' may operate in licensed, unlicensed, or both frequency spectrum. When operating in unlicensed frequency spectrum, the small cell base station 102' may utilize either LTE or NR technology and utilize the same 5 GHz unlicensed frequency spectrum as utilized by the WLAN AP 120. The small cell base station 102', utilizing LTE / 5G in unlicensed frequency spectrum, may enhance coverage to the access network, increase capacity of the access network, or both. NR in unlicensed spectrum may be referred to as NR-U. LTE in unlicensed spectrum may be referred to as LTE-U, licensed assisted access (LAA), or MulteFire. The wireless communication system 100 may further include a millimeter wave (mmW) base station 126 that may operate in mmW frequencies, near mmW frequencies, or a combination thereof in communication with the UE 128. Extremely high frequency (EHF) is a portion of the RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and wavelengths between 1 millimeter and 10 millimeters. Radio waves in this band may be referred to as millimeter waves. Near mmW may extend to a frequency of 3 GHz with a wavelength of 100 millimeters. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, also referred to as centimeter waves. Communications using the mmW / near mmW radio frequency bands have high path loss and relatively short range.The mmW base station 126 and UE 128 may utilize beamforming (transmitting, receiving, or both) over the mmW communication link 130 to compensate for very high path loss and short range. Further, it will be understood that in alternative configurations, one or more base stations 102 may also transmit using mmW or near mmW and beamforming. Therefore, it will be understood that the above illustrations are merely examples and should not be construed to limit the various aspects disclosed herein. Transmitting beamforming is a technique for focusing an RF signal in a specific direction. Traditionally, when a network node (for example, a base station) broadcasts an RF signal, it broadcasts the signal in all directions (omni-directionally). By transmitting beamforming, the network node determines where a given target device (for example, a UE) is located (relative to the transmitting network node) and projects a stronger downlink RF signal in that specific direction, thereby providing faster speeds (in terms of data transmission) and a stronger RF signal to the receiving device. To change the direction of the RF signal while transmitting, the network node can control the relative phase and amplitude of the RF signal at each of one or more transmitters broadcasting the RF signal.For example, network nodes can use arrays of antennas (referred to as “phased arrays” or “antenna arrays”) that create RF beams that can be “scattered” in different directions, without actually moving the antennas. Typically, RF currents from the transmitter are fed to each antenna with the correct phase relationship so that the radio waves from the separate antennas are combined to enhance radiation in the desired direction, while canceling out to suppress radiation in undesired directions. Transmitting beams may be quasi-collocated, meaning that they appear to the receiver (e.g., UE) to have the same parameters, regardless of whether the transmitting antennas of the network nodes themselves are physically collocated or not. In NR, there are four types of quasi-collocation relations (QCL). In particular, a QCL relation of a certain type means that certain parameters about a second reference RF signal in the second beam can be obtained from information about the source reference RF signal in the source beam. Thus, if the source reference RF signal is a QCL Type A, the receiver can use the source reference RF signal to estimate the Doppler shift, Doppler spread, average delay, and delay spread of the second reference RF signal transmitted on the same channel. If the source reference RF signal is a Type B QCL, the receiver can use the source reference RF signal to estimate the Doppler shift and Doppler spread of the second reference RF signal transmitted on the same channel. If the source reference RF signal is a Type C QCL, the receiver can use the source reference RF signal to estimate the Doppler shift and average delay of the second reference RF signal transmitted on the same channel. If the source reference RF signal is a Type D QCL, the receiver can use the source reference RF signal to estimate the spatial receiver parameters of the second reference RF signal transmitted on the same channel. In receiver beam shaping, the receiver uses the receiver beam to amplify the RF signals detected on a particular channel. For example, the receiver may increase the gain setting, adjust the phase setting, or a combination thereof, of the antenna array in a particular direction to amplify (i.e., to increase the gain level) the RF signals received from that direction. Thus, when a receiver is said to beam shape in a particular direction, it means that the beam gain in that direction is high relative to the beam gain along other directions, or that the beam gain in that direction is the highest compared to the beam gain in that direction of all other receiver beams available to the receiver.This results in a stronger received signal strength (e.g., reference signal received power (RSRP), reference received signal quality (RSRQ), signal to noise ratio (SINR), and so on) of the RF signal received from that direction. The receive beams may be spatially related. Spatial relatedness means that the parameters of the transmit beam for the second reference signal can be obtained from information about the receive beam for the first reference signal. For example, the UE may use a particular receive beam to receive one or more downlink reference signals (e.g., positioning reference signal (PRS), narrowband tracking reference signal (NRS), tracking reference signal (TRS), phase tracking reference signal (PTRS), cell-specific reference signal (CRS), channel state information reference signal (CSI-RS), primary synchronization signal (PSS), secondary synchronization signal (SSS), synchronization signal block (sSB), and so on) from the base station.The UE may then form a transmission beam to send one or more uplink reference signals (for example, an uplink positioning reference signal (UL-PRS), a voice reference signal (SRS), a demodulation reference signal (DMRS), a PTRS, and so on) to the base station based on the parameters of the receiving beam. Note that a downlink beam can be either a transmit beam or a receive beam, depending on the entity forming it. For example, if a base station is forming a downlink beam to transmit a reference signal to a UE, the downlink beam is a transmit beam. However, if a UE is forming a downlink beam, it is a receive beam to receive the downlink reference signal. Similarly, an uplink beam can be either a transmit beam or a receive beam, depending on the entity forming it. For example, if a base station is forming an uplink beam, it is an uplink receive beam, and if a UE is forming an uplink beam, it is an uplink transmit beam. In 5G, the frequency spectrum in which wireless nodes (for example, base stations 102 / 126, UE 104 / 128) operate is divided into several frequency ranges, FR1 (from 450 to 6000 MHz), FR2 (from 24250 to 52600 MHz), FR3 (above 52600 MHz), and FR4 (between FR1 and FR2). In a multi-carrier system, such as 5G, one of the carrier frequencies is referred to as the primary carrier or anchor carrier or primary serving cell or PCell, and the remaining carrier frequencies are referred to as secondary carriers or secondary serving cells or Scells. In carrier aggregation, the anchor carrier is the carrier operating on the primary frequency (for example, FR1) used by the UE 104 / 128 and the cell in which the UE 104 / 128 performs the initial radio source control (RRC) connection establishment procedure or initiates the RRC connection re-establishment procedure.The primary carrier carries all UE common and dedicated control channels and may be a carrier on a licensed frequency (but not always). A secondary carrier is a carrier operating on a second frequency (e.g., FR2) that can be configured after the RRC connection is established between the UE 104 and the anchor carrier and that can be used to provide additional radio resources. In some cases, the secondary carrier may be a carrier on an unlicensed frequency. The secondary carrier may only contain necessary signaling information and signals, for example, UE-specific ones may not be present in the secondary carrier, since the primary uplink and downlink carriers are usually UE-specific. This means that different UE 104 / 128s in a cell may have different downlink primary carriers. The same applies to the uplink primary carrier. The network can change the primary carrier of a UE 104 / 128 at any time.This is done, for example, to balance the load on different carriers. Since a serving cell (whether PCell or SCell) corresponds to a carrier / component carrier frequency on which multiple base stations communicate, the terms cell, serving cell, component carrier, carrier frequency, and the like can be used interchangeably. For example, still referring to Figure 1, one of the frequencies used by the macro cell base station 102 may be an anchor carrier (or PCell) and the other frequencies used by the macro cell base station 102, the mmW base station 126, or a combination thereof may be secondary carriers (“Scell”). Simultaneous transmission, reception, or both of multiple carriers may enable the UE 104 / 128 to significantly increase the data transmission rate, reception rate, or both. For example, two aggregate 20 MHz carriers in a multi-carrier system will theoretically result in a twofold increase in data rate (i.e., 40 MHz), compared to that achieved by a single 20 MHz carrier. The wireless communication system 100 may further include one or more UEs, such as UE 132, indirectly connected to one or more communication networks via one or more peer-to-peer (P2P) device-to-device (D2D) links (referred to as sidelinks). In the example in Figure 1, UE 132 has a D2D P2P link 134 with one of the UEs 104 connected to one of the base stations 102 (for example, through which UE 132 can indirectly obtain cellular connectivity) and a D2D P2P link 194 with WLAN STA 122 connected to WLAN AP 120 (through which UE 132 can indirectly obtain WLAN-based Internet connectivity). For example, the D2D P2P link 134 and D2D P2P link 136 may be supported by well-known D2D RATs, such as LTE Direct (LTE-D), WiFi Direct (WiFi-D), Bluetooth®, and so on. The wireless communication system 100 may further include a UE 138 that may communicate with a macro cell base station 102 via a communication link 118, with a mmW base station 126 via a mmW communication link 130, or a combination thereof. For example, the macro cell transmitter 102 may support a PCell and one or more SCells for the UE 138 and the mmW transmitter 126 may support one or more SCells for the UE 138. Figure 2A illustrates an example of a wireless network structure 200 based on various aspects. For example, the 5GC 210 (also referred to as the Next Generation Core (NGC)) can be viewed functionally as control plane functions 214 (e.g., UE registration, authentication, network access, gateway selection, and so on) and user plane functions 212, (e.g., UE gateway functions, access to the data network, IP routing, and so on) operating cooperatively to form a core network. The user plane interface (NG-U) 213 and the control plane interface (NG-C) 215 connect the gNB 222 to the 5GC 210 and specifically to the control plane function 214 and the user plane function 212. In additional configurations, the ng-eNB 224 can also be connected to the 5GC 210 via the NG-C 215 to the control plane function 214 and the NG-U 213 to the user plane function 212. Furthermore, the ng-eNB 224 can directly communicate with the gNB 222 via the backhaul connection 223.In some configurations, the New RAN 220 may have only one or more gNBs 222, while other configurations include one or more of ng-eNBs 224 and gNBs 222. Either gNBs 222 or ng-eNBs 224 may communicate with the UE 204 (e.g., from the UE depicted in Figure 1). Other optional aspects may include a location server 112, which may communicate with the 5GC 210 to provide location assistance to the UE 204. The location servers 112 may be implemented as a plurality of separate servers (e.g., physically separate servers, different software modules on a single server, different software modules spread across multiple physical servers, and so on), or alternatively each corresponding to a single server. The location servers 112 may be configured to support one or more location services for the UE 204 that may connect to the location servers 112 via the core network, the 5GC 210, via the Internet (not illustrated), or via both.Further, the location server 112 may be integrated into the core network components, or alternatively may be located outside the core network. Figure 2B illustrates another example of a wireless network structure 250 based on various aspects. For example, the 5GC 260 can be viewed functionally as a control plane function, provided by the access and mobility management function (AMF) 264, and a user plane function, provided by the user plane function (UPF) 262, which operate cooperatively to form a core network (i.e., the 5GC 260). The user plane interface 263 and the control plane interface 265 connect the ng-eNB 224 to the 5GC 260 and in particular to the UPF 262 and AMF 264. In additional configurations, the gNB 222 can also be connected to the 5GC 260 via the control plane interface 265 to the AMF 264 and the user plane interface 263 to the UPF 262. Furthermore, the ngeNB 224 can directly communicate with the gNB 222 via the backhaul connection 223, with or without the gNB's direct connectivity to the 5GC 260.In some configurations, the new RAN 220 may have only one or more gNBs 222, while other configurations include one or more of both ng-eNBs 224 and gNBs 222. Either gNBs 222 or ng-eNBs 224 may communicate with UEs 204 (for example, one of the UEs depicted in Figure 1). The New RAN base station 220 communicates with AMFs 264 via the N2 interface and with UPFs 262 via the N3 interface. The functions of AMF 264 include registration management, connection management, range management, mobility management, authorized interception, transport for session management (SM) messages between UE 204 and session management function (SMF) 266, transparent proxy service for routing SM messages, access authentication and access authorization, transport for short message service (SMS) messages between UE 204 and short message service function (SMSF) (not shown), and security anchor functionality (SEAF). AMF 264 also interacts with authentication server function (AUSF) (not shown) and UE 204, and receives intermediate keys generated as a result of UE 204's authentication process. In the case of authentication based on UMTS (Universal Mobile Telecommunications System) subscriber identity module (USIM), AMF 264 retrieves security material from AUSF. The functions of AMF 264 also include security context management (SCM). SCM receives keys from SEAF that it uses to derive access network-specific keys.The functionality of the AMF 264 also includes location service management for regulatory services, transport for location service messages between the UE 204 and the location management function (LMF) 270 (which acts as a location server 112), transport for location service messages between the RAN 220 and the new LMF 270, allocation of evolved packet system (EPS) operator identifiers to work with the EPS, and notification of UE 204 mobility events. In addition, the AMF 264 also supports functionality for non-3GPP access networks. The functions of the UPF 262 include acting as an anchor point for intra- / inter-RAT mobility (when applicable), acting as an external protocol data unit (PDU) session point of the interconnect to the data network (not shown), providing packet routing and forwarding, packet inspection, user plane policy rule enforcement (for example, gating, redirection, traffic steering), lawful interception (user plane collection), traffic usage reporting, quality of service (QoS) handling for the user plane (for example, uplink / downlink level enforcement, reflective QoS marking in the downlink), uplink traffic verification (service data flow (SDF) to QoS flow mapping), transport level packet marking in the uplink and downlink, downlink packet buffering and downlink data notification triggering, and sending and forwarding one or more end markers to the source RAN node.The UE 262 may also support the transfer of location service messages via the user plane between the UE 204 and a location server, such as a secure user plane location (SLP) platform (SUPL) 272. The functions of the SMF 266 include session management, UE Internet Protocol (IP) address allocation and management, user plane function selection and control, traffic steering configuration in the UPF 262 to route traffic to the appropriate destination, control of portions of the enforcement and QoS policies, and downlink data notification. The interface through which the SMF 266 communicates with the AMF 264 is referred to as the N11 interface. Other optional aspects may include an LMF 270, which may communicate with a 5GC 260 to provide location assistance to the UE 204. The LMF 270 may be implemented as a plurality of separate servers (for example, physically separate servers, different software modules on a single server, different software modules spread across multiple physical servers, and so on), or alternatively each corresponding to a single server. The LMF 270 may be configured to support one or more location services for the UE 204 that may connect to the LMF 270 via the core network, the 5GC 260, via the Internet (not illustrated), or via both. The SLP 272 may support similar functionality to the LMF 270, but the LMF 270 may communicate with the AMF 264, New RAN 220, and the UEs 204 via the control plane (for example, using interfaces and protocols intended for conveying signaling messages rather than voice).or data), SLP 272 may communicate with UE 204 and external clients (not shown in Figure 2B) via the user plane (for example, using protocols intended to carry voice or data such as transmission control protocol (TCP) and / or IP). In an aspect, the LMF 270, the SLP 272, or both may be integrated into a base station, such as a gNB 222 or an ng-eNB 224. When integrated into a gNB 222 or an ngeNB 224, the LMF 270 or SLP 272 may be referred to as a location management component (LMC). However, as used herein, references to the LMF 270 and SLP 272 include cases where the LMF 270 and SLP 272 are core network components (for example, a 5GC 260) and cases where the LMF 270 and SLP 272 are base station components. Figures 3A, 3B, and 3C illustrate some examples of components (represented by appropriate blocks) that may be incorporated into UE 302 (which may correspond to any of the UEs described herein), base station 304 (which may correspond to any of the base stations described herein), and network entity 306 (which may correspond to or embody any of the network functions described herein, including location server 230 and LMF 270, or may be independent of NG-RAN 220 and / or 5GC Infrastructure 210 / 260 depicted in Figures 2A and 2B, such as a private network) to support file transmission operations as taught herein. It will be appreciated that these components may be implemented in various types of equipment in different implementations (for example, in an ASIC, in a system-on-a-chip (SoC), and so on). The illustrated components may also be incorporated into other equipment in a communications system.For example, other equipment in the system may include components similar to those described to provide similar functionality. Also, a particular piece of equipment may contain one or more components. For example, the equipment may include multiple transceiver components that enable the equipment to operate on multiple carriers and / or communicate over different technologies. The UE 302 and base station 304 each include one or more wireless wide area network (WWAN) transceivers 310 and 350, respectively, providing means for communicating (e.g., means for transmitting, means for receiving, means for measuring, means for tuning, means for refraining from transmitting, and so on) over one or more wireless communication networks (not shown), such as a NR network, an LTE network, a GSM network, and / or the like. The WWAN transceivers 310 and 350 may each be connected to one or more antennas 316 and 356, respectively, to communicate with other network nodes, such as other UEs, access points, base stations (e.g., eNBs, gNBs), and so on, via at least one designated RAT (e.g., NR, LTE, GSM, and so on) over a wireless communication medium of interest (e.g., some set of time / frequency sources in a given frequency spectrum).WWAN transceivers 310 and 350 may be variously configured to transmit and encode signals 318 and 358 (for example, messages, indications, information, and so on), respectively, and conversely, to receive and decode signals 318 and 358 (for example, messages, indications, information, alerts, and so on), each in accordance with a specified RAT. Specifically, WWAN transceivers 310 and 350 include one or more transmitters 314 and 354, respectively, for transmitting and encoding signals 318 and 358, respectively, and one or more receivers 312 and 352, respectively, for receiving and decoding signals 318 and 358, respectively. The UE 302 and base station 304 each also include, in at least some cases, one or more short-range wireless transceivers 320 and 360, respectively. The short-range wireless transceivers 320 and 360 may be connected to one or more antennas 326 and 366, respectively, and provide means for communicating (e.g., means for transmitting, means for receiving, means for measuring, means for tuning, means for suppressing from transmitting, and so on) with other network nodes, such as other UEs, access points, base stations, and so on, via at least one designated RAT (e.g., WiFi, LTE-D, Bluetooth®, Zigbee®, Z-Wave®, PC5, dedicated short-range communication (DSRC), wireless access for vehicular environments (WAVE), near-field communication (NFC), and so on) over a wireless communication medium of interest.The short-range wireless transceivers 320 and 360 may be variously configured to transmit and encode signals 328 and 368 (for example, messages, indications, information, and so on), respectively, and conversely, to receive and decode signals 328 and 368 (for example, messages, indications, information, alerts, and so on), respectively, in accordance with a designated RAT. Specifically, the short-range wireless transceivers 320 and 360 include one or more transmitters 324 and 364, respectively, for transmitting and encoding signals 328 and 368, respectively, and one or more receivers 322 and 362, respectively, for receiving and decoding signals 328 and 368, respectively. As specific examples, the short-range wireless transceivers 320 and 360 may be WiFi transceivers, Bluetooth® transceivers, Zigbee® and / or Z-Wave® transceivers, NFC transceivers, or vehicle-to-vehicle (V2V) and / or vehicle-to-everything (V2X) transceivers. UE 302 and base station 304 also include, in at least some cases, satellite signal receivers 330 and 370. The satellite signal receivers 330 and 370 may each be connected to one or more antennas 336 and 376, and may provide means for receiving and / or measuring the position of satellite / communication signals 338 and 378, respectively. Where the satellite signal receivers 330 and 370 are satellite positioning system receivers, the satellite positioning / communication signals 338 and 378 may be global positioning system (GPS) signals, global navigation satellite system (GLONASS) signals, Galileo signals, Beidou signals, Indian Regional Navigation Satellite System (NAVIC) signals, Quasi-Zenith Satellite System (QZSS), etc. Where the satellite signal receivers 330 and 370 are non-terrestrial network (NTN) receivers, the satellite positioning / communication signals 338 and 378 may be communication signals (for example, carrying control and / or user data) originating from the 5G network.The satellite signal receivers 330 and 370 may comprise any hardware and / or software suitable for receiving and processing the satellite position / communication signals 338 and 378, respectively. The satellite signal receivers 330 and 370 may request appropriate information and operations from other systems, and, in at least some cases, perform calculations to determine the location of the UE 302 and the base station 304, respectively, using measurements obtained by the satellite positioning system algorithms. The base station 304 and the network entity 306 each include one or more network transceivers 380 and 390, respectively, providing means for communicating (e.g., means for transmitting, means for receiving, and so forth) with other network entities (e.g., other base stations 304, other network entities 306). For example, the base station 304 may use one or more network transceivers 380 to communicate with other base stations 304 or network entities 306 over one or more wired or wireless backhaul links. As another example, the network entity 306 may use one or more network transceivers 390 to communicate with one or more base stations 304 over one or more wired or wireless backhaul links, or with other network entities 306 over one or more wired or wireless core network interfaces. Transceivers can be configured to communicate over a wired or wireless link. The transceiver (whether a wired transceiver or a wireless transceiver) includes transmitting circuitry (for example, transmitters 314, 324, 354, 364) and receiving circuitry (for example, receivers 312, 322, 352, 362). The transceiver may be an integrated device (e.g., embodying transmitting circuitry and receiving circuitry in a single device) in some implementations, may comprise separate transmitting circuitry and separate receiving circuitry in some implementations, or may be embodied in other ways in other implementations. The transmitting circuitry and receiving circuitry of a wired transceiver (e.g., network transceivers 380 and 390 in some implementations) may be coupled to one or more wired network interface ports. The wireless transmitting circuitry (e.g., transmitters 314, 324, 354, 364) may include or be coupled to a plurality of antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array, which enables the respective devices (e.g., UE 302, base station 304) to perform beamforming transmissions, as described herein. Similarly, a wireless receiving circuit (e.g., receivers 312, 322, 352, 362) may include or be coupled to a plurality of antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array, which enables each device (e.g., UE 302, base station 304) to perform receiving beam shaping, as described herein. In an aspect, the transmitting circuit and the receiving circuit may share the same antenna (e.g., antennas 316, 326, 356, 366), so that each device may only receive or transmit at a given time, not both at the same time. Wireless transceivers (e.g., WWAN transceivers 310 and 350, short-range wireless transceivers 320 and 360) may also include a network listening module (NLM) or the like to perform various measurements. As used herein, various wireless transceivers (for example, transceivers 310, 320, 350, and 360, and network transceivers 380 and 390 in some implementations) and wired transceivers (for example, network transceivers 380 and 390 in some implementations) can generally be characterized as a transceiver, at least one transceiver, or one or more transceivers. Thus, whether a particular transceiver is a wired or wireless transceiver can be inferred from the type of communication performed. For example, backhaul communication between network devices or servers will generally involve signaling via wired transceivers, while wireless communication between a UE (for example, UE 302) and a base station (for example, base station 304) will generally involve signaling via wireless transceivers. The UE 302, base station 304, and network entity 306 also include other components that may be used in conjunction with the operations as disclosed herein. The UE 302, base station 304, and network entity 306 include one or more processors 332, 384, and 394, respectively, to provide functionality related to, for example, wireless communications, and to provide other processing functionality.Therefore, processors 332, 384, and 394 may provide means for processing, such as means for determining, means for calculating, means for receiving, means for transmitting, means for indicating, and so on. In aspects, processors 332, 384, and 394 may include, for example, one or more general purpose processors, multi-core processors, central processing units (CPUs), ASICs, digital signal processors (DSPs), field programmable gate arrays (FPGAs), other programmable logic devices or processing circuits, or various combinations thereof. The UE 302, the base station 304, and the network entity 306 include memory circuitry implementing memories 340, 386, and 396 (for example, each includes a memory device), respectively, for maintaining information (for example, information indicating reserved resources, thresholds, parameters, and so on). Therefore, the memories 340, 386, and 396 may provide means for storing, means for retrieving, means for maintaining, and so on. In some cases, the UE 302, the base station 304, and the network entity 306 may include positioning components 342, 388, and 398, respectively. Positioning components 342, 388, and 398 may be hardware circuitry that is part of or coupled to processors 332, 384, and 394, respectively, which, when executed, cause UE 302, base station 304, and network entity 306 to perform the functions described herein.In another aspect, the positioning components 342, 388, and 398 may be external to the processors 332, 384, and 394 (for example, part of a modem processing system, integrated with another processing system, and so forth). Alternatively, the positioning components 342, 388, and 398 may be memory modules stored in memories 340, 386, and 396, respectively, which, when executed by the processors 332, 384, and 394 (or modem processing system, another processing system, and so forth), cause the UE 302, the base station 304, and the network entity 306 to perform the functionality described herein. Figure 3A illustrates possible locations of the positioning components 342, which may, for example, be part of one or more WWAN transceivers 310, memory 340, one or more processors 332, or a combination thereof, or may be stand-alone components.Figure 3B illustrates possible locations of positioning component 388, which may, for example, be part of one or more WWAN transceivers 350, memory 386, one or more processors 384, or a combination thereof, or may be a stand-alone component. Figure 3C illustrates possible locations of positioning component 398, which may, for example, be part of one or more network transceivers 390, memory 396, one or more processors 394, or a combination thereof, or may be a stand-alone component. The UE 302 may include one or more sensors 344 coupled to one or more processors 332 to provide a means for detecting or detecting motion and / or orientation information independent of motion data derived from signals received by one or more WWAN transceivers 310, one or more short-range wireless transceivers 320, and / or satellite signal receivers 330. For example, the sensor(s) 344 may include an accelerometer (e.g., a micro-electromechanical systems (MEMS) device), a gyroscope, a geomagnetic sensor (e.g., a compass), an altimeter (e.g., a barometric pressure altimeter), and / or other types of motion-detecting sensors. In addition, the sensors 344 may include a number of different types of devices and combine their outputs to provide motion information.For example, sensor 344 may use a combination of multi-axis accelerometers and orientation sensors to provide the capability to calculate position in a two-dimensional (2D) and / or three-dimensional (3D) coordinate system. In addition, UE 302 includes a user interface 346 that provides means for providing indications (for example, audible and / or visual indications) to the user and / or for receiving user input (for example, when the user moves a sensing device such as a keyboard, touchscreen, microphone, and so on). Although not shown, base station 304 and network entity 306 may also include a user interface. Referring to one or more processors 384 in more detail, in the downlink, IP packets from the network entity 306 may be provided to the processors 384. The one or more processors 384 may implement functionality for the RRC layer, packet data convergence protocol (PDCP) layer, radio link control (RLC) layer, and medium access control (MAC) layer. The one or more processors 384 may provide RRC layer functionality related to broadcasting system information (for example, master information block (MIB), system information block (SIB)), RRC connection control (for example, RRC connection numbering, RRC connection establishment, RRC connection modification, and RRC connection release), inter-RAT mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality relates to header compression / decompression, security (encoding, decoding, integrity protection, integrity verification), and handover support functions;The RLC layer functionality deals with the transfer of upper layer PDUs, error correction via automatic repeat request (ARQ), merging, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and the MAC layer functionality deals with mapping between logical channels and transport channels, reporting of scheduling information, error correction, priority handling, and prioritization of logical channels. Transmitter 354 and receiver 352 may implement Layer-1 (L1) functionality related to various signal processing functions. Layer-1, which includes the physical layer (PHY), may include error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping to physical channels, modulation / demodulation of the physical channels, and MIMO antenna processing. Transmitter 354 handles mapping to signal constellations based on various modulation schemes (for example, binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The encoded and modulated symbols may then be split into parallel streams.Each stream can then be mapped to an orthogonal frequency division multiplexing (OFDM) subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domain, and then combined together using the inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM symbol stream is spatially precoded to produce multiple spatial streams. Channel estimates from the channel estimator can be used to determine coding and modulation schemes, as well as for spatial processing. Channel estimates can be obtained from reference signals and / or channel condition feedback transmitted by the UE 302. Each spatial stream can then be assigned to one or more different antennas 356. The transmitter 354 can modulate the RF carrier with the respective spatial stream for transmission. At UE 302, receivers 312 receive signals through their respective antennas 316. Receivers 312 recover the information modulated to RF carriers and provide the information to one or more processors 332. Transmitters 314 and receivers 312 implement Layer-1 functionality related to various signal processing functions. Receivers 312 may perform spatial processing on the information to recover each spatial stream destined for UE 302. If multiple spatial streams are destined for UE 302, they may be combined by receivers 312 into a single OFDM symbol stream. Receivers 312 then convert the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal comprises 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 point transmitted by the base station 304. This soft decision may be based on a channel estimate computed by a channel estimator. The soft decision is then encoded and decoded to recover the data and control signals originally transmitted by the base station 304 on the physical channel. The data and control signals are then provided to one or more processors 332, which implement Layer-3 (L3) and Layer-2 (L2) functionality. In the uplink, one or more processors 332 provide demultiplexing between transport and logical channels, packet reassembly, decoding, header decompression, and control signal processing to recover IP packets from the core network. One or more processors 332 are also responsible for error detection. Similar to the functionality described in connection with downlink transmissions by the base station 304, one or more processors 332 provide RRC layer functionality related to the acquisition of system information (e.g., MIB, SIB), RRC connections, and measurement reporting; PDCP layer functionality related to header compression / decompression, and security (encoding, decoding, integrity protection, integrity verification); The RLC layer functionality deals with the transfer of upper layer PDUs, error correction via ARQ, merging, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and the MAC layer functionality deals with the mapping between logical channels and transport channels, multiplexing MAC SDUs to transport blocks (TBs), demultiplexing MAC SDUs from TBs, reporting of scheduling information, error correction via hybrid auto-repeat request (HARQ), priority handling, and prioritization of logical channels. The channel estimates obtained by the channel estimator from the reference or feedback signals transmitted by the base station 304 can be used by the transmitter 314 to select appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the transmitter 314 can be provided to different antennas 316. The transmitter 314 can modulate the RF carrier with each of the spatial streams for transmission. The uplink transmission is processed at the base station 304 in a manner similar to that described in connection with the receiver function at the UE 302. The receiver 352 receives the signal through its respective antenna 356. The receiver 352 recovers the modulated information to the RF carrier and provides the information to one or more processors 384. In the uplink, one or more 384 processors provide demultiplexing between transport and logical channels, packet reassembly, decoding, header decompression, and control signal processing to recover IP packets from UE 302. IP packets from one or more 384 processors may be provided to the core network. One or more 384 processors are also responsible for error detection. For convenience, UE 302, base station 304, and / or network entity 306 are shown in Figure 3A, 3B, and 3C include various components that may be configured based on the various examples described herein. However, it will be appreciated that the illustrated components may have different functions in different designs. In particular, various components in Figures 3A-3C are optional in alternative configurations and various aspects of the configurations may differ due to design choices, cost, device usage, or other considerations. For example, in the case of Figure 3A, certain implementations of UE 302 may omit WWAN transceiver 310 (for example, a wearable device or tablet computer or PC or laptop may have Wi-Fi and / or Bluetooth capabilities without cellular capabilities), or may omit short range wireless transceiver 320 (for example, cellular only, and so on), or may omit satellite signal receiver 330, or may omit sensor 344, and so on.In another example, in the case of Figure 3B, certain implementations of base station 304 may omit WWAN transceiver 350 (for example, a Wi-Fi hotspot access point without cellular capabilities), or may omit short-range wireless transceiver 360 (for example, cellular only, and so on), or may omit satellite receiver 370, and so on. For brevity, illustrations of various alternative configurations are not provided here, but will be readily understood by those skilled in the art. Various components of the UE 302, the base station 304, and the network entity 306 may be communicatively coupled to each other via data buses 334, 382, ​​and 392, respectively. In an aspect, data buses 334, 382, ​​and 392 may each form, or be part of, the communication interface of the UE 302, the base station 304, and the network entity 306. For example, where different logical entities are embodied in the same device (for example, gNB and location server functionality are combined into the same base station 304), data buses 334, 382, ​​and 392 may provide communication between them. The components in Figures 3A, 3B, and 3C may be implemented in various ways. In some implementations, the components in Figures 3A, 3B, and 3C may be implemented in one or more circuits such as, for example, one or more processors and / or one or more ASICs (which may include one or more processors). Here, each circuit may utilize and / or incorporate at least one memory component to store information or executable code used by the circuit to provide this functionality. For example, some or all of the functionality represented by blocks 310 to 346 may be implemented by the processor and memory components of UE 302 (for example, by appropriate code execution and / or by appropriate configuration of the processor components).Similarly, some or all of the functionality represented by blocks 350 to 388 may be implemented by the processor and memory components of the base station 304 (for example, by appropriate code execution and / or by appropriate configuration of the processor components). Also, some or all of the functionality represented by blocks 390 to 398 may be implemented by the processor and memory components of the network entity 306 (for example, by appropriate code execution and / or by appropriate configuration of the processor components).For simplicity, various operations, actions, and / or functions are described herein as being performed by the UE, by the base station, by the network entity, and so on. However, as will be understood, such operations, actions, and / or functions may actually be performed by certain components or combinations of components of the UE 302, the base station 304, the network entity 306, and so on, such as processors 332, 384, 394, transceivers 310, 320, 350, and 360, memories 340, 386, and 396, positioning components 342, 388, and 398, and so on. In some designs, the network entity 306 may be implemented as a core network component. In other designs, the network entity 306 may be distinct from the network operator or cellular network infrastructure operating (for example, NG RAN 220 and / or 5GC 210 / 260). For example, the network entity 306 may be a private network component that can be configured to communicate with the UE 302 via the base station 304 or independently of the base station 304 (for example, via a non-cellular communication link, such as Wi-Fi). NR supports a number of cellular network-based positioning technologies, including downlink-based, uplink-based, and downlink-and-uplink-based positioning methods. Downlink-based positioning methods include observed time difference of arrival (OTDOA) in LTE, downlink time difference of arrival (DL-TDOA) in NR, and downlink angle of departure (DL-AoD) in NR. In the OTDOA or DL-TDOA positioning procedure, the UE measures the difference between the times of arrival (ToA) of reference signals (e.g., PRS, TRS, narrowband reference signal (NRS), CSI-RS, SSB, and so on) received from the base station pair, referred to as the reference signal time difference (RSTD) or time difference of arrival (TDOA) measurement, and reports it to the positioning entity. More specifically, the UE receives the identifiers of the reference base station (e.g., the serving base station) and some non-reference base stations in the assistance data.The UE then measures the RSTD between the reference base station and each non-reference base station. Based on the locations of the involved base stations and the known RSTD measurements, the positioning entity can estimate the UE's location. For DL-AoD positioning, the base station measures the angle and other channel properties (e.g., signal strength) of the downlink transmission beam used to communicate with the UE to estimate the UE's location. Uplink-based positioning includes uplink time difference of arrival (UL-TDOA) and uplink angle of arrival (UL-AoA). UL-TDOA is similar to DL-TDOA, but is based on an uplink reference signal (e.g., SRS) transmitted by the UE. For UL-AoA positioning, the base station measures the angle and other channel properties (e.g., gain level) of the uplink receiver beam used to communicate with the UE to estimate the UE's location. Downlink- and uplink-based positioning methods include enhanced cell-ID (E-CID) positioning and multi-roundtrip-time (RTT) positioning (also referred to as multi-cell RTT). In the RTT procedure, the initiator (base station or UE) transmits an RTT measurement signal (e.g., PRS or SRS) to the responder (UE or base station), which transmits an RTT response signal (e.g., SRS or PRS) back to the initiator. The RTT response signal includes the difference between the ToA of the RTT measurement signal and the transmission time of the RTT response signal, referred to as the receive-to-transmit (Rx-Tx) measurement. The initiator calculates the difference between the transmission time of the RTT measurement signal and the ToA of the RTT response signal, referred to as the Tx-Rx measurement. The propagation time (also referred to as the time-of-flight) between the initiator and the responder can be calculated from the TxRx and Rx-Tx measurements.Based on the known propagation time and speed of light, the distance between the initiator and responder can be determined. For multi-RTT positioning, the UE performs RTT procedures with multiple base stations to triangulate its location based on the known base station locations. RTT and multi-RTT methods can be combined with other positioning techniques, such as ULAoA and DL-AoD, to improve location accuracy. The E-CID positioning method is based on radio resource management (RRM) measurements. In E-CID, the UE reports the service cell ID, increment time (TA), and the identifier, estimated time, and signal strength of detected neighboring base stations. The UE's location is then estimated based on this information and the known location of the base station. To assist the positioning operation, a location server (e.g., location server 112, LMF 270, SLP 272) may provide assistance data to the UE. For example, the assistance data may include the base station (or base station cell / TRP) identifier for measuring the reference signal, the reference signal configuration parameters (e.g., the number of consecutive positioning slots, the periodicity of the positioning slots, the muting sequence, the frequency hopping sequence, the reference signal identifier (ID), the reference signal bandwidth, the slot offset, and so on), other parameters applicable to the particular positioning method, or a combination thereof. Alternatively, the assistance data may originate directly from the base station itself (e.g., in a periodically broadcast cost message, and so on). In some cases, the UE may self-detect neighboring network nodes without using assistance data. A location estimate may be called by other names, such as position estimate, location, position, position fix, fix, or the like. A location estimate may be geodetic and consist of coordinates (for example, latitude, longitude, and perhaps elevation) or may be civil and consist of a street address, postal address, or other verbal description of the location. The location estimate may further be defined relative to some other known location or defined absolutely (for example, using latitude, longitude, and perhaps elevation). The location estimate may include an expected error or uncertainty (for example, by including the area or volume that the location is expected to include with some specified or default confidence level). Various frame structures can be used to support downlink and uplink transmission between network nodes (e.g., base stations and UEs). Figure 4A is a diagram 400 illustrating an example downlink frame structure, based on aspects. Figure 4B is a 430 diagram illustrating an example of a channel in a downlink frame structure, based on aspects. Other wireless communication technologies may have different frame structures, different channels, or both. LTE, and in some cases NR, utilizes OFDM in the downlink and single-carrier frequency division multiplexing (SC-FDM) in the uplink. Unlike LTE, NR also has the option of using OFDM in the uplink. OFDM and SC-FDM partition the system bandwidth into multiple (K) orthogonal subcarriers, also often referred to as tones, bins, etc. Each subcarrier can be modulated with data. Typically, modulation symbols are transmitted in the frequency domain with OFDM and in the time domain with SC-FDM. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) may depend on the system bandwidth. For example, the subcarrier spacing might be 15 kHz and the minimum resource allocation (resource block) might be 12 subcarriers (or 180 kHz). As a result, the nominal FFT size may be equal to 128, 256, 504, 1024, or 2048 for a system bandwidth of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), respectively.The system bandwidth can also be partitioned into subbands. For example, a subband might cover 1.8 MHz (i.e., 6 source blocks), and there might be 1, 2, 4, 8, or 16 subbands for a system bandwidth of 1.25, 2.5, 5, 10, or 20 MHz, respectively. LTE supports a single numerology (subcarrier spacing, symbol length, and so on). In contrast, NR can support multiple numerologies (μ); for example, subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz or greater may be available. Table 1 below lists some of the different parameters for different NR numerologies. Table 1 μ SCS (kHz ) Symbol / Sot Slot / Subframe Slot / frame Slot Duration (milliseconds) Symbol Duration (ps) Max. nominal system BW (MHz) with 4K FFT size 0 15 14 1 10 1 66.7 50 1 30 14 2 20 0.5 33.3 100 2 60 14 4 40 0.25 16.7 200 3 120 14 8 80 0.125 8.33 400 4 240 14 16 160 0.0625 4.17 800 In the examples in Figures 4A and 4B, 15 kHz numerology is used. Thus, in the time domain, a 10 millisecond (ms) frame is divided into 10 equally sized subframes of 1 ms each, and each subframe covers one time slot. In Figures 4A and 4B, time is represented horizontally (e.g., on the X-axis) with time increasing from left to right, while frequency is represented vertically (e.g., on the Y-axis) with frequency increasing (or decreasing) from bottom to top. A source box can be used to represent a time slot, each time slot encompassing one or more time-concurrent source blocks (RBs) (also referred to as physical RBs (PRBs)) in the frequency domain. The source network is further divided into multiple source elements (REs). An RE may correspond to one symbol length in the time domain and one subcarrier in the frequency domain. In NR, a subframe is 1 ms long, a slot contains fourteen symbols in the time domain, and an RB contains twelve consecutive subcarriers in the frequency domain and fourteen consecutive symbols in the time domain. Thus, in NR there is one RB per slot. Depending on the SCS, an NR subframe can have fourteen symbols, twenty-eight symbols, or more, and thus can have 1 slot, 2 slots, or more. The number of bits carried by each RE depends on the modulation scheme. Some REs carry a downlink reference (pilot) signal (DL-RS). DL-RS can include PRS, TRS, PTRS, CRS, CSI-RS, DMRS, PSS, SSS, SSB, and so on. Figure 4A illustrates an example of an ET location carrying a PRS (labeled R). A PRS instance or “PRS opportunity is one instance of a periodically recurring time window (for example, a group of one or more consecutive slots) in which a PRS is expected to be transmitted. A PRS opportunity may also be referred to as a “PRS positioning opportunity, PRS positioning instance, “positioning opportunity, positioning instance, positioning repetition, or simply “opportunity, instance,” or “repetition.” The collection of source elements (REs) used for PRS transmission is called a PRS source. The collection of source elements can span multiple PRBs in the frequency domain and 'N' (for example, 1 or more) consecutive symbols within a slot in the time domain. In a given OFDM symbol in the time domain, the PRS source occupies consecutive PRBs in the frequency domain. A PRS source transmission in a given PRB has a specific comb size (also referred to as comb density). The comb size 'N' represents the subcarrier spacing (or frequency / pitch spacing) within each symbol of the PRS source configuration. Specifically, for a comb size 'N,' PRS is transmitted within every Nth subcarrier of the PRB symbol. For example, for comb-4, for every fourth symbol of the PRS source configuration, REs corresponding to every fourth subcarrier (for example, subcarriers 0, 4, 8) are used to transmit PRS from the PRS source. Currently, comb sizes comb-2, comb-4, comb-6, and comb-12 are supported for PRS DL. Figure 4A illustrates an exemplary PRS source configuration for comb-6 (which includes six symbols). That is, the shaded RE locations (labeled R) indicate the comb-6 PRS source configuration. A “PRS source set” is a set of PRS sources used for PRS signal transmission, where each PRS source has a PRS source ID. In addition, PRS sources in a PRS source set are associated with the same TRP. A PRS source set is identified by a PRS source set ID and is associated with a specific TRP (identified by the TRP ID). In addition, PRS sources in a PRS source frame have the same periodicity, a common muting pattern configuration, and the same repetition factor (e.g., PRSResourceRepetitionFactor) across slots. Periodicity is the time from the first repetition of the first PRS source of the first PRS instance to the same first repetition of the same first PRS source of the next PRS instance. The periodicity may have any length chosen from 2 μ Ξ{4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 160, 320, 640, 1280, 2560, 5040, 10240} slots, with μ = 0, 1, 2, 3. The repetition factor may have any length chosen from { 1, 2, 4, 6, 8, 16, 32} slots. A PRS source ID in a PRS source pool corresponds to a single broadcast (or broadcast ID) transmitted from a single TRP (where a TRP may transmit one or more broadcasts). This means that each PRS source in a PRS source pool may transmit on a different broadcast, and thus, a PRS source, or simply a source, may also be referred to as a broadcast. Note that this has no implications on whether the TRP and the broadcast on which the PRS is transmitted are known to the UE. A positioning frequency layer (also referred to as a frequency layer) is a collection of one or more PRS source sets in one or more TRPs that have the same values ​​for certain parameters. Specifically, a collection of PRS source sets has the same subcarrier spacing (SCS) and cyclic prefix (CP) type (meaning all numerologies supported for PDSCH are also supported for PRS), the same Point A, the same downlink PRS bandwidth, the same starting PRB (and center frequency), and the same comb size. The Point A parameter takes the value of the ARFCN-ValueNR parameter (where ARFCN stands for the absolute radio frequency channel number) and is an identifier / code that specifies a pair of physical radio channels used for transmission and reception. The downlink PRS bandwidth may have a granularity of four PRBs, with a minimum of 24 PRBs and a maximum of 272 PRBs.Currently, up to four frequency layers are defined, and up to two PRS source sets can be configured per TRP per frequency layer. The concept of frequency layers is somewhat similar to the concept of component carriers and bandwidth shares (BWP), but differs in that component carriers and BWP are used by a single base station (or macro cell base station and small cell base station) to transmit data channels, while frequency layers are used by multiple (usually three or more) base stations to transmit PRS. The UE can indicate the number of frequency layers it can support when sending its positioning capabilities to the network, such as during an LTE positioning protocol (LPP) session. For example, the UE can indicate whether it can support one or four positioning frequency layers. Figure 4B illustrates an example of multiple channels in the downlink slot of a radio frame. In NR, the channel bandwidth, or system bandwidth, is divided into multiple BWPs. BWPs are contiguous sets of PRBs selected from a contiguous subset of common RBs for a given numerology on a given carrier. Typically, a maximum of four BWPs can be defined in the downlink and uplink. This means that a UE can be configured with up to four BWPs on the downlink and up to four BWPs on the uplink. Only one BWP (uplink or downlink) can be active at any given time, meaning the UE can only receive or transmit through one BWP at a time. On the downlink, the bandwidth of each BWP must be equal to or greater than the SSB bandwidth, but the BWP may or may not contain SSB. Referring to Figure 4B, the primary synchronization signal (PSS) is used by the UE to determine the subframe / symbol timing and the physical layer identity. The secondary synchronization signal (SSS) is used by the UE to determine the physical layer cell identity group number and the radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the PCI. Based on the PCI, the UE can determine the location of the DL-RS. The physical broadcast channel (PBCH), which carries the MIB, can be logically grouped with the PSS and SSS to form an SSB (also referred to as SS / PBCH). The MIB provides a number of RBs in the downlink system bandwidth and a system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted over the PBCH, such as system information blocks (SIBs), and numbering messages. The physical downlink control channel (PDCCH) carries downlink control information (DCI) in one or more control channel elements (CCEs), each CCE comprising one or more RE group bundles (REGs) (which can span multiple symbols in the time domain), each REG bundle comprising one or more REGs, each REG corresponding to 12 source elements (one source block) in the frequency domain and one OFDM symbol in the time domain. The physical source set used to carry the PDCCH / DCI is referred to in NR as a control source set (CORESET). In NR, the PDCCH is limited to one CORESET and is transmitted with its own DMRS. This allows the formation of a UE-specific beam for the PDCCH. In the example in Figure 4B, there is one CORESET per BWP, and the CORESET spans three symbols (although it can be as little as one or two symbols) in the time domain. Unlike the LTE control channel, which occupies the entire system bandwidth, in NR, the PDCCH channel is localized to a specific region in the frequency domain (i.e., the CORESET). Thus, the frequency components of the PDCCH shown in Figure 4B are illustrated as less than one BWP in the frequency domain. Note that although the illustrated CORESETs are contiguous in the frequency domain, this need not be the case. Furthermore, CORESETs can span less than three symbols in the time domain. The DCI in the PDCCH carries information about uplink resource allocation (persistent and non-persistent) and a description of the downlink data transmitted to the UE. Multiple (for example, up to eight) DCIs can be configured in the PDCCH, and these DCIs can have one of several formats. For example, there are different DCI formats for uplink scheduling, for non-MIMO downlink scheduling, for MIMO downlink scheduling, and for uplink power control. The PDCCH can carry 1, 2, 4, 8, or 16 CCEs to accommodate different DCI payload sizes or coding rates. A positioning reference signal is defined for NR positioning to enable the UE to detect and measure more neighboring TRPs. Multiple configurations are supported to enable various deployments, such as indoor, outdoor, sub-6, and millimeter-wave (mmW) deployments. Both UE-based and UE-based position calculations are supported: Table 2 UE Measurement Reference Signal Positioning technique PRS DL RSTD DL DL-TDOA PRS DL RSRP PRS DL DL-TDOA, DL-AoD, Multi-RTT PRS / SRS DL for positioning UE Rx-Tx time difference Multi-RTT SSB / CSI-RS for RRM SS-RSRP (for RRM), SS-RSRQ (for RRM), CSI-RSRP (for RRM), CSI-RSRQ (for RRM) E-CID In a conventional system, the UE will report its capability to process PRS sources in a capability update, and then receive assistance data (AD) from a network entity (for example, from a location server) that lists DL-PRS sources, sorted in descending order of measurement priority. Since the AD typically lists more PRS sources than the UE can handle, the UE will, by agreement, select the first N PRS sources from the list to process, where N is the number of PRS sources the UE can handle. For example, the AD may list twenty DL-PRS sources but the UE can only process five of them. By agreement, The UE will select the first five PRS sources for processing. AD prioritizes PRS sources based solely on PRS measurements. However, to perform Rx-Tx measurements, the UE must perform both PRS measurements and SRS transmissions, and to obtain accurate Rx-Tx measurements, the PRS and SRS must be close in time, e.g., to minimize errors due to possible clock drift between the UE and the base station. The current standard states that the PRS and SRS must not be separated by more than 25 milliseconds (msec), but other proximity requirements, for example, 20 msec, 80 msec, 160 msec, and so on, are also intended. Figure 5 shows an example scenario where the PRS events (PRS0, PRS1, and PRS2) have different periods from the SRS events (SRS0 and SRS1). As a result, some PRS-SRS pairs do not satisfy the proximity requirement. In Figure 5, for example, the pairs {PRS0,SRS0} and {PRS2,SRS1} satisfy the proximity requirement, but the pairs {PRS1,SRS0} and {PRS1,SRS1} do not. One issue is that PRS sources are provided to the UE by the location server but the SRS configuration is provided to the UE by the serving base station, for example, via radio source control (RRC) messages. The location server is unaware of the SRS scheduling, and prioritizes PRS sources only on PRS measurements without considering SRS. As a result, when the UE selects the first N PRS sources defined in the AD per the agreement described above, some of the selected PRS sources may not meet the PRS-SRS proximity requirements. In Figure 5, for example, PRS1 can be included in the first N PRS sources defined in the AD but PRS1 does not meet the proximity requirements and thus should not be used for Rx-Tx measurements. Several approaches to this issue are being considered. One approach being considered is to apply the proximity time requirement only if there is an SRS transmission within 25 ms from at least one PRS DL source of each TRP in the assistance data. Another approach being considered is to apply the proximity time requirement only if there is at least one SRS transmission within the measurement period. Yet another approach being considered is to always apply the proximity time requirement regardless of the time separation between the PRS and SRS, but to require the UE to compensate for the difference in the received time of the radio frame containing the PRS and the subframe used for the SRS transmission. There are drawbacks associated with each of these approaches. The first two approaches ignore the proximity requirement if it cannot be met, essentially rendering it meaningless. The third approach imposes additional burden on the UE to track and compensate for the timing difference between the received PRS and the transmitted SRS. To overcome this drawback, an improved method for performing Rx-Tx measurements is presented here, where the PRS source from the AD is selected based on PRS-SRS proximity, rather than simply selecting the top N PRS sources from the list provided by the AD. Figure 6 illustrates a method 600 equivalent to proximity-based prioritization of UL and DL positioning sources based on aspects of the disclosure. Figure 6 is a signaling message diagram showing the interaction between UE 302, base station (BS) 304, and network entity (NE) 306, which may be a location server (for example, location server 112, LMF 270, or SLP 272). At 602, the network entity 306 requests capability information from the UE 302, and at 604, the UE provides the capability information to the network entity 306. At 606, the UE requests assistance data from the network entity, and at 608, the network entity provides the assistance data to the UE 302. In some aspects, the assistance data includes information identifying a first set of N PRS sources, and also includes M < N parameters. Examples of PRS sources include, but are not limited to, positioning reference signals (PRS), PRS source frames, PRS frequency layers, transmission / reception points (TRPs), cells, or combinations thereof. At 610, the UE receives, from the base station 304, information identifying a second set containing at least one SRS source. This information may be in the form of an SRS configuration, and may be received via RRC. Note that the sequence of signaling messages at 602, 604, 606, 608, and 610 is illustrative and not limiting, i.e., the specific sequence of such elements in Figure 6 may vary. For example, the UE 302 may receive PRS configuration information after receiving an SRS configuration, and vice versa. Similarly, the UE 302 may receive the information in response to a specific request for such information, or may receive the information unilaterally, i.e., without making a specific request for it. At 612, the UE 302 selects a PRS source based on the proximity of each PRS source to the SRS source. In some aspects, the UE 302 selects a PRS source that is within a maximum allowable distance from the SRS source—for example, within a proximity threshold—which the UE 302 may determine based on the PRS and SRS information received from the network entity 306 and the base station 304, respectively. At 614, the UE 302 receives a PRS, and at 616, the UE 302 sends an SRS. In the example illustrated in Figure 6, the PRS and SRS are within the proximity threshold, so at 618, the UE 302 calculates the Rx-Tx and at 620, reports the RxTx value to the base station 304, to the network entity 306, or both. Figure 7A, Figure 7B, Figure 7C, Figure 7D, and Figure 7E are flowcharts showing portions of an example process 700 related to proximity-based uplink and downlink positioning source prioritization, in accordance with aspects of the present disclosure. In some implementations, one or more of the process blocks of FIGS. 7A-7E may be performed by a user equipment (UE) (for example, UE 104). In some implementations, one or more of the process blocks of FIGS. 7A-7E may be performed by another device or group of devices separate from or comprising the UE. Additionally, or alternatively, one or more of the process blocks in Figures 7A-7E may be performed by one or more UE components 302, such as processor 332, memory 340, WWAN transceiver 310, short-range wireless transceiver 320, satellite signal receiver 330, sensor 344, user interface 346, and positioning component 342, any or all of which may be a means of performing process operations 700. As shown in Figure 7A, process 700 may include receiving, from a network entity, first information identifying a positioning reference signal (PRS) source (block 702). The means for performing the operations of block 702 may include a processor 332, a memory 340, or a WWAN transceiver 310 of the UE 302. For example, the UE 302 may receive first information identifying a positioning reference signal (PRS) source using a transceiver, such as a transmitter 314 or a transmitter 324. In some aspects, the network entity comprises a location server. In some aspects, the location server comprises a location management function (LMF) or a secure user plane (SLP) location platform (SUPL). As shown further in Figure 7A, process 700 may include receiving, from the base station, second information identifying the source of the voice reference signal (SRS) (block 704). The means for performing the operations of block 704 may include processor 332, memory 340, or WWAN transceiver 310 of UE 302. For example, UE 302 may receive second information identifying the source voice reference signal (SRS) using a transceiver, such as transmitter 314 or transmitter 324. In some aspects, the base station comprises a gNodeB (gNB). As further shown in Figure 7A, process 700 may include selecting, from the PRS sources identified by the first information, a PRS source that satisfies the PRS-SRS proximity requirements in relation to at least one SRS source identified by the second information (block 706). The means for performing the operations of block 706 may include a processor 332, a memory 340, or a WWAN transceiver 310 of the UE 302. For example, the UE 302 may select a PRS source that satisfies the PRS-SRS proximity requirements in relation to at least one SRS source identified by the second information, using the processor 332 or the positioning component 342, for example, based on information stored in the memory 340.In some aspects, selecting a PRS source that satisfies the PRS-SRS proximity requirement in relation to at least one SRS source identified by the second information comprises selecting a PRS source that has a time difference between the PRS reception and the SRS transmission that does not exceed a maximum time difference threshold. As further shown in Figure 7A, process 700 may include using a selected PRS source to perform at least a UE Rx-Tx measurement (block 708). The means for performing the operation of block 708 may include a processor 332, a memory 340, or a WWAN transceiver 310 of UE 302. For example, UE 302 may use the selected PRS source when performing UE Rx-Tx measurements using signals received by receiver 312 or receiver 322 and signals transmitted by transmitter 314 or transmitter 324. In some aspects, process 700 includes reporting the results of the Rx-Tx measurement to a base station, to a network entity, or to both. As shown in Figure 7B, in some aspects, selecting a PRS source that satisfies the PRS-SRS proximity requirement in relation to at least one SRS source identified by the second information (block 706) comprises selecting, from the PRS sources identified by the first information, a subset of PRS sources according to priority (block 710), and selecting, from the subset of PRS sources, a PRS source based on its time proximity to the SRS source identified by the second information (block 712). As shown in Figure 7C, in some aspects, selecting a subset of PRS sources according to priority (block 710) comprises determining a maximum number M of PRS sources that can be processed by the UE during a predetermined time interval (block 714), and selecting, from the PRS sources identified by the first information, the M highest priority PRS sources as the subset of PRS sources (block 716). As shown in Figure 7D, in some aspects, selecting a PRS source that satisfies the PRS-SRS proximity requirement in relation to at least one of the SRS sources identified by the second information (block 706) comprises identifying, as a first set and from the PRS sources identified by the first information, PRS sources to be considered for use for the Rx-Tx measurement (block 718), identifying, as a second set, one or more pairs of PRS-SRS sources that satisfy the PRS-SRS proximity requirement (block 720), identifying, as a third set, PRS sources from the first set that are part of at least one pair of PRS-SRS sources in the second set (block 722), and selecting some of the PRS sources in the third set (block 724). As shown in Figure 7E, in some aspects, selecting some of the entire PRS sources in the third set (block 724) comprises determining whether the maximum number of PRS sources that can be processed by the UE during a predetermined time interval (M) is less than the number of PRS sources in the third set (N) (block 726). If the UE can process more PRS sources during the specified time interval than in the third set (i.e., M>N), then all PRS sources in the third set are selected (block 728), and additional PRS sources will be selected from the first set until M PRS sources are selected (block 730). If the third set contains more PRS sources than the UE can process during a pre-defined time interval (i.e., M <n), maka dalam beberapa aspek, pasangan sumber prs-srs set kedua diprioritaskan, sebagai contoh, berdasarkan prs kedekatan srs, prioritas prs, dan sebagainya, (blok 732), kemudian dari m pertama dipilih 734).Process 700 may include additional implementations, such as any single implementation or combination of implementations described below and / or in conjunction with one or more other processes described elsewhere herein. Although Figure 7 shows an example of a process block 700, in some implementations, process 700 may include additional blocks, fewer blocks, different blocks, or blocks arranged differently than depicted in Figure 7. Additionally, or alternatively, two or more process blocks 700 may be executed in parallel. Figure 8 is a flowchart in an example process 800 relating to proximity-based prioritization of uplink and downlink positioning sources based on aspects of the disclosure. In some implementations, one or more of the process blocks in Figure 8 may be performed by a network entity (for example, location server 112, location server 230, LMF 270, SLP 272). In some implementations, one or more of the process blocks in Figure 8 may be performed by another device or group of devices separate from or comprising the network entity. Additionally, or alternatively, one or more of the process blocks in Figure 8 may be performed by one or more components of the network entity 306, such as processor 394, memory 396, network transceiver 390, and positioning component 398, any or all of which may be a means of performing the operations of process 800. As shown in Figure 8, process 800 may include transmitting, to a user equipment (UE), first information identifying a positioning reference signal (PRS) source (block 802). The means for performing the operations of block 802 may include a processor 394, a memory 396, or a network transceiver 390 of a network entity 306. For example, the network entity 306 may send the first information using the network transceiver 390. As further shown in Figure 8, process 800 may include transmitting, to the UE, second information specifying a plurality of PRS resources to be used by the UE at least to perform UE Rx-Tx measurements (block 804). The means for performing the operations of block 804 may include processor 394, memory 396, or network transceiver 390 of network entity 306. For example, network entity 306 may send the second information using network transceiver 390. Process 800 may include additional implementations, such as any single implementation or combination of implementations described below and / or in conjunction with one or more other processes described elsewhere herein. Although Figure 8 shows an example of a process block 800, in some implementations, process 800 may include additional blocks, fewer blocks, different blocks, or blocks arranged differently than depicted in Figure 8. Additionally, or alternatively, two or more process blocks 800 may be executed in parallel. In the detailed description above, it can be seen that different features are grouped together in examples. This manner of expression should not be understood to mean that the example clauses have more features than are explicitly mentioned in each clause. On the contrary, various aspects of the disclosure may include fewer than all the features of the individual example clauses disclosed. Therefore, the following clauses are hereby considered to be combined in the description, each clause by itself being able to stand as a separate example. Although each dependent clause may refer in a clause to a specific combination with one of the other clauses, the aspects of the dependent clause are not limited to that specific combination.It will be understood that other examples of clauses may also include combinations of aspects of a dependent clause with the subject matter of other dependent or independent clauses or combinations of any features with other dependent and independent clauses. The various aspects expressed herein expressly include these combinations, unless it is explicitly stated or it can be readily inferred that the specific combination is not intended (for example, contradictory aspects, such as defining elements as insulators and conductors). In addition, it is also intended that aspects of a clause may be included in other independent clauses, even though those clauses are not directly dependent in the independent clause. Examples of implementation are described in the following numbered clauses: Clause 1. A method of wireless communication carried out by user equipment (UE), the method comprising: receiving, from a network entity, first information identifying a positioning reference signal (PRS) source; receiving, from a base station, second information identifying a voice reference signal (SRS) source; selecting, from the PRS sources identified by the first information, a PRS source that satisfies the PRS-SRS proximity requirement in relation to at least one SRS source identified by the second information; and using the selected PRS source to perform at least one UE Rx-Tx measurement. Clause 2. The method in clause 1, wherein selecting, from the PRS sources identified by the first information, a PRS source that satisfies the PRS-SRS proximity requirement in relation to at least one of the SRS sources identified by the second information comprises selecting a PRS source having a time difference between the PRS reception and the SRS transmission that does not exceed a maximum time difference threshold. Clause 3. The method in any one of clauses 1 to 2, wherein selecting, from the PRS sources identified by the first information, a PRS source that satisfies the PRS-SRS proximity requirement in relation to at least one SRS source identified by the second information comprises: selecting, from the PRS sources identified by the first information, a subset of the PRS sources based on priority; and selecting, from the subset of the PRS sources, the PRS source based on its time proximity to the SRS source identified by the second information. Clause 4. The method in clause 3, wherein selecting, from the PRS sources identified by the first information, a subset of PRS sources according to priority: determining a maximum number M of PRS sources that may be processed by the UE during a predetermined time interval; and selecting, from the PRS sources identified by the first information, the M highest priority PRS sources as the subset of PRS sources. Clause 5. The method in any one of clauses 1 to 4, further comprising reporting the results of the Rx-Tx measurements to a base station, to a network entity, or to both. Clause 6. The method in any of clauses 1 to 5, wherein selecting, from the PRS sources identified by the first information, a PRS source that satisfies the PRS-SRS proximity requirement in relation to at least one of the SRS sources identified by the second information comprises: identifying, as a first set and from the PRS sources identified by the first information, the PRS sources to be considered for use for Rx-Tx measurements; identifying, as a second set, one or more pairs of PRS-SRS sources that satisfy the PRS-SRS proximity requirement; and identifying, as a third set, the PRS sources from the first set that are part of at least one pair of PRSSRS sources in the second set. Clause 7. The method in clause 6, wherein identifying, as a second set, one or more PRS-SRS source pairs that satisfy the PRS-SRS proximity requirement further comprises prioritizing the PRS-SRS source pairs in the second set based on proximity; and wherein identifying, as a third set, the PRS sources from the first set that are part of at least one PRSSRS source pair in the second set comprises: determining a maximum number M of PRS sources that may be processed by the UE during a predetermined interval of time; upon determining that the third set contains a number of PRS sources greater than or equal to M, selecting the first M PRS sources in the third set; and upon determining that the third set contains a number L of PRS sources less than M, selecting the PRS sources in the third set and using additional ML PRS sources from the first set. Clause 8. The method in any one of clauses 1 to 7, wherein the network entity comprises a location server. Clause 9. The method in clause 8, wherein the location server comprises a location management function (LMF) or a location platform - secure user plane (SUPL) location (SLP). Clause 10. The method in any one of clauses 1 to 9, wherein the base station comprises a gNodeB (gNB). Clause 11. A method of wireless communication carried out by a network entity, the method comprising: transmitting, to a user equipment (UE), first information identifying a positioning reference signal (PRS) source; and transmitting, to the UE, second information specifying a plurality of PRS sources to be used by the UE at least to perform UE Rx-Tx measurements. Clause 12. The method in clause 11, wherein the network entity comprises location servers. Clause 13. The method in clause 12, wherein the location server comprises a location management function (LMF) or a location platform - secure user plane (SUPL) location (SLP). Clause 14. User equipment (UE), comprising: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and at least one transceiver, the at least one processor being configured to: receive, via the at least one transceiver, from a network entity, first information identifying a positioning reference signal (PRS) source; receive, via the at least one transceiver, from a base station, second information identifying a voice reference signal (SRS) source; select, from the PRS sources identified by the first information, a PRS source that satisfies the PRS-SRS proximity requirements in conjunction with the at least one second piece of information; and use the SRS sources identified by the selected at least one PRS source to perform UE Rx-Tx measurements. Clause 15. The UE in clause 14, wherein, in order to select, from the PRS sources identified by the first information, a PRS source that satisfies the PRS-SRS proximity requirements in relation to the at least one SRS source identified by the second information, the at least one processor is configured to select the PRS source that has a time difference between the PRS reception and the SRS transmission that does not exceed a maximum time difference threshold. Clause 16. The UE in any one of clauses 14 to 15, wherein, in order to select, from the PRS sources identified by the first information, a PRS source that satisfies the PRS-SRS proximity requirements in relation to at least one SRS source identified by the second information, the at least one processor is configured to: select, from the PRS sources identified by the first information, a subset of PRS sources based on priority; and select, from the subset of PRS sources, a PRS source based on its time proximity to the SRS source identified by the second information. Clause 17. The UE in clause 16, wherein it selects, from the PRS sources identified by the first information, a subset of PRS sources according to priority: determines the maximum number M of PRS sources that may be processed by the UE during a predetermined time interval; and selects, from the PRS sources identified by the first information, the highest priority PRS sources M as a subset of PRS sources. Clause 18. The UE in any one of clauses 14 to 17, wherein the at least one processor is further configured to report the Rx-Tx measurement results to a base station, to a network entity, or to both. Clause 19. The UE in any one of clauses 14 to 18, wherein, in order to select, from the PRS sources identified by the first information, a PRS source that satisfies the PRS-SRS proximity requirement in relation to at least one of the SRS sources identified by the second information, the at least one processor is configured to: identify, as a first set and from the PRS sources identified by the first information, the PRS sources to be considered for use for the Rx-Tx measurement; identify, as a second set, one or more pairs of PRS-SRS sources that satisfy the PRS-SRS proximity requirement; and identify, as a third set, the PRS sources from the first set that are part of at least one pair of PRSSRS sources in the second set. Clause 20. The UE in clause 19, wherein, in order to identify, as a second set, one or more PRS-SRS source pairs that satisfy the PRS-SRS proximity requirements, at least one processor is configured to prioritize PRS-SRS source pairs in the second set based on proximity; and wherein, in order to identify, as a third set, PRS sources from the first set that are part of at least one PRSSRS source pair in the second set, at least one processor is configured to: determine a maximum number M of PRS sources that the UE may process during a pre-defined time interval; upon determining that the third set contains a number of PRS sources greater than or equal to M, select the first M PRS sources in the third set; and upon determining that the third set contains a number L of PRS sources less than M, select the PRS sources in the third set and use an additional ML PRS sources from the first set. Clause 21. UE in any of clauses 14 to 20, where the network entity comprises a location server. Clause 22. The UE in clause 21, where the location server comprises a location management function (LMF) or a location platform - secure user plane (SUPL) location (SLP). Clause 23. The UE in any of clauses 14 to 22, wherein the base station comprises a gNodeB (gNB). Clause 24. A network entity, comprising: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and at least one transceiver, the at least one processor being configured to: transmit, via the at least one transceiver, to a user equipment (UE), first information identifying a positioning reference signal (PRS) source; and transmit, via the at least one transceiver, to the UE, second information specifying a number of PRS sources to be used by the UE at least to perform UE Rx-Tx measurements. Clause 25. Network entity in clause 24, where the network entity consists of a location server. Clause 26. The network entity in clause 25, where the location server comprises a location management function (LMF) or a location platform - secure user plane (SUPL) location (SLP). Clause 27. User equipment (UE), comprising: means for receiving, from a network entity, first information identifying a positioning reference signal (PRS) source; means for receiving, from a base station, second information identifying a voice reference signal (SRS) source; means for selecting, from the PRS sources identified by the first information, a PRS source that satisfies the PRS-SRS proximity requirements in relation to at least one SRS source identified by the second information; and means for using the selected PRS source to perform at least one UE Rx-Tx measurement. Clause 28. The EU in clause 27, wherein means for selecting, from the PRS sources identified by the first information, the PRS source that satisfies the PRS-SRS proximity requirements in relation to at least one of the sources The SRS identified by the second information, comprises means for selecting a PRS source that has a time difference between the PRS reception and the SRS transmission that does not exceed a maximum time difference threshold. Clause 29. The UE in any one of clauses 27 to 28, wherein the means for selecting, from the PRS sources identified by the first information, a PRS source that satisfies the PRS-SRS proximity requirement in relation to at least one SRS source identified by the second information, comprises: means for selecting, from the PRS sources identified by the first information, a subset of the PRS sources based on priority; and means for selecting, from the subset of the PRS sources, the PRS source based on its time proximity to the SRS source identified by the second information. Clause 30. The UE in clause 29, wherein the means for selecting, from the PRS sources identified by the first information, a subset of PRS sources based on priority comprises: means for determining the maximum number M of PRS sources that the UE may process during a predetermined time interval; and means for selecting, from the PRS sources identified by the first information, the M highest priority PRS sources as the subset of PRS sources. Clause 31. The UE in any one of clauses 27 to 30, further comprises reporting the Rx-Tx measurement results to the base station, to the network entity, or to both. Clause 32. The UE in any one of clauses 27 to 31, wherein the means for selecting, from the PRS sources identified by the first information, the PRS sources that satisfy the PRS-SRS proximity requirements in relation to at least one of the SRS sources identified by the second information, comprises: means for identifying, as a first set and from the PRS sources identified by the first information, the PRS sources to be considered for use for the Rx64 measurement Tx; means for identifying, as a second set, one or more PRS-SRS source pairs that satisfy the PRS-SRS proximity requirements; and means for identifying, as a third device, a PRS source of the first device that is part of at least one PRS-SRS source pair of the second device. Clause 33. The UE in clause 32, wherein the means for identifying, as a second set, one or more PRS-SRS source pairs that satisfy the PRS-SRS proximity requirement, further comprises means for prioritizing the PRS-SRS source pairs in the second set based on proximity; and wherein the means for identifying, as a third device, the PRS sources of the first device that are part of at least one PRS-SRS source pair in the second set comprise: means for determining the maximum number M of PRS sources that the UE may process during a predetermined time interval; means for, upon determining that the third set contains a number of PRS sources greater than or equal to M, selecting the first M PRS sources in the third set; and means for, upon determining that the third set contains a number L of PRS sources less than M, selecting the PRS sources in the third set and using additional M L PRS sources from the first set. Clause 34. UE in any of clauses 27 to 33, where the network entity comprises a location server. Clause 35. The UE in clause 34, where the location server comprises a location management function (LMF) or a location platform - secure user plane (SUPL) location (SLP). Clause 36. UE in any one of clauses 27 to 35, wherein the base station comprises a gNodeB (gNB). Clause 37. A network entity, comprising: means for transmitting, to a user equipment (UE), first information identifying a positioning reference signal (PRS) source; and means for transmitting, to the UE, second information specifying a number of PRS sources to be used by the UE at least to perform UE Rx-Tx measurements. Clause 38. Network entity in clause 37, where the network entity consists of a location server. Clause 39. The network entity in clause 38, where the location server comprises a location management function (LMF) or a location platform - secure user plane (SUPL) location (SLP). Clause 40. Non-transient computer-readable medium storing computer-executable instructions that, when executed by user equipment (UE), cause the UE to: receive, from a network entity, first information identifying a positioning reference signal (PRS) source; receive, from a base station, second information identifying a voice reference signal (SRS) source; select, from the PRS sources identified by the first information, a PRS source that satisfies the PRS-SRS proximity requirements in relation to at least one SRS source identified by the second information; and use the selected PRS source to perform at least one UE Rx-Tx measurement. Clause 41. Non-transient computer-readable media that stores computer-executable instructions that, when executed by a network entity, cause the network entity to: transmit, to the user equipment (UE), first information identifying a positioning reference signal (PRS) source; and send, to the UE, second information specifying a number of PRS sources to be used by the UE at least to perform UE Rx-Tx measurements. Clause 40. The apparatus comprises a memory, a transceiver, and a processor communicatively coupled to the memory and the transceiver, the memory, the transceiver, and the processor configured to perform a method according to any one of clauses 1 to 13. Clause 41. Equipment consists of means for carrying out a method based on one of paragraphs 1 to 13. Clause 42. A non-transient computer-readable medium for storing computer-executable instructions, the computer-executable comprising at least one instruction for causing a computer or processor to perform a method in accordance with any of clauses 1 to 13. Other aspects include, but are not limited to, the following: In an aspect, a method of wireless communication performed by a user equipment (UE) includes receiving, from a network entity, information identifying a positioning reference signal (PRS) source; receiving, from a base station, information identifying a voice reference signal (SRS) source; selecting a PRS source based on its temporal proximity to the SRS source; and using the selected PRS source to perform at least UE Rx-Tx measurements. In some aspects, reporting RxTx measurement results to the base station, to the network entity, or to both. In some aspects, the method includes receiving information identifying a PRS source comprising receiving information identifying a first set of N positioning reference signal (PRS) sources and M < N parameters; receiving information identifying an SRS source comprising receiving information identifying a second set of at least one voice reference signal (SRS) source; selecting a PRS source based on its proximity to the SRS source comprising: identifying, from the first set and the second set, a third set of L PRS-SRS source pairs that satisfy the PRS-SRS proximity requirement; defining, from the first set of N PRS sources, a fourth set of M PRS sources considered to be used for the Rx-Tx measurement; and identifying, as a fifth set, a PRS-SRS pair of the third set whose PRS source is a member of the fourth set;and using the selected PRS source at least to perform UE Rx-Tx measurements consists of using the fifth set for Rx-Tx measurements.; In some aspects, the PRS-SRS proximity requirement consists of a maximum time difference between PRS reception and SRS transmission. In some aspects, the maximum time difference is + / - 25 milliseconds. In some aspects, the PRS-SRS pairs in the fifth set are prioritized based on proximity. In some aspects, using a fifth set for Rx-Tx measurements comprises: comparing a size K of the fifth set with a PRS processing capability J of the UE; upon determining that K ^ J, using a first J PRSSRS pair in the fifth set; and upon determining that K < J, using a PRS-SRS pair in the fifth set and using an additional J - K PRS source from the first set. In some aspects, J indicates the maximum number of PRS resources that can be processed by the UE at one time. In some aspects, the network entity consists of location servers. In some aspects, a location server comprises a location management function (LMF) or a location platform (SUPL) of a secure user plane (SLP). In some aspects, the base station consists of a gNodeB (gNB). In an aspect, a wireless communication method performed by a network entity includes transmitting, to a user equipment (UE), information identifying a first set of N positioning reference signal (PRS) sources; and transmitting, to the UE, M < N parameters that specify a plurality of PRS sources to be used by the UE at least to perform UE Rx-Tx measurements. In some aspects, the network entity consists of location servers. In some aspects, a location server comprises a location management function (LMF) or a location platform (SUPL) of a secure user plane (SLP). In an aspect, a user equipment (UE) includes memory; at least one transceiver; and at least one processor communicatively coupled to the memory and at least one transceiver, the at least one processor being configured to: receive, from a network entity, information identifying a positioning reference signal (PRS) source; receive, from a base station, information identifying a voice reference signal (SRS) source; select a PRS source based on its temporal proximity to the SRS source; and use the selected PRS source to perform at least UE Rx-Tx measurements. In some aspects, the at least one processor is further configured to report the results of the Rx-Tx measurements to a base station, to a network entity, or to both. In some aspects, the method includes receiving information identifying a PRS source comprising receiving information identifying a first set of N positioning reference signal (PRS) sources and parameters M < N; receiving information identifying an SRS source comprising receiving information identifying a second set of at least one voice reference signal (SRS) source; and selecting a PRS source based on its proximity to the SRS source comprising: identifying, from the first set and the second set, a third set of L PRS-SRS source pairs that satisfy the PRS-SRS proximity requirement; defining, from the first set of N PRS sources, a fourth set of M PRS sources considered to be used for Rx-Tx measurements; and identifying, as a fifth set, PRS-SRS pairs from the third set whose PRS source is a member of the fourth set; and using the selected PRS source for Rx-Tx measurements comprising using the fifth set for Rx-Tx measurements. In some aspects, the PRS-SRS proximity requirement consists of a maximum time difference between PRS reception and SRS transmission. In some aspects, the maximum time difference is + / - 25 milliseconds. In some aspects, the PRS-SRS pairs in the fifth set are prioritized based on proximity. In some aspects, using a fifth set for Rx-Tx measurements comprises: comparing a size K of the fifth set with a PRS processing capability J of the UE; upon determining that K k J, using a first J PRSSRS pair in the fifth set; and upon determining that K < J, using a PRS-SRS pair in the fifth set and using an additional J - K PRS sources from the first set. In some aspects, J indicates the maximum number of PRS resources that can be processed by the UE at one time. In some aspects, the network entity consists of location servers. In some aspects, a location server comprises a location management function (LMF) or a location platform (SUPL) of a secure user plane (SLP). In some aspects, the base station consists of a gNodeB (gNB). In an aspect, a network entity includes memory; at least one network interface; and at least one processor communicatively coupled to the memory and the at least one network interface, the at least one processor being configured to: cause the at least one network interface to send, to a user equipment (UE), information identifying a first set of N positioning reference signal (PRS) sources; and cause the at least one network interface to send, to the UE, M < N parameters that determine a plurality of PRS sources to be used by the UE to perform at least one UE Rx-Tx measurement. In some aspects, the network entity consists of location servers. In some aspects, a location server comprises a location management function (LMF) or a location platform (SUPL) of a secure user plane (SLP). In an aspect, user equipment (UE) includes means for receiving, from a network entity, information identifying a positioning reference signal (PRS) source; means for receiving, from a base station, information identifying a voice reference signal (SRS) source; means for selecting a PRS source based on its temporal proximity to the SRS source; and means for using the selected PRS source to perform at least UE Rx-Tx measurements. In an aspect, a network entity includes means for transmitting, to a user equipment (UE), information identifying a first set of N positioning reference signal (PRS) sources; and means for transmitting, to the UE, M < N parameters specifying a plurality of PRS sources to be used by the UE at least to perform UE Rx-Tx measurements. In an aspect, a non-transient computer-readable medium storing computer-executable instructions includes at least one instruction instructing a user equipment (UE) to receive, from a network entity, information identifying a positioning reference signal (PRS) source; at least one instruction instructing the UE to receive, from a base station, information identifying a voice reference signal (SRS) source; at least one instruction instructing the UE to receive a selected PRS source based on time proximity to the SRS source; and at least one instruction instructing the UE to receive using the selected PRS source at least to perform UE Rx-Tx measurements. In an aspect, a non-transient computer-readable medium storing computer-executable instructions includes at least one instruction that instructs the network entity to send, to a user equipment (UE), information that identifies a first set of N positioning reference signal (PRS) sources; and at least one instruction that instructs the network entity to send, to the UE, M < N parameters that specify a plurality of PRS sources to be used by the UE to perform at least UE Rx-Tx measurements. Those skilled in this area will appreciate that information and signals can be represented using any of a variety of different technologies and techniques. For example, the data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the above description can be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or combinations thereof. Furthermore, those skilled in the art will appreciate that the various illustrative logic blocks, modules, circuits, and algorithmic steps described in connection with the aspects disclosed herein may be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this hardware-software interchangeability, the various illustrative components, blocks, modules, circuits, and steps have been described above in general terms in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the particular application and the design constraints imposed on the overall system. A skilled craftsman may implement the described functionality in a variety of ways for any particular application, but such implementation decisions should not be construed as causing a departure from the scope of this disclosure. The various illustrative logic blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented or performed with general-purpose processors, DSPs, ASICs, FPGAs, or other programmable logic devices, discrete gates or transistor logic, discrete hardware components, or combinations thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but alternatively, it may be a conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or other such configurations. The methods, sequences, and / or algorithms described in connection with the aspects disclosed herein may be embodied directly in hardware, in software modules executed by the processor, or in a combination of both. The software modules may reside in random access memory (RAM), flash memory, read-only memory (ROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), registers, hard disks, removable disks, CD-ROMs, or other forms of storage media known in the art. Example storage media are coupled to the processor so that the processor can read information from, and write information to, the storage media. Alternatively, the storage media may be an integral part of the processor. The processor and storage media may reside in an ASIC. The ASIC may reside in a user terminal (for example, a UE).Alternatively, the processor and storage media can be placed as discrete components in the user terminal. In one or more exemplary aspects, the described functionality may be implemented in hardware, software, firmware, or a combination thereof. If implemented in software, the functionality may be stored or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable medium includes computer storage media and communication media includes any medium that facilitates the transfer of computer programs from one location to another. The storage medium may be any available medium that is accessible to a computer.By way of example, and not as a limitation, such computer-readable media may consist of RAM, ROM, EEPROM, CDROM or other optical disk storage, magnetic disk storage or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and is accessible by a computer. Also, any connection is properly referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technology such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technology such as infrared, radio, and microwave are included in the definition of medium.Disks and discs, as used herein, include compact discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs, where discs typically reproduce data magnetically, while discs typically reproduce data optically with a laser. Combinations of the above shall also be included within the scope of computer-readable media. While the foregoing disclosures are illustrative aspects of the disclosure, it should be noted that various changes and modifications may be made herein without departing from the scope of the disclosure as defined by the appended claims. The functions, steps, and / or actions of the method claims in accordance with the aspects of the disclosure described herein need not be performed in any particular order. Furthermore, although elements of the disclosure may be described or claimed in the singular, the plural is intended unless a limitation on the singular is explicitly stated.

Claims

Claim:

1. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving, from a network entity, first information identifying a positioning reference signal (PRS) source; receiving, from a base station, second information identifying a voice reference signal (SRS) source; selecting, from the PRS sources identified by the first information, a PRS source that satisfies a PRS-SRS proximity requirement in relation to at least one SRS source identified by the second information; and using the selected PRS source to perform at least one UE Rx-Tx measurement.

2. The method of claim 1, wherein selecting, from the PRS sources identified by the first information, a PRS source that satisfies the PRS-SRS proximity requirement in relation to the at least one SRS source identified by the second information, comprises selecting a PRS source that has a time difference between the PRS reception and the SRS transmission that does not exceed a maximum time difference threshold.

3. The method of claim 1, wherein selecting, from the PRS sources identified by the first information, a PRS source that satisfies the PRS-SRS proximity requirement in relation to at least one SRS source identified by the second information, comprises: selecting, from the PRS sources identified by the first information, a subset of the PRS sources based on priority; and selecting, from the subset of the PRS sources, the PRS source based on its time proximity to the at least one SRS source identified by the second information.

4. The method of claim 3, wherein selecting, from the PRS sources identified by the first information, a subset of PRS sources based on priority comprises: determining a maximum number M of PRS sources that may be processed by the UE during a pre-defined time interval; and selecting, from the PRS sources identified by the first information, the M highest priority PRS sources as the subset of PRS sources.

5. The method of claim 1, further comprising reporting the Rx-Tx measurement results to a base station, to a network entity, or to both.

6. The method of claim 1, wherein selecting, from the PRS sources identified by the first information, a PRS source that satisfies the PRS-SRS proximity requirement in relation to at least one SRS source identified by the second information, comprises: identifying, as a first set and from the PRS sources identified by the first information, the PRS sources to be considered for use for the RxTx measurement; identifying, as a second set, one or more pairs of PRS-SRS sources that satisfy the PRS-SRS proximity requirement; and identifying, as a third set, the PRS sources from the first set that are part of at least one pair of PRS-SRS sources in the second set.

7. The method of claim 6, wherein identifying, as a second set, one or more PRS-SRS source pairs that satisfy the PRS-SRS proximity requirement in relation to at least one SRS source identified by the second information, further comprising prioritizing the PRS-SRS source pairs in the second set based on proximity; and wherein identifying, as a third set, the PRS sources from the first set that are part of the at least one PRS-SRS source pair in the second set comprises: determining a maximum number M of PRS sources that can be processed by the UE during a pre-defined time interval; upon determining that the third set contains a number of PRS sources greater than or equal to M, selecting the first M PRS sources in the third set; and upon determining that the third set contains a number L of PRS sources less than M, selecting the PRS sources in the third set and using additional ML PRS sources from the first set.

8. The method of claim 1, wherein the network entity comprises a location server.

9. The method of claim 8, wherein the location server comprises a location management function (LMF) or a location platform - a secure user plane (SUPL) location (SLP).

10. The method of claim 1, wherein the base station comprises a gNodeB (gNB).

11. A wireless communication method performed by a network entity, the method comprising: transmitting, to a user equipment (UE), first information identifying a positioning reference signal (PRS) source; and transmitting, to the UE, second information specifying a plurality of PRS sources to be used by the UE at least to perform UE Rx-Tx measurements.

12. The method of claim 11, wherein the network entity comprises a location server.

13. The method of claim 12, wherein the location server comprises a location management function (LMF) or a location platform - a secure user plane (SUPL) location (SLP).

14. User equipment (UE), comprising: memory; at least one transceiver; and at least one processor communicatively coupled to the memory and at least one transceiver, the at least one processor being configured to: receive, via the at least one transceiver, from a network entity, first information identifying a positioning reference signal (PRS) source; receive, via the at least one transceiver, from a base station, second information identifying a voice reference signal (SRS) source; select, from the PRS sources identified by the first information, a PRS source that satisfies the PRS-SRS proximity requirements in relation to the at least one SRS source identified by the second information; and use the selected PRS source to perform UE Rx-Tx measurements.

15. The UE of claim 14, wherein, to select, from the PRS sources identified by the first information, a PRS source that satisfies the PRS-SRS proximity requirement in relation to the at least one SRS source identified by the second information, the at least one processor is configured to select the PRS source that has a time difference between the PRS reception and the SRS transmission that does not exceed a maximum time difference threshold.

16. The UE of claim 14, wherein, to select, from the PRS sources identified by the first information, a PRS source that satisfies the PRS-SRS proximity requirement in relation to the at least one SRS source identified by the second information, the at least one processor is configured to: select, from the PRS sources identified by the first information, a subset of the PRS sources based on priority; and select, from the subset of the PRS sources, the PRS source based on its time proximity to the at least one SRS source identified by the second information.

17. The UE of claim 16, wherein selecting, from the PRS sources identified by the first information, a subset of PRS sources based on priority comprises: determining a maximum number M of PRS sources that may be processed by the UE during a pre-defined time interval; and selecting, from the PRS sources identified by the first information, the M highest priority PRS sources as the subset of PRS sources.

18. The UE of claim 14, wherein the at least one processor is further configured to report the Rx-Tx measurement results to a base station, to a network entity, or to both.

19. The UE of claim 14, wherein, to select, from the PRS sources identified by the first information, PRS sources that satisfy the PRS-SRS proximity requirements in relation to the at least one SRS source identified by the second information, the at least one processor is configured to: identify, as a first set and from the PRS sources identified by the first information, the PRS sources to be considered for use for the RxTx measurement; identify, as a second set, one or more pairs of PRS-SRS sources that satisfy the PRS-SRS proximity requirements; and identify, as a third set, PRS sources from the first set that are part of the at least one pair of PRS-SRS sources in the second set.

20. The UE of claim 19, wherein, to identify, as a second set, one or more PRS-SRS source pairs that satisfy the PRS-SRS proximity requirement in relation to at least one SRS source identified by the second information, the at least one processor is configured to prioritize the one or more PRS-SRS source pairs in the second set based on proximity; and wherein, to identify, as a third set, a PRS source from the first set that is part of at least one PRS-SRS source pair in the second set, the at least one processor is configured to: determine a maximum number M of PRS sources that may be processed by the UE during a predefined time interval; upon determining that the third set contains a number of PRS sources greater than or equal to M, select the first M PRS sources in the third set;and when determining that the third set contains a number L of PRS sources less than M, selecting the PRS sources in the third set and using additional PRS sources ML from the first set.; 21. The UE in claim 14, wherein the network entity comprises a location server.

22. The UE of claim 21, wherein the location server comprises a location management function (LMF) or a secure user plane (SUPL) location platform (SLP).

23. The UE in claim 14, wherein the base station comprises a gNodeB (gNB).

24. A network entity, comprising: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and at least one transceiver, the at least one processor being configured to: transmit, via the at least one transceiver, to a user equipment (UE), first information identifying a positioning reference signal (PRS) source; and transmit, via the at least one transceiver, to the UE, second information specifying a plurality of PRS sources to be used by the UE at least to perform UE Rx-Tx measurements.

25. The network entity in claim 24, wherein the network entity comprises a location server.

26. The network entity in claim 25, wherein the location server comprises a location management function (LMF) or a location platform - a secure user plane (SUPL) location (SLP).

27. User equipment (UE), comprising: means for receiving, from a network entity, first information identifying a positioning reference signal (PRS) source; means for receiving, from a base station, second information identifying a voice reference signal (SRS) source; means for selecting, from the PRS sources identified by the first information, a PRS source that satisfies the PRS-SRS proximity requirements in relation to at least one SRS source identified by the second information; and means for using the selected PRS source to perform at least one UE Rx-Tx measurement.

28. The UE of claim 27, wherein the means for selecting, from the PRS sources identified by the first information, a PRS source that satisfies the PRS-SRS proximity requirement in relation to the at least one SRS source identified by the second information, comprises means for selecting the PRS source that has a time difference between the PRS reception and the SRS transmission that does not exceed a maximum time difference threshold.

29. The UE of claim 27, wherein the means for selecting, from the PRS sources identified by the first information, a PRS source that satisfies the PRS-SRS proximity requirement in relation to at least one SRS source identified by the second information, comprises: means for selecting, from the PRS sources identified by the first information, a subset of the PRS sources based on priority; and means for selecting, from the subset of the PRS sources, the PRS source based on its time proximity to the SRS source identified by the second information.

30. The UE of claim 29, wherein the means for selecting, from the PRS sources identified by the first information, a subset of PRS sources based on priority comprises: means for determining a maximum number M of PRS sources that may be processed by the UE during a pre-defined time interval; and means for selecting, from the PRS sources identified by the first information, the M highest priority PRS sources as the subset of PRS sources.

31. The UE in claim 27, further comprising reporting the Rx-Tx measurement results to a base station, to a network entity, or to both.

32. The UE of claim 27, wherein the means for selecting, from the PRS sources identified by the first information, a PRS source that satisfies the PRS-SRS proximity requirement in relation to at least one SRS source identified by the second information, comprises: means for identifying, as a first set and from the PRS sources identified by the first information, the PRS sources to be considered for use for the Rx-Tx measurement; means for identifying, as a second set, one or more pairs of PRS-SRS sources that satisfy the PRS-SRS proximity requirement; and means for identifying, as a third set, the PRS sources from the first set that are part of at least one pair of PRS-SRS sources in the second set.

33. The UE of claim 32, wherein the means for identifying, as a second set, one or more PRS-SRS source pairs that satisfy the PRS-SRS proximity requirements in relation to at least one SRS source identified by the second information, further comprises means for prioritizing the PRS-SRS source pairs in the second set based on proximity; and wherein the means for identifying, as a third device, the PRS sources of the first device that are part of the at least one PRS-SRS source pair in the second set comprises means for: determining a maximum number M of PRS sources that may be processed by the UE during a pre-defined time interval; upon determining that the third set contains a number of PRS sources greater than or equal to M, selecting the first M PRS sources in the third set;and when determining that the third set contains a number L of PRS sources less than M, selecting the PRS sources in the third set and using additional PRS sources ML from the first set.; 34. The UE in claim 27, wherein the network entity comprises a location server.

35. The UE of claim 34, wherein the location server comprises a location management function (LMF) or a secure user plane (SUPL) location platform (SLP).

36. The UE in claim 27, wherein the base station comprises a gNodeB (gNB).

37. A network entity, comprising: means for transmitting, to a user equipment (UE), first information identifying a positioning reference signal (PRS) source; and means for transmitting, to the UE, second information specifying a number of PRS sources to be used by the UE at least to perform UE Rx-Tx measurements.

38. The network entity in claim 37, wherein the network entity comprises a location server.

39. The network entity in claim 38, wherein the location server comprises a location management function (LMF) or a location platform - a secure user plane (SUPL) location (SLP).

40. A non-transient computer-readable medium storing computer-executable instructions that, when executed by user equipment (UE), trigger the UE to: receive, from a network entity, first information identifying a positioning reference signal (PRS) source; receive, from a base station, second information identifying a voice reference signal (SRS) source; select, from the PRS sources identified by the first information, a PRS source that satisfies the PRS-SRS proximity requirements in relation to at least one SRS source identified by the second information; and use the selected PRS source to perform at least one UE Rx-Tx measurement.

41. A non-transient computer-readable medium that stores computer-executable instructions that, when executed by a network entity, cause the network entity to: transmit, to a user equipment (UE), first information identifying a positioning reference signal (PRS) source; and transmit, to the UE, second information specifying a number of PRS sources to be used by the UE at least to perform UE Rx-Tx measurements.

Images