WO2024150204A1

WO2024150204A1 - Embedding cross-link interference measurements in channel state information measurements

Info

Publication number: WO2024150204A1
Application number: PCT/IB2024/052434
Authority: WO
Inventors: Khaled Nafez Rauf ARDAH; Ali Ramadan ALI; Ravi Kuchibhotla
Original assignee: Lenovo Singapore Pte Ltd
Current assignee: Lenovo Singapore Pte Ltd
Priority date: 2023-03-23
Filing date: 2024-03-13
Publication date: 2024-07-18
Anticipated expiration: 2025-09-23
Also published as: WO2024150204A9

Abstract

Various aspects of the present disclosure relate to embedding cross-link interference measurements in channel state information measurements. A victim UE is configured with CLI measurement and reporting configurations and channel state information (CSI) measurement and reporting resource configurations. An aggressor UE is configured with one or more muted uplink resources that are colliding with one or more measurement resources at the victim UE. The victim UE transmits one or more CSI measurement reports and one or more CLI measurement reports to a network entity, where at least one of the CLI measurements is embedded in CSI measurements of the CSI measurement report.

Description

EMBEDDING CROSS-LINK INTERFERENCE MEASUREMENTS IN CHANNEL STATE INFORMATION MEASUREMENTS

RELATED APPLICATION

[0001] This application claims priority to U.S. Patent Application Serial No. 63/491,927 filed March 23, 2023 entitled “EMBEDDING CROSS-LINK INTERFERENCE MEASUREMENTS IN CHANNEL STATE INFORMATION MEASUREMENTS,” the disclosure of which is incorporated by reference herein in its entirety.

TECHNICAL FIELD

[0002] The present disclosure relates to wireless communications, and more specifically to cross-link interference (CLI) measurement and reporting.

BACKGROUND

[0003] A wireless communications system may include one or multiple network communication devices, such as base stations, which may be otherwise known as an eNodeB (eNB), a nextgeneration NodeB (gNB), or other suitable terminology. Each network communication devices, such as a base station may support wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE), or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers). Additionally, the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G)).

[0004] Given the various network communication devices and user communication devices in a wireless communication system, situations can arise where these devices interfere with one another. For example, a victim UE may experience interference on its downlink reception due to an uplink transmission of one or more nearby aggressor UEs, which is also referred to as CLI.

SUMMARY

[0005] The present disclosure relates to methods, apparatuses, and systems that support embedding cross-link interference measurements in channel state information measurements. A victim UE is configured with CLI measurement and reporting configurations and channel state information (CSI) measurement and reporting resource configurations. An aggressor UE is configured with one or more muted uplink resources that are colliding with one or more measurement resources at the victim UE. The victim UE transmits one or more CSI measurement reports and one or more CLI measurement reports to a network entity, where at least one of the CLI measurements is embedded in CSI measurements of the CSI measurement report. By embedding one or more CLI measurements in CSI measurements of the CSI measurement report, the overhead of reporting CLI measurements is reduced.

[0006] Some implementations of the method and apparatuses described herein may further include to: transmit, to a first UE, a first signaling indicating CLI measurement and reporting configurations and CSI measurement and reporting resource configurations; transmit, to a second UE, a second signaling indicating an uplink transmission configuration that includes at least configuration of one or more muted uplink resources at the second UE that are colliding with one or more measurement resources at the first UE; and receive, from the first UE, a third signaling indicating one or more CSI measurement reports and one or more CLI measurement reports, wherein at least one of the CLI measurements is embedded in CSI measurements of the CSI measurement report.

[0007] In some implementations of the method and apparatuses described herein, the one or more muted uplink resources at the second UE are colliding with a CSI measurement resource at the first UE. Additionally or alternatively, the one or more muted uplink resources at the second UE are colliding with a CLI measurement resource at the first UE. Additionally or alternatively, each CSI measurement and reporting configuration is associated with a subband of a downlink bandwidth part. Additionally or alternatively, each CLI measurement and reporting configuration is associated with a subband of a downlink bandwidth part. Additionally or alternatively, a first CSI measurement of one measurement occasion is indicated as a reference and a second CSI measurement of another measurement occasion is reported as a differential measurement to the first CSI measurement. Additionally or alternatively, a first CLI measurement of one measurement occasion is indicated as a reference and a second CLI measurement of another measurement occasion is reported as a differential measurement to the first CLI measurement. Additionally or alternatively, the CLI measurements include at least one of sounding reference signal reference signal received power (SRS-RSRP), cross-link interference received signal strength indicator (CLL RSSI), or cross-link interference signal-to-interference-plus-noise ratio (CLLSINR).

[0008] Some implementations of the method and apparatuses described herein may further include to: receive, from a network entity, a first signaling indicating an uplink transmission configuration that includes at least configuration of one or more muted uplink resources at the apparatus that are colliding with one or more measurement resources at a UE; and transmit, to the network entity, a second signaling indicating an uplink transmission in accordance with the uplink transmission configuration.

[0009] In some implementations of the method and apparatuses described herein, the one or more muted uplink resources at the apparatus are colliding with a CSI measurement resource at the UE. Additionally or alternatively, the one or more muted uplink resources at the apparatus are colliding with a CLI measurement resource at the UE.

[0010] Some implementations of the method and apparatuses described herein may further include to: receive, from a network entity, a first signaling indicating CLI measurement and reporting configurations and CSI measurement and reporting resource configurations; and transmit, to the network entity, a second signaling indicating one or more CSI measurement reports and one or more CLI measurement reports, wherein at least one of the CLI measurements is embedded in CSI measurements of the CSI measurement report.

[0011] In some implementations of the method and apparatuses described herein, a CSI measurement resource at the apparatus is colliding with one or more muted uplink resources at a UE. Additionally or alternatively, a CLI measurement resource at the apparatus is colliding with one or more muted uplink resources at a UE. Additionally or alternatively, each CSI measurement and reporting configuration is associated with a subband of a downlink bandwidth part. Additionally or alternatively, each CLI measurement and reporting configuration is associated with a subband of a downlink bandwidth part. Additionally or alternatively, a first CSI measurement of one measurement occasion is indicated as a reference and a second CSI measurement of another measurement occasion is reported as a differential measurement to the first CSI measurement. Additionally or alternatively, a first CLI measurement of one measurement occasion is indicated as a reference and a second CLI measurement of another measurement occasion is reported as a differential measurement to the first CLI measurement. Additionally or alternatively, the CLI measurements include at least one of SRS-RSRP, CLI-RSSI, or CLLSINR.

BRIEF DESCRIPTION OF THE DRAWINGS

[0012] FIG. 1 illustrates an example of a wireless communications system that supports embedding cross-link interference measurements in channel state information measurements in accordance with aspects of the present disclosure.

[0013] FIG. 2 illustrates an example of an information element that supports embedding crosslink interference measurements in channel state information measurements in accordance with aspects of the present disclosure.

[0014] FIG. 3 illustrates an example of an information element that supports embedding crosslink interference measurements in channel state information measurements in accordance with aspects of the present disclosure.

[0015] FIG. 4 illustrates an example signaling diagram that supports embedding cross-link interference measurements in channel state information measurements in accordance with aspects of the present disclosure.

