Coexistence interference mitigation in sidelink devices

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) may receive report information indicating in-device coexistence (IDC) interference from a second UE. The UE may receive, from the second UE, a resource reservation message indicating a set of sidelink resources, and transmit, according to the report information, an IDC interference report to the second UE, the IDC interference report indicating IDC interference corresponding to at least a portion of the set of sidelink resources.

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. patent application No. 18 / 176,460, filed by Elazzouni et al. on February 28, 2023, entitled “SIDELINK IN-DEVICE CO-EXISTENCE INTERFERENCE MITIGATION,” which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0003] The following relates to wireless communications, including sidelink in-device coexistence (IDC) interference mitigation. Background Art

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, and more. These systems can 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, LTE-Advanced (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 technologies 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). A wireless multiple-access communication system may include one or more base stations, each of which supports wireless communication for communication devices, which may be referred to as user equipment (UE). Summary of the Invention

[0005] The described techniques relate to improved methods, systems, devices, and apparatuses for supporting sidelink in-device coexistence (IDC) interference mitigation. For example, a user equipment (UE) may detect and report IDC interference affecting sidelink communications, and a transmitting device may schedule resources for sidelink communications based on the reported IDC interference (e.g., resources may be scheduled to avoid using resources affected by the IDC interference). In some examples (e.g., when the UE is operating in autonomous resource selection mode), a receiving UE may receive configuration information from a transmitting UE indicating parameters for reporting IDC interference to the transmitting UE. The receiving UE may detect the IDC interference and subsequently send an IDC interference report to the transmitting UE. The transmitting UE may configure the report via radio resource control (RRC) signaling or as a measurement object (e.g., sidelink assistance information, sidelink measurement object, inter-UE coordination information, etc.). The receiving UE may send the IDC interference report as part of higher layer signaling (RRC signaling), radio link failure, etc. The receiving UE may report specific subchannels, resource pools, channels, etc., that are experiencing IDC interference. The sending UE may reserve subsequent sidelink resources to avoid using the indicated resources.

[0006] In some examples (e.g., when a UE is operating in a mode where a network entity schedules resources for sidelink transmissions), the transmitting UE, the receiving UE, or both may report IDC interference to the network entity, which may prevent the indicated resources from being used for future sidelink grants. The UE may send the IDC interference report to the network entity via RRC signaling, UE assistance information during network configuration, or two UEs may communicate with each other, and one UE may send the identified IDC interference to the network entity. In some cases, the IDC interference report may indicate interference affecting a specific radio access technology (RAT). In some examples, the UE may report power coexistence solutions to the network entity.

[0007] A method for wireless communication at a first user equipment (UE) is described. The method may include receiving report information indicating in-device coexistence interference from a second UE; receiving a resource reservation message indicating a set of sidelink resources from the second UE; and sending an in-device coexistence interference report to the second UE based on the report information, the in-device coexistence interference report indicating in-device coexistence interference corresponding to at least a portion of the set of sidelink resources.

[0008] An apparatus for wireless communication at a first UE is described. The apparatus may include: a processor; a memory coupled to the processor; and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: receive report information indicating in-device coexistence interference from a second UE; receive a resource reservation message indicating a set of sidelink resources from the second UE; and send an in-device coexistence interference report to the second UE based on the report information, the in-device coexistence interference report indicating in-device coexistence interference corresponding to at least a portion of the set of sidelink resources.

[0009] Another apparatus for wireless communication at a first UE is described. The apparatus may include: means for receiving report information from a second UE, the report information indicating in-device coexistence interference; means for receiving a resource reservation message from the second UE, the resource reservation message indicating a set of sidelink resources; and means for sending an in-device coexistence interference report to the second UE based on the report information, the in-device coexistence interference report indicating in-device coexistence interference corresponding to at least a portion of the set of sidelink resources.

[0010] A non-transitory computer-readable medium storing code for wireless communication at a first UE is described. The code may include instructions executable by a processor to: receive report information indicating in-device coexistence interference from a second UE; receive a resource reservation message indicating a set of sidelink resources from the second UE; and send an in-device coexistence interference report to the second UE based on the report information, the in-device coexistence interference report indicating in-device coexistence interference corresponding to at least a portion of the set of sidelink resources.

[0011] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the reporting information may include operations, features, components, or instructions for receiving sidelink RRC signaling including the reporting information, wherein the reporting information includes an indication that in-device coexistence interference reporting by the first UE can be enabled.

[0012] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving, in sidelink RRC signaling, an indication of a center frequency around which the first UE may be requested to report in-device coexistence interference, an indication of a sidelink resource pool for reporting in-device coexistence interference, an indication of one or more subchannels associated with reporting in-device coexistence interference, an indication of one or more active sidelink bandwidth portions or inactive sidelink bandwidth portions corresponding to in-device coexistence interference, or any combination thereof.

[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving report information may include operations, features, components, or instructions for receiving a measurement object configuration message, a sidelink assistance information message, or an inter-UE coordination information message.

[0014] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending, in an in-device coexistence interference report, an indication of one or more carrier frequencies, one or more sidelink bandwidth portions, one or more sidelink resource pools, one or more sidelink subchannels, one or more sidelink physical resource blocks, frequency resource ranges, or any combination thereof, that are affected by in-device coexistence interference.

[0015] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending an in-device coexistence interference report may include operations, features, components, or instructions for sending an indication of a link failure associated with the set of side link resources due to in-device coexistence interference.

[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 an event-triggered measurement object configuration in a report information; and detecting in-device coexistence interference based on monitoring the set of sidelink resources according to the event-triggered measurement object configuration, wherein sending the in-device coexistence interference report includes sending a medium access control (MAC) control element (CE) based on detecting the in-device coexistence interference.

[0017] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending an in-device coexistence interference report may include operations, features, components, or instructions for groupcasting the in-device coexistence interference report to a group of multiple sidelink UEs including a second UE.

[0018] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending an in-device coexistence interference report may include operations, features, components, or instructions for sending an inter-UE coordination message that includes an indication that a set of multiple side link resources including at least the portion of the set of side link resources may be non-preferred resources.

[0019] 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 request for an indication of non-preferred resources from a second UE, wherein sending the inter-UE coordination message may be based on receiving the request.

[0020] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving configuration information indicating one or more conditions upon which sending the inter-UE coordination message may be based.

[0021] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving an indication from a second UE that the second UE may be capable of receiving an inter-UE coordination message, wherein sending the inter-UE coordination message may be based on receiving the indication that the second UE may be capable of receiving the inter-UE coordination message.

[0022] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending, in an inter-UE coordination message, an indication of a first subset of the set of multiple sidelink resources that may be non-preferred due to in-device coexistence interference.

[0023] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: monitoring sidelink signaling from a second UE based on a resource reservation message; and detecting in-device coexistence interference on at least the portion of the set of sidelink resources based on the monitoring, wherein sending an in-device coexistence interference report may be based on detecting the in-device coexistence interference.

[0024] A method for wireless communication at a first UE is described. The method may include receiving a resource reservation message from a network entity, the resource reservation message indicating a set of sidelink resources for performing sidelink communication with at least a second UE; communicating with the second UE according to the resource reservation message; and sending an in-device coexistence interference report to the network entity based on performing the sidelink communication, the in-device coexistence interference report indicating in-device coexistence interference corresponding to at least a portion of the set of sidelink resources.

[0025] An apparatus for wireless communication at a first UE is described. The apparatus may include: a processor; a memory coupled to the processor; and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: receive a resource reservation message from a network entity, the resource reservation message indicating a set of sidelink resources for performing sidelink communication with at least a second UE; communicate with the second UE based on the resource reservation message; and send an in-device coexistence interference report to the network entity based on performing the sidelink communication, the in-device coexistence interference report indicating in-device coexistence interference corresponding to at least a portion of the set of sidelink resources.

[0026] Another apparatus for wireless communication at a first UE is described. The apparatus may include: means for receiving a resource reservation message from a network entity, the resource reservation message indicating a set of sidelink resources for performing sidelink communication with at least a second UE; means for communicating with the second UE based on the resource reservation message; and means for sending an in-device coexistence interference report to a network entity based on performing the sidelink communication, the in-device coexistence interference report indicating in-device coexistence interference corresponding to at least a portion of the set of sidelink resources.

[0027] A non-transitory computer-readable medium storing code for wireless communication at a first UE is described. The code may include instructions executable by a processor to: receive a resource reservation message from a network entity, the resource reservation message indicating a set of sidelink resources for performing sidelink communication with at least a second UE; communicate with the second UE based on the resource reservation message; and send an in-device coexistence interference report to the network entity based on performing the sidelink communication, the in-device coexistence interference report indicating in-device coexistence interference corresponding to at least a portion of the set of sidelink resources.

[0028] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending an in-device coexistence interference report may include operations, features, components, or instructions for sending an RRC message that includes an indication that at least the portion of the set of sidelink resources is experiencing in-device coexistence interference.

[0029] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending an in-device coexistence interference report may include operations, features, components, or instructions for sending a UE assistance information message that includes an indication that at least the portion of the set of sidelink resources is experiencing in-device coexistence interference.

[0030] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving an indication of in-device coexistence interference from a second UE, wherein sending the in-device coexistence interference report includes forwarding the indication of in-device coexistence interference to a network entity.

[0031] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending an in-device coexistence interference report may include operations, features, components, or instructions for sending an indication of in-device coexistence interference impact on wireless communications via a second radio access technology associated with the set of sidelink resources of the first radio access technology.

[0032] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending, in an in-device coexistence interference report, an indication of one or more carrier frequencies, one or more sidelink bandwidth portions, one or more sidelink resource pools, one or more sidelink subchannels, one or more sidelink physical resource blocks, frequency resource ranges, or any combination thereof, that are affected by in-device coexistence interference. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] Figure 1 An example of a wireless communication system supporting sidelink in-device coexistence (IDC) interference mitigation in accordance with one or more aspects of the present disclosure is illustrated.

[0034] Figure 2 An example of a wireless communication system supporting sidelink IDC interference mitigation according to one or more aspects of the present disclosure is illustrated.

[0035] Figure 3 An example of a timeline supporting sidelink IDC interference mitigation in accordance with one or more aspects of the present disclosure is illustrated.

[0036] Figure 4 An example of a wireless communication system supporting sidelink IDC interference mitigation according to one or more aspects of the present disclosure is illustrated.

[0037] Figure 5 An example of a process flow supporting sidelink IDC interference mitigation in accordance with one or more aspects of the present disclosure is illustrated.

[0038] Figure 6 An example of a process flow supporting sidelink IDC interference mitigation in accordance with one or more aspects of the present disclosure is illustrated.

[0039] Figure 7 An example of a process flow supporting sidelink IDC interference mitigation in accordance with one or more aspects of the present disclosure is illustrated.

[0040] Figure 8 and Figure 9 A block diagram illustrating a device supporting sidelink IDC interference mitigation according to one or more aspects of the present disclosure is illustrated.

[0041] Figure 10 A block diagram of a communication manager supporting sidelink IDC interference mitigation according to one or more aspects of the present disclosure is illustrated.

[0042] Figure 11 A diagram illustrating a system including a device supporting sidelink IDC interference mitigation in accordance with one or more aspects of the present disclosure is illustrated.

[0043] Figures 12 to 15 A flow chart illustrating a method of supporting sidelink IDC interference mitigation according to one or more aspects of the present disclosure is illustrated. DETAILED DESCRIPTION

[0044] In some examples, devices (e.g., user equipment (UE)) may experience in-device coexistence (IDC) interference. For example, the UE may support various types of communications, including fourth generation (4G) technologies such as Long Term Evolution (LTE), LTE-Advanced (LTE-A), or LTE-A Pro, fifth generation (5G) technologies, which may be referred to as New Radio (NR), and other wireless technologies such as Wi-Fi or Bluetooth. 4G and 5G technologies may include sidelink communications for direct communication between UEs. Sidelink communications may be performed according to a first mode (e.g., Mode 1) in which a network entity schedules sidelink resources for communication between sidelink UEs, or a second mode (e.g., Mode 2) in which a transmitting sidelink UE reserves sidelink resources (e.g., from a configured resource pool) for communication with a receiving sidelink UE.

[0045] Some radio transceivers at a UE may be very close to each other. The transmit power of a transmitting device may be higher than the receive power of a signal from another device. Additionally or alternatively, for some coexistence scenarios (e.g., different radio technologies operating on adjacent frequencies within the same UE), the filtering process may not be able to adequately avoid or mitigate interference across adjacent frequencies, between adjacent radio transceivers, etc. In some examples, the UE may not be able to resolve or minimize IDC interference in real time. Without a mechanism to indicate or report problematic frequency resources on which IDC interference is experienced, some wireless communications (e.g., sidelink communications) may fail, resulting in increased retransmissions, inefficient use of available system resources, increased system latency, and a reduced user experience.

[0046] As described herein, a UE may detect and report IDC interference affecting sidelink communications, and a transmitting device may schedule resources for sidelink communications based on the reported IDC interference (e.g., resources may be scheduled to avoid using resources affected by the IDC interference). In some examples described herein (e.g., when the UE operates in Mode 2), a receiving UE may receive configuration information from a transmitting UE indicating parameters for reporting IDC interference to the transmitting UE. The receiving UE may detect the IDC interference and subsequently send an IDC interference report to the transmitting UE. The transmitting UE may configure the report via radio resource control (RRC signaling) or as a measurement object (e.g., sidelink assistance information, sidelink measurement object, inter-UE coordination information, etc.). The receiving UE may send the IDC interference report as part of upper layer signaling (RRC signaling), radio link failure, etc. The receiving UE may report specific subchannels, resource pools, channels, etc. that are experiencing IDC interference. The transmitting UE may reserve subsequent sidelink resources to avoid using the indicated resources.

[0047] In some examples (e.g., when the UE is operating in Mode 1), the transmitting UE, the receiving UE, or both may report the IDC interference to the network entity, which may avoid the indicated resources from being used for future sidelink grants. The UE may send the IDC interference report to the network entity via RRC signaling, UE assistance information during network configuration, or two UEs may communicate with each other and one UE may send the identified IDC interference to the network entity. In some cases, the IDC interference report may indicate interference affecting a specific radio access technology (RAT). In some examples, the UE may report a power coexistence solution to the network entity (e.g., the UE may indicate to the network entity that the UE will change power settings (such as transmit power) to mitigate IDC interference, the UE supports IDC interference reporting based on transmit power changes, etc.).

[0048] Various aspects of the present disclosure are first described in the context of a wireless communication system. Aspects of the present disclosure are further illustrated and described with reference to wireless communication systems, timelines, and process flows. Aspects of the present disclosure are further illustrated and described with reference to apparatus diagrams, system diagrams, and flow charts related to sidelink IDC interference mitigation.

[0049] Figure 1An example of a wireless communication system 100 that supports sidelink IDC interference mitigation 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 LTE-Advanced (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.

[0050] 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 various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, among other nomenclature. In some examples, the network entities 105 and the UEs 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entities 105 may support a coverage area 110 (e.g., a geographic coverage area) within which the UEs 115 and the network entities 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area within which the network entities 105 and the UEs 115 may support signal communication based on one or more radio access technologies (RATs).

[0051] 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 both stationary and mobile at different times. The UEs 115 may be devices that take different forms or have different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. The UEs 115 described herein may be capable of supporting communication with various types of devices, such as Figure 1 105) as shown.

[0052] As described herein, a node of wireless communication system 100 (which may be referred to as a network node or 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 UE 115. As another example, the node may be 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 UE 115, the second node may be network entity 105, and the third node may be UE 115. In another aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be network entity 105. In 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, a 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.

[0053] In some examples, network entities 105 can communicate with core network 130, with each other, or both. For example, network entities 105 can communicate with 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, network entities 105 can communicate with each other via backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols) directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130). In some examples, network entities 105 can communicate with each other via midhaul communication links 162 (e.g., according to a midhaul interface protocol) or fronthaul communication links 168 (e.g., according to a fronthaul interface protocol), or any combination thereof. Backhaul communication links 120, midhaul communication links 162, or fronthaul communication links 168 can be or include one or more wired links (e.g., electrical links, fiber optic 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 .

[0054] 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 base transceiver station, a radio base station, an NR base station, an access point, a radio transceiver, a Node B, an eNodeB (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 eNodeB, or other suitable terminology). In some examples, the network entity 105 (e.g., the base station 140) may be implemented in a converged (e.g., monolithic, stand-alone) base station architecture that may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as the base station 140).

