IP Library Granted Patent US 12,225,574
Granted Patent B2
US 12,225,574 · App. 17/601,255 · Granted Feb 11, 2025

Priority-dependent uci resource determination

Inventors: Jonas Fröberg Olsson (Ljungsbro, SE); Kittipong Kittichokechai (Järfälla, SE); Yufei Blankenship (Kildeer, IL); Ali Behravan (Stockholm, SE); Bikramjit Singh (Kirkkonummi, FI); Mattias Andersson (Sundbyberg, SE)
Assignee: Telefonaktiebolaget LM Ericsson (publ)
H04W72/569H04L1/1864H04L5/0064H04W72/21H04W72/23
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,225,574
App. No.
17/601,255
Granted
Feb 11, 2025
Kind
B2
Abstract

Systems and methods for priority-dependent Uplink Control Information (UCI) resource determination are provided. In some embodiments, a wireless device determines that one or more UCIs are to be multiplexed onto a Physical Uplink Shared Channel (PUSCH); determines priorities of the PUSCH and/or each of the one or more UCIs; determines at least one beta offset value for one or more UCIs based on one or more of the priorities; set or adjust a UCI code rate based on the at least one beta offset value; and transmit a UCI according to the UCI code rate. This provides a simple and consistent method to deduce beta offset value for UCI based on priorities of UCI and PUSCH. The solution supports possible multiple different beta offset values determined without extra explicit signaling, i.e., it helps to reduce DCI bits needed to indicate potentially multiple beta offset values.

Claims (58)

1. A method of operating a wireless device for priority-dependent Uplink Control Information, UCI, resource determination, the method comprising:

determining that one or more UCIs are to be multiplexed onto a Physical Uplink Shared Channel, PUSCH;

determining priorities of the PUSCH and/or each of the one or more UCIs;

determining at least one beta offset value for the one or more UCIs based on one or more of the priorities of the PUSCH and/or each of a plurality of UCIs;

setting or adjusting a UCI code rate based on the at least one beta offset value; and

transmitting a UCI according to the UCI code rate;

wherein determining the at least one beta offset value for the UCI comprises determining beta offset values for a plurality of UCI messages based on the one or more of the priorities of the PUSCH and each of the plurality of UCIs;

wherein one beta offset value of the at least one beta offset value is determined for multiple UCIs to be multiplexed on the PUSCH based on a priority of all the UCIs and the PUSCH; and

wherein a beta offset value of the at least one beta offset value for a first transmission opportunity in a Configured Grant, CG, period is combined with a priority value to determine the beta offset value.

2. The method of claim 1 wherein the at least one beta offset value for the one or more UCI comprises a beta offset value for Hybrid Automatic Request Acknowledge, HARQ-ACK, or a beta offset value for Channel State Information, CSI.

3. The method of claim 1 wherein the beta offset value of each of the plurality of UCIs is determined separately based on a priority of the respective UCI and the PUSCH.

4. The method of claim 1 wherein the beta offset value for each of the plurality of UCIs is determined based on an indicated or configured beta factor.

5. The method of claim 1 wherein the beta offset value is one of the group consisting of:

determined from a table indexed by a combination of UCI and PUSCH priorities;

determined from a defined formula that considers a combination of UCI and PUSCH priorities; and

determined based on higher layer priorities.

6. The method of claim 1 wherein the UCI or PUSCH priority is explicitly indicated in the Download Control Information, DCI, semi-statically configured, and/or derived from other indicators.

7. The method of claim 1 wherein the PUSCH priority is explicitly indicated in an uplink, UL, scheduling grant or activation grant or is semi-statically configured.

8. The method of claim 1 wherein the HARQ-ACK for a Physical Downlink Shared Channel, PDSCH, has a same priority as the priority of the PDSCH.

9. The method of claim 8 wherein the PDSCH priority is indicated in Downlink, DL, scheduling DCI.

