Terminal, communication method, and system

Abstract

Provided is a terminal including: a control unit that determines the number of resource blocks used for a second uplink control channel at a value greater than one, the second uplink control channel being used before resources for a first uplink control channel are set for individual terminals; and a transmission unit that performs transmission via the second uplink control channel using the determined number of resource blocks.

Description

[Technical Field]

[0001] The present invention relates to a terminal and a base station in a wireless communication system. [Background technology]

[0002] For NR (New Radio) (also known as "5G"), the successor system to LTE (Long Term Evolution), technologies are being considered that meet the requirements of a large-capacity system, high data transmission speeds, low latency, simultaneous connection of many terminals, low cost, and power saving. Furthermore, for NR, the use of high frequency bands such as 52.6 to 71 GHz or 24.25 to 71 GHz is being considered.

[0003] In addition, in order to expand the frequency band, NR supports the use of frequency bands different from licensed bands (also called unlicensed bands, unlicensed carriers, or unlicensed CCs) licensed to telecommunications carriers (operators). In NR, systems that support unlicensed bands are called NR-U systems. [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] 3GPP TS 38.213 V16.6.0 (2021-06) [Non-patent document 2] 3GPP TS 38.211 V16.4.0 (2020-12) Summary of the Invention [Problem to be solved by the invention]

[0005] In NR, a physical uplink control channel (PUCCH) is used as a channel for transmitting uplink control information (see, for example, Non-Patent Documents 1 and 2). Note that the PUCCH is an example of an uplink control channel.

[0006] In existing technologies, PUCCH format 0 or 1 is used as the PUCCH format before configuring dedicated PUCCH resources. When transmitting PUCCH, it is desirable from the viewpoint of coverage, etc. to transmit with high transmission power within a range that does not exceed the maximum transmission power limited by regulations, etc.

[0007] However, in the existing technology, only one resource block (RB) is used as the number of PUCCH resources in the PUCCH format 0 or 1. With one RB, it is not possible to increase the transmission power.

[0008] The present invention has been made in consideration of the above points, and aims to provide a technique that enables a terminal to perform transmission on an uplink control channel using a number of RBs greater than one. [Means for solving the problem]

[0009] According to the disclosed technology, a control unit determines the number of resource blocks to be used in a second uplink control channel, which is used before a terminal-specific resource is configured for the first uplink control channel, to be a value greater than 1; a transmitter that performs transmission over the second uplink control channel using the number of resource blocks; A terminal comprising: [Effects of the Invention]

[0010] The disclosed technology provides a technology that enables a terminal to transmit on an uplink control channel using a number of RBs greater than one. [Brief explanation of the drawings]

[0011] [Figure 1] 1 is a diagram illustrating a wireless communication system according to an embodiment of the present invention. [Figure 2] 1 is a diagram illustrating a wireless communication system according to an embodiment of the present invention. [Figure 3] FIG. 10 is a diagram illustrating an example of a band. [Figure 4] FIG. 10 is a diagram showing maximum transmission power for each number of RBs. [Figure 5] FIG. 10 is a diagram illustrating an example of the RB size of a PUCCH. [Figure 6] FIG. 10 is a diagram illustrating an example of a PUCCH resource. [Figure 7] FIG. 10 is a diagram illustrating an example of a PUCCH resource. [Figure 8] FIG. 1 is a diagram for explaining an overview of an embodiment. [Figure 9] FIG. 1 is a diagram illustrating an example of a basic operation of the system. [Figure 10] FIG. 1 is a diagram for explaining a first embodiment. [Figure 11] FIG. 1 is a diagram for explaining a first embodiment. [Figure 12] FIG. 1 is a diagram for explaining a first embodiment. [Figure 13] FIG. 1 is a diagram for explaining a first embodiment. [Figure 14] FIG. 10 is a diagram for explaining a second embodiment. [Figure 15] FIG. 10 is a diagram for explaining a second embodiment. [Figure 16] FIG. 10 is a diagram for explaining a second embodiment. [Figure 17] FIG. 10 is a diagram for explaining a second embodiment. [Figure 18] FIG. 10 is a diagram for explaining a second embodiment. [Figure 19] FIG. 10 is a diagram for explaining a second embodiment. [Figure 20] FIG. 10 is a diagram for explaining a second embodiment. [Figure 21] FIG. 10 is a diagram for explaining a second embodiment. [Figure 22] FIG. 10 is a diagram for explaining a second embodiment. [Figure 23] FIG. 10 is a diagram for explaining a second embodiment. [Figure 24] FIG. 10 is a diagram for explaining a second embodiment. [Figure 25] FIG. 10 is a diagram for explaining a second embodiment. [Figure 26] FIG. 10 is a diagram for explaining a second embodiment. [Figure 27] FIG. 10 is a diagram for explaining a second embodiment. [Figure 28] FIG. 10 is a diagram for explaining a third embodiment. [Figure 29] FIG. 10 is a diagram for explaining a third embodiment. [Figure 30] FIG. 10 is a diagram for explaining a fourth embodiment. [Figure 31] FIG. 10 is a diagram for explaining a fourth embodiment. [Figure 32] 2 is a diagram illustrating an example of a functional configuration of a base station 10 according to an embodiment of the present invention. [Figure 33] FIG. 2 is a diagram illustrating an example of a functional configuration of a terminal 20 according to the embodiment of the present invention. [Figure 34] 2 is a diagram illustrating an example of a hardware configuration of a base station 10 or a terminal 20 according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0012] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. Note that the embodiment described below is an example, and the embodiment to which the present invention is applied is not limited to the following embodiment.

[0013] Existing technology is used as appropriate for the operation of the wireless communication system according to the embodiment of the present invention. The existing technology is, for example, the existing NR (e.g., Non-Patent Documents 1 and 2). The wireless communication system (base station 10 and terminal 20) according to the present embodiment basically operates in accordance with existing regulations. However, to solve the issues that arise when high frequency bands are used, the base station 10 and terminal 20 also perform operations that are not specified in the existing regulations. In the explanation of the embodiments described below, operations that are not specified in the existing regulations will be mainly explained. Note that all numerical values ​​described below are examples.

[0014] Furthermore, in the embodiments of the present invention, the duplex method may be a TDD (Time Division Duplex) method, an FDD (Frequency Division Duplex) method, or other methods (for example, Flexible Duplex, etc.).

[0015] Furthermore, in the embodiments of the present invention, "configuring" radio parameters and the like may mean that predetermined values ​​are pre-configured, or that radio parameters notified from the base station 10 or the terminal 20 are set. Note that the notation "A / B" used in the present embodiments means "A or B, or A and B."

[0016] (System Configuration)

[0017] Fig. 1 is a diagram illustrating a wireless communication system according to an embodiment of the present invention. As shown in Fig. 1, the wireless communication system according to the embodiment of the present invention includes a base station 10 and a terminal 20. Although Fig. 1 shows one base station 10 and one terminal 20, this is an example, and there may be a plurality of each.

[0018] The base station 10 is a communication device that provides one or more cells and performs wireless communication with the terminal 20. The physical resources of a wireless signal are defined in the time domain and the frequency domain.

[0019] OFDM is used as the radio access scheme. In the frequency domain, subcarrier spacing (SCS) of at least 15 kHz, 30 kHz, 120 kHz, and 240 kHz is supported. In this embodiment, larger SCSs are supported. Regardless of the SCS, a resource block is formed by a predetermined number (e.g., 12) of consecutive subcarriers.