[0055] In some examples, the network entity 105 can be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that can 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 can 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, smart radio head, remote radio head (RRH), remote radio unit (RRU), or transmit receive point (TRP). One or more components of the network entity 105 in the disaggregated 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 disaggregated RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0056] The functional split between CU 160, DU 165, and RU 170 is flexible and can support different functions 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, or RU 170. For example, a functional split of the protocol stack can be employed between CU 160 and DU 165, such that CU 160 can support one or more layers of the protocol stack and DU 165 can support one or more different layers of the protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functions and signaling (e.g., Radio Resource Control (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 the CU 160 and the DU 165 or between the DU 165 and the RU 170 can be within the protocol layer (e.g., some functions of the protocol layer can be performed by one of the CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by a different one of the CU 160, DU 165, or RU 170). The CU 160 can be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. The CU 160 can be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and the DU 165 can be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., an open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented according to interfaces (eg, channels) between layers of a protocol stack supported by respective network entities 105 communicating via these communication links.

[0057] In some wireless communication systems (e.g., wireless communication system 100), the infrastructure and spectrum resources used 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 one another. One or more IAB nodes 104 may be referred to as a donor entity or IAB donor. One or more DUs 165 or one or more RUs 170 may be partially controlled by one or more CUs 160 associated with a donor network entity 105 (e.g., 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 link 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by the coupled IAB donor's DU 165. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas 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 disaggregated 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.

[0058] For example, an access network (AN) or RAN may include communications between an access node (e.g., an IAB donor), IAB node 104, and one or more UEs 115. The IAB donor may facilitate connectivity between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). In other words, the IAB donor may refer to a RAN node with a wired or wireless connection to the core network 130. The IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170). In this case, the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and IAB node 104 may communicate via the F1 interface according to a protocol that defines signaling messages (e.g., the F1 AP protocol). Additionally or alternatively, CU 160 may communicate with the core network via an interface (which may be an example of part of a backhaul link) and may communicate with other CUs 160 (e.g., CUs 160 associated with alternative IAB donors) via an Xn-C interface (which may be an example of part of a backhaul link).

[0059] An IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, wireless self-backhaul capabilities, etc.). A DU 165 may act as a distributed scheduling node for child nodes associated with the IAB node 104, and an IAB-MT may act as a scheduled node for a parent node associated with the IAB node 104. In other words, an IAB donor may be referred to as a parent node that communicates with one or more child nodes (e.g., the IAB donor may relay UE transmissions through one or more other IAB nodes 104). Additionally or alternatively, depending on the relay chain or configuration of the AN, an IAB node 104 may also be referred to as a parent node or child node of other IAB nodes 104. Thus, the IAB-MT entity of an IAB node 104 may provide a Uu interface for child IAB nodes 104 to receive signaling from the parent IAB node 104, and a DU interface (e.g., DU 165) may provide a Uu interface for the parent IAB node 104 to signal to child IAB nodes 104 or UE 115.

[0060] For example, IAB node 104 may be referred to as a parent node supporting communications for child IAB nodes, or as a child IAB node associated with an IAB donor, or both. The IAB donor may include a CU 160 having a wired or wireless connection to the core network 130 (e.g., backhaul communication link 120) and may serve as a parent node for IAB node 104. For example, the DU 165 of the IAB donor may relay transmissions to UE 115 via IAB node 104, or may directly signal the transmissions to UE 115, or both. The CU 160 of the IAB donor may signal the establishment of a communication link to IAB node 104 via the F1 interface, and IAB node 104 may schedule transmissions (e.g., transmissions relayed from the IAB donor to UE 115) via the DU 165. In other words, data may be relayed to and from IAB node 104 via signaling via the NR Uu interface of the MT to IAB node 104. Communications with the IAB node 104 may be scheduled by the DU 165 of the IAB donor, and communications with the IAB node 104 may be scheduled by the DU 165 of the IAB node 104 .

[0061] Where the techniques described herein are applied in the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support sidelink IDC interference mitigation 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 disaggregated RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

[0062] 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 terminology, where "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 appliances or vehicles, meters, etc.

[0063] The UE 115 described herein may be capable of communicating 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.

[0064] UE 115 and network entity 105 may wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" may refer to a set of RF spectrum resources having a physical layer structure that defines the communication link 125. For example, a carrier used for communication link 125 may include a portion of an RF spectrum band (e.g., a bandwidth part (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 operation, user data, or other signaling. The wireless communication system 100 may support communications with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can 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 those devices 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 the network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of the RAN communicating with another device (e.g., directly or via one or more other network entities 105).

[0065] In some examples, such as in a carrier aggregation configuration, a carrier may also have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified according to a channel raster used for discovery by UE 115. A carrier may operate in a standalone mode, in which case initial acquisition and connection by UE 115 may occur via the carrier, or a carrier may operate in a non-standalone mode, in which case a different carrier (e.g., of the same or different radio access technology) is used to anchor the connection.

[0066] The communication link 125 shown in the wireless communication system 100 may include downlink transmissions (e.g., forward link transmissions) from the network entity 105 to the UE 115, uplink transmissions (e.g., return link transmissions) from the UE 115 to the network entity 105, or both, as well as other transmission configurations. A carrier may carry downlink communications or uplink communications (e.g., in an FDD mode) or may be configured to carry both downlink and uplink communications (e.g., in a TDD mode).

[0067] A carrier may be associated with a particular bandwidth of RF spectrum, and in some examples, the carrier bandwidth may be referred to as the "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths for carriers of a particular radio access technology (e.g., 1.4 megahertz (MHz), 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). Devices of the wireless communication system 100 (e.g., the network entity 105, the UE 115, or both) may have a hardware configuration that supports communication using a particular carrier bandwidth, or may be configurable to support communication using one of the set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network entity 105 or a UE 115 that supports concurrent communication using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., a subband, a BWP) or all of the carrier bandwidth.

[0068] The signal waveform transmitted via a carrier wave may include multiple subcarriers (e.g., using a multicarrier modulation (MCM) technique such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In systems employing MCM techniques, a resource element may refer to the 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 number 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 a relatively high number of resource elements (e.g., in a transmission duration) and a relatively high-order modulation scheme may correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communications with UE 115.

[0069] One or more parameter sets for a carrier may be supported, and the parameter set may include subcarrier spacing ( ) and cyclic prefix. A carrier can be divided into one or more BWPs with the same or different parameter sets. In some examples, UE 115 can be configured with multiple BWPs. In some examples, a single BWP for a carrier can be active at a given time, and communications by UE 115 can be constrained to one or more active BWPs.

[0070] The time interval for the network entity 105 or the UE 115 may be expressed in multiples of a basic time unit, which may be, for example, a sampling period. seconds, of which can represent the supported subcarrier spacing, and The supported discrete Fourier transform (DFT) size may be indicated. Time intervals of communication resources may be organized according to radio frames, each of which has a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., in the range of 0 to 1023).

[0071] 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 (e.g., in the time domain) into subframes, 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 appended to the front of each symbol period). In some wireless communication systems 100, the time slot may be further divided into a plurality of mini-slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0072] A subframe, slot, mini-slot, or 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 Transmit Time Interval (TTI). In some examples, the TTI duration (e.g., the number 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)).

[0073] Physical channels may be multiplexed according to various techniques for communication using carriers. For example, physical control channels and physical data channels may be multiplexed using one or more of time division multiplexing (TDM), frequency division multiplexing (FDM), or hybrid TDM-FDM techniques for signaling via downlink carriers. 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 the system bandwidth of a carrier or a subset of that bandwidth. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more of UEs 115 may monitor or search the control region for 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 number 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 multiple UEs 115 and a UE-specific search space set for transmitting control information to a specific UE 115 .

[0074] Network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used to communicate with network entity 105 (e.g., using a carrier) and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other identifier) ​​used to distinguish between adjacent cells. In some examples, a cell may also refer to a coverage area 110 or a portion (e.g., a sector) of coverage area 110 within which the logical communication entity operates. Depending on various factors, such as the capabilities of network entity 105, such cells may range from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be or may include a building, a subset of buildings, or an external space between or overlapping coverage areas 110.

[0075] A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access to UEs 115 that have a service subscription with a network provider that supports the macro cell. Compared to a macro cell, a small cell may be associated with a lower-power network entity 105 (e.g., a lower-power base station 140) and may operate using the same or different frequency bands (e.g., licensed or unlicensed) as the macro cell. A small cell may provide unrestricted access to UEs 115 that have a service subscription with the network provider, or may provide restricted access to UEs 115 associated with the small cell (e.g., UEs 115 in a closed subscriber group (CSG) or UEs 115 associated with users in a home or office). A network entity 105 may support one or more cells and may also use one or more component carriers to support communications via the one or more cells.

[0076] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access to different types of devices.

[0077] In some examples, network entities 105 (e.g., base stations 140, RUs 170) can be mobile and, therefore, provide communication coverage for mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies can overlap, but the different coverage areas 110 can be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies can be supported by different network entities 105. The wireless communication system 100 can 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.

[0078] The wireless communication system 100 may support synchronous or asynchronous operation. For synchronous operation, the network entities 105 (e.g., base stations 140) may have similar frame timing, and transmissions from different network entities 105 may be approximately aligned in time. For asynchronous operation, the network entities 105 may have different frame timing, and in some examples, transmissions from different network entities 105 may not be aligned in time. The techniques described herein may be used for both synchronous and asynchronous operation.

[0079] Some UEs 115, such as MTC or IoT devices, may be low-cost or low-complexity devices and may provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technologies that allow devices to communicate with each other or with a network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices with integrated sensors or meters to measure or acquire information and relay such information to a central server or application, which uses the information or presents it to a human interacting with the application. Some UEs 115 may be designed to collect information or enable automated behavior of machines or other equipment. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geographic event monitoring, queue management and tracking, remote security sensing, physical access control, and transaction-based commercial charging.

[0080] Some UEs 115 may be configured to employ a reduced power consumption operating mode, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception, but not concurrent transmission and reception). In some examples, half-duplex communication may be performed at a reduced peak rate. Other power conservation techniques for UEs 115 include entering a power-saving deep sleep mode when not engaged in active communications, operating using limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UEs 115 may be configured to operate using a narrowband protocol type associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a guard band of a carrier, or outside a carrier.

[0081] The wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). The UE 115 may be designed to support ultra-reliable or low-latency or critical functionality. Ultra-reliable communication may include private or group communications and may be supported by one or more services such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functionality 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.

[0082] In some examples, a UE 115 can be configured to support communication 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 performing D2D communication can be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), which can support aspects of such D2D communication configured (e.g., scheduled) by the network entity 105. In some examples, one or more UEs 115 in such a group can be outside of the coverage area 110 of the network entity 105 or can otherwise be unable or not configured to receive transmissions from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication can 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, network entity 105 may facilitate scheduling of resources for D2D communications. In some other examples, D2D communications may be performed between UEs 115 without involving network entity 105.

