Cross-link interference reporting on physical uplink channel

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) can receive a first message indicating a cross-link interference report configuration. The cross-link interference report configuration can be associated with a first rule set for determining an amount of resources for multiplexing cross-link interference reports on a physical uplink channel and a second rule set for multiplexing the cross-link interference reports on the physical uplink channel via the amount of resources. The UE can transmit the cross-link interference report on the physical uplink channel according to a first set of rules and a second set of rules. The cross-link interference report can indicate one or more cross-link interference measurements performed by the UE.

Description

[0001] Cross-references

[0002] This application claims the benefit of U.S. patent application No. 17 / 732,008, entitled “CROSS-LINK INTERFERENCE REPORTING ON PHYSICAL UPLINK CHANNELS,” filed by IBRAHIM et al. on April 28, 2022, which is assigned to the assignee of this application. Technical Field

[0003] The following relates to wireless communications, including cross-link interference (CLI) reporting on a physical uplink channel. Background Art

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, etc. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems) and fifth generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM).

[0005] A wireless multiple access communication system may include one or more network entities, each of which supports wireless communications for communication devices, which may be referred to as user equipment (UE). In some wireless communication systems, adjacent communication devices may send or receive communications concurrently, which may cause cross-link interference (CLI). Summary of the invention

[0006] The described techniques relate to improved methods, systems, devices, and apparatuses for supporting cross-link interference (CLI) reporting on a physical uplink channel. In general, the described techniques provide for configuring a communication device, such as a user equipment (UE), with one or more rules for performing CLI measurements and reporting. For example, a UE may receive a first message indicating a CLI report configuration. In some examples, the CLI report configuration may be associated with a first rule set for determining an amount of resources for multiplexing CLI reports on a physical uplink channel and a second rule set for multiplexing CLI reports on a physical uplink channel via the amount of resources. In some examples, the UE may send a CLI report on a physical uplink channel according to the first rule set and the second rule set. The CLI report may indicate one or more CLI measurements performed by the UE. Sending a CLI report on a physical uplink channel according to the first rule set and the second rule set may improve CLI reporting, thereby enhancing CLI mitigation techniques performed by the network.

[0007] A method for wireless communication at a UE is described. The method may include receiving a first message indicating a CLI reporting configuration, the CLI reporting configuration being associated with a first rule set for determining an amount of resources for multiplexing CLI reports on a physical uplink channel and a second rule set for multiplexing CLI reports on the physical uplink channel via the amount of resources; and sending a CLI report on the physical uplink channel according to the first rule set and the second rule set, the CLI report indicating one or more CLI measurements performed by the UE.

[0008] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions are executable by the processor to cause the apparatus to receive a first message indicating a CLI report configuration, the CLI report configuration being associated with a first rule set for determining an amount of resources for multiplexing CLI reports on a physical uplink channel and a second rule set for multiplexing CLI reports on the physical uplink channel via the amount of resources; and to send a CLI report on the physical uplink channel according to the first rule set and the second rule set, the CLI report indicating one or more CLI measurements performed by the UE.

[0009] Another apparatus for wireless communication at a UE is described. The apparatus may include means for receiving a first message indicating a CLI reporting configuration associated with a first rule set for determining an amount of resources for multiplexing CLI reports on a physical uplink channel and a second rule set for multiplexing CLI reports on the physical uplink channel via the amount of resources; and means for sending a CLI report on the physical uplink channel in accordance with the first rule set and the second rule set, the CLI report indicating one or more CLI measurements performed by the UE.

[0010] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to: receive a first message indicating a CLI report configuration, the CLI report configuration being associated with a first rule set for determining an amount of resources for multiplexing CLI reports on a physical uplink channel and a second rule set for multiplexing CLI reports on the physical uplink channel via the amount of resources; and send a CLI report on the physical uplink channel according to the first rule set and the second rule set, the CLI report indicating one or more CLI measurements performed by the UE.

[0011] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a second message that triggers the UE to report one or more CLI measurements and includes an offset indicator, wherein sending the CLI report may be based on receiving the second message and determining one or more CLI offset values ​​based on the offset indicator, wherein the amount of resources may be based on the one or more CLI offset values.

[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, determining one or more CLI offset values ​​may include operations, features, components, or instructions for determining one or more CLI offset values ​​using an offset indicator and a table comprising multiple sets of CLI offset values.

[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, determining one or more CLI offset values ​​may include operations, features, components, or instructions for calculating one or more CLI offset values ​​using differences from one or more channel state information (CSI) offset values.

[0014] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the CLI reporting configuration includes an indication of a difference value, and calculating the one or more CLI offset values ​​may be based on receiving the first message.

[0015] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, one or more CLI offset values ​​may be different from one or more CSI offset values.

[0016] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: receiving a second message indicating one or more CLI offset values, wherein the amount of resources may be based on the one or more CLI offset values; and receiving a third message triggering the UE to report one or more CLI measurements, wherein the third message may be common to a group of two or more UEs including the UE, and wherein sending the CLI report may be based on receiving the third message.

[0017] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the third message includes an offset indicator, and determining the one or more CLI offset values ​​may be further based on the offset indicator.

[0018] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for multiplexing CLI reports on a physical uplink channel via an amount of resources based on a second rule set, the physical uplink channel comprising a physical uplink shared channel (PUSCH), wherein sending the CLI report may be based on multiplexing.

[0019] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, multiplexing the CLI report may include operations, features, means, or instructions for: multiplexing the CLI report after the CSI report.

[0020] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, multiplexing a CLI report may include operations, features, components, or instructions for multiplexing a first portion of the CLI report after a first portion of the CSI report and multiplexing a second portion of the CLI report after a second portion of the CSI report.

[0021] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: receiving a second message instructing the UE to multiplex the CLI report with the feedback information, and multiplexing the CLI report with the feedback information based on receiving the second message, the physical uplink channel including a physical uplink control channel (PUCCH), wherein sending the CLI report may be based on the multiplexing.

[0022] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: receiving a third message instructing the UE to multiplex the CLI report with the CSI report, wherein multiplexing the CLI report with the feedback information includes multiplexing the CLI report with the feedback information and the CSI report based on receiving the second message and the third message.

[0023] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a CLI report may be multiplexed after a first portion of a CSI report and feedback information.

[0024] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, multiplexing a CLI report with feedback information and a CSI report may include operations, features, components, or instructions for multiplexing the CLI report with feedback information and a CSI report according to an ordering that may be based on respective priorities of the CLI report and the CSI report.

[0025] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, multiplexing a CLI report with feedback information and a CSI report may include operations, features, components, or instructions for multiplexing the feedback information, a first portion of the CSI report, and a first portion of the CLI report, and discarding at least a second portion of the CLI report.

[0026] A method for wireless communication at a network entity is described. The method may include sending a first message indicating a CLI report configuration associated with a first rule set for determining an amount of resources for multiplexing CLI reports on a physical uplink channel and a second rule set for multiplexing CLI reports on the physical uplink channel via the amount of resources; and receiving a CLI report on the physical uplink channel according to the first rule set and the second rule set, the CLI report indicating one or more CLI measurements performed by a UE.

[0027] An apparatus for wireless communication at a network entity is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executed by the processor to cause the apparatus to send a first message indicating a CLI report configuration, the CLI report configuration being associated with a first rule set for determining an amount of resources for multiplexing CLI reports on a physical uplink channel and a second rule set for multiplexing CLI reports on the physical uplink channel via the amount of resources; and receive a CLI report on the physical uplink channel according to the first rule set and the second rule set, the CLI report indicating one or more CLI measurements performed by a UE.

[0028] Another apparatus for wireless communication at a network entity is described. The apparatus may include means for sending a first message indicating a CLI reporting configuration associated with a first rule set for determining an amount of resources for multiplexing CLI reports on a physical uplink channel and a second rule set for multiplexing CLI reports on the physical uplink channel via the amount of resources; and means for receiving a CLI report on the physical uplink channel according to the first rule set and the second rule set, the CLI report indicating one or more CLI measurements performed by a UE.

[0029] A non-transitory computer-readable medium storing code for wireless communication at a network entity is described. The code may include instructions executable by a processor to: send a first message indicating a CLI report configuration, the CLI report configuration being associated with a first rule set for determining an amount of resources for multiplexing CLI reports on a physical uplink channel and a second rule set for multiplexing CLI reports on the physical uplink channel via the amount of resources; and receive a CLI report on the physical uplink channel according to the first rule set and the second rule set, the CLI report indicating one or more CLI measurements performed by a UE.

[0030] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a second message that triggers the UE to report one or more CLI measurements and includes an offset indicator, wherein receiving the CLI report may be based on receiving the second message, and wherein the amount of resources may be based on one or more CLI offset values ​​indicated by the offset indicator.

[0031] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the one or more CLI offset values ​​indicated by the offset indicator correspond to CLI offset values ​​included in the table.

[0032] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, one or more CLI offset values ​​indicated by the offset indicator may be based on a difference from one or more CSI offset values.

[0033] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the CLI report configuration includes an indication of the difference value.

[0034] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, one or more CLI offset values ​​may be different from one or more CSI offset values.

[0035] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: sending a second message indicating one or more CLI offset values, wherein the amount of resources may be based on the one or more CLI offset values; and sending a third message that triggers the UE to report one or more CLI measurements, wherein the third message may be common to a group of two or more UEs including the UE, and wherein receiving the CLI report may be based on the third message.

[0036] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the third message includes an offset indicator, and the one or more CLI offset values ​​may be based on the offset indicator.

[0037] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a CLI report may be multiplexed on a physical uplink channel via an amount of resources after a CSI report and based on a second set of rules.

[0038] In some examples of the methods, devices, and non-transitory computer-readable media described herein, a first portion of a CLI report may be multiplexed on a physical uplink channel via a resource amount after a first portion of a CSI report and based on a second set of rules, and a second portion of a CLI report may be multiplexed on a physical uplink channel via a resource amount after a second portion of a CSI report.

[0039] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a second message instructing the UE to multiplex the CLI report with the feedback information, wherein the CLI report may be multiplexed with the feedback information based on the second message.

[0040] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: sending a third message instructing the UE to multiplex the CLI report with the CSI report, wherein the CLI report can be multiplexed with the feedback information and the CSI report based on the third message.

[0041] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a CLI report may be multiplexed after a first portion of a CSI report and feedback information.

[0042] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a CLI report may be multiplexed with feedback information and a CSI report according to an ordering that may be based on respective priorities of the CLI report and the CSI report.

[0043] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, feedback information, a first portion of a CSI report, and a first portion of a CLI report may be multiplexed on a physical uplink channel, and at least a portion of a second portion of the CLI report may be discarded. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] Figure 1 , Figure 2A , Figure 2B and Figure 2C Each illustrates an example of a wireless communication system supporting cross-link interference (CLI) reporting on a physical uplink channel according to one or more aspects of the present disclosure.

[0045] Figure 3A and Figure 3B Each illustrates an example of a duplex operation scheme supporting CLI reporting on a physical uplink channel according to one or more aspects of the present disclosure.

[0046] Figure 4 An example of resource mapping to support CLI reporting on a physical uplink channel in accordance with one or more aspects of the present disclosure is illustrated.

[0047] Figure 5 An example of a process flow in a system supporting CLI reporting on a physical uplink channel in accordance with one or more aspects of the present disclosure is illustrated.

[0048] Figure 6 and Figure 7 A block diagram of a device supporting CLI reporting on a physical uplink channel according to one or more aspects of the present disclosure is shown.

[0049] Figure 8 A block diagram of a communications manager supporting CLI reporting on a physical uplink channel is shown in accordance with one or more aspects of the present disclosure.

[0050] Fig. 9 A diagram of a system including a device supporting CLI reporting on a physical uplink channel is shown in accordance with one or more aspects of the present disclosure.

[0051] Fig.10 and Fig.11 A block diagram of a device supporting CLI reporting on a physical uplink channel according to one or more aspects of the present disclosure is shown.

[0052] Fig.12 A block diagram of a communications manager supporting CLI reporting on a physical uplink channel is shown in accordance with one or more aspects of the present disclosure.

[0053] Fig.13A diagram of a system including a device supporting CLI reporting on a physical uplink channel is shown in accordance with one or more aspects of the present disclosure.

[0054] Figures 14 to 19 A flow chart illustrating a method of supporting CLI reporting on a physical uplink channel according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0055] In some wireless communication systems, a communication device such as a user equipment (UE) or a network entity may support wireless communication through one or more radio access technologies. Examples of radio access technologies may include fourth generation (4G) systems (such as long term evolution (LTE) systems) and fifth generation (5G) systems (which may be referred to as NR systems). In such cases, the communication device may operate in half-duplex mode or full-duplex mode or a combination thereof. In half-duplex mode, the communication device may send or receive communication during a time period such as a transmit time interval (TTI) that may span one or more time resources (e.g., symbols, microslots, time slots, etc.). In full-duplex mode, the communication device may simultaneously send and receive communication during the time period. That is, the communication received by the communication device may overlap with the communication sent by the communication device in the time domain. For example, the symbol occupied by the received signal may overlap with the symbol occupied by the transmitted signal.

[0056] In some examples, adjacent communication devices (e.g., UE, network entity, etc.) may concurrently perform full-duplex communication or half-duplex time division duplex (TDD) so that the communication received by the first communication device may overlap in time with the communication sent by the second communication device (e.g., adjacent communication device). In such an example, the communication sent by the second communication device may interfere with the communication received at the first communication device. In other words, because a communication device with full-duplex capability can receive signaling while the communication device is transmitting, in some cases, the communication device may be affected by a relatively increased amount of interference from other nearby transmitting devices (e.g., compared to communicating using half-duplex technology). Such interference may be referred to as cross-link interference (CLI) or other similar terms. In some examples, CLI may degrade the wireless communication between the first communication device and the network. Therefore, in order to mitigate the impact of CLI, the network may configure the first communication device to measure and report CLI.

[0057] In some examples, the network may configure the communication device (e.g., UE) to perform CLI reporting via higher layer (e.g., L3, radio resource control (RRC) layer) signaling. To increase the flexibility of CLI reporting, the network may configure the communication device to measure and report CLI, where CLI may be reported via lower layer (e.g., L1, physical (PHY) layer) signaling. For example, the communication device may report CLI via channel state information (CSI) reporting. However, in some examples, including CLI within CSI reporting may limit the reporting of CLI to instances when CSI is also reported.

[0058] Various aspects of the present disclosure generally relate to techniques for CLI reporting on physical uplink channels (e.g., physical uplink shared channel (PUSCH), physical uplink control channel (PUCCH)), and more specifically, to techniques for configuring a communication device with one or more rules for performing CLI reporting on one or more physical uplink channels. For example, to reduce signaling overhead for the communication device, the network may configure the communication device with one or more rules for multiplexing CLI reporting on the physical uplink channel (e.g., as uplink control information separate from CSI reporting). The network may configure the communication device to report CLI on the PUSCH or on the PUCCH.