[0020] When performing initial access, terminal 20 detects an SSB (SS / PBCH block) and identifies the SCS in the PDCCH and PDSCH based on the PBCH included in the SSB.

[0021] In the time domain, a slot is made up of multiple OFDM symbols (for example, 14 symbols regardless of the subcarrier spacing). Hereinafter, an OFDM symbol is called a "symbol." A slot is the scheduling unit. Subframes with a duration of 1 ms are defined, and a frame consisting of 10 subframes is defined. Note that the number of symbols per slot is not limited to 14.

[0022] As shown in Fig. 1, a base station 10 transmits control information or data to a terminal 20 in a DL (Downlink) and receives control information or data from the terminal 20 in an UL (Uplink). Both the base station 10 and the terminal 20 are capable of transmitting and receiving signals by performing beamforming. Furthermore, both the base station 10 and the terminal 20 are capable of applying MIMO (Multiple Input Multiple Output) communication to DL or UL. Furthermore, both the base station 10 and the terminal 20 may communicate via a SCell (Secondary Cell) and a PCell (Primary Cell) using CA (Carrier Aggregation).

[0023] The terminal 20 is a communication device equipped with a wireless communication function, such as a smartphone, a mobile phone, a tablet, a wearable terminal, an M2M (Machine-to-Machine) communication module, etc. As shown in Fig. 1, the terminal 20 receives control information or data from the base station 10 via DL and transmits control information or data to the base station 10 via UL, thereby utilizing various communication services provided by the wireless communication system.

[0024] Fig. 2 shows an example of the configuration of a wireless communication system when NR-DC (NR-Dual connectivity) is implemented. As shown in Fig. 2, a base station 10A serving as an MN (Master Node) and a base station 10B serving as an SN (Secondary Node) are provided. The base station 10A and the base station 10B are each connected to a core network. The terminal 20 communicates with both the base station 10A and the base station 10B.

[0025] A cell group provided by base station 10A, which is an MN, is called an MCG (Master Cell Group), and a cell group provided by base station 10B, which is an SN, is called an SCG (Secondary Cell Group). The operation in this embodiment may be performed in either the configuration shown in FIG. 1 or FIG. 2.

[0026] In the wireless communication system according to the present embodiment, when an unlicensed band is used, LBT (Listen Before Talk) is executed. The base station 10 or the terminal 20 transmits when the LBT result is idle, and does not transmit when the LBT result is busy.

[0027] (Regarding frequency bands) Figure 3 shows examples of frequency bands used in NR. NR has three frequency bands (which may also be called frequency ranges): FR1 (0.41 GHz to 7.125 GHz), FR2-1 (24.25 GHz to 52.6 GHz), and FR2-2 (52.6 GHz to 71 GHz). FR2-1 and FR2-2 may be collectively referred to as FR2. As shown in Figure 3, FR1 supports SCS of 15 kHz, 30 kHz, and 60 kHz, and a bandwidth (BW) of 5 to 100 MHz. FR2-1 supports SCS of 60 kHz, 120 kHz, and 240 kHz (SSB only), and a bandwidth (BW) of 50 to 400 MHz.

[0028] The wireless communication system according to this embodiment is assumed to use a frequency band of 52.6 GHz to 71 GHz. This frequency band may be an unlicensed band or a licensed band. Note that these are examples, and the technology according to the present invention is not limited to a specific band.

[0029] (Transmission power restrictions) For example, there are region-dependent regulations regarding transmission power for the unlicensed 60 GHz band in the high frequency band mentioned above. For example, the FCC regulations in the United States for the 52.6 GHz to 71 GHz band stipulate the EIRP (equivalent isotropically radiated power) and conducted power limits as follows:

[0030] Max avg, EIRP 40dBm Max peak EIRP 43dBm ·If emission-BW is less than 100 MHz, max peak conducted output power is {500mW × emission-BW / 100MHz} ·Otherwise, max peak conducted output power is 500mW Here, the relationship between the number of resource blocks (RBs) used for PUCCH transmission and transmission power when the emission bandwidth (BW) is less than 100 MHz is shown in Figure 4. As shown in Figure 4, it is possible to use a number of RBs greater than 1 so that the transmission power is equal to or less than the limited maximum transmission power.

[0031] (Number of RBs for PUCCH) The existing PUCCH formats 0 / 1 / 4 only support allocation of one PRB (Physical Resource Block), but the transmission bandwidth is not large enough to achieve the maximum transmission power under the regulations for the unlicensed band, for example, 60 GHz.

[0032] Therefore, in order to achieve the highest possible transmission power under the rules, it is conceivable to increase the number of RBs allocated to PUCCH formats 0 / 1 / 4. As an example, it is conceivable to allocate up to 12 RBs when the SCS is 120 kHz, up to 3 RBs when the SCS is 480 kHz, and up to 2 RBs when the SCS is 960 kHz.

[0033] For example, when the SCS is 120 kHz, it is conceivable that the number of RBs in each PUCCH format in Rel-15 / 16 shown in the upper part of FIG. 5 may be changed to the number of RBs shown in the lower part of FIG.

[0034] Here, the PUCCH resources before the dedicated PUCCH resource configuration in Rel-15 / 16 will be described (Non-Patent Document 1). The PUCCH resources before the dedicated PUCCH resource configuration are, for example, PUCCH resources that terminal 20 uses to transmit HARQ-ACK feedback of Msg.4 before RRC connection. Hereinafter, when a PUCCH resource is mentioned without any particular mention, the PUCCH resource in question is the PUCCH resource before the dedicated PUCCH resource configuration.

[0035] However, the techniques described in the following first to fourth embodiments may be applied to PUCCHs other than the PUCCH before dedicated PUCCH resource configuration.

[0036] The process in which terminal 20 determines the PUCCH resource to be used by itself in Rel-15 / 16 will be described.

[0037] Terminal 20 identifies one row of the cell-specific PUCCH resource set table shown in Figure 6(a) from the value of the 4-bit RMSI (specifically, for example, pucch-ResourceCommon) included in SIB1 received from base station 10, and identifies the PUCCH resource set defined in that row. As shown in Figure 6(a), here, a set of PUCCH format, first symbol, number of symbols, PRB offset, and first CS (cyclic shift) index is identified. Note that the PRB offset is the frequency width (expressed in terms of the number of RBs) from the end in the frequency direction of the BWP (bandwidth portion) used by terminal 20.

[0038] Furthermore, terminal 20 determines the PUCCH resource to use from the 3-bit value (PUCCH resource indicator field, PRI) in the DCI (specifically, DCI format 1_0 or 1_1) received from base station 10 on the PDCCH and the index (1 bit) of the first CCE in the PDCCH.

[0039] Specifically, for example, when the 4-bit RMSI (table index) is 1101, the PUCCH resource is determined according to the rule shown in FIG. 6(b).

[0040] Here, if terminal 20 receives 000 as the 3-bit value of DCI and the 1-bit value obtained from the CCE index is 0, the PUCCH resource is determined with the Hopping direction set to 0, the UE specific PRB offset set to 0, and the initial CS index set to 0. Note that the UE specific PRB offset is a UE-specific offset, and the value obtained by adding the UE-specific offset to the cell-specific offset becomes the offset used by terminal 20.

[0041] Figure 7 shows an example of PUCCH resource allocation (PUCCH resource set) when two users are multiplexed in the frequency direction and two users in the time direction, and there are four types of CS. The PRB offset is the offset from the edge of the BWP. User multiplexing in the frequency direction is performed using UE-specific PRB offsets in the frequency direction. Furthermore, frequency hopping allows frequencies that differ by half the number of allocated symbols to be used.

