Patent Description:
Document 3GPP TSG RAN WG1 meeting #96b R1-<NUM> relates to discussion of rate matching methods for PDSCH reliability enhancement schemes with multi TRP panel.

Document 3GPP TSG RAN WG1 #<NUM> R1-<NUM> relates to enhancements on multi-TRP/panel transmission.

The invention is defined by a method of wireless communication performed by a user equipment according to claim <NUM>, corresponding method of wireless communication performed by a base station according to claim <NUM> and the apparatuses according to claims <NUM> and <NUM>. Further details are defined by the claims <NUM>-<NUM> and <NUM>-<NUM>.

The terms "eNB", "base station", "NR BS", "gNB", "TRP", "AP", "node B", "5GNB", and "cell" may be used interchangeably herein.

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 repeating a TB using SDM, 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>, 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>, process <NUM> of <FIG>, and/or other processes as described herein.

In some aspects, UE <NUM> may include means for transmitting an indication that the UE <NUM> is capable of transmitting or receiving TB repetitions using SDM, means for receiving, and based at least in part on the indication, at least one DCI message that schedules a TB in a first resource and a repetition of the TB in a second resource, the first resource and the second resource at least partially overlapping in a time domain and a frequency domain, means for communicating the TB and the repetition of the TB using different antenna panels according to the at least one DCI message, 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.

In some aspects, base station <NUM> may include means for receiving an indication that a UE is capable of transmitting or receiving TB repetitions using SDM, means for transmitting, and based at least in part on receiving the indication, at least one DCI message that schedules a TB in a first resource and a repetition of the TB in a second resource, the first resource and the second resource at least partially overlapping in a time domain and a frequency domain, means for communicating the TB and the repetition of the TB according to the at least one DCI message, and/or the like. In some aspects, such means may include one or more components of base station <NUM> described in connection with <FIG>, such as antenna <NUM>, DEMOD <NUM>, MIMO detector <NUM>, receive processor <NUM>, controller/processor <NUM>, transmit processor <NUM>, TX MIMO processor <NUM>, MOD <NUM>, antenna <NUM>, and/or the like.

<FIG> is a diagram illustrating an example logical architecture of a distributed RAN <NUM>, according to aspects of the present disclosure.

A <NUM> access node <NUM> may include an access node controller <NUM>. The access node controller <NUM> may be a central unit (CU) of the distributed RAN <NUM>. In some aspects, a backhaul interface to a <NUM> core network <NUM> may terminate at the access node controller <NUM>. The <NUM> core network <NUM> may include a <NUM> control plane component <NUM> and a <NUM> user plane component <NUM> (e.g., a <NUM> gateway), and the backhaul interface for one or both of the <NUM> control plane and the <NUM> user plane may terminate at the access node controller <NUM>. Additionally, or alternatively, a backhaul interface to one or more neighbor access nodes <NUM> (e.g., another <NUM> access node <NUM>, an LTE access node, and/or the like) may terminate at the access node controller <NUM>.

The access node controller <NUM> may include and/or may communicate with one or more TRPs <NUM> (e.g., via an F1 Control (F1-C) interface and/or an F1 User (F1-U) interface). A TRP <NUM> may be a distributed unit (DU) of the distributed RAN <NUM>. In some aspects, a TRP <NUM> may correspond to a base station <NUM> described above in connection with <FIG>. For example, different TRPs <NUM> may be included in different base stations <NUM>. Additionally, or alternatively, multiple TRPs <NUM> may be included in a single base station <NUM>. In some aspects, a base station <NUM> may include a CU (e.g., access node controller <NUM>) and/or one or more DUs (e.g., one or more TRPs <NUM>). In some cases, a TRP <NUM> may be referred to as a cell, a panel, an antenna array, an array, and/or the like.

A TRP <NUM> may be connected to a single access node controller <NUM> or to multiple access node controllers <NUM>. In some aspects, a dynamic configuration of split logical functions may be present within the architecture of distributed RAN <NUM>. For example, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, a medium access control (MAC) layer, and/or the like may be configured to terminate at the access node controller <NUM> or at a TRP <NUM>.

