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>). In addition, successor systems of LTE are also under study for the purpose of achieving further broadbandization and increased speed beyond LTE (referred to as, for example, "LTE-A (LTE-Advanced)," "FRA (Future Radio Access)," "<NUM>, " "<NUM>, " "<NUM>+ (plus)," "NR (New RAT)," "LTE Rel. <NUM>," "LTE Rel. <NUM> (or later versions)," and so on).

In existing LTE systems (for example, LTE Rel. <NUM> to Rel. <NUM>), downlink (DL) and/or uplink (UL) communications are carried out using <NUM> subframes (referred to as, for example, "transmission time intervals (TTIs)"). This subframe is the unit of time to transmit one data packet that is channel-encoded, and is the processing unit in scheduling, link adaptation, retransmission control (HARQ (Hybrid Automatic Repeat reQuest), and so on.

In 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, PUCCH (Physical Uplink Control Channel)) or an uplink data channel (for example, PUSCH (Physical Uplink Shared Channel)). A structure (format) of the uplink control channel is referred to as a "PUCCH format (PF)," for example.

<CIT> discloses a method of PUCCH resource allocation for a MTC device comprising: receiving a physical downlink data channel (PDSCH); determining corresponding physical uplink control channel (PUCCH) resource based on one or more following parameters used for the PDSCH transmission: MTC band index, the lowest physical resource block (PRB) index and antenna port index; and transmitting ACK/NACK of the PDSCH on the determined PUCCH resource.

<CIT> discloses a UE that receives downlink control information from an eNB through a PDCCH (Physical Downlink Control channel) including one or more CCEs (Control Channel Elements). The UE transmits ACK/NACK (ACKnowledgment/Negative ACK) information associated with the downlink control information to the eNB by using at least one of a first PUCCH resource, which corresponds to an index determined on the basis of first offset information and an index of a specific CCE in the PDCCH and is generated using first cell identification information, and a second PUCCH resource, which corresponds to an index determined on the basis of second offset information and the index of the specific CCE and is generated using second cell identification information.

<CIT> discloses a technology for communicating data and control information on an uplink channel in a wireless communication system. A frame is constructed to communicate symbols between a base station and user equipment, and zones are configured for an uplink channel in an uplink subframe using a signaling message. A first zone in the uplink channel is configured as a physical uplink control channel (PUCCH) for transmission of control information and a second zone is configured as a physical uplink shared channel (PUSCH) for transmission of data information. The PUCCH zone configuration is transmitted to the user equipment by the base station, control information is received by the base station as uplink control information (UCI) on the PUCCH resource using a single carrier modulation, such as SC-FDMA, and the data is received at the base station on the PUSCH resource using a multicarrier modulation, such as OFDM.

In the standard contribution <NPL>", the authors disclose implicit PUCCH resource indication for PUCCH format with small UCI payload for RRC-connected mode and Msg <NUM>, as well as options for explicit resource indication.

<CIT> discloses communication using an uplink control channel that is configured to suit a short transmission time interval (TTI). A user terminal is provided with a transmitter for transmitting uplink control information via an uplink control channel and a control unit for controlling transmission of the uplink control information in a short TTI configured from a smaller number of symbols than in a normal TTI. The control unit transmits the uplink control information in a resource block for frequency-hopping between slots in the short TTI and maps a reference signal for demodulation to at least one symbol that constitutes the short slot.

For future radio communication systems (for example, LTE Rel. <NUM>, LTE Rel. <NUM> or later versions, <NUM>, NR, and so on), a study is underway to adopt frequency hopping in which a frequency resource to which an uplink channel and/or an uplink signal (uplink channel/signal) (at least one of, for example, an uplink control channel (PUCCH), an uplink data channel (PUSCH), a sounding reference signal (SRS), and so on) is mapped hops within a slot (intra-slot frequency hopping).

In the future radio communication systems, it is assumed that an accessible bandwidth (access BW (bandwidth)) is configured for each user terminal. Here, the access BW may be also referred to as a "carrier (component carrier (CC) or a system band)," or a "partial frequency band in the carrier (partial band)" or a "bandwidth part (BWP)"), and so on.

It is desired to appropriately control, in the future radio communication systems in which different access BWs may thus be configured for a plurality of user terminals, a pattern of intra-slot frequency hopping for an uplink channel/signal (positions of frequency resources for hopping and/or hopping timings (hopping boundaries) and so on).

The present invention has been made in view of the above, and it is therefore an object of the present invention to provide a user terminal and a radio communication method, whereby intra-slot frequency hopping of an uplink channel/signal can be controlled appropriately.

The present invention also provides a radio communication method, in accordance with claim <NUM>, and a radio communication system, in accordance with claim <NUM>.

According to the present invention, it is possible to appropriately control intra-slot frequency hopping for an uplink channel/signal.

Existing LTE systems (LTE Rel. <NUM> or former versions) support uplink control channels (for example, PUCCHs) of a plurality of formats (for example, LTE PUCCH formats (LTE PFs) <NUM> to <NUM> and so on) for the same duration (for example, <NUM> symbols in a normal cyclic prefix (CP)).

In future radio communication systems (for example, LTE Rel. <NUM> or later versions, <NUM>, NR, and so on), a study is underway to transmit UCI by using uplink control channels (for example, PUCCHs) of a plurality of formats (for example, NR PUCCH formats (NR PFs), also referred to simply as "PUCCH formats") different from each other at least in period.