[0042] (Summary of the problem and embodiment) In existing technology (for example, Non-Patent Document 1), PUCCH format 0 or 1 (sometimes referred to as PF0 / 1) is used as the PUCCH resource before dedicated PUCCH resource configuration, and the number of allocated RBs is one.

[0043] However, as mentioned above, in terms of transmission power, in operation in the 52.6 to 71 GHz band, it is necessary that the PUCCH resources before the dedicated PUCCH resource configuration can use a number of RBs greater than 1. For example, it is possible to use 30 or more RBs for PUCCH transmission.

[0044] Therefore, in this embodiment, as illustrated in FIG. 8, X RBs, which is a number greater than 1, are allocated to one terminal 20 as PUCCH resources (specifically, frequency resources).

[0045] In the prior art, there is no proposal as to how to specifically allocate X RBs, which is greater than 1, as PUCCH resources.

[0046] Furthermore, when an attempt is made to increase the number of RBs in PUCCH resources, there is a problem that, under the existing PUCCH resource set specifications, there is a possibility that FDM resources (resources in the frequency direction) may become insufficient.

[0047] Hereinafter, a technique for enabling X RBs, which is greater than 1, to be used as PUCCH resources before dedicated PUCCH resource configuration will be described in detail.

[0048] (Basic operation example) An example of basic operation of the wireless communication system in this embodiment will be described with reference to Fig. 9. In S101, terminal 20 receives SIB1 transmitted from base station 10. SIB1 includes the above-mentioned 4-bit RMSI (an index specifying a row in the table). Note that inclusion of 4-bit RMSI in SIB1 is just one example, and 4-bit RMSI may also be included in information other than SIB1 (e.g., MIB, SSB, SIB other than SIB1).

[0049] Furthermore, terminal 20 (and base station 10) holds a table of cell-specific PUCCH resource sets. Based on the 4-bit value received in S101, terminal 20 identifies a PUCCH resource set (cell-specific PUCCH resource set) shown in one row of the table.

[0050] In S102, terminal 20 receives DCI on the PDCCH and identifies a UE-specific PUCCH resource based on a 3-bit value (PRI) and a 1-bit value obtained from the CCE index. In S103, terminal 20 transmits an uplink signal using the identified PUCCH resource.

[0051] Specific processing operations according to the present embodiment will be described below as Examples 1 to 4. In each Example, an example of multiple PRB allocation to PUCCH format 0 / 1 before dedicated PUCCH resource configuration will be described. The outline is as follows. Example 1 is a basic example, and it is assumed that Examples 2 to 4 are implemented based on Example 1. However, any of Examples 2 to 4 may be implemented independently without based on Example 1.

[0052] Example 1: Example of operation regarding setting the number of RBs Example 2: Frequency domain resource configuration - Cell-specific PRB offset value - UE specific PRB offset value - Frequency hopping Example 3: Time domain resource configuration Example 4: OCC The following describes Examples 1 to 4. The examples described in Examples 1 to 4 can be implemented in combination.

[0053] Example 1 In the first embodiment, an embodiment will be described regarding a method for configuring the number of RBs in a PUCCH resource before configuring a dedicated PUCCH resource. The first embodiment is made up of examples 1-1 to 1-4, each of which will be described.

[0054] <Example 1-1> In Example 1-1, a common value is defined in specifications, etc. as the number of RBs in the PUCCH resource before the dedicated PUCCH resource is configured. The terminal 20 uses the number of RBs according to the definition to transmit using the PUCCH in S103 of Fig. 9, and the base station 10 receives using the PUCCH.

[0055] As an example, for PF0 / 1 before the dedicated PUCCH resource is configured, when the SCS is 120 / 480 kHz, the number of RBs is defined as 12. More specifically, for example, the number of RBs is defined for each combination of PF and SCS, as shown in Fig. 10. When the definition shown in Fig. 10 is applied, for example, when PF1 is used and 120 kHz is used as the SCS, terminal 20 determines the number of RBs to be 12 and performs PUCCH transmission using 12 RBs.

[0056] <Example 1-2> In Example 1-2, a cell-specific number of RBs is defined in the PUCCH resource set table before configuring dedicated PUCCH resources. An example of the table in this case is shown in Figure 11. In the table shown in Figure 11, a column for the number of RBs is added compared to the table shown in Figure 6(a). In the example of Figure 11, the number of RBs is defined for each of the cases where the SCS is 120 kHz and 480 kHz. In other words, the number of RBs is defined for each SCS. However, this is just an example, and the number of RBs for SCSs other than 120 kHz and 480 kHz may be included, or a number of RBs common to multiple SCSs may be defined.

[0057] Terminal 20 located in a certain cell identifies a PUCCH resource set to be used in that cell based on a 4-bit value (index) received from base station 10 in S101 of Fig. 9. As shown in Fig. 11, the number of RBs is linked to the PUCCH resource set linked to the index and the SCS, so terminal 20 can identify the number of RBs to be used for PUCCH transmission corresponding to the SCS by identifying the PUCCH resource set.

[0058] <Examples 1-3> In Examples 1-3, the cell-specific number of RBs is notified from the base station 10 to the terminal 20 by SIB1. SIB1 is notified from the base station 10 to the terminal 20, for example, in S101 of Fig. 9. For example, the number of RBs that does not depend on the SCS or PUCCH resource set may be notified from the base station 10 to the terminal 20 by SIB1.

[0059] Furthermore, the relationship between the number of RBs and the PF / SCS may be signaled by SIB1. In this case, terminal 20 determines the number of RBs to use for PUCCH transmission from the above relationship based on the PF signaled by the 4-bit RMSI, or the SCS used in that cell, or both the PF signaled by the 4-bit RMSI and the SCS used in that cell.

[0060] As an example, it is assumed that the information shown in Fig. 10 is notified from the base station 10 to the terminal 20 as the relationship between the number of RBs and PF / SCS by SIB1. Also, assuming that the table shown in Fig. 6(a) is used, for example, if 0011 (PF=1) is notified as the 4-bit RMSI and the SCS is 120 kHz, the terminal 20 determines the number of RBs to be 12.

[0061] <Examples 1-4> In Example 1-4, for example, in S102 of Fig. 9, the number of RBs in the PUCCH resource before the dedicated PUCCH resource is configured is notified from the base station 10 to the terminal 20 as a UE-specific value. This notification may be notified by a 3-bit value (PRI) of the DCI, or may be notified by a 1-bit value derived from the CCE index, or may be notified by a combination of the 3-bit PRI value and the 1-bit value derived from the CCE index. Furthermore, the number of RBs may be specified for each SCS.

[0062] As an example, it is assumed that the table of PUCCH resource sets shown in Figure 6(a) is defined, and for one of the PUCCH resource sets, terminal 20 determines the number of RBs to use for PUCCH transmission by itself according to the rule shown in Figure 12. For example, if the SCS is 120 kHz or 480 kHz and terminal 20 receives 000 as a 3-bit PRI, terminal 20 determines from Figure 12 that the number of RBs is 5. Note that in the example of Figure 12, the number of RBs is determined independently of the value of one bit derived from the CCE index, but rules may be defined such that the number of RBs varies depending on the value of one bit derived from the CCE index. Also, in the example of Figure 12, the number of RBs is determined independently of the SCS, but rules may be defined such that the number of RBs varies depending on the SCS.

[0063] Furthermore, multiple values ​​for the number of RBs may be signaled or defined assuming multiple UE power classes. Terminal 20 determines the number of RBs corresponding to its own power class as the number of RBs to use for PUCCH transmission.

