WO2025034521A1

WO2025034521A1 - Aperiodic sidelink resource reservation request

Info

Publication number: WO2025034521A1
Application number: PCT/US2024/040617
Authority: WO
Inventors: Alexandros MANOLAKOS; Mukesh Kumar; Gabi Sarkis
Original assignee: Qualcomm Inc
Current assignee: Qualcomm Inc
Priority date: 2023-08-07
Filing date: 2024-08-01
Publication date: 2025-02-13
Anticipated expiration: 2026-02-07

Abstract

Disclosed are techniques for wireless communication. Aspects of the disclosure are directed to an aperiodic sidelink resource reservation request that requests reservation of a set of time-frequency resources associated with a future time that is offset relative to a time reference, or alternatively requests reservation of a set of time-frequency resources at a future absolute time.

Description

APERIODIC SIDELINK RESOURCE RESERVATION REQUEST BACKGROUND OF THE DISCLOSURE 1. Field of the Disclosure [0001] Aspects of the disclosure relate generally to wireless technologies. 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 operating a first user equipment (UE) includes transmitting an aperiodic sidelink resource reservation request of a first type to a second UE, wherein the aperiodic sidelink resource reservation request requests reservation of a set of time- frequency resources associated with a future time that is offset relative to a time reference, and wherein aperiodic sidelink resource reservation requests of the first type are associated with a first set of relative timing offset options and aperiodic sidelink resource reservation requests of a second type are associated with a second set of relative timing offset options that is different than the first set of relative timing offset options; and communicating with the second UE on the set of time-frequency resources in accordance with the aperiodic sidelink resource reservation request. [0006] In an aspect, a method of operating a second user equipment (UE) includes receiving an aperiodic sidelink resource reservation request of a first type from a first UE, wherein the aperiodic sidelink resource reservation request requests reservation of a set of time- frequency resources at a future time that is offset relative to a time reference, and wherein aperiodic sidelink resource reservation requests of the first type are associated with a first set of relative timing offset options and aperiodic sidelink resource reservation requests of a second type are associated with a second set of relative timing offset options that is different than the first set of relative timing offset options; and communicating with the first UE on the set of time-frequency resources in accordance with the aperiodic sidelink resource reservation request. [0007] In an aspect, a method of operating a first user equipment (UE) includes transmitting an aperiodic sidelink resource reservation request to a second UE that requests reservation of a set of time-frequency resources at a future absolute time; and communicating with the second UE on the set of time-frequency resources in accordance with the aperiodic sidelink resource reservation request. [0008] In an aspect, a method of operating a second user equipment (UE) includes receiving an aperiodic sidelink resource reservation request from a first UE that requests reservation of a set of time-frequency resources at a future absolute time; and communicating with the first UE on the set of time-frequency resources in accordance with the aperiodic sidelink resource reservation request. [0009] In an aspect, a first user equipment (UE) includes one or more memories; and one or more processors communicatively coupled to the one or more memories, the one or more processors, either alone or in combination, configured to: transmit an aperiodic sidelink resource reservation request of a first type to a second UE, wherein the aperiodic sidelink resource reservation request requests reservation of a set of time-frequency resources associated with a future time that is offset relative to a time reference, and wherein aperiodic sidelink resource reservation requests of the first type are associated with a first set of relative timing offset options and aperiodic sidelink resource reservation requests of a second type are associated with a second set of relative timing offset options that is different than the first set of relative timing offset options; and communicate with the second UE on the set of time-frequency resources in accordance with the aperiodic sidelink resource reservation request. [0010] In an aspect, a second user equipment (UE) includes one or more memories; and one or more processors communicatively coupled to the one or more memories, the one or more processors, either alone or in combination, configured to: receive an aperiodic sidelink resource reservation request of a first type from a first UE, wherein the aperiodic sidelink resource reservation request requests reservation of a set of time-frequency resources at a future time that is offset relative to a time reference, and wherein aperiodic sidelink resource reservation requests of the first type are associated with a first set of relative timing offset options and aperiodic sidelink resource reservation requests of a second type are associated with a second set of relative timing offset options that is different than the first set of relative timing offset options; and communicate with the first UE on the set of time-frequency resources in accordance with the aperiodic sidelink resource reservation request. [0011] In an aspect, a user equipment (UE) includes one or more memories; and one or more processors communicatively coupled to the one or more memories, the one or more processors, either alone or in combination, configured to: transmit an aperiodic sidelink resource reservation request to a second UE that requests reservation of a set of time- frequency resources at a future absolute time; and communicate with the second UE on the set of time-frequency resources in accordance with the aperiodic sidelink resource reservation request. [0012] In an aspect, a user equipment (UE) includes one or more memories; and one or more processors communicatively coupled to the one or more memories, the one or more processors, either alone or in combination, configured to: receive an aperiodic sidelink resource reservation request from a first UE that requests reservation of a set of time- frequency resources at a future absolute time; and communicate with the first UE on the set of time-frequency resources in accordance with the aperiodic sidelink resource reservation request. [0013] In an aspect, a first user equipment (UE) includes means for transmitting an aperiodic sidelink resource reservation request of a first type to a second UE, wherein the aperiodic sidelink resource reservation request requests reservation of a set of time-frequency resources associated with a future time that is offset relative to a time reference, and wherein aperiodic sidelink resource reservation requests of the first type are associated with a first set of relative timing offset options and aperiodic sidelink resource reservation requests of a second type are associated with a second set of relative timing offset options that is different than the first set of relative timing offset options; and means for communicating with the second UE on the set of time-frequency resources in accordance with the aperiodic sidelink resource reservation request. [0014] In an aspect, a second user equipment (UE) includes means for receiving an aperiodic sidelink resource reservation request of a first type from a first UE, wherein the aperiodic sidelink resource reservation request requests reservation of a set of time-frequency resources at a future time that is offset relative to a time reference, and wherein aperiodic sidelink resource reservation requests of the first type are associated with a first set of relative timing offset options and aperiodic sidelink resource reservation requests of a second type are associated with a second set of relative timing offset options that is different than the first set of relative timing offset options; and means for communicating with the first UE on the set of time-frequency resources in accordance with the aperiodic sidelink resource reservation request. [0015] In an aspect, a user equipment (UE) includes means for transmitting an aperiodic sidelink resource reservation request to a second UE that requests reservation of a set of time- frequency resources at a future absolute time; and means for communicating with the second UE on the set of time-frequency resources in accordance with the aperiodic sidelink resource reservation request. [0016] In an aspect, a user equipment (UE) includes means for receiving an aperiodic sidelink resource reservation request from a first UE that requests reservation of a set of time- frequency resources at a future absolute time; and means for communicating with the first UE on the set of time-frequency resources in accordance with the aperiodic sidelink resource reservation request. [0017] In an aspect, a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a first user equipment (UE), cause the UE to: transmit an aperiodic sidelink resource reservation request of a first type to a second UE, wherein the aperiodic sidelink resource reservation request requests reservation of a set of time- frequency resources associated with a future time that is offset relative to a time reference, and wherein aperiodic sidelink resource reservation requests of the first type are associated with a first set of relative timing offset options and aperiodic sidelink resource reservation requests of a second type are associated with a second set of relative timing offset options that is different than the first set of relative timing offset options; and communicate with the second UE on the set of time-frequency resources in accordance with the aperiodic sidelink resource reservation request. [0018] In an aspect, a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a second user equipment (UE), cause the UE to: receive an aperiodic sidelink resource reservation request of a first type from a first UE, wherein the aperiodic sidelink resource reservation request requests reservation of a set of time-frequency resources at a future time that is offset relative to a time reference, and wherein aperiodic sidelink resource reservation requests of the first type are associated with a first set of relative timing offset options and aperiodic sidelink resource reservation requests of a second type are associated with a second set of relative timing offset options that is different than the first set of relative timing offset options; and communicate with the first UE on the set of time-frequency resources in accordance with the aperiodic sidelink resource reservation request. [0019] In an aspect, a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a user equipment (UE), cause the UE to: transmit an aperiodic sidelink resource reservation request to a second UE that requests reservation of a set of time-frequency resources at a future absolute time; and communicate with the second UE on the set of time-frequency resources in accordance with the aperiodic sidelink resource reservation request. [0020] In an aspect, a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a user equipment (UE), cause the UE to: receive an aperiodic sidelink resource reservation request from a first UE that requests reservation of a set of time-frequency resources at a future absolute time; and communicate with the first UE on the set of time-frequency resources in accordance with the aperiodic sidelink resource reservation request. [0021] 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 [0022] 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. [0023] FIG. 1 illustrates an example wireless communications system, according to aspects of the disclosure. [0024] FIGS.2A, 2B, and 2C illustrate example wireless network structures, according to aspects of the disclosure. [0025] 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. [0026] FIG. 4 is a diagram illustrating an example frame structure, according to aspects of the disclosure. [0027] FIGS. 5A and 5B are diagrams of example sidelink slot structures with and without feedback resources, according to aspects of the disclosure. [0028] FIG. 6 is a diagram showing how a shared channel (SCH) is established on a sidelink between two or more UEs, according to aspects of the disclosure. [0029] FIG.7 is a diagram illustrating an example of a resource pool for positioning configured within a sidelink resource pool for communication, according to aspects of the disclosure. [0030] FIG. 8A illustrates an example call flow for Mode A discovery, and FIG. 8B illustrates an example call flow for Mode B discovery, according to aspects of the disclosure. [0031] FIGS.9A and 9B illustrate various scenarios of interest for sidelink-only or joint Uu and sidelink positioning, according to aspects of the disclosure. [0032] FIG. 10 illustrates the two resource allocation modes for transmissions on a sidelink, according to aspects of the disclosure. [0033] FIG. 11 illustrates a location preparation phase of a position estimation procedure, in accordance with aspects of the disclosure. [0034] FIG.12 illustrates a location execution phase of the position estimation procedure of FIG. 11, in accordance with aspects of the disclosure. [0035] FIG. 13 depicts timing information associated with the respective phases depicted in FIGS.11-12 in accordance with aspects of the disclosure. [0036] FIG.14 illustrates an exemplary process of communications according to an aspect of the disclosure. [0037] FIG.15 illustrates an exemplary process of communications according to an aspect of the disclosure. [0038] FIG.16 illustrates an exemplary process of communications according to an aspect of the disclosure. [0039] FIG.17 illustrates an exemplary process of communications according to an aspect of the disclosure. [0040] FIG. 18 illustrates an example implementation of any of the processes of FIGS. 14-17, respectively, in accordance with aspects of the disclosure. [0041] FIG. 19 illustrates an example implementation of any of the processes of FIGS. 14-17, respectively, in accordance with aspects of the disclosure. [0042] FIG. 20 illustrates an example implementation of any of the processes of FIGS. 14-17, respectively, in accordance with aspects of the disclosure. [0043] FIG. 21 illustrates an example implementation of any of the processes of FIGS. 14-17, respectively, in accordance with aspects of the disclosure. DETAILED DESCRIPTION [0044] 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. [0045] Various aspects relate generally to aperiodic sidelink resource reservation requests. Scheduled location is used when the location of user equipment (UE) is desired at specific times in the future. For example, vehicles on a road may all be located at the same time to provide an indication of traffic congestion as well as to assist with vehicle communication. People, containers, transportation systems etc., may also be located at certain common times. Scheduled positioning sessions are known in Uu framework. However, scheduling of sidelink resources for scheduled position estimation sessions is limited. [0046] Particular aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. Aspects of the disclosure are directed to an aperiodic sidelink resource reservation request that requests reservation of a set of time-frequency resources associated with a future time that is offset relative to a time reference, or alternatively requests reservation of a set of time-frequency resources at a future absolute time. Such aspects may provide various technical advantages, such as flexibly supporting scheduled position estimation for sidelink-based position estimation sessions (e.g., which may facilitate location tracking that satisfies various application requirements for V2X, inventory tracking systems, and so on). [0047] 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. [0048] 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. [0049] 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. [0050] 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. [0051] 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. [0052] 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. [0053] 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). [0054] 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. [0055] 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. [0056] 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. [0057] 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. [0058] 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. [0059] 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). [0060] 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). [0061] 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. [0062] 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®. [0063] 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. [0064] 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. [0065] 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. [0066] 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. [0067] 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. [0068] 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. [0069] 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 TELECOMMUNICATION UNION® as a “millimeter wave” band. [0070] 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. [0071] 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. [0072] 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. [0073] 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. [0074] 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. [0075] 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. [0076] 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 802.11x 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. [0077] 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. [0078] 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. [0079] 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. [0080] 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. [0081] 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), WI-FI DIRECT®, BLUETOOTH®, and so on. [0082] 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). [0083] 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). [0084] 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. [0085] 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. [0086] 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. [0087] 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). [0088] 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. [0089] 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. [0090] 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. [0091] Deployment of communication systems, such as 5G NR systems, may be arranged in multiple manners with various components or constituent parts. In a 5G NR system, or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, or a network equipment, such as a base station, or one or more units (or one or more components) performing base station functionality, may be implemented in an aggregated or disaggregated architecture. For example, a base station (such as a Node B (NB), evolved NB (eNB), NR base station, 5G NB, access point (AP), a transmit receive point (TRP), or a cell, etc.) may be implemented as an aggregated base station (also known as a standalone base station or a monolithic base station) or a disaggregated base station. [0092] An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed throughout one or multiple other RAN nodes. The DUs may be implemented to communicate with one or more RUs. Each of the CU, DU and RU also can be implemented as virtual units, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU). [0093] Base station-type operation or network design may consider aggregation characteristics of base station functionality. For example, disaggregated base stations may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (such as the network configuration sponsored by the O-RAN ALLIANCE®)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C- RAN)). Disaggregation may include distributing functionality across two or more units at various physical locations, as well as distributing functionality for at least one unit virtually, which can enable flexibility in network design. The various units of the disaggregated base station, or disaggregated RAN architecture, can be configured for wired or wireless communication with at least one other unit. [0094] FIG. 2C illustrates an example disaggregated base station architecture 250, according to aspects of the disclosure. The disaggregated base station architecture 250 may include one or more central units (CUs) 280 (e.g., gNB-CU 226) that can communicate directly with a core network 267 (e.g., 5GC 210, 5GC 260) via a backhaul link, or indirectly with the core network 267 through one or more disaggregated base station units (such as a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC) 259 via an E2 link, or a Non-Real Time (Non-RT) RIC 257 associated with a Service Management and Orchestration (SMO) Framework 255, or both). A CU 280 may communicate with one or more DUs 285 (e.g., gNB-DUs 228) via respective midhaul links, such as an F1 interface. The DUs 285 may communicate with one or more radio units (RUs) 287 (e.g., gNB-RUs 229) via respective fronthaul links. The RUs 287 may communicate with respective UEs 204 via one or more radio frequency (RF) access links. In some implementations, the UE 204 may be simultaneously served by multiple RUs 287. [0095] Each of the units, i.e., the CUs 280, the DUs 285, the RUs 287, as well as the Near-RT RICs 259, the Non-RT RICs 257 and the SMO Framework 255, may include one or more interfaces or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller providing instructions to the communication interfaces of the units, can be configured to communicate with one or more of the other units via the transmission medium. For example, the units can include a wired interface configured to receive or transmit signals over a wired transmission medium to one or more of the other units. Additionally, the units can include a wireless interface, which may include a receiver, a transmitter or transceiver (such as a RF transceiver), configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other units. [0096] In some aspects, the CU 280 may host one or more higher layer control functions. Such control functions can include RRC, PDCP, service data adaptation protocol (SDAP), or the like. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 280. The CU 280 may be configured to handle user plane functionality (i.e., Central Unit – User Plane (CU- UP)), control plane functionality (i.e., Central Unit – Control Plane (CU-CP)), or a combination thereof. In some implementations, the CU 280 can be logically split into one or more CU-UP units and one or more CU-CP units. The CU-UP unit can communicate bidirectionally with the CU-CP unit via an interface, such as the E1 interface when implemented in an O-RAN configuration. The CU 280 can be implemented to communicate with the DU 285, as necessary, for network control and signaling. [0097] The DU 285 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 287. In some aspects, the DU 285 may host one or more of a RLC layer, a MAC layer, and one or more high PHY layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, or the like) depending, at least in part, on a functional split, such as those defined by the 3rd Generation Partnership Project (3GPP®). In some aspects, the DU 285 may further host one or more low PHY layers. Each layer (or module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 285, or with the control functions hosted by the CU 280. [0098] Lower-layer functionality can be implemented by one or more RUs 287. In some deployments, an RU 287, controlled by a DU 285, may correspond to a logical node that hosts RF processing functions, or low-PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, or the like), or both, based at least in part on the functional split, such as a lower layer functional split. In such an architecture, the RU(s) 287 can be implemented to handle over the air (OTA) communication with one or more UEs 204. In some implementations, real-time and non-real-time aspects of control and user plane communication with the RU(s) 287 can be controlled by the corresponding DU 285. In some scenarios, this configuration can enable the DU(s) 285 and the CU 280 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture. [0099] The SMO Framework 255 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework 255 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements which may be managed via an operations and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO Framework 255 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 269) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements can include, but are not limited to, CUs 280, DUs 285, RUs 287 and Near-RT RICs 259. In some implementations, the SMO Framework 255 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 261, via an O1 interface. Additionally, in some implementations, the SMO Framework 255 can communicate directly with one or more RUs 287 via an O1 interface. The SMO Framework 255 also may include a Non-RT RIC 257 configured to support functionality of the SMO Framework 255. [0100] The Non-RT RIC 257 may be configured to include a logical function that enables non- real-time control and optimization of RAN elements and resources, artificial intelligence/machine learning (AI/ML) workflows including model training and updates, or policy-based guidance of applications/features in the Near-RT RIC 259. The Non-RT RIC 257 may be coupled to or communicate with (such as via an A1 interface) the Near- RT RIC 259. The Near-RT RIC 259 may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs 280, one or more DUs 285, or both, as well as an O-eNB, with the Near-RT RIC 259. [0101] In some implementations, to generate AI/ML models to be deployed in the Near-RT RIC 259, the Non-RT RIC 257 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 259 and may be received at the SMO Framework 255 or the Non-RT RIC 257 from non-network data sources or from network functions. In some examples, the Non-RT RIC 257 or the Near-RT RIC 259 may be configured to tune RAN behavior or performance. For example, the Non-RT RIC 257 may monitor long-term trends and patterns for performance and employ AI/ML models to perform corrective actions through the SMO Framework 255 (such as reconfiguration via O1) or via creation of RAN management policies (such as A1 policies). [0102] FIGS. 3A, 3B, and 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. [0103] 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 (e.g., 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. [0104] 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., Wi-Fi, LTE Direct, BLUETOOTH®, ZIGBEE®, Z-WAVE®, PC5, dedicated short-range communications (DSRC), wireless access for vehicular environments (WAVE), near-field communication (NFC), ultra- wideband (UWB), 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 Wi-Fi transceivers, BLUETOOTH® transceivers, ZIGBEE® and/or Z-WAVE® transceivers, NFC transceivers, UWB transceivers, or vehicle-to-vehicle (V2V) and/or vehicle-to- everything (V2X) transceivers. [0105] 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. [0106] 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. [0107] 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. [0108] 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. [0109] 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. [0110] 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 sidelink resource component 342, 388, and 398, respectively. The sidelink resource component 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 sidelink resource component 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 sidelink resource component 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 sidelink resource component 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 sidelink resource component 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 sidelink resource component 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. [0111] 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. [0112] 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. [0113] 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. [0114] 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. [0115] 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. [0116] In the downlink, 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. [0117] 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. [0118] 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. [0119] 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. [0120] 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. [0121] 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 personal computer (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 signal 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. [0122] 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. [0123] 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 sidelink resource component 342, 388, and 398, etc. [0124] 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 Wi-Fi). [0125] 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. [0126] 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. [0127] 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. [0128] 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. [0129] 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. [0130] 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”). [0131] A collection of resource elements (REs) that are used for transmission of PRS is referred to as a “PRS resource.” The collection of resource elements can span multiple PRBs in the frequency domain and ‘N’ (such as 1 or more) consecutive symbol(s) within a slot in the time domain. In a given OFDM symbol in the time domain, a PRS resource occupies consecutive PRBs in the frequency domain. [0132] The transmission of a PRS resource within a given PRB has a particular comb size (also referred to as the “comb density”). A comb size ‘N’ represents the subcarrier spacing (or frequency/tone spacing) within each symbol of a PRS resource configuration. Specifically, for a comb size ‘N,’ PRS are transmitted in every Nth subcarrier of a symbol of a PRB. For example, for comb-4, for each symbol of the PRS resource configuration, REs corresponding to every fourth subcarrier (such as subcarriers 0, 4, 8) are used to transmit PRS of the PRS resource. Currently, comb sizes of comb-2, comb-4, comb-6, and comb-12 are supported for DL-PRS. FIG. 4 illustrates an example PRS resource configuration for comb-4 (which spans four symbols). That is, the locations of the shaded REs (labeled “R”) indicate a comb-4 PRS resource configuration. [0133] Currently, a DL-PRS resource may span 2, 4, 6, or 12 consecutive symbols within a slot with a fully frequency-domain staggered pattern. A DL-PRS resource can be configured in any higher layer configured downlink or flexible (FL) symbol of a slot. There may be a constant energy per resource element (EPRE) for all REs of a given DL-PRS resource. The following are the frequency offsets from symbol to symbol for comb sizes 2, 4, 6, and 12 over 2, 4, 6, and 12 symbols. 2-symbol comb-2: {0, 1}; 4-symbol comb-2: {0, 1, 0, 1}; 6-symbol comb-2: {0, 1, 0, 1, 0, 1}; 12-symbol comb-2: {0, 1, 0, 1, 0, 1, 0, 1, 0, 1, 0, 1}; 4-symbol comb-4: {0, 2, 1, 3} (as in the example of FIG. 4); 12-symbol comb-4: {0, 2, 1, 3, 0, 2, 1, 3, 0, 2, 1, 3}; 6-symbol comb-6: {0, 3, 1, 4, 2, 5}; 12-symbol comb-6: {0, 3, 1, 4, 2, 5, 0, 3, 1, 4, 2, 5}; and 12-symbol comb-12: {0, 6, 3, 9, 1, 7, 4, 10, 2, 8, 5, 11}. [0134] A “PRS resource set” is a set of PRS resources used for the transmission of PRS signals, where each PRS resource has a PRS resource ID. In addition, the PRS resources in a PRS resource set are associated with the same TRP. A PRS resource set is identified by a PRS resource set ID and is associated with a particular TRP (identified by a TRP ID). In addition, the PRS resources in a PRS resource set have the same periodicity, a common muting pattern configuration, and the same repetition factor (such as “PRS- ResourceRepetitionFactor”) across slots. The periodicity is the time from the first repetition of the first PRS resource of a first PRS instance to the same first repetition of the same first PRS resource of the next PRS instance. The periodicity may have a length selected from 2^μ*{4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 160, 320, 640, 1280, 2560, 5120, 10240} slots, with μ = 0, 1, 2, 3. The repetition factor may have a length selected from {1, 2, 4, 6, 8, 16, 32} slots. [0135] A PRS resource ID in a PRS resource set is associated with a single beam (or beam ID) transmitted from a single TRP (where a TRP may transmit one or more beams). That is, each PRS resource of a PRS resource set may be transmitted on a different beam, and as such, a “PRS resource,” or simply “resource,” also can be referred to as a “beam.” Note that this does not have any implications on whether the TRPs and the beams on which PRS are transmitted are known to the UE. [0136] A “PRS instance” or “PRS occasion” is one instance of a periodically repeated time window (such as a group of one or more consecutive slots) where PRS are expected to be transmitted. A PRS occasion also may be referred to as a “PRS positioning occasion,” a “PRS positioning instance, a “positioning occasion,” “a positioning instance,” a “positioning repetition,” or simply an “occasion,” an “instance,” or a “repetition.” [0137] A “positioning frequency layer” (also referred to simply as a “frequency layer”) is a collection of one or more PRS resource sets across one or more TRPs that have the same values for certain parameters. Specifically, the collection of PRS resource sets has the same subcarrier spacing and cyclic prefix (CP) type (meaning all numerologies supported for the physical downlink shared channel (PDSCH) are also supported for PRS), the same Point A, the same value of the downlink PRS bandwidth, the same start PRB (and center frequency), and the same comb-size. The Point A parameter takes the value of the parameter “ARFCN-ValueNR” (where “ARFCN” stands for “absolute radio-frequency channel number”) and is an identifier/code that specifies a pair of physical radio channel used for transmission and reception. The downlink PRS bandwidth may have a granularity of four PRBs, with a minimum of 24 PRBs and a maximum of 272 PRBs. Currently, up to four frequency layers have been defined, and up to two PRS resource sets may be configured per TRP per frequency layer. [0138] The concept of a frequency layer is somewhat like the concept of component carriers and bandwidth parts (BWPs), but different in that component carriers and BWPs are used by one base station (or a macro cell base station and a small cell base station) to transmit data channels, while frequency layers are used by several (usually three or more) base stations to transmit PRS. A UE may indicate the number of frequency layers it can support when it sends the network its positioning capabilities, such as during an LTE positioning protocol (LPP) session. For example, a UE may indicate whether it can support one or four positioning frequency layers. [0139] Note that the terms “positioning reference signal” and “PRS” generally refer to specific reference signals that are used for positioning in NR and LTE systems. However, as used herein, the terms “positioning reference signal” and “PRS” may also refer to any type of reference signal that can be used for positioning, such as but not limited to, PRS as defined in LTE and NR, TRS, PTRS, CRS, CSI-RS, DMRS, PSS, SSS, SSB, SRS, UL-PRS, etc. In addition, the terms “positioning reference signal” and “PRS” may refer to downlink, uplink, or sidelink positioning reference signals, unless otherwise indicated by the context. If needed to further distinguish the type of PRS, a downlink positioning reference signal may be referred to as a “DL-PRS,” an uplink positioning reference signal (e.g., an SRS-for-positioning, PTRS) may be referred to as an “UL-PRS,” and a sidelink positioning reference signal may be referred to as an “SL-PRS.” In addition, for signals that may be transmitted in the downlink, uplink, and/or sidelink (e.g., DMRS), the signals may be prepended with “DL,” “UL,” or “SL” to distinguish the direction. For example, “UL-DMRS” is different from “DL-DMRS.” [0140] Sidelink communication takes place in transmission or reception resource pools. In the frequency domain, the minimum resource allocation unit is a sub-channel (e.g., a collection of consecutive PRBs in the frequency domain). In the time domain, resource allocation is in one slot intervals. However, some slots are not available for sidelink, and some slots contain feedback resources. In addition, sidelink resources can be (pre)configured to occupy fewer than the 14 symbols of a slot. [0141] Sidelink resources are configured at the radio resource control (RRC) layer. The RRC configuration can be by pre-configuration (e.g., preloaded on the UE) or configuration (e.g., from a serving base station). [0142] NR sidelinks support hybrid automatic repeat request (HARQ) retransmission. FIG. 5A is a diagram 500 of an example slot structure without feedback resources, according to aspects of the disclosure. In the example of FIG.5A, time is represented horizontally and frequency is represented vertically. In the time domain, the length of each block is one orthogonal frequency division multiplexing (OFDM) symbol, and the 14 symbols make up a slot. In the frequency domain, the height of each block is one sub-channel. Currently, the (pre)configured sub-channel size can be selected from the set of {10, 15, 20, 25, 50, 75, 100} physical resource blocks (PRBs). [0143] For a sidelink slot, the first symbol is a repetition of the preceding symbol and is used for automatic gain control (AGC) setting. This is illustrated in FIG. 5A by the vertical and horizontal hashing. As shown in FIG. 5A, for sidelink, the physical sidelink control channel (PSCCH) and the physical sidelink shared channel (PSSCH) are transmitted in the same slot. Similar to the physical downlink control channel (PDCCH), the PSCCH carries control information about sidelink resource allocation and descriptions about sidelink data transmitted to the UE. Likewise, similar to the physical downlink shared channel (PDSCH), the PSSCH carries user data for the UE. In the example of FIG.5A, the PSCCH occupies half the bandwidth of the sub-channel and only three symbols. Finally, a gap symbol is present after the PSSCH. [0144] FIG.5B is a diagram 550 of an example slot structure with feedback resources, according to aspects of the disclosure. In the example of FIG.5B, time is represented horizontally and frequency is represented vertically. In the time domain, the length of each block is one OFDM symbol, and the 14 symbols make up a slot. In the frequency domain, the height of each block is one sub-channel. [0145] The slot structure illustrated in FIG. 5B is similar to the slot structure illustrated in FIG. 5A, except that the slot structure illustrated in FIG. 5B includes feedback resources. Specifically, two symbols at the end of the slot have been dedicated to the physical sidelink feedback channel (PSFCH). The first PSFCH symbol is a repetition of the second PSFCH symbol for AGC setting. In addition to the gap symbol after the PSSCH, there is a gap symbol after the two PSFCH symbols. Currently, resources for the PSFCH can be configured with a periodicity selected from the set of {0, 1, 2, 4} slots. [0146] The physical sidelink control channel (PSCCH) carries sidelink control information (SCI). First stage SCI (referred to as “SCI-1”) is transmitted on the PSCCH and contains information for resource allocation and decoding second stage SCI (referred to as “SCI- 2”). SCI-2 is transmitted on the physical sidelink shared channel (PSSCH) and contains information for decoding the data that will be transmitted on the shared channel (SCH) of the sidelink. SCI-1 information is decodable by all UEs, whereas SCI-2 information may include formats that are only decodable by certain UEs. This ensures that new features can be introduced in SCI-2 while maintaining resource reservation backward compatibility in SCI-1. [0147] Both SCI-1 and SCI-2 use the physical downlink control channel (PDCCH) polar coding chain, illustrated in FIG. 6. FIG. 6 is a diagram 600 showing how the shared channel (SCH) is established on a sidelink between two or more UEs, according to aspects of the disclosure. Specifically, information in the SCI-1602 is used for resource allocation 604 (by the network or the involved UEs) for the SCI-2 606 and SCH 608. In addition, information in the 6CI-1602 is used to determine/decode the contents of the SCI-2606 transmitted on the allocated resources. Thus, a receiver UE needs both the resource allocation 604 and the SCI-1602 to decode the SCI-2606. Information in the SCI-2606 is then used to determine/decode the SCH 608. [0148] The first 13 symbols of a slot in the time domain and the allocated subchannel(s) in the frequency domain form a sidelink resource pool. A sidelink resource pool may include resources for sidelink communication (transmission and/or reception), sidelink positioning (referred to as a resource pool for positioning (RP-P)), or both communication and positioning. A resource pool configured for both communication and positioning is referred to as a “shared” resource pool. In a shared resource pool, the RP-P is indicated by an offset, periodicity, number of consecutive symbols within a slot (e.g., as few as one symbol), and/or the bandwidth within a component carrier (or the bandwidth across multiple component carriers). In addition, the RP-P can be associated with a zone or a distance from a reference location. [0149] A base station (or a UE, depending on the resource allocation mode) can assign, to another UE, one or more resource configurations from the RP-Ps. Additionally or alternatively, a UE (e.g., a relay or a remote UE) can request one or more RP-P configurations, and it can include in the request one or more of the following: (1) its location information (or zone identifier), (2) periodicity, (3) bandwidth, (4) offset, (5) number of symbols, and (6) whether a configuration with “low interference” is needed (which can be determined through an assigned quality of service (QoS) or priority). [0150] A base station or a UE can configure/assign rate matching resources or RP-P for rate matching and/or muting to a sidelink UE such that when a collision exists between the assigned resources and another resource pool that contains data (PSSCH) and/or control (PSCCH), the sidelink UE is expected to rate match, mute, and/or puncture the data, DMRS, and/or CSI-RS within the colliding resources. This would enable orthogonalization between positioning and data transmissions for increased coverage of PRS signals. [0151] FIG. 7 is a diagram 700 illustrating an example of a resource pool for positioning configured within a sidelink resource pool for communication (i.e., a shared resource pool), according to aspects of the disclosure. In the example of FIG.7, time is represented horizontally and frequency is represented vertically. In the time domain, the length of each block is an orthogonal frequency division multiplexing (OFDM) symbol, and the 14 symbols make up a slot. In the frequency domain, the height of each block is a sub- channel. [0152] In the example of FIG. 7, the entire slot (except for the first and last symbols) can be a resource pool for sidelink communication. That is, any of the symbols other than the first and last can be allocated for sidelink communication. However, an RP-P is allocated in the last four pre-gap symbols of the slot. As such, non-sidelink positioning data, such as user data (PSSCH), CSI-RS, and control information, can only be transmitted in the first eight post-AGC symbols and not in the last four pre-gap symbols to prevent a collision with the configured RP-P. The non-sidelink positioning data that would otherwise be transmitted in the last four pre-gap symbols can be punctured or muted, or the non- sidelink data that would normally span more than the eight post-AGC symbols can be rate matched to fit into the eight post-AGC symbols. [0153] Sidelink positioning reference signals (SL-PRS) have been defined to enable sidelink positioning procedures among UEs. Like a downlink PRS (DL-PRS), an SL-PRS resource is composed of one or more resource elements (i.e., one OFDM symbol in the time domain and one subcarrier in the frequency domain). SL-PRS resources have been designed with a comb-based pattern to enable fast Fourier transform (FFT)-based processing at the receiver. SL-PRS resources are composed of unstaggered, or only partially staggered, resource elements in the frequency domain to provide small time of arrival (TOA) uncertainty and reduced overhead of each SL-PRS resource. SL-PRS may also be associated with specific RP-Ps (e.g., certain SL-PRS may be allocated in certain RP-Ps). SL-PRS have also been defined with intra-slot repetition (not shown in FIG. 7) to allow for combining gains (if needed). There may also be inter-UE coordination of RP-Ps to provide for dynamic SL-PRS and data multiplexing while minimizing SL-PRS collisions. [0154] A UE that assists a target UE in a positioning procedure may be referred to as a “positioning peer” or “Pos-Peer” UE. Two types of Pos-Peer UE discovery procedures have been introduced for sidelink cooperative positioning, referred to as Mode A and Mode B. FIG. 8A illustrates an example call flow 800 for Mode A discovery, and FIG. 8B illustrates an example call flow 850 for Mode B discovery, according to aspects of the disclosure. The purpose of these discovery procedures is to discover which Pos-Peer UEs are in the vicinity of a target UE. In Mode A, a Pos-Peer UE may announce its presence by broadcasting a sidelink Pos-Peer discovery message with a positioning flag, as shown in FIG.8A. In Mode B, a target UE that wants to discover Pos-Peer UEs may initiate by broadcasting a sidelink Pos-Peer solicitation message with field(s) related to positioning, as shown in FIG.8B. [0155] As shown in FIGS.8A and 8B, both Pos-Peer discovery and solicitation messages can be split into two parts, labeled “A” and “B,” to enable a more power efficient approach and a handshake between the target UE and the potential Pos-Peer UEs. A target UE can rank the potential Pos-Peer UEs (also referred to as anchor UEs) according to the following criteria: (1) location quality criterion, (2) channel quality criterion, (3) response time criterion, (4) mobility state criterion, or any combination thereof. [0156] NR supports, or enables, various sidelink positioning techniques. FIG. 9A illustrates various scenarios of interest for sidelink-only or joint Uu and sidelink positioning, according to aspects of the disclosure. In scenario 910, at least one peer UE with a known location can improve the Uu-based positioning (e.g., multi-cell round-trip-time (RTT), downlink time difference of arrival (DL-TDOA), etc.) of a target UE by providing an additional anchor (e.g., using sidelink RTT (SL-RTT)). In scenario 920, a low-end (e.g., reduced capacity, or “RedCap”) target UE may obtain the assistance of premium UEs to determine its location using, e.g., sidelink positioning and ranging procedures with the premium UEs. Compared to the low-end UE, the premium UEs may have more capabilities, such as more sensors, a faster processor, more memory, more antenna elements, higher transmit power capability, access to additional frequency bands, or any combination thereof. In scenario 930, a relay UE (e.g., with a known location) participates in the positioning estimation of a remote UE without performing uplink positioning reference signal (PRS) transmission over the Uu interface. Scenario 940 illustrates the joint positioning of multiple UEs. Specifically, in scenario 940, two UEs with unknown positions can be jointly located in non-line-of-sight (NLOS) conditions by utilizing constraints from nearby UEs. [0157] FIG. 9B illustrates additional scenarios of interest for sidelink-only or joint Uu and sidelink positioning, according to aspects of the disclosure. In scenario 950, UEs used for public safety (e.g., by police, firefighters, and/or the like) may perform peer-to-peer (P2P) positioning and ranging for public safety and other uses. For example, in scenario 950, the public safety UEs may be out of coverage of a network and determine a location or a relative distance and a relative position among the public safety UEs using sidelink positioning techniques. Similarly, scenario 960 shows multiple UEs that are out of coverage and determine a location or a relative distance and a relative position using sidelink positioning techniques, such as SL-RTT. [0158] FIG. 10 illustrates the two resource allocation modes for transmissions on NR sidelinks, according to aspects of the disclosure. In the first mode 1010 (labeled “Mode 1”), the base station 1002 (e.g., any of the base stations described herein) allocates time and/or frequency resources for sidelink communication between the involved V-UEs 1004 and 1006 (e.g., any of the V-UEs or sidelink-capable UEs described herein) via DCI 3_0. Each V-UE uses the allocated resources to transmit ranging signals (e.g., SL-PRS) to the other V-UE(s). [0159] In the second mode 1020 (labeled “Mode 2”), the involved UEs 1004 and 1006 autonomously select sidelink resources to use for transmission of ranging signals. A V- UE can only use the first mode if it has cellular coverage, and can use the second mode regardless of whether or not it has cellular coverage. Note that although FIG. 10 illustrates two V-UEs, as will be appreciated, they need not be V-UEs, and may instead be any other type of UE capable of sidelink communication. In addition, there may be more than the two V-UEs 1004 and 1006 illustrated. [0160] Signaling over the sidelink is the same between the two resource allocation modes. From the point of view of the receiver (e.g., V-UE 1006), there is no difference between the modes. That is, it does not matter to the receiver whether the resources for the ranging signals were allocated by the base station 1002 or the transmitter. [0161] Mode 1 supports dynamic grant (DG), configured grant (CG) Type 1, and CG Type 2. In some cases, CG Type 1 is activated via RRC signaling from the base station 1002. In some cases, the modulation and coding scheme (MCS) for sidelink transmissions is determined by the involved V-UEs 1004 and 1006 within limits set by the base station 1002. In Mode 2, the transmitting V-UE (e.g., V-UE 1004) performs channel sensing by blindly decodes all physical sidelink control channels (PSCCHs) to determine the resources reserved for other sidelink transmissions. The transmitting V-UE 1004 reports available resources to its upper layer and the upper layer determines resource usage. [0162] In addition, NR sidelinks support hybrid automatic repeat request (HARQ) retransmission. In Mode 1, the base station 1002 provides a dynamic grant for HARQ feedback or activates a configured sidelink grant. The sidelink feedback can be reported back to the base station by the transmitting UE (e.g., V-UE 1004). [0163] In some scenarios, a UE, LCS Client or application function (AF) that is requesting the location of a target UE may know a time at which the location should be obtained. Some examples of this are as follows: x Periodic Location: With a periodic deferred 5GC-MT-LR, the location of a UE is obtained at fixed periodic intervals. Clearly, the location time is then known in advance. x IIot Location: In a factory or warehouse with moving tools, components, packages etc., there could be a precise expectation of when a moving tool, component or package etc. will reach a specific location or will have completed a specific movement or operation. It may then be useful or critical to locate the tool, component or package etc. to confirm the expectation and make any further adjustments. x Scheduled Location: The location of UEs may sometimes be scheduled to occur at specific times in the future. For example, vehicles on a road may all be located at the same time to provide an indication of traffic congestion as well as to assist with V2X. People, containers, transportation systems etc., may also be located at certain common times. [0164] In the scenarios above, the known time, referred to as a scheduled location time, can be provided in advance to reduce the effective latency in providing location results. [0165] FIG. 11 illustrates a location preparation phase 1100 of a position estimation procedure, in accordance with aspects of the disclosure. At 1110, LCS client sends a location service request to 5GC LCS entities for a position estimate of a UE at a future time T, denoted as, e.g., T = 12:34:0000Z. At 1120, the 5GC LCS entities forward the location service request to LMF. At 1130, the LMF schedules the location session such that the UE location can be obtained/valid for the requested time T. To this end, operations 0-8 depict a location preparation phase for the position estimation procedure, e.g.: x 1. The LMF may request the positioning capabilities of the target device using the LPP Capability Transfer procedure x 2. The LMF sends a NRPPa POSITIONING INFORMATION REQUEST message to the serving gNB to request UL information for the target device x 3. The serving gNB determines the resources available for UL-SRS and configures the target device with the UL-SRS resource sets at operation 3a. x 4. The serving gNB provides the UL-SRS configuration information to the LMF in a NRPPa POSITIONING INFORMATION RESPONSE message. NOTE: It is up to implementation on whether SRS configuration is provided earlier than DL-PRS configuration. • 5. In the case of semi-persistent or aperiodic SRS, the LMF may request activation of UE SRS transmission by sending a NRPPa Positioning Activation Request message to the serving gNB of the target device. The gNB then activates the UE SRS transmission and sends a NRPPa Positioning Activation Response message. The target device begins the UL-SRS transmission according to the time domain behavior of UL-SRS resource configuration.

