WO2021006333A1 - Terminal device and communication method - Google Patents

Abstract

Provided is a terminal device which, upon receiving a DCI format including PDSCH scheduling information, updates the value of an NDI which is stored with respect to a HARQ process on the basis of an NDI field included in the DCI format including the PDSCH scheduling information. Upon receiving a DCI format that does not include PDSCH scheduling information and triggers a report of a HARQ-ACK codebook, the terminal device: determines a HARQ-ACK that is reported with respect to a HARQ process on the basis of an NDI field included in the DCI format that does not include PDSCH scheduling information and triggers a report of a HARQ-ACK codebook; and retains the value of the NDI stored with respect to the HARQ process.

Description

Terminal device and communication method

The present invention relates to a terminal device and a communication method.
The present application claims priority with respect to Japanese Patent Application No. 2019-129117 filed in Japan on July 11, 2019, the contents of which are incorporated herein by reference.

The wireless access system and wireless network of cellular mobile communication (hereinafter referred to as "Long Term Evolution (LTE)" or "EUTRA: Evolved Universal Terrestrial Radio Access") is a third-generation partnership project (3GPP: 3rdPergement). It is being examined in Project). In LTE, the base station device is also called an eNodeB (evolved NodeB), and the terminal device is also called 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.

In 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). In a single technical framework, NR is assumed to satisfy three scenarios: eMBB (enhanced Mobile Broadband), mMTC (massive Machine Type Communication), and URLLC (Ultra Reliable and Low Latency Communication). There is.

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.

Data error detection result, data reception result (received data was not wrong, received) from the data receiving side to the data transmitting side so that the data retransmission can be controlled appropriately. It is necessary to give appropriate feedback such as (the data was incorrect, the data was not received), etc. The data transmitting side retransmits the data that was not properly received by the receiving side based on the information fed back from the data receiving side. For example, the data transmitting side is a base station device, the data receiving side is a terminal device, the data is a transport block (transport block transmitted / received by PDSCH), and the data error detection result and reception result are HARQ-ACK. Efficient communication is achieved by realizing appropriate retransmission control. One aspect of the present invention provides a terminal device for efficient communication and a communication method used for the terminal device.

(1) The first aspect of the present invention is a terminal device including a processor and a memory for storing a computer program code, and when a DCI format including PDSCH scheduling information is received, PDSCH scheduling information is obtained. Updated the value of NDI stored for the HARQ process based on the NDI field included in the DCI format including, received the DCI format that does not include the PDSCH scheduling information and triggers the report of the HARQ-ACK codebook. In the case, the HARQ-ACK reported to the HARQ process is determined based on the NDI field included in the DCI format that does not include the PDSCH scheduling information and triggers the report of the HARQ-ACK codebook, and the HARQ process is determined. Performs an operation that includes retaining the stored NDI value.

(2) A second aspect of the present invention is a communication method used for a terminal device, and when a DCI format including PDSCH scheduling information is received, an NDI field included in the DCI format including PDSCH scheduling information. Does not include the step of updating the NDI value stored for the HARQ process based on, and the PDSCH scheduling information, but includes the PDSCH scheduling information when a DCI format that triggers a HARQ-ACK codebook report is received. Instead, the HARQ-ACK reported to the HARQ process is determined based on the NDI field included in the DCI format that triggers the reporting of the HARQ-ACK codebook, and the value of the NDI stored for the HARQ process is determined. Includes steps to hold and.

According to one aspect of the present invention, the terminal device can efficiently communicate. In addition, the base station device can efficiently perform communication.

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.

Hereinafter, embodiments of the present invention will be described.

"A and / or B" may be a term including "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 PCell (Primary Cell). An SCG is a group of serving cells composed of at least PSCell (Primary Secondary Cell). The PCell 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. A serving cell identifier is a short identifier for identifying a serving cell. The serving cell identifier may be given by an upper layer parameter.

The frame configuration will be described below.

