USER EQUIPMENT PROCESSING LOAD-AWARE POSITIONING REFERENCE SIGNAL MEASUREMENT PERIOD OPTIMIZATION BACKGROUND OF THE DISCLOSURE 1. Field of the Disclosure [0001] Aspects of the disclosure relate generally to wireless communications. 2. Description of the Related Art [0002] Wireless communication systems have developed through various generations, including a first-generation analog wireless phone service (1G), a second-generation (2G) digital wireless phone service (including interim 2.5G and 2.75G networks), a third-generation (3G) high speed data, Internet-capable wireless service and a fourth-generation (4G) service (e.g., Long Term Evolution (LTE) or WiMax). There are presently many different types of wireless communication systems in use, including cellular and personal communications service (PCS) systems. Examples of known cellular systems include the cellular analog advanced mobile phone 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), etc. [0003] A fifth generation (5G) wireless standard, referred to as New Radio (NR), enables higher data transfer speeds, greater numbers of connections, and better coverage, among other improvements. The 5G standard, according to the Next Generation Mobile Networks Alliance, is designed to provide higher data rates as compared to previous standards, more accurate positioning (e.g., based on reference signals for positioning (RS-P), such as downlink, uplink, or sidelink positioning reference signals (PRS)), and other technical enhancements. These enhancements, as well as the use of higher frequency bands, advances in PRS processes and technology, and high-density deployments for 5G, enable highly accurate 5G-based positioning. SUMMARY [0004] The following presents a simplified summary relating to one or more aspects disclosed herein. Thus, the following summary should not be considered an extensive overview relating to all contemplated aspects, nor should the following summary be considered to identify key or critical elements relating to all contemplated aspects or to delineate the scope associated with any particular aspect. Accordingly, the following summary has the sole purpose to present 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. [0005] In an aspect, a method of wireless positioning performed by a network entity includes determining that a positioning reference signal (PRS) processing load for a user equipment (UE) exceeds a PRS processing capacity of the UE; and sending, to the UE, assistance data that reduces the PRS processing load for the UE. [0006] In an aspect, a method of wireless positioning performed by a UE includes determining, based on information received from a network entity, that one or more PRS measurements is associated with a low-latency location request; modifying one or more parameters associated with the one or more PRS measurements to reduce measurement latency; and performing the one or more PRS measurements associated with the low-latency location request according to the modified one or more parameters. [0007] In an aspect, a network entity includes a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to: determine that a PRS processing load for a UE exceeds a PRS processing capacity of the UE; and send, via the at least one transceiver, to the UE, assistance data that reduces the PRS processing load for the UE. [0008] In an aspect, a UE includes a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to: determine, based on information received from a network entity, that one or more PRS measurements is associated with a low-latency location request; modify one or more parameters associated with the one or more PRS measurements to reduce measurement latency; and perform the one or more PRS measurements associated with the low-latency location request according to the modified one or more parameters. [0009] Other objects and advantages associated with the aspects disclosed herein will be apparent to those skilled in the art based on the accompanying drawings and detailed description. BRIEF DESCRIPTION OF THE DRAWINGS [0010] The accompanying drawings are presented to aid in the description of various aspects of the disclosure and are provided solely for illustration of the aspects and not limitation thereof. [0011] FIG. 1 illustrates an example wireless communications system, according to aspects of the disclosure. [0012] FIGS.2A and 2B illustrate example wireless network structures, according to aspects of the disclosure. [0013] FIGS. 3A, 3B, and 3C are simplified block diagrams of several sample aspects of components that may be employed in a user equipment (UE), a base station, and a network entity, respectively, and configured to support communications as taught herein. [0014] FIG. 4 is a diagram illustrating an example frame structure, according to aspects of the disclosure. [0015] FIG. 5 is a diagram illustrating various downlink channels within an example downlink slot, according to aspects of the disclosure. [0016] FIG. 6 is a diagram of an example positioning reference signal (PRS) configuration for the PRS transmissions of a given base station, according to aspects of the disclosure. [0017] FIG.7 illustrates a time difference of arrival (TDOA)-based positioning procedure in an example wireless communications system 700, according to aspects of the disclosure. [0018] FIG.8 illustrates an example Long-Term Evolution (LTE) positioning protocol (LPP) call flow between a UE and a location server for performing positioning operations. [0019] FIG. 9 illustrates an example of measuring PRS data during a measurement gap (MG), according to aspects of the disclosure. [0020] FIG. 10 is a time and frequency graph illustrating some of the parameters derived from the assistance data, and their effect on the measurement period, according to aspects of the disclosure. [0021] FIG.11 is a flowchart of an example process, performed by a network entity, associated with UE processing load-aware PRS measurement period optimization, according to aspects of the disclosure. [0022] FIG. 12 is a flowchart of an example process, performed by a UE, associated with UE processing load-aware PRS measurement period optimization, according to aspects of the disclosure. DETAILED DESCRIPTION [0023] Disclosed are techniques for wireless positioning. In an aspect, a network entity may determine that a positioning reference signal (PRS) processing load for a UE exceeds a PRS processing capacity of the UE, which the UE may have sent to the network entity in response to a request from the network entity to the UE. The network entity may send, to the UE, assistance data that reduces the PRS processing load for the UE. In another aspect, a user equipment (UE) may determine, based on information received from a network entity, that one or more PRS measurements is associated with a low-latency location request. The UE may modify one or more parameters associated with the one or more PRS measurements to reduce measurement latency. The UE may perform the one or more PRS measurements associated with the low-latency location request according to the modified one or more parameters. [0024] Aspects of the disclosure are provided in the following description and related drawings directed to various examples provided for illustration purposes. Alternate aspects may be devised without departing from the scope of the disclosure. Additionally, well-known elements of the disclosure will not be described in detail or will be omitted so as not to obscure the relevant details of the disclosure. [0025] The words “exemplary” and/or “example” are used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” and/or “example” is not necessarily to be construed as preferred or advantageous over other aspects. Likewise, the term “aspects of the disclosure” does not require that all aspects of the disclosure include the discussed feature, advantage or mode of operation. [0026] Those of skill in the art will appreciate that the information and signals described below may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description below may 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 corresponding technology, etc. [0027] 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 recognized that various actions described herein can be performed by specific circuits (e.g., application specific integrated circuits (ASICs)) by program instructions being executed by one or more processors, or by a combination of both. Additionally, the sequence(s) of actions described herein can be considered to be embodied entirely within any form of non- transitory computer-readable storage medium having stored therein a corresponding set of computer instructions that, upon execution, would cause or instruct an associated processor of a device to perform the functionality described herein. Thus, the various aspects of the disclosure may be embodied in a number of different forms, all of which have been contemplated to be within the scope of the claimed subject matter. In addition, for each of the aspects described herein, the corresponding form of any such aspects may be described herein as, for example, “logic configured to” perform the described action. [0028] As used herein, the terms “user equipment” (UE) and “base station” are not intended to be specific or otherwise limited to any particular radio access technology (RAT), unless otherwise noted. In general, a UE may be any wireless communication device (e.g., a mobile phone, router, tablet computer, laptop computer, consumer asset locating device, wearable (e.g., smartwatch, glasses, augmented reality (AR) / virtual reality (VR) headset, etc.), vehicle (e.g., automobile, 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 an “access terminal” or “AT,” a “client device,” a “wireless device,” a “subscriber device,” a “subscriber terminal,” a “subscriber station,” a “user terminal” or “UT,” a “mobile device,” a “mobile terminal,” a “mobile station,” or variations thereof. Generally, UEs can communicate with a core network via a RAN, and through the core network the UEs can be connected with external networks such as the Internet and with other UEs. Of course, other mechanisms of connecting to the core network and/or the Internet are also possible for the UEs, such as over wired access networks, wireless local area network (WLAN) networks (e.g., based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 specification, etc.) and so on. [0029] A base station may operate according to one of several RATs in communication with UEs depending on the network in which it is deployed, and may be alternatively referred to as an access point (AP), a network node, a NodeB, an evolved NodeB (eNB), a next generation eNB (ng-eNB), a New Radio (NR) Node B (also referred to as a gNB or gNodeB), etc. A base station may be used primarily to support wireless access by UEs, including supporting data voice and/or signaling connections for the supported UEs In some systems a base station may provide purely edge node signaling functions while in other systems it may provide additional control and/or network management functions. A communication link through which UEs can send signals to a base station is called an uplink (UL) channel (e.g., a reverse traffic channel, a reverse control channel, an access channel, etc.). A communication link through which the base station can send signals to UEs is called a downlink (DL) or forward link channel (e.g., a paging channel, a control channel, a broadcast channel, a forward traffic channel, etc.). As used herein the term traffic channel (TCH) can refer to either an uplink / reverse or downlink / forward traffic channel. [0030] The term “base station” may refer to a single physical transmission-reception 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 an antenna of the base station corresponding to a cell (or several cell sectors) of the base station. Where the term “base station” refers to multiple co-located physical TRPs, the physical TRPs may be an array of antennas (e.g., as in a multiple-input multiple-output (MIMO) system or where the base station employs beamforming) of the base station. Where the term “base station” refers to multiple non-co-located physical TRPs, the physical TRPs 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 radio head (RRH) (a remote base station connected to a serving base station). Alternatively, the non-co-located physical TRPs may be the serving base station receiving the measurement report from the UE and a neighbor base station whose reference radio frequency (RF) signals the UE is measuring. Because 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 are to be understood as referring to a particular TRP of the base station. [0031] In some implementations that support positioning of UEs, a base station may not support wireless access by UEs (e.g., may not support data, voice, and/or signaling connections for UEs), but may instead transmit reference signals to UEs to be measured by the UEs, and/or may receive and measure signals transmitted by the UEs. Such a base station may be referred to as a positioning beacon (e.g., when transmitting signals to UEs) and/or as a location measurement unit (e.g., when receiving and measuring signals from UEs). [0032] An “RF signal” comprises an electromagnetic wave of a given frequency that transports information through the space between a transmitter and a receiver As used herein a transmitter may transmit a single “RF signal” or multiple “RF signals” to a receiver. However, the receiver may receive multiple “RF signals” corresponding to each transmitted RF signal due to the propagation characteristics of RF signals through multipath channels. The same transmitted RF signal on different paths between the transmitter and 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 a wireless signal or an RF signal. [0033] FIG.1 illustrates an example wireless communications system 100, according to aspects of the disclosure. The wireless communications system 100 (which may also be referred to as a wireless wide area network (WWAN)) may include various base stations 102 (labeled “BS”) and various UEs 104. The base stations 102 may include macro cell base stations (high power cellular base stations) and/or small cell base stations (low power cellular base stations). In an aspect, the macro cell base stations may include eNBs and/or ng-eNBs where the wireless communications system 100 corresponds to an LTE network, or gNBs where the wireless communications system 100 corresponds to a NR network, or a combination of both, and the small cell base stations may include femtocells, picocells, microcells, etc. [0034] The base stations 102 may collectively form a RAN and interface with a core network 170 (e.g., an evolved packet core (EPC) or a 5G core (5GC)) through backhaul links 122, and through the core network 170 to one or more location servers 172 (e.g., a location management function (LMF) or a secure user plane location (SUPL) location platform (SLP)). The location server(s) 172 may be part of core network 170 or may be external to core network 170. A location server 172 may be integrated with a base station 102. A UE 104 may communicate with a location server 172 directly or indirectly. For example, a UE 104 may communicate with a location server 172 via the base station 102 that is currently serving that UE 104. A UE 104 may also communicate with a location server 172 through another path, such as via an application server (not shown), via another network, such as via a wireless local area network (WLAN) access point (AP) (e.g., AP 150 described below), and so on. For signaling purposes, communication between a UE 104 and a location server 172 may be represented as an indirect connection (e.g., through the core network 170, etc.) or a direct connection (e.g., as shown via direct connection 128), with the intervening nodes (if any) omitted from a signaling diagram for clarity. [0035] In addition to other functions, the base stations 102 may perform functions that relate to one or more of transferring user data, radio channel ciphering and deciphering, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment trace, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 may communicate with each other directly or indirectly (e.g., through the EPC / 5GC) over backhaul links 134, which may be wired or wireless. [0036] The base stations 102 may wirelessly communicate with the UEs 104. Each of the base stations 102 may provide communication coverage for a respective geographic coverage area 110. In an aspect, one or more cells may be supported by a base station 102 in each geographic coverage area 110. A “cell” is a logical communication entity used for communication with a base station (e.g., over some frequency resource, referred to as a carrier frequency, component carrier, carrier, band, or the like), and may be associated with an identifier (e.g., a physical cell identifier (PCI), an enhanced cell identifier (ECI), a virtual cell identifier (VCI), a cell global identifier (CGI), etc.) for distinguishing cells operating via the same or a different carrier frequency. 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. Because a cell is supported by a specific base station, the term “cell” may refer to either or both of the logical communication entity and the base station that supports it, depending on the context. In addition, because a TRP is typically the physical transmission point of a cell, the terms “cell” and “TRP” may be used interchangeably. In some cases, the term “cell” may also refer to a geographic coverage area of a base station (e.g., a sector), insofar as a carrier frequency can be detected and used for communication within some portion of geographic coverage areas 110. [0037] While neighboring macro cell base station 102 geographic coverage areas 110 may partially overlap (e.g., in a handover region), some of the geographic coverage areas 110 may be substantially overlapped by a larger geographic coverage area 110. For example, a small cell base station 102' (labeled “SC” for “small cell”) may have a geographic coverage area 110' that substantially overlaps with the geographic coverage area 110 of one or more macro cell base stations 102. A network that includes both small cell and macro cell base stations may be known as a heterogeneous network. A heterogeneous network may also include home eNBs (HeNBs), which may provide service to a restricted group known as a closed subscriber group (CSG). [0038] The communication links 120 between the base stations 102 and the UEs 104 may include uplink (also referred to as reverse link) transmissions from a UE 104 to a base station 102 and/or downlink (DL) (also referred to as forward link) transmissions from a base station 102 to a UE 104. The communication links 120 may use MIMO antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity. The communication links 120 may be through one or more carrier frequencies. Allocation of carriers may be asymmetric with respect to downlink and uplink (e.g., more or less carriers may be allocated for downlink than for uplink). [0039] The wireless communications system 100 may further include a wireless local area network (WLAN) access point (AP) 150 in communication with WLAN stations (STAs) 152 via communication links 154 in an unlicensed frequency spectrum (e.g., 5 GHz). When communicating in an unlicensed frequency spectrum, the WLAN STAs 152 and/or the WLAN AP 150 may perform a clear channel assessment (CCA) or listen before talk (LBT) procedure prior to communicating in order to determine whether the channel is available. [0040] The small cell base station 102' may operate in a licensed and/or an unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell base station 102' may employ LTE or NR technology and use the same 5 GHz unlicensed frequency spectrum as used by the WLAN AP 150. The small cell base station 102', employing LTE / 5G in an unlicensed frequency spectrum, may boost coverage to and/or increase capacity of the access network. NR in unlicensed spectrum may be referred to as NR-U. LTE in an unlicensed spectrum may be referred to as LTE-U, licensed assisted access (LAA), or MulteFire. [0041] The wireless communications system 100 may further include a millimeter wave (mmW) base station 180 that may operate in mmW frequencies and/or near mmW frequencies in communication with a UE 182. Extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 millimeter and 10 millimeters Radio waves in this band may be referred to as a millimeter wave. Near mmW may extend down 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 wave. Communications using the mmW/near mmW radio frequency band have high path loss and a relatively short range. The mmW base station 180 and the UE 182 may utilize beamforming (transmit and/or receive) over a mmW communication link 184 to compensate for the extremely high path loss and short range. Further, it will be appreciated that in alternative configurations, one or more base stations 102 may also transmit using mmW or near mmW and beamforming. Accordingly, it will be appreciated that the foregoing illustrations are merely examples and should not be construed to limit the various aspects disclosed herein. [0042] Transmit beamforming is a technique for focusing an RF signal in a specific direction. Traditionally, when a network node (e.g., a base station) broadcasts an RF signal, it broadcasts the signal in all directions (omni-directionally). With transmit beamforming, the network node determines where a given target device (e.g., a UE) is located (relative to the transmitting network node) and projects a stronger downlink RF signal in that specific direction, thereby providing a faster (in terms of data rate) and stronger RF signal for the receiving device(s). To change the directionality of the RF signal when transmitting, a network node can control the phase and relative amplitude of the RF signal at each of the one or more transmitters that are broadcasting the RF signal. For example, a network node may use an array of antennas (referred to as a “phased array” or an “antenna array”) that creates a beam of RF waves that can be “steered” to point in different directions, without actually moving the antennas. Specifically, the RF current from the transmitter is fed to the individual antennas with the correct phase relationship so that the radio waves from the separate antennas add together to increase the radiation in a desired direction, while cancelling to suppress radiation in undesired directions. [0043] Transmit beams may be quasi-co-located, meaning that they appear to the receiver (e.g., a UE) as having the same parameters, regardless of whether or not the transmitting antennas of the network node themselves are physically co-located. In NR, there are four types of quasi-co-location (QCL) relations. Specifically, a QCL relation of a given type means that certain parameters about a second reference RF signal on a second beam can be derived from information about a source reference RF signal on a source beam. Thus, if the source reference RF signal is 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 a second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL Type B, the receiver can use the source reference RF signal to estimate the Doppler shift and Doppler spread of a second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL Type C, the receiver can use the source reference RF signal to estimate the Doppler shift and average delay of a second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL Type D, the receiver can use the source reference RF signal to estimate the spatial receive parameter of a second reference RF signal transmitted on the same channel. [0044] In receive beamforming, the receiver uses a receive beam to amplify RF signals detected on a given channel. For example, the receiver can increase the gain setting and/or adjust the phase setting of an array of antennas in a particular direction to amplify (e.g., to increase the gain level of) the RF signals received from that direction. Thus, when a receiver is said to beamform in a certain direction, it means the beam gain in that direction is high relative to the beam gain along other directions, or the beam gain in that direction is the highest compared to the beam gain in that direction of all other receive beams available to the receiver. This results in a stronger received signal strength (e.g., reference signal received power (RSRP), reference signal received quality (RSRQ), signal-to- interference-plus-noise ratio (SINR), etc.) of the RF signals received from that direction. [0045] Transmit and receive beams may be spatially related. A spatial relation means that parameters for a second beam (e.g., a transmit or receive beam) for a second reference signal can be derived from information about a first beam (e.g., a receive beam or a transmit beam) for a first reference signal. For example, a UE may use a particular receive beam to receive a reference downlink reference signal (e.g., synchronization signal block (SSB)) from a base station. The UE can then form a transmit beam for sending an uplink reference signal (e.g., sounding reference signal (SRS)) to that base station based on the parameters of the receive beam. [0046] Note that a “downlink” beam may be either a transmit beam or a receive beam, depending on the entity forming it. For example, if a base station is forming the downlink beam to transmit a reference signal to a UE, the downlink beam is a transmit beam. If the UE is forming the downlink beam, however, it is a receive beam to receive the downlink reference signal. Similarly, an “uplink” beam may be either a transmit beam or a receive beam, depending on the entity forming it. For example, if a base station is forming the uplink beam, it is an uplink receive beam, and if a UE is forming the uplink beam, it is an uplink transmit beam. [0047] The electromagnetic spectrum is often subdivided, based on frequency/wavelength, into various classes, bands, channels, etc. In 5G NR two initial operating bands have been identified as frequency range designations FR1 (410 MHz – 7.125 GHz) and FR2 (24.25 GHz – 52.6 GHz). It should be understood that although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “Sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR2, which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz – 300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band. [0048] The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified an operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz – 24.25 GHz). Frequency bands falling within FR3 may inherit FR1 characteristics and/or FR2 characteristics, and thus may effectively extend features of FR1 and/or FR2 into mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz – 71 GHz), FR4 (52.6 GHz – 114.25 GHz), and FR5 (114.25 GHz – 300 GHz). Each of these higher frequency bands falls within the EHF band. [0049] With the above aspects in mind, unless specifically stated otherwise, it should be understood that the term “sub-6 GHz” or the like if used herein may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Further, unless specifically stated otherwise, it should be understood that the term “millimeter wave” or the like if used herein may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and/or FR5, or may be within the EHF band. [0050] 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 (e.g., FR1) utilized by a UE 104/182 and the cell in which the UE 104/182 either performs the initial radio resource control (RRC) connection establishment procedure or initiates the RRC connection re-establishment procedure. The primary carrier carries all common and UE-specific control channels, and may be a carrier in a licensed frequency (however, this is not always the case). A secondary carrier is a carrier operating on a second frequency (e.g., FR2) that may be configured once the RRC connection is established between the UE 104 and the anchor carrier and that may be used to provide additional radio resources. In some cases, the secondary carrier may be a carrier in an unlicensed frequency. The secondary carrier may contain only necessary signaling information and signals, for example, those that are UE-specific may not be present in the secondary carrier, since both primary uplink and downlink carriers are typically UE-specific. This means that different UEs 104/182 in a cell may have different downlink primary carriers. The same is true for the uplink primary carriers. The network is able to change the primary carrier of any UE 104/182 at any time. This is done, for example, to balance the load on different carriers. Because a “serving cell” (whether a PCell or an SCell) corresponds to a carrier frequency / component carrier over which some base station is communicating, the term “cell,” “serving cell,” “component carrier,” “carrier frequency,” and the like can be used interchangeably. [0051] For example, still referring to FIG. 1, one of the frequencies utilized by the macro cell base stations 102 may be an anchor carrier (or “PCell”) and other frequencies utilized by the macro cell base stations 102 and/or the mmW base station 180 may be secondary carriers (“SCells”). The simultaneous transmission and/or reception of multiple carriers enables the UE 104/182 to significantly increase its data transmission and/or reception rates. For example, two 20 MHz aggregated carriers in a multi-carrier system would theoretically lead to a two-fold increase in data rate (i.e., 40 MHz), compared to that attained by a single 20 MHz carrier. [0052] The wireless communications system 100 may further include a UE 164 that may communicate with a macro cell base station 102 over a communication link 120 and/or the mmW base station 180 over a mmW communication link 184. For example, the macro cell base station 102 may support a PCell and one or more SCells for the UE 164 and the mmW base station 180 may support one or more SCells for the UE 164. [0053] In some cases, the UE 164 and the UE 182 may be capable of sidelink communication. Sidelink-capable UEs (SL-UEs) may communicate with base stations 102 over communication links 120 using the Uu interface (i.e., the air interface between a UE and a base station). SL-UEs (e.g., UE 164, UE 182) may also communicate directly with each other over a wireless sidelink 160 using the PC5 interface (i.e., the air interface between sidelink-capable UEs). A wireless sidelink (or just “sidelink”) is an adaptation of the core cellular (e.g., LTE, NR) standard that allows direct communication between two or more UEs without the communication needing to go through a base station. Sidelink communication may be unicast or multicast, and may be used for device-to-device (D2D) media-sharing, vehicle-to-vehicle (V2V) communication, vehicle-to-everything (V2X) communication (e.g., cellular V2X (cV2X) communication, enhanced V2X (eV2X) communication, etc.), emergency rescue applications, etc. One or more of a group of SL- UEs utilizing sidelink communications may be within the geographic coverage area 110 of a base station 102. Other SL-UEs in such a group may be outside the geographic coverage area 110 of a base station 102 or be otherwise unable to receive transmissions from a base station 102. In some cases, groups of SL-UEs communicating via sidelink communications may utilize a one-to-many (1:M) system in which each SL-UE transmits to every other SL-UE in the group. In some cases, a base station 102 facilitates the scheduling of resources for sidelink communications. In other cases, sidelink communications are carried out between SL-UEs without the involvement of a base station 102. [0054] In an aspect, the sidelink 160 may operate over a wireless communication medium of interest, which may be shared with other wireless communications between other vehicles and/or infrastructure access points, as well as other RATs. A “medium” may be composed of one or more time, frequency, and/or space communication resources (e.g., encompassing one or more channels across one or more carriers) associated with wireless communication between one or more transmitter / receiver pairs. In an aspect, the medium of interest may correspond to at least a portion of an unlicensed frequency band shared among various RATs. Although different licensed frequency bands have been reserved for certain communication systems (e.g., by a government entity such as the Federal Communications Commission (FCC) in the United States), these systems, in particular those employing small cell access points, have recently extended operation into unlicensed frequency bands such as the Unlicensed National Information Infrastructure (U-NII) band used by wireless local area network (WLAN) technologies, most notably IEEE 80211x WLAN technologies generally referred to as “Wi-Fi” Example systems of this type include different variants of CDMA systems, TDMA systems, FDMA systems, orthogonal FDMA (OFDMA) systems, single-carrier FDMA (SC-FDMA) systems, and so on. [0055] Note that although FIG. 1 only illustrates two of the UEs as SL-UEs (i.e., UEs 164 and 182), any of the illustrated UEs may be SL-UEs. Further, although only UE 182 was described as being capable of beamforming, any of the illustrated UEs, including UE 164, may be capable of beamforming. Where SL-UEs are capable of beamforming, they may beamform towards each other (i.e., towards other SL-UEs), towards other UEs (e.g., UEs 104), towards base stations (e.g., base stations 102, 180, small cell 102’, access point 150), etc. Thus, in some cases, UEs 164 and 182 may utilize beamforming over sidelink 160. [0056] In the example of FIG.1, any of the illustrated UEs (shown in FIG.1 as a single UE 104 for simplicity) may receive signals 124 from one or more Earth orbiting space vehicles (SVs) 112 (e.g., satellites). In an aspect, the SVs 112 may be part of a satellite positioning system that a UE 104 can use as an independent source of location information. A satellite positioning system typically includes a system of transmitters (e.g., SVs 112) positioned to enable receivers (e.g., UEs 104) to determine their location on or above the Earth based, at least in part, on positioning signals (e.g., signals 124) received from the transmitters. Such a transmitter typically transmits a signal marked with a repeating pseudo-random noise (PN) code of a set number of chips. While typically located in SVs 112, transmitters may sometimes be located on ground-based control stations, base stations 102, and/or other UEs 104. A UE 104 may include one or more dedicated receivers specifically designed to receive signals 124 for deriving geo location information from the SVs 112. [0057] In a satellite positioning system, the use of signals 124 can be augmented by various satellite-based augmentation systems (SBAS) that may be associated with or otherwise enabled for use with one or more global and/or regional navigation satellite systems. For example an SBAS may include an augmentation system(s) that provides integrity information, differential corrections, etc., such as the Wide Area Augmentation System (WAAS), the European Geostationary Navigation Overlay Service (EGNOS), the Multi- functional Satellite Augmentation System (MSAS), the Global Positioning System (GPS) Aided Geo Augmented Navigation or GPS and Geo Augmented Navigation system (GAGAN), and/or the like. Thus, as used herein, a satellite positioning system may include any combination of one or more global and/or regional navigation satellites associated with such one or more satellite positioning systems. [0058] In an aspect, SVs 112 may additionally or alternatively be part of one or more non- terrestrial networks (NTNs). In an NTN, an SV 112 is connected to an earth station (also referred to as a ground station, NTN gateway, or gateway), which in turn is connected to an element in a 5G network, such as a modified base station 102 (without a terrestrial antenna) or a network node in a 5GC. This element would in turn provide access to other elements in the 5G network and ultimately to entities external to the 5G network, such as Internet web servers and other user devices. In that way, a UE 104 may receive communication signals (e.g., signals 124) from an SV 112 instead of, or in addition to, communication signals from a terrestrial base station 102. [0059] The wireless communications system 100 may further include one or more UEs, such as UE 190, that connects indirectly to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links (referred to as “sidelinks”). In the example of FIG. 1, UE 190 has a D2D P2P link 192 with one of the UEs 104 connected to one of the base stations 102 (e.g., through which UE 190 may indirectly obtain cellular connectivity) and a D2D P2P link 194 with WLAN STA 152 connected to the WLAN AP 150 (through which UE 190 may indirectly obtain WLAN-based Internet connectivity). In an example, the D2D P2P links 192 and 194 may be supported with any well-known D2D RAT, such as LTE Direct (LTE-D), WiFi Direct (WiFi-D), Bluetooth®, and so on. [0060] FIG.2A illustrates an example wireless network structure 200. For example, a 5GC 210 (also referred to as a Next Generation Core (NGC)) can be viewed functionally as control plane (C-plane) functions 214 (e.g., UE registration, authentication, network access, gateway selection, etc.) and user plane (U-plane) functions 212, (e.g., UE gateway function, access to data networks, IP routing, etc.) which operate cooperatively to form the core network. User plane interface (NG-U) 213 and control plane interface (NG-C) 215 connect the gNB 222 to the 5GC 210 and specifically to the user plane functions 212 and control plane functions 214, respectively. In an additional configuration, an ng-eNB 224 may also be connected to the 5GC 210 via NG-C 215 to the control plane functions 214 and NG-U 213 to user plane functions 212. Further, ng-eNB 224 may directly communicate with gNB 222 via a backhaul connection 223. In some configurations, a Next Generation RAN (NG-RAN) 220 may have one or more gNBs 222 while other configurations include one or more of both ng-eNBs 224 and gNBs 222. Either (or both) gNB 222 or ng-eNB 224 may communicate with one or more UEs 204 (e.g., any of the UEs described herein). [0061] Another optional aspect may include a location server 230, which may be in communication with the 5GC 210 to provide location assistance for UE(s) 204. The location server 230 can 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, etc.), or alternately may each correspond to a single server. The location server 230 can be configured to support one or more location services for UEs 204 that can connect to the location server 230 via the core network, 5GC 210, and/or via the Internet (not illustrated). Further, the location server 230 may be integrated into a component of the core network, or alternatively may be external to the core network (e.g., a third party server, such as an original equipment manufacturer (OEM) server or service server). [0062] FIG.2B illustrates another example wireless network structure 240. A 5GC 260 (which may correspond to 5GC 210 in FIG. 2A) can be viewed functionally as control plane functions, provided by an access and mobility management function (AMF) 264, and user plane functions, provided by a user plane function (UPF) 262, which operate cooperatively to form the core network (i.e., 5GC 260). The functions of the AMF 264 include registration management, connection management, reachability management, mobility management, lawful interception, transport for session management (SM) messages between one or more UEs 204 (e.g., any of the UEs described herein) and a session management function (SMF) 266, transparent proxy services for routing SM messages, access authentication and access authorization, transport for short message service (SMS) messages between the UE 204 and the short message service function (SMSF) (not shown), and security anchor functionality (SEAF). The AMF 264 also interacts with an authentication server function (AUSF) (not shown) and the UE 204, and receives the intermediate key that was established as a result of the UE 204 authentication process. In the case of authentication based on a UMTS (universal mobile telecommunications system) subscriber identity module (USIM), the AMF 264 retrieves the security material from the AUSF. The functions of the AMF 264 also include security context management (SCM). The SCM receives a key from the SEAF that it uses to derive access-network specific keys The functionality of the AMF 264 also includes location services management for regulatory services, transport for location services messages between the UE 204 and a location management function (LMF) 270 (which acts as a location server 230), transport for location services messages between the NG-RAN 220 and the LMF 270, evolved packet system (EPS) bearer identifier allocation for interworking with the EPS, and UE 204 mobility event notification. In addition, the AMF 264 also supports functionalities for non-3GPP (Third Generation Partnership Project) access networks. [0063] 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 interconnect to a data network (not shown), providing packet routing and forwarding, packet inspection, user plane policy rule enforcement (e.g., gating, redirection, traffic steering), lawful interception (user plane collection), traffic usage reporting, quality of service (QoS) handling for the user plane (e.g., uplink/ downlink rate 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 of one or more “end markers” to the source RAN node. The UPF 262 may also support transfer of location services messages over a user plane between the UE 204 and a location server, such as an SLP 272. [0064] The functions of the SMF 266 include session management, UE Internet protocol (IP) address allocation and management, selection and control of user plane functions, configuration of traffic steering at the UPF 262 to route traffic to the proper destination, control of part of policy enforcement and QoS, and downlink data notification. The interface over which the SMF 266 communicates with the AMF 264 is referred to as the N11 interface. [0065] Another optional aspect may include an LMF 270, which may be in communication with the 5GC 260 to provide location assistance for UEs 204. The LMF 270 can 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, etc.), or alternately may each correspond to a single server. The LMF 270 can be configured to support one or more location services for UEs 204 that can connect to the LMF 270 via the core network, 5GC 260, and/or via the Internet (not illustrated) The SLP 272 may support similar functions to the LMF 270 but whereas the LMF 270 may communicate with the AMF 264, NG-RAN 220, and UEs 204 over a control plane (e.g., using interfaces and protocols intended to convey signaling messages and not voice or data), the SLP 272 may communicate with UEs 204 and external clients (e.g., third-party server 274) over a user plane (e.g., using protocols intended to carry voice and/or data like the transmission control protocol (TCP) and/or IP). [0066] Yet another optional aspect may include a third-party server 274, which may be in communication with the LMF 270, the SLP 272, the 5GC 260 (e.g., via the AMF 264 and/or the UPF 262), the NG-RAN 220, and/or the UE 204 to obtain location information (e.g., a location estimate) for the UE 204. As such, in some cases, the third-party server 274 may be referred to as a location services (LCS) client or an external client. The third- party server 274 can 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, etc.), or alternately may each correspond to a single server. [0067] User plane interface 263 and control plane interface 265 connect the 5GC 260, and specifically the UPF 262 and AMF 264, respectively, to one or more gNBs 222 and/or ng-eNBs 224 in the NG-RAN 220. The interface between gNB(s) 222 and/or ng-eNB(s) 224 and the AMF 264 is referred to as the “N2” interface, and the interface between gNB(s) 222 and/or ng-eNB(s) 224 and the UPF 262 is referred to as the “N3” interface. The gNB(s) 222 and/or ng-eNB(s) 224 of the NG-RAN 220 may communicate directly with each other via backhaul connections 223, referred to as the “Xn-C” interface. One or more of gNBs 222 and/or ng-eNBs 224 may communicate with one or more UEs 204 over a wireless interface, referred to as the “Uu” interface. [0068] The functionality of a gNB 222 may be divided between a gNB central unit (gNB-CU) 226, one or more gNB distributed units (gNB-DUs) 228, and one or more gNB radio units (gNB-RUs) 229. A gNB-CU 226 is a logical node that includes the base station functions of transferring user data, mobility control, radio access network sharing, positioning, session management, and the like, except for those functions allocated exclusively to the gNB-DU(s) 228. More specifically, the gNB-CU 226 generally host the radio resource control (RRC), service data adaptation protocol (SDAP), and packet data convergence protocol (PDCP) protocols of the gNB 222. A gNB-DU 228 is a logical node that generally hosts the radio link control (RLC) and medium access control (MAC) layer of the gNB 222 Its operation is controlled by the gNB-CU 226 One gNB-DU 228 can support one or more cells, and one cell is supported by only one gNB-DU 228. The interface 232 between the gNB-CU 226 and the one or more gNB-DUs 228 is referred to as the “F1” interface. The physical (PHY) layer functionality of a gNB 222 is generally hosted by one or more standalone gNB-RUs 229 that perform functions such as power amplification and signal transmission/reception. The interface between a gNB-DU 228 and a gNB-RU 229 is referred to as the “Fx” interface. Thus, a UE 204 communicates with the gNB-CU 226 via the RRC, SDAP, and PDCP layers, with a gNB-DU 228 via the RLC and MAC layers, and with a gNB-RU 229 via the PHY layer. [0069] FIG. 3A, FIG. 3B, and FIG. 3C illustrate several example components (represented by corresponding blocks) that may be incorporated into a UE 302 (which may correspond to any of the UEs described herein), a base station 304 (which may correspond to any of the base stations described herein), and a network entity 306 (which may correspond to or embody any of the network functions described herein, including the location server 230 and the LMF 270, or alternatively may be independent from the NG-RAN 220 and/or 5GC 210/260 infrastructure depicted in FIGS. 2A and 2B, such as a private network) to support the operations described herein. It will be appreciated that these components may be implemented in different types of apparatuses in different implementations (e.g., in an ASIC, in a system-on-chip (SoC), etc.). The illustrated components may also be incorporated into other apparatuses in a communication system. For example, other apparatuses in a system may include components similar to those described to provide similar functionality. Also, a given apparatus may contain one or more of the components. For example, an apparatus may include multiple transceiver components that enable the apparatus to operate on multiple carriers and/or communicate via different technologies. [0070] The UE 302 and the 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, etc.) via one or more wireless communication networks (not shown), such as an 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, for communicating with other network nodes, such as other UEs, access points, base stations (e.g., eNBs, gNBs), etc., via at least one designated RAT (e.g., NR, LTE, GSM, etc.) over a wireless communication medium of interest (eg some set of time/frequency resources in a particular frequency spectrum) The WWAN transceivers 310 and 350 may be variously configured for transmitting and encoding signals 318 and 358 (e.g., messages, indications, information, and so on), respectively, and conversely, for receiving and decoding signals 318 and 358 (e.g., messages, indications, information, pilots, and so on), respectively, in accordance with the designated RAT. Specifically, the 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. [0071] The UE 302 and the base station 304 each also include, at least in 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 refraining from transmitting, etc.) with other network nodes, such as other UEs, access points, base stations, etc., via at least one designated RAT (e.g., WiFi, LTE-D, Bluetooth®, Zigbee®, Z-Wave®, PC5, dedicated short-range communications (DSRC), wireless access for vehicular environments (WAVE), near-field communication (NFC), etc.) over a wireless communication medium of interest. The short-range wireless transceivers 320 and 360 may be variously configured for transmitting and encoding signals 328 and 368 (e.g., messages, indications, information, and so on), respectively, and conversely, for receiving and decoding signals 328 and 368 (e.g., messages, indications, information, pilots, and so on), respectively, in accordance with the 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. [0072] The UE 302 and the base station 304 also include, at least in some cases, satellite signal receivers 330 and 370. The satellite signal receivers 330 and 370 may be connected to one or more antennas 336 and 376, respectively, and may provide means for receiving and/or measuring satellite positioning/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), 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 (e.g., carrying control and/or user data) originating from a 5G network. The satellite signal receivers 330 and 370 may comprise any suitable hardware and/or software for receiving and processing satellite positioning/communication signals 338 and 378, respectively. The satellite signal receivers 330 and 370 may request information and operations as appropriate from the other systems, and, at least in some cases, perform calculations to determine locations of the UE 302 and the base station 304, respectively, using measurements obtained by any suitable satellite positioning system algorithm. [0073] 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, etc.) with other network entities (e.g., other base stations 304, other network entities 306). For example, the base station 304 may employ the 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 employ the one or more network transceivers 390 to communicate with one or more base station 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. [0074] A transceiver may be configured to communicate over a wired or wireless link. A transceiver (whether a wired transceiver or a wireless transceiver) includes transmitter circuitry (e.g., transmitters 314, 324, 354, 364) and receiver circuitry (e.g., receivers 312, 322, 352, 362). A transceiver may be an integrated device (e.g., embodying transmitter circuitry and receiver circuitry in a single device) in some implementations, may comprise separate transmitter circuitry and separate receiver circuitry in some implementations, or may be embodied in other ways in other implementations. The transmitter circuitry and receiver 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 Wireless transmitter 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, that permits the respective apparatus (e.g., UE 302, base station 304) to perform transmit “beamforming,” as described herein. Similarly, wireless receiver circuitry (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, that permits the respective apparatus (e.g., UE 302, base station 304) to perform receive beamforming, as described herein. In an aspect, the transmitter circuitry and receiver circuitry may share the same plurality of antennas (e.g., antennas 316, 326, 356, 366), such that the respective apparatus can only receive or transmit at a given time, not both at the same time. A wireless transceiver (e.g., WWAN transceivers 310 and 350, short-range wireless transceivers 320 and 360) may also include a network listen module (NLM) or the like for performing various measurements. [0075] As used herein, the various wireless transceivers (e.g., transceivers 310, 320, 350, and 360, and network transceivers 380 and 390 in some implementations) and wired transceivers (e.g., network transceivers 380 and 390 in some implementations) may generally be characterized as “a transceiver,” “at least one transceiver,” or “one or more transceivers.” As such, whether a particular transceiver is a wired or wireless transceiver may be inferred from the type of communication performed. For example, backhaul communication between network devices or servers will generally relate to signaling via a wired transceiver, whereas wireless communication between a UE (e.g., UE 302) and a base station (e.g., base station 304) will generally relate to signaling via a wireless transceiver. [0076] The UE 302, the base station 304, and the network entity 306 also include other components that may be used in conjunction with the operations as disclosed herein. The UE 302, the base station 304, and the network entity 306 include one or more processors 332, 384, and 394, respectively, for providing functionality relating to, for example, wireless communication, and for providing other processing functionality. The processors 332, 384, and 394 may therefore provide means for processing, such as means for determining, means for calculating, means for receiving, means for transmitting, means for indicating, etc. In an aspect, the 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 circuitry, or various combinations thereof. [0077] The UE 302, the base station 304, and the network entity 306 include memory circuitry implementing memories 340, 386, and 396 (e.g., each including a memory device), respectively, for maintaining information (e.g., information indicative of reserved resources, thresholds, parameters, and so on). The memories 340, 386, and 396 may therefore provide means for storing, means for retrieving, means for maintaining, etc. In some cases, the UE 302, the base station 304, and the network entity 306 may include positioning module 342, 388, and 398, respectively. The positioning module 342, 388, and 398 may be hardware circuits that are part of or coupled to the processors 332, 384, and 394, respectively, that, when executed, cause the UE 302, the base station 304, and the network entity 306 to perform the functionality described herein. In other aspects, the positioning module 342, 388, and 398 may be external to the processors 332, 384, and 394 (e.g., part of a modem processing system, integrated with another processing system, etc.). Alternatively, the positioning module 342, 388, and 398 may be memory modules stored in the memories 340, 386, and 396, respectively, that, when executed by the processors 332, 384, and 394 (or a modem processing system, another processing system, etc.), cause the UE 302, the base station 304, and the network entity 306 to perform the functionality described herein. FIG. 3A illustrates possible locations of the positioning module 342, which may be, for example, part of the one or more WWAN transceivers 310, the memory 340, the one or more processors 332, or any combination thereof, or may be a standalone component. FIG.3B illustrates possible locations of the positioning module 388, which may be, for example, part of the one or more WWAN transceivers 350, the memory 386, the one or more processors 384, or any combination thereof, or may be a standalone component. FIG.3C illustrates possible locations of the positioning module 398, which may be, for example, part of the one or more network transceivers 390, the memory 396, the one or more processors 394, or any combination thereof, or may be a standalone component. [0078] The UE 302 may include one or more sensors 344 coupled to the one or more processors 332 to provide means for sensing or detecting movement and/or orientation information that is independent of motion data derived from signals received by the one or more WWAN transceivers 310, the one or more short-range wireless transceivers 320, and/or the satellite signal receiver 330 By way of example the sensor(s) 344 may include an accelerometer (e.g., a micro-electrical mechanical systems (MEMS) device), a gyroscope, a geomagnetic sensor (e.g., a compass), an altimeter (e.g., a barometric pressure altimeter), and/or any other type of movement detection sensor. Moreover, the sensor(s) 344 may include a plurality of different types of devices and combine their outputs in order to provide motion information. For example, the sensor(s) 344 may use a combination of a multi-axis accelerometer and orientation sensors to provide the ability to compute positions in two-dimensional (2D) and/or three-dimensional (3D) coordinate systems. [0079] In addition, the UE 302 includes a user interface 346 providing means for providing indications (e.g., audible and/or visual indications) to a user and/or for receiving user input (e.g., upon user actuation of a sensing device such a keypad, a touch screen, a microphone, and so on). Although not shown, the base station 304 and the network entity 306 may also include user interfaces. [0080] Referring to the one or more processors 384 in more detail, in the downlink, IP packets from the network entity 306 may be provided to the processor 384. The one or more processors 384 may implement functionality for an RRC layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The one or more processors 384 may provide RRC layer functionality associated with broadcasting of system information (e.g., master information block (MIB), system information blocks (SIBs)), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-RAT mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression/decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the transfer of upper layer PDUs, error correction through automatic repeat request (ARQ), concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, scheduling information reporting, error correction, priority handling, and logical channel prioritization. [0081] The transmitter 354 and the receiver 352 may implement Layer-1 (L1) functionality associated with various signal processing functions Layer-1 which includes a physical (PHY) layer, may include error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, interleaving, rate matching, mapping onto physical channels, modulation/demodulation of physical channels, and MIMO antenna processing. The transmitter 354 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an orthogonal frequency division multiplexing (OFDM) subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and/or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM symbol stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator may be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate may be derived from a reference signal and/or channel condition feedback transmitted by the UE 302. Each spatial stream may then be provided to one or more different antennas 356. The transmitter 354 may modulate an RF carrier with a respective spatial stream for transmission. [0082] At the UE 302, the receiver 312 receives a signal through its respective antenna(s) 316. The receiver 312 recovers information modulated onto an RF carrier and provides the information to the one or more processors 332. The transmitter 314 and the receiver 312 implement Layer-1 functionality associated with various signal processing functions. The receiver 312 may perform spatial processing on the information to recover any spatial streams destined for the UE 302. If multiple spatial streams are destined for the UE 302, they may be combined by the receiver 312 into a single OFDM symbol stream. The receiver 312 then converts 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 points transmitted by the base station 304. These soft decisions may be based on channel estimates computed by a channel estimator. The soft decisions are then decoded and de-interleaved to recover the data and control signals that were originally transmitted by the base station 304 on the physical channel The data and control signals are then provided to the one or more processors 332, which implements Layer-3 (L3) and Layer-2 (L2) functionality. [0083] In the uplink, the one or more processors 332 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets from the core network. The one or more processors 332 are also responsible for error detection. [0084] Similar to the functionality described in connection with the downlink transmission by the base station 304, the one or more processors 332 provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression/decompression, and security (ciphering, deciphering, integrity protection, integrity verification); RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through hybrid automatic repeat request (HARQ), priority handling, and logical channel prioritization. [0085] Channel estimates derived by the channel estimator from a reference signal or feedback transmitted by the base station 304 may be used by the transmitter 314 to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the transmitter 314 may be provided to different antenna(s) 316. The transmitter 314 may modulate an RF carrier with a respective spatial stream for transmission. [0086] 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 a signal through its respective antenna(s) 356. The receiver 352 recovers information modulated onto an RF carrier and provides the information to the one or more processors 384. [0087] In the uplink, the one or more processors 384 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets from the UE 302. IP packets from the one or more processors 384 may be provided to the core network. The one or more processors 384 are also responsible for error detection. [0088] For convenience, the UE 302, the base station 304, and/or the network entity 306 are shown in FIGS.3A, 3B, and 3C as including various components that may be configured according to the various examples described herein. It will be appreciated, however, that the illustrated components may have different functionality in different designs. In particular, various components in FIGS. 3A to 3C are optional in alternative configurations and the various aspects include configurations that may vary due to design choice, costs, use of the device, or other considerations. For example, in case of FIG.3A, a particular implementation of UE 302 may omit the WWAN transceiver(s) 310 (e.g., a wearable device or tablet computer or PC or laptop may have Wi-Fi and/or Bluetooth capability without cellular capability), or may omit the short-range wireless transceiver(s) 320 (e.g., cellular-only, etc.), or may omit the satellite signal receiver 330, or may omit the sensor(s) 344, and so on. In another example, in case of FIG. 3B, a particular implementation of the base station 304 may omit the WWAN transceiver(s) 350 (e.g., a Wi-Fi “hotspot” access point without cellular capability), or may omit the short-range wireless transceiver(s) 360 (e.g., cellular-only, etc.), or may omit the satellite receiver 370, and so on. For brevity, illustration of the various alternative configurations is not provided herein, but would be readily understandable to one skilled in the art. [0089] The various components of the UE 302, the base station 304, and the network entity 306 may be communicatively coupled to each other over data buses 334, 382, and 392, respectively. In an aspect, the data buses 334, 382, and 392 may form, or be part of, a communication interface of the UE 302, the base station 304, and the network entity 306, respectively. For example, where different logical entities are embodied in the same device (e.g., gNB and location server functionality incorporated into the same base station 304), the data buses 334, 382, and 392 may provide communication between them. [0090] The components of FIGS.3A, 3B, and 3C may be implemented in various ways. In some implementations, the components of FIGS. 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 use and/or incorporate at least one memory component for storing 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 processor and memory component(s) of the UE 302 (e.g., by execution of appropriate code and/or by appropriate configuration of processor components). Similarly, some or all of the functionality represented by blocks 350 to 388 may be implemented by processor and memory component(s) of the base station 304 (e.g., by execution of appropriate code and/or by appropriate configuration of processor components). Also, some or all of the functionality represented by blocks 390 to 398 may be implemented by processor and memory component(s) of the network entity 306 (e.g., by execution of appropriate code and/or by appropriate configuration of processor components). For simplicity, various operations, acts, and/or functions are described herein as being performed “by a UE,” “by a base station,” “by a network entity,” etc. However, as will be appreciated, such operations, acts, and/or functions may actually be performed by specific components or combinations of components of the UE 302, base station 304, network entity 306, etc., such as the processors 332, 384, 394, the transceivers 310, 320, 350, and 360, the memories 340, 386, and 396, the positioning module 342, 388, and 398, etc. [0091] 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 a network operator or operation of the cellular network infrastructure (e.g., NG RAN 220 and/or 5GC 210/260). For example, the network entity 306 may be a component of a private network that may be configured to communicate with the UE 302 via the base station 304 or independently from the base station 304 (e.g., over a non-cellular communication link, such as WiFi). [0092] FIG. 4 is a diagram illustrating an example frame structure, according to aspects of the disclosure. Various frame structures may be used to support downlink and uplink transmissions between network nodes (e.g., base stations and UEs). FIG.4 is a diagram 400 illustrating an example frame structure, according to aspects of the disclosure. The frame structure may be a downlink or uplink frame structure. Other wireless communications technologies may have different frame structures and/or different channels. [0093] LTE, and in some cases NR, utilizes orthogonal frequency-division multiplexing (OFDM) on the downlink and single-carrier frequency division multiplexing (SC-FDM) on the uplink. Unlike LTE, however, NR has an option to use OFDM on the uplink as well. OFDM and SC-FDM partition the system bandwidth into multiple (K) orthogonal subcarriers which are also commonly referred to as tones bins etc Each subcarrier may be modulated with data. In general, modulation symbols are sent in the frequency domain with OFDM and in the time domain with SC-FDM. The spacing between adjacent subcarriers may be fixed, and the total number of subcarriers (K) may be dependent on the system bandwidth. For example, the spacing of the subcarriers may be 15 kilohertz (kHz) and the minimum resource allocation (resource block) may be 12 subcarriers (or 180 kHz). Consequently, the nominal fast Fourier transform (FFT) size may be equal to 128, 256, 512, 1024, or 2048 for system bandwidth of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), respectively. The system bandwidth may also be partitioned into subbands. For example, a subband may cover 1.08 MHz (i.e., 6 resource blocks), and there may be 1, 2, 4, 8, or 16 subbands for system bandwidth of 1.25, 2.5, 5, 10, or 20 MHz, respectively. [0094] LTE supports a single numerology (subcarrier spacing (SCS), symbol length, etc.). In contrast, NR may support multiple numerologies (µ), for example, subcarrier spacings of 15 kHz (µ=0), 30 kHz (µ=1), 60 kHz (µ=2), 120 kHz (µ=3), and 240 kHz (µ=4) or greater may be available. In each subcarrier spacing, there are 14 symbols per slot. For 15 kHz SCS (µ=0), there is one slot per subframe, 10 slots per frame, the slot duration is 1 millisecond (ms), the symbol duration is 66.7 microseconds (µs), and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 50. For 30 kHz SCS (µ=1), there are two slots per subframe, 20 slots per frame, the slot duration is 0.5 ms, the symbol duration is 33.3 µs, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 100. For 60 kHz SCS (µ=2), there are four slots per subframe, 40 slots per frame, the slot duration is 0.25 ms, the symbol duration is 16.7 µs, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 200. For 120 kHz SCS (µ=3), there are eight slots per subframe, 80 slots per frame, the slot duration is 0.125 ms, the symbol duration is 8.33 µs, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 400. For 240 kHz SCS (µ=4), there are 16 slots per subframe, 160 slots per frame, the slot duration is 0.0625 ms, the symbol duration is 4.17 µs, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 800. [0095] In the example of FIG. 4, a numerology of 15 kHz is used. Thus, in the time domain, a 10 ms frame is divided into 10 equally sized subframes of 1 ms each, and each subframe includes one time slot. In FIG. 4, time is represented horizontally (on the X axis) with time increasing from left to right, while frequency is represented vertically (on the Y axis) with frequency increasing (or decreasing) from bottom to top. [0096] A resource grid may be used to represent time slots, each time slot including one or more time-concurrent resource blocks (RBs) (also referred to as physical RBs (PRBs)) in the frequency domain. The resource grid is further divided into multiple resource elements (REs). An RE may correspond to one symbol length in the time domain and one subcarrier in the frequency domain. In the numerology of FIG. 4, for a normal cyclic prefix, an RB may contain 12 consecutive subcarriers in the frequency domain and seven consecutive symbols in the time domain, for a total of 84 REs. For an extended cyclic prefix, an RB may contain 12 consecutive subcarriers in the frequency domain and six consecutive symbols in the time domain, for a total of 72 REs. The number of bits carried by each RE depends on the modulation scheme. [0097] Some of the REs may carry reference (pilot) signals (RS). The reference signals may include positioning reference signals (PRS), tracking reference signals (TRS), phase tracking reference signals (PTRS), cell-specific reference signals (CRS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), primary synchronization signals (PSS), secondary synchronization signals (SSS), synchronization signal blocks (SSBs), sounding reference signals (SRS), etc., depending on whether the illustrated frame structure is used for uplink or downlink communication. FIG.4 illustrates example locations of REs carrying a reference signal (labeled “R”). [0098] [0099] FIG. 5 is a diagram 500 illustrating various downlink channels within an example downlink slot. In FIG. 5, time is represented horizontally (on the X axis) with time increasing from left to right, while frequency is represented vertically (on the Y axis) with frequency increasing (or decreasing) from bottom to top. In the example of FIG. 5, a numerology of 15 kHz is used. Thus, in the time domain, the illustrated slot is one millisecond (ms) in length, divided into 14 symbols. [0100] In NR, the channel bandwidth, or system bandwidth, is divided into multiple bandwidth parts (BWPs). A BWP is a contiguous set of RBs selected from a contiguous subset of the common RBs for a given numerology on a given carrier. Generally, a maximum of four BWPs can be specified in the downlink and uplink. That is, 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) may be active at a given time, meaning the UE may only receive or transmit over one BWP at a time. On the downlink, the bandwidth of each BWP should be equal to or greater than the bandwidth of the SSB, but it may or may not contain the SSB. [0101] Referring to FIG.5, a primary synchronization signal (PSS) is used by a UE to determine subframe/symbol timing and a physical layer identity. A secondary synchronization signal (SSS) is used by a UE to determine a physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine a PCI. Based on the PCI, the UE can determine the locations of the aforementioned DL-RS. The physical broadcast channel (PBCH), which carries a master information block (MIB), may be logically grouped with the PSS and SSS to form an SSB (also referred to as an 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 through the PBCH, such as system information blocks (SIBs), and paging messages. [0102] The physical downlink control channel (PDCCH) carries downlink control information (DCI) within one or more control channel elements (CCEs), each CCE including one or more RE group (REG) bundles (which may span multiple symbols in the time domain), each REG bundle including one or more REGs, each REG corresponding to 12 resource elements (one resource block) in the frequency domain and one OFDM symbol in the time domain. The set of physical resources used to carry the PDCCH/DCI is referred to in NR as the control resource set (CORESET). In NR, a PDCCH is confined to a single CORESET and is transmitted with its own DMRS. This enables UE-specific beamforming for the PDCCH. [0103] In the example of FIG. 5, there is one CORESET per BWP, and the CORESET spans three symbols (although it may be only one or two symbols) in the time domain. Unlike LTE control channels, which occupy the entire system bandwidth, in NR, PDCCH channels are localized to a specific region in the frequency domain (i.e., a CORESET). Thus, the frequency component of the PDCCH shown in FIG.5 is illustrated as less than a single BWP in the frequency domain. Note that although the illustrated CORESET is contiguous in the frequency domain, it need not be. In addition, the CORESET may span less than three symbols in the time domain. [0104] The DCI within the PDCCH carries information about uplink resource allocation (persistent and non-persistent) and descriptions about downlink data transmitted to the UE, referred to as uplink and downlink grants, respectively. More specifically, the DCI indicates the resources scheduled for the downlink data channel (e.g., PDSCH) and the uplink data channel (e.g., physical uplink shared channel (PUSCH)). Multiple (e.g., up to eight) DCIs can be configured in the PDCCH, and these DCIs can have one of multiple formats. For example, there are different DCI formats for uplink scheduling, for downlink scheduling, for uplink transmit power control (TPC), etc. A PDCCH may be transported by 1, 2, 4, 8, or 16 CCEs in order to accommodate different DCI payload sizes or coding rates. [0105] FIG.6 is a diagram of an example PRS configuration 600 for the PRS transmissions of a given base station, according to aspects of the disclosure. In FIG. 6, time is represented horizontally, increasing from left to right. Each long rectangle represents a slot and each short (shaded) rectangle represents an OFDM symbol. In the example of FIG. 6, a PRS resource set 610 (labeled “PRS resource set 1”) includes two PRS resources, a first PRS resource 612 (labeled “PRS resource 1”) and a second PRS resource 614 (labeled “PRS resource 2”). The base station transmits PRS on the PRS resources 612 and 614 of the PRS resource set 610. [0106] The PRS resource set 610 has an occasion length (N_PRS) of two slots and a periodicity (T_PRS) of, for example, 160 slots or 160 milliseconds (ms) (for 15 kHz subcarrier spacing). As such, both the PRS resources 612 and 614 are two consecutive slots in length and repeat every T_PRS slots, starting from the slot in which the first symbol of the respective PRS resource occurs. In the example of FIG. 6, the PRS resource 612 has a symbol length (N_symb) of two symbols, and the PRS resource 614 has a symbol length (N_symb) of four symbols. The PRS resource 612 and the PRS resource 614 may be transmitted on separate beams of the same base station. [0107] Each instance of the PRS resource set 610, illustrated as instances 620a, 620b, and 620c, includes an occasion of length ‘2’ (i.e., N_PRS=2) for each PRS resource 612, 614 of the PRS resource set. The PRS resources 612 and 614 are repeated every T_PRS slots up to the muting sequence periodicity T_REP. As such, a bitmap of length T_REP would be needed to indicate which occasions of instances 620a, 620b, and 620c of PRS resource set 610 are muted (i.e., not transmitted). [0108] In an aspect, there may be additional constraints on the PRS configuration 600. For example, for all PRS resources (e.g., PRS resources 612, 614) of a PRS resource set (e.g., PRS resource set 610) the base station can configure the following parameters to be the same: (a) the occasion length (N_PRS), (b) the number of symbols (N_symb), (c) the comb type, and/or (d) the bandwidth. In addition, for all PRS resources of all PRS resource sets, the subcarrier spacing and the cyclic prefix can be configured to be the same for one base station or for all base stations. Whether it is for one base station or all base stations may depend on the UE’s capability to support the first and/or second option. [0109] FIG.7 illustrates a time difference of arrival (TDOA)-based positioning procedure in an example wireless communications system 700, according to aspects of the disclosure. TDOA is also referred to as reference signal time difference (RSTD). The TDOA-based positioning procedure may be an observed time difference of arrival (OTDOA) positioning procedure, as in LTE, or a downlink time difference of arrival (DL-TDOA) positioning procedure, as in 5G NR. Other positioning methods include DL-AoD and multi-RTT positioning. In the example of FIG.7, a UE 704 (e.g., any of the UEs described herein) is attempting to calculate an estimate of its location (referred to as “UE-based” positioning), or assist another entity (e.g., a base station or core network component, another UE, a location server, a third party application, etc.) to calculate an estimate of its location (referred to as “UE-assisted” positioning). The UE 704 may communicate with (e.g., send information to and receive information from) one or more of a plurality of base stations 702 (e.g., any combination of base stations described herein), labeled “BS1” 702-1, “BS2” 702-2, and “BS3” 702-3. [0110] To support location estimates, the base stations 702 may be configured to broadcast positioning reference signals (e.g., positioning reference signals (PRS), tracking reference signals (TRS), cell-specific reference signals (CRS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), etc.) to a UE 704 in their coverage areas to enable the UE 704 to measure characteristics of such reference signals. In a TDOA-based positioning procedure, the UE 704 measures the time difference, known as the reference signal time difference (RSTD) or TDOA, between specific downlink reference signals (e.g., PRS, TRS, CRS, CSI-RS, etc.) transmitted by different pairs of base stations 702, and either reports these RSTD measurements to a location server (e.g., location server 230, LMF 270, SLP 272) or computes a location estimate itself from the RSTD measurements. [0111] Generally, RSTDs are measured between a reference cell (e.g., a cell supported by base station 702-1 in the example of FIG. 7) and one or more neighbor cells (e.g., cells supported by base stations 702-2 and 702-3 in the example of FIG 7) The reference cell remains the same for all RSTDs measured by the UE 704 for any single positioning use of TDOA and would typically correspond to the serving cell for the UE 704 or another nearby cell with good signal strength at the UE 704. In an aspect, the neighbor cells would normally be cells supported by base stations different from the base station for the reference cell, and may have good or poor signal strength at the UE 704. The location computation can be based on the measured RSTDs and knowledge of the involved base stations’ 702 locations and relative transmission timing (e.g., regarding whether base stations 702 are accurately synchronized or whether each base station 702 transmits with some known time offset relative to other base stations 702). [0112] To assist TDOA-based positioning operations, the location server (e.g., location server 230, LMF 270, SLP 272) may provide assistance data to the UE 704 for the reference cell and the neighbor cells relative to the reference cell. For example, the assistance data may include identifiers (e.g., PCI, VCI, CGI, etc.) for each cell of a set of cells that the UE 704 is expected to measure (here, cells supported by the base stations 702). The assistance data may also provide the center channel frequency of each cell, various reference signal configuration parameters (e.g., the number of consecutive positioning slots, periodicity of positioning slots, muting sequence, frequency hopping sequence, reference signal identifier, reference signal bandwidth), and/or other cell related parameters applicable to TDOA-based positioning procedures. The assistance data may also indicate the serving cell for the UE 704 as the reference cell. [0113] In some cases, the assistance data may also include “expected RSTD” parameters, which provide the UE 704 with information about the RSTD values the UE 704 is expected to measure between the reference cell and each neighbor cell at its current location, together with an uncertainty of the expected RSTD parameter. The expected RSTD, together with the associated uncertainty, may define a search window for the UE 704 within which the UE 704 is expected to measure the RSTD value. In some cases, the value range of the expected RSTD may be +/- 500 microseconds (µs). In some cases, when any of the resources used for the positioning measurement are in FR1, the value range for the uncertainty of the expected RSTD may be +/- 32 µs. In other cases, when all of the resources used for the positioning measurement(s) are in FR2, the value range for the uncertainty of the expected RSTD may be +/- 8 µs. [0114] TDOA assistance information may also include positioning reference signal configuration information parameters which allow the UE 704 to determine when a positioning reference signal occasion will occur on signals received from various neighbor cells relative to positioning reference signal occasions for the reference cell, and to determine the reference signal sequence transmitted from the various cells in order to measure a reference signal time of arrival (ToA) or RSTD. [0115] In an aspect, while the location server (e.g., location server 230, LMF 270, SLP 272) may send the assistance data to the UE 704, alternatively, the assistance data can originate directly from the base stations 702 themselves (e.g., in periodically broadcasted overhead messages, etc.). Alternatively, the UE 704 can detect neighbor base stations itself without the use of assistance data. [0116] The UE 704 (e.g., based in part on the assistance data, if provided) can measure and (optionally) report the RSTDs between reference signals received from pairs of base stations 702. Using the RSTD measurements, the known absolute or relative transmission timing of each base station 702, and the known location(s) of the reference and neighbor base stations 702, the network (e.g., location server 230/LMF 270/SLP 272, a base station 702) or the UE 704 can estimate the location of the UE 704. More particularly, the RSTD for a neighbor cell “k” relative to a reference cell “Ref” may be given as (ToA_k – ToA_Ref). In the example of FIG.7, the measured RSTDs between the reference cell of base station 702-1 and the cells of neighbor base stations 702-2 and 702-3 may be represented as T2 – T1 and T3 – T1, where T1, T2, and T3 represent the ToA of a reference signal from the base station 702-1, 702-2, and 702-3, respectively. The UE 704 (if it is not the positioning entity) may then send the RSTD measurements to the location server or other positioning entity. Using (i) the RSTD measurements, (ii) the known absolute or relative transmission timing of each base station 702, (iii) the known location(s) of the base stations 702, and/or (iv) directional reference signal characteristics, such as the direction of transmission, the UE’s 704 location may be determined (either by the UE 704 or the location server). [0117] In an aspect, the location estimate may specify the location of the UE 704 in a two- dimensional (2D) coordinate system; however, the aspects disclosed herein are not so limited, and may also be applicable to determining location estimates using a three- dimensional (3D) coordinate system, if the extra dimension is desired. Additionally, while FIG. 7 illustrates one UE 704 and three base stations 702, as will be appreciated, there may be more UEs 704 and more base stations 702. [0118] Still referring to FIG.7, when the UE 704 obtains a location estimate using RSTDs, the necessary additional data (e.g., the base stations’ 702 locations and relative transmission timing) may be provided to the UE 704 by the location server. In some implementations, a location estimate for the UE 704 may be obtained (e.g., by the UE 704 itself or by the location server) from RSTDs and from other measurements made by the UE 704 (e.g., measurements of signal timing from global positioning system (GPS) or other global navigation satellite system (GNSS) satellites). In these implementations, known as hybrid positioning, the RSTD measurements may contribute towards obtaining the UE’s 704 location estimate but may not wholly determine the location estimate. [0119] FIG. 8 illustrates an example Long-Term Evolution (LTE) positioning protocol (LPP) procedure 800 between a UE 802 and a location server (illustrated as a location management function (LMF) 804) for performing positioning operations. As illustrated in FIG. 8, positioning of the UE 802 is supported via an exchange of LPP messages between the UE 802 and the LMF 804. The LPP messages may be exchanged between UE 802 and the LMF 804 via the UE’s 802 serving base station (illustrated as a serving gNB 806) and a core network (not shown). The LPP procedure 800 may be used to position the UE 802 in order to support various location-related services, such as navigation for UE 802 (or for the user of UE 802), or for routing, or for provision of an accurate location to a public safety answering point (PSAP) in association with an emergency call from UE 802 to a PSAP, or for some other reason. The LPP procedure 800 may also be referred to as a positioning session, and there may be multiple positioning sessions for different types of positioning methods (e.g., downlink time difference of arrival (DL-TDOA), round-trip-time (RTT), enhanced cell identity (E-CID), etc.). [0120] In some aspects, the UE 802 may receive a request for its positioning capabilities from the LMF 804 at stage 810 (e.g., an LPP Request Capabilities message). At stage 820, the UE 802 provides its positioning capabilities to the LMF 804 relative to the LPP protocol by sending an LPP Provide Capabilities message to LMF 804 indicating the position methods and features of these position methods that are supported by the UE 802 using LPP. The capabilities indicated in the LPP Provide Capabilities message may, in some aspects, indicate the type of positioning the UE 802 supports (e.g., DL-TDOA, RTT, E- CID, etc.) and may indicate the capabilities of the UE 802 to support those types of positioning. In other aspects, the UE 802 may unilaterally indicate its capabilities to the LMF 804, e.g., the UE 802 may send the LPP Provide Capabilities message to the LMF 804 without first receiving the LPP Request Capabilities message. [0121] In some aspects, the capabilities that the UE 802 indicates to the LMF 804 are expressed as parameters, which may be in the form of information elements (IEs). In some aspects, the capabilities that the UE 802 indicates to the LMF 804 includes the parameter NR-DL- PRS-ProcessingCapability, which indicates common DL-PRS processing capabilities applicable across all NR positioning methods supported by the UE. It includes the maximum number of positioning frequency layers supported. For each supported frequency band, the UE may indicate one or more of the following: • dl-PRS-BufferType, which indicates the PRS buffering capability as either type1 (symbol-level buffering) or type2 (slot-level buffering); • durationOfPRS-Processing, which indicates the duration N (ms) of PRS that the UE can process every T (ms) assuming the maximum PRS BW indicated in supportedBandwidthPRS. Possible values of N include {0.125, 0.25, 0.5, 1, 2, 4, 6, 8, 12, 16, 20, 25, 30, 32, 35, 40, 45, 50}. Possible values of T include {8, 16, 20, 30, 40, 80, 160, 320, 640, 1280}; and • maxNumOfDL-PRS-ResProcessedPerSlot, which indicates the maximum number N' of PRS resources that the UE can process per slot for each SCS (SCS15, SCS30, SCS60 and SCS120). Possible values of N' include {1, 2, 4, 8, 16, 24, 32, 48, 64}. [0122] In some aspects, upon reception of the LPP Provide Capabilities message, at stage 820, the LMF 804 determines to use a particular type of positioning method (e.g., DL-TDOA, RTT, E-CID, etc.) based on the indicated type(s) of positioning the UE 802 supports and determines a set of one or more transmission-reception points (TRPs) from which the UE 802 is to measure downlink positioning reference signals or towards which the UE 802 is to transmit uplink positioning reference signals. At stage 830, the LMF 804 sends an LPP Provide Assistance Data message to the UE 802 identifying the set of TRPs. In other aspects, the LPP Provide Assistance Data message at stage 830 may be sent by the LMF 804 to the UE 802 in response to an LPP Request Assistance Data message sent by the UE 802 to the LMF 804 (not shown in FIG.8). An LPP Request Assistance Data message may include an identifier of the UE’s 802 serving TRP and a request for the positioning reference signal (PRS) configuration of neighboring TRPs. In some aspects, the LMF 804 may send additional assistance data messages to the UE 802 (not shown in FIG.8). [0123] In some aspects, the assistance data includes the IE NR-DL-PRS-AssistanceData, which is used by the location server to provide DL-PRS assistance data. NR-DL-PRS- AssistanceData indicates to the UE 802 the set of PRS resources that the UE 802 is requested to measure. The assistance data may include a reference TRP that is used as the timing reference to define the search windows for all PRS resources. For example, the parameter nr-DL-PRS-ReferenceInfo defines the assistance data reference TRP whose DL-PRS configuration is included in nr-DL-PRS-AssistanceDataList. One or more nr- DL-PRS-SFN0-Offset parameters and one or more nr-DL-PRS-expectedRSTD parameters in the nr-DL-PRS-AssistanceDataList are provided relative to the assistance data reference TRP. [0124] In some aspects, the assistance data is organized in Positioning Frequency Layers (PFLs) and PRS Resource Sets. A PRS resource set is a collection of PRS resources on a single TRP that have the same periodicity and slot offset. Example periods include {4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 160, 320, 640, 1280, 2560, 5120, and 10240} ms. The slot offset step size is one slot. The PRS resources may have a repetition pattern, defined as a number of repetitions, e.g., {1, 2, 4, 6, 8, 16, or 32} slots and a step size, e.g., {1, 2, 4, 6, 8, 16, or 32} slots. For a PRS resource set, the assistance data may specify a number of symbols per slot, a muting pattern configuration, a power level, or some combination thereof. A PFL is a collection of PRS resource sets on one or more TRPs that have the same subcarrier spacing (SCS), cyclic prefix (CP) type, comb size, PRS bandwidth (e.g., {24, 28, 32, 36, … , 268, 272} physical resource blocks (PRBs)), point A, and starting PRB. [0125] At stage 840, the LMF 804 sends a request for location information to the UE 802. The request may be an LPP Request Location Information message. This message usually includes information elements defining the location information type, desired accuracy of the location estimate, and response time (i.e., desired latency). Note that a high latency requirement allows for a longer response time while a low latency requirement requires a shorter response time. Thus, a long response time is referred to as high latency and a short response time is referred to as low latency. A low-latency location request may ask the UE to process a smaller number of PRS resource samples to expedite the results. [0126] Note that in some implementations, the LPP Provide Assistance Data message sent at stage 830 may be sent after the LPP Request Location Information message at 840 if, for example the UE 802 sends a request for assistance data to LMF 804 (eg in an LPP Request Assistance Data message, not shown in FIG. 8) after receiving the request for location information at stage 840.

[0127] At stage 850, the UE 802 utilizes the assistance information received at stage 830 and any additional data (e.g., a desired location accuracy or a maximum response time) received at stage 840 to perform positioning operations (e.g., measurements of DL-PRS, transmission of UL-PRS, etc.) for the selected positioning method.

[0128] At stage 860, the UE 802 may send an LPP Provide Location Information message to the LMF 804 conveying the results of any measurements that were obtained at stage 850 (e.g., time of arrival (ToA), reference signal time difference (RSTD), reception-to-transmission (Rx-Tx) time difference, etc.) and before or when any maximum response time has expired (e.g., a maximum response time provided by the LMF 804 at stage 840). The LPP Provide Location Information message at stage 860 may also include the time (or times) at which the positioning measurements were obtained and the identity of the TRP(s) from which the positioning measurements were obtained. Note that the time between the request for location information at 840 and the response at 860 is the “response time” and indicates the latency of the positioning session.

[0129] The LMF 804 computes an estimated location of the UE 802 using the appropriate positioning techniques (e.g., DL-TDOA, RTT, E-CID, etc.) based, at least in part, on measurements received in the LPP Provide Location Information message at stage 860.

[0130] FIG. 9 illustrates an example 900 of measuring and processing PRS data during an active mode, which may also be referred to herein as a connected mode or connected state. In FIG. 9, each of the PRS occurrences, labeled PRS1, PRS2, and PRS3, is processed almost immediately by the UE, and the results are reported by the UE after the conclusion of the measurement period / response time. In a connected mode, PRS processing may extend beyond the measurement gap. The length of the measurement period 902 depends on a number of factors, among them the number of PRS samples to be taken. For example, T _RS TD,i is the measurement period for PRS RSTD measurement in positioning frequency layer i, and is calculated as specified below: where: * CSSF _PRS , _i is the carrier-specific scaling factor for PRS-based measurements, for the positioning frequency layer i. This factor accounts for sharing of measurement gaps between positioning measurements and mobility measurements (intra-frequency, inter-frequency and inter-RAT). CSSF > 1 when the measurement gaps are shared between multiple measurements, resulting in longer measurement delay.

* N _RxBeam,i is the UE Rx beam sweeping factor. This is the number of RX beams that the UE uses (sequentially) to measure a given PRS resource. In FR1, N _RxBeam,i ⁼ 1, and in FR2, N _RxBeam,i = 8. Where a UE indicates support for a reduced Rx beam sweeping factor, a location server may request a reduced Rx beam sweeping factor for low-latency measurements.

* is the maximum number of DL PRS resources per slot in positioning frequency layer i.

* {N _b T _i } is a UE capability combination per band where N _i is a duration of DL PRS symbols in ms processed every T _i ms for a given maximum bandwidth supported by UE, corresponding to durationOfPRS-Processing, which is reported by the UE.

* is a UE capability for number of DL PRS resources that it can process in a slot, corresponding to maxNumOfDL-PRS-ResProcessedPerSlot, which is reported by the UE.

* T _{available_PRS,i} = LCM(T _PRS,i , MGRP _i ), the least common multiple between TPRS I and MGRPp This parameter indicates the periodicity of PRS resources available within the measurement gap for each PFL.

* L _{available_PRS,i} is the time duration of available PRS in the positioning frequency layer i to be measured during T _{available_PRS,i} .

* Ns _ample is the number of samples processed for each PRS resource; N _sample = 4. For low-latency measurements, N _sample may be set to a number less than 4, e.g., 1 or 2.

* T _Iast is the measurement duration for the last PRS RSTD sample, including the sampling time and processing time; T _Iast = T _t + T _{available PRS,i} . * MGRP _i is the measurement gap periodicity.

* T _PRS,i is the effective PRS periodicity with PRS muting. T _PRS,i = , where k is the resource set index.

* is the higher-later parameter DL-PRS-Periodicity .

* N _muting is a scaling factor considering PRS muting.

If positioning frequency layer z has more than one DL PRS resource set with different PRS periodicities, the maximum PRS periodicity among DL PRS resource sets is used to derive the measurement period of that positioning frequency layer. The measurement period length requirement T _{RSTD Total} for L number of positioning frequency layers (PFLs) is given by: where i is the PFL index. The first term is the summation of the per-PFL durations, and the second term accounts for the transitions between PFLs.

[0131] As can be seen by the equations above, the measurement period formulas depend upon many parameters. Thus, one challenge is how to characterize the dependence of the measurement delay on the assistance data and the measurement gap configuration, and another is how the network, the UE, or both, can use such a characterization to reduce the measurement delay for low-latency positioning applications. Some parameters, such as

N _i , T _i , and , are UE PRS processing capability parameters, which are provided by the UE and generally do not change.

[0132] FIG. 10 is a time and frequency graph 1000 illustrating some of the parameters derived from the assistance data, and their effect on the measurement period. FIG. 10 illustrates three measurement gaps (MGs) 1002 and six different PRS resources identified by the legend in FIG. 10. The PRS resources can be transmitted by multiple TRPs. In conventional networks, only PRS resources that occur within an MG can be measured by the UE. Parameters that depend on the assistance data and the measurement gap configuration include the number of PFLs (which are processed sequentially), , and . Thus, these parameters are ones that the network may manipulate or configure via assistance data. Another parameter, N _sample , is another parameter that the network may manipulate or configure. Parameters that are under the control of the UE include CSSF _PRS,i , and N _RxBeam,i

[0133] To characterize the dependence of the measurement delay on the assistance data and the measurement gap configuration, it is noted that the term "PRS processing load" (represented by the character lambda "λ") refers to the number, duration, and availability of PRS resources relative to the UE's capability to process those PRS resources, and may be expressed as a ratio of the PRS resources over the UE's capacity to process those resources. Thus, when PRS processing load is greater than one, this indicates that there are more PRS resources to be processed than the UE has the capability to process in the required time. Moreover, it has been observed that the PRS measurement period length requirement scales approximately linearly with the effective normalized PRS load defined as follows:

When λ _PRS,i = 1, this indicates a load-limited or demand-limited scenario, e.g., the UE can keep up with processing in real time. When λ _PRS,i > 1, this indicates a processing- limited scenario, e.g., the UE needs more time to process all of the PRS signals, and thus will need to skip some processing. For example, given the parameters listed in Table 1, below, the PRS measurement period requirement will be as shown in Table 2, below:

Table 1 - Sample NR Positioning Scenario in FR1

Table 2 - PRS Measurement Period Requirement for Scenario in Table 1

[0134] It is desirable to provide a mechanism by which the network, the UE, or both, may enable or accommodate low-latency positioning measurements. Therefore, techniques for low- latency positioning measurements are herein presented.

[0135] Network-based approaches. In one approach, the network may take into account the

UE's processing load, e.g., as quantified by X _PRS,i , when providing assistance data and requesting low-latency measurements, in order to optimize the measurement latency. In some aspects, to reduce measurement delay according to the requirement, an LMF or other network entity could do one or more of the following:

• Reduce the number of PFLs that the UE is requested to monitor;

• For a given number of PFLs, the network could choose to place the PFLs in frequency bands in which the UE has higher processing capability;

Pack no more than N _t PRS resources per slot in PFL i;

• Pack at least N _i time duration of PRS per measurement gap in PFL i; or

• Select the PRS periodicity and measurement gap periodicity so that T _{available PRS,i}

T _i . Note that increasing T _{available PRS,i} substantially beyond T _i would be counter- productive.

[0136] It is noted that, because of the number of factors involved in the calculation of lambda and their relationships to the number of PFLs, TRPs, resources per TRP, etc., the problem of minimizing the measurement delay requirement with respect to the assistance data is highly non-linear and thus susceptible to multiple algorithmic solutions. One approach, for example, is for the network to attempt to tune the PRS assistance data to minimize the processing load. Once a processing load of unity is achieved, then no further improvement is needed from the measurement requirements perspective.

[0137] UE-based approaches. In another approach, the UE may determine (or be signaled) that measurements are associated with a low-latency location request, which may enable the UE to modify behaviors that are otherwise mandated or assumed, e.g., to prioritize those measurements. For example, in some aspects a positioning frequency layer (PFL) may be treated as low-latency by the UE if an LMF or other location server requests that the UE report measurements with some number of samples less than a sample threshold (e.g., N _sample ≤ N _THRESHOLD ) and/or the normalized PRS load less than a normalized PRS load threshold (e.g., λ _PRS,i ≤ N _THRESHOLD ). In some aspects, if an LMF requests that the UE reports measurements with N _THRESHOLD = 1 (single sample), and λ _THRESHOLD = 1 (load-limited) for a particular PFL, that PFL is considered a low-latency PFL.

[0138] Actions that may be taken by the UE in response to determining that measurements are associated with a low-latency location request may include, but are not limited to, the following. In some aspects, when a UE determines or is notified that a particular PFL is a low-latency PFL, the UE may prioritize measurements on that PFL, e.g., by setting CSSF _PRS,i = 1 so that there is no sharing of measurement gaps with RRM measurements. In some aspects, the UE may process a smaller number of samples than the fixed value of four that is conventionally mandated by the specifications. In some aspects, the UE may use a smaller number of Rx beams to measure the resources. The network-based approaches and the UE-based approaches may be used together or separately.

[0139] FIG. 11 is a flowchart of an example process 1100 associated with UE processing load- aware PRS measurement period optimization, according to aspects of the disclosure. In some implementations, one or more process blocks of FIG. 11 may be performed by a network entity (location server 172, LMF 270, etc.). In some implementations, one or more process blocks of FIG. 11 may be performed by another device or a group of devices separate from or including the network entity. Additionally, or alternatively, one or more process blocks of FIG. 11 may be performed by one or more components of network entity 306, such as processor(s) 394, memory 396, network transceiver(s) 390, and positioning module(s) 398, any or all of which may be means for performing the operations of process 1100. [0140] As shown in FIG. 11, process 1100 may include, at block 1110, determining that a positioning reference signal (PRS) processing load for a UE (i.e., how many PRS resources the UE is asked to measure) exceeds a PRS processing capacity of the UE (i.e., the UE's ability to process the PRS in real time without additional delays). If the PRS processing load exceeds the PRS process capability, the UE will still process all the data but it will not be able to do so as soon as the data becomes available over the air interface. Processing the data as soon as it is available should be beneficial for low- latency positioning. Means for performing the operation of block 1110 may include the processor(s) 394, memory 396, or network transceiver(s) 390 of the network entity 306. For example, in some aspects, determining that the PRS processing load for the UE exceeds the PRS processing capacity of the UE comprises receiving, from the UE, capability information associated with the PRS processing capability of the UE, and determining that the PRS processing load for the UE exceeds the PRS processing capacity of the UE based on the capability information. The network entity 306 may receive the information via the network transceiver(s) 390 and use the processor(s) 394 to determine that the PRS processing load for the UE exceeds the PRS processing capacity of the UE. [0141] In some aspects, receiving the capability information associated with the PRS processing capability of the UE comprises receiving at least one of a first duration in time N of PRS symbols that can be processed every second duration in time T, or a third number N' of PRS resources that the UE can process during a slot. In some aspects, determining that the PRS processing load for the UE exceeds the PRS processing capability of the UE based on the capability information comprises calculating a PRS processing load coefficient as a function of a maximum number of PRS resources per slot in a positioning frequency layer (PFL), a periodicity of PRS resources available within a measurement gap for the PFL, a time duration of PRS resources available in the PFL, and the capability information associated with the PRS processing capability of the UE. In some aspects, determining that the PRS processing load for the UE exceeds the PRS processing capability of the UE based on the capability information comprises determining that the PRS processing load coefficient exceeds a first threshold value. [0142] As further shown in FIG. 11, process 1100 may include, at block 1120, sending, to the UE assistance data that reduces the PRS processing load for the UE Means for performing the operation of block 1120 may include the processor(s) 394, memory 396, or network transceiver(s) 390 of the network entity 306. For example, the assistance data may be sent to the UE via the network transceiver(s) 390. In some aspects, sending, to the UE, assistance data that reduces the PRS processing load for the UE comprises sending assistance data that decreasing a number of positioning frequency layers (PFLs) that the UE is requested to monitor, decreasing a number of PRS resources per slot, decreasing a time duration for PRS in each measurement gap, matching the measurement gap periodicity and the PRS periodicity to the processing time T _i for each PFL, matching Tavailable to Ti for each PFL, or a combination thereof. [0143] In some aspects, process 1100 includes sending, to the UE, a location request, the location request indicating a reduced number of samples to be taken for each PRS resource. In some aspects, the network entity comprises a location server, a base station, or a combination thereof. [0144] Process 1100 may include additional implementations, such as any single implementation or any combination of implementations described below and/or in connection with one or more other processes described elsewhere herein. Although FIG. 11 shows example blocks of process 1100, in some implementations, process 1100 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in FIG.11. Additionally, or alternatively, two or more of the blocks of process 1100 may be performed in parallel. [0145] FIG. 12 is a flowchart of an example process 1200 associated with UE processing load- aware PRS measurement period optimization, according to aspects of the disclosure. In some implementations, one or more process blocks of FIG. 12 may be performed by a user equipment (UE) (e.g., UE 104). In some implementations, one or more process blocks of FIG. 12 may be performed by another device or a group of devices separate from or including the UE. Additionally, or alternatively, one or more process blocks of FIG.12 may be performed by one or more components of UE 302, such as processor(s) 332, memory 340, WWAN transceiver(s) 310, short-range wireless transceiver(s) 320, satellite signal receiver 330, sensor(s) 344, user interface 346, and positioning module(s) 342, any or all of which may be means for performing the operations of process 1200. [0146] As shown in FIG. 12, process 1200 may include, at block 1210, determining, based on information received from a network entity, that one or more positioning reference signal (PRS) measurements is associated with a low-latency location request Means for performing the operation of block 1210 may include the processor(s) 332, memory 340, or WWAN transceiver(s) 310 of the UE 302. For example, the UE 302 may determine that one or more positioning reference signal (PRS) measurements is associated with a low-latency location request, using the processor(s) 332. In some aspects, determining that the one or more PRS measurements is associated with a low-latency location request comprises determining that a positioning frequency layer (PFL) in which the one or more PRS measurements are to be made is a low-latency PFL. [0147] In some aspects, determining that the PFL in which the one or more PRS measurements are to be made is a low-latency PFL comprises receiving, from the network entity, an indication that the PFL is a low-latency PFL. In some aspects, determining that the one or more PRS measurements is associated with a low-latency location request comprises receiving, from the network entity, assistance data that results in a PRS processing load for the UE that does not exceed a PRS processing capacity of the UE. In some aspects, receiving the assistance data that results in a PRS processing load for the UE that does not exceed a PRS processing capacity of the UE comprises receiving assistance data that decreasing a number of positioning frequency layers (PFLs) that the UE is requested to monitor, decreasing a number of PRS resources per slot, decreasing a time duration for PRS in each measurement gap, matching the measurement gap periodicity and the PRS periodicity to the processing time T _i for each PFL, matching T _available to Ti for each PFL, or a combination thereof. In some aspects, determining, based on the information received from the network entity, that the one or more PRS measurements is associated with a low- latency location request comprises receiving, from a network entity, a location request, the location request indicating a reduced number of samples to be taken for each PRS resource. In some aspects, the network entity comprises a location server, a base station, or a combination thereof. [0148] As further shown in FIG.12, process 1200 may include, at block 1220, modifying one or more parameters associated with the one or more PRS measurements to reduce measurement latency. Means for performing the operation of block 1220 may include the processor(s) 332, memory 340, or WWAN transceiver(s) 310 of the UE 302. For example, the UE 302 may modify one or more parameters associated with the one or more PRS measurements to reduce measurement latency, using the processor(s) 332. In some aspects, modifying one or more parameters associated with the one or more PRS measurements to reduce measurement latency comprises setting a carrier-specific scaling factor (CSSF) to avoid sharing measurement gaps with other measurements, reducing a receive beam sweeping factor, or a combination thereof. [0149] As further shown in FIG. 12, process 1200 may include, at block 1230, performing the one or more PRS measurements associated with the low-latency location request according to the modified one or more parameters. Means for performing the operation of block 1230 may include the processor(s) 332, memory 340, or WWAN transceiver(s) 310 of the UE 302. For example, the UE 302 may perform the one or more PRS measurements associated with the low-latency location request according to the modified one or more parameters, using the WWAN transceiver(s) 310. [0150] Process 1200 may include additional implementations, such as any single implementation or any combination of implementations described below and/or in connection with one or more other processes described elsewhere herein. Although FIG. 12 shows example blocks of process 1200, in some implementations, process 1200 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in FIG.12. Additionally, or alternatively, two or more of the blocks of process 1200 may be performed in parallel. [0151] As will be appreciated, a technical advantage of method 1100 and method 1200 is that they allow the network and the UE, respectively, to optimize parameters associated with positioning measurements for low-latency positioning scenarios. Method 1100 provides mechanisms by which the network can adjust measurement parameters based on the specific capabilities of a UE. Method 1200 provides mechanisms by which a UE can optimize its own operating conditions to enable low-latency measurements and reporting. [0152] In the detailed description above it can be seen that different features are grouped together in examples. This manner of disclosure should not be understood as an intention that the example clauses have more features than are explicitly mentioned in each clause. Rather, the various aspects of the disclosure may include fewer than all features of an individual example clause disclosed. Therefore, the following clauses should hereby be deemed to be incorporated in the description, wherein each clause by itself can stand as a separate example. Although each dependent clause can refer in the clauses to a specific combination with one of the other clauses, the aspect(s) of that dependent clause are not limited to the specific combination. It will be appreciated that other example clauses can also include a combination of the dependent clause aspect(s) with the subject matter of any other dependent clause or independent clause or a combination of any feature with other dependent and independent clauses. The various aspects disclosed herein expressly include these combinations, unless it is explicitly expressed or can be readily inferred that a specific combination is not intended (e.g., contradictory aspects, such as defining an element as both an electrical insulator and an electrical conductor). Furthermore, it is also intended that aspects of a clause can be included in any other independent clause, even if the clause is not directly dependent on the independent clause. [0153] Implementation examples are described in the following numbered clauses: [0154] Clause 1. A method of wireless positioning performed by a network entity, the method comprising: determining that a positioning reference signal (PRS) processing load for a UE exceeds a PRS processing capacity of the UE; and sending, to the UE, assistance data that reduces the PRS processing load for the UE. [0155] Clause 2. The method of clause 1, wherein determining that the PRS processing load for the UE exceeds the PRS processing capacity of the UE comprises: receiving, from the UE, capability information associated with the PRS processing capability of the UE; and determining that the PRS processing load for the UE exceeds the PRS processing capacity of the UE based on the capability information. [0156] Clause 3. The method of clause 2, wherein receiving the capability information associated with the PRS processing capability of the UE comprises receiving at least one of: a first duration in time N of PRS symbols that can be processed every second duration in time T; or a third number N' of PRS resources that the UE can process during a slot. [0157] Clause 4. The method of any of clauses 2 to 3, wherein determining that the PRS processing load for the UE exceeds the PRS processing capability of the UE based on the capability information comprises calculating a PRS processing load coefficient as a function of a maximum number of PRS resources per slot in a positioning frequency layer (PFL), a periodicity of PRS resources available within a measurement gap for the PFL, a time duration of PRS resources available in the PFL, and the capability information associated with the PRS processing capability of the UE. [0158] Clause 5. The method of clause 4, wherein determining that the PRS processing load for the UE exceeds the PRS processing capability of the UE based on the capability information comprises determining that the PRS processing load coefficient exceeds a first threshold value. [0159] Clause 6. The method of any of clauses 1 to 5, wherein sending, to the UE, assistance data that reduces the PRS processing load for the UE comprises sending assistance data that: decreases a number of positioning frequency layers (PFLs) that the UE is requested to monitor; decreases a number of PRS resources per slot; decreases a time duration for PRS in each measurement gap; increases a period of PRS resources within the measurement gap for each PFL; matches a measurement gap periodicity and a PRS periodicity to a processing time for PRS symbols for each PFL; or a combination thereof. [0160] Clause 7. The method of any of clauses 1 to 6, further comprising: sending, to the UE, a location request, the location request indicating a reduced number of samples to be taken for each PRS resource, a reduced receive beam sweeping factor, or a combination thereof. [0161] Clause 8. A method of wireless positioning performed by a user equipment (UE), the method comprising: determining, based on information received from a network entity, that one or more positioning reference signal (PRS) measurements is associated with a low-latency location request; modifying one or more parameters associated with the one or more PRS measurements to reduce measurement latency; and performing the one or more PRS measurements associated with the low-latency location request according to the modified one or more parameters. [0162] Clause 9. The method of clause 8, wherein determining that the one or more PRS measurements is associated with a low-latency location request comprises determining that a positioning frequency layer (PFL) in which the one or more PRS measurements are to be made is a low-latency PFL. [0163] Clause 10. The method of clause 9, wherein determining that the PFL in which the one or more PRS measurements are to be made is a low-latency PFL comprises receiving, from the network entity, an indication that the PFL is a low-latency PFL. [0164] Clause 11. The method of any of clauses 8 to 10, wherein determining that the one or more PRS measurements is associated with a low-latency location request comprises receiving, from the network entity, assistance data that results in a PRS processing load for the UE that does not exceed a PRS processing capacity of the UE. [0165] Clause 12. The method of clause 11, wherein receiving the assistance data that results in a PRS processing load for the UE that does not exceed a PRS processing capacity of the UE comprises receiving assistance data that: decreases a number of positioning frequency layers (PFLs) that the UE is requested to monitor; decreases a number of PRS resources per slot; decreases a time duration for PRS in each measurement gap; increases a period of PRS resources within the measurement gap for each PFL; matches a measurement gap periodicity and a PRS periodicity to a processing time for PRS symbols for each PFL; or a combination thereof. [0166] Clause 13. The method of any of clauses 8 to 12, wherein determining, based on the information received from the network entity, that the one or more PRS measurements is associated with a low-latency location request comprises receiving, from a network entity, a location request, the location request indicating a reduced number of samples to be taken for each PRS resource, a reduced receive beam sweeping factor, or a combination thereof. [0167] Clause 14. The method of any of clauses 8 to 13, wherein modifying one or more parameters associated with the one or more PRS measurements to reduce measurement latency comprises: setting a carrier-specific scaling factor (CSSF) to avoid sharing measurement gaps with other measurements; reducing a receive beam sweeping factor; or a combination thereof. [0168] Clause 15. A network entity, comprising: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to: determine that a positioning reference signal (PRS) processing load for a UE exceeds a PRS processing capacity of the UE; and send, via the at least one transceiver, to the UE, assistance data that reduces the PRS processing load for the UE. [0169] Clause 16. The network entity of clause 15, wherein, to determine that the PRS processing load for the UE exceeds the PRS processing capacity of the UE, the at least one processor is configured to: receive, from the UE via the at least one transceiver, capability information associated with the PRS processing capability of the UE; and determine that the PRS processing load for the UE exceeds the PRS processing capacity of the UE based on the capability information. [0170] Clause 17. The network entity of clause 16, wherein, to receive the capability information associated with the PRS processing capability of the UE, the at least one processor is configured to receive at least one of: a first duration in time N of PRS symbols that can be processed every second duration in time T; or a third number N' of PRS resources that the UE can process during a slot. [0171] Clause 18. The network entity of any of clauses 16 to 17, wherein, to determine that the PRS processing load for the UE exceeds the PRS processing capability of the UE based on the capability information, the at least one processor is configured to calculate a PRS processing load coefficient as a function of a maximum number of PRS resources per slot in a positioning frequency layer (PFL), a periodicity of PRS resources available within a measurement gap for the PFL, a time duration of PRS resources available in the PFL, and the capability information associated with the PRS processing capability of the UE. [0172] Clause 19. The network entity of clause 18, wherein, to determine that the PRS processing load for the UE exceeds the PRS processing capability of the UE based on the capability information, the at least one processor is configured to determine that the PRS processing load coefficient exceeds a first threshold value. [0173] Clause 20. The network entity of any of clauses 15 to 19, wherein, to send, to the UE, assistance data that reduces the PRS processing load for the UE, the at least one processor is configured to send assistance data that: decreases a number of positioning frequency layers (PFLs) that the UE is requested to monitor; decreases a number of PRS resources per slot; decreases a time duration for PRS in each measurement gap; increases a period of PRS resources within the measurement gap for each PFL; matches a measurement gap periodicity and a PRS periodicity to a processing time for PRS symbols for each PFL; or a combination thereof. [0174] Clause 21. The network entity of any of clauses 15 to 20, wherein the at least one processor is further configured to: send, via the at least one transceiver, to the UE, a location request, the location request indicating a reduced number of samples to be taken for each PRS resource, a reduced receive beam sweeping factor, or a combination thereof. [0175] Clause 22. The network entity of any of clauses 15 to 21, wherein the network entity comprises a location server, a base station, or a combination thereof. [0176] Clause 23. A user equipment (UE), comprising: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to: determine, based on information received from a network entity, that one or more positioning reference signal (PRS) measurements is associated with a low-latency location request; modify one or more parameters associated with the one or more PRS measurements to reduce measurement latency; and perform the one or more PRS measurements associated with the low-latency location request according to the modified one or more parameters. [0177] Clause 24. The UE of clause 23, wherein, to determine that the one or more PRS measurements is associated with a low-latency location request, the at least one processor is configured to determine that a positioning frequency layer (PFL) in which the one or more PRS measurements are to be made is a low-latency PFL [0178] Clause 25. The UE of clause 24, wherein, to determine that the PFL in which the one or more PRS measurements are to be made is a low-latency PFL, the at least one processor is configured to receive, from the network entity, an indication that the PFL is a low- latency PFL. [0179] Clause 26. The UE of any of clauses 23 to 25, wherein, to determine that the one or more PRS measurements is associated with a low-latency location request, the at least one processor is configured to receive, from the network entity, assistance data that results in a PRS processing load for the UE that does not exceed a PRS processing capacity of the UE. [0180] Clause 27. The UE of clause 26, wherein, to receive the assistance data that results in a PRS processing load for the UE that does not exceed a PRS processing capacity of the UE, the at least one processor is configured to receive assistance data that: decreases a number of positioning frequency layers (PFLs) that the UE is requested to monitor; decreases a number of PRS resources per slot; decreases a time duration for PRS in each measurement gap; increases a period of PRS resources within the measurement gap for each PFL; matches a measurement gap periodicity and a PRS periodicity to a processing time for PRS symbols for each PFL; or a combination thereof. [0181] Clause 28. The UE of any of clauses 23 to 27, wherein, to determine, based on the information received from the network entity, that the one or more PRS measurements is associated with a low-latency location request, the at least one processor is configured to receive, from a network entity, a location request, the location request indicating a reduced number of samples to be taken for each PRS resource, a reduced receive beam sweeping factor, or a combination thereof. [0182] Clause 29. The UE of any of clauses 23 to 28, wherein, to modify one or more parameters associated with the one or more PRS measurements to reduce measurement latency, the at least one processor is configured to: set a carrier-specific scaling factor (CSSF) to avoid sharing measurement gaps with other measurements; reduce a receive beam sweeping factor; or a combination thereof. [0183] Clause 30. The UE of any of clauses 23 to 29, wherein the network entity comprises a location server, a base station, or a combination thereof. [0184] Clause 31. An apparatus comprising 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 of clauses 1 to 14. [0185] Clause 32. An apparatus comprising means for performing a method according to any of clauses 1 to 14. [0186] Clause 33. A non-transitory computer-readable medium storing computer-executable instructions, the computer-executable comprising at least one instruction for causing a computer or processor to perform a method according to any of clauses 1 to 14. [0187] Those of skill in the art will appreciate that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof. [0188] Further, those of skill in the art will appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the aspects disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure. [0189] The various illustrative logical blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented or performed with a general purpose processor, a digital signal processor (DSP), an ASIC, a field-programable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A 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 any other such configuration. [0190] The methods, sequences and/or algorithms described in connection with the aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in random access memory (RAM), flash memory, read-only memory (ROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An example storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal (e.g., UE). In the alternative, the processor and the storage medium may reside as discrete components in a user terminal. [0191] In one or more example aspects, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically while discs reproduce data optically with lasers Combinations of the above should also be included within the scope of computer-readable media. [0192] While the foregoing disclosure shows illustrative aspects of the disclosure, it should be noted that various changes and modifications could 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 contemplated unless limitation to the singular is explicitly stated.