Precoded reference signals for cross-link interference feedback reporting

Abstract

Certain aspects of the present disclosure provide techniques for wireless communication by an aggressor user equipment (UE), generally including receiving configuration information that configures at least one resource for the aggressor UE for transmitting a pre-coded reference signal (RS) for cross-link interference (CLI) measurements by an interfered UE; and transmitting the pre-decoded RS on the resource.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. patent application No. 17 / 859,839, filed on July 7, 2022, which is assigned to the assignee of the present application and is hereby expressly incorporated by reference in its entirety, as if fully set forth below and for all applicable purposes. Background Art Technical Field

[0003] Aspects of the present disclosure relate to wireless communications and, more particularly, to techniques for cross-link interference (CLI) feedback reporting using precoded reference signals.

[0004] Related technologies

[0005] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcasts or other similar types of services. These wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available wireless communication system resources with those users.

[0006] Although wireless communication systems have made tremendous technical progress over the years, challenges still exist. For example, complex and dynamic environments can still attenuate or block signals between wireless transmitters and wireless receivers. Therefore, there is a continued desire to improve the technical performance of wireless communication systems, including, for example: improving the speed and data carrying capacity of communications, improving the efficiency of using shared communication media, reducing the power used by transmitters and receivers when performing communications, improving the reliability of wireless communications, avoiding redundant transmission and / or reception and related processing, improving the coverage area of ​​wireless communications, increasing the number and types of devices that can access wireless communication systems, increasing the ability of different types of devices to communicate with each other, increasing the number and types of wireless communication media available for use, etc. Therefore, there is a need to further improve wireless communication systems to overcome the above-mentioned technical challenges and other challenges. Summary of the invention

[0007] One aspect provides a method for wireless communication by an aggressor user equipment (UE). The method includes: receiving configuration information, the configuration information configuring at least one resource for the aggressor UE to send a pre-decoded reference signal (RS) for a victim UE to perform cross-link interference (CLI) measurement; and sending the pre-decoded RS on the resource.

[0008] Another aspect provides a method for wireless communication by a victim UE. The method includes: receiving configuration information, the configuration information configuring one or more CLI measurement resources for the victim UE for measuring a CLI sounding reference signal (SRS); measuring CLI based on the SRS sent on the CLI measurement resources; and sending a report based on the measured CLI.

[0009] In another aspect, a method for wireless communication by a network entity is provided. The method includes sending first configuration information, the configuration information configuring at least one resource for an aggressor UE to send a pre-decoded RS for a victim UE to perform CLI measurement; sending second configuration information, the second configuration information configuring one or more CLI measurement resources for the victim UE to measure CLI SRS; and receiving a report generated by the victim UE based on the measured CLI SRS.

[0010] Other aspects provide: an apparatus operable to, configured to, or otherwise adapted to perform any one or more of the foregoing methods and / or those described elsewhere herein; a non-transitory computer-readable medium comprising instructions that, when executed by a processor of the apparatus, cause the apparatus to perform the foregoing methods and those described elsewhere herein; a computer program product embodied on a computer-readable storage medium, comprising: code for performing the foregoing methods and those described elsewhere herein; and / or an apparatus comprising components for performing the foregoing methods and those described elsewhere herein. By way of example, an apparatus may include a processing system, a device having a processing system, or a processing system cooperating through one or more networks.

[0011] For purposes of illustration, the following description and drawings set forth certain features. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The accompanying drawings depict certain features of the various aspects described herein and should not be considered to limit the scope of the disclosure.

[0013] Figure 1 An example wireless communication network is depicted.

[0014] Figure 2 An example disaggregated base station architecture is depicted.

[0015] Figure 3 Aspects of an example base station and example user equipment are depicted.

[0016] Figure 4A , Figure 4B , Figure 4C and Figure 4D Various example aspects of data structures for a wireless communication network are described.

[0017] Figure 5A , Figure 5B and Figure 5C Various examples of full-duplex time / frequency resource configurations are depicted.

[0018] Fig. 6A , Figure 6B and Figure 6C Various examples of full-duplex configurations are depicted.

[0019] Fig. 7A and Figure 7B Examples of interference sources at a UE are depicted.

[0020] Figure 8 is a call flow diagram illustrating an example of codebook-based uplink (UL) transmission in accordance with certain aspects of the present disclosure.

[0021] Fig. 9 is a call flow diagram illustrating an example of non-codebook based UL transmission in accordance with certain aspects of the present disclosure.

[0022] Fig.10 An example signal reception by a victim UE is depicted.

[0023] Fig.11 Depicted are call flow diagrams in accordance with certain aspects of the present disclosure.

[0024] Fig.12 A procedure for enabling CLI-aware CSI reporting in full-duplex (FD) scenarios is described.

[0025] Fig.13 Depicted is a diagram illustrating the difference between CLI-SRS and traditional SRS.

[0026] Fig.14 A method for wireless communication is described.

[0027] Fig.15 A method for wireless communication is described.

[0028] Fig.16 A method for wireless communication is described.

[0029] Fig.17 Aspects of an example communications device are depicted.

[0030] Fig.18 Aspects of an example communications device are depicted.

[0031] Fig.19 Aspects of an example communications device are depicted. DETAILED DESCRIPTION

[0032] Aspects of the present disclosure provide apparatus, methods, processing systems, and computer-readable media for cross-link interference (CLI) feedback reporting using precoded reference signals.

[0033] The term full-duplex (FD) describes simultaneous data transmission and reception on one channel. Therefore, FD devices are capable of bidirectional network data transmission at the same time. In contrast, half-duplex (HD) devices can only transmit in one direction at a time. With HD mode, data can move in both directions, but not at the same time.

[0034] If a user equipment (UE) operates in HD mode and a gNodeB (gNB) operates in sub-band FD (SBFD) or intra-band FD (IBFD), the UE may experience interference from multiple sources. For example, the interference may include inter-cell interference (ICI) from other gNBs, intra-cell cross-link interference (CLI) from UEs in the same cell, and inter-cell CLI from UEs in neighboring cells. Self-interference may also occur for FD UEs, i.e., UE uplink transmissions interfere with the reception of downlink transmissions. These interference sources may cause serious problems, including reduced spectral efficiency, increased power consumption, and poor UE performance.

[0035] Various aspects of the present disclosure provide techniques that may help detect such potential sources of interference. In some cases, an aggressor UE may be configured to transmit a pre-coded CLI reference signal (CLI-RS), essentially mimicking a future physical uplink shared channel (PUSCH) transmission, and the victim UE performs CLI measurements based on the transmitted pre-coded CLI-RS. These techniques will enable improved channel state feedback (CSF) calculations at the victim UE, allowing the gNB to receive accurate CSF reports that capture the impact of inter-UE CLI in FD slots.

[0036] The techniques presented herein may have significant benefits. For example, the transmission of precoded CLI-RS by an aggressor UE and subsequent CLI measurements and CSF reporting of the CLI measurements to a network entity may enable the network to generate a precoding configuration (e.g., a transmitted precoding matrix indicator (TPMI)) that will reduce (e.g., intra-cell CLI and inter-cell CLI) interference, thereby improving spectral efficiency, power savings, and UE performance.

[0037] Introduction to wireless communication networks

[0038] The techniques and methods described herein can be used in various wireless communication networks. Although various aspects may be described herein using terms commonly associated with 3G, 4G and / or 5G wireless technologies, various aspects of the present disclosure may also be applicable to other communication systems and standards not explicitly mentioned herein.

[0039] Figure 1 An example of a wireless communication network 100 is depicted in which various aspects described herein may be implemented.

[0040] In general, the wireless communication network 100 includes various network entities (alternatively, network elements or network nodes). A network entity is typically a communication device and / or a communication function performed by a communication device (e.g., user equipment (UE), base station (BS), component of a BS, server, etc.). For example, various functions of a network and various devices associated with and interacting with the network may be considered network entities. In addition, the wireless communication network 100 includes ground aspects, such as ground-based network entities (e.g., BS 102), and non-ground aspects, such as satellites 140 and aircraft 145, which may include airborne network entities (e.g., one or more BSs) capable of communicating with other network elements (e.g., ground BSs) and user equipment.

[0041] In the depicted example, the wireless communication network 100 includes a BS 102, a UE 104, and one or more core networks (such as an evolved packet core (EPC) 160 and a 5G core (5GC) network 190) that interoperate to provide communication services over various communication links (including wired and wireless links).

[0042] Figure 1 Various example UEs 104 are depicted, which may more generally include: a cellular phone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player, a camera, a game console, a tablet computer, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, an Internet of Things (IoT) device, an Always-On (AON) device, an edge processing device, or other similar devices. UE 104 may also be more generally referred to as a mobile device, a wireless device, a wireless communication device, a station, a mobile station, a subscriber station, a mobile subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a remote device, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, and others.

[0043] BS 102 wirelessly communicates with (e.g., sends signals to or receives signals from) UE 104 via communication link 120. Communication link 120 between BS 102 and UE 104 may include uplink (UL) (also referred to as a reverse link) transmissions from UE 104 to BS 102 and / or downlink (DL) (also referred to as a forward link) transmissions from BS 102 to UE 104. In various aspects, communication link 120 may employ multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity.

[0044] BS 102 may generally include: a Node B, an enhanced Node B (eNB), a next generation enhanced Node B (ng-eNB), a next generation Node B (gNB or gNodeB), an access point, a base transceiver, a radio base station, a radio transceiver, a transceiver function, a transmission and reception point, and / or the like. Each of BS 102 may provide communication coverage for a respective geographic coverage area 110, which may sometimes be referred to as a cell, and may overlap in some cases (e.g., a small cell 102' may have a coverage area 110' that overlaps with a coverage area 110 of a macro cell). For example, a BS may provide communication coverage for a macro cell (covering a relatively large geographic area), a pico cell (covering a relatively small geographic area, such as a stadium), a femto cell (a relatively small geographic area (e.g., a home)), and / or other types of cells.