• 6. The LMF provides the UL information to the selected gNBs in a NRPPa MEASUREMENT REQUEST message along with an indication of time T’. The message includes all information required to enable the gNBs/TRPs to perform the UL measurements.

• 7. The LMF sends a LPP Provide Assistance Data message to the target. The message includes any required assistance data for the target device to perform the necessary DL-PRS measurements.

• 8. The LMF sends a LPP Request Location Information message to request positioning measurements (e.g., TDOA, multi-RTT, AoA, etc.), along with an indication of time T’. [0166] FIG. 12 illustrates a location execution phase 1200 of the position estimation procedure of FIG.11, in accordance with aspects of the disclosure. In an example:

• 9a: The target device performs the DL-PRS measurements from all gNBs provided in the assistance data at operation 7 of FIG.11.

• 9b: Each gNB configured at operation 6 of FIG. 11 measures the UE SRS transmissions from the target device.

• 10. The target device reports the DL-PRS measurements for Multi-RTT to the LMF in a LPP Provide Location Information message, along with an indication of time T’’.

• 11. Each gNB reports the UE SRS measurements to the LMF in a NRPPa Measurement Response message, along with an indication of time T’’.

• 12. The LMF sends a NRPPa POSITIONING DEACTIVATION message to the serving gNB.

• 13. The LMF determines the RTTs from the UE and gNB Rx-Tx time difference measurements for each gNB for which corresponding UL and DL measurements were provided at operations 10 and 11 of FIG. 11 and calculates the position of the target device. [0167] At 1210, LMF sends a location service response to 5GC LCS entities, and the location service response is forwarded to the LCS client at 1220. [0168] FIG. 13 depicts timing information 1300 associated with the respective phases depicted in FIGS.11-12 in accordance with aspects of the disclosure. [0169] Referring to FIG. 13, the location service request at 1110-1120 is configured to request target device location at T = 12:34:0000Z (in the future). LMF schedules the location procedure such that the UE location can be obtained/valid for the requested time T. The positioning preparation phase starts at T-t1, where t1 depends on the expected duration of the location preparation phase, and which depends on e.g., selected positioning method, etc. AT operation 6, LMF provides a physical measurement time T’ to the TRPs and/or UE when the location measurements are to be obtained. Ultimately, t’ defines the time when the target device location is valid/obtained. T’ may specify a SFN/slot for example. T’ has a 1:1 relation to T (e.g., 1:1 relation to UTC). UE/TRPs perform the measurements such that the measurements/location is valid at time T’. [0170] The location report at operations 10-11 includes the measurements/location estimate together with the time stamp T’’, where T’’ is as close as possible to the requested time T’ i.e., ideally T’’ = T’. The location time error is į =(T’’-T’). The client receives the target device location with time stamp T=12:34:0000Z+į time T + t2 (i.e., at T=12:34:0000Z+ į +t2), where t2 is the latency and į is any error in the requested location time. The latency t2 as observed by the client excludes the location preparation phase. Any UE movement during latency t2 should have negligible impact on the validity and accuracy of the location estimate, i.e., the UE location at T is about the same as the UE location at T+ t2. [0171] In some designs, SCI format 2-C is used for the decoding of PSSCH, and providing inter- UE coordination information or requesting inter-UE coordination information. SCI format 2-C can be used only for unicast. The following information is transmitted by means of the SCI format 2-C: x HARQ process number – 4 bits x New data indicator – 1 bit x Redundancy version – 2 bits x Source ID – 8 bits x Destination ID – 16 bits • HARQ feedback enabled/disabled indicator – 1 bit

