Type 1 hybrid automatic repeat request acknowledgement codebook generation

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) may indicate UE capabilities for handling a physical downlink shared channel (PDSCH) and exclude an indication that the UE can monitor more than one PDSCH transmission within a time slot per component carrier (CC). The UE may receive control information indicating a codebook configuration for hybrid automatic repeat request (HARQ) acknowledgement (ACK) and including parameters that enable or disable such capability of the UE to monitor more than one PDSCH transmission within a time slot. The UE may monitor one or more downlink shared channel transmissions based on the control information and generate a HARQACK codebook for downlink transmissions, the codebook including feedback for one or more CCs based on the parameter in the control information.

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. patent application No. 18 / 512,472, filed by KHOSHNEVISAN et al. on November 17, 2023, entitled “TYPE1HYBRID AUTOMATIC REPEAT REQUEST ACKNOWLEDGMENT CODEBOOK GENERATION,” which claims the benefit of U.S. provisional patent application No. 63 / 483,090, filed by KHOSHNEVISAN et al. on February 3, 2023, entitled “TYPE 1HYBRID AUTOMATIC REPEATREQUEST ACKNOWLEDGMENT CODEBOOK GENERATION,” each of which is assigned to the assignee of this application and each of which is expressly incorporated herein by reference. Technical Field

[0003] The following relates to wireless communications, including type 1 hybrid automatic repeat request (HARQ) acknowledgement (ACK) codebook generation. Background Art

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

[0005] The UE may generate a feedback codebook based on semi-static information (such as the number of candidate downlink shared channel opportunities). For example, the UE may send an indication of whether it is capable of monitoring more than one physical downlink shared channel (PDSCH) per time slot, and the network entity may provide a configuration for the feedback codebook based on the indication. However, such an indication may be poorly defined (for example, there may be ambiguity as to whether the indication is to be applied per component carrier (CC), per frequency band, per cell group, or other formats), or the network entity may lack support for the indicated UE capability. Summary of the Invention

[0006] The described technology relates to improved methods, systems, devices, and apparatuses for supporting type 1 hybrid automatic repeat request (HARQ) acknowledgment (ACK) codebook generation. For example, the described technology provides rules and signaling for determining which user equipment (UE) capabilities and codebook configurations to consider when generating a feedback codebook for a physical downlink shared channel (PDSCH) transmission. Using a rule-based approach, a UE may send capability information that indicates the UE capabilities for processing PDSCH transmissions (e.g., based on processing or code block group (CBG) capabilities) and indicates that the UE is capable of monitoring more than one PDSCH per time slot and per component carrier (CC). A network entity may enable a UE with a feedback codebook configuration based on the capability information so that the UE may generate a feedback codebook for one or more PDSCH transmissions based on the configuration. The codebook may include feedback for a set of CCs based on a frequency band associated with the UE capability of monitoring more than one PDSCH per time slot and per CC. The codebook may include feedback for a time domain resource allocation (TDRA) group based on a non-overlapping start and length indicator value (SLIV).

[0007] Alternatively, the capability information may indicate the UE capability and indicate that the UE is capable of monitoring a certain number of PDSCH transmissions in a time slot. That is, the capability information may lack an explicit indication of the number of PDSCH transmissions that the UE can receive per CC in a time slot. The network entity may send control information indicating a feedback codebook configuration and parameters (e.g., radio resource control (RRC) parameters) that may enable or disable the UE to monitor more than one PDSCH transmission per time slot. Based on the parameters, the UE may generate a feedback codebook that includes feedback for one or more CCs based on the number of PDSCH transmissions that the network entity may enable the UE to monitor per time slot.

[0008] A method for wireless communication at a UE is described. The method may include: sending capability information indicating UE capabilities for processing a PDSCH, wherein the capability information includes an indication that the UE is capable of monitoring more than one downlink shared channel transmission per CC in a time slot; receiving control information indicating a codebook for HARQ-ACK at the UE; monitoring one or more downlink shared channel transmissions on one or more CCs based on the control information; and generating the codebook for the HARQ-ACK for the one or more downlink shared channel transmissions, wherein the codebook is based on the control information and includes feedback for a first set of CCs, the first set of CCs being at least a portion of the one or more CCs, wherein the first set of CCs for which the feedback is included is based on a frequency band associated with the indication in the capability information.

[0009] A UE for wireless communication is described. The UE may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and individually or collectively operable to execute the code to cause the UE to: send capability information indicating UE capabilities for processing a PDSCH, wherein the capability information includes an indication that the UE is capable of monitoring more than one downlink shared channel transmission per CC within a time slot; receive control information indicating a codebook for HARQ-ACK at the UE; monitor one or more downlink shared channel transmissions on one or more CCs; and generate the codebook for the HARQ-ACK for the one or more downlink shared channel transmissions, wherein the codebook is based on the control information and includes feedback for a first set of CCs, the first set of CCs being at least a portion of the one or more CCs, wherein the first set of CCs for which the feedback is included is based on a frequency band associated with the indication in the capability information.

[0010] Another UE for wireless communication is described. The UE may include: means for transmitting capability information indicating UE capabilities for processing a PDSCH, wherein the capability information includes an indication that the UE is capable of monitoring more than one downlink shared channel transmission per CC within a timeslot; means for receiving control information indicating a codebook for HARQ-ACK at the UE; means for monitoring one or more downlink shared channel transmissions on one or more CCs based on the control information; and means for generating the codebook for the HARQ-ACK for the one or more downlink shared channel transmissions, wherein the codebook is based on the control information and includes feedback for a first set of CCs, the first set of CCs being at least a portion of the one or more CCs, wherein the first set of CCs for which the feedback is included is based on a frequency band associated with the indication in the capability information.

[0011] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by one or more processors to: transmit capability information indicating UE capabilities for processing a PDSCH, wherein the capability information includes an indication that the UE is capable of monitoring more than one downlink shared channel transmission per CC within a time slot; receive control information indicating a codebook for HARQ-ACK at the UE; monitor one or more downlink shared channel transmissions on one or more CCs; and generate the codebook for the HARQ-ACK for the one or more downlink shared channel transmissions, wherein the codebook is based on the control information and includes feedback for a first set of CCs, the first set of CCs being at least a portion of the one or more CCs, wherein the first set of CCs for which the feedback is included is based on a frequency band associated with the indication in the capability information.

[0012] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, generating the codebook may include operations, features, components, or instructions for performing the following actions: including the feedback of candidate downlink shared channel opportunities on the first set of CCs for the TDRA group based on non-overlapping SLIVs.

[0013] Some examples of the methods, UEs, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining the first set of CCs as all CCs in the one or more CCs in the cell group based on the indication in the capability information indicating that the UE may be able to monitor the more than one downlink shared channels sent within the time slot for at least the frequency band in at least one frequency band combination.

[0014] Some examples of the methods, UEs, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining the first set of CCs as all CCs in the one or more CCs in the cell group based on the indication in the capability information indicating that the UE may be able to monitor the more than one downlink shared channels sent within the time slot for at least the frequency band in at least one frequency band combination that includes the cell group.

[0015] Some examples of the methods, UEs, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining the first set of CCs as all CCs in the one or more CCs in the frequency band based on the indication in the capability information indicating that the UE may be able to monitor the more than one downlink shared channels sent in the time slot for the frequency band in at least one frequency band combination.

[0016] Some examples of the methods, UEs, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining the first set of CCs to be all CCs in the one or more CCs in the frequency band based on the indication in the capability information indicating that the UE may be able to monitor the more than one downlink shared channel transmissions in the time slot for the frequency band in at least one frequency band combination, where the at least one frequency band combination corresponds to the one or more CCs in the one or more frequency bands.

[0017] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, generating the codebook may include operations, features, components, or instructions for including the feedback for a single candidate downlink shared channel opportunity on the second set of CCs without identifying a TDRA group of non-overlapping SLIVs.

[0018] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, the UE capabilities for processing the PDSCH included in the capability information include, in addition to the CBG processing capability, one or more of: a first UE capability associated with a first processing capability, a second UE capability associated with a second processing capability applicable to a set of multiple subcarrier spacings, and a restricted second UE capability associated with the second processing capability applicable to a subset of the set of multiple subcarrier spacings, wherein the first processing capability and the second processing capability may be different.

[0019] Some examples of the methods, UEs, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining that the UE may be able to monitor the more than one downlink shared channel transmissions within the time slot based on the indication being associated with the first UE capability without enabling the CBG processing type.

[0020] Some examples of the methods, UEs, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining that the UE may be able to monitor the more than one downlink shared channel transmissions within the time slot based on second control information that enables at least one of the second UE capability or the restricted second UE capability for the UE.

[0021] Some examples of the methods, UEs, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining that the UE may be able to monitor the more than one downlink shared channel transmission within the time slot based on the indication being associated with the first UE capability and in the absence of the enabled second UE processing type, the restricted second UE processing type, and the CBG processing type.

[0022] Some examples of the methods, UEs, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving the second control information enabling the CBG processing type for the UE; and determining that the UE may be able to monitor the more than one downlink shared channel transmission within the time slot based on the indication being associated with the first UE capability and based on the CBG processing type being enabled, and in the absence of the enabled second UE processing type and the restricted second UE processing type.

[0023] Some examples of the methods, UEs, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving the second control information that enables the CBG processing type for the UE and enables at least one of the second UE processing type or the restricted second UE processing type for the UE; and determining that the UE may be able to monitor the more than one downlink shared channel transmission within the time slot based on the indication being associated with the second UE processing type or one of the restricted second UE processing types and based on the CBG processing type being enabled.

[0024] Some examples of the methods, UEs, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving the second control information that enables at least one of the second UE processing type or the restricted second UE processing type for the UE; and determining that the UE may be able to monitor the more than one downlink shared channel transmission within the time slot based on the indication being associated with the second UE processing type or one of the restricted second UE processing types, and in the absence of an enabled CBG processing type.

[0025] Some examples of the methods, UEs, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: determining that the UE may be able to monitor the more than one downlink shared channel transmissions within the time slot may also indicate that the UE may be able to monitor the more than one downlink shared channel transmissions within the time slot based on at least one of the second UE processing type or the restricted second UE processing type.

[0026] A method for wireless communication at a UE is described. The method may include: receiving control information indicating a codebook for HARQ-ACK at the UE, wherein the control information includes a first parameter that disables or enables the UE to monitor more than one downlink shared channel transmission per time slot; monitoring one or more downlink shared channel transmissions based on the control information; and generating the codebook for the HARQ-ACK for the one or more downlink shared channel transmissions, wherein the codebook is based on the control information and includes feedback for one or more CCs based on the first parameter.

[0027] A UE for wireless communication is described. The UE may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and individually or collectively operable to execute the code to cause the UE to: receive control information indicating a codebook for HARQ-ACK at the UE, wherein the control information includes a first parameter that disables or enables the UE to monitor more than one downlink shared channel transmission per time slot; monitor one or more downlink shared channel transmissions based on the control information; and generate the codebook for the HARQ-ACK for the one or more downlink shared channel transmissions, wherein the codebook is based on the control information and includes feedback for one or more CCs based on the first parameter.

[0028] Another UE for wireless communication is described. The UE may include: means for receiving control information indicating a codebook for HARQ-ACK at the UE, wherein the control information includes a first parameter that disables or enables the UE to monitor more than one downlink shared channel transmission per time slot; means for monitoring one or more downlink shared channel transmissions based on the control information; and means for generating the codebook for the HARQ-ACK for the one or more downlink shared channel transmissions, wherein the codebook is based on the control information and includes feedback for one or more CCs based on the first parameter.

[0029] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by one or more processors to: receive control information indicating a codebook for HARQ-ACK at the UE, wherein the control information includes a first parameter that disables or enables the UE to monitor more than one downlink shared channel transmission per time slot; monitor one or more downlink shared channel transmissions; and generate the codebook for the HARQ-ACK for the one or more downlink shared channel transmissions, wherein the codebook is based on the control information and includes feedback for one or more CCs based on the first parameter.

[0030] Some examples of the methods, UEs, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending capability information indicating UE capabilities for processing PDSCH, wherein the capability information includes an indication of a number of downlink shared channel transmissions that the UE may be able to monitor within a time slot.

[0031] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, the first parameter enables the UE to monitor the more than one downlink shared channel transmissions by time slot on a per-CC basis, or on a per-bandwidth part basis, or on a per-cell group basis.

[0032] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, receiving the control information may include operations, features, components, or instructions for performing the following actions: receiving a second indication of a maximum number of downlink shared channel transmissions that the UE may be able to monitor within the time slot.

[0033] Some examples of the methods, UEs, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a second UE capability for monitoring the control information including the first parameter.

[0034] Some examples of the methods, UEs, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving second control information including a second parameter that enables the first parameter on a per-cell group basis, where the first parameter may be on a per-CC basis or on a per-bandwidth part basis.

[0035] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, receiving the control information may include operations, features, components, or instructions for performing the following actions: receiving the first parameter, wherein the first parameter enables the UE to monitor more than one downlink shared channel transmission per time slot or disables the UE from monitoring a single downlink shared channel transmission per time slot.

[0036] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, receiving the control information may include operations, features, components, or instructions for performing the following actions: receiving the first parameter, wherein the first parameter enables the UE to monitor a single downlink shared channel transmission per time slot or disables the UE from monitoring more than one downlink shared channel transmission per time slot.

[0037] A method for wireless communication at a network entity is described. The method may include receiving capability information indicating a UE capability for processing a PDSCH, wherein the capability information includes an indication that the UE is capable of monitoring more than one downlink shared channel transmission per CC in a timeslot; sending control information indicating a codebook for HARQ-ACK at the UE; sending one or more downlink shared channel transmissions on one or more CCs; and receiving feedback for a first set of CCs, the first set of CCs being at least a portion of the one or more CCs, the feedback being included in the codebook, wherein the first set of CCs for which the feedback is included is based on a frequency band associated with the indication in the capability information.

[0038] A network entity for wireless communication is described. The network entity may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and individually or collectively operable to execute the code to cause a UE to: receive capability information indicating UE capabilities for processing a PDSCH, wherein the capability information includes an indication that the UE is capable of monitoring more than one downlink shared channel transmission per CC in a timeslot; send control information indicating a codebook for HARQ-ACK at the UE; send one or more downlink shared channel transmissions on one or more CCs; and receive feedback for a first set of CCs, the first set of CCs being at least a portion of the one or more CCs, the feedback being included in the codebook, wherein the first set of CCs for which the feedback is included is based on a frequency band associated with the indication in the capability information.

[0039] Another network entity for wireless communication is described. The network entity may include: means for receiving capability information indicating UE capabilities for processing PDSCH, wherein the capability information includes an indication that the UE is capable of monitoring more than one downlink shared channel transmission per CC in a timeslot; means for sending control information indicating a codebook for HARQ-ACK at the UE; means for sending one or more downlink shared channel transmissions on one or more CCs; and means for receiving feedback for a first set of CCs, the first set of CCs being at least a portion of the one or more CCs, the feedback being included in the codebook, wherein the first set of CCs for which the feedback is included is based on a frequency band associated with the indication in the capability information.

[0040] A non-transitory computer-readable medium storing code for wireless communication at a network entity is described. The code may include instructions executable by one or more processors to: receive capability information indicating a UE capability for processing a PDSCH, wherein the capability information includes an indication that the UE is capable of monitoring more than one downlink shared channel transmission per CC in a timeslot; send control information indicating a codebook for HARQ-ACK at the UE; send one or more downlink shared channel transmissions on one or more CCs; and receive feedback for a first set of CCs, the first set of CCs being at least a portion of the one or more CCs, the feedback being included in the codebook, wherein the first set of CCs for which the feedback is included is based on a frequency band associated with the indication in the capability information.

[0041] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, receiving the feedback may include operations, features, components, or instructions for receiving the feedback for candidate downlink shared channel opportunities on the first set of CCs based on a TDRA group of non-overlapping SLIVs.

[0042] Some examples of the methods, network entities, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining the first set of CCs as all CCs in the one or more CCs in the cell group based on the indication in the capability information indicating that the UE may be able to monitor the more than one downlink shared channels sent within the time slot for at least the frequency band in at least one frequency band combination.

[0043] Some examples of the methods, network entities, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining the first set of CCs as all CCs in the one or more CCs in the cell group based on the indication in the capability information indicating that the UE may be able to monitor the more than one downlink shared channels sent within the time slot for at least the frequency band in at least one frequency band combination that includes the cell group.

[0044] Some examples of the methods, network entities, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining the first set of CCs as all CCs in the one or more CCs in the frequency band based on the indication in the capability information indicating that the UE may be able to monitor the more than one downlink shared channels sent in the time slot for the frequency band in at least one frequency band combination.

[0045] Some examples of the methods, network entities, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining the first set of CCs to be all CCs in the one or more CCs in the frequency band based on the indication in the capability information indicating that the UE may be able to monitor the more than one downlink shared channel transmissions in the time slot for the frequency band in at least one frequency band combination, where the at least one frequency band combination corresponds to the one or more CCs in the one or more frequency bands.

[0046] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, receiving the feedback may include operations, features, components, or instructions for receiving the feedback for a single candidate downlink shared channel opportunity on a second set of CCs without identifying a TDRA group of non-overlapping SLIVs.

