Terminal device and communication method

Abstract

The terminal device has: a receiving unit that receives a PDCCH including a DCI that triggers a type 3 HARQ-ACK codebook; and a transmitting unit that transmits a PUCCH including the triggered type 3 HARQ-ACK codebook, the slot in which the PUCCH is transmitted being given based on K1 obtained from a PDSCH-to-HARQ_feedback timing indicator field included in the DCI, the PUCCH being transmitted K1 slots after the slot in which the PDSCH is received in the case where the DCI schedules the PDSCH, the PUCCH being transmitted in a slot that is a slot after the slot in which the PDCCH is received corresponding to K1 in the case where the DCI does not schedule the PDSCH.

Description

TECHNICAL FIELD

[0001] The present application relates to a terminal device and a communication method.

[0002] This application claims priority from Japanese Patent Application No. 2020-22477 filed on February 13, 2020, the contents of which are incorporated herein by reference. BACKGROUND

[0003] In the 3rd Generation Partnership Project (3GPP), a wireless access scheme and a radio network for cellular mobile communication (hereinafter referred to as "Long Term Evolution (LTE)" or "Evolved Universal Terrestrial Radio Access (EUTRA)") are studied. In LTE, a base station device is also referred to as an eNodeB (evolved NodeB), and a terminal device is also referred to as a UE (User Equipment). LTE is a cellular communication system in which a plurality of base station devices are arranged in a cell-shaped area covered by the base station devices. A single base station device can manage a plurality of serving cells.

[0004] In the 3GPP, a next-generation standard (NR: New Radio) is studied for the purpose of making a proposal to the IMT (International Mobile Telecommunication)-2020, which is a standard for the next-generation mobile communication system established by the International Telecommunication Union (ITU) (Non-Patent Literature 1). NR is required to satisfy requirements assumed for three scenarios: eMBB (enhanced Mobile BroadBand), mMTC (massive Machine Type Communication), and URLLC (Ultra Reliable and Low Latency Communication) in a single technical framework.

[0005] Further, application of NR to an unlicensed spectrum is studied (Non-Patent Literature 2). It is studied to apply NR supporting a 100 MHz wide band to a carrier in an unlicensed spectrum to achieve a data rate of several Gbps.

[0006] Prior art documents

[0007] Non-patent literature

[0008] Non-patent literature 1: "New SID proposal: Study on New Radio Access Technology", RP-160671, NTT docomo, 3GPP TSG RAN Meeting #71, Goteborg, Sweden, 7th-10th March, 2016.

[0009] Non-patent literature 2: "New WID on NR-based Access to Unlicensed Spectrum", RP-182878, Qualcomm Incorporated, 3GPP TSG RAN Meeting #82, Sorrento, Italy, 10th-13th December, 2018.

[0010] Non-patent literature 3: "3GPP TS 38.211 V16.0.0 (2019-12), NR; Physical channels and modulation".

[0011] Non-patent literature 4: "3GPP TS 38.212 V16.0.0 (2019-12), NR; Multiplexing and channel coding".

[0012] Non-patent literature 5: "3GPP TS 38.213 V16.0.0 (2019-12), NR; Physical layer procedures for control".

[0013] Non-patent literature 6: "3GPP TS 38.214 V16.0.0 (2019-12), NR; Physical layer procedures for data". SUMMARY

[0014] Problems to be solved by the invention

[0015] One embodiment of the present invention provides a terminal device that can efficiently perform uplink transmission and / or reception of downlink transmission, a communication method for the terminal device, a base station device that can efficiently perform downlink transmission and / or reception of uplink transmission, and a communication method for the base station device.

[0016] Technical Solution

[0017] (1) The first aspect of the present application is a terminal device including: a reception section that receives a PDCCH including DCI that triggers a Type 3 HARQ-ACK codebook; and a transmission section that transmits a PUCCH including the triggered Type 3 HARQ-ACK codebook, the slot in which the PUCCH is transmitted being given based on K1 obtained from a PDSCH-to-HARQ_feedback timing indicator field included in the DCI, the PUCCH being transmitted K1 slots after the slot in which the PDSCH is received in a case where the DCI schedules the PDSCH, the PUCCH being transmitted in a slot that is a slot after the K1 in a case where the DCI does not schedule the PDSCH.

[0018] (2) The second aspect of the present application is a terminal device including: a reception section that receives a PDCCH including DCI that triggers a Type 3 HARQ-ACK codebook; and a transmission section that transmits a PUCCH including the triggered Type 3 HARQ-ACK codebook, the slot in which the PUCCH is transmitted being given based on K1 obtained from a PDSCH-to-HARQ_feedback timing indicator field included in the DCI, the PUCCH being transmitted K1 slots after the slot in which the PDSCH is received in a case where the DCI schedules the PDSCH, the PUCCH being transmitted in a slot that is a slot after the K1 in a case where the DCI does not schedule the PDSCH, the slot being indicated by a value of a TDRA field included in the DCI.

[0019] (3) The third aspect of the present application is a base station device including: a transmission section that transmits a PDCCH including DCI that triggers a Type 3 HARQ-ACK codebook; and a reception section that receives a PUCCH including the triggered Type 3 HARQ-ACK codebook, the slot in which the PUCCH is received being given based on K1 obtained from a PDSCH-to-HARQ_feedback timing indicator field included in the DCI, the PUCCH being received K1 slots after the slot in which the PDSCH is transmitted in a case where the DCI schedules the PDSCH, the PUCCH being received in a slot that is a slot after the K1 in a case where the DCI does not schedule the PDSCH, the slot being indicated by a value of a TDRA field included in the DCI.

[0020] (4) The fourth aspect of the present application is a base station device including: a transmission unit that transmits a PDCCH including DCI that triggers a Type 3 HARQ-ACK codebook; and a reception unit that receives a PUCCH including the triggered Type 3 HARQ-ACK codebook, the slot in which the PUCCH is received being given based on K1 obtained from a PDSCH-to-HARQ_feedback timing indicator field included in the DCI, the PUCCH being received K1 slots after the slot in which the PDSCH is transmitted in a case where the DCI schedules a PDSCH, the PUCCH being received in a slot that is a slot after the K1 corresponding to the slot in which the PDSCH is transmitted in a case where the DCI does not schedule a PDSCH.

[0021] (5) The fifth aspect of the present application is a communication method for a terminal device including: a step of receiving a PDCCH including DCI that triggers a Type 3 HARQ-ACK codebook; and a step of transmitting a PUCCH including the triggered Type 3 HARQ-ACK codebook, the slot in which the PUCCH is transmitted being given based on K1 obtained from a PDSCH-to-HARQ_feedback timing indicator field included in the DCI, the PUCCH being transmitted K1 slots after the slot in which the PDSCH is received in a case where the DCI schedules a PDSCH, the PUCCH being transmitted in a slot that is a slot after the K1 corresponding to the slot in which the PDCCH is received in a case where the DCI does not schedule a PDSCH.

[0022] (6) The sixth aspect of the present application is a communication method for a terminal device including: a step of receiving a PDCCH including DCI that triggers a Type 3 HARQ-ACK codebook; and a step of transmitting a PUCCH including the triggered Type 3 HARQ-ACK codebook, the slot in which the PUCCH is transmitted being given based on K1 obtained from a PDSCH-to-HARQ_feedback timing indicator field included in the DCI, the PUCCH being transmitted K1 slots after the slot in which the PDSCH is received in a case where the DCI schedules a PDSCH, the PUCCH being transmitted in a slot that is a slot after the K1 corresponding to the slot in which the PDSCH is received in a case where the DCI does not schedule a PDSCH.

[0023] (7) The seventh aspect of the present application is a communication method for a base station device, a communication method for a base station device including a step of transmitting a PDCCH including DCI that triggers a Type 3 HARQ-ACK codebook, and a step of receiving a PUCCH including the triggered Type 3 HARQ-ACK codebook, the slot in which the PUCCH is received being given based on K1 obtained from a PDSCH-to-HARQ_feedback timing indicator field included in the DCI, the PUCCH being received K1 slots after the slot in which the PDSCH is transmitted in a case where the DCI schedules a PDSCH, the PUCCH being received in a slot that is a slot after the K1 in a case where the DCI does not schedule a PDSCH.

[0024] (8) The eighth aspect of the present application is a communication method for a base station device, a communication method for a base station device including a step of transmitting a PDCCH including DCI that triggers a Type 3 HARQ-ACK codebook, and a step of receiving a PUCCH including the triggered Type 3 HARQ-ACK codebook, the slot in which the PUCCH is received being given based on K1 obtained from a PDSCH-to-HARQ_feedback timing indicator field included in the DCI, the PUCCH being received K1 slots after the slot in which the PDSCH is transmitted in a case where the DCI schedules a PDSCH, the PUCCH being received in a slot that is a slot after the K1 in a case where the DCI does not schedule a PDSCH, the slot in which the PUCCH is received being given based on a value indicated by a TDRA field included in the DCI.

[0025] Advantageous Effects

[0026] According to one aspect of the present application, a terminal device can efficiently perform communication. Furthermore, a base station device can efficiently perform communication. BRIEF DESCRIPTION OF DRAWINGS

[0027] Figure 1 is a conceptual diagram of a wireless communication system that is one aspect of the present embodiment.

[0028] Figure 2 is a diagram showing one example of an N slot symb , one example of the relationship of the subcarrier spacing setting μ, the slot setting, and the CP setting.

[0029] Figure 3 is a diagram showing one example of a resource grid in a subframe that is one aspect of the present embodiment.

[0030] Figure 4is a schematic block diagram showing the configuration of the terminal device 1 of one scheme of the present embodiment.

[0031] Figure 5 is a schematic block diagram showing the configuration of the base station device 3 of one scheme of the present embodiment.

[0032] Figure 6 is a diagram showing one example of reception of the SPS PDSCH of the present embodiment.

[0033] Figure 7 is a diagram showing one example of the Type 3 HARQ-ACK codebook in the case where the SPS PDSCH is not configured in the present embodiment.

[0034] Figure 8 is a diagram showing one example of the reporting of the HARQ-ACK information corresponding to the PDSCH scheduled by the DL grant and the SPS PDSCH in the case where the SPS PDSCH is configured in the terminal device 1 of the present embodiment.

[0035] Hereinafter, an embodiment of the present application will be described.

[0036] "A and / or B" can be a term including "A", "B", or "A and B".

[0037] A parameter or information indicates that one or more values can be the parameter or the information at least including a parameter or information indicating the one or more values. The upper layer parameter can be a single upper layer parameter. The upper layer parameter can also be an information element (IE) including a plurality of parameters.

[0038] Figure 1 is a conceptual diagram of a wireless communication system of one scheme of the present embodiment. In Figure 1 , the wireless communication system has the terminal devices 1A to 1C and the base station device 3 (gNB). Hereinafter, the terminal devices 1A to 1C will also be referred to as terminal devices 1 (UE).

[0039] The base station device 3 can be configured to include one or both of a MCG (Master Cell Group) and a SCG (Secondary Cell Group). The MCG is a group of serving cells including at least a PCell (Primary Cell). The SCG is a group of serving cells including at least a PSCell (Primary Secondary Cell). The PCell can be a serving cell given based on initial connection. The MCG can also be configured to include one or more SCells (Secondary Cells). The SCG can also be configured to include one or more SCells. A serving cell identity is a short identifier for identifying a serving cell. The serving cell identity can be given by an upper layer parameter.

[0040] Hereinafter, a frame structure is described.

[0041] In the wireless communication system of one aspect of the present embodiment, at least OFDM (Orthogonal Frequency Division Multiplex) is used. An OFDM symbol is a unit of time domain of OFDM. The OFDM symbol includes at least one or more subcarriers. The OFDM symbol can be converted into a time-continuous signal in baseband signal generation.

[0042] A subcarrier spacing (SCS) can be given by a subcarrier spacing Δf = 2 μ kHz. For example, a subcarrier spacing configuration μ of the subcarrier spacing can be set to any one of 0, 1, 2, 3, 4, and / or 5. The subcarrier spacing configuration μ can be given by an upper layer parameter for a certain BWP (BandWidth Part).

[0043] In the wireless communication system of one aspect of the present embodiment, a time unit T c is used to express a length of a time domain. The time unit T c may be given by T c = 1 / (Δf max · N f ). Δf max may be a maximum value of a subcarrier spacing supported in the wireless communication system of one aspect of the present embodiment. Δf max may also be Δfmax = 480 kHz. N f may be N f = 4096. The constant κ is κ = Δf max · N f / (Δf ref N f，ref ) = 64. Δf ref may be 15 kHz. N f，ref may be 2048.

[0044] The constant κ can also be a value indicating a relationship of a reference subcarrier spacing to T c . The constant κ can be used for a length of a subframe. A number of slots included in the subframe can be given based on at least the constant κ. Δf ref is a reference subcarrier spacing, N f，ref is a value corresponding to the reference subcarrier spacing.

[0045] The transmission of the downlink and / or the transmission of the uplink is constituted by a frame of 10 ms. The frame is constituted by including 10 subframes. A length of the subframe is 1 ms. The length of the frame can be given independently of the subcarrier spacing Δf. That is, the configuration of the frame can be given independently of μ. The length of the subframe can also be given independently of the subcarrier spacing Δf. That is, the configuration of the subframe can also be given independently of μ.

[0046] A number and an index of slots included in the subframe can be given for the configuration μ of the subcarrier spacing. For example, a first slot number n μ s may be given in ascending order in a range of 0 ~ N subframe，μ slot - 1 within the subframe. A number and an index of slots included in the frame can also be given for the configuration μ of the subcarrier spacing. For example, a second slot number n μ s，f may be given in ascending order in a range of 0 ~ N frame，μ slot - 1 within the frame. Consecutive N slot symb OFDM symbols can be included in one slot. N slot symb may be given based on at least a part or all of a slot configuration and / or a CP (Cyclic Prefix) configuration. The slot configuration can be given at least by an upper layer parameter tdd-UL-DL-ConfigurationCommon. The CP configuration can be given based on at least an upper layer parameter. The CP configuration can also be given based on at least dedicated RRC signaling. The first slot number and the second slot number are also referred to as a slot number (slot index).

[0047] Figure 2 N represents one embodiment of this method. slot symb An example of the relationship between the subcarrier spacing setting μ, the time slot setting, and the CP setting. Figure 2 In A, with the time slot set to 0, the subcarrier spacing set to μ to 2, and the CP set to normal CP (normal cyclic prefix), N slot symb =14, N frame，μ slot =40, N subframe，μ slot =4. Furthermore, in Figure 2 In B, with the time slot set to 0, the subcarrier spacing set to μ to 2, and the CP set to extended CP (extended cyclic prefix), N slot symb =12, N frame，μ slot =40, N subframe，μ slot =4. N in time slot setting 0 slot symb This can correspond to N in time slot setting 1. slot symb 2 times.

[0048] The following is an explanation of physical resources.

[0049] An antenna port is defined by that a channel through which a symbol is transmitted on one antenna port can be estimated from a channel through which another symbol is transmitted on the same antenna port. In a case where a large scale property of a channel through which a symbol is transmitted on one antenna port can be estimated from a channel through which a symbol is transmitted on another antenna port, two antenna ports are referred to as QCL (Quasi Co-Located). The large scale property can include at least a long term property of the channel. The large scale property can also include at least one or all of a delay spread, a Doppler spread, a Doppler shift, an average gain, an average delay, and a beam parameter. That the first antenna port and the second antenna port are QCL with respect to the beam parameter can mean that a reception beam assumed by the reception side for the first antenna port and a reception beam assumed by the reception side for the second antenna port are the same. That the first antenna port and the second antenna port are QCL with respect to the beam parameter can also mean that a transmission beam assumed by the reception side for the first antenna port and a transmission beam assumed by the reception side for the second antenna port are the same. The terminal device 1 can assume that two antenna ports are QCL in a case where a large scale property of a channel through which a symbol is transmitted on one antenna port can be estimated from a channel through which a symbol is transmitted on another antenna port. The two antenna ports being QCL can also mean that the two antenna ports are assumed to be QCL.

[0050] N μ RB，x N RB sc N (μ) symb N subframe，μ symb A resource grid of N μ RB，x may represent a number of resource blocks given for a subcarrier spacing configuration μ used for a carrier x. N μ RB，x may also be a maximum number of resource blocks given for a subcarrier spacing configuration μ used for a carrier x. The carrier x represents any one of a downlink carrier or an uplink carrier. That is, x is either "DL" or "UL". μ RB is a term including N μ RB，DL and / or N μ RB，UL RB sc ​This can represent the number of subcarriers included in a resource block. At least one resource grid can be given per antenna port p and / or per subcarrier spacing setting μ and / or per transmission direction setting. The transmission direction includes at least a downlink (DL) and an uplink (UL). Hereinafter, the set of parameters including at least some or all of the antenna port p, subcarrier spacing setting μ, and transmission direction setting is also referred to as the first radio parameter set. That is, a resource grid can be given for each first radio parameter set.

[0051] The carriers included in the serving cell in the downlink are called downlink carriers (or downlink component carriers). The carriers included in the serving cell in the uplink are called uplink carriers (uplink component carriers). The downlink component carriers and uplink component carriers are collectively referred to as component carriers (or carriers).

[0052] Each element in the resource grid given by each first radio parameter set is called a resource element. A resource element is determined by its frequency domain index k. sc and time domain index l sym To determine this. For a given first set of wireless parameters, the resource element is determined by the frequency domain index k. sc and time domain index l sym Determined. Determined by the frequency domain index k. sc and time domain index l sym A defined resource element is also called a resource element (k). sc , l sym The frequency domain index k sc Represents 0 to N μ RB N RB sc Any value from -1. μ RB This can be the number of resource blocks given for setting the subcarrier spacing μ. N RB sc N is the number of subcarriers included in the resource block. RB sc =12. Frequency domain index k sc This can correspond to the subcarrier index k. sc Time-domain index l sym It can correspond to OFDM symbol index l sym .

[0053] Figure 3 This is a schematic diagram illustrating an example of a resource grid in a subframe of one embodiment of this work. Figure 3 In the resource grid, the horizontal axis represents the time-domain index.sym , the vertical axis is an index k of a frequency domain sc In one subframe, the frequency domain of the resource grid can include N μ RB N RB sc subcarriers. In one subframe, the time domain of the resource grid can include 14 · 2 μ OFDM symbols. One resource block can be constituted to include N RB sc

[0054] The terminal device 1 can instruct to use only a subset of the resource grid for transceiving. The subset of the resource grid is also referred to as a BWP, and the BWP can be given based on at least a higher layer parameter and / or a part or all of the DCI. The BWP is also referred to as a bandwidth part (BP). That is, the terminal device 1 can also not instruct to use all of the set of the resource grid for transceiving. That is, the terminal device 1 can also instruct to use a part of the frequency resources within the resource grid for transceiving. One BWP can be constituted by a plurality of resource blocks on the frequency domain. One BWP can also be constituted by a plurality of resource blocks that are continuous on the frequency domain. The BWP set for the downlink carrier is also referred to as a downlink BWP. The BWP set for the uplink carrier is also referred to as an uplink BWP.

[0055] One or a plurality of downlink BWPs can be set for the terminal device 1. The terminal device 1 can attempt reception of a physical channel (e.g., PDCCH, PDSCH, SS / PBCH, etc.) in one of the one or a plurality of downlink BWPs. The one downlink BWP is also referred to as an active downlink BWP.

[0056] One or a plurality of uplink BWPs can also be set for the terminal device 1. The terminal device 1 can attempt transmission of a physical channel (e.g., PUCCH, PUSCH, PRACH, etc.) in one of the one or a plurality of uplink BWPs. The one uplink BWP is also referred to as an active uplink BWP.

[0057] A set of downlink BWPs can be set for each serving cell. The set of downlink BWPs can include one or a plurality of downlink BWPs. A set of uplink BWPs can also be set for each serving cell. The set of uplink BWPs can include one or a plurality of uplink BWPs.

[0058] ​The upper layer parameter is a parameter included in a signal of an upper layer. The signal of the upper layer can be RRC (Radio Resource Control) signaling or MAC CE (Medium Access Control Control Element). Here, the signal of the upper layer can be a signal of an RRC layer or a signal of a MAC layer.