[0045] Although BS102 is depicted as a single communication device in various aspects, BS102 can be implemented in various configurations. For example, one or more components of the base station may be decomposed, including a central unit (CU), one or more distributed units (DU), one or more radio units (RU), a near real-time (near RT) RAN intelligent controller (RIC) or a non-real-time (non-RT) RIC, to name a few examples. In another example, various aspects of the base station may be virtualized. More generally, a base station (e.g., BS102) may include components located at a single physical location or components located at various physical locations. In an example in which the base station includes components located at various physical locations, the various components may each perform a function so that the various components together implement functionality similar to that of a base station located at a single physical location. In some aspects, a base station including components located at various physical locations may be referred to as a decomposed radio access network architecture (such as an open RAN (O-RAN) or virtualized RAN (VRAN) architecture). Figure 2 An example decomposed base station architecture is depicted and described.

[0046] Different BSs 102 within the wireless communication network 100 may also be configured to support different radio access technologies (such as 3G, 4G, and / or 5G). For example, a BS 102 configured for 4G LTE (collectively referred to as the Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPC 160 via a first backhaul link 132 (e.g., an S1 interface). A BS 102 configured for 5G (e.g., 5G NR or Next Generation RAN (NG-RAN)) may interface with the 5GC 190 via a second backhaul link 184. The BSs 102 may communicate with each other directly or indirectly (e.g., via the EPC 160 or the 5GC 190) over a third backhaul link 134 (e.g., an X2 interface), which may be wired or wireless.

[0047] The wireless communication network 100 may subdivide the electromagnetic spectrum into various categories, frequency bands, channels, or other characteristics. In some aspects, the subdivision is provided based on wavelength and frequency, where frequency may also be referred to as a carrier, subcarrier, channel, tone, or subband. For example, 3GPP currently defines frequency range 1 (FR1) as including 410 MHz-7125 MHz, which is often (interchangeably) referred to as "below 6 GHz". Similarly, 3GPP currently defines frequency range 2 (FR2) as including 24,250 MHz-52,600 MHz, which is sometimes (interchangeably) referred to as "millimeter wave" ("mmW" or "mmWave"). A base station (e.g., a mmWave base station such as BS180) configured to communicate using mmWave / near mmWave radio bands may utilize beamforming (e.g., 182) with a UE (e.g., 104) to improve path loss and range.

[0048] The communication link 120 between the BS 102 and, for example, the UE 104 may be through one or more carriers, which may have different bandwidths (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, and / or other MHz) and may be aggregated in various aspects. The carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL ​​compared to UL).

[0049] Communications using higher frequency bands may have higher path loss and shorter range than communications at lower frequencies. Figure 1180) may utilize beamforming 182 with UE 104 to improve path loss and range. For example, BS 180 and UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming. In some cases, BS 180 may send beamformed signals to UE 104 in one or more transmit directions 182'. UE 104 may receive beamformed signals from BS 180 in one or more receive directions 182". UE 104 may also send beamformed signals to BS 180 in one or more transmit directions 182". BS 180 may also receive beamformed signals from UE 104 in one or more receive directions 182'. BS 180 and UE 104 may then perform beam training to determine the best receive and transmit directions for each of BS 180 and UE 104. It is noteworthy that the transmit direction and receive direction of BS 180 may be the same or different. Similarly, the transmit direction and receive direction of UE 104 may be the same or may be different.

[0050] Wireless communication network 100 also includes Wi-Fi AP 150 that communicates with Wi-Fi station (STA) 152 via communication link 154 in, for example, the 2.4 GHz and / or 5 GHz unlicensed spectrum.

[0051] Certain UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), a physical sidelink control channel (PSCCH), and / or a physical sidelink feedback channel (PSFCH).

[0052] The EPC 160 may include various functional components, including: a mobility management entity (MME) 162, other MMEs 164, a serving gateway 166, a multimedia broadcast multicast service (MBMS) gateway 168, a broadcast multicast service center (BM-SC) 170, and / or a packet data network (PDN) gateway 172, such as in the depicted example. The MME 162 may communicate with a home subscriber server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. In general, the MME 162 provides bearer and connection management.

[0053] Generally speaking, user Internet Protocol (IP) packets are transferred through the Serving Gateway 166, which itself is connected to the PDN Gateway 172. The PDN Gateway 172 provides UE IP address allocation and other functions. The PDN Gateway 172 and the BM-SC 170 are connected to the IP Services 176, which may include, for example, the Internet, an Intranet, an IP Multimedia Subsystem (IMS), a Packet Switched (PS) streaming media service, and / or other IP services.

[0054] The BM-SC 170 may provide functionality for MBMS user service provisioning and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS delivery, may be used to authorize and initiate MBMS bearer services within a public land mobile network (PLMN), and / or may be used to schedule MBMS delivery. The MBMS Gateway 168 may be used to distribute MBMS services to BSs 102 belonging to a multicast broadcast single frequency network (MBSFN) area broadcasting a specific service, and / or may be responsible for session management (start / stop) and for collecting eMBMS related charging information.

[0055] 5GC 190 may include various functional components, including: access and mobility management function (AMF) 192, other AMFs 193, session management function (SMF) 194, and user plane function (UPF) 195. AMF 192 may communicate with unified data management (UDM) 196.

[0056] AMF 192 is a control node that handles signaling between UE 104 and 5GC 190. AMF 192 provides, for example, Quality of Service (QoS) flow and session management.

[0057] Internet Protocol (IP) packets are delivered through UPF 195, which is connected to IP Services 197 and provides IP address allocation for UEs and other functions for 5GC 190. IP Services 197 may include, for example, the Internet, Intranet, IMS, PS streaming services, and / or other IP services.

[0058] In various aspects, a network entity or network node may be implemented as a converged base station, a decomposed base station, a component of a base station, an integrated access and backhaul (IAB) node, a relay node, a sidelink node, to name a few examples.

[0059] Figure 2An example disaggregated base station 200 architecture is depicted. The disaggregated base station 200 architecture may include one or more central units (CUs) 210 that may communicate directly with a core network 220 via a backhaul link, or indirectly with the core network 220 through one or more disaggregated base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 225 via an E2 link, or a non-real-time (non-RT) RIC 215 associated with a service management and orchestration (SMO) framework 205, or both. The CU 210 may communicate with one or more distributed units (DUs) 230 via respective midhaul links, such as an F1 interface. The DU 230 may communicate with one or more radio units (RUs) 240 via respective fronthaul links. The RU 240 may communicate with respective UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 240.

[0060] Each of these units (e.g., CU 210, DU 230, RU 240, and near-RT RIC 225, non-RT RIC 215, and SMO framework 205) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interface of the unit may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive or send signals to one or more of the other units via a wired transmission medium. Additionally or alternatively, the unit may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as a radio frequency (RF) transceiver) configured to receive or send signals, or both, to one or more of the other units on a wireless transmission medium.

[0061] In some aspects, CU 210 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 210. CU 210 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP)), control plane functionality (e.g., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 210 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 210 may be implemented to communicate with DU 230 for network control and signaling.

[0062] DU 230 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 240. In some aspects, DU 230 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) at least in part according to a functional split such as those defined by the 3rd Generation Partnership Project (3GPP). In some aspects, DU 230 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 230 or with control functions hosted by CU 210.

[0063] The lower layer functionality may be implemented by one or more RUs 240. In some deployments, the RU 240 controlled by the DU 230 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional split (such as a lower layer functional split). In such an architecture, the RU 240 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 240 may be controlled by the corresponding DU 230. In some scenarios, this configuration may enable the DU 230 and CU 210 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0064] The SMO framework 205 may be configured to support RAN deployment and configuration of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 205 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 205 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 290) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 210, DU 230, RU 240, and near-RT RIC 225. In some specific implementations, the SMO framework 205 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 211) via the O1 interface. Additionally, in some specific implementations, the SMO framework 205 may communicate directly with one or more RUs 240 via the O1 interface. The SMO framework 205 may also include a non-RT RIC 215 configured to support the functionality of the SMO framework 205 .

[0065] The non-RT RIC 215 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 225. The non-RT RIC 215 may be coupled to or in communication with the near-RT RIC 225 (such as via an A1 interface). The near-RT RIC 225 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 210, one or more DUs 230, or both, and the O-eNB with the near-RT RIC 225.

[0066] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 225, the non-RT RIC 215 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 225 and may be received from a non-network data source or from a network function at the SMO framework 205 or the non-RT RIC 215. In some examples, the non-RT RIC 215 or the near-RT RIC 225 may be configured to adjust RAN behavior or performance. For example, the non-RT RIC 215 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 205 (such as via reconfiguration of O1) or via the creation of RAN management policies (such as A1 policies).

[0067] Figure 3 Aspects of an example BS 102 and UE 104 are depicted.

[0068] In general, BS 102 includes various processors (e.g., 320, 330, 338, and 340), antennas 334a-334t (collectively 334), transceivers 332a-332t (collectively 332) including modulators and demodulators, and other aspects that enable wireless transmission of data (e.g., data source 312) and wireless reception of data (e.g., data sink 339). For example, BS 102 can transmit and receive data between BS 102 and UE 104. BS 102 includes a controller / processor 340 that can be configured to implement various functions described herein related to wireless communication.

[0069] In general, the UE 104 includes various processors (e.g., 358, 364, 366, and 380), antennas 352a-352r (collectively 352), transceivers 354a-354r (collectively 354) including modulators and demodulators, and other aspects that enable wireless transmission of data (e.g., retrieved from a data source 362) and wireless reception of data (e.g., provided to a data sink 360). The UE 104 includes a controller / processor 380 that can be configured to implement various functions described herein related to wireless communications.

