Hybrid automatic repeat request identifier determination associated with cross-link interference measurements

Abstract

Various aspects of the present disclosure generally relate to wireless communications. Various aspects relate generally to hybrid automatic repeat request (HARQ) identifier determination associated with cross-link interference (CLI) measurements. Some aspects more specifically relate to processing of HARQ identifier determination for communications that are discarded due to collisions with CLI measurements. In some aspects, a user equipment (UE) and / or a network node may skip incrementation of a value of a HARQ identifier for communications that are discarded due to conflicts with CLI measurements. Where the scheduling information indicates a single HARQ identifier or is associated with a single HARQ identifier, the UE and / or network node may not incremented HARQ identifiers for communications from the plurality of communications that are discarded due to conflicts with CLI measurements.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. non-provisional patent application No. 18 / 174,162, filed on February 24, 2023, entitled “HYBRID AUTOMATIC REPEATREQUEST IDENTIFIER DETERMINATION ASSOCIATED WITH CROSS-LINK INTERFERENCEMEASUREMENTS,” which is hereby expressly incorporated herein by reference. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications, and more particularly to techniques and apparatus associated with hybrid automatic repeat request (HARQ) identifier determination associated with cross-link interference (CLI) measurements. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth or transmit power). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0005] The above multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region, or global level. New Radio (NR) (which may be referred to as 5G) is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with a cyclic prefix (CP) on the downlink, CP-OFDM or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM) on the uplink, and supporting beamforming, multiple-input multiple-output (MIMO) antenna technology and carrier aggregation to improve spectrum efficiency, reduce costs, improve services, utilize new spectrum, and better integrate with other open standards. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR, and other radio access technologies remain useful.

[0006] The Hybrid Automatic Repeat Request (HARQ) process refers to a retransmission protocol in which the receiver checks for errors in received data and, if an error is detected, buffers the received data and requests retransmission from the transmitter. The HARQ receiver can then combine the buffered received data with the retransmitted data before channel decoding and error detection, which improves retransmission performance. Multiple HARQ processes can be used to avoid the impact of round-trip time on throughput. That is, other HARQ processes can transmit data while a given HARQ process is waiting for acknowledgment.

[0007] In some examples, a receiver (e.g., a user equipment (UE)) may apply or assign a HARQ identifier to a first scheduled communication in a timely manner. For example, the UE may increment the indicated HARQ identifier to determine the HARQ identifier for other communications scheduled by the scheduling information. This reduces the size of the scheduling information and reduces the signaling overhead associated with using a single communication to schedule multiple communications. Synchronization of the HARQ identifier between the transmitter and the receiver is important for ensuring that the HARQ process can be performed accurately. For example, a UE or a network node may use the HARQ identifier to track or identify data in a buffer so that the UE or network node can retransmit the data and / or combine the buffered data with the retransmitted data. If the HARQ identifier is incorrectly assigned or tracked, the UE or network node may retransmit incorrect data and / or may attempt to combine the buffered data with irrelevant retransmitted data. This may result in errors when decoding and / or receiving data. Additionally, incorrectly assigning or tracking a HARQ identifier may cause subsequent HARQ identifiers that are based on or otherwise associated with (eg, incremented from) the HARQ identifier to also be incorrect.

[0008] In some examples, communications (e.g., from multiple communications scheduled by a single downlink control information (DCI) communication or other scheduling information) may be dropped for reasons that are not associated with a high risk of missed detection (e.g., uplink dynamic signaling, as described in more detail elsewhere herein) (e.g., other than being associated with a time slot or symbol associated with a conflicting communication direction). For example, a UE may drop (e.g., not send or receive) a communication based on or otherwise associated with a configured cross-link interference (CLI) measurement resource. CLI in wireless communications refers to a scenario where two or more radio links operating at similar frequencies and / or in close proximity to each other interfere with each other, resulting in performance degradation of each link. However, if the dropped communication is a communication that is co-scheduled with multiple communications, the UE and the network node may be out of sync in processing the HARQ identifiers associated with the multiple communications. Summary of the Invention

[0009] Some aspects described herein relate to a user equipment (UE) for wireless communication. The UE may include at least one memory and at least one processor communicatively coupled to the at least one memory. The at least one processor may be operable to cause the UE to: receive, from a network node, a configuration associated with cross-link interference, the configuration indicating one or more time domain resources associated with cross-link interference (CLI) measurement. The at least one processor may be operable to cause the UE to: receive, from the network node, scheduling information associated with scheduling multiple communications, the scheduling information identifying a hybrid automatic repeat request (HARQ) identifier, and the scheduling information indicating that resources associated with a first one or more communications in the multiple communications do not overlap with the one or more time domain resources in a time domain, and that resources associated with a second one or more communications in the multiple communications at least partially overlap with the one or more time domain resources associated with the CLI measurement in the time domain. The at least one processor may be operable to cause the UE to: communicate, with the network node, the first one or more communications associated with corresponding HARQ identifiers identified by incrementing the value of the HARQ identifier used only for the first one or more communications.

[0010] Some aspects described herein relate to a network node for wireless communications. The network node may include at least one memory and at least one processor communicatively coupled to the at least one memory. The at least one processor may be operable to cause the network node to: transmit a configuration associated with cross-link interference for a UE, the configuration indicating one or more time domain resources associated with CLI measurement. The at least one processor may be operable to cause the network node to: transmit scheduling information associated with scheduling multiple communications for the UE, the scheduling information identifying a HARQ identifier and indicating that resources associated with a first one or more communications in the multiple communications do not overlap with the one or more time domain resources in a time domain, and that resources associated with a second one or more communications in the multiple communications at least partially overlap with the one or more time domain resources associated with the CLI measurement in the time domain. The at least one processor may be operable to cause the network node to: convey the first one or more communications associated with the UE, the first one or more communications being associated with a corresponding HARQ identifier identified by incrementing the value of the HARQ identifier used only for the first one or more communications.

[0011] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include: receiving a configuration associated with cross-link interference from a network node, the configuration indicating one or more time domain resources associated with CLI measurement. The method may include: receiving scheduling information associated with scheduling multiple communications from the network node, the scheduling information identifying a HARQ identifier, and the scheduling information indicating: resources associated with a first one or more communications in the multiple communications do not overlap with the one or more time domain resources in the time domain, and resources associated with a second one or more communications in the multiple communications at least partially overlap with the one or more time domain resources associated with the CLI measurement in the time domain. The method may include: communicating the first one or more communications with the network node, the first one or more communications being associated with a corresponding HARQ identifier identified by incrementing the value of the HARQ identifier used only for the first one or more communications.

[0012] Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include: sending a configuration associated with cross-link interference for a UE, the configuration indicating one or more time domain resources associated with CLI measurement. The method may include: sending scheduling information associated with scheduling multiple communications for the UE, the scheduling information identifying a HARQ identifier, and the scheduling information indicating that resources associated with a first one or more communications in the multiple communications do not overlap with the one or more time domain resources in the time domain, and resources associated with a second one or more communications in the multiple communications at least partially overlap with the one or more time domain resources associated with the CLI measurement in the time domain. The method may include: conveying the first one or more communications associated with the UE, the first one or more communications being associated with a corresponding HARQ identifier identified by incrementing the value of the HARQ identifier used only for the first one or more communications.

[0013] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to: receive, from a network node, a configuration associated with cross-link interference, the configuration indicating one or more time-domain resources associated with CLI measurement. The set of instructions, when executed by the one or more processors of the UE, may cause the UE to: receive, from the network node, scheduling information associated with scheduling multiple communications, the scheduling information identifying a HARQ identifier, and indicating that resources associated with a first one or more communications in the multiple communications do not overlap with the one or more time-domain resources in a time domain, and that resources associated with a second one or more communications in the multiple communications at least partially overlap with the one or more time-domain resources associated with the CLI measurement in the time domain. The set of instructions, when executed by the one or more processors of the UE, may cause the UE to: communicate, with the network node, the first one or more communications associated with corresponding HARQ identifiers identified by incrementing a value of the HARQ identifier used only for the first one or more communications.

[0014] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network node. The set of instructions, when executed by one or more processors of the network node, may cause the network node to: transmit a configuration associated with cross-link interference for a UE, the configuration indicating one or more time domain resources associated with CLI measurement. The set of instructions, when executed by the one or more processors of the network node, may cause the network node to: transmit scheduling information associated with scheduling multiple communications for the UE, the scheduling information identifying a HARQ identifier and indicating that resources associated with a first one or more communications in the multiple communications do not overlap with the one or more time domain resources in a time domain, and that resources associated with a second one or more communications in the multiple communications at least partially overlap with the one or more time domain resources associated with the CLI measurement in the time domain. The set of instructions, when executed by the one or more processors of the network node, may cause the network node to: communicate the first one or more communications associated with the UE, the first one or more communications associated with a corresponding HARQ identifier identified by incrementing a value of the HARQ identifier used only for the first one or more communications.

[0015] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a configuration associated with cross-link interference from a network node, the configuration indicating one or more time domain resources associated with CLI measurement. The apparatus may include means for receiving scheduling information associated with scheduling multiple communications from the network node, the scheduling information identifying a HARQ identifier, and the scheduling information indicating that resources associated with a first one or more communications in the multiple communications do not overlap with the one or more time domain resources in a time domain, and that resources associated with a second one or more communications in the multiple communications at least partially overlap with the one or more time domain resources associated with the CLI measurement in the time domain. The apparatus may include means for communicating the first one or more communications to the network node, the first one or more communications being associated with corresponding HARQ identifiers identified by incrementing the value of the HARQ identifier used only for the first one or more communications.

[0016] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include a component for transmitting a configuration associated with cross-link interference for a UE, the configuration indicating one or more time domain resources associated with CLI measurement. The apparatus may include a component for transmitting scheduling information associated with scheduling multiple communications for the UE, the scheduling information identifying a HARQ identifier, and the scheduling information indicating that resources associated with a first one or more communications in the multiple communications do not overlap with the one or more time domain resources in a time domain, and resources associated with a second one or more communications in the multiple communications at least partially overlap with the one or more time domain resources associated with the CLI measurement in the time domain. The apparatus may include a component for conveying the first one or more communications associated with the UE, the first one or more communications being associated with a corresponding HARQ identifier identified by incrementing the value of the HARQ identifier used only for the first one or more communications.

[0017] Aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network nodes, network entities, wireless communication devices, or processing systems as fully described with reference to the accompanying drawings and description and as illustrated in the accompanying drawings and description.

[0018] The foregoing has broadly outlined the features and technical advantages of the examples according to the present disclosure in an effort to make the following detailed description better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples can be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. When considered in conjunction with the accompanying drawings, the characteristics of the concepts disclosed herein (both their organization and method of operation) and the associated advantages will be better understood from the following description. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description and not as a definition of limitations to the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] In order to fully understand the above-mentioned features of the present disclosure, a more particular description of the invention briefly summarized above may be obtained by reference to various aspects (some of which are illustrated in the accompanying drawings). It should be noted, however, that the accompanying drawings illustrate only some typical aspects of the present disclosure and are not to be considered limiting of its scope, as the description may admit to other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0020] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0021] Figure 2is a diagram illustrating communication between an example network node and a user equipment (UE) in a wireless network according to the present disclosure.

[0022] Figure 3 is a diagram illustrating an example associated with cross-link interference (CLI) detection and mitigation according to the present disclosure.

[0023] Figure 4 is a diagram illustrating an example associated with multi-communication scheduling according to the present disclosure.

[0024] Figure 5 is a diagram of an example of an association of a hybrid automatic repeat request (HARQ) identifier determination associated with a CLI measurement according to the present disclosure.

[0025] Figure 6 is a diagram of an example associated with HARQ identifier determination associated with CLI measurement according to the present disclosure.

[0026] Figure 7 is a diagram of an example associated with HARQ identifier determination associated with CLI measurement according to the present disclosure.

[0027] Figure 8 is a flow chart illustrating an example process, performed, for example, by a UE, to support HARQ identifier determination associated with CLI measurements according to the present disclosure.

[0028] Figure 9 is a flow chart illustrating an example process, eg, performed by a network node, to support HARQ identifier determination associated with CLI measurements in accordance with the present disclosure.

[0029] Figure 10 is an illustration of an example apparatus for wireless communication supporting HARQ identifier determination associated with CLI measurements according to the present disclosure.

[0030] Figure 11 is an illustration of an example apparatus for wireless communication supporting HARQ identifier determination associated with CLI measurements according to the present disclosure. DETAILED DESCRIPTION

[0031] Various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms and should not be interpreted as being limited to any specific structure or function presented throughout the present disclosure. Instead, these aspects are provided so that the present disclosure will be thorough and complete, and the scope of protection of the present disclosure will be fully conveyed to those skilled in the art. It will be appreciated by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the present disclosure. For example, any amount of aspects set forth herein can be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods implemented using other structures, functionality, or structure and functionality in addition to or different from the various aspects of the disclosure set forth herein. Any aspect of the present disclosure disclosed herein may be embodied by one or more elements of a claim.

[0032] Several aspects of telecommunications systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms (collectively, "elements"). These elements may be implemented using hardware, software, or a combination of hardware and software. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0033] In some examples, one or more restrictions associated with communications that overlap or occur in the vicinity of a cross-link interference (CLI) measurement in the time domain may be configured and / or defined (e.g., by a wireless communication standard). For example, one or more scheduling availability restrictions may define user equipment (UE) behavior for conflicts between scheduled communications and CLI measurements. One or more scheduling availability restrictions may define valid communications and invalid communications. "Valid" communications may be scheduled or configured communications that are available (e.g., that the UE is expected to receive or send). "Invalid" communications or "restricted" communications may be communications that are unavailable (e.g., that the UE is not expected to receive or send), such as indicated by one or more scheduling availability restrictions. The UE may discard (e.g., refrain from sending or receiving) invalid communications or restricted communications.

[0034] However, if the dropped communication is a communication co-scheduled with multiple communications, the UE and the network node may not synchronize their processing of the hybrid automatic repeat request (HARQ) identifiers associated with the multiple communications. For example, the process of incrementing or determining the HARQ identifiers for multiple communications when a communication is dropped due to a conflict with a CLI measurement is not defined. As a result, the UE and the network node may perform different operations (e.g., increment or not increment) on the HARQ identifier associated with the dropped communication due to at least partial overlap in the time domain with resources associated with the CLI measurement. This may result in errors associated with the HARQ processes for the dropped communication and for other communications included in the multiple communications. Additionally, this may result in the UE and the network node unnecessarily using or applying the HARQ identifier for the dropped communication.