In some aspects, multiple TRPs <NUM> may transmit communications (e.g., the same communication or different communications) in the same transmission time interval (TTI) (e.g., a slot, a mini-slot, a subframe, a symbol, and/or the like) or different TTIs using different quasi-co-location (QCL) relationships (e.g., different spatial parameters, different transmission configuration indicator (TCI) states, different precoding parameters, different beamforming parameters, and/or the like). In some aspects, a TCI state may be used to indicate one or more QCL relationships. A TRP <NUM> may be configured to individually (e.g., using dynamic selection) or jointly (e.g., using joint transmission with one or more other TRPs <NUM>) serve traffic to a UE <NUM>.

Other examples may differ from what was described with regard to <FIG>.

<FIG> is a diagram illustrating an example <NUM> of multi-TRP communication (sometimes referred to as multi-panel communication), in accordance with various aspects of the present disclosure. As shown in <FIG>, multiple TRPs <NUM> may communicate with the same UE <NUM>. A TRP <NUM> may correspond to a TRP <NUM> described above in connection with <FIG>.

The multiple TRPs <NUM> (shown as TRP A and TRP B) may communicate with the same UE <NUM> in a coordinated manner (e.g., using coordinated multipoint transmissions and/or the like) to improve reliability, increase throughput, and/or the like. The TRPs <NUM> may coordinate such communications via an interface between the TRPs <NUM> (e.g., a backhaul interface, an access node controller <NUM>, and/or the like). The interface may have a smaller delay and/or higher capacity when the TRPs <NUM> are co-located at the same base station <NUM> (e.g., when the TRPs <NUM> are different antenna arrays or panels of the same base station <NUM>), and may have a larger delay and/or lower capacity (as compared to co-location) when the TRPs <NUM> are located at different base stations <NUM>. The different TRPs <NUM> may communicate with the UE <NUM> using different QCL relationships (e.g., different TCI states), different demodulation reference signal (DMRS) ports, different layers (e.g., of a multi-layer communication), and/or the like.

In a first multi-TRP transmission mode (e.g., Mode <NUM>), a single physical downlink control channel (PDCCH) may be used to schedule downlink data communications for a single physical downlink shared channel (PDSCH). In this case, multiple TRPs <NUM> (e.g., TRP A and TRP B) may transmit communications to the UE <NUM> on the same PDSCH. For example, a communication may be transmitted using a single codeword with different spatial layers for different TRPs <NUM> (e.g., where one codeword maps to a first set of layers transmitted by a first TRP <NUM> and maps to a second set of layers transmitted by a second TRP <NUM>). As another example, a communication may be transmitted using multiple codewords, where different codewords are transmitted by different TRPs <NUM> (e.g., using different sets of layers). In either case, different TRPs <NUM> may use different QCL relationships (e.g., different TCI states) for different DMRS ports corresponding to different layers. For example, a first TRP <NUM> may use a first QCL relationship or a first TCI state for a first set of DMRS ports corresponding to a first set of layers, and a second TRP <NUM> may use a second (different) QCL relationship or a second (different) TCI state for a second (different) set of DMRS ports corresponding to a second (different) set of layers. In some aspects, a TCI state in downlink control information (DCI) (e.g., transmitted on the PDCCH, such as DCI format 1_0, DCI format 1_1, and/or the like) may indicate the first QCL relationship (e.g., by indicating a first TCI state) and the second QCL relationship (e.g., by indicating a second TCI state). The first and the second TCI states may be indicated using a TCI field in the DCI. In general, the TCI field can indicate a single TCI state (for single-TRP transmission) or multiple TCI states (for multi-TRP transmission as discussed here) in this multi-TRP transmission mode (e.g., Mode <NUM>).

