WO2022084178A1

WO2022084178A1 - Pucch resource determination for multiplexed low priority and high priority uplink control information

Info

Publication number: WO2022084178A1
Application number: PCT/EP2021/078597
Authority: WO
Inventors: Kari Hooli; Matha DEGHEL; Klaus Hugl; Nhat-Quang NHAN; Zexian Li
Original assignee: Nokia Technologies Oy
Priority date: 2020-10-22
Filing date: 2021-10-15
Publication date: 2022-04-28
Also published as: EP4233436A1

Abstract

A method comprising: receiving a configuration for reporting high-priority uplink control information; receiving at least one downlink assignment; generating high-priority uplink control information; generating low-priority uplink control information; determining a payload size of uplink control information for transmission, wherein the payload size of the uplink control information for transmission is based, at least partially, on a payload size of the high-priority uplink control information; selecting an uplink resource set based, at least partially, on the determined payload size and at least one of: the received configuration, or a received indication value; selecting a resource of the selected uplink resource set based, at least partially, on a resource index associated with the high-priority uplink control information; and transmitting at least one of: the high-priority uplink control information, or the low-priority uplink control information based, at least partially, on the received configuration and the selected resource.

Description

PUCCH RESOURCE DETERMINATION FOR MULTIPLEXED LOW PRIORITY

AND HIGH PRIORITY UPLINK CONTROL INFORMATION

BACKGROUND

Technical Field

[0001] The example and non-limiting embodiments relate generally to communications and, more particularly, to multiplexing of high-priority uplink transmission ( s ) with low- priority uplink transmission ( s ) .

Brief Description of Prior Developments

[0002] It is known, for intra-user equipment collision handling at the physical layer, in case of high-priority uplink transmission overlapping with low-priority UL transmission, to drop the low- priority uplink transmission.

SUMMARY

[0003] The following summary is merely intended to be illustrative. The summary is not intended to limit the scope of the claims .

[0004] In accordance with one aspect, a method comprising: receiving a configuration for reporting high-priority uplink control information; receiving at least one downlink assignment; generating high-priority uplink control information; generating low-priority uplink control information; determining a payload size of uplink control information for transmission, wherein the payload size of the uplink control information for transmission is based, at least partially, on a payload size of the high-priority uplink control information; selecting an uplink resource set based, at least partially, on the determined payload size and at least one of : the received configuration, or a received indication value; selecting a resource of the selected uplink resource set based, at least partially, on a resource index associated with the high-priority uplink control information; and transmitting at least one of : the high-priority uplink control information, or the low-priority uplink control information based, at least partially, on the received configuration and the selected resource.

[0005] In accordance with one aspect, an apparatus comprising: at least one processor; and at least one memory and computer program code, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to: receive a configuration for reporting high- priority uplink control information; receive at least one downlink assignment; generate high-priority uplink control information; generate low-priority uplink control information; determine a payload size of uplink control information for transmission, wherein the payload size of the uplink control information for transmission is based, at least partially, on a payload size of the high-priority uplink control information; select an uplink resource set based, at least partially, on the determined payload size and at least one of: the received configuration, or a received indication value; select a resource of the selected uplink resource set based, at least partially, on a resource index associated with the high-priority uplink control information; and transmit at least one of : the high-priority uplink control information, or the low-priority uplink control information based, at least partially, on the received configuration and the selected resource. [0006] In accordance with one aspect, an apparatus comprising means for performing: receiving a configuration for reporting high-priority uplink control information; receiving at least one downlink assignment; generating high-priority uplink control information; generating low-priority uplink control information; determining a payload size of uplink control information for transmission, wherein the payload size of the uplink control information for transmission is based, at least partially, on a payload size of the high-priority uplink control information; selecting an uplink resource set based, at least partially, on the determined payload size and at least one of : the received configuration, or a received indication value; selecting a resource of the selected uplink resource set based, at least partially, on a resource index associated with the high-priority uplink control information; and transmitting at least one of : the high-priority uplink control information, or the low-priority uplink control information based, at least partially, on the received configuration and the selected resource.

[0007] In accordance with one aspect, a non-transitory computer-readable medium comprising program instructions stored thereon which, when executed with at least one processor, cause the at least one processor to: receive a configuration for reporting high-priority uplink control information; receive at least one downlink assignment; generate high-priority uplink control information; generate low-priority uplink control information; determine a payload size of uplink control information for transmission, wherein the payload size of the uplink control information for transmission is based, at least partially, on a payload size of the high-priority uplink control information; select an uplink resource set based, at least partially, on the determined payload size and at least one of: the received configuration, or a received indication value; select a resource of the selected uplink resource set based, at least partially, on a resource index associated with the high-priority uplink control information; and transmit at least one of : the high- priority uplink control information, or the low-priority uplink control information based, at least partially, on the received configuration and the selected resource.

[0008] In accordance with one aspect, a method comprising: receiving, at a user equipment, at least one downlink assignment, wherein the at least one downlink assignment comprises an indication of whether low-priority uplink control information is to be multiplexed on a high-priority uplink control information transmission; determining an uplink control information payload to be transmitted in an uplink channel based, at least partially, on the at least one downlink assignment; at least one of: where the indication indicates that the low-priority uplink control information is not to be multiplexed on the high-priority uplink control information transmission, determining a high-priority hybrid automatic repeat request codebook, an uplink resource set, and a number of resource blocks for the high-priority uplink control information transmission based on a first set of rules, or where the indication indicates that the low-priority uplink control information is to be multiplexed on the high-priority uplink control information transmission, determining the high- priority hybrid automatic repeat request codebook based on the first set of rules, and determining the uplink resource set and the number of resource blocks for the high-priority uplink control information transmission based on a second set of rules, wherein the second set of rules is based, at least partially, on the indication; and performing transmission of the high-priority uplink control information transmission based on the determined high-priority hybrid automatic repeat request codebook, the determined uplink resource set, and the determined number of resource blocks.

[0009] In accordance with one aspect, an apparatus comprising: at least one processor; and at least one non- transitory memory and computer program code, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to: receive at least one downlink assignment, wherein the at least one downlink assignment comprises an indication of whether low-priority uplink control information is to be multiplexed on a high-priority uplink control information transmission; determine an uplink control information payload to be transmitted in an uplink channel based, at least partially, on the at least one downlink assignment; at least one of: where the indication indicates that the low-priority uplink control information is not to be multiplexed on the high-priority uplink control information transmission, determine a high-priority hybrid automatic repeat request codebook, an uplink resource set, and a number of resource blocks for the high-priority uplink control information transmission based on a first set of rules, or where the indication indicates that the low-priority uplink control information is to be multiplexed on the high-priority uplink control information transmission, determine the high-priority hybrid automatic repeat request codebook based on the first set of rules, and determining the uplink resource set and the number of resource blocks for the high-priority uplink control information transmission based on a second set of rules, wherein the second set of rules is based, at least partially, on the indication; and perform transmission of the high-priority uplink control information transmission based on the determined high-priority hybrid automatic repeat request codebook, the determined uplink resource set, and the determined number of resource blocks.

[0010] In accordance with one aspect, an apparatus comprising means for performing: receiving at least one downlink assignment, wherein the at least one downlink assignment comprises an indication of whether low-priority uplink control information is to be multiplexed on a high-priority uplink control information transmission; determining an uplink control information payload to be transmitted in an uplink channel based, at least partially, on the at least one downlink assignment; at least one of: where the indication indicates that the low-priority uplink control information is not to be multiplexed on the high-priority uplink control information transmission, determining a high-priority hybrid automatic repeat request codebook, an uplink resource set, and a number of resource blocks for the high-priority uplink control information transmission based on a first set of rules, or where the indication indicates that the low-priority uplink control information is to be multiplexed on the high-priority uplink control information transmission, determining the high- priority hybrid automatic repeat request codebook based on the first set of rules, and determining the uplink resource set and the number of resource blocks for the high-priority uplink control information transmission based on a second set of rules, wherein the second set of rules is based, at least partially, on the indication; and performing transmission of the high-priority uplink control information transmission based on the determined high-priority hybrid automatic repeat request codebook, the determined uplink resource set, and the determined number of resource blocks.

[0011] In accordance with one aspect, a non-transitory computer-readable medium comprising program instructions stored thereon which, when executed with at least one processor, cause the at least one processor to: receive at least one downlink assignment, wherein the at least one downlink assignment comprises an indication of whether low-priority uplink control information is to be multiplexed on a high-priority uplink control information transmission; determine an uplink control information payload to be transmitted in an uplink channel based, at least partially, on the at least one downlink assignment; at least one of: where the indication indicates that the low-priority uplink control information is not to be multiplexed on the high-priority uplink control information transmission, determine a high-priority hybrid automatic repeat request codebook, an uplink resource set, and a number of resource blocks for the high-priority uplink control information transmission based on a first set of rules, or where the indication indicates that the low-priority uplink control information is to be multiplexed on the high-priority uplink control information transmission, determine the high-priority hybrid automatic repeat request codebook based on the first set of rules, and determining the uplink resource set and the number of resource blocks for the high-priority uplink control information transmission based on a second set of rules, wherein the second set of rules is based, at least partially, on the indication; and perform transmission of the high-priority uplink control information transmission based on the determined high-priority hybrid automatic repeat request codebook, the determined uplink resource set, and the determined number of resource blocks. [0012] In accordance with one aspect, a method comprising: transmitting, to a user equipment, a configuration for reporting high-priority uplink control information; transmitting at least one first downlink assignment; transmitting downlink data corresponding to the at least one first downlink assignment; determining an uplink resource set based, at least partially, on a payload size of expected high-priority uplink control information and a payload size of expected low-priority uplink control information; determining an indication for the determined uplink resource set; selecting a resource of the determined uplink resource set; determining a resource index associated with the selected resource; transmitting at least one second downlink assignment, wherein the at least one second downlink assignment comprises the determined indication and the determined resource index; transmitting downlink data corresponding to the at least one second downlink assignment; and receiving uplink data, from the user equipment, with the selected resource, wherein the received uplink data is associated with the downlink data corresponding to the at least one first downlink assignment and the downlink data corresponding to the at least one second downlink assignment .

[0013] In accordance with one aspect, an apparatus comprising: at least one processor; and at least one non- transitory memory and computer program code, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to: transmit a configuration for reporting high-priority uplink control information; transmit at least one first downlink assignment; transmit downlink data corresponding to the at least one first downlink assignment; determine an uplink resource set based, at least partially, on a payload size of expected high-priority uplink control information and a payload size of expected low-priority uplink control information; determine an indication for the determined uplink resource set; select a resource of the determined uplink resource set; determine a resource index associated with the selected resource; transmit at least one second downlink assignment, wherein the at least one second downlink assignment comprises the determined indication and the determined resource index; transmit downlink data corresponding to the at least one second downlink assignment; and receive uplink data, from the user equipment, with the selected resource, wherein the received uplink data is associated with the downlink data corresponding to the at least one first downlink assignment and the downlink data corresponding to the at least one second downlink assignment.

[0014] In accordance with one aspect, an apparatus comprising means for performing: transmitting a configuration for reporting high-priority uplink control information; transmitting at least one first downlink assignment; transmitting downlink data corresponding to the at least one first downlink assignment; determining an uplink resource set based, at least partially, on a payload size of expected high-priority uplink control information and a payload size of expected low-priority uplink control information; determining an indication for the determined uplink resource set; selecting a resource of the determined uplink resource set; determining a resource index associated with the selected resource; transmitting at least one second downlink assignment, wherein the at least one second downlink assignment comprises the determined indication and the determined resource index; transmitting downlink data corresponding to the at least one second downlink assignment; and receiving uplink data, from the user equipment, with the selected resource, wherein the received uplink data is associated with the downlink data corresponding to the at least one first downlink assignment and the downlink data corresponding to the at least one second downlink assignment .

[0015] In accordance with one aspect, a non-transitory computer-readable medium comprising program instructions stored thereon which, when executed with at least one processor, cause the at least one processor to: transmit a configuration for reporting high-priority uplink control information; transmit at least one first downlink assignment; transmit downlink data corresponding to the at least one first downlink assignment; determine an uplink resource set based, at least partially, on a payload size of expected high-priority uplink control information and a payload size of expected low-priority uplink control information; determine an indication for the determined uplink resource set; select a resource of the determined uplink resource set; determine a resource index associated with the selected resource; transmit at least one second downlink assignment, wherein the at least one second downlink assignment comprises the determined indication and the determined resource index; transmit downlink data corresponding to the at least one second downlink assignment; and receive uplink data, from the user equipment, with the selected resource, wherein the received uplink data is associated with the downlink data corresponding to the at least one first downlink assignment and the downlink data corresponding to the at least one second downlink assignment.

[0016] In accordance with one aspect, a method comprising: transmitting, to a user equipment, a configuration for reporting high-priority uplink control information, wherein the configuration comprises an indication of at least one semi-static reservation value; transmitting at least one first downlink assignment; transmitting downlink data corresponding to the at least one first downlink assignment; determining an uplink resource set based, at least partially, on a payload size of expected high-priority uplink control information and the at least one semi-static reservation value; selecting a resource of the determined uplink resource set; determining a resource index associated with the selected resource; transmitting at least one second downlink assignment, wherein the at least one second downlink assignment comprises an indication to perform uplink control information multiplexing, and the determined resource index; transmitting downlink data corresponding to the at least one second downlink assignment; and receiving uplink data, from the user equipment, with the selected resource, wherein the received uplink data is associated with the downlink data corresponding to the at least one first downlink assignment and the downlink data corresponding to the at least one second downlink assignment .

[0017] In accordance with one aspect, an apparatus comprising: at least one processor; and at least one non- transitory memory and computer program code, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to: transmit a configuration for reporting high-priority uplink control information, wherein the configuration comprises an indication of at least one semi-static reservation value; transmit at least one first downlink assignment; transmit downlink data corresponding to the at least one first downlink assignment; determine an uplink resource set based, at least partially, on a payload size of expected high- priority uplink control information and the at least one semi- static reservation value; select a resource of the determined uplink resource set; determine a resource index associated with the selected resource; transmit at least one second downlink assignment, wherein the at least one second downlink assignment comprises an indication to perform uplink control information multiplexing, and the determined resource index; transmit downlink data corresponding to the at least one second downlink assignment; and receive uplink data, from the user equipment, with the selected resource, wherein the received uplink data is associated with the downlink data corresponding to the at least one first downlink assignment and the downlink data corresponding to the at least one second downlink assignment.

[0018] In accordance with one aspect, an apparatus comprising means for performing: transmitting a configuration for reporting high-priority uplink control information, wherein the configuration comprises an indication of at least one semi-static reservation value; transmitting at least one first downlink assignment; transmitting downlink data corresponding to the at least one first downlink assignment; determining an uplink resource set based, at least partially, on a payload size of expected high-priority uplink control information and the at least one semi-static reservation value; selecting a resource of the determined uplink resource set; determining a resource index associated with the selected resource; transmitting at least one second downlink assignment, wherein the at least one second downlink assignment comprises an indication to perform uplink control information multiplexing, and the determined resource index; transmitting downlink data corresponding to the at least one second downlink assignment; and receiving uplink data, from the user equipment, with the selected resource, wherein the received uplink data is associated with the downlink data corresponding to the at least one first downlink assignment and the downlink data corresponding to the at least one second downlink assignment .

[0019] In accordance with one aspect, a non-transitory computer-readable medium comprising program instructions stored thereon which, when executed with at least one processor, cause the at least one processor to: transmit a configuration for reporting high-priority uplink control information, wherein the configuration comprises an indication of at least one semi-static reservation value; transmit at least one first downlink assignment; transmit downlink data corresponding to the at least one first downlink assignment; determine an uplink resource set based, at least partially, on a payload size of expected high- priority uplink control information and the at least one semi- static reservation value; select a resource of the determined uplink resource set; determine a resource index associated with the selected resource; transmit at least one second downlink assignment, wherein the at least one second downlink assignment comprises an indication to perform uplink control information multiplexing, and the determined resource index; transmit downlink data corresponding to the at least one second downlink assignment; and receive uplink data, from the user equipment, with the selected resource, wherein the received uplink data is associated with the downlink data corresponding to the at least one first downlink assignment and the downlink data corresponding to the at least one second downlink assignment. [0020] In accordance with one aspect, a method comprising: transmitting, to a user equipment, a configuration for reporting high-priority uplink control information; transmitting at least one first downlink assignment; transmitting downlink data corresponding to the at least one first downlink assignment; determining an uplink resource set based, at least partially, on a payload size of expected high-priority uplink control information and a payload size of expected low-priority uplink control information; selecting a resource of the determined uplink resource set; determining a resource index associated with the selected resource; transmitting at least one second downlink assignment, wherein the at least one second downlink assignment comprises the determined resource index, and a joint indication to perform uplink control information multiplexing and for a downlink assignment index associated with, at least, the at least one first downlink assignment; transmitting downlink data corresponding to the at least one second downlink assignment; and receiving uplink data, from the user equipment, with the selected resource, wherein the received uplink data is associated with the downlink data corresponding to the at least one first downlink assignment and the downlink data corresponding to the at least one second downlink assignment .