[0064] As an example, it is assumed that the relationship between the UE power class, SCS, and the number of RBs is notified from the base station 10 to the terminal 20, or that this relationship is specified, as shown in Fig. 13. If the power class of the terminal 20 is 1 and the SCS is 120 kHz, the terminal 20 determines the number of RBs to use for PUCCH transmission as 20, based on the relationship shown in Fig. 13.

[0065] <Combination of Examples 1-1 to 1-4> Examples 1-1 to 1-4 can be implemented in any combination. For example, the number of RBs X, which is a common value described in Example 1-1, may be defined, and a value in the range of 1 to X may be notified from base station 10 to terminal 20 as a cell-specific value for each cell, as in Example 1-2.

[0066] Furthermore, the cell-specific number of RBs Y described in Example 1-2 may be notified (or defined) to terminal 20, and terminal 20 may determine the value of the number of RBs to be used by itself from within the range of 1 to Y.

[0067] In Examples 1-1 to 1-4, if the number of RBs is not notified or specified, terminal 20 may assume that one RB is used for PUCCH transmission.

[0068] <Other examples> Depending on the number of RBs of the PUCCH resource, a "base sequence design, or time / frequency domain resource, or (base sequence design and time / frequency domain resource)" for the PUCCH resource before the dedicated PUCCH resource is configured may be specified, configured, or notified.

[0069] For example, in order to accommodate a larger number of RBs than the current FDM capacity (e.g., 20 RBs for an SCS of 120 kHz and a 100 MHz BW), the following may be applied. Details of the following will be explained in Examples 2 to 4 below.

[0070] ·FDM capacity adjustment No frequency hopping Increased TDM capacity ·Application of TD-OCC According to the first embodiment, the terminal 20 can perform transmission by PUCCH using a number of RBs greater than one.

[0071] Example 2 Next, a description will be given of a second embodiment, in which resource configuration in the frequency domain when a number of RBs greater than one can be used as PUCCH resources as described in the first embodiment will be described.

[0072] Specifically, at least a cell-specific PRB offset value or a UE-specific PRB offset value is determined according to the number of RBs for the PUCCH resource before the dedicated PUCCH resource configuration. The PRB offset value may be specified for each SCS / PF / UE power class, or may be notified from base station 10 to terminal 20 for each SCS / PF / UE power class. Below, examples of the cell-specific PRB offset value will be described in Examples 2-1-1 to 2-1-3, and examples of the UE-specific PRB offset value will be described as Examples 2-2-1 to 2-2-3. Also, an example related to frequency hopping will be described as Example 2-3.

[0073] <Example 2-1-1: Cell-specific PRB offset value> In Example 2-1-1, the cell-specific PRB offset value is defined in a cell-specific PUCCH resource set table. Fig. 14 shows an example of a cell-specific PUCCH resource set table including a column of cell-specific PRB offset values.

[0074] Based on the 4-bit RMSI received from the base station 10, the terminal 20 identifies the PUCCH resource set of the cell to which the terminal 20 belongs, and identifies the PRB offset value in the PUCCH resource set. For example, in the example of FIG. 14, if the 4-bit index is 1101, the terminal 20 determines the cell-specific PRB offset value as 10.

[0075] <Example 2-1-2: Cell-specific PRB offset value> In Example 2-1-2, for example, in S101 of Fig. 9, the cell-specific PRB offset value is notified from the base station 10 to the terminal 20 by SIB1. In this case, for example, the cell-specific PRB offset value is not specified in the PUCCH resource set table before the dedicated PUCCH resource is configured, and the cell-specific PRB offset value is notified independently from the base station 10 to the terminal 20 by SIB1.

[0076] <Example 2-1-3: Cell-specific PRB offset value> In Example 2-1-3, terminal 20 determines the cell-specific PRB offset value based on the number of RBs in the PUCCH resource and the cell-specific PRB offset index specified by the 4-bit RMSI.

[0077] The above-mentioned cell-specific PRB offset index may be defined for multiple RB allocation, or may be a cell-specific PRB offset value for one RB allocation (for example, the PRB offset in FIG. 6(a)).

[0078] The method by which terminal 20 determines the cell-specific PRB offset value based on the number of RBs in the PUCCH resource and the cell-specific PRB offset index is not limited to a specific method, but for example, the cell-specific PRB offset value is determined by multiplying the number of RBs in the PUCCH resource by the cell-specific PRB offset index.

[0079] In addition, if the number of RBs for PUCCH resources is not notified (i.e., if it is assumed that 1 RB will be used), the cell-specific PRB offset value specified in the PUCCH resource set table for 1 RB allocation (e.g., Figure 6(a)) may be used.

[0080] A more specific example of Example 2-1-3 will be described. Here, the cell-specific PUCCH resource set table shown in Fig. 15 is used. As shown in Fig. 15, this table has a column of PRB offset indexes.

[0081] In this case, for example, if the number of RBs in the PUCCH resource is 5 and the 4-bit RMSI is 1100, the cell-specific PRB offset index is 0 in the table, and therefore terminal 20 calculates the cell-specific PRB offset value as 0×5=0. The PUCCH resource set in this case is shown in the upper part of FIG.

[0082] Furthermore, for example, if the number of RBs in the PUCCH resource is 5 and the 4-bit RMSI is 1101, the cell-specific PRB offset index is 2 from the table, and therefore terminal 20 calculates the cell-specific PRB offset value as 2×5=10. The PUCCH resource set in this case is shown in the lower part of FIG.

[0083] <Examples common to Examples 2-1-1 to 2-1-3> In Example 2, multiple cell-specific PUCCH resource sets defined in a table may overlap in the frequency domain. An example of a table in which overlapping is permitted is shown in Fig. 17. Fig. 17 is a table assuming Example 2-1-1 as an example.

[0084] An example of a PUCCH resource set when two users can be multiplexed in the frequency direction is shown in Figure 18. The top of Figure 18 shows a PUCCH resource set when the index is 1100 (PRB offset = 0), the middle of Figure 18 shows a PUCCH resource set when the index is 1101 (PRB offset = 5), and the bottom of Figure 18 shows a PUCCH resource set when the index is 1110 (PRB offset = 10). As shown in Figure 18, an overlap of 5 RBs is allowed between PUCCH resource sets. Note that when time-frequency resources are shared between cells, the cyclic shifts of those resources may be different between cells.

[0085] For comparison, a table (FIG. 19) and an example of a PUCCH resource set (FIG. 20) based on existing regulations in which overlapping is not permitted are shown.

[0086] As shown in Figures 17 and 18, by allowing overlap of time-frequency resources in a PUCCH resource set, terminal 20 can transmit PUCCH over a larger bandwidth than when overlap is not allowed (Figures 19 and 20), i.e., when complete FDM multiplexing is performed between cells.

[0087] <Example 2-2-1: UE-specific PRB offset value> In Example 2-2-1, a UE-specific PRB offset value for multiple RB allocation is specified. Fig. 21 shows an example of the specified content (rules) including the UE-specific PRB offset value for multiple RB allocation. This differs from the existing specified content (e.g., Fig. 6(b)) in that the UE-specific PRB offset value includes "5" instead of "1".

[0088] The terminal 20 determines the UE-specific PRB offset value to be used by itself based on the 3-bit value of the DCI received from the base station 10 (or the 1-bit value derived from the 3-bit value of the DCI and the CCE index).

[0089] For example, if the value of the 3 bits is 010 in the example of FIG.

