Techniques for downlink feedback from multiple transmit and receive points

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) may transmit uplink messages to at least one TRP in a set of TRP, wherein each uplink message is associated with a first control resource set (CORESET) pool index value or a second CORESET pool index value and with a hybrid automatic repeat request (HARQ) identifier in a set of HARQ identifiers. In some cases, the UE may receive downlink feedback information (DFI) for the set of HARQ identifiers, where the DFI is associated with the first COREST pool index value or the second CORESET pool index value. Further, the DFI may be valid for at least one HARQ identifier of the set of HARQ identifiers based on a CORESET pool index value associated with the DFI and a CORESET pool index value associated with at least one uplink message.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. patent application No. 17 / 855,997, entitled “TECHNIQUES FOR DOWNLINK FEEDBACK FROM MULTIPLE TRANSMISSION AND RECEPTION POINTS,” filed by KHOSHNEVISAN et al. on July 1, 2022, which is assigned to the assignee of this patent application. Technical Field

[0003] The following relates to wireless communications, including techniques for downlink feedback from multiple transmit and receive points. Background Art

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

[0005] The described technology relates to improved methods, systems, devices and apparatuses that support technology for downlink feedback from multiple transmit and receive points (TRPs). For example, the technology described herein can enable a user equipment (UE) to verify downlink feedback information (DFI) from two or more TRPs for a hybrid automatic repeat request (HARQ) identifier (ID) set. The UE may send one or more uplink messages to at least one TRP in the TRP set, wherein each uplink message is associated with a first control resource set (CORESET) pool index or a second CORESET pool index. Additionally, each uplink message may be associated with a HARQ ID in the HARQ ID set. In some cases, the UE may receive a downlink message indicating a DFI for the HARQ ID set from a TRP in the TRP set, wherein the DFI is associated with the first CORESET pool index or the second CORESET pool index.

[0006] In some cases, the DFI may be valid for at least one HARQ ID in the set of HARQ IDs based on a CORESET pool index associated with the DFI and a CORESET pool index associated with at least one uplink message of the one or more uplink messages (e.g., an uplink message associated with at least one HARQ ID). For example, the DFI for a first HARQ ID in the set of HARQ IDs may be valid based on the CORESET pool index associated with the DFI and the CORESET pool index associated with the first uplink message being the same. In such cases, the DFI for the first HARQ ID may be valid based on the first symbol of the downlink message occurring at a first time threshold after the last symbol of the first uplink message associated with the first HARQ ID. Alternatively, the COREST pool index associated with the DFI and the COREST pool index associated with the first uplink message may be different, and the DFI for the first HARQ ID may be valid based on the first symbol of the downlink message appearing at a second time threshold after the last symbol of the first uplink message associated with the first HARQ ID.

[0007] A method for wireless communication at a UE is described. The method may include: sending one or more uplink messages to at least one TRP in a set of multiple TRPs, wherein each of the one or more uplink messages is associated with a first CORESET pool index value or a second CORESET pool index value, and wherein each uplink message is associated with a HARQ ID in a set of HARQ IDs. The method may include: receiving a downlink message indicating a DFI for the set of HARQ IDs from a TRP in the set of multiple TRPs, wherein the DFI is associated with the first CORESET pool index value or the second CORESET pool index value, and wherein based on the CORESET pool index value associated with the DFI and the CORESET pool index value associated with at least one of the one or more uplink messages, the DFI is valid for at least one HARQ ID in the set of HARQ IDs.

[0008] An apparatus for wireless communication at a UE is described. The apparatus may include: a processor; a memory coupled to the processor; and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: send one or more uplink messages to at least one TRP in a set of multiple TRPs, wherein each of the one or more uplink messages is associated with a first CORESET pool index value or a second CORESET pool index value, and wherein each uplink message is associated with a HARQ ID in a HARQ ID set; and receive a downlink message indicating a DFI for the HARQ ID set from a TRP in the set of multiple TRPs, wherein the DFI is associated with the first CORESET pool index value or the second CORESET pool index value, and wherein based on the CORESET pool index value associated with the DFI and the CORESET pool index value associated with at least one of the one or more uplink messages, the DFI is valid for at least one HARQ ID in the HARQ ID set.

[0009] Another apparatus for wireless communication at a UE is described. The apparatus may include: a component for sending one or more uplink messages to at least one TRP in a set of multiple TRPs, wherein each of the one or more uplink messages is associated with a first CORESET pool index value or a second CORESET pool index value, and wherein each uplink message is associated with a HARQ ID in a set of HARQ IDs; and a component for receiving a downlink message indicating a DFI for the set of HARQ IDs from a TRP in the set of multiple TRPs, wherein the DFI is associated with the first CORESET pool index value or the second CORESET pool index value, and wherein based on the CORESET pool index value associated with the DFI and the CORESET pool index value associated with at least one of the one or more uplink messages, the DFI is valid for at least one HARQ ID in the set of HARQ IDs.

[0010] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to perform the following operations: sending one or more uplink messages to at least one TRP in a set of multiple TRPs, wherein each of the one or more uplink messages is associated with a first CORESET pool index value or a second CORESET pool index value, and wherein each uplink message is associated with a HARQ ID in a HARQ ID set; and receiving a downlink message indicating a DFI for the HARQ ID set from a TRP in the set of multiple TRPs, wherein the DFI is associated with the first CORESET pool index value or the second CORESET pool index value, and wherein based on the CORESET pool index value associated with the DFI and the CORESET pool index value associated with at least one of the one or more uplink messages, the DFI is valid for at least one HARQ ID in the HARQ ID set.

[0011] Some examples of the methods, apparatus and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining that the DFI for a first HARQ ID in the HARQ ID set may be valid based on the first symbol of the downlink message appearing at a first time threshold after the last symbol of the first uplink message associated with the first HARQ ID in the HARQ ID set, wherein the first time threshold may be used to identify a most recently sent uplink message associated with at least one HARQ ID in the HARQ ID set.

[0012] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining that the DFI for the first HARQ ID in the HARQ ID set may be valid based on the CORESET pool index value associated with the DFI being the same as the CORESET pool index value associated with the first uplink message.

[0013] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining that the DFI for the first HARQ ID in the HARQ ID set may be valid based on the first symbol of the downlink message appearing at a second time threshold after the last symbol of the first uplink message associated with the first HARQ ID, wherein the CORESET pool index value associated with the DFI and the CORESET pool index value associated with the first uplink message may be different.

[0014] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving control signaling indicating the second time threshold.

[0015] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the second time threshold may be greater than or equal to the first time threshold, which may be used to identify the most recently sent uplink message associated with at least one HARQ ID in the HARQ ID set.

[0016] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: receiving a control message instructing each TRP in the set of multiple TRPs to send a corresponding DFI; and determining whether the DFI is valid based on the control message.

[0017] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the downlink message may include operations, features, components, or instructions for the following actions: receiving the downlink message via a CORESET associated with the first CORESET pool index value or the second CORESET pool index value, wherein the CORESET pool index value associated with the DFI corresponds to the first CORESET pool index value or the second CORESET pool index value associated with the CORESET used to receive the downlink message.

[0018] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving, within the downlink message, an indication of the CORESET pool index value associated with the DFI.

[0019] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: identifying a most recently transmitted uplink message among the one or more uplink messages for each HARQ ID in the HARQ ID set, identifying the most recently transmitted uplink message for each HARQ ID based on the first symbol of the downlink message appearing at a time threshold after the last symbol of each most recently transmitted first uplink message; and determining whether the DFI can be valid based on the most recently transmitted uplink message for each HARQ ID.

[0020] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: determining the CORESET pool index value associated with the at least one uplink message based on the CORESET pool index value associated with the corresponding control message that schedules the at least one uplink message, wherein the CORESET pool index value associated with the corresponding control message may be based on the CORESET used to receive the corresponding control message.

[0021] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving one or more control messages indicating one or more configured authorization configurations associated with the one or more uplink messages, wherein each of the one or more configured authorization configurations indicates the first CORESET pool index value or the second CORESET pool index value, and wherein the CORESET pool index value associated with each of the one or more uplink messages may be based on the one or more configured authorization configurations.

[0022] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving one or more control messages indicating one or more configured authorization configurations associated with the one or more uplink messages, wherein corresponding downlink control information for activating each of the one or more configured authorization configurations may be received via a corresponding CORESET associated with the first CORESET pool index value or the second CORESET pool index value, and wherein the CORESET pool index value associated with each of the one or more uplink messages may be based on the first CORESET pool index value or the second CORESET pool index value associated with the corresponding CORESET used to receive the corresponding downlink control information.

[0023] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the CORESET pool index value associated with each of the one or more uplink messages may be based on a corresponding HARQ ID in the HARQ ID set that may be associated with each uplink message, and each HARQ ID corresponds to the first CORESET pool index value or the second CORESET pool index value.

[0024] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first CORESET pool index value may be associated with a first TRP in the set of multiple TRPs, and the second CORESET pool index value may be associated with a second TRP in the set of multiple TRPs. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] Figure 1 An example of a wireless communication system supporting techniques for downlink feedback from multiple transmission and reception points in accordance with one or more aspects of the present disclosure is illustrated.

[0026] Figure 2 An example of a wireless communication system supporting techniques for downlink feedback from multiple transmission and reception points in accordance with one or more aspects of the present disclosure is illustrated.

[0027] Figure 3A and Figure 3B An example of a verification process for techniques supporting downlink feedback from multiple transmission and reception points in accordance with one or more aspects of the present disclosure is illustrated.

[0028] Figure 4 An example of a process flow in a system supporting techniques for downlink feedback from multiple transmission and reception points in accordance with one or more aspects of the present disclosure is illustrated.

[0029] Figure 5 and Figure 6 A block diagram of a device supporting techniques for downlink feedback from multiple transmission and reception points in accordance with one or more aspects of the present disclosure is shown.