[0021] In accordance with one aspect, an apparatus comprising: at least one processor; and at least one non- transitory memory and computer program code, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to: transmit a configuration for reporting high-priority uplink control information; transmit at least one first downlink assignment; transmit downlink data corresponding to the at least one first downlink assignment; determine an uplink resource set based, at least partially, on a payload size of expected high-priority uplink control information and a payload size of expected low-priority uplink control information; select a resource of the determined uplink resource set; determine a resource index associated with the selected resource; transmit at least one second downlink assignment, wherein the at least one second downlink assignment comprises the determined resource index, and a joint indication to perform uplink control information multiplexing and for a downlink assignment index associated with, at least, the at least one first downlink assignment; transmit downlink data corresponding to the at least one second downlink assignment; and receive uplink data, from the user equipment, with the selected resource, wherein the received uplink data is associated with the downlink data corresponding to the at least one first downlink assignment and the downlink data corresponding to the at least one second downlink assignment.

[0022] In accordance with one aspect, an apparatus comprising means for performing: transmitting a configuration for reporting high-priority uplink control information; transmitting at least one first downlink assignment; transmitting downlink data corresponding to the at least one first downlink assignment; determining an uplink resource set based, at least partially, on a payload size of expected high-priority uplink control information and a payload size of expected low-priority uplink control information; selecting a resource of the determined uplink resource set; determining a resource index associated with the selected resource; transmitting at least one second downlink assignment, wherein the at least one second downlink assignment comprises the determined resource index, and a joint indication to perform uplink control information multiplexing and for a downlink assignment index associated with, at least, the at least one first downlink assignment; transmitting downlink data corresponding to the at least one second downlink assignment; and receiving uplink data, from the user equipment, with the selected resource, wherein the received uplink data is associated with the downlink data corresponding to the at least one first downlink assignment and the downlink data corresponding to the at least one second downlink assignment .

[0023] In accordance with one aspect, a non-transitory computer-readable medium comprising program instructions stored thereon which, when executed with at least one processor, cause the at least one processor to: transmit a configuration for reporting high-priority uplink control information; transmit at least one first downlink assignment; transmit downlink data corresponding to the at least one first downlink assignment; determine an uplink resource set based, at least partially, on a payload size of expected high-priority uplink control information and a payload size of expected low-priority uplink control information; select a resource of the determined uplink resource set; determine a resource index associated with the selected resource; transmit at least one second downlink assignment, wherein the at least one second downlink assignment comprises the determined resource index, and a joint indication to perform uplink control information multiplexing and for a downlink assignment index associated with, at least, the at least one first downlink assignment; transmit downlink data corresponding to the at least one second downlink assignment; and receive uplink data, from the user equipment, with the selected resource, wherein the received uplink data is associated with the downlink data corresponding to the at least one first downlink assignment and the downlink data corresponding to the at least one second downlink assignment.

BRIEF DESCRIPTION OF THE DRAWINGS

[0024] The foregoing aspects and other features are explained in the following description, taken in connection with the accompanying drawings, wherein:

[0025] limiting exemplary system in which the exemplary embodiments may be practiced;

[0026] FIG. 2 is a table illustrating features as described herein;

[0027] FIG. 3 is a table illustrating features as described herein;

[0028] FIG. 4 is a table illustrating features as described herein;

[0029] FIG. 5 is a flowchart illustrating steps as described herein;

[0030] FIG. 6 is a flowchart illustrating steps as described herein;

[0031] FIG. 7 is a flowchart illustrating steps as described herein;

[0032] FIG. 8 is a flowchart illustrating steps as described herein; [0033] FIG. 9 is a flowchart illustrating steps as described herein;

[0034] FIG. 10 is a flowchart illustrating steps as described herein;

[0035] FIG. 11 is a flowchart illustrating steps as described herein; and

[0036] FIG. 12 is a flowchart illustrating steps as described herein .

DETAILED DESCRIPTION OF EMBODIMENTS

[0037] The following abbreviations that may be found in the specification and/or the drawing figures are defined as follows:

3 GPP third generation partnership project

5G fifth generation

5GC 5G core network

ACK acknowledgement

AMF access and mobility management function

A/N ACK/NACK

BWP bandwidth part

CB codebook

CBG code block group

CG configured grant

CSI channel state information

CU central unit

DAI downlink assignment index

DCI downlink control information

DG dynamic grant DL downlink

DM-RS demodulation reference signal

DU distributed unit eNB (or eNodeB) evolved Node B (e.g., an LTE base station)

EN-DC E-UTRA-NR dual connectivity en-gNB or En-gNB node providing NR user plane and control plane protocol terminations towards the UE, and acting as secondary node in EN-DC

E-UTRA evolved universal terrestrial radio access, i.e., the LTE radio access technology gNB (or gNodeB) base station for 5G/NR, i.e., a node providing NR user plane and control plane protocol terminations towards the UE, and connected via the NG interface to the 5GC

HARQ hybrid automatic repeat request

HP high priority

I/F interface

IIOT industrial Internet of Things

LI layer 1

LP low priority

LTE long term evolution

MAC medium access control

MME mobility management entity

NACK negative acknowledgement ng or NG new generation ng-eNB or NG-eNB new generation eNB

NR new radio

N/W or NW network

PDCCH physical downlink control channel

PDCP packet data convergence protocol

PDSCH physical downlink shared channel

PHY physical layer PRI PUCCH resource index/indicator

PUCCH physical uplink control channel

PUSCH physical uplink shared channel

RAN radio access network

RB resource block

RE resource element

RF radio frequency

RLC radio link control

RS reference signal

RRH remote radio head

RRC radio resource control

RU radio unit

Rx receiver

SCH shared channel

SDAP service data adaptation protocol

SGW serving gateway

SMF session management function

SR scheduling request

TB transport block

Tx transmitter

UCI uplink control information

UE user equipment (e.g., a wireless, typically mobile device)

UL uplink

UPF user plane function

URLLC ultra reliable low latency communication

WI work item

[ 0038 ] Turning to FI G . 1 , thi s f igure shows a block di agram o f one pos sible and non-limiting exampl e in which the examples may be practiced. A user equipment (UE) 110, radio access network (RAN) node 170, and network element (s) 190 are illustrated. In the example of FIG. 1, the user equipment (UE) 110 is in wireless communication with a wireless network 100. A UE is a wireless device that can access the wireless network 100. The UE 110 includes one or more processors 120, one or more memories 125, and one or more transceivers 130 interconnected through one or more buses 127. Each of the one or more transceivers 130 includes a receiver, Rx, 132 and a transmitter, Tx, 133. The one or more buses 127 may be address, data, or control buses, and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, fiber optics or other optical communication equipment, and the like. The one or more transceivers 130 are connected to one or more antennas 128. The one or more memories 125 include computer program code 123. The UE 110 includes a module 140, comprising one of or both parts 140- 1 and/or 140-2, which may be implemented in a number of ways. The module 140 may be implemented in hardware as module 140-1, such as being implemented as part of the one or more processors 120. The module 140-1 may be implemented also as an integrated circuit or through other hardware such as a programmable gate array. In another example, the module 140 may be implemented as module 140- 2, which is implemented as computer program code 123 and is executed by the one or more processors 120. For instance, the one or more memories 125 and the computer program code 123 may be configured to, with the one or more processors 120, cause the user equipment 110 to perform one or more of the operations as described herein. The UE 110 communicates with RAN node 170 via a wireless link 111. [0039] The RAN node 170 in this example is a base station that provides access by wireless devices such as the UE 110 to the wireless network 100. The RAN node 170 may be, for example, a base station for 5G, also called New Radio (NR) . In 5G, the RAN node 170 may be a NG-RAN node, which is defined as either a gNB or a ng-eNB. A gNB is a node providing NR user plane and control plane protocol terminations towards the UE, and connected via the NG interface to a 5GC (such as, for example, the network element (s) 190) . The ng-eNB is a node providing E-UTRA user plane and control plane protocol terminations towards the UE, and connected via the NG interface to the 5GC. The NG-RAN node may include multiple gNBs, which may also include a central unit (CU) (gNB-CU) 196 and distributed unit(s) (DUs) (gNB-DUs) , of which DU 195 is shown. Note that the DU may include or be coupled to and control a radio unit (RU) . The gNB-CU is a logical node hosting RRC, SDAP and PDCP protocols of the gNB or RRC and PDCP protocols of the en-gNB that controls the operation of one or more gNB-DUs. The gNB-CU terminates the Fl interface connected with the gNB-DU. The Fl interface is illustrated as reference 198, although reference 198 also illustrates a link between remote elements of the RAN node 170 and centralized elements of the RAN node 170, such as between the gNB-CU 196 and the gNB-DU 195. The gNB-DU is a logical node hosting RLC, MAC and PHY layers of the gNB or en-gNB, and its operation is partly controlled by gNB-CU. One gNB-CU supports one or multiple cells. One cell is supported by only one gNB-DU. The gNB-DU terminates the Fl interface 198 connected with the gNB-CU. Note that the DU 195 is considered to include the transceiver 160, e.g. , as part of a RU, but some examples of this may have the transceiver 160 as part of a separate RU, e.g. , under control of and connected to the DU 195. The RAN node 170 may also be an eNB (evolved NodeB) base station, for LTE (long term evolution) , or any other suitable base station or node.

[0040] The RAN node 170 includes one or more processors 152, one or more memories 155, one or more network interfaces (N/W I/F(s) ) 161, and one or more transceivers 160 interconnected through one or more buses 157. Each of the one or more transceivers 160 includes a receiver, Rx, 162 and a transmitter, Tx, 163. The one or more transceivers 160 are connected to one or more antennas 158. The one or more memories 155 include computer program code 153. The CU 196 may include the processor (s) 152, memories 155, and network interfaces 161. Note that the DU 195 may also contain its own memory/memories and processor ( s ) , and/or other hardware, but these are not shown.

[0041] The RAN node 170 includes a module 150, comprising one of or both parts 150-1 and/or 150-2, which may be implemented in a number of ways. The module 150 may be implemented in hardware as module 150-1, such as being implemented as part of the one or more processors 152. The module 150-1 may be implemented also as an integrated circuit or through other hardware such as a programmable gate array. In another example, the module 150 may be implemented as module 150-2, which is implemented as computer program code 153 and is executed by the one or more processors 152. For instance, the one or more memories 155 and the computer program code 153 are configured to, with the one or more processors 152, cause the RAN node 170 to perform one or more of the operations as described herein. Note that the functionality of the module 150 may be distributed, such as being distributed between the DU 195 and the

CU 196, or be implemented solely in the DU 195. [0042] The one or more network interfaces 161 communicate over a network such as via the links 176 and 131. Two or more gNBs 170 may communicate using, e.g. , link 176. The link 176 may be wired or wireless or both and may implement, for example, an Xn interface for 5G, an X2 interface for LTE, or other suitable interface for other standards.

[0043] The one or more buses 157 may be address, data, or control buses, and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, fiber optics or other optical communication equipment, wireless channels, and the like. For example, the one or more transceivers 160 may be implemented as a remote radio head (RRH) 195 for LTE or a distributed unit (DU) 195 for gNB implementation for 5G, with the other elements of the RAN node 170 possibly being physically in a different location from the RRH/DU, and the one or more buses 157 could be implemented in part as, for example, fiber optic cable or other suitable network connection to connect the other elements (e.g. , a central unit (CU) , gNB-CU) of the RAN node 170 to the RRH/DU 195. Reference 198 also indicates those suitable network link (s) .

[0044] It is noted that description herein indicates that "cells" perform functions, but it should be clear that equipment which forms the cell will perform the functions. The cell makes up part of a base station. That is, there can be multiple cells per base station. For example, there could be three cells for a single carrier frequency and associated bandwidth, each cell covering one-third of a 360 degree area so that the single base station's coverage area covers an approximate oval or circle. Furthermore, each cell can correspond to a single carrier and a base station may use multiple carriers. So if there are three 120 degree cells per carrier and two carriers, then the base station has a total of 6 cells .

[0045] The wireless network 100 may include a network element or elements 190 that may include core network functionality, and which provides connectivity via a link or links 181 with a further network, such as a telephone network and/or a data communications network (e.g. , the Internet) . Such core network functionality for 5G may include access and mobility management function (s) (AMF(s) ) and/or user plane functions (UPF(s) ) and/or session management function(s) (SMF(s) ) . Such core network functionality for LTE may include MME (Mobility Management Entity) /SGW (Serving Gateway) functionality. These are merely exemplary functions that may be supported by the network element (s) 190, and note that both 5G and LTE functions might be supported. The RAN node 170 is coupled via a link 131 to a network element 190. The link 131 may be implemented as, e.g. , an NG interface for 5G, or an SI interface for LTE, or other suitable interface for other standards. The network element 190 includes one or more processors 175, one or more memories 171, and one or more network interfaces (N/W I/F(s) ) 180, interconnected through one or more buses 185. The one or more memories 171 include computer program code 173. The one or more memories 171 and the computer program code 173 are configured to, with the one or more processors 175, cause the network element 190 to perform one or more operations.

[0046] The wireless network 100 may implement network virtualization, which is the process of combining hardware and software network resources and network functionality into a single, software-based administrative entity, a virtual network. Network virtualization involves platform virtualization, often combined with resource virtualization. Network virtualization is categorized as either external, combining many networks, or parts of networks, into a virtual unit, or internal, providing network- like functionality to software containers on a single system. Note that the virtualized entities that result from the network virtualization are still implemented, at some level, using hardware such as processors 152 or 175 and memories 155 and 171, and also such virtualized entities create technical effects.

[0047] The computer readable memories 125, 155, and 171 may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor based memory devices, flash memory, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory. The computer readable memories 125, 155, and 171 may be means for performing storage functions. The processors 120, 152, and 175 may be of any type suitable to the local technical environment, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on a multi- core processor architecture, as non-limiting examples. The processors 120, 152, and 175 may be means for performing functions, such as controlling the UE 110, RAN node 170, and other functions as described herein.

[0048] In general, the various embodiments of the user equipment 110 can include, but are not limited to, cellular telephones such as smart phones, tablets, personal digital assistants (PDAs) having wireless communication capabilities, portable computers having wireless communication capabilities, image capture devices such as digital cameras having wireless communication capabilities, gaming devices having wireless communication capabilities, music storage and playback appliances having wireless communication capabilities, Internet appliances permitting wireless Internet access and browsing, tablets with wireless communication capabilities, as well as portable units or terminals that incorporate combinations of such functions.

[0049] Features as described herein generally relate to multiplexing of high-priority (HP) uplink (UL) transmission ( s ) with low-priority (LP) UL transmission ( s ) . Example embodiments of the present disclosure may have application in new radio (NR) industrial Internet of Things (IIoT) scenarios and/or scenarios in which ultra-reliable low-latency communication (URLLC) support is enabled. More particularly, example embodiments of the present disclosure may relate to transmission of hybrid automatic repeat request (HARQ) feedback for physical downlink shared channel (PDSCH) with/while supporting intra-UE multiplexing/prioritization .

[0050] The use of the terms "high-priority HARQ-ACK" and "low- priority HARQ-ACK" are not limiting on the example embodiments of the present disclosure; example embodiments of the present disclosure may be applied with regard to other types of UL transmissions, including but not limited to HARQ-NACK transmissions .