In a second multi-TRP transmission mode (e.g., Mode <NUM>), multiple PDCCHs may be used to schedule downlink data communications for multiple corresponding PDSCHs (e.g., one PDCCH for each PDSCH). In this case, a first PDCCH may schedule a first codeword to be transmitted by a first TRP <NUM>, and a second PDCCH may schedule a second codeword to be transmitted by a second TRP <NUM>. Furthermore, first DCI (e.g., transmitted by the first TRP <NUM>) may schedule a first PDSCH communication associated with a first set of DMRS ports with a first QCL relationship (e.g., indicated by a first TCI state) for the first TRP <NUM>, and second DCI (e.g., transmitted by the second TRP <NUM>) may schedule a second PDSCH communication associated with a second set of DMRS ports with a second QCL relationship (e.g., indicated by a second TCI state) for the second TRP <NUM>. In this case, DCI (e.g., having DCI format 1_0, DCI format 1_1, and/or the like) may indicate a corresponding TCI state for a TRP <NUM> corresponding to the DCI. The TCI field of a DCI indicates the corresponding TCI state (e.g., the TCI field of the first DCI indicates the first TCI state and the TCI field of the second DCI indicates the second TCI state).

A UE may use a plurality of antenna panels to perform concurrent (e.g., simultaneous) uplink transmissions or receive concurrent (e.g., simultaneous) downlink transmissions. The use of a plurality of antenna panels for concurrent transmissions may be referred to as a non-coherent joint transmission or spatial division multiplexing (SDM). In some wireless networks, TB repetition may be used to improve performance of transmissions, reliability of transmissions, and/or the like. However, wireless networks generally lack support for techniques to signal, configure, indicate, schedule, or otherwise enable TB repetition using SDM.

Accordingly, some techniques and apparatuses described herein provide a framework for TB repetition using SDM. For example, as described herein, a UE may transmit a capability report to a base station indicating that the UE supports transmitting or receiving TB repetitions using SDM, and the base station may provide the UE with a high-level configuration to enable TB repetitions using SDM (e.g., via radio resource control (RRC) signaling). Accordingly, the base station may then transmit, to the UE, a single DCI message, or a plurality of DCI messages, that schedule TB repetitions in resources that at least partially overlap in a time domain and a frequency domain, and the UE may communicate (e.g., transmit or receive) the TB repetitions according to the DCI message(s).

<FIG> are diagrams illustrating one or more examples <NUM> of repeating a TB using SDM, in accordance with various aspects of the present disclosure. As shown in <FIG>, a base station <NUM> and a UE <NUM> may communicate with one another. In some aspects, the UE <NUM> may employ a plurality of transmit antenna panels (e.g., a plurality of physical uplink shared channel (PUSCH) antenna port groups) and/or a plurality of receive antenna panels (e.g., a plurality of PDSCH antenna port groups). In some aspects, the UE <NUM> may communicate with a plurality of TRPs (e.g., a plurality of antenna panels) associated with the base station <NUM>. In some aspects, the plurality of TRPs may be associated with more than one base station.

As shown in <FIG>, and by reference number <NUM>, the UE <NUM> may transmit, and the BS <NUM> may receive, an indication that the UE <NUM> is capable of transmitting and/or receiving TB repetitions using SDM. For example, the UE <NUM> may transmit a UE capability report indicating that the UE <NUM> is capable of transmitting and/or receiving TB repetitions using SDM.

In some aspects, the indication may indicate that the UE is capable of using SDM to transmit and/or receive TB repetitions scheduled by a single DCI message. That is, the indication may indicate that the UE is capable of using SDM to transmit TB repetitions using two uplink codewords (e.g., the UE may report capability for TBrepetitionby2ULCW) and/or to receive TB repetitions using two downlink codewords (e.g., the UE may report capability for TBrepetitionby2DLCW).

In some aspects, the indication may indicate that the UE is capable of using SDM to transmit and/or receive TB repetitions scheduled by a plurality of DCI messages (e.g., two DCI messages). For example, the indication may indicate that the UE is capable of using SDM to transmit TB repetitions scheduled by two uplink DCI messages (e.g., the UE may report capability for SDMby2ULDCI) and/or to receive TB repetitions scheduled by two downlink DCI messages (e.g., the UE may report capability for SDMby2DLDCI).

As shown by reference number <NUM>, the base station <NUM> may transmit (e.g., via RRC signaling), and the UE <NUM> may receive, a configuration that enables, for the UE <NUM>, TB repetitions that use SDM. For example, the base station <NUM> may transmit the configuration based at least in part on the UE <NUM> indicating a capability for TB repetitions that use SDM.