[0030] Figure 7 A block diagram of a communications manager supporting techniques for downlink feedback from multiple transmission and reception points in accordance with one or more aspects of the present disclosure is shown.

[0031] Figure 8

[0013] A diagram of a system including devices supporting techniques for downlink feedback from multiple transmission and reception points in accordance with one or more aspects of the present disclosure is shown.

[0032] Figures 9 to 11 A flow chart illustrating a method of supporting techniques for downlink feedback from multiple transmission and reception points in accordance with one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0033] Some wireless communication systems may support communication with a transmit and receive point (TRP), which may be referred to as multi-TRP (mTRP) communication, where a user equipment (UE) communicates with multiple TRPs. Additionally, each of the multiple TRPs may send separate downlink control information (DCI) to the UE (e.g., which may be referred to as mTRP multi-DCI communication). In some cases, the UE may send an uplink message to each of the multiple TRPs, and each uplink message may be associated with a hybrid automatic repeat request (HARQ) identifier (ID) in a set (e.g., a set of 16 HARQ IDs), so that the UE may expect to receive feedback for the HARQ ID set, which may be referred to as downlink feedback information (DFI). The UE may receive a downlink message (e.g., DCI) indicating a DFI associated with the HARQ ID set from a first TRP in the multiple TRPs. However, it may be challenging to determine whether the DFI is valid in the presence of multiple TRPs. For example, the DFI may include HARQ feedback for all HARQ IDs (e.g., all 16 HARQ IDs), but decoding information for uplink transmissions received at a first TRP may not be available at a second, different TRP. Therefore, the second TRP may not be able to send a DFI including HARQ feedback for the HARQ ID to the UE without incurring a certain delay (e.g., based on the time for the corresponding TRP to convey the decoding results of the message received from the UE, which may be exacerbated if the backhaul link between the TRPs is not ideal). In addition, the corresponding HARQ ID may not be associated with one TRP or another (e.g., each HARQ ID may be used by any TRP in different scheduling instances), and it may be difficult to determine the validity of the DFI included in a single message from one TRP.

[0034] The techniques described herein may enable a UE to determine whether a DFI associated with at least one HARQ ID in a set of HARQ IDs is valid when communicating with multiple TRPs. For example, the UE may receive a downlink message (e.g., DCI) including a DFI for a set of HARQ IDs from at least one TRP. Each HARQ ID in the set of HARQ IDs may be associated with one or more uplink messages sent to a first TRP (e.g., corresponding to a first control resource set (COREST) ​​pool index) or sent to a second TRP (e.g., corresponding to a second CORESET pool index). In some cases, the UE may determine that the DFI associated with the HARQ ID is valid based on the first symbol of the downlink message appearing at a first time threshold after the last symbol of the uplink message associated with the HARQ ID in the set of HARQ IDs. Additionally, the UE may determine that the DFI associated with the HARQ ID is valid based on the CORESET pool index associated with the DFI being the same as the CORESET pool index associated with the uplink message corresponding to the HARQ ID. In other examples, the CORESET pool index associated with the DFI and the CORESET pool index associated with the uplink message may be different, and the UE may determine that the DFI is valid based on the first symbol of the downlink message appearing at a second time threshold after the last symbol of the first uplink message associated with the HARQ ID, wherein the second time threshold is greater than or equal to the first time threshold.

[0035] Various aspects of the disclosure are first described in the context of a wireless communication system. Various aspects of the disclosure are then described in the context of a verification process and process flow, and are further illustrated and described through apparatus diagrams, system diagrams, and flow charts involving techniques for downlink feedback from multiple transmission and reception points.

[0036] Figure 1 An example of a wireless communication system 100 that supports techniques for downlink feedback from multiple transmission and reception points according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating according to other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

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

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

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

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

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

[0042] In some examples, the network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP). One or more components of the network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

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

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

[0045] Where the techniques described herein are applied to the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support the techniques for downlink feedback from multiple transmission and reception points as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0063] The wireless communication system 100 may support DFIs for multiple TRPs. For example, the UE 115 may send one or more uplink messages to at least one TRP in the TRP set, wherein each of the one or more uplink messages is associated with a first CORESET pool index or a second CORESET pool index (e.g., based on which TRP the UE 115 is communicating with). Additionally, each uplink message may be associated with a HARQ identifier in the HARQ identifier set. In some cases, the UE 115 may receive a downlink message (e.g., a PDCCH transmission carrying a DCI) from a TRP in the TRP set indicating a DFI for the HARQ identifier set, wherein the DFI is associated with the first CORESET pool index or the second CORESET pool index. In some examples, the validity of the DFI for a PUSCH with a given HARQ process number (e.g., HARQ ID) may be based on when the uplink message (e.g., PUSCH transmission) is received relative to the first symbol of the downlink message (e.g., DCI) carrying the DFI. For example, for a grant transmission configured for an uplink (e.g., a PUSCH transmission configured by ConfiguredGrantConfig), if the first symbol received by the PDCCH is a certain number of symbols provided by a threshold (e.g., cg-minDFI-Delay) after the last symbol of the PUSCH transmission or any repetition of the PUSCH transmission, then the HARQ-ACK information of the transport block corresponding to the HARQ process number may be valid. In other examples, for an uplink transmission scheduled by a dynamic grant (e.g., a PUSCH transmission scheduled by a certain DCI format), if the first symbol received by the PDCCH is a certain number of symbols provided by a threshold (e.g., cg-minDFI-Delay) after the last symbol of the PUSCH transmission, then the HARQ-ACK information of the transport block corresponding to the HARQ process number may be valid. In the case where the uplink message is sent over multiple time intervals (e.g., the PUSCH is sent over multiple time slots), the HARQ-ACK information of the transport block corresponding to the HARQ process number may be valid if the first symbol received by the PDCCH is a certain number of symbols provided by a threshold (e.g., cg-minDFI-Delay) after the last symbol sent by the PUSCH in the first time slot of the multiple time slots and if the value of the HARQ-ACK information is acknowledgment (ACK).Alternatively, if the first symbol received by the PDCCH is a certain number of symbols provided by a threshold (e.g., cg-minDFI-Delay) after the last symbol sent by the PUSCH in the last time slot of the multiple time slots and if the value of the HARQ-ACK information is a negative acknowledgement (NACK), then the HARQ-ACK information of the transport block corresponding to the HARQ process number can be valid. In addition, as described herein, the UE 115 can determine whether the DFI is valid (e.g., verify the DFI) based on the CORESET pool index associated with the DFI and the CORESET pool index associated with at least one of the one or more uplink messages.

[0064] For example, the UE 115 may determine that the DFI is valid for the first HARQ identifier based on the first symbol of the downlink message appearing at a first time threshold after the last symbol of the first uplink message associated with the first HARQ identifier. In some cases, the first time threshold may be used to identify the most recently transmitted uplink message associated with at least one HARQ identifier in the set of HARQ identifiers. Additionally, the UE 115 may determine that the DFI is valid based on the CORESET pool index associated with the DFI being the same as the CORESET pool index associated with the first uplink message. In some examples, the UE 115 may determine that the DFI is valid based on the first symbol of the downlink message appearing at a second time threshold after the last symbol of the first uplink message associated with the first HARQ identifier, wherein the CORESET pool index associated with the DFI is different from the CORESET pool index associated with the first uplink message.

[0065] Figure 2 An example of a wireless communication system 200 that supports techniques for downlink feedback from multiple TRPs in accordance with one or more aspects of the present disclosure is illustrated. In some examples, the wireless communication system 200 may implement aspects of the wireless communication system 100 or may be implemented by these aspects. For example, the wireless communication system 200 may be implemented by one or more network entities 205 (e.g., network entity 205-a and network entity 205-b) and one or more UEs 215, which may be as described herein. Figure 1 Examples of the corresponding devices described. Figure 2 In the example of FIG. 1 , the network entity 205 - a and / or the network entity 205 - b may be a CU 160, a DU 165, a RU 170, a base station 140, an IAB node 104, or a Figure 1In some aspects, the network entity 205-a may send the DFI 235 to the UE 215 via the communication link 210-a, and the UE 215 may determine whether the DFI is valid for one or more HARQ IDs based on one or more rules.

[0066] The wireless communication system 200 may support multi-TRP communications. For example, the UE 215 may communicate with multiple TRPs in the uplink and downlink. Figure 2 In the illustrated example, different TRPs are shown as corresponding network entities 205, but a single network entity 205 may have two or more TRPs, and the examples described herein should not be considered as limitations on the claims or the present disclosure. That is, each network entity 205 may be associated with one or more TRPs.

[0067] In some aspects, multiple DCIs may be sent to UE 215, where each TRP may send a corresponding DCI. For example, UE 215 may receive a first DCI from a first network entity (e.g., network entity 205-a), and the DCI may schedule one or more downlink messages (e.g., physical downlink shared channel (PDSCH) transmission) or one or more uplink messages (e.g., physical uplink shared channel (PUSCH) transmission). UE 215 may also receive a second DCI from a second network entity (e.g., network entity 205-b), the second DCI scheduling one or more downlink messages or one or more uplink messages. In some cases, the corresponding communication with each TRP may be associated with a different CORESET pool index value. For example, UE 215 may receive a control message that configures UE 215 for multi-TRP communication (e.g., in a given component carrier based on PDCCH-Config, including two different values ​​of CORESETPoolIndex in a CORESET that contains an active BWP for a serving cell). That is, each TRP may be associated with a corresponding CORESET pool index 220 (e.g., CORESET pool index 220-a, CORESET pool index 220-b) having a certain value (e.g., 0 or 1). Each CORESET pool index 220 may be associated with one or more CORESET IDs corresponding to the corresponding CORESET. Additionally, the UE 215 may distinguish between TRPs (e.g., network entity 205-a and network entity 205-b) based on the corresponding CORESET pool index.