[0059] The signal of the upper layer can be common RRC signaling. The common RRC signaling can have at least some or all of the following features C1 to C3. Feature C1) mapped to a BCCH logical channel or a CCCH logical channel Feature C2) includes at least a radioResourceConfigCommon information element Feature C3) mapped to a PBCH

[0060] The radioResourceConfigCommon information element can include information indicating a setting common in a serving cell. The setting common in the serving cell can include at least a setting of a PRACH. The setting of the PRACH can indicate at least one or more random access preamble indices. The setting of the PRACH can also indicate at least a time / frequency resource of the PRACH.

[0061] The signal of the upper layer can also be dedicated RRC signaling. The dedicated RRC signaling can have at least some or all of the following features D1 to D2. Feature D1) mapped to a DCCH logical channel Feature D2) includes at least a radioResourceConfigDedicated information element

[0062] The radioResourceConfigDedicated information element can include at least information indicating a setting unique to the terminal device 1. The radioResourceConfigDedicated information element can also include at least information indicating a setting of a BWP. The setting of the BWP can indicate at least a frequency resource of the BWP.

[0063] For example, the MIB, the first system information, and the second system information can be included in the common RRC signaling. Further, a message of an upper layer mapped to the DCCH logical channel and including at least the radioResourceConfigCommon can be included in the common RRC signaling. Further, a message of an upper layer mapped to the DCCH logical channel and not including the radioResourceConfigCommon information element can be included in the dedicated RRC signaling. Further, a message of an upper layer mapped to the DCCH logical channel and including at least the radioResourceConfigDedicated information element can be included in the dedicated RRC signaling.

[0064] The first system information can indicate at least a time index of an SS (Synchronization Signal) block. The SS block is also referred to as an SS / PBCH block. The SS / PBCH block is also referred to as SS / PBCH. The first system information can also include at least information associated with a PRACH resource. The first system information can also include at least information associated with a setup of an initial connection. The second system information can be system information other than the first system information.

[0065] The radioResourceConfigDedicated information element can include at least information associated with a PRACH resource. The radioResourceConfigDedicated information element can also include at least information associated with a setup of an initial connection.

[0066] Hereinafter, the physical channels and the physical signals of the various schemes of the present embodiment are described.

[0067] The uplink physical channel can correspond to a set of resource elements that carry information generated in an upper layer. The uplink physical channel is a physical channel used in an uplink carrier. At least a part or all of the following uplink physical channels are used in the wireless communication system of one scheme of the present embodiment.

[0068] • PUCCH (Physical Uplink Control CHannel)

[0069] • PUSCH (Physical Uplink Shared CHannel)

[0070] • PRACH (Physical Random Access CHannel)

[0071] A PUCCH can be used to transmit uplink control information (UCI). The uplink control information includes a part or all of the following: channel state information (CSI), a scheduling request (SR), and a HARQ-ACK corresponding to a transport block (TB), a MAC PDU, a DL-SCH, and a PDSCH.

[0072] The HARQ-ACK can include at least a HARQ-ACK bit corresponding to at least one transport block. The HARQ-ACK bit can indicate an ACK or a NACK corresponding to one or more transport blocks. The HARQ-ACK can include at least a HARQ-ACK codebook including one or more HARQ-ACK bits. The HARQ-ACK bit corresponding to one or more transport blocks can be a HARQ-ACK bit corresponding to a PDSCH including the one or more transport blocks. The HARQ-ACK bit can also indicate an ACK or a NACK corresponding to a CBG included in a transport block.

[0073] A scheduling request (SR) can be used at least for requesting resources for initial transmission of a PUSCH. A scheduling request bit can be used to indicate either a positive SR or a negative SR. The scheduling request bit indicating a positive SR is also referred to as "a positive SR is transmitted". The positive SR can indicate that resources for initial transmission of a PUSCH are requested by the terminal device 1. The positive SR can also indicate that a scheduling request is triggered by an upper layer. In a case where it is indicated that a scheduling request is transmitted by the upper layer, the positive SR can be transmitted. The scheduling request bit indicating a negative SR is also referred to as "a negative SR is transmitted". The negative SR can indicate that resources for initial transmission of a PUSCH are not requested by the terminal device 1. The negative SR can also indicate that a scheduling request is not triggered by the upper layer. In a case where it is not indicated that a scheduling request is transmitted by the upper layer, the negative SR can be transmitted.

[0074] The channel state information can include at least a part or all of a channel quality indicator (CQI), a precoding matrix indicator (PMI), and a rank indicator (RI). The CQI is an indicator associated with a quality (e.g., transmission strength) of a channel. The PMI is an indicator indicating precoding. The RI is an indicator indicating a rank (or a number of transmission layers) of transmission.

[0075] The PUCCH can support more than one PUCCH format (PUCCH format 0 to PUCCH format 4). The PUCCH format can be mapped and transmitted to the PUCCH. The PUCCH format can be transmitted by the PUCCH. Transmitting the PUCCH format can be transmitting the PUCCH.

[0076] The PUSCH is used at least for transmitting a transport block (TB, MAC PDU, UL-SCH, PUSCH). The PUSCH can also be used for transmitting at least a part or all of a transport block, a HARQ-ACK, channel state information, and a scheduling request. The PUSCH is used at least for transmitting a random access message 3.

[0077] The PRACH is used at least for transmitting a random access preamble (random access message 1). The PRACH can also be used at least for indicating some or all of an initial connection establishment procedure, a handover procedure, a connection re-establishment procedure, synchronization (timing adjustment) of transmission of the PUSCH, and a request for resources for the PUSCH. The random access preamble can be used to notify the base station device 3 of an index (random access preamble index) given by an upper layer of the terminal device 1.

[0078] In Figure 1 In wireless communication on the uplink, the following uplink physical signals are used. The uplink physical signals can not be used for transmitting information output from an upper layer, but are used by a physical layer.

[0079] • UL DMRS (UpLink Demodulation Reference Signal)

[0080] • SRS (Sounding Reference Signal)

[0081] • UL PTRS (UpLink Phase Tracking Reference Signal)

[0082] The UL DMRS is associated with transmission of the PUSCH and / or the PUCCH. The UL DMRS is multiplexed with the PUSCH or the PUCCH. The base station device 3 can use the UL DMRS to perform transmission path correction of the PUSCH or the PUCCH. Hereinafter, transmission of the PUSCH together with the UL DMRS associated with the PUSCH is simply referred to as transmission of the PUSCH. Hereinafter, transmission of the PUCCH together with the UL DMRS associated with the PUCCH is simply referred to as transmission of the PUCCH. The UL DMRS associated with the PUSCH is also referred to as a PUSCH-use UL DMRS. The UL DMRS associated with the PUCCH is also referred to as a PUCCH-use UL DMRS.

[0083] The SRS can not be associated with transmission of the PUSCH or the PUCCH. The base station device 3 can use the SRS to perform measurement of a channel state. The SRS can be transmitted in the last or last prescribed number of OFDM symbols of a subframe in an uplink slot.

[0084] The UL PTRS can be a reference signal used at least for phase tracking. The UL PTRS can be associated with a UL DMRS group including at least antenna ports for one or more UL DMRSs. The association of the UL PTRS with the UL DMRS group can be that the antenna ports of the UL PTRS are at least QCL with some or all of the antenna ports included in the UL DMRS group. The UL DMRS group can be identified based at least on an antenna port with a smallest index among the UL DMRSs included in the UL DMRS group. The UL PTRS can be mapped to the antenna port with the smallest index among one or more antenna ports to which a codeword is mapped. In a case where the codeword is mapped to at least a first layer and a second layer, the UL PTRS can be mapped to the first layer. The UL PTRS can also not be mapped to the second layer. An index of the antenna port to which the UL PTRS is mapped can be given based at least on a downlink control information.

[0085] In Figure 1 In wireless communication in a downlink from the base station device 3 to the terminal device 1, the following downlink physical channels are used. The downlink physical channels are used by the physical layer to transmit information output from the upper layer.

[0086] • PBCH (Physical Broadcast Channel)

[0087] • PDCCH (Physical Downlink Control Channel)

[0088] • PDSCH (Physical Downlink Shared Channel)

[0089] The PBCH is used at least to transmit a master information block (MIB). The PBCH can be transmitted based on a prescribed transmission interval. The PBCH can be transmitted at an interval of 80 ms. The PBCH can also be transmitted at an interval of 160 ms. The content of the information included in the PBCH can be updated every 80 ms. Some or all of the information included in the PBCH can be updated every 160 ms. The PBCH can be constituted by 288 subcarriers. The PBCH can also be constituted to include 2, 3, or 4 OFDM symbols. The MIB can include information associated with an identifier (index) of a synchronization signal. The MIB can also include information indicating at least a part of a number of slots, a number of subframes, and / or a number of radio frames in which the PBCH is transmitted.

[0090] The PDCCH is used at least for transmitting downlink control information (DCI: Downlink Control Information). The PDCCH can transmit at least the downlink control information. The PDCCH can include the downlink control information. The downlink control information is also referred to as a DCI format. The downlink control information can include at least one of a downlink grant (DL grant) or an uplink grant (UL grant). A DCI format for scheduling of the PDSCH is also referred to as a downlink DCI format. A DCI format for scheduling of the PUSCH is also referred to as an uplink DCI format. The downlink grant is also referred to as a downlink assignment (DL assignment) or a downlink allocation (DL allocation). The uplink DCI format includes at least one of DCI format 0_0 and DCI format 0_1.

[0091] The DCI format 0_0 is configured to include at least one or both of 1A to 1F.

[0092] 1A) DCI format identifier field

[0093] 1B) Frequency domain resource assignment field

[0094] 1C) Time domain resource assignment field

[0095] 1D) Frequency hopping flag field

[0096] 1E) MCS field

[0097] 1F) First CSI request field

[0098] The DCI format specific field can be at least used for indicating which one or more of DCI formats the DCI format including the DCI format specific field corresponds to. The one or more of DCI formats can be given at least based on one or more of DCI format 1_0, DCI format 1_1, DCI format 0_0, and / or DCI format 0_1.

[0099] The frequency domain resource allocation field can be at least used for indicating an allocation of frequency resources for a PUSCH scheduled by a DCI format including the frequency domain resource allocation field. The frequency domain resource allocation field is also referred to as FDRA (Frequency Domain Resource Allocation) field.

[0100] The time domain resource allocation field can be at least used for indicating an allocation of time resources for a PUSCH scheduled by a DCI format including the time domain resource allocation field. The time domain resource allocation field is also referred to as TDRA (Time Domain Resource Allocation) field.

[0101] The time domain resource allocation field can be at least used for indicating an allocation of time resources for a PUSCH scheduled by a DCI format including the time domain resource allocation field.

[0102] The frequency hopping flag field can be at least used for indicating whether frequency hopping is applied to a PUSCH scheduled by a DCI format including the frequency hopping flag field.

[0103] The MCS field can be at least used for indicating one or more of a modulation scheme and / or a target code rate for a PUSCH scheduled by a DCI format including the MCS field. The target code rate can be a target code rate for a transport block of the PUSCH. A size of the transport block (TBS: Transport Block Size) can be given at least based on the target code rate.

[0104] The first CSI request field is at least used for indicating a reporting of CSI. A size of the first CSI request field can be a prescribed value. The size of the first CSI request field can be 0, can be 1, can be 2, and can be 3.

[0105] The DCI format 0_1 is constituted to include one or more of 2A to 2G.

[0106] 2A) DCI format specific field

[0107] 2B) Frequency domain resource allocation field

[0108] 2C) Time domain resource allocation field

[0109] 2D) Frequency hopping flag field

[0110] 2E) MCS field

[0111] 2F) Second CSI request field

[0112] 2G) BWP field

[0113] The BWP field can be used to indicate an uplink BWP mapping a PUSCH scheduled by the DCI format 0_1.

[0114] The second CSI request field is used at least to indicate a report of CSI. A size of the second CSI request field can be given at least based on a parameter ReportTriggerSize of an upper layer (report trigger size).

[0115] The downlink DCI format includes at least one or both of the DCI format 1_0 and the DCI format 1_1.

[0116] The DCI format 1_0 is configured to include at least one or more of 3A to 3H.

[0117] 3A) Identifier for DCI formats field

[0118] 3B) Frequency domain resource assignment field

[0119] 3C) Time domain resource assignment field

[0120] 3D) Frequency hopping flag field

[0121] 3E) MCS field

[0122] 3F) First CSI request field

[0123] 3G) PDSCH-to-HARQ feedback timing indicator field

[0124] 3H) PUCCH resource indicator field

[0125] The PDSCH-to-HARQ feedback timing indicator field can be a field indicating the timing K1. In a case where the index of the slot including the last OFDM symbol of the PDSCH is slot n, the index of the slot including the start of the PUCCH or the start of the PUSCH can be n+K1, the PUCCH or the PUSCH at least including the HARQ-ACK corresponding to the transport block included in the PDSCH. In a case where the index of the slot including the last OFDM symbol of the PDSCH is slot n, the index of the slot of the OFDM symbol including the start of the PUCCH or the OFDM symbol including the start of the PUSCH can be n+K1, the OFDM symbol including the start of the PUCCH or the OFDM symbol including the start of the PUSCH at least including the HARQ-ACK corresponding to the transport block included in the PDSCH.

[0126] Hereinafter, the PDSCH-to-HARQ feedback timing indicator field can also be referred to as a HARQ indicator field.

[0127] The PUCCH resource indicator field can be a field indicating the index of one or more PUCCH resources included in the PUCCH resource set. Further, the value included in the PUCCH resource indicator field can be a PUCCH resource indicator (PRI). The PRI can be used to select (determine) the PUCCH resource used in the transmission of the PUCCH. The PRI can be used as an index of a list of one or more PUCCH resources included in the PUCCH resource set given by the upper layer parameter PUCCH-ResourceSet, i.e., the upper layer parameter resourceList. That is, the PRI can be used in selecting one of the one or more PUCCH resources included in the upper layer parameter resourceList.

[0128] The DCI format 1_1 is configured to include at least a part or all of 4A to 4J.

[0129] 4A) Identifier for DCI formats field

[0130] 4B) Frequency domain resource assignment field

[0131] 4C) Time domain resource assignment field

[0132] 4D) Frequency hopping flag field

[0133] 4E) MCS field: Modulation and Coding Scheme field

[0134] 4F) First CSI request field

[0135] 4G) PDSCH-to-HARQ feedback timing indicator field

[0136] 4H) PUCCH resource indicator field

[0137] 4J) BWP field

[0138] The frequency domain resource assignment field can be used at least for indicating an allocation of frequency resources for a PDSCH scheduled by a DCI format including the frequency domain resource assignment field. The frequency domain resource assignment field is also referred to as FDRA (Frequency Domain Resource Allocation) field.

[0139] The time domain resource assignment field can be used at least for indicating an allocation of time resources for a PDSCH scheduled by a DCI format including the time domain resource assignment field. The time domain resource assignment field is also referred to as TDRA (Time Domain Resource Allocation) field.

[0140] The BWP field can be used for indicating a downlink BWP in which a PDSCH scheduled by the DCI format 1_1 is mapped.

[0141] The DCI format 2_0 can be configured to include at least one or more slot format indicators (SFI: Slot Format Indicator).

[0142] The downlink control information can include Unlicensed access common information. The Unlicensed access common information is control information about access, transmission, and the like in the unlicensed band. The Unlicensed access common information can be information of a subframe configuration for Unlicensed Access (Slot configuration) of the downlink. The subframe configuration for Unlicensed Access (Slot configuration) of the downlink indicates a position of an OFDM symbol occupied in a subframe (slot) in which the PDCCH including the information of the subframe configuration for Unlicensed Access (Slot configuration) of the downlink is configured and / or a position of an OFDM symbol occupied in a next subframe (slot) of the subframe (slot) in which the PDCCH including the information of the subframe configuration for Unlicensed Access (Slot configuration) of the downlink is configured. Transmission and reception of the downlink physical channel, the downlink physical signal are performed in the occupied OFDM symbol. The Unlicensed access common information can be information of a subframe configuration (UL duration and offset) of the uplink. The subframe configuration (UL duration and offset) of the uplink indicates a position of a subframe (slot) of the uplink subframe (uplink slot) started from a subframe (slot) in which the PDCCH including the information of the subframe configuration (UL duration and offset) of the uplink is configured and a number of subframes (slots) of the uplink subframe (uplink slot). The terminal device 1 does not request reception of the downlink physical channel, the downlink physical signal in the subframe (slot) indicated by the information of the subframe configuration (UL duration and offset) of the uplink.

[0143] For example, the downlink control information including the downlink grant or the uplink grant including the C-RNTI (Cell-Radio Network Temporary Identifier) is transmitted and received through the PDCCH. For example, the Unlicensed access common information including the CC-RNTI (Common Control-Radio Network Temporary Identifier) is transmitted and received through the PDCCH.

[0144] In the various schemes of the embodiment, unless otherwise specified, the number of resource blocks indicates the number of resource blocks in the frequency domain.

[0145] The downlink grant is used for scheduling at least one PDSCH in one serving cell. The uplink grant is used for scheduling at least one PUSCH in one serving cell.

[0146] Note that various DCI formats can also include fields other than the above-described fields. For example, a field (NFI: New Feedback Indicator field) indicating whether HARQ-ACK information for PDSCH is detected correctly or not can be included. A field (NFI field) indicating whether to erase (flush) HARQ-ACK bits saved in a recording medium such as a memory or not can also be included.

[0147] A field (NFI field) indicating whether to include retransmission of a transmitted HARQ-ACK codebook can also be included. A field (PGI: PDSCH Group ID field) indicating a PDSCH group (associated PDSCH group) for PDSCH scheduled by a DCI format can also be included. A field (RPGI: Request PDSCH Group ID field) indicating a PDSCH group for which transmission of HARQ-ACK information is requested can also be included. A field (C-DAI: Counter Downlink Assignment Index field) indicating a cumulative number of transmitted PDCCHs can also be included. A field (T-DAI: Total Downlink Assignment Index field) indicating a total number of transmitted PDCCHs can also be included.

[0148] The terminal device 1 can associate a PDSCH group identifier (PGI: PDSCH Group ID) with each PDSCH. The PGI for a certain PDSCH can be indicated based on at least a DCI format for scheduling of the PDSCH. For example, a field (PGI field) indicating the PGI can be included in the DCI format. For example, a PDSCH group can be a set of PDSCHs having the same PGI (PDSCH group identifier). A PDSCH group can be one PDSCH or a set of one or more PDSCHs associated with the same PGI. The number of PDSCH groups set for the terminal device 1 can be 1, can be 2, can be 3, can be 4, or can be an integer of 0 or more other than these.

[0149] The requested PDSCH group (RPG) can be a PDSCH group corresponding to the HARQ-ACK information transmitted (reported) via the next PUCCH or PUSCH. The RPG (requested PDSCH group) can include one PDSCH group or a plurality of PDSCH groups. The indication of the RPG can be represented in a bitmap corresponding to each PDSCH group based on at least the DCI format. The RPG can be represented based on at least the RPGI field included in the DCI format. The terminal device 1 can generate a HARQ-ACK codebook for the indicated RPG and transmit (report) via the PUCCH or PUSCH.

[0150] The value of K1 (information or a parameter indicated by the timing indication field from the PDSCH to the HARQ feedback) indicated by the DCI format included in the PDCCH can be numerical or non-numerical. Here, the value of numerical means a value represented by a number, for example, can be a value in {0, 1, 2, …, 15}. The value of non-numerical can mean a value other than a number or can mean not to represent a numerical value. Hereinafter, the use of the value of numerical K1 and the value of non-numerical K1 will be described. For example, the PDSCH scheduled by the DCI format is transmitted by the base station device 3 in slot n and received by the terminal device 1. In the case where the value of K1 indicated by the DCI format is numerical, the terminal device 1 can transmit (report) the HARQ-ACK information corresponding to the PDSCH via the PUCCH or PUSCH in slot n+K1. In the case where the value of K1 indicated by the DCI format is non-numerical, the terminal device 1 can postpone the reporting of the HARQ-ACK information corresponding to the PDSCH. In the case where the value of non-numerical K1 is indicated by the DCI format including the scheduling information of the PDSCH, the terminal device 1 can postpone the reporting of the HARQ-ACK information corresponding to the PDSCH. For example, the terminal device 1 can store the HARQ-ACK information in a recording medium such as a memory, and does not transmit (report) the HARQ-ACK information via the next PUCCH or PUSCH, but transmits (reports) the HARQ-ACK information based on at least the DCI format other than the above-described DCI format to trigger the transmission of the HARQ-ACK information.

