Patent Description:
European patent application <CIT> describes a method for controlling retransmission by a User Equipment (UE) in a wireless communication system supporting Multiple Input Multiple Output (MIMO) technology. A plurality of transport blocks is initially transmitted to a Node B. A retransmission request for at least one of the plurality of transport blocks is received from the Node B. A precoding matrix is determined base on a number of at least one layer corresponding to the at least one transport block negatively acknowledged (NACKed) from the Node B. If the UE does not receive a Physical Downlink Control CHannel (PDCCH) intended for the UE from the Node.

<NPL>, discusses enhancement on MIMO for R16 and proposes the following:.

<CIT> describes a method for transmitting Physical Uplink Shared Channel (PUSCH) performed ab a User Equipment (UE) in a wireless communication system may include downlink control information (DCI) for uplink (UL) scheduling; and performing codebook based PUSCH transmission based on precoding information included in the DCI.

<CIT> describes systems, apparatuses, and methods for time domain resource allocation in wireless communications systems. Disclosed embodiments include time-domain symbol determination and/or indication using a combination of higher layer and downlink control information signaling for physical downlink shared channel and physical uplink shared channel; time domain resource allocation for mini-slot operations; rules for postponing and dropping for multiple mini-slot transmission; and collision handling of sounding reference signals with semi-statically or semi-persistently configured uplink transmissions.

In some aspects, a method of wireless communication, performed by a user equipment (UE), may include receiving a downlink communication that includes one or more codepoints indicating a plurality of transmit precoder matrix indicator (TPMI) indices; and identifying, based at least in part on the one or more codepoints, a first TPMI index, of the plurality of TPMI indices, for a first repetition of a physical uplink shared channel (PUSCH) transmission, wherein the PUSCH transmission is a codebook-based PUSCH transmission.

In some aspects, a UE for wireless communication may include memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to receive a downlink communication that includes one or more codepoints indicating a plurality of TPMI indices; and identify, based at least in part on the one or more codepoints, a first TPMI index, of the plurality of TPMI indices, for a first repetition of a PUSCH transmission, wherein the PUSCH transmission is a codebook-based PUSCH transmission.

In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. The one or more instructions, when executed by one or more processors of a UE, may cause the one or more processors to receive a downlink communication that includes one or more codepoints indicating a plurality of TPMI indices; and identify, based at least in part on the one or more codepoints, a first TPMI index, of the plurality of TPMI indices, for a first repetition of a PUSCH transmission, wherein the PUSCH transmission is a codebook-based PUSCH transmission.

In some aspects, an apparatus for wireless communication may include means for receiving a downlink communication that includes one or more codepoints indicating a plurality of TPMI indices; and means for identifying, based at least in part on the one or more codepoints, a first TPMI index, of the plurality of TPMI indices, for a first repetition of a PUSCH transmission, wherein the PUSCH transmission is a codebook-based PUSCH transmission.

In some aspects, a method for wireless communication, performed by a UE, may include receiving a downlink communication that schedules a first set of repetitions of a PUSCH transmission associated with a first uplink beam and a second set of repetitions of the PUSCH transmission associated with a second uplink beam; configuring respective redundancy versions for the first set of repetitions based at least in part on a first redundancy version sequence associated with the first uplink beam; and configuring respective redundancy versions for the second set of repetitions based at least in part on a second redundancy version sequence associated with the second uplink beam.

In some aspects, a UE for wireless communication may include memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to receive a downlink communication that schedules a first set of repetitions of a PUSCH transmission associated with a first uplink beam and a second set of repetitions of the PUSCH transmission associated with a second uplink beam; configure respective redundancy versions for the first set of repetitions based at least in part on a first redundancy version sequence associated with the first uplink beam; and configure respective redundancy versions for the second set of repetitions based at least in part on a second redundancy version sequence associated with the second uplink beam.

In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. The one or more instructions, when executed by one or more processors of a UE, may cause the one or more processors to receive a downlink communication that schedules a first set of repetitions of a PUSCH transmission associated with a first uplink beam and a second set of repetitions of the PUSCH transmission associated with a second uplink beam; configure respective redundancy versions for the first set of repetitions based at least in part on a first redundancy version sequence associated with the first uplink beam; and configure respective redundancy versions for the second set of repetitions based at least in part on a second redundancy version sequence associated with the second uplink beam.

In some aspects, an apparatus for wireless communication may include means for receiving a downlink communication that schedules a first set of repetitions of a PUSCH transmission associated with a first uplink beam and a second set of repetitions of the PUSCH transmission associated with a second uplink beam; means for configuring respective redundancy versions for the first set of repetitions based at least in part on a first redundancy version sequence associated with the first uplink beam; and means for configuring respective redundancy versions for the second set of repetitions based at least in part on a second redundancy version sequence associated with the second uplink beam.

Aspects generally include a method, non-transitory computer-readable medium, user equipment as substantially described herein with reference to and as illustrated by the accompanying drawings and specification.

Controller/processor <NUM> of base station <NUM>, controller/processor <NUM> of UE <NUM>, and/or any other component(s) of <FIG> may perform one or more techniques associated with transmit precoder matrix indicator (TPMI) and/or sounding reference signal resource indicator (SRI) indication for codebook-based physical uplink shared channel (PUSCH) repetition, as described in more detail elsewhere herein. For example, controller/processor <NUM> of base station <NUM>, controller/processor <NUM> of UE <NUM>, and/or any other component(s) of <FIG> may perform or direct operations of, for example, process <NUM> of <FIG> and/or other processes as described herein. Memories <NUM> and <NUM> may store data and program codes for base station <NUM> and UE <NUM>, respectively. In some aspects, memory <NUM> and/or memory <NUM> may comprise a non-transitory computer-readable medium storing one or more instructions for wireless communication. For example, the one or more instructions, when executed by one or more processors of the base station <NUM> and/or the UE <NUM>, may perform or direct operations of, for example, process <NUM> of <FIG> and/or other processes as described herein.