[0051] While the present disclosure describes high-priority and low-priority UL transmissions, additional or different priority levels may be possible for use with example embodiments. For example, there may also be a medium priority UL transmission, and or a first priority level, a second priority level, a third priority level, etc. The use of the terms "high-priority" and "low-priority" are not limiting on the example embodiments of the present disclosure.

[0052] In Rel-16 NR, there were two work items (WIs) directed to providing better support for IIoT/URLLC: URLLC PHY Enhancements and Industrial loT (IIoT) . Each of those WIs mentioned intra-UE multiplexing/prioritization addressing control-data, control- control, and data-data multiplexing/prioritization. For efficient support of intra-UE multiplexing/prioritization, in Rel-16, two levels of physical layer (PHY) priority (i.e. high-priority level 1; low-priority level 0) were introduced for UL data channels, as well as UL control channels. In Rel-16, prioritization is supported (i.e. between channels of different priorities) , but multiplexing between channels associated with different priorities is not supported, as can be seen in the agreement "Summary on UCI enhancements for URLLC," 3GPP TSG RAN WG1 #99, Rl-1913241, Reno, USA, November 18th-22nd, 2019.

[0053] However, as discussed during the Rel-17 WI preparation phase, multiplexing between channels with different priorities may serve to avoid performance degradation, at least in terms of spectral efficiency. The topic of multiplexing between channels associated with different priorities was included as part of the Rel-17 IIoT/URLLC WI . Specifically, the WI on enhanced IIoT and URLLC support for NR was approved in RAN#86 and revised in RAN#88e [RP-201310] .

[0054] In the Rel-17 discussions on this topic, which started in RANl#102e, it has been agreed to study multiplexing (of high- priority channel and low-priority channel) for several scenarios of overlapping channels. The scenario where a high-priority HARQ- ACK ( wi th/wi thout SR (scheduling request) ) overlaps with a low priority HARQ-ACK is one such scenario, and was mentioned in the RANl#102-e agreement "Summary#1 of email thread [102-e-NR- IIOT_URLLC_enh-04] , " 3GPP TSG RAN WG1 #102-e, Rl-2007075, e- Meeting, August 17th-28th, 2020.

[0055] Similar agreements were made considering overlapping

PUSCH and PUCCH carrying HARQ-ACK with different priorities.

[0056] When UE has received the dedicated physical uplink control channel (PUCCH) resource configuration, the PUCCH resource determination for HARQ-ACK feedback may occur in three steps. In a first step, the UE may be configured with up to 4 PUCCH resource sets, each set comprising one or more configured PUCCH resources. For each set, a maximum payload may be predetermined or configured. In an example, the first PUCCH resource set may be limited to carry up to 2 uplink control information (UCI) bits. The UE may select a PUCCH resource set based on the number of UCI bits to be transmitted, i.e. , the UCI payload size. In a second step, a downlink (DL) assignment may contain a PUCCH resource indicator (PRI) field, and the UE may select a PUCCH resource from the selected PUCCH resource set based on the PRI value. In a third step, where the PUCCH format is PUCCH format 2 or 3, the UE may determine a number of resource blocks (RBs) used in the transmission based on the UCI payload and a configured maximum code rate. The number of RBs may be determined to be a smallest number of RBs for which the code rate is below the maximum code rate, and may be capped/limited by the number of RBs configured for the selected PUCCH resource. [0057] It may be noted that two of the above steps for PUCCH resource determination for HARQ-ACK feedback (i.e. steps 1 and 3) may depend on the UCI payload size. Error in determining the number of low-priority HARQ-ACKs to be reported may cause UE selection of a different PUCCH resource set, or use of a smaller and/or different number of RBs, for the multiplexed HARQ-ACK feedback than what a gNB would expect/monitor based on the (expected) UCI payload size.

[0058] In NR Rel-15, two HARQ-ACK codebook types may be determined for HARQ-ACK feedback. A Type 1 codebook (CB) may be determined based on radio resource control (RRC) configured parameters, such as a set of slot timing values KI, a physical downlink shared channel (PDSCH) time domain allocation list, a semi-static UL/DL configuration, etc. As a result of determining the codebook based on RRC configured parameters, the Type 1 codebook (CB size and A/N (positive acknowledgement/negative acknowledgement) ordering within the Type 1 CB) may be reliably determined. However, as the CB does not depend on the actual PDSCH scheduling, the CB size may typically be larger than needed.

[0059] A Type 2 codebook may be determined based on the scheduled DL assignment ( s ) . The CB size may be dimensioned efficiently when determined based on the DL assignment ( s ) , but there is a risk of codebook determination error if the UE misses one or more DL assignments. To mitigate the error, a counter downlink assignment index (DAI) and, possibly, a total DAI may be included in the DL assignment ( s ) . The DAI may be a 2-bit counter of PDSCHs/downlink data transmitted/scheduled to the UE, with HARQ-ACK to be reported in the same codebook, up to the symbol on which the DL assignment with the DAI is transmitted. Codebook determination errors may occur when the UE misses the last DL assignment associated to the codebook, or when the UE misses 4 consecutive DL assignments. Codebook determination errors caused by the UE missing the last DL assignment may be more common than codebook determination errors caused by the UE missing 4 consecutive DL assignments. Example embodiments of the present disclosure may assume a case in which a Type 2 CB is used for LP HARQ-ACK.

[0060] Example embodiments of the present disclosure may enable multiplexing UCI with different priorities. The UCI may comprise HARQ-ACK, scheduling request (SR) , and/or channel state information (CSI) . In an URLLC scenario, for example, multiplexing should not impact the performance of the high-priority channel. In other words, in an example, multiplexing a high-priority HARQ- ACK and a low-priority UCI should not degrade the performance of high-priority HARQ-ACK.

[0061] Use of the term HARQ-ACK in the present disclosure should not be regarded as limiting the scope of the example embodiments to scenarios in which positive acknowledgements with different priorities are to be multiplexed and transmitted together. For example, it may be possible that a negative acknowledgement is multiplexed together with a positive acknowledgement, each with a different priority, using example embodiments of the present disclosure. In another example, it may be possible that negative acknowledgements with different priorities are multiplexed together using example embodiments of the present disclosure.

[0062] A low-priority UCI may comprise HARQ-ACK, SR and, possibly, CSI. The payload size for SR and CSI may be determined based on RRC configuration and, accordingly, may be sufficiently reliable. However, an error may occur in the determination of the Type 2 HARQ-ACK CB size, as discussed above. Example embodiments of the present disclosure may assume that determination of a high- priority HARQ-ACK codebook size is sufficiently reliable. Accordingly, example embodiments of the present disclosure may have the technical effect of addressing low-priority HARQ-ACK codebook errors that may impact the multiplexing of low-priority and high-priority HARQ-ACK.

[0063] Two types of low-priority HARQ-ACK errors may be considered with regard to use of a Type 2 CB . A first type of error may be that the UE may miss the last DL assignment, causing erroneous/incorrect determination of a low-priority HARQ-ACK codebook size. A second type of error may be that the UE may be scheduled with a couple of low-priority DL assignments and fails to detect all of them. In this situation, the UE may, accordingly, not report any low-priority HARQ-ACK feedback. For URLLC with target reliability of 99.99999%, the probability of missing up to 3 DL assignments may be worth considering.

[0064] With regard to each of these types of low-priority HARQ- ACK errors, error in the determination of the number of low- priority HARQ-ACK bits may cause problems in the decoding of uplink control information (e.g. at a gNB) . However, such decoding problems may be solved by, for example, separately encoding low- priority and high-priority UCI and implementing appropriate rules for rate matching. Accordingly, it may be assumed that HARQ-ACK codebooks are determined separately for low-priority and high- priority HARQ-ACK. [0065] It should also be noted that error in low-priority HARQ- ACK PUCCH resource determination, particularly with regard to the UCI payload size, may cause selection of a different PUCCH resource set, or use of a smaller number of RBs for the multiplexed HARQ- ACK feedback, than what a gNB may expect, given the true/expected UCI payload size.

[0066] Example embodiments of the present disclosure may have the technical effect of enabling avoidance of a UE/gNB discrepancy/error in the determination of the PUCCH resource and RBs used by the UE for transmitting UCI containing both high priority and low priority HARQ-ACK. In example embodiments of the present disclosure, a PUCCH resource set and/or the number of RBs used for UL transmission of HARQ-ACK may be determined at the UE based, at least partially, on a specific indication for multiplexed high-priority and low-priority HARQ-ACK. The determination of the PUCCH resource set and/or number of RBs may also be based on detected DL assignments and RRC configurations for SR, CSI, PUCCH resource sets and/or PUCCH resources. Three main example embodiments will be discussed in the following disclosure (Alternative 1, Alternative 2, and Alternative 3) . Variations of these example embodiments may also be presented.

[0067] As specified in Rel-16, a UE may be configured with separate PUCCH resource configurations for LP and HP UCI. In principle, the multiplexed LP and HP UCI may use PUCCH resources defined by: a LP PUCCH resource configuration; a HP PUCCH resource configuration; both resource configurations using specific additional rules for resource selection; or, alternatively, a third PUCCH resource configuration specific for multiplexed LP and HP UCI. Example embodiments of the present disclosure may be implemented where the HP PUCCH resource configuration is used for multiplexed LP and HP UCI. However, this is not limiting; the other PUCCH resource options may potentially be used with example embodiments of the present disclosure.

[0068] A PUCCH resource set of available PUCCH resource sets may be determined as described above (i.e. according to three steps) . In case of multiplexing of LP and HP UCI on PUCCH (which may, in an example, be dynamically indicated) , in an example embodiment each PUCCH resource set configuration available for the multiplexing may contain maxPayloadMinus1 , which may provide the maximum UCI payload size for the PUCCH resource set. If exceeded, the next PUCCH resource set (available for HP & LP UCI multiplexing) , if configured, may be used. In other words, if the UCI payload has a size that exceeds the maxPayloadMinusl indicated for a first PUCCH resource set, a second PUCCH resource set may be used instead; in this way, the PUCCH resource sets may be considered nested, or as being part of a hierarchy defined by maxPayloadMinusl values.

[0069] In an alternative example embodiment, multiplexed LP and HP UCI may use separate encoding with different maximum code rates (provided by maxCodeRate) . In an example embodiment, the PUCCH resource set may be selected for multiplexed LP and HP UCI by comparing an effective HP UCI payload size against the HP UCI payload limits configured to the HP PUCCH resource set. The effective HP UCI payload may _I,_eff = O_UCI,_HP +

or, alternatively, as where

the latter alternative takes into account the mapping of encoded HP UCI and LP UCI to separate symbols. In the equations, is

the ceiling function, O_UCI,_x and r_x are, respectively, the number of UCI information bits and maximum code rate for UCI with priority x (e.g. HP or LP) , and Q_m is the PUCCH modulation order of 2.

[0070] It may be noted that, in 3GPP specification notation, LP corresponds to PHY priority "0" and HP corresponds to PHY priority "1", i.e. 'HP' could be replaced with priority index '1' and 'LP' with priority index '0' to follow 3GPP notation.

[0071] Alternative 1 will now be described with reference to FIGs. 2-6. In Alternative 1, a specific indication that HP and LP HARQ-ACK are to be multiplexed may be defined based on the number of RBs 'n' and/or on the PUCCH resource set index 'm' to be used in the PUCCH transmission. The indication of multiplexing may be dynamic and may be included on the HP DL assignment. Variations for this indication of multiplexing will now be presented.

[0072] In Option A, a value 'm' may be included in the DL assignment for HP PDSCH. The dynamic indication may be derived using the function "m mod 2", where 'm' corresponds to the index of the PUCCH resource set m ∈ {0,...,M- 1} for M available PUCCH resource sets (i.e. indication of PUCCH resource set only) . All RBs configured for the PUCCH resource of the resource set (which may be indicated by PRI ) may be used (and not adjusted based on HP+LP UCI payload) to transmit (mul tiplexed/combined) HP+LP UCI .

[0073] In Option B, the indication may be derived using the function "n₀ mod 2", where "n₀ = n + is an ordered

index of the used RB amount n, containing indication of also PUCCH resource set 'm' . N_i is the number of different RB combinations used (for different UCI payloads) in PUCCH resource set i. [0074] In an example embodiment according to Option B, each index value 'n₀' may correspond to a unique combination of the number of used RBs 'n' and PUCCH resource set 'm' . Indexes may be ordered in a way that these combinations are used with increasing payload of the combined LP and HP UCI . Referring now to FIG. 2, illustrated is a table demonstrating an example of an ordered index n₀ and corresponding combinations of the numbers of used RBs 'n' and

PUCCH resource set 'm' . The PUCCH resource configuration may be the same as that illustrated in FIG. 3, discussed below.

[0075] Referring now to FIG. 2, the ordered index value 'n₀' may be calculated based on the number of used RBs 'n' and the PUCCH resource set 'm' . The ordered index 'n₀' may be defined by n₀ where 'N_i' is the number of di f f erent RB

combinations used (for different UCI payloads) in PUCCH resource set 'i ' . Typically, 'N_i' may be the number of RBs configured for a PUCCH resource in PUCCH resource set 'i' .

[0076] However, there are two specific situations to consider.

In a first situation, the maximum payload supported by PUCCH resource set 'i-1' may be larger than the payload supported by, e . g . , a single RB in PUCCH resource set 'i' . Accordingly, it may be possible that smallest RB amounts are never used in PUCCH resource set 'i' . In a second situation, it may be possible to configure more RBs to a PUCCH resource than needed for the maximum

UCI payload supported by the PUCCH resource set . A person of ordinary skill in the art may understand that this kind of configuration may not be optimal.

[0077] The first and second situations mentioned above may be taken into account by defining the ordered index 'n₀' with n₀= n_{min, m} where n_min,m may be the smallest number of RBs

(minus one) occupied by the smallest UCI payload of the PUCCH resource set 'm' . n_min,m = 0 may be used for the 1st and 2nd PUCCH resource set (m = 0 or m = 1) , and for other PUCCH resource sets may be used, where may

be the number of subcarriers per resource block (12) and 'L_m' may be the length of the PUCCH resource in symbols, excluding DM-RS . In addition, where 'Ni' may be the number of

different RB combinations actually used (for different UCI payloads) in PUCCH resource set 'i' .

[0078] In Option C, the indication may be derived using the function " (n+m) mod 2" , where 'n' is the number of used RBs and 'm' is the index of the used PUCCH resource set. This option may impose a limitation on the configured PUCCH resource sizes, as only odd number of RBs may be configured for the PUCCH resources. Otherwise, the highest number of RBs of a current PUCCH resource set and the lowest number of RBs of the next PUCCH resource set may produce the same indicator value, which may cause ambiguity.

[0079] In Option D, the indication may be derived using the function " (n+N_m) mod 2", which may provide an indication of the number of used RBs 'n' and of the index of the used PUCCH resource set 'm' . 'N_m' may indicate the number of RBs configured for the PUCCH resources in the resource set 'm' . This option may also impose a limitation on the configured PUCCH resource sizes, as only even numbers of RBs may be configured for the PUCCH resources. Otherwise, the highest number of RBs of current PUCCH resource set and the lowest number of RBs of the next PUCCH resource set may produce the same indicator value, which may cause ambiguity.

[0080] Referring now to FIG. 3, illustrated are examples of indicator values for different UCI payloads and number of used RBs 'n' with implementation of Option A (m mod 2) , Option B (n₀ mod 2) and Option C ( (n+m) mod 2) . The illustrated PUCCH resource configuration comprises PUCCH resource set #0 at 310, PUCCH resource set #1 at 320, and PUCCH resource set #2 at 330. It should be noted that the resource sets included in this PUCCH resource configuration are non-limiting examples of PUCCH resource set (s) with which a UE may be configured. Fewer, more, or different PUCCH resource set (s) may be configured at a UE that is configured to practice an example embodiment of the present disclosure .

[0081] At 310, PUCCH resource set #0 (i.e. pucch-ResourceSetld = 0, m = 0) supports UCI payloads of 1-2 bits, with PUCCH resources using PUCCH format 0 and 1 RB (i.e. N_m) . At 320, PUCCH resource set #1 (m = 1) supports UCI payloads of 3-14 bits, with PUCCH resources configured to use PUCCH format 2 with 2 symbols and up to 3 RB . At 330, PUCCH resource set #2 (m = 2) supports UCI payloads of 15-54 bits, with PUCCH resources configured to use PUCCH format 3 with 7 symbols and up to 3 RB . In the PUCCH resource sets included in the PUCCH resource configuration illustrated at FIG. 3, a maximum code rate of 0.15 is assumed.