[0151] A value of K1 that is not a number can be included in the sequence of higher layer parameters. The higher layer parameter can be a higher layer parameter dl-DataToUL-ACK. The higher layer parameter can be a different higher layer parameter from the higher layer parameter dl-DataToUL-ACK. The value of K1 can be a value indicated by a field representing a timing of HARQ feedback from PDSCH included in DCI format in the sequence of higher layer parameters. For example, the sequence of higher layer parameters is set to {0, 1, 2, 3, 4, 5, 15, a value that is not a number}, in a case where a number of bits of the field representing a timing of HARQ feedback from PDSCH included in DCI format is assumed to be 3, a code point "000" of the field representing a timing of HARQ feedback from PDSCH can indicate a value of K1 as 0, a code point "001" can indicate a value of K1 as 1, and a code point "111" can indicate a value of K1 as a value that is not a number. For example, the sequence of higher layer parameters is set to {a value that is not a number, 0, 1, 2, 3, 4, 5, 15}, in a case where a number of bits of the field representing a timing of HARQ feedback from PDSCH included in DCI format is assumed to be 3, a code point "000" of the field representing a timing of HARQ feedback from PDSCH can indicate a value of K1 as a value that is not a number, a code point "001" can indicate a value of K1 as 0, and a code point "111" can indicate a value of K1 as 15.

[0152] One physical channel can be mapped to one serving cell. One physical channel can also be mapped to a BWP provided to one carrier included in one serving cell.

[0153] One or more control resource sets (CORESET: COntrol REsource SET) can be configured in the terminal device 1. The terminal device 1 monitors PDCCH in the one or more control resource sets. Here, monitoring PDCCH in the one or more control resource sets can include monitoring one or more PDCCHs corresponding to the one or more control resource sets, respectively. Note that the PDCCH can include one or more PDCCH candidates and / or a set of PDCCH candidates. Furthermore, monitoring PDCCH can include monitoring and detecting PDCCH and / or DCI format transmitted via PDCCH.

[0154] A control resource set can represent a time / frequency domain in which one or more PDCCHs can be mapped. The control resource set can be a region in which the terminal device 1 monitors PDCCH. The control resource set can be constituted by contiguous resources (Localized resource). The control resource set can also be constituted by non-contiguous resources (distributed resource).

[0155] In the frequency domain, a mapping unit of the control resource set can be a resource block. For example, in the frequency domain, a mapping unit of the control resource set can be 6 resource blocks. In the time domain, a mapping unit of the control resource set can be an OFDM symbol. For example, in the time domain, a mapping unit of the control resource set can be 1 OFDM symbol.

[0156] Mapping of the control resource set to resource blocks can be given based on at least an upper layer parameter. The upper layer parameter can include a bitmap for a group of resource blocks (RBG: Resource Block Group). The group of resource blocks can be given by 6 contiguous resource blocks.

[0157] The number of OFDM symbols constituting the control resource set can be given based on at least an upper layer parameter.

[0158] A certain control resource set can be a common control resource set. The common control resource set can be a control resource set commonly set for a plurality of terminal devices 1. The common control resource set can be given based on at least some or all of the MIB, the first system information, the second system information, the common RRC signaling, and the cell ID. For example, time resources and / or frequency resources of the control resource set in which the terminal device 1 monitors the PDCCH for scheduling of the first system information can be given based on at least the MIB.

[0159] The control resource set set in the MIB is also referred to as CORESET #0. The CORESET #0 can be a control resource set with index #0.

[0160] A certain control resource set can also be a dedicated control resource set. The dedicated control resource set can be a control resource set set to be dedicated to the terminal device 1. The dedicated control resource set can be given based on at least some or all of the dedicated RRC signaling and the value of the C-RNTI. A plurality of control resource sets can be constituted in the terminal device 1, and an index (control resource set index) can be given to each control resource set. One or more control channel elements (CCEs) can also be constituted within the control resource set, and an index (CCE index) can be given to each CCE.

[0161] A set of candidates of the PDCCH monitored by the terminal device 1 can be defined from the viewpoint of a search area (Search space). That is, the set of PDCCH candidates monitored by the terminal device 1 can be given according to the search area.

[0162] A search area can be configured as one or more PDCCH candidates including one or more aggregation levels. An aggregation level of a PDCCH candidate can indicate a number of CCEs configuring the PDCCH. A PDCCH candidate can be mapped to one or more CCEs.

[0163] The terminal device 1 can monitor at least one or more search areas in a time slot in which DRX (Discontinuous reception) is not configured. The DRX can be given based on at least an upper layer parameter. The terminal device 1 can also monitor at least one or more search space sets in a time slot in which the DRX is not configured. A plurality of search space sets can be configured in the terminal device 1. An index (search space set index) can be given to each search space set.

[0164] A search space set can be configured to include at least one or more search areas. An index (search area index) can be given to each search area.

[0165] A search space set can be associated with at least one control resource set, respectively. A search space set can also be included in one control resource set, respectively. An index of the control resource set associated with the search space set can be given to the search space set, respectively.

[0166] A search area can include two types of CSS (Common Search Space) and USS (UE-specific Search Space). The CSS can be a search area commonly configured for a plurality of terminal devices 1. The USS can be a search area including a search area configured for each individual terminal device 1. The CSS can be given based on at least a synchronization signal, an MIB, first system information, second system information, common RRC signaling, dedicated RRC signaling, a cell ID, and the like. The USS can be given based on at least dedicated RRC signaling and / or a value of a C-RNTI. The CSS can be a search area configured for a resource (control resource element) commonly used for a plurality of terminal devices 1. The USS can be a search area configured for a resource (control resource element) for each individual terminal device 1.

[0167] For the CSS, Type 0-PDCCH CSS for DCI format scrambled by SI-RNTI used for transmitting system information in a primary cell and Type 1-PDCCH CSS for DCI format scrambled by RA-RNTI, TC-RNTI used for initial access can be used. For the CSS, Type PDCCH CSS for DCI format scrambled by CC-RNTI used for Unlicensed access can be used. The terminal device 1 can monitor PDCCH candidates in these search areas. The DCI format scrambled by the prescribed RNTI can be a DCI format to which CRC (Cyclic Redundancy Check) scrambled by the prescribed RNTI is added.

[0168] The information associated with the reception of the PDCCH can include information associated with an ID indicating a destination of the PDCCH. The ID indicating the destination of the PDCCH can be an ID used for scrambling of CRC bits added to the PDCCH. The ID indicating the destination of the PDCCH is also referred to as RNTI (Radio Network Temporary Identifier). The information associated with the reception of the PDCCH can include information associated with an ID used for scrambling of CRC bits added to the PDCCH. The terminal device 1 can attempt to receive the PDCCH based on at least the information associated with the ID included in the PBCH.

[0169] The RNTI can include: SI-RNTI (System Information-RNTI), P-RNTI (Paging-RNTI), C-RNTI (Common-RNTI), Temporary C-RNTI, RA-RNTI (Random Access-RNTI), CC-RNTI (Common Control-RNTI), INT-RNTI (Interruption-RNTI). The SI-RNTI is used at least for scheduling of the PDSCH including system information for transmission. The P-RNTI is used at least for scheduling of the PDSCH including paging information and / or system information change notification and the like for transmission. The C-RNTI is used at least for scheduling of user data to the terminal device 1 which has RRC connection. The Temporary C-RNTI is used at least for scheduling of the random access message 4. The Temporary C-RNTI is used at least for scheduling of the PDSCH including data mapped to the CCCH in the logical channel. The RA-RNTI is used at least for scheduling of the random access message 2. The CC-RNTI is used at least for transmitting control information for unlicensed access. The INT-RNTI is used at least for indicating pre-emption in the downlink.

[0170] Note that the CIF (Carrier Indicator Field) indicating for which serving cell (or which component carrier) the PDSCH or PUSCH is scheduled by the PDCCH / DCI can not be included in the PDCCH and / or DCI included in the CSS.

[0171] Note that in a case where the terminal device 1 is configured to perform communication (transmission and / or reception) using carrier aggregation (CA) of a plurality of serving cells and / or a plurality of component carriers, the CIF indicating for which serving cell and / or which component carrier the PDSCH or PUSCH is scheduled by the PDCCH / DCI can be included in the PDCCH and / or DCI included in the USS for the prescribed serving cell (prescribed component carrier).

[0172] Note that in a case where the terminal device 1 is configured to perform communication using one serving cell and / or one component carrier, the CIF indicating for which serving cell and / or which component carrier the PDSCH or PUSCH is scheduled by the PDCCH / DCI can not be included in the PDCCH and / or DCI included in the USS.

[0173] The common control resource set can include the CSS. The common control resource set can include both the CSS and the USS. The dedicated control resource set can include the USS. The dedicated control resource set can include the CSS.

[0174] A physical resource of a search area is constituted by a constituent unit (CCE: Control Channel Element) of a control channel. The CCE is constituted by a prescribed number of resource element groups (REGs). For example, the CCE can be constituted by 6 REGs. The REG can be constituted by 1 OFDM symbol of 1 PRB (Physical Resource Block). That is, the REG can be constituted to include 12 resource elements (REs). The PRB is also referred to as a RB (Resource Block).

[0175] The PDSCH is used at least for transmitting / receiving a transport block. The PDSCH can also be used at least for transmitting / receiving a random access message 2 (random access response). The PDSCH can also be used at least for transmitting / receiving system information including parameters for initial access.

[0176] In Figure 1 In wireless communication in the downlink, the following downlink physical signals are used. The downlink physical signals can not be used for transmitting information output from an upper layer, but are used by a physical layer.

[0177] • Synchronization signal (SS)

[0178] • DL DMRS (DownLink DeModulation Reference Signal)

[0179] • CSI-RS (Channel State Information-Reference Signal)

[0180] • DL PTRS (DownLink Phase Tracking Reference Signal)

[0181] The synchronization signal is used for the terminal device 1 to acquire synchronization of the frequency domain and / or the time domain of the downlink. The synchronization signal includes a PSS (Primary Synchronization Signal) and an SSS (Secondary Synchronization Signal).

[0182] The SS block (SS / PBCH block) is configured to include at least a part or all of the PSS, the SSS, and the PBCH.

[0183] The DL DMRS is associated with the transmission of the PBCH, the PDCCH, and / or the PDSCH. The DL DMRS is multiplexed with the PBCH, the PDCCH, and / or the PDSCH. The terminal device 1 can use the DL DMRS corresponding to the PBCH, the PDCCH, or the PDSCH for transmission path correction of the PBCH, the PDCCH, or the PDSCH.

[0184] The CSI-RS can be a signal used at least for calculating channel state information. The pattern of the CSI-RS assumed by the terminal device can be given at least by an upper layer parameter.

[0185] The PTRS can be a signal used at least for compensation of phase noise. The pattern of the PTRS assumed by the terminal device can be given at least on the basis of an upper layer parameter and / or DCI.

[0186] The DL PTRS can be associated with a DL DMRS group including at least an antenna port for one or more DL DMRSs.

[0187] The downlink physical channel and the downlink physical signal are also referred to as downlink signals. The uplink physical channel and the uplink physical signal are also referred to as uplink signals. The downlink signals and the uplink signals are also collectively referred to as physical signals. The downlink signals and the uplink signals are also collectively referred to as signals. The downlink physical channel and the uplink physical channel are collectively referred to as physical channels. The downlink physical signal and the uplink physical signal are collectively referred to as physical signals.

[0188] The BCH (Broadcast CHannel), the UL-SCH (Uplink-Shared CHannel), and the DL-SCH (Downlink-Shared CHannel) are transport channels. A channel used in the Medium Access Control (MAC) layer is referred to as a transport channel. The unit of the transport channel used in the MAC layer is also referred to as a transport block (TB) or a MAC PDU. The control of the HARQ (Hybrid Automatic Repeat reQuest) is performed per transport block in the MAC layer. The transport block is the unit of data delivered by the MAC layer to the physical layer. In the physical layer, the transport block is mapped to a codeword, and modulation processing is performed per codeword.

[0189] The base station device 3 and the terminal device 1 exchange (transmit and receive) a signal of an upper layer in the upper layer. For example, the base station device 3 and the terminal device 1 can transmit and receive an RRC message (Radio Resource Control message, RRC information) in the radio resource control (RRC) layer. Further, the base station device 3 and the terminal device 1 can also transmit and receive a MAC CE (Control Element) in the MAC layer. Here, the RRC message and / or the MAC CE is also referred to as a signal of the upper layer (higher layer signaling).

[0190] The PUSCH and the PDSCH can be used at least for transmitting RRC signaling and / or a MAC CE. Here, the RRC signaling transmitted by the base station device 3 through the PDSCH can be signaling common to a plurality of terminal devices 1 within a serving cell. The signaling common to a plurality of terminal devices 1 within a serving cell is also referred to as common RRC signaling. The RRC signaling transmitted by the base station device 3 through the PDSCH can also be signaling dedicated to a certain terminal device 1 (also referred to as dedicated signaling or UE-specific signaling). The signaling dedicated to a terminal device 1 is also referred to as dedicated RRC signaling. A higher layer parameter specific to a serving cell can be transmitted / received to a plurality of terminal devices 1 within the serving cell using common signaling or to a certain terminal device 1 using dedicated signaling. A higher layer parameter specific to a UE can also be transmitted / received to a certain terminal device 1 using dedicated signaling.

[0191] The BCCH (Broadcast Control CHannel), the CCCH (Common Control CHannel), and the DCCH (Dedicated Control CHannel) are logical channels. The BCCH, for example, is a channel of an upper layer for transmitting / receiving an MIB. Further, the CCCH (Common Control CHannel) is a channel of an upper layer for transmitting / receiving common information in a plurality of terminal devices 1. Here, the CCCH, for example, can be used for a terminal device 1 that does not perform RRC connection. Further, the DCCH (Dedicated Control CHannel) is a channel of an upper layer used at least for transmitting / receiving dedicated control information to a terminal device 1. Here, the DCCH, for example, can be used for a terminal device 1 in RRC connection.

[0192] The BCCH in the logical channel can be mapped to the BCH, the DL-SCH, or the UL-SCH in the transport channel. The CCCH in the logical channel can be mapped to the DL-SCH or the UL-SCH in the transport channel. The DCCH in the logical channel can be mapped to the DL-SCH or the UL-SCH in the transport channel.

[0193] The UL-SCH in the transport channel can be mapped to the PUSCH in the physical channel. The DL-SCH in the transport channel can be mapped to the PDSCH in the physical channel. The BCH in the transport channel can be mapped to the PBCH in the physical channel.

[0194] NR-U (New Radio-Unlicensed) can be applied in a certain component carrier. NR-U can be applied in a certain serving cell as well. Application of NR-U in a certain component carrier (or a certain serving cell) can include at least a part or all of elements A1 to A6 including the following (framework, configuration).

[0195] Element A1: A second SS burst set is configured in the certain component carrier (or the certain serving cell)

[0196] Element A2: The base station device 3 transmits a second SS / PBCH block in the certain component carrier (or the certain serving cell)

[0197] Element A3: The terminal device 1 receives a second SS / PBCH block in the certain component carrier (or the certain serving cell)

[0198] Element A4: The base station device 3 transmits a PDCCH in a second Type 0 PDCCH common search area of the certain component carrier (or the certain serving cell)

[0199] Element A5: The terminal device 1 receives a PDCCH in a second Type 0 PDCCH common search area of the certain component carrier (or the certain serving cell)

[0200] Element A6: An upper layer parameter (for example, a field included in MIB) associated with NR-U indicates a first value (for example, 1)

[0201] NR-U (New Radio-Unlicensed) can not be applied in a certain component carrier. NR-U can not be applied in a certain serving cell as well. Non-application of NR-U in a certain component carrier (or a certain serving cell) can include at least a part or all of elements B1 to B6 including the following (framework, configuration).

[0202] Element B1: A first SS burst set is configured in the certain component carrier (or the certain serving cell)

[0203] Element B2: The base station device 3 transmits a first SS / PBCH block in the certain component carrier (or the certain serving cell)

[0204] Element B3: The terminal device 1 receives a first SS / PBCH block in the certain component carrier (or the certain serving cell)

[0205] Element B4: The base station device 3 transmits a PDCCH in a first Type 0 PDCCH common search area of the certain component carrier (or the certain serving cell)

[0206] Element B5: The terminal device 1 receives the PDCCH in the first Type 0 PDCCH common search space area of the certain component carrier (or the certain serving cell)

[0207] Element B6: An upper layer parameter associated with the NR-U (for example, a field included in the MIB) indicates a value different from the first value (for example, 0)

[0208] A certain component carrier can be set as a licensed band. A certain serving cell can be set as a licensed band. Here, the setting of a certain component carrier (or a certain serving cell) as a licensed band can include at least some or all of the following settings 1 to 3.

[0209] Setting 1: An upper layer parameter indicating operation in a licensed band is given for a certain component carrier (or a certain serving cell) or an upper layer parameter indicating operation in an unlicensed band is not given for a certain component carrier (or a certain serving cell)

[0210] Setting 2: A certain component carrier (or a certain serving cell) is set to operate in a licensed band or a certain component carrier (or a certain serving cell) is not set to operate in an unlicensed band

[0211] Setting 3: A certain component carrier (or a certain serving cell) is included in a licensed band or a certain component carrier (or a certain serving cell) is not included in an unlicensed band

[0212] The licensed band can be a band in which a terminal device (expected) to operate in the licensed band requests a radio station authorization. The licensed band can also be a band in which only a terminal device manufactured by an operator (merchant, business, group, enterprise) holding a radio station authorization operates. The unlicensed band can be a band in which a channel access procedure is not requested before transmitting a physical signal.

[0213] The unlicensed band can be a band in which a terminal device (expected) to operate in the unlicensed band does not request a radio station authorization. The unlicensed band can also be a band in which a terminal device manufactured by one or all of an operator holding a radio station authorization and / or an operator not holding a radio station authorization operates. The unlicensed band can also be a band in which a channel access procedure is requested before transmitting a physical signal.

[0214] Whether or not NR-U is applied in a certain component carrier (or a certain serving cell) can be determined based on at least whether or not the certain component carrier (or the certain serving cell) is configured as a frequency band operable in an unlicensed band (e.g., a frequency band operable only in an unlicensed band). For example, a list of frequency bands designed for NR or carrier aggregation of NR can be specified. For example, in a case where a certain frequency band includes one or more frequency bands operable in an unlicensed band (e.g., a frequency band operable only in an unlicensed band) in the list, NR-U can be applied in the certain frequency band. In addition, in a case where a certain frequency band does not include one or more frequency bands operable in an unlicensed band (e.g., a frequency band operable only in an unlicensed band) in the list, NR-U can not be applied in the certain frequency band, but a general NR (e.g., NR of Rel. 15 or NR other than NR-U of Rel. 16) can be applied.

[0215] Whether or not NR-U is applied in a certain component carrier (or a certain serving cell) can be determined based on at least whether or not the component carrier (or the serving cell) is configured as a frequency band operable in NR-U (e.g., a frequency band operable only in NR-U). For example, it can be that, in terms of a certain frequency band, one or more frequency bands included in the list are included in the frequency band operable in NR-U (e.g., a frequency band operable only in NR-U), and NR-U is applied in the certain frequency band. In addition, it can also be that, in terms of a certain frequency band, one or more frequency bands included in the list are not included in the frequency band operable in NR-U (e.g., a frequency band operable only in NR-U), and a general NR (e.g., NR of Rel. 15 or NR other than NR-U of Rel. 16) is applied in the certain frequency band instead of NR-U.

[0216] Whether or not NR-U is applied in a certain component carrier (or a certain serving cell) can be determined based on information included in an MIB or system information. For example, it can be that, in a case where the MIB (or the system information) includes information indicating whether or not NR-U is applied, NR-U is applied to a serving cell to which the MIB (or the system information) corresponds in a case where the information indicates that NR-U is applied. On the other hand, it can also be that, in a case where the information does not indicate that NR-U is applied, a general NR is applied to the serving cell to which the MIB (or the system information) corresponds instead of NR-U. Alternatively, it can be that the information indicates whether or not the unlicensed band is operable.