[0068] In some cases, the UE 215 may use a CORESET pool index of a CORESET where the UE 215 receives a control message (e.g., DCI) for sending feedback (e.g., HARQ acknowledgement (HARQ-ACK)). For example, the UE 215 may be configured to send joint or separate feedback in response to a downlink message (e.g., HARQ-ACK for a physical downlink control channel (PDCCH). In some scenarios (e.g., ideal backhaul between the first network entity 205 and the second network entity), the UE 215 may be configured to send joint feedback on uplink resources (e.g., physical uplink control channel (PUCCH) resources) (e.g., via ackNackFeedbackMode=joint). In some other cases (e.g., ideal backhaul or non-ideal backhaul between the first network entity 205 and the second network entity), the UE 215 may be configured to send separate feedback on uplink resources (e.g., via ackNackFeedbackMode=separate). That is, the UE 215 may send separate feedback for downlink messages associated with the first CORESET pool index and for downlink messages associated with the second CORESET pool index. The uplink resources containing feedback for different CORESET pool indexes may be included in the same time slot (e.g., but not overlapping). For example, the UE 215 may time division multiplex (TDM) feedback for downlink messages associated with the first CORESET pool index 220 with feedback for downlink messages associated with the second CORESET pool index 220 (e.g., two PUCCHs may be sent simultaneously).

[0069] Additionally or alternatively, the UE 215 may receive a downlink message (e.g., DCI) from the network entity 205 indicating a DFI (e.g., PUSCH HARQ-ACK) based on one or more uplink messages (e.g., PUSCH transmissions). The UE 215 may receive an indication of whether the network entity 205 has received (e.g., correctly decoded) an uplink message based on the DFI. In some cases, the uplink message may be associated with a dynamic grant (e.g., based on scheduling information included in the DCI) or associated with a configured grant (CG) (e.g., CG-PUSCH) such that resources associated with the CG can support retransmissions. Additionally, the UE 215 may select a HARQ ID, a new data indicator (NDI) (e.g., the NDI may be switched for new transmissions but not for retransmissions), and a redundancy version (RV) for each CG opportunity. In some cases, the network entity 205 may receive an uplink message associated with the CG and may decode the uplink message based on uplink control information (UCI) associated with the CG and multiplexed with the uplink message. That is, the network entity 205 may decode the UCI and then decode the uplink message (e.g., uplink data on the CG-PUSCH). The UCI may include HARQ ID, RV, NDI, and channel occupancy time (COT) sharing information (e.g., related to unlicensed operation). In some cases, the UE 215 may encode the UCI independently of the uplink message.

[0070] In some cases, the network entity 205 may send a downlink message (e.g., DCI) including the DFI, which may indicate feedback information (e.g., HARQ-ACK) for each HARQ ID associated with a previous uplink message (e.g., one or more previous PUSCH transmissions corresponding to a CG-PUSCH or a dynamically granted PUSCH). In some examples, the downlink message may include a tag associated with the DFI (e.g., a DFI tag may be added to a DCI format 0_1 ​​having a CRC scrambled by a configured scheduling radio network temporary identifier (CS-RNTI)). For example, the tag may indicate a value of 0, which may indicate that the DFI is not included in the downlink message (e.g., the DCI may be a normal uplink DCI and may activate the CG-PUSCH). For another example, the tag may indicate a value of 1, which may further indicate that the DFI is included in the downlink message (e.g., 16 bits indicate a HARQ-ACK for each HARQ ID transmitted for a previous PUSCH).

[0071] In some cases (e.g., non-ideal backhaul), the network entity 205 may send a separate DFI (e.g., in a multi-DCI based uplink operation). For example, the DFI may include confirmation feedback (e.g., HARQ-ACK) for a set of HARQ IDs (e.g., 16 HARQ IDs). The first network entity 205 (e.g., network entity 205-a) may send a DFI for the set of HARQ IDs, however, a subset of HARQ IDs from the set of HARQ IDs may be associated with one or more uplink messages sent to the second network entity 205 (e.g., network entity 205-b), and the first network entity 205 may not know whether the one or more uplink messages sent to the second network entity 205 are successfully received and / or decoded. That is, before the first network entity 205 sends a downlink message containing the DFI (e.g., a 16-bit HARQ-ACK bitmap in one DCI), the second network entity 205 may not (e.g., may not be able to) communicate the DFI of the one or more messages associated with the HARQ ID subset to the second network entity 205. Therefore, it may be difficult for the UE 215 to determine whether the DFI for the HARQ ID subset associated with the one or more uplink messages in the DFI (e.g., a joint DFI) is valid. In addition, each HARQ ID may be used by any network entity 205 in different scheduling instances, so that (e.g., from the perspective of the UE 215) there may not be a semi-static split between HARQ IDs. Therefore, techniques for verifying the DFI may be needed.

[0072] Techniques described herein may enable a UE 215 to determine that a DFI 235 for a HARQ ID in a set of HARQ IDs is valid based on a CORESET pool index associated with a DFI 235 and a CORESET pool index associated with at least one uplink message sent by the UE 215 to one or more TRPs in a set of TRPs, such as a network entity 205-a or a network entity 205-b. For example, the UE 215 may send an uplink message 230-a associated with a first HARQ ID to the network entity 205-a via a communication link 210-a and send an uplink message 230-b associated with a second HARQ ID to the network entity 205-b via a communication link 210-b. In some cases, a TRP corresponding to the network entity 205-a may be associated with a CORESET pool index 220-a, which may be further associated with a CORESET ID 225-a and a CORESET ID 225-b. Similarly, the TRP corresponding to the network entity 205-b may be associated with a CORESET pool index 220-b, which is further associated with a CORESET ID 225-c and a CORESET ID 225-d. In some cases, the CORESET pool index 220-a may be different from the CORESET pool index 220-a. Additionally, the CORESET ID 225 may be unique. In some cases, the network entity 205-a may send a DFI 235 for the first HARQ ID and the second HARQ ID to the UE 215 (e.g., via a DCI). The UE 215 may verify the DFI 235 associated with the first HARQ ID and the second HARQ ID based on the CORESET pool index 220 associated with the DFI 235 and the CORESET pool index 220 associated with at least one of the uplink message 230-a or the uplink message 230-b.

[0073] For example, the UE 215 may determine whether the DFI 235 is valid for the first HARQ ID based on the first symbol of the downlink message carrying the DFI 235 appearing at a first time threshold after the last symbol of the uplink message 230-a associated with the first HARQ ID. In addition, the UE 215 may determine whether the DFI 235 is valid for the first HARQ ID based on the CORESET pool index associated with the DFI 235 being the same as the CORESET pool index associated with the uplink message 230-a, as described in reference to Figure 3A described.

[0074] For another example, the UE 215 may determine that the DFI 235 is valid for the second HARQ ID based on the first symbol of the downlink message carrying the DFI 235 appearing at the first time threshold after the last symbol of the uplink message 230-b associated with the second HARQ ID. In addition, the UE 215 may determine that the DFI 235 is valid for the second HARQ ID based on the first symbol of the downlink message carrying the DFI 235 appearing at the second time threshold after the last symbol of the uplink message 230-b associated with the second HARQ ID, wherein the CORESET pool index associated with the DFI 235 is different from the CORESET pool index associated with the uplink message 230-b, as shown in reference Figure 3B described.

[0075] Figure 3A and Figure 3B An example of a verification process 300 (e.g., verification process 300-a, verification process 300-b) supporting techniques for downlink feedback from multiple TRPs according to one or more aspects of the present disclosure is illustrated. In some examples, the verification process 300 may implement or be implemented by aspects of the wireless communication system 100 and the wireless communication system 200. For example, the verification process 300 may be implemented by one or more network entities 105 and one or more UEs 115, which may be as described herein with reference to Figure 1 An example of the corresponding device. The verification process 300 may support verification of a DFI for one or more HARQ IDs, each of which is associated with an uplink message sent by the UE to multiple TRPs.

[0076] In some cases, in the examples of verification process 300-a and verification process 300-b, the UE may be configured with multiple (e.g., two) CORESET pool index 305 values, such as CORESET pool index 305-a and CORESET pool index 305-b (e.g., in component carriers). In some cases, each CORESET pool index 305 may be associated with a different TRP (e.g., corresponding to one or more network entities 105), such as a first TRP and a second TRP. Additionally, the UE may verify the DFI 310 received via a downlink message 315 (e.g., downlink message 315-a, downlink message 315-b) from the first TRP, the second TRP, or both (e.g., separateDFI is RRC configured) (e.g., the UE may determine whether any part of the DFI is valid).

[0077] In some cases, according to the verification process 300-a, the UE may send one or more uplink messages 320, wherein each uplink message 320 is associated with a HARQ ID 325 (e.g., HARQ ID 325-a, HARQ ID 325-b, HARQ ID 325-c, etc.) in the set of HARQ IDs 325. For example, the UE may send an uplink message 320-a associated with HARQ ID 325-a and an uplink message 320-d associated with HARQ ID 325-a to the first TRP associated with the CORESET pool index 305-a. Additionally, the UE may send an uplink message 320-b associated with HARQ ID 325-b and an uplink message 320-c associated with HARQ ID 325-c to the second TRP associated with the CORESET pool index 305-b.

[0078] In some cases, the UE may receive a downlink message 315-a (e.g., a DCI format 0_1 ​​with a CRC scrambled by the CS-RNTI) indicating a DFI 310-a for a set of HARQ IDs 325 (e.g., a DFI flag in the DCI is set to 1) . Additionally, the UE may determine a CORESET pool index 305 associated with the DFI 310-a. In some cases, the CORESET pool index 305 associated with the DFI 310-a may be based on the CORESET pool index 305 in which the downlink message 315-a is received. For example, the UE may receive the downlink message 315-a in the CORESET pool index 305-a, and therefore, the DFI 310-a may be associated with the CORESET pool index 305-a. In some other cases, the downlink message 315 - a may include a field indicating the CORESET pool index 305 associated with the DFI 310 - a .

[0079] In some cases, the UE may determine the most recently transmitted uplink message 320 whose last symbol is at least a delay 330-a before the first symbol of the downlink message 315-a (e.g., for each HARQ ID 325). The delay 330-a may be a certain number of symbols. Additionally, the UE may determine a CORESET pool index 305 associated with each uplink message 320. In some cases (e.g., DG-PUSCH or CG-PUSCH), the CORESET pool index 305 associated with each uplink message 320 may be based on a control message that schedules the uplink message 320. For example, the UE may receive a control message that schedules the uplink message 320-a in the CORESET associated with the CORESET pool index 305-a, and therefore, the uplink message 320-a may be associated with the CORESET pool index 305-a. In some other cases (e.g., CG-PUSCH), the CORESET pool index 305 associated with each uplink message 320 may be based on a CG configuration (e.g., RRC configured). For example, the uplink message 320-b may be associated with a CG configuration indicating the CORESET pool index 305-b, and thus, the uplink message 320-b may be associated with the CORESET pool index 305-b. In some other cases (e.g., CG-PUSCH), the CORESET pool index 305 associated with each uplink message 320 may be based on a control message (e.g., DCI) activating the CG configuration. For example, the UE may receive a control message via the CORESET associated with the CORESET pool index 305-b, wherein the control message activates the CG configuration associated with the uplink message 320-c. Thus, the uplink message 320-c may be associated with the CORESET pool index 305-b. Alternatively, each HARQ ID 325 may be associated with a CORESET pool index 305 (e.g., directly) (e.g., semi-statically split between the HARQ IDs 325 across two TRPs). For example, HARQ ID 325-d may be associated with CORESET pool index 305-a, such that uplink message 320-d is associated with CORESET pool index 305-a.

[0080] In some cases, the UE may determine whether the DFI 310-a for the HARQ ID 325 is valid based on the last symbol of the corresponding uplink message 320 being at least a threshold or delay 330-a (e.g., cg-minDFI-delay) before the first symbol of the downlink message 315-a. Additionally, the UE may determine that the DFI 310-a for the HARQ ID 325 is valid based on the CORESET pool index 305 associated with the corresponding uplink message 320 and the CORESET pool index 305 associated with the DFI 310-a being the same. For example, the UE may determine that DFI 310-a is associated with HARQ ID 325-a and that HARQ ID 325-d is valid based on the last symbol of uplink message 320-a and uplink message 320-d being at least delay 330-a before the first symbol of downlink message 315-a and based on the uplink message 320-a and uplink message 320-d being associated with CORESET pool index 305-a. Conversely, the UE may determine that DFI 310-a is associated with HARQ ID 325-b and that HARQ ID 325-c is invalid based on the uplink message 320-b and uplink message 320-c being associated with CORESET pool index 305-b (e.g., even if the last symbol of uplink message 320-b and uplink message 320-c is at least delay 330-a before the first symbol of downlink message 315-a).

[0081] In some examples, an uplink message 320 (e.g., a PUSCH repetition) associated with a CORESET pool index 305 (which is the same as the CORESET pool index 305 associated with DFI 310-a) may occur over multiple time slots such that DFI 310-a may be valid for HARQ ID 325 based on the last symbol of the uplink message 320 in the first of the multiple time slots reaching delay 330-a (e.g., if DFI 310-a for HARQ ID 325 is ACK). Similarly, an uplink message 320 associated with a CORESET pool index 305 (which is the same as the CORESET pool index 305 associated with DFI 310-a) may appear over multiple time slots such that DFI 310-a may be valid for HARQ ID 325 based on the last symbol of the uplink message 320 in the last time slot of the multiple time slots reaching delay 330-c (e.g., if DFI 310-a for HARQ ID 325 is NACK).

[0082] Additionally or alternatively, according to the verification process 300-b, the UE may send an uplink message 320-e associated with the HARQ ID 325-e and an uplink message 320-h associated with the HARQ ID 325-h to the first TRP associated with the CORESET pool index 305-a. Additionally, the UE may send an uplink message 320-f associated with the HARQ ID 325-g and an uplink message 320-c associated with the HARQ ID 325-g to the second TRP associated with the CORESET pool index 305-b.

[0083] In some cases, the UE may receive a downlink message 315-b indicating a DFI 310-b for a set of HARQ IDs 325, including HARQ ID 325-e, HARQ ID 325-f, HARQ ID 325-g, and HARQ ID 325-h. Additionally, the UE may determine a CORESET pool index 305 associated with the DFI 310-b, as described with reference to the verification process 300-a. For example, the UE may determine that the DFI 310-b is associated with the CORESET pool index 305-a.

[0084] In some cases, the UE may determine the most recently transmitted uplink message 320 whose last symbol is at least a delay 330-b before the first symbol of a downlink message 315-b (e.g., for each HARQ ID 325). Additionally, the UE may determine the CORESET pool index 305 associated with each uplink message 320, as described with reference to the verification process 300-a. For example, the UE may determine that uplink message 320-e is associated with CORESET pool index 305-a, uplink message 320-f is associated with CORESET pool index 305-b, uplink message 320-g is associated with CORESET pool index 305-b, and uplink message 320-h is associated with CORESET pool index 305-a.

[0085] In some cases, the UE may determine that the DFI 310-b for the HARQ ID 325 is valid based on the last symbol of the corresponding uplink message 320 being at least a delay 330-b before the first symbol of the downlink message 315-b. Additionally, the UE may determine whether the DFI 310-b for the HARQ ID 325 is valid based on the CORESET pool index 305 associated with the corresponding uplink message 320 and the CORESET pool index 305 associated with the DFI 310-b being the same. For example, the UE may determine that DFI 310-b is associated with HARQ ID 325-e and that HARQ ID 325-h is valid based on the last symbol of uplink message 320-e and uplink message 320-h being at least a delay 330-b before the first symbol of downlink message 315-a and based on the uplink message 320-e and uplink message 320-h being associated with CORESET pool index 305-a.

[0086] Additionally, the UE may determine whether the DFI 310-b for the HARQ ID 325 is valid (e.g., without regard to the CORESET pool index 305) based on the last symbol of the corresponding uplink message 320 being at least a delay 330-c (e.g., cg-minDFI-Delay-second-threshold) before the first symbol of the downlink message 315-b. In some cases, the delay 330-c may be greater than or equal to (e.g., in the case of ideal backhaul) the delay 330-b (e.g., RRC configured). For example, the UE may determine that the DFI 310-b for the HARQ ID 325-f is valid based on the last symbol of the uplink message 320-f being at least a delay 330-b and at least a delay 330-c before the first symbol of the downlink message 315-b. Conversely, the UE may determine that the DFI 310-b for the HARQ ID 325-g is valid based on the last symbol of the uplink message 320-g being within a delay 330-c before the first symbol of the downlink message 315-b (e.g., even if the last symbol of the uplink message 320-g is at least a delay 330-b before the first symbol of the downlink message 315-b).

[0087] In some examples, the uplink message 320 (e.g., an uplink transmission) may occur over multiple time slots such that based on the last symbol of the uplink message 320 in the first time slot of the multiple time slots reaching the delay 330-c (e.g., if the DFI 310-b for the HARQ ID 325 is an ACK), the DFI 310-b may be valid for the HARQ ID 325. Similarly, the uplink message 320 (e.g., an uplink transmission) may occur over multiple time slots such that based on the last symbol of the uplink message 320 in the last time slot of the multiple time slots reaching the delay 330-c (e.g., if the DFI 310-b for the HARQ ID 325 is a NACK), the DFI 310-b may be valid for the HARQ ID 325.

[0088] Figure 4 An example of a process flow 400 in a system supporting techniques for downlink feedback from multiple TRPs in accordance with one or more aspects of the present disclosure is illustrated. In some examples, the process flow 400 may implement or be implemented by aspects of the wireless communication system 100, the wireless communication system 200, and the verification process 300. For example, the process flow 400 may be implemented by one or more network entities 405 (e.g., network entity 405-a and network entity 405-b) and one or more UEs 415 (e.g., UE 415), which may be described herein with reference to Figure 1 Examples of the corresponding devices described. Figure 2 In the example of FIG. 1 , the network entity 405 may be a CU 160, a DU 165, a RU 170, a base station 140, an IAB node 104, or a Figure 1 Examples of the one or more other network nodes.

[0089] In some cases, at 420, UE 415 may receive one or more control messages from network entity 405-a, network entity 405-b, or both, the one or more control messages instructing each TRP in the set of TRPs (e.g., corresponding to one or more of network entity 405-a or network entity 405-b) to send a respective DFI. In some cases, the first CORESET pool index value may be associated with the TRP of network entity 405-a, and the second CORESET pool index value may be associated with the TRP of network entity 405-b.

[0090] In some cases, the one or more control messages may indicate one or more CG configurations associated with one or more uplink messages to be sent by the UE 415, wherein each of the one or more configured authorization configurations indicates the first CORESET pool index value or the second CORESET pool index value, and wherein the CORESET pool index value associated with each of the one or more uplink messages to be sent by the UE 415 is based at least in part on the one or more CG configurations. In some cases, a respective DCI activating each of the one or more CG configurations is received via a respective CORESET associated with the first CORESET pool index value or the second CORESET pool index value, and wherein the CORESET pool index value associated with each of the one or more uplink messages is based at least in part on the first CORESET pool index value or the second CORESET pool index value associated with the respective CORESET for receiving the DCI.

[0091] At 425, UE 415 may send the one or more uplink messages to at least one TRP in the TRP set, wherein each of the one or more uplink messages is associated with the first CORESET pool index value or the second CORESET pool index value. That is, UE 415 may send the one or more uplink messages to network entity 405-a, network entity 405-b, or both. Additionally, each uplink message may be associated with a HARQ ID in the HARQ ID set.

[0092] At 430, the UE 415 may receive a downlink message indicating a DFI for the HARQ ID set from a TRP in the set of TRPs (e.g., corresponding to the network entity 405-a), wherein the DFI is associated with the first CORESET pool index value or the second CORESET pool index value. In some cases, the UE 415 may receive the DFI via a CORESET associated with the first CORESET pool index or the second CORESET pool index. In some cases, the CORESET pool index value associated with the DFI corresponds to the first CORESET pool index or the second CORESET pool index used to receive the downlink message. In some other cases, the UE 415 may receive an indication of the CORESET pool index value with the DFI within the downlink message.

[0093] In some cases, at 435, the UE 415 may identify a most recently transmitted uplink message among the one or more uplink messages for each HARQ ID in the HARQ ID set based at least in part on a first symbol of the downlink message appearing at a first time threshold after a last symbol of each most recently transmitted first uplink message, identifying the most recently transmitted uplink message for each HARQ ID.

[0094] In some cases, at 440, the UE 415 may determine a CORESET pool index value associated with at least one of the one or more uplink messages based on a CORESET pool index value associated with a corresponding control message that schedules the at least one uplink message, wherein the CORESET pool index value associated with the corresponding control message is based at least in part on the CORESET used to receive the corresponding control message. In some other cases, the CORESET pool index value associated with each of the one or more uplink messages may be based at least in part on a corresponding HARQ ID in the set of HARQ IDs associated with each uplink message, wherein each HARQ ID corresponds to the first CORESET pool index value or the second CORESET pool index value.

[0095] At 445, the UE 415 may determine that the DFI is valid for at least one HARQ ID in the set of HARQ IDs based on the CORESET pool index value associated with the DFI and the CORESET pool index value associated with the at least one uplink message in the one or more uplink messages. In some cases, the UE 415 may determine that the DFI is valid for the first HARQ ID in the set of HARQ IDs based on the first symbol of the downlink message occurring at the first time threshold after the last symbol of the first uplink message associated with the first HARQ ID, wherein the first time threshold is used to identify the most recently transmitted uplink message associated with at least one HARQ ID in the set of HARQ IDs. In some cases, the UE 415 may determine whether the DFI is valid based on the control message from the network entity 405-a, the network entity 405-b, or both.

[0096] Additionally, the UE 415 may determine that the DFI for the first HARQ ID in the set of HARQ IDs is valid based on the CORESET pool index value associated with the DFI and the CORESET pool index value associated with the first uplink message being the same.

[0097] Additionally or alternatively, the UE 415 may determine that the DFI for the first HARQ ID in the set of HARQ IDs is valid based on the first symbol of the downlink message occurring at a second time threshold after the last symbol of the first uplink message associated with the first HARQ ID, wherein the CORESET pool index value associated with the DFI is different from the CORESET pool index value associated with the first uplink message. In some cases, the UE 415 may receive control signaling indicating the second time threshold. The second time threshold may be greater than or equal to the first time threshold, and the first time threshold is used to identify the most recently transmitted uplink message associated with the at least one HARQ ID in the set of HARQ IDs.

[0098] Figure 5 A block diagram 500 of a device 505 supporting techniques for downlink feedback from multiple TRPs according to one or more aspects of the present disclosure is shown. The device 505 may be an example of aspects of a UE 115 as described herein. The device 505 may include a receiver 510, a transmitter 515, and a communication manager 520. The device 505 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0099] The receiver 510 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels related to techniques for downlink feedback from multiple TRPs, data channels, information channels). The information may be passed to other components of the device 505. The receiver 510 may utilize a single antenna or a collection of multiple antennas.

