Terminal, wireless communication system, and communication method

Abstract

To appropriately generate feedback information when scheduling a plurality of PDSCHs by one piece of control information.SOLUTION: The terminal includes a receiver configured to receive configuration information related to bundling of feedback information for a plurality of downlink shared channels scheduled by single downlink control information, a controller configured to generate feedback information including first feedback information for the single downlink shared channel and second feedback information for the plurality of downlink shared channels bundled based on the configuration information, and a transmitter configured to transmit the feedback information in uplink, wherein the second feedback information includes 1-bit bundled information.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a terminal, a base station, and a feedback method 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 114.25 GHz is being considered.

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

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

[0005] As slot lengths become shorter with the use of higher frequency bands, it is expected that a base station will schedule multiple PDSCHs for a terminal using one piece of control information (DCI).

[0006] However, the conventional technology described in Non-Patent Document 1 and the like does not specify how to generate feedback information (specifically, HARQ-ACK information) when scheduling multiple PDSCHs with one DCI, and there is a possibility that the conventional technology will not be able to generate feedback information appropriately.

[0007] The present invention has been made in view of the above points, and aims to provide a technique that enables appropriate generation of feedback information when scheduling multiple PDSCHs using one control information. [Means for solving the problem]

[0008] According to the disclosed technology, a receiving unit receives configuration information regarding bundling of feedback information for a plurality of downlink shared channels scheduled by a single downlink control information; a control unit that generates feedback information including first feedback information for a single downlink shared channel and second feedback information for a plurality of bundled downlink shared channels based on the configuration information; a transmitter for transmitting the feedback information via uplink; Equipped with The second feedback information includes information bundled in one bit. A terminal is provided. [Effects of the Invention]

[0009] According to the disclosed technology, a technology is provided that enables appropriate generation of feedback information when scheduling multiple PDSCHs using one piece of control information. [Brief explanation of the drawings]

[0010] [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 illustrating the relationship between SCS and symbol length. [Figure 5] FIG. 10 is a diagram illustrating a method for generating an R16 Type 2 HARQ-ACK CB. [Figure 6] A diagram showing the configuration of R16 Type 2 HARQ-ACK CB. [Figure 7] FIG. 1 is a diagram illustrating an example of a basic procedure according to an embodiment of the present invention. [Figure 8] FIG. 1 is a diagram for explaining a first embodiment. [Figure 9] FIG. 1 is a diagram for explaining a first embodiment. [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. 10 is a diagram for explaining a second embodiment. [Figure 13] FIG. 10 is a diagram for explaining a second embodiment. [Figure 14] FIG. 10 is a diagram for explaining a third embodiment. [Figure 15] FIG. 10 is a diagram for explaining a third embodiment. [Figure 16] FIG. 10 is a diagram for explaining a third embodiment. [Figure 17] 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 18] 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 19] 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. [Figure 20] FIG. 1 is a diagram illustrating the configuration of a vehicle. DETAILED DESCRIPTION OF THE INVENTION

[0011] 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.

[0012] Existing technology is used as appropriate in the operation of the wireless communication system according to the embodiment of the present invention. The existing technology is, for example, the existing NR. The wireless communication system (base station 10 and terminal 20) according to the present embodiment basically operates in accordance with existing regulations (e.g., Non-Patent Document 1). 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 are mainly explained. Note that all numerical values ​​described below are examples.

[0013] 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.).

[0014] Furthermore, in the embodiments of the present invention, when radio parameters and the like are "configured," it may mean that predetermined values ​​are pre-configured, or that radio parameters notified from the base station 10 or the terminal 20 are set.

[0015] (System Configuration)

[0016] 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.

[0017] 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.

[0018] OFDM is used as the radio access method. In the frequency domain, subcarrier spacing (SCS) of at least 15 kHz, 30 kHz, 120 kHz, and 240 kHz is supported. Regardless of the SCS, a resource block is composed of a predetermined number of consecutive subcarriers (e.g., 12).

[0019] 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.

[0020] 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.

[0021] 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).

[0022] 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.

[0023] Terminal 20 is capable of performing carrier aggregation, which aggregates multiple cells (multiple CCs (component carriers)) to communicate with base station 10. In carrier aggregation, one PCell (primary cell) and one or more SCells (secondary cells) are used. Also, a PUCCH-SCell having a PUCCH may be used. Also, a PUCCH group may be configured.

[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). In addition, in a DC, an MCG is composed of one PCell and one or more SCells, and an SCG is composed of one PSCell (Primary SCell) and one or more SCells. Note that in this specification, a CC (Component Carrier) and a cell may be used synonymously. Also, a PCell and a PSCell may be referred to as an SPCell.

[0026] In the wireless communication system according to this embodiment, when an unlicensed band is used, LBT (Listen Before Talk) is executed. The base station 10 or the terminal 20 senses a signal, and transmits if the sensing result is idle, and does not transmit if the sensing result is busy. Note that LBT is not necessarily performed in an unlicensed band, and there may be cases where LBT is not performed in an unlicensed band.

[0027] (Regarding frequency bands) Fig. 3 shows examples of frequency bands used in the existing NR and frequency bands used in the wireless communication system according to this embodiment. The existing NR has two frequency bands (which may also be referred to as frequency ranges): FR1 (0.41 GHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). As shown in Fig. 3, FR1 supports SCSs of 15 kHz, 30 kHz, and 60 kHz, and a bandwidth (BW) of 5 to 100 MHz. FR2 supports SCSs 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 the present embodiment is assumed to use frequency bands higher than 52.6 GHz (for example, 52.6 GHz to 114.25 GHz) that are not used in existing NR. Note that the technology according to the present invention is not limited to application to such high frequency bands, and can also be applied to existing frequency bands.

[0029] Furthermore, in this embodiment, it is assumed that, with the expansion of the frequency band as described above, an SCS wider than the existing SCS will be used. For example, an SCS of 480 kHz or an SCS wider than 480 kHz will be used as the SCS for SSB and PDCCH / PDSCH.

[0030] In the high frequency band, it is expected that multiple narrow beams will be used to compensate for the large propagation loss, and the SCS will be wider than the existing FR2 SCS (for example, 480 kHz, 960 kHz).

[0031] Figure 4 shows the relationship between SCS and symbol length (symbol time length). As shown in Figure 4, as the SCS becomes wider, the symbol length (symbol time length) becomes shorter. Also, assuming that the number of symbols per slot is constant (i.e., 14 symbols), as the SCS becomes wider, the slot length becomes shorter.