[0090] <Example 2-2-2: UE-specific PRB offset value> In Example 2-2-2, terminal 20 determines a UE-specific PRB offset value based on the number of RBs in the PUCCH resource and a UE-specific PRB offset index specified by a 3-bit value of DCI (or a 1-bit value derived from the 3-bit value of DCI and a CCE index).

[0091] The above-mentioned UE-specific PRB offset index may be defined for multiple RB allocation, or may be a UE-specific PRB offset value for one RB allocation (for example, the PRB offset in FIG. 6(b)).

[0092] The method by which terminal 20 determines the UE-specific PRB offset value based on the number of RBs in the PUCCH resource and the UE-specific PRB offset index is not limited to a specific method, but for example, the UE-specific PRB offset value is determined as the product of the number of RBs in the PUCCH resource and the UE-specific PRB offset index.

[0093] Note that when the number of RBs of the PUCCH resource is not notified (that is, when it is assumed that one RB is used), the UE-specific PRB offset value defined for one RB allocation can be used.

[0094] A more specific example of Example 2-2-2 will be described. Here, it is assumed that a PUCCH resource set with a cell-specific PRB offset value of 5 is used in a certain cell, and that a UE-specific PUCCH resource is determined from the PUCCH resource set based on the specifications shown in Fig. 22 .

[0095] In this case, for example, if the number of RBs in the PUCCH resource is 5 and the 3-bit value of the DCI is 000, the UE-specific PRB offset index is 0 from Figure 22, and therefore terminal 20 calculates the UE-specific PRB offset value as 0 x 5 = 0. The PUCCH resource in this case is shown in the upper part of Figure 23.

[0096] Furthermore, for example, if the number of RBs in the PUCCH resource is 5 and the 3-bit value of the DCI is 010, the UE-specific PRB offset index is 1 from Figure 22, and therefore terminal 20 calculates the UE-specific PRB offset value as 1 x 5 = 5. The PUCCH resource in this case is shown in the lower part of Figure 23.

[0097] <Common to Examples 2-2-1 to 2-2-2: UE-specific PRB offset value> The number of users (terminals) to be frequency-division multiplexed (FDM) in UE-specific PUCCH resources may be configurable for each cell.

[0098] An example in which the number of RBs in the cell-specific PUCCH resource is 12 is shown in Fig. 24. As shown in Fig. 24, in a cell in area A, three users can be frequency-multiplexed, in a cell in area B, multiple users cannot be frequency-multiplexed, and in a cell in area C, two users can be frequency-multiplexed.

[0099] In the example shown in Fig. 24, in region A, 4 RBs are required to achieve the maximum allowable transmission power, so 3 users are frequency-multiplexed in the same time domain resource. In region B, 12 RBs are required to achieve the maximum allowable transmission power, so frequency-multiplexing in the same time domain resource is not supported. In region C, 6 RBs are required to achieve the maximum allowable transmission power, so 2 users are frequency-multiplexed in the same time domain resource.

[0100] Since the number of RBs required to achieve the maximum allowable transmission power may differ from region to region, an appropriate number of users can be multiplexed by making it possible to set the number of users who can be frequency multiplexed for each cell as described above.

[0101] <Example 2-3-1: Frequency hopping> In Example 2-3-1, frequency hopping may not be applied to the PUCCH resource. As an example, frequency hopping may be enabled / disabled and configured in each cell.

[0102] Figure 25 shows an example of a PUCCH resource set when frequency hopping is disabled. The example in Figure 25 shows an example in which the left end (e.g., low frequency side) of the UL BWP is set to the position where PRB offset = 0, and the frequency position of the PUCCH resource set is shifted to the right by the frequency width of the PRB offset. Figure 25 is just one example, and for example, the right end (e.g., high frequency side) of the UL BWP may be set to the position where PRB offset = 0, and the frequency position of the PUCCH resource set may be shifted to the left by the frequency width of the PRB offset.

[0103] As a method for notifying whether the setting is valid or invalid, for example, Alt.1 or Alt.2 below can be applied.

[0104] Alt.1) The base station 10 notifies the terminal 20 of the above valid / invalid status by SIB1.

[0105] Alt.2) The above enable / disable is implicitly notified to terminal 20. For example, if the number of RBs of the PUCCH resource is greater than X (X is a natural number), frequency hopping is disabled, and if the number of RBs of the PUCCH resource is not greater than X, frequency hopping is enabled. The value of X may be specified as a higher layer parameter, or may be set from base station 10 to terminal 20.

[0106] In Example 2-3-1, if frequency hopping is not performed, no frequency hopping gain can be obtained, but the terminal 20 can perform PUCCH transmission in a larger bandwidth.

[0107] <Example 2-3-2: Frequency hopping> In Example 2-3-2, depending on whether frequency hopping is enabled or disabled, a cell-specific PRB offset value / UE-specific PRB offset value is defined or is notified from the base station 10 to the terminal 20. Specific examples will be described as Alt. 1 and Alt. 2 below.

[0108] Alt.1) In Alt.1, a PRB offset value is defined (or notified from base station 10 to terminal 20) for each of whether frequency hopping is enabled and disabled. The PRB offset value may be defined or notified for each SCS / PF / UE power class.

[0109] Figure 26 shows an example of a cell-specific PUCCH resource set table in Alt. 1. As shown in Figure 26, PRB offsets are defined for both the cases where frequency hopping is ON and where it is OFF. For example, if 0010 is reported by the 4-bit RMSI and frequency hopping is ON, terminal 20 identifies the PUCCH resource using the PUCCH resource set with PRB offset = 3 in 4-bit RMSI = 0010.

[0110] Alt.2) In Alt.2, if frequency hopping is disabled, the PRB offset value is determined from the number of RBs in the PUCCH resource and the cell-specific PRB offset index specified by the 4-bit RMSI. For example, the PRB offset value is calculated as the product of the number of RBs in the PUCCH resource and the cell-specific PRB offset index.

[0111] An example of a cell-specific PUCCH resource set table in Alt.2 is shown in Figure 27. In this example, if the number of RBs is 5 and the 4-bit RMSI is 1101 (cell-specific PRB offset index = 2), the cell-specific PRB offset value is calculated as 2 × 5 = 10.

[0112] In Example 2-3-2 as well, if frequency hopping is not performed, no frequency hopping gain can be obtained, but terminal 20 can transmit PUCCH over a larger bandwidth.

[0113] Example 3 Next, a third embodiment will be described. In the third embodiment, a cell-specific PUCCH resource set can be configured to time-division multiplex (TDM) more than two users (terminals). The number of users to be time-multiplexed in the cell-specific PUCCH resource set may be configurable for each cell.

[0114] Specifically, in a certain cell, a UE-specific symbol offset value is notified from base station 10 to terminal 20 using a 3-bit value of DCI (or a 1-bit value derived from the 3-bit value of DCI and a CCE index), and terminal 20 determines the time position of the PUCCH resource according to the UE-specific symbol offset value.

[0115] Examples are shown in Figures 28 and 29. Figure 28 shows the specified contents of UE-specific PUCCH resources in a certain cell. For example, if terminal 20 receives 000 as the 3-bit value of DCI, terminal 20 determines the UE-specific symbol offset index to be 0 based on the relationship shown in Figure 28. For example, terminal 20 performs PUCCH transmission using the PUCCH resource at the time position indicated by Index #0 in Figure 29.