<FIG> are diagrams to show examples of a PUCCH in a future radio communication system. <FIG> shows a PUCCH (a short PUCCH or first uplink control channel) constituted of a relatively small number of symbols (duration, for example, one to two symbols). <FIG> shows a PUCCH (a long PUCCH or second uplink control channel) constituted of a larger number of symbols (duration, for example, <NUM> to <NUM> symbols) than that of the short PUCCH.

As shown in <FIG>, the short PUCCH may be mapped to a certain number of symbols (for example, one to two symbols) (PUCCH duration) from the end of a slot. Note that the symbols to which the short PUCCH is mapped are not limited to those at the end of the slot but may be the certain number of symbols at the start of or in the middle of the slot. The starting position of the short PUCCH in the time direction in the slot may be indicated by an index of a starting symbol.

In addition, the short PUCCH is mapped to one or more frequency resources (for example, one or more PRBs). Note that it is assumed in <FIG> that the short PUCCH is mapped to consecutive PRBs, but the short PUCCH may be mapped to nonconsecutive PRBs.

Alternatively, the short PUCCH may be time-division-multiplexed and/or frequency-division-multiplexed with an uplink data channel (hereinafter also referred to as a "PUSCH") in the slot. Furthermore, the short PUCCH may be time-division-multiplexed and/or frequency-division-multiplexed with a downlink data channel (hereinafter also referred to as a "PDSCH") and/or a downlink control channel (hereinafter also referred to as a "PDCCH (Physical Downlink Control Channel)") in the slot.

The short PUCCH may use a multi-carrier waveform (for example, an OFDM (Orthogonal Frequency Division Multiplexing) waveform) or may use a single-carrier waveform (for example, a DFT-s-OFDM (Discrete Fourier Transform-Spread-Orthogonal Frequency Division Multiplexing) waveform or an OFDM waveform using a CAZAC (Constant Amplitude Zero Auto Correlation) sequence (for example, a CGS (Computer Generated Sequence) or a Zhadoff-chu sequence)) as a reference sequence of a transmission signal.

The format of the short PUCCH may be, for example, PUCCH format (PF) <NUM> or <NUM>. The format of the short PUCCH may vary depending on the number of bits of the UCI (for example, whether the number of bits is up to <NUM> bits or more than <NUM> bits). For example, PUCCH format <NUM> may be used for the UCI of up to <NUM> bits, while PUCCH format <NUM> may be used for UCI of more than <NUM> bits (see <FIG>).

Meanwhile, as shown in <FIG>, the long PUCCH may be mapped over a larger number of symbols (for example, <NUM> to <NUM> symbols) (PUCCH duration) than that of the short PUCCH. In <FIG>, the long PUCCH is not mapped to a certain number of symbols at the starting of the slot but may be mapped to the certain number of symbols at the start. The starting position of the long PUCCH in the time direction in the slot may be indicated by an index of a starting symbol.

As illustrated in <FIG>, to obtain a power boosting effect, the long PUCCH may be constituted of a smaller number of frequency resources (for example, one or two PRBs) than that of the short PUCCH or may be constituted of an equal number of frequency resources to that of the short PUCCH.

The long PUCCH may be frequency-division-multiplexed with a PUSCH in the slot. The long PUCCH may be time-division-multiplexed with a PDCCH in the slot. The long PUCCH may be mapped to the same slot as that of the short PUCCH. In the long PUCCH, a single-carrier waveform (for example, a DFT-s-OFDM waveform) may be used, or a multi-carrier waveform (for example, an OFDM waveform) may be used.

The format of the long PUCCH may be, for example, PUCCH format (PF) <NUM>, <NUM> or <NUM>. The format of the long PUCCH may vary depending on the number of bits of the UCI (for example, whether the number of bits is up to <NUM> bits or more than <NUM> bits). For example, PUCCH format <NUM> may be used for UCI of up to <NUM> bits, while PUCCH format <NUM> or <NUM> may be used for UCI of more than <NUM> bits (see <FIG>).

Furthermore, the format of the long PUCCH may be controlled based on the number N of bits of the UCI. For example, PUCCH format <NUM> may be used for UCI of more than N bits (or N bits or more), while PUCCH format <NUM> may be used for UCI of up to N bits (or less than N bits) and more than <NUM> bits (see <FIG>).

Note that <FIG> is merely an example, and N may be N = <NUM> or may be N > <NUM>. Alternatively, in <FIG>, N of different values may be used for PUCCH format <NUM> and PUCCH format <NUM>. For example, N =<NUM> may be used for PUCCH format <NUM>, while N = <NUM> may be used for PUCCH format <NUM>.

Furthermore, the format of the long PUCCH may vary depending on whether or not to employ block-wise spreading before DFT (for example, block-wise spreading in a time domain using orthogonal cover code (OCC)). For example, PUCCH format <NUM> may be used in the case of not employing block-wise spreading before DFT, while PUCCH format <NUM> may be used in the case of employing block-wise spreading before DFT. Note that, in PUCH format <NUM> or/and <NUM>, block-wise spreading after DFT (for example, block-wise spreading in the time domain using OCC) may be employed.