[0083] In some systems, D2D communication link 135 may be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, vehicles may communicate using vehicle-to-everything (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination thereof. Vehicles may signal information related to traffic conditions, signal scheduling, weather, safety, emergency situations, or any other information relevant to the V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure (such as roadside units) or with the network via one or more network nodes (e.g., network entity 105, base station 140, RU 170) using vehicle-to-network (V2N) communication, or both.

[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, which may be an evolved packet core (EPC) or a 5G core (5GC), may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) for managing access and mobility, and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) for routing packets or interconnecting to external networks. The control plane entities may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management, for UEs 115 served by network entities 105 (e.g., base stations 140) associated with the core network 130. User IP packets may be transferred through the user plane entities, which may provide IP address allocation and other functions. The user plane entities may connect to one or more network operators' IP services 150. 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 can operate using one or more frequency bands that can range from 300 megahertz (MHz) to 300 gigahertz (GHz). Generally speaking, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from approximately one decimeter to one meter in length. UHF waves can be blocked or redirected by buildings and environmental features (which can be referred to as clusters), but these waves can penetrate structures sufficiently for a macrocell to provide service to UEs 115 located indoors. Communication using UHF waves can be associated with smaller antennas and a shorter range (e.g., less than 100 kilometers) compared to communication using the 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 may also operate in the very high frequency (SHF) region (also known as the centimeter band) using spectrum in the 3 GHz to 30 GHz range, or in the extremely high frequency (EHF) region (e.g., 30 GHz to 300 GHz), also known as the millimeter band. In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between the UE 115 and the network entity 105 (e.g., base station 140, RU 170), and the EHF antennas of the corresponding devices may be smaller and more closely spaced than UHF antennas. In some examples, such technology may facilitate the use of antenna arrays within the device. However, the propagation of EHF transmissions may be subject to even greater attenuation and a shorter range than SHF or UHF transmissions. The techniques disclosed herein may be employed across transmissions using one or more different frequency regions, and the frequency band usage specified across these frequency regions may vary by country or regulatory agency.

[0087] The wireless communication system 100 can utilize both 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 using unlicensed bands, such as the 5 GHz Industrial, Scientific, and Medical (ISM) band. When operating using unlicensed RF spectrum bands, devices such as the network entity 105 and the UE 115 can employ carrier sensing for conflict detection and avoidance. In some examples, operations using the unlicensed bands can be based on a carrier aggregation configuration (e.g., LAA) in conjunction with component carriers operating using licensed bands. Operations using the unlicensed spectrum can include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among others.

[0088] A network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input, multiple-output (MIMO) communications, or beamforming. The antennas of the network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which can 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, antennas or antenna arrays associated with the network entity 105 may be located at different geographic locations. The network entity 105 may include an antenna array having a set of multiple 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 include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panels may support RF beamforming for signals transmitted via the antenna ports.

[0089] The network entity 105 or the UE 115 may use MIMO communication to exploit multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers. This technique may be referred to as spatial multiplexing. The multiple signals may, for example, be transmitted by a transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports for channel measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO), in which multiple spatial layers are transmitted to the same receiving device, and multi-user MIMO (MU-MIMO), in which multiple spatial layers are transmitted to multiple devices.

[0090] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can 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 the signals communicated via the antenna elements can include the transmitting or receiving device applying an amplitude shift, a phase shift, or both to the signals carried by the antenna elements associated with the device. The adjustments associated with each of these antenna elements can be defined by a set of beamforming weights associated with a particular direction (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other direction).

[0091] The network entity 105 or the UE 115 may use beam sweeping techniques as part of a beamforming operation. For example, the network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with the UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by the network entity 105 along different directions. For example, the network entity 105 may transmit signals according to different sets of beamforming weights associated with different transmission directions. Transmissions along different beam directions may be used to identify (e.g., by a transmitting device (such as the network entity 105) or by a receiving device (such as the UE 115)) the beam direction for later transmission or reception by the network entity 105.

[0092] Some signals (such as data signals associated with a particular receiving device) may be transmitted by a transmitting device (e.g., transmitting network entity 105, transmitting UE 115) along a single beam direction (e.g., a direction associated with a receiving device (e.g., receiving network entity 105 or receiving UE 115)). In some examples, a beam direction associated with transmission along a single beam direction may be determined based on signals transmitted along one or more beam directions. For example, UE 115 may receive one or more of the signals transmitted by network entity 105 along different directions and may report to network entity 105 an indication of the signal received by UE 115 with the highest signal quality or other acceptable signal quality.

[0093] In some examples, transmission by a device (e.g., by network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a configured set of beams across the system bandwidth or one or more subbands. Network entity 105 may transmit reference signals (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS)), which may or may not be precoded. UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel codebook, a linear combination codebook, or a port-selective codebook). Although these techniques are described with reference to signals sent by a network entity 105 (e.g., base station 140, RU 170) in one or more directions, UE 115 may use similar techniques to send signals multiple times in different directions (e.g., to identify a beam direction for subsequent transmission or reception by UE 115) or to send signals in a single direction (e.g., to send data to a receiving device).

[0094] A receiving device (e.g., UE 115) may perform reception operations according to multiple reception configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a receiving device (e.g., network entity 105). For example, the receiving device may perform reception according to multiple reception directions by receiving via different antenna subarrays, processing received signals according to different antenna subarrays, receiving according to different sets of receive beamforming weights applied to signals received at multiple antenna elements of an antenna array (e.g., different sets of directional listening weights), or processing received signals according to different sets of receive beamforming weights applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as "listening" according to different reception configurations or reception directions. In some examples, the receiving device may use a single reception configuration to receive along a single beam direction (e.g., when receiving data signals). A single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0095] The wireless communication system 100 may be a packet-based network operating according to a layered protocol stack. In the user plane, communications at the bearer or PDCP layer may be IP-based. The RLC layer may perform packet segmentation and reassembly for communication via logical channels. The MAC layer may perform priority handling and multiplexing of logical channels into transport channels. The MAC layer may also support retransmission using error detection, error correction, or both to improve link efficiency. In the control plane, the RRC layer may provide for the establishment, configuration, and maintenance of RRC connections between the UE 115 and the network entity 105 or core network 130 for radio bearers supporting user plane data. The PHY layer may map transport channels to physical channels.

[0096] UE 115 and network entity 105 may support retransmission of data to increase the likelihood of successful data reception. Hybrid Automatic Repeat Request (HARQ) feedback is a technique used to increase the likelihood of correct data reception via 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 throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, a device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a particular slot for data received via previous symbols in that slot. In other examples, the device may provide HARQ feedback in subsequent slots or based on some other time interval.

[0097] In some examples, as described herein, a UE 115 (e.g., UE 115-a) may detect and report IDC interference affecting sidelink communications, and a transmitting device (e.g., network entity 105-a or UE 115) may schedule resources for sidelink communications based on the reported IDC interference (e.g., resources may be scheduled to avoid using resources affected by the IDC interference). In some examples described herein (e.g., when UE 115 and UE 115 operate in Mode 2), a receiving UE 115 may receive configuration information from a transmitting UE 115 indicating parameters for reporting IDC interference to UE 115. The receiving UE 115 may detect the IDC interference and subsequently send an IDC interference report to the transmitting UE 115. The transmitting UE 115 may configure the report via RRC signaling or as a measurement object (e.g., sidelink assistance information, sidelink measurement object, inter-UE coordination information, etc.). The receiving UE 115 may send the IDC interference report as part of upper layer signaling (RRC signaling), radio link failure, etc. The UE 115 may report the specific subchannel, resource pool, channel, etc. that is experiencing IDC interference. The transmitting UE 115 may reserve subsequent sidelink resources to avoid using the indicated resources.

[0098] In some examples (e.g., when UE 115 operates in Mode 1), the transmitting UE 115, the receiving UE 115, or both may report IDC interference to the network entity 105, which may prevent the indicated resources from being used for future sidelink grants. UE 115 may send the IDC interference report to the network entity during network configuration via RRC signaling, UE assistance information, or the two UEs may communicate with each other and one UE 115 may send the identified IDC interference to the network entity 105. In some cases, the IDC interference report may indicate interference affecting a specific RAT. In some examples, UE 115 may report power coexistence solutions to the network entity 105.

[0099] Figure 2 An example of a wireless communication system 200 that supports sidelink IDC interference mitigation according to one or more aspects of the present disclosure is illustrated. The wireless communication system 200 may implement aspects of the wireless communication system 100 or may be implemented by aspects of the wireless communication system 100. For example, the wireless communication system 200 may include a network entity 105-a and one or more UEs 115 (e.g., UE 115-a and UE 115-b), which may be reference entities. Figure 1 Examples of corresponding devices described.

[0100] UE 115-a and UE 115-b may communicate with each other via wireless communication link 205-b (e.g., via sidelink communication). Network entity 105-a may communicate with one or more UEs 115 (e.g., UE 115-a) via wireless communication link 205-a (e.g., a Uu link). UE 115-a and UE 115-b may communicate according to a first sidelink mode (e.g., Mode 1, in which network entity 105-a allocates sidelink resources for sidelink communication between UE 115-a and UE 115-b) or a second sidelink mode (e.g., Mode 2, in which the transmitting UE 115-a allocates sidelink resources for sidelink communication between UE 115-a and UE 115-b).

[0101] In some examples, one or more of UEs 115 may experience IDC interference. For example, UE 115-a may support one or more transceivers 210 (e.g., associated with multiple transmit / receive chains). For example, transceiver 210-a may be associated with a first RAT (e.g., cellular or NR technology associated with an NR baseband and communicating via antenna 215-a), transceiver 210-b may be associated with a second RAT (e.g., GPS associated with a GPS baseband and communicating via antenna 215-b), and transceiver 210-c may be associated with a third RAT (e.g., Bluetooth or Wi-Fi technology associated with an NR baseband and communicating via antenna 215-c).

[0102] Communications via one transceiver 210 may cause IDC interference to another transceiver 210. For example, NR communications via transceiver 210-a (e.g., via antenna 215-a) may cause IDC interference to transceiver 210-b (e.g., via antenna 215-b), transceiver 210-c (e.g., via antenna 215-b), or both. Similarly, Bluetooth or Wi-Fi 32 signaling via transceiver 210-c (e.g., via antenna 215-c) may cause interference to one or more transceivers 210 (e.g., transceiver 210-a). This IDC interference may degrade the quality of communications via one or more RATs, increase signaling overhead and system latency, reduce communication reliability, and degrade the user experience.

[0103] IDC interference may be caused by the proximity between radio transceivers 210 within a UE 115-a. In some examples, the transmit power of a transmitter (e.g., via a transceiver 210) may be higher than the receive power of a signal received by a receiver (e.g., via another transceiver 210). In such examples, the relatively small amount of IDC interference generated by the transmission via a transceiver 210 may affect the reception and decoding of the received signal at the other transceiver 210. In some examples (e.g., different RATs operating on adjacent frequency resources), filtering performed by one transceiver 210 at a UE 115-a may not be sufficient to resolve the IDC interference. Furthermore, in some examples, the UE 115-a may not support a single radio frequency design (e.g., at a single transceiver 210) for resolving or filtering IDC interference.

[0104] IDC interference may occur for various RATs that use different frequency resources (e.g., adjacent, overlapping, or closely located frequency resource ranges). For example, a first frequency band and a second frequency band (e.g., an NR band spanning 2300 MHz to 2400 MHz and a second NR band spanning 2496 MHz to 3690 MHz) may be allocated for NR communications, while a third frequency band (e.g., 2400 MHz to 2483.5 MHz, including up to 79 channels) may be allocated for Wi-Fi or Bluetooth communications. In such examples, NR communications may cause IDC interference to Wi-Fi or Bluetooth reception, and vice versa. Similarly, uplink communications via the NR band may cause interference to Global Navigation Satellite System (GNSS) channels or Indian Regional Navigation Satellite System (IRNSS) navigation or positioning systems. Additionally or alternatively, mmWave communications (e.g., via channels below 6 MHz) may cause mutual interference based on the channels used or transmit chain sharing, etc. Reference Figure 3 An example of IDC interference is described in more detail.

[0105] In some examples, as described herein, a UE 115 (e.g., UE 115-a) may detect and report IDC interference affecting sidelink communications, and a transmitting device (e.g., network entity 105-a or UE 115-b) may schedule resources for sidelink communications (e.g., via communication link 205-b) based on the reported IDC interference (e.g., resources may be scheduled to avoid using resources affected by the IDC interference). In some examples described herein (e.g., when UE 115-a and UE 115-b are operating in Mode 2), a receiving UE 115 (e.g., UE 115-a) may receive configuration information from a transmitting UE 115 (e.g., UE 115-b) indicating parameters for reporting IDC interference to UE 115-b. The receiving UE 115-a may detect the IDC interference and subsequently send an IDC interference report to the transmitting UE 115-b. The transmitting UE 115-b may configure the report via RRC signaling or as a measurement object (e.g., sidelink assistance information, sidelink measurement object, inter-UE coordination information, etc.). The receiving UE 115-a may send the IDC interference report as part of upper layer signaling (RRC signaling), radio link failure, etc. The UE 115-a may report the specific subchannel, resource pool, channel, etc. that is experiencing IDC interference. The transmitting UE 115-b may reserve subsequent sidelink resources to avoid using the indicated resources.

