JP2021027553A - Terminal device and communication method - Google Patents

Abstract

To provide a terminal device and a base station device that can efficiently transmit and receive HARQ-ACK.SOLUTION: A terminal device includes: a reception unit that receives a PDCCH (608) that deactivates an SPS PDSCH and a PDCCH including a DCI format that triggers transmission of a codebook including one or more pieces of HARQ-ACK information; and a transmission unit that transmits a PUCCH including the codebook. First HARQ-ACK information corresponding to deactivation of the SPS PDSCH is included in the one or more pieces of HARQ-ACK information, and the first HARQ-ACK information is included in a field corresponding to a HARQ process having the smallest HARQ process ID in one or more HARQ processes formed in the codebook (609).SELECTED DRAWING: Figure 6

Description

The present invention relates to a terminal device and a communication method.

Wireless access method and wireless network for cellular mobile communication (hereinafter referred to as "Long T"
"erm Evolution (LTE)" or "EUTRA: Evolved U"
It is called "niversal Terrestrial Radio Access". ) Is being considered in the 3rd Generation Partnership Project (3GPP). In LTE, the base station apparatus is also referred to as an eNodeB (evolved NodeB), and the terminal apparatus is also referred to as a UE (User Equipment). LTE is a cellular communication system in which a plurality of areas covered by a base station apparatus are arranged in a cell shape. A single base station device may manage multiple serving cells.

At 3GPP, the next-generation standard (NR: New Radio) will be examined in order to propose to IMT (International Mobile Telecommunication) -2020, which is a standard for next-generation mobile communication systems established by the International Telecommunication Union (ITU). (Non-Patent Document 1). NR is an eMBB (enhanced Mobile Broadband), mMTC (massive Mac) within the framework of a single technology.
ine Type Communication), URLLC (Ultra Relia)
It is required to meet the requirements assuming the three scenarios of ble and Low Latency Communication).

In addition, the application of NR in the license-free frequency band (Unlicensed Spectrum) is being studied (Non-Patent Document 2). It is being studied to apply NR supporting a wide band of 100 MHz to a carrier in an unlicensed frequency band to realize a data rate of several Gbps.

"New SID proposal: Study on New Radio Access Technology", RP-160671, NTT docomo, 3GPP TSG RAN Meeting # 71, Goteborg, Sweden, 7th-10th March, 2016. "New WID on NR-based Access to Unlicensed Spectrum", RP-182878, Qualcomm Incorporated, 3GPP TSG RAN Meeting # 82, Sorrento, Italy, 10th --13th December, 2018. "3GPP TS 38.211 V15.5.0 (2019-03), NR; Physical channels and modulation". "3GPP TS 38.212 V15.5.0 (2019-03), NR; Multiplexing and channel coding". "3GPP TS 38.213 V15.5.0 (2019-03), NR; Physical layer procedures for control". "3GPP TS 38.214 V15.5.0 (2019-03), NR; Physical layer procedures for data".

The present invention relates to a terminal device capable of efficiently performing uplink transmission and / or receiving downlink transmission, a communication method used for the terminal device, efficiently downlink transmission, and / or uplink. Provided are a base station apparatus capable of receiving and receiving transmission, and a communication method used for the base station apparatus.

(1) A first aspect of the present invention is a terminal device, which is a DCI format that receives a PDCCH that deactivates an SPS PDSCH and triggers the transmission of a codebook containing one or more HARQ-ACK information. The first HARQ-ACK information corresponding to the deactivation of the SPS PDSCH includes the receiving unit for receiving the PDCCH including the above, and the transmitting unit for transmitting the PUCCH including the invention, and the one or a plurality of the above. The first HARQ-ACK information is included in the field corresponding to the HARQ process having the smallest HARQ process ID among the one or more configured HARQ processes, which is included in the HARQ-ACK information.

(2) A second aspect of the present invention is a DCI that is a base station apparatus that transmits a PDCCH that deactivates the SPS PDSCH and triggers the transmission of a codebook containing one or more HARQ-ACK information. The one or a plurality of first HARQ-ACK information corresponding to the deactivation of the SPS PDSCH is provided with a transmission unit for transmitting a PDCCH including a format and a receiving unit for receiving a PUCCH including the codebook. The first HARQ-ACK information is included in the field corresponding to the HARQ process having the smallest HARQ process ID among the one or more configured HARQ processes in the codebook. ..

(3) A third aspect of the present invention is a communication method used for a terminal device, which receives a PDCCH that deactivates an SPS PDSCH and transmits a codebook containing one or more HARQ-ACK information. The first HARQ-ACK information corresponding to the deactivation of the SPS PDSCH includes a step of receiving a PDCCH including a DCI format that triggers the process and a step of transmitting a PUCCH containing the codebook. Alternatively, the first HARQ-ACK information is included in the field corresponding to the HARQ process having the smallest HARQ process ID among the configured one or more HARQ processes in the codebook, which is included in the plurality of HARQ-ACK information. Include.

(4) A fourth aspect of the present invention is a communication method used for a base station apparatus, which transmits a PDCCH for deactivating an SPS PDSCH and includes one or a plurality of HARQ-ACK information in a codebook. The first HARQ-ACK information corresponding to the deactivation of the SPS PDSCH includes the step of transmitting the PDCCH including the DCI format that triggers the transmission and the step of receiving the PUCCH including the codebook. The first HARQ-ACK is included in the field corresponding to the HARQ process having the smallest HARQ process ID among the configured HARQ processes in the codebook, which is included in the one or more HARQ-ACK information. Include information.

According to the present invention, the terminal device can efficiently communicate. In addition, the base station device can efficiently communicate.

It is a conceptual diagram of the wireless communication system which concerns on one aspect of this Embodiment. ^{This is an example showing the relationship between the N slot} _symb , the setting μ of the subcarrier interval, the slot setting, and the CP setting according to one aspect of the present embodiment. It is the schematic which shows an example of the resource grid in the subframe which concerns on one aspect of this Embodiment. It is a schematic block diagram which shows the structure of the terminal apparatus 1 which concerns on one aspect of this Embodiment. It is a schematic block diagram which shows the structure of the base station apparatus 3 which concerns on one aspect of this Embodiment. It is a figure which showed an example of the reception of SPS PDSCH in this embodiment. It is a figure which showed an example of the type 3 HARQ-ACK codebook when SPS PDSCH is not configured in this embodiment. It is a figure which showed an example of the report of HARQ-ACK information corresponding to PDSCH and SPS PDSCH scheduled by DL grant when SPS PDSCH is configured in terminal apparatus 1 in this embodiment. It is a figure which showed an example which reports HARQ-ACK information for the deactivation of SPS PDSCH and HARQ trigger bit in this embodiment.

Hereinafter, embodiments of the present invention will be described.

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

When a parameter or information indicates one or more values, the parameter or information may include at least 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: Information Element) including a plurality of parameters.

FIG. 1 is a conceptual diagram of a wireless communication system according to one aspect of the present embodiment. In FIG. 1, the wireless communication system includes terminal devices 1A to 1C and a base station device 3 (gNB). Hereinafter, the terminal devices 1A to 1C are also referred to as a terminal device 1 (UE).

The base station device 3 may be configured to include one or both of the MCG (Master Cell Group) and the SCG (Secondary Cell Group). An MCG is a group of serving cells composed of at least a PCell (Primary Cell). SCG is at least PSCell (Primary S)
It is a group of serving cells composed of (econdary Cell). P
The Cell may be a serving cell given based on the 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 identifier may be given by a higher layer parameter.

The frame configuration will be described below.

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

The subcarrier spacing (SCS: SubCarrier Spacing) may be given by the ^{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 BWP (BandWidth Part), the subcarrier spacing setting μ may be given by the upper layer parameters.

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

The constant κ may be a value indicating the relationship between the reference subcarrier interval and T _c. The constant κ may be used for the length of the subframe. The number of slots contained in the subframe may be given, at least based on the constant κ. Δf _ref is the reference subcarrier interval, and N _{f and ref} are values corresponding to the reference subcarrier interval.

The transmission on the downlink and / or the transmission on the uplink consists of a frame of 10 ms. 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 μ.

The number and index of slots contained in a subframe may be given for a given subcarrier spacing setting μ. For example, the first slot number n ^mu _s is, ^{N subframe} in the subframe ^0, may be given in ascending order in the range of ^mu _slot -1. The number and index of slots contained in the frame may be given for the setting μ of the subcarrier spacing. For example, the second slot numbers n ^μ _{s, f} may be given in ascending order in the range of 0 to N ^{frame, μ} _{slot -1 in the frame.} One slot may contain consecutive N ^slot _{symbs of OFDM symbols.} The N ^slot _symb may be given at least on the basis of some or all of the slot configuration and / or CP (Cyclo Prefix) settings. The slot setting may be given by at least the upper layer parameter tdd-UL-DL-CompositionCommon. CP settings may be given at least based on higher layer parameters. CP settings may be given at least based 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 the N slot} _symb , the setting μ of the subcarrier interval, the slot setting, and the 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 CP (normal cyclic prefix), N ^slot _symb = 14, N ^{frame, μ} _slot = 40, N ^{subframe, μ} _slot = 4. Further, in FIG. 2B, when the slot setting is 0, the subcarrier interval setting μ is 2, and the CP setting is extended CP (extended cyclic prefix), N ^slot _symb = 12, N ^{frame, μ} _slot = 40, N ^{subframe, μ} _slot = 4. ^{The N slot} _{symb at} slot setting 0 may correspond to twice the ^{N slot} _symb at slot setting 1.

The physical resources will be described below.

An antenna port is defined by the fact that the channel through which a symbol is transmitted in one antenna port can be estimated from the channel through which another symbol is transmitted in the same antenna port. If the large scale property of the channel on which the symbol is transmitted in one antenna port can be estimated from the channel in which the symbol is transmitted in the other antenna port, the two antenna ports are QCL (Quantum Co-Located). ) Is called. Large scale characteristics may include at least the long interval characteristics of the channel. Large-scale characteristics are delayed spread (delay sp)
read), Doppler spread (Doppler spread), Doppler shift (
Doppler shift, average gain, average delay, and beam parameters (spatial Rx para).
It may contain at least a part or all of meters). The fact that the first antenna port and the second antenna port are QCL with respect to the beam parameters means that the receiving beam assumed by the receiving side with respect to the first antenna port and the receiving beam assumed by the receiving side with respect to the second antenna port. May be the same. The fact that the first antenna port and the second antenna port are QCL with respect to the beam parameters means that the transmitting beam assumed by the receiving side with respect to the first antenna port and the transmitting beam assumed by the receiving side with respect to the second antenna port. May be the same. The terminal device 1 assumes that the two antenna ports are QCLs when the large-scale characteristics of the channel through which the symbol is transmitted in one antenna port can be estimated from the channel in which the symbol is transmitted in the other antenna port. May be done. The fact that the two antenna ports are QCLs may mean that the two antenna ports are QCLs.

^{A resource grid of N μ} _{RB, x} N ^RB _sc subcarriers and N ^(μ) _symb N ^{subframe, μ} _symb OFDM symbols is provided for each of the subcarrier spacing settings and carrier sets. N ^μ _{RB, x} may indicate the number of resource blocks given for setting the subcarrier spacing μ for carrier x. N ^μ _{RB, x} may be the maximum number of resource blocks given for setting the subcarrier spacing μ for carrier x. The carrier x indicates either a downlink carrier or an uplink carrier. That is, x is "DL" or "UL". N ^μ _RB is a name that includes ^{N μ} _{RB, DL} , and / or N ^μ _{RB, UL.} ^NRB _sc may indicate the number of subcarriers contained 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: DownLink) and an uplink (UL: UpLink). Hereinafter, a set of parameters including at least a part or all of the antenna port p, the subcarrier interval setting μ, and the transmission direction setting is also referred to as a first radio parameter set. That is, one resource grid may be given for each first set of radio parameters.

In the downlink, the carrier included in the serving cell is referred to as a downlink carrier (or downlink component carrier). In the uplink, the carrier included in the serving cell is referred to as an uplink carrier (uplink component carrier). The downlink component carrier and the uplink component carrier are collectively referred to as a component carrier (or carrier).

Each element in the resource grid given for each first set of radio parameters is referred to as a resource element. The resource element is specified by the _{frequency domain index k sc} and the time domain index l _sym. For a first set of radio parameters, resource elements are identified by a _{frequency domain index k sc} and a time domain index l _sym. The resource element specified by the frequency domain index k _sc and the time domain index l _sym is also referred to as _{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 given for setting the subcarrier spacing μ. N ^RB _sc is the number of subcarriers included in the resource block, and N ^RB _sc = 12. The frequency domain index k _sc may correspond to the subcarrier index k _sc. The time domain index l _sym may correspond to the OFDM symbol index l _sym.

FIG. 3 is a schematic view showing an example of a resource grid in the subframe according to one aspect of the present embodiment. In the resource grid of FIG. 3, the horizontal axis is the time domain index l _sym , and the vertical axis is the frequency domain index k _sc . In one subframe, the frequency domain of the resource grid contains N ^μ _RB N ^RB _sc subcarriers. In one subframe, the time domain of the resource grid may contain 14.2 ^{μ OFDM symbols.} One resource block ^is configured to include ^N _{RB sc} subcarriers. The time domain of the resource block may correspond to a 1 OFDM symbol. The time domain of the resource block may correspond to 14 OFDM symbols. The time domain of the resource block may correspond to one or more slots. The time domain of the resource block may correspond to one subframe.

The terminal device 1 may be instructed to transmit and receive using only a subset of the resource grid. A subset of the resource grid, also referred to as BWP, may be given based on at least some or all of the upper layer parameters and / or DCI. BWP is also referred to as a band part (BP: Bandwidth Part). That is, the terminal device 1 may not be instructed to perform transmission / reception using the entire set of resource grids. That is, the terminal device 1 may be instructed to perform transmission / reception using a part of the frequency resources in the resource grid. One BWP may be composed of a plurality of resource blocks in the frequency domain. One BWP may be composed of a plurality of continuous resource blocks in the frequency domain. The BWP set for the downlink carrier is also referred to as the downlink BWP. The BWP set for the uplink carrier is also referred to as an uplink BWP.

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

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

A set of downlink BWPs may be set for each of the serving cells. A set of downlink BWPs may include one or more downlink BWPs. A set of uplink BWPs may be set for each of the serving cells. Uplink BW
The set of Ps may include one or more uplink BWPs.

The upper layer parameter is a parameter included in the upper layer signal. The signal of the upper layer may be RRC (Radio Resource Control) signaling or MAC CE (Media Access Control Control Element). Here, the signal of the upper layer may be a signal of the RRC layer or a signal of the MAC layer.

The signal of the upper layer may be common RRC signaling (comon RRC signaling). The common RRC signaling may include at least some or all of the following features C1 to C3.
Feature C1) Mapped to BCCH logical channel or CCCH logical channel Feature C2) Mapped to feature C3) PBCH containing at least a radioRelocationConfigCommon information element

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

The signal of the upper layer may be dedicated RRC signaling (dedicated RRC signaling). Dedicated RRC signaling may include at least some or all of the following features D1 to D2.
Feature D1) Features mapped to DCCH logical channels D2) Includes at least a radioResourceControlDedicated information element

The radioResourceControlDedicated information element may include at least information indicating settings specific to the terminal device 1. The radioResourceControlDedicated information element may include at least information indicating the setting of the BWP. The BWP settings may at least indicate the frequency resources of the BWP.

For example, the MIB, the first system information, and the second system information may be included in the common RRC signaling. In addition, higher layer messages that are mapped to the DCCH logical channel and that include at least the radioResourceConfigCommon may be included in the common RRC signaling. Further, the message of the upper layer which is mapped to the DCCH logical channel and does not include the radioResourceConfigCommon information element may be included in the dedicated RRC signaling. Further, the upper layer messages that are mapped to the DCCH logical channel and include at least the radioRelocationConfigdicated information element may be included in the dedicated RRC signaling.

The first system information may at least indicate the time index of the SS (Synchronization Signal) block. SS block (SS block)
Is also referred to as an SS / PBCH block (SS / PBCH block). The SS / PBCH block is also referred to as SS / PBCH. The first system information may include at least information related to the PRACH resource. The first system information may include at least information related to the initial connection settings. The second system information may be system information other than the first system information.

The radioResourceControlDedicated information element may include at least information related to the PRACH resource. The radioResourceConfigDedicated information element may include at least information related to the initial connection settings.

Hereinafter, physical channels and physical signals according to various aspects of the present embodiment will be described.

The uplink physical channel may correspond to a set of resource elements that carry information that occurs in the upper layers. The uplink physical channel is a physical channel used in the uplink carrier. In the 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: Uplink Control Information). Uplink control information includes channel state information (CSI: Channel State Information), scheduling request (SR: Scheduling Request), transport block (TB: Transport block, MAC PDU: Medium Access Control Download, Digital Protocol Data Unit). -HARQ-ACK (Hybrid Au) corresponding to Shared Channel, PDSCH: Physical Download Sharp Channel)
Includes part or all of the tomato-repair request ACKnowledgement).

