JP7638890B2 - Terminal device, base station device, and communication method - Google Patents

Description

The present invention relates to a terminal device, a base station device, and a communication method.
This application claims priority to Japanese Patent Application No. 2019-206776, filed in Japan on November 15, 2019, the contents of which are incorporated herein by reference.

A radio access method and a radio network for cellular mobile communication (hereinafter referred to as "Long Term Evolution (LTE)" or "EUTRA: Evolved Universal Terrestrial Radio Access") are being studied in the ^3rd Generation Partnership Project (3GPP). In LTE, a base station device is also called eNodeB (evolved NodeB), and a terminal device is also called UE (User Equipment). LTE is a cellular communication system in which areas covered by base station devices are arranged in multiple cell shapes. A single base station device may manage multiple serving cells.

3GPP is currently studying the next-generation standard (NR: New Radio) to propose it for IMT (International Mobile Telecommunication)-2020, a standard for next-generation mobile communication systems formulated by the International Telecommunication Union (ITU) (Non-Patent Document 1). NR is required to meet the requirements of three scenarios, eMBB (enhanced Mobile BroadBand), mMTC (massive Machine Type Communication), and URLLC (UltraReliable and Low Latency Communication), within a single technology framework.

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

One aspect of the present invention provides a terminal device that communicates efficiently, a communication method used in the terminal device, a base station device that communicates efficiently, and a communication method used in the base station device.

(1) A first aspect of the present invention is a terminal device comprising: a receiving unit that receives a first PDSCH; and a transmitting unit that reports a first HARQ-ACK codebook of X bits for the first PDSCH via a first PUCCH transmission opportunity, the terminal device receiving a second PDSCH after the first PUCCH transmission opportunity, generating a second HARQ-ACK codebook for the second PDSCH, deleting X bits from the beginning of the second HARQ-ACK codebook, and reporting the second HARQ-ACK codebook and HARQ-ACK information including the first HARQ-ACK codebook via the second PUCCH transmission opportunity.
(2) A second aspect of the present invention is a terminal device comprising: a receiving unit that receives a first PDSCH; and a transmitting unit that reports a first HARQ-ACK codebook of X bits for the first PDSCH via a first PUCCH transmission opportunity, and includes receiving a second PDSCH after the first PUCCH transmission opportunity, generating a second HARQ-ACK codebook for the second PDSCH, and reporting HARQ-ACK information generated by adding bits from the X+1th bit onwards of the second HARQ-ACK codebook to the first HARQ-ACK information via the second PUCCH transmission opportunity.
(3) A third aspect of the present invention is a terminal device comprising: a receiving unit that receives a first PDSCH; and a transmitting unit that reports a first HARQ-ACK codebook of X bits for the first PDSCH via a first PUCCH transmission opportunity, the terminal device receiving a second PDSCH after the first PUCCH transmission opportunity, generating a second HARQ-ACK codebook for the second PDSCH, and reporting HARQ-ACK information generated by replacing bits from the beginning of the second HARQ-ACK codebook with the first HARQ-ACK codebook via the second PUCCH transmission opportunity.
(4) A fourth aspect of the present invention is a terminal device comprising: a receiving unit that receives a first PDSCH; and a transmitting unit that reports a first HARQ-ACK codebook including at least a HARQ-ACK bit for the first PDSCH via a PUCCH corresponding to a first PUCCH transmission opportunity, the terminal device receiving the second PDSCH after the first PUCCH transmission opportunity, generating a second HARQ-ACK codebook including at least a HARQ-ACK bit for the second PDSCH, generating HARQ-ACK information based at least on the second HARQ-ACK codebook and parameters used in generating the first HARQ-ACK codebook, and reporting the HARQ-ACK information via the second PUCCH transmission opportunity.
(5) A fifth aspect of the present invention is a base station device comprising: a transmitter that transmits a first PDSCH; and a receiver that receives a first HARQ-ACK codebook of X bits for the first PDSCH via a first PUCCH transmission opportunity, wherein a second PDSCH is transmitted after the first PUCCH transmission opportunity, a second HARQ-ACK codebook for the second PDSCH is generated, X bits are deleted from the top of the second HARQ-ACK codebook, and the second HARQ-ACK codebook and HARQ-ACK information including the first HARQ-ACK codebook are received via the second PUCCH transmission opportunity.
(6) A sixth aspect of the present invention is a base station device comprising: a transmitter that transmits a first PDSCH; and a receiver that receives a first HARQ-ACK codebook of X bits for the first PDSCH via a first PUCCH transmission opportunity, wherein a second PDSCH is transmitted after the first PUCCH transmission opportunity, a second HARQ-ACK codebook for the second PDSCH is generated, and bits from the X+1th bit onwards of the second HARQ-ACK codebook are added to the first HARQ-ACK codebook to generate HARQ-ACK information, and the generated HARQ-ACK information is received via the second PUCCH transmission opportunity.
(7) A seventh aspect of the present invention is a base station device comprising: a transmitter that transmits a first PDSCH; and a receiver that receives a first HARQ-ACK codebook of X bits for the first PDSCH via a first PUCCH transmission opportunity, the base station device transmitting a second PDSCH after the first PUCCH transmission opportunity, generating a second HARQ-ACK codebook for the second PDSCH, and receiving HARQ-ACK information generated by replacing bits from the top of the second HARQ-ACK codebook with the first HARQ-ACK codebook via the second PUCCH transmission opportunity.
(8) An eighth aspect of the present invention is a base station device comprising: a transmitter unit that transmits a first PDSCH; and a receiver unit that receives a first HARQ-ACK codebook including at least a HARQ-ACK bit for the first PDSCH via a PUCCH corresponding to a first PUCCH transmission opportunity, the receiver unit transmitting the second PDSCH after the first PUCCH transmission opportunity, generating a second HARQ-ACK codebook including at least a HARQ-ACK bit for the second PDSCH, generating HARQ-ACK information based at least on the second HARQ-ACK codebook and parameters used in generating the first HARQ-ACK codebook, and receiving the HARQ-ACK information via the second PUCCH transmission opportunity.
(9) A ninth aspect of the present invention is a communication method for use in a terminal device, the communication method including: receiving a first PDSCH; reporting a first HARQ-ACK codebook of X bits for the first PDSCH via a first PUCCH transmission opportunity; receiving a second PDSCH after the first PUCCH transmission opportunity; generating a second HARQ-ACK codebook for the second PDSCH; deleting X bits from the top of the second HARQ-ACK codebook; and reporting the second HARQ-ACK codebook and HARQ-ACK information including the first HARQ-ACK codebook via a second PUCCH transmission opportunity.
(10) A tenth aspect of the present invention is a communication method for use in a terminal device, comprising: receiving a first PDSCH; reporting a first HARQ-ACK codebook of X bits for the first PDSCH via a first PUCCH transmission opportunity; receiving a second PDSCH after the first PUCCH transmission opportunity; generating a second HARQ-ACK codebook for the second PDSCH; and reporting HARQ-ACK information generated by adding bits from the X+1th bit onwards of the second HARQ-ACK codebook to the first HARQ-ACK information via a second PUCCH transmission opportunity.
(11) An eleventh aspect of the present invention is a communication method for use in a terminal device, the communication method including: receiving a first PDSCH; reporting a first HARQ-ACK codebook of X bits for the first PDSCH via a first PUCCH transmission opportunity; receiving a second PDSCH after the first PUCCH transmission opportunity; generating a second HARQ-ACK codebook for the second PDSCH; deleting X bits from the top of the second HARQ-ACK codebook; and reporting the second HARQ-ACK codebook and HARQ-ACK information including the first HARQ-ACK codebook via a second PUCCH transmission opportunity.
(12) A twelfth aspect of the present invention is a communication method used in a terminal device, the communication method including: receiving a first PDSCH; reporting a first HARQ-ACK codebook including at least a HARQ-ACK bit for the first PDSCH via a PUCCH corresponding to a first PUCCH transmission opportunity; receiving the second PDSCH after the first PUCCH transmission opportunity; and generating a second HARQ-ACK codebook including at least a HARQ-ACK bit for the second PDSCH;
generating HARQ-ACK information based at least on the second HARQ-ACK codebook and parameters used to generate the first HARQ-ACK codebook; and reporting the HARQ-ACK information via a second PUCCH transmission opportunity.
(13) A thirteenth aspect of the present invention is a communication method for use in a base station device, the communication method including: transmitting a first PDSCH; receiving a first HARQ-ACK codebook of X bits for the first PDSCH via a first PUCCH transmission opportunity; transmitting a second PDSCH after the first PUCCH transmission opportunity; generating a second HARQ-ACK codebook for the second PDSCH; deleting X bits from the top of the second HARQ-ACK codebook; and receiving the second HARQ-ACK codebook and HARQ-ACK information including the first HARQ-ACK codebook via a second PUCCH transmission opportunity.
(14) A fourteenth aspect of the present invention is a communication method for use in a base station device, the communication method including: transmitting a first PDSCH; receiving a first HARQ-ACK codebook of X bits for the first PDSCH via a first PUCCH transmission opportunity; transmitting a second PDSCH after the first PUCCH transmission opportunity; generating a second HARQ-ACK codebook for the second PDSCH; and receiving, via a second PUCCH transmission opportunity, HARQ-ACK information generated by adding bits from the X+1th bit onwards of the second HARQ-ACK codebook to the first HARQ-ACK codebook.
(15) A fifteenth aspect of the present invention is a communication method for use in a base station device, the communication method including: transmitting a first PDSCH; receiving a first HARQ-ACK codebook of X bits for the first PDSCH via a first PUCCH transmission opportunity; transmitting a second PDSCH after the first PUCCH transmission opportunity; generating a second HARQ-ACK codebook for the second PDSCH; and receiving, via the second PUCCH transmission opportunity, HARQ-ACK information generated by replacing bits from the top of the second HARQ-ACK codebook with the first HARQ-ACK codebook.
(16) A sixteenth aspect of the present invention is a communication method for use in a base station device, comprising: transmitting a first PDSCH; receiving a first HARQ-ACK codebook including at least a HARQ-ACK bit for the first PDSCH via a PUCCH corresponding to a first PUCCH transmission opportunity; transmitting the second PDSCH after the first PUCCH transmission opportunity; generating a second HARQ-ACK codebook including at least a HARQ-ACK bit for the second PDSCH; generating HARQ-ACK information based at least on the second HARQ-ACK codebook and parameters used in generating the first HARQ-ACK codebook; and receiving the HARQ-ACK information via the second PUCCH transmission opportunity.

According to one aspect of the present invention, a terminal device can communicate efficiently. Also, a base station device can communicate efficiently.

1 is a conceptual diagram of a wireless communication system according to an embodiment of the present invention. 1 is an example showing a relationship between N ^slot _symb , a subcarrier interval setting μ, a slot setting, and a CP setting according to an aspect of the present embodiment. FIG. 2 is a schematic diagram illustrating an example of a resource grid in a subframe according to an aspect of the present embodiment. A diagram showing an example of a monitoring opportunity for a search area set according to one aspect of this embodiment. 1 is a schematic block diagram showing a configuration of a terminal device 1 according to an aspect of the present embodiment. 1 is a schematic block diagram showing a configuration of a base station device 3 according to one aspect of the present embodiment. FIG. 11 is a diagram showing an example of correspondence between a monitoring occasion for a search space set (Monitoring occasion for search space set) and a monitoring occasion for a PDCCH (Monitoring occasion for PDCCH) according to one aspect of this embodiment. A diagram showing an example configuration of a set of PDCCH monitoring opportunities for slot n in one embodiment of the present invention. A diagram showing an example configuration of a set of PDCCH monitoring opportunities for slot n in one embodiment of the present invention. A diagram showing an example configuration of a set of PDCCH monitoring opportunities for slot n in one embodiment of the present invention. A figure showing an example of counter DAI and total DAI indication according to one embodiment of the present invention. A diagram showing an example of a procedure for configuring a HARQ-ACK codebook in one embodiment of the present invention. A diagram showing an example of a procedure for configuring a HARQ-ACK codebook in one embodiment of the present invention. A diagram showing an example of a procedure for configuring a HARQ-ACK codebook in one embodiment of the present invention. A figure showing an example of generating HARQ-ACK information in one aspect of this embodiment. A figure showing an example of generating HARQ-ACK information in one aspect of this embodiment. A figure showing an example of generating HARQ-ACK information in one aspect of this embodiment. A figure showing an example of generating HARQ-ACK information in one aspect of this embodiment.

The following describes an embodiment of the present invention.

"A and/or B" may be a term including "A", "B", or "A and B".

ceil(A) is the ceiling function of A. ceil(A) may be a function that outputs the smallest integer in a range that is not less than A. log2(B) is a base 2 logarithmic function for B. pow(A,B) is a power function defined for constant A. That is, pow(A,B) is A to the Bth power. mod(E,F) may be a function that outputs the remainder when E is divided by F. mod(E,F) may be a function that outputs a value corresponding to the remainder when E is divided by F. (E)mod(F) may be a function that outputs the remainder when E is divided by F. (E)mod(F) may be a function that outputs a value corresponding to the remainder when E is divided by F.

A parameter or information indicating one or more values may mean that the parameter or information at least includes a parameter or information indicating the one or more values. The upper layer parameter may be a single upper layer parameter. The upper layer parameter may be an information element (IE) including multiple parameters.

Figure 1 is a conceptual diagram of a wireless communication system according to one aspect of this embodiment. In Figure 1, the wireless communication system comprises terminal devices 1A to 1C and a base station device 3. Hereinafter, terminal devices 1A to 1C are also referred to as terminal device 1.

The base station device 3 may be configured to include one or both of an MCG (Master Cell Group) and an 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 may be a serving cell provided based on an initial connection. The MCG may be configured to include one or more SCells (Secondary Cells). The SCG may be configured to include one or more SCells. The serving cell identity is a short identifier for identifying a serving cell. The serving cell identity may be provided by a higher layer parameter.

The frame structure is explained below.

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

The subcarrier spacing (SCS) may be given by a subcarrier spacing Δf=2 ^μ ·15 kHz. For example, the subcarrier spacing configuration μ may be set to any of 0, 1, 2, 3, 4, and/or 5. For a certain BandWidth Part (BWP), the subcarrier spacing configuration μ may be given by higher layer parameters.

In the wireless communication system according to one aspect of the present embodiment, a time unit _Tc is used to express a length in the time domain. The time unit _Tc may be given by _Tc = 1/(Δf _max · N _f ). Δf _max may be a maximum value of a subcarrier spacing supported in the wireless communication system according to one aspect of the present embodiment. Δf _max may be Δf _max = 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.

The constant κ may be a value indicating the relationship between the reference subcarrier spacing and _Tc . The constant κ may be used for the length of the subframe. The number of slots included in the subframe may be given based at least on the constant κ. Δf _ref is the reference subcarrier spacing, and N _f,ref is a value corresponding to the reference subcarrier spacing.

Downlink transmission and/or uplink transmission are composed of a 10 ms frame. The frame is composed of 10 subframes. The length of the subframe is 1 ms. The frame length may be given regardless of the subcarrier spacing Δf. That is, the frame setting may be given regardless of μ. The subframe length may be given regardless of the subcarrier spacing Δf. That is, the subframe setting may be given regardless of μ.

For a certain subcarrier spacing setting μ, the number and index of slots included in a subframe may be given. For example, the first slot number n ^μ _s may be given in the range from 0 to N ^{subframe, μ} _slot −1 in ascending order in the subframe. For a certain subcarrier spacing setting μ, the number and index of slots included in a frame may be given. For example, the second slot number n ^μ _s,f may be given in the range from 0 to N ^{frame, μ} _slot −1 in ascending order in the frame. N ^slot _symb consecutive OFDM symbols may be included in one slot. N ^slot _symb may be given at least based on a slot configuration and/or a part or all of a CP (Cyclic Prefix) configuration. The slot configuration may be given by at least an upper layer parameter tdd-UL-DL-ConfigurationCommon. The CP configuration may be provided based at least on a higher layer parameter. The CP configuration may be provided based at least on a dedicated RRC signaling. The first slot number and the second slot number are also referred to as slot numbers (slot indexes).

Fig. 2 is an example showing the relationship between N ^slot _symb , subcarrier interval setting μ, and CP setting according to one aspect of the present embodiment. In Fig. 2A, for example, when the subcarrier interval setting μ is 2 and the CP setting is normal cyclic prefix (CP), N ^slot _symb = 14, N ^{frame, μ} _slot = 40, and N ^{subframe, μ} _slot = 4. Also, in Fig. 2B, for example, when the subcarrier interval setting μ is 2 and the CP setting is extended cyclic prefix (CP), N ^slot _symb = 12, N ^{frame, μ} _slot = 40, and N ^{subframe, μ} _slot = 4.

The physical resources are explained below.

An antenna port is defined by the fact that the channel on which a symbol is transmitted at one antenna port can be estimated from the channel on which another symbol is transmitted at the same antenna port. If the large scale properties of the channel on which a symbol is transmitted at one antenna port can be estimated from the channel on which a symbol is transmitted at the other antenna port, the two antenna ports are said to be Quasi Co-Located (QCL). The large scale properties may include at least the long-range properties of the channel. The large scale properties may include at least some or all of the delay spread, Doppler spread, Doppler shift, average gain, average delay, and spatial Rx parameters. The first antenna port and the second antenna port are QCL with respect to beam parameters may be the same as the receiving beam assumed by the receiving side for the first antenna port and the receiving beam assumed by the receiving side for the second antenna port. The first antenna port and the second antenna port being QCL with respect to the beam parameters may mean that the transmission beam assumed by the receiving side for the first antenna port and the transmission beam assumed by the receiving side for the second antenna port are the same. The terminal device 1 may assume that the two antenna ports are QCL when the large-scale characteristics of the channel through which symbols are transmitted at one antenna port can be estimated from the channel through which symbols are transmitted at another antenna port. The two antenna ports being QCL may mean that the two antenna ports are assumed to be QCL.

For each subcarrier spacing configuration and set of carriers, a resource grid of ^NμRB _,x ^NRBsc _subcarriers and N ^(μ) _symb ^{Nsubframe,μsymb} _OFDM symbols is provided. ^NμRB _,x may denote the number of resource blocks provided for the subcarrier spacing configuration μ for carrier x. ^NμRB _,x may be the maximum number of resource blocks provided for the subcarrier spacing configuration μ for carrier x. Carrier x may denote either a downlink carrier or an uplink _carrier . That is, x may be "DL" or "UL _" . ^NμRB is a designation that includes ^NμRB _,DL and/or ^NμRB _,UL . ^NRBsc may denote the number of subcarriers included in one resource block. At least one resource grid may be provided for each antenna port p, and/or for each subcarrier spacing setting μ, and/or for each transmission direction setting. The transmission direction includes at least a downlink (DL) and an uplink (UL). Hereinafter, a set of parameters including at least the antenna port p, the subcarrier spacing setting μ, and some or all of the transmission direction settings is also referred to as a first radio parameter set. That is, one resource grid may be provided for each first radio parameter set.

In the downlink, a carrier included in a serving cell is called a downlink carrier (or downlink component carrier). In the uplink, a carrier included in a serving cell is called an uplink carrier (uplink component carrier). Downlink component carriers and uplink component carriers are collectively called component carriers (or carriers).

Each element in the resource grid provided for each first radio parameter set is called a resource element. The resource element is identified by a frequency domain index k _sc and a time domain index l _sym . For a certain first radio parameter set, the resource element is identified by a frequency domain index k _sc and a time domain index l _sym . A resource element identified by a frequency domain index k _sc and a time domain index l _sym is also called a resource element (k _sc , l _sym ). The frequency domain index k _sc indicates any value from 0 to N ^μ _RB N ^RB _sc -1. N ^μ _RB may be the number of resource blocks provided for the setting μ of the subcarrier spacing. ^{N RB} _sc is the number of subcarriers included in a resource block, and N ^RB _sc =12. The frequency domain index k _sc may correspond to the subcarrier index k _sc . The time domain index l _sym may correspond to the OFDM symbol index l _sym .

FIG. 3 is a schematic diagram showing an example of a resource grid in a subframe according to an aspect of the present embodiment. In the resource grid of FIG. 3, the horizontal axis is a time domain index l _sym and the vertical axis is a frequency domain index k _sc . In one subframe, the frequency domain of the resource grid includes N ^μ _RB N ^RB _sc subcarriers. In one subframe, the time domain of the resource grid may include 14·2 ^μ OFDM symbols. One resource block includes N ^RB _sc subcarriers. The time domain of the resource block may correspond to one OFDM symbol. The time domain of the resource block may correspond to 14 OFDM symbols. The time domain of the resource block may correspond to one or more slots. The time domain of the resource block may correspond to one subframe.