• CSI request – 1 bit

• Providing/Requesting indicator – 1 bit, where value 0 indicates SCI format 2-C is used for providing inter-UE coordination information and value 1 indicates SCI format 2-C is used for requesting inter-UE coordination information [0172] If the 'Providing/Requesting indicator' field is set to 0, all the remaining fields are set as follows

• Resource Combinations

bits, as defined in clause 8.1.5 of [6, TS 38.214], where:

• and is the number of entries in the higher layer

parameter sl-ResourceReservePeriodList, if higher layer parameter sl- MultiReserveResource is configured; ^=0 otherwise

• N subChannel SL is the number of subchannels in a resource pool provided by the higher layer parameter sl-NumSubchannel

• First resource location – 8 bits

• Reference slot location

• Resource set type – 1 bit, where value 0 indicates preferred resource set and value 1 indicates non-preferred resource set.

• Lowest subChannel indices –

bits [0173] In some designs, the SL-ResourceReservePeriod is configured as follows: SL-UE-SelectedConfigRP-r16 ::= SEQUENCE { sl-CBR-PriorityTxConfigList-r16 SL-CBR-PriorityTxConfigList-r16 OPTIONAL, -- Need M sl-Thres-RSRP-List-r16 SL-Thres-RSRP-List-r16 OPTIONAL, -- Need M sl-MultiReserveResource-r16 ENUMERATED {enabled} OPTIONAL, -- Need M sl-MaxNumPerReserve-r16 ENUMERATED {n2, n3} OPTIONAL, -- Need M sl-SensingWindow-r16 ENUMERATED {ms100, ms1100} OPTIONAL, -- Need M sl-SelectionWindowList-r16 SL-SelectionWindowList-r16 OPTIONAL, -- Need M sl-ResourceReservePeriodList-r16 SEQUENCE (SIZE (1..16)) OF SL- ResourceReservePeriod-r16 OPTIONAL, -- Need M sl-RS-ForSensing-r16 ENUMERATED {pscch, pssch}, ..., [[ sl-CBR-PriorityTxConfigList-v1650 SL-CBR-PriorityTxConfigList-v1650 OPTIONAL -- Need M ]] } SL-ResourceReservePeriod-r16 ::= CHOICE { sl-ResourceReservePeriod1-r16 ENUMERATED {ms0, ms100, ms200, ms300, ms400, ms500, ms600, ms700, ms800, ms900, ms1000}, sl-ResourceReservePeriod2-r16 INTEGER (1..99) } [0174] In some designs, sl-ResourceReservePeriodList configures a set of possible resource reservation periods allowed in the resource pool in the unit of ms. Up to 16 values can be configured per resource pool. The value ms0 is always configured. [0175] Scheduled location is used when the location of UEs is desired at specific times in the future. For example, vehicles on a road may all be located at the same time to provide an indication of traffic congestion as well as to assist with V2X. People, containers, transportation systems etc., may also be located at certain common times. Scheduled positioning sessions are known in Uu framework. However, scheduling of sidelink resources for scheduled position estimation sessions is limited. [0176] Aspects of the disclosure are directed to an aperiodic sidelink resource reservation request that requests reservation of a set of time-frequency resources associated with a future time that is offset relative to a time reference, or alternatively requests reservation of a set of time-frequency resources at a future absolute time. Such aspects may provide various technical advantages, such as flexibly supporting scheduled position estimation for sidelink-based position estimation sessions (e.g., which may facilitate location tracking that satisfies various application requirements for V2X, inventory tracking systems, and so on). [0177] FIG.14 illustrates an exemplary process 1400 of communications according to an aspect of the disclosure. The process 1400 of FIG. 14 is performed by a first UE, such as UE 302. [0178] Referring to FIG.14, at 1410, the first UE (e.g., transmitter 314 or 324, etc.) transmits an aperiodic sidelink resource reservation request of a first type to a second UE. In an aspect, the aperiodic sidelink resource reservation request requests reservation of a set of time- frequency resources associated with a future time that is offset relative to a time reference. In a further aspect, aperiodic sidelink resource reservation requests of the first type are associated with a first set of relative timing offset options and aperiodic sidelink resource reservation requests of a second type are associated with a second set of relative timing offset options that is different than the first set of relative timing offset options. [0179] Referring to FIG. 14, at 1420, the first UE (e.g., transmitter 314 or 324, receiver 312 or 322, etc.) communicates with the second UE on the set of time-frequency resources in accordance with the aperiodic sidelink resource reservation request. [0180] FIG.15 illustrates an exemplary process 1500 of communications according to an aspect of the disclosure. The process 1500 of FIG.15 is performed by a second UE, such as UE 302. [0181] Referring to FIG. 15, at 1510, the second UE (e.g., receiver 312 or 322, etc.) receives an aperiodic sidelink resource reservation request of a first type from a first UE. In an aspect, the aperiodic sidelink resource reservation request requests reservation of a set of time- frequency resources associated with a future time that is offset relative to a time reference. In a further aspect, aperiodic sidelink resource reservation requests of the first type are associated with a first set of relative timing offset options and aperiodic sidelink resource reservation requests of a second type are associated with a second set of relative timing offset options that is different than the first set of relative timing offset options. [0182] Referring to FIG. 15, at 1520, the second UE (e.g., transmitter 314 or 324, receiver 312 or 322, etc.) communicates with the first UE on the set of time-frequency resources in accordance with the aperiodic sidelink resource reservation request. [0183] Referring to FIGS.14-15, in some designs, the second set of relative timing offset options is a subset of the first set of relative timing offset options, or the first set of relative timing offset options is associated with a first information element (IE) and the second set of relative timing offset options is associated with a second IE, or the first set of relative timing offset options is defined in units of milliseconds or seconds or hours or days, or any combination thereof. [0184] Referring to FIGS. 14-15, in some designs, the aperiodic sidelink resource reservation request of the first type is associated with a sidelink-based position estimation session of the first UE, the second UE, or both. In an aspect, the sidelink-based position estimation session comprises a location preparation phase and two or more location execution phases (e.g., a single instance of FIG.11 followed by multiple instances of FIG.12). [0185] Referring to FIGS.14-15, in some designs, a maximum timing offset associated with the first set of relative timing offset options is based on a subframe number (SFN)-based timing duration. In some designs, the SFN-based timing duration corresponds to a subframe duration, or a hyper frame duration. [0186] Referring to FIGS. 14-15, in some designs, the time reference corresponds to a current time, or a subframe number (SFN)-based timing index. [0187] Referring to FIGS. 14-15, in some designs, the aperiodic sidelink resource reservation request of the first type is transmitted by the first UE (and received by the second UE) via medium access control command element (MAC-CE) or via both MAC-CE and sidelink control information (SCI). [0188] Referring to FIGS. 14-15, in some designs, the first UE further receives (and the second UE further transmits) resource availability information associated with the second UE, resource conflict information associated with the second UE, or both. In an aspect, the set of time-frequency resources is selected based on the resource availability information, the resource conflict information, or both. [0189] Referring to FIGS.14-15, in some designs, the communicating at 1420 or 1520 comprises a transmission operation, a reception operation, or both. [0190] Referring to FIGS. 14-15, in a specific example, assume that the second set of relative timing offset options includes sl-ResourceReservePeriod1-r16 ENUMERATED {ms0, ms100, ms200, ms300, ms400, ms500, ms600, ms700, ms800, ms900, ms1000}. In this case, in an example, these relative timing offset options may be expanded in the first set of relative timing options, e.g., sl-ResourceReservePeriod1- r16 ENUMERATED {ms0, ms100, ms200, ms300, ms400, ms500, ms600, ms700, ms800, ms900, ms1000, ms2000, ms4000, ms8000, ms16000}. [0191] Referring to FIGS.14-15, in a specific example, a new IE may be defined for the first set of relative timing offset options, e.g., sl-ResourceReservePeriodHour- r18 INTEGER (1..99), or sl-ResourceReservePeriodmilisecond- r18 INTEGER (1..3600*1000). [0192] Referring to FIGS. 14-15, in a specific example, assume that SFN rolls over after 1024 subframes, such that the maximum time span of an SFN cycle is around 10.24 seconds. In an aspect, with SFN time, SL UE need to make sure advance positioning session with in 10.24 second. For example, the maximum timing offset may an SFN-based timing index such as 10.24 seconds (e.g., UE can schedule advance positioning session with max advance time 10.24 seconds only). In another example, the maximum timing offset may an SFN-based timing index such as 2.84 hours (e.g., hyper frame duration or hyper frame number (HFN)-based). In this case, UE can schedule advance positioning session with max advance time 2.84 hours only. [0193] Referring to FIGS.14-15, in a specific example, a client may tolerate some deviation with respect to time T. In an aspect, LMF/Anchor may define tolerance level in terms of msec with respect to some SFN (e.g., X msec with respect to SFN0). [0194] FIG.16 illustrates an exemplary process 1600 of communications according to an aspect of the disclosure. The process 1600 of FIG. 16 is performed by a first UE, such as UE 302. [0195] Referring to FIG.16, at 1610, the first UE (e.g., transmitter 314 or 324, etc.) transmits an aperiodic sidelink resource reservation request to a second UE that requests reservation of a set of time-frequency resources at a future absolute time. [0196] Referring to FIG. 16, at 1620, the first UE (e.g., transmitter 314 or 324, receiver 312 or 322, etc.) communicates with the second UE on the set of time-frequency resources in accordance with the aperiodic sidelink resource reservation request. [0197] FIG.17 illustrates an exemplary process 1700 of communications according to an aspect of the disclosure. The process 1700 of FIG.17 is performed by a second UE, such as UE 302. [0198] Referring to FIG. 17, at 1710, the second UE (e.g., receiver 312 or 322, etc.) receives an aperiodic sidelink resource reservation request to a second UE that requests reservation of a set of time-frequency resources at a future absolute time. [0199] Referring to FIG. 17, at 1720, the second UE (e.g., transmitter 314 or 324, receiver 312 or 322, etc.) communicates with the first UE on the set of time-frequency resources in accordance with the aperiodic sidelink resource reservation request. [0200] Referring to FIGS. 16-17, in some designs, the future absolute time is defined via coordinated universal time (UTC). For example, there will be cases SL UE and gNB will have UTC time available. In this case, as an example, both SL UE and gNB can notify this to LMF, which may facilitate advanced scheduling of sidelink position estimation on the order of days or longer. [0201] Referring to FIGS. 16-17, in some designs, the aperiodic sidelink resource reservation request is associated with a sidelink-based position estimation session of the first UE, the second UE, or both. [0202] Referring to FIGS. 16-17, in some designs, the aperiodic sidelink resource reservation request of the first type is transmitted by the first UE (and received by the second UE) via medium access control command element (MAC-CE) or via both MAC-CE and sidelink control information (SCI). [0203] FIG. 18 illustrates an example implementation 1800 of any of the processes 1400-1700 of FIGS. 14-17, respectively, in accordance with aspects of the disclosure. At (1), UE-B transmits a request for preferred resources (or to avoid the use of non-preferred resources) to UE-A. At (2), UE-A transmits inter-UE coordination (IUC) signal (i.e., an aperiodic sidelink resource reservation request) to UE-B. At (3), UE-B performs a sidelink transmission (e.g., targeting UE-A and/or other sidelink UEs) on resource(s) selected based on the IUC signal. In some designs, in a resource avoidance IUC scheme, a UE includes which resources are non-preferred to be used by someone else; in this case, it will include the resources that the UE has been scheduled in advanced (e.g., IUC may convey to the other UEs in the vicinity that these specific resources should not be scheduled by someone else). In some designs, in a collision notification IUC scheme, a UE indicates that a collision exists between a resource that was reserved by another UE and the UE's schedule-in-advanced reservation. [0204] FIG. 19 illustrates an example implementation 1900 of any of the processes 1400-1700 of FIGS. 14-17, respectively, in accordance with aspects of the disclosure. At (1), UE-A detects a triggering condition for reserving resources. At (2), UE-A transmits inter-UE coordination (IUC) signal (i.e., an aperiodic sidelink resource reservation request) to UE- B. At (3), UE-B performs a sidelink transmission (e.g., targeting UE-A and/or other sidelink UEs) on resource(s) selected based on the IUC signal. In an aspect, the IUC signal may be configured as a 1-bit indication that indicates whether a specific resource will be a collision, in case of a collision notification IUC scheme. In a further aspect, the IUC signal be configured as a 1-bit indication that indicates a collection of preferred and/or non-preferred resources. [0205] In some designs, the IUC signaling is piggybacked onto other data sent by UE-A. In some designs, the IUC signaling is transmitted via MAC-CE, or both MAC-CE and SCI-2C (e.g., reception of SCI-2C is optional feature and its transmission is up to UE implementation in some designs; in some designs, SCI-2C is limited to unicast). [0206] FIG. 20 illustrates an example implementation 2000 of any of the processes 1400-1700 of FIGS. 14-17, respectively, in accordance with aspects of the disclosure. At (1), UE-A transmits a resource preference to UE-B. At (2), UE-B selects resources for sidelink transmission based on the resource preference (e.g., so, if UE-B attempts to reserve resources, UE-B is biased towards selecting a preferred resource). At (3), UE-B and/or UE-A perform sidelink transmission on the preferred resource. [0207] FIG. 21 illustrates an example implementation 2000 of any of the processes 1400-1700 of FIGS. 14-17, respectively, in accordance with aspects of the disclosure. At (1), UE-A and UE-B perform sidelink transmission and UE-B attempts to reserve a resource. At (2), UE-B indicates that there is a conflict with the resource that UE-B is attempting to reserve. At (3), UE-B performs resource re-selection (e.g., so, if UE-B attempts another resource reservation, UE-B will reserve the reselected resource instead of the conflicted resource). At (4), UE-B and/or UE-A perform sidelink transmission on the reselected resource. [0208] Referring to FIGS. 14-17, in a specific example, a SL UE may receive a scheduled in advanced reservation of SL resources. In an aspect, SL UE includes in the process of FIG. 18 or FIG. 19 non-preferred (or conflicted) resources, the resources it has received as “scheduled in advanced” (e.g., to avoid other UEs attempting to use those resources, i.e., to keep the reservation). [0209] Referring to FIGS. 14-17, in a specific example, if any other nearby SL UE use same resources in the future, the SL UE may use the procedure of FIG.21 to provide A collision indicator on the collided resource set A. In this case, the other SL UE shall remove/avoid the transmission/reception on the collided resource set A. [0210] Referring to FIGS.14-17, in a specific example, assume that a first UE determines a UE for providing the conflict information to in a PSFCH as follows • if, for a resource pool, sl-TypeUE-A is not provided, the first UE has been indicated a first reserved resource and a second reserved resource as resources for PSSCH reception or, if for a resource pool sl-TypeUE-A is provided, has been indicated at least the first reserved resource or the second reserved resource for PSSCH reception,

