CONFIGURATIONS AND SWITCHING BETWEEN DIFFERENT MODES OF SDM PUSCH

Apparatus, methods, and computer program products for transmitting SDM PUSCH are provided. An example method may include receiving, from a second network entity, downlink control information (DCI) scheduling a physical uplink shared channel (PUSCH) transmission, where the PUSCH transmission includes a first portion associated with a first subset of layers within a set of layers and a second portion associated with a second subset of layers within the set of layers. The example method may further include mapping at least one transport block (TB) or codeword (CW) to the first portion or the second portion based on the DCI or a radio resource control (RRC) configuration. The example method may further include transmitting the at least one TB or CW to the second network entity.

TECHNICAL FIELD

The present disclosure relates generally to communication systems, and more particularly, to wireless communication systems with spatial division multiplexing (SDM) physical uplink shared channel (PUSCH).

INTRODUCTION

BRIEF SUMMARY

In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus at a first network entity, such as a user equipment (UE), are provided. The apparatus may include a memory and at least one processor coupled to the memory. The memory and the at least one processor coupled to the memory may be configured to receive, from a second network entity, downlink control information (DCI) scheduling a physical uplink shared channel (PUSCH) transmission, where the PUSCH transmission includes a first portion associated with a first subset of layers within a set of layers and a second portion associated with a second subset of layers within the set of layers. The memory and the at least one processor coupled to the memory may be further configured to map at least one transport block (TB) or codeword (CW) to the first portion or the second portion based on the DCI or a radio resource control (RRC) configuration. The memory and the at least one processor coupled to the memory may be further configured to transmit the at least one TB or CW to the second network entity.

In another aspect of the disclosure, a method, a computer-readable medium, and an apparatus at a first network entity, such as a base station, are provided. The apparatus may include a memory and at least one processor coupled to the memory. The memory and the at least one processor coupled to the memory may be configured to transmit, to a second network entity, DCI scheduling a PUSCH transmission including a first portion and a second portion, where the PUSCH transmission includes a first portion associated with a first subset of layers within a set of layers and a second portion associated with a second subset of layers within the set of layers. The memory and the at least one processor coupled to the memory may be further configured to receive at least one TB or CW from the second network entity, where the at least one TB or CW is mapped to the first portion or the second portion based on the DCI or an RRC configuration.

DETAILED DESCRIPTION

Referring again toFIG.1, in some aspects, the UE104may include a PUSCH component198. In some aspects, the PUSCH component198may be configured to receive, from a second network entity, DCI scheduling a PUSCH transmission, where the PUSCH transmission includes a first portion associated with a first subset of layers within a set of layers and a second portion associated with a second subset of layers within the set of layers. In some aspects, the PUSCH component198may be further configured to map at least one TB or CW to the first portion or the second portion based on the DCI or an RRC configuration. In some aspects, the PUSCH component198may be further configured to transmit the at least one TB or CW to the second network entity.

In certain aspects, the base station102may include a PUSCH component199. In some aspects, the PUSCH component199may be configured to transmit, to a second network entity, DCI scheduling a PUSCH transmission including a first portion and a second portion, where the PUSCH transmission includes a first portion associated with a first subset of layers within a set of layers and a second portion associated with a second subset of layers within the set of layers. In some aspects, the PUSCH component199may be further configured to receive at least one TB or CW from the second network entity, where the at least one TB or CW may be mapped to the first portion or the second portion based on the DCI or an RRC configuration.

