Asymmetric round-trip time positioning

Abstract

A method of operating a device comprises determining a first time at which a third node transmits a first reference signal to a second node, determining a second time at which a first node receives a second reference signal from the second node, and determining a cross-node Rx-Tx time difference between the second time and the first time.

Description

Qualcomm Ref. No. 2500147WO1 / 94ASYMMETRIC ROUND-TRIP TIME POSITIONINGTECHNICAL FIELD

[0001] Aspects of the disclosure relate generally to wireless technologies.BACKGROUND

[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)), RF sensing, and other technical enhancements. These enhancements, as well as the use of higher frequency bands, enable improved RF sensing and 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 QC2500147WOQualcomm Ref. No. 2500147WO2 / 94mechanisms disclosed herein in a simplified form to precede the detailed description presented below.

[0005] In an aspect, a method of wireless positioning performed by a device comprises:determining a first time at which a third node transmits a first reference signal to a second node; determining a second time at which a first node receives a second reference signal from the second node; and determining a cross-node Rx-Tx time difference between the second time and the first time.

[0006] In an aspect, a device comprises: one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors, either alone or in combination, configured to: determine a first time at which a third node transmits a first reference signal to a second node; determine a second time at which a first node receives a second reference signal from the second node; and determine a cross-node Rx-Tx time difference between the second time and the first time.

[0007] In an aspect, a device comprises: means for determining a first time at which a third node transmits a first reference signal to a second node; means for determining a second time at which a first node receives a second reference signal from the second node; and means for determining a cross-node Rx-Tx time difference between the second time and the first time.

[0008] In an aspect, a non-transitory computer-readable medium stores computer-executable instructions that, when executed by A device, cause the device to: determine a first time at which a third node transmits a first reference signal to a second node; determine a second time at which a first node receives a second reference signal from the second node; and determine a cross-node Rx-Tx time difference between the second time and the first time.

[0009] Other obj ects and advantages associated with the aspects disclosed herein will be apparent to those skilled in the art based on the accompanying drawings and detailed description.BRIEF DESCRIPTION OF THE DRAWINGS

[0010] The accompanying drawings are presented to aid in the description of various aspects of the disclosure and are provided solely for illustration of the aspects and not limitation thereof.QC2500147WOQualcomm Ref. No. 2500147WO3 / 94

[0011] FIG. 1 illustrates an example wireless communications system, according to aspects of the disclosure.

[0012] FIGS. 2 A, 2B, and 2C illustrate example wireless network structures, according to aspects of the disclosure.

[0013] FIGS. 3A, 3B, and 3C are simplified block diagrams of several sample aspects of components that may be employed in a user equipment (UE), a base station, and a network entity, respectively, and configured to support communications as taught herein.

[0014] FIG. 4 is a diagram illustrating an example round-trip-time (RTT) procedure for determining a location of a UE, according to aspects of the disclosure.

[0015] FIG. 5 is a diagram showing example timings of RTT measurement signals exchanged between a base station and a UE, according to aspects of the disclosure.

[0016] FIG. 6 illustrates an example signal flow diagram for new radio (NR) multi -RTT (mRTT), according to aspects of the disclosure.

[0017] FIG. 7 is a diagram illustrating an example sidelink (SL) ranging and positioning procedure, according to aspects of the disclosure.

[0018] FIGS. 8A, 8B, and 8C illustrate examples of non-terrestrial networks (NTNs) and air-to- ground (ATG) networks.

[0019] FIG. 9A illustrates an example of sidelink Rx-Tx time difference, according to aspects of the disclosure.

[0020] FIG. 9B illustrates an example of cross-UE sidelink Rx-Tx time difference, according to aspects of the disclosure.

[0021] FIGS. 10A - 10B illustrate examples of sidelink-based timing measurements that may be related to asymmetric RTT.

[0022] FIGS. 11 A - 1 IB illustrate examples of sidelink reception time difference measurements, according to aspects of the disclosure.

[0023] FIGS. 12A- 12B illustrate examples of TRP-based timing measurements that may be related to asymmetric RTT.

[0024] FIG. 13 illustrates an example method of wireless positioning, according to aspects of the disclosure.DETAILED DESCRIPTION

[0025] Aspects of the disclosure are provided in the following description and related drawings directed to various examples provided for illustration purposes. Alternate aspects may beQC2500147WOQualcomm Ref. No. 2500147WO4 / 94devised 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.

[0026] Various aspects relate generally to wireless positioning. Some aspects more specifically relate to asymmetric multiple round trip time (mRTT) positioning. In some examples, a device determines a cross-node Rx-Tx time difference between a first time at which a third node transmits a first reference signal to a second node and a second time at which the first node receives a second reference signal from the second node.

[0027] The nodes may be, for example, user equipment (UEs), transmission-reception points (TRPs), and / or next generation node Bs (gNBs). One or more of the nodes may be ‘oneway’ nodes that are either unwilling or unable to transmit or receive reference signals. For example, a ‘one-way’ node may be receive-only (no reference signal transmission) or transmit-only (no reference signal reception). The cross-node Rx-Tx time difference may be used (e.g., along with a time difference between reception of the first reference signal by the second node, and transmission of the second reference signal by the second node) to determine an asymmetric mRTT value. One or more asymmetric mRTT values may be used to determine a location of a node (e.g., the second node).

[0028] Particular aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. In some examples, by determining asymmetric mRTT values, the described techniques can leverage the availability of ‘one-way’ nodes to perform positioning. For example, symmetric mRTT may rely on there being a suitable number of ‘two-way’ nodes being available to transmit and receive reference signals. However, asymmetric mRTT may be performed even if ‘two-way’ nodes are unavailable, or too weak / distant to provide suitable reference signals. Accordingly, asymmetric mRTT may facilitate positioning in a wide variety of scenarios.

[0029] 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.

[0030] 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. ForQC2500147WOQualcomm Ref. No. 2500147WO5 / 94example, 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.

[0031] 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.

[0032] 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 (loT) 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 alsoQC2500147WOQualcomm Ref. No. 2500147WO6 / 94possible 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.

[0033] 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.

[0034] 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 (MEMO) 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 receivesQC2500147WOQualcomm Ref. No. 2500147WO7 / 94wireless 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.

[0035] 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).

[0036] 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.

[0037] 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.

[0038] 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 UEQC2500147WOQualcomm Ref. No. 2500147WO8 / 94104 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.

[0039] 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.

[0040] 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 loT (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, becauseQC2500147WOQualcomm Ref. No. 2500147WO9 / 94a 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.

[0041] 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).

[0042] 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).

[0043] 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.

[0044] 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',QC2500147WOQualcomm Ref. No. 2500147WO10 / 94employing 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®.

[0045] 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.

[0046] 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 theQC2500147WOQualcomm Ref. No. 2500147WO11 / 94radio waves from the separate antennas add together to increase the radiation in a desired direction, while cancelling to suppress radiation in undesired directions.

[0047] 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.

[0048] 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.

[0049] 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 blockQC2500147WOQualcomm Ref. No. 2500147WO12 / 94(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.

[0050] 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.

[0051] 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.

[0052] 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 5GNR 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.

[0053] 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 representQC2500147WOQualcomm Ref. No. 2500147WO13 / 94frequencies 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.

[0054] 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.

[0055] 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 wouldQC2500147WOQualcomm Ref. No. 2500147WO14 / 94theoretically lead to a two-fold increase in data rate (i.e., 40 MHz), compared to that attained by a single 20 MHz carrier.

[0056] 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.

[0057] 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, vehi cl e-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.

[0058] 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 wirelessQC2500147WOQualcomm Ref. No. 2500147WO15 / 94communication 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.1 lx 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.

[0059] 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.

[0060] 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.QC2500147WOQualcomm Ref. No. 2500147WO16 / 94

[0061] In a satellite positioning system, the use of signals 124 can be augmented by various satellite-based augmentation systems (SB AS) 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 Multifunctional 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.

[0062] In an aspect, SVs 112 may additionally or alternatively be part of one or more nonterrestrial 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.

[0063] 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.

[0064] 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,QC2500147WOQualcomm Ref. No. 2500147WO17 / 94gateway 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).

[0065] 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).

[0066] 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 messageQC2500147WOQualcomm Ref. No. 2500147WO18 / 94service (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.

[0067] 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.

[0068] 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. TheQC2500147WOQualcomm Ref. No. 2500147WO19 / 94interface over which the SMF 266 communicates with the AMF 264 is referred to as the Nil interface.

[0069] 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).

[0070] 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.

[0071] 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.QC2500147WOQualcomm Ref. No. 2500147WO20 / 94

[0072] 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 “Fl” 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.

[0073] 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, AP, TRP, 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.

[0074] 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 withQC2500147WOQualcomm Ref. No. 2500147WO21 / 94the 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).

[0075] 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 (0-RAN (such as the network configuration sponsored by the 0-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.

[0076] 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 Fl 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.

[0077] 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 oneQC2500147WOQualcomm Ref. No. 2500147WO22 / 94or 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.

[0078] 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 El interface when implemented in an 0-RAN configuration. The CU 280 can be implemented to communicate with the DU 285, as necessary, for network control and signaling.

[0079] 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 CU280.

[0080] 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,QC2500147WOQualcomm Ref. No. 2500147WO23 / 94the 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.

[0081] 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 01 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 02 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 01 interface. Additionally, in some implementations, the SMO Framework 255 can communicate directly with one or more RUs 287 via an 01 interface. The SMO Framework 255 also may include a Non-RT RIC 257 configured to support functionality of the SMO Framework 255.

[0082] 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 Al 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.QC2500147WOQualcomm Ref. No. 2500147WO24 / 94

[0083] 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 01) or via creation of RAN management policies (such as Al policies).

[0084] 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. 2 A 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.

[0085] 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 fortuning, 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 oneQC2500147WOQualcomm Ref. No. 2500147WO25 / 94designated 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.

[0086] 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 vehi cl e-to- vehicle (V2V) and / or vehicle-to- everything (V2X) transceivers.QC2500147WOQualcomm Ref. No. 2500147WO26 / 94

[0087] The UE 302 and the base station 304 also include, at least in some cases, satellite signal interfaces 330 and 370, which each include one or more satellite signal receivers 332 and 372, respectively, and may optionally include one or more satellite signal transmitters 334 and 374, respectively. In some cases, the base station 304 may be a terrestrial base station that may communicate with space vehicles (e.g., space vehicles 112) via the satellite signal interface 370. In other cases, the base station 304 may be a space vehicle (or other non-terrestrial entity) that uses the satellite signal interface 370 to communicate with terrestrial networks and / or other space vehicles.

[0088] The satellite signal receivers 332 and 372 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 receiver(s) 332 and 372 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) signals, etc. Where the satellite signal receiver(s) 332 and 372 are nonterrestrial 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 receiver(s) 332 and 372 may comprise any suitable hardware and / or software for receiving and processing satellite positioning / communication signals 338 and 378, respectively. The satellite signal receiver(s) 332 and 372 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.

[0089] The optional satellite signal transmitter(s) 334 and 374, when present, may be connected to the one or more antennas 336 and 376, respectively, and may provide means for transmitting satellite positioning / communication signals 338 and 378, respectively. Where the satellite signal transmitter(s) 374 are satellite positioning system transmitters, the satellite positioning / communication signals 378 may be GPS signals, GLONASS® signals, Galileo signals, Beidou signals, NAVIC, QZSS signals, etc. Where the satellite signal transmitter(s) 334 and 374 are NTN transmitters, the satellite positioning / communication signals 338 and 378 may be communication signals (e.g.,QC2500147WOQualcomm Ref. No. 2500147WO27 / 94carrying control and / or user data) originating from a 5G network. The satellite signal transmitter(s) 334 and 374 may comprise any suitable hardware and / or software for transmitting satellite positioning / communication signals 338 and 378, respectively. The satellite signal transmitter(s) 334 and 374 may request information and operations as appropriate from the other systems.

[0090] 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.

[0091] 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 onlyQC2500147WOQualcomm Ref. No. 2500147WO28 / 94receive 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.

[0092] 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.

[0093] 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 342, 384, and 394, respectively, for providing functionality relating to, for example, wireless communication, and for providing other processing functionality. The processors 342, 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 342, 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.

[0094] The UE 302, the base station 304, and the network entity 306 include memory circuitry implementing memories 340, 386, and 396 (e.g., each including a memory device), respectively, for maintaining information (e.g., information indicative of reserved resources, thresholds, parameters, and so on). The memories 340, 386, and 396 may therefore provide means for storing, means for retrieving, means for maintaining, etc. In some cases, the UE 302, the base station 304, and the network entity 306 may include positioning component 348, 388, and 398, respectively. The positioning component 348,QC2500147WOQualcomm Ref. No. 2500147WO29 / 94388, and 398 may be hardware circuits that are part of or coupled to the processors 342, 384, and 394, respectively, that, when executed, cause the UE 302, the base station 304, and the network entity 306 to perform the functionality described herein. In other aspects, the positioning component 348, 388, and 398 may be external to the processors 342, 384, and 394 (e.g., part of a modem processing system, integrated with another processing system, etc.). Alternatively, the positioning component 348, 388, and 398 may be memory modules stored in the memories 340, 386, and 396, respectively, that, when executed by the processors 342, 384, and 394 (or a modem processing system, another processing system, etc.), cause the UE 302, the base station 304, and the network entity 306 to perform the functionality described herein. FIG. 3A illustrates possible locations of the positioning component 348, which may be, for example, part of the one or more WWAN transceivers 310, the memory 340, the one or more processors 342, or any combination thereof, or may be a standalone component. FIG. 3B illustrates possible locations of the positioning 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 positioning 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.

[0095] The UE 302 may include one or more sensors 344 coupled to the one or more processors 342 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 interface 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.QC2500147WOQualcomm Ref. No. 2500147WO30 / 94

[0096] 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.

[0097] 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.

[0098] The transmitter 354 and the receiver 352 may implement Layer- 1 (LI) 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 divisionQC2500147WOQualcomm Ref. No. 2500147WO31 / 94multiplexing (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.

[0099] 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 342. 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 342, which implements Layer-3 (L3) and Layer-2 (L2) functionality.

[0100] In the downlink, the one or more processors 342 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 342 are also responsible for error detection.

[0101] Similar to the functionality described in connection with the downlink transmission by the base station 304, the one or more processors 342 provides RRC layer functionalityQC2500147WOQualcomm Ref. No. 2500147WO32 / 94associated 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.

[0102] 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.

[0103] 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.

[0104] 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.

[0105] For convenience, the UE 302, the base station 304, and / or the network entity 306 are shown in FIGS. 3 A, 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. 3 A,QC2500147WOQualcomm Ref. No. 2500147WO33 / 94a 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 interface 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 interface 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.

[0106] 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 308, 382, and 392, respectively. In an aspect, the data buses 308, 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 308, 382, and 392 may provide communication between them.

[0107] The components of FIGS. 3A, 3B, and 3C may be implemented in various ways. In some implementations, the components of FIGS. 3 A, 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, variousQC2500147WOQualcomm Ref. No. 2500147WO34 / 94operations, 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 342, 384, 394, the transceivers 310, 320, 350, and 360, the memories 340, 386, and 396, the positioning component 348, 388, and 398, etc.

[0108] 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).

[0109] FIG. 4 illustrates an example wireless communications system 400, according to aspects of the disclosure. In the example of FIG. 4, a UE 404 (e.g., any of the UEs described herein) is attempting to calculate an estimate of its location, or assist another entity (e.g., a base station or core network component, another UE, a location server, a third party application, etc.) to calculate an estimate of its location. The UE 404 may transmit and receive wireless signals to and from a plurality of network nodes (labeled “Node”) 402- 1, 402-2, and 402-3 (collectively, network nodes 402). The network nodes 402 may include one or more base stations (e.g., any of the base stations described herein), one or more reconfigurable intelligent displays (RIS), one or more positioning beacons, one or more UEs (e.g., connected over sidelinks), etc.

[0110] In a network-centric RTT positioning procedure the serving base station (e.g., one of network nodes 402) instructs the UE 404 to measure RTT measurement signals (e.g., PRS) from two or more neighboring network nodes 402 (and typically the serving base station, as at least three network nodes 402 are needed for a two-dimensional location estimate). The involved network nodes 402 transmit RTT measurement signals on low reuse resources (e.g., resources used by the network nodes 402 to transmit system information, where the network nodes 402 are base stations) allocated by the network (e.g., location server 230, LMF 270, SLP 272). The UE 404 records the arrival time (also referred to as the receive time, reception time, time of reception, or time of arrival) of each RTT measurement signal relative to the UE’s 404 current downlink timing (e.g., asQC2500147WOQualcomm Ref. No. 2500147WO35 / 94derived by the UE 404 from a downlink signal received from its serving base station), and transmits a common or individual RTT response signal (e.g., SRS) to the involved network nodes 402 on resources allocated by its serving base station. The UE 404, if it not the positioning entity, reports a UE reception-to-transmission (Rx-Tx) time difference measurement to the positioning entity. The UE Rx-Tx time difference measurement indicates the time difference between the arrival time of each RTT measurement signal at the UE 404 and the transmission time(s) of the RTT response signal(s). Each involved network node 402 also reports, to the positioning entity, a network node Rx-Tx time difference measurement (also referred to as a base station (BS) or gNB Rx-Tx time difference measurement), which indicates the difference between the transmission time of the RTT measurement signal and the reception time of the RTT response signal.