[0217] A certain component carrier can be configured as an unlicensed band. A certain serving cell can be configured as an unlicensed band. Here, the configuration of a certain component carrier (or a certain serving cell) as an unlicensed band can include at least some or all of the following configurations 4 to 6.

[0218] Setting 4: An upper layer parameter indicating to act in the unlicensed band is given for a certain component carrier (or a certain serving cell)

[0219] Setting 5: A certain component carrier (or a certain serving cell) is set to act in the unlicensed band

[0220] Setting 6: A certain component carrier (or a certain serving cell) includes in the unlicensed band

[0221] Hereinafter, the description is made on the assumption that the component carrier is set in the licensed band or set in the unlicensed band. Note that the "component carrier is set in the licensed band" can be "serving cell is set in the licensed band", and the "component carrier is set in the unlicensed band" can be "serving cell is set in the unlicensed band".

[0222] Whether the terminal device 1 receives the first SS / PBCH block or the second SS / PBCH block in a certain component carrier can be given based on at least a part or all of whether NR-U is applied in the certain component carrier and whether the certain component carrier is set in the unlicensed band.

[0223] For example, it can be that the terminal device 1 receives the first SS / PBCH block in a case where a certain component carrier is set in the licensed band. Further, it can also be that the terminal device 1 receives the first PDCCH in the first TypeO PDCCH common search area set in a case where a certain component carrier is set in the licensed band. Further, it can also be that the base station device 3 transmits the first SS / PBCH block in a case where a certain component carrier is set in the licensed band. Further, it can also be that the base station device 3 receives the first PDCCH in the first TypeO PDCCH common search area set in a case where a certain component carrier is set in the licensed band.

[0224] It can be that the terminal device 1 receives the second SS / PBCH block in a case where a certain component carrier is set in the unlicensed band. Further, it can also be that the terminal device 1 receives the second PDCCH in the second TypeO PDCCH common search area set in a case where a certain component carrier is set in the unlicensed band. Further, it can also be that the base station device 3 transmits the second SS / PBCH block in a case where a certain component carrier is set in the unlicensed band. Further, it can also be that the base station device 3 receives the second PDCCH in the second TypeO PDCCH common search area set in a case where a certain component carrier is set in the unlicensed band.

[0225] For example, it can be that the terminal device 1 receives the first SS / PBCH block in a case where NR-U is not applied in a certain component carrier and the component carrier is set in a licensed band. Further, it can be that the terminal device 1 receives the first PDCCH in the first Type 0-PDCCH common search space set in a case where NR-U is not applied in a certain component carrier and the component carrier is set in a licensed band. Further, it can be that the base station device 3 transmits the first SS / PBCH block in a case where NR-U is not applied in a certain component carrier and the component carrier is set in a licensed band. Further, it can be that the base station device 3 receives the first PDCCH in the first Type 0-PDCCH common search space set in a case where NR-U is not applied in a certain component carrier and the component carrier is set in a licensed band.

[0226] For example, it can be that the terminal device 1 receives the second SS / PBCH block in a case where NR-U is not applied in a certain component carrier and the component carrier is set in an unlicensed band. Further, it can be that the terminal device 1 receives the first PDCCH in the second Type 0-PDCCH common search space set in a case where NR-U is not applied in a certain component carrier and the component carrier is set in an unlicensed band. Further, it can be that the base station device 3 transmits the second SS / PBCH block in a case where NR-U is not applied in a certain component carrier and the component carrier is set in an unlicensed band. Further, it can be that the base station device 3 receives the first PDCCH in the second Type 0-PDCCH common search space set in a case where NR-U is not applied in a certain component carrier and the component carrier is set in an unlicensed band.

[0227] For example, it can be that the terminal device 1 receives the second SS / PBCH block in a case where NR-U is applied in a certain component carrier and the component carrier is set in a licensed band. Further, it can be that the terminal device 1 receives the first PDCCH in the second Type 0-PDCCH common search space set in a case where NR-U is applied in a certain component carrier and the component carrier is set in a licensed band. Further, it can be that the base station device 3 transmits the second SS / PBCH block in a case where NR-U is applied in a certain component carrier and the component carrier is set in a licensed band. Further, it can be that the base station device 3 receives the first PDCCH in the second Type 0-PDCCH common search space set in a case where NR-U is applied in a certain component carrier and the component carrier is set in a licensed band.

[0228] For example, the terminal device 1 can receive the second SS / PBCH block in a case where NR-U is applied in a certain component carrier and the component carrier is set in the unlicensed band. Also, the terminal device 1 can receive the first PDCCH in the second Type 0 PDCCH common search space set in a case where NR-U is applied in a certain component carrier and the component carrier is set in the unlicensed band. Also, the base station device 3 can transmit the second SS / PBCH block in a case where NR-U is applied in a certain component carrier and the component carrier is set in the unlicensed band. Also, the base station device 3 can receive the first PDCCH in the second Type 0 PDCCH common search space set in a case where NR-U is applied in a certain component carrier and the component carrier is set in the unlicensed band.

[0229] Next, a configuration example of the terminal device 1 according to one aspect of the present embodiment will be described.

[0230] Figure 4 is a schematic block diagram illustrating a configuration of the terminal device 1 according to one aspect of the present embodiment. As shown in Figure 4 the terminal device 1 is configured to include a radio transceiver 10 and an upper layer processing section 14. The radio transceiver 10 is configured to include at least a part or all of an antenna section 11, an RF (Radio Frequency) section 12, and a baseband section 13. The upper layer processing section 14 is configured to include at least a part or all of a medium access control layer processing section 15 and a radio resource control layer processing section 16. The radio transceiver 10 is also referred to as a transmission section, a reception section, or a physical layer processing section. The transmission section can transmit a physical signal and / or a physical channel. The physical signal can include an uplink demodulation reference signal and / or a sounding reference signal. The physical channel can include a PRACH, a PUCCH, and / or a PUSCH. The transmission section can transmit a part or all of the PRACH, the PUCCH, and / or the PUSCH. The reception section can receive a physical signal and / or a physical channel. The physical signal can include a downlink demodulation reference signal, a channel state information reference signal, and / or a synchronization signal. The physical channel can include a PBCH, a PDCCH, and / or a PDSCH. The reception section can receive a part or all of the PBCH, the PDCCH, and / or the PDSCH.

[0231] The upper layer processing section 14 outputs uplink data (transport block) generated by a user's operation or the like to the radio transceiver 10. The upper layer processing section 14 performs processing of the MAC layer, the PDCP (Packet Data Convergence Protocol) layer, the RLC (Radio Link Control) layer, and the RRC layer.

[0232] The media access control layer processing section 15 included in the upper layer processing section 14 performs processing of the MAC layer.

[0233] The radio resource control layer processing section 16 included in the upper layer processing section 14 performs processing of the RRC layer. The radio resource control layer processing section 16 performs management of various setting information / parameters of the device itself. The radio resource control layer processing section 16 sets various setting information / parameters based on a signal of the upper layer received from the base station device 3. That is, the radio resource control layer processing section 16 sets various setting information / parameters based on information indicating the various setting information / parameters received from the base station device 3. Note that the setting information can include information associated with processing or setting of the physical channel or physical signal (that is, the physical layer), the MAC layer, the PDCP layer, the RLC layer, the RRC layer. The parameter can be an upper layer parameter.

[0234] The radio transceiver section 10 performs processing of the physical layer such as modulation, demodulation, encoding, decoding, and the like. The radio transceiver section 10 separates, demodulates, and decodes a received physical signal, and outputs the decoded information to the upper layer processing section 14. The radio transceiver section 10 generates a physical signal by modulating, encoding, and baseband signal generation (conversion to a time-continuous signal) of data, and transmits to the base station device 3.

[0235] The RF section 12 converts (down converts) a signal received via the antenna section 11 into a baseband signal by quadrature demodulation, and removes unnecessary frequency components. The RF section 12 outputs an analog signal subjected to processing to the baseband section.

[0236] The baseband section 13 converts an analog signal input from the RF section 12 into a digital signal. The baseband section 13 removes a portion equivalent to a CP (Cyclic Prefix) from the converted digital signal, performs fast Fourier transform (FFT) on a signal after the CP is removed, and extracts a signal in the frequency domain.

[0237] The baseband section 13 performs inverse fast Fourier transform (IFFT) on data, generates an OFDM symbol, and generates a digital signal of the baseband by attaching a CP to the generated OFDM symbol, and converts the digital signal of the baseband into an analog signal. The baseband section 13 outputs the converted analog signal to the RF section 12.

[0238] The RF section 12 uses a low-pass filter to remove extraneous frequency components from an analog signal input from the baseband section 13, up-converts the analog signal to a carrier frequency, and transmits it via the antenna section 11. In addition, the RF section 12 amplifies the power. Furthermore, the RF section 12 can also have a function of controlling the transmission power. The RF section 12 is also referred to as a transmission power control section.

[0239] Hereinafter, a configuration example of the base station device 3 according to one aspect of the present embodiment will be described.

[0240] Figure 5 is a schematic block diagram showing the configuration of the base station device 3 according to one aspect of the present embodiment. As shown in Figure 5 the base station device 3 is configured to include a radio transceiver section 30 and an upper layer processing section 34. The radio transceiver section 30 is configured to include an antenna section 31, an RF section 32, and a baseband section 33. The upper layer processing section 34 is configured to include a medium access control layer processing section 35 and a radio resource control layer processing section 36. The radio transceiver section 30 is also referred to as a transmission section, a reception section, or a physical layer processing section. The reception section can receive physical signals and / or physical channels. The physical signals can include uplink demodulation reference signals and / or sounding reference signals. The physical channels can include PRACH, PUCCH, and / or PUSCH. The transmission section can transmit some or all of the PRACH, PUCCH, and / or PUSCH. The transmission section can transmit physical signals and / or physical channels. The physical signals can include downlink demodulation reference signals, channel state information reference signals, and / or synchronization signals. The physical channels can include PBCH, PDCCH, and / or PDSCH. The transmission section can transmit some or all of the PBCH, PDCCH, and / or PDSCH.

[0241] The upper layer processing section 34 performs processing of the MAC layer, the PDCP layer, the RLC layer, and the RRC layer.

[0242] The medium access control layer processing section 35 included in the upper layer processing section 34 performs processing of the MAC layer.

[0243] The radio resource control layer processing section 36 included in the upper layer processing section 34 performs processing of the RRC layer. The radio resource control layer processing section 36 generates or acquires, from a higher node, downlink data (transport block) configured in the PDSCH, system information, an RRC message, a MAC CE, and the like, and outputs them to the radio transceiver section 30. Further, the radio resource control layer processing section 36 performs management of various setting information / parameters of each terminal device 1. The radio resource control layer processing section 36 can set various setting information / parameters to each terminal device 1 via a signal of an upper layer. That is, the radio resource control layer processing section 36 transmits / broadcasts information indicating various setting information / parameters. Note that the setting information can include information associated with processing or setting of a physical channel or a physical signal (that is, a physical layer), a MAC layer, a PDCP layer, an RLC layer, an RRC layer. The parameter can be an upper layer parameter.

[0244] Since the radio transceiver section 30 has the same functions as the radio transceiver section 10, the description is omitted.

[0245] Each section of the terminal device 1 indicated by the reference numerals 10 to 16 can also be configured as a circuit. Each section of the base station device 3 indicated by the reference numerals 30 to 36 can also be configured as a circuit.

[0246] The terminal device 1 can perform carrier sense before transmitting a physical signal. Further, the base station device 3 can perform carrier sense before transmitting a physical signal. The carrier sense can be energy detection in a radio channel. Whether or not the physical signal can be transmitted can be given based on the carrier sense performed before transmitting the physical signal. For example, in a case where energy detected by the carrier sense performed before transmitting the physical signal is greater than a prescribed threshold value, it can be determined that transmission of the physical channel can not be performed or cannot be performed. Further, in a case where energy detected by the carrier sense performed before transmitting the physical signal is less than a prescribed threshold value, it can be determined that transmission of the physical channel can be performed or can be performed. Further, in a case where energy detected by the carrier sense performed before transmitting the physical signal is equal to a prescribed threshold value, transmission of the physical channel can be performed or can not be performed. That is, in a case where energy detected by the carrier sense performed before transmitting the physical signal is equal to a prescribed threshold value, it can be determined that transmission cannot be performed or can be performed.

[0247] The procedure of giving whether or not it is possible to transmit a physical channel based on carrier sensing is also called LBT (Listen Before Talk). A state in which it is judged as a result of LBT that it is not possible to transmit a physical signal is also called a busy state or busy. For example, the busy state can be a state in which energy detected by carrier sensing is greater than a prescribed threshold. Further, a state in which it is judged as a result of LBT that it is possible to transmit a physical signal is also called an idle state or idle. For example, the idle state can be a state in which energy detected by carrier sensing is less than a prescribed threshold. It is also called LBT failure that it is judged as a result of LBT that it is not possible to transmit a physical signal.

[0248] The value of the interval (channel occupancy interval) in which the channel is continuously occupied (Channel Occupancy Time: COT) can be determined in advance by each country, or can be determined in advance for each frequency band. The base station device 3 can notify the terminal device 1 of the channel occupancy interval. The terminal device 1 can recognize the length of the channel occupancy interval, and grasp the timing at which the channel occupancy interval ends. For example, the maximum value of the COT can be any one of 2 ms, 3 ms, 6 ms, 8 ms, 10 ms.

[0249] The terminal device 1 can multiplex and transmit uplink control information (UCI) to the PUCCH. The terminal device 1 can also multiplex and transmit UCI to the PUSCH. The UCI can include at least one of channel state information (CSI) of the downlink, a scheduling request (SR) indicating a request of a PUSCH resource, a HARQ-ACK (Hybrid Automatic Repeat request ACKnowledgement) for downlink data (Transport block, Medium Access Control Protocol Data Unit: MAC PDU, Downlink-Shared Channel: DL-SCH, Physical Downlink Shared Channel: PDSCH).

[0250] The HARQ-ACK is also called ACK / NACK, HARQ feedback, HARQ-ACK feedback, HARQ response, HARQ-ACK response, HARQ information, HARQ-ACK information, HARQ control information, and HARQ-ACK control information.

[0251] It can also be that a semi-persistent scheduling (SPS) PDSCH is configured by an upper layer parameter in each BWP of a certain serving cell. Activation or deactivation of the SPS PDSCH can be performed per serving cell. Activation or deactivation of the SPS PDSCH can also be independently performed across serving cells. The SPS (Semi-Persistent Scheduling) PDSCH can be a PDSCH that is semi-persistently scheduled by the terminal device 1.

[0252] In the downlink SPS PDSCH, a downlink assignment (DL assignment) can be given by a PDCCH and maintained based on L1 signaling indicating activation of the SPS. In the downlink SPS PDSCH, a downlink assignment (DL assignment) can be given by a PDCCH and cleared based on L1 signaling indicating deactivation of the SPS.

[0253] When configuring the SPS PDSCH, the upper layer (RRC) can configure some or all of the parameters of cs-RNTI, nrofHARQ-Processes, and periodicity. Here, the cs-RNTI can be a value of an RNTI for activation of the SPS PDSCH or deactivation of the SPS PDSCH or retransmission of the SPS PDSCH. In addition, the nrofHARQ-Processes can be the number of HARQ processes configured for the SPS PDSCH. In addition, the periodicity can be the period of the DL assignment configured for the SPS PDSCH.

[0254] When the SPS PDSCH is released or deactivated by the upper layer, some or all of the corresponding configurations can be released. When the SPS PDSCH is released or deactivated by the upper layer, some or all of the corresponding configurations can be initialized.

[0255] After configuring the DL assignment for the SPS PDSCH, the MAC entity can consider that the Nth DAslot DL assignment occurs in the slot n DA shown in Equation 1 in order. Here, n DAslot may be (numberOfSlotsPerFrame*SFN DA + n DAslot ) = {numberOfSlotsPerFrame*SFN start_time + slot start_time) * periodicity * numberOfSlotsPerFrame / 10} mod (1024 * numberOfSlotsPerFrame). Here, the numberOfSlotsPerFrame can be the number of continuous slots included in one radio frame. The numberOfSlotsPerFrame can be the number of slots constituting one radio frame. The numberOfSlotsPerFrame can be 10, 20, 40, 80, or 160. In addition, the SFN DA may be the radio frame number including the slot nDAslot. The SFN start_time may be the radio frame number including the slot in which the DL assignment is initialized (activated) or reinitialized (reactivated), and in which the SPS PDSCH is first transmitted. The slot start_time may be the slot number in which the DL assignment is initialized (activated) or reinitialized (reactivated), and in which the SPS PDSCH is first transmitted. The periodicity can be given by an upper layer parameter. The periodicity can be 10, 20, 32, 40, 64, 80, 128, 160, 320, or 640.

[0256] The HARQ process for the SPS PDSCH can be set to one or more HARQ processes by an upper layer parameter nrofHARQ-Processes. The HARQ process ID included in the HARQ process for the SPS PDSCH can be common to the HARQ process ID included in the HARQ process for the PDSCH scheduled by the DL grant included in the DCI format. The HARQ process ID included in the HARQ process for the SPS PDSCH can also be different from the HARQ process ID included in the HARQ process for the PDSCH scheduled by the DL grant included in the DCI format.

[0257] The terminal device 1 can report (transmit) the HARQ-ACK information corresponding to the SPS PDSCH to the base station device 3 using the PUCCH. The PUCCH can be constituted by the PUCCH format 0. In addition, the PUCCH can also be constituted by the PUCCH format 1. The PUCCH can also be constituted by the PUCCH format 0 for NR-U. The PUCCH can also be constituted by the PUCCH format 1 for NR-U.

[0258] The PUCCH resources (PUCCH resources) corresponding to the SPS PDSCH for sending HARQ-ACK information can be constructed based on the activation DCI format of the SPS PDSCH. Terminal device 1 can continue to use the PUCCH resources constructed by this DCI format from the time the SPS PDSCH is activated until it is disabled. Terminal device 1 can continue to use the information (parameters) related to DL assignment included in the activation DCI format for the SPS PDSCH for receiving the SPS PDSCH from the time it is activated until it is disabled.

[0259] Alternatively, for the scheduling of SPS PDSCH, terminal device 1 may not expect the reception of PDCCH other than the DCI format PDCCH that includes the activation and deactivation of the SPS PDSCH. Alternatively, for the scheduling of new transmissions of SPS PDSCH, terminal device 1 may not expect the reception of PDCCH other than the DCI format PDCCH that includes the activation and deactivation of the SPS PDSCH.

[0260] Figure 6 This diagram illustrates an example of receiving the SPS PDSCH in this embodiment. Figure 6 In this context, the period of SPS PDSCH is assumed to be p. x PDCCH 601 can be a PDCCH including a DCI format that activates the SPS PDSCH. SPSPDSCH 602 is the first PDSCH activated by the DCI format included in PDCCH 601. Terminal device 1 can determine the time slot where a PUCCH exists to transmit HARQ-ACK information corresponding to SPSPDSCH 602 based on the value of K1 included in the DCI format of the activated SPS PDSCH included in PDCCH 601. For example, in Figure 6 Since K1 is 1, terminal device 1 can use PUCCH603 to send the HARQ-ACK information corresponding to SPS PDSCH602 one time slot later, i.e., in Slot#m+1, based on the time slot in which terminal device 1 receives SPS PDSCH602.