In some aspects, the configuration may enable TB repetitions, using SDM, scheduled by a single DCI message. For example, the configuration may set a first RRC signaling (flag <NUM>) to a first value (e.g., <NUM>) to enable TB repetitions scheduled by a single DCI message. Similarly, the base station <NUM> may transmit another configuration to the UE <NUM> that disables TB repetitions, using SDM, scheduled by a single DCI message. For example, the configuration may set the first RRC signaling to a second value (e.g., <NUM>) to disable TB repetitions scheduled by a single DCI message.

In some aspects, the configuration may enable TB repetitions, using SDM, scheduled by a plurality of DCI messages (e.g., two DCI messages). For example, the configuration may set a second RRC signaling (flag2) to a first value (e.g., <NUM>) to enable TB repetitions scheduled by a plurality of DCI messages. Similarly, the base station <NUM> may transmit another configuration to the UE <NUM> that disables TB repetitions, using SDM, scheduled by a plurality of DCI messages (e.g., two DCI messages). For example, the configuration may set the second RRC signaling to a second value (e.g., <NUM>) to disable TB repetitions scheduled by a plurality of DCI messages.

As shown in <FIG>, and by reference number 515a, in some aspects, the base station <NUM> may transmit, and the UE <NUM> may receive, a single DCI message that schedules a TB (e.g., an initial repetition of the TB) and at least one repetition of the TB. The single DCI message may indicate a single resource allocation for the TB and the repetition of the TB. That is, a first resource that is to be used for the TB, and a second resource that is to be used for the repetition of the TB, may overlap in a time domain and a frequency domain (e.g., the first resource and the second resource may be the same).

The base station <NUM> may transmit the single DCI message based at least in part on the UE <NUM> indicating that the UE is capable of using SDM to transmit and/or receive TB repetitions scheduled by a single DCI message. Moreover, the base station <NUM> may transmit the single DCI message after enabling, for the UE <NUM>, TB repetitions scheduled by a single DCI message.

In some aspects, the base station <NUM> may transmit a message indicating that a maximum number of codewords scheduled by the single DCI message is more than one (e.g., two codewords). For example, an RRC message may indicate (e.g., using a maxNrofULCodeWordsScheduledByDCI parameter) that a maximum number of uplink codewords scheduled by the DCI message is two uplink codewords. As another example, an RRC message may indicate (e.g., using a maxNrofDLCodeWordsScheduledByDCI parameter) that a maximum number of downlink codewords scheduled by the DCI message is two downlink codewords.

In some aspects, the single DCI message may schedule transmission of at least a first codeword and a second codeword. For example, a single uplink DCI message may schedule a first uplink codeword and a second uplink codeword, and the second uplink codeword may be a repetition of the first uplink codeword. As another example, a single downlink DCI message may schedule a first downlink codeword and a second downlink codeword, and the second downlink codeword may be a repetition of the first downlink codeword.

In some aspects, the single DCI message may indicate first parameters (e.g., a first new data indicator (NDI) value, a first MCS, a first redundancy version (RV), and/or the like) for the first codeword, and second parameters (e.g., a second NDI value, a second MCS, a second RV, and/or the like) for the second codeword. In addition, the single DCI message may indicate a first beam indication for the first codeword and a second beam indication for the second codeword. For example, the single DCI message may indicate respective transmission configuration indicator (TCI) states, respective sounding reference signal (SRS) resource indicators (SRIs), respective SRS resource set indicators, and/or the like, for the beam indications for the first codeword and the second codeword.

Moreover, a demodulation reference signal (DMRS) antenna port indication of the single DCI message may be used for the first codeword and the second codeword. For example, the DMRS antenna port indication may be associated with two or more DMRS code division multiplexing (CDM) groups (e.g., when the single DCI message schedules more than one codeword). In this case, a first DMRS CDM group may be associated with the first codeword, and the remaining DMRS CDM groups (e.g., a second DMRS CDM group, and so forth) may be associated with the second codeword.