The HARQ-ACK may include at least the HARQ-ACK bits (HARQ-ACK information) corresponding to one transport block. The HARQ-ACK bit may indicate an ACK (acknowledgement) or NACK (negate-acknowledgement) corresponding to one or more transport blocks. The HARQ-ACK may include at least a HARQ-ACK codebook containing one or more HARQ-ACK bits. The fact that the HARQ-ACK bit corresponds to one or more transport blocks may mean that the HARQ-ACK bit corresponds to a PDSCH containing the one or more transport blocks. The HARQ-ACK bit may indicate ACK or NACK corresponding to one CBG (Code Block Group) included in the transport block.

Scheduling Requests (SRs) may at least be used to request PUSCH resources for initial transmission. The scheduling request bit may be used to indicate either a positive SR (positive SR) or a negative SR (negative SR). The fact that the scheduling request bit indicates a positive SR is also referred to as "a positive SR is transmitted". A positive SR may indicate that the terminal device 1 requires a PUSCH resource for initial transmission. A positive SR may indicate that the scheduling request is Triggered by the upper layer. A positive SR may be transmitted when the higher layer instructs it to transmit a scheduling request. The fact that the scheduling request bit indicates a negative SR is also referred to as "a negative SR is transmitted". A negative SR may indicate that the terminal device 1 does not require a PUSCH resource for initial transmission. A negative SR may indicate that the scheduling request is not triggered by the upper layer. Negative SRs may be sent if the higher layer does not instruct them to send scheduling requests.

The channel state information may include at least a part or all of a channel quality index (CQI: Channel Quality Indicator), a precoder matrix index (PMI: Precoder Matrix Indicator), and a rank index (RI: Rank Indicator). CQI is an index related to channel quality (for example, propagation intensity), and PMI is an index indicating a precoder. RI is an index that indicates the transmission rank (or the number of transmission layers).

The PUCCH may support one or more PUCCH formats (PUCCH format 0 to PUCCH format 4). The PUCCH format may be mapped to the PUCCH and transmitted. The PUCCH format may be transmitted in PUCCH. The transmission of the PUCCH format may mean that the PUCCH is transmitted.

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

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

In FIG. 1, the following uplink physical signals are used in the uplink wireless communication. The uplink physical signal does not have to be used to transmit the information output from the upper layer, but it is used by the physical layer.
-UL DMRS (UpLink Demodulation Reference Si)
gnal)
・ SRS (Sounding Reference Signal)
-UL PTRS (UpLink Phase Tracking Reference Signal)

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

The SRS need not be associated with the transmission of PUSCH or PUCCH. The base station apparatus 3 may use SRS for measuring the channel state. The SRS may be transmitted at the end of the subframe in the uplink slot, or at a predetermined number of OFDM symbols from the end.

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

In FIG. 1, the following downlink physical channels are used in the downlink wireless communication from the base station device 3 to the terminal device 1. The downlink physical channel is used by the physical layer to transmit the information output from the upper layer.
・ PBCH (Physical Broadcast Channel)
-PDCCH (Physical Downlink Control Channel)
・ PDSCH (Physical Downlink Sharp Channel)

PBCH is a master information block (MIB: Master Info)
It is at least used to transmit rmation Block, BCH, Broadcast Channel). The PBCH may be transmitted based on a predetermined transmission interval. PBCH may be transmitted at intervals of 80 ms. PBCH may be transmitted at intervals of 160 ms. The content 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 configured to include 2, 3, or 4 OFDM symbols. The MIB may include information related to the 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 through which the PBCH is transmitted.

The PDCCH is at least used for the transmission of downlink control information (DCI: Downlink Control Information). The PDCCH may be transmitted including at least downlink control information. The PDCCH may include downlink control information. The downlink control information is also referred to as DCI format. The downlink control information may include at least one of a downlink grant (DL grant) and an uplink grant (UL grant). The DCI format used for PDSCH scheduling is also referred to as the downlink DCI format. The DCI format used for PUSCH scheduling is also referred to as the uplink DCI format. The downlink grant is also referred to as a downlink assignment (DL assignment) or a downlink assignment (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 configured to include at least part or all of 1A to 1F.
1A) DCI format specific field (Identifier for DCI forms field)
1B) Frequency domain resource allocation field (Frequency domain resource field)
1C) Time domain resource allocation field (Time domain resource)
associate field)
1D) Frequency hopping flag field (Frequency hopping flag field)
1E) MCS field (MCS field: Modulation and Coding Scheme field)
1F) First CSI request field (First CSI request file)
ld)

The DCI format specific field may be at least used to indicate whether the DCI format containing the DCI format specific field corresponds to one or more DCI formats. The one or more DCI formats may be given at least on the basis of DCI format 1_1, DCI format 1-11, DCI format 0_0, and / or part or all of DCI format 0_1.

The frequency domain resource allocation field may be at least used to indicate the frequency resource allocation for the PUSCH scheduled by the DCI format containing 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 at least used to indicate the allocation of time resources for the PUSCH scheduled by the DCI format containing the time domain resource allocation field.

The frequency hopping flag field may be at least used to indicate whether frequency hopping is applied to the PUSCH scheduled by the DCI format containing the frequency hopping flag field.

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

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

DCI format 0-1 is configured to include at least some or all of 2A to 2G.
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) Second CSI request field (Second CSI request fi)
eld)
2G) BWP field (BWP field)

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

The second CSI request field is at least used to direct CSI reporting. The size of the second CSI request field may be given at least based on the upper layer parameter ReportTriggerSize.

The downlink DCI format includes 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 specific field (Identifier for DCI forms field)
3B) Frequency domain resource allocation field (Frequency domain resource field)
3C) Time domain resource allocation field (Time domain resource)
associate field)
3D) Frequency hopping flag field (Frequency hopping flag field)
3E) MCS field (MCS field: Modulation and Coding Scheme field)
3F) First CSI request field (First CSI request file)
ld)
3G) PDSCH-to-HARQ feedback timing indicator field (PDSCH-to-HARQ feedback timing indicator field)
3H) PUCCH resource indicator field (PUCCH resource indicator field)

The timing instruction field from PDSCH to HARQ feedback may be a field indicating timing K1. When the index of the slot containing the last OFDM symbol of the PDSCH is slot n, the index of the PUCCH containing at least HARQ-ACK corresponding to the transport block contained in the PDSCH or the slot containing the PUSCH is n + K1. May be good. The last OFD of PDSCH
When the index of the slot containing the M symbol is slot n, the slot containing the first OFDM symbol of PUCCH containing at least HARQ-ACK corresponding to the transport block included in the PDSCH or the first OFDM symbol of PUSCH. The index 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 a HARQ instruction field.

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

The DCI format 1-1-1 is configured to include at least a part or all of 4A to 4J.
4A) DCI format specific field (Identifier for DCI forms field)
4B) Frequency domain resource allocation field (Frequency domain resource field)
4C) Time domain resource allocation field (Time domain resource)
associate field)
4D) Frequency hopping flag field (Frequency hopping flag field)
4E) MCS field (MCS field: Modulation and Coding Scheme field)
4F) First CSI request field (First CSI request file)
ld)
4G) PDSCH-to-HARQ feedback timing indicator field (PDSCH-to-HARQ feedback timing indicator field)
4H) PUCCH resource indicator field (PUCCH resource indicator field)
4J) BWP field (BWP field)

The BWP field may be used to indicate the downlink BWP to which the PDSCH scheduled in DCI format 1-11 is mapped.

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

The downlink control information may include common access information. Unified access common information is control information related to access, transmission / reception, etc. in a license-free frequency band. The Unified access common information may be information on a downlink subframe configuration (Subframe configuration for Unlicensed Access) (slot configuration: Slot configuration). The downlink subframe configuration (slot configuration) is the position of the OFDM symbol occupied in the subframe (slot) in which the PDCCH containing the downlink subframe configuration (slot configuration) information is arranged, and / or the downlink. Indicates the position of the OFDM symbol occupied in the next subframe (slot) of the subframe (slot) in which the PDCCH containing the information of the subframe configuration (slot configuration) of is placed. The downlink physical channel and the downlink physical signal are transmitted and received in the occupied OFDM symbol. The Unified access common information may be information on the uplink subframe configuration (UL duration and offset) (slot configuration). In the uplink subframe configuration (slot configuration), the uplink subframe (uplink slot) starts based on the subframe (slot) in which the PDCCH containing the information of the uplink subframe configuration (slot configuration) is arranged. Indicates the position of the subframe (slot) to be created and the number of subframes (slots) of the uplink subframe (uplink slot). The terminal device 1 is not required to receive the downlink physical channel and the downlink physical signal in the subframe (slot) indicated by the information of the uplink subframe configuration (slot configuration).

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). For example, Unified access common information is transmitted and received by PDCCH including CC-RNTI (Common Control-Radio Network Identifier Identifier).

In various aspects of this embodiment, unless otherwise stated, the number of resource blocks indicates the number of resource blocks in the frequency domain.

The downlink grant is at least used for scheduling one PDSCH in one serving cell. Uplink grants are used at least for scheduling one PUSCH in one serving cell.

In addition, various DCI formats may further include fields different from the above-mentioned fields. For example, a field (NFI: New Feedback Indicator field) indicating whether or not the HARQ-ACK information of PDSCH is correctly detected may be included. A field (NFI field) indicating whether or not to erase (flash) the HARQ-ACK bit stored in a recording medium such as a memory may be included. A field (NFI field) indicating whether or not to include the 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 (associates) may be included. A field (RPGI: Request PDSCH Group ID field) indicating a PDSCH group instructed to transmit HARQ-ACK information may be included. A field (C-DAI: Counter Downlink Assignment Index field) indicating the cumulative number of PDCCHs transmitted may be included. A field (T-DAI: Total Downlink Assignment Index field) indicating the total number of PDCCHs transmitted 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 PDSCH may be indicated at least based on the DCI format used to schedule the PDSCH. For example, a field indicating PGI (PGI field) may be included in the DCI format. For example, the PDSCH group may be a set of PDSCHs having the same PGI (PDSCH group identifier). The PDSCH group may be one PDSCH or a set of one or more PDSCHs associated with the same PGI. The number of PDSCH groups set for the terminal device 1 may be 1, may be 2, may be 3, may be 4, or any other. It may be an integer greater than or equal to 0.

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

The value of K1 (information or parameter indicated by the timing indicator field from PDSCH to HARQ feedback) indicated by the DCI format included in the PDCCH may be numerical or non-numerical. ) May be. Here, the numerical value means a value represented by a numerical value, for example, {0, 1, 2, ... .. .. , 15}. A non-numeric value may mean a non-numeric value or may mean no numerical value. Hereinafter, the operation of the numerical value of K1 and the non-numerical value of K1 will be described. For example, the PDSCH scheduled in the DCI format is transmitted in the base station apparatus 3 in slot n and received in the terminal apparatus 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 in slot n + K1 via PUCCH or PUSCH. If the value of K1 indicated by the DCI format is non-numeric, the terminal device 1 may postpone reporting the HARQ-ACK information corresponding to the PDSCH. If the DCI format containing the PDSCH scheduling information indicates a non-numeric value of K1, the terminal device 1 may postpone reporting the HARQ-ACK information corresponding to the PDSCH. For example, the terminal device 1 stores the HARQ-ACK information in a recording medium such as a memory, does not transmit (report) the HARQ-ACK information via the next PUCCH or PUSCH, and does not transmit (report) the HARQ-ACK information other than the above-mentioned DCI format. The transmission of the HARQ-ACK information may be triggered to transmit (report) the HARQ-ACK information based on at least the DCI format.

The non-numeric value of K1 may be included in the sequence of upper layer parameters. The upper layer parameter may be the upper layer parameter dl-DataToUL-ACK. The upper layer parameter may be an upper layer parameter different from the upper layer parameter dl-DataToUL-ACK. The value of K1 may be a value indicated by a timing instruction field from PDSCH to HARQ feedback included in the DCI format in the series of upper layer parameters. For example, it is assumed that the sequence of upper layer parameters is set to {0,1,2,3,4,5,15, non-numeric value}, and the number of bits of the timing instruction field from PDSCH to HARQ feedback is 3. If so, the code point “000” in the timing instruction field from PDSCH to HARQ feedback may indicate that the value of K1 is 0, and the code point “001” indicates that the value of K1 is 1. Alternatively, the code point "111" may indicate that the value of K1 is a non-numeric value. For example, it is assumed that the sequence of upper layer parameters is set to {non-numeric value, 0,1,2,3,4,5,15} and the number of bits of the timing instruction field from PDSCH to HARQ feedback is 3. If so, the code point “000” in the timing instruction field from PDSCH to HARQ feedback may indicate that the value of K1 is a non-numeric value, and the code point “001” may indicate that the value of K1 is 0. This may be indicated, or the code point “111” may indicate that the value of K1 is 15.

One physical channel may be mapped to one serving cell. One physical channel may be mapped to one BWP set for one carrier contained in one serving cell.

The terminal device 1 has one or more control resource sets (CORESET: Control).
REsource SET) may be set. The terminal device 1 monitors the PDCCH in one or more control resource sets (monitor). Here, monitoring PDCCH in one or more control resource sets may include monitoring one or more PDCCHs corresponding to each of one or more control resource sets. The PDCCH may include one or more sets of PDCCH candidates and / or PDCCH candidates. Monitoring the PDCCH may also include monitoring and detecting the PDCCH and / or the DCI format transmitted via the PDCCH.

The control resource set may indicate a time frequency domain in which one or more PDCCHs can be mapped. The control resource set may be an area in which the terminal device 1 monitors the PDCCH. A control resource set is a localized resource.
It may be composed of ce). 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 control resource set mapping unit 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 control resource sets to resource blocks may be given at least based on higher layer parameters. The upper layer parameter may include a bitmap for a group of resource blocks (RBG: Resource Block Group). The group of resource blocks may be given by six consecutive resource blocks.

The number of OFDM symbols that make up the control resource set may be given at least based on the upper layer parameters.

A certain control resource set may be a common control resource set (Common control resource set). The common control resource set may be a control resource set that is commonly set for a plurality of terminal devices 1. The common control resource set may be given at least based on the MIB, the first system information, the second system information, the common RRC signaling, and some or all of the cell IDs. For example, the time and / or frequency resources of the control resource set set to monitor the PDCCH used for scheduling the first system information may be given at least based on the MIB.

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

A control resource set is a dedicated control resource set.
It may be a roll resource set). The dedicated control resource set may be a control resource set that is set to be used exclusively for the terminal device 1. The dedicated control resource set may be given based on at least some or all of the dedicated RRC signaling and the value of 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 each CCE may be given an index (CCE index).

The set of PDCCH candidates monitored by the terminal device 1 is a search area (Search).
It may be defined from the viewpoint of space). That is, the set of PDCCH candidates monitored by the terminal device 1 may be given by the search area.

The search area is a P of one or more aggregation levels.
It may be configured to include one or more DCCH candidates. The aggregation level of PDCCH candidates may indicate the number of CCEs constituting the PDCCH. PDDCH candidates may be mapped to one or more CCEs.

The terminal device 1 may monitor at least one or a plurality of search areas in a slot in which DRX (Discontinuity reception) is not set. DRX may be given at least based on the upper layer parameters. The terminal device 1 may monitor at least one or more search area sets (Search space set) in slots where DRX is not set. A plurality of search area sets may be configured in the terminal device 1. An index (search area set index) may be assigned to each search area set.

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

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

The search region may have two types, CSS (Comon Search Space, common search region) and USS (UE-specific Search Space). The CSS may be a search area that is commonly set for a plurality of terminal devices 1. The USS may be a search area that includes settings that are used exclusively for the individual terminal device 1. The CSS may be given at least based on the synchronization signal, MIB, first system information, second system information, common RRC signaling, dedicated RRC signaling, cell ID, and the like. USS may be given at least based on dedicated RRC signaling and / or values of C-RNTI. The CSS may be a search area set as a common resource (control resource element) for a plurality of terminal devices 1. The USS may be a search area set in a resource (control resource element) for each individual terminal device 1.

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

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

RNTI is 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), INT-RNTI (Interruption-RNTI) may be included. SI-RNTI is at least used for scheduling PDSCHs transmitted containing system information. P-RNTI is at least used for scheduling PDSCH transmitted containing information such as paging information and / or system information change notifications. C-RNTI is at least used to schedule user data for RRC-connected terminal equipment 1. Temporary C-RNTI is at least used for scheduling random access messages 4. Temporary C-RNTI is at least used to schedule a PDSCH that contains data that maps to CCCH in a logical channel. RA-RNTI is at least used for scheduling random access message 2. CC-RNTI is at least used for transmitting and receiving control information of Unlicensed access. INT-RNTI is at least used to indicate pre-emption on the downlink.

Note that the PDCCH and / or DCI included in the CSS does not include a CIF (Carrier Indicator Field) indicating which serving cell (or which component carrier) the PDCCH / DCI schedules the PDSCH or PUSCH. You may.

When carrier aggregation (CA: carrier aggregation) is set for the terminal device 1 to aggregate a plurality of serving cells and / or a plurality of component carriers for communication (transmission and / or reception), a predetermined value is provided. The PDCCH and / or DCI contained in the USS for a serving cell (predetermined component carrier) includes a CIF indicating which serving cell and / or which component carrier the PDCCH / DCI is scheduling a PDSCH or PUSCH for. May be good.