[0047] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the UE capabilities for processing the PDSCH included in the capability information include, in addition to the CBG processing capability, one or more of: a first UE capability associated with a first processing capability, a second UE capability associated with a second processing capability applicable to a set of multiple subcarrier spacings, and a restricted second UE capability associated with the second processing capability applicable to a subset of the set of multiple subcarrier spacings, wherein the first processing capability and the second processing capability may be different.

[0048] Some examples of the methods, network entities, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining that the UE may be able to monitor the more than one downlink shared channel transmissions within the time slot based on the indication being associated with the first UE capability without enabling the CBG processing type.

[0049] Some examples of the methods, network entities, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining that the UE may be able to monitor the more than one downlink shared channel transmissions within the time slot based on second control information that enables at least one of a second UE processing type or a restricted second UE processing type for the UE.

[0050] Some examples of the methods, network entities, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining that the UE may be able to monitor the more than one downlink shared channel transmission within the time slot based on the indication being associated with the first UE capability and in the absence of the enabled second UE processing type, the restricted second UE processing type, and the CBG processing type.

[0051] Some examples of the methods, network entities, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: sending the second control information enabling the CBG processing type for the UE; and determining that the UE may be able to monitor the more than one downlink shared channel transmission within the time slot based on the indication being associated with the first UE capability and based on the CBG processing type being enabled, and in the absence of the enabled second UE processing type and the restricted second UE processing type.

[0052] Some examples of the methods, network entities, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending the second control information that enables the CBG processing type for the UE and enables at least one of the second UE processing type or the restricted second UE processing type for the UE; and determining that the UE may be able to monitor the more than one downlink shared channel transmission within the time slot based on the indication being associated with one of the second UE processing type or the restricted second UE processing type and based on the CBG processing type being enabled.

[0053] Some examples of the methods, network entities, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: sending the second control information to enable at least one of the second UE processing type or the restricted second UE processing type for the UE; and determining that the UE may be able to monitor the more than one downlink shared channel transmission within the time slot based on the indication being associated with the second UE processing type or one of the restricted second UE processing types, and in the absence of an enabled CBG processing type.

[0054] Some examples of the methods, network entities, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: determining that the UE may be able to monitor the more than one downlink shared channel transmissions within the time slot may also indicate that the UE may be able to monitor the more than one downlink shared channel transmissions within the time slot based on at least one of the second UE processing type or the restricted second UE processing type.

[0055] A method for wireless communication at a network entity is described. The method may include: sending control information indicating a codebook for HARQ-ACK at a UE, wherein the control information includes a first parameter that disables or enables the UE to monitor more than one downlink shared channel transmission per time slot; sending one or more downlink shared channel transmissions; and receiving feedback for one or more CCs based on the first parameter, wherein the feedback is included in the codebook for the HARQ-ACK for the one or more downlink shared channel transmissions, and wherein the codebook is based on the control information.

[0056] A network entity for wireless communication is described. The network entity may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and individually or collectively operable to execute the code to cause a UE to: send control information indicating a codebook for HARQ-ACK at the UE, wherein the control information includes a first parameter that disables or enables the UE to monitor more than one downlink shared channel transmission per time slot; send one or more downlink shared channel transmissions; and receive feedback for one or more CCs based on the first parameter, wherein the feedback is included in the codebook for the HARQ-ACK for the one or more downlink shared channel transmissions, and wherein the codebook is based on the control information.

[0057] Another network entity for wireless communication is described. The network entity may include: means for sending control information indicating a codebook for HARQ-ACK at a UE, wherein the control information includes a first parameter that disables or enables the UE to monitor more than one downlink shared channel transmission per time slot; means for sending one or more downlink shared channel transmissions; and means for receiving feedback for one or more CCs based on the first parameter, wherein the feedback is included in the codebook for the HARQ-ACK for the one or more downlink shared channel transmissions, and wherein the codebook is based on the control information.

[0058] A non-transitory computer-readable medium storing code for wireless communication at a network entity is described. The code may include instructions executable by one or more processors to: transmit control information indicating a codebook for HARQ-ACK at a UE, wherein the control information includes a first parameter that disables or enables the UE to monitor more than one downlink shared channel transmission per time slot; transmit one or more downlink shared channel transmissions; and receive feedback for one or more CCs based on the first parameter, wherein the feedback is included in the codebook for the HARQ-ACK for the one or more downlink shared channel transmissions, and wherein the codebook is based on the control information.

[0059] Some examples of the methods, network entities, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving capability information indicating UE capabilities for processing PDSCH, wherein the capability information includes an indication of a number of downlink shared channel transmissions that the UE may be able to monitor within a timeslot.

[0060] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the first parameter enables the UE to monitor the more than one downlink shared channel transmissions by time slot on a per-CC basis, or on a per-bandwidth part basis, or on a per-cell group basis.

[0061] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, sending the control information may include operations, features, components, or instructions for performing the following actions: sending a second indication of a maximum number of downlink shared channel transmissions that the UE may be able to monitor within the time slot.

[0062] Some examples of the methods, network entities, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a second UE capability for monitoring the control information including the first parameter.

[0063] Some examples of the methods, network entities, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending second control information including a second parameter that enables the first parameter on a per-cell group basis, where the first parameter may be on a per-CC basis or on a per-bandwidth part basis.

[0064] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, sending the control information may include operations, features, components, or instructions for performing the following actions: sending the first parameter, wherein the first parameter enables the UE to monitor more than one downlink shared channel transmission per time slot or disables the UE from monitoring a single downlink shared channel transmission per time slot.

[0065] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, sending the control information may include operations, features, components, or instructions for performing the following actions: sending the first parameter, wherein the first parameter enables the UE to monitor a single downlink shared channel transmission per time slot or disables the UE from monitoring more than one downlink shared channel transmission per time slot. BRIEF DESCRIPTION OF THE DRAWINGS

[0066] Figure 1 An example of a wireless communication system supporting type 1 hybrid automatic repeat request (HARQ) acknowledgement (ACK) codebook generation according to one or more aspects of the present disclosure is illustrated.

[0067] Figure 2 An example of a wireless communication system supporting Type 1 HARQ-ACK capabilities in accordance with one or more aspects of the present disclosure is illustrated.

[0068] Figure 3 An example of a frame format supporting Type 1 HARQ-ACK codebook generation according to one or more aspects of the present disclosure is illustrated.

[0069] Figure 4 and Figure 5 An example of a process flow supporting Type 1 HARQ-ACK codebook generation according to one or more aspects of the present disclosure is illustrated.

[0070] Figure 6 and Figure 7A block diagram illustrating a device supporting Type 1 HARQ-ACK codebook generation according to one or more aspects of the present disclosure is shown.

[0071] Figure 8 A block diagram illustrating a communications manager supporting Type 1 HARQ-ACK codebook generation according to one or more aspects of the present disclosure is illustrated.

[0072] Figure 9 A diagram illustrating a system including a device supporting Type 1 HARQ-ACK codebook generation in accordance with one or more aspects of the present disclosure is illustrated.

[0073] Figure 10 and Figure 11 A block diagram illustrating a device supporting Type 1 HARQ-ACK codebook generation according to one or more aspects of the present disclosure is shown.

[0074] Figure 12 A block diagram illustrating a communications manager supporting Type 1 HARQ-ACK codebook generation according to one or more aspects of the present disclosure is illustrated.

[0075] Figure 13 A diagram illustrating a system including a device supporting Type 1 HARQ-ACK codebook generation in accordance with one or more aspects of the present disclosure is illustrated.

[0076] Figures 14 to 19 A flowchart illustrating a method for supporting Type 1 HARQ-ACK codebook generation according to one or more aspects of the present disclosure is illustrated. DETAILED DESCRIPTION

[0077] In some examples, a user equipment (UE) may generate a feedback codebook based on semi-statically received configuration information, which may be based on different capabilities of the UE. That is, the UE may report one or more different capabilities, each of which identifies the number of physical downlink shared channel (PDSCH) opportunities that the UE may be able to monitor or receive for a corresponding feature set in a given time slot on a component carrier (CC). For example, the UE may report the ability (e.g., processing capability) to monitor (and receive) a first number of PDSCH opportunities under type 1 processing conditions, the ability to monitor (and receive) a second number of PDSCH opportunities under type 2 processing conditions, the ability to monitor (and receive) a third number of PDSCH opportunities under type 1 processing conditions with code block groups (CBGs) enabled, and the ability to monitor (and receive) a fourth number of PDSCH opportunities under type 2 processing conditions with CBGs enabled. Each of these numbers may be different, and therefore, the network entity may enable specific configuration information for the UE to generate a feedback codebook based on different capabilities.

[0078] However, when a network entity enables multiple different configurations, there may be ambiguities in generating the feedback codebook. For example, when determining the feedback codebook, the UE may provide feedback for each PDSCH opportunity, or if multiple opportunities overlap, the UE may provide feedback for each time domain resource allocation (TDRA) group, where a TDRA group may include a unique set of overlapping start and length indicator values ​​(SLIVs). When a network entity enables a UE with different configurations, each corresponding to a different capability for receiving PDSCH transmissions within a timeslot (e.g., a different number of PDSCH transmissions per timeslot), the UE may need additional information to determine how large the feedback codebook may be and which TDRA groups the UE may consider including in the feedback codebook. In addition, the network entity may lack support for some capabilities of the UE's PDSCH reception, which may limit the feedback codebook or reduce resource usage efficiency.

[0079] The technology described herein supports rules and signaling for determining which UE capabilities and codebook configurations to consider when generating a feedback codebook for PDSCH transmission. Using rule-based techniques, a UE may send capability information to a network entity that indicates the UE capabilities for processing PDSCH transmissions and an indication that the UE is capable of monitoring more than one PDSCH transmission per time slot and per CC. A network entity may enable a UE with one or more configurations, each of which is associated with a reported UE capability. Since the UE capabilities each identify the number of PDSCH opportunities that the UE is capable of monitoring within a time slot, the configuration may also be based on a different number of PDSCH opportunities. The UE may generate a feedback codebook (e.g., a type 1 hybrid automatic repeat request (HARQ) acknowledgment (ACK) codebook) for PDSCH transmission based on the UE capabilities and configuration, wherein the codebook includes feedback for a set of component carriers based on the frequency band associated with the configuration. That is, given the different capabilities reported by the UE, the rules may specify which CCs the UE is to consider to determine the TDRA group for non-overlapping SLIVs.

[0080] Alternatively, the network entity may send control information including a radio resource control (RRC) parameter that indicates the number of PDSCH opportunities that the UE will monitor per time slot. The UE may send capability information to the network entity that indicates the UE capability for processing PDSCH transmissions and an indication that the UE is capable of monitoring a certain number (e.g., one or more) of PDSCH transmissions per time slot, per CC. Instead of providing different feedback codebook configurations to the UE based on different UE capabilities, or in addition to this, the network entity may send control information including an RRC parameter that may enable or disable the UE to monitor more than one PDSCH per time slot. In some examples, the parameter may indicate the number of PDSCHs that the UE is to monitor. Thus, the UE may generate a feedback codebook based on the control information that includes feedback for one or more CCs based on the information in the RRC parameter.

[0081] Various aspects of the present disclosure are first described in the context of a wireless communication system. Various aspects of the present disclosure are then described in the context of frame formats and process flows. Various aspects of the present disclosure are further illustrated and described by and with reference to apparatus diagrams, system diagrams, and flow diagrams related to Type 1 HARQ-ACK codebook generation.

[0082] Figure 1 An example of a wireless communication system 100 that supports type 1 HARQ-ACK codebook generation according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a long term evolution (LTE) network, an advanced LTE (LTE-A) network, an LTE-A Pro network, a new radio (NR) network, or a network operating according to other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

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

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

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

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

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

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

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

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

[0091] Where the techniques described herein are applied in the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support Type 1 HARQ-ACK codebook generation as described herein. For example, some operations described as being performed by the UE 115 or the network entity 105 (e.g., the base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., the IAB node 104, the DU 165, the CU 160, the RU 170, the RIC 175, the SMO 180).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0113] The wireless communication system 100 can utilize licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 can employ license assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology using unlicensed bands (such as the 5 GHz industrial, scientific, and medical (ISM) band). When operating using unlicensed RF spectrum bands, devices such as the network entity 105 and the UE 115 can employ carrier sensing for conflict detection and avoidance. In some examples, operations using unlicensed bands can be based on carrier aggregation configuration (e.g., LAA) in conjunction with CCs operating using licensed bands. Operations using unlicensed spectrum can include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among others.

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

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

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

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

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

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

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

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

[0122] In some examples, UE 115 may determine a type 1 HARQ-ACK codebook (e.g., a semi-static HARQ-ACK codebook) based on semi-static information (e.g., candidate PDSCH opportunities). The candidate PDSCH opportunities correspond to opportunities during which UE 115 may receive PDSCH transmissions. In some cases, UE 115 may determine a set of PDSCH opportunities for the codebook on a per-downlink serving cell basis based on several factors. In some examples, the set of PDSCH opportunities may be based on a set of configured K1 values, which may be a set of possible slot timing offset values ​​(e.g., an offset between PDSCH and HARQ-ACK transmissions) that may be indicated by downlink control information (DCI). For example, if DCI format 1_0 is configured in the serving cell and DCI format 1_1 is not configured, the set of K1 values ​​may be {1, 2, 3, 4, 5, 6, 7, 8}. If DCI format 1_1 or DCI format 1_2 is configured for the serving cell, K1 may be provided by dl-DataToUL-ACK in the RRC configuration.

[0123] Additionally, for each K1 value, UE 115 may determine a set of PDSCH TDRA candidates (e.g., corresponding to SLIVs within a time slot). In some examples, TDRA candidates that overlap with semi-static uplink symbols may be removed because UE 115 may not be able to monitor the PDSCH corresponding to the overlapping TDRA opportunities or corresponding SLIVs, and the remaining TDRA candidates (e.g., rows) may be grouped such that the number of groups is equal to the maximum number of non-overlapping SLIVs in the time slot and the number of bits required by the HARQ-ACK codebook for that K1 value.

[0124] In some examples, HARQ-ACK codebook determination can be a two-step process, comprising first determining a set of PDSCH opportunities as described herein, and then determining the HARQ-ACK codebook based on the set of PDSCH opportunities. A type 1 HARQ-ACK codebook can accommodate as many bits as there are potential PDSCH receptions. For example, if TDRA includes SLIVs for non-overlapping symbols {0,1}, {2,3}, {4,5}, ..., {12,13}, then there may be 7 bits per K1 value per CC. That is, if K1 = {1,2,3}, then depending on how many SLIVs overlap with uplink symbols per slot, there may be 7*3 = 21 bits per CC for FDD, and slightly fewer bits for TDD. That is, by time slot and by K1 value, UE 115 may identify any SLIVs that overlap with uplink symbols and perform TDRA grouping after removing overlapping SLIVs (eg, UE 115 performs TDRA grouping only for SLIVs that do not overlap with semi-static uplink symbols).

[0125] If the UE 115 fails to indicate the ability to monitor more than one PDSCH per time slot, an exception to this process of determining the HARQ-ACK codebook based on the PDSCH timing may occur. In such cases, there may be one bit per time slot per K1 value. Therefore, the UE 115 can avoid performing TDRA grouping, and the size of the HARQ-ACK codebook can be independent of the maximum number of non-overlapping SLIVs corresponding to different TDRA rows within the time slot. Otherwise, the UE capability with respect to the maximum number of PDSCHs per time slot may not be considered, and instead the UE 115 may determine the HARQ-ACK codebook by considering the maximum number of non-overlapping SLIVs in the TDRA rows in the time slot or the set of candidates. That is, if there is more than one bit per time slot per K1 value, the UE 115 may determine the size (e.g., the number of bits) of the HARQ-ACK codebook based on the maximum number of non-overlapping SLIVs in the TDRA rows in the time slot or the set of candidates.

[0126] For each K1 value, if the UE 115 fails to indicate the ability to monitor more than one unicast PDSCH or multicast PDSCH per time slot, and if the set of SLIVs corresponding to the TDRA row is non-zero, the UE 115 may add a location (e.g., M ) for each PDSCH in the codebook. A,c =M A,c ∪j, where M A,c ( M ) may represent a set of candidate PDSCH reception opportunities for serving cell c, and j may represent an index of an opportunity for candidate PDSCH reception. Thus, based on the UE 115 failing to indicate its capabilities, there may be one bit per slot (e.g., to support one PDSCH). Otherwise (e.g., not), the UE 115 may perform TDRA grouping to identify the maximum number of non-overlapping SLIVs in the slot. Each TDRA group may then contribute to the set of candidate PDSCH reception opportunities (M ) A,c ) adds a location (j). That is, there may be more than one bit per time slot based on the number of non-overlapping SLIVs.

