US11968678B2ActiveUtilityA1
UCI multiplexing with physical layer priority and LCH based prioritization
Est. expiryApr 6, 2041(~14.7 yrs left)· nominal 20-yr term from priority
Inventors:Weidong YangRalf RossbachFangli XuAmir Aminzadeh GohariChunxuan YeDawei ZhangHaijing HuOghenekome OteriSigen YeWei ZengWenshu Zhang
H04W 72/1268H04L 1/1812H04W 72/566H04W 72/21H04W 24/02H04L 1/1671H04L 5/0053H04L 5/0055H04L 5/0057H04L 1/1854H04L 1/0026
51
PatentIndex Score
0
Cited by
33
References
20
Claims
Abstract
Methods and wireless communication systems are provided for uplink control information (UCI) multiplexing with physical layer (PHY) priority and logical channel (LCH) based prioritization.
Claims
exact text as granted — not AI-modifiedThe invention claimed is:
1. A method for a user equipment (UE) to perform uplink control information (UCI) multiplexing with physical layer (PHY) priority and logical channel (LCH) based prioritization, the method comprising:
assuming, at a PHY entity of the UE, a scheduling request (SR) status for a SR;
identifying, at the PHY entity of the UE, a target physical uplink shared channel (PUSCH) for UCI multiplexing based on PHY priority rules and the SR status that assumed by the PHY entity;
indicating, from the PHY entity to the MAC entity, a physical uplink control channel (PUCCH) resource Z and UCI contents of the PUCCH resource Z, wherein indicating the PUCCH resource Z includes indicating a starting symbol and a duration of a PUCCH corresponding to the target PUSCH, and wherein the UCI contents includes the SR;
receiving, at the PHY entity, transport blocks from the MAC entity; and
generating, at the PHY entity, uplink transmissions for the transport blocks,
wherein if the MAC entity does not generate a MAC protocol data unit (PDU) for the target PUSCH or another PUSCH corresponding to one of the transport blocks delivered by the MAC entity at least partially overlaps with the target PUSCH, and if the transmission of the PUCCH resource Z would overlap with any PUSCH on a same component carrier or on another component carrier, the PHY entity transmits neither the target PUSCH nor the PUCCH resource Z,
wherein if the MAC entity does not generate the MAC PDU for the target PUSCH or another PUSCH corresponding to one of the transport blocks delivered by the MAC entity at least partially overlaps with the target PUSCH, and if the transmission of the PUCCH resource Z would not overlap with any PUSCH on the same component carrier or on another component carrier, the PHY entity transmits over the PUCCH resource Z, and
wherein if the MAC entity generates the MAC PDU for the target PUSCH or the target PUSCH is without an uplink shared channel (UL-SCH) and is not dropped due to another PUSCH corresponding to one of the transport blocks delivered by the MAC entity, the PHY entity multiplexes the UCI, except for the SR, over the target PUSCH.
2. The method of claim 1 , wherein identifying, at the PHY entity, the target PUSCH for UCI multiplexing is further based on at least one of channel state information (CSI) and a hybrid automatic repeat request-acknowledgement (HARQ-ACK).
3. The method of claim 2 , further comprising selecting, at the PHY entity, the target PUSCH for UCI multiplexing to avoid overlapping of a HARQ-ACK PUCCH resource using a PUCCH format 1 and an SR PUCCH resource using the PUCCH format 1.
4. The method of claim 1 , wherein the UCI contents further include at least one of hybrid automatic repeat request-acknowledgement (HARQ) feedback and channel state information (CSI).
5. The method of claim 1 , wherein the UCI contents further include one or more SR resource identifier (ID) of one or more SR included in the PUCCH resource Z.
6. The method of claim 1 , further comprising selecting, by the PHY entity, a dynamic grant (DG) PUSCH as a candidate for the target PUSCH for UCI multiplexing.
7. The method of claim 1 , further comprising not selecting, by the PHY entity, configured grant (CG) PUSCHs as candidates for the target PUSCH for UCI multiplexing.
8. The method of claim 1 , further comprising not selecting, by the PHY entity, semi-persistent channel state information (SP-CSI) PUSCHs as candidates for the target PUSCH for UCI multiplexing.
9. The method of claim 1 , further comprising selecting, by the PHY entity, configured grant (CG) PUSCHs as candidates for the target PUSCH for UCI multiplexing.
10. The method of claim 9 , further comprising selecting, by the PHY entity, a CG PUSCH occasion as one of the candidates for the target PUSCH when the CG PUSCH occasion does not overlap with a dynamic grant (DG) PUSCH candidate or a CG PUSCH candidate previously admitted to a set of hypothetical PUSCH transmissions.
11. The method of claim 10 , further comprising selecting, by the PHY entity, semi-persistent channel state information (SP-CSI) PUSCH as one of possible candidates for the target PUSCH for UCI multiplexing when the PHY entity assumes that an overlapping SR is negative and when the SP-CSI PUSCH does not overlap with a previously admitted DG PUSCH or a previously admitted CG PUSCH.
12. The method of claim 11 , further comprising, for each component carrier (CC), following a processing order to derive non-overlapping PUSCHs or PUSCH occasions in a slot to admit to the set of hypothetical PUSCH transmissions, wherein a candidate admitted earlier to the set of hypothetical PUSCH transmissions blocks a later overlapping PUSCH or later overlapping PUSCH occasion in the slot from being admitted to the set of hypothetical PUSCH transmissions.
13. The method of claim 12 , wherein the processing order comprises processing dynamic grant (DG) PUSCHs, followed by CG PUSCH occasions with a CG configuration with slot aggregation or PUSCH repetition continuing from a previous slot (CG continuations), followed by new CG PUSCH occasions configured to start in the slot (new CG transmissions), and followed by the SP-CSI PUSCHs.
14. The method of claim 12 , wherein the processing order comprises processing dynamic grant (DG) PUSCHs, followed by the SP-CSI PUSCHs, followed by CG PUSCH occasions with a CG configuration with slot aggregation or PUSCH repetition continuing from a previous slot (CG continuations), and followed by new CG PUSCH occasions configured to start in the slot (new CG transmissions).
15. The method of claim 12 , wherein the processing order comprises processing dynamic grant (DG) PUSCHs, followed by CG PUSCH occasions with a CG configuration with slot aggregation or PUSCH repetition continuing from a previous slot (CG continuations), followed by the SP-CSI PUSCHs, and followed by new CG PUSCH occasions configured to start in the slot (new CG transmissions).
16. The method of claim 13 , wherein the PHY entity independently derives, for high priority (HP) physical layer priority and low priority (LP) physical layer priority, the non-overlapping PUSCHs or PUSCH occasions in the slot to admit to the set of hypothetical PUSCH transmissions.
17. The method of claim 16 , wherein when a selected LP PUSCH for UCI multiplexing overlaps with a selected HP PUSCH for UCI multiplexing, the MAC entity generates a single corresponding MAC PDU.
18. The method of claim 13 , wherein the PHY entity derives the non-overlapping PUSCHs or PUSCH occasions in the slot to admit to the set of hypothetical PUSCH transmissions with a dependence between high priority (HP) physical layer priority and low priority (LP) physical layer priority, and wherein the PHY entity does not consider LP PUSCHs until selection of HP PUSCHs for admitting to the set of hypothetical PUSCH transmissions is complete.
19. The method of claim 13 , wherein the PHY entity derives the non-overlapping PUSCHs or PUSCH occasions in the slot to admit to the set of hypothetical PUSCH transmissions with a dependence between high priority (HP) physical layer priority and low priority (LP) physical layer priority, and wherein the PHY entity considers HP PUSCHs in selecting a LP PUSCH to admit to the set of hypothetical PUSCH transmissions.
20. A method for a user equipment (UE) to perform uplink control information (UCI) multiplexing with physical layer (PHY) priority and logical channel (LCH) based prioritization, the method comprising:
determining, at a PHY entity of the UE, a scheduling request (SR) status for an SR based on whether an SR status indication is received from a media access control (MAC) entity of the UE;
identifying, at the PHY entity of the UE, a target physical uplink shared channel (PUSCH) for UCI multiplexing based at least in part on PHY priority rules and the SR status;
indicating, from the PHY entity to the MAC entity, a physical uplink control channel (PUCCH) resource Z and UCI contents of the PUCCH resource Z, wherein indicating the PUCCH resource Z includes indicating a starting symbol and a duration of a PUCCH corresponding to the target PUSCH, and wherein the UCI contents includes the SR;
receiving, at the PHY entity, transport blocks from the MAC entity; and
generating, at the PHY entity, uplink transmissions for the transport blocks,
wherein if the MAC entity does not generate a MAC protocol data unit (PDU) for the target PUSCH or another PUSCH corresponding to one of the transport blocks delivered by the MAC entity at least partially overlaps with the target PUSCH, and if the transmission of the PUCCH resource Z would overlap with any PUSCH on a same component carrier or on another component carrier, the PHY entity transmits neither the target PUSCH nor the PUCCH resource Z,
wherein if the MAC entity does not generate the MAC PDU for the target PUSCH or another PUSCH corresponding to one of the transport blocks delivered by the MAC entity at least partially overlaps with the target PUSCH, and if the transmission of the PUCCH resource Z would not overlap with any PUSCH on the same component carrier or on another component carrier, the PHY entity transmits over the PUCCH resource Z, and
wherein if the MAC entity generates the MAC PDU for the target PUSCH or the target PUSCH is without an uplink shared channel (UL-SCH) and is not dropped due to another PUSCH corresponding to one of the transport blocks delivered by the MAC entity, the PHY entity multiplexes the UCI, except for the SR, over the target PUSCH.Cited by (0)
No later patents cite this yet.
References (0)
No backward citations on record.