When communicating with the terminal device 1 using one serving cell and / or one component carrier, the PDCCH / DCI included in the USS includes which serving cell and / or the PDCCH / DCI. Alternatively, a CIF indicating which component carrier the PDSCH or PUSCH is scheduled for may not be included.

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

The physical resource of the search area is the control channel configuration unit (CCE: Control Cha).
It is composed of nnel Element). CCE is composed of a predetermined number of resource element groups (REG: Resource Element Group). For example, CCE may consist of 6 REGs. The REG may be composed of one PRB (Physical Resource Block) 1 OFDM symbol. That is, the REG may be configured to include 12 resource elements (RE: Resource Elements). The PRB is also simply referred to as an RB (Resource Block).

PDSCH is at least used to transmit / receive transport blocks. The PDSCH may at least be used to send / receive a random access message 2 (random access response). The PDSCH may at least be used 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 signal does not have to be used to transmit the information output from the upper layer, but it is used by the physical layer.
-Synchronization signal (SS: Synchronization signal)
-DL DMRS (DownLink Demodulation Reference
Signal)
-CSI-RS (Channel State Information-Reference Signal)
-DL PTRS (DownLink Phase Tracking Reference)
eSignal)

The synchronization signal is used by the terminal device 1 to synchronize the downlink frequency domain and / or the time domain. The synchronization signal is PSS (Primary System Science).
ation Signal) and SSS (Secondary Synchronization Signal) are included.

The SS block (SS / PBCH block) is composed of PSS, SSS, and at least a part or all of PBCH.

DL DMRS is associated with the transmission of PBCH, PDCCH, and / or PDSCH. DL DMRS is multiplexed on PBCH, PDCCH, and / or PDSCH. The terminal device 1 may use the PBCH, the PDCCH, or the DL DMRS corresponding to the PDSCH to perform propagation path correction of the PBCH, PDCCH, or PDSCH.

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

The PTRS may be at least the signal used to compensate for phase noise. The pattern of PTRS assumed by the terminal device is the upper layer parameter and / or D.
It may be given at least based on CI.

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

The downlink physical channel and the downlink physical signal are also referred to as a downlink physical signal. Uplink physical channels and uplink physical signals are also referred to as uplink signals. The downlink signal and the uplink signal are also collectively referred to as a physical signal. The downlink signal and the uplink signal are also collectively referred to as a signal. The downlink physical channel and the uplink physical channel are collectively referred to as a physical channel. The downlink physical signal and the uplink physical signal are collectively referred to as a physical signal.

BCH (Broadcast Channel), UL-SCH (Uplink-Sh)
The ared Channel) and DL-SCH (Downlink-Shared Channel) are transport channels. The channel used in the medium access control (MAC) layer is called a transport channel. The unit of transport channel used in the MAC layer is also called a transport block (TB) or MAC PDU. HARQ (Hybrid Automatic Repeat request) for each transport block in the MAC layer
st) is controlled. A transport block is a unit of data that the MAC layer passes to the physical layer (deliver). 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 / transmit) signals of the upper layer in the upper 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) in the radio resource control (RRC: Radio Resource Control) layer. .. Further, the base station device 3 and the terminal device 1
May transmit and receive MAC CE (Control Element) in the MAC layer. Here, RRC signaling and / or MAC CE is also referred to as a higher layer signal (higher layer signaling).

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

BCCH (Broadcast Control Channel), CCCH (Common Control Channel), and DCCH (Dedicated C)
"ontrol Channel" is a logical channel. For example, BCCH is M
An upper layer channel used to transmit / receive IB. Further, CCCH (Common Control Channel) is an upper layer channel used for transmitting / receiving common information in a plurality of terminal devices 1. Here, CCCH may be used, for example, for a terminal device 1 that is not RRC-connected. Further, the DCCH (Dedicated Control Channel) is at least an upper layer channel used for transmitting / receiving dedicated control information (dedicated control information) to the terminal device 1. Here, the DCCH may be used, for example, for the terminal device 1 connected by RRC.

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

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

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

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

A component carrier may be set to a licensed band. Some serving cells may be set in the licensed band. Here, setting a certain component carrier (or a certain serving cell) to the license band may include at least a part or all of the following settings 1 to 3.
Setting 1: An upper layer parameter is given to indicate that a component carrier (or a serving cell) operates in the licensed band, or an unlicensed band is given to a component carrier (or a serving cell). ) Is not given. Setting 2: A component carrier (or a serving cell) is set to operate in the licensed band, or a certain serving cell is set to operate in the unlicensed band. A component carrier (or a serving cell) is not set Setting 3: A component carrier (or a serving cell) is included in the licensed band, or a component carrier (or a serving cell) is not included in the unlicensed band

The license band may be a band in which a radio station license is required for a terminal device that operates (expected) in the license band. The licensed band may be a band in which only terminal devices manufactured by a business operator (business entity, business, group, company) holding a radio station license are permitted to operate. The unlicensed band may be a band that does not require a channel access procedure prior to transmitting a physical signal.

The unlicensed band may be a band in which a radio station license is not required for a terminal device that operates (expected) in the unlicensed band. The unlicensed band is a band in which a terminal device manufactured by a business operator holding a radio station license and / or a part or all of a business operator not holding a radio station license is permitted to operate. Good. The unlicensed band may be a band that requires a channel access procedure prior to transmitting a physical signal.

Whether or not NR-U is applied to a component carrier (or a serving cell) is determined by at least a band in which the component carrier (or the serving cell) can operate in an unlicensed band (for example, an unlicensed band). It may be decided based on whether or not it is set to (a band that can be operated only by). For example, a list of bands designed for NR or carrier aggregation of NR may be specified. For example, if one or more bands in the list are included in a band that can be operated in the unlicensed band (for example, a band that can be operated only in the unlicensed band), the NR-U is included in the band. May be applied. Further, if one or more bands in the list are not included in the band that can be operated in the unlicensed band (for example, the band that can be operated only in the unlicensed band), the NR-U is included in the band. Is not applied, and normal NR (for example, NR of release 15 or NR other than NR-U of release 16) may be applied.

Whether or not NR-U is applied to a component carrier (or a serving cell) is determined only in a band in which the component carrier (or the serving cell) can operate NR-U (for example, NR-U). It may be decided based on whether or not it is set to an operable band). For example, if one or more bands in the list are included in a band that can be operated by NR-U (for example, a band that can be operated only by NR-U), the NR-U is included in the band. May be applied. Further, if one or more bands in the list are not included in the band that can be operated by NR-U (for example, the band that can be operated only by NR-U), the band is included in NR-U. Is not applied, and normal NR (for example, NR of release 15 or NR other than NR-U of release 16) may be applied.

Whether or not NR-U is applied to a certain component carrier (or a certain serving cell) may be determined based on the information contained in the MIB or system information. For example, if the MIB (or system information) contains information indicating whether or not to apply NR-U, and the information indicates that NR-U is applied, the MIB (or said). NR-U may be applied to the serving cell to which the system information) corresponds. On the other hand, if the information does not indicate that NR-U is applied, NR-U is not applied to the serving cell to which the MIB (or the system information) corresponds, and normal NR is applied. May be good. Alternatively, it may indicate whether or not the information can be operated in a license-free band.

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

Hereinafter, the description will be made on the assumption that the component carrier is set to the licensed band or the unlicensed band. Note that "the component carrier is set to the licensed band" may mean "the serving cell is set to the licensed band", and "the component carrier is set to the unlicensed band" means " The serving cell may be set to the unlicensed band.

Whether the terminal device 1 receives the first SS / PBCH block or the second SS / PBCH block in a certain component carrier depends on whether NR-U is applied in the certain component carrier. And it may be given at least on a part or all of whether or not the component carrier is set in the unlicensed band.

For example, if a component carrier is set in the licensed band, the terminal device 1 may receive the first SS / PBCH block. Further, when a certain component carrier is set to the license band, the terminal device 1 may receive the first PDCCH in the first type 0 PDCCH common search area set. Further, when a certain component carrier is set to the license band, the base station apparatus 3 may transmit the first SS / PBCH block. Further, when a certain component carrier is set to the license band, the base station apparatus 3 may receive the first PDCCH in the first type 0 PDCCH common search area set.

If a component carrier is set to an unlicensed band, the terminal device 1 may receive a second SS / PBCH block. Further, when a certain component carrier is set to the unlicensed band, the terminal device 1 may receive the second PDCCH in the second type 0 PDCCH common search area set. Further, when a certain component carrier is set to the unlicensed band, the base station apparatus 3 may transmit the second SS / PBCH block. Further, when a certain component carrier is set to the unlicensed band, the base station apparatus 3 may receive the second PDCCH in the second type 0 PDCCH common search area set.

For example, if NR-U is not applied to a component carrier and the component carrier is set to the licensed band, the terminal device 1 may receive the first SS / PBCH block. Further, when NR-U is not applied to a certain component carrier and the component carrier is set to the license band, the terminal device 1 receives the first PDCCH in the first type 0 PDCCH common search area set. You may. Further, when NR-U is not applied to a certain component carrier and the component carrier is set to the license band, the base station apparatus 3 may transmit the first SS / PBCH block. Further, when NR-U is not applied to a certain component carrier and the component carrier is set to the license band, the base station apparatus 3 receives the first PDCCH in the first type 0 PDCCH common search area set. You may.

For example, if NR-U is not applied to a component carrier and the component carrier is set to an unlicensed band, the terminal device 1 may receive a second SS / PBCH block. Further, when NR-U is not applied to a certain component carrier and the component carrier is set to the unlicensed band, the terminal device 1 receives the first PDCCH in the second type 0PDCCH common search area set. You may. Further, when NR-U is not applied to a certain component carrier and the component carrier is set to the unlicensed band, the base station apparatus 3 may transmit a second SS / PBCH block. Further, when NR-U is not applied to a certain component carrier and the component carrier is set to the unlicensed band, the base station apparatus 3 sets the first PDCCH in the second type 0 PDCCH common search area set. You may receive it.

For example, if NR-U is applied in a component carrier and the component carrier is set in the licensed band, the terminal device 1 may receive the second SS / PBCH block. Further, when NR-U is applied to a certain component carrier and the component carrier is set to the license band, the terminal device 1 receives the first PDCCH in the second type 0PDCCH common search area set. May be good. Further, when NR-U is applied to a certain component carrier and the component carrier is set to the license band, the base station apparatus 3 may transmit a second SS / PBCH block. Further, when NR-U is applied to a certain component carrier and the component carrier is set to the license band, the base station apparatus 3 receives the first PDCCH in the second type 0PDCCH common search area set. You may.

For example, if NR-U is applied in a certain component carrier and the component carrier is set to the unlicensed band, the terminal device 1 may receive the second SS / PBCH block. Further, when NR-U is applied to a certain component carrier and the component carrier is set to the unlicensed band, the terminal device 1 receives the first PDCCH in the second type 0PDCCH common search area set. You may. Further, when NR-U is applied to a certain component carrier and the component carrier is set to the unlicensed band, the base station apparatus 3 may transmit the second SS / PBCH block. Further, when NR-U is applied to a certain component carrier and the component carrier is set to the unlicensed band, the base station apparatus 3 receives the first PDCCH in the second type 0 PDCCH common search area set. You may.

Hereinafter, a configuration example of the terminal device 1 according to one aspect of the present embodiment will be described.

FIG. 4 is a schematic block diagram showing the configuration of the terminal device 1 according to one aspect of the present embodiment. As shown in the figure, the terminal device 1 includes a wireless transmission / reception unit 10 and an upper layer processing unit 14. The radio transmission / reception unit 10 includes at least a part or all of an antenna unit 11, an RF (Radio Frequency) unit 12, and a baseband unit 13. The upper layer processing unit 14 includes at least a part or all of the medium access control layer processing unit 15 and the radio resource control layer processing unit 16. The wireless transmission / reception unit 10 is also referred to as a transmission unit, a reception unit, or a physical layer processing unit. The transmitter may transmit physical signals and / or physical channels. The physical signal may include an uplink demodulation reference signal and / or a sounding reference signal. The physical channel may include PRACH, PUCCH, and / or PUSCH. The transmission unit may transmit a part or all of PRACH, PUCCH, and PUSCH. The receiver may receive physical signals and / or physical channels. The physical signal may include a downlink demodulation reference signal, a channel state information reference signal, and / or a synchronization signal. The physical channel may include PBCH, PDCCH, and / or PDSCH. The receiving unit may receive PBCH, PDCCH, and / or a part or all of PDSCH.

The upper layer processing unit 14 outputs the uplink data (transport block) generated by the user's operation or the like to the wireless transmission / reception unit 10. The upper layer processing unit 14 includes a MAC layer, a packet data integration protocol (PDCP: Packet Data Convergence Protocol) layer, and a wireless link control (RLC: Radio Link Control).
ol) The layer and the RRC layer are processed.

The medium access control layer processing unit 15 included in the upper layer processing unit 14 processes the MAC layer.

The radio resource control layer processing unit 16 included in the upper layer processing unit 14 processes the RRC layer. The wireless resource control layer processing unit 16 manages various setting information / parameters of its own device. The radio resource control layer processing unit 16 sets various setting information / parameters based on the signal of the upper layer received from the base station apparatus 3. That is, the radio resource control layer processing unit 16 sets various setting information / parameters based on the information indicating various setting information / parameters received from the base station apparatus 3. The setting information may include information related to processing or setting of a physical channel, a physical signal (that is, a physical layer), a MAC layer, a PDCP layer, an RLC layer, and an RRC layer. The parameter may be an upper layer parameter.

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

The RF unit 12 converts the signal received via the antenna unit 11 into a baseband signal by orthogonal demodulation (down conversion), 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 uses CP (Cyclic Pr) from the converted digital signal.
The portion corresponding to efix) is removed, and the signal from which the CP is removed is subjected to a fast Fourier transform (FFT) to extract a signal in the frequency domain.

The baseband unit 13 transforms the data into an inverse fast Fourier transform (IFFT: Inverse F).
ast Fourier Transfer) to generate an OFDM symbol, add CP to the generated OFDM symbol, generate a baseband digital signal, and convert the baseband digital signal to 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 excess frequency components from the analog signal input from the baseband unit 13, upconverts the analog signal to the carrier frequency, and transmits the analog signal via the antenna unit 11. To do. Further, the RF unit 12 amplifies the electric power. Further, the RF unit 12 may have a function of controlling the transmission power. The RF unit 12 is also referred to as a transmission power control unit.

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

FIG. 5 is a schematic block diagram showing the configuration of the base station device 3 according to one aspect of the present embodiment. As shown in the figure, the base station apparatus 3 includes a wireless 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 wireless transmission / reception unit 30 is also referred to as a transmission unit, a reception unit, or a physical layer processing unit. The receiver may receive physical signals and / or physical channels. The physical signal may include an uplink demodulation reference signal and / or a sounding reference signal. The physical channel may include PRACH, PUCCH, and / or PUSCH. The transmitting unit may receive a part or all of PRACH, PUCCH, and PUSCH. The transmitter may transmit physical signals and / or physical channels. The physical signal may include a downlink demodulation reference signal, a channel state information reference signal, and / or a synchronization signal. The physical channel may include PBCH, PDCCH, and / or PDSCH. The transmitter may transmit part or all of PBCH, PDCCH, and / or PDSCH.

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

The medium access control layer processing unit 35 included in the upper layer processing unit 34 processes the MAC layer.

The radio resource control layer processing unit 36 included in the upper layer processing unit 34 processes the RRC layer. The wireless resource control layer processing unit 36 generates downlink data (transport block), system information, RRC message, MAC CE, etc. arranged in the PDSCH, or acquires them from a higher-level node and outputs them to the wireless transmission / reception unit 30. .. Further, the radio resource control layer processing unit 36 manages various setting information / parameters of 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 / notifies information indicating various setting information / parameters. The setting information may include information related to processing or setting of a physical channel, a physical signal (that is, a physical layer), a MAC layer, a PDCP layer, an RLC layer, and an RRC layer. The parameter may be an upper layer parameter.

Since the function of the wireless transmission / reception unit 30 is the same as that of the wireless transmission / reception unit 10, the description thereof will be omitted.

Each portion of the terminal device 1 with reference numerals 10 to 16 may be configured as a circuit. Each portion of the base station apparatus 3 with reference numerals 30 to 36 may be configured as a circuit.

The terminal device 1 has a carrier sense prior to transmitting a physical signal.
) May be carried out. Further, the base station apparatus 3 may perform carrier sense prior to the transmission of the physical signal. The carrier sense may be to perform Energy detection on a radio channel. Whether or not the physical signal can be transmitted may be given based on the carrier sense performed prior to the transmission of the physical signal. For example, if the amount of energy detected by the carrier sense performed prior to the transmission of the physical signal is greater than a predetermined threshold, the physical channel may not be transmitted or cannot be transmitted. May be determined. Further, when the amount of energy detected by the carrier sense performed prior to the transmission of the physical signal is smaller than a predetermined threshold value, the physical channel may be transmitted or can be transmitted. It may be judged. Further, when the amount of energy detected by the carrier sense performed prior to the transmission of the physical signal is equal to a predetermined threshold value, the transmission of the physical channel may or may not be performed. .. That is, when the amount of energy detected by the carrier sense performed prior to the transmission of the physical signal is equal to the predetermined threshold value, it may be determined that the transmission is impossible or the transmission is possible. Good.