In some aspects, the single DCI message may support an association of the TB and the repetition of the TB. For example, the first codeword may be used for the TB and the second codeword may be used for the repetition of the TB. In some aspects, a TB size associated with the TB and the repetition of the TB is the same (e.g., TB sizes are not determined independently for the TB and the repetition of the TB). In this case, a TB size for the transmission of the first codeword and the second codeword may be based at least in part on the first codeword (e.g., a TB size for the second codeword is the same as the first codeword).

Accordingly, the single DCI message may schedule a first PUSCH or PDSCH transmission (shown as PUSCH/PDSCH <NUM>) and a second PUSCH or PDSCH transmission (shown as PUSCH/PDSCH <NUM>). The first PUSCH/PDSCH transmission may be associated with the first codeword and may be scheduled for transmission or reception using a first antenna panel of the UE <NUM> and a first beam. The second PUSCH/PDSCH transmission may be associated with the second codeword and may be scheduled for transmission or reception using a second antenna panel of the UE <NUM> and a second beam.

In some aspects, the single DCI message may provide an indication (e.g., a dynamic indication) that the single DCI message schedules TB repetitions that use SDM (rather than schedules different TBs that use SDM). For example, a reserved value for one or more fields in the single DCI message may indicate that the single DCI message schedules TB repetitions that use SDM. As an example, the single DCI message may toggle (e.g., set) an NDI associated with the second codeword (e.g., to indicate new data), and identify an MCS for the second codeword that indicates a retransmission (e.g., the MCS is associated with a modulation order indication but not a coding rate indication, such as MCS <NUM>, <NUM>, <NUM>, or <NUM> identified in 3GPP Technical Specification <NUM>, table <NUM>. <NUM>-<NUM>). In other words, the UE <NUM> may determine that the single DCI message indicates the scheduling of TB repetitions using SDM based at least in part on a determination that the DCI indicates an invalid combination of an NDI value and an MCS for the second codeword (e.g., the combination indicates new data and a retransmission).

In some aspects, a radio network temporary identifier (RNTI) associated with the single DCI message may provide an indication (e.g., a dynamic indication) that the single DCI message schedules TB repetitions that use SDM (rather than schedules different TBs that use SDM). For example, a RNTI may be defined for use with DCI associated with a maximum number of uplink or downlink codewords that is more than one codeword (e.g., two codewords). Accordingly, the UE <NUM> may determine that the single DCI message schedules TB repetitions that use SDM based at least in part on descrambling the DCI using the RNTI.

As shown in <FIG>, and by reference number 515b, in some aspects, the base station <NUM> may transmit, and the UE <NUM> may receive, a plurality of DCI messages (e.g., two DCI messages) that schedule a TB (e.g., an initial repetition of the TB) and at least one repetition of the TB. The plurality of DCI messages may indicate respective resource allocations for the TB and the repetition of the TB. That is, a first resource that is to be used for the TB, and a second resource that is to be used for the repetition of the TB, may at least partially overlap (e.g., partially overlap or fully overlap) in a time domain and a frequency domain.

The base station <NUM> may transmit the plurality of DCI messages based at least in part on the UE <NUM> indicating that the UE is capable of using SDM to transmit and/or receive TB repetitions scheduled by a plurality of DCI messages. Moreover, the base station <NUM> may transmit the plurality of DCI messages after enabling, for the UE <NUM>, TB repetitions scheduled by a plurality of DCI message.

In some aspects, prior to receiving the plurality of DCI messages, the UE <NUM> may receive, from the base station <NUM>, a control resource set (CORESET) configuration (e.g., a configuration for a ControlResourceSet parameter) that includes at least two different CORESET pool index (e.g., CORESETPoolIndex) values. The configuration may be a PDCCH configuration (e.g., a configuration for the higher-layer parameter PDCCH-Config).

In some aspects, the plurality of DCI messages may include a first DCI message and a second DCI message. The first DCI message may be associated with a first CORESET associated with a first CORESET pool index value (e.g., <NUM>). That is, the UE <NUM> may receive the first DCI message in the first CORESET associated with the first CORESET pool index value. The second DCI message may be associated with a second CORESET associated with a second CORESET pool index value (e.g., <NUM>). That is, the UE <NUM> may receive the second DCI message in the second CORESET associated with the second CORESET pool index value.