[0082] In the example of FIG. 3, the ordered index value 'n₀' may be calculated as in the example of FIG. 2.

[0083] In the examples of FIGs. 2, 3, and 4, the indication may be determined to have a value of '0' or '1' . As further described below, the UE may compare this value with a value determined based on the size of UCI that it intends to report (i.e. HP UCI payload size + LP UCI payload size) . In other examples, the indication may be more than a single bit, as further described below.

[0084] At 310, m = 0 (index of the PUCCH resource set) , n₀ = 1 (ordered index value based on 'm' and 'n' ) , and n = 1 (number of used RBs) . Accordingly, for Option A (m mod 2) the indication is 0; for Option B (n₀ mod 2) the indication is 1; and for Option C ( (n+m) mod 2) the indication is 1.

[0085] At 320, m = 1 (index of the PUCCH resource set) , n₀ = 2 , 3, or 4 (ordered index value based on 'm' and 'n' ) , and n = 1, 2, or 3 (number of used RBs) . Accordingly, for Option A (m mod 2) the indication is 1; for Option B (n₀ mod 2) the indication is 0 where n₀ = 2 , 1 where n₀ =3, and 0 where n₀ = 4; and for Option C ( (n+m) mod 2) the indication is 0 where n = 1, 1 where n = 2, and 0 where n = 3.

[0086] At 330, m = 2 (index of the PUCCH resource set) , n₀ = 5, 6, or 7 (ordered index value based on 'm' and 'n' ) , and n = 1, 2, or 3 (number of used RBs) . Accordingly, for Option A (m mod 2) the indication is 0; for Option B (n₀ mod 2) the indication is 1 where n₀ = 5, 0 where n₀ = 6 , and 1 where n₀ = 7; and for Option C ( (n+m) mod 2) the indication is 1 where n = 1, 0 where n = 2, and 1 where n = 3.

[0087] It may be noted that, for Option A (m mod 2) , the value of the indication alternates between consecutive PUCCH resource sets, and for Option B (n₀ mod 2) and Option C ( (n+m) mod 2) , the value of the indication alternates between consecutive RBs as well as when moving from current PUCCH resource set to the next PUCCH resource set. However, Option C has the requirement that only odd numbers of RBs are configured for the PUCCH resources. Otherwise, the highest number of RBs of a current PUCCH resource set and the lowest number of RBs of the next PUCCH resource set may produce the same indicator value, which may cause ambiguity.

[0088] Referring now to FIG. 4, illustrated are examples of indicator values for different UCI payloads and numbers of used RBs 'n' with implementation of Alternative 1, Option D ( (n+N_m) mod 2) . The illustrated PUCCH resource configuration comprises PUCCH resource set #0 at 410, PUCCH resource set #1 at 420, and PUCCH resource set #2 at 430. It should be noted that the resource sets included in this PUCCH resource configuration are a non- limiting example of PUCCH resource set (s) with which a UE may be configured. Fewer, more, or different PUCCH resource set (s) may be configured at a UE configured to practice an example embodiment of the present disclosure.

[0089] At 410, PUCCH resource set #0 (i.e. pucch-ResourceSetld = 0, m = 0) supports UCI payloads of 1-2 bits, with PUCCH resources using PUCCH format 0 and 1 RB (i.e. N_m) . At 420, PUCCH resource set #1 (i.e. m = 1) supports UCI payloads of 3-9 bits, with PUCCH resources configured to use PUCCH format 2 with 2 symbols and up to 2 RB . At 430, PUCCH resource set #2 (i.e. m = 2) supports UCI payloads of 10-72 bits, with PUCCH resources configured to use PUCCH format 3 with 7 symbols and up to 4 RB .

[0090] At 410, m = 0 (index of the PUCCH resource set) , N_m = 1 (the number of RBs configured for the PUCCH resources in the resource set 'm' ) , and n = 1 (number of used RBs) . Accordingly, for Option D ( (n+N_m) mod 2) , the indication is 0. [0091] At 420, m = 1 (index of the PUCCH resource set) , N_m = 2 (the number of RBs configured for the PUCCH resources in the resource set 'm' ) , and n = 1 or 2 (number of used RBs) .

Accordingly, for Option D ( (n+N_m) mod 2) , the indication is 1 where n = 1, and 0 where n = 2.

[0092] At 430, m = 2 (index of the PUCCH resource set) , N_m = 4 (the number of RBs configured for the PUCCH resources in the resource set 'm' ) , and n = 1, 2, 3, or 4 (number of used RBs) . Accordingly, for Option D ( (n+N_m) mod 2) , the indication is 1 where n = 1, 0 where n = 2, 1 where n = 3, and 0 where n = 4.

[0093] It may be noted that, for Option D ( (n+N_m) mod 2) , the value of the indication alternates between consecutive RBs as well as when moving from a current PUCCH resource set to the next PUCCH resource set. However, Option D has the requirement that only even numbers of RBs are configured for the PUCCH resources. Otherwise, the highest number of RBs of current PUCCH resource set and the lowest number of RBs of the next PUCCH resource set may produce the same indicator value, which may cause ambiguity.

[0094] In an example embodiment implementing Alternative 1, a UE may derive a value based on the size of UCI that it intends to report (i.e. HP UCI payload size + LP UCI payload size) , and may compare the derived value to an indication value received from a gNB . If the values differ, the UE may add NACKs to the LP HARQ- ACK CB until the value derived by the UE matches with the indication value received from the gNB. When the values differ, it may mean that the derived value is less than the received indication value due to the UE missing at least one DL assignment. [0095] FIGs. 2-4 consider variations of Alternative 1 in which a 1 bit dynamic indication is used. However, the indication may be extended to 2 bits. In an example embodiment, the modulo used for an indication may be extended to modulo of 4. This may be beneficial in cases where an ambiguity in the number of LP HARQ- ACK bits may cause a change in more than one RB . This may not be a typical scenario, but may occur when a PUCCH resource is short, e.g. one symbol and LP HARQ-ACK is configured to use a low code rate, or when CBG-based operation is used on LP PDSCH. In an alternative example embodiment, where the dynamic indication comprises 'k' bits, the modulo operation may involve using modulo of 2^k.

[0096] In another example embodiment, the combined indication of the number of used RBs 'n' and PUCCH resource set 'm' may be split into separate indications 'i 1' and 'i2' , where one may be used for PUCCH resource set ID#, (i 1 = n mod 2) ; and the other one for a number of used RBs (i2 = N_m mod 2) .

[0097] In another example embodiment, a flag for HP & LP UCI multiplexing and, hence, presence of LP HARQ-ACK, may be included in/with the HP DL assignment. In another example embodiment, the HP DL assignment flag for HP & LP UCI multiplexing may be extended to a 2-bit field. For example, value 11 may indicate that LP UCI is not multiplexed. The remaining 3 values (00, 10, 01) may be used for the specific indicator determined with modulo 3.

[0098] In another example embodiment, for 'k' bits dynamic indication, one signaling state (e.g. all ones) may indicate no LP multiplexing, whereas the remaining 2^k-l states may be used for the envisioned indication using modulo of (2^k-l) . [0099] FIG. 5 illustrates potential steps for implementing Alternative 1, which may have the technical effect of avoiding a UE/gNB discrepancy/error in the determination of the PUCCH resource and RBs to be used by the UE for transmitting UCI containing both high-priority and low-priority HARQ-ACK (i.e. multiplexed UL transmissions with different priorities) . These steps may be performed at a UE . The UE may, for example, be an IIoT device, and/or may be a UE as described above. At 510, a UE may receive a configuration for HP UCI reporting. At 520, the UE may receive at least one DL assignment for a PDSCH associated with (HP) HARQ-ACK. For example, PDSCH received with the at least one DL may be configured to trigger the UE to respond with, at least, an HP HARQ-ACK. The DL assignment may contain/include an indication value. At 530, the UE may derive a value based on the HP UCI payload size and an LP UCI payload size. For example, the HP UCI payload size may correspond to PDSCH received according to the at least one DL assignment received at 520. The value may be derived based on the configuration for HP UCI reporting received at 510. At 540, the UE may compare the received indication value and the derived value. If the values are not equal, at 550 the UE may increment the LP HARQ-ACK CB size with one or more NACKs. Based on this update, the UE may re-derive the value based on the HP UCI payload size and the (updated) LP UCI payload size and perform the comparison again, at 540. If the values are equal, at 560 the UE may select a PUCCH resource set based on the HP UCI payload size and the (optionally, updated) LP UCI payload size. The UE may select a PUCCH resource of the selected PUCCH resource set based on a PRI (PUCCH resource index) received in the at least one downlink assignment. The UE may multiplex the HP HARQ-ACK and the LP HARQ-ACK. If the UE is configured to perform Option A, at 570, the UE may transmit the (multiplexed) HP UCI and LP UCI using the RBs configured for the PUCCH resource. If the UE is configured to perform Option B, C, or D, the UE may transmit the (multiplexed) HP UCI and LP UCI using the RBs determined based on the HP UCI payload size and the LP UCI payload size.

[00100] FIG. 6 illustrates potential steps for implementing Alternative 1 , which may have the technical effect of avoiding a UE/gNB discrepancy/error in the determination of the PUCCH resource and RBs used by the UE for transmitting UCI containing both high priority and low priority HARQ-ACK. These steps may be performed at a gNB or other base station. The gNB may, for example, be in communication with an IIoT device and/or a UE as described above. At 610, the gNB may transmit a configuration for HP UCI reporting to a UE . At 620, the gNB may transmit at least one DL assignment for PDSCH and corresponding PDSCHs/downlink data. The UE receiving the DL assignment and corresponding PDSCHs may (later) respond with, at least, HARQ-ACK having low priority. At 630, the gNB may determine a PUCCH resource set based on (expected) HP and LP UCI payload sizes. The LP UCI payload may correspond to the PDSCH transmitted at 620. If the configuration transmitted at 610 indicates that Option B, C, or D is to be performed at the UE, the gNB may also determine a number of RBs based on the HP UCI payload size and LP UCI payload size. At 640, the gNB may determine an indication for PUCCH resource set. If the configuration indicates that Option B, C, or D is to be performed at the UE, the gNB may also determine a number of RBs. At 650, the gNB may select a PUCCH resource from a PUCCH resource set indicated by the determined indication for a PUCCH resource set, and may determine the corresponding PRI . At 660, the gNB may transmit at least one DL assignment for PDSCH with PRI and with the indication. The gNB may transmit the corresponding PDSCHs /downlink data according to the assignment. The at least one DL assignment and PDSCHs transmitted at 660 may be different than the at least one DL assignment and PDSCHs transmitted at 620. For example, the at least one DL assignment and PDSCHs transmitted at 620 may be configured to trigger low priority UCI reporting from the UE, while the at least one DL assignment and PDSCHs transmitted at 660 may be configured to trigger high priority UCI reporting from the UE . UCI payloads corresponding to the PDSCH transmitted at 620 and PDSCH transmitted at 660 may be determined according to such assumptions. If the configuration indicates that Option A is to be performed at the UE, at 670, the gNB may receive a (multiplexed) HP UCI and LP UCI using the RBs configured for the PUCCH resource. If the configuration indicates that Option B, C, or D is to be performed at the UE, the gNB may receive a (multiplexed) HP UCI and LP UCI using the RBs determined based on the HP UCI payload size and the LP UCI payload size. For example, the HP+LP UCI may comprise UCI responsive to the PDSCH transmitted at 620 and UCI responsive to the PDSCH transmitted at 660.

[00101] Alternative 2 will now be described with reference to FIGs. 7 and 8. In Alternative 2, a specific indication may be a configuration of a semi-static size reservation 'Y' , which may be used instead of a determined LP HARQ-ACK payload to determine PUCCH resource (s) , e.g. a PUCCH resource set, that may be used for uplink transmission for multiplexed HP and LP HARQ-ACKs . Semi-static size reservation 'Y' may be provided by RRC or, alternatively, the size of 'Y' may be dynamically indicated to a UE, as further described below. [00102] In an example embodiment implementing Alternative 2, an LP HARQ-ACK size reservation 'Y' may be used by a UE, instead of a determined LP HARQ-ACK CB size, when selecting a PUCCH resource set. The size of 'Y' may be fixed by the configuration or, alternatively, there may be a dynamic indication in the scheduling DL assignment of PDSCH (which may be similar to the indication included in the DL assignment for PDSCH received in Alternative 1) for selecting one of, e.g. , 'K=2^k-1' configured values for 'Y' using k-bit dynamic indication.

[00103] In an example embodiment, all RBs configured for a PUCCH resource (which may be indicated by PRI ) of a PUCCH resource set may be used (and not adjusted based on HP+LP UCI payload) . Alternatively, LP HARQ-ACK size reservation 'Y' may also be used in the determination of a number of RBs used as part of the combined HP+LP UCI payload size.

[00104] In an example embodiment, a flag for HP & LP UCI multiplexing and, hence, presence of LP HARQ-ACK, may be included in/with the HP DL assignment.

[00105] In another example embodiment, the HP DL assignment flag for HP & LP UCI multiplexing may be extended to a 2-bit field. For example, value 00 may indicate that LP UCI is not multiplexed. The remaining K=3 values (11, 01, 10) may be used to indicate one of K=3 configured size values 'Y' for the LP HARQ-ACK semi-static size reservation. In another example embodiment, for 'k' bits dynamic indication, one signaling state (e.g. all zeros) may indicate no LP multiplexing, whereas the remaining K=2^k-1 states may be used to indicate one of K=2^k-1 configured size values of 'Y' . [00106] It may be noted that LP HARQ-ACK size reservation 'Y' may differ from the actual number of LP HARQ-ACKs . When 'Y' is larger than the actual number of HARQ-ACKs, a PUCCH resource set with unnecessarily large PUCCH resources may be selected. Although this may result in an increased use of UL resources, it might not cause dropping of LP HARQ-ACKs (i.e. situation where LP HARQ-ACKS are not multiplexed) , which would trigger PDSCH retransmissions on a larger amount of DL resources. When 'Y' is smaller than the actual number of HARQ-ACKs, a PUCCH resource that is too small for the actual LP+HP UCI may be selected, which may cause some LP UCI to be dropped or compressed. This may trigger unnecessary PDSCH retransmission. However, as 'Y' impacts only the PUCCH resource set selection in Alternative 2, and not determination of a number of RBs/selection of a resource in the selected set, the negative impact of underestimating/overestimating LP UCI size may be limited to cases where LP+HP UCI size is rather close to the UCI size limit of a selected PUCCH resource set.

[00107] It may be noted that Alternative 2 may be applied to scenarios in which LP HARQ-ACK is multiplexed on HP PUSCH as well. In such a scenario, a reliable determination of the total number of LP+HP HARQ-ACKs may be needed to ensure that HARQ-ACKs and UL- shared channel (SCH) are mapped to the resource elements (REs) in the same way at both the UE and gNB . It may also be noted that a UL DAI on/included with an UL grant may be used for HP HARQ-ACKs. Considering the cases where LP HARQ-ACK may be multiplexed on HP PUSCH, the LP HARQ-ACK size reservation 'Y' may be used to determine the size of LP HARQ-ACK CB to be multiplexed on HP PUSCH. In an example embodiment in which HP CG (configured grant) PUSCH is performed, the size of 'Y' may be configured via, e.g. , RRC signaling. In an alternative example embodiment in which HP DG (dynamic grant) PUSCH is performed, the size of 'Y' may be dynamically indicated in UL grant scheduling HP DG PUSCH transmission; multiple 'Y' values may be configured, and the indication in the UL grant downlink control information (DCI) may be used to point to one specific value of the configured values.