[0100] The transmitter 515 may provide means for transmitting signals generated by other components of the device 505. For example, the transmitter 515 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to techniques for downlink feedback from multiple TRPs). In some examples, the transmitter 515 may be co-located with the receiver 510 in a transceiver component. The transmitter 515 may utilize a single antenna or a collection of multiple antennas.

[0101] The communication manager 520, the receiver 510, the transmitter 515, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of the techniques for downlink feedback from multiple TRPs as described herein. For example, the communication manager 520, the receiver 510, the transmitter 515, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

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

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

[0104] In some examples, communication manager 520 may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 510, transmitter 515, or both. For example, communication manager 520 may receive information from receiver 510, transmit information to transmitter 515, or be integrated in conjunction with receiver 510, transmitter 515, or both to obtain information, output information, or perform various other operations as described herein.

[0105] According to an example as disclosed herein, the communication manager 520 may support wireless communication at a UE. For example, the communication manager 520 may be configured to or otherwise support a component for sending one or more uplink messages to at least one TRP in a set of multiple TRPs, wherein each of the one or more uplink messages is associated with a first CORESET pool index value or a second CORESET pool index value, and wherein each uplink message is associated with a HARQ ID in a set of HARQ IDs. The communication manager 520 may be configured to or otherwise support a component for receiving a downlink message indicating a DFI for the set of HARQ IDs from a TRP in the set of multiple TRPs, wherein the DFI is associated with the first CORESET pool index value or the second CORESET pool index value, and wherein based on the CORESET pool index value associated with the DFI and the CORESET pool index value associated with at least one of the one or more uplink messages, the DFI is valid for at least one HARQ ID in the set of HARQ IDs.

