Dynamic hybrid automatic repeat request (HARQ) codebook for multiple transmit receive point (TRP) communications

Abstract

This disclosure provides systems, methods, and apparatus for wireless communication. In one aspect, a multiple transmit receive point (TRP) approach is provided for hybrid automatic repeat request (HARQ) acknowledgement (ACK) feedback using a counter downlink assignment indicator (DAI) (cDAI) and a total DAI (tDAI). For example, some techniques and apparatuses described herein may provide a joint counting method in which cDAI and tDAI are jointly implemented and tracked between TRPs of a multi-TRP group. This may be useful in ideal backhaul scenarios when multiple TRP groups are jointly scheduled, and may be more robust against errors than a separate counting method. Some techniques and apparatuses described herein may provide separate counting methods in which cDAI and tDAI are implemented and tracked by respective TRPs of a multi-TRP population, respectively.

Description

[0001] This divisional application is a divisional application of the PCT national phase patent application with a PCT international filing date of February 7, 2020, national application number 202080013379.3, and titled “Dynamic Hybrid Automatic Repeat Request (HARQ) Codebook for Multiple Transmission Reception Point (TRP) Communications”. Technical Field

[0002] Various aspects of the present disclosure relate generally to wireless communications, and more particularly to techniques for dynamic hybrid automatic repeat request (HARQ) codebooks for multiple transmission reception point (TRP) communications. Background Art

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

[0004] A wireless communication network may include several base stations (BS) that can support communication for several user equipments (UEs). User equipments (UEs) may communicate with base stations (BSs) via downlinks (DL) and uplinks (UL). DL (or forward link) refers to the communication link from the BS to the UE, while UL (or reverse link) refers to the communication link from the UE to the BS. As will be described in more detail herein, a BS may be referred to as a Node B, gNB, access point (AP), radio head, transmit receive point (TRP), new radio (NR) BS, 5G Node B, or other examples.

[0005] The above multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different user equipment to communicate at city, country, region, and even global levels. New Radio (NR) (which may also be referred to as 5G) is an enhancement set to the LTE mobile standard promulgated by the Third Generation Partnership Project (3GPP). NR is designed to improve spectrum efficiency, reduce costs, improve services, utilize new spectrum, and better integrate with other open standards by using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on DL, using CP-OFDM and / or SC-FDM (e.g., also referred to as discrete Fourier transform spread OFDM (DFT-s-OFDM) on UL, and support beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation to better support mobile broadband Internet access. However, as the demand for mobile broadband access continues to grow, there is a need for further improvements in LTE and NR technologies. Summary of the invention

[0006] The systems, methods, and devices of the disclosure each have several innovative aspects, no single one of which is solely responsible for the desirable attributes disclosed herein.

[0007] An innovative aspect of the subject matter described in the present disclosure may be implemented in a wireless communication method performed by a user equipment (UE). The method may include receiving at least one of: one or more first downlink control information (DCI) transmissions or one or more second DCI transmissions, wherein the one or more first DCI transmissions are associated with a first transmit reception point (TRP), and the one or more second DCI transmissions are associated with a second TRP, and wherein the one or more first DCI transmissions and the one or more second DCI transmissions are associated with a physical downlink control channel (PDCCH) monitoring opportunity; determining one or more hybrid automatic repeat request acknowledgment (HARQ-ACK) payloads based at least in part on a counter downlink assignment indicator (DAI) value and a total DAI value of the one or more first DCI transmissions and the one or more second DCI transmissions; and transmitting HARQ-ACK feedback based at least in part on the one or more HARQ-ACK payloads.

[0008] In some implementations, the method may include determining whether a DCI transmission associated with the first TRP or the second TRP was not received based at least in part on a counter DAI value and a total DAI value, and the HARQ-ACK feedback may identify whether the DCI transmission was not received.

[0009] In some implementations, the method may include determining which of the first TRP and the second TRP transmitted the DCI transmission based at least in part on a ranking of the first TRP and the second TRP, wherein the ranking is based at least in part on a control resource set identifier or a search space identifier of the DCI transmission.

[0010] In some implementations, the method may include determining which of the first TRP and the second TRP transmitted the DCI transmission based at least in part on an order of the first TRP and the second TRP, and the order may be based at least in part on an indication in the DCI transmission indicating which TRP transmitted the DCI transmission.

[0011] In some implementations, the counter DAI value indicates a corresponding counter value for each DCI transmission transmitted by the first TRP and the second TRP at or before the PDCCH monitoring opportunity. In some implementations, the total DAI value indicates the total number of DCI transmissions that have been transmitted jointly by the first TRP and the second TRP at or before the PDCCH monitoring opportunity. In some implementations, the first TRP and the second TRP are associated with a single serving cell. In some implementations, the total DAI value applies to all serving cells and TRPs across the first TRP and the second TRP for the PDCCH monitoring opportunity.

[0012] In some implementations, the one or more HARQ-ACK payloads include a joint HARQ-ACK payload of the first TRP and the second TRP. In some implementations, the one or more HARQ-ACK payloads include respective HARQ-ACK payloads of the first TRP and the second TRP. In some implementations, the HARQ-ACK feedback indicates that the DCI transmission was not received, and the HARQ-ACK feedback indicates which TRP transmitted the DCI transmission based at least in part on a fixed assumption about which TRP transmitted the DCI transmission. In some implementations, the HARQ-ACK feedback indicates that the DCI transmission was not received, and the HARQ-ACK feedback indicates which TRP transmitted the DCI transmission based at least in part on which TRP transmitted an adjacent DCI transmission before or after the DCI transmission.

[0013] In some implementations, the total DAI value includes the corresponding total DAI values ​​of the first TRP and the second TRP, and the counter DAI value is maintained separately for the first TRP and the second TRP. In some implementations, when the UE is configured to have a single serving cell, the total DAI value is not provided in one or more first DCI transmissions and one or more second DCI transmissions. In some implementations, the method may include determining which of the first TRP and the second TRP transmitted a specific DCI transmission in one or more first DCI transmissions or one or more second DCI transmissions based at least in part on a TRP differentiation technique. In some implementations, the method may include determining which of the first TRP and the second TRP transmitted a specific counter DAI value or a specific total DAI value based at least in part on a TRP differentiation technique. In some implementations, when the UE is configured to have a single serving cell, the total DAI value is provided in one or more first DCI transmissions and one or more second DCI transmissions.

[0014] In some implementations, the method may include receiving information indicating whether the counter DAI value and the total DAI value are based at least in part on a joint count of the first TRP and the second TRP or a separate count. In some implementations, the information indicating whether the counter DAI value and the total DAI value are based at least in part on a joint count or a separate count further indicates whether the first TRP and the second TRP are associated with a joint scheduling configuration. In some implementations, the information indicating whether the counter DAI value and the total DAI value are based at least in part on a joint count of the first TRP and the second TRP or a separate count includes information indicating whether the HARQ-ACK feedback uses a joint HARQ-ACK payload of the first TRP and the second TRP or a separate HARQ-ACK payload. In some implementations, the method may include receiving information indicating whether the HARQ-ACK feedback uses a joint HARQ-ACK payload of the first TRP and the second TRP or a separate HARQ-ACK payload. In some implementations, the first TRP and the second TRP are distinguished at least in part based on the corresponding control resource set identifiers of the first TRP and the second TRP.

[0015] Another innovative aspect of the subject matter described in the present disclosure may be implemented in a UE for wireless communication. The UE may include a memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to obtain at least one of the following: one or more first DCI transmissions or one or more second DCI transmissions, wherein the one or more first DCI transmissions are associated with a first TRP, and the one or more second DCI transmissions are associated with a second TRP, and wherein the one or more first DCI transmissions and the one or more second DCI transmissions are associated with a PDCCH monitoring opportunity; determining one or more HARQ-ACK payloads based at least in part on the counter DAI value and the total DAI value of the one or more first DCI transmissions and the one or more second DCI transmissions; and outputting HARQ-ACK feedback based at least in part on the one or more HARQ-ACK payloads. In some aspects, the UE may perform or implement any one or more of the aspects described in conjunction with the methods described herein above or elsewhere.

[0016] Another innovative aspect of the subject matter described in the present disclosure may be implemented in a non-transitory computer-readable medium storing one or more instructions for wireless communication. The one or more instructions, when executed by one or more processors of the UE, may cause the one or more processors to receive at least one of the following: one or more first DCI transmissions or one or more second DCI transmissions, wherein the one or more first DCI transmissions are associated with a first TRP, and the one or more second DCI transmissions are associated with a second TRP, and wherein the one or more first DCI transmissions and the one or more second DCI transmissions are associated with a PDCCH monitoring opportunity; determining one or more HARQ-ACK payloads based at least in part on the counter DAI value and the total DAI value of the one or more first DCI transmissions and the one or more second DCI transmissions; and providing HARQ-ACK feedback based at least in part on the one or more HARQ-ACK payloads. In some aspects, the non-transitory computer-readable medium may implement any one or more of the aspects described in conjunction with the methods described herein above or elsewhere.

[0017] Another innovative aspect of the subject matter described in the present disclosure may be implemented in a device for wireless communication. The device may include a device for receiving at least one of the following: one or more first DCI transmissions or one or more second DCI transmissions, wherein the one or more first DCI transmissions are associated with a first TRP, and the one or more second DCI transmissions are associated with a second TRP, and wherein the one or more first DCI transmissions and the one or more second DCI transmissions are associated with a PDCCH monitoring opportunity; a device for determining one or more HARQ-ACK payloads based at least in part on the counter DAI value and the total DAI value of the one or more first DCI transmissions and the one or more second DCI transmissions; and a device for transmitting HARQ-ACK feedback based at least in part on the one or more HARQ-ACK payloads. In some aspects, the equipment may perform or implement any one or more of the aspects described in conjunction with the methods described herein above or elsewhere.

[0018] Aspects generally include methods, apparatuses, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, transmission reception points, wireless communication devices, and processing systems as substantially described herein with reference to and as illustrated in the accompanying drawings.

[0019] Details of one or more implementations of the subject matter described in the present disclosure are set forth in the accompanying drawings and the following description. Other features, aspects, and advantages will become apparent from this description, the accompanying drawings, and the claims. It should be noted that the relative dimensions of the following drawings may not be drawn to scale. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1 is a block diagram conceptually illustrating an example of a wireless communication network.

[0021] Figure 2 is a block diagram conceptually illustrating an example of a base station in communication with a UE in a wireless communication network.

[0022] Figure 3 is a diagram illustrating an example of dynamic hybrid automatic repeat request (HARQ)-acknowledgement (ACK) codebook usage for multiple transmission reception point (TRP) communications.

[0023] Figure 4 is a diagram illustrating an example of HARQ-ACK feedback determination for multi-TRP communications using a joint total downlink assignment indicator approach.

[0024] Figure 5 is a diagram illustrating an example process performed, for example, by user equipment.

[0025] Like reference numbers and designations in the various drawings indicate like elements. DETAILED DESCRIPTION

[0026] The following description is directed to certain implementations in order to describe the innovative aspects of the present disclosure. However, one of ordinary skill in the art will readily recognize that the teachings herein can be applied in many different ways. Some examples in the present disclosure are based on wireless and wired local area network (LAN) communications according to the Institute of Electrical and Electronics Engineers (IEEE) 802.11 wireless standard, the IEEE 802.3 Ethernet standard, and the IEEE 1901 Power Line Communication (PLC) standard. However, the described implementations can be implemented in any device, system, or network capable of transmitting and receiving radio frequency signals according to any of the following wireless communication protocols: any of the IEEE 802.11 standards, (Bluetooth) standard, code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), global system for mobile communications (GSM), GSM / general packet radio service (GPRS), enhanced data GSM environment (EDGE), terrestrial trunked radio (TETRA), wideband CDMA (W-CDMA), evolution data optimized (EV-DO), 1xEV-DO, EV-DO Revision A, EV-DO Revision B, high speed packet access (HSPA), high speed downlink packet access (HSDPA), high speed uplink packet access (HSUPA), evolved high speed packet access (HSPA+), long term evolution (LTE), AMPS, or other known signals for communication within a wireless network, cellular network, or Internet of Things (IoT) network (such as, a system utilizing 3G, 4G or 5G or further implementations thereof).