Furthermore, as shown in <FIG>, frequency hopping in which a frequency resource hops at a certain timing in one slot (intra slot frequency hopping) may be employed on the long PUCCH. Although not shown, similar intra-slot frequency hopping may also be employed on the short PUCCH and/or PUSCH constituted of a plurality of symbols.

<FIG> are diagrams to show examples of intra-slot frequency hopping of a PUCCH (for example, a long PUCCH). Note that, although a long PUCCH is illustrated as an example of a PUCCH in <FIG>, the intra-slot frequency hopping can be similarly employed on other uplink channels/signals, such as a short PUCCH, a PUSCH, and an SRS.

As shown in <FIG>, in the above-described future radio communication system, an accessible bandwidth (access BW (bandwidth)) may be configured for each user terminal. Here, the access BW may be also referred to as a "carrier (component carrier (CC) or a system band)," or a "partial frequency band in the carrier (partial band)" or a "bandwidth part (BWP)"), and so on.

For example, in <FIG>, an access BW of user terminal #<NUM> is configured to be wider than an access BW of user terminal #<NUM>. The distance (offset) between frequency resources to which PUCCHs are mapped may be different (<FIG>) or may be the same (<FIG>) for user terminals #<NUM> and #<NUM> having different access BWs.

In addition, in the above-described future radio communication system, a study is underway to enable UCI transmission using a long PUCCH over a plurality of slots. <FIG> are diagrams to show examples of a long PUCCH over a plurality of slots. Note that, although a long PUCCH is illustrated in each of <FIG>, these examples are similarly applicable to other uplink channels/signals, such as a PUSCH and an SRS.

As shown in <FIG>, in the case of the long PUCCH over a plurality of slots, the slots may have the same duration (PUCCH duration) and/or starting symbol of the long PUCCH. Note that, although not illustrated, the slots may have different PUCCH durations and/or starting symbols.

As shown in <FIG>, intra-slot frequency hopping may be employed on the long PUCCH over a plurality of slots in each slot. Alternatively, as shown in <FIG>, for the long PUCCH over a plurality of slots, frequency hopping which causes frequency resources to which the long PUCCH is mapped to hop among the plurality of slots (inter-slot frequency hopping) may be employed.

Note that intra-slot frequency hopping (<FIG>) and inter-slot frequency hopping (<FIG>) are not simultaneously employed for the same user terminal in the long PUCCH over a plurality of slots.

As described above, in the future radio communication system (for example, LTE Rel. <NUM> or later versions, <NUM>, NR, and so on), it is assumed that the access BW may be different for each user terminal (for example, <FIG>). Hence, it is desired to flexibly control, for each user terminal, a pattern of intra-slot frequency hopping (for example, positions of frequency resources for hopping and/or hopping timings, and so on) of an uplink channel/signal (for example, at least one of the above-described long PUCCH, short PUCCH, PUSCH, SRS, and so on).

In view of this, the inventors of the present invention studied a method for flexibly controlling a pattern of intra-slot frequency hopping of an uplink channel/signal and reached the present invention.

Hereinafter, the present embodiment will be described in detail. In the following, a description will be given mainly of a PUCCH and/or a PUSCH (PUCCH/PUSCH) as an example of an uplink channel/signal. However, the present embodiment is also applicable to other uplink channels and/or uplink signals, such as an SRS. In addition, "PUCCH" is hereinafter used as a general term for a long PUCCH and/or a short PUCCH.

In a first aspect, a description will be given of determination of frequency resources to which a PUCCH/PUSCH is to be mapped, when intra-slot frequency hopping is employed on the PUCCH/PUSCH.

When intra-slot frequency hopping is employed on a PUCCH/PUSCH, a radio base station may report to a user terminal about information related to frequency resources to which the PUCCH/PUSCH is to be mapped (frequency resource information).

Here, the frequency resource information may include information indicating an index of a certain frequency resource (for example, a first-hop (starting) frequency resource) (for example, an index of a PRB and/or a resource element (RE) (PRB/RE)) and information related to other frequency resources (for example, second- and subsequent-hop frequent resources). The information related to the other frequency resources may be, for example, information indicating a certain frequency offset (frequency offset information) or information indicating indices of the other frequency resources.

<FIG> are diagrams to show examples of a frequency offset when intra-slot frequency hopping according to the first aspect is employed. In <FIG>, cases of employing intra-slot frequency hopping in a BWP configured for a user terminal are illustrated. However, the bandwidth for which the intra-slot frequency hopping is employed is not limited to the BWP as long as being an access BW of the user terminal. In <FIG>, hopping between two frequency resources is shown, but hopping may be among two or more frequency resources.

<FIG> shows cases in which a frequency resource of each of first and second hops is constituted of a certain number of resource units (for example, one or more PRBs or REs). In <FIG>, the user terminal is assumed to be reported about index #n (for example, the smallest index) of a certain resource unit (for example, PRB/RE) of the first-hop frequency resource.

For example, in <FIG>, the radio base station reports to the user terminal about frequency offset information indicating frequency offset k from index #n of the previous-hop (here, first-hop) frequency resource. In <FIG>, the user terminal may determine index #n+k (for example, the smallest PRB index or RE index) of the next-hop (here, second-hop) frequency resource, based on index #n of the previous-hop (here, first-hop) frequency resource and frequency offset k (k = integer).