The terminal device 1 may be instructed to transmit and receive using only a subset of the resource grid. The subset of the resource grid may also be referred to as a BWP, and the BWP may be given based on at least a part or all of the upper layer parameters and/or the DCI. The BWP is also referred to as a band part (BP: bandwidth part). That is, the terminal device 1 may not be instructed to transmit and receive using all the sets of the resource grid. That is, the terminal device 1 may be instructed to transmit and receive using some of the frequency resources in the resource grid. One BWP may be composed of multiple resource blocks in the frequency domain. One BWP may be composed of multiple consecutive resource blocks in 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.

One or more downlink BWPs may be configured for the terminal device 1. The terminal device 1 may attempt to receive a physical channel (e.g., PDCCH, PDSCH, SS/PBCH, etc.) in one of the one or more downlink BWPs. The one downlink BWP is also referred to as an activated downlink BWP.

One or more uplink BWPs may be configured for the terminal device 1. The terminal device 1 may attempt to transmit a physical channel (e.g., PUCCH, PUSCH, PRACH, etc.) in one of the one or more uplink BWPs. The one uplink BWP is also referred to as an activated uplink BWP.

A set of downlink BWPs may be configured for each serving cell. The set of downlink BWPs may include one or more downlink BWPs. A set of uplink BWPs may be configured for each serving cell. The set of uplink BWPs may include one or more uplink BWPs.

The higher layer parameters are parameters included in the higher layer signal. The higher layer signal may be RRC (Radio Resource Control) signaling or MAC CE (Medium Access Control Element). Here, the higher layer signal may be an RRC layer signal or a MAC layer signal.

The higher layer signal may be common RRC signaling. The common RRC signaling may include at least some or all of the following features C1 to C3.
Feature C1) Mapped to the BCCH logical channel or the CCCH logical channel Feature C2) Includes at least the radioResourceConfigCommon information element Feature C3) Mapped to the PBCH

The radioResourceConfigCommon information element may include information indicating a configuration commonly used in the serving cell. The configuration commonly used in the serving cell may include at least a PRACH configuration. The PRACH configuration may at least indicate one or more random access preamble indexes. The PRACH configuration may at least indicate a time/frequency resource of the PRACH.

The higher layer signaling may be dedicated RRC signaling. The dedicated RRC signaling may comprise at least some or all of the following features D1 to D2:
Feature D1) Mapped to DCCH logical channel Feature D2) Includes at least radioResourceConfigDedicated information element

The radioResourceConfigDedicated information element may include at least information indicating a setting specific to the terminal device 1. The radioResourceConfigDedicated information element may include at least information indicating a BWP setting. The BWP setting may indicate at least the frequency resource of the BWP.

For example, the MIB, the first system information, and the second system information may be included in the common RRC signaling. Also, an upper layer message that is mapped to the DCCH logical channel and includes at least radioResourceConfigCommon may be included in the common RRC signaling. Also, an upper layer message that is mapped to the DCCH logical channel and does not include the radioResourceConfigCommon information element may be included in the dedicated RRC signaling. Also, an upper layer message that is mapped to the DCCH logical channel and includes at least the radioResourceConfigDedicated information element may be included in the dedicated RRC signaling.

The first system information may at least indicate 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 an SS/PBCH. The first system information may include at least information related to a PRACH resource. The first system information may include at least information related to setting up an initial connection. The second system information may be system information other than the first system information.

The radioResourceConfigDedicated information element may include at least information related to PRACH resources. The radioResourceConfigDedicated information element may include at least information related to setting up an initial connection.

The following describes physical channels and physical signals relating to various aspects of this embodiment.

An uplink physical channel may correspond to a set of resource elements carrying information generated in a higher layer. An uplink physical channel is a physical channel used in an uplink carrier. In a wireless communication system according to one aspect of the present embodiment, at least some or all of the following uplink physical channels are used:
・PUCCH (Physical Uplink Control CHannel)
・PUSCH (Physical Uplink Shared CHannel)
・PRACH (Physical Random Access CHannel)

The PUCCH may be used to transmit uplink control information (UCI). The uplink control information includes some or all of the HARQ-ACK (Hybrid Automatic Repeat request ACKnowledgement) corresponding to the channel state information (CSI), the scheduling request (SR), and the transport block (TB, MAC PDU, Medium Access Control Protocol Data Unit, DL-SCH, Downlink-Shared Channel, PDSCH, Physical Downlink Shared Channel).

The HARQ-ACK information may include at least a HARQ-ACK bit corresponding to at least one transport block. The HARQ-ACK bit may indicate an ACK (acknowledgement) or a NACK (negative-acknowledgement) corresponding to one or more transport blocks. The HARQ-ACK information may 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 may correspond to a PDSCH including the one or more transport blocks. The HARQ-ACK bit may indicate an ACK or a NACK corresponding to one CBG (Code Block Group) included in the transport block.

The scheduling request (SR) may be used at least to request PUSCH resources for initial transmission. The scheduling request bit may 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 may indicate that PUSCH resources for initial transmission are requested by the terminal device 1. The positive SR may indicate that the scheduling request is triggered by the upper layer. The positive SR may be transmitted when the upper layer instructs the transmission of a scheduling request. The scheduling request bit indicating a negative SR is also referred to as "a negative SR is transmitted". The negative SR may indicate that PUSCH resources for initial transmission are not requested by the terminal device 1. The negative SR may indicate that the scheduling request is not triggered by the upper layer. A negative SR may be transmitted when no scheduling request is indicated to be transmitted by higher layers.

The channel state information may include at least some or all of a Channel Quality Indicator (CQI), a Precoder Matrix Indicator (PMI), and a Rank Indicator (RI). The CQI is an index related to the quality of the channel (e.g., propagation strength), and the PMI is an index indicating the precoder. The RI is an index indicating the transmission rank (or the number of transmission layers).

The PUCCH supports PUCCH formats (PUCCH format 0 to PUCCH format 4). The PUCCH format may be mapped to the PUCCH and transmitted. The PUCCH format may be transmitted on the PUCCH. The transmission of the PUCCH format may mean that the PUCCH is transmitted.

The PUSCH is used at least to transmit transport blocks (TB, MAC PDU, UL-SCH, PUSCH). The PUSCH may be used at least to transmit transport blocks, HARQ-ACK information, channel state information, and some or all of the scheduling request. The PUSCH is used at least to transmit random access message 3.

The PRACH is used at least to transmit a random access preamble (random access message 1). The PRACH may be used at least to indicate some or all of the initial connection establishment procedure, the handover procedure, the connection re-establishment procedure, synchronization (timing adjustment) for the transmission of the PUSCH, and the request for resources for the PUSCH. The random access preamble may be used to notify the base station device 3 of an index (random access preamble index) provided by a higher layer of the terminal device 1.

In Fig. 1, the following uplink physical signals are used in uplink wireless communication: The uplink physical signals may not be used to transmit information output from higher layers, but are used by the physical layer.
・UL DMRS (UpLink Demodulation Reference Signal)
・SRS (Sounding Reference Signal)
・UL PTRS (UpLink Phase Tracking Reference Signal)

The UL DMRS is related to the transmission of the PUSCH and/or the PUCCH.
The DMRS is multiplexed with the PUSCH or PUCCH. The base station device 3 may use the UL DMRS to perform propagation path correction of the PUSCH or PUCCH. Hereinafter, transmitting the PUSCH and the UL DMRS related to the PUSCH together is simply referred to as transmitting the PUSCH. Hereinafter, transmitting the PUCCH and the UL DMRS related to the PUCCH together is simply referred to as transmitting the PUCCH. The UL DMRS related to the PUSCH is also referred to as the UL DMRS for the PUSCH. The UL DMRS related to the PUCCH is also referred to as the UL DMRS for the PUCCH.

The SRS may not be related to the transmission of the PUSCH or PUCCH. The base station device 3 may use the SRS for measuring the channel state. The SRS may be transmitted at the end of a subframe in an uplink slot or a predetermined number of OFDM symbols from the end.

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

1, the following downlink physical channels are used in downlink wireless communication from the base station device 3 to the terminal device 1. The downlink physical channels are used by the physical layer to transmit information output from a higher layer.
・PBCH (Physical Broadcast Channel)
・PDCCH (Physical Downlink Control Channel)
・PDSCH (Physical Downlink Shared Channel)

The PBCH is used at least to transmit a Master Information Block (MIB, BCH, Broadcast Channel). The PBCH may be transmitted based on a predetermined transmission interval. The PBCH may be transmitted at intervals of 80 ms. The PBCH may be transmitted at intervals of 160 ms. The contents of the information contained in the PBCH may be updated every 80 ms. Some or all of the information contained in the PBCH may be updated every 160 ms. The PBCH may be composed of 288 subcarriers. The PBCH may be composed of 2, 3, or 4 OFDM symbols. The MIB may include information related to an identifier (index) of the synchronization signal. The MIB may include information indicating at least a portion of the slot number, subframe number, and/or radio frame number in which the PBCH is transmitted.

The PDCCH is used at least for transmitting downlink control information (DCI). The PDCCH may be transmitted including at least the downlink control information. The PDCCH may include the downlink control information. The downlink control information is also referred to as a DCI format. The downlink control information may include at least either a downlink grant or an uplink grant. The DCI format used for scheduling the PDSCH is also referred to as a downlink DCI format. The DCI format used for scheduling the PUSCH is also referred to as an uplink DCI format. The downlink grant is also referred to as a downlink assignment or a downlink allocation. The uplink DCI format includes at least one or both of DCI format 0_0 and DCI format 0_1.

DCI format 0_0 is composed of at least some or all of 1A to 1E.
1A) Identifier for DCI formats field
1B) Frequency domain resource assignment field
1C) Time Domain Resource Assignment Field
1D) Frequency hopping flag field
1E) MCS field (Modulation and Coding Scheme field)

The DCI format specific field may be used at least to indicate to which of one or more DCI formats the DCI format including the DCI format specific field corresponds. The one or more DCI formats may be based at least on some or all of DCI format 1_0, DCI format 1_1, DCI format 0_0, and/or DCI format 0_1.

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

The time domain resource allocation field may be used at least to indicate the allocation of time resources for a PUSH scheduled by a DCI format that includes the time domain resource allocation field.

The frequency hopping flag field may be used at least to indicate whether frequency hopping is applied to a PUSH scheduled by a DCI format that includes the frequency hopping flag field.

The MCS field may be used to indicate at least a part or all of a modulation scheme and/or a target coding rate for a PUSCH scheduled by a DCI format including the MCS field. The target coding rate may be a target coding rate for a transport block of the PUSCH. The size of the transport block (TBS: Transport Block Size) may be given based at least on the target coding rate.

DCI format 0_1 is configured to include at least some or all of 2A to 2I.
2A) DCI format specific field 2B) Frequency domain resource allocation field 2C) Time domain resource allocation field 2D) Frequency hopping flag field 2E) MCS field 2F) CSI request field
2G) BWP field
2H) First UL DAI field ( ^1st downlink assignment index)
2I) Second UL DAI field ( ^2nd downlink assignment index)

The first UL DAI field is used at least to indicate the transmission status of the PDSCH. If a dynamic HARQ-ACK codebook is used, the size of the first UL DAI field may be 2 bits.

The second UL DAI field is used at least to indicate the transmission status of the PDSCH. If a dynamic HARQ-ACK codebook including two sub-codebooks is used, the size of the second UL DAI field may be 2 bits.

The BWP field may be used to indicate the uplink BWP to which the PUSH scheduled by DCI format 0_1 is mapped.

The CSI request field is used at least to indicate a CSI report. The size of the CSI request field may be based at least on the higher layer parameter ReportTriggerSize.

The downlink DCI formats include at least one or both of DCI format 1_0 and DCI format 1_1.

DCI format 1_0 is configured to include at least some or all of 3A to 3M.
3A) Identifier for DCI formats field
3B) Frequency domain resource assignment field
3C) Time domain resource assignment field
3D) Frequency hopping flag field
3E) MCS field (Modulation and Coding Scheme field)
3F) First CSI request field
3G) PDSCH-to-HARQ feedback timing indicator field
3H) PUCCH resource indicator field
3I) First PDSCH Group Indicator field
3J) First New Feedback Indicator field
3K) First Requested PDSCH Group Indicator field
3L) First Downlink Assignment Index field
3M) First Other Group Downlink Assignment Index field

The timing indication field from the PDSCH to the HARQ feedback may be a field indicating timing K1. If the index of the slot including the last OFDM symbol of the PDSCH is slot n, the index of the slot including the PUCCH or PUSCH including at least HARQ-ACK information corresponding to the transport block included in the PDSCH may be n+K1. If the index of the slot including the last OFDM symbol of the PDSCH is slot n, the index of the slot including the first OFDM symbol of the PUCCH or the first OFDM symbol of the PUSCH including at least HARQ-ACK information corresponding to the transport block included in the PDSCH may be n+K1.

Hereinafter, the PDSCH-to-HARQ feedback timing indicator field (PDSCH-to-HARQ_feedback timing indicator field) may be referred to as the HARQ indication field.

The PUCCH resource indication field may be a field indicating the index of one or more PUCCH resources included in the PUCCH resource set.

Details of the first PGI field, the first NFI field, the first RPGI field, the first DAI field, and the first separate group DAI field are described below.

DCI format 1_1 is configured to include at least some or all of 4A to 4O.
4A) Identifier for DCI formats field
4B) Frequency domain resource assignment field
4C) Time domain resource assignment field
4D) Frequency hopping flag field
4E) MCS field (Modulation and Coding Scheme field)
4F) First CSI request field
4G) PDSCH-to-HARQ feedback timing indicator field
4H) PUCCH resource indicator field
4J) BWP field
4K) Second PGI field (second PDSCH Group Indicator field)
4L) Second New Feedback Indicator field
4M) Second Requested PDSCH Group Indicator field
4N) Second Downlink Assignment Index field
4O) First Other Group Downlink Assignment Index field

The BWP field may be used to indicate the downlink BWP to which the PDSCH scheduled by DCI format 1_1 is mapped.

Descriptions of the second PGI field, the second NFI field, the second RPGI field, the second DAI field, and the second separate group DAI field are provided below.

DCI format 2_0 may be configured to include at least one or more Slot Format Indicators (SFIs).

Each DCI format (DCI Format 1_0, DCI Format 1_1, DCI Format 0_0, and/or DCI Format 0_1DCI Format 1_1) may include fields other than those described above.

In various aspects of this embodiment, unless otherwise specified, the number of resource blocks refers to the number of resource blocks in the frequency domain.

The downlink grant is used at least for scheduling one PDSCH in one serving cell.

The uplink grant is used at least for scheduling one PUSH in one serving cell.

One physical channel may be mapped to one serving cell. One physical channel may be mapped to one BWP configured on one carrier included in one serving cell.

The terminal device 1 may be configured with one or more control resource sets (CORESET: COntrol REsource SET). The terminal device 1 monitors the PDCCH in one or more control resource sets. Here, monitoring the PDCCH in one or more control resource sets may include monitoring one or more PDCCHs corresponding to each of the one or more control resource sets. In addition, the PDCCH may include one or more PDCCH candidates and/or a set of PDCCH candidates. In addition, monitoring the PDCCH may include monitoring and detecting the PDCCH and/or a DCI format transmitted via the PDCCH.

The control resource set may indicate a time-frequency region to which one or more PDCCHs may be mapped. The control resource set may be a region in which the terminal device 1 monitors the PDCCHs. The control resource set may be composed of continuous resources (localized resources). The control resource set may be composed of non-contiguous resources (distributed resources).

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

The mapping of the control resource set to resource blocks may be based at least on higher layer parameters. The higher layer parameters may include a bitmap for a group of resource blocks (RBG). The group of resource blocks may be provided by six consecutive resource blocks.

The number of OFDM symbols constituting a control resource set may be given based at least on higher layer parameters.

A control resource set may be a common control resource set. The common control resource set may be a control resource set that is set in common for multiple terminal devices 1. The common control resource set may be given based on at least a part or all of the MIB, the first system information, the second system information, the common RRC signaling, and the cell ID. For example, the time resource and/or the frequency resource of the control resource set that is set to monitor the PDCCH used for scheduling the first system information may be given based on at least the MIB.

The control resource set configured in the MIB is also referred to as CORESET#0. CORESET#0 may be the control resource set with index #0.

A control resource set may be a dedicated control resource set. The dedicated control resource set may be a control resource set configured to be used exclusively for the terminal device 1. The dedicated control resource set may be provided based on at least dedicated RRC signaling and some or all of the value of the C-RNTI. Multiple control resource sets may be configured in the terminal device 1, and an index (control resource set index) may be assigned to each control resource set. One or more control channel elements (CCEs) may be configured in the control resource set, and an index (CCE index) may be assigned to each CCE.

The set of PDCCH candidates monitored by the terminal device 1 may be defined in terms of a search space. That is, the set of PDCCH candidates monitored by the terminal device 1 may be given by a search space.

The search space may be configured to include one or more PDCCH candidates of one or more aggregation levels. The aggregation level of the PDCCH candidate may indicate the number of CCEs that constitute the PDCCH. The PDCCH candidate may be mapped to one or more CCEs.

The terminal device 1 may monitor at least one or more search space sets in slots where DRX (Discontinuous reception) is not set. DRX may be provided based at least on higher layer parameters. The terminal device 1 may monitor at least one or more search space sets in slots where DRX is not set. Multiple search space sets may be configured in the terminal device 1. An index (search space set index) may be assigned to each search space set.

The search area set may be configured to include at least one or more search areas. Each search area may be assigned an index (search area index).

Each of the search space sets may be associated with at least one control resource set. Each of the search space sets may be included in one control resource set. For each of the search space sets, an index of the control resource set associated with the search space set may be given.

A monitoring periodicity for the search area set may be set for each search area set. The monitoring periodicity for the search area set may indicate at least the interval of slots during which the search area set is monitored by the terminal device 1. Upper layer parameters indicating at least the monitoring periodicity for the search area set may be provided for each search area set.

