Pre-emption priority level for uplink control information (UCI) and physical uplink shared channel (PUSCH) conflict resolution
Apparatuses and methods are disclosed for pre-emption priority level for Uplink Control Information (UCI) and/or Physical Uplink Shared Channel (PUSCH) conflict resolution. In one embodiment, a method implemented in a network node includes indicating to a wireless device (WD) a priority associated with at least one uplink (UL) channel; and receiving at least one UL signal based at least in part on the indicated priority. In another embodiment, a method implemented in a WD includes determining a priority associated with at least one of at least two uplink (UL) channels; and resolving a conflict between the at least two uplink channels based at least in part on the determined priority.
1. A method implemented in a network node configured to communicate with a wireless device, the method comprising:
indicating to the wireless device a pre-emption priority level associated with at least two uplink channels;
determining whether a timeline permits multiplexing the at least two uplink channels on a physical uplink shared channel (PUSCH); and
when the timeline permits multiplexing the at least two uplink channels on the PUSCH, then receiving uplink control information (UCI) multiplexed with the PUSCH on overlapping resources according to pre-emption priority levels of a physical uplink control channel (PUCCH); and
when the timeline does not permit multiplexing of the at least two uplink channels, then puncturing the PUSCH and receiving UCI over the PUCCH.
2. The method of claim 1 , wherein the pre-emption priority level is configured to allow the wireless device to resolve a conflict between an uplink channel of the at least two uplink channels associated with the pre-emption priority level and at least one other uplink channel for a same uplink resource.
3. The method of claim 1 , wherein the at least two uplink channels associated with the indicated pre-emption priority level is one of a PUCCH and a PUSCH.
4. The method of claim 3 , wherein the pre-emption priority level is associated with at least one UCI.
5. The method of claim 4 , wherein the at least one UCI includes at least one of a Hybrid Automatic Repeat reQuest (HARQ) acknowledgement (ACK) a channel state information (CSI) and a scheduling request (SR).
6. The method of claim 1 , wherein the pre-emption priority level is associated with at least one logical channel (LCH).
7. The method of claim 1 , wherein the indicating the pre-emption priority level comprises indicating the pre-emption priority level in at least a downlink control information (DCI) message.
8. The method of claim 7 , wherein the indicating the pre-emption priority level further comprises:
transmitting a field indicating the pre-emption priority level for a Hybrid Automatic Repeat reQuest (HARQ) acknowledgement (ACK) the field included in the DCI message, the DCI message one of scheduling and activating a physical downlink shared channel (PDSCH) to which the HARQ ACK is associated.
9. The method of claim 1 , wherein the indicating the pre-emption priority level comprises indicating the pre-emption priority level in at least a field within a logical channel configuration information element (IE).
10. The method of claim 9 , wherein the field within the logical channel configuration IE is a priority field, the pre-emption priority level being derived from a value in the priority field.
11. The method of claim 9 , wherein the field within the logical channel configuration IE is a pre-emption priority level field, the pre-emption priority level field being different from a priority field in the logical channel configuration IE.
12. The method of claim 1 , wherein the indicating the pre-emption priority level comprises indicating the pre-emption priority level in at least one of:
a beta offset indicator;
a radio resource control (RRC) signaling;
a field within a channel state information report configuration information element (IE);
a beta factors field in a PUSCH configuration IE; and
a multiple Hybrid Automatic Repeat reQuest (HARQ) acknowledgments (ACKs) PUCCH resource list parameter indicating a pre-emption priority level for each of the multiple HARQ ACKs.
13. A method implemented in a wireless device configured to communicate with a network node, the method comprising:
determining a pre-emption priority level associated with a physical uplink control channel (PUCCH) of at least two uplink channels on overlapping resources;
determining whether a timeline permits multiplexing the at least two uplink channels on a physical uplink shared channel (PUSCH);
when the timeline permits multiplexing the at least two uplink channels on the PUSCH, then transmitting uplink control information (UCI) multiplexed with the PUSCH on the overlapping resources according to pre-emption priority levels of the PUCCH; and
when the timeline does not permit multiplexing of the at least two uplink channels, then puncturing the PUSCH and transmitting UCI over the PUCCH.
14. The method of claim 13 , wherein determining the pre-emption priority level comprises obtaining a downlink control information (DCI) message comprising the pre-emption priority level from the network node, the DCI scheduling a downlink transmission and a HARQ ACK is feedback of whether the downlink transmission is successfully received.
15. The method of claim 13 , further comprising: determining a pre-emption priority level associated with another uplink channel of the at least two uplink channels, the another uplink channel being PUCCH or PUSCH; and
prior to transmitting a HARQ ACK:
determining that the PUCCH has same or higher pre-emption priority level than that of the another uplink channel.
16. The method of claim 15 , further comprising: dropping the HARQ ACK when determining that the PUCCH has lower pre-emption priority level than that of the another uplink channel.
17. The method of claim 13 , wherein the at least two uplink channels associated with the determined pre-emption priority level is one of a PUCCH and a PUSCH.
18. The method of claim 17 , wherein the pre-emption priority level is associated with at least one UCI.
19. The method of claim 18 , wherein the at least one UCI includes at least one of a HARQACK, a channel state information (CSI) and a scheduling request (SR).
20. The method of claim 13 , wherein the pre-emption priority level is associated with at least one logical channel (LCH).
21. The method of claim 13 , wherein the determining the pre-emption priority level comprises:
determining the pre-emption priority level based at least in part on an indication of the pre-emption priority level in at least a downlink control information (DCI) message.