[0106] By including or configuring the communication manager 520 according to the examples described herein, the device 505 (e.g., a processor controlling or otherwise coupled to the receiver 510, the transmitter 515, the communication manager 520, or a combination thereof) may support techniques for validating downlink feedback from multiple TRPs, which may result in reduced processing, reduced power consumption, and more efficient utilization of communication resources, among other advantages.

[0107] Figure 6 A block diagram 600 of a device 605 supporting techniques for downlink feedback from multiple TRPs according to one or more aspects of the present disclosure is shown. The device 605 may be an example of aspects of the device 505 or UE 115 as described herein. The device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. The device 605 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0108] The receiver 610 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels related to techniques for downlink feedback from multiple TRPs, data channels, information channels). The information may be passed to other components of the device 605. The receiver 610 may utilize a single antenna or a collection of multiple antennas.

[0109] The transmitter 615 may provide means for transmitting signals generated by other components of the device 605. For example, the transmitter 615 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to techniques for downlink feedback from multiple TRPs). In some examples, the transmitter 615 may be co-located with the receiver 610 in a transceiver component. The transmitter 615 may utilize a single antenna or a collection of multiple antennas.

[0110] Device 605 or its various components may be examples of components for performing various aspects of the technology for downlink feedback from multiple TRPs as described herein. For example, communication manager 620 may include HARQ component 625, verification component 630, or any combination thereof. Communication manager 620 may be an example of various aspects of communication manager 520 as described herein. In some examples, communication manager 620 or its various components may be configured to use or otherwise cooperate with receiver 610, transmitter 615, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, communication manager 620 may receive information from receiver 610, transmit information to transmitter 615, or be integrated in combination with receiver 610, transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.

[0111] According to an example as disclosed herein, the communication manager 620 may support wireless communication at a UE. The HARQ component 625 may be configured to or otherwise support components for sending one or more uplink messages to at least one TRP in a set of multiple TRPs, wherein each of the one or more uplink messages is associated with a first CORESET pool index value or a second CORESET pool index value, and wherein each uplink message is associated with a HARQ ID in a set of HARQ IDs. The verification component 630 may be configured to or otherwise support components for receiving a downlink message indicating a DFI for the set of HARQ IDs from a TRP in the set of multiple TRPs, wherein the DFI is associated with the first CORESET pool index value or the second CORESET pool index value, and wherein based on the CORESET pool index value associated with the DFI and the CORESET pool index value associated with at least one of the one or more uplink messages, the DFI is valid for at least one HARQ ID in the set of HARQ IDs.

[0112] Figure 7A block diagram 700 of a communication manager 720 supporting techniques for downlink feedback from multiple TRPs in accordance with one or more aspects of the present disclosure is shown. The communication manager 720 may be an example of aspects of the communication manager 520, the communication manager 620, or both as described herein. The communication manager 720 or its various components may be examples of components for performing various aspects of the techniques for downlink feedback from multiple TRPs as described herein. For example, the communication manager 720 may include a HARQ component 725, a verification component 730, a timing verification component 735, an index verification component 740, a configuration component 745, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0113] According to an example as disclosed herein, the communication manager 720 may support wireless communication at a UE. The HARQ component 725 may be configured to or otherwise support a component for sending one or more uplink messages to at least one TRP in a set of multiple TRPs, wherein each of the one or more uplink messages is associated with a first CORESET pool index value or a second CORESET pool index value, and wherein each uplink message is associated with a HARQ ID in a set of HARQ IDs. The verification component 730 may be configured to or otherwise support a component for receiving a downlink message indicating a DFI for the set of HARQ IDs from a TRP in the set of multiple TRPs, wherein the DFI is associated with the first CORESET pool index value or the second CORESET pool index value, and wherein based on the CORESET pool index value associated with the DFI and the CORESET pool index value associated with at least one of the one or more uplink messages, the DFI is valid for at least one HARQ ID in the set of HARQ IDs.

[0114] In some examples, the timing verification component 735 may be configured to or otherwise support components for determining that the DFI is valid for a first HARQ ID based on the first symbol of the downlink message appearing at a first time threshold after the last symbol of a first uplink message associated with a first HARQ ID in the HARQ ID set, wherein the first time threshold is used to identify a most recently transmitted uplink message associated with at least one HARQ ID in the HARQ ID set.

[0115] In some examples, the index verification component 740 may be configured to or otherwise support components for determining that the DFI for the first HARQ ID in the HARQ ID set is valid based on the CORESET pool index value associated with the DFI and the CORESET pool index value associated with the first uplink message being the same.

[0116] In some examples, the timing verification component 735 may be configured to or otherwise support components for determining that the DFI for the first HARQ ID in the HARQ ID set is valid based on the first symbol of the downlink message appearing at a second time threshold after the last symbol of the first uplink message associated with the first HARQ ID, wherein the CORESET pool index value associated with the DFI is different from the CORESET pool index value associated with the first uplink message.