• detects a first SCI format 1-A that includes a first priority value, ^_^, and the first reserved resource for PSSCH transmission from a second UE,

• detects a second SCI format 1-A that includes a second priority value, ^_ଶ ^ ^_^, and the second reserved resource for PSSCH transmission from a third UE, and

• determines that the first and second resources overlap in time and frequency

• the PSFCH occasions for resource conflict information of the second UE and the third UE are valid

• the conflict information receiver flag in SCI Format 1-A from the second UE and the third UE is set to 1, if sl-IndicationUE-B = 'enabled'

• determines the first SCI format 1-A and the second SCI format 1-A are not received later than sl-MinTimeGapPSFCH before the PSFCH occasion for conflict information

• determines to transmit to the second UE the PSFCH with the conflict information

• determines to transmit to either the second UE or the third UE the PSFCH with the conflict information, if ^_ଶ ൌ ^_^ [0211] In an aspect, a UE may include conflict indication if it detects:

• A first SCI format 1-A reserving first reserved resource for transmission of SL-PRS from a second UE

• and

• A scheduled in advanced indication (MAC-CE, or higher layer (SLPP)) that indicates the same reserved resource for transmission of SL-PRS from a third UE. [0212] In a further aspect, a UE may include conflict indication if it detects:

• A scheduled in advanced indication (MAC-CE, or higher layer (SLPP)) that indicates a first reserved resource for transmission of SL-PRS from a second UE