A monitoring offset for the search area set may be set for each search area set. The monitoring offset for the search area set may indicate at least an offset from a reference index (e.g., slot #0) of the index of the slot in which the search area set is monitored by the terminal device 1. A higher layer parameter indicating at least the monitoring offset for the search area set may be provided for each search area set.

For each search area set, a monitoring pattern for the search area set may be configured. The monitoring pattern for the search area set may indicate the first OFDM symbol for the search area set for which monitoring is performed. The monitoring pattern for the search area set may be given by a bitmap indicating the first OFDM symbol in one or more slots. Higher layer parameters indicating at least the monitoring pattern for the search area set may be given for each search area set.

A monitoring occasion for the search area set may be given based at least on some or all of the monitoring interval for the search area set, the monitoring offset for the search area set, the monitoring pattern for the search area set, and/or the DRX settings.

Figure 4 is a diagram showing an example of a monitoring opportunity for a search area set according to one aspect of this embodiment. In Figure 4, a search area set 91 and a search area set 92 are set in a primary cell 301, a search area set 93 is set in a secondary cell 302, and a search area set 94 is set in a secondary cell 303.

In Figure 4, the blocks indicated by grid lines represent search area set 91, the blocks indicated by diagonal lines going up to the right represent search area set 92, the blocks indicated by diagonal lines going up to the left represent search area set 93, and the blocks indicated by horizontal lines represent search area set 94.

The monitoring interval of the search area set 91 is set to 1 slot, the monitoring offset of the search area set 91 is set to 0 slots, and the monitoring pattern of the search area set 91 is set to [1, 0, 0, 0, 0, 0, 1, 0, 0, 0, 0, 0, 0]. That is, the monitoring opportunities for the search area set 91 are the first OFDM symbol (OFDM symbol #0) and the eighth OFDM symbol (OFDM symbol #7) in each slot.

The monitoring interval of the search area set 92 is set to 2 slots, the monitoring offset of the search area set 92 is set to 0 slots, and the monitoring pattern of the search area set 92 is set to [1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]. That is, the monitoring opportunity for the search area set 92 is the first OFDM symbol (OFDM symbol #0) in each of the even slots.

The monitoring interval of search area set 93 is set to 2 slots, the monitoring offset of search area set 93 is set to 0 slots, and the monitoring pattern of search area set 93 is set to [0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0]. That is, the monitoring opportunity for search area set 93 is the 8th OFDM symbol (OFDM symbol #7) in each of the even slots.

The monitoring interval of the search area set 94 is set to 2 slots, the monitoring offset of the search area set 94 is set to 1 slot, and the monitoring pattern of the search area set 94 is set to [1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]. That is, the monitoring opportunity for the search area set 94 is the first OFDM symbol (OFDM symbol #0) in each odd slot.

The physical resources of the search area are composed of control channel units (CCE: Control Channel Elements). A CCE is composed of a predetermined number of resource element groups (REG: Resource Element Groups). For example, a CCE may be composed of six REGs. A REG may be composed of one OFDM symbol of one PRB (Physical Resource Block). In other words, a REG may be composed of 12 resource elements (RE: Resource Elements). A PRB is also simply referred to as an RB (Resource Block).

The PDSCH is at least used to transmit a transport block. The PDSCH may be at least used to transmit a random access message 2 (random access response). The PDSCH may be at least used to transmit system information including parameters used for initial access.

In Fig. 1, the following downlink physical signals are used in downlink wireless communication: The downlink physical signals may not be used to transmit information output from higher layers, but are used by the physical layer.
・Synchronization signal (SS)
・DL DMRS (DownLink DeModulation Reference Signal)
・CSI-RS (Channel State Information-Reference Signal)
・DL PTRS (DownLink Phase Tracking Reference Signal)

The synchronization signal is used by the terminal device 1 to synchronize the frequency domain and/or time domain of the downlink. The synchronization signal includes a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS).

An SS block (SS/PBCH block) is composed of at least a PSS, an SSS, and some or all of the PBCH.

DL DMRS is related to the transmission of PBCH, PDCCH, and/or PDSCH. DL DMRS is multiplexed onto PBCH, PDCCH, and/or PDSCH. Terminal device 1 may use DL DMRS corresponding to the PBCH, PDCCH, or PDSCH to perform propagation path correction of the PBCH, PDCCH, or PDSCH.

The CSI-RS may be a signal used at least to calculate channel state information. The CSI-RS pattern assumed by the terminal device may be given at least by higher layer parameters.

The PTRS may be a signal used at least for phase noise compensation. The pattern of the PTRS assumed by the terminal device may be based at least on higher layer parameters and/or DCI.

The DL PTRS may be associated with a DL DMRS group that includes at least the antenna ports used for one or more DL DMRSs.

The downlink physical channels and downlink physical signals are also referred to as downlink signals. The uplink physical channels and uplink physical signals are also referred to as uplink signals. The downlink signals and uplink signals are collectively also referred to as physical signals. The downlink signals and uplink signals are collectively also referred to as signals. The downlink physical channels and uplink physical channels are collectively referred to as physical channels. The downlink physical signals and uplink physical signals are collectively referred to as physical signals.

BCH (Broadcast CHannel), UL-SCH (Uplink-Shared CHannel), and DL-SCH (Downlink-Shared CHannel) are transport channels. Channels used in the Medium Access Control (MAC) layer are called transport channels. The unit of transport channel used in the MAC layer is also called a transport block (TB) or MAC PDU. In the MAC layer, HARQ (Hybrid Automatic Repeat reQuest) control is performed for each transport block. A transport block is a unit of data that the MAC layer delivers to the physical layer. In the physical layer, transport blocks are mapped to code words, and modulation processing is performed for each code word.

The base station device 3 and the terminal device 1 exchange (transmit and receive) higher layer signals in the higher layer. For example, the base station device 3 and the terminal device 1 may transmit and receive RRC signaling (RRC message: Radio Resource Control message; RRC information: Radio Resource Control information) in the Radio Resource Control (RRC) layer. The base station device 3 and the terminal device 1 may also transmit and receive MAC CE (Control Element) in the MAC layer. Here, the RRC signaling and/or MAC CE are also referred to as higher layer signaling.

The PUSCH and the PDSCH may be used at least to transmit RRC signaling and/or MAC CE. Here, the RRC signaling transmitted from the base station device 3 on the PDSCH may be common signaling for multiple terminal devices 1 in the serving cell. The signaling common to multiple terminal devices 1 in the serving cell is also referred to as common RRC signaling. The RRC signaling transmitted from the base station device 3 on the PDSCH may be dedicated signaling (also referred to as dedicated signaling or UE specific signaling) for a certain terminal device 1. The signaling dedicated to the terminal device 1 is also referred to as dedicated RRC signaling. The upper layer parameters specific to the serving cell may be transmitted using common signaling for multiple terminal devices 1 in the serving cell or dedicated signaling for a certain terminal device 1. The UE-specific higher layer parameters may be transmitted using dedicated signaling for a certain terminal device 1.

BCCH (Broadcast Control CHannel), CCCH (Common Control CHannel), and DCCH (Dedicated Control CHannel) are logical channels. For example, BCCH is an upper layer channel used to transmit MIB. CCCH (Common Control CHannel) is an upper layer channel used to transmit information common to multiple terminal devices 1. Here, CCCH may be used, for example, for terminal devices 1 that are not RRC-connected. DCCH (Dedicated Control CHannel) is an upper layer channel that is used at least to transmit dedicated control information to terminal device 1. Here, DCCH may be used, for example, for terminal devices 1 that are RRC-connected.

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

The UL-SCH in the transport channel may be mapped to the PUSCH in the physical channel. The DL-SCH in the transport channel may be mapped to the PDSCH in the physical channel. The BCH in the transport channel may be mapped to the PBCH in the physical channel.

Below, we will explain an example configuration of a terminal device 1 related to one aspect of this embodiment.

Figure 5 is a schematic block diagram showing the configuration of a terminal device 1 according to one aspect of this embodiment. As shown in the figure, the terminal device 1 is configured to include a radio transmission/reception unit 10 and an upper layer processing unit 14. The radio transmission/reception unit 10 is configured to include at least an antenna unit 11, an RF (Radio Frequency) unit 12, and some or all of a baseband unit 13. The upper layer processing unit 14 is configured to include at least a medium access control layer processing unit 15, and some or all of a radio resource control layer processing unit 16. The radio transmission/reception unit 10 may be configured to include at least a transmission unit and some or all of a reception unit.

The upper layer processing unit 14 outputs uplink data (transport block) generated by user operation, etc., to the radio transceiver unit 10. The upper layer processing unit 14 processes the MAC layer, the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, and the RRC layer.

The media access control layer processing unit 15 provided in the upper layer processing unit 14 performs MAC layer processing.

The radio resource control layer processing unit 16 included in the upper layer processing unit 14 performs processing of the RRC layer. The radio resource control layer processing unit 16 manages various setting information/parameters of the device itself. The radio resource control layer processing unit 16 sets various setting information/parameters based on the upper layer signal received from the base station device 3. That is, the radio resource control layer processing unit 16 sets various setting information/parameters based on information indicating the various setting information/parameters received from the base station device 3. The setting information may include information related to processing or setting of the physical channel or physical signal (i.e., the physical layer), the MAC layer, the PDCP layer, the RLC layer, and the RRC layer. The parameters may be upper layer parameters.

The wireless transceiver unit 10 performs physical layer processing such as modulation, demodulation, encoding, and decoding. The wireless transceiver unit 10 separates, demodulates, and decodes the received physical signal, and outputs the decoded information to the upper layer processing unit 14. The wireless transceiver unit 10 generates a physical signal by modulating, encoding, and generating a baseband signal (converting to a time-continuous signal) on the data, and transmits the physical signal to the base station device 3.

The RF unit 12 converts the signal received via the antenna unit 11 into a baseband signal by quadrature demodulation (down-convert) and removes unnecessary frequency components. The RF unit 12 outputs the processed analog signal to the baseband unit.

The baseband unit 13 converts the analog signal input from the RF unit 12 into a digital signal. The baseband unit 13 removes the portion corresponding to the cyclic prefix (CP) from the converted digital signal, and performs a fast Fourier transform (FFT) on the signal from which the CP has been removed to extract a signal in the frequency domain.

The baseband unit 13 performs an Inverse Fast Fourier Transform (IFFT) on the data to generate an OFDM symbol, adds a CP to the generated OFDM symbol, generates a baseband digital signal, and converts the baseband digital signal into an analog signal. The baseband unit 13 outputs the converted analog signal to the RF unit 12.

The RF unit 12 uses a low-pass filter to remove unnecessary frequency components from the analog signal input from the baseband unit 13, up-converts the analog signal to a carrier frequency, and transmits it via the antenna unit 11. The RF unit 12 also amplifies the power. The RF unit 12 may also have a function of controlling the transmission power. The RF unit 12 is also referred to as a transmission power control unit.

Below, we will explain an example configuration of a base station device 3 related to one aspect of this embodiment.

Figure 6 is a schematic block diagram showing the configuration of a base station device 3 according to one aspect of this embodiment. As shown in the figure, the base station device 3 includes a radio transmission/reception unit 30 and an upper layer processing unit 34. The radio transmission/reception unit 30 includes an antenna unit 31, an RF unit 32, and a baseband unit 33. The upper layer processing unit 34 includes a medium access control layer processing unit 35 and a radio resource control layer processing unit 36. The radio transmission/reception unit 30 may be configured to include at least a transmitting unit and some or all of a receiving unit.

The upper layer processing unit 34 performs processing of the MAC layer, PDCP layer, RLC layer, and RRC layer.

The media access control layer processing unit 35 provided in the upper layer processing unit 34 performs MAC layer processing.

The radio resource control layer processing unit 36 included in the upper layer processing unit 34 performs processing of the RRC layer. The radio resource control layer processing unit 36 generates downlink data (transport block), system information, RRC messages, MAC CE, etc. to be placed in the PDSCH, or acquires them from the upper node, and outputs them to the radio transmission/reception unit 30. The radio resource control layer processing unit 36 also manages various setting information/parameters for each terminal device 1. The radio resource control layer processing unit 36 may set various setting information/parameters for each terminal device 1 via a signal of the upper layer. That is, the radio resource control layer processing unit 36 transmits/reports information indicating various setting information/parameters. The setting information may include information related to processing or setting of a physical channel or physical signal (i.e., the physical layer), the MAC layer, the PDCP layer, the RLC layer, and the RRC layer. The parameters may be upper layer parameters.

The functions of the wireless transceiver unit 30 are similar to those of the wireless transceiver unit 10, so their explanation will be omitted.

Each of the units numbered 10 to 16 in the terminal device 1 may be configured as a circuit. Each of the units numbered 30 to 36 in the base station device 3 may be configured as a circuit.

The terminal device 1 may perform carrier sense prior to the transmission of a physical signal. The base station device 3 may perform carrier sense prior to the transmission of a physical signal. Carrier sense may be energy detection in a radio channel. The possibility of transmitting the physical signal may be given based on the carrier sense performed prior to the transmission of the physical signal. For example, when the amount of energy detected by the carrier sense performed prior to the transmission of the physical signal is greater than a predetermined threshold, the transmission of the physical channel may not be performed, or it may be determined that the transmission is impossible. When the amount of energy detected by the carrier sense performed prior to the transmission of the physical signal is smaller than a predetermined threshold, the transmission of the physical channel may be performed, or it may be determined that the transmission is possible. When the amount of energy detected by the carrier sense performed prior to the transmission of the physical signal is equal to a predetermined threshold, the transmission of the physical channel may or may not be performed. In other words, when the amount of energy detected by the carrier sense performed prior to the transmission of the physical signal is equal to a predetermined threshold, it may be determined that the transmission is impossible, or it may be determined that the transmission is possible.

The procedure in which the possibility of transmitting a physical channel is given based on carrier sense is also called LBT (Listen Before Talk). A situation in which it is determined that transmission of a physical signal is impossible as a result of LBT is also called a busy state or busy. For example, the busy state may be a state in which the amount of energy detected by carrier sense is greater than a predetermined threshold. Also, a situation in which it is determined that transmission of a physical signal is possible as a result of LBT is also called an idle state or idle. For example, the idle state may be a state in which the amount of energy detected by carrier sense is less than a predetermined threshold.

In a certain component carrier, NR-U (New Radio - Unlicensed) may be applied. In a certain serving cell, NR-U may be applied. The application of NR-U in a certain component carrier (or a certain serving cell) may include at least a technique (framework, configuration) including some or all of the following elements A1 to A6.
Element A1: A second SS burst set is configured in the certain component carrier (or the certain serving cell). Element A2: The base station device 3 transmits a second SS/PBCH block in the certain component carrier (or the certain serving cell). Element A3: The terminal device 1 receives a second SS/PBCH block in the certain component carrier (or the certain serving cell). Element A4: The base station device 3 transmits a PDCCH in a second type-0 PDCCH common search space set in the certain component carrier (or the certain serving cell). Element A5: The terminal device 1 receives a PDCCH in a second type-0 PDCCH common search space set in the certain component carrier (or the certain serving cell). Element A6: An upper layer parameter related to the NR-U (e.g., a field included in the MIB) indicates a first value (e.g., 1).

In a certain component carrier, NR-U (New Radio - Unlicensed) may not be applied. In a certain serving cell, NR-U may not be applied. The fact that NR-U is not applied in a certain component carrier (or a certain serving cell) may include at least a technique (framework, configuration) including some or all of the following elements B1 to B6.
Element B1: A first SS burst set is configured in the certain component carrier (or the certain serving cell). Element B2: The base station device 3 transmits a first SS/PBCH block in the certain component carrier (or the certain serving cell). Element B3: The terminal device 1 receives a first SS/PBCH block in the certain component carrier (or the certain serving cell). Element B4: The base station device 3 transmits a PDCCH in a first type-0 PDCCH common search space set in the certain component carrier (or the certain serving cell). Element B5: The terminal device 1 receives a PDCCH in a first type-0 PDCCH common search space set in the certain component carrier (or the certain serving cell). Element B6: An upper layer parameter related to the NR-U (e.g., a field included in the MIB) indicates a value different from the first value (e.g., 0).

A certain component carrier may be configured in a licensed band. A certain serving cell may be configured in a licensed band. Here, the configuration of a certain component carrier (or a certain serving cell) in a licensed band may include at least a part or all of the following configurations 1 to 3.
Configuration 1: A higher layer parameter indicating that a certain component carrier (or a certain serving cell) operates in a licensed band is provided, or a higher layer parameter indicating that a certain component carrier (or a certain serving cell) operates in an unlicensed band is not provided. Configuration 2: A certain component carrier (or a certain serving cell) is configured to operate in a licensed band, or a certain component carrier (or a certain serving cell) is not configured to operate in an unlicensed band. Configuration 3: A certain component carrier (or a certain serving cell) is included in the licensed band, or a certain component carrier (or a certain serving cell) is not included in the unlicensed band.

A licensed band may be a band in which a radio station license is required for terminal devices that are expected to operate in the licensed band. A licensed band may be a band in which only terminal devices manufactured by operators (business entities, businesses, organizations, companies) that hold radio station licenses are permitted to operate. An unlicensed band may be a band in which no channel access procedure is required prior to the transmission of a physical signal.

An unlicensed band may be a band in which no radio station license is required for terminal devices that are (expected to) operate in the unlicensed band. An unlicensed band may be a band in which terminal devices manufactured by operators that hold radio station licenses and/or some or all of operators that do not hold radio station licenses are permitted to operate. An unlicensed band may be a band in which a channel access procedure is required prior to the transmission of a physical signal.

Whether NR-U is applied to a certain component carrier (or a certain serving cell) may be determined based at least on whether the certain component carrier (or the certain serving cell) is set to a band that can be operated in an unlicensed band (e.g., a band that can only be operated in an unlicensed band). For example, a list of bands designed for NR or NR carrier aggregation may be specified. For example, if a certain band is included in a band in which one or more bands in the list can be operated in an unlicensed band (e.g., a band that can only be operated in an unlicensed band), NR-U may be applied to the certain band. Also, if a certain band is not included in a band in which one or more bands in the list can be operated in an unlicensed band (e.g., a band that can only be operated in an unlicensed band), NR-U may not be applied to the certain band, and normal NR (e.g., NR of Release 15, or NR other than NR-U of Release 16) may be applied.

Whether NR-U is applied to a component carrier (or a serving cell) may be determined based at least on whether the component carrier (or the serving cell) is set to a band in which NR-U can operate (e.g., a band that can only be operated with NR-U). For example, if a list of bands for which NR or NR carrier aggregation is designed for operation is specified, and one or more bands in the list are specified as bands in which NR-U can operate (e.g., a band that can only be operated with NR-U), NR-U is applied if the band set for the component carrier (or the serving cell) is one of the one or more bands, and NR-U is not applied if it is a band other than the one or more bands, and normal NR (e.g., Release 15 NR, or NR other than Release 16 NR-U) may be applied.

Whether NR-U is applied to a certain component carrier (or a certain serving cell) may be determined based on information contained in system information (e.g., Master Information Block (MIB, or Physical Broadcast Channel (PBCH))). For example, if the MIB contains information indicating whether NR-U is applied, and the information indicates that NR-U is applied, NR-U may be applied to the serving cell corresponding to that MIB. On the other hand, if the information does not indicate that NR-U is applied, NR-U may not be applied to the serving cell corresponding to that MIB, and normal NR may be applied. Alternatively, the information may indicate whether operation is possible in an unlicensed band.

A certain component carrier may be set to an unlicensed band. A certain serving cell may be set to an unlicensed band. Here, the setting of a certain component carrier (or a certain serving cell) to an unlicensed band may include at least a part or all of the following settings 4 to 6.
Configuration 4: A higher layer parameter is provided to a certain component carrier (or a certain serving cell) indicating that it operates in an unlicensed band. Configuration 5: A certain component carrier (or a certain serving cell) is configured to operate in an unlicensed band. Configuration 6: A certain component carrier (or a certain serving cell) is included in the unlicensed band.

The following explanation will be given assuming that NR-U is applied to a component carrier or that NR-U is not applied. Note that "NR-U is applied to a component carrier" may mean "NR-U is applied to a serving cell", and "NR-U is not applied to a component carrier" may mean "NR-U is not applied to a serving cell".

For example, if NR-U is not applied to a certain component carrier, the terminal device 1 may receive a first SS/PBCH block. Also, if NR-U is not applied to a certain component carrier, the terminal device 1 may receive a first PDCCH in a first type-0 PDCCH common search space set. Also, if NR-U is not applied to a certain component carrier, the base station device 3 may transmit a first SS/PBCH block. Also, if NR-U is not applied to a certain component carrier, the base station device 3 may transmit a first PDCCH in a first type-0 PDCCH common search space set. The first SS/PBCH block may be received in any of the SS/PBCH block candidates included in the first SS burst set. The first SS/PBCH block may be transmitted in any of the SS/PBCH block candidates included in the first SS burst set.

The terminal device 1 may multiplex uplink control information (UCI) onto the PUCCH and transmit it. The terminal device 1 may multiplex UCI onto the PUSCH and transmit it. The UCI may include at least one of downlink channel state information (CSI), a scheduling request (SR) indicating a request for PUSCH resources, and hybrid automatic repeat request ACKnowledgement (HARQ-ACK) information for downlink data (Transport block, Medium Access Control Protocol Data Unit: MAC PDU, Downlink-Shared Channel: DL-SCH, Physical Downlink Shared Channel: PDSCH).

HARQ control for one transport block (TB) may be called a HARQ process. HARQ control can operate in parallel for multiple transport blocks (TBs). Each HARQ process may be associated with a HARQ process identifier.

The terminal device 1 may be associated with a PDSCH group identifier (PGI: PDSCH Group ID) for each PDSCH. The PGI of a certain PDSCH may be indicated at least based on the DCI format used for scheduling the PDSCH. For example, a field (PGI field) indicating the PGI may be included in the DCI format. For example, the PDSCH group may be a set of PDSCHs having the same PGI (PDSCH group identifier). The PDSCH group may be one PDSCH, or a set of one or more PDSCHs associated with the same PGI. The number of PDSCH groups configured for the terminal device 1 is N _group . N _group may be 1, 2, 3, 4, or any other integer equal to or greater than 0. The number of PDSCH groups that can be configured for the terminal device 1 is N _group,max . For example, for the terminal device 1, a number of PDSCH groups corresponding to an integer value equal to or less than N _group,max may be configured. It may be set based at least on N _group and/or RRC parameters.

The PGI field is a general term for the first PGI field and the second PGI field. The terminal device 1 may determine the PDSCH group to which a certain PDSCH is linked based at least on the value of the PGI field included in the DCI field used for scheduling the certain PDSCH.

For example, the second PGI field may be included in DCI format 1_1. For example, the number of bits of the second PGI field, N _PGI,second , may be 1 or 2. For example, the number of bits of the second PGI field, N _PGI,second , may be given by ceil(log2(N _group )). For example, the number of bits of the second PGI field, N _PGI,second , may be given by ceil(log2(N _group,max )). For example, the first PGI field may not be included in DCI format 1_0. For example, the first PGI field may be included in DCI format 1_0. For example, the number of bits of the first PGI field, N _PGI,first , may be 1 or 2. For example, the number of bits in the first PGI field, N _PGI,first , may be given by ceil(log2(N _group )). For example, the number of bits in the first PGI field, N _PGI,first , may be given by ceil(log2(N _{group ,max} )).

For example, for the terminal device 1, a DCI format 1_0 not including a first PGI field may be set, and a DCI format 1_1 including a second PGI field may be set. Here, the number of bits N _PGI,second of the second PGI field may be ceil(log2(N _group )). Here, the number of bits N _PGI,second of the second PGI field may be greater than ceil(log2(N _group )). Here, the number of bits N _PGI,second of the second PGI field may be ceil(log2(N _group,max )). Here, the PDSCH group of the PDSCH scheduled by the DCI format 1_0 may be linked to the PDSCH group with the smallest index (for example, the PDSCH group with index 0) among the PDSCH groups set in the terminal device 1. Here, the PDSCH group of the PDSCH scheduled by the DCI format 1_0 may be linked to the PDSCH group with the largest index (for example, the PDSCH group with index N _group -1) among the PDSCH groups set in the terminal device 1. Here, the PDSCH group of the PDSCH scheduled by the DCI format 1_0 may be linked to a predetermined PDSCH group (for example, a PDSCH group fixed in advance by a description in a specification or the like). Here, the PDSCH group of the PDSCH scheduled by the DCI format 1_0 may not be linked to any of the N _group PDSCH groups. Here, the PDSCH group of the PDSCH scheduled by the DCI format 1_1 may be linked to a PDSCH group identified at least based on the value of the second PGI field.

For example, for the terminal device 1, a DCI format 1_0 including a first PGI field may be set, and a DCI format 1_1 including a second PGI field may be set. Here, the number of bits N _PGI,first of the first PGI field may be ceil(log2(N _group )). Here, the number of bits N _PGI,first of the first PGI field may be greater than ceil(log2(N _group )). Here, the number of bits N _PGI,first of the first PGI field may be ceil(log2(N _{group ,max} )). Here, the number of bits N _PGI,second of the second PGI field may be ceil(log2(N _group )). Here, the number of bits N _PGI,second of the second PGI field may be greater than ceil(log2(N _group )). Here, the number of bits N _PGI,second of the second PGI field may be ceil(log2(N _group,max )). Here, the PDSCH group of the PDSCH scheduled by the DCI format 1_0 may be linked to a PDSCH group identified based at least on the value of the first PGI field. Here, the PDSCH group of the PDSCH scheduled by the DCI format 1_1 may be linked to a PDSCH group identified based at least on the value of the second PGI field.

The Requested PDSCH Group (RPG) may be a PDSCH group corresponding to the HARQ-ACK information to be transmitted (reported) via the next PUCCH or PUSCH. The RPG (Requested PDSCH Group) may include one PDSCH group or multiple PDSCH groups. The indication of the RPG may be indicated in the form of a bitmap corresponding to each PDSCH group based at least on the DCI format. The RPG may be indicated at least on the basis of the RPGI field included in the DCI format. The terminal device 1 may generate a HARQ-ACK codebook for the indicated RPG and transmit (report) it via the PUCCH or PUSCH.

The RPGI field is a general term for the first RPGI field and the second RPGI field. The terminal device 1 may determine the request PDSCH group based at least on the value of the RPGI field.

For example, the second RPGI field may be included in DCI format 1_1. For example, the first RPGI field may not be included in DCI format 1_0. For example, the first RPGI field may be included in DCI format 1_0. For example, the number of bits of the second RPGI field, NRPG _,second , may be equal to _Ngroup . For example, the number of bits of the second RPGI field, NRPG _,second , may be equal to Ngroup _,max .

For example, a DCI format 1_0 not including a first RPGI field may be set for the terminal device 1, and a DCI format 1_1 including a second RPGI field may be set. Here, the number of bits of the second RPGI field may be equal to N _group . Here, the number of bits of the second RPGI field may be equal to N _group,max . Here, detection of the DCI format 1_0 may trigger transmission of one or more HARQ-ACK information corresponding to one or more transport blocks included in one or more PDSCHs linked to the PDSCH group with the smallest index (for example, the PDSCH group with index 0). Here, detection of the DCI format 1_0 may trigger transmission of one or more HARQ-ACK information corresponding to one or more transport blocks included in one or more PDSCHs linked to the PDSCH group with the largest index (for example, the PDSCH group with index N _group -1). Here, the detection of the DCI format 1_0 may trigger the transmission of one or more HARQ-ACK information corresponding to one or more transport blocks included in one or more PDSCHs linked to a predetermined PDSCH _group (for example, a PDSCH group fixed in advance by a description in a specification or the like). Here, the detection of the DCI format 1_0 may trigger the transmission of one or more HARQ-ACK information corresponding to one or more transport blocks included in one or more PDSCHs not linked to any of the N group PDSCH groups. Here, the detection of the DCI format 1_1 may trigger the transmission of one or more HARQ-ACK information corresponding to one or more transport blocks included in one or more PDSCHs corresponding to one or more PDSCH groups indicated at least based on the second RPGI field.

For example, a DCI format 1_0 including a first RPGI field may be set for the terminal device 1, and a DCI format 1_1 including a second RPGI field may be set. Here, the number of bits of the first RPGI field may be equal to N _group . Here, the number of bits of the first RPGI field may be equal to N _group,max . Here, the number of bits of the second RPGI field may be equal to N _group . Here, the number of bits of the second RPGI field may be equal to N _group,max . Here, detection of the DCI format 1_0 may trigger transmission of one or more HARQ-ACK information corresponding to one or more transport blocks included in one or more PDSCHs corresponding to one or more PDSCH groups indicated at least based on the first RPGI field. Here, detection of the DCI format 1_1 may trigger transmission of one or more HARQ-ACK information corresponding to one or more transport blocks included in one or more PDSCHs corresponding to one or more PDSCH groups indicated based at least on the second RPGI field.

The NFI (New Feedback Indicator) field may be a DCI field indicating whether HARQ-ACK information including HARQ-ACK bits corresponding to a transport block of a PDSCH is correctly detected. The NFI field may be a field indicating whether to erase (flush) the HARQ-ACK bits stored in a recording medium such as a memory.

The NFI field is a collective term for the first NFI field and the second NFI field.

For example, a DCI format 1_0 not including a first NFI field may be set for the terminal device 1, and a DCI format 1_1 including a second NFI field may be set. Here, the number of bits N _NFI,second of the second NFI field may be equal to N _group . Here, the number of bits N NFI _,second of the second NFI field may be equal to N _group,max . Here, it may be assumed that the NFI of the PDSCH group with the smallest index (for example, the PDSCH group with index 0) has been toggled upon detection of the DCI format 1_0. Here, it may be assumed that the NFI of the PDSCH group with the largest index (for example, the PDSCH group with index N _group -1) has been toggled upon detection of the DCI format 1_0. Here, it may be assumed that the NFI of a predetermined PDSCH group (for example, a PDSCH group fixed in advance by a description in a specification or the like) has been toggled by the detection of the DCI format 1_0. Here, it may be assumed that the NFI of N _group PDSCH groups has been toggled by the detection of the DCI format 1_0. Here, it may not be assumed that the NFI of N _group PDSCH groups has been toggled by the detection of the DCI format 1_0. Here, it may be triggered by the detection of the DCI format 1_1 to transmit one or more HARQ-ACK information corresponding to one or more transport blocks included in one or more PDSCHs corresponding to one or more PDSCH groups indicated at least based on the second NFI field. Here, each bit of the second NFI field included in the DCI format 1_1 may correspond to one PDSCH group.

For example, for the terminal device 1, a DCI format 1_0 including a first NFI field may be set, and a DCI format 1_1 including a second NFI field may be set. Here, the number of bits N _NFI,first of the first NFI field may be 1. Here, the number of bits N _NFI,second of the second NFI field may be equal to N _group . Here, the number of bits N NFI _,second of the second NFI field may be equal to N _group,max . Here, the first NFI field included in the DCI format 1_0 may correspond to a PDSCH group with the smallest index (for example, a PDSCH group with index 0). Here, the first NFI field included in the DCI format 1_0 may correspond to a PDSCH group with the largest index (for example, a PDSCH group with index N _group -1). Here, the first NFI field included in the DCI format 1_0 may correspond to a predetermined PDSCH group (for example, a PDSCH group fixed in advance by a description in a specification or the like). Here, the first NFI field included in the DCI format 1_0 may correspond to a PDSCH group to which a PDSCH scheduled by the DCI format 1_0 is linked. Here, each bit of the second NFI field included in the DCI format 1_1 may correspond to one PDSCH group.

For example, for the terminal device 1, a DCI format 1_0 including a first NFI field may be set, and a DCI format 1_1 including a second NFI field may be set. Here, the number of bits N _NFI,first of the first NFI field may be equal to N _group . Here, the number of bits N _NFI,first of the first NFI field may be equal to N _group,max . Here, the number of bits N _NFI,second of the second NFI field may be equal to N _group . Here, the number of bits N _NFI,second of the second NFI field may be equal to N _group,max . Here, each bit of the first NFI field included in the DCI format 1_0 may correspond to one PDSCH group. Here, each bit of the second NFI field included in the DCI format 1_1 may correspond to one PDSCH group.

For example, after a HARQ-ACK bit corresponding to a transport block included in a PDSCH scheduled by a DCI format is transmitted, the terminal device 1 may store the value of the NFI bit corresponding to each PDSCH group indicated by the DCI format. For example, when the terminal device 1 receives a DCI format, the terminal device 1 may store the value of the NFI bit corresponding to each PDSCH group indicated by the DCI format. Here, the received NFI bit may be referred to as an NFI bit indicated by an NFI field included in a DCI format used for scheduling the PDSCH for the PDSCH for the PDSCH. The stored NFI bit may be referred to as an NFI bit already stored in the terminal device 1 before the DCI format used for scheduling the PDSCH for the PDSCH is detected for the PDSCH. For each PDSCH group, the initial value of the value of the stored NFI bit may be set to 0 in advance. The terminal device 1 may compare the value of the received NFI bit with the value of the stored NFI bit to determine whether the NFI bit corresponding to the PDSCH group is toggled. The terminal device 1 may determine that the NFI bit is toggled when the values of the received NFI bit and the stored NFI bit are different. The terminal device 1 may determine that the base station device 3 has detected HARQ-ACK information corresponding to the PDSCH group in which the NFI bit (i.e., the received NFI bit) is toggled, compared to the value of the previously received NFI bit (i.e., the stored NFI bit) for the PDSCH group. For example, when the base station device 3 detects HARQ-ACK information corresponding to the PDSCH group, it may toggle the NFI bit corresponding to the PDSCH group. When the values of the received NFI bit and the stored NFI bit are equal, it may determine that the NFI bit is not toggled. The terminal device 1 may determine that the base station device 3 has not detected HARQ-ACK information corresponding to the PDSCH group in which the NFI bit (i.e., the received NFI bit) is not toggled, compared to the value of the previously received NFI bit (i.e., the stored NFI bit) for the PDSCH group. For example, if the base station device 3 does not detect HARQ-ACK information corresponding to a PDSCH group, the base station device 3 may not toggle the NFI bit corresponding to the PDSCH group. Here, toggling means switching to a different value.

The received NFI may be configured with one or more received NFI bits. Each entry of the received NFI may be a received NFI bit corresponding to each PDSCH group. The stored NFI may be configured with one or more stored NFI bits. Each entry of the stored NFI may be a stored NFI bit corresponding to each PDSCH group.

When the terminal device 1 generates a HARQ-ACK codebook corresponding to a certain PDSCH group, if the NFI bit is toggled compared to the value of the previously received NFI bit (i.e., the saved NFI bit) for the PDSCH group, the terminal device 1 may delete (or not include) already reported HARQ-ACK information (HARQ-ACK information other than HARQ-ACK information that has not yet been reported) from the HARQ-ACK codebook corresponding to the PDSCH group. If there is a PDSCH that has been detected in the PDSCH group and for which HARQ-ACK information has not yet been reported, the terminal device 1 may not delete (or may include) the HARQ-ACK information corresponding to the PDSCH. That is, the terminal device 1 may multiplex the HARQ-ACK information corresponding to the PDSCH into the aforementioned HARQ-ACK codebook. The terminal device 1 may flush already reported HARQ-ACK information for one or more HARQ-ACK information corresponding to a PDSCH group for which the NFI bit is toggled, and may not flush unreported HARQ-ACK information. Here, flushing means returning the HARQ-ACK information to an initial value (e.g., NACK). When the terminal device 1 receives a toggled NFI and then transmits a HARQ-ACK codebook corresponding to the PDSCH group for the NFI bit, the terminal device 1 generates and transmits a HARQ-ACK codebook using unflushed HARQ-ACK information (unreported HARQ-ACK information). When the terminal device 1 receives a non-toggled NFI and then transmits a HARQ-ACK codebook corresponding to the PDSCH group for that NFI bit, it generates and transmits a HARQ-ACK codebook using non-flushed HARQ-ACK information (reported HARQ-ACK information and non-reported HARQ-ACK information).

The terminal device 1 may determine a HARQ-ACK codebook based at least on whether the NFI bit is toggled. The terminal device 1 may determine a HARQ-ACK codebook corresponding to a certain PDSCH group based at least on whether the stored NFI bit and the received NFI bit corresponding to the certain PDSCH group are toggled.

The value of K1 (information or parameter indicated by the timing indication field from PDSCH to HARQ feedback) indicated by the DCI format included in the PDCCH may be numerical or non-numerical. Here, the numerical value means a value expressed by a number, and may be a value among {0, 1, 2, ... . . , 15}. The non-numerical value may mean a value other than a number, or may mean not indicating a number. The operation of the numerical value of K1 and the non-numerical value of K1 will be described below. For example, the PDSCH scheduled by the DCI format is transmitted from the base station device 3 in slot n and received by the terminal device 1. When the value of K1 indicated by the DCI format is a numerical value, the terminal device 1 may transmit (report) HARQ-ACK information corresponding to the PDSCH via PUCCH or PUSCH in slot n+K1. When the value of K1 indicated by the DCI format is a non-numeric value, the terminal device 1 may postpone the reporting of HARQ-ACK information corresponding to the PDSCH. When a non-numeric value of K1 is indicated by a DCI format including scheduling information of the PDSCH, the terminal device 1 may postpone the reporting of HARQ-ACK information corresponding to the PDSCH. For example, the terminal device 1 may store the HARQ-ACK information in a recording medium such as a memory, and not transmit (report) the HARQ-ACK information via the next PUCCH or PUSCH, and may transmit (report) the HARQ-ACK information by triggering the transmission of the HARQ-ACK information based at least on a DCI format other than the above-mentioned DCI format.

The non-numeric value of K1 may be included in the first series of higher layer parameters. The first higher layer parameter may be the higher layer parameter dl-DataToUL-ACK. The first higher layer parameter may be a higher layer parameter different from the higher layer parameter dl-DataToUL-ACK. The value of K1 may be a value indicated by a PDSCH to HARQ feedback timing indication field included in DCI format 1_0 or DCI format 1_1 in the first series of higher layer parameters. For example, assuming that the first higher layer parameter sequence is set to {0, 1, 2, 3, 4, 5, 15, non-numeric value} and the number of bits of the PDSCH to HARQ feedback timing indication field is 3, then the codepoint "000" in the PDSCH to HARQ feedback timing indication field may indicate that the value of K1 is 0, the codepoint "001" may indicate that the value of K1 is 1, and the codepoint "111" may indicate that the value of K1 is a non-numeric value. For example, assuming that the first higher layer parameter sequence is set to {non-numeric value, 0, 1, 2, 3, 4, 5, 15} and the number of bits of the PDSCH to HARQ feedback timing indication field is 3, then the codepoint "000" in the PDSCH to HARQ feedback timing indication field may indicate that the value of K1 is a non-numeric value, the codepoint "001" may indicate that the value of K1 is 0, and the codepoint "111" may indicate that the value of K1 is 15.

For example, the PDSCH to HARQ feedback timing indication field included in DCI format 1_0 may not indicate a non-numeric value. For example, a code point of the PDSCH to HARQ feedback timing indication field included in DCI format 1_0 may indicate a non-numeric value. For example, the PDSCH to HARQ feedback timing indication field included in DCI format 1_1 may not indicate a non-numeric value. For example, a code point of the PDSCH to HARQ feedback timing indication field included in DCI format 1_1 may indicate a non-numeric value.

Figure 7 is a diagram showing an example of the correspondence between the monitoring occasion for search space set and the monitoring occasion for PDCCH according to one aspect of the present embodiment. In Figure 7, the monitoring occasion for the search space set in the primary cell is the first OFDM symbol of the slot, and the monitoring occasion for the search space set in the secondary cell is the first OFDM symbol of the slot and the middle OFDM symbol of the slot (e.g., OFDM symbol #7). In Figure 7, the monitoring occasion for the PDCCH corresponds to the first OFDM symbol of slot #n and the middle OFDM symbol of slot #n, and the first OFDM symbol of slot #n+1 and the middle OFDM symbol of slot #n+1. In other words, the monitoring occasion for the PDCCH may be defined as an occasion in which the monitoring occasion for the search space set is set in at least one of one or more serving cells. Furthermore, the monitoring opportunity for the PDCCH may correspond to an index of an OFDM symbol in which a monitoring opportunity for a search space set is set in at least one of one or more serving cells.

In a slot, a monitoring opportunity for a search space set starting from a certain OFDM symbol index may correspond to a monitoring opportunity for a PDCCH starting from the certain OFDM symbol index. A monitoring opportunity for a PDCCH starting from a certain OFDM symbol index may correspond to each of the monitoring opportunities for a search space set starting from a certain OFDM symbol index.

The terminal device 1 may determine a set of PDCCH monitoring opportunities for HARQ-ACK information transmitted in a PUCCH arranged in a slot of index n (slot#n) based on at least a part or all of the value of the timing K1 and the value of the slot offset K0. The set of PDCCH monitoring opportunities for HARQ-ACK information transmitted in a PUCCH arranged in a slot of index n is also referred to as a set of PDCCH monitoring opportunities for slot n (monitoring occasion for PDCCH for slot#n). Here, the set of PDCCH monitoring opportunities includes M PDCCH monitoring opportunities. For example, the slot offset K0 may be indicated based at least on the value of a time domain resource allocation field included in a downlink DCI format. The slot offset K0 is a value indicating the number of slots (slot difference) from a slot including the last OFDM symbol in which a PDCCH including a DCI format including a time domain resource allocation field indicating the slot offset K0 is arranged to the first OFDM symbol of a PDSCH scheduled by the DCI format.

Figure 8 is a diagram showing an example of the configuration of a set of monitoring opportunities of the PDCCH for slot n according to one aspect of the present embodiment. In Figure 8, the monitoring opportunity of the search space set in the primary cell is the first OFDM symbol of the slot, and the monitoring opportunity of the search space set in the secondary cell is the first OFDM symbol of the slot and the middle OFDM symbol of the slot (e.g., OFDM symbol #7). In Figure 8, the monitoring opportunity of the search space set in the primary cell is configured to include 801 and 804, and the monitoring opportunity of the search space set in the secondary cell is configured to include 802, 803, 805, and 806. In Figure 8, DCI format 811 is detected in 802, DCI format 812 is detected in 804, DCI format 813 is detected in 805, and DCI format 814 is detected in 806.

For example, when it is indicated that HARQ-ACK information is transmitted in slot n based at least on the timing K1 and slot offset K0 indicated by DCI format 811, the terminal device 1 may determine the PDCCH monitoring opportunity defined at least on the basis of 801 as the PDCCH monitoring opportunity for slot n. For example, when it is not indicated that HARQ-ACK information is transmitted in slot n based at least on the timing K1 and slot offset K0 indicated by DCI format 812, and it is not indicated that HARQ-ACK information is transmitted in slot n based at least on the timing K1 and slot offset K0 indicated by DCI format 813, the terminal device 1 may not determine the PDCCH monitoring opportunity defined at least on some or all of 804 and 805 as the PDCCH monitoring opportunity for slot n. For example, if it is indicated that HARQ-ACK information is transmitted in slot n based at least on the timing K1 and slot offset K0 indicated by DCI format 814, terminal device 1 may determine that a PDCCH monitoring opportunity defined based at least on 806 is the PDCCH monitoring opportunity for slot n.

That is, if a DCI format detected in a monitoring opportunity of any search space set corresponding to a monitoring opportunity of a certain PDCCH triggers transmission of HARQ-ACK information in slot n, the terminal device 1 may determine the monitoring opportunity of the PDCCH as a PDCCH monitoring opportunity for slot n. Also, if a DCI format detected in a monitoring opportunity of a search space set corresponding to a monitoring opportunity of a certain PDCCH does not trigger transmission of HARQ-ACK information in slot n, the terminal device 1 may not determine the monitoring opportunity of the PDCCH as a PDCCH monitoring opportunity for slot n. Also, if a DCI format is not detected in a monitoring opportunity of a search space set corresponding to a monitoring opportunity of a certain PDCCH, the terminal device 1 may not determine the monitoring opportunity of the PDCCH as a PDCCH monitoring opportunity for slot n.

The PUCCH resource used for transmitting the HARQ-ACK information in slot n may be identified based at least on a PUCCH resource indication field included in the last DCI format among one or more DCI formats detected in a set of PDCCH monitoring opportunities for the slot n. Here, each of the one or more DCI formats triggers the transmission of the HARQ-ACK information in slot n. The last DCI format may be a DCI format corresponding to the last index (largest index) among the DCI formats detected in the set of PDCCH monitoring opportunities for the slot n. The indices of the DCI formats in the set of PDCCH monitoring opportunities for the slot n are given in ascending order with respect to the index of the serving cell in which the DCI format is detected, and then in ascending order with respect to the index of the PDCCH monitoring opportunity in which the DCI format is detected. The indices of the PDCCH monitoring opportunities are given in ascending order on the time axis.

The second upper layer parameter may include an upper layer parameter related to generation and reporting of HARQ-ACK information. A first value of the second upper layer parameter may correspond to a conventional specification in which NR-U is not applied. A second value of the second upper layer parameter may correspond to a specification in which NR-U is applied. The upper layer parameter pdsch-HARQ-ACK-Codebook may be an upper layer parameter indicating a type of HARQ-ACK codebook. The upper layer parameter pdsch-HARQ-ACK-Codebook may be set to any of the values semi-static and dynamic. The upper layer parameter pdsch-HARQ-ACK-Codebook may be set to a value enhancedDynamic-r16. The value of enhancedDynamic-r16 in the upper layer parameter pdsch-HARQ-ACK-Codebook may correspond to the application of NR-U. When NR-U is applied, the terminal device 1 may be configured with some or all of the following settings. Here, the setting of the upper layer parameters related to the HARQ-ACK codebook when NR-U is applied may be referred to as NR-U HARQ-ACK setting.
Setting 1: The second higher layer parameter is set to a second value. Setting 2: The second higher layer parameter is set to a second value. Setting 3: The higher layer parameter pdsch-HARQ-ACK-Codebook is set to enhancedDynamic-r16.

When the upper layer parameter pdsch-HARQ-ACK-Codebook is set to a value of semi-static, the size of the HARQ-ACK codebook may be determined semi-statically in advance based on at least the upper layer parameter when generating the HARQ-ACK codebook. That is, the size of the HARQ-ACK codebook may not depend on the detection state of the actual DCI format. When the upper layer parameter pdsch-HARQ-ACK-Codebook is set to a value of dynamic, the size of the HARQ-ACK codebook may be determined dynamically based on at least the counter DAI and/or the total DAI indicated by the detected DCI format when generating the HARQ-ACK codebook. If the higher layer parameter pdsch-HARQ-ACK-Codebook is set to the value of semi-static or dynamic, the terminal device 1 may not expect more than one PDSCH group. If the higher layer parameter pdsch-HARQ-ACK-Codebook is set to the value of enhancedDynamic-r16, a HARQ-ACK codebook or sub-codebook may be generated for each PDSCH group. If the higher layer parameter pdsch-HARQ-ACK-Codebook is set to the value of enhancedDynamic-r16, the terminal device 1 may not expect one or more PDSCH groups.

When the NR-U HARQ-ACK configuration is given, the terminal device 1 may include, for the PDSCH group g linked to the scheduled PDSCH, a PDCCH monitoring opportunity corresponding to a DCI format that at least satisfies condition A1, condition A2, and part or all of condition A3 in the set of PDCCH monitoring opportunities for slot n. The base station device 3 may expect that the HARQ-ACK information that triggered the transmission for the PDSCH group g corresponds to a PDCCH monitoring opportunity after the time when the NFI bit corresponding to the PDSCH group g was last toggled. By determining the set of PDCCH monitoring opportunities in the terminal device 1 based at least on the toggle state of the NFI bit indicated by the base station device 3, ambiguity in the recognition of the reception/transmission state of the HARQ-ACK information between the terminal device 1 and the base station device 3 can be avoided, and efficient transmission and reception of HARQ-ACK information can be realized.
Condition A1: HARQ-ACK information corresponding to a PDSCH scheduled by the DCI format is triggered when it is transmitted via PUCCH in slot n. Condition A2: PDSCH group g is indicated by the PGI field included in the DCI format. Condition A3: The DCI format is detected after the last occurrence of an event in which the NFI bit corresponding to the PDSCH group g is toggled. Here, an event in which the NFI bit is toggled indicates an event in which the received NFI is toggling compared to the stored NFI.

Figure 9 is a diagram showing an example of the configuration of a set of PDCCH monitoring opportunities for slot n according to one aspect of the present embodiment. Figure 10 is a diagram showing an example of the configuration of a set of PDCCH monitoring opportunities for slot n according to one aspect of the present embodiment.

9 and 10, the shaded blocks indicate PDCCH, the white blocks indicate PDSCH, and the vertically lined blocks indicate PUCCH. An arrow pointing from each PDSCH to one of the PUCCHs indicates that the initial transmission of the HARQ-ACK bit corresponding to the transport block included in the PDSCH corresponding to the start point of the arrow is performed in the PUCCH corresponding to the end point of the arrow. Here, a solid arrow indicates that the transmission of the PUCCH is triggered by the DCI format used for scheduling the PDSCH (timing K1 is a numerical value), and a dotted arrow indicates that the transmission of the PUCCH is not triggered by the DCI format used for scheduling the PDSCH (timing K1 is a non-numerical value). In FIG. 9, the absence of an arrow pointing from the PDSCH to the PUCCH does not necessarily mean that the transmission (initial transmission, etc.) of the HARQ-ACK bit corresponding to the transport block included in the PDSCH is not triggered.

In Figures 9 and 10, it is assumed that terminal device 1 is given NR-U HARQ-ACK configuration.

In FIG. 9, the DCI format used for scheduling PDSCH 911 is included in PDCCH 901, the DCI format used for scheduling PDSCH 912 is included in PDCCH 902, the DCI format used for scheduling PDSCH 913 is included in PDCCH 903, the DCI format used for scheduling PDSCH 914 is included in PDCCH 904, and the DCI format used for scheduling PDSCH 915 is included in PDCCH 905.

In FIG. 9, it is assumed that all PDSCHs are linked to PDSCH group g. The terminal device 1 transmits HARQ-ACK information 931 including HARQ-ACK bits corresponding to transport blocks included in PDSCH 915 and PDSCH 914 via PUCCH 921 in slot n. The terminal device 1 may detect PDCCH 901 and store the received NFI. When the terminal device 1 detects PDCCH 902, the received NFI is indicated by the DCI format included in PDCCH 902. The terminal device 1 may determine that the NFI bit is toggled by comparing the received NFI (which has a value of 1) with the stored NFI (which has a value of 0). After the determination, the terminal device 1 may store the received NFI as the stored NFI. When the terminal device 1 detects PDCCH 903, the received NFI is indicated by the DCI format included in PDCCH 903. The terminal device 1 may determine that the NFI bit is toggled by comparing the received NFI (value is 0) with the stored NFI (value is 1). After the determination, the terminal device 1 may store the received NFI as the stored NFI. When the terminal device 1 detects the PDCCH 904, the received NFI is indicated by a DCI format included in the PDCCH 904. The terminal device 1 may determine that the NFI bit is toggled by comparing the received NFI (value is 1) with the stored NFI (value is 0). After the determination, the terminal device 1 may store the received NFI as the stored NFI. When the terminal device 1 detects the PDCCH 905, the received NFI is indicated by a DCI format included in the PDCCH 905. The terminal device 1 may determine that the NFI bit is not toggled by comparing the received NFI (value is 1) with the stored NFI (value is 1). After the determination, the terminal device 1 may store the received NFI as a saved NFI. The event in which the NFI bit is toggled at the time when the PDCCH 904 is detected is the last NFI bit toggle event until the PUCCH 921 is transmitted. The terminal device 1 may include, for the generation of the HARQ-ACK information 931, a PDCCH monitoring opportunity corresponding to the DCI format from the last NFI bit toggle event to the detection of the last DCI format in a set of PDCCH monitoring opportunities for slot n. For example, the terminal device 1 may include a PDCCH monitoring opportunity corresponding to the PDCCH 904 and the PDCCH 905 in a set of PDCCH monitoring opportunities for slot n. The NFI bit toggle event is an event in which it is determined that the NFI bit is toggled. The NFI bit toggle event is triggered by the NFI bit included in the DCI format. If the NFI bit included in the DCI format (the received NFI) toggles compared to the stored NFI, an NFI bit toggle event is triggered.

That is, when the NR-U HARQ-ACK configuration is given, the terminal device 1 may determine a set of PDCCH monitoring opportunities for slot n based at least on determining (identifying, identifying, recognizing, judging) the last NFI bit toggle event for the PDSCH group g associated with the scheduled PDSCH. For example, the terminal device 1 may include a PDCCH monitoring opportunity after the timing at which the last NFI bit toggle event occurs for the PDSCH group g in the set of PDCCH monitoring opportunities for slot n. For example, the terminal device 1 may include a PDCCH monitoring opportunity at the timing at which the last NFI bit toggle event occurs for the PDSCH group g in the set of PDCCH monitoring opportunities for slot n. For example, the terminal device 1 may not include a PDCCH monitoring opportunity before the timing at which the last NFI bit toggle event occurs for the PDSCH group g in the set of PDCCH monitoring opportunities for slot n.

Also, for example, the terminal device 1 may include, for the PDSCH group g, a PDCCH monitoring opportunity after the PDCCH monitoring opportunity at which the DCI format related to the last NFI bit toggle event is detected in the set of PDCCH monitoring opportunities for slot n. For example, the terminal device 1 may include, for the PDSCH group g, a PDCCH monitoring opportunity at which the DCI format related to the last NFI bit toggle event is detected in the set of PDCCH monitoring opportunities for slot n. For example, the terminal device 1 may not include, for the PDSCH group g, a PDCCH monitoring opportunity before the PDCCH monitoring opportunity at which the DCI format related to the last NFI bit toggle event is detected in the set of PDCCH monitoring opportunities for slot n. Here, the DCI format related to the last NFI bit toggle event is a DCI format that triggers the occurrence of the last NFI bit toggle event.

When the NR-U HARQ-ACK configuration is given, the terminal device 1 may store the HARQ-ACK reporting state for the reception of the PDSCH. The initial value of the HARQ-ACK reporting state may be set in advance to not applicable (N/A), null, or undefined. After receiving the PDSCH, the terminal device 1 may set the HARQ-ACK reporting state corresponding to the reception of the PDSCH to not reported. The terminal device 1 may set the HARQ-ACK reporting state to reported when a transmission is triggered on an uplink physical channel in which a HARQ-ACK bit corresponding to the reception of the PDSCH is present. For a PDSCH reception in which the HARQ-ACK reporting state is already reported, the terminal device 1 may delete (or set to the initial value) the HARQ-ACK reporting state when detecting that the NFI bit corresponding to the PDSCH group associated with the PDSCH has been toggled compared to the previously received NFI bit. When the terminal device 1 detects that the NFI bit corresponding to the PDSCH group associated with the PDSCH for which the HARQ-ACK report status is unreported has been toggled compared to the previously received NFI bit, the terminal device 1 may not delete (or set to an initial value) the HARQ-ACK report status. That is, the terminal device 1 may keep the HARQ-ACK report status unreported. For the PDSCH group g associated with the scheduled PDSCH, the terminal device 1 may include a PDCCH monitoring opportunity corresponding to a DCI format that satisfies part or all of the conditions A1, A2, and B1 in the set of PDCCH monitoring opportunities for slot n. For the PDSCH group g, the base station device 3 may expect that the HARQ-ACK information that triggered the transmission corresponds to a PDCCH monitoring opportunity for which the NFI corresponding to the PDSCH group g is not toggled (the HARQ-ACK report status is the initial value in the terminal device 1). By determining the set of PDCCH monitoring opportunities in the terminal device 1 based at least on the toggle state of the NFI bit instructed by the base station device 3, ambiguity in the understanding of the reception/transmission state of HARQ-ACK information between the terminal device 1 and the base station device 3 can be avoided, thereby enabling efficient transmission and reception of HARQ-ACK information.
Condition B1: The HARQ-ACK reporting status corresponding to the reception of the PDSCH scheduled by the DCI format is unreported or already reported.

The terminal device 1 does not have to include a PDCCH monitoring opportunity corresponding to a DCI format that does not satisfy at least any of condition A1, condition A2, or condition B1 for a PDSCH group g linked to the scheduled PDSCH in the set of PDCCH monitoring opportunities for slot n.

In FIG. 9, when PDCCH 901 is detected, the terminal device 1 may set the HARQ-ACK report status corresponding to PDSCH 911 to not reported. After transmitting HARQ-ACK information corresponding to PDSCH 911, the terminal device 1 may set the HARQ-ACK report status corresponding to PDSCH 911 to reported. When PDCCH 902 is detected, the terminal device 1 may set the HARQ-ACK report status corresponding to PDSCH 911 to an initial value because the NFI bit is toggled. When PDCCH 902 is detected, the terminal device 1 may set the HARQ-ACK report status corresponding to PDSCH 912 to not reported. When PDCCH 903 is detected, the terminal device 1 may set the HARQ-ACK report status corresponding to PDSCH 912 to an initial value because the NFI bit is toggled. When the PDCCH 903 is detected, the terminal device 1 may set the HARQ-ACK report state corresponding to the PDSCH 913 to not reported. When the PDCCH 904 is detected, the terminal device 1 may set the HARQ-ACK report state corresponding to the PDSCH 913 to an initial value by toggling the NFI bit. When the PDCCH 904 is detected, the terminal device 1 may set the HARQ-ACK report state corresponding to the PDSCH 914 to not reported. When the PDCCH 905 is detected, the terminal device 1 may hold the HARQ-ACK report state corresponding to the PDSCH 914 as already reported by not toggling the NFI bit. When the PDCCH 905 is detected, the terminal device 1 may set the HARQ-ACK report state corresponding to the PDSCH 915 to not reported. Before the PUCCH 921 is transmitted, the HARQ-ACK reporting states corresponding to the PDSCH 911, the PDSCH 912, and the PDSCH 913 are initial values, the HARQ-ACK reporting state corresponding to the PDSCH 914 has been reported, and the HARQ-ACK reporting state corresponding to the PDSCH 915 has not been reported. The terminal device 1 may include a PDCCH monitoring opportunity corresponding to a PDSCH whose HARQ-ACK reporting state is not reported or has been reported in a set of PDCCH monitoring opportunities for slot n when generating the HARQ-ACK information 931. For example, the terminal device 1 may include a PDCCH monitoring opportunity corresponding to the PDSCH 914 and the PDSCH 915 in a set of PDCCH monitoring opportunities for slot n. For example, the terminal device 1 may not include PDCCH monitoring opportunities corresponding to PDSCH 911, PDSCH 912, and PDSCH 913 in the set of PDCCH monitoring opportunities for slot n.

Figure 11 is a diagram showing an example of counter DAI and total DAI indication in one embodiment of this invention.

The Counter DAI indicates, for a PDCCH monitoring opportunity in a serving cell, the cumulative number of PDCCHs (or a value at least related to the cumulative number) detected up to a PDCCH monitoring opportunity in the serving cell in M PDCCH monitoring opportunities (a set of PDCCH monitoring opportunities for slot n). The Counter DAI may also be referred to as C-DAI. The Total DAI may indicate, for M PDCCH monitoring opportunities, the cumulative number of PDCCHs (or a value at least related to the cumulative number) detected up to a PDCCH monitoring opportunity in the serving cell. The Total DAI may also be referred to as T-DAI.

The DAI field is a general term for the first DAI field and the second DAI field. The separate group DAI field is a general term for the first separate group DAI field and the second separate group DAI field. The separate group DAI field used to generate a HARQ-ACK codebook for a certain PDSCH may be included in a DCI format used for scheduling a PDSCH group different from the PDSCH group linked to the PDSCH. For example, the separate group DAI field may be a separate group DAI field included in the DCI format.

For example, if one serving cell is configured and the upper layer parameter pdsch-HARQ-ACK-Codebook is set to a value of dynamic, the number of bits of the second DAI field may be 2, and the second DAI field may indicate a counter DAI. That is, the two bits of the second DAI field may be a counter DAI. If more than one serving cell is configured and the upper layer parameter pdsch-HARQ-ACK-Codebook is set to a value of dynamic, the number of bits of the second DAI field may be 4, and the two most important bits (MSBs) of the second DAI field may indicate a counter DAI, and the two least significant bits (LSBs) of the second DAI field may indicate a total DAI. That is, the two MSBs of the second DAI field may be a counter DAI. That is, the 2 LSBs of the second DAI field may be the total DAI.

The total DAI used to generate a HARQ-ACK codebook for a certain PDSCH may be indicated by some or all of the bits of a second DAI field included in a DCI format used for scheduling a PDSCH group different from the PDSCH group linked to the PDSCH. For example, the total DAI may be indicated by one MSB, two MSBs, or three MSBs of the second DAI field. For example, the total DAI may be indicated by one LSB, two LSBs, or three LSBs of the second DAI field.

The following describes the indication of the counter DAI and the total DAI. In FIG. 11, the arrows pointing from the DAI field (DAI field) and the other group DAI field (OG-DAI field) to either the counter DAI (C-DAI) or the total DAI (T-DAI) indicate that the counter DAI or the total DAI is indicated by the DAI field or the other group DAI field. The number of bits in the other group DAI field may be 1 (i.e., may be set to 1). The number of bits in the other group DAI field may be 2 (i.e., may be set to 2). The number of bits in the other group DAI field may be 3 (i.e., may be set to 3). The number of bits in the other group DAI field may be the number of bits used to indicate the counter DAI (i.e., may be set to the number of bits used to indicate the counter DAI). The number of bits in the other group DAI field may be given by an upper layer parameter.

In FIG. 11, the counter DAI may be indicated by the first DAI field or the second DAI field. The total DAI may be indicated by the other group DAI field. If the number of bits of the second DAI field is 2, the counter DAI may be indicated by the second DAI field. If the number of bits of the second DAI field is 4, the counter DAI may be indicated by the 2 most important bits (MSBs) of the second DAI field. If the number of bits of the second DAI field is 4, the total DAI may be indicated by the 2 least significant bits (LSBs) of the second DAI field. For example, if one serving cell is configured and NR-U HARQ-ACK configuration is not given, the counter DAI may be indicated by the first DAI field or the second DAI field. For example, if one serving cell is configured and NR-U HARQ-ACK configuration is not given, the total DAI may not be indicated. For example, if one serving cell is configured and NR-U HARQ-ACK configuration is given and multiple PDSCH groups are scheduled, the total DAI may be indicated by the separate group DAI field.

In FIG. 10 and FIG. 11, the indication of the total DAI by the different group DAI field in the retransmission of the HARQ-ACK codebook for PDSCH 1011 via PUCCH 1022 will be described. Here, PDSCH 1011 scheduled by PDCCH 1001 is linked to PDSCH group g, and PDSCH 1012 scheduled by PDCCH 1002 and PDSCH 1013 scheduled by PDCCH 1003 are linked to PDSCH group h different from PDSCH group g. The following describes the generation of HARQ-ACK information for PDSCH group g. The terminal device 1 receives PDCCH 1001 including a DCI format for scheduling PDSCH 1011, and transmits HARQ-ACK information 1031 including a HARQ-ACK bit corresponding to PDSCH 1011 via PUCCH 1021. Here, it is assumed that the PUCCH 1021 is not detected in the base station device 3, and the HARQ-ACK information 1031 is retransmitted via the PUCCH 1022. The separate group DAI field for the PDSCH 1011 linked to the PDSCH group g may be included in the DCI format included in the PDCCH 1002 and/or the PDCCH 1003 linked to the PDSCH group h. The counter DAI used to generate the HARQ-ACK codebook for the PDSCH 1011 may be indicated by the DAI field included in the PDCCH 1001. The total DAI used to generate the HARQ-ACK codebook for the PDSCH 1011 may be indicated by the DAI field included in the PDCCH 1001. The total DAI used to generate the HARQ-ACK codebook for the PDSCH 1011 may be indicated by the separate group DAI field.

Figures 12, 13, and 14 are diagrams showing an example of a procedure for configuring a HARQ-ACK codebook (a codebook for HARQ-ACK information) according to one aspect of this embodiment. <AX> in Figures 12, 13, and 14 is also referred to as step AX. In Figures 12, 13, and 14, "A=B" may mean that A is set to B. In Figures 12, 13, and 14, "A=B" may mean that B is input to A. The terminal device 1 generates a HARQ-ACK codebook based on the procedures described in Figures 12, 13, and 14. When an NR-U HARQ-ACK setting is given, the terminal device 1 generates a HARQ-ACK codebook for each PDSCH group based on the procedures described in Figures 12, 13, and 14, and when multiple HARQ-ACK codebooks are generated, the multiple HARQ-ACK codebooks may be concatenated.

The HARQ-ACK codebook may be provided based on at least some or all of steps A1 to A58.

The HARQ-ACK codebook corresponding to a certain PDSCH group may be provided based on at least some or all of steps A1 to A46. The HARQ-ACK codebook corresponding to a certain PDSCH group may be provided based on one or more HARQ-ACK bits corresponding to one or more transport blocks included in one or more PDSCHs included in the certain PDSCH group.

The HARQ-ACK codebook may be based on at least some or all of the set of PDCCH monitoring opportunities, the value of the UL DAI field, and/or the DAI field and/or the separate group DAI field.

The HARQ-ACK codebook may be based at least on some or all of the set of PDCCH monitoring opportunities, the UL DAI, the counter DAI, and/or the total DAI.

In step A1, a serving cell index c is set to 0. The serving cell index may be given for each serving cell based at least on higher layer parameters.

In step A2, m is set to 0. m may indicate the index of a monitoring opportunity for a PDCCH including DCI format 1_0 or DCI format 1_1.

In step A3, j may be set to 0.

In step A4, V _temp may be set to 0.

In step A5, V _temp2 may be set to 0.

In step A6, V _s may be set to φ, where φ denotes the empty set.

In step A7, N ^DL _cells may be set to the number of serving cells, which may be the number of serving cells configured in the terminal device 1.

In step A8, M may be set to the number of monitoring opportunities for the PDCCH.

In step A9, a first evaluation formula m<M is evaluated. If the first evaluation formula is true, step A10 may be executed. If the first evaluation formula is false, step A34 may be executed.

In step A10, c may be set to 0.

In step A11, a second evaluation formula c<N ^DL _cells is evaluated. If the second evaluation formula is true, step A11 may be executed. If the second evaluation formula is false, step A33 may be executed.

In step A12, if the PDCCH monitoring opportunity m in the serving cell c is before the switching of the activated downlink BWP, step A13 may be executed. In step A12, if there is a switching of the activated uplink BWP in the PCell and the switching of the activated downlink BWP is not triggered by DCI format 1_1, step A13 may be executed. If both of the above two conditions are not met, step A14 may be executed.

In step A13, c may be set to c+1.

In step A14, step A15 may be executed.

If the NR-U HARQ-ACK configuration is not given in step A15 and condition C1 or condition C2 is satisfied, step A16 may be executed. If the NR-U HARQ-ACK configuration is given in step A15 and condition C3 or condition C4 is satisfied, step A16 may be executed.
Condition C1: There is a PDSCH associated with a PDCCH at a PDCCH monitoring opportunity m in a serving cell c. Condition C2: There is a PDCCH indicating the release of an SPS PDSCH in a serving cell c. Condition C3: There is a PDSCH associated with a PDCCH associated with a PDCCH at a PDCCH monitoring opportunity m in a serving cell c. Condition C4: There is a PDCCH indicating the release of an SPS PDSCH in a serving cell c and associated with a PDSCH group g.

In step A16, a third evaluation equation V ^DL _C-DAI,c,m ≦V _temp is evaluated. If the third evaluation equation is true, step A17 may be executed. If the third evaluation equation is false, step A18 may be executed.

V ^DL _C-DAI,c,m is a value of a counter DAI (Downlink Assignment Index) given based at least on a PDCCH detected at a PDCCH monitoring occasion m in a serving cell c. In determining the counter DAI, the indexes of the PDCCHs detected at M monitoring occasions may be given the serving cell index c first and the PDCCH monitoring occasion m second. That is, the indexes of the PDCCHs detected at M PDCCH monitoring occasions may be first mapped in the order of the serving cell index c, and then mapped in the order of the PDCCH monitoring occasion m (serving cell index first, PDCCH monitoring occasion second mapping). The counter DAI may be referred to as a C-DAI (Counter Downlink Assignment Index).

In step A17, j may be set to j+1.

Step A18 may be a step indicating completion of the operation based on the third evaluation formula in step A12.

In step A19, V _temp may be set to V ^DL _C-DAI,c,m .

In step A20, a fourth evaluation equation V ^DL _T-DAI,m =φ may be evaluated. If the fourth evaluation equation is true, step A21 may be executed. If the fourth evaluation equation is false, step A22 may be executed.

V ^DL _T-DAI,m may be a value of a total DAI based at least on PDCCHs detected at PDCCH monitoring opportunity m in serving cell c. The total DAI may indicate a cumulative number (or a value at least related to the cumulative number) of PDCCHs detected up to PDCCH monitoring opportunity m in M PDCCH monitoring opportunities. The total DAI may be referred to as a Total Downlink Assignment Index (T-DAI).

The HARQ-ACK codebook may be multiplexed onto a PUSCH scheduled based at least on DCI format 0_1, and V ^DL _T-DAI,m may be replaced with V ^UL _DAI , at least when m=M−1.

In step A21, V _temp2 may be set to V ^DL _C-DAI,c,m .

In step A22, step A23 may be executed.

In step A23, V _temp2 may be set to V ^DL _T-DAI,m .

Step A24 may be a step indicating completion of the operation based on the fourth evaluation formula in step A20.

In step A25, step A26 may be executed if 1) harq-ACK-SpatialBundlingPUCCH is not provided, and 2) the PDCCH monitoring opportunity m is a PDCCH monitoring opportunity including DCI format 1_0 or DCI format 1_1, and 3) maxNrofCodeWordsScheduledByDCI is set in at least one BWP in at least one serving cell for reception of two transport blocks. maxNrofCodeWordsScheduledByDCI may be information indicating whether or not transmission of two transport blocks in PDSCH is supported.

In step A26, o ^ACK _a (8j+2(V ^DL _C-DAI,c,m −1)) may be set to the value of a HARQ-ACK bit corresponding to a first transport block of serving cell c. A HARQ-ACK bit value of 1 may indicate an ACK. A HARQ-ACK bit value of 0 may indicate a NACK. The first transport block of the serving cell c may be the first transport block included in a PDSCH scheduled by a DCI format included in a PDCCH detected at a PDCCH monitoring opportunity m in the serving cell c. o ^ACK _a (X) is o ^{∼ ACK} _X.

In step A27, o ^ACK _a (8j+2(V ^DL _C-DAI,c,m −1)+1) may be set to a value of a HARQ-ACK bit corresponding to a second transport block of the serving cell c. The second transport block of the serving cell c may be the second transport block included in a PDSCH scheduled by a DCI format included in a PDCCH detected at a PDCCH monitoring opportunity m in the serving cell c.

The PDSCH including a first transport block and the PDSCH not including a second transport block may mean that the PDSCH includes one transport block.

In step A28, _Vs may be set to _Vs ∪ {8j+2( ^VDLC _-DAI,c,m -1),8j+2( ^VDLC _-DAI,c,m -1)+1}. Y ∪ Z may denote the union of set Y and set Z. {*} may be a set that includes *.

In step A29, step A30 may be executed if 1) a harq-ACK-SpatialBundlingPUCCH is provided, and 2) the PDCCH monitoring opportunity m is a PDCCH monitoring opportunity including DCI format 1_1, and 3) maxNrofCodeWordsScheduledByDCI is configured in at least one BWP in at least one serving cell for reception of two transport blocks.

In step A30, o ^ACK _a (4j+V ^DL _C-DAI,c,m −1) may be set to a value given by a binary AND operation of a first HARQ-ACK bit corresponding to a first transport block of the serving cell c and a second HARQ-ACK bit corresponding to a second transport block of the serving cell c.

In step A31, V _s may be set to V _s ∪ {4j+V ^DL _C−DAI,c,m −1}.

If, in step A32, the conditions of step A25 and the conditions of step A29 are not satisfied, step A33 may be executed.

In step A33, o ^ACK _a (4j+V ^DL _C-DAI,c,m −1) may be set to the value of the first HARQ-ACK bit corresponding to the first transport block of the serving cell c. In step A33, o ^ACK _a (4j+V ^DL _C-DAI,c,m −1) may be set to the value of the HARQ-ACK bit of the serving cell c.

In step A34, V _s may be set to V _s ∪ {4j+V ^DL _C−DAI,c,m −1}.

Step A35 may be a step indicating completion of the operation of step A25.

Step A36 may be a step indicating completion of the operation of step A15.

In step A37, c may be set to c+1.

Step A38 may be a step indicating completion of the operation of step A12.

In step A39, step A11 may be executed.

In step A40, m may be set to m+1.

In step A41, step A10 may be executed.

In step A42, a fifth evaluation equation V _temp2 <V _temp may be executed. If the fifth evaluation equation is true, step A43 may be executed. If the fifth evaluation equation is false, step A44 may be executed.

In step A43, j may be set to j+1.

Step A44 may be a step indicating completion of step A42.

In step A45, if 1) harq-ACK-SpatialBundlingPUCCH is not provided, and 2) maxNrofCodeWordsScheduledByDCI is set in at least one BWP in at least one serving cell, step A46 may be executed. If both of the above two conditions are not met, step A47 may be executed.