[0070] Regarding example downlink transmissions, BS 102 includes a transmit processor 320 that can receive data from a data source 312 and control information from a controller / processor 340. The control information can be for a physical broadcast channel (PBCH), a physical control format indicator channel (PCFICH), a physical HARQ indicator channel (PHICH), a physical downlink control channel (PDCCH), a group common PDCCH (GC PDCCH), and / or others. In some examples, the data can be for a physical downlink shared channel (PDSCH).

[0071] The transmit processor 320 may process (e.g., encode and symbol map) data and control information to obtain data symbols and control symbols, respectively. The transmit processor 320 may also generate reference symbols, such as for a primary synchronization signal (PSS), a secondary synchronization signal (SSS), a PBCH demodulation reference signal (DMRS), and a channel state information reference signal (CSI-RS).

[0072] The transmit (TX) multiple-input multiple-output (MIMO) processor 330 may perform spatial processing (e.g., pre-coding) on ​​data symbols, control symbols, and / or reference symbols, where applicable, and may provide an output symbol stream to a modulator (MOD) in a transceiver 332a-332t. Each modulator in the transceiver 332a-332t may process a corresponding output symbol stream to obtain an output sample stream. Each modulator may further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The downlink signals from the modulators in the transceivers 332a-332t may be transmitted via antennas 334a-334t, respectively.

[0073] To receive downlink transmissions, UE 104 includes antennas 352a-352r that can receive downlink signals from BS 102 and can provide received signals to demodulators (DEMODs) in transceivers 354a-354r, respectively. Each demodulator in transceivers 354a-354r can condition (e.g., filter, amplify, downconvert, and digitize) a corresponding received signal to obtain input samples. Each demodulator can further process the input samples to obtain received symbols.

[0074] A MIMO detector 356 may obtain received symbols from all demodulators in transceivers 354a-354r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor 358 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for UE 104 to a data sink 360, and provide decoded control information to a controller / processor 380.

[0075] With respect to example uplink transmissions, the UE 104 also includes a transmit processor 364 that may receive and process data from a data source 362 (e.g., for a PUSCH) and control information from a controller / processor 380 (e.g., for a physical uplink control channel (PUCCH)). The transmit processor 364 may also generate reference symbols for reference signals (e.g., a sounding reference signal (SRS)). The symbols from the transmit processor 364 may be pre-decoded by a TX MIMO processor 366, if applicable, further processed by a modulator in the transceivers 354a-354r (e.g., for SC-FDM), and transmitted to the BS 102.

[0076] At BS 102, uplink signals from UE 104 may be received by antennas 334 a-334 t, processed by demodulators in transceivers 332 a-332 t, detected by MIMO detector 336 if applicable, and further processed by receive processor 338 to obtain decoded data and control information transmitted by UE 104. Receive processor 338 may provide the decoded data to a data sink 339 and the decoded control information to a controller / processor 340.

[0077] Memories 342 and 382 may store data and program codes for BS 102 and UE 104, respectively.

[0078] Scheduler 344 may schedule UEs for data transmission on the downlink and / or uplink.

[0079] In various aspects, BS 102 may be described as sending and receiving various types of data associated with the methods described herein. In these contexts, "sending" may refer to various mechanisms for outputting data, such as outputting data from a data source 312, a scheduler 344, a memory 342, a transmit processor 320, a controller / processor 340, a TX MIMO processor 330, a transceiver 332a-332t, an antenna 334a-334t, and / or other aspects described herein. Similarly, "receiving" may refer to various mechanisms for obtaining data, such as obtaining data from an antenna 334a-334t, a transceiver 332a-332t, a RX MIMO detector 336, a controller / processor 340, a receive processor 338, a scheduler 344, a memory 342, and / or other aspects described herein.

[0080] In various aspects, the UE 104 may also be described as sending and receiving various types of data associated with the methods described herein. In these contexts, "sending" may refer to various mechanisms for outputting data, such as outputting data from a data source 362, a memory 382, ​​a transmit processor 364, a controller / processor 380, a TX MIMO processor 366, a transceiver 354a-354t, an antenna 352a-352t, and / or other aspects described herein. Similarly, "receiving" may refer to various mechanisms for obtaining data, such as obtaining data from an antenna 352a-352t, a transceiver 354a-354t, a RX MIMO detector 356, a controller / processor 380, a receive processor 358, a memory 382, ​​and / or other aspects described herein.

[0081] In some aspects, the processor may be configured to perform various operations (such as those associated with the methods described herein) and send (output) data to or receive (obtain) data from another interface configured to send or receive data, respectively.

[0082] Figure 4A , Figure 4B , Figure 4C and Figure 4D Describes a method for use in a wireless communication network such as Figure 1 Various aspects of the data structure of the wireless communication network 100).

[0083] Specifically, Figure 4A is a diagram 400 illustrating an example of a first subframe within a 5G (e.g., 5G NR) frame structure, Figure 4B is a diagram 430 illustrating an example of a DL channel within a 5G subframe, Figure 4C is a diagram 450 illustrating an example of a second subframe within a 5G frame structure, and Figure 4D FIG480 is a diagram illustrating an example of UL channels within a 5G subframe.

[0084] Wireless communication systems can utilize orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) on both the uplink and downlink. Such systems can also support half-duplex operation using time division duplex (TDD). OFDM and single carrier frequency division multiplexing (SC-FDM) can be used to maximize the system bandwidth (e.g., Figure 4B and Figure 4D The modulation symbols may be transmitted in the frequency domain using OFDM and / or in the time domain using SC-FDM.

[0085] The wireless communication frame structure may be frequency division duplex (FDD), where for a particular set of subcarriers, subframes within the subcarrier set are dedicated to either DL or UL. The wireless communication frame structure may also be time division duplex (TDD), where for a particular set of subcarriers, subframes within the subcarrier set are dedicated to both DL and UL.

[0086] exist Figure 4A and Figure 4C In the wireless communication frame structure, TDD is used, where D is DL, U is UL, and X is used flexibly between DL / UL. The UE can be configured with a time slot format (dynamically configured by DL control information (DCI) or semi-statically / statically configured by radio resource control (RRC) signaling) through the received time slot format indicator (SFI). In the depicted example, the 10ms frame is divided into 10 equally sized 1ms subframes. Each subframe may include one or more time slots. In some examples, each time slot may include 7 or 14 symbols, depending on the time slot format. The subframe may also include micro-time slots, which typically have fewer symbols than the entire time slot. Other wireless communication technologies may have different frame structures and / or different channels.

[0087] In certain aspects, the number of slots within a subframe is based on the slot configuration and parameter set. For example, for slot configuration 0, different parameter sets (μ) 0 to 5 allow for 1, 2, 4, 8, 16, and 32 slots per subframe, respectively. For slot configuration 1, different parameter sets 0 to 2 allow for 2, 4, and 8 slots per subframe, respectively. Thus, for slot configuration 0 and parameter set μ, there are 14 symbols / slot and 2μ slots / subframe. The subcarrier spacing and symbol length / duration are a function of the parameter set. The subcarrier spacing may be equal to 2 μ × 15kHz, where μ is parameter set 0 to 5. Thus, parameter set μ=0 has a subcarrier spacing of 15kHz, and parameter set μ=5 has a subcarrier spacing of 480kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figure 4A , Figure 4B , Figure 4C and Figure 4D An example is provided for slot configuration 0 with 14 symbols per slot and parameter set μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs.

[0088] like Figure 4A , Figure 4B , Figure 4C and Figure 4DAs depicted in , a resource grid can be used to represent a frame structure. Each time slot includes a resource block (RB) (also called a physical RB (PRB)) extending, for example, 12 consecutive subcarriers. The resource grid is divided into a plurality of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0089] like Figure 4A As illustrated, some REs carry Figure 1 and Figure 3 The RS may include a demodulation RS (DMRS) and / or a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and / or a phase tracking RS (PT-RS).

[0090] Figure 4B Examples of various DL channels within a subframe of a frame are illustrated.The Physical Downlink Control Channel (PDCCH) carries DCI within one or more Control Channel Elements (CCEs), each CCE comprising, for example, nine RE Groups (REGs), each REG comprising, for example, four consecutive REs in an OFDM symbol.

[0091] The primary synchronization signal (PSS) may be in symbol 2 of a particular subframe of a frame. The PSS is transmitted by a UE (e.g., Figure 1 and Figure 3 104) is used to determine subframe / symbol timing and physical layer identification.

[0092] A Secondary Synchronization Signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and radio frame timing.

[0093] Based on the physical layer identifier and the physical layer cell identifier group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the aforementioned DMRS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block. The MIB provides the system frame number (SFN) and the number of RBs in the system bandwidth. The physical downlink shared channel (PDSCH) carries user data, broadcast system information (such as system information blocks (SIBs)) that is not sent via the PBCH, and / or paging messages.

[0094] As in Figure 4CAs illustrated in , some REs carry DMRS for channel estimation at the base station (indicated as R for a specific configuration, but other DMRS configurations are possible). The UE may send DMRS for PUCCH and DMRS for PUSCH. The PUSCH DMRS may be sent, for example, in the first one or two symbols of the PUSCH. The PUCCH DMRS may be sent in different configurations depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used. UE 104 may send a sounding reference signal (SRS). The SRS may be sent, for example, in the last symbol of a subframe. The SRS may have a comb structure, and the UE may send the SRS on one of the teeth of the comb. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.

[0095] Figure 4D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at a position as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), and HARQ ACK / NACK feedback. The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0096] Overview of full-duplex communication

[0097] As mentioned above, full-duplex (FD) devices are capable of sending network data in both directions simultaneously. In contrast, half-duplex (HD) devices can only send in one direction at a time. With HD mode, data can move in both directions, but not at the same time.