[0035] Various aspects generally relate to HARQ identifier determination associated with CLI measurements. Some aspects more specifically relate to handling of HARQ identifier determination for communications that are dropped (e.g., not sent or received) due to overlap with CLI measurements in the time domain. For example, the dropped communication may be a communication scheduled together with multiple communications, such as via a single downlink control information (DCI) communication or as part of another semi-static configuration (such as a semi-persistent scheduling (SPS) configuration or a configuration grant (CG) configuration). In some aspects, a UE and / or a network node may drop (e.g., may not expect to receive or send) a communication because the time domain resources of the communication at least partially overlap with time domain resources associated with CLI measurements (e.g., CLI measurement resources and / or time slots associated with CLI measurements). In some aspects, the UE and / or the network node may avoid incrementing the value of the HARQ identifier for communications that are dropped due to a collision with a CLI measurement (e.g., in the time domain). In other words, for scheduling information associated with scheduling multiple communications, where the scheduling information indicates a single HARQ identifier or is associated with a single HARQ identifier, the UE and / or network node may not increment the HARQ identifier from the multiple communications for communications that are dropped due to a conflict with the CLI measurement (e.g., in the time domain).

[0036] Certain aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, the described techniques can be used to synchronize the processing of HARQ identifier determination between a UE and a network node when a communication is dropped (e.g., not sent or received) due to a conflict with a CLI measurement. This ensures that there is no misalignment of HARQ identifiers between the UE and the network node, ensures that there is no oversize of the HARQ identifiers (e.g., the HARQ identifiers are not assigned to communications or opportunities that are not actually sent or received), and ensures that the HARQ identifiers are used continuously by the UE and the network node, thereby reducing complexity and simplifying the management of the HARQ process, etc.

[0037] Figure 1 1 is a diagram illustrating an example of a wireless network according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network or elements of a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include one or more network nodes 110 (shown as network node (NN) 110a, network node 110b, network node 110c, and network node 110d), one UE 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other network entities. The network node 110 is an entity that communicates with the UE 120. As shown in the figure, the network node 110 may include one or more network nodes. For example, the network node 110 may be a converged network node, meaning that the converged network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). As another example, the network node 110 may be a disaggregated network node (sometimes referred to as a disaggregated base station), meaning that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed between two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0038] In some examples, network node 110 is or includes a network node (such as an RU) that communicates with UE 120 via a radio access link. In some examples, network node 110 is or includes a network node (such as a DU) that communicates with other network nodes 110 via a fronthaul link or a midhaul link. In some examples, network node 110 is or includes a network node (such as a CU) that communicates with other network nodes 110 via a midhaul link or communicates with a core network via a backhaul link. In some examples, network node 110 (such as a converged network node 110 or a decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, or one or more DUs. Network node 110 may include, for example, an NR network node, an LTE network node, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point or a transmit receive point (TRP), a DU, an RU, a CU, a mobility element of a network, a core network node, a network element, network equipment, and / or a RAN node. In some examples, network nodes 110 may be interconnected to each other or to one or more other network nodes 110 in wireless network 100 using any suitable transport network via various types of fronthaul interfaces, midhaul interfaces, or backhaul interfaces, such as direct physical connections, air interfaces, or virtual networks.

[0039] Each network node 110 may provide communication coverage for a particular geographic area. In the 3rd Generation Partnership Project (3GPP), the term "cell" may refer to a coverage area of ​​a network node 110 or a network node subsystem serving the coverage area, depending on the context in which the term is used.

[0040] The network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, or another type of cell. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs 120 with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a residence) and may allow restricted access by UEs 120 associated with the femto cell (e.g., UEs 120 in a closed subscriber group (CSG)). A network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell may be referred to as a pico network node. A network node 110 for a femto cell may be referred to as a femto network node or a home network node.

[0041] The wireless network 100 may be a heterogeneous network that includes different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, or relay network nodes. These different types of network nodes 110 may have different transmit power levels, different coverage areas, or different impacts on interference in the wireless network 100. For example, a macro network node may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico network node, a femto network node, and a relay network node may have a lower transmit power level (e.g., 0.1 watt to 2 watts). Figure 1 In the example shown, network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. A network node may support one or more (e.g., three) cells. In some examples, the cells may not necessarily be stationary, and the geographic area of ​​the cells may move depending on the location of a mobile network node 110 (e.g., a mobile network node).

[0042] In some aspects, the term "base station" or "network node" may refer to a converged base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, a "base station" or "network node" may refer to a CU, a DU, a RU, a near real-time (near-RT) RAN intelligent controller (RIC), and / or a non-real-time (non-RT) RIC. In some aspects, the term "base station" or "network node" may refer to a device configured to perform one or more functions, such as those described herein in conjunction with network node 110. In some aspects, the term "base station" or "network node" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of multiple different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to repeatedly perform at least a portion of the function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one of the base station functions but not another base station function. In this way, a single device may include more than one base station.

[0043] The network controller 130 may be coupled to or in communication with a set of network nodes 110 and may provide coordination and control for the network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link. The network nodes 110 may also communicate directly with each other or indirectly via a wireless backhaul communication link or a wired backhaul communication link. In some aspects, the network controller 130 may be a CU or a core network device, or the network controller 130 may include a CU or a core network device.

[0044] UEs 120 may be dispersed throughout wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, an access terminal, a terminal, a mobile station, or a subscriber unit. UE 120 may be a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet device, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device, or a satellite radio), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, a UE function of a network node, or any other suitable device configured to communicate via a wireless medium.

[0045] UE 120 may be included within a housing that houses components of UE 120, such as a processor component or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, the processor component (e.g., one or more processors) and the memory component (e.g., memory) may be operatively coupled, communicatively coupled, electronically coupled, or electrically coupled.

[0046] Devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various categories, bands, or channels by frequency or wavelength. For example, devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the “sub-6 GHz” band in various documents and articles. Similar naming issues sometimes arise in connection with FR2, which is often (interchangeably) referred to as the “millimeter wave” band in various documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

[0047] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz–24.25GHz). The frequency bands falling within FR3 can inherit FR1 characteristics or FR2 characteristics, and thus the features of FR1 or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz–71GHz), FR4 (52.6GHz–114.25GHz), and FR5 (114.25GHz–300GHz). Each of these higher frequency bands falls within the EHF band.

[0048] Considering the above examples, unless otherwise specifically stated, if the term "sub-6 GHz" is used herein, it may broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Furthermore, unless otherwise specifically stated, if the term "millimeter wave" is used herein, it may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a, FR4-1, or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, or FR5) may be modified, and that the techniques described herein are applicable to those modified frequency ranges.

[0049] In some aspects, the UE 120 may include a communications manager 140. As described in greater detail elsewhere herein, the communications manager 140 may receive a configuration associated with cross-link interference from a network node, the configuration indicating one or more time domain resources associated with CLI measurement; receive scheduling information associated with scheduling a plurality of communications from the network node, the scheduling information identifying a HARQ identifier and indicating that resources associated with a first one or more communications in the plurality of communications do not overlap with the one or more time domain resources in the time domain, and resources associated with a second one or more communications in the plurality of communications at least partially overlap with the one or more time domain resources associated with the CLI measurement in the time domain; and communicate the first one or more communications to the network node, the first one or more communications being associated with a respective HARQ identifier identified by incrementing a value of the HARQ identifier for only the first one or more communications. Additionally or alternatively, the communications manager 140 may perform one or more other operations described herein.

[0050] In some aspects, the network node 110 may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may transmit a configuration associated with cross-link interference for a UE, the configuration indicating one or more time domain resources associated with CLI measurement; transmit scheduling information associated with scheduling a plurality of communications for the UE, the scheduling information identifying a HARQ identifier and indicating that resources associated with a first one or more communications in the plurality of communications do not overlap with the one or more time domain resources in the time domain, and resources associated with a second one or more communications in the plurality of communications at least partially overlap with the one or more time domain resources associated with the CLI measurement in the time domain; and communicate the first one or more communications associated with the UE, the first one or more communications being associated with a respective HARQ identifier identified by incrementing a value of the HARQ identifier for only the first one or more communications. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0051] Figure 2 is a diagram illustrating an example network node communicating with a UE in a wireless network according to the present disclosure. The network node may correspond to Figure 1 Similarly, the UE may correspond to the network node 110. Figure 1 UE 120. Network node 110 may be equipped with a set of antennas 234a through 234t, such as T antennas (T ≥ 1). UE 120 may be equipped with a set of antennas 252a through 252r, such as R antennas (R ≥ 1). Figure 2The network node 110 depicted in FIG includes one or more radio frequency components, such as an antenna 234 and a modem 232. In some examples, the network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include radio frequency components, such as one or more CUs or one or more DUs, that facilitate direct communication with the UE 120.

[0052] At network node 110, a transmit processor 220 may receive data intended for UE 120 (or a group of UEs 120) from a data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCSs) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from the UE 120. A transmit (TX) multiple-input, multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, or reference symbols, as applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a through 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of a modem 232. The modems 232a through 232t may transmit a set of downlink signals (eg, T downlink signals) via a corresponding set of antennas 234 (eg, T antennas) (shown as antennas 234a through 234t).

[0053] At UE 120, a set of antennas 252 (shown as antennas 252a through 252r) may receive downlink signals from network node 110 or other network nodes 110 and may provide a set of receive signals (e.g., R receive signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a through 254r). The term "controller / processor" may refer to one or more controllers and / or one or more processors. In some examples, one or more components of UE 120 may be included in a housing 284.

[0054] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the network node 110 via the communication unit 294.

[0055] One or more antennas (e.g., antennas 234a to 234t or antennas 252a to 252r) may include or may be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc. An antenna panel, antenna group, set of antenna elements, or antenna array may include one or more antenna elements (in a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, or a plurality of antenna elements coupled to one or more transmit or receive components (such as antennas). Figure 2 One or more antenna elements of one or more components).

[0056] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information (e.g., for reports including RSRP, RSSI, RSRQ, or CQI) from the controller / processor 280. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, or a TX MIMO processor 266. The transceiver may be used by a processor (e.g., the controller / processor 280) and a memory 282 to perform aspects of any of the methods described herein.

[0057] At the network node 110, uplink signals from the UE 120 or other UEs may be received by an antenna 234, processed by a modem 232 (e.g., a demodulator component of the modem 232, shown as DEMOD), detected by a MIMO detector 236, if applicable, and further processed by a receive processor 238 to obtain decoded data and control information transmitted via the UE 120. The receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to a controller / processor 240. The network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink or uplink communications. In some examples, the modem 232 of the network node 110 may include a modulator and a demodulator. In some examples, the network node 110 includes a transceiver. The transceiver may include any combination of an antenna 234, a modem 232, a MIMO detector 236, a receive processor 238, a transmit processor 220, or a TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform aspects of any of the methods described herein.

[0058] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, or Figure 2 Any other component of the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, or the like may perform one or more techniques associated with determining a HARQ identifier associated with a CLI measurement, as described in greater detail elsewhere herein. Figure 2 Any other component of the may perform or direct e.g. Figure 8 The process of 800 Figure 9 900 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for network node 110 and UE 120, respectively. In some examples, memory 242 or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly or after compilation, conversion, or interpretation) by one or more processors of network node 110 or UE 120, may cause the one or more processors, UE 120, or network node 110 to perform or direct, for example, Figure 8 The process of 800 Figure 9 The process 900 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, or interpreting instructions, etc.

[0059] In some aspects, the UE 120 includes components for receiving a configuration associated with cross-link interference from a network node, the configuration indicating one or more time domain resources associated with CLI measurement; components for receiving scheduling information associated with scheduling multiple communications from the network node, the scheduling information indicating that: resources associated with a first one or more communications in the multiple communications do not overlap with the one or more time domain resources in the time domain, and resources associated with a second one or more communications in the multiple communications at least partially overlap with the one or more time domain resources associated with the CLI measurement in the time domain, and the scheduling information is associated with a HARQ identifier; and / or components for communicating the first one or more communications to the network node, the first one or more communications being associated with a corresponding HARQ identifier identified by incrementing a value of the HARQ identifier used only for the first one or more communications. Means for UE 120 to perform the operations described herein may include, for example, one or more of communications manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0060] In some aspects, the network node 110 includes means for sending a configuration associated with cross-link interference for a UE, the configuration indicating one or more time domain resources associated with CLI measurement; means for sending scheduling information associated with scheduling multiple communications for the UE, the scheduling information indicating that: resources associated with a first one or more communications in the multiple communications do not overlap with the one or more time domain resources in the time domain, and resources associated with a second one or more communications in the multiple communications at least partially overlap with the one or more time domain resources associated with the CLI measurement in the time domain, and the scheduling information is associated with a HARQ identifier; and / or means for conveying the first one or more communications associated with the UE, the first one or more communications being associated with a respective HARQ identifier identified by incrementing a value of the HARQ identifier used only for the first one or more communications. Means for the network node 110 to perform the operations described herein may include, for example, one or more of the communication manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

[0061] A converged base station (e.g., a converged network node) may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A decomposed base station (e.g., a decomposed network node) may be configured to utilize a protocol stack that is physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, the CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually spread across one or more other network nodes. The DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), among others.

[0062] Base station type operation or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate scaling of the communication system by separating base station functionality into one or more units that can be deployed separately. A disaggregated base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which may enable flexibility in network design. Each unit of the disaggregated base station may be configured for wired or wireless communication with at least one other unit of the disaggregated base station.

[0063] Figure 3 3 is a diagram illustrating an example associated with CLI detection and mitigation 300 according to the present disclosure. In dynamic time division duplexing (TDD), the allocation of network resources for uplink and downlink can be dynamically modified depending on the traffic load. For example, when UE 120 has uplink data to transmit, network node (NN) 110 can configure UE 120 with a TDD configuration (e.g., a TDD mode) having more uplink transmit time intervals (TTIs) (e.g., frames, subframes, slots, mini-slots, and / or symbols), and when UE 120 has downlink data to receive, a TDD configuration can be configured for UE 120 with more downlink TTIs. The TDD configuration can be dynamically configured to modify the allocation of uplink TTIs and downlink TTIs for communication between network node 110 and UE 120.

[0064] like Figure 3 As shown, when neighboring network nodes 110 use different TDD configurations to communicate with UE 120, this may result in downlink communication 310 between first network node 110-1 and first UE 120-1 in the same TTI as uplink communication 320 between second network node 110-2 and second UE 120-2. These communications in different transmission directions (e.g., downlink versus uplink) in the same TTI may interfere with each other, which may be referred to as CLI.

[0065] For example, in a first operation 330, the first network node 110-1 may transmit a downlink communication 310, and the second network node 110-2 may receive the downlink communication. The reception of the downlink communication 310 may cause interference (e.g., CLI) at the second network node 110-2 with the reception of the uplink communication 320 by the second network node 110-2 from the second UE 120-2. This may be referred to as downlink-to-uplink (DL-to-UL) interference, network node-to-network node interference, gNB-to-gNB interference, etc.