In step A46, O ^ACK may be set to 2(4j+V _temp2 ).

In step A47, step A48 may be executed.

In step A48, ^O_ACK may be set to 4j+ _Vtemp2 .

Step A49 may be a step indicating completion of the operation of step A12.

In step A50, for i _N ∈{0,1,...,O ^ACK -1} _\ V _s is satisfied, o ^ACK _a (i _N ) may be set to the value of NACK. V\W may denote the set obtained by subtracting the elements included in set W from set V. V\W may be the difference set of V with respect to W.

In step A51, c may be set to 0.

In step A52, a seventh evaluation formula c<N ^DL _cells is evaluated. If the seventh evaluation formula is true, step A54 may be executed. If the second evaluation formula is false, step A58 may be executed.

In step A54, step A54 may be executed if a PDSCH (SPS PDSCH) scheduled by a grant configured in one or more slots in monitoring opportunities of M PDCCHs is configured to be received and transmission of the SPS PDSCH is activated.

In step A54, O ^ACK may be set to O ^ACK +1. In step A54, O ^ACK may be set to O ^ACK +N _SPS , where N _SPS may be the number of SPS PDSCHs that are configured to be received in the M PDCCH monitoring occasions 1001.

In step A55, o ^ACK (O ^ACK -1) may be set to a value of a HARQ-ACK bit corresponding to a transport block included in the SPS PDSCH. In step A55, o ^ACK (O ^ACK -i _SPS ) may be set to a value of a HARQ-ACK bit corresponding to a transport block included in the SPS PDSCH. i _SPS may satisfy the condition that i _SPS ∈{0, 1, ..., N _SPS -1}. In step A55, o ^ACK (O ^ACK -1) may be set to a value given by a logical AND of HARQ-ACK bits corresponding to transport blocks included in one or more SPS PDSCHs that are set to be received in the monitoring occasions of M PDCCHs.