[0032] In a wireless communication system, in response to data reception via PDSCH from base station 10, terminal 20 transmits HARQ-ACK information, in which a HARQ-ACK information bit value is set in a HARQ-ACK codebook (sometimes referred to as HARQ-ACK CB), to base station 10 as feedback. Note that transmitting / receiving data via PDSCH may also be referred to as transmitting / receiving PDSCH. Furthermore, information transmitted as feedback to base station 10 may also be referred to as a HARQ-ACK codebook. Generating information to be transmitted as feedback to base station 10 may also be expressed as generating a HARQ-ACK codebook.

[0033] However, as described above, when the slot length is shortened due to the use of a high frequency band, it is assumed that multiple PDSCHs will be scheduled with one DCI scheduling. Based on such an assumption, it is not clear in the prior art how to generate the HARQ-ACK CB.

[0034] Hereinafter, an embodiment relating to generation of a HARQ-ACK CB in a system capable of scheduling multiple PDSCHs by scheduling using one DCI will be described. In this embodiment, in particular, an example relating to a dynamically generated type 2 HARQ-ACK CB will be described. Hereinafter, scheduling multiple PDSCHs by scheduling using one DCI may be referred to as multi-PDSCH scheduling.

[0035] (How to generate type2 HARQ-ACK CB) First, a method for generating a type 2 HARQ-ACK CB in Rel. 16 will be described with reference to Fig. 5. Note that in the system according to the present embodiment, the method for generating a type 2 HARQ-ACK CB in Rel. 16 may be applied to a cell or the like in which scheduling of multiple PDSCHs by scheduling using one DCI is not permitted.

[0036] In the example of Fig. 5, terminal 20 receives DCI in cell #0 and cell #2 in PDCCH occasion #1. Terminal 20 receives DCI in cell #1 in PDCCH occasion #2. Terminal 20 receives DCI in cell #2 in PDCCH occasion #3. Terminal 20 receives DCI in cell #1 and cell #2 in PDCCH occasion #4.

[0037] The Downlink Assignment Indicator (Index) (DAI) field is enclosed in parentheses in the DCI in Figure 5. The DAI field includes a counter DAI (cDAI) and a total DAI (tDAI).

[0038] The counter DAI is a value obtained by counting the transmitted DCI in the order of cell → PDCCH occasion. The total DAI is the total number of DCIs in the PDCCH occasion, and increases as the number of PDCCH occasions increases.

[0039] Based on the bit position based on the counter DAI and total DAI notified in the DCI, terminal 20 determines the bit position of the HARQ-ACK information for the PDSCH scheduled in that DCI (bit position in type 2 HARQ-ACK CB) and sets the HARQ-ACK information at that bit position. By transmitting the HARQ-ACK CB generated in this way to base station 10, base station 10 can determine which PDSCH the HARQ-ACK information is for and can perform appropriate retransmission, etc.

[0040] Note that even when one PDSCH is transmitted with one DCI, if spatial multiplexing is performed, the number of TBs (transport blocks) (which may be the number of codewords) will be, for example, two. That is, the number of HARQ-ACK information bits for that DCI will be two. Furthermore, if spatial bundling is performed, even if the number of TBs is two, the number of HARQ-ACK information bits will be one. Furthermore, when CBG (code block group)-based transmission is performed, ACK / NACK is returned in CBG units within the TB, so the number of HARQ-ACK information bits will be the number of CBGs per TB. From this perspective, in Rel-16, terminal 20 determines the number of HARQ-ACK bits for each PDSCH reception based on the following information elements received by terminal 20 from base station 10:

[0041] ·maxNrofCodeWordsScheduledByDCI ·harq-ACK-SpatialBundlingPUCCH ·PDSCH-CodeBlockGroupTransmission (About CBG) In Rel-16, when CBG-based transmission is configured in a cell in a PUCCH cell group, the type 2 HARQ-ACK CB is generated as a concatenation of two sub-codebooks shown in FIG.

[0042] The first sub-codebook is a codebook that stores bits of HARQ-ACK information for TB based PDSCH receptions, SPS PDSCH release, SPS PDSCH reception, and DCI format 1_1 indicating SCell dormancy.

[0043] The second sub-codebook is a codebook that stores bits of HARQ-ACK information for CBG-based PDSCH reception in the cell.

[0044] (Processing contents assumed in this embodiment) In this embodiment, it is assumed that the base station 10 performs one of the following operations Alt1 to 3 with regard to counting the DAI when generating a type 2 HARQ-ACK CB corresponding to a DCI that schedules multiple PDSCHs. Note that C-DAI is Counter-DAI, and T-DAI is Total-DAI.

[0045] Alt1: Count C-DAI / T-DAI for each DCI.

[0046] Alt2: Count C-DAI / T-DAI for each PDSCH.

[0047] Alt3: Count C-DAI / T-DAI for every M scheduled PDSCHs, where M is a configurable value, e.g., 1, 2, 4, etc.

[0048] More details about Atl1 and Alt2 are as follows:

[0049] <alt1> The method of counting the C-DAI / T-DAI for each DCI may be the same as in Rel-16. When generating a type 2 HARQ-ACK CB corresponding to a DCI for which multiple PDSCHs can be scheduled, assuming the above Alt1 (DAI count for each DCI), terminal 20 generates at least two sub-codebooks for a certain PUCCH cell group. Of the two sub-codebooks, the first sub-codebook is for the following DCI. Note that the SLIV indicates the time resource allocated to the PDSCH. The TDRA table consists of multiple rows, and when an index indicating a certain row is specified by the DCI, terminal 20 receives the PDSCH using the time resource specified by the SLIV of that row.

[0050] DCI where CBG-based scheduling is not configured and a TDRA table with one SLIV per row is configured CBG-based scheduling is not configured, a TDRA table is configured with multiple SLIVs in at least one row, and a DCI that schedules only one PDSCH Of the two sub-codebooks, the second sub-codebook is for the following DCI:

[0051] A TDRA table is configured with multiple SLIVs in at least one row, and a DCI that schedules multiple PDSCHs <alt2> In generating a type 2 HARQ-ACK CB corresponding to DCI for which multiple PDSCHs can be scheduled, when the above Alt2 (DAI count for each PDSCH) is assumed, the base station 10 performs the following operation.

[0052] PDSCH(s) scheduled by a single DCI are counted first, serving cell(s) in the same PDCCH monitoring occasion of the same PUCCH cell group are counted second, and PDCCH monitoring occasion(s) are counted third. That is, counting is performed in the order of PDSCH -> cell -> PDCCH monitoring occasion. Based on this count value, terminal 20 can, for example, store HARQ-ACK information bit values ​​for each PDSCH in a HARQ-ACK codebook.

