Patent Description:
In the UMTS (Universal Mobile Telecommunications System) network, the specifications of Long Term Evolution (LTE) have been drafted for the purpose of further increasing high speed data rates, providing lower latency and so on (see Non-Patent Literature <NUM>). For the purpose of further widening a bandwidth and increasing the speed in comparison with LTE, the succeeding systems of LTE (which are also referred to as, for example, LTE-A (LTE-Advanced), FRA (Future Radio Access), <NUM>, <NUM>, <NUM>+ (plus), NR (New RAT), LTE Rel. <NUM> and later versions, or the like) are also under study.

In the existing LTE systems (for example, LTE Rel. <NUM> to Rel. <NUM>), downlink (DL) and/or uplink (UL) communication is performed by using a subframe (also referred to as a transmission time interval (TTI) or the like) of <NUM>. The subframe is a transmission time unit of one data packet coded by channel coding, and is a processing unit of scheduling, link adaptation, retransmission control (HARQ (Hybrid Automatic Repeat reQuest)), and so on.

In the existing LTE systems (for example, LTE Rel. <NUM> to Rel. <NUM>), a user terminal transmits uplink control information (UCI) by using an uplink control channel (for example, a PUCCH (Physical Uplink Control Channel)) or an uplink shared channel (for example, a PUSCH (Physical Uplink Shared Channel)). A configuration (format) of the uplink control channel is referred to as a PUCCH format or the like.

<NPL>, provides a text proposal on resource allocation for PUCCH for NR in TS38. <NUM> and discusses some remaining issues relating to implicit mapping.

<NPL>, summarizes some issues for further study in relation to PUCCH resource allocation and observes that implicit PUCCH resource allocation should only be specified if it can handle and avoid resource collisions, otherwise, NR should use explicit PUCCH resource allocation only.

<NPL>, summarizes agreements regarding resource allocation for NR physical uplink control channel (PUCCH) and makes some proposals like e.g. identifying the PUCCH format implicitly via the configured COREST and UCI payload size.

For the future radio communication systems (for example, LTE Rel. <NUM> or later versions, <NUM>, <NUM>+, NR and so on), a method of allocating resources for an uplink control channel (for example, PUCCH resources) used for transmission of UCI to the user terminal is under study.

For example, the following method is under study: before RRC (Radio Resource Control) connection setup, the user terminal determines PUCCH resources to be used for transmission of UCI, based on at least one of a certain field value in system information (for example, RMSI (Remaining Minimum System Information)) and a certain field value and an implicit value in downlink control information (DCI).

However, with the above method of determining PUCCH resources, PUCCH frequency resources to be used for frequency hopping within a certain bandwidth may not be appropriately determined.

The present invention is made in view of such circumstances, and has one object to provide a user terminal and a radio base station that can appropriately determine PUCCH frequency resources to be used for frequency hopping within a certain bandwidth.

The object of the present disclosure is achieved by the subject matter of the appended independent claims. Examples are provided to facilitate the understanding of the present disclosure.

One example of a user terminal of the present invention includes: a receiving section that receives a downlink control channel; and a control section that determines an initial cyclic shift index for an uplink control channel based on the downlink control channel, in which a difference between different initial cyclic shift indexes based on different downlink control channels is different depending on a format of the uplink control channel. Advantageous Effects of Invention.

According to the present invention, PUCCH frequency resources to be used for frequency hopping within a certain bandwidth can be appropriately determined.

In the future radio communication systems (for example, LTE Rel. <NUM> or later versions, <NUM>, NR, or the like), a configuration (also referred to as a format, a PUCCH format (PF), or the like) for an uplink control channel (for example, a PUCCH) used for transmission of UCI is under study. For example, in LTE Rel. <NUM>, support of five types of PFs <NUM> to <NUM> is under study. Note that the term "PF" as used in the following description is merely an example, and a different term may be used.

For example, each of PFs <NUM> and <NUM> is a PF used for transmission of UCI of up to <NUM> bits (for example, transmission confirmation information (also referred to as a HARQ-ACK (Hybrid Automatic Repeat reQuest-Acknowledge), an ACK, a NACK, or the like)). PF <NUM> can be allocated to <NUM> or <NUM> symbols, and is therefore also referred to as a short PUCCH, a sequence-based short PUCCH, or the like. In contrast, PF <NUM> can be allocated to <NUM> to <NUM> symbols, and is therefore also referred to as a long PUCCH or the like. In PF <NUM>, a plurality of user terminals may be multiplexed in code division multiplexing (CDM) within the same physical resource block (also referred to as a PRB, a resource block (RB), or the like) by means of time-domain block-wise spreading using at least one of a CS and an OCC.

Each of PFs <NUM> to <NUM> is a PF used for transmission of UCI of more than <NUM> bits (for example, channel state information (CSI) (or CSI and a HARQ-ACK and/or a scheduling request (SR))). PF <NUM> can be allocated to <NUM> or <NUM> symbols, and is therefore also referred to as a short PUCCH or the like. In contrast, each of PFs <NUM> and <NUM> can be allocated to <NUM> to <NUM> symbols, and is therefore also referred to as a long PUCCH or the like. In PF <NUM>, a plurality of user terminals may be multiplexed in CDM by means of (frequency-domain) block-wise spreading before DFT.

Regarding resources (for example, PUCCH resources) used for transmission of an uplink control channel of the formats as described above, determination of PUCCH resources to be used for transmission of UCI, based on at least one of a certain field value in system information (for example, RMSI (Remaining Minimum System Information)) and a certain field value and an implicit value in downlink control information (DCI) before RRC connection setup is under study.

For example, before RRC connection setup, one of a plurality of PUCCH resources is specified based on a certain field value in RMSI (also referred to as an index value, an RMSI index value, a certain value, an indicator (indication), an RMSI indicator, a certain value, or the like). For example, <NUM> types of PUCCH resources are specified based on a <NUM>-bit RMSI index value.

Each PUCCH resource indicated by the RMSI index value may include one or more cell-specific parameters. For example, the cell-specific parameters include at least one of the following parameters, and may include another parameter.

One of a plurality of PUCCH resources is specified based on at least one of a certain field value (a PUCCH resource indicator, an ACK/NACK resource indicator (ARI), an ACK/NACK resource offset (ARO), or a TPC command field value) in DCI and an implicit value. For example, <NUM> PUCCH resources are specified based on a <NUM>-bit ARI in DCI and a <NUM>-bit implicit value.

Each PUCCH resource indicated by at least one of the ARI and the implicit value may include one or more user terminal-specific (UE-specific) parameters. For example, the UE-specific parameters include at least one of the following parameters, and may include another parameter.

The implicit value may be, for example, derived based on at least one of the following parameters. Note that the implicit value may be any value derived without explicit signaling.

<FIG> is a diagram to show an example of PUCCH resources indicated by the RMSI index values. For example, as shown in <FIG>, each value of a <NUM>-bit RMSI index may indicate a PUCCH period and a cell-specific PRB offset.

<FIG> are each a diagram to show an example of PUCCH resources indicated by the ARI. <FIG> shows an example of PUCCH resources for PUCCH format <NUM>, and <FIG> shows an example of PUCCH resources for PUCCH format <NUM>.

For example, as shown in <FIG>, a <NUM>-bit ARI may indicate a hopping direction, a UE-specific PRB offset, and a plurality of initial CS indexes. For example, the user terminal may derive a <NUM>-bit value r (implicit value), based on a CCE index, and may determine one of the plurality of initial CS indexes, based on the value r.

When frequency hopping is applied to the PUCCH in the future radio communication systems as described above, it is assumed that frequency resources assigned to the PUCCH are PRBs that are away from a PRB at each edge of a certain bandwidth (for example, a bandwidth part (BWP)) by a certain offset value x.

Here, the BWP is a partial band configured in a carrier, and is referred to as a partial band or the like. The BWP may include a BWP for the uplink (UL) (a UL BWP, an uplink BWP), and a BWP for the downlink (DL) (a DL BWP, a downlink BWP). An uplink BWP for random access (initial access) may be referred to as an initial BWP, an initial uplink BWP, an initial access BWP, or the like.

A downlink BWP used to detect a block including a synchronization signal and a broadcast channel (also referred to as an SSB (Synchronization Signal Block), an SS/PBCH block (Synchronization Signal/Physical Broadcast Channel Block), or the like) may be referred to as an initial downlink BWP or the like.

When one or more BWPs (at least one of one or more uplink BWPs and one or more downlink BWPs) are configured for the user terminal, at least one of the BWPs may be activated. A BWP in an active state may also be referred to as an active BWP (an active uplink BWP or an active downlink BWP) or the like. A default BWP (a default BWP (a default uplink BWP or a default downlink BWP)) may be configured for the user terminal.

For example, it is assumed that the frequency resources of the first hop include certain number of PRBs that are away from one edge of a certain bandwidth (for example, an initial access BWP) by a certain offset value x, and the frequency resources of the second hop include certain PRBs that are away from another edge of the certain bandwidth by the certain offset value x.

The certain offset value x is derived based on at least one of the cell-specific PRB offset indicated by the RMSI index value and the UE-specific PRB offset indicated by the ARI. For example, the following equation may hold: Certain offset value x = Cell-specific PRB offset + UE-specific PRB offset.

However, when the cell-specific PRB offset indicated by the RMSI index value is a fixed value (for example, any one of <NUM> to <NUM> in <FIG>) as shown in <FIG>, PUCCH allocation may be concentrated on both edge regions of a certain bandwidth (for example, an initial access BWP), and PUCCH frequency resources to be used for frequency hopping within the certain bandwidth may not be appropriately assigned.