As described herein, a node (which may be referred to as a node, a network node, a network entity, or a wireless node) may include, be, or be included in (e.g., be a component of) a base station (e.g., any base station described herein), a UE (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, an integrated access and backhauling (IAB) node, a distributed unit (DU), a central unit (CU), a remote/radio unit (RU) (which may also be referred to as a remote radio unit (RRU)), and/or another processing entity configured to perform any of the techniques described herein. For example, a network node may be a UE. As another example, a network node may be a base station or network entity. As another example, a first network node may be configured to communicate with a second network node or a third network node. In one aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a UE. In another aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a base station. In yet other aspects of this example, the first, second, and third network nodes may be different relative to these examples. Similarly, reference to a UE, base station, apparatus, device, computing system, or the like may include disclosure of the UE, base station, apparatus, device, computing system, or the like being a network node. For example, disclosure that a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node. Consistent with this disclosure, once a specific example is broadened in accordance with this disclosure (e.g., a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node), the broader example of the narrower example may be interpreted in the reverse, but in a broad open-ended way. In the example above where a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node, the first network node may refer to a first UE, a first base station, a first apparatus, a first device, a first computing system, a first set of one or more one or more components, a first processing entity, or the like configured to receive the information; and the second network node may refer to a second UE, a second base station, a second apparatus, a second device, a second computing system, a second set of one or more components, a second processing entity, or the like.

As described herein, communication of information (e.g., any information, signal, or the like) may be described in various aspects using different terminology. Disclosure of one communication term includes disclosure of other communication terms. For example, a first network node may be described as being configured to transmit information to a second network node. In this example and consistent with this disclosure, disclosure that the first network node is configured to transmit information to the second network node includes disclosure that the first network node is configured to provide, send, output, communicate, or transmit information to the second network node. Similarly, in this example and consistent with this disclosure, disclosure that the first network node is configured to transmit information to the second network node includes disclosure that the second network node is configured to receive, obtain, or decode the information that is provided, sent, output, communicated, or transmitted by the first network node.

At least one of the TX processor368, the RX processor356, and the controller/processor359may be configured to perform aspects in connection with PUSCH component198ofFIG.1.

FIG.4is a diagram400illustrating a base station402in communication with a UE404. Referring toFIG.4, the base station402may transmit a beamformed signal to the UE404in one or more of the directions402a,402b,402c,402d,402e,402f,402g,402h. The UE404may receive the beamformed signal from the base station402in one or more receive directions404a,404b,404c,404d. The UE404may also transmit a beamformed signal to the base station402in one or more of the directions404a-404d. The base station402may receive the beamformed signal from the UE404in one or more of the receive directions402a-402h. The base station402/UE404may perform beam training to determine the best receive and transmit directions for each of the base station402/UE404. The transmit and receive directions for the base station402may or may not be the same. The transmit and receive directions for the UE404may or may not be the same.

In response to different conditions, the UE404may determine to switch beams, e.g., between beams402a-402h. The beam at the UE404may be used for reception of downlink communication and/or transmission of uplink communication. In some examples, the base station402may send a transmission that triggers a beam switch by the UE404. For example, the base station402may indicate a transmission configuration indication (TCI) state change, and in response, the UE404may switch to a new beam for the new TCI state of the base station402. In some instances, a UE may receive a signal, from a base station, configured to trigger a transmission configuration indication (TCI) state change via, for example, a MAC control element (CE) command. The TCI state change may cause the UE to find the best UE receive beam corresponding to the TCI state from the base station, and switch to such beam. Switching beams may allow for enhanced or improved connection between the UE and the base station by ensuring that the transmitter and receiver use the same configured set of beams for communication.

The base station402and the UE404may each include multiple transmission reception points (TRPs). Each TRP may include different RF modules having a shared hardware and/or software controller. Each TRP may perform separate baseband processing. Each TRP may include a different antenna panel or a different set of antenna elements.

A set of time and frequency resources that may be used for one or more transmissions of SRS may be referred to as an “SRS resource set.” In some communication systems, the SRS resource set applicability for an SRS resource set may be configured by a higher layer parameter, such as “usage” associated with the SRS resource set, such as in the SRS-ResourceSet parameter. For example, usage may be configured as one of beam management, codebook, non-codebook, antenna switching, or the like. Each SRS resource set may be configured with one or more (such as up to 16) SRS resources. Each SRS resource set may be aperiodic, semi-persistent, or periodic.

In some wireless communication systems, two types of PUSCH transmissions may be supported. The first type may be referred to as codebook based transmission. For codebook based transmission, a UE may be configured with one SRS resource set with “usage” set to “codebook.” For example, a maximum of 4 SRS resources within the set may be configured for the UE. Each SRS resource may be radio resource control (RRC) configured with a number of ports, such as one or more ports. The SRS resource indicator (SRI) field in the UL DCI scheduling the PUSCH may indicate one SRS resource. The number of ports configured for the indicated SRS resource may determine number of antenna ports for the PUSCH. The PUSCH may be transmitted with the same spatial domain filter (which may be otherwise referred to as a “beam”) as the indicated SRS resources. The number of layers (i.e., rank) or transmitted precoding matrix indicator (TPMI) (e.g., for precoder) for the scheduled PUSCH may be determined from a separate DCI field “Precoding information and number of layers.”

For non-codebook-based transmission, a UE may be configured with one SRS resource set with “usage” set to “non-codebook.” For example, a maximum of 4 SRS resources within the set may be configured for the UE. Each SRS resource may be RRC configured with one port. The SRI field in the UL DCI scheduling the PUSCH may indicate one or more SRS resources. A number of indicated SRS resources may determine the rank (i.e., number of layers) for the scheduled PUSCH. The PUSCH may be transmitted with the same precoder as well as a same spatial domain filter (i.e., beam) as the indicated SRS resources.

In some aspects, multi-TRP or multi-panel may be used for enhancing reliability and robustness for PUSCH. For example, if one link using a first TRP is blocked and one repetition of the PUSCH fails to be received, another repetition may be received and decoded by another TRP. Therefore, with multi-TRP, diversity of transmission is increased and the PUSCH transmission may be more reliable. A repetition may be otherwise referred to as a transmission occasion.

A PUSCH transmission may be transmitted in one or more repetitions (which may also be referred to as “portion” herein) using different types of repetition. For different PUSCH repetitions corresponding to the same TB, the repetitions are transmitted in different slots in type A repetition while the repetitions are transmitted in different mini-slots in type B repetition. The number of repetitions may be RRC configured or may be indicated dynamically, such as by utilizing a time-domain resource assignment (TDRA) field of DCI. In some wireless communication systems, all the repetitions may be transmitted with the same beam. For example, the SRI field of the DCI may be applied to all the repetitions. SRI may be a field in the UL DCI that determines the beam or power control parameters for PUSCH by pointing to one or more SRS resources within an SRS resource set.

In some other wireless communication systems, different PUSCH repetitions are intended to be received at different TRPs, panels, or antennas at the base station and the repetitions may use the same beam or different beams. For example, two sets of repetitions that each include its own beam associated with its own power control parameters may be provided. Each set of repetitions may include one or more repetitions. Such two sets of repetitions may correspond with two SRS resource sets which may include DCI that may indicate two beams and two sets of power control parameters by indicating one or more SRS resources within each of the two SRS resource sets. Aspects herein enable association between the two SRS resource sets and the two set of PUSCH repetitions.

FIG.5is a diagram500illustrating communications between a UE502and a network entity504(e.g., a base station). As illustrated inFIG.5, the network entity504may configure the UE502with at least two SRS resource sets506. In some aspects, the network entity504may not support dynamic order switching. In some aspects, the SRS resource sets506may include an SRS resource set identifier (ID), which may be represented by an srs-ResourceSetID field in an SRS-ResourceSet parameter. In some aspects, the SRS resource sets506may include a parameter that represents an order, such as an SRS-ResourceSetOrder parameter. The network entity504may be a network node. A network node may be implemented as an aggregated base station, as a disaggregated base station, an integrated access and backhaul (IAB) node, a relay node, a sidelink node, or the like. A network entity can be implemented in an aggregated or monolithic base station architecture, or alternatively, in a disaggregated base station architecture, and may include one or more of a CU, a DU, a RU, a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC), or a Non-Real Time (Non-RT) RIC.

In some aspects, the network entity504may transmit a DCI508to the UE502. In some aspects, dynamic order switching may be supported by the network entity504. In some aspects, the DCI508may include one or more bits, such as two bits, to indicate an order for the SRS resource sets in the SRS resource sets506.

The UE502may transmit one or more repetitions of a PUSCH, such as a first PUSCH repetition510, a second PUSCH repetition512, a third PUSCH repetition514, and a fourth PUSCH repetition516, to the network entity504. In some aspects, within two SRS resource sets in the SRS resource sets506, the SRS resource set with the lowest ID may correspond with the first set of repetitions (first may be the one that appears first in time) and the SRS resource set with the second lowest ID corresponds to the second set of repetitions. For example, a first set of PUSCH repetitions may include the first PUSCH repetition510and the second PUSCH repetition512while the second set of PUSCH repetitions may include the third PUSCH repetition514and the fourth PUSCH repetition516. The first set of PUSCH repetitions may correspond with the SRS resource set with the lowest ID.

In some aspects, within two SRS resource sets in the SRS resource sets506, the SRS resource set with the highest ID may correspond with the first set of repetitions and the SRS resource set with the second highest ID corresponds to the second set of repetitions. For example, a first set of PUSCH repetitions may include the first PUSCH repetition510and the second PUSCH repetition512while the second set of PUSCH repetitions may include the third PUSCH repetition514and the fourth PUSCH repetition516. The first set of PUSCH repetitions may correspond with the SRS resource set with the highest ID. In some aspects, the SRS resource set associated with the first PUSCH repetition510, the second PUSCH repetition512, the third PUSCH repetition514, and the fourth PUSCH repetition516, may be determined based on the parameter that represents an order.

In some aspects, if dynamic order switching is supported by the network entity504and the DCI508include one or more bits that represent an order, the one or more bits may represent a DCI code point that may correspond with an order. For example, a DCI code point may be 0, 1, 2, or 3 and may be associated with an order 1, 2, 12, and 21. Table 2 illustrates an example correspondence between a set of DCI codepoints and a corresponding set of relationships that indicate an order of PUSCH transmission.

As illustrated in Table 2, the SRS resource set indicator may be based on whether 2 SRS resource sets are configured corresponding to that DCI format.

