Terminals, base stations, and communication methods

Abstract

Provided is a terminal comprising: a reception unit that receives, by a downlink, control information including information for scheduling a plurality of downlink shared signals and information indicating that feedback to a downlink shared signal is to be disabled; and a control unit that determines, on the basis of whether feedback to the downlink shared signal is set as enabled or set as disabled in the control information, whether information about feedback to the downlink shared signal is to be transmitted.

Description

[Technical Field] 【0001】 The present invention relates to a terminal, base station, and communication method in a wireless communication system. [Background technology] 【0002】 In NR (New Radio) (also known as "5G"), the successor system to LTE (Long Term Evolution), technologies are being considered that meet requirements such as a large-capacity system, high-speed data transmission, low latency, simultaneous connection of many terminals, low cost, and low power consumption (for example, Non-Patent Document 1). 【0003】 NR Release 17 explores the use of higher frequency bands than previous releases (e.g., Non-Patent Document 2). For example, it examines applicable neurology, including subcarrier spacing and channel bandwidth, physical layer design, and anticipated interferences in actual wireless communication in the frequency band from 52.6 GHz to 71 GHz. 【0004】 Furthermore, NR is considering a multi-PDSCH scheduling function that schedules multiple PDSCHs within a single DCI for higher frequency bands such as 52.6GHz to 71GHz. [Prior art documents] [Non-patent literature] 【0005】 [Non-Patent Document 1] 3GPP TS 38.300 V16.6.0(2021-06) [Non-Patent Document 2] 3GPP TS 38.306 V16.5.0(2021-06) [Overview of the project] [Problems that the invention aims to solve] 【0006】 There is a problem in that specifications for applying wireless communication systems to high-frequency bands are not defined. For example, the prior art described in Non-Patent Document 1, etc., does not specify how to invalidate feedback information (specifically HARQ-ACK information) when applying multi-PDSCH scheduling, and it is possible that the prior art may not be able to properly invalidate the feedback information. 【0007】 This invention has been made in view of the above points, and aims to apply wireless communication systems to high-frequency bands. [Means for solving the problem] 【0008】 According to the disclosed technology, a terminal is provided which includes a receiving unit that receives control information on the downlink, including information for scheduling multiple downlink shared signals and information indicating that feedback to the downlink shared signals is disabled, and a control unit that determines whether or not to transmit feedback information to the downlink shared signals based on whether the feedback to the downlink shared signals is set to be enabled or disabled in the control information. [Effects of the Invention] 【0009】 The disclosed technology provides a method for applying wireless communication systems to high-frequency bands. [Brief explanation of the drawing] 【0010】 [Figure 1] This figure illustrates a wireless communication system according to an embodiment of the present invention. [Figure 2] This figure shows an example configuration of a wireless communication system according to an embodiment of the present invention. [Figure 3] This figure shows an example of a frequency range according to an embodiment of the present invention. [Figure 4] This figure shows the relationship between SCS and symbol length. [Figure 5] This is the first diagram illustrating how the PDSCH slot window is determined. [Figure 6] This is a second diagram for explaining a method for determining a PDSCH slot window. [Figure 7] This is a diagram for explaining a method for determining candidate reception opportunities in each slot. [Figure 8] This is a diagram showing an example of a type 1 HARQ-ACK codebook. [Figure 9] This is a diagram for explaining HARQ-ACK in multi-PDSCH scheduling. [Figure 10] This is a diagram for explaining a method for generating a type 2 HARQ-ACK codebook. [Figure 11] This is a diagram showing a configuration example of a type 2 HARQ-ACK codebook. [Figure 12] This is a diagram showing an example of terminal capability information regarding multi-PDSCH scheduling. [Figure 13] This is a diagram showing an example of terminal capability information regarding invalidation of a HARQ-ACK codebook in a non-terrestrial network of NR. [Figure 14] This is a diagram showing an example of terminal capability information regarding invalidation of a HARQ-ACK codebook in a multi-broadcast service of NR. [Figure 15] This is a diagram showing an example of a basic procedure according to an embodiment of the present invention. [Figure 16] This is a first diagram showing a specific example according to Case C of Example 2 of an embodiment of the present invention. [Figure 17] This is a second diagram showing a specific example according to Case C of Example 2 of an embodiment of the present invention. [Figure 18] This is a diagram showing an example of a functional configuration of a base station according to an embodiment of the present invention. [Figure 19] This is a diagram showing an example of a functional configuration of a terminal according to an embodiment of the present invention. [Figure 20] This is a diagram showing an example of a hardware configuration of a base station or a terminal according to an embodiment of the present invention. [Figure 21]This figure shows an example of the configuration of a vehicle according to an embodiment of the present invention. [Modes for carrying out the invention] 【0011】 Embodiments of the present invention will be described below with reference to the drawings. Note that the embodiments described below are examples, and the embodiments to which the present invention applies are not limited to those described below. 【0012】 In the operation of the wireless communication system according to the embodiments of the present invention, existing technologies may be used as appropriate. Such existing technologies include, but are not limited to, existing NR or LTE. Furthermore, the term "LTE" as used herein has a broad meaning that includes LTE-Advanced and LTE-Advanced and later technologies (e.g., NR), unless otherwise specified. 【0013】 Furthermore, in the embodiments of the present invention described below, terms such as SS (Synchronization signal), PSS (Primary SS), SSS (Secondary SS), PBCH (Physical broadcast channel), PRACH (Physical random access channel), PDCCH (Physical Downlink Control Channel), PDSCH (Physical Downlink Shared Channel), PUCCH (Physical Uplink Control Channel), and PUSCH (Physical Uplink Shared Channel), which are used in existing LTE systems, will be used. This is for convenience of description, and similar signals, functions, etc., may be called by other names. Also, the above terms in NR correspond to NR-SS, NR-PSS, NR-SSS, NR-PBCH, NR-PRACH, etc. However, even if a signal is used in NR, it is not necessarily explicitly stated as "NR-". 【0014】 Furthermore, in the embodiments of the present invention, the duplex method may be a TDD (Time Division Duplex) method, an FDD (Frequency Division Duplex) method, or any other method (for example, a Flexible Duplex). 【0015】 Furthermore, in the embodiments of the present invention, "configuring" wireless parameters, etc., may mean that predetermined values ​​are pre-configured, or that wireless parameters notified from a base station or terminal are configured. 【0016】 (System Configuration) Figure 1 is a diagram illustrating an embodiment of the wireless communication system according to the present invention. A wireless communication system according to an embodiment of the present invention includes a base station 10 and a terminal 20, as shown in Figure 1. Although Figure 1 shows one base station 10 and one terminal 20, this is an example, and there may be multiple base stations 10 and terminal 20. 【0017】 Base station 10 is a communication device that provides one or more cells and performs wireless communication with terminal 20. The physical resources of the wireless signal are defined in the time domain and the frequency domain. The time domain may be defined by the number of OFDM (Orthogonal Frequency Division Multiplexing) symbols, and the frequency domain may be defined by the number of subcarriers or resource blocks. In addition, the TTI (Transmission Time Interval) in the time domain may be a slot, or the TTI may be a subframe. 【0018】 The base station 10 transmits synchronization signals and system information to the terminal 20. The synchronization signals are, for example, NR-PSS and NR-SSS. The system information is transmitted, for example, via NR-PBCH and is also called broadcast information. The synchronization signals and system information may also be called SSB (SS / PBCH block). As shown in Figure 1, the base station 10 transmits control signals or data to the terminal 20 via DL (Downlink) and receives control signals or data from the terminal 20 via UL (Uplink). Both the base station 10 and the terminal 20 are capable of transmitting and receiving signals using 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. In addition, both the base station 10 and the terminal 20 may communicate via secondary cells (SCell) and primary cells (PCell) using CA (Carrier Aggregation). Furthermore, terminal 20 may communicate via the primary cell of base station 10 and the primary secondary cell group cell (PSCell: Primary SCG Cell) of other base stations 10 using DC (Dual Connectivity). 【0019】 Terminal 20 is a communication device equipped with wireless communication capabilities, such as a smartphone, mobile phone, tablet, wearable device, or M2M (Machine-to-Machine) communication module. As shown in Figure 1, Terminal 20 receives control signals or data from the base station 10 via DL and transmits control signals or data to the base station 10 via UL, thereby utilizing various communication services provided by the wireless communication system. Terminal 20 also receives various reference signals transmitted from the base station 10 and performs propagation path quality measurements based on the reception results of these reference signals. Terminal 20 may also be referred to as UE and base station 10 as gNB. 【0020】 Figure 2 shows an example configuration of a wireless communication system according to an embodiment of the present invention. Figure 2 shows an example configuration of a wireless communication system when NR-DC (NR-Dual connectivity) is implemented. As shown in Figure 2, a base station 10A that acts as the MN (Master Node) and a base station 10B that acts as the SN (Secondary Node) are provided. Base stations 10A and 10B are each connected to the core network. Terminal 20 communicates with both base station 10A and base station 10B. 【0021】 A cell group provided by base station 10A, which is an MN (Mobile Network Unit), is called an MCG (Master Cell Group), and a cell group provided by base station 10B, which is an SN (Stationary Network Unit), is called an SCG (Secondary Cell Group). In a DC (Data Center), an MCG consists of one PCell and one or more SCells, and an SCG consists of one PSCell (Primary SCell) and one or more SCells. In this specification, CC (Component Carrier) and cell may be used synonymously. Also, PCell and PSCell may be referred to as SPCell. 【0022】 In the wireless communication system of this embodiment, when using an unlicensed band, LBT (Listen Before Talk) is performed. The base station 10 or terminal 20 senses the signal and transmits if the sensing result is idle, and refrains from transmitting if the sensing result is busy. Note that LBT is not always performed in the unlicensed band, and there may be cases where LBT is not performed in the unlicensed band. 【0023】 Figure 3 shows an example of frequency ranges according to an embodiment of the present invention. The NR specification of 3GPP Release 17 considers operating in frequency bands above 52.6 GHz, for example. As shown in Figure 3, the currently defined frequency range FR (Frequency range) 1 is from 410 MHz to 7.125 GHz, with a Subcarrier Spacing (SCS) of 15, 30, or 60 kHz and a bandwidth of 5 MHz to 100 MHz. FR2-1 is from 24.25 GHz to 52.6 GHz, with an SCS of 60, 120, or 240 kHz and a bandwidth of 50 MHz to 400 MHz. Furthermore, the newly introduced frequency band, FR2-2, is from 52.6 GHz to 71 GHz. 【0024】 In the newly operated frequency band FR2-2, up to 64 SSB beams may be supported in both the licensed and unlicensed bands. Furthermore, in the initial Bandwidth Part (BWP), 120kHz SCS for SSB and 120kHz SCS for initial access signals and channels may be supported. 【0025】 In addition to 120kHz SCS, SSB at 480kHz SCS may be supported. This SSB may enable initial access to support CORESET (Control Resource Set)#0 / Type0-PDCCH included in the MIB. However, the following limitations may apply: For example, the entry number of the synchronization raster may be restricted. Also, in the case of 480kHz SCS SSB, only 480kHz SCS CORESET#0 / Type0-PDCCH may be supported. Furthermore, SSB-CORESET multiplexing pattern 1 (SS / PBCH block and CORESET multiplexing pattern 1) may be preferred. 【0026】 It may be supported to uniquely identify the ANR (Automatic Neighbor Relation) and PCI (Physical Cell Identity) for detecting 120kHz SCS, 480kHz SCS, and 960kHz SCS SSBs. It may also be supported to support CORESET#0 / Type0-PDCCH included in the MIB of 120kHz SCS, 480kHz SCS, and 960kHz SSBs. Furthermore, it may be supported to support one CORESET#0 / Type0-PDCCH SCS per SSB SCS. For example, {SSB SCS, CORESET#0 / Type0-PDCCH SCS} may support {120,120}, {480,480}, and {960,960}. 【0027】 Figure 4 shows the relationship between SCS and symbol length. As shown in Figure 4, as the SCS widens, the symbol length (duration of the symbol) decreases. Also, assuming that the number of symbols per slot remains constant (i.e., 14 symbols), as the SCS widens, the slot length decreases. 【0028】 In a wireless communication system, terminal 20, upon receiving data from base station 10 via PDSCH, transmits HARQ-ACK information to base station 10 as feedback, which is HARQ-ACK information bit values ​​set in a HARQ-ACK codebook (sometimes referred to as HARQ-ACK CB). Note that transmitting / receiving data via PDSCH can be rephrased as transmitting / receiving PDSCH. The information transmitted to base station 10 as feedback may also be called a HARQ-ACK codebook. Generating the information to be transmitted to base station 10 as feedback may be expressed as generating a HARQ-ACK codebook. 【0029】 However, as mentioned above, if the slot length is shortened by using high frequency bands, it is expected that multiple PDSCHs will be scheduled with a single DCI scheduling. Hereafter, scheduling multiple PDSCHs with a single DCI scheduling may be referred to as multi-PDSCH scheduling. 【0030】 (Regarding the generation of Type 1 HARQ-ACK codebooks) This section describes how to generate a Type 1 HARQ-ACK codebook. The following explanation assumes the use of PUCCH as the channel for transmitting HARQ-ACK information, but PUSCH may also be used as the channel. 【0031】 First, the general flow consists of the following steps A and B. 【0032】 In step A, terminal 20 determines HARQ-ACK occasions that indicate possible PDSCHs to receive. The bit index in the HARQ-ACK occasions represents the reception opportunity for each PDSCH. The HARQ-ACK occasions may also be called the HARQ-ACK codebook. 【0033】 In step B, terminal 20 determines the O in the HARQ-ACK occasions determined in step A. ACK The value of each HARQ-ACK information bit is determined. For example, if data is successfully received during a reception opportunity, that bit will become an ACK bit. 【0034】 Then, terminal 20 transmits HARQ-ACK information to base station 10, in which the value of the HARQ-ACK information bit is set to the bit position of each reception opportunity. 【0035】 Step A consists of Step A-1 and Step A-2, as described below. 【0036】 <Step A-1> Terminal 20 determines the PDSCH slot window based on the configured K1 set. 【0037】 The K1 set C(K1) = {1, 2, 3, 4}, and the uplink and downlink neurology are equal (μ DL =μ UL Figure 5 shows an example of a PDSCH slot window in the case of ). 【0038】 Figure 5 is the first diagram illustrating the method for determining the PDSCH slot window. In Figure 5, the upper row shows the serving cell c that receives the PDSCH, and the lower row shows the PUCCH cell. The same applies to subsequent figures. 【0039】 K1 represents the distance (number of slots) between the slot that received the PDSCH and the slot that sent the PUCCH, as viewed from the PUCCH cell. In other words, K1 is a parameter value that indicates the timing of feedback transmission. 【0040】 In Figure 5, since PUCCH is transmitted in slot n+4 of the PUCCH cell, slots n to n+3 of serving cell c are determined as the PDSCH slot window (the time window of slots that may receive PDSCH). 【0041】 Figure 6 is a second diagram illustrating the method for determining the PDSCH slot window. The K1 set C(K1) = {1, 2, 3, 4, 5}, and μ DL >μ ULFigure 7 shows an example of the PDSCH slot window in this case. In Figure 7, since PUCCH is transmitted in slot n+5 of the PUCCH cell, slots 2n to 2n+9 of serving cell c are determined as the PDSCH slot window (the time window of slots that may receive PDSCH). For example, slot 2n of the serving cell corresponds to the time position of slot n of the PUCCH cell, so based on the slot length in the PUCCH cell, slot n+5, which is 5 slots later (K1=5), becomes the slot that transmits PUCCH. 【0042】 <Step A-2> In step A-2, terminal 20 determines the candidate PDSCH reception occasions for each slot in the window determined in step A-2. Specifically, it executes the procedures S1 to S3 as follows. 【0043】 In S1, candidate PDSCH reception occasions are associated with a set R (set of rows) in the TDRA (Time Domain Resource Allocation) table. 【0044】 In S2, duplicate portions of the allocation information (SLIV) in the TDRA table that are configured with ULs set by TDD-UL-DL-ConfigurationCommon and TDD-UL-DL-ConfigDedicated are removed. 【0045】 In S3, for candidate PDSCH reception occasions that overlap in the time domain, the candidate PDSCH reception occasions are determined according to predetermined rules. 【0046】 Figure 7 is a diagram illustrating the method for determining candidate reception opportunities in each slot. Referring to Figure 7, an example of determining candidate PDSCH reception occasions in a given slot n is explained. In the TDRA table shown in Figure 7(a), each row corresponds to one SLIV (assignment information: indicating the starting symbol and symbol length in the slot), and there are nine types, each identified by the row index (RI). The RI is specified by the DCI, and terminal 20 recognizes the specified SLIV as the actual PDSCH reception occasion. K1 is also specified by the DCI. 【0047】 (b) shows all SLIVs for RIs specified in the TDRA table, arranged in slots. For convenience of notation, three slots are shown, but each slot contains nine possible SLIVs. 【0048】 Here, as shown in (c), RI2, RI3, and RI8 are excluded from candidate PDSCH reception occasions because they overlap with semistatic UL symbols. 【0049】 After excluding RI2, RI3, and RI8, the remaining SLIVs are RI0, RI1, and RI4-7. As shown in (d) and (e), RI0 and RI4 overlap, and RI1 overlaps with RI5 and RI6. However, according to the predetermined rules, RI0 and RI4 become one occasion as candidate PDSCH reception occasions and are assigned index 0, and RI1 and RI5 also become one occasion as candidate PDSCH reception occasions and are assigned index 1. As a result, the candidate PDSCH reception occasions in that slot (M A,c ) becomes {0,1,2,3}. 【0050】 Figure 8 shows an example of a Type 1 HARQ-ACK codebook. As the above processing is performed on each slot, the M consisting of candidate PDSCH reception occasions for each slot in the PDSCH slot window is shown in Figure 8. A,cThis is generated. 【0051】 (Multi-PDSCH / PUSCH scheduling) Next, we will discuss multi-PDSCH scheduling. 【0052】 The TDRA table used in multi-PDSCH scheduling is, for example, a table with one or more SLIVs in each row. Furthermore, the multiple PDSCHs scheduled by a single DCI may or may not be temporally consecutive. 【0053】 More specifically, the TDRA table is expanded so that each row can represent up to eight PDSCHs. Each PDSCH has a separate SLIV and mapping type. The number of PDSCHs scheduled in a single DCI is implicitly indicated by the number of valid SLIVs in the rows of the TDRA table, which is notified by the DCI. 【0054】 (HARQ-ACK in multi-PDSCH scheduling in Release 16) In this embodiment, terminal 20 can transmit HARQ-ACK feedback to multiple PDSCHs scheduled by multi-PDSCH scheduling using the same PUCCH. 【0055】 In other words, HARQ-ACK information corresponding to multiple PDSCHs scheduled by a single DCI that schedules multiple PDSCHs is multiplexed into a single PUCCH in the slot determined based on K1. 【0056】 Figure 9 illustrates HARQ-ACK in multi-PDSCH scheduling. Here, as shown in Figure 9, K1 is the slot offset between the slot in the last PDSCH scheduled by the DCI and the slot carrying the HARQ-ACK information corresponding to the multiple scheduled PDSCHs. 【0057】 K1 is a value notified by the PDSCH-to-HARQ_feedback timing indicator field in DCI. If the PDSCH-to-HARQ_feedback timing indicator field is not present in DCI, K1 is a value provided by dl-DataToUL-ACK. 【0058】 Furthermore, in this embodiment, there are the following options 1, 1a, and 2 for generating a Type 1 HARQ-ACK codebook corresponding to a DCI that schedules multiple PDSCHs. 【0059】 Option 1: Terminal 20 determines candidate PDSCH reception occasions based on each SLIV in each row of the TDRA table and the extension of the K1 set. 【0060】 Option 1a: Terminal 20 determines candidate PDSCH reception occasions based on each SLIV in each row of the TDRA table. 【0061】 Option 2: Terminal 20 determines candidate PDSCH reception occasions based on the last SLIV in each row of the TDRA table. 【0062】 (Regarding the generation of Type 2 HARQ-ACK codebooks) Next, we will discuss the generation of Type 2 HARQ-ACK codebooks in Release 16. 【0063】 Figure 10 illustrates how to generate a Type 2 HARQ-ACK codebook. In the example in Figure 10, terminal 20 receives DCIs in cells #0 and #2 on PDCCH occasion #1. Terminal 20 receives a DCI in cell #1 on PDCCH occasion #2. Terminal 20 receives a DCI in cell #2 on PDCCH occasion #3. Terminal 20 receives a DCI in cells #1 and #2 on PDCCH occasion #4. 【0064】 In Figure 10, the values ​​in parentheses in the DCI indicate the Downlink Assignment Indicator (Index(DAI)) field. The DAI field contains a Counter-DAI (Counter-DAI(C-DAI)) and a Total-DAI (Total-DAI(T-DAI)). 【0065】 The DAI counter is the value obtained by counting the transmitted DCIs 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. 【0066】 Terminal 20 determines the bit position of the HARQ-ACK information for the PDSCH scheduled by DCI (the bit position in the Type 2 HARQ-ACK codebook) based on the bit positions derived from the counter DAI and total DAI notified by DCI, and sets the HARQ-ACK information at that bit position. By transmitting the HARQ-ACK codebook generated in this way to base station 10, base station 10 can determine which PDSCH the HARQ-ACK information is for and perform appropriate retransmissions, etc. 【0067】 Even when transmitting one PDSCH with one DCI, if spatial multiplexing is performed, the number of TBs (transport blocks) (which may also be the number of codewords) will be, for example, two. In other words, the number of HARQ-ACK bits for that DCI will be two. Also, if spatial bundling is performed, even if the number of TBs is two, the number of HARQ-ACK bits will be one. Furthermore, when performing CBG (code block group) based transmission, since ACK / NACK is returned for each CBG within a TB, the number of HARQ-ACK bits will be the number of CBGs per TB. From this perspective, terminal 20 determines the number of HARQ-ACK bits for each PDSCH reception based on the following information elements that terminal 20 receives from base station 10. 【0068】 ·maxNrofCodeWordsScheduledByDCI ·harq-ACK-SpatialBundlingPUCCH ·PDSCH-CodeBlockGroupTransmission (About CBG) 【0069】 Figure 11 shows an example of the configuration of a Type 2 HARQ-ACK codebook. When CBG-based transmission is configured in a cell within a PUCCH cell group, a Type 2 HARQ-ACK codebook is generated as a concatenation of the two subcodebooks shown in Figure 11. 【0070】 The first subcodebook is a codebook that stores bits of HARQ-ACK information for TB-based PDSCH receptions, SPS PDSCH releases, SPS PDSCH receptions, and DCI format 1_1 indicating SCell dormancy. 【0071】 The second subcodebook is a codebook that stores the bits of HARQ-ACK information for CBG-based PDSCH reception in the above cell. 【0072】 (Regarding the agreements made in Release 17) Furthermore, in Release 17, the following is agreed upon: By setting {SLIV, mapping type, scheduling offset K0 (or K2)} for each PDSCH (or PUSCH) in a row of a TDRA table, it is possible to indicate that a row of a TDRA table is in a contiguous or non-contiguous slot. 【0073】 (Type 1 HARQ-ACK codebook for multi-PDSCH scheduling) To enhance the generation of Type 1 HARQ-ACK codebooks for DCI, which can schedule multiple PDSCHs, the set of candidate PDSCH receive opportunities corresponding to UL slots with HARQ-ACK transmissions is determined based on a set of downlink slots and a set of SLIVs corresponding to each downlink slot belonging to the set of downlink slots. 【0074】 A set of downlink slots includes all single downlink slots that can be scheduled by any row index r in the DCI's TDRA table, which directs the uplink slots as HARQ-ACK feedback timings. 【0075】 The set of SLIVs corresponding to a downlink slot (belonging to the set of downlink slots) includes at least all SLIVs that can be scheduled within the downlink slot by any row index r in the DCI's TDRA table that designates the uplink slot as HARQ-ACK feedback timing. 【0076】 Furthermore, the following are listed as areas for future consideration in Release 17. • Further details on truncating the SLIV set The impact of allowing multiple PDSCHs to be received in one slot. For example, processing duplicate SLIVs from different rows in the same downlink slot and different downlink slots. • Impact on time domain bundles, if supported. 【0077】 (Type 2 HARQ-ACK codebook for multi-PDSCH scheduling) Next, we will discuss the Type 2 HARQ-ACK codebook for multi-PDSCH scheduling in Release 17. In Release 17, it has been agreed that Proposal 1 (where C-DAI / T-DAI are counted per DCI) will be adopted to generate a Type 2 HARQ-ACK codebook for DCIs that can schedule multiple PDSCHs. 【0078】 If Proposal 1 (where C-DAI / T-DAI are counted per DCI) is adopted to generate a Type 2 HARQ-ACK codebook for DCIs that can schedule multiple PDSCHs, it is agreed that at least two subcodebooks will be generated for each PUCCH cell group. 【0079】 The first subcodebook is used in the following cases: • DCI is not configured with CBG-based scheduling and consists of TDRA tables, each containing rows with a single SLIV. • DCI that is not configured with CBG-based scheduling, consists of a TDRA table containing at least one row with multiple SLIVs, and schedules only a single PDSCH. 【0080】 The second subcodebook is used in the following cases: • DCI consisting of a TDRA table with at least one row containing multiple SLIVs, and scheduling multiple PDSCHs. 【0081】 Regarding the second subcodebook in Release 17, the following points are subject to future consideration. • How to adjust the size of HARQ-ACK feedback to accommodate different DCIs (if necessary) • Can the HARQ-ACK bits of the two PDSCHs scheduled by this DCI be included in the first subcodebook? 【0082】 Furthermore, regarding subcodebooks in Release 17, the following points are subject to future consideration. • Release of SPS PDSCH, instruction to pause SCell without scheduled PDSCH. 【0083】 Furthermore, in Release 17, the following are matters for future consideration. • Two or three subcodebooks when CBG is configured for serving cells in a PUCCH cell group • The impact of time-domain bundling, if supported. For example, the number of subcodebooks containing a single codebook when all A / N bits are bundled into one bit per DCI. 【0084】 To generate a Type 2 HARQ-ACK codebook for DCIs that can schedule multiple PDSCHs, the HARQ-ACK bits corresponding to instructions for SPS-PDSCH release or suspension of SCells without scheduled PDSCHs belong to the first subcodebook. 【0085】 (Regarding the disabling of HARQACK) Next, we will discuss the HARQ-ACK disabling being considered in Release 17. For the Type 2 HARQ-ACK codebook for Non-Terrestrial Networks (NTN), and for DCI of PDSCHs using feedback-enabled HARQ processes, C-DAI and T-DAI are values ​​that count only feedback-enabled processes (i.e., processes that are not disabled). 【0086】 In other words, terminal 20 does not need to send a HARQ-ACK for the disabled HPN (HARQ Processor Number). 【0087】 Whether DCIs that signal the release of SPS and other DCIs are included in the C-DAI and T-DAI counts remains a subject for future investigation. 【0088】 Furthermore, for DCIs in PDSCH that use a HARQ process with feedback disabled, the Type 2 HARQ-ACK codebook supports only one of the following options: 【0089】 <Option 1> C-DAI and T-DAI are the number of processes for which feedback has been enabled, even though they have not been incremented, and are taken into consideration by terminal 20 for the generation of type 2 HARQ-ACK codebooks. 【0090】 <Option 2> Regardless of the values ​​for generating the Type 2 HARQ-ACK codebook, the C-DAI and T-DAI are ignored by terminal 20. 【0091】 Furthermore, in the case of a Type 1 HARQ-ACK codebook, terminal 20 consistently reports a NACK only for HARQ processes where feedback is disabled, regardless of the corresponding PDSCH decoding result. 【0092】 (Regarding related terminal capability information) Next, we will describe conventional terminal capability information related to this embodiment. 【0093】 Figure 12 shows an example of terminal capability information related to multi-PDSCH scheduling. The functional group (FG) for multi-PDSCH scheduling with a subcarrier spacing of 120 kHz targets the 52.6–71 GHz frequency band, but whether or not to extend it to other frequency bands is under consideration. For example, this FG may target the 24–52.6 GHz frequency band. 【0094】 Figure 13 shows an example of terminal capability information regarding the disabling of HARQ-ACK codebooks in NR's non-terrestrial network. Different Function Groups (FGs) are defined for Type 1 and Type 2 HARQ-ACK codebooks in NR's non-terrestrial network. Terminal capability information regarding the disabling of HARQ-ACK codebooks in each FG is a subject for future investigation. 【0095】 Figure 14 shows an example of terminal capability information regarding the disabling of the HARQ-ACK codebook in NR's Multicast and Broadcast Service. Different Function Groups (FGs) are defined for the HARQ-ACK codebook in NR's Multicast and Broadcast Service (MBS) depending on the notification method for enabling / disabling it. 【0096】 (Previous problems) Traditionally, there has been a problem in that the combined operation of multi-PDSCH scheduling and HARQ feedback disabling has not been considered. Specifically, there is a problem in that it is unclear whether it is permissible to set both HARQ feedback disabling and multi-PDSCH scheduling for a particular HARQ process. Furthermore, if simultaneous settings are permitted, there is a problem in that it is unclear how this will affect the generation of the HARQ-ACK codebook. 【0097】 (Summary of this embodiment) Therefore, this embodiment describes an operation that combines multi-PDSCH scheduling and the disabling of HARQ feedback. Below, specific examples, from Example 1 to Example 6, will be described. 【0098】 (Basic operation) Figure 15 shows an example of a basic procedure according to an embodiment of the present invention. 【0099】 In S100, terminal 20 transmits capability information (UE capability) to base station 10. Based on this capability information, base station 10 can determine, for example, the content of the information to be transmitted to terminal 20 in S101 and S102 below. 【0100】 In S101, the base station 10 sends configuration information to the terminal 20 via an RRC message, and the terminal 20 receives the configuration information. This configuration information includes, for example, the K1 set and the TDRA table, as described later. The K1 set and the TDRA table may be notified to the terminal 20 from the base station 10, or they may be predetermined in the specifications, etc., and the base station 10 and the terminal 20 may use the predetermined ones. The TDRA table may also be called time domain resource allocation configuration information. 【0101】 In S102, base station 10 transmits scheduling (allocation information) for multiple PDSCHs to terminal 20 via DCI, and terminal 20 receives the DCI. The DCI also includes information about uplink resources for transmitting HARQ-ACK information. 【0102】 In S103, terminal 20 receives PDSCH based on scheduling information in DCI, and in S104 transmits HARQ-ACK information to base station 10. Base station 10 receives the HARQ-ACK information. 【0103】 (Example 1) This embodiment describes an example that clarifies whether it is permitted to configure both HARQ feedback disabling and multi-PDSCH scheduling for a specific HARQ process. 【0104】 <Plan 1> Terminal 20 may assume that multi-PDSCH scheduling is set for the cell and that HARQ feedback is not disabled for the HPN of the same cell. 【0105】 Furthermore, terminal 20 may assume that multi-PDSCH scheduling is set for the cell and that HARQ feedback is not disabled for any HPN in any cell within the same PUCCH cell group. 【0106】 Note that "multi-PDSCH scheduling is configured" may mean that a TDRA table containing multiple SLIVs in at least one row is configured. 【0107】 <Plan 2> Terminal 20 may be configured to disable HARQ feedback, and it may be assumed that the HPN is not assigned to a PDSCH scheduled by the multi-PDSCH scheduling DCI. 【0108】 This may also mean that HPNs configured to disable HARQ feedback should not be scheduled with multi-PDSCH scheduling DCIs, but rather with single-PDSCH scheduling DCIs. 【0109】 <Plan 3> Terminal 20 may assume that multiple (active) PDSCHs are scheduled by a single DCI, and that the HPN of any of the multiple scheduled PDSCHs is not configured to disable HARQ feedback. 【0110】 This may mean that if a multi-PDSCH scheduling DCI schedules only one (active) PDSCH, the HPN of that single (active) PDSCH can be set to disable HARQ feedback. 【0111】 Furthermore, this may also mean that if a multi-PDSCH scheduling DCI schedules multiple (active) PDSCHs, the HPNs of all (active) PDSCHs can be configured to enable HARQ feedback. 【0112】 <Plan 4> If multiple (active) PDSCHs are scheduled by a single DCI, it may be permitted for the HPN of any of the scheduled PDSCHs to be configured to disable HARQ feedback. 【0113】 Furthermore, if multiple (active) PDSCHs are scheduled by a single DCI, terminal 20 may assume that the HPNs of the multiple (active) PDSCHs have the same HARQ feedback enable / disable setting. 【0114】 This may mean that an error case exists if HARQ feedback is enabled in some HPNs of multiple (valid) PDSCHs, while HARQ feedback is disabled in other HPNs of multiple (valid) PDSCHs. 【0115】 Terminal 20 may report limited terminal capability information to base station 10 as shown in one of the following options. 【0116】 <Option 1> The terminal capability information of FG24-1d may be restricted to use in terrestrial cells and / or unicast transmission. 【0117】 <Option 2> FG26-6 (and / or 26-6a) may be restricted to cases where multi-PDSCH scheduling is not configured. Note that "multi-PDSCH scheduling is not configured" may mean "FG24-1d is not supported." 【0118】 <Option 3> FG33-2a (and 33-2b) may be restricted to cases where multi-PDSCH scheduling is not configured. Note that "multi-PDSCH scheduling is not configured" may mean "FG24-1d is not supported." 【0119】 <Option 4> The HPN used for multi-PDSCH scheduling may be restricted to unicast transmissions. 【0120】 <Option 5> HPNs used for multicast transmission may be made unavailable for multi-PDSCH scheduling. 【0121】 Options 1 through 3 can achieve the same effect as Proposal 1 mentioned above. Furthermore, options 4 and 5 can achieve the same effect as Proposal 2 mentioned above. 【0122】 Furthermore, FG24-1d may also be defined as "a terminal function for supporting multi-PDSCH scheduling." 【0123】 Furthermore, FG26-6 (and / or 26-6a) may also be "a terminal function to support the disabling of HARQ feedback (in the case of NTN)." 【0124】 Furthermore, FG33-2a (and 33-2b) may also be "a terminal function to support the disabling of HARQ feedback (in the case of MBS)." 【0125】 This embodiment makes it possible to clarify whether it is permitted to disable HARQ feedback and enable multi-PDSCH scheduling for a specific HARQ process. 【0126】 (Example 2) This embodiment describes an example of how HARQ feedback operates when multi-PDSCH scheduling and HARQ feedback are disabled. 【0127】 The following explains the possible cases when both multi-PDSCH scheduling and HARQ feedback are disabled (in the same cell). 【0128】 <Case A> When terminal 20 receives a single PDSCH scheduled by a single PDSCH scheduling DCI, it may perform one of the following optional actions: 【0129】 <Option A-1> Terminal 20 may be required to report a HARQ-ACK regardless of whether the HPN is configured to enable or disable HARQ feedback. In the case of an HPN where HARQ feedback is disabled, terminal 20 may determine the ACK / NACK based on the actual decoding result. 【0130】 <Option A-2> Terminal 20 may decide whether or not to report a HARQ-ACK based on whether HPN is configured to enable or disable HARQ feedback. 【0131】 <Case B> Terminal 20 may perform one of the following optional actions if a single (valid) PDSCH scheduled by the Multi-PDSCH Scheduling DCI is transmitted. 【0132】 <Option B-1> Terminal 20 may perform the same actions as option A-1 in case A. 【0133】 <Option B-2> Terminal 20 may perform the same operation as option A-2 in case A. 【0134】 <Case C> If terminal 20 receives multiple (valid) PDSCHs scheduled by the Multi-PDSCH Scheduling DCI, terminal 20 may perform one of the following optional actions: 【0135】 <Option C-1> Terminal 20 may be required to report HARQ-ACKs for all PDSCHs, regardless of whether the HPN of the PDSCH is configured to enable or disable HARQ feedback. In the case of an HPN where HARQ feedback is disabled, terminal 20 may determine the ACK / NACK based on the actual decoding result. 【0136】 <Option C-2> Terminal 20 may be required to report HARQ-ACKs for all PDSCHs scheduled by a single DCI if any PDSCH's HPN is set to enable HARQ feedback. Conversely, terminal 20 may not be required to report HARQ-ACKs for all PDSCHs if all PDSCHs' HPNs are set to disable HARQ feedback. 【0137】 Furthermore, if any of the PDSCH's HPNs support HARQ, and the HPN is set to disable HARQ feedback, terminal 20 may determine ACK / NACK based on the actual decoding result. Also, if all PDSCH HPNs are set to disable HARQ feedback, terminal 20 may report nothing or report a NACK, regardless of the actual decoding result. 【0138】 <Option C-3> Terminal 20 does not have to report HARQ-ACKs for all PDSCHs scheduled by a single DCI if the HPN of any PDSCH is set to disable HARQ feedback. Alternatively, terminal 20 may report HARQ-ACKs for all PDSCHs if the HPNs of all PDSCHs are set to enable HARQ feedback. 【0139】 Furthermore, if any of the HPNs of the PDSCHs are set to disable HARQ feedback, terminal 20 may either not report anything or report a NACK for each PDSCH that includes an HPN set to enable HARQ feedback, regardless of the actual decoding result. 【0140】 <Option C-4> Terminal 20 may decide whether or not to report a HARQ-ACK for each PDSCH based on whether the HPN is configured to enable or disable HARQ feedback. In the case of an HPN where HARQ feedback is disabled, terminal 20 may report nothing or report a NACK, regardless of the actual decoding result. 【0141】 Let's explain a specific example of Case C mentioned above. 【0142】 Figure 16 is the first figure showing a specific example relating to Case C of Embodiment 2 of the present invention. It assumes that eight PDSCHs are scheduled by one PDCCH. HPN1 to 8 are assigned to each PDSCH in ascending order. Enabling / disabling HARQ feedback is as follows: 【0143】 Enabled: HPN1 / 2 / 3 / 4 Invalid: HPN5 / 6 / 7 / 8 【0144】 Figure 17 is a second diagram showing a specific example related to Case C of Embodiment 2 of the present invention. Figure 17 shows the operating results of each option in Case C. "A / N" means that ACK or NACK is reported. "A / N not reported" means that nothing is reported. 【0145】 Any combination of options A-1 / A-2 in Case A, options B-1 / B-2 in Case B, and options C-1 / C-2 / C-3 / C-4 in Case C is possible. The most promising combination is as follows: Option A-1 + Option B-1 + Option C-1 => Option 1 Option A-2 + Option B-1 + Option C-1 => Option 2 Option A-2 + Option B-2 + Option C-1 => Option 3 Option A-2 + Option B-2 + Option C-2 => Option 4 Option A-2 + Option B-2 + Option C-3 => Option 5 Option A-2 + Option B-2 + Option C-4 => Option 6 【0146】 Terminal 20, operating under Option 1, must report a HARQ-ACK to the PDSCH in either case, regardless of whether the HPN is configured to enable or disable HARQ feedback. 【0147】 In case A, terminal 20, which operates under option 2, decides whether or not to report a HARQ-ACK based on whether the HPN is configured to enable or disable HARQ feedback. 【0148】 Furthermore, terminal 20 operating under Option 2 will report a HARQ-ACK in cases B and C, regardless of whether the HPN is configured to enable or disable HARQ feedback. 【0149】 In case A, terminal 20 performing option 3 determines whether or not to report a HARQ-ACK based on whether HPN is configured to enable or disable HARQ feedback. 【0150】 Furthermore, in case B, terminal 20 performing option 3 will decide whether or not to report a single (valid) PDSCH HARQ-ACK based on whether HPN is configured to enable or disable HARQ feedback. 【0151】 Furthermore, in case C, terminal 20 performing option 3 will report a HARQ-ACK regardless of whether HPN is configured to enable or disable HARQ feedback. 【0152】 In case A, terminal 20 performing option 4 determines whether or not to report a HARQ-ACK based on whether HPN is configured to enable or disable HARQ feedback. 【0153】 Furthermore, in case B, terminal 20 performing option 4 will decide whether or not to report a single (valid) PDSCH HARQ-ACK based on whether the HPN is configured to enable or disable HARQ feedback. 【0154】 Furthermore, in case C, terminal 20 operating under Option 4 will report HARQ-ACKs for all PDSCHs scheduled by a single DCI if any of the PDSCH's HPNs are set to enable HARQ feedback. Also, terminal 20 operating under Option 4 will not report HARQ-ACKs for any PDSCHs if all of the PDSCH's HPNs are set to disable HARQ feedback. 【0155】 In case A, terminal 20 performing option 5 determines whether or not to report a HARQ-ACK based on whether HPN is configured to enable or disable HARQ feedback. 【0156】 Furthermore, in case B, terminal 20 performing option 5 will decide whether or not to report a single (valid) PDSCH HARQ-ACK based on whether HPN is configured to enable or disable HARQ feedback. 【0157】 Furthermore, in case C, terminal 20 operating under Option 5 will not report HARQ-ACKs for all PDSCHs scheduled by a single DCI if the HPN of any PDSCH is set to disable HARQ feedback. Also, terminal 20 operating under Option 5 will report HARQ-ACKs for all PDSCHs if the HPNs of all PDSCHs are set to enable HARQ feedback. 【0158】 In case A, terminal 20 performing option 6 determines whether or not to report a HARQ-ACK based on whether HPN is configured to enable or disable HARQ feedback. 【0159】 Furthermore, in case B, terminal 20 performing option 6 will decide whether or not to report a single (valid) PDSCH HARQ-ACK based on whether HPN is configured to enable or disable HARQ feedback. 【0160】 Furthermore, in the case of case C, terminal 20 performing option 6 will decide whether or not to report a HARQ-ACK for each PDSCH based on whether the HPN is set to enable or disable HARQ feedback. 【0161】 This embodiment clarifies the behavior of HARQ feedback when multi-PDSCH scheduling is combined with the disabling of HARQ feedback. 【0162】 (Example 3) This embodiment describes an example in which terminal 20, operating under each option of Example 2, generates a Type 2 HARQ-ACK codebook in a manner that does not involve a time-domain bundle. Time-domain bundles will be discussed later, along with Example 5. 【0163】 For terminal 20 operating under Option 1 of Example 2, the rules specified for generating the HARQ-ACK codebook for multi-PDSCH scheduling agreed upon in Release 17 may be reused. 【0164】 In this case, terminal 20 may determine the ACK / NACK based on the actual decoding result if the HPN is configured to enable HARQ feedback. 【0165】 <Option 2, First Subcodebook> Terminal 20, which operates under Option 2 of Example 2, generates the first subcodebook as follows: 【0166】 <Option 2-1> The DCI related to the first subcodebook may be as follows: • Single PDSCH scheduling DCI with HPN configured to enable HARQ feedback. • Multi-PDSCH scheduling DCI that schedules only one (active) PDSCH. • DCIs that release SPS, DCIs that instruct Scell ​​to pause (and other DCIs that do not schedule PDSCH) 【0167】 The structure of the first subcodebook may be as follows: ACK / NACK for single PDSCH scheduling DCI that schedules a PDSCH with an HPN configured to have HARQ feedback enabled. ACK / NACK for multi-PDSCH scheduling DCI that schedules only one (valid) PDSCH. ACK / NACK to DCIs that release SPS, DCIs that instruct Scell ​​to pause (and other DCIs that do not schedule PDSCH) 【0168】 The C-DAI / T-DAI included in the first subcodebook may be as follows: In the case of a single PDSCH scheduling DCI that schedules a PDSCH with an HPN configured to enable HARQ feedback, a multi-PDSCH scheduling DCI that schedules only one (active) PDSCH, and other DCIs that do not schedule a PDSCH (e.g., a DCI that releases SPS, a DCI that instructs Scells to pause, etc.), the C-DAI / T-DAI included in the first subcodebook is the number of single PDSCH scheduling DCIs that schedule a PDSCH with an HPN configured to enable HARQ feedback, a multi-PDSCH scheduling DCI that schedules only one (active) PDSCH, and other DCIs that do not schedule a PDSCH (e.g., a DCI that releases SPS, a DCI that instructs Scells to pause, etc.). 【0169】 For a single PDSCH scheduling DCI that schedules a PDSCH with an HPN configured to disable HARQ feedback, the C-DAI / T-DAI included in the first subcodebook may be one of the following: 【0170】 <Plan 1> The C-DAI / T-DAI included in the first subcodebook may be the sum of a single PDSCH scheduling DCI that schedules a PDSCH with an HPN configured to enable HARQ feedback, a multi-PDSCH scheduling DCI that schedules only one (active) PDSCH, and other DCIs that do not schedule a PDSCH (e.g., a DCI that releases an SPS, a DCI that instructs a Scell ​​to pause, etc.). 【0171】 <Plan 2> Terminal 20 may ignore the C-DAI and T-DAI regardless of the values ​​for generating a Type 2 HARQ-ACK codebook. 【0172】 <Option 2-2> The DCI related to the first subcodebook may be as follows: • Single PDSCH scheduling DCI • Multi-PDSCH scheduling DCI that schedules only one (active) PDSCH. • DCIs that release SPS, DCIs that instruct Scell ​​to pause (and other DCIs that do not schedule PDSCH) 【0173】 The structure of the first subcodebook may be as follows: ACK / NACK for single PDSCH scheduling DCI that schedules a PDSCH with an HPN configured to have HARQ feedback enabled. NACK for single PDSCH scheduling DCI with HPN configured to disable HARQ feedback ACK / NACK for multi-PDSCH scheduling DCI that schedules only one (valid) PDSCH. ACK / NACK to DCIs that release SPS, DCIs that instruct Scell ​​to pause (and other DCIs that do not schedule PDSCH) 【0174】 The C-DAI / T-DAI included in the first subcodebook may be the number of DCIs related to the first subcodebook, including single PDSCH scheduling DCIs that schedule PDSCHs, multi-PDSCH scheduling DCIs that schedule only one (active) PDSCH, and other DCIs that do not schedule PDSCHs (e.g., DCIs that release SPS, DCIs that instruct Scells to pause, etc.). 【0175】 <Option 2, Second Subcodebook> The second subcodebook of Option 2 may include the following: 【0176】 The second subcodebook of Option 2 may include a multi-PDSCH scheduling DCI for scheduling multiple (valid) PDSCHs. 【0177】 Additionally, the second subcodebook of Option 2 may include HARQ-ACK information bits (M bits) for the second subcodebook included in each DCI. 【0178】 The HARQ-ACK information bits may include the following: Regardless of whether the HPN is configured to enable or disable HARQ feedback, an ACK / NACK is issued for the scheduled (enabled) PDSCH (terminal 20 determines whether an ACK or NACK is reported based on the actual decoding result, even if the HPN is configured to disable HARQ feedback). • NACK for unscheduled (or invalid) PDSCH 【0179】 M is determined by the maximum number of scheduled PDSCHs among all cells in the PUCCH cell group. 【0180】 The C-DAI and T-DAI applied to the second subcodebook of Option 2 may also be the number of multi-PDSCH scheduling DCIs that schedule multiple (valid) PDSCHs. 【0181】 <Option 3, First Subcodebook> Terminal 20, which operates according to option 3 of Example 2, generates the first subcodebook as follows: 【0182】 <Option 3-1> The DCI related to the first subcodebook may be as follows: • Single PDSCH scheduling DCI with HPN configured to enable HARQ feedback. • Multi-PDSCH scheduling DCI that schedules only one (active) PDSCH with an HPN configured to enable HARQ feedback. • DCIs that release SPS, DCIs that instruct Scell ​​to pause (and other DCIs that do not schedule PDSCH) 【0183】 The structure of the first subcodebook may be as follows: ACK / NACK for single PDSCH scheduling DCI that schedules a PDSCH with an HPN configured to have HARQ feedback enabled. ACK / NACK for multi-PDSCH scheduling DCI that schedules only one (valid) PDSCH with an HPN configured to enable HARQ feedback. ACK / NACK to DCIs that release SPS, DCIs that instruct Scell ​​to pause (and other DCIs that do not schedule PDSCH) 【0184】 The C-DAI / T-DAI included in the first subcodebook may be as follows: In the case of a single PDSCH scheduling DCI that schedules a PDSCH with an HPN configured to enable HARQ feedback, and other DCIs that do not schedule a PDSCH (e.g., a DCI that releases SPS, a DCI that instructs Scell ​​to pause, etc.), the C-DAI / T-DAI included in the first subcodebook is the number of single PDSCH scheduling DCIs that schedule a PDSCH with an HPN configured to enable HARQ feedback, a multi-PDSCH scheduling DCI that schedules only one (active) PDSCH with an HPN configured to enable HARQ feedback, and other DCIs that do not schedule a PDSCH (e.g., a DCI that releases SPS, a DCI that instructs Scell ​​to pause, etc.). 【0185】 For a single PDSCH scheduling DCI that schedules a PDSCH with an HPN configured to disable HARQ feedback, the C-DAI / T-DAI included in the first subcodebook may be one of the following: 【0186】 <Plan 1> The C-DAI / T-DAI included in the first subcodebook may be the sum of a single PDSCH scheduling DCI that schedules a PDSCH with an HPN configured to enable HARQ feedback, a multi-PDSCH scheduling DCI that schedules only one (active) PDSCH with an HPN configured to enable HARQ feedback, and other DCIs that do not schedule a PDSCH (e.g., a DCI that releases SPS, a DCI that instructs Scell ​​to pause, etc.). 【0187】 <Plan 2> Terminal 20 may ignore the C-DAI and T-DAI regardless of the values ​​for generating a Type 2 HARQ-ACK codebook. 【0188】 <Option 3-2> The DCI related to the first subcodebook may be as follows: • Single PDSCH scheduling DCI with HPN configured to enable HARQ feedback. • Multi-PDSCH scheduling DCI that schedules only one (active) PDSCH. • DCIs that release SPS, DCIs that instruct Scell ​​to pause (and other DCIs that do not schedule PDSCH) 【0189】 The structure of the first subcodebook may be as follows: ACK / NACK for single PDSCH scheduling DCI that schedules a PDSCH with an HPN configured to have HARQ feedback enabled. ACK / NACK for multi-PDSCH scheduling DCI that schedules only one (valid) PDSCH with an HPN configured to enable HARQ feedback. NACK for single PDSCH scheduling DCI with HPN configured to disable HARQ feedback ACK / NACK to DCIs that release SPS, DCIs that instruct Scell ​​to pause (and other DCIs that do not schedule PDSCH) 【0190】 The C-DAI / T-DAI included in the first subcodebook may be as follows: In the case of a single PDSCH scheduling DCI that schedules a PDSCH with an HPN configured to enable HARQ feedback, a multi-PDSCH scheduling DCI that schedules only one (active) PDSCH, and other DCIs that do not schedule a PDSCH (e.g., a DCI that releases SPS, a DCI that instructs Scell ​​to pause, etc.), the C-DAI / T-DAI included in the first subcodebook is the number of single PDSCH scheduling DCIs that schedule a PDSCH with an HPN configured to enable HARQ feedback, a multi-PDSCH scheduling DCI that schedules only one (active) PDSCH with an HPN configured to enable HARQ feedback, and other DCIs that do not schedule a PDSCH (e.g., a DCI that releases SPS, a DCI that instructs Scell ​​to pause, etc.). 【0191】 For a single PDSCH scheduling DCI that schedules a PDSCH with an HPN configured to disable HARQ feedback, the C-DAI / T-DAI included in the first subcodebook may be one of the following: 【0192】 <Plan 1> The C-DAI / T-DAI included in the first subcodebook may be the sum of a single PDSCH scheduling DCI that schedules a PDSCH with an HPN configured to enable HARQ feedback, a multi-PDSCH scheduling DCI that schedules only one (active) PDSCH with an HPN configured to enable HARQ feedback, and other DCIs that do not schedule a PDSCH (e.g., a DCI that releases SPS, a DCI that instructs Scell ​​to pause, etc.). 【0193】 <Plan 2> Terminal 20 may ignore the C-DAI and T-DAI regardless of the values ​​for generating a Type 2 HARQ-ACK codebook. 【0194】 <Option 3-3> The DCI related to the first subcodebook may be as follows: • Single PDSCH scheduling DCI • Multi-PDSCH scheduling DCI that schedules only one (active) PDSCH. • DCIs that release SPS, DCIs that instruct Scell ​​to pause (and other DCIs that do not schedule PDSCH) 【0195】 The structure of the first subcodebook may be as follows: ACK / NACK for single PDSCH scheduling DCI that schedules a PDSCH with an HPN configured to have HARQ feedback enabled. NACK for single PDSCH scheduling DCI with HPN configured to disable HARQ feedback ACK / NACK for multi-PDSCH scheduling DCI that schedules only one (valid) PDSCH with an HPN configured to enable HARQ feedback. ACK / NACK for multi-PDSCH scheduling DCI that schedules only one (valid) PDSCH with an HPN configured to enable HARQ feedback. ACK / NACK to DCIs that release SPS, DCIs that instruct Scell ​​to pause (and other DCIs that do not schedule PDSCH) 【0196】 The C-DAI / T-DAI included in the first subcodebook may be the number of DCIs related to the first subcodebook, including single PDSCH scheduling DCIs that schedule PDSCHs, multi-PDSCH scheduling DCIs that schedule only one (active) PDSCH, and other DCIs that do not schedule PDSCHs (e.g., DCIs that release SPS, DCIs that instruct Scells to pause, etc.). 【0197】 <Option 3, Second Subcodebook> The second subcodebook for Option 3 may be the same as the second subcodebook for Option 2. 【0198】 <Option 4, Subcodebook 1> The first subcodebook for Option 4 may be the same as the first subcodebook for Option 3. 【0199】 <Option 4, Second Subcodebook> Terminal 20, which operates under option 4 of Example 2, generates the second subcodebook as follows: 【0200】 <Option 4-1> The DCI related to the second subcodebook may be as follows: Multi-PDSCH scheduling DCI that schedules multiple (enabled) PDSCHs, including at least one PDSCH with an HPN configured to enable HARQ feedback. 【0201】 The structure of the second subcodebook may be as follows: • If the HPN included in any PDSCH is set to enable HARQ feedback, ACK / NACK will be issued to the PDSCH scheduled by a single DCI. 【0202】 The C-DAI / T-DAI included in the second subcodebook may be as follows: In the case of a multi-PDSCH scheduling DCI that schedules multiple (active) PDSCHs, including at least one PDSCH with an HPN configured to enable HARQ feedback, the C-DAI / T-DAI included in the second subcodebook is the number of multi-PDSCH scheduling DCIs that schedule multiple (active) PDSCHs, including at least one PDSCH with an HPN configured to enable HARQ feedback. 【0203】 For a multi-PDSCH scheduling DCI that schedules multiple (enabled) PDSCHs with HPNs that have all HARQ feedback disabled, the C-DAI / T-DAI included in the second subcodebook may be one of the following: 【0204】 <Plan 1> The C-DAI / T-DAI included in the second subcodebook may be the number of multi-PDSCH scheduling DCIs that schedule multiple (active) PDSCHs, including at least one PDSCH with an HPN configured to enable HARQ feedback. 【0205】 <Plan 2> Terminal 20 may ignore the C-DAI and T-DAI regardless of the values ​​for generating a Type 2 HARQ-ACK codebook. 【0206】 <Option 4-2> The DCI related to the second subcodebook may be as follows: • Multi-PDSCH scheduling DCI for scheduling multiple (active) PDSCHs 【0207】 The structure of the second subcodebook may be as follows: • If the HPN included in any PDSCH is set to enable HARQ feedback, ACK / NACK will be issued to the PDSCH scheduled by a single DCI. • NACK for single PDSCH scheduling DCI when all HPNs are set to disable HARQ feedback. 【0208】 For DCIs related to the second subcodebook, the C-DAI / T-DAIs included in the second subcodebook may be the number of multi-PDSCH scheduling DCIs that schedule multiple (valid) PDSCHs. 【0209】 <Option 5, Subcodebook 1> The first subcodebook for Option 5 may be the same as the first subcodebook for Option 3. 【0210】 <Option 5, Second Subcodebook> Terminal 20, which operates under option 5 of Example 2, generates the second subcodebook as follows: 【0211】 <Option 5-1> The DCI related to the second subcodebook may be as follows: • Multi-PDSCH scheduling DCI that schedules multiple (enabled) PDSCHs with HPNs that have all HARQ feedback enabled. 【0212】 The structure of the second subcodebook may be as follows: • If the HPN included in all PDSCHs is set to enable HARQ feedback, ACK / NACK for PDSCHs scheduled by a single DCI will be enabled. 【0213】 The C-DAI / T-DAI included in the second subcodebook may be as follows: In the case of a multi-PDSCH scheduling DCI that schedules multiple (enabled) PDSCHs having HPNs with all HARQ feedback enabled, the C-DAI / T-DAI included in the second subcodebook is the number of multi-PDSCH scheduling DCIs that schedule multiple (enabled) PDSCHs having HPNs with all HARQ feedback enabled. 【0214】 For a multi-PDSCH scheduling DCI that schedules multiple (enabled) PDSCHs, including at least one PDSCH with an HPN set to disable HARQ feedback, the C-DAI / T-DAI included in the second subcodebook may be one of the following proposals: 【0215】 <Plan 1> The C-DAI / T-DAI included in the second subcodebook may also be the number of multi-PDSCH scheduling DCIs that schedule multiple (enabled) PDSCHs with HPNs that have all HARQ feedbacks enabled. 【0216】 <Plan 2> Terminal 20 may ignore the C-DAI and T-DAI regardless of the values ​​for generating a Type 2 HARQ-ACK codebook. 【0217】 <Option 5-2> The DCI related to the second subcodebook may be as follows: • Multi-PDSCH scheduling DCI for scheduling multiple (active) PDSCHs 【0218】 The structure of the second subcodebook may be as follows: · If the HPNs included in all PDSCHs are set to enable HARQ feedback, ACK / NACK for the PDSCHs scheduled by a single DCI · If the HPNs included in any PDSCHs are set to disable HARQ feedback, NACK for the PDSCHs scheduled by a single DCI 【0219】 For the DCI related to the second sub - codebook, the C - DAI / T - DAI included in the second sub - codebook may be the number obtained by counting the multi - PDSCH scheduling DCIs that schedule a plurality of (valid) PDSCHs. 【0220】 <Option 6> The terminal 20 operating according to Option 6 of Example 2 may operate according to any of the following options. 【0221】 <Option 6 - 1> The first sub - codebook of Option 6 - 1 may be the same as the first sub - codebook of Option 3. 【0222】 The DCI related to the second sub - codebook may be as follows. · Multi - PDSCH scheduling DCI that schedules a plurality of (valid) PDSCHs 【0223】 The configuration of the second sub - codebook may be as follows. · ACK / NACK for PDSCHs having HPNs with HARQ feedback enabled · NACK for PDSCHs having HPNs with HARQ feedback disabled 【0224】 For the DCI related to the second sub - codebook, the C - DAI / T - DAI included in the second sub - codebook may be the number obtained by counting the multi - PDSCH scheduling DCIs that schedule a plurality of (valid) PDSCHs. 【0225】 <Option 6-2> The first subcodebook of Option 6-2 may be the same as the first subcodebook of Option 3. 【0226】 The DCI related to the second subcodebook may be as follows: Multi-PDSCH scheduling DCI that schedules multiple (enabled) PDSCHs, including at least one PDSCH with an HPN configured to enable HARQ feedback. 【0227】 The structure of the second subcodebook may be as follows: ACK / NACK to PDSCH with HPN configured to have HARQ feedback enabled. • NACK to a PDSCH with an HPN configured to disable HARQ feedback (this PDSCH is scheduled together with another PDSCH with an HPN configured to enable HARQ feedback). 【0228】 The C-DAI / T-DAI included in the second subcodebook may be as follows: In the case of a multi-PDSCH scheduling DCI that schedules multiple (active) PDSCHs, including at least one PDSCH with an HPN configured to enable HARQ feedback, the C-DAI / T-DAI included in the second subcodebook is the number of multi-PDSCH scheduling DCIs that schedule multiple (active) PDSCHs, including at least one PDSCH with an HPN configured to enable HARQ feedback. 【0229】 For a multi-PDSCH scheduling DCI that schedules multiple (enabled) PDSCHs with HPNs that have all HARQ feedback disabled, the C-DAI / T-DAI included in the second subcodebook may be one of the following: 【0230】 <Plan 1> The C-DAI / T-DAI included in the second subcodebook may be the number of multi-PDSCH scheduling DCIs that schedule multiple (active) PDSCHs, including at least one PDSCH with an HPN configured to enable HARQ feedback. 【0231】 <Plan 2> Terminal 20 may ignore the C-DAI and T-DAI regardless of the values ​​for generating a Type 2 HARQ-ACK codebook. 【0232】 <Option 6-3> The first subcodebook of Option 6-3 may have the same configuration as the first subcodebook of Option 3, with the following additions. The added configuration will be described later. • Multi-PDSCH scheduling DCI that schedules multiple (enabled) PDSCHs, including only one PDSCH with an HPN configured to enable HARQ feedback. 【0233】 The DCI related to the second subcodebook may be as follows: Multi-PDSCH scheduling DCI that schedules multiple (enabled) PDSCHs, including multiple PDSCHs with HPNs configured to have HARQ feedback enabled. 【0234】 The structure of the second subcodebook may be as follows: ACK / NACK to PDSCH with HPN configured to have HARQ feedback enabled. • NACK to a PDSCH with an HPN configured to disable HARQ feedback (this PDSCH is scheduled together with several other PDSCHs with HPNs configured to enable HARQ feedback). 【0235】 The C-DAI / T-DAI included in the second sub-codebook may be as follows. That is, in the case of multi-PDSCH scheduling DCI that schedules a plurality of (valid) PDSCHs including a plurality of PDSCHs having an HPN with HARQ feedback enabled, the C-DAI / T-DAI included in the second sub-codebook is the number obtained by counting the multi-PDSCH scheduling DCI that schedules a plurality of (valid) PDSCHs including a plurality of PDSCHs having an HPN with HARQ feedback enabled. 【0236】 In the case of multi-PDSCH scheduling DCI that schedules a plurality of (valid) PDSCHs having an HPN with all HARQ feedback disabled, the C-DAI / T-DAI included in the second sub-codebook may be any of the following proposals. 【0237】 <Proposal 1> The C-DAI / T-DAI included in the second sub-codebook may be the number obtained by counting the multi-PDSCH scheduling DCI that schedules a plurality of (valid) PDSCHs including at least one PDSCH having an HPN with HARQ feedback enabled. 【0238】 <Proposal 2> The terminal 20 may ignore C-DAI and T-DAI regardless of the value for generating the type 2 HARQ-ACK codebook. 【0239】 <Example 1> When the DCI schedules a plurality of PDSCHs with all HPNs having HARQ feedback disabled, the operation of the terminal 20 for each option is as follows. 【0240】 The terminal 20 operating in option 6-1 reports a NACK for the DCI. The terminal 20 operating in option 6-2 or option 6-3 does not report anything for the DCI. 【0241】 <Example 2> If DCI schedules multiple PDSCHs where only one HPN is configured to enable HARQ feedback and the other HPNs are configured to disable HARQ feedback, the behavior of each option terminal 20 is as follows: 【0242】 A terminal 20 operating under Option 6-1 or Option 6-2 assumes that the DCI is associated with the second subcodebook. A terminal 20 operating under Option 6-3 assumes that the DCI is associated with the first subcodebook. 【0243】 The first subcodebook of option 6-3 mentioned above specifically consists of one of the following options: 【0244】 <Option 6-3A> The DCI related to the first subcodebook may be as follows: • Single PDSCH scheduling DCI with HPN configured to enable HARQ feedback. • Multi-PDSCH scheduling DCI that schedules only one (active) PDSCH with an HPN configured to enable HARQ feedback. • Multi-PDSCH scheduling DCI that schedules multiple (enabled) PDSCHs, including only one PDSCH with an HPN configured to enable HARQ feedback. • DCIs that release SPS, DCIs that instruct Scell ​​to pause (and other DCIs that do not schedule PDSCH) 【0245】 The structure of the first subcodebook may be as follows: ACK / NACK for single PDSCH scheduling DCI that schedules a PDSCH with an HPN configured to have HARQ feedback enabled. ACK / NACK for multi-PDSCH scheduling DCI that schedules only one (valid) PDSCH with an HPN configured to enable HARQ feedback. ACK / NACK for multi-PDSCH scheduling DCI that schedules multiple (enabled) PDSCHs, including only one PDSCH with an HPN configured to enable HARQ feedback. ACK / NACK to DCIs that release SPS, DCIs that instruct Scell ​​to pause (and other DCIs that do not schedule PDSCH) 【0246】 The C-DAI / T-DAI included in the first subcodebook may be as follows: In other words, for single PDSCH scheduling DCIs that schedule a PDSCH with an HPN configured to enable HARQ feedback, multi-PDSCH scheduling DCIs that schedule multiple (enabled) PDSCHs including only one PDSCH with an HPN configured to enable HARQ feedback, and other DCIs that do not schedule PDSCHs (e.g., DCIs that release SPS, DCIs that instruct Scells to pause, etc.), the C-DAI / T-DAI included in the first subcodebook is the count of single PDSCH scheduling DCIs that schedule a PDSCH with an HPN configured to enable HARQ feedback, multi-PDSCH scheduling DCIs that schedule only one (enabled) PDSCH with an HPN configured to enable HARQ feedback, multi-PDSCH scheduling DCIs that schedule multiple (enabled) PDSCHs including only one PDSCH with an HPN configured to enable HARQ feedback, and other DCIs that do not schedule PDSCHs (e.g., DCIs that release SPS, DCIs that instruct Scells to pause, etc.). 【0247】 For a single PDSCH scheduling DCI that schedules a PDSCH with an HPN configured to disable HARQ feedback, the C-DAI / T-DAI included in the first subcodebook may be one of the following: 【0248】 <Plan 1> The C-DAI / T-DAI included in the first subcodebook may be the sum of single PDSCH scheduling DCIs that schedule PDSCHs with HPNs configured to enable HARQ feedback, multi-PDSCH scheduling DCIs that schedule only one (active) PDSCH with an HPN configured to enable HARQ feedback, multi-PDSCH scheduling DCIs that schedule multiple (active) PDSCHs, including only one PDSCH with an HPN configured to enable HARQ feedback, and other DCIs that do not schedule PDSCHs (e.g., DCIs that release SPS, DCIs that instruct Scells to pause, etc.). 【0249】 <Plan 2> Terminal 20 may ignore the C-DAI and T-DAI regardless of the values ​​for generating a Type 2 HARQ-ACK codebook. 【0250】 <Option 6-3B> The DCI related to the first subcodebook may be as follows: • Single PDSCH scheduling DCI with HPN configured to enable HARQ feedback. • Multi-PDSCH scheduling DCI that schedules only one (active) PDSCH. • Multi-PDSCH scheduling DCI that schedules multiple (enabled) PDSCHs, including only one PDSCH with an HPN configured to enable HARQ feedback. • DCIs that release SPS, DCIs that instruct Scell ​​to pause (and other DCIs that do not schedule PDSCH) 【0251】 The structure of the first subcodebook may be as follows: ACK / NACK for single PDSCH scheduling DCI that schedules a PDSCH with an HPN configured to have HARQ feedback enabled. ACK / NACK for multi-PDSCH scheduling DCI that schedules only one (valid) PDSCH with an HPN configured to enable HARQ feedback. NACK for multi-PDSCH scheduling DCI that schedules only one (enabled) PDSCH with an HPN that has HARQ feedback disabled. ACK / NACK for multi-PDSCH scheduling DCI that schedules multiple (enabled) PDSCHs, including only one PDSCH with an HPN configured to enable HARQ feedback. ACK / NACK to DCIs that release SPS, DCIs that instruct Scell ​​to pause (and other DCIs that do not schedule PDSCH) 【0252】 The C-DAI / T-DAI included in the first subcodebook may be as follows: a single PDSCH scheduling DCI that schedules a PDSCH with an HPN configured to enable HARQ feedback, a multi-PDSCH scheduling DCI that schedules only one (enabled) PDSCH, a multi-PDSCH scheduling DCI that schedules multiple (enabled) PDSCHs, including only one PDSCH with an HPN configured to enable HARQ feedback, and other DCIs that do not schedule PDSCHs (e.g., a DCI that releases SPS, a DCI that instructs Scell ​​to pause, etc.), in which case the C-DAI / T-DAI included in the first subcodebook may be as follows: This is the total number of DCIs that schedule a single PDSCH with an HPN configured to enable RQ feedback, a multi-PDSCH scheduling DCI that schedules only one (active) PDSCH with an HPN configured to enable HARQ feedback, a multi-PDSCH scheduling DCI that schedules multiple (active) PDSCHs, including only one PDSCH with an HPN configured to enable HARQ feedback, and other DCIs that do not schedule PDSCHs (e.g., a DCI that releases SPS, a DCI that instructs Scell ​​to pause, etc.). 【0253】 For a single PDSCH scheduling DCI that schedules a PDSCH with an HPN configured to disable HARQ feedback, the C-DAI / T-DAI included in the first subcodebook may be one of the following: 【0254】 <Plan 1> The C-DAI / T-DAI included in the first subcodebook may be the sum of single PDSCH scheduling DCIs that schedule PDSCHs with HPNs configured to enable HARQ feedback, multi-PDSCH scheduling DCIs that schedule only one (active) PDSCH with an HPN configured to enable HARQ feedback, multi-PDSCH scheduling DCIs that schedule multiple (active) PDSCHs, including only one PDSCH with an HPN configured to enable HARQ feedback, and other DCIs that do not schedule PDSCHs (e.g., DCIs that release SPS, DCIs that instruct Scells to pause, etc.). 【0255】 <Plan 2> Terminal 20 may ignore the C-DAI and T-DAI regardless of the values ​​for generating a Type 2 HARQ-ACK codebook. 【0256】 <Option 6-3C> The DCI related to the first subcodebook may be as follows: • Single PDSCH scheduling DCI • Multi-PDSCH scheduling DCI that schedules only one (active) PDSCH. • Multi-PDSCH scheduling DCI that schedules multiple (enabled) PDSCHs, including only one PDSCH with an HPN configured to enable HARQ feedback. • DCIs that release SPS, DCIs that instruct Scell ​​to pause (and other DCIs that do not schedule PDSCH) 【0257】 The structure of the first subcodebook may be as follows: ACK / NACK for single PDSCH scheduling DCI that schedules a PDSCH with an HPN configured to have HARQ feedback enabled. NACK for single PDSCH scheduling DCI with HPN configured to disable HARQ feedback ACK / NACK for multi-PDSCH scheduling DCI that schedules only one (valid) PDSCH with an HPN configured to enable HARQ feedback. ACK / NACK for multi-PDSCH scheduling DCI that schedules only one (valid) PDSCH with an HPN configured to enable HARQ feedback. ACK / NACK for multi-PDSCH scheduling DCI that schedules multiple (enabled) PDSCHs, including only one PDSCH with an HPN configured to enable HARQ feedback. ACK / NACK to DCIs that release SPS, DCIs that instruct Scell ​​to pause (and other DCIs that do not schedule PDSCH) 【0258】 The C-DAI / T-DAI included in the first subcodebook may be the number of DCIs related to the first subcodebook, including single PDSCH scheduling DCIs that schedule PDSCHs, multi-PDSCH scheduling DCIs that schedule only one (active) PDSCH, multi-PDSCH scheduling DCIs that schedule multiple (active) PDSCHs including only one PDSCH with an HPN set to enable HARQ feedback, and other DCIs that do not schedule PDSCHs (e.g., DCIs that release SPS, DCIs that instruct Scells to pause, etc.). 【0259】 For example, terminal 20 operating under option 6-3A will not report anything about a single PDSCH scheduling DCI using an HPN with HARQ feedback disabled. Furthermore, terminal 20 will not report anything about a multi-PDSCH scheduling DCI containing only one valid PDSCH with an HPN that has HARQ feedback disabled. 【0260】 Furthermore, terminal 20 operating under option 6-3B will not report anything for single PDSCH scheduling DCIs using HPNs with HARQ feedback disabled. Also, terminal 20 will report a NACK for multi-PDSCH scheduling DCIs that include only one valid PDSCH with an HPN that has HARQ feedback disabled. 【0261】 Furthermore, terminal 20 operating under Option 6-3C reports a NACK for single PDSCH scheduling DCIs using HPNs with HARQ feedback disabled. Also, terminal 20 reports a NACK for multi-PDSCH scheduling DCIs containing only one valid PDSCH with an HPN that has HARQ feedback disabled. 【0262】 If no reports are submitted for each option, the codebook size can be reduced. Alternatively, if NACKs are submitted, the codebook size can be fixed. 【0263】 According to this embodiment, when multi-PDSCH scheduling and HARQ feedback disabling are combined, a type 2 HARQ-ACK codebook can be generated in a manner that does not involve time-domain bundles. 【0264】 (Example 4) This embodiment describes an example in which terminal 20, operating under each option of Example 2, generates a Type 1 HARQ-ACK codebook in a manner that does not involve a time-domain bundle. Time-domain bundles will be discussed later, along with Example 5. 【0265】 <Option 1> Terminal 20 may reuse the procedure for generating a Type 1 HARQ-ACK codebook for cells configured with multi-PDSCH scheduling. 【0266】 This may mean that terminal 20 determines ACK / NACK based on the actual decoding result of any PDSCH on a cell, regardless of whether HPN is set to enable or disable HARQ feedback, if multi-PDSCH scheduling is set for any cell. 【0267】 Furthermore, if multi-PDSCH scheduling is set for any cell, terminal 20 may determine ACK / NACK based on the actual decoding result of the PDSCH on the cell within the same PUCCH cell group, regardless of whether HPN is set to enable or disable HARQ feedback. 【0268】 <Option 2> Terminal 20 may report a NACK for the SLIV corresponding to the HPN with HARQ feedback disabled, based on the procedure for generating a Type 1 HARQ-ACK codebook in multi-PDSCH scheduling. 【0269】 According to this embodiment, when multi-PDSCH scheduling and HARQ feedback disabling are combined, a type 1 HARQ-ACK codebook can be generated in a manner that does not involve time-domain bundles. 【0270】 (Example 5) In this embodiment, an example will be described in which a terminal 20 that operates according to each option of Embodiment 2 generates a Type 2 HARQ-ACK codebook in a method involving a time-domain bundle. 【0271】 (Regarding the time-domain bundle) The time-domain bundle agreed upon in Release 17 will be described. According to the time-domain bundle, a HARQ bundling group for collectively transmitting HARQ-ACKs for a plurality of PDSCHs is set. 【0272】 In the case of multi-PDSCH scheduling using a single DCI, new RRC parameters (such as numberOfHARQ-BundlingGroups) are introduced. For the Type 2 HARQ-ACK codebook for each serving cell, the number of HARQ bundling groups with a value range of {1, 2, 4} is set in the RRC parameter. 【0273】 [[ID=!4]]IIf the RRC parameter is not set for the serving cell, the time-domain bundle of the Type 2 HARQ-ACK codebook is not valid for the serving cell. 【0274】 The maximum number of PDSCHs assigned to each bundling group is ceil(N PDSCH,MAX / N HBG ). Here, N HBG is the number of bundling groups set by the numberOfHARQ-BundlingGroups of the serving cell, and N PDSCH,MAX is the maximum set number of PDSCHs of the serving cell. 【0275】 The PDSCH corresponding to the [configured or valid] SLIV of the row index of the TDRA table indicated by the multi-PDSCH scheduling DCI is assigned to the bundling group. For example, N HBG = 4, N PDSCH,MAX / N HBGIf =8 and 5 PDSCHs are scheduled, the PDSCHs are assigned to each group by reusing the CBG grouping scheme of 2 / 1 / 1 / 1. 【0276】 For empty groups or groups filled only with invalid PDSCHs, the HARQ-ACK bit of the bundling group is set to NACK (the same principle as when no time-domain bundle is set). 【0277】 The logical AND operation is applied to all valid PDSCHs within the same bundling group to generate one HARQ-ACK bit per group, for at least 1TB. 【0278】 If the number of HARQ bundling groups for a serving cell is set to 1, the HARQ-ACK bits corresponding to any DCI of the serving cell belong to the first subcodebook. 【0279】 If the data size is at least 1TB and the number of HARQ bundling groups in the serving cell is set to a number greater than 1, the corresponding HARQ-ACK bit for multi-PDSCH scheduling (meaning that the multi-PDSCH scheduling DCI schedules multiple PDSCHs) belongs to the second subcodebook. 【0280】 Here, the number of HARQ-ACK bits corresponding to the multi-PDSCH scheduling DCI is determined based on the maximum Q value across all serving cells in the same PUCCH cell group, where Q = (numberOfHARQ - maximum number of PDSCH configurations for cells without BundlingGroups configured) or Q = (numberOfHARQ - number of configured HARQ bundling groups for cells with BundlingGroups configured). 【0281】 Next, the operation of each option shown in Example 2 will be described in this embodiment. 【0282】 For terminal 20 operating under Option 1 of Example 2, the rules specified for generating the HARQ-ACK codebook for multi-PDSCH scheduling agreed upon in Release 17 may be reused. 【0283】 <Option 2, First Subcodebook> Terminal 20, which operates under Option 2 of Example 2, generates the first subcodebook as follows: 【0284】 <Option 2-1> The DCI related to the first subcodebook may be as follows: • Single PDSCH scheduling DCI with HPN configured to enable HARQ feedback. • Multi-PDSCH scheduling DCI that schedules only one (active) PDSCH. • Multi-PDSCH scheduling DCI that schedules multiple (active) PDSCHs in a cell with only one time-domain bundling group configured. • DCIs that release SPS, DCIs that instruct Scell ​​to pause (and other DCIs that do not schedule PDSCH) 【0285】 The structure of the first subcodebook may be as follows: ACK / NACK for single PDSCH scheduling DCI that schedules a PDSCH with an HPN configured to have HARQ feedback enabled. ACK / NACK for multi-PDSCH scheduling DCI that schedules only one (valid) PDSCH. • Bundled bits indicating ACK / NACK for multi-PDSCH scheduling DCI that schedules multiple (valid) PDSCHs in a cell with only one time-domain bundling group configured. ACK / NACK to DCIs that release SPS, DCIs that instruct Scell ​​to pause (and other DCIs that do not schedule PDSCH) 【0286】 The C-DAI / T-DAI included in the first subcodebook may be as follows: In other words, for single PDSCH scheduling DCIs that schedule PDSCHs with HPNs configured to enable HARQ feedback, multi-PDSCH scheduling DCIs that schedule only one (active) PDSCH, multi-PDSCH scheduling DCIs that schedule multiple (active) PDSCHs in a cell with only one time-domain bundling group configured, and other DCIs that do not schedule PDSCHs (e.g., DCIs that release SPS, DCIs that instruct Scells to pause, etc.), the C-DAI / T-DAI included in the first subcodebook is the count of single PDSCH scheduling DCIs that schedule PDSCHs with HPNs configured to enable HARQ feedback, multi-PDSCH scheduling DCIs that schedule only one (active) PDSCH, multi-PDSCH scheduling DCIs that schedule multiple (active) PDSCHs in a cell with only one time-domain bundling group configured, and other DCIs that do not schedule PDSCHs (e.g., DCIs that release SPS, DCIs that instruct Scells to pause, etc.). 【0287】 For a single PDSCH scheduling DCI that schedules a PDSCH with an HPN configured to disable HARQ feedback, the C-DAI / T-DAI included in the first subcodebook may be one of the following: 【0288】 <Plan 1> The C-DAI / T-DAI included in the first subcodebook may be the count of single PDSCH scheduling DCIs that schedule PDSCHs with HPNs configured to enable HARQ feedback, multi-PDSCH scheduling DCIs that schedule only one (active) PDSCH, multi-PDSCH scheduling DCIs that schedule multiple (active) PDSCHs in a cell configured with only one time-domain bundling group, and other DCIs that do not schedule PDSCHs (e.g., DCIs that release SPS, DCIs that instruct Scells to pause, etc.). 【0289】 <Plan 2> Terminal 20 may ignore the C-DAI and T-DAI regardless of the values ​​for generating a Type 2 HARQ-ACK codebook. 【0290】 <Option 2-2> The DCI related to the first subcodebook may be as follows: • Single PDSCH scheduling DCI • Multi-PDSCH scheduling DCI that schedules only one (active) PDSCH. • Multi-PDSCH scheduling DCI that schedules multiple (active) PDSCHs in a cell with only one time-domain bundling group configured. • DCIs that release SPS, DCIs that instruct Scell ​​to pause (and other DCIs that do not schedule PDSCH) 【0291】 The structure of the first subcodebook may be as follows: ACK / NACK for single PDSCH scheduling DCI that schedules a PDSCH with an HPN configured to have HARQ feedback enabled. NACK for single PDSCH scheduling DCI with HPN configured to disable HARQ feedback ACK / NACK for multi-PDSCH scheduling DCI that schedules only one (valid) PDSCH. • Bundled bits indicating ACK / NACK for multi-PDSCH scheduling DCI that schedules multiple (valid) PDSCHs in a cell with only one time-domain bundling group configured. ACK / NACK to DCIs that release SPS, DCIs that instruct Scell ​​to pause (and other DCIs that do not schedule PDSCH) 【0292】 The C-DAI / T-DAI included in the first subcodebook may be the number of DCIs related to the first subcodebook, including single PDSCH scheduling DCIs that schedule PDSCHs, multi-PDSCH scheduling DCIs that schedule only one (active) PDSCH, multi-PDSCH scheduling DCIs that schedule multiple (active) PDSCHs in a cell with only one time-domain bundling group configured, and other DCIs that do not schedule PDSCHs (e.g., DCIs that release SPS, DCIs that instruct Scells to pause, etc.). 【0293】 <Option 2, Second Subcodebook> The second subcodebook of Option 2 may include the following: 【0294】 The second subcodebook of Option 2 may include a multi-PDSCH scheduling DCI that schedules multiple (valid) PDSCHs in cells with multiple time-domain bundling groups configured or in cells without time-domain bundles configured. 【0295】 Additionally, the second subcodebook of Option 2 may include HARQ-ACK information bits (M bits) for the second subcodebook included in each DCI. 【0296】 M is determined by the number of time-domain bundling groups of cells within a PUCCH cell group that consist of time-domain bundlings, and the maximum number of scheduled PDSCHs between cells that do not consist of time-domain bundlings. 【0297】 The C-DAI and T-DAI applied to the second subcodebook of Option 2 may also be the number of multi-PDSCH scheduling DCIs that schedule multiple (active) PDSCHs in a cell with multiple time-domain bundling groups configured. 【0298】 <Bundling method related to Option 2> If the number of bundling groups is set to 1 (i.e., the time-domain bundle of the first subcodebook), terminal 20 bundles the HARQ-ACK bits of the first TB of a valid PDSCH into 1 bit by a logical AND operation. 【0299】 Furthermore, terminal 20 inputs an ACK / NACK to valid PDSCHs, regardless of whether HPN is configured to enable or disable HARQ feedback. Terminal 20 also inputs an ACK to invalid PDSCHs. 【0300】 Terminal 20 bundles the HARQ-ACK bits of the second TB of a valid PDSCH into 1 bit by a logical AND operation if any cell in the PUCCH cell group is set to a maximum of 2TB. 【0301】 Terminal 20 generates a NACK for a second TB if there is only one TB for all PDSCHs scheduled by a single DCI. 【0302】 Terminal 20 sends an ACK / NACK to the second TB of a valid PDSCH, regardless of whether HPN is set to enable or disable HARQ feedback, if at least one PDSCH has 2TB. In this case, terminal 20 sends an ACK for invalid PDSCHs and for PDSCHs with only one TB. 【0303】 In this embodiment, the phrase "inputting ACK / NACK to a valid PDSCH" can be replaced with "determining ACK / NACK based on the actual decoding result of a valid PDSCH." 【0304】 Furthermore, if the number of bundling groups is greater than 1 (i.e., a time-domain bundle of the second subcodebook), terminal 20 may operate in one of the following proposed bundling methods. 【0305】 <Plan 1> Terminal 20 may perform bundling based on a valid PDSCH. 【0306】 If the number of valid PDSCHs is less than or equal to the number of bundling groups, each bundling group contains at most one valid PDSCH. 【0307】 Terminal 20 may, for the first TB of group M, generate an ACK / NACK to the bundling group for the first TB of the PDSCH if the bundling group contains a valid PDSCH. Otherwise, terminal 20 may generate a NACK to the bundling group. 【0308】 Terminal 20 may generate an ACK / NACK to the bundling group for the second TB in the M group if a maximum of 2TB is set and the bundling group contains 2TB of valid PDSCH. Otherwise, terminal 20 may generate a NACK to the bundling group. 【0309】 Furthermore, if the number of valid PDSCHs is greater than the number of bundling groups, terminal 20 assigns the valid PDSCHs to bundling groups. For example, terminal 20 assigns N HBG =4, N PDSCH,MAX / N HBG If =8 and 5 PDSCHs are scheduled, the PDSCHs may be assigned to each group by reusing the CBG grouping scheme of 2 / 1 / 1 / 1. 【0310】 Terminal 20, in the case of the first TB of group M, may input an ACK / NACK to a valid PDSCH for each bundling group, provided that the bundle contains at least one valid PDSCH. A logical AND operation is applied to the bits. 【0311】 Terminal 20 may, for the second TB of a group M, generate an ACK / NACK for the second TB of a valid 2TB PDSCH for each bundling group, provided that the group contains at least one valid 2TB PDSCH. Terminal 20 may also generate a NACK for valid PDSCHs that contain only one TB in the group. A logical AND operation is applied to the bits. 【0312】 Terminal 20 may generate a NACK to the bundling group if there is only one TB in each valid PDSCH within the bundling group. 【0313】 <Plan 2> Terminal 20 may perform bundling based on the scheduled PDSCH. 【0314】 If the number of scheduled PDSCHs is less than or equal to the number of bundling groups, each bundling group will contain at most one scheduled PDSCH. 【0315】 Terminal 20 may, for the first TB of group M, generate an ACK / NACK to the bundling group for the first TB of the PDSCH if the bundling group contains a valid PDSCH. Otherwise, terminal 20 may generate a NACK to the bundling group. 【0316】 Terminal 20 may generate an ACK / NACK to the bundling group for the second TB in the M group if a maximum of 2TB is set and the bundling group contains 2TB of valid PDSCH. Otherwise, terminal 20 may generate a NACK to the bundling group. 【0317】 Furthermore, if the number of scheduled PDSCHs is greater than the number of bundling groups, terminal 20 assigns the scheduled PDSCHs to bundling groups. For example, terminal 20 assigns N HBG =4, N PDSCH,MAX / N HBG If =8 and 5 PDSCHs are scheduled, the scheduled PDSCHs may be assigned to each group by reusing the CBG grouping scheme of 2 / 1 / 1 / 1. 【0318】 Terminal 20, in the case of the first TB of group M, may input an ACK / NACK to a valid PDSCH for each bundling group, provided that the bundling group contains at least one valid PDSCH. Terminal 20 may generate an ACK to an invalid PDSCH. A logical AND operation is applied to the bits. 【0319】 Terminal 20 may generate a NACK to the bundling group if each scheduled PDSCH in the bundling group is invalid. 【0320】 Terminal 20 may, for the second TB of a group M, generate an ACK / NACK for the second TB of a valid 2TB PDSCH for each bundling group, provided that the group contains at least one valid 2TB PDSCH. Terminal 20 may also generate a NACK for a valid PDSCH that contains only one TB in the group, or for an invalid PDSCH in the group. A logical AND operation is applied to the bits. 【0321】 Terminal 20 may generate a NACK to the bundling group if there is only one TB in each active PDSCH in the bundling group, or if each scheduled PDSCH in the bundling group is disabled, and the HPN has HARQ feedback enabled. 【0322】 <Option 3, First Subcodebook> Terminal 20, which operates according to option 3 of Example 2, generates the first subcodebook as follows: 【0323】 <Option 3-1> The DCI related to the first subcodebook may be as follows: • Single PDSCH scheduling DCI with HPN configured to enable HARQ feedback. • Multi-PDSCH scheduling DCI that schedules only one (active) PDSCH with an HPN configured to enable HARQ feedback. • Multi-PDSCH scheduling DCI that schedules multiple (active) PDSCHs in a cell with only one time-domain bundling group configured. • DCIs that release SPS, DCIs that instruct Scell ​​to pause (and other DCIs that do not schedule PDSCH) 【0324】 The structure of the first subcodebook may be as follows: ACK / NACK for single PDSCH scheduling DCI that schedules a PDSCH with an HPN configured to have HARQ feedback enabled. ACK / NACK for multi-PDSCH scheduling DCI that schedules only one (valid) PDSCH with an HPN configured to enable HARQ feedback. • Bundled bits indicating ACK / NACK for multi-PDSCH scheduling DCI that schedules multiple (valid) PDSCHs in a cell with only one time-domain bundling group configured. ACK / NACK to DCIs that release SPS, DCIs that instruct Scell ​​to pause (and other DCIs that do not schedule PDSCH) 【0325】 The C-DAI / T-DAI included in the first subcodebook may be as follows: In other words, for single PDSCH scheduling DCIs that schedule PDSCHs with HPNs configured to enable HARQ feedback, multi-PDSCH scheduling DCIs that schedule multiple (active) PDSCHs in a cell with only one time-domain bundling group configured, and other DCIs that do not schedule PDSCHs (e.g., DCIs that release SPS, DCIs that instruct Scells to pause, etc.), the C-DAI / T-DAI included in the first subcodebook is the count of single PDSCH scheduling DCIs that schedule PDSCHs with HPNs configured to enable HARQ feedback, multi-PDSCH scheduling DCIs that schedule only one (active) PDSCH with an HPN configured to enable HARQ feedback, multi-PDSCH scheduling DCIs that schedule multiple (active) PDSCHs in a cell with only one time-domain bundling group configured, and other DCIs that do not schedule PDSCHs (e.g., DCIs that release SPS, DCIs that instruct Scells to pause, etc.). 【0326】 For a single PDSCH scheduling DCI that schedules a PDSCH with an HPN configured to disable HARQ feedback, the C-DAI / T-DAI included in the first subcodebook may be one of the following: 【0327】 <Plan 1> The C-DAI / T-DAI included in the first subcodebook may be the count of single PDSCH scheduling DCIs that schedule PDSCHs with HPNs configured to enable HARQ feedback, multi-PDSCH scheduling DCIs that schedule only one (active) PDSCH with an HPN configured to enable HARQ feedback, multi-PDSCH scheduling DCIs that schedule multiple (active) PDSCHs in a cell configured with only one time-domain bundling group, and other DCIs that do not schedule PDSCHs (e.g., DCIs that release SPS, DCIs that instruct Scells to pause, etc.). 【0328】 <Plan 2> Terminal 20 may ignore the C-DAI and T-DAI regardless of the values ​​for generating a Type 2 HARQ-ACK codebook. 【0329】 <Option 3-2> The DCI related to the first subcodebook may be as follows: • Single PDSCH scheduling DCI with HPN configured to enable HARQ feedback. • Multi-PDSCH scheduling DCI that schedules only one (active) PDSCH. • Multi-PDSCH scheduling DCI that schedules multiple (active) PDSCHs in a cell with only one time-domain bundling group configured. • DCIs that release SPS, DCIs that instruct Scell ​​to pause (and other DCIs that do not schedule PDSCH) 【0330】 The structure of the first subcodebook may be as follows: ACK / NACK for single PDSCH scheduling DCI that schedules a PDSCH with an HPN configured to have HARQ feedback enabled. ACK / NACK for multi-PDSCH scheduling DCI that schedules only one (valid) PDSCH with an HPN configured to enable HARQ feedback. NACK for single PDSCH scheduling DCI with HPN configured to disable HARQ feedback • Bundled bits indicating ACK / NACK for multi-PDSCH scheduling DCI that schedules multiple (valid) PDSCHs in a cell with only one time-domain bundling group configured. ACK / NACK to DCIs that release SPS, DCIs that instruct Scell ​​to pause (and other DCIs that do not schedule PDSCH) 【0331】 The C-DAI / T-DAI included in the first subcodebook may be as follows: a single PDSCH scheduling DCI that schedules a PDSCH with an HPN configured to enable HARQ feedback, a multi-PDSCH scheduling DCI that schedules only one (active) PDSCH, a multi-PDSCH scheduling DCI that schedules multiple (active) PDSCHs in a cell configured with only one time-domain bundling group, and other DCIs that do not schedule PDSCHs (e.g., a DCI that releases SPS, a DCI that instructs Scell ​​to pause, etc.), the C-DAI / T-DAI included in the first subcodebook may be as follows: This is the number of DCIs that schedule a single PDSCH scheduling DCI that schedules a PDSCH with an HPN configured to enable RQ feedback, a multi-PDSCH scheduling DCI that schedules only one (enabled) PDSCH with an HPN configured to enable HARQ feedback, a multi-PDSCH scheduling DCI that schedules multiple (enabled) PDSCHs in a cell configured with only one time-domain bundling group, and other DCIs that do not schedule PDSCHs (e.g., a DCI that releases SPS, a DCI that instructs Scell ​​to pause, etc.). 【0332】 For a single PDSCH scheduling DCI that schedules a PDSCH with an HPN configured to disable HARQ feedback, the C-DAI / T-DAI included in the first subcodebook may be one of the following: 【0333】 <Plan 1> The C-DAI / T-DAI included in the first subcodebook may be the count of single PDSCH scheduling DCIs that schedule PDSCHs with HPNs configured to enable HARQ feedback, multi-PDSCH scheduling DCIs that schedule only one (active) PDSCH with an HPN configured to enable HARQ feedback, multi-PDSCH scheduling DCIs that schedule multiple (active) PDSCHs in a cell configured with only one time-domain bundling group, and other DCIs that do not schedule PDSCHs (e.g., DCIs that release SPS, DCIs that instruct Scells to pause, etc.). 【0334】 <Plan 2> Terminal 20 may ignore the C-DAI and T-DAI regardless of the values ​​for generating a Type 2 HARQ-ACK codebook. 【0335】 <Option 3-3> The DCI related to the first subcodebook may be as follows: • Single PDSCH scheduling DCI • Multi-PDSCH scheduling DCI that schedules only one (active) PDSCH. • Multi-PDSCH scheduling DCI that schedules multiple (active) PDSCHs in a cell with only one time-domain bundling group configured. • DCIs that release SPS, DCIs that instruct Scell ​​to pause (and other DCIs that do not schedule PDSCH) 【0336】 The structure of the first subcodebook may be as follows: ACK / NACK for single PDSCH scheduling DCI that schedules a PDSCH with an HPN configured to have HARQ feedback enabled. NACK for single PDSCH scheduling DCI with HPN configured to disable HARQ feedback ACK / NACK for multi-PDSCH scheduling DCI that schedules only one (valid) PDSCH with an HPN configured to enable HARQ feedback. ACK / NACK for multi-PDSCH scheduling DCI that schedules only one (valid) PDSCH with an HPN configured to enable HARQ feedback. • Bundled bits indicating ACK / NACK for multi-PDSCH scheduling DCI that schedules multiple (valid) PDSCHs in a cell with only one time-domain bundling group configured. ACK / NACK to DCIs that release SPS, DCIs that instruct Scell ​​to pause (and other DCIs that do not schedule PDSCH) 【0337】 The C-DAI / T-DAI included in the first subcodebook may be the number of DCIs related to the first subcodebook, including single PDSCH scheduling DCIs that schedule PDSCHs, multi-PDSCH scheduling DCIs that schedule only one (active) PDSCH, multi-PDSCH scheduling DCIs that schedule multiple (active) PDSCHs in a cell with only one time-domain bundling group configured, and other DCIs that do not schedule PDSCHs (e.g., DCIs that release SPS, DCIs that instruct Scells to pause, etc.). 【0338】 <Option 3, Second Subcodebook> The second subcodebook for Option 3 may be the same as the second subcodebook for Option 2. 【0339】 <Bundling method related to Option 3> The time-domain bundling method from Option 2 may be applied to Option 3. 【0340】 <Option 4, Subcodebook 1> The first subcodebook of Option 4 may be the same as the first subcodebook of Option 3. 【0341】 <Option 4, Second Subcodebook> Terminal 20, which operates according to option 4 of Example 2, generates the second subcodebook as follows: 【0342】 <Option 4-1> The DCI related to the second subcodebook may be as follows: Multi-PDSCH scheduling DCI that includes at least one PDSCH with an HPN configured to enable HARQ feedback and schedules multiple (enabled) PDSCHs in cells with multiple time-domain bundling groups configured or cells without time-domain bundlings configured. 【0343】 The structure of the second subcodebook may be as follows: • If the HPN included in any PDSCH is set to enable HARQ feedback, bundled bits indicating ACK / NACK for a PDSCH scheduled by a single DCI that schedules a PDSCH in a cell with multiple time-domain bundling groups or a cell without time-domain bundlings. 【0344】 The C-DAI / T-DAI included in the second subcodebook may be as follows: In the case of a multi-PDSCH scheduling DCI that schedules multiple (effective) PDSCHs in a cell with multiple time-domain bundling groups configured or a cell without time-domain bundles configured, which includes at least one PDSCH having an HPN configured with HARQ feedback enabled, the C-DAI / T-DAI included in the second subcodebook is the number of multi-PDSCH scheduling DCIs that schedule multiple (effective) PDSCHs in a cell with multiple time-domain bundling groups configured or a cell without time-domain bundles configured, which includes at least one PDSCH having an HPN configured with HARQ feedback enabled. 【0345】 For a multi-PDSCH scheduling DCI that schedules multiple (enabled) PDSCHs with HPNs that have all HARQ feedback disabled, the C-DAI / T-DAI included in the second subcodebook may be one of the following: 【0346】 <Plan 1> The C-DAI / T-DAI included in the second subcodebook may be the number of multi-PDSCH scheduling DCIs that include at least one PDSCH with an HPN configured to enable HARQ feedback and schedule multiple (enabled) PDSCHs in a cell with multiple time-domain bundling groups configured or in a cell without time-domain bundlings configured. 【0347】 <Plan 2> Terminal 20 may ignore the C-DAI and T-DAI regardless of the values ​​for generating a Type 2 HARQ-ACK codebook. 【0348】 <Option 4-2> The DCI related to the second subcodebook may be as follows: • Multi-PDSCH scheduling DCI for scheduling multiple (valid) PDSCHs in cells with multiple time-domain bundling groups configured or cells without time-domain bundling configured. 【0349】 The structure of the second subcodebook may be as follows: • If the HPN included in any PDSCH is set to enable HARQ feedback, bundled bits indicating ACK / NACK for a PDSCH scheduled by a single DCI that schedules a PDSCH in a cell with multiple time-domain bundling groups or a cell without time-domain bundlings. • NACK for PDSCH scheduled by a single DCI in a cell with multiple time-domain bundling groups configured or in a cell without time-domain bundling configured, when all HPNs are set to disable HARQ feedback. 【0350】 For DCIs related to the second subcodebook, the C-DAI / T-DAIs included in the second subcodebook may be the number of multi-PDSCH scheduling DCIs that schedule multiple (valid) PDSCHs in cells with multiple time-domain bundling groups or cells without time-domain bundles. 【0351】 <Bundling method related to Option 4> The time-domain bundling method from Option 2 may also be applied to Option 4. 【0352】 <Option 5, Subcodebook 1> The first subcodebook for Option 5 may be the same as the first subcodebook for Option 3. 【0353】 <Option 5, Second Subcodebook> Terminal 20, which operates under option 5 of Example 2, generates the second subcodebook as follows: 【0354】 <Option 5-1> The DCI related to the second subcodebook may be as follows: • Multi-PDSCH scheduling DCI that schedules multiple (enabled) PDSCHs with HPNs set to enable all HARQ feedback in cells with multiple time-domain bundling groups configured or cells without time-domain bundlings configured. 【0355】 The structure of the second subcodebook may be as follows: • If the HPN included in all PDSCHs is set to enable HARQ feedback, bundled bits indicating ACK / NACK for PDSCHs scheduled by a single DCI that schedules PDSCHs in cells with multiple time-domain bundling groups or cells without time-domain bundlings. 【0356】 The C-DAI / T-DAI included in the second subcodebook may be as follows: In the case of a multi-PDSCH scheduling DCI that schedules multiple (enabled) PDSCHs having HPNs with all HARQ feedback enabled in a cell with multiple time-domain bundling groups configured or a cell without time-domain bundles configured, the C-DAI / T-DAI included in the second subcodebook is the count of the multi-PDSCH scheduling DCIs that schedule multiple (enabled) PDSCHs having HPNs with all HARQ feedback enabled in a cell with multiple time-domain bundling groups configured or a cell without time-domain bundles configured. 【0357】 For a multi-PDSCH scheduling DCI that schedules multiple (enabled) PDSCHs, including at least one PDSCH with an HPN set to disable HARQ feedback, the C-DAI / T-DAI included in the second subcodebook may be one of the following proposals: 【0358】 <Plan 1> The C-DAI / T-DAI included in the second subcodebook may also be the number of multi-PDSCH scheduling DCIs that schedule multiple (active) PDSCHs with HPNs that enable all HARQ feedback in cells with multiple time-domain bundling groups configured or cells without time-domain bundles configured. 【0359】 <Plan 2> Terminal 20 may ignore the C-DAI and T-DAI regardless of the values ​​for generating a Type 2 HARQ-ACK codebook. 【0360】 <Option 5-2> The DCI related to the second subcodebook may be as follows: • Multi-PDSCH scheduling DCI for scheduling multiple (valid) PDSCHs in cells with multiple time-domain bundling groups configured or cells without time-domain bundling configured. 【0361】 The structure of the second subcodebook may be as follows: • If the HPN included in all PDSCHs is set to enable HARQ feedback, bundled bits indicating ACK / NACK for PDSCHs scheduled by a single DCI that schedules PDSCHs in cells with multiple time-domain bundling groups or cells without time-domain bundlings. • If the HPN included in any PDSCH is set to disable HARQ feedback, NACK for a PDSCH scheduled by a single DCI in a cell with multiple time-domain bundling groups or a cell without time-domain bundlings. 【0362】 For DCIs related to the second subcodebook, the C-DAI / T-DAIs included in the second subcodebook may be the number of multi-PDSCH scheduling DCIs that schedule multiple (valid) PDSCHs in cells with multiple time-domain bundling groups or cells without time-domain bundles. 【0363】 <Bundling method related to Option 5> The time-domain bundling method from Option 2 may also be applied to Option 5. 【0364】 <Option 6> The terminal 20 performing the operation of option 6 in Example 2 may perform any of the following optional operations. 【0365】 <Option 6-1> The first subcodebook of Option 6-1 may be the same as the first subcodebook of Option 3. 【0366】 The DCI related to the second subcodebook may be as follows: • Multi-PDSCH scheduling DCI for scheduling multiple (valid) PDSCHs in cells with multiple time-domain bundling groups configured or cells without time-domain bundling configured. 【0367】 The structure of the second subcodebook may be as follows: • Bundled bits indicating ACK / NACK for multiple (active) PDSCHs scheduled by multi-PDSCH scheduling DCI in a cell with multiple time-domain bundling groups configured. - ACK / NACK for multiple (active) PDSCHs scheduled by the Multi-PDSCH Scheduling DCI in cells where no time-domain bundle is configured (ACK for PDSCHs with HPNs that have HARQ feedback enabled, NACK for PDSCHs with HPNs that have HARQ feedback disabled) 【0368】 For DCIs related to the second subcodebook, the C-DAI / T-DAIs included in the second subcodebook may be the number of multi-PDSCH scheduling DCIs that schedule multiple (valid) PDSCHs in cells with multiple time-domain bundling groups or cells without time-domain bundles. 【0369】 <Bundling method related to Option 6-1> Terminal 20 may reuse the bundling method related to Option 2 if the number of bundling groups is set to 1 (i.e., the time-domain bundle of the first subcodebook). 【0370】 Furthermore, if the number of bundling groups is greater than 1 (i.e., a time-domain bundle of the second subcodebook), terminal 20 may operate in one of the following proposed bundling methods. 【0371】 <Plan 1> Terminal 20 may perform bundling based on a valid PDSCH having an HPN configured to enable HARQ feedback. 【0372】 Terminal 20 may set NACK to M HARQ-ACK bits of the first TB if each PDSCH has an HPN set to disable HARQ feedback, and in the maximum case, set NACK to M HARQ-ACK bits of the second TB. 【0373】 If the number of valid PDSCHs with HPNs configured to enable HARQ feedback is less than or equal to the number of bundling groups, each bundling group will contain at most one valid PDSCH with an HPN configured to enable HARQ feedback. 【0374】 Terminal 20 may generate an ACK / NACK to the first TB of the PDSCH in the first TB of the M group if the bundling group contains at least one valid PDSCH having an HPN configured to enable HARQ feedback. Otherwise, Terminal 20 may generate a NACK to the bundling group. 【0375】 Terminal 20 may generate an ACK / NACK to the bundling group for the second TB in the M group if a maximum of 2TB is set and the bundling group includes a valid 2TB PDSCH with an HPN configured to enable HARQ feedback. Otherwise, terminal 20 may generate a NACK to the bundling group. 【0376】 Furthermore, if the number of valid PDSCHs with HPNs configured to enable HARQ feedback is greater than the number of bundling groups, terminal 20 assigns the valid PDSCHs with HPNs configured to enable HARQ feedback to bundling groups. For example, terminal 20 assigns N HBG =4, N PDSCH,MAX / N HBGIf PDSCHs with HPNs set to =8 and 5 HARQ feedback enabled are scheduled, the PDSCHs with HPNs set to HARQ feedback may be assigned to each group by reusing the 2 / 1 / 1 / 1 CBG grouping scheme. 【0377】 Terminal 20 may input an ACK / NACK to a valid PDSCH if, for the first TB of group M, each bundling group contains a valid PDSCH with an HPN set to enable HARQ feedback. A logical AND operation is applied to the bits. 【0378】 Terminal 20 may, for the second TB of a group M, generate an ACK / NACK for the second TB of a valid PDSCH having an HPN configured to enable 2TB of HARQ feedback, provided that the group contains at least one valid PDSCH having an HPN configured to enable 2TB of HARQ feedback. Terminal 20 may also generate an ACK for a valid PDSCH having an HPN configured to enable HARQ feedback that has only one TB in the group. A logical AND operation is applied to the bits. 【0379】 Terminal 20 may generate a NACK to the bundling group if there is only one TB in each valid PDSCH within the bundling group. 【0380】 <Plan 2> Terminal 20 may perform bundling based on a valid PDSCH. 【0381】 If the number of valid PDSCHs is less than or equal to the number of bundling groups, each bundling group contains at most one valid PDSCH. 【0382】 Terminal 20 may generate an ACK / NACK to the first TB of the PDSCH in the first TB of the M group if the bundling group contains at least one valid PDSCH having an HPN configured to enable HARQ feedback. Otherwise, Terminal 20 may generate a NACK to the bundling group. 【0383】 Terminal 20 may generate an ACK / NACK to the bundling group for the second TB in the M group if a maximum of 2TB is set and the bundling group includes a valid 2TB PDSCH with an HPN configured to enable HARQ feedback. Otherwise, terminal 20 may generate a NACK to the bundling group. 【0384】 Furthermore, if the number of valid PDSCHs is greater than the number of bundling groups, terminal 20 assigns the valid PDSCHs to bundling groups. For example, terminal 20 assigns N HBG =4, N PDSCH,MAX / N HBG If =8 and 5 PDSCHs are scheduled, the PDSCHs may be assigned to each group by reusing the CBG grouping scheme of 2 / 1 / 1 / 1. 【0385】 Terminal 20 may, in the case of the first TB of group M, input an ACK / NACK to the valid PDSCH having an HPN set to enable HARQ feedback for each bundling group, if that HPN has an HPN set to enable HARQ feedback. In that case, terminal 20 may generate an ACK to the valid PDSCH having an HPN set to disable HARQ feedback. A logical AND operation is applied to the bits. 【0386】 Terminal 20 may generate a NACK to the bundling group if each valid PDSCH in the bundling group has an HPN configured to disable HARQ feedback. 【0387】 Terminal 20 may, for the second TB of a group M, generate an ACK / NACK for the second TB of a valid PDSCH having an HPN configured to enable 2TB of HARQ feedback, provided that the group contains at least one valid PDSCH having an HPN configured to enable 2TB of HARQ feedback. Terminal 20 may also generate an ACK for a valid PDSCH having an HPN configured to enable HARQ feedback that has only one TB in the group. A logical AND operation is applied to the bits. 【0388】 Terminal 20 may generate a NACK to the bundling group if each valid PDSCH in the bundling group has an HPN configured to disable HARQ feedback, or if each valid PDSCH in the bundling group has only one TB. 【0389】 For example, in Proposal 1, Group #1 is for HPN #1 and Group #2 is for HPN #2. (The grouping is based on a valid PDSCH with an HPN configured to enable HARQ feedback.) 【0390】 In the case of Option 2, Group #1 is for HPN #1 to #3, and Group #2 is for HPN #4 to #5. Next, in the first group, the ACK / NACK of HPN #1 and HPN #2 are bundled to obtain the bits. In the case of Group #2, a NACK is generated. 【0391】 <Plan 3> Terminal 20 may perform bundling based on the scheduled PDSCH. 【0392】 If the number of scheduled PDSCHs is less than or equal to the number of bundling groups, each bundling group will contain at most one scheduled PDSCH. 【0393】 Terminal 20 may generate an ACK / NACK to the first TB of the PDSCH in the first TB of the M group if the bundling group contains at least one valid PDSCH having an HPN configured to enable HARQ feedback. Otherwise, Terminal 20 may generate a NACK to the bundling group. 【0394】 Terminal 20 may generate an ACK / NACK to the bundling group for the second TB in the M group if a maximum of 2TB is set and the bundling group includes a valid 2TB PDSCH with an HPN configured to enable HARQ feedback. Otherwise, terminal 20 may generate a NACK to the bundling group. 【0395】 Furthermore, if the number of scheduled PDSCHs is greater than the number of bundling groups, terminal 20 assigns the scheduled PDSCHs to bundling groups. For example, terminal 20 assigns N HBG =4, N PDSCH,MAX / N HBG If =8 and 5 PDSCHs are scheduled, the scheduled PDSCHs may be assigned to each group by reusing the CBG grouping scheme of 2 / 1 / 1 / 1. 【0396】 For the first TB of the M group, terminal 20 may input an ACK / NACK to the valid PDSCH having an HPN configured to enable HARQ feedback, if the bundling group contains at least one valid PDSCH having an HPN configured to enable HARQ feedback. In that case, terminal 20 may generate an ACK to the valid PDSCH having an HPN configured to disable HARQ feedback, or to the disabled PDSCH. A logical AND operation is applied to the bits. 【0397】 Terminal 20 may generate a NACK to the bundling group if each active PDSCH in the bundling group has an HPN configured to disable HARQ feedback, or if each scheduled PDSCH in the bundling group is disabled. 【0398】 Terminal 20 may, for the second TB of a group M, generate an ACK / NACK for the second TB of a valid PDSCH with an HPN configured to enable 2TB HARQ feedback, provided that the bundling group contains at least one valid PDSCH with an HPN configured to enable 2TB HARQ feedback. Terminal 20 may also generate an ACK for a valid PDSCH with an HPN configured to enable HARQ feedback that has only one TB in the group, or for a valid PDSCH with an HPN configured to disable HARQ feedback, or for any invalid PDSCH in the group. A logical AND operation is applied to the bits. 【0399】 Terminal 20 may generate a NACK to the bundling group if each active PDSCH in the bundling group has an HPN configured to disable HARQ feedback, or if each active PDSCH in the bundling group has only one TB, or if each scheduled PDSCH in the bundling group is disabled. 【0400】 <Option 6-2> The first subcodebook of Option 6-2 may be the same as the first subcodebook of Option 3. 【0401】 The DCI related to the second subcodebook may be as follows: • Multi-PDSCH scheduling DCI that schedules multiple (enabled) PDSCHs, including at least one PDSCH with an HPN configured to enable HARQ feedback, in cells with multiple time-domain bundling groups configured or cells without time-domain bundlings configured. 【0402】 The structure of the second subcodebook may be as follows: • Bundled bits indicating ACK / NACK for multiple (active) PDSCHs scheduled by a multi-PDSCH scheduling DCI that schedules multiple (active) PDSCHs, including at least one PDSCH with an HPN set to enable HARQ feedback, in a cell with multiple time-domain bundling groups configured. - ACK / NACK for multiple (enabled) PDSCHs, including at least one PDSCH with an HPN set to enable HARQ feedback, in a cell where no time-domain bundle is set (ACK / NACK for PDSCHs with an HPN set to enable HARQ feedback, NACK for PDSCHs with an HPN set to disable HARQ feedback (these PDSCHs are scheduled together with another PDSCH with an HPN set to enable HARQ feedback)) 【0403】 The C-DAI / T-DAI included in the second subcodebook may be as follows: In the case of a multi-PDSCH scheduling DCI that schedules multiple (active) PDSCHs, including at least one PDSCH with an HPN set to enable HARQ feedback, in a cell with multiple time-domain bundling groups configured or a cell without a time-domain bundle configured, the C-DAI / T-DAI included in the second subcodebook is the count of the multi-PDSCH scheduling DCIs that schedule multiple (active) PDSCHs, including at least one PDSCH with an HPN set to enable HARQ feedback, in a cell with multiple time-domain bundling groups configured or a cell without a time-domain bundle configured. 【0404】 For a multi-PDSCH scheduling DCI that schedules multiple (enabled) PDSCHs with HPNs that have all HARQ feedback disabled in a cell with multiple time-domain bundling groups configured or in a cell without a time-domain bundle configured, the C-DAI / T-DAI included in the second subcodebook may be one of the following: 【0405】 <Plan 1> The C-DAI / T-DAI included in the second subcodebook may be the number of multi-PDSCH scheduling DCIs that schedule multiple (active) PDSCHs, including at least one PDSCH with an HPN set to enable HARQ feedback, in cells with multiple time-domain bundling groups or cells without time-domain bundles. 【0406】 <Plan 2> Terminal 20 may ignore the C-DAI and T-DAI regardless of the values ​​for generating a Type 2 HARQ-ACK codebook. 【0407】 <Bundling method related to Option 6-2> Terminal 20 may reuse the bundling method related to Option 2 if the number of bundling groups is set to 1 (i.e., the time-domain bundle of the first subcodebook). 【0408】 Furthermore, if the terminal 20 has more than one bundling group (i.e., a time-domain bundle of the second subcodebook), it may reuse the bundling method related to option 6-1. 【0409】 The difference between Option 6-2 and Option 6-1 is as follows: For example, if DCI schedules multiple PDSCHs on an HPN where all HARQ feedback is disabled, the bundling method under Option 6-1 reports a bundled M-bit NACK to DCI. In this case, the bundling method under Option 6-2 does not send HARQ feedback to DCI. 【0410】 Therefore, the case described in "Option 6-1 Second Subcodebook Bundle" as "if there is an HPN with HARQ feedback disabled in each active PDSCH" does not occur in Option 6-2 Second Subcodebook Bundle. 【0411】 <Option 6-3> The first subcodebook of Option 6-3 may have the same configuration as the first subcodebook of Option 3, with the following additions. The added configuration will be described later. • Multi-PDSCH scheduling DCI that schedules multiple (enabled) PDSCHs, including only one PDSCH with an HPN configured to enable HARQ feedback, in cells with multiple time-domain bundling groups configured or cells without time-domain bundlings configured. 【0412】 The DCI related to the second subcodebook may be as follows: • Multi-PDSCH scheduling DCI that schedules multiple (enabled) PDSCHs, including multiple PDSCHs with HPNs that have HARQ feedback enabled, in cells with multiple time-domain bundling groups configured or cells without time-domain bundlings configured. 【0413】 The structure of the second subcodebook may be as follows: • Bundled bits indicating ACK / NACK for multiple (active) PDSCHs scheduled by a multi-PDSCH scheduling DCI that schedules multiple (active) PDSCHs, including at least one PDSCH with an HPN set to enable HARQ feedback, in a cell with multiple time-domain bundling groups configured. - ACK / NACK for multiple (enabled) PDSCHs, including at least one PDSCH with an HPN set to enable HARQ feedback, in a cell where no time-domain bundle is set (ACK / NACK for PDSCHs with an HPN set to enable HARQ feedback, NACK for PDSCHs with an HPN set to disable HARQ feedback (these PDSCHs are scheduled together with another PDSCH with an HPN set to enable HARQ feedback)) 【0414】 The C-DAI / T-DAI included in the second subcodebook may be as follows: In the case of a multi-PDSCH scheduling DCI that schedules multiple (active) PDSCHs, including at least one PDSCH with an HPN set to enable HARQ feedback, in a cell with multiple time-domain bundling groups configured or a cell without a time-domain bundle configured, the C-DAI / T-DAI included in the second subcodebook is the count of the multi-PDSCH scheduling DCIs that schedule multiple (active) PDSCHs, including at least one PDSCH with an HPN set to enable HARQ feedback, in a cell with multiple time-domain bundling groups configured or a cell without a time-domain bundle configured. 【0415】 For a multi-PDSCH scheduling DCI that schedules multiple (enabled) PDSCHs with HPNs that have all HARQ feedback disabled in a cell with multiple time-domain bundling groups configured or in a cell without a time-domain bundle configured, the C-DAI / T-DAI included in the second subcodebook may be one of the following: 【0416】 <Plan 1> The C-DAI / T-DAI included in the second subcodebook may be the number of multi-PDSCH scheduling DCIs that schedule multiple (active) PDSCHs, including at least one PDSCH with an HPN set to enable HARQ feedback, in cells with multiple time-domain bundling groups or cells without time-domain bundles. 【0417】 <Plan 2> Terminal 20 may ignore the C-DAI and T-DAI regardless of the values ​​for generating a Type 2 HARQ-ACK codebook. 【0418】 The first subcodebook of option 6-3 mentioned above specifically consists of one of the following options: 【0419】 <Option 6-3A> The DCI related to the first subcodebook may be as follows: • Single PDSCH scheduling DCI with HPN configured to enable HARQ feedback. • Multi-PDSCH scheduling DCI that schedules only one (active) PDSCH with an HPN configured to enable HARQ feedback. • Multi-PDSCH scheduling DCI that schedules multiple (active) PDSCHs in a cell with only one time-domain bundling group configured. • Multi-PDSCH scheduling DCI that schedules multiple (enabled) PDSCHs, including only one PDSCH with an HPN configured to enable HARQ feedback, in cells with multiple time-domain bundling groups configured or cells without time-domain bundlings configured. • DCIs that release SPS, DCIs that instruct Scell ​​to pause (and other DCIs that do not schedule PDSCH) 【0420】 The structure of the first subcodebook may be as follows: ACK / NACK for single PDSCH scheduling DCI that schedules a PDSCH with an HPN configured to have HARQ feedback enabled. ACK / NACK for multi-PDSCH scheduling DCI that schedules only one (valid) PDSCH with an HPN configured to enable HARQ feedback. • Bundled bits indicating ACK / NACK for multiple (valid) PDSCHs scheduled by Multi-PDSCH Scheduling DCI, which schedules multiple (valid) PDSCHs in a cell with only one time-domain bundling group configured. • ACK / NACK for PDSCHs scheduled by a multi-PDSCH scheduling DCI that schedules multiple (enabled) PDSCHs, including only one PDSCH with an HPN configured to enable HARQ feedback, in cells with multiple time-domain bundling groups configured or cells without time-domain bundlings configured. ACK / NACK to DCIs that release SPS, DCIs that instruct Scell ​​to pause (and other DCIs that do not schedule PDSCH) 【0421】 The C-DAI / T-DAI included in the first subcodebook may be as follows: a single PDSCH scheduling DCI that schedules a PDSCH with an HPN configured to enable HARQ feedback; a multi-PDSCH scheduling DCI that schedules multiple (enabled) PDSCHs in a cell with only one time-domain bundling group configured; a multi-PDSCH scheduling DCI that schedules multiple (enabled) PDSCHs, including only one PDSCH with an HPN configured to enable HARQ feedback in a cell with multiple time-domain bundling groups configured or a cell with no time-domain bundlings configured; and other DCIs that do not schedule PDSCHs (e.g., a DCI that releases SPS, a DCI that instructs Scell ​​to pause, etc.). In the case of a C-DAI / T-DAI included in the first subcodebook, the HPN configured to enable HARQ feedback is configured to enable HARQ feedback. This is the number of DCIs that schedule a single PDSCH with N, a multi-PDSCH scheduling DCI that schedules only one (active) PDSCH with an HPN set to enable HARQ feedback, a multi-PDSCH scheduling DCI that schedules multiple (active) PDSCHs in a cell with only one time-domain bundling group, a multi-PDSCH scheduling DCI that schedules multiple (active) PDSCHs, including only one PDSCH with an HPN set to enable HARQ feedback in a cell with multiple time-domain bundling groups or a cell with no time-domain bundlings, and other DCIs that do not schedule PDSCHs (e.g., DCIs that release SPS, DCIs that instruct Scells to pause, etc.). 【0422】 For a single PDSCH scheduling DCI that schedules a PDSCH with an HPN configured to disable HARQ feedback, the C-DAI / T-DAI included in the first subcodebook may be one of the following: 【0423】 <Plan 1> The C-DAI / T-DAI included in the first subcodebook may also be the count of single PDSCH scheduling DCIs that schedule PDSCHs with HPNs configured to enable HARQ feedback, multi-PDSCH scheduling DCIs that schedule only one (active) PDSCH with an HPN configured to enable HARQ feedback, multi-PDSCH scheduling DCIs that schedule multiple (active) PDSCHs in a cell with only one time-domain bundling group configured, multi-PDSCH scheduling DCIs that schedule multiple (active) PDSCHs, including only one PDSCH with an HPN configured to enable HARQ feedback in a cell with multiple time-domain bundling groups configured or a cell with no time-domain bundles configured, and other DCIs that do not schedule PDSCHs (e.g., DCIs that release SPS, DCIs that instruct Scells to pause, etc.). 【0424】 <Plan 2> Terminal 20 may ignore the C-DAI and T-DAI regardless of the values ​​for generating a Type 2 HARQ-ACK codebook. 【0425】 <Option 6-3B> The DCI related to the first subcodebook may be as follows: • Single PDSCH scheduling DCI with HPN configured to enable HARQ feedback. • Multi-PDSCH scheduling DCI that schedules multiple (active) PDSCHs in a cell with only one time-domain bundling group configured. • Multi-PDSCH scheduling DCI that schedules multiple (enabled) PDSCHs, including only one PDSCH with an HPN configured to enable HARQ feedback, in cells with multiple time-domain bundling groups configured or cells without time-domain bundlings configured. • DCIs that release SPS, DCIs that instruct Scell ​​to pause (and other DCIs that do not schedule PDSCH) 【0426】 The structure of the first subcodebook may be as follows: ACK / NACK for single PDSCH scheduling DCI that schedules a PDSCH with an HPN configured to have HARQ feedback enabled. ACK / NACK for multi-PDSCH scheduling DCI that schedules only one (valid) PDSCH with an HPN configured to enable HARQ feedback. NACK for multi-PDSCH scheduling DCI that schedules only one (enabled) PDSCH with an HPN that has HARQ feedback disabled. • Bundled bits indicating ACK / NACK for multiple (valid) PDSCHs scheduled by Multi-PDSCH Scheduling DCI, which schedules multiple (valid) PDSCHs in a cell with only one time-domain bundling group configured. • ACK / NACK for PDSCHs scheduled by a multi-PDSCH scheduling DCI that schedules multiple (enabled) PDSCHs, including only one PDSCH with an HPN configured to enable HARQ feedback, in cells with multiple time-domain bundling groups configured or cells without time-domain bundlings configured. ACK / NACK to DCIs that release SPS, DCIs that instruct Scell ​​to pause (and other DCIs that do not schedule PDSCH) 【0427】 The C-DAI / T-DAI included in the first subcodebook may be as follows: a single PDSCH scheduling DCI that schedules a PDSCH with an HPN configured to enable HARQ feedback; a multi-PDSCH scheduling DCI that schedules only one (enabled) PDSCH; a multi-PDSCH scheduling DCI that schedules multiple (enabled) PDSCHs in a cell with only one time-domain bundling group configured; a multi-PDSCH scheduling DCI that schedules multiple (enabled) PDSCHs, including only one PDSCH with an HPN configured to enable HARQ feedback, in a cell with multiple time-domain bundling groups configured or a cell with no time-domain bundles configured; and other DCIs that do not schedule PDSCHs (e.g., a DCI that releases SPS, a DCI that instructs Scell ​​to pause, etc.). In the case of these, the C-DAI / T-DAI included in the first subcodebook may be as follows: a single PDSCH scheduling DCI that schedules a PDSCH with an HPN configured to enable HARQ feedback; a multi-PDSCH scheduling DCI that schedules only one PDSCH with an HPN configured to enable HARQ feedback; and other DCIs that do not schedule PDSCHs (e.g., a DCI that releases SPS, a DCI that instructs Scell ​​to pause, etc.). This is the count of single PDSCH scheduling DCIs that schedule PDSCHs with HPNs configured to enable RQ feedback, multi-PDSCH scheduling DCIs that schedule only one (active) PDSCH with an HPN configured to enable HARQ feedback, multi-PDSCH scheduling DCIs that schedule multiple (active) PDSCHs in a cell with only one time-domain bundling group configured, multi-PDSCH scheduling DCIs that schedule multiple (active) PDSCHs, including only one PDSCH with an HPN configured to enable HARQ feedback in a cell with multiple time-domain bundling groups configured or a cell with no time-domain bundlings configured, and other DCIs that do not schedule PDSCHs (e.g., DCIs that release SPS, DCIs that instruct Scells to pause, etc.). 【0428】 For a single PDSCH scheduling DCI that schedules a PDSCH with an HPN configured to disable HARQ feedback, the C-DAI / T-DAI included in the first subcodebook may be one of the following: 【0429】 <Plan 1> The C-DAI / T-DAI included in the first subcodebook may also be the count of single PDSCH scheduling DCIs that schedule PDSCHs with HPNs configured to enable HARQ feedback, multi-PDSCH scheduling DCIs that schedule only one (active) PDSCH with an HPN configured to enable HARQ feedback, multi-PDSCH scheduling DCIs that schedule multiple (active) PDSCHs in a cell with only one time-domain bundling group configured, multi-PDSCH scheduling DCIs that schedule multiple (active) PDSCHs, including only one PDSCH with an HPN configured to enable HARQ feedback in a cell with multiple time-domain bundling groups configured or a cell with no time-domain bundles configured, and other DCIs that do not schedule PDSCHs (e.g., DCIs that release SPS, DCIs that instruct Scells to pause, etc.). 【0430】 <Plan 2> Terminal 20 may ignore the C-DAI and T-DAI regardless of the values ​​for generating a Type 2 HARQ-ACK codebook. 【0431】 <Option 6-3C> The DCI related to the first subcodebook may be as follows: • Single PDSCH scheduling DCI • Multi-PDSCH scheduling DCI that schedules only one (active) PDSCH. • Multi-PDSCH scheduling DCI that schedules multiple (active) PDSCHs in a cell with only one time-domain bundling group configured. • Multi-PDSCH scheduling DCI that schedules multiple (enabled) PDSCHs, including only one PDSCH with an HPN configured to enable HARQ feedback, in cells with multiple time-domain bundling groups configured or cells without time-domain bundlings configured. • DCIs that release SPS, DCIs that instruct Scell ​​to pause (and other DCIs that do not schedule PDSCH) 【0432】 The structure of the first subcodebook may be as follows: ACK / NACK for single PDSCH scheduling DCI that schedules a PDSCH with an HPN configured to have HARQ feedback enabled. NACK for single PDSCH scheduling DCI with HPN configured to disable HARQ feedback ACK / NACK for multi-PDSCH scheduling DCI that schedules only one (valid) PDSCH with an HPN configured to enable HARQ feedback. ACK / NACK for multi-PDSCH scheduling DCI that schedules only one (valid) PDSCH with an HPN configured to enable HARQ feedback. • Bundled bits indicating ACK / NACK for multiple (valid) PDSCHs scheduled by Multi-PDSCH Scheduling DCI, which schedules multiple (valid) PDSCHs in a cell with only one time-domain bundling group configured. • ACK / NACK for PDSCHs scheduled by a multi-PDSCH scheduling DCI that schedules multiple (enabled) PDSCHs, including only one PDSCH with an HPN configured to enable HARQ feedback, in cells with multiple time-domain bundling groups configured or cells without time-domain bundlings configured. ACK / NACK to DCIs that release SPS, DCIs that instruct Scell ​​to pause (and other DCIs that do not schedule PDSCH) 【0433】 The C-DAI / T-DAI included in the first subcodebook may be the number of DCIs related to the first subcodebook, including single PDSCH scheduling DCIs that schedule PDSCHs, multi-PDSCH scheduling DCIs that schedule only one (active) PDSCH, multi-PDSCH scheduling DCIs that schedule multiple (active) PDSCHs in a cell with only one time-domain bundling group, multi-PDSCH scheduling DCIs that schedule multiple (active) PDSCHs including only one PDSCH with an HPN set to enable HARQ feedback in a cell with multiple time-domain bundling groups or a cell with no time-domain bundlings, and other DCIs that do not schedule PDSCHs (e.g., DCIs that release SPS, DCIs that instruct Scells to pause, etc.). 【0434】 <Bundling method related to Option 6-3> Terminal 20 may reuse the bundling method related to Option 2 if the number of bundling groups is set to 1 (i.e., the time-domain bundle of the first subcodebook). 【0435】 Furthermore, if the terminal 20 has more than one bundling group (i.e., a time-domain bundle of the second subcodebook), it may reuse the bundling method related to option 6-1. 【0436】 According to this embodiment, a Type 2 HARQ-ACK codebook can be generated in a time-domain bundle manner when multi-PDSCH scheduling and HARQ feedback disabling are combined. 【0437】 (Example 6) This embodiment describes an example in which a terminal 20 performing each option of Embodiment 2 generates a Type 1 HARQ-ACK codebook in a manner that includes a time-domain bundle. 【0438】 (Regarding time-domain bundles) This section describes time-domain bundles in the Type 1 HARQ-ACK codebook. Time-domain bundles configure a HARQ bundling group for sending HARQ-ACKs to multiple PDSCHs together. 【0439】 For multi-PDSCH scheduling using a single DCI, a new RRC parameter (such as enableTimeDomainHARQ-Bundling) is introduced. This RRC parameter enables time-domain bundling for type 1 HARQ-ACK codebooks per serving cell. 【0440】 If the RRC parameter enables time-domain bundling, to determine the set of candidate PDSCH reception opportunities, the row index is removed if at least one symbol of all PDSCHs associated with the row index is configured as a semi-static uplink. This is the same as for slot-aggregated PDSCHs in Release 16. 【0441】 The pruning procedure in Release 16 is performed based on the last configured SLIV for each row index. 【0442】 The logical AND operation is applied to all valid PDSCHs associated with the determined candidate PDSCH reception opportunity, at least for 1TB. 【0443】 When the parameter enableTimeDomainHARQ-Bundling is set, it is worth considering whether terminal 20 should assume that the last scheduled SLIV does not overlap with a semi-static UL symbol. 【0444】 <Terminal operation related to Example 6> For a determined candidate PDSCH reception opportunity, terminal 20 may perform one of the following actions if the TDRA line contains only one SLIV. 【0445】 <Plan 1> Terminal 20 may generate an ACK / NACK if SLIV is enabled and HARQ feedback is enabled in the HPN. Terminal 20 may also generate a NACK if SLIV is disabled or if HARQ feedback is disabled in the HPN. 【0446】 <Plan 2> Terminal 20 may generate an ACK / NACK if SLIV is enabled. Terminal 20 may also generate a NACK if SLIV is disabled. 【0447】 Furthermore, if the TDRA row contains multiple SLIVs, terminal 20 may perform one of the following actions: 【0448】 <Plan 1> Terminal 20 may input an ACK / NACK to an SLIV whose row contains an HPN that is set to enable HARQ feedback. Then, a logical AND operation is applied to the row's bits. 【0449】 <Plan 2> Terminal 20 may input an ACK / NACK for valid SLIVs. Terminal 20 may input an ACK for invalid SLIVs in a row. Then, a logical AND operation is applied to the bits of the row. 【0450】 Furthermore, if terminal 20 has multiple SLIVs in a TDRA row, and each SLIV has an HPN set to disable HARQ feedback, terminal 20 may perform one of the following proposed actions. 【0451】 <Plan 1> Terminal 20 may generate a NACK for the associated candidate PDSCH reception opportunity. 【0452】 <Plan 2> Terminal 20 may input an ACK / NACK for valid SLIVs. Terminal 20 may input an ACK for invalid SLIVs in a row. Then, a logical AND operation is applied to the bits of the row. 【0453】 According to this embodiment, a Type 1 HARQ-ACK codebook can be generated in a time-domain bundle manner when multi-PDSCH scheduling and HARQ feedback disabling are combined. 【0454】 In this embodiment, the multi-PDSCH scheduling DCI may mean a downlink-permitted DCI format consisting of a TDRA table in which at least one row contains multiple SLIVs. 【0455】 In this embodiment, the single PDSCH scheduling DCI may mean a downlink-permitted DCI format consisting of a TDRA table with one SLIV in each row. 【0456】 A "valid PDSCH" may mean a PDSCH that does not conflict with the uplink symbols specified in tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated. 【0457】 An "invalid PDSCH" may mean a PDSCH that conflicts with an uplink symbol specified in tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated. 【0458】 Each of the options described in the above-mentioned embodiments may be any of the following: • Set by parameters of the higher layer. • Reported as terminal capability by terminal 20. • This will be stated in the specifications. • Determined by the settings of the upper layer parameters and the reported terminal capabilities (a combination of the above determinations). 【0459】 Terminal 20 may transmit terminal capability information to base station 10 indicating whether it supports configuring both scheduling of multiple PDSCHs and disabling HARQ feedback (in the same cell) in a single DCI. 【0460】 Terminal 20 may transmit terminal capability information to base station 10 indicating whether it supports time-domain bundles for configuring both scheduling of multiple PDSCHs and disabling HARQ feedback (in the same cell) in a single DCI. 【0461】 Terminal 20 may transmit terminal capability information to base station 10 indicating whether it supports Type 1 HARQ-ACK feedback for scheduling multiple PDSCHs and disabling HARQ feedback (in the same cell) together in a single DCI. 【0462】 Terminal 20 may transmit terminal capability information to base station 10 indicating whether it supports Type 2 HARQ-ACK feedback for scheduling multiple PDSCHs and disabling HARQ feedback (in the same cell) together in a single DCI. 【0463】 (Device configuration) Next, we will describe an example of the functional configuration of the base station 10 and terminal 20 that perform the processes and operations described above. The base station 10 and terminal 20 include functions to perform the embodiments described above. However, the base station 10 and terminal 20 may each be equipped with only one of the proposed functions from the embodiments. 【0464】 <Base station 10> Figure 18 shows an example of the functional configuration of a base station. As shown in Figure 18, 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 Figure 18 is merely an example. The names of the functional categories and functional units can be anything as long as they can perform the operations according to the embodiment of the present invention. The transmitting unit 110 and the receiving unit 120 may be called the communication unit. 【0465】 The transmitting unit 110 includes the function of generating a signal to be transmitted to the terminal 20 and transmitting the signal wirelessly. The receiving unit 120 includes the function of receiving various signals transmitted from the terminal 20 and obtaining information from the received signals, for example, information of a higher layer. The transmitting unit 110 also has the function of transmitting NR-PSS, NR-SSS, NR-PBCH, DL / UL control signals, DL data, etc. to the terminal 20. The transmitting unit 110 also transmits setting information, etc., as described in the embodiment. 【0466】 The setting unit 130 stores pre-configured setting information and various setting information to be transmitted to the terminal 20 in a storage device and reads it from the storage device as needed. The control unit 140 performs control of the entire base station 10, including control related to signal transmission and reception. The signal transmission function unit of the control unit 140 may be included in the transmission unit 110, and the signal reception function unit of the control unit 140 may be included in the reception unit 120. The transmission unit 110 and the reception unit 120 may also be called the transmitter and receiver, respectively. 【0467】 <Terminal 20> Figure 19 shows an example of the functional configuration of a terminal. As shown in Figure 19, 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 Figure 19 is merely an example. The names of the functional categories and functional units can be anything as long as they can perform the operations according to the embodiment of the present invention. The transmitting unit 210 and the receiving unit 220 may be called the communication unit. 【0468】 The transmitting unit 210 creates a transmission signal from the transmission data and transmits the transmission signal wirelessly. The receiving unit 220 wirelessly receives various signals and obtains signals from higher layers from the received physical layer signals. The transmitting unit 210 also transmits a HARQ-ACK, and the receiving unit 220 receives the configuration information and the like as described in the embodiment. 【0469】 The setting unit 230 stores various setting information received from the base station 10 by the receiving unit 220 in a storage device and reads it from the storage device as needed. The setting unit 230 also stores pre-set setting information. The control unit 240 controls the entire terminal 20, including control related to signal transmission and reception. The signal transmission function in the control unit 240 may be included in the transmission unit 210, and the signal reception function in the control unit 240 may be included in the reception unit 220. The transmission unit 210 and the reception unit 220 may also be called the transmitter and receiver, respectively. 【0470】 The terminal or base station of this embodiment may be configured as one of the terminals or base stations described in the following sections. Furthermore, the following communication methods may be implemented. 【0471】 <Configuration of this embodiment> (Section 1) A receiving unit that receives control information via downlink, including information for scheduling multiple downlink shared signals and information indicating that feedback to the downlink shared signals should be disabled. The system includes a control unit that determines whether or not to transmit feedback information to the downlink shared signal based on whether or not feedback to the downlink shared signal is set to enabled or disabled in the control information. Terminal. (Section 2) The control unit, if feedback to any of the multiple downlink shared signals specified in the control information is disabled, determines whether or not to transmit feedback information for each downlink shared signal based on whether the feedback is set to be enabled or disabled. The terminal described in paragraph 1. (Section 3) The control unit decides not to transmit feedback information for any of the multiple downlink shared signals specified in the control information if feedback to any of the downlink shared signals specified in the control information is disabled. The terminal described in paragraph 1. (Section 4) The control unit decides whether to transmit or not transmit feedback information for any of the multiple downlink shared signals specified in the control information, regardless of whether feedback to any of the downlink shared signals is disabled. The terminal described in paragraph 1. (Section 5) A transmitting unit that transmits control information to a terminal, including information for scheduling multiple downlink shared signals and information indicating that feedback to the downlink shared signals should be disabled. The control unit includes a control unit which assumes that the terminal will decide whether or not to transmit feedback information to the downlink shared signal based on whether or not feedback to the downlink shared signal is set to enabled or disabled in the control information, Base station. (Section 6) The steps include receiving control information on the downlink, which includes information for scheduling multiple downlink shared signals and information indicating that feedback to the downlink shared signals should be disabled, The system includes the step of determining whether or not to transmit feedback information to the downlink shared signal based on whether or not feedback to the downlink shared signal is set to enabled or disabled in the control information. The communication method used by the terminal. 【0472】 Any of the above configurations provides a technology that enables the application of wireless communication systems to high frequency bands. According to paragraph 2, for each downlink shared signal, it is possible to decide whether or not to transmit feedback information based on whether feedback is set to be enabled or disabled. According to paragraph 3, if feedback to any of the downlink shared signals is disabled, feedback information may not be transmitted for the multiple downlink shared signals specified in the control information. According to paragraph 4, it can be assumed that the terminal decides whether or not to transmit feedback information to the downlink shared signal based on whether feedback to the downlink shared signal is set to be enabled or disabled in the control information. 【0473】 (Hardware configuration) The block diagrams (Figures 18 and 19) used in the description of the above embodiments show functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may be realized by combining the one or more devices with software. 【0474】 Functions include, but are not limited to, judgment, decision, judgment, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, assumption, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission is called a transmitting unit or transmitter. As mentioned above, the method of implementation is not particularly limited. 【0475】 For example, the base station 10, terminal 20, etc. in one embodiment of the present disclosure may function as a computer that processes the wireless communication method of the present disclosure. Figure 20 is a diagram showing an example of the hardware configuration of the base station 10 and terminal 20 according to one embodiment of the present disclosure. The above-mentioned base station 10 and terminal 20 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. 【0476】 In the following explanation, the term "device" can be replaced with "circuit," "device," "unit," etc. The hardware configuration of the base station 10 and terminal 20 may include one or more of the devices shown in the figure, or it may be configured to omit some of the devices. 【0477】 Each function in the base station 10 and terminal 20 is realized by loading predetermined software (programs) onto hardware such as the processor 1001 and storage device 1002, which allows the processor 1001 to perform calculations, control communication by the communication device 1004, and control at least one of the reading and writing of data in the storage device 1002 and auxiliary storage device 1003. 【0478】 The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may consist of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc. For example, the control unit 140, control unit 240, etc., described above may be implemented by the processor 1001. 【0479】 Furthermore, the processor 1001 reads programs (program code), software modules, or data from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002, and executes various processes accordingly. The program used is one that causes a computer to execute at least a part of the operations described in the above embodiment. For example, the control unit 140 of the base station 10 shown in Figure 18 may be implemented by a control program stored in the storage device 1002 and operated by the processor 1001. Also, for example, the control unit 240 of the terminal 20 shown in Figure 19 may be implemented by a control program stored in the storage device 1002 and operated by the processor 1001. Although the above processes have been described as being executed by one processor 1001, they may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The program may be transmitted from the network via a telecommunications line. 【0480】 The storage device 1002 is a computer-readable recording medium and may consist of at least one of the following: ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. The storage device 1002 may also be called a register, cache, main memory, etc. The storage device 1002 can store executable programs (program code), software modules, etc., for implementing a communication method according to one embodiment of this disclosure. 【0481】 The auxiliary storage device 1003 is a computer-readable recording medium and may consist of at least one of the following: an optical disc such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disc, a digital multipurpose disc, a Blu-ray® disc), a smart card, flash memory (e.g., a card, a stick, a key drive), a floppy® disk, a magnetic strip, etc. The above-mentioned storage medium may also be a database, server, or other suitable medium that includes at least one of the storage device 1002 and the auxiliary storage device 1003. 【0482】 The communication device 1004 is hardware (transceiver / receiver device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc. The communication device 1004 may include high-frequency switches, duplexers, filters, frequency synthesizers, etc., to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the transmit / receive antenna, amplifier section, transmit / receive section, transmission path interface, etc., may be implemented by the communication device 1004. The transmit / receive section may be implemented with physically or logically separated transmitting and receiving sections. 【0483】 The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, LED lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel). 【0484】 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 different buses may be configured for each device. 【0485】 Furthermore, the base station 10 and terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), and an FPGA (Field Programmable Gate Array), and some or all of each functional block may be realized by such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components. 【0486】 Figure 21 shows an example of the configuration of vehicle 2001. As shown in Figure 21, vehicle 2001 comprises a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021-2029, an information service unit 2012, and a communication module 2013. Each aspect / embodiment described in this disclosure may be applied to a communication device mounted on vehicle 2001, for example, to the communication module 2013. 【0487】 The drive unit 2002 consists of, for example, an engine, a motor, or a hybrid of an engine and a motor. The steering unit 2003 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, which is operated by the user. 【0488】 The electronic control unit 2010 consists of a microprocessor 2031, memory (ROM, RAM) 2032, and communication ports (IO ports) 2033. Signals from various sensors 2021 to 2029 installed in the vehicle 2001 are input to the electronic control unit 2010. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit). 【0489】 Signals from various sensors 2021-2029 include current signals from current sensor 2021 which senses motor current, front and rear wheel rotation speed signals obtained by rotation speed sensor 2022, front and rear wheel air pressure signals obtained by air pressure sensor 2023, vehicle speed signals obtained by vehicle speed sensor 2024, acceleration signals obtained by acceleration sensor 2025, accelerator pedal depression signals obtained by accelerator pedal sensor 2029, brake pedal depression signals obtained by brake pedal sensor 2026, shift lever operation signals obtained by shift lever sensor 2027, and detection signals obtained by object detection sensor 2028 for detecting obstacles, vehicles, pedestrians, etc. 【0490】 The Information Services Unit 2012 consists of various devices for providing various types of information, such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, television, and radio, and one or more ECUs that control these devices. The Information Services Unit 2012 uses information acquired from external devices via a communication module 2013, etc., to provide various multimedia information and multimedia services to the occupants of the vehicle 2001. 【0491】 The driver assistance system unit 2030 consists of various devices that provide functions to prevent accidents or reduce the driver's workload, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS), 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 driver assistance system unit 2030 also sends and receives various information via the communication module 2013 to realize driver assistance functions or autonomous driving functions. 【0492】 The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 2001 via its communication port. For example, the communication module 2013 sends and receives data via its communication port 2033 to the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, the microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021-29 provided in the vehicle 2001. 【0493】 The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with external devices. For example, it can send and receive various types of information to and from external devices via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station or a mobile station. 【0494】 The communication module 2013 transmits current signals from current sensors input to the electronic control unit 2010 to an external device via wireless communication. The communication module 2013 also transmits, via wireless communication, other signals input to the electronic control unit 2010, including front and rear wheel rotation speed signals obtained by the rotation speed sensor 2022, front and rear wheel air pressure signals obtained by the air pressure sensor 2023, vehicle speed signals obtained by the vehicle speed sensor 2024, acceleration signals obtained by the acceleration sensor 2025, accelerator pedal depression signals obtained by the accelerator pedal sensor 2029, brake pedal depression signals obtained by the brake pedal sensor 2026, shift lever operation signals obtained by the shift lever sensor 2027, and detection signals obtained by the object detection sensor 2028 for detecting obstacles, vehicles, pedestrians, etc. 【0495】 The communication module 2013 receives various information (traffic information, signal information, distance information, etc.) transmitted from an external device and displays it on the information service unit 2012 installed in the vehicle 2001. The communication module 2013 also stores the various information received from the external device in memory 2032, which is available to the microprocessor 2031. Based on the information stored in memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axles 2009, sensors 2021-2029, etc., installed in the vehicle 2001. 【0496】 (Supplement to the embodiment) While 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, substitutions, etc. Specific numerical examples have been used to facilitate understanding of the invention, but 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, and matters described in two or more items may be combined as needed, and matters described in one item may be applied to matters described in another item (as long as they do not contradict each other). The boundaries of functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of physical parts. The operation of multiple functional units may be physically performed by one part, or the operation of one functional unit may be physically performed by multiple parts. Regarding the processing procedures described in the embodiments, the order of processing may be changed as long as it does not contradict each other. For the convenience of explaining the processing, the base station 10 and terminal 20 have been described using functional block diagrams, but such devices may be implemented in hardware, software, or a combination thereof. The software operated by the processor of the base station 10 according to an embodiment of the present invention and the software operated by the processor of the terminal 20 according to an embodiment of the present invention may 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. 【0497】 Furthermore, the notification of information is not limited to the embodiments / models described herein and may be carried out by other methods. For example, the notification of information may be carried out by physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), upper layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling), broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals, or combinations thereof. Also, RRC signaling may be called RRC messages, and may be, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc. 【0498】 Each aspect / embodiment described in this disclosure includes LTE (Long Term Evolution), LTE-A (LTE-Advanced), 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 (where x is, for example, an integer or decimal)), 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)), and IEEE This may apply to at least one system utilizing 802.20, UWB (Ultra-WideBand), Bluetooth®, or other appropriate systems, and to next-generation systems extended, modified, created, or defined based thereon. It may also apply to a combination of multiple systems (for example, a combination of at least one of LTE and LTE-A with 5G). 【0499】 The processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described herein may be reordered, provided they are consistent with each other. For example, the methods described herein present various step elements in an exemplary order and are not limited to that specific order. 【0500】 In this specification, specific operations performed by the base station 10 may, in some cases, be performed by its upper node. In a network consisting of one or more network nodes having a base station 10, it is clear that various operations performed for communication with the terminal 20 can be performed by the base station 10 and at least one of the other network nodes (for example, an MME or S-GW, but not limited to these). Although the above example illustrates the case where there is one other network node besides the base station 10, the other network node may be a combination of multiple other network nodes (for example, an MME and an S-GW). 【0501】 The information or signals described in this disclosure may be output from a higher layer (or lower layer) to a lower layer (or higher layer). They may also be input and output via multiple network nodes. 【0502】 Input and output information may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information may be overwritten, updated, or appended to. Output information may be deleted. Input information may be transmitted to other devices. 【0503】 The determination in this disclosure may be made by a value represented by one bit (0 or 1), by a boolean value (true or false), or by a numerical comparison (for example, a comparison with a predetermined value). 【0504】 Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name. 【0505】 Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technology (such as coaxial cable, fiber optic cable, twisted pair, or digital subscriber line (DSL)) and wireless technology (such as infrared or microwave), then at least one of these wired and wireless technologies is included in the definition of a transmission medium. 【0506】 The information, signals, etc. described in this disclosure may be represented using any of the various different techniques. For example, the data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof. 【0507】 In addition, terms used 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 the channel and symbol may be a signal (signaling). Also, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, cell, frequency carrier, etc. 【0508】 The terms “system” and “network” as used in this disclosure are interchangeable. 【0509】 Furthermore, the information, parameters, etc., described in this disclosure may be expressed using absolute values, relative values ​​from a given value, or other corresponding information. For example, wireless resources may be indicated by an index. 【0510】 The names used for the parameters described above are not restrictive in any way. Furthermore, the formulas and other expressions using these parameters may differ from those expressly disclosed in this disclosure. Various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, and therefore, the various names assigned to these various channels and information elements are not restrictive in any way. 【0511】 In this disclosure, terms such as "Base Station (BS)", "wireless 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. 【0512】 A base station can house one or more (e.g., three) cells. If a base station houses multiple cells, the entire coverage area of ​​the base station can be divided into several smaller areas, each of which may also be provided with communication services by a base station subsystem (e.g., a Remote Radio Head (RRH)). The terms “cell” or “sector” refer to part or all of the coverage area of ​​at least one of the base station and / or base station subsystems that provide communication services in that coverage. 【0513】 In this disclosure, terms such as "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" may be used interchangeably. 【0514】 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 several other appropriate terms. 【0515】 At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile body, the mobile body itself, etc. The mobile body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does not necessarily move during communication operation. 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. 【0516】 Furthermore, the term "base station" in this disclosure may be interpreted as "user terminal." For example, the various aspects / embodiments of this disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple terminals 20 (which may be called, for example, D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.). In this case, the terminals 20 may have the functions that the base station 10 has. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, uplink channel, downlink channel, etc., may be interpreted as side channel. 【0517】 Similarly, the term "user terminal" in this disclosure may be replaced with "base station." In this case, the base station may be configured to have the same functions as the user terminal described above. 【0518】 As used in this disclosure, the terms “determining” and “determining” may encompass a wide variety of actions. “Determining” may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiry (e.g., searching in a table, database, or other data structure), and ascertaining. “Determining” may also include, for example, receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, and accessing (e.g., accessing data in memory). Furthermore, "judgment" and "decision" can include considering something as having been "judged" or "decided" after resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment" and "decision" can include considering something as having been "judged" or "decided" after some action. Also, "judgment (decision)" can be reinterpreted as "assuming," "expecting," or "considering." 【0519】 The terms “connected,” “coupled,” or any variation thereof, mean 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” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be reinterpreted as “access.” As used in this disclosure, two elements may be considered to be “connected” or “coupled” with each other using at least one of one or more wires, cables, and printed electrical connections, and, in some non-limiting and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, and optical (both visible and invisible) domain. 【0520】 The reference signal can also be abbreviated as RS (Reference Signal), and may be called a pilot depending on the applicable standard. 【0521】 In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on." 【0522】 Any reference to elements using the designations “first,” “second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, references to the first and second elements do not imply that only two elements may be employed, or that the first element must precede the second element in any way. 【0523】 In the configuration of each of the above devices, "means" may be replaced with "part," "circuit," "device," etc. 【0524】 Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR. 【0525】 A wireless frame may consist of one or more frames in the time domain. Each of these frames in the time domain may be called a subframe. A subframe may further consist 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. 【0526】 Numerical logic may be communication parameters applied to at least one of the transmission and reception of a signal or channel. Numerical logic may include, for example, at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processes performed by the transceiver in the frequency domain, and specific windowing processes performed by the transceiver in the time domain. 【0527】 A slot may consist of one or more symbols in the time domain (such as OFDM (Orthogonal Frequency Division Multiplexing) symbols, SC-FDMA (Single Carrier Frequency Division Multiple Access) symbols, etc.). A slot may also be a time unit based on neurology. 【0528】 A slot may include multiple minislots. Each minislot may consist of one or more symbols in the time domain. Minislots may also be called subslots. Minislots 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. 【0529】 Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Different names may be used for each of these terms. 【0530】 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 mini-slot may be called a TTI. In other words, at least one of a subframe and a TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, mini-slot, etc., instead of a subframe. 【0531】 Here, TTI refers to, for example, the smallest unit of time for scheduling in wireless communication. For example, in an LTE system, the base station schedules each terminal 20 to allocate wireless resources (such as the frequency bandwidth and transmission power available to each terminal 20) in TTI units. However, the definition of TTI is not limited to this. 【0532】 TTI may be a transmission time unit for channel-encoded data packets (transport blocks), code blocks, code words, etc., or it may be a processing unit for scheduling, link adaptation, etc. Given a TTI, the actual time interval (e.g., number of symbols) to which the transport block, code block, code word, etc. are mapped may be shorter than the given TTI. 【0533】 Furthermore, if one slot or one mini-slot is referred to as TTI, then one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute the minimum time unit of scheduling. In addition, the number of slots (number of mini-slots) that constitute the minimum time unit of scheduling may be controlled. 【0534】 A TTI with a time length of 1ms may also be called a normal TTI, long TTI, normal subframe, long subframe, slot, etc. A TTI shorter than a normal TTI may also be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, mini slot, sub slot, slot, etc. 【0535】 Furthermore, long TTIs (e.g., normal TTIs, subframes, etc.) may be interpreted as TTIs with a time length exceeding 1 ms, and short TTIs (e.g., shortened TTIs, etc.) may be interpreted as TTIs with a TTI length less than that of a long TTI but 1 ms or more. 【0536】 A resource block (RB) is a resource allocation unit in the time domain and frequency domain, and in the frequency domain, it may contain one or more consecutive subcarriers. The number of subcarriers in an RB may be the same regardless of the neurology, for example, 12. The number of subcarriers in an RB may be determined based on the neurology. 【0537】 Furthermore, the time domain of RB may contain one or more symbols and may be the length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc., may each consist of one or more resource blocks. 【0538】 One or more RBs may also be called a Physical RB (PRB), Sub-Carrier Group (SCG), Resource Element Group (REG), PRB pair, RB pair, etc. 【0539】 Furthermore, a resource block may consist of one or more resource elements (REs). For example, one RE may be a radio resource area comprising one subcarrier and one symbol. 【0540】 A Bandwidth Part (BWP), also known as a partial bandwidth, may represent a subset of consecutive common resource blocks (RBs) for a particular neurology system in a given carrier. These common RBs may be identified by an index of the RBs relative to a common reference point of the carrier. A Bandwidth Part (PRB) may be defined and numbered within a given BWP. 【0541】 A BWP may include a BWP for UL (Ultraviolet Link) and a BWP for DL ​​(Download Link). One or more BWPs may be set for a terminal 20 within a single carrier. 【0542】 At least one of the configured BWPs may be active, and terminal 20 does not need to be expected to send or receive a predetermined signal / channel outside of the active BWP. In this disclosure, terms such as "cell" and "carrier" may be read as "BWP". 【0543】 The structures described above, such as wireless frames, subframes, slots, minislots, and symbols, are merely illustrative. For example, the number of subframes included in a wireless frame, the number of slots per subframe or wireless 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, and the number of symbols, symbol length, and cyclic prefix (CP) length within a TTI can be varied in various ways. 【0544】 In this disclosure, if articles are added through translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural. 【0545】 In this 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 "combine" may be interpreted similarly to "different." 【0546】 Each aspect / embodiment described herein may be used individually, in combination, or switched between as needed during implementation. Furthermore, notification of specific information (e.g., notification that "X is") is not limited to explicit notification, but may also be implicit (e.g., by not providing such notification). 【0547】 Although the present disclosure has been described in detail above, it will be 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 intent and scope of the present disclosure as defined by the claims. Therefore, the descriptions in the present disclosure are illustrative and not intended to be restrictive in any way. [Explanation of Symbols] 【0548】 10 base station 110 Transmitter 120 Receiver 130 Setting section 140 Control Unit 20 devices 210 Transmitter 220 Receiver 230 Setting section 240 Control Unit 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device 2001 Vehicle 2002 Drive Unit 2003 Steering Department 2004 Accelerator pedal 2005 Brake pedal 2006 Shift Lever 2007 Front Wheel 2008 Rear wheel 2009 Axle 2010 Electronic Control Unit 2012 Information Services Department 2013 Communication Module 2021 Current Sensor 2022 Rotation speed sensor 2023 Pneumatic Sensor 2024 Vehicle Speed ​​Sensor 2025 Accelerometer 2026 Brake Pedal Sensor 2027 Shift lever sensor 2028 Object Detection Sensor 2029 Accelerator pedal sensor 2030 Driver Support Systems Department 2031 Microprocessor 2032 memory (ROM, RAM) 2033 Communication port (I / O port)