[0127] In some examples, whether UE 115 fails to indicate the ability to monitor more than one PDSCH per time slot may be a condition that is neither explicitly defined nor controlled by network entity 105. In some cases, it may not be clear whether the condition can be applied per CC, per frequency band, or per cell group and based on the UE capabilities, the condition may be defined. For example, there may be multiple UE capabilities (e.g., up to 2, up to 4, up to 7) indicating more than one PDSCH per time slot, including UE capabilities for PDSCH processing type 1 (e.g., normal timeline, pdsch-ProcessingType1-DifferentTB-PerSlot), PDSCH processing type 2 (e.g., fast timeline, pdsch-ProcessingType2), PDSCH processing type 2 with scheduling restrictions (e.g., pdsch-ProcessingType2-Limited), (CBG)-based PDSCH reception for PDSCH processing type 1 (e.g., cbgPDSCH-ProcessingType1-DifferentTB-PerSlot), or CBG-based PDSCH reception for PDSCH processing type 2 (e.g., cbgPDSCH-ProcessingType2-DifferentTB-PerSlot), as well as other UE capabilities. Such UE capabilities can be indicated per feature set so that the granularity of UE capability signaling can be per frequency band, per frequency band combination. Therefore, UE 115 may fail to specify to which UE capability the condition regarding more than one PDSCH per slot applies.

[0128] In some examples, for PDSCH processing type 1 and non-CBG capability, the UE 115 may indicate that two PDSCHs per time slot are supported for band 1 in the band combination {band 1, band 2}. Additionally, the UE 115 may separately indicate that two PDSCHs per time slot are supported for band 2 in the band combination {band 1, band 2} (e.g., not for both bands in the band combination at the same time). The network entity 105 may configure CC 1 in band 1 and CC 2 in band 2, where the configured TDRAs for the two bands include more than one non-overlapping SLIV. Additionally, the network entity 105 may schedule more than one PDSCH per time slot in one of the two CCs, but not in both CCs. Based on the RRC configuration, the UE 115 may not be informed which CC may be scheduled with more than one PDSCH per time slot, which may affect the type 1 HARQ-ACK codebook construction and result in codebook size mismatch. This problem may occur if the UE capabilities are on a per-band, per-band combination basis, and functionality depends on the UE capabilities, without RRC parameters that can be configured by the network entity 105. That is, it may not be clear whether the UE 115 is to support one or more than one PDSCH per timeslot in any one band.

[0129] In some other examples, UE 115 may indicate support for 7 PDSCHs per slot for UE processing capability type 1, 1 PDSCH per slot for CBG-based PDSCH capability, or 2 PDSCHs per slot for UE processing capability type 2 with scheduling restrictions. In such cases, it may be unclear whether UE 115 should consider network-configured RRC parameters related to CBG-based PDSCH (e.g., PDSCH-CodeBlockGroupTransmission), UE processing capability type 2 (e.g., processingType2Enabled), or both to know which UE capability to consider to know whether to apply the condition. Furthermore, the RRC parameter processingType2Enabled may fail to distinguish between UE processing capability type 2 and UE processing capability type 2 with scheduling restrictions.

[0130] Additionally or alternatively, UE 115 may support the ability to monitor more than one PDSCH per slot, which network entity 105 may prefer not to use or may lack the corresponding capability. For example, UE 115 may support 7 PDSCHs per slot for both Band 1 and Band 2 in the band combination {Band 1, Band 2}, and network entity 105 may configure two CCs in Band 1 and three CCs in Band 2. Network entity 105 may still intend to transmit up to one PDSCH per slot. For example, network entity 105 may intend to transmit one PDSCH per slot in all CCs in Band 1 and Band 2, in all CCs in Band 1 but not in any CC in Band 2, or in some but not all CCs in Band 1. The configured TDRA for each of the five CCs may include 7 non-overlapping SLIVs, however, the 7 non-overlapping SLIVs may not be based on transmitting 7 PDSCHs per slot for UE 115. In contrast, 7 non-overlapping SLIVs may provide the flexibility to dynamically TDM different UEs 115 in different symbols of a slot. In this way, the Type 1 HARQ-ACK codebook may have 35 bits (e.g., 7*5 bits) per PDSCH slot across all CCs for UE 115. However, for some CCs, only one bit per PDSCH slot may be sufficient.

[0131] To address issues related to the unclear definition of conditions for UE 115 indicating its ability to monitor more than one PDSCH per time slot and the lack of corresponding capabilities at the network entity 105, the wireless communication system 100 may support techniques for clarifying how to interpret conditions based on the indicated UE capabilities or using new RRC configurations to indicate conditions without defining the UE capabilities. Using a rule-based approach, the UE 115 may send capability information indicating the UE capabilities for processing PDSCH transmissions (e.g., based on processing or CBG capabilities) and indicating that the UE 115 is capable of monitoring more than one PDSCH per time slot and per CC. The network entity 105 may enable the UE 115 with a feedback codebook configuration based on the capability information so that the UE 115 may generate a feedback codebook (e.g., a Type 1 HARQ-ACK codebook) for one or more PDSCH transmissions based on the configuration. The codebook may include feedback for a set of CCs based on the frequency band associated with the UE capability to monitor more than one PDSCH per time slot and per CC. The codebook may include feedback of TDRA groups based on non-overlapping SLIV.

[0132] Alternatively, the capability information may indicate the UE capability and indicate that the UE 115 is capable of monitoring a certain number of PDSCH transmissions in a time slot. That is, the capability information may lack an explicit indication of the number of PDSCH transmissions that the UE 115 can receive per CC in a time slot. The network entity 105 may send control information indicating a feedback codebook configuration and parameters (e.g., RRC parameters) that enable or disable the UE 115 from monitoring more than one PDSCH transmission per time slot. Based on the parameters, the UE 115 may generate a feedback codebook that includes feedback for one or more CCs based on the number of PDSCH transmissions that the network entity 105 may enable the UE 115 to monitor per time slot.

[0133] Figure 2 An example of a wireless communication system 200 that supports type 1 HARQ-ACK codebook generation according to one or more aspects of the present disclosure is illustrated. In some examples, the wireless communication system 200 may implement aspects of the wireless communication system 100, or may be implemented by aspects of the wireless communication system 100. For example, the wireless communication system 200 may include a UE 115-a and a network entity 105-a (which may be examples of corresponding devices as described herein). The UE 115-a and the network entity 105-a may support type 1 HARQ-ACK codebook generation, which may be based on one or more capabilities of the UE 115-a for processing physical uplink shared channel (PUSCH) transmissions and a corresponding feedback codebook configuration enabled by the network entity 105-a for the UE 115-a.

[0134] The wireless communication system 200 may support communication between the UE 115-a and the network entity 105-a. For example, the UE 115-a and the network entity 105-a may perform uplink and downlink communication via a corresponding communication link 205, which may be a reference to a wireless communication system 200. Figure 1An example of the communication link 125 described. In some examples, the UE 115-a may transmit capability information 210 indicating UE capabilities for processing a PDSCH. The UE capabilities may include one or more of: a first UE capability associated with a first processing capability (e.g., pdsch-ProcessingType1-DifferentTB-PerSlot), a second UE capability associated with a second processing capability applicable to a set of multiple subcarrier spacings (e.g., pdsch-ProcessingType2), a limited second UE capability associated with a second processing capability applicable to a subset of the multiple subcarrier spacings (e.g., pdsch-ProcessingType2-Limited), a CBG processing capability associated with the first processing capability (e.g., cbgPDSCH-ProcessingType1-DifferentTB-PerSlot-r16), or a CBG processing capability associated with the second processing capability (e.g., cbgPDSCH-ProcessingType2-DifferentTB-PerSlot-r16). The first processing capability and the second processing capability may be different.

[0135] For example, the first processing capability may define whether the UE is able to monitor up to two, four or seven unicast PDSCHs for several transport blocks multiplexed in the time domain, the several transport blocks having PDSCHs scrambled using C-RNTI, TC-RNTI or CS-RNTI in one serving cell with the same time slot per CC. The second processing capability may indicate the UE capability of receiving 1, 2, 4 or 7 unicast PDSCHs for different transport blocks per time slot, per CC for a set of subcarrier spacings. The restricted second processing capability may indicate the UE capability of receiving 1, 2, 4 or 7 unicast PDSCHs for different transport blocks per time slot, per CC for a limitation of 30 kHz subcarrier spacing in the presence of scheduling restrictions (e.g., regarding the maximum number of resource blocks). In addition, the CBG processing capability associated with the first processing capability and the second processing capability may indicate that the UE supports CBG-based reception of 1, 2, 4 or 7 unicast PDSCHs per time slot, per CC. In addition to the UE capabilities for processing PDSCH, the capability information 210 may also include an indication that the UE 115 - a is capable of monitoring more than one PDSCH transmission per CC within a timeslot.

[0136] UE 115-a may receive control information 215 indicating a codebook 225 (e.g., a type 1 HARQ-ACK codebook) for HARQ-ACK at UE 115-a. After monitoring one or more PDSCH transmissions 220 from network entity 105-a, UE 115-a may generate codebook 225 for PDSCH transmissions 220 based on control information 215. That is, UE 115-a may generate codebook 225 based on the ability of UE 115-a to monitor (and receive) more than one PDSCH per CC in a timeslot and the feedback codebook configuration enabled by network entity 105-a. In some examples, codebook 225 may include feedback (e.g., HARQ-ACK feedback) for a first set of CCs based on a frequency band associated with an indication that UE 115-a is capable of monitoring more than one PDSCH transmission 220 per CC in a timeslot. That is, based on the indication in the capability information 210, the UE 115-a may perform TDRA grouping based on non-overlapping SLIV for determining the number of PDSCH opportunities to include in the codebook 225 (e.g., a type 1 HARQ-ACK codebook).

[0137] In some examples, UE 115-a may determine, based on the indication in capability information 210, a first set of CCs in one or more CCs for which UE 115-a monitors PDSCH transmission 220. For example, if UE 115-a indicates an ability to monitor more than one PDSCH per time slot for at least one band in at least one band combination (e.g., band 1 in band combination {band 1, band 2}), codebook 225 may include feedback for all configured CCs in the cell group. Alternatively, if UE 115-a indicates an ability to monitor more than one PDSCH per time slot for at least one band in the band combination that includes the cell group, codebook 225 may include feedback for all configured CCs in the cell group. In these cases, the first set of CCs may include all CCs in the one or more CCs in the cell group for which UE 115-a monitors PDSCH transmission 220 for any UE capability to process PDSCH transmission 220.

[0138] In some other examples, if UE 115-a indicates the capability to monitor more than one PDSCH per time slot for a band in at least one band combination, codebook 225 may include feedback for all configured CCs in the band. Alternatively, if UE 115-a indicates the capability to monitor more than one PDSCH per time slot for a band in a band combination that is consistent with configured CCs across all bands, codebook 225 may include feedback for all configured CCs in the band. That is, a band combination may correspond to one or more CCs in one or more bands. In such a case, UE 115-a may determine the first set of CCs to be all CCs in the one or more CCs in the band for any UE capability for processing PDSCH transmission 220.

[0139] In some cases, different UE capabilities and control information 215 may generate different first sets of CCs for inclusion in feedback in codebook 225 based on TDRA grouping of non-overlapping SLIVs. For example, UE 115-a may indicate (e.g., in capability information 210) support for receiving two PDSCH transmissions 220 per time slot for band 1 in the band combination {band 1, band 2}. Control information 215 (e.g., RRC configuration) may indicate CC1 in band 1 and CC2 in band 2. Thus, if UE 115-a includes feedback for all CCs in a cell group based on UE 115-a indicating a capability to monitor more than one PDSCH per time slot for at least one band in at least one band combination (e.g., option 1) or a capability to monitor more than one PDSCH per time slot for at least one band in a band combination that includes the CCs (e.g., option 2), UE 115-a may include feedback for both CC1 and CC2. Alternatively, if UE 115-a includes feedback for all CCs in a band based on UE 115-a indicating the capability to monitor more than one PDSCH per time slot for a band in at least one band combination (e.g., option 3) or the capability to monitor more than one PDSCH per time slot for a band in at least one band combination that is consistent with CCs across all bands (e.g., option 4), UE 115-a may include feedback only for CC1 (because the capability information 210 only indicates support for CCs in the same supported bands).

[0140] In some other examples, UE 115-a may indicate (e.g., in capability information 210) support for receiving two PDSCH transmissions 220 per time slot for band 1 in the band combination {band 1, band 2}. Control information 215 (e.g., RRC configuration) may indicate CC1 in band 1 and CC2 in band 3 (e.g., where band 3 is outside the band combination). Thus, UE 115-a may support the capability to monitor more than one PDSCH transmission 220 per time slot for the band combination {band 1, band 2} but not for the band combination {band 1, band 3}. Thus, if UE 115-a includes feedback for all CCs in a cell group based on UE 115-a indicating the capability to monitor more than one PDSCH per time slot for at least one band in at least one band combination (e.g., option 1), UE 115-a may include feedback for both CC1 and CC2. If UE 115-a includes feedback for all CCs in the cell group based on UE 115-a indicating the ability to monitor more than one PDSCH per time slot for at least one frequency band in a frequency band combination that includes the CC (e.g., option 2) or the ability to monitor more than one PDSCH per time slot for frequency bands in at least one frequency band combination that are consistent with CCs across all frequency bands (e.g., option 4), UE 115-a may not include feedback for CC1 or CC2, because in such cases it is required that the frequency band combination corresponds to the cell group. If UE 115-a includes feedback for all CCs in the frequency band based on UE 115-a indicating the ability to monitor more than one PDSCH per time slot for frequency bands in at least one frequency band combination (e.g., option 3), UE 115-a may include feedback only for CC1, or UE 115-a may include feedback only for CC1.

[0141] In some other examples, UE 115-a may indicate (e.g., in capability information 210) support for receiving two PDSCH transmissions per time slot for Band 1 and Band 2 in the band combination {Band 1, Band 2}. UE 115-a may indicate this support as a separate instance of a feature set (e.g., separate indications of support for Band 1 and Band 2 in the band combination {Band 1, Band 2}). Control information 215 (e.g., an RRC configuration) may indicate CC1 in Band 1 and CC2 in Band 2. Thus, if UE 115-a includes feedback for all CCs in a cell group based on UE 115-a indicating the ability to monitor more than one PDSCH per time slot for at least one frequency band in at least one frequency band combination (e.g., option 1), at least one frequency band in a frequency band combination of a cell group that includes a CC (e.g., option 2), frequency bands in at least one frequency band combination (e.g., option 3), or frequency bands in at least one frequency band combination that are consistent with CCs across all frequency bands (e.g., option 4), then UE 115-a may include feedback for both CC1 and CC2. In such a case, UE 115-a may perform TDRA grouping for CC1 and CC2.

[0142] Additionally or alternatively, codebook 225 may include feedback for a second set of CCs, where, based on UE 115-a avoiding performing TDRA grouping for non-overlapping SLIVs, only one candidate PDSCH opportunity per time slot may be considered in the codebook for each CC in the second set of CCs. This situation may occur if UE 115-a fails to indicate the ability to monitor more than one PDSCH transmission 220 per time slot. In such cases, codebook 225 may include feedback for a single candidate PDSCH opportunity on the second set of CCs without identifying a TDRA group for non-overlapping SLIVs. Thus, the second set of CCs may include CCs that are not included in the first set of CCs (e.g., the second set may be in addition to the first set). Alternatively, the first set of CCs may include CCs that are not included in the second set of CCs (e.g., the first set may be in addition to the second set).

[0143] In some cases, UE support for receiving more than one PDSCH per time slot may be determined based on the UE capabilities indicated in the capability information 210. For example, the capability may be determined based on the capability for PDSCH processing type 1 and the non-CBG based PDSCH capability. That is, UE 115-a may use a first UE capability associated with a first processing capability (e.g., pdsch-ProcessingType1-DifferentTB-PerSlot) to receive more than one PDSCH per time slot for a CC even if a second UE processing type (e.g., PDSCH processing type 2) or a CBG processing type is configured for the CC. UE 115-a may determine that it is able to monitor more than one PDSCH transmission 220 within a time slot based on the indication in the capability information 210 associated with the first UE capability without enabling the CBG processing type for UE 115-a. That is, the first UE capability may not be associated with the CBG processing type, and UE 115-a may use the first UE capability for the purpose of type 1 HARQ-ACK codebook generation (regardless of the RRC configuration of enabling type 2 processing or CBG-based PDSCH from the network entity 105-a), and if the CBG capability is configured for other purposes, UE 115-a may continue to follow the CBG-based process.

[0144] Alternatively, the UE 115-a may determine which UE capability to apply for receiving more than one PDSCH transmission 220 within a time slot based on whether a second UE capability, a restricted second UE capability, a CBG processing capability, or a combination thereof is configured for a given CC. That is, the UE 115-a may determine that the UE 115-a is capable of monitoring more than one PDSCH transmission 220 within a time slot (or may determine that the UE 115-a is not capable of monitoring more than one PDSCH transmission 220 within a time slot) based on receiving second control information (e.g., RRC signaling) from the network entity 105-a, the second control information enabling at least one of the second UE capability or the restricted second UE capability, enabling CBG-based PDSCH reception, or a combination thereof for the UE 115-a.

[0145] In some examples, if the CBG processing type (e.g., PDSCH-CodeBlockGroupTransmission) and the second UE processing type (e.g., processingType2Enabled) are not configured for UE 115-a, UE 115-a may use the first UE capability (e.g., pdsch-ProcessingType1-DifferentTB-PerSlot) to receive more than one PDSCH transmission 220 within a timeslot. That is, UE 115-a may determine that it is capable of monitoring more than one PDSCH transmission 220 within a timeslot based on the indication in the capability information 210 associated with the first UE capability and in the absence of the enabled second UE processing type, the restricted second UE processing type, and the CBG processing type.