[0059] For example, the network may configure the communication device with one or more parameters for determining the amount of resources for multiplexing CLI reports on PUSCH. In some examples, the network may indicate the parameters to the communication device via semi-static signaling (e.g., via an RRC message) or dynamic signaling (e.g., via dedicated downlink control information (DCI) or group common DCI), or both. In some examples, the network may use dynamic signaling to trigger the communication device to perform CLI reporting. Additionally or alternatively, the network may configure the communication device with one or more rules for multiplexing CLI reports on PUSCH (e.g., via the determined amount of resources). For example, the network may configure the communication device to determine whether to multiplex the CLI report on PUSCH with the CSI report based on the relative priority of the CLI report and the CSI report.

[0060] Additionally or alternatively, the network may configure the communication device with one or more rules for determining whether to multiplex the CLI report on the PUCCH with other uplink control information, such as downlink feedback information (e.g., hybrid automatic repeat request acknowledgement (HARQ-ACK) information), CSI report, or both. For example, the network may configure the communication device to multiplex the CLI report with the downlink feedback information or CSI report (or both) based on one or more indicators and the relative priority of the CLI report and the CSI report.

[0061] Certain aspects of the subject matter described herein can be implemented to achieve one or more of the following potential advantages. The techniques employed by the described communication device can provide benefits and enhancements to the operation of the communication device, including implementing a configuration of the communication device having one or more rules for performing CLI reporting on a physical uplink channel. In addition, as described herein, techniques for CLI reporting on a physical uplink channel can support higher data rates, spectrum efficiency enhancements, and efficient resource utilization, thereby improving throughput and reliability. Such techniques can therefore result in improved network operation and network efficiency, as well as other benefits.

[0062] Aspects of the disclosure are first described in the context of a wireless communication system. Aspects of the disclosure are also described in the context of an operating scheme, resource mapping, and process flow. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flow diagrams relating to CLI reporting on a physical uplink channel.

[0063] Figure 1 An example of a wireless communication system 100 that supports CLI reporting on a physical uplink channel according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating according to other systems and radio technologies (including future systems and radio technologies not explicitly mentioned herein).

[0064] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may include devices in different forms or with different capabilities. In different examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, etc. In some examples, the network entities 105 and the UE 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entity 105 may support a coverage area 110 (e.g., a geographic coverage area), and the UE 115 and the network entity 105 may establish one or more communication links 125 over the coverage area. The coverage area 110 may be an example of a geographic area over which the network entity 105 and the UE 115 may support signal communications according to one or more radio access technologies (RATs).

[0065] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile, or stationary and mobile at different times. The UEs 115 may be devices in different forms or with different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of communicating with various types of devices (e.g., Figure 1 105 or other UEs 115 or network entities 105 shown in FIG.

[0066] As described herein, a node of the wireless communication system 100 (which may be referred to as a network node or a wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node may be a UE 115. As another example, the node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In yet other aspects of this example, the first node, the second node, and the third node may be different relative to these examples. Similarly, references to UE 115, network entity 105, apparatus, device, computing system, etc. may include disclosure of UE 115, network entity 105, apparatus, device, computing system, etc. as nodes. For example, disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from the second node.

[0067] In some examples, the network entities 105 may communicate with the core network 130, or communicate with each other, or both. For example, the network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3 or other interface protocols). In some examples, the network entities 105 may communicate with each other over the backhaul communication links 120 (e.g., according to X2, Xn or other interface protocols) directly (e.g., directly between the network entities 105) or indirectly (e.g., via the core network 130). In some examples, the network entities 105 may communicate with each other via the midhaul communication link 162 (e.g., according to the midhaul interface protocol) or the fronthaul communication link 168 (e.g., according to the fronthaul interface protocol) or any combination thereof. The backhaul communication link 120, the midhaul communication link 162, or the fronthaul communication link 168 may be or include one or more wired links (e.g., electrical links, optical fiber links), one or more wireless links (e.g., radio links, wireless optical links), etc. or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .

[0068] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a transceiver base station, a radio base station, an NR base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next-generation Node B, or a gigabit Node B (any of which may be referred to as a gNB), a 5G NB, a next-generation eNB (ng-eNB), a home Node B, a home evolved Node B, or other suitable terms). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, stand-alone) base station architecture, which may be configured to utilize a protocol stack physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140).

[0069] In some examples, the network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, 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, the network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, an intelligent radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmission and reception point. One or more components of the network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0070] The functional split between CU 160, DU 165, and RU 170 is flexible and may support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, and RU 170. For example, a functional split of a protocol stack may be employed between CU 160 and DU 165 such that CU 160 may support one or more layers of a protocol stack and DU 165 may support one or more different layers of a protocol stack. In some examples, CU 160 may host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., RRC, service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or 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 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DU 165 and the RU 170, such that the DU 165 may support one or more layers of the protocol stack, and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 may be within the protocol layer (e.g., some functions of the protocol layer may be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by a different one of CU 160, DU 165, or RU 170). CU 160 may be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented based on interfaces (eg, channels) between layers of a protocol stack supported by respective network entities 105 communicating over those communication links.

[0071] In some wireless communication systems (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be controlled in part by one or more CUs 160 associated with a donor network entity 105 (e.g., a donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile termination (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include a collection of independent antennas for relaying communications with the UE 115, or may share the same antenna of the IAB node 104 (e.g., of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.

[0072] In the case where the techniques described herein are applied to the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support CLI reporting on a physical uplink channel as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

[0073] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable term, where a "device" may also be referred to as a unit, a station, a terminal, or a client, etc. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or may be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects such as electrical appliances or vehicles, meters, etc.

[0074] The UE 115 described herein may be able to communicate with various types of devices, such as other UEs 115, which may sometimes act as relays, as well as network entities 105 and network equipment, including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 shown.

[0075] The UE 115 and the network entity 105 may wirelessly communicate with each other via one or more communication links 125 (e.g., access links) on one or more carriers. The term "carrier" may refer to a set of RF spectrum resources having a defined physical layer structure to support the communication link 125. For example, a carrier for the communication link 125 may include a portion of an RF spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communications with the UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used for both frequency division duplex (FDD) and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between a device and any portion (e.g., entity, sub-entity) of the network entity 105. For example, the terms "send," "receive," or "communicate" when referring to the network entity 105 may refer to any portion of a network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of a RAN communicating with another device (e.g., directly or via one or more other network entities 105).

[0076] The signal waveform transmitted over the carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The amount of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), such that the more resource elements a device receives and the higher the order of the modulation scheme, the higher the data rate of the device may be. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers, beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0077] The time interval of the network entity 105 or the UE 115 may be expressed in multiples of a basic time unit, which may be, for example, T s =1 / (Δf max ·N f ) seconds sampling period, where Δf max It can represent the maximum supported subcarrier spacing, and N f The maximum supported discrete Fourier transform (DFT) size may be indicated. Time intervals of the communication resources may be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0078] Each frame may include a plurality of consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix added before each symbol period). In some wireless communication systems 100, the time slot may be further divided into a plurality of micro-time slots including one or more symbols. Excluding the cyclic prefix, each symbol period may contain one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0079] A subframe, a time slot, a mini-time slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., a certain amount of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in a burst of a shortened TTI (sTTI)).

[0080] Physical channels may be multiplexed on a carrier according to various techniques. For example, physical control channels and physical data channels may be multiplexed on a downlink carrier using one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth or a subset of a system bandwidth of a carrier. One or more control regions (e.g., CORESETs) may be configured for a group of UEs 115. For example, one or more UEs in UE 115 may monitor or search a control region to obtain control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to a plurality of UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .

[0081] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and thus provide communication coverage for mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.

[0082] The wireless communication system 100 can be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 can be configured to support ultra-reliable low-latency communication (URLLC). UE 115 can be designed to support ultra-reliable, low-latency or critical functions. Ultra-reliable communication may include private communication or group communication, and may be supported by one or more services (such as push-to-talk, video or data). Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency and ultra-reliable low-latency may be used interchangeably herein.

[0083] In some examples, a UE 115 may be able to communicate directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group that are performing D2D communication may be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), which may support aspects of such D2D communication configured or scheduled by the network entity 105. In some examples, one or more UEs 115 in such a group may be outside of the coverage area 110 of the network entity 105, or may be unable or not configured to receive transmissions from the network entity 105 for other reasons. In some examples, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system, in which each UE 115 transmits to each of the other UEs 115 in the group. In some examples, the network entity 105 may facilitate scheduling of resources for D2D communication. In some other examples, D2D communications may be performed between UEs 115 without involving network entity 105 .

[0084] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity for managing access and mobility (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) and at least one user plane entity for routing packets or interconnecting to an external network (e.g., a serving gateway (S-GW)), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)). The control plane entity may manage non-access layer (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by a network entity 105 (e.g., a base station 140) associated with the core network 130. User IP packets may be transported by user plane entities, which may provide IP address allocation and other functions. The user plane entity may be connected to an IP service 150 for one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0085] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Typically, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength range is about one decimeter to one meter. UHF waves may be blocked or redirected by buildings and environmental features, which may be referred to as clusters, but these waves may be sufficient to penetrate structures so that macro cells provide services to UEs 115 located indoors. Transmission of UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) than transmission using smaller frequencies and longer wavelengths of the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0086] The wireless communication system 100 can utilize licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 can employ license assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band. When operating in an unlicensed RF spectrum band, devices such as network entities 105 and UE 115 can employ carrier sensing for conflict detection and avoidance. In some examples, operations in unlicensed bands can be based on a carrier aggregation configuration (e.g., LAA) combined with component carriers operating in licensed bands. Operations in unlicensed spectrum can include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, and the like.

[0087] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas, which can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of the network entity 105 or UE 115 may be located in one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, the antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may have an antenna array having a set of rows and columns of antenna ports that the network entity 105 can use to support beamforming for communications with the UE 115. Similarly, the UE 115 may have one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.

[0088] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals communicated via antenna elements of an antenna array so that some signals propagating in a particular direction relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals communicated via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of these antenna elements may be defined by a set of beamforming weights associated with a particular direction (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other direction).