[0106] In some examples (e.g., when UE 115-a and UE 115-b are operating in Mode 1), transmitting UE 115-b, receiving UE 115-a, or both may report IDC interference to network entity 105-a, which may prevent the indicated resources from being used for future sidelink grants. UE 115 may send the IDC interference report to the network entity via RRC signaling, UE assistance information during network configuration, or the two UEs may communicate with each other and one UE 115 (e.g., UE 115-a) may send the identified IDC interference to network entity 105-a. In some cases, the IDC interference report may indicate interference affecting a specific RAT. In some examples, UE 115 may report a power coexistence solution to network entity 105-a.

[0107] Figure 3 Illustrated are examples of timelines (eg, timeline 300 , timeline 301 , and timeline 302 ) that support sidelink IDC interference mitigation in accordance with one or more aspects of the present disclosure. Figure 3 Aspects of the wireless communication system 100 and the wireless communication system 200 may be implemented or implemented by aspects of these wireless communication systems. For example, a UE (eg, which may correspond to a similar device such as reference Figure 1 and 2The depicted UE 115) may communicate according to timeline 300, timeline 301, timeline 302, or any combination thereof, and may experience and report IDC interference as described herein.

[0108] In some examples, a UE communicating according to timeline 300 may experience IDC interference. For example, the UE may transmit signal 305 according to a first RAT (e.g., a Wi-Fi transmission) via frequency band 315-a (e.g., a 5 GHz frequency band, such as the 5.15 GHz to 5.85 GHz frequency band) and may also receive signal 310 (e.g., a cellular or NR transmission) via frequency band 315-b (e.g., an NR channel, such as the 4.4 GHz to 5.0 GHz frequency band). Although frequency bands 315-a and 315-b may not overlap in frequency, a receiver associated with signal 310 may experience IDC interference caused by signal 305. For example, signal 305 may be transmitted at a transmit power (P1), and signal 310 may be received at a receive power (P2), which may be lower than power P1. Although the UE may transmit signal 305 via frequency band 315-a, out-of-band (OOB) transmissions may occur via frequency resources 320-a, spurious transmissions may occur via frequency resources 320-b, or a combination thereof. In such examples, a portion of the transmission via frequency band 315-a, the OOB transmissions, the spurious transmissions, or any combination thereof may cause IDC interference to reception of signal 310.

[0109] In such an example, IDC interference may be caused by NR transmissions (e.g., Wi-Fi signaling) to another RAT or NR receptions from another RAT, or both, due to an operating band (e.g., band 315-a) adjacent to an ISM band (e.g., band 315-b). Similarly, according to timeline 301, a UE may communicate via adjacent or nearby band 315. For example, the UE may communicate via band 315-c (e.g., a 2.4 GHz band, such as the 2.402 GHz to 2.482 GHz band used for Wi-Fi or Bluetooth signaling) and band 315-d (e.g., an NR band, such as the 2.496 GHz to 2.690 GHz band). Transmissions via band 315-c may generate IDC interference with band 315-d (e.g., or vice versa). Similarly, the UE may communicate via frequency band 315-a (e.g., a 5 GHz band, such as the 5.15 GHz to 5.85 GHz band used for Wi-Fi or Bluetooth signaling) and frequency band 315-d (e.g., an NR band, such as the 4.4 GHz to 5.0 GHz band). Transmissions via frequency band 315-a may cause IDC interference to frequency band 315-b (e.g., as described with reference to timeline 300).

[0110] In some examples, a UE may experience IDC interference, such as intermodulation distortion (IMD) interference, due to dual connectivity (e.g., New Radio Dual Connectivity (NR-DC)). For example, the UE may perform simultaneous transmissions via different RATs. The UE may transmit a signal 325 (e.g., an NR transmission) via a frequency band located at frequency F3 (e.g., 4450 MHz) and may simultaneously (e.g., at least partially overlapping in time) transmit a signal 330 (e.g., an LTE transmission) via a frequency band located at frequency F1 (e.g., 1940 MHz). In dual connectivity scenarios (e.g., NR-DC or E-UTRAN Dual Connectivity (EN-DC), etc.), the UE may transmit uplink transmissions via a primary cell group (MCG) and a secondary cell group (e.g., SCG). IMD interference may occur due to the combination of simultaneous transmissions and operating frequency bands used during dual connectivity operation. For example, simultaneous transmission of signal 325 and signal 330 may cause interference 335 (eg, at frequency F2, such as 2510 MHz), which may affect reception of signal 340 (eg, transmitted using another RAT, such as Wi-Fi via a frequency band such as the 2.4 GHz band).

[0111] In some examples, the UE may attempt to resolve IDC interference by implementing a power allocation solution, such as referring to Figure 3 IDC interference as described. Dynamic or semi-static power allocation procedures may be applied (e.g., for physical layer purposes and synchronization), such as inter-band FDM coexistence with static power allocation for each carrier. However, in such a scheme, synchronization between sidelink UEs may not occur. When the transmission from one sidelink transmission overlaps with the reception of another sidelink transmission, inter-band FDM coexistence may not be feasible if the inter-band separation is not large enough (e.g., does not exceed a threshold). For inter-band and intra-band FDM coexistence with dynamic power sharing, the UE may drop or sacrifice transmissions from some RATs in favor of transmissions associated with other RATs (e.g., according to one or more rules). However, such techniques may not support sidelink transmissions or may cause sidelink transmissions to be interrupted, degraded, or deprioritized.

[0112] As reference Figure 3 As described herein, IDC interference may therefore degrade sidelink communications (e.g., or any type of wireless communications), and the UE may not support mechanisms for identifying, mitigating, or avoiding such IDC interference. As described herein, a UE may identify IDC interference (e.g., IDC interference affecting sidelink resources) and may report the IDC interference to a transmitting sidelink UE, a network entity, or both.

[0113] As reference Figures 4 to 7As described in more detail, a UE may detect and report IDC interference affecting sidelink communications, and a transmitting device may schedule resources for sidelink communications based on the reported IDC interference (e.g., resources may be scheduled to avoid using resources affected by the IDC interference). In some examples described herein (e.g., when the UE and UE 115-b operate in Mode 2), a receiving UE may receive configuration information from a transmitting UE indicating parameters for reporting IDC interference to the transmitting UE. The receiving UE may detect the IDC interference and subsequently send an IDC interference report to the transmitting UE 115-b. The transmitting UE may configure the report via RRC signaling or as a measurement object (e.g., sidelink assistance information, sidelink measurement object, inter-UE coordination information, etc.). The receiving UE may send the IDC interference report as part of upper layer signaling (RRC signaling), radio link failure, etc. The receiving UE may report a specific subchannel, resource pool, channel, etc. that is experiencing IDC interference. The transmitting UE may reserve subsequent sidelink resources to avoid using the indicated resources.

[0114] In some examples (e.g., when the UE is operating in Mode 1), the transmitting UE, the receiving UE, or both may report IDC interference to the network entity, which may prevent the indicated resources from being used for future sidelink grants. The UE may send the IDC interference report to the network entity via RRC signaling, UE assistance information during network configuration, or the two UEs may communicate with each other and one UE may send the identified IDC interference to the network entity. In some cases, the IDC interference report may indicate interference affecting a specific RAT. In some examples, the UE may report power coexistence solutions to the network entity.

[0115] Figure 4 An example of a wireless communication system 400 that supports sidelink IDC interference mitigation according to one or more aspects of the present disclosure is illustrated. The wireless communication system 400 may implement aspects of the wireless communication system 100 and the wireless communication system 200, or may be implemented by aspects of these wireless communication systems. For example, the wireless communication system 200 may include one or more UEs 115 (e.g., UE 115-c and UE 115-d), which may be reference Figure 1 and Figure 2 Examples of corresponding devices described.