In view of this, the inventors of the present invention come up with the idea of enabling appropriate determination of PUCCH frequency resources to be used for frequency hopping within a certain bandwidth, by using a value based on the certain bandwidth (for example, an initial access BWP) for the cell-specific PRB offset value, instead of using a fixed value. The inventors of the present invention come up with the idea of causing a difference between different initial CS indexes based on the PDCCH to be different depending on a PUCCH format.

The present embodiment will be described below in detail.

In the present embodiment, the user terminal receives system information including a value based on a certain bandwidth or an index value indicating a cell-specific PRB offset (first offset value) being <NUM>. Based on the cell-specific PRB offset, the user terminal determines PUCCH frequency resources to be used for frequency hopping within the certain bandwidth.

The following description is based on an assumption that the certain bandwidth is an initial access BWP. The certain bandwidth, however, is not limited to this, and may be another bandwidth such as an uplink BWP or a downlink BWP.

The following description is also based on an assumption that the system information including an index value indicating a cell-specific PRB offset value is RMSI. The system information, however, may be any type of information as long as the information is information broadcast in a certain unit (for example, a cell unit, a component carrier unit, or a carrier unit). The index value indicating a cell-specific PRB offset in RMSI is hereinafter also referred to as an RMSI index value.

In the first aspect, the cell-specific PRB offset indicated by the RMSI index value will be described. The cell-specific PRB offset may have four values or two values including at least one of a value based on an initial access BWP and <NUM>.

<FIG> is a diagram to show an example of the RMSI index values indicating a cell-specific PRB offset of four values according to the first aspect. As shown in <FIG>, each PUCCH period may be associated with a cell-specific PRB offset of four values, and the cell-specific PRB offset of four values may be indicated by respective four different RMSI indexes. For example, in <FIG>, each of four PUCCH periods of <NUM>, <NUM>, <NUM>, and <NUM> symbols is associated with a cell-specific PRB offset of four values.

In <FIG>, as the cell-specific PRB offset, four values {<NUM>, floor((Initial_BWP/<NUM>)*(<NUM>/<NUM>)), floor((Initial_BWP/<NUM>)*(<NUM>/<NUM>)), floor((Initial_BWP/<NUM>)*(<NUM>/<NUM>))} are indicated. Here, Initial_BWP may be the number of PRBs constituting the initial access BWP.

<FIG> are each a diagram to show an example of frequency hopping using the cell-specific PRB offset of four values according to the first aspect. <FIG> show examples of frequency hopping when the RMSI index value of <FIG> is <NUM>, <NUM>, <NUM>, and <NUM>, respectively, (in other words, when the PUCCH period is <NUM> symbols). Note that frequency hopping illustrated in the following description is merely examples, and frequency hopping is not limited to such illustrated examples. For example, the PUCCH period may be configured by a part of the symbols (for example, <NUM>, <NUM>, or <NUM> symbols) of a slot.

Note that, in <FIG>, the UE-specific PRB offset specified by the ARI in DCI is <NUM>, or the UE-specific PRB offset is not used. <FIG> assume a case that the number of PRBs constituting the initial access BWP is an even number, but this is not restrictive. The number of PRBs constituting the initial access BWP may be an odd number, and patterns of frequency hopping are not limited to the illustrated patterns.

As shown in <FIG>, when the cell-specific PRB offset indicated by the RMSI index value is "<NUM>", the user terminal may determine the use of a certain number of PRBs at both the edges of the initial access BWP for PUCCH frequency resources to be used for frequency hopping within the initial access BWP. Specifically, the user terminal may determine the use of a certain number of PRBs (for example, one PRB) at both the edges of the initial access BWP for frequency resources of each of the first hop and the second hop.

As shown in <FIG>, when the cell-specific PRB offset indicated by the RMSI index value is "floor((Initial_BWP/<NUM>)*(<NUM>/<NUM>))", the user terminal may determine the use of a certain number of PRBs away from both the edges of the initial access BWP by floor((Initial_BWP/<NUM>)*(<NUM>/<NUM>)) for PUCCH frequency resources to be used for frequency hopping within the initial access BWP. Specifically, the user terminal may determine the use of a certain number of PRBs (for example, one PRB) away from both the edges of the initial access BWP by floor((Initial_BWP/<NUM>)*(<NUM>/<NUM>)) for frequency resources of the first hop and the second hop respectively.

In a similar manner, in <FIG>, the user terminal may determine the use of a certain number of PRBs away from both the edges of the initial access BWP by the cell-specific PRB offsets "floor((Initial_BWP/<NUM>)*(<NUM>/<NUM>))" and "floor((Initial_BWP/<NUM>)*(<NUM>/<NUM>))" indicated by respective RMSI index values for PUCCH frequency resources to be used for frequency hopping within the initial access BWP.

In this manner, for each value of the cell-specific PRB offset, a ratio with respect to the entire bandwidth obtained by equally dividing the bandwidth from each edge to the center (or to the PRB at the center) of the initial access BWP may be used. Specifically, the value may be a value obtained by multiplying the bandwidth by a certain coefficient α (α ≤ <NUM>). For example, in <FIG>, the bandwidth from each edge to the center of the initial access BWP is equally divided into four, but this is not restrictive. For example, the bandwidth may be equally divided into three as shown in <FIG>.

<FIG> are each a diagram to show another example of frequency hopping using the cell-specific PRB offset of four values according to the first aspect. <FIG> are different from <FIG> in that the bandwidth from each edge to the center of the initial access BWP in <FIG> is equally divided into three. In the description of <FIG>, the difference from <FIG> will be mainly described.

In the case shown in <FIG>, as the cell-specific PRB offset, four values {<NUM>, floor((Initial_BWP/<NUM>)*(<NUM>/<NUM>)), floor((Initial_BWP/<NUM>)*(<NUM>/<NUM>)), floor((Initial_BWP/<NUM>)*(<NUM>/<NUM>))} may be used. In this case, the four values indicated by the RMSI index values shown in <FIG> are also substituted by {<NUM>, floor((Initial _BWP/<NUM>)*(<NUM>/<NUM>)), floor((Initial_BWP/<NUM>)*(<NUM>/<NUM>)), floor((Initial_BWP/<NUM>)*(<NUM>/<NUM>))}.

As shown in <FIG> and <FIG>, by using a ratio with respect to the entire bandwidth obtained by equally dividing the bandwidth from each edge to the center (or to the PRB at the center) of the initial access BWP for each value of the cell-specific PRB offset, PUCCH resources to be used for frequency hopping can be distributed in the entire initial access BWP.

<FIG> are each a diagram to show an example of frequency hopping using a cell-specific PRB offset of two values according to the first aspect. As shown in <FIG>, when the cell-specific PRB offset of two values is used, the bandwidth from each edge to the center of the initial access BWP may be equally divided into two.

In the case shown in <FIG>, as the cell-specific PRB offset, two values {<NUM>, floor((Initial_BWP/<NUM>)*(<NUM>/<NUM>))} may be used.

<FIG> are each a diagram to show another example of frequency hopping using the cell-specific PRB offset of two values according to the first aspect. <FIG> are different from <FIG> in that two values {<NUM>, floor((Initial_BWP/<NUM>)*(<NUM>/<NUM>))} are used as the cell-specific PRB offset.

<FIG> is a diagram to show an example of the RMSI index values indicating the cell-specific PRB offset of two values according to the first aspect. As shown in <FIG>, each PUCCH period may be associated with a cell-specific PRB offset of two values, and the cell-specific PRB offset of two values may be indicated by respective two different RMSI indexes. For example, in <FIG>, each of four PUCCH periods of <NUM>, <NUM>, <NUM>, and <NUM> symbols is associated with a cell-specific PRB offset of two values.

Whether the cell-specific PRB offset has the above two values or the above four values may be (<NUM>) defined in a specification, (<NUM>) determined based on a PUCCH period, or (<NUM>) determined based on an initial access BWP.

For example, when the above selection is "(<NUM>) defined in a specification", as shown in <FIG>, a table defining the RMSI index indicating the cell-specific PRB offset of four values for each PUCCH period may be provided. Alternatively, as shown in <FIG>, a table defining the RMSI index indicating the cell-specific PRB offset of two values for each PUCCH period may be provided. Alternatively, as shown in <FIG>, a table defining the RMSI index indicating the cell-specific PRB offset of four values and two values depending on a PUCCH period may be provided.

Alternatively, (<NUM>) the user terminal may determine which cell-specific PRB offset of four values or two values is to be used, based on a PUCCH period used for transmission of UCI. For example, the user terminal may determine which table of <FIG> or <FIG> is to be used, based on a PUCCH period.

Alternatively, (<NUM>) the user terminal may determine which cell-specific PRB offset of four values or two values is to be used, based on the number of PRBs constituting the initial access BWP used for transmission of UCI. For example, the user terminal may determine which table of <FIG> or <FIG> is to be used, based on the number of PRBs constituting the initial PRB.

According to the first aspect, PUCCH frequency resources to be used for frequency hopping within the initial access BWP are determined by using the cell-specific PRB offset based on the initial access BWP. Therefore, in comparison with a case where a fixed value is used as the cell-specific PRB offset, the PUCCH frequency resources can be flexibly allocated.

In the second aspect, the initial CS index in UE-specific PUCCH resources will be described.

The tables of <FIG> described above show an initial CS index of a case of r = <NUM> and an initial CS index of a case of r = <NUM> for each ARI. As described above, r may be a value based on the CCE index. For example, r may be a value obtained by normalizing the CCE index using an aggregation level, i.e., (CCE index/Aggregation level) mod <NUM>.