[0027] A hybrid automatic repeat request (HARQ) acknowledgment (ACK) system provides feedback to a UE indicating whether certain transmissions have been received by the UE. For example, when a transmission has been received by the UE, the UE may provide HARQ feedback indicating an ACK value, and may provide HARQ feedback (also known as HARQ-ACK feedback) indicating a negative ACK (NACK) value when the transmission has not been received by the UE or is received unsuccessfully. HARQ-ACK feedback may use a semi-static configuration or a dynamic configuration, in which the UE uses a configured or predefined size for HARQ feedback (or for a HARQ codebook used to generate HARQ feedback), and in a dynamic configuration, the UE determines the size of the HARQ feedback or the HARQ codebook. Some of the techniques and apparatus described herein relate to a dynamic HARQ-ACK system, but the techniques and apparatus described herein may be implemented using another type of HARQ-ACK system, such as a semi-static HARQ-ACK system.

[0028] In some cases, the UE may use a HARQ codebook to determine HARQ feedback. For example, the UE may determine whether a group of transmissions is successfully received, may add ACK or NACK to the codebook in a specific order to indicate which transmissions in the group of transmissions are successfully received, and may use the codebook to generate HARQ feedback.

[0029] As an example, the UE may determine whether downlink control information (DCI) and the corresponding data transmission are successfully received, and may provide HARQ feedback indicating which DCI and the corresponding data transmission are successfully received. In this case, the UE may determine the HARQ codebook based at least in part on a physical downlink control channel (PDCCH) monitoring opportunity of the DCI and a downlink (DL) assignment indicator (DAI) associated with the DCI.

[0030] For example, the PDCCH monitoring opportunities may be based at least in part on the configuration of different search space sets in different cells. The UE may use the union of the PDCCH monitoring opportunities across the active DL bandwidth parts (BWPs) of all configured serving cells, sorted in ascending order of the start time of the search space sets associated with the PDCCH monitoring opportunities. If two search space sets are associated with the same start time, the two search space sets may be counted as a single PDCH monitoring opportunity.

[0031] The UE may receive a DAI in a DCI, such as in a downlink grant associated with the DCI. The DAI may include a counter DAI (sometimes abbreviated as cDAI) and a total DAI (sometimes abbreviated as tDAI). The cDAI may indicate the cumulative number of serving cells and PDCCH monitoring opportunity pairs in which DL DCI has been transmitted by the base station, up to the current serving cell and PDCCH monitoring opportunity. When there are multiple serving cells, such as in carrier aggregation, tDAI may be used. The tDAI may indicate the total number of serving cells and PDCCH monitoring opportunities in which DL DCI has been transmitted by the base station, up to the current PDCCH monitoring opportunity. Therefore, the same tDAI monitoring value may be used for all DCIs in the same PDCCH monitoring opportunity. This provides protection against missing the DCI corresponding to the last serving cell in a particular PDCCH monitoring opportunity, because the tDAI informs the UE that, based on the cDAI, one more DCI is to be expected than the DCI already received. The cDAI and tDAI of a specific DCI are represented herein as {cDAI, tDAI} or (cDAI, tDAI).

[0032] If no DL DCI is missed, the ACK / NACK corresponding to the received PDSCH may be placed in the codebook in the same order as the cDAI. If the DL DCI is missed, the NACK may be placed in the codebook at a position corresponding to the cDAI of the missed DL DCI. The UE may determine whether the DL DCI is missed by comparing consecutive cDAI values ​​(e.g., a cDAI value of 0, then 1, then 3 may indicate that a DCI with a cDAI value of 2 is missed) or by comparing the tDAI and cDAI of all DCIs in a given PDCCH monitoring opportunity. The UE may generate HARQ feedback based at least in part on the codebook and may provide HARQ feedback to the base station. Thus, the UE may identify the DCI that has been missed and may generate HARQ feedback based at least in part on the cDAI and tDAI.

[0033] Some wireless communication systems may use a multi-transmission reception point (TRP) transmission technique in which multiple TRPs (or multiple antenna panels, or multiple antenna sub-panels) transmit the same transmission or corresponding transmissions. In this case, each TRP can provide a corresponding DCI to schedule a corresponding codeword or transmission from each TRP. It is ideal to provide HARQ-ACK feedback for multi-TRP deployments so that the TRP (or a base station associated with the TRP) can determine when DCI reception is unsuccessful. However, performing HARQ-ACK feedback for multi-TRP communications may be challenging. For example, different TRPs may be associated with different return conditions, and there may be differences in the HARQ-ACK feedback process for a joint payload (HARQ-ACK feedback for a multi-TRP group is associated with all TRPs in the multi-TRP group) compared to a separate payload (HARQ-ACK feedback for a multi-TRP group is provided using a corresponding HARQ-ACK payload for each TRP in the multi-TRP group).

[0034] Some techniques and apparatus described herein provide a multi-TRP approach for HARQ-ACK feedback using cDAI and tDAI. For example, some techniques and apparatus described herein may provide a joint counting method in which cDAI and tDAI are jointly implemented and tracked between each TRP of a multi-TRP group. This may be useful in an ideal backhaul scenario when multiple TRP groups are jointly scheduled, and may be more robust against errors than a separate counting method. For example, cDAI may indicate the cumulative number of serving cell, TRP, and PDCCH monitoring opportunity triplets in which DL DCI has been sent by the base station, up to the current serving cell, TRP, and current PDCCH monitoring opportunity triplet. The serving cell, TRP, and PDCCH monitoring opportunity triplet may refer to information that identifies a combination of serving cell, TRP, and PDCCH monitoring opportunity. For example, considering a set of serving cells 1 and 2, TRPs A and B, and PDCCH monitoring opportunities X and Y, possible triplets include [1A X], [2A X], [1B X], [2B X], [1A Y], [2A Y], [1B Y], and [2B Y], for a total of 8 triplets. tDAI may indicate the total number of such triplets in which DL DCI has been transmitted by the base station until the current PDCCH monitoring opportunity. These triplets may be arranged in any order. A more detailed description of the cDAI and tDAI counting methods is provided in conjunction with Figure 4 Some techniques and apparatus described herein may provide a separate counting method, where cDAI and tDAI are implemented and tracked separately by each TRP of a multi-TRP group. This is useful for both ideal and non-ideal backhaul scenarios.

