Capability signaling for physical uplink shared channel repetition
The techniques described herein may provide for sub-slot based physical uplink shared channel (PUSCH) repetition (i.e., back-to-back PUSCH repetition within a slot) according to user equipment (UE) capability. A UE may employ uplink data repetition capability reporting for base station scheduling of uplink data repetition and base station management of the number of transport blocks (TBs) that a UE supports (e.g., processes and transmits for uplink) on a per-slot basis. According to the techniques described herein, a UE may indicate whether it supports mini-slot repetition (e.g., for ultra-reliable low-latency communication (URLLC), enhanced mobile broadband (eMBB), or both) via an uplink data repetition capability report. The uplink data repetition capability report may further indicate a maximum number of supported repetitions per TB, a number of supported TBs per slot, etc., such that a base station may configure or schedule PUSCH repetition based on the UE's reported capability.
1. A user equipment (UE) for wireless communication, comprising:
one or more memories storing processor-executable code; and
one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the UE to:
transmit, to a network entity, an uplink data repetition capability report comprising an indication of whether the UE supports sub-slot physical uplink shared channel (PUSCH) repetition and a quantity of PUSCH transmissions supported per slot by the UE, wherein the uplink data repetition capability report indicates different PUSCH repetition capabilities associated with different processing time capabilities of the UE for different service types and indicates a maximum quantity of PUSCH transmissions supported per slot for all transport blocks (TBs) permitted in a slot, wherein each PUSCH repetition is counted as one PUSCH transmission of the maximum quantity of PUSCH transmissions;
receive signaling comprising an uplink grant configuring one or more PUSCH repetitions within a slot based at least in part on the uplink data repetition capability report; and
transmit, based at least in part on the uplink grant, the one or more configured PUSCH repetitions within the slot.
2. The UE of claim 1 , wherein the uplink data repetition capability report comprises an indication that PUSCH repetition is supported in a first band at a sub-slot level and is not supported in a second band at the sub-slot level.
3. The UE of claim 1 , wherein the uplink data repetition capability report indicates PUSCH repetition capabilities for each band of a configured band combination.
4. The UE of claim 1 , wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:
determine the uplink data repetition capability report based on a determination that multiple PUSCH transmissions per repetition are supported by the UE.
5. The UE of claim 1 , wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:
determine, based at least on a gap requirement between non-repeated PUSCH transmissions, the uplink data repetition capability report, wherein the uplink data repetition capability report comprises an indication of a defined gap.
6. The UE of claim 5 , wherein the defined gap is based at least in part on a configured subcarrier spacing, one or more processing time capabilities of the UE, or a combination thereof.
7. The UE of claim 1 , wherein the quantity of PUSCH transmissions supported per slot by the UE is based at least in part on a quantity of PUSCH repetitions supported per transport block by the UE and a quantity of transport blocks supported per slot by the UE.
8. The UE of claim 1 , wherein, to receive the signaling comprising the uplink grant, the one or more processors are individually or collectively operable to execute the code to cause the UE to:
receive the signaling comprising the uplink grant and a time domain resource assignment for transmission of the one or more configured PUSCH repetitions based at least in part on the uplink data repetition capability report,
wherein the time domain resource assignment includes a start and length indicator value (SLIV) indicating a starting symbol and a transmission duration for the one or more configured PUSCH repetitions.
9. The UE of claim 8 , wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:
identify directions for a plurality of symbols spanning the transmission duration; and
determine, based at least in part on the starting symbol and the identified directions for the plurality of symbols, a subset of the plurality of symbols for scheduling the one or more configured PUSCH repetitions.
10. The UE of claim 1 , wherein the uplink data repetition capability report further comprises indications of:
a maximum length of each data repetition supported by the UE, and a maximum quantity of repetitions supported by the UE.
11. The UE of claim 10 , wherein, based at least in part on the uplink data repetition capability report, the uplink grant includes a starting symbol index, a length of each data repetition, and a number of data repetitions permitted during uplink transmission.
12. The UE of claim 1 , wherein the uplink data repetition capability report indicates different PUSCH repetition capabilities associated with PUSCH repetitions configuration for each of a first band and a second band of a configured band combination.
13. A method for wireless communications at a user equipment (UE), comprising:
transmitting, to a network entity, an uplink data repetition capability report comprising an indication of whether the UE supports sub-slot physical uplink shared channel (PUSCH) repetition and a quantity of PUSCH transmissions supported per slot by the UE, wherein the uplink data repetition capability report indicates different PUSCH repetition capabilities associated with different processing time capabilities of the UE for different service types and indicates a maximum quantity of PUSCH transmissions supported per slot for all transport blocks (TBs) permitted in a slot, wherein each PUSCH repetition is counted as one PUSCH transmission of the maximum quantity of PUSCH transmissions;
receiving signaling comprising an uplink grant configuring one or more PUSCH repetitions within a slot based at least in part on the uplink data repetition capability report; and
transmitting, based at least in part on the uplink grant, the one or more configured PUSCH repetitions within the slot.
14. The method of claim 13 , wherein the uplink data repetition capability report comprises an indication that PUSCH repetition is supported in a first band at a sub-slot level and is not supported in a second band at the sub-slot level.
15. The method of claim 13 , wherein the uplink data repetition capability report indicates PUSCH repetition capabilities for each band of a configured band combination.
16. The method of claim 13 , further comprising: determining the uplink data repetition capability report based on determining that multiple PUSCH transmissions per repetition are supported by the UE.
17. The method of claim 13 , further comprising: determining, based at least on a gap between non-repeated PUSCH transmissions, the uplink data repetition capability report, wherein the uplink data repetition capability report comprises an indication of a defined gap.
18. The method of claim 17 , wherein the defined gap is based at least in part on a configured subcarrier spacing, one or more processing capabilities of the UE, or a combination thereof.
19. The method of claim 13 , wherein the quantity of PUSCH transmissions supported per slot by the UE is based at least in part on a quantity of PUSCH repetitions supported per transport block by the UE and a quantity of transport blocks supported per slot by the UE.
20. The method of claim 13 , wherein receiving the signaling comprising the uplink grant comprises:
receiving the signaling comprising the uplink grant and a time domain resource assignment for transmitting the one or more configured PUSCH repetitions based at least in part on the uplink data repetition capability report,
wherein the time domain resource assignment includes a start and length indicator value (SLIV) indicating a starting symbol and a transmission duration for the one or more configured PUSCH repetitions.
21. The method of claim 20 , wherein the method further comprises:
identifying directions for a plurality of symbols spanning the transmission duration; and
determining, based at least in part on the starting symbol and the identified directions for the plurality of symbols, a subset of the plurality of symbols for scheduling the one or more configured PUSCH repetitions.
22. The method of claim 13 , wherein the uplink data repetition capability report further comprises indications of:
a maximum length of each data repetition supported by the UE, and a maximum quantity of repetitions supported by the UE.
23. The method of claim 22 , wherein the uplink grant, based at least in part on the uplink data repetition capability report, includes a starting symbol index, a length of each data repetition, and a number of data repetitions permitted during uplink transmission.
24. The method of claim 13 , wherein the quantity of PUSCH transmissions supported per slot by the UE is based at least in part on a quantity of transport blocks supported per slot by the UE, and wherein each transport block of the quantity of transport blocks comprises one PUSCH repetition.
25. A non-transitory, computer-readable medium storing code for wireless communication at a user equipment (UE), the code comprising instructions executable by one or more processors to:
transmit, to a network entity, an uplink data repetition capability report comprising an indication of whether the UE supports sub-slot physical uplink shared channel (PUSCH) repetition and a quantity of PUSCH transmissions supported per slot by the UE, wherein the uplink data repetition capability report indicates different PUSCH repetition capabilities associated with different processing time capabilities of the UE for different service types and indicates a maximum quantity of PUSCH transmissions supported per slot for all transport blocks (TBs) permitted in a slot, wherein each PUSCH repetition is counted as one PUSCH transmission of the maximum quantity of PUSCH transmissions;
receive signaling comprising an uplink grant configuring one or more PUSCH repetitions within a slot based at least in part on the uplink data repetition capability report; and
transmit, based at least in part on the uplink grant, the one or more configured PUSCH repetitions within the slot.
26. The non-transitory, computer-readable medium of claim 25 , wherein the quantity of PUSCH transmissions supported per slot by the UE is based at least in part on a quantity of transport blocks supported per slot by the UE, and wherein each transport block of the quantity of transport blocks comprises one PUSCH repetition.
27. The non-transitory, computer-readable medium of claim 25 ,
wherein the uplink data repetition capability report comprises an indication that PUSCH repetition is supported in a first band at a sub-slot level and is not supported in a second band at the sub-slot level.
28. The non-transitory, computer-readable medium of claim 25 , wherein the uplink data repetition capability report indicates PUSCH repetition capabilities for each band of a configured band combination.
29. A user equipment (UE) for wireless communication, comprising:
means for transmitting, to a network entity, an uplink data repetition capability report comprising an indication of whether the UE supports sub-slot physical uplink shared channel (PUSCH) repetition and a quantity of PUSCH transmissions supported per slot by the UE, wherein the uplink data repetition capability report indicates different PUSCH repetition capabilities associated with different processing time capabilities of the UE for different service types and indicates a maximum quantity of PUSCH transmissions supported per slot for all transport blocks (TBs) permitted in a slot, wherein each PUSCH repetition is counted as one PUSCH transmission of the maximum quantity of PUSCH transmissions;
means for receiving signaling comprising an uplink grant configuring one or more PUSCH repetitions within a slot based at least in part on the uplink data repetition capability report; and
means for transmitting, based at least in part on the uplink grant, the one or more configured PUSCH repetitions within the slot.
30. The UE of claim 29 , wherein the quantity of PUSCH transmissions supported per slot by the UE is based at least in part on a quantity of transport blocks supported per slot by the UE, and wherein each transport block of the quantity of transport blocks comprises one PUSCH repetition.