[0117] In some examples, timing verification component 735 can be configured or otherwise support means for receiving control signaling indicating the second time threshold.

[0118] In some examples, the second time threshold is greater than or equal to the first time threshold, and the first time threshold is used to identify the most recently sent uplink message associated with the at least one HARQ ID in the HARQ ID set.

[0119] In some examples, the verification component 730 may be configured or otherwise support a component for receiving a control message instructing each TRP in the set of multiple TRPs to send a corresponding DFI. In some examples, the verification component 730 may be configured or otherwise support a component for determining whether the DFI is valid based on the control message.

[0120] In some examples, to support receiving the downlink message, the index verification component 740 may be configured to or otherwise support components for receiving the downlink message via a CORESET associated with the first CORESET pool index value or the second CORESET pool index value, wherein the CORESET pool index value associated with the DFI corresponds to the first CORESET pool index value or the second CORESET pool index value associated with the CORESET used to receive the downlink message.

[0121] In some examples, index verification component 740 may be configured or otherwise support means for receiving an indication of the CORESET pool index value associated with the DFI within the downlink message.

[0122] In some examples, the timing verification component 735 may be configured to or otherwise support a component for identifying a most recently transmitted uplink message of the one or more uplink messages for each HARQ ID in the set of HARQ IDs, identifying the most recently transmitted uplink message for each HARQ ID based on the first symbol of the downlink message appearing at a time threshold after the last symbol of each most recently transmitted first uplink message. In some examples, the timing verification component 735 may be configured to or otherwise support a component for determining whether the DFI is valid based on the most recently transmitted uplink message for each HARQ ID.

[0123] In some examples, the index verification component 740 may be configured to or otherwise support components for determining the CORESET pool index value associated with the at least one uplink message based on a CORESET pool index value associated with a corresponding control message that schedules the at least one uplink message, wherein the CORESET pool index value associated with the corresponding control message is based on the CORESET used to receive the corresponding control message.

[0124] In some examples, configuration component 745 may be configured to or otherwise support components for receiving one or more control messages indicating one or more configured authorization configurations associated with the one or more uplink messages, wherein each of the one or more configured authorization configurations indicates the first CORESET pool index value or the second CORESET pool index value, and wherein the CORESET pool index value associated with each of the one or more uplink messages is based on the one or more configured authorization configurations.

[0125] In some examples, configuration component 745 may be configured as or otherwise support means for receiving one or more control messages indicating one or more configured authorization configurations associated with the one or more uplink messages, wherein corresponding downlink control information activating each of the one or more configured authorization configurations is received via a corresponding CORESET associated with the first CORESET pool index value or the second CORESET pool index value, and wherein the CORESET pool index value associated with each of the one or more uplink messages is based on the first CORESET pool index value or the second CORESET pool index value associated with the corresponding CORESET used to receive the corresponding downlink control information.

[0126] In some examples, the CORESET pool index value associated with each of the one or more uplink messages is based on a corresponding HARQ ID in the HARQ ID set associated with each uplink message. In some examples, each HARQ ID corresponds to the first CORESET pool index value or the second CORESET pool index value.

[0127] In some examples, the first CORESET pool index value is associated with a first TRP in the set of multiple TRPs, and the second CORESET pool index value is associated with a second TRP in the set of multiple TRPs.

[0128] Figure 8 A diagram of a system 800 including a device 805 supporting techniques for downlink feedback from multiple TRPs according to one or more aspects of the present disclosure is shown. The device 805 may be an example of a device 505, a device 605, or a UE 115 as described herein or include components thereof. The device 805 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 805 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 820, an input / output (I / O) controller 810, a transceiver 815, an antenna 825, a memory 830, a code 835, and a processor 840. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 845).

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

[0130] In some cases, the device 805 may include a single antenna 825. However, in some other cases, the device 805 may have more than one antenna 825, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 815 may communicate bidirectionally via one or more antennas 825, wired or wireless links, as described herein. For example, the transceiver 815 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 815 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 825 for transmission; and demodulating packets received from one or more antennas 825. The transceiver 815 or the transceiver 815 and one or more antennas 825 may be examples of transmitters 515, transmitters 615, receivers 510, receivers 610, or any combination thereof or components thereof as described herein.

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

[0132] The processor 840 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 840 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 840. The processor 840 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 830) to cause the device 805 to perform various functions (e.g., functions or tasks that support technology for downlink feedback from multiple TRPs). For example, the device 805 or a component of the device 805 may include a processor 840 and a memory 830 coupled to or coupled to the processor 840, and the processor 840 and the memory 830 are configured to perform the various functions described herein.

[0133] According to an example as disclosed herein, the communication manager 820 may support wireless communication at a UE. For example, the communication manager 820 may be configured to or otherwise support a component for sending one or more uplink messages to at least one TRP in a set of multiple TRPs, wherein each of the one or more uplink messages is associated with a first CORESET pool index value or a second CORESET pool index value, and wherein each uplink message is associated with a HARQ ID in a set of HARQ IDs. The communication manager 820 may be configured to or otherwise support a component for receiving a downlink message indicating a DFI for the set of HARQ IDs from a TRP in the set of multiple TRPs, wherein the DFI is associated with the first CORESET pool index value or the second CORESET pool index value, and wherein based on the CORESET pool index value associated with the DFI and the CORESET pool index value associated with at least one of the one or more uplink messages, the DFI is valid for at least one HARQ ID in the set of HARQ IDs.

[0134] By including or configuring the communications manager 820 according to the examples described herein, the device 805 may support techniques for verifying downlink feedback from multiple TRPs, which may result in improved communications reliability, reduced latency, an improved user experience associated with reduced processing, reduced power consumption, more efficient use of communications resources, improved coordination between devices, longer battery life, and improved use of processing power, among other advantages.

[0135] In some examples, the communication manager 820 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 815, one or more antennas 825, or any combination thereof. Although the communication manager 820 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 820 may be supported or performed by the processor 840, the memory 830, the code 835, or any combination thereof. For example, the code 835 may include instructions executable by the processor 840 to cause the device 805 to perform various aspects of the techniques for downlink feedback from multiple TRPs as described herein, or the processor 840 and the memory 830 may be otherwise configured to perform or support such operations.

[0136] Fig. 9 A flow chart illustrating a method 900 for supporting techniques for downlink feedback from multiple TRPs according to one or more aspects of the present disclosure is shown. The operations of the method 900 may be implemented by a UE or components thereof as described herein. For example, the operations of the method 900 may be implemented by a UE or components thereof as described herein. Figures 1 to 8The UE 115 described herein may be executed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0137] At 905, the method may include: sending one or more uplink messages to at least one TRP in the set of multiple TRPs, wherein each of the one or more uplink messages is associated with a first CORESET pool index value or a second CORESET pool index value, and wherein each uplink message is associated with a HARQ ID in the set of HARQ IDs. The operations of 905 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 905 may be performed as described in reference to Figure 7 The HARQ component 725 is used to perform.

[0138] At 910, the method may include: receiving a downlink message from a TRP in the set of the plurality of TRPs indicating a DFI for the set of HARQ IDs, wherein the DFI is associated with the first CORESET pool index value or the second CORESET pool index value, and wherein the DFI is valid for at least one HARQ ID in the set of HARQ IDs based on the CORESET pool index value associated with the DFI and the CORESET pool index value associated with at least one of the one or more uplink messages. The operations of 910 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 910 may be performed as described in reference to Figure 7 The verification component 730 is used to perform.

[0139] Fig.10 A flow chart illustrating a method 1000 for supporting techniques for downlink feedback from multiple TRPs according to one or more aspects of the present disclosure is shown. The operations of the method 1000 may be implemented by a UE or components thereof as described herein. For example, the operations of the method 1000 may be implemented by a UE or components thereof as described herein. Figures 1 to 8 The UE 115 described herein may be executed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0140] At 1005, the method may include: sending one or more uplink messages to at least one TRP in a set of multiple TRPs, wherein each of the one or more uplink messages is associated with a first CORESET pool index value or a second CORESET pool index value, and wherein each uplink message is associated with a HARQ ID in a set of HARQ IDs. The operations of 1005 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1005 may be performed as described in reference to Figure 7 The HARQ component 725 is used to perform.

[0141] At 1010, the method may include: receiving a downlink message from a TRP in the set of the plurality of TRPs indicating a DFI for the set of HARQ IDs, wherein the DFI is associated with the first CORESET pool index value or the second CORESET pool index value, and wherein the DFI is valid for at least one HARQ ID in the set of HARQ IDs based on the CORESET pool index value associated with the DFI and the CORESET pool index value associated with at least one of the one or more uplink messages. The operations of 1010 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1010 may be performed as described in reference to Figure 7 The verification component 730 is used to perform.

[0142] At 1015, the method may include determining that the DFI for the first HARQ ID is valid based on the first symbol of the downlink message occurring at a first time threshold after the last symbol of the first uplink message associated with the first HARQ ID in the set of HARQ IDs, wherein the first time threshold is used to identify the most recently transmitted uplink message associated with at least one HARQ ID in the set of HARQ IDs. The operations of 1015 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1015 may be performed as described in reference to Figure 7 The timing verification component 735 is used to perform.

[0143] At 1020, the method may include: determining that the DFI for the first HARQ ID in the set of HARQ IDs is valid based on the CORESET pool index value associated with the DFI being the same as the CORESET pool index value associated with the first uplink message. The operations of 1020 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1020 may be performed as described in reference to Figure 7 The index verification component 740 described above is used to perform.