The procedure in which the transmission availability of a physical channel is given based on the carrier sense is also referred to as LBT (Listen Before Talk). The situation in which it is determined that the physical signal cannot be transmitted as a result of the LBT is also referred to as a busy state or a busy state. For example, the busy state may be a state in which the amount of energy detected by carrier sense is larger than a predetermined threshold value. Further, the situation in which it is determined that the physical signal can be transmitted as a result of LBT is also referred to as an idle state or an idle. For example, the idle state may be a state in which the amount of energy detected by carrier sense is smaller than a predetermined threshold value. The determination that the transmission of a physical signal is impossible as a result of LBT is also referred to as LBT fileure.

The value of the section (channel occupancy section) (Channel Occupancy Time: COT) in which the channel is continuously occupied may be predetermined by the country, or may be predetermined for each frequency band. The base station apparatus 3 may notify the terminal apparatus 1 of the channel occupied section. The terminal device 1 recognizes the length of the channel occupied section, and can grasp the timing at which the channel occupied section ends. For example, the maximum value of COT may be any of 2 ms, 3 ms, 6 ms, 8 ms, and 10 ms.

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

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. ..

The quasi-static scheduling (SPS) PDSCH may be configured by upper layer parameters for each BWP in a serving cell. Activation or deactivation of SPS PDSCH may be performed for each serving cell. Activation or deactivation of SPS PDSCH may be performed independently between serving cells. The SPS (Semi-Persistent Scheduling) PDSCH may be a PDSCH quasi-statically scheduled to the terminal device 1.

In the downlink SPS PDSCH, the downlink assignment (DL assignment) may be given by the PDCCH and stored based on the L1 signaling that directs the activation of the SPS. In the downlink SPS PDSCH, the downlink assignment (DL assignment) may be given by the PDCCH and cleared based on the L1 signaling indicating the inactivation of the SPS.

When the SPS PDSCH is configured, the upper layer (RRC) may configure some or all of the parameters of cs-RNTI, nrovHRQ-Processes, and periodity. Here, cs-RNTI may be the value of RNTI for activating SPS PDSCH, deactivating SPS PDSCH, or retransmitting SPS PDSCH. Also, nrovHRQ-Processes may be the number of HARQ processes configured for SPS PDSCH. Also, the periopathy may be a period of DL association configured for the SPS PDSCH.

When the SPS PDSCH is released or deactivated by the upper layer, the corresponding part or all configuration may be released. When the SPS PDSCH is released or deactivated by the upper layer, the corresponding configuration may be initialized in part or in whole.

After the DL assignment for the SPS PDSCH is configured, the MAC entity _{may consider that the NDAth} DL assignment occurs sequentially in the _{slot n DA slot shown in Equation 1. Here, n DAslot} may be given by _{(numberOfSlotsPerFrame * SFN DA + n DAslot} ) = {(numberOfSlotsPerFrame * SFN start_time + slot start_time) + N DA * periodicity * numberOfSlotsPerFrame / 10} mod (1024 * numbeOfSlotsPerFrame). Here, the numberOfSlotsPerFrame may be the number of consecutive slots included in one Radio frame. The numberOfSlotsPerFlame may be the number of slots that make up one Radio frame. The numberOfSlotsPerFlame may be 10, 20, 40, 80, or 160. Further, the SFN _DA may be a Radio frame number including the slot nDA slot. The SFN _{start_time} may be a Radio frame number that includes the slot in which the DL assert has been initialized (activated) or reinitialized (reactivated) and the SPS PDSCH has been transmitted for the first time. The slot _{start_time} may be the slot number to which the SPS PDSCH is transmitted for the first time after the DL assert has been initialized (activated) or reinitialized (reactivated). Periodicity may be given by the upper layer parameters. The periopathy may be 10, 20, 32, 40, 64, 80, or 80. It may be 128, 160, 320, or 640. Here, the Radio frame may be a frame having a length of 10 ms.

For the HARQ process for SPS PDSCH, one or more HARQ processes may be set by the upper layer parameter nrov HARQ-Processes. The HARQ process ID included in the HARQ process for the SPS PDSCH may be shared with the HARQ process ID included in the HARQ process for the DL grant scheduled in the DCI format. The HARQ process ID included in the HARQ process for the SPS PDSCH may be different from the HARQ process ID included in the HARQ process for the DL grant scheduled in the DCI format.

The terminal device 1 may report (transmit) the HARQ-ACK information corresponding to the SPS PDSCH to the base station device 3 using the PUCCH. The PUCCH may be composed of PUCCH format 0. Further, the PUCCH may be composed of the PUCCH form1. The PUCCH may be composed of PUCCH form 0 for NR-U. The PUCCH may be composed of PUCCH form1 for NR-U.

The PUCCH resource (PUCCH resource) for transmitting the HARQ-ACK information corresponding to the SPS PDSCH may be configured based on the DCI format that activates the SPS PDSCH. The terminal device 1 may continue to use the PUCCH resource configured by the DCI format until the SPS PDSCH is deactivated when the SPS PDSCH is activated. The terminal device 1 receives information (parameters) regarding the DL association contained in the DCI format used for activating the SPS PDSCH from the activation of the SPS PDSCH to the deactivation of the SPS PDSCH. You may continue to use it for.

The terminal device 1 does not have to expect the reception of PDCCH excluding the PDCCH including the DCI format that activates and deactivates the SPS PDSCH for scheduling the SPS PDSCH. The terminal device 1 does not have to expect the reception of PDCCH excluding the PDCCH containing the DCI format that activates and deactivates the SPS PDSCH for scheduling new transmission of the SPS PDSCH.

FIG. 6 is a diagram showing an example of reception of SPS PDSCH in this embodiment. 6, the period of SPS PDSCH is assumed to _{p x.} PDCCH601 may be a PDCCH containing a DCI format that activates the SPS PDSCH. SPS PDSCH 602 is the first PDSCH activated by the DCI format contained in PDCCH 601. The terminal device 1 may determine the slot in which the PUCCH for transmitting the HARQ-ACK information corresponding to the SPS PDSCH 602 exists, based on the value of K1 included in the DCI format in which the SPS PDSCH included in the PDCCH 601 is activated. .. For example, since K1 is 1 in FIG. 6, the terminal device 1 is set to HARQ-ACK corresponding to SPS PDSCH 602 in Slot # m + 1 after one slot with reference to the slot in which the terminal device 1 received SPS PDSCH 602. Information may be transmitted using PUCCH603.

In FIG. 6, the SPS PDSCH 604 and SPS PDSCH 606 may be PDSCHs without PDCCH instructing the scheduling of PDSCHs. The terminal device 1 may determine the slot in which the PUCCH for transmitting the HARQ-ACK information corresponding to the SPS PDSCH 604 exists based on the value of K1 included in the DCI format in which the SPS PDSCH included in the PDCCH 601 is activated. .. For example, since K1 is 1 in FIG. 6, the terminal device 1 has a HARQ corresponding to the SPS PDSCH 604 after one slot with reference to the slot in which the terminal device 1 has received the SPS PDSCH 604, that is, Slot # m + p _{x + 1.} -ACK information may be transmitted using PUCCH605. Further, the terminal device 1 determines the slot in which the PUCCH for transmitting the HARQ-ACK information corresponding to the SPS PDSCH606 exists, based on the value of K1 included in the DCI format in which the SPS PDSCH included in the PDCCH601 is activated. May be good. For example, since K1 is 1 in FIG. 6, the terminal device 1 has a HARQ corresponding to the SPS PDSCH606 _{one slot later, that is, Slot # m + jp x + 1 with respect to the slot in which the terminal device 1 received the SPS PDSCH606.} -ACK information may be transmitted using PUCCH607. Here, j may be an integer of 1 or more.

In FIG. 6, the PDCCH 608 may be a PDCCH containing a DCI format that deactivates the SPS PDSCH. The terminal device 1 may generate HARQ-ACK information corresponding to whether the SPS PDSCH has been successfully deactivated by the PDCCH 608. That is, the terminal device 1 may generate an ACK if the SPS PDSCH is successfully deactivated by the PDCCH 608. The terminal device 1 may generate a NACK if the SPS PDSCH fails to be deactivated by the PDCCH 608. The terminal device 1 may determine the HARQ-ACK information corresponding to the deactivation of the SPS PDSCH based on the value of K1 contained in the DCI format containing the SPS PDSCH contained in the PDCCH 601. For example, in FIG. 6, since K1 included in the DCI format included in the PDCCH 608 is 1, the terminal device 1 has _{SPS PDSCH after one slot with reference to the slot receiving the PDCCH 608, that is, Slot # m + jp x} + 3. HARQ-ACK information corresponding to the deactivation of is may be transmitted using PUCCH609.

The terminal device 1 may report the HARQ-ACK information corresponding to the SPS PDSCH release (release) to the base station device 3 by using the HARQ-ACK codebook. The terminal device 1 is indicated by the value of the DCI format 1_0 corresponding to the SPS PDSCH release (release) or the PDSCH-to-HARQ feedback timing indicator field (PDSCH-to-HARQ_fedback timing indicator field) included in the DCI format 1-11. The HARQ-ACK information corresponding to the slot may be reported to the base station apparatus 3 using the HARQ-ACK codebook.

The SPS PDSCH release may be performed by the DCI format included in the PDCCH.

Scheduling activation when the DCI format CRC is scrambled with the CS-RNTI given by the upper layer parameter cs-RNTI and the new data indicator field of the transport block is set to 0. ) Or for scheduling release, the terminal device 1 may validate the downlink SPS assignment PDCCH (DL SPS assignment PDCCH) or the uplink grant type 2 PDCCH (UL grant Type 2 PDCCH). .. Scheduling activation may be performed at least based on the activation and the HARQ process ID (HARQ process number), redundancy version included in the DCI format. Scheduling releases include the HARQ process number (HARQ process ID) (HARQ process number), redundancy version, modulation and coding scheme, and resource block assignment (resour) included in the activation and DCI format. It may be done at least on the basis of (block assignment). {A mod B} is a modulo operation. The modulo operation is a function that outputs the remainder when A is divided by B, and is expressed as {A mod B}. For example, (5 mod 4) = 1.

If the downlink data is successfully decrypted, an ACK may be generated for the downlink data. If the downlink data is not successfully decoded, a NACK may be generated for the downlink data. HARQ-ACK may include at least the HARQ-ACK bits corresponding to one transport block. The HARQ-ACK bit may indicate ACK (ACKnowledgement) or NACK (Negative-ACKnowledgement) corresponding to one or more transport blocks. The HARQ-ACK may include at least a HARQ-ACK codebook containing one or more HARQ-ACK bits. Corresponding to one or more transport blocks of the HARQ-ACK bit may mean that the HARQ-ACK bit corresponds to a PDSCH containing the one or more transport blocks.

The HARQ control corresponding to 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 may include a field indicating the HARQ process identifier. The HARQ process identifier is also referred to as the HARQ process ID.

NDI (New Data Indicator) may be indicated in DCI format for each HARQ process. For example, the NDI field may be included in the DCI format (DL assessment) containing the PDSCH scheduling information. The NDI field may be 1 bit. The terminal device 1 may store (store) the value of NDI for each HARQ process. The base station device 3 may store (store) the NDI value for each HARQ process for each terminal device 1. The terminal device 1 may update the stored NDI value using the detected DCI format NDI field. The base station apparatus 3 may set the updated NDI value or the non-updated NDI value in the NDI field of the DCI format and transmit it to the terminal apparatus 1. The terminal device 1 may update the value of the NDI stored by using the detected DCI format NDI field for the detected HARQ process corresponding to the value of the detected DCI format HARQ process identifier field. ..

The terminal device 1 may determine whether the received transport block is a new transmission or a retransmission based on the value of the NDI field of the DCI format (DL association). The terminal device 1 compares the previously received NDI value to the transport block of a HARQ process, and if the detected DCI format NDI field value is toggled, the received transport block It may be determined that the transmission is new. When the base station apparatus 3 transmits a transport block for new transmission in a certain HARQ process, the base station apparatus 3 toggles the value of the NDI stored for the HARQ process and transmits the toggled NDI to the terminal apparatus 1. May be good. When the base station apparatus 3 transmits a transport block for retransmission in a certain HARQ process, the base station apparatus 3 does not toggle the value of the NDI stored for the HARQ process, and even if the non-toggled NDI is transmitted to the terminal apparatus 1. Good. Terminal 1 receives the detected DCI format NDI field value if it is not toggled (if it is the same) compared to the previously received NDI value for the transport block of a HARQ process. It may be determined that the transport block is retransmitted. Here, toggle means switching to a different value.

The terminal device 1 outputs HARQ-ACK information in the slot indicated by the value of the HARQ instruction field included in the DCI format 1_0 corresponding to PDSCH reception or the DCI format 1-11 in the HARQ-ACK codebook. ) May be reported to the base station apparatus 3.

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

dl-DataToUL-ACK shows a list of HARQ-ACK timings for PDSCH. Timing is the number of slots between the slot where the PDSCH was received (or the slot containing the last OFDM symbol to which the PDSCH is mapped) and the slot where HARQ-ACK is transmitted for the received PDSCH. is there. For example, dl-DataToUL-ACK may be a list of one, two, or three, four, five, six, seven, or eight timings. When dl-DataToUL-ACK is a list of timings, the HARQ indicator field is 0 bits. If dl-DataToUL-ACK is a list of two timings, the HARQ indicator field is 1 bit. For a list of timings with 3 or 4 dl-DataToUL-ACKs, the HARQ indicator field is 2 bits. If the dl-DataToUL-ACK is a list of 5, 6, or 7, or 8 timings, the HARQ indicator field is 3 bits. When dl-DataToUL-ACK is _{a list of timings of n K1} , the HARQ indicator field may be ceil (log2 (n _K1 )). Here, ceil (X _A ) is a function that outputs an integer obtained by rounding up the decimal point of the numerical value X _A. For example, ceil (2.3) may be 3. Further, the dl-DataToUL-ACK is composed of a list of timings having a value in the range of 0 to 31. For example, dl-DataToUL-ACK consists of a list of timings with any value in the range 0-63.

The size of dl-DataToUL-ACK is defined as the number of elements that dl-DataToUL-ACK contains. The size of dl-DataToUL-ACK may be referred to as _{L para.} The index of dl-DataToUL-ACK may indicate the order (number) of the elements of dl-DataToUL-ACK. For example, if the size of dl-DataToUL-ACK is 8 (L _para = 8), the index of dl-DataToUL-ACK is any of 1, 2, 3, 4, 5, 6, 7, or 8. It may be a value. The index of dl-DataToUL-ACK may be given, indicated, or indicated by the value indicated by the HARQ indicator 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 8 elements, the size of the HARQ-ACK codebook may be 8. For example, if the dl-DataToUL-ACK consists of two elements, the size of the HARQ-ACK codebook may be 2. Each HARQ-ACK information constituting the HARQ-ACK codebook may be HARQ-ACK information for PDSCH reception at each slot timing of dl-DataToUL-ACK. This type of HARQ-ACK codebook is also referred to as a Semi-static HARQ-ACK codebook.

An example of setting the HARQ instruction field will be described. For example, the dl-DataToUL-ACK consists of a list of eight timings 0, 7, 15, 23, 31, 39, 47, 55, and the HARQ indicator field consists of 3 bits. The HARQ instruction field "000" may correspond to the first 0 in the list of dl-DataToUL-ACK as the corresponding timing. That is, the HARQ instruction field “000” may correspond to the value 0 indicated by the index 1 of dl-DataToUL-ACK. The HARQ instruction field "001" may correspond to the second 7 in the list of dl-DataToUL-ACK as the corresponding timing. The HARQ instruction field "010" may correspond to the third 15 in the list of dl-DataToUL-ACK as the corresponding timing. The HARQ instruction field "011" may correspond to the fourth 23 in the list of dl-DataToUL-ACK as the corresponding timing. The HARQ instruction field "100" may correspond to the fifth 31 of the list of dl-DataToUL-ACK as the corresponding timing. The HARQ instruction field "101" may correspond to the sixth 39 in the list of dl-DataToUL-ACK as the corresponding timing. The HARQ instruction field "110" may correspond to the seventh 47 in the list of dl-DataToUL-ACK as the corresponding timing. The HARQ instruction field "111" may correspond to the eighth 55 in the list of dl-DataToUL-ACK as the corresponding timing. When the received HARQ instruction field indicates "000", the terminal device 1 may transmit the corresponding HARQ-ACK in the 0th slot from the received PDSCH slot. When the received HARQ instruction field indicates "001", the terminal device 1 may transmit the corresponding HARQ-ACK in the seventh slot from the received PDSCH slot. When the received HARQ instruction field indicates "010", the terminal device 1 may transmit the corresponding HARQ-ACK in the 15th slot from the received PDSCH slot. When the received HARQ instruction field indicates "011", the terminal device 1 may transmit the corresponding HARQ-ACK in the 23rd slot from the slot of the received PDSCH. When the received HARQ instruction field indicates "100", the terminal device 1 may transmit the corresponding HARQ-ACK in the 31st slot from the slot of the received PDSCH. When the received HARQ instruction field indicates "101", the terminal device 1 may transmit the corresponding HARQ-ACK in the 39th slot from the slot of the received PDSCH. When the received HARQ instruction field indicates "110", the terminal device 1 may transmit the corresponding HARQ-ACK in the 47th slot from the slot of the received PDSCH. When the received HARQ instruction field indicates "111", the terminal device 1 may transmit the corresponding HARQ-ACK in the 55th slot from the slot of the received PDSCH.

