Round trip time measurement procedure on reciprocal cross-link interference measurement resources

Abstract

In one aspect, a base station (BS) determines a CLI measurement resource configuration associated with first and second UEs, the reciprocal CLI measurement resource configuration including resources associated with both a CLI measurement procedure and an RTT measurement procedure between the first UE and the second UE. The BS transmits the reciprocal CLI measurement resource configuration to the first and second UEs. The first and second UEs perform both a CLI measurement procedure and an RTT measurement procedure with the second UE based on the resources associated with the reciprocal CLI measurement resource configuration.

Description

[0001] Public background

[0002] 1. Public Domain

[0003] Aspects of the present disclosure relate generally to wireless communications and, more particularly, to round-trip time measurement procedures on reciprocal cross-link interference (CLI) resources.

[0004] 2. Description of Related Technologies

[0005] Wireless communication systems have evolved over several generations, including first-generation analog wireless telephone service (1G), second-generation (2G) digital wireless telephone service (including transitional 2.5G networks), third-generation (3G) high-speed data wireless service with Internet capabilities, and fourth-generation (4G) services (e.g., LTE or WiMax). Currently, there are 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), Global System for Mobile Access (GSM) TDMA variants, and the like.

[0006] The fifth generation (5G) wireless standard, known as New Radio (NR), enables higher data transmission speeds, a greater number of connections, and better coverage, among other improvements. According to the Next Generation Mobile Networks Alliance, the 5G standard is designed to provide data rates of tens of megabits per second to each of tens of thousands of users, and 1 gigabit per second to dozens of employees on an office floor. Hundreds of thousands of simultaneous connections should be supported to support large wireless deployments. As a result, the spectral efficiency of 5G mobile communications should be significantly improved compared to the current 4G standard. In addition, signaling efficiency should be improved and latency should be significantly reduced compared to current standards.

[0007] Overview

[0008] The following is a simplified summary of one or more aspects disclosed herein. Thus, the following summary should not be considered an exhaustive overview of all contemplated aspects, nor should it be considered to identify key or critical elements related to all contemplated aspects or to delineate the scope associated with any particular aspect. Accordingly, the sole purpose of the following summary is to present certain concepts related to one or more aspects of the mechanisms disclosed herein in a simplified form prior to the detailed description given below.

[0009] An aspect relates to a method of operating a first user equipment (UE), the method comprising: receiving a reciprocal cross-link interference (CLI) measurement resource configuration associated with the first UE and a second UE; and performing both a CLI measurement procedure and a round-trip time (RTT) measurement procedure with the second UE based on resources associated with the reciprocal CLI measurement resource configuration.

[0010] Another aspect relates to a method of operating a base station, the method comprising: determining a reciprocal cross-link interference (CLI) measurement resource configuration associated with a first user equipment (UE) and a second UE, the reciprocal CLI measurement resource configuration comprising resources associated with both a CLI measurement procedure and a round trip time (RTT) measurement procedure between the first UE and the second UE; and transmitting the reciprocal CLI measurement resource configuration to the first UE and the second UE.

[0011] Another aspect relates to a first user equipment (UE), comprising: means for receiving a reciprocal cross-link interference (CLI) measurement resource configuration associated with the first UE and a second UE; and means for performing both a CLI measurement procedure and a round trip time (RTT) measurement procedure with the second UE based on resources associated with the reciprocal CLI measurement resource configuration.

[0012] Another aspect relates to a base station, comprising: means for determining a reciprocal cross-link interference (CLI) measurement resource configuration associated with a first user equipment (UE) and a second UE, the reciprocal CLI measurement resource configuration comprising resources associated with both a CLI measurement procedure and a round trip time (RTT) measurement procedure between the first UE and the second UE; and means for transmitting the reciprocal CLI measurement resource configuration to the first UE and the second UE.

[0013] Another aspect relates to a first user equipment (UE) comprising: a memory, at least one communication interface, and at least one processor communicatively coupled to the memory and the at least one communication interface, the at least one processor configured to: receive a reciprocal cross-link interference (CLI) measurement resource configuration associated with the first UE and a second UE; and perform both a CLI measurement procedure and a round trip time (RTT) measurement procedure with the second UE based on resources associated with the reciprocal CLI measurement resource configuration.

[0014] Another aspect relates to a base station, comprising: a memory, at least one communication interface, and at least one processor communicatively coupled to the memory and the at least one communication interface, the at least one processor configured to: determine a reciprocal cross-link interference (CLI) measurement resource configuration associated with a first user equipment (UE) and a second UE, the reciprocal CLI measurement resource configuration comprising resources associated with both a CLI measurement procedure and a round trip time (RTT) measurement procedure between the first UE and the second UE; and transmit the reciprocal CLI measurement resource configuration to the first UE and the second UE.

[0015] Another aspect relates to a non-transitory computer-readable medium comprising instructions stored thereon that, when executed, cause a first user equipment (UE) to: receive a reciprocal cross-link interference (CLI) measurement resource configuration associated with the first UE and a second UE; and perform both a CLI measurement procedure and a round trip time (RTT) measurement procedure with the second UE based on resources associated with the reciprocal CLI measurement resource configuration.

[0016] Another aspect relates to a non-transitory computer-readable medium comprising instructions stored thereon that, when executed, cause a base station to: determine a reciprocal cross-link interference (CLI) measurement resource configuration associated with a first user equipment (UE) and a second UE, the reciprocal CLI measurement resource configuration comprising resources associated with both a CLI measurement procedure and a round trip time (RTT) measurement procedure between the first UE and the second UE; and transmit the reciprocal CLI measurement resource configuration to the first UE and the second UE.

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

[0019] The accompanying drawings are presented to aid in describing the aspects of the disclosure and are provided solely for illustration of the aspects and not limitation thereof.

[0020] Figure 1

[0011] An exemplary wireless communication system in accordance with various aspects is illustrated.

[0021] Figure 2A and 2B

[0014] Example wireless network structures according to various aspects are illustrated.

[0022] Figures 3A to 3C is a simplified block diagram of several sample aspects of components that may be employed in a wireless communication node and configured to support communications as taught herein.

[0023] Figure 4A and 4Bis a diagram illustrating examples of frame structures and channels within these frame structures in accordance with aspects of the present disclosure.

[0024] Figure 4C Illustrated are exemplary PRS configurations for cells supported by a wireless node.

[0025] Figure 5 is a diagram illustrating an exemplary technique for determining the positioning of a UE using information obtained from multiple base stations.

[0026] Figure 6 is a diagram illustrating exemplary timing of round trip time (RTT) measurement signals exchanged between a base station and a UE according to aspects of the present disclosure.

[0027] Figure 7 An exemplary wireless communication system in accordance with aspects of the present disclosure is illustrated.

[0028] Figure 8 An exemplary wireless communication system in accordance with aspects of the present disclosure is illustrated.

[0029] Figure 9 An exemplary wireless communication system in accordance with aspects of the present disclosure is illustrated.

[0030] Figure 10 is a diagram illustrating exemplary timing of RTT measurement signals exchanged between a base station and a UE according to aspects of the present disclosure.

[0031] Figure 11 Illustrated are a series of symbols associated with an attacker UE and a victim UE according to other aspects of the present disclosure.

[0032] Figure 12 Illustrated are a series of symbols associated with a UE according to other aspects of the present disclosure.

[0033] Figure 13 A scenario is illustrated in which UE 1 is in proximity to UEs 2 - 4 according to an embodiment of the present disclosure.

[0034] Figure 14

[0014] Exemplary methods of wireless communication in accordance with aspects of the present disclosure are illustrated.

[0035] Figure 15

[0014] Exemplary methods of wireless communication in accordance with aspects of the present disclosure are illustrated.

[0036] Figure 16 It shows that the various aspects of the present disclosure are respectively Figure 14-15 1 is a diagram of exemplary timing of RTT measurement signals exchanged between UEs for an example implementation of a process.

[0037] Figure 17It shows that the various aspects of the present disclosure are respectively Figure 14-15 FIG. 1 is a diagram of exemplary timing of RTT measurement signals exchanged between UEs according to another example implementation of a process of FIG.

[0038] Detailed description

[0039] Aspects of the present disclosure are provided below in the description and related drawings of various examples provided for illustrative purposes. Alternative aspects can be designed without departing from the scope of the present disclosure. In addition, well-known elements in the present disclosure will not be described in detail or will be omitted to avoid obscuring the relevant details of the present disclosure.

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

[0041] Those skilled in the art will appreciate that the information and signals described below may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the following description 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 specific application, in part on the desired design, in part on the corresponding technology, etc.

[0042] In addition, many aspects are described in terms of sequences of actions performed by, for example, elements of a computing device. It will be appreciated that the various actions described herein can be performed by dedicated circuits (e.g., application specific integrated circuits (ASICs)), by program instructions being executed by one or more processors, or by a combination of the two. In addition, the sequences of actions described herein may be considered to be fully embodied within any form of non-transient computer-readable storage medium having stored therein a corresponding set of computer instructions that, upon execution, will cause or instruct an associated processor of a device to perform the functionality described herein. Thus, various aspects of the present disclosure may be embodied in several different forms, all of which have been contemplated as falling within the scope of the claimed subject matter. In addition, for each aspect described herein, the corresponding form of any such aspect may be described herein as, for example, "logic configured to perform the described actions."

[0043] As used herein, the terms "user equipment" (UE) and "base station" are not intended to be specific to or otherwise limited to any particular radio access technology (RAT), unless otherwise specified. In general, a UE can be any wireless communication device (e.g., a mobile phone, router, tablet, laptop, tracking device, wearable device (e.g., smart watch, glasses, augmented reality (AR) / virtual reality (VR) headset, etc.), vehicle (e.g., car, motorcycle, bicycle, etc.), Internet of Things (IoT) device, etc.) used by a user to communicate on a wireless communication network. A UE can be mobile or can be stationary (e.g., at certain times) and can communicate with a radio access network (RAN). As used herein, the term "UE" can be interchangeably referred to as an "access terminal" or "AT," "client device," "wireless device," "subscriber device," "subscriber terminal," "subscriber station," "user terminal" or UT, "mobile terminal," "mobile station," or variations thereof. In general, a UE can communicate with a core network via the RAN, and through the core network, the UE can connect to external networks (such as the Internet) and other UEs. Of course, other mechanisms for connecting to the core network and / or the Internet are also possible for the UE, such as through a wired access network, a wireless local area network (WLAN) network (eg, based on IEEE 802.11, etc.), and the like.

[0044] A base station may operate according to one of several RATs when in communication with a UE, depending on the network in which it is deployed, and may be referred to interchangeably as an access point (AP), network node, Node B, evolved Node B (eNB), New Radio (NR) Node B (also known as gNB or gNodeB), etc. Additionally, in some systems, a base station may provide pure edge node signaling functionality, while in other systems, a base station may provide additional control and / or network management functionality. The communication link by which a UE may send signals to a base station is referred to as an uplink (UL) channel (e.g., reverse traffic channel, reverse control channel, access channel, etc.). The communication link by which a base station may send signals to a UE is referred to as a downlink (DL) or forward link channel (e.g., paging channel, control channel, broadcast channel, forward traffic channel, etc.). As used herein, the term traffic channel (TCH) may refer to either a UL / reverse or a DL / forward traffic channel.

[0045] The term "base station" may refer to a single physical transmission point or to multiple physical transmission points that may or may not be co-located. For example, where the term "base station" refers to a single physical transmission point, the physical transmission point may be a base station antenna corresponding to a cell of the base station. Where the term "base station" refers to multiple co-located physical transmission points, the physical transmission points may be an antenna array of the base station (e.g., as in a multiple-input multiple-output (MIMO) system or where the base station employs beamforming). Where the term "base station" refers to multiple non-co-located physical transmission points, the physical transmission points may be a distributed antenna system (DAS) (a network of spatially separated antennas connected to a common source via a transmission medium) or a remote radio head (RRH) (a remote base station connected to a serving base station). Alternatively, the non-co-located physical transmission points may be a serving base station that receives measurement reports from a UE and a neighbor base station whose reference RF signal the UE is measuring.

[0046] An "RF signal" comprises an electromagnetic wave of a given frequency that transmits 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, due to the propagation characteristics of each RF signal through a multipath channel, a receiver may receive multiple "RF signals" corresponding to each transmitted RF signal. The same RF signal transmitted over different paths between a transmitter and a receiver may be referred to as a "multipath" RF signal.

[0047] According to various aspects, Figure 1 An exemplary wireless communication system 100 is illustrated. The wireless communication system 100, which may also be referred to as a wireless wide area network (WWAN), may include various base stations 102 and various UEs 104. The base stations 102 may include macrocell base stations (high-power cellular base stations) and / or small cell base stations (low-power cellular base stations). In one aspect, the macrocell base stations may include eNBs (where the wireless communication system 100 corresponds to an LTE network), or gNBs (where the wireless communication system 100 corresponds to a 5G network), or a combination of both, and the small cell base stations may include femtocells, picocells, microcells, etc.