[0098] Examples of FD communication include in-band FD (IBFD) and sub-band FD. Figure 5A and Figure 5B As shown in Figure 1, with IBFD, devices can transmit and receive on the same time-frequency resources. In this case, the downlink (DL) and uplink (UL) share the same IBFD time-frequency resources, which may completely overlap ( Figure 5A ) or partially overlap ( Figure 5B ).

[0099] like Figure 5C As shown, in the case of SBFD (also known as flexible duplexing), a device can transmit and receive simultaneously but using different frequency resources. In this case, DL resources can be separated from UL resources in the frequency domain by a guard band.

[0100] Interference to UEs and / or network entities (e.g., base stations such as gNBs or nodes of decomposed base stations) operating in FD mode may appear in the form of CLI from neighboring nodes as well as self-interference (SI). Figure 5A , Figure 5B , Figure 5C and FIG. 5D illustrate example interference scenarios for various FD communication use cases.

[0101] like Fig. 6A The first scenario illustrated is that the gNBs communicate using FD capabilities when FD is enabled for the gNB (e.g., with non-overlapping UL / DL subbands) but disabled for each connected UE (which in turn may be enabled for half-duplex (HD) communications). In this case, CLI between UEs, SI from the FD gNB, and CLI between the gNB and neighboring gNBs interfere with FD communications.

[0102] like Figure 6B As shown, the second scenario is when FD is enabled for both the gNB and the FD UE / client equipment (CPE) connected to the gNB, the gNB communicates with the FD UE using the FD capability. If the gNB is connected to a HD UE next to the FD UE, the gNB communicates with the HD UE. In this case, the CLI between the UEs, the SI from the gNB and the FD UE, and the CLI between the FD gNB and the neighboring gNBs interfere with the FD communication.

[0103] like Figure 6C The third scenario illustrated is when FD is enabled for two gNBs (e.g., in a multi-TRP scenario) and FD is enabled at one UE / CPE connected to the two gNBs, in which case the two gNBs can communicate with the FD UE using FD capabilities. If one of the two gNBs is connected to a HD UE next to the FD UE, then one gNB communicates with both the HD UE and the FD UE. In this case, the CLI between the UEs, the SI from the FD UE, and the CLI between the two gNBs may interfere with the FD communication.