• and

• A scheduled in advanced indication (MAC-CE, or higher layer (SLPP)) that indicates the same reserved resource for transmission of SL-PRS from a third UE. • Then a conflict indication may be sent [0213] Referring to FIGS.14-17, in a specific example, a single position estimation session may include a single^Location Execution Phase and a single Location Preparation Phase. In an aspect, Location Preparation Phase include resource sensing and selection. This configuration is suitable for latency use case, but may not be optimal from a signaling and power perspective. In an aspect, multiple Location Execution Phases may be performed for a given Location Preparation Phase, e.g.:

• Location Preparation Phase (T- t1)

• Location Execution Phase (T)

• Location Execution Phase (T1)

• Location Execution Phase (T2)…etc. [0214] In this case, both SL UE and LMF may support multiple location execution phases per location preparation phase. [0215] 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. [0216] Implementation examples are described in the following numbered clauses: [0217] Clause 1. A method of operating a first user equipment (UE), comprising: transmitting an aperiodic sidelink resource reservation request of a first type to a second UE, wherein the aperiodic sidelink resource reservation request requests reservation of a set of time- frequency resources associated with a future time that is offset relative to a time reference, and wherein aperiodic sidelink resource reservation requests of the first type are associated with a first set of relative timing offset options and aperiodic sidelink resource reservation requests of a second type are associated with a second set of relative timing offset options that is different than the first set of relative timing offset options; and communicating with the second UE on the set of time-frequency resources in accordance with the aperiodic sidelink resource reservation request. [0218] Clause 2. The method of clause 1, wherein the second set of relative timing offset options is a subset of the first set of relative timing offset options, or wherein the first set of relative timing offset options is associated with a first information element (IE) and the second set of relative timing offset options is associated with a second IE, or wherein the first set of relative timing offset options is defined in units of milliseconds or seconds or hours or days, or any combination thereof. [0219] Clause 3. The method of any of clauses 1 to 2, wherein the aperiodic sidelink resource reservation request of the first type is associated with a sidelink-based position estimation session of the first UE, the second UE, or both. [0220] Clause 4. The method of clause 3, wherein the sidelink-based position estimation session comprises a location preparation phase and two or more location execution phases. [0221] Clause 5. The method of any of clauses 1 to 4, wherein a maximum timing offset associated with the first set of relative timing offset options is based on a subframe number (SFN)-based timing duration. [0222] Clause 6. The method of clause 5, wherein the SFN-based timing duration corresponds to a subframe duration, or a hyper frame duration. [0223] Clause 7. The method of any of clauses 1 to 6, wherein the time reference corresponds to a current time, or a subframe number (SFN)-based timing index. [0224] Clause 8. The method of any of clauses 1 to 7, wherein the aperiodic sidelink resource reservation request of the first type is transmitted via medium access control command element (MAC-CE) or via both MAC-CE and sidelink control information (SCI). [0225] Clause 9. The method of any of clauses 1 to 8, further comprising: receiving resource availability information associated with the second UE, resource conflict information associated with the second UE, or both, wherein the set of time-frequency resources is selected based on the resource availability information, the resource conflict information, or both. [0226] Clause 10. The method of any of clauses 1 to 9, wherein the communicating comprises a transmission operation, a reception operation, or both. [0227] Clause 11. A method of operating a second user equipment (UE), comprising: receiving an aperiodic sidelink resource reservation request of a first type from a first UE, wherein the aperiodic sidelink resource reservation request requests reservation of a set of time- frequency resources at a future time that is offset relative to a time reference, and wherein aperiodic sidelink resource reservation requests of the first type are associated with a first set of relative timing offset options and aperiodic sidelink resource reservation requests of a second type are associated with a second set of relative timing offset options that is different than the first set of relative timing offset options; and communicating with the first UE on the set of time-frequency resources in accordance with the aperiodic sidelink resource reservation request. [0228] Clause 12. The method of clause 11, further comprising: transmitting an indication of the reservation of the set of time-frequency resources to one or more other UEs, or transmitting an indication that the set of time-frequency resources is non-preferred to the one or more other UEs. [0229] Clause 13. The method of any of clauses 11 to 12, wherein the second set of relative timing offset options is a subset of the first set of relative timing offset options, or wherein the first set of relative timing offset options is associated with a first information element (IE) and the second set of relative timing offset options is associated with a second IE, or wherein the first set of relative timing offset options is defined in units of milliseconds or seconds or hours or days, or any combination thereof. [0230] Clause 14. The method of any of clauses 11 to 13, wherein the aperiodic sidelink resource reservation request of the first type is associated with a sidelink-based position estimation session of the first UE, the second UE, or both. [0231] Clause 15. The method of clause 14, wherein the sidelink-based position estimation session comprises a location preparation phase and two or more location execution phases. [0232] Clause 16. The method of any of clauses 11 to 15, wherein a maximum timing offset associated with the first set of relative timing offset options is based on a subframe number (SFN)-based timing duration. [0233] Clause 17. The method of clause 16, wherein the SFN-based timing duration corresponds to a subframe duration, or a hyper frame duration. [0234] Clause 18. The method of any of clauses 11 to 17, wherein the time reference corresponds to a current time, or a subframe number (SFN)-based timing index. [0235] Clause 19. The method of any of clauses 11 to 18, wherein the aperiodic sidelink resource reservation request of the first type is received via medium access control command element (MAC-CE) or via both MAC-CE and sidelink control information (SCI). [0236] Clause 20. The method of any of clauses 11 to 19, further comprising: transmitting resource availability information associated with the second UE, resource conflict information associated with the second UE, or both, wherein the set of time-frequency resources is based on the resource availability information, the resource conflict information, or both. [0237] Clause 21. The method of any of clauses 11 to 20, wherein the communicating comprises a transmission operation, a reception operation, or both. [0238] Clause 22. A method of operating a first user equipment (UE), comprising: transmitting an aperiodic sidelink resource reservation request to a second UE that requests reservation of a set of time-frequency resources at a future absolute time; and communicating with the second UE on the set of time-frequency resources in accordance with the aperiodic sidelink resource reservation request. [0239] Clause 23. The method of clause 22, wherein the future absolute time is defined via coordinated universal time (UTC). [0240] Clause 24. The method of any of clauses 22 to 23, wherein the aperiodic sidelink resource reservation request is associated with a sidelink-based position estimation session of the first UE, the second UE, or both. [0241] Clause 25. The method of any of clauses 22 to 24, wherein the aperiodic sidelink resource reservation request is transmitted via medium access control command element (MAC- CE) or via both MAC-CE and sidelink control information (SCI). [0242] Clause 26. A method of operating a second user equipment (UE), comprising: receiving an aperiodic sidelink resource reservation request from a first UE that requests reservation of a set of time-frequency resources at a future absolute time; and communicating with the first UE on the set of time-frequency resources in accordance with the aperiodic sidelink resource reservation request. [0243] Clause 27. The method of clause 26, wherein the future absolute time is defined via coordinated universal time (UTC). [0244] Clause 28. The method of any of clauses 26 to 27, wherein the aperiodic sidelink resource reservation request is associated with a sidelink-based position estimation session of the first UE, the second UE, or both. [0245] Clause 29. The method of any of clauses 26 to 28, further comprising: transmitting an indication of the reservation of the set of time-frequency resources to one or more other UEs, or transmitting an indication that the set of time-frequency resources is non- preferred to the one or more other UEs. [0246] Clause 30. The method of any of clauses 26 to 29, wherein the aperiodic sidelink resource reservation request of the first type is received via medium access control command element (MAC-CE) or via both MAC-CE and sidelink control information (SCI). [0247] Clause 31. A first user equipment (UE), comprising: one or more memories; and one or more processors communicatively coupled to the one or more memories, the one or more processors, either alone or in combination, configured to: transmit an aperiodic sidelink resource reservation request of a first type to a second UE, wherein the aperiodic sidelink resource reservation request requests reservation of a set of time-frequency resources associated with a future time that is offset relative to a time reference, and wherein aperiodic sidelink resource reservation requests of the first type are associated with a first set of relative timing offset options and aperiodic sidelink resource reservation requests of a second type are associated with a second set of relative timing offset options that is different than the first set of relative timing offset options; and communicate with the second UE on the set of time-frequency resources in accordance with the aperiodic sidelink resource reservation request. [0248] Clause 32. The UE of clause 31, wherein the second set of relative timing offset options is a subset of the first set of relative timing offset options, or wherein the first set of relative timing offset options is associated with a first information element (IE) and the second set of relative timing offset options is associated with a second IE, or wherein the first set of relative timing offset options is defined in units of milliseconds or seconds or hours or days, or any combination thereof. [0249] Clause 33. The UE of any of clauses 31 to 32, wherein the aperiodic sidelink resource reservation request of the first type is associated with a sidelink-based position estimation session of the first UE, the second UE, or both. [0250] Clause 34. The UE of clause 33, wherein the sidelink-based position estimation session comprises a location preparation phase and two or more location execution phases. [0251] Clause 35. The UE of any of clauses 31 to 34, wherein a maximum timing offset associated with the first set of relative timing offset options is based on a subframe number (SFN)-based timing duration. [0252] Clause 36. The UE of clause 35, wherein the SFN-based timing duration corresponds to a subframe duration, or a hyper frame duration. [0253] Clause 37. The UE of any of clauses 31 to 36, wherein the time reference corresponds to a current time, or a subframe number (SFN)-based timing index. [0254] Clause 38. The UE of any of clauses 31 to 37, wherein the aperiodic sidelink resource reservation request of the first type is transmitted via medium access control command element (MAC-CE) or via both MAC-CE and sidelink control information (SCI). [0255] Clause 39. The UE of any of clauses 31 to 38, wherein the one or more processors, either alone or in combination, are further configured to: receive resource availability information associated with the second UE, resource conflict information associated with the second UE, or both, wherein the set of time-frequency resources is selected based on the resource availability information, the resource conflict information, or both. [0256] Clause 40. The UE of any of clauses 31 to 39, wherein the communicating comprises a transmission operation, a reception operation, or both. [0257] Clause 41. A second user equipment (UE), comprising: one or more memories; and one or more processors communicatively coupled to the one or more memories, the one or more processors, either alone or in combination, configured to: receive an aperiodic sidelink resource reservation request of a first type from a first UE, wherein the aperiodic sidelink resource reservation request requests reservation of a set of time-frequency resources at a future time that is offset relative to a time reference, and wherein aperiodic sidelink resource reservation requests of the first type are associated with a first set of relative timing offset options and aperiodic sidelink resource reservation requests of a second type are associated with a second set of relative timing offset options that is different than the first set of relative timing offset options; and communicate with the first UE on the set of time-frequency resources in accordance with the aperiodic sidelink resource reservation request. [0258] Clause 42. The UE of clause 41, wherein the one or more processors, either alone or in combination, are further configured to: transmit an indication of the reservation of the set of time-frequency resources to one or more other UEs, or transmit an indication that the set of time-frequency resources is non-preferred to the one or more other UEs. [0259] Clause 43. The UE of any of clauses 41 to 42, wherein the second set of relative timing offset options is a subset of the first set of relative timing offset options, or wherein the first set of relative timing offset options is associated with a first information element (IE) and the second set of relative timing offset options is associated with a second IE, or wherein the first set of relative timing offset options is defined in units of milliseconds or seconds or hours or days, or any combination thereof. [0260] Clause 44. The UE of any of clauses 41 to 43, wherein the aperiodic sidelink resource reservation request of the first type is associated with a sidelink-based position estimation session of the first UE, the second UE, or both. [0261] Clause 45. The UE of clause 44, wherein the sidelink-based position estimation session comprises a location preparation phase and two or more location execution phases. [0262] Clause 46. The UE of any of clauses 41 to 45, wherein a maximum timing offset associated with the first set of relative timing offset options is based on a subframe number (SFN)-based timing duration. [0263] Clause 47. The UE of clause 46, wherein the SFN-based timing duration corresponds to a subframe duration, or a hyper frame duration. [0264] Clause 48. The UE of any of clauses 41 to 47, wherein the time reference corresponds to a current time, or a subframe number (SFN)-based timing index. [0265] Clause 49. The UE of any of clauses 41 to 48, wherein the aperiodic sidelink resource reservation request of the first type is received via medium access control command element (MAC-CE) or via both MAC-CE and sidelink control information (SCI). [0266] Clause 50. The UE of any of clauses 41 to 49, wherein the one or more processors, either alone or in combination, are further configured to: transmit resource availability information associated with the second UE, resource conflict information associated with the second UE, or both, wherein the set of time-frequency resources is based on the resource availability information, the resource conflict information, or both. [0267] Clause 51. The UE of any of clauses 41 to 50, wherein the communicating comprises a transmission operation, a reception operation, or both. [0268] Clause 52. A user equipment (UE), comprising: one or more memories; and one or more processors communicatively coupled to the one or more memories, the one or more processors, either alone or in combination, configured to: transmit an aperiodic sidelink resource reservation request to a second UE that requests reservation of a set of time- frequency resources at a future absolute time; and communicate with the second UE on the set of time-frequency resources in accordance with the aperiodic sidelink resource reservation request. [0269] Clause 53. The UE of clause 52, wherein the future absolute time is defined via coordinated universal time (UTC). [0270] Clause 54. The UE of any of clauses 52 to 53, wherein the aperiodic sidelink resource reservation request is associated with a sidelink-based position estimation session of the first UE, the second UE, or both. [0271] Clause 55. The UE of any of clauses 52 to 54, wherein the aperiodic sidelink resource reservation request is transmitted via medium access control command element (MAC- CE) or via both MAC-CE and sidelink control information (SCI). [0272] Clause 56. A user equipment (UE), comprising: one or more memories; and one or more processors communicatively coupled to the one or more memories, the one or more processors, either alone or in combination, configured to: receive an aperiodic sidelink resource reservation request from a first UE that requests reservation of a set of time- frequency resources at a future absolute time; and communicate with the first UE on the set of time-frequency resources in accordance with the aperiodic sidelink resource reservation request. [0273] Clause 57. The UE of clause 56, wherein the future absolute time is defined via coordinated universal time (UTC). [0274] Clause 58. The UE of any of clauses 56 to 57, wherein the aperiodic sidelink resource reservation request is associated with a sidelink-based position estimation session of the first UE, the second UE, or both. [0275] Clause 59. The UE of any of clauses 56 to 58, wherein the one or more processors, either alone or in combination, are further configured to: transmit an indication of the reservation of the set of time-frequency resources to one or more other UEs, or transmit an indication that the set of time-frequency resources is non-preferred to the one or more other UEs. [0276] Clause 60. The UE of any of clauses 56 to 59, wherein the aperiodic sidelink resource reservation request of the first type is received via medium access control command element (MAC-CE) or via both MAC-CE and sidelink control information (SCI). [0277] Clause 61. A first user equipment (UE), comprising: means for transmitting an aperiodic sidelink resource reservation request of a first type to a second UE, wherein the aperiodic sidelink resource reservation request requests reservation of a set of time-frequency resources associated with a future time that is offset relative to a time reference, and wherein aperiodic sidelink resource reservation requests of the first type are associated with a first set of relative timing offset options and aperiodic sidelink resource reservation requests of a second type are associated with a second set of relative timing offset options that is different than the first set of relative timing offset options; and means for communicating with the second UE on the set of time-frequency resources in accordance with the aperiodic sidelink resource reservation request. [0278] Clause 62. The UE of clause 61, wherein the second set of relative timing offset options is a subset of the first set of relative timing offset options, or wherein the first set of relative timing offset options is associated with a first information element (IE) and the second set of relative timing offset options is associated with a second IE, or wherein the first set of relative timing offset options is defined in units of milliseconds or seconds or hours or days, or any combination thereof. [0279] Clause 63. The UE of any of clauses 61 to 62, wherein the aperiodic sidelink resource reservation request of the first type is associated with a sidelink-based position estimation session of the first UE, the second UE, or both. [0280] Clause 64. The UE of clause 63, wherein the sidelink-based position estimation session comprises a location preparation phase and two or more location execution phases. [0281] Clause 65. The UE of any of clauses 61 to 64, wherein a maximum timing offset associated with the first set of relative timing offset options is based on a subframe number (SFN)-based timing duration. [0282] Clause 66. The UE of clause 65, wherein the SFN-based timing duration corresponds to a subframe duration, or a hyper frame duration. [0283] Clause 67. The UE of any of clauses 61 to 66, wherein the time reference corresponds to a current time, or a subframe number (SFN)-based timing index. [0284] Clause 68. The UE of any of clauses 61 to 67, wherein the aperiodic sidelink resource reservation request of the first type is transmitted via medium access control command element (MAC-CE) or via both MAC-CE and sidelink control information (SCI). [0285] Clause 69. The UE of any of clauses 61 to 68, further comprising: means for receiving resource availability information associated with the second UE, resource conflict information associated with the second UE, or both, wherein the set of time-frequency resources is selected based on the resource availability information, the resource conflict information, or both. [0286] Clause 70. The UE of any of clauses 61 to 69, wherein the communicating comprises a transmission operation, a reception operation, or both. [0287] Clause 71. A second user equipment (UE), comprising: means for receiving an aperiodic sidelink resource reservation request of a first type from a first UE, wherein the aperiodic sidelink resource reservation request requests reservation of a set of time-frequency resources at a future time that is offset relative to a time reference, and wherein aperiodic sidelink resource reservation requests of the first type are associated with a first set of relative timing offset options and aperiodic sidelink resource reservation requests of a second type are associated with a second set of relative timing offset options that is different than the first set of relative timing offset options; and means for communicating with the first UE on the set of time-frequency resources in accordance with the aperiodic sidelink resource reservation request. [0288] Clause 72. The UE of clause 71, further comprising: means for transmitting an indication of the reservation of the set of time-frequency resources to one or more other UEs, or means for transmitting an indication that the set of time-frequency resources is non- preferred to the one or more other UEs. [0289] Clause 73. The UE of any of clauses 71 to 72, wherein the second set of relative timing offset options is a subset of the first set of relative timing offset options, or wherein the first set of relative timing offset options is associated with a first information element (IE) and the second set of relative timing offset options is associated with a second IE, or wherein the first set of relative timing offset options is defined in units of milliseconds or seconds or hours or days, or any combination thereof. [0290] Clause 74. The UE of any of clauses 71 to 73, wherein the aperiodic sidelink resource reservation request of the first type is associated with a sidelink-based position estimation session of the first UE, the second UE, or both. [0291] Clause 75. The UE of clause 74, wherein the sidelink-based position estimation session comprises a location preparation phase and two or more location execution phases. [0292] Clause 76. The UE of any of clauses 71 to 75, wherein a maximum timing offset associated with the first set of relative timing offset options is based on a subframe number (SFN)-based timing duration. [0293] Clause 77. The UE of clause 76, wherein the SFN-based timing duration corresponds to a subframe duration, or a hyper frame duration. [0294] Clause 78. The UE of any of clauses 71 to 77, wherein the time reference corresponds to a current time, or a subframe number (SFN)-based timing index. [0295] Clause 79. The UE of any of clauses 71 to 78, wherein the aperiodic sidelink resource reservation request of the first type is received via medium access control command element (MAC-CE) or via both MAC-CE and sidelink control information (SCI). [0296] Clause 80. The UE of any of clauses 71 to 79, further comprising: means for transmitting resource availability information associated with the second UE, resource conflict information associated with the second UE, or both, wherein the set of time-frequency resources is based on the resource availability information, the resource conflict information, or both. [0297] Clause 81. The UE of any of clauses 71 to 80, wherein the communicating comprises a transmission operation, a reception operation, or both. [0298] Clause 82. A user equipment (UE), comprising: means for transmitting an aperiodic sidelink resource reservation request to a second UE that requests reservation of a set of time-frequency resources at a future absolute time; and means for communicating with the second UE on the set of time-frequency resources in accordance with the aperiodic sidelink resource reservation request. [0299] Clause 83. The UE of clause 82, wherein the future absolute time is defined via coordinated universal time (UTC). [0300] Clause 84. The UE of any of clauses 82 to 83, wherein the aperiodic sidelink resource reservation request is associated with a sidelink-based position estimation session of the first UE, the second UE, or both. [0301] Clause 85. The UE of any of clauses 82 to 84, wherein the aperiodic sidelink resource reservation request is transmitted via medium access control command element (MAC- CE) or via both MAC-CE and sidelink control information (SCI). [0302] Clause 86. A user equipment (UE), comprising: means for receiving an aperiodic sidelink resource reservation request from a first UE that requests reservation of a set of time- frequency resources at a future absolute time; and means for communicating with the first UE on the set of time-frequency resources in accordance with the aperiodic sidelink resource reservation request. [0303] Clause 87. The UE of clause 86, wherein the future absolute time is defined via coordinated universal time (UTC). [0304] Clause 88. The UE of any of clauses 86 to 87, wherein the aperiodic sidelink resource reservation request is associated with a sidelink-based position estimation session of the first UE, the second UE, or both. [0305] Clause 89. The UE of any of clauses 86 to 88, further comprising: means for transmitting an indication of the reservation of the set of time-frequency resources to one or more other UEs, or means for transmitting an indication that the set of time-frequency resources is non-preferred to the one or more other UEs. [0306] Clause 90. The UE of any of clauses 86 to 89, wherein the aperiodic sidelink resource reservation request of the first type is received via medium access control command element (MAC-CE) or via both MAC-CE and sidelink control information (SCI). [0307] Clause 91. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a first user equipment (UE), cause the UE to: transmit an aperiodic sidelink resource reservation request of a first type to a second UE, wherein the aperiodic sidelink resource reservation request requests reservation of a set of time- frequency resources associated with a future time that is offset relative to a time reference, and wherein aperiodic sidelink resource reservation requests of the first type are associated with a first set of relative timing offset options and aperiodic sidelink resource reservation requests of a second type are associated with a second set of relative timing offset options that is different than the first set of relative timing offset options; and communicate with the second UE on the set of time-frequency resources in accordance with the aperiodic sidelink resource reservation request. [0308] Clause 92. The non-transitory computer-readable medium of clause 91, wherein the second set of relative timing offset options is a subset of the first set of relative timing offset options, or wherein the first set of relative timing offset options is associated with a first information element (IE) and the second set of relative timing offset options is associated with a second IE, or wherein the first set of relative timing offset options is defined in units of milliseconds or seconds or hours or days, or any combination thereof. [0309] Clause 93. The non-transitory computer-readable medium of any of clauses 91 to 92, wherein the aperiodic sidelink resource reservation request of the first type is associated with a sidelink-based position estimation session of the first UE, the second UE, or both. [0310] Clause 94. The non-transitory computer-readable medium of clause 93, wherein the sidelink-based position estimation session comprises a location preparation phase and two or more location execution phases. [0311] Clause 95. The non-transitory computer-readable medium of any of clauses 91 to 94, wherein a maximum timing offset associated with the first set of relative timing offset options is based on a subframe number (SFN)-based timing duration. [0312] Clause 96. The non-transitory computer-readable medium of clause 95, wherein the SFN- based timing duration corresponds to a subframe duration, or a hyper frame duration. [0313] Clause 97. The non-transitory computer-readable medium of any of clauses 91 to 96, wherein the time reference corresponds to a current time, or a subframe number (SFN)- based timing index. [0314] Clause 98. The non-transitory computer-readable medium of any of clauses 91 to 97, wherein the aperiodic sidelink resource reservation request of the first type is transmitted via medium access control command element (MAC-CE) or via both MAC-CE and sidelink control information (SCI). [0315] Clause 99. The non-transitory computer-readable medium of any of clauses 91 to 98, further comprising computer-executable instructions that, when executed by the UE, cause the UE to: receive resource availability information associated with the second UE, resource conflict information associated with the second UE, or both, wherein the set of time-frequency resources is selected based on the resource availability information, the resource conflict information, or both. [0316] Clause 100. The non-transitory computer-readable medium of any of clauses 91 to 99, wherein the communicating comprises a transmission operation, a reception operation, or both. [0317] Clause 101. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a second user equipment (UE), cause the UE to: receive an aperiodic sidelink resource reservation request of a first type from a first UE, wherein the aperiodic sidelink resource reservation request requests reservation of a set of time-frequency resources at a future time that is offset relative to a time reference, and wherein aperiodic sidelink resource reservation requests of the first type are associated with a first set of relative timing offset options and aperiodic sidelink resource reservation requests of a second type are associated with a second set of relative timing offset options that is different than the first set of relative timing offset options; and communicate with the first UE on the set of time-frequency resources in accordance with the aperiodic sidelink resource reservation request. [0318] Clause 102. The non-transitory computer-readable medium of clause 101, further comprising computer-executable instructions that, when executed by the UE, cause the UE to: transmit an indication of the reservation of the set of time-frequency resources to one or more other UEs, or transmit an indication that the set of time-frequency resources is non-preferred to the one or more other UEs. [0319] Clause 103. The non-transitory computer-readable medium of any of clauses 101 to 102, wherein the second set of relative timing offset options is a subset of the first set of relative timing offset options, or wherein the first set of relative timing offset options is associated with a first information element (IE) and the second set of relative timing offset options is associated with a second IE, or wherein the first set of relative timing offset options is defined in units of milliseconds or seconds or hours or days, or any combination thereof. [0320] Clause 104. The non-transitory computer-readable medium of any of clauses 101 to 103, wherein the aperiodic sidelink resource reservation request of the first type is associated with a sidelink-based position estimation session of the first UE, the second UE, or both. [0321] Clause 105. The non-transitory computer-readable medium of clause 104, wherein the sidelink-based position estimation session comprises a location preparation phase and two or more location execution phases. [0322] Clause 106. The non-transitory computer-readable medium of any of clauses 101 to 105, wherein a maximum timing offset associated with the first set of relative timing offset options is based on a subframe number (SFN)-based timing duration. [0323] Clause 107. The non-transitory computer-readable medium of clause 106, wherein the SFN-based timing duration corresponds to a subframe duration, or a hyper frame duration. [0324] Clause 108. The non-transitory computer-readable medium of any of clauses 101 to 107, wherein the time reference corresponds to a current time, or a subframe number (SFN)- based timing index. [0325] Clause 109. The non-transitory computer-readable medium of any of clauses 101 to 108, wherein the aperiodic sidelink resource reservation request of the first type is received via medium access control command element (MAC-CE) or via both MAC-CE and sidelink control information (SCI). [0326] Clause 110. The non-transitory computer-readable medium of any of clauses 101 to 109, further comprising computer-executable instructions that, when executed by the UE, cause the UE to: transmit resource availability information associated with the second UE, resource conflict information associated with the second UE, or both, wherein the set of time-frequency resources is based on the resource availability information, the resource conflict information, or both. [0327] Clause 111. The non-transitory computer-readable medium of any of clauses 101 to 110, wherein the communicating comprises a transmission operation, a reception operation, or both. [0328] Clause 112. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a user equipment (UE), cause the UE to: transmit an aperiodic sidelink resource reservation request to a second UE that requests reservation of a set of time-frequency resources at a future absolute time; and communicate with the second UE on the set of time-frequency resources in accordance with the aperiodic sidelink resource reservation request. [0329] Clause 113. The non-transitory computer-readable medium of clause 112, wherein the future absolute time is defined via coordinated universal time (UTC). [0330] Clause 114. The non-transitory computer-readable medium of any of clauses 112 to 113, wherein the aperiodic sidelink resource reservation request is associated with a sidelink- based position estimation session of the first UE, the second UE, or both. [0331] Clause 115. The non-transitory computer-readable medium of any of clauses 112 to 114, wherein the aperiodic sidelink resource reservation request is transmitted via medium access control command element (MAC-CE) or via both MAC-CE and sidelink control information (SCI). [0332] Clause 116. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a user equipment (UE), cause the UE to: receive an aperiodic sidelink resource reservation request from a first UE that requests reservation of a set of time-frequency resources at a future absolute time; and communicate with the first UE on the set of time-frequency resources in accordance with the aperiodic sidelink resource reservation request. [0333] Clause 117. The non-transitory computer-readable medium of clause 116, wherein the future absolute time is defined via coordinated universal time (UTC). [0334] Clause 118. The non-transitory computer-readable medium of any of clauses 116 to 117, wherein the aperiodic sidelink resource reservation request is associated with a sidelink- based position estimation session of the first UE, the second UE, or both. [0335] Clause 119. The non-transitory computer-readable medium of any of clauses 116 to 118, further comprising computer-executable instructions that, when executed by the UE, cause the UE to: transmit an indication of the reservation of the set of time-frequency resources to one or more other UEs, or transmit an indication that the set of time- frequency resources is non-preferred to the one or more other UEs. [0336] Clause 120. The non-transitory computer-readable medium of any of clauses 116 to 119, wherein the aperiodic sidelink resource reservation request of the first type is received via medium access control command element (MAC-CE) or via both MAC-CE and sidelink control information (SCI). [0337] 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. [0338] 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. [0339] 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. [0340] 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. [0341] 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. [0342] 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. For example, 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. Further, no component, function, action, or instruction described or claimed herein should be construed as critical or essential unless explicitly described as such. Furthermore, as used herein, the terms “set,” “group,” and the like are intended to include one or more of the stated elements. Also, as used herein, the terms “has,” “have,” “having,” “comprises,” “comprising,” “includes,” “including,” and the like does not preclude the presence of one or more additional elements (e.g., an element “having” A may also have B). Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Also, as used herein, the term “or” is intended to be inclusive when used in a series and may be used interchangeably with “and/or,” unless explicitly stated otherwise (e.g., if used in combination with “either” or “only one of”) or the alternatives are mutually exclusive (e.g., “one or more” should not be interpreted as “one and more”). Furthermore, although components, functions, actions, and instructions may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated. Accordingly, as used herein, the articles “a,” “an,” “the,” and “said” are intended to include one or more of the stated elements. Additionally, as used herein, the terms “at least one” and “one or more” encompass “one” component, function, action, or instruction performing or capable of performing a described or claimed functionality and also “two or more” components, functions, actions, or instructions performing or capable of performing a described or claimed functionality in combination.