In some aspects, UE <NUM> may include means for receiving a downlink communication that includes one or more codepoints indicating a plurality of TPMI indices, means for identifying, based at least in part on the one or more codepoints, a first TPMI index, of the plurality of TPMI indices, for a first repetition of a physical uplink shared channel (PUSCH) transmission, wherein the PUSCH transmission is a codebook-based PUSCH transmission, and/or the like. In some aspects, the UE <NUM> includes means for receiving a downlink communication that schedules a first set of repetitions of a PUSCH transmission associated with a first uplink beam and a second set of repetitions of the PUSCH transmission associated with a second uplink beam, means for configuring respective redundancy versions for the first set of repetitions based at least in part on a first redundancy version sequence associated with the first uplink beam, means for configuring respective redundancy versions for the second set of repetitions based at least in part on a second redundancy version sequence associated with the second uplink beam, and/or the like. In some aspects, such means may include one or more components of UE <NUM> described in connection with <FIG>, such as controller/processor <NUM>, transmit processor <NUM>, TX MIMO processor <NUM>, MOD <NUM>, antenna <NUM>, DEMOD <NUM>, MIMO detector <NUM>, receive processor <NUM>, and/or the like.

As indicated above, a BS may schedule or configure uplink transmissions for a UE on an uplink. In some cases, the BS may configure the UE to perform a codebook-based PUSCH transmission, which may be a PUSCH transmission that is configured to be performed in a sounding reference signal (SRS) resource set with a usage of 'codebook' configured for the UE. The SRS resource set may include N SRS resources (e.g., where N = <NUM>, <NUM>, <NUM>, or <NUM>), and the BS may configure the quantity of SRS ports and spatial relation information for each of the SRS resources on a per-SRS resource basis.

The spatial relation information for an SRS resource may indicate a reference signal index (e.g., a synchronization signal block (SSB), a channel state information reference signal (CSI-RS), or another SRS resource) for transmission of the SRS resource (and thus, the associated PUSCH transmission). The UE may use the same spatial domain transmission filter as the reference signal indicated in the spatial relation information (spatialRelationInfo), which may effectively be an uplink beam for the PUSCH transmission.

The BS may indicate, to the UE, an SRS resource for a PUSCH transmission by indicating the SRS resource in an SRS resource indicator (SRI) field in a downlink communication (e.g., a downlink control information (DCI) communication with a format 0_1, which may be an uplink scheduling DCI) that schedules the PUSCH transmission. The UE may use the same spatial domain transmission filter for the PUSCH transmission as the indicated SRS resource, and may use the quantity of SRS ports of the indicated SRS resource as the quantity of antenna ports for the PUSCH transmission.

In some cases, the downlink communication may further indicate a TPMI and a quantity of layers for the PUSCH transmission. For example, if the downlink communication is a DCI communication, the DCI communication may include a Precoding Information and Number of Layers field that indicates the TPMI and the quantity of layers. The Precoding Information and Number of Layers field may include a codepoint (e.g., a plurality of bits indicating or representing a particular value) that identifies an index associated with a row or column in a table or another type of data structure. The row or column may indicate the quantity of layers and the TPMI that are associated with the index.

In some cases, the size of the field may be based at least in part on the quantity of antenna ports indicated for the SRS resource, a Codebooksubset field, a Maxrank field, and/or a TransformPrecoder field. The quantity of antenna ports may be used to identify a quantity of rows for an associated TPMI matrix. The Codebooksubset field may indicate whether the antenna ports are fully coherent, partially coherent, noncoherent, or a combination thereof in the case that some antenna ports are pair-wise coherent but not full coherent (e.g., Pair <NUM> of two antenna ports are coherent, Pair <NUM> of another two antenna ports are coherent, but Pair <NUM> and Pair <NUM> are noncoherent). For example, the Codebooksubset field may indicate that the antenna ports are fullyAndPartialAndNonCoherent, or partialAndNonCoherent, or noncoherent. In some cases, all TPMI indices that may be indicated by the BS may be used for fullyAndPartialAndNonCoherent antenna ports, a subset of the TPMI indices may be used for partialAndNonCoherent antenna ports, and another subset of the TPMI indices may be used for noncoherent antenna ports. The Maxrank field may indicate a maximum quantity of layers for the PUSCH transmission. The Maxrank field may be used only if the TransformPrecoder field is not enabled. The TransformPrecoder field may indicate whether DFT-s-OFDM or CP-OFDM is enabled based at least in part on whether the TransformPrecoder field is enabled.

In some cases, a BS may configure a UE to transmit a plurality of repetitions of the same PUSCH transmission (e.g., a plurality of repetitions of the same PUSCH transport block), where each repetition may be directed to a TRP among a plurality of TRPs in a multi-TRP configuration, an antenna panel among a plurality of antenna panels in a multi-panel configuration, or an antenna among a plurality of antennas in a multi-antenna configuration. Thus, if an access link between the UE and a TRP (or antenna panel or antenna) is blocked such that a repetition transmitted to the TRP is not received, another repetition transmitted to another TRP may be received such that the PUSCH transmission can be decoded.

In some cases, the UE may be configured to transmit repetitions of a PUSCH transmission in different time-domain resources (e.g., slots/mini-slots). Each time-domain resource configured for a repetition of the PUSCH transmission may be referred to as a PUSCH transmission occasion. In some cases, the quantity of the repetitions (and thus, the quantity of PUSCH transmission occasions) may be configured via radio resource control (RRC) signaling or may be indicated dynamically (e.g., via DCI or medium access control control element (MAC-CE) signaling) through the use of a time domain resource assignment (TDRA) field. However, the BS may be capable of configuring only one TPMI that is to be used across all repetitions of the PUSCH transmission. If the same TPMI (and thus, the same precoder) is used for repetitions that are directed to different TRPs, antenna panels, or antennas, the transmissions of repetitions may experience reduced performance and/or reliability because channel conditions for the TRPs, antenna panels, or antennas, may be different and not optimally addressed by the same precoder.

Some aspects described herein provide techniques and apparatuses for TPMI and/or SRI indication for codebook-based PUSCH repetition. In some aspects, a UE may receive, from a BS, a downlink communication that includes one or more codepoints indicating a plurality of TPMI indices and/or an SRI codepoint indicating one or more SRS resources. The UE may identify, based at least in part on the one or more codepoints, one or more TPMI indices, of the plurality of TPMI indices, for one or more repetitions of a codebook-based PUSCH transmission and/or may identify, based at least in part on the SRI codepoint, one or more SRS resources for the one or more repetitions.

The ability to indicate a plurality of TPMI indices and/or a plurality of SRS resources in a single downlink communication permits the BS to configure a plurality of repetitions of a codebook-based PUSCH transmission to have different precoders, different SRS resources, and/or other parameters while reducing or minimizing signaling overhead. The ability to configure repetitions of a codebook-based PUSCH transmission to have different precoders, different SRS resources, and/or other parameters permits the repetitions to be beamformed and/or otherwise optimized for different channel conditions (e.g., multi-TRP channel conditions, multi-panel channel conditions, multi-antenna channel conditions, and/or the like), which increases the performance and reliability of the PUSCH transmissions.