In <FIG>, the radio base station reports to the user terminal about frequency offset information indicating frequency offset k from index #m of a frequency resource used as a reference (reference frequency resource). The user terminal may be reported about (configured with) the information indicating index #m through higher layer signaling. In <FIG>, the user terminal may determine index #m+k (for example, the smallest PRB index or RE index) of the second-hop frequency resource, based on index #m of the reference frequency resource and frequency offset k (k = integer).

In <FIG>, the radio base station reports to the user terminal about frequency offset information indicating frequency offset k of index #l (for example, a PRB or RE index) of an edge of the access BW (here, BWP) of the user terminal. Index #l may be an index (for example, a PRB index or RE index) of the opposite edge of the access BW from that of the first-hop frequency resource.

In <FIG>, the user terminal may determine index #l+k (for example, the smallest PRB index or RE index) of the second-hop frequency resource, based on index #l of the edge of the access BWP and frequency offset k (k = integer).

In the first aspect, when intra-slot frequency hopping is employed on the PUCCH/PUSCH, the radio base station reports to the user terminal about frequency resource information (for example, information indicating frequency offset k shown in any of <FIG>), whereby the user terminal can appropriately control the pattern of intra-slot frequency hopping, based on the frequency resource information.

In a second aspect, a detailed description will be given of signaling in the case of employing intra-slot frequency hopping on a PUCCH.

A user terminal is configured with (reported by a radio base station about) a plurality of sets (PUCCH resource sets, parameter sets) each including one or more parameters related to resources for the PUCCH (PUCCH resources) through higher layer signaling in advance. One of the plurality of PUCCH resource sets is specified by using a certain field in downlink control information (DCI). The user terminal controls transmission of the PUCCH, based on the PUCCH resource set indicated by a value of certain field in the DCI.

When intra-slot frequency hopping is employed on the PUCCH, each of the PUCCH resource sets configured through higher layer signaling may include frequency resource information described in the first aspect and the like.

<FIG> are diagrams to show an example of PUCCH resource sets according to the second aspect. As shown in <FIG>, values in the certain field in the DCI indicate respective PUCCH resource sets. For example, in <FIG>, values "<NUM>," "<NUM>," "<NUM>," and "<NUM>" of the certain field indicate PUCCH resource sets #<NUM>, #<NUM>, #<NUM>, and #<NUM>, respectively.

As illustrated in <FIG>, each of the PUCCH resource sets may include at least one of the following parameters.

Note that at least one of the parameters shown in <FIG> may be semi-statically configured through higher layer signaling instead of being dynamically specified as a PUCCH resource set.

Note that the user terminal (UE) may estimate a PUCCH format, based on reported PUCCH resource without being explicitly reported about the PUCCH format to the UE. For example, when the reported number of symbols of the PUCCH is smaller than four, the UE can estimate that the PUCCH format for a short PUCCH is reported. In <FIG>, each of the PUCCH resource sets may indicate a PUCCH resource of a single PUCCH format. Furthermore, different PUCCH formats may be used for respective PUCCH resource sets. Furthermore, at least one of the parameters in <FIG> may be specified for each PUCCH resource set and for each PUCCH format. For example, enabling frequency hopping or not for each of the PUCCH resource sets may be specified for each of PUCCH formats <NUM> to <NUM>.

Furthermore, each value of certain field in the DCI shown in <FIG> may indicate a PUCCH resource set of each PUCCH format. For example, the value "<NUM>" of certain field may indicate PUCCH resource set #<NUM> in PUCCH format <NUM> and PUCCH resource set #<NUM> in PUCCH format <NUM>. In this way, the same value of certain field may indicate the same and/or different PUCCH resource sets among the PUCCH formats.

According to the second aspect, when intra-slot frequency hopping is employed on the PUCCH, a PUCCH resource set including frequency resource information of the PUCCH (for example, information indicating frequency offset k shown in any of <FIG>) is specified for the user terminal, whereby the user terminal can appropriately control the pattern of intra-slot frequency hopping for the PUCCH, based on the frequency resource information.

In a third aspect, a description will be given of signaling in the case of employing intra-slot frequency hopping for a PUSCH.

DCI for scheduling a PUSCH in one or a plurality of slots may include information (time resource information) indicating symbols to be used for transmission of the PUSCH in each slot. The time resource information may be, for example, information indicating an index of the first symbol (starting symbol index) and/or the number (time length or duration) of the symbols to which the PUSCH is allocated in a slot (for example, an index associated with the starting symbol index and/or the number of symbols in a certain table).

Furthermore, one of the plurality of configurations of the PUSCH (PUSCH configurations) may be configured for a user terminal through higher layer signaling (for example, RRC signaling). The plurality of PUSCH configurations include a default PUSCH configuration (also referred to as configuration <NUM>, default configuration, and so on) to be used until a PUSCH configuration is configured through higher layer signaling.

Allocation of frequency resources for the PUSCH is carried out in a certain resource unit (for example, PRB or group including one or more PRBs (resource block group (RBG))). The size of each RBG (RBG size or the number of PRBs in each RBG) may be determined for each PUSCH configuration depending on the number of PRBs in the access BW (for example, the BWP) of the user terminal.

For example, when the access BW is constituted of X<NUM> to X<NUM> PRBs, RBG size <NUM> may be used for PUSCH configuration #<NUM> while RBG size may be used for PUSCH configuration #<NUM>. When the access BW is constituted of certain numbers of X<NUM>+<NUM> to X<NUM> PRBs, RBG size <NUM> may be used for PUSCH configuration #<NUM> while RBG size <NUM> may be used for PUSCH configuration #<NUM>.

