RU2794194C2 - Hybrid automatic repeat request (harq) dynamic coding chart for multiple transmission and reception point (trp) communications - Google Patents

Abstract

FIELD: wireless communications.

SUBSTANCE: receiving configuration information at the radio resource control (RRC) layer containing an indicator of whether the hybrid automatic repeat request (HARQ-ACK) acknowledgment feedback should use the combined working HARQ-ACK data or separate working HARQ-ACK data. One or more first downlink control information (DCI) transmissions associated with a first control resource set identifier (CORESET) are received. One or more DCI transmissions associated with the second CORESET identifier are received, and when the RRC configuration information indicates that the HARQ-ACK feedback uses the combined HARQ-ACK working data, the combined HARQ-ACK working data is transmitted based on the combined HARQ -ACK of the encoding table used to generate the HARQ-ACK feedback associated with the first CORESET identifier and the second CORESET identifier.

EFFECT: increase in the throughput and reliability of wireless networks.

30 cl, 5 dwg

Description

Cross-reference to related application

[0001] This patent application claims priority to Provisional Patent Application No. 62/805766, filed February 14, 2019, entitled "DYNAMIC HARQ CODEBOOK FOR MULTI-TRP COMMUNICATION" and U.S. Non-Provisional Patent Application No. 16/783983, filed February 6, 2020, entitled "DYNAMIC HYBRID AUTOMATIC REPEAT REQUEST (HARQ) CODEBOOK FOR MULTI-TRANSMIT RECEIVE POINT (TRP) COMMUNICATION", which are hereby expressly referenced herein.

The field of technology to which the invention belongs

[0002] Aspects of the present disclosure relate generally to wireless communications, and more specifically to technologies for dynamic hybrid automatic repeat request (HARQ) codebook for multi-reception point (TRP) communication.

State of the art

[0003] Wireless communication systems are widely deployed to provide various communication services such as telephony, video, data, messaging, and broadcasting. Exemplary wireless communication systems may use multiple access technologies capable of supporting communication with multiple users by sharing available system resources (such as bandwidth, transmit power, or further 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), single carrier frequency division multiple access (SC-FDMA) and synchronized time and code division multiple access (TD-SCDMA) and Long Term Evolution (LTE) systems . The LTE/LTE-Advanced standard is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) based mobile communication standard published through the 3rd Generation Partnership Project (3GPP).

[0004] A wireless communication network may include a certain number of base stations (BS) that can communicate for a certain number of user equipments (UEs). A user equipment (UE) may communicate with a base station (BS) via a downlink (DL) and an uplink (UL). Downlink DL (or forward link) refers to the link from the BS to the UE, and UL (or reverse link) refers to the link from the UE to the BS. As described in more detail herein, a BS may be referred to as a Node B, gNB, Access Point (AP), Radio Head, Receiving Point (TRP), New Radio Standard (NR) BS, 5G Node B, or further examples.

[0005] The above multiple access technologies are adapted in various communication standards in order to provide a common protocol that allows different subscriber devices to exchange data at a city, national, regional, and even global level. The new radio standard (NR), which may also be referred to as 5G, is a set of improvements to the LTE mobile device standard published through the 3rd Generation Partnership Project (3GPP). NR is designed to better support mobile broadband Internet access by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and better integrating with other open standards using cyclic orthogonal frequency division multiplexing (OFDM). Prefix (CP) (CP-OFDM) in DL, using CP-OFDM or SC-FDM (also known as Discrete Fourier Transform Spreading OFDM (DFT-s-OFDM)) in UL, and shaping support radiation patterns, multi-input multiple-output (MIMO) antenna technology, and carrier aggregation. However, as the demand for mobile broadband continues to grow, there is a need to further improve LTE and NR technologies.

The essence of the invention

[0006] The systems, methods, and devices of this disclosure have several innovative aspects, none of which are solely responsible for the required attributes disclosed herein.

[0007] One innovative aspect of the subject matter described in this disclosure may be implemented in a wireless communication method implemented by a user equipment (UE). The method may include 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 the first receiving point -transmissions (TRP) and one or more second DCI transmissions are associated with a second TRP, and wherein one or more first DCI transmissions and one or more second DCI transmissions are associated with a monitoring period of a physical downlink control channel (PDCCH); determining one or more hybrid automatic repeat request (HARQ-ACK) acknowledgment payloads based at least in part on calculated downlink assignment indicator (DAI) values and the total DAI values of one or more first DCI transmissions and one or more second DCI transmissions; and transmitting feedback on the HARQ-ACK based at least in part on the one or more payload HARQ-ACK data.

[0008] In some implementations, the method may include determining whether a DCI transmission associated with a first TRP or a second TRP has been received or not received based at least in part on the calculated DAI values and the total DAI values, and vice versa. communication over the HARQ-ACK may either not be received or a DCI transmission received.

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

[0010] In some implementations, the method may include determining which TRP, of the first TRP and the second TRP, is transmitting the DCI transmission at least in part based on the order of the first TRP and the second TRP, the order being based at least at least partially on an indicator, in the DCI transmission, of which TRP is transmitting the DCI transmission.

[0011] In some implementations, the DAI counts indicate the respective counts of each DCI transmission transmitted by the first TRP and the second TRP at or before the PDCCH monitoring period. In some implementations, the total DAI values indicate the total number of DCI transmissions that are collectively transmitted by the first TRP and the second TRP at or before the PDCCH monitoring period. In some implementations, the first TRP and the second TRP are associated with the same serving cell. In some implementations, common DAI values are applied to all serving cells and TRPs, from the first TRP and the second TRP, during the PDCCH monitoring period.

[0012] In some implementations, one or more payload HARQ-ACK data includes the combined payload HARQ-ACK data for the first TRP and the second TRP. In some implementations, the one or more payload HARQ-ACK data includes corresponding payload HARQ-ACK data for the first TRP and the second TRP. In some implementations, the HARQ-ACK feedback indicates that a DCI transmission was not received, and the HARQ-ACK feedback indicates which TRP is transmitting the DCI transmission, based at least in part on a fixed assumption as to whether which TRP is transmitting the DCI transmission. In some implementations, the HARQ-ACK feedback indicates that a DCI transmission was not received, and the HARQ-ACK feedback indicates which TRP is transmitting a DCI transmission based at least in part on which TRP is transmitting an adjacent DCI transmission before or after DCI transmission.

[0013] In some implementations, the total DAI values include the respective total DAI values for the first TRP and the second TRP, and the calculated DAI values are maintained separately for the first TRP and the second TRP. In some implementations, when the UE is configured with a single serving cell, common DAI values are 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 TRP, from a first TRP and a second TRP, is transmitting a particular DCI transmission, from one or more first DCI transmissions, or from one or more second DCI transmissions of at least partly based on TRP differentiation technology. In some implementations, the method may include determining which TRP, from the first TRP and the second TRP, is transmitting a specific DAI count or a specific total DAI value based at least in part on TRP differentiation technology. In some implementations, when the UE is configured with one serving cell, common DAI values are 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 counted DAI values and the total DAI values are based at least in part on a combined count or a separate count for the first TRP and the second TRP. In some implementations, information indicating whether the counted DAI values and the total DAI values are based at least in part on a combined count or a separate count further indicates whether or not the first TRP and second TRP are associated with the combined scheduling configuration. In some implementations, information indicating whether the counted DAI values and the total DAI values are based at least in part on the combined count or separate count for the first TRP and the second TRP includes information indicating whether feedback is used on HARQ-ACK combined working HARQ-ACK data or separate working HARQ-ACK data for the first TRP and the second TRP. In some implementations, the method may include receiving information indicating whether the HARQ-ACK feedback uses the combined HARQ-ACK payload data or separate HARQ-ACK payload data for the first TRP and the second TRP. In some implementations, the first TRP and the second TRP are distinguished at least in part based on the respective control resource set identifiers of the first TRP and the second TRP.

