# US 12,225,574 B2 · Priority-dependent uci resource determination > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,225,574 B2 - Document ID: US12225574B2 - Status: Granted - Kind: B2 - Application number: 17/601,255 - Filed: 2020-04-02 - Published: 2022-06-09 - Granted: 2025-02-11 - Earliest claimed: 2019-04-02 - Assignees: Telefonaktiebolaget LM Ericsson (publ) - Applicants: Telefonaktiebolaget LM Ericsson (publ) - Inventors: Jonas Fröberg Olsson; Kittipong Kittichokechai; Yufei Blankenship; Ali Behravan; Bikramjit Singh; Mattias Andersson - Web page: https://patentgrep.com/patent/US12225574B2 ## CPC - H04L 1/0072: {Error control for data other than payload data, e.g. control data} - H04W 72/569: {of the traffic information} - H04L 1/0042: {Encoding specially adapted to other signal generation operation, e.g. in order to reduce transmit distortions, jitter, or to improve signal shape (H04L1/0067 takes precedence)} - H04L 1/007: {Unequal error protection (for format H04L1/0078; for codes per se H03M13/35)} - H04L 1/0075: {Transmission of coding parameters to receiver (H04L1/0023 takes precedence)} - H04L 1/1864: {ARQ related signaling (H04L1/1607 takes precedence)} - H04L 5/0007: {the frequencies being orthogonal, e.g. OFDM(A) or DMT} - H04L 5/0044: {Allocation of payload; Allocation of data channels, e.g. PDSCH or PUSCH} - H04L 5/0053: {Allocation of signalling, i.e. of overhead other than pilot signals} - H04L 5/0055: {Physical resource allocation for ACK/NACK (for physical mapping arrangements in ARQ protocols H04L1/1861)} - H04L 5/0057: {Physical resource allocation for CQI} - H04L 5/0064: {Rate requirement of the data, e.g. scalable bandwidth, data priority} - H04L 5/0091: {Signalling for the administration of the divided path, e.g. signalling of configuration information} - H04W 72/21: in the uplink direction of a wireless link, i.e. towards the network - H04W 72/23: in the downlink direction of a wireless link, i.e. towards a terminal - H04L 1/1896: {ARQ related signaling} - H04L 5/0051: {of dedicated pilots, i.e. pilots destined for a single user or terminal} - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## 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 ### Claim 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. ### Claim 2 (depends on 1) 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. ### Claim 3 (depends on 1) 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. ### Claim 4 (depends on 1) 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. ### Claim 5 (depends on 1) 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. ### Claim 6 (depends on 1) 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. ### Claim 7 (depends on 1) 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. ### Claim 8 (depends on 1) 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. ### Claim 9 (depends on 8) The method of claim 8 wherein the PDSCH priority is indicated in Downlink, DL, scheduling DCI. ### Claim 10 (depends on 9) The method of claim 9 wherein the PDSCH priority is semi-statically configured. ### Claim 11 (depends on 1) 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. ### Claim 12 (depends on 11) The method of claim 11 wherein the A-CSI always has a lowest priority with respect to other UCIs and PUSCHs. ### Claim 13 (depends on 11) The method of claim 11 wherein the priority of the A-CSI is semi-statically configured. ### Claim 14 (depends on 11) 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. ### Claim 15 (depends on 11) 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. ### Claim 16 (depends on 11) 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. ### Claim 17 (depends on 1) 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. ### Claim 18 (depends on 17) The method of claim 17 wherein different configurations carry different traffic with different reliabilities or priorities. ### Claim 19 (depends on 1) 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. ### Claim 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. ### Claim 21 (depends on 20) 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. ### Claim 22 (depends on 21) 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. ### Claim 23 (depends on 21) 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. ### Claim 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. ### Claim 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.