[0016] FIG. 5 illustrates an example of CSI measurements configuration at a victim UE and corresponding CLI transmission of an aggressor UE that supports embedding cross-link interference measurements in channel state information measurements in accordance with aspects of the present disclosure.

[0017] FIG. 6 illustrates an example of using one or both of one or more CSI measurements or one or more CLI measurements to interpolate, extrapolate, or predict the CLI measurements on some SBs or symbols/slots that supports embedding cross-link interference measurements in channel state information measurements in accordance with aspects of the present disclosure.

[0018] FIGs. 7 and 8 illustrate examples of block diagrams of devices that support embedding cross-link interference measurements in channel state information measurements in accordance with aspects of the present disclosure.

[0019] FIGs. 9 through 15 illustrate flowcharts of methods that support embedding cross-link interference measurements in channel state information measurements in accordance with aspects of the present disclosure.

DETAILED DESCRIPTION

[0020] UE-UE CLI refers to the interference experienced by a victim UE on its downlink reception due to an uplink transmission of one or more of nearby aggressor UEs. To facilitate the UE-UE CLI mitigation or avoidance, the network may configure a victim UE (e.g., an RRC CONNECTED victim UE) to perform CLI measurements and report them in accordance with the measurement configuration. A CLI measurement and reporting framework can be specified where each victim UE can be configured with up to 32 CLI-RSRP and 64 CLI-RSSI measurement resources. One solution is a CLI framework based on layer 3 (L3)-filtered periodical or event triggered reports, and therefore has limited flexibility and large latency.

[0021] In some situations, the serving base station may require faster CLI measurements reporting to dynamically adjust the scheduled UE transmission and the reception strategies for UE- UE CLI mitigation or avoidance. Layer 1 (Ll)/Layer 2 (L2) based UE-to-UE CLI measurement and reporting may be used to reduce the reporting latency compared to an L3 -based reporting framework. However, L1/L2 based UE-to-UE CLI reporting may increase the CLI reporting overhead, especially if the number of CLI measurements is large. The techniques discussed herein provide a CLI measurement and reporting framework that reduces the CLI measurement reporting overhead and latency.

[0022] The techniques discussed herein allow a network entity to locally derive the CLI measurements of a victim UE from the CSI measurements and reports received from the victim UE. The network entity may configure a victim UE with CSI-based measurement resources, where some resources are configured to be colliding with uplink transmissions (e.g., CLI transmissions) at one or more aggressor UEs, while some other resources are configured to be colliding with blanked (or muted) resources at one or more aggressor UEs. The serving network node may use the CSI reports from the victim UE to derive the CLI-based measurements from one or more of aggressor UEs, e.g., as the difference between two or more of CSI-based measurement resources sets or using any of at least one CLI interpolation, extrapolation, or CLI prediction technique. Thus, CLI measurements are effectively embedded in CSI measurements of the CSI measurement report. The network entity may use the locally derived CLI-based measurements when determining the victim UE transmission and the reception strategies for inter-UE CLI mitigation or avoidance.

[0023] By embedding one or more CLI measurements in CSI measurements of the CSI measurement report, separate CLI measurement resources need not be used thereby reducing the overhead (e.g., the number of bits transmitted) of reporting CLI measurements. Additionally, a CSI measurement at one occasion may be used as a reference value and the CSI measurement at another occasion may be a differential measurement relative to the reference value. This further reduces overhead (e.g., the number of bits transmitted) because the differential measurement may be represented using fewer bits than the full CSI measurement.

[0024] Aspects of the present disclosure are described in the context of a wireless communications system. Aspects of the present disclosure are further illustrated and described with reference to device diagrams and flowcharts.

[0025] FIG. 1 illustrates an example of a wireless communications system 100 that supports embedding cross-link interference measurements in channel state information measurements in accordance with aspects of the present disclosure. The wireless communications system 100 may include one or more network entities 102, one or more UEs 104, a core network 106, and a packet data network 108. The wireless communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE- Advanced (LTE-A) network. In some other implementations, the wireless communications system 100 may be a 5G network, such as an NR network. In other implementations, the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20. The wireless communications system 100 may support radio access technologies beyond 5G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA), etc.

[0026] The one or more network entities 102 may be dispersed throughout a geographic region to form the wireless communications system 100. One or more of the network entities 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a radio access network (RAN), a base transceiver station, an access point, a NodeB, an eNodeB (eNB), a next-generation NodeB (gNB), or other suitable terminology. A network entity 102 and a UE 104 may communicate via a communication link 110, which may be a wireless or wired connection. For example, a network entity 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.

[0027] A network entity 102 may provide a geographic coverage area 112 for which the network entity 102 may support services (e.g., voice, video, packet data, messaging, broadcast, etc.) for one or more UEs 104 within the geographic coverage area 112. For example, a network entity 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or multiple radio access technologies. In some implementations, a network entity 102 may be moveable, for example, a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but the different geographic coverage areas 112 may be associated with different network entities 102. Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0028] The one or more UEs 104 may be dispersed throughout a geographic region of the wireless communications system 100. A UE 104 may include or may be referred to as a mobile device, a wireless device, a remote device, a remote unit, a handheld device, or a subscriber device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an Internet-of-Things (loT) device, an Internet- of-Everything (loE) device, or machine-type communication (MTC) device, among other examples. In some implementations, a UE 104 may be stationary in the wireless communications system 100. In some other implementations, a UE 104 may be mobile in the wireless communications system 100.

[0029] The one or more UEs 104 may be devices in different forms or having different capabilities. Some examples of UEs 104 are illustrated in FIG. 1. A UE 104 may be capable of communicating with various types of devices, such as the network entities 102, other UEs 104, or network equipment (e.g., the core network 106, the packet data network 108, a relay device, an integrated access and backhaul (IAB) node, or another network equipment), as shown in FIG. 1. Additionally, or alternatively, a UE 104 may support communication with other network entities 102 or UEs 104, which may act as relays in the wireless communications system 100.

[0030] A UE 104 may also be able to support wireless communication directly with other UEs 104 over a communication link 114. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link 114 may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.

[0031] A network entity 102 may support communications with the core network 106, or with another network entity 102, or both. For example, a network entity 102 may interface with the core network 106 through one or more backhaul links 116 (e.g., via an SI, N2, N6, or another network interface). The network entities 102 may communicate with each other over the backhaul links 116 (e.g., via an X2, Xn, or another network interface). In some implementations, the network entities 102 may communicate with each other directly (e.g., between the network entities 102). In some other implementations, the network entities 102 may communicate with each other or indirectly (e.g., via the core network 106). In some implementations, one or more network entities 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC). An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs). [0032] In some implementations, a network entity 102 may be configured in a disaggregated architecture, which may be configured to utilize a protocol stack physically or logically distributed among two or more network entities 102, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, a network entity 102 may include one or more of a central unit (CU), a distributed unit (DU), a radio unit (RU), a RAN Intelligent Controller (RIC) (e.g., a Near-Real Time RIC (Near-RT RIC), a Non-Real Time RIC (Non-RT RIC)), a Service Management and Orchestration (SMO) system, or any combination thereof.

[0033] An RU may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmission reception point (TRP). One or more components of the network entities 102 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 102 may be located in distributed locations (e.g., separate physical locations). In some implementations, one or more network entities 102 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU), a virtual DU (VDU), a virtual RU (VRU)).