10. The method of claim 9 wherein the PDSCH priority is semi-statically configured.

11. The method of claim 1 wherein an Aperiodic CSI, A-CSI, has a same priority as a priority indicator in a UL grant requesting the CSI.

12. The method of claim 11 wherein the A-CSI always has a lowest priority with respect to other UCIs and PUSCHs.

13. The method of claim 11 wherein the priority of the A-CSI is semi-statically configured.

14. The method of claim 11 wherein the beta offset value of the A-CSI is identical to or is derived from a beta offset indicator in the DCI.

15. The method of claim 11 wherein the beta offset value of the A-CSI is determined from a combination of a beta offset indicator in the DCI and the priority of the PUSCH.

16. The method of claim 11 wherein a priority of a specific A-CSI that is determined based on a PDSCH Demodulation Reference Signal, DMRS, to be multiplexed on the PUSCH is the same as the priority of the PDSCH.

17. The method of claim 1 wherein the beta offset value for one of the UCIs multiplexed in the PUSCH is determined based on a configuration used, wherein the configuration used comprises a configuration type or number used in a UL with multiple Configured Grants, CGs.

18. The method of claim 17 wherein different configurations carry different traffic with different reliabilities or priorities.

19. The method of claim 1 wherein, where a dynamic grant follows a failed UL transmission in a CG, the determination of the beta offset value for the UCI transmitted in the PUSCH utilizes information for a given CG where an initial UL transmission happened out of multiple CGs.

20. A method of operating a radio network node for priority-dependent Uplink Control Information, UCI, resource determination, the method comprising:

determining that a plurality of UCIs are to be multiplexed onto a Physical Uplink Shared Channel, PUSCH; and

receiving a UCI according to a UCI code rate based on at least one beta offset value determined based on one or more of priorities of the PUSCH and each of the plurality of UCIs;

wherein the at least one beta offset value for the UCI comprises beta offset values for a plurality of UCI messages based on one or more of the priorities of the PUSCH and each of the plurality of UCIs;

wherein one beta offset value of the at least one beta offset value is determined for multiple UCIs to be multiplexed on the PUSCH based on a priority of all the UCIs and the PUSCH; and

wherein a beta offset value of the at least one beta offset value for a first transmission opportunity in a Configured Grant, CG, period is combined with a priority value to determine the beta offset value.

21. The method of claim 20 wherein the beta offset value for the UCI comprises a beta offset value for Hybrid Automatic Request Acknowledge, HARQ-ACK, or a beta offset value for Channel State Information, CSI.

22. The method of claim 21 wherein the beta offset value of each of the plurality of UCIs is determined separately based on a priority of the respective UCI and the PUSCH.

23. The method of claim 21 wherein the beta offset value for each of the plurality of UCIs is determined based on an indicated or configured beta factor.

24. A wireless device for priority-dependent Uplink Control Information, UCI, resource determination, the wireless device comprising:

one or more processors; and

memory storing instructions executable by the one or more processors, whereby the wireless device is operable to:

determine that one or more UCIs are to be multiplexed onto a Physical Uplink Shared Channel, PUSCH;

determine priorities of the PUSCH and/or each of the one or more UCIs;

determine at least one beta offset value for the one or more UCIs based on one or more of the priorities of the PUSCH and/or each of a plurality of UCIs;

set or adjust a UCI code rate based on the at least one beta offset value; and

transmit a UCI according to the UCI code rate;

wherein determining the at least one beta offset value for the UCI comprises determining beta offset values for a plurality of UCI messages based on the one or more of the priorities of the PUSCH and each of the plurality of UCIs;

wherein one beta offset value of the at least one beta offset value is determined for multiple UCIs to be multiplexed on the PUSCH based on a priority of all the UCIs and the PUSCH; and

wherein a beta offset value of the at least one beta offset value for a first transmission opportunity in a Configured Grant, CG, period is combined with a priority value to determine the beta offset value.