[0116] The relationship between the UE-specific symbol offset index and the time domain resource of the PUCCH may be specified as a higher layer parameter, or may be set by the base station 10 to the terminal 20. Furthermore, the UE-specific symbol offset index may be individually notified from the base station 10 to the terminal 20.

[0117] Even if the FDM capacity is reduced due to multiple RB allocation, the multiplexing capacity can be increased by increasing the number of time-multiplexed users as in the third embodiment.

[0118] Example 4 In the fourth embodiment, terminal 20 applies TD-OCC (Time Domain - Orthogonal Cover Code) to the PUCCH resource before the dedicated PUCCH resource is configured. This allows user (terminal) multiplexing by code. Note that, although TD-OCC is used here, this is not limitative. For example, FD-OCC (Frequency Domain - Orthogonal Cover Code) may also be used.

[0119] As an orthogonal sequence in TD-OCC, for example, an orthogonal sequence for PUCCH format 1 disclosed in Non-Patent Document 2 can be used. This is shown in Fig. 30. In the example of Fig. 30, the orthogonal sequence to be used is determined according to the index of the orthogonal sequence (and the PUCCH length, etc.). However, this is just an example, and the orthogonal sequence used in the fourth embodiment is not limited to the orthogonal sequence for PUCCH format 1.

[0120] Even if the FDM capacity is reduced due to multiple RB allocation, by applying OCC as in the fourth embodiment, user (terminal) multiplexing can be performed, and therefore the multiplexing capacity can be increased.

[0121] In relation to the method of notifying the index (OCC index), examples 4-1 to 4-3 will be described below.

[0122] <Example 4-1> In Example 4-1, a cell-specific OCC index is defined, or is notified (instructed) from the base station 10 to the terminal 20. Specifically, there are Examples 4-1-1 and 4-1-2 below.

[0123] Example 4-1-1) In Example 4-1-1, a cell-specific OCC index is defined in a PUCCH resource set table for multiple RB allocation, and terminal 20 uses an OCC index defined in a PUCCH resource set corresponding to a 4-bit RMSI received from base station 10. That is, for example, a column of OCC indexes is included in the PUCCH resource set table for multiple RB allocation.

[0124] Example 4-1-2) In Example 4-1-2, the cell-specific OCC index is notified by SIB1 from the base station 10 to the terminal 20. In this case, the cell-specific OCC index is not specified in the PUCCH resource set table, and the cell-specific OCC index is notified independently by SIB1.

[0125] <Example 4-2> In Example 4-2, a UE-specific OCC index is notified from the base station 10 to the terminal 20. Specifically, for example, a UE-specific OCC index is defined for multiple RB allocation. This definition includes the relationship between a 3-bit value of DCI (or a 1-bit value derived from the 3-bit value of DCI and a CCE index) and the UE-specific OCC index.

[0126] The terminal 20 identifies the UE-specific OCC index to be used by itself based on the 3-bit value of the DCI received from the base station 10 (or the 1-bit value derived from the 3-bit value of the DCI and the CCE index).

[0127] <Example 4-3> In Example 4-3, the base station 10 notifies the terminal 20 of a set of cell-specific OCC indexes and a UE-specific OCC index (any one of the set).

[0128] Specifically, for example, a cell-specific PUCCH resource set table shown in Figure 31(a) is defined. As shown in Figure 31(a), a set of OCC indices is defined for each cell-specific PUCCH resource set. Terminal 20 determines a specific PUCCH resource set and ascertains the set of OCC indices based on the 4-bit RMSI received from base station 10. In the example of Figure 31, if the 4-bit RMSI = 1101, the set of OCC indices is {2, 3}.

[0129] Here, assuming that the UE-specific PUCCH resources are specified as shown in Figure 31(b), terminal 20 identifies the UE-specific OCC index to be used by itself from {2,3} based on the 3-bit value of DCI (or a 1-bit value derived from the 3-bit value of DCI and the CCE index) received from base station 10. For example, if the 3-bit value of DCI = 000, the OCC index is determined to be 2.

[0130] In the fourth embodiment, a default OCC index (for example, OCC index 0) may be defined, and if no OCC index is not notified, the terminal 20 may use the default OCC index.

[0131] (Example common to Examples 1 to 4) The examples described in the first to fourth embodiments may be applied only to operations in the 52.6 to 71 GHz band (e.g., FR2-2). The examples described in the first to fourth embodiments may be applied only to operations in the 60 GHz unlicensed band.

[0132] (Variation) In any of the first to fourth embodiments, the following operations may be performed.

[0133] The operation of the embodiment may be executed only when the terminal 10 notifies the base station 20 of capability information indicating that the terminal 20 supports the function of the embodiment.

[0134] In the operations using SIB1 in the first to fourth embodiments, other signals (for example, MIB, SSB, SIB other than SIB1) may be used instead of SIB1.

[0135] The bit numbers such as 4 bits and 3 bits described in the first to fourth embodiments are merely examples. The 4-bit RMSI may be replaced with information of any number of bits from 1 to 16 bits, for example. The 3-bit DCI may be replaced with information of any number of bits from 1 to 16 bits, for example.

[0136] Furthermore, the techniques described in the first to fourth embodiments may be applied to PUCCHs other than the PUCCH before the dedicated PUCCH resource configuration.

[0137] (Device configuration) Next, an example of the functional configuration of the base station 10 and the terminal 20 that execute the processes and operations described above will be described.

[0138] <Base station 10> Fig. 32 is a diagram showing an example of the functional configuration of the base station 10. As shown in Fig. 32, the base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Fig. 32 is merely an example. The names of the functional divisions and functional units may be any as long as they can execute the operations related to the embodiment of the present invention. Furthermore, the transmitting unit 110 and the receiving unit 120 may be collectively referred to as a communication unit.

[0139] The transmitter 110 has a function of generating a signal to be transmitted to the terminal 20 and transmitting the signal wirelessly. The receiver 120 has a function of receiving various signals transmitted from the terminal 20 and acquiring, for example, information of a higher layer from the received signals. The transmitter 110 also has a function of transmitting, to the terminal 20, an NR-PSS, an NR-SSS, an NR-PBCH, a DL / UL control signal, DCI via a PDCCH, data via a PDSCH, and the like.

[0140] The setting unit 130 stores preset setting information and various setting information to be transmitted to the terminal 20 in a storage device provided in the setting unit 130, and reads out the information from the storage device as needed.

[0141] The control unit 140 schedules DL reception or UL transmission of the terminal 20 via the transmission unit 110. The control unit 140 also includes a function for performing LBT. The functional unit related to signal transmission in the control unit 140 may be included in the transmission unit 110, and the functional unit related to signal reception in the control unit 140 may be included in the reception unit 120. The transmission unit 110 may also be called a transmitter, and the reception unit 120 may also be called a receiver.

[0142] <Terminal 20> Fig. 33 is a diagram showing an example of the functional configuration of the terminal 20. As shown in Fig. 33, the terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Fig. 33 is merely an example. The names of the functional divisions and functional units may be any as long as they can execute the operations related to the embodiment of the present invention. The transmitting unit 210 and the receiving unit 220 may be collectively referred to as a communication unit.

[0143] The transmitter 210 creates a transmission signal from transmission data and transmits the transmission signal wirelessly. The receiver 220 wirelessly receives various signals and acquires a higher layer signal from the received physical layer signal. The receiver 220 also has a function of receiving NR-PSS, NR-SSS, NR-PBCH, DL / UL / SL control signals, DCI via PDCCH, data via PDSCH, and the like transmitted from the base station 10. For example, the transmitter 210 may transmit a PSCCH (Physical Sidelink Control Channel), a PSSCH (Physical Sidelink Shared Channel), a PSDCH (Physical Sidelink Discovery Channel), a PSBCH (Physical Sidelink Broadcast Channel), and the like to another terminal 20 as D2D communication, and the receiver 120 may receive the PSCCH, PSSCH, PSDCH, PSBCH, and the like from the other terminal 20.