[0146] Alternatively, if a CBG processing type (e.g., PDSCH-CodeBlockGroupTransmission) is configured and a second UE processing type (e.g., processingType2Enabled) is not configured for UE 115-a, UE 115-a may use a CBG processing type (e.g., cbgPDSCH-ProcessingType1-DifferentTB-PerSlot-r16) to receive more than one PDSCH transmission 220 within a time slot. In such a case, UE 115-a may receive second control information (e.g., RRC signaling) from network entity 105-a that enables the CBG processing type for UE 115-a. UE 115-a may determine that it is capable of monitoring one or more PDSCH transmissions 220 within a time slot based on the indication in capability information 210 associated with the first UE capability and based on enabling the CBG processing type, and in the absence of an enabled second UE processing type and a restricted second UE processing type.

[0147] If both the CBG processing type (e.g., PDSCH-CodeBlockGroupTransmission) and the second UE processing type (e.g., processingType2Enabled) are configured for UE 115-a, UE 115-a may use the second UE capability (for limited second UE capability) to monitor more than one PDSCH transmission 220 within a time slot. In such a case, UE 115-a may receive second control information (e.g., RRC signaling) that enables the CBG processing type for UE 115-a and enables at least one of the second UE processing type or the limited second UE processing type for UE 115-a. UE 115-a may determine that it is capable of monitoring more than one PDSCH transmission 220 within a time slot based on an indication in capability information 210 associated with one of the second UE processing type or the limited second UE processing type and based on the CBG processing type being enabled.

[0148] If a CBG processing type (e.g., PDSCH-CodeBlockGroupTransmission) is not configured and a second UE processing type (e.g., processingType2Enabled) or a restricted second UE processing type (e.g., pdsch-ProcessingType2-Limited) is configured for UE 115-a, UE 115-a may use the second UE capability or the restricted second UE capability to monitor more than one PDSCH transmission 220 within a time slot. That is, UE 115-a may receive second control information (e.g., RRC signaling) that enables at least one of the second UE processing type or the restricted second UE processing type for UE 115-a. UE 115-a may be associated with one of the second UE processing type or the restricted second UE processing type based on an indication in capability information 210 and determine that it is capable of monitoring more than one PDSCH transmission 220 within a time slot in the absence of an enabled CBG processing type. In some cases, if UE 115-a indicates both the second UE processing type and the restricted second UE processing type, UE 115-a may use corresponding capabilities associated with a greater number of PDSCH transmissions 220 per time slot (e.g., if UE 115-a indicates more than one PDSCH per time slot in at least one of the two second UE capabilities, UE 115-a may perform TDRA grouping). That is, the second UE capabilities or the restricted second UE capabilities may indicate that UE 115-a is capable of monitoring more than one PDSCH transmission 220 within a time slot.

[0149] In some examples, the indication that the UE 115-a supports more than one PDSCH transmission 220 per time slot may be ambiguous (e.g., as to which UE capability applies to the condition). In such cases, the network entity 105-a may use an RRC configuration to enable or disable the UE 115-a from monitoring more than one PDSCH transmission 220 per time slot. The UE 115-a may receive control information 215 indicating a codebook 225. Additionally, the codebook 225 may include a first parameter (e.g., an RRC parameter) that enables or disables the UE 115-a from monitoring more than one PDSCH transmission 220 per time slot. In some examples, the network entity 105-a may indicate the first parameter per serving cell (e.g., per CC), per BWP, or per cell group, which may enable the UE 115-a to monitor more than one PDSCH transmission 220 per time slot on a per-CC basis, on a per-BWP basis, or on a per-cell group basis.

[0150] In some examples, the first parameter may configure (e.g., enable, disable) whether the UE 115-a can monitor more than one PDSCH transmission 220 per time slot (e.g., if the network entity 105-a configures the first parameter, the UE 115-a may receive more than one PDSCH transmission 220, and if the network entity 105-a avoids configuring the first parameter, the UE 115-a may fail to monitor more than one PDSCH transmission 220). In this way, the condition regarding whether the UE 115-a indicates the ability to monitor more than one PDSCH per time slot may be replaced with a condition regarding whether the first parameter (e.g., higher layer parameter X) for generating the codebook 225 is provided to the UE 115-a. Alternatively, the first parameter may indicate a maximum number of PDSCH transmissions 220 that the UE 115-a may be able to monitor within a time slot.

[0151] In some examples, the UE 115-a may indicate an ability to monitor a certain number of PDSCH transmissions 220 within a time slot. For example, instead of indicating that the UE 115-a is capable of monitoring more than one PDSCH transmission 220 per CC within a time slot, the capability information 210 may indicate the number of PDSCH transmissions 220 that the UE 115-a is capable of monitoring within a time slot. After monitoring one or more PDSCH transmissions 220 from the network entity 105-a based on the control information 215 and based on the capability information 210 and the first parameter, the UE 115-a may generate a codebook 225 (e.g., a type 1 HARQ-ACK codebook) for the PDSCH transmissions 220. The codebook 225 may include feedback for one or more CCs based on the first parameter. For example, if the first parameter enables the UE 115-a to monitor more than one PDSCH transmission 220 per CC within a time slot, the codebook 225 may include feedback for a set of CCs.

[0152] In some examples, UE 115-a may indicate a separate UE capability that indicates that UE 115-a supports the first parameter. For example, UE 115-a may transmit a second UE capability for monitoring control information 215 that includes the first parameter. In this manner, if UE 115-a transmits the second UE capability, network entity 105-a may transmit control information 215 indicating the first parameter. If UE 115-a avoids indicating the second UE capability, UE 115-a may generate a codebook 225 based on the ability to support monitoring of more than one PDSCH transmission 220 per CC within a time slot.

[0153] In addition, to ensure that both UE 115-a and network entity 105-a understand whether the first parameter is configured, network entity 105-a may send a second parameter (e.g., a second RRC parameter) that enables UE 115-a and network entity 105-a to utilize the first parameter. In some examples, network entity 105-a may configure the second parameter per cell group and the first parameter per CC or per BWP. That is, UE 115-a may receive second control information from network entity 105-a that includes the second parameter, which enables the first parameter on a per-cell group basis, where the first parameter is enabled on a per-CC basis or on a per-BWP basis. In such a case, UE 115-a may determine codebook 225 based on the first parameter.

[0154] Alternatively, the first parameter may explicitly configure whether the UE 115-a is to monitor one or more PDSCH transmissions 220 per time slot, which may ensure that both the UE 115-a and the network entity 105-a understand how many PDSCH transmissions 220 the UE 115-a can receive per time slot. For example, the first parameter may include an explicit {ON, OFF} configuration (indicating whether the UE capability to receive more than one PDSCH transmission 220 within a time slot is on or off) or an explicit {Single PDSCH, Multiple PDSCH} configuration (indicating whether the UE is to monitor a single PDSCH transmission 220 or multiple PDSCH transmissions 220 within a time slot). For example, the first parameter may explicitly configure and enable multiple PDSCH capability per time slot or disable single PDSCH capability per time slot. In such a case, the UE 115-a may perform TDRA grouping based on non-overlapping SLIVs to determine candidate PDSCHs and enable single PDSCH capability per time slot or disable multiple PDSCH capability per time slot. In such cases, UE 115 - a may avoid performing TDRA grouping based on non-overlapping SLIVs and may consider only one bit per time slot (per K1 value) when generating codebook 225 .

[0155] Figure 3 An example of a frame format 300 supporting type 1 HARQ-ACK codebook generation according to one or more aspects of the present disclosure is illustrated. In some examples, the frame format 300 may be implemented by the wireless communication system 100 and the wireless communication system 200. For example, the frame format 300 may be implemented by the wireless communication system 100 and the wireless communication system 200. Figure 1 and Figure 2 The described UE 115 and network entity 105 implement. In some examples, the frame format 300 can depict overlapping and non-overlapping SLIVs 305 that the UE 115 can use to perform TDRA grouping and generate feedback codebooks for one or more PDSCH transmissions.

[0156] As reference Figure 2As described, UE 115-a may transmit capability information indicating the UE's capability for processing PDSCH (e.g., any of pdsch-ProcessingType1-DifferentTB-PerSlot, pdsch-ProcessingType2, pdsch-ProcessingType2-Limited, cbgPDSCH-ProcessingType1-DifferentTB-PerSlot-r16, or cbgPDSCH-ProcessingType2-DifferentTB-PerSlot-r16) and including an indication that UE 115 is capable of monitoring more than one PDSCH transmission per CC within a timeslot. Additionally, UE 115 may receive control information from network entity 105 indicating a codebook (e.g., a Type 1 HARQ-ACK codebook) for HARQ-ACK feedback at UE 115. The codebook may include feedback information (e.g., ACK / NACK bits) related to one or more PDSCH transmissions.

[0157] In some examples, the network entity 105 (via control information) may indicate resources allocated for one or more PDSCH transmissions (e.g., via resource grants), which may be indicated based on the SLIV 305. The SLIV 305 may use a single value to define the starting symbol and the number of consecutive symbols for the PDSCH allocation in a time slot. The control information may indicate multiple SLIVs 305-a and a single SLIV 305-b. In some examples, the frame format 300 may illustrate an example of a PDSCH TDRA that the UE 115 may encounter when receiving the control information. For example, the frame format 300 may include TDRA row 0 and TDRA row 1. Additionally, the frame format 300 may indicate resources across multiple time slots, including time slot n-4, time slot n-3, time slot n-2, time slot n-1, and time slot n.

[0158] In some cases, the UE 115 may generate a codebook for more than one PDSCH transmission received via the resources indicated by the SLIV 305. For a slot with a single SLIV 305-a, the UE 115 may generate a single ACK bit for each slot in the slot for inclusion in the codebook. For example, the UE may generate a single ACK bit for slot n-3. For a slot with non-overlapping SLIVs 305, and if the UE 115 is capable of monitoring more than one PDSCH transmission per slot, the UE 115 may perform TDRA grouping of the non-overlapping SLIVs 305 and include feedback in the codebook for one or more candidate PDSCH opportunities on the CC set, as described herein with reference to Figure 2 described.

[0159] Figure 4 An example of a process flow 400 for supporting Type 1 HARQ-ACK codebook generation according to one or more aspects of the present disclosure is illustrated. The process flow 400 may implement aspects of the wireless communication system 100 and the wireless communication system 200, or may be implemented by aspects of the wireless communication system 100 and the wireless communication system 200. For example, the process flow 400 may illustrate operations between a UE 115-b and a network entity 105-b (which may be examples of corresponding devices described herein). In the following description of the process flow 400, the operations between the UE 115-b and the network entity 105-b may be sent in an order different from the example order shown, or the operations performed by the UE 115-b and the network entity 105-b may be performed in a different order or at different times. Some operations may also be omitted from the process flow 400, and other operations may be added to the process flow 400.

[0160] At 405, UE 115-b may send capability information indicating UE capabilities for processing the PDSCH to network entity 105-b, wherein the capability information includes an indication that UE 115-b is capable of monitoring (and receiving) more than one PDSCH transmission per CC in a timeslot. The UE capabilities may include at least one of a first processing capability, a second processing capability, a restricted second processing capability, or a CBG processing capability.

[0161] At 410, UE 115-b may receive control information from network entity 105-b indicating a codebook to use for HARQ-ACK at UE 115-b. For example, UE 115-b may receive RRC signaling indicating a Type 1 HARQ-ACK codebook configuration.

[0162] At 415, UE 115-b may monitor one or more PDSCH transmissions on one or more CCs based on the control information. The CCs may be in a cell group or in a frequency band of at least one frequency band combination.

[0163] At 420, UE 115-b may determine a first set of CCs in the one or more CCs for which feedback is to be included in the codebook. In some examples, UE 115-b may determine that the first set of CCs includes all CCs in the one or more CCs in the cell group in which UE 115-b monitors the frequency bands for the one or more PDSCH transmissions based on capability information indicating that UE 115-b is capable of monitoring one or more PDSCH transmissions in a time slot for at least one frequency band in a frequency band combination, a frequency band in a frequency band combination that includes a cell group, or a frequency band in a frequency band combination that is consistent with one or more CCs across all frequency bands.

[0164] At 425, UE 115-b may generate a HARQ-ACK codebook for one or more PDSCH transmissions, wherein the codebook is based on the control information and includes feedback for a first set of CCs, the first set of CCs being at least a portion of the one or more CCs, wherein the first set of CCs for which feedback is included is based on a frequency band associated with an indication in the capability information. In some examples, UE 115-b may include feedback for the first set of CCs based on a TDRA group of non-overlapping SLIVs associated with the one or more candidate PDSCH opportunities.

[0165] Figure 5 An example of a process flow 500 for supporting Type 1 HARQ-ACK codebook generation according to one or more aspects of the present disclosure is illustrated. The process flow 500 may implement aspects of the wireless communication system 100 and the wireless communication system 200, or may be implemented by aspects of the wireless communication system 100 and the wireless communication system 200. For example, the process flow 500 may illustrate operations between a UE 115-c and a network entity 105-c (which may be examples of corresponding devices described herein). In the following description of the process flow 500, operations between the UE 115-c and the network entity 105-c may be sent in a different order than the example order shown, or operations performed by the UE 115-c and the network entity 105-c may be performed in a different order or at different times. Some operations may also be omitted from the process flow 500, and other operations may be added to the process flow 500.

[0166] At 505, the UE 115-c may send capability information indicating UE capabilities for processing the PDSCH to the network entity 105-c, wherein the capability information includes an indication of a number of PDSCH transmissions that the UE 115-c is capable of that the UE 115-c is capable of monitoring within the time slot. The UE capabilities may include at least one of a first processing capability, a second processing capability, a restricted second processing capability, or a CBG processing capability.

[0167] At 510, the UE 115-c may receive control information from the network entity 105-c indicating a codebook for HARQ-ACK at the UE 115-c, wherein the control information includes a first parameter (e.g., an RRC parameter) that disables or enables the UE 115-c to monitor more than one PDSCH per time slot. In other words, the first parameter may indicate whether the UE 115-c may receive more than one PDSCH per time slot, such that the UE 115-c may generate a codebook (e.g., a Type 1 HARQ-ACK codebook) accordingly.

[0168] The UE 115-c may monitor one or more PDSCH transmissions on one or more CCs at 515. The CCs may be in a cell group or in a frequency band of at least one frequency band combination.

[0169] At 520, the UE 115-c may receive second control information from the network entity 105-c including a second parameter that enables the first parameter on a per-cell group basis, where the first parameter is on a per-CC basis or on a per-BWP basis. That is, the second parameter may indicate to the UE 115-c and the network entity 105-c that the first parameter is configured and that the UE 115-c is to enable the capability based on the first parameter (rather than based on the capability as referred to herein). Figure 4 15 - c ) to support more than one PDSCH transmission per time slot.

[0170] At 525, the UE 115-c may generate a HARQ-ACK codebook for one or more PDSCH transmissions, wherein the codebook is based on the control information and includes feedback for the first set of CCs based on the first parameters. For example, if the first parameters enable the UE 115-c to support reception of more than one PDSCH opportunity per slot, the UE 115-c may include feedback for the first set of CCs in the codebook.

[0171] Figure 6 A block diagram 600 illustrates a device 605 that supports type 1 HARQ-ACK codebook generation according to one or more aspects of the present disclosure. The device 605 can be an example of aspects of the UE 115 as described herein. The device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. The device 605 may also include a processor. Each of these components can communicate with each other (e.g., via one or more buses).

[0172] The receiver 610 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels related to type 1 HARQ-ACK codebook generation, data channels, information channels). The information may be delivered to other components of the device 605. The receiver 610 may utilize a single antenna or a collection of multiple antennas.

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

[0174] The communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of Type 1 HARQ-ACK codebook generation as described herein. For example, the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may support methods for performing one or more of the functions described herein.

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

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

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

[0178] According to examples disclosed herein, the communication manager 620 may support wireless communications at a UE. For example, the communication manager 620 may be configured as or otherwise support means for sending capability information indicating the UE's capability to process a PDSCH, wherein the capability information includes an indication that the UE is capable of monitoring more than one downlink shared channel transmission per CC within a time slot. The communication manager 620 may be configured as or otherwise support means for receiving control information indicating a codebook for HARQ-ACK at the UE. The communication manager 620 may be configured as or otherwise support means for monitoring one or more downlink shared channel transmissions on one or more CCs based on the control information. The communication manager 620 may be configured as or otherwise support means for generating a codebook for HARQ-ACK for one or more downlink shared channel transmissions, wherein the codebook is based on the control information and includes feedback for a first set of CCs, the first set of CCs being at least a portion of the one or more CCs, wherein the first set of CCs for which feedback is included is based on a frequency band associated with the indication in the capability information.

[0179] Additionally or alternatively, according to examples disclosed herein, the communication manager 620 may support wireless communications at a UE. For example, the communication manager 620 may be configured as or otherwise support means for receiving control information indicating a codebook for HARQ-ACK at the UE, wherein the control information includes a first parameter that disables or enables the UE to monitor more than one downlink shared channel transmission per time slot based on the control information. The communication manager 620 may be configured as or otherwise support means for monitoring one or more downlink shared channel transmissions based on the control information. The communication manager 620 may be configured as or otherwise support means for generating a codebook for HARQ-ACK for one or more downlink shared channel transmissions, wherein the codebook is based on the control information and includes feedback for one or more CCs based on the first parameter.