[0048] Each base station 102 may collectively form a RAN and interface with a core network 170 (e.g., an evolved packet core (EPC) or a next generation core (NGC)) via backhaul links 122, and, via the core network 170, with one or more location servers 172. Among other functions, the base stations 102 may also perform functions related to one or more of communicating user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, RAN information management (RIM), paging, positioning, and delivery of alert messages. The base stations 102 may communicate with each other directly or indirectly (e.g., via the EPC / NGC) over backhaul links 134, which may be wired or wireless.

[0049] Base stations 102 may communicate wirelessly with UEs 104. Each base station 102 may provide communication coverage for a respective geographic coverage area 110. In one aspect, one or more cells may be supported by base stations 102 in each coverage area 110. A "cell" is a logical communication entity used to communicate with a base station (e.g., on a frequency resource, which may be referred to as a carrier frequency, component carrier, carrier, frequency band, etc.) and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID)) to distinguish between cells operating on the same or different carrier frequencies. In some cases, different cells may be configured according to different protocol types (e.g., machine type communication (MTC), narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB), or other) that may provide access to different types of UEs. In some cases, the term "cell" may also refer to a geographic coverage area (e.g., a sector) of a base station, in the sense that a carrier frequency may be detected and used for communications within a portion of geographic coverage area 110.

[0050] Although the geographic coverage areas 110 of adjacent macrocell base stations 102 may partially overlap (e.g., in a handover region), some geographic coverage areas 110 may be substantially overlapped by a larger geographic coverage area 110. For example, a small cell base station 102' may have a coverage area 110' that substantially overlaps with the coverage areas 110 of one or more macrocell base stations 102. A network that includes both small cell and macrocell base stations may be referred to as a heterogeneous network. A heterogeneous network may also include a home eNB (HeNB), which may provide service to a restricted group known as a closed subscriber group (CSG).

[0051] The communication link 120 between the base station 102 and the UE 104 may include UL (also known as reverse link) transmissions from the UE 104 to the base station 102 and / or downlink (DL) (also known as forward link) transmissions from the base station 102 to the UE 104. The communication link 120 may utilize MIMO antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link 120 may be over one or more carrier frequencies. The allocation of carriers may be asymmetric with respect to the DL and UL (e.g., more or fewer carriers may be allocated to the DL than to the UL).

[0052] The wireless communication system 100 may further include a wireless local area network (WLAN) access point (AP) 150 in communication with a WLAN station (STA) 152 in an unlicensed spectrum (e.g., 5 GHz) via a communication link 154. When communicating in the unlicensed spectrum, the WLAN STA 152 and / or the WLAN AP 150 may perform a clear channel assessment (CCA) to determine whether the channel is available before communicating.

[0053] Small cell base station 102' can operate in licensed and / or unlicensed spectrum. When operating in the unlicensed spectrum, small cell base station 102' can employ LTE or 5G technology and use the same 5 GHz unlicensed spectrum used by WLAN AP 150. Small cell base station 102' employing LTE / 5G in the unlicensed spectrum can improve coverage and / or increase capacity of the access network. LTE in the unlicensed spectrum may be referred to as LTE Unlicensed (LTE-U), Licensed Assisted Access (LAA), or MulteFire.

[0054] The wireless communication system 100 may further include a millimeter wave (mmW) base station 180 that can operate in mmW and / or near-mmW frequencies to communicate with a UE 182. Extremely high frequencies (EHF) are part of the RF spectrum within the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 mm and 10 mm. Radio waves in this frequency band may be referred to as millimeter waves. Near-mmW frequencies extend down to 3 GHz with a wavelength of 100 mm. Super high frequency (SHF) frequency bands extend between 3 GHz and 30 GHz and are also referred to as centimeter waves. Communications using mmW / near-mmW radio frequency bands 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) on the mmW communication link 184 to compensate for the extremely high path loss and short range. Furthermore, it will be appreciated that, in alternative configurations, one or more base stations 102 may also transmit using mmW or near-mmW frequencies and beamforming. Accordingly, it will be appreciated that the foregoing explanation is merely an example, and should not be construed as limiting the various aspects disclosed herein.

[0055] Transmit beamforming is a technique for focusing an RF signal in a specific direction. Conventionally, when a network node (e.g., a base station) broadcasts an RF signal, it broadcasts the signal in all directions (omnidirectionally). Using 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 the receiving device with a faster (in terms of data rate) and stronger RF signal. In order to change the directionality of the RF signal during transmission, the network node can control the phase and relative amplitude of the RF signal at each of the one or more transmitters broadcasting the RF signal. For example, the network node can use an antenna array (referred to as a "phased array" or "antenna array") that generates a beam of RF waves that can be "steered" in different directions without actually moving the antennas. Specifically, the RF currents from the transmitters are fed to the individual antennas in the correct phase relationship so that the radio waves from the separate antennas add together in the desired direction to increase radiation, while canceling out in undesired directions to suppress radiation.

[0056] The transmit beams can be quasi-colocated, meaning that they appear to the receiver (e.g., UE) to have the same parameters, regardless of whether the transmit antennas of the network nodes themselves are physically colocated. In NR, there are four types of quasi-colocation (QCL) relationships. Specifically, a given type of QCL relationship means that certain parameters about the second reference RF signal on the second beam can be derived from information about the source reference RF signal on the source beam. Therefore, 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 the 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 the 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 the second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL type D, the receiver may use the source reference RF signal to estimate spatial reception parameters of a second reference RF signal transmitted on the same channel.

[0057] In receive beamforming, a receiver uses a receive beam to amplify the RF signal detected on a given channel. For example, the receiver may increase the gain setting of the antenna array and / or adjust the phase setting of the antenna array in a particular direction to amplify (e.g., increase the gain level of) the RF signal received from that direction. Thus, when a receiver is said to be beamforming in a certain direction, it means that 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 for 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 and noise ratio (SINR), etc.) for the RF signal received from that direction.

[0058] The receive beams can be spatially correlated. This spatial relationship means that the parameters of the transmit beam used for the second reference signal can be derived from information about the receive beam of the first reference signal. For example, a UE can use a specific receive beam to receive a reference downlink reference signal (e.g., a synchronization signal block (SSB)) from a base station. The UE can then form a transmit beam based on the parameters of the receive beam to send an uplink reference signal (e.g., a sounding reference signal (SRS)) to the base station.

[0059] Note that depending on the entity forming the "downlink" beam, the beam can be a transmit beam or a receive beam. For example, if the base station is forming a downlink beam to transmit a reference signal to the UE, the downlink beam is a transmit beam. However, if the UE is forming a downlink beam, the downlink beam is a receive beam for receiving downlink reference signals. Similarly, depending on the entity forming the "uplink" beam, the beam can be a transmit beam or a receive beam. For example, if the base station is forming an uplink beam, the uplink beam is an uplink receive beam, while if the UE is forming an uplink beam, the uplink beam is an uplink transmit beam.

[0060] In 5G, the spectrum in which wireless nodes (e.g., base stations 102 / 180, UEs 104 / 182) operate is divided into multiple frequency ranges: FR1 (from 450 to 6000 MHz), FR2 (from 24250 to 52600 MHz), FR3 (above 52600 MHz), and FR4 (between FR1 and FR2). In a multi-carrier system (such as 5G), one of the carrier frequencies is referred to as the "primary carrier" or "anchor carrier" or "primary serving cell" or "PCell," and the remaining carrier frequencies are referred to as "secondary carriers" or "secondary serving cells" or "SCells." In carrier aggregation, the anchor carrier is the carrier operating on the primary frequency (e.g., FR1) utilized by the UE 104 / 182 and on the cell in which the UE 104 / 182 performs an initial radio resource control (RRC) connection establishment procedure or initiates an RRC connection re-establishment procedure. The primary carrier carries all common and UE-specific control channels. A secondary carrier is a carrier operating on a second frequency (e.g., FR2) that can be configured once an RRC connection is established between a UE 104 and an anchor carrier, and can be used to provide additional radio resources. The secondary carrier may contain only necessary signaling information and signals; for example, UE-specific signaling information and signals may not be present in the secondary carrier, as both the primary uplink and downlink carriers are typically UE-specific. This means that different UEs 104 / 182 in a cell can have different downlink primary carriers. The same is true for the uplink primary carrier. The network can change the primary carrier for any UE 104 / 182 at any time. This is done, for example, to balance the load on different carriers. Since a "serving cell" (whether a PCell or SCell) corresponds to the carrier frequency / component carrier that a base station is using for communications, the terms "cell," "serving cell," "component carrier," "carrier frequency," etc., may be used interchangeably.

[0061] For example, still referring to Figure 1In one embodiment, one of the frequencies utilized by the macrocell base station 102 may be an anchor carrier (or "PCell"), and the other frequencies utilized by the macrocell base station 102 and / or the mmW base station 180 may be secondary carriers ("SCells"). Simultaneous transmission and / or reception of multiple carriers enables the UE 104 / 182 to significantly increase its data transmission and / or reception rate. For example, two 20 MHz aggregated carriers in a multi-carrier system would theoretically result in a two-fold increase in data rate (i.e., 40 MHz) compared to the data rate achieved by a single 20 MHz carrier.

[0062] The wireless communication system 100 may further include one or more UEs (such as UE 190) that are indirectly connected to one or more communication networks via one or more device-to-device (D2D) or peer-to-peer (P2P) links. Figure 1 In the example shown in FIG1 , UE 190 has a D2D P2P link 192 with a UE 104 connected to a base station 102 (e.g., UE 190 can indirectly obtain cellular connectivity therefrom), and a D2D P2P link 194 with a WLAN STA 152 connected to a WLAN AP 150 (e.g., UE 190 can indirectly obtain WLAN-based Internet connectivity therefrom). In one example, the D2D P2P links 192 and 194 can use any well-known D2D RAT (such as LTE Direct (LTE-D), WiFi Direct (WiFi-D), etc.) to support.

[0063] The wireless communication system 100 may further include a UE 164 that may communicate with the macrocell base station 102 over the communication link 120 and / or with the mmW base station 180 over the mmW communication link 184. For example, the macrocell 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. In an aspect, the UE 164 may include a positioning component 166 that may enable the UE 164 to perform the UE operations described herein. Note that although Figure 1 Only one UE is illustrated as having a fully staggered SRS component 166, but Figure 1 Any UE in the may be configured to perform the UE operations described herein.

[0064] According to various aspects, Figure 2AAn example wireless network architecture 200 is illustrated. For example, NGC 210 (also referred to as "5GC") can be functionally considered to include control plane functions 214 (e.g., UE registration, authentication, network access, gateway selection, etc.) and user plane functions 212 (e.g., UE gateway functions, access to data networks, IP routing, etc.), which operate in conjunction to form a core network. A user plane interface (NG-U) 213 and a control plane interface (NG-C) 215 connect gNBs 222 to NGC 210, specifically to control plane functions 214 and user plane functions 212. In additional configurations, eNBs 224 can also connect to NGC 210 via NG-C 215 to control plane functions 214 and NG-U 213 to user plane functions 212. Furthermore, eNBs 224 can communicate directly with gNBs 222 via backhaul connections 223. In some configurations, the new RAN 220 may have only one or more gNBs 222, while other configurations include both one or more eNBs 224 and one or more gNBs 222. The gNB 222 or the eNB 224 may be associated with a UE 204 (e.g., Figure 1 204). Another optional aspect may include a location server 230 that may be in communication with the NGC 210 to provide location assistance to the UE 204. The location servers 230 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules spread across multiple physical servers, etc.), or alternatively may each correspond to a single server. The location servers 230 may be configured to support one or more location services for the UE 204, which may be connected to the location server 230 via the core network, the NGC 210, and / or via the Internet (not illustrated). Furthermore, the location server 230 may be integrated into a component of the core network, or alternatively may be external to the core network.