[00108] FIG. 7 illustrates potential steps for implementing Alternative 2 , which may have the technical effect of avoiding a UE/gNB discrepancy/error in the determination of the PUCCH resource and RBs used by the UE for transmitting UCI containing both high-priority and low-priority HARQ-ACK. These steps may be performed at a UE . The UE may, for example, be an IIoT device, and/or may be a UE as described above. At 710, a UE may receive a configuration for HP UCI reporting that provides at least one semi-static reservation value 'Y' . At 720, the UE may receive at least one DL assignment for PDSCH. For example, the at least one DL assignment may be used for PDSCH configured to trigger, at least, high-priority feedback. At 730, the UE may determine whether HP and LP UCI multiplexing is indicated by, for example, the value of 'Y' , an indication of a configured value of 'Y' , and/or presence of a flag for HP & LP UCI multiplexing included in the DL assignment. If multiplexing is not indicated, at 740 the UE may select a PUCCH resource set based on the HP UCI payload size and may select a PUCCH resource from the selected PUCCH resource set based on PRI . At 750, the UE may transmit the HP UCI using the RBs determined based on the HP UCI payload size.

[00109] If multiplexing is indicated, at 760 the UE may determine a UCI payload size for a PUCCH resource set selection, where the PUCCH resource set may be selected based on HP UCI payload size and LP UCI payload size, by replacing the LP HARQ— ACK CB size with indicated 'Y' value. In other words, the PUCCH resource set may be selected based on a combination/sum of 'Y' and the HP UCI payload size, rather than based on a combination/sum of the LP UCI payload size and the HP UCI payload size. At 770, the UE may determine a PUCCH resource of the selected PUCCH resource set based on PRI . The UE may transmit (multiplexed/combined) HP+LP UCI using the RBs configured for the determined PUCCH resource. Alternatively, the UE may determine the number of RBs based on the combination of HP UCI payload size and LP UCI payload size. Alternatively, LP HARQ-ACK size reservation 'Y' may also be used in the determination of a number of RBs used as part of the combined HP+LP UCI payload size.

[00110] FIG. 8 illustrates potential steps for implementing Alternative 2, which may have the technical effect of avoiding a UE/gNB discrepancy/error in the determination of the PUCCH resource and RBs used by the UE for transmitting UCI containing both high-priority and low-priority HARQ-ACK. These steps may be performed at a gNB or other base station. The gNB may, for example, be in communication with an IIoT device and/or a UE as described above. At 810, a gNB may transmit a configuration for HP UCI reporting to a UE . The configuration may provide at least one semi-static reservation value, 'Y' , or an indication of a configured value for 'Y' . At 820, the gNB may transmit at least one DL assignment for PDSCH. The gNB may transmit PDSCHs/downlink data wi th/corresponding to the assignment. For example, the at least one DL assignment may be used to transmit PDSCH configured to trigger, at least, low-priority feedback from the UE . At 830, the gNB may determine a PUCCH resource set based on an (expected) HP UCI payload size and an (expected) LP UCI payload size by replacing the LP HARQ-ACK CB size with the 'Y' value indicated in the configuration. In other words, the gNB may determine the PUCCH resource set based on the (expected) HP UCI payload size and the 'Y' value, rather than based on HP UCI payload size and the LP UCI payload size. Alternatively, LP HARQ-ACK size reservation 'Y' may also be used in the determination of a number of RBs used as part of the combined HP+LP UCI payload size. At 840, the gNB may select a PUCCH resource and determine the corresponding PRI . At 850, the gNB may transmit at least one DL assignment for PDSCH. The DL assignment may include an indication for HP and LP UCI multiplexing (such as a 'Y' value or a flag) and an indication of the PRI. The gNB may transmit PDSCHs/downlink data according to/corresponding with the DL assignment. For example, the at least one DL assignment may be used to transmit PDSCH configured to trigger high-priority feedback from the UE . At 860, the gNB may receive ( combined/mul tiplexed) HP+LP UCI on the RBs configured for the selected PUCCH resource on the determined PUCCH resource set. For example, the HP+LP UCI may comprise UCI responsive to the PDSCH transmitted at 820 and UCI responsive to the PDSCH transmitted at 850.

[00111] Alternative 3 will now be described with reference to

FIGs. 9 and 10. In Alternative 3, a specific indication may be defined by combining a dynamic indication of LP UCI multiplexing and LP HARQ-ACK codebook size and may be used to determine PUCCH resource (s) that may be used for uplink transmission for multiplexed HP and LP HARQ-ACKs . In contrast to an indication comprising repetition of the 2-bit LP HARQ total DAI, this dynamic indication may provide the ability to dynamically indicate if LP UCI is to be multiplexed or not. In an example embodiment, 'k' bits may be indicated. In an example embodiment, k = 2 bits, similar to when total DAI repetition are used for indication. With 'k' bits, values { 0...2^k— 1 } may be indicated. Value 2^k-l may indicate that an LP UCI is not to be multiplexed together with HP UCI, while values { 0...2^k— 2 } (i.e. all other values) may indicate that LP UCI is to be multiplexed with HP UCI. The value may also indicate the number of the received PDSCHs (scheduled by a DL assignment) 'L' by mapping it to a value (e.g. using L mod 2^k-l) . It should be noted that, in contrast to an indication comprising the total DAI for the case of k = 2 bits, the value to be mapped may be (L mod 3) , whereas the 2-bit total DAI may be mapped with (L mod 4) only. Accordingly, UE may receive/have the combination of two 'L' indications, given by the cyclic indication of a factor of 3 (in the HP DL assignment, using 'mod 3' ) , and the total DAI using "mod 4" in the last LP DL assignment. This may cause changes to codebook determination .

[00112] As a HP DL assignment may indicate DAI with shorter modulo cycle (3) , in an example embodiment it may be advantageous (e.g. reliable) to first determine LP codebook based on the DAI value received on/with the DL assignment, and then check if there is a discrepancy between a DL assignment DAI and a DAI received with another DL assignment. If there is a discrepancy between the two DAI values, the UE may add a number of NACKs, corresponding to the difference, to the end of the LP codebook. When the DAI values differ, it may mean that the derived value is less than the received indication value due to UE missing at least one DL assignment corresponding to the LP codebook.

[00113] In an example embodiment implementing Alternative 3, two sub-codebooks for LP HARQ may be operated. Variations/implementations of Alternative 3 will now be discussed. [00114] In a first implementation, 4 bit dynamic signaling may be used (i.e. 2 bits for each sub-codebook) , although this might not be optimal from an overhead viewpoint. 4 bit dynamic signaling may allow indication of the following intentions: (a) only the first sub-codebook, (b) only the second sub-codebook, (c) both sub-codebooks, or (d) no LP UCI/HARQ-ACK is to be multiplexed. In an example embodiment, an indication of the codebook size for each of the multiplexed codebooks may also be available, as described above, for one codebook for 2 bit (i.e. using mapping) .

[00115] In a second implementation, the dynamic 2-bit indication may only indicate the codebook size of the first (TB-based) sub- codebook of LP HARQ, and that only the first sub-codebook is to be multiplexed (i.e. the second HARQ-ACK codebook for code block group (CBG) -based PDSCH with much larger size due to CBG HARQ-ACK feedback is neglected as having a higher potential to create worse decoding performance due to overall higher UCI payload size (s) ) .

[00116] In an alternative example embodiment, the UE may be configured by RRC if the 2 bit dynamic indication in the DL assignment for PDSCH with HP HARQ-ACK is associated with the first or the second sub-codebook. Therefore, the gNB may conf igure/indicate if only the first or the second sub-codebook is/can be multiplexed.

[00117] In a third implementation, if, for HP HARQ-ACK, two sub- codebooks (i.e. CBG based PDSCH) are also configured, the 2-bit indication of the first sub-codebook of LP HARQ may be indicated by a DL assignment scheduling PDSCH with HP HARQ of the first sub- codebook. The 2-bit indication of the second sub-codebook (i.e. for CBG) of LP HARQ may be indicated by a DL assignment scheduling PDSCH with HP HARQ of the second sub-codebook (i.e. HP CBG-based HARQ-ACK) . In other words, the indication may be associated with the same sub-codebook between LP and HP HARQ-ACK. The indication whether both LP HARQ-ACK sub-codebooks are to be multiplexed may be carried in two independent DL assignments scheduling PDSCH with HP HARQ-ACK in both sub-codebooks. In case the HP HARQ-ACK codebook does not contain a sub-codebook (either for TB or CBG) , then the corresponding LP HARQ-ACK sub-codebook may be dropped.

[00118] Example embodiments implementing Alternative 3 may have the same issue (s) as the prior art solution involving two sub- codebooks, as described above. More specifically, Type 2 CB may comprise two sub-codebooks for TB-based and CBG-based operation, with an independent number of scheduled PDSCHs 'L' . In principle, double the number of bits may be required (i.e. 2+2 bits, 2 bits for each of the low-priority sub-codebooks) . Some variations on Alternative 3 may serve to limit the overhead to only 2 bits.

[00119] In contrast to Alternative 1 and Alternative 2, Alternative 3 clearly requires at least 2 bits of dynamic signaling; Alternative 1 and Alternative 2 may be operated with 1 bit for dynamic signaling, and so may be operated with lower overhead .

[00120] It may be noted that, as described above with regard to Alternative 2, Alternative 3 may also be applied to scenarios in which LP HARQ-ACK is multiplexed on HP PUSCH.

[00121] In contrast to Alternative 1, the dynamic signaling of Alternative 3 may include an indication of the LP HARQ-ACK codebook size. [00122] FIG. 9 illustrates potential steps for implementing Alternative 3, which may have the technical effect of avoiding a UE/gNB discrepancy/error in the determination of the PUCCH resource and RBs used by the UE for transmitting UCI containing both high-priority and low-priority HARQ-ACK. These steps may be performed at a UE . The UE may, for example, be an IIoT device, and/or may be a UE as described above. FIG. 9, for simplicity, shows an example of the second implementation of Alternative 3, in which only the first sub-codebook of LP HARQ-ACK is indicated (i.e. the second LP HARQ-ACK sub-codebook is not multiplexed) , as described above. At 910, a UE may receive a configuration for HP UCI reporting. At 920, the UE may receive at least one DL assignment for PDSCH. For example, PDSCH received according to the at least one DL assignment may be configured to trigger HP feedback. At 930, the UE may determine whether HP and LP UCI multiplexing has been indicated with a dynamic indication of LP UCI multiplexing. If multiplexing has not been indicated, at 940, the UE may select a PUCCH resource set based on HP UCI payload size. The UE may select a PUCCH resource of the selected PUCCH resource set based on PRI included in the at least one downlink assignment. At 950, the UE may transmit HP UCI using RBs determined based on the HP UCI payload size.

[00123] If multiplexing has been indicated, at 960 the UE may determine a LP HARQ-ACK CB based, at least partially, on a DAI indication on/included with the DL assignment. For example, the DAI may be associated with PDSCH configured to trigger the LP HARQ- ACK to be transmitted. The UE may determine the UCI payload size for PUCCH resource set selection based on HP UCI payload size and LP UCI payload size. At 970, the UE may determine a PUCCH resource of the determined PUCCH resource set based on PRI . For example, the PRI may be associated with the HP UCI. The UE may transmit (multiplexed/combined) HP+LP UCI using the RBs configured for the determined PUCCH resource.

[00124] FIG. 10 illustrates potential steps for implementing Alternative 3, which may have the technical effect of avoiding a UE/gNB discrepancy/error in the determination of the PUCCH resource and RBs used by the UE for transmitting UCI containing both high-priority and low-priority HARQ-ACK. These steps may be performed at a gNB . The gNB may, for example, be in communication with an IIoT device and/or a UE as described above. At 1010, the gNB may transmit, to a UE, a configuration for HP UCI reporting. At 1020, the gNB may transmit at least one DL assignment for PDSCH. The gNB may transmit PDSCHs wi th/corresponding to the assignment. For example the PDSCH transmitted according to the at least one DL assignment may be configured to trigger low-priority feedback. At 1030, the gNB may determine a PUCCH resource set based on a (expected) HP UCI payload size and a (expected) LP UCI payload size. At 1040, the gNB may select a PUCCH resource of the determined PUCCH resource set. The gNB may determine the corresponding PRI . At 1050, the gNB may transmit at least one DL assignment for PDSCH. The assignment may include the determined PRI, and may include a joint indication of HP+LP UCI multiplexing and LP DAI. The gNB may transmit PDSCHs/downlink data according/corresponding to the assignment. For example, the PDSCH transmitted according to the at least one DL assignment may be configured to trigger high-priority feedback. At 1060, the gNB may receive a (multiplexed/combined) HP+LP UCI on the RBs configured for the selected PUCCH resource of the determined PUCCH resource set. For example, the HP+LP UCI may comprise UCI responsive to the PDSCH transmitted at 1020 and UCI responsive to the PDSCH transmitted at 1050.

[00125] In some of the example embodiments of the present disclosure, an indication of whether or not LP UCI is multiplexed with HP UCI may be assumed to be contained in DL assignment ( s ) configured to trigger HP UCI .

[00126] It may be noted that, in some of the example embodiments described above, an indication may be included with/in HP DL assignment (i.e. a DL assignment configured to trigger HP UCI) due to the higher reliability of the transmission. HP DL assignment may be sent with short latency, that is, a last HP DL assignment may be sent at a same time or later than an LP DL assignment (i.e. a DL assignment configured to trigger LP UCI) . In alternative example embodiments, an indication may be included in an LP DL assignment rather than an HP DL assignment.

[00127] It may be noted that LP UCI may contain LP HARQ-ACK, SR and, possibly, CSI . The size of LP SR and CSI may be determined based on RRC configuration and, accordingly, example embodiments of the present disclosure may be applied to determination of LP HARQ-ACK CB.

[00128] It may be noted that LP HARQ-ACK CB size may be incremented in steps of NACK(s) that a UE is configured to report per PDSCH transmission. NACKs may be added to the end of LP HARQ-ACK CB, as the error may likely be due to missed detection of a last DL assignment. If NACK ( s ) are added in more than 2^b-l iterations, where 'b' is the number of DAI bits in LP DL assignment, the whole LP HARQ-ACK CB may be set to NACKs, as it may be uncertain which LP DL assignments are missed. [00129] FIG. 11 illustrates the potential steps of an example method 1100. The example method 1100 may include receiving a configuration for reporting high-priority uplink control information, 1110; receiving at least one downlink assignment, 1120; generating high-priority uplink control information, 1130; generating low-priority uplink control information, 1140; determining a payload size of uplink control information for transmission, wherein the payload size of the uplink control information for transmission is based, at least partially, on a payload size of the high-priority uplink control information, 1150; selecting an uplink resource set based, at least partially, on the determined payload size and at least one of: the received configuration, or a received indication value, 1160; selecting a resource of the selected uplink resource set based, at least partially, on a resource index associated with the high-priority uplink control information, 1170; and transmitting at least one of : the high-priority uplink control information, or the low- priority uplink control information based, at least partially, on the received configuration and the selected resource, 1180. For example, the at least one downlink assignment may be used to receive data that triggers the generating of the high-priority uplink control information, such as a HP HARQ-ACK.

[00130] FIG. 12 illustrates the potential steps of an example method 1200. The example method 1200 may include receiving, at a user equipment, at least one downlink assignment, wherein the at least one downlink assignment comprises an indication of whether low-priority uplink control information is to be multiplexed on a high-priority uplink control information transmission, 1210; determining an uplink control information payload to be transmitted in an uplink channel based, at least partially, on the at least one downlink assignment, 1220; at least one of : where the indication indicates that the low-priority uplink control information is not to be multiplexed on the high-priority uplink control information transmission, determining a high-priority hybrid automatic repeat request codebook, an uplink resource set, and a number of resource blocks for the high-priority uplink control information transmission based on a first set of rules, or where the indication indicates that the low-priority uplink control information is to be multiplexed on the high-priority uplink control information transmission, determining the high- priority hybrid automatic repeat request codebook based on the first set of rules, and determining the uplink resource set and the number of resource blocks for the high-priority uplink control information transmission based on a second set of rules, wherein the second set of rules are is based, at least partially, on the indication, 1230; and performing transmission of the high-priority uplink control information transmission based on the determined high-priority hybrid automatic repeat request codebook, the determined uplink resource set, and the determined number of resource blocks, 1240.