When the upper layer parameter pdsch-AggressionFactor is given to the terminal device 1, the N _PDSCH ^repeat may be the value of the pdsch-AggressionFactor. When the upper layer parameter pdsch-AggressionFactor is not given to the terminal device 1, the 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 and / or PUSCH transmission in slot n + k. Here, k may be the number of slots indicated by the HARQ indicator field included in the DCI format corresponding to the PDSCH reception. Further, if the HARQ instruction 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 the PDCCH containing DCI format 1_1 and is configured not to monitor the PDCCH containing DCI format 1-11, the HARQ-ACK timing value K1 is (1, 2, 3, It may be a part or all of 4, 5, 6, 7, 8). When the terminal device 1 is configured to monitor PDCCH including DCI format 1-11, the HARQ-ACK timing value K1 may be given by the upper layer parameter dl-DataToUL-ACK.

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

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

The terminal device 1 receives a slot for receiving PDCCH, a slot for transmitting HARQ-ACK information based on the value of the HARQ instruction field included in the received DCI format, and a plurality of candidate PDSCHs corresponding to the HARQ-ACK information. You may determine the set of slots. For example, when dl-DataToUL-ACK is (1, 2, 3, 4, 5, 6, 7, 8), the terminal device 1 receives the PDSCH in the slot m, and the DCI included in the PDCCH scheduling the PDSCH. It is assumed that the HARQ instruction field included in the format indicates 4. The terminal device 1 may determine that the HARQ-ACK information is transmitted in the slot (m + 4). In the terminal device 1, other HARQ-ACK information transmitted in the slot (m + 4) is the HARQ-ACK information for PDSCH reception in the slot (m + (1-4)) and the HARQ-ACK information in the slot (m + (2-4)). HARQ-ACK information for PDSCH reception, HARQ-ACK information for PDSCH reception in slot (m + (3-4)), HARQ-ACK information for PDSCH reception in slot (m + (5-4)), and slot (m +) HARQ-ACK information for PDSCH reception in (6-4)), HARQ-ACK information for PDSCH reception in slot (m + (7-4)), and HARQ- for PDSCH reception in slot (m + (8-4)). It may be determined that it is ACK information.

The dl-DataToUL-ACK may be configured not only as a value indicating the number of slots as the timing of HARQ-ACK, but also as a value (information) indicating that HARQ-ACK is held. When the terminal device 1 receives a HARQ instruction field indicating a value indicating that the PDCCH holds the HARQ-ACK, the terminal device 1 holds the HARQ-ACK (HARQ-ACK information) for the PDSCH scheduled by the PDCCH, and holds the HARQ-ACK. You may wait for the transmission of ACK (HARQ-ACK information).

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

The HARQ-ACK codebook corresponding to a PDSCH group is one or more corresponding to any one or more transport blocks contained in any one or more PDSCHs contained in the PDSCH group. It may be given based on the HARQ-ACK bit of. The HARQ-ACK codebook may be given at least based on a set of monitoring occasions for PDCCH, some or all of the values in the counter DAI field. The HARQ-ACK codebook may be given further based on the value of the UL DAI field. The HARQ-ACK codebook may be given further based on the value of the DAI field. The HARQ-ACK codebook may be given further based on the value of the total DAI field.

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

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

When the DCI format detected in the monitoring opportunity of any search region set corresponding to the monitoring opportunity of a PDCCH triggers transmission of HARQ-ACK information in slot n, the terminal device 1 monitors the PDCCH. The opportunity may be determined as a PDCCH monitoring opportunity for slot n. Further, when the DCI format detected in the monitoring opportunity of the search area set corresponding to the monitoring opportunity of a certain PDCCH does not trigger the transmission of HARQ-ACK information in the slot n, the terminal device 1 has the monitoring opportunity of the PDCCH. Does not have to be determined as a PDCCH monitoring opportunity for slot n. Further, when the DCI format is not detected in the monitoring opportunity of the search area set corresponding to the monitoring opportunity of a certain PDCCH, the terminal device 1 does not have to determine the monitoring opportunity of the PDCCH as the PDCCH monitoring opportunity for the slot n. ..

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

The counter DAI (Counter DAI) is the cumulative number (or cumulative) of PDCCH detected up to the monitoring opportunity of the PDCCH in the serving cell for the monitoring opportunity of the PDCCH in the serving cell in the monitoring opportunity of M PDCCH. It may be at least a value related to the number). The counter DAI may also be referred to as C-DAI. The C-DAI corresponding to the PDSCH may be indicated by a field contained in the DCI format used for scheduling the PDSCH. The total DAI may indicate the cumulative number (or at least a value related to the cumulative number) of PDCCH detected by the monitoring opportunity m of PDCCH in the monitoring opportunity of M PDCCH. The total DAI may indicate the cumulative number (or at least a value related to the cumulative number) of PDSCHs detected by the monitoring opportunity m of PDCCH in the monitoring opportunity of M PDCCHs. The total DAI may be referred to as a T-DAI (Total Downlink Assignment Index).

Semi-static HARQ-ACK codebook (type 1 HARQ-ACK codebook) or Dynamic HARQ-ACK codebook (type 2 HARQ-ACK codebook) is directed (triggered, requested) to be transmitted based on DL acknowledgment. It may be an ACK codebook. The DCI format containing the HARQ indicator field may be a DL association (Downlink association). D
The Lasignment may be a DCI format used for scheduling PDSCH. The DL association may be a DCI format used for PDSCH allocation. The Semi-static HARQ-ACK codebook may be configured based on the dl-StatoUL-ACK and the HARQ indicator field. The size of the Semi-static HARQ-ACK codebook may be given based on the size contained in the dl-StatoUL-ACK. The timing of the slots included in the Semi-static HARQ-ACK codebook, or Dynamic HARQ-ACK codebook, may be given based on the value of the HARQ indicator field and the slot in which the DCI containing the HARQ indicator field was received.

A type 3 HARQ-ACK codebook can be said to be a HARQ-ACK codebook whose transmission is triggered by a DCI format (DL acknowledgment) with PDSCH scheduling information. The type 3 HARQ-ACK codebook is transmitted by a DCI format different from the DCI format with PDSCH scheduling information (DCI format only for instructing the transmission of HARQ-ACK codebook, DCI format with PUSCH scheduling information). It can be said that it is a triggered HARQ-ACK codebook.

The type 3 HARQ-ACK codebook may be instructed (triggered, requested) to be transmitted by a DCI format that is not a DL assert. For example, DL
A DCI format that is not an acknowledgment is a type 3 HARQ-ACK.
It may be a DCI format used only to trigger the transmission of the codebook. For example, the DCI format that is not DL assert may be a DCI format (UL grant) that schedules PUSCH.

The type 3 HARQ-ACK codebook may be instructed (triggered, requested) to be transmitted by the DCI format which is a DL assert. The DCI format may include a dedicated field for instructing (triggering, requesting) the transmission of the HARQ-ACK codebook.

The type 3 HARQ-ACK codebook may be instructed (triggered, requested) to be transmitted by the DCI format that schedules the PUSCH. The DCI format may include a dedicated field for instructing (triggering, requesting) the transmission of the HARQ-ACK codebook.

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

A type 4 HARQ-ACK codebook can be said to be a HARQ-ACK codebook in which transmission is triggered by a DCI format that does not involve PDSCH scheduling information and does not perform PUSCH scheduling. The DCI format that triggers the type 4 HARQ-ACK codebook may include one or more HARQ process IDs to be reported and an NDI. The DCI format is referred to as a trigger-only DCI format.

Base station equipment 3 uses HARQ trigger bits to attach type 3 HARQ-ACK to terminal equipment 1.
When instructing (requesting) the transmission (report) of the codebook, the terminal device 1 is the terminal device 1.
The HARQ-ACK information contained in some or all of the HARQ processes configured in the terminal device 1 and the value of NDI included in some or all of the HARQ processes configured in the terminal device 1 are obtained by using the type 3 HARQ-ACK codebook. It may be transmitted (reported) to the base station device 3. When the base station apparatus 3 instructs (requests) the transmission (report) of the type 3 HARQ-ACK codebook to the terminal apparatus 1 using the HARQ trigger bit, the terminal apparatus 1 is included in the HARQ process for one HARQ process. The one HARQ-ACK information to be generated and the value of one NDI included in the HARQ process may be transmitted (reported) to the base station apparatus 3.

When the base station apparatus 3 instructs (requests) the transmission (report) of the type 4 HARQ-ACK codebook to the terminal apparatus 1 using the trigger-dedicated DCI format, the terminal apparatus 1 has the HARQ process ID included in the trigger-dedicated DCI format. , NDI exists in the HARQ process ID stored in the terminal device 1 and the NDI, the HARQ-ACK information stored in the terminal device 1 is transmitted, and the HARQ included in the trigger dedicated DCI format is transmitted. If the process ID and NDI do not exist in the HARQ process ID and NDI stored in the terminal device 1, NACK may be transmitted.

A type 3 HARQ-ACK codebook and / or a type 4 HARQ-ACK codebook may include HARQ-ACK information for more than one or all HARQ processes. For example, the HARQ process may mean the HARQ process used for PDSCH. For example, all HARQ processes may mean all of the HARQ processes that can be used in at least one Serving cell. For example, the number of HARQ processes that can be used in one Serving cell may be 16. For example, the number of HARQ processes that can be used in five Serving cells may be 80. For example, the plurality of HARQ processes may mean a plurality of HARQ processes configured by RRC signing. For example, the plurality of HARQ processes may mean a plurality of HARQ processes instructed by the Downlink control information. For example, a plurality of HARQ processes may mean a plurality of HARQ processes that are explicitly or implicitly indicated. For example, the number of a plurality of HARQ processes may be eight. For example, the number of multiple HARQ processes may be 10.

The type 3 HARQ-ACK codebook can be said to be a HARQ-ACK codebook in which the HARQ process of the PDSCH corresponding to the HARQ-ACK included in the HARQ-ACK codebook is defined. The slot in which the PDSCH corresponding to the HARQ-ACK included in the type 3 HARQ-ACK codebook is received is not limited in advance, and may be set by scheduling the base station apparatus 3.

The type 3 HARQ-ACK codebook may include a value of NDI associated with the HARQ process corresponding to the HARQ-ACK reported in the type 3 HARQ-ACK codebook. The type 3 HARQ-ACK codebook may include a value of NDI per HARQ process that includes the HARQ-ACK information reported in the type 3 HARQ-ACK codebook. The terminal device 1 may determine (set) the HARQ-ACK information to be included in the type 3 HARQ-ACK codebook based on at least some or all of the stored HARQ processes and NDI values. The HARQ-ACK may be HARQ-ACK information corresponding to a transport block for a HARQ process. The value of the NDI may indicate the NDI for the HARQ process. Further, the value of the NDI is the N corresponding to the HARQ-ACK information.
DI may be indicated.

When the terminal device 1 receives the PDCCH including the DCI format including the HARQ trigger bit and the terminal device 1 does not have the SPS PDSCH configured, the terminal device 1 is included in the HARQ process configured in the terminal device 1. The HARQ-ACK information to be used and the value of NDI included in the HARQ process may be transmitted using a PUCCH that transmits the HARQ-ACK information corresponding to the PDSCH scheduled by the PDCCH.

The fact that the SPS PDSCH is configured in the terminal device 1 may mean that the SPS PDSCH is activated in the terminal device 1. Further, the fact that the SPS PDSCH is configured in the terminal device 1 may mean that the configuration of the SPS PDSCH is provided in the terminal device 1 (provided).

The fact that the SPS PDSCH is not configured in the terminal device 1 may mean that the SPS PDSCH is deactivated in the terminal device 1. Further, the fact that the SPS PDSCH is not configured in the terminal device 1 may mean that the configuration of the SPS PDSCH is not provided in the terminal device 1 (not provided).

The fact that the terminal device 1 receives the SPS PDSCH may mean that the terminal device 1 is configured with the SPS PDSCH.

FIG. 7 is a diagram showing an example of a type 3 HARQ-ACK codebook when the SPS PDSCH is not configured in the present embodiment. The dl-DataToUL-ACK indicated by 700 is 1, 2, and 3. It is assumed that the PDCCH 701 schedules the PDSCH 704, the PDCCH 702 schedules the PDSCH 705, and the PDCCH 703 schedules the PDSCH 706. The DCI format included in the PDCCH 701 has a K1 of 2, a HARQ process ID of 1, an NDI of 1, and a HARQ trigger bit of 0. Here, the HARQ trigger bit is the HARQ-ACK information included in a part or all of the HARQ process configured in the terminal device 1 by the base station apparatus 3, and the value of NDI included in the part or all of the HARQ process. It may be a parameter that instructs (requests) the terminal device 1 to report (transmit). The DCI format included in the PDCCH 702 has a K1 of 1, a HARQ process ID of 2, an NDI of 1, and a HARQ trigger bit of 0. The DCI format included in the PDCCH 703 has a K1 of 1, a HARQ process ID of 3, an NDI of 0, and a HARQ trigger bit of 1.

The HARQ-ACK information corresponding to PDSCH704 is NACK, and the HARQ-ACK information corresponding to PDSCH705 is ACK. The terminal device 1 has HARQ-ACK information corresponding to PDSCH704 and HARQ-ACK information corresponding to PDSCH705 based on the K1 value of DCI format contained in PDCCH701 and the K1 value of DCI format contained in PDCCH702. Is transmitted by PUCCH707.

The HARQ-ACK information corresponding to PDSCH706 is NACK. The terminal device 1 transmits HARQ-ACK information corresponding to PDCCH706 by PUCCH708 based on the value of K1 of DCI format included in PDCCH703. Here, since the HARQ trigger bit of the DCI format included in the PDCCH 703 is 1, the terminal device 1 includes HARQ-ACK information included in a part or all of the HARQ processes configured in the terminal device 1 and a part thereof. Alternatively, the NDI value included in the entire HARQ process is transmitted by PUCCH708. That is, since the HARQ trigger bit of the DCI format included in the PDCCH 703 is 1, the terminal device 1 has the HARQ-ACK included in the HARQ process ID1, the HARQ process ID2, and the HARQ process ID3 configured in the terminal device 1. The information, the HARQ process ID1 configured in the terminal device 1, the HARQ process ID2, and the NDI value included in the HARQ process ID3 are transmitted by PUCCH708.

Even if the HARQ-ACK information and NDI value transmitted by PUCCH708 are placed at the beginning of the bit string (MSB: Most Significant Bit) from the HARQ-ACK information and NDI value included in the HARQ process with a small HARQ process ID. Good. Even if the HARQ-ACK information and NDI value transmitted by PUCCH708 are placed at the beginning of the bit string (MSB: Most Significant Bit) from the HARQ-ACK information and NDI value included in the HARQ process having a large HARQ process ID. Good. Even if the HARQ-ACK information and NDI value transmitted by PUCCH708 are placed at the beginning of the bit string (MSB: Most Significant Bit) from the HARQ-ACK information and NDI value included in the HARQ process assigned earlier. Good.

The SPS PDSCH is configured in the terminal device 1, the terminal device 1 receives the SPS PDSCH, and the HARQ trigger bit included in the DCI format is included in a part or all of the HARQ processes configured in the terminal device 1. When the transmission of HARQ-ACK information is requested (instructed), the terminal device 1 has a problem that the NDI corresponding to SPS PDSCH cannot be reported in the transmission of the HARQ-ACK information because the value of NDI for SPS PDSCH does not exist. appear.

The SPS PDSCH is configured in the terminal device 1, the terminal device 1 receives the SPS PDSCH, and the HARQ trigger bit included in the DCI format is included in a part or all of the HARQ processes configured in the terminal device 1. When the transmission of HARQ-ACK information is requested (instructed), the terminal device 1 may map the HARQ-ACK information included in the HARQ process corresponding to the SPS PDSCH with a predetermined value. Here, the predetermined value may be 0 or 1.

A part in which the SPS PDSCH is configured in the terminal device 1, the terminal device 1 receives the PDSCH scheduled by the SPS PDSCH and the DL grant, and the HARQ trigger bit included in the DCI format is configured in the terminal device 1. Alternatively, when requested (instructed) to transmit HARQ-ACK information contained in all HARQ processes, terminal device 1 is included in HARQ-ACK included in one or more PDSCHs scheduled by DL grant. Even if the information and the NDI value included in the HARQ process are first mapped to the bit string to be the input of the PUCCH resource, and then the HARQ-ACK information included in the HARQ process corresponding to the SPS PDSCH and the predetermined value are mapped. Good.