[0261] exist Figure 6 In this context, SPS PDSCH 604 and SPS PDSCH 606 ​​can be PDSCHs without accompanying PDCCH scheduling instructions. Terminal device 1 can determine the existence of a PUCCH slot for transmitting HARQ-ACK information corresponding to SPS PDSCH 604 based on the K1 value included in the DCI format of the SPS PDSCH included in the activated PDCCH 601. For example, in...Figure 6 In the case where K1 is 1, the terminal device 1 can determine the slot in which the PUCCH corresponding to the SPS PDSCH 604 is transmitted, based on the value of K1 included in the DCI format of the SPS PDSCH included in the activated PDCCH 601. For example, in the case where K1 is 1, the terminal device 1 can determine the slot in which the PUCCH corresponding to the SPS PDSCH 604 is transmitted, based on the slot in which the SPS PDSCH 604 is received by the terminal device 1. That is, the terminal device 1 can determine the slot in which the PUCCH corresponding to the SPS PDSCH 604 is transmitted, as Slot#m+p. x In the case where K1 is 1, the terminal device 1 can determine the slot in which the PUCCH corresponding to the SPS PDSCH 604 is transmitted, based on the slot in which the SPS PDSCH 604 is received by the terminal device 1. That is, the terminal device 1 can determine the slot in which the PUCCH corresponding to the SPS PDSCH 604 is transmitted, as Slot#m+p. Figure 6 In the case where K1 is 1, the terminal device 1 can determine the slot in which the PUCCH corresponding to the SPS PDSCH 606 is transmitted, based on the slot in which the SPS PDSCH 606 is received by the terminal device 1. That is, the terminal device 1 can determine the slot in which the PUCCH corresponding to the SPS PDSCH 606 is transmitted, as Slot#m+jp. x In the case where K1 is 1, the terminal device 1 can determine the slot in which the PUCCH corresponding to the SPS PDSCH 606 is transmitted, based on the slot in which the SPS PDSCH 606 is received by the terminal device 1. That is, the terminal device 1 can determine the slot in which the PUCCH corresponding to the SPS PDSCH 606 is transmitted, as Slot#m+jp.

[0262] In the case where K1 is 1, the terminal device 1 can determine the slot in which the PUCCH corresponding to the SPS PDSCH 606 is transmitted, based on the slot in which the SPS PDSCH 606 is received by the terminal device 1. That is, the terminal device 1 can determine the slot in which the PUCCH corresponding to the SPS PDSCH 606 is transmitted, as Slot#m+jp. Figure 6 In the case where K1 is 1, the terminal device 1 can determine the slot in which the PUCCH corresponding to the SPS PDSCH 606 is transmitted, based on the slot in which the SPS PDSCH 606 is received by the terminal device 1. That is, the terminal device 1 can determine the slot in which the PUCCH corresponding to the SPS PDSCH 606 is transmitted, as Slot#m+jp. Figure 6 In the case where K1 is 1, the terminal device 1 can determine the slot in which the PUCCH corresponding to the SPS PDSCH 606 is transmitted, based on the slot in which the SPS PDSCH 606 is received by the terminal device 1. That is, the terminal device 1 can determine the slot in which the PUCCH corresponding to the SPS PDSCH 606 is transmitted, as Slot#m+jp. x In the case where K1 is 1, the terminal device 1 can determine the slot in which the PUCCH corresponding to the SPS PDSCH 606 is transmitted, based on the slot in which the SPS PDSCH 606 is received by the terminal device 1. That is, the terminal device 1 can determine the slot in which the PUCCH corresponding to the SPS PDSCH 606 is transmitted, as Slot#m+jp.

[0263] The terminal device 1 can report HARQ-ACK information corresponding to the SPS PDSCH release to the base station device 3 using a HARQ-ACK codebook. The terminal device 1 can report HARQ-ACK information corresponding to a slot indicated by a value of a PDSCH-to-HARQ_feedback timing indicator field included in DCI format 1_0 or DCI format 1_1 corresponding to the SPS PDSCH release to the base station device 3 using a HARQ-ACK codebook.

[0264] The SPS PDSCH release can be made by a DCI format included in a PDCCH.

[0265] In a case where a CRC of the DCI format is scrambled by a CS-RNTI given by an upper layer parameter cs-RNTI, and a new data indicator field of the transport block is set to 0, the terminal device 1 can validate a downlink SPS assignment PDCCH (DL SPS assignment PDCCH) or an uplink grant Type 2 PDCCH (UL grant Type 2 PDCCH) for scheduling activation or scheduling release. The scheduling activation can be made based on at least the validation and a HARQ process number (HARQ process ID) and a redundancy version included in the DCI format. The scheduling release can be made based on at least the validation and a HARQ process number (HARQ process ID), a redundancy version, a modulation and coding scheme, and a resource block assignment included in the DCI format. {A mod B} is a modulo operation. The modulo operation is a function that outputs a remainder when A is divided by B, denoted as {A mod B}. For example, it can be (5 mod 4) = 1.

[0266] In a case where the downlink data is successfully decoded, an ACK for the downlink data can be generated. In a case where the downlink data is not successfully decoded, a NACK for the downlink data can be generated. The HARQ-ACK can include at least a HARQ-ACK bit corresponding to at least one transport block. The HARQ-ACK bit can indicate an ACK (Acknowledgement) or a NACK (Negative-Acknowledgement) corresponding to one or more transport blocks. The HARQ-ACK can include at least a HARQ-ACK codebook including one or more HARQ-ACK bits. The HARQ-ACK bit corresponding to one or more transport blocks can be a HARQ-ACK bit corresponding to a PDSCH including the one or more transport blocks.

[0267] A HARQ control corresponding to one transport block can be referred to as a HARQ process. A HARQ process identifier can be given per HARQ process. A field indicating the HARQ process identifier can be included in the DCI format. The HARQ process identifier is also referred to as a HARQ process ID.

[0268] A NDI (New Data Indicator) can be indicated per HARQ process by the DCI format. For example, a NDI field can be included in the DCI format (DL assignment) including scheduling information of the PDSCH. The NDI field can be 1 bit. The terminal device 1 can store the value of the NDI per HARQ process. The base station device 3 can store the value of the NDI per HARQ process for each terminal device 1. The terminal device 1 can update the stored value of the NDI using the detected NDI field of the DCI format. The base station device 3 can transmit the updated value of the NDI or the un-updated value of the NDI to the terminal device 1 as the NDI field of the DCI format. The terminal device 1 can update the stored value of the NDI using the detected NDI field of the DCI format for the HARQ process corresponding to the value of the HARQ process identifier field of the detected DCI format.

[0269] The terminal device 1 can determine whether the received transport block is a new transmission or a retransmission based on the value of the NDI field of the DCI format (DL assignment). In the case of comparing the transport block of a certain HARQ process with the value of the NDI received previously, if the value of the NDI field of the detected DCI format is flipped, the terminal device 1 can determine that the transport block is a new transmission. In the case of transmitting a new transport block in a certain HARQ process, the base station device can flip the stored value of the NDI for the HARQ process and transmit the flipped NDI to the terminal device 1. In the case of transmitting a retransmission transport block in a certain HARQ process, the base station device 3 can also not flip the stored value of the NDI for the HARQ process and transmit the unflipped NDI to the terminal device 1. In the case of comparing the transport block of a certain HARQ process with the value of the NDI received previously, if the value of the NDI field of the detected DCI format is not flipped (same), the terminal device 1 can determine that the received transport block is a retransmission. Note that flipping here means switching to a different value.

[0270] The terminal device 1 can report HARQ-ACK information to the base station device 3 using a HARQ-ACK codebook in a slot indicated by the value of the HARQ indication field included in the DCI format 1_0 or DCI format 1_1 corresponding to PDSCH reception.

[0271] For DCI format 1_0, the value of the HARQ indication field can be mapped to a set of slot numbers (1, 2, 3, 4, 5, 6, 7, 8). For DCI format 1_1, the value of the HARQ indication field can be mapped to a set of slot numbers given by the upper layer parameter dl-DataToUL-ACK. The number of slots indicated based on at least the value of the HARQ indication field can also be referred to as HARQ-ACK timing or K1. For example, HARQ-ACK indicating the decoding status of PDSCH (downlink data) transmitted in slot n can be reported (transmitted) in slot n+K1.

[0272] dl-DataToUL-ACK represents a list of timing of HARQ-ACK for PDSCH. The timing refers to a number of slots between a slot (or a slot including a last OFDM symbol of which the PDSCH is mapped) in which the PDSCH is received, and a slot in which HARQ-ACK for the received PDSCH is transmitted, as a reference. For example, dl-DataToUL-ACK can be a list of 1 or 2 or 3 or 4 or 5 or 6 or 7 or 8 timings. In a case where dl-DataToUL-ACK is a list of 1 timing, the HARQ indication field is 0 bits. In a case where dl-DataToUL-ACK is a list of 2 timings, the HARQ indication field is 1 bit. In a case where dl-DataToUL-ACK is a list of 3 or 4 timings, the HARQ indication field is 2 bits. In a case where dl-DataToUL-ACK is a list of 5 or 6 or 7 or 8 timings, the HARQ indication field is 3 bits. In a case where dl-DataToUL-ACK is a list of n K1 timings, the HARQ indication field can be ceil(log2(n K1 )). Here, ceil(X A ) is a function that outputs an integer number by rounding down a decimal point of X A . For example, ceil(2.3) can be 3. In addition, dl-DataToUL-ACK is constituted by a list of timings of any value in a range of 0 to 31. For example, dl-DataToUL-ACK is constituted by a list of timings of any value in a range of 0 to 63.

[0273] The size of dl-DataToUL-ACK is defined as a number of elements included in dl-DataToUL-ACK. The size of dl-DataToUL-ACK can also be referred to as L para . The index of dl-DataToUL-ACK can represent an order (number) of elements of dl-DataToUL-ACK. For example, in a case where the size of dl-DataToUL-ACK is 8 (L para = 8), the index of dl-DataToUL-ACK can be any value of 1, 2, 3, 4, 5, 6, 7, or 8. The index of dl-DataToUL-ACK can be given or represented or indicated by a value represented by the HARQ indication field.

[0274] The terminal device 1 can set the size of the HARQ-ACK codebook in accordance with the size of the dl-DataToUL-ACK. For example, in a case where the dl-DataToUL-ACK is constituted by 8 elements, the size of the HARQ-ACK codebook can be 8. For example, in a case where the dl-DataToUL-ACK is constituted by 2 elements, the size of the HARQ-ACK codebook can be 2. Each HARQ-ACK information constituting the HARQ-ACK codebook can be HARQ-ACK information for PDSCH reception of each slot timing of the dl-DataToUL-ACK. This type of HARQ-ACK codebook is also referred to as a semi-static HARQ-ACK codebook.

[0275] An example of the setting of the HARQ indication field will be described. For example, the dl-DataToUL-ACK is constituted by a list of 8 timings of 0, 7, 15, 23, 31, 39, 47, 55, and the HARQ indication field is constituted by 3 bits. The HARQ indication field "000" as the corresponding timing can correspond to the first 0 of the list of the dl-DataToUL-ACK. That is, the HARQ indication field "000" can correspond to the value 0 indicated by the index 1 of the dl-DataToUL-ACK. The HARQ indication field "001" as the corresponding timing can correspond to the second 7 of the list of the dl-DataToUL-ACK. The HARQ indication field "010" as the corresponding timing can correspond to the third 15 of the list of the dl-DataToUL-ACK. The HARQ indication field "011" as the corresponding timing can correspond to the fourth 23 of the list of the dl-DataToUL-ACK. The HARQ indication field "100" as the corresponding timing can correspond to the fifth 31 of the list of the dl-DataToUL-ACK. The HARQ indication field "101" as the corresponding timing can correspond to the sixth 39 of the list of the dl-DataToUL-ACK. The HARQ indication field "110" as the corresponding timing can correspond to the seventh 47 of the list of the dl-DataToUL-ACK. The HARQ indication field "111" as the corresponding timing can correspond to the eighth 55 of the list of the dl-DataToUL-ACK. In a case where the received HARQ indication field indicates "000", the terminal device 1 can transmit the corresponding HARQ-ACK in the 0th slot from the slot of the received PDSCH. In a case where the received HARQ indication field indicates "001", the terminal device 1 can transmit the corresponding HARQ-ACK in the seventh slot from the slot of the received PDSCH. In a case where the received HARQ indication field indicates "010", the terminal device 1 can transmit the corresponding HARQ-ACK in the 15th slot from the slot of the received PDSCH. In a case where the received HARQ indication field indicates "011", the terminal device 1 can transmit the corresponding HARQ-ACK in the 23rd slot from the slot of the received PDSCH. In a case where the received HARQ indication field indicates "100", the terminal device 1 can transmit the corresponding HARQ-ACK in the 31st slot from the slot of the received PDSCH. In a case where the received HARQ indication field indicates "101", the terminal device 1 can transmit the corresponding HARQ-ACK in the 39th slot from the slot of the received PDSCH.In a case where the received HARQ indication field represents "110", the terminal device 1 can transmit the corresponding HARQ-ACK in the slots from the slot of the received PDSCH to the 47th slot. In a case where the received HARQ indication field represents "111", the terminal device 1 can transmit the corresponding HARQ-ACK in the slots from the slot of the received PDSCH to the 55th slot.

[0276] In a case where the terminal device 1 is given the upper layer parameter pdsch-AggregationFactor, N PDSCH repeat may be the value of pdsch-AggregationFactor. In a case where the terminal device 1 is not given the upper layer parameter pdsch-AggregationFactor, N PDSCH repeat may be 1. The terminal device 1 can report the HARQ-ACK information for the PDSCH reception from the slot n-N PDSCH repeat +1 to the slot n using the PUCCH transmission and / or the PUSCH transmission in the slot n+k. Here, k can be the number of slots indicated by the HARQ indication field included in the DCI format corresponding to the PDSCH reception. Further, in a case where the HARQ indication field is not included in the DCI format, k can be given by the upper layer parameter dl-DataToUL-ACK.

[0277] In a case where the terminal device 1 is configured to monitor the PDCCH including the DCI format 1_0 and not to monitor the PDCCH including the DCI format 1_1, the HARQ-ACK timing value K1 can be one or all of (1, 2, 3, 4, 5, 6, 7, 8). In a case where the terminal device 1 is configured to monitor the PDCCH including the DCI format 1_1, the HARQ-ACK timing value K1 can be given by the upper layer parameter dl-DataToUL-ACK.

[0278] The terminal device 1 can determine a set of a plurality of opportunities for transmitting HARQ-ACK information for a corresponding one or more candidate PDSCH receptions through a PUCCH of a certain slot. The terminal device 1 can determine a plurality of slots of a slot timing K1 included in the dl-DataToUL-ACK as a plurality of opportunities for the candidate PDSCH receptions. K1 can be a set of k, for example, in a case where the dl-DataToUL-ACK is (1, 2, 3, 4, 5, 6, 7, 8), HARQ-ACK information for a PDSCH reception of a slot of n-1, a PDSCH reception of a slot of n-2, a PDSCH reception of a slot of n-3, a PDSCH reception of a slot of n-4, a PDSCH reception of a slot of n-5, a PDSCH reception of a slot of n-6, a PDSCH reception of a slot of n-7, and a PDSCH reception of a slot of n-8 can be transmitted through a PUCCH of a slot of n. The terminal device 1 can set ACK or NACK as the HARQ-ACK information based on a transport block included in a PDSCH actually received in a slot corresponding to the candidate PDSCH reception, and set NACK as the HARQ-ACK information in a case where no PDSCH is received in a slot corresponding to the candidate PDSCH reception.

[0279] A HARQ indicator field included in a DCI format received through a PDCCH of a slot of n-1 can represent 1. A HARQ indicator field included in a DCI format received through a PDCCH of a slot of n-2 can represent 2. A HARQ indicator field included in a DCI format received through a PDCCH of a slot of n-3 can represent 3. A HARQ indicator field included in a DCI format received through a PDCCH of a slot of n-4 can represent 4. A HARQ indicator field included in a DCI format received through a PDCCH of a slot of n-5 can represent 5. A HARQ indicator field included in a DCI format received through a PDCCH of a slot of n-6 can represent 6. A HARQ indicator field included in a DCI format received through a PDCCH of a slot of n-7 can represent 7. A HARQ indicator field included in a DCI format received through a PDCCH of a slot of n-8 can represent 8.

[0280] The terminal device 1 can determine the slot in which the PDCCH is received, the slot in which the HARQ-ACK information is transmitted based on the value of the HARQ indicator field included in the received DCI format, and the set of slots of the plurality of candidate PDSCH receptions corresponding to the HARQ-ACK information. For example, in the case of dl-DataToUL-ACK being (1, 2, 3, 4, 5, 6, 7, 8), the terminal device 1 receives the PDSCH in slot m, the HARQ indicator field included in the DCI format included in the PDCCH scheduling the PDSCH indicates 4. The terminal device 1 can determine that the HARQ-ACK information is transmitted in slot (m+4). The terminal device 1 can also determine that the other HARQ-ACK information transmitted in slot (m+4) is the HARQ-ACK information for the PDSCH reception in slots (m+(1-4)), the HARQ-ACK information for the PDSCH reception in slots (m+(2-4)), the HARQ-ACK information for the PDSCH reception in slots (m+(3-4)), the HARQ-ACK information for the PDSCH reception in slots (m+(5-4)), the HARQ-ACK information for the PDSCH reception in slots (m+(6-4)), the HARQ-ACK information for the PDSCH reception in slots (m+(7-4)), and the HARQ-ACK information for the PDSCH reception in slots (m+(8-4)).

[0281] The dl-DataToUL-ACK as the timing of the HARQ-ACK can not only constitute a value indicating the number of slots, but also a value indicating the HARQ-ACK is held (information). In the case where the HARQ indicator field indicating the value indicating the HARQ-ACK is held is received by the PDCCH, the terminal device 1 can hold the HARQ-ACK (HARQ-ACK information) for the PDSCH scheduled by the PDCCH and wait for transmission of the HARQ-ACK (HARQ-ACK information).

[0282] In the above description, as the type of the HARQ-ACK codebook, the semi-static HARQ-ACK codebook is described, but a different type of HARQ-ACK codebook can be used. A HARQ-ACK codebook of a type referred to as a dynamic HARQ-ACK codebook is described.

[0283] A HARQ-ACK codebook corresponding to a certain PDSCH group can be given based on one or more HARQ-ACK bits corresponding to any one of one or more transport blocks included in any one of one or more PDSCHs included in the certain PDSCH group. The HARQ-ACK codebook can also be given based on at least a part or all of a value of a counting DAI field, a set of monitoring occasions for PDCCH. The HARQ-ACK codebook can also be given based on a value of a UL DAI field. The HARQ-ACK codebook can also be given based on a value of a DAI field. The HARQ-ACK codebook can also be given based on a value of a total DAI field.

[0284] A HARQ-ACK codebook size of a dynamic HARQ-ACK codebook can be based on a field of a DCI format. The size of the HARQ-ACK codebook can be set based on a value of a counting DAI field of a last received DCI format. The counting DAI field can indicate a cumulative number of PDSCHs or transport blocks scheduled until reception of the corresponding DCI format. The size of the dynamic HARQ-ACK codebook can be set based on a value of a total DAI field of a DCI format. The total DAI field can indicate a total number of PDSCHs or transport blocks scheduled until transmission of the HARQ-ACK codebook.

[0285] The terminal device 1 can determine a set of monitoring occasions for PDCCH for HARQ-ACK information to be transmitted in a PUCCH configured in a slot #n based on at least a part or all of a value of a timing K1 and a value of a slot offset K0. The set of monitoring occasions for PDCCH for HARQ-ACK information to be transmitted in a PUCCH configured in a slot #n is also referred to as a set of monitoring occasions for PDCCH for slot #n. Here, the set of monitoring occasions for PDCCH can include M monitoring occasions for PDCCH. For example, the slot offset K0 can be indicated based on at least a value of a time domain resource allocation field included in a downlink DCI format. The slot offset K0 can be a value indicating a number of slots (slot difference) from a slot including an end of an OFDM symbol in which a PDCCH including the DCI format is configured to a start of a PDSCH scheduled by the DCI format, the DCI format including the time domain resource allocation field indicating the slot offset K0.

[0286] The terminal device 1 can determine the monitoring occasion of the PDCCH corresponding to the DCI format detected in the monitoring occasion of the search space set corresponding to the monitoring occasion of the PDCCH as the PDCCH monitoring occasion for the slot n. In addition, the terminal device 1 can not determine the monitoring occasion of the PDCCH corresponding to the DCI format detected in the monitoring occasion of the search space set corresponding to the monitoring occasion of the PDCCH as the PDCCH monitoring occasion for the slot n. In addition, the terminal device 1 can not determine the monitoring occasion of the PDCCH corresponding to the DCI format not detected in the monitoring occasion of the search space set corresponding to the monitoring occasion of the PDCCH as the PDCCH monitoring occasion for the slot n.