At least OFDM (Orthogonal Frequency Division Multiplex) is used in the wireless communication system according to one aspect of the present embodiment. 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 is composed of a frame of 10 ms. The frame is composed of 10 subframes. The length of the subframe is 1 ms. The frame length may be given regardless of the subcarrier spacing Δf. That is, the frame setting may be given regardless of μ. The 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 the setting μ of a subcarrier spacing. For example, the first slot number n ^μ _s may be given in ascending order in the range of 0 to N ^{subframe, μ} _slot -1 within the ^subframe . 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. N ^slot _symbs may be given at least based on 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-ConfigurationCommon. CP settings may be given at least based on upper 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 explained 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 delay spread (delay spread), Doppler spread (Doppler spread), Doppler shift (Doppler shift), average gain (average gain), average delay (avatage gain), and beam parameters (spray). It may include at least some or all. 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 ^(μ) _simb N ^{subframe, μ} _symb OFDM symbols is provided for each subcarrier spacing setting and carrier set. 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 perform transmission / reception 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 region. 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 BWP 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. A set of uplink BWPs may include one or more uplink BWPs.

The upper layer parameter is a parameter included in the signal of the upper layer. The signal of the upper layer may be RRC (Radio Access Control) signaling or MAC CE (Medium 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) Map to BCCH logical channel or CCCH logical channel Feature C2) Map to radioRelocationConfigCommon information element C3) Map to PBCH

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 indicate at least the PRACH time / frequency resources.

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 radioResourceConfigDedicated information element may include at least information indicating a setting unique 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, upper layer messages that are mapped to DCCH logical channels and that include at least radioResourceConfigCommon may be included in the common RRC signaling. Further, the upper layer message that is mapped to the DCCH logical channel and does not include the radioResourceConfigCommon information element may be included in the dedicated RRC signaling. Further, an upper layer message that is mapped to a DCCH logical channel and contains at least a radioResourceControlDedicated 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. The 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)

PUCCH may be used to transmit uplink control information (UCI: Uplink Control Information). Uplink control information includes channel status information (CSI: Channel State Information), scheduling request (SR: Scheduling Request), transport block (TB: Transport block, MAC PDU: Medium Access Control, Digital Control Data Unit). -Includes a part or all of HARQ-ACK (Hybrid Automatic Repeat request ACKnowledgement) corresponding to Sharp Channel, PDSCH: Physical Downlink Shared Channel.

HARQ-ACK may include at least the HARQ-ACK bit (HARQ-ACK information) corresponding to one transport block. The HARQ-ACK bit may indicate 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 Request (SR) may be at least 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 sent when the upper layer instructs it to send 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 PUSCH resources for initial transmission. A negative SR may indicate that the scheduling request is not triggered by the upper layer. Negative SR may be transmitted if the upper layer does not instruct it to transmit the scheduling request.

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

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 at least used to transmit transport blocks (TB, MAC PDU, UL-SCH, PUSCH). The 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 an initial connection establishment procedure, a handover procedure, a connection re-establishment procedure, synchronization (timing adjustment) for PUSCH transmission, and some or all of the resource requests for 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 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 Signal)
・ SRS (Sounding Reference Signal)
-UL PTRS (UpLink Phase Tracking Reference Signal)

UL DMRS is associated with PUSCH and / or PUCCH transmission. UL DMRS is multiplexed with PUSCH or PUCCH. The base station apparatus 3 may use UL DMRS to correct the propagation path of PUSCH or PUCCH. Hereinafter, transmitting both PUSCH and UL DMRS related to the PUSCH is referred to simply as transmitting the PUSCH. Hereinafter, transmitting PUCCH and UL DMRS related to the PUCCH together is referred to simply 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.

SRS does not have to be related to PUSCH or PUCCH transmission. 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 DMRS. The association between the UL PTRS and the UL DMRS group may be that the antenna port of the UL PTRS and a part or all of 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 smallest 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 at least used to transmit a master information block (MIB: Master Information 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.

PDCCH is at least used for transmitting 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 allocation 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 field)

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

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

The MCS field may be at least used to indicate a 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 transport block of the PUSCH. 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 part 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 field)
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 allocation 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 field)
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. When the index of the slot containing the last OFDM symbol of the PDSCH is slot n, the first OFDM symbol of the PUCCH or the first OFDM symbol of the PUSCH containing at least HARQ-ACK corresponding to the transport block contained in the PDSCH The index of the included slot 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 instruction 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 allocation 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 field)
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.

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

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 Unified 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 office) (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. The position of the subframe (slot) to be formed and the number of subframes (slots) of the uplink subframe (uplink slot) are shown. 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 downlink grant or uplink grant is transmitted and received by PDCCH including 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 specified, 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.

Note that the 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 a 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 transmitted PDCCHs may be included. A field (T-DAI: Total Downlink Assignment Index field) indicating the total number of PDCCHs to be transmitted may be included.

The terminal device 1 may be associated with a PDSCH group identifier (PGI: PDSCHGroupID) 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: Requested PDSCH Group) 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 a plurality of PDSCH groups. The RPG instructions may be given corresponding to 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 series 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, assume 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 in the timing indicator 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.