A base sequence to which a CS is applied may be a CAZAC (Constant Amplitude Zero Auto-Correlation) sequence such as a Zadoff-Chu sequence (for example, a sequence with a low PAPR (peak-to-average power ratio)), may be a sequence defined in a specification (for example, a sequence with a low PAPR, or a sequence given in a table), or may be a sequence in conformity to a CAZAC sequence (a CG-CAZAC (computer generated CAZAC) sequence). CS hopping based on the initial CS index may be performed. A signal using the base sequence and the CS may be a DMRS (Demodulation Reference Signal) of PF <NUM> (each value of UCI) and PF <NUM>.

In <FIG>, for example, when the ARI is "<NUM>", the UE with r = <NUM> has the initial CS index of "<NUM>", and thus uses a CS index {<NUM>, <NUM>} according to a value of UCI, whereas the UE with r = <NUM> has the initial CS index of "<NUM>", and thus uses a CS index {<NUM>, <NUM>} according to a value of UCI. Therefore, for PF <NUM>, an interval between the CS indexes corresponding to two values of UCI is <NUM>, and an interval between the CS indexes corresponding to r = <NUM> and <NUM> is <NUM>, irrespective of a value of the ARI.

Therefore, when <NUM> CS indexes are available for one PRB, the interval between the CS indexes corresponding to two values of UCI is a maximum value, and the interval between the CS indexes corresponding to r = <NUM> and <NUM> is a maximum value.

In <FIG>, for example, when the ARI is "<NUM>", the UE with r = <NUM> has the initial CS index of "<NUM>", and thus uses a CS index {<NUM>}, whereas the UE with r = <NUM> has the initial CS index of "<NUM>", and thus uses a CS index {<NUM>}. Therefore, for PF <NUM> as well, an interval between the CS indexes corresponding to r = <NUM> and <NUM> is <NUM>, irrespective of a value of the ARI.

The interval between the CS indexes corresponding to r = <NUM> and <NUM> may be increased. The interval between the CS indexes corresponding to r = <NUM> and <NUM> may be a maximum value (corresponding to phase rotation π). When <NUM> CS indexes are available for one PRB, the interval between the CS indexes corresponding to r = <NUM> and <NUM> may be a maximum value of <NUM>. For example, the initial CS index corresponding to r = <NUM> may be "<NUM>", and the initial CS index corresponding to r = <NUM> may be "<NUM>".

To use such initial CS indexes, either an independent table or a common table as described below may be used.

PUCCH resources indicated by the ARI may be specified by using individual tables for a plurality of PUCCH formats.

<FIG> is a diagram to show an example of a table for PF <NUM>. <FIG> is similar to <FIG>.

<FIG> is a diagram to show an example of a table for PF <NUM>. When comparing the table for PF <NUM> and the table for PF <NUM>, the table for PF <NUM> is different from the table for PF <NUM> in that the initial CS index corresponding to r = <NUM> of the table for PF <NUM> is "<NUM>".

For example, two CSs (CS amounts) are used in PF <NUM>, and one CS (CS amount) is used in PF <NUM>.

Therefore, when the initial CS index "<NUM>" is specified in the table for PF <NUM> shown in <FIG>, UCI is transmitted by using a CS of the CS index {<NUM>, <NUM>} according to a UCI value. When the initial CS index "<NUM>" is specified, UCI is transmitted by using a CS of the CS index {<NUM>, <NUM>} according to a UCI value.

In contrast, when the initial CS index "<NUM>" is specified in the table for PF <NUM> shown in <FIG>, UCI is transmitted by using the initial CS index {<NUM>}. In a similar manner, when the initial CS index "<NUM>" is specified, UCI is transmitted by using the initial CS index {<NUM>}.

PUCCH resources indicated by the ARI may be specified by using a common table for a plurality of PUCCH formats.

<FIG> is a diagram to show an example of a common table for PF <NUM> and PF <NUM>. In <FIG>, PUCCH resources indicated by the ARI are specified in the common table for PFs <NUM> and <NUM>.

When comparing <FIG> and <FIG>, <FIG> is different from <FIG> in that the initial CS index corresponding to r = <NUM> of <FIG> is α<NUM>. For example, α<NUM> = <NUM> may be specified for PF <NUM>, and α<NUM> = <NUM> may be specified for PF <NUM>.

In a case of PF <NUM>, when the initial CS index "<NUM>" is specified in the table shown in <FIG>, UCI is transmitted by using a CS of the CS index {<NUM>, <NUM>} according to a UCI value. When the initial CS index "<NUM>" is specified, UCI is transmitted by using a CS of the CS index {<NUM>, <NUM>} according to a UCI value.

In contrast, in a case of PF <NUM>, when the initial CS index "<NUM>" is specified in the table shown in <FIG>, UCI is transmitted by using the CS index {<NUM>}. When the initial CS index "<NUM>" is specified, UCI is transmitted by using the initial CS index {<NUM>}.

When the common table shown in <FIG> is used, tables for PFs <NUM> and <NUM> can be communalized.

Note that, in <FIG>, and <FIG>, for PF <NUM>, an interval between the initial CS indexes corresponding to r = <NUM> and <NUM> may be <NUM>. Thus, the initial CS indexes corresponding to r = <NUM> and <NUM> may be any one of {<NUM>, <NUM>}, {<NUM>, <NUM>}, and {<NUM>, <NUM>}. For PF <NUM>, an interval between the initial CS indexes corresponding to r = <NUM> and <NUM> may be <NUM>. Thus, the initial CS indexes corresponding to r = <NUM> and <NUM> may be any one of {<NUM>, <NUM>}, {<NUM>, <NUM>}, and {<NUM>, <NUM>}.

In this manner, a difference between different initial CS shift indexes (initial CS indexes corresponding to r = <NUM> and <NUM>) based on different PDCCHs (for example, CCE indexes) may be different depending on PF <NUM> and PF <NUM>.

When the table of <FIG> or <FIG> is used for PF <NUM>, the CS indexes {<NUM>} and {<NUM>} are not used, unlike the table for PF <NUM> shown in <FIG>. Note that CS indexes (for example, {<NUM>} and {<NUM>}) not specified in the table of <FIG> or <FIG> may be available as PUCCH resources after RRC connection setup.

In PF <NUM>, it may be assumed that an orthogonal sequence (time domain OCC (orthogonal cover code), OCC) is fixed. For example, in PF <NUM>, it may be assumed that information (orthogonal sequence index, SF (Spread Factor) index) i specifying an orthogonal sequence is <NUM>.

In PF <NUM>, it may be assumed that an orthogonal sequence is not used.

Therefore, when a plurality of UEs transmit PUCCHs of PF <NUM> including different CSs, a plurality of PUCCHs may be multiplexed in CDM.

According to the second aspect, for PF <NUM>, in comparison with a case of using the table of <FIG>, the interval between the CS indexes corresponding to r = <NUM> and <NUM> is increased. As a result, tolerance to frequency selectivity can be enhanced, and communication quality can be improved.

In the table shown in <FIG>, only the UE-specific PRB offset of two values can be applied to PF <NUM>. In the tables shown in <FIG> and <FIG>, however, the UE-specific PRB offset of four values can also be applied to PF <NUM>, in a similar manner to PF <NUM>. In this manner, the UE-specific PRB offset that can be applied to PF <NUM> can be increased. Therefore, PUCCH frequency resources to be used for frequency hopping within a certain bandwidth can be more flexibly determined than the table shown in <FIG>.

In the third aspect, whether frequency hopping is enabled or disabled (enable/disable) in cell-specific PUCCH resources will be described.

Information indicating whether frequency hopping is enabled or disabled may be added to the information of PUCCH resources based on the RMSI index value as in <FIG> described above.

The PUCCH may support only "frequency hopping enabled". As shown in <FIG>, the frequency hopping may be enabled in all of the PUCCH resources. Common PUCCH resources for FR (Frequency Range) <NUM> and FR <NUM> may be specified as one table.

FR <NUM> may be a frequency range lower than a certain frequency. FR <NUM> may be a frequency range lower than the certain frequency. The certain frequency may be <NUM>. FR <NUM> may be <NUM> to <NUM>, and FR <NUM> may be <NUM> to <NUM>.

Whether frequency hopping is enabled or disabled in the PUCCH may be different depending on a frequency range. PUCCH resources for FR <NUM> and PUCCH resources for FR <NUM> may be specified as independent tables.

For FR <NUM>, as shown in <FIG> described above, frequency hopping may be enabled in all of the PUCCH resources. For FR <NUM>, as shown in <FIG>, frequency hopping may be disabled in all of the PUCCH resources.

When a subcarrier spacing of FR <NUM> is higher than a subcarrier spacing of FR <NUM>, symbol time of FR <NUM> is shorter than symbol time of FR <NUM>. When PUCCH time is short with respect to time (transient time) taken before a waveform is stabilized at the time of frequency hopping, communication quality may be deteriorated. Such deterioration of communication quality can be avoided by disabling frequency hopping in FR <NUM>.

Whether frequency hopping is enabled or disabled in the PUCCH may be different depending on a frequency range and a PUCCH period. PUCCH resources for FR <NUM> and PUCCH resources for FR <NUM> may be specified as independent tables.

For FR <NUM>, as shown in <FIG> described above, it may be indicated that frequency hopping is enabled in all of the PUCCH resources. For FR <NUM>, as shown in <FIG>, frequency hopping may be disabled in PUCCH resources having a PUCCH period of a certain period or less, and frequency hopping may be enabled in PUCCH resources having a PUCCH period longer than the certain period. The certain period may be <NUM> symbols, for example.