[0065] According to various aspects, Figure 2BAnother example wireless network architecture 250 is illustrated. For example, NGC 260 (also referred to as "5GC") can be functionally considered to include control plane functions provided by access and mobility management function (AMF) / user plane function (UPF) 264, and user plane functions provided by session management function (SMF) 262, which operate in conjunction to form the core network (i.e., NGC 260). User plane interface 263 and control plane interface 265 connect eNB 224 to NGC 260, specifically to SMF 262 and AMF / UPF 264, respectively. In additional configurations, gNB 222 can also connect to NGC 260 via control plane interface 265 to AMF / UPF 264 and user plane interface 263 to SMF 262. Furthermore, eNB 224 can communicate directly with gNB 222 via backhaul connection 223, regardless of whether it has direct gNB connectivity with NGC 260. In some configurations, the new RAN 220 may have only one or more gNBs 222, while other configurations include both one or more eNBs 224 and one or more gNBs 222. The gNB 222 or the eNB 224 may communicate with the UE 204 (e.g., Figure 1 The base station of the new RAN 220 communicates with the AMF side of the AMF / UPF 264 through the N2 interface and communicates with the UPF side of the AMF / UPF 264 through the N3 interface.

[0066] The functions of the AMF include registration management, connection management, reachability management, mobility management, lawful interception, session management (SM) messaging between the UE 204 and the SMF 262, a transparent proxy service for routing SM messages, access authentication and access authorization, short message service (SMS) messaging between the UE 204 and the short message service function (SMSF) (not shown), and security anchor functionality (SEAF). The AMF also interacts with the authentication server function (AUSF) (not shown) and the UE 204, and receives intermediate keys established as a result of the UE 204 authentication process. In the case of authentication based on the UMTS (Universal Mobile Telecommunications System) Subscriber Identity Module (USIM), the AMF retrieves security material from the AUSF. The functions of the AMF also include security context management (SCM). The SCM receives keys from the SEAF, which are used by the SCM to derive keys that vary depending on the access network. The functionality of the AMF also includes location service management for regulatory services, transmission of location service messages between the UE 204 and the Location Management Function (LMF) 270 and between the new RAN 220 and the LMF 270, allocation of EPS bearer identifiers for interworking with the Evolved Packet System (EPS), and notification of mobility events for the UE 204. In addition, the AMF also supports functionality for non-3GPP access networks.

[0067] The functions of the UPF include: acting as an anchor point for intra-RAT / inter-RAT mobility (when applicable), acting as an external protocol data unit (PDU) session point for interconnection to the 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, user plane quality of service (QoS) handling (e.g., UL / DL rate enforcement, reflective QoS marking in DL), UL traffic verification (mapping of service data flows (SDFs) to QoS flows), transport level packet marking in UL and DL, DL packet buffering and DL data notification triggering, and sending and forwarding one or more "end markers" to the source RAN node.

[0068] The functions of the SMF 262 include session management, UE Internet Protocol (IP) address allocation and management, selection and control of user plane functions, configuration of traffic steering for routing traffic to the correct destination at the UPF, control of part of policy enforcement and QoS, and downlink data notification. The interface through which the SMF 262 communicates with the AMF side of the AMF / UPF 264 is called the N11 interface.

[0069] Another optional aspect may include an LMF 270 that can be in communication with the NGC 260 to provide location assistance for the UE 204. The LMF 270 can be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules spread across multiple physical servers, etc.), or alternatively, each can correspond to a single server. The LMF 270 can be configured to support one or more location services for the UE 204, which can connect to the LMF 270 via the core network, the NGC 260, and / or via the Internet (not illustrated).

[0070] Figure 3A 、 3B 3C illustrate several sample components (represented by corresponding blocks) that may be incorporated into a UE 302 (which may correspond to any UE described herein), a base station 304 (which may correspond to any base station described herein), and a network entity 306 (which may correspond to or embody any network function described herein, including location server 230 and LMF 270) to support file transfer operations as taught herein. It will be appreciated that these components may be implemented in different types of devices (e.g., in an ASIC, in a system-on-chip (SoC), etc.) in different implementations. The illustrated components may also be incorporated into other devices in a communication system. For example, other devices in the system may include components similar to those described to provide similar functionality. Furthermore, a given device may include one or more of these components. For example, a device may include multiple transceiver components that enable the device to operate on multiple carriers and / or communicate via different technologies.

[0071] UE 302 and base station 304 each include a wireless wide area network (WWAN) transceiver 310 and 350, respectively, configured to communicate via one or more wireless communication networks (not shown) (such as NR networks, LTE networks, GSM networks, etc.). WWAN transceivers 310 and 350, respectively, can 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.) over a wireless communication medium of interest (e.g., a set of time / frequency resources in a specific spectrum) via at least one designated RAT (e.g., NR, LTE, GSM, etc.). WWAN transceivers 310 and 350, respectively, can be configured in various ways according to the designated RAT to transmit and encode signals 318 and 358 (e.g., messages, indications, information, etc.), and conversely, to receive and decode signals 318 and 358 (e.g., messages, indications, information, pilots, etc.). Specifically, 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.

[0072] In at least some cases, the UE 302 and the base station 304 also include wireless local area network (WLAN) transceivers 320 and 360, respectively. The WLAN transceivers 320 and 360 can be connected to one or more antennas 326 and 366, respectively, for communication via at least one designated RAT (e.g., WiFi, LTE-D, ) to communicate with other network nodes (such as other UEs, access points, base stations, etc.) over the wireless communication medium of interest. WLAN transceivers 320 and 360 can be configured in various ways according to a designated RAT to transmit and encode signals 328 and 368 (e.g., messages, indications, information, etc.), and conversely, to receive and decode signals 328 and 368 (e.g., messages, indications, information, pilots, etc.). Specifically, transceivers 320 and 360 include one or more transmitters 324 and 364, respectively, to transmit and encode signals 328 and 368, respectively, and one or more receivers 322 and 362, respectively, to receive and decode signals 328 and 368, respectively.

[0073] The transceiver circuitry including the transmitter and receiver may comprise an integrated device in some implementations (e.g., the transmitter circuitry and the receiver circuitry implemented as a single communication device), may comprise separate transmitter devices and separate receiver devices in some implementations, or may be implemented in other ways in other implementations. In one aspect, the transmitter may comprise or be coupled to multiple antennas (e.g., antennas 316, 336, and 376), such as an antenna array, that permit the respective device to perform transmit “beamforming,” as described herein. Similarly, the receiver may comprise or be coupled to multiple antennas (e.g., antennas 316, 336, and 376), such as an antenna array, that permit the respective device to perform receive beamforming, as described herein. In one aspect, the transmitter and receiver may share the same multiple antennas (e.g., antennas 316, 336, and 376), such that the respective device can only receive or transmit at a given time, but not both simultaneously. The wireless communication devices of apparatus 302 and / or 304 (eg, one or both of transceivers 310 and 320 and / or one or both of transceivers 350 and 360) may also include a network listening module (NLM) or the like for performing various measurements.

[0074] In at least some cases, devices 302 and 304 also include satellite positioning system (SPS) receivers 330 and 370. SPS receivers 330 and 370 can be connected to one or more antennas 336 and 376, respectively, for receiving SPS signals 338 and 378, respectively, such as Global Positioning System (GPS) signals, Global Navigation Satellite System (GLONASS) signals, Galileo signals, BeiDou signals, Indian Regional Navigation Satellite System (NAVIC), Quasi-Zenith Satellite System (QZSS), etc. SPS receivers 330 and 370 can include any suitable hardware and / or software for receiving and processing SPS signals 338 and 378, respectively. SPS receivers 330 and 370 request information and operations from other systems as appropriate and perform the necessary calculations to determine the position of devices 302 and 304 using measurements obtained by any suitable SPS algorithm.

[0075] The base station 304 and the network entity 306 each include at least one network interface 380 and 390 for communicating with other network entities. For example, the network interfaces 380 and 390 (e.g., one or more network access ports) can be configured to communicate with one or more network entities via a wired backhaul connection or a wireless backhaul connection. In some aspects, the network interfaces 380 and 390 can be implemented as transceivers configured to support wired signal communication or wireless signal communication. The communication can involve, for example, sending and receiving messages, parameters, or other types of information.

[0076] Apparatuses 302, 304, and 306 also include other components that may be used in conjunction with the operations disclosed herein. UE 302 includes processor circuitry that implements a processing system 332 for providing, for example, functionality related to false base station (FBS) detection as disclosed herein, and for providing other processing functionality. Base station 304 includes a processing system 384 for providing, for example, functionality related to FBS detection as disclosed herein, and for providing other processing functionality. Network entity 306 includes a processing system 394 for providing, for example, functionality related to FBS detection as disclosed herein, and for providing other processing functionality. In one aspect, processing systems 332, 384, and 394 may include, for example, one or more general-purpose processors, multi-core processors, ASICs, digital signal processors (DSPs), field programmable gate arrays (FPGAs), or other programmable logic devices or processing circuitry.

[0077] Apparatuses 302, 304, and 306 include memory circuitry implementing memory components 340, 386, and 396 (e.g., each including a memory device) for maintaining information (e.g., information indicating reserved resources, thresholds, parameters, etc.). In some cases, apparatuses 302 and 304 may include cross-link interference (CLI) round trip time (RTT) modules 342 and 388, respectively. CLI RTT modules 342 and 388 may be hardware circuits that are part of or coupled to processing systems 332 and 384, respectively, that, when executed, cause apparatus 302 to perform the functionality described herein. Alternatively, CLIRTT modules 342 and 388 may be memory modules (e.g., memory modules stored in memory components 340 and 386) that are coupled to the processing systems 332 and 384, respectively. Figures 3A-3B ), which, when executed by processing systems 332 and 384, cause devices 302 and 304 to perform the functionality described herein.

[0078] UE 302 may include one or more sensors 344 coupled to processing system 332 to provide movement and / or orientation information that is independent of motion data derived from signals received by WWAN transceiver 310, WLAN transceiver 320, and / or GPS receiver 330. By way of example, sensor(s) 344 may include an accelerometer (e.g., a microelectromechanical system (MEMS) device), a gyroscope, a geomagnetic sensor (e.g., a compass), an altimeter (e.g., a barometric altimeter), and / or any other type of motion detection sensor. Furthermore, sensor(s) 344 may include multiple different types of devices and combine their outputs to provide movement information. For example, sensor(s) 344 may use a combination of a multi-axis accelerometer and an orientation sensor to provide the ability to calculate a position in a 2D and / or 3D coordinate system.

[0079] In addition, UE 302 includes a user interface 346 for providing indications to the user (e.g., audible and / or visual indications) and / or for receiving user input (e.g., upon user actuation of a sensing device such as a keypad, touch screen, microphone, etc.). Although not shown, devices 304 and 306 may also include user interfaces.

[0080] Referring to the processing system 384 in more detail, in the downlink, IP packets from the network entity 306 may be provided to the processing system 384. The processing system 384 may implement functionality for the RRC layer, the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, and the Medium Access Control (MAC) layer. The processing system 384 may provide RRC layer functionality associated with broadcasting system information (e.g., Master Information Block (MIB), System Information Block (SIB)), 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 transmission of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, scheduling information reporting, error correction, priority handling, and logical channel prioritization.

[0081] Transmitter 354 and receiver 352 may implement Layer 1 functionality associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping onto the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. Transmitter 354 handles the mapping to the signal constellation 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 orthogonal frequency division multiplexing (OFDM) subcarriers, multiplexed with reference signals (e.g., pilots) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time-domain OFDM symbol stream. The OFDM stream is spatially precoded to generate multiple spatial streams. Channel estimates from a channel estimator can be used to determine the coding and modulation schemes and for spatial processing. The channel estimates can be derived from a reference signal and / or channel condition feedback transmitted by the UE 302. Each spatial stream can then be provided to one or more different antennas 356. The transmitter 354 can modulate an RF carrier with the corresponding spatial stream for transmission.

[0082] At UE 302, receiver 312 receives the signal via its corresponding antenna(s) 316. Receiver 312 recovers the information modulated onto the RF carrier and provides the information to processing system 332. Transmitter 314 and receiver 312 implement Layer 1 functionality associated with various signal processing functions. Receiver 312 may perform spatial processing on the information to recover any spatial streams destined for UE 302. If there are multiple spatial streams destined for UE 302, they may be combined by receiver 312 into a single OFDM symbol stream. 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 includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, as well as the reference signal, are recovered and demodulated by determining the signal constellation point most likely transmitted by base station 304. These soft decisions may be based on channel estimates calculated by a channel estimator. These soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted on the physical channel by the base station 304. These data and control signals are then provided to the processing system 332 that implements layer 3 and layer 2 functionality.

[0083] In the UL, the processing system 332 provides demultiplexing between transport channels and logical channels, packet reassembly, code decoding, header decompression, and control signal processing to recover IP packets from the core network. The processing system 332 is also responsible for error detection.

[0084] Similar to the functionality described in conjunction with DL transmissions performed by the base station 304, the processing system 332 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (ciphering, deciphering, integrity protection, integrity verification); RLC layer functionality associated with transmission of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0085] Channel estimates derived by a channel estimator from a reference signal or feedback transmitted by base station 304 may be used by transmitter 314 to select appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by transmitter 314 may be provided to different antenna(s) 316. Transmitter 314 may modulate an RF carrier with the corresponding spatial stream for transmission.