One or more control resource sets (CORESET: Control REsource SET) may be set in the terminal device 1. 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 to 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. The control resource set may be composed of continuous resources (Located resources). The control resource set may be composed of discontinuous resources (distributed resources).

In the frequency region, 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 the control resource set to the resource block may be given at least based on the upper 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 called CORESET # 0. CORESET # 0 may be a control resource set at index # 0.

A certain control resource set may be a dedicated control resource set (Dedicated control 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 C-RNTI values. 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 (CCE) may be configured in the control resource set, and an index (CCE index) may be assigned to each CCE.

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

The search area may be configured to include one or more PDCCH candidates of one or more aggregation levels (Aggression level). 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 upper layer parameters. The terminal device 1 may monitor at least one or a plurality of search area sets (Search paceset) in a slot in which 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 a plurality of 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 area may have two types, CSS (Comon Search Space, common search area) 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 C-RNTI values. 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.

The CSS is for type 0PDCCH CSS for the SI-RNTI scrambled DCI format used to transmit system information in the primary cell, and for the 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 Accessed 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) , 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 including paging information and / or information such as 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 message 4. Temporary C-RNTI is at least used to schedule a PDSCH containing 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.

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 included 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 / / or 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 resources in the search area are composed of control channel configuration units (CCE: Control Channel Elements). 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 Element). PRB is also simply referred to as RB (Resource Block).

PDSCH is at least used to send / 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 Signal)

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

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 in order to correct the propagation path of the PBCH, PDCCH, or PDSCH.

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 a signal used to compensate for phase noise. The pattern of PTRS envisioned by the terminal device may be given at least based on the upper layer parameters and / or DCI.

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

The downlink physical 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-Shared Channel) and DL-SCH (Downlink-Shared Channel) are transport channels. The channel used in the medium access control (MAC: Medium Access Control) layer is called a transport channel. The unit of the transport channel used in the MAC layer is also called a transport block (TB) or MAC PDU. HARQ (Hybrid Automatic Repeat Request) is controlled for each transport block in the MAC layer. 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 (higher layer). For example, the base station device 3 and the terminal device 1 may perform RRC signaling (RRC message: Radio Resource Control message; RRC information: Radio Resource transmission / reception 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 an upper 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 terminal device 1 using dedicated signaling.

BCCH (Broadcast Control Channel), CCCH (Control Control Channel), and DCCH (Dedicated Control Channel) are logical channels. For example, BCCH is an upper layer channel used to transmit / receive MIBs. 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.

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 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 processes the MAC layer, the packet data integration protocol (PDCP: Packet Data Convergence Protocol) layer, the wireless link control (RLC: Radio Link Control) layer, and the RRC layer.

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: down cover), and removes unnecessary frequency components. The RF unit 12 outputs the processed analog signal to the baseband unit.

The baseband unit 13 converts the analog signal input from the RF unit 12 into a digital signal. The baseband unit 13 removes a portion corresponding to CP (Cyclic Prefix) from the converted digital signal, performs a fast Fourier transform (FFT: Fast Fourier Transform) on the signal from which the CP has been removed, and transmits a signal in the frequency domain. Extract.

The baseband unit 13 performs inverse fast Fourier transform (IFFT) on the data to generate an OFDM symbol, adds CP to the generated OFDM symbol, generates a baseband digital signal, and basebands the data. Converts a band digital signal into an analog signal. The baseband unit 13 outputs the converted analog signal to the RF unit 12.