<FIG> are diagrams illustrating one or more examples <NUM> of TPMI and/or SRI indication for codebook-based PUSCH repetition, in accordance with various aspects of the present disclosure. As shown in <FIG>, example(s) <NUM> may include communication between a UE (e.g., a UE <NUM>) and a BS (e.g., a BS <NUM>). In some aspects, the UE and the BS may be included in a wireless network, such as wireless network <NUM>. In some aspects, the UE and the BS may communicate on a wireless access link, which may include a downlink and an uplink.

In some aspects, the BS may schedule or configure the UE to transmit one or more repetitions of a PUSCH transmission. For example, the BS may schedule or configure the UE to transmit a first repetition on the uplink to the BS (e.g., to an antenna or an antenna panel of the BS), a second repetition on the uplink (e.g., to another antenna or antenna panel of the BS) or on another uplink to another BS (e.g., where the BS and the other BS are TRPs in a multi-TRP configuration), and so on. In some aspects, the PUSCH transmission may be a codebook-based PUSCH transmission (e.g., where an SRS resource set is configured for the PUSCH transmission with usage of 'codebook').

As shown in <FIG>, and by reference number <NUM>, to schedule or configure the one or more repetitions of the PUSCH transmission, the BS transmits a downlink communication to the UE. The downlink communication includes one or more codepoints indicating a plurality of TPMI indices for the PUSCH transmission and/or may include an SRI codepoint indicating one or more SRS resources for the PUSCH transmission.

In some aspects, the BS may schedule or configure PUSCH transmissions for the UE using a configured uplink grant. In this case, the BS may transmit an RRC communication that configures recurring or periodic resources that the UE may use for the PUSCH transmissions (which may be referred to as Type <NUM> configured grant PUSCH (CG-PUSCH) scheduling), or may transmit an RRC communication that configures the CG-PUSCH and activates the CG-PUSCH via a DCI communication (which may be referred to as Type <NUM> CG-PUSCH). If the downlink communication is a Type <NUM> CG-PUSCH RRC communication, the one or more codepoints may be included in a precodingAndNumberOfLayers field in the RRC communication, and the SRI codepoint may be included in an srs-Resourceindicator field in the RRC communication.

In some aspects, the BS may schedule or configure PUSCH transmissions for the UE using dynamic scheduling. In this case, the BS may transmit DCI communications (e.g., format 0_1 DCI communications) to the UE to schedule or configure resources for PUSCH transmissions. If the downlink communication is a DCI communication, the one or more codepoints may be included in a Precoding Information and Number of Layers field or another field that is used to indicate TPMI indices and a quantity of layers for the PUSCH transmission, and/or the SRI codepoint may be included in an SRI field.

In some aspects, the precodingAndNumberOfLayers field in an RRC communication or a Precoding Information and Number of Layers field in a DCI communication indicates one or more of the plurality of TPMI indices. For example, either of these fields includes a codepoint of the one or more codepoints, and the codepoint points to or otherwise indicates a quantity of layers and one or more TPMI indices for the PUSCH transmission. In some aspects, an RRC communication may include a plurality of precodingAndNumberOfLayers fields, or a DCI communication may include a plurality of Precoding Information and Number of Layers fields. In this case, each precodingAndNumberOfLayers field or Precoding Information and Number of Layers field may indicate a single TPMI index such that the plurality of precodingAndNumberOfLayers fields or the Precoding Information and Number of Layers fields indicate a plurality of TPMI indices. In some aspects, if the BS is to configure a single TPMI index for a PUSCH transmission (e.g., such as where an SRI codepoint indicates one SRS resource or is not configured with <NUM>-TPMI), the BS may set the codepoint in the precodingAndNumberOfLayers fields or the Precoding Information and Number of Layers fields after the first precodingAndNumberOfLayers field or the Precoding Information and Number of Layers field to a predetermined value, such as a <NUM>-value.

The quantity of layers, the quantity of TPMI indices, and the TPMI indices indicated by a codepoint in a precodingAndNumberOfLayers field or a Precoding Information and Number of Layers field may be based at least in part on an interpretation of the value of the codepoint. <FIG> illustrates an example table for indicating a plurality of TPMI indices. Other example tables for indicating a plurality of TPMI indices may be used. As shown in <FIG>, a first column of the table may include an index value for each row in the table. The index value may correspond to an associated codepoint value indicated in a precodingAndNumberOfLayers field or a Precoding Information and Number of Layers field. The table may include a second column identifying a mapping associated with an index value in the same row. The mapping may indicate the quantity of layers, the quantity of TPMI indices, and the TPMI indices for an index value (codepoint value). As further shown in <FIG>, the mapping in each row may specify an order of the TPMI indices indicated in the row. In this case, each combination of TPMI indices may be included in the table a plurality of times such that different orders of the same combination of TPMI indices are included. As an example, and as illustrated in <FIG>, the example table may include an index value <NUM> associated with a TPMI index order of (TPMI <NUM>, TPMI <NUM>), and may include an index value <NUM> associated with the reverse TPMI index order of (TPMI <NUM>, TPMI <NUM>).

In some aspects, the BS may be permitted to indicate any of the index values included in the table. To reduce the quantity of bits included in the codepoint of the precodingAndNumberOfLayers field or the Precoding Information and Number of Layers field (and thus, the overhead of the codepoint), the BS may semi-statically configure (e.g., via RRC signaling) a subset of the table that the BS is permitted to use. In this case, the subset of the table may be configured as another (smaller) table into which the codepoint may index. In some aspects, to more flexibly utilize the table, the BS may be permitted to dynamically (e.g., via MAC-CE or DCI) configure and change the subset of the table that is used to indicate TPMI indices.