[0034] Split of functionality between a CU, a DU, and an RU may be flexible and may support different functionalities depending upon which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combinations thereof) are performed at a CU, a DU, or an RU. For example, a functional split of a protocol stack may be employed between a CU and a DU such that the CU may support one or more layers of the protocol stack and the DU may support one or more different layers of the protocol stack. In some implementations, the CU may host upper protocol layer (e.g., a layer 3 (L3), a layer 2 (L2)) functionality and signaling (e.g., Radio Resource Control (RRC), service data adaption protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU may be connected to one or more DUs or RUs, and the one or more DUs or RUs may host lower protocol layers, such as a layer 1 (LI) (e.g., physical (PHY) layer) or an L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU. [0035] Additionally, or alternatively, a functional split of the protocol stack may be employed between a DU and an RU such that the DU may support one or more layers of the protocol stack and the RU may support one or more different layers of the protocol stack. The DU may support one or multiple different cells (e.g., via one or more RUs). In some implementations, a functional split between a CU and a DU, or between a DU and an RU may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU, a DU, or an RU, while other functions of the protocol layer are performed by a different one of the CU, the DU, or the RU).

[0036] A CU may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions. A CU may be connected to one or more DUs via a midhaul communication link (e.g., Fl, Fl-c, Fl-u), and a DU may be connected to one or more RUs via a fronthaul communication link (e.g., open fronthaul (FH) interface). In some implementations, a midhaul communication link or a fronthaul communication link may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities 102 that are in communication via such communication links.

[0037] The core network 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The core network 106 may be an evolved packet core (EPC), or a 5G core (5GC), which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management functions (AMF)) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P- GW), a user plane function (UPF)), or a location management function (LMF), which is a control plane entity that manages location services. In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc.) for the one or more UEs 104 served by the one or more network entities 102 associated with the core network 106.

[0038] The core network 106 may communicate with the packet data network 108 over one or more backhaul links 116 (e.g., via an SI, N2, N6, or another network interface). The packet data network 108 may include an application server 118. In some implementations, one or more UEs 104 may communicate with the application server 118. A UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the core network 106 via a network entity 102. The core network 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server 118 using the established session (e.g., the established PDU session). The PDU session may be an example of a logical connection between the UE 104 and the core network 106 (e.g., one or more network functions of the core network 106).

[0039] In the wireless communications system 100, the network entities 102 and the UEs 104 may use resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers) to perform various operations (e.g., wireless communications). In some implementations, the network entities 102 and the UEs 104 may support different resource structures. For example, the network entities 102 and the UEs 104 may support different frame structures. In some implementations, such as in 4G, the network entities 102 and the UEs 104 may support a single frame structure. In some other implementations, such as in 5G and among other suitable radio access technologies, the network entities 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures). The network entities 102 and the UEs 104 may support various frame structures based on one or more numerologies.

[0040] One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., /r=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. The first numerology (e.g., /r=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., /r=l) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., /r=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., /r=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., /r=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0041] A time interval of a resource (e.g., a communication resource) may be organized according to frames (also referred to as radio frames). Each frame may have a duration, for example, a 10 millisecond (ms) duration. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.

[0042] Additionally or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may include a number (e.g., quantity) of slots. Each slot may include a number (e.g., quantity) of symbols (e.g., orthogonal frequency division multiplexing (OFDM) symbols). In some implementations, the number (e.g., quantity) of slots for a subframe may depend on a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing), a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g., /r=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

[0043] In the wireless communications system 100, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR4 (52.6 GHz - 114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), and FR5 (114.25 GHz - 300 GHz). In some implementations, the network entities 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by the network entities 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data). In some implementations, FR2 may be used by the network entities 102 and the UEs 104, among other equipment or devices for short- range, high data rate capabilities.

[0044] FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies). For example, FR1 may be associated with a first numerology (e.g., /r=0), which includes 15 kHz subcarrier spacing; a second numerology (e.g., /r=l), which includes 30 kHz subcarrier spacing; and a third numerology (e.g., /r=2), which includes 60 kHz subcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies). For example, FR2 may be associated with a third numerology (e.g., /r=2), which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., /r=3), which includes 120 kHz subcarrier spacing.

[0045] In one or more implementations, a network entity 102 transmits CLI and CSI measurement and reporting configurations 120 to a UE 122 (which may be a UE 104), also referred to as a victim UE. The UE 122 includes a CLI and CSI measurement reporting system 124 that performs CLI and CSI measurements at the UE 122. The network entity 102 also transmits an uplink transmission configuration 126 to a UE 128 (which may be another UE 104), also referred to as an aggressor UE. The uplink transmission configuration 126 configures the UE 128 so that one or more muted uplink resources at the UE 128 are colliding with one or more measurement resources at the UE 122. The uplink transmission configuration 126 may also configures the UE 128 so that one or more transmission resources at the UE 128 are colliding with one or more measurement resources at the UE 122. The network entity 102 receives CLI and CSI measurement reports 130 from the UE 122, with at least one of the CLI measurements being embedded in CSI measurements of the CSI measurement report. The network entity 102 may use the embedded CLI measurements when determining the UE 122 transmission and the reception strategies for inter-UE CLI mitigation or avoidance.

[0046] Communication between devices discussed herein, such as between UEs 104 and network entities 102, is performed using any of a variety of different signaling. For example, such signaling can be any of various messages, requests, or responses, such as triggering messages, configuration messages, and so forth. By way of another example, such signaling can be any of various signaling mediums or protocols over which messages are conveyed, such as any combination of radio resource control (RRC), downlink control information (DCI), uplink control information (UCI), sidelink control information (SCI), medium access control element (MAC-CE), sidelink positioning protocol (SLPP), PC5 radio resource control (PC5-RRC) and so forth.

[0047] In one or more implementations, L1/L2 based UE-to-UE CLI measurement and reporting, including for UE-to-UE co-channel CLI handling, is taken into consideration. This may include accounting for UE processing/reporting delay. This may also include the mechanism of L1/L2 based CLI measurement and reporting and the benefits of L1/L2 based CLI measurement and reporting compared with existing L3 CLI/CSI measurement and report. This may also include accounting for information exchange delay between network entities (e.g., base stations) if applicable.

[0048] In one or more implementations, L1/L2 CLI resource configuration and reporting is taken into consideration. This may include, for the purpose of UE-to-UE CLI mitigation, considering the following potential enhancements: for L1/L2 UE-to-UE CLI reporting, periodic, semi-persistent, aperiodic reporting, event triggered reporting; for L1/L2 UE-to-UE CLI measurement, periodic, semi-persistent, or aperiodic measurement resource.

[0049] In one or more implementations, for UE-to-UE component-channel CLI measurement, a baseline of reusing existing channel(s)/signal(s)/measurement_resource(s) is taken into consideration. For example, SRS resources defined in Release- 16 for sounding reference signal reference signal received power (SRS-RSRP) measurement, CLI-RSSI resources defined in Release- 16 for CLI-RSSI measurement are taken into consideration. Potential enhancements are also taken into consideration.

[0050] A CLI framework (e.g., an L3 -based CLI framework) may use an information element (IE) MeasObjectCLI that specifies information applicable for SRS-RSRP measurements and/or CLI-RSSI measurements.

[0051] FIG. 2 illustrates an example 200 of an information element that supports embedding cross-link interference measurements in channel state information measurements in accordance with aspects of the present disclosure. The example 200 illustrates a MeasObjectCLI IE.