[0111] A UE-centric RTT positioning procedure is similar to the network-based procedure, except that the UE 404 transmits uplink RTT measurement signal(s) (e.g., on resources allocated by the serving base station). The uplink RTT measurement signal(s) are measured by multiple network nodes 402 in the neighborhood of the UE 404. Each involved network node 402 responds with a downlink RTT response signal and reports a network node Rx-Tx time difference measurement to the positioning entity. The network node Rx-Tx time difference measurement indicates the time difference between the arrival time of the RTT measurement signal at the network node 402 and the transmission time of the RTT response signal. The UE 404, if it is not the positioning entity, reports, for each network node 402, a UE Rx-Tx time difference measurement that indicates the difference between the transmission time of the RTT measurement signal and the reception time of the RTT response signal.

[0112] In order to determine the location (x, y) of the UE 404, the positioning entity needs to know the locations of the network nodes 402, which may be represented in a reference coordinate system as (x_k, y_y), where k=l, 2, 3 in the example of FIG. 4. Where the UE 404 is the positioning entity, a location server with knowledge of the network geometry (e.g., location server 230, LMF 270, SLP 272) may provide the locations of the involved network nodes 402 to the UE 404.

[0113] The positioning entity determines each distance 410 (d_k, where k=l, 2, 3) between the UE 404 and the respective network node 402 based on the UE Rx-Tx and network node Rx-Tx time difference measurements and the speed of light, as described further below with reference to FIG. 5. Specifically, in the example of FIG. 4, the distance 410-1QC2500147WOQualcomm Ref. No. 2500147WO36 / 94between the UE 404 and the network node 402-1 is d_l, the distance 410-2 between the UE 404 and the network node 402-2 is d_2, and the distance 410-3 between the UE 404 and the network node 402-3 is d_3. Once each distance 410 is determined, the positioning entity can solve for the location (x, y) of the UE 404 by using a variety of known geometric techniques, such as trilateration. From FIG. 4, it can be seen that the location of the UE 404 ideally lies at the common intersection of three semicircles, each semicircle being defined by radius dk and center (x_k, y_k), where k=l, 2, 3.

[0114] FIG. 5 is a diagram 500 showing example timings of RTT measurement signals exchanged between a network node 502 (labeled “Node”) and a UE 504, according to aspects of the disclosure. The UE 504 may be any of the UEs described herein. The network node 502 may be a base station (e.g., any of the base stations described herein), an RIS, a positioning beacon, another UE (e.g., connected over a sidelink), or the like.

[0115] In the example of FIG. 5, the network node 502 (labeled “BS”) sends an RTT measurement signal 510 (e.g., PRS) to the UE 504 at time T_l. The RTT measurement signal 510 has some propagation delay T Prop as it travels from the network node 502 to the UE 504. At time T_2 (the reception time of the RTT measurement signal 510 at the UE 504), the UE 504 measures the RTT measurement signal 510. After some UE processing time, the UE 504 transmits an RTT response signal 520 (e.g., SRS) at time T_3. After the propagation delay T Prop, the network node 502 measures the RTT response signal 520 from the UE 504 at time T_4 (the reception time of the RTT response signal 520 at the network node 502).

[0116] The UE 504 reports the difference between time T_3 and time T_2 (i.e., the UE’s 504 Rx-Tx time difference measurement, shown as UE_Rx-Tx 512) to the positioning entity. Similarly, the network node 502 reports the difference between time T_4 and time T_1 (i.e., the network node’s 502 Rx-Tx time difference measurement, shown as Node Rx- Tx 522) to the positioning entity. Using these measurements and the known speed of light, the positioning entity can calculate the distance to the UE 504 as d = l / 2*c*(Node_Rx- Tx - UE_Rx-Tx) = l / 2*c*(T_4 - T_l) - l / 2*c*(T_3 - T_2), where c is the speed of light.

[0117] Based on the known location of the network node 502 and the distance between the UE 504 and the network node 502 (and at least two other network nodes 502), the positioning entity can calculate the location of the UE 504. As shown in FIG. 4, the location of the UE 504 lies at the common intersection of three semicircles, each semicircle beingQC2500147WOQualcomm Ref. No. 2500147WO37 / 94defined by a radius of the distance between the UE 504 and a respective network node 502.

[0118] In an aspect, the positioning entity may calculate the UE’s 404 / 504 location using a two- dimensional coordinate system; however, the aspects disclosed herein are not so limited, and may also be applicable to determining locations using a three-dimensional coordinate system, if the extra dimension is desired. Additionally, while FIG. 4 illustrates one UE 404 and three network nodes 402 and FIG. 5 illustrates one UE 504 and one network node 502, as will be appreciated, there may be more UEs 404 / 504 and more network nodes 402 / 502.

[0119] FIG. 6 illustrates an example signal flow diagram for new radio (NR) multi -RTT (mRTT), according to aspects of the disclosure. The figure includes a UE 630, a gNB / TRP 641, a gNB / TRP 651, a gNB / TRP 652, a gNB / TRP 653, and an LMF 690. The gNB / TRP 641 may be associated with a serving cell of UE 630. The gNB / TRP 651, gNB / TRP 652, and gNB / TRP 653 may be associated with neighbor cells of UE 630.

[0120] At 600, LMF 690 may use a new radio positioning protocol a (NRPPa) TRP information exchange procedure to obtain TRP information used (e.g., required) for mRTT positioning.

[0121] At 601, LMF 690 may request positioning capabilities of UE 630 using a long term evolution positioning protocol (LPP) capability transfer procedure.

[0122] At 602, LMF 690 sends an NRPPa positioning information request message to serving gNB / TRP 641 to request uplink information for UE 630.

[0123] At 603, serving gNB / TRP 641 determines one or more resources available for one or more uplink sounding reference signals (UL-SRSs). At 603a, serving gNB / TRP 641 configures UE 630 with one or more UL-SRS resource sets (e.g., sends a configuration message indicating the one or more UL-SRSs, the one or more UL-SRS resource sets, or any combination thereof).

[0124] At 604, serving gNB / TRP 641 provides the UL-SRS configuration information to LMF 690 in an NRPPa positioning information response message. Optionally, the SRS configuration may be provided earlier than a DL-PRS configuration.

[0125] At 605a, LMF 690 may request activation of UE SRS transmission by sending an NRPPa positioning activation request message to serving gNB / TRP 641. The request for activation of UE SRS transmission may be associated with semi-persistent or aperiodic SRS. At 605b, serving gNB / TRP 641 activates the UE SRS transmission. UE 630 beginsQC2500147WOQualcomm Ref. No. 2500147WO38 / 94the UL-SRS transmission according to time domain behavior of the UL-SRS resource configuration. At 605c, serving gNB / TRP 641 sends an NRPPa positioning activation response message.

[0126] At 606, LMF 690 provides uplink information to one or more gNBs (e.g., one or more neighbor gNBs of UE 630) in an NRPPa measurement request message. The NRPPa measurement request message may include information used (e.g., all information required) to enable the one or more gNBs (e.g., gNB / TRP 651, gNB / TRP 652, and gNB / TRP 653) to perform uplink measurements.

[0127] At 607, LMF 690 sends an LPP provide assistance data message to UE 630. The LPP provide assistance data message may include assistance data (e.g., any required assistance data) for UE 630 to perform one or more downlink positioning reference signals (DL- PRS) measurements. The LPP provide assistance data message may indicate one or more PRS and / or one or more gNBs that transmit the one or more PRS (e.g., gNB / TRP 641, gNB / TRP 651, gNB / TRP 652, and / or gNB / TRP 653).

[0128] At 608, LMF 690 sends an LPP request location information message to request mRTT measurements. At 609a, UE 630 performs DL-PRS measurements of one or more PRSs received from one or more gNBs indicated in the assistance data at 607 (e.g., all gNBs indicated in the assistance data at 607). In non-terrestrial networks, UE 630 may perform the DL-PRS measurements from a single TRP at different time instances. At 609b, one or more of the gNBs configured at 606 (e.g., all configured gNBs) measure one or more UE SRS transmissions from UE 630.

[0129] At 610, UE 630 reports the DL-PRS measurements for mRTT to LMF 690 in an LPP provide location information message. At 611, one or more gNBs (e.g., all gNBs) report the UE SRS measurements to LMF 690 in an NRPPa measurement response message. At 612, LMF 690 sends an NRPPa positioning deactivation message to serving gNB / TRP 641. At 613, LMF 690 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 610 and / or 611 and calculates the position of UE 630.