[0035] Specific implementations of the subject matter described in this disclosure may be implemented to achieve one or more of the following potential advantages. Some implementations of the subject matter may improve the throughput and reliability of wireless networks, particularly wireless networks deployed using multiple TRPs. In addition, some implementations described herein may improve the reliability of HARQ-ACK feedback and reduce the inefficiency of multi-TRP downlink communications. Further, some implementations described herein may provide HARQ-ACK feedback regardless of whether the multi-TRP group is associated with an ideal backhaul or a non-ideal backhaul, thereby improving the versatility of the multi-TRP group and potentially relaxing the implementation requirements for the multi-TRP group.

[0036] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be implemented in many different forms and should not be interpreted as being limited to any specific structure or function given throughout the present disclosure. On the contrary, these aspects are provided to make the present disclosure thorough and complete, and it will fully convey the scope of the present disclosure to those skilled in the art. Based on the teachings herein, it should be appreciated by those of ordinary skill in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is implemented independently or implemented in combination with any other aspect of the present disclosure. For example, any number of aspects set forth herein can be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods practiced using supplements or other other structures, functionality, or structures and functionality as the various aspects of the present disclosure set forth herein. It should be understood that any aspect of the present disclosure disclosed herein can be implemented by one or more elements of the claims.

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

[0038] It should be noted that although various aspects may be described herein using terminology typically associated with 3G or 4G wireless technology, various aspects of the present disclosure may be applied in communication systems based on other generations, such as 5G / NR and later generations.

[0039] Figure 1 1 is a diagram illustrating a wireless network 100 in which various aspects of the present disclosure may be practiced. The wireless network 100 may be an LTE network or some other wireless network, such as a 5G or NR network. The wireless network 100 may include several BSs 110 (shown as BSs 110a, BSs 110b, BSs 110c, and BSs 110d) and other network entities. A BS is an entity that communicates with a user equipment (UE) and may also be referred to as a base station, NR BS, B node, gNB, 5G B node (NB), access point, transmit receive point (TRP), or other examples. Each BS may provide communication coverage for a particular geographic area. In 3GPP, the term "cell" may refer to a coverage area of ​​a BS or a BS subsystem serving the coverage area, depending on the context in which the term is used.

[0040] A BS may provide communication coverage for a macro cell, a pico cell, a femto cell, or another type of cell. A macro cell may cover a relatively large geographic area (such as several kilometers in radius) and may allow unrestricted access by UEs with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscriptions. A femto cell may cover a relatively small geographic area (such as a residence) and may allow restricted access by UEs associated with the femto cell (such as UEs in a closed subscriber group (CSG)). A BS for a macro cell may be referred to as a macro BS. A BS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS. In Figure 1 In the example shown in , BS 110a may be a macro BS for macro cell 102a, BS 110b may be a pico BS for pico cell 102b, and BS 110c may be a femto BS for femto cell 102c. The BS may support one or more (e.g., three) cells. The terms "eNB", "base station", "NR BS", "gNB", "TRP", "AP", "B node", "5G NB", and "cell" may be used interchangeably herein.

[0041] In some aspects, the cells may not necessarily be stationary, and the geographic area of ​​the cells may move depending on the location of the mobile BS. In some aspects, the BSs may be interconnected to each other or to one or more other BSs or network nodes (not shown) in the wireless network 100 via various types of backhaul interfaces, such as direct physical connections, virtual networks, or other examples using any suitable transport network.

[0042] The wireless network 100 may also include a relay station. A relay station is an entity that can receive transmissions of data from an upstream station (such as a BS or UE) and send transmissions of the data to a downstream station (such as a UE or BS). A relay station may also be a UE that can relay transmissions for other UEs. Figure 1 In the example shown in , a relay station 110d may communicate with a macro BS 110a and a UE 120d to facilitate communication between the BS 110a and the UE 120d. A relay station may also be referred to as a relay BS, a relay base station, a relay, or other examples.

[0043] The wireless network 100 may be a heterogeneous network including different types of BSs, such as a macro BS, a pico BS, a femto BS, a relay BS, or other examples. These different types of BSs may have different transmit power levels, different coverage areas, and different effects on interference in the wireless network 100. For example, a macro BS may have a high transmit power level (such as 5 to 40 watts), while a pico BS, a femto BS, and a relay BS may have a lower transmit power level (such as 0.1 to 2 watts).

[0044] A network controller 130 may be coupled to a set of BSs and may provide coordination and control of these BSs. The network controller 130 may communicate with each BS via a backhaul. The BSs may also communicate with each other indirectly, such as directly or via a wireless or wired backhaul.

[0045] UE 120 (such as 120a, 120b, 120c) can be dispersed throughout the wireless network 100, and each UE can be stationary or mobile. UE can also be referred to as an access terminal, terminal, mobile station, subscriber unit, station or other examples. UE can be a cellular phone (such as a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or equipment, a biometric sensor / device, a wearable device (smart watch, smart clothing, smart glasses, smart wristband, smart jewelry (such as smart ring, smart bracelet)), an entertainment device (such as music or video equipment, or satellite radio), a vehicle-mounted component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, or any other suitable device configured to communicate via a wireless or wired medium.

[0046] Some UEs may be considered as machine type communication (MTC) UEs, or evolved or enhanced machine type communication (eMTC) UEs. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, or other examples, which may communicate with a base station, another device (such as a remote device), or some other entity. A wireless node may provide connectivity to or to a network (such as a wide area network, the Internet, or a cellular network), for example, via a wired or wireless communication link. Some UEs may be considered as Internet of Things (IoT) devices, or may be implemented as NB-IoT (narrowband Internet of Things) devices. Some UEs may be considered as client equipment (CPE). UE 120 may be included inside a housing that houses components of UE 120, such as a processor component, a memory component, or other examples.

[0047] In general, any number of wireless networks may be deployed in a given geographic area. Each wireless network may support a specific RAT and may operate on one or more frequencies. RAT may also be referred to as a radio technology, an air interface, or other examples. Frequency may also be referred to as a carrier, a frequency channel, or other examples. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0048] In some aspects, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (without using base station 110 as an intermediary to communicate with each other) using one or more sidelink channels. For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or other examples), mesh networks, or other examples. In this case, UE 120 may perform scheduling operations, resource selection operations, or other operations described elsewhere herein as being performed by base station 110.

[0049] As indicated above, Figure 1 are provided as examples. Other examples may differ from those described in Figure 1 The content described.

[0050] Figure 2 A block diagram of a design 200 of a base station 110 and a UE 120 is shown, which may be Figure 1 One for each base station and one for each UE in the base station 110. Base station 110 may be equipped with T antennas 234a through 234t, and UE 120 may be equipped with R antennas 252a through 252r, where in general T≧1 and R≧1.

[0051] At the base station 110, the transmit processor 220 may receive data for one or more UEs from the data source 212, select one or more modulation and coding schemes (MCS) for each UE based at least in part on a channel quality indicator (CQI) received from the UE, process (e.g., encode and modulate) the data for each UE based at least in part on the MCS selected for the UE, and provide data symbols for all UEs. The transmit processor 220 may also process system information (e.g., for semi-static resource partitioning information (SRPI) or other examples) and control information (e.g., CQI requests, grants, upper layer signaling, or other examples), and provide overhead symbols and control symbols. The transmit processor 220 may also generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS)) and synchronization signals (e.g., primary synchronization signals (PSS) and secondary synchronization signals (SSS)). A transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (such as precoding) on ​​data symbols, control symbols, overhead symbols, or reference symbols, where applicable, and may provide T output symbol streams to T modulators (MOD) 232a to 232t. Each modulator 232 may process a respective output symbol stream (such as for OFDM or other examples) to obtain an output sample stream. Each modulator 232 may further process (such as converting to analog, amplifying, filtering, and up-converting) the output sample stream to obtain a downlink signal. The T downlink signals from modulators 232a to 232t may be transmitted via T antennas 234a to 234t, respectively. According to various aspects described in more detail below, position coding may be used to generate synchronization signals to convey additional information.

