JP7680998B2 - 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. 2020-25107, filed in Japan on February 18, 2020, the contents of which are incorporated herein by reference.

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

3GPP is currently studying and standardizing the next-generation standard (NR: New Radio) as a 5G communication method. NR is required to meet the requirements of three scenarios, eMBB (enhanced Mobile Broadband), mMTC (massive Machine Type Communication), and URLLC (Ultra Reliable and Low Latency Communication), within a single technology framework.

Methods using multiple frequency spectrums are also being considered (Non-Patent Document 2). Multiple base station devices are being considered to communicate with terminal devices using different frequency spectrums. One base station device uses the frequency spectrum for the downlink and the uplink, and the other base station device communicates with terminal device 1 using the frequency spectrum for the downlink.

"New SID on inter-gNB coordination for multi-carrier/TRP operations for NR", RP-192292, NTT docomo, INC 3GPP TSG RAN Meeting #85, NewportBeach, USA, September 16-20, 2019.

In order to be able to appropriately control data retransmission, it is necessary for the data receiving side to appropriately feed back data error detection results, data reception results (received data was not erroneous, received data was erroneous, data was not received), etc. to the data transmitting side. The data transmitting side retransmits data that was not properly received at the receiving side based on the information fed back from the data receiving side. For example, the data transmitting side is a base station device, the data receiving side is a terminal device, the data is a transport block (transport block transmitted and received on PDSCH), and the data error detection result or reception result is HARQ-ACK. Efficient communication is achieved by realizing appropriate retransmission control. One aspect of the present invention provides a terminal device, a base station device, a communication method used in the terminal device, and a communication method used in the base station device that perform efficient communication.

(1) A first aspect of the present invention is a terminal device having a processor and a memory for storing computer program code, and performing operations including setting a first periodic resource and a second periodic resource in an uplink cell managed by a first base station device, and transmitting a HARQ-ACK codebook including a HARQ-ACK for a PDSCH of a downlink cell managed by a second base station device using the first periodic resource and the second periodic resource.

(2) Further, the HARQ-ACK codebook is composed of multiple HARQ-ACKs, each of which corresponds to a different HARQ process, and the HARQ-ACK codebook composed of the HARQ-ACKs corresponding to a first set of HARQ processes is transmitted on the first periodic resource, and the HARQ-ACK codebook composed of the HARQ-ACKs corresponding to a second set of HARQ processes is transmitted on the second periodic resource.

(3) Furthermore, an uplink cell managed by the second base station device is not configured for the terminal device.

(4) A second aspect of the present invention is a terminal device including a processor and a memory for storing computer program code, the terminal device including: setting periodic resources in an uplink cell managed by a first base station device; transmitting a HARQ-ACK codebook including a HARQ-ACK for a PDSCH of a downlink cell managed by a second base station device using the periodic resources; the HARQ-ACK codebook is composed of a plurality of HARQ-ACKs, each of which corresponds to a different HARQ process; and transmitting the HARQ-ACK codebook composed of the HARQ-ACKs corresponding to a first set of HARQ processes and the HARQ-ACK codebook composed of the HARQ-ACKs corresponding to a second set of HARQ processes. and transmitting the codebook in sequence in the time domain.

(5) Furthermore, an uplink cell managed by the second base station device is not configured for the terminal device.

(6) A third aspect of the present invention is a base station device comprising a processor and a memory for storing computer program code, which performs operations including setting a first periodic resource and a second periodic resource in an uplink cell for a terminal device, receiving from the terminal device a HARQ-ACK codebook including a HARQ-ACK for a PDSCH of a downlink cell managed by a different base station device using the first periodic resource and the second periodic resource, and forwarding the received HARQ-ACK to the different base station device.

(7) Further, the HARQ-ACK codebook is composed of multiple HARQ-ACKs, each of which corresponds to a different HARQ process, and the HARQ-ACK codebook composed of the HARQ-ACKs corresponding to a first set of HARQ processes is received on the first periodic resource, and the HARQ-ACK codebook composed of the HARQ-ACKs corresponding to a second set of HARQ processes is received on the second periodic resource.

(8) A fourth aspect of the present invention is a base station device including a processor and a memory for storing computer program code, the base station device configuring a periodic resource in an uplink cell for a terminal device, receiving a HARQ-ACK codebook including a HARQ-ACK for a PDSCH of a downlink cell managed by a different base station device in the periodic resource, the HARQ-ACK codebook being composed of a plurality of HARQ-ACKs, each of the HARQ-ACKs corresponding to a different HARQ process, and the HARQ-ACK codebook being composed of the HARQ-ACKs corresponding to a first set of HARQ processes and the HARQ-ACK codebook being composed of the HARQ-ACKs corresponding to a second set of HARQ processes. The base station device performs operations including receiving the HARQ-ACK and the codebook in a time domain in sequence, and transferring the received HARQ-ACK to the different base station device.

(9) A fifth aspect of the present invention is a communication method for use in a terminal device, comprising the steps of: setting a first periodic resource and a second periodic resource in an uplink cell managed by a first base station device; and transmitting a HARQ-ACK codebook including a HARQ-ACK for a PDSCH of a downlink cell managed by a second base station device using the first periodic resource and the second periodic resource.

(10) Further, the HARQ-ACK codebook is composed of a plurality of HARQ-ACKs, each of which corresponds to a different HARQ process, and the HARQ-ACK codebook composed of the HARQ-ACKs corresponding to a first set of HARQ processes is transmitted on the first periodic resource, and the HARQ-ACK codebook composed of the HARQ-ACKs corresponding to a second set of HARQ processes is transmitted on the second periodic resource.

(11) Furthermore, an uplink cell managed by the second base station device is not configured for the terminal device.

(12) A sixth aspect of the present invention is a communication method for use in a terminal device, comprising: setting periodic resources in an uplink cell managed by a first base station device; transmitting a HARQ-ACK codebook including a HARQ-ACK for a PDSCH of a downlink cell managed by a second base station device, using the periodic resources; the HARQ-ACK codebook is composed of a plurality of HARQ-ACKs, each of the HARQ-ACKs corresponding to a different HARQ process, and transmitting the HARQ-ACK codebook composed of the HARQ-ACKs corresponding to a first set of HARQ processes and the HARQ-ACK codebook composed of the HARQ-ACKs corresponding to a second set of HARQ processes in a time domain in sequence.

(13) Furthermore, an uplink cell managed by the second base station device is not configured for the terminal device.

(14) A seventh aspect of the present invention is a communication method for use in a base station device, comprising the steps of: setting a first periodic resource and a second periodic resource in an uplink cell for a terminal device; receiving from the terminal device, using the first periodic resource and the second periodic resource, a HARQ-ACK codebook including a HARQ-ACK for a PDSCH of a downlink cell managed by a different base station device; and forwarding the received HARQ-ACK to the different base station device.

(15) Further, the HARQ-ACK codebook is composed of a plurality of HARQ-ACKs, each of which corresponds to a different HARQ process, and the HARQ-ACK codebook composed of the HARQ-ACKs corresponding to a first set of HARQ processes is received on the first periodic resource, and the HARQ-ACK codebook composed of the HARQ-ACKs corresponding to a second set of HARQ processes is received on the second periodic resource.

(16) An eighth aspect of the present invention is a communication method used in a base station device, comprising the steps of: setting a periodic resource in an uplink cell for a terminal device; receiving a HARQ-ACK codebook including a HARQ-ACK for a PDSCH of a downlink cell managed by a different base station device, using the periodic resource; the HARQ-ACK codebook is composed of a plurality of HARQ-ACKs, each of which corresponds to a different HARQ process; and receiving the HARQ-ACK codebook composed of the HARQ-ACKs corresponding to a first set of HARQ processes and the HARQ-ACK codebook composed of the HARQ-ACKs corresponding to a second set of HARQ processes. The method includes the steps of receiving the HARQ-ACK and the codebook in a time domain in sequence, and transferring the received HARQ-ACK to the different base station device.

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. 1 is a diagram illustrating an example of a configuration of a radio frame, a subframe, and a slot 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. FIG. 2 is a diagram illustrating an example of the configuration of one REG according to one aspect of the present embodiment. A figure showing an example of the configuration of CCE related to one aspect of this embodiment. A figure showing an example of the relationship between the number of REGs constituting a group of REGs and a mapping method of PDCCH candidates in one embodiment of the present invention. 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. A figure showing an example of a search area set in a terminal device 1 according to one aspect of this embodiment. A figure showing an example of a search area set in a terminal device 1 according to one aspect of this embodiment. A figure showing an example of a search area set in a terminal device 1 according to one aspect of this embodiment. A figure showing an example of a search area set in a terminal device 1 according to 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".

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 includes terminal devices 1A to 1C and base station devices 3A to 3B. Hereinafter, terminal devices 1A to 1C are also referred to as terminal devices 1 (UE). Hereinafter, base station devices 3A to 3B are also referred to as base station devices 3 (gNB).

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 terminal device 1 communicates with the base station device 3A (first base station device) and the base station device 3B (second base station device) simultaneously. The base station device 3A and the base station device 3B communicate with the terminal device 1 using different frequency spectrums (carrier frequencies). This operation may be called carrier aggregation or dual connectivity. The communication between the terminal device 1 and the base station device 3A and the communication between the terminal device 1 and the base station device 3B are each configured with different cells (serving cells). The base station device 3A uses a downlink frequency spectrum and an uplink frequency spectrum. The base station device 3B uses only the downlink frequency spectrum. The base station device 3A and the base station device 3B are connected by wire or wirelessly, and exchange control information, data, etc. For example, the control information is HARQ-ACK. The terminal device 1 makes an initial connection with the base station device 3A. After the connection with the base station device 3A is established, a connection with the base station device 3B is additionally established for the terminal device 1. A frequency spectrum used for communication is added to the terminal device 1. A cell (serving cell) used for communication is added to the terminal device 1.

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 a higher layer parameter.

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 length of the frame may be given regardless of the subcarrier spacing Δf. That is, the frame setting may be given regardless of μ. The length of the subframe 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 ascending order within the subframe in a range from 0 to N ^subframe,μ _slot −1. 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 ascending order within the frame in a range from 0 to N ^frame,μ _slot −1. N ^slot _symb consecutive OFDM symbols may be included in one slot. ^{N slot} _symb may be given based on at least a slot configuration and/or a part or all of a CP (Cyclic Prefix) configuration. The slot configuration may be given by at least a higher layer parameter tdd-UL-DL-ConfigurationCommon. The CP configuration may be given based at least on the higher layer parameter. The CP configuration may be given based at least on 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 μ, slot setting, and CP setting according to one aspect of the present embodiment. In Fig. 2A, when the slot setting is 0, the subcarrier interval setting μ is 2, and the CP setting is normal cyclic prefix (normal CP), N ^slot _symb = 14, N ^{frame, μ} _slot = 40, and N ^{subframe, μ} _slot = 4. 2B , when the slot setting is 0, the subcarrier spacing 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. N ^slot _symb in slot setting 0 may correspond to twice the N ^slot _symb in slot setting 1.

In the terminal device 1, a common subcarrier spacing setting, slot setting, and CP setting may be performed for each cell, or a different subcarrier spacing setting, slot setting, and CP setting may be performed for each cell. In the base station device 3A and the base station device 3B, a common subcarrier spacing setting, slot setting, and CP setting may be performed, or a different subcarrier spacing setting, slot setting, and CP setting may be performed.

Figure 3 is an example showing the configuration of a radio frame, a subframe, and a slot according to one aspect of this embodiment. In the example shown in Figure 3, the length of the slot is 0.5 ms, the length of the subframe is 1 ms, and the length of the radio frame is 10 ms. A slot may be a unit of resource allocation in the time domain. For example, a slot may be a unit to which one transport block is mapped. For example, a transport block may be mapped to one slot. Here, a transport block may be a unit of data transmitted within a predetermined interval (e.g., a transmission time interval (TTI)) defined in a higher layer (e.g., MAC: Medium Access Control, RRC: Radio Resource Control).

For example, the length of the slot may be given by the number of OFDM symbols. For example, the number of OFDM symbols may be 7 or 14. The length of the slot may be given based on at least the length of the OFDM symbol. The length of the OFDM symbol may differ based at least on the subcarrier spacing. The length of the OFDM symbol may also be given based at least on the number of points of the fast Fourier transform (FFT) used to generate the OFDM symbol. The length of the OFDM symbol may also include the length of a cyclic prefix (CP) added to the OFDM symbol. Here, the OFDM symbol may be referred to as a symbol. In addition, when a communication method other than OFDM is used in communication between the terminal device 1 and the base station device 3 (for example, when SC-FDMA or DFT-s-OFDM is used), the generated SC-FDMA symbol and/or DFT-s-OFDM symbol is also called an OFDM symbol. Furthermore, unless otherwise specified, OFDM includes SC-FDMA or DFT-s-OFDM.

