Multiplexing of PUCCH for beam failure recovery and other signals
Apparatuses, systems, and methods for multiplexing of PUCCH for beam failure recovery and other signals. A UE may determine a transmission dropping rule and a transmission power scaling rule for a PUCCH which is dedicatedly configured for secondary BFR transmission, such as a PUCCH-BFR, when it is multiplexed with at least one other signal. The PUCCH-BFR and the at least one other signal may be multiplexed in a CC or in multiple CCs. The UE may determine a transmission dropping rule, e.g., so that UE can transmit an uplink signals with higher priority and drop the other uplink signal with lower priority to avoid beam collisions. The UE may determine a transmission power scaling rule, e.g., so the UE may scale transmission power within a CC and/or across CCs. The UE may multiplex the PUCCH-BFR with the at least one other signal according to the rules.
1. A method for receiving a physical uplink control channel (PUCCH) configured for secondary beam failure recover (PUCCH-BFR), comprising:
receiving a configuration including a configuration associated with beam failure recovery (BFR) to be sent on a physical uplink control channel (PUCCH), wherein the BFR to be sent on the PUCCH (PUCCH-BFR) is associated with a scheduling request (SR) for BFR;
when transmission occasions for one PUCCH-BFR and K 0 PUCCHs for respective normal SRs would overlap with a transmission of a PUCCH with HARQ-ACK information in a slot or with a transmission of a PUCCH with one or more channel state information (CSI) reports in the slot, CEIL {log 2 (K 0 +2)} bits representing a negative SR or a positive SR for BFR and normal SRs are appended to bits of the HARQ-ACK information or prepended to bits of the one or more CSI reports for transmission;
determining a PUCCH resource for the transmission including the CEIL {log 2 (K 0 +2)} bits; and
transmitting the transmission including the CEIL {log 2 (K 0 +2)} bits.
2. The method of claim 1 ,
wherein the configuration associated with BFR to be sent on the PUCCH is included in a SchedulingRequestResourceConfig parameter.
3. The method of claim 1 ,
wherein the configuration is related to a SchedulingRequestResource identifier.
4. The method of claim 1 ,
wherein the CEIL {log 2 (K 0 +2)} bits are ordered in values of schedulingRequestResourceId for the SR for BFR and the K 0 normal scheduling requests.
5. The method of claim 1 ,
wherein the transmission satisfies a timeline requirement as defined in 3GPP Technical Specification 38.213.
6. The method of claim 1 ,
wherein an all-zero value for the CEIL {log 2 (K 0 +2)} bits represent the negative SR value across BFR based SR.
7. The method of claim 1 ,
wherein the PUCCH-BFR is received via one of PUCCH format 0 or PUCCH format 1.
8. A method for transmitting a physical uplink control channel (PUCCH) configured for secondary beam failure recover (PUCCH-BFR), comprising:
transmitting, to a user equipment (UE), a configuration including a configuration associated with beam failure recovery (BFR) to be sent on a physical uplink control channel (PUCCH), wherein the BFR to be sent on the PUCCH (PUCCH-BFR) is associated with a scheduling request (SR) for BFR;
determining, when a transmission occasions for one PUCCH-BFR and K 0 PUCCHs for respective normal SRs would overlap with a transmission of a PUCCH with HARQ-ACK information from the UE in a slot or with a transmission of a PUCCH with one or more channel state information (CSI) reports from the UE in the slot, that CEIL {log 2 (K 0 +2)} bits representing a negative SR or a positive SR for BFR and normal SRs will be appended to bits of the HARQ-ACK information or prepended to bits of the one or more CSI reports for transmission;
determining a PUCCH resource for receiving the transmission from the UE, including the CEIL {log 2 (K 0 +2)} bits; and
receiving the transmission from the UE, including the CEIL {log 2 (K 0 +2)} bits.
9. The method of claim 8 ,
wherein the configuration associated with BFR to be sent on the PUCCH is included in a SchedulingRequestResourceConfig parameter.
10. The method of claim 8 ,
wherein the configuration is related to a SchedulingRequestResource identifier.
11. The method of claim 8 ,
wherein the CEIL {log 2 (K 0 +2)} bits are ordered in values of schedulingRequestResourceId for the SR for BFR and the K 0 normal scheduling requests.
12. The method of claim 8 ,
wherein the transmission satisfies a timeline requirement as defined in 3GPP Technical Specification 38.213.
13. The method of claim 8 ,
wherein an all-zero value for the CEIL {log 2 (K 0 +2)} bits represent the negative SR value across BFR based SR.
14. The method of claim 8 ,
wherein the PUCCH-BFR is received via one of PUCCH format 0 or PUCCH format 1.
15. An apparatus, comprising:
a memory; and
at least one processor in communication with the memory and configured to:
transmit, to a user equipment (UE), a configuration including a configuration associated with beam failure recovery (BFR) to be sent on a physical uplink control channel (PUCCH), wherein the BFR to be sent on the PUCCH (PUCCH-BFR) is associated with a scheduling request (SR) for BFR;
determine, when a transmission occasions for one PUCCH-BFR and K 0 PUCCHs for respective normal SRs would overlap with a transmission of a PUCCH with HARQ-ACK information from the UE in a slot or with a transmission of a PUCCH with one or more channel state information (CSI) reports from the UE in the slot, that CEIL {log 2 (K 0 +2)} bits representing a negative SR or a positive SR for BFR and normal SRs will be appended to bits of the HARQ-ACK information or prepended to bits of the one or more CSI reports for transmission;
determine a PUCCH resource for receiving the transmission from the UE, including the CEIL {log 2 (K 0 +2)} bits; and
receive the transmission from the UE, including the CEIL {log 2 (K 0 +2)} bits.
16. The apparatus of claim 15 ,
wherein the configuration associated with BFR to be sent on the PUCCH is included in a SchedulingRequestResourceConfig parameter.
17. The apparatus of claim 15 ,
wherein the configuration is related to a SchedulingRequestResource identifier.
18. The apparatus of claim 15 ,
wherein the CEIL {log 2 (K 0 +2)} bits are ordered in values of schedulingRequestResourceId for the SR for BFR and the K 0 normal scheduling requests.
19. The apparatus of claim 15 ,
wherein the transmission satisfies a timeline requirement as defined in 3GPP Technical Specification 38.213.
20. The apparatus of claim 15 ,
wherein an all-zero value for the CEIL {log 2 (K 0 +2)} bits represent the negative SR value across BFR based SR.