[0086] UL transmissions are processed at base station 304 in a manner similar to that described in conjunction with the receiver functionality at UE 302. Receiver 352 receives the signal through its respective antenna(s) 356. Receiver 352 recovers information modulated onto the RF carrier and provides the information to processing system 384.

[0087] In the UL, the processing system 384 provides demultiplexing between transport and logical channels, packet reassembly, code decoding, header decompression, and control signal processing to recover IP packets from the UE 302. The IP packets from the processing system 384 can be provided to the core network. The processing system 384 is also responsible for error detection.

[0088] For convenience, devices 302, 304 and / or 306 are Figures 3A-3C 1 and 2. The diagram in FIG. 1 shows various components that can be configured according to the various examples described herein. However, it will be appreciated that the illustrated blocks can have different functionality in different designs.

[0089] The various components of devices 302 , 304 , and 306 may communicate with each other via data buses 334 , 382 , and 392 , respectively. Figures 3A-3C The components of can be implemented in various ways. In some implementations, Figures 3A-3CThe components of the present invention may be implemented in one or more circuits (e.g., such as one or more processors and / or one or more ASICs (which may include one or more processors)). Here, each circuit may use and / or include 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 the processor and memory components of the UE 302 (e.g., by executing appropriate code and / or by appropriately configuring the processor components). Similarly, some or all of the functionality represented by blocks 350 to 388 may be implemented by the processor and memory components of the base station 304 (e.g., by executing appropriate code and / or by appropriately configuring the processor components). Furthermore, some or all of the functionality represented by blocks 390 to 396 may be implemented by the processor and memory components of the network entity 306 (e.g., by executing appropriate code and / or by appropriately configuring the processor components). For simplicity, various operations, actions, and / or functions are described herein as being performed “by a UE,” “by a base station,” “by a positioning entity,” etc. However, as will be appreciated, such operations, actions, and / or functions may actually be performed by a specific component or combination of components of the UE, base station, positioning entity, etc., such as the processing systems 332, 384, 394, the transceivers 310, 320, 350, and 360, the memory components 340, 386, and 396, the CLI RTT modules 342, 388, etc.

[0090] Figure 4A is a diagram 400 illustrating an example of a DL frame structure in accordance with aspects of the present disclosure. Figure 4B is a diagram 430 illustrating an example of channels within a DL frame structure in accordance with aspects of the present disclosure. Other wireless communication technologies may have different frame structures and / or different channels.

[0091] LTE, and in some cases NR, utilizes OFDM on the downlink and single-carrier frequency division multiplexing (SC-FDM) on the uplink. However, unlike LTE, NR also has the option of using OFDM on the uplink. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, which are also often referred to as tones, bins, etc. Each subcarrier can be modulated with data. Generally speaking, modulation symbols are sent in the frequency domain for OFDM and in the time domain for SC-FDM. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the subcarrier spacing can be 15 kHz, and the minimum resource allocation (resource block) can be 12 subcarriers (or 180 kHz). Therefore, for system bandwidths of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), the nominal FFT size can be equal to 128, 256, 512, 1024, or 2048, respectively. The system bandwidth may be further divided into subbands. For example, a subband may cover 1.08 MHz (ie, 6 resource blocks), and there may be 1, 2, 4, 8, or 16 subbands for system bandwidths of 1.25, 2.5, 5, 10, or 20 MHz, respectively.

[0092] LTE supports a single parameter set (subcarrier spacing, symbol length, etc.). In contrast, NR can support multiple parameter designs. For example, subcarrier spacing of 15kHz, 30kHz, 60kHz, 120kHz, and 204kHz or larger may be available. Table 1 provided below lists some of the various parameters used for different NR parameter sets.

[0093]

[0094] Table 1

[0095] exist Figure 4A and 4B In the example of , a parameter design of 15 kHz is used. Therefore, in the time domain, a frame (e.g., 10 ms) is divided into 10 equally sized subframes, each 1 ms, and each subframe includes one time slot. Figure 4A and 4B , time is represented horizontally (eg, on the X-axis), where time increases from left to right, and frequency is represented vertically (eg, on the Y-axis), where frequency increases (or decreases) from bottom to top.

[0096] A resource grid may be used to represent a time slot, each of which includes one or more time-concurrent resource blocks (RBs) (also known as physical RBs (PRBs)) in the frequency domain. The resource grid is further divided into a plurality of resource elements (REs). An RE may correspond to one symbol length in the time domain and one subcarrier in the frequency domain. Figure 4A and 4B In the parameter design of [1], for a normal cyclic prefix, an RB may contain 12 consecutive subcarriers in the frequency domain and 7 consecutive symbols in the time domain (OFDM symbols for DL ​​and SC-FDMA symbols for UL), for a total of 84 REs. For an extended cyclic prefix, an RB may contain 12 consecutive subcarriers in the frequency domain and 6 consecutive symbols in the time domain, for a total of 72 REs. The number of bits carried by each RE depends on the modulation scheme.

[0097] like Figure 4A As explained in [1], some REs carry DL reference (pilot) signals (DL-RS) for channel estimation at the UE. DL-RS may include a demodulation reference signal (DMRS) and a channel state information reference signal (CSI-RS), with exemplary locations at Figure 4A are marked with an "R".

[0098] Figure 4B An example of various channels within a DL subframe of an explanation frame. The physical downlink control channel (PDCCH) carries DL control information (DCI) within one or more control channel elements (CCEs), each CCE comprising 9 RE groups (REGs), each REG comprising 4 consecutive REs in an OFDM symbol. DCI carries information about UL resource allocations (persistent and non-persistent) and a description of DL data transmitted to the UE. Multiple (e.g., up to 8) DCIs can be configured in the PDCCH, and these DCIs can have one of a variety of formats. For example, there are different DCI formats for UL scheduling, for non-MIMO DL scheduling, for MIMO DL scheduling, and for UL power control.

[0099] The primary synchronization signal (PSS) is used by the UE to determine the subframe / symbol timing and the physical layer identity. The secondary synchronization signal (SSS) is used by the UE to determine the physical layer cell identity group number and the radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the PCI. Based on the PCI, the UE can determine the position of the aforementioned DL-RS. The physical broadcast channel (PBCH) carrying the MIB can be logically grouped with the PSS and SSS to form an SSB (also known as SS / PBCH). The MIB provides the number of RBs in the DL system bandwidth and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information that is not transmitted through the PBCH (such as system information blocks (SIBs)), and paging messages.

[0100] In some cases, Figure 4A The DL RS illustrated in may be a downlink (DL) positioning reference signal (PRS). Figure 4C An exemplary DL PRS configuration 400C for a cell supported by a wireless node, such as base station 102, is illustrated. Figure 4C It shows how the DL PRS positioning opportunity is determined by the system frame number (SFN), the subframe offset (Δ PRS )452C and DLPRS periodicity (T PRS )420C. Typically, the cell-specific DL PRS subframe configuration is determined by a “PRS configuration index” included in the Observed Time Difference of Arrival (OTDOA) assistance data. PRS To define. DL PRS periodicity (T PRS )420C and the cell-specific subframe offset (Δ PRS ) is based on DL PRS configuration index I PRS As defined in Table 2 below.

[0101]

[0102] Table 2 – DL PRS configuration

[0103] The DL PRS configuration is defined with reference to the SFN of the cell that transmits the DL PRS. PRS The downlink subframes include the first subframe of the first DL PRS positioning opportunity, and the DL PRS instance can meet the following requirements:

[0104]

[0105] where n f is SFN and 0≤n f ≤1023, n s By nf The timeslot number within the defined radio frame and 0≤n s ≤19, T PRS is the DL PRS periodicity 420C, and Δ PRS It is the subframe offset 452C that varies from cell to cell.

[0106] like Figure 4C As shown in , the subframe offset Δ varies from cell to cell. PRS 452C may be defined in terms of the number of subframes transmitted starting from system frame number 0 (time slot "number 0", which is labeled as time slot 450C) to the start of the first (subsequent) DL PRS positioning opportunity. Figure 4C In the example of FIG. 4 , the number of consecutive positioning subframes (N ) in each consecutive DL PRS positioning opportunity 418C-a, 418C-b, and 418C-c is PRS ) is equal to 4. That is, each shaded block representing DL PRS positioning opportunities 418C-a, 418C-b, and 418C-c represents four subframes.

[0107] In some aspects, when a UE receives a PRS configuration index I in OTDOA assistance data for a particular cell, PRS When , the UE can use Table 2 to determine the DL PRS periodicity T PRS 420C and DL PRS subframe offset Δ PRS The UE may then determine the radio frame, subframe, and time slot when the DL PRS is scheduled in the cell (e.g., using equation (1)). The OTDOA assistance data may be determined, for example, by a location server (e.g., location server 230, LMF 270) and include assistance data for a reference cell and several neighbor cells supported by each base station.

[0108] Typically, DL PRS opportunities from all cells in the network using the same frequency are aligned in time and may have a fixed, known time offset (e.g., a cell-specific subframe offset 452C) relative to other cells in the network using different frequencies. In a SFN synchronous network, all wireless nodes (e.g., base stations 102) may be aligned on both frame boundaries and system frame numbers. Thus, in a SFN synchronous network, all cells supported by each wireless node may use the same PRS configuration index for any particular frequency of DL PRS transmission. On the other hand, in a SFN asynchronous network, each wireless node may be aligned on frame boundaries but not on system frame numbers. Thus, in a SFN asynchronous network, the PRS configuration index for each cell may be individually configured by the network to align the DL PRS opportunities in time.

[0109] If the UE can obtain the cell timing (e.g., SFN) of at least one cell (e.g., a reference cell or a serving cell), the UE can determine the timing of the DL PRS opportunities of the reference cell and neighbor cells for OTDOA positioning. The timing of other cells can then be derived by the UE, for example, based on an assumption that DL PRS opportunities from different cells overlap.

[0110] The set of resource elements used to transmit DL PRS is called a "PRS resource". The set of resource elements may span multiple PRBs in the frequency domain and N (e.g., 1 or more) consecutive symbols within a slot in the time domain. In a given OFDM symbol, a DL PRS resource occupies consecutive PRBs. A DL PRS resource is described by at least the following parameters: a DL PRS resource identifier (ID), a sequence ID, a comb size N, a resource element offset in the frequency domain, a starting slot and a starting symbol, the number of symbols per DL PRS resource (i.e., the duration of the DL PRS resource), and QCL information (e.g., QCL with other DL reference signals). In some designs, one antenna port is supported. The comb size indicates the number of subcarriers carrying DL PRS in each symbol. For example, a comb size of -4 means that every fourth subcarrier of a given symbol carries DL PRS.

[0111] A "PRS resource set" is a group of PRS resources used to transmit a DL PRS signal, where each DL PRS resource has a PRS resource ID. In addition, the DL PRS resources in the DL PRS resource set are associated with the same transmit reception point (TRP). The PRS resource ID in the PRS resource set is associated with a single beam transmitted from a single TRP (wherein a TRP may transmit one or more beams). That is, each DL PRS resource in the DL PRS resource set may be transmitted on a different beam, and as such, a "PRS resource" may also be referred to as a "beam". Note that this does not have any implication as to whether the TRP and beam in which the DL PRS is transmitted are known to the UE. A "DL PRS opportunity" is an example of a periodically repeating time window (e.g., a group of one or more consecutive time slots) in which a DL PRS is expected to be transmitted. A DL PRS opportunity may also be referred to as a "DL PRS positioning opportunity," "positioning opportunity," or simply "opportunity."

[0112] Note that the terms "positioning reference signal" and "PRS" may sometimes refer to specific reference signals used for positioning in LTE or NR systems. However, as used herein, unless otherwise indicated, the terms "positioning reference signal" and "PRS" refer to any type of reference signal that can be used for positioning, such as, but not limited to, PRS signals in LTE or NR, navigation reference signals (NRS) in 5G, transmitter reference signals (TRS), cell-specific reference signals (CRS), channel state information reference signals (CSI-RS), primary synchronization signals (PSS), secondary synchronization signals (SSS), SSB, etc.

[0113] Uplink (UL) reference signals can also be configured as PRSs. For example, SRSs are uplink-only signals transmitted by the UE to help the base station obtain channel state information (CSI) for each user. Channel state information describes how the RF signal propagates from the UE to the base station and accounts for the combined effects of scattering, fading, and power loss with distance. Systems use SRSs for resource scheduling, link adaptation, massive MIMO, beam management, and more.

[0114] Several enhancements to the previous definition of SRS have been proposed for SRS for positioning (SRS-P) (e.g., as used herein, SRS-P is an example of UL PRS), such as a new staggering pattern within SRS resources, a new comb type for SRS, a new sequence for SRS, a higher number of SRS resource sets per component carrier, and a higher number of SRS resources per component carrier. In addition, the parameters "SpatialRelationInfo" and "PathLossReference" are to be configured based on DL RSs from neighboring TRPs. Still further, one SRS resource can be transmitted outside the active bandwidth part (BWP), and one SRS resource can span multiple component carriers. Finally, a UE can transmit over the same transmit beam from multiple SRS resources for UL-AoA. All of these are features in addition to the current SRS framework, which is configured through RRC higher layer signaling (and potentially triggered or activated through MAC control elements (CEs) or downlink control information (DCI)).