[0104] Fig. 7A and Figure 7B Various forms of interference for FD communications are also illustrated. As illustrated in the figure, if the UE operates in HD mode and the gNB operates in FD (mode) SBFD / IBFD, the interference sources at the UE include inter-cell interference from other gNBs, intra-cell CLI from UEs in the same cell, and inter-cell CLI from UEs in neighboring cells (such as Figure 7B Additionally, there may be self-interference for full-duplex UEs.

[0105] Overview of codebook-based and non-codebook UL transmission

[0106] Some deployments support codebook-based transmission and non-codebook-based transmission schemes for uplink transmission with wideband precoder.Codebook-based UL transmission is based on BS configuration and can be used in situations where reciprocity may not hold.

[0107] Figure 8 is a call flow diagram 800 illustrating an example of a conventional codebook-based UL transmission using a wideband precoder. As illustrated, the UE transmits (unprecoded) SRS with up to 2 SRS resources, each with 1, 2, or 4 ports. The gNB measures the SRS and based on the measurements selects one SRS resource and a wideband precoder to be applied to the SRS ports within the selected resource.

[0108] As illustrated, the gNB configures the selected SRS resources for the UE via an SRS resource indicator (SRI) and configures the wideband precoder for the UE via a transmit precoder matrix indicator (TPMI). For dynamic grants, the SRI and TPMI may be configured via DCI format 0_1. For configured grants (e.g., for semi-persistent uplink), the SRI and TPMI may be configured via RRC or DCI.

[0109] The UE determines the selected SRS resources according to the SRI and determines the precoding according to the TPMI and transmits the PUSCH accordingly.

[0110] Fig. 9 is a call flow diagram 900 illustrating an example of non-codebook based UL transmission. As illustrated, the UE transmits a (pre-decoded) SRS. Although the example shows 2 SRS resources, the UE can utilize up to 4 SRS resources for transmission (where each resource has 1 port). The gNB measures the SRS and selects one or more SRS resources based on the measurement. In this case, since the UE transmits the pre-decoded SRS by selecting the SRS resource, the gNB also efficiently selects the pre-decoding. For non-codebook based UL transmission, each SRS resource corresponds to a layer. The pre-decoder of a layer is actually the pre-decoder of the SRS simulated by the UE. Selecting N SRS resources means that the rank is N. The UE will use the same pre-decoder as the SRS to send the PUSCH.

[0111] As illustrated, the gNB configures the selected SRS resources for the UE via an SRS Resource Indicator (SRI). For dynamic grants, the SRI may be configured via DCI format 0_1. For configured grants, the SRI may be configured via RRC or DCI.

[0112] Aspects related to pre-coded reference signals for CLI feedback reporting

[0113] Various aspects of the present disclosure provide techniques that can help detect potential interference sources (e.g., inter-UE CLI described above). In some cases, the aggressor UE can be configured to send a pre-coded CLI-RS, essentially mimicking a future PUSCH transmission. The victim UE can be configured to perform CLI measurements based on the transmitted pre-coded CLI-RS.

[0114] like Fig.10 As illustrated, the received (Rx) signal at the victim UE (UE1) can be expressed as:

[0115] y=HPx+H CLI Tz+n;

[0116] Among them, H CLI Tz is the effective CLI channel (based on the CLI channel and UL precoder at the aggressor).

[0117] The techniques proposed in this article enable improved channel state feedback (CSF) calculation at the victim UE, allowing the gNB to receive accurate CSF reports that capture the impact of inter-UE CLI in FD slots.

[0118] In some scenarios, unprecoded CLI channel estimation may be utilized. In this case, unprecoded CLI-RS may be used to estimate the CLI channel, and TPMI precoding may be indicated in the CSF configuration. In some cases, whether the CSF is based on precoded CLI-RS or unprecoded CLI-RS may depend on the channel conditions. For example, if the channel is associated with a rapidly changing CLI, a CSF based on precoded CLI-RS may be beneficial.

[0119] For reference Fig.11 The call flow diagram 1100 is used to understand the concept of CSF based on pre-decoded CLI-RS.

[0120] As illustrated in the figure, the aggressor UE may receive configuration information from a network entity (e.g., a node of a gNB or a disaggregated base station), which configures at least one resource for the aggressor UE to send a pre-decoded RS (CLI-RS) for the victim UE to perform CLI measurement. Similarly, the victim UE may receive configuration information for configuring the same resource for the victim UE to measure CLI.

[0121] The aggressor UE may then send a precoded RS (eg, SRS) on the resource. The victim UE may measure the CLI based on the precoded CLI-RS and generate and send a CSI report based on the measurement.

[0122] Fig.12is a timing diagram illustrating the overall procedure for CLI-aware CSI reporting under FD based on pre-coded CLI-RS from the perspective of the aggressor UE and the victim UE. Although this example shows PUSCH scheduled by dynamic grant based on DCI, the same process can also be extended to PUSCH and semi-persistent (SP) CLI-RS based on configured grant (CG).

[0123] As illustrated in the figure, the victim UE can measure CLI based on the pre-decoded CLI-RS (sent by the aggressor UE) and generate CSI / CLI reports. Based on the CSI / CLI reports, the gNB operating in FD mode can receive the pre-decoded PUSCH from the aggressor UE and send PDSCH with parameters optimized based on the CSI / CLI reports to the victim UE.

[0124] In some cases, the gNB may configure the aggressor UE with a precoded RS for probing the inter-UE CLI channel (or for Rnn measurement at the victim). To better simulate the CLI that may occur during the upcoming PUSCH transmission of the aggressor UE (at the victim UE), the CLI-RS may be precoded with the same precoder selected for the upcoming PUSCH transmission.

[0125] According to the first option, the gNB may configure a multi-port CLI-SRS for the aggressor, which is pre-coded with the same pre-decoder as PUSCH. In this case, the CLI sounding reference signal (CLI-SRS) can be used for explicit or implicit CLI channel measurement. The power control of CLI-SRS can be configured to follow the same power control of PUSCH.

[0126] According to the second option, a multi-port RS similar to CSI-RS may be pre-coded using the same pre-decoder as PUSCH. In this case, the RS may have the same number of ports as the upcoming PUSCH. For this method, the UE may need to be able to support the generation and transmission of RS similar to CSI-RS, which may not be desirable.

[0127] According to the second option, a pre-coded PUSCH demodulation reference signal (DMRS) may be used to sound the CLI channel. In some cases, the PUSCH allocation may be dynamic and the positioning of the DMRS symbols may change, and the victim UE may not know the scrambling ID used in the DMRS sequence generation. Therefore, the gNB may configure the AP multi-port CLI measurement resources that match the DMRS configuration for the victim UE. For repetitions, multiple pre-decoders may be supported. In some cases, there may be no filtering with other grants (e.g., filtering may be limited to within the repetition).

[0128] In some cases, a new RS signal that can be embedded in the PUSCH may be defined. In order to distinguish from the DMRS, the new RS may have a scrambling ID different from that of the DMRS.

[0129] In some cases (e.g., for codebook-based UL), the gNB may instruct the aggressor UE to precode CLI-SRS with the same precoder used for the upcoming PUSCH. According to one option, the pairing of CLI-RS and DG / CG PUSCH may be decided after the gNB has decided on SRI / TPMI. For DG-based UL DCI, each grant may indicate the TPMI precoder to be used. The DG UL DCI may trigger both aperiodic aperiodic (AP) multi-port CLI-SRS and PUSCH. The precoder indicated by the DCI may be used for both PUSCH and CLI-SRS. In this way, AP CLI-SRS and PUSCH are linked (paired) by the triggering DCI. In some cases, AP CLI-SRS may be configured to have the same number of ports as DG-PUSCH. The method may also be applied to CG-PUSCH (Type 2), where SP CLI-SRS and CG-PUSCH Type 2 transmissions may be similarly linked via activation DCI.

[0130] For CG-PUSCH type-1, persistent CLI-SRS can be configured and indicated via radio resource control (RRC) configuration. In this case, the same precoding and number of layers and the same SRI field can be used. If there is no indication of such parameters in the DCI, the method can also be applied to type 2 CG-PUSCH by default.

[0131] In codebook-based UL, the gNB decides the SRI based on one or more SRS resources (using parameter usage=codebook). This allows UL beam scanning, which is particularly useful for FR2. As mentioned above, the gNB may have already decided on the SRI / TPMI, or may send the CLI-SRS before selecting the SRI / TPMI.

[0132] In some cases, the aggressor UE may be configured with multiple CLI-SRS resources. In this case, each CLI-SRS may be associated with an SRS (linked by an SRI). The aggressor UE may send multiple CLI-SRS, in which case the victim UE may have multiple CLI assumptions (for reporting). For example, assuming that the resource set contains two SRS resources (two CLI-SRS resources), the aggressor UE may need to decide the TPMI used for pre-coding the CLI-SRS. In one case, the UE may be configured with a predefined rule for finding the TPMI for the CLI-SRS (e.g., based on the most recently configured PUSCH TPMI used (assuming that the TPMI is fixed for multiple PUSCH transmissions)). This can be used for CLI / CSI reporting.

[0133] In some cases, precoding may not be considered (e.g., TPMI using the identity matrix). In this case, only the analog beam may be associated with the SRI. This approach may be useful for an enhanced CSF (eCSF) framework, where the TPMI may be signaled to the victim UE as part of the eCSI reporting configuration.

[0134] In some cases, there may be a mechanism to distinguish CLI-SRS from conventional (legacy) SRS used for uplink channel estimation, because legacy SRS is not pre-coded with TPMI. In some cases, CLI-SRS may be distinguished from legacy SRS by RRC configuration. For example, in the configuration, CLI-SRS may be an SRS configuration with a new usage value (e.g., usage=CLI). Fig.13 As illustrated, in this case, the association between PUSCH and SRS may only apply to CLI-SRS (eg, and there may be no association through DCI between legacy SRS and PUSCH).

[0135] In some cases (e.g., for non-codebook based UL transmissions), the gNB may indicate to the aggressor UE the association between the CLI-SRS and the precoder for the upcoming PUSCH. For non-codebook based UL, there is typically no TPMI and precoding is transparent. In this case, the aggressor UE may derive the precoder based on the downlink (DL) CSI-RS (e.g., when the spatial relationship between the CSI-RS and SRS is indicated).

[0136] According to one option, CLI-RS and DG / CG PUSCH pairing may occur after the gNB has decided on the SRI. In this case, the DG UL DCI may indicate the SRI and trigger the AP multi-port CLI-SRS transmission. The same SRI may be used for PUSCH and CLI-SRS to indicate the number of precoders and layers to be used. The number of CLI-SRS for a port may match the number of upcoming PUSCH layers.

[0137] For CG-PUSCH type 2, the same approach may be applied, where SP CLI-SRS and CG-PUSCH type 2 transmissions are linked via activation DCI. However, for CG-PUSCH type-1, periodic SP CLI-SRS may be configured and indicated in the RRC configuration. In this case, the same SRI field may be used (if not indicated in the DCI, this may also be applied by default to CG-PUSCH type 2).

[0138] According to another option, the gNB may not decide on the SRI before the CLI-SRS is sent. In some cases, the aggressor UE may be configured with multiple multi-port CLI-SRS resources, and each CLI-SRS may be associated with an SRI selection. In this case, the aggressor UE sends multiple CLI-SRSs, and the victim will have multiple CLI hypotheses for reporting. In other cases, a dedicated CLI-SRS may not be required. In this case, the same SRS resource (e.g., using usage=nonCodebook) can be used for both UL channel and CLI measurements. In this case, the victim UE may measure multiple single-port zero-power SRSs (ZP-SRSs). This approach can be used to extend the eCSF framework to nonCodebook UL, where the eCSF report indicates to the victim UE which interference hypothesis to use.

[0139] According to certain aspects, the gNB may configure one or more multi-port ZP-SRS for victim UEs for measurements on pre-coded CLI channels. According to one option, to enable CLI-aware CSF, each ZP-SRS may be used to derive a CLI hypothesis, which in turn may be used to determine preferred CSF parameters. In this case, the CLI hypothesis may be the covariance matrix of the pre-coded CLI channel Or a combined Rnn measurement for one or more CLI sources and other residual interference plus noise. According to another option, the victim UE may report explicit CLI measurements to the gNB. For example, the victim UE may report the covariance of the CLI channel or Rnn feedback.

[0140] As described above, in some cases, the CLI-SRS may be sent before the TPMI is determined. In this case, if the eCSF is configured for codebook-based UL, the TPMI may be unknown when the CLI-SRS is sent. According to one option, no precoding may be applied to the CLI-SRS (TPMI is the identity matrix) and only simulated beams may be associated with the SRI. The victim UE may be configured for eCSF reporting and one or more TPMIs may be indicated in the eCSF reporting configuration.

[0141] In some cases, when CLI-SRS is sent, SRI (non-codebook UL) may be unknown. In this case, the same SRS resource (with usage=nonCodebook) can be used for both UL channel estimation and CLI channel sounding. The victim UE may be configured with multiple single-port ZP-SRS and configured for eCSF reporting to indicate the CLI assumption. In the case of NonCodebook UL, the CLI assumption may be an SRI value (the SRI value may indicate the UL rank and layer index). In this case, the eCSF report configuration may include one or more CLI assumptions.

[0142] In some cases, the CLI spatial response may depend on the selection of TPMI and rank at the aggressor. In turn, the optimal CSF selection (e.g., PMI, RI, CQI) may be different for different TPMI / rank assumptions at the aggressor. Single-layer CLI and multi-layer CLI may also be different because multi-layer interference may cover wider angles and be more difficult to avoid in angular space. Single-layer interference may result in non-uniform CLI in angular space. In some cases, the performance may depend on the pre-coded CLI channel, the orientation of the victim UE and the aggressor UE, and the TPMI selection at the aggressor UE.

[0143] Example Operation of User Equipment

[0144] Fig.14 The method for transmitting the signal to the aggressor UE (such as Figure 1 and Figure 3 An example of a method 1400 for performing wireless communications with a UE 104).

[0145] Method 1400 begins at step 1405, receiving configuration information, the configuration information configuring at least one resource for the aggressor UE to send a pre-decoded RS for the victim UE to perform CLI measurement. In some cases, the operation of this step refers to or can be referred to as Fig.17 The circuit for receiving and / or the code for receiving are executed.

[0146] Then, the method 1400 proceeds to step 1410: sending the pre-decoded RS on the resource. In some cases, the operation of this step refers to or can be referred to as Fig.17 The circuit for sending and / or the code for sending are executed.

[0147] In some aspects, the method 1400 further comprises sending the PUSCH using the same pre-decoder used when sending the pre-decoded RS. In some cases, the operation of this step refers to or can be performed by referring to Fig.17 The circuit for sending and / or the code for sending are executed.

[0148] In some aspects, the configuration information configures the UE to use the same precoder as the PUSCH to send the multi-port CLI-SRS.

[0149] In some aspects, the UE transmits multi-port CLI-SRS with power control based on power control of the PUSCH.

[0150] In some aspects, the configuration information configures the UE to use the same precoder as the PUSCH to send the multi-port RS; and the RS is sent using the same number of ports as the PUSCH.

[0151] In some aspects, the RS comprises a PUSCH DMRS with dynamic symbol positioning.

[0152] In some aspects, the RS is embedded in the PUSCH; and the RS embedded in the PUSCH is scrambled with a scrambling ID different from a scrambling ID used to scramble the DMRS.

[0153] In some aspects, the method 1400 also includes receiving an indication from a network entity that the aggressor UE is to precode the RS using the same precoder as used to transmit the PUSCH. In some cases, the operation of this step refers to or can be performed by reference to Fig.17 The circuit for receiving and / or the code for receiving are executed.

[0154] In some aspects, the indication is sent as a DCI.

[0155] In some aspects, the DCI indicates the TPMI used for precoding RS and PUSCH.

[0156] In some aspects, the aggressor UE is configured with rules for determining the TPMI for precoding the RS on each of the plurality of resources.

[0157] In some aspects, the indication is provided via RRC configuration.

[0158] In some aspects, the configuration information configures a plurality of resources for the aggressor UE, each resource being associated with an RS sent for CLI measurement of the victim UE.

[0159] In some aspects, these rules allow the identity matrix to be used as the TPMI.

[0160] In some aspects, the method 1400 further includes receiving an indication of an association between the pre-decoded RS and a pre-decoder for an upcoming PUSCH. In some cases, the operation of this step refers to or may be performed by reference to Fig.17 The circuit for receiving and / or the code for receiving are executed.

[0161] In some aspects, the association is provided by a SRI indicated via a DCI.

[0162] In some aspects, the RRC configuration indicates that the association is provided via SRI.

[0163] In some aspects, where the DCI does not indicate a SRI, a default association is assumed.

[0164] In some aspects, the aggressor is configured with a plurality of resources for sending precoded RS for CLI measurement by the victim UE; and each resource of the plurality of resources is associated with a SRI.

[0165] In some aspects, the precoded RS includes an SRS; and the configuration information indicates a usage type of the SRS for CLI measurement.

[0166] In some aspects, the resources are also used to send SRS for uplink channel measurements.

[0167] In one aspect, method 1400 or any aspect related thereto may be performed by an apparatus such as Fig.17 The method 1400 is performed by a communication device 1700 that includes various components that are operable, configured, or adapted to perform the method 1400. The communication device 1700 is described in more detail below.

[0168] It should be noted that Fig.14 This is merely one example of a method, and other methods including fewer, additional, or alternative steps may also be consistent with the present disclosure.

[0169] Fig.15 The method for a victim UE (such as Figure 1 and Figure 3 An example of a method 1500 for performing wireless communications with a UE 104).

[0170] The method 1500 begins at step 1505 by receiving configuration information, the configuration information configuring one or more CLI measurement resources for the victim UE to measure the CLI SRS. In some cases, the operation of this step refers to or can be referred to as Fig.18 The circuit for receiving and / or the code for receiving are executed.

[0171] Then, the method 1500 proceeds to step 1510, measuring the CLI based on the SRS sent on the CLI measurement resource. In some cases, the operation of this step refers to or can be referred to as Fig.18 The circuit for measuring and / or the code for measuring are executed.

[0172] Then, method 1500 proceeds to step 1515, sending a report based on the measured CLI. In some cases, the operation of this step refers to or can be referred to as Fig.18 The circuit for sending and / or the code for sending are executed.

[0173] In some aspects, the configuration information configures one or more multi-port ZP-SRS resources for a victim UE for measurement of a precoded CLI SRS.

[0174] In some aspects, the method 1500 further includes deriving a CLI hypothesis based on measurements made on each ZP-SRS resource. In some cases, the operation of this step refers to or may be performed by reference to Fig.18 The circuit for deriving and / or the code for deriving are used to perform the deriving.

[0175] In some aspects, the report includes explicit CLI measurements made on the ZP-SRS resources.

[0176] In some aspects, the configuration information indicates one or more TPMIs.

[0177] In some aspects, the configuration information configures a plurality of single-port ZP-SRS resources for the victim UE for measurement of precoded CLI SRS; and the report indicates a CLI hypothesis based on the measurements made on the plurality of single-port ZP-SRS resources.

[0178] In one aspect, method 1500 or any aspect related thereto may be performed by an apparatus such as Fig.18 The method 1500 is performed by a communication device 1800 that includes various components operable to, configured to, or adapted to perform the method 1500. The communication device 1800 is described in more detail below.

[0179] It should be noted that Fig.15This is merely one example of a method, and other methods including fewer, additional, or alternative steps may also be consistent with the present disclosure.

[0180] Example Operations of Network Entities

[0181] Fig.16 shows a method for use by network entities such as Figure 1 and Figure 3 BS102 or as relative to Figure 2 An example of a method 1600 of performing wireless communications with a decomposed base station is discussed.

[0182] Method 1600 begins at step 1605, sending first configuration information, the first configuration information configuring at least one resource for the aggressor UE to send a pre-decoded RS for the victim UE to perform CLI measurement. In some cases, the operation of this step refers to or can be referred to as Fig.19 The circuit for sending and / or the code for sending are executed.

[0183] Then, the method 1600 proceeds to step 1610, sending second configuration information, the second configuration information configuring one or more CLI measurement resources for the victim UE to measure the CLI SRS. In some cases, the operation of this step refers to or can be referred to as Fig.19 The circuit for sending and / or the code for sending are executed.

[0184] Then, the method 1600 proceeds to step 1615 to receive a report generated by the victim UE based on the measured CLI SRS. In some cases, the operation of this step refers to or can be performed by referring to Fig.19 The circuit for receiving and / or the code for receiving are executed.

[0185] In some aspects, the method 1600 also includes receiving a PUSCH transmitted using the same precoder as used when transmitting the precoded RS. In some cases, the operation of this step refers to or can be performed by referring to Fig.19 The circuit for receiving and / or the code for receiving are executed.

[0186] In some aspects, the configuration information configures the UE to use the same precoder as the PUSCH to send the multi-port CLI-SRS.

[0187] In some aspects, the configuration information configures the aggressor UE to transmit the multi-port RS using the same precoder as the PUSCH.

[0188] In some aspects, the method 1600 also includes sending an indication that the aggressor UE is to precode the RS using the same precoder as used to send the PUSCH. In some cases, the operation of this step refers to or can be performed by reference to Fig.19 The circuit for sending and / or the code for sending are executed.

[0189] In some aspects, the indication is sent as a DCI.

[0190] In some aspects, the DCI indicates the TPMI used for precoding RS and PUSCH.

[0191] In some aspects, the aggressor UE is configured with rules for determining the TPMI for precoding the RS on each of the plurality of resources.

[0192] In some aspects, the indication is provided via RRC configuration.

[0193] In some aspects, the configuration information configures a plurality of resources for the aggressor UE, each resource being associated with an RS sent for CLI measurement of the victim UE.

[0194] In some aspects, the method 1600 further includes sending an indication of an association between the pre-coded RS and a pre-decoder for an upcoming PUSCH. In some cases, the operation of this step refers to or may be performed by reference to Fig.19 The circuit for sending and / or the code for sending are executed.

[0195] In some aspects, the association is provided by a SRI indicated via a DCI.

[0196] In some aspects, the RRC configuration indicates that the association is provided via SRI.

[0197] In some aspects, the aggressor is configured with a plurality of resources for sending precoded RS for CLI measurement by the victim UE; and each resource of the plurality of resources is associated with a SRI.

[0198] In some aspects, the configuration information configures one or more multi-port ZP-SRS resources for a victim UE for measurement of a precoded CLI SRS.

[0199] In some aspects, the report includes explicit CLI measurements made on the ZP-SRS resources.

[0200] In some aspects, the configuration information indicates one or more TPMIs.

[0201] In some aspects, the configuration information configures a plurality of single-port ZP-SRS resources for the victim UE for measurement of precoded CLI SRS; and the report indicates a CLI hypothesis based on the measurements made on the plurality of single-port ZP-SRS resources.

[0202] In one aspect, method 1600 or any aspect related thereto may be performed by an apparatus such as Fig.19 The method 1600 is performed by a communication device 1900 that includes various components operable to, configured to, or adapted to perform the method 1600. The communication device 1900 is described in more detail below.

[0203] It should be noted that Fig.16 This is merely one example of a method, and other methods including fewer, additional, or alternative steps may also be consistent with the present disclosure.

[0204] Example Communication Device

[0205] Fig.17 Depicted are aspects of an example communications device 1700. In some aspects, communications device 1700 is user equipment, such as described above with respect to Figure 1 and Figure 3 The UE 104.

[0206] The communication device 1700 includes a processing system 1705 coupled to a transceiver 1745 (e.g., a transmitter and / or a receiver). The transceiver 1745 is configured to transmit and receive signals for the communication device 1700, such as the various signals described herein, via an antenna 1750. The processing system 1705 may be configured to perform processing functions for the communication device 1700, including processing signals received by the communication device 1700 and / or to be transmitted by the communication device.

[0207] The processing system 1705 includes one or more processors 1710. In various aspects, such as with respect to Figure 3 As described, the one or more processors 1710 may represent one or more of the receive processor 358, the transmit processor 364, the TX MIMO processor 366, and / or the controller / processor 380. The one or more processors 1710 are coupled to the computer-readable medium / memory 1725 via the bus 1740. In some aspects, the computer-readable medium / memory 1725 is configured to store instructions (e.g., computer-executable code) that, when executed by the one or more processors 1710, cause the one or more processors 1710 to perform operations relative to the computer-readable medium / memory 1725. Fig.14The method 1400 or any aspect related thereto is described. It should be noted that references to a processor performing a function of the communication device 1700 may include one or more processors 1710 performing that function of the communication device 1700.

[0208] In the depicted example, computer readable medium / memory 1725 stores code (e.g., executable instructions), such as code for receiving 1730 and code for transmitting 1735. Processing of code for receiving 1730 and code for transmitting 1735 may cause communication device 1700 to perform operations relative to Fig.14 The method 1400 described herein or any aspect related thereto.

[0209] The one or more processors 1710 include circuits configured to implement (e.g., execute) code stored in the computer-readable medium / memory 1725, including circuits such as circuits for receiving 1715 and circuits for transmitting 1720. Processing by the circuits for receiving 1715 and the circuits for transmitting 1720 may enable the communication device 1700 to perform operations relative to Fig.14 The method 1400 described herein or any aspect related thereto.

[0210] The various components of the communication device 1700 may be provided for performing Fig.14 The components of the method 1400 or any aspect related to the method. For example, the components for sending, transmitting or outputting for sending may include Figure 3 The illustrated transceiver 354 and / or antenna 352 of the UE 104, and / or Fig.17 The transceiver 1745 and antenna 1750 of the communication device 1700 in FIG. 1 may include Figure 3 The illustrated transceiver 354 and / or antenna 352 of the UE 104, and / or Fig.17 The transceiver 1745 and antenna 1750 of the communication device 1700.

[0211] Fig.18 Depicted are aspects of an example communications device 1800. In some aspects, the communications device 1800 is user equipment, such as described above with respect to Figure 1 and Figure 3 The UE 104.

[0212] The communication device 1800 includes a processing system 1805 coupled to a transceiver 1865 (e.g., a transmitter and / or a receiver). The transceiver 1865 is configured to transmit and receive signals for the communication device 1800, such as various signals as described herein, via an antenna 1870. The processing system 1805 may be configured to perform processing functions for the communication device 1800, including processing signals received and / or to be transmitted by the communication device 1800.

[0213] The processing system 1805 includes one or more processors 1810. In various aspects, such as with respect to Figure 3 As described, the one or more processors 1810 may represent one or more of the receive processor 358, the transmit processor 364, the TX MIMO processor 366, and / or the controller / processor 380. The one or more processors 1810 are coupled to the computer-readable medium / memory 1835 via the bus 1860. In some aspects, the computer-readable medium / memory 1835 is configured to store instructions (e.g., computer-executable code) that, when executed by the one or more processors 1810, cause the one or more processors 1810 to perform operations relative to the computer-readable medium / memory 1835. Fig.15 The method 1500 or any aspect related thereto is described. It should be noted that references to a processor performing a function of the communication device 1800 may include one or more processors 1810 performing that function of the communication device 1800.

[0214] In the depicted example, computer readable medium / memory 1835 stores code (e.g., executable instructions), such as code 1840 for receiving, code 1845 for measuring, code 1850 for sending, and code 1855 for deriving. Processing of code 1840 for receiving, code 1845 for measuring, code 1850 for sending, and code 1855 for deriving may cause communication device 1800 to perform operations relative to Fig.15 The method 1500 described herein or any aspect related thereto.

[0215] The one or more processors 1810 include circuits configured to implement (e.g., execute) code stored in the computer-readable medium / memory 1835, including circuits such as circuits for receiving 1815, circuits for measuring 1820, circuits for transmitting 1825, and circuits for deriving 1830. The processing of the circuits for receiving 1815, measuring 1820, transmitting 1825, and deriving 1830 may cause the communication device 1800 to perform operations relative to Fig.15 The method 1500 described herein or any aspect related thereto.

[0216] The various components of the communication device 1800 may be provided for performing Fig.15 The components of the method 1500 or any aspect related to the method. For example, the components for sending, transmitting or outputting for sending may include Figure 3 The illustrated transceiver 354 and / or antenna 352 of the UE 104, and / or Fig.18 The transceiver 1865 and antenna 1870 of the communication device 1800 in FIG. 1 may include Figure 3 The illustrated transceiver 354 and / or antenna 352 of the UE 104, and / or Fig.18 The transceiver 1865 and antenna 1870 of the communication device 1800.

[0217] Fig.19 Various aspects of an example communications device 1900 are depicted. In some aspects, communications device 1900 is a network entity such as Figure 1 and Figure 3 BS102 or as relative to Figure 2 The decomposed base station in question.

[0218] The communication device 1900 includes a processing system 1905 coupled to a transceiver 1945 (e.g., a transmitter and / or a receiver) and / or a network interface 1955. The transceiver 1945 is configured to transmit and receive signals for the communication device 1900 via an antenna 1950, such as the various signals described herein. The network interface 1955 is configured to transmit and receive signals for the communication device 1900 via a communication link (e.g., as described herein with respect to Figure 2 The backhaul link, midhaul link and / or fronthaul link) obtains and transmits signals for the communication device 1900. The processing system 1905 can be configured to perform processing functions of the communication device 1900, including processing signals received and / or to be sent by the communication device 1900.

[0219] The processing system 1905 includes one or more processors 1910. In various aspects, such as with respect to Figure 3 As described, the one or more processors 1910 may represent one or more of the receive processor 338, the transmit processor 320, the TX MIMO processor 330, and / or the controller / processor 340. The one or more processors 1910 are coupled to the computer-readable medium / memory 1925 via the bus 1940. In certain aspects, the computer-readable medium / memory 1925 is configured to store instructions (e.g., computer-executable code) that, when executed by the one or more processors 1910, cause the one or more processors 1910 to perform operations relative to the computer-readable medium / memory 1925. Fig.16The method 1600 or any aspect related thereto is described. It should be noted that reference to a processor of the communication device 1900 that performs a function may include one or more processors 1910 of the communication device 1900 that perform that function.

[0220] In the depicted example, computer readable medium / memory 1925 stores code (e.g., executable instructions), such as code for transmitting 1930 and code for receiving 1935. Processing of code for transmitting 1930 and code for receiving 1935 may cause communication device 1900 to perform operations with respect to Fig.16 The method 1600 described herein or any aspect related thereto.

[0221] The one or more processors 1910 include circuits configured to implement (e.g., execute) code stored in the computer-readable medium / memory 1925, including circuits such as circuits for transmitting 1915 and circuits for receiving 1920. Processing by the circuits for transmitting 1915 and the circuits for receiving 1920 may enable the communication device 1900 to perform operations with respect to Fig.16 The method 1600 described herein or any aspect related thereto.

[0222] The various components of the communication device 1900 may be provided for performing Fig.16 Means for sending, transmitting or outputting for sending may include Figure 3 The transceiver 332 and / or antenna 334 of BS 102 are shown, and / or Fig.19 The transceiver 1945 and antenna 1950 of the communication device 1900 in FIG. 1 may include Figure 3 The illustrated transceiver 332 and / or antenna 334 of the BS 102, and / or Fig.19 The transceiver 1945 and antenna 1950 of the communication device 1900.

[0223] Sample Clauses

[0224] Specific implementation examples are described in the following numbered clauses:

[0225] Clause 1: A method for wireless communication by an aggressor UE, comprising: receiving configuration information, the configuration information configuring at least one resource for the aggressor UE to send a pre-decoded RS for a victim UE to perform CLI measurement; and sending the pre-decoded RS on the resource.

[0226] Clause 2: The method of clause 1, further comprising: transmitting a PUSCH using the same precoder as used when transmitting the precoded RS.

[0227] Clause 3: The method of clause 2, wherein the configuration information configures the UE to transmit multi-port CLI-SRS using the same precoder as the PUSCH.

[0228] Clause 4: The method of clause 3, wherein the UE transmits the multi-port CLI-SRS with power control based on power control of the PUSCH.

[0229] Clause 5: The method of clause 2, wherein: the configuration information configures the UE to use the same precoder as the PUSCH to send a multi-port RS; and the RS is sent using the same number of ports as the PUSCH.

[0230] Clause 6: A method as set forth in clause 2, wherein the RS comprises a PUSCH DMRS with dynamic symbol positioning.

[0231] Clause 7: The method of clause 2, wherein: the RS is embedded in the PUSCH; and the RS embedded in the PUSCH is scrambled using a scrambling ID different from a scrambling ID used to scramble a DMRS.

[0232] Clause 8: The method of clause 2, further comprising: receiving an indication from a network entity, the indication instructing the aggressor UE to precode the RS using the same precoder as the precoder used to transmit the PUSCH.

[0233] Clause 9: The method of clause 8, wherein the indication is sent as a DCI.

[0234] Clause 10: The method of clause 9, wherein the DCI indicates a TPMI used for precoding the RS and the PUSCH.

[0235] Clause 11: The method of clause 10, wherein the aggressor UE is configured with rules for determining the TPMI for precoding the RS on each of the plurality of resources.

[0236] Clause 12: A method as described in clause 8, wherein the indication is provided via RRC configuration.

[0237] Clause 13: The method of clause 8, wherein the configuration information configures a plurality of resources for the aggressor UE, each resource being associated with an RS sent for CLI measurement of the victim UE.

[0238] Clause 14: The method of clause 13, wherein the rule allows the identity matrix to be the TPMI.

[0239] Clause 15: The method of clause 2, further comprising: receiving an indication of an association between the precoded RS and a precoder for an upcoming PUSCH.

[0240] Clause 16: A method as described in clause 15, wherein the association is provided by a SRI indicated via a DCI.

[0241] Clause 17: A method as described in clause 16, wherein the RRC configuration indicates that the association is provided via SRI.

[0242] Clause 18: A method as described in clause 15, wherein in the event that the DCI does not indicate an SRI, a default association is assumed.

[0243] Clause 19: The method of clause 15, wherein: the aggressor is configured with a plurality of resources for sending precoded RS for the victim UE to perform CLI measurement; and each resource of the plurality of resources is associated with a SRI.

[0244] Clause 20: A method as described in any of clauses 1 to 19, wherein: the precoded RS comprises an SRS; and the configuration information indicates a usage type of the SRS for CLI measurement.

[0245] Clause 21: A method as described in any of clauses 1 to 20, wherein the resources are also used to send an SRS for uplink channel measurement.

[0246] Clause 22: A method of wireless communication by a victim UE, comprising: receiving configuration information, the configuration information configuring one or more CLI measurement resources for the victim UE for measuring CLI SRS; measuring CLI based on SRS sent on the CLI measurement resources; and sending a report based on the measured CLI.

[0247] Clause 23: The method of clause 22, wherein the configuration information configures one or more multi-port ZP-SRS resources for the victim UE for measurement of precoded CLI SRS.

[0248] Clause 24: The method of clause 23, further comprising: deriving a CLI hypothesis based on measurements made on each ZP-SRS resource.

[0249] Clause 25: The method of clause 23, wherein the reporting comprises explicit CLI measurements made on the ZP-SRS resources.

[0250] Clause 26: A method as recited in any one of clauses 22 to 25, wherein the configuration information indicates one or more TPMIs.

[0251] Clause 27: A method according to any one of clauses 22 to 26, wherein: the configuration information configures multiple single-port ZP-SRS resources for the victim UE for measurement of pre-decoded CLI SRS; and the report indicates a CLI hypothesis based on measurements made on the multiple single-port ZP-SRS resources.

[0252] Clause 28: A method for wireless communication by a network entity, comprising: sending first configuration information, wherein the first configuration information configures at least one resource for an aggressor UE to send a pre-decoded RS for a victim UE to perform CLI measurement; sending second configuration information, wherein the second configuration information configures one or more CLI measurement resources for the victim UE to measure CLI SRS; and receiving a report generated by the victim UE based on the measured CLI SRS.

[0253] Clause 29: The method of clause 28, further comprising: receiving a PUSCH transmitted using the same precoder as used when transmitting the precoded RS.

[0254] Clause 30: The method of clause 29, wherein the configuration information configures the UE to transmit multi-port CLI-SRS using the same precoder as the PUSCH.

[0255] Clause 31: The method of clause 29, wherein the configuration information configures the aggressor UE to transmit a multi-port RS using the same precoder as the PUSCH.

[0256] Clause 32: The method of clause 29, further comprising sending an indication that the aggressor UE is to precode the RS using the same precoder as the precoder used to transmit the PUSCH.

[0257] Clause 33: The method of clause 32, wherein the indication is sent as a DCI.

[0258] Clause 34: A method as set forth in clause 33, wherein the DCI indicates a TPMI for precoding the RS and the PUSCH.

[0259] Clause 35: The method of clause 34, wherein the aggressor UE is configured with rules for determining the TPMI for precoding the RS on each of the plurality of resources.

[0260] Clause 36: A method as described in clause 32, wherein the indication is provided via RRC configuration.

[0261] Clause 37: The method of clause 32, wherein the configuration information configures a plurality of resources for the aggressor UE, each resource being associated with an RS sent for CLI measurement of the victim UE.

[0262] Clause 38: The method of clause 29, further comprising: sending an indication of an association between the precoded RS and a precoder for an upcoming PUSCH.

[0263] Clause 39: A method as described in clause 38, wherein the association is provided by a SRI indicated via a DCI.

[0264] Clause 40: A method as described in clause 38, wherein the RRC configuration indicates that the association is provided via SRI.

[0265] Clause 41: The method of clause 38, wherein the aggressor is configured with a plurality of resources for sending precoded RS for the victim UE to perform CLI measurement; and each resource of the plurality of resources is associated with a SRI.

[0266] Clause 42: A method as described in any of clauses 28 to 41, wherein the configuration information configures one or more multi-port ZP-SRS resources for the victim UE for measurement of pre-coded CLI SRS.

[0267] Clause 43: The method of clause 42, wherein the reporting comprises explicit CLI measurements made on the ZP-SRS resources.

[0268] Clause 44: A method as recited in any one of clauses 28 to 43, wherein the configuration information indicates one or more TPMIs.

[0269] Clause 45: A method according to any one of clauses 28 to 44, wherein: the configuration information configures multiple single-port ZP-SRS resources for the victim UE for measurement of pre-decoded CLI SRS; and the report indicates a CLI hypothesis based on measurements made on the multiple single-port ZP-SRS resources.

[0270] Clause 46: An apparatus comprising: a memory including executable instructions; and a processor configured to execute the executable instructions and cause the apparatus to perform the method of any one of clauses 1 to 45.

[0271] Clause 47: An apparatus comprising: means for performing the method according to any one of clauses 1 to 45.

[0272] Clause 48: A non-transitory computer readable medium comprising executable instructions which, when executed by a processor of an apparatus, cause the apparatus to perform the method of any one of clauses 1 to 45.

[0273] Clause 49: A computer program product embodied on a computer readable storage medium, the computer readable storage medium comprising code for performing the method according to any one of clauses 1 to 45.

[0274] Additional considerations

[0275] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. The examples discussed herein are not limited to the scope, applicability or aspects set forth in the claims. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. For example, without departing from the scope of the present disclosure, the functions and arrangements of the elements discussed may be changed. Each example may omit, replace or add various procedures or components as appropriate. For example, the described method may be performed in an order different from the order described, and various actions may be added, omitted or combined. In addition, the features described for some examples may be combined in some other examples. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods practiced using other structures, functionality, or structures and functionality other than the various aspects of the present disclosure set forth herein or different from the various aspects of the present disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.

[0276] The various illustrative logical blocks, modules, and circuits described in conjunction with the present disclosure may be implemented or executed using a general purpose processor, a digital signal processor (DSP), an ASIC, a field programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic components, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any commercially available processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, a system on a chip (SoC), or any other such configuration.

[0277] As used herein, a phrase referring to "at least one of" a list of items refers to any combination of those items (including single members). As an example, "at least one of a, b, or c" is intended to cover: a, b, c, ab, ac, bc, and abc, as well as any combination with multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other ordering of a, b, and c).