The RF unit 12 uses a low-pass filter to remove 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 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 wireless resource control layer processing unit 36 manages various setting information / parameters of each terminal device 1. The wireless 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 part 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 may carry out carrier sense prior to the transmission of the physical signal. 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 (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 a 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 the physical channel is given based on the carrier sense is also called 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. It is also called LBT fileure that it is determined that the transmission of a physical signal is impossible as a result of LBT.

The value of the section in which the channel is continuously occupied (channel occupancy section) (Channel Occupancy Time: COT) may be predetermined depending on the country, or may be predetermined for each frequency band. The base station device 3 may notify the terminal device 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 (Channel State Information: CSI), scheduling request indicating a PUSCH resource request (Scheduling Request: SR), and downlink data (Transport block, Medium Access PDU PDU PDU PDU PDU -It may include at least one of HARQ-ACK (Hybrid Automatic Repeat request ACKnowledgement) for Sharp Channel: DL-SCH, Physical Downlink Shared Channel: PDSCH.

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

If the downlink data is successfully decrypted, an ACK for the downlink data is generated. If the downlink data is not successfully decrypted, a NACK is 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 with one HARQ-ACK bit may mean that the HARQ-ACK bit corresponds to a PDSCH containing the one or more transport blocks.

HARQ control for one transport block may be called a HARQ process. One HARQ process identifier may be given for each HARQ process. The DCI format contains a field indicating the HARQ process identifier.

NDI (New Data Indicator) is shown in DCI format for each HARQ process. For example, the NDI field is included in the DCI format (DL association) containing the PDSCH scheduling information. The NDI field is 1 bit. The terminal device 1 stores (stores) the value of NDI for each HARQ process. The base station device 3 stores (stores) the NDI value for each HARQ process for each terminal device 1. The terminal device 1 updates the stored NDI value using the detected DCI format NDI field. The base station apparatus 3 sets the updated NDI value or the non-updated NDI value in the NDI field of the DCI format and transmits it to the terminal apparatus 1. The terminal device 1 updates 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 determines whether the received transport block is a new transmission or a retransmission based on the value of the NDI field of the DCI format (DL assignment). The terminal device 1 compares the previously received NDI value to the transport block of a HARQ process, and if the detected DCI format NDI field value is toggled, the received transport block Judge that it is a new transmission. 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. 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 transmits the non-toggled NDI to the terminal apparatus 1. Terminal 1 is received if the value of the detected DCI format NDI field is not toggled (if it is the same) compared to the previously received NDI value for the transport block of a HARQ process. It is 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, and the HARQ-ACK codebook (HARQ-ACK codebook). ) May be reported to the base station apparatus 3.

For DCI format 1_0, the value of the HARQ indicator field may be mapped to a set of slots (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 the HARQ-ACK is transmitted for the received PDSCH. is there. For example, dl-DataToUL-ACK is a list of one, two, or three, four, five, six, seven, or eight timings. If dl-DataToUL-ACK is a list of timings, the HARQ indicator field is 0 bits. When 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. For example, dl-DataToUL-ACK consists of a list of timings with any value in the range 0-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 indicates the order (number) of the elements of dl-DataToUL-ACK. For example, when 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. The 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 sets the size of the HARQ-ACK codebook according to the size of the dl-DataToUL-ACK. For example, when dl-DataToUL-ACK consists of 8 elements, the size of HARQ-ACK codebook is 8. For example, when dl-DataToUL-ACK consists of two elements, the size of HARQ-ACK codebook is 2. Each HARQ-ACK information constituting the HARQ-ACK codebook is HARQ-ACK information for PDSCH reception at each slot timing of dl-DataToUL-ACK. This type of HARQ-ACK codebook is also referred to as 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. When the HARQ instruction field is "000", it corresponds to the first 0 in the list of dl-DataToUL-ACK as the corresponding timing. That is, the HARQ instruction field "000" corresponds to the value 0 indicated by the index 1 of dl-DataToUL-ACK. The HARQ instruction field "001" corresponds to the second 7 in the list of dl-DataToUL-ACK as the corresponding timing. The HARQ instruction field "010" corresponds to the third 15 in the list of dl-DataToUL-ACK as the corresponding timing. The HARQ instruction field "011" corresponds to the fourth 23 in the list of dl-DataToUL-ACK as the corresponding timing. When the HARQ instruction field is "100", the corresponding timing corresponds to the fifth 31 in the list of dl-DataToUL-ACK. The HARQ instruction field "101" corresponds to the sixth 39 in the list of dl-DataToUL-ACK as the corresponding timing. The HARQ instruction field "110" corresponds to the seventh 47 in the list of dl-DataToUL-ACK as the corresponding timing. The HARQ instruction field "111" corresponds 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 transmits 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 transmits the corresponding HARQ-ACK in the 7th slot from the received PDSCH slot. When the received HARQ instruction field indicates "010", the terminal device 1 transmits 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 transmits the corresponding HARQ-ACK in the 23rd slot from the received PDSCH slot. When the received HARQ instruction field indicates "100", the terminal device 1 transmits the corresponding HARQ-ACK in the 31st slot from the received PDSCH slot. When the received HARQ instruction field indicates "101", the terminal device 1 transmits the corresponding HARQ-ACK in the 39th slot from the received PDSCH slot. When the received HARQ instruction field indicates "110", the terminal device 1 transmits the corresponding HARQ-ACK in the 47th slot from the received PDSCH slot. When the received HARQ instruction field indicates "111", the terminal device 1 transmits the corresponding HARQ-ACK in the 55th slot from the received PDSCH slot.

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. If 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. Also, if the HARQ indicator 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 PDCCH containing DCI format 1_1 and is configured not to monitor 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). If 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 determines a set of multiple opportunities for receiving one or more candidate PDSCHs to transmit the corresponding HARQ-ACK information on the PUCCH of a slot. The terminal device 1 determines 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 of is 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 PDSCH is not received in the slot to be used, NACK is set as HARQ-ACK information.

The HARQ instruction field included in the DCI format received by the PDCCH of the slot n-1 indicates 1. The HARQ instruction field included in the DCI format received by the PDCCH of the n-2 slot indicates 2. The HARQ instruction field included in the DCI format received by the PDCCH of the n-3 slot indicates 3. The HARQ instruction field included in the DCI format received by the PDCCH of the slot n-4 indicates 4. The HARQ instruction field included in the DCI format received by the PDCCH of the n-5 slot indicates 5. The HARQ instruction field included in the DCI format received by the PDCCH of the slot n-6 indicates 6. The HARQ instruction field included in the DCI format received by the PDCCH of the slot n-7 indicates 7. The HARQ instruction field included in the DCI format received by the PDCCH of the slot n-8 indicates 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. 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 PDCCH in the slot m, and the HARQ instruction field included in the DCI format is 4. Is shown. The terminal device 1 determines 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)). Judge that it is ACK information.