When a subcarrier spacing of FR <NUM> is higher than a subcarrier spacing of FR <NUM>, symbol time of FR <NUM> is shorter than symbol time of FR <NUM>. When PUCCH time is short with respect to time (transient time) taken before a waveform is stabilized at the time of frequency hopping, communication quality may be deteriorated. When the PUCCH period is <NUM> symbols in FR <NUM>, the PUCCH time is particularly shortened, and thus communication quality may be deteriorated. Such deterioration of communication quality can be avoided by disabling frequency hopping when the PUCCH period of FR <NUM> is <NUM> symbols.

Note that <FIG> or <FIG> may indicate whether frequency hopping is enabled or disabled, in accordance with the rules of <FIG>, <FIG>, or <FIG>.

According to the third aspect, whether frequency hopping is enabled or disabled can be configured as cell-specific PUCCH resources. Deterioration of communication quality can be avoided if determination as to whether frequency hopping is enabled or disabled is made based on at least one of a frequency range and a PUCCH period (number of symbols).

In the fourth aspect, the orthogonal sequence in the UE-specific PUCCH resources will be described.

The UE-specific PUCCH resources may include information related to an orthogonal sequence.

When at least one of a CS and an orthogonal sequence of the PUCCH of PF <NUM> transmitted to a plurality of UEs is different, a plurality of PUCCHs may be multiplexed in CDM.

In PF <NUM>, a signal z obtained by subjecting a block y(<NUM>),. , y(Nsc - <NUM>) of a complex value symbol to be transmitted to spreading using an orthogonal sequence wi(m) may be given according to the following formula (<NUM>). [Formula <NUM>] <MAT>.

Here, Nsc represents the number (for example, <NUM>) of subcarriers in one PRB, NSF represents an orthogonal sequence capacity (number of orthogonal sequences, orthogonal sequence length), and NSF, <NUM> represents an orthogonal sequence capacity corresponding to m' = <NUM>.

As shown in <FIG>, for PF <NUM>, the PUCCH period (PUCCH length, number of PUCCH symbols) and information as to whether intra-slot frequency hopping (intra-slot hopping) is enabled or disabled may be associated with the orthogonal sequence capacity.

In the PUCCH of PF <NUM>, symbols of a DMRS and symbols of UCI may be alternately mapped. Spreading using an orthogonal sequence may be performed for the DMRS, and spreading using an orthogonal sequence may be performed for the UCI.

When intra-slot frequency hopping is enabled, two orthogonal sequence capacities, specifically, an orthogonal sequence capacity in the first hop (before hopping) and an orthogonal sequence capacity in the second hop (after hopping), are determined for each of the DMRS and the UCI. The orthogonal sequence capacity corresponding to m' = <NUM> may be the smaller orthogonal sequence capacity of the two orthogonal sequence capacities, and the orthogonal sequence capacity corresponding to m' = <NUM> may be the larger orthogonal sequence capacity of the two orthogonal sequence capacities.

As shown in <FIG>, orthogonal sequences for PF <NUM> may be specified. An orthogonal sequence of an orthogonal sequence capacity NSF is specified for each of the orthogonal sequence capacities. The orthogonal sequence may be given according to the following formula (<NUM>), using information (orthogonal sequence index) i specifying an orthogonal sequence and information ϕ related to a phase. [Formula <NUM>] <MAT>.

As shown in <FIG>, the UE-specific PUCCH resources may include an initial CS index and an orthogonal sequence index i.

When comparing <FIG> and <FIG>, <FIG> is different from <FIG> in that <FIG> includes the orthogonal sequence index i corresponding to each of r = <NUM> and r = <NUM>. The initial CS index corresponding to r = <NUM> is α<NUM>, in a similar manner to <FIG>. α<NUM> = <NUM> may be specified for PF <NUM>, and α<NUM> = <NUM> may be specified for PF <NUM>.

Note that, in <FIG>, for PF <NUM>, an interval between the initial CS indexes corresponding to r = <NUM> and <NUM> may be <NUM>. Thus, the initial CS indexes corresponding to r = <NUM> and <NUM> may be any one of {<NUM>, <NUM>}, {<NUM>, <NUM>}, and {<NUM>, <NUM>}. For PF <NUM>, an interval between the initial CS indexes corresponding to r = <NUM> and <NUM> may be <NUM>. Thus, the initial CS indexes corresponding to r = <NUM> and <NUM> may be any one of {<NUM>, <NUM>}, {<NUM>, <NUM>}, and {<NUM>, <NUM>}.

The orthogonal sequence index i corresponding to r = <NUM> may be <NUM>. The orthogonal sequence index i corresponding to r = <NUM> may be S<NUM>. S<NUM> may be determined based on the orthogonal sequence capacity NSF. For example, S<NUM> may be determined by using either of following determination methods <NUM> and <NUM>.

To obtain S<NUM> as above, S<NUM> may be calculated according to NSF - <NUM>. These two orthogonal sequence indexes may be determined so that a difference between the orthogonal sequence index corresponding to r = <NUM> and the orthogonal sequence index corresponding to r = <NUM> has a maximum value.

In PF <NUM>, multiplexing using a CS may have lower tolerance to frequency selectivity in comparison with multiplexing using an orthogonal sequence. In contrast, multiplexing using an orthogonal sequence may have lower tolerance to UE movement speed in comparison with multiplexing using a CS.

According to the fourth aspect, for PF <NUM>, by multiplexing PUCCHs of a plurality of UEs by using a CS and an orthogonal sequence, tolerance to frequency selectivity can be enhanced in comparison with a case where PUCCHs of a plurality of UEs are multiplexed using only a CS. By multiplexing PUCCHs of a plurality of UEs by using a CS and an orthogonal sequence, tolerance to frequency selectivity and tolerance to UE movement speed can be achieved.

In the fifth aspect, PUCCH resources before RRC connection may be allocated avoiding the last period of a slot.

In the PUCCH resources before RRC connection, a cell-specific frequency offset and a cell-specific time offset may be associated with each other.

For example, for the PUCCH, the UE before RRC connection determines a starting symbol index or a cell-specific symbol index offset, according to a value of the cell-specific PRB offset. The UE may use one of following determination methods <NUM> and <NUM>.

The four values {<NUM>, floor((Initial _BWP/<NUM>)*(<NUM>/<NUM>)), floor((Initial _BWP/<NUM>)*(<NUM>/<NUM>)), floor((Initial_BWP/<NUM>)*(<NUM>/<NUM>))} of the cell-specific PRB offset as shown in <FIG> may be associated with the symbol index offset of {<NUM>, <NUM>, <NUM>, <NUM>} symbols.

The UE determines a symbol index offset corresponding to the cell-specific PRB offset, according to determination of the cell-specific PRB offset. The UE allocates the PUCCH, avoiding a period of the symbol index offset from the end of a slot. For example, when the symbol index offset is <NUM>, the PUCCH is allocated up to the last symbol of a slot. When the symbol index offset is <NUM>, the PUCCH is allocated avoiding the last one symbol of a slot.

According to determination method <NUM>, when the PUCCH resources are changed to the frequency direction due to a change of the RMSI index value caused by the association between the cell-specific PRB offset and the symbol index offset, the PUCCH resources are changed to the time direction as well. The UE can allocate the PUCCH, avoiding the last zero to three symbols of a slot.

The four values {<NUM>, floor((Initial_BWP/<NUM>)*(<NUM>/<NUM>)), floor((Initial_BWP/<NUM>)*(<NUM>/<NUM>)), floor((Initial_BWP/<NUM>)*(<NUM>/<NUM>))} of the cell-specific PRB offset as shown in <FIG> may be associated with the symbol index offset of {<NUM>, <NUM>, <NUM>, <NUM>} symbols.

The UE determines a symbol index offset corresponding to the cell-specific PRB offset, according to determination of the cell-specific PRB offset. The UE allocates the PUCCH, avoiding a period of the symbol index offset from the end of a slot. For example, when the symbol index offset is <NUM>, the PUCCH is allocated up to the last symbol of a slot. When the symbol index offset is <NUM> or <NUM>, the PUCCH is allocated avoiding the last one or two symbols of a slot.

According to determination method <NUM>, when the PUCCH resources are changed to the frequency direction due to a change of the RMSI index value in the last two values of the four values of the cell-specific PRB offset, the PUCCH resources are changed to the time direction as well. The UE can allocate the PUCCH, avoiding the last zero to two symbols of a slot. It is assumed that an SRS and a short PUCCH are transmitted using <NUM> or <NUM> symbols. Therefore, if the symbol index offset is <NUM> symbols at the maximum, the PUCCH can be mapped avoiding the SRS and the short PUCCH.

The PUCCH period may be fixed irrespective of the symbol index offset. In this case, the PUCCH shifts to the start of a slot due to increase of the symbol index offset.

The PUCCH period may be changed due to the symbol index offset. For example, the PUCCH period may be shortened due to increase of the symbol index offset.

Association between the cell-specific PRB offset and the symbol index offset may be defined in a specification. The symbol index offset may be added to the tables as in <FIG>, <FIG>, <FIG>, and <FIG> to <FIG>.

According to the fifth aspect, in a cell in which an SRS (Sounding Reference Signal) or a short PUCCH (PF <NUM>, PF <NUM>) after RRC connection is transmitted using the last symbol of a slot, PUCCH resources before RRC connection can be configured so as to avoid the SRS or the short PUCCH. By associating a time direction offset and a frequency direction offset of PUCCH resources with each other, overhead for notification can be reduced in comparison with a case where the time direction offset and the frequency direction offset are independently configured.