[0052] At UE 120, antennas 252a to 252r may receive downlink signals from base station 110 or other base stations and may provide received signals to demodulators (DEMODs) 254a to 254r, respectively. Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) the received signal to obtain input samples. Each demodulator 254 may further process the input samples (e.g., for OFDM or other examples) to obtain received symbols. A MIMO detector 256 may obtain received symbols from all R demodulators 254a to 254r, perform MIMO detection on the received symbols where applicable, and provide detected symbols. A receive processor 258 may process (e.g., demodulate and decode) the detected symbols, provide decoded data for UE 120 to a data sink 260, and provide decoded control information and system information to a controller or processor (controller / processor) 280. The channel processor may determine reference signal received power (RSRP), received signal strength indicator (RSSI), reference signal received quality (RSRQ), channel quality indicator (CQI), or other examples.In some aspects, one or more components of UE 120 may be included in a housing.

[0053] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information from a controller / processor 280 (such as for reports including RSRP, RSSI, RSRQ, CQI, or other examples). The transmit processor 264 may also generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266, if applicable, further processed by modulators 254a through 254r (such as for DFT-s-OFDM, CP-OFDM, or other examples), and transmitted to the base station 110. At the base station 110, uplink signals from the UE 120 and other UEs may be received by the antenna 234, processed by the demodulator 232, detected by the MIMO detector 236, if applicable, and further processed by the receive processor 238 to obtain decoded data and control information sent by the UE 120. The receive processor 238 may provide decoded data to a data sink 239 and decoded control information to a controller / processor 240. The base station 110 may include a communication unit 244 and communicate with the network controller 130 via the communication unit 244. The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292.

[0054] In some implementations, the controller / processor 240 may be a component of a processing system. A processing system may generally refer to a system or series of machines or components that receives inputs and processes those inputs to produce a set of outputs that may be delivered to other systems or components such as the UE 120. For example, a processing system of the UE 120 may refer to a system that includes various other components or subcomponents of the UE 120.

[0055] The processing system of UE 120 may interface with other components of UE 120, and may process information (such as input or signal) received from other components, output information to other components, etc. For example, a chip or modem of UE 120 may include a processing system, a first interface for receiving or obtaining information, and a second interface for outputting, transmitting, or providing information. In some cases, the first interface may refer to an interface between a processing system of a chip or modem and a receiver, so that UE 120 may receive information or signal input, and the information may be passed to the processing system. In some cases, the second interface may refer to an interface between a processing system of a chip or modem and a transmitter, so that UE 120 may transmit information output from the chip or modem. A person of ordinary skill in the art will readily appreciate that the second interface may also obtain or receive information or signal input, and the first interface may also output, transmit, or provide information.

[0056] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component(s) of the base station 110 may perform one or more techniques associated with dynamic hybrid automatic repeat request (HARQ) codebooks for multiple transmission reception point (TRP) communications, as described in more detail elsewhere herein. For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, or Figure 2 Any other component(s) may perform or direct e.g. Figure 5 The operations of process 500 or other processes as described herein may be performed. Memories 242 and 282 may store data and program codes for base station 110 and UE 120, respectively. Scheduler 246 may schedule UEs for data transmission on the downlink or uplink.

[0057] In some aspects, the UE 120 may include a device for receiving at least one of the following: one or more first downlink control information (DCI) transmissions or one or more second DCI transmissions, wherein the one or more first DCI transmissions are associated with a first transmit reception point (TRP) and the one or more second DCI transmissions are associated with a second TRP, and wherein the one or more first DCI transmissions and the one or more second DCI transmissions are associated with a physical downlink control channel (PDCCH) monitoring opportunity; a device for determining one or more hybrid automatic repeat request acknowledgment (HARQ-ACK) payloads based at least in part on a counter downlink assignment indicator (DAI) value and a total DAI value of the one or more first DCI transmissions and the one or more second DCI transmissions; a device for transmitting HARQ-ACK feedback based at least in part on the one or more HARQ-ACK payloads; and a device for transmitting HARQ-ACK feedback based at least in part on the one or more HARQ-ACK payloads. A device for determining whether a DCI transmission associated with a first TRP or a second TRP has not been received based on a counter DAI value and a total DAI value; a device for determining which of the first TRP and the second TRP transmitted a specific DCI transmission among one or more first DCI transmissions and one or more second DCI transmissions based at least in part on a TRP differentiation technique; a device for determining which of the first TRP and the second TRP transmitted a specific counter DAI value or a specific total DAI value based at least in part on a TRP differentiation technique; a device for receiving information indicating whether the counter DAI value and the total DAI value are based at least in part on a joint count of the first TRP and the second TRP or a separate count; a device for receiving information indicating whether HARQ-ACK feedback uses a joint HARQ-ACK payload or a separate HARQ-ACK payload for the first TRP and the second TRP; or other examples. In some aspects, such a device may include a device for determining which of the first TRP and the second TRP transmitted a specific counter DAI value or a specific total DAI value based at least in part on a TRP differentiation technique. Figure 2 One or more components of UE 120 are described.

[0058] Figure 3 is a diagram illustrating an example 300 of dynamic hybrid automatic repeat request (HARQ)-acknowledgement (ACK) codebook usage for multiple transmission reception point (TRP) communications.

[0059] like Figure 3As shown in , multiple TRPs 305 (shown as TRP A and TRP B) can communicate with the same UE 120 in a coordinated manner (such as using coordinated multipoint transmission or other examples) to improve reliability, increase throughput, or other examples. The TRPs 305 can coordinate these communications via a backhaul, which may have less latency or higher capacity when the TRPs 305 are co-located at the same base station 110 (such as different antenna arrays of the same base station 110), or may have greater latency or lower capacity when the TRPs 305 are located at different base stations 110. In some cases, the backhaul may be an ideal backhaul, such as a backhaul associated with a threshold waiting time or a backhaul that allows joint scheduling of TRP A and TRP B. In some other cases, the backhaul may be a non-ideal backhaul, such as a backhaul whose waiting time does not meet a threshold or does not allow joint scheduling.

[0060] TRP A and TRP B may be referred to herein as a multi-TRP group. As used herein, a multi-TRP group may refer to a group of TRPs to communicate with the same UE, a group of TRPs managed as a group by an access node controller, a group of TRPs transmitting the same physical downlink shared channel (PDSCH), a group of TRPs transmitting individual PDSCHs simultaneously or contemporaneously, or other examples.

[0061] A TRP may also be referred to as a BS, NR BS, Node B, 5G NB, AP, gNB, or some other term, or may also be used interchangeably with a "cell". In some aspects, multiple TRPs may be included in a single BS 110 (such as using corresponding antenna panels or quasi-co-location relationships). In some aspects, different TRPs may be included in different BSs 110. A TRP may use one or more antenna ports. A group of TRPs (such as TRP A and TRP B) may be configured to serve traffic to UE 120 individually (such as using dynamic selection) or jointly (such as using joint transmission). TRPs may be coordinated or collaborated via an access node controller (ANC). In some aspects, an inter-TRP interface may not be required or present. A TRP may be associated with a higher layer identifier, such as a control resource set (CORESET) identifier. For example, a CORESET identifier may include, may be based at least in part on, or may be mapped to a CORESET pool index.

[0062] As shown, a first physical downlink control channel (PDCCH) 310 may schedule communications for TRP A, and a second PDCCH 315 may schedule communications for TRP B. Here, as shown by reference numeral 320, the communications are PDSCHs, which may be common between TRP A and TRP B or may be different (such as different payloads, different modulation and coding schemes, different transmit powers, or different repetition schemes). For example, in a first multi-TRP transmission mode (mode 1), a single PDCCH may be used to schedule downlink data communications for a single PDSCH. In this case, multiple TRPs 305 (here TRP A and TRP B) may transmit communications to UE 120 on the same PDSCH. In some aspects, different TRPs 305 may transmit in different (such as non-intersecting) resource block (RB) sets or different symbol sets. Additionally or alternatively, different TRPs 305 may transmit using different layers (such as different multiple-input multiple-output (MIMO) layers). In some aspects, transmissions on different layers may occur in overlapping resource blocks or overlapping codewords. As another example, in a second multi-TRP transmission mode (Mode 2), multiple PDCCHs may be used to schedule downlink data communications for multiple corresponding PDSCHs (such as one PDCCH for each PDSCH).

[0063] As further shown, each PDCCH may be associated with a corresponding DCI, and each DCI may be associated with a cDAI and a tDAI value. In some aspects, the cDAI and tDAI values ​​may be associated with a joint counting approach, where TRP A and TRP B may coordinate via an ideal backhaul to determine a set of cDAI and tDAI values ​​for a set of DCIs. A description of joint counting for multiple TRP groups is provided below with reference to Figure 4 To provide. In some aspects, the cDAI value and the tDAI value may be associated with a separate counting approach, where each of TRPA and TRP B has corresponding cDAI and tDAI values. For example, the separate counting approach may treat each TRP as a corresponding physical uplink control channel (PUCCH) group by maintaining separate cDAI values ​​and tDAI values ​​for each TRP. In such a scenario, if there is only one serving cell for UE 120, it may not be necessary to include the total DAI value in the DL DCI. Therefore, the TRP may not include the total DAI value in the DL DCI, which can save resources that would otherwise be used by the TRP and the UE to track and process the total DAI value.