[0066] In addition, as in the second operation 340, the second UE 120-2 may transmit an uplink communication 320, and the first UE 120-1 may receive the uplink communication. The reception of the uplink communication 320 by the first UE 120-1 may cause interference (e.g., CLI) at the first UE 120-1 to the downlink communication 310 from the first network node 110-1. This may be referred to as uplink to downlink (UL to DL) interference or UE to UE interference, etc. When the first UE 120-1 and the second UE 120-2 are in close proximity, this UE to UE interference may occur or may increase, and may be avoided or mitigated by preventing the UE 120 from being scheduled in different transmit directions in the same TTI. In some examples, UE to UE interference may occur between UEs in the same cell (e.g., communicating with the same network node, rather than as Figure 3 different network nodes as shown).

[0067] In some examples, UE 120 (e.g., first UE 120-1 and / or second UE 120-2) may be configured to measure and / or report measurements of CLI. For example, CLI may be measured to facilitate and / or improve full-duplex operation at network node 110 and / or UE 120. "Full-duplex communication" in a wireless network refers to simultaneous, bidirectional communication between devices in a wireless network. For example, a UE 120 or network node 110 operating in full-duplex mode may send uplink communications and receive downlink communications simultaneously (e.g., in the same time slot or the same symbol). "Half-duplex communication" in a wireless network refers to unidirectional communication (e.g., only downlink communication or only uplink communication) between devices at a given time (e.g., in a given time slot or a given symbol). For example, for full-duplex communication, a downlink bandwidth part (BWP) and an uplink BWP may be active simultaneously (e.g., using the same or at least partially overlapping time domain resources). Downlink and uplink transmissions may occur in overlapping frequency bands (e.g., in-band full-duplex (IBFD)) or adjacent frequency bands (e.g., sub-band full-duplex (SBFD)). In a given downlink and uplink time slot symbol, a half-duplex UE 120 may transmit in the uplink frequency band or receive in the downlink frequency band. In a given downlink and uplink time slot symbol, a full-duplex UE 120 may transmit in the uplink frequency band and / or receive in the downlink frequency band (e.g., in the same time slot). Due to full-duplex operation, the UE 120 and / or the network node 110 may experience CLI in a manner similar to that described elsewhere herein.

[0068] CLI measurements and reporting may be associated with dynamic / flexible TDD and / or common to both SBFD mode and dynamic / flexible TDD. CLI measurements and reporting may be associated with measurement resource / reporting configuration, measurement / reporting information (e.g., including UE processing delays), related information exchange (e.g., between network nodes), and / or the use of measurements at network nodes. Other mechanisms may be defined for network node-to-network node (e.g., gNB-to-gNB) CLI processing or UE-to-UE CLI processing for SBFD.

[0069] UE 120 may be configured to explicitly report CLI measurements, such as CLI-RSRP measurements and / or CLI-RSSI measurements, among others. UE 120 may report CLI based at least in part on explicit CLI reporting (e.g., UE 120 may report explicit CLI measurements, such as CLI-RSRP measurements and / or CLI-RSSI measurements). In a CLI framework, UE 120 may perform Layer 3 (L3) CLI reporting based at least in part on periodic measurement resources (e.g., periodic CLI measurement resources). As used herein, "CLI measurement resources" may refer to time domain resources, frequency domain resources, and / or spatial domain resources to be measured by UE 120. In an adaptive L3 CLI framework, UE 120 may perform L3 CLI reporting based at least in part on adaptive periodic measurement resources. In a Layer 2 (L2) CLI framework, UE 120 may perform L2 CLI reporting based at least in part on semi-persistent or persistent measurement resources (e.g., via an uplink MAC control element (MAC-CE)). In a Layer 1 (L1) CLI framework, the UE 120 may perform L1 CLI reporting based at least in part on aperiodic, semi-persistent, or periodic measurement resources (e.g., via a physical uplink shared channel (PUSCH) or a physical uplink control channel (PUCCH)). This may provide the UE 120 with increased configuration flexibility and adaptation to dynamic CLI as it moves between the CLI framework, the adaptive L3 CLI framework, the L2 CLI framework, and the L1 CLI framework.

[0070] In some examples, one or more restrictions associated with communications that overlap or occur in the vicinity of a CLI measurement in the time domain may be configured and / or defined (e.g., by a wireless communication standard such as 3GPP). For example, one or more scheduling availability restrictions may define UE behavior for conflicts between scheduled communications and CLI measurements. As used herein, a "conflict" or resource "conflict" may refer to a first one or more radio resources (e.g., associated with a communication) and a second one or more radio resources (e.g., associated with a CLI measurement) that at least partially overlap in the time domain. For example, 3GPP Technical Specification (TS) Version 17.8.0 may define one or more scheduling availability restrictions when UE 120 is performing CLI measurements.

[0071] One or more scheduling availability constraints may define valid communications and invalid communications. "Valid" communications may be scheduled or configured communications that are available (e.g., intended for UE 120 to receive or send). "Invalid" communications or "restricted" communications may be communications that are unavailable (e.g., intended for UE 120 to receive or send), as indicated by one or more scheduling availability constraints. UE 120 may discard (e.g., refrain from sending or receiving) invalid or restricted communications. For example, if one or more scheduling availability constraints indicate that UE 120 is not intended to send or receive a given communication, UE 120 may discard (e.g., refrain from sending or receiving) the given communication.

[0072] For example, one or more scheduling availability restrictions may indicate that communications that at least partially overlap with time domain resources (e.g., OFDM symbols) associated with CLI measurement are invalid communications. Additionally, one or more scheduling availability restrictions may indicate that communications that at least partially overlap with time gaps (e.g., multiple OFDM symbols) occurring before and / or after CLI measurement are invalid communications. When TDD intra-band carrier aggregation is configured, scheduling restrictions on the serving cell performing CLI measurement may apply to all serving cells in the same frequency band on symbols that fully or partially overlap with the restricted symbols.

[0073] For example, one or more scheduling availability restrictions for CLI measurements may indicate that the UE 120 is not expected to send PUCCH communications, PUSCH communications, and / or sounding reference signal (SRS) communications on the OFDM symbol on which the UE 120 performs CLI measurements, and on one (1) data symbol preceding the OFDM symbol used for CLI measurements (e.g., for 15 kHz and / or 30 kHz subcarrier spacing in FR1 or for 60 kHz subcarrier spacing in FR2), or on two (2) data symbols preceding the OFDM symbol used for CLI measurements (e.g., for 60 kHz subcarrier spacing in FR1 or 120 kHz spacing in FR2). As another example, for a UE 120 that does not support frequency division multiplexing reception of serving cell downlink signals / channels and SRS-RSRP (e.g., does not support cli-SRS-RSRP-FDM_DL), it may be undesirable for the UE 120 to receive physical downlink control channel (PDCCH) communications, physical downlink shared channel (PDSCH) communications, and / or channel state information (CSI) reference signals (CSI-RS) for tracking and / or for CQI on the OFDM symbol on which the UE 120 performs SRS-RSRP measurements, and on one (1) data symbol before the OFDM symbol used for SRS-RSRP measurements (e.g., for 15 kHz and / or 30 kHz subcarrier spacing in FR1 or for 60 kHz subcarrier spacing in FR2), or on two (2) data symbols before the OFDM symbol used for SRS-RSRP measurements (e.g., for 60 kHz subcarrier spacing in FR1 or 120 kHz spacing in FR2).

[0074] As another example, for a UE 120 that does not support serving cell downlink signals / channels (e.g., PDSCH / PDCCH) and CLI-RSSI frequency division multiplexing reception (e.g., does not support cli-RSSI-FDM-DL), it may be undesirable for the UE 120 to receive PDCCH communications, PDSCH communications, and / or CSI-RS for tracking and / or for CQI on the OFDM symbol on which the UE 120 performs CLI-RSSI measurement, and on one (1) data symbol prior to the OFDM symbol used for CLI-RSSI measurement (e.g., for 15 kHz and / or 30 kHz subcarrier spacing in FR1 or for 60 kHz subcarrier spacing in FR2), or on two (2) data symbols prior to the OFDM symbol used for CLI-RSSI measurement (e.g., for 60 kHz subcarrier spacing in FR1 or 120 kHz spacing in FR2).

[0075] Figure 4is a diagram illustrating an example associated with a multi-communication schedule 400 according to the present disclosure. Figure 4 As shown, DCI 405 may schedule multiple communications, shown as communication 1 through communication M. The communications may be uplink communications (eg, PUSCH communications) or downlink communications (eg, PDSCH communications).

[0076] For example, when scheduling communications, network node 110 may send and UE 120 may receive DCI 405. DCI 405 may indicate a time domain resource assignment (TDRA) for one or more communications. For example, DCI 405 may include a TDRA field that includes a TDRA index value. The TDRA index value may indicate a row index of a corresponding TDRA table, and the row index may correspond to a set of TDRA parameters (sometimes referred to as scheduling parameters or scheduling information). In some examples, the TDRA parameter set may include one or more start and length indicator values ​​(SLIVs) and a scheduling offset value. Network node 110 and UE 120 may use those TDRA parameters for scheduling communications. For example, a TDRA index value z in DCI 405 may correspond to a row index z+1 in a TDRA table. For example, a TDRA index value of 0 may correspond to a row index of 1.

[0077] For downlink communication (e.g., PDSCH communication), TDRA parameters may include, for example, a K0 value, an S value, and an L value. The K0 value may represent a scheduling offset (e.g., in the form of a number of time slots) between a time slot containing DCI 405 (for scheduling downlink communication) and a time slot containing scheduled downlink communication (scheduled by the scheduling DCI). The S value may represent the starting symbol of the downlink communication in the indicated time slot. The L value may represent the length (e.g., the number of consecutive symbols) of the downlink communication (e.g., in the indicated time slot). For uplink communication (e.g., PUSCH communication), TDRA parameters may include, for example, a K2 value, an S value, and an L value. The K2 value may represent a scheduling offset (e.g., in the form of a number of time slots) between a time slot containing DCI 405 (for scheduling uplink communication) and a time slot containing scheduled uplink communication (scheduled by the DCI 405). The S value may represent the starting symbol of the uplink communication in the indicated time slot. The L value may represent the length (eg, the number of consecutive symbols) of the uplink communication (eg, in the indicated time slot).

[0078] The number of communications scheduled by DCI 405 (e.g., M) may be the number of SLIVs included in the indicated row of the TDRA table (e.g., the row indicated by the TDRA field in DCI 405). In some examples, multiple communications may be included in consecutive time slots. In other examples, multiple communications may be included in non-consecutive time slots. Each communication may have a different SLIV. In some examples, some parameters may be shared between multiple communications, such as MCS and / or frequency domain resource assignments. In some examples, some parameters may be indicated for the respective communications, such as a new data indicator (NDI) and / or a redundancy version (RV).

[0079] In some examples, DCI 405 may indicate a HARQ identifier. A HARQ identifier may also be referred to as a HARQ process identifier. A HARQ process refers to a retransmission protocol in which a receiver checks for errors in received data, and if an error is detected, the receiver buffers the received data and requests a retransmission from the transmitter. The HARQ receiver is then able to combine the buffered received data with the retransmitted data before channel decoding and error detection, which improves the performance of retransmissions. The HARQ protocol may be implemented at the MAC layer. The HARQ protocol relies on the transmitter receiving an acknowledgment (e.g., an acknowledgment (ACK) or a negative acknowledgment (NACK)) from the receiver. The round-trip time, which includes both the processing time of the transmitter and the processing time of the receiver as well as propagation delays, means that such acknowledgments are not received immediately.

[0080] Generally speaking, a transmitter becomes inactive (relative to communicating with a receiver wireless communication device) while waiting for an acknowledgment or a scheduling opportunity, which means that average throughput can be relatively low. This corresponds to a single HARQ process (also known as a stop-and-wait (SAW) process). The HARQ process stops and waits for an acknowledgment before continuing to transmit additional data. Multiple HARQ processes can be used to avoid the impact of round-trip time on throughput. That is, other HARQ processes can transmit data while a given HARQ process is waiting for an acknowledgment. The HARQ entity within the MAC layer manages multiple HARQ processes. In operation, the transmitter buffers the data being transmitted until a positive acknowledgment has been received (if a retransmission is required). Once a positive acknowledgment has been received or the maximum number of retransmissions allowed has been reached, the data is cleared from the transmit buffer. Once the transmitter's transmit buffer has been cleared, new data can be transmitted by the given HARQ process.

[0081] The HARQ protocol can be used on the downlink or uplink. "Downlink HARQ" may refer to the transmission of downlink data on the PDSCH with a HARQ acknowledgment returned on the PUCCH or PUSCH. "Uplink HARQ" may refer to the transmission of uplink data on the PUSCH with a HARQ acknowledgment returned on the PDCCH. For both downlink HARQ and uplink HARQ, each serving cell has its own HARQ entity and its own set of HARQ processes. In addition, both downlink HARQ and uplink HARQ are asynchronous, which means that there is no fixed timing pattern for each HARQ process. Instead, the network node must signal the identity of the relevant HARQ process with each downlink resource allocation. Although asynchronous HARQ increases signaling overhead, asynchronous HARQ increases flexibility because retransmissions do not have to be scheduled during specific time slots.