[0278] As used herein, the term "determining" encompasses a wide variety of actions. For example, "determining" may include calculating, computing, processing, deriving, investigating, searching (e.g., searching in a table, a database, or another data structure), ascertaining, and the like. Additionally, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), and the like. Furthermore, "determining" may include resolving, selecting, choosing, establishing, and the like.

[0279] The method disclosed herein includes one or more actions for implementing the method. The method actions may be interchangeable with each other without departing from the scope of the claims. In other words, unless a specific order of actions is specified, the order and / or use of specific actions may be modified without departing from the scope of the claims. In addition, the various operations of the method described above may be performed by any suitable component capable of performing the corresponding function. The component may include various hardware and / or software components and / or modules, including but not limited to circuits, application specific integrated circuits (ASICs) or processors.

[0280] The following claims are not intended to be limited to the various aspects shown herein, but should be given the full scope consistent with the language of the claims. Within the claims, unless otherwise specified, reference to an element in the singular form is not intended to mean "one and only one", but "one or more". Unless otherwise specified, the term "some" refers to one or more. Any claim element is not interpreted according to the provisions of 35 U.S.C. § 112 (f) unless the element is explicitly stated using the phrase "member for...". All structural and functional equivalents of the elements of the various aspects described throughout this disclosure that are known or will be known later to a person of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. In addition, regardless of whether such disclosure is explicitly stated in the claims, anything disclosed herein is not intended to be disclosed to the public.