Hereinafter, a structure of a radio communication system according to the present embodiment will be described. In the radio communication system, the radio communication method according to each aspect described above is applied. Note that the radio communication method according to each aspect described above may be employed independently, or at least two of the radio communication methods may be employed in combination.

<FIG> is a diagram to show an example of a schematic structure of the radio communication system according to the present embodiment. A radio communication system <NUM> can adopt carrier aggregation (CA) and/or dual connectivity (DC) to group a plurality of fundamental frequency blocks (component carriers) into one, where the system bandwidth in an LTE system (for example, <NUM>) constitutes one unit. Note that the radio communication system <NUM> may be referred to as SUPER <NUM>, LTE-A (LTE-Advanced), IMT-Advanced, <NUM>, <NUM>, FRA (Future Radio Access), NR (New RAT (New Radio Access Technology)), or the like.

The radio communication system <NUM> shown in <FIG> includes a radio base station <NUM> that forms a macro cell C1, and radio base stations 12a to 12c that form small cells C2, which are placed within the macro cell C1 and which are narrower than the macro cell C1. Also, user terminals <NUM> are placed in the macro cell C1 and in each small cell C2. Different numerologies may be applied among cells and/or within a cell.

Here, the numerology refers to communication parameters in the frequency direction and/or the time direction (for example, at least one of a spacing between subcarriers (subcarrier spacing), a bandwidth, a symbol length, a CP time length (CP length), a subframe length, a TTI time length (TTI length), the number of symbols in each TTI, a radio frame configuration, a filtering process, a windowing process, and so on). In the radio communication system <NUM>, for example, a subcarrier spacing such as <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> may be supported.

The user terminals <NUM> can connect with both the radio base station <NUM> and the radio base stations <NUM>. It is assumed that the user terminals <NUM> use the macro cell C1 and the small cells C2, which use different frequencies, at the same time by means of CA or DC. The user terminals <NUM> can adopt CA or DC by using a plurality of cells (CCs) (for example, two or more CCs). As the plurality of cells, the user terminals can use a licensed band CC and an unlicensed band CC.

The user terminals <NUM> can perform communication by using time division duplex (TDD) or frequency division duplex (FDD) in each cell. The TDD cell and the FDD cell may be respectively referred to as a TDD carrier (frame configuration type <NUM>), and an FDD carrier (frame configuration type <NUM>), for example.

Furthermore, in each cell (carrier), a single numerology may be employed, or a plurality of different numerologies may be employed.

Between the user terminals <NUM> and the radio base station <NUM>, communication can be carried out by using a carrier of a relatively low frequency band (for example, <NUM>) and a narrow bandwidth (referred to as, for example, an "existing carrier," a "Legacy carrier" and so on). Meanwhile, between the user terminals <NUM> and the radio base stations <NUM>, a carrier of a relatively high frequency band (for example, <NUM>, <NUM>, <NUM> to <NUM>, and so on) and a wide bandwidth may be used, or the same carrier as that used between the user terminals <NUM> and the radio base station <NUM> may be used.

Connection between the radio base station <NUM> and each radio base station <NUM> (or between two radio base stations <NUM>) may be implemented by a configuration enabling wired connection (for example, an optical fiber in compliance with CPRI (Common Public Radio Interface), an X2 interface, and so on), or enabling radio connection.

The radio base station <NUM> and the radio base stations <NUM> are each connected with a higher station apparatus <NUM>, and are connected with a core network <NUM> via the higher station apparatus <NUM>. Note that the higher station apparatus <NUM> may be, for example, an access gateway apparatus, a radio network controller (RNC), a mobility management entity (MME) and so on, but is by no means limited to these.

Note that the radio base station <NUM> is a radio base station having a relatively wide coverage, and may be referred to as a "macro base station," a "central node," an "eNB (eNodeB)," a "gNB (gNodeB)," a "transmission/reception point (TRP)" and so on. The radio base stations <NUM> are radio base stations having local coverages, and may be referred to as "small base stations," "micro base stations," "pico base stations," "femto base stations," "HeNBs (Home eNodeBs)," "RRHs (Remote Radio Heads)," "eNBs," "gNBs," "transmission/reception points" and so on. Hereinafter, the radio base stations <NUM> and <NUM> will be collectively referred to as "radio base stations <NUM>," unless specified otherwise.

Each of the user terminals <NUM> is a terminal that supports various communication schemes such as LTE, LTE-A, <NUM>, and NR, and may include not only mobile communication terminals but stationary communication terminals. The user terminal <NUM> can perform device-to-device communication (D2D) with another user terminal <NUM>.

In the radio communication system <NUM>, as radio access schemes, OFDMA (orthogonal frequency division multiple access) can be applied to the downlink (DL), and SC-FDMA (single-carrier frequency division multiple access) can be applied to the uplink (UL). OFDMA is a multi-carrier communication scheme to perform communication by dividing a frequency band into a plurality of narrow frequency bands (subcarriers) and mapping data to each subcarrier. SC-FDMA is a single carrier communication scheme to mitigate interference between terminals by dividing the system bandwidth into bands including one or continuous resource blocks per terminal, and allowing a plurality of terminals to use mutually different bands. Note that the uplink and downlink radio access schemes are by no means limited to the combinations of these, and OFDMA may be used in the UL.

In the radio communication system <NUM>, multi-carrier waveforms (for example, OFDM waveforms) may be used, or single carrier waveforms (for example, DFT-s-OFDM waveforms) may be used.

In the radio communication system <NUM>, a DL shared channel (also referred to as a PDSCH (Physical Downlink Shared Channel), a DL data channel, and so on), which is shared by the user terminals <NUM>, a broadcast channel (PBCH (Physical Broadcast Channel)), L1/L2 control channels and so on, are used as DL channels. User data, higher layer control information, SIBs (System Information Blocks) and so on are communicated on the PDSCH. The MIBs (Master Information Blocks) are communicated on the PBCH.

The L1/L2 control channels include a DL control channel (a PDCCH (Physical Downlink Control Channel) and an EPDCCH (Enhanced Physical Downlink Control Channel)), a PCFICH (Physical Control Format Indicator Channel), a PHICH (Physical Hybrid-ARQ Indicator Channel) and so on. Downlink control information (DCI), including PDSCH and PUSCH scheduling information, and so on are communicated on the PDCCH. The number of OFDM symbols to use for the PDCCH is communicated on the PCFICH. The EPDCCH is frequency-division multiplexed with the PDSCH and used to communicate DCI and so on, like the PDCCH. Retransmission control information (ACK/NACK) of a HARQ for the PUSCH can be communicated on at least one of the PHICH, the PDCCH, and the EPDCCH.

In the radio communication system <NUM>, a UL shared channel (also referred to as a PUSCH (Physical Uplink Shared Channel), an uplink shared channel, and so on), which is shared by the user terminals <NUM>, an uplink control channel (PUCCH (Physical Uplink Control Channel)), a random access channel (PRACH (Physical Random Access Channel)) and so on are used as UL channels. User data and higher layer control information are communicated on the PUSCH. Uplink control information (UCI) including at least one of retransmission control information (A/N) and channel state information (CSI) of DL signals and so on is communicated on the PUSCH or the PUCCH. By means of the PRACH, random access preambles for establishing connections with cells can be communicated.

<FIG> is a diagram to show an example of an overall structure of the radio base station according to the present embodiment. A radio base station <NUM> includes a plurality of transmitting/receiving antennas <NUM>, amplifying sections <NUM>, transmitting/receiving sections <NUM>, a baseband signal processing section <NUM>, a call processing section <NUM> and a transmission line interface <NUM>. Note that the radio base station <NUM> may be configured to include one or more transmitting/receiving antennas <NUM>, one or more amplifying sections <NUM> and one or more transmitting/receiving sections <NUM>.

User data to be transmitted from the radio base station <NUM> to the user terminal <NUM> by the DL is input from the higher station apparatus <NUM> to the baseband signal processing section <NUM>, via the transmission line interface <NUM>.

In the baseband signal processing section <NUM>, the user data is subjected to transmission processes, such as a PDCP (Packet Data Convergence Protocol) layer process, division and coupling of the user data, RLC (Radio Link Control) layer transmission processes such as RLC retransmission control, MAC (Medium Access Control) retransmission control (for example, an HARQ (Hybrid Automatic Repeat reQuest) transmission process), scheduling, transport format selection, channel coding, an inverse fast Fourier transform (IFFT) process, and a precoding process, and the result is forwarded to each transmitting/receiving section <NUM>.

The transmitting/receiving sections <NUM> convert baseband signals that are pre-coded and output from the baseband signal processing section <NUM> on a per antenna basis, to have radio frequency bands and transmit the result. The radio frequency signals having been subjected to frequency conversion in the transmitting/receiving sections <NUM> are amplified in the amplifying sections <NUM>, and transmitted from the transmitting/receiving antennas <NUM>.

It is possible to adopt constitution with transmitters/receivers, transmitting/receiving circuits or transmitting/receiving apparatus that can be described based on general understanding of the technical field to which the present invention pertains. Note that each transmitting/receiving section <NUM> may be structured as a transmitting/receiving section in one entity, or may be constituted with a transmitting section and a receiving section.

Meanwhile, as for UL signals, radio frequency signals that are received in the transmitting/receiving antennas <NUM> are amplified in the amplifying sections <NUM>. The transmitting/receiving sections <NUM> receive the UL signals amplified in the amplifying sections <NUM>.