[0144] Fig.11 1 is a flow chart illustrating a method 1100 for supporting techniques for downlink feedback from multiple TRPs according to one or more aspects of the present disclosure. The operations of the method 1100 may be implemented by a UE or components thereof as described herein. For example, the operations of the method 1100 may be implemented by a UE or components thereof as described herein. Figures 1 to 8 The UE 115 described herein may be executed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0145] At 1105, the method may include: sending one or more uplink messages to at least one TRP in the set of multiple TRPs, wherein each of the one or more uplink messages is associated with a first CORESET pool index value or a second CORESET pool index value, and wherein each uplink message is associated with a HARQ ID in the set of HARQ IDs. The operations of 1105 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1105 may be performed as described in reference to Figure 7 The HARQ component 725 is used to perform.

[0146] At 1110, the method may include: receiving a downlink message from a TRP in the set of the plurality of TRPs indicating a DFI for the set of HARQ IDs, wherein the DFI is associated with the first CORESET pool index value or the second CORESET pool index value, and wherein the DFI is valid for at least one HARQ ID in the set of HARQ IDs based on the CORESET pool index value associated with the DFI and the CORESET pool index value associated with at least one of the one or more uplink messages. The operations of 1110 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1110 may be performed as described in reference to Figure 7 The verification component 730 is used to perform.

[0147] At 1115, the method may include determining that the DFI for the first HARQ ID is valid based on the first symbol of the downlink message occurring at a first time threshold after the last symbol of the first uplink message associated with the first HARQ ID in the set of HARQ IDs, wherein the first time threshold is used to identify the most recently transmitted uplink message associated with at least one HARQ ID in the set of HARQ IDs. The operations of 1115 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1115 may be performed as described in reference to Figure 7 The timing verification component 735 is used to perform.

[0148] At 1120, the method may include determining that the DFI for the first HARQ ID in the set of HARQ IDs is valid based on the first symbol of the downlink message occurring at a second time threshold after the last symbol of the first uplink message associated with the first HARQ ID, wherein the CORESET pool index value associated with the DFI is different from the CORESET pool index value associated with the first uplink message. The operations of 1120 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1120 may be performed as described in reference to Figure 7 The timing verification component 735 is used to perform.

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

[0150] Aspect 1: A method for wireless communication at a UE, the method comprising: sending one or more uplink messages to at least one TRP of a plurality of TRPs, wherein each of the one or more uplink messages is associated with a first CORESET pool index value or a second CORESET pool index value, and wherein each uplink message is associated with a HARQ ID in a HARQ ID set; and receiving a downlink message indicating a DFI for the HARQ ID set from a TRP of the plurality of TRPs, wherein the DFI is associated with the first CORESET pool index value or the second CORESET pool index value, and wherein the DFI is valid for at least one HARQ ID in the HARQ ID set based at least in part on the CORESET pool index value associated with the DFI and the CORESET pool index value associated with at least one of the one or more uplink messages.

[0151] Aspect 2: According to the method described in Aspect 1, the method also includes: determining that the DFI for the first HARQ ID is valid based at least in part on the first symbol of the downlink message appearing at a first time threshold after the last symbol of the first uplink message associated with the first HARQ ID in the HARQ ID set, wherein the first time threshold is used to identify the most recently sent uplink message associated with at least one HARQ ID in the HARQ ID set.

[0152] Aspect 3: According to the method according to Aspect 2, the method also includes: determining that the DFI for the first HARQ ID in the HARQ ID set is valid, at least in part based on the CORESET pool index value associated with the DFI being the same as the CORESET pool index value associated with the first uplink message.

[0153] Aspect 4: According to the method of Aspect 2, the method also includes: determining that the DFI for the first HARQ ID in the HARQ ID set is valid, at least in part based on the first symbol of the downlink message appearing at a second time threshold after the last symbol of the first uplink message associated with the first HARQ ID, wherein the CORESET pool index value associated with the DFI is different from the CORESET pool index value associated with the first uplink message.

[0154] Aspect 5: According to the method of aspect 4, the method further includes: receiving control signaling indicating the second time threshold.

[0155] Aspect 6: A method according to any one of Aspects 4 to 5, wherein the second time threshold is greater than or equal to the first time threshold, and the first time threshold is used to identify the most recently sent uplink message associated with the at least one HARQ ID in the HARQ ID set.

[0156] Aspect 7: According to the method described in any one of Aspects 1 to 6, the method further includes: receiving a control message instructing each TRP in the multiple TRPs to send a corresponding DFI; and determining whether the DFI is valid based at least in part on the control message.

[0157] Aspect 8: A method according to any one of Aspects 1 to 7, wherein receiving the downlink message includes: receiving the downlink message via a CORESET associated with the first CORESET pool index value or the second CORESET pool index value, wherein the CORESET pool index value associated with the DFI corresponds to the first CORESET pool index value or the second CORESET pool index value associated with the CORESET used to receive the downlink message.

[0158] Aspect 9: The method according to any one of aspects 1 to 7, the method further comprising: receiving an indication of the CORESET pool index value associated with the DFI within the downlink message.

[0159] Aspect 10: According to the method described in any one of Aspects 1 to 9, the method further includes: identifying the most recently sent uplink message among the one or more uplink messages for each HARQ ID in the HARQID set, identifying the most recently sent uplink message for each HARQ ID based at least in part on the first symbol of the downlink message appearing at a time threshold after the last symbol of each most recently sent first uplink message; and determining whether the DFI is valid based at least in part on the most recently sent uplink message for each HARQ ID.

[0160] Aspect 11: According to the method described in any one of Aspects 1 to 10, the method further includes: determining the CORESET pool index value associated with the at least one uplink message based at least in part on the CORESET pool index value associated with the corresponding control message that schedules the at least one uplink message, wherein the CORESET pool index value associated with the corresponding control message is at least in part based on the CORESET used to receive the corresponding control message.

[0161] Aspect 12: According to the method described in any one of Aspects 1 to 10, the method further includes: receiving one or more control messages indicating one or more configured authorization configurations associated with the one or more uplink messages, wherein each of the one or more configured authorization configurations indicates the first CORESET pool index value or the second CORESET pool index value, and wherein the CORESET pool index value associated with each of the one or more uplink messages is at least partially based on the one or more configured authorization configurations.

[0162] Aspect 13: According to the method described in any one of Aspects 1 to 10, the method further includes: receiving one or more control messages indicating one or more configured authorization configurations associated with the one or more uplink messages, wherein corresponding downlink control information for activating each of the one or more configured authorization configurations is received via the corresponding CORESET associated with the first CORESET pool index value or the second CORESET pool index value, and wherein the CORESET pool index value associated with each of the one or more uplink messages is at least partially based on the first CORESET pool index value or the second CORESET pool index value associated with the corresponding CORESET used to receive the corresponding downlink control information.

[0163] Aspect 14: A method according to any one of Aspects 1 to 10, wherein the CORESET pool index value associated with each uplink message of the one or more uplink messages is at least partially based on the corresponding HARQ ID associated with each uplink message in the HARQ ID set, and each HARQ ID corresponds to the first CORESET pool index value or the second CORESET pool index value.

[0164] Aspect 15: A method according to any one of Aspects 1 to 14, wherein the first CORESET pool index value is associated with a first TRP among the multiple TRPs, and the second CORESET pool index value is associated with a second TRP among the multiple TRPs.

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

[0166] Aspect 17: An apparatus for wireless communication at a UE, the apparatus comprising: at least one component for performing the method according to any one of aspects 1 to 15.

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

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

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

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

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

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

[0173] Computer-readable medium includes both non-transient computer storage medium and communication medium, and it includes any medium that facilitates computer program to be transmitted from one position to another position.Non-transient storage medium can be any available medium that can be accessed by general or special-purpose computer.By way of example and not limitation, non-transient computer-readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage device, disk storage device or other magnetic storage device, or can be used for carrying or storing desired program code parts and any other non-transient medium that can be accessed by general or special-purpose computer or general or special-purpose processor in the form of instruction or data structure.In addition, any connection is appropriately referred to as computer-readable medium.For example, if software is sent from website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of computer-readable medium. As used herein, disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc. Disks can reproduce data magnetically, while discs can reproduce data optically using lasers. Combinations of the above are also included within the scope of computer readable media.

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

[0175] The terms "determine" or "determining" encompass a variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or other data structure), ascertaining, and the like. Furthermore, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), etc. Additionally, "determining" may include parsing, obtaining, selecting, choosing, establishing, and other such similar actions.

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

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

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

Claims

1. A method for wireless communication at a user equipment (UE), the method comprising: sending one or more uplink messages to at least one of the plurality of transmission and reception points, wherein each of the one or more uplink messages is associated with a first control resource set pool index value or a second control resource set pool index value, and wherein each uplink message is associated with a hybrid automatic repeat request (HARQ) identifier in a set of HARQ identifiers; as well as A downlink message indicating downlink feedback information for the HARQ identifier set is received from a transmitting and receiving point among the multiple transmitting and receiving points, wherein the downlink feedback information is associated with the first control resource pool index value or the second control resource pool index value, and wherein the downlink feedback information is valid for at least one HARQ identifier in the HARQ identifier set at least partially based on the control resource pool index value associated with the downlink feedback information and the control resource pool index value associated with at least one uplink message among the one or more uplink messages.

2. The method according to claim 1, further comprising: The downlink feedback information for a first HARQ identifier in the HARQ identifier set is determined to be valid based at least in part on the first symbol of the downlink message appearing at a first time threshold after the last symbol of a first uplink message associated with the first HARQ identifier in the HARQ identifier set, wherein the first time threshold is used to identify the most recently sent uplink message associated with at least one HARQ identifier in the HARQ identifier set.

3. The method according to claim 2, further comprising: The downlink feedback information for the first HARQ identifier in the HARQ identifier set is determined to be valid based at least in part on the control resource set pool index value associated with the downlink feedback information and the control resource set pool index value associated with the first uplink message being the same.