[0116] In some examples, UE 115-c and UE 115-d may communicate with each other via wireless communication link 405 (e.g., PC-5 interface). In some examples, a transmitting device (e.g., UE 115-d) may schedule sidelink resources to be used for communication with UE 115-c. The sidelink resources may span all or a portion of one or more frequency bands, subbands, channels, etc. (e.g., one or more subchannels such as subchannel 1, subchannel 2, and subchannel 3). However, due to IDC interference (e.g., as described in reference Figures 2 to 3 Due to the described IDC interference 410, UE 115-c may not be able to correctly receive some or all scheduled transmissions. IDC interference 410 may affect some frequency resources (e.g., subchannel 2 and at least a portion of subchannel 3). IDC interference 410 may cause sidelink transmission failures, excessive retransmissions, and in some cases, radio link failure (RLF). Techniques described herein may support reporting and mitigation of IDC interference 410.

[0117] For example, a receiving UE (e.g., UE 115-c) may signal a transmitting UE (e.g., UE 115-d) that it is experiencing an IDC problem (e.g., IDC interference 410) at a certain frequency (e.g., in one or more frequency resources). The transmitting UE (e.g., UE 115-d) may then avoid reserving the IDC-affected frequency for transmissions to the receiving UE (e.g., UE 115-c). For example, UE 115-d may indicate that IDC interference 410 affects part or all of subchannel 2 and part or all of subchannel 3. For example, in the case of unicast signaling, UE 115-d or a network entity (e.g., via control signaling, such as Mode 2 Setup signaling) may configure the receiving UE 115-c to report the IDC interference via higher layer signaling (e.g., such as an RRCReconfigurationSidelink message). The higher layer signaling (e.g., an information element of an RRC message) may enable IDC interference reporting from the receiving UE 115-c. In some examples, IDC may be added to an RRC message (e.g., an RRCReconfigurationSidelink message), which may include one or more fields. For example, the RRC message may include an assistance message field (e.g., an idc-AssistanceConfig field) that includes configuration information for UE 115-c to report assistance information to notify UE 115-d (e.g., or a network entity) of an IDC problem detected by the UE. The RRC message may include a serving frequency list message (e.g., a candidateServingFreqListNR field) that may indicate, for each candidate NR serving cell, a center frequency around which the UE 115-c is requested to report an IDC problem. The RRC message may include a resource pool field (e.g., a CandidateResourcePools resource) that may indicate a resource pool configured for reporting IDC problems. The RRC message may include a subchannel list field (e.g., a CandidateSubchannelList field) indicating that the UE 115-c is requested to report IDC issues for the configured candidate subchannels (e.g., subchannel 1, subchannel 2, and subchannel 3). The RRC message may include a BWP list message (e.g., a CandidateSLBWPList field) indicating that the UE 115-c is requested to report IDC issues for the configured active or inactive sidelink BWPs. The RRC message may include a granularity message indicating the granularity of the UE's reporting (e.g., indicating whether the UE is to report the center frequency, resource pool, subchannel, BWP, or other subset of frequency resources that is experiencing IDC interference 410, etc.).

[0118] The granularity of reporting IDC interference may be configurable (e.g., by a network entity, a transmitting UE 115-d, or a combination thereof). The configured granularity may indicate that the UE reports IDC interference 410 at a carrier frequency granularity. In such an example, the UE may report that a carrier frequency or list of carrier frequencies is affected by an IDC frequency sharing issue. The transmitter (e.g., UE 115-d) may then attempt to transmit sidelink signaling via a different carrier frequency or may relay deployment reselection to a different UE 115 (e.g., another candidate transmitting UE 115). In some examples, the configured granularity may indicate that the UE will report IDC interference 410 at a BWP granularity. In such an example, UE 115-c may report that the entire sidelink BWP (e.g., or a portion of the sidelink BWP) is affected by an IDC issue. The transmitting UE 115-d may then attempt to configure a different bandwidth portion for Mode 2 deployment, or may avoid transmitting high quality of service (QoS) traffic via the indicated BWP, or (e.g., for a relay deployment UE) may perform relay reselection.

[0119] The configured granularity may indicate that UE 115-c will report IDC interference 410 at the sidelink resource pool granularity. In such an example, UE 115-c may report that an IDC problem is occurring at a certain resource pool. This may trigger resource pool reconfiguration, if possible. In some examples, the configured granularity may indicate that UE 115-c will report IDC interference 410 at the sidelink subchannel granularity. In such an example, UE 115-c may report the subchannels affected by IDC interference 410 (e.g., subchannel 2 and subchannel 3). The IDC interference report may indicate that the transmitting UE 115-d will avoid using the reported subchannels affected by IDC interference 410. In some examples, the configured granularity may indicate that UE 115-c will report IDC interference 410 at the PRB or frequency granularity level. In such an example, UE 115-c may report individual PRBs or frequency ranges affected by IDC interference 410. The transmitting UE 115-d may then avoid using the resources reported to be experiencing IDC problems. As described herein, the UE 115-c may report IDC interference at any granularity (e.g., it may indicate carrier frequency, sidelink BWP, sidelink resource pool, sidelink subchannel, PRB or frequency resource range affected by the sidelink, etc.). In some cases, the UE 115-c may report IDC interference 410 at a configured granularity.

[0120] In some examples (e.g., instead of configuring the IDC report as part of a PC5-RRC configuration, such as various RRC message fields described herein), the IDC report may be configured as a measurement object. For example, during a measurement configuration provided from a transmitting UE 115-d to a receiving UE 115-d, the transmitting UE 115-d may configure the UE 115-c with the measurement object. In such an example, the UE 115-c may detect (e.g., measure) the IDC interference 410 and report the IDC interference (e.g., if one or more conditions configured via the measurement object are met). In such an example, the UE 115-c may report the IDC interference information via sidelink assistance information (e.g., ueAssistanceInformationSidelink-r17), or as a sidelink measurement object or as an inter-UE coordination information message.

[0121] In some examples, UE 115-c may send an IDC interference report to UE 115-d as part of upper layer signaling (e.g., PC5 RRC signaling or ueAssistanceInformationSidelink-r17 message). In the event of a severe IDC problem (e.g., resulting in RLF), UE 115-c may indicate the IDC difficulty in an indication message (e.g., RRCReconifgurationFailureSidelink message) to prompt UE 115-d to attempt to communicate using a different sidelink BWP, a different sidelink resource pool, or a different frequency resource group. In some examples, UE 115-c may report the problematic subchannels (e.g., the subchannels affected by IDC interference 410) in UE capability information (e.g., prior to the PC-5 RRC establishment procedure). In such examples, UE 115-c may indicate information for potential transmitters (e.g., in capability information) (e.g., prior to any RRC configuration information). In such an example, UE 115-c may determine resources affected by IDC interference 410 (e.g., based on current or previous sidelink signaling) and may indicate the affected resources via capability information. The transmitting UE 115-d may then avoid using the indicated resources for subsequent sidelink communications.

[0122] In some examples, the IDC interference report may be configured as an event-triggered measurement. In such examples, the UE 115-c may send a message (e.g., a medium access control (MAC) control element (CE)) whenever an IDC problem is encountered. For example, the UE 115-c may send a MAC-CE indicating the presence of an IDC interference report upon detecting IDC interference 410 (e.g., when the channel quality drops below a threshold due to IDC interference 410, or when the amount of IDC interference 410 meets a threshold).

[0123] The UE 115-c may report IDC interference via one or more IDC parameters to indicate IDC interference. For example, the IDC interference report may include an affected carrier frequency field (e.g., an affectedCarrierFreqList IDC field) indicating a list of carrier frequencies affected by the IDC problem. The IDC interference report may include an affected frequency list field (e.g., an affectedFrequencyList IDC field) indicating a list of PRBs or frequency ranges affected by the IDC problem. The IDC interference report may include an affected subchannel field (e.g., an affectedSubchannelList IDC field) indicating a list of subchannels affected by the IDC problem. The IDC interference report may include an affected resource pool field (e.g., an affectedResourcePoolList IDC field) indicating a list of carrier frequencies affected by the IDC problem. The IDC interference report may include an affected BWP field (e.g., an affectedBWPList IDC field) indicating a list of sidelink BWPs affected by the IDC problem. An IDC interference report may include an affected system type field (e.g., a victimSystemType IDC field) that indicates a list of victim system types that caused IDC interference (e.g., by a given RAT). Such a field may indicate a RAT such as GPS, Global Navigation Satellite System (GLONASS), BeiDou Navigation Satellite System (BDS), Galileo, and Navigation in Indian Constellation (NavIC), which may indicate the type of GNSS. Such a field may indicate a WLAN or Bluetooth RAT.

[0124] Figure 5 An example of a process flow 500 for supporting sidelink IDC interference mitigation according to one or more aspects of the present disclosure is illustrated. The process flow 500 may implement Figures 1 to 4 For example, the process flow 500 may include UE 115-e and UE 115-f, which may be reference Figures 1 to 5 Examples of corresponding devices described.

[0125] At 505, UE 115-f may receive reporting information indicating IDC interference (e.g., from UE 115-e). The reporting information may include sidelink RRC signaling, which may include an indication that IDC interference reporting by UE 115-f is enabled. The reporting information may indicate a granularity for reporting IDC interference at 525. For example, the reporting information may indicate a center frequency around which UE 115-f is requested to report IDC interference, an indication of a sidelink resource pool for IDC interference, an indication of one or more active sidelink BWPs or inactive sidelink BWPs corresponding to the IDC interference, or any combination thereof. In some examples, UE 115-f may receive the reporting information from another device (e.g., another UE 115 or a network entity 105).

[0126] In some examples, the report information may include a measurement object configuration message, a sidelink information message, an inter-UE coordination information message, etc. The report information may include event-triggered measurement object configuration information. In such an example, the UE 115-f may detect IDC interference (e.g., determine that one or more events or one or more conditions are satisfied) at 520 and may send an IDC interference report based on being triggered by the detected IDC interference (e.g., the detected event or condition). In such an example, the UE 115-f may send a MAC-CE including the event-triggered IDC interference report at 525.

[0127] At 510 , UE 115 - f may receive a resource reservation message (eg, from UE 115 - e when operating in mode 2) indicating (eg, reserving) a set of sidelink resources for performing sidelink communications (eg, with UE 115 - e).

[0128] At 515, UE 115-e may send a sidelink message to UE 115-f. UE 115-e may send the sidelink message via the set of sidelink resources according to the reservation message sent at 510.

[0129] At 520, UE 115-f may detect IDC interference (e.g., based on monitoring the sidelink message sent by UE 115-e at 515 via the resources indicated at 510). For example, UE 115-f may monitor the sidelink message, fail to successfully receive or decode the sidelink message, possibly due to IDC interference, detect IDC interference based on one or more measurements, or any combination thereof. Based on the monitoring or detected failure, UE 115-f may detect IDC interference, and UE 115-f may report the IDC interference at 525.

[0130] At 525, UE 115-f may send an IDC interference report to UE 115-e based on the reporting information, the IDC interference report indicating IDC interference corresponding to at least a portion of the set of sidelink resources allocated at 510. UE 115-f may send, in the IDC interference report, an indication of one or more carrier frequencies, sidelink BWPs, sidelink resource pools, sidelink subchannels, sidelink PRBs, frequency resource ranges, or any combination thereof affected by the IDC interference (e.g., resources in which IDC interference is detected or a threshold is satisfied).

[0131] In some examples, the IDC interference report can be an indication of a link failure associated with the set of sidelink resources due to IDC interference. For example, the IDC interference report can be included in the RLF report.

[0132] In some examples, at 525, UE 115-f may multicast the IDC interference report to multiple UEs 115 (e.g., including UE 115-e). Multicasting the IDC interference report may allow potential transmitters to exclude the reporting UE 115-f from the group, or the potential transmitters may avoid using the indicated resources. Such a process may allow the network to avoid misinterpreting negative feedback signaling (e.g., negative acknowledgement (NACK) indications) continuously sent by a multicast member, thereby preventing the multicast capacity from being severely limited.

[0133] In some examples, the IDC interference report may be an inter-UE coordination message that includes an indication that the sidelink resource affected by the IDC interference is a non-preferred resource (e.g., as described in reference to FIG. Figure 7 In some examples, the IDC interference report may be carried via a MAC-CE message or a Sidelink Control Information (SCI) message (eg, an SCI format 2-C message).

[0134] At 530, UE 115-e may send a resource reservation message to UE 115-f based on the IDC interference report received from UE 115-f at 525. For example, UE 115-e may reserve sidelink resources that are not indicated in the IDC interference report (e.g., sidelink resources that are not affected by the IDC interference detected at 520). In some examples, UE 115-e may reserve resources at 510, indicating a first set of resources for a first time period. At 525, based on the IDC interference report 525, UE 115-e may reserve a second set of resources for a second time period. In some cases, the second time period may not overlap with the first time period (e.g., the second set of resources may be another set of resources reserved to avoid frequency resources indicated in the IDC interference report). In some examples, the second time period may at least partially overlap with the first set of resources, in which case the resource reservation message sent at 525 may include at least some reselection of the resources (e.g., if some resources in the first set of resources have been indicated in the IDC interference report, some resources in the second set of resources may override or replace the resources reserved at step 510).

[0135] Figure 6 An example of a process flow 600 for supporting sidelink IDC interference mitigation according to one or more aspects of the present disclosure is illustrated. The process flow 600 may implement Figures 1 to 5 For example, the process flow 500 may include UE 115-e and UE 115-f, and network entity 105-b, which may be reference Figures 1 to 5 Examples of corresponding devices described.

[0136] UE 115-h and UE 115-g may perform sidelink communications while operating according to Mode 1. At 610, one or more UEs 115 (e.g., UE 115-h at 610-a, UE 115-g at 610-b, or both) may receive scheduling information (e.g., a resource reservation message) (e.g., from network entity 105-b) indicating a set of sidelink resources for performing sidelink communications.

[0137] At 615, UE 115-g and UE 115-h may communicate with each other via the sidelink resources indicated at 610. At 620-a, UE 115-g may detect IDC interference (eg, based on the sidelink communication at 615).

[0138] In some examples, each UE 115 may send an IDC interference report indicating IDC interference around at least a portion of the sidelink resources granted at 610. For example, both the transmitting UE and the receiving UE may report detected IDC issues occurring on the sidelink resources (e.g., because the network may be responsible for provisioning resources to the sidelink UEs for sidelink communication). For example, UE 115-g may send an IDC interference report at 625-a, and UE 115-h may detect IDC interference at 620-b and send an IDC interference report at 630.

[0139] The IDC interference report may be part of the network configuration for PC-5 communications (e.g., may be carried via sl-ConfigDedicatedNR in an RRCconfiguration message). In some examples, UE 115-g (e.g., at 605-a), UE 115-h (e.g., at 605-b), or both may be configured by network entity 105-b to send the IDC interference report at 625 and 630, respectively. In some examples, UE 115-g, UE 115-h, or both may send the IDC interference report as part of a sidelink UE assistance information message.

[0140] In some examples, the IDC reporting information may be reported separately by the transmitter and receiver, or may be reported only by a single UE 115 (e.g., by the transmitting UE on behalf of both the transmitting UE and the receiving UE). For example, one UE 115 may relay the IDC interference report to the network entity 105-b (e.g., on behalf of another UE 115). For example, UE 115-h may receive the indication of IDC interference (e.g., at 625-a) and may send the IDC interference report at 630 (e.g., may forward the indication of IDC interference to the network entity 105-b).

[0141] In some examples, an IDC interference report (e.g., sent by one or both UEs 115) may indicate that IDC interference associated with sidelink resources of a first RAT is impacting wireless communications via a second RAT. For Uu sidelink intermodulation interference affecting some other RAT, UE 115-h may report (e.g., to network entity 105-b) the Uu-PC5 band combination that caused the IDC issue. This IDC interference report may be reported as part of a Uu unified air interface (UAI) that indicates interference from sidelink signaling (e.g., the Uu UAI may report assistance from the sidelink, which may or may not be an intermodulation issue). UE 115-h may send the IDC interference report information via a PC-5 link, a Uu link, or a combination thereof. In some examples, UE 115-h, UE 115-g, or both may apply an FDM power sharing solution. UE 115 may report to the network that UE 115 has determined to share power to support coexistence. The network entity 105 - b may then reassign PC-5 resources to alleviate some IDC issues, or communicate with another network entity 105 - b (eg, a network entity associated with a particular RAT) to coordinate resource sharing in the sidelink.

[0142] UE 115-h (e.g., or UE 115-g) may report IDC interference via one or more IDC parameters to indicate IDC interference. For example, an IDC interference report may include an affected carrier frequency field (e.g., an affectedCarrierFreqList IDC field or an affectedCarrierFreqList field) indicating a list of carrier frequencies affected by the IDC problem. An IDC interference report may include an affected frequency list field (e.g., an affectedFrequencyList IDC field) indicating a list of PRBs or frequency ranges affected by the IDC problem. An IDC interference report may include an affected subchannel field (e.g., an affectedSubchannelList IDC field) indicating a list of subchannels affected by the IDC problem. An IDC interference report may include an affected resource pool field (e.g., an affectedResourcePoolList IDC field) indicating a list of carrier frequencies affected by the IDC problem. An IDC interference report may include an affected BWP field (e.g., an affectedBWPList IDC field) indicating a list of sidelink BWPs affected by the IDC problem. An IDC interference report may include an affected system type field (e.g., a victimSystemType IDC field), which indicates a list of victim system types (e.g., by a given RAT) that caused IDC interference. Such a field may indicate a RAT, such as GPS, GLONASS, BDS, Galileo, and NavIC, which may indicate the type of GNSS. Such a field may indicate a WLAN or Bluetooth RAT. An IDC interference report may include an interference direction (e.g., an interferenceDirection IDC field), which indicates the direction of the IDC interference. A field value of "PC5" may indicate that only PC-5 signaling was subject to IDC interference, a value of "other" may indicate that only another radio was subject to IDC interference, and a value of "both" may indicate that both PC-5 and another radio were subject to IDC interference. "Other" radios may refer to one or more RATs.

[0143] Figure 7 An example of a process flow 700 for supporting sidelink IDC interference mitigation according to one or more aspects of the present disclosure is illustrated. The process flow 700 may implement Figures 1 to 6 For example, the process flow 700 may include UE 115-i and UE 115-j, which may be reference Figures 1 to 6 Examples of corresponding devices described.

[0144] At 705 , UE 115 - i may select resources to allocate to UE 115 - j (eg, when UE 115 - i and UE 115 - j are operating in Mode 2 ).

[0145] At 710, UE 115-j may receive reporting information (eg, from UE 115-i) indicating IDC interference. The reporting information may include configuration information (eg, an IDC interference report) for sending an indication of non-preferred resources.

[0146] At 715, UE 115-j may receive a resource reservation message (e.g., from UE 115-i when operating in mode 2) indicating (e.g., reserving) a set of sidelink resources for performing sidelink communications (e.g., with UE 115-i). UE 115-j may detect the IDC interference (e.g., when communicating with UE 115-e via the resources indicated at or prior to any sidelink communications with UE 115-i).

[0147] At 720, UE 115-j may send an IDC interference report to UE 115-i, the IDC interference report indicating IDC interference corresponding to at least a portion of a set of sidelink resources. The IDC interference report may be an inter-UE coordination information message indicating a set of preferred sidelink resources (e.g., resources that are not currently or are unlikely to be affected by IDC interference) or a set of non-preferred (e.g., not preferred) sidelink resources (e.g., resources that are currently or will likely be affected by IDC interference). In some examples, UE 115-j may perform proactive IDC interference reporting. For example, receiving UE 115-j may send an IDC interference report at 720 (e.g., prior to resource reservation at 730 and without utilizing the previous resource reservation that occurred at 715). In such an example, UE 115-j may indicate non-preferred sidelink resources, and UE 115-i may select sidelink resources at 725 and reserve the selected sidelink resources at 730 to avoid using the non-preferred sidelink resources indicated at 720. In some examples, UE 115-j may perform reactive IDC interference reporting. For example, based on receiving the resource reservation at 715, UE 115-j may determine that some of the indicated or granted sidelink resources are subject to IDC interference (e.g., and are therefore non-preferred resources). In response, UE 115-j may send an IDC interference report (e.g., an inter-UE coordination message indicating non-preferred resources) at 720. At 725, UE 115-i may select sidelink resources (e.g., may perform sidelink resource reselection) to avoid using non-preferred resources and may indicate an updated resource reservation at 730.

[0148] Non-preferred resources (e.g., as indicated in an IDC interference report) may be defined as sidelink resources that meet one or more conditions. For example, a non-preferred resource may be a resource reserved by another UE and: an RSRP measurement meets or exceeds a threshold (e.g., to protect the reporting UE or the transmitting UE from interference from the other UE 115); or an RARP measurement is below a threshold but the reporting UE is the intended recipient of a transmission via the reserved resource (e.g., to protect the reporting UE's reception from interference from another UE). A non-preferred resource may be a resource in a time slot in which the reporting UE 115-j is unable to receive a transmission from the transmitting UE 115-i due to a half-duplex deployment. Non-preferred resources may overlap only with frequencies that are internally affected by IDC interference. The non-preferred resource set may include only frequency resources (e.g., as indicated by a frequency resource indication value (FRIV)), and a time resource indication value (TRIV) may be used to indicate other IDC parameters (e.g., such as the various IDC fields described herein).

[0149] In some examples, the IDC interference report (e.g., indicating non-preferred resources) may be unicast, multicast, groupcast, or broadcast. The trigger for transmission of the IDC interference report may include a request from the transmitting UE 115-i (e.g., the report information sent at 710 may include a request to send an IDC interference report indicating non-preferred resources (e.g., an inter-UE coordination message)). In some examples, the request (e.g., the report information) may be sent via sidelink control information (e.g., SCI 2 or SCI format 2-C) or a MAC-CE. The resource set (e.g., the resource reservation at 715, or the resources indicated in the IDC interference report) may be sent as an SCI2 message (e.g., SCI carried via a physical sidelink shared channel (PSSCH)) or a MAC-CE. In some examples, the transmitting UE 115-i may send capability information via an SCI message (e.g., via the report information at 710) indicating that the UE 115-i is capable of using the IDC interference information (e.g., to select or reselect resources at 725). If an IDC indication (e.g., an IDC interference report) is received via SCI signaling, UE 115-i may forward the IDC indication from the physical layer to the MAC layer. In some examples, UE 115-j may send an IDC interference report upon request or based on one or more conditions. These conditions may be configured via PC-5 RRC signaling, or may be pre-configured, indicated in one or more standard documents, etc. If the conditions are met, UE 115-j may send an IDC interference report. In some examples, non-preferred resources due to IDC interference may be reported along with other non-preferred resources (e.g., a set of non-preferred resources, a subset of which are non-preferred based on IDC interference), or may be reported separately and explicitly indicate (e.g., indicate) which resources are not preferred due to IDC interference.

[0150] Figure 8 A block diagram 800 illustrates a device 805 that supports sidelink IDC interference mitigation according to one or more aspects of the present disclosure. The device 805 can be an example of aspects of the UE 115 as described herein. The device 805 can include a receiver 810, a transmitter 815, and a communication manager 820. The device 805 can also include a processor. Each of these components can communicate with each other (e.g., via one or more buses).

[0151] Receiver 810 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to sidelink IDC interference mitigation). The information may be passed to other components of device 805. Receiver 810 may utilize a single antenna or a collection of multiple antennas.

[0152] Transmitter 815 may provide means for transmitting signals generated by other components of device 805. For example, transmitter 815 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to sidelink IDC interference mitigation). In some examples, transmitter 815 may be co-located with receiver 810 in a transceiver module. Transmitter 815 may utilize a single antenna, or a collection of multiple antennas.

[0153] The communication manager 820, the receiver 810, the transmitter 815, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of sidelink IDC interference mitigation as described herein. For example, the communication manager 820, the receiver 810, the transmitter 815, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0154] In some examples, the communication manager 820, the receiver 810, the transmitter 815, 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 components, discrete hardware components, or any combination thereof configured as or otherwise supporting components for performing the functions described herein. In some examples, the processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0155] Additionally or alternatively, in some examples, the communication manager 820, the receiver 810, the transmitter 815, 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 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be performed by a general-purpose processor (e.g., configured as or otherwise supporting means for performing the functions described herein), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

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