In some aspects, the first DCI message may schedule transmission of a first codeword and the second DCI message schedule transmission of a second codeword. For example, a first uplink DCI message may schedule a first uplink codeword, a second uplink DCI message may schedule a second uplink codeword, and the second uplink codeword may be a repetition of the first uplink codeword. As another example, a first downlink DCI message may schedule a first downlink codeword, a second downlink DCI message may schedule a second downlink codeword, and the second downlink codeword may be a repetition of the first downlink codeword.

In some aspects, the first and second DCI messages may support an association of the TB and the repetition of the TB. For example, the first codeword scheduled by the first DCI message may be used for the TB and the second codeword scheduled by the second DCI message may be used for the repetition of the TB. In some aspects, the first and second DCI messages may indicate one or more of the same parameters (e.g., the same hybrid automatic repeat request (HARQ) process identifier, the same TB size, the same NDI value, and/or the like) for the first codeword (e.g., for the TB) and the second codeword (e.g., for the repetition of the TB). In some aspects, the first and second DCI messages may indicate respective beam indications for the first codeword (e.g., for the TB) and the second codeword (e.g., for the repetition of the TB). For example, the first DCI message may indicate a first TCI state, SRI, SRS resource set indicator, and/or the like, for the first codeword, and the second DCI message may indicate a second TCI state, SRI, SRS resource set indicator, and/or the like, for the second codeword.

Accordingly, the plurality of DCI messages may schedule a first PUSCH or PDSCH transmission (shown as PUSCH/PDSCH <NUM>) and a second PUSCH or PDSCH transmission (shown as PUSCH/PDSCH <NUM>). The first PUSCH/PDSCH transmission may be associated with the first codeword scheduled by the first DCI message, and may be scheduled for transmission or reception using a first antenna panel of the UE <NUM> and a first beam. The second PUSCH/PDSCH transmission may be associated with the second codeword scheduled by the second DCI message, and may be scheduled for transmission or reception using a second antenna panel of the UE <NUM> and a second beam.

As shown in <FIG>, and by reference number <NUM>, the base station <NUM> and the UE <NUM> may communicate according to the single DCI message or the plurality of DCI messages. The base station <NUM> and the UE <NUM> may both communicate using a plurality of antenna panels.

In some aspects, the base station <NUM> may transmit, and the UE <NUM> may receive, downlink TB repetitions according to the single DCI message or the plurality of DCI messages. In this case, the UE <NUM> may receive the downlink TB repetitions using a plurality of antenna panels. For example, the UE <NUM> may receive the TB (e.g., an initial repetition of the TB) using a first antenna panel and a first beam, and receive the repetition of the TB using a second antenna panel and a second beam. In some aspects, the UE <NUM> may receive the TB from a first TRP (e.g., associated with the base station <NUM>) and receive the repetition of the TB from a second TRP (e.g., associated with the base station <NUM> or another base station).

In some aspects, the UE <NUM> may transmit, and the base station <NUM> may receive, uplink TB repetitions according to the single DCI message or the plurality of DCI messages. In this case, the UE <NUM> may transmit the uplink TB repetitions using a plurality of antenna panels. For example, the UE <NUM> may transmit the TB (e.g., an initial repetition of the TB) using a first antenna panel and a first beam, and transmit the repetition of the TB using a second antenna panel and a second beam. In some aspects, the UE <NUM> may transmit the TB to a first TRP (e.g., associated with the base station <NUM>) and transmit the repetition of the TB to a second TRP (e.g., associated with the base station <NUM> or another base station).

<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., UE <NUM> and/or the like) performs operations associated with repeating a TB using SDM.

As shown in <FIG>, in some aspects, process <NUM> may include transmitting an indication that the UE is capable of transmitting or receiving TB repetitions using SDM (block <NUM>). For example, the UE (e.g., using controller/processor <NUM>, transmit processor <NUM>, TX MIMO processor <NUM>, MOD <NUM>, antenna <NUM>, and/or the like) may transmit an indication that the UE is capable of transmitting or receiving TB repetitions using SDM, as described above.