[0064] In some aspects, such as in situations where the TRPs use separate counts, the UE 120 may use TRP differentiation to determine which downlink grant (and thus which cDAI and tDAI) belongs to which TRP, and to determine which HARQ codebook may contain the ACK / NACK for a particular DCI. The TRP differentiation may be based at least in part on a configuration (such as using a control resource set identifier or a search space identifier for the downlink grant), or may be implicitly or explicitly indicated in the DCI (such as using an added bit, using an existing field, using a cyclic redundancy check mask, or other examples). Thus, the UE 120 may differentiate between cDAI and tDAI for different TRPs without using a joint counting system, thereby saving backhaul resources between TRPs that would otherwise be used to implement the joint counting system.

[0065] In some aspects, UE 120 may receive an indication from TRP A or B or from another device indicating whether a joint count or a separate count will be used. For example, the indication may include radio resource control configuration information. In some aspects, the indication may be associated with, coupled with, or may be an indication indicating whether a joint HARQ-ACK payload or a separate HARQ-ACK payload will be used. Additionally or alternatively, the indication may be associated with or coupled with an indication to UE 120 regarding whether TRP A and TRP B are associated with an ideal backhaul condition or a non-ideal backhaul condition. For example, an indication indicating whether TRP A and TRP B are associated with an ideal backhaul condition or a non-ideal backhaul condition, or an indication indicating whether a joint HARQ-ACK payload or a separate HARQ-ACK payload will be used may implicitly indicate whether a joint count or a separate count is to be used (such as a joint count is used for an ideal backhaul state and a separate count is used for a non-ideal backhaul condition).

[0066] As shown by reference numeral 325, UE 120 may determine one or more HARQ-ACK payloads (such as one or more codebooks) based at least in part on the cDAI value and the tDAI value. For example, UE 120 may place an ACK or NACK in a joint codebook (when a joint HARQ-ACK payload is to be used) or a separate codebook (when a separate HARQ-ACK payload is to be used) in a position corresponding to the DCI received from TRP A and TRP B. As shown by reference numeral 330, UE 120 may provide HARQ-ACK feedback to TRP A or TRP B (shown by reference numeral 335). For example, the HARQ-ACK feedback may be generated based at least in part on the HARQ-ACK payload or may include the HARQ-ACK payload. In this way, UE 120 can provide an indication of which DCI (or which PDSCH) was unsuccessfully received in a multi-TRP system using joint counting or separate counting.

[0067] Figure 4 4 is a diagram illustrating example 400 of HARQ-ACK feedback determination for multi-TRP communications using a joint tDAI approach. Example 400 includes TRP A and TRP B (such as TRP 305). TRP A and TRP B may be associated with corresponding PDCCH monitoring opportunities (shown here with diagonal shading). For example, TRP A is associated with 2 PDCCH monitoring opportunities per time slot, and TRPB is associated with 1 PDCCH monitoring opportunity per time slot. The DCI received on a specific PDCCH monitoring opportunity is shown with dotted shading occupying a portion of the specific PDCCH monitoring opportunity. In addition, the notation (cDAI, tDAI) is used to show each cDAI value and tDAI value pair. These cDAI value and tDAI value pairs may be received in the DCI and shown at corresponding positions of the physical uplink control channel (PUCCH) scheduled by the DCI.

[0068] As indicated by reference numeral 410, a first cDAI / tDAI pair and a second cDAI / tDAI pair may be associated with the same tDAI value of 2 and cDAI values ​​of 1 and 2, respectively. This may be because, starting from the first PDCCH monitoring opportunity (and because search spaces with the same start time are considered a single PDCCH monitoring opportunity), two total DCIs are cumulatively transmitted by TRP A and TRPB. In addition, the DCI transmitted by TRP A is counted before the DCI transmitted by TRP B. This may be attributed to the counting order assigned to TRP A and TRP B for the purpose of determining cDAI and tDAI values. For example, the order may be based at least in part on a control resource set identifier, a search space identifier, a TRP distinguishing value in the DCI, or other examples. The cDAI may be based at least in part on the cumulative number of instances in which downlink DCI has been transmitted by the gNB, up to the current PDCCH monitoring opportunity, TRP, and serving cell instance. The tDAI may be based at least in part on the total number of instances in which downlink DCI has been transmitted by the gNB, up to the current PDCCH monitoring opportunity. For example, the cumulative number of instances and the total number of instances may be determined based at least in part on an order, such as serving cell first, TRP second, and PDCCH monitoring opportunity third.

[0069] As further shown, UE 120 may successfully receive the first, second, and third DCIs. UE 120 may add an ACK or NACK value to a position in the codebook based at least in part on the result of decoding the PDSCH associated with the DCI corresponding to the position. For example, UE 120 may add an ACK when the PDSCH is successfully decoded and may add a NACK when the PDSCH is not successfully decoded.

[0070] As indicated by reference numeral 420, UE 120 may fail to receive the fourth DCI, as indicated by an X on the fourth DCI. For example, the UE may determine that UE 120 failed to receive the fourth DCI based at least in part on receiving the fifth DCI. UE 120 may determine that UE 120 received DCI with a cDAI value of 3 and a cDAI value of 5, and did not receive DCI with a cDAI value of 4, indicating that the fourth DCI was missed.

[0071] Accordingly, and as indicated by reference numeral 430, UE 120 may send a DCI to the Figure 4The codebook shown in the lower right corner adds a NACK. This may indicate that the PDSCH corresponding to the fourth DCI is not received because the UE 120 is unaware of the location of the PDSCH corresponding to the fourth DCI. The UE 120 may determine this location based at least in part on a joint count, at least in part on a TRP differentiation technique, or at least in part on a rule. For example, the UE 120 may assume that the unreceived DCI is associated with a specific TRP, may assume that the unreceived DCI is associated with a TRP other than the TRP for which the DCI was most recently received, may assume that the unreceived DCI is associated with a TRP other than the TRP for which the DCI was received immediately after the unreceived DCI, or other examples. As further shown, the UE 120 may transmit a physical uplink control channel based at least in part on a codebook. In some aspects, the UE 120 may generate and transmit corresponding codebooks for TRP A and TRP B. Thus, the UE 120 may perform joint counting for multi-TRP communication.

[0072] In some aspects, one serving cell of UE 120 may be configured to receive a single TRP transmission, while another serving cell of UE 120 may be configured to receive multiple TRP transmissions. In this case, in a joint counting approach, the DCI may include tDAI for multiple TRP groups even if there is only a single serving cell. Thus, the same tDAI value may be used in all DCIs across all serving cells and TRPs in the same PDCCH monitoring opportunity.

[0073] Figure 5 is a diagram illustrating an example process 500 performed, for example, by a UE. Example process 500 shows an example in which a UE (such as UE 120) performs operations associated with dynamic HARQ techniques for multi-TRP communication.

[0074] like Figure 5, in some aspects, process 500 may include receiving at least one of: one or more first downlink control information (DCI) transmissions or one or more second DCI transmissions, wherein the one or more first DCI transmissions are associated with a first transmit receive point (TRP) and the one or more second DCI transmissions are associated with a second TRP (block 510). For example, a UE (such as using antenna 252, DEMOD 254, MIMO detector 256, receive processor 258, controller / processor 280, or other examples) may receive at least one of the one or more first DCI transmissions or the one or more second DCI transmissions. In other words, the UE may successfully receive the one or more first DCI transmissions and the one or more second DCI transmissions, or may fail to receive one or more of the one or more first DCI transmissions or the one or more second DCI transmissions. The one or more first DCI transmissions may be associated with a first TRP, and the one or more second DCI transmissions may be associated with a second TRP. For example, the first TRP and the second TRP may be TRPs in a TRP group.

[0075] like Figure 5 As shown in FIG. 5 , in some aspects, process 500 may include determining one or more hybrid automatic repeat request acknowledgement (HARQ-ACK) payloads based at least in part on a counter downlink assignment indicator (DAI) value and a total DAI value for the one or more first DCI transmissions and the one or more second DCI transmissions (block 520). For example, a UE (such as using controller / processor 280 or other examples) may determine one or more HARQ-ACK payloads (such as one or more codebooks) based at least in part on a cDAI value and a tDAI value for the one or more first DCI transmissions and the one or more second DCI transmissions.

[0076] like Figure 5 As shown in , in some aspects, process 500 may include transmitting HARQ-ACK feedback based at least in part on one or more HARQ-ACK payloads (block 530). For example, the UE (such as using controller / processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, or other examples) may provide HARQ-ACK feedback based at least in part on one or more HARQ-ACK payloads. In some aspects, UE 120 may transmit HARQ-ACK feedback to the first TRP or the second TRP.

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