For example, the length of the slot may be 0.125 ms, 0.25 ms, 0.5 ms, or 1 ms. For example, when the subcarrier spacing is 15 kHz, the length of the slot may be 1 ms. For example, when the subcarrier spacing is 30 kHz, the length of the slot may be 0.5 ms. For example, when the subcarrier spacing is 120 kHz, the length of the slot may be 0.125 ms. For example, when the subcarrier spacing is 15 kHz, the length of the slot may be 1 ms. For example, when the slot length is 0.125 ms, one subframe may be composed of eight slots. For example, when the slot length is 0.25 ms, one subframe may be composed of four slots. For example, when the slot length is 0.5 ms, one subframe may be composed of two slots. For example, when the slot length is 1 ms, one subframe may be composed of one slot.

Here, OFDM includes a multi-carrier communication method to which pulse shaping, PAPR reduction, out-of-band emission reduction, or filtering and/or phase processing (e.g., phase rotation, etc.) are applied. The multi-carrier communication method may be a communication method that generates/transmits a signal in which multiple subcarriers are multiplexed.

A radio frame may be given by the number of subframes. The number of subframes for a radio frame may be, for example, 10. A radio frame may be given by the number of slots.

In the terminal device 1, a common radio frame configuration, subframe configuration, and slot configuration may be set for each cell, or a different radio frame configuration, subframe configuration, and slot configuration may be set for each cell. In the base station device 3A and the base station device 3B, a common radio frame configuration, subframe configuration, and slot configuration may be set, or a different radio frame configuration, subframe configuration, and slot configuration may be set.

The physical resources are explained below.

Antenna ports are defined by the fact that the channel on which symbols are transmitted at one antenna port can be estimated from the channel on which other symbols are transmitted at the same antenna port. If the large scale property of the channel on which symbols are transmitted at one antenna port can be estimated from the channel on which symbols are transmitted at another antenna port, the two antenna ports are said to be Quasi Co-Location (QCL). The large scale property may include at least the long-range property of the channel. The large-scale characteristics may include at least some or all of 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 the beam parameters may be that a receiving beam assumed by the receiving side for the first antenna port is the same as a receiving beam assumed by the receiving side for the second antenna port. The first antenna port and the second antenna port are QCL with respect to the beam parameters may be that a transmitting beam assumed by the receiving side for the first antenna port is the same as a transmitting beam assumed by the receiving side for the second antenna port. The terminal device 1 may assume that the two antenna ports are QCL if 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 fact that the two antenna ports are 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. 4 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. 4, 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.

Figure 4 shows an example of a resource grid in one cell.

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 sets of the resource grid. That is, the terminal device 1 may be instructed to transmit and receive using some 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 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 signal may be dedicated RRC signaling. The dedicated RRC signaling may have at least some or all of the following features D1 to D2: Feature D1) Mapped to the DCCH logical channel Feature D2) Includes at least the 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 at least indicate 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 a Hybrid Automatic Repeat request ACKnowledgement (HARQ-ACK) corresponding to a channel state information (CSI), a scheduling request (SR), and a transport block (TB, MAC PDU, Medium Access Control Protocol Data Unit, DL-SCH, Downlink-Shared Channel, PDSCH, Physical Downlink Shared Channel). In addition, the uplink control information may include information that is not described above.

The HARQ-ACK may include at least a HARQ-ACK bit (HARQ-ACK information) 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 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 NACK corresponding to one Code Block Group (CBG) 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 a PUSCH resource for initial transmission is requested by the terminal device 1. The positive SR may indicate that a scheduling request is triggered by an upper layer. The positive SR may be transmitted when an 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 a PUSCH resource for initial transmission is not requested by the terminal device 1. A negative SR may indicate that no scheduling request is triggered by higher layers. A negative SR may be sent when no scheduling request is indicated to be sent 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 indicator related to the quality of the channel (e.g., propagation strength), and the PMI is an indicator indicating the precoder. The RI is an indicator indicating the transmission rank (or the number of transmission layers).

One or more PUCCH formats (PUCCH format 0 to PUCCH format 4) may be supported for the PUCCH. The PUCCH format may be mapped to the PUCCH and transmitted. The PUCCH format may be transmitted on the PUCCH. Transmission of the PUCCH format may mean that the PUCCH is transmitted.

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

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.

In addition, an uplink physical signal not described above may also be used.

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 one of a downlink grant (DL grant) or an uplink grant (UL 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 called a downlink assignment (DL assignment) or a downlink allocation (DL 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 1F.
1A) DCI Format Identifier Field
1B) Frequency domain resource assignment field
1C) Time Domain Resource Allocation Field
1D) Frequency hopping flag field
1E) MCS field (Modulation and Coding Scheme field)
1F) CSI request field

The DCI format specific field may be used at least to indicate to which of one or more DCI formats the DCI format containing 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 at least to indicate a modulation scheme and/or a part or all of 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.

The CSI request field is used at least to indicate the reporting of CSI. The size of the CSI request field may be a predetermined value. The size of the CSI request field may be 0, 1, 2, or 3.

DCI format 0_1 is configured to include at least some or all of 2A to 2H.
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) UL DAI field (downlink assignment index)

The UL DAI field is used at least to indicate the transmission status of the PDSCH. When a dynamic HARQ-ACK codebook is used, the size of the UL DAI field may be 2 bits. The UL DAI field indicates the size of the HARQ-ACK codebook transmitted on the PUSCH. The UL DAI field indicates the number of HARQ-ACKs included in the HARQ-ACK codebook transmitted on the PUSCH. The UL DAI field indicates the number of PDSCHs in which the corresponding HARQ-ACKs are included in the HARQ-ACK codebook transmitted on the PUSCH. The UL DAI field indicates the number of PDSCHs and SPS releases in which the corresponding HARQ-ACK is included in the HARQ-ACK codebook transmitted on the PUSCH.

The UL DAI field may indicate a value to which modulo arithmetic has been applied. An example in which the UL DAI field is 2 bits will be described. If the number of PDSCHs in which the corresponding HARQ-ACK is included in the HARQ-ACK codebook transmitted by the PUSCH is 0, the UL DAI field indicates "00". If the number of PDSCHs in which the corresponding HARQ-ACK is included in the HARQ-ACK codebook transmitted by the PUSCH is 1, the UL DAI field indicates "01". If the number of PDSCHs in which the corresponding HARQ-ACK is included in the HARQ-ACK codebook transmitted by the PUSCH is 2, the UL DAI field indicates "10". When the number of PDSCHs in which the corresponding HARQ-ACK is included in the HARQ-ACK codebook transmitted by the PUSCH is three, the UL DAI field is indicated as "11". When the number of PDSCHs in which the corresponding HARQ-ACK is included in the HARQ-ACK codebook transmitted by the PUSCH is four, the UL DAI field is indicated as "00". When the number of PDSCHs in which the corresponding HARQ-ACK is included in the HARQ-ACK codebook transmitted by the PUSCH is five, the UL DAI field is indicated as "01". When the number of PDSCHs in which the corresponding HARQ-ACK is included in the HARQ-ACK codebook transmitted by the PUSCH is six, the UL DAI field is indicated as "10". When the number of PDSCHs including the corresponding HARQ-ACK in the HARQ-ACK codebook transmitted by the PUSCH is 7, the UL DAI field indicates “11.” In this example, a modulo operation using the value “4” is performed on the number of PDSCHs including the corresponding HARQ-ACK in the HARQ-ACK codebook transmitted by the PUSCH.

The terminal device 1 interprets the UL DAI field taking into account the total number of received PDSCHs. For example, the terminal device 1 receives four PDSCHs and receives a UL DAI field indicating "00". In this case, the terminal device 1 interprets the number of PDSCHs in which the corresponding HARQ-ACK is included in the HARQ-ACK codebook transmitted by the PUSCH indicated by the UL DAI field as being four. For example, the terminal device 1 receives three PDSCHs and receives a UL DAI field indicating "00". In this case, the terminal device 1 interprets the number of PDSCHs in which the corresponding HARQ-ACK is included in the HARQ-ACK codebook transmitted by the PUSCH indicated by the UL DAI field as being four, and determines that reception of one PDSCH has been missed.

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 at least used 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 3H.
3A) DCI Format Identifier Field
3B) Frequency domain resource assignment field
3C) Time Domain Resource Allocation 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

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 a HARQ-ACK 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 a HARQ-ACK 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.

DCI format 1_1 is configured to include at least some or all of 4A to 4J.
4A) DCI Format Identifier Field
4B) Frequency domain resource assignment field
4C) Time Domain Resource Allocation 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

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

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

The downlink control information may include a slot format indicator (SFI). A pattern indicating whether each subframe (slot) in a plurality of subframes (slots) is an uplink subframe (slot), a downlink subframe (slot), or a flexible subframe (slot) may be transmitted and received using the downlink control information. The terminal device 1 may determine that a subframe (slot) not indicated by the received SFI is a flexible subframe (slot). When the transmission of a PUSCH is scheduled for a flexible subframe (slot) by a UL grant, the terminal device 1 processes the flexible subframe (slot) as an uplink subframe (slot). When the transmission of a PUSCH is not scheduled for a flexible subframe (slot) by a UL grant, the terminal device 1 monitors PDCCH candidates in the flexible subframe (slot) and performs a process of detecting a DL assignment. When reception of a PDSCH is scheduled by a DL assignment in a flexible subframe (slot), the terminal device 1 processes the flexible subframe (slot) as a downlink subframe (slot).

For example, downlink control information including a downlink grant or an uplink grant is transmitted and received on a PDCCH including a C-RNTI (Cell-Radio Network Temporary Identifier).

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 downlink grant is used at least for scheduling a PDSCH in the same slot as the slot in which the downlink grant is transmitted. The downlink grant may be used for scheduling a PDSCH in a slot different from the slot in which the downlink grant is transmitted. The uplink grant is used at least for scheduling one PUSH in one serving cell.

Note that various DCI formats may further include fields different from the above-mentioned fields. For example, a field (NFI: New Feedback Indicator field) indicating whether the HARQ-ACK information of the PDSCH is correctly detected may be included. A field (NFI field) indicating whether to erase (flush) the HARQ-ACK bit stored in a recording medium such as a memory may be included. A field (NFI field) indicating whether to include retransmission of the transmitted HARQ-ACK codebook may be included. A field (PGI: PDSCH Group ID field) indicating the PDSCH group to which the PDSCH scheduled by the DCI format belongs (linked) may be included. A field (RPGI: Request PDSCH Group ID field) indicating the PDSCH group to which the transmission of HARQ-ACK information is instructed may be included. A field indicating the cumulative number of transmitted PDCCHs (C-DAI: Counter Downlink Assignment Index field) may be included. A field indicating the total number of transmitted PDCCHs (T-DAI: Total Downlink Assignment Index field) may be included.

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 based at least on the DCI format used for scheduling the PDSCH. For example, a field indicating the PGI (PGI field) may be included in the DCI format. For example, a PDSCH group may be a set of PDSCHs having the same PGI (PDSCH group identifier). A PDSCH group may be one PDSCH or a set of one or more PDSCHs associated with the same PGI. The number of PDSCH groups set for the terminal device 1 may be 1, 2, 3, 4, or any other integer equal to or greater than 0.

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 corresponding to each PDSCH group in the form of a bitmap 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 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 sequence of higher layer parameters. The higher layer parameter may be the higher layer parameter dl-DataToUL-ACK. The 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 the DCI format in the sequence of higher layer parameters. For example, assuming that the sequence of higher layer parameters 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, the code point "000" of the PDSCH to HARQ feedback timing indication field may indicate that the value of K1 is 0, the code point "001" may indicate that the value of K1 is 1, and the code point "111" may indicate that the value of K1 is a non-numeric value. For example, assuming that the sequence of higher layer parameters is set to {non-numeric value, 0, 1, 2, 3, 4, 5, 15} and the number of bits in 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.

The HARQ-ACK bits (HARQ-ACK information) corresponding to the transport blocks transmitted and received in the downlink frequency band (frequency spectrum, carrier, component carrier) of base station device 3A are transmitted and received in the uplink frequency band (frequency spectrum, carrier, component carrier) of base station device 3A in the manner described above based on at least one of the various fields described above (PDSCH-to-HARQ feedback timing indicator field, HARQ indication field, PUCCH resource indication field, NFI field, PGI field, RPGI field, C-DAI field, T-DAI field, UL DAI field) contained in the DCI format.