[00131] In accordance with one aspect, an example method may be provided comprising: receiving a configuration for reporting high- priority uplink control information; receiving at least one downlink assignment; generating high-priority uplink control information; generating low-priority uplink control information; determining a payload size of uplink control information for transmission, wherein the payload size of the uplink control information for transmission may be based, at least partially, on a payload size of the high-priority uplink control information; selecting an uplink resource set based, at least partially, on the determined payload size and at least one of : the received configuration, or a received indication value; selecting a resource of the selected uplink resource set based, at least partially, on a resource index associated with the high-priority uplink control information; and transmitting at least one of : the high-priority uplink control information, or the low-priority uplink control information based, at least partially, on the received configuration and the selected resource.

[00132] The at least one downlink assignment may schedule downlink data associated with a high-priority hybrid automatic repeat request .

[00133] The example method may further comprise: based, at least partially, on the at least one downlink assignment, determining whether to perform multiplexing of the high-priority uplink control information with the low-priority uplink control information for uplink transmission.

[00134] The at least one downlink assignment may comprise a flag, wherein the determining of whether to perform multiplexing of the high-priority uplink control information with the low-priority uplink control information for uplink transmission may be based, at least partially, on the flag.

[00135] The example method may further comprise: multiplexing, in response to a determination to perform the multiplexing, the high- priority uplink control information and the low-priority uplink control information to form a multiplexed uplink control information, wherein the transmitting of at least one of the high- priority uplink control information or the low-priority uplink control information may comprise transmitting the multiplexed uplink control information.

[00136] The at least one downlink assignment may comprise the received indication value, wherein the example method may further comprise: determining a first value based on the payload size of the high-priority uplink control information and a payload size of the low-priority uplink control information; and comparing the received indication value with the determined first value.

[00137] The determined first value is different from the received indication value, wherein the example method may further comprise: adding at least one negative acknowledgement to the low-priority uplink control information and updating the determined first value based on the adding of the at least one negative acknowledgement.

[00138] The example method may further comprise: determining one or more resource blocks based on the payload size of the high- priority uplink control information and a payload size of the low- priority uplink control information, wherein the transmitting of at least one of the high-priority uplink control information or the low-priority uplink control information may comprise transmitting with the one or more determined resource blocks .

[00139] The received indication value may comprise an uplink resource set index modulo two, wherein the comparing of the received indication value with the determined first value may comprise comparing the uplink resource set index modulo two with the determined first value modulo two.

[00140] The received indication value may comprise an ordered index of an expected number of resource blocks, wherein the comparing of the received indication value with the determined first value may comprise comparing the ordered index modulo two with the determined first value.

[00141] The received indication value may comprise a number of expected resource blocks and an uplink resource set index, wherein the comparing of the received indication value with the determined first value may comprise comparing a sum of the number of expected resource blocks and the uplink resource set index, modulo two, with the determined first value.

[00142] The received indication value may comprise a number of expected resource blocks, and a number of resource blocks configured for an uplink resource of the selected uplink resource set, wherein the comparing of the received indication value with the determined first value may comprise comparing a sum of the number of expected resource blocks and the number of resource blocks configured for the uplink resource of the selected uplink resource set, modulo two, with the determined first value.

[00143] The example method may further comprise: receiving a configuration of at least one semi-static reservation value.

[00144] The determining of whether to perform multiplexing of the high-priority uplink control information with the low-priority uplink control information for uplink transmission may result in a determination that multiplexing is not to be performed, wherein the transmitting of at least one of the high-priority uplink control information or the low-priority uplink control information may comprise transmitting the high-priority uplink control information and not the low-priority uplink control information, wherein the example method may further comprise: determining one or more resource blocks based on the payload size of the high- priority uplink control information, wherein the transmitting of the high-priority uplink control information may comprise transmitting the high-priority uplink control information with the one or more determined resource blocks.

[00145] The determining of whether to perform multiplexing of the high-priority uplink control information with the low-priority uplink control information for uplink transmission may result in a determination that multiplexing is to be performed, wherein the determined payload size may be further based on the at least one semi-static reservation value.

[00146] The at least one downlink assignment may comprise a value configured to indicate one of a plurality of configured semi- static reservation values as the at least one semi-static reservation value.

[00147] The received indication value may comprise at least a first indication.

[00148] The at least one downlink assignment may comprise the received indication value, wherein the determining of whether to perform multiplexing of the high-priority uplink control information with the low-priority uplink control information for uplink transmission may be based, at least partially, on a value of the first indication.

[00149] The first indication may be configured to indicate a number of acknowledgements for low-priority downlink data the low- priority uplink control information comprises. [00150] At 1 east one of the at least one downlink assignment may comprise an indication of a downlink assignment index, wherein the number of acknowledgements may be further based on the indication of the downlink assignment index.

[00151] The at least one downlink assignment comprising the indication of the downlink assignment index may schedule downlink data associated with a low-priority hybrid automatic repeat request .

[00152] The f irst indication may be configured to identify one or more sub-codebooks for transmitting uplink data.

[00153] The first indication may be configured to indicate a codebook size of a low-priority sub-codebook comprised in the low- priority uplink control information.

[00154] The determining of whether to perform multiplexing of the high-priority uplink control information with the low-priority uplink control information for uplink transmission may result in a determination that multiplexing is to be performed, wherein the example method may further comprise: determining a codebook for the low-priority uplink control information, wherein the determined payload size may be further based on a payload size of the low-priority uplink control information.

[00155] The determining of whether to perform multiplexing of the high-priority uplink control information with the low-priority uplink control information for uplink transmission may result in a determination that multiplexing is not to be performed, wherein the transmitting of at least one of the high-priority uplink control information or the low-priority uplink control information may comprise transmitting the high-priority uplink control information and not the low-priority uplink control information, wherein the example method may further comprise: determining one or more resource blocks based on the payload size of the high- priority uplink control information, wherein the transmitting of the high-priority uplink control information may comprise transmitting the high-priority uplink control information with the one or more determined resource blocks.

[00156] The determining of whether to perform multiplexing of the high-priority uplink control information with the low-priority uplink control information for uplink transmission may result in a determination that multiplexing is to be performed, wherein the transmitting of at least one of the high-priority uplink control information or the low-priority uplink control information may comprise transmitting the high-priority uplink control information and the low-priority uplink control information.

[00157] The transmitting of at least one of the high-priority uplink control information or the low-priority uplink control information may comprise transmitting with one or more resource blocks configured for the selected resource of the selected uplink resource set.

[00158] In accordance with one example embodiment, an apparatus may comprise: at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to: receive a configuration for reporting high-priority uplink control information; receive at least one downlink assignment; generate high-priority uplink control information; generate low-priority uplink control information; determine a payload size of uplink control information for transmission, wherein the payload size of the uplink control information for transmission may be based, at least partially, on a payload size of the high-priority uplink control information; select an uplink resource set based, at least partially, on the determined payload size and at least one of: the received configuration, or a received indication value; select a resource of the selected uplink resource set based, at least partially, on a resource index associated with the high-priority uplink control information; and transmit at least one of : the high- priority uplink control information, or the low-priority uplink control information based, at least partially, on the received configuration and the selected resource.

[00159] The at least one downlink assignment may schedule downlink data associated with a high-priority hybrid automatic repeat request .

[00160] The example apparatus may be further configured to: based, at least partially, on the at least one downlink assignment, determine whether to perform multiplexing of the high-priority uplink control information with the low-priority uplink control information for uplink transmission.

[00161] The at least one downlink assignment may comprise a flag, wherein determining whether to perform multiplexing of the high- priority uplink control information with the low-priority uplink control information for uplink transmission may be based, at least partially, on the flag. [00162] The example apparatus may be further configured to: multiplex, in response to a determination to perform the multiplexing, the high-priority uplink control information and the low-priority uplink control information to form a multiplexed uplink control information, wherein transmitting at least one of the high-priority uplink control information or the low-priority uplink control information may comprise transmitting the multiplexed uplink control information.

[00163] The at least one downlink assignment may comprise the received indication value, wherein the example apparatus may be further configured to: determine a first value based on the payload size of the high-priority uplink control information and a payload size of the low-priority uplink control information; and compare the received indication value with the determined first value.

[00164] The determined first value may be different from the received indication value, wherein the example apparatus may be further configured to: add at least one negative acknowledgement to the low-priority uplink control information and update the determined first value based on adding the at least one negative acknowledgement .

[00165] The example apparatus may be further configured to: determine one or more resource blocks based on the payload size of the high-priority uplink control information and a payload size of the low-priority uplink control information, wherein transmitting at least one of the high-priority uplink control information or the low-priority uplink control information may comprise transmitting with the one or more determined resource blocks. [00166] The received indication value may comprise an uplink resource set index modulo two, wherein comparing the received indication value with the determined first value may comprise comparing the uplink resource set index modulo two with the determined first value modulo two.

[00167] The received indication value may comprises an ordered index of an expected number of resource blocks, wherein comparing the received indication value with the determined first value may comprise comparing the ordered index modulo two with the determined first value.

[00168] The received indication value may comprise a number of expected resource blocks and an uplink resource set index, wherein comparing the received indication value with the determined first value may comprise comparing a sum of the number of expected resource blocks and the uplink resource set index, modulo two, with the determined first value.

[00169] The received indication value may comprise a number of expected resource blocks, and a number of resource blocks configured for an uplink resource of the selected uplink resource set, wherein comparing the received indication value with the determined first value may comprise comparing a sum of the number of expected resource blocks and the number of resource blocks configured for the uplink resource of the selected uplink resource set, modulo two, with the determined first value.

[00170] The example apparatus may be further configured to: receive a configuration of at least one semi-static reservation value . [00171] Determining whether to perform multiplexing of the high- priority uplink control information with the low-priority uplink control information for uplink transmission may result in a determination that multiplexing is not to be performed, wherein transmitting at least one of the high-priority uplink control information or the low-priority uplink control information may comprise transmitting the high-priority uplink control information and not the low-priority uplink control information, wherein the example apparatus may be further configured to: determine one or more resource blocks based on the payload size of the high-priority uplink control information, wherein transmitting the high-priority uplink control information may comprise transmitting the high- priority uplink control information with the one or more determined resource blocks.

[00172] Determining whether to perform multiplexing of the high- priority uplink control information with the low-priority uplink control information for uplink transmission may result in a determination that multiplexing is to be performed, wherein the determined payload size may be further based on the at least one semi-static reservation value.

[00173] The at least one downlink assignment may comprise a value configured to indicate one of a plurality of configured semi- static reservation values as the at least one semi-static reservation value.

[00174] The received indication value may comprise at least a first indication.

[00175] The at least one downlink assignment may comprise the received indication value, wherein determining whether to perform multiplexing of the high-priority uplink control information with the low-priority uplink control information for uplink transmission may be based, at least partially, on a value of the first indication.

[00176] The first indication may be configured to indicate a number of acknowledgements for low-priority downlink data the low- priority uplink control information comprises.

[00177] At 1 east one of the at least one downlink assignment may comprise an indication of a downlink assignment index, wherein the number of acknowledgements may be further based on the indication of the downlink assignment index.

[00178] The at least one downlink assignment comprising the indication of the downlink assignment index may schedule downlink data associated with a low-priority hybrid automatic repeat request .

[00179] The first indication may be configured to identify one or more sub-codebooks for transmitting uplink data.

[00180] The f irst indication may be configured to indicate a codebook size of a low-priority sub-codebook comprised in the low- priority uplink control information.

[00181] Determining whether to perform multiplexing of the high- priority uplink control information with the low-priority uplink control information for uplink transmission may result in a determination that multiplexing is to be performed, wherein the example apparatus may be further configured to: determine a codebook for the low-priority uplink control information, wherein the determined payload size may be further based on a payload size of the low-priority uplink control information.

[00182] Determining whether to perform multiplexing of the high- priority uplink control information with the low-priority uplink control information for uplink transmission may result in a determination that multiplexing is not to be performed, wherein transmitting at least one of the high-priority uplink control information or the low-priority uplink control information may comprise transmitting the high-priority uplink control information and not the low-priority uplink control information, wherein the example apparatus may be further configured to: determine one or more resource blocks based on the payload size of the high-priority uplink control information, wherein transmitting the high-priority uplink control information may comprise transmitting the high- priority uplink control information with the one or more determined resource blocks.

[00183] Determining whether to perform multiplexing of the high- priority uplink control information with the low-priority uplink control information for uplink transmission may result in a determination that multiplexing is to be performed, wherein transmitting at least one of the high-priority uplink control information or the low-priority uplink control information may comprise transmitting the high-priority uplink control information and the low-priority uplink control information.

[00184] T ransmitting at least one of the high-priority uplink control information or the low-priority uplink control information may comprise transmitting with one or more resource blocks configured for the selected resource of the selected uplink resource set.

[00185] In accordance with one example embodiment, an apparatus may comprise: circuitry configured to perform: receiving a configuration for reporting high-priority uplink control information; receiving at least one downlink assignment; generating high-priority uplink control information; generating low-priority uplink control information; determining a payload size of uplink control information for transmission, wherein the payload size of the uplink control information for transmission may be based, at least partially, on a payload size of the high- priority uplink control information; selecting an uplink resource set based, at least partially, on the determined payload size and at least one of: the received configuration, or a received indication value; selecting a resource of the selected uplink resource set based, at least partially, on a resource index associated with the high-priority uplink control information; and transmitting at least one of : the high-priority uplink control information, or the low-priority uplink control information based, at least partially, on the received configuration and the selected resource .