[0144] The setting unit 230 stores various pieces of setting information received from the base station 10 or other terminals by the receiving unit 220 in a storage device provided in the setting unit 230, and reads the information from the storage device as needed. The setting unit 230 also stores setting information that is set in advance.

[0145] The control unit 240 controls the terminal 20. The functional unit in the control unit 240 related to signal transmission may be included in the transmission unit 210, and the functional unit in the control unit 240 related to signal reception may be included in the reception unit 220. Furthermore, the transmission unit 210 may be called a transmitter, and the reception unit 220 may be called a receiver.

[0146] <Summary> This embodiment provides at least the terminals and base stations shown in the following items 1 to 6. (Section 1) a control unit that determines the number of resource blocks to be used in a second uplink control channel that is used before the terminal-specific resources are configured for the first uplink control channel to be a value greater than 1; a transmitter that performs transmission over the second uplink control channel using the number of resource blocks; A terminal comprising: (Section 2) a receiving unit that receives information indicating the number of resource blocks from a base station as cell-specific information, or receives information indicating the number of resource blocks from a base station as terminal-specific information; The control unit determines the number of resource blocks based on information received from the base station. 1. The terminal described in paragraph 1. (Section 3) The control unit determines a frequency position of the frequency resource by using an offset according to a size of the frequency resource in the second uplink control channel. 2. A terminal according to claim 1 or 2. (Section 4) The resource of the second uplink control channel in a certain cell is a resource that is allowed to overlap with the resource of the second uplink control channel in another cell. A terminal according to any one of paragraphs 1 to 3. (Section 5) The frequency resource of the second uplink control channel used by the terminal is used as the frequency resource of the second uplink control channel in two or more other terminals by time division multiplexing. A terminal according to any one of paragraphs 1 to 4. (Section 6) a transmitter that transmits, to a terminal, information indicating the number of resource blocks to be used in a second uplink control channel that is used before a terminal-specific resource is set for the first uplink control channel as cell-specific information, or transmits, to the terminal, the information indicating the number of resource blocks as terminal-specific information; a receiving unit for receiving a signal transmitted through the second uplink control channel using the number of resource blocks; A base station comprising:

[0147] Any of terms 1 to 6 enables a terminal to transmit on an uplink control channel using a number of RBs greater than one. In particular, term 2 allows the number of resource blocks to be determined based on information received from the base station, making it possible to use a number of resource blocks appropriate to the status of the cell or terminal. Term 3 uses an offset according to the size of the frequency resource, making it possible to use resources at appropriate frequency positions in the bandwidth portion.

[0148] Furthermore, the fourth term allows resource overlap, allowing a larger number of resource blocks to be used, and the fifth term allows time division multiplexing to accommodate multiple users, allowing a larger number of resource blocks to be used per user.

[0149] (Hardware configuration) The block diagrams (FIGS. 32 and 33) used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are connected directly or indirectly (for example, by wire, wirelessly, etc.) and these multiple devices. The functional block may be realized by combining the single device or the multiple devices with software.

[0150] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocation, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how these functions are implemented.

[0151] For example, the base station 10, the terminal 20, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 34 is a diagram illustrating an example of the hardware configuration of the base station 10 and the terminal 20 according to an embodiment of the present disclosure. The base station 10 and the terminal 20 described above may be physically configured as a computer device including a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0152] In the following description, the term "apparatus" can be read as a circuit, a device, a unit, etc. The hardware configuration of the base station 10 and the terminal 20 may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.

[0153] Each function in the base station 10 and the terminal 20 is realized by loading predetermined software (programs) onto hardware such as the processor 1001, the memory device 1002, etc., so that the processor 1001 performs calculations, controls communication by the communication device 1004, and controls at least one of reading and writing data in the memory device 1002 and the auxiliary memory device 1003.

[0154] The processor 1001 controls the entire computer by running, for example, an operating system. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, the above-mentioned control unit 140, control unit 240, etc. may be realized by the processor 1001.

[0155] Furthermore, the processor 1001 reads programs (program codes), software modules, data, etc. from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002, and executes various processes in accordance with the programs. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 140 of the base station 10 shown in FIG. 32 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. Furthermore, for example, the control unit 240 of the terminal 20 shown in FIG. 33 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. While the above-described various processes have been described as being executed by one processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may be transmitted from a network via a telecommunications line.

[0156] The storage device 1002 is a computer-readable recording medium and may be configured, for example, by at least one of a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a random access memory (RAM), etc. The storage device 1002 may also be called a register, a cache, a main memory, etc. The storage device 1002 can store executable programs (program codes), software modules, etc. for implementing a communication method according to an embodiment of the present disclosure.

[0157] The secondary storage device 1003 is a computer-readable recording medium, and may be, for example, at least one of an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray disc), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy disk, a magnetic strip, etc. The above-mentioned storage medium may be, for example, a database, a server, or other suitable medium including at least one of the storage device 1002 and the secondary storage device 1003.

[0158] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, or a communication module. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, a transmission / reception antenna, an amplifier unit, a transmission / reception unit, a transmission path interface, etc. may be realized by the communication device 1004. The transmission / reception unit may be implemented as a transmission unit and a reception unit that are physically or logically separated.

[0159] The input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (for example, a display, a speaker, an LED lamp, etc.) that performs output to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (for example, a touch panel).

[0160] Furthermore, each device such as the processor 1001 and the storage device 1002 is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.

[0161] Furthermore, base station 10 and terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized by the hardware. For example, processor 1001 may be implemented using at least one of these pieces of hardware.

[0162] (Supplementary explanation of the embodiment) Although the embodiments of the present invention have been described above, the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, and substitutions. While specific numerical examples have been used to facilitate understanding of the invention, unless otherwise specified, these numerical values ​​are merely examples, and any appropriate values ​​may be used. The division of items in the above description is not essential to the present invention; two or more items may be combined as needed, and items described in one item may apply to items described in another item (unless inconsistent). The boundaries between functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries between physical components. The operations of multiple functional units may be performed by a single physical component, or the operations of a single functional unit may be performed by multiple physical components. The order of the processing steps described in the embodiments may be reversed as long as there is no contradiction. For convenience of processing description, the base station 10 and terminal 20 have been described using functional block diagrams. However, such devices may be implemented using hardware, software, or a combination thereof. The software operated by the processor of the base station 10 in accordance with an embodiment of the present invention and the software operated by the processor of the terminal 20 in accordance with an embodiment of the present invention may each be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, registers, hard disk (HDD), removable disk, CD-ROM, database, server or any other suitable storage medium.

[0163] Furthermore, the notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB)), other signals, or a combination thereof. Furthermore, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

[0164] Each aspect / embodiment described in the present disclosure may be applied to at least one of systems using LTE (Long Term Evolution), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), FRA (Future Radio Access), NR (New Radio), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark), IEEE 802.20, UWB (Ultra-Wideband), Bluetooth (registered trademark), or other appropriate systems, and next-generation systems extended based on these. Furthermore, a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A with 5G, etc.) may also be applied.

[0165] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described herein may be changed unless it is consistent. For example, the methods described in this disclosure present elements of various steps using an example order and are not limited to the particular order presented.