[0180] By including or configuring the communication manager 620 according to the examples described herein, the device 605 (e.g., a processor controlling the receiver 610, the transmitter 615, the communication manager 620, or a combination thereof or otherwise coupled thereto) can support techniques for indicating Type 1 HARQ-ACK codebook capabilities, which can improve resource utilization, clarify the UE's ability to receive more than one PDSCH per time slot, and ensure peer network entity capabilities to improve communication between the UE and the network entity.

[0181] Figure 7 A block diagram 700 illustrates a device 705 that supports type 1 HARQ-ACK codebook generation according to one or more aspects of the present disclosure. The device 705 can be an example of aspects of the device 605 or UE 115 as described herein. The device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. The device 705 may also include a processor. Each of these components can communicate with each other (e.g., via one or more buses).

[0182] The receiver 710 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels related to type 1 HARQ-ACK codebook generation, data channels, information channels). The information may be delivered to other components of the device 705. The receiver 710 may utilize a single antenna or a collection of multiple antennas.

[0183] The transmitter 715 may provide means for transmitting signals generated by other components of the device 705. For example, the transmitter 715 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels related to type 1 HARQ-ACK codebook generation, data channels, information channels). In some examples, the transmitter 715 may be co-located with the receiver 710 in a transceiver module. The transmitter 715 may utilize a single antenna or a collection of multiple antennas.

[0184] The device 705 or its various components may be examples of components for performing various aspects of type 1 HARQ-ACK codebook generation as described herein. For example, the communication manager 720 may include a capability component 725, a control information component 730, a PDSCH component 735, a codebook component 740, a parameter component 745, or any combination thereof. The communication manager 720 may be an example of aspects of the communication manager 620 as described herein. In some examples, the communication manager 720 or its various components may be configured to use or otherwise cooperate with the receiver 710, the transmitter 715, or both to perform various operations (e.g., receive, obtain, monitor, output, transmit). For example, the communication manager 720 may receive information from the receiver 710, transmit information to the transmitter 715, or be integrated with the receiver 710, the transmitter 715, or both to obtain information, output information, or perform various other operations as described herein.

[0185] According to examples disclosed herein, a communication manager 720 may support wireless communications at a UE. A capability component 725 may be configured as or otherwise support means for transmitting capability information indicating the UE's capability to process a PDSCH, wherein the capability information includes an indication that the UE is capable of monitoring more than one downlink shared channel transmission per CC within a time slot. A control information component 730 may be configured as or otherwise support means for receiving control information indicating a codebook for HARQ-ACK at the UE. A PDSCH component 735 may be configured as or otherwise support means for monitoring one or more downlink shared channel transmissions on one or more CCs based on the control information. A codebook component 740 may be configured as or otherwise support means for generating a codebook for HARQ-ACK for one or more downlink shared channel transmissions, wherein the codebook is based on the control information and includes feedback for a first set of CCs, the first set of CCs being at least a portion of the one or more CCs, wherein the first set of CCs for which feedback is included is based on a frequency band associated with the indication in the capability information.

[0186] Additionally or alternatively, according to examples as disclosed herein, the communication manager 720 may support wireless communications at a UE. The parameter component 745 may be configured as or otherwise support means for receiving control information indicating a codebook for HARQ-ACK at the UE, wherein the control information includes a first parameter that disables or enables the UE to monitor more than one downlink shared channel transmission per time slot. The PDSCH component 735 may be configured as or otherwise support means for monitoring one or more downlink shared channel transmissions based on the control information. The codebook component 740 may be configured as or otherwise support means for generating a codebook for HARQ-ACK for one or more downlink shared channel transmissions, wherein the codebook is based on the control information and includes feedback for one or more CCs based on the first parameter.

[0187] Figure 8 A block diagram 800 illustrates a communication manager 820 that supports type 1 HARQ-ACK codebook generation according to one or more aspects of the present disclosure. The communication manager 820 can be an example of aspects of the communication manager 620, the communication manager 720, or both as described herein. The communication manager 820 or its various components can be examples of means for performing various aspects of type 1 HARQ-ACK codebook generation as described herein. For example, the communication manager 820 can include a capability component 825, a control information component 830, a PDSCH component 835, a codebook component 840, a parameter component 845, a TDRA grouping component 850, a capability control component 855, a parameter control component 860, a capability indication component 865, or any combination thereof. Each of these components can communicate with each other directly or indirectly (e.g., via one or more buses).

[0188] According to examples disclosed herein, a communication manager 820 may support wireless communications at a UE. A capability component 825 may be configured as or otherwise support means for transmitting capability information indicating the UE's capability to process a PDSCH, wherein the capability information includes an indication that the UE is capable of monitoring more than one downlink shared channel transmission per CC within a time slot. A control information component 830 may be configured as or otherwise support means for receiving control information indicating a codebook for HARQ-ACK at the UE. A PDSCH component 835 may be configured as or otherwise support means for monitoring one or more downlink shared channel transmissions on one or more CCs based on the control information. A codebook component 840 may be configured as or otherwise support means for generating a codebook for HARQ-ACK for one or more downlink shared channel transmissions, wherein the codebook is based on the control information and includes feedback for a first set of CCs, the first set of CCs being at least a portion of the one or more CCs, wherein the first set of CCs for which feedback is included is based on a frequency band associated with the indication in the capability information.

[0189] In some examples, to support codebook generation, the TDRA grouping component 850 may be configured as or otherwise support means for feedback of candidate downlink shared channel opportunities on a first set of CCs including a non-overlapping SLIV (SLIV) based TDRA (TDRA) group.

[0190] In some examples, the TDRA grouping component 850 may be configured as or otherwise support a component for determining a first set of CCs as all CCs in one or more CCs in a cell group based on an indication in the capability information indicating that the UE is capable of monitoring more than one downlink shared channel transmission within a time slot for at least one frequency band in at least one frequency band combination.

[0191] In some examples, the TDRA grouping component 850 may be configured as or otherwise support a component for determining a first set of CCs as all CCs in one or more CCs in a cell group based on an indication in the capability information indicating that the UE is capable of monitoring more than one downlink shared channel transmission within a time slot for at least a frequency band in at least one frequency band combination that includes the cell group.

[0192] In some examples, the TDRA grouping component 850 may be configured as or otherwise support means for determining a first set of CCs as all CCs in one or more CCs in a frequency band based on an indication in the capability information indicating that the UE is capable of monitoring more than one downlink shared channel transmission within a time slot for a frequency band in at least one frequency band combination.

[0193] In some examples, the TDRA grouping component 850 may be configured as or otherwise support means for determining a first set of CCs as all CCs in one or more CCs in a frequency band based on an indication in the capability information indicating that the UE is capable of monitoring more than one downlink shared channel transmission within a time slot for a frequency band in at least one frequency band combination, where at least one frequency band combination corresponds to one or more CCs in the one or more frequency bands.

[0194] In some examples, to support codebook generation, the TDRA grouping component 850 may be configured as or otherwise support a component for including feedback for a single candidate downlink shared channel opportunity on a second set of CCs without identifying a TDRA (TDRA) group for non-overlapping SLIVs (SLIVs).

[0195] In some examples, in addition to the CBG processing capability, the UE capabilities for processing the PDSCH included in the capability information also include one or more of the following: a first UE capability associated with a first processing capability, a second UE capability associated with a second processing capability applicable to a set of multiple subcarrier spacings, and a restricted second UE capability associated with a second processing capability applicable to a subset of the set of multiple subcarrier spacings, wherein the first processing capability and the second processing capability are different.

[0196] In some examples, capability indication component 865 may be configured as or otherwise support means for determining that the UE is capable of monitoring more than one downlink shared channel transmission within a timeslot based on an indication associated with the first UE capability without enabling the CBG processing type.

[0197] In some examples, the capability indication component 865 may be configured as or otherwise support a component for determining that the UE is capable of monitoring more than one downlink shared channel transmission within a time slot based on second control information enabling at least one of a second UE processing type or a restricted second UE processing type for the UE.

[0198] In some examples, the capability indication component 865 may be configured as or otherwise support a component for determining that the UE is capable of monitoring more than one downlink shared channel transmission within a timeslot based on an indication associated with the first UE capability and in the absence of an enabled second UE processing type, a restricted second UE processing type, and a CBG processing type.

[0199] In some examples, capability indication component 865 can be configured as or otherwise support means for receiving second control information enabling a CBG process type for the UE. In some examples, capability indication component 865 can be configured as or otherwise support means for determining that the UE is capable of monitoring more than one downlink shared channel transmission within a timeslot based on the indication being associated with the first UE capability and based on the CBG process type being enabled, and in the absence of an enabled second UE process type and a restricted second UE process type.

[0200] In some examples, capability indication component 865 can be configured as or otherwise support means for receiving second control information that the CBG processing type is enabled for the UE and at least one of the second UE processing type or the restricted second UE processing type is enabled for the UE. In some examples, capability indication component 865 can be configured as or otherwise support means for determining that the UE is capable of monitoring more than one downlink shared channel transmission within a timeslot based on the indication being associated with one of the second UE processing type or the restricted second UE processing type and based on the CBG processing type being enabled.

[0201] In some examples, capability indication component 865 can be configured as or otherwise support means for receiving second control information enabling at least one of the second UE processing type or the restricted second UE processing type for the UE. In some examples, capability indication component 865 can be configured as or otherwise support means for determining that the UE is capable of monitoring more than one downlink shared channel transmission within a timeslot based on the indication being associated with one of the second UE processing type or the restricted second UE processing type and in the absence of an enabled CBG processing type.

[0202] In some examples, the capability indication component 865 may be configured as or otherwise support a component for determining that the UE is capable of monitoring more than one downlink shared channel transmission within a time slot and also indicating that the UE is capable of monitoring more than one downlink shared channel transmission within a time slot based on at least one of a second UE processing type or a restricted second UE processing type.

[0203] Additionally or alternatively, according to examples as disclosed herein, the communication manager 820 may support wireless communications at the UE. The parameter component 845 may be configured as or otherwise support a component for receiving control information indicating a codebook for HARQ-ACK at the UE, wherein the control information includes a first parameter that disables or enables the UE to monitor more than one downlink shared channel transmission per time slot. In some examples, the PDSCH component 835 may be configured as or otherwise support a component for monitoring one or more downlink shared channel transmissions based on the control information. In some examples, the codebook component 840 may be configured as or otherwise support a component for generating a codebook for HARQ-ACK for one or more downlink shared channel transmissions, wherein the codebook is based on the control information and includes feedback for one or more CCs based on the first parameter.

[0204] In some examples, capability component 825 may be configured as or otherwise support means for sending capability information indicating UE capabilities for processing PDSCH, wherein the capability information includes an indication of a number of downlink shared channel transmissions that the UE is capable of monitoring within a timeslot.

[0205] In some examples, the first parameter enables the UE to monitor more than one downlink shared channel transmission per timeslot on a per CC basis, or on a per bandwidth part basis, or on a per cell group basis.

[0206] In some examples, to support receiving control information, parameter component 845 can be configured as or otherwise support means for receiving a second indication of a maximum number of downlink shared channel transmissions that the UE can monitor within a timeslot.

[0207] In some examples, capability control component 855 can be configured as or otherwise support means for sending second UE capabilities for monitoring control information including the first parameter.

[0208] In some examples, parameter control component 860 may be configured as or otherwise support means for receiving second control information including a second parameter that enables the first parameter on a per-cell group basis, where the first parameter is on a per-CC basis or on a per-bandwidth portion basis.

[0209] In some examples, to support receiving control information, parameter component 845 may be configured as or otherwise support means for receiving a first parameter, where the first parameter enables the UE to monitor more than one downlink shared channel transmission per time slot or disables the UE from monitoring a single downlink shared channel transmission per time slot.

[0210] In some examples, to support receiving control information, parameter component 845 may be configured as or otherwise support a component for receiving a first parameter, where the first parameter enables the UE to monitor a single downlink shared channel transmission per time slot or disables the UE from monitoring more than one downlink shared channel transmission per time slot.

[0211] Figure 9 A diagram illustrating a system 900 including a device 905 supporting type 1 HARQ-ACK codebook generation according to one or more aspects of the present disclosure is shown. The device 905 may be an example of, or include components of, the device 605, device 705, or UE 115 as described herein. The device 905 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 905 may include components for two-way voice and data communication, including components for sending and receiving communications, such as a communication manager 920, an input / output (I / O) controller 910, a transceiver 915, an antenna 925, a memory 930, code 935, and a processor 940. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 945).

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

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

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

[0215] The processor 940 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 940 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 940. The processor 940 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 930) to cause the device 905 to perform various functions (e.g., functions or tasks supporting type 1 HARQ-ACK codebook generation). For example, the device 905 or a component of the device 905 may include a processor 940 and a memory 930 coupled to or coupled to the processor 940, the processor 940 and the memory 930 being configured to perform the various functions described herein.

[0216] According to examples disclosed herein, the communication manager 920 may support wireless communications at a UE. For example, the communication manager 920 may be configured as or otherwise support means for transmitting capability information indicating the UE's capability to process a PDSCH, wherein the capability information includes an indication that the UE is capable of monitoring more than one downlink shared channel transmission per CC within a time slot. The communication manager 920 may be configured as or otherwise support means for receiving control information indicating a codebook for HARQ-ACK at the UE. The communication manager 920 may be configured as or otherwise support means for monitoring one or more downlink shared channel transmissions on one or more CCs based on the control information. The communication manager 920 may be configured as or otherwise support means for generating a codebook for HARQ-ACK for one or more downlink shared channel transmissions, wherein the codebook is based on the control information and includes feedback for a first set of CCs, the first set of CCs being at least a portion of the one or more CCs, wherein the first set of CCs for which feedback is included is based on a frequency band associated with the indication in the capability information.

[0217] Additionally or alternatively, according to examples disclosed herein, the communication manager 920 may support wireless communications at a UE. For example, the communication manager 920 may be configured as or otherwise support means for receiving control information indicating a codebook for HARQ-ACK at the UE, wherein the control information includes a first parameter that disables or enables the UE to monitor more than one downlink shared channel transmission per time slot. The communication manager 920 may be configured as or otherwise support means for monitoring one or more downlink shared channel transmissions based on the control information. The communication manager 920 may be configured as or otherwise support means for generating a codebook for HARQ-ACK for one or more downlink shared channel transmissions, wherein the codebook is based on the control information and includes feedback for one or more CCs based on the first parameter.

[0218] By including or configuring the communication manager 920 according to the examples described herein, the device 905 can support techniques for indicating Type 1 HARQ-ACK codebook capabilities, which can improve resource utilization, clarify the UE's ability to receive more than one PDSCH per time slot, and ensure peer network entity capabilities to improve communication between the UE and the network entity.

[0219] In some examples, the communication manager 920 can be configured to use or otherwise cooperate with the transceiver 915, one or more antennas 925, or any combination thereof to perform various operations (e.g., receive, monitor, transmit). Although the communication manager 920 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 920 can be supported or performed by the processor 940, the memory 930, the code 935, or any combination thereof. For example, the code 935 may include instructions that can be executed by the processor 940 to cause the device 905 to perform various aspects of type 1 HARQ-ACK codebook generation as described herein, or the processor 940 and the memory 930 may be otherwise configured to perform or support such operations.

[0220] Figure 10 A block diagram 1000 illustrates a device 1005 that supports type 1 HARQ-ACK codebook generation according to one or more aspects of the present disclosure. The device 1005 may be an example of aspects of the network entity 105 as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. The device 1005 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0221] Receiver 1010 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of device 1005. In some examples, receiver 1010 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1010 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0222] The transmitter 1015 may provide means for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of the device 1005. For example, the transmitter 1015 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 1015 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, the transmitter 1015 may support outputting information by transmitting signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1015 and the receiver 1010 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0223] The communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of Type 1 HARQ-ACK codebook generation as described herein. For example, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may support methods for performing one or more of the functions described herein.

[0224] In some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof can be implemented in hardware (e.g., in a communication management circuit). The hardware can include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic components, discrete hardware components, or any combination thereof configured as or otherwise supporting components for performing the functions described in this disclosure. In some examples, the processor and a memory coupled to the processor can be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

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

[0226] In some examples, communication manager 1020 can be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with receiver 1010, transmitter 1015, or both. For example, communication manager 1020 can receive information from receiver 1010, transmit information to transmitter 1015, or be integrated in conjunction with receiver 1010, transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.

[0227] According to examples as disclosed herein, the communication manager 1020 may support wireless communications at a network entity. For example, the communication manager 1020 may be configured as or otherwise support means for receiving capability information indicating UE capabilities for processing PDSCH, wherein the capability information includes an indication that the UE is capable of monitoring more than one downlink shared channel transmission per CC within a time slot. The communication manager 1020 may be configured as or otherwise support means for sending control information indicating a codebook for HARQ-ACK at the UE. The communication manager 1020 may be configured as or otherwise support means for sending one or more downlink shared channel transmissions on one or more CCs. The communication manager 1020 may be configured as or otherwise support means for receiving feedback for a first set of CCs, the first set of CCs being at least a portion of the one or more CCs, the feedback being included in the codebook, wherein the first set of CCs for which the feedback is included is based on a frequency band associated with the indication in the capability information.