[0052] The following fields are included in CLI-ResourceConfig field descriptions.

[0053] A srs-ResourceConfig field indicates SRS resources to be used for CLI measurements.

[0054] An rssi-ResourceConfig field indicates CLI-RSSI resources to be used for CLI measurements.

[0055] The MeasObjectCLI field descriptions include a cli-ResourceConfig field that indicates

SRS and/or CLI-RSSI resource configuration for CLI measurement.

The following fields are included in SRS-ResourceConfigCLI field descriptions.

[0056] A refBWP field indicates a downlink (DL) bandwidth part (BWP) id that is used to derive the reference point of the SRS resource. [0057] A rejServCelllndex field indicates the index of the reference serving cell that the rejBWP belongs to. If this field is absent, the reference serving cell is PCell.

[0058] A srs-SCS field indicates subcarrier spacing for SRS. In one or more implementations the values 15, 30 kHz or 60 kHz (FR1), and 60 or 120 kHz (FR2) are applicable.

The following fields are included in RSSI-ResourceConfigCLI field descriptions.

[0059] An nrojPRBs field indicates an allowed size of the measurement bandwidth (BANDWIDTH). In one or more implementations multiples of 4 are allowed. In one or more implementations, the smallest configurable number is a minimum of 4 and the width of the active DL BWP. If the configured value is larger than the width of the active DL BWP, the UE shall assume that the actual CLI-RSSI resource bandwidth is within the active DL BWP.

[0060] An nrojSymbols field indicates that within a slot that is configured for CLI-RSSI measurement, the UE measures the RSSI from startPosition to startPosition + nrojSymbols - 1. The configured CLI-RSSI resource does not exceed the slot boundary of the reference subcarrier spacing (SCS). If the SCS of configured DL BWP(s) is larger than the reference SCS, network configures startPosition and nrojSymbols such that the configured CLI-RSSI resource is not to exceed the slot boundary corresponding to the configured BWP SCS. If the reference SCS is larger than SCS of configured DL BWP(s), network ensures startPosition and nrojSymbols are integer multiple of reference SCS divided by configured BWP SCS.

[0061] An rejServCelllndex field indicates the index of the reference serving cell. Frequency reference point of the RSSI resource is subcarrier 0 of CRB0 of the reference serving cell. If this field is absent, the reference serving cell is PCell.

[0062] An rssi-PeriodicityAndOjjset field indicates periodicity and slot offset for this CLI-RSSI resource. Values are in "number of slots". Value sll corresponds to a periodicity of 1 slot, value sl2 corresponds to a periodicity of 2 slots, and so on. For each periodicity the corresponding offset is given in number of slots.

[0063] An rssi-SCS field indicates a reference subcarrier spacing for CLI-RSSI measurement. In one or more implementations, the values 15, 30 kHz or 60 kHz (FR1), and 60 or 120 kHz (FR2) are applicable. UE performs CLI-RSSI measurement with the SCS of the active bandwidth part within the configured CLI-RSSI resource in the active BWP regardless of the reference SCS of the measurement resource.

[0064] A startPosition field indicates an OFDM symbol location of the CLI-RSSI resource within a slot.

[0065] A startPRB field indicates a starting physical resource block (PRB) index of the measurement bandwidth. For the case where the reference subcarrier spacing is smaller than subcarrier spacing of active DL BWP(s), network configures startPRB and nrofPRBs are as a multiple of active bandwidth (BW) SCS divided by reference SCS.

[0066] FIG. 3 illustrates an example 300 of an information element that supports embedding cross-link interference measurements in channel state information measurements in accordance with aspects of the present disclosure. The example 300 illustrates a ReportConfigNR IE.

[0067] The following fields are included in CLI-EventTriggerConfig field descriptions.

[0068] An il-Threshold field indicates a threshold value associated to the selected trigger quantity (e.g. SRS-RSRP, CLI-RSSI) to be used in CLI measurement report triggering condition for event il.

[0069] An eventld field indicates a choice of CLI event triggered reporting criteria.

[0070] A maxReportCLI field indicates a max number of CLI measurement resource to include in the measurement report.

[0071] A reportAmount field indicates a number of measurement reports.

[0072] A reportOnLeave field indicates whether or not the UE shall initiate the measurement reporting procedure when the leaving condition is met for a CLI measurement resource in srsTriggeredList or rssiTriggeredList.

[0073] A timeToTrigger field indicates a time during which specific criteria for the event needs to be met in order to trigger a measurement report.

[0074] The following fields are included in CLI-PeriodicalReportConfig field descriptions. [0075] A maxReportCLI field indicates a Max number of CLI measurement resource to include in the measurement report.

[0076] A reportAmount field indicates a number of measurement reports.

[0077] A reportQuantityCLI field indicates the CLI measurement quantities to be included in the measurement report.

[0078] Returning to FIG. 1, the techniques discussed herein allow a network entity 102 to locally derive the CLI measurements of a victim UE from the CSI measurements and reports received from the victim UE. The network entity may configure a victim UE with CSI-based measurement resources, where some resources are configured to be colliding with uplink transmissions (e.g., CLI transmissions) at one or more aggressor UEs, while some other resources are configured to be colliding with blanked (or muted) resources at one or more aggressor UEs. The serving network node may use the CSI reports from the victim UE to derive the CLI-based measurements from one or more of aggressor UEs, e.g., as the difference between two or more of CSI-based measurement resources sets or using any of at least one CLI interpolation, extrapolation, or CLI prediction technique. Thus, CLI measurements are embedded in CSI measurements of the CSI measurement report. The network entity may use the locally derived CLI-based measurements when determining the victim UE transmission and the reception strategies for inter-UE CLI mitigation or avoidance.

[0079] In one or more implementations, a network entity transmits to a victim UE one or both of CLI or CSI measurement and reporting resource configuration and transmits to one or more of aggressor UEs uplink transmission configurations, where the network entity configures one or more blanked (e.g., muted) uplink resources at one or more aggressor UEs that are colliding with one or more CSI measurement resources at the victim UE. For example, the network entity may configure the victim UE to report the following CSI-based measurement information based on CSI-based RS resources (e.g., CSI-RS and/or synchronization signal block (SSB) resources): measurement results per CSI-based RS resource; CSI-based RS resource measurement identifiers. Moreover, the network node may configure the victim UE to report the following CLI-based measurement information based on CLI-based RS resources (e.g., SRS and/or CLI-RSSI resources): measurement results per resource, e.g., per SRS or CLI-RSSI resource; CLI-based resource(s) indexes, e.g., SRS or CLI- RSSI resource(s) indexes.

[0080] In one or more implementations, each CLI/CSI measurement and reporting configuration is associated with a DL subband of a DL BWP. In some other implementations, each CLI/CSI measurement and reporting configuration is associated with a DL BWP.

[0081] In one or more implementations, the victim UE performs CLI measurements (e.g., SRS- RSRP, CLI-RSSI) and CSI measurements (e.g., SINR, RSSI, CQI) based on the CLI and CSI - based RS resources and then transmits the one or more of CLI and CSI reports to the serving network node, e.g., via physical uplink control channel (PUCCH) or physical uplink shared channel (PUSCH) resources. The CLI/CSI reports can be associated with periodic, semi-persistent, or aperiodic CLI/CSI measurement resources and report types. Table 1 shows applicable combinations of CLI/CSI resource and report types.