[0166] In this specification, a specific operation that is described as being performed by the base station 10 may also be performed by its upper node in some cases. In a network consisting of one or more network nodes having the base station 10, it is clear that various operations performed for communication with the terminal 20 may be performed by at least one of the base station 10 and another network node other than the base station 10 (such as, but not limited to, an MME or an S-GW). Although the above example illustrates a case where there is one other network node other than the base station 10, the other network node may be a combination of multiple other network nodes (such as an MME and an S-GW).

[0167] The information or signals described in the present disclosure may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), or may be input / output via multiple network nodes.

[0168] Input and output information may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information may be overwritten, updated, or added to. Output information may be deleted. Input information may be sent to another device.

[0169] In the present disclosure, the determination may be made based on a value represented by one bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., comparison with a predetermined value).

[0170] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0171] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.

[0172] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0173] Note that terms explained in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.

[0174] As used in this disclosure, the terms "system" and "network" are used interchangeably.

[0175] Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, relative values ​​from a predetermined value, or other corresponding information. For example, a radio resource may be indicated by an index.

[0176] The names used for the above-described parameters are not intended to be limiting in any way. Furthermore, the mathematical expressions using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.

[0177] In this disclosure, terms such as "base station (BS)," "radio base station," "base station," "fixed station," "NodeB," "eNodeB (eNB)," "gNodeB (gNB)," "access point," "transmission point," "reception point," "transmission / reception point," "cell," "sector," "cell group," "carrier," and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0178] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be divided into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., a small indoor base station (RRH: Remote Radio Head)). The term "cell" or "sector" refers to a part or the entire coverage area of ​​a base station and / or base station subsystem that provides communication service within this coverage.

[0179] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. may be used interchangeably.

[0180] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

[0181] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile body, or the mobile body itself. The mobile body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may also include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

[0182] Furthermore, a base station in the present disclosure may be read as a terminal. For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a terminal is replaced with communication between a plurality of terminals 20 (which may be called, for example, D2D (Device-to-Device) or V2X (Vehicle-to-Everything)). In this case, the terminal 20 may be configured to have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to communication between terminals (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel.

[0183] Similarly, the term "terminal" in the present disclosure may be read as "base station." In this case, the base station may be configured to have the functions of the terminal described above.

[0184] As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and the like. Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.

[0185] The terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection 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. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using one or more wires, cables, and / or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

[0186] The reference signal may be abbreviated as RS (Reference Signal) or may be called a pilot depending on the applicable standard.

[0187] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0188] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.

[0189] The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc.

[0190] When used in this disclosure, the terms "include," "including," and variations thereof are intended to be inclusive, similar to the term "comprising." Furthermore, when used in this disclosure, the term "or" is not intended to be an exclusive or.

[0191] A radio frame may be composed of one or more frames in the time domain. Each of the one or more frames in the time domain may be called a subframe. A subframe may further be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0192] Numerology may be communication parameters that apply to at least one of transmission and reception of a signal or channel, such as subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering operations performed by the transceiver in the frequency domain, and specific windowing operations performed by the transceiver in the time domain.

[0193] A slot may be composed of one or more symbols (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol or a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol) in the time domain. A slot may be a time unit based on numerology.

[0194] A slot may include multiple minislots. Each minislot may consist of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (or PUSCH) mapping type B.

[0195] The radio frame, subframe, slot, minislot, and symbol all represent time units for transmitting signals, and may be referred to by other names corresponding to the radio frame, subframe, slot, minislot, and symbol.

[0196] For example, one subframe may be called a transmission time interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, or the like instead of a subframe. Furthermore, one slot may be called a unit time. The unit time may differ for each cell depending on the numerology.

[0197] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate wireless resources (such as frequency bandwidth and transmission power that can be used by each terminal 20) to each terminal 20 in TTI units. Note that the definition of TTI is not limited to this.

[0198] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

[0199] When one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

[0200] A TTI having a time length of 1 ms may be called a regular TTI (TTI in LTE Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.

[0201] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.

[0202] A resource block (RB) is a resource allocation unit in the time domain and frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of numerology, for example, 12. The number of subcarriers included in an RB may also be determined based on numerology.

[0203] The time domain of an RB may include one or more symbols and may have a length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc. may each be composed of one or more resource blocks.

[0204] Note that one or more RBs may also be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, or the like.

[0205] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

[0206] A Bandwidth Part (BWP) (which may also be referred to as a fractional bandwidth) may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a common reference point of the carrier. PRBs may be defined in a given BWP and numbered within that BWP.

[0207] The BWP may include a BWP for UL (UL BWP) and a BWP for DL ​​(DL BWP). One or more BWPs may be configured for a UE within one carrier.

[0208] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell," "carrier," etc. in this disclosure may be read as "BWP."

[0209] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc. may be changed in various ways.

[0210] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0211] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."

[0212] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, notification of predetermined information (e.g., notification that "X is true") is not limited to being done explicitly, but may be done implicitly (e.g., by not notifying the predetermined information).

[0213] Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure. [Explanation of symbols]

[0214] 10 base station 110 Transmitter 120 Receiver 130 Setting section 140 Control Unit 20 terminals 210 Transmitter 220 Receiving unit 230 Setting Section 240 Control Unit 1001 processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication equipment 1005 Input Device 1006 Output Device

Claims

1. A terminal capable of communication in a specified frequency band, a receiving unit for receiving configuration information of the number of resource blocks to be used in a second physical uplink control channel that is used before a terminal-specific resource is configured for a first physical uplink control channel in the frequency band; a control unit that determines the number of resource blocks based on the configuration information; a transmitter that performs transmission over the second physical uplink control channel using the determined number of resource blocks; When the number of resource blocks is not notified by the setting information, the control unit determines the number of resource blocks to be 1.

2. The control unit determines, as offsets in the frequency domain of the resource blocks, offset values ​​of cell-specific physical resource blocks and offset values ​​of terminal-specific physical resource blocks; the offset value of the cell-specific physical resource block is determined based on multiplying the number of resource blocks by an offset index of the cell-specific physical resource block; The terminal of claim 1 , wherein the offset value of the terminal-specific physical resource block is determined based on multiplying the number of resource blocks by an offset index of the terminal-specific physical resource block.

3. The terminal according to claim 1 , wherein operations of the receiving unit, the control unit, and the transmitting unit are applied only to operations in the frequency band in FR (Frequency Range) 2-2.

4. A communication method for a terminal capable of communication in a specified frequency band, receiving configuration information of the number of resource blocks to be used in a second physical uplink control channel that is used before terminal-specific resources are configured for a first physical uplink control channel in the frequency band; determining the number of resource blocks based on the configuration information; determining the number of resource blocks to be 1 when the number of resource blocks is not notified by the configuration information; performing transmission over the second physical uplink control channel using the determined number of resource blocks.

5. A system capable of communication in a specified frequency band, including a terminal and a base station, The base station a transmitter configured to transmit, to the terminal, configuration information on the number of resource blocks to be used in a second physical uplink control channel that is used before a resource dedicated to the terminal is configured for a first physical uplink control channel in the frequency band; a receiving unit that receives a signal transmitted on the second physical uplink control channel from the terminal using the number of resource blocks; The terminal a receiving unit that receives the setting information from the base station; a control unit that determines the number of resource blocks based on the configuration information; a transmitter configured to transmit to the base station via the second physical uplink control channel by using the determined number of resource blocks; The control unit determines the number of resource blocks to be 1 when the number of resource blocks is not notified by the setting information.

Images