Claims

CLAIMS What is claimed is: 1. A method of operating a first user equipment (UE), comprising: transmitting an aperiodic sidelink resource reservation request of a first type to a second UE, wherein the aperiodic sidelink resource reservation request requests reservation of a set of time-frequency resources associated with a future time that is offset relative to a time reference, and wherein aperiodic sidelink resource reservation requests of the first type are associated with a first set of relative timing offset options and aperiodic sidelink resource reservation requests of a second type are associated with a second set of relative timing offset options that is different than the first set of relative timing offset options; and communicating with the second UE on the set of time-frequency resources in accordance with the aperiodic sidelink resource reservation request.

2. The method of claim 1, wherein the second set of relative timing offset options is a subset of the first set of relative timing offset options, or wherein the first set of relative timing offset options is associated with a first information element (IE) and the second set of relative timing offset options is associated with a second IE, or wherein the first set of relative timing offset options is defined in units of milliseconds or seconds or hours or days, or any combination thereof.

3. The method of claim 1, wherein the aperiodic sidelink resource reservation request of the first type is associated with a sidelink-based position estimation session of the first UE, the second UE, or both.

4. The method of claim 3, wherein the sidelink-based position estimation session comprises a location preparation phase and two or more location execution phases.

5. The method of claim 1, wherein a maximum timing offset associated with the first set of relative timing offset options is based on a subframe number (SFN)-based timing duration.