Table 1 Applicable combination of CLI/CSI resource and report types

[0082] The network entity (e.g., serving network entity) receives the one or more of CLI and/or CSI measurement reports from the victim UE, where the serving network entity may use the measurement reports to locally derive one or more of CLI-based measurements corresponding to one or more of aggressor UEs, e.g., as the difference between two or more of CSLbased measurement resources sets or using a CLI interpolation, extrapolation, and/or prediction technique.

[0083] FIG. 4 illustrates an example signaling diagram 400 that supports embedding cross-link interference measurements in channel state information measurements in accordance with aspects of the present disclosure. The signaling diagram 400 illustrates a network entity 402, a victim UE 404, and an aggressor UE 406. [0084] At 408, the network entity 402 transmits CLI and CSI measurement and reporting configurations to the victim UE 404.

[0085] At 410, the network entity 402 transmits an uplink transmit (Tx) configuration 410 to the aggressor UE 406.

[0086] At 412, the network entity 412 transmits CSI-RSs to the victim UE 404.

[0087] At 414, the aggressor UE 406 sends one or more uplink transmissions, such as one or more of SRS, PUSCH, or PUCCH.

[0088] At 416, the victim UE 404 performs one or both of CLI or CSI measurements.

[0089] At 418, the victim UE 404 transmits one or both of CLI or CSI reports to the network entity 402.

[0090] At 420, the network entity 402 derives one or more CLI measurements using one or more CSI or CLI measurements.

[0091] FIG. 5 illustrates an example 500 of CSI measurements configuration at a victim UE and corresponding CLI transmission of an aggressor UE that supports embedding cross-link interference measurements in channel state information measurements in accordance with aspects of the present disclosure. The example 500 shows example CLI and CSI measurements configuration at a victim UE 502 and the corresponding CLI transmission configuration at an aggressor UE 504, where the DL BWP of the victim UE 502 in slot#2 is divided into three DL subbands (SBs). In the DL SB#0, the victim UE 502 is configured with one CSI measurement resource colliding with uplink transmissions (e.g., SRS, PUSCH or PUCCH) at the aggressor UE 504 and one CLI measurement resource colliding with uplink CLI-RS transmission, e.g., SRS at the aggressor UE 504. Differently, in DL SB#1 and DL SB#2, the victim UE 502 is configured with two CSI measurement resources, where one of them is colliding with uplink transmission (e.g., SRS, DMRS, PUSCH, or PUCCH) while the other is colliding with muted (or blanked) uplink resources at the aggressor UE 504.

[0092] The victim UE 502 performs the CLI and the CSI measurements and then reports the results back to the network entity via the configured reports resources. The network entity may use the measurement reports to derive locally one or more of CLI measurements corresponding to the aggressor UE 504, e.g., at SB#1 as difference between the CSI measurement #1 and #3 or at SB#1 and SB#2 as the difference between the CSI measurement #1 and #2. In some other examples, the network entity may use one or both of one or more CSI measurements or one or more CLI measurements to interpolate, extrapolate, or predict the CLI measurements on some SBs or symbols/slots.

[0093] FIG. 6 illustrates an example 600 of using one or both of one or more CSI measurements or one or more CLI measurements to interpolate, extrapolate, or predict the CLI measurements on some SBs or symbols/slots that supports embedding cross-link interference measurements in channel state information measurements in accordance with aspects of the present disclosure. The network entity uses one or more of derived or reported CLI measurement occasions (one or both of SBs or slots) to derive one or more of missing CLI measurement occasions using a one or more of a CLI interpolation, extrapolation, or prediction technique. In the example 600, CLI measurement occasions (e.g., one or both of SBs or slots) are illustrated at 602 (e.g., at #0, #2, #3, #6, and #9). One or more of CLI interpolation, extrapolation, or prediction is used at 604 resulting in CLI measurement values for missing CLI measurement occasions (e.g., one or both of SBs or slots) as illustrated at 606. These missing CLI measurement occasions are illustrated as #1, #4, #5, #7, #8, and #10.

[0094] In one or more implementations, the victim UE may be configured to report one or both of the CLI or CSI measurements of multiple measurement occasions (e.g., subbands or time resources), where one or both of the CLI or CSI measurement of one of the measurements occasions is indicated as a reference and one or both of the CLI or CSI measurements of the other occasions are reported as one or both of differential CLI or CSI measurements to the indicated reference.

[0095] Accordingly, allowing a serving network node to locally derive the CLI measurements of a victim UE from its CSI measurements and reports, where some CSI resources are configured to be colliding with uplink transmissions (e.g., CLI transmissions) at one or more of aggressor UEs, while some other CSI resources are configured to be colliding with blanked (or muted) resources at one or more of aggressor UEs is described.

[0096] Furthermore, differential CSI and CLI reporting, where one or both of the CLI or CSI measurement of one of the measurements occasions is indicated as a reference and one or both of the CLI or CSI measurements of the other measurements occasions are reported as differential measurements to the indicated reference.

[0097] FIG. 7 illustrates an example of a block diagram 700 of a device 702 that supports embedding cross-link interference measurements in channel state information measurements in accordance with aspects of the present disclosure. The device 702 may be an example of a network entity 102 as described herein. The device 702 may support wireless communication with one or more network entities 102, UEs 104, or any combination thereof. The device 702 may include components for bi-directional communications including components for transmitting and receiving communications, such as a processor 704, a memory 706, a transceiver 708, and an I/O controller 710. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0098] The processor 704, the memory 706, the transceiver 708, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. For example, the processor 704, the memory 706, the transceiver 708, or various combinations or components thereof may support a method for performing one or more of the operations described herein.

[0099] In some implementations, the processor 704, the memory 706, the transceiver 708, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure. In some implementations, the processor 704 and the memory 706 coupled with the processor 704 may be configured to perform one or more of the functions described herein (e.g., executing, by the processor 704, instructions stored in the memory 706).

[0100] For example, the processor 704 may support wireless communication at the device 702 in accordance with examples as disclosed herein. Processor 704 may be configured as or otherwise support to: transmit, to a first UE, a first signaling indicating CLI measurement and reporting configurations and CSI measurement and reporting resource configurations; transmit, to a second UE, a second signaling indicating an uplink transmission configuration that includes at least configuration of one or more muted uplink resources at the second UE that are colliding with one or more measurement resources at the first UE; and receive, from the first UE, a third signaling indicating one or more CSI measurement reports and one or more CLI measurement reports, where at least one of the CLI measurements is embedded in CSI measurements of the CSI measurement report.

[0101] Additionally or alternatively, the processor 704 may be configured to or otherwise support: where the one or more muted uplink resources at the second UE are colliding with a CSI measurement resource at the first UE; where the one or more muted uplink resources at the second UE are colliding with a CLI measurement resource at the first UE where each CSI measurement and reporting configuration is associated with a subband of a downlink bandwidth part where each CLI measurement and reporting configuration is associated with a subband of a downlink bandwidth part where a first CSI measurement of one measurement occasion is indicated as a reference and a second CSI measurement of another measurement occasion is reported as a differential measurement to the first CSI measurement where a first CLI measurement of one measurement occasion is indicated as a reference and a second CLI measurement of another measurement occasion is reported as a differential measurement to the first CLI measurement where the CLI measurements include at least one of sounding reference SRS-RSRP, CLI-RSSI, or CLI-SINR.