FIG. 8 is a diagram showing an example of reporting HARQ-ACK information corresponding to the PDSCH and the SPS PDSCH scheduled by the DL grant when the SPS PDSCH is configured in the terminal device 1 in the present embodiment. The PDCCH 801 schedules the PDSCH 804, the PDCCH 802 schedules the PDSCH 805, and the PDCCH 803 schedules the PDSCH 806. The terminal device 1 may transmit the HARQ-ACK information corresponding to PDSCH804 and the HARQ-ACK information corresponding to PDSCH805 to PUCCH807 based on at least the value of K1. Since the HARQ trigger bit included in the DCI format included in the PDCCH 801 and the PDCCH 802 is 0, the terminal device 1 does not have to transmit (report) the value of NDI.

Since K1 of SPS PDSCH809 is 2, the terminal device 1 may transmit HARQ-ACK information corresponding to SPS PDSCH809 using PUCCH808. The terminal device 1 transmits the HARQ-ACK information corresponding to the PDSCH806 scheduled by the PDCCH 803 using the PUCCH 808 after one slot because the value of K1 included in the DCI format included in the PDCCH 803 is 1. You may.

The HARQ trigger bit included in the DCI format included in the PDCCH 803 transmits the HARQ-ACK information contained in a part or all of the HARQ processes configured in the terminal device 1 and the value of NDI for the HARQ-ACK information. The terminal device 1 uses PUCCH808 to obtain HARQ-ACK information included in a part or all of the HARQ processes configured in the terminal device 1 and the value of NDI for the HARQ-ACK information. You may send it. Here, since the value of NDI corresponding to SPS PDSCH809 is not set, the terminal device 1 may set a predetermined value in the field of the value of NDI corresponding to SPS PDSCH809 in PUCCH808 and transmit PUCCH808. .. The predetermined value may be 0 or 1. In PUCCH 808 of FIG. 8, field 811 may be a field for HARQ-ACK information corresponding to one or more PDSCHs scheduled by DL grant and NDI for the HARQ-ACK information. The field 812 may be a field for HARQ-ACK information corresponding to the SPS PDSCH and NDI for the HARQ-ACK information.

A part in which the SPS PDSCH is configured in the terminal device 1, the terminal device 1 receives the PDSCH scheduled by the SPS PDSCH and the DL grant, and the HARQ trigger bit included in the DCI format is configured in the terminal device 1. Alternatively, when the transmission of HARQ-ACK information contained in the entire HARQ process is requested (instructed), the triggered HARQ-ACK information and the bit string mapped to the PUCCH that transmits the NDI for the HARQ-ACK information are {. HARQ-ACK information, NDI} may be arranged in this order.

The SPS PDSCH is configured in the terminal device 1, the terminal device 1 receives the SPS PDSCH, and the HARQ trigger bit included in the DCI format is included in a part or all of the HARQ processes configured in the terminal device 1. When the transmission of HARQ-ACK information is requested (instructed), the terminal device 1 may map only the HARQ-ACK information included in the HARQ process corresponding to the SPS PDSCH.

A part in which the SPS PDSCH is configured in the terminal device 1, the terminal device 1 receives the PDSCH scheduled by the SPS PDSCH and the DL grant, and the HARQ trigger bit included in the DCI format is configured in the terminal device 1. Alternatively, when the transmission of HARQ-ACK information included in all HARQ processes is requested (instructed) and there are a plurality of HARQ processes having the same HARQ process ID, the terminal device 1 has the HARQ process ID of the same HARQ process ID. The HARQ-ACK information included in the (latest) HARQ process configured last from the processes and the NDI for the HARQ-ACK information may be reported to the base station apparatus 3.

The SPS PDSCH is configured in the terminal device 1, the terminal device 1 receives the SPS PDSCH, and the HARQ trigger bit included in the DCI format is included in a part or all of the HARQ processes configured in the terminal device 1. When the transmission of HARQ-ACK information is requested (instructed), the terminal device 1 does not have to transmit (report) the HARQ-ACK information included in the HARQ process corresponding to the SPS PDSCH.

The terminal device 1 receives the PDCCH containing the DCI format indicating the deactivation of the SPS PDSCH, and the HARQ trigger bit included in the DCI format is included in a part or all of the HARQ processes configured in the terminal device 1. When the transmission of the HARQ-ACK information is requested (instructed), the terminal device 1 may map the HARQ-ACK information corresponding to the deactivation of the SPS PDSCH with a predetermined value. Here, the predetermined value may be 0 or 1.

The terminal device 1 receives the PDCCH containing the DCI format indicating the deactivation of the SPS PDSCH, and the HARQ trigger bit included in the DCI format is included in a part or all of the HARQ processes configured in the terminal device 1. When the transmission of the HARQ-ACK information is requested (instructed), the terminal device 1 may transmit only the HARQ-ACK information corresponding to the deactivation of the SPS PDSCH.

The terminal device 1 receives the PDCCH containing the DCI format indicating the deactivation of the SPS PDSCH, and the HARQ trigger bit included in the DCI format is included in a part or all of the HARQ processes configured in the terminal device 1. When the transmission of the HARQ-ACK information is requested (instructed), the terminal device 1 does not have to transmit the HARQ-ACK information corresponding to the deactivation of the SPS PDSCH.

FIG. 9 is a diagram showing an example of reporting HARQ-ACK information for the deactivation of SPS PDSCH and the HARQ trigger bit in the present embodiment. PDCCH901 schedules PDSCH902. PDCCH906 schedules PDSCH907. The PDCCH 908 may be a PDCCH that deactivates the SPS PDSCH. The HARQ-ACK information corresponding to PDSCH902 is ACK, and the terminal device 1 transmits the HARQ-ACK information using PUCCH903. The HARQ-ACK information corresponding to PDSCH907 is ACK, and the terminal device 1 transmits the HARQ-ACK information using PUCCH909. The HARQ-ACK information corresponding to the SPS PDSCH904 is NACK, and the terminal device 1 transmits the HARQ-ACK information using the PUCCH905. The HARQ-ACK information corresponding to the PDCCH that deactivates the SPS PDSCH is ACK, and the terminal device 1 transmits the HARQ-ACK information using the PUCCH 909.

The base station device 3 uses the HARQ trigger bit field of the DCI format included in the PDCCH 906 to obtain the HARQ-ACK information contained in a part or all of the HARQ processes configured in the terminal device 1 and the NDI for the HARQ-ACK information. When the terminal device 1 instructs (requests) to transmit using the PUCCH 909, the terminal device 1 indicates the HARQ-ACK information corresponding to PDSCH902, the NDI for the HARQ-ACK information, and the HARQ- corresponding to PDSCH907. The ACK information and the NDI for the HARQ-ACK information are mapped to the field 910 included in the PUCCH909, and the HARQ-ACK information corresponding to the SPS PDSCH904 and the first predetermined value are mapped to the field 911 included in the PUCCH909. The HARQ-ACK information corresponding to the PDCCH908 that deactivates the SPS PDSCH and the second predetermined value may be mapped to the field 912 included in the PUCCH909 and the PUCCH909 may be transmitted. Here, the first predetermined value may be 0 or 1. Further, the second predetermined value may be 0, 1, or may be a value different from the first predetermined value. For example, when the first predetermined value is 0, the second predetermined value may be 1. For example, when the first predetermined value is 1, the second predetermined value may be 0. The first predetermined value is referred to as a value of NDI with respect to SPS PDSCH. The second predetermined value is referred to as the value of NDI for the inactivation of SPS PDSCH.

The value of NDI with respect to SPS PDSCH may be a predetermined value. The value of NDI for deactivation of SPS PDSCH may differ from the value of NDI for said SPS PDSCH. For example, if the value of NDI for SPS PDSCH is 0, the value of NDI for deactivation of SPS PDSCH may be 1. For example, if the value of NDI for SPS PDSCH is 1, the value of NDI for deactivation of SPS PDSCH may be 0.

The terminal device 1 does not have to transmit the value of NDI for the SPS PDSCH to the base station device 3. For example, in FIG. 9, the terminal device 1 may transmit only the HARQ-ACK information (NACK) without transmitting the 0 included in the field 911. The terminal device 1 does not have to transmit the value of NDI for the deactivation of the SPS PDSCH to the base station device 3. For example, in FIG. 9, the terminal device 1 may not transmit the 1 included in the field 912, but may transmit only the HARQ-ACK information (ACK).

The DCI format that triggers the transmission of a type 4 HARQ-ACK codebook may include an NDI field. The DCI format that triggers the transmission of a type 4 HARQ-ACK codebook includes an NDI field per HARQ process that includes a HARQ-ACK in a type 4 HARQ-ACK codebook. The base station apparatus 3 sets the latest NDI value stored for each HARQ process in the NDI field of the above DCI format. The terminal device 1 determines (sets) the HARQ-ACK to be included in the type 4 HARQ-ACK codebook based on the NDI field included in the DCI format that triggers the transmission of the type 4 HARQ-ACK codebook. The HARQ-ACK may be a HARQ-ACK corresponding to a transport block for a HARQ process. The NDI field may indicate the NDI for the HARQ process. Specifically, if the terminal device 1 has the same NDI value stored for each HARQ process and the NDI value indicated by the DCI format that triggers the transmission of the type 4 HARQ-ACK codebook, the corresponding HARQ process The HARQ-ACK information stored (stored) for is included in the type 4 HARQ-ACK codebook, and the NDI value stored for each HARQ process and the transmission of the type 4 HARQ-ACK codebook are triggered. If the value of NDI indicated by the DCI format is different, include NACK in the type 4 HARQ-ACK codebook for the corresponding HARQ process.

An example will be described. For example, the terminal device 1 stores "1" as the value of NDI for HARQ process # 1 and stores "ACK" as HARQ-ACK for HARQ process # 1. Terminal device 1 receives a DCI format that triggers the transmission of a type 4 HARQ-ACK codebook, including '1' as the value of NDI for HARQ process # 1. Terminal device 1 states that the value of NDI stored for HARQ process # 1 is the same as the value of NDI for HARQ process # 1 indicated by the DCI format that triggers the transmission of type 4 HARQ-ACK codebook. Include'ACK', which is determined and stored as HARQ-ACK for HARQ process # 1, in the type 4 HARQ-ACK codebook.

An example will be described. For example, the terminal device 1 stores '1' as the value of NDI for HARQ process # 1 and stores'ACK' as HARQ-ACK for HARQ process # 1. Terminal device 1 receives a DCI format that triggers the transmission of a type 4 HARQ-ACK codebook, including '0' as the value of NDI for HARQ process # 1. The terminal device 1 determines that the NDI value stored for the HARQ process # 1 is different from the NDI value for the HARQ process # 1 indicated by the DCI format that triggers the transmission of the type 4 HARQ-ACK codebook. , Include'NACK'in the type 4 HARQ-ACK codebook as HARQ-ACK for HARQ process # 1. Since the terminal device 1 has a different NDI value for the HARQ process # 1 and the NDI value for the HARQ process # 1 indicated by the DCI format that triggers the transmission of the type 4 HARQ-ACK codebook. Recognize that the detection of the DCI format including the scheduling information for HARQ process # 1 was missed.

When the terminal device 1 receives the DCI format including the PDSCH scheduling information, the terminal device 1 updates the NDI value stored for the HARQ process based on the NDI field included in the DCI format including the PDSCH scheduling information. When a DCI format that does not include PDSCH scheduling information and triggers a report of HARQ-ACK codebook (eg, type 4 HARQ-ACK codebook) is received, it does not include PDSCH scheduling information and HARQ-ACK.
The HARQ-ACK reported to the HARQ process is determined based on the NDI field included in the DCI format that triggers the report of the codebook, and the value of the NDI stored for the HARQ process is retained. When the terminal device 1 includes the NDI field for each HARQ process and receives the DCI format instructing the transmission of the type 4 HARQ-ACK codebook, the terminal device 1 determines the HARQ-ACK reported to the HARQ process based on the NDI field. Do not use (do not store, do not store) as the NDI value of the previous transmission for the HARQ process.

An example will be described. For example, the terminal device 1 stores "1" as the value of NDI for HARQ process # 1 and stores "ACK" as HARQ-ACK for HARQ process # 1. The terminal device 1 receives a DCI format that triggers the transmission of a type 4 HARQ-ACK codebook, including '0' as the value of NDI for HARQ process # 1. The terminal device 1 determines that the NDI value stored for the HARQ process # 1 is different from the NDI value for the HARQ process # 1 indicated by the DCI format that triggers the transmission of the type 4 HARQ-ACK codebook. , Judged as'NACK'as HARQ-ACK for HARQ process # 1, and did not use '0' as the value of NDI for HARQ process # 1 (not stored, not stored), and already stored '1 Continue to use'(keep remembering, keep storing).

An example will be described. For example, the terminal device 1 stores "1" as the value of NDI for HARQ process # 1 and stores "ACK" as HARQ-ACK for HARQ process # 1. For example, the terminal device 1 stores "0" as the value of NDI for HARQ process # 2, and stores "ACK" as HARQ-ACK for HARQ process # 2. Terminal device 1 receives a DCI format that triggers the transmission of a type 4 HARQ-ACK codebook, including '0' as the value of NDI for HARQ process # 1 and '0' as the value of NDI for HARQ process # 2. .. The terminal device 1 determines that the NDI value stored for the HARQ process # 1 and the NDI value for the HARQ process # 1 indicated by the DCI format that triggers the transmission of the type 4 HARQ-ACK codebook are different. , Judge as'NACK'as HARQ-ACK for HARQ process # 1. The terminal device 1 states that the value of NDI stored for HARQ process # 2 is the same as the value of NDI for HARQ process # 2 indicated by the DCI format that triggers the transmission of type 4 HARQ-ACK codebook. Include'ACK', which is determined and stored as HARQ-ACK for HARQ process # 2, in the type 4 HARQ-ACK codebook. The terminal device 1 does not use the value '0' of the NDI field notified in the DCI format as the value of NDI for HARQ process # 1 (does not store or stores), and stores the already stored '1'. Continue to use (keep remembering, keep storing). The terminal device 1 continues to use the already stored '0' as the value of the NDI for the HARQ process # 2, which is the same as the value of the NDI field notified in the DCI format (keep storing, keep storing).

The HARQ process is tied to the transport block. The terminal device 1 does not apply (do not use) the NDI field for a HARQ process contained in the DCI format indicating the transmission of the type 4 HARQ-ACK codebook to the NDI value of the previous transmission of the transport block of the HARQ process. ).

When the terminal device 1 receives the SPS PDSCH and receives the DCI format that triggers the transmission of the type 4 HARQ-ACK codebook containing the HARQ-ACK information corresponding to the SPS PDSCH (HARQ process of the SPS PDSCH), the terminal device 1 receives the SPS PDSCH. , You may expect that the value of the NDI field corresponding to the SPS PDSCH included in the DCI format is a predetermined value. Here, the predetermined value may be 0 or 1.

The terminal device 1 receives the PDCCH instructing the deactivation of the SPS PDSCH and performs a DCI form that triggers the transmission of the type 4 HARQ-ACK codebook containing the HARQ-ACK information corresponding to the deactivation of the SPS PDSCH. Upon receipt, the terminal device 1 may expect the value of the NDI field corresponding to the deactivation of the SPS PDSCH included in the DCI format to be a predetermined value. Here, the predetermined value may be 0 or 1. Further, the predetermined value may be a value different from the NDI field value for the HARQ-ACK information corresponding to the SPS PDSCH. For example, when the value of the NDI field for the HARQ-ACK information corresponding to the SPS PDSCH is 0, the predetermined value may be 1. For example, when the value of the NDI field for the HARQ-ACK information corresponding to the SPS PDSCH is 1, the predetermined value may be 0.

If the HARQ process ID contained in the DCI form that triggers the reporting of type 4 HARQ-ACK codebook is the HARQ process ID configured for the SPS PDSCH, the terminal device 1 is the value of the NDI field contained in the DCI form. When is X _NDI , the HARQ-ACK information corresponding to the HARQ process ID for the SPS PDSCH is included in the PUCCH, and when the value of the NDI field included in the DCI format is Y _NDI , the SPS PDSCH The PUCCH may contain the HARQ-ACK information corresponding to the deactivation. Here, X _NDI may be 0 or 1. Further, Y _NDI may be 0, 1 or a value different from _{X NDI.} For example, if X _NDI is 0, Y _NDI may be 1. For example, if X _NDI is 1, Y _NDI may be 0.

When the terminal device 1 receives a DCI format that triggers a report of a type 4 HARQ-ACK codebook containing HARQ-ACK information corresponding to the deactivation of the SPS PDSCH, the terminal device 1 receives a DCI format of the SPS PDSCH included in the DCI format. It may be expected that the HARQ process ID corresponding to the deactivation is the same as the HARQ process ID of the last received SPS PDSCH.

When the terminal device 1 receives a DCI form that triggers a report of a type 4 HARQ-ACK codebook containing HARQ-ACK information corresponding to the deactivation of the SPS PDSCH, the terminal device 1 receives the SPS PDSCH contained in the DCI form. It may be expected that the HARQ process ID corresponding to the deactivation is one HARQ process ID out of one or more HARQ process IDs configured for the SPS PDSCH.