[0228] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1020 may support wireless communications at a network entity. For example, the communication manager 1020 may be configured as or otherwise support means for transmitting control information indicating a codebook for HARQ-ACK at a UE, wherein the control information includes a first parameter that disables or enables the UE to monitor more than one downlink shared channel transmission per time slot. The communication manager 1020 may be configured as or otherwise support means for transmitting one or more downlink shared channel transmissions. The communication manager 1020 may be configured as or otherwise support means for receiving feedback for one or more CCs based on the first parameter, wherein the feedback is included in a codebook for HARQ-ACK for the one or more downlink shared channel transmissions, and wherein the codebook is based on the control information.

[0229] By including or configuring the communication manager 1020 according to the examples described herein, the device 1005 (e.g., a processor controlling the receiver 1010, the transmitter 1015, the communication manager 1020, or a combination thereof or otherwise coupled thereto) can support techniques for indicating Type 1 HARQ-ACK codebook capabilities, which can improve resource utilization, clarify the UE's ability to receive more than one PDSCH per time slot, and ensure peer network entity capabilities to improve communication between the UE and the network entity.

[0230] Figure 11 A block diagram 1100 illustrates a device 1105 that supports type 1 HARQ-ACK codebook generation according to one or more aspects of the present disclosure. The device 1105 may be an example of aspects of the device 1005 or network entity 105 as described herein. The device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120. The device 1105 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0231] Receiver 1110 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of device 1105. In some examples, receiver 1110 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1110 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0232] The transmitter 1115 may provide means for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of the device 1105. For example, the transmitter 1115 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 1115 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, the transmitter 1115 may support outputting information by transmitting signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1115 and the receiver 1110 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0233] Device 1105 or its various components may be examples of means for performing various aspects of Type 1 HARQ-ACK codebook generation as described herein. For example, communication manager 1120 may include capability manager 1125, codebook manager 1130, PDSCH manager 1135, feedback manager 1140, parameter manager 1145, or any combination thereof. Communication manager 1120 may be an example of aspects of communication manager 1020 as described herein. In some examples, communication manager 1120 or its various components may be configured to use or otherwise cooperate with receiver 1110, transmitter 1115, or both to perform various operations (e.g., receive, obtain, monitor, output, transmit). For example, communication manager 1120 may receive information from receiver 1110, transmit information to transmitter 1115, or be integrated with receiver 1110, transmitter 1115, or both to obtain information, output information, or perform various other operations as described herein.

[0234] According to examples as disclosed herein, a communication manager 1120 may support wireless communications at a network entity. A capability manager 1125 may be configured as or otherwise support means for receiving capability information indicating UE capabilities for processing PDSCH, wherein the capability information includes an indication that the UE is capable of monitoring more than one downlink shared channel transmission per CC within a timeslot. A codebook manager 1130 may be configured as or otherwise support means for sending control information indicating a codebook for HARQ-ACK at the UE. A PDSCH manager 1135 may be configured as or otherwise support means for sending one or more downlink shared channel transmissions on one or more CCs. A feedback manager 1140 may be configured as or otherwise support means for receiving feedback for a first set of CCs, the first set of CCs being at least a portion of the one or more CCs, the feedback being included in a codebook, wherein the first set of CCs for which feedback is included is based on a frequency band associated with the indication in the capability information.

[0235] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1120 may support wireless communications at a network entity. The parameter manager 1145 may be configured as or otherwise support means for transmitting control information indicating a codebook for HARQ-ACK at a UE, wherein the control information includes a first parameter that disables or enables the UE to monitor more than one downlink shared channel transmission per time slot. The PDSCH manager 1135 may be configured as or otherwise support means for transmitting one or more downlink shared channel transmissions. The feedback manager 1140 may be configured as or otherwise support means for receiving feedback for one or more CCs based on the first parameter, wherein the feedback is included in a codebook for HARQ-ACK for the one or more downlink shared channel transmissions, and wherein the codebook is based on the control information.

[0236] Figure 12 A block diagram 1200 illustrates a communication manager 1220 that supports type 1 HARQ-ACK codebook generation according to one or more aspects of the present disclosure. The communication manager 1220 may be an example of aspects of the communication manager 1020, the communication manager 1120, or both, as described herein. The communication manager 1220 or its various components may be examples of means for performing various aspects of type 1 HARQ-ACK codebook generation as described herein. For example, the communication manager 1220 may include a capability manager 1225, a codebook manager 1230, a PDSCH manager 1235, a feedback manager 1240, a parameter manager 1245, a TDRA grouping manager 1250, a parameter control manager 1255, a capability configuration manager 1260, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses), which communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0237] According to examples as disclosed herein, a communication manager 1220 may support wireless communications at a network entity. A capability manager 1225 may be configured as or otherwise support means for receiving capability information indicating UE capabilities for processing PDSCH, wherein the capability information includes an indication that the UE is capable of monitoring more than one downlink shared channel transmission per CC within a timeslot. A codebook manager 1230 may be configured as or otherwise support means for sending control information indicating a codebook for HARQ-ACK at the UE. A PDSCH manager 1235 may be configured as or otherwise support means for sending one or more downlink shared channel transmissions on one or more CCs. A feedback manager 1240 may be configured as or otherwise support means for receiving feedback for a first set of CCs, the first set of CCs being at least a portion of the one or more CCs, the feedback being included in a codebook, wherein the first set of CCs for which feedback is included is based on a frequency band associated with the indication in the capability information.

[0238] In some examples, to support receiving feedback, feedback manager 1240 may be configured as or otherwise support means for receiving feedback of candidate downlink shared channel opportunities on a first set of CCs for a non-overlapping SLIV (SLIV) based TDRA (TDRA) group.

[0239] In some examples, the TDRA group manager 1250 may be configured as or otherwise support means for determining a first set of CCs as all CCs in one or more CCs in a cell group based on an indication in the capability information indicating that the UE is capable of monitoring more than one downlink shared channel transmission within a time slot for at least one frequency band in at least one frequency band combination.

[0240] In some examples, the TDRA group manager 1250 may be configured as or otherwise support means for determining a first set of CCs as all CCs in one or more CCs in a cell group based on an indication in the capability information indicating that the UE is capable of monitoring more than one downlink shared channel transmission within a time slot for at least a frequency band in at least one frequency band combination comprising the cell group.

[0241] In some examples, the TDRA group manager 1250 may be configured as or otherwise support means for determining a first set of CCs as all CCs in one or more CCs in a frequency band based on an indication in the capability information indicating that the UE is capable of monitoring more than one downlink shared channel transmission within a time slot for a frequency band in at least one frequency band combination.

[0242] In some examples, the TDRA group manager 1250 may be configured as or otherwise support means for determining a first set of CCs as all CCs in one or more CCs in a frequency band based on an indication in the capability information indicating that the UE is capable of monitoring more than one downlink shared channel transmission within a time slot for a frequency band in at least one frequency band combination, where at least one frequency band combination corresponds to one or more CCs in the one or more frequency bands.

[0243] In some examples, to support receiving feedback, the TDRA group manager 1250 may be configured as or otherwise support means for receiving feedback for a single candidate downlink shared channel opportunity on a second set of CCs without identifying a TDRA (TDRA) group of non-overlapping SLIVs (SLIVs).

[0244] In some examples, in addition to the CBG processing capability, the UE capabilities for processing the PDSCH included in the capability information also include one or more of the following: a first UE capability associated with a first processing capability, a second UE capability associated with a second processing capability applicable to a set of multiple subcarrier spacings, and a restricted second UE capability associated with a second processing capability applicable to a subset of the set of multiple subcarrier spacings, wherein the first processing capability and the second processing capability are different.

[0245] In some examples, capability configuration manager 1260 may be configured as or otherwise support means for determining that a UE is capable of monitoring more than one downlink shared channel transmission within a timeslot based on an indication associated with a first UE capability without enabling a CBG processing type.

[0246] In some examples, the capability configuration manager 1260 may be configured as or otherwise support a component for determining that the UE is capable of monitoring more than one downlink shared channel transmission within a time slot based on second control information enabling at least one of a second UE processing type or a restricted second UE processing type for the UE.

[0247] In some examples, the capability configuration manager 1260 may be configured as or otherwise support components for determining that the UE is capable of monitoring more than one downlink shared channel transmission within a timeslot based on an indication associated with the first UE capability and in the absence of an enabled second UE processing type, a restricted second UE processing type, and a CBG processing type.

[0248] In some examples, capability configuration manager 1260 can be configured as or otherwise support means for transmitting second control information for enabling a CBG process type for the UE. In some examples, capability configuration manager 1260 can be configured as or otherwise support means for determining that the UE is capable of monitoring more than one downlink shared channel transmission within a timeslot based on an indication associated with a first UE capability and based on the CBG process type being enabled, and in the absence of an enabled second UE process type and a restricted second UE process type.

[0249] In some examples, the capability configuration manager 1260 can be configured as or otherwise support means for transmitting second control information that enables the CBG processing type for the UE and enables at least one of the second UE processing type or the restricted second UE processing type for the UE. In some examples, the capability configuration manager 1260 can be configured as or otherwise support means for determining that the UE is capable of monitoring more than one downlink shared channel transmission within a timeslot based on an indication associated with one of the second UE processing type or the restricted second UE processing type and based on the CBG processing type being enabled.

[0250] In some examples, the capability configuration manager 1260 can be configured as or otherwise support means for sending second control information that enables at least one of the second UE processing type or the restricted second UE processing type for the UE. In some examples, the capability configuration manager 1260 can be configured as or otherwise support means for determining that the UE is capable of monitoring more than one downlink shared channel transmission within a timeslot based on the indication being associated with one of the second UE processing type or the restricted second UE processing type and in the absence of an enabled CBG processing type.

[0251] In some examples, determining that the UE is capable of monitoring more than one downlink shared channel transmission within the time slot is also based on at least one of the second UE processing type or the restricted second UE processing type indicating that the UE is capable of monitoring more than one downlink shared channel transmission within the time slot.

[0252] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1220 may support wireless communications at a network entity. The parameter manager 1245 may be configured as or otherwise support means for sending control information indicating a codebook for HARQ-ACK at a UE, wherein the control information includes a first parameter that disables or enables the UE to monitor more than one downlink shared channel transmission per time slot. In some examples, the PDSCH manager 1235 may be configured as or otherwise support means for sending one or more downlink shared channel transmissions. In some examples, the feedback manager 1240 may be configured as or otherwise support means for receiving feedback for one or more CCs based on a first parameter, wherein the feedback is included in a codebook for HARQ-ACK for one or more downlink shared channel transmissions, and wherein the codebook is based on the control information.

[0253] In some examples, capability manager 1225 may be configured as or otherwise support means for receiving capability information indicating UE capabilities for processing PDSCH, where the capability information includes an indication of a number of downlink shared channel transmissions that the UE is capable of monitoring within a timeslot.

[0254] In some examples, the first parameter enables the UE to monitor more than one downlink shared channel transmission per timeslot on a per CC basis, or on a per bandwidth part basis, or on a per cell group basis.

[0255] In some examples, to support sending control information, parameter manager 1245 can be configured as or otherwise support means for sending a second indication of a maximum number of downlink shared channel transmissions that the UE can monitor within a timeslot.

[0256] In some examples, parameter control manager 1255 may be configured as or otherwise support means for receiving second UE capabilities for monitoring control information including the first parameter.

[0257] In some examples, the parameter control manager 1255 may be configured as or otherwise support means for sending second control information including a second parameter that enables the first parameter on a per-cell group basis, where the first parameter is on a per-CC basis or on a per-bandwidth portion basis.

[0258] In some examples, to support sending control information, parameter manager 1245 may be configured as or otherwise support a component for sending a first parameter, where the first parameter enables the UE to monitor more than one downlink shared channel transmission per time slot or disables the UE from monitoring a single downlink shared channel transmission per time slot.

[0259] In some examples, to support sending control information, parameter manager 1245 may be configured as or otherwise support a component for sending a first parameter, where the first parameter enables the UE to monitor a single downlink shared channel transmission per time slot or disables the UE from monitoring more than one downlink shared channel transmission per time slot.

[0260] Figure 13 A diagram of a system 1300 including a device 1305 supporting type 1 HARQ-ACK codebook generation according to one or more aspects of the present disclosure is illustrated. Device 1305 may be an example of, or include components of, device 1005, device 1105, or network entity 105 as described herein. Device 1305 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communication via one or more wired interfaces, via one or more wireless interfaces, or any combination thereof. Device 1305 may include components that support outgoing and incoming communications, such as a communication manager 1320, a transceiver 1310, an antenna 1315, a memory 1325, code 1330, and a processor 1335. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1340).

[0261] The transceiver 1310 may support bidirectional communication via a wired link, a wireless link, or both as described herein. In some examples, the transceiver 1310 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1310 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1305 may include one or more antennas 1315, which may be capable of transmitting or receiving wireless transmissions (e.g., concurrently). The transceiver 1310 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., via one or more antennas 1315, via a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1315, from a wired receiver); and demodulating the signal. In some implementations, the transceiver 1310 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1315 configured to support various receive or obtain operations, or one or more interfaces coupled to one or more antennas 1315 configured to support various transmit or output operations, or a combination thereof. In some implementations, the transceiver 1310 may include or be configured to be coupled to one or more processors or memory components operable to perform or support operations based on received or obtained information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some implementations, the transceiver 1310, or the transceiver 1310 and one or more antennas 1315, or the transceiver 1310 and one or more antennas 1315 and one or more processors or memory components (e.g., processor 1335 or memory 1325 or both) may be included in a chip or chip assembly installed in the device 1305. In some examples, the transceiver is operable to support communications via one or more communication links (eg, communication link 125 , backhaul communication link 120 , midhaul communication link 162 , fronthaul communication link 168 ).

[0262] Memory 1325 may include RAM and ROM. Memory 1325 may store computer-readable, computer-executable code 1330 including instructions that, when executed by processor 1335, cause device 1305 to perform the various functions described herein. Code 1330 may be stored in a non-transitory computer-readable medium (such as system memory or another type of memory). In some cases, code 1330 may not be directly executable by processor 1335, but may (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some cases, memory 1325 may contain, for example, a BIOS that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0263] The processor 1335 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or any combination thereof). In some cases, the processor 1335 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1335. The processor 1335 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 1325) to cause the device 1305 to perform various functions (e.g., functions or tasks supporting type 1 HARQ-ACK codebook generation). For example, the device 1305 or a component of the device 1305 may include a processor 1335 and a memory 1325 coupled to the processor 1335, the processor 1335 and the memory 1325 being configured to perform the various functions described herein. The processor 1335 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software (such as an operating system, virtual machine, or container instance)) that can host functionality (e.g., by executing code 1330) to perform the functions of the device 1305. The processor 1335 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1305 (such as in the memory 1325). In some implementations, the processor 1335 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 (which may be passed to other systems or components of the device 1305, for example). For example, the processing system of the device 1305 may refer to a system that includes various other components or subcomponents of the device 1305, such as the processor 1335, or the transceiver 1310, or the communication manager 1320, or other components or combinations of components of the device 1305. The processing system of device 1305 can be interfaced with other components of device 1305 and can process information (such as input or signals) received from other components or output information to other components. For example, the chip or modem of device 1305 may include a processing system and one or more interfaces for outputting information or for obtaining information, or both. The one or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to obtain information, or the same interface configured to output information and obtain information, among other specific implementations. In some specific implementations, the one or more interfaces may refer to an interface between the processing system of the chip or modem and a transmitter, so that device 1305 can transmit information output from the chip or modem.Additionally or alternatively, in some implementations, the one or more interfaces may refer to an interface between a processing system of a chip or modem and a receiver, such that the device 1305 can obtain information or signal input and the information can be transmitted to the processing system. A person skilled in the art will readily recognize that the first interface can also obtain information or signal input, and the second interface can also output information or signal output.

[0264] In some examples, bus 1340 may support communications for protocol layers of a protocol stack (e.g., within a protocol layer). In some examples, bus 1340 may support communications associated with logical channels of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within components of device 1305 or between different components of device 1305 that may be co-located or located in different locations (e.g., where device 1305 may refer to a system in which one or more of communication manager 1320, transceiver 1310, memory 1325, code 1330, and processor 1335 may be located in one of the different components or divided between the different components).

[0265] In some examples, communication manager 1320 can manage aspects of communications with core network 130 (e.g., via one or more wired or wireless backhaul links). For example, communication manager 1320 can manage the delivery of data communications for client devices, such as one or more UEs 115. In some examples, communication manager 1320 can manage communications with other network entities 105 and can include a controller or scheduler for coordinating with other network entities 105 to control communications with UEs 115. In some examples, communication manager 1320 can support an X2 interface within LTE / LTE-A wireless communication network technology to provide communications between network entities 105.

[0266] According to examples as disclosed herein, the communication manager 1320 may support wireless communications at a network entity. For example, the communication manager 1320 may be configured as or otherwise support means for receiving capability information indicating UE capabilities for processing PDSCH, wherein the capability information includes an indication that the UE is capable of monitoring more than one downlink shared channel transmission per CC within a time slot. The communication manager 1320 may be configured as or otherwise support means for sending control information indicating a codebook for HARQ-ACK at the UE. The communication manager 1320 may be configured as or otherwise support means for sending one or more downlink shared channel transmissions on one or more CCs. The communication manager 1320 may be configured as or otherwise support means for receiving feedback for a first set of CCs, the first set of CCs being at least a portion of the one or more CCs, the feedback being included in the codebook, wherein the first set of CCs for which the feedback is included is based on a frequency band associated with the indication in the capability information.