[0015] Another innovative aspect of the subject matter described in this disclosure may be implemented at a UE for wireless communication. The UE may include a storage device and one or more processors operatively coupled to the storage device. The memory and one or more processors may be configured 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 the first TRP. , and one or more second DCI transmissions are associated with the second TRP, and wherein one or more first DCI transmissions and one or more second DCI transmissions are associated with the PDCCH monitoring period; determine one or more operational HARQ-ACK data based at least in part on the calculated DAI values and the total DAI values of one or more first DCI transmissions and one or more second DCI transmissions; and deduce feedback on the HARQ-ACK based at least in part on the one or more operational HARQ-ACK data. In some aspects, the UE may perform or implement any one or more of the aspects described in connection with the method, above or elsewhere in this document.

[0016] Yet another innovative aspect of the subject matter described in this disclosure may be implemented in a non-volatile computer-readable medium that stores one or more instructions for wireless communication. One or more instructions, when executed by one or more UE processors, may cause 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 one or more second DCI transmissions are associated with a second TRP, and wherein one or more first DCI transmissions and one or more second DCI transmissions are associated with a PDCCH monitoring period; determine one or more operational HARQ-ACK data based at least in part on the calculated DAI values and the total DAI values of one or more first DCI transmissions and one or more second DCI transmissions; and provide feedback on the HARQ-ACK based at least in part on the one or more working HARQ-ACK data. In some aspects, a non-volatile computer-readable medium may implement any one or more of the aspects described in connection with the method, above or elsewhere herein.

[0017] Yet another innovative aspect of the subject matter described in this disclosure may be implemented in wireless communications equipment. The equipment may include means 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 the first TRP, and one or more second DCI transmissions are associated with a second TRP, and wherein one or more first DCI transmissions and one or more second DCI transmissions are associated with a PDCCH monitoring period; means for determining one or more operational HARQ-ACK data based at least in part on the calculated DAI values and the total DAI values of one or more first DCI transmissions and one or more second DCI transmissions; and means for feedback on the HARQ-ACK based at least in part on the one or more payload HARQ-ACK data. In some aspects, the equipment may perform or implement any one or more of the aspects described in connection with the method, above or elsewhere in this document.

[0018] Aspects generally include the method, equipment, system, computer program product, non-volatile computer-readable medium, user equipment, base station, point of reception and transmission, wireless communication device, and processing system actually described herein with reference and illustrated by means of the accompanying drawings.

[0019] Details of one or more implementations of the subject matter described in this disclosure are set forth in the accompanying drawings and in the description below. Other features, aspects and advantages should become apparent from the description, drawings and 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] FIG. 1 is a block diagram conceptually illustrating an example of a wireless communication network.

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

[0022] FIG. 3 is a diagram illustrating an example of using Hybrid Automatic Repeat Request (HARQ) dynamic coding tables for multi-receiving-receiving-point (TRP) communication.

[0023] FIG. 4 is a diagram illustrating an example of determining HARQ-ACK feedback for communicating with multiple TRPs using a combined approach based on common downlink assignment indicators.

[0024] FIG. 5 is a diagram illustrating an exemplary process performed by, for example, a subscriber unit.

[0025] Like reference numerals and designations throughout the various drawings indicate like elements.

Detailed description of the invention

[0026] The following description is directed to specific implementations for the purposes of describing innovative aspects of this disclosure. However, those skilled in the art will recognize that the ideas in this document may be applied in a variety of different ways. Some examples in this disclosure are based on wireless and wired communication based on a local area network (LAN) according to the Institute of Electrical and Electronics Engineers (IEEE) 802.11 wireless standards, the IEEE 802.3 Ethernet standards, and the IEEE Power Line Communications (PLC) standards. 1901. However, the described implementations may be implemented in any device, system, or network that is capable of transmitting and receiving RF signals in accordance with any of the wireless communication standards, including any of the IEEE 802.11 standards, ^Bluetooth® _is a multi-access standard with Code Division Multiple Access (CDMA), Standard, Frequency Division Multiple Access (FDMA), Standard, Time Division Multiple Access (TDMA), Global System for Mobile Communications (GSM), Standard, GSM/Common Packet Service Enhanced Data Environment (EDGE) standard, Terrestrial Trunking System (TETRA) based standard, Wideband CDMA (W-CDMA) based standard, High Speed Packet Data (EV- DO), 1xEV-DO Standard, EV-DO Standard Version A, EV-DO Standard Version B, High Speed Packet Access (HSPA) Based Standard, High Speed Downlink Packet Access (HSDPA) Based Standard, High Speed Packet Access (HSDPA) Based Standard Uplink Packet Access (HSUPA), Enhanced High Speed Packet Access (HSPA+), Long Term Evolution (LTE), AMPS or other known signals that are used to exchange data in a wireless network, cellular network or networks based on the Internet of Things (IoT), for example, in systems using 3G, 4G or 5G or additional technology implementations.

[0027] The hybrid automatic repeat request (HARQ) acknowledgment (ACK) system provides a mechanism for the UE to provide feedback indicating whether or not certain transmissions have been received by the UE. For example, the UE may provide HARQ feedback indicating an ACK value when a transmission is received by the UE, and may provide HARQ feedback (also referred to as "HARQ-ACK feedback") indicating a negative reception (NACK) value when the transmission is not received by the UE or is not received successfully. The HARQ-ACK feedback may use a semi-static configuration, in which the UE uses a configured or preset size for the HARQ feedback (or for the HARQ codebook used to generate the HARQ feedback), or a dynamic configuration, in which the UE determines the size of the HARQ feedback or HARQ codebook. Some of the technologies and equipment described herein refer to a dynamic HARQ-ACK system, although the technologies and equipment 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 determine the HARQ feedback using the HARQ codebook. For example, the UE may determine whether or not a transmission set has been successfully received, may add ACKs or NACKs to the codebook in a specific order to indicate which transmissions of the transmission set have been successfully received, and may generate HARQ feedback using the codebook.

[0029] As one example, the UE may determine whether or not downlink control information (DCI) and corresponding data transmissions are received successfully, and may provide HARQ feedback indicating which DCI and corresponding data transmissions are received successfully. In this case, the UE may determine the HARQ codebook based at least in part on DCI Physical Downlink Control Channel (PDCCH) monitoring periods and Downlink Assignment Indicators (DL) (DAI) associated with the DCI.

[0030] For example, the PDCCH monitoring periods may be based at least in part on the configurations of different sets of search spaces in different cells. The UE may use a union of PDCCH monitoring periods across all active portions of the DL bandwidth (BWP) of configured serving cells ordered in ascending order of the start time of the set of search spaces associated with the PDCCH monitoring period. If two sets of search spaces are associated with the same start time, the two sets of search spaces may be counted as one PDCCH monitoring period.