[0082] For example, the DCI 405 may indicate a single HARQ identifier. The receiver (eg, UE 120) may apply or assign the HARQ identifier to the first scheduled communication in time (eg, Figure 4 4. Communication 1 is shown. For example, UE 120 may increment the indicated HARQ identifier to determine the HARQ identifier for other communications scheduled by DCI 405. This reduces the size of DCI 405 and reduces the signaling overhead associated with scheduling multiple communications using a single DCI. For example, DCI 405 may indicate HARQ identifier 0. UE 120 may assign or apply HARQ identifier 0 to communication 1. For the next communication in time (e.g., communication 2), UE 120 may increment HARQ identifier 0 (e.g., add a value of 1 to the previous HARQ identifier). For example, UE 120 may assign or apply HARQ identifier 1 to communication 1 (e.g., 0+1=1). Similarly, UE 120 may increment the HARQ identifier and assign or apply HARQ identifier 2 to communication 2 (e.g., 1+1=2). UE 120 may continue to increment the HARQ identifier and apply the identifier to the corresponding communications scheduled by DCI 405 (eg, communication 3 may be associated with HARQ identifier 3, and communication M may be associated with HARQ identifier M).

[0083] Synchronization of HARQ identifiers between the transmitter and receiver is important for ensuring that the HARQ process can be performed accurately. For example, the UE 120 or the network node 110 may use the HARQ identifier to track or identify data in the buffer so that the UE 120 or the network node 110 can retransmit the data and / or combine the buffered data with the retransmitted data. If the HARQ identifier is incorrectly assigned or tracked, the UE 120 or the network node 110 may retransmit incorrect data and / or may attempt to combine the buffered data with unrelated retransmitted data. This may result in errors when decoding and / or receiving data. Additionally, incorrectly assigning or tracking the HARQ identifier may cause subsequent HARQ identifiers that are based on the HARQ identifier or are otherwise associated with the HARQ identifier (e.g., incremented from the HARQ identifier) ​​to also be incorrect.

[0084] For example, network node 110 may transmit and UE 120 may receive a TDD configuration (e.g., a common TDD configuration or a dedicated TDD configuration for UE 120) indicating a communication direction associated with a corresponding time interval (e.g., a time slot or symbol). For example, the TDD configuration may indicate a pattern of downlink time slots, uplink time slots, hybrid time slots, and / or flexible time slots. A downlink time slot may refer to a time interval during which only downlink communication is permitted. An uplink time slot may refer to a time interval during which only uplink communication is permitted. A hybrid time slot may refer to a time interval during which only uplink communication is permitted in a first subset of OFDM symbols in a time slot and only downlink communication is permitted in a second subset of OFDM symbols in a time slot. A flexible time slot may refer to a time interval during which both uplink and downlink communication are permitted. The TDD configuration may be a semi-static configuration. In some examples, such as when a DCI schedules multiple communications, one or more of the scheduled communications may occur in a time slot or time interval associated with a conflicting communication direction. A conflicting communication direction may refer to a communication direction that is different from a communication direction associated with a scheduled communication. For example, an uplink communication may be scheduled in a downlink time slot, or a downlink communication may be scheduled in an uplink time slot. In such an example, the UE 120 may discard the scheduled communication and may skip incrementing the HARQ identifier. As another example, if a communication is scheduled to occur during a flexible time slot or symbol, and the time domain resources of the communication at least partially overlap with the time domain resources of a synchronization signal block (SSB) or are indicated by a PDCCH configuration of a system information block (SIB) 1 (e.g., in a master information block (MIB)) for a control resource set (CORESET) associated with a type 0 PDCCH common search space (CSS) set, the UE 120 may discard the scheduled communication and may skip incrementing the HARQ identifier.

[0085] For example, if communication 2 (such as Figure 41) is an uplink communication and is scheduled to occur during a downlink time interval (e.g., a downlink time slot or symbol), UE 120 may discard (e.g., not transmit) communication 2 and may not increment the HARQ identifier for communication 2. Thus, communication 3 may be associated with HARQ identifier 2, rather than communication 3 being associated with HARQ identifier 3 as described above. Similarly, communication M may be associated with HARQ identifier M-1 (e.g., assuming only communication 2 is discarded). Avoiding incrementing the HARQ identifier in this scenario ensures that there is no misalignment of the HARQ identifiers between UE 120 and network node 110, ensures that there is no excessive size of the HARQ identifiers, and ensures that the HARQ identifiers are used continuously by UE 120 and network node 110, thereby reducing complexity and simplifying the management of the HARQ process.

[0086] In some examples, UE 120 may discard (e.g., not send or receive) communications that at least partially overlap with a conflicting communication direction as indicated by another DCI or a slot format indicator (SFI) DCI. Additionally or alternatively, UE 120 may discard communications based on or otherwise associated with an uplink cancellation indication, high priority communications, or other dynamic signaling. However, due to the possibility of missed detection associated with dynamic signaling (e.g., dynamic signaling may be less robust to missed detections), UE 120 may still increment the HARQ identifier for these discarded communications.

[0087] However, in some examples, communications (e.g., from multiple communications scheduled by a single DCI or other scheduling information) may be dropped (e.g., delinking the dynamic signaling described above) for other reasons not associated with a high risk of missed detection (e.g., other than being associated with a time slot associated with a conflicting communication direction). For example, as described in more detail elsewhere herein, the UE 120 may drop (e.g., not send or receive) a communication based on or otherwise associated with a configured CLI measurement resource. However, if the dropped communication is a communication scheduled with multiple communications (e.g., such as a communication scheduled by DCI 405), the UE 120 and the network node 110 may be out of sync in their handling of HARQ identifiers associated with the multiple communications. For example, the handling of incrementing or determining HARQ identifiers for multiple communications is not defined. Therefore, UE 120 and network node 110 may perform different operations (e.g., increment or not increment) on HARQ identifiers associated with communications that were discarded due to at least partial overlap with resources associated with CLI measurement in the time domain. This may result in errors associated with HARQ processes for the discarded communication and for other communications included in the plurality of communications. Additionally, this may cause UE 120 and network node 110 to unnecessarily use or consume HARQ identifiers for the discarded communication.

[0088] Various aspects generally relate to HARQ identifier determination associated with CLI measurements. Some aspects more specifically relate to handling HARQ identifier determination for communications that are dropped (e.g., not sent or received) due to overlap with CLI measurements in the time domain. For example, the dropped communication may be a communication scheduled with multiple communications, such as via a single DCI communication or as part of another semi-static configuration (such as an SPS configuration or a CG configuration). In some aspects, the UE 120 and / or the network node 110 may drop (e.g., may not desire to receive or send) a communication because the time domain resources of the communication at least partially overlap with time domain resources associated with CLI measurements (e.g., CLI measurement resources and / or time slots associated with CLI measurements). In some aspects, the UE 120 and / or the network node 110 may avoid incrementing the HARQ identifier for the communication that was dropped due to a collision with the CLI measurement (e.g., in the time domain). In other words, for scheduling information associated with scheduling multiple communications, where the scheduling information indicates or is associated with a single HARQ identifier, the UE 120 and / or the network node 110 may not increment the HARQ identifier from the multiple communications for a communication that was dropped due to a collision with the CLI measurement (e.g., in the time domain).

[0089] In some aspects, the multiple communications may be uplink communications (e.g., PUSCH communications) or downlink communications (e.g., PDSCH communications) scheduled by a single DCI communication. The single DCI communication may indicate a single HARQ identifier. The UE 120 and / or the network node 110 may not increment the single HARQ identifier for a communication from the multiple communications that is discarded due to a collision with the CLI measurement (e.g., in the time domain). Additionally, the UE 120 and / or the network node 110 may not apply the HARQ identifier indicated by the DCI to the discarded communication.

[0090] In some aspects, the multiple communications may be semi-statically configured (e.g., rather than scheduled by DCI). For example, the multiple communications may be SPS communications or CG configurations. In such examples, a HARQ identifier associated with a period (e.g., an SPS period or a CG period) may not be incremented for a communication from the multiple semi-static communications that is discarded due to a collision with a CLI measurement because the communication occurred during a time slot associated with the conflicting communication direction and / or for another reason. Additionally, the UE 120 and / or the network node 110 may not apply the initial HARQ identifier determined for the period to the discarded communication.

[0091] Certain aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, the described techniques can be used to synchronize the processing of HARQ identifier determination between the UE 120 and the network node 110 when a communication is dropped (e.g., not sent or received) due to a conflict with a CLI measurement. This ensures that there is no misalignment of HARQ identifiers between the UE 120 and the network node 110, ensures that there is no excessive size of the HARQ identifiers, and ensures that the UE 120 and the network node 110 use HARQ identifiers continuously, thereby reducing complexity and simplifying the management of the HARQ process, etc.

[0092] Figure 5 5 is a diagram illustrating an example of HARQ identifier determination 500 associated with CLI measurement according to the present disclosure. Figure 5 As shown, one or more network nodes 110 (e.g., network node 110, base station, gNB, CU, DU, and / or RU) may communicate with UE 120. In some aspects, network node 110 and UE 120 may be part of a wireless network, such as wireless network 100. UE 120 and network node 110 may be part of a wireless network, such as wireless network 100. Figure 5 The operations shown are performed after a wireless connection has been established.

[0093] In some aspects, the operations described herein as being performed by network node 110 may be performed by multiple different network nodes. For example, configuration operations may be performed by a first network node (e.g., a CU or DU), and radio communication operations may be performed by a second network node (e.g., a DU or RU).

[0094] As used herein, "outputting" or "sending" a communication from network node 110 to UE 120 may refer to direct transmission (e.g., from network node 110 to UE 120) or indirect transmission via one or more other network nodes or devices. For example, if network node 110 is a DU, indirect transmission to UE 120 may include the DU outputting or sending the communication to the RU, and the RU sending the communication to UE 120, or may include causing the RU to send the communication (e.g., triggering the transmission of a physical layer reference signal). Similarly, "sending" a communication from UE 120 to network node 110 may refer to direct transmission (e.g., from UE 120 to network node 110) or indirect transmission via one or more other network nodes or devices. For example, if network node 110 is a DU, indirect transmission to network node 110 may include UE 120 sending the communication to the RU, and the RU sending the communication to the DU. Similarly, network node 110 "obtaining" or "receiving" a communication may refer to directly receiving the transmission carrying the communication (e.g., from UE 120 to network node 110) or receiving the communication (or information derived from receipt of the communication) via one or more other network nodes or devices.

[0095] In a first operation 505, UE 120 may send a capability report, and network node 110 may receive or obtain the capability report. The capability report may indicate the UE's support for HARQ identifier processing for communications dropped due to a conflict with a CLI measurement, as described in greater detail elsewhere herein. For example, the capability report may indicate that UE 120 supports skipping and / or not incrementing HARQ identifier values ​​for communications (e.g., such as multiple communications scheduled together via a single DCI communication) that are dropped (e.g., not sent or received) due to a conflict with resources associated with a CLI measurement.

[0096] In some aspects, the capability report may indicate one or more UE capabilities associated with CLI measurement. For example, the capability report may indicate whether the UE 120 supports frequency division multiplexing reception of a serving cell downlink signal / channel and SRS-RSRP (e.g., cli-SRS-RSRP-FDM_DL capability as defined by 3GPP or otherwise fixed). As another example, the capability report may indicate whether the UE 120 supports frequency division multiplexing reception of a serving cell downlink signal / channel (e.g., PDSCH / PDCCH) and CLI-RSSI (e.g., cli-RSSI-FDM-DL capability as defined by 3GPP or otherwise fixed). The capability report may be included in uplink communications, PUCCH communications, PUSCH communications, uplink control information (UCI) communications, and / or UE assistance information (UAI) communications, among others.

[0097] In a second operation 510, the network node 110 may send or output configuration information and the UE 120 may receive the configuration information. In some aspects, the UE 120 may receive the configuration information via one or more of system information signaling, RRC signaling, one or more MAC-CEs and / or DCI, etc. In some aspects, the configuration information may include an indication of one or more configuration parameters for selection by the UE 120 (e.g., stored by the UE 120 and / or previously indicated by the network node 110 or another network device) and / or explicit configuration information for the UE 120 to configure itself, etc.

[0098] In some aspects, the configuration information may indicate that the UE 120 is to avoid incrementing a HARQ identifier value for communications (e.g., such as multiple communications scheduled together via a single DCI communication) that are discarded (e.g., not sent or received) due to a conflict with a CLI measurement. For example, the configuration information may indicate that for multiple communications scheduled via a single DCI communication, if a communication (e.g., in the multiple communications) at least partially overlaps in the time domain with resources associated with the CLI measurement, then HARQ identifier incrementing is to be skipped for the communication. Furthermore, the configuration information may indicate that the HARQ identifier indicated by the DCI is not to be applied to the communication.

[0099] For example, as described in more detail elsewhere herein, if the time domain resources of a communication (e.g., a PUSCH communication or a PDSCH communication) at least partially overlap with the time domain resources associated with CLI measurement, the communication will be discarded (e.g., UE 120 is not expected to send or receive the communication). The time domain resources associated with CLI measurement may include resources (e.g., OFDM symbols) during which UE 120 will perform CLI measurement and time gaps before and / or after the resources (e.g., OFDM symbols) during which UE 120 will perform CLI measurement. The time gaps may be different for different subcarrier spacings and different operating frequency ranges (e.g., FR1 or FR2). For example, if UE 120 does not support frequency division multiplexing of transmission or reception of communications with CLI measurement resources (e.g., as indicated by different capabilities of UE 120 for different measurement types, such as CLI measurement based on CLI RSSI or CLI measurement based on SRS RSRP), then UE 120 does not support receiving or sending communications in time domain resources that at least partially overlap with resources associated with CLI measurement, as described in more detail elsewhere herein. In such a scenario, UE 120 may drop the communication and may refrain from performing HARQ identifier incrementing for the communication.

[0100] In some aspects, the configuration information may indicate that for semi-static communications (e.g., SPS communications or CG communications) in which multiple communication opportunities are configured together in a single cycle under the same configuration, the UE 120 will avoid incrementing the HARQ identifier value for invalid communications. As used herein, an "opportunity" may refer to a configured radio resource (e.g., a time / frequency resource) available for the UE 120 to receive or send communications. Invalid communications may be communications that are discarded due to overlapping in the time domain with a slot or symbol having a conflicting communication direction, with an SSB included in a flexible slot, or with a given search space set (e.g., a search space set configured as a CORESET configured for a Type 0-PDCCH CSS set via pdcch-ConfigSIB1 in the MIB), and / or with a CLI measurement, as described in more detail elsewhere herein.

[0101] For example, the configuration information may indicate that for an SPS period with multiple PDSCH opportunities or a CG period with multiple PUSCH opportunities, if one or a combination of conditions is met, a PDSCH opportunity in the multiple PDSCH opportunities or a PUSCH opportunity in the multiple PUSCH opportunities is not considered valid and HARQ ID incrementing is skipped. Otherwise, the PDSCH opportunity or PUSCH opportunity is valid and HARQ ID incrementing is not skipped. For example, the conditions may include whether the opportunity occurs in a time slot or symbol associated with a conflicting communication direction (e.g., whether the PDSCH / PUSCH opportunity conflicts with a UL / DL symbol indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated). As another example, the condition may include whether an uplink opportunity (e.g., a PUSCH opportunity) occurs during a flexible symbol or time slot associated with SSB communication and / or associated with a search space associated with initial access or synchronization (e.g., whether the PUSCH opportunity collides with a flexible symbol or time slot indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, and in which symbol or time slot, the PUSCH opportunity collides with an SSB symbol indicated by ssb-PositionsInBurst or a symbol of a CORESET for a Type0-PDCCH CSS set indicated by pdcch-ConfigSIB1 in the MIB). As another example, the condition may include whether a PDSCH opportunity or a PUSCH opportunity overlaps with a symbol that collides with a CLI measurement. In some aspects, the condition may be defined by a wireless communication standard such as 3GPP or otherwise fixed (e.g., in this case, the condition may not be indicated by configuration information and may be pre-configured or configured for the UE 120 as part of an original equipment manufacturer (OEM) configuration).

[0102] In some aspects, the configuration information may include a CLI measurement configuration. For example, the UE 120 may be configured (e.g., by the network node 110) to perform CLI measurements. For example, the network node 110 may send and the UE 120 may receive a configuration associated with cross-link interference, the configuration indicating one or more time domain resources associated with the CLI measurement. For example, the CLI measurement may include a CLI RSSI measurement and / or an SRS RSRP measurement. For example, the CLI measurement configuration may indicate that the UE 120 will perform and report CLI measurement information based on one or more SRS resources or otherwise associated with one or more SRS resources. As another example, the CLI measurement configuration may indicate that the UE 120 will perform and report CLI measurement information based on a CLI-RSSI resource or otherwise associated with a CLI-RSSI resource. For example, the CLI measurement configuration may configure measurement objects associated with the CLI measurement. The measurement object may indicate the frequency / time location and subcarrier spacing of the signal to be measured for CLI measurement (e.g., the frequency / time location of the SRS resource and / or CLI-RSSI resource to be measured and the subcarrier spacing of the SRS resource). For example, an RRC information element (e.g., a MeasObjectCLI information element) may indicate information applicable to SRS-RSRP measurement and / or CLI-RSSI measurement for a CLI measurement configuration. For example, a CLI measurement configuration may indicate the configuration of SRS resources to be used for CLI measurement (e.g., via srs-ResourceConfig included in the CLI measurement configuration) and / or the configuration of CLI-RSSI resources for CLI measurement (e.g., via rssi-ResourceConfig included in the CLI measurement configuration). In some aspects, the configuration of the measurement object for CLI measurement may indicate the SRS and / or CLI-RSSI resource configuration for CLI measurement (e.g., via cli-ResourceConfig included in the configuration of the measurement object). The configuration of resources (eg, SRS resources and / or CLI-RSSI resources) may indicate time / frequency resources, periodicity, slot offset, and / or other configuration information to enable UE 120 to identify the location of the resources in time and / or frequency.

[0103] In some aspects, the configuration information may include configurations for semi-static and / or periodic communications, such as an SPS configuration or a CG configuration. SPS communications may include periodic downlink communications configured for UE 120, such that network node 110 does not need to send a separate DCI (e.g., directly or via one or more network nodes) to schedule each downlink communication, thereby saving signaling overhead. UE 120 may be configured with an SPS configuration for SPS communications. For example, UE 120 may receive the SPS configuration via RRC signaling sent by network node 110 (e.g., directly or via one or more network nodes). The SPS configuration may indicate resource allocations associated with one or more SPS downlink opportunities (e.g., in the time, frequency, spatial, and / or code domains) and the periodicity with which the resource allocations for the opportunities are repeated, such that scheduled SPS opportunities for UE 120 occur periodically. The SPS configuration may also configure HARQ-ACK feedback resources for UE 120 to send HARQ-ACK feedback for SPS PDSCH communications received in a given SPS opportunity.

[0104] CG communication may include periodic uplink communication configured for UE 120, so that network node 110 does not need to send a separate DCI to schedule each uplink communication, thereby saving signaling overhead. UE 120 may be configured with a CG configuration for CG communication. For example, UE 120 may receive the CG configuration via RRC signaling sent by network node 110. The CG configuration may indicate resource allocations associated with one or more CG uplink opportunities (e.g., in the time domain, frequency domain, spatial domain, and / or code domain) and the periodicity with which the resource allocations for the opportunities are repeated, such that scheduled CG opportunities for UE 120 occur periodically. In some examples, the CG configuration may identify a resource pool or multiple resource pools available for uplink transmission by UE 120. The CG configuration may configure contention-free CG communication (e.g., where resources are dedicated to UE 120 to transmit uplink communications) or contention-based CG communication (e.g., where UE 120 competes for access to a channel in the configured resource allocation, such as by using a channel access procedure or a channel sensing procedure).

[0105] In some aspects, the configuration of semi-static and / or periodic communications may include a period in which multiple opportunities are configured. For example, the configuration information may indicate a period associated with multiple semi-static communications. For example, the configuration information may indicate an SPS configuration (e.g., a single SPS configuration) that configures multiple SPS opportunities associated with an SPS period. Similarly, the configuration information may indicate a CG configuration (e.g., a single CG configuration) that configures multiple CG opportunities associated with a CG period. In such examples, the UE 120 may determine a HARQ identifier associated with a period (e.g., an SPS period or a CG period) and may increment the HARQ identifier to assign a HARQ identifier for the corresponding opportunity included in the period. For example, the HARQ identifier associated with the period may be based on a HARQ identifier offset value, a symbol associated with the period, and a periodicity associated with multiple semi-static communications, or may be otherwise associated with a HARQ identifier offset value, a symbol associated with the period, and a periodicity associated with multiple semi-static communications. For example, the HARQ identifier associated with a cycle may be based on, or otherwise associated with, floor(HARQ ID offset + current symbol / SPS or CG periodicity) modulo the number of configured HARQ processes allocated to the cycle.

[0106] UE 120 may configure itself based at least in part on the configuration information.In some aspects, UE 120 may be configured to perform one or more operations described herein based at least in part on the configuration information.

[0107] In a third operation 515, the network node 110 may send scheduling information associated with scheduling multiple communications, and the UE 120 may receive the scheduling information. For example, the network node 110 (e.g., a DU) may determine the scheduling information. The UE 120 may receive the scheduling information from the network node 110 (e.g., an RU). The multiple communications may be multiple PDSCH communications or multiple PUSCH communications. In some aspects, the multiple communications may be dynamically granted communications. In such examples, the scheduling information may include DCI (e.g., a single DCI communication scheduling the multiple communications). In other aspects, the multiple communications may be multiple semi-static or periodic communications, such as multiple SPS communications (or opportunities) or multiple CG communications (or opportunities). In such examples, the scheduling information may be included in configuration information (e.g., the third operation 515 may be performed as part of the second operation 510 or in the same signaling as the second operation). The scheduling information and / or the multiple communications may be associated with a HARQ identifier (e.g., a HARQ process identifier).

[0108] In a fourth operation 520, UE 120 may identify or determine HARQ identifiers associated with the plurality of communications. For example, network node 110 may transmit DCI scheduling the plurality of communications, and UE 120 may receive the DCI. The DCI may indicate a single HARQ identifier (e.g., assigned to or applied to the first valid communication in time among the plurality of communications). For example, UE 120 may perform HARQ identifier incrementing to determine the HARQ identifier for a corresponding communication among the plurality of communications (e.g., by incrementing the value of the HARQ identifier indicated by the DCI for each communication in the plurality of communications).

[0109] As another example, UE 120 may determine an initial HARQ identifier associated with a period (e.g., a CG period or an SPS period) associated with multiple communications, such as when the multiple communications are semi-static or periodic communications (e.g., SPS or CG communications). The initial HARQ identifier associated with the period may be assigned to or applied to a first valid opportunity in time among the multiple opportunities associated with the period. For example, the initial HARQ identifier associated with the period may be based on a HARQ identifier offset value, a symbol associated with the period, and a periodicity associated with the multiple semi-static communications, or otherwise associated with the HARQ identifier offset value, a symbol associated with the period, and a periodicity associated with the multiple semi-static communications. For example, the initial HARQ identifier associated with the period may be based on or otherwise associated with floor(HARQ ID offset + current symbol / SPS or CG periodicity) modulo the number of configured HARQ processes assigned to the period. For example, UE 120 may perform HARQ identifier incrementing to determine a HARQ identifier for a corresponding opportunity among the plurality of opportunities (eg, by incrementing a value of an initial HARQ identifier determined for a period of each of the plurality of opportunities).

[0110] In a fifth operation 525, the UE 120 may detect that a communication (or opportunity) from the plurality of communications (or opportunities) is to be dropped (e.g., not sent or received by the UE 120). For example, based on or otherwise associated with one or more drop rules, it may be undesirable for the UE 120 to send or receive the communication or opportunity. For example, the one or more drop rules may be based on or otherwise associated with (e.g., in conjunction with) a communication (or opportunity) that conflicts with a CLI measurement. Figure 3 ). For example, UE 120 may detect that time domain resources associated with the communication or opportunity at least partially overlap in the time domain with resources associated with the CLI measurement (e.g., with the OFDM symbol to be used for performing the measurement and / or with a time gap before or after the OFDM symbol).