Step A56 may be a step indicating completion of the operation of step A53.

In step A57, c may be set to c+1.

Step A58 may be a step indicating completion of the operation of step A52.

The first to seventh evaluation formulas are also referred to as evaluation formulas. An evaluation formula being true may mean that the evaluation formula is satisfied. An evaluation formula being false may mean that the evaluation formula is not true. An evaluation formula being false may mean that the evaluation formula is not satisfied.

O ^ACK is the size of the HARQ-ACK codebook (e.g., the number of bits included in the HARQ-ACK codebook). O ^ACK may correspond to each PDSCH group. O _ACK is the number of bits of UCI corresponding to HARQ-ACK information multiplexed into PUCCH or PUSCH. O _ACK may be given by O ^ACK .

The PUCCH transmission opportunity (PUCCH transmission occasion) may be a transmission opportunity for attempting to transmit a PUCCH that reports HARQ-ACK information for a PDSCH. The PUCCH transmission opportunity (PUCCH transmission occasion) may be a transmission opportunity for the terminal device 1 to attempt to transmit a PUCCH used to report HARQ-ACK information for a PDSCH. The PUCCH transmission opportunity for the PDSCH may be indicated based at least on the timing K1 indicated by the DCI format that schedules the PDSCH. The terminal device 1 may transmit a PUCCH in a PUCCH transmission opportunity depending on the result of the LBT. The terminal device 1 may transmit a PUCCH in a PUCCH transmission opportunity when it is determined to be in an idle state as a result of the LBT. The terminal device 1 may not transmit a PUCCH in a PUCCH transmission opportunity depending on the result of the LBT. If the terminal device 1 determines that the PUCCH transmission opportunity is in a busy state as a result of the LBT, the terminal device 1 does not need to transmit the PUCCH.