[0031] The UE may receive DAI in the DCI (eg, in a downlink grant associated with the DCI). DAI may include calculated DAI (sometimes abbreviated as "cDAI") and total DAI (sometimes abbreviated as "tDAI"). The CDAI may indicate the cumulative number of pairs from the serving cell and the PDCCH monitoring period in which the DCI DLs are sent by the base station up to the current serving cell and the current PDCCH monitoring period. TDAI may be used when multiple serving cells are present, such as in carrier aggregation. The TDAI may indicate the total number of serving cells and PDCCH monitoring periods in which the DCI DL is transmitted by the base station up to the current PDCCH monitoring period. Thus, the same tDAI monitoring value can be used for all DCIs in the same PDCCH monitoring period. This provides protection against missing the DCI corresponding to the last serving cell in a particular PDCCH monitoring period, because tDAI needs to inform the UE that another DCI is expected relative to what was received according to cDAI. CDAI and tDAI for a particular DCI are expressed herein as {cDAI, tDAI} or (cDAI, tDAI).

[0032] If the DCI DL is not skipped, then the ACK/NACKs corresponding to the received PDSCH may be placed in the codebook in the same order as the cDAI. If the DCI DL is skipped, then the NACK may be placed in the codebook at the position corresponding to the cDAI of the skipped DCI DL. The UE may determine whether or not a DL DCI is skipped by comparing successive cDAI values (eg, cDAI values of 0 then 1 then 3 may indicate that a DCI with a cDAI value of 2 is skipped), or by comparing tDAI and cDAI of all DCIs in a given PDCCH monitoring period. 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 is missing and may generate HARQ feedback based at least in part on cDAI and tDAI.

[0033] Some wireless communication systems may use a multi-receive-receive point (TRP) transmission technique, where multiple TRPs (either multiple antenna panels or multiple antenna sub-panels) perform identical transmission or corresponding transmissions. In such a case, each TRP may provide a corresponding DCI to schedule the corresponding codeword or transmission from each TRP. It may be desirable to provide feedback on the HARQ-ACK for a multi-TRP deployment such that the TRP (or the base station associated with the TRP) can determine when a DCI is unsuccessfully received. However, it may be difficult to perform HARQ-ACK feedback for communication with multiple TRPs. For example, different TRPs may be associated with different backhaul conditions and there may be differences in the HARQ-ACK feedback process for the combined traffic data (for which the HARQ-ACK feedback for a group of multiple TRPs is relevant for all TRPs from a group of multiple TRPs) versus individual payloads (for which HARQ-ACK feedback for a group of multiple TRPs is provided using the corresponding payload HARQ-ACKs for each TRP from a group of multiple TRPs).

[0034] Some of the technologies and equipment described herein provide a multi-TRP approach for HARQ-ACK feedback using cDAI and tDAI. For example, some of the technologies and equipment described herein may provide a joint scoring method in which cDAI and tDAI are implemented and tracked jointly between TRPs from a group of multiple TRPs. It can be useful in an ideal backhaul scenario where a group of multiple TRPs are collectively scheduled, and can be more reliable with respect to errors than the separate counting method. For example, cDAI may indicate the cumulative number of triples from the serving cell, TRP, and PDCCH monitoring period in which the DCI DL is sent by the base station, up to triples from the current serving cell, TRP, and PDCCH monitoring period three times. A triple of a serving cell, a TRP, and a PDCCH monitoring period three times may mean information that identifies a combination of a serving cell, a TRP, and a PDCCH monitoring period. For example, given the set of serving cells 1 and 2, TRPs A and B, and PDCCH monitoring periods X and Y, possible triples include [X 1 A], [X 2 A], [1 X B], [2 X B] , [1 A Y], [2 A Y], [1 B Y] and [2 B Y], for a total of 8 triplets. TDAI may indicate the total number of such triplets in which DL DCIs are transmitted by the base station up to the current PDCCH monitoring period. These triplets can be placed in any order. A more detailed description of the cDAI and tDAI scoring approaches is provided in connection with FIG. 4. Some of the technologies and equipment described in this document may provide a separate scoring method in which cDAI and tDAI are implemented and tracked separately by respective TRPs from a group of multiple TRPs. It can be useful for ideal and non-ideal backhaul scenarios.

[0035] Specific implementations of the subject matter described in this disclosure may be implemented to realize one or more of the following potential benefits. Some implementations of the subject matter may improve the throughput and reliability of wireless networks, in particular wireless networks using multiple TRP deployments. In addition, some implementations described herein may improve the reliability of HARQ-ACK feedback and reduce the communication inefficiency in a multi-TRP downlink. Additionally, some implementations described herein may provide HARQ-ACK feedback regardless of whether a multi-TRP group is associated with an ideal backhaul or a non-ideal backhaul, thereby increasing the multi-TRP group versatility and possibly weakening implementation requirements for groups of multiple TRPs.

[0036] The following describes in detail various aspects of the disclosure with reference to the accompanying drawings. However, this disclosure may be implemented in a variety of different forms and should not be construed as being limited to any particular structure or function presented in this disclosure. Rather, these aspects are provided in such a manner that this disclosure is comprehensive and complete and fully conveys the scope of the disclosure to those skilled in the art. Based on the teachings herein, those skilled in the art will appreciate that the scope of the disclosure is intended to cover any aspect of the disclosure disclosed herein, whether implemented independently or combined with any other aspect of the disclosure. For example, the equipment may be implemented or the method may be practiced using any number of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover such equipment or method that is practiced using other structure, functionality, or structure and functionality in addition to or in addition to the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed in this document may be implemented through one or more elements of the claims.

[0037] The following are several aspects of communication systems in relation to various types of equipment and technologies. This equipment and technology is described in the detailed description below and illustrated in the accompanying drawings through various blocks, modules, components, circuits, steps, processes, algorithms, and additional examples (collectively referred to as "elements"). These elements may be implemented using hardware, software, or combinations of the foregoing. Whether these elements are implemented as hardware or software depends on the particular application and design constraints imposed by the overall system.

[0038] It should be noted that while aspects may be described herein using terminology commonly associated with 3G or 4G wireless technologies, aspects of the present disclosure may apply to other generations of communication systems, such as 5G/NR and higher.

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