FIG.6is a diagram600illustrating an example cyclical mapping pattern for PUSCH repetitions. As illustrated inFIG.6, the DCI602may schedule four PUSCH repetitions, PUSCH repetition604, PUSCH repetition606, PUSCH repetition608, and PUSCH repetition610. For cyclical beam mapping, the first PUSCH repetition604and the third PUSCH repetition608may be associated with a first beam and a first set of power control parameters. The second PUSCH repetition606and the fourth PUSCH repetition610may be associated with a second beam and a second set of power control parameters. The cyclical mapping pattern may be applicable for both Type A and Type B repetitions.

FIG.7is a diagram700illustrating an example mapping pattern for PUSCH repetitions. As illustrated inFIG.7, the DCI702schedule may schedule four PUSCH repetitions. The four PUSCH repetitions may be arranged differently based on the codepoint in the DCI702. For example, based on codepoint 0, the four PUSCH repetitions may be PUSCH repetition704A, PUSCH repetition706A, PUSCH repetition708A, and PUSCH repetition710A, which may be all based on the first beam and the first set of power control parameters (and toward the first TRP). Based on codepoint 1, the four PUSCH repetitions may be PUSCH repetition704B, PUSCH repetition706B, PUSCH repetition708B, and PUSCH repetition710B, which may be all based on the second beam and the second set of power control parameters (and toward the second TRP). Based on codepoint 2, the four PUSCH repetitions may be PUSCH repetition704C, PUSCH repetition706C, PUSCH repetition708C, and PUSCH repetition710C, where the PUSCH repetition704C and the PUSCH repetition708C may be based on the first beam and the first set of power control parameters (and toward the first TRP) and the PUSCH repetition706C and the PUSCH repetition710C may be based on the second beam and the second set of power control parameters (and toward the second TRP). Based on codepoint 3, the four PUSCH repetitions may be PUSCH repetition704D, PUSCH repetition706D, PUSCH repetition708D, and PUSCH repetition710D, where the PUSCH repetition706D and the PUSCH repetition710D may be based on the first beam and the first set of power control parameters (and toward the first TRP) and the PUSCH repetition704D and the PUSCH repetition708D may be based on the second beam and the second set of power control parameters (and toward the second TRP).

In some aspects, a PUSCH transmission may be based on SDM and may be associated with multiple sets of DM-RS ports, which may be in turn respectively associated with multiple sets of MIMO layers in multiple panels at the UE. The PUSCH transmission may be transmitted based on the multiple sets of MIMO layers in multiple panels at the UE with different transmission beams, precoders, and power control parameters. For example, a first portion of the PUSCH transmission may be transmitted via a first set of MIMO layers associated with a first set of DM-RS ports via a first panel using a first transmission beam (and associated TCI state) to a first TRP of a base station. A second portion of the PUSCH transmission may be transmitted via a second set of MIMO layers associated with a second set of DM-RS ports via a second panel using a second transmission beam (and associated TCI state) to a second TRP of a base station. Such a PUSCH transmission may be based on one TB and one CW or more than one TB and more than one CW. A TB may be a payload of data passed between a medium access control (MAC) layer and a PHY layer for transmitting data in the TB. The PHY layer may convert the TB into a CW by appending (which may also be referred to as “scrambling”) a cyclic redundancy check (CRC) to the TB, segment the TB into multiple code blocks of configured size (e.g., segmented into code blocks between 40 and 6144 bits) or padded to a configured size (e.g., padded to 40 bits with 0s if the TB is smaller than 40 bits), then process each code block with a turbo coder and reassemble the code blocks into a CW. Such a process after appending CRC may also be collectively referred to as encoding and modulation.

As used herein, the term “SDM PUSCH” may refer to a PUSCH transmission that includes different portions based on SDM. As used herein, the term “repetition” and “portion” may be used interchangeably to refer to repetitions of a PUSCH.FIG.8is a diagram800illustrating a first mode of processing SDM PUSCH transmission (Mode 1). As illustrated inFIG.8, to transmit a PUSCH transmission, a single TB802may be used for generating a CW806after encoding, scrambling, and modulation at804. The CW806may be mapped to (at808) a first set of MIMO layers810A associated with a first SRI/TPMI (e.g., as indicated by DCI) associated with a first panel of the UE, and then transmitted using a transmit beam associated with the first set of MIMO layers810A to a first TRP820A of the base station820. The CW806may also be mapped to (at808) a second set of MIMO layers810B associated with a second SRI/TPMI (e.g., as indicated by DCI) associated with a second panel of the UE, and then transmitted using a transmit beam associated with the second set of MIMO layers810B to a second TRP820B of the base station820. Transmitting different portions of the PUSCH transmission that correspond with transmission using different set of layers that are respectively associated with different panels and beams based on a same TB and a same CW may be a first mode of processing SDM PUSCH transmission. A single NDI, a single RV, and a single MCS may be used for the TB802and the CW806.

FIG.9is a diagram900illustrating example of a second mode of processing SDM PUSCH transmission. As illustrated inFIG.9, to transmit a PUSCH transmission, a first portion of the PUSCH transmission may correspond to a first TB902A, which may be used for generating a CW906A after encoding, scrambling, and modulation at904A. The CW906A may be mapped to (at908) a first set of MIMO layers910A associated with a first SRI/TPMI (e.g., as indicated by DCI) associated with a first panel of the UE, and then transmitted using a transmit beam associated with the first set of MIMO layers910A to a first TRP920A of the base station920. A second portion of the PUSCH transmission may correspond to a second TB902B, which may be used for generating a CW906B after encoding, scrambling, and modulation at904B. The CW906B may be mapped to (at908) a second set of MIMO layers910B associated with a second SRI/TPMI (e.g., as indicated by DCI) associated with a second panel of the UE, and then transmitted using a transmit beam associated with the second set of MIMO layers910B to a second TRP920B of the base station920. The TB902A may be associated with a first modulation and coding scheme (MCS), a first redundancy version (RV), and a first new data indicator (NDI). The TB902B may be associated with a second MCS, a second RV, and a second NDI. The first MCS, first RV, and the first NDI may be represented by a DCI in one or more fields separate from one or more fields representing the second MCS, the second RV, and the second NDI. A value of the first MCS may be identical with or different from the second MCS. A value of the first NDI may be identical with or different from the second NDI. A value of the first RV may be identical with or different from the second RV. Transmitting different portions of the PUSCH transmission that correspond with transmission using different set of layers that are respectively associated with different panels and beams based on different TBs and different CWs may be a second mode of processing SDM PUSCH transmission (Mode 2).

The first mode of processing SDM PUSCH transmission and the second mode of processing SDM PUSCH transmission may provide different advantages that may be situational. For example, the first mode may be more suitable to reliability/diversity as the TB is mapped to layers from both sets, which means that if one beam is blocked, the TB may be still decoded from the layers mapped to the other beam. The second mode may be more suitable for capacity increase because different MCS may be used to adapt the coding rate and modulation order to the effective signal to interference and noise ratio (SINR) of each set of layers/each beam. Aspects provided herein may enable a UE to distinguish and determine how to process SDM PUSCH transmission. Aspects provided herein may also enable a UE to use different CWs and TBs associated with different NDI, RV, and MCS regardless of whether the UE is operating in sTRP or mTRP. Aspects provided herein may also provide additional modes of processing SDM PUSCH transmission that may be more efficient.