[0102] For example, the processor 704 may support wireless communication at the device 702 in accordance with examples as disclosed herein. Processor 704 may be configured as or otherwise support a means for transmitting, to a first UE, a first signaling indicating CLI measurement and reporting configurations and CSI measurement and reporting resource configurations; transmitting, to a second UE, a second signaling indicating an uplink transmission configuration that includes at least configuration of one or more muted uplink resources at the second UE that are colliding with one or more measurement resources at the first UE; and receiving, from the first UE, a third signaling indicating one or more CSI measurement reports and one or more CLI measurement reports, where at least one of the CLI measurements is embedded in CSI measurements of the CSI measurement report. [0103] Additionally or alternatively, the processor 704 may be configured to or otherwise support: where the one or more muted uplink resources at the second UE are colliding with a CSI measurement resource at the first UE where the one or more muted uplink resources at the second UE are colliding with a CLI measurement resource at the first UE where each CSI measurement and reporting configuration is associated with a subband of a downlink bandwidth part where each CLI measurement and reporting configuration is associated with a subband of a downlink bandwidth part where a first CSI measurement of one measurement occasion is indicated as a reference and a second CSI measurement of another measurement occasion is reported as a differential measurement to the first CSI measurement where a first CLI measurement of one measurement occasion is indicated as a reference and a second CLI measurement of another measurement occasion is reported as a differential measurement to the first CLI measurement where the CLI measurements include at least one of sounding reference SRS-RSRP, CLI-RSSI, or CLI-SINR.

[0104] The processor 704 of the device 702, such as a UE 104, may support wireless communication in accordance with examples as disclosed herein. The processor 704 includes at least one controller coupled with at least one memory, and is configured to or operable to cause the processor to receive, from a network entity, a first signaling indicating an uplink transmission configuration that includes at least configuration of one or more muted uplink resources at the apparatus that are colliding with one or more measurement resources at a UE; and transmit, to the network entity, a second signaling indicating an uplink transmission in accordance with the uplink transmission configuration.

[0105] Additionally or alternatively, the 704 includes at least one controller coupled with at least one memory, and is configured to or operable to cause the processor to receive, from a network entity, a first signaling indicating CLI measurement and reporting configurations and CSI measurement and reporting resource configurations; and transmit, to the network entity, a second signaling indicating one or more CSI measurement reports and one or more CLI measurement reports, wherein at least one of the CLI measurements is embedded in CSI measurements of the CSI measurement report.

[0106] The processor 704 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some implementations, the processor 704 may be configured to operate a memory array using a memory controller. In some other implementations, a memory controller may be integrated into the processor 704. The processor 704 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 706) to cause the device 702 to perform various functions of the present disclosure.

[0107] The memory 706 may include random access memory (RAM) and read-only memory (ROM). The memory 706 may store computer-readable, computer-executable code including instructions that, when executed by the processor 704 cause the device 702 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some implementations, the code may not be directly executable by the processor 704 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some implementations, the memory 706 may include, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.

[0108] The I/O controller 710 may manage input and output signals for the device 702. The I/O controller 710 may also manage peripherals not integrated into the device 702. In some implementations, the I/O controller 710 may represent a physical connection or port to an external peripheral. In some implementations, the I/O controller 710 may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS/2®, UNIX®, LINUX®, or another known operating system. In some implementations, the I/O controller 710 may be implemented as part of a processor, such as the processor 704. In some implementations, a user may interact with the device 702 via the I/O controller 710 or via hardware components controlled by the I/O controller 710.

[0109] In some implementations, the device 702 may include a single antenna 712. However, in some other implementations, the device 702 may have more than one antenna 712 (i.e., multiple antennas), including multiple antenna panels or antenna arrays, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 708 may communicate bi-directionally, via the one or more antennas 712, wired, or wireless links as described herein. For example, the transceiver 708 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 708 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 712 for transmission, and to demodulate packets received from the one or more antennas 712.

[0110] FIG. 8 illustrates an example of a block diagram 800 of a device 802 that supports embedding cross-link interference measurements in channel state information measurements in accordance with aspects of the present disclosure. The device 802 may be an example of a UE 104 as described herein. The device 802 may support wireless communication with one or more network entities 102, UEs 104, or any combination thereof. The device 802 may include components for bidirectional communications including components for transmitting and receiving communications, such as a processor 804, a memory 806, a transceiver 808, and an I/O controller 810. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0111] The processor 804, the memory 806, the transceiver 808, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. For example, the processor 804, the memory 806, the transceiver 808, or various combinations or components thereof may support a method for performing one or more of the operations described herein.

[0112] In some implementations, the processor 804, the memory 806, the transceiver 808, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure. In some implementations, the processor 804 and the memory 806 coupled with the processor 804 may be configured to perform one or more of the functions described herein (e.g., executing, by the processor 804, instructions stored in the memory 806).

[0113] For example, the processor 804 may support wireless communication at the device 802 in accordance with examples as disclosed herein. Processor 804 may be configured as or otherwise support to: receive, from a network entity, a first signaling indicating an uplink transmission configuration that includes at least configuration of one or more muted uplink resources at the apparatus that are colliding with one or more measurement resources at a UE; and transmit, to the network entity, a second signaling indicating an uplink transmission in accordance with the uplink transmission configuration.

[0114] Additionally or alternatively, the processor 804 may be configured to or otherwise support: where the one or more muted uplink resources at the apparatus are colliding with a CSI measurement resource at the UE; where the one or more muted uplink resources at the apparatus are colliding with a CLI measurement resource at the UE.

[0115] For example, the processor 804 may support wireless communication at the device 802 in accordance with examples as disclosed herein. Processor 804 may be configured as or otherwise support a means for receiving, from a network entity, a first signaling indicating an uplink transmission configuration that includes at least configuration of one or more muted uplink resources at an apparatus implementing the method that are colliding with one or more measurement resources at a UE; and transmitting, to the network entity, a second signaling indicating an uplink transmission in accordance with the uplink transmission configuration.

[0116] Additionally or alternatively, the processor 804 may be configured to or otherwise support: where the one or more muted uplink resources at the apparatus are colliding with a CSI measurement resource at the UE; where the one or more muted uplink resources at the apparatus are colliding with a CLI measurement resource at the UE.

[0117] For example, the processor 804 may support wireless communication at the device 802 in accordance with examples as disclosed herein. Processor 804 may be configured as or otherwise support to: receive, from a network entity, a first signaling indicating CLI measurement and reporting configurations and CSI measurement and reporting resource configurations; and transmit, to the network entity, a second signaling indicating one or more CSI measurement reports and one or more CLI measurement reports, where at least one of the CLI measurements is embedded in CSI measurements of the CSI measurement report.