Such an RBG size depending on the access BW for each PUSCH configuration may be defined in a table. In the table, the RBG size is determined for each level of the number of PRBs of the access BW. The number of levels of the number of PRBs is, for example, four to six, and four to six records may be included in the table. Note that the table may be common to the PUSCH and the PUCCH or may be unique to each of the PUSCH and the PUCCH. Alternatively, the RBG size may be fixed irrespective of the duration (the number of symbols) of the PUSCH.

When intra-slot frequency hopping is employed on the PUSCH thus configured, frequency resource information described in the first aspect may be specified by DCI. Furthermore, employing frequency hopping or not may be specified by the DCI.

Here, the DCI may be DCI (also referred to as common DCI, fallback DCI, and so on) mapped to a search space (common search space) common to one or more user terminals and/or DCI (also referred to as individual DCI, non fallback DCI, and so on) mapped to a user-terminal-specific search space.

The fallback DCI is DCI for which contents are not configured through user-terminal-specific higher layer signaling (for example, RRC signaling). The non fallback DCI is DCI for which contents can be configured through user-terminal-specific higher layer signaling (for example, RRC signaling). The non fallback DCI may be used for scheduling of the PUSCH and may be referred to as "UL grant" and so on.

<FIG> is a diagram to show an example of DCI according to the third aspect. As shown in <FIG>, DCI (fallback DCI and/or non fallback DCI) may indicate at least one kind of the following information.

Specifically, the kinds of information shown in <FIG> may be indicated in separate fields (also referred to as "parameters," "information elements (IEs)," and so on) in the DCI. Alternatively, at least two of these may be indicated in a single field (joint field) in the DCI.

For example, information (a) indicating enabling frequency hopping or not may be indicated in a single field in the DCI, and both information (b) related to the frequency resources for second and subsequent hops and information (c) of frequency resource allocation for the PUSCH may be indicated in another single field (for example, resource allocation field) in the DCI.

Alternatively, information (a) indicating enabling frequency hopping or not, information (b) related to the frequency resources for second and subsequent hops, and information (c) of frequency resource allocation for the PUSCH may all be indicated in a single field (for example, resource allocation field) in the DCI.

Furthermore, information (d) indicating which one of intra-slot frequency hopping and inter-slot frequency hopping is enabled for the PUSCH over a plurality of slots may be indicated in the same joint field for information related to time resource of the PUSCH (for example, information indicating a starting symbol and/or information indicating the number of symbols in the slot in <FIG>), or may be indicated in a different field in the DCI from a field for the information related to time resource.

<FIG> are diagrams to show examples of a joint field in DCI according to the third aspect. In <FIG>, information (a) indicating enabling frequency hopping or not, information (b) of the frequency resources for second and subsequent hops, and information (c) of frequency resource allocation for the PUSCH are indicated in an X-bit joint field (for example, resource allocation field) in the DCI.

For example, in <FIG>, ceil [log (Y RBs* (Y RBs + <NUM>))] bits indicate information (a) of frequency resource allocation for the PUSCH (for example, the number Y of PRBs), Z bits indicate information (b) of the frequency resources for second and subsequent hops, and information (c) of frequency resource allocation for the PUSCH.

The number X of bits of the joint field may be a fixed value, may be a value configured through higher layer signaling, or may be a value derived from the access BW (for example, UL BWP) of the user terminal. For example, in a case where X is fixed, X may be X = <NUM> when the DCI is fallback DCI, while X may be X = <NUM> when the DCI is non fallback DCI.

Furthermore, the number Z of bits indicating information (b) of the frequency resources for second and subsequent hops and information (c) of frequency resource allocation for the PUSCH may be a fixed value or may be a value derived from a bandwidth S of the access BW (for example, UL BWP) of the user terminal or the total bandwidth S of frequency hopping. For example, Z may be <NUM> bit (Z = <NUM> bit) when the bandwidth S of the access BW or the total bandwidth S of the frequency hopping is equal to or smaller than a certain threshold, while Z may be <NUM> bits (Z = <NUM> bits) when the total bandwidth S is greater than the certain threshold.

<FIG> shows information indicated by each bit value when Z = <NUM>. For example, a bit value "<NUM>" indicates not enabling frequency hopping, while a bit value "<NUM>" indicates a frequency offset "<NUM>/<NUM> * S" in the case of enabling frequency hopping.

<FIG> shows information indicated by each bit value when Z = <NUM>. For example, a bit value "<NUM>" indicates not enabling frequency hopping, while bit values "<NUM>," "<NUM>," "<NUM>" indicate frequency offsets "<NUM>/<NUM> * S," "+<NUM>/<NUM> * S," and "-<NUM>/<NUM> * S", respectively, in the case of enabling frequency hopping.

The user terminal may control intra-slot frequency hopping of the PUSCH, based on information (a) of frequency resource allocation for the PUSCH indicated by ceil [log (Y RBs* (Y RBs + <NUM>))] bits and the frequency offset indicated by the bit value of Z bits.

Note that the PUSCH for which the above intra-slot frequency hopping is enabled may communicate at least one of user data, higher layer control information, and message <NUM>. Message <NUM> is higher layer control information transmitted from a user terminal in response to a random access response (RAR or message <NUM>) from a radio base station in a random access procedure.