25. A network node for priority-dependent Uplink Control Information, UCI, resource determination, the network node comprising:

one or more processors; and

memory comprising instructions to cause the network node to:

determine that a plurality of UCIs are to be multiplexed onto a Physical Uplink Shared Channel, PUSCH; and

receive a UCI according to a UCI code rate based on at least one beta offset value determined based on one or more of priorities of the PUSCH and each of the plurality of UCIs;

wherein the at least one beta offset value for the UCI comprises beta offset values for a plurality of UCI messages based on the one or more of the priorities of the PUSCH and each of the plurality of UCIs;

wherein one beta offset value of the at least one beta offset value is determined for multiple UCIs to be multiplexed on the PUSCH based on a priority of all the UCIs and the PUSCH; and

wherein a beta offset value of the at least one beta offset value for a first transmission opportunity in a Configured Grant, CG, period is combined with a priority value to determine the beta offset value.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 7, 2021
From: FRÖBERG OLSSON, JONAS; KITTICHOKECHAI, KITTIPONG; BLANKENSHIP, YUFEI; BEHRAVAN, ALI; ANDERSSON, MATTIAS
To: TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
Reel/Frame 057724/0891 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 7, 2021
From: SINGH, BIKRAMJIT
To: OY L M ERICSSON AB
Reel/Frame 057724/0925 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 7, 2021
From: OY L M ERICSSON AB
To: TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
Reel/Frame 057724/0930 →
Continuity (2)
Provisional Application 62828309 · Apr 2, 2019
Related Publication 20220183025A1 · Jun 9, 2022
References Cited (18)
US 20210051509A1 · Wu · 2021 [cited by examiner]
US 20210068100A1 · Takeda · 2021 [cited by examiner]
US 20210321394A1 · Li · 2021 [cited by examiner]
CN 102484869A · 2012 [cited by applicant]
CN 107852289A · 2018 [cited by applicant]
CN 108566267A · 2018 [cited by applicant]
WO 2018165347A1 · 2018 [cited by applicant]
WO 2018231728A1 · 2018 [cited by applicant]
WO WO2019137213A1 · 2019 [cited by examiner]
Author Unknown, “Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) protocol specification (Release 15),” Technical Specification 38.331, Version 15.4.0, Dec. 2018, 3GPP Organizational … [cited by applicant]
First Office Action for Chinese Patent Application No. 202080040835.3, mailed Jan. 9, 2024, 14 pages. [cited by applicant]
Examination Report for European Patent Application No. 20718811.1, mailed Jun. 22, 2023, 6 pages. [cited by applicant]
Author Unkown, “Technical Specification Group Radio Access Network; NR; Multiplexing and channel coding (Release 15),” Technical Specification 38.212, Version 15.5.0, Mar. 2019, 3GPP Organizational Partners, 101 pages. [cited by applicant]
Author Unknown, “Technical Specification Group Radio Access Network; NR; Physical layer procedures for control (Release 15),” Technical Specification 38.213, Version 15.4.0, Dec. 2018, 3GPP Organizational Partners, 104 … [cited by applicant]
CMCC, “R1-1902337: Discussion on intra-UE multiplexing,” 3GPP TSG RAN WG1 #96, Feb. 25-Mar. 1, 2019, Athens, Greece, 4 pages. [cited by applicant]
Ericsson, “R1-1805168: On PUCCH/SPUCCH reliability for URLLC,” 3GPP TSG RAN WG1 Meeting 92b, Apr. 16-20, 2018, Sanya, China, 10 pages. [cited by applicant]
International Search Report and Written Opinion for International Patent Application No. PCT/IB2020/053153, mailed Jul. 23, 2020, 12 pages. [cited by applicant]
International Preliminary Report on Patentability for International Patent Application No. PCT/IB2020/053153, mailed May 14, 2021, 11 pages. [cited by applicant]