[0118] Additionally or alternatively, the processor 804 may be configured to or otherwise support: where a CSI measurement resource at the apparatus is colliding with one or more muted uplink resources at a UE; where a CLI measurement resource at the apparatus is colliding with one or more muted uplink resources at a UE; where each CSI measurement and reporting configuration is associated with a subband of a downlink bandwidth part; where each CLI measurement and reporting configuration is associated with a subband of a downlink bandwidth part; where a first CSI measurement of one measurement occasion is indicated as a reference and a second CSI measurement of another measurement occasion is reported as a differential measurement to the first CSI measurement; where a first CLI measurement of one measurement occasion is indicated as a reference and a second CLI measurement of another measurement occasion is reported as a differential measurement to the first CLI measurement; where the CLI measurements include at least one of sounding reference SRS-RSRP, CLI-RSSI, or CLI-SINR.

[0119] For example, the processor 804 may support wireless communication at the device 802 in accordance with examples as disclosed herein. Processor 804 may be configured as or otherwise support a means for receiving, from a network entity, a first signaling indicating CLI measurement and reporting configurations and CSI measurement and reporting resource configurations; and transmitting, to the network entity, a second signaling indicating one or more CSI measurement reports and one or more CLI measurement reports, where at least one of the CLI measurements is embedded in CSI measurements of the CSI measurement report.

[0120] Additionally or alternatively, the processor 804 may be configured to or otherwise support: where a CSI measurement resource at an apparatus implementing the method is colliding with one or more muted uplink resources at a UE; where a CLI measurement resource at an apparatus implementing the method is colliding with one or more muted uplink resources at a UE; where each CSI measurement and reporting configuration is associated with a subband of a downlink bandwidth part; where each CLI measurement and reporting configuration is associated with a subband of a downlink bandwidth part; where a first CSI measurement of one measurement occasion is indicated as a reference and a second CSI measurement of another measurement occasion is reported as a differential measurement to the first CSI measurement; where a first CLI measurement of one measurement occasion is indicated as a reference and a second CLI measurement of another measurement occasion is reported as a differential measurement to the first CLI measurement; where the CLI measurements include at least one of sounding reference SRS- RSRP, CLI-RSSI, or CLI-SINR. [0121] The processor 804 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some implementations, the processor 804 may be configured to operate a memory array using a memory controller. In some other implementations, a memory controller may be integrated into the processor 804. The processor 804 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 806) to cause the device 802 to perform various functions of the present disclosure.

[0122] The memory 806 may include random access memory (RAM) and read-only memory (ROM). The memory 806 may store computer-readable, computer-executable code including instructions that, when executed by the processor 804 cause the device 802 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some implementations, the code may not be directly executable by the processor 804 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some implementations, the memory 806 may include, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.

[0123] The I/O controller 810 may manage input and output signals for the device 802. The I/O controller 810 may also manage peripherals not integrated into the device 802. In some implementations, the I/O controller 810 may represent a physical connection or port to an external peripheral. In some implementations, the I/O controller 810 may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS/2®, UNIX®, LINUX®, or another known operating system. In some implementations, the I/O controller 810 may be implemented as part of a processor, such as the processor 804. In some implementations, a user may interact with the device 802 via the I/O controller 810 or via hardware components controlled by the I/O controller 810.

[0124] In some implementations, the device 802 may include a single antenna 812. However, in some other implementations, the device 802 may have more than one antenna 812 (i.e., multiple antennas), including multiple antenna panels or antenna arrays, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 808 may communicate bi-directionally, via the one or more antennas 812, wired, or wireless links as described herein. For example, the transceiver 808 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 808 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 812 for transmission, and to demodulate packets received from the one or more antennas 812.

[0125] FIG. 9 illustrates a flowchart of a method 900 that supports embedding cross-link interference measurements in channel state information measurements in accordance with aspects of the present disclosure. The operations of the method 900 may be implemented by a device or its components as described herein. For example, the operations of the method 900 may be performed by a network entity 102 as described with reference to FIGs. 1 through 8. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.

[0126] At 905, the method may include transmitting, to a first UE, a first signaling indicating CLI measurement and reporting configurations and CSI measurement and reporting resource configurations. The operations of 905 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 905 may be performed by a device as described with reference to FIG. 1.

[0127] At 910, the method may include transmitting, to a second UE, a second signaling indicating an uplink transmission configuration that includes at least configuration of one or more muted uplink resources at the second UE that are colliding with one or more measurement resources at the first UE. The operations of 910 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 910 may be performed by a device as described with reference to FIG. 1.

[0128] At 915, the method may include receiving, from the first UE, a third signaling indicating one or more CSI measurement reports and one or more CLI measurement reports, wherein at least one of the CLI measurements is embedded in CSI measurements of the CSI measurement report. The operations of 915 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 915 may be performed by a device as described with reference to FIG. 1.

[0129] FIG. 10 illustrates a flowchart of a method 1000 that supports embedding cross-link interference measurements in channel state information measurements in accordance with aspects of the present disclosure. The operations of the method 1000 may be implemented by a device or its components as described herein. For example, the operations of the method 1000 may be performed by a network entity 102 as described with reference to FIGs. 1 through 8. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.

[0130] At 1005, the method may include a first CSI measurement of one measurement occasion is indicated as a reference and a second CSI measurement of another measurement occasion is reported as a differential measurement to the first CSI measurement. The operations of 1005 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1005 may be performed by a device as described with reference to FIG. 1.

[0131] FIG. 11 illustrates a flowchart of a method 1100 that supports embedding cross-link interference measurements in channel state information measurements in accordance with aspects of the present disclosure. The operations of the method 1100 may be implemented by a device or its components as described herein. For example, the operations of the method 1100 may be performed by a network entity 102 as described with reference to FIGs. 1 through 8. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.

[0132] At 1105, the method may include a first CLI measurement of one measurement occasion is indicated as a reference and a second CLI measurement of another measurement occasion is reported as a differential measurement to the first CLI measurement. The operations of 1105 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1105 may be performed by a device as described with reference to FIG. 1. [0133] FIG. 12 illustrates a flowchart of a method 1200 that supports embedding cross-link interference measurements in channel state information measurements in accordance with aspects of the present disclosure. The operations of the method 1200 may be implemented by a device or its components as described herein. For example, the operations of the method 1200 may be performed by a UE 104 as described with reference to FIGs. 1 through 8. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.

[0134] At 1205, the method may include receiving, from a network entity, a first signaling indicating an uplink transmission configuration that includes at least configuration of one or more muted uplink resources at an apparatus implementing the method that are colliding with one or more measurement resources at a UE. The operations of 1205 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1205 may be performed by a device as described with reference to FIG. 1.

[0135] At 1210, the method may include transmitting, to the network entity, a second signaling indicating an uplink transmission in accordance with the uplink transmission configuration. The operations of 1210 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1210 may be performed by a device as described with reference to FIG. 1.

[0136] FIG. 13 illustrates a flowchart of a method 1300 that supports embedding cross-link interference measurements in channel state information measurements in accordance with aspects of the present disclosure. The operations of the method 1300 may be implemented by a device or its components as described herein. For example, the operations of the method 1300 may be performed by a UE 104 as described with reference to FIGs. 1 through 8. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.

[0137] At 1305, the method may include the one or more muted uplink resources at the apparatus are colliding with a CSI measurement resource at the UE. The operations of 1305 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1305 may be performed by a device as described with reference to FIG. 1.

[0138] FIG. 14 illustrates a flowchart of a method 1400 that supports embedding cross-link interference measurements in channel state information measurements in accordance with aspects of the present disclosure. The operations of the method 1400 may be implemented by a device or its components as described herein. For example, the operations of the method 1400 may be performed by a UE 104 as described with reference to FIGs. 1 through 8. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.