[0157] According to examples disclosed herein, the communication manager 820 may support wireless communications at a first UE. For example, the communication manager 820 may be configured as or otherwise support means for receiving report information indicating IDC interference from a second UE. The communication manager 820 may be configured as or otherwise support means for receiving a resource reservation message indicating a set of sidelink resources from the second UE. The communication manager 820 may be configured as or otherwise support means for sending an IDC interference report to the second UE based on the report information, the IDC interference report indicating IDC interference corresponding to at least a portion of the set of sidelink resources.

[0158] Additionally or alternatively, according to examples disclosed herein, the communication manager 820 may support wireless communications at the first UE. For example, the communication manager 820 may be configured as or otherwise support means for receiving a resource reservation message from a network entity, the resource reservation message indicating a set of sidelink resources for performing sidelink communications with at least a second UE. The communication manager 820 may be configured as or otherwise support means for communicating with the second UE based on the resource reservation message. The communication manager 820 may be configured as or otherwise support means for sending an IDC interference report to the network entity based on performing sidelink communications, the IDC interference report indicating IDC interference corresponding to at least a portion of the set of sidelink resources.

[0159] By including or configuring the communication manager 820 according to examples as described herein, the device 805 (e.g., a processor controlling or otherwise coupled to the receiver 810, the transmitter 815, the communication manager 820, or any combination thereof) can support techniques for IDC interference reporting and mitigation, thereby reducing system latency, making signaling more reliable, and improving user experience.

[0160] Figure 9 A block diagram 900 illustrates a device 905 that supports sidelink IDC interference mitigation according to one or more aspects of the present disclosure. The device 905 may be an example of aspects of the device 805 or UE 115 as described herein. The device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. The device 905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0161] Receiver 910 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to sidelink IDC interference mitigation). The information may be passed to other components of device 905. Receiver 910 may utilize a single antenna or a collection of multiple antennas.

[0162] Transmitter 915 may provide means for transmitting signals generated by other components of device 905. For example, transmitter 915 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to sidelink IDC interference mitigation). In some examples, transmitter 915 may be co-located with receiver 910 in a transceiver module. Transmitter 915 may utilize a single antenna, or a collection of multiple antennas.

[0163] Device 905 or its various components may be examples of means for performing various aspects of sidelink IDC interference mitigation as described herein. For example, communications manager 920 may include an IDC interference information manager 925, a resource reservation manager 930, an IDC interference report manager 935, a sidelink communications manager 940, or any combination thereof. Communications manager 920 may be an example of aspects of communications manager 820 as described herein. In some examples, communications manager 920 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise coordinating with receiver 910, transmitter 915, or both. For example, communications manager 920 may receive information from receiver 910, transmit information to transmitter 915, or be integrated with receiver 910, transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.

[0164] According to examples disclosed herein, a communication manager 920 may support wireless communications at a first UE. An IDC interference information manager 925 may be configured as or otherwise support means for receiving report information indicating IDC interference from a second UE. A resource reservation manager 930 may be configured as or otherwise support means for receiving a resource reservation message indicating a set of sidelink resources from the second UE. An IDC interference report manager 935 may be configured as or otherwise support means for sending an IDC interference report to the second UE based on the report information, the IDC interference report indicating IDC interference corresponding to at least a portion of the set of sidelink resources.

[0165] Additionally or alternatively, according to examples disclosed herein, the communication manager 920 may support wireless communication at a first UE. The resource reservation manager 930 may be configured as or otherwise support means for receiving a resource reservation message from a network entity, the resource reservation message indicating a set of sidelink resources for performing sidelink communication with at least a second UE. The sidelink communication manager 940 may be configured as or otherwise support means for communicating with the second UE based on the resource reservation message. The IDC interference report manager 935 may be configured as or otherwise support means for sending an IDC interference report to the network entity based on performing sidelink communication, the IDC interference report indicating IDC interference corresponding to at least a portion of the set of sidelink resources.

[0166] Figure 10Block diagram 1000 illustrates a communication manager 1020 that supports sidelink IDC interference mitigation according to one or more aspects of the present disclosure. Communication manager 1020 may be an example of communication manager 820, communication manager 920, or aspects of both, as described herein. Communication manager 1020 or its various components may be examples of components for performing various aspects of sidelink IDC interference mitigation as described herein. For example, communication manager 1020 may include an IDC interference information manager 1025, a resource reservation manager 1030, an IDC interference report manager 1035, a sidelink communication manager 1040, a measurement object manager 1045, an inter-UE coordination manager 1050, an IDC detection manager 1055, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses).

[0167] According to examples disclosed herein, a communication manager 1020 may support wireless communications at a first UE. An IDC interference information manager 1025 may be configured as or otherwise support means for receiving report information indicating IDC interference from a second UE. A resource reservation manager 1030 may be configured as or otherwise support means for receiving a resource reservation message indicating a set of sidelink resources from the second UE. An IDC interference report manager 1035 may be configured as or otherwise support means for sending an IDC interference report to the second UE based on the report information, the IDC interference report indicating IDC interference corresponding to at least a portion of the set of sidelink resources.

[0168] In some examples, to support receiving reporting information, the IDC interference information manager 1025 may be configured as or otherwise support means for receiving sidelink RRC signaling including reporting information, wherein the reporting information includes an indication that IDC interference reporting by the first UE is enabled.

[0169] In some examples, the IDC interference information manager 1025 may be configured as or otherwise support a component for receiving, in sidelink RRC signaling, an indication of a center frequency around which the first UE is requested to report IDC interference, an indication of a sidelink resource pool for reporting IDC interference, an indication of one or more subchannels associated with reporting IDC interference, an indication of one or more active sidelink bandwidth portions or inactive sidelink bandwidth portions corresponding to the IDC interference, or any combination thereof.

[0170] In some examples, to support receiving reporting information, the IDC interference information manager 1025 may be configured as or otherwise support a component for receiving a measurement object configuration message, a sidelink assistance information message, or an inter-UE coordination information message.

[0171] In some examples, the IDC interference report manager 1035 may be configured as or otherwise support a component for sending in an IDC interference report an indication of one or more carrier frequencies, one or more sidelink bandwidth portions, one or more sidelink resource pools, one or more sidelink subchannels, one or more sidelink physical resource blocks, frequency resource ranges, or any combination thereof that are affected by the IDC interference.

[0172] In some examples, to support sending an IDC interference report, the IDC interference reporting manager 1035 may be configured as or otherwise support means for sending an indication of a link failure associated with the set of side link resources due to IDC interference.

[0173] In some examples, the measurement object manager 1045 can be configured as or otherwise support means for receiving an event-triggered measurement object configuration in the report information. In some examples, the measurement object manager 1045 can be configured as or otherwise support means for detecting IDC interference based on monitoring the set of sidelink resources according to the event-triggered measurement object configuration, wherein sending the IDC interference report includes sending a MAC control element (CE) based on detecting the IDC interference.

[0174] In some examples, to support sending an IDC interference report, the IDC interference report manager 1035 may be configured as or otherwise support means for multicasting the IDC interference report to a group of multiple sidelink UEs including the second UE.

[0175] In some examples, to support sending an IDC interference report, the inter-UE coordination manager 1050 may be configured as or otherwise support a component for sending an inter-UE coordination message that includes an indication that a set of multiple side link resources including at least the portion of the set of side link resources are non-preferred resources.

[0176] In some examples, the inter-UE coordination manager 1050 may be configured as or otherwise support means for receiving a request for an indication of non-preferred resources from a second UE, wherein sending the inter-UE coordination message is based on receiving the request.

[0177] In some examples, the inter-UE coordination manager 1050 may be configured as or otherwise support means for receiving configuration information indicating one or more conditions upon which sending the inter-UE coordination message is based.

[0178] In some examples, the inter-UE coordination manager 1050 may be configured as or otherwise support a component for receiving an indication from a second UE that the second UE is capable of receiving inter-UE coordination messages, wherein sending the inter-UE coordination message is based on receiving the indication that the second UE is capable of receiving inter-UE coordination messages.

[0179] In some examples, the inter-UE coordination manager 1050 may be configured as or otherwise support means for sending an indication in an inter-UE coordination message of a first subset of the set of multiple sidelink resources that is not preferred due to IDC interference.

[0180] In some examples, the IDC detection manager 1055 can be configured as or otherwise support means for monitoring sidelink signaling from the second UE based on the resource reservation message. In some examples, the IDC detection manager 1055 can be configured as or otherwise support means for detecting IDC interference on at least the portion of the set of sidelink resources based on the monitoring, wherein sending the IDC interference report is based on detecting the IDC interference.

[0181] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1020 may support wireless communications at the first UE. In some examples, the resource reservation manager 1030 may be configured as or otherwise support means for receiving a resource reservation message from a network entity, the resource reservation message indicating a set of sidelink resources for performing sidelink communications with at least a second UE. The sidelink communication manager 1040 may be configured as or otherwise support means for communicating with the second UE based on the resource reservation message. In some examples, the IDC interference report manager 1035 may be configured as or otherwise support means for sending an IDC interference report to the network entity based on performing sidelink communications, the IDC interference report indicating IDC interference corresponding to at least a portion of the set of sidelink resources.