[0115] As mentioned above, the SRS in NR is a UE-specifically configured reference signal transmitted by the UE for the purpose of sounding the uplink radio channel. Similar to the CSI-RS, this type of sounding provides varying levels of knowledge of the radio channel characteristics. At one extreme, the SRS can be used simply at the gNB to obtain signal strength measurements, e.g., for UL beam management purposes. At the other extreme, the SRS can be used at the gNB to obtain detailed amplitude and phase estimates as a function of frequency, time, and space. In NR, channel sounding with SRS supports a more diverse set of use cases than LTE (e.g., downlink CSI acquisition for reciprocity-based gNB transmit beamforming (downlink MIMO); uplink CSI acquisition for link adaptation and codebook / non-codebook-based precoding for uplink MIMO, uplink beam management, etc.).

[0116] SRS can be configured using various options. The time / frequency mapping of SRS resources is defined by the following properties.

[0117] Time duration N 码元 SRS - The time duration of the SRS resource can be 1, 2 or 4 consecutive OFDM symbols within a slot, in contrast to LTE which only allows a single OFDM symbol per slot.

[0118] • Starting symbol position 10—The starting symbol of the SRS resource can be located anywhere within the last 6 OFDM symbols of a slot, provided that the resource does not cross the end-of-slot boundary.

[0119] Repetition factor R—For SRS resources configured with frequency hopping, repetition allows the same set of subcarriers to be sounded in R consecutive OFDM symbols before the next hop occurs (as used herein, "hop" specifically refers to frequency hopping). For example, the values ​​of R are 1, 2, 4, where R ≤ N 码元 SRS .

[0120] Transmission comb spacing K TC and comb offset k TC - SRS resources can occupy resource elements (REs) in a frequency domain comb structure, where the comb spacing is 2 or 4 REs as in LTE. This structure allows frequency domain multiplexing of different SRS resources for the same or different users on different combs, where different combs are offset from each other by an integer number of REs. The comb offset is defined with respect to the PRB boundary and can take values ​​of 0, 1, ..., K TC -1 RE range. Therefore, for the comb tooth spacing K TC =2, there are 2 different comb teeth that can be used for multiplexing (if needed), and for the comb tooth spacing K TC=4, there are 4 different comb teeth available.

[0121] • Periodicity and slot offset for periodic / semi-persistent SRS cases.

[0122] The sounding bandwidth within the bandwidth section.

[0123] For low-latency positioning, the gNB may trigger PRS (e.g., UL PRS (such as UL SRS-P), DL PRS, RTT procedure with Rx-Tx time difference measurement including both UL PRS and DL PRS, etc.) via DCI (e.g., the transmitted SRS-P may include repetitions or beam sweeping to enable several gNBs to receive the SRS-P). Alternatively, the gNB may send information about aperiodic PRS (e.g., UL PRS or DL ​​PRS) transmission to the UE (e.g., the configuration may include information about PRS from multiple gNBs to enable the UE to perform timing calculations for positioning (UE-based) or for reporting (UE-assisted)). Although various embodiments of the present disclosure relate to DL PRS-based positioning procedures, some or all of such embodiments may also be applicable to UL SRS-P-based (or more generally, UL PRS-based) positioning procedures.

[0124] Note that the terms "sounding reference signal," "SRS," and "SRS-P" may sometimes refer to specific reference signals used for positioning in LTE or NR systems. However, as used herein, unless otherwise indicated, the terms "sounding reference signal," "SRS," and "SRS-P" refer to any type of reference signal that can be used for positioning, such as, but not limited to, SRS signals in LTE or NR, navigation reference signals (NRS) in 5G, transmitter reference signals (TRS), random access channel (RACH) signals used for positioning (e.g., RACH preambles, such as Msg-1 in a 4-step RACH procedure or Msg-A in a 2-step RACH procedure), etc.

[0125] Various NR positioning aspects introduced by 3GPP Release 16 relate to improving the position accuracy of positioning schemes involving measurement(s) associated with one or more UL or DL ​​PRSs (e.g., higher bandwidth (BW), FR2 beam sweeping, angle-based measurements such as angle of arrival (AoA) and angle of departure (AoD) measurements, multi-cell round trip time (RTT) measurements, etc.). If latency reduction is a priority, UE-based positioning techniques are typically used (e.g., DL-only techniques without UL position measurement reports). However, if latency is less critical, UE-assisted positioning techniques can be used, whereby data measured by the UE is reported to a network entity (e.g., location server 230, LMF 270, etc.). By implementing the LMF in the RAN, the latency associated with UE-assisted positioning techniques can be reduced to some extent.

[0126] Layer 3 (L3) signaling (e.g., RRC or Position Positioning Protocol (LPP)) is typically used to transmit reports that include location-based data associated with UE-assisted positioning techniques. Compared to Layer 1 (L1 or PHY layer) signaling or Layer 2 (L2 or MAC layer) signaling, L3 signaling is associated with relatively high latency (e.g., above 100 ms). In some scenarios, lower latency (e.g., less than 100 ms, less than 10 ms, etc.) for location-based reporting between the UE and the RAN may be desirable. In such scenarios, L3 signaling may not be able to achieve these lower latency levels. L3 signaling for positioning measurements may include any combination of the following:

[0127] One or more TOA, TDOA, RSRP or Rx-Tx time difference measurements,

[0128] One or more AoA / AoD (e.g., currently only DL AoA and UL AoD are reported for gNB->LMF as agreed) measurements,

[0129] One or more multipath reporting measurements, e.g., per-path ToA, RSRP, AoA / AoD (e.g., per-path ToA currently only allowed in LTE)

[0130] One or more motion states (e.g., walking, driving, etc.) and trajectories (e.g., currently for a UE), and / or

[0131] • One or more report quality indicators.

[0132] Recently, L1 and L2 signaling have been contemplated for use in association with DL PRS-based reporting. For example, L1 and L2 signaling are currently used in some systems to transmit CSI reports (e.g., reports of channel quality indication (CQI), precoding matrix indicator (PMI), layer indicator (Li), L1-RSRP, etc.). A CSI report may include a set of fields in a predefined order (e.g., defined by the relevant standard). A single UL transmission (e.g., on PUSCH or PUCCH) may include multiple reports, referred to herein as "sub-reports," which are arranged according to a predefined priority (e.g., defined by the relevant standard). In some designs, the predefined order may be based on the associated sub-report periodicity (e.g., aperiodic / semi-persistent / periodic (A / SP / P) on PUSCH / PUCCH), the measurement type (e.g., L1-RSRP or non-L1-RSRP), the serving cell index (e.g., in a carrier aggregation (CA) scenario), and the report configuration ID (reportconfigID). For 2-part CSI reporting, all reported parts 1 are grouped together, and part 2 is grouped separately, and each group is encoded separately (e.g., the part 1 payload size is fixed based on configuration parameters, while the part 2 size is variable and depends on the configuration parameters and also on the associated part 1 content). The number of coded bits / symbols to be output after coding and rate matching is calculated based on the number of input bits and the beta factor as per the relevant standard. A link (e.g., time offset) is defined between the instance of the RS being measured and the corresponding report. In some designs, CSI-like reporting based on DL PRS measurement data using L1 and L2 signaling can be implemented.

[0133] Figure 5 An exemplary DL PRS 500 is illustrated for processing by a wireless communication system in accordance with aspects of the present disclosure. Figure 5 In the IEEE 802.11a positioning session (TPRS), a PRS transmit beam is transmitted by a cell (or transmit receive point (TRP)) at a series of beam-specific positioning occasions in corresponding time slots / symbols. These PRS transmit beams are received at the UE as PRS receive beams and then processed (e.g., for various positioning measurements by the UE).

[0134] Figure 6 An exemplary wireless communication system 600 is illustrated in accordance with aspects of the present disclosure. Figure 6In the example, eNB2 and eNB3 are synchronized with each other so that TOA (e.g., TDOA) measurements (labeled as T1, T2, and T3) can be used to generate a positioning estimate for the UE. Multiple TDOA measurements can be used for triangulation (e.g., four or more cells or eNBs). In TDOA-based positioning schemes, network synchronization errors are the main bottleneck in positioning accuracy.

[0135] Another positioning technique that requires cell (or satellite) synchronization is based on observed time difference of arrival (OTDOA).An example of an OTDOA-based positioning solution is GPS, which is limited to an accuracy of 50-100 ns (e.g., 15-30 meters).

[0136] In NR, precise timing synchronization across the network is not required. Instead, coarse timing synchronization (e.g., within the cyclic prefix (CP) duration of an OFDM symbol) across gNBs is sufficient. RTT-based methods typically only require coarse timing synchronization and are therefore the preferred positioning method in NR.

[0137] In network-centric RTT estimation, a serving base station (e.g., base station 102) instructs a UE (e.g., UE 104) to scan / receive RTT measurement signals (e.g., PRS) on the serving base station and two or more neighboring base stations (e.g., at least three base stations are required). The one or more base stations transmit RTT measurement signals on low reuse resources (e.g., resources used by the base station to transmit system information) allocated by the network (e.g., location server 230, LMF 270). The UE records the arrival time (also known as reception time, received time, received time, or time of arrival (ToA)) of each RTT measurement signal relative to the current downlink timing of the UE (e.g., as derived by the UE from the DL signal received from its serving base station), and (e.g., when instructed by its serving base station) transmits a common or individual RTT response message (e.g., SRS, UL-PRS) to the one or more base stations, and may calculate the difference T between the ToA of the RTT measurement signal and the transmission time of the RTT response message. Rx→Tx (For example, Figure 10 T in Rx→Tx 1012) is included in the payload of each RTT response message. The RTT response message will include a reference signal from which the base station can infer the ToA of the RTT response. By comparing the difference between the transmission time of the RTT measurement signal and the ToA of the RTT response, the base station can infer the ToA of the RTT response. Tx→Rx (For example, Figure 10 T in Tx→Rx 1022) Differences from UE reports T Rx→Tx (For example, Figure 10 T in Rx→Tx1012), the base station can infer the propagation time between the base station and the UE, from which the base station can determine the distance between the UE and the base station by assuming the speed of light during the propagation time.

[0138] UE-centric RTT estimation is similar to the network-based approach, except that the UE transmits uplink RTT measurement signals (e.g., when instructed by the serving base station), which are received by multiple base stations in the vicinity of the UE. Each involved base station responds with a downlink RTT response message, which may include in the RTT response message payload the time difference between the ToA of the RTT measurement signal at the base station and the transmission time of the RTT response message from the base station.

[0139] For both network-centric and UE-centric procedures, the side performing the RTT calculation (the network or the UE) typically (but not always) transmits a first message or signal (e.g., an RTT measurement signal), and the other side responds with one or more RTT response messages or signals, which may include the difference between the ToA of the first message or signal and the transmission time of the RTT response message or signal.

[0140] Figure 7 An exemplary wireless communication system 700 is illustrated in accordance with aspects of the present disclosure. Figure 7 In an example, a UE 704 (which may correspond to any UE described herein) is attempting to calculate an estimate of its position, or assist another entity (e.g., a base station or core network component, another UE, a location server, a third-party application, etc.) in calculating an estimate of its position. The UE 704 may communicate wirelessly with a plurality of base stations 702-1, 702-2, and 702-3 (collectively referred to as base stations 702, which may correspond to any base station described herein) using RF signals and standardized protocols for modulating the RF signals and exchanging information packets. By extracting different types of information from the exchanged RF signals and utilizing the layout of the wireless communication system 700 (i.e., base station locations, geometry, etc.), the UE 704 may determine its position, or assist in determining its position in a predefined reference coordinate system. In one aspect, the UE 704 may specify its position using a two-dimensional coordinate system; however, the aspects disclosed herein are not limited thereto and may also be applicable to determining position using a three-dimensional coordinate system where additional dimensions are desired. Additionally, while Figure 7 One UE 704 and three base stations 702 are illustrated, but as will be appreciated, there may be more UEs 704 and more base stations 702 .

[0141] To support position estimation, a base station 702 may be configured to broadcast reference RF signals (e.g., PRS, NRS, CRS, TRS, CSI-RS, PSS, SSS, etc.) to UEs 704 in its coverage area, enabling the UEs 704 to measure characteristics of such reference RF signals. For example, a UE 704 may measure the ToA of specific reference RF signals (e.g., PRS, NRS, CRS, CSI-RS, etc.) transmitted by at least three different base stations 702, and may report these ToA (and additional information) back to the serving base station 702 or another positioning entity (e.g., location server 230, LMF 270) using an RTT positioning method.

