WO2020108333A1

WO2020108333A1 - Multiple physical uplink control channel (pucch) resources for an uplink control information (uci) report

Info

Publication number: WO2020108333A1
Application number: PCT/CN2019/119071
Authority: WO
Inventors: Cheng-Rung Tsai
Original assignee: Mediatek Inc.
Priority date: 2018-11-27
Filing date: 2019-11-18
Publication date: 2020-06-04
Also published as: TW202025825A; TWI756586B; CN111492710A

Abstract

A method for a user equipment (UE) to report an uplink control information (UCI) report based on multiple physical uplink control channel (PUCCH) resources configured to the UE is described. The UE can receive configuration information of PUCCH resources and one or more PUCCH resource sets from a base station (BS) in a wireless communication system, and an index from a PUCCH resource indicator field in a downlink control information (DCI) providing a downlink transmission. The UE can determine one or more PUCCH resource sets from the configured one or more PUCCH resource sets based on a payload size of a UCI including a hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback of the downlink transmission. The UE can further determine multiple PUCCH resources from the determined one or more PUCCH resource sets based on the received index, and transmit the UCI on one of the determined multiple PUCCH resources.

Description

MULTIPLE PHYSICAL UPLINK CONTROL CHANNEL (PUCCH) RESOURCES FOR AN UPLINK CONTROL INFORMATION (UCI) REPORT

INCORPORATION BY REFERENCE

This present application claims the benefit of U.S. Provisional Application No. 62/771,634, “Multiple PUCCH Resources for Uplink Control Information Reporting” filed on November 27, 2018, which is incorporated herein by reference in its entirety.

TECHNICAL FIELD

The present disclosure relates to wireless communications, and specifically relates to physical uplink control channel (PUCCH) resource configuration for uplink control information (UCI) reporting.

BACKGROUND

The background description provided herein is for the purpose of generally presenting the context of the disclosure. Work of the presently named inventors, to the extent the work is described in this background section, as well as aspects of the description that may not otherwise qualify as prior art at the time of filing, are neither expressly nor impliedly admitted as prior art against the present disclosure.

Uplink L1/L2 control signaling can be used to support data transmission on downlink or uplink transport channels. In Long Term Evolution (LTE) or New Radio (NR) networks, uplink control information (UCI) can be transmitted over resources specifically assigned for uplink L1/L2 control on physical uplink control channel (PUCCH) . The UCI can include hybrid automatic repeat request acknowledgements (HARQ-ACKs) for received downlink shared channel (DL-SCH) transport blocks, channel state information (CSI) related to downlink channel conditions useful for downlink scheduling, and scheduling requests (SRs) indicating a device needs uplink resources for uplink shared channel (UP-SCH) transmission.

SUMMARY

Aspects of the disclosure provide a method for a user equipment (UE) to report an uplink control information (UCI) report based on multiple physical uplink control channel (PUCCH) resources configured to the UE. In an embodiment, a UE receives configuration information of PUCCH resources and one or more PUCCH resource sets from a base station (BS) in a wireless communication system. The UE further receives an index from a PUCCH resource indicator field in a downlink control information (DCI) providing a downlink transmission. The UE can determine one or more PUCCH resource sets from the configured one or more PUCCH resource sets based on a payload size of a UCI including a hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback of the downlink transmission. The UE can further determine multiple PUCCH resources from the determined one or more PUCCH resource sets based on the received index, and transmit the UCI on one of the determined multiple PUCCH resources.

In an example, the multiple determined PUCCH resources are distributed over different subbands.

In an embodiment, the UE receives the configuration information of the one or more PUCCH resource sets each including a first resource list, and determines a first PUCCH resource set from the configured one or more PUCCH resource sets based on the payload size of the UCI including the HARQ-ACK feedback of the downlink transmission. The UE determines the multiple PUCCH resources from the first resource list in the first PUCCH resource set based on the received index according to an index-to-PUCCH resource mapping rule.

In an embodiment, the UE receives the configuration information of the one or more PUCCH resource sets each including multiple second resource lists, and determines a second PUCCH resource set from the configured one or more PUCCH resource sets based on the payload size of the UCI including the HARQ-ACK feedback of the downlink transmission. The UE further determines the multiple PUCCH resources from the multiple second resource lists in the second PUCCH resource set based on the received index. In an example, each of the multiple PUCCH resources is from a different one of the multiple second resource lists, and is associated with the received index.

In an embodiment, the UE receives the configuration information of the one or more PUCCH resource sets each including a third resource list, wherein at least two of the one or more PUCCH resource sets are configured with a same maximum UCI payload size, and determines multiple third PUCCH resource sets from the configured one or more PUCCH resource sets based on the payload size of the UCI including the HARQ-ACK feedback of the downlink transmission, wherein the multiple third PUCCH resource sets have a same maximum UCI payload size. The UE may further determines the multiple PUCCH resources from the multiple third resource lists in the multiple third PUCCH resource sets based on the received index. In an example, each of the multiple PUCCH resources is from a different one of the multiple third resource lists, and associated with the received index.

In an embodiment, the UE can receive the configuration information of the one or more PUCCH resource sets each including a fourth resource list, each fourth resource list including multiple PUCCH resource candidate sets each including multiple PUCCH resources. The UE can further a fourth PUCCH resource set from the configured one or more PUCCH resource sets based on the payload size of the UCI including the HARQ-ACK feedback of the downlink transmission. The UE can further determine a first PUCCH resource candidate set from the fourth resource list in the determined fourth PUCCH resource set based on the received index, the multiple PUCCH resources included in the first PUCCH resource candidate set being the determined multiple PUCCH resources.

Aspects of the disclosure further provide apparatuses and non-transitory computer-readable media for providing multiple PUCCH resources for a UCI report.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of this disclosure that are proposed as examples will be described in detail with reference to the following figures, wherein like numerals reference like elements, and wherein:

FIG. 1 shows a wireless communication system 100 and an uplink control information (UCI) reporting process 130 according to some embodiments of the disclosure;

FIG. 2A shows a scenario where the system 100 operates over an unlicensed band 201;

FIG. 2B shows a scenario where multiple candidate physical uplink control channel (PUCCH) resources 230-233 are configured that are distributed in the different subbands 210-213, respectively;

FIG. 3 shows examples of a PUCCH resource configuration 320, a resource format configuration 330, and a PUCCH resource 301;

FIG. 4 shows an example of a PUCCH resource set configuration 400 for hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback;

FIG. 5 shows an example of a procedure 500 for the UE 110 to determine which PUCCH resource from a selected PUCCH resource set 510 should be used for a HARQ-ACK feedback;

FIG. 6 shows an example process 600 for providing a single PUCCH resource for a HARQ-ACK feedback;

FIG. 7 shows a HARQ-ACK feedback process 700 according to an embodiment of the disclosure;

FIG. 8 shows an example of the index-to-PUCCH resource mapping rule according to an embodiment of the disclosure;