Claims

1. A method for wireless communication by an aggressor user equipment (UE), comprising: receiving configuration information, wherein the configuration information configures at least one resource for the aggressor UE to send a pre-coded reference signal (RS) for the victim UE to perform cross-link interference (CLI) measurement; and The precoded RS is sent on the resource.

2. The method of claim 1, further comprising transmitting a physical uplink shared channel (PUSCH) using the same precoder as used when transmitting the precoded RS.

3. The method according to claim 2, wherein: The configuration information configures the UE to use the same precoder as the PUSCH to send a multi-port CLI sounding reference signal (CLI-SRS). 4 . The method of claim 3 , wherein the UE transmits the multi-port CLI-SRS with power control based on power control of the PUSCH.

5. The method according to claim 2, wherein: The configuration information configures the UE to use the same predecoder as the PUSCH to send a multi-port RS; and The RS is transmitted using the same number of ports as the PUSCH.

6. The method according to claim 2, wherein: The RS includes a PUSCH Demodulation Reference Signal (DMRS) with dynamic symbol positioning.

7. The method according to claim 2, wherein: The RS is embedded in the PUSCH; and The RS embedded in the PUSCH is scrambled using a scrambling ID different from a scrambling ID used to scramble a demodulation reference signal (DMRS).

8. The method of claim 2, further comprising receiving an indication from a network entity, the indication instructing the aggressor UE to precode the RS using the same precoder as the precoder used to transmit the PUSCH.