In the baseband signal processing section <NUM>, UL data that is included in the UL signals that are input is subjected to a fast Fourier transform (FFT) process, an inverse discrete Fourier transform (IDFT) process, error correction decoding, a MAC retransmission control receiving process, and RLC layer and PDCP layer receiving processes, and forwarded to the higher station apparatus <NUM> via the transmission line interface <NUM>. The call processing section <NUM> performs call processing, such as setting up and releasing for communication channels, manages the state of the radio base station <NUM>, and manages the radio resources.

The transmission line interface <NUM> transmits and/or receives signals to and/or from the higher station apparatus <NUM> via a certain interface. The transmission line interface <NUM> may transmit and/or receive signals (backhaul signaling) with neighboring radio base stations <NUM> via an inter-base station interface (for example, an optical fiber in compliance with the CPRI (Common Public Radio Interface) and an X2 interface).

The transmitting/receiving sections <NUM> transmit DL signals (including at least one of a DL data signal, a DL control signal (DCI), a DL reference signal, and system information (for example, RMSI, SIBs, and MIBs)) to the user terminals <NUM>, and receive UL signals (including at least one of a UL data signal, a UL control signal, and a UL reference signal) from the user terminals <NUM>.

The transmitting/receiving sections <NUM> receive UCI from the user terminals <NUM> by using an uplink shared channel (for example, a PUSCH) or an uplink control channel (for example, a short PUCCH and/or a long PUCCH). The UCI may include at least one of a HARQ-ACK, CSI, an SR, beam identification information (for example, beam index (BI)), a buffer status report (BSR) of a DL data channel (for example, a PDSCH).

The transmitting/receiving sections <NUM> may receive uplink control information by using an uplink control channel. The transmitting/receiving sections <NUM> may transmit system information (for example, RMSI) including index value(s) of one or more resources (PUCCH resources) for the uplink control channel. The transmitting/receiving sections <NUM> may transmit downlink control information (downlink control channel) including index value(s) (for example, ARI(s)) indicating one or more resources for the uplink control channel.

<FIG> is a diagram to show an example of a functional structure of the radio base station according to the present embodiment. Note that <FIG> primarily shows functional blocks that pertain to characteristic parts of the present embodiment, and it is assumed that the radio base station <NUM> includes other functional blocks that are necessary for radio communication as well. As shown in <FIG>, the baseband signal processing section <NUM> includes a control section <NUM>, a transmission signal generation section <NUM>, a mapping section <NUM>, a received signal processing section <NUM>, and a measurement section <NUM>.

The control section <NUM> controls the whole of the radio base station <NUM>. The control section <NUM>, for example, controls the generation of DL signals in the transmission signal generation section <NUM>, the mapping of DL signals in the mapping section <NUM>, the UL signal receiving processes (for example, demodulation and so on) in the received signal processing section <NUM>, and the measurements in the measurement section <NUM>.

Specifically, the control section <NUM> performs scheduling of the user terminals <NUM>. Specifically, the control section <NUM> may perform scheduling and/or retransmission control of the DL data and/or the uplink shared channel, based on UCI (for example, CSI and/or BIs) from the user terminals <NUM>.

The control section <NUM> may control a configuration (format) of an uplink control channel (for example, a long PUCCH and/or a short PUCCH), and may perform control so as to transmit control information related to the uplink control channel.

The control section <NUM> may control PUCCH resources. Specifically, the control section <NUM> may determine one or more PUCCH resources to be notified to the user terminals <NUM>. The control section <NUM> may control at least one of the generation and the transmission of system information (for example, RMSI) indicating at least one of the determined PUCCH resources.

The control section <NUM> may determine an index value to be included in the system information from among a plurality of index values indicating at least different numbers of PUCCH resources. For example, the control section <NUM> may determine the index value, based on the number of user terminals within a cell.

The control section <NUM> may control the received signal processing section <NUM> so as to perform receiving processes for UCI from the user terminals <NUM>, based on a format of the uplink control channel.

The control section <NUM> may control reception of the uplink control channel using an initial cyclic shift index based on the downlink control channel. A difference between a plurality of initial cyclic shift indexes based on a plurality of downlink control channels may be different depending on a format of the uplink control channel.

The control section <NUM> can be constituted with a controller, a control circuit or control apparatus that can be described based on general understanding of the technical field to which the present invention pertains.

The transmission signal generation section <NUM> generates DL signals (including a DL data signal, a DL control signal, and a DL reference signal) based on commands from the control section <NUM> and outputs the DL signals to the mapping section <NUM>.

The transmission signal generation section <NUM> can be constituted with a signal generator, a signal generation circuit or signal generation apparatus that can be described based on general understanding of the technical field to which the present invention pertains.

The mapping section <NUM> maps the DL signals generated in the transmission signal generation section <NUM> to certain radio resources, based on commands from the control section <NUM>, and outputs these to the transmitting/receiving sections <NUM>. The mapping section <NUM> can be constituted with a mapper, a mapping circuit or mapping apparatus that can be described based on general understanding of the technical field to which the present invention pertains.

The received signal processing section <NUM> performs receiving processes (for example, demapping, demodulation, decoding and so on) of UL signals (for example, including a UL data signal, a UL control signal, and a UL reference signal) that are transmitted from the user terminals <NUM>. Specifically, the received signal processing section <NUM> may output the received signals and signals after the receiving processes to the measurement section <NUM>. The received signal processing section <NUM> performs UCI receiving processes, based on an uplink control channel configuration indicated by the control section <NUM>.

The measurement section <NUM> can be constituted with a measurer, a measurement circuit or measurement apparatus that can be described based on general understanding of the technical field to which the present invention pertains.

The measurement section <NUM>, for example, may measure UL channel quality, based on UL reference signal received power (for example, RSRP (Reference Signal Received Power)) and/or received quality (for example, RSRQ (Reference Signal Received Quality)). The measurement results may be output to the control section <NUM>.

<FIG> is a diagram to show an example of an overall structure of the user terminal according to the present embodiment. A user terminal <NUM> includes a plurality of transmitting/receiving antennas <NUM> for MIMO communication, amplifying sections <NUM>, transmitting/receiving sections <NUM>, a baseband signal processing section <NUM> and an application section <NUM>.

Radio frequency signals that are received in the plurality of transmitting/receiving antennas <NUM> are amplified in respective amplifying sections <NUM>. The transmitting/receiving sections <NUM> receive the DL signals amplified in the amplifying sections <NUM>. The transmitting/receiving sections <NUM> convert the received signals into baseband signals through frequency conversion, and output the baseband signals to the baseband signal processing section <NUM>.

The baseband signal processing section <NUM> performs, on each input baseband signal, an FFT process, error correction decoding, a retransmission control receiving process, and so on. The DL data is forwarded to the application section <NUM>. The application section <NUM> performs processes related to higher layers above the physical layer and the MAC layer, and so on. Broadcast information is also forwarded to the application section <NUM>.

Meanwhile, the UL data is input from the application section <NUM> to the baseband signal processing section <NUM>. The baseband signal processing section <NUM> performs a retransmission control transmission process (for example, an HARQ transmission process), channel coding, rate matching, puncturing, a discrete Fourier transform (DFT) process, an IFFT process and so on, and the result is forwarded to the transmitting/receiving sections <NUM>. UCI is also subjected to at least one of channel coding, rate matching, puncturing, a DFT process, and an IFFT process, and is forwarded to the transmitting/receiving sections <NUM>.

The transmitting/receiving sections <NUM> convert the baseband signals output from the baseband signal processing section <NUM> to have radio frequency band and transmit the result. The radio frequency signals having been subjected to frequency conversion in the transmitting/receiving sections <NUM> are amplified in the amplifying sections <NUM>, and transmitted from the transmitting/receiving antennas <NUM>.

The transmitting/receiving sections <NUM> receive DL signals (including at least one of a DL data signal, a DL control signal (DCI), a DL reference signal, and system information (for example, RMSI, SIBs, MIBs)) for the user terminals <NUM>, and transmit UL signals (including at least one of a UL data signal, a UL control signal, and a UL reference signal) from the user terminals <NUM>.

The transmitting/receiving sections <NUM> transmit UCI to the radio base station <NUM> by using an uplink shared channel (for example, a PUSCH) or an uplink control channel (for example, a short PUCCH and/or a long PUCCH).

The transmitting/receiving sections <NUM> may transmit uplink control information by using an uplink control channel. The transmitting/receiving sections <NUM> may receive system information (for example, RMSI) including index value(s) of one or more resources (PUCCH resources) for the uplink control channel. The transmitting/receiving sections <NUM> may receive downlink control information (downlink control channel) including index value(s) (for example, ARI(s)) indicating one or more resources for the uplink control channel.

The transmitting/receiving sections <NUM> can be constituted with transmitters/receivers, transmitting/receiving circuits or transmitting/receiving apparatus that can be described based on general understanding of the technical field to which the present invention pertains. Further, each transmitting/receiving section <NUM> may be structured as a transmitting/receiving section in one entity, or may be constituted with a transmitting section and a receiving section.

<FIG> is a diagram to show an example of a functional structure of the user terminal according to the present embodiment. Note that <FIG> primarily shows functional blocks that pertain to characteristic parts of the present embodiment, and it is assumed that the user terminal <NUM> includes other functional blocks that are necessary for radio communication as well. As shown in <FIG>, the baseband signal processing section <NUM> provided in the user terminal <NUM> includes a control section <NUM>, a transmission signal generation section <NUM>, a mapping section <NUM>, a received signal processing section <NUM> and a measurement section <NUM>.