[0267] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1320 may support wireless communications at a network entity. For example, the communication manager 1320 may be configured as or otherwise support means for transmitting control information indicating a codebook for HARQ-ACK at a UE, wherein the control information includes a first parameter that disables or enables the UE to monitor more than one downlink shared channel transmission per time slot. The communication manager 1320 may be configured as or otherwise support means for transmitting one or more downlink shared channel transmissions. The communication manager 1320 may be configured as or otherwise support means for receiving feedback for one or more CCs based on the first parameter, wherein the feedback is included in a codebook for HARQ-ACK for the one or more downlink shared channel transmissions, and wherein the codebook is based on the control information.

[0268] By including or configuring the communication manager 1320 according to the examples described herein, the device 1305 can support techniques for indicating Type 1 HARQ-ACK codebook capabilities, which can improve resource utilization, clarify the UE's ability to receive more than one PDSCH per time slot, and ensure peer network entity capabilities to improve communication between the UE and the network entity.

[0269] In some examples, the communication manager 1320 can be configured to use or otherwise cooperate with the transceiver 1310, one or more antennas 1315 (e.g., where applicable), or any combination thereof to perform various operations (e.g., receive, obtain, monitor, output, transmit). Although the communication manager 1320 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1320 may be supported or performed by the transceiver 1310, the processor 1335, the memory 1325, the code 1330, or any combination thereof. For example, the code 1330 may include instructions that can be executed by the processor 1335 to cause the device 1305 to perform various aspects of type 1 HARQ-ACK codebook generation as described herein, or the processor 1335 and the memory 1325 may be otherwise configured to perform or support such operations.

[0270] Figure 14 A flow chart illustrating a method 1400 for supporting type 1 HARQ-ACK codebook generation according to one or more aspects of the present disclosure is illustrated. The operations of the method 1400 may be implemented by a UE or components thereof as described herein. For example, the operations of the method 1400 may be implemented by a UE or components thereof as described herein. Figures 1 to 9 The UE 115 described herein performs. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0271] At 1405, the method may include: sending capability information indicating the UE's capability to process the PDSCH, wherein the capability information includes an indication that the UE is capable of monitoring more than one downlink shared channel transmission per CC within a time slot. The operations of 1405 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1405 may be performed as described in reference to Figure 8 The described capability component 825 performs.

[0272] At 1410, the method may include receiving control information indicating a codebook for HARQ-ACK at the UE. The operations of 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed as described in reference to Figure 8 The control information component 830 is described as performing.

[0273] At 1415, the method may include monitoring one or more downlink shared channel transmissions on one or more CCs based on the control information. The operations of 1415 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1415 may be performed as described in reference to Figure 8 The PDSCH component 835 is described as performing.

[0274] At 1420, the method may include generating a codebook for HARQ-ACK for one or more downlink shared channel transmissions, wherein the codebook is based on the control information and includes feedback for a first set of CCs, the first set of CCs being at least a portion of the one or more CCs, wherein the first set of CCs for which feedback is included is based on a frequency band associated with an indication in the capability information. The operations of 1420 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1420 may be performed as described with reference to Figure 8 The codebook component 840 performs as described.

[0275] Figure 15 A flow chart illustrating a method 1500 for supporting type 1 HARQ-ACK codebook generation according to one or more aspects of the present disclosure is illustrated. The operations of the method 1500 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1500 may be implemented by a UE or a component thereof as described herein. Figures 1 to 9 The UE 115 described herein performs. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0276] At 1505, the method may include: sending capability information indicating the UE's capability to process the PDSCH, wherein the capability information includes an indication that the UE is capable of monitoring more than one downlink shared channel transmission per CC within a time slot. The operations of 1505 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1505 may be performed as described in reference to Figure 8 The described capability component 825 performs.

[0277] At 1510, the method may include receiving control information indicating a codebook for HARQ-ACK at the UE. The operations of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed as described in reference to Figure 8 The control information component 830 is described as performing.

[0278] At 1515, the method may include monitoring one or more downlink shared channel transmissions on one or more CCs based on the control information. The operations of 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed as described in reference to Figure 8 The PDSCH component 835 is described as performing.

[0279] At 1520, the method may include feedback of candidate downlink shared channel opportunities on a first set of CCs including a TDRA (TDRA) group based on non-overlapping SLIV (SLIV). The operations of 1520 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1520 may be as described in reference to Figure 8 The TDRA grouping component 850 is described as performing.

[0280] At 1525, the method may include generating a codebook for HARQ-ACK for one or more downlink shared channel transmissions, wherein the codebook is based on the control information and includes feedback for a first set of CCs, the first set of CCs being at least a portion of the one or more CCs, wherein the first set of CCs for which feedback is included is based on a frequency band associated with an indication in the capability information. The operations of 1525 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1525 may be performed as described with reference to Figure 8 The codebook component 840 performs as described.

[0281] Figure 16 A flow chart illustrating a method 1600 for supporting type 1 HARQ-ACK codebook generation according to one or more aspects of the present disclosure is illustrated. The operations of the method 1600 may be implemented by a UE or components thereof as described herein. For example, the operations of the method 1600 may be implemented by a UE or components thereof as described herein. Figures 1 to 9 The UE 115 described herein performs. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0282] At 1605, the method may include receiving control information indicating a codebook for HARQ-ACK at the UE, wherein the control information includes a first parameter that disables or enables the UE to monitor more than one downlink shared channel transmission per time slot. The operations of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described in reference to Figure 8 The parameter component 845 is described as executing.

[0283] At 1610, the method may include monitoring one or more downlink shared channel transmissions based on the control information. The operations of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed as described in reference to Figure 8 The PDSCH component 835 is described as performing.

[0284] At 1615, the method may include generating a codebook for HARQ-ACK for one or more downlink shared channel transmissions, wherein the codebook is based on the control information and includes feedback for one or more CCs based on the first parameter. The operations of 1615 may be performed according to the examples disclosed herein. In some examples, aspects of the operations of 1615 may be performed as described in reference to Figure 8 The codebook component 840 performs as described.

[0285] Figure 17 A flow chart illustrating a method 1700 for supporting type 1 HARQ-ACK codebook generation according to one or more aspects of the present disclosure is illustrated. The operations of the method 1700 may be implemented by a UE or components thereof as described herein. For example, the operations of the method 1700 may be implemented by a UE or components thereof as described herein. Figures 1 to 9 The UE 115 described herein performs. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0286] At 1705, the method may include: sending a UE capability for monitoring control information, the control information including a first parameter that disables or enables the UE to monitor more than one downlink shared channel transmission per time slot. The operations of 1705 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1705 may be performed as described in reference to Figure 8 The described capacity control component 855 performs.

[0287] At 1710, the method may include receiving control information indicating a codebook for HARQ-ACK at the UE, wherein the control information includes a first parameter. The operations of 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed as described in reference to Figure 8 The parameter component 845 is described as executing.

[0288] At 1715, the method may include monitoring one or more downlink shared channel transmissions based on the control information. The operations of 1715 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1715 may be performed as described in reference to Figure 8 The PDSCH component 835 is described as performing.

[0289] At 1720, the method may include generating a codebook for HARQ-ACK for one or more downlink shared channel transmissions, wherein the codebook is based on the control information and includes feedback for one or more CCs based on the first parameter. The operations of 1720 may be performed according to the examples disclosed herein. In some examples, aspects of the operations of 1720 may be performed as described in reference to Figure 8 The codebook component 840 performs as described.

[0290] Figure 18 A flow chart illustrating a method 1800 for supporting type 1 HARQ-ACK codebook generation according to one or more aspects of the present disclosure is illustrated. The operations of the method 1800 may be implemented by a network entity or component thereof as described herein. For example, the operations of the method 1800 may be implemented by a network entity or component thereof as described herein. Figures 1 to 5 as well as Figures 10 to 13 The network entity described herein performs. In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0291] At 1805, the method may include receiving capability information indicating a UE capability for processing a PDSCH, wherein the capability information includes an indication that the UE is capable of monitoring more than one downlink shared channel transmission per CC within a time slot. The operations of 1805 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1805 may be performed as described in reference to Figure 12 The described capability manager 1225 performs.

[0292] At 1810, the method may include sending control information indicating a codebook for HARQ-ACK at the UE. The operations of 1810 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1810 may be performed as described in reference to Figure 12 The described codebook manager 1230 is executed.

[0293] At 1815, the method may include: transmitting one or more downlink shared channel transmissions on one or more CCs. The operations of 1815 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1815 may be performed as described in reference to Figure 12 The described PDSCH manager 1235 performs

[0294] At 1820, the method may include receiving feedback for a first set of CCs, the first set of CCs being at least a portion of one or more CCs, the feedback being included in a codebook, wherein the first set of CCs for which the feedback is included is based on a frequency band associated with an indication in the capability information. The operations of 1820 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1820 may be performed as described with reference to Figure 12 The described feedback manager 1240 performs.

[0295] Figure 19 A flow chart illustrating a method 1900 for supporting type 1 HARQ-ACK codebook generation according to one or more aspects of the present disclosure is illustrated. The operations of the method 1900 may be implemented by a network entity or component thereof as described herein. For example, the operations of the method 1900 may be implemented by a network entity or component thereof as described herein. Figures 1 to 5 as well as Figures 10 to 13 The network entity described herein performs. In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0296] At 1905, the method may include: sending control information indicating a codebook for HARQ-ACK at the UE, wherein the control information includes a first parameter that disables or enables the UE to monitor more than one downlink shared channel transmission per time slot. The operations of 1905 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1905 may be performed as described in reference to Figure 12 The parameter manager 1245 described here performs.

[0297] At 1910, the method may include: transmitting one or more downlink shared channel transmissions. The operations of 1910 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1910 may be performed as described in reference to Figure 12 The described PDSCH manager 1235 performs

[0298] At 1915, the method may include receiving feedback for one or more CCs based on a first parameter, wherein the feedback is included in a codebook for HARQ-ACK transmitted for one or more downlink shared channels, and wherein the codebook is based on control information. The operations of 1915 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1915 may be performed as described in reference to Figure 12 The described feedback manager 1240 performs.

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

[0300] Aspect 1: A method for wireless communication at a UE, the method comprising: sending capability information indicating UE capability for processing PDSCH, wherein the capability information includes an indication that the UE is capable of monitoring more than one downlink shared channel transmission per CC within a time slot; receiving control information indicating a codebook for HARQ-ACK at the UE; monitoring one or more downlink shared channel transmissions on one or more CCs based on the control information; and generating the codebook for the HARQ-ACK for the one or more downlink shared channel transmissions, wherein the codebook is based at least in part on the control information and includes feedback for a first set of CCs, the first set of CCs being at least a portion of the one or more CCs, wherein the first set of CCs for which the feedback is included is based at least in part on a frequency band associated with the indication in the capability information.

[0301] Aspect 2: The method of aspect 1, wherein generating the codebook comprises: including the feedback of candidate downlink shared channel opportunities on the first set of CCs based at least in part on a TDRA group of non-overlapping SLIVs.

[0302] Aspect 3: According to the method of Aspect 2, the method also includes: determining the first set of CCs as all CCs of the one or more CCs in the cell group based at least in part on the indication in the capability information indicating that the UE is capable of monitoring the more than one downlink shared channels sent within the time slot for at least the frequency band in at least one frequency band combination.

[0303] Aspect 4: According to the method described in any one of Aspects 2 to 3, the method further includes: determining the first set of CCs as all CCs in the one or more CCs in the cell group based at least in part on the indication in the capability information indicating that the UE is capable of monitoring the more than one downlink shared channel sent within the time slot for at least the frequency band in at least one frequency band combination including the cell group.

[0304] Aspect 5: According to the method described in any one of Aspects 2 to 4, the method further includes: determining the first set of CCs as all CCs in the one or more CCs in the frequency band based at least in part on the indication in the capability information indicating that the UE is capable of monitoring the more than one downlink shared channel sent within the time slot for the frequency band in at least one frequency band combination.

[0305] Aspect 6: According to the method described in any one of Aspects 2 to 5, the method further includes: determining the first set of CCs as all CCs in the one or more CCs in the frequency band based at least in part on the indication in the capability information indicating that the UE is capable of monitoring the more than one downlink shared channel sent within the time slot for the frequency band in at least one frequency band combination, wherein the at least one frequency band combination corresponds to the one or more CCs in the one or more frequency bands.

[0306] Aspect 7: The method according to any one of aspects 1 to 6, wherein generating the codebook comprises: including the feedback for a single candidate downlink shared channel opportunity on the second set of CCs without identifying a TDRA group of non-overlapping SLIVs.

[0307] Aspect 8: A method according to any one of Aspects 1 to 7, wherein, in addition to the CBG processing capability, the UE capability for processing the PDSCH included in the capability information also includes one or more of the following items: a first UE capability associated with a first processing capability, a second UE capability associated with a second processing capability applicable to multiple subcarrier intervals, and a restricted second UE capability associated with the second processing capability applicable to a subset of the multiple subcarrier intervals, wherein the first processing capability and the second processing capability are different.

[0308] Aspect 9: According to the method of aspect 8, the method also includes: determining that the UE is capable of monitoring the more than one downlink shared channel transmission within the time slot based at least in part on the indication being associated with the first UE capability without enabling CBG processing type.

[0309] Aspect 10: According to the method described in any one of Aspects 8 to 9, the method further includes: determining that the UE is capable of monitoring the more than one downlink shared channel transmission within the time slot based at least in part on second control information enabling at least one of the second UE capability or the restricted second UE capability for the UE.

[0310] Aspect 11: According to the method of Aspect 10, the method also includes: determining that the UE is capable of monitoring the more than one downlink shared channel transmission within the time slot based at least in part on the indication being associated with the first UE capability and in the absence of the enabled second UE processing type, the restricted second UE processing type and the CBG processing type.

[0311] Aspect 12: According to the method described in any one of Aspects 10 to 11, the method further includes: receiving the second control information for enabling the CBG processing type for the UE; and determining that the UE is capable of monitoring the more than one downlink shared channel transmission within the time slot based at least in part on the indication being associated with the first UE capability and based on the CBG processing type being enabled, and in the absence of the enabled second UE processing type and the restricted second UE processing type.

[0312] Aspect 13: According to the method described in any one of Aspects 10 to 12, the method further includes: receiving the second control information enabling the CBG processing type for the UE and enabling at least one of the second UE processing type or the restricted second UE processing type for the UE; and determining that the UE is capable of monitoring the more than one downlink shared channel transmission within the time slot based at least in part on the indication being associated with the second UE processing type or one of the restricted second UE processing types and based on the CBG processing type being enabled.

[0313] Aspect 14: According to the method described in any one of Aspects 10 to 13, the method further includes: receiving the second control information for enabling at least one of the second UE processing type or the restricted second UE processing type for the UE; and determining that the UE is capable of monitoring the more than one downlink shared channel transmission within the time slot based at least in part on the indication being associated with the second UE processing type or one of the restricted second UE processing types, and in the absence of an enabled CBG processing type.

[0314] Aspect 15: According to the method of Aspect 14, the method also includes: determining that the UE is capable of monitoring the more than one downlink shared channel transmission within the time slot is also at least partially based on at least one of the second UE processing type or the restricted second UE processing type indicating that the UE is capable of monitoring the more than one downlink shared channel transmission within the time slot.

[0315] Aspect 16: A method for wireless communication at a UE, the method comprising: receiving control information indicating a codebook for HARQ-ACK at the UE, wherein the control information includes a first parameter that enables or disables the UE from monitoring more than one downlink shared channel transmission per time slot; monitoring one or more downlink shared channel transmissions based on the control information; and generating the codebook for the HARQ-ACK for the one or more downlink shared channel transmissions, wherein the codebook is based at least in part on the control information and includes feedback for one or more CCs based at least in part on the first parameter.

[0316] Aspect 17: The method according to aspect 16 further comprises: sending capability information indicating the UE capability for processing PDSCH, wherein the capability information comprises an indication of the number of downlink shared channel transmissions that the UE can monitor in a time slot.

[0317] Aspect 18: A method according to any one of aspects 16 to 17, wherein the first parameter enables the UE to monitor the more than one downlink shared channel transmission by time slot on a per-CC basis, or on a per-BWP basis, or on a per-cell group basis.

[0318] Aspect 19: The method according to any one of aspects 16 to 18, wherein receiving the control information includes: receiving a second indication of a maximum number of downlink shared channel transmissions that the UE can monitor within the time slot.

[0319] Aspect 20: The method according to any one of aspects 16 to 19, further comprising: sending a second UE capability for monitoring the control information including the first parameter.

[0320] Aspect 21: According to any one of aspects 16 to 20, the method further includes: receiving second control information including a second parameter, the second parameter enabling the first parameter on a per-cell group basis, wherein the first parameter is on a per-CC basis or on a per-BWP basis.

[0321] Aspect 22: A method according to any one of Aspects 16 to 21, wherein receiving the control information includes: receiving the first parameter, wherein the first parameter enables the UE to monitor more than one downlink shared channel transmission per time slot or prevents the UE from monitoring a single downlink shared channel transmission per time slot.