[0287] The PUCCH resource for transmitting the HARQ-ACK information in the slot n can be determined based on at least a PUCCH resource indication field included in a last DCI format among one or more DCI formats detected in the set of the monitoring occasions of the PDCCH for the slot n. Here, the one or more DCI formats respectively trigger the HARQ-ACK information to be transmitted in the slot n. The last DCI format can be a DCI format corresponding to a last index (a largest index) among the DCI formats detected in the set of the monitoring occasions of the PDCCH for the slot n. The index of the DCI format in the set of the monitoring occasions of the PDCCH for the slot n is given in ascending order with respect to an index of a serving cell in which the DCI format is detected, and then, in ascending order with respect to an index of the monitoring occasion of the PDCCH in which the DCI format is detected. The index of the monitoring occasion of the PDCCH is given in ascending order on a time axis.

[0288] A counter DAI can represent a cumulative number (or also a value associated with at least a cumulative number) of PDCCHs detected for a PDCCH monitoring occasion in a serving cell, from the PDCCH monitoring occasion in the serving cell, among M PDCCH monitoring occasions. The counter DAI can also be referred to as a C-DAI. A C-DAI corresponding to a PDSCH can be represented by a field included in a DCI format for scheduling of the PDSCH. A total DAI can represent a cumulative number (or also a value associated with at least a cumulative number) of PDCCHs detected up to a PDCCH monitoring occasion m, among M PDCCH monitoring occasions. The total DAI can also represent a cumulative number (or also a value associated with at least a cumulative number) of PDSCHs detected up to a PDCCH monitoring occasion m, among M PDCCH monitoring occasions. The total DAI can be referred to as a T-DAI (Total Downlink Assignment Index).

[0289] A semi-static HARQ-ACK codebook (Type 1 HARQ-ACK codebook) or a dynamic HARQ-ACK codebook (Type 2 HARQ-ACK codebook) can be a HARQ-ACK codebook transmitted based on a DL assignment indication (trigger, request). A DCI format including a HARQ indicator field can be a DL assignment. The DL assignment can be a DCI format for scheduling of a PDSCH. The DL assignment can be a DCI format for allocation of a PDSCH. The HARQ-ACK codebook can be constructed based on dl-DataToUL-ACK and the HARQ indicator field. A size of the semi-static HARQ-ACK codebook can be given based on a size included in dl-DataToUL-ACK. A timing of a slot included in the semi-static HARQ-ACK codebook or the dynamic HARQ-ACK codebook can be given based on a value of the HARQ indicator field and a slot in which the DCI including the HARQ indicator field is received.

[0290] A Type 3 HARQ-ACK codebook can be a HARQ-ACK codebook triggered to be transmitted by a DCI format accompanying scheduling information (DL assignment) of a PDSCH. The Type 3 HARQ-ACK codebook can also be a HARQ-ACK codebook triggered to be transmitted by a DCI format not accompanying scheduling information of a PDSCH.

[0291] The Type 3 HARQ-ACK codebook can be indicated (triggered, requested) by a DCI format as a DL assignment. The DCI format can include a dedicated field indicating (triggering, requesting) transmission of the Type 3 HARQ-ACK codebook.

[0292] In the Type 3 HARQ-ACK codebook, a bit included in the DCI format that triggers transmission of a part or all of the HARQ-ACK information included in the HARQ process is referred to as a HARQ trigger bit.

[0293] In a case where the terminal device 1 is given the upper layer parameter pdsch-HARQ-ACK-OneShotFeedback-r16 and the base station device 3 indicates (requests) transmission (reporting) of the Type 3 HARQ-ACK codebook to the terminal device 1 using the HARQ trigger bit, the terminal device 1 can transmit (report) to the base station device 3 the HARQ-ACK information included in a part or all of the HARQ processes constituted in the terminal device 1 and the value of the NDI included in a part or all of the HARQ processes constituted in the terminal device 1 using the Type 3 HARQ-ACK codebook. In a case where the terminal device 1 is given the upper layer parameter pdsch-HARQ-ACK-OneShotFeedback-r16 and the base station device 3 indicates (requests) transmission (reporting) of the Type 3 HARQ-ACK codebook to the terminal device 1 using the HARQ trigger bit, the terminal device 1 can transmit (report) to the base station device 3 the HARQ-ACK information included in one HARQ process and the value of the NDI included in the HARQ process for the HARQ process.

[0294] In a case where the terminal device 1 is not given the upper layer parameter pdsch-HARQ-ACK-OneShotFeedback-r16 and the base station device 3 indicates (requests) transmission (reporting) of the Type 3 HARQ-ACK codebook to the terminal device 1 using the HARQ trigger bit, the terminal device 1 can transmit (report) to the base station device 3 the HARQ-ACK information included in a part or all of the HARQ processes constituted in the terminal device 1 using the Type 3 HARQ-ACK codebook. In a case where the terminal device 1 is not given the upper layer parameter pdsch-HARQ-ACK-OneShotFeedback-r16 and the base station device 3 indicates (requests) transmission (reporting) of the Type 3 HARQ-ACK codebook to the terminal device 1 using the HARQ trigger bit, the terminal device 1 can transmit (report) to the base station device 3 the HARQ-ACK information included in one HARQ process for the HARQ process.

[0295] The upper layer parameter pdsch-HARQ-ACK-OneShotFeedback-r16 given to the terminal device 1 can be the meaning that the upper layer parameter pdsch-HARQ-ACK-OneShotFeedback-r16 is set by an enabled value.

[0296] The type 3 HARQ-ACK codebook can include HARQ-ACK information for a part or all of HARQ processes. The HARQ processes can be, for example, HARQ processes for PDSCH. The all of HARQ processes can be, for example, all of HARQ processes that can be used in at least one serving cell. The number of HARQ processes that can be used in one serving cell can be, for example, 16. The number of HARQ processes that can be used in 5 serving cells can be, for example, 80. The plurality of HARQ processes can be, for example, a plurality of HARQ processes constituted by RRC signaling. The plurality of HARQ processes can be, for example, a plurality of HARQ processes indicated by downlink control information. The plurality of HARQ processes can be, for example, a plurality of HARQ processes explicitly or implicitly indicated. The number of the plurality of HARQ processes can be, for example, 8. The number of the plurality of HARQ processes can be, for example, 10.

[0297] The type 3 HARQ-ACK codebook can be a HARQ-ACK codebook that defines HARQ processes of PDSCH to which HARQ-ACK included in the type 3 HARQ-ACK codebook corresponds. The slot in which the PDSCH to which the HARQ-ACK included in the type 3 HARQ-ACK codebook corresponds is not limited in advance, and can be set by scheduling of the base station device 3.

[0298] The type 3 HARQ-ACK codebook can include a value of NDI associated with a HARQ process corresponding to HARQ-ACK reported by the type 3 HARQ-ACK codebook. The type 3 HARQ-ACK codebook can include a value of NDI of each HARQ process including HARQ-ACK information reported by the type 3 HARQ-ACK codebook. The terminal device 1 can judge (set) HARQ-ACK information included in the type 3 HARQ-ACK codebook based on at least a part or all of the HARQ processes and the value of NDI stored. The HARQ-ACK can be HARQ-ACK information corresponding to a transport block for a certain HARQ process. The value of NDI can indicate NDI for the certain HARQ process. In addition, the value of NDI can identify NDI corresponding to the HARQ-ACK information.

[0299] In a case where the terminal device 1 is given the upper layer parameter pdsch-HARQ-ACK-OneShotFeedback-r16, and the terminal device 1 receives the PDCCH including the DCI format in which the HARQ trigger bit is set to 1, and a SPS PDSCH is not configured in the terminal device 1, the terminal device 1 can transmit the HARQ-ACK information included in the HARQ process configured in the terminal device 1, the value of the NDI included in the HARQ process, and the HARQ-ACK information corresponding to the PDSCH scheduled by the PDCCH using the PUCCH.

[0300] In a case where the terminal device 1 is not given the upper layer parameter pdsch-HARQ-ACK-OneShotFeedback-r16, and the terminal device 1 receives the PDCCH including the DCI format in which the HARQ trigger bit is set to 1, and a SPS PDSCH is not configured in the terminal device 1, the terminal device 1 can transmit the HARQ-ACK information included in the HARQ process configured in the terminal device 1, the value of the NDI included in the HARQ process, and the HARQ-ACK information corresponding to the PDSCH scheduled by the PDCCH using the PUCCH.

[0301] The terminal device 1 receiving the PDCCH including the DCI format in which the HARQ trigger bit is set to 1 can mean that the base station device 3 instructs (requests) the transmission (reporting) of the type 3 HARQ-ACK codebook to the terminal device 1. The HARQ trigger bit being set to 1 can mean that the transmission (reporting) of the type 3 HARQ-ACK codebook is instructed (requested).

[0302] In a case where the terminal device 1 is instructed by the base station device 3 to receive a plurality of PDSCHs, to transmit (report) HARQ-ACK information corresponding to the plurality of PDSCHs using PUCCH in a certain slot, and there is no DCI format set to trigger a Type 3 HARQ-ACK codebook among a plurality of DCI formats included in a plurality of PDCCHs that schedule the plurality of PDSCHs, the terminal device 1 can determine a PUCCH using a parameter related to reporting of HARQ-ACK information included in a last-received DCI format among DCI formats included in a plurality of PDCCHs that schedule the plurality of PDSCHs, generate a Type 1 HARQ-ACK codebook or a Type 2 HARQ-ACK codebook, and then transmit the Type 1 HARQ-ACK codebook or the Type 2 HARQ-ACK codebook using the determined PUCCH. Parameters related to reporting of HARQ-ACK information included in DCI formats other than the last-received DCI format can be ignored. Here, the parameter related to reporting of HARQ-ACK information can be a parameter for determining a PUCCH resource. The parameter related to reporting of HARQ-ACK information can be a PRI.

[0303] In a case where the terminal device 1 is instructed by the base station device 3 to receive a plurality of PDSCHs, to transmit (report) HARQ-ACK information corresponding to the plurality of PDSCHs using PUCCH in a certain slot, and there is at least one DCI format set to trigger a Type 3 HARQ-ACK codebook among a plurality of DCI formats included in a plurality of PDCCHs that schedule the plurality of PDSCHs, the terminal device 1 can determine a PUCCH using a parameter related to reporting of HARQ-ACK information included in a DCI format that triggers a Type 3 HARQ-ACK codebook, and can ignore parameters related to reporting of HARQ-ACK information included in DCI formats other than the DCI format that triggers a Type 3 HARQ-ACK codebook. Here, the parameter related to reporting of HARQ-ACK information can be a parameter for determining a PUCCH resource. The parameter related to reporting of HARQ-ACK information can be a PRI.

[0304] In a case where the terminal device 1 is instructed by the base station device 3 to receive a plurality of PDSCHs, transmits (reports) HARQ-ACK information corresponding to the plurality of PDSCHs using a PUCCH in a certain slot, and there is no DCI format set to trigger a Type 3 HARQ-ACK codebook among a plurality of DCI formats included in a plurality of PDCCHs that schedule the plurality of PDSCHs, the terminal device 1 can generate a Type 1 HARQ-ACK codebook or a Type 2 HARQ-ACK codebook. Further, the terminal device 1 can include part or all of the HARQ-ACK information reported in the certain slot in the Type 1 HARQ-ACK codebook or the Type 2 HARQ-ACK codebook.

[0305] In a case where the terminal device 1 is instructed by the base station device 3 to receive a plurality of PDSCHs, transmits (reports) HARQ-ACK information corresponding to the plurality of PDSCHs using a PUCCH in a certain slot, and there is no DCI format set to trigger a Type 3 HARQ-ACK codebook among a plurality of DCI formats included in a plurality of PDCCHs that schedule the plurality of PDSCHs, the terminal device 1 can generate a codebook set by an upper layer parameter pdsch-HARQ-ACK-codebook. Further, the terminal device 1 can include part or all of the HARQ-ACK information reported in the certain slot in the codebook set by the upper layer parameter pdsch-HARQ-ACK-codebook. The codebook set by the upper layer parameter pdsch-HARQ-ACK-codebook can be a Type 1 HARQ-ACK codebook or a Type 2 HARQ-ACK codebook.

[0306] In a case where the terminal device 1 is instructed by the base station device 3 to receive a plurality of PDSCHs, transmits (reports) HARQ-ACK information corresponding to the plurality of PDSCHs using a PUCCH in a certain slot, and there is at least one DCI format set to trigger a Type 3 HARQ-ACK codebook among a plurality of DCI formats included in a plurality of PDCCHs that schedule the plurality of PDSCHs, the terminal device 1 can generate a Type 3 HARQ-ACK codebook. Further, the terminal device 1 can include part or all of the HARQ-ACK information reported in the certain slot in the Type 3 HARQ-ACK codebook.

[0307] Figure 6is a diagram representing one example of a selection method of a HARQ-ACK codebook of the present embodiment. dl-DataToUL-ACK represented by 600 is 6, 5, 4. It is assumed that PDCCH 601 schedules PDSCH 604, PDCCH 602 schedules PDSCH 605, and PDCCH 603 schedules PDSCH 606. Furthermore, in the DCI format included in PDCCH 601, the value of the field of timing indication from PDSCH to HARQ feedback (HARQ Timing) is 0, in the DCI format included in PDCCH 702, the value of the field of timing indication from PDSCH to HARQ feedback (HARQ Timing) is 1, and in the DCI format included in PDCCH 703, the value of the field of timing indicator from PDSCH to HARQ feedback (HARQ Timing) is 2. The HARQ timing can also be referred to as a PDSCH-to-HARQ_feedback timing indicator. The HARQ timing field can also be referred to as a PDSCH-to-HARQ_feedback timing indicator field. The terminal device 1 can determine the slot in which to transmit the PUCCH including the HARQ-ACK information corresponding to the PDSCHs, based on at least the value of the field of timing indication from PDSCH to HARQ feedback (HARQ Timing). That is, the HARQ-ACK information corresponding to PDSCH 604, the HARQ-ACK information corresponding to PDSCH 605, and the HARQ-ACK information corresponding to PDSCH 606 can be transmitted (reported) in slot m+6.

[0308] In a case where none of the DCI format included in PDCCH 601, the DCI format included in PDCCH 602, and the DCI format included in PDCCH 603 is set as a Type 3 HARQ-ACK codebook trigger, the terminal device 1 can generate a codebook set by the upper layer parameter pdsch-HARQ-ACK-codebook. Here, the terminal device 1 can transmit the generated codebook using PUCCH 607 determined based on the parameter related to the reporting of HARQ-ACK information included in the DCI format included in PDCCH 603.

[0309] In a case where any one of the DCI format included in the PDCCH 601, the DCI format included in the PDCCH 602, and the DCI format included in the PDCCH 603 is set to trigger the Type 3 HARQ-ACK codebook, the terminal device 1 can generate the Type 3 HARQ-ACK codebook. For example, in a case where the HARQ trigger bit is set to 1 in the DCI format included in the PDCCH 602, and neither the DCI format included in the PDCCH 601 nor the DCI format included in the PDCCH 603 is set to trigger the Type 3 HARQ-ACK codebook, the terminal device 1 can transmit the generated Type 3 HARQ-ACK codebook using the PUCCH 607 determined based on the parameter related to the report of the HARQ-ACK information included in the DCI format included in the PDCCH 602.

[0310] The SPS PDSCH being configured in the terminal device 1 can mean that the SPS PDSCH is activated in the terminal device 1. Further, the SPS PDSCH being configured in the terminal device 1 can mean that the terminal device 1 is provided with the configuration of the SPS PDSCH.

[0311] The SPS PDSCH not being configured in the terminal device 1 can mean that the SPS PDSCH is disabled in the terminal device 1. Further, the SPS PDSCH not being configured in the terminal device 1 can mean that the terminal device 1 is not provided with the configuration of the SPS PDSCH.

[0312] The terminal device 1 receiving the SPS PDSCH can mean that the SPS PDSCH is configured in the terminal device 1.

[0313] Figure 7is a drawing representing one example of a Type 3 HARQ-ACK codebook which does not constitute SPS PDSCH in the present embodiment. dl-DataToUL-ACK represented by 700 is 6, 5, 4. It is assumed that PDCCH 701 schedules PDSCH 704, PDCCH 702 schedules PDSCH 705, and PDCCH 703 schedules PDSCH 706. In the DCI format included in PDCCH 701, the value of the field of HARQ Timing indicating the timing from PDSCH to HARQ feedback is 0, the HARQ Process ID is 1, the NDI is 1, and the HARQ trigger bit is 0. In the DCI format included in PDCCH 702, the value of the field of HARQ Timing indicating the timing from PDSCH to HARQ feedback is 1, the HARQ Process ID is 2, the NDI is 1, and the HARQ trigger bit is 0. In the DCI format included in PDCCH 703, the value of the field of HARQ Timing indicating the timing from PDSCH to HARQ feedback is 2, the HARQ Process ID is 3, the NDI is 0, and the HARQ trigger bit is 1. The HARQ timing can also be referred to as a PDSCH-to-HARQ_feedback timing indicator. The HARQ timing field can also be referred to as a PDSCH-to-HARQ_feedback timing indicator field.

[0314] It is assumed that the HARQ-ACK information corresponding to PDSCH 704 is NACK. It is assumed that the HARQ-ACK information corresponding to PDSCH 705 is ACK. The terminal device 1 can determine the slot in which to transmit the PUCCH including the HARQ-ACK information corresponding to PDSCH 704 based on at least the value of the field of HARQ Timing indicating the timing from PDSCH to HARQ feedback of the DCI format included in PDCCH 701. Furthermore, the terminal device 1 can determine the slot in which to transmit the PUCCH including the HARQ-ACK information corresponding to PDSCH 705 based on the value of the field of HARQ Timing indicating the timing from PDSCH to HARQ feedback of the DCI format included in PDCCH 702. For example, in Figure 7In the case where the value of the HARQ Timing field of the DCI format included in the PDCCH 701 is 0 and the value 6 as index 0 corresponding to the value of the HARQ timing among one or more values of the upper layer parameter 700 of dl-DataToUL-ACK is K1 (the number of slots from the PDSCH to the HARQ feedback), the terminal device 1 can transmit the HARQ-ACK information corresponding to the PDSCH 704 in the PUCCH in the slot Slot #m+6 after 6 slots from the PDSCH 704, for example. In the case where the value of the HARQ Timing field of the DCI format included in the PDCCH 701 is 0 and the value 6 as index 0 corresponding to the value of the HARQ timing among one or more values of the upper layer parameter 700 of dl-DataToUL-ACK is K1 (the number of slots from the PDSCH to the HARQ feedback), the terminal device 1 can transmit the HARQ-ACK information corresponding to the PDSCH 704 in the PUCCH in the slot Slot #m+6 after 6 slots from the PDSCH 704, for example. Figure 7 In the case where the value of the HARQ Timing field of the DCI format included in the PDCCH 702 is 1 and the value 5 as index 1 corresponding to the value of the HARQ timing among one or more values of the upper layer parameter 700 of dl-DataToUL-ACK is the timing from the PDSCH to the HARQ feedback, the terminal device 1 can transmit the HARQ-ACK information corresponding to the PDSCH 705 in the PUCCH in the slot Slot #m+6 after 5 slots from the PDSCH 705, for example. In addition, in the case where the PRI of the DCI format included in the PDCCH 701 and the PRI of the DCI format included in the PDCCH 702 indicate the PUCCH 707, the terminal device 1 can include the HARQ-ACK information corresponding to the PDSCH 704 and the HARQ-ACK information corresponding to the PDSCH 705 in the Type 1 HARQ-ACK codebook or the Type 2 HARQ-ACK codebook and transmit the Type 1 HARQ-ACK codebook or the Type 2 HARQ-ACK codebook using the PUCCH 707.