In some aspects, the quantity of SRS resources, and the SRS resources, indicated by an SRI codepoint in an srs-ResourceIndicator field in an RRC communication or an SRI field in a DCI communication may be based at least in part on an interpretation of the value of the SRI codepoint. <FIG> illustrates an example table for indicating one or more SRS resources. Other example tables for indicating one or more SRS resources may be used. As shown in <FIG>, a first column of the table may include an index value for each row in the table. The index value may correspond to an associated SRI codepoint value indicated in an srs-ResourceIndicator field or an SRI field. The table may include one or more columns identifying a mapping associated with an index value in the same row based at least in part on a quantity of SRS resources configured for a PUSCH transmission. For example, the table may include a row indicating a mapping for a quantity of <NUM> configured SRS resources, a row indicating a mapping for a quantity of <NUM> configured SRS resources, a row indicating a mapping for a quantity of <NUM> configured SRS resources, and so on. The mapping may indicate the SRS resource(s) and the order of the SRS resources for an index value (SRI codepoint value). In this case, each combination of SRS resources may be included in the table a plurality of times such that different orders of the same combination of SRS resources are included. As an example, and as illustrated in <FIG>, the example table may include an index value <NUM> associated with a TPMI index order of (SRS resource <NUM>, SRS resource <NUM>), and may include an index value <NUM> associated with the reverse order of (SRS resource <NUM>, SRS resource <NUM>).

In some aspects, if the srs-ResourceIndicator field or the SRI field indicates a plurality of SRS resources for a plurality of TPMI indices, the UE may use, for each SRS resource indicated by an SRI codepoint, the spatial relation information (spatialRelationInfo) of the SRS resource for the spatial domain transmission filter for a repetition of a PUSCH transmission associated with the SRS resource. Moreover, for each SRS resource indicated by an SRI codepoint, the UE may use the quantity of SRS ports associated with the SRS resource for the quantity of transmit antenna ports that is to be used for the PUSCH transmission. In this case, the UE may determine the TPMI matrix for a TPMI index for an associated repetition based at least in part on the quantity of SRS ports associated with the SRS resource.

In some aspects, if the srs-ResourceIndicator field or the SRI field indicates a single SRS resource for a plurality of TPMI indices, the UE may use, for the SRS resource and the plurality of TPMI indices, the same spatial relation information (spatialRelationInfo) for transmission of the repetition(s) associated with the plurality of TPMI indices. In some aspects, the BS may configure a single SRS resource for a plurality of TPMI indices in cases where relative low frequency bands are used, such as sub-<NUM> or <NUM> NR frequency range <NUM> (FR1), as separate uplink beams may not be needed for transmission of different repetitions of the PUSCH transmission to different TRPs, different antenna panels, or different antennas. In some aspects, the BS may transmit, to the UE, an indication of the SRS resources that are permitted to be used with a plurality of TPMI indices. In this case, the indication may be included in an RRC communication as part of an SRS resource configuration for SRS resources in an SRS resource set with usage set to 'codebook'. In some aspects, the ability to switch between indicating one TPMI index or a plurality of TPMI indexes with the same SRS resource, and the ability to switch between indicating one SRS resource and a plurality of SRS resources, may be configurable by the BS via RRC signaling.

As shown in <FIG>, and by reference number <NUM>, the UE may identify one or more TPMI indices for one or more repetitions of a PUSCH transmission (e.g., a codebook-based PUSCH transmission) based at least in part on the one or more codepoints included in the downlink communication, and/or may identify one or more SRS resources for the one or more repetitions based at least in part on the SRI codepoint indicated in the downlink communication.

In some aspects, the UE may identify the one or more TPMI indices by determining the value of a codepoint included in the one or more codepoints and by performing a lookup in a table (e.g., such as the example table illustrated in <FIG>) or another type of data structure to identify an index, associated with the value, in the table. In this case, the UE may identify a row in the table in which the UE performs the lookup to determine the quantity of layers, the quantity of TPMI indices, the TPMI indices, and the order of the TPMI indices indicated by the codepoint. In some aspects, the UE may identify the one or more TPMI indices by performing a lookup to identify the row in a subset of the table configured by the BS and indicated in an RRC communication or a MAC-CE communication.