Claims

[Claim 1] A receiving unit that receives control information via downlink, including information for scheduling multiple downlink shared signals and information indicating that feedback to the downlink shared signals should be disabled. The system includes a control unit that determines whether or not to transmit feedback information to the downlink shared signal based on whether or not feedback to the downlink shared signal is set to enabled or disabled in the control information. Terminal. [Claim 2] The control unit, if feedback to any of the multiple downlink shared signals specified in the control information is disabled, determines whether or not to transmit feedback information for each downlink shared signal based on whether the feedback is set to be enabled or disabled. The terminal according to claim 1. [Claim 3] The control unit decides not to transmit feedback information for any of the multiple downlink shared signals specified in the control information if feedback to any of the downlink shared signals specified in the control information is disabled. The terminal according to claim 1. [Claim 4] The control unit decides whether to transmit or not transmit feedback information for any of the multiple downlink shared signals specified in the control information, regardless of whether feedback to any of the downlink shared signals is disabled. The terminal according to claim 1. [Claim 5] A transmitting unit that transmits control information to a terminal, including information for scheduling multiple downlink shared signals and information indicating that feedback to the downlink shared signals should be disabled. The control unit includes a control unit which assumes that the terminal will decide whether or not to transmit feedback information to the downlink shared signal based on whether or not feedback to the downlink shared signal is set to enabled or disabled in the control information, Base station. [Claim 6] The steps include receiving control information on the downlink, which includes information for scheduling multiple downlink shared signals and information indicating that feedback to the downlink shared signals should be disabled, The system includes the step of determining whether or not to transmit feedback information to the downlink shared signal based on whether or not feedback to the downlink shared signal is set to enabled or disabled in the control information. The communication method used by the terminal.

Images