As further shown in <FIG>, in some aspects, process <NUM> may include receiving, based at least in part on the indication, at least one DCI message that schedules a TB in a first resource and a repetition of the TB in a second resource, the first resource and the second resource at least partially overlapping in a time domain and a frequency domain (block <NUM>). For example, the UE (e.g., using antenna <NUM>, DEMOD <NUM>, MIMO detector <NUM>, receive processor <NUM>, controller/processor <NUM>, and/or the like) may receive, based at least in part on the indication, at least one DCI message that schedules a TB in a first resource and a repetition of the TB in a second resource, the first resource and the second resource at least partially overlapping in a time domain and a frequency domain, as described above.

As further shown in <FIG>, in some aspects, process <NUM> may include communicating the TB and the repetition of the TB using different antenna panels according to the at least one DCI message (block <NUM>). For example, the UE (e.g., using 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) may communicate the TB and the repetition of the TB using different antenna panels according to the at least one DCI message, as described above.

In a first aspect, the indication indicates that the UE is capable of transmitting or receiving TB repetitions in a plurality of codewords scheduled by a single DCI message.

In a second aspect, alone or in combination with the first aspect, the at least one DCI message is a single DCI message that schedules a transmission of a first codeword and a second codeword.

In a third aspect, alone or in combination with one or more of the first and second aspects, the second codeword is a repetition of the first codeword.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, the first codeword is to be used for the TB and the second codeword is to be used for the repetition of the TB.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, a TB size associated with the transmission is based at least in part on the first codeword.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, process <NUM> includes receiving a configuration that enables TB repetitions using SDM scheduled by a single DCI message.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the at least one DCI message indicates that TB repetitions using SDM are scheduled by the at least one DCI message.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, an RNTI associated with the at least one DCI message indicates that TB repetitions using SDM are scheduled by the at least one DCI message.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the indication indicates that the UE is capable of transmitting or receiving TB repetitions scheduled by a plurality of DCI messages.

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the at least one DCI message includes a first DCI message and a second DCI message, and the first DCI message is associated with a first CORESET associated with a first CORESET pool index, and the second DCI message is associated with a second CORESET associated with a second CORESET pool index.

In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, the at least one DCI message includes a first DCI message and a second DCI message, and the first DCI message schedules a transmission of a first codeword and the second DCI message schedules a transmission of a second codeword.

In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, the second codeword is a repetition of the first codeword.

In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, the at least one DCI message includes a first DCI message and a second DCI message, and the first DCI message and the second DCI message identify a same HARQ process identifier, a same TB size, a same NDI value, and different beam indications.

In a fourteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, process <NUM> includes receiving a configuration that enables TB repetitions using SDM scheduled by a plurality of DCI messages.

<FIG> is a diagram illustrating an example process <NUM> performed, for example, by a base station, in accordance with various aspects of the present disclosure. Example process <NUM> is an example where the base station (e.g., base station <NUM> and/or the like) performs operations associated with repeating a TB using SDM.

As shown in <FIG>, in some aspects, process <NUM> may include receiving an indication that a UE is capable of transmitting or receiving TB repetitions using SDM (block <NUM>). For example, the base station (e.g., using antenna <NUM>, DEMOD <NUM>, MIMO detector <NUM>, receive processor <NUM>, controller/processor <NUM>, and/or the like) may receive an indication that a UE is capable of transmitting or receiving TB repetitions using SDM, as described above.

As further shown in <FIG>, in some aspects, process <NUM> may include transmitting, based at least in part on the indication, at least one DCI message that schedules a TB in a first resource and a repetition of the TB in a second resource, the first resource and the second resource at least partially overlapping in a time domain and a frequency domain (block <NUM>). For example, the base station (e.g., using controller/processor <NUM>, transmit processor <NUM>, TX MIMO processor <NUM>, MOD <NUM>, antenna <NUM>, and/or the like) may transmit, based at least in part on the indication, at least one DCI message that schedules a TB in a first resource and a repetition of the TB in a second resource, the first resource and the second resource at least partially overlapping in a time domain and a frequency domain, as described above.