The PUCCH transmission opportunity may correspond to one PUCCH resource. The one PUCCH resource may be a PUCCH resource indicated by a DCI format that schedules a PDSCH. Here, a slot in which the PUCCH transmission opportunity is arranged may be indicated based at least on the timing K1 indicated by the DCI format. When the one PUCCH resource collides with a PUSCH in the time domain, a HARQ-ACK corresponding to the PDSCH may be transmitted on the PUSCH. Even when the one PUCCH resource collides with a PUSCH in the time domain, the PUCCH transmission opportunity corresponding to the one PUCCH resource may be valid.

Figure 15 shows an example of generating HARQ-ACK information.

In FIG. 15 and FIG. 16, the shaded blocks indicate PDCCH, the white blocks indicate PDSCH, and the vertically lined blocks indicate PUCCH or PUCCH transmission occasions. The arrows pointing from each of the PDSCHs to either the PUCCH or the PUCCH transmission occasions indicate that the initial transmission of the HARQ-ACK bits corresponding to the transport block included in the PDSCH corresponding to the start point of the arrow is performed in the PUCCH or PUCCH transmission occasion corresponding to the end point of the arrow. Here, the solid arrow indicates that the transmission of the PUCCH or the PUCCH transmission at the PUCCH transmission opportunity is triggered by the DCI format used for scheduling the PDSCH (timing K1 is a numerical value). In FIG. 15, it is assumed that the terminal device 1 is given the NR-U HARQ-ACK setting.

15 and 16, a PUCCH transmission opportunity may be defined as a PUCCH transmission opportunity set in a slot indicated by a PDSCH-to-HARQ feedback timing indicator field included in one or more DCI formats detected in a set of PDCCH monitoring opportunities corresponding to the PUCCH transmission opportunity. That is, a PUCCH transmission opportunity in slot n may be provided by one or more DCI formats detected in a set of PDCCH monitoring opportunities for slot n.

15, the slot in which PUCCH 1522 is placed may be indicated by a PDSCH-to-HARQ feedback timing indicator field included in each of PDCCH 1501 and PDCCH 1502. Also, the slot in which PUCCH 1523 is placed may be indicated by a PDSCH-to-HARQ feedback timing indicator field included in each of PDCCH 1503 and PDCCH 1504.

In FIG. 15, it is assumed that PDSCH1511 to PDSCH1514 are linked to PDSCH group g (i.e., the same PDSCH group). After PUCCH transmission opportunity 1521, terminal device 1 receives PDCCH1501 and receives PDSCH1511 scheduled by the DCI format included in PDCCH1501. Here, it is assumed that HARQ-ACK information reported via PUCCH transmission opportunity 1521 is correctly detected in base station device 3, and NFI bit (NFI bit corresponding to PDSCH group g) is toggled in base station device 3, and counter DAI (counter DAI corresponding to PDSCH group g) and/or total DAI (total DAI corresponding to PDSCH group g) are reset. Terminal device 1 receives PDCCH1502 and receives PDSCH1512 scheduled by the DCI format included in PDCCH1502. Here, the DCI format included in the PDCCH 1501 indicates 0 as the NFI bit and 1 as the counter DAI. Here, the DCI format included in the PDCCH 1502 indicates 0 as the NFI bit and 2 as the counter DAI. The terminal device 1 attempts to report (transmit) the PUCCH via the PUCCH transmission opportunity 1522 in order to report HARQ-ACK information for the PDSCH 1511 and the PDSCH 1512. Furthermore, after the PUCCH transmission opportunity 1522, the terminal device 1 receives the PDCCH 1503 and receives the PDSCH 1513 scheduled by the DCI format included in the PDCCH 1503. The terminal device 1 receives the PDCCH 1504 and receives the PDSCH 1514 scheduled by the DCI format included in the PDCCH 1504. For example, if the DCI format included in PDCCH1503 indicates 0 as the NFI bit and 3 as the counter DAI, and the DCI format included in PDCCH1504 indicates 0 as the NFI bit and 4 as the counter DAI, the terminal device 1 may assume, based on the NFI bit, that the HARQ-ACK information for PDSCH1511 and PDSCH1512 is not correctly detected (decoded) in the base station device 3. That is, in such a case, the base station device 3 may continue to accumulate the values of the counter DAI and/or the total DAI without toggling the NFI bit corresponding to the PDSCH group g indicated by the DCI formats included in each of PDCCH1501 to PDCCH1504. Also, in such a case, the terminal device 1 may report (transmit) HARQ-ACK information for PDSCH 1511, PDSCH 1512, PDSCH 1513, and PDSCH 1514 via a PUCCH transmission opportunity 1523. The base station device 3 receives the HARQ-ACK information via a PUCCH transmission opportunity 1521 and toggles the NFI bit. The base station device 3 transmits a PDCCH 1501 used for scheduling the PDSCH 1511, and indicates an NFI of 0 and a counter DAI of 1 according to the DCI format included in the PDCCH 1501. The base station device 3 transmits a PDCCH 1502 used for scheduling the PDSCH 1512, and indicates an NFI of 0 and a counter DAI of 2 according to the DCI format included in the PDCCH 1502. Base station device 3 transmits PDCCH 1503 used for scheduling PDSCH 1513, and indicates an NFI of 0 and a counter DAI of 3 according to the DCI format included in PDCCH 1503. Base station device 3 transmits PDCCH 1504 used for scheduling PDSCH 1514, and indicates an NFI of 0 and a counter DAI of 4 according to the DCI format included in PDCCH 1504.

In FIG. 15, the terminal device 1 generates an X-bit first HARQ-ACK codebook according to the procedures shown in FIG. 12, FIG. 13, and FIG. 14 based at least on the counter DAI corresponding to PDSCH 1511, the counter DAI corresponding to PDSCH 1512, and/or the total DAI corresponding to PDSCH 1512, and attempts to report (transmit) the codebook via the PUCCH transmission opportunity 1522. The size (length, number of bits) of the first HARQ-ACK codebook may be determined based at least on the total DAI corresponding to PDSCH 1512. Here, for example, the number of bits X of the first HARQ-ACK codebook may be 2. The terminal device 1 may generate a second HARQ-ACK codebook by the procedure shown in FIG. 12, FIG. 13, and FIG. 14 based at least on the counter DAI corresponding to PDSCH 1511, the counter DAI corresponding to PDSCH 1512, the counter DAI corresponding to PDSCH 1513, the counter DAI corresponding to PDSCH 1514, and/or the total DAI corresponding to PDSCH 1514. The size (length, number of bits) of the second HARQ-ACK codebook may be determined based at least on the total DAI corresponding to PDSCH 1514. Here, for example, the number of bits of the second HARQ-ACK codebook may be 4. The terminal device 1 may delete X bits from the beginning of the second HARQ-ACK codebook. For example, 2 bits may be deleted from the beginning of the 4-bit second HARQ-ACK codebook. The terminal device 1 may report (transmit) HARQ-ACK information including at least the first HARQ-ACK codebook and the second HARQ-ACK codebook from which the first X bits have been deleted, via the PUCCH transmission opportunity 1523. For example, 4-bit HARQ-ACK information including the 2-bit first HARQ-ACK codebook and the 2-bit second HARQ-ACK codebook may be reported (transmitted) via the PUCCH transmission opportunity 1523. The base station device 3 may receive the above-mentioned 4-bit HARQ-ACK information via the PUCCH transmission opportunity 1523.