[0053] The bit width of the counter DCI field in fallback DCI (i.e., DCI formats 0_0, 1_0) is the same as that in Rel-15 NR.

[0054] In serving cells in the same PUCCH cell group where CBG retransmission is not configured, the number of bits of the counter DAI and total DAI in non-fallback DCI is extended as necessary based on at least the following:

[0055] Number of SLIVs associated with the row index of the TDRA table (About the assignment) Alt1 to Alt3 for the above-mentioned type 2 HARQ-ACK feedback have the following problems.

[0056] (1) The number of sub-codebooks and the details of their configuration are unclear. In particular, it is unclear how the sub-codebooks differ depending on whether CBG-based scheduling is configured. For example, the number of sub-codebooks and the configuration of the sub-codebooks for each of the following are unclear:

[0057] CBG-based scheduling for single PDSCH scheduling only CBG-based scheduling for multiple PDSCH scheduling (2) Regarding the time-domain bundling of HARQ-ACK information, the impact on the codebook / sub-codebook configuration is unclear, the details of bundling are unclear, and the conditions for performing time-domain bundling are unclear. Regarding the conditions, it is necessary to consider the settings of CBD-based transmission and spatial bundling, etc.

[0058] (3) It is not clear what the terminal 20 should do when it is notified of support for the type 2-HARQ-ACK-Codebook for PDSCH receptions scheduled in the same PDCCH monitoring occasion that are greater than one.

[0059] An example of an operation that solves the problem will be described below.

[0060] (Basic operation) First, an example of a basic operation in the wireless communication system of this embodiment will be described with reference to FIG.

[0061] In S100, the terminal 20 transmits capability information (UE capability) to the base station 10. Using this capability information, the base station 10 can determine, for example, the content of the information to be transmitted to the terminal 20 in S101 and S102 below.

[0062] In S101, the base station 10 transmits setting information to the terminal 20 by an RRC message, and the terminal 20 receives the setting information. The setting information may be, for example, whether or not CBG-based transmission is performed. The setting information may also be information notified by RRC signaling, which will be described later in the description of the embodiments.

[0063] In S102, the base station 10 transmits information including, for example, scheduling (allocation information) for multiple PDSCHs by DCI to the terminal 20, and the terminal 20 receives the DCI. The DCI includes a C-DAI and a T-DAI.

[0064] In S103, the terminal 20 receives the PDSCH based on the scheduling information in the DCI, and in S104 transmits HARQ-ACK information (type 2 HARQ-ACK CB) to the base station 10. The base station 10 receives the HARQ-ACK information.

[0065] Each example will be described below.

[0066] Example 1 First, a description will be given of Example 1. Example 1 is an example for the above-mentioned Alt1 (C-DAI / T-DAI count for each DCI). Example 1 has options 1 to 3, each of which will be described below.

[0067] <Example 1: Option 1> Fig. 8 shows an example of a type 2 HARQ-ACK codebook in option 1. As shown in Fig. 8, in option 1, terminal 20 generates separate sub-codebooks for TB-based scheduling and CBG-based scheduling. Furthermore, terminal 20 generates separate sub-codebooks for single-PDSCH scheduling and multiple-PDSCH scheduling.

[0068] For example, terminal 20 includes HARQ-ACK information for SPS release, SPS receptions, and Scell ​​dormancy DCI in a first codebook, which is a sub-codebook for TB-based single PDSCH scheduling.

[0069] More specifically, Option 1 includes Option 1-1 and Option 1-2 below, each of which will be described below. Note that multi-PDSCH may be used as a synonym for multiple PDSCH.

[0070] <Example 1: Option 1-1> In option 1-1, terminal 20 does not generate a separate sub-codebook for DCI that schedules multiple PDSCHs, regardless of the number of PDSCHs to be scheduled. As a result, the number of sub-codebooks generated by terminal 20 is as follows:

[0071] · In multi-PDSCH scheduling, if CBG-based transmission is supported, at least four sub-codebooks are required.

[0072] · If CBG-based transmission in multi-PDSCH scheduling is not supported, at least three sub-codebooks are required.

[0073] The number of HARQ-ACK bits in each sub-codebook in Option 1-1 is as follows:

[0074] For the first sub-codebook for TB-based single PDSCH scheduling, the number of HARQ-ACK bits for each DCI is the same as the number of HARQ-ACK bits in the TB-based sub-codebook in Rel-16.

[0075] For the second sub-codebook for TB-based multi-PDSCH scheduling, the number of HARQ-ACK bits for each DCI is N PDSCH ×N multi TB is determined as follows.

[0076] where N PDSCH is the maximum number of PDSCHs that can be scheduled by one DCI for all PDSCH serving cells. This maximum number is determined, for example, by configuration via RRC signaling or specifications.

[0077] If the configuration or specification by RRC signaling determines that the maximum number of CWs / TBs for one PDSCH when multiple PDSCHs are scheduled by one DCI is greater than 1, and if spatial bundling is not supported or enabled in the case of multiple PDSCH scheduling, N multi TB = 2. If the RRC configuration or specifications determine that the maximum number of CWs / TBs for one PDSCH when multiple PDSCHs are scheduled by one DCI is greater than 1, N shall be used unless "spatial bundling is not supported or enabled in the case of multi-PDSCH scheduling." multi TB =1.

[0078] N unless "the maximum number of CWs / TBs for one PDSCH when multiple PDSCHs are scheduled by one DCI is determined to be greater than 1 by the RRC configuration or specifications." multi TB =1.

[0079] In the third sub-codebook for CBG-based single PDSCH scheduling, the number of HARQ-ACK bits for each DCI is the same as that in the CBG-based sub-codebook in Rel-16.

[0080] In the fourth sub-codebook (if any) for CBG-based multi-PDSCH scheduling, the number of HARQ-ACK bits for each DCI is N across all serving cells configured for CBG-based multi-PDSCH scheduling. PDSCH,c ×N multi TB,c ×N CBG / TB multi,c is determined as the maximum value of

[0081] where N PDSCH,c is the maximum number of PDSCHs that can be scheduled with one DCI in serving cell c. multi TB,c is the maximum number of CWs / TBs for one PDSCH when multiple PDSCHs are scheduled with one DCI in serving cell c. CBG / TB multi,c is the maximum number of CBGs when multi-PDSCH with DCI is scheduled in serving cell c.

[0082] <Example 1: Option 1-2> In option 1-2, terminal 20 generates separate sub-codebooks according to the number of PDSCHs scheduled by DCI. Fig. 9 shows an example of a type 2 HARQ-ACK codebook in option 1-2.

[0083] The number of sub-codebooks in Option 1-2 is as follows: In this specification, "A and / or B" means "A and B, or A or B."