[0089] UE 115 and network entity 105 may support retransmission of data to increase the possibility of successfully receiving data. Hybrid automatic repeat request (HARQ) feedback is a technology for increasing the possibility of correctly receiving data through a communication link (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ can improve the throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, a device may support simultaneous slot HARQ feedback, wherein the device may provide HARQ feedback in a specific time slot for data received in a previous symbol in the time slot. In some other examples, the device may provide HARQ feedback in a subsequent time slot or according to some other time interval.

[0090] The wireless communication system 100 may support techniques for configuring a communication device (e.g., UE 115) with one or more rules for performing CLI reporting on a physical uplink channel. For example, UE 115 may receive a first message indicating a CLI reporting configuration. In some examples, the CLI reporting configuration may be associated with a first set of rules for determining an amount of resources for multiplexing CLI reports on a physical uplink channel and a second set of rules for multiplexing CLI reports on a physical uplink channel via an amount of resources. In some examples, UE 115 may send a CLI report on a physical uplink channel according to the first set of rules and the second set of rules. The CLI report may indicate one or more CLI measurements performed by the UE. In some examples, by sending a CLI report to a network according to the described techniques, UE 115 may provide one or more enhancements to CLI mitigation techniques performed by the network and other benefits.

[0091] Figure 2A , Figure 2B and Figure 2CEach illustrates an example of a wireless communication system 200 that supports CLI reporting on a physical uplink channel according to one or more aspects of the present disclosure. In some examples, the wireless communication system 200 (e.g., wireless communication system 200-a, wireless communication system 200-b, and wireless communication system 200-c) can implement aspects of the wireless communication system 100. For example, the wireless communication systems 200 may each include one or more network entities 205 (e.g., network entity 205-a, network entity 205-b, network entity 205-c, network entity 205-d, network entity 205-e, and network entity 205-f) and one or more UEs 215 (e.g., UE 215-a, UE 215-b, UE 215-c, UE 215-d, UE 215-e, and UE 215-f), which may be reference 1. Figure 1 Examples of corresponding devices described. Figure 2A , Figure 2B and Figure 2C In the example of FIG. 1 , the network entity 205 may be as shown in FIG. Figure 1 Examples of CU 160, DU 165, RU 170, base station 140, IAB node 104, or one or more other network nodes are described. Wireless communication system 200 may include features for improving communication between UE 215 and the network, as well as other benefits.

[0092] exist Figure 2A , Figure 2B and Figure 2C In the example of , UE 215 and network entity 205 can communicate via one or more communication links 210 (e.g., communication link 210-a, communication link 210-b, communication link 210-c, and communication link 210-d) and via one or more communication links 220 (e.g., communication link 220-a, communication link 220-b, communication link 220-c, communication link 220-d, and communication link 220-e). Communication link 210 can be an example of an uplink, and communication link 220 can be an example of a downlink. Additionally or alternatively, communication link 210 and communication link 220 can each be as described in detail in detail in FIG. Figure 1Examples of the communication link 125 described. Each wireless communication system 200 may illustrate a communication device (e.g., one or more UEs 215, one or more network entities 205) operating in a full-duplex mode (e.g., performing full-duplex wireless communication) or a half-duplex TDD mode (e.g., performing half-duplex TDD wireless communication). That is, full-duplex (or half-duplex TDD) capability may exist at one or more network entities 205, one or more UEs 215 (or both). For example, the wireless communication system 200 may support a TDD radio frequency band (e.g., a radio frequency spectrum band configured for TDD communication), an FDD radio frequency band (e.g., a radio frequency spectrum band configured for FDD communication), full-duplex communication at one or more network entities 205 (and / or one or more UEs 215), half-duplex communication at one or more UEs 215, or any combination thereof.

[0093] Each wireless communication system 200 can support multiple types of full-duplex operation. For example, a communication device (e.g., network entity 205, UE 215) operating within the wireless communication system 200 can support in-band full-duplex (IBFD) operation, sub-band FDD (SBFD) operation (e.g., frequency duplex operation), or both. In some examples of IBFD operation, a communication device can send and receive wireless communications on the same time and frequency resources (e.g., the same time slot and component carrier bandwidth). For example, downlink communications and uplink communications can share time and frequency resources (e.g., IBFD time and frequency resources). In some examples, time and frequency resources may partially overlap or completely overlap. Additionally or alternatively, for SBFD operation, a communication device may send and receive communications on the same time resources and one or more different frequency resources. That is, downlink resources may be separated from uplink resources in the frequency domain.

[0094] exist Figure 2A In some examples, the network entity 205-a may support SBFD operations such that downlink communications sent by the network entity 205-a (e.g., to the UE 215-b) may overlap in time with uplink communications received by the network entity 205-a (e.g., from the UE 215-a). In some examples, the network entity 205-a may configure communications for the UE 215-a and the UE 215-b according to the resource structure 240. The resource structure 240 may include time domain resources (e.g., time slots, symbols) allocated for downlink data 250 (e.g., time domain resources 245-a), time domain resources allocated for uplink data 251 (e.g., time domain resources 245-d), and one or more time domain resources allocated for both the downlink data 250 and the uplink data 251 (e.g., time domain resources 245-b and time domain resources 245-c).

[0095] In some examples, the time domain resources (e.g., time domain resources 245-b and time domain resources 245-c) allocated for both downlink data 250 and uplink data 251 can be referred to as D+U time slots (or D+U symbols). In some examples, the D+U time slots can include half-duplex symbols (e.g., downlink symbols or uplink symbols) or full-duplex symbols (e.g., both downlink symbols and uplink symbols). For example, time domain resources 245-b and time domain resources 245-c (e.g., D+U time slots) can be examples of time slots where the radio frequency band is used to send both uplink communications (e.g., uplink transmissions) and downlink communications (e.g., downlink transmissions). In some examples, uplink transmissions and downlink transmissions can occur in overlapping frequency bands (e.g., for IBFD operations) or adjacent frequency bands (e.g., for SBFD operations).

[0096] For SBFD operation in which uplink transmission and downlink transmission occur in adjacent frequency bands, a half-duplex communication device may transmit in an uplink RF band or receive in a downlink RF band. That is, for a given time domain resource such as time domain resource 245-b (e.g., for a given D+U time slot or a given D+U symbol), a half-duplex device (e.g., UE 215-a, UE 215-b) may transmit uplink data 251 in an uplink RF band 271 (e.g., perform PUSCH transmission), or receive downlink data 250 in a downlink RF band 270. For example, UE 215-a may transmit uplink data 251 in an uplink RF band 271, while UE 215-b may receive downlink data 250 in a downlink RF band 270.

[0097] Additionally or alternatively, for SBFD operations in which uplink and downlink transmissions occur in adjacent frequency bands, a full-duplex device may transmit in an uplink RF band and receive in a downlink RF band. That is, for a given time domain resource such as time domain resource 245-b (e.g., for a given D+U time slot or a given D+U symbol), a full-duplex device may transmit uplink data 251 in an uplink RF band 271 (e.g., perform a PUSCH transmission) and receive downlink data 250 in a downlink RF band 270. Figure 2B In the example of , UE 215 - c (eg, a full-duplex device) may send communications in an uplink RF band and receive communications in a downlink RF band (eg, in the same D+U time slot or the same D+U symbol).

[0098] In some examples, full-duplex communication can provide latency reduction. For example, latency savings can be achieved by receiving downlink signals in uplink time slots. In addition, full-duplex communication can provide spectrum efficiency enhancement (e.g., per cell or per UE), efficient resource utilization and coverage extension, and other benefits. However, in some examples, full-duplex communication may cause one or more types of interference, such as inter-cell interference (e.g., from adjacent communication devices), self-interference (e.g., for full-duplex communication devices) and CLI (e.g., inter-cell CLI or intra-cell CLI). For example, a communication device (e.g., one or more network entities 205, one or more UEs 215) may experience self-interference 230 (e.g., self-interference 230-a, self-interference 230-b, self-interference 230-c, and self-interference 230-d) between a pair of beams (such as a beam for sending communication and a beam for receiving communication). In some examples, self-interference may be caused by signal leakage between an antenna panel for sending communication and an antenna panel for receiving communication.

[0099] Additionally or alternatively, neighboring communication devices (e.g., neighboring UE 215, neighboring network entity 205) may concurrently perform full-duplex communication (or half-duplex TDD) such that communications received by a first communication device may overlap in time with communications sent by a second communication device (e.g., neighboring communication device). In such an example, communications sent by the second communication device may interfere with communications received at the first communication device. For example, communications sent by the second communication device may result in a CLI at the first communication device. In some examples, a CLI (e.g., CLI 225-a, CLI 225-b, CLI 225-c, CLI 225-d, CLI 225-e, or CLI 225-f) may be caused by energy leakage due to timing and frequency misalignment (e.g., misalignment) between neighboring communication devices.

[0100] Additionally or alternatively, CLI may be caused by an automatic gain control (AGC) mismatch (eg, misalignment). Figure 2A As illustrated in the example of , the AGC of UE 215-b may be driven (e.g., controlled) by downlink communications from a serving cell (e.g., network entity 205-a). In such an example, uplink communications sent from UE 215-a may saturate the AGC of UE 215-b, resulting in a misalignment (e.g., loss of orthogonality) of downlink communications received by UE 215-b and uplink communications sent by UE 215-a. In some examples, the misalignment of downlink communications and uplink communications may result in CLI 225-a at UE 215-b.

[0101] In some examples, network entity 205-a may operate in full-duplex mode (e.g., SBFD or IBFD) and UE 215 (e.g., UE 215-a and UE 215-b) may operate in half-duplex mode. For example, network entity 205-a may receive uplink communications from UE 215-a (e.g., via communication link 210-a) while sending downlink communications to UE 215-b (e.g., via communication link 220-a). In such an example, full-duplex communications at network entity 205-a may cause self-interference 230-a. Additionally or alternatively, network entity 205-a and network entity 205-b (e.g., adjacent network entities) may perform full-duplex communications concurrently such that a downlink signal sent by network entity 205-b may overlap an uplink signal received by network entity 205-a, thereby causing CLI 225-b.

[0102] Additionally or alternatively, UE 215-a and UE 215-b (e.g., adjacent UEs) may concurrently perform half-duplex TDD communications such that an uplink signal transmitted by UE 215-b may overlap a downlink signal received by UE 215-a, which may result in CLI 225-a. In some examples, UE 215-a may operate in a cell different from a cell in which UE 215-b may operate. For example, UE 215-a and UE 215-b may operate in adjacent cells. In an example, CLI 225 may be an example of an inter-cell CLI. Additionally or alternatively, network entity 205-b may concurrently perform full-duplex communications with network entity 205-a. In such an example, downlink communications transmitted by network entity 205-b may result in inter-cell interference at UE 215-b. For example, downlink communications sent by network entity 205-b (eg, to another UE (not shown)) may interfere with downlink communications received by UE 215-b (eg, from network entity 205-a).

[0103] In some other examples, UE 215-a and UE 215-b may operate in the same cell. In such an example, CLI 225 may be an example of an intra-cell CLI. For example, network entity 205-a may operate in full-duplex mode (e.g., in SBFD) such that network entity 205-a may configure downlink communications for UE 215-a in frequency domain resources adjacent to frequency domain resources allocated for uplink communications from UE 215-b. For example, network entity 205-a may configure UE 215-b to receive downlink data 250 in time domain resources 245-b and in downlink radio frequency band 270 (e.g., from network entity 205-a), and UE 215-a may be configured to send uplink data 251 in time domain resources 245-b (e.g., adjacent frequency resources) in uplink radio frequency band 271. In such an example, uplink communications sent by UE 215-a may interfere with downlink communications received at UE 215-b.

[0104] exist Figure 2B In some examples of wireless communication systems 200-b, network entity 205-c and UE 215-c may each operate in a full-duplex mode (e.g., IBDF) such that UE 215-c may receive downlink communications from network entity 205-c via communication link 220-b while simultaneously sending uplink communications to network entity 205-c via communication link 210-c. In such an example, full-duplex communications at network entity 205-c and full-duplex communications at UE 215-c may result in self-interference 230-b and self-interference 230-c, respectively. In some examples of wireless communication systems 200-b, UE 215-c and UE 215-d may each operate in a multiple transmit and receive mode. In such an example, downlink communications and uplink communications performed by network entity 205-c may occur at two different antenna panels located at two transmit and receive points. For example, reception of uplink communications from UE 215-c may occur at an antenna panel at a first transmit and receive point, and transmission of downlink communications to UE 215-c may occur at an antenna panel at a second transmit and receive point. In some other examples, reception of uplink communications and transmission of downlink communications may occur at two co-located antenna panels of a network entity 205-c (e.g., a single base station).

[0105] exist Figure 2CIn an example of a wireless communication system 200-c, UE 215-e may operate in a full-duplex mode (e.g., SBFD) such that UE 215-e may receive downlink communications from network entity 205-f via communication link 220-d while simultaneously sending uplink communications to network entity 205-e via communication link 210-d. In such an example, full-duplex communications at UE 215-e may result in self-interference 230-d. In some examples of wireless communication system 200-c, network entity 205-e and network entity 205-f may be examples of transmit and receive points, and UE 215-e (e.g., and UE 215-f) may operate in a multiple transmit and receive mode. In such an example, uplink communications sent from UE 215-e may result in CLI 225-e (e.g., intra-cell CLI) at UE 215-f.

[0106] In some examples, to reduce interference within the wireless communication system 200, the network (e.g., one or more network entities 205) may employ one or more interference mitigation techniques. Figure 2A As illustrated in the example of , the network may configure UE 215-b to perform CLI measurements and reports. In some examples, the network may configure UE 215 to perform CLI measurements and reports, wherein the report is sent via lower layer (e.g., L1, PHY layer) signaling (e.g., via a lower layer CLI framework). The L1 CLI framework may provide increased flexibility and enable the network to adapt to dynamic changes in the CLI. In some examples of the L1 CLI framework, CLI measurements and reports may be triggered via DCI (e.g., a dedicated DCI or a group common DCI). Additionally or alternatively, for L1 CLI measurements and reports, the network may configure UE 215-a (e.g., a sending UE, an interfering UE) with resources for sending reference signals to be measured by UE 215-b. For example, the network may configure UE 215-a with non-periodic, semi-persistent, or periodic resources (e.g., non-zero power sounding reference signal (SRS) resources) for sending reference signals. Additionally or alternatively, the network may configure UE 215-b (e.g., a receiving UE, an aggressor UE) with resources for performing CLI measurements on reference signals sent by UE 215-a. For example, the network may configure UE 215-b with aperiodic, semi-persistent, or periodic CLI resources.

[0107] In some examples, the network entity 205-a and the UE 215-b may support subband-based CLI measurement and reporting. Additionally or alternatively, the network entity 205-a and the UE 215-b may support beam-based CLI measurement and reporting. For example, the UE 215-b may determine a beam for performing CLI measurement based on a quasi-co-location relationship (e.g., a quasi-co-location relationship associated with a spatial parameter of a received beam, a type D quasi-co-location relationship) between one or more beams (e.g., a transmit configuration indicator (TCI) state) and a configured CLI measurement resource.

[0108] In some examples of CLI reporting via lower layer signaling, the network may configure UE 215-b to measure and report CLI using the CSI framework. For example, the network may configure UE 215-b to include a CLI report as part of a CSI report. In some examples, the network may configure UE 215-b to report CLI as part of a CSI report via higher layer parameters such as a reportQuantity information element (IE). That is, the CSI framework may be extended to include CLI reporting. In such an example, the CLI measurement resources may be based on interference measurement resources (or other resources allocated for CLI measurements). For example, the network may configure CLI resources via measurement resource configuration, such as interference measurement resources for interference measurements with zero power SRS or CSI. In some examples, the network may configure UE 215-b via virtual channel measurement resources so that the CLI measurement resources may be based on interference measurement resources with zero power SRS or CSI interference measurements. It should be understood that the names of the IEs described herein may vary based on the specific implementation of one or more devices (e.g., UE 215, network entity 205, or both), and the examples described herein should not be considered limited to the scope of coverage of the claims or the present disclosure.

[0109] In some examples, if the network configures UE 215-b to measure and report CLI reports via the CSI framework, the network may configure UE 215-b to report CLI (e.g., CLI 225-a) using the same one or more rules as may be used to report CSI. That is, if the network configures UE 215-b to perform CLI reporting as part of the CSI reporting framework, the network may configure UE 215-b using (e.g., following) the same one or more multiplexing rules as may be used for CSI.

[0110] For example, the network may configure UE 215-b to map CSI reports (e.g., uplink control information) on one or more uplink channels according to one or more mapping rules. Here, the network may configure UE 215-b with one or more rules for mapping uplink control information, such as downlink feedback information or CSI reports (or both), on PUSCH. In some examples, the network may configure UE 215-b to map feedback information (e.g., HARQ-ACK information) to resource elements around demodulation reference signal (DMRS) symbols. That is, the modulated HARQ-ACK symbol may be mapped starting on an available (e.g., first available) non-DMRS symbol after a DMRS symbol (e.g., first DMRS symbol). In some examples, the modulated HARQ-ACK symbol may be mapped starting on the first available non-DMRS symbol after the first DMRS symbol, regardless of the amount (e.g., quantity) of DMRS symbols allocated in the PUSCH transmission. Additionally or alternatively, the network may configure UE 215-b to begin mapping the first portion of the CSI and the second portion of the CSI on the first available non-DMRS symbol (e.g., regardless of the amount of DMRS symbols allocated in the PUSCH transmission). In some examples, if the PUSCH transmission is punctured by feedback information (e.g., HARQ-ACK), the network may configure UE 215-b to begin mapping the first portion of the CSI after a particular amount of reserved HARQ-ACK resource elements. That is, the first portion of the CSI may not be mapped on the reserved HARQ ACK resource elements.

[0111] Additionally or alternatively, the second portion of the CSI may not be mapped on resource elements used for the first portion of the CSI. In some examples, if the PUSCH is HARQ-ACK rate matched, the second portion of the CSI and the PUSCH data may be mapped to reserved HARQ-ACK resource elements. Additionally or alternatively, the network may configure UE 215-b to map HARQ-ACK and then (e.g., subsequently) map the first portion of the CSI report. In such an example, the first portion of the CSI report and the second portion of the CSI report may not be mapped on HARQ-ACK resource elements.

[0112] In some examples, for uplink control information on PUSCH with uplink shared channel data, the amount of resources used for the first part of CSI (e.g., CSI part 1) may be calculated according to the following Equation 1:

[0113]

[0114] The parameter Q′ CSI-1The parameter O may represent the number of coded modulation symbols (eg, per layer) transmitted for the first part of the CSI report. CSI-1 may represent the amount of bits corresponding to the first part of the CSI report, and the parameter L CSI-1 The parameter may represent the amount of cyclic redundancy check bits used for the first part of the CSI report. can represent an offset (e.g., a scaling factor), the parameter The parameter may represent the amount of resource elements available for transmitting uplink control information in OFDM symbol (l) in a PUSCH transmission. The parameter C may represent the amount (e.g., the total number) of OFDM symbols for PUSCH (e.g., including OFDM symbols allocated for DMRS), and the parameter α may represent a scaling factor (e.g., configured via higher layer signaling). In some examples, the parameter C UL-SCH The parameter K may represent the amount of code blocks of uplink shared channel data used for PUSCH transmission, and r may represent the (eg, rth) code block size of uplink shared channel data for PUSCH transmission. Additionally or alternatively, parameter Q′ ACK The number of decoded modulation symbols (eg, per layer) used for feedback information (eg, HARQ-ACK) sent on the PUSCH may be indicated.

[0115] Additionally or alternatively, for uplink control information on PUSCH without uplink shared channel data, the amount of resources used for the first part of CSI (e.g., CSI part 1) may be calculated according to the following equation 2:

[0116]

[0117] The parameter R can represent the decoding rate of PUSCH, and the parameter Q m It can indicate the modulation order of PUSCH.

[0118] Additionally or alternatively, for uplink control information on a PUSCH with uplink shared channel data, the amount of resources used for the second part of the CSI (e.g., CSI part 2) may be calculated according to the following equation 3:

[0119]

[0120] The parameter Q′ CSI-2 The parameter O may represent the amount of coded modulation symbols (eg, per layer) transmitted for the second part of the CSI report. CSI-2 may represent the amount of bits corresponding to the second part of the CSI report, and the parameter L CSI-2The amount of cyclic redundancy check bits used for the second part of the CSI report may be indicated.

[0121] In some examples, the item may correspond to the amount of resources available for uplink control information, and It may correspond to the amount of bits in the decoding block. Therefore, the decoding rate of the PUSCH transmission may be determined according to the following equation 4:

[0122]

[0123] Additionally or alternatively, for uplink control information on PUSCH without uplink shared channel data, the amount of resources used for the second part of CSI (e.g., CSI part 2) may be calculated according to the following equation 5:

[0124]

[0125] In some other examples, the network may configure UE 215-b with one or more rules for mapping uplink control information on PUCCH. For example, the network may configure UE 215-b according to a PUCCH format (e.g., PUCCH format 2). In such an example, the network may configure UE 215-b to encode (e.g., jointly encode) one or more bits corresponding to feedback information (e.g., HARQ-ACK), scheduling request, CSI report, or any combination thereof. Additionally or alternatively, the amount of CSI bits (e.g., corresponding to CSI reports) that can be attached to feedback information bits or scheduling request bits can be determined so that the uplink control information bits attached by the cyclic redundancy check can be encoded at a decoding rate that does not exceed a threshold (e.g., a maximum configured decoding rate or other suitable decoding rate). In some examples, if the decoding rate exceeds the threshold for PUCCH format 2, UE 215-b may, for example, discard the CSI bits using the same priority rule (or multiple rules) as that available for CSI omission on PUSCH.

[0126] In some other examples, the network may configure UE 215-b according to one or more other PUCCH formats (e.g., PUCCH format 3, PUCCH format 4). In such an example, the simultaneous transmission of feedback information, scheduling requests, and CSI reports may be configured via control signaling. For example, the network may configure UE 215-b using a configuration (e.g., an RRC configuration) to encode (e.g., jointly encode) the feedback information (e.g., with or without a scheduling request) and the first part of the CSI report. In such an example, the second part of the CSI may then be encoded (e.g., separately encoded). Additionally or alternatively, the network may configure UE 215-b to encode (e.g., jointly) the feedback information (e.g., with or without a scheduling request) and the first part of the CSI report at a coding rate (e.g., a maximum coding rate or other suitable coding rate for PUCCH format 3 or PUCCH format 4). In some examples, the remaining resources (e.g., if available) of the configured resources (e.g., physical resource blocks (PRBs)) can be used to encode the second part of the CSI report. In some examples, some (or all) bits of the second part of the CSI report can be dropped, for example, using the same priority rule (or rules) as can be used to omit CSI on the PUSCH.

[0127] However, in some examples, configuring UE 215-b to measure and report CLI via lower layer signaling (e.g., as part of a CSI framework) may increase control signaling overhead at UE 215-b (e.g., associated with sending a channel state information report). Therefore, in some other examples of CLI reporting via lower layer signaling, the network may configure UE 215-b to measure and report CLI via a dedicated CLI reporting framework. In such examples, the CLI reporting configuration may include CLI measurement resources (e.g., resources for zero-power SRS or CSI interference measurements), which may be based on the CLI measurement resources. In some examples, by using a dedicated CLI reporting framework, the network may reduce the impact of CLI reporting on the CSI process. For example, a CLI report may be configured as a type of uplink control information (e.g., in addition to uplink control information or other information used for CSI reporting).

[0128] In such cases, if the network configures UE 215-b to measure and report CLI reports via a dedicated CLI reporting framework, the CLI reports may be configured separately from the CSI reports. For example, the CLI reports may be configured for UE 215-b as part of another type of uplink control information (e.g., in addition to CSI, feedback information, and scheduling resources). Thus, the network may configure UE 215-b with one or more rules for performing CLI measurement and reporting. For example, the network may configure UE 215-b with (e.g., define) one or more rules for multiplexing CLI on one or more physical uplink channels (e.g., PUSCH, PUCCH, or both). Additionally or alternatively, the network may configure UE 215-b with one or more rules for determining an amount of resources to be used to multiplex CLI on a physical uplink channel (e.g., PUSCH). For example, the network may utilize one or more offset values ​​(such as parameters) to be used to determine the amount of resources. ). Additionally or alternatively, the network may configure UE 215-b with one or more rules for mapping CLI reports on PUSCH (e.g., one or more mapping rules for PUSCH allocation). In some examples, the network may configure UE 215-b with one or more rules for determining whether CLI reports may be multiplexed on PUCCH. In such an example, the network may configure UE 215-b with one or more rules for encoding (e.g., and mapping) CLI reports to PUCCH.