In FIG. 15, the terminal device 1 generates an X-bit first HARQ-ACK codebook according to the procedures shown in FIG. 12, FIG. 13, and FIG. 14 based at least on the counter DAI corresponding to PDSCH 1511, the counter DAI corresponding to PDSCH 1512, and/or the total DAI corresponding to PDSCH 1512, and attempts to report (transmit) the codebook via the PUCCH transmission opportunity 1522. The size (length, number of bits) of the first HARQ-ACK codebook may be determined based at least on the total DAI corresponding to PDSCH 1512. Here, for example, the number of bits X of the first HARQ-ACK codebook may be 2. The terminal device 1 may generate a second HARQ-ACK codebook by the procedures shown in Figures 12, 13, and 14 based on at least the counter DAI corresponding to PDSCH 1511, the counter DAI corresponding to PDSCH 1512, the counter DAI corresponding to PDSCH 1513, the counter DAI corresponding to PDSCH 1514, and/or the total DAI corresponding to PDSCH 1514. The size (length, number of bits) of the second HARQ-ACK codebook may be determined based at least on the total DAI corresponding to PDSCH 1514. Here, for example, the number of bits of the second HARQ-ACK codebook may be 4. The terminal device 1 may add the X+1th bit and subsequent bits of the second HARQ-ACK codebook to the first HARQ-ACK codebook, and report (transmit) the generated HARQ-ACK information via the PUCCH transmission opportunity 1523. For example, the third bit (the third MSB) and the fourth bit (the fourth MSB) of the second HARQ-ACK codebook may be added to the 2-bit first HARQ-ACK codebook, and a total of 4 bits of HARQ-ACK information may be reported (transmitted) via the PUCCH transmission opportunity 1523. The base station device 3 may receive the above-mentioned 4-bit HARQ-ACK information via the PUCCH transmission opportunity 1523.

15, the terminal device 1 generates an X-bit first HARQ-ACK codebook according to the procedures shown in FIG. 12, FIG. 13, and FIG. 14 based at least on the counter DAI corresponding to PDSCH 1511, the counter DAI corresponding to PDSCH 1512, and/or the total DAI corresponding to PDSCH 1512, and attempts to report (transmit) the codebook via a PUCCH transmission opportunity 1522. The size (length, number of bits) of the first HARQ-ACK codebook may be determined based at least on the total DAI corresponding to PDSCH 1512. Here, for example, the number of bits X of the first HARQ-ACK codebook may be 2. The terminal device 1 may generate a second HARQ-ACK codebook by the procedures shown in Figures 12, 13, and 14 based on at least a counter DAI corresponding to PDSCH 1511, a counter DAI corresponding to PDSCH 1512, a counter DAI corresponding to PDSCH 1513, a counter DAI corresponding to PDSCH 1514, and/or a counter DAI corresponding to PDSCH 1514. The size (length, number of bits) of the second HARQ-ACK codebook may be determined based at least on the total DAI corresponding to PDSCH 1514. Here, for example, the number of bits of the second HARQ-ACK codebook may be 4. The terminal device 1 may replace the first bit of the second HARQ-ACK codebook with the first HARQ-ACK codebook, and report (transmit) the generated HARQ-ACK information via the PUCCH transmission opportunity 1523. The terminal device 1 may replace one or more bits from the beginning of the second HARQ-ACK codebook with one or more bits of the first HARQ-ACK codebook, and report (transmit) the generated HARQ-ACK information via the PUCCH transmission opportunity 1523. For example, the terminal device 1 may replace the first bit (the first MSB) and the second bit (the second MSB) of the second HARQ-ACK codebook with the first HARQ-ACK codebook, and report (transmit) the updated second HARQ-ACK information as HARQ-ACK information via the PUCCH transmission opportunity 1523. For example, the terminal device 1 may replace the first bit of the second HARQ-ACK codebook with the first bit of the first HARQ-ACK codebook, replace the second bit of the second HARQ-ACK codebook with the second bit of the first HARQ-ACK codebook, and report (transmit) the updated second HARQ-ACK codebook via the PUCCH transmission opportunity 1523. The base station device 3 may receive the above-mentioned 4-bit HARQ-ACK information via the PUCCH transmission opportunity 1523.

Figure 16 shows an example of generating HARQ-ACK information.

16, the slot in which PUCCH 1622 is placed may be indicated by the PDSCH-to-HARQ feedback timing indicator field included in each of PDCCH 1601, PDCCH 1602, PDCCH 1603, PDCCH 1604, and PDCCH 1605. Also, the slot in which PUCCH 1623 is placed may be indicated by the PDSCH-to-HARQ feedback timing indicator field included in each of PDCCH 1606 and PDCCH 1607.

16, it is assumed that PDSCH1611 to PDSCH1617 are linked to PDSCH group g (i.e., the same PDSCH group). After PUCCH transmission opportunity 1621, terminal device 1 receives PDCCH1601, PDCCH1602, PDCCH1603, PDCCH1604, and PDCCH1605, and receives PDSCH1611, PDSCH1612, PDSCH1613, PDSCH1614, and PDSCH1615 scheduled by the DCI format included in each PDCCH. Here, it is assumed that the HARQ-ACK information reported via the PUCCH transmission opportunity 1621 is correctly detected in the base station device 3, and the NFI bit (NFI bit for PDSCH group g) is toggled in the base station device 3, and the counter DAI (counter DAI for PDSCH group g) and/or the total DAI (total DAI for PDSCH group g) are reset. It is assumed that the NFI bit (NFI bit for PDSCH group g) is toggled in the base station device 3, and the counter DAI (counter DAI for PDSCH group g) and/or the total DAI (total DAI for PDSCH group g) are reset at the timing before the PDCCH 1601 is transmitted. Here, the DCI format included in the PDCCH 1601 indicates 0 as the NFI bit and 1 as the counter DAI. The DCI format included in the PDCCH 1602 indicates 0 as the NFI bit and 2 as the counter DAI. The DCI format included in the PDCCH 1603 indicates 0 as the NFI bit and 3 as the counter DAI. The DCI format included in the PDCCH 1604 indicates 0 as the NFI bit and 4 as the counter DAI. The DCI format included in the PDCCH 1605 indicates 0 as the NFI bit and 1 as the counter DAI. The terminal device 1 attempts to report (transmit) the PUCCH via the PUCCH transmission opportunity 1622 in order to report HARQ-ACK information including the HARQ-ACK bit for each of the PDSCH 1611, the PDSCH 1612, the PDSCH 1613, the PDSCH 1614, and the PDSCH 1615. Furthermore, the terminal device 1 receives the PDCCH 1606 after the PUCCH transmission opportunity 1622, and receives the PDSCH 1616 scheduled by the DCI format included in the PDCCH 1606. The terminal device 1 receives the PDCCH 1607, and receives the PDSCH 1617 scheduled by the DCI format included in the PDCCH 1607. For example, if the DCI format included in the PDCCH 1606 indicates 0 as the NFI bit and 2 as the counter DAI, and the DCI format included in the PDCCH 1607 indicates 0 as the NFI bit and 3 as the counter DAI, the terminal device 1 may assume that the HARQ-ACK information for the PDCCH 1601, the PDCCH 1602, the PDCCH 1603, the PDCCH 1604, and the PDCCH 1605 is not correctly detected (decoded) in the base station device 3 based on the NFI bit. That is, in such a case, the base station device 3 may continue to accumulate the values of the counter DAI and/or the total DAI without toggling the NFI bit corresponding to the PDSCH group g indicated by the DCI format included in each of the PDCCHs 1601 to 1607. Also, in such a case, the terminal device 1 may attempt to report (transmit) HARQ-ACK information including the HARQ-ACK bit for each of the PDSCHs 1611, 1612, 1613, 1614, 1615, 1616, and 1617 via the PUCCH transmission opportunity 1623. The base station device 3 receives the HARQ-ACK information via the PUCCH transmission opportunity 1621 and toggles the NFI bit. The base station device 3 transmits a PDCCH 1601 used for scheduling a PDSCH 1611, and indicates an NFI of 0 and a counter DAI of 1 according to the DCI format included in the PDCCH 1601. The base station device 3 transmits a PDCCH 1602 used for scheduling a PDSCH 1612, and indicates an NFI of 0 and a counter DAI of 2 according to the DCI format included in the PDCCH 1602. The base station device 3 transmits a PDCCH 1603 used for scheduling a PDSCH 1613, and indicates an NFI of 0 and a counter DAI of 3 according to the DCI format included in the PDCCH 1603. The base station device 3 transmits a PDCCH 1604 used for scheduling a PDSCH 1614, and indicates an NFI of 0 and a counter DAI of 4 according to the DCI format included in the PDCCH 1604. The base station device 3 transmits a PDCCH 1605 used for scheduling a PDSCH 1615, and indicates an NFI of 0 and a counter DAI of 1 according to the DCI format included in the PDCCH 1605. The base station device 3 transmits a PDCCH 1606 used for scheduling a PDSCH 1616, and indicates an NFI of 0 and a counter DAI of 2 according to the DCI format included in the PDCCH 1606. The base station device 3 transmits a PDCCH 1607 used for scheduling a PDSCH 1617, and indicates an NFI of 0 and a counter DAI of 3 according to the DCI format included in the PDCCH 1607.

Figure 17 shows an example of generating HARQ-ACK information.

Figure 18 shows an example of generating HARQ-ACK information.

The HARQ-AC codebook may be generated according to the procedures shown in Figures 12, 13, and 14. The HARQ-ACK information may be composed of one or more HARQ-ACK codebooks. The HARQ-ACK information may be generated based on one or more HARQ-ACK codebooks.

In Fig. 17 and Fig. 18, V _temp may be a parameter used in the procedure of generating HARQ-ACK information in Fig. 12, Fig. 13, and Fig. 14. V _temp may be a parameter used in the procedure of generating a HARQ-ACK codebook. V _temp may be given by a DCI format that schedules a PDSCH. V _temp may be a variable to which a value of a counter DAI included in a DCI format detected by a PDCCH monitoring opportunity corresponding to a previous PUCCH transmission opportunity is set. j may be a parameter used in the procedure of generating HARQ-ACK information in Fig. 12, Fig. 13, and Fig. 14. j may be a variable given based on a value of a counter DAI included in a DCI format detected by a PDCCH monitoring opportunity corresponding to a previous PUCCH transmission opportunity.

Vtemp may be defined as a remainder obtained by dividing the size O ^ACK of the HARQ-ACK codebook by a predetermined number (for example, 4). That is, _Vtemp = mod (O ^ACK , 4). _Vtemp may be defined as a remainder obtained by dividing the value obtained by subtracting the number of HARQ-ACK bits corresponding to the SPS PDSCH from the size O ^ACK of the HARQ-ACK codebook by the predetermined number. j may be defined as a quotient obtained by dividing the size O ^ACK of the HARQ-ACK codebook by a predetermined number (for example, 4). That is, _Vtemp = floor (O ^ACK , 4). _Vtemp may be defined as a quotient obtained by dividing the value obtained by subtracting the number of HARQ-ACK bits corresponding to the SPS PDSCH from the size O ^ACK of the HARQ-ACK codebook by the predetermined number.

16 and 17, the generation of HARQ-ACK information transmitted via the PUCCH transmission opportunity 1623 will be described. The terminal device 1 may generate the HARQ-ACK codebook 1701 by the procedure shown in FIG. 12, FIG. 13, and FIG. 14 based at least on the counter DAI corresponding to the PDSCH 1611, the counter DAI corresponding to the PDSCH 1612, the counter DAI corresponding to the PDSCH 1613, the counter DAI corresponding to the PDSCH 1614, the counter DAI corresponding to the PDSCH 1615, and/or the total DAI corresponding to the PDSCH 1615. The size (length, number of bits) of the HARQ-ACK codebook 1701 may be determined based at least on the total DAI corresponding to the PDSCH 1615. For the PUCCH transmission opportunity 1622, a HARQ-ACK codebook 1701 (first HARQ-ACK codebook) with V _temp =1, j=1, and 5 bits is output by the procedure of generating the HARQ-ACK codebook of FIG. 12, FIG. 13, and FIG. 14. The HARQ-ACK codebook 1701 may be a HARQ-ACK codebook generated for a set of PDCCH monitoring opportunities corresponding to the slot n in which the PUCCH transmission opportunity 1622 is arranged. The terminal device 1 may store the output parameters (e.g., V _temp =1, and j=1). The terminal device 1 may store the output parameters (e.g., V _temp =1, and j=1) for a PUCCH transmission opportunity different from the PUCCH transmission opportunity 1622. When the NFI bit is not toggled, the terminal device 1 may generate the second HARQ-ACK codebook by referring to the parameters output in generating the HARQ-ACK codebook 1701 (first HARQ-ACK codebook). The terminal device 1 may generate the HARQ-ACK codebook 1702 by the procedures shown in Figures 12, 13, and 14 based on at least the counter DAI corresponding to the PDSCH 1616, the counter DAI corresponding to the PDSCH 1617, and/or the total DAI corresponding to the PDSCH 1616. The size (length, number of bits) of the HARQ-ACK codebook 1702 may be determined based at least on the total DAI corresponding to the PDSCH 1617. For example, when the terminal device 1 initializes the procedure for generating the HARQ-ACK codebook in Figures 12, 13, and 14, if the value of the counter DAI (e.g., 2) indicated by the DCI format included in the first received PDCCH (e.g., PDCCH 1606) is greater than the stored value of V _temp (e.g., 1), the terminal device 1 may set j to the stored value of j (e.g., 1) and generate a 7-bit HARQ-ACK codebook 1702 by the procedure for generating the HARQ-ACK codebook. The HARQ-ACK codebook 1702 may include at least a HARQ-ACK codebook generated for a set of PDCCH monitoring opportunities corresponding to slot n in which the PUCCH transmission opportunity 1623 is arranged. The terminal device 1 may replace (override, replace) the first bit of the HARQ-ACK codebook 1702 with the HARQ-ACK codebook 1701 to generate HARQ-ACK information 1703. For example, the terminal device 1 may replace the first to fifth bits of the HARQ-ACK codebook 1702 with five bits of the HARQ-ACK codebook 1701 to generate HARQ-ACK information 1703. For example, the terminal device 1 may replace (override, replace) the Yth bit from the top of the HARQ-ACK codebook 1702 with the HARQ-ACK codebook 1701 to generate HARQ-ACK information 1703. Y may be the size (length, number of bits) of the HARQ-ACK codebook 1701. Y may be given based at least on the stored j and/or V _temp . For example, Y=4×j+V _temp may be used. For example, the terminal device 1 may replace the first to fifth bits of the HARQ-ACK codebook 1702 with five bits of the HARQ-ACK codebook 1701 to generate HARQ-ACK information 1703. The terminal device 1 may report (transmit) the HARQ-ACK information 1703 via the PUCCH transmission opportunity 1623. The base station device 3 may receive the HARQ-ACK information 1703 via the PUCCH transmission opportunity 1623. Here, the HARQ-ACK codebook or HARQ-ACK information (for example, the HARQ-AC codebook 1701) reported (transmitted) via the PUCCH transmission opportunity 1622 may be referred to as the first HARQ-ACK information or the first HARQ-ACK codebook. The HARQ-ACK codebook (eg, HARQ-AC codebook 1702) generated for the PUCCH transmission opportunity 1623 may be referred to as a second HARQ-ACK codebook.