As further shown in <FIG>, in some aspects, process <NUM> may include communicating the TB and the repetition of the TB according to the at least one DCI message (block <NUM>). For example, the base station (e.g., using 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) may communicate the TB and the repetition of the TB according to the at least one DCI message, as described above.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, process <NUM> includes transmitting a configuration that enables TB repetitions using SDM scheduled by a single DCI message.

In a fourteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, process <NUM> includes transmitting a configuration that enables TB repetitions using SDM scheduled by a plurality of DCI messages.

<FIG> is a conceptual data flow diagram <NUM> illustrating the data flow between different components in an example apparatus <NUM>. The apparatus <NUM> may be a UE (e.g., UE <NUM>). In some aspects, the apparatus <NUM> includes a transmission component <NUM> and/or a reception component <NUM>.

In some aspects, transmission component <NUM> may transmit an indication that the apparatus <NUM> is capable of transmitting or receiving TB repetitions using SDM. For example, transmission component <NUM> may transmit the indication to an apparatus <NUM> (e.g., base station <NUM>).

In some aspects, reception component <NUM> may receive at least one DCI message that schedules a TB in a first resource and a repetition of the TB in a second resource. For example, reception component <NUM> may receive the at least one DCI from the apparatus <NUM>. The first resource and the second resource may at least partially overlap in a time domain and a frequency domain. Reception component <NUM> may receive the at least one DCI message based at least in part on transmission component <NUM> transmitting the indication.

In some aspects, transmission component <NUM> and/or reception component <NUM> may communicate the TB and the repetition of the TB according to the at least one DCI message. For example, transmission component <NUM> and/or reception component <NUM> may communicate with the apparatus <NUM>. In some aspects, transmission component <NUM> may transmit the TB and the repetition of the TB. In some aspects, reception component <NUM> may receive the TB and the repetition of the TB.

The apparatus <NUM> may include additional components that perform each of the blocks of the algorithm in the aforementioned process <NUM> of <FIG>, and/or the like. Each block in the aforementioned process <NUM> of <FIG>, and/or the like may be performed by a component and the apparatus <NUM> may include one or more of those components.

<FIG> is a conceptual data flow diagram <NUM> illustrating the data flow between different components in an example apparatus <NUM>. The apparatus <NUM> may be a base station (e.g., base station <NUM>). In some aspects, the apparatus <NUM> includes a reception component <NUM> and/or a transmission component <NUM>.

In some aspects, reception component <NUM> may receive an indication that an apparatus <NUM> (e.g., UE <NUM>) is capable of transmitting or receiving TB repetitions using SDM. For example, reception component <NUM> may receive the indication from the apparatus <NUM>.

In some aspects, transmission component <NUM> may transmit at least one DCI message that schedules a TB in a first resource and a repetition of the TB in a second resource. For example, transmission component <NUM> may transmit the at least one DCI to the apparatus <NUM>. The first resource and the second resource may at least partially overlap in a time domain and a frequency domain. Transmission component <NUM> may transmit the at least one DCI message based at least in part on reception component <NUM> receiving the indication.

In some aspects, reception component <NUM> and/or transmission component <NUM> may communicate the TB and the repetition of the TB according to the at least one DCI message. For example, reception component <NUM> and/or transmission component <NUM> may communicate with the apparatus <NUM>. In some aspects, reception component <NUM> may receive the TB and the repetition of the TB. In some aspects, transmission component <NUM> may transmit the TB and the repetition of the TB.

Claim 1:
A method of wireless communication performed by a user equipment, UE (<NUM>), comprising:
transmitting (<NUM>), to a base station (<NUM>), an indication that the UE (<NUM>) is capable of transmitting or receiving transport block, TB, repetitions using spatial division multiplexing, SDM;
receiving (<NUM>), from the base station (<NUM>) and based at least in part on the indication, at least one downlink control information, DCI, message that schedules a TB in a first resource and a repetition of the TB in a second resource, the first resource and the second resource at least partially overlapping in a time domain and a frequency domain; and
communicating (<NUM>) the TB and the repetition of the TB using different antenna panels according to the at least one DCI message.