[0182] In some examples, to support sending an IDC interference report, the IDC interference reporting manager 1035 may be configured as or otherwise support a component for sending an RRC message that includes an indication that at least the portion of the set of sidelink resources is experiencing IDC interference.

[0183] In some examples, to support sending an IDC interference report, the IDC interference reporting manager 1035 may be configured as or otherwise support a component for sending a UE assistance information message that includes an indication that at least the portion of the set of sidelink resources is experiencing IDC interference.

[0184] In some examples, the IDC interference reporting manager 1035 may be configured as or otherwise support means for receiving an indication of IDC interference from the second UE, wherein sending the IDC interference report includes forwarding the indication of IDC interference to a network entity.

[0185] In some examples, to support sending an IDC interference report, the IDC interference reporting manager 1035 may be configured as or otherwise support a component for sending an indication of the IDC interference impact on the wireless communication associated with the set of side link resources of the first radio access technology via the second radio access technology.

[0186] In some examples, the IDC interference report manager 1035 may be configured as or otherwise support a component for sending in an IDC interference report an indication of one or more carrier frequencies, one or more sidelink bandwidth portions, one or more sidelink resource pools, one or more sidelink subchannels, one or more sidelink physical resource blocks, frequency resource ranges, or any combination thereof that are affected by the IDC interference.

[0187] Figure 11 A diagram illustrates a system 1100 including a device 1105 that supports sidelink IDC interference mitigation, according to one or more aspects of the present disclosure. Device 1105 may be an example of, or include components of, device 805, device 905, or UE 115, as described herein. Device 1105 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. Device 1105 may include components for two-way voice and data communication, including components for sending and receiving communications, such as a communication manager 1120, an input / output (I / O) controller 1110, a transceiver 1115, an antenna 1125, memory 1130, code 1135, and a processor 1140. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, or electrically) via one or more buses (e.g., bus 1145).

[0188] I / O controller 1110 can manage input and output signals for device 1105. I / O controller 1110 can also manage peripheral devices that are not integrated into device 1105. In some cases, I / O controller 1110 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1110 can utilize an operating system such as iOS. ® ANDROID ® , MS-DOS ® 、MS-WINDOWS ® , OS / 2® , UNIX ® 、LINUX ® or another known operating system. Additionally or alternatively, I / O controller 1110 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 1110 may be implemented as part of a processor, such as processor 1140. In some cases, a user may interact with device 1105 via I / O controller 1110 or via hardware components controlled by I / O controller 1110.

[0189] In some cases, device 1105 may include a single antenna 1125. However, in some other cases, device 1105 may have more than one antenna 1125, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 1115 may communicate bidirectionally via one or more antennas 1125, a wired link, or a wireless link as described herein. For example, transceiver 1115 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 1115 may also include a modem for modulating packets; providing the modulated packets to one or more antennas 1125 for transmission; and demodulating packets received from one or more antennas 1125. Transceiver 1115, or transceiver 1115 and one or more antennas 1125, may be examples of transmitter 815, transmitter 915, receiver 810, receiver 910, or any combination thereof, or components thereof, as described herein.

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

[0191] Processor 1140 may include an intelligent hardware device (e.g., a general-purpose processor, DSP, CPU, microcontroller, ASIC, FPGA, programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 1140 may be configured to operate a memory array using a memory controller. In other cases, the memory controller may be integrated into processor 1140. Processor 1140 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1130) to cause device 1105 to perform various functions (e.g., functions or tasks supporting sidelink IDC interference mitigation). For example, device 1105 or a component of device 1105 may include processor 1140 and memory 1130 coupled to or to processor 1140, with processor 1140 and memory 1130 configured to perform the various functions described herein.

[0192] According to examples disclosed herein, the communication manager 1120 may support wireless communications at a first UE. For example, the communication manager 1120 may be configured as or otherwise support means for receiving report information indicating IDC interference from a second UE. The communication manager 1120 may be configured as or otherwise support means for receiving a resource reservation message indicating a set of sidelink resources from the second UE. The communication manager 1120 may be configured as or otherwise support means for sending an IDC interference report to the second UE based on the report information, the IDC interference report indicating IDC interference corresponding to at least a portion of the set of sidelink resources.

[0193] Additionally or alternatively, according to examples disclosed herein, the communication manager 1120 may support wireless communications at a first UE. For example, the communication manager 1120 may be configured as or otherwise support means for receiving a resource reservation message from a network entity, the resource reservation message indicating a set of sidelink resources for performing sidelink communications with at least a second UE. The communication manager 1120 may be configured as or otherwise support means for communicating with the second UE based on the resource reservation message. The communication manager 1120 may be configured as or otherwise support means for sending an IDC interference report to the network entity based on performing sidelink communications, the IDC interference report indicating IDC interference corresponding to at least a portion of the set of sidelink resources.

[0194] By including or configuring a communication manager 1120 according to examples described herein, the device 1105 can support techniques for IDC interference reporting and mitigation, thereby improving communication reliability, reducing system latency, improving user experience, reducing signaling overhead, and improving user experience.

[0195] In some examples, the communication manager 1120 can be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise coordinating with the transceiver 1115, one or more antennas 1125, or any combination thereof. Although the communication manager 1120 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1120 can be supported or performed by the processor 1140, the memory 1130, the code 1135, or any combination thereof. For example, the code 1135 can include instructions that are executable by the processor 1140 to cause the device 1105 to perform various aspects of sidelink IDC interference mitigation as described herein, or the processor 1140 and the memory 1130 can be otherwise configured to perform or support such operations.

[0196] Figure 12 A flowchart is illustrated that illustrates a method 1200 for supporting sidelink IDC interference mitigation according to one or more aspects of the present disclosure. The operations of the method 1200 may be implemented by a UE or components thereof as described herein. For example, the operations of the method 1200 may be implemented by a UE or components thereof as described herein. Figures 1 to 11 The described functions may be performed by the UE 115. 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.

[0197] At 1205, the method may include receiving report information indicating IDC interference from the second UE. The operations of 1205 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1205 may be performed as described in reference to Figure 10 The described IDC interference information manager 1025 is executed.

[0198] At 1210, the method may include receiving a resource reservation message indicating a set of sidelink resources from a second UE. The operations of 1210 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1210 may be performed as described in reference to Figure 10 The resource reservation manager 1030 described is executed.

[0199] At 1215, the method may include: sending an IDC interference report to the second UE based on the reporting information, the IDC interference report indicating IDC interference corresponding to at least a portion of the set of side link resources. The operations of 1215 may be performed according to the examples disclosed herein. In some examples, aspects of the operations of 1215 may be performed as described in reference to Figure 10 The IDC interference reporting manager 1035 described herein is executed.

[0200] Figure 13A flowchart is illustrated that illustrates a method 1300 for supporting sidelink IDC interference mitigation according to one or more aspects of the present disclosure. The operations of the method 1300 may be implemented by a UE or components thereof as described herein. For example, the operations of the method 1300 may be implemented by a UE or components thereof as described herein. Figures 1 to 11 The described functions may be performed by the UE 115. 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.

[0201] At 1305, the method may include receiving report information indicating IDC interference from the second UE. The operations of 1305 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1305 may be performed as described in reference to Figure 10 The described IDC interference information manager 1025 is executed.

[0202] At 1310, the method may include receiving a resource reservation message indicating a set of sidelink resources from a second UE. The operations of 1310 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1310 may be performed as described in reference to Figure 10 The resource reservation manager 1030 described is executed.

[0203] At 1315, the method may include monitoring sidelink signaling from the second UE based on the resource reservation message. The operations of 1315 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1315 may be performed as described in reference to Figure 10 The described IDC detection manager 1055 is executed.

[0204] At 1320, the method may include detecting IDC interference on at least the portion of the set of side link resources based on the monitoring. The operations of 1320 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1320 may be performed as described in reference to Figure 10 The described IDC detection manager 1055 is executed.

[0205] At 1325, the method may include: sending an IDC interference report to the second UE based on the reporting information, the IDC interference report indicating IDC interference corresponding to at least a portion of the set of sidelink resources, wherein sending the IDC interference report is based on detecting the IDC interference. The operations of 1325 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1325 may be performed as described in reference to Figure 10 The IDC interference reporting manager 1035 described herein is executed.

[0206] Figure 14A flowchart is illustrated that illustrates a method 1400 for supporting sidelink IDC interference mitigation according to one or more aspects of the present disclosure. The operations of the method 1400 may be implemented by a UE or components thereof as described herein. For example, the operations of the method 1400 may be implemented by a UE or components thereof as described herein. Figures 1 to 11 The described functions may be performed by the UE 115. 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.

[0207] At 1405, the method may include receiving a resource reservation message from a network entity, the resource reservation message indicating a set of sidelink resources for performing sidelink communications with at least a second UE. 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 10 The resource reservation manager 1030 described is executed.

[0208] At 1410, the method may include communicating with the second UE according to the resource reservation message. The operations of 1410 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1410 may be performed as described in reference to Figure 10 The sidelink communication manager 1040 described is executed.

[0209] At 1415, the method may include: sending an IDC interference report to a network entity based on performing the sidelink communication, the IDC interference report indicating IDC interference corresponding to at least a portion of the set of sidelink resources. The operations of 1415 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1415 may be performed as described in reference to Figure 10 The IDC interference reporting manager 1035 described herein is executed.

[0210] Figure 15 A flowchart is illustrated that illustrates a method 1500 for supporting sidelink IDC interference mitigation according to one or more aspects of the present disclosure. The operations of the method 1500 may be implemented by a UE or components thereof as described herein. For example, the operations of the method 1500 may be implemented by a UE or components thereof as described herein. Figures 1 to 11 The described functions may be performed by the UE 115. 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.

[0211] At 1505, the method may include receiving a resource reservation message from a network entity, the resource reservation message indicating a set of sidelink resources for performing sidelink communications with at least a second UE. 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 10 The resource reservation manager 1030 described is executed.

[0212] At 1510, the method may include communicating with the second UE according to the resource reservation message. 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 10 The sidelink communication manager 1040 described is executed.

[0213] At 1515, the method may include receiving an indication of IDC interference from the second UE, wherein sending the IDC interference report includes forwarding the indication of IDC interference to the network entity. 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 10 The IDC interference reporting manager 1035 described herein is executed.

[0214] At 1520, the method may include forwarding an indication of IDC interference to a network entity based on performing the sidelink communication, the indication of IDC interference indicating IDC interference corresponding to at least a portion of the set of sidelink resources. 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 with reference to Figure 10 The IDC interference reporting manager 1035 described herein is executed.

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

[0216] Aspect 1: A method for wireless communication at a first UE, the method comprising: receiving report information indicating in-device coexistence interference from a second UE; receiving a resource reservation message indicating a set of side link resources from the second UE; and sending an in-device coexistence interference report to the second UE based on the report information, the in-device coexistence interference report indicating in-device coexistence interference corresponding to at least a portion of the set of side link resources.

[0217] Aspect 2: The method according to aspect 1, wherein receiving the report information includes: receiving sidelink RRC signaling including the report information, wherein the report information includes an indication that in-device coexistence interference reporting by the first UE is enabled.

[0218] Aspect 3: According to the method according to Aspect 2, the method also includes: receiving in the sidelink RRC signaling an indication of a center frequency around which the first UE is requested to report the in-device co-existence interference, an indication of a sidelink resource pool for reporting the in-device co-existence interference, an indication of one or more subchannels associated with reporting the in-device co-existence interference, an indication of one or more active sidelink bandwidth parts or inactive sidelink bandwidth parts corresponding to the in-device co-existence interference, or any combination thereof.

[0219] Aspect 4: The method according to any one of aspects 1 to 3, wherein receiving the report information includes: receiving a measurement object configuration message, a sidelink assistance information message, or an inter-UE coordination information message.

[0220] Aspect 5: According to the method described in any one of Aspects 1 to 4, the method further includes: sending an indication of one or more carrier frequencies, one or more side link bandwidth parts, one or more side link resource pools, one or more side link subchannels, one or more side link physical resource blocks, frequency resource ranges or any combination thereof affected by the in-device coexistence interference in the in-device coexistence interference report.

[0221] Aspect 6: The method according to any one of aspects 1 to 5, wherein sending the in-device coexistence interference report includes: sending an indication of a link failure associated with the set of sidelink resources due to the in-device coexistence interference.

[0222] Aspect 7: According to the method described in any one of Aspects 1 to 6, the method further includes: receiving an event-triggered measurement object configuration in the reporting information; and detecting the in-device coexistence interference based at least in part on monitoring the set of side link resources according to the event-triggered measurement object configuration, wherein sending the in-device coexistence interference report includes sending a MAC control element (CE) based at least in part on detecting the in-device coexistence interference.

[0223] Aspect 8: The method according to any one of aspects 1 to 7, wherein sending the in-device coexistence interference report includes: multicasting the in-device coexistence interference report to multiple sidelink UEs including the second UE.

[0224] Aspect 9: A method according to any one of Aspects 1 to 8, wherein sending the in-device coexistence interference report includes: sending an inter-UE coordination message, the inter-UE coordination message including an indication that multiple side link resources including at least the portion of the set of side link resources are non-preferred resources.

[0225] Aspect 10: The method according to aspect 9, further comprising: receiving a request for an indication of non-preferred resources from the second UE, wherein sending the inter-UE coordination message is based at least in part on receiving the request.

[0226] Aspect 11: The method according to any one of aspects 9 to 10 further comprises: receiving configuration information indicating one or more conditions, wherein sending the inter-UE coordination message is at least partially based on satisfying the one or more conditions.