[0129] In some examples, the network may configure UE 215-b with such rules via a CLI report configuration (e.g., via a CLIreportconfig IE). For example, UE 215-b may receive a first message indicating a CLI report configuration 255. In some examples, the CLI report configuration 255 may be associated with a first set of rules for determining an amount of resources for multiplexing CLI reports 260 on a physical uplink channel and a second set of rules for multiplexing CLI reports 260 on a physical uplink channel via the amount of resources. In some examples, UE 215-b may send a CLI report 260 on a physical uplink channel according to the first set of rules and the second set of rules. The CLI report 260 may indicate one or more CLI measurements performed by the UE.

[0130] As described herein, techniques for CLI reporting on a physical uplink channel may provide one or more enhancements to network performance in some network deployment scenarios. In some examples, such techniques for CLI reporting on a physical uplink channel may provide one or more enhancements for interference mitigation (e.g., interference handling, interference management), such as inter-network entity CLI, inter-UE CLI, self-interference, inter-subband CLI, and inter-operator CLI. For example, by sending CLI report 260 to the network, UE 215-b may provide one or more enhancements to CLI mitigation techniques performed by the network, as well as other benefits.

[0131] Figure 3A and Figure 3B Each illustrates an example of a duplex operation scheme 300 supporting CLI reporting on a physical uplink channel according to one or more aspects of the present disclosure. In some examples, the full-duplex operation scheme 300 (full-duplex operation scheme 300-a and full-duplex operation scheme 300-b) can implement various aspects of the wireless communication system 100 or be implemented by various aspects of the wireless communication system 100. For example, the full-duplex operation scheme 300 can be implemented by a network entity or a UE, which can be as shown in reference Figure 1 Examples of the corresponding devices described. Figure 3A and Figure 3B In some examples, the network entity may be as shown in FIG. Figure 1 Examples of CU 160, DU 165, RU 170, base station 140, IAB node 104, or one or more other network nodes are described. Full-duplex operation scheme 300 may include features for improving communications between a UE and a network, among other benefits.

[0132] In some examples, a wireless communication device (e.g., a network entity or a UE) may support full-duplex communication, wherein the communication device may send and receive communications simultaneously, thereby facilitating latency savings achieved by receiving downlink signals in uplink time slots (or symbols). In some examples, a communication device may support multiple (e.g., two) types of full-duplex operation. For example, a communication device may support SBFD operation, wherein the communication device may send and receive communications on the same time resources and on different frequency resources. That is, downlink resources may be separated from uplink resources in the frequency domain.

[0133] For example, Figure 3AAs illustrated in the example of , the network may configure one or more UEs according to configuration 305-a. In such an example, the network may configure a downlink transmission (e.g., transmission of downlink data 310) for the UE in a frequency domain resource (e.g., resource 315-a), which may be adjacent to a frequency domain resource (e.g., resource 315-b) configured for an uplink transmission (e.g., transmission of uplink data 320) of another UE. In some examples, in order to reduce interference between uplink transmissions (e.g., scheduled for resource 315-a) and downlink transmissions (e.g., scheduled for resource 315-b), the network may configure resource 315-a and resource 315-b to be separated by a guard band 316.

[0134] Additionally or alternatively, such as Figure 3B As illustrated in the example of , a network (e.g., a network entity) may support IBFD operation so that the network entity can send and receive communications on the same time resources and the same frequency resources (e.g., the same time slot and carrier bandwidth). For example, the network may configure one or more UEs according to configuration 305-b, configuration 305-c, or both. In such an example, the network may configure downlink transmissions (e.g., transmissions of downlink 310) and uplink transmissions (e.g., transmissions of uplink 320) so that the downlink transmissions and uplink transmissions may share the same one or more time and frequency resources (e.g., IBFD time and frequency resources). In some examples, the network may configure one or more UEs according to configuration 305-b so that one or more time and frequency resources (e.g., resources 315-c) allocated for transmission of uplink data 320 may overlap (e.g., completely overlap) with one or more time and frequency resources (e.g., resources 315-d) allocated for transmission of downlink data 310. Additionally or alternatively, the network may configure one or more UEs according to configuration 305-c such that a portion of one or more time and frequency resources (e.g., resources 315-e) allocated for transmission of uplink data 320 may overlap with a portion of one or more time and frequency resources (e.g., resources 315-f) allocated for transmission of downlink data 310. That is, resources 315-e may partially overlap with resources 315-f.

[0135] In some examples, although full-duplex communication may provide one or more spectral efficiency enhancements (e.g., per cell or per UE), efficient resource utilization, and coverage area extension, concurrent full-duplex communication performed by adjacent communication devices may result in CLI. For example, adjacent communication devices may perform full-duplex communication concurrently, such that communications received by a first communication device may overlap in time with communications sent by a second communication device (e.g., an adjacent communication device). In such an example, communications sent by the second communication device may result in CLI at the first communication device. In some examples, in order to reduce the impact of CLI, the network may employ one or more interference mitigation techniques.

[0136] As described herein, some techniques for CLI reporting on a physical uplink channel may provide one or more enhancements to interference mitigation techniques. For example, a network may send a first message to a UE indicating a CLI reporting configuration. In some examples, the CLI reporting configuration may be associated with a first set of rules for determining an amount of resources for multiplexing CLI reports on a physical uplink channel and a second set of rules for multiplexing CLI reports on a physical uplink channel via an amount of resources. In some examples, the network may receive a CLI report on a physical uplink channel according to the first set of rules and the second set of rules. The CLI report may indicate one or more CLI measurements performed by the UE. In some examples, the network may apply one or more CLI mitigation techniques based on the CLI report. For example, the network may schedule the UE so that CLI can be reduced. Additionally or alternatively, a network entity may instruct one or more of the UEs to switch beams so that CLI can be reduced. Therefore, by receiving the CLI report, the network may provide one or more enhancements to the CLI mitigation techniques performed by the network as well as other benefits.

[0137] Figure 4 An example of a resource mapping 400 for supporting CLI reporting on a physical uplink channel according to one or more aspects of the present disclosure is illustrated. In some examples, the resource mapping 400 may implement or be implemented by aspects of the wireless communication system 100. For example, the resource mapping 400 may be implemented by a network entity or a UE, which may be as described in reference to Figure 1 Examples of the corresponding devices described. Figure 4 In the example of Figure 1 Examples of CU 160, DU 165, RU 170, base station 140, IAB node 104, or one or more other network nodes are described. Resource mapping 400 may include features for improving communications between a UE and a network, among other benefits.

[0138] In some examples, the network may configure one or more communication devices (e.g., UEs) to measure and report CLI reports via a dedicated CLI reporting framework. In such examples, the network may configure the UE with one or more rules for performing CLI measurements and reporting. For example, the network may configure the UE with one or more rules for multiplexing CLI on one or more physical uplink channels (e.g., PUSCH, PUCCH, or both). Figure 4 As illustrated in the example of , the network may configure the CLI report to be multiplexed on the PUSCH. In such an example, the network may configure the UE with one or more rules for multiplexing (e.g., mapping) the CLI report on the PUSCH (e.g., one or more mapping rules for PUSCH allocation). In some examples, the network may configure the UE to multiplex (e.g., send) the CLI report on the PUSCH and suppress multiplexing (e.g., sending) the CSI report on the PUSCH. In such an example, the network may configure the UE to map the CLI report to the resources of the PUSCH according to the same mapping that may be used by the UE to map the CSI report on the PUSCH.

[0139] Additionally or alternatively, the UE may be configured to multiplex the CSI report and the CLI report on the PUSCH. In such an example, the network may configure the UE to multiplex the CLI report after the CSI report. That is, the CSI report may be assigned an increased priority relative to the CLI report. For example, the network may configure the UE to map the first part of the CSI report and the second part of the CSI report to resource elements on the PUSCH before mapping the first part of the CLI report and the second part of the CLI report (e.g., if available). Figure 4 As illustrated in the example of , the network may configure the UE to map the first CSI part 410 and the second CSI part 415 to resource elements on the PUSCH 405 before mapping the first CLI part 430 .

[0140] Additionally or alternatively, the network may configure the UE to multiplex the first part of the CLI report and the first part of the CSI report before the second part of the CSI report. That is, the CLI report may be assigned an increased priority relative to the second part of the CSI report. For example, the network may configure the UE to map the first part of the CSI report and the first part of the CLI report to resource elements on the PUSCH before mapping the second part of the CSI report and the second part of the CLI report (e.g., if available). Figure 4 As illustrated in the example of , the network may configure the UE to map the first CSI part 410 and the first CLI part 430 to resource elements on the PUSCH 405 before mapping the second CSI part 415 .

[0141] Additionally or alternatively, the network may configure the UE with one or more rules for determining resources to be used for multiplexing CLI on a physical uplink channel (e.g., PUSCH). For example, based on the one or more rules for multiplexing CLI on PUSCH, the UE may determine the amount of resource elements to allocate for each of multiple types of uplink control information (e.g., the first CSI part 410, the second CSI part 415, the feedback information 420, the DMRS 425, and the first CLI part 430 according to the one or more rules). For example, if the CLI report is assigned an increased priority relative to the second part of the CSI report (e.g., if the first CLI part 430 is mapped before the second CSI part 415), the UE may determine the amount of resource elements to allocate for each of the multiple types of uplink control information according to Equation 6 or Equation 7 (or both).

[0142] In some examples, for uplink control information on the PUSCH with uplink shared channel data, the amount of resources used for the second CSI part 415 (e.g., CSI part 2) may be calculated according to the following Equation 6:

[0143]

[0144] The parameter Q′ CLI-1 The amount of coded modulation symbols (eg, per layer) used for transmission of the first CLI part 430 (eg, CLI part 1) may be indicated.

[0145] Additionally or alternatively, for uplink control information on PUSCH without uplink shared channel data, the amount of resources used for the second CSI part 415 may be calculated according to the following equation 7:

[0146]

[0147] In some examples, the network may utilize an offset value (e.g., a cross-link information offset value, ) to configure the UE. The cross-link information offset value may be an example of an offset value as described with reference to FIG. 2. In some examples, the cross-link information offset value may be indicated via parameters such as beta_cli_p1 IE and beta_cli_p2 IE (e.g., one or more offset indicators), which may be different from parameters (e.g., beta_csi_p1 IE and beta_csi_p2 IE) used to indicate an offset value for CSI (e.g., a CSI offset value). In some examples, the CLI offset value may be semi-statically configured or dynamically indicated (e.g., indicated via beta_cli_p1 IE and beta_cli_p2 IE). In some examples, the CLI offset value semi-statically configured (e.g., via RRC signaling) may be different from the offset value semi-statically configured for CSI (e.g., a semi-statically configured CSI offset value).