9. The method of claim 8, wherein the indication is sent as downlink control information (DCI).

10. The method of claim 8, wherein the indication is provided via a radio resource control (RRC) configuration.

11. The method according to claim 9, wherein the DCI indicates a transmitted precoding matrix indicator (TPMI) for precoding the RS and the PUSCH.

12. The method according to claim 8, wherein the configuration information configures a plurality of resources for the aggressor UE, each resource being associated with an RS sent for CLI measurement of the victim UE.

13. The method according to claim 12, wherein: The aggressor UE is configured with rules for determining a TPMI for precoding a RS on each of the plurality of resources. The method of claim 12 , wherein the rule allows the identity matrix as the TPMI.

15. The method of claim 1, wherein: The pre-coded RS includes a sounding reference signal (SRS); and The configuration information indicates the usage type of the SRS for CLI measurement.

16. The method according to claim 2, further comprising: An indication of an association between the precoded RS and a precoder for an upcoming PUSCH is received.

17. The method of claim 16, wherein the association is provided by a sounding reference signal (SRS) resource identifier (SRI) indicated via downlink control information (DCI).

18. The method of claim 17, wherein a radio resource control (RRC) configuration indicates that the association is provided via a SRI. The method of claim 16 , wherein in case the DCI does not indicate a SRI, a default association is assumed.

20. The method of claim 16, wherein: The aggressor is configured with a plurality of resources for sending a pre-coded RS for the victim UE to perform CLI measurement; and Each resource of the plurality of resources is associated with a sounding reference signal (SRS) resource identifier (SRI).

21. The method of claim 1, wherein the resources are also used to transmit a sounding reference signal (SRS) for uplink channel measurement.

22. A method for wireless communication by a victim user equipment (UE), comprising: receiving configuration information, wherein the configuration information configures one or more CLI measurement resources for the victim UE to measure a cross-link interference (CLI) sounding reference signal (SRS); measuring the CLI based on the SRS sent on the CLI measurement resource; and Send reports based on the measured CLI.

23. The method according to claim 22, wherein the configuration information configures one or more multi-port zero-power SRS (ZP-SRS) resources for the victim UE for measurement of pre-coded CLI SRS.

24. The method according to claim 23, further comprising: The CLI assumptions are derived based on measurements made on each ZP-SRS resource.

25. The method of claim 23, wherein the reporting comprises explicit CLI measurements made on the ZP-SRS resources.

26. The method of claim 22, wherein the configuration information indicates one or more transmitted precoding matrix indicators (TPMIs).

27. The method of claim 22, wherein: The configuration information configures a plurality of single-port zero-power SRS (ZP-SRS) resources for the victim UE for measurement of pre-decoded CLI SRS; and The report indicates a CLI assumption based on measurements made on the plurality of single-port ZP-SRS resources.

28. A method for wireless communication by a network entity, the method comprising: Sending first configuration information, wherein the first configuration information configures at least one resource for an aggressor user equipment (UE) to send a pre-decoded reference signal (RS) for a victim UE to perform cross link interference (CLI) measurement; Sending second configuration information, where the second configuration information configures one or more CLI measurement resources for the victim UE to measure the CLI SRS; as well as A report generated by the victim UE based on the measured CLI SRS is received.

29. The method according to claim 28, further comprising: A physical uplink shared channel (PUSCH) transmitted using the same precoder as used when transmitting the pre-decoded RS is received.

30. The method of claim 29, wherein: The configuration information configures the UE to use the same precoder as the PUSCH to send a multi-port CLI sounding reference signal (CLI-SRS).

Images