[0227] Aspect 12: According to the method described in any one of Aspects 9 to 11, the method further includes: receiving an indication from the second UE that the second UE is capable of receiving the inter-UE coordination message, wherein sending the inter-UE coordination message is at least partially based on receiving the indication that the second UE is capable of receiving the inter-UE coordination message.

[0228] Aspect 13: The method according to any one of aspects 9 to 12, further comprising: sending an indication of the first subset of the plurality of sidelink resources that is not preferred due to in-device co-existence interference in the inter-UE coordination message.

[0229] Aspect 14: According to the method described in any one of Aspects 1 to 13, the method further includes: monitoring sidelink signaling from the second UE at least in part based on the resource reservation message; and detecting the in-device coexistence interference on at least the part of the set of sidelink resources at least in part based on the monitoring, wherein sending the in-device coexistence interference report is at least in part based on detecting the in-device coexistence interference.

[0230] Aspect 15: A method for performing wireless communications at a first UE, the method comprising: receiving a resource reservation message from a network entity, the resource reservation message indicating a set of sidelink resources for performing sidelink communications with at least a second UE; communicating with the second UE based on the resource reservation message; and sending an in-device coexistence interference report to the network entity based at least in part on performing the sidelink communications, the in-device coexistence interference report indicating in-device coexistence interference corresponding to at least a portion of the set of sidelink resources.

[0231] Aspect 16: The method of aspect 15, wherein sending the in-device coexistence interference report comprises sending a radio resource control message including an indication that at least the portion of the set of sidelink resources experiences the in-device coexistence interference.

[0232] Aspect 17: A method according to any one of Aspects 15 to 16, wherein sending the in-device coexistence interference report includes: sending a UE assistance information message, the UE assistance information message including an indication that at least the portion of the set of side link resources experiences the in-device coexistence interference.

[0233] Aspect 18: The method according to any one of Aspects 15 to 17, further comprising: receiving an indication of the in-device coexistence interference from the second UE, wherein sending the in-device coexistence interference report comprises forwarding the indication of the in-device coexistence interference to the network entity.

[0234] Aspect 19: A method according to any one of Aspects 15 to 18, wherein sending the in-device coexistence interference report includes: sending an indication of the in-device coexistence interference impact associated with the set of side link resources of the first radio access technology on wireless communications via the second radio access technology.

[0235] Aspect 20: According to the method described in any one of Aspects 15 to 19, the method further includes: sending an indication of one or more carrier frequencies, one or more side link bandwidth parts, one or more side link resource pools, one or more side link subchannels, one or more side link physical resource blocks, frequency resource ranges or any combination thereof affected by the in-device coexistence interference in the in-device coexistence interference report.

[0236] Aspect 21: An apparatus for performing wireless communication at a first 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 14.

[0237] Aspect 22: An apparatus for wireless communication at a first UE, the apparatus comprising at least one component for performing the method according to any one of aspects 1 to 14.

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

[0239] Aspect 24: An apparatus for wireless communication at a first 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 15 to 20.

[0240] Aspect 25: An apparatus for wireless communication at a first UE, the apparatus comprising at least one component for performing the method according to any one of aspects 15 to 20.

[0241] Aspect 26: A non-transitory computer-readable medium storing code for wireless communication at a first UE, the code comprising instructions executable by a processor to perform the method according to any one of aspects 15 to 20.

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

[0243] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and the terminology of LTE, LTE-A, LTE-A Pro, or NR may be used throughout 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.

[0244] The information and signals described herein may be represented by any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips referred to throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0245] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or executed using a general purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration).

[0246] The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored as one or more instructions or codes of a computer-readable medium, or sent using one or more instructions or codes of a computer-readable medium. Other examples and 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 a combination of any of these. Features that implement the functions may also be physically located at different locations, including being distributed so that various parts of the functions are implemented at different physical locations.

[0247] Computer-readable media includes both non-transitory computer storage media and communication media, including any media that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer. By way of example and not limitation, non-transitory computer-readable media can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwaves, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwaves are included within the definition of computer-readable media. As used herein, disk and disc include CDs, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs. Disks can reproduce data magnetically, and discs can reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0248] 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, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). 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 this 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."

[0249] The term "determining" encompasses a variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, searching (such as by searching in a table, database, or other data structure), ascertaining, and the like. Furthermore, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), and the like. Furthermore, "determining" may include resolving, retrieving, selecting, choosing, establishing, and other such similar actions.

[0250] 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 similar components. If only the first reference label is used in the specification, the description can apply to any of the similar components having the same first reference label, regardless of the second reference label or other subsequent reference labels.

[0251] The description set forth herein in conjunction with the accompanying drawings describes example configurations and does not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," rather than "preferred" or "having advantages over other examples." The detailed description includes specific details to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0252] The description herein is provided to enable one of ordinary skill in the art to make or use the present disclosure. Various modifications to the present disclosure will be apparent to those 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. Thus, the present disclosure is not limited to the examples and designs described herein, but should be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. An apparatus for wireless communication at a first user equipment (UE), the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: receiving, from a second UE, report information indicating in-device coexistence interference; receiving a resource reservation message indicating a set of sidelink resources from the second UE; as well as An in-device coexistence interference report is sent to the second UE according to the reporting information, where the in-device coexistence interference report indicates in-device coexistence interference corresponding to at least a portion of the set of sidelink resources.

2. The apparatus of claim 1 , wherein the instructions for receiving the report information are executable by the processor to cause the apparatus to: Sidelink radio resource control signaling including the reporting information is received, wherein the reporting information includes an indication that in-device coexistence interference reporting by the first UE is enabled.

3. The apparatus of claim 2, wherein the instructions are further executable by the processor to cause the apparatus to: Receiving, in the sidelink radio resource control signaling, an indication of a center frequency around which the first UE is requested to report the in-device coexistence interference, an indication of a sidelink resource pool for reporting the in-device coexistence interference, an indication of one or more subchannels associated with reporting the in-device coexistence interference, an indication of one or more active sidelink bandwidth parts or inactive sidelink bandwidth parts corresponding to the in-device coexistence interference, or any combination thereof.

4. The apparatus of claim 1 , wherein the instructions for receiving the report information are executable by the processor to cause the apparatus to: Receive a measurement object configuration message, a sidelink assistance information message, or an inter-UE coordination information message.

5. The apparatus of claim 1 , wherein the instructions are further executable by the processor to cause the apparatus to: An indication of one or more carrier frequencies, one or more sidelink bandwidth parts, one or more sidelink resource pools, one or more sidelink subchannels, one or more sidelink physical resource blocks, frequency resource ranges, or any combination thereof, affected by the in-device coexistence interference is sent in the in-device coexistence interference report.

6. The apparatus of claim 1 , wherein the instructions for sending the in-device coexistence interference report are executable by the processor to cause the apparatus to: An indication of a link failure associated with the set of sidelink resources due to the in-device coexistence interference is sent.

7. The apparatus of claim 1 , wherein the instructions are further executable by the processor to cause the apparatus to: receiving an event-triggered measurement object configuration in the report information; and The in-device coexistence interference is detected based at least in part on monitoring the set of sidelink resources according to the measurement object configuration triggered by the event, wherein sending the in-device coexistence interference report comprises sending a medium access control (MAC) control element (CE) based at least in part on detecting the in-device coexistence interference.

8. The apparatus of claim 1 , wherein the instructions for sending the in-device coexistence interference report are executable by the processor to cause the apparatus to: The in-device coexistence interference report is multicasted to a plurality of sidelink UEs including the second UE.

9. The apparatus of claim 1 , wherein the instructions for sending the in-device coexistence interference report are executable by the processor to cause the apparatus to: An inter-UE coordination message is sent, the inter-UE coordination message including an indication that a plurality of sidelink resources including at least the portion of the set of sidelink resources are non-preferred resources.

10. The apparatus of claim 9, wherein the instructions are further executable by the processor to cause the apparatus to: A request for an indication of non-preferred resources is received from the second UE, wherein sending the inter-UE coordination message is based at least in part on receiving the request.

11. The apparatus of claim 9, wherein the instructions are further executable by the processor to cause the apparatus to: Configuration information is received indicating one or more conditions, wherein sending the inter-UE coordination message is based at least in part on satisfying the one or more conditions.

12. The apparatus of claim 9, wherein the instructions are further executable by the processor to cause the apparatus to: An indication is received from the second UE that the second UE is capable of receiving the inter-UE coordination message, wherein sending the inter-UE coordination message is based at least in part on receiving the indication that the second UE is capable of receiving the inter-UE coordination message.

13. The apparatus of claim 9, wherein the instructions are further executable by the processor to cause the apparatus to: An indication of a first subset of the plurality of sidelink resources that is not preferred due to in-device coexistence interference is sent in the inter-UE coordination message.

14. The apparatus of claim 1 , wherein the instructions are further executable by the processor to cause the apparatus to: monitoring sidelink signaling from the second UE based at least in part on the resource reservation message; and The in-device coexistence interference on at least the portion of the set of sidelink resources is detected based at least in part on the monitoring, wherein sending the in-device coexistence interference report is based at least in part on detecting the in-device coexistence interference.

15. An apparatus for wireless communication at a first user equipment (UE), the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: receiving a resource reservation message from a network entity, the resource reservation message indicating a set of sidelink resources for performing sidelink communications with at least a second UE; communicating with the second UE according to the resource reservation message; as well as An in-device coexistence interference report is sent to the network entity based at least in part on performing the sidelink communication, the in-device coexistence interference report indicating in-device coexistence interference corresponding to at least a portion of the set of sidelink resources.

16. The apparatus of claim 15, wherein the instructions for sending the in-device coexistence interference report are executable by the processor to cause the apparatus to: A radio resource control message is sent, the radio resource control message including an indication that at least the portion of the set of sidelink resources is experiencing the in-device coexistence interference.

17. The apparatus of claim 15, wherein the instructions for sending the in-device coexistence interference report are executable by the processor to cause the apparatus to: A UE assistance information message is sent, the UE assistance information message including an indication that at least the portion of the set of sidelink resources experiences the in-device coexistence interference.

18. The apparatus of claim 15, wherein the instructions are further executable by the processor to cause the apparatus to: An indication of the in-device coexistence interference is received from the second UE, wherein sending the in-device coexistence interference report comprises forwarding the indication of the in-device coexistence interference to the network entity.

19. The apparatus of claim 15, wherein the instructions for sending the in-device coexistence interference report are executable by the processor to cause the apparatus to: An indication is sent that the in-device coexistence interference associated with the set of sidelink resources of the first radio access technology affects wireless communications via the second radio access technology.

20. The apparatus of claim 15, wherein the instructions are further executable by the processor to cause the apparatus to: An indication of one or more carrier frequencies, one or more sidelink bandwidth parts, one or more sidelink resource pools, one or more sidelink subchannels, one or more sidelink physical resource blocks, frequency resource ranges, or any combination thereof, affected by the in-device coexistence interference is sent in the in-device coexistence interference report.

21. A method for wireless communication at a first user equipment (UE), the method comprising: receiving, from a second UE, report information indicating in-device coexistence interference; receiving a resource reservation message indicating a set of sidelink resources from the second UE; as well as An in-device coexistence interference report is sent to the second UE according to the reporting information, where the in-device coexistence interference report indicates in-device coexistence interference corresponding to at least a portion of the set of sidelink resources.

22. The method of claim 21, wherein receiving the report information comprises: Sidelink radio resource control signaling including the reporting information is received, wherein the reporting information includes an indication that in-device coexistence interference reporting by the first UE is enabled.

23. The method of claim 21, wherein receiving the report information comprises: Receive a measurement object configuration message, a sidelink assistance information message, or an inter-UE coordination information message.

24. The method according to claim 21, further comprising: An indication of one or more carrier frequencies, one or more sidelink bandwidth parts, one or more sidelink resource pools, one or more sidelink subchannels, one or more sidelink physical resource blocks, frequency resource ranges, or any combination thereof, affected by the in-device coexistence interference is sent in the in-device coexistence interference report.

25. The method of claim 21 , wherein sending the in-device coexistence interference report comprises: An indication of a link failure associated with the set of sidelink resources due to the in-device coexistence interference is sent.

26. The method according to claim 21, further comprising: receiving an event-triggered measurement object configuration in the report information; as well as The in-device coexistence interference is detected based at least in part on monitoring the set of sidelink resources according to the measurement object configuration triggered by the event, wherein sending the in-device coexistence interference report comprises sending a medium access control (MAC) control element (CE) based at least in part on detecting the in-device coexistence interference.

27. The method of claim 21 , wherein sending the in-device coexistence interference report comprises: The in-device coexistence interference report is multicasted to a plurality of sidelink UEs including the second UE.

28. The method of claim 21 , wherein sending the in-device coexistence interference report comprises: An inter-UE coordination message is sent, the inter-UE coordination message including an indication that a plurality of sidelink resources including at least the portion of the set of sidelink resources are non-preferred resources.

29. The method according to claim 21, further comprising: monitoring sidelink signaling from the second UE based at least in part on the resource reservation message; as well as The in-device coexistence interference on at least the portion of the set of sidelink resources is detected based at least in part on the monitoring, wherein sending the in-device coexistence interference report is based at least in part on detecting the in-device coexistence interference.

30. A method for wireless communication at a first user equipment (UE), the method comprising: receiving a resource reservation message from a network entity, the resource reservation message indicating a set of sidelink resources for performing sidelink communications with at least a second UE; communicating with the second UE according to the resource reservation message; as well as An in-device coexistence interference report is sent to the network entity based at least in part on performing the sidelink communication, the in-device coexistence interference report indicating in-device coexistence interference corresponding to at least a portion of the set of sidelink resources.

Images