When the base station apparatus 3 transmits a DCI form that triggers a report of a type 4 HARQ-ACK codebook containing HARQ-ACK information corresponding to the deactivation of the SPS PDSCH, the base station apparatus 3 is included in the DCI form. The HARQ process ID corresponding to the deactivation of the PDSCH may be set to the HARQ process ID of the SPS PDSCH last transmitted.

When the base station apparatus 3 transmits a DCI form that triggers a report of a type 4 HARQ-ACK codebook containing HARQ-ACK information corresponding to the deactivation of the SPS PDSCH, the base station apparatus 3 is included in the DCIform. The HARQ process ID corresponding to the deactivation of the SPS PDSCH may be set by selecting one HARQ process ID from one or more HARQ process IDs configured for the SPS PDSCH.

An example will be described. For example, the terminal device 1 stores '1' as the value of NDI for HARQ process # 1 corresponding to PDSCH scheduled by DL grant, stores'ACK' as HARQ-ACK for HARQ process # 1, and SPS. 'ACK' is stored as HARQ-ACK for HARQ process # 2 corresponding to PDSCH. Terminal device 1 contains a DCI format that triggers the transmission of a type 4 HARQ-ACK codebook, including '1' as the value of the NDI field for HARQ process # 1 and '0' as the value of the NDI field for HARQ process # 2. Receive. The terminal device 1 has the same value of the NDI stored for the HARQ process # 1 and the value of the NDI field for the HARQ process # 1 indicated by the DCI format that triggers the transmission of the type 4 HARQ-ACK codebook. By the DCI format that triggers the transmission of type 4 HARQ-ACK codebook to HARQ process # 2, including'ACK' stored as HARQ-ACK information for HARQ process # 1 in the type 4 HARQ-ACK codebook. Since the value of the indicated NDI field is '0', it is judged that the HARQ-ACK information corresponding to SPS PDSCH is reported, and'ACK' stored as HARQ-ACK for HARQ process # 2 corresponding to SPS PDSCH is stored. Included in type 4 HARQ-ACK codebook.

An example will be described. For example, the terminal device 1 is configured with HARQ process # 2 and HARQ process # 3 for SPS PDSCH. The terminal device 1 stores '1' as the value of NDI for HARQ process # 1 corresponding to PDSCH scheduled by DL grant, stores'ACK' as HARQ-ACK for HARQ process # 1, and stores it in SPS PDSCH. 'NACK' is stored as the HARQ-ACK for the corresponding HARQ process # 2, and'ACK' is stored as the HARQ-ACK for the HARQ process # 3 corresponding to the SPS PDSCH. In addition, the terminal device 1 receives the PDCCH that deactivates the SPS PDSCH, and successfully deactivates the SPS PDSCH, so that it stores ‘ACK’. Terminal device 1 contains '1' as the value of the NDI field for HARQ process # 1, '1' as the value of the NDI field for HARQ process # 2, and '0' as the value of the NDI field for HARQ process # 3. Receives a DCI format that triggers the transmission of a type 4 HARQ-ACK codebook, including. The terminal device 1 has the same value of the NDI stored for the HARQ process # 1 and the value of the NDI field for the HARQ process # 1 indicated by the DCI format that triggers the transmission of the type 4 HARQ-ACK codebook. By the DCI format that triggers the transmission of the type 4 HARQ-ACK codebook to the HARQ process # 2 by including'ACK' stored as the HARQ-ACK information for the HARQ process # 1 in the type 4 HARQ-ACK codebook. Since the value of the indicated NDI field is '1', it is judged that the report is the HARQ-ACK information corresponding to the deactivation of the SPS PDSCH, and it is stored as the HARQ-ACK information corresponding to the deactivation of the SPS PDSCH. The SPS PDSCH HARQ process because the value of the NDI field indicated by the DCI format that includes'ACK'in the type 4 HARQ-ACK codebook and triggers the transmission of the type 4 HARQ-ACK codebook to HARQ process # 3 is '0'. It is determined that the HARQ-ACK information corresponding to # 3 is reported, and'ACK' stored as HARQ-ACK corresponding to the HARQ process # 3 corresponding to SPS PDSCH is included in the type 4 HARQ-ACK codebook.

A type 3 HARQ-ACK codebook may include a HARQ-ACK information field and an NDI field. A type 4 HARQ-ACK codebook may include a HARQ-ACK information field. A type 3 HARQ-ACK codebook may include a HARQ-ACK information field and an NDI field for a HARQ process. A type 4 HARQ-ACK codebook may include a HARQ-ACK information field for a HARQ process. The HARQ-ACK information field is a type 3 HARQ-ACK codebook reported by the terminal device 1 to the base station device 3, and the HARQ-ACK information included in each HARQ process included in the type 3 HARQ-ACK codebook is mapped. It may be a field. The HARQ-ACK information field is a type 4 HARQ-ACK codebook reported by the terminal device 1 to the base station device 3, and HARQ-ACK information included in each HARQ process included in the type 4 HARQ-ACK codebook is mapped. It may be a field. The NDI field is a map of the value of NDI stored in the terminal device 1 for each HARQ process included in the type 3 HARQ-ACK codebook in the type 3 HARQ-ACK codebook reported by the terminal device 1 to the base station device 3. It may be a field to be used.

The DCI format that triggers the reporting (transmission) of a type 3 HARQ-ACK codebook may include a HARQ trigger field. The DCI format that triggers the reporting (transmission) of a type 4 HARQ-ACK codebook may include one or more HARQ process IDs to be reported and an NDI for that HARQ process ID.

Triggering a report (transmission) of HARQ-ACK information contained in one or more HARQ processes configured in terminal device 1 means triggering a report (transmission) of a type 3 HARQ-ACK codebook. May be good. Triggering the reporting (transmission) of HARQ-ACK information contained in one or more HARQ processes configured in terminal device 1 means triggering the reporting (transmission) of type 4 HARQ-ACK codebook. May be good.

The size of the type 3 HARQ-ACK codebook may be given at least based on the number of HARQ processes configured in terminal device 1 and the PDCCH that deactivates the SPS PDSCH. For example, if the number of HARQ processes configured in terminal device 1 is 16 and terminal device 1 does not receive a PDCCH that deactivates the SPS PDSCH, the size of the type 3 HARQ-ACK codebook will be in the HARQ process. It may be the sum (32 bits) of the number of HARQ-ACK information contained (16 bits) and the number of NDIs (16 bits) for the HARQ process. For example, if the number of HARQ processes configured in terminal device 1 is 16, and terminal device 1 receives a PDCCH that deactivates the SPS PDSCH, the size of the type 3 HARQ-ACK codebook is included in the HARQ process. The sum (33 bits) of the number of HARQ-ACK information (16 bits), the number of NDIs for the HARQ process (16 bits), and the HARQ-ACK information (1 bit) corresponding to the deactivation of SPS PDSCH. There may be. For example, if the number of HARQ processes configured in terminal device 1 is 16, and terminal device 1 receives a PDCCH that deactivates the SPS PDSCH, the size of the type 3 HARQ-ACK codebook is included in the HARQ process. The number of HARQ-ACK information (16 bits), the number of NDIs for the HARQ process (16 bits), the HARQ-ACK information corresponding to the deactivation of SPS PDSCH (1 bit), and a predetermined number corresponding to the NDI. It may be the sum (34 bits) of the value (1 bit). Here, the'predetermined value corresponding to NDI'does not function as NDI because there is no NDI value for SPS PDSCH, but a value for setting in the NDI field included in the type 4 HARQ-ACK codebook ( It may be a placeholder value).

The size of the type 4 HARQ-ACK codebook may be given at least based on the number of HARQ processes configured in terminal device 1 and the PDCCH that deactivates the SPS PDSCH. For example, if the number of HARQ processes configured in terminal device 1 is 16 and terminal device 1 does not receive a PDCCH that deactivates the SPS PDSCH, the size of the type 4 HARQ-ACK codebook will be in the HARQ process. It may be the number of HARQ-ACK information included (16 bits). For example, if the number of HARQ processes configured in terminal device 1 is 16, and terminal device 1 receives a PDCCH that deactivates the SPS PDSCH, the size of the type 4 HARQ-ACK codebook is included in the HARQ process. It may be the sum (17 bits) of the number of HARQ-ACK information (16 bits) and the HARQ-ACK information (1 bit) corresponding to the deactivation of the SPS PDSCH.

The HARQ process for SPS PDSCH may differ from the HARQ process for PDSCH scheduled by DL assignment. For example, 16 HARQ processes are configured in terminal device 1, and HARQ processes with HARQ process IDs 0, 1, and 2 are assigned for SPS PDSCH and HARQ process IDs 3, 4, 5, 6 HARQ processes, 7, 8, 9, 10, 11, 12, 13, 14, and 15, may be assigned for PDSCH scheduled by DL association.

The HARQ process for SPS PDSCH may be the same as the HARQ process for PDSCH scheduled by DL assignment. For example, if the terminal device 1 is configured with 16 HARQ processes, the HARQ process IDs assigned for the SPS PDSCH are 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, The HARQ process IDs are 11, 12, 13, 14, and 15 and are assigned for PDSCH scheduled by DL assessment are 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 , 11, 12, 13, 14, and 15.

When the HARQ process ID for the SPS PDSCH and the HARQ process ID of the PDSCH scheduled by DL acknowledgment are the same and the terminal device 1 receives a PDCCH containing a DCI format that triggers a report of type 4 HARQ-ACK codebook. , The terminal device 1 reports HARQ-ACK and NDI corresponding to the SPS PDSCH based on the RNTI in which the PDCCH is scrambled, or HARQ-ACK and NDI corresponding to the PDSCH scheduled by DL association. You may decide whether to report. Here, when the RNTI is C-RNTI, the terminal device 1 may report the HARQ-ACK information and NDI corresponding to the PDSCH scheduled by DL assert. Further, when the RNTI is CS-RNTI, the terminal device 1 may report the HARQ-ACK information and the NDI corresponding to the SPS PDSCH.

The terminal device 1 may consider that the HARQ-ACK information corresponding to the deactivation of the SPS PDSCH belongs to the HARQ process in which the HARQ process ID is a predetermined value (consider). Here, the predetermined value may be 0, 1 or an integer from 0 to 15. Further, the predetermined value may be a value equal to the smallest HARQ process ID among the HARQ process IDs belonging to one or a plurality of HARQ processes composed of a certain serving cell. Also, the predetermined value may be equal to the smallest HARQ process ID among the HARQ process IDs belonging to one or more HARQ processes configured for SPS PDSCH in a serving cell. Further, the predetermined value may be a value equal to the largest HARQ process ID among the HARQ process IDs belonging to one or more HARQ processes composed of a certain serving cell. Also, the predetermined value may be equal to the largest HARQ process ID among the HARQ process IDs belonging to one or more HARQ processes configured for SPS PDSCH in a serving cell.

In the type 3 HARQ-ACK codebook and the type 4 HARQ-ACK codebook, the field to which the HARQ-ACK information corresponding to the deactivation of the SPS PDSCH is mapped is the field corresponding to the HARQ process in which the HARQ process ID is a predetermined value. You may. Here, the predetermined value may be 0, 1 or an integer from 0 to 15. Further, the predetermined value may be a value equal to the smallest HARQ process ID among the HARQ process IDs belonging to one or a plurality of HARQ processes composed of a certain serving cell. Also, the predetermined value may be equal to the smallest HARQ process ID among the HARQ process IDs belonging to one or more HARQ processes configured for SPS PDSCH in a serving cell. Further, the predetermined value may be a value equal to the largest HARQ process ID among the HARQ process IDs belonging to one or more HARQ processes composed of a certain serving cell. Also, the predetermined value may be equal to the largest HARQ process ID among the HARQ process IDs belonging to one or more HARQ processes configured for SPS PDSCH in a serving cell.

An example relating to the type 3 HARQ-ACK codebook will be described. For example, in a serving cell, HARQ process # 1 is configured for PDSCH scheduled by DL assessment, HARQ process # 2 and HARQ process # 3 are configured for SPS PDSCH. The terminal device 1 stores'NACK'as HARQ-ACK for HARQ process # 2 corresponding to SPS PDSCH, and stores'ACK'as HARQ-ACK for HARQ process # 3 corresponding to SPS PDSCH. In addition, the terminal device 1 receives the PDCCH that deactivates the SPS PDSCH, and successfully deactivates the SPS PDSCH, so that it stores ‘ACK’. The terminal device 1 receives the PDSCH scheduled by the DL assignment, stores "1" as the NDI value for the HARQ process # 1 corresponding to the PDSCH, and stores "1" as the HARQ-ACK information for the HARQ process # 1. Is stored, and the HARQ trigger field of the DCI format containing the DL assignment indicates that the HARQ-ACK information stored in the terminal device 1 is reported to the base station device 3. The terminal device 1 includes'ACK'stored as HARQ-ACK information for HARQ process # 1 and NDI value '1' for HARQ process # 1 in the type 3 HARQ-ACK codebook, and is configured for SPS PDSCH. 'ACK' and NDI stored as HARQ-ACK information corresponding to the deactivation of SPS PDSCH for HARQ process # 2 having the smallest HARQ process ID among one or more HARQ processes. Predetermined values corresponding to'ACK'and NDI are included in the type 3 HARQ-ACK codebook and stored as HARQ-ACK corresponding to HARQ process # 3 for SPS PDSCH for HARQ process # 3. Include the value of in the type 3 HARQ-ACK codebook.

The'predetermined value corresponding to NDI'does not function as NDI because there is no NDI value for SPS PDSCH, but it is a value to be set in the NDI field included in the type 4 HARQ-ACK codebook (placeholder value). It may be.