4. The method according to claim 2, further comprising: The downlink feedback information for the first HARQ identifier in the HARQ identifier set is determined to be valid based at least in part on the first symbol of the downlink message appearing at a second time threshold after the last symbol of the first uplink message associated with the first HARQ identifier, wherein the control resource set pool index value associated with the downlink feedback information is different from the control resource set pool index value associated with the first uplink message.

5. The method according to claim 4, further comprising: Control signaling indicating the second time threshold is received.

6. The method of claim 4, wherein the second time threshold is greater than or equal to the first time threshold, and the first time threshold is used to identify the most recently sent uplink message associated with the at least one HARQ identifier in the HARQ identifier set.

7. The method according to claim 1, further comprising: receiving a control message instructing each of the plurality of transmitting and receiving points to transmit corresponding downlink feedback information; as well as Based at least in part on the control message, a determination is made as to whether the downlink feedback information is valid.

8. The method of claim 1 , wherein receiving the downlink message comprises: The downlink message is received via a control resource set associated with the first control resource set pool index value or the second control resource set pool index value, wherein the control resource set pool index value associated with the downlink feedback information corresponds to the first control resource set pool index value or the second control resource set pool index value associated with the control resource set used to receive the downlink message.

9. The method according to claim 1, further comprising: An indication of the control resource set pool index value associated with the downlink feedback information is received within the downlink message.

10. The method according to claim 1, further comprising: identifying a most recently transmitted uplink message of the one or more uplink messages for each HARQ identifier in the set of HARQ identifiers, identifying the most recently transmitted uplink message for each HARQ identifier based at least in part on a first symbol of the downlink message occurring at a time threshold after a last symbol of each most recently transmitted first uplink message; as well as A determination is made whether the downlink feedback information is valid based at least in part on the most recently transmitted uplink message for each HARQ identifier.

11. The method according to claim 1, further comprising: The control resource pool index value associated with at least one uplink message is determined at least in part based on a control resource pool index value associated with a corresponding control message that schedules the at least one uplink message, wherein the control resource pool index value associated with the corresponding control message is at least in part based on a control resource set used to receive the corresponding control message.

12. The method according to claim 1, further comprising: Receive one or more control messages indicating one or more configured authorization configurations associated with the one or more uplink messages, wherein each of the one or more configured authorization configurations indicates the first control resource set pool index value or the second control resource set pool index value, and wherein the control resource set pool index value associated with each of the one or more uplink messages is at least partially based on the one or more configured authorization configurations.

13. The method according to claim 1, further comprising: Receive one or more control messages indicating one or more configured authorization configurations associated with the one or more uplink messages, wherein corresponding downlink control information for activating each of the one or more configured authorization configurations is received via a corresponding control resource set associated with the first control resource set pool index value or the second control resource set pool index value, and wherein the control resource set pool index value associated with each of the one or more uplink messages is at least partially based on the first control resource set pool index value or the second control resource set pool index value associated with the corresponding control resource set used to receive the corresponding downlink control information.

14. A method according to claim 1, wherein the control resource set pool index value associated with each uplink message of the one or more uplink messages is at least partially based on the corresponding HARQ identifier associated with each uplink message in the HARQ identifier set, wherein each HARQ identifier corresponds to the first control resource set pool index value or the second control resource set pool index value.

15. A method according to claim 1, wherein the first control resource set pool index value is associated with a first sending and receiving point among the multiple sending and receiving points, and the second control resource set pool index value is associated with a second sending and receiving point among the multiple sending and receiving points.

16. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: sending one or more uplink messages to at least one of the plurality of transmission and reception points, wherein each of the one or more uplink messages is associated with a first control resource set pool index value or a second control resource set pool index value, and wherein each uplink message is associated with a hybrid automatic repeat request (HARQ) identifier in a set of HARQ identifiers; as well as A downlink message indicating downlink feedback information for the HARQ identifier set is received from a transmitting and receiving point among the multiple transmitting and receiving points, wherein the downlink feedback information is associated with the first control resource pool index value or the second control resource pool index value, and wherein the downlink feedback information is valid for at least one HARQ identifier in the HARQ identifier set at least partially based on the control resource pool index value associated with the downlink feedback information and the control resource pool index value associated with at least one uplink message among the one or more uplink messages.

17. The apparatus of claim 16, wherein the instructions are further executable by the processor to cause the apparatus to: The downlink feedback information for a first HARQ identifier in the HARQ identifier set is determined to be valid based at least in part on the first symbol of the downlink message appearing at a first time threshold after the last symbol of a first uplink message associated with the first HARQ identifier in the HARQ identifier set, wherein the first time threshold is used to identify the most recently sent uplink message associated with at least one HARQ identifier in the HARQ identifier set.

18. The apparatus of claim 17, wherein the instructions are further executable by the processor to cause the apparatus to: The downlink feedback information for the first HARQ identifier in the HARQ identifier set is determined to be valid based at least in part on the control resource set pool index value associated with the downlink feedback information and the control resource set pool index value associated with the first uplink message being the same.

19. The apparatus of claim 17, wherein the instructions are further executable by the processor to cause the apparatus to: The downlink feedback information for the first HARQ identifier in the HARQ identifier set is determined to be valid based at least in part on the first symbol of the downlink message appearing at a second time threshold after the last symbol of the first uplink message associated with the first HARQ identifier, wherein the control resource set pool index value associated with the downlink feedback information is different from the control resource set pool index value associated with the first uplink message.

20. The apparatus of claim 19, wherein the instructions are further executable by the processor to cause the apparatus to: Control signaling indicating the second time threshold is received.

21. The apparatus of claim 19, wherein the second time threshold is greater than or equal to the first time threshold, the first time threshold being used to identify the most recently transmitted uplink message associated with the at least one HARQ identifier in the HARQ identifier set.

22. The apparatus of claim 16, wherein the instructions are further executable by the processor to cause the apparatus to: receiving a control message instructing each of the plurality of transmission and reception points to transmit corresponding downlink feedback information; and Based at least in part on the control message, a determination is made as to whether the downlink feedback information is valid.

23. The apparatus of claim 16, wherein the instructions to receive the downlink message are executable by the processor to cause the apparatus to: The downlink message is received via a control resource set associated with the first control resource set pool index value or the second control resource set pool index value, wherein the control resource set pool index value associated with the downlink feedback information corresponds to the first control resource set pool index value or the second control resource set pool index value associated with the control resource set used to receive the downlink message.

24. The apparatus of claim 16, wherein the instructions are further executable by the processor to cause the apparatus to: An indication of the control resource set pool index value associated with the downlink feedback information is received within the downlink message.

25. The apparatus of claim 16, wherein the instructions are further executable by the processor to cause the apparatus to: Identifying a most recently transmitted uplink message of the one or more uplink messages for each HARQ identifier in the set of HARQ identifiers, identifying the most recently transmitted uplink message for each HARQ identifier based at least in part on a first symbol of the downlink message occurring at a time threshold after a last symbol of each most recently transmitted first uplink message; and A determination is made whether the downlink feedback information is valid based at least in part on the most recently transmitted uplink message for each HARQ identifier.

26. The apparatus of claim 16, wherein the instructions are further executable by the processor to cause the apparatus to: The control resource pool index value associated with at least one uplink message is determined at least in part based on a control resource pool index value associated with a corresponding control message that schedules the at least one uplink message, wherein the control resource pool index value associated with the corresponding control message is at least in part based on a control resource set used to receive the corresponding control message.

27. The apparatus of claim 16, wherein the instructions are further executable by the processor to cause the apparatus to: Receive one or more control messages indicating one or more configured authorization configurations associated with the one or more uplink messages, wherein each of the one or more configured authorization configurations indicates the first control resource set pool index value or the second control resource set pool index value, and wherein the control resource set pool index value associated with each of the one or more uplink messages is at least partially based on the one or more configured authorization configurations.

28. The apparatus of claim 16, wherein the instructions are further executable by the processor to cause the apparatus to: Receive one or more control messages indicating one or more configured authorization configurations associated with the one or more uplink messages, wherein corresponding downlink control information for activating each of the one or more configured authorization configurations is received via a corresponding control resource set associated with the first control resource set pool index value or the second control resource set pool index value, and wherein the control resource set pool index value associated with each of the one or more uplink messages is at least partially based on the first control resource set pool index value or the second control resource set pool index value associated with the corresponding control resource set used to receive the corresponding downlink control information.

29. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: means for transmitting one or more uplink messages to at least one of a plurality of transmission and reception points, wherein each of the one or more uplink messages is associated with a first control resource set pool index value or a second control resource set pool index value, and wherein each uplink message is associated with a hybrid automatic repeat request (HARQ) identifier from a set of HARQ identifiers; and A component for receiving a downlink message indicating downlink feedback information for the HARQ identifier set from a transmitting and receiving point among the multiple transmitting and receiving points, wherein the downlink feedback information is associated with the first control resource set pool index value or the second control resource set pool index value, and wherein the downlink feedback information is valid for at least one HARQ identifier in the HARQ identifier set at least in part based on the control resource set pool index value associated with the downlink feedback information and the control resource set pool index value associated with at least one uplink message among the one or more uplink messages.

30. A non-transitory computer-readable medium storing code for wireless communication at a user equipment (UE), the code comprising instructions executable by a processor to: sending one or more uplink messages to at least one of a plurality of transmission and reception points, wherein each of the one or more uplink messages is associated with a first control resource set pool index value or a second control resource set pool index value, and wherein each uplink message is associated with a hybrid automatic repeat request (HARQ) identifier in a set of HARQ identifiers; and A downlink message indicating downlink feedback information for the HARQ identifier set is received from a transmitting and receiving point among the multiple transmitting and receiving points, wherein the downlink feedback information is associated with the first control resource pool index value or the second control resource pool index value, and wherein the downlink feedback information is valid for at least one HARQ identifier in the HARQ identifier set at least partially based on the control resource pool index value associated with the downlink feedback information and the control resource pool index value associated with at least one uplink message among the one or more uplink messages.

Images