[0142] In an aspect, although described as the UE 704 measuring the reference RF signal from the base station 702, the UE 704 may measure the reference RF signal from one of the multiple cells supported by the base station 702. In the event that the UE 704 measures the reference RF signal transmitted by the cell supported by the base station 702, the at least two other reference RF signals measured by the UE 704 to perform the RTT procedure will be from cells supported by base stations 702 different from the first base station 702 and may have good or poor signal strength at the UE 704.

[0143] In order to determine the location (x, y) of the UE 704, the entity determining the location of the UE 704 needs to know the location of the base station 702, which can be expressed in a reference coordinate system as (x k ,y k ), among which Figure 7 In the example of , k = 1, 2, 3. If one of base station 702 (e.g., a serving base station) or UE 704 determines the location of UE 704, the location of the base station 702 in question may be provided to the serving base station 702 or UE 704 by a location server (e.g., location server 230, LMF 270) that has knowledge of the network geometry. Alternatively, the location server may use the known network geometry to determine the location of UE 704.

[0144] The UE 704 or the corresponding base station 702 can determine the distance (d k , where k=1, 2, 3). In one aspect, determining the RTT 710 of signals exchanged between the UE 704 and any base station 702 and converting the RTT 710 to a distance (d kAs discussed further below, RTT techniques can measure the time between sending a signaling message (e.g., a reference RF signal) and receiving a response. These methods can utilize calibration to remove any processing delays. In some environments, it can be assumed that the processing delays of the UE 704 and the base station 702 are the same. However, such an assumption may not hold true in practice.

[0145] Once each distance d is determined k , UE 704, base station 702 or location server (e.g., location server 230, LMF 270) can solve the location (x, y) of UE 704 by using various known geometric design techniques (e.g., such as trilateration). Figure 7 It can be seen that the location of UE 704 is ideally located at the common intersection of three semicircles, each of which has a radius d k and center (x k ,y k ), where k = 1, 2, 3.

[0146] In some examples, additional information may be obtained in the form of an angle of arrival (AoA) or angle of departure (AoD), which defines a linear direction (e.g., which may be in the horizontal plane or in three dimensions) or a range of possible directions (e.g., of the UE 704 as seen from the location of the base station 702). The intersection of the two directions at or near a point (x, y) may provide another estimate of the location of the UE 704.

[0147] A position estimate (e.g., for a UE 704) may be referred to by other names, such as a position estimate, a position, a fix, a position fix, a fix, etc. A position estimate may be geodetic and include coordinates (e.g., latitude, longitude, and possibly altitude), or may be municipal and include a street address, a postal address, or some other verbal description of the location. A position estimate may further be defined relative to some other known location or in absolute terms (e.g., using latitude, longitude, and possibly altitude). A position estimate may include an expected error or uncertainty (e.g., by including an area or volume within which the position is expected to be contained with some specified or default confidence level).

[0148] Figure 8 An exemplary wireless communication system 800 is illustrated in accordance with aspects of the present disclosure. Figure 7 When describing an example of a multi-cell RTT positioning solution, Figure 8 Depicts an example of a single-cell RTT positioning scheme. Figure 8 In , RTT1 is measured together with AoD1 associated with the beam over which DL PRS is transmitted from the cell to the UE. Figure 8The overlapping region of RTT1 and AoD1 depicted in provides a coarse position estimate for the associated UE.

[0149] Figure 9 An exemplary wireless communication system 900 is illustrated in accordance with various aspects of the present disclosure. Specifically, Figure 10 Described is a directional positioning scheme that determines two AoA or AoD measurements, where an overlapping area of ​​the two AoA or AoD measurements provides a coarse position estimate for the associated UE.

[0150] Figure 10 is a diagram 1000 illustrating exemplary timing of RTT measurement signals exchanged between a base station 1002 (e.g., any base station described herein) and a UE 1004 (e.g., any UE described herein) in accordance with aspects of the present disclosure. Figure 10 In the example of FIG, the base station 1002 sends an RTT measurement signal 1010 (eg, PRS, NRS, CRS, CSI-RS, etc.) to the UE 1004 at time t1. The RTT measurement signal 1010 has a certain propagation delay T when traveling from the base station 1002 to the UE 1004. Prop At time t2 (ToA of the RTT measurement signal 1010 at the UE 1004), the UE 1004 receives / measures the RTT measurement signal 1010. After a certain UE processing time, the UE 1004 transmits the RTT response signal 1020 at time t3. Prop Thereafter, the base station 1002 receives / measures the RTT response signal 1020 from the UE 1004 at time t4 (ToA of the RTT response signal 1020 at the base station 1002 ).

[0151] To identify the ToA (e.g., t2) of a reference signal (e.g., RTT measurement signal 1010) transmitted by a given network node (e.g., base station 1002), a receiver (e.g., UE 1004) first jointly processes all resource elements (REs) on the channel on which the transmitter is transmitting the reference signal and performs an inverse Fourier transform to convert the received reference signal to the time domain. This conversion of the received reference signal to the time domain is called an estimate of the channel energy response (CER). The CER shows peaks on the channel that vary over time, and therefore the earliest "significant" peak should correspond to the ToA of the reference signal. Typically, the receiver will use a noise-related quality threshold to filter out false local peaks, thereby assuming that the significant peaks on the channel are correctly identified. For example, the receiver may select a ToA estimate that is the earliest local maximum of the CER, which is at least X dB above the median CER and at most Y dB below the main peak on the channel. The receiver determines the CER for each reference signal from each transmitter in order to determine the ToA for each reference signal from different transmitters.

[0152] In some designs, the RTT response signal 1020 may explicitly include the difference between time t3 and time t2 (ie, T Rx→Tx 1012). Using this measurement and the difference between time t4 and time t1 (ie, T Tx→Rx 1022), the base station 1002 (or other positioning entities, such as the location server 230, the LMF 270) can calculate the distance to the UE 1004 as:

[0153]

[0154] Where c is the speed of light. Figure 10 It is not explicitly explained in

[15] , but an additional source of delay or error may be due to the UE and gNB hardware group delay in positioning the location.

[0155] Cross-link interference (CLI) is UE-to-UE interference where a transmission from an "aggressor" UE causes interference at a "victim" UE. For example, in a TDD system, nearby UEs have different UL-DL slot formats, and the victim UE may receive a transmission from the aggressor UE within its UL (transmit) symbols that collide with the victim UE's DL (receive) symbols (i.e., interfering symbols).

[0156] Figure 11 Illustrated is a series of symbols 1100 associated with an aggressor UE 1 and a victim UE 2 according to other aspects of the present disclosure. These symbols include uplink symbols identified as U (where the respective UE is transmitting), downlink symbols designated as D (where the respective UE is receiving), and transition symbols designated as F (where the respective UE is neither receiving nor transmitting). Figure 11 In , CLI may occur at symbol 1102, where UE 1 is configured with U symbols (eg, PUCCH, PUSCH, PRACH preamble, SRS, etc.) and UE 2 is configured with D symbols.

[0157] The network can configure CLI interference resources for interference management. In this case, the victim UE can be configured to measure the CLI from the aggressor UE in the CLI interference resources. Generally speaking, this CLE measurement procedure does not affect the UL transmission of the aggressor UE.

[0158] In 3GPP Release 16, Layer 3 measurement and reporting mechanisms are defined for CLI. For example, CLI management may include SRS-RSRP or CLI received signal strength indicator (RSSI). In some designs, CLI measurement resource configuration may be provided in a measurement object. In some designs, this may include the periodicity, frequency, RB, and OFDM symbol for CLI measurement.

[0159] Dynamic TDD can include scheduling-based DL / UL switching. At certain times, in a format where UE 1 performs UL transmission and UE 2 performs DL reception, UE 1 may introduce interference to UE 2. At other times, in a different timeslot configuration, UE 2 may also introduce interference to UE 1. In such scenarios, reciprocal (bidirectional or bilateral) CLI can be measured.

[0160] Figure 12 Illustrated is a series of symbols 1200 associated with UE 1 and UE 2 according to other aspects of the present disclosure. CLI from UE 1 to UE 2 occurs at symbol 1202, where UE 2 is configured with U symbols (e.g., PUCCH, PUSCH, PRACH preamble, SRS, etc.) and UE 2 is configured with D symbols. CLI from UE 2 to UE 1 occurs at symbol 1204, where UE 2 is configured with U symbols (e.g., PUCCH, PUSCH, PRACH preamble, SRS, etc.) and UE 1 is configured with D symbols.

[0161] Figure 13 Scenario 1300 is illustrated in which UE 1 is in proximity to UEs 2-4, according to an embodiment of the present disclosure. The relative distance between UE 1 and each of UEs 2-4 can be estimated in a manner similar to the BS-UE RTT measurements described above and subsequently factored into one or more positioning measurements. Generally, such RTT measurements can be dynamically scheduled by the network, which can be somewhat burdensome.

[0162] Various embodiments of the present disclosure are directed to opportunistically utilizing CLI measurement resource configuration to perform RTT measurements between UEs. In some designs, RTT measurements can be piggybacked onto the CLI measurement procedure, while the CLI measurement procedure itself remains unchanged. Such an approach can provide various technical advantages, such as simplifying the implementation of UE-to-UE measurement procedures and reducing resource utilization associated with UE-to-UE measurement procedures.

[0163] Figure 14 Illustrated is an exemplary wireless communication process 1400 in accordance with aspects of the present disclosure. Process 1400 may be performed by a first UE, such as UE 302.

[0164] At 1410, a first UE (e.g., receiver 312, receiver 322, etc.) receives a reciprocal CLI measurement resource configuration associated with the first UE and a second UE. For example, the CLI measurement resource configuration may be received from a base station, such as BS 304. In some designs, the CLI measurement resource configuration may configure first resources associated with a first reference signal used for positioning from the first UE to the second UE and second resources associated with a second reference signal used for positioning from the second UE to the first UE. For example, the first and / or second reference signals may correspond to an SRS, an SRS-P (e.g., a "legacy" positioning SRS), or a sidelink reference signal (SL-RS).

[0165] At 1420, the first UE (e.g., receiver 312, transmitter 314, receiver 322, transmitter 324, etc.) performs a CLI measurement procedure and an RTT measurement procedure with the second UE based on resources associated with the reciprocal CLI measurement resource configuration. As will be described in more detail below, the first UE can be an initiator UE that transmits an initial reference signal for positioning for the RTT measurement procedure, or a responder UE that transmits a response reference signal for positioning.

[0166] Figure 15 Illustrated is an exemplary wireless communication process 1500 in accordance with aspects of the present disclosure. Process 1500 may be performed by a base station, such as BS 304.

[0167] At 1510, the BS 304 (e.g., the processing system 384, the CLI RTT module 388, etc.) determines a reciprocal CLI measurement resource configuration associated with a first UE and a second UE, the reciprocal CLI measurement resource configuration including resources associated with both a CLI measurement procedure and a round trip time (RTT) measurement procedure between the first UE and the second UE. In some designs, the CLI measurement resource configuration may configure first resources associated with a first reference signal used for positioning from the first UE to the second UE and second resources associated with a second reference signal used for positioning from the second UE to the first UE. For example, the first and / or second reference signals may correspond to an SRS, an SRS-P (e.g., a "legacy" positioning SRS), or an SL-RS.

[0168] At 1520, BS 304 (eg, transmitter 354, transmitter 364, etc.) transmits the reciprocal CLI measurement resource configuration to the first UE and the second UE.

[0169] Reference Figure 14-15In some designs as mentioned above, the first UE may correspond to an initiator UE associated with an RTT measurement procedure. In this case, the first UE transmits a first reference signal for positioning to the second UE on a first resource associated with a reciprocal CLI measurement resource configuration, and measures a first time (t1) associated with transmitting the first reference signal for positioning. In response to transmitting the first reference signal, the first UE further receives a second reference signal for positioning from the second UE on a second resource associated with the reciprocal CLI measurement resource configuration, and measures a second time (t4) associated with receiving the second reference signal for positioning. In some designs, the first UE may report timing measurement information associated with a delay from the measured first time (t1) to the measured second time (t4). For example, the report may be directed to an entity that calculates RTT, such as the second UE or a network entity (e.g., a base station, or a network entity (such as an LMF) via the base station). In some designs, the first UE may receive an indication of the RTT associated with the RTT measurement procedure from the base station based at least in part on the reported timing measurement information. In some designs, the first UE may be the entity that calculates RTT. In this case, the first UE may further receive, from the second UE, timing measurement information associated with a delay from a third time (t2) at which the second UE receives the first reference signal used for positioning to a fourth time (t3) at which the second UE transmits the second reference signal used for positioning. The first UE may then calculate the RTT between the first UE and the second UE based on the first time (t1), the second time (t4), and the timing measurement information (t2->t3).

[0170] Reference Figure 14-15In other designs, the first UE may correspond to a responder UE associated with the RTT measurement procedure. In this case, the first UE transmits a first reference signal for positioning from the second UE on a first resource associated with the reciprocal CLI measurement resource configuration and measures a first time (t2) associated with receiving the first reference signal for positioning. In response to receiving the first reference signal for positioning on a second resource associated with the reciprocal CLI measurement resource configuration, the first UE further transmits a second reference signal for positioning to the second UE and measures a second time (t3) associated with transmitting the second reference signal for positioning. In some designs, the first UE may report timing measurement information associated with a delay from the measured first time (t2) to the measured second time (t3). For example, the report may be directed to an entity that calculates the RTT, such as the second UE or a network entity (e.g., a base station, or a network entity (such as an LMF) via the base station). In some designs, the first UE may receive an indication of the RTT associated with the RTT measurement procedure from the base station based at least in part on the reported timing measurement information. In some designs, the first UE may be the entity that calculates the RTT (eg, based on timing measurement information from the second UE indicating t4->t3).

[0171] Figure 16 It shows that the various aspects of the present disclosure are respectively Figure 14-15 1600 is a diagram of exemplary timing of RTT measurement signals exchanged between UE 1 and UE 2 for an example implementation of processes 1400 - 1500 .

[0172] exist Figure 16 In the example of FIG1 , UE 1 sends a reference signal 1602 (e.g., SRS, SRS-P, SL-RS, etc.) to UE 2 on UL symbol 1604 at time t1. In this case, the reference signal 1602 is used as both a CLI measurement signal and an RTT measurement signal. The reference signal 1602 has a certain propagation delay T as it travels from UE 1 to UE 2. Prop At time t2 (ToA of reference signal 1602 at UE 2), UE 2 receives / measures the ToA(t2) of reference signal 1602 on D symbol 1606 and also performs CLI measurement on reference signal 1602. After a certain UE processing time, UE 2 transmits reference signal 1608 on uplink symbol 1610 at time t3. Reference signal 1608 serves as both an RTT response signal and a CLI measurement signal. Reference signal 1608 has a certain propagation delay T as it travels from UE 2 to UE 1. PropAt time t4 (ToA of reference signal 1608 at UE 1), UE 1 receives / measures ToA(t4) of reference signal 1608 on D symbol 1612 and also performs CLI measurement on reference signal 1608. The way to identify ToA is as described above with reference to Figure 10 discussed and can also be found here Figure 16 to be used, and thus will not be described further for the sake of brevity.

[0173] In some designs, the reference signal 1608 may explicitly include the difference between time t3 and time t2 (ie, T Rx→Tx 1614). Using this measurement and the difference between time t4 and time t1 (ie, T Tx→Rx 1616), UE1, UE2 or a network component (e.g., BS 304, LMF, etc.) may calculate the distance between UE1 and UE2 as follows:

[0174]

[0175] Where c is the speed of light. Figure 16 It is not explicitly explained in , but an additional source of delay or error may be due to the UE hardware group delay in positioning the position.

[0176] Reference Figure 16 It will be appreciated that symbols (or resources) 1604, 1606, 1610, and 1612 may be part of a reciprocal CLI resource configuration, similar to the legacy CLI measurement procedure. However, UEs 1 and 2 are further configured to perform the aforementioned RTT measurement on these symbols, thereby opportunistically utilizing these symbols to measure not only CLI but also RTT.

[0177] Figure 17 It shows that the various aspects of the present disclosure are respectively Figure 14-15 FIG1700 is a diagram illustrating exemplary timing of RTT measurement signals exchanged between UE 1 and UE 2 according to another exemplary implementation of the processes 1400-1500. FIG1700 is a diagram illustrating exemplary timing of RTT measurement signals exchanged between UE 1 and UE 2 according to another exemplary implementation of the processes 1400-1500. Figure 16 An expanded version of diagram 1600 in which additional RTT measurements are made.

[0178] exist Figure 17 For the first RTT measurement, as described above Figure 16 Aspects 1602-1616 are implemented as described. Figure 17 In the example, after a certain additional UE processing time, UE 2 at time t 3BAnother reference signal 1702 is transmitted on uplink symbol 1704. Reference signal 1702 serves as both an RTT response signal (to reference signal 1602) and a CLI measurement signal. Reference signal 1702 has a certain propagation delay T as it travels from UE 2 to UE 1. Prop At time t 4B (ToA of reference signal 1702 at UE 1), UE 1 receives / measures the ToA of reference signal 1702 on D symbol 1706 (t 4B ), and also performs CLI measurement on reference signal 1702. The way in which ToA can be identified is referred to above Figure 10 discussed and can also be found here Figure 17 to be used, and thus will not be described further for the sake of brevity.

[0179] In some designs, the reference signal 1702 may explicitly include the time t 3B and the difference between time t2 (i.e., T Rx→Tx 1708). Using this measurement and the difference between time t4 and time t1 (ie, T Tx→Rx 1710), UE1, UE2 or a network component (e.g., BS 304, LMF, etc.) may calculate the distance between UE1 and UE2 as follows:

[0180]

[0181] Where c is the speed of light. Figure 17 It is not explicitly explained in , but an additional source of delay or error may be due to the UE hardware group delay in positioning the position.

[0182] Reference Figure 17 It will be appreciated that symbols (or resources) 1604, 1606, 1610, 1602, 1704, and 1706 may be part of a reciprocal CLI resource configuration, similar to the legacy CLI measurement procedure. However, UEs 1 and 2 are further configured to perform the aforementioned RTT measurement on these symbols, thereby opportunistically utilizing these symbols to measure not only CLI but also RTT.

[0183] Reference Figure 16-17 In some designs, a first reciprocal CLI resource pair for RTT may be associated with an initiator UE (e.g., 1604 and 1612, or 1604 and 1706), and a second reciprocal CLI resource pair for RTT may be associated with a responder UE (e.g., 1606 and 1610, or 1606 and 1704). Each resource pair is associated with one RTT measurement procedure. Figure 17As shown in , resource pairs may partially overlap (e.g., 1604-1606 are used as parts of two different reciprocal CLI resource pairs for RTT). In some designs, a pattern for RTT estimation may be defined in the reciprocal CLI resource configuration. Such a pattern may include multiple paired resources for RTT (e.g., Figure 17 , thereby facilitating two different RTT measurements). The way in which two resources are paired in this manner may occur in various ways. For example, adjacent Tx (U) and Rx (D) resources may be organized as a reciprocal CLI resource pair for RTT. In another example, a time anchor (e.g., t1) may be defined. In this case, different time offsets may be defined, where a resource associated with the time anchor is paired with a resource associated with each corresponding time offset from the time anchor. In some designs, the responding UE for each resource pair may be configured to report its time difference (i.e., T Rx→Tx or t3-t2), although in some designs the initiating UE of each resource pair may alternatively report its time difference (ie, T Tx→Rx or t4-t1). In some designs, it is possible to implement Figure 17 to reduce distance estimation errors (eg, the RTT measurements may be averaged, etc.).

[0184] Reference Figure 13-17 In some designs, RTT estimation may occur in various ways. In some designs, the assisting (or responding) UE may measure times T2 and T3 and obtain the time difference T Rx→Tx = T3 - T2. In some designs, the initiating (or positioning) UE may measure times T1 and T4 and obtain the time difference T Tx→Rx =T4-T1. For UE-based RTT estimation, the responder UE may feed back the Rx-Tx time difference to the network, and the network may deliver the time difference to the initiator UE. Alternatively, the responder UE may feed back the Rx-Tx time difference to the initiator UE via a side link (e.g., to achieve low latency and power savings, where network interaction is bypassed). In this case, the initiator UE may calculate the RTT between the two UEs. In other designs, network-based (e.g., BS-based or LMF-based) CLI positioning may be implemented. In this case, the initiator and responder UEs may feed back their respective time differences to the network, and the network may then deliver the estimated RTT back to the initiator and / or responder UE. The RTT calculation may be performed with respect to the algorithm already described above, for example:

[0185]

[0186] Reference Figure 14-17In some designs, the range information between the two UEs may be derived based on the estimated UE. In some designs, the range information may help the victim UE manage interference with the aggressor UE. In some designs, the UE may derive the relative positioning information between the two UEs based on the estimated RTT and angle information (e.g., AoD / AoA). In some designs, the angle information may be provided by the network. In other designs, the angle information may be estimated independently at the UE. In some designs, the network may deliver the positioning information of the assisting (responding) UE to the positioning (initiating) UE. In some designs, the positioning UE may derive its own positioning information based on the positioning information of the assisting UE(s) and the corresponding estimated RTT(s). In some designs, the positioning information of at least three assisting UEs may be received (and the RTT may be derived for the at least three assisting UEs) (e.g., as Figure 13 ).

[0187] Those skilled in the art will appreciate that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0188] In addition, those skilled in the art will appreciate that the various illustrative logic blocks, modules, circuits, and algorithmic steps described in conjunction with the aspects disclosed herein can be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps are generally described above in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. A skilled person may implement the described functionality in different ways for each specific application, but such implementation decisions should not be interpreted as causing a departure from the scope of this disclosure.