In some aspects, if the downlink communication includes a plurality of codepoints (e.g., one codepoint in each precodingAndNumberOfLayers field or in each Precoding Information and Number of Layers field, the UE may determine the value for each codepoint and may perform a lookup in a table based at least in part on each value to identify a row specifying a TPMI index for each codepoint.

In some aspects, the UE may identify the table in which to perform the lookup based at least in part on the quantity of SRS resources indicated by the SRI codepoint, based at least in part on whether the srs-ResourceIndicator field or the SRI field in which the SRI codepoint is included is configured with a <NUM>-TPMI configuration, and/or other factors. As an example, the UE may determine to use a first table (e.g., a table that is used to indicate a plurality of TPMI indices, such as the example table illustrated in <FIG>) to interpret the value of the codepoint if the SRI codepoint indicates two or more SRS resources, and may determine to use a second table (e.g., a table that is used to indicate a single TPMI index) to interpret the value of the codepoint if the SRI codepoint indicates a single SRS resource. As another example, the UE may determine to use a table (e.g., a table that is used to indicate a plurality of TPMI indices, such as the example table illustrated in <FIG>) to interpret the value of the codepoint if the SRI codepoint indicates two or more SRS resources, and may determine to use the same table to interpret the value of the codepoint if the SRI codepoint indicates a single SRS resource. In this case, the UE may use the first TPMI index indicated in the row associated with the value of the codepoint if the SRI codepoint indicates a single SRS resource.

As another example, the UE may determine to use a first table (e.g., a table that is used to indicate a plurality of TPMI indices, such as the example table illustrated in <FIG>) to interpret the value of the codepoint if the SRI codepoint indicates a single SRS resource and is configured with <NUM>-TPMI (e.g., such that the SRS resource corresponds to a plurality of TPMI indices indicated by the downlink communication), and may determine to use a second table (e.g., a table that is used to indicate a single TPMI index) to interpret the value of the codepoint if the SRI codepoint indicates a single SRS resource and is not configured with <NUM>-TPMI (e.g., such that SRS resource corresponds to a single TPMI index indicated by the downlink communication). As another example, the UE may determine to use a table (e.g., a table that is used to indicate a plurality of TPMI indices, such as the example table illustrated in <FIG>) to interpret the value of the codepoint if the SRI codepoint indicates two or more SRS resources, and may determine to use the same table to interpret the value of the codepoint if the SRI codepoint indicates a single SRS resource. In this case, the UE may use the first TPMI index indicated in the row associated with the value of the codepoint if the SRI codepoint indicates a single SRS resource.

In some aspects, the UE may identify the one or more SRS resources by determining the value of the SRI codepoint and by performing a lookup in a table (e.g., such as the example table illustrated in <FIG>) or another type of data structure to identify an index, associated with the value, in the table. In this case, the table in which the UE performs the lookup may indicate the SRS resource(s) and the order of the SRS resource(s). In some aspects, the UE may identify the one or more SRS resources by performing a lookup to identify the row in a subset of the table configured by the BS and indicated in an RRC communication or a MAC-CE communication.

In some aspects, the UE may map the TPMI indices and/or the SRS resource(s) to the one or more repetitions of the PUSCH transmission. For example, the UE may map a first TPMI index and/or a first SRS resource to a first repetition of the PUSCH transmission, may map a second TPMI index and/or a second SRS resource to a second repetition of the PUSCH transmission, and so on. The UE may map the TPMI indices to the repetition(s) of the PUSCH transmission based at least in part on the order of the TPMI indices associated with the value of the codepoint (e.g., as indicated in the table in which the UE performed the lookup). For example, the UE may map the first ordered TPMI index to the first repetition and may map the second ordered TPMI index to the second repetition.

Similarly, the UE may map the SRS resource(s) to the repetition(s) of the PUSCH transmission based at least in part on the order of the SRS resource(s) associated with the value of the SRI codepoint (e.g., as indicated in the table in which the UE performed the lookup). For example, the UE may map the first ordered SRS resource to the first repetition and may map the second ordered SRS resource to the second repetition. In some aspects, if a single SRS resource is indicated by the SRI codepoint, the UE may map the SRS resource to each of the repetitions scheduled by the downlink communication.

Moreover, the UE may determine whether an SRS resource indicated by the SRI codepoint maps to one or two TPMI indices based at least in part on whether an srs-ResourceIndicator field or an SRI field in which the SRI codepoint is included is configured with <NUM>-TPMI. In this case, the UE may determine that an SRS resource maps to two TPMIs based at least in part on determining that the srs-ResourceIndicator field or the SRI field is configured with <NUM>-TPMI. The UE may determine that an SRS resource maps to one TPMI based at least in part on determining that the srs-ResourceIndicator field or the SRI field is not configured with <NUM>-TPMI.

In some aspects, the UE may use various techniques to map TPMI indices and/or SRS resources to repetitions of a PUSCH transmission where the quantity of repetitions exceeds the quantity of TPMI indices and/or the quantity of SRS resources. <FIG> and <FIG> illustrate some example techniques. However, other techniques may be used. The mapping of TPMI indices and/or SRS resources to repetitions of a PUSCH transmission where the quantity of repetitions exceeds the quantity of TPMI indices and/or the quantity of SRS resources may be fixed (e.g., in a specification or configured or coded at the UE), may be semi-statically configurable via RRC signaling, may be dynamically configurable via MAC-CE or DCI signaling, and/or the like.

As shown in <FIG>, an example mapping for TPMI indices and/or SRS resources may include an alternating mapping of TPMI indices and/or SRS resources to repetitions of a PUSCH transmission. In this example, the UE may alternate between TPMI <NUM>/SRS resource <NUM> and TPMI <NUM>/SRS resource <NUM> for repetitions <NUM> through <NUM>. In particular, the UE may map TPMI <NUM>/SRS resource <NUM> to repetition <NUM>, may map TPMI <NUM>/SRS resource <NUM> to repetition <NUM>, may map TPMI <NUM>/SRS resource <NUM> to repetition <NUM>, and may map TPMI <NUM>/SRS resource <NUM> to repetition <NUM>. Thus, TPMI <NUM>/SRS resource <NUM> are mapped to odd-numbered repetitions and TPMI <NUM>/SRS resource <NUM> are mapped to even-numbered repetitions. In other examples, TPMI <NUM>/SRS resource <NUM> are mapped to odd-numbered repetitions and TPMI <NUM>/SRS resource <NUM> are mapped to even-numbered repetitions.

As shown in <FIG>, an example mapping for TPMI indices and/or SRS resources may include a grouped mapping of TPMI indices and/or SRS resources to repetitions of a PUSCH transmission. In this example, the UE may map TPMI <NUM>/SRS resource <NUM> to a first group of repetitions (e.g., repetitions <NUM> and <NUM>) and may map TPMI <NUM>/SRS resource <NUM> to a second (subsequent) group of repetitions (e.g., repetitions <NUM> and <NUM>). In other examples, TPMI <NUM>/SRS resource <NUM> are mapped to the first group of repetitions and TPMI <NUM>/SRS resource <NUM> are mapped to the second group of repetitions.

As shown in <FIG>, the UE may determine a redundancy version (RV) for each repetition of a PUSCH transmission. The RV for a repetition may be used to rate match the payload of the PUSCH transmission in the repetition. In some aspects, the UE may determine the RV for a repetition based at least in part on the TPMI index and/or SRS resource mapped to the repetition. In this case, each TPMI index and/or SRS resource may be associated with an RV sequence, and the RV for a repetition may be based at least in part on the RV sequence of the TPMI index and/or SRS resource mapped to the repetition. As an example, and as illustrated in <FIG>, a first TPMI and a first SRS resource (e.g., TPMI <NUM>/SRS resource <NUM>) may be associated with a first RV sequence (e.g., <NUM>→<NUM>→<NUM>→<NUM>), and a second TPMI and a second SRS resource (e.g., TPMI <NUM>/SRS resource <NUM>) may be associated with a second RV sequence (e.g., <NUM>→<NUM>→<NUM>→<NUM>).

In this case, the second RV sequence is essentially the same RV sequence as the first RV sequence, but configured with an RV offset value such that the starting point of the second RV sequence is shifted relative to the first RV sequence. Since the RV offset value causes the second RV sequence to be shifted relative to the first RV sequence, the likelihood that adjacent repetitions will be transmitted with the same RV is reduced or eliminated. In some aspects, the first RV sequence and the second RV sequence may be different RV sequences configured such that the likelihood that adjacent repetitions will be transmitted with the same RV is reduced or eliminated.

For example, and as illustrated in <FIG>, TPMI <NUM>/SRS resource <NUM> and TPMI <NUM>/SRS resource <NUM> may be mapped to repetitions <NUM> through <NUM> of a PUSCH transmission in an alternating manner such that TPMI <NUM>/SRS resource <NUM> are mapped to odd-numbered repetitions and TPMI <NUM>/SRS resource <NUM> are mapped to even-numbered repetitions. RVs may be mapped to the odd-numbered repetitions based at least in part on the first RV sequence associated with TPMI <NUM>/SRS resource <NUM>, and RVs may be mapped to the even-numbered repetitions based at least in part on the second RV sequence associated with TPMI <NUM>/SRS resource <NUM>. Accordingly, the RV mappings may be RV <NUM> for repetition <NUM>, RV <NUM> for repetition <NUM>, RV <NUM> for repetition <NUM>, RV <NUM> for repetition <NUM>, RV <NUM> for repetition <NUM>, RV <NUM> for repetition <NUM>, RV <NUM> for repetition <NUM>, and RV <NUM> for repetition <NUM>. Thus, no adjacent repetitions are assigned the same RV as a result of the RV offset value.

In some aspects, the UE may configure redundancy versions for repetitions of PUSCH transmission. The PUSCH transmission may be codebook-based or non-codebook-based. In these examples, the UE may receive a downlink communication from the BS that schedules a first set of repetitions of a PUSCH transmission associated with a first uplink beam (e.g., the first set of repetitions are associated with the same spatial domain transmission filter, as described above) and a second set of repetitions of the PUSCH transmission associated with a second uplink beam (e.g., the second set of repetitions are associated with the same spatial domain transmission filter, as described above, which may be different from the spatial domain transmission filter of the first set of repetitions). The UE may configure respective redundancy versions for the first set of repetitions based at least in part on a first redundancy version sequence associated with the first uplink beam, and may configure respective redundancy versions for the second set of repetitions based at least in part on a second redundancy version sequence associated with the second uplink beam.

In this way, the ability to indicate a plurality of TPMI indices and/or a plurality of SRS resources in a single downlink communication permits the BS to configure a plurality of repetitions of a codebook-based PUSCH transmission to have different precoders, different SRS resources, and/or other parameters while reducing or minimizing signaling overhead. The ability to configure repetitions of a codebook-based PUSCH transmission to have different precoders, different SRS resources, and/or other parameters permits the repetitions to be beamformed and/or otherwise optimized for different channel conditions (e.g., multi-TRP channel conditions, multi-panel channel conditions, multi-antenna channel conditions, and/or the like), which increases the performance and reliability of the PUSCH transmissions.

<FIG> is a diagram illustrating an example process <NUM> performed, for example, by a UE, in accordance with various aspects of the present disclosure. Example process <NUM> is an example where the UE (e.g., a UE <NUM>) performs operations associated with TPMI and/or SRI indication for codebook-based PUSCH repetition.

As shown in <FIG>, in some aspects, process <NUM> may include receiving a downlink communication that includes one or more codepoints indicating a plurality of TPMI indices (block <NUM>). For example, the UE (e.g., using antenna <NUM>, DEMOD <NUM>, MIMO detector <NUM>, receive processor <NUM>, controller/processor <NUM>, memory <NUM>, and/or the like) may receive a downlink communication that includes one or more codepoints indicating a plurality of TPMI indices, as described above.

As further shown in <FIG>, in some aspects, process <NUM> may include identifying, based at least in part on the one or more codepoints, a first TPMI index, of the plurality of TPMI indices, for a first repetition of a PUSCH transmission, wherein the PUSCH transmission is a codebook-based PUSCH transmission (block <NUM>). For example, the UE (e.g., using receive processor <NUM>, transmit processor <NUM>, controller/processor <NUM>, memory <NUM>, and/or the like) may identify, based at least in part on the one or more codepoints, a first TPMI index, of the plurality of TPMI indices, for a first repetition of a PUSCH transmission, as described above. In some aspects, the PUSCH transmission is a codebook-based PUSCH transmission.

In a first aspect, the one or more codepoints includes a single codepoint, in a Precoding Information and Number of Layers field of the downlink communication, indicating the plurality of TPMI indices; and process <NUM> further comprises identifying, based at least in part on the one or more codepoints, a second TPMI index, of the plurality of TPMI indices, for a second repetition of the PUSCH transmission. In a second aspect, alone or in combination with the first aspect, the codepoint indicates a same quantity of layers for the first repetition of the PUSCH transmission and the second repetition of the PUSCH transmission.

In a third aspect, alone or in combination with one or more of the first and second aspects, order of the first TPMI index and the second TPMI index is indicated by a row in a table associated with a value indicated by the codepoint. In a fourth aspect, alone or in combination with one or more of the first through third aspects, a reverse order of the first TPMI index and the second TPMI index is indicated by another row in the table associated with another codepoint value. In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, identifying the first TPMI index and the second TPMI index comprises identifying, based at least in part on a value indicated by the codepoint, a row in a table specifying the first TPMI index and the second TPMI index.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, identifying the first TPMI index and the second TPMI index comprises identifying the row from a subset of rows of the table indicated in a radio resource control communication or a medium access control element communication. In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the one or more codepoints include a first codepoint, in a first Precoding Information and Number of Layers field of the downlink communication, indicating the first TPMI index and a second codepoint, in a second Precoding Information and Number of Layers field of the downlink communication, indicating a second TPMI index of the plurality of TPMI indices.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the downlink communication includes an SRI codepoint that indicates one or more SRS resources, having a usage set to codebook, for the PUSCH transmission. In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, indicates a plurality of SRS resources; and process <NUM> further comprises identifying, based at least in part on the one or more codepoints, a second TPMI index, of the plurality of TPMI indices, for a second repetition of the PUSCH transmission; and identifying, based at least in part on the SRI codepoint, a first SRS resource of, the plurality of SRS resources, for the first repetition of the PUSCH transmission and a second SRS resource, of the plurality of SRS resources, for a second repetition of the PUSCH transmission.

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, an order of the first SRS resource and the second SRS resource is indicated by a row in a table associated with a value indicated by the SRI codepoint. In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, a reverse order of the first SRS resource and the second SRS resource is indicated by another row in the table associated with another SRI codepoint value.

In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, identifying the first SRS resource and the second SRS resource comprises identifying, based at least in part on a value indicated by the SRI codepoint, a row in a table specifying the first SRS resource and the second SRS resource.

In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, process <NUM> further comprises identifying spatial relation information, associated with the first SRS resource, as a spatial domain transmission filter to be used for the first repetition of the PUSCH transmission; and identifying spatial relation information, associated with the second SRS resource, as a spatial domain transmission filter to be used for the second repetition of the PUSCH transmission. In a fourteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, process <NUM> further comprises identifying a quantity of SRS ports, associated with the first SRS resource, as a quantity of transmit antenna ports for the first repetition of the PUSCH transmission, wherein the first TPMI index is interpreted based at least in part on the first SRS resource; and identifying a quantity of SRS ports, associated with the second SRS resource, as a quantity of transmit antenna ports for the second repetition of the PUSCH transmission, wherein the second TPMI index is interpreted based at least in part on the second SRS resource.

In a fifteenth aspect, alone or in combination with one or more of the first through fourteenth aspects, the SRI codepoint indicates a single SRS resource; and process <NUM> further comprises identifying, based at least in part on the SRI codepoint, the SRS resource for the first repetition of the PUSCH transmission and a second repetition of the PUSCH transmission. In a sixteenth aspect, alone or in combination with one or more of the first through fifteenth aspects, identifying the first TPMI index comprises identifying , based at least in part on a value indicated by a codepoint of the one or more codepoints, a row in a first table specifying the first TPMI index, or identifying , based at least in part on a value indicated by the codepoint, a row in a first table specifying the plurality of TPMI indices, wherein the first TPMI index is listed first among the plurality of TPMI indices in the row.

In a seventeenth aspect, alone or in combination with one or more of the first through sixteenth aspects, identifying, based at least in part on the one or more codepoints, a second TPMI index, of the plurality of TPMI indices, for a second repetition of the PUSCH transmission; and identifying, based at least in part on the SRI codepoint, an SRS resource of the one or more SRS resources for the first repetition of the PUSCH transmission and for the second repetition of the PUSCH transmission. In an eighteenth aspect, alone or in combination with one or more of the first through seventeenth aspects, process <NUM> further comprises identifying spatial relation information, associated with the SRS resource, as a spatial domain transmission filter to be used for the first repetition of the PUSCH transmission and for the second repetition of the PUSCH transmission.

In a nineteenth aspect, alone or in combination with one or more of the first through eighteenth aspects, the SRS resource is identified, in a radio resource control communication, among a plurality of candidate SRS resources that are permitted to be associated with multiple TPMI indices. In a twentieth aspect, alone or in combination with one or more of the first through nineteenth aspects, the SRS resource is associated with the first TPMI index and the second TPMI index; and identifying the first TPMI index and the second TPMI index comprises identifying, based at least in part on a value indicated by the one or more codepoints, a row in a table specifying the first TPMI index and the second TPMI index.

In a twenty-first aspect, alone or in combination with one or more of the first through twentieth aspects, the SRI codepoint indicates a single SRS resource; and process <NUM> further comprises identifying, based at least in part on the SRI codepoint, the SRS resource for the first repetition of the PUSCH transmission and a second repetition of the PUSCH transmission. In a twenty-second aspect, alone or in combination with one or more of the first through twenty-first aspects, identifying the first TPMI index comprises identifying, based at least in part on a value indicated by a codepoint of the one or more codepoints, a row in a first table specifying the first TPMI index, or identifying, based at least in part on a value indicated by the codepoint, a row in a first table specifying the plurality of TPMI indices, wherein the first TPMI index is listed first among the plurality of TPMI indices in the row.

In a twenty-third aspect, alone or in combination with one or more of the first through twenty-second aspects, the SRI codepoint is configurable by radio resource control signaling to indicate one SRS resource or a plurality of SRS resources based at least in part on a UE capability of the UE. In a twenty-fourth aspect, alone or in combination with one or more of the first through twenty-third aspects, process <NUM> further comprises identifying, based at least in part on the SRI codepoint, a first SRS resource of, the plurality of SRS resources, for the first repetition of the PUSCH transmission; identifying, for a second repetition of the PUSCH transmission a second TPMI index of the plurality of TPMI indices based at least in part on the one or more codepoints and a second SRS resource of the plurality of SRS resources based at least in part on the SRI codepoint; and identifying, for a third repetition of the PUSCH transmission, the first TPMI index and the first SRS resource.

In a twenty-fifth aspect, alone or in combination with one or more of the first through twenty-fourth aspects, a mapping of the first TPMI index and the first SRS resource to the first repetition and to the third repetition, and a mapping of the second TPMI index and the second SRS resource to the second repetition, are based at least in part on a fixed alternating mapping for the first TPMI index, the first SRS resource, the second TPMI index, and the second SRS resource. In a twenty-sixth aspect, alone or in combination with one or more of the first through twenty-fifth aspects, a mapping of the first TPMI index and the first SRS resource to the first repetition and to the third repetition, and a mapping of the second TPMI index and the second SRS resource to the second repetition, are based at least in part on a mapping for the first TPMI index, the first SRS resource, the second TPMI index, and the second SRS resource indicated in a radio resource control communication or a downlink control information communication.

In a twenty-seventh aspect, alone or in combination with one or more of the first through twenty-sixth aspects, process <NUM> further comprises configuring respective redundancy versions for the first repetition of the PUSCH transmission and for the third repetition of the PUSCH transmission based at least in part on a redundancy version sequence; and configuring a redundancy version for the second repetition of the PUSCH transmission based at least in part on an offset value applied to the redundancy version sequence. In a twenty-eighth aspect, alone or in combination with one or more of the first through twenty-seventh aspects, the downlink communication is a DCI communication; the one or more codepoints are indicated in a Precoding Information and Number of Layers field in the DCI communication; and the SRI codepoint is indicated in an SRI field in the DCI communication.

In a twenty-ninth aspect, alone or in combination with one or more of the first through twenty-eighth aspects, the PUSCH transmission is configured by an uplink configured grant configuration; the downlink communication is an RRC communication configuring the uplink configured grant configuration; the one or more codepoints are indicated in a preocdingAndNumberOfLayers field in the RRC communication; and the SRI codepoint is indicated in an srs-ResourceIndicator field in the RRC communication. In a thirtieth aspect, alone or in combination with one or more of the first through twenty-ninth aspects, the PUSCH transmission is configured by an uplink configured grant configuration via a radio resource control communication; the downlink communication is a DCI communication that activates the uplink configured grant configuration; the one or more codepoints are indicated in a Precoding Information and Number of Layers field in the DCI communication; and the SRI codepoint is indicated in an SRI field in the DCI communication.

<FIG> is a diagram illustrating an example process <NUM> performed, for example, by a user equipment (UE), in accordance with various aspects of the present disclosure. Example process <NUM> is an example where the UE (e.g., UE <NUM>) performs operations associated with TPMI and/or SRI indication for codebook-based PUSCH repetition.

As shown in <FIG>, in some aspects, process <NUM> may include receiving a downlink communication that schedules a first set of repetitions of a PUSCH transmission associated with a first uplink beam and a second set of repetitions of the PUSCH transmission associated with a second uplink beam (block <NUM>). For example, the UE (e.g., using reception component <NUM>, depicted in <FIG>) may receive a downlink communication that schedules a first set of repetitions of a PUSCH transmission associated with a first uplink beam and a second set of repetitions of the PUSCH transmission associated with a second uplink beam, as described above.

As further shown in <FIG>, in some aspects, process <NUM> may include configuring respective redundancy versions for the first set of repetitions based at least in part on a first redundancy version sequence associated with the first uplink beam (block <NUM>). For example, the UE (e.g., using configuration component <NUM>, depicted in <FIG>) may configure respective redundancy versions for the first set of repetitions based at least in part on a first redundancy version sequence associated with the first uplink beam, as described above.

As further shown in <FIG>, in some aspects, process <NUM> may include configuring respective redundancy versions for the second set of repetitions based at least in part on a second redundancy version sequence associated with the second uplink beam (block <NUM>). For example, the UE (e.g., using the configuration component <NUM>, depicted in <FIG>) may configure respective redundancy versions for the second set of repetitions based at least in part on a second redundancy version sequence associated with the second uplink beam, as described above.

In a first aspect, the second redundancy sequence comprises the first redundancy sequence having a starting point that is shifted based at least in part on a redundancy version offset.

<FIG> is a diagram of an example apparatus <NUM> for wireless communication. The apparatus <NUM> may be a UE, or a UE may include the apparatus <NUM>. In some aspects, the apparatus <NUM> includes a reception component <NUM> and a transmission component <NUM>, which may be in communication with one another (for example, via one or more buses and/or one or more other components). As shown, the apparatus <NUM> may communicate with another apparatus <NUM> (such as a UE, a base station, or another wireless communication device) using the reception component <NUM> and the transmission component <NUM>. As further shown, the apparatus <NUM> may include an identification component <NUM> and/or a configuration component <NUM>, among other examples.

In some aspects, the apparatus <NUM> may be configured to perform one or more operations described herein in connection with <FIG>. Additionally, or alternatively, the apparatus <NUM> may be configured to perform one or more processes described herein, such as process <NUM> of <FIG>. In some aspects, the apparatus <NUM> and/or one or more components shown in <FIG> may include one or more components of the UE described above in connection with <FIG>. Additionally, or alternatively, one or more components shown in <FIG> may be implemented within one or more components described above in connection with <FIG>. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or a processor to perform the functions or operations of the component.

The reception component <NUM> may receive (e.g., from the apparatus <NUM>) a downlink communication that includes one or more codepoints indicating a plurality of TPMI indices. The identification component <NUM> may identify, based at least in part on the one or more codepoints, a first TPMI index, of the plurality of TPMI indices, for a first repetition of a PUSCH transmission, where the PUSCH transmission is a codebook-based PUSCH transmission.

The identification component <NUM> may identify, based at least in part on the SRI codepoint, a first SRS resource of a plurality of SRS resources, for the first repetition of the PUSCH transmission. The identification component <NUM> may identify for a second repetition of the PUSCH transmission, a second TPMI index of the plurality of TPMI indices based at least in part on the one or more codepoints, and a second SRS resource of the plurality of SRS resources based at least in part on the SRI codepoint. The identification component <NUM> may identify, for a third repetition of the PUSCH transmission the first TPMI index, and the first SRS resource, the first TPMI index and the first SRS resource.

The configuration component <NUM> may configure respective redundancy versions for the first repetition of the PUSCH transmission and for the third repetition of the PUSCH transmission based at least in part on a redundancy version sequence. The configuration component <NUM> may configure a redundancy version for the second repetition of the PUSCH transmission based at least in part on an offset value applied to the redundancy version sequence.

The identification component <NUM> may identify spatial relation information, associated with the first SRS resource, as a spatial domain transmission filter to be used for the first repetition of the PUSCH transmission. The identification component <NUM> may identify spatial relation information, associated with the second SRS resource, as a spatial domain transmission filter to be used for the second repetition of the PUSCH transmission.

The identification component <NUM> may identify, based at least in part on the one or more codepoints, a second TPMI index, of the plurality of TPMI indices, for a second repetition of the PUSCH transmission. The identification component <NUM> may identify, based at least in part on the SRI codepoint, an SRS resource of the one or more SRS resources for the first repetition of the PUSCH transmission and for the second repetition of the PUSCH transmission. The identification component <NUM> may identify spatial relation information, associated with the SRS resource, as a spatial domain transmission filter to be used for the first repetition of the PUSCH transmission and for the second repetition of the PUSCH transmission.

<FIG> is a diagram of an example apparatus <NUM> for wireless communication. The apparatus <NUM> may be a UE, or a UE may include the apparatus <NUM>. In some aspects, the apparatus <NUM> includes a reception component <NUM> and a transmission component <NUM>, which may be in communication with one another (for example, via one or more buses and/or one or more other components). As shown, the apparatus <NUM> may communicate with another apparatus <NUM> (such as a UE, a base station, or another wireless communication device) using the reception component <NUM> and the transmission component <NUM>. As further shown, the apparatus <NUM> may include a configuration component <NUM>.

The reception component <NUM> may receive (e.g., from the apparatus <NUM>) a downlink communication that schedules a first set of repetitions of a PUSCH transmission associated with a first uplink beam and a second set of repetitions of the PUSCH transmission associated with a second uplink beam. The configuration component <NUM> may configure respective redundancy versions for the first set of repetitions based at least in part on a first redundancy version sequence associated with the first uplink beam. The configuration component <NUM> may configure respective redundancy versions for the second set of repetitions based at least in part on a second redundancy version sequence associated with the second uplink beam.

Claim 1:
A method (<NUM>) of wireless communication performed by a user equipment, UE, (<NUM>), comprising:
receiving (<NUM>, <NUM>) a downlink communication that includes one or more codepoints indicating a plurality of transmit precoder matrix indicator, TPMI, indices, wherein the one or more codepoints includes a single codepoint, in a Precoding Information and Number of Layers field of the downlink communication, indicating the plurality of TPMI indices; and
identifying (<NUM>, <NUM>), based at least in part on the one or more codepoints, a first TPMI index, of the plurality of TPMI indices, for configuring a first repetition of a physical uplink shared channel, PUSCH, transmission and a second TPMI index, of the plurality of TPMI indices, for configuring a second repetition of the PUSCH transmission,
wherein the PUSCH transmission is a codebook-based PUSCH transmission.