The control section <NUM>, for example, controls the generation of UL signals in the transmission signal generation section <NUM>, the mapping of UL signals in the mapping section <NUM>, the DL signal receiving processes in the received signal processing section <NUM>, and the measurements in the measurement section <NUM>.

The control section <NUM> controls an uplink control channel used for transmission of UCI from the user terminals <NUM>, based on an explicit indication from the radio base station <NUM> or implicit determination of the user terminals <NUM>.

The control section <NUM> may control a configuration (format) of the uplink control channel (for example, a long PUCCH and/or a short PUCCH). The control section <NUM> may control the format of the uplink control channel, based on control information from the radio base station <NUM>. The control section <NUM> may control a PUCCH format (format of the uplink control channel) used for transmission of UCI, based on information related to a fallback.

The control section <NUM> may determine PUCCH resources to be used for transmission of UCI, based on at least one of information via higher layer signaling, downlink control information, and an implicit value.

Specifically, when the control section <NUM> transmits UCI by using an uplink control channel before RRC (Radio Resource Control) connection setup, the control section <NUM> may determine resources for the uplink control channel to be used for transmission of the UCI, based on an index in system information (for example, RMSI).

For example, the control section <NUM> may determine resources for transmission of the uplink control information, based on at least one of a bit value and an implicit value in downlink control information, from among one or more PUCCH resources indicated by the index value included in the system information.

The control section <NUM> may determine frequency resources for an uplink control channel to be used for frequency hopping within the certain bandwidth, based on a value based on a certain bandwidth or a cell-specific PRB offset (first offset value) being <NUM>.

The certain bandwidth may be a certain number of physical resource blocks constituting an initial access BWP (a bandwidth part used for initial access of the user terminal <NUM>).

The cell-specific PRB offset value may have two values or four values. The control section <NUM> may determine whether the cell-specific PRB offset value has two values or the four values, based on at least one of a specification (table determined in advance), a period of the uplink control channel, and the certain bandwidth.

The control section <NUM> may determine the frequency resources for the uplink control channel, based on a cell-specific PRB offset value and a UE-specific PRB offset value (second offset value) that is indicated by at least one of an index value and an implicit value in downlink control information.

The control section <NUM> may control acquisition of PUCCH resources from a table (for example, <FIG>, <FIG>, and <FIG>) stored in a storage section, based on an index value in system information (for example, an RMSI index). The control section <NUM> may control acquisition of PUCCH resources from a table (for example, <FIG>, <FIG>) stored in a storage section, based on an index value in DCI (for example, an ARI).

The control section <NUM> may determine an initial cyclic shift index for an uplink control channel, based on a downlink control channel. A difference between a plurality of initial cyclic shift indexes (initial CS indexes corresponding to r = <NUM> and <NUM>) based on a plurality of downlink control channels (for example, PDCCH CCE indexes) may be different depending on a format of an uplink control channel (for example, PF <NUM> and PF <NUM>).

A difference between two initial cyclic shift indexes corresponding to a certain format of an uplink control channel (for example, PF <NUM>) may be a maximum value (for example, corresponding to <NUM> or phase rotation n) (second aspect).

The control section <NUM> may apply a certain orthogonal sequence to an uplink control channel, or may not apply an orthogonal sequence to the uplink control channel (second aspect).

The control section <NUM> may apply an orthogonal sequence to an uplink control channel. The control section <NUM> may determine an orthogonal sequence (for example, an orthogonal sequence index i), based on at least one of a downlink control channel (for example, a PDCCH CCE index) and a length of the orthogonal sequence (for example, NSF) (fourth aspect).

The control section <NUM> may determine whether or not to perform frequency hopping of an uplink control channel, based on at least one of an index value and a frequency range (third aspect).

The transmission signal generation section <NUM> generates (for example, coding, rate matching, puncturing, modulation, and so on) UL signals (including a UL data signal, a UL control signal, a UL reference signal, and UCI) based on commands from the control section <NUM>, and outputs the UL signals to the mapping section <NUM>. The transmission signal generation section <NUM> can be constituted with a signal generator, a signal generation circuit or signal generation apparatus that can be described based on general understanding of the technical field to which the present invention pertains.

The mapping section <NUM> maps the UL signals generated in the transmission signal generation section <NUM> to radio resources, based on commands from the control section <NUM>, and outputs the result to the transmitting/receiving sections <NUM>. The mapping section <NUM> can be constituted with a mapper, a mapping circuit or mapping apparatus that can be described based on general understanding of the technical field to which the present invention pertains.

The received signal processing section <NUM> performs receiving processes (for example, demapping, demodulation, decoding and so on) of DL signals (a DL data signal, scheduling information, a DL control signal, a DL reference signal). The received signal processing section <NUM> outputs information received from the radio base station <NUM> to the control section <NUM>. The received signal processing section <NUM>, for example, outputs broadcast information, system information, higher layer control information via higher layer signaling such as RRC signaling, physical layer control information (L1/L2 control information) and so on to the control section <NUM>.

The received signal processing section <NUM> can be constituted with a signal processor, a signal processing circuit or signal processing apparatus that can be described based on general understanding of the technical field to which the present invention pertains. The received signal processing section <NUM> can constitute the receiving section according to the present invention.

The measurement section <NUM> measures a channel state based on a reference signal (for example, a CSI-RS) from the radio base station <NUM>, and outputs measurement results to the control section <NUM>. Note that the measurement of the channel state may be performed for each CC.

The measurement section <NUM> can be constituted with a signal processor, a signal processing circuit, a signal processing apparatus, a measurer, a measurement circuit or measurement apparatus that can be described based on general understanding of the technical field to which the present invention pertains.

Note that the block diagrams that have been used to describe the above embodiments show blocks in functional units. These functional blocks (components) may be implemented in arbitrary combinations of hardware and/or software. Also, the method for implementing each functional block is not particularly limited. That is, each functional block may be realized by one piece of apparatus that is physically and/or logically aggregated, or may be realized by directly and/or indirectly connecting two or more physically and/or logically separate pieces of apparatus (via wire and/or wireless, for example) and using these plurality of pieces of apparatus.

For example, a radio base station, a user terminal, and so on according to one embodiment of the present invention may function as a computer that executes the processes of the radio communication method of the present invention. <FIG> is a diagram to show an example of a hardware structure of the radio base station and the user terminal according to one embodiment of the present invention. Physically, the above-described radio base station <NUM> and user terminals <NUM> may each be formed as computer apparatus that includes a processor <NUM>, a memory <NUM>, a storage <NUM>, a communication apparatus <NUM>, an input apparatus <NUM>, an output apparatus <NUM>, a bus <NUM>, and so on.

Note that, in the following description, the word "apparatus" may be interpreted as "circuit," "device," "unit," and so on. The hardware structure of the radio base station <NUM> and the user terminals <NUM> may be designed to include one or a plurality of apparatuses shown in the drawings, or may be designed not to include part of pieces of apparatus.

Each function of the radio base station <NUM> and the user terminals <NUM> is implemented, for example, by allowing certain software (programs) to be read on hardware such as the processor <NUM> and the memory <NUM>, and by allowing the processor <NUM> to perform calculations to control communication via the communication apparatus <NUM> and control reading and/or writing of data in the memory <NUM> and the storage <NUM>.

Furthermore, the processor <NUM> reads programs (program codes), software modules, data, and so on from the storage <NUM> and/or the communication apparatus <NUM>, into the memory <NUM>, and executes various processes according to these. As for the programs, programs to allow computers to execute at least part of the operations of the above-described embodiments are used. For example, the control section <NUM> of each user terminal <NUM> may be implemented by control programs that are stored in the memory <NUM> and that operate on the processor <NUM>, and other functional blocks may be implemented likewise.

The memory <NUM> is a computer-readable recording medium, and may be constituted with, for example, at least one of a ROM (Read Only Memory), an EPROM (Erasable Programmable ROM), an EEPROM (Electrically EPROM), a RAM (Random Access Memory), and other appropriate storage media. The memory <NUM> may be referred to as a "register," a "cache," a "main memory (primary storage apparatus)" and so on. The memory <NUM> can store executable programs (program codes), software modules, and the like for implementing the radio communication method according to one embodiment of the present invention.

The communication apparatus <NUM> is hardware (transmitting/receiving device) for allowing inter-computer communication via a wired and/or wireless network, and may be referred to as, for example, a "network device," a "network controller," a "network card," a "communication module," and so on. The communication apparatus <NUM> may be configured to include a high frequency switch, a duplexer, a filter, a frequency synthesizer, and so on in order to realize, for example, frequency division duplex (FDD) and/or time division duplex (TDD). For example, the above-described transmitting/receiving antennas <NUM> (<NUM>), amplifying sections <NUM> (<NUM>), transmitting/receiving sections <NUM> (<NUM>), transmission line interface <NUM>, and so on may be implemented by the communication apparatus <NUM>.

Also, the radio base station <NUM> and the user terminals <NUM> may be structured to include hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), an FPGA (Field Programmable Gate Array), and so on, and part or all of the functional blocks may be implemented by the hardware.

Note that the terminology described in this specification and/or the terminology that is needed to understand this specification may be replaced by other terms that convey the same or similar meanings. For example, "channels" and/or "symbols" may be "signals" ("signaling"). Also, "signals" may be "messages. " A reference signal may be abbreviated as an "RS," and may be referred to as a "pilot," a "pilot signal," and so on, depending on which standard applies. Furthermore, a "component carrier (CC)" may be referred to as a "cell," a "frequency carrier," a "carrier frequency" and so on.