FIG. 9 shows another HARQ-ACK feedback process 900 according to an embodiment of the disclosure;

FIG. 10 shows an example of determining multiple PUCCH resources from multiple resource lists in a selected PUCCH resource set 1010;

FIG. 11 shows another example of determining multiple PUCCH resources from multiple resource lists in a selected PUCCH resource set 1110;

FIG. 12 shows another HARQ-ACK feedback process 1200 according to an embodiment of the disclosure;

FIG. 13 shows an example of determination of multiple PUCCH resources from multiple selected PUCCH resource sets 1310-1320;

FIG. 14 shows another example of determination of multiple PUCCH resources from multiple selected PUCCH resource sets 1410a-1410n;

FIG. 15 shows another HARQ-ACK feedback process 1500 according to an embodiment of the disclosure;

FIG. 16 shows an example of determination of a PUCCH resource candidate set from a selected PUCCH resource set 1610;

FIG. 17 shows an example process 1700 for providing multiple PUCCH resources for a HARQ-ACK feedback according to some embodiments of the disclosure;

FIG. 18 shows an example of a channel state information (CSI) report configuration 1800;

FIG. 19 shows an example process 1900 for providing a PUCCH resource for a CSI report;

FIG. 20 shows a CSI reporting process 2000 according to an embodiment of the disclosure;

FIG. 21 shows an example CSI report configuration 2100 in which multiple PUCCH resources are configured for one bandwidth part (BWP) ;

FIG. 22 shows another CSI report process 2200 according to an embodiment of the disclosure;

FIG. 23 shows an example of a CSI report configuration 2300 that includes multiple PUCCH CSI resource lists 2310-2330;

FIG. 24 shows an example process 2400 for providing multiple PUCCH resources for a CSI report according to some embodiments of the disclosure; and

FIG. 25 shows an example apparatus 2500 according to embodiments of the disclosure.

DETAILED DESCRIPTION OF EMBODIMENTS

I. Multiple PUCCH resources for a UCI report

FIG. 1 shows a wireless communication system 100 according to some embodiments of the disclosure. The system 100 can include a user equipment (UE) 110 and a base station (BS) 120. In some examples, the system 100 employs the fifth-generation (5G) New Radio (NR) air interface developed by the 3rd Generation Partnership Project (3GPP) . In some examples, the system 100 employs other wireless communication technologies developed by various standard development organizations. In some examples, the system 100 employs non-standardized wireless communication technologies.

In some examples, the BS 120 can be a base station implementing a gNB node as specified in the 5G NR air interface standards developed by 3GPP. In one example, the BS 120 can be configured to control one or more antenna arrays to form directional Tx or Rx beams for transmitting or receiving wireless signals. The UE 110 can be a mobile phone, a laptop computer, a vehicle carried mobile communication device, a utility meter fixed at a certain location, and the like. Similarly, the UE 110 can employ one or more antenna arrays to generate directional Tx or Rx beams for transmitting or receiving wireless signals in one example. Depending on the air interface between the BS 120 and the UE 110, the BS 120 and the UE 110 can communicate with each other according to respective communication protocols.

In various embodiments, the UE 110 can transmit (or report) uplink control information (UCI) over a physical uplink control channel (PUCCH) to support data transmission on downlink or uplink transport channels. The UCI can include hybrid automatic repeat request acknowledgements (HARQ-ACKs) for received downlink shared channel (DL-SCH) transport blocks (or transport sub-blocks when code block grouping (CBG) is used) , channel state information (CSI) related to downlink channel conditions useful for downlink scheduling, and scheduling requests (SRs) indicating the UE 110 needs uplink resources for uplink shared channel (UP-SCH) transmission.

AUCI can be transmitted over a PUCCH resource specifically assigned for PUCCH transmission. For example, the PUCCH resource can be a frequency domain and time domain physical transmission resource, such as resources of a number of symbols and a number of physical resource blocks (PRBs) over an orthogonal frequency division multiplex (OFDM) resource grid.

In an example (not shown in FIG. 1) , corresponding to a UCI to be transmitted, one PUCCH resource can be configured by the BS 120 to the UE 110. The configuration can be performed, for example, through radio resource control (RRC) signaling, media access (MAC) layer control element (CE) , downlink control information, or a combination thereof. Assuming the system 100 operates with a licensed spectrum, the configured PUCCH resource can readily be available for the UE 110. However, when an unlicensed spectrum is introduced to the system 100, configuration of a single PUCCH resource for UCI reporting over the unlicensed spectrum may be unreliable.

FIG. 2A shows a scenario where the system 100 operates over an unlicensed band 201. The unlicensed band 201 is partitioned into subbands from 210 to 213 each, for example, having a bandwidth of 20 MHz. APUCCH resource 220 can be configured by the BS 120 to the UE 110 for transmission of a UCI. Before the transmission of the UCI, the UE 110 can perform an access procedure, such as a listen before talk (LBT) access procedure, on each subbands 210-213 to determine whether the subbands 210-213 are available. As shown, the LBT access procedure can be failed on the

subbands

211 and 213 because transmission activities of another transmitter are detected in the

subbands

211 and 213. In contrast, the LBT access procedure can be successful on the

subbands

210 and 212 because transmission activities are not detected in the

subbands

210 and 212. Accordingly, transmissions are allowed over the

subbands

210 and 212 but not allowed over the

subbands

211 and 213. The subbands 210-213 can be referred to as LBT subbands when a LBT access procedure is performed prior to access to those subbands.

The PUCCH resource 220 can be scheduled by the BS 120 in advance without knowledge of whether the respective subband 211is available when the PUCCH 220 is to be transmitted. When the subband 211 is determined to be unavailable, the transmission of the PUCCH resource 220 may have to be given up. Failure of feedback of fatal information (e.g., HARQ-ACK) may degrade the performance of the system 100 when operating over the unlicensed spectrum 201.

To improve the reliability of UCI reporting over subbands, in some examples, multiple PUCCH resources can be configured for one UCI transmission. FIG. 2B showsa scenario where multiple candidate PUCCH resources 230-233are configured that are distributed in the different subbands 210-213, respectively. As shown, when the subbands210 and 212 are available as a result of the LBT access procedure, the

candidate PUCCH resources

230 and 232 can be used for the UCI reporting. The UE 110 may select a PUCCH resource, for example, the PUCCH resource 230, from the

candidate PUCCH resources

230 and 232 to perform the UCI transmission.

FIG. 1 shows a UCI reporting process 130 corresponding to the scenario of FIG. 2B. In a first step 131 of the process 130, configuration information of the multiple PUCCH resources230-233 can be signaled from the BS 120 to the UE 110 through one or multiple times of signaling. Depending on content of the respective UCI (e.g., HARQ-ACK or CSI) to be reported from the UE to the BS 120 and methods employed for the UCI reporting, different configurations can be provided in the step 131. The UE 110 can accordingly determine or derive the multiple PUCCH resources 230-233. At a second step 132, the UE 110 can transmit the UCI over a PUCCH resource selected from the multiple PUCCH resources 230-233 configured in the first step 131 based on a result of a LBT access procedure.