[0078] In a first aspect, the UE may determine whether a DCI transmission associated with a first TRP or a second TRP has not been received based at least in part on a counter DAI value and a total DAI value. HARQ-ACK feedback may identify whether the DCI transmission has not been received. In a second aspect, alone or in combination with the first aspect, determining whether the DCI transmission has not been received further includes determining which of the first TRP and the second TRP transmitted the DCI transmission based at least in part on an ordering of the first TRP and the second TRP, and the ordering is based at least in part on a control resource set identifier or a search space identifier of the DCI transmission. In a third aspect, alone or in combination with one or more of the first and second aspects, determining whether the DCI transmission has not been received further includes determining which of the first TRP and the second TRP transmitted the DCI transmission based at least in part on an ordering of the first TRP and the second TRP. The order may be based at least in part on an indication in the DCI transmission indicating which TRP transmitted the DCI transmission.

[0079] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, the counter DAI value indicates a corresponding counter value for each DCI transmission transmitted by the first TRP and the second TRP at or before the PDCCH monitoring opportunity. In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the total DAI value indicates the total number of DCI transmissions that have been transmitted jointly by the first TRP and the second TRP at or before the PDCCH monitoring opportunity. In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the first TRP and the second TRP are associated with a single serving cell. In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the total DAI value is applicable to all serving cells and TRPs across the first TRP and the second TRP for the PDCCH monitoring opportunity. In an eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the one or more HARQ-ACK payloads include a joint HARQ-ACK payload of the first TRP and the second TRP. In a ninth aspect, either alone or in combination with one or more of the first to eighth aspects, the one or more HARQ-ACK payloads include corresponding HARQ-ACK payloads of the first TRP and the second TRP.

[0080] In the tenth aspect, either alone or in combination with one or more of the first to ninth aspects, the HARQ-ACK feedback indicates that the DCI transmission was not received, and the HARQ-ACK feedback indicates which TRP transmitted the DCI transmission based at least in part on a fixed assumption about which TRP transmitted the DCI transmission. In the eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, the HARQ-ACK feedback indicates that the DCI transmission was not received, and the HARQ-ACK feedback indicates which TRP transmitted the DCI transmission based at least in part on which TRP transmitted an adjacent DCI transmission before or after the DCI transmission. In the twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, the total DAI value includes corresponding total DAI values ​​for the first TRP and the second TRP, and the counter DAI value is maintained separately for the first TRP and the second TRP. In the thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, when the first TRP is associated with a single serving cell, a total DAI value is not provided for the first TRP. In the fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the UE may determine which of the first TRP and the second TRP transmitted a specific DCI transmission among the one or more first DCI transmissions and the one or more second DCI transmissions based at least in part on the TRP differentiation technique. In the fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, the UE may determine which of the first TRP and the second TRP transmitted a specific counter DAI value or a specific total DAI value based at least in part on the TRP differentiation technique.

[0081] In the sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, when the first TRP is associated with a single serving cell, a total DAI value is provided for the first TRP. In the seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, the UE may receive information indicating whether the counter DAI value and the total DAI value are based at least in part on a joint count or a separate count of the first TRP and the second TRP. In the eighteenth aspect, alone or in combination with one or more of the first to seventeenth aspects, the information indicating whether the counter DAI value and the total DAI value are based at least in part on a joint count or a separate count further indicates whether the first TRP and the second TRP are associated with a joint scheduling configuration. In the nineteenth aspect, alone or in combination with one or more of the first to eighteenth aspects, the information indicating whether the counter DAI value and the total DAI value are based at least in part on a joint count or a separate count of the first TRP and the second TRP includes information indicating whether the HARQ-ACK feedback uses a joint HARQ-ACK payload or a separate HARQ-ACK payload for the first TRP and the second TRP. In the twentieth aspect, either alone or in combination with one or more of the first to nineteenth aspects, the UE may receive information indicating whether HARQ-ACK feedback uses a joint HARQ-ACK payload or separate HARQ-ACK payloads for the first TRP and the second TRP. In the twenty-first aspect, either alone or in combination with one or more of the first to twentieth aspects, the first TRP and the second TRP are distinguished based at least in part on respective control resource set identifiers of the first TRP and the second TRP.

[0082] although Figure 5 An example block diagram of process 500 is shown, but in some aspects, process 500 may include Figure 5 Additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in the process 500. Additionally or alternatively, two or more blocks of the process 500 may be executed in parallel.

[0083] As used herein, the term "component" is intended to be broadly interpreted as hardware, firmware, or a combination of hardware and software. As used herein, a "processor" is implemented with hardware, firmware, or a combination of hardware and software.

[0084] As used herein, a phrase referring to "at least one" of a list of items refers to any combination of those items, including single members. As an example, "at least one of a, b, or c" is intended to cover: a, b, c, ab, ac, bc, and abc.

[0085] The various illustrative logics, logic blocks, modules, circuits, and algorithmic processes described in conjunction with the aspects disclosed herein may be implemented as electronic hardware, computer software, or a combination of the two. This interchangeability of hardware and software has been generally described in terms of their functionality and illustrated in the various illustrative components, blocks, modules, circuits, and processes described above. Whether such functionality is implemented in hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0086] The hardware and data processing apparatus for implementing the various illustrative logics, logic blocks, modules, and circuits described in conjunction with the aspects disclosed herein may be implemented or executed with a general purpose single-chip or multi-chip processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (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, or any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in cooperation with a DSP core, or any other such configuration. In some aspects, specific processes and methods may be performed by circuit systems dedicated to a given function.

[0087] In one or more aspects, the functions described may be implemented in hardware, digital electronic circuitry, computer software, firmware (including the structures disclosed in this specification and their structural equivalents), or in any combination thereof. Implementations of the subject matter described in this specification may also be implemented as one or more computer programs, i.e., one or more modules of computer program instructions encoded on a computer storage medium for execution by a data processing apparatus or for controlling the operation of a data processing apparatus.

[0088] If implemented in software, each function can be stored on a computer-readable medium or transmitted therethrough as one or more instructions or codes. The process of the method or algorithm disclosed herein can be implemented in a processor executable software module that can reside on a computer-readable medium. Computer-readable media include both computer storage media and communication media, including any medium that can be implemented to transfer a computer program from one place to another. Storage media can be any available medium that can be accessed by a computer. As an example and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage or other magnetic storage devices, or any other medium that can be used to store the desired program code in the form of an instruction or data structure and can be accessed by a computer. Any connection may also be appropriately referred to as a computer-readable medium. As used herein, "disk" and "disc" include compact discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), floppy disks and blue-ray discs, wherein disks often reproduce data magnetically and discs reproduce data optically with lasers. The above combination should also be included in the scope of computer-readable media. Additionally, the operations of a method or algorithm may reside as one or any combination or set of codes and instructions on a machine-readable medium and a computer-readable medium, which may be incorporated into a computer program product.

[0089] Various modifications to the aspects described in this disclosure may be apparent to those skilled in the art, and the universal principles defined herein may be applied to other aspects without departing from the spirit or scope of the disclosure. Thus, the claims are not intended to be limited to the aspects shown herein, but should be granted the broadest scope consistent with the disclosure, the principles and novel features disclosed herein.

[0090] In addition, one of ordinary skill in the art will readily appreciate that the terms "upper" and "lower / lower" are sometimes used for convenience in describing the drawings and indicate relative positions corresponding to the orientation of the drawings on a correctly oriented page, and may not reflect the actual orientation of any device as implemented.

[0091] Certain features described in this specification in the context of separate aspects may also be implemented in combination in a single aspect. Conversely, various features described in the context of a single aspect may also be implemented in multiple aspects separately or in any suitable subcombination. Furthermore, while features may be described above as functioning in certain combinations and even initially claimed as such, one or more features from a claimed combination may in some cases be removed from the combination, and a claimed combination may be directed to a subcombination, or a variation of a subcombination.

[0092] Similarly, although operations are depicted in a particular order in the accompanying drawings, this should not be understood as requiring such operations to be performed in the particular order shown or in a sequential order, or to perform all the operations described in order to achieve the desired result. In addition, the accompanying drawings may schematically depict one or more example processes in the form of a flow chart. However, other operations not depicted may be incorporated into the example processes schematically illustrated. For example, one or more additional operations may be performed before, after, simultaneously or between any of the illustrated operations. In some environments, multitasking and parallel processing may be advantageous. In addition, the separation of various system components in the aspects described above should not be understood as requiring such separation in all aspects, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products. Additionally, other aspects also fall within the scope of the appended claims. In some cases, the actions described in the claims may be performed in different orders and still achieve the desired result.

Claims

1. A wireless communication method performed by a user equipment UE, comprising: receiving information indicating whether hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback uses a joint HARQ-ACK payload or separate HARQ-ACK payloads for the first transmission reception point (TRP) and the second TRP; receiving a downlink control information (DCI) transmission associated with the first TRP and a serving cell; as well as The HARQ-ACK feedback is provided based at least in part on whether the joint HARQ-ACK payload is used or the individual HARQ-ACK payload is used and the DCI transmission.

2. The method of claim 1, wherein the DCI is associated with a Physical Downlink Control Channel (PDCCH) for scheduling Physical Downlink Shared Channel (PDSCH) communications, and wherein the HARQ-ACK feedback indicates which PDSCH communications were unsuccessfully received.