[0111] For example, UE 120 may detect that a communication scheduled via a single DCI communication among multiple communications conflicts with resources associated with a CLI measurement. For example, a PUSCH communication or a PDSCH communication scheduled by a DCI that schedules multiple PUSCH communications or multiple PDSCH communications may conflict (e.g., in the time domain) with a CLI measurement to be performed by UE 120. As a result, UE 120 may detect that the PUSCH communication or the PDSCH communication is to be dropped (e.g., not sent or received by UE 120). In other words, it may not be desirable for UE 120 to send a PUSCH communication or receive a PDSCH communication. In conjunction with Figure 3 A scenario where UE 120 drops a communication due to a conflict with CLI measurements is described in more detail.

[0112] As another example, if the multiple communications are multiple semi-static or periodic opportunities, the UE 120 may detect that the opportunity from the multiple opportunities associated with a given period is invalid. For example, the UE 120 may detect that the opportunity (e.g., an SPS opportunity or a CG opportunity) is invalid based on a resource associated with an opportunity that at least partially overlaps with a time slot or symbol associated with the conflicting communication direction or is otherwise associated with the resource. For example, the UE 120 may receive a TDD configuration (e.g., in the second operation 510). The conflicting communication direction may be indicated via a TDD configuration that indicates a pattern of communication directions for the time slot or symbol. The TDD configuration may be a cell-specific or UE-specific TDD uplink / downlink configuration (e.g., tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated). As another example, the UE 120 may detect that an opportunity (e.g., an SPS opportunity or a CG opportunity) is invalid based on resources associated with or otherwise associated with an opportunity that at least partially overlaps with a flexible slot or symbol associated with SSB communication (e.g., an SSB indicated by ssb-PositionsInBurst). As another example, the UE 120 may detect that an opportunity (e.g., an SPS opportunity or a CG opportunity) is invalid based on resources associated with or otherwise associated with an opportunity that at least partially overlaps with a slot or symbol associated with a search space associated with initial access or synchronization (e.g., the search space may be search space #0 and / or associated with a symbol of a CORESET for a Type 0-PDCCH CSS set indicated by pdcch-ConfigSIB1 in the MIB). As another example, UE 120 may detect that an opportunity (e.g., an SPS opportunity or a CG opportunity) is invalid based on resources associated with an opportunity that at least partially overlaps or is otherwise associated with resources associated with CLI measurements, in a manner similar to that described in more detail elsewhere herein.

[0113] In a sixth operation 530, the UE 120 may skip incrementing the HARQ process identifier value for the discarded communication. For example, the UE 120 may avoid incrementing the HARQ identifier for the discarded communication or opportunity (e.g., associated with the plurality of communications as determined in the fourth operation 520). For example, the UE 120 may avoid incrementing the HARQ identifier for one or more communications or opportunities that at least partially overlap in the time domain with one or more time domain resources associated with CLI measurement and / or based on other conditions or associated with other conditions as described in more detail elsewhere herein.

[0114] For example, for a single DCI scheduling multiple communications, if a communication in the multiple communications overlaps with a symbol that collides with a CLI measurement, incrementing the HARQ process identifier value for that communication may be skipped. Furthermore, the HARQ identifier indicated by the single DCI may not be applied or assigned to the communication. UE 120 may skip assigning a HARQ identifier for a discarded communication. For example, UE 120 may avoid assigning or applying the HARQ identifier indicated by the single DCI to a communication that was discarded due to a conflict with a CLI measurement.

[0115] For a semi-static communication cycle (e.g., an SPS cycle or a CG cycle) associated with multiple opportunities, if an opportunity among the multiple opportunities is invalid (e.g., determined to be invalid in a manner similar to that described in conjunction with fifth operation 525), the UE 120 may avoid incrementing the HARQ identifier associated with the semi-static communication cycle for the (e.g., invalid and / or discarded) opportunity. The initial HARQ identifier associated with the semi-static communication cycle may be applied or assigned to the first valid opportunity (e.g., the first in time) among the multiple opportunities associated with the semi-static communication cycle.

[0116] In some aspects, UE 120 may determine to skip or not communicate a communication or opportunity. For example, UE 120 may determine that no data is available for communication by a configured opportunity, may determine to send or receive another communication, and / or may otherwise determine that UE 120 will not use the scheduled communication and / or configured opportunity. In such examples, UE 120 may send, and network node 110 may receive, an indication that the communication and / or opportunity will be skipped or not used. For example, UE 120 may send, and network node 110 may receive, an indication that a communication and / or opportunity will be skipped or not used. For example, UE 120 may send UCI indicating that a CG opportunity from a plurality of CG opportunities associated with a CG period will be skipped or not used by UE 120 for PUSCH transmission. In such examples, UE 120 and / or network node 110 may treat the skipped communication or opportunity as invalid. UE 120 and / or network node 110 may refrain from incrementing the HARQ identifier associated with the period for the skipped communication or opportunity, and may not assign or apply the initial HARQ identifier associated with the period to the skipped communication or opportunity.

[0117] The network node 110 may perform operations similar or identical to the fourth operation 520, the fifth operation 525, and / or the sixth operation 530. For example, the network node 110 may track, determine, and / or maintain an indication of HARQ identifiers used for communications in a manner similar to the UE 120 described herein.

[0118] In a seventh operation 535, the UE 120 and the network node 110 may communicate (e.g., send or receive) one or more communications, the first one or more communications being associated with a corresponding HARQ identifier associated with a HARQ identifier that is incremented only for the one or more communications (e.g., and not for discarded communications or opportunities, as described in more detail elsewhere herein). In other words, for valid communications or opportunities from the plurality of communications or opportunities (e.g., the valid communications or opportunities may not overlap in the time domain with resources associated with CLI measurement and / or meet one or more other criteria described herein), the UE 120 may determine the HARQ identifier for the corresponding valid communication or opportunity by incrementing the value of the HARQ identifier for each of the valid communications or opportunities (e.g., and not incrementing the value of the HARQ identifier for the invalid communications or opportunities).

[0119] This enables the UE 120 and the network node 110 to perform HARQ processes for valid communications or opportunities. For example, this ensures that HARQ identifiers are synchronized between the UE 120 and the network node 110 when a communication or opportunity is dropped due to a collision with a CLI measurement or due to other reasons described herein. Additionally, this reduces consumption of the HARQ process identifier pool by not assigning HARQ identifiers to communications or opportunities that are dropped due to a collision with a CLI measurement. For example, this can enable the UE 120 and the network node 110 to synchronize the processing of HARQ identifier determination between the UE 120 and the network node 110 when a communication is dropped (e.g., not sent or received) due to a collision with a CLI measurement. This ensures that there is no misalignment of HARQ identifiers between the UE 120 and the network node 110, ensures that there is no excessive size of HARQ identifiers, and ensures that the UE 120 and the network node 110 use HARQ identifiers continuously, thereby reducing complexity and simplifying the management of HARQ processes, etc.

[0120] Figure 6 is a diagram of an example associated with HARQ identifier determination 600 associated with CLI measurement according to the present disclosure. For example, Figure 6 Multiple communications (eg, such as Figure 66. In some aspects, communication 1, communication 2, communication 3, and communication 4 may be uplink communications (e.g., PUSCH communications). In other aspects, communication 1, communication 2, communication 3, and communication 4 may be downlink communications (e.g., PDSCH communications). Although four communications are shown as being scheduled by DCI 605, in other examples, DCI 605 may schedule a different number of communications.

[0121] like Figure 6 As shown, UE 120 may not be expected to send or receive one or more communications scheduled by DCI 605. For example, UE 120 may drop one or more of the communications scheduled by DCI 605. As an example, and as Figure 6 As shown, UE 120 may discard communication 1 and communication 3, and may communicate (eg, send or receive) communication 2 and communication 4. In other words, communication 1 and communication 3 may be invalid communications, and communication 2 and communication 4 may be valid communications.

[0122] For example, the time domain resources for communication 1 may at least partially overlap with symbols or time slots associated with the conflicting communication direction (e.g., as indicated by the TDD configuration). For example, if communication 1 is a downlink communication, the symbol or time slot may be an uplink symbol or uplink time slot. The time domain resources for communication 3 may at least partially overlap with symbols associated with CLI measurements, as described in more detail elsewhere herein. Therefore, it may not be desirable for UE 120 to transmit or receive communication 1 or communication 3.

[0123] like Figure 6As shown, DCI 605 may indicate a HARQ process identifier (e.g., shown as HARQ ID=1). For example, the value of the HARQ identifier indicated by DCI 605 may be 1. UE 120 may determine the HARQ identifier for the corresponding communication scheduled by DCI 605 by incrementing the value of the HARQ identifier indicated by DCI 605. For example, UE 120 may assign or apply the HARQ identifier indicated by DCI 605 to the first valid communication at a time scheduled by DCI 605. For example, Communication 1 may be an invalid communication. Therefore, UE 120 may avoid incrementing the value of the HARQ identifier and may avoid applying or assigning the HARQ identifier indicated by DCI 605 to Communication 1. UE 120 may assign or apply the HARQ identifier indicated by DCI 605 to Communication 2 (e.g., the first valid communication at a time scheduled by DCI 605). UE 120 may refrain from incrementing the value of the HARQ identifier for communication 3 and may refrain from applying or assigning the HARQ identifier indicated by DCI 605 to communication 3 because communication 3 was dropped due to a conflict with the CLI measurement. UE 120 may increment the value of the HARQ identifier and may apply or assign the incremented value (e.g., 2, because 1+1=2) to communication 4 (e.g., the next valid communication in time scheduled by DCI 605).

[0124] Figure 7 is a diagram of an example associated with HARQ identifier determination 700 associated with CLI measurement according to the present disclosure. For example, Figure 7 Can depict multiple opportunities (e.g. Figure 7 In some aspects, the multiple opportunities may be uplink opportunities (e.g., CG opportunities). In other aspects, the multiple opportunities may be downlink opportunities (e.g., SPS communications). For example, multiple opportunities may be associated with the semi-static period 705. The semi-static period 705 may be associated with a single configuration (e.g., a single SPS configuration or a single CG configuration). The semi-static period 705 may be an SPS period or a CG period. Although five opportunities are shown as being associated with the semi-static period 705, in other examples, the semi-static period 705 may include a different number of opportunities.

[0125] The semi-static period 705 may be associated with an initial HARQ identifier. For example, the UE 120 and / or the network node 110 may determine the initial HARQ identifier for the semi-static period 705 in a manner similar to that described in more detail elsewhere herein. Figure 7As shown, in some examples, UE 120 may drop one or more of the opportunities (e.g., may not desire to use one or more of the opportunities to send or receive communications). For example, opportunity 1 may conflict with a symbol or time slot associated with a conflicting communication direction (e.g., as indicated by a TDD configuration). For example, if opportunity 1 is an uplink opportunity or a CG opportunity, opportunity 1 may be configured or scheduled to occur in radio resources that at least partially overlap with a downlink time slot or symbol in the time domain. Therefore, it may be undesirable for UE 120 to transmit or receive using resources associated with opportunity 1.

[0126] It may not be desirable for UE 120 to transmit or receive communications using resources associated with opportunity 3 because these resources may conflict with resources associated with CLI measurements. For example, the time domain resources associated with opportunity 3 may at least partially overlap in the time domain with resources associated with CLI measurements. Therefore, in some examples and as described in more detail elsewhere herein, it may not be desirable for UE 120 to transmit or receive communications using resources associated with opportunity 3. It may not be desirable for UE 120 to transmit or receive communications using resources associated with opportunity 4 because the resources may conflict with symbols associated with SSB reception. For example, opportunity 4 may be configured or scheduled to occur during a flexible time slot or symbol (e.g., as indicated by a TDD configuration), and opportunity 4 may be configured or scheduled to occur in time domain resources that at least partially overlap with symbols associated with SSB. Therefore, it may not be desirable for UE 120 to transmit or receive using resources associated with opportunity 4. UE 120 may similarly discard other opportunities for other reasons described elsewhere herein.

[0127] In other words, UE 120 may determine that timing 1, timing 3, and timing 4 are invalid timings. UE 120 may determine that timing 2 and timing 5 are valid timings. Therefore, UE 120 may use timing 2 and timing 5 to send or receive communications. Figure 7As shown, the UE 120 may assign or apply the initial HARQ identifier determined for the semi-static period 705 to the first valid opportunity in time associated with the semi-static period 705. For example, the UE 120 may refrain from incrementing the initial HARQ identifier determined for the semi-static period 705 and / or may refrain from applying or assigning the initial HARQ identifier determined for the semi-static period 705 to opportunity 1. The UE 120 may assign or apply the initial HARQ identifier (e.g., HARQ ID 1) determined for the semi-static period 705 to opportunity 2. The UE 120 may refrain from incrementing the initial HARQ identifier determined for the semi-static period 705 and / or may refrain from applying or assigning the HARQ identifier determined for the semi-static period 705 to opportunities 3 and 4. The UE 120 may refrain from incrementing the HARQ identifier determined for the semi-static period 705 and may assign or apply the incremented HARQ identifier to opportunity 5 (e.g., the next valid opportunity in time associated with the semi-static period 705). For example, Figure 7 As shown, UE 120 may assign or apply HARQ identifier 2 to opportunity 5.

[0128] Figure 8 is a flow diagram illustrating an example process 800 performed, for example, by a UE, to support HARQ identifier determination associated with CLI measurements in accordance with the present disclosure. Example process 800 is an example of operations in which a UE (e.g., UE 120) performs operations associated with HARQ identifier determination associated with CLI measurements.

[0129] like Figure 8 As shown, in some aspects, process 800 may include receiving a configuration associated with cross-link interference from a network node, the configuration indicating one or more time domain resources associated with CLI measurement (block 810). For example, a UE (such as by using Figure 10 The communication manager 1008 or receiving component 1002 depicted in FIG may receive a configuration associated with cross-link interference from a network node, the configuration indicating one or more time domain resources associated with CLI measurement, as described above.

[0130] like Figure 8 As further shown, in some aspects, process 800 may include receiving, from the network node, scheduling information associated with scheduling a plurality of communications, the scheduling information identifying a HARQ identifier, the scheduling information indicating that resources associated with a first one or more communications in the plurality of communications do not overlap with the one or more time domain resources in a time domain, and that resources associated with a second one or more communications in the plurality of communications at least partially overlap with the one or more time domain resources associated with the CLI measurement in the time domain (block 820). For example, a UE (such as by using Figure 10The communication manager 1008 or the receiving component 1002 depicted in the figure may receive scheduling information associated with scheduling multiple communications from the network node, the scheduling information identifying a HARQ identifier, the scheduling information indicating that: resources associated with a first one or more communications in the multiple communications do not overlap with the one or more time domain resources in the time domain, and resources associated with a second one or more communications in the multiple communications at least partially overlap with the one or more time domain resources associated with the CLI measurement in the time domain, as described above.

[0131] like Figure 8 As further shown, in some aspects, process 800 may include communicating with the network node the first one or more communications associated with a corresponding HARQ identifier identified by incrementing the value of the HARQ identifier for only the first one or more communications (block 830). For example, a UE (such as by using Figure 10 The communication manager 1008, receiving component 1002, or sending component 1004 depicted in the figure may communicate the first one or more communications with the network node, the first one or more communications being associated with the corresponding HARQ identifier identified by incrementing the value of the HARQ identifier used only for the first one or more communications, as described above.

[0132] Process 800 may include additional aspects, such as any single aspect or any combination of aspects described below or in conjunction with one or more other processes described elsewhere herein.

[0133] In a first additional aspect, process 800 includes skipping HARQ identifier incrementing for the second one or more communications.

[0134] In a second additional aspect, alone or in combination with the first aspect, process 800 includes skipping assigning the HARQ identifier to the second one or more communications.

[0135] In a third additional aspect, alone or in combination with one or more of the first and second aspects, the scheduling information comprises downlink control information that schedules the plurality of communications.

[0136] In a fourth additional aspect, alone or in combination with one or more of the first to third aspects, the multiple communications include: multiple PDSCH communications, or multiple PUSCH communications.

[0137] In a fifth additional aspect, alone or in combination with one or more of the first to fourth aspects, the plurality of communications comprises a plurality of semi-static communications, and the scheduling information comprises configuration information indicating a period associated with the plurality of semi-static communications.

[0138] In a sixth additional aspect, alone or in combination with one or more of the first to fifth aspects, the HARQ identifier that is incremented only for the first one or more communications is also associated with the resource associated with the first one or more communications not overlapping with the following items in the time domain: time slots or symbols associated with conflicting communication directions, flexible time slots or symbols associated with SSB communications, or time slots or symbols associated with search spaces associated with initial access or synchronization.

[0139] In a seventh additional aspect, alone or in combination with one or more of the first to sixth aspects, process 800 includes receiving a TDD configuration indicating a pattern of communication directions for time slots or symbols, the conflicting communication directions indicated by the TDD configuration.

[0140] In an eighth additional aspect, alone or in combination with one or more of the first to seventh aspects, the HARQ identifier is associated with the period and is associated with a HARQ identifier offset value, a symbol associated with the period, and a periodicity associated with the multiple semi-static communications.

[0141] In a ninth additional aspect, either alone or in combination with one or more of aspects one to eight, process 800 comprises assigning the HARQ identifier to the communication that first appears in the time domain from the first one or more communications; and incrementing the HARQ identifier used only for the first one or more communications.

[0142] In a tenth additional aspect, alone or in combination with one or more of the first to ninth aspects, the plurality of semi-static communications comprises a plurality of SPS communications or a plurality of CG communications.

[0143] In an eleventh additional aspect, alone or in combination with one or more of aspects one to ten, process 800 comprises sending an indication to the network node that a communication from the plurality of communications or the first one or more communications will not be sent by the UE; and skipping incrementing or assigning the HARQ identifier for the communication.

[0144] In a twelfth additional aspect, alone or in combination with one or more of aspects 1 to eleven, the one or more time domain resources associated with the CLI measurement include at least one of: a first one or more symbols associated with measuring the CLI, or a second one or more symbols before or after the first one or more symbols.

[0145] although Figure 8 Example blocks of process 800 are shown, but in some aspects, process 800 may include Figure 8800. In some embodiments, the process 800 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in FIG. Additionally or alternatively, two or more blocks of the blocks of process 800 may be performed in parallel.

[0146] Figure 9 9 is a flow diagram illustrating an example process 900, performed, for example, by a network node, to support HARQ identifier determination associated with CLI measurements in accordance with the present disclosure. Example process 900 is an example of operations in which a network node (e.g., network node 110) performs operations associated with HARQ identifier determination associated with CLI measurements.

[0147] like Figure 9 As shown, in some aspects, process 900 may include sending a configuration associated with cross-link interference to the UE, the configuration indicating one or more time domain resources associated with CLI measurement (block 910). For example, a network node (such as by using Figure 11 The communication manager 1108 or the transmitting component 1104 depicted in FIG may transmit a configuration associated with cross-link interference for the UE, the configuration indicating one or more time domain resources associated with CLI measurement, as described above.

[0148] like Figure 9 As further shown, in some aspects, process 900 may include sending scheduling information associated with scheduling a plurality of communications for the UE, the scheduling information identifying a HARQ identifier, the scheduling information indicating that resources associated with a first one or more communications in the plurality of communications do not overlap with the one or more time-domain resources in the time domain, and that resources associated with a second one or more communications in the plurality of communications at least partially overlap with the one or more time-domain resources associated with the CLI measurement in the time domain (block 920). For example, a network node (such as by using Figure 11 The communication manager 1108 or the sending component 1104 depicted in the figure may send scheduling information associated with scheduling multiple communications for the UE, the scheduling information identifying a HARQ identifier, the scheduling information indicating that: resources associated with a first one or more communications in the multiple communications do not overlap with the one or more time domain resources in the time domain, and resources associated with a second one or more communications in the multiple communications at least partially overlap with the one or more time domain resources associated with the CLI measurement in the time domain, as described above.

[0149] like Figure 9As further shown, in some aspects, process 900 may include communicating the first one or more communications associated with the UE, the first one or more communications associated with the respective HARQ identifiers identified by incrementing the value of the HARQ identifier for only the first one or more communications (block 930). For example, a network node (such as by using Figure 11 The communication manager 1108, receiving component 1102, or sending component 1104 depicted in the figure may communicate the first one or more communications associated with the UE, the first one or more communications being associated with the corresponding HARQ identifier identified by incrementing the value of the HARQ identifier used only for the first one or more communications, as described above.

[0150] Process 900 may include additional aspects, such as any single aspect or any combination of aspects described below or in conjunction with one or more other processes described elsewhere herein.

[0151] In a first additional aspect, process 900 includes skipping HARQ identifier incrementing for the second one or more communications.

[0152] In a second additional aspect, alone or in combination with the first aspect, process 900 includes skipping assigning the HARQ identifier to the second one or more communications.

[0153] In a third additional aspect, alone or in combination with one or more of the first and second aspects, the scheduling information comprises downlink control information that schedules the plurality of communications.

[0154] In a fourth additional aspect, alone or in combination with one or more of the first to third aspects, the multiple communications include: multiple PDSCH communications, or multiple PUSCH communications.

[0155] In a fifth additional aspect, alone or in combination with one or more of the first to fourth aspects, the plurality of communications comprises a plurality of semi-static communications, and the scheduling information comprises configuration information indicating a period associated with the plurality of semi-static communications.

[0156] In a sixth additional aspect, alone or in combination with one or more of the first to fifth aspects, the HARQ identifier that is incremented only for the first one or more communications is also associated with the resource associated with the first one or more communications not overlapping with the following items in the time domain: time slots or symbols associated with conflicting communication directions, flexible time slots or symbols associated with SSB communications, or time slots or symbols associated with search spaces associated with initial access or synchronization.

[0157] In a seventh additional aspect, alone or in combination with one or more of the first to sixth aspects, process 900 includes sending a TDD configuration indicating a pattern of communication directions for time slots or symbols, the conflicting communication directions indicated by the TDD configuration.

[0158] In an eighth additional aspect, alone or in combination with one or more of the first to seventh aspects, the HARQ identifier is associated with the period and is associated with a HARQ identifier offset value, a symbol associated with the period, and a periodicity associated with the multiple semi-static communications.

[0159] In a ninth additional aspect, alone or in combination with one or more of aspects one to eight, process 900 comprises assigning the HARQ identifier to the communication that first appears in the time domain from the first one or more communications; and incrementing the HARQ identifier used only for the first one or more communications.

[0160] In a tenth additional aspect, alone or in combination with one or more of the first to ninth aspects, the plurality of semi-static communications comprises a plurality of SPS communications or a plurality of CG communications.

[0161] In an eleventh additional aspect, alone or in combination with one or more of aspects one to ten, process 900 comprises: receiving an indication associated with the UE that communications from the plurality of communications or the first one or more communications will not be sent by the UE; and skipping incrementing or assigning the HARQ identifier for the communication associated with receiving the indication.

[0162] In a twelfth additional aspect, alone or in combination with one or more of aspects 1 to eleven, the one or more time domain resources associated with the CLI measurement include at least one of: a first one or more symbols associated with measuring the CLI, or a second one or more symbols before or after the first one or more symbols.

[0163] although Figure 9 Example blocks of process 900 are shown, but in some aspects, process 900 may include Figure 9 The blocks depicted in the process 900 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 900. Additionally or alternatively, two or more of the blocks in the process 900 may be performed in parallel.

[0164] Figure 101 is a diagram of an example apparatus 1000 for wireless communication supporting HARQ identifier determination associated with CLI measurements according to the present disclosure. Apparatus 1000 may be a UE, or a UE may include apparatus 1000. In some aspects, apparatus 1000 includes a receiving component 1002, a transmitting component 1004, and a communication manager 1008 that may communicate with each other (e.g., via one or more buses). In some aspects, communication manager 1008 may be, or may be similar to, communication manager 140. As shown, apparatus 1000 may communicate with another apparatus 1006 (such as a UE, a network node, or another wireless communication device) using receiving component 1002 and transmitting component 1004.

[0165] In some aspects, the apparatus 1000 may be configured and / or operable to perform the Figures 5 to 7 Additionally or alternatively, the apparatus 1000 may be configured and / or operable to perform one or more of the processes described herein, such as Figure 8 In some aspects, the apparatus 1000 may include the above-mentioned process 800. Figure 2 One or more components of a described UE.

[0166] The receiving component 1002 may receive communications, such as reference signals, control information, and / or data communications, from the apparatus 1006. The receiving component 1002 may provide the received communications to one or more other components of the apparatus 1000, such as the communications manager 1008. In some aspects, the receiving component 1002 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components. In some aspects, the receiving component 1002 may include the processing described above in conjunction with Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, and / or memories of a UE are described.

[0167] The transmitting component 1004 may transmit communications, such as reference signals, control information, and / or data communications, to the device 1006. In some aspects, the communication manager 1008 may generate communications and may transmit the generated communications to the transmitting component 1004 for transmission to the device 1006. In some aspects, the transmitting component 1004 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1006. In some aspects, the transmitting component 1004 may include the above-described embodiments in conjunction with Figure 2One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, and / or memories of the described UE. In some aspects, the transmitting component 1004 can be co-located with the receiving component 1002 in a transceiver.

[0168] The communication manager 1008 may receive, or may cause the receiving component 1002 to receive, from the network node a configuration associated with cross-link interference, the configuration indicating one or more time domain resources associated with CLI measurement. The communication manager 1008 may receive, or may cause the receiving component 1002 to receive, from the network node scheduling information associated with scheduling a plurality of communications, the scheduling information indicating that resources associated with a first one or more communications in the plurality of communications do not overlap with the one or more time domain resources in the time domain, and that resources associated with a second one or more communications in the plurality of communications at least partially overlap with the one or more time domain resources associated with the CLI measurement in the time domain, and the scheduling information is associated with a HARQ identifier. The communication manager 1008 may communicate the first one or more communications to the network node, the first one or more communications being associated with corresponding HARQ identifiers, the corresponding HARQ identifiers being associated with incrementing the HARQ identifiers for use only with the first one or more communications. In some aspects, the communication manager 1008 may perform one or more operations described elsewhere herein as being performed by one or more components of the communication manager 1008.

[0169] The communication manager 1008 may include the above combined Figure 2 In some aspects, the communication manager 1008 includes a set of components, such as a HARQ processing component 1010, etc. Alternatively, the set of components may be separate and distinct from the communication manager 1008. In some aspects, one or more components in the set of components may include the components described above in conjunction with Figure 2 The controller / processor, memory of the UE described herein may be implemented in the controller / processor, memory, or may be implemented in the controller / processor, memory. Additionally or alternatively, one or more components in the component set may be at least partially implemented as software stored in the memory. For example, a component (or a portion of a component) may be implemented as an instruction or code that is stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0170] Receiving component 1002 may receive a configuration associated with cross-link interference from a network node, the configuration indicating one or more time domain resources associated with CLI measurement. Receiving component 1002 may receive scheduling information associated with scheduling multiple communications from the network node, the scheduling information indicating that resources associated with a first one or more communications in the multiple communications do not overlap with the one or more time domain resources in the time domain, and that resources associated with a second one or more communications in the multiple communications at least partially overlap with the one or more time domain resources associated with the CLI measurement in the time domain, and the scheduling information is associated with a HARQ identifier. Receiving component 1002 and / or transmitting component 1004 may communicate the first one or more communications to the network node, the first one or more communications being associated with corresponding HARQ identifiers, the corresponding HARQ identifiers being associated with the HARQ identifiers that are incremented only for the first one or more communications.

[0171] The HARQ processing component 1010 can skip incrementing the HARQ identifier for the second one or more communications.

[0172] The HARQ processing component 1010 can skip assigning the HARQ identifier to the second one or more communications.

[0173] Receiving component 1002 can receive a TDD configuration indicating a pattern of communication directions for time slots or symbols, the conflicting communication directions being indicated by the TDD configuration.

[0174] The HARQ processing component 1010 can assign the HARQ identifier to a communication that first occurs in the time domain from the first one or more communications.

[0175] The HARQ processing component 1010 can increment the HARQ identifier only for the first one or more communications.

[0176] Transmitting component 1004 can transmit an indication to the network node that a communication from the plurality of communications or the first one or more communications is not to be transmitted by the apparatus 1000 .

[0177] HARQ processing component 1010 can refrain from incrementing or assigning the HARQ identifier for the communication.

[0178] Figure 10 The number and arrangement of components shown are provided as examples. In practice, there may be Figure 10 The components shown may include additional components, fewer components, different components, or components arranged in a different manner. Figure 10 Two or more components shown may be implemented in a single component, or Figure 10The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Figure 10 The illustrated set of component(s) may be described as being executable by Figure 10 Another component shown is a collection of one or more functions performed.

[0179] Figure 11 1 is a diagram of an example apparatus 1100 for wireless communication supporting HARQ identifier determination associated with CLI measurements according to the present disclosure. Apparatus 1100 may be a network node, or a network node may include apparatus 1100. In some aspects, apparatus 1100 includes a receiving component 1102, a transmitting component 1104, and a communication manager 1108 that may communicate with each other (e.g., via one or more buses). Communication manager 1108 may be, or may be similar to, communication manager 150. As shown, apparatus 1100 may communicate with another apparatus 1106 (such as a UE, a network node, or another wireless communication device) using receiving component 1102 and transmitting component 1104.

[0180] In some aspects, the apparatus 1100 may be configured and / or operable to perform the Figures 5 to 7 Additionally or alternatively, the apparatus 1100 may be configured and / or operable to perform one or more of the processes described herein, such as Figure 9 In some aspects, the apparatus 1100 may include the process 900 described above in conjunction with Figure 2 One or more components of a described network node.

[0181] The receiving component 1102 may receive communications, such as reference signals, control information, and / or data communications, from the apparatus 1106. The receiving component 1102 may provide the received communications to one or more other components of the apparatus 1100, such as the communications manager 1108. In some aspects, the receiving component 1102 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components. In some aspects, the receiving component 1102 may include the processing described above in conjunction with Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, and / or memories of the described network nodes.

[0182] The transmitting component 1104 may transmit communications, such as reference signals, control information, and / or data communications, to the device 1106. In some aspects, the communication manager 1108 may generate communications and may transmit the generated communications to the transmitting component 1104 for transmission to the device 1106. In some aspects, the transmitting component 1104 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1106. In some aspects, the transmitting component 1104 may include the above-described embodiments in conjunction with Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, and / or memories of the described network nodes. In some aspects, the transmitting component 1104 can be co-located with the receiving component 1102 in a transceiver.

[0183] The communications manager 1108 may transmit, or may cause the transmitting component 1104 to transmit, a configuration associated with cross-link interference for a UE, the configuration indicating one or more time domain resources associated with CLI measurement. The communications manager 1108 may transmit, or may cause the transmitting component 1104 to transmit, scheduling information associated with scheduling a plurality of communications for the UE, the scheduling information indicating that resources associated with a first one or more communications in the plurality of communications do not overlap with the one or more time domain resources in the time domain, and that resources associated with a second one or more communications in the plurality of communications at least partially overlap with the one or more time domain resources associated with the CLI measurement in the time domain, and the scheduling information is associated with a HARQ identifier. The communications manager 1108 may convey the first one or more communications associated with the UE, the first one or more communications associated with corresponding HARQ identifiers, the corresponding HARQ identifiers associated with incrementing the HARQ identifiers for only the first one or more communications. In some aspects, the communications manager 1108 may perform one or more operations described elsewhere herein as being performed by one or more components of the communications manager 1108.

[0184] The communication manager 1108 may include the above combined Figure 2 In some aspects, the communication manager 1108 includes a set of components, such as a HARQ processing component 1110, etc. Alternatively, the set of components may be separate and distinct from the communication manager 1108. In some aspects, one or more components in the set of components may include the components described above in conjunction with Figure 2The controller / processor, memory, scheduler and / or communication unit of the network node described herein may be implemented in, or may be implemented in, the controller / processor, memory, scheduler and / or communication unit of the network node described herein. Additionally or alternatively, one or more components in the component set may be at least partially implemented as software stored in the memory. For example, a component (or a portion of a component) may be implemented as instructions or code that is stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0185] The transmitting component 1104 may transmit a configuration associated with cross-link interference for the UE, the configuration indicating one or more time domain resources associated with the CLI measurement. The transmitting component 1104 may transmit scheduling information associated with scheduling multiple communications for the UE, the scheduling information indicating that resources associated with a first one or more communications in the multiple communications do not overlap with the one or more time domain resources in the time domain, and resources associated with a second one or more communications in the multiple communications at least partially overlap with the one or more time domain resources associated with the CLI measurement in the time domain, and the scheduling information is associated with a HARQ identifier. The receiving component 1102 and / or the transmitting component 1104 may convey the first one or more communications associated with the UE, the first one or more communications being associated with a corresponding HARQ identifier, the corresponding HARQ identifier being associated with the HARQ identifier that is incremented only for the first one or more communications.

[0186] The HARQ processing component 1110 can refrain from incrementing the HARQ identifier for the second one or more communications.

[0187] The HARQ processing component 1110 can refrain from assigning the HARQ identifier to the second one or more communications.

[0188] Transmitting component 1104 can transmit a TDD configuration indicating a pattern of communication directions for time slots or symbols, the conflicting communication directions indicated by the TDD configuration.

[0189] The HARQ processing component 1110 can assign the HARQ identifier to a communication that first occurs in the time domain from the first one or more communications.

[0190] The HARQ processing component 1110 can increment the HARQ identifier only for the first one or more communications.

[0191] Receiving component 1102 can receive an indication associated with the UE that a communication from the plurality of communications or the first one or more communications is not to be sent by the UE.

[0192] The HARQ processing component 1110 can refrain from incrementing or assigning the HARQ identifier for the communication in association with receiving the indication.

[0193] Figure 11 The number and arrangement of components shown in the figure are provided as examples. In practice, there may be Figure 11 The components shown may include additional components, fewer components, different components, or components arranged in a different manner. Figure 11 Two or more components shown may be implemented in a single component, or Figure 11 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Figure 11 The shown collection of component(s) may perform the operations described as being performed by Figure 11 Another component shown as a collection of components performs one or more functions.

[0194] The following provides an overview of some aspects of the disclosure:

[0195] Aspect 1: A method of wireless communication performed by a user equipment (UE), comprising: receiving a configuration associated with cross-link interference from a network node, the configuration indicating one or more time domain resources associated with cross-link interference (CLI) measurement; receiving scheduling information associated with scheduling multiple communications from the network node, the scheduling information identifying a hybrid automatic repeat request (HARQ) identifier, and the scheduling information indicating: resources associated with a first one or more communications of the multiple communications do not overlap with the one or more time domain resources in the time domain, and resources associated with a second one or more communications of the multiple communications at least partially overlap with the one or more time domain resources associated with the CLI measurement in the time domain; and communicating the first one or more communications with the network node, the first one or more communications being associated with corresponding HARQ identifiers identified by incrementing the value of the HARQ identifier used only for the first one or more communications.

[0196] Aspect 2: The method according to aspect 1, further comprising: skipping HARQ identifier incrementing for the second one or more communications.

[0197] Aspect 3: The method according to any one of aspects 1 to 2, further comprising: skipping assigning the HARQ identifier to the second one or more communications.

[0198] Aspect 4: The method according to any one of aspects 1 to 3, wherein the scheduling information includes downlink control information that schedules the multiple communications.

[0199] Aspect 5: The method according to any one of aspects 1 to 4, wherein the multiple communications include: multiple physical downlink shared channel (PDSCH) communications, or multiple physical uplink shared channel (PUSCH) communications.

[0200] Aspect 6: The method according to any one of aspects 1 to 5, wherein the plurality of communications comprises a plurality of semi-static communications, and the scheduling information comprises configuration information indicating a period associated with the plurality of semi-static communications.

[0201] Aspect 7: A method according to Aspect 6, wherein only the value of the HARQ identifier used for the first one or more communications is incremented and is also associated with the resources associated with the first one or more communications not overlapping with the following items in the time domain: time slots or symbols associated with conflicting communication directions, flexible time slots or symbols associated with synchronization signal block (SSB) communications, or time slots or symbols associated with search spaces associated with initial access or synchronization.

[0202] Aspect 8: The method according to aspect 7, further comprising: receiving a time division duplex (TDD) configuration indicating a pattern of communication directions for time slots or symbols, the conflicting communication directions being indicated by the TDD configuration.

[0203] Aspect 9: The method of aspect 6, wherein the HARQ identifier is associated with the period and is associated with a HARQ identifier offset value, a symbol associated with the period, and a periodicity associated with the plurality of semi-static communications.

[0204] Aspect 10: The method of aspect 9, further comprising: assigning the HARQ identifier to a communication that first occurs in the time domain from among the first one or more communications; and incrementing the HARQ identifier used only for the first one or more communications.

[0205] Aspect 11: The method according to any one of aspects 6 to 10, wherein the plurality of semi-static communications comprises a plurality of semi-persistent scheduling (SPS) communications or a plurality of configuration grant (CG) communications.

[0206] Aspect 12: The method according to any one of aspects 1 to 11 further includes: sending an indication to the network node that a communication from the multiple communications or the first one or more communications will not be sent by the UE; and skipping incrementing or assigning the HARQ identifier for the communication.

[0207] Aspect 13: The method according to any one of Aspects 1 to 12, wherein the one or more time domain resources associated with the CLI measurement include at least one of the following: a first one or more symbols associated with measuring CLI, or a second one or more symbols before or after the first one or more symbols.

[0208] Aspect 14: A method of wireless communication performed by a network node, comprising: sending a configuration associated with cross-link interference to a user equipment (UE), the configuration indicating one or more time domain resources associated with cross-link interference (CLI) measurement; sending scheduling information associated with scheduling multiple communications to the UE, the scheduling information identifying a hybrid automatic repeat request (HARQ) identifier, and the scheduling information indicating: resources associated with a first one or more communications among the multiple communications do not overlap with the one or more time domain resources in the time domain, and resources associated with a second one or more communications among the multiple communications at least partially overlap with the one or more time domain resources associated with the CLI measurement in the time domain; and conveying the first one or more communications associated with the UE, the first one or more communications being associated with corresponding HARQ identifiers identified by incrementing the value of the HARQ identifier used only for the first one or more communications.

[0209] Aspect 15: The method of aspect 14, further comprising: skipping HARQ identifier incrementing for the second one or more communications.

[0210] Aspect 16: The method according to any one of aspects 14 to 15, further comprising: skipping assigning the HARQ identifier to the second one or more communications.

[0211] Aspect 17: The method according to any one of aspects 14 to 16, wherein the scheduling information includes downlink control information scheduling the plurality of communications.

[0212] Aspect 18: The method according to any one of aspects 14 to 17, wherein the multiple communications include: multiple physical downlink shared channel (PDSCH) communications, or multiple physical uplink shared channel (PUSCH) communications.

[0213] Aspect 19: The method according to any one of aspects 14 to 18, wherein the plurality of communications comprises a plurality of semi-static communications, and the scheduling information comprises configuration information indicating a period associated with the plurality of semi-static communications.

[0214] Aspect 20: A method according to Aspect 19, wherein the value of the HARQ identifier used for the first one or more communications is only incremented and is also associated with the resources associated with the first one or more communications not overlapping with the following items in the time domain: time slots or symbols associated with conflicting communication directions, flexible time slots or symbols associated with synchronization signal block (SSB) communications, or time slots or symbols associated with search spaces associated with initial access or synchronization.

[0215] Aspect 21: The method according to aspect 20, further comprising: transmitting a time division duplex (TDD) configuration indicating a pattern of communication directions for time slots or symbols, the conflicting communication directions being indicated by the TDD configuration.

[0216] Aspect 22: The method according to any one of aspects 19 to 21, wherein the HARQ identifier is associated with the period and is associated with a HARQ identifier offset value, a symbol associated with the period, and a periodicity associated with the plurality of semi-static communications.

[0217] Aspect 23: The method of aspect 22, further comprising: assigning the HARQ identifier to a communication that first occurs in the time domain from among the first one or more communications; and incrementing the HARQ identifier used only for the first one or more communications.

[0218] Aspect 24: The method according to any one of aspects 19 to 23, wherein the plurality of semi-static communications comprises a plurality of semi-persistent scheduling (SPS) communications or a plurality of configuration grant (CG) communications.

[0219] Aspect 25: The method according to any one of Aspects 14 to 24 further includes: receiving an indication associated with the UE that communications from the multiple communications or the first one or more communications will not be sent by the UE; and skipping the incrementing or assignment of the HARQ identifier used for the communication in association with receiving the indication.

[0220] Aspect 26: A method according to any one of Aspects 14 to 25, wherein the one or more time domain resources associated with the CLI measurement include at least one of the following: a first one or more symbols associated with measuring CLI, or a second one or more symbols before or after the first one or more symbols.

[0221] Aspect 27: An apparatus for wireless communication at a device, 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 one or more of the methods described in aspects 1 to 13.

[0222] Aspect 28: An apparatus for wireless communication, comprising: a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 1 to 13.

[0223] Aspect 29: An apparatus for wireless communication, comprising: at least one component for performing the method according to one or more of aspects 1 to 13.

[0224] Aspect 30: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 13.

[0225] Aspect 31: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 13.

[0226] Aspect 32: An apparatus for wireless communication at a device, 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 one or more of the methods described in aspects 14 to 26.

[0227] Aspect 33: An apparatus for wireless communication, comprising: a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 14 to 26.

[0228] Aspect 34: An apparatus for wireless communication, comprising: at least one component for performing the method according to one or more of aspects 14 to 26.

[0229] Aspect 35: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 14 to 26.

[0230] Aspect 36: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 14 to 26.

[0231] While the foregoing disclosure provides illustration and description, it is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of these aspects.

[0232] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware or hardware and software. "Software" should be broadly interpreted as meaning an instruction, an instruction set, a code, a code segment, a program code, a program, a subroutine, a software module, an application, a software application, a software package, a routine, a subroutine, an object, an executable program, a thread of execution, a process or a function, etc., whether it is described in software, firmware, middleware, microcode, hardware description language or other terms. As used herein, a "processor" is implemented with hardware or a combination of hardware and software. It will be apparent that the system or method described herein can be implemented in different forms of hardware or a combination of hardware and software. The actual dedicated control hardware or software code for implementing these systems or methods does not limit various aspects. Therefore, the operation and behavior of these systems or methods are described herein without reference to specific software code, because those skilled in the art will understand that software and hardware can be designed to implement these systems or methods at least in part based on the description herein.

[0233] As used herein, "satisfying a threshold" may mean a value is greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0234] Although specific combinations of features are described in the claims or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner not specifically described in the claims or not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" a list of items refers to any combination of these items (which includes a single member). As an example, "at least one of the following: a, b, or c" is intended to cover a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination of multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other arrangement of a, b, and c).

[0235] Any element, action or instruction used herein should not be interpreted as key or necessary unless explicitly described as such. In addition, as used herein, the articles "one" and "a kind of" are intended to include one or more projects and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more projects connected with the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "group" and "cluster" are intended to include one or more projects and can be used interchangeably with "one or more". If only want to refer to a project, then use the phrase "only one" or similar terms. Moreover, as used herein, the terms "having", "containing", "comprising" and similar terms are intended to be open terms, which do not limit the elements they modify (for example, element "comprising" A can also contain B). In addition, the phrase "based on" is intended to represent "at least partially based on", unless explicitly stated otherwise. Furthermore, as used herein, the term "or" when used continuously is intended to be inclusive and is used interchangeably with "and / or" unless expressly stated otherwise (e.g., if used in conjunction with "either" or "only one of").

Claims

1. A user equipment (UE) for wireless communication, comprising: at least one memory; and at least one processor communicatively coupled to the at least one memory, the at least one processor operable to cause the UE to: receiving a configuration associated with cross-link interference from a network node, the configuration indicating one or more time domain resources associated with cross-link interference (CLI) measurement; Receiving scheduling information associated with scheduling a plurality of communications from the network node, the scheduling information identifying a hybrid automatic repeat request (HARQ) identifier, and the scheduling information indicating: resources associated with a first one or more communications of the plurality of communications do not overlap in the time domain with the one or more time domain resources, and resources associated with second one or more communications of the plurality of communications at least partially overlap in the time domain with the one or more time domain resources associated with the CLI measurement; as well as The first one or more communications are communicated with the network node, the first one or more communications being associated with respective HARQ identifiers identified by incrementing a value of the HARQ identifier used only for the first one or more communications.

2. The UE of claim 1 , wherein the at least one processor is further operable to cause the UE to: HARQ identifier incrementing for the second one or more communications is skipped.

3. The UE of claim 1 , wherein the at least one processor is further operable to cause the UE to: Assigning the HARQ identifier to the second one or more communications is skipped. The UE of claim 1 , wherein the scheduling information comprises downlink control information that schedules the plurality of communications.

5. The UE of claim 1 , wherein the plurality of communications comprises: Multiple Physical Downlink Shared Channel (PDSCH) communications, or Multiple Physical Uplink Shared Channel (PUSCH) communications. 6 . The UE of claim 1 , wherein the plurality of communications comprises a plurality of semi-static communications, and the scheduling information comprises configuration information indicating a period associated with the plurality of semi-static communications.

7. The UE of claim 1 , wherein the at least one processor is further operable to cause the UE to: sending an indication to the network node that a communication from the plurality of communications or the first one or more communications is not to be sent by the UE; and Incrementing or assigning the HARQ identifier for the communication is skipped.

8. The UE according to claim 1 , wherein the one or more time domain resources associated with the CLI measurement include at least one of the following: the first one or more symbols associated with the measurement CLI, or A second one or more symbols that precede or follow the first one or more symbols.

9. A network node for wireless communication, comprising: at least one memory; and at least one processor communicatively coupled to the at least one memory, the at least one processor operable to cause the network node to: transmitting a configuration associated with cross-link interference for a user equipment (UE), the configuration indicating one or more time domain resources associated with cross-link interference (CLI) measurement; Sending scheduling information associated with scheduling multiple communications for the UE, the scheduling information identifying a hybrid automatic repeat request (HARQ) identifier, and the scheduling information indicating: resources associated with a first one or more communications of the plurality of communications do not overlap in the time domain with the one or more time domain resources, and resources associated with second one or more communications of the plurality of communications at least partially overlap in the time domain with the one or more time domain resources associated with the CLI measurement; as well as The first one or more communications associated with the UE are communicated, the first one or more communications being associated with respective HARQ identifiers identified by incrementing a value of the HARQ identifier used only for the first one or more communications.

10. The network node of claim 9, wherein the at least one processor is further operable to cause the network node to: HARQ identifier incrementing for the second one or more communications is skipped.

11. The network node of claim 9, wherein the at least one processor is further operable to cause the network node to: Assigning the HARQ identifier to the second one or more communications is skipped.

12. The network node of claim 9, wherein the scheduling information comprises downlink control information that schedules the plurality of communications.

13. The network node of claim 9, wherein the plurality of communications comprises: Multiple Physical Downlink Shared Channel (PDSCH) communications, or Multiple Physical Uplink Shared Channel (PUSCH) communications.

14. The network node of claim 9, wherein the at least one processor is further operable to cause the network node to: receiving an indication that a communication from the plurality of communications or the first one or more communications associated with the UE is not to be sent by the UE; and Incrementing or assigning the HARQ identifier for the communication is skipped in association with receiving the indication.

15. The network node of claim 9, wherein the one or more time domain resources associated with the CLI measurement include at least one of: the first one or more symbols associated with the measurement CLI, or A second one or more symbols that precede or follow the first one or more symbols.

16. A method of wireless communication performed by a user equipment (UE), comprising: receiving a configuration associated with cross-link interference from a network node, the configuration indicating one or more time domain resources associated with cross-link interference (CLI) measurement; Receiving scheduling information associated with scheduling a plurality of communications from the network node, the scheduling information being associated with a hybrid automatic repeat request (HARQ) identifier, and the scheduling information indicating: resources associated with a first one or more communications of the plurality of communications do not overlap in the time domain with the one or more time domain resources, and resources associated with second one or more communications of the plurality of communications at least partially overlap in the time domain with the one or more time domain resources associated with the CLI measurement; as well as The first one or more communications are communicated with the network node, the first one or more communications being associated with respective HARQ identifiers identified by incrementing a value of the HARQ identifier used only for the first one or more communications.

17. The method of claim 16, wherein the plurality of communications comprises a plurality of semi-static communications, and the scheduling information comprises configuration information indicating a period associated with the plurality of semi-static communications.

18. The method of claim 17, wherein incrementing the value of the HARQ identifier for only the first one or more communications is further associated with the resources associated with the first one or more communications not overlapping in the time domain with: the time slots or symbols associated with the conflicting communication directions, Flexible time slots or symbols associated with synchronization signal block (SSB) communications, or The time slots or symbols associated with the search space associated with initial access or synchronization.

19. The method according to claim 18, further comprising: A time division duplex (TDD) configuration is received that indicates a pattern of communication directions for time slots or symbols, the conflicting communication directions being indicated by the TDD configuration.

20. The method of claim 17, wherein the HARQ identifier is associated with the period and is associated with a HARQ identifier offset value, a symbol associated with the period, and a periodicity associated with the plurality of semi-static communications.

21. The method according to claim 20, further comprising: assigning the HARQ identifier to a communication from the first one or more communications that first occurs in the time domain; as well as The HARQ identifier is incremented only for the first one or more communications.

22. The method of claim 17, wherein the plurality of semi-persistent communications comprises a plurality of semi-persistent scheduling (SPS) communications or a plurality of configuration grant (CG) communications.

23. A method of wireless communication performed by a network node, comprising: transmitting a configuration associated with cross-link interference for a user equipment (UE), the configuration indicating one or more time domain resources associated with cross-link interference (CLI) measurement; Sending scheduling information associated with scheduling multiple communications for the UE, the scheduling information being associated with a hybrid automatic repeat request (HARQ) identifier and indicating: resources associated with a first one or more communications of the plurality of communications do not overlap in the time domain with the one or more time domain resources, and resources associated with second one or more communications of the plurality of communications at least partially overlap in the time domain with the one or more time domain resources associated with the CLI measurement; as well as The first one or more communications associated with the UE are communicated, the first one or more communications being associated with respective HARQ identifiers identified by incrementing a value of the HARQ identifier used only for the first one or more communications.

24. The method of claim 23, wherein the plurality of communications comprises a plurality of semi-static communications, and the scheduling information comprises configuration information indicating a period associated with the plurality of semi-static communications.

25. The method of claim 24, wherein incrementing the value of the HARQ identifier for only the first one or more communications is further associated with the resources associated with the first one or more communications not overlapping in the time domain with: the time slots or symbols associated with the conflicting communication directions, Flexible time slots or symbols associated with synchronization signal block (SSB) communications, or The time slots or symbols associated with the search space associated with initial access or synchronization.

26. The method according to claim 25, further comprising: A time division duplex (TDD) configuration is transmitted that indicates a pattern of communication directions for time slots or symbols, the conflicting communication directions being indicated by the TDD configuration.

27. The method of claim 24, wherein the HARQ identifier is associated with the period and is associated with a HARQ identifier offset value, a symbol associated with the period, and a periodicity associated with the plurality of semi-static communications.

28. The method according to claim 27, further comprising: assigning the HARQ identifier to a communication from the first one or more communications that first occurs in the time domain; as well as The HARQ identifier is incremented only for the first one or more communications.

29. The method of claim 24, wherein the plurality of semi-static communications comprises a plurality of semi-persistent scheduling (SPS) communications or a plurality of configuration grant (CG) communications.

30. The method of claim 23, wherein the one or more time domain resources associated with the CLI measurement include at least one of: the first one or more symbols associated with the measurement CLI, or A second one or more symbols that precede or follow the first one or more symbols.

Images