The subbands210-213 in the FIGs. 2A-2B examples can be included in a bandwidth part (BWP) or a component carrier configured to the UE 110. In other examples, the subbands 210-213 can each be configured as a component carrier, and be combined using a carrier aggregation scheme. In Further examples, the scheme of multiple PUCCH resources for UCI reporting can be configured over carriers in a licensed spectrum. Under such a configuration, a LBT procedure is not performed prior to access to a subband, and diverse PUCCH resources at different frequency and time locations can be provided to improve reliability of UCI reporting.

II. Multiple PUCCH resources for HARQ-ACK feedback

1. Examples of HARQ-ACK feedback with a PUCCH resource

FIG. 3 shows examples of a PUCCH resource configuration 320, a resource format configuration 330, and a PUCCH resource 301 corresponding to the PUCCH resource configuration 320. As shown, the PUCCH resource configuration 320 can indicate a PUCCH resource ID 321, a starting PRB in frequency domain 322, a resource format 323, and possibly other parameters. The resource format configuration 330 (corresponding to the resource format323 indicated by the PUCCH resource configuration) can indicate a starting symbol 331, a number of PRBs 332 (optional) , a number of symbols (optional) , and other possible parameters.

The PUCCH resource 301 is show in an OFDM resource grid310 as specified by the PUCCH resource configuration 320 and the resource format configuration 330. For example, the PUCCH resource 301 has a PUCCH resource ID of #2, starts from PRB #4 until PRB #11 (lasting for 8 PRBs) in frequency domain, and starts from symbol #2 until symbol #7 (lasting for 6 symbols) . As shown, by a PUCCH resource configuration, a PUCCH resource in frequency and time domain can be identified.