According to the third aspect, when intra-slot frequency hopping is employed on the PUSCH, DCI including frequency resource information of the PUSCH (for example, information indicating frequency offset k illustrated in any of <FIG>) is transmitted from the radio base station, whereby the user terminal can appropriately control the pattern of intra-slot frequency hopping for the PUSCH, based on the frequency resource information.

"Intra-slot frequency hopping" above is applicable not only to a PUCCH/PUSCH scheduled in a single slot but also to a PUCCH/PUSCH over a plurality of slots, in each of the slots.

Even when intra-slot frequency hopping is employed on a PUCCH/PUSCH over a plurality of slots, employing intra-slot frequency hopping in a slot may be controlled based on the number of symbols (for example, the number of UL symbols) available in the slot. For example, when the number of symbols available in a slot is smaller than a certain threshold X, employing the intra-slot frequency hopping in the slot may be set at off. Note that X may be <NUM> or <NUM>, for example.

Hereinafter, a structure of a radio communication system according to the present embodiment will be described. In this radio communication system, the radio communication methods according to the above-described aspects are employed. Note that the radio communication methods according to the above-described aspects may be employed independently or may be employed by combining at least two of the radio communication methods.

<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 LTE systems (for example, <NUM>) constitutes one unit. Note that the radio communication system <NUM> may be also referred to as "SUPER <NUM>," "LTE-A (LTE-Advanced)," "IMT-Advanced," "<NUM>," "<NUM>," "FRA (Future Radio Access)," "NR (New RAT: New Radio Access Technology)," and so on.

The radio communication system <NUM> shown in <FIG> is provided with 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. A configuration in which different numerologies are applied between cells and/or within a cell may be adopted.

Here, "numerology" refers to communication parameters in the frequency direction and/or the time direction (for example, at least one of the subcarrier spacing (subcarrier interval), the bandwidth, the symbol length, the time length of CPs (CP length), the subframe length, the time length of TTIs (TTI length), the number of symbols per TTI, the radio frame structure, the filtering process, the windowing process, and so on). The radio communication system <NUM> may support subcarrier spacings of <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and so on, for example.

The user terminals <NUM> can connect with both the radio base station <NUM> and the radio base stations <NUM>. The user terminals <NUM> may use the macro cell C1 and the small cells C2, which use different frequencies, at the same time by means of CA or DC. Also, the user terminals <NUM> can execute CA or DC by using a plurality of cells (CCs) (for example, two or more CCs). Furthermore, the user terminals can use licensed band CCs and unlicensed band CCs as a plurality of cells.