FIG.10is a diagram1000illustrating example communications between a UE1002and a network entity1004(e.g., a base station). The network entity1004may be a network node. A network node may be implemented as an aggregated base station, as a disaggregated base station, an IAB node, a relay node, a sidelink node, or the like. A network entity can be implemented in an aggregated or monolithic base station architecture, or alternatively, in a disaggregated base station architecture, and may include one or more of a CU, a DU, a RU, a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC), or a Non-Real Time (Non-RT) RIC.

As illustrated inFIG.10, the network entity1004may configure the UE1002with at least two SRS resource sets1006, which may be configured based on a RRC configuration1007. In some aspects, each of the SRS resource sets1006may include an SRS resource set ID, which may be represented by an srs-ResourceSetID field in an SRS-ResourceSet parameter. In some aspects, the network entity1004may transmit a DCI1008to the UE1002. In some aspects, the DCI1008may include one or more bits, such as two bits (e.g., the codepoints illustrated in Table 2), to indicate an order for different portions/transmissions in the PUSCH transmission1014. The DCI1008may schedule an SDM PUSCH. In some aspects, the DCI1008may include at least two sets of MIMO layers that may be respectively associated with at least two sets of DM-RS ports respectively associated with at least two transmit beams (and TCI states) or two SRS resource sets. The UE1002may determine whether to process the SDM PUSCH (at1012) based on: 1) one TB and CW is mapped to both sets of MIMO layers (first mode of processing SDM PUSCH), 2) two respective TBs and CWs are mapped to respective sets of layers (second mode of processing SDM PUSCH), or 3) other ways of mapping TB and CW to the MIMO layers (other mode(s) of processing SDM PUSCH), based on the DCI or the RRC configuration1007. In some aspects, after processing the SDM PUSCH, the UE1002may transmit the PUSCH transmission1014to the network entity1004.

In some aspects, the RRC configuration1007may be per bandwidth part (BWP) or per serving cell. In some aspects, the RRC configuration1007may configure one mode of processing SDM PUSCH and the UE1002may process the SDM PUSCH accordingly at1012. In some aspects, the RRC configuration1007may configure more than mode of processing SDM PUSCH and the UE1002may use additional signaling to determine which mode to use when processing the SDM PUSCH at1012.

In some aspects, the DCI1008may explicitly or implicitly indicate the first mode of processing SDM PUSCH or the second mode of processing SDM PUSCH. In some aspects, the DCI1008may include two MCS/NDI/RV fields including a first set of MCS/RV/NDI fields and a second set of MCS/RV/NDI fields associated with two TBs including a first TB and a second TB. The DCI may dynamically disable (e.g., in the DCI1008or in another DCI) one of the TBs based on the MCS/RV/NDI values for the corresponding TB being set to one or more configured values. If neither the first set of MCS/RV/NDI fields nor the second set of MCS/RV/NDI fields associated with a TB is disabled, the UE1002may process the SDM PUSCH based on the second mode. If the first set of MCS/RV/NDI fields and the second set of MCS/RV/NDI fields are not disabled, the UE1002may process the SDM PUSCH based on the first mode.

In some aspects, an SRS resource set indicator (such as the codepoint) in the DCI1008may be used for indicating the first mode of processing SDM PUSCH and the second mode of processing SDM PUSCH. An example is illustrated in Table 3 below:

As illustrated in table 3, for Mode 2, SRS resource set indicator may also indicate whether layers of the first TB or the second TB map to the first SRS resource set or the second SRS resource set. As illustrated in table 3, codepoint 0 and codepoint 1 may indicate that the PUSCH is based on sTRP without SDM. Codepoint 2 may indicate using the first mode of processing SDM PUSCH where a single TB is mapped to different portions of the SDM PUSCH based on different sets of MIMO layers towards different TRPs (and additionally indicate the association between the SRS resource sets and the sets of MIMO layers). Codepoint 3 may indicate using the first mode of processing SDM PUSCH where a single TB is mapped to different portions of the SDM PUSCH based on different sets of MIMO layers towards different TRPs (and additionally indicate the association between the SRS resource sets and the sets of MIMO layers). Codepoint 4 may indicate using the second mode of processing SDM PUSCH where different TBs are mapped to different portions of the SDM PUSCH based on different sets of MIMO layers towards different TRPs (and additionally indicate the association between the SRS resource sets and the sets of MIMO layers). Codepoint 5 may indicate using the second mode of processing SDM PUSCH where different TBs are mapped to different portions of the SDM PUSCH based on different sets of MIMO layers towards different TRPs (and additionally indicate the association between the SRS resource sets and the sets of MIMO layers). Similarly, the codepoints may be used for indicating other modes of processing SDM PUSCH.

In some aspects, the UE1002may determine whether to use the first mode of processing SDM PUSCH, the second mode of processing SDM PUSCH, or other mode(s) of processing SDM PUSCH at1012based on a number of layers in the first set (which may be indicated by the first SRI field or TPMI field in the DCI1008and may be represented by r1) and a number of layers in the second set (which may be indicated by the second SRI field or TPMI field in the DCI1008and may be represented by r2). For example, (r1,r2)=(1,1), (2,1), (1,2), Mode 1 may be used. For (r1,r2)=(2,2), Mode 2 may be used.

In some aspects, if a PUSCH is scheduled with a configured number (such as 4) or smaller number of layers, and the DCI1008includes two sets of MCS/RV/NDI fields, the UE1002may determine whether one CW and one TB is mapped to all MIMO layers, or two CWs and two TBs are mapped to two sets of MIMO layers based on whether the PUSCH is associated with one SRS resource set or one TCI state, or two SRS resource sets or two TCI states. In some aspects, if two to four layers are used for the PUSCH, Mode 2 may be used (and two TB s or two CWs) may be used. There may be two sets of MIMO layers associated with the two SRS resource sets/two beams (and associated TCI states). In some aspects, when all MIMO layers for transmitting the PUSCH are associated with one SRS resource set and one TCI state, the all MIMO layers may be mapped to one TB and one CW. In such aspects, the DCI1008may still include two sets of NDI/RV/MCS fields. In some aspects, whether the PUSCH is associated with one SRS resource set or one TCI state, or two SRS resource sets or two TCI states may be determined based on the SRS resource set indicator in the DCI1008. If the PUSCH is associated with one SRS resource set or one TCI state, the UE1002may ignore a second set of NDI/RV/MCS fields.

In some aspects, the UE1002may use a third mode of processing SDM PUSCH transmission.FIG.11is a diagram1100illustrating example of a third mode of processing SDM PUSCH transmission. As illustrated inFIG.11, to transmit a PUSCH transmission, a single TB1102A may be encoded at1104. After the encoding at1102A, at1105A, rate matching may be performed based on a first RV; scrambling and modulation may also be performed at1105A. Based on the processing at1105A, a CW1106A may be generated (based on the TB1102A and a first RV). At1105B, rate matching may be performed based on a second RV; scrambling and modulation may also be performed at1105B. Based on the processing at1105B, a CW1106B may be generated (based on the TB1102A and a second RV). The CW1106A may be mapped to (at1108) a first set of MIMO layers1110A associated with a first SRI/TPMI (e.g., as indicated by DCI) associated with a first panel of the UE, and then transmitted using a transmit beam associated with the first set of MIMO layers1110A to a first TRP1120A of the base station1120. The CW1106B may be mapped to (at1108) a second set of MIMO layers1110B associated with a second SRI/TPMI (e.g., as indicated by DCI) associated with a second panel of the UE, and then transmitted using a transmit beam associated with the second set of MIMO layers1110B to a second TRP1120B of the base station1120.