[0130] The mRTT positioning method makes use of (1) the UE Rx-Tx time difference measurements (and optionally downlink (DL) PRS reference signal received power (RSRP) (DL-PRS-RSRP), DL-PRS reference signal received path power (RSRPP) (DL- PRS-RSRPP), and / or DL reference signal carrier phase (RSCP) (DL-RSCP) of downlink signals received from multiple TRPs (e.g., gNB / TRP 641, gNB / TRP 651, gNB / TRP 652,QC2500147WOQualcomm Ref. No. 2500147WO39 / 94and / or gNB / TRP 653), measured by UE 630 and (2) the measured gNB Rx-Tx time difference measurements (and optionally UL-SRS-RSRP and / or UL-SRS-RSRPP and / or UL-RSCP) at TRPs (e g., gNB / TRP 641, gNB / TRP 651, gNB / TRP 652, and / or gNB / TRP 653) of uplink signals transmitted from UE 630.

[0131] UE 630 measures the UE Rx-Tx time difference measurements (and optionally DL-PRS- RSRP and / or DL-PRS-RSRPP and / or DL-RSCP of the received signals) using assistance data received from the positioning server, and the TRPs measure the gNB Rx-Tx time difference measurements (and optionally UL-SRS-RSRP and / or UL-SRS-RSRPP and / or UL-RSCP of the received signals) using assistance data received from the positioning server. The measurements are used to determine the RTTs at the positioning server which are used to estimate the location of UE 630.

[0132] For network verification of UE location in non-terrestrial networks, the mRTT positioning method makes use of (1) the UE Rx-Tx time difference measurements (and optionally DL-PRS-RSRP and / or DL-PRS-RSRPP) of downlink signals received from a single TRP at different time instances, measured by UE 630 and (2) the measured gNB Rx-Tx time difference measurements (and optionally UL-SRS-RSRP and / or UL-SRS- RSRPP) at a single TRP at different time instances of uplink signals transmitted from UE. Together with each UE Rx-Tx time difference measurement, UE 630 also reports the UE Rx-Tx time difference subframe offset measurement in unit of subframe and the DL timing drift due to Doppler on service link between UE and satellite.

[0133] In the mRTT positioning method, the position of UE 630 may be estimated based on measurements performed at both UE and TRPs. The measurements performed at UE 630 and TRPs are UE / gNB Rx-Tx time difference measurements (and optionally DL-PRS- RSRP, DL-PRS-RSRPP, UL-SRS-RSRP, UL-SRS RSRPP, and / or DL-RSCP / UL-RSCP) of DL-PRS and UL-SRS, which are used by LMF 690 to determine the RTTs.

[0134] For network verification of UE location in non-terrestrial networks, the measurements can be performed at a single TRP at different time instances. The additional measurements performed at UE are the UE Rx-Tx time difference subframe offset in unit of subframe and the DL timing drift due to Doppler in service link between UE and satellite. UE 630 may require measurement gaps to perform the mRTT measurements from NR TRPs. UE 630 may request measurement gaps from a gNB using a measurement gap request procedure. UE 630 may also request to activate preconfigured measurement gaps.QC2500147WOQualcomm Ref. No. 2500147WO40 / 94

[0135] Assistance data may be transferred from LMF 690 to UE 630. The assistance data may include physical cell IDs (PCIs), global cell IDs (GCIs), PRS IDs, and ARFCNs of candidate NR TRPs for measurement. The assistance data may include timing relative to a serving (reference) TRP of candidate NR TRPs. The assistance data may include a DL- PRS configuration of candidate NR TRPs. The assistance data may include an indication of which DL-PRS resource sets across DL-PRS positioning frequency layers are linked for DL-PRS bandwidth aggregation. The assistance data may include SSB information of the TRPs, specifying the time and frequency occupancy of SSBs. The assistance data may include a PRS-only transmission point (TP) indication. The assistance data may include on-demand DL-PRS configurations, possibly with information on which configurations are available for DL-PRS bandwidth aggregation. The assistance data may include a validity area of the assistance data.

[0136] Measurement results may be transferred from UE 630 to LMF 690. The measurement results may include physical cell identifier (PCI), global cell identifier (GCI), PRS ID, absolute radio frequency channel number (ARFCN), PRS resource ID, and PRS resource set ID for each measurement. The measurement results may include DL-PRS-RSRP measurements. The measurement results may include UE Rx-Tx time difference measurements. The measurement results may include DL-RSCP measurements. The measurement results may include a timestamp of the measurement. The measurement results may include a quality for each measurement. The measurement results may include a timing advance (TA) offset used by UE 630.

[0137] The measurement results may include UE Rx timing error group (TEG) IDs, UE Tx TEG IDs, and UE Rx-Tx TEG IDs associated with UE Rx-Tx time difference measurements. The measurement results may include line-of-sight (LOS) / non-line-of-sight (NLOS) information for UE measurements. The measurement results may include DL-PRS- RSRPP measurements. The measurement results may include an association of UE Tx TEG ID and SRS. The measurement results may include an indication that DL-PRS bandwidth aggregation has been used for UE Rx-Tx time difference measurements. The measurement results may include an indication that the reported measurements are based on receiving single or multiple hops of DL-PRS. The measurement results may include a UE Rx-Tx time difference subframe offset. The measurement results may include DL timing drift.QC2500147WOQualcomm Ref. No. 2500147WO41 / 94

[0138] The DL-RSCP measurement may be reported along with the UE Rx-Tx time difference measurement. The DL-RSCP may be measured from a single DL PRS positioning frequency layer.

[0139] Assistance data may be transferred from one or more gNBs (e.g., gNB / TRP 641, gNB / TRP 651, gNB / TRP 652, and / or gNB / TRP 653) to LMF 690. The assistance data may include PCI, GCI, ARFCN, and TRP IDs of the TRPs served by the gNB. The assistance data may include timing information of the TRPs served by the gNB. The assistance data may include the DL-PRS configuration of the TRPs served by the gNB. The assistance data may include an indication of which DL-PRS resource sets across DL- PRS positioning frequency layers are linked for DL-PRS bandwidth aggregation.

[0140] The assistance data may include SSB information of the TRPs, detailing a time and frequency occupancy of SSBs. The assistance data may include spatial direction information of the DL-PRS resources of the TRPs served by the gNB. The assistance data may include geographical coordinates information of the DL-PRS resources of the TRPs served by the gNB. The assistance data may include a TRP type.

[0141] The assistance data may include on-demand DL-PRS information, possibly together with information on which configurations are available for DL-PRS bandwidth aggregation. The assistance data may include TRP Tx TEG association information. The assistance data may include common TA parameters of TRPs. The assistance data may include mobile TRP location information. The assistance data may include a mobile integrated access backhaul mobile terminal (IAB-MT) UE ID.

[0142] Uplink (UL) information or UE configuration data may be transferred from the serving gNB (e.g., gNB / TRP 641) to LMF 690. The UL information or UE configuration data may include the UE SRS configuration. The UL information or UE configuration data may include a system frame number (SFN) initialization time for the SRS configuration. The data may include an SRS transmission status.

[0143] Measurement results may be transferred from one or more gNBs (e.g., gNB / TRP 641, gNB / TRP 651, gNB / TRP 652, and / or gNB / TRP 653) to LMF 690. The measurement results may include an NR cell global identifier (NCGI) and / or TRP ID of the measurement. The measurement results may include the gNB Rx-Tx time difference measurement. The measurement results may include UL-SRS-RSRP and UL-SRS- RSRPP. The measurement results may include a UL-RSCP measurement. The measurement results may include a UL angle-of-arrival (AoA) (e.g., azimuth and / orQC2500147WOQualcomm Ref. No. 2500147WO42 / 94elevation). The measurement results may include multiple UL angle-of-arrivals (AoAs) (e.g., azimuth and / or elevation). The measurement results may include an SRS resource type. The measurement results may include a timestamp of the measurement.

[0144] The measurement results may include a quality for each measurement. The measurement results may include beam information of the measurement. The measurement results may include LOS / NLOS information for each measurement. The measurement results may include an antenna reference point (ARP) ID of the measurement. The measurement results may include mobile TRP location information.

[0145] UL-SRS transmission characteristic information may be transferred from LMF 690 to one or more gNBs (e.g., gNB / TRP 641, gNB / TRP 651, gNB / TRP 652, and / or gNB / TRP 653). The UL-SRS transmission characteristics information may be requested UL-SRS transmission characteristics information. The information may include a number of transmissions or a duration for which the UL-SRS is requested. The information may include a bandwidth. The information may include a resource type (e.g., periodic, semi- persistent, or aperiodic). The information may include a number of requested SRS resource sets and SRS resources per set. The information may include a pathloss reference (e.g., PCI, synchronization signal block (SSB) index, DL-PRS ID, DL-PRS resource set ID, and / or DL-PRS resource ID). The information may include spatial relation information (e g., PCI, SSB index, DL-PRS ID, DL-PRS resource set ID, DL-PRS resource ID, non-zero power (NZP) CSI-RS resource ID, SRS resource ID, and / or positioning SRS resource ID). The information may include a periodicity of the SRS for each SRS resource set. The information may include SSB information. The information may include a carrier frequency of the SRS transmission bandwidth.

[0146] TRP measurement request information may be transferred from LMF 690 to one or more gNBs (e.g., gNB / TRP 641, gNB / TRP 651, gNB / TRP 652, and / or gNB / TRP 653). The information may include a TRP ID and NCGI of the TRP to receive UL-SRS. The information may include a UE-SRS configuration. The information may include UL timing information together with timing uncertainty for a reception of SRS by candidate TRPs. The information may include report characteristics for the measurements. The information may include measurement quantities. The information may include a measurement periodicity. The information may include a measurement beam information request. The information may include search window information. The information may include expected UL additionally or alternatively and / or zenith angle of arrival (ZoA)QC2500147WOQualcomm Ref. No. 2500147WO43 / 94and / or an uncertainty range. The information may include a number of TRP Rx TEGs. The information may include a number of TRP Rx-Tx TEGs. The information may include response time. The information may include a measurement characteristics request indicator. The information may include measurement time occasions for a measurement instance.

[0147] Requested positioning activation or deactivation information may be transferred from LMF 690 to one or more gNBs (e.g., gNB / TRP 641, gNB / TRP 651, gNB / TRP 652, and / or gNB / TRP 653). The information may include SP UL-SRS (e.g., activation or deactivation). The information may include a request (e.g., positioning SRS resource). The information may include a set ID to be activated or deactivated (e.g., a spatial relation for the resource). The information may indicate an identifier (e.g., IDi) and / or an activation time. The information may include an aperiodic UL-SRS (e.g., aperiodic SRS resource). The information may include a trigger list (e.g., activation time). The information may indicate UL-SRS (e.g., release all).

[0148] FIG. 7 is a diagram illustrating an example sidelink (SL) ranging and positioning procedure, according to aspects of the disclosure.

[0149] NR supports various sidelink ranging techniques. Sidelink-based ranging and positioning (SLRP) enables the determination of the relative distance(s) between UEs and optionally their absolute position(s), where the absolute position of at least one involved UE is known. This technique is valuable in situations where global navigation satellite system (GNSS) positioning is degraded or unavailable (e.g., tunnels, urban canyons, etc.) and can also enhance range and positioning accuracy when GNSS is available.

[0150] SLRP is based on calculating an inter-UE RTT measurement, as determined from the transmit and receive times of sidelink positioning reference signals (SL-PRS) (a wideband positioning signal defined for sidelink-based positioning). Each UE reports an RTT measurement to all other participating UEs, along with its location (if known). For UEs having zero or inaccurate knowledge of their location, the RTT procedure yields an inter- UE range between the involved UEs. For UEs having accurate knowledge of their location, the range yields an absolute position.

[0151] FIG. 7 illustrates an example sidelink-based ranging and positioning (SLRP) procedure 700, according to aspects of the disclosure. An SLRP procedure 700 is established using the Sidelink Positioning Protocol (SLPP) to identify participating UEs, perform session establishment, and exchange measurements and measurement results. SLPP reuses theQC2500147WOQualcomm Ref. No. 2500147WO44 / 94basic Long-Term Evolution (LTE) positioning protocol (LPP) message constructs of Request / Provide Capabilities, Request / Provide Assistance Data, and Request / Provide Location Information.

[0152] An SLRP procedure 700 (or session) begins with a target UE 702 (a UE with an unknown or inaccurate location that is attempting to be located) transmitting, at stage 705, an SLPP Request Capabilities message requesting capability information from one or more peer UEs. As shown in FIG. 7, at least one of the peer UEs, UE 701, is capable of being an anchor UE for the SLRP procedure 700. As such, at stage 710, the anchor UE 701 responds with an SLPP Provide Capabilities message that includes an indication that it is capable of being an anchor UE for the SLRP procedure 700. The SLPP Provide Capabilities message may also include the location of the anchor UE 701, or this may be provided later. Note that while FIG. 7 illustrates the target UE 702 initiating the SLPP capabilities exchange procedure by transmitting the SLPP Request Capabilities message, an SLPP capabilities exchange can be initiated by either a target UE 702 or an anchor UE 701. In the latter case, an anchor UE 701 may be, for example, an RSU situated at an intersection periodically polling vehicles to establish a positioning session by transmitting SLPP Request Capabilities messages to the vehicles.

[0153] At stage 715, after the initial capability exchange, the anchor UE 701 transmits an SLPP Request Assistance Data message to the target UE 702. At stage 720, the target UE 702 transmits an SLPP Provide Assistance Data message to the anchor UE 701, which may include the configuration of one or more SL-PRS resources to be transmitted by the anchor UE 701 for measurement by the target UE 702 for the SLRP procedure 700. Alternatively or additionally, the SLPP Provide Assistance Data message may include configuration information for one or more SL-PRS resources to be transmitted by the target UE 702 for measurement by the anchor UE 701. In some cases (not shown), the target UE 702 may transmit an SLPP Request Assistance Data message to the anchor UE 701 to obtain configuration information for the one or more SL-PRS resources transmitted by the anchor UE 701 for measurement by the target UE 702. The target UE 702 provides the requested configuration information in an SLPP Provide Assistance Data message. In some cases, the respective UE 204 may not transmit an SLPP Request Assistance Data message, but instead, only the SLPP Provide Assistance Data message.

[0154] At stages 725 and 730, the involved peer UEs 204 transmit the configured SL-PRS resources to each other. Alternatively, only the anchor UE 701 of the target UE 702 mayQC2500147WOQualcomm Ref. No. 2500147WO45 / 94transmit SL-PRS resources (e.g., in the case of a sidelink time-difference of arrival (SL- TDOA) procedure). The resources on which the SL-PRS are transmitted may be configured during the assistance data exchange(s) at stages 715 and 720. The anchor UE 701 measures the reception-to-transmission (Rx-Tx) time difference between the transmission time of the SL-PRS resource(s) at stage 725 and the reception time of the SL-PRS resource(s) at stage 730. Likewise, the target UE 702 measures the Rx-Tx time difference between the reception time of the SL-PRS resource(s) at stage 725 and the transmission time of the SL-PRS resource(s) at stage 730. Note that although FIG. 7 illustrates the anchor UE 701 transmitting SL-PRS first, the target UE 702 may instead transmit SL-PRS first as may be specified in the SLPP Provide Assistance Data message at stage 720.

[0155] At stage 735, the target UE 702 transmits an SLPP Request Location Information message to the anchor UE 701. At stage 740, the anchor UE 701 responds with an SLPP Provide Location Information message that includes the Rx-Tx time difference measurement(s) obtained by the anchor UE 701. Alternatively or additionally (not shown), the anchor UE 701 may transmit an SLPP Request Location Information message to the target UE 702 and the target UE 702 may respond with an SLPP Provide Location Information message including the Rx-Tx time difference measurement(s) obtained by the target UE 702. If the anchor UE 701 has not yet provided its location to the target UE 702, it does so at this point.

[0156] The target UE 702 is then able to determine the RTT between itself and the anchor UE 701 based on the Rx-Tx time difference measurements. Based on the RTT measurement and the speed of light, the target UE 702 can then estimate the distance (or range) between the two UEs 204. If the target UE 702 also has the absolute location (e.g., geographic coordinates) of the anchor UE 701 and two or more additional anchor UEs 701, the target UE 702 can use that location and the distance to the anchor UEs 701 to determine its own absolute location (e.g., based on trilateration).

[0157] Note that while FIG. 7 illustrates one anchor UE 701, a target UE 702 may perform, or attempt to perform, the SLRP procedure 700 with multiple anchor UEs 701. Further, while FIG. 7 illustrates the SLPP Request Location Information being transmitted after the SL-PRS resources are transmitted, it may be transmitted before SL-PRS transmission.

[0158] The SL-RTT positioning method makes use of SL Rx-Tx time difference measurements (and optionally SL-PRS-RSRP and / or SL-PRS-RSRPP) of sidelink signals received atQC2500147WOQualcomm Ref. No. 2500147WO46 / 94the target UE from one or more peer UEs (e.g., anchor UEs) and the SL Rx-Tx time difference measurements (and optionally SL-PRS-RSRP and / or SL-PRS-RSRPP) performed at the one or more peer UEs (e.g., anchor UEs) of sidelink signals transmitted by the target UE. The SL Rx-Tx time difference measurements performed by a pair of UEs allows determining the distance / range between the pair of UEs. Distance / range measurements between a target UE and multiple peer UEs may be used to determine the location of the target UE relative to the locations of the peer UEs (e.g., anchor UEs).

[0159] For sidelink positioning and ranging using SL-RTT, SL-AoA, SL-time difference of arrival (TDOA), and / or SL-Time of arrival (TOA) methods, UEs may transmit and / or receive SL-PRS over the NR PC5 interface. A UE may be configured with one or more sidelink resource pools via system information or dedicated signaling while inside NG- RAN coverage or via pre-configuration while outside NG-RAN coverage.

[0160] A sidelink resource pool that may be used for the transmission of both SL-PRS and SL data may be referred to as an SL-PRS shared resource pool. A sidelink resource pool that may only be used for the transmission of SL-PRS and may not be used for SL data may be referred to as an SL-PRS dedicated resource pool.

[0161] Two sidelink resource allocation schemes for SL-PRS may be supported: scheme 1 and scheme 2. In scheme 1, the SL-PRS resource allocation may be provided by the network. In scheme 2, the UE defines the SL-PRS transmission resources in the resource pool(s).

[0162] Scheme 1 may be characterized by the UE needing to be in the RRC CONNECTED state in order to transmit SL-PRS. Scheme 1 may be characterized by the NG-RAN scheduling the transmission resources. Scheme 2 may be characterized by the UE transmitting SL- PRS when inside NG-RAN coverage, irrespective of which RRC state the UE is in, and when outside NG-RAN coverage, the UE autonomously selecting transmission resources from the resource pool(s).

[0163] The SL-RTT positioning method makes use of SL Rx-Tx time difference measurements performed by a pair of UEs (e.g., target UE and anchor UE). Both UEs measure the Rx- Tx time difference using the SL-PRS transmitted / received by the pair of UEs. The SL Rx-Tx time difference measurements performed by a pair of UEs defines the RTT between the UEs, which may be converted into a range estimate between the pair of UEs. For SL-RTT, the pair of UEs may transmit and receive SL-PRS once (also referred to as “single-sided RTT”) or multiple times (also referred to as “double-sided RTT”). A UE may report multiple SL Rx-Tx time difference measurements for the same SL-PRSQC2500147WOQualcomm Ref. No. 2500147WO47 / 94transmission and up to four different SL-PRS receptions, or report multiple SL Rx-Tx time difference measurements for the same SL-PRS reception and up to four different SL-PRS transmissions, or both.

[0164] Assistance data may be transferred between endpoints. The assistance data may include an application layer ID, identifying a UE for which the assistance data are applicable. The assistance data may include an SL-PRS Sequence ID. The assistance data may include anchor UE location coordinates. The assistance data may include SL-PRS Tx ARP location coordinates. The assistance data may include SL-PRS Tx information (e.g., SL- PRS Priority, SL-PRS Delay Budget, SL-PRS Bandwidth, SL-PRS Periodicity, and SL- PRS Tx trigger indication). The assistance data may include association information between the SL-PRS Tx ARP-ID and the already transmitted SL-PRS resources.

[0165] Location request information that may be transferred between endpoints. The location request information may include requested location information type (e.g., location estimate, location measurements, range estimate, and / or range measurements). The location request information may include periodic reporting criteria (e.g., amount of reports and the reporting interval). The location request information may include positioning QoS (e.g., desired horizontal and vertical accuracy, desired range accuracy, response time, and / or velocity request). The location request information may include environment information (e.g., expected multipath and non-line-of-sight (NLOS) in the current area). The location request information may include scheduled location time. The location request information may include requested measurement information (e.g., ARP Information Request, LOS-NLOS Indicator Request, SL-PRS-RSRP Request, SL-PRS- RSRPP Request, additional paths request, Tx time info request, multiple SL-PRS Rx-Tx time differences request, measurements for multiple ARP-IDs Request, and / or associated SL-PRS Tx time stamp request).

[0166] Location result information may be transferred between endpoints. The location result information may include a location estimate. The location result information may include a range estimate. The location result information may include a velocity estimate. The location result information may include SL-RTT measurement information (e.g., an application layer ID of the peer UE from which the measurements were made, an LOS- NLOS indicator, an SL-PRS Rx ARP ID, and / or a measurement result list. The measurement result list may include an SL-PRS resource ID, an SL-PRS Rx-Tx time difference measurement, an SL-PRS-RSRP measurement, SL-PRS-RSRPPQC2500147WOQualcomm Ref. No. 2500147WO48 / 94measurements, an additional paths measurement, a time stamp of measurements, a trimming quality of measurement, and / or SL-PRS Tx time information.

[0167] The measurement result list may be provided up to four times. The measurement result list may include multiple Rx-Tx time difference measurements for the same SL-PRS transmission and up to four different SL-PRS receptions. The measurement result list may include multiple Rx-Tx time difference measurements for the same SL-PRS reception and up to four different SL-PRS transmissions, or a combination of both.

[0168] Sidelink relative time of arrival (TSL-RTOA), applicable for sidelink, may be defined as the beginning time of SL subframe #i containing SL-PRS received from a UE, relative to the relative time of arrival (RTOA) reference time. The SL-RTOA reference time is defined as To + tsL-PRS, where To is the nominal beginning time of SFN 0 or DFN 0, provided by SFN and DFN initialization time, respectively, and tsL-PRS = (10zz / + nsf) x 10'3, where nf and / / / are the SFN or DFN and the subframe number of the SL-PRS, respectively. For frequency range 1 (FR1), the reference point for TSL-RTOA measurement may be the Rx antenna connector of the UE. For frequency range 2 (FR2), the reference point for TSL-RTOA measurement may be the Rx antenna of the UE.

[0169] Sidelink reference signal time difference (SL-RSTD), applicable for sidelink, may be defined as the SL relative timing difference between the UE j and the reference UE z, defined as 7 si. -Rs - ESL-RX;, where ESL-RX; is the time when the UE receives the start of one subframe from UE j, and ESL-RXI is the time when the UE receives the corresponding start of one subframe from UE z that is closest in time to the subframe received from UE j. For FR1, the reference point for SL RSTD measurement may be the Rx antenna connector of the UE. For FR2, the reference point for SL RSTD measurement may be the Rx antenna of the UE.

[0170] Sidelink Rx-Tx time difference, applicable for sidelink, may be defined as TUE-RX-TUE- TX, where TUE-RX is the UE received timing of sidelink subframe #i from a transmitting UE, defined by the first detected path in time. If the UE reports the transmission timestamp of a SL PRS, TUE-TX may be the transmit timing of the sidelink subframe #j of the SL PRS of the UE. Otherwise, TUE -TX may be the transmit timing of the UE of sidelink subframe #j that is closest in time to the subframe #i received from the transmitting UE. The same antenna reference point may be used for receiver and transmitter for the Rx-Tx time difference measurement. If the UE reports the transmission timestamp of a SL PRS, the SL Rx-Tx time difference may be modulo wrapped around to result in values betweenQC2500147WOQualcomm Ref. No. 2500147WO49 / 94-0.5 milliseconds to +0.5 milliseconds. For FR1, the reference point for TUE-RX measurement may be the Rx antenna connector of the UE and the reference point for TUE- TX measurement may be the Tx antenna connector of the UE. For FR2, the reference point for TUE-RX measurement may be the Rx antenna of the UE and the reference point for TUE- TX measurement may be the Tx antenna of the UE.

[0171] FIGS. 8A, 8B, and 8C illustrate examples of non-terrestrial networks (NTNs) and air-to- ground (ATG) networks.

[0172] FIGS. 8A and 8B illustrate example NTN scenarios, according to aspects of the disclosure. In FIG. 8A and / or FIG. 8B are a UE 810, a satellite 820, a satellite 830, a gateway 840, and / or a data network 850. UE 810 may be in a field of view of satellite 820. The field of view may comprise one or more beam footprints. The satellites may be, for example, uncrewed aerial system (UAS) platforms. There may be a service link 812 between UE 810 and satellite 820, an inter-satellite link 823 between satellite 820 and satellite 830, a feeder link 824 between satellite 820 and gateway 840, a feeder link 834 between satellite 830 and gateway 840, and / or a gateway to data network link 845 between gateway 840 and data network 850. In an example, feeder link 824 may be mandatory if there is no inter-satellite link 823.

[0173] FIG. 8A illustrates a scenario associated with a transparent payload. A transparent payload may be associated with radio frequency filtering, frequency conversion, and / or amplification. A waveform signal repeated by the payload may be unchanged.

[0174] FIG. 8B illustrates a scenario associated with a regenerative payload. A regenerative payload may be associated with radio frequency filtering, frequency conversion, and / or amplification, as well as demodulation / decoding, switching and / or routing, and / or coding / modulation. In effect, the regenerative payload scenario may be equivalent to having all or part of the functions of a base station (e.g., a gNB) on board the satellite (or UAS platform).

[0175] Different platforms may have different altitude ranges, orbits, and beam footprint sizes.Low earth orbit (LEO) satellites may operate at an altitude range of 300 to 1500 km. They may have circular orbits around the earth and a beam footprint size of 100 to 1000 km. medium earth orbit (MEO) satellites may operate at an altitude range of 7000 to 25000 km. They may have circular orbits around the Earth, with a beam footprint size of 100 to 1000 km. Geostationary equatorial orbit (GEO) satellites may operate at an altitude of 35,786 km. They may maintain a notional station-keeping position fixed in terms ofQC2500147WOQualcomm Ref. No. 2500147WO50 / 94elevation and azimuth relative to a given earth point, with a beam footprint size of 200 to 3500 km. UAS platforms, including high-altitude platform systems (HAPS), may operate at altitudes ranging from 8 to 50 km (e.g., 20 km for HAPS). UAS platforms may have beam footprint sizes ranging from 5 to 200 km. High elliptical orbit (HEO) satellites may operate at altitudes ranging from 400 to 50,000 km. They may have elliptical orbits around the earth and a beam footprint size of 200 to 3500 km.

[0176] Various NTN scenarios may be associated with various characteristics, as described in the following examples.

[0177] In a GEO transparent payload scenario (e.g., scenario GEO A), a satellite altitude may be 35786 km, a relative speed of satellite with respect to earth may be negligible, a minimum elevation for both feeder and service links may be 10 degrees, typical minimum / maximum NTN beam footprint diameters may be 100 km / 3500 km, maximum propagation delay contribution to the round trip delay on the radio interface between the gNB and the UE may be 541.46 milliseconds (e.g., in a worst case), minimum propagation delay contribution to the round trip delay on the radio interface between the gNB and the UE may be 477.48 milliseconds, and maximum round trip delay variation as seen by the UE may be negligible.

[0178] In a GEO regenerative payload scenario (e.g., scenario GEO B), a satellite altitude may be 35786 km, a relative speed of satellite with respect to earth may be negligible, a minimum elevation for both feeder and service links may be 10 degrees, typical minimum / maximum NTN beam footprint diameters may be 100 km / 3500 km, maximum propagation delay contribution to the round trip delay on the radio interface between the gNB and the UE may be 270.73 milliseconds, minimum propagation delay contribution to the round trip delay on the radio interface between the gNB and the UE may be 238.74 milliseconds, and maximum round trip delay variation as seen by the UE may be negligible.

[0179] In a LEO transparent payload scenario (e.g., scenario LEO Cl and / or LEO C2), a satellite altitude may be 600 km, a relative speed of satellite with respect to earth may be 7.56 km per second, a minimum elevation for both feeder and service links may be 10 degrees, typical minimum / maximum NTN beam footprint diameters may be 50 km / 1000 km, maximum propagation delay contribution to the round trip delay on the radio interface between the gNB and the UE may be 25.77 milliseconds, minimum propagation delay contribution to the round trip delay on the radio interface between the gNB and the UEQC2500147WOQualcomm Ref. No. 2500147WO51 / 94may be 8 milliseconds, and maximum round trip delay variation as seen by the UE may be up to + / - 93.0 microseconds per second (e.g., in a worst case).

[0180] In a LEO regenerative payload scenario (e.g., scenario LEO DI and / or LEO D2), a satellite altitude may be 600 km, a relative speed of satellite with respect to earth may be 7.56 km per second, a minimum elevation for both feeder and service links may be 10 degrees, typical minimum / maximum NTN beam footprint diameters may be 50 km / 1000 km, maximum propagation delay contribution to the round trip delay on the radio interface between the gNB and the UE may be 12.89 milliseconds, minimum propagation delay contribution to the round trip delay on the radio interface between the gNB and the UE may be 4 milliseconds, and maximum round trip delay variation as seen by the UE may be up to + / - 47.6 microseconds per second.

[0181] A beam footprint diameter may depend on orbit, earth latitude, antenna design, and / or radio resource management strategy in a given system. Delay variation may measure how fast the round trip delay (e.g., a function of UE-satellite-NTN gateway distance) varies over time. In an example, a worst case is when the satellite moves towards / away from the UE at a ten degree elevation angle, assuming the UE speed is 1200 km / h. It is expressed in microseconds per second (ps / s) and may be negligible in a GEO scenario. The speed of light for delay calculation may be 299792458 meters per second (m / s).

[0182] For terrestrial networks, propagation delay may be on the order of microseconds. For GEO A, a propagation difference may be equal to 65 milliseconds (i.e., 542 milliseconds minus 477 milliseconds). For GEO B, a propagation difference may be equal to 32 milliseconds (i.e., 270 milliseconds minus 238 milliseconds). For LEO A, a propagation difference may be equal to 17 milliseconds (i.e., 25 milliseconds minus 8 milliseconds). For GEO B, a propagation difference may be equal to 7 milliseconds (i.e., 13 milliseconds minus 4 milliseconds).

[0183] In an example, a UE may be served by a LEO satellite SI, and also within a coverage of an incoming LEO satellite S2. The UE may perform measurements of neighboring cells originating from LEO satellite S2 for mobility purposes based on a measurement configuration provided to the UE. However, a propagation delay difference from the UE to LEO satellite Si and the UE to LEO satellite S2 may vary significantly. If an SSB- based measurement timing configuration (SMTC) measurement gap configuration does not consider the propagation delay difference, the UE may miss the SSB / CSI-RS measurement window and may be unable to perform measurements on the configuredQC2500147WOQualcomm Ref. No. 2500147WO52 / 94reference signals. This challenge may be captured for both GEO and LEO scenarios and may be addressed with priority for LEO scenarios. A same issue may arise in a positioning measurement in case expected RSTD differences are very different, and gap durations are small.

[0184] FIG. 8C illustrates an example ATG scenario, according to aspects of the disclosure. In FIG. C is a data network 850, an ATG UE 860, an ATG BS 870, and a terrestrial network 880. There may be a link 867 between ATG UE 860 and ATG BS 870, and a gateway to data network link 857 between ATG BS 870 and data network 850. An angle between an ATG BS boresight and the nearest TN BS boresight in azimuth may be 60 degrees. An isolation distance 871 may separate the ATG BS 870 from the nearest base station of terrestrial network 880.

[0185] An ATG network refers to an in-flight connectivity technique, using ground-based cell towers that send signals up to an aircraft’s antenna(s) of an onboard ATG terminal. As a plane travels into different sections of airspace, the onboard ATG terminal may automatically connect to a cell with strongest received signal power, just as a mobile phone does on the ground. In this network, a direct radio link may be established between a BS on the ground and a customer premise equipment (CPE) type of UE mounted in the aircraft.

[0186] In an example, ATG network deployment scenarios may be associated with extremely large inter-site distance (ISD) and large coverage range. In order to control network deployment costs and considering the limited number of flights, a large ISD is preferred, e.g., about 100 km to 200 km. At the same time, when the plane is above the sea, the distance between the plane and the nearest base station could be more than 200 km and even up to 300 km. Therefore, ATG networks may be able to provide up to 300 km cell coverage range.

[0187] In an example, ATG network deployment scenarios may be associated with utilization of non-disjoint frequency for deploying both ATG and terrestrial networks (e.g., a same operating band wherein the ATG network and the TN use adjacent carriers). Operators may be interested to adopt the same frequency for deploying both ATG networks and TNs to reduce frequency resource costs. Interference between ATG networks and TNs may become non-negligible and may be addressed.

[0188] In an example, ATG network deployment scenarios may be associated with powerful onboard ATG terminal capacity. On-board ATG terminals can be much more powerful thanQC2500147WOQualcomm Ref. No. 2500147WO53 / 94normal terrestrial UEs, e.g., with higher effective isotropic radiated power (EIRP) via much larger transmission power and / or much larger on-board antenna gain.

[0189] Multi-RTT (mRTT) has been used in various deployment scenarios to determine a position and / or location of a target device (e.g., a target UE). For example, as shown in FIG. 4 above, several nodes may perform an RTT procedure with the target device, and the RTT values obtained via each node may facilitate a position determination. To participate in mRTT, each node may act as a ‘two-way’ node that performs transmission and reception of one or more reference signals.

[0190] In accordance with aspects of the disclosure, consideration is given to a scenario where a ‘one-way’ node participates as a transmitter or a receiver, but not as both. For example, a network may deploy a transmission point (TP) that is capable of transmitting reference signals, but is not capable of receiving reference signals; or a reception point (RP) that is capable of receiving reference signals, but is not capable of transmission. In a nonterrestrial network (NTN), for example, a satellite may transmit, but not receive, reference signals. As another example, a UE may perform antenna tilting or antenna nulling (e.g., to enhance coverage in a partial coverage scenario, or to avoid interference), causing transmission or reception to become inaccessible. Or, a UE may be capable of receiving reference signals, but may be in a power saving state that prevents transmission of reference signals. Other deployments may be imagined in which one or more nodes are either unwilling or unable to participate in mRTT as both transmitters and receivers.

[0191] In order to perform positioning in scenarios with one or more ‘one-way’ nodes, asymmetric RTT is introduced. Generally, an RTT value may be based on a calculation involving four values (e.g., two reception timestamps and two transmission timestamps). In an asymmetric scenario (e.g., a scenario where at least one participant can not and / or does not transmit or receive reference signals), knowledge of the four values may be distributed among three or more entities. As will be discussed in greater detail below, to determine the asymmetric RTT, one entity may obtain the four distributed values (or values related thereto, such as difference values) from the three or more entities and perform an appropriate calculation.

[0192] In accordance with aspects of the disclosure, mRTT measurements and LMF assumptions for asymmetric mRTT measurements may be enhanced. For example, transmission by TRPl / gNBl / UEl and reception by TRP2 / gNB2 / UE2, or vice versa. In accordance with aspects of the disclosure, two TRPs (e.g., TRP1 and TRP2) may belong to a same gNB,QC2500147WOQualcomm Ref. No. 2500147WO54 / 94or different gNBs. In accordance with aspects of the disclosure, two UEs (e.g., UE1 and UE2) may be associated with asymmetric partial coverage. In accordance with aspects of the disclosure, mRTT measurement may be enhanced and signaling for asymmetric mRTT may be introduced. The mRTT measurement and signaling for asymmetric mRTT may apply to downlink and / or uplink mRTT, sidelink mRTT, or any combination thereof.

[0193] FIG. 9A illustrates an example of sidelink Rx-Tx time difference, according to aspects of the disclosure. The figure illustrates a UE 951 (e.g., a UE) and a UE 952 (e.g., a transmitting UE). UE 951 may transmit a reference signal 961 to UE 952. UE 952 may transmit a reference signal 962 to UE 951. The transmitting of reference signal 962 by UE 952 may be after the reception of reference signal 961 by UE 952 from UE 951.

[0194] Sidelink Rx-Tx time difference at UE 951 may be defined as TUE-RX-TUE-TX, where TUE- RX is the UE 951 received timing of sidelink subframe #i from UE 952 (e.g., reference signal 962), defined by the first detected path in time. If UE 951 reports the transmission timestamp of a SL PRS (e.g., transmission timestamp of reference signal 961), TUE-TX may be the transmit timing of the sidelink subframe #j of the SL PRS of UE 951. Otherwise, TUE-TX may be the transmit timing of UE 951 of sidelink subframe #j that is closest in time to the subframe #i received from UE 952. The same antenna reference point may be used for receiver and transmitter for the Rx-Tx time difference measurement.

[0195] If the UE reports the transmission timestamp of a SL PRS, the SL Rx-Tx time difference may be modulo wrapped around to result in values between -0.5 milliseconds to +0.5 milliseconds.

[0196] For FR1, the reference point for TUE-RX measurement may be the Rx antenna connector of the UE and the reference point for TUE-TX measurement may be the Tx antenna connector of the UE. For FR2, the reference point for TUE-RX measurement may be the Rx antenna of the UE and the reference point for TUE-TX measurement may be the Tx antenna of the UE.

[0197] FIG. 9B illustrates an example of cross-UE sidelink Rx-Tx time difference, according to aspects of the disclosure. The figure illustrates a UE 981 (e.g., a first UE), a UE 982 (e.g., a transmitting second UE), and a UE 983 (e.g., a third UE). UE 983 may transmit a reference signal 991 to UE 982. UE 982 may transmit a reference signal 992 to UE 981. The transmitting of reference signal 992 by UE 982 may be after the reception of reference signal 991 by UE 982 from UE 983.QC2500147WOQualcomm Ref. No. 2500147WO55 / 94

[0198] Cross-UE sidelink Rx-Tx time difference at UE 981 may be defined as TUE-RX-TUE-TX, where TUE-RX is the UE 981 received timing of sidelink subframe #i from UE 982 (e.g., receive timing of reference signal 992), defined by the first detected path in time. If UE 981 reports the transmission timestamp of a SL PRS (e.g., transmission timestamp of reference signal 991), TUE-TX may be the transmit timing of the sidelink subframe #j of the SL PRS of UE 983. Otherwise, TUE-TX may be the transmit timing of UE 983 of sidelink subframe #j that is closest in time to the subframe #i received from UE 982.

[0199] If UE 981 reports the transmission timestamp of a SL PRS, the SL Rx-Tx time difference may be modulo wrapped around to result in values between -0.5 milliseconds to +0.5 milliseconds.

[0200] For FR1, the reference point for TUE-RX measurement may be the Rx antenna connector of UE 981 and the reference point for TUE-TX measurement may be the Tx antenna connector of UE 983. For FR2, the reference point for TUE-RX measurement may be the Rx antenna of UE 981 and the reference point for TUE-TX measurement may be the Tx antenna of UE 983.

[0201] FIGS. 10A- 10B illustrate examples of timing measurements that may be related to sidelink-based asymmetric RTT. In the illustrated examples are a UE 1001, a UE 1002, and a UE 1003. UE 1001 and UE 1003 may be anchor UEs. UE 1002 may be a target UE (e.g., a target object of a positioning procedure). One or more timing measurements by UE 1001, UE 1002, and / or UE 1003 may facilitate determination of an asymmetric RTT value and / or one or more components thereof. In an example, the asymmetric RTT value and / or the one or more components thereof may be combined with one or more other values (e.g., other asymmetric RTT values) to determine a location of UE 1002. In an example, the asymmetric RTT value and / or the one or more components may be reported to another entity (e.g., a base station or location server) to determine a location of UE 1002.

[0202] As shown in FIG. 10 A, UE 1003 may transmit a reference signal 1011 at a cross-UE transmit time Tcross-Tx. The reference signal 1011 transmitted by UE 1003 may be received by UE 1002 at a receive time TRX. A propagation time of the reference signal 1011 (e.g., as transmitted by UE 1003 and received by UE 1002) may be equal to a difference between the receive time TRXand the cross-UE transmit time Tcross-TX(e.g., TRX-Tcross-TX).

[0203] UE 1002 may transmit a reference signal 1012 at a transmit time TTX. The transmitting by UE 1002 of reference signal 1012 (at TTX) may be based on, in response to, and / orQC2500147WOQualcomm Ref. No. 2500147WO56 / 94triggered by the receiving by UE 1002 of reference signal 1011 (at TRX). Additionally or alternatively, the transmitting by UE 1002 of reference signal 1012 may be based on a configuration (e.g., a timing configuration) by a network (e.g., by an LMF, location server, and / or base station). Between the receiving of reference signal 1011 and the transmitting of reference signal 1012 is a time difference 1021 (e.g., a UE Tx-Rx time difference).

[0204] The reference signal 1012 transmitted by UE 1002 may be received by UE 1001 at a cross-UE receive time Tcross-Rx. A propagation time of the reference signal 1012 (e.g., as transmitted by UE 1002 and received by UE 1001) may be equal to a difference between the cross-UE receive time Tcross-Rx and the transmit time TTX(e.g., Tcross-Rx - TTX).

[0205] The receiving by UE 1001 of reference signal 1012 (at Tcross-Rx) may be after the transmitting by UE 1003 of reference signal 1011 (at Tcross-Tx). Between the transmitting of reference signal 1011 and the receiving of reference signal 1012 is a time difference 1022 (e.g., a cross-UE Rx-Tx time difference).

[0206] The reference signal 1011 and / or the reference signal 1012 may be any appropriate signal, for example, a downlink reference signal, an uplink reference signal, a sidelink reference signal, a positioning reference signals (PRS), a sidelink PRS (SL PRS), a sounding reference signal (SRS), a reference signal for positioning (RS-P), or any combination thereof. For example, reference signal 1011 transmitted by UE 1003 may be a SL PRS and reference signal 1012 transmitted by UE 1102 may be a SL PRS.

[0207] In an example, an asymmetric RTT may be expressed as the sum of the propagation time of reference signal 1011 and the propagation time of reference signal 1012 (e.g., [TRX- Tcross-Tx] + [Tcross-Rx—TTX]). In another example, the asymmetric RTT may be expressed as the time difference 1022 minus the time difference 1021 (e.g., [Tcross-Rx—Tcross-Tx]—[TTX- TRX]).

[0208] In accordance with aspects of the disclosure, an entity (e.g., UE 1001, UE 1002, UE 1003, LMF, location server, base station, or any other suitable entity) may determine and / or obtain two or more values used to determine the propagation time of reference signal 1011 (e.g., Tcross-Tx and TRX), the propagation time of reference signal 1012 (e.g., TTXand Tcross-Rx), the time difference 1021 (e.g., TRXand TTX), the time difference 1022 (e.g., Tcross- Tx and Tcross-Rx), or any combination thereof.

[0209] In accordance with aspects of the disclosure, an entity (e.g., UE 1001, UE 1002, UE 1003, LMF, location server, base station, or any other suitable entity) may determine and / orQC2500147WOQualcomm Ref. No. 2500147WO57 / 94obtain two or more values used to determine the asymmetric RTT. The two or more values may include the propagation time of reference signal 1011, the propagation time of reference signal 1012, the time difference 1021, the time difference 1022, or any of the components thereof (e.g., one or more of Tcross-Tx, TRX, TTX, and TCTOSS-RX).

[0210] The values may be determined and / or obtained directly or indirectly. For example, if a first entity transmits or receives a reference signal, then the first entity may (directly) observe and / or record the transmission or reception timing. As another example, a second entity may transmit or receive a reference signal at a particular transmission or reception timing, and communicate a transmission timestamp or reception timestamp to the first entity. The timestamp may be communicated, for example, in a message and / or via a communication link.

[0211] In FIG. 10A, there is a communication link 1031 between UE 1001 and UE 1003, a communication link 1032 between UE 1001 and UE 1002, and a communication link 1033 between UE 1002 andUE 1003. The communication links may be configured and / or used to transmit a timestamp, receive a timestamp, or both. The communication links may be associated with direct sidelink communications, indirect sidelink communications (e.g., via a relay UE), or any other suitable communication method (e.g., uplink and downlink by an LMF, location server, and / or base station).

[0212] Several examples follow, but it will be understood that in general, an RTT value may be determined based on four values (e.g., timestamps). In an asymmetric scenario (e.g., a scenario where at least one participant does not transmit or receive a reference signal), the four values may be distributed among three or more entities (e.g., UE 1001, UE 1002, and UE 1003). To determine the asymmetric RTT, one entity may obtain the four distributed values (or values related thereto, such as the time difference 1021 and the time difference 1022) from the three or more entities and perform an appropriate calculation.

[0213] As a first example, UE 1001 may receive reference signal 1012 at reception time Tcross- RX. Because UE 1001 is the receiver of reference signal 1012, UE 1001 may determine reception time TCTOSS-RX based on, for example, direct observation. In accordance with aspects of the disclosure, the UE 1001 may use TCTOSS-RX to determine the time difference 1022, the propagation time of reference signal 1012, the asymmetric RTT, or any combination thereof, as will be discussed in greater detail below.

[0214] In accordance with a first variation of the first example, UE 1001 may receive, from UE 1003 (e.g., via communication link 1031), a timestamp indicating a transmission timeQC2500147WOQualcomm Ref. No. 2500147WO58 / 94Tcross-Tx associated with transmission of reference signal 1011. Because UE 1003 is the transmitter of reference signal 1011, UE 1003 may determine transmission time TCTOSS-TX based on, for example, direct observation. Based on TCTOSS-RX (e.g., directly observed by UE 1001) and TCTOSS-TX (e.g., communicated to UE 1001 by UE 1003), UE 1001 may determine the time difference 1022 based on a difference between Tcross-Rx and TCTOSS-TX. UE 1001 may report the time difference 1022 to another entity (e.g., UE 1002, UE 1003, a base station, a location server, or any other entity). Additionally or alternatively, UE 1001 may use the time difference 1022 to determine an asymmetric RTT.

[0215] In accordance with a second variation of the first example, UE 1001 may receive, from UE 1002 (e.g., via communication link 1032), a timestamp indicating a transmission time TTX associated with transmission of reference signal 1012. Because UE 1002 is the transmitter of reference signal 1012, UE 1002 may determine transmission time Tixbased on, for example, direct observation. Based on TCTOSS-RX (e.g., directly observed by UE 1001) and TTX(e.g., communicated to UE 1001 by UE 1002), UE 1001 may determine a propagation time of reference signal 1012 based on a difference between Tcross-Rx and TTX. UE 1001 may report the propagation time of reference signal 1012 to another entity (e.g., UE 1002, UE 1003, a base station, a location server, or any other entity). Additionally or alternatively, UE 1001 may use the propagation time of reference signal 1012 to determine the asymmetric RTT.

[0216] As noted above, UE 1001 may determine the time difference 1022 (as in the first variation) or the propagation time of reference signal 1012 (as in the second variation). To determine the asymmetric RTT, UE 1001 may further determine the time difference 1021 or the propagation time of reference signal 1011 via communication with UE 1002, UE 1003, or both (e.g., by receiving timestamps or indications of time differences via communication link 1031 and / or communication link 1032). UE 1001 may determine an asymmetric RTT based on the time difference 1021 and the time difference 1022. Additionally or alternatively, UE 1001 may determine an asymmetric RTT based on the propagation time of reference signal 1012 and the propagation time of reference signal 1011.

[0217] As a second example, UE 1002 may receive reference signal 1011 at reception time TRX and transmit reference signal 1012 at transmission time TTX. Because UE 1002 is the receiver of reference signal 1011 and the transmitter of reference signal 1012, UE 1002 may determine TRX, TTX, and / or the time difference 1021 based on, for example, directQC2500147WOQualcomm Ref. No. 2500147WO59 / 94observation. Similar to the first example, one or more other values may be obtained through communication with UE 1001 and / or UE 1003. UE 1002 may use TRX, TTX, and / or the time difference 1021 in combination with the one or more other values to determine the time difference 1022, the propagation time of reference signal 1011, the propagation time of reference signal 1012, the asymmetric RTT, or any combination thereof. UE 1002 may report any or all of the aforementioned values to another entity (e.g., UE 1001, UE 1003, a base station, a location server, or any other entity).

[0218] As a third example, UE 1003 may transmit reference signal 1011 at transmission time Tcross-Tx. Because UE 1003 is the transmitter of reference signal 1011, UE 1003 may determine Tcross-Tx based on, for example, direct observation. Similar to the first and second examples, one or more other values may be obtained through communication with UE 1001 and / or UE 1002. UE 1001 may use Tcross-Tx in combination with the one or more other values to determine the propagation time of reference signal 1011, the propagation time of reference signal 1012, the time difference 1021, the time difference 1022, the asymmetric RTT, or any combination thereof. UE 1003 may report any or all of the aforementioned values to another entity (e.g., UE 1001, UE 1002, a base station, a location server, or any other entity).

[0219] In the foregoing examples, timestamps are sent and / or received via one or more of communication link 1031, communication link 1032, and / or communication link 1033. However, it will be understood that one or more timestamps may be encoded in a reference signal such as reference signal 1011 and / or reference signal 1012, and thereby communicated to other mRTT participants. For example, UE 1003 may encode the Tcross- Tx transmission timestamp into reference signal 1011; UE 1002 may encode the received Tcross-Tx transmission timestamp, the TRXreception timestamp, the TTXtransmission timestamp, or any combination thereof, into reference signal 1012.

[0220] FIG. 10B illustrates another approach for performing timing measurements that may be related to sidelink-based asymmetric RTT. Similar to FIG. 10 A, FIG. 10B illustrates UE 1001, UE 1002, UE 1003, with communication link 1031, communication link 1032, and communication link 1033 therebetween.

[0221] In FIG. 10B, a reference signal 1051 and a reference signal 1052 may differ in some respects from the reference signal 1011 and reference signal 1012 described previously with respect to FIG. 10 A.QC2500147WOQualcomm Ref. No. 2500147WO60 / 94

[0222] UE 1002 may transmit reference signal 1051 at a transmit time TTX. UE 1003 may receive reference signal 1051 at receive time TCTOSS-RX. UE 1001 may transmit reference signal 1052 at transmit time Tcross-Tx. UE 1002 may receive reference signal 1052 at a receive time TRX. The transmitting by UE 1001 of reference signal 1052 (at TTX) may be based on, in response to, and / or triggered by the receiving by UE 1003 of reference signal 1051 (at TRX). For example, the transmitting by UE 1001 of reference signal 1052 (at TTX) may be based on, in response to, and / or triggered by obtaining a reception timestamp (e.g., via communication link 1031) indicating a reception timing of reference signal 1051 (at TRX). Additionally or alternatively, the transmitting by UE 1002 of reference signal 1012 may be based on a configuration (e.g., a timing configuration) by a network (e.g., by an LMF, location server, and / or base station).

[0223] Similar to FIG. 10A, any entity that calculates, determines, and / or obtains TRXand TTX, either by direct observation, communication via the communication links, or any combination thereof, may determine the time difference 1061. Additionally or alternatively, any entity that calculates, determines, and / or obtains TCross-Rx and TCTOSS-TX may determine the time difference 1062. Additionally or alternatively, any entity that calculates, determines, and / or obtains Tcross-Tx and TRXmay determine the propagation time of reference signal 1051. Additionally or alternatively, any entity that calculates, determines, and / or obtains TTXand Tcross-Rx may determine the propagation time of reference signal 1052.

[0224] Similar to FIG. 10A, any entity that calculates, determines, and / or obtains the time difference 1061 and the time difference 1062, either by direct observation, communication via the communication links, or any combination thereof, may determine the asymmetric RTT. Additionally or alternatively, any entity that calculates, determines, and / or obtains the propagation time of reference signal 1051 and the propagation time of reference signal 1052 may determine the asymmetric RTT.

[0225] FIGS. 11 A - 1 IB illustrate examples of sidelink reception time difference measurements, according to aspects of the disclosure. The figures illustrate a UE 1103 (e.g., a serving anchor UE), a UE 1102 (e.g., a UE), a UE 1101 (e.g., a first neighboring anchor UE), and a UE 1104 (e.g., a second neighboring anchor UE).

[0226] UE 1103 may transmit a first reference signal (e.g., a first SL PRS). The first reference signal may be received by one or more UEs, including for example UE 1102, UE 1101, and UE 1104. The first reference signal may be received as a reference signal 1112 byQC2500147WOQualcomm Ref. No. 2500147WO61 / 94UE 1102, as a reference signal 1113 by UE 1101, and as a reference signal 1114 by UE 1104. If the distances from UE 1103 to UE 1102, UE 1101, and UE 1104 are different, then the propagation times of reference signal 1112, reference signal 1113 and reference signal 1114 may be different.

[0227] One or more of the UEs that receive the first reference signal (e.g., UE 1102 in the illustrated example) may transmit a second reference signal (e.g., a second SL PRS). Between the reception by UE 1102 of the reference signal 1112 and the transmission of the second reference signal is a time difference 1132. The time difference 1132 may be reported in a UE measurement report TUE_RX->TX.

[0228] The second reference signal may be received by one or more UEs, including for example UE 1103, UE 1101, and UE 1104. The second reference signal may be received as a reference signal 1121 by UE 1103, as a reference signal 1123 by UE 1101, and as a reference signal 1124 by UE 1104. If the distances from UE 1102 to UE 1103, UE 1101, and UE 1104 are different, then the propagation times of reference signal 1121, reference signal 1123 and reference signal 1124 may be different.

[0229] Between the transmission by UE 1103 of the first reference signal (e.g., reference signal 1112) and the reception of the reference signal 1121 is a time difference 1131. The time difference 1131 may be equal to a propagation time of reference signal 1112 (e.g., Tprop, serving UE^UE ), plus time difference 1132, plus a propagation time of reference signal 1121 (e.g., Tprop.uE^serving UE). The time difference 1131 may be reported in a serving UE report TUE_RX->TX.

[0230] Between the reception by UE 1101 of the reference signal 1113 and the reception of the reference signal 1123 is a time difference 1133. The reference signal 1113 may have a propagation time (e.g., TprOp, serving _uE^Neighboring_UEi). The time difference 1133 may be reported in a UE 1 measurement report TNeighboring_UEi_Rx _i ^Neighboring _UEI_RX _2.

[0231] Between the reception by UE 1104 of the reference signal 1114 and the reception of the reference signal 1124 is a time difference 1134. The reference signal 1114 may have a propagation time (e.g., TprOp, serving UE^NeighboringUE2). The time difference 1134 may be reported in a UE 2 measurement report TNeighboringUE2 Rx ^Neighboring UE2 Rx 2.

[0232] In accordance with aspects of the disclosure, a sidelink cross-UE Rx-Rx time difference measurement may be reported. A first reception time may correspond to path time of reference signal reception by a first UE (e.g., reception of reference signal 1113 by UE 1101), which is transmitted by a third UE (e.g., UE 1103) and received by the first UEQC2500147WOQualcomm Ref. No. 2500147WO62 / 94and a second UE (e.g., reception of reference signal reference signal 1112 by UE 1102). A second reception time may correspond to a path time of reference signal reception by the first UE, which is transmitted by the second UE (e.g., UE 1102) and received (e.g., only received) by the first UE (e.g., reception of reference signal 1123 by UE 1101). In an example, the second transmission (e.g., of reference signal 1123 by UE 1102) may not be synchronized with the first transmission (e.g., of reference signal 1113 by UE 1101). In an example, there is a processing time between the first SL reference signal transmission from the third UE (e.g., UE 1103) and the second reference signal transmission from the second UE (e.g., UE 1102).

[0233] In an example, a sidelink Rx-Rx time difference at the first UE (e.g., UE 1101) is defined as TUE2-RX - TUE3-RX, where TUE2-RX is the first UE received timing of sidelink subframe #i from a transmitting second UE (e.g., UE 1102), defined by the first detected path in time, and TUE3-RX is the first UE received timing of sidelink subframe #j from a third UE (e.g., UE 1103), defined by the first detected path in time. If the first UE reports the transmission timestamp of a SL PRS, the SL Rx-Rx time difference may be modulo wrapped around to result in values between -0.5 ms to +0.5 ms.

[0234] For frequency range 1 (FR1), the reference point for TUE2-RX measurement may be the Rx antenna connector of the first UE and the reference point for TUE3-RX measurement may be the Rx antenna connector of the first UE. For frequency range 2 (FR2), the reference point for TUE2-RX measurement may be the Rx antenna of the first UE and the reference point for TUE3-RX measurement may be the Rx antenna of the first UE.

[0235] A UE may be requested and / or configured to report measurements to an LMF and / or location service. In an example, a UE may report a transmission time of a TP-only UE and / or a reception time (e.g., SL RTOA) of an RP-only TRP. The UE may report an antenna reference point (ARP) identifier for one or more ARPs involved in the RTT measurements. The UE may report ARP identifiers for one or more TP-only ARPs (e.g., indicating that the identified ARPs are TP-only) and for one or more RP-only ARPs (e.g., indicating that the identified ARPs are RP-only). The LMF and / or location server may determine a sidelink Rx-Tx time difference based on the reports. The LMF and / or location server may determine a sidelink Rx-Rx time difference based on the reports. If a UE reports a cross-UE SL Rx-Tx time difference, the UE may provide a flag to indicate that a measurement is a cross-UE measurements, one or more identifiers of one or moreQC2500147WOQualcomm Ref. No. 2500147WO63 / 94involved UEs and / or one or more involved ARPs, one or more indications of whether a UE / ARP is transmit-only or receive-only, or any combination thereof.

[0236] In sidelink-based asymmetric RTT, UEs (e.g., an anchor reporting UE and one or more other neighboring anchor UEs) may signal with one another. In an example, a first UE may report a reference signal transmission time to a second UE and the second UE may determine the cross-UE Rx-Tx time difference. In an example, a first UE may report a reference signal reception time (e.g., SL RTOA) to a second UE and the second UE may determine the cross-UE Rx-Tx time difference. In an example, a first UE may determine a first reference signal reception time (e.g., SL RTOA), wherein the reference signal is sent from a second UE, and a second reference signal reception time, wherein the reference signal is sent from a third UE to the second UE. The first UE may determine the cross-UE Rx-Tx time difference and report the cross-UE Rx-Tx time difference to the second UE or third UE. The first UE may report the first reference signal reception time and the second reference signal reception time to the second UE or third UE, and the second UE or third UE may determine the cross-UE Rx-Tx time difference.

[0237] Reporting may be associated with a granularity factor. In an example, if a UE is requested to provide measurements of transmission time, reception time, gNB-cross-TRP Rx-Rx time difference, and / or gNB-cross-TRP Rx-Tx time difference with a timing granularity factor, the timing granularity factor may be taken into account when configuring measurements.

[0238] Asymmetric RTT measurements may involve one or more ARP Rx timing error groups (TEGs). In an example, if a UE is requested to provide measurements of reception time, gNB-cross-TRP Rx-Rx time difference, and / or gNB-cross-TRP Rx-Tx time difference with a number of ARP Rx TEGs (e.g., N ARP Rx TEGs), it may, if supported, use the N ARP Rx TEGs to measure a same resource (e.g., SL-PRS resource) with different RX TEGs for a UE / ARP indicated as RP-only, and report the corresponding measurements. The request may indicate the number of TEGs (N) to consider when obtaining measurements.

[0239] Asymmetric RTT measurements may involve one or more ARP Tx TEGs. In an example, if a UE is requested to provide measurements of transmission time with a number of Tx TEGs (e.g., M ARP Tx TEGs), it may, if supported, use the M ARP Tx TEGs to indicate a transmission time of a same resource (e.g., SL-PRS resource) with different transmission TEGs for a UE / ARP indicated as TP-only, and report the correspondingQC2500147WOQualcomm Ref. No. 2500147WO64 / 94measurements. The number of ARP Tx TEGs (M) may be indicated in the request message.

[0240] Asymmetric RTT measurements may involve one or more TRP Rx-Tx TEGs or TRP Rx- Rx TEGs. In an example, if a UE is requested to provide measurements of a gNB-cross- TRP Rx-Tx time difference or a gNB-cross-TRP Rx-Rx time difference with a number of Rx-Tx TEGs or a number of Rx-Rx TEGs, it may, if supported, use the number of Rx- Tx TEGs or the number of Rx-Rx TEGs to measure a same resource (e.g., SL-PRS resource) with different Rx-Tx TEGs or Rx-Rx TEGs for a UE / ARP indicated as RP- only, and report the corresponding measurements. The number of Rx-Tx TEGs and / or the number of Rx-Rx TEGs may be indicated in the request message.

[0241] A UE may indicate one or more capabilities to an LMF and / or location server (e.g., upon request by the LMF and / or location server). The UE may indicate support for an asymmetric RTT method, support for asymmetric RTT measurements, support for coordination with other UEs for cross-UE asymmetric RTT methods and / or measurements, a list of UEs that support cross-UE asymmetric RTT methods and / or measurements (e.g., if supported), or any combination thereof.

[0242] An LMF and / or location server may request asymmetric measurement from a UE. The request may indicate, for example, one or more asymmetric measurements to be obtained, one or more ARP identifiers or UE identifiers of one or more ARPs / UEs to be involved in the one or more asymmetric measurements, one or more gNB identifiers of one or more gNBs to be involved in the one or more asymmetric measurements, or any combination thereof. The UE may report the requested measurements.

[0243] FIGS. 12A- 12B illustrate examples of timing measurements that may be related to sidelink-based asymmetric RTT. In the illustrated examples are a TRP 1201, a UE 1202, and a TRP 1203. TRP 1201 and TRP 1203 may be anchor UEs. UE 1202 may be a target UE (e.g., a target object of a positioning procedure). The TRP 1201 and / or TRP 1203 may be part of a terrestrial network (TN) or a non-terrestrial network (NTN). For example, TRP 1201 and TRP 1203 may be transmit-only and receive-only, respectively (e.g., TRP 1203 may be a satellite in an NTN and TRP 1201 may be an RP in a TN). Although TRP 1201 and TRP 1203 are described as TRPs, it will be understood that these are merely illustrations, and that one or more of TRP 1201 and TRP 1203 may be implemented as a base station (e.g., gNB) or any other device capable of transmitting or receiving a reference signal.QC2500147WOQualcomm Ref. No. 2500147WO65 / 94

[0244] One or more timing measurements by TRP 1201, UE 1202, and / or TRP 1203 may facilitate determination of an asymmetric RTT value and / or one or more components thereof. In an example, the asymmetric RTT value and / or the one or more components thereof may be combined with one or more other values (e.g., other asymmetric RTT values) to determine a location of UE 1202. In an example, the asymmetric RTT value and / or the one or more components may be reported to another entity (e.g., a base station or location server) to determine a location of UE 1202.

[0245] As shown in FIG. 12A, TRP 1203 may transmit a reference signal 1211 at a cross-TRP transmit time Tcross-Tx. The reference signal 1211 transmitted by TRP 1203 may be received by UE 1202 at a receive time TRX. A propagation time of the reference signal 1211 (e.g., as transmitted by TRP 1203 and received by UE 1202) may be equal to a difference between the receive time TRXand the cross-TRP transmit time Tcross-Tx (e.g., TRX-T cross-Tx) •

[0246] UE 1202 may transmit a reference signal 1212 at a transmit time TTX. The transmitting by UE 1202 of reference signal 1212 (at TTX) may be based on, in response to, and / or triggered by the receiving by UE 1202 of reference signal 1211 (at TRX). Additionally or alternatively, the transmitting by UE 1202 of reference signal 1212 may be based on a configuration (e.g., a timing configuration) by a network (e.g., by an LMF, location server, and / or base station). Between the receiving of reference signal 1211 and the transmitting of reference signal 1212 is a time difference 1221 (e.g., a UE Tx-Rx time difference).

[0247] The reference signal 1212 transmitted by UE 1202 may be received by TRP 1201 at a cross-TRP receive time TcrOss-Rx. A propagation time of the reference signal 1212 (e.g., as transmitted by UE 1202 and received by TRP 1201) may be equal to a difference between the cross-TRP receive time TCTOSS-RX and the transmit time TTX(e.g., Tcross-Rx - TTX).

[0248] The receiving by TRP 1201 of reference signal 1212 (at Tcross-Rx) may be after the transmitting by TRP 1203 of reference signal 1211 (at Tcross-Tx). Between the transmitting of reference signal 1211 and the receiving of reference signal 1212 is a time difference 1222 (e.g., a cross-TRP Rx-Tx time difference).

[0249] The reference signal 1211 and / or the reference signal 1212 may be any appropriate signal, for example, a downlink reference signal, an uplink reference signal, a sidelink reference signal, a positioning reference signals (PRS), a sidelink PRS (SL PRS), a sounding reference signal (SRS), a reference signal for positioning (RS-P), or any combinationQC2500147WOQualcomm Ref. No. 2500147WO66 / 94thereof. For example, reference signal 1211 transmitted by TRP 1203 may be a DL reference signal (e.g., PRS) and reference signal 1212 transmitted by UE 1202 may be an uplink reference signal (e.g., SRS).

[0250] Similar to FIGS. 10A-10B, an asymmetric RTT in the context of FIGS. 12A-11B may be expressed as the sum of the propagation time of reference signal 1211 and the propagation time of reference signal 1212 (e.g., [TRX- TCTOSS-TX] + [Tcross-Rx - TTX]). In another example, the asymmetric RTT may be expressed as the time difference 1222 minus the time difference 1221 (e.g., [Tcross-Rx - Tcross-Tx] - [TTX- TRX]).

[0251] In accordance with aspects of the disclosure, an entity (e.g., TRP 1201, UE 1202, TRP 1203, LMF, location server, base station, or any other suitable entity) may determine and / or obtain two or more values used to determine the propagation time of reference signal 1211 (e.g., Tcross-Tx and TRX), the propagation time of reference signal 1212 (e.g., TTX and Tcross-Rx), the time difference 1221 (e.g., TRXand TTX), the time difference 1222 (e.g., Tcross-Tx and Tcross-Rx), or any combination thereof.

[0252] In accordance with aspects of the disclosure, an entity (e.g., TRP 1201, UE 1202, TRP 1203, LMF, location server, base station, or any other suitable entity) may determine and / or obtain two or more values used to determine the asymmetric RTT. The two or more values may include the propagation time of reference signal 1211, the propagation time of reference signal 1212, the time difference 1221, the time difference 1222, or any of the components thereof (e.g., one or more of Tcross-Tx, TRX, TTX, and TCTOSS-RX).

[0253] The values may be determined and / or obtained directly or indirectly. For example, if a first entity transmits or receives a reference signal, then the first entity may (directly) observe and / or record the transmission or reception timing. As another example, a second entity may transmit or receive a reference signal at a particular transmission or reception timing, and communicate a transmission timestamp or reception timestamp to the first entity. The timestamp may be communicated, for example, in a message and / or via a communication link.

[0254] In FIG. 12A, there is a communication link 1231 between TRP 1201 and TRP 1203, a communication link 1232 between TRP 1201 and UE 1202, and a communication link 1233 between UE 1202 and TRP 1203. The communication links may be configured and / or used to transmit a timestamp, receive a timestamp, or both. The communication links may be associated with direct uplink / downlink communications, indirectQC2500147WOQualcomm Ref. No. 2500147WO67 / 94uplink / downlink communications (e.g., via a relay), or any other suitable communication method.

[0255] Similar to FIGS. 10A-10B, an RTT value in the context of FIGS. 12A-11B may be determined based on four values (e.g., timestamps). In an asymmetric scenario (e.g., a scenario where at least one participant does not transmit or receive a reference signal), the fourvalues may be distributed among three or more entities (e.g., TRP 1201, UE 1202, and TRP 1203). To determine the asymmetric RTT, one entity may obtain the four distributed values (or values related thereto, such as the time difference 1221 and the time difference 1222) from the three or more entities and perform an appropriate calculation.

[0256] Several particular examples for a particular entity to determine an RTT value were described above in the context of FIGS. 10A-10B. For brevity, the examples will not be repeated here. It will be understood that the examples of FIGS. 10A-10B may be implemented in the context of FIGS. 12A-11B by, for example, allowing TRP 1201 to stand in the place of UE 1001, allowing TRP 1203 to stand in the place of UE 1003, and by allowing the type of reference signal to vary (e.g., DL reference signal and UL reference signal rather than SL reference signal).

[0257] FIG. 12B illustrates another approach for performing timing measurements that may be related to sidelink-based asymmetric RTT. Similar to FIG. 12A, FIG. 12B illustrates TRP 1201, UE 1202, TRP 1203, with communication link 1231, communication link 1232, and communication link 1233 therebetween.

[0258] In FIG. 12B, a reference signal 1251 and a reference signal 1252 may differ in some respects from the reference signal 1211 and reference signal 1212 described previously with respect to FIG. 12 A.

[0259] UE 1202 may transmit reference signal 1251 at a transmit time TTX. TRP 1203 may receive reference signal 1251 at receive time TCTOSS-RX. TRP 1201 may transmit reference signal 1252 at transmit time TCTOSS-TX. UE 1202 may receive reference signal 1252 at a receive time TRX. The transmitting by TRP 1201 of reference signal 1252 (at TTX) may be based on, in response to, and / or triggered by the receiving by TRP 1203 of reference signal 1251 (at TRX). For example, the transmitting by TRP 1201 of reference signal 1252 (at TTX) may be based on, in response to, and / or triggered by obtaining a reception timestamp (e.g., via communication link 1231) indicating a reception timing of reference signal 1251 (at TRX). Additionally or alternatively, the transmitting by UE 1202 ofQC2500147WOQualcomm Ref. No. 2500147WO68 / 94reference signal 1212 may be based on a configuration (e.g., a timing configuration) by a network (e.g., by an LMF, location server, and / or base station).

[0260] Similar to FIG. 12A, any entity that calculates, determines, and / or obtains TRXand TTX, either by direct observation, communication via the communication links, or any combination thereof, may determine the time difference 1261. Additionally or alternatively, any entity that calculates, determines, and / or obtains TCTOSS-RX and TCTOSS-TX may determine the time difference 1262. Additionally or alternatively, any entity that calculates, determines, and / or obtains TCTOSS-TX and TRXmay determine the propagation time of reference signal 1251. Additionally or alternatively, any entity that calculates, determines, and / or obtains TTXand Tcross-Rx may determine the propagation time of reference signal 1252.

[0261] Similar to FIG. 12A, any entity that calculates, determines, and / or obtains the time difference 1261 and the time difference 1262, either by direct observation, communication via the communication links, or any combination thereof, may determine the asymmetric RTT. Additionally or alternatively, any entity that calculates, determines, and / or obtains the propagation time of reference signal 1251 and the propagation time of reference signal 1252 may determine the asymmetric RTT.

[0262] As noted above in FIG. 12A, a time difference 1222 (e.g., a cross-TRP Rx-Tx time difference) may be measured between the transmitting of reference signal 1211 by TRP 1203 and the receiving of reference signal 1212 by TRP 1201. As noted above in FIG.12B, a time difference 1262 (e.g., a cross-TRP Tx-Rx time difference) may be measured between the transmitting of reference signal 1252 by TRP 1201 and the receiving of reference signal 1251 by TRP 1203. In an example, a transmission time may correspond to a subframe timing of a transmitted reference signal (e.g., reference signal 1211 or reference signal 1252. Additionally or alternatively, a reception time may correspond to a path time of a received reference signal (e.g., SRS).

[0263] A gNB-x-TRP Rx-Tx time difference may be defined as TgNB-TRP2-RX - TgNB-TRPi-rx where TgNB-TRP2-RX is the second TRP received timing of uplink subframe #i containing SRS associated with UE, defined by the first detected path in time, and TgNB-TRPi-Tx is the first TRP transmit timing of downlink subframe #j that is closest in time to the subframe #i received from the UE. Multiple SRS resources may be used to determine a start of one subframe containing SRS. A reference point for TgNB-TRP2-RX may be an Rx antenna connector for a type 1-C base station, an Rx antenna (e.g., the center location of theQC2500147WOQualcomm Ref. No. 2500147WO69 / 94radiating region of the Rx antenna) for type 1-0 or 2-0 base stations, and / or an Rx transceiver array boundary connector for type 1-H base stations. A reference point for TgNB-TRPi-rx may be a Tx antenna connector for type 1-C base stations, a Tx antenna (e.g., the center location of the radiating region of the Tx antenna) for type 1-0 or 2-0 base stations, and / or Tx transceiver array boundary connector for type 1-H base stations.

[0264] In accordance with aspects of the disclosure, a TRP and / or gNB may measure and / or indicate a reference signal transmission time. For example, a transmission time may correspond to a subframe timing of a transmitted reference signal (e.g., by a first TRP). Additionally or alternatively, a transmission time may correspond to a measured RS timing at a transmitting TRP side (e.g., before going into the air). The transmission time may be considered as a downlink relative time of transmission (DL RTOT). A TRP may provide a timestamp to indicate when a transmission time is done (e.g., an NR timestamp or a coordinated universal time (UTC) timing). Multiple transmission times may be provided depending on an antenna reference point (ARP) being used and / or one or more timing error groups (TEGs) being considered for a given ARP. There may be multiple transmission time indications depending on a number of resource element groups (REGs). A device may need to indicate a corrected transmission time accounting for transmission timing errors and / or offsets with respect to other (unsynchronized) TRPs and / or gNBs.

[0265] TgNB-rx is the TRP transmit timing of downlink subframe #j that is closest in time to the subframe #i received from the UE. The reference point for T§NB-TX may be a Tx antenna connector for type 1-C base stations, the Tx antenna (e.g., the center location of the radiating region of the Tx antenna) for type 1-0 or 2-0 base stations, and / or a transceiver array boundary connector for type 1-H base stations.

[0266] In an example, a downlink relative time of transmission (TDL-RTOT) may be the beginning of subframe i containing PRS transmitted from TP j . Multiple PRS resources may be used to determine the beginning of one subframe containing PRS transmitted at a TP. A reference point for TDL-RTOT may be a Tx antenna connector for type 1-C base stations, a Tx antenna (e.g., the center location of the radiating region of the Tx antenna) for type 1-0 or 2-0 base stations, and / or a transceiver array boundary connector for type 1-H base stations.

[0267] In an example, TDL-RTOT may be the beginning of subframe i containing a reference signal (e.g., PRS) transmitted from TP j, relative to an RTOT reference time. Multiple PRSQC2500147WOQualcomm Ref. No. 2500147WO70 / 94resources may be used to determine the beginning of one subframe containing PRS transmitted at a TP.

[0268] The DL RTOT reference time may be defined as To+tpps, where To is the nominal beginning time of SFN 0 provided by an SFN initialization time of a second TRP or synchronization signal or relative time difference (RTD) with the second TRP, and tpps is (l0nf+nsf) x 10'3, where / / / and / / are the system frame number and the subframe number of the PRS, respectively. A reference point for TDL-RTOT may be a Tx antenna connector for type 1-C base stations, a Tx antenna (e.g., the center location of the radiating region of the Tx antenna) for type 1-0 or 2-0 base stations, and / or a transceiver array boundary connector for type 1-H base stations.

[0269] For mRTT measurements reported from a gNB to an LMF and / or location server, the gNB may be requested and / or configured to report measurements. In an example, a gNB may report a transmission time (e.g., of TP-only TRPs) and / or a reception time (e.g., uplink relative time of arrival (RTOA) (e.g., of RP-only TRPs). Additionally or alternatively, gNB may report TRP IDs for TP-only TRPs (e.g., indicating that the TRP is TP-only) and / or RP-only TRPs (e.g., indicating that the TRP is RP-only) involved in the measurements. An LMF and / or location server may determine an Rx-Tx time difference based on the reports. If the gNB reports a gNB-cross-TRP Rx-Tx time difference, the report may include a flag to indicate that the measurement is cross- TRP / gNB, identifiers of one or more of the involved TRPs and / or gNBs, which TRPs / gNBs are transmitting and / or receiving, or any combination thereof.

[0270] As noted above, determination of asymmetric mRTT may involve signaling between TRPs. In an example, a first TRP may report a reference signal transmission time to a second TRP (e.g., directly or via a gNB using an Fl interface); the second TRP may determine the gNB-cross-TRP Rx-Tx time difference and report the time difference to the gNB (e.g., a base station central unit of the gNB). In an example, a first TRP may report a reference signal reception time (e.g., UL RTOA) to a second TRP (e.g., directly or via a gNB using an Fl interface); the second TRP may determine the gNB-cross-TRP Rx-Tx time difference and report it to gNB (e.g., a base station central unit of the gNB). The gNB may determine the difference.

[0271] Determination of asymmetric mRTT may involve signaling between gNBs (e.g., a serving gNB and one or more neighboring gNBs). In an example, a first gNB may report a reference signal transmission time to a second gNB; the second gNB may determine theQC2500147WOQualcomm Ref. No. 2500147WO71 / 94gNB-cross-TRP Rx-Tx time difference (e.g., using Xn signaling). In an example, a first gNB may report a reference signal reception time (e.g., UL RTOA) to a second gNB; the second gNB may determine the gNB-cross-TRP Rx-Tx time difference (e.g., using Xn signaling).

[0272] Reporting may be associated with a granularity factor. In an example, if a gNB is requested to provide measurements of transmission time, reception time, and / or gNB- cross-TRP Rx-Tx time difference with a timing granularity factor, the timing granularity factor may be taken into account when configuring measurements.

[0273] Asymmetric RTT measurements may involve one or more TRP Rx timing error groups (TEGs). In an example, if a gNB is requested to provide measurements of reception time and / or gNB-cross-TRP Rx-Tx time difference with a number of Rx TEGs, it may, if supported, use the number of Rx TEGs to measure a same resource (e.g., SRS resource) with different Rx TEGs for a TRP indicated as RP-only, and report the corresponding measurements. The number of Rx TEGs may be indicated in the request message.

[0274] Asymmetric RTT measurements may involve one or more TRP Tx TEGs. In an example, if a gNB is requested to provide measurements of transmission time and / or gNB-cross- TRP Rx-Tx time difference with a number of Tx TEGs, it may, if supported, use the number of Tx TEGs to indicate a transmission time of a same resource (e.g., PRS resource) with different transmission TEGs for a TRP indicated as TP-only, and report the corresponding measurements. The number of Tx TEGs may be indicated in the request message.

[0275] Asymmetric RTT measurements may involve one or more TRP Rx-Tx TEGs. In an example, if a gNB is requested to provide measurements of a gNB-cross-TRP Rx-Tx time difference with a number of Rx-Tx TEGs, it may, if supported, use the number of Rx-Tx TEGs to measure a same resource (e.g., SRS resource) with different RX TEGs for a TRP indicated as RP-only, and report the corresponding measurements. The number of Rx-Tx TEGs may be indicated in the request message.

[0276] A gNB may indicate TRP information to an LMF and / or location server. The TRP information may be provided, for example, upon request by the LMF and / or location server.

[0277] A gNB may indicate one or more capabilities to an LMF and / or location server. The gNB may indicate support for an asymmetric RTT method, support for asymmetric RTT measurements, support for coordination with other gNBs for cross-gNB asymmetric RTTQC2500147WOQualcomm Ref. No. 2500147WO72 / 94methods and / or measurements, a list of gNBs that support cross-gNB asymmetric RTT methods and / or measurements (e.g., if supported), or any combination thereof.

[0278] An LMF and / or location server may request asymmetric measurement from a gNB. The request may indicate, for example, one or more asymmetric measurements to be obtained, one or more TRP identifiers of one or more TRP to be involved in the one or more asymmetric measurements, one or more gNB identifiers of one or more gNBs to be involved in the one or more asymmetric measurements, or any combination thereof. The gNB may report the requested measurements.

[0279] A UE may be requested and / or configured to report measurements to an LMF and / or location service. In an example, a UE may report a transmission time of a TP-only UE and / or a reception time (e.g., SL RTOA) of an RP-only TRP. The UE may report an antenna reference point (ARP) identifier for one or more ARPs involved in the RTT measurements. The UE may report ARP identifiers for one or more TP-only ARPs (e.g., indicating that the identified ARPs are TP-only) and for one or more RP-only ARPs (e.g., indicating that the identified ARPs are RP-only). The LMF and / or location server may determine a sidelink Rx-Tx time difference based on the reports. The LMF and / or location server may determine a sidelink Rx-Rx time difference based on the reports. If a UE reports a cross-UE SL Rx-Tx time difference, the UE may provide a flag to indicate that a measurement is a cross-UE measurements, one or more identifiers of one or more involved UEs and / or one or more involved ARPs, one or more indications of whether a UE / ARP is transmit-only or receive-only, or any combination thereof.

[0280] FIG. 13 illustrates an example method 1300 of wireless positioning, according to aspects of the disclosure. In an aspect, method 1300 may be performed by a device (e.g., any of the UEs, TRPs, and / or gNBs described herein).

[0281] At 1310, the device determines a first time at which a third node transmits a first reference signal to a second node.

[0282] In an aspect, where the device is a UE (e.g., analogous to UE 302), operation 1310 may be performed by the one or more WWAN transceivers 310, the one or more short-range wireless transceivers 320, the memory 340, the one or more processors 342, and / or the positioning component 348, any or all of which may be considered means for performing this operation.

[0283] In an aspect, where the device is a TRP and / or gNB (e.g., analogous to base station 304), operation 1310 may be performed by the one or more WWAN transceivers 350, the oneQC2500147WOQualcomm Ref. No. 2500147WO1or more short-range wireless transceivers 360, the memory 386, the one or more processors 384, and / or the positioning component 388, any or all of which may be considered means for performing this operation.

[0284] At 1320, the device determines a second time at which a first node receives a second reference signal from the second node.

[0285] In an aspect, where the device is a UE (e.g., analogous to UE 302), operation 1320 may be performed by the one or more WWAN transceivers 310, the one or more short-range wireless transceivers 320, the memory 340, the one or more processors 342, and / or the positioning component 348, any or all of which may be considered means for performing this operation.

[0286] In an aspect, where the device is a TRP and / or gNB (e.g., analogous to base station 304), operation 1320 may be performed by the one or more WWAN transceivers 350, the one or more short-range wireless transceivers 360, the memory 386, the one or more processors 384, and / or the positioning component 388, any or all of which may be considered means for performing this operation.

[0287] At 1330, the device determines a cross-node Rx-Tx time difference between the second time and the first time.

[0288] In an aspect, where the device is a UE (e.g., analogous to UE 302), operation 1330 may be performed by the one or more WWAN transceivers 310, the one or more short-range wireless transceivers 320, the memory 340, the one or more processors 342, and / or the positioning component 348, any or all of which may be considered means for performing this operation.

[0289] In an aspect, where the device is a TRP and / or gNB (e.g., analogous to base station 304), operation 1330 may be performed by the one or more WWAN transceivers 350, the one or more short-range wireless transceivers 360, the memory 386, the one or more processors 384, and / or the positioning component 388, any or all of which may be considered means for performing this operation.

[0290] As will be appreciated, a technical advantage of the method 1300 is that the cross-node Rx-Tx time difference may contribute to the determination of an mRTT value (e.g., an asymmetric mRTT value), and thereby facilitate positioning (e.g., of the second node), even in a scenario where one or more of the nodes (e.g., the first node and / or the third node) is receive-only or transmit-only.QC2500147WOQualcomm Ref. No. 2500147WO74 / 94

[0291] 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.

[0292] Implementation examples are described in the following numbered clauses:

[0293] Clause 1. A method of wireless positioning performed by a device, comprising:determining a first time at which a third node transmits a first reference signal to a second node; determining a second time at which a first node receives a second reference signal from the second node; and determining a cross-node Rx-Tx time difference between the second time and the first time.

[0294] Clause 2. The method of clause 1, wherein the device is the first node, and further comprising: receiving, at the second time, from the second node, the second reference signal; and obtaining a transmission timestamp indicating the first time at which the third node transmitted the first reference signal to the second node.

[0295] Clause 3. The method of clause 2, wherein the obtaining the transmission timestamp comprises: determining the transmission timestamp based on the second reference signal; receiving the transmission timestamp from the third node; receiving the transmission timestamp from the third node via the second node; or receiving the transmission timestamp from a base station.QC2500147WOQualcomm Ref. No. 2500147WO75 / 94

[0296] Clause 4. The method of any of clauses 2 to 3, wherein the transmission timestamp indicates: a subframe timing of a subframe comprising the first reference signal; a measured timing of the transmission of the first reference signal; or a relative time of transmission of the first reference signal.

[0297] Clause 5. The method of any of clauses 2 to 4, wherein the transmission timestamp indicates: a system time corresponding to a frame, subframe, slot, symbol, or any combination thereof; or a coordinated universal time (UTC).

[0298] Clause 6. The method of any of clauses 2 to 5, wherein obtaining a transmission timestamp comprises: obtaining a plurality of transmission timestamps; and selecting the transmission timestamp from the plurality of transmission timestamps; wherein the plurality of transmission timestamps correspond to a plurality of timing error groups (TEGs), a plurality of antenna reference points (ARPs), or both.

[0299] Clause 7. The method of any of clauses 1 to 6, wherein the device is the second node, and further comprising: receiving, from the third node, the first reference signal; transmitting, to the first node, the second reference signal; determining a Tx-Rx time difference between the transmitting of the second reference signal and the receiving of the first reference signal; receiving: an indication of a first time at which the third node transmitted the first reference signal and an indication of a second time at which the first node received the second reference signal; or an indication of a cross-node Rx-Tx time difference between the second time and the first time; and determining, based on the cross-node Rx-Tx time difference and the Tx-Rx time difference, an asymmetric round trip time (RTT) measurement.

[0300] Clause 8. The method of clause 7, further comprising: transmitting, to the first node, the third node, a base station, a location management function (LMF), or any combination thereof, a measurement report comprising the asymmetric RTT measurement; or determining a position of the second node based on: the asymmetric RTT measurement; and a plurality of other asymmetric RTT measurements.

[0301] Clause 9. The method of any of clauses 1 to 8, wherein the device is the third node, and further comprising: transmitting, at the first time, to the second node, the first reference signal; receiving a reception timestamp indicating the second time at which the first node received the second reference signal from the second node; and determining a cross-node Rx-Tx time difference between the second time and the first time.QC2500147WOQualcomm Ref. No. 2500147WO76 / 94

[0302] Clause 10. The method of clause 9, wherein the receiving the reception timestamp comprises: receiving the reception timestamp from the first node via a sidelink message; or receiving the reception timestamp from a base station via a downlink message.

[0303] Clause 11. The method of any of clauses 9 to 10, wherein the reception timestamp indicates: a subframe timing of a subframe comprising the second reference signal; a measured timing of the reception of the second reference signal; or a relative time of reception of the second reference signal.

[0304] Clause 12. The method of any of clauses 9 to 11, further comprising transmitting, to the first node, the second node, a base station, a location management function (LMF), or any combination thereof, a measurement report comprising the cross-node Rx-Tx time difference.

[0305] Clause 13. The method of any of clauses 1 to 12, further comprising: receiving, from the second node, an indication of a Tx-Rx time difference between transmission by the second node of the of the second reference signal and reception by the second node of the first reference signal; determining, based on the cross-node Rx-Tx time difference and the Tx- Rx time difference, a asymmetric round trip time (RTT) measurement; and determining a position of the second node based on: the asymmetric RTT measurement; and a plurality of other asymmetric RTT measurements.

[0306] Clause 14. The method of any of clauses 1 to 13, further comprising transmitting, to the first node, the second node, the third node, a base station, a location management function (LMF), or any combination thereof, a measurement report comprising the cross-node Rx- Tx time difference.

[0307] Clause 15. The method of clause 14, wherein the measurement report comprises one or more of: an indication that the measurement report comprises an Rx-Tx time difference between two different nodes; identifiers of the two different nodes; or an indicator of which of the two different nodes is a receive-only participant and which of the two different nodes is a transmit-only participant.

[0308] Clause 16. The method of any of clauses 1 to 15, wherein: the first node is a receive-only participant in a positioning procedure associated with an asymmetric RTT measurement; the third node is a transmit-only participant in the positioning procedure associated with the asymmetric RTT measurement; or any combination thereof.

[0309] Clause 17. The method of any of clauses 1 to 16, wherein the first node is a first user equipment (UE), the second node is a second UE, the third node is a third LE, the secondQC2500147WOQualcomm Ref. No. 2500147WOTIMreference signal is a sidelink reference signal, and the cross-node Rx-Tx time difference is a cross-UE sidelink Rx-Tx time difference.

[0310] Clause 18. The method of any of clauses 1 to 17, wherein the first node is a first transmission-reception point (TRP), the second node is a second UE, the third node is a third TRP, the second reference signal is a sounding reference signal (SRS), and the crossnode Rx-Tx time difference is a cross-TRP Rx-Tx time difference.

[0311] Clause 19. A device comprising: one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors, either alone or in combination, configured to: determine a first time at which a third node transmits a first reference signal to a second node; determine a second time at which a first node receives a second reference signal from the second node; and determine a cross-node Rx-Tx time difference between the second time and the first time.

[0312] Clause 20. The device of clause 19, wherein the device is the first node, and wherein the one or more processors, either alone or in combination, are further configured to: receive, via the one or more transceivers, at the second time, from the second node, the second reference signal; and obtain a transmission timestamp indicating the first time at which the third node transmitted the first reference signal to the second node.

[0313] Clause 21. The device of clause 20, wherein the obtaining the transmission timestamp comprises: determine the transmission timestamp based on the second reference signal; receive, via the one or more transceivers, the transmission timestamp from the third node; receive, via the one or more transceivers, the transmission timestamp from the third node via the second node; or receive, via the one or more transceivers, the transmission timestamp from a base station.

[0314] Clause 22. The device of any of clauses 20 to 21, wherein the transmission timestamp indicates: a subframe timing of a subframe comprising the first reference signal; a measured timing of the transmission of the first reference signal; or a relative time of transmission of the first reference signal.

[0315] Clause 23. The device of any of clauses 20 to 22, wherein the transmission timestamp indicates: a system time corresponding to a frame, subframe, slot, symbol, or any combination thereof; or a coordinated universal time (UTC).

[0316] Clause 24. The device of any of clauses 20 to 23, wherein obtaining a transmission timestamp comprises: obtain a plurality of transmission timestamps; and select theQC2500147WOQualcomm Ref. No. 2500147WOtransmission timestamp from the plurality of transmission timestamps; wherein the plurality of transmission timestamps correspond to a plurality of timing error groups (TEGs), a plurality of antenna reference points (ARPs), or both.

[0317] Clause 25. The device of any of clauses 19 to 24, wherein the device is the second node, and wherein the one or more processors, either alone or in combination, are further configured to: receive, via the one or more transceivers, from the third node, the first reference signal; transmit, via the one or more transceivers, to the first node, the second reference signal; determine a Tx-Rx time difference between the transmitting of the second reference signal and the receiving of the first reference signal; receive, via the one or more transceivers: an indication of a first time at which the third node transmitted the first reference signal and an indication of a second time at which the first node received the second reference signal; or an indication of a cross-node Rx-Tx time difference between the second time and the first time; and determine, based on the cross-node Rx- Tx time difference and the Tx-Rx time difference, an asymmetric round trip time (RTT) measurement.

[0318] Clause 26. The device of clause 25, wherein the one or more processors, either alone or in combination, are further configured to: transmit, via the one or more transceivers, to the first node, the third node, a base station, a location management function (LMF), or any combination thereof, a measurement report comprising the asymmetric RTT measurement; or determine a position of the second node based on: the asymmetric RTT measurement; and a plurality of other asymmetric RTT measurements.

[0319] Clause 27. The device of any of clauses 19 to 26, wherein the device is the third node, and wherein the one or more processors, either alone or in combination, are further configured to: transmit, via the one or more transceivers, at the first time, to the second node, the first reference signal; receive, via the one or more transceivers, a reception timestamp indicating the second time at which the first node received the second reference signal from the second node; and determine a cross-node Rx-Tx time difference between the second time and the first time.

[0320] Clause 28. The device of clause 27, wherein the receiving the reception timestamp comprises: receive, via the one or more transceivers, the reception timestamp from the first node via a sidelink message; or receive, via the one or more transceivers, the reception timestamp from a base station via a downlink message.QC2500147WOQualcomm Ref. No. 2500147WO79 / 94

[0321] Clause 29. The device of any of clauses 27 to 28, wherein the reception timestamp indicates: a subframe timing of a subframe comprising the second reference signal; a measured timing of the reception of the second reference signal; or a relative time of reception of the second reference signal.

[0322] Clause 30. The device of any of clauses 27 to 29, wherein the one or more processors, either alone or in combination, are further configured to transmit, via the one or more transceivers, to the first node, the second node, a base station, a location management function (LMF), or any combination thereof, a measurement report comprising the crossnode Rx-Tx time difference.

[0323] Clause 31. The device of any of clauses 19 to 30, wherein the one or more processors, either alone or in combination, are further configured to: receive, via the one or more transceivers, from the second node, an indication of a Tx-Rx time difference between transmission by the second node of the of the second reference signal and reception by the second node of the first reference signal; determine, based on the cross-node Rx-Tx time difference and the Tx-Rx time difference, a asymmetric round trip time (RTT) measurement; and determine a position of the second node based on: the asymmetric RTT measurement; and a plurality of other asymmetric RTT measurements.

[0324] Clause 32. The device of any of clauses 19 to 31, wherein the one or more processors, either alone or in combination, are further configured to transmit, via the one or more transceivers, to the first node, the second node, the third node, a base station, a location management function (LMF), or any combination thereof, a measurement report comprising the cross-node Rx-Tx time difference.

[0325] Clause 33. The device of clause 32, wherein the measurement report comprises one or more of: an indication that the measurement report comprises an Rx-Tx time difference between two different nodes; identifiers of the two different nodes; or an indicator of which of the two different nodes is a receive-only participant and which of the two different nodes is a transmit-only participant.

[0326] Clause 34. The device of any of clauses 19 to 33, wherein: the first node is a receive-only participant in a positioning procedure associated with an asymmetric RTT measurement; the third node is a transmit-only participant in the positioning procedure associated with the asymmetric RTT measurement; or any combination thereof.

[0327] Clause 35. The device of any of clauses 19 to 34, wherein the first node is a first user equipment (UE), the second node is a second UE, the third node is a third LE, the secondQC2500147WOQualcomm Ref. No. 2500147WO80 / 94reference signal is a sidelink reference signal, and the cross-node Rx-Tx time difference is a cross-UE sidelink Rx-Tx time difference.

[0328] Clause 36. The device of any of clauses 19 to 35, wherein the first node is a first transmission-reception point (TRP), the second node is a second UE, the third node is a third TRP, the second reference signal is a sounding reference signal (SRS), and the crossnode Rx-Tx time difference is a cross-TRP Rx-Tx time difference.

[0329] Clause 37. A device comprising: means for determining a first time at which a third node transmits a first reference signal to a second node; means for determining a second time at which a first node receives a second reference signal from the second node; and means for determining a cross-node Rx-Tx time difference between the second time and the first time.

[0330] Clause 38. The device of clause 37, wherein the device is the first node, and further comprising: means for receiving, at the second time, from the second node, the second reference signal; and means for obtaining a transmission timestamp indicating the first time at which the third node transmitted the first reference signal to the second node.

[0331] Clause 39. The device of clause 38, wherein the obtaining the transmission timestamp comprises: means for determining the transmission timestamp based on the second reference signal; means for receiving the transmission timestamp from the third node; means for receiving the transmission timestamp from the third node via the second node; or means for receiving the transmission timestamp from a base station.

[0332] Clause 40. The device of any of clauses 38 to 39, wherein the transmission timestamp indicates: a subframe timing of a subframe comprising the first reference signal; a measured timing of the transmission of the first reference signal; or a relative time of transmission of the first reference signal.

[0333] Clause 41. The device of any of clauses 38 to 40, wherein the transmission timestamp indicates: a system time corresponding to a frame, subframe, slot, symbol, or any combination thereof; or a coordinated universal time (UTC).

[0334] Clause 42. The device of any of clauses 38 to 41, wherein obtaining a transmission timestamp comprises: means for obtaining a plurality of transmission timestamps; and means for selecting the transmission timestamp from the plurality of transmission timestamps; wherein the plurality of transmission timestamps correspond to a plurality of timing error groups (TEGs), a plurality of antenna reference points (ARPs), or both.QC2500147WOQualcomm Ref. No. 2500147WO81 / 94

[0335] Clause 43. The device of any of clauses 37 to 42, wherein the device is the second node, and further comprising: means for receiving, from the third node, the first reference signal; means for transmitting, to the first node, the second reference signal; means for determining a Tx-Rx time difference between the transmitting of the second reference signal and the receiving of the first reference signal; means for receiving: an indication of a first time at which the third node transmitted the first reference signal and an indication of a second time at which the first node received the second reference signal; or an indication of a cross-node Rx-Tx time difference between the second time and the first time; and means for determining, based on the cross-node Rx-Tx time difference and the Tx-Rx time difference, an asymmetric round trip time (RTT) measurement.

[0336] Clause 44. The device of clause 43, further comprising: means for transmitting, to the first node, the third node, a base station, a location management function (LMF), or any combination thereof, a measurement report comprising the asymmetric RTT measurement; or means for determining a position of the second node based on: the asymmetric RTT measurement; and a plurality of other asymmetric RTT measurements.

[0337] Clause 45. The device of any of clauses 37 to 44, wherein the device is the third node, and further comprising: means for transmitting, at the first time, to the second node, the first reference signal; means for receiving a reception timestamp indicating the second time at which the first node received the second reference signal from the second node; and means for determining a cross-node Rx-Tx time difference between the second time and the first time.

[0338] Clause 46. The device of clause 45, wherein the receiving the reception timestamp comprises: means for receiving the reception timestamp from the first node via a sidelink message; or means for receiving the reception timestamp from a base station via a downlink message.

[0339] Clause 47. The device of any of clauses 45 to 46, wherein the reception timestamp indicates: a subframe timing of a subframe comprising the second reference signal; a measured timing of the reception of the second reference signal; or a relative time of reception of the second reference signal.

[0340] Clause 48. The device of any of clauses 45 to 47, further comprising means for transmitting, to the first node, the second node, a base station, a location management function (LMF), or any combination thereof, a measurement report comprising the crossnode Rx-Tx time difference.QC2500147WOQualcomm Ref. No. 2500147WO82 / 94

[0341] Clause 49. The device of any of clauses 37 to 48, further comprising: means for receiving, from the second node, an indication of a Tx-Rx time difference between transmission by the second node of the of the second reference signal and reception by the second node of the first reference signal; means for determining, based on the cross-node Rx-Tx time difference and the Tx-Rx time difference, a asymmetric round trip time (RTT) measurement; and means for determining a position of the second node based on: the asymmetric RTT measurement; and a plurality of other asymmetric RTT measurements.

[0342] Clause 50. The device of any of clauses 37 to 49, further comprising means for transmitting, to the first node, the second node, the third node, a base station, a location management function (LMF), or any combination thereof, a measurement report comprising the cross-node Rx-Tx time difference.

[0343] Clause 51. The device of clause 50, wherein the measurement report comprises one or more of: an indication that the measurement report comprises an Rx-Tx time difference between two different nodes; identifiers of the two different nodes; or an indicator of which of the two different nodes is a receive-only participant and which of the two different nodes is a transmit-only participant.

[0344] Clause 52. The device of any of clauses 37 to 51, wherein: the first node is a receive-only participant in a positioning procedure associated with an asymmetric RTT measurement; the third node is a transmit-only participant in the positioning procedure associated with the asymmetric RTT measurement; or any combination thereof.

[0345] Clause 53. The device of any of clauses 37 to 52, wherein the first node is a first user equipment (UE), the second node is a second UE, the third node is a third UE, the second reference signal is a sidelink reference signal, and the cross-node Rx-Tx time difference is a cross-UE sidelink Rx-Tx time difference.

[0346] Clause 54. The device of any of clauses 37 to 53, wherein the first node is a first transmission-reception point (TRP), the second node is a second UE, the third node is a third TRP, the second reference signal is a sounding reference signal (SRS), and the crossnode Rx-Tx time difference is a cross-TRP Rx-Tx time difference.

[0347] Clause 55. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a device, cause the device to: determine a first time at which a third node transmits a first reference signal to a second node; determine a second time at which a first node receives a second reference signal from the second node;QC2500147WOQualcomm Ref. No. 2500147WO83 / 94and determine a cross-node Rx-Tx time difference between the second time and the first time.

[0348] Clause 56. The non-transitory computer-readable medium of clause 55, wherein the device is the first node, and further comprising computer-executable instructions that, when executed by the device, cause the device to: receive, at the second time, from the second node, the second reference signal; and obtain a transmission timestamp indicating the first time at which the third node transmitted the first reference signal to the second node.

[0349] Clause 57. The non-transitory computer-readable medium of clause 56, wherein the obtaining the transmission timestamp comprises: determine the transmission timestamp based on the second reference signal; receive the transmission timestamp from the third node; receive the transmission timestamp from the third node via the second node; or receive the transmission timestamp from a base station.

[0350] Clause 58. The non-transitory computer-readable medium of any of clauses 56 to 57, wherein the transmission timestamp indicates: a subframe timing of a subframe comprising the first reference signal; a measured timing of the transmission of the first reference signal; or a relative time of transmission of the first reference signal.

[0351] Clause 59. The non-transitory computer-readable medium of any of clauses 56 to 58, wherein the transmission timestamp indicates: a system time corresponding to a frame, subframe, slot, symbol, or any combination thereof; or a coordinated universal time (UTC).

[0352] Clause 60. The non-transitory computer-readable medium of any of clauses 56 to 59, wherein obtaining a transmission timestamp comprises: obtain a plurality of transmission timestamps; and select the transmission timestamp from the plurality of transmission timestamps; wherein the plurality of transmission timestamps correspond to a plurality of timing error groups (TEGs), a plurality of antenna reference points (ARPs), or both.

[0353] Clause 61. The non-transitory computer-readable medium of any of clauses 55 to 60, wherein the device is the second node, and further comprising computer-executable instructions that, when executed by the device, cause the device to: receive, from the third node, the first reference signal; transmit, to the first node, the second reference signal; determine a Tx-Rx time difference between the transmitting of the second reference signal and the receiving of the first reference signal; receive: an indication of a first time at which the third node transmitted the first reference signal and an indication of a secondQC2500147WOQualcomm Ref. No. 2500147WO84 / 94time at which the first node received the second reference signal; or an indication of a cross-node Rx-Tx time difference between the second time and the first time; and determine, based on the cross-node Rx-Tx time difference and the Tx-Rx time difference, an asymmetric round trip time (RTT) measurement.

[0354] Clause 62. The non-transitory computer-readable medium of clause 61, further comprising computer-executable instructions that, when executed by the device, cause the device to: transmit, to the first node, the third node, a base station, a location management function (LMF), or any combination thereof, a measurement report comprising the asymmetric RTT measurement; or determine a position of the second node based on: the asymmetric RTT measurement; and a plurality of other asymmetric RTT measurements.

[0355] Clause 63. The non-transitory computer-readable medium of any of clauses 55 to 62, wherein the device is the third node, and further comprising computer-executable instructions that, when executed by the device, cause the device to: transmit, at the first time, to the second node, the first reference signal; receive a reception timestamp indicating the second time at which the first node received the second reference signal from the second node; and determine a cross-node Rx-Tx time difference between the second time and the first time.

[0356] Clause 64. The non-transitory computer-readable medium of clause 63, wherein the receiving the reception timestamp comprises: receive the reception timestamp from the first node via a sidelink message; or receive the reception timestamp from a base station via a downlink message.

[0357] Clause 65. The non-transitory computer-readable medium of any of clauses 63 to 64, wherein the reception timestamp indicates: a subframe timing of a subframe comprising the second reference signal; a measured timing of the reception of the second reference signal; or a relative time of reception of the second reference signal.

[0358] Clause 66. The non-transitory computer-readable medium of any of clauses 63 to 65, further comprising computer-executable instructions that, when executed by the device, cause the device to transmit, to the first node, the second node, a base station, a location management function (LMF), or any combination thereof, a measurement report comprising the cross-node Rx-Tx time difference.

[0359] Clause 67. The non-transitory computer-readable medium of any of clauses 55 to 66, further comprising computer-executable instructions that, when executed by the device,QC2500147WOQualcomm Ref. No. 2500147WO85 / 94cause the device to: receive, from the second node, an indication of a Tx-Rx time difference between transmission by the second node of the of the second reference signal and reception by the second node of the first reference signal; determine, based on the cross-node Rx-Tx time difference and the Tx-Rx time difference, a asymmetric round trip time (RTT) measurement; and determine a position of the second node based on: the asymmetric RTT measurement; and a plurality of other asymmetric RTT measurements.

[0360] Clause 68. The non-transitory computer-readable medium of any of clauses 55 to 67, further comprising computer-executable instructions that, when executed by the device, cause the device to transmit, to the first node, the second node, the third node, a base station, a location management function (LMF), or any combination thereof, a measurement report comprising the cross-node Rx-Tx time difference.

[0361] Clause 69. The non-transitory computer-readable medium of clause 68, wherein the measurement report comprises one or more of: an indication that the measurement report comprises an Rx-Tx time difference between two different nodes; identifiers of the two different nodes; or an indicator of which of the two different nodes is a receive-only participant and which of the two different nodes is a transmit-only participant.

[0362] Clause 70. The non-transitory computer-readable medium of any of clauses 55 to 69, wherein: the first node is a receive-only participant in a positioning procedure associated with an asymmetric RTT measurement; the third node is a transmit-only participant in the positioning procedure associated with the asymmetric RTT measurement; or any combination thereof.

[0363] Clause 71. The non-transitory computer-readable medium of any of clauses 55 to 70, wherein the first node is a first user equipment (UE), the second node is a second UE, the third node is a third UE, the second reference signal is a sidelink reference signal, and the cross-node Rx-Tx time difference is a cross-UE sidelink Rx-Tx time difference.

[0364] Clause 72. The non-transitory computer-readable medium of any of clauses 55 to 71, wherein the first node is a first transmission-reception point (TRP), the second node is a second UE, the third node is a third TRP, the second reference signal is a sounding reference signal (SRS), and the cross-node Rx-Tx time difference is a cross-TRP Rx-Tx time difference.

[0365] 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 beQC2500147WOQualcomm Ref. No. 2500147WO86 / 94referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0366] 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.

[0367] 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.

[0368] 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. InQC2500147WOQualcomm Ref. No. 2500147WO87 / 94the 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.

[0369] 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.

[0370] 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 theQC2500147WOQualcomm Ref. No. 2500147WO88 / 94stated 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.QC2500147WO

Claims

1. Qualcomm Ref. No. 2500147WO89 / 94CLAIMSWhat is claimed is:

1. A device comprising:one or more memories;one or more transceivers; andone or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors, either alone or in combination, configured to:determine a first time at which a third node transmits a first reference signal to a second node;determine a second time at which a first node receives a second reference signal from the second node; anddetermine a cross-node Rx-Tx time difference between the second time and the first time.

2. The device of claim 1, wherein the device is the first node, and wherein the one or more processors, either alone or in combination, are further configured to:receive, via the one or more transceivers, at the second time, from the second node, the second reference signal; andobtain a transmission timestamp indicating the first time at which the third node transmitted the first reference signal to the second node.

3. The device of claim 2, wherein the obtaining the transmission timestamp comprises:determine the transmission timestamp based on the second reference signal; receive, via the one or more transceivers, the transmission timestamp from the third node;receive, via the one or more transceivers, the transmission timestamp from the third node via the second node; orreceive, via the one or more transceivers, the transmission timestamp from a base station.

4. The device of claim 2, wherein the transmission timestamp indicates:a subframe timing of a subframe comprising the first reference signal;QC2500147WOQualcomm Ref. No. 2500147WO90 / 94a measured timing of the transmission of the first reference signal; or a relative time of transmission of the first reference signal.

5. The device of claim 2, wherein the transmission timestamp indicates:a system time corresponding to a frame, subframe, slot, symbol, or any combination thereof; ora coordinated universal time (UTC).

6. The device of claim 2, wherein obtaining a transmission timestamp comprises:obtain a plurality of transmission timestamps; andselect the transmission timestamp from the plurality of transmission timestamps;wherein the plurality of transmission timestamps correspond to a plurality of timing error groups (TEGs), a plurality of antenna reference points (ARPs), or both.

7. The device of claim 1, wherein the device is the second node, and wherein the one or more processors, either alone or in combination, are further configured to:receive, via the one or more transceivers, from the third node, the first reference signal;transmit, via the one or more transceivers, to the first node, the second reference signal;determine a Tx-Rx time difference between the transmitting of the second reference signal and the receiving of the first reference signal;receive, via the one or more transceivers:an indication of a first time at which the third node transmitted the first reference signal and an indication of a second time at which the first node received the second reference signal; oran indication of a cross-node Rx-Tx time difference between the second time and the first time; anddetermine, based on the cross-node Rx-Tx time difference and the Tx-Rx time difference, an asymmetric round trip time (RTT) measurement.QC2500147WOQualcomm Ref. No. 2500147WO91 / 948. The device of claim 7, wherein the one or more processors, either alone or in combination, are further configured to:transmit, via the one or more transceivers, to the first node, the third node, a base station, a location management function (LMF), or any combination thereof, a measurement report comprising the asymmetric RTT measurement; or determine a position of the second node based on:the asymmetric RTT measurement; anda plurality of other asymmetric RTT measurements.

9. The device of claim 1, wherein the device is the third node, and wherein the one or more processors, either alone or in combination, are further configured to:transmit, via the one or more transceivers, at the first time, to the second node, the first reference signal;receive, via the one or more transceivers, a reception timestamp indicating the second time at which the first node received the second reference signal from the second node; anddetermine a cross-node Rx-Tx time difference between the second time and the first time.

10. The device of claim 9, wherein the receiving the reception timestamp comprises:receive, via the one or more transceivers, the reception timestamp from the first node via a sidelink message; orreceive, via the one or more transceivers, the reception timestamp from a base station via a downlink message.

11. The device of claim 9, wherein the reception timestamp indicates:a subframe timing of a subframe comprising the second reference signal; a measured timing of the reception of the second reference signal; or a relative time of reception of the second reference signal.

12. The device of claim 9, wherein the one or more processors, either alone or in combination, are further configured to transmit, via the one or more transceivers, to the first node, the second node, a base station, a location management function (LMF), orQC2500147WOQualcomm Ref. No. 2500147WO92 / 94any combination thereof, a measurement report comprising the cross-node Rx-Tx time difference.

13. The device of claim 1, wherein the one or more processors, either alone or in combination, are further configured to:receive, via the one or more transceivers, from the second node, an indication of a Tx-Rx time difference between transmission by the second node of the of the second reference signal and reception by the second node of the first reference signal;determine, based on the cross-node Rx-Tx time difference and the Tx-Rx time difference, an asymmetric round trip time (RTT) measurement; and determine a position of the second node based on:the asymmetric RTT measurement; anda plurality of other asymmetric RTT measurements.

14. The device of claim 1, wherein the one or more processors, either alone or in combination, are further configured to transmit, via the one or more transceivers, to the first node, the second node, the third node, a base station, a location management function (LMF), or any combination thereof, a measurement report comprising the cross-node Rx-Tx time difference.

15. The device of claim 14, wherein the measurement report comprises one or more of:an indication that the measurement report comprises an Rx-Tx time difference between two different nodes;identifiers of the two different nodes; oran indicator of which of the two different nodes is a receive-only participant and which of the two different nodes is a transmit-only participant.

16. The device of claim 1, wherein:the first node is a receive-only participant in a positioning procedure associated with an asymmetric RTT measurement;the third node is a transmit-only participant in the positioning procedure associated with the asymmetric RTT measurement; orany combination thereof.QC2500147WOQualcomm Ref. No. 2500147WO93 / 9417. The device of claim 1, wherein the first node is a first user equipment (UE), the second node is a second UE, the third node is a third UE, the second reference signal is a sidelink reference signal, and the cross-node Rx-Tx time difference is a cross-UE sidelink Rx-Tx time difference.

18. The device of claim 1, wherein the first node is a first transmission-reception point (TRP), the second node is a second UE, the third node is a third TRP, the second reference signal is a sounding reference signal (SRS), and the cross-node Rx-Tx time difference is a cross-TRP Rx-Tx time difference.

19. A method of wireless positioning performed by a device, comprising:determining a first time at which a third node transmits a first reference signal to a second node;determining a second time at which a first node receives a second reference signal from the second node; anddetermining a cross-node Rx-Tx time difference between the second time and the first time.

20. A device comprising:means for determining a first time at which a third node transmits a first reference signal to a second node;means for determining a second time at which a first node receives a second reference signal from the second node; andmeans for determining a cross-node Rx-Tx time difference between the second time and the first time.QC2500147WO

Images