Furthermore, the user terminals <NUM> can perform communication using time division duplex (TDD) or frequency division duplex (FDD) in each cell. A TDD cell and an FDD cell may be referred to as a "TDD carrier (frame structure type <NUM>)" and an "FDD carrier (frame structure type <NUM>)," respectively, 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 using a carrier of a relatively low frequency band (for example, <NUM>) and a narrow bandwidth (referred to as 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 with the radio base station <NUM> may be used.

A structure may be employed in which wired connection (for example, an optical fiber in compliance with the CPRI (Common Public Radio Interface), an X2 interface, and so on) or wireless connection is established between the radio base station <NUM> and the radio base stations <NUM> (or between two radio base stations <NUM>).

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, 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 "transmitting/receiving point (TRP)," and so on. Also, 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," "transmitting/receiving 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.

The user terminals <NUM> are terminals to support various communication schemes such as LTE, LTE-A, <NUM>, NR, and so on, and may include not only mobile communication terminals but also stationary communication terminals. Furthermore, the user terminals <NUM> can perform device-to-device (D2D) communication with other user terminals <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 formed with 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 not limited to the combinations of these, and OFDMA may be used in UL.

Furthermore, in the radio communication system <NUM>, a multi-carrier waveform (for example, an OFDM waveform) may be used, or a single-carrier waveform (for example, a DFT-s-OFDM waveform) may be used.

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

The L1/L2 control channels include downlink control channels (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 is communicated in the PDCCH, for example. The number of OFDM symbols to use for the PDCCH is communicated in the PCFICH. The EPDCCH is frequency-division-multiplexed with the PDSCH and used to communicate DCI and so on, like the PDCCH. HARQ retransmission control information (ACK/NACK) in response to the PUSCH can be communicated in at least one of the PHICH, the PDCCH, and the EPDCCH.

In the radio communication system <NUM>, an uplink (UL) shared channel (PUSCH (Physical Uplink Shared Channel, also referred to as an "uplink data channel" and so on)), which is used by each user terminal <NUM> on a shared basis, an uplink control channel (PUCCH (Physical Uplink Control Channel)), a random access channel (PRACH (Physical Random Access Channel)), and so on are used as uplink (UL) channels. User data and higher layer control information are communicated in the PUSCH. Uplink control information (UCI) including at least one of downlink (DL) signal retransmission control information (A/N), channel state information (CSI), and so on, is communicated in 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> is provided with 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 a user terminal <NUM> on the downlink 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>.

The transmitting/receiving sections <NUM> can be constituted with transmitters/receivers, transmitting/receiving circuits, or pieces of 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 uplink (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>. The transmitting/receiving sections <NUM> convert the received signals into the baseband signal through frequency conversion and output to the baseband signal processing section <NUM>.

In the baseband signal processing section <NUM>, UL data that is included in the input UL signals 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 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. Also, 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).

Also, the transmitting/receiving sections <NUM> transmit downlink (DL) signals (including at least one of DL data signals, DL control signals, and DL reference signals) to the user terminals <NUM>, and receive uplink (UL) signals (including at least one of UL data signals, UL control signals, and UL reference signals) from the user terminals <NUM>.

In addition, the transmitting/receiving sections <NUM> receive UCI from the user terminals <NUM> on uplink data channels (for example, PUSCHs) or uplink control channels (for example, short PUCCHs and/or long PUCCHs). The transmitting/receiving sections <NUM> receive uplink data (user data and/or higher layer control information) from the user terminals <NUM> on uplink data channels (for example, PUSCHs).

Also, the transmitting/receiving sections <NUM> transmit control information (higher layer control information) through higher layer signaling and downlink control information (DCI) through physical layer signaling. Specifically, the transmitting/receiving sections <NUM> transmit frequency resource information (first aspect). For example, the transmitting/receiving sections <NUM> may transmit a plurality of parameter sets (PUCCH resource sets) each including the frequency resource information through higher layer signaling and transmit downlink control information indicating one of the plurality of parameter sets (second aspect). The transmitting/receiving sections <NUM> may transmit downlink control information including the frequency resource information (third aspect).

<FIG> is a diagram to show an example of a functional structure of a radio base station according to the present embodiment. Note that, although <FIG> primarily shows functional blocks that pertain to characteristic parts of the present embodiment, 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> is provided with 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> controls, for example, the generation of DL signals by the transmission signal generation section <NUM>, the mapping of DL signals by the mapping section <NUM>, the receiving processes (for example, demodulation) for UL signals by the received signal processing section <NUM>, and the measurements by the measurement section <NUM>.

To be more specific, the control section <NUM> performs scheduling for the user terminals <NUM>. Specifically, the control section <NUM> may perform scheduling and/or retransmission control of the downlink data channel and/or uplink data channel, based on UCI (for example, CSI and/or BI) from the user terminals <NUM>.

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

Also, the control section <NUM> may control intra-slot frequency hopping of an uplink control channel (for example, a long PUCCH and/or a short PUCCH) in one slot or over a plurality of slots. Specifically, the control section <NUM> may control generation and/or transmission of the frequency resource information.

Furthermore, the control section <NUM> may control intra-slot frequency hopping of an uplink data channel (for example, a PUSCH) in one slot or over a plurality of slots. Specifically, the control section <NUM> may control generation and/or transmission of the frequency resource information.

Also, the control section <NUM> may control generation and/or transmission of PUCCH resource sets.

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

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 DL data signals, DL control signals, and DL reference signals), based on commands from the control section <NUM> and outputs the DL signals to the mapping section <NUM>.

The transmission signal generation section <NUM> may be 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> may be 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 the receiving process (for example, demapping, demodulation, decoding, and so on) of UL signals (including, for example, UL data signals, UL control signals, and UL reference signals) that are transmitted from the user terminals <NUM>. Specifically, the received signal processing section <NUM> may output the received signals, the signals after the receiving process, and so on, to the measurement section <NUM>. Furthermore, the received signal processing section <NUM> performs the receiving process of UCI, based on the uplink control channel structures according to commands from 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> may measure the channel quality in UL, based on, for example, the received power (for example, RSRP (Reference Signal Received Power)) and/or the received quality (for example, RSRQ (Reference Signal Received Quality)) of UL reference signals. The measurement results may be output to the control section <NUM>.

<FIG> is a diagram to show an example of an overall structure of a user terminal according to the present embodiment. Each user terminal <NUM> is provided with 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 the amplifying sections <NUM>. The transmitting/receiving sections <NUM> receive 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 uplink (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 each transmitting/receiving section <NUM>. On UCI, at least one of channel coding, rate matching, puncturing, a DFT process, and an IFFT process is performed, and the result is transferred to each transmitting/receiving section <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>.

Furthermore, the transmitting/receiving sections <NUM> receive the downlink (DL) signals (including DL data signals, DL control signals, and DL reference signals) of the numerology configured in the user terminals <NUM>, and transmit the UL signals (including UL data signals, UL control signals, and UL reference signals) of the numerology.

In addition, the transmitting/receiving sections <NUM> transmit UCI to the radio base station <NUM> on uplink data channels (for example, PUSCHs) or uplink control channels (for example, short PUCCHs and/or long PUCCHs).

Furthermore, the transmitting/receiving sections <NUM> receive control information (higher layer control information) through higher layer signaling and downlink control information (DCI) through physical layer signaling. Specifically, the transmitting/receiving sections <NUM> receive frequency resource information (first aspect). Also, the transmitting/receiving sections <NUM> may receive a plurality of parameter sets (PUCCH resource sets) each including the frequency resource information, through higher layer signaling, and receive downlink control information indicating one of the plurality of parameter sets (second aspect). The transmitting/receiving sections <NUM> may receive downlink control information including the frequency resource information (third aspect).

The transmitting/receiving sections <NUM> may be transmitters/receivers, transmitting/receiving circuits, or pieces of transmitting/receiving apparatus that can be described based on general understanding of the technical field to which the present invention pertains. In addition, 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 a user terminal according to the present embodiment. Note that, although <FIG> primarily shows functional blocks that pertain to characteristic parts of the present embodiment, 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> included in the user terminal <NUM> is provided with 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, for example, 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>, the measurements in the measurement section <NUM>, and so on.

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

Furthermore, the control section <NUM> may control a structure (format) of an uplink control channel (for example, a long PUCCH and/or a short PUCCH). The control section <NUM> may control the uplink control channel format, based on the control information from the radio base station <NUM>.

Also, the control section <NUM> may control transmission of an uplink control channel (for example, a long PUCCH and/or a short PUCCH) in one slot or over a plurality of slots.

Specifically, the control section <NUM> may control frequency hopping of an uplink control channel in each slot, based on information related to frequency resources to which the uplink control channel is to be mapped (frequency resource information) (first aspect).

Also, in the case of receiving a plurality of parameter sets each including the frequency resource information through higher layer signaling, the control section <NUM> may control frequency hopping of an uplink control channel in each slot, based on one of the plurality of parameter sets specified by downlink control information (second aspect).

Here, the frequency resource information may include information indicating any of a frequency offset from the previous-hop frequency resource, a frequency offset from a frequency resource configured through higher layer signaling, and a frequency offset from an edge of a frequency band configured for the user terminal.

When an uplink control channel is transmitted over a plurality of slots, the control section <NUM> may control frequency hopping of the uplink control channel in each slot, based on information indicating which one of frequency hopping in each slot (intra-slot frequency hopping) and frequency hopping among the plurality of slots (inter-slot frequency hopping) is employed.

Furthermore, the control section <NUM> may control transmission of an uplink data channel (for example, a PUSCH) in one slot or over a plurality of slots.

Specifically, the control section <NUM> may control frequency hopping of an uplink data channel in each slot, based on information related to frequency resources to which the uplink data channel is to be mapped (frequency resource information) (first aspect).

Also, in the case of receiving downlink control information including information related to the frequency resources, the control section <NUM> may control frequency hopping of the uplink data channel in each slot, based on the downlink control information (third aspect).

When an uplink data channel is transmitted over a plurality of slots, the control section <NUM> may control frequency hopping of the uplink data channel in each slot, based on information indicating which one of frequency hopping in each slot (intra-slot frequency hopping) and frequency hopping among a plurality of slots (inter-slot frequency hopping) is employed.

Furthermore, the control section <NUM> may determine PUCCH resources to be used in a PUCCH format, based on higher layer signaling and/or downlink control information.

The control section <NUM> may control at least one of the transmission signal generation section <NUM>, the mapping section <NUM>, and the transmitting/receiving sections <NUM> to perform a transmission process of UCI, based on the PUCCH format.

The transmission signal generation section <NUM> generates (for example, through coding, rate matching, puncturing, modulation, and so on) UL signals (including UL data signals, UL control signals, UL reference signals, and UCI), based on commands from the control section <NUM> and outputs these signals to the mapping section <NUM>. The transmission signal generation section <NUM> may be 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 these to the transmitting/receiving sections <NUM>. The mapping section <NUM> may be 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 a receiving process (for example, demapping, demodulation, decoding, and so on) on DL signals (DL data signals, scheduling information, DL control signals, and DL reference signals). 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> outputs, for example, broadcast information, system information, higher layer control information through 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. Also, the received signal processing section <NUM> can constitute a receiving section according to the present invention.

The measurement section <NUM> measures channel states, based on reference signals (for example, CSI-RSs) from the radio base station <NUM>, and outputs the measurement results to the control section <NUM>. Note that the channel state measurements may be conducted per CC.

The measurement section <NUM> can be constituted with a signal processor, a signal processing circuit, or signal processing apparatus, and 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 a radio base station and a user terminal according to the present embodiment. 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 more of apparatuses shown in the drawings, or may be designed not to include part of apparatuses.

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 read and/or write 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/or the like for implementing a 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 wired and/or wireless networks, 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 used 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 replaced by "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 radio frame may be constituted of one or a plurality of periods (frames) in the time domain. A subframe may have a fixed time length (for example, <NUM>) independent of numerology.

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 assigned to these individual channels and information elements are in no respect limiting.

The information, signals, and/or others 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).

Software, whether referred to as "software," "firmware," "middleware," "microcode," or "hardware description language," or called by other names, should be interpreted broadly to mean instructions, instruction sets, code, code segments, program codes, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on.

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" as used herein 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," "receiving 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 mobile station may be also referred to as "transmission apparatus," "reception 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, (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, by higher layer signaling, at least one parameter set each including information related to a frequency resource to which an uplink control channel is to be mapped;
a control section (<NUM>) configured to control intra-slot frequency hopping of the uplink control channel in each slot, based on the information related to the frequency resource determined based on the at least one parameter set and a field in downlink control information indicating a parameter set of the at least one parameter set; and
a transmitting section (<NUM>) configured to transmit the uplink control channel,
wherein, when the uplink control channel is transmitted over a plurality of slots, the control section (<NUM>) is configured to control frequency hopping of the uplink control channel in each slot based on information indicating which is applied between intra-slot frequency hopping in each slot and inter-slot frequency hopping over the plurality of slots; and
wherein the receiving section (<NUM>) is further configured to receive the information indicating which is applied between intra-slot frequency hopping in each slot and inter-slot frequency hopping over the plurality of slots by the higher layer signalling.