3. The method of claim 1, wherein the HARQ-ACK feedback is provided using the joint HARQ-ACK payload, and wherein the joint HARQ-ACK payload is related to the first TRP and the second TRP.

4. The method of claim 1, wherein the HARQ-ACK feedback is provided using the joint HARQ-ACK payload, and wherein the joint HARQ-ACK payload includes a joint codebook corresponding to the DCI received from the first TRP and the second TRP.

5. The method of claim 1, wherein the HARQ-ACK feedback is transmitted using the joint HARQ-ACK payload, and wherein a counter downlink assignment indicator cDAI and a total downlink assignment indicator tDAI are jointly tracked between the first TRP and the second TRP.

6. The method of claim 1, wherein the HARQ-ACK feedback is provided using the separate HARQ-ACK payload, and wherein corresponding separate HARQ-ACK payloads provide HARQ-ACK feedback for corresponding TRPs in the first TRP and the second TRP.

7. The method of claim 1, wherein the HARQ-ACK feedback is provided using the separate HARQ-ACK payload, and wherein the separate HARQ-ACK payload includes separate codebooks corresponding to the DCI received from the first TRP and the second TRP.

8. The method of claim 1, wherein the HARQ-ACK feedback is provided using the separate HARQ-ACK payload, and wherein a counter downlink assignment indicator cDAI and a total downlink assignment indicator tDAI are tracked separately by the first TRP and the second TRP.

9. A user equipment UE for wireless communication, comprising: Memory; as well as one or more processors operatively coupled to the memory, the memory and the one or more processors being configured to: receiving information indicating whether hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback uses a joint HARQ-ACK payload or separate HARQ-ACK payloads for the first transmission reception point (TRP) and the second TRP; receiving a downlink control information (DCI) transmission associated with the first TRP and a serving cell; as well as The HARQ-ACK feedback is provided based at least in part on whether the joint HARQ-ACK payload is used or the individual HARQ-ACK payload is used and the DCI transmission.

10. The UE of claim 9, wherein the DCI is associated with a Physical Downlink Control Channel (PDCCH) for scheduling Physical Downlink Shared Channel (PDSCH) communications, and wherein the HARQ-ACK feedback indicates which PDSCH communications were unsuccessfully received.

11. The UE of claim 9, wherein the HARQ-ACK feedback is provided using the joint HARQ-ACK payload, and wherein the joint HARQ-ACK payload is related to the first TRP and the second TRP.

12. The UE of claim 9, wherein the HARQ-ACK feedback is provided using the joint HARQ-ACK payload, and wherein the joint HARQ-ACK payload includes a joint codebook corresponding to the DCI received from the first TRP and the second TRP.

13. The UE of claim 9, wherein the HARQ-ACK feedback is transmitted using the joint HARQ-ACK payload, and wherein a counter downlink assignment indicator cDAI and a total downlink assignment indicator tDAI are jointly tracked between the first TRP and the second TRP.

14. The UE of claim 9, wherein the HARQ-ACK feedback is provided using the separate HARQ-ACK payload, and wherein corresponding separate HARQ-ACK payloads provide HARQ-ACK feedback for corresponding TRPs in the first TRP and the second TRP.

15. The UE of claim 9, wherein the HARQ-ACK feedback is provided using the separate HARQ-ACK payload, and wherein the separate HARQ-ACK payload includes separate codebooks corresponding to the DCI received from the first TRP and the second TRP.

16. A UE as described in claim 9, wherein the HARQ-ACK feedback is provided using the separate HARQ-ACK payload, and wherein a counter downlink assignment indicator cDAI and a total downlink assignment indicator tDAI are tracked separately by the first TRP and the second TRP.

17. A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising: One or more instructions that, when executed by one or more processors of a user equipment UE, cause the UE to: receiving information indicating whether hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback uses a joint HARQ-ACK payload or separate HARQ-ACK payloads for the first transmission reception point (TRP) and the second TRP; receiving a downlink control information (DCI) transmission associated with the first TRP and a serving cell; as well as The HARQ-ACK feedback is provided based at least in part on whether the joint HARQ-ACK payload is used or the individual HARQ-ACK payload is used and the DCI transmission.

18. The non-transitory computer-readable medium of claim 17, wherein the DCI is associated with a Physical Downlink Control Channel (PDCCH) for scheduling Physical Downlink Shared Channel (PDSCH) communications, and wherein the HARQ-ACK feedback indicates which PDSCH communications were unsuccessfully received.

19. The non-transitory computer-readable medium of claim 17, wherein the HARQ-ACK feedback is provided using the joint HARQ-ACK payload, and wherein the joint HARQ-ACK payload is related to the first TRP and the second TRP.

20. The non-transitory computer-readable medium of claim 17, wherein the HARQ-ACK feedback is provided using the joint HARQ-ACK payload, and wherein the joint HARQ-ACK payload comprises a joint codebook corresponding to the DCI received from the first TRP and the second TRP.

21. A non-transitory computer-readable medium as described in claim 17, wherein the HARQ-ACK feedback is transmitted using the joint HARQ-ACK payload, and wherein a counter downlink assignment indicator cDAI and a total downlink assignment indicator tDAI are jointly tracked between the first TRP and the second TRP.

22. A non-transitory computer-readable medium as described in claim 17, wherein the HARQ-ACK feedback is provided using the separate HARQ-ACK payloads, and wherein corresponding separate HARQ-ACK payloads provide HARQ-ACK feedback for corresponding TRPs in the first TRP and the second TRP.

23. The non-transitory computer-readable medium of claim 17, wherein the HARQ-ACK feedback is provided using the separate HARQ-ACK payload, and wherein the separate HARQ-ACK payload comprises separate codebooks corresponding to the DCI received from the first TRP and the second TRP.

24. A non-transitory computer-readable medium as described in claim 17, wherein the HARQ-ACK feedback is provided using the separate HARQ-ACK payload, and wherein a counter downlink assignment indicator cDAI and a total downlink assignment indicator tDAI are tracked separately by the first TRP and the second TRP.

25. A device for wireless communication, comprising: means for receiving information indicating whether hybrid automatic repeat request acknowledgement HARQ-ACK feedback uses a joint HARQ-ACK payload or separate HARQ-ACK payloads for the first transmission reception point TRP and the second TRP; means for receiving a downlink control information (DCI) transmission associated with the first TRP and a serving cell; as well as Means for providing the HARQ-ACK feedback based at least in part on whether the joint HARQ-ACK payload is used or the individual HARQ-ACK payload is used and the DCI transmission.

26. The apparatus of claim 25, wherein the DCI is associated with a Physical Downlink Control Channel (PDCCH) for scheduling Physical Downlink Shared Channel (PDSCH) communications, and wherein the HARQ-ACK feedback indicates which PDSCH communications were unsuccessfully received.

27. The apparatus of claim 25, wherein the HARQ-ACK feedback is provided using the joint HARQ-ACK payload, and wherein the joint HARQ-ACK payload is related to the first TRP and the second TRP.

28. The apparatus of claim 25, wherein the HARQ-ACK feedback is provided using the joint HARQ-ACK payload, and wherein the joint HARQ-ACK payload comprises a joint codebook corresponding to the DCI received from the first TRP and the second TRP.

29. The apparatus of claim 25, wherein the HARQ-ACK feedback is transmitted using the joint HARQ-ACK payload, and wherein a counter downlink assignment indicator cDAI and a total downlink assignment indicator tDAI are jointly tracked between the first TRP and the second TRP.

30. The apparatus of claim 25, wherein the HARQ-ACK feedback is provided using the separate HARQ-ACK payloads, and wherein corresponding separate HARQ-ACK payloads provide HARQ-ACK feedback for corresponding TRPs in the first TRP and the second TRP.

31. A wireless communication method performed by a user equipment UE, comprising: receiving radio resource control (RRC) configuration information, the RRC configuration information including an indication of whether hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback uses a joint HARQ-ACK payload or a separate HARQ-ACK payload; receiving one or more downlink control information DCIs associated with a first control resource set CORESET identifier; receiving one or more DCIs associated with a second CORESET identifier; wherein when the RRC configuration information indicates that the HARQ-ACK feedback uses the joint HARQ-ACK payload, transmitting the joint HARQ-ACK payload based on a joint HARQ-ACK codebook for generating HARQ-ACK feedback associated with the first CORESET identifier and the second CORESET identifier; as well as Wherein, when the RRC configuration information indicates that the HARQ-ACK feedback uses the separate HARQ-ACK payload, a first separate HARQ-ACK payload based on a separate HARQ-ACK codebook for generating HARQ-ACK feedback associated with the first CORESET identifier and a second separate HARQ-ACK payload based on a separate HARQ-ACK codebook for generating HARQ-ACK feedback associated with the second CORESET identifier are transmitted.

32. The method of claim 31 , wherein the one or more DCIs associated with the first CORESET identifier include a downlink assignment indicator (DAI) associated with the first CORESET identifier, and wherein the one or more DCIs associated with the second CORESET identifier include a DAI associated with the second CORESET identifier.