[0040] The BS may provide communication coverage for a macro cell, pico cell, femto cell, or other type of cell. A macro cell may cover a relatively large geographic area (eg, several kilometers in radius) and may allow unrestricted access by a UE with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE with a service subscription. A femtocell may cover a relatively small geographic area (eg, a home) and may allow limited access by UEs having an association with the femtocell (eg, 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 home BS. In the example shown in FIG. 1, 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 (eg, three) cells. The terms "eNB", "base station", "NR BS", "gNB", "TRP", "AP", "Node B", "5G NB", and "cell" may be used interchangeably in this document.

[0041] In some aspects, the cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of the mobile BS. In some aspects, BSs may interconnect with each other or with one or more other BSs or network nodes (not shown) in wireless network 100 through various types of backhaul interfaces, such as through a direct physical connection, a virtual network, or further examples with using any suitable transport network.

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

[0043] Wireless network 100 may be a heterogeneous network that includes various types of BSs, such as macro BSs, pico BSs, femto BSs, relay BSs, or further 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, macro BSs may have a high transmit power level (eg, 5-40 W), while , femto BS, and relay BSs may have lower transmit power levels (eg, 0.1-2 W).

[0044] Network controller 130 may connect to a set of BSs and may provide coordination and control for these BSs. The network controller 130 may communicate with the BS through a backhaul. The BSs may also communicate with each other, for example, directly or indirectly via a wireless or wired backhaul.

[0045] UE 120 (eg, 120a, 120b, 120c) may be distributed throughout wireless network 100, and each UE may be fixed or mobile. A UE may also be referred to as an access terminal, a terminal, a mobile station, a subscriber unit, a station, or further examples. The UE may be a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless subscriber station (WLL), a tablet computer, a camera, a gaming device, netbook, smartbook, ultrabook, medical device or equipment, biometric sensors/devices, wearable devices (smart watches, smart clothes, smart glasses, smart bracelets, smart jewelry (e.g. smart ring, smart bracelet)), multimedia device (e.g. music or video device or satellite radio device), vehicle component or sensor, smart meters/sensors, industrial manufacturing equipment, Global Positioning System based device, or any other suitable device that is configured to communicate over a wireless or wired medium .

[0046] Some UEs may be considered machine communication (MTC) or enhanced or enhanced machine communication (eMTC) capable UEs. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, counters, monitors, location tags, or further examples that can communicate with a base station, another device (e.g., a remote device), or some other object. A wireless node may provide, for example, connectivity to/to a network (eg, to/to a wide area network such as the Internet or a cellular network) via a wired or wireless link. Some UEs may be considered Internet of Things (IoT) capable devices, or may be implemented as NB-IoT (Narrowband Internet of Things) capable devices. Some UEs may be considered terminal user equipment (CPEs). UE 120 may be included within a package that contains components of UE 120, such as processor components, storage components, or further examples.

[0047] In general, any number of wireless networks can 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, air interface, or further examples. Frequency may also be referred to as carrier, frequency channel, or further examples. Each frequency can support one 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 (shown as UE 120a and UE 120e) can communicate directly using one or more sidelink channels (without using base station 110 as an intermediary to communicate with each other ). For example, UE 120 may communicate using peer-to-peer (P2P), device-to-device (D2D), vehicle-to-anything (V2X) protocol (which may include vehicle-to-vehicle (V2V) , Vehicle to Infrastructure (V2I) protocol or more examples), mesh network or more examples. In this case, UE 120 may perform scheduling operations, resource selection operations, or other operations described elsewhere in this document as being performed by base station 110.

[0049] As noted above, FIG. 1 is provided as an example. Other examples may differ from what is described with respect to FIG. 1.

[0050] FIG. 2 shows a block diagram of a design solution 200 for base station 110 and UE 120, which may be one of the base stations and one of the UEs in FIG. 1. Base station 110 may be equipped with T antennas 234a-234t and UE 120 may be equipped with R antennas 252a-252r, with T≥1 and R≥1 in general.

[0051] At base station 110, transmit processor 220 may receive data from data source 212 for one or more UEs, select one or more modulation and coding schemes (MCS) at least in part for each UE based on channel quality indicators ( CQI) received from the UE, process (eg, 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. Transmit processor 220 may also process system information (eg, semi-static resource segmentation information (SRPI) or additional examples) and control information (eg, CQI requests, transmission permissions, upper layer signaling, or additional examples) and provide overhead characters and control characters. Transmit processor 220 may also generate reference symbols for reference signals (eg, cell-specific reference signal (CRS)) and synchronization signals (eg, primary synchronization signal (PSS) and secondary synchronization signal (SSS)). Multiple input multiple output (MIMO) transmit (TX) processor 230 may perform spatial processing (eg, precoding) on data symbols, control symbols, service symbols, or reference symbols, if applicable, and provide T output symbol streams in T modulators 232a-232t (MOD). Each modulator 232 may process a corresponding output symbol stream (eg, for OFDM or further examples) to obtain an output sample stream. Each modulator 232 can further process (eg, convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. T downlink signals from modulators 232a-232t may be transmitted via T antennas 234a-234t, respectively. According to various aspects, described in more detail below, synchronization signals may be generated with location-based coding to convey additional information.

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

[0053] In the uplink, at UE 120, transmit processor 264 may receive and process data from data source 262 and control information (eg, for messages including RSRP, RSSI, RSRQ, CQI, and more examples) from a controller/ processor 280. Transmitter processor 264 may also generate reference symbols for one or more reference signals. Symbols from transmit processor 264 may be pre-coded by TX MIMO processor 266, if applicable, further processed by modulators 254a-254r (eg, for DFT-s-FDM, OFDM, and more examples) and transmitted to base station 110. At base station 110, uplink signals from UE 120 and other UEs may be received via antennas 234, processed by demodulators 232, detected by MIMO detector 236, if applicable, and further processed by receive processor 238 to obtain decoded data and control information sent by UE 120. Receive processor 238 may provide decoded data to data sink 239 and decoded control information to controller/processor 240. Base station 110 may include communication module 244 and communicate with network controller 130 via communication module 244. The network controller 130 may include a communications module 294, a controller/processor 290, and a storage device 292.

[0054] In some implementations, controller/processor 240 may be a component of a processing system. A processing system can generally mean a system or sequence of machines or components that receives inputs and processes the inputs to form a set of outputs (which can be communicated to other systems or components, such as UE 120). For example, the processing system of UE 120 may mean a system including various other components or sub-components of UE 120.

[0055] The processing system of UE 120 may interact with other components of UE 120 and may process information received from other components (eg, inputs or signals), output information to other components, and so on. For example, a chip or modem of UE 120 may include a processing system, a first interface to receive or receive information, and a second interface to output, transmit or provide information. In some cases, the first interface may mean an interface between a chip or modem processing system and a receiving device such that UE 120 can receive information or input signals and the information can be transmitted to the processing system. In some cases, the second interface may mean an interface between the chip or modem processing system and the transmitter, such that UE 120 can transmit information output from the chip or modem. Those skilled in the art will readily recognize that the second interface may also receive or receive information or inputs, and the first interface may also output, transmit, or provide information.

[0056] Controller/processor 240 of base station 110, controller/processor 280 of UE 120, or any other component(s) of FIG. 2 may perform one or more technologies associated with a dynamic hybrid automatic repeat request (HARQ) codebook for multi-point-of-receive (TRP) communication, as described in more detail elsewhere herein. For example, controller/processor 240 of base station 110, controller/processor 280 of UE 120, or any other component(s) of FIG. 2 may perform or direct operations, such as the process 500 of FIG. 5 or other processes as described in this document. Memories 242 and 282 may store data and program codes for base station 110 and UE 120, respectively. Scheduler 246 may schedule the UE for data transmission on the downlink and/or uplink.

[0057] In some aspects, UE 120 may include means for receiving at least one of the following: one or more first transmissions of downlink control information (DCI) or one or more second DCI transmissions, wherein one or more more than the first DCI transmissions are associated with a first receiving-transmission point (TRP), and one or more second DCI transmissions are associated with the second TRP, and wherein one or more first DCI transmissions and one or more second DCI transmissions are associated with a monitoring period physical downlink control channel (PDCCH); means for determining one or more hybrid automatic repeat request (HARQ-ACK) acknowledgment service data based at least in part on calculated downlink assignment indicator (DAI) values and the total DAI values of one or more first DCIs - gears and one or more second DCI gears; means for transmitting feedback on the HARQ-ACK based at least in part on one or more working HARQ-ACK data; means for determining whether a DCI transmission associated with the first TRP or the second TRP is not received or received based at least in part on the calculated DAI values and the total DAI values; means for determining which TRP, of the first TRP and the second TRP, is transmitting a particular DCI transmission, of one or more first DCI transmissions and one or more second DCI transmissions based at least in part on a TRP differentiation technique; means for determining which TRP, of the first TRP and the second TRP, is transmitting the specific DAI counted value or the specific total DAI value based at least in part on the TRP differentiation technique; means for receiving information indicating whether the counted DAI values and the total DAI values are based at least in part on a combined count or a separate count for the first TRP and the second TRP; means for receiving information indicating whether the HARQ-ACK feedback uses the combined HARQ-ACK payload data or separate HARQ-ACK payload data for the first TRP and the second TRP; or more examples. In some aspects, such means may include one or more components of UE 120 described in connection with FIG. 2.

[0058] FIG. 3 is a diagram illustrating an example 300 of using hybrid automatic repeat request (HARQ) dynamic acknowledgment (ACK) coding tables to communicate with multiple round-trip points (TRPs).

[0059] As shown in FIG. 3, multiple TRPs 305 (shown as TRP A and TRP B) may communicate with the same UE 120 in a coordinated manner (eg, using coordinated multipoint transmissions or additional examples) to improve reliability, increase throughput, or additional examples. The TRPs 305 may coordinate this communication over a backhaul, which may have lower latency or higher throughput when the TRPs 305 are co-located in the identical base station 110 (eg, different antenna arrays of the identical base station 110) or may have greater delay or less throughput 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 delay threshold or a backhaul that allows combined scheduling of TRP A and TRP B. In some other cases, the backhaul may be a non-ideal backhaul, eg, a backhaul with a delay time that cannot meet a threshold or that does not allow federated scheduling.

[0060] TRP A and TRP B may be referred to herein as a group of several TRPs. As used herein, a group of multiple TRPs may mean a set of TRPs that need to communicate with the same UE, a set of TRPs managed as a group by an access node controller, a set of TRPs that transmit the same physical downlink shared channel (PDSCH ), a set of TRPs that transmit a single PDSCH at the same time or at the same time, or more examples.

[0061] TRP may also be referred to as BS, NR BS, Node B, 5G NB, AP, gNB, or some other term, or may be used interchangeably with "cell". In some aspects, multiple TRPs may be included in one BS 110 (eg, using appropriate antenna panels or quasi-collocation relationships). In some aspects, different TRPs may be included in different BS 110. A TRP may use one or more antenna ports. A set of TRPs (eg, TRP A and TRP B) may be configured to separately (eg, using dynamic selection) or collectively (eg, using aggregated transmission) service traffic at UE 120. The TRPs may be coordinated by or interact with through the Access Node Controller (ANC). In some aspects, an interface between TRPs may not be required or present. The TRP may be associated with a top-level identifier, such as a control resource set (base set) identifier. For example, the base set identifier may include, be based at least in part on, or be mapped to an index of the base set pool.

[0062] As shown, the first physical downlink control channel (PDCCH) 310 may schedule communication for TRP A, and the second PDCCH 315 may schedule communication for TRP B. Here, as shown by reference number 320, the communication is a PDSCH, which may be common between TRP A and TRP B, or may be different (eg, different payload data, different modulation and coding schemes, different transmit powers, or different repetition schemes). For example, in the first multi-TRP transmission mode (mode 1), one PDCCH may be used to schedule downlink communication for one PDSCH. In this case, multiple TRPs 305 (here, TRP A and TRP B) may communicate with UE 120 on the same PDSCH. In some aspects, different TRPs 305 may be transmitted in different (eg, non-overlapping) resource block (RB) sets or in different character sets. Additionally or alternatively, different TRPs 305 may transmit using different layers (eg, different multiple input multiple output (MIMO) layers). In some aspects, transmissions across different layers may occur in overlapping resource blocks or in overlapping symbols. As another example, in the second multi-TRP transmission mode (mode 2), multiple PDCCHs may be used to schedule downlink communication for multiple respective PDSCHs (eg, one PDCCH for each PDSCH).

[0063] As shown in more detail, each PDCCH may be associated with a corresponding DCI, and each DCI may be associated with cDAI and tDAI values. In some aspects, the cDAI values and tDAI values may be associated with a pooled counting approach in which TRP A and TRP B may be coordinated across an ideal backhaul to determine cDAI values and tDAI values for a DCI set. A description of the combined count for a group of multiple TRPs is provided in connection with FIG. 4 below. In some aspects, cDAI values and tDAI values may be associated with a single count approach in which TRP A and TRP B have corresponding cDAI and tDAI values. For example, a single count approach can 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 case, if there is only one serving cell for UE 120, it may not be necessary to include a common DAI value in the DCI DL. Thus, the TRP may not include the common DAI value in the DCI DL, which saves TRP and UE resources that would otherwise have to be used to track and process the common DAI value.

[0064] In some aspects, for example, in the case where TRPs use a separate count, UE 120 may use TRP differentiation to determine which downlink grant (and therefore which cDAI and tDAI) belong to which TRP, and determine which HARQ codebook may include ACK/NACK for a particular DCI. The TRP differentiation may be based at least in part on configuration (eg, using a control resource set identifier or a downlink grant search space identifier) or may be implicit or explicit in the DCI (eg, using additional bit, using an existing field, using a CRC mask, or additional examples). Thus, UE 120 can distinguish between cDAI and tDAI of different TRPs without using a joint scoring system, thereby saving the transit of resources between TRPs that would otherwise have to be used in order to implement a joint scoring system.

[0065] In some aspects, UE 120 may receive, from TRP A or B, or from another device, an indication of whether a combined count or a separate count should be used. For example, the indicator may include configuration information at the radio resource control layer. In some aspects, this indicator may be associated or linked, or may be an indication of whether the combined HARQ-ACK payload or separate HARQ-ACK payload is to be used. Additionally or alternatively, this indicator may be associated or associated with an indicator, at UE 120, as to whether TRP A and TRP B are associated with ideal backhaul or non-ideal backhaul conditions. For example, an indicator of whether TRP A and TRP B are associated with ideal backhaul conditions or non-ideal backhaul conditions, or an indicator of whether combined working HARQ-ACK data or separate working HARQ-ACK data should be used, may implicitly indicate whether a pooled or separate scoring should be used (eg, pooled for ideal backhaul conditions and separate scoring for non-ideal backhaul conditions).

[0066] As shown by reference 325, UE 120 may determine one or more operational HARQ-ACK data (eg, one or more codebooks) based at least in part on cDAI values and tDAI values. For example, UE 120 may place ACKs or NACKs at the locations of the combined codebook (when combined HARQ-ACK payload data should be used) or separate codebooks (when separate HARQ-ACK payload data should be used) corresponding to the DCI received from TRP A and TRP B. As shown by reference 330, UE 120 may provide HARQ-ACK feedback (shown by reference 335) in TRP A or TRP B. For example, the HARQ-ACK feedback may be generated at least based at least in part on the HARQ-ACK payload, or may include the HARQ-ACK payload. Thus, UE 120 may provide an indication of which DCIs (or which PDSCHs) are being unsuccessfully received in a multi-TRP system using a combined count or a separate count.

[0067] FIG. 4 is a diagram illustrating an example 400 of determining HARQ-ACK feedback for communicating with multiple TRPs using a combined tDAI-based approach. Example 400 includes TRP A and TRP B (eg, TRP 305). TRP A and TRP B may be associated with respective PDCCH monitoring periods (shown here with diagonal shading). For example, TRP A is associated with 2 PDCCH monitoring periods per slot, and TRP B is associated with 1 PDCCH monitoring period per slot. The DCI received in a specific PDCCH monitoring period is shown with a dotted line occupying a portion of the specific PDCCH monitoring period. In addition, various pairs of cDAI values and tDAI values are shown using the notation (cDAI, tDAI). These pairs of cDAI values and tDAI values may be received in the DCI and are shown in the corresponding location of the Physical Uplink Control Channel (PUCCH) scheduled by the DCI.

[0068] As shown by reference 410, the first cDAI/tDAI pair and the second cDAI/tDAI pair may be associated with an identical tDAI value at 2 and corresponding cDAI values at 1 and 2. This may be because that, from the first PDCCH monitoring period (and since the search spaces are to have the same start time to be considered one PDCCH monitoring period), two common DCIs are cumulatively transmitted by TRP A and TRP B. In addition, the DCI transmitted by TRP A is counted before the DCI transmitted by TRP B. This may be due to the order of counting assigned by TRP A and TRP B for purposes 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 DCI TRP derivation value, or further examples. The CDAI may be based at least in part on the cumulative number of instances in which the downlink DCI is transmitted by the gNB up to the current instance of the PDCCH monitoring period, TRP, and serving cell. The TDAI may be based at least in part on the total number of instances in which the downlink DCI is transmitted by the gNB up to the current PDCCH monitoring period. For example, the cumulative number of instances and the total number of instances may be determined at least in part based on order, eg, based on the order of serving cell first, TRP second, and PDCCH monitoring period third.

[0069] As shown in more detail, UE 120 can successfully receive the first, second, and third DCIs. UE 120 may add an ACK or NACK value to a location in the codebook based at least in part on the decoding result of the PDSCH associated with the DCI corresponding to the location. 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 shown by reference 420, UE 120 may erroneously receive the fourth DCI shown by X over the fourth DCI. For example, the UE may determine that UE 120 was erroneously receiving the fourth DCI based at least in part on receiving the fifth DCI. UE 120 may determine that UE 120 received DCI with cDAI value of 3 and cDAI value of 5 and does not receive DCI with cDAI value of 4, thereby indicating that the fourth DCI is skipped.

[0071] Accordingly, and as shown by reference 430, UE 120 may add NACKs to the codebook shown in the lower right corner of FIG. 4 at a location agreed with DCI. This may indicate that the PDSCH corresponding to the fourth DCI is not received because UE 120 does not know the location of the PDSCH corresponding to the fourth DCI. UE 120 may determine this location based at least in part on a combined count, at least in part on a TRP differentiation technique, or at least in part on a rule. For example, UE 120 may assume that a non-received DCI is associated with a particular TRP, may assume that a non-received DCI is associated with a TRP other than the TRP for which the DCI was last received, may assume that a non-received DCI is associated with a TRP, other than a TRP for which a DCI is accepted immediately after a rejected DCI, or more examples. As shown in more detail, UE 120 may transmit a physical uplink control channel based at least in part on a codebook. In some aspects, UE 120 may generate and transmit corresponding codebooks for TRP A and TRP B. Thus, UE 120 may perform combined counting for communication with multiple TRPs.

[0072] In some aspects, one serving cell of UE 120 may be configured to receive transmissions with a single TRP, while another serving cell of UE 120 may be configured to receive a transmission with multiple TRPs. In this case, in the pooled count approach, DCI may include tDAI for a group of multiple TRPs even if there is one serving cell. Thus, the same tDAI value can be used for all DCIs for all serving cells and TRPs in identical PDCCH monitoring periods.

[0073] FIG. 5 is a diagram illustrating an exemplary process 500 performed by a UE, for example. Exemplary process 500 shows an example in which a UE (eg, UE 120) performs operations associated with dynamic HARQ technology to communicate with multiple TRPs.

[0074] As shown in FIG. 5, in some aspects, process 500 may include 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 DCIs -transmissions are associated with a first transmit-receive point (TRP), and one or more second DCI transmissions are associated with a second TRP (block 510). For example, the UE (eg, using antenna 252, DEMOD 254, MIMO detector 256, receive processor 258, controller/processor 280, or further examples) may receive at least one of one or more first DCI transmissions, or one or more second DCI transmissions. In other words, the UE may successfully receive one or more first DCI transmissions and one or more second DCI transmissions, or may erroneously receive one or more DCI transmissions from one or more first DCI transmissions or one or more second DCI transmissions. . One or more first DCI transmissions may be associated with the first TRP and one or more second DCI transmissions may be associated with the second TRP. For example, the first TRP and the second TRP may belong to a TRP group.

[0075] As shown in FIG. 5, in some aspects, process 500 may include determining one or more hybrid automatic repeat request (HARQ-ACK) acknowledgment data payload based at least in part on calculated downlink assignment indicator (DAI) values. and common DAI values of one or more first DCI transmissions and one or more second DCI transmissions (block 520). For example, the UE (eg, using controller/processor 280 or further examples) may determine one or more working HARQ-ACK data (eg, one or more codebooks) based at least in part on cDAI values and tDAI values of one or more first DCI transmissions and one or more second DCI transmissions.

[0076] As shown in FIG. 5, in some aspects, process 500 may include feedback on a HARQ-ACK based at least in part on one or more payload HARQ-ACK data (block 530). For example, the UE (eg, using controller/processor 280, TX processor 264, TX MIMO processor 266, MOD 254, antenna 252, or further examples) may provide feedback on the HARQ-ACK based at least in part on the or more working HARQ-ACK data. In some aspects, UE 120 may send feedback on the HARQ-ACK in the first TRP or the second TRP.

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

[0078] In a first aspect, the UE may determine whether the DCI transmission associated with the first TRP or the second TRP is not received or received based at least in part on the calculated DAI values and the total DAI values. Feedback on the HARQ-ACK may identify whether a DCI transmission was not received or received. In a second aspect, alone or in combination with the first aspect, determining whether a DCI transmission is not received or received further includes determining which TRP, of the first TRP and the second TRP, is transmitting the DCI transmission at least in part. based on the ordering of the first TRP and the second TRP, and the ordering is based at least in part on the control resource set identifier or 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 a DCI transmission is not received or received further includes determining which TRP, of the first TRP and the second TRP, is transmitting the DCI transmission. based at least in part on the order of the first TRP and the second TRP. The order may be based at least in part on an indicator, in the DCI transmission, of which TRP is transmitting the DCI transmission.

[0079] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the DAI counts indicate the respective counts of each DCI transmission transmitted by the first TRP and the second TRP at or before the PDCCH monitoring period. In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the total DAI values indicate the total number of DCI transmissions that are collectively transmitted by the first TRP and the second TRP in or before the PDCCH monitoring period. In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the first TRP and the second TRP are associated with the same serving cell. In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, common DAI values are applied to all serving cells and TRPs, from the first TRP and the second TRP, during the PDCCH monitoring period. In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the one or more HARQ-ACK payload data includes the combined HARQ-ACK payload data for the first TRP and the second TRP. In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the one or more payload HARQ-ACK data includes corresponding payload HARQ-ACK data for the first TRP and the second TRP.

[0080] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, the HARQ-ACK feedback indicates that a DCI transmission was not received and the HARQ-ACK feedback indicates which TRP is transmitting The DCI transmission is based at least in part on a fixed assumption as to which TRP is transmitting the DCI transmission. In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the HARQ-ACK feedback indicates that a DCI transmission has not been received and the HARQ-ACK feedback indicates which TRP is transmitting the DCI transmission. based at least in part on which TRP transmits the adjacent DCI transmission before or after the DCI transmission. In the twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the total DAI values include the respective total DAI values for the first TRP and the second TRP, and the calculated DAI values are maintained separately for the first TRP and the second TRP. . In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, when the first TRP is associated with one serving cell, common DAI values are not provided for the first TRP. In a fourteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, the UE may determine which TRP, from the first TRP and the second TRP, is transmitting a particular DCI transmission, from one or more of the first DCI transmissions and one or more more than second DCI transmissions based at least in part on TRP differentiation technology. In a fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, the UE may determine which TRP, from the first TRP and the second TRP, transmits a specific DAI count or a specific total DAI value of at least partly based on TRP differentiation technology.

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

[0082] Although FIG. 5 shows exemplary steps of process 500, in some aspects, process 500 may include additional steps, fewer steps, different steps, or differently arranged steps than those illustrated in FIG. 5. Additionally or alternatively, two or more of the steps in process 500 may be performed in parallel.

[0083] As used herein, the term "component" should be construed broadly as hardware, firmware, or a combination of hardware and software. As used herein, a "processor" is implemented in hardware, firmware, or a combination of hardware and software.

[0084] As used herein, a phrase meaning "at least one of" a list of elements means any combination of these elements, including single elements. By way of example, "at least one of: a, b, or c" is intended to cover: a, b, c, a-b, a-c, b-c, and a-b-c.

[0085] The various illustrative logic elements, modules, circuits, and algorithm processes described in connection with the aspects disclosed herein may be implemented as electronic hardware, computer software, or combinations of the foregoing. The interchangeability of hardware and software is generally described in terms of functionality and illustrated in the various illustrative components, blocks, modules, circuits, and processes described above. Whether this functionality is implemented in hardware or software depends on the particular application and structural constraints imposed on the overall system.

[0086] The hardware and data processing equipment used to implement the various illustrative logic elements, blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented or executed using a single or multi-chip processor of a common destination, digital signal processor (DSP), application specific integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic device, discrete logic element or transistor logic, discrete hardware components, or any combination of the foregoing, designed to perform features described in this document. A general purpose processor may be a microprocessor or any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors together with a DSP core, or any other such configuration. In some aspects, specific processes and methods may be implemented through a scheme that is specific to a given function.

[0087] In one or more aspects, the described functions may be implemented in hardware, digital electronic circuitry, computer software, firmware, which includes the structures disclosed in this detailed description and their structural equivalents, or any combination of the foregoing. . Aspects of the subject matter described in this detailed description may also be implemented as one or more computer programs, i. as one or more modules of computer program instructions encoded on computer storage media for executing or controlling the operation of data processing equipment.

[0088] If implemented in software, the functions may be stored or transmitted as one or more instructions or code on a computer-readable medium. The processes of a method or algorithm disclosed herein may be implemented in a processor-executable program module that may reside on a computer-readable medium. Computer-readable media includes both computer storage media and communication media, including any transmission medium that can move a computer program from one place to another. Storage media can be any available media that can be accessed by a computer. By way of example, and not limitation, these computer-readable media may comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage device, magnetic disk storage device or other magnetic storage devices, or any other medium that can be used to in order to store the desired program code in the form of instructions or data structures, and which can be accessed by a computer. Also, any connection may correctly be referred to as a "machine-readable medium". "Disk (disk)" and "disc (disc)", as used herein, include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc. disk, while disks (disk) usually reproduce data magnetically, while disks (disc) usually reproduce data optically using lasers. Combinations of the above should also be included in computer readable media. In addition, the steps of the method or algorithm may reside as one or any combination or set of codes and instructions on a computer-readable medium and a computer-readable medium that may be included in a computer program product.

[0089] Various modifications of the aspects described in this disclosure may become apparent to those skilled in the art, and the general principles set forth herein may apply to other aspects without departing from the spirit or scope of this disclosure. Thus, the claims are not intended to be limited to the aspects shown herein, but are intended to satisfy the broadest scope in accordance with this disclosure, principles, and novel features disclosed herein.

[0090] Additionally, those skilled in the art should appreciate that the terms "top" and "bottom" are sometimes used for ease of description of drawings and indicate relative positions corresponding to drawing orientation on a properly oriented page, and may not reflect a proper implementation. device orientation.

[0091] Certain features that are explained in this detailed description in the context of separate aspects may also be implemented in combination in one aspect. Conversely, various features that are described in the context of one aspect may also be implemented in multiple aspects individually or in any suitable subcombination. In addition, although the features may be described above as operating in certain combinations and even initially claimed in the claims per se, one or more features from the claimed combination may in some cases be excluded from the combination, and the claimed combination may be directed to a subcombination or to change subcombinations.

[0092] Likewise, although the operations are illustrated in the drawings in a particular order, this should not be understood as a requirement that such operations must be performed in the particular order shown, or in sequential order, or that all illustrated operations must be performed in order to achieve desired results. Additionally, the drawings may schematically illustrate one or more exemplary processes in the form of a flow diagram. However, other operations that are not illustrated may be included in the exemplary processes that are schematically illustrated. For example, one or more additional operations may be performed before, after, at the same time, or between any of the illustrated operations. Under certain circumstances, 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 software components and systems may generally be integrated into one software product or bundled into several software products. . Additionally, these and other aspects are within the scope of the appended claims. In some cases, the steps set forth in the claims may be performed in a different order and still achieve the desired results.

Claims (53)

1. A wireless communication method implemented by a user equipment (UE), comprising the steps of: receiving radio resource control (RRC) layer configuration information containing an indicator of whether the hybrid automatic repeat request (HARQ-ACK) acknowledgment feedback should use combined HARQ-ACK payload data or separate HARQ-ACK payload data; receiving one or more first downlink control information (DCI) transmissions associated with a first control resource set identifier (CORESET); receiving one or more DCI transmissions associated with the second CORESET identifier; wherein, when the RRC configuration information indicates that the HARQ-ACK feedback uses the combined HARQ-ACK payload data, the combined HARQ-ACK payload data is transmitted based on the combined HARQ-ACK codebook used to generate the HARQ feedback. -ACK associated with the first CORESET identifier and the second CORESET identifier; wherein, when the RRC configuration information indicates that the HARQ-ACK feedback uses separate HARQ-ACK payload data, the first separate HARQ-ACK payload data is transmitted based on the separate HARQ-ACK codebook used to generate the feedback. a HARQ-ACK associated with the first CORESET ID and a second separate HARQ-ACK payload based on the separate HARQ-ACK codebook used to generate the HARQ-ACK feedback associated with the second CORESET ID. 2. The method of claim 1, wherein at least one or more DCI transmissions associated with the first CORESET includes a downlink assignment indicator (DAI) associated with the first CORESET, and wherein at least at least one or more DCI transmissions associated with the second CORESET includes a DAI indicator associated with the second CORESET. 3. The method of claim 2, wherein at least one of the DAIs associated with the first CORESET or the DAIs associated with the second CORESET is associated with a physical downlink control channel (PDCCH) used for communication scheduling. over a physical downlink shared channel (PDSCH). 4. The method of claim 3, wherein the HARQ-ACK feedback indicates which PDSCH links were unsuccessfully received. 5. The method of claim 2, wherein at least one of the DAIs associated with the first CORESET or the DAIs associated with the second CORESET includes counted downlink assignment indicators (cDAIs). 6. The method of claim 2, wherein at least one of the DAIs associated with the first CORESET or the DAIs associated with the second CORESET includes common downlink assignment indicators (tDAI). 7. The method of claim 2, wherein the DAIs associated with the first CORESET and the DAIs associated with the second CORESET are tracked jointly when the RRC configuration information indicates that the HARQ-ACK feedback uses the combined operational HARQ-ACKs. -data. 8. The method of claim 7, wherein the DAIs associated with the first CORESET and the DAIs associated with the second CORESET are counted in order based on the first CORESET and the second CORESET. 9. The method of claim 2, wherein the DAIs associated with the first CORESET and the DAIs associated with the second CORESET are tracked separately when the RRC configuration information indicates that the HARQ-ACK feedback uses separate operational HARQ-ACKs. -data. 10. Subscriber equipment (UE) for wireless communication, containing: Memory device; And one or more processors coupled to a storage device, wherein the storage device and one or more processors are configured to: receive configuration information at the radio resource control (RRC) level, containing an indicator of whether the hybrid automatic repeat request (HARQ-ACK) acknowledgment feedback should use the combined working HARQ-ACK data or separate working HARQ-ACK data; receive one or more first transmissions of downlink control information (DCI) associated with a first control resource set identifier (CORESET); receive one or more DCI transmissions associated with the second CORESET identifier; wherein, when the RRC configuration information indicates that the HARQ-ACK feedback uses the combined HARQ-ACK payload data, the combined HARQ-ACK payload data is transmitted based on the combined HARQ-ACK codebook used to generate the HARQ feedback. -ACK associated with the first CORESET identifier and the second CORESET identifier; wherein, when the RRC configuration information indicates that the HARQ-ACK feedback uses separate HARQ-ACK payload data, the first separate HARQ-ACK payload data is transmitted based on the separate HARQ-ACK codebook used to generate the feedback. a HARQ-ACK associated with the first CORESET ID and a second separate HARQ-ACK payload based on the separate HARQ-ACK codebook used to generate the HARQ-ACK feedback associated with the second CORESET ID. 11. The user equipment (UE) of claim 10, wherein at least one or more DCI transmissions associated with the first CORESET identifier includes a downlink assignment indicator (DAI) associated with the first CORESET identifier, and wherein at least one or more DCI transmissions associated with the second CORESET includes a DAI associated with the second CORESET. 12. The user equipment (UE) of claim 11, wherein at least one of the DAIs associated with the first CORESET or the DAIs associated with the second CORESET is associated with a physical downlink control channel (PDCCH), used for scheduling communications over the Physical Downlink Shared Channel (PDSCH). 13. The user equipment (UE) of claim 12, wherein the HARQ-ACK feedback indicates which association PDSCHs were unsuccessfully received. 14. The user equipment (UE) of claim 11, wherein at least one of the DAIs associated with the first CORESET or the DAIs associated with the second CORESET includes calculated downlink assignment indicators (cDAIs). ). 15. The user equipment (UE) of claim 11, wherein at least one of the DAIs associated with the first CORESET or the DAIs associated with the second CORESET includes common downlink assignment indicators (tDAI ). 16. The user equipment (UE) of claim 11, wherein the DAIs associated with the first CORESET and the DAIs associated with the second CORESET are tracked jointly when the RRC configuration information indicates that the HARQ-ACK feedback uses combined working HARQ-ACK data. 17. The user equipment (UE) of claim 16, wherein the DAIs associated with the first CORESET and the DAIs associated with the second CORESET are counted in order based on the first CORESET and the second CORESET. 18. The user equipment (UE) of claim 11, wherein the DAIs associated with the first CORESET and the DAIs associated with the second CORESET are tracked separately when the RRC configuration information indicates that the HARQ-ACK uses separate working HARQ-ACK data. 19. Non-volatile computer-readable media that stores one or more instructions for wireless communication, and one or more instructions contain: one or more instructions that, when executed by one or more user equipment (UE) processors, instruct one or more processors: receive configuration information at the radio resource control (RRC) level, containing an indicator of whether the hybrid automatic repeat request (HARQ-ACK) acknowledgment feedback should use the combined working HARQ-ACK data or separate working HARQ-ACK data; receive one or more first downlink control information (DCI) transmissions associated with a first control resource set identifier (CORESET); receive one or more DCI transmissions associated with the second CORESET identifier; wherein, when the RRC configuration information indicates that the HARQ-ACK feedback uses the combined HARQ-ACK payload data, the combined HARQ-ACK payload data is transmitted based on the combined HARQ-ACK codebook used to generate the HARQ feedback. -ACK associated with the first CORESET identifier and the second CORESET identifier; wherein, when the RRC configuration information indicates that the HARQ-ACK feedback uses separate HARQ-ACK payload data, the first separate HARQ-ACK payload data is transmitted based on the separate HARQ-ACK codebook used to generate the feedback. a HARQ-ACK associated with the first CORESET ID and a second separate HARQ-ACK payload based on the separate HARQ-ACK codebook used to generate the HARQ-ACK feedback associated with the second CORESET ID. 20. The nonvolatile computer-readable medium of claim 19, wherein at least one or more DCI transmissions associated with the first CORESET includes a downlink assignment indicator (DAI) associated with the first CORESET, and wherein at least one or more DCI transmissions associated with the second CORESET includes a DAI indicator associated with the second CORESET. 21. The nonvolatile computer-readable medium of claim 20, wherein at least one of the DAIs associated with the first CORESET or the DAIs associated with the second CORESET is associated with a physical downlink control channel (PDCCH) used for communication scheduling on a physical downlink shared channel (PDSCH). 22. The non-volatile computer-readable medium of claim 21, wherein the HARQ-ACK feedback indicates which PDSCH connections were unsuccessfully received. 23. The nonvolatile computer-readable medium of claim 20, wherein at least one of the DAIs associated with the first CORESET or the DAIs associated with the second CORESET includes counted downlink assignment indicators (cDAIs). 24. The nonvolatile computer-readable medium of claim 20, wherein at least one of the DAIs associated with the first CORESET or the DAIs associated with the second CORESET includes common downlink assignment indicators (tDAI). 25. The non-volatile computer-readable medium of claim 20, wherein the DAIs associated with the first CORESET and the DAIs associated with the second CORESET are tracked jointly when the RRC configuration information indicates that the HARQ-ACK feedback uses combined operational HARQs. -ACK data. 26. The nonvolatile computer-readable medium of claim 25, wherein the DAIs associated with the first CORESET and the DAIs associated with the second CORESET are counted in order based on the first CORESET and the second CORESET. 27. The nonvolatile computer-readable medium of claim 20, wherein the DAIs associated with the first CORESET and the DAIs associated with the second CORESET are tracked separately when the RRC configuration information indicates that the HARQ-ACK feedback uses separate operational HARQs. -ACK data. 28. Equipment for wireless communication, containing: means for receiving radio resource control (RRC) layer configuration information comprising an indicator of whether the hybrid automatic repeat request (HARQ-ACK) acknowledgment feedback should use combined HARQ-ACK payload data or separate HARQ-ACK payload data ; means for receiving one or more first downlink control information (DCI) transmissions associated with a first control resource set identifier (CORESET); means for receiving one or more DCI transmissions associated with the second CORESET identifier; wherein, when the RRC configuration information indicates that the HARQ-ACK feedback uses the combined HARQ-ACK payload data, the combined HARQ-ACK payload data is transmitted based on the combined HARQ-ACK codebook used to generate the HARQ feedback. -ACK associated with the first CORESET identifier and the second CORESET identifier; wherein, when the RRC configuration information indicates that the HARQ-ACK feedback uses separate HARQ-ACK payload data, the first separate HARQ-ACK payload data is transmitted based on the separate HARQ-ACK codebook used to generate the feedback. a HARQ-ACK associated with the first CORESET ID and a second separate HARQ-ACK payload based on the separate HARQ-ACK codebook used to generate the HARQ-ACK feedback associated with the second CORESET ID. 29. The wireless communications equipment of claim 28, wherein at least one or more DCI transmissions associated with the first CORESET includes a downlink assignment indicator (DAI) associated with the first CORESET, and wherein at least one or more DCI transmissions associated with the second CORESET identifier includes a DAI indicator associated with the second CORESET identifier. 30. The wireless communications equipment of claim 29, wherein at least one of the DAIs associated with the first CORESET or the DAIs associated with the second CORESET is associated with a physical downlink control channel (PDCCH) used for scheduling communications over a physical downlink shared channel (PDSCH).

Images