In other words, the PUSCH may include one TB, which may be encoded, and then separately rate matched using the first RV and the second RV to create first repetition and second repetition of the TB respectively. The modulated symbols of the first repetition may mapped to first set of MIMO layers (associated with the first SRS resource set/first TCI state/first precoding) and the modulated symbols of the second repetition are mapped to second set of MIMO layers (associated with the second SRS resource set/second TCI state/second precoding). As such, each repetition may be self-decodable as rate matching is separate and performance may be better than the first mode if one of the beams is blocked.

In some aspects, the CW1106A and the CW1106B are associated with a single NDI and MCS and may be respectively associated with a first RV and a second RV. In some aspects, the first RV and the second RV may be indicated by two RV fields in the DCI1008. In some aspects, one RV field in the DCI1008may indicate the first RV and the second RV may be obtained based on a RV offset that may be independent of the DCI1008(such as configured in RRC configuration1007or configured without signaling from the network entity1004).

FIG.12is a diagram1200illustrating example of a fourth mode of processing SDM PUSCH transmission. As illustrated inFIG.12, to transmit a PUSCH transmission, a first portion of the PUSCH transmission may correspond to a first TB1202A, which may be used for generating a CW1206A after encoding, scrambling, and modulation at1204A. The CW1206A may be mapped to (at1208) at least one layer in a first set of MIMO layers1210A associated with a first SRI/TPMI (e.g., as indicated by DCI) associated with a first panel of the UE and at least one layer in a second set of MIMO layers1210B associated with a second SRI/TPMI (e.g., as indicated by DCI) associated with a second panel of the UE. The CW1206A may be then transmitted using a transmit beam associated with the first set of MIMO layers1210A to a first TRP1220A of the base station1220and transmitted using a transmit beam associated with the second set of MIMO layers1210B to a second TRP1220B of the base station1220. A second portion of the PUSCH transmission may correspond to a second TB1202B, which may be used for generating a CW1206B after encoding, scrambling, and modulation at1204B. The CW1206B may be mapped to (at1208) at least one layer in a first set of MIMO layers1210A associated with a first SRI/TPMI (e.g., as indicated by DCI) associated with a first panel of the UE and at least one layer in a second set of MIMO layers1210B associated with a second SRI/TPMI (e.g., as indicated by DCI) associated with a second panel of the UE. The CW1206B may be then transmitted using a transmit beam associated with the first set of MIMO layers1210A to a first TRP1220A of the base station1220and transmitted using a transmit beam associated with the second set of MIMO layers1210B to a second TRP1220B of the base station1220. Such a mode may enhance reliability for each of the two TB s (or at least one of the two TB s) as the layers of the TB are mapped to layers from both beams while the two TB s/CWs may be scheduled with different MCS.

FIG.13is a flowchart1300of a method of wireless communication. The method may be performed by a first network entity (e.g., the UE104, the UE1002; the apparatus1504).

At1302, the first network entity may receive, from a second network entity, DCI scheduling a PUSCH transmission, where the PUSCH transmission includes a first portion associated with a first subset of layers within a set of layers and a second portion associated with a second subset of layers within the set of layers. For example, the UE1002may receive, from a second network entity (e.g.,1004), DCI1008scheduling a PUSCH transmission, where the PUSCH transmission includes a first portion associated with a first subset of layers within a set of layers and a second portion associated with a second subset of layers within the set of layers. In some aspects,1302may be performed by the PUSCH component198. In some aspects, the DCI includes a first indication associated with a first modulation and coding scheme (MCS), a first new data indicator (NDI), or a first redundancy version (RV), where the first indication may be associated with a first TB or a first CW associated with the first subset of layers, where the DCI includes a second indication associated with a second MCS, a second NDI, or a second RV, where the second indication may be associated with a second TB or a second CW associated with the second subset of layers.

At1304, the first network entity may map at least one TB or CW to the first portion or the second portion based on the DCI or an RRC configuration. For example, the UE1002may map (e.g., at1012) at least one TB or CW to the first portion or the second portion based on the DCI or an RRC configuration1007. In some aspects,1304may be performed by the PUSCH component198. In some aspects, to map the at least one TB or CW to the first portion or the second portion based on the DCI or the RRC configuration, the first network entity may map the at least one TB or CW to the first portion or the second portion based on the RRC configuration, and the RRC configuration may be associated with a bandwidth part (BWP) or a serving cell. In some aspects, to map the at least one TB or CW to the first portion or the second portion based on the DCI or the RRC configuration, the first network entity may map the at least one TB or CW to the first portion or the second portion based on the DCI. In some aspects, the DCI includes an SRS resource set indicator, and where the first network entity may map the at least one TB or CW to the first portion or the second portion based on the SRS resource set indicator. In some aspects, the SRS resource set indicator indicates a first SRS resource set associated with the first subset of layers and a second SRS resource set associated with the second subset of layers. In some aspects, to map the at least one TB or CW to the first portion or the second portion based on the DCI or the RRC configuration, the first network entity may map the at least one TB or CW to the first portion or the second portion based on a first number of layers associated with the first subset of layers and a second number of layers associated with the second subset of layers. In some aspects, to map the at least one TB or CW to the first portion or the second portion based on the DCI or the RRC configuration, the first network entity may map the at least one TB or CW to the first portion or the second portion based on a number of SRS resource sets associated with the PUSCH transmission, and where the DCI includes a first indication associated with a first MCS, a first NDI, or a first RV, where the first indication may be associated with a first TB or a first CW associated with the first subset of layers, where the DCI includes a second indication associated with a second MCS, a second NDI, or a second RV, where the second indication may be associated with a second TB or a second CW associated with the second subset of layers. In some aspects, the number of SRS resource sets associated with the PUSCH transmission may be one, and where the DCI further includes a disable indication, where the disable indication may be configured to cause the first network entity to refrain from using the first MCS, the first NDI, or the first RV associated with the first indication or refrain from using the second MCS, the second NDI, or the second RV associated with the second indication. In some aspects, the at least one TB or CW includes one TB, a first CW, and a second CW, and where the first CW may be based on rate matching the one TB using a first RV and the second CW may be based on rate matching the one TB using the second RV. In some aspects, the first RV may be indicated by the DCI, and where the second RV may be indicated by the DCI or configured based on a RV offset relative to the first RV, the RV offset may be independent of the DCI. For example, the RV offset may be independent of DCI based on the DCI not including a field representing the RV offset. The DCI may include a field representing the first RV without a field representing the second RV and without a field representing the RV offset. In some aspects, the RV offset may be configured without base station signaling. In some aspects, the RV offset may be configured based on an RRC configuration, such as the RRC configuration1007or a different RRC configuration.