33. The method of claim 32, wherein at least one of the DAI associated with the first CORESET identifier or the DAI associated with the second CORESET identifier is associated with a Physical Downlink Control Channel (PDCCH) for scheduling Physical Downlink Shared Channel (PDSCH) communications.

34. The method of claim 33, wherein the HARQ-ACK feedback indicates which PDSCH communications were unsuccessfully received.

35. The method of claim 32, wherein at least one of the DAI associated with the first CORESET identifier or the DAI associated with the second CORESET identifier comprises a counter downlink assignment indicator (cDAI).

36. The method of claim 32, wherein at least one of the DAI associated with the first CORESET identifier or the DAI associated with the second CORESET identifier comprises a total downlink assignment indicator, tDAI.

37. The method of claim 32, wherein when the RRC configuration information indicates that the HARQ-ACK feedback uses the joint HARQ-ACK payload, the DAI associated with the first CORESET identifier and the DAI associated with the second CORESET identifier are jointly tracked.

38. The method of claim 37, wherein the DAI associated with the first CORESET identifier and the DAI associated with the second CORESET identifier are counted in an order based on the first CORESET identifier and the second CORESET identifier.

39. The method of claim 32, wherein when the RRC configuration information indicates that the HARQ-ACK feedback uses the separate HARQ-ACK payload, the DAI associated with the first CORESET identifier and the DAI associated with the second CORESET identifier are tracked separately.

40. A user equipment UE for wireless communication, comprising: Memory; as well as one or more processors coupled to the memory, the memory and the one or more processors being configured to: receiving radio resource control (RRC) configuration information, the RRC configuration information including an indication of whether hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback uses a joint HARQ-ACK payload or a separate HARQ-ACK payload; receiving one or more downlink control information DCIs associated with a first control resource set CORESET identifier; receiving one or more DCIs associated with a second CORESET identifier; wherein when the RRC configuration information indicates that the HARQ-ACK feedback uses the joint HARQ-ACK payload, transmitting the joint HARQ-ACK payload based on a joint HARQ-ACK codebook for generating HARQ-ACK feedback associated with the first CORESET identifier and the second CORESET identifier; as well as Wherein, when the RRC configuration information indicates that the HARQ-ACK feedback uses the separate HARQ-ACK payload, a first separate HARQ-ACK payload based on a separate HARQ-ACK codebook for generating HARQ-ACK feedback associated with the first CORESET identifier and a second separate HARQ-ACK payload based on a separate HARQ-ACK codebook for generating HARQ-ACK feedback associated with the second CORESET identifier are transmitted.

41. The UE of claim 40, wherein the one or more DCIs associated with the first CORESET identifier include a downlink assignment indicator (DAI) associated with the first CORESET identifier, and wherein the one or more DCIs associated with the second CORESET identifier include a DAI associated with the second CORESET identifier.

42. The UE of claim 41, wherein at least one of the DAI associated with the first CORESET identifier or the DAI associated with the second CORESET identifier is associated with a physical downlink control channel (PDCCH) for scheduling physical downlink shared channel (PDSCH) communications.

43. The UE of claim 42, wherein the HARQ-ACK feedback indicates which PDSCH communications were unsuccessfully received.

44. The UE of claim 41, wherein at least one of the DAI associated with the first CORESET identifier or the DAI associated with the second CORESET identifier comprises a counter downlink assignment indicator (cDAI).

45. The UE of claim 41, wherein at least one of the DAI associated with the first CORESET identifier or the DAI associated with the second CORESET identifier comprises a total downlink assignment indicator, tDAI.

46. ​​The UE of claim 41, wherein when the RRC configuration information indicates that the HARQ-ACK feedback uses the joint HARQ-ACK payload, the DAI associated with the first CORESET identifier and the DAI associated with the second CORESET identifier are jointly tracked.

47. The UE of claim 46, wherein the DAI associated with the first CORESET identifier and the DAI associated with the second CORESET identifier are counted in an order based on the first CORESET identifier and the second CORESET identifier.

48. The UE of claim 41, wherein when the RRC configuration information indicates that the HARQ-ACK feedback uses the separate HARQ-ACK payload, the DAI associated with the first CORESET identifier and the DAI associated with the second CORESET identifier are tracked separately.

49. A non-transitory computer-readable medium storing one or more instructions for wireless communication, the one or more instructions comprising: One or more instructions that, when executed by one or more processors of a user equipment UE, cause the one or more processors to perform the following operations: receiving radio resource control (RRC) configuration information, the RRC configuration information including an indication of whether hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback uses a joint HARQ-ACK payload or a separate HARQ-ACK payload; receiving one or more downlink control information DCIs associated with a first control resource set CORESET identifier; receiving one or more DCIs associated with a second CORESET identifier; wherein when the RRC configuration information indicates that the HARQ-ACK feedback uses the joint HARQ-ACK payload, transmitting the joint HARQ-ACK payload based on a joint HARQ-ACK codebook for generating HARQ-ACK feedback associated with the first CORESET identifier and the second CORESET identifier; as well as Wherein, when the RRC configuration information indicates that the HARQ-ACK feedback uses the separate HARQ-ACK payload, a first separate HARQ-ACK payload based on a separate HARQ-ACK codebook for generating HARQ-ACK feedback associated with the first CORESET identifier and a second separate HARQ-ACK payload based on a separate HARQ-ACK codebook for generating HARQ-ACK feedback associated with the second CORESET identifier are transmitted.

50. The non-transitory computer-readable medium of claim 49, wherein the one or more DCIs associated with the first CORESET identifier include a downlink assignment indicator (DAI) associated with the first CORESET identifier, and wherein the one or more DCIs associated with the second CORESET identifier include a DAI associated with the second CORESET identifier.

51. The non-transitory computer-readable medium of claim 50, wherein at least one of the DAI associated with the first CORESET identifier or the DAI associated with the second CORESET identifier is associated with a Physical Downlink Control Channel (PDCCH) for scheduling Physical Downlink Shared Channel (PDSCH) communications.

52. The non-transitory computer-readable medium of claim 51, wherein the HARQ-ACK feedback indicates which PDSCH communications were unsuccessfully received.

53. The non-transitory computer-readable medium of claim 50, wherein at least one of the DAI associated with the first CORESET identifier or the DAI associated with the second CORESET identifier comprises a counter downlink assignment indicator (cDAI).

54. The non-transitory computer-readable medium of claim 50, wherein at least one of the DAI associated with the first CORESET identifier or the DAI associated with the second CORESET identifier comprises a total downlink assignment indicator, tDAI.

55. The non-transitory computer-readable medium of claim 50, wherein when the RRC configuration information indicates that the HARQ-ACK feedback uses the joint HARQ-ACK payload, a DAI associated with the first CORESET identifier and a DAI associated with the second CORESET identifier are tracked jointly.

56. The non-transitory computer-readable medium of claim 55, wherein the DAI associated with the first CORESET identifier and the DAI associated with the second CORESET identifier are counted in an order based on the first CORESET identifier and the second CORESET identifier.

57. The non-transitory computer-readable medium of claim 50, wherein when the RRC configuration information indicates that the HARQ-ACK feedback uses the separate HARQ-ACK payload, the DAI associated with the first CORESET identifier and the DAI associated with the second CORESET identifier are tracked separately.

58. A device for wireless communication, comprising: A means for receiving a radio resource control (RRC) configuration message, the RRC configuration message including an indication of whether hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback uses a joint HARQ-ACK payload or a separate HARQ-ACK payload; means for receiving one or more downlink control information DCIs associated with a first control resource set CORESET identifier; means for receiving one or more DCIs associated with a second CORESET identifier; wherein when the RRC configuration information indicates that the HARQ-ACK feedback uses the joint HARQ-ACK payload, a means for transmitting the joint HARQ-ACK payload based on a joint HARQ-ACK codebook for generating HARQ-ACK feedback associated with the first CORESET identifier and the second CORESET identifier; as well as wherein when the RRC configuration information indicates that the HARQ-ACK feedback uses the separate HARQ-ACK payload, a means for transmitting a first separate HARQ-ACK payload based on a separate HARQ-ACK codebook for generating HARQ-ACK feedback associated with the first CORESET identifier and a second separate HARQ-ACK payload based on a separate HARQ-ACK codebook for generating HARQ-ACK feedback associated with the second CORESET identifier.

59. The apparatus of claim 58, wherein the one or more DCIs associated with the first CORESET identifier include a downlink assignment indicator (DAI) associated with the first CORESET identifier, and wherein the one or more DCIs associated with the second CORESET identifier include a DAI associated with the second CORESET identifier.

60. The apparatus of claim 59, wherein at least one of the DAI associated with the first CORESET identifier or the DAI associated with the second CORESET identifier is associated with a Physical Downlink Control Channel (PDCCH) for scheduling Physical Downlink Shared Channel (PDSCH) communications.

Images