[0315] Assume that the HARQ-ACK information corresponding to the PDSCH 706 is NACK. The terminal device 1 transmits the HARQ-ACK information corresponding to the PDSCH 706 through the PUCCH 708 based on the value of the HARQ feedback timing indication field of the DCI format included in the PDCCH 703. Here, the HARQ trigger bit of the DCI format included in the PDCCH 703 is 1, and thus, in a case where the terminal device 1 is given the upper layer parameter 710 of pdsch-HARQ-ACK-OneShotFeedback-r16, the terminal device 1 includes the HARQ-ACK information included in a part or all of the HARQ processes constituted in the terminal device 1 and the values of the NDI included in the part or all of the HARQ processes in the Type 3 HARQ-ACK codebook and transmits the Type 3 HARQ-ACK codebook through the PUCCH 708. That is, the HARQ trigger bit of the DCI format included in the PDCCH 703 is 1, and thus, the terminal device 1 includes the HARQ-ACK information included in the HARQ process ID 1, the HARQ process ID 2, and the HARQ process ID 3 constituted in the terminal device 1 and the values of the NDI included in the HARQ process ID 1, the HARQ process ID 2, and the HARQ process ID 3 constituted in the terminal device 1 in the Type 3 HARQ-ACK codebook and transmits the Type 3 HARQ-ACK codebook through the PUCCH 708. Further, the HARQ trigger bit of the DCI format included in the PDCCH 703 is 1, and thus, in a case where the terminal device 1 is not given the upper layer parameter 710 of pdsch-HARQ-ACK-OneShotFeedback-r16, the terminal device 1 includes the HARQ-ACK information included in a part or all of the HARQ processes constituted in the terminal device 1 in the Type 3 HARQ-ACK codebook and transmits the Type 3 HARQ-ACK codebook through the PUCCH 708. That is, the HARQ trigger bit of the DCI format included in the PDCCH 703 is 1, and thus, the terminal device 1 includes the HARQ-ACK information included in the HARQ process ID 1, the HARQ process ID 2, and the HARQ process ID 3 constituted in the terminal device 1 in the Type 3 HARQ-ACK codebook and transmits the Type 3 HARQ-ACK codebook through the PUCCH 708.

[0316] In a case where there exist a first PUCCH including a Type 3 HARQ-ACK codebook and a second PUCCH including a Type 1 HARQ-ACK codebook or a Type 2 HARQ-ACK codebook in one slot, the terminal device 1 can not transmit the second PUCCH but transmit only the first PUCCH. For example, in a case where the HARQ trigger bit of the DCI format included in the PDCCH 703 is 1 and the terminal device 1 is given the upper layer parameter 710 of pdsch-HARQ-ACK-OneShotFeedback-r16, the terminal device 1 can not transmit the second PUCCH but transmit only the first PUCCH. Figure 7In this case, the terminal device 1 can also transmit the PUCCH 708 including the type 3 HARQ-ACK codebook, and not transmit the PUCCH 707 including the type 1 HARQ-ACK codebook or the type 2 HARQ-ACK codebook.

[0317] The values of the HARQ-ACK information and the NDI transmitted by the PUCCH 708 can also be configured at the start (MSB: Most Significant Bit) of the bit string according to the values of the HARQ-ACK information and the NDI included in the HARQ process with a small HARQ process ID. The values of the HARQ-ACK information and the NDI transmitted by the PUCCH 708 can also be configured at the start (MSB: Most Significant Bit) of the bit string according to the values of the HARQ-ACK information and the NDI included in the HARQ process with a large HARQ process ID. The values of the HARQ-ACK information and the NDI transmitted by the PUCCH 708 can also be configured at the start (MSB: Most Significant Bit) of the bit string according to the values of the HARQ-ACK information and the NDI included in the HARQ process assigned first.

[0318] In a case where the terminal device 1 is given the upper layer parameter pdsch-HARQ-ACK-OneShotFeedback-r16, the size of the type 3 HARQ-ACK codebook can be given based on at least one or all of the number of HARQ processes constituted in the terminal device 1 and the disabled PDCCH for the SPS PDSCH. For example, in a case where the terminal device 1 is given the upper layer parameter pdsch-HARQ-ACK-OneShotFeedback-r16 and the number of HARQ processes constituted in the terminal device 1 is 16, and the terminal device 1 does not receive the disabled PDCCH for the SPS PDSCH, the size of the type 3 HARQ-ACK codebook can be the sum (32 bits) of the number of HARQ-ACK information included in the HARQ processes (16 bits) and the number of NDI that is the latest with respect to the respective HARQ processes (16 bits). The number of NDI that is the latest with respect to one HARQ process can be two. For example, in a case where the terminal device 1 is given the upper layer parameter pdsch-HARQ-ACK-OneShotFeedback-r16 and the number of HARQ processes constituted in the terminal device 1 is 16, and the terminal device 1 receives the disabled PDCCH for the SPS PDSCH, the size of the type 3 HARQ-ACK codebook can be the sum (33 bits) of the number of HARQ-ACK information included in the HARQ processes (16 bits), the number of NDI that is the latest with respect to the respective HARQ processes (16 bits), and HARQ-ACK information (1 bit) corresponding to the disable of the SPS PDSCH. For example, in a case where the terminal device 1 is given the upper layer parameter pdsch-HARQ-ACK-OneShotFeedback-r16 and the number of HARQ processes constituted in the terminal device 1 is 16, and the terminal device 1 receives the disabled PDCCH for the SPS PDSCH, the size of the type 3 HARQ-ACK codebook can be the sum (33 bits) of the number of HARQ-ACK information included in the HARQ processes (16 bits), the number of NDI that is the latest with respect to the respective HARQ processes (16 bits), HARQ-ACK information (1 bit) corresponding to the disable of the SPS PDSCH, and a prescribed value (1 bit) corresponding to the NDI. Here, the 'prescribed value corresponding to the NDI' means that since there is no value of the NDI for the SPS PDSCH, the function as the NDI is not performed, but can be a placeholder value for a value set in the NDI field included in the type 3 HARQ-ACK codebook. The prescribed value corresponding to the NDI can be 0 or 1.

[0319] In a case where the terminal device 1 is not given the upper layer parameter pdsch-HARQ-ACK-OneShotFeedback-r16, the size of the type 3 HARQ-ACK codebook can be given based on at least one or all of the number of HARQ processes constituted in the terminal device 1 and the disabled PDCCH for SPS PDSCH. For example, in a case where the terminal device 1 is not given the upper layer parameter pdsch-HARQ-ACK-OneShotFeedback-r16, the number of HARQ processes constituted in the terminal device 1 is 16, and the terminal device 1 does not receive the disabled PDCCH for SPS PDSCH, the size of the type 3 HARQ-ACK codebook can be the number of HARQ-ACK information included in the HARQ processes (16 bits). For example, in a case where the terminal device 1 is not given the upper layer parameter pdsch-HARQ-ACK-OneShotFeedback-r16, the number of HARQ processes constituted in the terminal device 1 is 16, and the terminal device 1 receives the disabled PDCCH for SPS PDSCH, the size of the type 3 HARQ-ACK codebook can be the sum of the number of HARQ-ACK information included in the HARQ processes (16 bits) and the HARQ-ACK information corresponding to the disabled SPS PDSCH (1 bit) (17 bits).

[0320] Triggering the reporting (transmission) of the HARQ-ACK information included in one or more HARQ processes constituted in the terminal device 1 can mean triggering the reporting (transmission) of the type 3 HARQ-ACK codebook.

[0321] Figure 8is a diagram indicating one example of reporting of HARQ-ACK information corresponding to PDSCHs scheduled by DL grant and SPS PDSCH in a case where the terminal device 1 is configured with SPS PDSCH in the present embodiment. It is assumed that the PDCCH 801 schedules the PDSCH 804, the PDCCH 802 schedules the PDSCH 805, and the PDCCH 803 schedules the PDSCH 806. In the DCI format included in the PDCCH 801, the value of the field of timing indication from PDSCH to HARQ feedback (HARQ Timing) is 0, the HARQ process ID is 1, the NDI is 1, and the HARQ trigger bit is 0. In the DCI format included in the PDCCH 802, the value of the field of timing indication from PDSCH to HARQ feedback (HARQ Timing) is 1, the HARQ process ID is 3, the NDI is 1, and the HARQ trigger bit is 0. In the DCI format included in the PDCCH 803, the value of the field of timing indicator from PDSCH to HARQ feedback (HARQ Timing) is 3, the HARQ process ID is 4, the NDI is 0, and the HARQ trigger bit is 1. The HARQ timing can also be referred to as a PDSCH-to-HARQ_feedback timing indicator. The HARQ timing field can also be referred to as a PDSCH-to-HARQ_feedback timing indicator field.

[0322] It is assumed that the HARQ-ACK information corresponding to the PDSCH 804 is NACK. It is assumed that the HARQ-ACK information corresponding to the PDSCH 805 is ACK. The terminal device 1 can determine the slot in which to transmit the PUCCH including the HARQ-ACK information corresponding to the PDSCH 804 based on at least the value of the field of timing indicator from PDSCH to HARQ feedback (HARQ Timing) of the DCI format included in the PDCCH 801. Further, the terminal device 1 can determine the slot in which to transmit the PUCCH including the HARQ-ACK information corresponding to the PDSCH 805 based on the value of the field of timing indicator from PDSCH to HARQ feedback (HARQ Timing) of the DCI format included in the PDCCH 802. Further, the terminal device 1 can determine the slot in which to transmit the PUCCH including the HARQ-ACK information corresponding to the SPS PDSCH 809 based on the value of the field of timing indicator from PDSCH to HARQ feedback (HARQ Timing) included in the configuration 810 related to reporting of HARQ-ACK information corresponding to the SPS PDSCH 809. For example, in a case where the value of the field of timing indicator from PDSCH to HARQ feedback (HARQ Timing) included in the configuration 810 related to reporting of HARQ-ACK information corresponding to the SPS PDSCH 809 is 0, the terminal device 1 can determine the slot in which to transmit the PUCCH including the HARQ-ACK information corresponding to the SPS PDSCH 809 based on the value of the field of timing indicator from PDSCH to HARQ feedback (HARQ Timing) of the DCI format included in the PDCCH 803. Figure 8In the case where the value of the HARQ Timing field of the DCI format included in the PDCCH 801 is 0 and 7, which is the value of the dl-DataToUL-ACK of the higher layer parameter 800 as the index 0 corresponding to the value of the HARQ timing, is K1 (the number of slots from the PDSCH to the HARQ feedback), the terminal device 1 can transmit the HARQ-ACK information corresponding to the PDSCH 804 in the PUCCH in the slot Slot #m+7 after 7 slots from the PDSCH 804. Further, for example, in the case where the value of the HARQ Timing field of the DCI format included in the PDCCH 802 is 1 and 6, which is the value of the dl-DataToUL-ACK of the higher layer parameter 800 as the index 1 corresponding to the value of the HARQ timing, is K1 (the number of slots from the PDSCH to the HARQ feedback), the terminal device 1 can transmit the HARQ-ACK information corresponding to the PDSCH 805 in the PUCCH in the slot Slot #m+7 after 6 slots from the PDSCH 805. Further, for example, in the case where the value of the HARQ Timing field of the DCI format included in the PDCCH 802 is 1 and 6, which is the value of the dl-DataToUL-ACK of the higher layer parameter 800 as the index 1 corresponding to the value of the HARQ timing, is K1 (the number of slots from the PDSCH to the HARQ feedback), the terminal device 1 can transmit the HARQ-ACK information corresponding to the PDSCH 805 in the PUCCH in the slot Slot #m+7 after 6 slots from the PDSCH 805. Figure 8 In the case where the value of the HARQ Timing field of the DCI format included in the PDCCH 802 is 1 and 6, which is the value of the dl-DataToUL-ACK of the higher layer parameter 800 as the index 1 corresponding to the value of the HARQ timing, is K1 (the number of slots from the PDSCH to the HARQ feedback), the terminal device 1 can transmit the HARQ-ACK information corresponding to the PDSCH 805 in the PUCCH in the slot Slot #m+7 after 6 slots from the PDSCH 805. Further, for example, in the case where the value of the HARQ Timing field of the DCI format included in the PDCCH 802 is 1 and 6, which is the value of the dl-DataToUL-ACK of the higher layer parameter 800 as the index 1 corresponding to the value of the HARQ timing, is K1 (the number of slots from the PDSCH to the HARQ feedback), the terminal device 1 can transmit the HARQ-ACK information corresponding to the PDSCH 805 in the PUCCH in the slot Slot #m+7 after 6 slots from the PDSCH 805. Figure 8 In the case where the value of the HARQ Timing field of the DCI format included in the PDCCH 802 is 1 and 6, which is the value of the dl-DataToUL-ACK of the higher layer parameter 800 as the index 1 corresponding to the value of the HARQ timing, is K1 (the number of slots from the PDSCH to the HARQ feedback), the terminal device 1 can transmit the HARQ-ACK information corresponding to the PDSCH 805 in the PUCCH in the slot Slot #m+7 after 6 slots from the PDSCH 805. Further, for example, in the case where the value of the HARQ Timing field of the DCI format included in the PDCCH 802 is 1 and 6, which is the value of the dl-DataToUL-ACK of the higher layer parameter 800 as the index 1 corresponding to the value of the HARQ timing, is K1 (the number of slots from the PDSCH to the HARQ feedback), the terminal device 1 can transmit the HARQ-ACK information corresponding to the PDSCH 805 in the PUCCH in the slot Slot #m+7 after 6 slots from the PDSCH 805.

[0323] In a case where there exist, in one slot, a first PUCCH including a Type 3 HARQ-ACK codebook and a second PUCCH including a Type 1 HARQ-ACK codebook or a Type 2 HARQ-ACK codebook, the terminal device 1 can not transmit the second PUCCH, and transmit only the first PUCCH. For example, in Figure 8 , the terminal device 1 can also transmit the PUCCH 808 including the Type 3 HARQ-ACK codebook, and not transmit the PUCCH 814 including the Type 1 HARQ-ACK codebook or the Type 2 HARQ-ACK codebook.

[0324] In a case where the terminal device 1 is given the upper layer parameter pdsch-HARQ-ACK-OneShotFeedback-r16, and the HARQ trigger bit included in the DCI format included in the PDCCH 803 is 1, and the PRI included in the DCI format indicates the PUCCH 808, the terminal device 1 can include the HARQ-ACK information included in part or all of the HARQ processes constituted in the terminal device 1 and the value of the NDI for the HARQ-ACK information in the Type 3 HARQ-ACK codebook, and transmit the Type 3 HARQ-ACK codebook using the PUCCH 808. Here, the value of the NDI corresponding to the SPS PDSCH 809 is not set, and therefore the terminal device 1 can set a prescribed value in the field of the value of the NDI corresponding to the SPS PDSCH 809 in the PUCCH 808, and transmit the PUCCH 808. The prescribed value can be 0, or 1. In Figure 8 , the field 811 can be a field for the HARQ-ACK information corresponding to one or more PDSCHs scheduled by a DL grant and the NDI for the HARQ-ACK information. The field 812 can be a field for the HARQ-ACK information corresponding to the SPS PDSCH and the NDI for the HARQ-ACK information.

[0325] In a case where the terminal device 1 is given the upper layer parameter pdsch-HARQ-ACK-OneShotFeedback-r16, and there is constituted an SPS PDSCH in the terminal device 1, and the terminal device 1 receives the SPS PDSCH and a PDSCH scheduled by a DL grant, and the HARQ trigger bit included in the DCI format is 1, the bit string mapped to the PUCCH for transmitting the triggered HARQ-ACK information and the NDI for the HARQ-ACK information can be configured in the order of {HARQ-ACK information, NDI}.

[0326] The DCI format triggering the type 3 HARQ-ACK codebook can be used by scheduling the PDSCH. The DCI format triggering the type 3 HARQ-ACK codebook can not be used for scheduling the PDSCH.

[0327] A field indicating whether the DCI format schedules or does not schedule the PDSCH can be included in the DCI format triggering the type 3 HARQ-ACK codebook. A field indicating whether the DCI format schedules or does not schedule the DL-SCH can be included in the DCI format triggering the type 3 HARQ-ACK codebook. The size of the field can be 1 bit, or 2 bits, or a predetermined number of bits. The field is referred to as the PDSCH indicator. Further, it can be that, in the case where the PDSCH indicator is 1, the DCI format schedules the PDSCH. It can also be that, in the case where the PDSCH indicator is 0, the DCI format does not schedule the PDSCH.

[0328] In the case where the DCI format schedules the PDSCH, i.e., in the case where the value of the PDSCH indicator field included in the DCI format is 1, the terminal device 1 can transmit the PUCCH including a certain type of HARQ-ACK codebook in the time slot after the time slot given by the value of K1 based on the HARQ timing, from the time slot including the OFDM symbol at the end of which the PDSCH scheduled by the DCI format is included. For example, in the case where the PDSCH is scheduled by the DCI format triggering the type 3 HARQ-ACK codebook in the time slot n, and the value of K1 given by the value based on the HARQ timing is 4, the terminal device 1 can transmit the PUCCH including the type 3 HARQ-ACK codebook in the time slot n+4.

[0329] The terminal device 1 can determine the difference (offset) from the time slot including the OFDM symbol at the end of which the PDCCH including the DCI format is included to the time slot in which the transmission of the HARQ-ACK information including a certain type of HARQ-ACK codebook is started, based on at least the PDSCH indicator field included in the DCI format.

[0330] The certain type of HARQ-ACK codebook can include any one of the type 1 HARQ-ACK codebook, the type 2 HARQ-ACK codebook, and the type 3 HARQ-ACK codebook.

[0331] In a case where the DCI format does not schedule the PDSCH, i.e., in a case where the value of the PDSCH indicator field included in the DCI format is 0, the terminal device 1 can transmit the PUCCH including a certain type of HARQ-ACK codebook in a time slot subsequent to a time slot given by a value of K1 based on a value of the HARQ timing, from a time slot in which the PDCCH including the DCI format is received. For example, in a case where the PDCCH including the DCI format triggering the type 3 HARQ-ACK codebook is received in a time slot n, the value of the PDSCH indicator field included in the DCI format is set to 0, and the value of K1 based on the value of the HARQ timing is 4, the terminal device 1 can transmit the PUCCH including the type 3 HARQ-ACK codebook in a time slot n+4. The terminal device 1 can determine the K1 based on at least the PDSCH indicator field included in the DCI format triggering the type 3 HARQ-ACK codebook. The base station device 3 can determine the K1 and include it in the DCI format.

[0332] In a case where the DCI format does not schedule the PDSCH, i.e., in a case where the value of the PDSCH indicator field included in the DCI format is 0, the terminal device 1 can transmit the PUCCH including a certain type of HARQ-ACK codebook in a time slot subsequent to a time slot given by a value of K1 based on a value of the HARQ timing, from a time slot indicated by a value of the TDRA field included in the DCI format. For example, in a case where the value of the TDRA field included in the DCI format triggering the type 3 HARQ-ACK codebook indicates a time slot n, the value of the PDSCH indicator field included in the DCI format is set to 0, and the value of K1 based on the value of the HARQ timing is 4, the terminal device 1 can transmit the PUCCH including the type 3 HARQ-ACK codebook in a time slot n+4. The terminal device 1 can determine the K1 based on at least the PDSCH indicator field included in the DCI format triggering the type 3 HARQ-ACK codebook. The base station device 3 can determine the K1 and include it in the DCI format.

[0333] To indicate whether the DCI format schedules or does not schedule the PDSCH, the value of a certain field can be set to a prescribed value. To indicate whether the DCI format schedules or does not schedule the DL-SCH, the value of a certain field can be set to a prescribed value. The certain field can be the TDRA field, or the FDRA field, or both the TDRA and FDRA fields. Further, the prescribed value can be all 0, or all 1. Further, the prescribed value can change the value according to the frequency resource allocation method of the PDSCH. Further, in a case where the frequency resource allocation of the PDSCH is the first method, the prescribed value can be all 0. Further, in a case where the frequency resource allocation of the PDSCH is the second method, the prescribed value can be all 1. Further, in a case where the frequency resource allocation of the PDSCH is the second method, the prescribed value can be a value greater than N BWP SIZE (L RBs - 1) + RB start . Here, N BWP SIZE may be the number of resource blocks (RBs) constituting a BWP. Further, L RBs may be the number of contiguously allocated resource blocks. Further, RB start may be the starting of the hypothetical resource blocks. Further, RB start may also be the starting of the resource blocks.