[00186] As used in this application, the term "circuitry" may refer to one or more or all of the following: (a) hardware-only circuit implementations (such as implementations in only analog and/or digital circuitry) and (b) combinations of hardware circuits and software, such as (as applicable) : (i) a combination of analog and/or digital hardware circuit (s) with sof tware/f irmware and (ii) any portions of hardware processor (s) with software (including digital signal processor ( s ) ) , software, and memory (ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and (c) hardware circuit (s) and or processor ( s ) , such as a microprocessor ( s ) or a portion of a microprocessor ( s ) , that requires software (e.g. , firmware) for operation, but the software may not be present when it is not needed for operation." This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.

[00187] In accordance with one example embodiment, an apparatus may comprise means for performing: receiving a configuration for reporting high-priority uplink control information; receiving at least one downlink assignment; generating high-priority uplink control information; generating low-priority uplink control information; determining a payload size of uplink control information for transmission, wherein the payload size of the uplink control information for transmission may be based, at least partially, on a payload size of the high-priority uplink control information; selecting an uplink resource set based, at least partially, on the determined payload size and at least one of: the received configuration, or a received indication value; selecting a resource of the selected uplink resource set based, at least partially, on a resource index associated with the high-priority uplink control information; and transmitting at least one of : the high-priority uplink control information, or the low-priority uplink control information based, at least partially, on the received configuration and the selected resource.

[00188] In accordance with one example embodiment, a non- transitory computer-readable medium comprising program instructions stored thereon which, when executed with at least one processor, cause the at least one processor to: receive a configuration for reporting high-priority uplink control information; receive at least one downlink assignment; generate high-priority uplink control information; generate low-priority uplink control information; determine a payload size of uplink control information for transmission, wherein the payload size of the uplink control information for transmission may be based, at least partially, on a payload size of the high-priority uplink control information; select an uplink resource set based, at least partially, on the determined payload size and at least one of: the received configuration, or a received indication value; select a resource of the selected uplink resource set based, at least partially, on a resource index associated with the high-priority uplink control information; and transmit at least one of : the high- priority uplink control information, or the low-priority uplink control information based, at least partially, on the received configuration and the selected resource.

[00189] In accordance with one aspect, an example method may be provided comprising: receiving, at a user equipment, at least one downlink assignment, wherein the at least one downlink assignment comprises an indication of whether low-priority uplink control information is to be multiplexed on a high-priority uplink control information transmission; determining an uplink control information payload to be transmitted in an uplink channel based, at least partially, on the at least one downlink assignment; at least one of : where the indication indicates that the low-priority uplink control information is not to be multiplexed on the high- priority uplink control information transmission, determining a high-priority hybrid automatic repeat request codebook, an uplink resource set, and a number of resource blocks for the high-priority uplink control information transmission based on a first set of rules, or where the indication indicates that the low-priority uplink control information is to be multiplexed on the high- priority uplink control information transmission, determining the high-priority hybrid automatic repeat request codebook based on the first set of rules, and determining the uplink resource set and the number of resource blocks for the high-priority uplink control information transmission based on a second set of rules, wherein the second set of rules may be based, at least partially, on the indication; and performing transmission of the high- priority uplink control information transmission based on the determined high-priority hybrid automatic repeat request codebook, the determined uplink resource set, and the determined number of resource blocks.

[00190] In accordance with one example embodiment, an apparatus may comprise: at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to: receive at least one downlink assignment, wherein the at least one downlink assignment comprises an indication of whether low-priority uplink control information is to be multiplexed on a high-priority uplink control information transmission; determine an uplink control information payload to be transmitted in an uplink channel based, at least partially, on the at least one downlink assignment; at least one of: where the indication indicates that the low-priority uplink control information is not to be multiplexed on the high-priority uplink control information transmission, determine a high-priority hybrid automatic repeat request codebook, an uplink resource set, and a number of resource blocks for the high-priority uplink control information transmission based on a first set of rules, or where the indication indicates that the low-priority uplink control information is to be multiplexed on the high-priority uplink control information transmission, determine the high-priority hybrid automatic repeat request codebook based on the first set of rules, and determining the uplink resource set and the number of resource blocks for the high-priority uplink control information transmission based on a second set of rules, wherein the second set of rules may be based, at least partially, on the indication; and perform transmission of the high-priority uplink control information transmission based on the determined high-priority hybrid automatic repeat request codebook, the determined uplink resource set, and the determined number of resource blocks.

[00191] In accordance with one example embodiment, an apparatus may comprise: circuitry configured to perform: receiving at least one downlink assignment, wherein the at least one downlink assignment comprises an indication of whether low-priority uplink control information is to be multiplexed on a high-priority uplink control information transmission; determining an uplink control information payload to be transmitted in an uplink channel based, at least partially, on the at least one downlink assignment; at least one of : where the indication indicates that the low-priority uplink control information is not to be multiplexed on the high- priority uplink control information transmission, determining a high-priority hybrid automatic repeat request codebook, an uplink resource set, and a number of resource blocks for the high-priority uplink control information transmission based on a first set of rules, or where the indication indicates that the low-priority uplink control information is to be multiplexed on the high- priority uplink control information transmission, determining the high-priority hybrid automatic repeat request codebook based on the first set of rules, and determining the uplink resource set and the number of resource blocks for the high-priority uplink control information transmission based on a second set of rules, wherein the second set of rules may be based, at least partially, on the indication; and performing transmission of the high- priority uplink control information transmission based on the determined high-priority hybrid automatic repeat request codebook, the determined uplink resource set, and the determined number of resource blocks.

[00192] In accordance with one example embodiment, an apparatus may comprise means for performing: receiving at least one downlink assignment, wherein the at least one downlink assignment comprises an indication of whether low-priority uplink control information is to be multiplexed on a high-priority uplink control information transmission; determining an uplink control information payload to be transmitted in an uplink channel based, at least partially, on the at least one downlink assignment; at least one of: where the indication indicates that the low-priority uplink control information is not to be multiplexed on the high-priority uplink control information transmission, determining a high-priority hybrid automatic repeat request codebook, an uplink resource set, and a number of resource blocks for the high-priority uplink control information transmission based on a first set of rules, or where the indication indicates that the low-priority uplink control information is to be multiplexed on the high-priority uplink control information transmission, determining the high- priority hybrid automatic repeat request codebook based on the first set of rules, and determining the uplink resource set and the number of resource blocks for the high-priority uplink control information transmission based on a second set of rules, wherein the second set of rules may be based, at least partially, on the indication; and performing transmission of the high-priority uplink control information transmission based on the determined high-priority hybrid automatic repeat request codebook, the determined uplink resource set, and the determined number of resource blocks.

[00193] In accordance with one example embodiment, a non- transitory computer-readable medium comprising program instructions stored thereon which, when executed with at least one processor, cause the at least one processor to: receive at least one downlink assignment, wherein the at least one downlink assignment comprises an indication of whether low-priority uplink control information is to be multiplexed on a high-priority uplink control information transmission; determine an uplink control information payload to be transmitted in an uplink channel based, at least partially, on the at least one downlink assignment; at least one of : where the indication indicates that the low-priority uplink control information is not to be multiplexed on the high- priority uplink control information transmission, determine a high-priority hybrid automatic repeat request codebook, an uplink resource set, and a number of resource blocks for the high-priority uplink control information transmission based on a first set of rules, or where the indication indicates that the low-priority uplink control information is to be multiplexed on the high- priority uplink control information transmission, determine the high-priority hybrid automatic repeat request codebook based on the first set of rules, and determining the uplink resource set and the number of resource blocks for the high-priority uplink control information transmission based on a second set of rules, wherein the second set of rules may be based, at least partially, on the indication; and perform transmission of the high-priority uplink control information transmission based on the determined high-priority hybrid automatic repeat request codebook, the determined uplink resource set, and the determined number of resource blocks.

[00194] In accordance with one aspect, an example method may be provided comprising: transmitting, to a user equipment, a configuration for reporting high-priority uplink control information; transmitting at least one first downlink assignment; transmitting downlink data corresponding to the at least one first downlink assignment; determining an uplink resource set based, at least partially, on a payload size of expected high-priority uplink control information and a payload size of expected low-priority uplink control information; determining an indication for the determined uplink resource set; selecting a resource of the determined uplink resource set; determining a resource index associated with the selected resource; transmitting at least one second downlink assignment, wherein the at least one second downlink assignment may comprise the determined indication and the determined resource index; transmitting downlink data corresponding to the at least one second downlink assignment; and

[00195] receiving uplink data, from the user equipment, with the selected resource, wherein the received uplink data may be associated with the downlink data corresponding to the at least one first downlink assignment and the downlink data corresponding to the at least one second downlink assignment.

[00196] In accordance with one example embodiment, an apparatus may comprise: at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to: transmit a configuration for reporting high-priority uplink control information; transmit at least one first downlink assignment; transmit downlink data corresponding to the at least one first downlink assignment; determine an uplink resource set based, at least partially, on a payload size of expected high-priority uplink control information and a payload size of expected low-priority uplink control information; determine an indication for the determined uplink resource set; select a resource of the determined uplink resource set; determine a resource index associated with the selected resource; transmit at least one second downlink assignment, wherein the at least one second downlink assignment may comprise the determined indication and the determined resource index; transmit downlink data corresponding to the at least one second downlink assignment; and receive uplink data, from the user equipment, with the selected resource, wherein the received uplink data may be associated with the downlink data corresponding to the at least one first downlink assignment and the downlink data corresponding to the at least one second downlink assignment.

[00197] In accordance with one example embodiment, an apparatus may comprise: circuitry configured to perform: transmitting a configuration for reporting high-priority uplink control information; transmitting at least one first downlink assignment; transmitting downlink data corresponding to the at least one first downlink assignment; determining an uplink resource set based, at least partially, on a payload size of expected high-priority uplink control information and a payload size of expected low-priority uplink control information; determining an indication for the determined uplink resource set; selecting a resource of the determined uplink resource set; determining a resource index associated with the selected resource; transmitting at least one second downlink assignment, wherein the at least one second downlink assignment may comprise the determined indication and the determined resource index; transmitting downlink data corresponding to the at least one second downlink assignment; and receiving uplink data, from the user equipment, with the selected resource, wherein the received uplink data may be associated with the downlink data corresponding to the at least one first downlink assignment and the downlink data corresponding to the at least one second downlink assignment.

[00198] In accordance with one example embodiment, an apparatus may comprise means for performing: transmitting a configuration for reporting high-priority uplink control information; transmitting at least one first downlink assignment; transmitting downlink data corresponding to the at least one first downlink assignment; determining an uplink resource set based, at least partially, on a payload size of expected high-priority uplink control information and a payload size of expected low-priority uplink control information; determining an indication for the determined uplink resource set; selecting a resource of the determined uplink resource set; determining a resource index associated with the selected resource; transmitting at least one second downlink assignment, wherein the at least one second downlink assignment may comprise the determined indication and the determined resource index; transmitting downlink data corresponding to the at least one second downlink assignment; and receiving uplink data, from the user equipment, with the selected resource, wherein the received uplink data may be associated with the downlink data corresponding to the at least one first downlink assignment and the downlink data corresponding to the at least one second downlink assignment.

[00199] In accordance with one example embodiment, a non- transitory computer-readable medium comprising program instructions stored thereon which, when executed with at least one processor, cause the at least one processor to: transmit a configuration for reporting high-priority uplink control information; transmit at least one first downlink assignment; transmit downlink data corresponding to the at least one first downlink assignment; determine an uplink resource set based, at least partially, on a payload size of expected high-priority uplink control information and a payload size of expected low-priority uplink control information; determine an indication for the determined uplink resource set; select a resource of the determined uplink resource set; determine a resource index associated with the selected resource; transmit at least one second downlink assignment, wherein the at least one second downlink assignment may comprise the determined indication and the determined resource index; transmit downlink data corresponding to the at least one second downlink assignment; and receive uplink data, from the user equipment, with the selected resource, wherein the received uplink data may be associated with the downlink data corresponding to the at least one first downlink assignment and the downlink data corresponding to the at least one second downlink assignment.

[00200] In accordance with one aspect, an example method may be provided comprising: transmitting, to a user equipment, a configuration for reporting high-priority uplink control information, wherein the configuration may comprise an indication of at least one semi-static reservation value; transmitting at least one first downlink assignment; transmitting downlink data corresponding to the at least one first downlink assignment; determining an uplink resource set based, at least partially, on a payload size of expected high-priority uplink control information and the at least one semi-static reservation value; selecting a resource of the determined uplink resource set; determining a resource index associated with the selected resource; transmitting at least one second downlink assignment, wherein the at least one second downlink assignment may comprise an indication to perform uplink control information multiplexing, and the determined resource index; transmitting downlink data corresponding to the at least one second downlink assignment; and receiving uplink data, from the user equipment, with the selected resource, wherein the received uplink data may be associated with the downlink data corresponding to the at least one first downlink assignment and the downlink data corresponding to the at least one second downlink assignment. [00201] In accordance with one example embodiment, an apparatus may comprise: at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to: transmit a configuration for reporting high-priority uplink control information, wherein the configuration may comprise an indication of at least one semi- static reservation value; transmit at least one first downlink assignment; transmit downlink data corresponding to the at least one first downlink assignment; determine an uplink resource set based, at least partially, on a payload size of expected high- priority uplink control information and the at least one semi- static reservation value; select a resource of the determined uplink resource set; determine a resource index associated with the selected resource; transmit at least one second downlink assignment, wherein the at least one second downlink assignment may comprise an indication to perform uplink control information multiplexing, and the determined resource index; transmit downlink data corresponding to the at least one second downlink assignment; and receive uplink data, from the user equipment, with the selected resource, wherein the received uplink data may be associated with the downlink data corresponding to the at least one first downlink assignment and the downlink data corresponding to the at least one second downlink assignment.

[00202] In accordance with one example embodiment, an apparatus may comprise: circuitry configured to perform: transmitting a configuration for reporting high-priority uplink control information, wherein the configuration may comprise an indication of at least one semi-static reservation value; transmitting at least one first downlink assignment; transmitting downlink data corresponding to the at least one first downlink assignment; determining an uplink resource set based, at least partially, on a payload size of expected high-priority uplink control information and the at least one semi-static reservation value; selecting a resource of the determined uplink resource set; determining a resource index associated with the selected resource; transmitting at least one second downlink assignment, wherein the at least one second downlink assignment may comprise an indication to perform uplink control information multiplexing, and the determined resource index; transmitting downlink data corresponding to the at least one second downlink assignment; and receiving uplink data, from the user equipment, with the selected resource, wherein the received uplink data may be associated with the downlink data corresponding to the at least one first downlink assignment and the downlink data corresponding to the at least one second downlink assignment.

[00203] In accordance with one example embodiment, an apparatus may comprise means for performing: transmitting a configuration for reporting high-priority uplink control information, wherein the configuration may comprise an indication of at least one semi- static reservation value; transmitting at least one first downlink assignment; transmitting downlink data corresponding to the at least one first downlink assignment; determining an uplink resource set based, at least partially, on a payload size of expected high-priority uplink control information and the at least one semi-static reservation value; selecting a resource of the determined uplink resource set; determining a resource index associated with the selected resource; transmitting at least one second downlink assignment, wherein the at least one second downlink assignment may comprise an indication to perform uplink control information multiplexing, and the determined resource index; transmitting downlink data corresponding to the at least one second downlink assignment; and receiving uplink data, from the user equipment, with the selected resource, wherein the received uplink data may be associated with the downlink data corresponding to the at least one first downlink assignment and the downlink data corresponding to the at least one second downlink assignment .

[00204] In accordance with one example embodiment, a non- transitory computer-readable medium comprising program instructions stored thereon which, when executed with at least one processor, cause the at least one processor to: transmit a configuration for reporting high-priority uplink control information, wherein the configuration may comprise an indication of at least one semi-static reservation value; transmit at least one first downlink assignment; transmit downlink data corresponding to the at least one first downlink assignment; determine an uplink resource set based, at least partially, on a payload size of expected high-priority uplink control information and the at least one semi-static reservation value; select a resource of the determined uplink resource set; determine a resource index associated with the selected resource; transmit at least one second downlink assignment, wherein the at least one second downlink assignment may comprise an indication to perform uplink control information multiplexing, and the determined resource index; transmit downlink data corresponding to the at least one second downlink assignment; and receive uplink data, from the user equipment, with the selected resource, wherein the received uplink data may be associated with the downlink data corresponding to the at least one first downlink assignment and the downlink data corresponding to the at least one second downlink assignment .

[00205] In accordance with one aspect, an example method may be provided comprising: transmitting, to a user equipment, a configuration for reporting high-priority uplink control information; transmitting at least one first downlink assignment; transmitting downlink data corresponding to the at least one first downlink assignment; determining an uplink resource set based, at least partially, on a payload size of expected high-priority uplink control information and a payload size of expected low-priority uplink control information; selecting a resource of the determined uplink resource set; determining a resource index associated with the selected resource; transmitting at least one second downlink assignment, wherein the at least one second downlink assignment may comprise the determined resource index, and a joint indication to perform uplink control information multiplexing and for a downlink assignment index associated with, at least, the at least one first downlink assignment; transmitting downlink data corresponding to the at least one second downlink assignment; and receiving uplink data, from the user equipment, with the selected resource, wherein the received uplink data may be associated with the downlink data corresponding to the at least one first downlink assignment and the downlink data corresponding to the at least one second downlink assignment.

[00206] In accordance with one example embodiment, an apparatus may comprise: at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to: transmit a configuration for reporting high-priority uplink control information; transmit at least one first downlink assignment; transmit downlink data corresponding to the at least one first downlink assignment; determine an uplink resource set based, at least partially, on a payload size of expected high-priority uplink control information and a payload size of expected low-priority uplink control information; select a resource of the determined uplink resource set; determine a resource index associated with the selected resource; transmit at least one second downlink assignment, wherein the at least one second downlink assignment may comprise the determined resource index, and a joint indication to perform uplink control information multiplexing and for a downlink assignment index associated with, at least, the at least one first downlink assignment; transmit downlink data corresponding to the at least one second downlink assignment; and receive uplink data, from the user equipment, with the selected resource, wherein the received uplink data may be associated with the downlink data corresponding to the at least one first downlink assignment and the downlink data corresponding to the at least one second downlink assignment .

[00207] In accordance with one example embodiment, an apparatus may comprise: circuitry configured to perform: transmitting a configuration for reporting high-priority uplink control information; transmitting at least one first downlink assignment; transmitting downlink data corresponding to the at least one first downlink assignment; determining an uplink resource set based, at least partially, on a payload size of expected high-priority uplink control information and a payload size of expected low-priority uplink control information; selecting a resource of the determined uplink resource set; determining a resource index associated with the selected resource; transmitting at least one second downlink assignment, wherein the at least one second downlink assignment may comprise the determined resource index, and a joint indication to perform uplink control information multiplexing and for a downlink assignment index associated with, at least, the at least one first downlink assignment; transmitting downlink data corresponding to the at least one second downlink assignment; and receiving uplink data, from the user equipment, with the selected resource, wherein the received uplink data may be associated with the downlink data corresponding to the at least one first downlink assignment and the downlink data corresponding to the at least one second downlink assignment.

[00208] In accordance with one example embodiment, an apparatus may comprise means for performing: transmitting a configuration for reporting high-priority uplink control information; transmitting at least one first downlink assignment; transmitting downlink data corresponding to the at least one first downlink assignment; determining an uplink resource set based, at least partially, on a payload size of expected high-priority uplink control information and a payload size of expected low-priority uplink control information; selecting a resource of the determined uplink resource set; determining a resource index associated with the selected resource; transmitting at least one second downlink assignment, wherein the at least one second downlink assignment may comprise the determined resource index, and a joint indication to perform uplink control information multiplexing and for a downlink assignment index associated with, at least, the at least one first downlink assignment; transmitting downlink data corresponding to the at least one second downlink assignment; and receiving uplink data, from the user equipment, with the selected resource, wherein the received uplink data may be associated with the downlink data corresponding to the at least one first downlink assignment and the downlink data corresponding to the at least one second downlink assignment.

[00209] In accordance with one example embodiment, a non- transitory computer-readable medium comprising program instructions stored thereon which, when executed with at least one processor, cause the at least one processor to: transmit a configuration for reporting high-priority uplink control information; transmit at least one first downlink assignment; transmit downlink data corresponding to the at least one first downlink assignment; determine an uplink resource set based, at least partially, on a payload size of expected high-priority uplink control information and a payload size of expected low-priority uplink control information; select a resource of the determined uplink resource set; determine a resource index associated with the selected resource; transmit at least one second downlink assignment, wherein the at least one second downlink assignment may comprise the determined resource index, and a joint indication to perform uplink control information multiplexing and for a downlink assignment index associated with, at least, the at least one first downlink assignment; transmit downlink data corresponding to the at least one second downlink assignment; and receive uplink data, from the user equipment, with the selected resource, wherein the received uplink data may be associated with the downlink data corresponding to the at least one first downlink assignment and the downlink data corresponding to the at least one second downlink assignment. [00210] It should be understood that the foregoing description is only illustrative. Various alternatives and modifications can be devised by those skilled in the art. For example, features recited in the various dependent claims could be combined with each other in any suitable combination ( s ) . In addition, features from different embodiments described above could be selectively combined into a new embodiment. Accordingly, the description is intended to embrace all such alternatives, modification and variances which fall within the scope of the appended claims.

Claims

CLAIMS What is claimed is:

1. An apparatus comprising: at least one processor; and at least one non-transitory memory and computer program code, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to: receive a configuration for reporting high-priority uplink control information; receive at least one downlink assignment; generate high-priority uplink control information; generate low-priority uplink control information; determine a payload size of uplink control information for transmission, wherein the payload size of the uplink control information for transmission is based, at least partially, on a payload size of the high-priority uplink control information; select an uplink resource set based, at least partially, on the determined payload size and at least one of : the received configuration, or a received indication value; select a resource of the selected uplink resource set based, at least partially, on a resource index associated with the high-priority uplink control information; and transmit at least one of: the high-priority uplink control information, or the low-priority uplink control information based, at least partially, on the received configuration and the selected resource.

2. The apparatus of claim 1, wherein the at least one downlink assignment schedules downlink data associated with a high- priority hybrid automatic repeat request.

3. The apparatus of claim 1 or 2, wherein the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to: based, at least partially, on the at least one downlink assignment, determine whether to perform multiplexing of the high-priority uplink control information with the low-priority uplink control information for uplink transmission .

4. The apparatus of any of claims 1 through 3, wherein the at least one downlink assignment comprises a flag, wherein determining whether to perform multiplexing of the high- priority uplink control information with the low-priority uplink control information for uplink transmission is based, at least partially, on the flag.

5. The apparatus of claim 3 or 4, wherein the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to: multiplex, in response to a determination to perform the multiplexing, the high-priority uplink control information and the low-priority uplink control information to form a multiplexed uplink control information, wherein transmitting at least one of the high-priority uplink control information or the low- priority uplink control information comprises transmitting the multiplexed uplink control information.

6. The apparatus of any of claims 1 through 5, wherein the at least one downlink assignment comprises the received indication value, wherein the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to: determine a first value based on the payload size of the high-priority uplink control information and a payload size of the low-priority uplink control information; and compare the received indication value with the determined first value.

7. The apparatus of claim 6, where the determined first value is different from the received indication value, wherein the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to: add at least one negative acknowledgement to the low- priority uplink control information and update the determined first value based on adding the at least one negative acknowledgement.

8. The apparatus of claim 6 or 7, wherein the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to: determine one or more resource blocks based on the payload size of the high-priority uplink control information and a payload size of the low-priority uplink control information, wherein transmitting at least one of the high-priority uplink control information or the low-priority uplink control information comprises transmitting with the one or more determined resource blocks.

9. The apparatus of any of claims 1 through 5, wherein the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to: receive a configuration of at least one semi-static reservation value.

10. The apparatus of claim 9, wherein determining whether to perform multiplexing of the high-priority uplink control information with the low-priority uplink control information for uplink transmission results in a determination that multiplexing is not to be performed, wherein transmitting at least one of the high-priority uplink control information or the low-priority uplink control information comprises transmitting the high-priority uplink control information and not the low-priority uplink control information, wherein the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to: determine one or more resource blocks based on the payload size of the high-priority uplink control information, wherein transmitting the high-priority uplink control information comprises transmitting the high-priority uplink control information with the one or more determined resource blocks.

11. The apparatus of claim 9 or 10, wherein determining whether to perform multiplexing of the high-priority uplink control information with the low-priority uplink control information for uplink transmission results in a determination that multiplexing is to be performed, wherein the determined payload size is further based on the at least one semi-static reservation value.

12. The apparatus of any of claims 9 through 11, wherein the at least one downlink assignment comprises a value configured to indicate one of a plurality of configured semi-static reservation values as the at least one semi-static reservation value.

13. The apparatus of any of claims 1 through 5, wherein the received indication value comprises at least a first indication .

14. The apparatus of claim 13, wherein the at least one downlink assignment comprises the received indication value, wherein determining whether to perform multiplexing of the high-priority uplink control information with the low- priority uplink control information for uplink transmission is based, at least partially, on a value of the first indication .

15. The apparatus of claim 13 or 14, wherein the first indication is configured to indicate a number of acknowledgements for low-priority downlink data the low- priority uplink control information comprises.

16. The apparatus of claim 15, wherein at least one of the at least one downlink assignment comprises an indication of a downlink assignment index, wherein the number of acknowledgements is further based on the indication of the downlink assignment index.

17. The apparatus of claim 16, wherein the at least one downlink assignment comprising the indication of the downlink assignment index schedules downlink data associated with a low-priority hybrid automatic repeat request.

18. The apparatus of any of claims 13 through 17, wherein the first indication is configured to identify one or more sub- codebooks for transmitting uplink data.

19. The apparatus of any of claims 13 through 18, wherein the first indication is configured to indicate a codebook size of a low-priority sub-codebook comprised in the low-priority uplink control information.

20. The apparatus of any of claims 13 through 19, wherein determining whether to perform multiplexing of the high- priority uplink control information with the low-priority uplink control information for uplink transmission results in a determination that multiplexing is to be performed, wherein the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to: determine a codebook for the low-priority uplink control information, wherein the determined payload size is further based on a payload size of the low-priority uplink control information.

21. The apparatus of any of claims 13 through 20, wherein determining whether to perform multiplexing of the high- priority uplink control information with the low-priority uplink control information for uplink transmission results in a determination that multiplexing is not to be performed, wherein transmitting at least one of the high-priority uplink control information or the low-priority uplink control information comprises transmitting the high-priority uplink control information and not the low-priority uplink control information, wherein the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to: determine one or more resource blocks based on the payload size of the high-priority uplink control information, wherein transmitting the high-priority uplink control information comprises transmitting the high-priority uplink control information with the one or more determined resource blocks.

22. The apparatus of any of claims 13 through 21, wherein determining whether to perform multiplexing of the high- priority uplink control information with the low-priority uplink control information for uplink transmission results in a determination that multiplexing is to be performed, wherein transmitting at least one of the high-priority uplink control information or the low-priority uplink control information comprises transmitting the high-priority uplink control information and the low-priority uplink control information.

23. The apparatus of any of claims 13 through 22, wherein transmitting at least one of the high-priority uplink control information or the low-priority uplink control information comprises transmitting with one or more resource blocks configured for the selected resource of the selected uplink resource set.

24. A method comprising: receiving a configuration for reporting high-priority uplink control information; receiving at least one downlink assignment; generating high-priority uplink control information; generating low-priority uplink control information; determining a payload size of uplink control information for transmission, wherein the payload size of the uplink control information for transmission is based, at least partially, on a payload size of the high-priority uplink control information; selecting an uplink resource set based, at least partially, on the determined payload size and at least one of : the received configuration, or a received indication value; selecting a resource of the selected uplink resource set based, at least partially, on a resource index associated with the high-priority uplink control information; and transmitting at least one of: the high-priority uplink control information, or the low-priority uplink control information based, at least partially, on the received configuration and the selected resource.

25. The method of claim 24, wherein the at least one downlink assignment schedules downlink data associated with a high- priority hybrid automatic repeat request.

26. The method of claim 24 or 25, further comprising: based, at least partially, on the at least one downlink assignment, determining whether to perform multiplexing of the high-priority uplink control information with the low-priority uplink control information for uplink transmission .

27. The method of any of claims 24 through 26, wherein the at least one downlink assignment comprises a flag, wherein the determining of whether to perform multiplexing of the high- priority uplink control information with the low-priority uplink control information for uplink transmission is based, at least partially, on the flag.

28. The method of claim 26 or 27, further comprising: multiplexing, in response to a determination to perform the multiplexing, the high-priority uplink control information and the low-priority uplink control information to form a multiplexed uplink control information, wherein the transmitting of at least one of the high-priority uplink control information or the low- priority uplink control information comprises transmitting the multiplexed uplink control information.

29. The method of any of claims 24 through 28, wherein the at least one downlink assignment comprises the received indication value, further comprising: determining a first value based on the payload size of the high-priority uplink control information and a payload size of the low-priority uplink control information; and comparing the received indication value with the determined first value.

30. The method of claim 29, where the determined first value is different from the received indication value, further comprising : adding at least one negative acknowledgement to the low- priority uplink control information and updating the determined first value based on the adding of the at least one negative acknowledgement.

31. The method of claim 29 or 30, further comprising determining one or more resource blocks based on the payload size of the high-priority uplink control information and a payload size of the low-priority uplink control information, wherein the transmitting of at least one of the high-priority uplink control information or the low-priority uplink control information comprises transmitting with the one or more determined resource blocks.

32. The method of any of claims 24 through 28, further comprising receiving a configuration of at least one semi- static reservation value.

33. The method of claim 32, wherein the determining of whether to perform multiplexing of the high-priority uplink control information with the low-priority uplink control information for uplink transmission results in a determination that multiplexing is not to be performed, wherein the transmitting of at least one of the high-priority uplink control information or the low-priority uplink control information comprises transmitting the high-priority uplink control information and not the low-priority uplink control information, further comprising: determining one or more resource blocks based on the payload size of the high-priority uplink control information, wherein the transmitting of the high- priority uplink control information comprises transmitting the high-priority uplink control information with the one or more determined resource blocks .

34. The method of claim 32 or 33, wherein the determining of whether to perform multiplexing of the high-priority uplink control information with the low-priority uplink control information for uplink transmission results in a determination that multiplexing is to be performed, wherein the determined payload size is further based on the at least one semi-static reservation value.

35. The method of any of claims 32 through 34, wherein the at least one downlink assignment comprises a value configured to indicate one of a plurality of configured semi-static reservation values as the at least one semi-static reservation value.

36. The method of any of claims 24 through 28, wherein the received indication value comprises at least a first indication .

37. The method of claim 36, wherein the at least one downlink assignment comprises the received indication value, wherein the determining of whether to perform multiplexing of the high-priority uplink control information with the low- priority uplink control information for uplink transmission is based, at least partially, on a value of the first indication .

38. The method of claim 36 or 37, wherein the first indication is configured to indicate a number of acknowledgements for low-priority downlink data the low-priority uplink control information comprises.

39. The method of claim 38, wherein at least one of the at least one downlink assignment comprises an indication of a downlink assignment index, wherein the number of acknowledgements is further based on the indication of the downlink assignment index.

40. The method of claim 39, wherein the at least one downlink assignment comprising the indication of the downlink assignment index schedules downlink data associated with a low-priority hybrid automatic repeat request.

41. The method of any of claims 36 through 40, wherein the first indication is configured to identify one or more sub- codebooks for transmitting uplink data.

42. The method of any of claims 36 through 41, wherein the first indication is configured to indicate a codebook size of a low-priority sub-codebook comprised in the low-priority uplink control information.

43. The method of any of claims 36 through 42, wherein the determining of whether to perform multiplexing of the high- priority uplink control information with the low-priority uplink control information for uplink transmission results in a determination that multiplexing is to be performed, further comprising : determining a codebook for the low-priority uplink control information, wherein the determined payload size is further based on a payload size of the low-priority uplink control information .

44. The method of any of claims 36 through 43, wherein the determining of whether to perform multiplexing of the high- priority uplink control information with the low-priority uplink control information for uplink transmission results in a determination that multiplexing is not to be performed, wherein the transmitting of at least one of the high-priority uplink control information or the low-priority uplink control information comprises transmitting the high-priority uplink control information and not the low-priority uplink control information, further comprising: determining one or more resource blocks based on the payload size of the high-priority uplink control information, wherein the transmitting of the high- priority uplink control information comprises transmitting the high-priority uplink control information with the one or more determined resource blocks .

45. The method of any of claims 36 through 44, wherein the determining of whether to perform multiplexing of the high- priority uplink control information with the low-priority uplink control information for uplink transmission results in a determination that multiplexing is to be performed, wherein the transmitting of at least one of the high-priority uplink control information or the low-priority uplink control information comprises transmitting the high-priority uplink control information and the low-priority uplink control information .

46. The method of any of claims 36 through 45, wherein the transmitting of at least one of the high-priority uplink control information or the low-priority uplink control information comprises transmitting with one or more resource blocks configured for the selected resource of the selected uplink resource set.

47. An apparatus comprising means for performing: receiving a configuration for reporting high-priority uplink control information; receiving at least one downlink assignment; generating high-priority uplink control information; generating low-priority uplink control information; determining a payload size of uplink control information for transmission, wherein the payload size of the uplink control information for transmission is based, at least partially, on a payload size of the high-priority uplink control information; selecting an uplink resource set based, at least partially, on the determined payload size and at least one of : the received configuration, or a received indication value; selecting a resource of the selected uplink resource set based, at least partially, on a resource index associated with the high-priority uplink control information; and transmitting at least one of: the high-priority uplink control information, or the low-priority uplink control information based, at least partially, on the received configuration and the selected resource.

48. A non- transitory computer-readable medium comprising program instructions stored thereon which, when executed with at least one processor, cause the at least one processor to: receive a configuration for reporting high-priority uplink control information; receive at least one downlink assignment; generate high-priority uplink control information; generate low-priority uplink control information; determine a payload size of uplink control information for transmission, wherein the payload size of the uplink control information for transmission is based, at least partially, on a payload size of the high-priority uplink control information; select an uplink resource set based, at least partially, on the determined payload size and at least one of: the received configuration, or a received indication value; select a resource of the selected uplink resource set based, at least partially, on a resource index associated with the high-priority uplink control information; and transmit at least one of: the high-priority uplink control information, or the low-priority uplink control information based, at least partially, on the received configuration and the selected resource.

49. An apparatus comprising: at least one processor; and at least one non-transitory memory and computer program code, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to: transmit a configuration for reporting high- priority uplink control information; transmit at least one first downlink assignment; transmit downlink data corresponding to the at least one first downlink assignment; determine an uplink resource set based, at least partially, on a payload size of expected high- priority uplink control information and a payload size of expected low-priority uplink control information; determine an indication for the determined uplink resource set; select a resource of the determined uplink resource set; determine a resource index associated with the selected resource; transmit at least one second downlink assignment, wherein the at least one second downlink assignment comprises the determined indication and the determined resource index; transmit downlink data corresponding to the at least one second downlink assignment; and receive uplink data, from the user equipment, with the selected resource, wherein the received uplink data is associated with the downlink data corresponding to the at least one first downlink assignment and the downlink data corresponding to the at least one second downlink assignment.