[0139] At 1405, the method may include the one or more muted uplink resources at the apparatus are colliding with a CLI measurement resource at the UE. The operations of 1405 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1405 may be performed by a device as described with reference to FIG. 1.

[0140] FIG. 15 illustrates a flowchart of a method 1500 that supports embedding cross-link interference measurements in channel state information measurements in accordance with aspects of the present disclosure. The operations of the method 1500 may be implemented by a device or its components as described herein. For example, the operations of the method 1500 may be performed by a UE 104 as described with reference to FIGs. 1 through 8. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.

[0141] At 1505, the method may include receiving, from a network entity, a first signaling indicating CLI measurement and reporting configurations and CSI measurement and reporting resource configurations. The operations of 1505 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1505 may be performed by a device as described with reference to FIG. 1.

[0142] At 1510, the method may include transmitting, to the network entity, a second signaling indicating one or more CSI measurement reports and one or more CLI measurement reports, wherein at least one of the CLI measurements is embedded in CSI measurements of the CSI measurement report. The operations of 1510 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1510 may be performed by a device as described with reference to FIG. 1.

[0143] FIG. 16 illustrates a flowchart of a method 1600 that supports embedding cross-link interference measurements in channel state information measurements in accordance with aspects of the present disclosure. The operations of the method 1600 may be implemented by a device or its components as described herein. For example, the operations of the method 1600 may be performed by a UE 104 as described with reference to FIGs. 1 through 8. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.

[0144] At 1605, the method may include a CSI measurement resource at an apparatus implementing the method is colliding with one or more muted uplink resources at a UE. The operations of 1605 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1605 may be performed by a device as described with reference to FIG. 1.

[0145] It should be noted that the methods described herein describes possible implementations, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible. Further, aspects from two or more of the methods may be combined.

[0146] The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed with a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. [0147] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.

[0148] Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.

[0149] Any connection may be properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media. [0150] As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of’ or “one or more of’ or “one or both of’) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Similarly, a list of at least one of A; B; or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. Further, as used herein, including in the claims, a “set” may include one or more elements.

[0151] The terms “transmitting,” “receiving,” or “communicating,” when referring to a network entity, may refer to any portion of a network entity (e.g., a base station, a CU, a DU, a RU) of a RAN communicating with another device (e.g., directly or via one or more other network entities).

[0152] The description set forth herein, in connection with the appended drawings, describes example configurations and does not represent all the examples that may be implemented or that are within the scope of the claims. The term “example” used herein means “serving as an example, instance, or illustration,” and not “preferred” or “advantageous over other examples.” The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described example.

[0153] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

Claims

CLAIMS What is claimed is:

1. An apparatus for wireless communication, comprising: a processor; and a memory coupled with the processor, the processor configured to cause the apparatus to: transmit, to a first user equipment (UE), a first signaling indicating cross-link interference (CLI) measurement and reporting configurations and channel state information (CSI) measurement and reporting resource configurations; transmit, to a second UE, a second signaling indicating an uplink transmission configuration that includes at least configuration of one or more muted uplink resources at the second UE that are colliding with one or more measurement resources at the first UE; and receive, from the first UE, a third signaling indicating one or more CSI measurement reports and one or more CLI measurement reports, wherein at least one of the CLI measurements is embedded in CSI measurements of the CSI measurement report.

2. The apparatus of claim 1, wherein the one or more muted uplink resources at the second UE are colliding with a CSI measurement resource at the first UE.

3. The apparatus of claim 1, wherein the one or more muted uplink resources at the second UE are colliding with a CLI measurement resource at the first UE.

4. The apparatus of claim 1, wherein each CSI measurement and reporting configuration is associated with a subband of a downlink bandwidth part.

5. The apparatus of claim 1, wherein each CLI measurement and reporting configuration is associated with a subband of a downlink bandwidth part.

6. The apparatus of claim 1, wherein a first CSI measurement of one measurement occasion is indicated as a reference and a second CSI measurement of another measurement occasion is reported as a differential measurement to the first CSI measurement.

7. The apparatus of claim 1, wherein a first CLI measurement of one measurement occasion is indicated as a reference and a second CLI measurement of another measurement occasion is reported as a differential measurement to the first CLI measurement.

8. The apparatus of claim 1, wherein the CLI measurements include at least one of sounding reference signal reference signal received power (SRS-RSRP), cross-link interference received signal strength indicator (CLLRSSI), or cross-link interference signal-to-interference-plus-noise ratio (CLI-SINR).

9. An apparatus for wireless communication, comprising: a processor; and a memory coupled with the processor, the processor configured to cause the apparatus to: receive, from a network entity, a first signaling indicating an uplink transmission configuration that includes at least configuration of one or more muted uplink resources at the apparatus that are colliding with one or more measurement resources at a user equipment (UE); and transmit, to the network entity, a second signaling indicating an uplink transmission in accordance with the uplink transmission configuration.

10. The apparatus of claim 9, wherein the one or more muted uplink resources at the apparatus are colliding with a channel state information (CSI) measurement resource at the UE.

11. The apparatus of claim 9, wherein the one or more muted uplink resources at the apparatus are colliding with a cross-link interference (CLI) measurement resource at the UE.

12. An apparatus for wireless communication, comprising: a processor; and a memory coupled with the processor, the processor configured to cause the apparatus to: receive, from a network entity, a first signaling indicating cross-link interference (CLI) measurement and reporting configurations and channel state information (CSI) measurement and reporting resource configurations; and transmit, to the network entity, a second signaling indicating one or more CSI measurement reports and one or more CLI measurement reports, wherein at least one of the CLI measurements is embedded in CSI measurements of the CSI measurement report.

13. The apparatus of claim 12, wherein a CSI measurement resource at the apparatus is colliding with one or more muted uplink resources at a user equipment (UE).

14. The apparatus of claim 12, wherein a CLI measurement resource at the apparatus is colliding with one or more muted uplink resources at a user equipment (UE).

15. The apparatus of claim 12, wherein each CSI measurement and reporting configuration is associated with a subband of a downlink bandwidth part.

16. The apparatus of claim 12, wherein each CLI measurement and reporting configuration is associated with a subband of a downlink bandwidth part.

17. A processor for wireless communication, comprising: at least one controller coupled with at least one memory and configured to cause the processor to: receive, from a network entity, a first signaling indicating cross-link interference (CLI) measurement and reporting configurations and channel state information (CSI) measurement and reporting resource configurations; and transmit, to the network entity, a second signaling indicating one or more CSI measurement reports and one or more CLI measurement reports, wherein at least one of the CLI measurements is embedded in CSI measurements of the CSI measurement report.

18. The processor of claim 17, wherein a first CSI measurement of one measurement occasion is indicated as a reference and a second CSI measurement of another measurement occasion is reported as a differential measurement to the first CSI measurement.

19. The processor of claim 17, wherein a first CLI measurement of one measurement occasion is indicated as a reference and a second CLI measurement of another measurement occasion is reported as a differential measurement to the first CLI measurement.

20. The processor of claim 17, wherein the CLI measurements include at least one of sounding reference signal reference signal received power (SRS-RSRP), cross-link interference received signal strength indicator (CLLRSSI), or cross-link interference signal-to-interference-plus-noise ratio (CLI-SINR).