FIG. 4 shows an example of a PUCCH resource set configuration 400for HARQ-ACK feedback. As shown, the PUCCH resource set configuration 400can indicate a number (e.g., 4) of PUCCH resource sets (e.g., label with #1, #2, and so on) . Each PUCCH resource set for HARQ-ACK reporting can typically include a PUCCH resource set ID (401) , information of a unique maximum UCI payload size (402) (e.g., 2 bits, 10 bits, or 40 bits) , and a resource list (403) including one or more PUCCH resource IDs. In the FIG. 4 example, the information of the maximum UCI payload size (402) is indicated in a form of the maximum payloadsize minus 1 (denoted by maxPayloadMinus1) . According to the PUCCH resource ID, a PUCCH resource configuration as described in the FIG. 3 example can be identified.

FIG. 5 shows an example of a procedure 500 for the UE 110 to determine which PUCCH resource from a selected PUCCH resource set 510 should be used for a HARQ-ACK feedback. For example, configuration information of a number of PUCCH resource sets (e.g., 4) can be received by the UE 110. During a first step, the UE 110 may select one PUCCH resource set 510 from the configured PUCCH resource sets based on a payload size of a UCI to be transmitted. For example, the selected PUCCH resource set 510 can indicate a smallest maximum payload size that can accommodate the to-be-transmitted payload size among the configured PUCCH resource sets.

During a second step, based on an index (referred to as an indicating index) from a DCI that provides a downlink transmission, the UE 110 can select a PUCCH resource (represented by a PUCCH resource ID) from a resource list 511 in the selected PUCCH resource set 510. The selection is illustrated in a mapping table 520 where different indices (referred to as mapping indices) are associated with different PUCCH resource IDs.

Each of the mapping indices in the mapping table 520can be explicitly indicated by the indicating index conveyed by the UCI, or can be derived based on the indicating index conveyed by the UCI (implicitly indicated) . For example, when the size of the resource list 511 is smaller than or equal to 8, the indicating index in a PUCCH resource indicator field (e.g., having a length of 3 bits) in the respective DCI can be used as the mapping index in the mapping table 520. In contrast, when the size of the resource list 511 is larger than 8 (e.g., 30) , the mapping index used in the mapping table can be calculated based on the value (the indicating index) of the PUCCH resource indicator field and other parameters of corresponding PDCCH reception associated by the DCI.

FIG. 6 shows an example process 600 for providing a single PUCCH resource for a HARQ-ACK feedback. The process 600 can be performed at the UE 110. The system 100 is used to explain the process 600. The process 600 can start from S601 and proceed to S610.

At S610, configuration information of multiple PUCCH resources and one or more PUCCH resource sets can be received at the UE 110 from the BS 120, for example, by RRC signaling. The configuration information may be transmitted with separate RRC messages.

At S620, an indicating index from a PUCCH resource indicator field in a DCI providing a downlink transmission can be received. For example, the downlink transmission can be a transmission of a physical downlink shared channel (PDSCH) , or a semi-persistent scheduling (SPS) PDSCH release. The DCI associated with the downlink transmission may indicate a PUCCH resource for a HARQ-ACK feedback of reception of the downlink transmission by using a PUCCH resource indicator. Additionally, the DCI may provide a time offset (e.g., in terms of slots or symbols) with respect to the DCI or the downlink transmission to indicate a timing of the PUCCH resource for the HARQ-ACK feedback.

A UCI carrying the HARQ-ACK feedback can be transmitted later over the indicated PUCCH resource. In some examples, multiple downlink transmissions over a same or different carriers taking place over multiple time periods may be indicated with a same PUCCH resource, and HARQ-ACK feedbacks for the multiple downlink transmissions may form a code book and be transmitted using the indicated PUCCH resource. Thus, a payload size of the UCI carrying the code book may vary depending on the number of the multiple downlink transmissions.

In some examples, the BS 120 may request the UE 120 to provide a CSI report together with a HARQ-ACK feedback of a certain downlink transmission, which may increase the payload size of the UCI. Additionally, the UE 110 may need to send an SR to request for uplink transmission resources. The SR may also be included in the UCI.

At S630, a PUCCH resource set can be determined from the PUCCH resource sets configured at S610 based on the payload size of the UCI including at least the HARQ-ACK feedback of the downlink transmission at S620.

At S640, the PUCCH resource can be determined from the PUCCH resource set determined at S630 based on the indicating index received at S620. For example, the indicating index can explicitly or implicitly indicate a mapping index to a PUCCH resource list in the PUCCH resource set determined at S630.

At S650, the UCI can be transmitted on the PUCCH resource determined at S640. The process 600 can then proceed to S699 and terminates at S699.

In the process 600, the PUCCH resource set having a certain maximum UCI payload size may provide multiple PUCCH resources that are suitable for different types of PUCCH structures. For example, compared with Long Term Revolution (LTE) , more flexible PUCCH structures are defined in NR to target different applications and use cases. A NR PUCCH structure can have a short or a long duration. The short duration PUCCH may span 1 or 2 symbols in a slot, and be multiplexed with downlink or uplink data channel in a time division multiplexing (TDM) manner. For example, a short duration PUCCH can be inserted in the last part of one slot to enable fast HARQ-ACK feedback. In contrast, a long duration PUCCH may span 4 to 11 symbols, and be multiplexed in a frequency division multiplexing (FDM) manner in a slot. The long duration PUCCH may thus provide adequate coverage and robustness desired by some use cases.

Accordingly, at the step S620, the BS 120 can determine the indicating index corresponding to the PUCCH resource based on a respective PUCCH structure suitable for a specific application and, optionally, other parameters (e.g., a channel condition, UE capability, and the like) . The indicating index is subsequently provided to the UE 110.

2. Examples of providing multiple PUCCH resources for a HARQ-ACK feedback

FIG. 7 shows a HARQ-ACK feedback process 700 according to an embodiment of the disclosure. In the process 700, multiple PUCCH resources are provided for a HARQ-ACK feedback based on an index-to-PUCCH resource mapping rule. The process 700 can be performed by the UE 110, and the system 100 is used to explain the process 700.

As shown in FIG. 7, the process 700 starts from S701, ends at S799, and includes steps from S710 to S750. The steps S710-S730 can be similar to the steps S610-S630 in the Fig. 6 example, respectively. However, the steps S740-S750 are different from the steps S640-S650. The differences between the

processes

600 and 700 are highlighted with underlines in FIG. 7.

Specifically, at S740, multiple PUCCH resources can be determined from a resource list in a PUCCH resource set determined at S730 based on an indicating index received at S720. Particularly, the step of S740 is performed based on the index-to-PUCCH resource mapping rule that associate smultiple PUCCH resources with one indicating index.

FIG. 8 shows an example of the index-to-PUCCH resource mapping rule according to an embodiment of the disclosure. As shown, a selected PUCCH resource set 810 includes a resource list 811. A number (denoted by

) of candidate PUCCH resources can be selected from the resource list 811 based on a mapping table 820.

takes a value of 3 in the FIG. 8 example. In various examples,

can be a default value or can be signaled from the BS 120 to the UE 110 by RRC, MAC CE, or DCI signaling.

A mapping index in the mapping table 820 can be indicated by the indicating index received at S720 explicitly or implicitly. Then, three PUCCH resource IDs (e.g., 10th, 11th, and 12th IDs of the resource list 811) associated with the mapping index (e.g., index 3) can be determined according to the mapping table 820. In this way, the indicating index can be mapped to the intended PUCCH resources.

At S750, a UCI can be transmitted on at least one of the multiple PUCCH resources determined at S740. For example, the candidate PUCCH resources determined at S740 may be distributed over multiple subbands. After a LBT access procedure, a subset of the multiple subbands are available. Accordingly, the UE 110 may select one or more candidate PUCCH resources in the available subbands for transmission of the UCI.

FIG. 9 shows another HARQ-ACK feedback process 900 according to an embodiment of the disclosure. In the process 900, multiple PUCCH resources are provided for a HARQ-ACK feedback based on a selected PUCCH resource set that includes multiple resource lists. The process 900 can be performed by the UE 110, and the system 100 is used to explain the process 900.

As shown in FIG. 9, the process 900 starts from S901, ends at S999, and includes steps from S910 to S950. Compared with the process 600in the FIG. 6 example, the steps S920-S930 can be similar to the steps S620-S630, while the steps S910, S940, and S950 are different from the steps S610, S640, and S650. The differences between the

processes

600 and 900 are highlighted with underlines in FIG. 9.

Specifically, at S910, configuration information of multiple PUCCH resources and one or more PUCCH resource sets can be received. Particularly, among those PUCCH resource sets, a number of PUCCH resource sets can each include multiple resource lists.

At S940, multiple PUCCH resources can be determined from the multiple resource lists of a PUCCH resource set determined at S930 based on an indicating index received at S920.

FIG. 10 shows an example of determining multiple PUCCH resources from multiple resource lists in a selected PUCCH resource set 1010. The selected PUCCH resource set 1010 can include multiple resource list 1011a-1011n. Assuming

number of PUCCH resources are to be determined. Each of the

number of the PUCCH resources can be from a different resource list among the resource lists 1011a-1011n in the selected PUCCH resource set 1010.

In the FIG. 10 example,

can be equal to the number of the resource lists 1011a-1011n. Accordingly, as shown in a mapping table 1020, corresponding to a mapping index determined based on the indicating index received at S920, multiples PUCCH resource ID seach from a different one of the resource lists 1011a-1011n can be determined. On each resource list 1011a-1011n, the PUCCH resource ID associated with the mapping index is selected. The association between the PUCCH resource ID and the mapping index can be predefined.

FIG. 11 shows another example of determining multiple PUCCH resources from multiple resource lists resource lists 1110a-1110n in a selected PUCCH resource set 1110. In the FIG. 11 example, a number of to-be-determined PUCCH resources,

can be smaller than a number of the resource lists 1110a-1110n in the selected PUCCH resource set 1110. As shown, two resource lists 1110a and 1110c (the 1st and 3rd resource lists) are selected (for example, based on a predefined rule) , and based on a mapping index, two PUCCH resource IDs from the two resource lists 1110a and 1110ccan be determined.

Similar to the FIG. 8 example, the number of PUCCH resources,

can be a default number or can be indicated through RRC, MAC CE, or DCI signaling. In other examples,

can be determined in other different ways.

At S950, a UCI can be transmitted on at least one of the multiple PUCCH resources determined at S940.

FIG. 12 shows another HARQ-ACK feedback process 1200 according to an embodiment of the disclosure. In the process 1200, multiple PUCCH resources are provided for a HARQ-ACK feedback based on multiple selected PUCCH resource sets that have a same maximum UCI payload size. The process 1200 can be performed by the UE 110, and the system 100 is used to explain the process 1200.

As shown in FIG. 12, the process 1200 can start from S1201, terminate at S1299, and include steps from S1210 to S1250. Compared with the process 600in the FIG. 6 example, the step S1220 can be similar to the step S620, while the steps S1210, and S1230-S1250 are different from the steps S610, and S630-S650. The differences between the

processes

600 and 1200 are highlighted with underlines in FIG. 12.

Specifically, at S1210, configuration information of multiple PUCCH resources and multiple PUCCH resource sets can be received. Particularly, some of the multiple PUCCH resource sets can be configured with a same maximum UCI payload size. There can be different maximum UCI payload sizes in the configuration information each associated with multiple PUCCH resource sets. Thus, corresponding to a payload size of a to-be-transmitted UCI, multiple PUCCH resource sets can be selected.

At S1230, multiple PUCCH resource sets can be determined from the configured multiple PUCCH resource sets based on a payload size of a UCI including at least a HARQ-ACK feedback of a downlink transmission described at S1220. For example, the multiple PUCCH resource sets can have a same maximum UCI payload size that is the smallest maximum UCI payload size among the configured multiple PUCCH resource sets that can accommodate the UCI.

At S1240, based on an indicating index received at S1220, multiple PUCCH resources can be determined from resource lists in the multiple PUCCH resource sets determined at S1230. For example, each of the multiple PUCCH resources can be from a different one of the multiple resource lists.

FIG. 13 shows an example of determination of multiple PUCCH resources from multiple selected PUCCH resource sets 1310-1320. As shown, the PUCCH resource sets 1310-1320 can each have information 1311-1321 indicating a same maximum UCI payload size, and thus be selected at the same time from the multiple PUCCH resource sets configured at S1210. A mapping index can be determined according to the indicating index that explicitly or implicitly indicates the mapping index. Based on the mapping index and according to a mapping table 130, two PUCCH resource IDs can be determined from the two selected PUCCH resource sets 1310 and 1320.

FIG. 14 shows another example of determination of multiple PUCCH resources from multiple selected PUCCH resource sets 1410a-1410n. The PUCCH resource sets 1410a-1410n can include information indicate a same maximum UCI payload size, and accordingly be selected at the same time from the multiple PUCCH resource sets configured at S1210. Based on a number,

of the multiple candidate PUCCH resources to be determined, a subset (

number) of the PUCCH resource sets 1410a-1410n can be determined. As an example,

takes a number of 2, and accordingly the 1st and 3rd PUCCH resource sets of the PUCCH resource sets 1410a-1410n are selected in FIG. 14. Subsequently, based on a mapping index determined based on the indicating index received at S1220,

PUCCH resources can be selected from the

PUCCH resource sets (the 1st and 3rd PUCCH resource sets) .

The number of candidate PUCCH resources,

can be equal to the selected PUCCH resource sets (the FIG. 13 example) , or can be smaller than the selected PUCCH resource sets (the FIG. 14 example) .

can be a default value, or can be signaled from the BS 120 to the UE 110 through RRC, MAC CE, or DCI signaling.

At S1250, a UCI can be transmitted on at least one of the multiple PUCCH resources determined at S1240.

FIG. 15 shows another HARQ-ACK feedback process 1500 according to an embodiment of the disclosure. In the process 1500, multiple PUCCH resources are provided for a HARQ-ACK feedback based on a selected PUCCH resource set that include PUCCH resource candidate sets each including multiple PUCCH resource IDs. The process 1500 can be performed by the UE 110, and the system 100 is used to explain the process 1500.

As shown in FIG. 15, the process 1500 can start from S1501, end at S1599, and include steps from S1510 to S1550. Compared with the process 600 in the FIG. 6 example, the steps S1520-S1530 can be similar to the steps S620-S630, while the steps S1510, and S1540-S1550 are different from the steps S610, and S640-S650. The differences between the

processes

600 and 1500 are highlighted with underlines in FIG. 15.

Specifically, at S1510, configuration information of multiple PUCCH resources and one or more PUCCH resource sets can be received. Particularly, some of the PUCCH resource sets can each include a resource list that includes a group of PUCCH resource candidate sets instead of PUCCH resource IDs. Each PUCCH resource candidate set can include multiple PUCCH IDs.

At S1540, a PUCCH resource candidate set can be determined from a resource list in a PUCCH resource set determined at S1530 based on an indicating index received at S1520. The multiple PUCCH resources in the PUCCH resource candidate set can subsequently be used for the HARQ-ACK feedback.

FIG. 16 shows an example of determination of a PUCCH resource candidate set from a selected PUCCH resource set 1610. As shown, the PUCCH resource set 1610 can include a resource list 1611 on which one or more PUCCH resource candidate sets (denoted by PUCCH-Candidate set) can be listed. Each PUCCH resource candidate set can include multiple PUCCH resource IDs. A mapping index in a mapping table 1620 can be determined based on the indicating index received at S1520. The indicating index may explicitly or implicitly indicate the mapping index. Based on the mapping index and referring to the mapping table 1620, a PUCCH resource candidate set can be selected from the PUCCH resource candidate sets in the resource list 1611. Multiple PUCCH resources indicated by the selected PUCCH resource candidate set can accordingly be determined.

At S1550, a UCI can be transmitted on at least one of the multiple PUCCH resources configured in the PUCCH resource candidate set determined at S1540.

3. Example process of providing multiple PUCCH resources for a HARQ-ACK feedback

FIG. 17 shows an example process 1700 for providing multiple PUCCH resources for a HARQ-ACK feedback according to some embodiments of the disclosure. The process 1700 can be performed at the UE 110. The system 100 is used to explain the process 1700. The process 1700 can start from S1701 and proceed to S1710.

At S1710, configuration information of multiple PUCCH resources and one or more PUCCH resource sets can be received. Each of the PUCCH resources can be associated with a PUCCH resource ID. The configuration information of the one or more PUCCH resources can be different for different examples.

In a first example, the one or more PUCCH resource sets can each include a unique maximum UCI payload size, and a resource list in which multiple PUCCH resource IDs are listed.

In a second example, the one or more PUCCH resource sets can each include a unique maximum UCI payload size, and multiple resource lists each including multiple PUCCH resource IDs.

In a third example, the multiple PUCCH resource sets can each include a resource list in which multiple PUCCH resource IDs are listed. However, different member of the multiple PUCCH resource set can share a same maximum UCI payload size, and thus can be selected together corresponding to a payload of a UCI to be reported.

In a fourth example, the one or more PUCCH resource sets can each include a unique maximum UCI payload size, and a resource list in which multiple PUCCH resource candidate sets are listed. Within each PUCCH resource set, multiple PUCCH resource IDs are listed.

At S1720, an indicating index from a PUCCH resource indicator field in a DCI providing a downlink transmission can be received.

At S1730, one or more PUCCH resource sets from the configured PUCCH resource sets can be determined based on a payload size of a to-be-reported UCI. The UCI can include at least a HARQ-ACK feedback of the downlink transmission. Corresponding to the first, second, or fourth examples at S1710, one PUCCH resource set can be determined. For the third example at S1710, multiple PUCCH resource sets can be determined due to different PUCCH resource sets can share a same maximum UCI payload size.

At S1740, based on the indicating index received at S1720, multiple PUCCH resources can be determined from the one or more PUCCH resource sets determined at the S1730. In an example, the multiple PUCCH resources are distributed in different subbands.

Corresponding to the first example at S1710, a specific mapping rule between an indicating index and multiple PUCCH resources on a resource list of the PUCCH resource set determined at S1730 can be employed in order to determine the multiple PUCCH resources.

Corresponding to the second example at S1710, a mapping index can first be determined based on the indicating index. Then, with the mapping index, a PUCCH resource ID can be selected from each of the multiple PUCCH resource lists of the PUCCH resource set determined at S1730. Alternatively, a PUCCH resource ID can be selected from each of a subset of the multiple PUCCH resource lists of the PUCCH resource set determined at S1730.

Corresponding to the third example at S1710, a mapping index can first be determined based on the indicating index. Then, with the mapping index, a PUCCH resource ID can be selected from each of the multiple PUCCH resource sets determined at S1730.

Corresponding to the fourth example at S1710, a mapping index can first be determined based on the indicating index. Then, with the mapping index, a PUCCH resource candidate set can be selected from the PUCCH resource list of the PUCCH resource set determined at S1730. The PUCCH resource candidate set provides multiple PUCCH resource IDs.

At S1750, the UCI can be transmitted on at least one of the multiple PUCCH resources determined at S1740. For example, the multiple PUCCH resources can be distributed in a set of subbands. The UE 110 may perform a LBT access procedure to determine which subbands are available. Then, the UE 110 may select one or more PUCCH resources in the available subbands to transmit the UCI. The process 1700 can then proceed to S1799 and terminates at S1799.

III. Multiple PUCCH resources for CSI reporting

1. Examples of CSI reporting with a single PUCCH resource configured in a BWP

In some examples, the UE 110 may perform CSI reporting according to a CSI report configuration. For example, the UE 110 operating on a carrier can be configured with one or more BWPs (e.g., up to four BWPs) . Each BWP can be a contiguous set of PRBs selected from the carrier. As configured, each BWP can have a BWP ID, a certain frequency location, a size, a numerology and control resource sets (CORSETs) . Typically, one BWP is active among the multiple configured BWPs at a given time. The UE 110 may not transmit a PUSCH or PUCCH over non-active BWPs. For purpose of CSI reporting, the CSI report configuration can specify a PUCCH resource per BWP. While operating in an active BWP, in response to a request of the BS 120, the UE 110 may determine a PUCCH resource configured in the active BWP, and transmit a CSI report over the PUCCH resource.

FIG. 18 shows an example of a CSI report configuration 1800. The CSI report configuration can include a PUCCH CSI resource list 1810. The PUCCH CSI resource list 1810 can include one or more PUCCH CSI resources 1811-1813. Each PUCCH CSI resource can include a BWP ID and a PUCCH resource ID. As can be seen, a PUCCH resource represented by the respective PUCCH resource ID is configured for each BWP represented by the BWP ID.

FIG. 19 shows an example process 1900 for providing a PUCCH resource for a CSI report. The process 1900 can be performed at the UE 110. The system 100 is used to explain the process 1900. The process 1900 can start from S1901 and proceed to S1910.

At S1910, configuration information for a CSI report can be received. The configuration information can include a PUCCH CSI resource list including one or more PUCCH CSI resources in a component carrier. Each PUCCH CSI resource specifies a PUCCH resource ID associated with a BWP ID. The configuration information may further include one or more PUCCH resources each associated with a PUCCH resource ID. The configuration information can be signaled from the BS 120 to the UE 110, for example, through one or multiple messages of RRC signaling.

The UE 110 may operate on the carrier that is partitioned into multiple BWPs. Each BWP can be associated with the BWP IDs indicated in the PUCCH CSI resource list. Thus, based on the received PUCCH CSI resources, a PUCCH resource can be determined for each BWP of the carrier using the respective BWP ID.

The BS 120 can request the UE 110 to perform the CSI report, for example, through RRC, MAC CE, or DCI signaling. A request from the BS 120 may specify a timing for the CSI report. Alternatively, a request from the BS 120 may specify a sequence of timings for the UE 110 to periodically perform CSI reporting.

At S1920, a BWP ID of an active BWP in the carrier can be determined in order to perform the CSI report.

At S1930, a PUCCH CSI resource can be determined from the PUCCH CSI resource list received at S1910 based on the BWP ID determined at S1920.

At S1940, a UCI including at least the CSI report can be transmitted on a PUCCH resource configured in the PUCCH CSI resource determined at S1930. The process 1900 can proceed to S1999, and terminates at S1999.

2. Examples of providing multiple PUCCH resources in a BWP for a CSI report

FIG. 20 shows a CSI reporting process 2000 according to an embodiment of the disclosure. In the process 2000, multiple PUCCH resources in a BWP are provided for a CSI report based on a PUCCH CSI resource list in which multiple PUCCH resource IDs are associated with one BWP. The process 2000 can be performed by the UE 110, and the system 100 is used to explain the process 2000.

As shown in FIG. 20, the process 2000 can start from S2001, end at S2099, and include steps from S2010 to S2040. The steps S2020-S2030 can be similar to the steps S1920-S1930 in the FIG. 19 example, respectively. However, the steps S2010 and S2040 are different from the steps S1910 and S1940. The differences between the

processes

1900 and 2000 are highlighted with underlines in FIG. 20.

Specifically, at S2010, configuration information for a CSI report can be received. The configuration information can include a resource list including one or more PUCCH CSI resources in a carrier. Particularly, for each PUCCH CSI resource, multiple PUCCH resource IDs are specified to be associated with a BWP ID. Those BWP IDs can correspond to BWPs partitioned from the carrier.

FIG. 21 shows an example CSI report configuration 2100 in which multiple PUCCH resources are configured for one BWP. As shown, in the CSI report configuration 2100, a PUCCH CSI resource list 2110 includes multiple PUCCH CSI resources 2111-2113. Each of the PUCCH CSI resources 2111-2113 includes a BWP ID, and multiple PUCCH resource IDs.

At S2030, when a PUCCH CSI resource is determined from the resource list configured at S2010, multiple PUCCH resources indicated by the PUCCH CSI resource can be determined.

At S2040, a UCI including at least the CSI report can be transmitted on at least one of the multiple PUCCH resources configured in the PUCCH CSI resource determined at S2030. For example, the multiple PUCCH resources can be distributed in multiple subbands of an active BWP the UE 110 operates on. The UE 110 may perform a LBT access procedure to determine which subbands are available. Then, the UE 110 may select one or more of the PUCCH resources in the available subbands to transmit the UCI. In addition, the UCI may include an SR when the UE 110 needs uplink resource for data transmission.

FIG. 22 shows another CSI report process 2200 according to an embodiment of the disclosure. In the process 2200, multiple PUCCH resources are provided for a CSI report based on a CSI report configuration including multiple PUCCH CSI resource lists. The process 2200 can be performed by the UE 110, and the system 100 is used to explain the process 2200.

As shown in FIG. 22, the process 2200 can start from S2201, ends at S2299, and include steps from S2210 to S2240. The steps S2220 can be similar to the step S1920 in the FIG. 19 example, respectively. However, the steps S2210 and S2230-S2240 are different from the steps S1910 and S1930-S1940. The differences between the

processes

1900 and 2200 are highlighted with underlines in FIG. 22.

Specifically, at S2210, configuration information for a CSI report can be received. Particularly, the configuration information can include multiple resource lists each including one or more PUCCH CSI resources in a same carrier. Each PUCCH CSI resource includes a BWP ID and one PUCCH resource ID. Those BWP IDs can correspond to BWPs partitioned from the carrier.

FIG. 23 shows an example of a CSI report configuration 2300 that includes multiple PUCCH CSI resource lists 2310-2330. Each PUCCI resource list can include one or multiple PUCCH CSI resources. Each PUCCH CSI resource can specify one PUCCH resource ID associated with a BWP ID. In addition, a same BWP ID can be indicated in different PUCCH CSI resource lists. For example, the BWP IDs in the PUCCH CSI resources 2311-2313 of the PUCCH CSI resource list 2310 can be the same as that in the PUCCH CSI resources 2321-2323 of the PUCCH CSI resource list 2320, respectively. Under such a configuration, for one active BWP ID, multiple PUCCH resource IDs can be determined from the multiple PUCCH CSI resource lists.

At S2230, multiple PUCCH CSI resources can be determined from the multiple resource lists based on a BWP ID determined at S2220. For example, the multiple PUCCH CSI resources each include the same BWP ID. Accordingly, multiple PUCCH resource IDs in the multiple PUCCH CSI resources can be identified.

At S2240, a UCI including at least the CSI report can be transmitted on at least one of the multiple PUCCH resources configured in the multiple PUCCH CSI resources determined at S2230. Similarly, the multiple PUCCH resources can be distributed in different subbands. The UE 110 may select a subset of the PUCCH resources for the CSI report based on availabilities of the respective subbands.

3. Example process of providing multiple PUCCH resources in a BWP for a CSI report

FIG. 24 shows an example process 2400 for providing multiple PUCCH resources for a CSI report according to some embodiments of the disclosure. The process 2400 can be performed at the UE 110. The system 100 is used to explain the process 2400. The process 2400 can start from S2401 and proceed to S2410.

At S2410, configuration information of a CSI report in a carrier can be received. The configuration information can vary for different examples. In a first example, the configuration information may include one PUCCH CSI resource list that includes one or multiple PUCCH CSI resources in the carrier. Each PUCCH CSI resource can include a BWP ID associated with multiple PUCCH resource IDs.

In a second example, the configuration information may include multiple PUCCH CSI resource lists that each includes one or multiple PUCCH CSI resources in the carrier. Different from the first example, each PUCCH CSI resource may include a BWP ID associated with one PUCCH resource, and different PUCCH CSI resource lists may indicate a same BWP ID.

At S2420, a BWP ID of an active BWP in the carrier can be determined.

At S2430, one or more PUCCH CSI resources can be determined from the one or more PUCCH CSI resource lists based on the BWP ID. For example, corresponding to the first example, one PUCCH CSI resource indicating the active BWP ID can be determined. Accordingly, the multiple PUCCH resource IDs indicated in the PUCCH CSI resource can be identified. Corresponding to the second example, multiple PUCCH CSI resources on different PUCCH CSI resource lists and sharing the same active BWP ID can be determined. Accordingly, the multiple PUCCH resources indicated by the multiple PUCCH CSI resources can be identified.

At S2440, a UCI including at least the CSI report can be transmitted on at least one of the multiple PUCCH resources indicated at S2430. Similarly, those PUCCH resources indicated at S2430 may be distributed in different subbands. The UE 110 can perform a LBT access procedure, and select from a subset of those PUCCH resources in the available subbands. The process 2400 can proceeds to S2499, and terminates at S2499.

IV. Apparatus and computer readable medium

FIG. 25 shows an example apparatus 2500 according to embodiments of the disclosure. The apparatus 2500 can be configured to perform various functions in accordance with one or more embodiments or examples described herein. Thus, the apparatus 2500 can provide means for implementation of mechanisms, techniques, processes, functions, components, systems described herein. For example, the apparatus 2500 can be used to implement functions of the UEs or BSs in various embodiments and examples described herein. The apparatus 2500 can include a general purpose processor or specially designed circuits to implement various functions, components, or processes described herein in various embodiments. The apparatus 2500 can include processing circuitry 2510, a memory 2520, and a radio frequency (RF) module 2530.

In various examples, the processing circuitry 2510 can include circuitry configured to perform the functions and processes described herein in combination with software or without software. In various examples, the processing circuitry 2510 can be a digital signal processor (DSP) , an application specific integrated circuit (ASIC) , programmable logic devices (PLDs) , field programmable gate arrays (FPGAs) , digitally enhanced circuits, or comparable device or a combination thereof.

In some other examples, the processing circuitry 2510 can be a central processing unit (CPU) configured to execute program instructions to perform various functions and processes described herein. Accordingly, the memory 2520 can be configured to store program instructions. The processing circuitry 2510, when executing the program instructions, can perform the functions and processes. The memory 2520 can further store other programs or data, such as operating systems, application programs, and the like. The memory 2520 can include non-transitory storage media, such as a read only memory (ROM) , a random access memory (RAM) , a flash memory, a solid state memory, a hard disk drive, an optical disk drive, and the like.

In an embodiment, the RF module 2530 receives a processed data signal from the processing circuitry 2510 and converts the data signal to beam forming wireless signals that are then transmitted via antenna arrays 2540, or vice versa. The RF module 2530 can include a digital to analog convertor (DAC) , an analog to digital converter (ADC) , a frequency up convertor, a frequency down converter, filters and amplifiers for reception and transmission operations. The RF module 2530 can include multi-antenna circuitry for beamforming operations. For example, the multi-antenna circuitry can include an uplink spatial filter circuit, and a downlink spatial filter circuit for shifting analog signal phases or scaling analog signal amplitudes. The antenna arrays 2540 can include one or more antenna arrays.

The apparatus 2500 can optionally include other components, such as input and output devices, additional or signal processing circuitry, and the like. Accordingly, the apparatus 2500 may be capable of performing other additional functions, such as executing application programs, and processing alternative communication protocols.

The processes and functions described herein can be implemented as a computer program which, when executed by one or more processors, can cause the one or more processors to perform the respective processes and functions. The computer program may be stored or distributed on a suitable medium, such as an optical storage medium or a solid-state medium supplied together with, or as part of, other hardware. The computer program may also be distributed in other forms, such as via the Internet or other wired or wireless telecommunication systems. For example, the computer program can be obtained and loaded into an apparatus, including obtaining the computer program through physical medium or distributed system, including, for example, from a server connected to the Internet.

The computer program may be accessible from a computer-readable medium providing program instructions for use by or in connection with a computer or any instruction execution system. The computer readable medium may include any apparatus that stores, communicates, propagates, or transports the computer program for use by or in connection with an instruction execution system, apparatus, or device. The computer-readable medium can be magnetic, optical, electronic, electromagnetic, infrared, or semiconductor system (or apparatus or device) or a propagation medium. The computer-readable medium may include a computer-readable non-transitory storage medium such as a semiconductor or solid state memory, magnetic tape, a removable computer diskette, a random access memory (RAM) , a read-only memory (ROM) , a magnetic disk and an optical disk, and the like. The computer-readable non-transitory storage medium can include all types of computer readable medium, including magnetic storage medium, optical storage medium, flash medium, and solid state storage medium.

While aspects of the present disclosure have been described in conjunction with the specific embodiments thereof that are proposed as examples, alternatives, modifications, and variations to the examples may be made. Accordingly, embodiments as set forth herein are intended to be illustrative and not limiting. There are changes that may be made without departing from the scope of the claims set forth below.

Claims

A method, comprising:

receiving configuration information of physical uplink control channel (PUCCH) resources and one or more PUCCH resource sets at a user equipment (UE) from a base station (BS) in a wireless communication system;

receiving an index from a PUCCH resource indicator field in a downlink control information (DCI) providing a downlink transmission;

determining one or more PUCCH resource sets from the configured one or more PUCCH resource sets based on a payload size of an uplink control information (UCI) including a hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback of the downlink transmission;

determining multiple PUCCH resources from the determined one or more PUCCH resource sets based on the received index; and

transmitting the UCI on one of the determined multiple PUCCH resources.
The method of claim 1, wherein the multiple determined PUCCH resources are distributed over different subbands.
The method of claim 1, wherein

receiving the configuration information includes:

receiving the configuration information of the one or more PUCCH resource sets each including a first resource list;

the determining the one or more PUCCH resource sets includes:

determining a first PUCCH resource set from the configured one or more PUCCH resource sets based on the payload size of the UCI including the HARQ-ACK feedback of the downlink transmission; and

the determining the multiple PUCCH resources includes:

determining the multiple PUCCH resources from the first resource list in the first PUCCH resource set based on the received index according to an index-to-PUCCH resource mapping rule.
The method of claim 1, wherein

the receiving the configuration information includes:

receiving the configuration information of the one or more PUCCH resource sets each including multiple second resource lists;

the determining the one or more PUCCH resource sets includes:

determining a second PUCCH resource set from the configured one or more PUCCH resource sets based on the payload size of the UCI including the HARQ-ACK feedback of the downlink transmission; and

the determining the multiple PUCCH resources includes:

determining the multiple PUCCH resources from the multiple second resource lists in the second PUCCH resource set based on the received index.
The method of claim 4, wherein each of the multiple PUCCH resources is from a different one of the multiple second resource lists, and is associated with the received index.
The method of claim 1, wherein

the receiving the configuration information includes:

receiving the configuration information of the one or more PUCCH resource sets each including a third resource list, wherein at least two of the one or more PUCCH resource sets are configured with a same maximum UCI payload size;

the determining the one or more PUCCH resource sets includes:

determining multiple third PUCCH resource sets from the configured one or more PUCCH resource sets based on the payload size of the UCI including the HARQ-ACK feedback of the downlink transmission, wherein the multiple third PUCCH resource sets have a same maximum UCI payload size; and

the determining the multiple PUCCH resources includes:

determining the multiple PUCCH resources from the multiple third resource lists in the multiple third PUCCH resource sets based on the received index.
The method of claim 6, wherein each of the multiple PUCCH resources is from a different one of the multiple third resource lists, and associated with the received index.
The method of claim 1, wherein

the receiving the configuration information includes:

receiving the configuration information of the one or more PUCCH resource sets each including a fourth resource list, each fourth resource list including multiple PUCCH resource candidate sets each including multiple PUCCH resources;

the determining the one or more PUCCH resource sets includes:

determining a fourth PUCCH resource set from the configured one or more PUCCH resource sets based on the payload size of the UCI including the HARQ-ACK feedback of the downlink transmission; and

the determining the multiple PUCCH resources includes:

determining a first PUCCH resource candidate set from the fourth resource list in the determined fourth PUCCH resource set based on the received index, the multiple PUCCH resources included in the first PUCCH resource candidate set being the determined multiple PUCCH resources.
A user equipment (UE) , comprising circuitry configured to:

receive configuration information of physical uplink control channel (PUCCH) resources and one or more PUCCH resource sets;

receive an index from a PUCCH resource indicator field in a downlink control information (DCI) providing a downlink transmission;

determining one or more PUCCH resource sets from the configured one or more PUCCH resource sets based on a payload size of an uplink control information (UCI) including a hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback of the downlink transmission;

determine multiple PUCCH resources from the determined one or more PUCCH resource sets based on the received index; and

transmit the UCI on one of the determined multiple PUCCH resources.
The UE of claim 9, wherein the multiple determined PUCCH resources are distributed over different subbands.
The UE of claim 9, wherein the circuitry is configured to:

receive the configuration information of the one or more PUCCH resource sets each including a first resource list;

determine a first PUCCH resource set from the configured one or more PUCCH resource sets based on the payload size of the UCI including the HARQ-ACK feedback of the downlink transmission; and

determine the multiple PUCCH resources from the first resource list in the first PUCCH resource set based on the received index according to an index-to-PUCCH resource mapping rule.
The UE of claim 9, wherein the circuitry is configured to:

receive the configuration information of the one or more PUCCH resource sets each including multiple second resource lists;

determine a second PUCCH resource set from the configured one or more PUCCH resource sets based on the payload size of the UCI including the HARQ-ACK feedback of the downlink transmission; and

determine the multiple PUCCH resources from the multiple second resource lists in the second PUCCH resource set based on the received index.
The UE of claim 12, wherein each of the multiple PUCCH resources is from a different one of the multiple second resource lists, and is associated with the received index.
The UE of claim 9, wherein the circuitry is configured to:

receive the configuration information of the one or more PUCCH resource sets each including a third resource list, wherein at least two of the one or more PUCCH resource sets are configured with a same maximum UCI payload size;

determine multiple third PUCCH resource sets from the configured one or more PUCCH resource sets based on the payload size of the UCI including the HARQ-ACK feedback of the downlink transmission, wherein the multiple third PUCCH resource sets have a same maximum UCI payload size; and

determine the multiple PUCCH resources from the multiple third resource lists in the multiple third PUCCH resource sets based on the received index.
The UE of claim 14, wherein each of the multiple PUCCH resources is from a different one of the multiple third resource lists, and associated with the received index.
The UE of claim 9, wherein the circuitry is configured to:

receive the configuration information of the one or more PUCCH resource sets each including a fourth resource list, each fourth resource list including multiple PUCCH resource candidate sets each including multiple PUCCH resources;

determine a fourth PUCCH resource set from the configured one or more PUCCH resource sets based on the payload size of the UCI including the HARQ-ACK feedback of the downlink transmission; and

determine a first PUCCH resource candidate set from the fourth resource list in the determined fourth PUCCH resource set based on the received index, the multiple PUCCH resources included in the first PUCCH resource candidate set being the determined multiple PUCCH resources.