At1306, the first network entity may transmit the at least one TB or CW to the second network entity. For example, the UE1002may transmit the at least one TB or CW (e.g., the PUSCH transmission1014) to the second network entity (e.g.,1004). In some aspects,1306may be performed by the PUSCH component198. In some aspects, the DCI further includes a disable indication, where the disable indication may be configured to cause the first network entity to refrain from using the second MCS, the second NDI, or the second RV associated with the second indication, and where the at least one TB or CW correspond to the first TB or the first CW based on the disable indication. In some aspects, the at least one TB or CW includes a first TB or a first CW and a second TB or a second CW, and where at least one of the first CW or the second CW may be associated with at least one first layer of the first subset of layers and at least one second layer of the second subset of layers.

FIG.14is a flowchart1400of a method of wireless communication. The method may be performed by a first network entity (e.g., the base station102, the network entity1004, the network entity1502, the network entity1602).

At1402, the first network entity may transmit, to a second network entity, DCI scheduling a PUSCH transmission including a first portion and a second portion, where the PUSCH transmission includes a first portion associated with a first subset of layers within a set of layers and a second portion associated with a second subset of layers within the set of layers. For example, the network entity1004may transmit, to a second network entity (e.g., the UE1002), DCI1008scheduling a PUSCH transmission including a first portion and a second portion, where the PUSCH transmission includes a first portion associated with a first subset of layers within a set of layers and a second portion associated with a second subset of layers within the set of layers. In some aspects,1402may be performed by the PUSCH component199. In some aspects, the DCI includes a first indication associated with a first MCS, a first NDI, or a first RV, where the first indication may be associated with a first TB or a first CW associated with the first subset of layers, where the DCI includes a second indication associated with a second MCS, a second NDI, or a second RV, where the second indication may be associated with a second TB or a second CW associated with the second subset of layers. In some aspects, the DCI further includes a disable indication, where the disable indication indicates refraining from using the second MCS, the second NDI, or the second RV associated with the second indication, and where the at least one TB or CW correspond to the first TB or the first CW based on the disable indication. In some aspects, the DCI includes an SRS resource set indicator, and the at least one TB or CW may be mapped to the first portion or the second portion based on the SRS resource set indicator. In some aspects, the SRS resource set indicator indicates a first SRS resource set associated with the first subset of layers and a second SRS resource set associated with the second subset of layers. In some aspects, the first RV may be indicated by the DCI, and where the second RV may be indicated by the DCI or configured based on a RV offset relative to the first RV, the RV offset may be independent of the DCI. For example, the RV offset may be independent of DCI based on the DCI not including a field representing the RV offset. The DCI may include a field representing the first RV without a field representing the second RV and without a field representing the RV offset. In some aspects, the RV offset may be configured without base station signaling. In some aspects, the RV offset may be configured based on an RRC configuration, such as the RRC configuration1007or a different RRC configuration.

At1404, the first network entity may receive at least one TB or CW from the second network entity, where the at least one TB or CW is mapped to the first portion or the second portion based on the DCI or an RRC configuration. For example, the network entity1004may receive at least one TB or CW (e.g., the PUSCH transmission1014) from the second network entity, where the at least one TB or CW is mapped to the first portion or the second portion based on the DCI or an RRC configuration1007. In some aspects,1404may be performed by the PUSCH component199. In some aspects, the at least one TB or CW may be mapped to the first portion or the second portion based on the RRC configuration, and where the RRC configuration may be associated with a BWP or a serving cell. In some aspects, the at least one TB or CW may be mapped to the first portion or the second portion based on the DCI. In some aspects, the at least one TB or CW may be mapped to the first portion or the second portion based on a first number of layers associated with the first subset of layers and a second number of layers associated with the second subset of layers. In some aspects, the at least one TB or CW may be mapped to the first portion or the second portion based on a number of SRS resource sets associated with the PUSCH transmission, and where the DCI includes a first indication associated with a first MCS, a first NDI, or a first RV, where the first indication may be associated with a first TB or a first CW associated with the first subset of layers, where the DCI includes a second indication associated with a second MCS, a second NDI, or a second RV, where the second indication may be associated with a second TB or a second CW associated with the second subset of layers. In some aspects, the number of SRS resource sets associated with the PUSCH transmission may be one, and where the DCI includes a disable indication indicating refraining from using the first MCS, the first NDI, or the first RV associated with the first indication or refraining from using second MCS, the second NDI, or the second RV associated with the second indication. In some aspects, the at least one TB or CW includes one TB, a first CW, and a second CW, and where the first CW may be based on rate matching the one TB using a first RV and the second CW may be based on rate matching the one TB using the second RV. In some aspects, the at least one TB or CW includes a first TB or a first CW and a second TB or a second CW, and where at least one of the first CW or the second CW may be associated with at least one first layer of the first subset of layers and at least one second layer of the second subset of layers.

FIG.15is a diagram1500illustrating an example of a hardware implementation for an apparatus1504. The apparatus1504may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus1504may include a cellular baseband processor1524(also referred to as a modem) coupled to one or more transceivers1522(e.g., cellular RF transceiver). The cellular baseband processor1524may include on-chip memory1524′. In some aspects, the apparatus1504may further include one or more subscriber identity modules (SIM) cards1520and an application processor1506coupled to a secure digital (SD) card1508and a screen1510. The application processor1506may include on-chip memory1506′. In some aspects, the apparatus1504may further include a Bluetooth module1512, a WLAN module1514, a satellite system module1516(e.g., GNSS module), one or more sensor modules1518(e.g., barometric pressure sensor/altimeter; motion sensor such as inertial management unit (IMU), gyroscope, and/or accelerometer(s); light detection and ranging (LIDAR), radio assisted detection and ranging (RADAR), sound navigation and ranging (SONAR), magnetometer, audio and/or other technologies used for positioning), additional memory modules1526, a power supply1530, and/or a camera1532. The Bluetooth module1512, the WLAN module1514, and the satellite system module1516may include an on-chip transceiver (TRX)/receiver (RX). The cellular baseband processor1524communicates through the transceiver(s)1522via one or more antennas1580with the UE104and/or with an RU associated with a network entity1502. The cellular baseband processor1524and the application processor1506may each include a computer-readable medium/memory1524′,1506′, respectively. The additional memory modules1526may also be considered a computer-readable medium/memory. Each computer-readable medium/memory1524′,1506′,1526may be non-transitory. The cellular baseband processor1524and the application processor1506are each responsible for general processing, including the execution of software stored on the computer-readable medium/memory. The software, when executed by the cellular baseband processor1524/application processor1506, causes the cellular baseband processor1524/application processor1506to perform the various functions described herein. The computer-readable medium/memory may also be used for storing data that is manipulated by the cellular baseband processor1524/application processor1506when executing software. The cellular baseband processor1524/application processor1506may be a component of the UE350and may include the memory360and/or at least one of the TX processor368, the RX processor356, and the controller/processor359. In one configuration, the apparatus1504may be a processor chip (modem and/or application) and include just the cellular baseband processor1524and/or the application processor1506, and in another configuration, the apparatus1504may be the entire UE (e.g., see350ofFIG.3) and include the additional modules of the apparatus1504.