The HARQ-ACK bit (HARQ-ACK information) corresponding to the transport block transmitted and received in the downlink frequency band (frequency spectrum, carrier, component carrier) of base station device 3B is transmitted and received using a periodic resource set in advance in the uplink frequency band (frequency spectrum, carrier, component carrier) of base station device 3A. Here, the timing (time resource) at which the HARQ-ACK bit (HARQ-ACK information) is transmitted and received is not indicated in the DCI format. Here, the frequency domain resource (resource block, code) at which the HARQ-ACK bit (HARQ-ACK information) is transmitted and received is not indicated in the DCI format. Here, the PDSCH group to which the HARQ-ACK bit (HARQ-ACK information) to be transmitted and received belongs is not indicated by the DCI format, and the HARQ-ACK bit (HARQ-ACK information) for each HARQ process of the downlink of the base station device 3B is transmitted and received in the uplink frequency band of the base station device 3A. The HARQ-ACK bit (HARQ-ACK information) corresponding to the transport block transmitted and received in the downlink frequency band of the base station device 3B is transmitted and received using a HARQ-ACK codebook consisting of HARQ-ACK bits corresponding to multiple HARQ processes. Every time this HARQ-ACK codebook is transmitted, the HARQ-ACK bit (HARQ-ACK information) for each HARQ-process held in the terminal device 1 is reset or flushed.

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: CONtrolREsource 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 be 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 contiguous resources (localized resources). The control resource set may be composed of discontinuous 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, which may include a bitmap for a group of resource blocks (RBG). The group of resource blocks may be given by six consecutive resource blocks.

The number of OFDM symbols constituting the control resource set may be given based at least on higher layer parameters. For example, the start positions of the OFDM symbols constituting the control resource set are notified from the base station device 3 to the terminal device 1 using higher layer signaling. For example, the end positions of the OFDM symbols constituting the control resource set are notified from the base station device 3 to the terminal device 1 using higher layer signaling.

A control resource set may be a common control resource set. The common control resource set may be a control resource set commonly set for a plurality of 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 configured 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 a part or all of the dedicated RRC signaling and the value of the C-RNTI. A plurality of 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.

A CCE may be configured to include one or more groups of REGs. A group of REGs is also referred to as a REG bundle. The number of REGs constituting one REG group is referred to as a bundle size. For example, the bundle size of a REG may be 1, 2, 3, or 6. In interleaved mapping, an interleaver may be applied on a REG bundle basis. The terminal device 1 may assume that the precoders applied to the REs in a group of REGs are the same. The terminal device 1 may perform channel estimation assuming that the precoders applied to the REs in a group of REGs are the same. On the other hand, the terminal device 1 may assume that the precoders applied to the REs between the groups of REGs are not the same. In other words, the terminal device 1 may not assume that the precoders applied to the REs between the groups of REGs are the same. “Between groups of REGs” may be rephrased as “between two different groups of REGs.” The terminal device 1 can perform channel estimation on the assumption that the precoders applied to the REs between the groups of REGs are not the same.

The set of PDCCH candidates monitored by the terminal device 1 is defined in terms of a search space. That is, the set of PDCCH candidates monitored by the terminal device 1 is given by the 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 number of CCEs constituting a PDCCH candidate is also referred to as an aggregation level (AL). When one PDCCH candidate is composed of an aggregation of multiple CCEs, one PDCCH candidate is composed of multiple CCEs with consecutive CCE numbers. A set of PDCCH candidates with an aggregation level of AL _X is also referred to as a search space of the aggregation level AL _X. That is, the search space of the aggregation level AL _X may be configured to include one or more PDCCH candidates with an aggregation level of AL _X. In addition, the search space may include PDCCH candidates of multiple aggregation levels. For example, a CSS may include PDCCH candidates of multiple aggregation levels. For example, a USS may include PDCCH candidates of multiple aggregation levels. A set of aggregation levels of PDCCH candidates included in a CSS and a set of aggregation levels of PDCCH candidates included in a USS may be specified/configured, respectively.

The terminal device 1 may monitor at least one or more search spaces in a slot 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 a slot 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.

The search space may have two types: CSS (Common Search Space) and USS (UE-specific Search Space). The CSS may be a search space set in common for multiple terminal devices 1. The USS may be a search space including settings used exclusively for individual terminal devices 1. The CSS may be given based on at least a synchronization signal, an MIB, first system information, second system information, common RRC signaling, dedicated RRC signaling, a cell ID, etc. The USS may be given based on at least a value of dedicated RRC signaling and/or a C-RNTI. The CSS may be a search space set in a resource (control resource element) common to multiple terminal devices 1. The USS may be a search space set in a resource (control resource element) for each individual terminal device 1.

The CSS may be a type 0 PDCCH CSS for a DCI format scrambled by an SI-RNTI used to transmit system information in a primary cell, and a type 1 PDCCH CSS for a DCI format scrambled by an RA-RNTI or TC-RNTI used for initial access. The CSS may be a type PDCCH CSS for a DCI format scrambled by a CC-RNTI used for unlicensed access. The terminal device 1 can monitor PDCCH candidates in those search areas. The DCI format scrambled by a specific RNTI may be a DCI format to which a CRC (Cyclic Redundancy Check) scrambled by a specific RNTI is added.

The information related to the reception of the PDCCH may include information related to an ID indicating the destination of the PDCCH. The ID indicating the destination of the PDCCH may be an ID used for scrambling the CRC bits added to the PDCCH. The ID indicating the destination of the PDCCH is also called RNTI (Radio Network Temporary Identifier). The information related to the reception of the PDCCH may include information related to an ID used for scrambling the CRC bits added to the PDCCH. The terminal device 1 can attempt to receive the PDCCH based at least on the information related to the ID included in the PBCH.

RNTI may include SI-RNTI (System Information - RNTI), P-RNTI (Paging - RNTI), C-RNTI (Common - RNTI), Temporary C-RNTI (TC-RNTI), RA-RNTI (Random Access - RNTI), CC-RNTI (Common Control - RNTI), and INT-RNTI (Interruption - RNTI). SI-RNTI is used at least for scheduling PDSCH transmitted including system information. P-RNTI is used at least for scheduling PDSCH transmitted including paging information and/or information such as a change notification of system information. The C-RNTI is used at least for scheduling user data for the RRC-connected terminal device 1. The Temporary C-RNTI is used at least for scheduling the random access message 4. The Temporary C-RNTI is used at least for scheduling the PDSCH including data mapped to the CCCH in the logical channel. The RA-RNTI is used at least for scheduling the random access message 2. The CC-RNTI is used at least for transmitting and receiving control information for unlicensed access. The INT-RNTI is used at least for indicating pre-emption in the downlink.

In addition, the PDCCH and/or DCI included in the CSS may not include a Carrier Indicator Field (CIF) indicating which serving cell (or which component carrier) the PDCCH/DCI is scheduling the PDSCH or PUSCH for.

In addition, when carrier aggregation (CA) is configured for terminal device 1, which aggregates multiple serving cells and/or multiple component carriers to communicate (transmit and/or receive), the PDCCH and/or DCI included in the USS for a specific serving cell (specific component carrier) may include a CIF indicating which serving cell and/or which component carrier the PDCCH/DCI is scheduling the PDSCH or PUSCH for.

In addition, when communication is performed using one serving cell and/or one component carrier for terminal device 1, the PDCCH and/or DCI included in the USS does not need to include a CIF indicating which serving cell and/or which component carrier the PDCCH/DCI is scheduling the PDSCH or PUSCH for.

The common control resource set may include a CSS. The common control resource set may include both a CSS and a USS. The dedicated control resource set may include a USS. The dedicated control resource set may include a CSS.

The physical resources of the search area are composed of control channel units (CCE: Control Channel Element). A CCE is composed of a predetermined number of resource element groups (REG: Resource Element Group). 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 Element). A PRB is also simply called an RB (Resource Block).

In other words, the terminal device 1 can detect the PDCCH and/or DCI for the terminal device 1 by blindly detecting PDCCH candidates included in a search space within a control resource set.

The number of blind detections for one control resource set in one serving cell and/or one component carrier may be determined based on the type of search area for the PDCCH included in the control resource set, the type of aggregation level, and the number of PDCCH candidates. Here, the type of search area may include at least one of CSS and/or USS and/or UGSS (UE Group SS) and/or GCSS (Group CSS). The type of aggregation level indicates the maximum aggregation level supported for the CCEs that constitute the search area, and may be specified/set from at least one of {1, 2, 4, 8, ..., X} (X is a predetermined value). The number of PDCCH candidates may indicate the number of PDCCH candidates for a certain aggregation level. In other words, the number of PDCCH candidates may be specified/set for each of multiple aggregation levels. In addition, the UGSS may be a search area commonly assigned to one or more terminal devices 1. The GCSS may be a search space to which DCI including parameters related to the CSS is mapped for one or more terminal devices 1. The aggregation level indicates an aggregation level of a predetermined number of CCEs and is related to the total number of CCEs constituting one PDCCH and/or search space.

In addition, the magnitude of the aggregation level may be associated with the coverage corresponding to the PDCCH and/or search area or the size of the DCI included in the PDCCH and/or search area (DCI format size, payload size).

In addition, when the start position (start symbol) of the PDCCH symbol is set for one control resource set, and when more than one PDCCH in the control resource set can be detected in a predetermined period, the type of search region for the PDCCH included in the control resource set, the type of aggregation level, and the number of PDCCH candidates may be set for the time region corresponding to each start symbol. The type of search region, the type of aggregation level, and the number of PDCCH candidates for the PDCCH included in the control resource set may be set for each control resource set, provided/set via DCI and/or higher layer signals (RRC signaling), or predefined/set by specifications. The number of PDCCH candidates may be the number of PDCCH candidates in a predetermined period. The predetermined period may be 1 millisecond. The predetermined period may be 1 microsecond. The predetermined period may be the period of one slot. The predetermined period may be the period of one OFDM symbol.

In addition, when there is more than one start position (start symbol) of the PDCCH symbol for one control resource set, that is, when there are multiple timings for blind detection (monitoring) of the PDCCH in a specified period, the type of search space for the PDCCH included in the control resource set, the type of aggregation level, and the number of PDCCH candidates may be set for the time domain corresponding to each start symbol. The type of search space for the PDCCH included in the control resource set, the type of aggregation level, and the number of PDCCH candidates may be set for each control resource set, provided/set via DCI and/or higher layer signals, or predefined/set by a specification.

In addition, as a method of indicating the number of PDCCH candidates, the number to be reduced from a predetermined number of PDCCH candidates may be specified/set for each aggregation level.

The terminal device 1 may transmit/notify the base station device 3 of capability information related to blind detection. The terminal device 1 may transmit/notify the base station device 3 of the number of PDCCH candidates that can be processed in one subframe as capability information related to PDCCH. The terminal device 1 may transmit/notify the base station device 3 of capability information related to blind detection when more than a predetermined number of control resource sets can be set for one or more serving cells/component carriers.

The terminal device 1 may transmit/notify capability information related to blind detection to the base station device 3 when more than a specified number of control resource sets can be configured for a specified period of one or more serving cells/component carriers.

The capability information related to the blind detection may include information indicating the maximum number of blind detections in a predetermined period. The capability information related to the blind detection may include information indicating that PDCCH candidates can be reduced. The capability information related to the blind detection may include information indicating the maximum number of control resource sets that can be blind detected in a predetermined period. The maximum number of control resource sets and the maximum number of serving cells and/or component carriers that can monitor the PDCCH may be set as individual parameters or as common parameters. The capability information related to the blind detection may include information indicating the maximum number of control resource sets that can be simultaneously blind detected in a predetermined period.

If the terminal device 1 does not support the capability to detect (blind detection) more than a predetermined number of control resource sets in a predetermined period, the terminal device 1 may not transmit/notify capability information related to the blind detection. If the base station device 3 does not receive capability information related to the blind detection, the base station device 3 may configure the control resource set so as not to exceed the predetermined number for blind detection, and transmit the PDCCH.

The settings for the control resource set include a parameter indicating an index (ControlResourceSetId) that identifies the control resource set. The settings for the control resource set may also include a parameter indicating the frequency resource region of the control resource set (the number of resource blocks constituting the control resource set). The settings for the control resource set may also include a parameter indicating the type of mapping from CCE to REG. The settings for the control resource set may also include a REG bundle size. RRC signaling may be used to transmit and receive a message indicating the settings for the control resource set. A SIB may be used to transmit and receive a message indicating the settings for the control resource set. A MIB may be used to transmit and receive a message indicating the settings for the control resource set.

The search area setting includes a parameter indicating an index (search area index) for identifying the search area. The search area setting includes a parameter indicating an index of a control resource set in which the search area is arranged. The search area setting may include a parameter indicating a period and an offset of a slot in which the search area is arranged. The search area setting may include a parameter indicating the number of slots in which the search area is consecutively arranged. The search area setting may include a parameter indicating an OFDM symbol in a slot in which the PDCCH candidates are monitored. The search area setting may include a parameter indicating the number of PDCCH candidates in which monitoring is performed for each CCE aggregation level. The search area setting may include a parameter indicating a DCI format in which monitoring is performed. The search area setting may include a parameter indicating a type of the search area (CSS or USS). RRC signaling may be used to transmit and receive a message indicating the search area setting. A SIB may be used to transmit and receive a message indicating the search area setting. A MIB may be used to transmit and receive a message indicating the search area setting.

The PDSCH is used at least to transmit/receive transport blocks. The PDSCH may be used at least to transmit/receive a random access message 2 (random access response). The PDSCH may be used at least to transmit/receive 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.