[0189] The various illustrative logical blocks, modules, and circuits described in conjunction with the various aspects disclosed herein may be implemented or executed with a general purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0190] The methods, sequences and / or algorithms described in conjunction with the various aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. The 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, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor so that the processor can read and write information from / to the storage medium. In an alternative, the storage medium may be integrated into the processor. The processor and storage medium may reside in an ASIC. The ASIC may reside in a user terminal (e.g., UE). In an alternative, the processor and storage medium may reside in the user terminal as discrete components.

[0191] In one or more exemplary aspects, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, each function may be stored on or transmitted via a computer-readable medium as one or more instructions or code. Computer-readable media includes both computer storage media and communication media, including any medium that facilitates the transfer of a computer program from one location to another. A storage medium may be any available medium that can be accessed by a computer. By way of example and not limitation, such computer-readable media may include 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. Similarly, any connection is also properly referred to as 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 microwaves, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwaves are included in the definition of medium. As used herein, disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, where disks typically reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0192] Although the foregoing disclosure shows illustrative aspects of the present disclosure, it should be noted that various changes and modifications may be made therein without departing from the scope of the present disclosure as defined by the appended claims. The functions, steps, and / or actions in the method claims according to the various aspects of the present disclosure described herein do not have to be performed in any particular order. Furthermore, although elements of the present disclosure may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated.

Claims

1. A method of operating a first user equipment (UE), comprising: receiving a reciprocal cross-link interference (CLI) measurement resource configuration associated with the first UE and the second UE; as well as Both a CLI measurement procedure and a round trip time (RTT) measurement procedure are performed with the second UE based on resources associated with the reciprocal CLI measurement resource configuration.

2. The method of claim 1 , wherein the RTT measurement procedure comprises: transmitting, to the second UE, a first reference signal for positioning on a first resource associated with the reciprocal CLI measurement resource configuration; measuring a first time associated with transmitting the first reference signal for positioning; receiving, in response to the transmitting, a second reference signal for positioning from the second UE on second resources associated with the reciprocal CLI measurement resource configuration; as well as A second time associated with receiving the second reference signal for positioning is measured.

3. The method of claim 2, further comprising: Timing measurement information associated with the measured first time and second time is reported. The method of claim 3 , wherein the reporting reports the timing measurement information to the second UE. The method of claim 3 , wherein the reporting reports the timing measurement information to a network node.

6. The method of claim 5, further comprising: An indication of an RTT associated with the RTT measurement procedure is received from the network node based in part on the reported timing measurement information.

7. The method of claim 2, further comprising: receiving, from the second UE, timing measurement information associated with a delay from a third time at which the first reference signal for positioning is received at the second UE to a fourth time at which the second reference signal for positioning is transmitted from the second UE; as well as An RTT between the first UE and the second UE is calculated based on the first time, the second time, and the timing measurement information.

8. The method of claim 1 , wherein the RTT measurement procedure comprises: receiving, from the second UE on first resources associated with the reciprocal CLI measurement resource configuration, a first reference signal for positioning; measuring a first time associated with receiving the first reference signal for positioning; transmitting, in response to the receiving, a second reference signal for positioning to the second UE on second resources associated with the reciprocal CLI measurement resource configuration; as well as A second time associated with transmitting the second reference signal used for positioning is measured.

9. The method of claim 8, further comprising: Timing measurement information associated with a delay from the measured first time to the measured second time is reported.

10. The method of claim 9, wherein the reporting reports the timing measurement information to the second UE.

11. The method of claim 9, wherein the reporting reports the timing measurement information to a network node.