[0334] In a case where the DCI format does not include the PDSCH indicator field, and the value of a certain field included in the DCI format is a prescribed value indicating that the PDSCH is not scheduled, the terminal device 1 can transmit the PUCCH including a certain type of HARQ-ACK codebook in a slot after a slot given by K1 based on the HARQ timing from the slot in which the PDCCH including the DCI format is received. Here, the certain field can be the TDRA field, or the FDRA field, or both the TDRA and FDRA fields. Further, the prescribed value can be all 0, or all 1. Further, the prescribed value can change the value according to the frequency resource allocation method of the PDSCH. Further, in a case where the frequency resource allocation of the PDSCH is the first method, the prescribed value can be all 0. Further, in a case where the frequency resource allocation of the PDSCH is the second method, the prescribed value can be all 1. Further, in a case where the frequency resource allocation of the PDSCH is the second method, the prescribed value can be a value greater than N BWP SIZE (L RBs - 1) + RB start . Here, N BWP SIZEmay be the number of resource blocks (Resource blocks) constituting a BWP. Further, L RBs may be the number of resource blocks allocated continuously. Further, RB start may be the starting of hypothetical resource blocks. Further, RB start may also be the starting of resource blocks. For example, in a case where the terminal device 1 receives the PDCCH including the DCI format triggering the Type 3 HARQ-ACK codebook in the slot n, and the value of the FDRA field included in the DCI format is a prescribed value indicating that no PDSCH is scheduled, and the value of K1 given based on the value of the HARQ timing is 4, the terminal device 1 can transmit the PUCCH including the Type 3 HARQ-ACK codebook in the slot n+4. The terminal device 1 can determine the K1 based on at least the value of the certain field included in the DCI format triggering the Type 3 HARQ-ACK codebook being the prescribed value indicating that no PDSCH is scheduled. The base station device 3 can determine the K1 and include it in the DCI format.

[0335] In a case where the DCI format does not include the PDSCH indicator field, and the value of a certain field included in the DCI format is a prescribed value indicating that no PDSCH is scheduled, the terminal device 1 can transmit the PUCCH including a certain type of HARQ-ACK codebook in a slot after a slot corresponding to K1 given based on the value of the HARQ timing, starting from a slot indicated by the value of the TDRA field included in the DCI format. Here, the certain field can be the TDRA field, or the FDRA field, or both the TDRA and FDRA fields. Further, the prescribed value can be all 0, or all 1. Further, the prescribed value can change values depending on the frequency resource allocation method of the PDSCH. Further, in a case where the frequency resource allocation of the PDSCH is the first method, the prescribed value can be all 0. Further, in a case where the frequency resource allocation of the PDSCH is the second method, the prescribed value can be all 1. Further, in a case where the frequency resource allocation of the PDSCH is the second method, the prescribed value can be a value greater than N BWP SIZE (L RBs -1) + RB start Here, N BWP SIZE may be the number of resource blocks (Resource blocks) constituting a BWP. Further, L RBs may be the number of resource blocks allocated continuously. Further, RB start may be the starting of hypothetical resource blocks. Further, RB startmay be the starting of the resource block. For example, in a case where the slot indicated by the value of the TDRA field included in the DCI format that triggers the Type 3 HARQ-ACK codebook is slot n, the value of the FDRA field included in the DCI format is a prescribed value indicating that no PDSCH is scheduled, and the value of K1 given based on the value of the HARQ timing is 4, the terminal device 1 can transmit the PUCCH including the Type 3 HARQ-ACK codebook in slot n+4. The terminal device 1 can determine the K1 based on at least the value of the certain field included in the DCI format that triggers the Type 3 HARQ-ACK codebook being the prescribed value indicating that no PDSCH is scheduled. The base station device 3 can determine the K1 and include it in the DCI format.

[0336] In a case where the value of a certain field included in the DCI format is a prescribed value indicating that no PDSCH is scheduled, the terminal device 1 can transmit the PUCCH including a certain type of HARQ-ACK codebook in a slot subsequent to a slot given by K1 based on the value of the HARQ timing, from the slot in which the PDCCH including the DCI format is received. Here, the certain field can be the TDRA field, the FDRA field, or both the TDRA and FDRA fields. Further, the prescribed value can be all 0 or all 1. Further, the prescribed value can change in value depending on the frequency resource allocation method of the PDSCH. Further, in a case where the frequency resource allocation of the PDSCH is the first method, the prescribed value can be all 0. Further, in a case where the frequency resource allocation of the PDSCH is the second method, the prescribed value can be all 1. Further, in a case where the frequency resource allocation of the PDSCH is the second method, the prescribed value can be a value greater than N BWP SIZE (L RBs -1)+RB start Here, N BWP SIZE may be the number of resource blocks (Resource block) constituting the BWP. Further, L RBs may be the number of resource blocks allocated continuously. Further, RB start may be the starting of the hypothetical resource block. Further, RB startmay be the starting of the resource block. For example, in a case where the terminal device 1 receives the PDCCH including the DCI format triggering the type 3 HARQ-ACK codebook in the slot n, the value of the FDRA field included in the DCI format is the prescribed value indicating that the PDSCH is not scheduled, and the value of K1 given based on the value of the HARQ timing is 4, the terminal device 1 can transmit the PUCCH including the type 3 HARQ-ACK codebook in the slot n+4. The terminal device 1 can determine the K1 based on at least the value of the certain field included in the DCI format triggering the type 3 HARQ-ACK codebook being the prescribed value indicating that the PDSCH is not scheduled. The base station device 3 can determine the K1 and include it in the DCI format.

[0337] In a case where the value of a certain field included in the DCI format is the prescribed value indicating that the PDSCH is not scheduled, the terminal device 1 can transmit the PUCCH including a certain type of HARQ-ACK codebook in the slot subsequent to the slot given based on the value of the HARQ timing from the slot indicated by the value of the TDRA field included in the DCI format. Here, the certain field can be the TDRA field, the FDRA field, or both the TDRA and FDRA fields. Further, the prescribed value can be all 0 or all 1. Further, the prescribed value can change the value depending on the frequency resource allocation method of the PDSCH. Further, in a case where the frequency resource allocation of the PDSCH is the first method, the prescribed value can be all 0. Further, in a case where the frequency resource allocation of the PDSCH is the second method, the prescribed value can be all 1. Further, in a case where the frequency resource allocation of the PDSCH is the second method, the prescribed value can be the value greater than N BWP SIZE (L RBs -1)+RB start Here, N BWP SIZE may be the number of resource blocks (Resource block) constituting the BWP. Further, L RBs may be the number of continuously allocated resource blocks. Further, RB start may be the starting of the hypothetical resource block. Further, RB startIt can also be the starting of a resource block. For example, in a case where a slot indicated by a value of a TDRA field included in a DCI format triggering a type 3 HARQ-ACK codebook is slot n, a value of an FDRA field included in the DCI format is a prescribed value indicating that no PDSCH is scheduled, and a value of K1 given based on a value of HARQ timing is 4, the terminal device 1 can transmit a PUCCH including the type 3 HARQ-ACK codebook in slot n+4. The terminal device 1 can determine the K1 based on at least the value of the certain field included in the DCI format triggering the type 3 HARQ-ACK codebook being the prescribed value indicating that no PDSCH is scheduled. The base station device 3 can determine the K1 and include it in the DCI format.

[0338] The DCI format not scheduling the PDSCH can be that a PDSCH received through a PDSCH reception opportunity allocated by a resource allocation included in the DCI format does not include a DL-SCH. The value of the certain field included in the DCI format being the prescribed value indicating that no PDSCH is scheduled can be that a PDSCH received through a PDSCH reception opportunity allocated by a resource allocation included in the DCI format does not include a DL-SCH. The value of a PDSCH indicator field included in the DCI format being 0 can be that a PDSCH received through a PDSCH reception opportunity allocated by a resource allocation included in the DCI format does not include a DL-SCH. In a case where a certain type of HARQ-ACK codebook is generated, the terminal device 1 can not consider a PDSCH reception opportunity in which no DL-SCH is included. The PDSCH reception opportunity can be an opportunity in which the terminal device 1 receives a PDSCH in a resource indicated by a resource allocation included in a DCI format. The PDSCH reception opportunity can be an opportunity in which the terminal device 1 receives a PDSCH in a resource indicated by one or both of a frequency resource allocation (FDRA) and a time resource allocation (TDRA) included in a DCI format.

[0339] The slot after the slot equivalent to K1 can be a slot K1 slots in time from a certain slot as a reference. For example, in a case where the value of K1 is 5 and the slot as a reference is n, the slot after the slot equivalent to K1 can be n+K1.

[0340] The terminal device 1 can ignore the value of the C-DAI included in the DCI format triggering the Type 3 HARQ-ACK codebook. The terminal device 1 can also ignore the value of the T-DAI included in the DCI format triggering the Type 3 HARQ-ACK codebook. The terminal device 1 can not take the value of the C-DAI included in the DCI format triggering the Type 3 HARQ-ACK codebook into account in the generation of a certain type of HARQ-ACK codebook. The terminal device 1 can also not take the value of the T-DAI included in the DCI format triggering the Type 3 HARQ-ACK codebook into account in the generation of a certain type of HARQ-ACK codebook.

[0341] In some or more of the HARQ processes in the scheduled cell, the terminal device 1 can not expect to receive a plurality of PDSCHs overlapping in the time domain. In some or more of the HARQ processes in the scheduled cell, the terminal device 1 can not expect to receive a PDSCH overlapping in the time domain with a certain PDSCH except for a PDSCH not including a DL-SCH scheduled by the DCI format triggering the Type 3 HARQ-ACK codebook. In some or more of the HARQ processes in the scheduled cell, the terminal device 1 can not expect to receive a second PDSCH overlapping in the time domain with a first PDSCH. Here, the first PDSCH can not include a PDSCH not including a DL-SCH scheduled by the DCI format triggering the Type 3 HARQ-ACK codebook. In some or more of the HARQ processes in the scheduled cell, the terminal device 1 can expect a PDSCH not including a DL-SCH to overlap in the time domain with a certain PDSCH. In some or more of the HARQ processes in the scheduled cell, the terminal device 1 can expect to be scheduled with a certain PDSCH overlapping in the time domain with a PDSCH not including a DL-SCH. In some or more of the HARQ processes in the scheduled cell, the terminal device 1 can receive a certain PDSCH overlapping in the time domain with a PDSCH not including a DL-SCH. In some or more of the HARQ processes in the scheduled cell, the terminal device 1 can receive a PDSCH not including a DL-SCH overlapping in the time domain with a certain PDSCH. In some or more of the HARQ processes in the scheduled cell, the terminal device 1 can expect to be scheduled with a PDSCH not including a DL-SCH overlapping in the time domain with a certain PDSCH. In some or more of the HARQ processes in the scheduled cell, the terminal device 1 can expect a certain PDSCH to overlap in the time domain with a PDSCH not including a DL-SCH.

[0342] One aspect of the present application can achieve efficient communication. One aspect of the present application can achieve efficient transmission and reception of HARQ-ACK information. One aspect of the present application can achieve efficient transmission and reception of HARQ-ACK codebooks. One aspect of the present application can eliminate mismatch of identification between the terminal device 1 and the base station device 3 in the HARQ process, and can cause the HARQ process to operate appropriately.

[0343] Hereinafter, the aspects of the various devices of one aspect of the present embodiment will be described.

[0344] (1) To achieve the above object, the present application adopts the following scheme. That is, the first aspect of the present application is a terminal device having a processor and a memory storing computer program codes, comprising: a reception unit that receives a PDCCH including DCI that triggers a Type 3 HARQ-ACK codebook; and a transmission unit that transmits a PUCCH including the triggered Type 3 HARQ-ACK codebook, the slot in which the PUCCH is transmitted being given based on K1 obtained from a PDSCH-to-HARQ_feedback timing indicator field included in the DCI, the PUCCH being transmitted K1 slots after the slot in which the PDSCH is received in a case where the DCI schedules the PDSCH, the PUCCH being transmitted in a slot that is a slot after the K1 corresponding to the K1 in a case where the DCI does not schedule the PDSCH.

[0345] (2) The second aspect of the present application is a terminal device comprising: a reception unit that receives a PDCCH including DCI that triggers a Type 3 HARQ-ACK codebook; and a transmission unit that transmits a PUCCH including the triggered Type 3 HARQ-ACK codebook, the slot in which the PUCCH is transmitted being given based on K1 obtained from a PDSCH-to-HARQ_feedback timing indicator field included in the DCI, the PUCCH being transmitted K1 slots after the slot in which the PDSCH is received in a case where the DCI schedules the PDSCH, the PUCCH being transmitted in a slot that is a slot after the K1 corresponding to the K1 in a case where the DCI does not schedule the PDSCH.

[0346] (3) The third aspect of the present application is a base station device comprising: a transmission unit that transmits a PDCCH including DCI that triggers a Type 3 HARQ-ACK codebook; and a reception unit that receives a PUCCH including the triggered Type 3 HARQ-ACK codebook, the slot in which the PUCCH is received being given based on K1 obtained from a PDSCH-to-HARQ_feedback timing indicator field included in the DCI, the PUCCH being received K1 slots after the slot in which the PDSCH is transmitted in a case where the DCI schedules the PDSCH, the PUCCH being received in a slot that is a slot after the K1 corresponding to the K1 in a case where the DCI does not schedule the PDSCH.

[0347] (4) A fourth aspect of the present application is a base station device including: a transmission section that transmits a PDCCH including DCI of a type 3 HARQ-ACK codebook; and a reception section that receives a PUCCH including the type 3 HARQ-ACK codebook triggered, a slot in which the PUCCH is received being given based on K1 obtained from a PDSCH-to-HARQ_feedback timing indicator field included in the DCI, the PUCCH being received K1 slots after a slot in which a PDSCH is transmitted in a case where the DCI schedules the PDSCH, the PUCCH being received in a slot corresponding to a slot after the K1 in a case where the DCI does not schedule the PDSCH.

[0348] The program operating in the base station device 3 and the terminal device 1 according to the aspect of the present application can be a program (a program causing a computer to function) that controls a CPU (Central Processing Unit) or the like to realize the functions of the above-described embodiments according to the aspect of the present application. Then, information processed by these devices is temporarily stored in a RAM (Random Access Memory) while it is processed, and thereafter, stored in various ROMs such as a Flash ROM (Read Only Memory), an HDD (Hard Disk Drive), and the like, and read out, corrected, and written by the CPU as necessary.

[0349] Note that a part of the terminal device 1 and the base station device 3 according to the above-described embodiments can also be realized by a computer. In this case, a program for realizing the control functions can be recorded in a computer-readable recording medium, and realized by reading the program recorded in the recording medium into a computer system and executing.

[0350] Note that the "computer system" referred to here means a computer system built in the terminal device 1 or the base station device 3, and a computer system including an OS, a peripheral device, and the like. Further, the "computer-readable recording medium" means a removable medium such as a flexible disk, a magneto-optical disk, a ROM, a CD-ROM, and the like, and a storage device such as a hard disk built in the computer system.

[0351] Moreover, the "computer-readable recording medium" can include a medium that dynamically stores the program for a short time, like a communication line in the case where the program is transmitted via a network such as the Internet or a communication line such as a telephone line, and a medium that stores the program for a fixed period of time, like a volatile memory inside a computer system that is a server or a client in this case. Furthermore, the above-described program can be a program for realizing a part of the above-described functions, and can also be a program that can realize the above-described functions by being combined with a program already recorded in a computer system.

[0352] The terminal device 1 can be constituted by at least one processor and at least one memory including computer program instructions (computer programs). The memory and the computer program instructions (computer programs) can be such a constitution that the terminal device 1 performs the actions, processes described in the above-described embodiments using the processor. The base station device 3 can be constituted by at least one processor and at least one memory including computer program instructions (computer programs). The memory and the computer program instructions (computer programs) can be such a constitution that the base station device 3 performs the actions, processes described in the above-described embodiments using the processor.

[0353] Furthermore, the base station device 3 in the above-described embodiments can also be realized as an assembly (device group) constituted by a plurality of devices. Each device constituting the device group can have a part or all of each function or each functional block of the base station device 3 of the above-described embodiments. As the device group, it is sufficient to have all of each function or each functional block of the base station device 3. Furthermore, the terminal device 1 of the above-described embodiments can also communicate with the base station device as an assembly.

[0354] Furthermore, the base station device 3 in the above-described embodiments can be an EUTRAN (Evolved Universal Terrestrial Radio Access Network) and / or an NG-RAN (NextGen RAN, NR RAN). Furthermore, the base station device 3 in the above-described embodiments can also have a part or all of the functions of a higher node for an eNodeB and / or a gNB.

[0355] Furthermore, a part or all of the terminal device 1, the base station device 3 of the above-described embodiments can be realized as an LSI that is typically an integrated circuit, or as a chip set. Each functional block of the terminal device 1, the base station device 3 can be individual chip, or a part or all of them can be integrated into a chip. Furthermore, the method of integration is not limited to an LSI, and a dedicated circuit or a general purpose processor can be used. Furthermore, in a case where with the advancement of semiconductor technology, a technology of an integrated circuit that replaces LSIs appears, an integrated circuit based on the technology can also be used.

[0356] Further, in the above-described embodiments, the terminal device is described as one example of the communication device, but the application of the present application is not limited thereto, and can be applied to a stationary or non-movable electronic device, such as a terminal device or a communication device, provided indoors or outdoors, such as an AV device, a kitchen device, a cleaning / washing device, an air conditioning device, an office device, a vending machine, and other living devices.

[0357] The above-described embodiments of the present application have been described in detail with reference to the accompanying drawings, but the specific configuration is not limited to the present embodiments, and design changes and the like within the scope of the gist of the present application are also included. Further, one aspect of the present application can be variously changed within the scope of the technical means shown in the technical solution, and embodiments obtained by appropriately combining the technical means disclosed in the different embodiments are also included in the technical scope of the present application. Further, a configuration obtained by replacing elements that have the same effects as the elements described in the above-described embodiments with each other is also included.

[0358] Industrial applicability

[0359] One aspect of the present application can be used, for example, in a communication system, a communication device (such as a portable telephone device, a base station device, a wireless LAN device, or a sensor device), an integrated circuit (such as a communication chip), or a program.

[0360] Explanation of reference numerals

[0361] 1 (1A, 1B, 1C) terminal device

[0362] 3 base station device

[0363] 10, 30 wireless transceiver section

[0364] 11, 31 antenna section

[0365] 12, 32 RF section

[0366] 13, 33 baseband section

[0367] 14, 34 upper layer processing section

[0368] 15, 35 medium access control layer processing section

[0369] 16, 36 radio resource control layer processing section

Claims

1. A terminal device comprising: a reception section that receives a PDCCH including a DCI including a dedicated field that triggers a Type 3 HARQ-ACK codebook; and a transmission section that transmits a PUCCH including the triggered Type 3 HARQ-ACK codebook, a slot in which the PUCCH is transmitted is given based on K1 obtained from a PDSCH-to-HARQ_feedback timing indicator field included in the DCI, in a case where the DCI schedules a PDSCH, the PUCCH is transmitted K1 slots after a slot in which the PDSCH is received, in a case where the DCI does not schedule a PDSCH, the PUCCH is transmitted K1 slots after a slot in which the PDCCH is received.

2. The terminal device according to claim 1, wherein the Type 3 HARQ-ACK codebook includes HARQ-ACK information for all HARQ processes.

3. A base station device comprising: a transmission section that transmits a PDCCH including a DCI including a dedicated field that triggers a Type 3 HARQ-ACK codebook; and a reception section that receives a PUCCH including the triggered Type 3 HARQ-ACK codebook, a slot in which the PUCCH is received is given based on K1 obtained from a PDSCH-to-HARQ_feedback timing indicator field included in the DCI, in a case where the DCI schedules a PDSCH, the PUCCH is received K1 slots after a slot in which the PDSCH is transmitted, in a case where the DCI does not schedule a PDSCH, the PUCCH is received K1 slots after a slot in which the PDCCH is transmitted.

4. The base station device according to claim 3, wherein the Type 3 HARQ-ACK codebook includes HARQ-ACK information for all HARQ processes.

5. A communication method for a terminal device, the communication method comprising: a step of receiving a PDCCH including a DCI including a dedicated field that triggers a Type 3 HARQ-ACK codebook; and a step of transmitting a PUCCH including the triggered Type 3 HARQ-ACK codebook, a slot in which the PUCCH is transmitted is given based on K1 obtained from a PDSCH-to-HARQ_feedback timing indicator field included in the DCI, in a case where the DCI schedules a PDSCH, the PUCCH is transmitted K1 slots after a slot in which the PDSCH is received, in a case where the DCI does not schedule a PDSCH, the PUCCH is transmitted K1 slots after a slot in which the PDCCH is received. ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ 6. The communication method according to claim 5, wherein the type 3 HARQ-ACK codebook contains HARQ-ACK information for all HARQ processes.

Images