Furthermore, a slot may be constituted of one or a plurality of symbols in the time domain (OFDM (Orthogonal Frequency Division Multiplexing) symbols, SC-FDMA (Single Carrier Frequency Division Multiple Access) symbols, and so on). Furthermore, a slot may be a time unit based on numerology. A slot may include a plurality of mini-slots. Each mini-slot may be constituted of one or a plurality of symbols in the time domain. A mini-slot may be referred to as a "sub-slot.

A radio frame, a subframe, a slot, a mini-slot, and a symbol all express time units in signal communication. A radio frame, a subframe, a slot, a mini-slot, and a symbol may each be called by other applicable terms. For example, one subframe may be referred to as a "transmission time interval (TTI)," a plurality of consecutive subframes may be referred to as a "TTI" or one slot or one mini-slot may be referred to as a "TTI. " That is, a subframe and/or a TTI may be a subframe (<NUM>) in existing LTE, may be a shorter period than <NUM> (for example, <NUM> to <NUM> symbols), or may be a longer period than <NUM>. Note that a unit expressing TTI may be referred to as a "slot," a "mini-slot," and so on instead of a "subframe.

TTIs may be transmission time units for channel-encoded data packets (transport blocks), code blocks, and/or codewords, or may be the unit of processing in scheduling, link adaptation, and so on. Note that, when TTIs are given, the time interval (for example, the number of symbols) to which transport blocks, code blocks, and/or codewords are actually mapped may be shorter than the TTIs.

A TTI having a time length of <NUM> may be referred to as a "normal TTI" (TTI in LTE Rel. <NUM> to Rel. <NUM>), a "long TTI," a "normal subframe," a "long subframe" and so on. A TTI that is shorter than a normal TTI may be referred to as a "shortened TTI," a "short TTI," a "partial or fractional TTI," a "shortened subframe," a "short subframe," a "mini-slot," a "sub-slot" and so on.

A resource block (RB) is the unit of resource allocation in the time domain and the frequency domain, and may include one or a plurality of consecutive subcarriers in the frequency domain. Also, an RB may include one or a plurality of symbols in the time domain, and may be one slot, one mini-slot, one subframe, or one TTI in length. One TTI and one subframe each may be constituted of one or a plurality of resource blocks. Note that one or a plurality of RBs may be referred to as a "physical resource block (PRB (Physical RB))," a "sub-carrier group (SCG)," a "resource element group (REG),"a "PRB pair," an "RB pair" and so on.

Also, the information, parameters, and so on described in this specification may be represented in absolute values or in relative values with respect to certain values, or may be represented in another corresponding information. For example, radio resources may be specified by certain indices.

For example, since various channels (PUCCH (Physical Uplink Control Channel), PDCCH (Physical Downlink Control Channel), and so on) and information elements can be identified by any suitable names, the various names allocated to these various channels and information elements are in no respect limiting.

The information, signals, and so on described in this specification may be represented by using any of a variety of different technologies.

Also, information, signals, and so on can be output from higher layers to lower layers, and/or from lower layers to higher layers. Information, signals, and so on may be input and/or output via a plurality of network nodes.

Reporting of information is by no means limited to the aspects/embodiments described in this specification, and other methods may be used as well. For example, reporting of information may be implemented by using physical layer signaling (for example, downlink control information (DCI), uplink control information (UCI), higher layer signaling (for example, RRC (Radio Resource Control) signaling, broadcast information (master information block (MIB), system information blocks (SIBs), and so on), MAC (Medium Access Control) signaling and so on), and other signals and/or combinations of these.

Note that physical layer signaling may be referred to as "L1/L2 (Layer <NUM>/Layer <NUM>) control information (L1/L2 control signals)," "L1 control information (L1 control signal)," and so on. Also, RRC signaling may be referred to as an "RRC message," and can be, for example, an RRC connection setup (RRCConnectionSetup) message, an RRC connection reconfiguration (RRCConnectionReconfiguration) message, and so on. Also, MAC signaling may be reported using, for example, MAC control elements (MAC CEs).

Also, software, commands, information, and so on may be transmitted and received via communication media. For example, when software is transmitted from a website, a server, or other remote sources by using wired technologies (coaxial cables, optical fiber cables, twisted-pair cables, digital subscriber lines (DSL), and so on) and/or wireless technologies (infrared radiation, microwaves, and so on), these wired technologies and/or wireless technologies are also included in the definition of communication media.

The terms "system" and "network" used in this specification may be used interchangeably.

In the present specification, the terms "base station (BS)," "radio base station," "eNB," "gNB," "cell," "sector," "cell group," "carrier," and "component carrier" may be used interchangeably. A base station may be referred to as a "fixed station," "NodeB," "eNodeB (eNB)," "access point," "transmission point," "reception point," "transmission/reception point," "femto cell," "small cell" and so on.

A base station can accommodate one or a plurality of (for example, three) cells (also referred to as "sectors"). When a base station accommodates a plurality of cells, the entire coverage area of the base station can be partitioned into multiple smaller areas, and each smaller area can provide communication services through base station subsystems (for example, indoor small base stations (RRHs (Remote Radio Heads))). The term "cell" or "sector" refers to part of or the entire coverage area of a base station and/or a base station subsystem that provides communication services within this coverage.

In the present specification, the terms "mobile station (MS)," "user terminal," "user equipment (UE)," and "terminal" may be used interchangeably.

A base station and/or a mobile station may be referred to as a "transmitting apparatus," a "receiving apparatus," and so on.

Furthermore, the radio base stations in this specification may be interpreted as user terminals. For example, each aspect/embodiment of the present invention may be applied to a configuration in which communication between a radio base station and a user terminal is replaced with communication among a plurality of user terminals (D2D (Device-to-Device)). In this case, the user terminals <NUM> may have the functions of the radio base stations <NUM> described above. In addition, wording such as "uplink" and "downlink" may be interpreted as "side. " For example, an uplink channel may be interpreted as a side channel.

Actions which have been described in this specification to be performed by a base station may, in some cases, be performed by upper nodes. In a network including one or a plurality of network nodes with base stations, it is clear that various operations that are performed to communicate with terminals can be performed by base stations, one or more network nodes (for example, MMEs (Mobility Management Entities), S-GW (Serving-Gateways), and so on may be possible, but these are not limiting) other than base stations, or combinations of these.

The order of processes, sequences, flowcharts, and so on that have been used to describe the aspects/embodiments herein may be re-ordered as long as inconsistencies do not arise.

The aspects/embodiments illustrated in this specification may be applied to LTE (Long Term Evolution), LTE-A (LTE-Advanced), LTE-B (LTE-Beyond), SUPER <NUM>, IMT-Advanced, <NUM> (4th generation mobile communication system), <NUM> (5th generation mobile communication system), FRA (Future Radio Access), New-RAT (Radio Access Technology), NR (New Radio), NX (New radio access), FX (Future generation radio access), GSM (registered trademark) (Global System for Mobile communications), CDMA <NUM>, UMB (Ultra Mobile Broadband), IEEE <NUM> (Wi-Fi (registered trademark)), IEEE <NUM> (WiMAX (registered trademark)), IEEE <NUM>, UWB (Ultra-WideBand), Bluetooth (registered trademark), systems that use other adequate radio communication methods and/or next-generation systems that are enhanced based on these.

The phrase "based on" (or "on the basis of") as used in this specification does not mean "based only on" (or "only on the basis of"), unless otherwise specified.

Reference to elements with designations such as "first," "second" and so on as used herein does not generally limit the quantity or order of these elements. These designations may be used herein only for convenience, as a method for distinguishing between two or more elements. Thus, reference to the first and second elements does not imply that only two elements may be employed, or that the first element must precede the second element in some way.

The term "judging (determining)" as used herein may encompass a wide variety of actions. For example, "judging (determining)" may be interpreted to mean making "judgments (determinations)" about calculating, computing, processing, deriving, investigating, looking up, (for example, searching a table, a database, or some other data structures), ascertaining, and so on. In addition, "judging (determining)" as used herein may be interpreted to mean making "judgments (determinations)" about resolving, selecting, choosing, establishing, comparing, and so on. In other words, "judging (determining)" may be interpreted to mean making "judgments (determinations)" about some action.

The terms "connected" and "coupled," or any variation of these terms as used herein mean all direct or indirect connections or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other.

In this specification, when two elements are connected, the two elements may be considered "connected" or "coupled" to each other by using one or more electrical wires, cables and/or printed electrical connections, and, as some non-limiting and non-inclusive examples, by using electromagnetic energy having wavelengths in radio frequency regions, microwave regions and/or (both visible and invisible) optical regions, or the like.

In this specification, the phrase "A and B are different" may mean that "A and B are different from each other. " The terms "separate," "be coupled" and so on may be interpreted similarly.

When terms such as "including," "comprising," and variations of these are used in this specification or in claims, these terms are intended to be inclusive, in a manner similar to the way the term "provide" is used.

Claim 1:
A terminal (<NUM>) comprising:
a receiving section (<NUM>) configured to receive a physical downlink control channel, PDCCH; and
a control section (<NUM>) configured to determine, based on the PDCCH, an initial cyclic shift index from a parameter set for a physical uplink control channel, PUCCH, before radio resource control, RRC, connection,
wherein if the parameter set is either an initial cyclic shift index set {<NUM>,<NUM>} for PUCCH format <NUM> or an initial cyclic index set {<NUM>, <NUM>} for PUCCH format <NUM>, then the initial cyclic shift index depends on a control channel element, CCE, index for the PDCCH, and then physical resource block, PRB, indexes in a first hopping direction and in a second hopping direction of the PUCCH depend on a PUCCH resource indicator field value.