[0322] Aspect 23: A method according to any one of Aspects 16 to 22, wherein receiving the control information includes: receiving the first parameter, wherein the first parameter enables the UE to monitor a single downlink shared channel transmission per time slot or prevents the UE from monitoring more than one downlink shared channel transmission per time slot.

[0323] Aspect 24: A method for wireless communication at a network entity, the method comprising: receiving capability information indicating UE capabilities for processing PDSCH, wherein the capability information includes an indication that the UE is capable of monitoring more than one downlink shared channel transmission per CC within a time slot; sending control information indicating a codebook for HARQ-ACK at the UE; sending one or more downlink shared channel transmissions on one or more CCs; and receiving feedback for a first set of CCs, the first set of CCs being at least a portion of the one or more CCs, the feedback being included in the codebook, wherein the first set of CCs for which the feedback is included is based at least in part on a frequency band associated with the indication in the capability information.

[0324] Aspect 25: The method of aspect 24, wherein receiving the feedback comprises receiving the feedback for candidate downlink shared channel opportunities on the first set of CCs based at least in part on a TDRA group of non-overlapping SLIVs.

[0325] Aspect 26: According to the method of Aspect 25, the method also includes: determining the first set of CCs as all CCs of the one or more CCs in the cell group based at least in part on the indication in the capability information indicating that the UE is capable of monitoring the more than one downlink shared channel sent within the time slot for at least the frequency band in at least one frequency band combination.

[0326] Aspect 27: According to the method described in any one of Aspects 25 to 26, the method further includes: determining the first set of CCs as all CCs of the one or more CCs in the cell group based at least in part on the indication in the capability information indicating that the UE is capable of monitoring the more than one downlink shared channels sent within the time slot for at least the frequency band in at least one frequency band combination including the cell group.

[0327] Aspect 28: According to the method described in any one of Aspects 25 to 27, the method further includes: determining the first set of CCs as all CCs of the one or more CCs in the frequency band based at least in part on the indication in the capability information indicating that the UE is capable of monitoring the more than one downlink shared channel sent within the time slot for the frequency band in at least one frequency band combination.

[0328] Aspect 29: According to the method described in any one of Aspects 25 to 28, the method further includes: determining the first set of CCs as all CCs in the one or more CCs in the frequency band based at least in part on the indication in the capability information indicating that the UE is capable of monitoring the more than one downlink shared channel sent within the time slot for the frequency band in at least one frequency band combination, wherein the at least one frequency band combination corresponds to the one or more CCs in one or more frequency bands.

[0329] Aspect 30: The method according to any one of aspects 24 to 29, wherein receiving the feedback comprises receiving the feedback for a single candidate downlink shared channel opportunity on the second set of CCs without identifying a TDRA group of non-overlapping SLIVs.

[0330] Aspect 31: A method according to any one of Aspects 24 to 30, wherein, in addition to the CBG processing capability, the UE capability for processing the PDSCH included in the capability information also includes one or more of the following items: a first UE capability associated with a first processing capability, a second UE capability associated with a second processing capability applicable to multiple subcarrier intervals, and a restricted second UE capability associated with the second processing capability applicable to a subset of the multiple subcarrier intervals, wherein the first processing capability and the second processing capability are different.

[0331] Aspect 32: The method according to Aspect 31 further includes: determining that the UE is capable of monitoring the more than one downlink shared channel transmission within the time slot based at least in part on the indication being associated with the first UE capability without enabling CBG processing type.

[0332] Aspect 33: According to the method described in any one of Aspects 31 to 32, the method further includes: determining that the UE is capable of monitoring the more than one downlink shared channel transmission within the time slot based at least in part on second control information enabling at least one of a second UE processing type or a restricted second UE processing type for the UE.

[0333] Aspect 34: According to the method of Aspect 33, the method also includes: determining that the UE is capable of monitoring the more than one downlink shared channel transmission within the time slot based at least in part on the indication being associated with the first UE capability and in the absence of the enabled second UE processing type, the restricted second UE processing type and the CBG processing type.

[0334] Aspect 35: According to the method described in any one of Aspects 33 to 34, the method further includes: sending second control information for enabling a CBG processing type for the UE; and determining that the UE is able to monitor the more than one downlink shared channel transmission within the time slot based at least in part on the indication being associated with the first UE capability and based on the CBG processing type being enabled, and in the absence of the enabled second UE processing type and the restricted second UE processing type.

[0335] Aspect 36: According to the method described in any one of Aspects 33 to 35, the method further includes: sending second control information to enable the CBG processing type for the UE and to enable at least one of the second UE processing type or the restricted second UE processing type for the UE; and determining that the UE is capable of monitoring the more than one downlink shared channel transmission within the time slot based at least in part on the indication being associated with the second UE processing type or one of the restricted second UE processing types and based on the CBG processing type being enabled.

[0336] Aspect 37: According to the method described in any one of Aspects 33 to 36, the method further includes: sending second control information to enable at least one of the second UE processing type or the restricted second UE processing type for the UE; and determining that the UE is able to monitor the more than one downlink shared channel transmission within the time slot based at least in part on the indication being associated with the second UE processing type or one of the restricted second UE processing types, and in the absence of an enabled CBG processing type.

[0337] Aspect 38: According to the method of Aspect 37, the method also includes: determining that the UE is capable of monitoring the more than one downlink shared channel transmission within the time slot is also at least partially based on at least one of the second UE processing type or the restricted second UE processing type indicating that the UE is capable of monitoring the more than one downlink shared channel transmission within the time slot.

[0338] Aspect 39: A method for wireless communication at a network entity, the method comprising: sending control information indicating a codebook for HARQ-ACK at a UE, wherein the control information comprises a first parameter that disables or enables the UE to monitor more than one downlink shared channel transmission per time slot; sending one or more downlink shared channel transmissions; and receiving feedback for one or more CCs based at least in part on the first parameter, wherein the feedback is included in the codebook for the HARQ-ACK for the one or more downlink shared channel transmissions, and wherein the codebook is based at least in part on the control information.

[0339] Aspect 40: The method according to aspect 39 further comprises: receiving capability information indicating the UE capability for processing PDSCH, wherein the capability information comprises an indication of the number of downlink shared channel transmissions that the UE can monitor in a time slot.

[0340] Aspect 41: A method according to any one of aspects 39 to 40, wherein the first parameter enables the UE to monitor the more than one downlink shared channel transmissions by time slot on a per-CC basis, or on a per-BWP basis, or on a per-cell group basis.

[0341] Aspect 42: The method according to any one of aspects 39 to 41, wherein sending the control information comprises sending a second indication of a maximum number of downlink shared channel transmissions that the UE can monitor within the time slot.

[0342] Aspect 43: The method according to any one of aspects 39 to 42, further comprising: receiving a second UE capability for monitoring the control information including the first parameter.

[0343] Aspect 44: According to any one of aspects 39 to 43, the method further includes: sending second control information including a second parameter, the second parameter enabling the first parameter on a per-cell group basis, wherein the first parameter is on a per-CC basis or on a per-BWP basis.

[0344] Aspect 45: A method according to any one of Aspects 39 to 44, wherein sending the control information includes: sending the first parameter, wherein the first parameter enables the UE to monitor more than one downlink shared channel transmission per time slot or prevents the UE from monitoring a single downlink shared channel transmission per time slot.

[0345] Aspect 46: A method according to any one of Aspects 39 to 45, wherein sending the control information includes: sending the first parameter, wherein the first parameter enables the UE to monitor a single downlink shared channel transmission per time slot or prevents the UE from monitoring more than one downlink shared channel transmission per time slot.

[0346] Aspect 47: A UE for wireless communication, the UE comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or collectively to execute the code to cause the UE to perform a method according to any one of Aspects 1 to 15.

[0347] Aspect 48: A UE for wireless communication, the UE comprising at least one component for performing the method according to any one of aspects 1 to 15.

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

[0349] Aspect 50: A UE for wireless communication, the UE comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and individually or collectively operable to execute the code to cause the UE to perform a method according to any one of Aspects 16 to 23.

[0350] Aspect 51: A UE for wireless communication, the UE comprising at least one component for performing the method according to any one of aspects 16 to 23.

[0351] Aspect 52: A non-transitory computer-readable medium storing code for wireless communication at a UE, the code comprising instructions executable by one or more processors to perform the method according to any one of aspects 16 to 23.

[0352] Aspect 53: A network entity for wireless communication, the network entity comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and individually or collectively operable to execute the code to cause the UE to cause the device to perform a method according to any one of Aspects 24 to 38.

[0353] Aspect 54: A network entity for wireless communication, the network node comprising at least one component for performing the method according to any one of aspects 24 to 38.

[0354] Aspect 55: A non-transitory computer-readable medium storing code for wireless communication at a network entity, the code comprising instructions executable by one or more processors to perform the method according to any one of aspects 24 to 38.

[0355] Aspect 56: A network entity for wireless communication, the network entity comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and individually or collectively operable to execute the code to cause the UE to perform a method according to any one of aspects 39 to 46.

[0356] Aspect 57: A network entity for wireless communication, the network node comprising at least one component for performing the method according to any one of aspects 39 to 46.

[0357] Aspect 58: A non-transitory computer-readable medium storing code for wireless communication at a network entity, the code comprising instructions executable by one or more processors to perform the method of any one of aspects 39 to 46.

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

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

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

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

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

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

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

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

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

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

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

Claims

1. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and individually or collectively operable to execute the code to cause the UE to: receiving control information indicating a codebook for hybrid automatic repeat request acknowledgement at the UE, wherein the control information includes a first parameter that disables or enables the UE to monitor more than one downlink shared channel transmission per time slot; monitoring one or more downlink shared channel transmissions based at least in part on the control information; as well as Generating the codebook for the hybrid automatic repeat request acknowledgment for the one or more downlink shared channel transmissions, wherein the codebook is based at least in part on the control information and includes feedback for one or more component carriers based at least in part on the first parameter.

2. The UE of claim 1 , wherein the first parameter enables the UE to monitor the more than one downlink shared channel transmissions per time slot on a per component carrier basis, or on a per bandwidth part basis, or on a per cell group basis.

3. The UE of claim 1 , wherein the one or more processors are further operable, individually or collectively, to execute the code to cause the UE to: A second UE capability for monitoring the control information including the first parameter is sent.

4. The UE of claim 1 , wherein, to receive the control information, the one or more processors are further operable, individually or collectively, to execute the code to cause the UE to: The first parameter is received, wherein the first parameter enables the UE to monitor more than one downlink shared channel transmission per time slot or disables the UE from monitoring a single downlink shared channel transmission per time slot.

5. The UE of claim 1 , wherein, to receive the control information, the one or more processors are further operable, individually or collectively, to execute the code to cause the UE to: The first parameter is received, wherein the first parameter enables the UE to monitor a single downlink shared channel transmission per time slot or disables the UE from monitoring more than one downlink shared channel transmission per time slot.

6. The UE of claim 1 , wherein the one or more processors are further operable, individually or collectively, to execute the code to cause the UE to: Capability information indicating a UE capability for processing a physical downlink shared channel is transmitted, wherein the capability information includes an indication of a number of downlink shared channel transmissions that the UE is capable of monitoring in a timeslot.

7. The UE of claim 1 , wherein, to receive the control information, the one or more processors are further operable, individually or collectively, to execute the code to cause the UE to: A second indication of a maximum number of downlink shared channel transmissions that the UE can monitor within the time slot is received.

8. The UE of claim 1 , wherein the one or more processors are further operable, individually or collectively, to execute the code to cause the UE to: Second control information is received including a second parameter that enables the first parameter on a per-cell-group basis, wherein the first parameter is on a per-component-carrier basis or on a per-bandwidth-part basis.

9. A network entity for wireless communication, the network entity comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and individually or collectively operable to execute the code to cause the network entity to: transmitting control information indicating a codebook for hybrid automatic repeat request acknowledgement at a user equipment (UE), wherein the control information includes a first parameter that disables or enables the UE to monitor more than one downlink shared channel transmission per time slot; transmitting one or more downlink shared channel transmissions based at least in part on the control information; as well as and receiving feedback for one or more component carriers based at least in part on the first parameter, wherein the feedback is included in the codebook for the hybrid automatic repeat request acknowledgment transmitted by the one or more downlink shared channels, and wherein the codebook is based at least in part on the control information.

10. The network entity of claim 9, wherein the first parameter enables the UE to monitor the more than one downlink shared channel transmissions per time slot on a per component carrier basis, or on a per bandwidth part basis, or on a per cell group basis.

11. The network entity of claim 9, wherein the one or more processors are further operable, individually or collectively, to execute the code to cause the network entity to: A second UE capability for monitoring the control information including the first parameter is received.

12. The network entity of claim 9, wherein to send the control information, the one or more processors are further operable, individually or collectively, to execute the code to cause the network entity to: The first parameter is transmitted, wherein the first parameter enables the UE to monitor more than one downlink shared channel transmission per time slot or disables the UE from monitoring a single downlink shared channel transmission per time slot.

13. The network entity of claim 9, wherein to send the control information, the one or more processors are further operable, individually or collectively, to execute the code to cause the network entity to: The first parameter is transmitted, wherein the first parameter enables the UE to monitor a single downlink shared channel transmission per time slot or disables the UE from monitoring more than one downlink shared channel transmission per time slot.

14. The network entity of claim 9, wherein the one or more processors are further operable, individually or collectively, to execute the code to cause the network entity to: Capability information indicating a UE capability for processing a physical downlink shared channel is received, wherein the capability information includes an indication of a number of downlink shared channel transmissions that the UE is capable of monitoring in a timeslot.

15. The network entity of claim 9, wherein to send the control information, the one or more processors are further operable, individually or collectively, to execute the code to cause the network entity to: A second indication of a maximum number of downlink shared channel transmissions that the UE can monitor in the time slot is sent.

16. The network entity of claim 9, wherein the one or more processors are further operable, individually or collectively, to execute the code to cause the network entity to: Second control information is sent including a second parameter that enables the first parameter on a per-cell-group basis, wherein the first parameter is on a per-component-carrier basis or on a per-bandwidth-part basis.

17. A method for wireless communication at a user equipment (UE), the method comprising: receiving control information indicating a codebook for hybrid automatic repeat request acknowledgement at the UE, wherein the control information includes a first parameter that disables or enables the UE to monitor more than one downlink shared channel transmission per time slot; monitoring one or more downlink shared channel transmissions based at least in part on the control information; as well as Generating the codebook for the hybrid automatic repeat request acknowledgment for the one or more downlink shared channel transmissions, wherein the codebook is based at least in part on the control information and includes feedback for one or more component carriers based at least in part on the first parameter.

18. The method of claim 17, wherein the first parameter enables the UE to monitor the more than one downlink shared channel transmissions per time slot on a per component carrier basis, or on a per bandwidth part basis, or on a per cell group basis.

19. The method according to claim 17, further comprising: A second UE capability for monitoring the control information including the first parameter is sent.

20. The method of claim 17, wherein receiving the control information comprises: The first parameter is received, wherein the first parameter enables the UE to monitor more than one downlink shared channel transmission per time slot or disables the UE from monitoring a single downlink shared channel transmission per time slot.

21. The method of claim 17, wherein receiving the control information comprises: The first parameter is received, wherein the first parameter enables the UE to monitor a single downlink shared channel transmission per time slot or disables the UE from monitoring more than one downlink shared channel transmission per time slot.

22. The method according to claim 17, further comprising: Capability information indicating a UE capability for processing a physical downlink shared channel is transmitted, wherein the capability information includes an indication of a number of downlink shared channel transmissions that the UE is capable of monitoring in a timeslot.

23. The method of claim 17, wherein receiving the control information comprises: A second indication of a maximum number of downlink shared channel transmissions that the UE can monitor within the time slot is received.

24. The method according to claim 17, further comprising: Second control information is received including a second parameter that enables the first parameter on a per-cell-group basis, wherein the first parameter is on a per-component-carrier basis or on a per-bandwidth-part basis.

25. A method for wireless communication at a network entity, the method comprising: transmitting control information indicating a codebook for hybrid automatic repeat request acknowledgement at a user equipment (UE), wherein the control information includes a first parameter that disables or enables the UE to monitor more than one downlink shared channel transmission per time slot; transmitting one or more downlink shared channel transmissions based at least in part on the control information; as well as and receiving feedback for one or more component carriers based at least in part on the first parameter, wherein the feedback is included in the codebook for the hybrid automatic repeat request acknowledgment transmitted by the one or more downlink shared channels, and wherein the codebook is based at least in part on the control information.

26. The method of claim 25, wherein the first parameter enables the UE to monitor the more than one downlink shared channel transmissions per timeslot on a per component carrier basis, or on a per bandwidth part basis, or on a per cell group basis.

27. The method according to claim 25, further comprising: A second UE capability for monitoring the control information including the first parameter is received.

28. The method of claim 25, wherein sending the control information comprises: The first parameter is transmitted, wherein the first parameter enables the UE to monitor more than one downlink shared channel transmission per time slot or disables the UE from monitoring a single downlink shared channel transmission per time slot.

29. The method according to claim 25, further comprising: Capability information indicating a UE capability for processing a physical downlink shared channel is received, wherein the capability information includes an indication of a number of downlink shared channel transmissions that the UE is capable of monitoring in a timeslot.

30. The method of claim 25, wherein sending the control information comprises: A second indication of a maximum number of downlink shared channel transmissions that the UE can monitor in the time slot is sent.

Images