[0084] The number of sub-codebooks in TB-based multi-PDSCH scheduling and / or CBG-based multi-PDSCH scheduling may be defined in a specification, or may be configured by the base station 10 to the terminal 20 by RRC signaling.

[0085] For example, two sub-codebooks are provided for a TB-based multi-PDSCH, one sub-codebook for DCI scheduling PDSCHs 2 to 4, and the other sub-codebook for DCI scheduling PDSCHs 5 to 8. As a result, for example, HARQ-ACK information for DCI scheduling PDSCH 3 is included in the former sub-codebook.

[0086] The number of HARQ-ACK bits in each sub-codebook is as follows:

[0087] The number of HARQ-ACK bits for each DCI in the sub-codebook corresponding to the TB-based PDSCH [N_k-1,N_k] (a value between N_k-1 and N_k) is N_k × N multi TB It is determined as N multi TB The method for determining the value is the same as that for Option 1-1.

[0088] The number of HARQ-ACK bits for each DCI in the sub-codebook corresponding to the CBG-based [N_k-1,N_k] PDSCH (if this is allowed) is N_k × N multi TB,c ×N CBG / TB multi,c It is determined as N multi TB,c and N CBG / TB multi,c The method for determining the value is the same as that for Option 1-1.

[0089] An advantage of Option 1-1 is that the number of sub-codebooks can be reduced compared to Option 1-2, and an advantage of Option 1-2 is that the redundancy of the sub-codebooks for multi-PDSCH is lower compared to Option 1-1.

[0090] <Example 1: Option 2> Next, Option 2 of Example 1 will be described. In Option 2, the terminal 20 generates separate sub-codebooks for different (sets of) serving cells. FIG. 10 shows an example of a type 2 HARQ-ACK codebook in Option 2.

[0091] In option 2, the terminal 20 performs the following process for DCI or PDSCH that is not included in the first subcodebook.

