A user equipment, UE, for configuring Physical Uplink Control Channel, PUCCH, resources, the UE comprising: a processor; and a memory coupled to the processor, wherein the memory stores a computer-executable program that, when executed by the processor, causes the UE to: receive a first bandwidth part, BWP, configuration associated with a first uplink, UL, BWP, the first BWP configuration including a PUCCH-ConfigList information element, IE, as a PUCCH configuration list, which includes a first PUCCH-Config IE and a second PUCCH-Config IE, the first PUCCH-Config IE indicating a first set of PUCCH resource identifiers, IDs, the second PUCCH-Config IE indicating a second set of PUCCH resource IDs; and receive a second BWP configuration associated with a second UL BWP, the second BWP configuration including a third PUCCH-Config IE, the third PUCCH-Config IE indicating a third set of PUCCH resource IDs, wherein: each PUCCH resource ID in the first and second set of PUCCH resource IDs is associated with a respective PUCCH spatial relation information ID, a first PUCCH resource selected from the first set of PUCCH resource IDs for transmitting a first hybrid automatic repeat request acknowledgement, HARQ-ACK, codebook corresponds to a low priority, a second PUCCH resource selected from the second set of PUCCH resource IDs for transmitting a second HARQ-ACK codebook corresponds to a high priority, the first set of PUCCH resource IDs and the second set of PUCCH resource IDs share no common PUCCH resource ID, and the first set of PUCCH resource IDs shares at least one PUCCH resource ID with the third set of PUCCH resource IDs. a processor; and a memory coupled to the processor, wherein the memory stores a computer-executable program that, when executed by the processor, causes the UE to: receive a first bandwidth part, BWP, configuration associated with a first uplink, UL, BWP, the first BWP configuration including a PUCCH-ConfigList information element, IE, as a PUCCH configuration list, which includes a first PUCCH-Config IE and a second PUCCH-Config IE, the first PUCCH-Config IE indicating a first set of PUCCH resource identifiers, IDs, the second PUCCH-Config IE indicating a second set of PUCCH resource IDs; and receive a second BWP configuration associated with a second UL BWP, the second BWP configuration including a third PUCCH-Config IE, the third PUCCH-Config IE indicating a third set of PUCCH resource IDs, wherein: each PUCCH resource ID in the first and second set of PUCCH resource IDs is associated with a respective PUCCH spatial relation information ID, a first PUCCH resource selected from the first set of PUCCH resource IDs for transmitting a first hybrid automatic repeat request acknowledgement, HARQ-ACK, codebook corresponds to a low priority, a second PUCCH resource selected from the second set of PUCCH resource IDs for transmitting a second HARQ-ACK codebook corresponds to a high priority, the first set of PUCCH resource IDs and the second set of PUCCH resource IDs share no common PUCCH resource ID, and the first set of PUCCH resource IDs shares at least one PUCCH resource ID with the third set of PUCCH resource IDs. receive a first bandwidth part, BWP, configuration associated with a first uplink, UL, BWP, the first BWP configuration including a PUCCH-ConfigList information element, IE, as a PUCCH configuration list, which includes a first PUCCH-Config IE and a second PUCCH-Config IE, the first PUCCH-Config IE indicating a first set of PUCCH resource identifiers, IDs, the second PUCCH-Config IE indicating a second set of PUCCH resource IDs; and receive a second BWP configuration associated with a second UL BWP, the second BWP configuration including a third PUCCH-Config IE, the third PUCCH-Config IE indicating a third set of PUCCH resource IDs, wherein: each PUCCH resource ID in the first and second set of PUCCH resource IDs is associated with a respective PUCCH spatial relation information ID, a first PUCCH resource selected from the first set of PUCCH resource IDs for transmitting a first hybrid automatic repeat request acknowledgement, HARQ-ACK, codebook corresponds to a low priority, a second PUCCH resource selected from the second set of PUCCH resource IDs for transmitting a second HARQ-ACK codebook corresponds to a high priority, the first set of PUCCH resource IDs and the second set of PUCCH resource IDs share no common PUCCH resource ID, and the first set of PUCCH resource IDs shares at least one PUCCH resource ID with the third set of PUCCH resource IDs. each PUCCH resource ID in the first and second set of PUCCH resource IDs is associated with a respective PUCCH spatial relation information ID, a first PUCCH resource selected from the first set of PUCCH resource IDs for transmitting a first hybrid automatic repeat request acknowledgement, HARQ-ACK, codebook corresponds to a low priority, a second PUCCH resource selected from the second set of PUCCH resource IDs for transmitting a second HARQ-ACK codebook corresponds to a high priority, the first set of PUCCH resource IDs and the second set of PUCCH resource IDs share no common PUCCH resource ID, and the first set of PUCCH resource IDs shares at least one PUCCH resource ID with the third set of PUCCH resource IDs.