As discussed herein, the PUSCH component198may be configured to receive, from a second network entity, DCI scheduling a PUSCH transmission, where the PUSCH transmission includes a first portion associated with a first subset of layers within a set of layers and a second portion associated with a second subset of layers within the set of layers. In some aspects, the PUSCH component198may be further configured to map at least one TB or CW to the first portion or the second portion based on the DCI or an RRC configuration. In some aspects, the PUSCH component198may be further configured to transmit the at least one TB or CW to the second network entity. The PUSCH component198may be within the cellular baseband processor1524, the application processor1506, or both the cellular baseband processor1524and the application processor1506. The PUSCH component198may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by one or more processors configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by one or more processors, or some combination thereof. As shown, the apparatus1504may include a variety of components configured for various functions. In one configuration, the apparatus1504, and in particular the cellular baseband processor1524and/or the application processor1506, includes means for receiving, from a second network entity, DCI scheduling a PUSCH transmission, where the PUSCH transmission includes a first portion associated with a first subset of layers within a set of layers and a second portion associated with a second subset of layers within the set of layers. In some aspects, the apparatus1504may further include means for mapping at least one TB or CW to the first portion or the second portion based on the DCI or an RRC configuration. In some aspects, the apparatus1504may further include means for transmitting the at least one TB or CW to the second network entity. In some aspects, the means for mapping the at least one TB or CW to the first portion or the second portion based on the DCI or the RRC configuration may include means for mapping the at least one TB or CW to the first portion or the second portion based on a first number of layers associated with the first subset of layers and a second number of layers associated with the second subset of layers. In some aspects, the means for mapping the at least one TB or CW to the first portion or the second portion based on the DCI or the RRC configuration may include means for mapping the at least one TB or CW to the first portion or the second portion based on a number of sounding reference signal (SRS) resource sets associated with the PUSCH transmission. The means may be the PUSCH component198of the apparatus1504configured to perform the functions recited by the means. As described herein, the apparatus1504may include the TX processor368, the RX processor356, and the controller/processor359. As such, in one configuration, the means may be the TX processor368, the RX processor356, and/or the controller/processor359configured to perform the functions recited by the means.

FIG.16is a diagram1600illustrating an example of a hardware implementation for a network entity1602. The network entity1602may be a BS, a component of a BS, or may implement BS functionality. The network entity1602may include at least one of a CU1610, a DU1630, or an RU1640. For example, depending on the layer functionality handled by the component199, the network entity1602may include the CU1610; both the CU1610and the DU1630; each of the CU1610, the DU1630, and the RU1640; the DU1630; both the DU1630and the RU1640; or the RU1640. The CU1610may include a CU processor1612. The CU processor1612may include on-chip memory1612′. In some aspects, the CU1610may further include additional memory modules1614and a communications interface1618. The CU1610communicates with the DU1630through a midhaul link, such as an F1 interface. The DU1630may include a DU processor1632. The DU processor1632may include on-chip memory1632′. In some aspects, the DU1630may further include additional memory modules1634and a communications interface1638. The DU1630communicates with the RU1640through a fronthaul link. The RU1640may include an RU processor1642. The RU processor1642may include on-chip memory1642′. In some aspects, the RU1640may further include additional memory modules1644, one or more transceivers1646, antennas1680, and a communications interface1648. The RU1640communicates with the UE104. The on-chip memory1612′,1632′,1642′ and the additional memory modules1614,1634,1644may each be considered a computer-readable medium/memory. Each computer-readable medium/memory may be non-transitory. Each of the processors1612,1632,1642is responsible for general processing, including the execution of software stored on the computer-readable medium/memory. The software, when executed by the corresponding processor(s) causes the processor(s) to perform the various functions described herein. The computer-readable medium/memory may also be used for storing data that is manipulated by the processor(s) when executing software.

As discussed herein, the PUSCH component199may be configured to transmit, to a second network entity, DCI scheduling a PUSCH transmission including a first portion and a second portion, where the PUSCH transmission includes a first portion associated with a first subset of layers within a set of layers and a second portion associated with a second subset of layers within the set of layers. In some aspects, the PUSCH component199may be further configured to receive at least one TB or CW from the second network entity, where the at least one TB or CW may be mapped to the first portion or the second portion based on the DCI or an RRC configuration. The PUSCH component199may be within one or more processors of one or more of the CU1610, DU1630, and the RU1640. The PUSCH component199may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by one or more processors configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by one or more processors, or some combination thereof. The network entity1602may include a variety of components configured for various functions. In one configuration, the network entity1602includes means for transmitting, to a second network entity, DCI scheduling a PUSCH transmission including a first portion and a second portion, where the PUSCH transmission includes a first portion associated with a first subset of layers within a set of layers and a second portion associated with a second subset of layers within the set of layers. In some aspects, the network entity1602may further include means for receiving at least one TB or CW from the second network entity, where the at least one TB or CW may be mapped to the first portion or the second portion based on the DCI or an RRC configuration. The means may be the PUSCH component199of the network entity1602configured to perform the functions recited by the means. As described herein, the network entity1602may include the TX processor316, the RX processor370, and the controller/processor375. As such, in one configuration, the means may be the TX processor316, the RX processor370, and/or the controller/processor375configured to perform the functions recited by the means.

Aspect 1 is a first network entity for wireless communication, including: a memory; and at least one processor coupled to the memory, where the at least one processor is configured to: receive, from a second network entity, downlink control information (DCI) scheduling a physical uplink shared channel (PUSCH) transmission, where the PUSCH transmission includes a first portion associated with a first subset of layers within a set of layers and a second portion associated with a second subset of layers within the set of layers; map at least one transport block (TB) or codeword (CW) to the first portion or the second portion based on the DCI or a radio resource control (RRC) configuration; and transmit the at least one TB or CW to the second network entity.

Aspect 2 is the first network entity of aspect 1, where to map the at least one TB or CW to the first portion or the second portion based on the DCI or the RRC configuration, the at least one processor is configured to map the at least one TB or CW to the first portion or the second portion based on the RRC configuration, and where the RRC configuration is associated with a bandwidth part (BWP) or a serving cell.

Aspect 3 is the first network entity of any of aspects 1 to 2, where to map the at least one TB or CW to the first portion or the second portion based on the DCI or the RRC configuration, the at least one processor is configured to map the at least one TB or CW to the first portion or the second portion based on the DCI.

Aspect 4 is the first network entity of any of aspects 1 to 3, where the DCI includes a first indication associated with a first modulation and coding scheme (MCS), a first new data indicator (NDI), or a first redundancy version (RV), where the first indication is associated with a first TB or a first CW associated with the first subset of layers, where the DCI includes a second indication associated with a second MCS, a second NDI, or a second RV, where the second indication is associated with a second TB or a second CW associated with the second subset of layers.