[0092] The terminal 20 divides the multiple serving cells into M sets. For example, the i-th serving cell set is denoted by C i ={serving cell#m1,....,serving cell #m i } and make it correspond to the i-th sub-codebook.

[0093] Next, the terminal 20 selects the set C i For DCI scheduling multi-PDSCH in serving cells belonging to N i,max HARQ-ACK bits are generated and included in the i-th sub-codebook.

[0094] Option 2 has the advantage over option 1 that it can reduce the number of sub-codebooks while maintaining the same redundancy level.

[0095] In Option 2, there are two options for the process of determining the set of serving cells and the number of HARQ-ACK bits, which will be described as Options 2-1 and 2-2.

[0096] <Example 1: Option 2-1> In option 2-1, the mapping between the serving cell and the serving cell set is configured in the terminal 20 by RRC signaling. i,max is calculated for the serving cell of the set based on the PDSCH related parameters (e.g., CBG, CW, multi-PDSCH scheduling related parameters).

[0097] N i,max is set C i max(N DL,multiple TB,c ×N CBG / TB,multiple HAQRQ-ACK,c ×N PDSCH,multiple c ,N DL,single TB,c ×N CBG / TB,single HARQ-ACK,c ) is calculated based on the maximum value of

[0098] N DL,multiple TB,c is the maximum number of CWs / TBs when multi-PDSCH is scheduled by DCI in serving cell c. If spatial bundling in the multi-PDSCH scheduling case is enabled or configured, this value is 1.

[0099] N CBG / TB,multiple HAQRQ-ACK,c is the maximum number of CBGs when multi-PDSCH is scheduled by DCI in serving cell c. If CBG-based transmission in multi-PDSCH scheduling with single DCI is not supported or CBG-based transmission is not configured in serving cell c, this value is 1.

[0100] N PDSCH,multiple c is the maximum number of PDSCHs that can be scheduled by one DCI in serving cell c.

[0101] N DL,single TB,c is the maximum number of CWs / TBs when a single PDSCH is scheduled in serving cell c. If spatial bundling is enabled or configured, this value is 1.

[0102] N CBG / TB,single HARQ-ACK,c is the maximum number of CBGs when a single PDSCH with DCI is scheduled in serving cell c. If CBG-based transmission is not configured in serving cell c, this value is 1.

[0103] <Example 1: Option 2-2> In option 2, the number of serving cell sets and the corresponding maximum number of HARQ-ACK bits (N i,max ) is specified in a specification or configured by the base station 10 to the terminal 20 by RRC signaling. The terminal 20 determines which serving cell set includes the serving cell c based on the PDSCH-related parameters. Specifically, this is as follows.

[0104] For each i>0, N i-1,max ≦N i,max If N i-1,max ≦max(N DL,multiple TB,c ×N CBG / TB,multiple HAQRQ-ACK,c ×N PDSCH,multiple c ,N DL,single TB,c ×N CBG / TB,single HARQ-ACK,c )≦N i,max If so, then serving cell c is in serving cell set C i Included in.

[0105] <Example 1: Option 3> In option 3, terminal 20 generates separate sub-codebooks based on the actual scheduling information in the DCI. Figure 11 shows an example of a type 2 HARQ-ACK codebook in option 3. More specifically, multiple sub-codebooks with different target numbers of HARQ-ACK bits are generated as follows.

[0106] Here, the number of sub-codebooks and the corresponding fixed number of HARQ-ACK bits are set by RRC signaling or specified in a specification, for example, the first sub-codebook is N1 bits, the second sub-codebook is N2 bits, ..., the Mth sub-codebook is N M bits, where N1≦N2≦...≦N M is.

[0107] The terminal 20 receives N PDSCH actual For DCIs that schedule PDSCHs, i-1 ≦N TB c ×N CBG c ×N PDSCH actual ≦N i If the following holds, the HARQ-ACK information for the PDSCH scheduled by the DCI is included in the i-th sub-codebook.

[0108] where N PDSCH actual is the number of actual PDSCHs scheduled by the current DCI. PDSCH actual The following explanation will be given based on the size of the

[0109] (N PDSCH actual > 1) N TB c is the maximum number of TBs / CWs per PDSCH in multi-PDSCH scheduling. If spatial bundling for the multi-PDSCH scheduling case is enabled or configured, this value is 1.

[0110] N CBG c is the maximum number of CBGs when multiple PDSCHs are scheduled by DCI1_1 in serving cell c. If PDSCHs are scheduled by DCI1_0 / 1_2, or if CBG-based transmission is not supported in multi-PDSCH scheduling with a single DCI, or if CBG-based transmission is not supported in serving cell c, this value is 1.

[0111] (N PDSCH actual = 1) N TB c is the maximum number of TBs / CWs when a single PDSCH is scheduled in serving cell c. If spatial bundling is enabled or configured, this value is 1.

[0112] N CBG c is the maximum number of CBGs when a single PDSCH is scheduled by DCI1_1 in serving cell c. If a PDSCH is scheduled by DCI1_0 / 1_2, or if CBG-based transmission is not supported in serving cell c, this value is 1.

[0113] In option 3, for SPS release, SPS PDSCH receptions, and Scell ​​dormancy indication, HARQ-ACK information is included in, for example, the first sub-codebook. Option 3 has the advantage of being less redundant than options 1 and 2.

[0114] According to the first embodiment, it is possible to appropriately generate a type 2 HARQ-ACK codebook when counting DAI for each DCI.

[0115] Example 2 Next, a description will be given of Example 2. Example 2 is an example corresponding to the above-mentioned Alt2 (counting C-DAI / T-DAI for each PDSCH). The number of sub-codebooks is as follows.

[0116] If CBG-based scheduling is not configured in any cell, terminal 20 generates two sub-codebooks as a type 2 HARQ-ACK codebook. Fig. 12 shows an example of the type 2 HARQ-ACK codebook in this case.

[0117] The first sub-codebook is a sub-codebook for DCIs without DAI field extension, such as DCI1_0 and non-fallback DCIs with a TDRA table configured with only one SLIV per row.

[0118] The second sub-codebook is a sub-codebook for a DCI with a DAI field extension, such as a non-fallback DCI in which a TDRA table having multiple SLIVs is configured in at least one row.

[0119] The above first sub-codebook is, for example, a sub-codebook for DCI scheduling a single PDSCH, and the second sub-codebook is, for example, a sub-codebook for DCI scheduling multiple PDSCHs.

[0120] When CBG-based scheduling is configured in a serving cell, terminal 20 generates two or three sub-codebooks as a type 2 HARQ-ACK codebook. Fig. 13 shows an example of the type 2 HARQ-ACK codebook in this case.

[0121] The first sub-codebook is a sub-codebook for DCI without DAI field extension, such as DCI1_0 and DCI1_2 in which a TDRA table having only one SLIV per row is configured. The first sub-codebook is, for example, a sub-codebook for DCI scheduling a single PDSCH with CBG.

[0122] The second sub-codebook is a sub-codebook for DCI scheduling CBG-based transmission with DAI field extension, such as DCI1_1 in a serving cell configured for CBG-based transmission. The second sub-codebook is a sub-codebook for DCI scheduling multiple PDSCHs with CBG, such as DCI1_1 in a serving cell configured for CBG-based transmission.

[0123] The third sub-codebook is a sub-codebook for DCIs scheduling TB-based transmission with DAI field extension, such as DCI1_1 of a serving cell where CBG-based transmission is not configured, and DCI1_2 where a TDRA table with multiple SLIVs in at least one row is configured. The third sub-codebook is, for example, a sub-codebook for DCIs scheduling multiple PDSCHs without CBG.

[0124] In the second embodiment, there are the following options 1 and 2 for DAI when multiple DCIs are transmitted in the same PDCCH occasion.

[0125] <Example 2: Option 1> Terminal 20 does not assume DCI that schedules multiple PDSCHs when detecting multiple DCIs in the same PDCCH occasion. Option 1 includes the following options 1-1 and 1-2.

[0126] <Example 2: Option 1-1> When detecting multiple DCIs in the same PDCCH occasion, terminal 20 does not assume DCIs for which a TDRA table including multiple SLIVs is set in at least one row.

[0127] <Example 2: Option 1-2> When detecting multiple DCIs in the same PDCCH occasion, terminal 20 assumes that the DCIs are those for which a TDRA table including multiple SLIVs is set in at least one row. However, scheduling multiple PDSCHs is not permitted for any DCI. Note that option 1-1 is stricter than option 1-2.

[0128] For example, suppose that DCI#1 and DCI#2 are detected in the same PDCCH monitoring occasion in the same cell. Furthermore, DCI#1 and DCI#2 each schedule one PDSCH. If DCI#1 is DCI format 1_1 with a TDRA table configured for multiple PDSCH scheduling, option 1-2 does not result in an error, but option 1-1 results in an error case.

[0129] <Example 2: Option 2> In option 2, terminal 20 assumes that there is DCI that schedules multiple PDSCHs when detecting multiple DCIs in the same PDCCH occasion.

[0130] In this case, the base station 20 first counts the DAI for the PDSCH for each DCI, and then counts for each PDCCH monitoring occasion.

[0131] The following options 2-1 and 2-2 are used to determine the order of DCIs in a count of multiple DCIs.

[0132] In option 2-1, the base station 10 determines the order of DCIs based on the "start and / or end time" of the "first and / or last PDSCH" scheduled by each DCI. For example, the earlier time is counted first.

[0133] In option 2-2, the base station 10 determines the order of the DCIs based on the number of PDSCHs scheduled in each DCI, for example, counting the DCIs in descending order of the number of PDSCHs.

[0134] According to the second embodiment, it is possible to appropriately generate a type 2 HARQ-ACK codebook when performing DAI counting for each PDSCH.

[0135] Example 3 Next, a third embodiment will be described. The third embodiment can be applied to both the first and second embodiments. In the third embodiment, time domain bundling of multiple PDSCHs scheduled by one DCI will be described. The bundling in the time domain is, for example, combining two bits into one bit by ANDing (or ORing) HARQ-ACK information for a PDSCH received at time 1 and HARQ-ACK information for a PDSCH received at time 2.

[0136] First, the following options 1 and 2 will be described as conditions for the terminal 20 to determine whether to perform time domain bundling.

[0137] <Example 3: Option 1> In Option 1, whether to perform (enable) time domain bundling across multiple PDSCHs is determined depending on "whether CBG-based transmission (for multiple PDSCH scheduling) is configured," and / or "the maximum number of TBs / CWs in a PDSCH (for multiple PDSCH scheduling)," and / or "whether spatial bundling is configured when a maximum of two CWs / TBs (for multiple PDSCH scheduling) are configured." An example will be described below.

[0138] Example 1: When CBG-based transmission for multiple PDSCH scheduling is configured, the terminal 20 determines that time-domain bundling across multiple PDSCHs cannot be enabled.

[0139] Example 2: If the maximum number of TB / CWs of a PDSCH is set to 2 and spatial bundling is not configured, the terminal 20 determines that time domain bundling across multiple PDSCHs cannot be enabled.

[0140] <Example 3: Option 2> In option 2, whether to perform (enable) time domain bundling across multiple PDSCHs is determined independently of "whether CBG-based transmission (for multiple PDSCH scheduling) is configured" and / or "the maximum number of TBs / CWs per PDSCH (for multiple PDSCH scheduling)" and / or "whether spatial bundling is configured when a maximum of two CWs / TBs (for multiple PDSCH scheduling) are configured." An example will be described below.

[0141] For example, when the maximum number of TB / CW for a PDSCH is set to 2, the terminal 20 determines that time domain bundling across multiple PDSCHs can be enabled or disabled. Whether to enable or disable bundling may be determined based on an instruction from the base station 10 (RRC, MAC, DCI, etc.).

[0142] Next, the bundling method across multiple PDSCHs will be described in the following cases 1 and 2.

[0143] <Example 3: Case 1> In case 1, if the maximum number of CW / TB of PDSCH for multiple PDSCH scheduling is 1 in all serving cells in the sub-codebook due to RRC configuration or specifications, terminal 20 bundles HARQ-ACK information for multiple PDSCHs into M bits, or terminal 20 bundles HARQ-ACK information for each of "M PDSCHs" into 1 bit. M may be determined by specifications or may be set by base station 10 via RRC. M may be 1, 2, 3, 4, or any number equal to or greater than 5.

[0144] <Example 3: Case 2> In case 2, if the RRC configuration or specification specifies that the maximum number of CW / TB of PDSCH for multiple PDSCH scheduling is 2 in at least one serving cell in the sub-codebook and time domain bundling is enabled, then there are Option 1 and Option 2 below.

[0145] In Option 1, regardless of the explicit configuration of spatial bundling in such cases, spatial bundling is (implicitly) enabled and steps 1 and 2 below are performed.

[0146] In step 1, the terminal 20 performs spatial bundling for HARQ-ACK of each PSCH in the same way as spatial bundling in Rel-16. In step 2, the terminal 20 performs time-domain bundling across multiple PDSCHs.

[0147] Option 2 requires explicit configuration for spatial bundling. In such a case, if spatial bundling is configured, terminal 20 first performs spatial bundling and then performs time-domain bundling across multiple PDSCHs, as shown in Fig. 14 .

[0148] If the spatial band is not set, the following options are available: 2-1 and 2-2.

[0149] In option 2-1, as shown in Fig. 15, terminal 20 first performs time-domain bundling over the first TB in each of the multiple PDSCHs, and then performs time-domain bundling over the second TB in each of the multiple PDSCHs. Note that if only one TB is actually scheduled, the second TB is ACKed.

[0150] Option 2-2 is an error case.

[0151] The effect of Example 3 on the codebook / sub-codebook will be explained for Example 1 (Alt1) and Example 2 (Alt2), respectively, as shown in FIG.

[0152] <Impact on Example 1 (Alt1)> Time-domain bundling does not affect the separation of sub-codebooks. For example, if HARQ-ACK information for multiple PDSCHs can be bundled into one bit per DCI, the HARQ-ACK information for multiple PDSCHs and a single PDSCH are included in separate sub-codebooks.

[0153] <Impact on Example 2 (Alt2)> Time-domain bundling affects the separation of sub-codebooks: When time-domain bundling across multiple PDSCHs is enabled, HARQ-ACK information bits for one DCI may be included in a sub-codebook for a single PDSCH.

[0154] The selection of a sub-codebook can be performed based on the number of HARQ-ACK information bits per DCI after bundling. For example, if HARQ-ACK information for multiple PDSCHs can be bundled into one bit per DCI, HARQ-ACK information for multiple PDSCH scheduling and single PDSCH scheduling is included in one sub-codebook, as shown in Figure 16. Note that Figure 16 is an example of the case where "max #CW = 1, max # PDSCHs by one DCI = 8, CBG not configured".

[0155] According to the third embodiment, it is possible to appropriately perform time domain bundling when performing multiple PDSCH scheduling using DCI.

[0156] (Other examples) An example applicable to any of the first to third embodiments will be described below.

[0157] Which of the above-mentioned multiple embodiments / options is used may be set by upper layer parameters transmitted from the base station 10 to the terminal 20, may be notified from the terminal 20 to the base station 10 as terminal capability (UE capability), may be defined by specifications, or may be set by upper layer parameters and notified by the terminal 20 as terminal capability (UE capability).

[0158] Information indicating whether terminal 20 supports scheduling of multiple PDSCHs based on a single DCI may be defined as UE capability.

[0159] Furthermore, as the terminal capability (UE Capability), information indicating whether or not the terminal 20 supports C-DAI / T-DAI counted for each DCI for type 2 HARQ-ACK feedback for multi-PDSCH scheduling may be defined.

[0160] Furthermore, as the terminal capability (UE Capability), information indicating whether or not the terminal 20 supports C-DAI / T-DAI counted for each PDSCH for type 2 HARQ-ACK feedback for multi-PDSCH scheduling may be defined.

[0161] Furthermore, information indicating whether terminal 20 supports separate sub-codebooks for DCI scheduling multiple PDSCHs and / or CBG-based transmissions in different serving cells may be defined as UE capability.

[0162] Furthermore, information indicating whether terminal 20 supports separate sub-codebooks for DCI scheduling different numbers of PDSCHs and / or CBG-based transmissions may be defined as UE capability.

[0163] Furthermore, information indicating whether or not terminal 20 supports time domain bundling across multiple PDSCHs may be defined as terminal capability (UE capability).

[0164] Furthermore, as the UE capability, information indicating whether or not the terminal 20 supports time domain bundling across multiple PDSCHs may be defined when a maximum of two TB / CWs can be scheduled for multi-PDSCH scheduling.

[0165] The terminal 20 may transmit one or more of the above-mentioned capability information to the base station 10. Furthermore, based on the capability information received from the terminal 20, the base station 10 may instruct the terminal 20 to operate in accordance with the capability.

[0166] As a variation, the techniques described in the first to third embodiments may be applied to a type 1 HARQ-ACK codebook or a HARQ-ACK codebook other than types 1 and 2. The order of the sub-codebooks in each embodiment is an example, and the order may be other than the order described in each embodiment.

[0167] Furthermore, the technique of the first embodiment may be applied to the case where the DAI is counted for each PDSCH, and the technique of the second embodiment may be applied to the case where the DAI is counted for each DCI.

[0168] In addition, in the first to third embodiments, an example is described in which sub-codebooks for TB-based scheduling (scheduling by the first method) and sub-code blocks for CBG-based scheduling (scheduling by the second method) are separated, but this is just an example. The scheduling by the first method may be a method other than TB-based scheduling, and the scheduling by the second method may be a method other than CBG-based scheduling.

[0169] (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.

[0170] <Base station 10> Fig. 17 is a diagram showing an example of the functional configuration of the base station 10. As shown in Fig. 17, 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. 17 is merely an example. The names of the functional divisions and functional units may be any as long as they can execute the operations according 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.

[0171] 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.

[0172] 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.

[0173] 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.

[0174] <Terminal 20> Fig. 18 is a diagram showing an example of the functional configuration of the terminal 20. As shown in Fig. 18, 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. 18 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.

[0175] 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.

[0176] The setting unit 230 stores various setting information received by the receiving unit 220 from the base station 10 or other terminals 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. The control unit 240 controls the terminal 20. The control unit 240 also includes a function for performing LBT.

[0177] The terminal and base station of this embodiment may be configured as the terminal and base station shown in the following items. Also, the following feedback method may be implemented.

[0178] <Configurations related to Examples 1 and 3> (Section 1) a control unit that generates feedback information including first feedback information for control information for performing scheduling on the downlink shared channel using a first method and second feedback information for control information for performing scheduling on the downlink shared channel using a second method; a transmitter that transmits the feedback information via an uplink; At least the first feedback information includes third feedback information for control information for scheduling a single downlink shared channel and fourth feedback information for control information for scheduling a plurality of downlink shared channels. Terminal. (Section 2) The fourth feedback information includes a plurality of pieces of feedback information corresponding to different numbers of downlink control channels for which scheduling is performed using control information. 1. The terminal described in paragraph 1. (Section 3) a control unit that generates feedback information including first feedback information for control information for performing scheduling on the downlink shared channel using a first method and a plurality of second feedback information for control information for performing scheduling on the downlink shared channel using a second method; a transmitter that transmits the feedback information via an uplink; Each of the plurality of second feedback information corresponds to a different set of cells. Terminal. (Section 4) The control unit performs spatial bundling on feedback information of each of the plurality of downlink shared channels, and then performs time domain bundling on feedback information of the plurality of downlink shared channels. A terminal according to any one of paragraphs 1 to 3. (Section 5) a transmitter that transmits first control information for performing scheduling on the downlink shared channel using a first method and second control information for performing scheduling on the downlink shared channel using a second method; a receiver configured to receive feedback information via uplink, the feedback information including first feedback information for the first control information and second feedback information for the second control information; At least the first feedback information includes third feedback information for control information for scheduling a single downlink shared channel and fourth feedback information for control information for scheduling a plurality of downlink shared channels. Base station. (Section 6) generating feedback information including first feedback information for control information for scheduling the downlink shared channel in a first manner and second feedback information for control information for scheduling the downlink shared channel in a second manner; transmitting the feedback information on an uplink; At least the first feedback information includes third feedback information for control information for scheduling a single downlink shared channel and fourth feedback information for control information for scheduling a plurality of downlink shared channels. The feedback method implemented by the device.

[0179] Any of the above configurations provides a technique that enables appropriate transmission of feedback information when multiple PDSCHs are scheduled using one control information. According to the second clause, feedback information that clearly indicates the difference in the number of downlink control channels can be generated. According to the fourth clause, time-domain bundling can be appropriately performed when multiple downlink shared channels are scheduled using control information.

[0180] <Configurations related to Examples 2 and 3> (Section 1) a control unit that generates feedback information including first feedback information for control information for scheduling a single downlink shared channel and second feedback information for control information for scheduling a plurality of downlink shared channels; a transmitter for transmitting the feedback information via uplink; A terminal comprising: (Section 2) When scheduling based on code block groups is configured in a certain cell, the control unit further includes, in the feedback information, third feedback information for control information in a cell in which scheduling based on code block groups is not configured. 1. The terminal described in paragraph 1. (Section 3) The control unit assumes that none of the plurality of pieces of control information detected in the same control channel monitoring occasion schedules the plurality of downlink shared channels. 2. A terminal according to claim 1 or 2. (Section 4) The control unit performs spatial bundling on feedback information of each of the plurality of downlink shared channels, and then performs time domain bundling on feedback information of the plurality of downlink shared channels. A terminal according to any one of paragraphs 1 to 3. (Section 5) a transmitter that transmits first control information for scheduling a single downlink shared channel and second control information for scheduling a plurality of downlink shared channels; a receiver configured to receive feedback information via uplink, the feedback information including first feedback information for the first control information and second feedback information for the second control information; A base station comprising: (Section 6) generating feedback information including first feedback information for control information for scheduling a single downlink shared channel and second feedback information for control information for scheduling a plurality of downlink shared channels; transmitting the feedback information on an uplink; A feedback method performed by a terminal, comprising:

[0181] Any of the above configurations provides a technique that enables appropriate transmission of feedback information when multiple PDSCHs are scheduled by one control information. According to the second clause, feedback information can be generated depending on whether scheduling based on code block groups is configured. According to the third clause, it is possible to clarify the operation when multiple control information is received at the same control channel monitoring opportunity. According to the fourth clause, it is possible to appropriately perform time domain bundling when multiple downlink shared channels are scheduled by control information.

[0182] (Hardware configuration) The block diagrams (FIGS. 17 and 18) 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 directly or indirectly connected (for example, using wires, wirelessly, etc.) and these multiple devices. The functional block may be realized by combining the single device or the multiple devices with software.

[0183] 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.

[0184] 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. 19 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.

[0185] 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.

[0186] 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.

[0187] 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.

[0188] 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. 17 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. 18 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.

[0189] 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.

[0190] 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.

[0191] 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.

[0192] 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).

[0193] 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.

[0194] 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.

[0195] Furthermore, the terminal 20 or the base station 10 may be provided in the vehicle 1. An example of the configuration of the vehicle 1 is shown in FIG.

[0196] As shown in Figure 20, the vehicle 1 includes a drive unit 2, a steering unit 3, an accelerator pedal 4, a brake pedal 5, a shift lever 6, left and right front wheels 7, left and right rear wheels 8, an axle 9, an electronic control unit 11, various sensors 21 to 29, an information service unit 12, and a communication module 13.

[0197] The drive unit 2 is composed of, for example, an engine, a motor, or a hybrid of an engine and a motor. The steering unit 3 includes at least a steering wheel (also called a handle), and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel operated by the user.

[0198] The electronic control unit 11 is made up of a microprocessor 31, memory (ROM, RAM) 32, and a communication port (IO port) 33. Signals are input to the electronic control unit 11 from various sensors 21 to 27 provided in the vehicle. The electronic control unit 11 may also be called an ECU (Electronic Control Unit).

[0199] The signals from the various sensors 21 to 28 include a current signal from a current sensor 21 that senses the current of the motor, a rotation speed signal of the front and rear wheels obtained by a rotation speed sensor 22, an air pressure signal of the front and rear wheels obtained by an air pressure sensor 23, a vehicle speed signal obtained by a vehicle speed sensor 24, an acceleration signal obtained by an acceleration sensor 25, an accelerator pedal depression amount signal obtained by an accelerator pedal sensor 29, a brake pedal depression amount signal obtained by a brake pedal sensor 26, a shift lever operation signal obtained by a shift lever sensor 27, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 28.

[0200] The information service unit 12 is composed of various devices, such as a car navigation system, an audio system, speakers, a television, and a radio, for providing various types of information such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 12 uses information acquired from external devices via the communication module 13, etc., to provide various types of multimedia information and multimedia services to the occupants of the vehicle 1.

[0201] The driving assistance system unit 30 is composed of various devices that provide functions for preventing accidents and reducing the driver's driving burden, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS, etc.), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps, etc.), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. The driving assistance system unit 30 also transmits and receives various information via the communication module 13 to realize driving assistance functions or autonomous driving functions.

[0202] The communication module 13 can communicate with the microprocessor 31 and components of the vehicle 1 via the communication port. For example, the communication module 13 transmits and receives data via the communication port 33 to and from the drive unit 2, steering unit 3, accelerator pedal 4, brake pedal 5, shift lever 6, left and right front wheels 7, left and right rear wheels 8, axles 9, the microprocessor 31 and memory (ROM, RAM) 32 in the electronic control unit 11, and sensors 21 to 28, which are provided in the vehicle 1.

[0203] The communication module 13 is a communication device that can be controlled by the microprocessor 31 of the electronic control unit 11 and can communicate with an external device. For example, it transmits and receives various information to and from the external device via wireless communication. The communication module 13 may be located either inside or outside the electronic control unit 11. The external device may be, for example, a base station, a mobile station, or the like.

[0204] The communication module 13 transmits, via wireless communication, to an external device a current signal from the current sensor that is input to the electronic control unit 11. The communication module 13 also transmits, via wireless communication, to an external device, the rotation speed signals of the front and rear wheels acquired by the rotation speed sensor 22, the air pressure signals of the front and rear wheels acquired by the air pressure sensor 23, the vehicle speed signal acquired by the vehicle speed sensor 24, the acceleration signal acquired by the acceleration sensor 25, the accelerator pedal depression amount signal acquired by the accelerator pedal sensor 29, the brake pedal depression amount signal acquired by the brake pedal sensor 26, the shift lever operation signal acquired by the shift lever sensor 27, and the detection signals for detecting obstacles, vehicles, pedestrians, etc. acquired by the object detection sensor 28, all of which are input to the electronic control unit 11.

[0205] The communication module 13 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from external devices and displays it on the information service unit 12 provided in the vehicle. The communication module 13 also stores the various information received from external devices in a memory 32 that can be used by the microprocessor 31. Based on the information stored in the memory 32, the microprocessor 31 may control the drive unit 2, steering unit 3, accelerator pedal 4, brake pedal 5, shift lever 6, left and right front wheels 7, left and right rear wheels 8, axles 9, sensors 21 to 28, and the like provided in the vehicle 1.

[0206] The communication module 13 may be the terminal 20 or the base station 10 described in this embodiment.

[0207] (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; features described in two or more items may be used in combination as needed, and features described in one item may apply to features 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.

[0208] 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.

[0209] Each aspect / embodiment described in the present disclosure may be any of the following: LTE (Long Term Evolution), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (x is, for example, an integer or decimal number)), FRA (Future Radio Access), NR (new Radio), New radio access (NX), Future generation radio access (FX), 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 The present invention may be applied to at least one of systems using 802.20, UWB (Ultra-Wideband), Bluetooth (registered trademark), or other appropriate systems, and next-generation systems that are extended, modified, created, or defined based on these systems. The present invention may also be applied to a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A with 5G).