6. The method of claim 5, wherein the SFN-based timing duration corresponds to a subframe duration, or a hyper frame duration.

7. The method of claim 1, wherein the time reference corresponds to a current time, or a subframe number (SFN)-based timing index.

8. The method of claim 1, wherein the aperiodic sidelink resource reservation request of the first type is transmitted via medium access control command element (MAC-CE) or via both MAC-CE and sidelink control information (SCI).

9. The method of claim 1, further comprising: receiving resource availability information associated with the second UE, resource conflict information associated with the second UE, or both, wherein the set of time-frequency resources is selected based on the resource availability information, the resource conflict information, or both.

10. The method of claim 1, wherein the communicating comprises a transmission operation, a reception operation, or both.

11. A method of operating a second user equipment (UE), comprising: receiving an aperiodic sidelink resource reservation request of a first type from a first UE, wherein the aperiodic sidelink resource reservation request requests reservation of a set of time-frequency resources at a future time that is offset relative to a time reference, and wherein aperiodic sidelink resource reservation requests of the first type are associated with a first set of relative timing offset options and aperiodic sidelink resource reservation requests of a second type are associated with a second set of relative timing offset options that is different than the first set of relative timing offset options; and communicating with the first UE on the set of time-frequency resources in accordance with the aperiodic sidelink resource reservation request.