Aspect 5 is the first network entity of any of aspects 1-4, where the DCI further includes a disable indication, where the disable indication is configured to cause the at least one processor to refrain from using the second MCS, the second NDI, or the second RV associated with the second indication, and where the at least one TB or CW correspond to the first TB or the first CW based on the disable indication.

Aspect 6 is the first network entity of any of aspects 1-5, where the DCI includes a sounding reference signal (SRS) resource set indicator, and where the at least one processor is configured to map the at least one TB or CW to the first portion or the second portion based on the SRS resource set indicator.

Aspect 7 is the first network entity of any of aspects 1-6, where the SRS resource set indicator indicates a first SRS resource set associated with the first subset of layers and a second SRS resource set associated with the second subset of layers.

Aspect 8 is the first network entity of any of aspects 1-7, where to map the at least one TB or CW to the first portion or the second portion based on the DCI or the RRC configuration, the at least one processor is configured to map the at least one TB or CW to the first portion or the second portion based on a first number of layers associated with the first subset of layers and a second number of layers associated with the second subset of layers.

Aspect 9 is the first network entity of any of aspects 1 to 8, where to map the at least one TB or CW to the first portion or the second portion based on the DCI or the RRC configuration, the at least one processor is configured to map the at least one TB or CW to the first portion or the second portion based on a number of sounding reference signal (SRS) resource sets associated with the PUSCH transmission, and where the DCI includes a first indication associated with a first modulation and coding scheme (MCS), a first new data indicator (NDI), or a first redundancy version (RV), where the first indication is associated with a first TB or a first CW associated with the first subset of layers, where the DCI includes a second indication associated with a second MCS, a second NDI, or a second RV, where the second indication is associated with a second TB or a second CW associated with the second subset of layers.

Aspect 10 is the first network entity of any of aspects 1-9, where the number of SRS resource sets associated with the PUSCH transmission is one, and where the DCI further includes a disable indication, where the disable indication is configured to cause the at least one processor to refrain from using the first MCS, the first NDI, or the first RV associated with the first indication or refrain from using the second MCS, the second NDI, or the second RV associated with the second indication.

Aspect 11 is the first network entity of any of aspects 1 to 10, where the at least one TB or CW includes one TB, a first CW, and a second CW, and where the first CW is based on rate matching the one TB using a first redundancy version (RV) and the second CW is based on rate matching the one TB using the second RV.

Aspect 12 is the first network entity of any of aspects 1 to 11, where the first RV is indicated by the DCI, and where the second RV is indicated by the DCI or configured based on an RV offset relative to the first RV, the RV offset being independent of the DCI.

Aspect 13 is the first network entity of any of aspects 1 to 12, where the at least one TB or CW includes a first TB or a first CW and a second TB or a second CW, and where at least one of the first CW or the second CW is associated with at least one first layer of the first subset of layers and at least one second layer of the second subset of layers.

Aspect 14 is a first network entity for wireless communication, including: a memory; and at least one processor coupled to the memory, where the at least one processor is configured to: transmit, to a second network entity, downlink control information (DCI) scheduling a physical uplink shared channel (PUSCH) transmission, where the PUSCH transmission includes a first portion associated with a first subset of layers within a set of layers and a second portion associated with a second subset of layers within the set of layers; and receive at least one transport block (TB) or codeword (CW) from the second network entity, where the at least one TB or CW is mapped to the first portion or the second portion based on the DCI or a radio resource control (RRC) configuration.

Aspect 15 is the first network entity of aspect 14, where the at least one TB or CW is mapped to the first portion or the second portion based on the RRC configuration, and where the RRC configuration is associated with a bandwidth part (BWP) or a serving cell.

Aspect 16 is the first network entity of any of aspects 14 to 15, where the at least one TB or CW is mapped to the first portion or the second portion based on the DCI.

Aspect 17 is the first network entity of any of aspects 14 to 16, where the DCI includes a first indication associated with a first modulation and coding scheme (MCS), a first new data indicator (NDI), or a first redundancy version (RV), where the first indication is associated with a first TB or a first CW associated with the first subset of layers, where the DCI includes a second indication associated with a second MCS, a second NDI, or a second RV, where the second indication is associated with a second TB or a second CW associated with the second subset of layers.

Aspect 18 is the first network entity of any of aspects 14 to 17, where the DCI further includes a disable indication, where the disable indication indicates refraining from using the second MCS, the second NDI, or the second RV associated with the second indication, and where the at least one TB or CW correspond to the first TB or the first CW based on the disable indication.

Aspect 19 is the first network entity of any of aspects 14 to 18, where the DCI includes a sounding reference signal (SRS) resource set indicator, and the at least one TB or CW is mapped to the first PUSCH transmission or the second PUSCH transmission based on the SRS resource set indicator.

Aspect 20 is the first network entity of any of aspects 14 to 19, where the SRS resource set indicator indicates a first SRS resource set associated with the first subset of layers and a second SRS resource set associated with the second subset of layers.

Aspect 21 is the first network entity of any of aspects 14 to 20, where the at least one TB or CW is mapped to the first portion or the second portion based on a first number of layers associated with the first subset of layers and a second number of layers associated with the second subset of layers.

Aspect 22 is the first network entity of any of aspects 14 to 21, where the at least one TB or CW is mapped to the first portion or the second portion based on a number of sounding reference signal (SRS) resource sets associated with the PUSCH transmission, and where the DCI includes a first indication associated with a first modulation and coding scheme (MCS), a first new data indicator (NDI), or a first redundancy version (RV), where the first indication is associated with a first TB or a first CW associated with the first subset of layers, where the DCI includes a second indication associated with a second MCS, a second NDI, or a second RV, where the second indication is associated with a second TB or a second CW associated with the second subset of layers.

Aspect 23 is the first network entity of any of aspects 14 to 22, where the number of SRS resource sets associated with the PUSCH transmission is one, and where the DCI includes a disable indication indicating refraining from using the first MCS, the first NDI, or the first RV associated with the first indication or refraining from using the second MCS, the second NDI, or the second RV associated with the second indication.

Aspect 24 is the first network entity of any of aspects 14 to 23, where the at least one TB or CW includes one TB, a first CW, and a second CW, and where the first CW is based on rate matching the one TB using a first redundancy version (RV) and the second CW is based on rate matching the one TB using the second RV.

Aspect 25 is the first network entity of any of aspects 14 to 24, where the first RV is indicated by the DCI, and where the second RV is indicated by the DCI or configured based on an RV offset relative to the first RV, the RV offset being independent of the DCI.

Aspect 26 is the first network entity of any of aspects 14 to 25, where the at least one TB or CW includes a first TB or a first CW and a second TB or a second CW, and where at least one of the first CW or the second CW is associated with at least one first layer of the first subset of layers and at least one second layer of the second subset of layers.

Aspect 27 is a method of wireless communication for implementing any of aspects 1 to 13.

Aspect 28 is an apparatus for wireless communication including means for implementing any of aspects 1 to 13.

Aspect 30 is a method of wireless communication for implementing any of aspects 14 to 26.

Aspect 31 is an apparatus for wireless communication including means for implementing any of aspects 14 to 26.