The DL DMRS is related to the transmission of the PBCH, the PDCCH, and/or the PDSCH. The DL DMRS is multiplexed onto the PBCH, the PDCCH, and/or the PDSCH. The terminal device 1 may use the DL DMRS corresponding to the PBCH, the PDCCH, or the PDSCH to perform propagation path correction of the PBCH, the PDCCH, or the PDSCH. The terminal device 1 may determine that the base station device 3 is transmitting a signal based on detection of the DL DMRS.

The CSI-RS may be a signal used at least to calculate channel state information. The CSI-RS pattern assumed by the terminal device 1 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 1 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.

In addition, downlink physical signals not described above may also be used.

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, the transport block is mapped to a codeword, and modulation processing is performed for each codeword.

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. Herein, the RRC signaling and/or the 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/received using signaling common to multiple terminal devices 1 in the serving cell or signaling dedicated to a certain terminal device 1. UE-specific higher layer parameters may be transmitted/received using signaling dedicated to 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/receive MIB. CCCH (Common Control CHannel) is an upper layer channel used to transmit/receive common information in 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 used at least to transmit/receive control information (dedicated control information) dedicated to terminal device 1. Here, the DCCH may be used, for example, for a terminal device 1 that is 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.

Figure 5 is a diagram showing an example of the configuration of one REG according to one aspect of the present embodiment. The REG may be configured by one OFDM symbol of one PRB. That is, the REG may be configured by 12 consecutive REs in the frequency domain. Some of the REs constituting the REG may be REs to which downlink control information is not mapped. The REG may be configured to include REs to which downlink control information is not mapped, or may be configured without including REs to which downlink control information is not mapped. The RE to which downlink control information is not mapped may be an RE to which a reference signal is mapped, an RE to which a channel other than the control channel is mapped, or an RE to which the terminal device 1 assumes that the control channel is not mapped.

