Methods of multiplexing a high priority SR on a low priority PUSCH

1 . A user equipment (UE), comprising:

transmitting circuitry configured to:

in a case that at least one physical uplink control channel (PUCCH) for a high priority (HP) scheduling request (SR) (HP-SR PUCCH) overlaps with a low priority (LP) physical uplink shared channel (PUSCH), and in a case that HP SR multiplexing on the LP PUSCH is enabled, use different SR multiplexing methods based on whether a hybrid automatic repeat request-acknowledgment (HARQ-ACK) is multiplexed and based on a HARQ-ACK priority, and

in a case that the HARQ-ACK is multiplexed on the LP PUSCH, report the HP SR jointly with the multiplexed HARQ-ACK.

2 . The UE of claim 1 , wherein the transmitting circuitry is further configured to:

in a case that no HARQ-ACK is multiplexed on the PUSCH, report the HP SR after performing one or more HP HARQ-ACK procedures using reserved resource elements (REs) for an HP HARQ-ACK.

3 . The UE of claim 1 , wherein the transmitting circuitry is further configured to:

in a case that the HARQ-ACK is multiplexed on the LP PUSCH and a positive HP SR exists, report the HP SR jointly with the multiplexed HARQ-ACK, and

in a case that the HARQ-ACK is multiplexed on the LP PUSCH and the positive HP SR does not exist, report only the multiplexed HARQ-ACK.

4 . The UE of claim 1 , wherein the transmitting circuitry is further configured to:

in a case that an HP HARQ-ACK does not exist, drop the LP PUSCH and transmit only an HP PUCCH for a positive HP SR, and

in a case that the HP HARQ-ACK exists, transmit the LP PUSCH with an HP HARQ-ACK and drop the at least one HP-SR PUCCH.

5 . A base station (gNB), comprising:

receiving circuitry configured to:

in a case that at least one physical uplink control channel (PUCCH) for a high priority (HP) scheduling request (SR) (HP-SR PUCCH) overlaps with a low priority (LP) physical uplink shared channel (PUSCH), and in a case that HP SR multiplexing on the LP PUSCH is enabled, use different SR multiplexing methods based on whether a hybrid automatic repeat request-acknowledgment (HARQ-ACK) is multiplexed and based on a HARQ-ACK priority, and

in a case that the HARQ-ACK is multiplexed on the LP PUSCH, receive the HP SR jointly with the multiplexed HARQ-ACK.

6 . The gNB of claim 5 , wherein the receiving circuitry is further configured to:

in a case that no HARQ-ACK is multiplexed on the PUSCH, receive the HP SR after performing one or more HP HARQ-ACK procedures using reserved resource elements (REs) for an HP HARQ-ACK.

7 . The gNB of claim 5 , wherein the receiving circuitry is further configured to:

in a case that the HARQ-ACK is multiplexed on the LP PUSCH and a positive HP SR exists, receive the HP SR jointly with the multiplexed HARQ-ACK, and

in a case that the HARQ-ACK is multiplexed on the LP PUSCH and the positive HP SR does not exist, receive only the multiplexed HARQ-ACK.

8 . The gNB of claim 5 , wherein the receiving circuitry is further configured to:

in a case that an HP HARQ-ACK does not exist, receive only an HP PUCCH for a positive HP SR, instead of receiving the LP PUSCH, and

in a case that the HP HARQ-ACK exists, receive the LP PUSCH with an HP HARQ-ACK, instead of receiving the at least one HP-SR PUCCH.

9 . A method performed by a user equipment (UE) to multiplex a high priority (HP) scheduling request (SR) on a low priority (LP) physical uplink shared channel (PUSCH), the method comprising:

in a case that at least one physical uplink control channel (PUCCH) for the HP SR (HP-SR PUCCH) overlaps with the LP PUSCH, using different SR multiplexing methods based on whether a hybrid automatic repeat request-acknowledgment (HARQ-ACK) is multiplexed and based on a HARQ-ACK priority, and

in a case that the HARQ-ACK is multiplexed on the LP PUSCH, reporting the HP SR jointly with the multiplexed HARQ-ACK.