12. The method of claim 11, further comprising: transmitting an indication of the reservation of the set of time-frequency resources to one or more other UEs, or transmitting an indication that the set of time-frequency resources is non-preferred to the one or more other UEs.

13. The method of claim 11, wherein the second set of relative timing offset options is a subset of the first set of relative timing offset options, or wherein the first set of relative timing offset options is associated with a first information element (IE) and the second set of relative timing offset options is associated with a second IE, or wherein the first set of relative timing offset options is defined in units of milliseconds or seconds or hours or days, or any combination thereof.

14. The method of claim 11, wherein the aperiodic sidelink resource reservation request of the first type is associated with a sidelink-based position estimation session of the first UE, the second UE, or both.

15. The method of claim 14, wherein the sidelink-based position estimation session comprises a location preparation phase and two or more location execution phases.

16. The method of claim 11, wherein a maximum timing offset associated with the first set of relative timing offset options is based on a subframe number (SFN)-based timing duration.

17. The method of claim 16, wherein the SFN-based timing duration corresponds to a subframe duration, or a hyper frame duration.

18. The method of claim 11, wherein the time reference corresponds to a current time, or a subframe number (SFN)-based timing index.

19. The method of claim 11, wherein the aperiodic sidelink resource reservation request of the first type is received via medium access control command element (MAC-CE) or via both MAC-CE and sidelink control information (SCI).

20. The method of claim 11, further comprising: transmitting resource availability information associated with the second UE, resource conflict information associated with the second UE, or both, wherein the set of time-frequency resources is based on the resource availability information, the resource conflict information, or both.

21. The method of claim 11, wherein the communicating comprises a transmission operation, a reception operation, or both.

22. A method of operating a first user equipment (UE), comprising: transmitting an aperiodic sidelink resource reservation request to a second UE that requests reservation of a set of time-frequency resources at a future absolute time; and communicating with the second UE on the set of time-frequency resources in accordance with the aperiodic sidelink resource reservation request.

23. The method of claim 22, wherein the future absolute time is defined via coordinated universal time (UTC).

24. The method of claim 22, wherein the aperiodic sidelink resource reservation request is associated with a sidelink-based position estimation session of the first UE, the second UE, or both.

25. The method of claim 22, wherein the aperiodic sidelink resource reservation request is transmitted via medium access control command element (MAC- CE) or via both MAC-CE and sidelink control information (SCI).

26. A method of operating a second user equipment (UE), comprising: receiving an aperiodic sidelink resource reservation request from a first UE that requests reservation of a set of time-frequency resources at a future absolute time; and communicating with the first UE on the set of time-frequency resources in accordance with the aperiodic sidelink resource reservation request.

27. The method of claim 26, wherein the future absolute time is defined via coordinated universal time (UTC).

28. The method of claim 26, wherein the aperiodic sidelink resource reservation request is associated with a sidelink-based position estimation session of the first UE, the second UE, or both.

29. The method of claim 26, further comprising: transmitting an indication of the reservation of the set of time-frequency resources to one or more other UEs, or transmitting an indication that the set of time-frequency resources is non-preferred to the one or more other UEs.

30. The method of claim 26, wherein the aperiodic sidelink resource reservation request of the first type is received via medium access control command element (MAC-CE) or via both MAC-CE and sidelink control information (SCI).