[0148] In some examples, for the dynamic indication of the CLI offset value, the network may trigger the UE to perform a cross-link interference report via a dedicated DCI. In such an example, the CLI offset value may be indicated to the UE via the same signaling (e.g., reusing 2 bits of the same DCI) that can be used to indicate the offset value for CSI reporting (e.g., the CSI offset value). Additionally or alternatively, the network may trigger the UE to perform both cross-link interference reporting and CSI reporting via a dedicated DCI (e.g., the same dedicated DCI). In such an example, the CLI offset value and the CSI offset value may be indicated to the UE via the same signaling. That is, the same DCI message (e.g., 2 bits of the same DCI) may be used to indicate the offset value for both CLI reporting and CSI reporting. In such an example, the network may configure the UE with a table that enables selection (e.g., joint selection) of the offset value for CLI reporting and CSI reporting. Additionally or alternatively, the network may configure the UE with the CLI offset value via a relative offset to the channel state interference offset value (e.g., indicated via a dedicated DCI). That is, the relative offset may be configured by the network (e.g., via RRC configuration for CLI reporting). In some examples, the network may semi-statically configure the UE to determine the CLI offset value using a difference from the CSI offset value, where the difference may be indicated to the UE via semi-static signaling and the CSI offset may be indicated to the UE via dynamic signaling (e.g., beta_csi_p1 IE and beta_csi_p2 IE).

[0149] In some examples of dynamic indication of a CLI offset value, the network may trigger the UE to perform a cross-link interference report via a DCI that may be common to multiple UEs (e.g., a group common DCI). In such an example, the network may configure PUSCH resources (e.g., for carrying CLI reports) via semi-static signaling (e.g., via RRC). In such an example, the network may indicate the CLI offset value via parameters included in the configuration (such as beta_cli_p1 IE and beta_cli_p2 IE configured via RRC). Additionally or alternatively, the network may configure the UE to multiplex the CLI report on another PUSCH (such as a dynamic PUSCH). In such an example, the network may configure the UE to use (e.g., follow) the CLI offset value indicated to the network via DCI (e.g., if available). In some examples, if the UE fails to receive (or the network refrains from sending) a DCI containing a CLI offset value, the UE may use the CLI offset value indicated to the UE via control signaling (such as RRC signaling) (e.g., the UE may follow the CLI offset value configured by RRC).

[0150] Additionally or alternatively, the network may configure the UE with one or more rules for determining whether a CLI report may be multiplexed on the PUCCH. In such an example, the network may configure the UE with one or more rules for encoding (e.g., and mapping) the CLI to the PUCCH. In some examples, the network may configure the UE to multiplex (e.g., send) the CLI report on the PUCCH and refrain from multiplexing the CSI report on the PUCCH. In such an example, the network may configure the UE to multiplex the CLI report to the resources of the PUSCH according to the same one or more rules that may be used by the UE to multiplex the CSI report to the PUCCH.

[0151] The UE may be configured to multiplex CSI reports and CLI reports on the PUCCH. In such an example, the network may configure the UE to multiplex CLI reports on the PUCCH based on the values ​​of one or more parameters indicated from the network to the UE (e.g., simultaneousHARQ-ACK-CLI IE and simultaneousCSI-CLI IE). For example, the UE may determine whether to multiplex downlink feedback information (e.g., downlink HARQ-ACK) and CLI reports in the same PUCCH with or without a scheduling request based on the value of a first parameter such as the simultaneousHARQ-ACK-CLI IE. In some examples, if the UE fails to receive (e.g., or the network suppresses sending) the first parameter, the UE may discard the CLI report and include the downlink feedback information (e.g., with or without a scheduling request) in the PUCCH. Additionally or alternatively, the UE may determine whether to multiplex CSI reports and CLI reports in the same PUCCH based on the value of a second parameter such as the simultaneousCSI-CLI IE. In some examples, if the UE fails to receive (eg, or the network refrains from sending) the second parameter, the UE may discard the CLI report and include the CSI report in the PUCCH.

[0152] In some examples, information (e.g., flags) corresponding to one or more parameters may not be available to the UE. In such examples, the UE may refrain from following (e.g., may ignore) the one or more flags. For example, if a CLI report is available to the UE and a CSI report is not available to the UE, the UE may multiplex the CLI report regardless of the value of the second parameter (e.g., the value of the simultaneousCSI-CLI IE).

[0153] In some examples, if a CLI report or a CSI report is available for the UE (e.g., if the UE is configured to report CLI or CSI), the UE may determine whether to multiplex the CLI report or the CSI report on the same PUCCH as downlink feedback information based on the values ​​of one or more corresponding parameters. For example, if the UE is configured to report CLI, the network may configure the UE to determine whether to multiplex the CLI report on the same PUCCH (e.g., as downlink feedback information) based on the value of a first parameter such as a simultaneousHARQ-ACK-CLI IE. In some examples, if the value of the first parameter (e.g., simultaneousHARQ-ACK-CLI IE) is set to zero, the UE may multiplex downlink feedback (e.g., with or without a scheduling request) and suppress multiplexing of the CLI report. Therefore, if the value of the first parameter (e.g., simultaneousHARQ-ACK-CLI IE) is set to one, the UE may determine to multiplex downlink feedback (e.g., with or without a scheduling request) and the CLI report.

[0154] Additionally or alternatively, if the UE is configured to report CSI, the network may configure the UE to determine whether to multiplex CSI (e.g., as downlink feedback information) on the same PUCCH based on the value of the second parameter (e.g., simultaneousHARQ-ACK-CSI IE). In some examples, if the value of the second parameter (e.g., simultaneousHARQ-ACK-CSI IE) is set to zero, the UE may multiplex downlink feedback (e.g., with or without a scheduling request) and suppress multiplexing CSI reporting. Therefore, if the value of the second parameter (e.g., simultaneousHARQ-ACK-CSI IE) is set to one, the UE may determine to multiplex downlink feedback (e.g., with or without a scheduling request) and CSI reporting.

[0155] In some examples, if CLI reports and CSI reports are available for the UE (e.g., if the UE is configured to report CLI and CSI), the UE may determine whether to multiplex the CLI reports and the CSI reports on the same PUCCH based on the value of a third parameter such as the simultaneousCSI-CLI IE. For example, if the value of the third parameter (e.g., the simultaneousCSI-CLI IE) is set to one, the UE may multiplex downlink feedback (e.g., with or without a scheduling request), CLI reports, and CSI reports. Additionally or alternatively, if the value of the third parameter (e.g., the simultaneousCSI-CLI IE) is set to zero, the UE may multiplex downlink feedback (e.g., with or without a scheduling request) and CSI reports, and suppress multiplexing of the CLI report.

[0156] In some examples, if the network configures the UE to report CLI and CSI on PUCCH, the UE may multiplex the CLI report and the CSI report according to one or more rules (e.g., configured by the network). In some examples, the one or more rules for multiplexing the CLI report and the CSI report may depend on the format of the PUCCH. For PUCCH format 2, the network may configure the UE to multiplex the CSI report on the PUCCH and discard the CLI report.

[0157] In some examples, the network may configure the UE according to a PUCCH format (e.g., PUCCH format 3 or PUCCH format 4). In such an example, the network may configure the UE via control signaling (e.g., via RRC configuration) with one or more rules for simultaneously sending downlink feedback (e.g., with or without a scheduling request), CSI reports, and CLI reports. For example, the network may configure the UE to multiplex downlink feedback information (e.g., with or without a scheduling request) and the first part of the CSI report before multiplexing the CLI report. That is, the network may configure the UE to jointly encode bits corresponding to the downlink feedback information (e.g., with or without a scheduling request) and bits corresponding to the first part of the CSI report, and may separately encode bits corresponding to the first part of the CLI report, bits corresponding to the second part of the CSI report, and bits corresponding to the second part of the CLI report (e.g., if configured). In such an example, the feedback information (e.g., with or without a scheduling request) and the first part of the CSI report may be jointly encoded with a configured coding rate (e.g., a maximum coding rate for PUCCH format 3 or PUCCH format 4 or an otherwise acceptable coding rate). Additionally or alternatively, the remaining resources in the configured PRBs (e.g., if available) may be used to encode the first part of the CLI report, the second part of the CSI report, and the second part of the CLI report (e.g., if configured).

[0158] In some examples, the UE may encode the first part of the CLI report, the second part of the CSI report, and the second part of the CLI report based on the respective priorities of the CLI report and the CSI report (e.g., if configured). For example, some (or all) of the bits corresponding to the first part of the CLI report, the second part of the CSI report, and the second part of the CLI may be dropped (e.g., due to lack of remaining resources) according to an order that may be based on the respective priorities of the CLI report and the CSI report. In some examples, the order in which the bits are dropped may start with the bits associated with the relatively lowest priority. In some examples, the order (e.g., a priority order from relatively higher priority to relatively lower priority) may indicate that the UE encodes the first part of the CLI report, the second part of the CSI report, and then the second part of the CLI.

[0159] Additionally or alternatively, the ordering may instruct the UE to encode the second part of the CSI report, the first part of the CLI report, and then the second part of the CLI. In some cases, the network may configure the UE to jointly encode bits corresponding to the feedback information (e.g., with or without a scheduling request), the first part of the CSI report, and the first part of the CLI report. In some examples (e.g., if configured), the UE may separately encode bits corresponding to the second part of the CSI report and the second part of the CLI report. In such examples, some (or all) of the bits corresponding to the second part of the CSI report and the second part of the CLI report may be discarded based on the respective priorities of the CSI report and the CLI report (e.g., may be discarded starting with bits corresponding to the second part of the CLI report).

[0160] In some examples, the network may configure the UE with one or more rules for performing CLI measurements and reporting via a CLI report configuration (e.g., via a CLIreportconfig IE). For example, the UE may receive a first message indicating a CLI report configuration. In some examples, the CLI report configuration may be associated with a first set of rules for determining an amount of resources for multiplexing CLI reports on a physical uplink channel and a second set of rules for multiplexing CLI reports on a physical uplink channel via the amount of resources. In some examples, the UE may send a CLI report on a physical uplink channel according to the first set of rules and the second set of rules. The CLI report may indicate one or more CLI measurements performed by the UE. In some examples, by sending the CLI report to the network, the UE may provide one or more enhancements to CLI mitigation techniques performed by the network as well as other benefits.

[0161] Figure 5 An example of a process flow 500 in a system supporting CLI reporting on a physical uplink channel according to one or more aspects of the present disclosure is illustrated. The process flow 500 may implement or be implemented by one or more aspects of the wireless communication system 100 and the wireless communication system 200. For example, the process flow 500 may include a network entity 505 and a UE 515, which may be as described in reference to Figure 1 , Figure 2A , Figure 2B and Figure 2C Examples of corresponding devices described herein. Process flow 500 may be implemented by network entity 505, UE 515, or both. In the following description of process flow 500, operations between network entity 505 and UE 515 may occur in a different order or at a different time than shown. Some operations may also be omitted from process flow 500, and other operations may be added to process flow 500.

[0162] At 520, UE 515 may receive a first message indicating a CLI report configuration. The CLI report configuration may be as described in reference Figure 2A , Figure 3 and Figure 4 Examples of the described CLI reporting configurations. For example, the CLI reporting configuration may be associated with a first set of rules for determining an amount of resources for multiplexing CLI reports on a physical uplink channel and a second set of rules for multiplexing CLI reports on a physical uplink channel via the amount of resources.

[0163] In some examples, UE 515 may multiplex CLI reports on a physical uplink channel at 525. For example, UE 515 may multiplex CLI reports on a physical uplink channel (eg, PUSCH, PUCCH) via an amount of resources based on a second set of rules.

[0164] At 530, UE 515 may send a CLI report on a physical uplink channel according to the first set of rules and the second set of rules. For example, at 525, UE 515 may send a CLI report based on multiplexing the CLI report on the physical uplink channel. In some examples, the CLI report may be as described in reference Figure 2A , Figure 3 and Figure 4 Examples of CLI reports. For example, a CLI report may indicate one or more CLI measurements performed by UE 515.

[0165] Figure 6 A block diagram 600 of a device 605 supporting CLI reporting on a physical uplink channel according to one or more aspects of the present disclosure is shown. The device 605 may be an example of aspects of a UE 115 as described herein. The device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. The device 605 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0166] The receiver 610 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., a control channel related to CLI reporting on a physical uplink channel, a data channel, an information channel). The information may be communicated to other components of the device 605. The receiver 610 may utilize a single antenna or a collection of multiple antennas.

[0167] The transmitter 615 may provide means for transmitting signals generated by other components of the device 605. For example, the transmitter 615 may transmit information such as packets associated with various information channels (e.g., a control channel related to CLI reporting on a physical uplink channel, a data channel, an information channel), user data, control information, or any combination thereof. In some examples, the transmitter 615 may be co-located with the receiver 610 in a transceiver module. The transmitter 615 may utilize a single antenna or a collection of multiple antennas.

[0168] The communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof or various components thereof may be examples of means for performing various aspects of CLI reporting on a physical uplink channel as described herein. For example, the communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

[0169] In some examples, the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof, which is configured to or otherwise supports means for performing the functions described in the present disclosure. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0170] Additionally or alternatively, in some examples, the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting means for performing the functions described in the present disclosure).

[0171] In some examples, communication manager 620 can be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 610, transmitter 615, or both. For example, communication manager 620 can receive information from receiver 610, transmit information to transmitter 615, or be integrated with receiver 610, transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.

[0172] According to examples as disclosed herein, the communication manager 620 may support wireless communications at a UE (e.g., device 605). For example, the communication manager 620 may be configured to or otherwise support means for receiving a first message indicating a CLI report configuration associated with a first rule set for determining an amount of resources for multiplexing CLI reports on a physical uplink channel and a second rule set for multiplexing CLI reports on a physical uplink channel via the amount of resources. The communication manager 620 may be configured to or otherwise support means for sending a CLI report on a physical uplink channel according to the first rule set and the second rule set, the CLI report indicating one or more CLI measurements performed by the UE.

[0173] By including or configuring the communication manager 620 according to the examples described herein, the device 605 (e.g., a processor controlling or otherwise coupled to the receiver 610, the transmitter 615, the communication manager 620, or a combination thereof) can support techniques for reducing processing, reducing power consumption, and more efficiently utilizing communication resources.

[0174] Figure 7 A block diagram 700 of a device 705 supporting CLI reporting on a physical uplink channel according to one or more aspects of the present disclosure is shown. The device 705 may be an example of aspects of the device 605 or UE 115 as described herein. The device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. The device 705 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0175] The receiver 710 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., a control channel related to CLI reporting on a physical uplink channel, a data channel, an information channel). The information may be communicated to other components of the device 705. The receiver 710 may utilize a single antenna or a collection of multiple antennas.

[0176] The transmitter 715 may provide means for transmitting signals generated by other components of the device 705. For example, the transmitter 715 may transmit information such as packets associated with various information channels (e.g., a control channel related to CLI reporting on a physical uplink channel, a data channel, an information channel), user data, control information, or any combination thereof. In some examples, the transmitter 715 may be co-located with the receiver 710 in a transceiver module. The transmitter 715 may utilize a single antenna or a collection of multiple antennas.