[0210] 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.

[0211] 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).

[0212] The information, signals, etc. 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.

[0213] 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.

[0214] 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).

[0215] 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.

[0216] 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.

[0217] 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.

[0218] 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.

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

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

[0221] 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.

[0222] 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.

[0223] 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.

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

[0225] 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.

[0226] At least one of the base station and the mobile station may be referred to as 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 object, the mobile object itself, etc. The mobile object refers to a movable object, and may move at any speed. Naturally, this also includes cases where the mobile object is stationary. Examples of the mobile object include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and objects mounted thereon. The mobile object may also be a mobile object that moves autonomously based on an operational command. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (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 be a device that does 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.

[0227] 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.

[0228] 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.

[0229] 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.

[0230] 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.

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

[0232] 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."

[0233] 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.

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

[0235] 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.

[0236] 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.

[0237] 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.

[0238] 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.

[0239] 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.

[0240] 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.

[0241] 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.

[0242] 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.

[0243] 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.

[0244] 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.

[0245] 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.

[0246] 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.

[0247] 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.

[0248] 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.

[0249] 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.

[0250] 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.

[0251] 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.

[0252] 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.

[0253] 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."

[0254] 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.

[0255] 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.

[0256] 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."

[0257] 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).

[0258] 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]

[0259] 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 receiving unit for receiving configuration information regarding bundling of feedback information for multiple downlink shared channels scheduled by a single downlink control information; a control unit that generates feedback information including first feedback information for a single downlink shared channel and second feedback information for a plurality of bundled downlink shared channels based on the configuration information; a transmitter for transmitting the feedback information via an uplink; Equipped with the second feedback information includes information bundled in one bit; Terminal.

2. the first feedback information is included in a first sub-codebook, the second feedback information is included in a second sub-codebook, and the feedback information is included in a codebook obtained by concatenating the second sub-codebook to the first sub-codebook. The terminal according to claim 1 .

3. The second feedback information includes information bundled into the one bit when spatial bundling is set. The terminal according to claim 1 .

4. A wireless communication system including a terminal and a base station, The terminal a receiving unit for receiving configuration information regarding bundling of feedback information for multiple downlink shared channels scheduled by a single downlink control information; a control unit that generates feedback information including first feedback information for a single downlink shared channel and second feedback information for a plurality of bundled downlink shared channels based on the configuration information; a transmitter for transmitting the feedback information via an uplink; Equipped with the second feedback information includes information bundled in one bit; The base station receives the feedback information. Wireless communication system.

5. receiving configuration information regarding bundling of feedback information for multiple downlink shared channels scheduled by a single downlink control information; generating feedback information including first feedback information for a single downlink shared channel and second feedback information for a plurality of bundled downlink shared channels based on the configuration information; transmitting the feedback information on an uplink; Equipped with the second feedback information includes information bundled in one bit; A method of communication by a terminal.

Images