12. The method of claim 11, further comprising: An indication of an RTT associated with the RTT measurement procedure is received from the network node based in part on the reported timing measurement information.

13. The method of claim 1, wherein the RTT measurement procedure is associated with a reference signal exchange between the first UE and the second UE.

14. The method of claim 13, wherein the reference signal comprises a sounding reference signal (SRS), a sounding reference signal for positioning (SRS-P), a sidelink reference signal (SL-RS), or a combination thereof.

15. The method of claim 1, Wherein the RTT measurement procedure includes multiple RTT measurements, Wherein each of the plurality of RTT measurements is associated with a resource pair.

16. The method of claim 15, wherein: For each resource pair, the resource pair is paired based on being adjacent resources associated with different configured receive-transmit directions.

17. The method of claim 15, wherein: For each resource pair, the resource pair is paired based on a first resource being associated with an anchor time and a second resource being associated with an offset from the anchor time.

18. A method of operating a network node, comprising: determining a reciprocal cross-link interference (CLI) measurement resource configuration associated with a first user equipment (UE) and a second UE, the reciprocal CLI measurement resource configuration comprising resources associated with both a CLI measurement procedure and a round trip time (RTT) measurement procedure between the first UE and the second UE; as well as The reciprocal CLI measurement resource configuration is transmitted to the first UE and the second UE.

19. The method of claim 18, further comprising: Timing measurement information associated with the RTT measurement procedure is received from the first UE and the second UE.

20. The method of claim 19, further comprising: Obtaining an RTT based on the received timing measurement information; as well as The RTT is transmitted to at least one of the first UE and the second UE.

21. The method of claim 18, wherein the RTT measurement procedure is associated with a reference signal exchange between the first UE and the second UE.

22. The method of claim 21, wherein the reference signal comprises a sounding reference signal (SRS), a sounding reference signal for positioning (SRS-P), a sidelink reference signal (SL-RS), or a combination thereof.

23. The method of claim 18, Wherein the RTT measurement procedure includes multiple RTT measurements, Wherein each of the plurality of RTT measurements is associated with a resource pair.

24. The method of claim 23, wherein: For each resource pair, the resource pair is paired based on being adjacent resources associated with different configured receive-transmit directions.

25. The method of claim 23, wherein: For each resource pair, the resource pair is paired based on a first resource being associated with an anchor time and a second resource being associated with an offset from the anchor time.

26. A first user equipment (UE), comprising: means for receiving a reciprocal cross-link interference (CLI) measurement resource configuration associated with the first UE and the second UE; as well as Means for performing both a CLI measurement procedure and a round trip time (RTT) measurement procedure with the second UE based on resources associated with the reciprocal CLI measurement resource configuration.

27. The first UE according to claim 26, wherein the RTT measurement procedure comprises: transmitting, to the second UE, a first reference signal for positioning on a first resource associated with the reciprocal CLI measurement resource configuration; measuring a first time associated with transmitting the first reference signal for positioning; receiving, in response to the transmitting, a second reference signal for positioning from the second UE on second resources associated with the reciprocal CLI measurement resource configuration; as well as A second time associated with receiving the second reference signal for positioning is measured.

28. The first UE according to claim 27, further comprising: Means for reporting timing measurement information associated with the measured first time and second time.

29. The first UE of claim 28, wherein the report reports the timing measurement information to the second UE.

30. The first UE of claim 28, wherein the reporting reports the timing measurement information to a network node.

31. The first UE according to claim 30, further comprising: Means for receiving, from the network node, an indication of an RTT associated with the RTT measurement procedure based in part on the reported timing measurement information.

32. The first UE according to claim 27, further comprising: means for receiving, from the second UE, timing measurement information associated with a delay from a third time at which the first reference signal for positioning is received at the second UE to a fourth time at which the second reference signal for positioning is transmitted from the second UE; as well as means for calculating an RTT between the first UE and the second UE based on the first time, the second time, and the timing measurement information.

33. The first UE according to claim 26, wherein the RTT measurement procedure comprises: receiving, from the second UE on first resources associated with the reciprocal CLI measurement resource configuration, a first reference signal for positioning; measuring a first time associated with receiving the first reference signal for positioning; transmitting, in response to the receiving, a second reference signal for positioning to the second UE on second resources associated with the reciprocal CLI measurement resource configuration; as well as A second time associated with transmitting the second reference signal used for positioning is measured.

34. The first UE according to claim 33, further comprising: Means for reporting timing measurement information associated with a delay from a measured first time to a measured second time.

35. The first UE of claim 34, wherein the report reports the timing measurement information to the second UE.

36. The first UE of claim 34, wherein the reporting reports the timing measurement information to a network node.

37. The first UE according to claim 36, further comprising: Means for receiving, from the network node, an indication of an RTT associated with the RTT measurement procedure based in part on the reported timing measurement information.

38. The first UE of claim 26, wherein the RTT measurement procedure is associated with a reference signal exchange between the first UE and the second UE.

39. The first UE of claim 38, wherein the reference signal comprises a sounding reference signal (SRS), a sounding reference signal for positioning (SRS-P), a sidelink reference signal (SL-RS), or a combination thereof.

40. The first UE according to claim 26, Wherein the RTT measurement procedure includes multiple RTT measurements, Wherein each of the plurality of RTT measurements is associated with a resource pair.

41. The first UE according to claim 40, wherein: For each resource pair, the resource pair is paired based on being adjacent resources associated with different configured receive-transmit directions.

42. The first UE according to claim 40, wherein: For each resource pair, the resource pair is paired based on a first resource being associated with an anchor time and a second resource being associated with an offset from the anchor time.

43. A network node comprising: means for determining a reciprocal cross-link interference (CLI) measurement resource configuration associated with a first user equipment (UE) and a second UE, the reciprocal CLI measurement resource configuration comprising resources associated with both a CLI measurement procedure and a round trip time (RTT) measurement procedure between the first UE and the second UE; as well as Means for transmitting the reciprocal CLI measurement resource configuration to the first UE and the second UE.

44. The network node of claim 43, further comprising: Means for receiving timing measurement information associated with the RTT measurement procedure from the first UE and the second UE.

45. The network node of claim 44, further comprising: means for obtaining an RTT based on the received timing measurement information; as well as Means for transmitting the RTT to at least one of the first UE and the second UE.

46. ​​The network node of claim 43, wherein the RTT measurement procedure is associated with a reference signal exchange between the first UE and the second UE.

47. The network node of claim 46, wherein the reference signal comprises a sounding reference signal (SRS), a sounding reference signal for positioning (SRS-P), a sidelink reference signal (SL-RS), or a combination thereof.

48. The network node according to claim 43, Wherein the RTT measurement procedure includes multiple RTT measurements, Wherein each of the plurality of RTT measurements is associated with a resource pair.

49. The network node of claim 48, wherein: For each resource pair, the resource pair is paired based on being adjacent resources associated with different configured receive-transmit directions.

50. The network node of claim 48, wherein: For each resource pair, the resource pair is paired based on a first resource being associated with an anchor time and a second resource being associated with an offset from the anchor time.

51. A first user equipment (UE), comprising: Memory; at least one communication interface; as well as at least one processor communicatively coupled to the memory and the at least one communication interface, the at least one processor configured to: receiving a reciprocal cross-link interference (CLI) measurement resource configuration associated with the first UE and the second UE; and Both a CLI measurement procedure and a round trip time (RTT) measurement procedure are performed with the second UE based on resources associated with the reciprocal CLI measurement resource configuration.

52. The first UE of claim 51 , wherein the RTT measurement procedure comprises: transmitting, to the second UE, a first reference signal for positioning on a first resource associated with the reciprocal CLI measurement resource configuration; measuring a first time associated with transmitting the first reference signal for positioning; receiving, in response to the transmitting, a second reference signal for positioning from the second UE on second resources associated with the reciprocal CLI measurement resource configuration; as well as A second time associated with receiving the second reference signal for positioning is measured.

53. The first UE of claim 52, wherein the at least one processor is further configured to: Timing measurement information associated with the measured first time and second time is reported.

54. The first UE of claim 53, wherein the report reports the timing measurement information to the second UE.

55. The first UE of claim 53, wherein the reporting reports the timing measurement information to a network node.

56. The first UE of claim 55, wherein the at least one processor is further configured to: An indication of an RTT associated with the RTT measurement procedure is received from the network node based in part on the reported timing measurement information.

57. The first UE of claim 52, wherein the at least one processor is further configured to: receiving, from the second UE, timing measurement information associated with a delay from a third time at which the first reference signal for positioning is received at the second UE to a fourth time at which the second reference signal for positioning is transmitted from the second UE; and An RTT between the first UE and the second UE is calculated based on the first time, the second time, and the timing measurement information.

58. The first UE of claim 51 , wherein the RTT measurement procedure comprises: receiving, from the second UE on first resources associated with the reciprocal CLI measurement resource configuration, a first reference signal for positioning; measuring a first time associated with receiving the first reference signal for positioning; transmitting, in response to the receiving, a second reference signal for positioning to the second UE on second resources associated with the reciprocal CLI measurement resource configuration; as well as A second time associated with transmitting the second reference signal used for positioning is measured.

59. The first UE of claim 58, wherein the at least one processor is further configured to: Timing measurement information associated with a delay from the measured first time to the measured second time is reported.

60. The first UE of claim 59, wherein the report reports the timing measurement information to the second UE.

61. The first UE of claim 59, wherein the reporting reports the timing measurement information to a network node.

62. The first UE of claim 61 , wherein the at least one processor is further configured to: An indication of an RTT associated with the RTT measurement procedure is received from the network node based in part on the reported timing measurement information.

63. The first UE of claim 51, wherein the RTT measurement procedure is associated with a reference signal exchange between the first UE and the second UE.

64. The first UE of claim 63, wherein the reference signal comprises a sounding reference signal (SRS), a sounding reference signal for positioning (SRS-P), a sidelink reference signal (SL-RS), or a combination thereof.

65. The first UE according to claim 51, Wherein the RTT measurement procedure includes multiple RTT measurements, Wherein each of the plurality of RTT measurements is associated with a resource pair.

66. The first UE according to claim 65, wherein For each resource pair, the resource pair is paired based on being adjacent resources associated with different configured receive-transmit directions.

67. The first UE according to claim 65, wherein: For each resource pair, the resource pair is paired based on a first resource being associated with an anchor time and a second resource being associated with an offset from the anchor time.

68. A network node comprising: Memory; at least one communication interface; as well as at least one processor communicatively coupled to the memory and the at least one communication interface, the at least one processor configured to: determining a reciprocal cross-link interference (CLI) measurement resource configuration associated with a first user equipment (UE) and a second UE, the reciprocal CLI measurement resource configuration comprising resources associated with both a CLI measurement procedure and a round trip time (RTT) measurement procedure between the first UE and the second UE; as well as The reciprocal CLI measurement resource configuration is transmitted to the first UE and the second UE.

69. The network node of claim 68, wherein the at least one processor is further configured to: Timing measurement information associated with the RTT measurement procedure is received from the first UE and the second UE.

70. The network node of claim 69, wherein the at least one processor is further configured to: Obtaining the RTT based on the received timing measurement information; and The RTT is transmitted to at least one of the first UE and the second UE.

71. The network node of claim 68, wherein the RTT measurement procedure is associated with a reference signal exchange between the first UE and the second UE.

72. The network node of claim 71, wherein the reference signal comprises a sounding reference signal (SRS), a sounding reference signal for positioning (SRS-P), a sidelink reference signal (SL-RS), or a combination thereof.

73. The network node according to claim 68, Wherein the RTT measurement procedure includes multiple RTT measurements, Wherein each of the plurality of RTT measurements is associated with a resource pair.

74. The network node of claim 73, wherein: For each resource pair, the resource pair is paired based on being adjacent resources associated with different configured receive-transmit directions.

75. The network node of claim 73, wherein: For each resource pair, the resource pair is paired based on a first resource being associated with an anchor time and a second resource being associated with an offset from the anchor time.

76. A non-transitory computer-readable medium comprising instructions stored thereon, the instructions, when executed, causing a first user equipment (UE): receiving a reciprocal cross-link interference (CLI) measurement resource configuration associated with the first UE and the second UE; and Both a CLI measurement procedure and a round trip time (RTT) measurement procedure are performed with the second UE based on resources associated with the reciprocal CLI measurement resource configuration.

77. A non-transitory computer-readable medium comprising instructions stored thereon, the instructions, when executed, causing a network node to: determining a reciprocal cross-link interference (CLI) measurement resource configuration associated with a first user equipment (UE) and a second UE, the reciprocal CLI measurement resource configuration comprising resources associated with both a CLI measurement procedure and a round trip time (RTT) measurement procedure between the first UE and the second UE; and The reciprocal CLI measurement resource configuration is transmitted to the first UE and the second UE.

Images