Figure 6 is a diagram showing an example of the configuration of a CCE according to one aspect of this embodiment. A CCE may be composed of six REGs. As shown in Figure 6 (a), a CCE (CCE #0) may be composed of REGs that are continuously mapped (such mapping may be called localized mapping) (such mapping may be called non-interleaved CCE-to-REG mapping) (such mapping may be called non-interleaved mapping). It is not necessary that all REGs constituting a CCE are continuous in the frequency domain. For example, when all of the multiple resource blocks constituting a control resource set are not continuous in the frequency domain, even if the numbers assigned to the REGs are continuous, the resource blocks constituting each REG with consecutive numbers are not continuous in the frequency domain. When a control resource set is composed of multiple OFDM symbols and multiple REGs constituting one CCE are arranged across multiple time intervals (OFDM symbols), a CCE (CCE #1) may be composed of a group of REGs that are continuously mapped, as shown in FIG. 6(b).

As shown in FIG. 6(c), a CCE (CCE#2) may be configured with REGs that are non-contiguously mapped (such mapping may be referred to as distributed mapping) (such mapping may be referred to as interleaved CCE-to-REG mapping) (such mapping may be referred to as interleaved mapping). REGs that constitute a CCE may be non-contiguously mapped to time-frequency resources using an interleaver. When a control resource set is configured with multiple OFDM symbols and multiple REGs that constitute one CCE are arranged across multiple time intervals (OFDM symbols), as shown in FIG. 6(d), a CCE (CCE#3) may be configured with REGs that are non-contiguously mapped by mixing REGs of different time intervals (OFDM symbols). As shown in Fig. 6(e), CCE (CCE #4) may be composed of REGs that are distributed and mapped in groups of multiple REGs. As shown in Fig. 6(f), CCE (CCE #5) may be composed of REGs that are distributed and mapped in groups of multiple REGs.

Figure 7 is a diagram showing an example of REGs constituting a PDCCH candidate according to one aspect of the present embodiment and the number of REGs constituting a group of REGs. In the example shown in Figure 7 (a), a PDCCH candidate is mapped to one OFDM symbol, and three REG groups (REG groups) each including two REGs are configured. That is, in the example shown in Figure 7 (a), one REG group is composed of two REGs. The number of REGs constituting a group of REGs in the frequency domain may include a divisor of the number of PRBs mapped in the frequency direction. In the example shown in Figure 7 (a), the number of REGs constituting a group of REGs in the frequency domain may be 1, 2, 3, or 6.

In the example shown in FIG. 7(b), the PDCCH candidates are mapped to two OFDM symbols, and three REG groups each including two REGs are configured. In the example shown in FIG. 7(b), the number of REGs constituting the frequency domain REG group may be either 1 or 3.

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

Figure 8 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 includes a radio transmission/reception unit 10 and an upper layer processing unit 14. The radio transmission/reception unit 10 includes at least an antenna unit 11, an RF (Radio Frequency) unit 12, and a part or all of a baseband unit 13. The upper layer processing unit 14 includes at least a medium access control layer processing unit 15, and a part or all of a radio resource control layer processing unit 16. The radio transmission/reception unit 10 is also referred to as a transmitting unit, a receiving unit, or a physical layer processing unit.

The physical layer processing unit includes a decoding unit. The receiving unit (also referred to as the receiving processing unit) of the terminal device 1 receives the PDCCH. The decoding unit of the terminal device 1 decodes the received PDCCH. More specifically, the decoding unit of the terminal device 1 performs blind decoding processing on the received signal of the resource corresponding to the USS PDCCH candidate. The decoding unit of the terminal device 1 performs blind decoding processing on the received signal of the resource corresponding to the CSS PDCCH candidate. The receiving processing unit of the terminal device 1 monitors the PDCCH candidates within the control resource set. The receiving processing unit of the terminal device 1 monitors the PDCCH candidates within the control resource set.

The reception processing unit of the terminal device 1 monitors PDCCH candidates within a control resource set of a downlink frequency band (cell, component carrier, carrier) managed by the base station device 3A. The reception processing unit of the terminal device 1 monitors PDCCH candidates within a control resource set of a downlink frequency band (cell, component carrier, carrier) managed by the base station device 3B. The reception unit of the terminal device 1 receives the PDSCH. The reception processing unit of the terminal device 1 performs processing to receive the PDSCH in the downlink frequency band (cell, component carrier, carrier) managed by the base station device 3A. The reception processing unit of the terminal device 1 performs processing to receive the PDSCH in the downlink frequency band (cell, component carrier, carrier) managed by the base station device 3B. The reception processing unit of the terminal device 1 performs processing such as demodulation and decoding on the PDSCH.

The transmission unit (also referred to as the transmission processing unit) of the terminal device 1 transmits a HARQ-ACK. The transmission processing unit of the terminal device 1 transmits a HARQ-ACK for the PDSCH. The transmission processing unit of the terminal device 1 transmits a HARQ-ACK in an uplink frequency band (cell, component carrier, carrier) managed in the base station device 3A. The transmission processing unit of the terminal device 1 transmits a HARQ-ACK for the PDSCH in a downlink frequency band (cell, component carrier, carrier) managed in the base station device 3A, and a HARQ-ACK for the PDSCH in a downlink frequency band (cell, component carrier, carrier) managed in the base station device 3B. The transmission processing unit of the terminal device 1 transmits a HARQ-ACK for the PDSCH of the downlink frequency band (cell, component carrier, carrier) managed by the base station device 3A and a HARQ-ACK for the PDSCH of the downlink frequency band (cell, component carrier, carrier) managed by the base station device 3B, in an uplink frequency band (cell, component carrier, carrier) managed by the base station device 3A. The transmission processing unit of the terminal device 1 transmits a HARQ-ACK for the PDSCH of the downlink frequency band (cell, component carrier, carrier) managed by the base station device 3A by a first method, and transmits a HARQ-ACK for the PDSCH of the downlink frequency band (cell, component carrier, carrier) managed by the base station device 3B by a second method.

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 radio resource control layer processing unit 16 sets a control resource set based on the RRC signaling received from the base station device 3. The radio resource control layer processing unit 16 sets a search space within the control resource set. The radio resource control layer processing unit 16 sets PDCCH candidates to be monitored within the control resource set. The radio resource control layer processing unit 16 sets the number of PDCCH candidates to be monitored within the control resource set. The radio resource control layer processing unit 16 sets the aggregation level of the PDCCH candidates to be monitored within the control resource set.

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 into a time-continuous signal) 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.

The terminal device 1 receives a PDCCH. The terminal device 1 receives a PDSCH. The radio resource control layer processing unit 16 sets a control resource set. The radio resource control layer processing unit 16 sets a search space. The radio resource control layer processing unit 16 sets a control resource set based on RRC signaling. The radio resource control layer processing unit 16 sets a search space based on RRC signaling. The receiving unit of the terminal device 1 monitors multiple PDCCH candidates within the search space of the set control resource set. The receiving unit of the terminal device 1 monitors multiple PDCCH candidates within the search space of the set control resource set in a certain slot. The decoding unit of the terminal device 1 decodes the monitored PDCCH candidates. The decoding unit of the terminal device 1 decodes the received PDSCH.

The receiver of the terminal device 1 monitors a number of PDCCH candidates set based on RRC signaling within a search area of a control resource set in a certain slot. The receiver of the terminal device 1 monitors PDCCH candidates consisting of one or more OFDM symbols set based on RRC signaling within a search area of a control resource set in a certain slot. The receiver of the terminal device 1 monitors PDCCH candidates in a search area in the first half of a slot (e.g., the first OFDM symbol, or the first and second OFDM symbols, or the first, second and third OFDM symbols) in a certain slot. The receiving unit of the terminal device 1 monitors PDCCH candidates in a search area in the first half of a slot (e.g., the first OFDM symbol, or the first and second OFDM symbols, or the first, second and third OFDM symbols) and monitors PDCCH candidates in a search area in the second half of the slot (e.g., the eighth OFDM symbol, or the eighth and ninth OFDM symbols, or the eighth, ninth and tenth OFDM symbols). Note that the receiving unit of the terminal device 1 may set three or more search areas in a slot, each of which is a search area of a different OFDM symbol, and monitor PDCCH candidates in a further distributed manner within the slot.

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

Figure 5 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 is also referred to as a transmitting unit, a receiving unit, or a physical layer processing 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 radio resource control layer processing unit 36 sets a control resource set for the terminal device 1. Multiple PDCCH candidates are configured (set) within the set control resource set. The radio resource control layer processing unit 36 sets a search space for the terminal device 1.

The radio resource control layer processing unit 36 sets resources for transmitting HARQ-ACK to the terminal device 1. The radio resource control layer processing unit 36 of the base station device 3A sets resources for transmitting HARQ-ACK for the PDSCH of the downlink frequency band (cell, component carrier, carrier) managed in the base station device 3B. The radio resource control layer processing unit 36 of the base station device 3A sets resources for transmitting HARQ-ACK for the PDSCH of the downlink frequency band (cell, component carrier, carrier) managed in the base station device 3B to the uplink frequency band (cell, component carrier, carrier) managed in the base station device 3A.

The functions of the radio transmission/reception unit 30 are similar to those of the radio transmission/reception unit 10, so the description will be omitted as appropriate. The radio transmission/reception unit 30 also grasps the SS (search space) configured in the terminal device 1. The radio transmission/reception unit 30 grasps the search space in the control resource set configured in the terminal device 1. The radio transmission/reception unit 30 grasps the PDCCH candidates monitored in the terminal device 1 and grasps the search space. The radio transmission/reception unit 30 grasps which control channel element each PDCCH candidate monitored in the terminal device 1 is composed of (knows the number of the control channel element in which the PDCCH candidate is composed). The radio transmission/reception unit 30 includes an SS grasping unit, and the SS grasping unit grasps the SS configured in the terminal device 1. The SS grasping unit grasps one or more PDCCH candidates in the control resource set configured as the search space of the terminal device. The SS grasping unit grasps the PDCCH candidates (the number of PDCCH candidates, the numbers of the PDCCH candidates) configured in the search area of the control resource set of the terminal device 1.

The SS grasping unit grasps the configuration of the search area within the control resource set (the number of PDCCH candidates, the OFDM symbols of the PDCCH candidates, and the aggregation level of the PDCCH candidates). The transmitting unit of the wireless transceiver unit 30 transmits the PDCCH to the terminal device 1 using the PDCCH candidates within the search area of the control resource set.

The SS grasping unit may grasp that the configuration of the search area of a certain slot is such that one or more PDCCH candidates are composed of OFDM symbols in the first half of the slot (e.g., the first OFDM symbol, or the first and second OFDM symbols, or the first, second and third OFDM symbols). The SS grasping unit may grasp that the configuration of the search area of a certain slot is such that one or more PDCCH candidates are composed of OFDM symbols in the first half of the slot (e.g., the first OFDM symbol, or the first and second OFDM symbols, or the first, second and third OFDM symbols), and one or more PDCCH candidates are composed of OFDM symbols in the second half of the slot (e.g., the eighth OFDM symbol, or the eighth and ninth OFDM symbols, or the eighth, ninth and tenth OFDM symbols). The SS grasping unit may grasp that three or more search areas are composed of different OFDM symbol search areas in a certain slot.

The receiving unit (also referred to as the receiving processing unit) of base station device 3 receives the HARQ-ACK. The receiving processing unit of base station device 3 receives the HARQ-ACK for the PDSCH. The receiving processing unit of base station device 3 (base station device 3A) receives the HARQ-ACK in the uplink frequency band (cell, component carrier, carrier). The receiving processing unit of base station device 3A receives the HARQ-ACK for the PDSCH in the downlink frequency band (cell, component carrier, carrier) managed by base station device 3A, and the HARQ-ACK for the PDSCH in the downlink frequency band (cell, component carrier, carrier) managed by base station device 3B. The reception processing unit of the base station device 3A receives HARQ-ACK for the PDSCH of the downlink frequency band (cell, component carrier, carrier) managed by the base station device 3A and HARQ-ACK for the PDSCH of the downlink frequency band (cell, component carrier, carrier) managed by the base station device 3B, in the uplink frequency band (cell, component carrier, carrier) managed by the base station device 3A. The reception processing unit of the base station device 3A receives HARQ-ACK for the PDSCH of the downlink frequency band (cell, component carrier, carrier) managed by the base station device 3A by a first method, and receives HARQ-ACK for the PDSCH of the downlink frequency band (cell, component carrier, carrier) managed by the base station device 3B by a second method.

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 transmits uplink control information (UCI) to the base station device 3. The terminal device 1 may multiplex the UCI onto the PUCCH and transmit it. The terminal device 1 may multiplex the 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 a Hybrid Automatic Repeat request ACKnowledgement (HARQ-ACK) for downlink data (Transport block, Medium Access Control Protocol Data Unit (MAC PDU), Downlink-Shared Channel (DL-SCH), Physical Downlink Shared Channel (PDSCH)).

HARQ-ACK may also be referred to as ACK/NACK, HARQ feedback, HARQ-ACK feedback, HARQ response, HARQ-ACK response, HARQ information, HARQ-ACK information, HARQ control information, and HARQ-ACK control information.

If the downlink data is successfully decoded, an ACK for the downlink data is generated. If the downlink data is not successfully decoded, a NACK for the downlink data is generated. The HARQ-ACK 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 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.

HARQ control for one transport block may be referred to as a HARQ process. One HARQ process identifier may be given for each HARQ process. The DCI format includes a field indicating the HARQ process identifier.

NDI (New Data Indicator) is indicated in the DCI format for each HARQ process. For example, the NDI field is included in the DCI format (DL assignment) including the scheduling information of the PDSCH. The NDI field is 1 bit. The terminal device 1 stores (stores) the value of NDI for each HARQ process. The base station device 3 stores (stores) the value of NDI for each HARQ process for each terminal device 1. The terminal device 1 updates the stored NDI value using the NDI field of the detected DCI format. The base station device 3 sets the updated NDI value or the non-updated NDI value in the NDI field of the DCI format and transmits it to the terminal device 1. The terminal device 1 updates the stored NDI value using the NDI field of the detected DCI format for the HARQ process corresponding to the value of the HARQ process identifier field of the detected DCI format.

The terminal device 1 determines whether the received transport block is a new transmission or a retransmission based on the value of the NDI field of the DCI format (DL assignment). The terminal device 1 compares the previously received NDI value for a transport block of a certain HARQ process, and if the value of the detected NDI field of the DCI format is toggled, determines that the received transport block is a new transmission. When the base station device 3 transmits a transport block of a new transmission in a certain HARQ process, it toggles the value of the NDI stored for the HARQ process and transmits the toggled NDI to the terminal device 1. When the base station device 3 transmits a transport block of a retransmission in a certain HARQ process, it does not toggle the value of the NDI stored for the HARQ process and transmits the non-toggled NDI to the terminal device 1. The terminal device 1 compares the value of the NDI field of the detected DCI format with the previously received NDI value for a transport block of a certain HARQ process, and if the value of the NDI field of the detected DCI format has not been toggled (is the same), determines that the received transport block is a retransmission. Note that toggling here means switching to a different value.

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

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

dl-DataToUL-ACK indicates a list of timings of HARQ-ACK for PDSCH. The timing is the number of slots between the slot in which PDSCH is received (or the slot containing the last OFDM symbol to which PDSCH is mapped) and the slot in which HARQ-ACK for the received PDSCH is transmitted. For example, dl-DataToUL-ACK is a list of 1, 2, 3, 4, 5, 6, 7, or 8 timings. If dl-DataToUL-ACK is a list of 1 timing, the HARQ indication field is 0 bits. If dl-DataToUL-ACK is a list of 2 timings, the HARQ indication field is 1 bit. If dl-DataToUL-ACK is a list of 3 or 4 timings, the HARQ indication field is 2 bits. When dl-DataToUL-ACK is a list of 5, 6, 7, or 8 timings, the HARQ indication field is 3 bits. For example, dl-DataToUL-ACK is composed of a list of timings having any value in the range from 0 to 31. For example, dl-DataToUL-ACK is composed of a list of timings having any value in the range from 0 to 63.

The size of the dl-DataToUL-ACK is defined as the number of elements that the dl-DataToUL-ACK contains. The size of the dl-DataToUL-ACK may be referred to as L _para . The index of the dl-DataToUL-ACK indicates the order (number) of the elements of the dl-DataToUL-ACK. For example, if the size of the dl-DataToUL-ACK is 8 (L _para =8), the index of the dl-DataToUL-ACK is any value of 1, 2, 3, 4, 5, 6, 7, or 8. The index of the dl-DataToUL-ACK may be given, indicated, or indicated by the value indicated by the HARQ indication field.

The terminal device 1 may set the size of the HARQ-ACK codebook according to the size of the dl-DataToUL-ACK. For example, if the dl-DataToUL-ACK consists of eight elements, the size of the HARQ-ACK codebook is 8. For example, if the dl-DataToUL-ACK consists of two elements, the size of the HARQ-ACK codebook is 2. Each HARQ-ACK information constituting the HARQ-ACK codebook is HARQ-ACK information for PDSCH reception at each slot timing of the dl-DataToUL-ACK. This type of HARQ-ACK codebook is also called a semi-static HARQ-ACK codebook.

An example of the setting of the HARQ indication field is explained below. For example, dl-DataToUL-ACK is composed of a list of eight timings: 0, 7, 15, 23, 31, 39, 47, and 55, and the HARQ indication field is composed of three bits. The HARQ indication field of "000" corresponds to the first 0 in the list of dl-DataToUL-ACK as the corresponding timing. In other words, the HARQ indication field of "000" corresponds to the value 0 indicated by the index 1 of dl-DataToUL-ACK. The HARQ indication field of "001" corresponds to the second 7 in the list of dl-DataToUL-ACK as the corresponding timing. The HARQ indication field of "010" corresponds to the third 15 in the list of dl-DataToUL-ACK as the corresponding timing. The HARQ indication field "011" corresponds to the fourth 23 in the list of dl-DataToUL-ACK as the corresponding timing. The HARQ indication field "100" corresponds to the fifth 31 in the list of dl-DataToUL-ACK as the corresponding timing. The HARQ indication field "101" corresponds to the sixth 39 in the list of dl-DataToUL-ACK as the corresponding timing. The HARQ indication field "110" corresponds to the seventh 47 in the list of dl-DataToUL-ACK as the corresponding timing. The HARQ indication field "111" corresponds to the eighth 55 in the list of dl-DataToUL-ACK as the corresponding timing. When the received HARQ indication field indicates "000", the terminal device 1 transmits the corresponding HARQ-ACK in the 0th slot from the slot of the received PDSCH. When the received HARQ indication field indicates "001", the terminal device 1 transmits the corresponding HARQ-ACK in the 7th slot from the slot of the received PDSCH. When the received HARQ indication field indicates "010", the terminal device 1 transmits the corresponding HARQ-ACK in the 15th slot from the slot of the received PDSCH. When the received HARQ indication field indicates "011", the terminal device 1 transmits the corresponding HARQ-ACK in the 23rd slot from the slot of the received PDSCH. When the received HARQ indication field indicates "100", the terminal device 1 transmits the corresponding HARQ-ACK in the 31st slot from the slot of the received PDSCH. When the received HARQ indication field indicates "101", the terminal device 1 transmits the corresponding HARQ-ACK in the 39th slot from the slot of the received PDSCH. If the received HARQ indication field indicates "110", the terminal device 1 transmits the corresponding HARQ-ACK in the 47th slot from the slot of the received PDSCH. If the received HARQ indication field indicates "111", the terminal device 1 transmits the corresponding HARQ-ACK in the 55th slot from the slot of the received PDSCH.

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

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

The terminal device 1 determines a set of multiple opportunities for one or more candidate PDSCH receptions, for transmitting corresponding HARQ-ACK information on the PUCCH of a certain slot. The terminal device 1 determines multiple slots of slot timing K1 included in dl-DataToUL-ACK as multiple opportunities for candidate PDSCH reception. K1 may be a set of k. For example, when dl-DataToUL-ACK is (1, 2, 3, 4, 5, 6, 7, 8), in the PUCCH of slot n, HARQ-ACK information is transmitted for PDSCH reception of slot n-1, PDSCH reception of slot n-2, PDSCH reception of slot n-3, PDSCH reception of slot n-4, PDSCH reception of slot n-5, PDSCH reception of slot n-6, PDSCH reception of slot n-7, and PDSCH reception of slot n-8. When the terminal device 1 actually receives a PDSCH in a slot corresponding to the reception of a candidate PDSCH, it sets ACK or NACK as the HARQ-ACK information based on the transport block contained in that PDSCH, and when the terminal device 1 does not receive a PDSCH in the slot corresponding to the reception of a candidate PDSCH, it sets NACK as the HARQ-ACK information.

The HARQ indication field included in the DCI format received on the PDCCH in slot n-1 indicates 1. The HARQ indication field included in the DCI format received on the PDCCH in slot n-2 indicates 2. The HARQ indication field included in the DCI format received on the PDCCH in slot n-3 indicates 3. The HARQ indication field included in the DCI format received on the PDCCH in slot n-4 indicates 4. The HARQ indication field included in the DCI format received on the PDCCH in slot n-5 indicates 5. The HARQ indication field included in the DCI format received on the PDCCH in slot n-6 indicates 6. The HARQ indication field included in the DCI format received on the PDCCH in slot n-7 indicates 7. The HARQ indication field included in the DCI format received in the PDCCH of slot n-8 indicates 8.

Based on the slot in which the PDCCH was received and the value of the HARQ indication field included in the received DCI format, the terminal device 1 determines the slot in which to transmit HARQ-ACK information and the set of multiple candidate PDSCH reception slots corresponding to that HARQ-ACK information. For example, if dl-DataToUL-ACK is (1, 2, 3, 4, 5, 6, 7, 8), the terminal device 1 receives the PDCCH in slot m, and the HARQ indication field included in the DCI format indicates 4. The terminal device 1 determines to transmit HARQ-ACK information in slot (m+4). The terminal device 1 determines that the other HARQ-ACK information transmitted in slot (m+4) is HARQ-ACK information for PDSCH reception in slot (m+(1-4)), HARQ-ACK information for PDSCH reception in slot (m+(2-4)), HARQ-ACK information for PDSCH reception in slot (m+(3-4)), HARQ-ACK information for PDSCH reception in slot (m+(5-4)), HARQ-ACK information for PDSCH reception in slot (m+(6-4)), HARQ-ACK information for PDSCH reception in slot (m+(7-4)), and HARQ-ACK information for PDSCH reception in slot (m+(8-4)).

The dl-DataToUL-ACK can be configured not only as a value indicating the number of slots as the timing of the HARQ-ACK, but also as a value (information) indicating that the HARQ-ACK is to be held. When the terminal device 1 receives a HARQ indication field indicating a value indicating that the HARQ-ACK is to be held in the PDCCH, the terminal device 1 holds the HARQ-ACK (HARQ-ACK information) for the PDSCH scheduled in that PDCCH, and waits to transmit the HARQ-ACK (HARQ-ACK information).

In the above, the Semi-static HARQ-ACK codebook has been described as a type of HARQ-ACK codebook, but a different type of HARQ-ACK codebook may be used. A type of HARQ-ACK codebook called a Dynamic HARQ-ACK codebook will be described.

The HARQ-ACK codebook corresponding to a certain PDSCH group is given 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 is given based on at least a set of monitoring occasions for PDCCH and some or all of the value of the counter DAI field. The HARQ-ACK codebook may be further given based on the value of the UL DAI field. The HARQ-ACK codebook may be further given based on the value of the DAI field. The HARQ-ACK codebook may be further given based on the value of the total DAI field.

The HARQ-ACK codebook size of the Dynamic HARQ-ACK codebook is based on a field in the DCI format. The size of the HARQ-ACK codebook may be set based on the value of the counter DAI field of the last received DCI format. The counter DAI field indicates the cumulative number of PDSCHs or transport blocks scheduled until reception of the corresponding DCI format. The size of the HARQ-ACK codebook may be set based on the value of the total DAI field of the DCI format. The total DAI field indicates the total number of PDSCHs or transport blocks scheduled until transmission of the HARQ-ACK codebook.

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.

If a DCI format detected in a monitoring opportunity of any search space set corresponding to a monitoring opportunity of a certain PDCCH triggers (includes triggering information) to transmit 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 (does not include triggering information) to transmit 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 Counter DAI indicates the cumulative number of PDCCHs (or a value at least related to the cumulative number) detected up to a monitoring opportunity of a PDCCH in a serving cell in M PDCCH monitoring opportunities for a certain PDCCH monitoring opportunity in the serving cell. The Counter DAI may also be referred to as C-DAI. The C-DAI corresponding to a PDSCH may be indicated by a field included in a DCI format used for scheduling the PDSCH. The Total DAI may indicate the cumulative number of PDCCHs (or a value at least related to the cumulative number) detected up to a monitoring opportunity m of a PDCCH in M PDCCH monitoring opportunities. The Total DAI may be referred to as T-DAI (Total Downlink Assignment Index).

A Semi-static HARQ-ACK codebook (Type 1 HARQ-ACK codebook) or a Dynamic HARQ-ACK codebook (Type 2 HARQ-ACK codebook) is a HARQ-ACK codebook whose transmission is instructed (triggered, requested) based on a DL assignment. The DCI format that includes the HARQ indication field is a DL assignment (Downlink assignment). The DL assignment is a DCI format used for scheduling the PDSCH. The DL assignment is a DCI format used for allocating the PDSCH. The semi-static HARQ-ACK codebook is configured based on the dl-DataToUL-ACK and HARQ indication fields. The size of the semi-static HARQ-ACK codebook is based on the size included in the dl-DataToUL-ACK. The timing of the slots included in the semi-static HARQ-ACK codebook or the dynamic HARQ-ACK codebook is based on the value of the HARQ indication field and the slot in which the DCI including the HARQ indication field was received.

The Dynamic HARQ-ACK codebook or Semi-static HARQ-ACK codebook is the first method for transmitting and receiving HARQ-ACK. The first method is used for transmitting and receiving HARQ-ACK for PDSCH of the downlink frequency band (cell, component carrier, carrier) managed in base station device 3A. The second method is used for transmitting and receiving HARQ-ACK for PDSCH of the downlink frequency band (cell, component carrier, carrier) managed in base station device 3B.

The HARQ-ACK codebook of the second method includes HARQ-ACK information for a plurality of HARQ processes. For example, the HARQ process means the HARQ process used for the PDSCH. For example, the number of HARQ processes that can be used in one serving cell (a downlink cell managed in the base station device 3B) is 16. For example, the number of HARQ processes means a plurality of HARQ processes configured by RRC signaling. For example, the number of the plurality of HARQ processes is 8. For example, the number of the plurality of HARQ processes is 10. For example, 16 HARQ processes (HARQ process 0, HARQ process 1, HARQ
HARQ process 2, HARQ process 3, HARQ process 4, HARQ process 5, HARQ process 6, HARQ process 7, HARQ process 8, HARQ process 9, HARQ process 10, HARQ process 11, HARQ process 12, HARQ process 13, HARQ process 14, and HARQ process 15) are divided into two sets (first set and second set). One HARQ-ACK codebook is configured by the HARQ-ACK for each HARQ process in each set. For example, the first set of HARQ processes is HARQ process 0, HARQ process 1, HARQ process 2, HARQ process 3, HARQ process 4, HARQ process 5, HARQ process 6, and HARQ process 7. For example, the second set of HARQ processes is HARQ process 8, HARQ process 9, HARQ process 10, HARQ process 11, HARQ process 12, HARQ process 13, HARQ process 14, and HARQ process 15.

An example of one HARQ-ACK codebook for the second method will be described. A case where HARQ-ACK is configured for eight HARQ processes (HARQ process 0, HARQ process 1, HARQ process 2, HARQ process 3, HARQ process 4, HARQ process 5, HARQ process 6, HARQ process 7) will be described. When one transport block is transmitted and received for each HARQ process in the downlink cell of the base station device 3B, one bit of HARQ-ACK is used for each HARQ process. One HARQ-ACK codebook is configured with a total of 8 bits: 1 bit of HARQ-ACK for HARQ process 0, 1 bit of HARQ-ACK for HARQ process 1, 1 bit of HARQ-ACK for HARQ process 2, 1 bit of HARQ-ACK for HARQ process 3, 1 bit of HARQ-ACK for HARQ process 4, 1 bit of HARQ-ACK for HARQ process 5, 1 bit of HARQ-ACK for HARQ process 6, and 1 bit of HARQ-ACK for HARQ process 7. When two transport blocks are transmitted and received for each HARQ process in the downlink cell of the base station device 3B, a 2-bit HARQ-ACK is used for each HARQ process. One HARQ-ACK codebook is configured with a total of 16 bits: 2 bits of HARQ-ACK for HARQ process 0, 2 bits of HARQ-ACK for HARQ process 1, 2 bits of HARQ-ACK for HARQ process 2, 2 bits of HARQ-ACK for HARQ process 3, 2 bits of HARQ-ACK for HARQ process 4, 2 bits of HARQ-ACK for HARQ process 5, 2 bits of HARQ-ACK for HARQ process 6, and 2 bits of HARQ-ACK for HARQ process 7. The constructed HARQ-ACK codebook is transmitted from the terminal device 1 in the uplink cell of the base station device 3A.

The first method can be said to be a method in which the time resource (slot) used for transmitting HARQ-ACK is dynamically notified by DCI format. The second method can be said to be a method in which the time resource (slot) used for transmitting HARQ-ACK is semi-statically notified by RRC signaling. The first method can be said to be a method in which the time resource (slot) used for transmitting HARQ-ACK is aperiodic. The second method can be said to be a method in which the time resource (slot) used for transmitting HARQ-ACK is periodic. In the second method, the time resource (slot) used for transmitting HARQ-ACK may be static.

The first method is a method in which the frequency resource (physical channel) used for transmitting the HARQ-ACK is dynamically notified by the DCI format. The second method is a method in which the frequency resource (physical channel) used for transmitting the HARQ-ACK is semi-statically notified by RRC signaling.

The first method can be said to be a HARQ-ACK codebook that defines the relationship between the slot in which the HARQ-ACK codebook is transmitted and received and the slot of the PDSCH to which the HARQ-ACK included in the HARQ-ACK codebook corresponds. The HARQ process used for the PDSCH to which the HARQ-ACK included in the HARQ-ACK codebook of the first method corresponds is not limited in advance and is set by the scheduling of the base station device 3. The HARQ-ACK codebook of the second method can be said to be a HARQ-ACK codebook that defines the HARQ process of the PDSCH to which the HARQ-ACK included in the HARQ-ACK codebook corresponds.

For example, as frequency resources used for transmitting and receiving the HARQ-ACK codebook of the second method, frequency resources for every 8 slots are notified from the base station device 3 to the terminal device 1 by RRC signaling. For example, the period and offset are notified from the base station device 3 to the terminal device 1. For example, 8 is notified as the period. Any of 0, 1, 2, 3, 4, 5, 6, and 7 is notified as the offset. Here, the offset indicates how far the slots are shifted from a slot of a certain reference timing at which periodic resource allocation is performed. Here, the period may be equal to the total number of HARQ processes used in the downlink cell. For example, if the total number of HARQ processes used in the downlink cell is 8, the period of the frequency resources used for transmitting and receiving the HARQ-ACK codebook of the second method may be 8. For example, when the total number of HARQ processes used in a downlink cell is 16, the period of the frequency resources used for transmitting and receiving the HARQ-ACK codebook of the second method may be 16. Here, the offset candidate may be equal to the value of the period. Here, the period may be equal to the total number of HARQ processes used in a plurality of downlink cells. Here, the period may be equal to the total number of HARQ processes configured in the HARQ-ACK codebook.

For example, the terminal device 1 transmits a HARQ-ACK codebook consisting of a HARQ-ACK for the HARQ process of the first set of the second method in a period of 16 slots from slot 0. For example, the base station device 3A receives a HARQ-ACK codebook consisting of a HARQ-ACK for the HARQ process of the first set of the second method in a period of 16 slots from slot 0. The terminal device 1 transmits, in slot 0, a HARQ-ACK codebook consisting of eight HARQ-ACKs for a first set of HARQ processes consisting of eight HARQ processes (HARQ process 0, HARQ process 1, HARQ process 2, HARQ process 3, HARQ process 4, HARQ process 5, HARQ process 6, and HARQ process 7). The base station device 3A receives a HARQ-ACK codebook consisting of eight HARQ-ACKs for a first set of HARQ processes consisting of eight HARQ processes (HARQ process 0, HARQ process 1, HARQ process 2, HARQ process 3, HARQ process 4, HARQ process 5, HARQ process 6, and HARQ process 7) in slot 0. Next, the terminal device 1 transmits a HARQ-ACK codebook consisting of eight HARQ-ACKs for the first set of HARQ processes in slot 16. The base station device 3A receives a HARQ-ACK codebook consisting of eight HARQ-ACKs for the first set of HARQ processes in slot 16. Next, the terminal device 1 transmits a HARQ-ACK codebook consisting of eight HARQ-ACKs for the first set of HARQ processes in slot 32. The base station device 3A receives a HARQ-ACK codebook consisting of eight HARQ-ACKs for the first set of HARQ processes in slot 32. Here, the resource with a period of slots 0 to 16 is an example of a first periodic resource.

For example, the terminal device 1 transmits a HARQ-ACK codebook consisting of HARQ-ACKs for the HARQ processes of the second set of the second method in a period of 16 slots from slot 8. For example, the base station device 3A receives a HARQ-ACK codebook consisting of HARQ-ACKs for the HARQ processes of the second set of the second method in a period of 16 slots from slot 8. The terminal device 1 transmits, in slot 8, a HARQ-ACK codebook consisting of eight HARQ-ACKs for the HARQ processes of a second set consisting of eight HARQ processes (HARQ process 8, HARQ process 9, HARQ process 10, HARQ process 11, HARQ process 12, HARQ process 13, HARQ process 14, and HARQ process 15). The base station device 3A receives, in slot 8, a HARQ-ACK codebook consisting of eight HARQ-ACKs for the second set of HARQ processes (HARQ process 8, HARQ process 9, HARQ process 10, HARQ process 11, HARQ process 12, HARQ process 13, HARQ process 14, and HARQ process 15). Next, the terminal device 1 receives, in slot 24, a HARQ-ACK codebook consisting of eight HARQ-ACKs for the second set of HARQ processes (HARQ process 8, HARQ process 9, HARQ process 10, HARQ process 11, HARQ process 12, HARQ process 13, HARQ process 14, and HARQ process 15). The base station device 3A transmits a HARQ-ACK codebook consisting of eight HARQ-ACKs for the second set of HARQ processes in slot 24. Next, the terminal device 1 transmits a HARQ-ACK codebook consisting of eight HARQ-ACKs for the second set of HARQ processes in slot 40. The base station device 3A receives a HARQ-ACK codebook consisting of eight HARQ-ACKs for the second set of HARQ processes in slot 40. Here, the resources with a period of every 16 slots from slot 8 are an example of a second periodic resource.

For example, the terminal device 1 transmits a HARQ-ACK codebook consisting of a HARQ-ACK for the HARQ process of the first set of the second method and a HARQ-ACK codebook consisting of a HARQ-ACK for the HARQ process of the second set of the second method in a period of 8 slots from slot 0 in the time domain in sequence. For example, the base station device 3 receives a HARQ-ACK codebook consisting of a HARQ-ACK for the HARQ process of the first set of the second method and a HARQ-ACK codebook consisting of a HARQ-ACK for the HARQ process of the second set of the second method in a period of 8 slots from slot 0 in sequence in the time domain. The terminal device 1 transmits, in slot 0, a HARQ-ACK codebook consisting of eight HARQ-ACKs for a first set of HARQ processes consisting of eight HARQ processes (HARQ process 0, HARQ process 1, HARQ process 2, HARQ process 3, HARQ process 4, HARQ process 5, HARQ process 6, and HARQ process 7). The base station device 3A receives, in slot 0, a HARQ-ACK codebook consisting of eight HARQ-ACKs for a first set of HARQ processes consisting of eight HARQ processes (HARQ process 0, HARQ process 1, HARQ process 2, HARQ process 3, HARQ process 4, HARQ process 5, HARQ process 6, and HARQ process 7). Next, in slot 8, the terminal device 1 transmits a HARQ-ACK codebook consisting of eight HARQ-ACKs for a second set of HARQ processes consisting of eight HARQ processes (HARQ process 8, HARQ process 9, HARQ process 10, HARQ process 11, HARQ process 12, HARQ process 13, HARQ process 14, and HARQ process 15). The base station device 3A receives, in slot 8, a HARQ-ACK codebook consisting of eight HARQ-ACKs for the second set of HARQ processes (HARQ process 8, HARQ process 9, HARQ process 10, HARQ process 11, HARQ process 12, HARQ process 13, HARQ process 14, and HARQ process 15). Next, the terminal device 1 receives, in slot 16, a HARQ-ACK codebook consisting of eight HARQ-ACKs for the first set of HARQ processes (HARQ process 8, HARQ process 9, HARQ process 10, HARQ process 11, HARQ process 12, HARQ process 13, HARQ process 14, and HARQ process 15). The base station device 3A transmits a HARQ-ACK codebook consisting of eight HARQ-ACKs for the first set of HARQ processes in slot 16. Next, the terminal device 1 transmits a HARQ-ACK codebook consisting of eight HARQ-ACKs for the second set of HARQ processes in slot 24. The base station device 3A receives a HARQ-ACK codebook consisting of eight HARQ-ACKs for the second set of HARQ processes in slot 24. Here, the resource with a period of every eight slots from slot 0 is an example of a periodic resource.

Terminal device 1 transmits a HARQ-ACK codebook including a HARQ-ACK for the PDSCH of the downlink cell of base station device 3B in the uplink cell of base station device 3A. Base station device 3A receives the HARQ-ACK codebook including a HARQ-ACK for the PDSCH that terminal device 1 received in the downlink cell of base station device 3B in the uplink cell managed by base station device 3A, and notifies (transfers) the received HARQ-ACK to base station device 3B.

Each time the terminal device 1 transmits a HARQ-ACK codebook, it resets (flushes) the HARQ-ACK held (stored) for each HARQ process. The reset (flushed) HARQ-ACK is set to NACK as the default value. If the HARQ-ACK for the HARQ process used to transmit the PDSCH is ACK, the base station device 3B recognizes that the PDSCH has been properly received without data errors in the terminal device 1 and does not retransmit the data. If the HARQ-ACK for the HARQ process used to transmit the PDSCH is NACK, the base station device 3B recognizes that the PDSCH has not been properly received without data errors in the terminal device 1 and retransmits the data. The base station device 3B ignores the HARQ-ACK for the HARQ process not used for transmitting the PDSCH.

When a Dynamic HARQ-ACK codebook (Type 2 HARQ-ACK codebook) is used as the HARQ-ACK codebook of the first method, the UL grant includes a UL DAI field. The UL grant may include a UL DAI field for each PDSCH group. The number of PDSCH groups to be used may be configured from the base station device 3 to the terminal device 1 using RRC signaling. The base station device 3 transmits an UL grant including a UL DAI field for each PDSCH group to the terminal device 1, and receives a PUSH including HARQ-ACK information for each PDSCH group. The terminal device 1 receives an UL grant including a UL DAI field for each PDSCH group from the base station device 3, and transmits a PUSCH including HARQ-ACK information for each PDSCH group. The terminal device 1 receives an UL grant including a UL DAI field for each PDSCH group from the base station device 3, and transmits a PUSCH including HARQ-ACK information for all preconfigured PDSCH groups.

For example, when there are two PDSCH groups, PDSCH group 1 and PDSCH group 2, the UL DAI field for PDSCH group 1 and the UL DAI field for PDSCH group 2 are included in the UL grant. The terminal device 1 uses the UL DAI field for PDSCH group 1 to determine the HARQ-ACK information for PDSCH group 1, and uses the UL DAI field for PDSCH group 2 to determine the HARQ-ACK information for PDSCH group 2. The UL DAI field indicates the number of PDSCHs in which the HARQ-ACK corresponding to the HARQ-ACK codebook transmitted on the PUSH is included. If the number of received PDSCHs is less than the number of PDSCHs indicated by the UL DAI field, the terminal device 1 determines that there is a PDCCH that has missed detection, and sets a bit indicating NACK to the corresponding HARQ-ACK bit. The terminal device 1 transmits HARQ-ACK information for PDSCH group 1 and HARQ-ACK information for PDSCH group 2 by PUSCH. The base station device 3 judges whether a PDCCH detection error in PDSCH group 1 has occurred in the terminal device 1 from the HARQ-ACK information for PDSCH group 1 received by PUSCH, and judges whether a PDCCH detection error in PDSCH group 2 has occurred in the terminal device 1 from the HARQ-ACK information for PDSCH group 2 received by PUSCH. In this way, by including the UL DAI field for each PDSCH group in the UL grant, the terminal device 1 judges whether a PDCCH detection error for each PDSCH group has occurred, and the base station device 3 can appropriately recognize the judgment result in the terminal device 1.

The UL grant may include one UL DAI field for all PDSCH groups. The base station device 3 transmits an UL grant including UL DAI fields for all PDSCH groups to the terminal device 1, and receives a PUSCH including HARQ-ACK information for all PDSCH groups. The terminal device 1 receives an UL grant including UL DAI fields for all PDSCH groups from the base station device 3, and transmits a PUSCH including HARQ-ACK information for all PDSCH groups. The UL DAI field for all PDSCH groups may indicate the size of the HARQ-ACK codebook including HARQ-ACK information for all PDSCH groups. The UL DAI field for all PDSCH groups may indicate the number of HARQ-ACKs for all PDSCH groups included in the HARQ-ACK codebook transmitted in the PUSCH. The UL DAI field for all PDSCH groups may indicate the number of PDSCHs of all PDSCH groups for which a corresponding HARQ-ACK is included in the HARQ-ACK codebook transmitted on the PUSCH.

For example, when there are two PDSCH groups, PDSCH group 1 and PDSCH group 2, the UL DAI field for the combined PDSCH group consisting of PDSCH group 1 and PDSCH group 2 is included in the UL grant. The terminal device 1 uses the UL DAI field to determine HARQ-ACK information for PDSCH group 1 and PDSCH group 2. The UL DAI field indicates the number of PDSCHs of all PDSCH groups in which the HARQ-ACK corresponding to the HARQ-ACK codebook transmitted by the PUSCH is included. If the number of received PDSCHs is less than the number of PDSCHs indicated by the UL DAI field, the terminal device 1 determines that there is a PDCCH that has missed detection, and sets a bit indicating NACK to the corresponding HARQ-ACK bit. The terminal device 1 transmits HARQ-ACK information for PDSCH group 1 and PDSCH group 2 by PUSCH.

Figure 10 is a diagram showing an example of a search area set in a terminal device 1 according to one aspect of the present embodiment. In Figure 10, 14 OFDM symbols (l = 0, l = 1, l = 2, l = 3, l = 4, l = 5, l = 6, l = 7, l = 8, l = 9, l = 10, l = 11, l = 12, l = 13) are configured in one slot. In Figure 10, the first (l = 0) to seventh (l = 6) OFDM symbols are the OFDM symbols in the first half of the slot, and the eighth (l = 7) to fourteenth (l = 13) OFDM symbols are the OFDM symbols in the first half of the slot. In Figure 10, the first search area is set to the first (l = 0) OFDM symbol in the slot.

Figure 11 is a diagram showing an example of a search area set in a terminal device 1 according to one aspect of the present embodiment. In Figure 11, 14 OFDM symbols (l = 0, l = 1, l = 2, l = 3, l = 4, l = 5, l = 6, l = 7, l = 8, l = 9, l = 10, l = 11, l = 12, l = 13) are configured in one slot. In Figure 11, the first (l = 0) to seventh (l = 6) OFDM symbols are the OFDM symbols in the first half of the slot, and the eighth (l = 7) to fourteenth (l = 13) OFDM symbols are the OFDM symbols in the first half of the slot. In Figure 11, the second search area is set to the first (l = 0) OFDM symbol of the slot and the eighth (l = 7) OFDM symbol of the slot. In this case, one PDCCH candidate is composed of one or more CCEs in the first OFDM symbol (l=0) of the slot, or one or more CCEs in the eighth OFDM symbol (l=7) of the slot. Note that the search space set in the first OFDM symbol (l=0) of the slot and the search space set in the eighth OFDM symbol (l=7) of the slot may be logically different search spaces. Figure 11 may be a search space set consisting of the search space set in the first OFDM symbol (l=0) of the slot and the search space set in the eighth OFDM symbol (l=7) of the slot.

Figure 12 is a diagram showing an example of a search area set in a terminal device 1 according to one aspect of the present embodiment. In Figure 12, 14 OFDM symbols (l = 0, l = 1, l = 2, l = 3, l = 4, l = 5, l = 6, l = 7, l = 8, l = 9, l = 10, l = 11, l = 12, l = 13) are configured in one slot. In Figure 12, the first (l = 0) to seventh (l = 6) OFDM symbols are OFDM symbols in the first half of the slot, and the eighth (l = 7) to fourteenth (l = 13) OFDM symbols are OFDM symbols in the first half of the slot. In Figure 12, the third search area is set from the first (l = 0) to the second (l = 1) OFDM symbol in the slot. In this case, one PDCCH candidate consists of one or more CCEs in the first (l=0) and second (l=1) OFDM symbols of a slot.

Figure 13 is a diagram showing an example of a search area set in a terminal device 1 according to one aspect of the present embodiment. In Figure 13, 14 OFDM symbols (l = 0, l = 1, l = 2, l = 3, l = 4, l = 5, l = 6, l = 7, l = 8, l = 9, l = 10, l = 11, l = 12, l = 13) are configured in one slot. In Figure 13, the first (l = 0) to seventh (l = 6) OFDM symbols are the OFDM symbols in the first half of the slot, and the eighth (l = 7) to fourteenth (l = 13) OFDM symbols are the OFDM symbols in the first half of the slot. In Figure 13, the fourth search space is set to the first (l = 0) OFDM symbol of the slot, the fourth (l = 3) OFDM symbol of the slot, the eighth (l = 7) OFDM symbol of the slot, and the twelfth (l = 11) OFDM symbol of the slot. In this case, one PDCCH candidate is composed of one or more CCEs of the first (l = 0) OFDM symbol of the slot, or one or more CCEs of the fourth (l = 3) OFDM symbol of the slot, or one or more CCEs of the eighth (l = 7) OFDM symbol of the slot, or one or more CCEs of the twelfth (l = 11) OFDM symbol of the slot.

As described above, one aspect of the present invention allows HARQ-ACK to be appropriately exchanged between the terminal device 1 and the base station device 3. As a result, the base station device 3 can appropriately control the retransmission of data. By realizing appropriate retransmission control, efficient communication is achieved.

It takes time for base station device 3A to notify (transfer) HARQ-ACK to base station device 3B. In one aspect of the present invention, by using a set of HARQ processes used for communication with terminal device 1 in the downlink cell of base station device 3B in a time-division manner, communication can be performed using the HARQ process of one set in the waiting state until the HARQ-ACK for the HARQ process of the other set is notified from base station device 3A to base station device 3B, thereby realizing efficient communication.

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 including a processor and a memory for storing computer program code, and performs operations including setting a first periodic resource and a second periodic resource in an uplink cell managed by a first base station device, and transmitting a HARQ-ACK codebook including a HARQ-ACK for a PDSCH of a downlink cell managed by a second base station device, using the first periodic resource and the second periodic resource.

(2) Further, the HARQ-ACK codebook is composed of multiple HARQ-ACKs, each of which corresponds to a different HARQ process, and the HARQ-ACK codebook composed of the HARQ-ACKs corresponding to a first set of HARQ processes is transmitted on the first periodic resource, and the HARQ-ACK codebook composed of the HARQ-ACKs corresponding to a second set of HARQ processes is transmitted on the second periodic resource.

(3) Furthermore, an uplink cell managed by the second base station device is not configured for the terminal device.

(4) A second aspect of the present invention is a terminal device including a processor and a memory for storing computer program code, the terminal device configuring a periodic resource in an uplink cell managed by a first base station device, transmitting a HARQ-ACK codebook including a HARQ-ACK for a PDSCH of a downlink cell managed by a second base station device using the periodic resource, the HARQ-ACK codebook being composed of a plurality of HARQ-ACKs, each of the HARQ-ACKs being a different HARQ
and transmitting, in a time domain, the HARQ-ACK codebook consisting of the HARQ-ACKs corresponding to a first set of HARQ processes and a second set of HARQ processes, in a time domain in sequence.

(5) Furthermore, an uplink cell managed by the second base station device is not configured for the terminal device.

(6) A third aspect of the present invention is a base station device comprising a processor and a memory for storing computer program code, which performs operations including setting a first periodic resource and a second periodic resource in an uplink cell for a terminal device, receiving from the terminal device a HARQ-ACK codebook including a HARQ-ACK for a PDSCH of a downlink cell managed by a different base station device using the first periodic resource and the second periodic resource, and forwarding the received HARQ-ACK to the different base station device.

(7) Further, the HARQ-ACK codebook is composed of multiple HARQ-ACKs, each of which corresponds to a different HARQ process, and the HARQ-ACK codebook composed of the HARQ-ACKs corresponding to a first set of HARQ processes is received on the first periodic resource, and the HARQ-ACK codebook composed of the HARQ-ACKs corresponding to a second set of HARQ processes is received on the second periodic resource.

(8) A fourth aspect of the present invention is a base station device including a processor and a memory for storing computer program code, the base station device configuring a periodic resource in an uplink cell for a terminal device, receiving a HARQ-ACK codebook including a HARQ-ACK for a PDSCH of a downlink cell managed by a different base station device in the periodic resource, the HARQ-ACK codebook being composed of a plurality of HARQ-ACKs, each of the HARQ-ACKs corresponding to a different HARQ process, and the HARQ-ACK codebook being composed of the HARQ-ACKs corresponding to a first set of HARQ processes and the HARQ-ACK codebook being composed of the HARQ-ACKs corresponding to a second set of HARQ processes. The base station device performs operations including receiving the HARQ-ACK and the codebook in a time domain in sequence, and transferring the received HARQ-ACK to the different base station device.

(9) A fifth aspect of the present invention is a communication method for use in a terminal device, comprising the steps of: setting a first periodic resource and a second periodic resource in an uplink cell managed by a first base station device; and transmitting a HARQ-ACK codebook including a HARQ-ACK for a PDSCH of a downlink cell managed by a second base station device using the first periodic resource and the second periodic resource.

(10) Further, the HARQ-ACK codebook is composed of a plurality of HARQ-ACKs, each of which corresponds to a different HARQ process, and the HARQ-ACK codebook composed of the HARQ-ACKs corresponding to a first set of HARQ processes is transmitted on the first periodic resource, and the HARQ-ACK codebook composed of the HARQ-ACKs corresponding to a second set of HARQ processes is transmitted on the second periodic resource.

(11) Furthermore, an uplink cell managed by the second base station device is not configured for the terminal device.

(12) A sixth aspect of the present invention is a communication method for use in a terminal device, comprising: setting periodic resources in an uplink cell managed by a first base station device; transmitting a HARQ-ACK codebook including a HARQ-ACK for a PDSCH of a downlink cell managed by a second base station device, using the periodic resources; the HARQ-ACK codebook is composed of a plurality of HARQ-ACKs, each of the HARQ-ACKs corresponding to a different HARQ process, and transmitting the HARQ-ACK codebook composed of the HARQ-ACKs corresponding to a first set of HARQ processes and the HARQ-ACK codebook composed of the HARQ-ACKs corresponding to a second set of HARQ processes in a time domain in sequence.

(13) Furthermore, an uplink cell managed by the second base station device is not configured for the terminal device.

(14) A seventh aspect of the present invention is a communication method for use in a base station device, comprising the steps of: setting a first periodic resource and a second periodic resource in an uplink cell for a terminal device; receiving from the terminal device, using the first periodic resource and the second periodic resource, a HARQ-ACK codebook including a HARQ-ACK for a PDSCH of a downlink cell managed by a different base station device; and forwarding the received HARQ-ACK to the different base station device.

(15) Further, the HARQ-ACK codebook is composed of a plurality of HARQ-ACKs, each of which corresponds to a different HARQ process, and the HARQ-ACK codebook composed of the HARQ-ACKs corresponding to a first set of HARQ processes is received on the first periodic resource, and the HARQ-ACK codebook composed of the HARQ-ACKs corresponding to a second set of HARQ processes is received on the second periodic resource.

(16) An eighth aspect of the present invention is a communication method used in a base station device, comprising the steps of: setting a periodic resource in an uplink cell for a terminal device; receiving a HARQ-ACK codebook including a HARQ-ACK for a PDSCH of a downlink cell managed by a different base station device, using the periodic resource; the HARQ-ACK codebook is composed of a plurality of HARQ-ACKs, each of which corresponds to a different HARQ process; and receiving the HARQ-ACK codebook composed of the HARQ-ACKs corresponding to a first set of HARQ processes and the HARQ-ACK codebook composed of the HARQ-ACKs corresponding to a second set of HARQ processes. The method includes the steps of receiving the HARQ-ACK and the codebook in a time domain in sequence, and transferring the received HARQ-ACK to the different base station device.

The base station device 3 and the terminal device 1 according to one aspect of the present invention may be programs (programs that cause a computer to function) that control a CPU (Central Processing Unit) or the like so as to realize the functions of the above-described embodiment according 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. Also, 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 embodiment 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 embodiment 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

Claims (16)

A terminal device comprising a processor and a memory for storing computer program code,
Configuring a first periodic resource and a second periodic resource in an uplink cell managed by a first base station device;
transmitting a HARQ-ACK codebook including a HARQ-ACK for a PDSCH of a downlink cell managed by a second base station device using the first periodic resource and the second periodic resource;
The HARQ-ACK codebook is composed of a plurality of HARQ-ACKs, each of which corresponds to a HARQ process having a different HARQ process number;
transmitting the HARQ-ACK codebook consisting of a first set of a plurality of HARQ processes and the corresponding HARQ-ACKs on the first periodic resource, and transmitting the HARQ-ACK codebook consisting of a second set of HARQ processes and the corresponding HARQ-ACKs on the second periodic resource;
HARQ process numbers of the HARQ processes corresponding to each of the HARQ-ACK codebooks are preset;
HARQ process numbers of the first set of HARQ processes are different from HARQ process numbers of the second set of HARQ processes;
Terminal device. The HARQ-ACK codebook is composed of a plurality of HARQ-ACKs, each of which corresponds to a different HARQ process;
transmitting the HARQ-ACK codebook consisting of the HARQ processes of the first set and the corresponding HARQ-ACKs on the first periodic resource;
transmitting the HARQ-ACK codebook consisting of the HARQ processes of the second set and the corresponding HARQ-ACKs on the second periodic resource;
The terminal device according to claim 1 . An uplink cell managed by the second base station device is not configured for the terminal device;
The terminal device according to claim 1 . A terminal device comprising a processor and a memory for storing computer program code,
Configuring periodic resources in an uplink cell managed by a first base station device;
transmitting a HARQ-ACK codebook including a HARQ-ACK for a PDSCH of a downlink cell managed by a second base station device using the periodic resource;
The HARQ-ACK codebook is composed of a plurality of HARQ-ACKs, each of which corresponds to a HARQ process having a different HARQ process number;
transmitting the HARQ-ACK codebook consisting of the HARQ-ACKs corresponding to a first set of HARQ processes and the HARQ-ACKs corresponding to a second set of HARQ processes in a time domain in sequence;
Performing an action including
the HARQ process numbers of the HARQ processes in the first set are different from the HARQ process numbers of the HARQ processes in the second set;
Terminal device. An uplink cell managed by the second base station device is not configured for the terminal device;
The terminal device according to claim 4. A base station device comprising a processor and a memory for storing computer program code,
configuring a first periodic resource and a second periodic resource in an uplink cell for a terminal device;
receiving, from the terminal device, a HARQ-ACK codebook including a HARQ-ACK for a PDSCH of a downlink cell managed by a different base station device, using the first periodic resource and the second periodic resource;
forwarding the received HARQ-ACK to the different base station device;
Performing an action including
The HARQ-ACK codebook is composed of a plurality of HARQ-ACKs, each of which corresponds to a HARQ process having a different HARQ process number;
receiving the HARQ-ACK codebook consisting of a first set of a plurality of HARQ processes and the corresponding HARQ-ACKs from the terminal device on the first periodic resource, and receiving the HARQ-ACK codebook consisting of a second set of HARQ processes and the corresponding HARQ-ACKs from the terminal device on the second periodic resource;
HARQ process numbers of the HARQ processes corresponding to each of the HARQ-ACK codebooks are preset;
HARQ process numbers of the first set of HARQ processes are different from HARQ process numbers of the second set of HARQ processes;
Base station equipment. The HARQ-ACK codebook is composed of a plurality of HARQ-ACKs, each of which corresponds to a different HARQ process;
receiving the HARQ-ACK codebook consisting of the HARQ processes of the first set and the corresponding HARQ-ACKs on the first periodic resource;
receiving the HARQ-ACK codebook consisting of the HARQ processes of the second set and the corresponding HARQ-ACKs on the second periodic resource;
The base station device according to claim 6. A base station device comprising a processor and a memory for storing computer program code,
Configuring periodic resources in an uplink cell for a terminal device;
receiving, via the periodic resource, a HARQ-ACK codebook including a HARQ-ACK for a PDSCH of a downlink cell managed by a different base station device;
The HARQ-ACK codebook is composed of a plurality of HARQ-ACKs, each of which corresponds to a HARQ process having a different HARQ process number;
receiving the HARQ-ACK codebook consisting of the HARQ-ACKs corresponding to a first set of HARQ processes and a second set of HARQ processes in a time domain in sequence;
forwarding the received HARQ-ACK to the different base station device;
Performing an action including
the HARQ process numbers of the HARQ processes in the first set are different from the HARQ process numbers of the HARQ processes in the second set;
Base station equipment. A communication method for use in a terminal device, comprising:
configuring a first periodic resource and a second periodic resource in an uplink cell managed by a first base station device;
transmitting a HARQ-ACK codebook including a HARQ-ACK for a PDSCH of a downlink cell managed by a second base station device, using the first periodic resource and the second periodic resource;
Including,
The HARQ-ACK codebook is composed of a plurality of HARQ-ACKs, each of which corresponds to a HARQ process having a different HARQ process number;
transmitting the HARQ-ACK codebook consisting of a first set of a plurality of HARQ processes and the corresponding HARQ-ACKs on the first periodic resource, and transmitting the HARQ-ACK codebook consisting of a second set of HARQ processes and the corresponding HARQ-ACKs on the second periodic resource;
HARQ process numbers of the HARQ processes corresponding to each of the HARQ-ACK codebooks are preset;
HARQ process numbers of the first set of HARQ processes are different from HARQ process numbers of the second set of HARQ processes;
Communication methods. The HARQ-ACK codebook is composed of a plurality of HARQ-ACKs, each of which corresponds to a different HARQ process;
transmitting the HARQ-ACK codebook consisting of the HARQ processes of the first set and the corresponding HARQ-ACKs on the first periodic resource;
transmitting the HARQ-ACK codebook consisting of the HARQ processes of the second set and the corresponding HARQ-ACKs on the second periodic resource;
The communication method according to claim 9. An uplink cell managed by the second base station device is not configured for the terminal device;
The communication method according to claim 9. A communication method for use in a terminal device, comprising:
configuring periodic resources in an uplink cell managed by a first base station;
transmitting a HARQ-ACK codebook including a HARQ-ACK for a PDSCH of a downlink cell managed by a second base station device using the periodic resource;
The HARQ-ACK codebook is composed of a plurality of HARQ-ACKs, each of which corresponds to a HARQ process having a different HARQ process number;
transmitting the HARQ-ACK codebook consisting of the HARQ-ACKs corresponding to a first set of HARQ processes and a second set of HARQ processes in a time domain in sequence;
Including,
the HARQ process numbers of the HARQ processes in the first set are different from the HARQ process numbers of the HARQ processes in the second set;
Communication methods. An uplink cell managed by the second base station device is not configured for the terminal device;
The communication method according to claim 12. A communication method used in a base station device, comprising:
configuring a first periodic resource and a second periodic resource in an uplink cell for a terminal device;
receiving, from the terminal device, a HARQ-ACK codebook including a HARQ-ACK for a PDSCH of a downlink cell managed by a different base station device, using the first periodic resource and the second periodic resource; and transferring the received HARQ-ACK to the different base station device;
Including,
The HARQ-ACK codebook is composed of a plurality of HARQ-ACKs, each of which corresponds to a HARQ process having a different HARQ process number;
receiving the HARQ-ACK codebook consisting of a first set of a plurality of HARQ processes and the corresponding HARQ-ACKs from the terminal device on the first periodic resource, and receiving the HARQ-ACK codebook consisting of a second set of HARQ processes and the corresponding HARQ-ACKs from the terminal device on the second periodic resource;
HARQ process numbers of the HARQ processes corresponding to each of the HARQ-ACK codebooks are preset;
HARQ process numbers of the first set of HARQ processes are different from HARQ process numbers of the second set of HARQ processes;
Communication methods. The HARQ-ACK codebook is composed of a plurality of HARQ-ACKs, each of which corresponds to a different HARQ process;
receiving the HARQ-ACK codebook consisting of the HARQ-ACKs corresponding to the first set of HARQ processes on the first periodic resource, and receiving the HARQ-ACK codebook consisting of the HARQ-ACKs corresponding to the second set of HARQ processes on the second periodic resource;
The communication method according to claim 14. A communication method used in a base station device, comprising:
configuring periodic resources in an uplink cell for a terminal device;
receiving, via the periodic resource, a HARQ-ACK codebook including a HARQ-ACK for a PDSCH of a downlink cell managed by a different base station device;
The HARQ-ACK codebook is composed of a plurality of HARQ-ACKs, each of which corresponds to a HARQ process having a different HARQ process number;
receiving the HARQ-ACK codebook consisting of the HARQ-ACKs corresponding to a first set of HARQ processes and a second set of HARQ processes in a time domain in sequence;
transmitting the received HARQ-ACK to the different base station device;
Including,
the HARQ process numbers of the HARQ processes in the first set are different from the HARQ process numbers of the HARQ processes in the second set;
Communication methods.

Images