[0177] The device 705 or its various components may be examples of components for performing various aspects of CLI reporting on a physical uplink channel as described herein. For example, the communication manager 720 may include a CLI configuration component 725, a CLI reporting component 730, or any combination thereof. The communication manager 720 may be an example of various aspects of the communication manager 620 as described herein. In some examples, the communication manager 720 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with the receiver 710, the transmitter 715, or both. For example, the communication manager 720 may receive information from the receiver 710, transmit information to the transmitter 715, or be integrated with the receiver 710, the transmitter 715, or both to obtain information, output information, or perform various other operations as described herein.

[0178] According to examples as disclosed herein, the communication manager 720 can support wireless communications at a UE (e.g., device 705). The CLI configuration component 725 can be configured to or otherwise support means for receiving a first message indicating a CLI report configuration associated with a first rule set for determining an amount of resources for multiplexing CLI reports on a physical uplink channel and a second rule set for multiplexing CLI reports on a physical uplink channel via the amount of resources. The CLI reporting component 730 can be configured to or otherwise support means for sending a CLI report on a physical uplink channel according to the first rule set and the second rule set, the CLI report indicating one or more CLI measurements performed by the UE.

[0179] Figure 8A block diagram 800 of a communication manager 820 supporting CLI reporting on a physical uplink channel in accordance with one or more aspects of the present disclosure is shown. The communication manager 820 may be an example of aspects of the communication manager 620, the communication manager 720, or both as described herein. The communication manager 820 or its various components may be examples of means for performing various aspects of CLI reporting on a physical uplink channel as described herein. For example, the communication manager 820 may include a CLI configuration component 825, a CLI reporting component 830, a trigger component 835, an offset value component 840, and a reporting manager 845, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses).

[0180] According to examples as disclosed herein, the communication manager 820 can support wireless communications at a UE. The CLI configuration component 825 can be configured to or otherwise support means for receiving a first message indicating a CLI report configuration, the CLI report configuration being associated with a first rule set for determining an amount of resources for multiplexing CLI reports on a physical uplink channel and a second rule set for multiplexing CLI reports on a physical uplink channel via the amount of resources. The CLI reporting component 830 can be configured to or otherwise support means for sending a CLI report on a physical uplink channel according to the first rule set and the second rule set, the CLI report indicating one or more CLI measurements performed by the UE.

[0181] In some examples, trigger component 835 may be configured to or otherwise support means for receiving a second message that triggers the UE to report one or more CLI measurements and includes an offset indicator, wherein sending the CLI report is based on receiving the second message. In some examples, offset value component 840 may be configured to or otherwise support means for determining one or more CLI offset values ​​based on the offset indicator, wherein the amount of resources is based on the one or more CLI offset values.

[0182] In some examples, to support determining one or more CLI offset values, offset value component 840 may be configured or otherwise support means for determining one or more CLI offset values ​​using an offset indicator and a table including a plurality of sets of CLI offset values. In some examples, to support determining one or more CLI offset values, offset value component 840 may be configured or otherwise support means for calculating one or more CLI offset values ​​using a difference from one or more CSI offset values.

[0183] In some examples, the CLI reporting configuration includes an indication of the difference value. In some examples, calculating the one or more CLI offset values ​​is based on receiving the first message. In some examples, the one or more CLI offset values ​​are different from the one or more CSI offset values.

[0184] In some examples, the offset value component 840 can be configured to or otherwise support means for receiving a second message indicating one or more CLI offset values, wherein the amount of resources is based on the one or more CLI offset values. In some examples, the trigger component 835 can be configured to or otherwise support means for receiving a third message that triggers the UE to report one or more CLI measurements, wherein the third message is common to a group of two or more UEs including the UE, and wherein sending the CLI report is based on receiving the third message.

[0185] In some examples, the third message includes an offset indicator. In some examples, determining one or more CLI offset values ​​is further based on the offset indicator. In some examples, the CLI reporting component 830 may be configured to or otherwise support a component for multiplexing CLI reports on a physical uplink channel via a resource amount based on a second rule set, the physical uplink channel including a PUSCH, wherein sending the CLI report is based on multiplexing. In some examples, to support multiplexing CLI reports, the CLI reporting component 830 may be configured to or otherwise support a component for multiplexing CLI reports after CSI reports.

[0186] In some examples, to support multiplexing CLI reports, the report manager 845 may be configured or otherwise support means for multiplexing a first portion of the CLI report after a first portion of the CSI report. In some examples, to support multiplexing CLI reports, the report manager 845 may be configured or otherwise support means for multiplexing a second portion of the CLI report after a second portion of the CSI report.

[0187] In some examples, CLI reporting component 830 may be configured or otherwise support means for receiving a second message instructing the UE to multiplex the CLI report with the feedback information. In some examples, CLI reporting component 830 may be configured or otherwise support means for multiplexing the CLI report with the feedback information based on receiving the second message, the physical uplink channel comprising a PUCCH, wherein sending the CLI report is based on multiplexing.

[0188] In some examples, CLI reporting component 830 may be configured or otherwise support means for receiving a third message instructing the UE to multiplex the CLI report with the CSI report, wherein multiplexing the CLI report with the feedback information includes. In some examples, CLI reporting component 830 may be configured or otherwise support means for multiplexing the CLI report with the feedback information and the CSI report based on receiving the second message and the third message. In some examples, the CLI report is multiplexed after the first portion of the CSI report and the feedback information.

[0189] In some examples, to support multiplexing of CLI reports with feedback information and CSI reports, CLI reporting component 830 may be configured as or otherwise support components for multiplexing CLI reports with feedback information and CSI reports based on an ordering based on their respective priorities.

[0190] In some examples, to support multiplexing the CLI report with the feedback information and the CSI report, the report manager 845 may be configured or otherwise support means for multiplexing the feedback information, the first portion of the CSI report, and the first portion of the CLI report. In some examples, to support multiplexing the CLI report with the feedback information and the CSI report, the report manager 845 may be configured or otherwise support means for discarding at least the second portion of the CLI report.

[0191] Fig. 9 A diagram of a system 900 including a device 905 supporting CLI reporting on a physical uplink channel according to one or more aspects of the present disclosure is shown. The device 905 may be an example of a device 605, a device 705, or a UE 115 as described herein or include a component of the device 605, the device 705, or a UE 115. The device 905 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 905 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 920, an input / output (I / O) controller 910, a transceiver 915, an antenna 925, a memory 930, a code 935, and a processor 940. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 945).

[0192] I / O controller 910 can manage input and output signals of device 905. I / O controller 910 can also manage peripheral devices that are not integrated into device 905. In some cases, I / O controller 910 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 910 can utilize an operating system such as or another known operating system. Additionally or alternatively, I / O controller 910 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 910 may be implemented as part of a processor such as processor 940. In some cases, a user may interact with device 905 via I / O controller 910 or via hardware components controlled by I / O controller 910.

[0193] In some cases, the device 905 may include a single antenna 925. However, in some other cases, the device 905 may have more than one antenna 925, which can send or receive multiple wireless transmissions concurrently. The transceiver 915 can communicate bidirectionally via one or more antennas 925, wired or wireless links, as described herein. For example, the transceiver 915 may represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. The transceiver 915 may also include a modem that modulates packets, provides the modulated packets to one or more antennas 925 for transmission, and demodulates packets received from one or more antennas 925. The transceiver 915 or the transceiver 915 and one or more antennas 925 can be examples of transmitters 615, transmitters 715, receivers 610, receivers 710, or any combination or components thereof as described herein.

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

[0195] The processor 940 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 cases, the processor 940 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 940. The processor 940 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 930) so that the device 905 performs various functions (e.g., functions or tasks that support CLI reporting on a physical uplink channel). For example, the device 905 or a component of the device 905 may include a processor 940 and a memory 930 coupled to or coupled to the processor 940, and the processor 940 and the memory 930 are configured to perform the various functions described herein.

[0196] According to examples as disclosed herein, the communication manager 920 may support wireless communications at a UE (e.g., device 905). For example, the communication manager 920 may be configured to or otherwise support means for receiving a first message indicating a CLI report configuration associated with a first rule set for determining an amount of resources for multiplexing CLI reports on a physical uplink channel and a second rule set for multiplexing CLI reports on a physical uplink channel via the amount of resources. The communication manager 920 may be configured to or otherwise support means for sending a CLI report on a physical uplink channel according to the first rule set and the second rule set, the CLI report indicating one or more CLI measurements performed by the UE.

[0197] By including or configuring the communication manager 920 according to examples as described herein, the device 905 can support techniques for improving communication reliability, reducing latency, more efficiently utilizing communication resources, and improving utilization of processing power.

[0198] In some examples, the communication manager 920 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 915, one or more antennas 925, or any combination thereof. Although the communication manager 920 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 920 may be supported or performed by the processor 940, the memory 930, the code 935, or any combination thereof. For example, the code 935 may include instructions executable by the processor 940 to cause the device 905 to perform various aspects of CLI reporting on the physical uplink channel as described herein, or the processor 940 and the memory 930 may be otherwise configured to perform or support such operations.

[0199] Fig.10 A block diagram 1000 of a device 1005 supporting CLI reporting on a physical uplink channel according to one or more aspects of the present disclosure is shown. The device 1005 may be an example of aspects of the network entity 105 as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. The device 1005 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0200] The receiver 1010 may provide a means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of the device 1005. In some examples, the receiver 1010 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 1010 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0201] The transmitter 1015 may provide means for outputting (e.g., sending, providing, communicating, transmitting) information generated by other components of the device 1005. For example, the transmitter 1015 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 1015 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1015 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1015 and the receiver 1010 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0202] The communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof or various components thereof may be examples of means for performing various aspects of CLI reporting on a physical uplink channel as described herein. For example, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

[0203] In some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting means for performing the functions described in the present disclosure. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0204] Additionally or alternatively, in some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting means for performing the functions described in the present disclosure).

[0205] In some examples, communication manager 1020 can be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 1010, transmitter 1015, or both. For example, communication manager 1020 can receive information from receiver 1010, transmit information to transmitter 1015, or integrate with receiver 1010, transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.

[0206] According to examples as disclosed herein, the communication manager 1020 may support wireless communication at a network entity, e.g., device 1005. For example, the communication manager 1020 may be configured to or otherwise support means for sending a first message indicating a CLI report configuration associated with a first rule set for determining an amount of resources for multiplexing CLI reports on a physical uplink channel and a second rule set for multiplexing CLI reports on a physical uplink channel via the amount of resources. The communication manager 1020 may be configured to or otherwise support means for receiving a CLI report on a physical uplink channel according to the first rule set and the second rule set, the CLI report indicating one or more CLI measurements performed by the UE.

[0207] By including or configuring the communication manager 1020 according to the examples described herein, the device 1005 (e.g., a processor controlling or otherwise coupled to the receiver 1010, the transmitter 1015, the communication manager 1020, or a combination thereof) can support techniques for reducing processing, reducing power consumption, and more efficiently utilizing communication resources.

[0208] Fig.11 A block diagram 1100 of a device 1105 supporting CLI reporting on a physical uplink channel according to one or more aspects of the present disclosure is shown. The device 1105 may be an example of aspects of the device 1005 or network entity 105 as described herein. The device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120. The device 1105 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0209] The receiver 1110 may provide a means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be delivered to other components of the device 1105. In some examples, the receiver 1110 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 1110 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0210] The transmitter 1115 may provide means for outputting (e.g., sending, providing, communicating, transmitting) information generated by other components of the device 1105. For example, the transmitter 1115 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 1115 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1115 may support outputting information by sending signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1115 and the receiver 1110 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0211] Device 1105 or its various components may be examples of components for performing various aspects of CLI reporting on a physical uplink channel as described herein. For example, communication manager 1120 may include configuration indication component 1125, reporting component 1130, or any combination thereof. Communication manager 1120 may be an example of various aspects of communication manager 1020 as described herein. In some examples, communication manager 1120 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 1110, transmitter 1115, or both. For example, communication manager 1120 may receive information from receiver 1110, transmit information to transmitter 1115, or be integrated with receiver 1110, transmitter 1115, or both to obtain information, output information, or perform various other operations as described herein.

[0212] According to examples as disclosed herein, the communication manager 1120 may support wireless communications at a network entity, e.g., the device 1105. The configuration indicating component 1125 may be configured to or otherwise support means for sending a first message indicating a CLI report configuration associated with a first rule set for determining an amount of resources for multiplexing CLI reports on a physical uplink channel and a second rule set for multiplexing CLI reports on a physical uplink channel via the amount of resources. The reporting component 1130 may be configured to or otherwise support means for receiving a CLI report on a physical uplink channel according to the first rule set and the second rule set, the CLI report indicating one or more CLI measurements performed by the UE.

[0213] Fig.12 A block diagram 1200 of a communication manager 1220 supporting CLI reporting on a physical uplink channel according to one or more aspects of the present disclosure is shown. The communication manager 1220 may be an example of aspects of the communication manager 1020, the communication manager 1120, or both as described herein. The communication manager 1220 or its various components may be examples of means for performing various aspects of CLI reporting on a physical uplink channel as described herein. For example, the communication manager 1220 may include a configuration indication component 1225, a reporting component 1230, a report triggering component 1235, an offset value indication component 1240, a multiplexing indication component 1245, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses), which may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with a network entity 105, between devices, components, or virtualized components associated with a network entity 105), or any combination thereof.

[0214] According to examples as disclosed herein, the communication manager 1220 may support wireless communications at a network entity. The configuration indication component 1225 may be configured to or otherwise support means for sending a first message indicating a CLI report configuration associated with a first rule set for determining an amount of resources for multiplexing CLI reports on a physical uplink channel and a second rule set for multiplexing CLI reports on a physical uplink channel via the amount of resources. The reporting component 1230 may be configured to or otherwise support means for receiving a CLI report on a physical uplink channel according to the first rule set and the second rule set, the CLI report indicating one or more CLI measurements performed by the UE.

[0215] In some examples, report trigger component 1235 may be configured to or otherwise support a component for sending a second message that triggers the UE to report one or more CLI measurements and includes an offset indicator, wherein receiving the CLI report is based on receiving the second message, and wherein the amount of resources is based on one or more CLI offset values ​​indicated by the offset indicator.

[0216] In some examples, the one or more CLI offset values ​​indicated by the offset indicator correspond to CLI offset values ​​included in the table. In some examples, the one or more CLI offset values ​​indicated by the offset indicator are based on a difference from one or more CSI offset values.

[0217] In some examples, the CLI reporting configuration includes an indication of a difference value. In some examples, one or more CLI offset values ​​are different from one or more CSI offset values.

[0218] In some examples, the offset value indicating component 1240 can be configured to or otherwise support means for sending a second message indicating one or more CLI offset values, wherein the amount of resources is based on the one or more CLI offset values. In some examples, the reporting triggering component 1235 can be configured to or otherwise support means for sending a third message triggering the UE to report one or more CLI measurements, wherein the third message is common to a group of two or more UEs including the UE, and wherein receiving the CLI report is based on the third message.

[0219] In some examples, the third message includes an offset indicator. In some examples, one or more CLI offset values ​​are based on the offset indicator. In some examples, the CLI report is multiplexed on the physical uplink channel via the resource amount after the CSI report and based on the second rule set.