As shown in FIG. 17, parameters (e.g., V temp , j, O ACK , V s, etc. ₎ used for generating a HARQ-ACK codebook (HARQ-ACK codebook 1701) based on a set of PDCCH monitoring opportunities for a slot in which the PUCCH transmission opportunity 1622 is arranged may be used for generating a HARQ-ACK codebook based on a set ^of PDCCH monitoring opportunities for a slot in which the PUCCH transmission opportunity 1623 is arranged. For example, _when the parameters include at least V _temp , an initial value of V _temp in generating a HARQ-ACK codebook based on a set of PDCCH monitoring opportunities for a slot in which the PUCCH transmission opportunity 1623 is arranged may be given based at least on the parameters. For example, when the parameters include at least j, an initial value of j in generating a HARQ-ACK codebook based on a set of PDCCH monitoring opportunities for a slot in which the PUCCH transmission opportunity 1623 is arranged may be given based at least on the parameters.

As shown in FIG. 17, a portion of the HARQ-ACK codebook based on a set of PDCCH monitoring opportunities for a slot in which the PUCCH transmission opportunity 1623 is located may be replaced with a HARQ-ACK codebook (HARQ-ACK codebook 1701) based on a set of PDCCH monitoring opportunities for a slot in which the PUCCH transmission opportunity 1622 is located, based at least on parameters used for generating the HARQ-ACK codebook 1701.

As shown in FIG. 17, the size of the HARQ-ACK codebook 1702 may be given based at least on parameters used to generate a HARQ-ACK codebook (HARQ-ACK codebook 1701) based on a set of PDCCH monitoring opportunities for the slot in which the PUCCH transmission opportunity 1622 is located.

16 and 18, the generation of HARQ-ACK information transmitted via the PUCCH transmission opportunity 1623 will be described. The terminal device 1 may generate a HARQ-ACK codebook 1801 by the procedure shown in FIG. 12, FIG. 13, and FIG. 14 based at least on the counter DAI corresponding to the PDSCH 1611, the counter DAI corresponding to the PDSCH 1612, the counter DAI corresponding to the PDSCH 1613, the counter DAI corresponding to the PDSCH 1614, the counter DAI corresponding to the PDSCH 1615, and/or the total DAI corresponding to the PDSCH 1615. The size (length, number of bits) of the HARQ-ACK codebook 1801 may be determined based at least on the total DAI corresponding to the PDSCH 1615. Here, it is assumed that the DCI format included in the PDCCH 1604 and the PDCCH 1605 is not detected. For the PUCCH transmission opportunity 1622, V _temp =3, j =0, and a 3-bit HARQ-ACK codebook 1801 (first HARQ-ACK codebook) are output by the procedure of generating the HARQ-ACK codebook of Figures 12, 13, and 14. The terminal device 1 may store the output parameters (e.g., V _temp =3, and j =0). When the NFI bit is not toggled, the terminal device 1 may generate the second HARQ-ACK codebook by referring to the parameters output in generating the HARQ-ACK codebook 1801 (first HARQ-ACK codebook). Here, if the counter DAI indicated by the DCI format included in the first received PDCCH (e.g., PDCCH 1606) is equal to or less than the stored value of V _temp , the terminal device 1 may update the stored j to j+1 (i.e., may increment the stored value of j by 1). The terminal device 1 may generate the HARQ-ACK codebook 1802 by the procedure shown in Figures 12, 13, and 14 based at least on the counter DAI corresponding to the PDSCH 1616, the counter DAI corresponding to the PDSCH 1617, and/or the total DAI corresponding to the PDSCH 1616. The size (length, number of bits) of the HARQ-ACK codebook 1802 may be determined based at least on the total DAI corresponding to the PDSCH 1617. For example, the terminal device 1 may set j to the stored (updated) j value (for example, 1) at the time of initialization of the procedure for generating the HARQ-ACK codebook in FIG. 12, FIG. 13, and FIG. 14, and generate a 7-bit HARQ-ACK codebook 1802 by the procedure for generating the HARQ-ACK codebook. The terminal device 1 may replace (override, replace) the first bit of the HARQ-ACK codebook 1802 with the HARQ-ACK codebook 1801, and generate the HARQ-ACK information 1803. For example, the terminal device 1 may replace (override, replace) the Y-th bit from the top of the HARQ-ACK codebook 1802 with the HARQ-ACK codebook 1801, and generate the HARQ-ACK information 1803. Y may be the size (length, number of bits) of the HARQ-ACK codebook 1801. Y may be given based at least on the stored j and/or V _temp . For example, Y=4×j+V _temp may be used. For example, the terminal device 1 may replace the first to third bits of the HARQ-ACK codebook 1802 with three bits of the HARQ-ACK codebook 1801 to generate HARQ-ACK information 1803. The terminal device 1 may report (transmit) the HARQ-ACK information 1803 via the PUCCH transmission opportunity 1623. The base station device 3 may receive the HARQ-ACK information 1803 via the PUCCH transmission opportunity 1623. Here, the HARQ-ACK codebook or HARQ-ACK information (e.g., HARQ-AC codebook 1801) reported (transmitted) via the PUCCH transmission opportunity 1622 may be referred to as the first HARQ-ACK information or the first HARQ-ACK codebook, and the HARQ-ACK codebook (e.g., HARQ-AC codebook 1802) generated for the PUCCH transmission opportunity 1623 may be referred to as the second HARQ-ACK codebook.

As shown in FIG. 18, parameters (e.g., V temp , j, O ACK , V s, etc. ₎ used for generating a HARQ-ACK codebook (HARQ-ACK codebook 1801) based on a set of PDCCH monitoring opportunities for a slot in which the PUCCH transmission opportunity 1622 is arranged may be used for generating a HARQ-ACK codebook based on a set ^of PDCCH monitoring opportunities for a slot in which the PUCCH transmission opportunity 1623 is arranged. For example, _when the parameters include at least V _temp , an initial value of V _temp in generating a HARQ-ACK codebook based on a set of PDCCH monitoring opportunities for a slot in which the PUCCH transmission opportunity 1623 is arranged may be given based at least on the parameters. For example, when the parameters include at least j, an initial value of j in generating a HARQ-ACK codebook based on a set of PDCCH monitoring opportunities for a slot in which the PUCCH transmission opportunity 1623 is arranged may be given based at least on the parameters.

As shown in FIG. 18, a portion of the HARQ-ACK codebook based on a set of PDCCH monitoring opportunities for a slot in which the PUCCH transmission opportunity 1623 is located may be replaced with a HARQ-ACK codebook (HARQ-ACK codebook 1801) based on a set of PDCCH monitoring opportunities for a slot in which the PUCCH transmission opportunity 1622 is located, based at least on parameters used for generating the HARQ-ACK codebook 1801.

As shown in FIG. 18, the size of the HARQ-ACK codebook 1802 may be given based at least on parameters used to generate a HARQ-ACK codebook (HARQ-ACK codebook 1801) based on a set of PDCCH monitoring opportunities for the slot in which the PUCCH transmission opportunity 1622 is located.

The terminal device 1 generates a HARQ-ACK codebook based on the above parameters ( _Vtemp , j, ^OACK , _Vs, etc.) and transmits the HARQ-ACK codebook at a PUCCH transmission opportunity. The base station device 3 determines HARQ-ACK information for the PDSCH transmitted based on the above parameters ( _Vtemp , j, ^OACK , _Vs , etc.) for the HARQ-ACK codebook received at a PUCCH transmission opportunity.

Another example of the generation of HARQ-ACK information transmitted via the PUCCH transmission opportunity 1623 will be described in FIG. 16 and FIG. 17. For the PUCCH transmission opportunity 1622, V _temp =1, j=1, and a 5-bit HARQ-ACK codebook 1701 (first HARQ-ACK codebook) are output by the procedure of generating the HARQ-ACK codebook of FIG. 12, FIG. 13, and FIG. 14. The HARQ-ACK codebook 1701 may be a HARQ-ACK codebook generated for a set of PDCCH monitoring opportunities corresponding to the slot n in which the PUCCH transmission opportunity 1622 is arranged. The terminal device 1 may store the output parameters (for example, V _temp =1, and j=1). The terminal device 1 may store the output parameters (e.g., V _temp =1 and j=1) for a PUCCH transmission opportunity different from the PUCCH transmission opportunity 1622. When the NFI bit is not toggled, the terminal device 1 may generate HARQ-ACK information 1703 to be reported in the PUCCH corresponding to the PUCCH transmission opportunity 1623 by referring to the parameters output in generating the HARQ-ACK codebook 1701 (first HARQ-ACK codebook) when generating the second HARQ-ACK codebook. For example, the terminal device 1 may generate a 3-bit HARQ-ACK codebook 1702 based at least on a set of PDCCH monitoring opportunities corresponding to the PUCCH transmission opportunity 1623. The terminal device 1 may generate HARQ-ACK information 1704 by deleting (or cutting, extracting, or trimming) a part or all of the HARQ-ACK codebook 1702, or by adding one or more bits to the HARQ-ACK codebook 1702. The HARQ-ACK information 1703 may be generated by combining the HARQ-ACK codebook 1701 and the HARQ-ACK information 1704. The terminal device 1 may report (transmit) the HARQ-ACK information 1703 via the PUCCH transmission opportunity 1623. The base station device 3 may receive the HARQ-ACK information 1703 via the PUCCH transmission opportunity 1623.

Here, the generation of the HARQ-ACK information 1704 may be based at least on parameters (e.g., V _temp , j, O ^ACK , V _s , etc.) used to generate the HARQ-ACK codebook 1701. For example, based at least on the parameters, a part or all of the HARQ-ACK codebook 1702 may be deleted for the generation of the HARQ-ACK information 1704. For example, based at least on the parameters, one or more bits may be added to the HARQ-ACK codebook 1702 for the generation of the HARQ-ACK information 1704.

For example, when N1701+N1702>j*4+V _temp , the last N _rm =N1701+N1702-j*4-V _temp bits may be deleted from the HARQ-ACK codebook 1702. Here, N1701 is the number of bits of the HARQ-ACK codebook 1701, and N1702 is the number of bits of the HARQ-ACK codebook 1702. Also, j is the sum of j1701 output in generating the HARQ-ACK codebook 1701 and j1702 output in generating the HARQ-ACK codebook 1702. Also, V _temp is the V _temp output in generating the HARQ-ACK codebook 1702.

For example, HARQ-ACK codebook 1702 may be provided as HARQ-ACK information 1704, where N1701+N1702=j*4+V _temp .

For example, if N1701+N1702<j*4+ _Vtemp , _Nadd =j*4+ _Vtemp -N1701-N1702 bits may be added to the beginning of the HARQ-ACK codebook 1702. The values of the _Nadd bits may be set to indicate a NACK, for example, the _Nadd bits may all be set to zero.

For example, if N1701+N1702<j*4+ _Vtemp , _Nadd =j*4+ _Vtemp -N1701-N1702 bits may be added to the end of the HARQ-ACK codebook 1701.

As a different method, the following processing may be performed. In FIG. 16, the terminal device 1 generates a first HARQ-ACK codebook according to the procedures shown in FIG. 12, FIG. 13, and FIG. 14 based at least on the counter DAI corresponding to PDSCH 1611, the counter DAI corresponding to PDSCH 1612, the counter DAI corresponding to PDSCH 1613, the counter DAI corresponding to PDSCH 1614, the counter DAI corresponding to PDSCH 1615, and/or the total DAI corresponding to PDSCH 1615, and attempts to report (transmit) the first HARQ-ACK codebook via the PUCCH transmission opportunity 1522. The terminal device 1 generates a second HARQ-ACK codebook according to the procedures shown in FIG. 12, FIG. 13, and FIG. 14 based on at least the counter DAI corresponding to PDSCH 1616, the counter DAI corresponding to PDSCH 1617, and/or the total DAI corresponding to PDSCH 1617. Next, the terminal device 1 calculates ((Vtemp+1) mod 4-1) using the final Vtemp stored for the generation of the first HARQ-ACK codebook. If the value of the above formula is positive, the ((Vtemp+1) mod 4-1)-th bit is deleted from the beginning of the generated second HARQ-ACK codebook. If the value of the above formula is negative, ((Vtemp+1) mod 4-1) bits are added to the beginning of the generated second HARQ-ACK codebook. For the added bits, a bit indicating NAKC is set as HARQ-ACK information. If the value of the above formula is zero, no bits are deleted or added to the generated second HARQ-ACK codebook. After performing the above process, the terminal device 1 then adds the first HARQ-ACK codebook to the beginning of the second HARQ-ACK codebook. The terminal device 1 reports (transmits) the HARQ-ACK codebook in which the first HARQ-ACK codebook is added to the beginning of the second HARQ-ACK codebook via the PUCCH transmission opportunity 1623. 16, a 5-bit first HARQ-ACK codebook is generated based at least on a counter DAI corresponding to PDSCH 1611, a counter DAI corresponding to PDSCH 1612, a counter DAI corresponding to PDSCH 1613, a counter DAI corresponding to PDSCH 1614, a counter DAI corresponding to PDSCH 1615, and/or a total DAI corresponding to PDSCH 1615. A 3-bit second HARQ-ACK codebook is generated based at least on a counter DAI corresponding to PDSCH 1616, a counter DAI corresponding to PDSCH 1617, and/or a total DAI corresponding to PDSCH 1617. The final Vtemp saved for the generation of the first HARQ-ACK codebook is 1, and the value of ((Vtemp+1) mod 4-1) is 1. Thus, the first bit from the beginning of the generated second HARQ-ACK codebook is deleted to generate a 2-bit second HARQ-ACK codebook. The 5-bit first HARQ-ACK codebook is added to the beginning of the 2-bit second HARQ-ACK codebook to generate a 7-bit HARQ-ACK codebook. The 7-bit HARQ-ACK codebook is reported (transmitted) via the PUCCH transmission opportunity 1623.

One aspect of the present invention is capable of realizing efficient communication. One aspect of the present invention is capable of realizing efficient transmission and reception of HARQ-ACK information. One aspect of the present invention is capable of realizing efficient transmission and reception of HARQ-ACK codebooks.

Various aspects of the device relating to one aspect of this embodiment are described below.

(1) In order to achieve the above object, the aspects of the present invention take the following measures. That is, a first aspect of the present invention is a terminal device comprising a receiving unit that receives a first PDSCH and a transmitting unit that reports a first HARQ-ACK codebook of X bits for the first PDSCH via a first PUCCH transmission opportunity, and includes receiving a second PDSCH after the first PUCCH transmission opportunity, generating a second HARQ-ACK codebook for the second PDSCH, deleting X bits from the beginning of the second HARQ-ACK codebook, and reporting the second HARQ-ACK codebook and HARQ-ACK information including the first HARQ-ACK codebook via the second PUCCH transmission opportunity.

(2) A second aspect of the present invention is a terminal device comprising a receiving unit that receives a first PDSCH and a transmitting unit that reports a first HARQ-ACK codebook of X bits for the first PDSCH via a first PUCCH transmission opportunity, and includes receiving a second PDSCH after the first PUCCH transmission opportunity, generating a second HARQ-ACK codebook for the second PDSCH, and reporting HARQ-ACK information generated by adding bits from the X+1th bit onwards of the second HARQ-ACK codebook to the first HARQ-ACK information via the second PUCCH transmission opportunity.

(3) A third aspect of the present invention is a terminal device comprising a receiving unit that receives a first PDSCH and a transmitting unit that reports a first HARQ-ACK codebook of X bits for the first PDSCH via a first PUCCH transmission opportunity, and includes receiving a second PDSCH after the first PUCCH transmission opportunity, generating a second HARQ-ACK codebook for the second PDSCH, and reporting HARQ-ACK information generated by replacing the first bits of the second HARQ-ACK codebook with the first HARQ-ACK codebook via the second PUCCH transmission opportunity.

(4) A fourth aspect of the present invention is a terminal device comprising a receiving unit that receives a first PDSCH and a transmitting unit that reports a first HARQ-ACK codebook including at least a HARQ-ACK bit for the first PDSCH via a PUCCH corresponding to a first PUCCH transmission opportunity, and includes receiving the second PDSCH after the first PUCCH transmission opportunity, generating a second HARQ-ACK codebook including at least a HARQ-ACK bit for the second PDSCH, generating HARQ-ACK information based at least on the second HARQ-ACK codebook and parameters used in generating the first HARQ-ACK codebook, and reporting the HARQ-ACK information via the second PUCCH transmission opportunity.

(5) In the first aspect of the present invention, the second aspect of the present invention, the third aspect of the present invention, and the fourth aspect of the present invention, the first PDSCH and the second PDSCH are linked to the same PDSCH group.

(6) A fifth aspect of the present invention is a base station device comprising a transmitter that transmits a first PDSCH and a receiver that receives a first HARQ-ACK codebook of X bits for the first PDSCH via a first PUCCH transmission opportunity, wherein a second PDSCH is transmitted after the first PUCCH transmission opportunity, a second HARQ-ACK codebook for the second PDSCH is generated, X bits are deleted from the beginning of the second HARQ-ACK codebook, and the second HARQ-ACK codebook and HARQ-ACK information including the first HARQ-ACK codebook are received via the second PUCCH transmission opportunity.

(7) A sixth aspect of the present invention is a base station device comprising a transmitter that transmits a first PDSCH and a receiver that receives a first HARQ-ACK codebook of X bits for the first PDSCH via a first PUCCH transmission opportunity, wherein a second PDSCH is transmitted after the first PUCCH transmission opportunity, a second HARQ-ACK codebook for the second PDSCH is generated, and bits from the X+1th bit onwards of the second HARQ-ACK codebook are added to the first HARQ-ACK codebook to generate HARQ-ACK information, which is received via the second PUCCH transmission opportunity.

(8) A seventh aspect of the present invention is a base station device comprising a transmitter that transmits a first PDSCH and a receiver that receives a first HARQ-ACK codebook of X bits for the first PDSCH via a first PUCCH transmission opportunity, and includes transmitting a second PDSCH after the first PUCCH transmission opportunity, generating a second HARQ-ACK codebook for the second PDSCH, and receiving HARQ-ACK information generated by replacing bits from the beginning of the second HARQ-ACK codebook with the first HARQ-ACK codebook via the second PUCCH transmission opportunity.

(9) An eighth aspect of the present invention is a base station device comprising: a transmitter unit that transmits a first PDSCH; and a receiver unit that receives a first HARQ-ACK codebook including at least a HARQ-ACK bit for the first PDSCH via a PUCCH corresponding to a first PUCCH transmission opportunity, the receiver unit transmitting the second PDSCH after the first PUCCH transmission opportunity, generating a second HARQ-ACK codebook including at least a HARQ-ACK bit for the second PDSCH, generating HARQ-ACK information based at least on the second HARQ-ACK codebook and parameters used in generating the first HARQ-ACK codebook, and receiving the HARQ-ACK information via the second PUCCH transmission opportunity.

(10) In the fifth aspect of the present invention, the sixth aspect of the present invention, the seventh aspect of the present invention, and the eighth aspect of the present invention, the first PDSCH and the second PDSCH are linked to the same PDSCH group.

The above embodiment relating to one aspect of the present invention makes it possible to properly realize transmission and reception of HARQ-ACK information between the terminal device 1 and the base station device 3.

The base station device 3 and the program operating in the terminal device 1 relating to one aspect of the present invention may be a program that controls a CPU (Central Processing Unit) or the like (a program that causes a computer to function) so as to realize the functions of the above-described embodiment relating to one aspect of the present invention. Information handled by these devices is temporarily stored in a RAM (Random Access Memory) during processing, and is then stored in various ROMs such as a Flash ROM (Read Only Memory) or a HDD (Hard Disk Drive), and is read, modified, and written by the CPU as necessary.

In addition, a part of the terminal device 1 and the base station device 3 in the above-mentioned embodiment may be realized by a computer. In that case, the program for realizing this control function may be recorded on a computer-readable recording medium, and the program recorded on the recording medium may be read into a computer system and executed to realize the control function.

The "computer system" referred to here is a computer system built into the terminal device 1 or base station device 3, and includes hardware such as the OS and peripheral devices. Furthermore, the "computer-readable recording medium" refers to portable media such as flexible disks, optical magnetic disks, ROMs, and CD-ROMs, and storage devices such as hard disks built into the computer system.

Furthermore, "computer-readable recording medium" may also include something that dynamically holds a program for a short period of time, such as a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line, or something that holds a program for a fixed period of time, such as volatile memory within a computer system that serves as a server or client in such a case. The above program may also be one that realizes part of the functions described above, or one that can realize the functions described above in combination with a program already recorded in the computer system.

The terminal device 1 may be composed of at least one processor and at least one memory including computer program instructions (computer program). The memory and computer program instructions (computer program) may be configured to cause the terminal device 1 to perform the operations and processing described in the above embodiments using the processor. The base station device 3 may be composed of at least one processor and at least one memory including computer program instructions (computer program). The memory and computer program instructions (computer program) may be configured to cause the base station device 3 to perform the operations and processing described in the above embodiments using the processor.

The base station device 3 in the above-described embodiment can also be realized as an aggregate (device group) consisting of multiple devices. Each of the devices constituting the device group may have some or all of the functions or functional blocks of the base station device 3 related to the above-described embodiment. It is sufficient for an device group to have all of the functions or functional blocks of the base station device 3. The terminal device 1 related to the above-described embodiment can also communicate with the base station device as an aggregate.

In addition, the base station device 3 in the above-mentioned embodiment may be an EUTRAN (Evolved Universal Terrestrial Radio Access Network) and/or an NG-RAN (NextGen RAN, NR RAN). In addition, the base station device 3 in the above-mentioned embodiment may have some or all of the functions of an upper node for an eNodeB and/or a gNB.

In addition, some or all of the terminal device 1 and base station device 3 in the above-mentioned embodiments may be realized as an LSI, which is typically an integrated circuit, or as a chip set. Each functional block of the terminal device 1 and base station device 3 may be individually chipped, or some or all may be integrated and chipped. The integrated circuit method is not limited to LSI, and may be realized by a dedicated circuit or a general-purpose processor. Furthermore, if an integrated circuit technology that can replace LSI emerges due to advances in semiconductor technology, it is also possible to use an integrated circuit based on that technology.

In addition, in the above-described embodiment, a terminal device is described as an example of a communication device, but the present invention is not limited to this and can also be applied to terminal devices or communication devices such as stationary or non-movable electronic devices installed indoors or outdoors, such as AV equipment, kitchen equipment, cleaning/washing equipment, air conditioning equipment, office equipment, vending machines, and other household appliances.

Although an embodiment of the present invention has been described above in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and design modifications and the like that do not depart from the gist of the present invention are also included. Furthermore, various modifications of one aspect of the present invention are possible within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present invention. Also included are configurations in which elements described in the above embodiments are substituted for elements that have the same effect.

One aspect of the present invention can be used, for example, in a communication system, a communication device (e.g., a mobile phone device, a base station device, a wireless LAN device, or a sensor device), an integrated circuit (e.g., a communication chip), or a program.

1 (1A, 1B, 1C) Terminal device 3 Base station device 10, 30 Radio transmission/reception unit 11, 31 Antenna unit 12, 32 RF unit 13, 33 Baseband unit 14, 34 Upper layer processing unit 15, 35 Media access control layer processing unit 16, 36 Radio resource control layer processing unit 91, 92, 93, 94 Search space set 301 Primary cell 302, 303 Secondary cell 801, 802, 803, 804, 805, 806 Search space set monitoring opportunity 811, 812, 813, 814 DCI format 1101, 1102, 1103, 1104, 1105 PDCCH
1111, 1112, 1113, 1114, 1115 PDSCH
1121, 1122, 1123 PUCCH

Claims (3)

A receiving unit that receives a first PDSCH;
a transmitter configured to report a first HARQ-ACK codebook of X bits for the first PDSCH via a first PUCCH transmission opportunity;
receiving a second PDSCH after the first PUCCH transmission opportunity and generating a second HARQ-ACK codebook for the second PDSCH;
The terminal device reports HARQ-ACK information generated by adding bits from the X+1th bit onward of the second HARQ-ACK codebook to the first HARQ-ACK codebook via a second PUCCH transmission opportunity. A transmitter that transmits a first PDSCH;
a receiving unit configured to receive a first HARQ-ACK codebook of X bits for the first PDSCH via a first PUCCH transmission opportunity;
Transmitting a second PDSCH after the first PUCCH transmission opportunity, a second HARQ-ACK codebook for the second PDSCH is generated;
The base station device receives HARQ-ACK information generated by adding the X+1th bit and subsequent bits of the second HARQ-ACK codebook to the first HARQ-ACK codebook, via a second PUCCH transmission opportunity. A communication method for use in a terminal device, comprising:
Receive a first PDSCH;
reporting a first HARQ-ACK codebook of X bits for the first PDSCH via a first PUCCH transmission opportunity;
receiving a second PDSCH after the first PUCCH transmission opportunity and generating a second HARQ-ACK codebook for the second PDSCH;
the communication method comprising: reporting HARQ-ACK information generated by adding bits from the X+1th bit onward of the second HARQ-ACK codebook to the first HARQ-ACK codebook via a second PUCCH transmission opportunity.

Images