The dl-DataToUL-ACK can 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. Waits for 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 a different type of HARQ-ACK codebook may be used. A type of HARQ-ACK codebook called a Dynamic HARQ-ACK codebook will be described.

A HARQ-ACK codebook corresponding to a PDSCH group is one or more HARQ-corresponding to any one or more transport blocks contained in any one or more PDSCHs contained in the PDSCH group. Given based on the ACK bit. The HARQ-ACK codebook is given at least based on a set of PDCCH monitoring opportunities (Monitoringoccasion 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. , 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 is based on the DCI format field. 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 indicates the cumulative number of PDSCHs or transport blocks scheduled to receive the corresponding DCI format. The size of the HARQ-ACK codebook may be set based on the value of the total DAI field in DCI format. The total DAI field indicates 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 placed in the slot of index n is also the set of PDCCH monitoring opportunities (monitoring occupation for PDCCH for slot # n) for slot n. It is called. Here, the set of monitoring opportunities for PDCCH includes 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. The 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 is 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 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 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 instructed to be transmitted based on DL acknowledgment (triggered, requested). It is an ACK codebook (second HARQ-ACK codebook). The DCI format including the HARQ indicator field is DL association (Downlink association). DL association is a DCI format used for PDSCH scheduling. DL association is a DCI format used for PDSCH allocation. The Semi-static HARQ-ACK codebook is configured based on the dl-StatoUL-ACK and the HARQ instruction field. The size of the Semi-static HARQ-ACK codebook is based on the size included in dl-StatoUL-ACK. The timing of the slots included in the Semi-static HARQ-ACK codebook or the Dynamic HARQ-ACK codebook is based on the value of the HARQ instruction field and the slot in which the DCI including the HARQ instruction field is received.

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

The first HARQ-ACK codebook contains HARQ-ACK information for a plurality or all HARQ processes. For example, HARQ process means HARQ process used for PDSCH. For example, all HARQ processes 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 is 16. For example, the number of HARQ processes that can be used in the five Serving cells is 80. For example, a plurality of HARQ processes means a plurality of HARQ processes configured by RRC signing. For example, the plurality of HARQ processes means a plurality of HARQ processes instructed by the Downlink control information. For example, a plurality of HARQ processes means a plurality of HARQ processes that are explicitly or implicitly instructed. For example, the number of a plurality of HARQ processes is eight. For example, the number of a plurality of HARQ processes is 10.

The second HARQ-ACK codebook can be said to be a HARQ-ACK codebook whose transmission is triggered by a DCI format (DL acknowledgment) accompanied by PDSCH scheduling information. The first HARQ-ACK codebook is based on a DCI format different from the DCI format with PDSCH scheduling information (DCI format only for instructing the transmission of the HARQ-ACK codebook, DCI format with PUSCH scheduling information). It can be said that it is a HARQ-ACK codebook in which transmission is triggered.

The second HARQ-ACK codebook can be said to be a HARQ-ACK codebook in which the relationship between the slot through which the HARQ-ACK codebook is transmitted and received and the PDSCH slot corresponding to the HARQ-ACK included in the HARQ-ACK codebook is defined. The HARQ process used for the PDSCH corresponding to the HARQ-ACK included in the second HARQ-ACK codebook is not limited in advance, and is set by the scheduling of the base station apparatus 3. It can be said that the first HARQ-ACK codebook is 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 HARQ-ACK included in the first HARQ-ACK codebook is received is not limited in advance, and is set by the scheduling of the base station apparatus 3.

The DCI format that triggers the transmission of the first HARQ-ACK codebook includes an NDI field. The DCI format that triggers the transmission of the first HARQ-ACK codebook includes an NDI field for each HARQ process that includes HARQ-ACK in the first 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 first HARQ-ACK codebook based on the NDI field included in the DCI format that triggers the transmission of the first 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, the terminal device 1 corresponds to the case where the NDI value stored for each HARQ process and the NDI value indicated by the DCI format that triggers the transmission of the first HARQ-ACK codebook are the same. The HARQ-ACK information stored (stored) for the HARQ process is included in the first HARQ-ACK codebook, and the NDI value stored for each HARQ process and the first HARQ-ACK If the value of NDI indicated by the DCI format that triggers the transmission of the codebook is different, the NACK is included in the first HARQ-ACK codebook for the corresponding HARQ process.

An example will be explained. 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 the first HARQ-ACK codebook, including '1' as the value of NDI for HARQ process # 1. In the terminal device 1, the value of NDI stored for HARQ process # 1 and the value of NDI for HARQ process # 1 indicated by the DCI format that triggers the transmission of the first HARQ-ACK codebook are the same. It is determined that there is, and'ACK'stored as HARQ-ACK for HARQ process # 1 is included in the first HARQ-ACK codebook.

An example will be explained. 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 the first HARQ-ACK codebook, including '0' as the value of NDI for HARQ process # 1. When the terminal device 1 differs between 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 first HARQ-ACK codebook. Judge and include'NACK'in the first HARQ-ACK codebook as the HARQ-ACK for HARQ process # 1. In the terminal device 1, the value of NDI stored for HARQ process # 1 and the value of NDI for HARQ process # 1 indicated by the DCI format that triggers the transmission of the first HARQ-ACK codebook are different. Therefore, it is recognized that the detection of the DCI format including the scheduling information for HARQ process # 1 has been 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 (type 3 HARQ-ACK codebook) (first HARQ-ACK codebook) is received, it does not include PDSCH scheduling information and HARQ- 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 ACK 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 first HARQ-ACK codebook, the terminal device 1 determines the HARQ-ACK reported to the HARQ process based on the NDI field. However, it is not used (not stored or stored) as the NDI value of the previous transmission for the HARQ process.

An example will be explained. 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 the first HARQ-ACK codebook, including '0' as the value of NDI for HARQ process # 1. When the terminal device 1 differs between 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 first HARQ-ACK codebook. Judging, it is judged as'NACK'as HARQ-ACK for HARQ process # 1, and '0' is not used (not stored, not stored) as the value of NDI for HARQ process # 1, and it is already stored. Continue to use '1' (keep remembering, keep storing).

An example will be explained. 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. The terminal device 1 contains a DCI format that triggers the transmission of the first HARQ-ACK codebook, including '0' as the NDI value for HARQ process # 1 and '0' as the NDI value for HARQ process # 2. Receive. When the terminal device 1 differs between 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 first HARQ-ACK codebook. Judge and judge as'NACK'as HARQ-ACK for HARQ process # 1. The terminal device 1 has the same NDI value for the HARQ process # 2 and the NDI value for the HARQ process # 2 indicated by the DCI format that triggers the transmission of the first HARQ-ACK codebook. It is determined that there is, and'ACK'stored as HARQ-ACK for HARQ process # 2 is included in the first 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 the 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 (keep storing, keep storing) the already stored '0', which is the same as the value of the NDI field notified in the DCI format, as the value of NDI for HARQ process # 2.

The HARQ process is linked to the transport block. The terminal device 1 does not apply the NDI field for a HARQ process included in the DCI format instructing the transmission of the first HARQ-ACK codebook to the NDI value of the previous transmission of the transport block of the HARQ process ( Not used).

One aspect of the present invention can realize efficient communication. One aspect of the present invention can realize efficient transmission / reception of HARQ-ACK information. One aspect of the present invention can realize efficient transmission / reception of a HARQ-ACK codebook. One aspect of 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. The terminal device 1 appropriately recognizes a detection error of the DCI format including the scheduling information of the HARQ process PDSCH based on the NDI field for a HARQ process included in the DCI format instructing the transmission of the first HARQ-ACK codebook. At the same time, it is possible to appropriately perform processing related to the determination of new transmission or retransmission of the transport block related to the HARQ process.

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, and when a DCI format including PDSCH scheduling information is received, the PDSCH scheduling information is included. When the value of NDI stored for the HARQ process is updated based on the NDI field included in the DCI format, and the DCI format that does not include the PDSCH scheduling information and triggers the report of the HARQ-ACK codebook is received. , PDSCH scheduling information is not included, HARQ-ACK to be reported to the HARQ process is determined based on the NDI field included in the DCI format that triggers the report of the HARQ-ACK codebook, and stored in the HARQ process. Performs an operation that includes retaining the value of the NDI that has been set.

(2) A second aspect of the present invention is a communication method used for a terminal device, and when a DCI format including PDSCH scheduling information is received, an NDI field included in the DCI format including PDSCH scheduling information. Does not include the step of updating the NDI value stored for the HARQ process based on, and the PDSCH scheduling information, but includes the PDSCH scheduling information when a DCI format that triggers a HARQ-ACK codebook report is received. Instead, the HARQ-ACK reported to the HARQ process is determined based on the NDI field included in the DCI format that triggers the reporting of the HARQ-ACK codebook, and the value of the NDI stored for the HARQ process is determined. Includes steps to hold and.

The program operating in the base station device 3 and the terminal device 1 according to one aspect of the present invention controls a CPU (Central Processing Unit) or the like so as to realize the functions of the above embodiment related to one aspect of the present invention. It may be a program (a program that makes a computer function). Then, the information handled by these devices is temporarily stored in RAM (Random Access Memory) at the time of processing, and then stored in various ROMs such as Flash ROM (Read Only Memory) and HDD (Hard Disk Drive). If necessary, the CPU reads, corrects, and writes.

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 be a program for realizing 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 a computer program instruction (computer program). 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 device 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. In addition, one aspect of the present invention can be variously modified within the scope of the claims, and the technical aspects of the present invention are also obtained by appropriately combining the technical means disclosed in the different embodiments. Included in the range. 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.

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

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 (2)

1. When a terminal device including a processor and a memory for storing a computer program code receives a DCI format including PDSCH scheduling information, HARQ is based on an NDI field included in the DCI format including PDSCH scheduling information. When the value of NDI stored for the process is updated, the PDSCH scheduling information is not included, and the DCI format that triggers the report of HARQ-ACK codebook is received, the PDSCH scheduling information is not included and HARQ- To determine the HARQ-ACK to be reported to the HARQ process based on the NDI field included in the DCI format that triggers the report of the ACK codebook, and to retain the value of the NDI stored for the HARQ process. A terminal device that performs an operation that includes.
2. When a DCI format including PDSCH scheduling information is received, which is a communication method used for a terminal device, an NDI stored in the HARQ process based on the NDI field included in the DCI format including PDSCH scheduling information. When the step of updating the value of PDSCH and the DCI format that does not include the PDSCH scheduling information and triggers the report of HARQ-ACK codebook are received, the PDSCH scheduling information is not included and triggers the report of HARQ-ACK codebook. A communication method including a step of determining HARQ-ACK to be reported to a HARQ process based on an NDI field included in the DCI format and holding the value of NDI stored for the HARQ process.

Images