[0220] In some examples, the CLI report is multiplexed on the physical uplink channel via the resource amount after the first portion of the CSI report and based on the second rule set. In some examples, the second portion of the CLI report is multiplexed on the physical uplink channel via the resource amount after the second portion of the CSI report.

[0221] In some examples, the multiplexing indication component 1245 can be configured to or otherwise support a component for sending a second message indicating that the UE multiplexes the CLI report with the feedback information, wherein the CLI report is multiplexed with the feedback information based on the second message.

[0222] In some examples, the multiplexing indication component 1245 may be configured to or otherwise support means for sending a third message instructing the UE to multiplex the CLI report with the CSI report, wherein the CLI report is multiplexed with the feedback information and the CSI report based on the third message.

[0223] In some examples, the CLI report is multiplexed after the first part of the CSI report and the feedback information. In some examples, the CLI report is multiplexed with the feedback information and the CSI report according to an ordering based on the respective priorities of the CLI report and the CSI report.

[0224] In some examples, the feedback information, the first portion of the CSI report, and the first portion of the CLI report are multiplexed on a physical uplink channel. In some examples, at least a portion of the second portion of the CLI report is discarded.

[0225] Fig.13 A diagram of a system 1300 including a device 1305 supporting CLI reporting on a physical uplink channel according to one or more aspects of the present disclosure is shown. The device 1305 may be an example of a device 1005, a device 1105, or a network entity 105 as described herein, or include components thereof. The device 1305 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1305 may include components that support output and acquisition communications, such as a communication manager 1320, a transceiver 1310, an antenna 1315, a memory 1325, a code 1330, and a processor 1335. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1340).

[0226] The transceiver 1310 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, the transceiver 1310 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1310 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1305 may include one or more antennas 1315 that may be capable of (e.g., concurrently) sending or receiving wireless transmissions. The transceiver 1310 may also include a modem for modulating a signal, providing a modulated signal for transmission (e.g., via one or more antennas 1315, via a wired transmitter), receiving a modulated signal (e.g., from one or more antennas 1315, from a wired receiver), and demodulating a signal. The transceiver 1310 or transceiver 1310 and one or more antennas 1315 or wired interfaces (where applicable) may be examples of transmitter 1015, transmitter 1115, receiver 1010, receiver 1110, or any combination thereof or any components thereof as described herein. In some examples, the transceiver may be operable to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0227] Memory 1325 may include RAM and ROM. Memory 1325 may store computer-readable, computer-executable code 1330 including instructions that, when executed by processor 1335, cause device 1305 to perform various functions described herein. Code 1330 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1330 may not be directly executable by processor 1335, but may (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some cases, memory 1325 may also include, among other things, BIOS, which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0228] The processor 1335 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof). In some cases, the processor 1335 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1335. The processor 1335 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1325) so that the device 1305 performs various functions (e.g., functions or tasks that support CLI reporting on a physical uplink channel). For example, the device 1305 or a component of the device 1305 may include a processor 1335 and a memory 1325 coupled to the processor 1335, and the processor 1335 and the memory 1325 are configured to perform the various functions described herein. Processor 1335 can be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can host functionality (e.g., by executing code 1330) to perform the functions of device 1305.

[0229] In some examples, bus 1340 may support communications of a protocol layer (e.g., within a protocol layer) of a protocol stack. In some examples, bus 1340 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within a component of device 1305, or communications performed between different components of device 1305 that may be co-located or located in different locations (e.g., where device 1305 may refer to a system in which one or more of communication manager 1320, transceiver 1310, memory 1325, code 1330, and processor 1335 may be located in one of the different components or divided between the different components).

[0230] In some examples, communication manager 1320 can manage aspects of communications with core network 130 (e.g., via one or more wired or wireless backhaul links). For example, communication manager 1320 can manage delivery of data communications for client devices such as one or more UEs 115. In some examples, communication manager 1320 can manage communications with other network entities 105 and can include a controller or scheduler for controlling communications with UE 115 in collaboration with other network entities 105. In some examples, communication manager 1320 can support an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between network entities 105.

[0231] According to examples as disclosed herein, the communication manager 1320 may support wireless communications at a network entity, e.g., device 1305. For example, the communication manager 1320 may be configured to or otherwise support means for sending a first message indicating a CLI report configuration associated with a first rule set for determining an amount of resources for multiplexing CLI reports on a physical uplink channel and a second rule set for multiplexing CLI reports on a physical uplink channel via the amount of resources. The communication manager 1320 may be configured to or otherwise support means for receiving a CLI report on a physical uplink channel according to the first rule set and the second rule set, the CLI report indicating one or more CLI measurements performed by the UE.

[0232] By including or configuring the communication manager 1320 according to examples as described herein, the device 1305 can support techniques for improving communication reliability, reducing latency, more efficiently utilizing communication resources, and improving utilization of processing power.

[0233] In some examples, the communication manager 1320 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1310, one or more antennas 1315 (e.g., where applicable), or any combination thereof. Although the communication manager 1320 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1320 may be supported or performed by the processor 1335, the memory 1325, the code 1330, the transceiver 1310, or any combination thereof. For example, the code 1330 may include instructions executable by the processor 1335 to cause the device 1305 to perform various aspects of CLI reporting on the physical uplink channel as described herein, or the processor 1335 and the memory 1325 may be otherwise configured to perform or support such operations.

[0234] Fig.14 A flow chart illustrating a method 1400 for supporting CLI reporting on a physical uplink channel according to one or more aspects of the present disclosure is shown. The operations of the method 1400 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1400 may be implemented by a UE or a component thereof as described herein. Figures 1 to 9 The UE 115 described herein may be executed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0235] At 1405, the method may include receiving a first message indicating a CLI reporting configuration associated with a first rule set for determining an amount of resources for multiplexing CLI reports on a physical uplink channel and a second rule set for multiplexing CLI reports on a physical uplink channel via the amount of resources. The operations of 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed as described in reference to Figure 8 The CLI configuration component 825 is executed.

[0236] At 1410, the method may include sending a CLI report on a physical uplink channel according to a first set of rules and a second set of rules, the CLI report indicating one or more CLI measurements performed by the UE. The operations of 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed as described in reference to Figure 8 The CLI reporting component 830 is used to execute.

[0237] Fig.15 A flowchart illustrating a method 1500 for supporting CLI reporting on a physical uplink channel according to one or more aspects of the present disclosure is shown. The operations of the method 1500 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1500 may be implemented by a UE or a component thereof as described herein. Figures 1 to 9 The UE 115 described herein may be executed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0238] At 1505, the method may include receiving a first message indicating a CLI reporting configuration associated with a first rule set for determining an amount of resources for multiplexing CLI reports on a physical uplink channel and a second rule set for multiplexing CLI reports on a physical uplink channel via the amount of resources. The operations of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed as described in reference to Figure 8 The CLI configuration component 825 is executed.

[0239] At 1510, the method may include receiving a second message that triggers the UE to report one or more CLI measurements and includes an offset indicator. The operations of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed as described in reference to Figure 8 The trigger component 835 is used to execute.

[0240] At 1515, the method may include determining one or more CLI offset values ​​based on the offset indicator, wherein the amount of resources is based on the one or more CLI offset values. The operations of 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed as described in reference to Figure 8 The offset value component 840 is used to perform the above operation.

[0241] At 1520, the method may include sending a CLI report on a physical uplink channel according to the first set of rules and the second set of rules, the CLI report indicating one or more CLI measurements performed by the UE, wherein sending the CLI report is based on receiving the second message. The operations of 1520 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1520 may be performed as described in reference to Figure 8 The CLI reporting component 830 is used to execute.

[0242] Fig.16 A flow chart illustrating a method 1600 for supporting CLI reporting on a physical uplink channel according to one or more aspects of the present disclosure is shown. The operations of the method 1600 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1600 may be implemented by a UE or a component thereof as described herein. Figures 1 to 9 The UE 115 described herein may be executed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0243] At 1605, the method may include receiving a first message indicating a CLI reporting configuration associated with a first rule set for determining an amount of resources for multiplexing CLI reports on a physical uplink channel and a second rule set for multiplexing CLI reports on a physical uplink channel via the amount of resources. The operations of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described in reference to Figure 8 The CLI configuration component 825 is executed.

[0244] At 1610, the method may include receiving a second message indicating one or more CLI offset values, wherein the amount of resources is based on the one or more CLI offset values. The operations of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed as described in reference to Figure 8 The offset value component 840 is used to perform the above operation.

[0245] At 1615, the method may include receiving a third message that triggers the UE to report one or more CLI measurements, wherein the third message is common to a group of two or more UEs including the UE. The operations of 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1615 may be performed as described in reference to Figure 8 The trigger component 835 is used to execute.

[0246] At 1620, the method may include sending a CLI report on a physical uplink channel according to the first set of rules and the second set of rules, the CLI report indicating one or more CLI measurements performed by the UE, and wherein sending the CLI report is based on receiving a third message. The operations of 1620 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1620 may be performed as described in reference to Figure 8 The CLI reporting component 830 is used to execute.

[0247] Fig.17 A flow chart illustrating a method 1700 for supporting CLI reporting on a physical uplink channel according to one or more aspects of the present disclosure is shown. The operations of the method 1700 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1700 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 5 as well as Figures 10 to 13 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0248] At 1705, the method may include sending a first message indicating a CLI reporting configuration associated with a first rule set for determining an amount of resources for multiplexing CLI reports on a physical uplink channel and a second rule set for multiplexing CLI reports on a physical uplink channel via the amount of resources. The operations of 1705 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed as described in reference to Fig.12 The configuration instructs component 1225 to execute.

[0249] At 1710, the method may include receiving a CLI report on a physical uplink channel according to a first set of rules and a second set of rules, the CLI report indicating one or more CLI measurements performed by the UE. The operations of 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed as described in reference to Fig.12 The reporting component 1230 is used to execute.

[0250] Fig.18A flow chart illustrating a method 1800 for supporting CLI reporting on a physical uplink channel according to one or more aspects of the present disclosure is shown. The operations of the method 1800 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1800 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 5 as well as Figures 10 to 13 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0251] At 1805, the method may include sending a first message indicating a CLI reporting configuration associated with a first rule set for determining an amount of resources for multiplexing CLI reports on a physical uplink channel and a second rule set for multiplexing CLI reports on a physical uplink channel via the amount of resources. The operations of 1805 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1805 may be performed as described in reference to Fig.12 The configuration instructs component 1225 to execute.

[0252] At 1810, the method may include sending a second message that triggers the UE to report one or more CLI measurements and includes an offset indicator. The operations of 1810 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1810 may be performed as described in reference to Fig.12 The report triggers component 1235 to execute.

[0253] At 1815, the method may include receiving a CLI report on a physical uplink channel according to a first set of rules and a second set of rules, the CLI report indicating one or more CLI measurements performed by the UE, wherein receiving the CLI report is based on receiving a second message, and wherein the amount of resources is based on one or more CLI offset values ​​indicated by the offset indicator. The operations of 1815 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1815 may be performed as described in reference to Fig.12 The reporting component 1230 is used to execute.

[0254] Fig.19 A flow chart illustrating a method 1900 for supporting CLI reporting on a physical uplink channel according to one or more aspects of the present disclosure is shown. The operations of the method 1900 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1900 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 5 as well as Figures 10 to 13In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0255] At 1905, the method may include sending a first message indicating a CLI reporting configuration associated with a first rule set for determining an amount of resources for multiplexing CLI reports on a physical uplink channel and a second rule set for multiplexing CLI reports on a physical uplink channel via the amount of resources. The operations of 1905 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1905 may be performed as described in reference to Fig.12 The configuration instructs component 1225 to execute.

[0256] At 1910, the method may include sending a second message indicating one or more CLI offset values, wherein the amount of resources is based on the one or more CLI offset values. The operations of 1910 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1910 may be performed as described in reference to Fig.12 The offset value instructs component 1240 to execute.

[0257] At 1915, the method may include sending a third message that triggers the UE to report one or more CLI measurements, wherein the third message is common to a group of two or more UEs including the UE. The operations of 1915 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1915 may be performed as described in reference to Fig.12 The report triggers component 1235 to execute.

[0258] At 1920, the method may include receiving a CLI report on a physical uplink channel according to a first set of rules and a second set of rules, the CLI report indicating one or more CLI measurements performed by the UE, and wherein receiving the CLI report is based on a third message. The operations of 1920 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1920 may be performed as described in reference to Fig.12 The reporting component 1230 is used to execute.

[0259] The following provides an overview of various aspects of the disclosure:

[0260] Aspect 1: A method for wireless communication at a UE, the method comprising: receiving a first message indicating a CLI report configuration, the CLI report configuration being associated with a first rule set for determining an amount of resources for multiplexing CLI reports on a physical uplink channel and a second rule set for multiplexing the CLI reports on the physical uplink channel via the amount of resources; and sending the CLI report on the physical uplink channel according to the first rule set and the second rule set, the CLI report indicating one or more CLI measurements performed by the UE.

[0261] Aspect 2: According to the method described in Aspect 1, the method also includes: receiving a second message that triggers the UE to report the one or more CLI measurements and includes an offset indicator, wherein sending the CLI report is at least partially based on receiving the second message; and determining one or more CLI offset values ​​based at least partially on the offset indicator, wherein the resource amount is at least partially based on the one or more CLI offset values.

[0262] Aspect 3: The method according to aspect 2, wherein determining the one or more CLI offset values ​​comprises: determining the one or more CLI offset values ​​using the offset indicator and a table including a plurality of CLI offset values.

[0263] Aspect 4: The method according to aspect 2, wherein determining the one or more CLI offset values ​​comprises: calculating the one or more CLI offset values ​​using a difference value from one or more CSI offset values.

[0264] Aspect 5: The method according to aspect 4, wherein the CLI reporting configuration includes an indication of the difference value, and calculating the one or more CLI offset values ​​is based at least in part on receiving the first message.

[0265] Aspect 6: The method according to any one of aspects 2 to 5, wherein the one or more CLI offset values ​​are different from one or more CSI offset values.

[0266] Aspect 7: According to the method according to Aspect 1, the method also includes: receiving a second message indicating one or more CLI offset values, wherein the resource amount is at least partially based on the one or more CLI offset values; and receiving a third message that triggers the UE to report the one or more CLI measurements, wherein the third message is common to a group of two or more UEs including the UE, and wherein sending the CLI report is at least partially based on receiving the third message.

[0267] Aspect 8: The method according to aspect 7, wherein the third message includes an offset indicator, and determining the one or more CLI offset values ​​is further based at least in part on the offset indicator.

[0268] Aspect 9: According to any one of Aspects 1 to 8, the method further includes: multiplexing the CLI report on the physical uplink channel via the resource amount based at least in part on the second rule set, the physical uplink channel including PUSCH, wherein sending the CLI report is based at least in part on the multiplexing.

[0269] Aspect 10: The method according to Aspect 9, wherein multiplexing the CLI report comprises: multiplexing the CLI report after the CSI report.

