Cancellation and replacement of PUSCH
Apparatuses, systems, and methods for cancellation and/or replacement of PUSCHs. A user equipment device (UE) may configure a first PUSCH and a second PUSCH, where the first PUSCH may correspond to a configured grant and where the second PUSCH may correspond to a configured grant or scheduled by a PDCCH on a serving cell. The UE may determine that at least one transmission occasion associated with the first PUSCH overlaps in time with at least one transmission occasion associated with the second PUSCH. The UE may drop transmissions scheduled for the second PUSCH, e.g., based on determining that a priority of the first PUSCH is higher than a priority of the second PUSCH, e.g., starting with a first symbol of a repetition of the second PUSCH which overlaps in time with one or more repetitions of the first PUSCH.
1. A method for selection of physical uplink shared channels (PUSCHs), comprising:
configuring a first PUSCH and a second PUSCH, wherein the first PUSCH corresponds to a first configured grant, and wherein the second PUSCH is scheduled by a physical downlink control channel (PDCCH) on a serving cell;
determining that at least one transmission repetition associated with the first PUSCH overlaps in time with at least one transmission repetition associated with the second PUSCH; and
dropping one or more transmission repetitions, wherein the dropping includes:
determining whether a downlink hybrid automatic repeat request (HARQ) process identifier (HPID) of the first PUSCH is different from an HPID of the second PUSCH;
in response to determining that the HPID of the first PUSCH is different from the HPID of the second PUSCH, dropping, when a priority of the first PUSCH is higher than a priority of the second PUSCH, for each respective repetition of the second PUSCH, transmission repetitions scheduled for the second PUSCH starting with a first symbol of the respective repetition of the second PUSCH which overlaps in time with one or more repetitions of the first PUSCH; and
in response to determining that the HPID of the first PUSCH is not different from the HPID of the second PUSCH, dropping transmission repetitions scheduled for the first PUSCH starting from a first symbol of a repetition of the first PUSCH which overlaps in time with one or more repetition of the second PUSCH.
2. The method of claim 1 ,
wherein the first PUSCH is associated with a first priority level, wherein the second PUSCH is associated with a second priority level, wherein the first priority level is associated with a high priority, and wherein the second priority level is associated with one of low priority or no priority.
3. The method of claim 1 ,
wherein the first PUSCH is one of a PUSCH with slot aggregation, a PUSCH with repetition type A, or a PUSCH with repetition type B.
4. The method of claim 1 ,
wherein the second PUSCH is one of a PUSCH with slot aggregation, a PUSCH with repetition type A, or a PUSCH with repetition type B.
5. The method of claim 1 , further comprising:
transmitting at least a portion of transmissions scheduled for the second PUSCH that do not time overlap with transmissions scheduled for the first PUSCH.
6. The method of claim 1 , further comprising:
skipping at least a portion of transmissions scheduled for the second PUSCH that do not time overlap with transmissions scheduled for the first PUSCH.
7. An apparatus, comprising:
a memory; and
a processing element in communication with the memory, wherein the processing element is configured to:
configure a first physical uplink shared channel (PUSCH) and a second PUSCH, wherein the first PUSCH corresponds to a first configured grant, and wherein the second PUSCH is scheduled by a physical downlink control channel (PDCCH) on a serving cell;
determine that at least one transmission repetition associated with the first PUSCH overlaps in time with at least one transmission repetition associated with the second PUSCH; and
drop one or more transmission repetitions, wherein to drop the one or more transmission repetitions, the processing element is further configured to:
determine whether a downlink hybrid automatic repeat request (HARQ) process identifier (HPID) of the first PUSCH is different from an HPID of the second PUSCH;
in response to determining that the HPID of the first PUSCH is different from the HPID of the second PUSCH, drop, when a priority of the first PUSCH is higher than a priority of the second PUSCH, for each respective repetition of the second PUSCH, transmission repetitions scheduled for the second PUSCH starting with a first symbol of the respective repetition of the second PUSCH which overlaps in time with one or more repetitions of the first PUSCH; and
in response to determining that the HPID of the first PUSCH is not different from the HPID of the second PUSCH, drop transmission repetitions scheduled for the first PUSCH starting from a first symbol of a repetition of the first PUSCH which overlaps in time with one or more repetition of the second PUSCH.
8. The apparatus of claim 7 ,
wherein the first PUSCH is associated with a first priority level, wherein the second PUSCH is associated with a second priority level, wherein the first priority level is associated with a high priority, and wherein the second priority level is associated with one of low priority or no priority.
9. The apparatus of claim 7 ,
wherein the first PUSCH is one of a PUSCH with slot aggregation, a PUSCH with repetition type A, or a PUSCH with repetition type B.
10. The apparatus of claim 7 ,
wherein the second PUSCH is one of a PUSCH with slot aggregation, a PUSCH with repetition type A, or a PUSCH with repetition type B.
11. A user equipment device (UE), comprising:
at least one antenna;
at least one radio, wherein the at least one radio is configured to perform cellular communication using at least one radio access technology (RAT); and
one or more processors coupled to the at least one radio, wherein the one or more processors and the at least one radio are configured to perform voice and/or data communications;
wherein the one or more processors are configured to cause the UE to:
determine that at least one transmission repetition associated with a first configured grant physical uplink shared channel (PUSCH) overlaps in time with at least one transmission repetition associated with a second PUSCH scheduled by a physical downlink control channel (PDCCH) on a serving cell; and
drop one or more transmission repetitions, wherein to drop the one or more transmission repetitions, the one or more processors are further configured to cause the UE to:
determine whether a downlink hybrid automatic repeat request (HARD) process identifier (HPID) of the first configured grant PUSCH is different from an HPID of the second PUSCH;
in response to determining that the HPID of the first configured grant PUSCH is different from the HPID of the second PUSCH, drop, when a priority of the first configured grant PUSCH is higher than a priority of the second PUSCH, for each respective repetition of the second PUSCH, transmission repetitions scheduled for the second PUSCH starting with a first symbol of the respective repetition of the second PUSCH which overlaps in time with one or more repetitions of the first configured grant PUSCH; and
in response to determining that the HPID of the first configured grant PUSCH is not different from the HPID of the second PUSCH, drop transmission repetitions scheduled for the first configured grant PUSCH starting from a first symbol of a repetition of the first configured grant PUSCH which overlaps in time with one or more repetition of the second PUSCH.
12. The UE of claim 11 ,
wherein the first configured grant PUSCH uses repetition type B.
13. The UE of claim 11 ,
wherein the second PUSCH uses slot aggregation or repetition type A.
14. The UE of claim 11 ,
wherein the UE supports interlaced transmissions.
15. The UE of claim 11 ,
wherein the one or more processors are further configured to cause the UE to:
check, on a repetition-by-repetition basis, each actual repetition in the first configured grant PUSCH with each actual repetition in the second PUSCH to determine whether or not repetitions overlap in time.
16. The UE of claim 11 ,
wherein the first configured grant PUSCH is one of a PUSCH with slot aggregation, a PUSCH with repetition type A, or a PUSCH with repetition type B.
17. The UE of claim 11 ,
wherein the second PUSCH is one of a PUSCH with slot aggregation, a PUSCH with repetition type A, or a PUSCH with repetition type B.
18. The UE of claim 11 ,
wherein the one or more processors are further configured to cause the UE to:
transmit at least a first portion of transmissions scheduled for the second PUSCH that do not time overlap with transmissions scheduled for the first configured grant PUSCH; and
skip at least a second portion of transmissions scheduled for the second PUSCH that do not time overlap with transmissions scheduled for the first configured grant PUSCH.
19. The UE of claim 11 ,
wherein the first configured grant PUSCH is associated with a first priority level, wherein the second PUSCH is associated with a second priority level, wherein the first priority level is associated with a high priority, and wherein the second priority level is associated with one of low priority or no priority.
20. The UE of claim 11 ,
wherein the one or more processors are further configured to cause the UE to:
transmit at least a portion of transmissions scheduled for the second PUSCH that do not time overlap with transmissions scheduled for the first configured grant PUSCH.