The'predetermined value corresponding to NDI'does not function as NDI because there is no NDI value for SPS PDSCH, but the terminal device 1 converts the HARQ-ACK information corresponding to SPS PDSCH into the type 4 HARQ-ACK codebook. It may be a value indicating whether it is included or whether the HARQ-ACK information corresponding to the deactivation of SPS PDSCH is included in the type 4 HARQ-ACK codebook. For example, _{when the'predetermined} value corresponding to NDI'is X NDI2, it may mean that the terminal device 1 includes the HARQ-ACK information corresponding to the SPS PDSCH in the type 4 HARQ-ACK codebook. For example, _{if the'predetermined} value corresponding to NDI'is Y NDI2, it may mean that the terminal device 1 has included the HARQ-ACK information corresponding to the deactivation of the SPS PDSCH in the type 4 HARQ-ACK codebook. Good. Here, X _NDI2 may be 0 or 1. Further, Y _NDI2 may be 0, 1 or a value different from _{X NDI2.} For example, if X _NDI2 is 0, Y _NDI2 may be 1. For example, if X _NDI2 is 1, Y _NDI2 may be 0.

An example relating to the type 4 HARQ-ACK codebook will be described. For example, in a serving cell, HARQ process # 1 is configured for PDSCH scheduled by DL assessment, HARQ process # 2 and HARQ process # 3 are configured for SPS PDSCH. The terminal device 1 stores '1' as the value of NDI for the HARQ process # 1 corresponding to the PDSCH scheduled by DL assert, stores'ACK' as the HARQ-ACK for the HARQ process # 1, and stores it in the SPS PDSCH. 'NACK' is stored as the HARQ-ACK for the corresponding HARQ process # 2, and'ACK' is stored as the HARQ-ACK for the HARQ process # 3 corresponding to the SPS PDSCH. In addition, the terminal device 1 receives the PDCCH that deactivates the SPS PDSCH, and successfully deactivates the SPS PDSCH, so that it stores ‘ACK’. Terminal device 1 contains '1' as the value of the NDI field for HARQ process # 1, '1' as the value of the NDI field for HARQ process # 2, and '0' as the value of the NDI field for HARQ process # 3. Receives a DCI format that triggers the transmission of a type 4 HARQ-ACK codebook, including. The terminal device 1 has the same value of the NDI stored for the HARQ process # 1 and the value of the NDI field for the HARQ process # 1 indicated by the DCI format that triggers the transmission of the type 4 HARQ-ACK codebook. Corresponds to the deactivation of SPS PDSCH because'ACK'stored as HARQ-ACK information for HARQ process # 1 is included in the type 4 HARQ-ACK codebook and the PDCCH that deactivates SPS PDSCH is received. It is judged that the HARQ-ACK information is reported, and it is stored as the HARQ-ACK information corresponding to the deactivation of the SPS PDSCH in the HARQ process # 2 having the smallest HARQ process ID among the HARQ processes configured for the SPS PDSCH. SPS PDSCH because the value of the NDI field indicated by the DCI format that triggers the transmission of type 4 HARQ-ACK codebook to HARQ process # 3 is '0', including the'ACK' that is being performed in the type 4 HARQ-ACK codebook. It is determined that the HARQ-ACK information corresponding to the HARQ process # 3 of the above is reported, and the'ACK' stored as the HARQ-ACK corresponding to the HARQ process # 3 corresponding to the SPS PDSCH is included in the type 4 HARQ-ACK codebook.

In the type 3 HARQ-ACK codebook and the type 4 HARQ-ACK codebook, the fields to which the HARQ-ACK information corresponding to the deactivation of the SPS PDSCH is mapped are other than the fields set for the HARQ process configured in the terminal device 1. It may be a field of.

An example relating to the type 3 HARQ-ACK codebook will be described. For example, in a serving cell, HARQ process # 1 is configured for PDSCH scheduled by DL assessment, HARQ process # 2 and HARQ process # 3 are configured for SPS PDSCH. The terminal device 1 stores'NACK'as HARQ-ACK for HARQ process # 2 corresponding to SPS PDSCH, and stores'ACK'as HARQ-ACK for HARQ process # 3 corresponding to SPS PDSCH. In addition, the terminal device 1 receives the PDCCH that deactivates the SPS PDSCH, and successfully deactivates the SPS PDSCH, so that it stores ‘ACK’. The terminal device 1 receives the PDSCH scheduled by the DL assignment, stores "1" as the NDI value for the HARQ process # 1 corresponding to the PDSCH, and stores "1" as the HARQ-ACK information for the HARQ process # 1. Is stored, and the HARQ trigger field of the DCI format containing the DL assignment indicates that the HARQ-ACK information stored in the terminal device 1 is reported to the base station device 3. The terminal device 1 includes'ACK'stored as HARQ-ACK information for HARQ process # 1 and NDI value '1' for HARQ process # 1 in the type 3 HARQ-ACK codebook, and HARQ for HARQ process # 2. Includes'NACK'stored as -ACK information and a predetermined value corresponding to NDI in the type 3 HARQ-ACK codebook, and for HARQ process # 3, HARQ-ACK corresponding to HARQ process # 3 for SPS PDSCH. The type 3 HARQ-ACK codebook contains the predetermined values corresponding to'ACK'and NDI stored as, and the HARQ-ACK information'ACK' corresponding to the deactivation of SPS PDSCH and the predetermined value corresponding to NDI. And are included in the type 3 HARQ-ACK codebook. Here, the terminal device 1 does not have to include a predetermined value corresponding to NDI in the type 3 HARQ-ACK codebook. Further, the terminal device 1 does not have to include a predetermined value corresponding to the NDI corresponding to the deactivation of the SPS PDSCH in the type 3 HARQ-ACK codebook.

An example relating to the type 4 HARQ-ACK codebook will be described. For example, in a serving cell, HARQ process # 1 is configured for PDSCH scheduled by DL assessment, HARQ process # 2 and HARQ process # 3 are configured for SPS PDSCH. The terminal device 1 stores '1' as the value of NDI for HARQ process # 1 corresponding to the PDSCH scheduled by DL assert, stores'ACK' as HARQ-ACK for HARQ process # 1, and stores it in SPS PDSCH. 'NACK' is stored as the HARQ-ACK for the corresponding HARQ process # 2, and'ACK' is stored as the HARQ-ACK for the HARQ process # 3 corresponding to the SPS PDSCH.
In addition, the terminal device 1 receives the PDCCH that deactivates the SPS PDSCH, and successfully deactivates the SPS PDSCH, so that it stores'ACK'. Terminal device 1 contains '1' as the value of the NDI field for HARQ process # 1, '1' as the value of the NDI field for HARQ process # 2, and '0' as the value of the NDI field for HARQ process # 3. Receives a DCI format that triggers the transmission of a type 4 HARQ-ACK codebook, including. The terminal device 1 has the same value of the NDI stored for the HARQ process # 1 and the value of the NDI field for the HARQ process # 1 indicated by the DCI format that triggers the transmission of the type 4 HARQ-ACK codebook. By the DCI format that triggers the transmission of the type 4 HARQ-ACK codebook to the HARQ process # 2 by including'ACK' stored as the HARQ-ACK information for the HARQ process # 1 in the type 4 HARQ-ACK codebook. Since the value of the indicated NDI field is '0', it is judged that the HARQ-ACK information corresponding to HARQ process # 2 of SPS PDSCH is reported, and stored as HARQ-ACK corresponding to HARQ process # 2 corresponding to SPS PDSCH. SPS PDSCH because the value of the NDI field indicated by the DCI format that triggers the transmission of type 4 HARQ-ACK codebook to HARQ process # 3 is '0', including the'NACK'that is being included in the type 4 HARQ-ACK codebook. Includes'ACK', which is stored as HARQ-ACK corresponding to HARQ process # 3 corresponding to SPS PDSCH, in the type 4 HARQ-ACK codebook, judging that it is a report of HARQ-ACK information corresponding to HARQ process # 3. Include the HARQ-ACK information'ACK' corresponding to the deactivation of the SPS PDSCH in the type 4 HARQ-ACK codebook. Here, in the HARQ process corresponding to SPS PDSCH, the terminal device 1 does not have to refer to the value of the NDI field included in the DCI format. Further, in the HARQ process corresponding to SPS PDSCH, the terminal device 1 refers to the value of the NDI field included in the DCI format, and when the value of the NDI field is X _NDI3 , corresponds to the HARQ process ID for SPS PDSCH. When the HARQ-ACK information to be generated is included in the type 4 HARQ-ACK codebook and the value of the NDI field included in the DCI format is Y _NDI , the HARQ-ACK information corresponding to the deactivation of the SPS PDSCH is included in the type 4 HARQ-. It may be included in the ACK codebook. Here, X _NDI3 may be 0 or 1. Further, Y _NDI3 may be 0, 1 or a value different from _{X NDI3.} For example, when X _NDI3 is 0, Y _NDI3 may be 1. For example, if X _NDI3 is 1, Y _NDI3 may be 0.

The HARQ-ACK information corresponding to the deactivation of the SPS PDSCH may be transmitted using the HARQ-ACK information field in the Type 3 HARQ-ACK codebook for the HARQ process containing a HARQ process ID. Here, the HARQ process ID may be determined by {HARQ process ID = [floor (CURRET_slot × 10 / (numberOfSlotsPerFrame × periodicity))] mod nofHARQ-Processes}. Here, CURRENT_slot is the number of the slot in which the PDCCH that deactivates the SPS PDSCH is received, and is determined by {CURRET_slot = [(SFN × numberOfSlotsPerFrame) + slot number in the frame]}. Further, the numberOfSlotsPerFrame may be the number of slots constituting one frame. When the SCS is 15 kHz, the numberOfSlotsPerFrame may be 10. When the SCS is 30 kHz, the numberOfSlotsPerFrame may be 20. When the SCS is 60 kHz, the numberOfSlotsPerFrame may be 40. When the SCS is 120 kHz, the numberOfSlotsPerFrame may be 80. When the SCS is 240 kHz, the numberOfSlotsPerFrame may be 160. The periodicity may be the period of the SPS PDSCH. Further, the periodicity may be 10, 20, 32, 40, 64, or 80. However, it may be 128, 160, 320, or 640. The nrovHRQ-Processes may be the number of HARQ processes configured for the SPS PDSCH. The SFN (System frame number) may be the number of the frame containing the slot in which the PDCCH that deactivates the SPS PDSCH is received. Here, the frame may be a frame having a length of 10 ms. The HARQ process ID determined by the above formula is referred to as a release HARQ process ID (HARQ process ID for release).

In a HARQ process, the terminal device 1 stores HARQ-ACK information for the HARQ process, the terminal device 1 receives the PDCCH that deactivates the SPS PDSCH, and the terminal device 1 receives the type 3 HARQ-ACK. When the DCI format that triggers the report (transmission) of the codebook is received and the HARQ process ID for release is the same as the HARQ process ID possessed by the certain HARQ process, the terminal device 1 is stored in the terminal device 1. The HARQ-ACK information for the HARQ process and the value of NDI are not discarded, and the HARQ-ACK information corresponding to the deactivation of SPS PDSCH is displayed in the HARQ-ACK information field for the HARQ process in the type 3 HARQ-ACK codebook. It may be mapped and a value corresponding to the NDI may be mapped to the NDI field for the HARQ process in the type 3 HARQ-ACK codebook.

In a HARQ process, the terminal device 1 stores the HARQ-ACK information for the HARQ process, the terminal device 1 receives the PDCCH that deactivates the SPS PDSCH, and the terminal device 1 receives the type 4 HARQ-ACK. When a DCI format that triggers a codebook report (transmission) is received and the HARQ process ID for release is the same as the HARQ process ID possessed by the HARQ process, the terminal device 1 is stored in the terminal device 1. The HARQ-ACK information for the HARQ process and the value of NDI are not discarded, and the HARQ-ACK information corresponding to the deactivation of SPS PDSCH is displayed in the HARQ-ACK information field for the HARQ process in the type 4 HARQ-ACK codebook. You may map.

In a HARQ process, the terminal device 1 stores HARQ-ACK information for the HARQ process, the terminal device 1 receives the PDCCH that deactivates the SPS PDSCH, and the terminal device 1 receives the type 3 HARQ-ACK. When the DCI format that triggers the report (transmission) of the codebook is received and the HARQ process ID for release is the same as the HARQ process ID possessed by the certain HARQ process, the terminal device 1 is stored in the terminal device 1. Discard the HARQ-ACK information and NDI value for the HARQ process, and map the HARQ-ACK information corresponding to the deactivation of SPS PDSCH in the HARQ-ACK information field for the HARQ process in the type 3 HARQ-ACK codebook. Then, a value corresponding to NDI may be mapped to the NDI field for the HARQ process in the type 3 HARQ-ACK codebook.

In a HARQ process, the terminal device 1 stores the HARQ-ACK information for the HARQ process, the terminal device 1 receives the PDCCH that deactivates the SPS PDSCH, and the terminal device 1 receives the type 4 HARQ-ACK. Report of codebook (
When the DCI format that triggers transmission) is received and the HARQ process ID for release is the same as the HARQ process ID possessed by the HARQ process, the terminal device 1 has the HARQ stored in the terminal device 1. The HARQ-ACK information for the process and the value of NDI may be discarded and the HARQ-ACK information corresponding to the deactivation of SPS PDSCH may be mapped to the HARQ-ACK information field for the HARQ process in the type 4 HARQ-ACK codebook. ..

Including the HARQ-ACK information in the PUCCH may mean including the HARQ-ACK information in the codebook.

The present invention can realize efficient communication. The present invention can realize efficient transmission / reception of HARQ-ACK information. The present invention can realize efficient transmission / reception of a HARQ-ACK codebook. The present invention can eliminate the recognition mismatch between the terminal device 1 and the base station device 3 in the HARQ process and allow the HARQ process to operate appropriately.

Hereinafter, aspects of various devices according to one aspect of the present embodiment will be described.

(1) In order to achieve the above object, the aspect of the present invention has taken the following measures. That is, the first aspect of the present invention is a terminal device including a processor and a memory for storing a computer program code, which receives a PDCCH that deactivates the SPS PDSCH and receives one or more HARQs. A second unit that includes a receiving unit that receives a PDCCH including a DCI format that triggers transmission of a codebook containing -ACK information, and a transmitting unit that transmits a PUCCH containing the codebook, and corresponds to the deactivation of the SPS PDSCH. One HARQ-ACK information is included in the one or more HARQ-ACK information, and corresponds to the HARQ process having the smallest HARQ process ID among the one or more configured HARQ processes in the codebook. The field contains the first HARQ-ACK information.

(2) A second aspect of the present invention is a DCI that is a base station apparatus that transmits a PDCCH that deactivates the SPS PDSCH and triggers the transmission of a codebook containing one or more HARQ-ACK information. The one or a plurality of first HARQ-ACK information corresponding to the deactivation of the SPS PDSCH is provided with a transmission unit for transmitting a PDCCH including a format and a receiving unit for receiving a PUCCH including the codebook. The first HARQ-ACK information is included in the field corresponding to the HARQ process having the smallest HARQ process ID among the one or more configured HARQ processes in the codebook. ..

The program that operates in the base station device 3 and the terminal device 1 according to the present invention is a program that controls a CPU (Central Processing Unit) or the like (makes a computer function) so as to realize the functions of the above-described embodiment related to the present invention. It may be a program). The information handled by these devices is temporarily stored in RAM (Random Access Memory) during the processing, and then various ROMs such as Flash ROM (Read Only Memory) and HD.
It is stored in D (Hard Disk Drive), and is read, modified, and written by the CPU as needed.

Note that the terminal device 1 and a part of the base station device 3 in the above-described 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 by the computer system and executed.

The "computer system" referred to here is a computer system built in the terminal device 1 or the base station device 3, and includes hardware such as an OS and peripheral devices. Further, the "computer-readable recording medium" refers to a portable medium such as a flexible disk, a magneto-optical disk, a ROM, or a CD-ROM, or a storage device such as a hard disk built in a computer system.

Furthermore, a "computer-readable recording medium" is a medium that dynamically holds a program for a short period of time, such as a communication line when a program is transmitted via a network such as the Internet or a communication line such as a telephone line. In that case, a program may be held for a certain period of time, such as a volatile memory inside a computer system serving as a server or a client. Further, the above-mentioned program may be a program for realizing a part of the above-mentioned functions, and may further realize the above-mentioned functions in combination with a program already recorded in the computer system.

The terminal device 1 may consist of at least one processor and at least one memory including computer program instructions (computer programs). The memory and the computer program instruction (computer program) may be configured such that the terminal device 1 performs the operations and processes described in the above-described embodiment by using a processor. The base station apparatus 3 may consist of at least one processor and at least one memory including computer program instructions (computer programs). The memory and the computer program instruction (computer program) may be configured such that the base station apparatus 3 performs the operations and processes described in the above-described embodiment by using a processor.

Further, the base station device 3 in the above-described embodiment can also be realized as an aggregate (device group) composed of a plurality of devices. Each of the devices constituting the device group may include a part or all of each function or each function block of the base station device 3 according to the above-described embodiment. As the device group, it suffices to have each function or each function block of the base station device 3. Further, the terminal device 1 according to the above-described embodiment can also communicate with the base station device as an aggregate.

Further, the base station apparatus 3 in the above-described embodiment may be EUTRAN (Evolved Universal Terrestrial Radio Access Network) and / or NG-RAN (NextGen RAN, NR RAN). Further, the base station apparatus 3 in the above-described embodiment may have a part or all of the functions of the upper node with respect to the eNodeB and / or the gNB.

Further, a part or all of the terminal device 1 and the base station device 3 in the above-described embodiment may be realized as an LSI which is typically an integrated circuit, or may be realized as a chipset. Each functional block of the terminal device 1 and the base station device 3 may be individually chipped, or a part or all of them may be integrated into a chip. Further, the method of making an integrated circuit is not limited to LSI, and may be realized by a dedicated circuit or a general-purpose processor. Further, when an integrated circuit technology that replaces an LSI appears due to advances in semiconductor technology, it is also possible to use an integrated circuit based on this technology.

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

Although the embodiments of the present invention have been described in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and design changes and the like within a range not deviating from the gist of the present invention are also included. Further, the present invention can be variously modified within the scope of the claims, and the technical scope of the present invention also includes embodiments obtained by appropriately combining the technical means disclosed in the different embodiments. Is done. In addition, the elements described in each of the above-described embodiments include a configuration in which elements having the same effect are replaced with each other.

1 (1A, 1B, 1C) Terminal device 3 Base station device 10, 30 Wireless transmission / reception section 11, 31 Antenna section 12, 32 RF section 13, 33 Baseband section 14, 34 Upper layer Processing section 15, 35 Medium access control layer Processing unit 16, 36 Radio resource control layer processing unit

Claims (4)

A receiver that receives a PDCCH that deactivates the SPS PDSCH and receives a PDCCH containing a DCI format that triggers the transmission of a codebook containing one or more HARQ-ACK information.
A transmission unit for transmitting a PUCCH including the codebook is provided.
The first HARQ-ACK information corresponding to the deactivation of the SPS PDSCH is included in the one or more HARQ-ACK information.
A terminal device that includes the first HARQ-ACK information in a field corresponding to a HARQ process having the smallest HARQ process ID among one or more configured HARQ processes in the codebook. A transmitter that transmits a PDCCH that deactivates the SPS PDSCH and transmits a PDCCH containing a DCI format that triggers the transmission of a codebook containing one or more HARQ-ACK information.
A receiving unit that receives a PUCCH including the codebook is provided.
The first HARQ-ACK information corresponding to the deactivation of the SPS PDSCH is included in the one or more HARQ-ACK information.
A base station apparatus that includes the first HARQ-ACK information in a field corresponding to a HARQ process having the smallest HARQ process ID among one or more configured HARQ processes in the codebook. A communication method used for terminal devices.
A step of receiving a PDCCH that deactivates the SPS PDSCH and a PDCCH containing a DCI format that triggers the transmission of a codebook containing one or more HARQ-ACK information.
A step of transmitting a PUCCH containing the codebook is provided.
The first HARQ-ACK information corresponding to the deactivation of the SPS PDSCH is included in the one or more HARQ-ACK information.
A communication method in which the first HARQ-ACK information is included in the field corresponding to the HARQ process having the smallest HARQ process ID among one or more configured HARQ processes in the codebook. A communication method used for base station equipment.
A step of transmitting a PDCCH that deactivates the SPS PDSCH and a PDCCH containing a DCI format that triggers the transmission of a codebook containing one or more HARQ-ACK information.
A step of receiving a PUCCH containing the codebook is provided.
The first HARQ-ACK information corresponding to the deactivation of the SPS PDSCH is included in the one or more HARQ-ACK information.
A communication method in which the first HARQ-ACK information is included in the field corresponding to the HARQ process having the smallest HARQ process ID among one or more configured HARQ processes in the codebook.

Images