[0270] Aspect 11: The method according to Aspect 9, wherein multiplexing the CLI report comprises: multiplexing the first part of the CLI report after the first part of the CSI report; and multiplexing the second part of the CLI report after the second part of the CSI report.

[0271] Aspect 12: According to the method described in any one of Aspects 1 to 8, the method further includes: receiving a second message instructing the UE to multiplex the CLI report with feedback information; and multiplexing the CLI report with the feedback information based at least in part on receiving the second message, the physical uplink channel including PUCCH, wherein sending the CLI report is based at least in part on the multiplexing.

[0272] Aspect 13: According to the method according to Aspect 12, the method also includes: receiving a third message instructing the UE to multiplex the CLI report with the CSI report, wherein multiplexing the CLI report with the feedback information includes multiplexing the CLI report with the feedback information and the CSI report at least partially based on receiving the second message and the third message.

[0273] Aspect 14: The method according to aspect 13, wherein the CLI report is multiplexed after the first part of the CSI report and the feedback information.

[0274] Aspect 15: A method according to Aspect 13, wherein multiplexing the CLI report with the feedback information and the CSI report includes: multiplexing the CLI report with the feedback information and the CSI report according to an ordering based at least in part on the respective priorities of the CLI report and the CSI report.

[0275] Aspect 16: A method according to Aspect 13, wherein multiplexing the CLI report with the feedback information and the CSI report includes: multiplexing the feedback information, the first part of the CSI report and the first part of the CLI report; and discarding at least the second part of the CLI report.

[0276] Aspect 17: A method for wireless communication at a network entity, the method comprising: sending a first message indicating a CLI report configuration, the CLI report configuration being associated with a first set of rules for determining an amount of resources for multiplexing CLI reports on a physical uplink channel and a second set of rules for multiplexing the CLI reports on the physical uplink channel via the amount of resources; and receiving the CLI report on the physical uplink channel according to the first set of rules and the second set of rules, the CLI report indicating one or more CLI measurements performed by a UE.

[0277] Aspect 18: According to the method according to Aspect 17, the method also includes: sending a second message that triggers the UE to report the one or more CLI measurements and includes an offset indicator, wherein receiving the CLI report is at least partially based on receiving the second message, and wherein the amount of resources is at least partially based on one or more CLI offset values ​​indicated by the offset indicator.

[0278] Aspect 19: The method according to aspect 18, wherein the one or more CLI offset values ​​indicated by the offset indicator correspond to CLI offset values ​​included in a table.

[0279] Aspect 20: The method according to aspect 18, wherein the one or more CLI offset values ​​indicated by the offset indicator are based at least in part on differences from one or more CSI offset values.

[0280] Aspect 21: The method according to Aspect 20, wherein the CLI reporting configuration includes an indication of the difference.

[0281] Aspect 22: The method according to any one of aspects 18 to 21, wherein the one or more CLI offset values ​​are different from one or more CSI offset values.

[0282] Aspect 23: According to the method according to Aspect 17, the method also includes: sending a second message indicating one or more CLI offset values, wherein the resource amount is at least partially based on the one or more CLI offset values; and sending a third message triggering the UE to report the one or more CLI measurements, wherein the third message is common to a group of two or more UEs including the UE, and wherein receiving the CLI report is at least partially based on the third message.

[0283] Aspect 24: The method according to aspect 23, wherein the third message includes an offset indicator, and the one or more CLI offset values ​​are based at least in part on the offset indicator.

[0284] Aspect 25: The method according to any one of aspects 17 to 24, wherein the CLI report is multiplexed on the physical uplink channel via the amount of resources after the CSI report and based at least in part on the second rule set.

[0285] Aspect 26: A method according to any one of Aspects 17 to 24, wherein the first part of the CLI report is multiplexed on the physical uplink channel via the resource amount after the first part of the CSI report and at least partially based on the second rule set, and the second part of the CLI report is multiplexed on the physical uplink channel via the resource amount after the second part of the CSI report.

[0286] Aspect 27: According to any one of Aspects 17 to 24, the method further includes: sending a second message instructing the UE to multiplex the CLI report with feedback information, wherein the CLI report is multiplexed with the feedback information at least in part based on the second message.

[0287] Aspect 28: According to the method according to Aspect 27, the method also includes: sending a third message instructing the UE to multiplex the CLI report with the CSI report, wherein the CLI report is multiplexed with the feedback information and the CSI report at least in part based on the third message.

[0288] Aspect 29: The method according to aspect 28, wherein the CLI report is multiplexed after the first part of the CSI report and the feedback information.

[0289] Aspect 30: The method according to aspect 28, wherein the CLI report is multiplexed with the feedback information and the CSI report according to an ordering based at least in part on respective priorities of the CLI report and the CSI report.

[0290] Aspect 31: The method according to aspect 28, wherein the feedback information, the first part of the CSI report and the first part of the CLI report are multiplexed on the physical uplink channel, and at least a part of the second part of the CLI report is discarded.

[0291] Aspect 32: An apparatus for performing wireless communications at a UE, the apparatus comprising a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 1 to 16.

[0292] Aspect 33: An apparatus for wireless communication at a UE, the apparatus comprising at least one means for performing a method according to any one of aspects 1 to 16.

[0293] Aspect 34: A non-transitory computer-readable medium storing a code for wireless communication at a UE, the code comprising instructions executable by a processor to perform a method according to any one of aspects 1 to 16.

[0294] Aspect 35: An apparatus for wireless communication at a network entity, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 17 to 31.

[0295] Aspect 36: An apparatus for wireless communication at a network entity, the apparatus comprising at least one means for performing the method according to any one of aspects 17 to 31.

[0296] Aspect 37: A non-transitory computer-readable medium storing code for wireless communication at a network entity, the code comprising instructions executable by a processor to perform the method according to any one of aspects 17 to 31.

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

[0298] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0299] The information and signals described herein may be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the specification may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0300] The various illustrative blocks and components described in conjunction 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 an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0301] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. When implemented in software executed by a processor, the functions may be stored as one or more instructions or codes on a computer-readable medium, or sent on a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or any combination of these items. Features that implement the functions may also be physically located at different locations, including being distributed so that the various parts of the functions are implemented at different physical locations.

[0302] Computer-readable medium includes both non-transient computer storage medium and communication medium, and it includes any medium that facilitates computer program to be transported from one place to another.Non-transient storage medium can be any available medium that can be accessed by general or special-purpose computer.By way of example and not limitation, non-transient computer-readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage device, disk storage device or other magnetic storage device, or can be used for carrying or storing desired program code member and can be accessed by general or special-purpose computer or general or special-purpose processor in the form of instruction or data structure Any other non-transient medium.Moreover, any connection is appropriately referred to as computer-readable medium.For example, if software is sent from website, server or other remote source using coaxial cable, optical fiber cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, optical fiber cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, includes 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.

[0303] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items followed by a phrase such as "at least one of" or "one or more 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 FEC AB or AC or BC or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on."

[0304] The term "determining" encompasses a variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or other data structure), ascertaining, and similar actions. Additionally, "determining" may include receiving (such as receiving information), accessing (such as accessing data in a memory), and similar actions. Additionally, "determining" may include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.

[0305] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label to distinguish between the similar components. If only the first reference label is used in the specification, the description may apply to any of the similar components having the same first reference label regardless of the second reference label, or other subsequent reference labels.

[0306] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "having advantages over other examples." The specific implementation includes specific details to provide an understanding of the technology. However, the technologies 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 examples.

[0307] The description herein is provided to enable one of ordinary skill in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Therefore, the present disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for wireless communication at a user equipment (UE), the method comprising: receiving a first message indicating a cross-link interference reporting configuration associated with a first set of rules for determining an amount of resources for multiplexing cross-link interference reports on a physical uplink channel and a second set of rules for multiplexing the cross-link interference reports on the physical uplink channel via the amount of resources; as well as The cross-link interference report is sent on the physical uplink channel according to the first set of rules and the second set of rules, the cross-link interference report indicating one or more cross-link interference measurements performed by the UE.

2. The method according to claim 1, further comprising: receiving a second message that triggers the UE to report the one or more cross-link interference measurements and includes an offset indicator, wherein sending the cross-link interference report is based at least in part on receiving the second message; as well as One or more cross-link interference offset values ​​are determined based at least in part on the offset indicator, wherein the amount of resources is based at least in part on the one or more cross-link interference offset values.

3. The method of claim 2, wherein determining the one or more cross-link interference offset values ​​comprises: The one or more cross-link interference offset values ​​are determined using the offset indicator and a table including a plurality of cross-link interference offset values.

4. The method of claim 2, wherein determining the one or more cross-link interference offset values ​​comprises: The one or more cross-link interference offset values ​​are calculated using differences from one or more channel state information offset values.

5. The method of claim 4, wherein the cross-link interference reporting configuration includes an indication of the difference value, and calculating the one or more cross-link interference offset values ​​is based at least in part on receiving the first message.

6. The method of claim 2, wherein the one or more cross-link interference offset values ​​are different from one or more channel state information offset values.

7. The method according to claim 1, further comprising: receiving a second message indicating one or more cross-link interference offset values, wherein the amount of resources is based at least in part on the one or more cross-link interference offset values; as well as A third message is received that triggers the UE to report the one or more cross-link interference measurements, wherein the third message is common to a group of two or more UEs including the UE, and wherein sending the cross-link interference report is based at least in part on receiving the third message.

8. The method of claim 7, wherein the third message includes an offset indicator, and determining the one or more cross-link interference offset values ​​is further based at least in part on the offset indicator.

9. The method according to claim 1, further comprising: The cross-link interference reports are multiplexed on the physical uplink channel via the amount of resources based at least in part on the second rule set, the physical uplink channel comprising a physical uplink shared channel, wherein sending the cross-link interference reports is based at least in part on the multiplexing.

10. The method of claim 9, wherein multiplexing the cross-link interference reports comprises: The cross-link interference report is multiplexed after the channel state information report.

11. The method of claim 9, wherein multiplexing the cross-link interference reports comprises: multiplexing the first part of the cross-link interference report after the first part of the channel state information report; as well as The second portion of the cross-link interference report is multiplexed after the second portion of the channel state information report.

12. The method according to claim 1, further comprising: receiving a second message instructing the UE to multiplex the cross-link interference report with feedback information; as well as The cross-link interference report is multiplexed with the feedback information based at least in part on receiving the second message, the physical uplink channel comprising a physical uplink control channel, wherein sending the cross-link interference report is based at least in part on the multiplexing.

13. The method according to claim 12, further comprising: Receiving a third message instructing the UE to multiplex the cross-link interference report with a channel state information report, wherein multiplexing the cross-link interference report with the feedback information comprises: The cross-link interference report is multiplexed with the feedback information and the channel state information report based at least in part on receiving the second message and the third message.

14. The method of claim 13, wherein the cross-link interference report is multiplexed after the first part of the channel state information report and the feedback information.

15. The method of claim 13, wherein multiplexing the cross-link interference report with the feedback information and the channel state information report comprises: The cross-link interference report is multiplexed with the feedback information and the channel state information report according to an ordering based at least in part on respective priorities of the cross-link interference report and the channel state information report.

16. The method of claim 13, wherein multiplexing the cross-link interference report with the feedback information and the channel state information report comprises: multiplexing the feedback information, the first part of the channel state information report, and the first part of the cross-link interference report; as well as At least a second portion of the cross-link interference report is discarded.

17. A method for wireless communication at a network entity, the method comprising: sending a first message indicating a cross-link interference reporting configuration associated with a first set of rules for determining an amount of resources for multiplexing cross-link interference reports on a physical uplink channel and a second set of rules for multiplexing the cross-link interference reports on the physical uplink channel via the amount of resources; as well as The cross-link interference report is received on the physical uplink channel according to the first set of rules and the second set of rules, the cross-link interference report indicating one or more cross-link interference measurements performed by a user equipment (UE).

18. The method according to claim 17, further comprising: Sending a second message that triggers the UE to report the one or more cross-link interference measurements and includes an offset indicator, wherein receiving the cross-link interference report is at least partially based on receiving the second message, and wherein the amount of resources is at least partially based on one or more cross-link interference offset values ​​indicated by the offset indicator.

19. The method of claim 18, wherein the one or more cross-link interference offset values ​​indicated by the offset indicator correspond to cross-link interference offset values ​​included in a table.

20. The method of claim 18, wherein the one or more cross-link interference offset values ​​indicated by the offset indicator are based at least in part on differences from one or more channel state information offset values.

21. The method of claim 20, wherein the cross-link interference reporting configuration includes an indication of the difference.

22. The method according to claim 17, further comprising: sending a second message indicating one or more cross-link interference offset values, wherein the amount of resources is based at least in part on the one or more cross-link interference offset values; as well as A third message is sent that triggers the UE to report the one or more cross-link interference measurements, wherein the third message is common to a group of two or more UEs including the UE, and wherein receiving the cross-link interference report is based at least in part on the third message.

23. The method of claim 22, wherein the third message includes an offset indicator, and the one or more cross-link interference offset values ​​are based at least in part on the offset indicator.

24. The method of claim 17, wherein the cross-link interference report is multiplexed on the physical uplink channel via the amount of resources after a channel state information report and based at least in part on the second set of rules.

25. A method according to claim 17, wherein the first part of the cross-link interference report is multiplexed on the physical uplink channel via the resource amount after the first part of the channel state information report and at least partially based on the second rule set, and the second part of the cross-link interference report is multiplexed on the physical uplink channel via the resource amount after the second part of the channel state information report.

26. The method according to claim 17, further comprising: A second message is sent instructing the UE to multiplex the cross-link interference report with feedback information, wherein the cross-link interference report is multiplexed with the feedback information based at least in part on the second message.

27. The method according to claim 26, further comprising: A third message is sent instructing the UE to multiplex the cross-link interference report with a channel state information report, wherein the cross-link interference report is multiplexed with the feedback information and the channel state information report based at least in part on the third message.

28. The method of claim 27, wherein the cross-link interference report is multiplexed with the feedback information and the channel state information report according to an ordering based at least in part on respective priorities of the cross-link interference report and the channel state information report.

29. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: processor; a memory coupled to the processor; as well as instructions stored in the memory and executable by the processor to cause the apparatus to: receiving a first message indicating a cross-link interference reporting configuration associated with a first set of rules for determining an amount of resources for multiplexing cross-link interference reports on a physical uplink channel and a second set of rules for multiplexing the cross-link interference reports on the physical uplink channel via the amount of resources; as well as The cross-link interference report is sent on the physical uplink channel according to the first set of rules and the second set of rules, the cross-link interference report indicating one or more cross-link interference measurements performed by the UE.

30. An apparatus for wireless communication at a network entity, the apparatus comprising: processor; a memory coupled to the processor; as well as instructions stored in the memory and executable by the processor to cause the apparatus to: sending a first message indicating a cross-link interference reporting configuration associated with a first set of rules for determining an amount of resources for multiplexing cross-link interference reports on a physical uplink channel and a second set of rules for multiplexing the cross-link interference reports on the physical uplink channel via the amount of resources; as well as The cross-link interference report is received on the physical uplink channel according to the first set of rules and the second set of rules, the cross-link interference report indicating one or more cross-link interference measurements performed by a user equipment (UE).

Images