Terminal device and communication method

Abstract

A terminal device transmits a PUCCH in a certain slot, receives a plurality of DCI formats in a set of PDCCH monitoring opportunities corresponding to the certain slot, wherein there are a plurality of PUCCHs in the certain slot, and in a case where the plurality of PUCCHs include a first PUCCH including a first type of HARQ-ACK codebook and a second PUCCH including a second type of HARQ-ACK codebook, the second PUCCH is not transmitted.

Description

Technical Field

[0001] This invention relates to a terminal device and a communication method.

[0002] This application claims priority to Japanese Patent Application No. 2020-010586, filed in Japan on January 27, 2020, the contents of which are incorporated herein by reference. Background Technology

[0003] The 3rd Generation Partnership Project (3GPP) studied radio access methods and radio networks for cellular mobile communications (hereinafter referred to as "Long Term Evolution (LTE)" or "Evolved Universal Terrestrial Radio Access (EUTRA)"). In LTE, base station equipment is also called eNodeB (evolved NodeB), and terminal equipment is also called UE (User Equipment). LTE is a cellular communication system that uses multiple base station equipment configured in a cell-like structure to cover an area. A single base station equipment can manage multiple serving cells.

[0004] Within 3GPP, research was conducted on the next-generation standard (NR: New Radio) in order to make recommendations to IMT (International Mobile Telecommunication)-2020, the standard for next-generation mobile communication systems developed by the International Telecommunication Union (ITU) (Non-Patent Document 1). NR was required to meet the requirements of the following three scenarios within a single technical framework: eMBB (enhanced Mobile Broadband), mMTC (massive Machine-Type Communication), and URLLC (Ultra-Reliable and Low-Latency Communication).

[0005] Furthermore, the application of NR in the unlicensed spectrum was investigated (Non-Patent Document 2). The study explored applying NR supporting a 100MHz bandwidth to carriers in the unlicensed spectrum to achieve data rates of several Gbps.

[0006] Existing technical documents

[0007] Non-patent literature

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

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

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

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

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

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

[0014] The problem the invention aims to solve

[0015] One aspect of the present invention provides a terminal device capable of efficiently receiving uplink and / or downlink transmissions, a communication method for the terminal device, a base station device capable of efficiently receiving downlink and / or uplink transmissions, and a communication method for the base station device.

[0016] Technical solution

[0017] (1) A first aspect of the present invention is a terminal device comprising: a transmitting unit that transmits a HARQ-ACK codebook via PUCCH in a certain time slot; and a receiving unit that receives a plurality of DCI formats in a set of PDCCH monitoring opportunities corresponding to the certain time slot, wherein the resources for the PUCCH are determined by a PUCCH resource indication field included in a DCI format identified as the last received among the plurality of DCI formats, and wherein if at least one of the plurality of DCI formats is set to trigger a first HARQ-ACK codebook type, the HARQ-ACK codebook is generated using the first HARQ-ACK codebook type, and if none of the plurality of DCI formats is set to trigger the first HARQ-ACK codebook type, the HARQ-ACK codebook is generated using a second HARQ-ACK codebook different from the first HARQ-ACK codebook.

[0018] (2) A second aspect of the present invention is a terminal device comprising: a transmitting unit that transmits a PUCCH in a certain time slot; and a receiving unit that receives a plurality of DCI formats in a set of PDCCH monitoring opportunities corresponding to the certain time slot, wherein a plurality of PUCCHs exist in the certain time slot, and when the plurality of PUCCHs includes a first PUCCH including a HARQ-ACK codebook of a first type and a second PUCCH including a HARQ-ACK codebook of a second type, the second PUCCH is not transmitted.

[0019] (3) A third aspect of the present invention is a base station apparatus comprising: a receiving unit that receives a HARQ-ACK codebook via PUCCH in a certain time slot; and a transmitting unit that transmits a plurality of DCI formats in a set of PDCCH monitoring opportunities corresponding to the certain time slot, wherein the resources for the PUCCH are determined by a PUCCH resource indication field included in a DCI format identified as the last transmitted among the plurality of DCI formats, wherein if at least one of the plurality of DCI formats is set to trigger a first HARQ-ACK codebook type, the HARQ-ACK codebook is generated using the first HARQ-ACK codebook type, and if none of the plurality of DCI formats is set to trigger the first HARQ-ACK codebook type, the HARQ-ACK codebook is generated using a second HARQ-ACK codebook different from the first HARQ-ACK codebook.

[0020] (4) The fourth aspect of the present invention is a base station apparatus comprising: a receiving unit that receives a PUCCH in a certain time slot; and a transmitting unit that transmits a plurality of DCI formats in a set of PDCCH monitoring opportunities corresponding to the certain time slot, wherein there are a plurality of PUCCHs in the certain time slot, and the second PUCCH is not transmitted when the plurality of PUCCHs include a first PUCCH including a HARQ-ACK codebook of a first type and a second PUCCH including a HARQ-ACK codebook of a second type.

[0021] (5) A fifth aspect of the present invention is a communication method for a terminal device, comprising: a step of transmitting a HARQ-ACK codebook via PUCCH in a certain time slot; and a step of receiving a plurality of DCI formats in a set of PDCCH monitoring opportunities corresponding to the certain time slot, wherein the resources for the PUCCH are determined by a PUCCH resource indication field included in the last received DCI format among the plurality of DCI formats, wherein if at least one of the plurality of DCI formats is set to trigger a first HARQ-ACK codebook type, the HARQ-ACK codebook is generated using the first HARQ-ACK codebook type, and if none of the plurality of DCI formats is set to trigger the first HARQ-ACK codebook type, the HARQ-ACK codebook is generated using a second HARQ-ACK codebook different from the first HARQ-ACK codebook.

[0022] (6) The sixth aspect of the present invention is a communication method for a terminal device, comprising: a step of transmitting a PUCCH in a certain time slot; and a step of receiving a plurality of DCI formats in a set of PDCCH monitoring opportunities corresponding to the certain time slot, wherein a plurality of PUCCHs exist in the certain time slot, and the second PUCCH is not transmitted when the plurality of PUCCHs includes a first PUCCH including a HARQ-ACK codebook of a first type and a second PUCCH including a HARQ-ACK codebook of a second type.

[0023] (7) A seventh aspect of the present invention is a communication method for a base station device, comprising: receiving a HARQ-ACK codebook via PUCCH in a certain time slot; and transmitting a plurality of DCI formats in a set of PDCCH monitoring opportunities corresponding to the certain time slot, wherein the resources for the PUCCH are determined by a PUCCH resource indication field included in the last transmitted DCI format identified among the plurality of DCI formats, and generating the HARQ-ACK codebook using the first HARQ-ACK codebook type when at least one of the plurality of DCI formats is set to trigger a first HARQ-ACK codebook type, and generating the HARQ-ACK codebook using a second HARQ-ACK codebook different from the first HARQ-ACK codebook when none of the plurality of DCI formats is set to trigger the first HARQ-ACK codebook type.

[0024] (8) The eighth aspect of the present invention is a communication method for a base station device, comprising: a step of receiving a PUCCH in a certain time slot; and a step of transmitting a plurality of DCI formats in a set of PDCCH monitoring opportunities corresponding to the certain time slot, wherein a plurality of PUCCHs exist in the certain time slot, and the second PUCCH is not transmitted when the plurality of PUCCHs includes a first PUCCH including a HARQ-ACK codebook of a first type and a second PUCCH including a HARQ-ACK codebook of a second type.

[0025] Beneficial effects

[0026] According to one aspect of the present invention, the terminal device can perform communication efficiently. Furthermore, the base station device can perform communication efficiently. Attached Figure Description

[0027] Figure 1 This is a conceptual diagram of a wireless communication system according to one embodiment of this invention.

[0028] Figure 2 N represents one embodiment of this method. slot symb An example of the relationship between the subcarrier spacing setting μ, the time slot setting, and the CP setting.

[0029] Figure 3 This is a schematic diagram illustrating an example of a resource grid in a subframe of one embodiment of this work.

[0030] Figure 4 This is a schematic block diagram illustrating the configuration of a terminal device 1 according to one embodiment of this invention.

[0031] Figure 5This is a schematic block diagram illustrating the configuration of a base station device 3 according to one embodiment of this invention.

[0032] Figure 6 This diagram illustrates an example of receiving the SPS PDSCH in this embodiment.

[0033] Figure 7 This is a diagram illustrating an example of a type 3HARQ-ACK codebook where SPS PDSCH is not constituted in this embodiment.

[0034] Figure 8 This is a diagram illustrating an example of the reporting of HARQ-ACK information corresponding to the PDSCH and SPS PDSCH scheduled via DL authorization when an SPS PDSCH is configured in the terminal device 1 in this embodiment.

[0035] Figure 9 This diagram illustrates an example of multiple overlapping PUCCHs in this embodiment.

[0036] Figure 10 This is a diagram illustrating an example of the application of TPC commands in this implementation. Detailed Implementation

[0037] The embodiments of the present invention will be described below.

[0038] "A and / or B" can be a phrase that includes "A", "B" or "A and B".

[0039] A parameter or information element represents one or more values. The parameter or information element can include at least the parameter or information representing those one or more values. A parent parameter can be a single parent parameter. A parent parameter can also be an information element (IE: Information Element) that includes multiple parameters.

[0040] Figure 1 This is a conceptual diagram of a wireless communication system according to one embodiment of this invention. Figure 1 In this wireless communication system, there are terminal devices 1A to 1C and base station device 3 (gNB). Hereinafter, terminal devices 1A to 1C will also be referred to as terminal device 1 (UE).

[0041] Base station device 3 can be configured to include one or both of MCG (Master Cell Group) and SCG (Secondary Cell Group). MCG is a group of serving cells that includes at least one PCell (Primary Cell). SCG is a group of serving cells that includes at least one PSCell (Primary Secondary Cell). The PCell can be a serving cell assigned based on the initial connection. MCG can also be configured to include one or more SCells (Secondary Cells). The serving cell identity is a short identifier used to identify the serving cell. The serving cell identity can be given by upper-layer parameters.

[0042] The frame structure will be explained below.

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

[0044] The subcarrier spacing (SCS) can be determined by the subcarrier spacing Δf = 2. μ • Given at 15kHz. For example, the subcarrier spacing configuration μ can be set to any one of 0, 1, 2, 3, 4, and / or 5. The subcarrier spacing configuration μ can be given by upper-layer parameters for a specific BWP (BandWidth Part).

[0045] In one embodiment of the wireless communication system, the time unit T is used. c To represent the length of the time domain. The time unit is T. c It can be made by T c =1 / (Δf) max ·N f Δf is given by ) max This can be the maximum subcarrier spacing supported in a wireless communication system according to one embodiment of this invention. Δf max It can also be Δfmax =480kHz. N f It can be N f =4096. The constant κ is κ = Δf max ·N f / (Δf ref N f，ref ) = 64. Δf ref It can be 15kHz. N f，ref It could be 2048.

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

[0047] Downlink and / or uplink transmissions consist of 10ms frames. Each frame comprises 10 subframes. Each subframe is 1ms long. The frame length can be given independently of the subcarrier spacing Δf. That is, the frame setting can be given independently of μ. Similarly, the subframe length can also be given independently of the subcarrier spacing Δf. In other words, the subframe setting can also be given independently of μ.

[0048] The number and index of the time slots included in a subframe can be given for setting the subcarrier interval μ. For example, the first time slot number n μ s It can be 0 to N within the subframe subframe，μ slot The values ​​are given in ascending order within the range of -1. The number and index of the time slots included in the frame can also be given for setting the subcarrier spacing μ. For example, the second time slot number n... μ s，f It can be 0 to N within the frame. frame，μ slot The values ​​within the range of -1 are given in ascending order. Consecutive N values... slot symb One OFDM symbol can be included in one time slot. slot symb It can be given based on at least some or all of the slot configuration and / or CP (Cyclic Prefix) settings. The slot configuration can be given at least by the upper-layer parameter tdd-UL-DL-ConfigurationCommon. The CP setting can be given at least by the upper-layer parameter. The CP setting can also be given at least by dedicated RRC signaling. The first and second slot numbers are also called slot numbers (slot indexes).

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

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

[0051] Antenna ports are defined as follows: a channel transmitting symbols at one antenna port can be estimated based on a channel transmitting other symbols at the same antenna port. When the large-scale property of a channel transmitting symbols at one antenna port can be estimated based on a channel transmitting symbols at another antenna port, the two antenna ports are said to be QCL (Quasi Co-Located). The large-scale property can include at least the long-range characteristics of the channel. The large-scale property can also include at least some or all of the following: delay spread, Doppler spread, Doppler shift, average gain, average delay, and spatial Rx parameters. QCL for the first and second antenna ports with respect to beam parameters can mean that the receiver's assumed receive beam for the first antenna port is the same as the receiver's assumed receive beam for the second antenna port. QCL for the first and second antenna ports with respect to beam parameters can also mean that the receiver's assumed transmit beam for the first antenna port is the same as the receiver's assumed transmit beam for the second antenna port. Terminal device 1 can assume that both antenna ports are QCLs if the large-scale characteristics of the channel transmitting symbols at one antenna port can be estimated based on the channel transmitting symbols at the other antenna port. Alternatively, it can be assumed that both antenna ports are QCLs.

[0052] Given N μ RB，x N RB sc Subcarriers and N (μ) symb N subframe，μ symb The resource grids of each OFDM symbol are used for setting the subcarrier spacing and the carrier set, respectively. μ RB，x N can represent the number of resource blocks given for setting the subcarrier spacing μ for carrier x. μ RB，x It can also be the maximum number of resource blocks given for setting the subcarrier spacing μ for carrier x. Carrier x represents either a downlink carrier or an uplink carrier. That is, x is "DL" or "UL". N μ RB It includes N μ RB，DL and / or N μ RB，UL the title. N RB scThis can represent the number of subcarriers included in a resource block. At least one resource grid can be given per antenna port p and / or per subcarrier spacing setting μ and / or per transmission direction setting. The transmission direction includes at least a downlink (DL) and an uplink (UL). Hereinafter, the set of parameters including at least some or all of the antenna port p, subcarrier spacing setting μ, and transmission direction setting is also referred to as the first radio parameter set. That is, a resource grid can be given for each first radio parameter set.

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

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

[0055] Figure 3 This is a schematic diagram illustrating an example of a resource grid in a subframe of one embodiment of this work. Figure 3 In the resource grid, the horizontal axis represents the time-domain index.sym The vertical axis represents the frequency domain index k. sc In a subframe, the frequency domain of the resource grid includes N. μ RB N RB sc 14.2 subcarriers. Within a subframe, the temporal domain of the resource grid can include 14.2 subcarriers. μ A resource block consists of N OFDM symbols. RB sc A resource block can correspond to one OFDM symbol in the time domain. It can also correspond to 14 OFDM symbols. Furthermore, it can correspond to one or more time slots. Finally, it can correspond to one subframe.

[0056] Terminal device 1 can instruct the use of only a subset of the resource grid for transmission and reception. This subset of the resource grid is also called the BWP, which can be given based on at least a portion or all of the upper-layer parameters and / or the DCI. The BWP is also referred to as the Bandwidth Part (BP). That is, terminal device 1 may also instruct the use of only a portion of the resource grid for transmission and reception. Specifically, terminal device 1 may instruct the use of only a portion of the frequency resources within the resource grid. A BWP can consist of multiple resource blocks in the frequency domain. A BWP can also consist of multiple consecutive resource blocks in the frequency domain. The BWP configured for the downlink carrier is also called the downlink BWP. The BWP configured for the uplink carrier is also called the uplink BWP.

[0057] One or more downlink BWPs can be configured for terminal device 1. Terminal device 1 can attempt to receive physical channels (e.g., PDCCH, PDSCH, SS / PBCH, etc.) in one of the downlink BWPs. This one downlink BWP is also called the activated downlink BWP.

[0058] One or more uplink BWPs can also be configured for terminal device 1. Terminal device 1 can attempt to transmit physical channels (e.g., PUCCH, PUSCH, PRACH, etc.) in one of the one or more uplink BWPs. This one uplink BWP is also called the active uplink BWP.

[0059] A set of downlink BWPs can be configured for each serving cell. This set of downlink BWPs can include one or more downlink BWPs. Similarly, a set of uplink BWPs can be configured for each serving cell. This set of uplink BWPs can include one or more uplink BWPs.

[0060] Upper-layer parameters are the parameters included in the signals of the upper layer. These upper-layer signals can be RRC (Radio Resource Control) signaling or MAC CE (Medium Access Control Control Element). In this context, the upper-layer signals can be either RRC layer signals or MAC layer signals.

[0061] The upper-layer signal can be common RRC signaling. Common RRC signaling can have at least some or all of the following characteristics C1 to C3.

[0062] Feature C1) is mapped to either the BCCH logical channel or the CCCH logical channel.

[0063] Feature C2) includes at least the radioResourceConfigCommon information element.

[0064] Feature C3) mapped to PBCH

[0065] The `radioResourceConfigCommon` information element may include information representing settings common to the serving cell. Settings common to the serving cell may include at least PRACH settings. These PRACH settings may represent at least one or more random access preamble indices. These PRACH settings may also represent at least the time / frequency resources of the PRACH.

[0066] The upper-layer signals can also be dedicated RRC signaling. Dedicated RRC signaling can have at least some or all of the following characteristics D1 to D2.

[0067] Feature D1) is mapped to the DCCH logical channel

[0068] Feature D2) includes at least the radioResourceConfigDedicated information element.

[0069] The `radioResourceConfigDedicated` information element may include at least information indicating settings specific to terminal device 1. The `radioResourceConfigDedicated` information element may also include at least information indicating BWP settings. These BWP settings may at least indicate the frequency resources of the BWP.

[0070] For example, MIB, first system information, and second system information can be included in the common RRC signaling. Furthermore, upper-layer messages mapped to the DCCH logical channel and including at least the radioResourceConfigCommon information element can be included in the common RRC signaling. Additionally, upper-layer messages mapped to the DCCH logical channel but excluding the radioResourceConfigCommon information element can be included in the dedicated RRC signaling. Furthermore, upper-layer messages mapped to the DCCH logical channel and including at least the radioResourceConfigDedicated information element can be included in the dedicated RRC signaling.

[0071] The first system information may at least represent the time index of the SS (Synchronization Signal) block. The SS block is also called the SS / PBCH block. The first system information may also include at least information associated with the PRACH resource. The first system information may also include at least information associated with the initial connection settings. The second system information may be system information other than the first system information.

[0072] The radioResourceConfigDedicated information element may include at least the information associated with the PRACH resource. The radioResourceConfigDedicated information element may also include at least the information associated with the initial connection settings.

[0073] The physical channels and physical signals of various schemes in this embodiment will be described below.

[0074] An uplink physical channel can correspond to a set of resource elements carrying information generated at the upper layer. An uplink physical channel is a physical channel used in the uplink carrier. In one embodiment of this wireless communication system, at least some or all of the following uplink physical channels are used.

[0075] • PUCCH (Physical Uplink Control Channel)

[0076] • PUSCH (Physical Uplink Shared Channel)

[0077] • PRACH (Physical Random Access Channel)

[0078] PUCCH can be used to send uplink control information (UCI). Uplink control information includes some or all of the following: Channel State Information (CSI), Scheduling Request (SR), and HARQ-ACK (Hybrid Automatic Repeat Request ACK knowledgement) corresponding to the transport block (TB, MACPDU, DL-SCH, PDSCH).

[0079] HARQ-ACK may include at least one HARQ-ACK bit (HARQ-ACK information) corresponding to at least one transport block. The HARQ-ACK bit may represent an ACK (acknowledgment) or NACK (negative-acknowledgment) corresponding to one or more transport blocks. HARQ-ACK may include at least a HARQ-ACK codebook containing one or more HARQ-ACK bits. The correspondence between HARQ-ACK bits and one or more transport blocks may be that the HARQ-ACK bit corresponds to the PDSCH including the one or more transport blocks. The HARQ-ACK bit may also represent an ACK or NACK corresponding to a CBG (Code Block Group) included in the transport block.

[0080] A scheduling request (SR) can be used at least to request resources for the initial PUSCH transmission. The scheduling request bits can be used to indicate either a positive SR or a negative SR. A positive SR indicating a scheduling request bit is also called "a positive SR has been sent." A positive SR can indicate that terminal device 1 has requested resources for the initial PUSCH transmission. A positive SR can also indicate a scheduling request triggered by an upper layer. A positive SR can be sent when indicating a scheduling request from an upper layer. A negative SR indicating a scheduling request bit is also called "a negative SR has been sent." A negative SR can indicate that terminal device 1 has not requested resources for the initial PUSCH transmission. A negative SR can also indicate that a scheduling request has not been triggered by an upper layer. A negative SR can also be sent when not indicating a scheduling request from an upper layer.

[0081] Channel state information may include at least some or all of the following: Channel Quality Indicator (CQI), Precoder Matrix Indicator (PMI), and Rank Indicator (RI). CQI is an indicator associated with channel quality (e.g., transmission strength), PMI is an indicator of precoding, and RI is an indicator of transmission rank (or transmission layer number).

[0082] A PUCCH can support more than one PUCCH format (PUCCH format 0 to PUCCH format 4). A PUCCH format can be mapped and sent to a PUCCH. A PUCCH format can be sent via a PUCCH. Sending a PUCCH format can be equivalent to sending a PUCCH.

[0083] PUSCH is used at least to transmit transport blocks (TB, MAC PDU, UL-SCH, PUSCH). PUSCH may also be used to transmit at least some or all of the transport blocks, HARQ-ACK, channel state information, and scheduling requests. PUSCH is used at least to transmit random access messages.

[0084] The PRACH is used at least to send the random access preamble (Random Access Message 1). The PRACH can also be used to represent at least some or all of the following: the initial connection establishment process, the handover procedure, the connection re-establishment process, the synchronization (timing adjustment) of PUSCH transmissions, and requests for resources for the PUSCH. The random access preamble can be used to notify the base station device 3 of an index (random access preamble index) provided by the upper layer of terminal device 1.

[0085] exist Figure 1 In uplink wireless communication, the following uplink physical signals are used. These uplink physical signals may not be used to transmit information output from the upper layer, but are used by the physical layer.

[0086] • UL DMRS (Uplink Demodulation Reference Signal)

[0087] • SRS (Sounding Reference Signal)

[0088] • UL PTRS (Uplink Phase Tracking Reference Signal)

[0089] UL DMRS is associated with the transmission of PUSCH and / or PUCCH. UL DMRS is multiplexed with PUSCH or PUCCH. Base station device 3 can use UL DMRS to perform transmission path correction for PUSCH or PUCCH. Hereinafter, the UL DMRS associated with the PUSCH will be referred to only as the PUSCH transmission. Hereinafter, the UL DMRS associated with the PUCCH will be referred to only as the PUCCH transmission. The UL DMRS associated with the PUSCH is also referred to as the PUSCH UL DMRS. The UL DMRS associated with the PUCCH is also referred to as the PUCCH UL DMRS.

[0090] SRS transmission may be independent of PUSCH or PUCCH transmission. Base station device 3 can use SRS to measure channel state. SRS can be transmitted at the end of a subframe in an uplink time slot or within a specified number of OFDM symbols.

[0091] The UL PTRS can be a reference signal used at least for phase tracking. The UL PTRS can be associated with a group of UL DMRSs that includes at least one antenna port for one or more UL DMRSs. The association of the UL PTRS with the UL DMRS group can be that the antenna port of the UL PTRS and some or all of the antenna ports included in the UL DMRS group are at least QCLs. The UL DMRS group can be identified at least based on the antenna port with the smallest index among the UL DMRSs included in the UL DMRS group. The UL PTRS can be mapped to the antenna port with the smallest index among one or more antenna ports mapping a codeword. If a codeword is mapped to at least Layer 1 and Layer 2, the UL PTRS can be mapped to the Layer 1. The UL PTRS may also not be mapped to the Layer 2. The index of the antenna port mapping the UL PTRS can be given at least based on downlink control information.

[0092] exist Figure 1 In the downlink wireless communication from base station device 3 to terminal device 1, the following downlink physical channel is used. The downlink physical channel is used by the physical layer to transmit information output from the upper layer.

[0093] ·PBCH (Physical Broadcast Channel)

[0094] • PDCCH (Physical Downlink Control Channel)

[0095] • PDSCH (Physical Downlink Shared Channel)

[0096] The PBCH is used at least to transmit the Master Information Block (MIB, BCH, Broadcast Channel). The PBCH can be transmitted based on a specified transmission interval. The PBCH can be transmitted at 80ms intervals or 160ms intervals. The content of the information included in the PBCH can be updated every 80ms. Part or all of the information included in the PBCH can be updated every 160ms. The PBCH can consist of 288 subcarriers. The PBCH can also be configured to include 2, 3, or 4 OFDM symbols. The MIB may include information associated with an identifier (index) of the synchronization signal. The MIB may also include information indicating at least a portion of the slot number, subframe number, and / or radio frame number from which the PBCH is transmitted.

[0097] The PDCCH is used at least to transmit downlink control information (DCI). The PDCCH may include downlink control information for transmission. Downlink control information is also called the DCI format. Downlink control information may include at least one of downlink grant (DL grant) or uplink grant (UL grant). The DCI format used for PDSCH scheduling is also called the downlink DCI format. The DCI format used for PUSCH scheduling is also called the uplink DCI format. Downlink grant is also called downlink assignment (DL assignment) or downlink allocation (DL allocation). The uplink DCI format includes at least one or both of DCI format 0_0 and DCI format 0_1.

[0098] The DCI format 0_0 is composed of at least some or all of 1A to 1F.

[0099] 1A) Identifier for DCI formats field

[0100] 1B) Frequency domain resource assignment field

[0101] 1C) Time domain resource assignment field

[0102] 1D) Frequency hopping flag field

[0103] 1E) MCS field (MCS field: Modulation and Coding Scheme field)

[0104] 1F) First CSI request field

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

[0106] The frequency domain resource allocation field can be used to indicate at least the allocation of frequency resources used by a PUSCH scheduled by a DCI format that includes this frequency domain resource allocation field. The frequency domain resource allocation field is also known as the FDRA (Frequency Domain Resource Allocation) field.

[0107] The time-domain resource allocation field can at least be used to indicate the allocation of time resources used by a PUSCH scheduled by a DCI format that includes the time-domain resource allocation field.

[0108] The frequency hopping flag field can at least be used to indicate whether frequency hopping is applied to PUSCHs scheduled by a DCI format that includes the frequency hopping flag field.

[0109] The MCS field can be used to indicate at least a portion or all of the modulation scheme and / or target coding rate used by the PUSCH scheduled by the DCI format including the MCS field. The target coding rate can be the target coding rate used by the transport block of the PUSCH. The transport block size (TBS) can be given at least based on the target coding rate.

[0110] The First CSI Request field is used at least to indicate the CSI's reporting requirements. The size of the First CSI Request field can be a specified value. The size of the First CSI Request field can be 0, 1, 2, or 3.

[0111] DCI format 0_1 ​​consists of at least some or all of 2A to 2G.

[0112] 2A) Specific fields in DCI format

[0113] 2B) Frequency domain resource allocation field

[0114] 2C) Time-domain resource allocation field

[0115] 2D) Frequency Hopping Flag Field

[0116] 2E)MCS field

[0117] 2F) Second CSI request field

[0118] 2G) BWP field

[0119] The BWP field can be used to indicate the uplink BWP mapped to the PUSCH scheduled via DCI format 0_1.

[0120] The second CSI request field is used at least to indicate the CSI report. The size of the second CSI request field can be given at least based on the higher-level parameter ReportTriggerSize (report trigger size).

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

[0122] DCI format 1_0 is composed of at least some or all of 3A to 3H.

[0123] 3A) Identifier for DCI formats field

[0124] 3B) Frequency domain resource assignment field

[0125] 3C) Time domain resource assignment field

[0126] 3D) Frequency hopping flag field

[0127] 3E)MCS field (MCS field: Modulation and Coding Scheme field)

[0128] 3F) First CSI request field

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

[0130] 3H) PUCCH resource indicator field

[0131] The timing indication field from PDSCH to HARQ feedback can be a field indicating timing K1. When the index of the time slot including the OFDM symbol at the end of the PDSCH is time slot n, the index of the time slot including the PUCCH or PUSCH can be n+K1, where the PUCCH or PUSCH at least includes a HARQ-ACK corresponding to the transport block included in the PDSCH. When the index of the time slot including the OFDM symbol at the end of the PDSCH is time slot n, the index of the time slot including the OFDM symbol at the start of the PUCCH or the OFDM symbol at the start of the PUSCH can be n+K1, where the OFDM symbol at the start of the PUCCH or the OFDM symbol at the start of the PUSCH at least includes a HARQ-ACK corresponding to the transport block included in the PDSCH.

[0132] The PDSCH-to-HARQ feedback timing indicator field can also be referred to as the HARQ indicator field.

[0133] The PUCCH Resource Indicator field can be a field representing an index of one or more PUCCH resources included in the PUCCH Resource Set. Furthermore, the value included in the PUCCH Resource Indicator field can be a PUCCH Resource Identifier (PRI: PUCCHResource Indicator). The PRI can be used to select (determine) the PUCCH resource used in the transmission of the PUCCH. The PRI can also be used as an index to the upper-layer parameter resourceList, which includes a list of one or more PUCCH resources included in the PUCCH Resource Set given by the upper-layer parameter resourceList. That is, the PRI can be used when selecting one PUCCH resource from the one or more PUCCH resources included in the upper-layer parameter resourceList.

[0134] DCI format 1_1 can be configured to include at least some or all of 4A to 4J.

[0135] 4A) Identifier for DCI formats field

[0136] 4B) Frequency domain resource assignment field

[0137] 4C) Time domain resource assignment field

[0138] 4D) Frequency hopping flag field

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

[0140] 4F) First CSI request field

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

[0142] 4H) PUCCH resource indicator field

[0143] 4J) BWP field

[0144] The BWP field can be used to indicate the downlink BWP mapped to the PDSCH scheduled via DCI format 1_1.

[0145] DCI format 2_0 can be configured to include at least one or more slot format indicators (SFI).

[0146] Downlink control information may include Unlicensed Access Common Information (UQCI). UQCI is control information regarding access, transmission, and reception in unlicensed frequency bands. UQCI can also include information about the downlink subframe configuration for Unlicensed Access (Slot configuration). The downlink subframe configuration (Slot configuration) indicates the position of the occupied OFDM symbol in a PDCCH subframe (Slot) configured with downlink UQCI information and / or the position of the occupied OFDM symbol in the next subframe (Slot) after the PDCCH subframe (Slot) configured with downlink UQCI information. Downlink physical channels and downlink physical signals are transmitted and received within the occupied OFDM symbols. UQCI can also include information about the uplink subframe configuration (UL duration and offset) (Slot configuration). The uplink subframe structure (time slot structure) indicates the position and number of uplink subframes (time slots) starting from a PDCCH subframe (time slot) configured with information including the uplink subframe structure (time slot structure). Terminal device 1 does not request to receive downlink physical channels or downlink physical signals in the subframes (time slots) indicated by the information in the uplink subframe structure (time slot structure).

[0147] For example, the PDCCH is used to send and receive downlink control information, including downlink grants or uplink grants, such as the C-RNTI (Cell-Radio Network Temporary Identifier). For example, the PDCCH is used to send and receive unlicensed access information, including the CC-RNTI (Common Control-Radio Network Temporary Identifier).

[0148] In various embodiments of this implementation, unless otherwise stated, the number of resource blocks refers to the number of resource blocks in the frequency domain.

[0149] Downlink grants are required to schedule at least one PDSCH within a serving cell. Uplink grants are required to schedule at least one PUSCH within a serving cell.

[0150] It should be noted that various DCI formats may also include fields different from those described above. For example, they may include a field indicating whether the HARQ-ACK information of the PDSCH was correctly detected (NFI: New Feedback Indicator field). They may also include a field indicating whether the HARQ-ACK bits stored in the recording medium, such as memory, have been erased (refreshed) (NFI field).

[0151] It may also include a field indicating whether retransmissions of the sent HARQ-ACK codebook are included (NFI field). It may also include a field indicating the PDSCH group (PGI: PDSCH Group ID field) associated with the PDSCH scheduled by the DCI format. It may also include a field indicating the PDSCH group from which the HARQ-ACK information was sent (RPGI: Request PDSCHGroup ID field). It may also include a field indicating the cumulative number of PDCCHs sent (C-DAI: CounterDownlink Assignment Index field). It may also include a field indicating the total number of PDCCHs sent (T-DAI: Total Downlink Assignment Index field).

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

[0153] A Requested PDSCH Group (RPG) can be a PDSCH group corresponding to a HARQ-ACK message sent (reported) via the next PUCCH or PUSCH. An RPG can include one or more PDSCH groups. The indication of the RPG can be represented, at least based on the DCI format, in bitmap form corresponding to each PDSCH group. The RPG can be represented, at least based on the RPGI field included in the DCI format. Terminal device 1 can generate a HARQ-ACK codebook for the indicated RPG and send (report) it via PUCCH or PUSCH.

[0154] The value of K1 (information or parameter indicated by the timing indication field from PDSCH to HARQ feedback) indicated by the DCI format included in the PDCCH can be numerical or non-numerical. Here, a numerical value means a value represented by a number, for example, a value in {0, 1, 2, ..., 15}. A non-numerical value can mean a value other than a number, or it can mean that it does not represent a number. The application of numerical and non-numerical K1 values ​​will be explained below. For example, the PDSCH scheduled by this DCI format is transmitted by base station device 3 in time slot n and received by terminal device 1. When the value of K1 indicated by this DCI format is numerical, terminal device 1 can transmit (report) the HARQ-ACK information corresponding to the PDSCH via PUCCH or PUSCH in time slot n+K1. When the value of K1 indicated by this DCI format is non-numerical, terminal device 1 can delay reporting the HARQ-ACK information corresponding to the PDSCH. When the DCI format, which includes scheduling information from the PDSCH, indicates a non-numerical value for K1, the terminal device 1 may delay reporting the HARQ-ACK information corresponding to that PDSCH. For example, the terminal device 1 may store the HARQ-ACK information in a recording medium such as memory, and instead of sending (reporting) the HARQ-ACK information via the next PUCCH or PUSCH, it may trigger the transmission of the HARQ-ACK information based on at least a DCI format other than the aforementioned DCI format.

[0155] Non-numeric values ​​for K1 can be included in the sequence of upper-level parameters. These upper-level parameters can be the upper-level parameter dl-DataToUL-ACK. They can also be different from the upper-level parameter dl-DataToUL-ACK. The value of K1 can be a value represented by the timing indication field fed back to HARQ from the PDSCH included in the DCI format, within the sequence of upper-level parameters. For example, if the sequence of upper-level parameters is set to {0, 1, 2, 3, 4, 5, 15, non-numeric values}, assuming the number of bits in the timing indication field fed back to HARQ from the PDSCH is 3, the code point "000" can represent a K1 value of 0, the code point "001" can represent a K1 value of 1, and the code point "111" can represent a non-numeric value for K1. For example, if the sequence of upper-level parameters is set to {non-numeric values, 0, 1, 2, 3, 4, 5, 15}, and assuming that the number of bits in the timing indication field fed back from PDSCH to HARQ is 3, the code point "000" in the timing indication field fed back from PDSCH to HARQ can represent that the value of K1 is a non-numeric value, the code point "001" can represent that the value of K1 is 0, and the code point "111" can represent that the value of K1 is 15.

[0156] A physical channel can be mapped to a serving cell. A physical channel can also be mapped to a BWP (Block Window) assigned to a carrier within a serving cell.

[0157] Terminal device 1 can configure one or more control resource sets (CORESET). Terminal device 1 monitors PDCCHs within one or more control resource sets. Monitoring PDCCHs within one or more control resource sets can include monitoring one or more PDCCHs corresponding to each of the one or more control resource sets. It should be noted that a PDCCH can include one or more PDCCH candidates and / or a set of PDCCH candidates. Furthermore, monitoring PDCCHs can include monitoring and detecting the PDCCH and / or the DCI format transmitted via the PDCCH.

[0158] A control resource set can represent a time-domain / frequency-domain area that can map one or more PDCCHs. The control resource set can be the area where terminal device 1 monitors the PDCCH. The control resource set can consist of contiguous resources (localized resources) or discontinuous resources (distributed resources).

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

[0160] The mapping of control resource sets to resource blocks can be given at least based on upper-level parameters. These upper-level parameters may include a bitmap of resource block groups (RBGs). A resource block group can be given by six consecutive resource blocks.

[0161] The number of OFDM symbols constituting the control resource set can be given at least based on the upper-level parameters.

[0162] A control resource set can be a common control resource set. The common control resource set can be a control resource set jointly configured for multiple terminal devices 1. The common control resource set can be given based at least on some or all of the MIB, first system information, second system information, common RRC signaling, and cell ID. For example, the time and / or frequency resources of the control resource set configuring the PDCCH used for scheduling the first system information can be given at least based on the MIB.

[0163] The control resource set set in the MIB is also called CORESET#0. CORESET#0 can be the control resource set with index #0.

[0164] A control resource set can also be a dedicated control resource set. A dedicated control resource set can be a control resource set configured for use exclusively by terminal device 1. A dedicated control resource set can be given based on at least some or all of the values ​​of dedicated RRC signaling and C-RNTI. Multiple control resource sets can be constructed in terminal device 1, and each control resource set can be assigned an index (control resource set index). Alternatively, more than one control channel element (CCE) can be constructed within a control resource set, and each CCE can be assigned an index (CCE index).

[0165] The set of candidate PDCCHs monitored by terminal device 1 can be defined from the perspective of the search space. That is, the set of candidate PDCCHs monitored by terminal device 1 can be given based on the search space.

[0166] The search region can be comprised of one or more PDCCH candidates, each with one or more aggregation levels. The aggregation level of a PDCCH candidate can represent the number of CCEs that constitute that PDCCH. PDDCH candidates can be mapped to one or more CCEs.

[0167] Terminal device 1 can monitor at least one or more search areas in time slots where DRX (Discontinuous Reception) is not configured. DRX can be provided at least based on upper-layer parameters. Terminal device 1 can also monitor at least one or more search space sets in time slots where DRX is not configured. Multiple search space sets can be configured within terminal device 1. Each search space set can be assigned an index (search space set index).

[0168] A search region set can consist of at least one or more search regions. Each search region can be assigned an index (search region index).

[0169] Each search region set can be associated with at least one control resource set. Search regions sets can also be individually included within a control resource set. Indexes of the control resource sets associated with each search region set can be provided.

[0170] The search area can include two types: CSS (Common Search Space) and USS (UE-specific Search Space). CSS can be a search area shared by multiple terminal devices 1. USS can be a search area specifically configured for a single terminal device 1. CSS can be based at least on synchronization signals, MIB, first system information, second system information, common RRC signaling, dedicated RRC signaling, cell ID, etc. USS can be based at least on dedicated RRC signaling and / or C-RNTI values. CSS can be a search area set for resources (control resource elements) shared by multiple terminal devices 1. USS can be a search area set for resources (control resource elements) of each individual terminal device 1.

[0171] For CSS, Type 0 PDCCH CSS, scrambled with the DCI format using SI-RNTI for transmitting system information in the primary cell, and Type 1 PDCCH CSS, scrambled with the DCI format using RA-RNTI and TC-RNTI for initial access, can be used. For CSS, Type PDCCH CSS, scrambled with the DCI format using CC-RNTI for unlicensed access, can also be used. Terminal device 1 can monitor PDCCH candidates in these search areas. The DCI format scrambled with the specified RNTI can be a DCI format with an additional CRC (Cyclic Redundancy Check) scrambled with the specified RNTI.

[0172] Information associated with receiving the PDCCH may include information associated with an ID indicating the destination of the PDCCH. The ID indicating the destination of the PDCCH may be an ID scrambled for the CRC bits appended to the PDCCH. The ID indicating the destination of the PDCCH is also known as the RNTI (Radio Network Temporary Identifier). The information associated with receiving the PDCCH may include information associated with an ID scrambled for the CRC bits appended to the PDCCH. Terminal device 1 can attempt to receive the PDCCH based at least on the information associated with this ID included in the PBCH.

[0173] RNTIs can include: SI-RNTI (System Information RNTI), P-RNTI (Paging RNTI), C-RNTI (Common RNTI), Temporary C-RNTI, RA-RNTI (Random Access RNTI), CC-RNTI (Common Control RNTI), and INT-RNTI (Interruption RNTI). SI-RNTI is used at least for scheduling PDSCHs that include system information for transmission. P-RNTI is used at least for scheduling PDSCHs that include paging information and / or system information change notifications. C-RNTI is used at least for scheduling user data for RRC-connected terminal device 1. Temporary C-RNTI is used at least for scheduling random access message 4. Temporary C-RNTI is used at least for scheduling PDSCHs that include data mapped to CCCHs in logical channels. RA-RNTI is used at least for scheduling random access message 2. CC-RNTI is used at least for sending and receiving control information for unlicensed access. INT-RNTI is used at least for indicating pre-emption in the downlink.

[0174] It should be noted that the PDCCH and / or DCI included in the CSS may not include the CIF (Carrier Indicator Field) of the PDSCH or PUSCH that indicates which serving cell (or component carrier) the PDCCH / DCI is scheduled for.

[0175] It should be noted that when the terminal device 1 is configured to aggregate multiple serving cells and / or multiple component carriers for communication (transmission and / or reception), carrier aggregation (CA: carrier aggregation) can be used. The PDCCH and / or DCI included in the USS for the specified serving cell (specified component carrier) may include a CIF indicating which serving cell and / or which component carrier the PDCCH / DCI is scheduled for.

[0176] It should be noted that when using a serving cell and / or a component carrier to communicate with terminal device 1, the PDCCH and / or DCI included in the USS may not include the CIF indicating which serving cell and / or component carrier the PDCCH / DCI is scheduled for.

[0177] A public control resource set may include CSS. A public control resource set may also include both CSS and USS (User Profile Objects). A private control resource set may include USS. A private control resource set may include CSS.

[0178] The physical resources of the search area are composed of control channel elements (CCEs). Each CCE consists of a specified number of resource element groups (REGs). For example, a CCE can consist of 6 REGs. Each REG can consist of one OFDM symbol of one physical resource block (PRB). That is, a REG can be configured to include 12 resource elements (REs). A PRB is also simply referred to as a resource block (RB).

[0179] The PDSCH is used at least to send / receive transport blocks. The PDSCH can also be used at least to send / receive Random Access Message 2 (Random Access Response). The PDSCH can also be used at least to send / receive system information including parameters used for initial access.

[0180] exist Figure 1 In downlink wireless communication, the following downlink physical signals are used. These downlink physical signals may not be used to transmit information output from the upper layer, but are used by the physical layer.

[0181] • Synchronization signal (SS)

[0182] • DL DMRS (Downlink Demodulation Reference Signal)

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

[0184] • DL PTRS (Downlink Phase Tracking Reference Signal)

[0185] Synchronization signals are used to enable terminal device 1 to obtain downlink frequency and / or time domain synchronization. Synchronization signals include PSS (Primary Synchronization Signal) and SSS (Secondary Synchronization Signal).

[0186] An SS block (SS / PBCH block) is composed of at least one or all of PSS, SSS and PBCH.

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

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

[0189] PTRS can be a signal used at least for phase noise compensation. The mode of PTRS assumed by the terminal device can be given at least based on upper-layer parameters and / or DCI.

[0190] A DL PTRS can be associated with a DL DMRS group that includes at least one antenna port for one or more DL DMRS.

[0191] Downlink physical channels and downlink physical signals are also called downlink signals. Uplink physical channels and uplink physical signals are also called uplink signals. Downlink signals and uplink signals are collectively referred to as physical signals. Downlink signals and uplink signals are collectively referred to as signals. Downlink physical channels and uplink physical channels are collectively referred to as physical channels. Downlink physical signals and uplink physical signals are collectively referred to as physical signals.

[0192] BCH (Broadcast Channel), UL-SCH (Uplink-Shared Channel), and DL-SCH (Downlink-Shared Channel) are transport channels. Channels used in the Medium Access Control (MAC) layer are called transport channels. The unit of a transport channel used in the MAC layer is also called a transport block (TB) or MAC PDU. The MAC layer performs HARQ (Hybrid Automatic Repeat reQuest) control on a per-TB basis. A transport block is the unit of data delivered from the MAC layer to the physical layer. In the physical layer, transport blocks are mapped to codewords and modulated on a per-codeword basis.

[0193] Base station device 3 and terminal device 1 exchange (transmit and receive) signals at the higher layer. For example, base station device 3 and terminal device 1 can transmit and receive RRC signaling (RRC message, RRC information) at the Radio Resource Control (RRC) layer. Furthermore, base station device 3 and terminal device 1 can also transmit and receive MAC CE (Control Element) at the MAC layer. Here, RRC signaling and / or MAC CE are also referred to as higher layer signaling.

[0194] PUSCH and PDSCH can be used to transmit at least RRC signaling and / or MAC CE. Here, the RRC signaling transmitted by base station device 3 via PDSCH can be signaling common to multiple terminal devices 1 within the serving cell. Signaling common to multiple terminal devices 1 within the serving cell is also called common RRC signaling. RRC signaling transmitted from base station device 3 via PDSCH can also be signaling specific to a particular terminal device 1 (also called dedicated signaling or UE-specific signaling). Signaling specific to terminal device 1 is also called dedicated RRC signaling. Upper-layer parameters specific to the serving cell can be transmitted / received to multiple terminal devices 1 within the serving cell using common signaling or transmitted / received to a particular terminal device 1 using dedicated signaling. UE-specific upper-layer parameters can also be transmitted / received to a particular terminal device 1 using dedicated signaling.

[0195] BCCH (Broadcast Control Channel), CCCH (Common Control Channel), and DCCH (Dedicated Control Channel) are logical channels. For example, BCCH is a higher-layer channel used for transmitting / receiving MIBs. Furthermore, CCCH (Common Control Channel) is a higher-layer channel used for transmitting / receiving common information among multiple terminal devices 1. Here, CCCH can be used, for example, for terminal devices 1 that are not connected via RRC. Furthermore, DCCH (Dedicated Control Channel) is a higher-layer channel used at least for transmitting / receiving dedicated control information to / from terminal devices 1. Here, DCCH can be used, for example, for terminal devices 1 in an RRC connection.

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

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

[0198] NR-U (New Radio-Unlicensed) can be applied on a component carrier. NR-U can also be applied on a serving cell. Applying NR-U on a component carrier (or a serving cell) may include at least some or all of the following elements (framework, structure) from A1 to A6.

[0199] Element A1: Constitutes a second SS burst set in a certain component carrier (or a certain serving cell).

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

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

[0202] Element A4: Base station device 3 centrally transmits PDCCH in the common search area of ​​the second type 0 PDCCH of a certain component carrier (or a certain serving cell).

[0203] Element A5: Terminal device 1 centrally receives PDCCH in the common search area of ​​the second type 0 PDCCH of a certain component carrier (or a certain serving cell).

[0204] Element A6: The upper-level parameter associated with NR-U (e.g., a field included in the MIB) represents the first value (e.g., 1).

[0205] NR-U (New Radio-Unlicensed) may also not be applied in a specific component carrier. NR-U may also not be applied in a specific serving cell. Applying NR-U without a specific component carrier (or serving cell) may include at least some or all of the following elements (framework, structure): elements B1 through B6.

[0206] Element B1: Constitutes the first SS burst set in a certain component carrier (or a certain serving cell).

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

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

[0209] Element B4: Base station device 3 centrally transmits PDCCH in the common search area of ​​the first type 0 PDCCH of a certain component carrier (or a certain serving cell).

[0210] Element B5: Terminal device 1 centrally receives PDCCH in the common search area of ​​the first type 0 PDCCH of a certain component carrier (or a certain serving cell).

[0211] Element B6: The higher-level parameter associated with NR-U (e.g., a field included in the MIB) represents a value different from this first value (e.g., 0).

[0212] A component carrier can be designated as a licensed band. A serving cell can be designated as a licensed band. Here, designating a component carrier (or a serving cell) as a licensed band may include at least some or all of the following settings 1 to 3.

[0213] Setting 1: Provide upper-layer parameters for operation in the licensed band for a specific component carrier (or serving cell), or provide upper-layer parameters for operation in the unlicensed band without specifying a specific component carrier (or serving cell).

[0214] Setting 2: Specify a component carrier (or a serving cell) to operate in the licensed frequency band, or do not specify a component carrier (or a serving cell) to operate in the unlicensed frequency band.

[0215] Setting 3: A component carrier (or a serving cell) is included in the licensed frequency band, or a component carrier (or a serving cell) is not included in the unlicensed frequency band.

[0216] A licensed frequency band can be a frequency band in which a terminal device (expecting) to operate in the licensed frequency band requests authorization from a radio station. A licensed frequency band can also be a frequency band in which only terminal devices manufactured by an operator (business, enterprise, group, company) that holds authorization from a radio station are authorized to operate. An unlicensed frequency band can be a frequency band in which a channel access procedure is not requested before transmitting physical signals.

[0217] An unlicensed frequency band can be a frequency band in which a terminal device operating in that unlicensed frequency band does not (expect) to request authorization from a radio station. An unlicensed frequency band can also be a frequency band authorized for operation by terminal devices manufactured by some or all of the operators that hold radio station authorization and / or those that do not. An unlicensed frequency band can also be a frequency band in which a channel access process is requested before transmitting physical signals.

[0218] Whether to apply NR-U in a component carrier (or a serving cell) can be determined at least based on whether that component carrier (or serving cell) is designated as a band that can operate in unlicensed bands (e.g., a band that can only operate in unlicensed bands). For example, a list of bands designed for NR or NR carrier aggregation can be specified. For example, if a band is included in one or more bands in the list that can operate in unlicensed bands (e.g., a band that can only operate in unlicensed bands), NR-U can be applied in that band. Furthermore, if a band is not included in the list that is included in one or more bands that can operate in unlicensed bands (e.g., a band that can only operate in unlicensed bands), NR-U may not be applied in that band, and instead, regular NR (e.g., NR of version 15 or NR-U other than version 16) may be applied.

[0219] Whether to apply NR-U in a component carrier (or a serving cell) can be determined at least based on whether the component carrier (or the serving cell) is configured as a frequency band capable of operating NR-U (e.g., a frequency band that can only operate in NR-U). For example, it is possible that, for a given frequency band, if one or more frequency bands in the list are included in the frequency bands that can be used by NR-U (e.g., a frequency band that can only be used by NR-U), NR-U is applied to that frequency band without applying NR-U, if one or more frequency bands in the list are not included in the frequency bands that can be used by NR-U (e.g., a frequency band that can only be used by NR-U).

[0220] Whether to apply NR-U on a specific component carrier (or serving cell) can be determined based on information included in the MIB or system information. For example, the MIB (or system information) may include information indicating whether NR-U is applied; if this information indicates NR-U application, then NR-U is applied to the serving cell corresponding to that MIB (or system information). Alternatively, if this information does not indicate NR-U application, then normal NR, instead of NR-U, is applied to the serving cell corresponding to that MIB (or system information). Or, the information may indicate whether it can be used in unlicensed frequency bands.

[0221] A component carrier may be set to an unlicensed frequency band. A serving cell may be set to an unlicensed frequency band. Here, setting a component carrier (or a serving cell) to an unlicensed frequency band may include at least some or all of the following settings 4 to 6.

[0222] Setting 4: Provide upper-layer parameters for operation in the unlicensed frequency band for a specific component carrier (or serving cell).

[0223] Setting 5: Specify a component carrier (or a serving cell) to operate in the unlicensed frequency band.

[0224] Setting 6: A component carrier (or a serving cell) is included in the unlicensed frequency band.

[0225] The following explanation assumes that the component carrier is set in either a licensed frequency band or an unlicensed frequency band. It should be noted that "the component carrier is set in a licensed frequency band" can mean "the serving cell is set in a licensed frequency band", and "the component carrier is set in an unlicensed frequency band" can mean "the serving cell is set in an unlicensed frequency band".

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

[0227] For example, if a component carrier is set in a licensed frequency band, terminal device 1 may receive the first SS / PBCH block. Alternatively, if a component carrier is set in a licensed frequency band, terminal device 1 may receive the first PDCCH within a common search area for the first type 0 PDCCH. Alternatively, if a component carrier is set in a licensed frequency band, base station device 3 may transmit the first SS / PBCH block. Alternatively, if a component carrier is set in a licensed frequency band, base station device 3 may receive the first PDCCH within a common search area for the first type 0 PDCCH.

[0228] Alternatively, if a component carrier is set to an unlicensed frequency band, terminal device 1 may receive the second SS / PBCH block. Alternatively, if a component carrier is set to an unlicensed frequency band, terminal device 1 may receive the second PDCCH within a common search area for the second type 0PDCCH. Alternatively, if a component carrier is set to an unlicensed frequency band, base station device 3 may transmit the second SS / PBCH block. Alternatively, if a component carrier is set to an unlicensed frequency band, base station device 3 may receive the second PDCCH within a common search area for the second type 0PDCCH.

[0229] For example, terminal device 1 may receive the first SS / PBCH block when NR-U is not applied on a certain component carrier and that component carrier is set in a licensed frequency band. Alternatively, terminal device 1 may receive the first PDCCH in a first type 0PDCCH common search area when NR-U is not applied on a certain component carrier and that component carrier is set in a licensed frequency band. Alternatively, base station device 3 may transmit the first SS / PBCH block when NR-U is not applied on a certain component carrier and that component carrier is set in a licensed frequency band. Alternatively, base station device 3 may receive the first PDCCH in a first type 0PDCCH common search area when NR-U is not applied on a certain component carrier and that component carrier is set in a licensed frequency band.

[0230] For example, terminal device 1 may receive the second SS / PBCH block when NR-U is not applied to a certain component carrier and that component carrier is set in an unlicensed frequency band. Alternatively, terminal device 1 may receive the first PDCCH in a common search area of ​​the second type 0PDCCH when NR-U is not applied to a certain component carrier and that component carrier is set in an unlicensed frequency band. Alternatively, base station device 3 may transmit the second SS / PBCH block when NR-U is not applied to a certain component carrier and that component carrier is set in an unlicensed frequency band. Alternatively, base station device 3 may receive the first PDCCH in a common search area of ​​the second type 0PDCCH when NR-U is not applied to a certain component carrier and that component carrier is set in an unlicensed frequency band.

[0231] For example, if NR-U is applied to a component carrier and that component carrier is set in a licensed frequency band, terminal device 1 may receive a second SS / PBCH block. Alternatively, if NR-U is applied to a component carrier and that component carrier is set in a licensed frequency band, terminal device 1 may receive a first PDCCH within a second type 0PDCCH common search area. Alternatively, if NR-U is applied to a component carrier and that component carrier is set in a licensed frequency band, base station device 3 may transmit a second SS / PBCH block. Alternatively, if NR-U is applied to a component carrier and that component carrier is set in a licensed frequency band, base station device 3 may receive a first PDCCH within a second type 0PDCCH common search area.

[0232] For example, if NR-U is applied on a component carrier and that component carrier is set in an unlicensed frequency band, terminal device 1 may receive the second SS / PBCH block. Alternatively, if NR-U is applied on a component carrier and that component carrier is set in an unlicensed frequency band, terminal device 1 may receive the first PDCCH within a second type 0PDCCH common search area. Alternatively, if NR-U is applied on a component carrier and that component carrier is set in an unlicensed frequency band, base station device 3 may transmit the second SS / PBCH block. Alternatively, if NR-U is applied on a component carrier and that component carrier is set in an unlicensed frequency band, base station device 3 may receive the first PDCCH within a second type 0PDCCH common search area.

[0233] Hereinafter, an example of the configuration of a terminal device 1 according to one embodiment will be described.

[0234] Figure 4 This is a schematic block diagram illustrating the configuration of terminal device 1 according to one embodiment of this invention. Figure 4 As shown, the terminal device 1 is configured to include a wireless transceiver unit 10 and an upper-layer processing unit 14. The wireless transceiver unit 10 is configured to include at least a portion or all of an antenna unit 11, an RF (Radio Frequency) unit 12, and a baseband unit 13. The upper-layer processing unit 14 is configured to include at least a portion or all of a media access control layer processing unit 15 and a radio resource control layer processing unit 16. The wireless transceiver unit 10 is also referred to as a transmitting unit, a receiving unit, or a physical layer processing unit. The transmitting unit can transmit physical signals and / or physical channels. Physical signals may include uplink demodulation reference signals and / or probe reference signals. Physical channels may include PRACH, PUCCH, and / or PUSCH. The transmitting unit can transmit some or all of PRACH, PUCCH, and PUSCH. The receiving unit can receive physical signals and / or physical channels. Physical signals may include downlink demodulation reference signals, channel state information reference signals, and / or synchronization signals. Physical channels may include PBCH, PDCCH, and / or PDSCH. The receiving unit can receive some or all of PBCH, PDCCH and / or PDSCH.

[0235] The upper-layer processing unit 14 outputs uplink data (transmission blocks) generated through user operations to the wireless transceiver unit 10. The upper-layer processing unit 14 performs processing at the MAC layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and RRC layer.

[0236] The media access control layer processing unit 15 of the upper layer processing unit 14 performs MAC layer processing.

[0237] The Radio Resource Control (RRC) layer processing unit 16, included in the upper-layer processing unit 14, performs RRC layer processing. The RRC layer processing unit 16 manages various setting information / parameters for the device itself. The RRC layer processing unit 16 sets various setting information / parameters based on signals received from the upper layer from the base station device 3. That is, the RRC layer processing unit 16 sets various setting information / parameters based on information representing various setting information / parameters received from the base station device 3. It should be noted that this setting information may include information related to the processing or setting of the physical channel or physical signal (i.e., the physical layer), MAC layer, PDCP layer, RLC layer, and RRC layer. The parameter may be an upper-layer parameter.

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

[0239] The RF unit 12 converts the signal received by the antenna unit 11 into a baseband signal through quadrature demodulation (down-conversion), removing unwanted frequency components. The RF unit 12 then outputs the processed analog signal to the baseband unit.

[0240] The baseband unit 13 converts the analog signal input from the RF unit 12 into a digital signal. The baseband unit 13 removes the part equivalent to the CP (Cyclic Prefix) from the converted digital signal, performs a Fast Fourier Transform (FFT) on the signal after removing the CP, and extracts the signal in the frequency domain.

[0241] The baseband unit 13 performs an inverse fast fourier transform (IFFT) on the data to generate OFDM symbols, appends a CP to the generated OFDM symbols to generate a digital baseband signal, and converts the digital baseband signal into an analog signal. The baseband unit 13 outputs the converted analog signal to the RF unit 12.

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

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

[0244] Figure 5 This is a schematic block diagram illustrating the configuration of a base station device 3 according to one embodiment of this invention. Figure 5 As shown, the base station device 3 is configured to include a wireless transceiver unit 30 and an upper-layer processing unit 34. The wireless transceiver unit 30 is configured to include an antenna unit 31, an RF unit 32, and a baseband unit 33. The upper-layer processing unit 34 is configured to include a media access control layer processing unit 35 and a radio resource control layer processing unit 36. The wireless transceiver unit 30 is also referred to as a transmitting unit, a receiving unit, or a physical layer processing unit. The receiving unit can receive physical signals and / or physical channels. Physical signals may include uplink demodulation reference signals and / or sounding reference signals. Physical channels may include PRACH, PUCCH, and / or PUSCH. The transmitting unit can receive some or all of PRACH, PUCCH, and PUSCH. The transmitting unit can transmit physical signals and / or physical channels. Physical signals may include downlink demodulation reference signals, channel state information reference signals, and / or synchronization signals. Physical channels may include PBCH, PDCCH, and / or PDSCH. The transmitting unit can transmit some or all of PBCH, PDCCH, and / or PDSCH.

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

[0246] The media access control layer processing unit 35 of the upper layer processing unit 34 performs MAC layer processing.

[0247] The Radio Resource Control (RRC) layer processing unit 36, included in the upper-layer processing unit 34, performs RRC layer processing. The RRC layer processing unit 36 ​​generates or obtains downlink data (transmission blocks), system information, RRC messages, MAC CE, etc., configured in the PDSCH from the upper-level node, and outputs them to the radio transceiver unit 30. Furthermore, the RRC layer processing unit 36 ​​manages various setting information / parameters for each terminal device 1. The RRC layer processing unit 36 ​​can set various setting information / parameters for each terminal device 1 via signals from the upper layer. That is, the RRC layer processing unit 36 ​​transmits / broadcasts information representing various setting information / parameters. It should be noted that this setting information may include information related to the processing or setting of the physical channel or physical signal (i.e., the physical layer), MAC layer, PDCP layer, RLC layer, and RRC layer. This parameter may be an upper-layer parameter.

[0248] Since the function of the wireless transceiver unit 30 is the same as that of the wireless transceiver unit 10, the description is omitted.

[0249] The components of terminal device 1 marked with reference numerals 10 to 16 can also be configured as circuits. The components of base station device 3 marked with reference numerals 30 to 36 can also be configured as circuits.

[0250] Terminal device 1 can perform carrier sense before transmitting a physical signal. Similarly, base station device 3 can perform carrier sense before transmitting a physical signal. Carrier sense can be performed as energy detection in a radio channel. Whether or not a physical signal can be transmitted can be determined based on the carrier sense performed before transmission. For example, if the energy detected by carrier sense before transmission is greater than a predetermined threshold, it can be determined that transmission through the physical channel is either not possible or impossible. Conversely, if the energy detected by carrier sense before transmission is less than a predetermined threshold, it can be determined that transmission through the physical channel is possible or possible. Furthermore, if the energy detected by carrier sense before transmission is equal to a predetermined threshold, transmission through the physical channel can be performed or not. In other words, if the energy detected by carrier sense before transmission is equal to a predetermined threshold, it can be determined that transmission is either impossible or possible.

[0251] The process of determining whether a physical channel can be transmitted based on carrier sensing is also called LBT (Listen Before Talk). A condition where LBT determines that a physical signal cannot be transmitted is also called a busy state. For example, a busy state could be a state where the energy detected by carrier sensing is greater than a specified threshold. Conversely, a condition where LBT determines that a physical signal can be transmitted is also called an idle state. For example, an idle state could be a state where the energy detected by carrier sensing is less than a specified threshold. A condition where LBT determines that a physical signal cannot be transmitted is also called an LBT failure.

[0252] The value of the continuous channel occupancy time (COT) can be predetermined by each country or by each frequency band. Base station device 3 can notify terminal device 1 of the COT. Terminal device 1 can identify the length of the COT and determine the timing of its end. For example, the maximum value of COT can be any one of 2ms, 3ms, 6ms, 8ms, or 10ms.

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

[0254] HARQ-ACK is also known 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.

[0255] Alternatively, the semi-statically scheduled (SPS) PDSCH can be configured by upper-layer parameters in each BWP of a serving cell. Activation or disabling of the SPS PDSCH can be performed on a per-serving-cell basis. Activation or disabling of the SPS PDSCH can also be performed independently between serving cells. The SPS (Semi-Persistent Scheduling) PDSCH can be a PDSCH semi-statically scheduled by terminal device 1.

[0256] In the downlink SPS PDSCH, the downlink assignment (DL assignment) can be given by the PDCCH and stored based on the L1 signaling indicating the SPS is active. In the downlink SPS PDSCH, the downlink assignment (DL assignment) can be given by the PDCCH and initialized (cleared) based on the L1 signaling indicating the SPS is disabled.

[0257] When constructing an SPS PDSCH, the upper layer (RRC) can configure some or all of the parameters cs-RNTI, nrofHARQ-Processes, and periodicity. Here, cs-RNTI can be the value of the RNTI used for activating, disabling, or retransmitting the SPS PDSCH. Furthermore, nrofHARQ-Processes can be the number of HARQ processes constructed for the SPS PDSCH. Additionally, periodicity can be the period of the DL assignment constructed for the SPS PDSCH.

[0258] When the SPS PDSCH is released or disabled by the upper layer, some or all of its configurations can be released. When the SPS PDSCH is released or disabled by the upper layer, some or all of its configurations can be initialized.

[0259] After constructing the DL assignment for SPS PDSCH, the MAC entity can consider the time slot n shown in Equation 1. DAslot The Nth occurrence in sequence DA DL assignments. Here, n DAslot It can be calculated by (numberOfSlotsPerFrame*SFN) DA +n DAslot )={(numberOfSlotsPerFrame*SFN start_time +slot start_timeThe expression `(1024 * numberOfSlotsPerFrame) + NDA * periodicity * numberOfSlotsPerFrame / 10` mod (1024 * numberOfSlotsPerFrame) is given. Here, `numberOfSlotsPerFrame` can be the number of consecutive slots included in a radio frame. `numberOfSlotsPerFrame` can also be the number of slots constituting a radio frame. `numberOfSlotsPerFrame` can be 10, 20, 40, 80, or 160. Furthermore, SFN... DA This can be a radio frame number that includes the nDA slot. SFN start_time This can be the radio frame number of the slot in which the DL assignment is initialized (activated) or re-initialized (reactivated), and then the SPS PDSCH is transmitted for the first time. start_time This can be used to initialize (activate) or reinitialize (reactivate) the DL assignment, and then send the slot number of the SPS PDSCH for the first time. The periodicity can be given by the upper layer parameters. The periodicity can be 10, 20, 32, 40, 64, 80, 128, 160, 320, or 640.

[0260] The HARQ process used for SPS PDSCH can be configured with one or more HARQ processes via the upper-level parameter `nrofHARQ-Processes`. The HARQ process ID included in the HARQ process used for SPS PDSCH can be shared with the HARQ process ID included in the DCI format for PDSCH scheduled via DL authorization. Alternatively, the HARQ process ID included in the HARQ process used for SPS PDSCH can be different from the HARQ process ID included in the DCI format for PDSCH scheduled via DL authorization.

[0261] Terminal device 1 can use PUCCH to report (send) HARQ-ACK information corresponding to SPS PDSCH to base station device 3. This PUCCH can be composed of PUCCH format 0. Alternatively, this PUCCH can be composed of PUCCH format 1. This PUCCH can also be composed of PUCCH format 0 for NR-U. This PUCCH can also be composed of PUCCH format 1 for NR-U.

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

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

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

[0265] exist Figure 6 In this context, SPS PDSCH 604 and SPS PDSCH 606 ​​can be PDSCHs without accompanying PDCCH scheduling instructions. Terminal device 1 can determine the existence of a PUCCH slot for transmitting HARQ-ACK information corresponding to SPS PDSCH 604 based on the K1 value included in the DCI format of the SPS PDSCH included in the activated PDCCH 601. For example, in... Figure 6 Since K1 is 1, terminal device 1 can use the time slot when it receives SPS PDSCH604 as a reference, and then proceed one time slot later, i.e., Slot#m+p. x +1 uses PUCCH605 to send HARQ-ACK information corresponding to SPS PDSCH604. Furthermore, terminal device 1 can determine the existence of a PUCCH slot for sending HARQ-ACK information corresponding to SPS PDSCH606 based on the value of K1 included in the DCI format of the SPS PDSCH included in the activated PDCCH601. For example, in Figure 6 Since K1 is 1, terminal device 1 can use the time slot when it receives SPS PDSCH606 as a reference, and then, after one time slot, i.e., Slot#m+jp... x +1 uses PUCCH607 to send the HARQ-ACK information corresponding to SPS PDSCH606. Here, j can be an integer greater than 1.

[0266] exist Figure 6 In this context, PDCCH 608 can be a PDCCH in a DCI format that includes disabling the SPS PDSCH. Terminal device 1 can generate HARQ-ACK information corresponding to whether the SPS PDSCH was successfully disabled via PDCCH 608. That is, if the SPS PDSCH is successfully disabled via PDCCH 608, terminal device 1 can generate an ACK. If disabling the SPS PDSCH via PDCCH 608 fails, terminal device 1 can generate a NACK. Terminal device 1 can determine the HARQ-ACK information corresponding to the disabling of the SPS PDSCH based on the value of K1 included in the DCI format of the SPS PDSCH included in the activated PDCCH 601. For example, in... Figure 6 In the PDCCH608, the K1 in the DCI format is 1. Therefore, terminal device 1 can use the time slot of receiving PDCCH608 as a reference, and then, after one time slot, i.e., Slot#m+jp... x +3 uses PUCCH609 to send HARQ-ACK information corresponding to the disablement of SPS PDSCH.

[0267] Terminal device 1 can use the HARQ-ACK codebook to report HARQ-ACK information corresponding to the SPS PDSCH release to base station device 3. Terminal device 1 can also use the HARQ-ACK codebook to report HARQ-ACK information corresponding to the time slot indicated by the value of the PDSCH-to-HARQ_feedback timing indicator field included in DCI format 1_0 or DCI format 1_1 corresponding to the SPS PDSCH release to base station device 3.

[0268] SPS PDSCH release can be performed using the DCI format included in the PDCCH.

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

[0270] If downlink data is successfully decoded, an ACK can be generated for that downlink data. If downlink data is not successfully decoded, a NACK can be generated for that downlink data. A HARQ-ACK may include at least one HARQ-ACK bit corresponding to one transport block. The HARQ-ACK bit may represent an ACK (acknowledgment) or NACK (negative-ACK) corresponding to one or more transport blocks. A HARQ-ACK may include at least a HARQ-ACK codebook containing one or more HARQ-ACK bits. The correspondence between HARQ-ACK bits and one or more transport blocks may be that the HARQ-ACK bits correspond to the PDSCH containing those one or more transport blocks.

[0271] The HARQ control corresponding to a transport block can be called a HARQ process. A HARQ process identifier can be given for each HARQ process. The DCI format can include a field representing the HARQ process identifier. The HARQ process identifier is also called the HARQ process ID.

[0272] The New Data Indicator (NDI) can be represented in DCI format per HARQ process. For example, the DCI format (DL assignment) including PDSCH scheduling information can include an NDI field. The NDI field can be 1 bit. Terminal device 1 can store the NDI value per HARQ process. Base station device 3 can store the NDI value for each terminal device 1 per HARQ process. Terminal device 1 can update the stored NDI value using the detected DCI format NDI field. Base station device 3 can send the updated NDI value or the unupdated NDI value as the DCI format NDI field to terminal device 1. Terminal device 1 can update the stored NDI value using the detected DCI format NDI field for the HARQ process corresponding to the value of the detected DCI format HARQ process identifier field.

[0273] Terminal device 1 can determine whether a received transport block is a new transmission or a retransmission based on the value of the NDI field in the DCI format (DL assignment). When comparing a transport block from a certain HARQ process with previously received NDI values, if the detected value of the NDI field in the DCI format is flipped, terminal device 1 can determine that the transport block is a new transmission. In the case of a newly transmitted transport block being sent in a certain HARQ process, the base station device can flip the stored NDI value for that HARQ process and send the flipped NDI to terminal device 1. In the case of a retransmitted transport block being sent in a certain HARQ process, the base station device 3 can also choose not to flip the stored NDI value for that HARQ process and send the unflipped NDI to terminal device 1. When comparing a transport block from a certain HARQ process with previously received NDI values, if the detected value of the NDI field in the DCI format is not flipped (is the same), terminal device 1 can determine that the received transport block is a retransmission. It should be noted that, here, flipping means switching to a different value.

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

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

[0276] `dl-DataToUL-ACK` represents a list of timings for HARQ-ACKs against the PDSCH. Timing refers to the number of time slots between the time slot in which the PDSCH is received (or the time slot including the last OFDM symbol mapping the PDSCH) and the time slot in which the HARQ-ACK for the received PDSCH is sent. For example, `dl-DataToUL-ACK` can be a list of 1, 2, 3, 4, 5, 6, 7, or 8 timings. When `dl-DataToUL-ACK` is a list of 1 timing, the HARQ indicator field is 0 bits. When `dl-DataToUL-ACK` is a list of 2 timings, the HARQ indicator field is 1 bit. When `dl-DataToUL-ACK` is a list of 3 or 4 timings, the HARQ indicator field is 2 bits. When `dl-DataToUL-ACK` is a list of 5, 6, 7, or 8 timings, the HARQ indicator field is 3 bits. `dl-DataToUL-ACK` is n... K1 In the case of a list of timed events, the HARQ indicator field can be ceil(log2(n K1 )). Here ceil(X) A ) is the output of the value X A The function is an integer function that rounds down to the nearest integer. For example, ceil(2.3) can be 3. Furthermore, dl-DataToUL-ACK consists of a list of timing values ​​in the range 0 to 31. For example, dl-DataToUL-ACK consists of a list of timing values ​​in the range 0 to 63.

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

[0278] Terminal device 1 can set the size of the HARQ-ACK codebook according to the size of dl-DataToUL-ACK. For example, if dl-DataToUL-ACK consists of 8 elements, the size of the HARQ-ACK codebook can be 8. For example, if dl-DataToUL-ACK consists of 2 elements, the size of the HARQ-ACK codebook can be 2. The individual HARQ-ACK information constituting the HARQ-ACK codebook can be the HARQ-ACK information received by the PDSCH for each time slot of dl-DataToUL-ACK. This type of HARQ-ACK codebook is also called a semi-static HARQ-ACK codebook.

[0279] Here's an example illustrating the setting of the HARQ indicator field. For instance, dl-DataToUL-ACK consists of a list of eight timings: 0, 7, 15, 23, 31, 39, 47, and 55. The HARQ indicator field consists of 3 bits. The HARQ indicator field "000" corresponds to the first 0 in the dl-DataToUL-ACK list. That is, HARQ indicator field "000" corresponds to the value 0 represented by index 1 in dl-DataToUL-ACK. The HARQ indicator field "001" corresponds to the second 7 in the dl-DataToUL-ACK list. The HARQ indicator field "010" corresponds to the third 15 in the dl-DataToUL-ACK list. The HARQ indicator field "011" corresponds to the fourth 23 in the dl-DataToUL-ACK list. The HARQ indication field "100" corresponds to the fifth '31' in the dl-DataToUL-ACK list. The HARQ indication field "101" corresponds to the sixth '39' in the dl-DataToUL-ACK list. The HARQ indication field "110" corresponds to the seventh '47' in the dl-DataToUL-ACK list. The HARQ indication field "111" corresponds to the eighth '55' in the dl-DataToUL-ACK list. When the received HARQ indication field is "000", terminal device 1 can send the corresponding HARQ-ACK from the received PDSCH time slot to the 0th time slot. When the received HARQ indication field is "001", terminal device 1 can send the corresponding HARQ-ACK from the received PDSCH time slot to the 7th time slot. If the received HARQ indication field indicates "010", terminal device 1 can send the corresponding HARQ-ACK from the time slot of the received PDSCH to the 15th time slot. If the received HARQ indication field indicates "011", terminal device 1 can send the corresponding HARQ-ACK from the time slot of the received PDSCH to the 23rd time slot. If the received HARQ indication field indicates "100", terminal device 1 can send the corresponding HARQ-ACK from the time slot of the received PDSCH to the 31st time slot. If the received HARQ indication field indicates "101", terminal device 1 can send the corresponding HARQ-ACK from the time slot of the received PDSCH to the 39th time slot.If the received HARQ indication field indicates "110", terminal device 1 can send the corresponding HARQ-ACK from the time slot of the received PDSCH to the 47th time slot. If the received HARQ indication field indicates "111", terminal device 1 can send the corresponding HARQ-ACK from the time slot of the received PDSCH to the 55th time slot.

[0280] Given the upper-layer parameter pdsch-AggregationFactor for terminal device 1, N PDSCH repeat This can be the value of pdsch-AggregationFactor. Without specifying the upper-level parameter pdsch-AggregationFactor for terminal device 1, N... PDSCH repeat It can be 1. Terminal device 1 can use PUCCH transmission and / or PUSCH transmission in time slot n+k to report HARQ-ACK information for PDSCH reception from time slot n-NPDSCHrepeat+1 to time slot n. Here, k can be the number of time slots indicated by the HARQ indication field included in the DCI format corresponding to the PDSCH reception. Furthermore, if the DCI format does not include the HARQ indication field, k can be given by the upper-layer parameter dl-DataToUL-ACK.

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

[0282] Terminal device 1 can determine a set of multiple opportunities for receiving one or more candidate PDSCHs for sending corresponding HARQ-ACK information through the PUCCH of a certain time slot. Terminal device 1 can determine multiple time slots of time slot timing K1 included in dl-DataToUL-ACK as multiple opportunities for receiving candidate PDSCHs. K1 can be a set of k. For example, when dl-DataToUL-ACK is (1, 2, 3, 4, 5, 6, 7, 8), HARQ-ACK information for receiving PDSCHs in time slots n-1, n-2, n-3, n-4, n-5, n-6, n-7, and n-8 can be sent through the PUCCH of time slot n. If the terminal device 1 actually receives the PDSCH in the time slot corresponding to the candidate PDSCH reception, it can set the ACK or NACK to HARQ-ACK information based on the transport blocks included in the PDSCH. If the PDSCH is not received in the time slot corresponding to the candidate PDSCH reception, it can set the NACK to HARQ-ACK information.

[0283] The HARQ indicator field included in the DCI format received via PDCCH in time slot n-1 can represent 1. The HARQ indicator field included in the DCI format received via PDCCH in time slot n-2 can represent 2. The HARQ indicator field included in the DCI format received via PDCCH in time slot n-3 can represent 3. The HARQ indicator field included in the DCI format received via PDCCH in time slot n-4 can represent 4. The HARQ indicator field included in the DCI format received via PDCCH in time slot n-5 can represent 5. The HARQ indicator field included in the DCI format received via PDCCH in time slot n-6 can represent 6. The HARQ indicator field included in the DCI format received via PDCCH in time slot n-7 can represent 7. The HARQ indicator field included in the DCI format received via PDCCH in time slot n-8 can represent 8.

[0284] Terminal device 1 can determine the time slot in which the PDCCH is received, the time slot in which HARQ-ACK information is sent based on the value of the HARQ indicator field included in the received DCI format, and the set of time slots in which multiple candidate PDSCHs corresponding to the HARQ-ACK information are received. For example, if dl-DataToUL-ACK is (1, 2, 3, 4, 5, 6, 7, 8), and terminal device 1 receives the PDSCH in time slot m, scheduling the HARQ indicator field included in the DCI format of the PDCCH to represent 4. Terminal device 1 can determine that HARQ-ACK information should be sent in time slot (m+4). Terminal device 1 can also determine that the other HARQ-ACK information sent in time slot (m+4) is the HARQ-ACK information received by PDSCH for time slot (m+(1-4)), the HARQ-ACK information received by PDSCH for time slot (m+(2-4)), the HARQ-ACK information received by PDSCH for time slot (m+(3-4)), the HARQ-ACK information received by PDSCH for time slot (m+(5-4)), the HARQ-ACK information received by PDSCH for time slot (m+(6-4)), the HARQ-ACK information received by PDSCH for time slot (m+(7-4)), and the HARQ-ACK information received by PDSCH for time slot (m+(8-4)).

[0285] The dl-DataToUL-ACK, used as the timing for HARQ-ACK, can not only constitute a value indicating the number of time slots, but also a value (information) indicating that HARQ-ACK is being held. Upon receiving a HARQ indication field via PDCCH indicating a value for holding HARQ-ACK, terminal device 1 can hold the HARQ-ACK (HARQ-ACK information) scheduled for PDSCH by that PDCCH and wait to send another HARQ-ACK (HARQ-ACK information).

[0286] In the above description, a semi-static HARQ-ACK codebook was explained as a type of HARQ-ACK codebook, but different types of HARQ-ACK codebooks can also be used. A type of HARQ-ACK codebook called a dynamic HARQ-ACK codebook will be explained.

[0287] The HARQ-ACK codebook corresponding to a given PDSCH group can be given based on one or more HARQ-ACK bits corresponding to any one or more transport blocks included in any one or more PDSCHs within that PDSCH group. The HARQ-ACK codebook can also be given based on at least the set of monitoring occasions for PDCCHs, a portion or all of the values ​​of the count DAI field. The HARQ-ACK codebook can also be given based on the value of the UL DAI field. The HARQ-ACK codebook can also be given based on the value of the DAI field. The HARQ-ACK codebook can also be given based on the value of the total DAI field.

[0288] The size of the dynamic HARQ-ACK codebook can be based on fields in the DCI format. The size of the HARQ-ACK codebook can also be set based on the value of the count (DAI) field in the last received DCI format. The count (DAI) field represents the cumulative number of PDSCHs or transport blocks scheduled up to the reception of the corresponding DCI format. Alternatively, the size of the dynamic HARQ-ACK codebook can be set based on the value of the total (DAI) field in the DCI format. The total (DAI) field represents the total number of PDSCHs or transport blocks scheduled up to the transmission of the HARQ-ACK codebook.

[0289] Terminal device 1 can determine, at least based on a portion or all of the value of timing K1 and slot offset K0, a set of monitoring opportunities for a PDCCH used to transmit HARQ-ACK information in a PUCCH configured in index n (slot #n). This set of monitoring opportunities for a PDCCH used to transmit HARQ-ACK information in a PUCCH configured in index n is also called a set of monitoring occasions for a PDCCH for slot #n. Here, this set of PDCCH monitoring opportunities may include M PDCCH monitoring opportunities. For example, slot offset K0 can be represented at least based on the value of the time domain resource allocation field included in the downlink DCI format. Slot offset K0 can be a value representing the number of slots (slot difference) from the slot containing the trailing OFDM symbol of a PDCCH configured with a DCI format to the OFDM symbol representing the starting point of a PDSCH scheduled by that DCI format, where the DCI format includes a time domain resource allocation field representing the slot offset K0.

[0290] If the DCI format detected in any of the search area sets corresponding to a certain PDCCH monitoring opportunity triggers the transmission of HARQ-ACK information in time slot n, the terminal device 1 may determine that PDCCH monitoring opportunity as a PDCCH monitoring opportunity for time slot n. Furthermore, if the DCI format detected in the search area set corresponding to a certain PDCCH monitoring opportunity does not trigger the transmission of HARQ-ACK information in time slot n, the terminal device 1 may not determine that PDCCH monitoring opportunity as a PDCCH monitoring opportunity for time slot n. Similarly, if no DCI format is detected in the search area set corresponding to a certain PDCCH monitoring opportunity, the terminal device 1 may not determine that PDCCH monitoring opportunity as a PDCCH monitoring opportunity for time slot n.

[0291] The PUCCH resources used to send HARQ-ACK information in time slot n can be determined at least based on the PUCCH resource indication field included in the last DCI format of one or more DCI formats detected in the set of monitoring opportunities for PDCCH in time slot n. Here, each of the one or more DCI formats triggers the transmission of HARQ-ACK information in time slot n. The last DCI format can be the DCI format corresponding to the last index (the largest index) of the DCI formats detected in the set of monitoring opportunities for PDCCH in time slot n. The indices of the DCI formats in the set of monitoring opportunities for PDCCH in time slot n are given in ascending order relative to the index of the serving cell that detected the DCI format, and then in ascending order relative to the index of the monitoring opportunity for the PDCCH that detected the DCI format. The indices of the PDCCH monitoring opportunities are given in ascending order on the time axis.

[0292] Counter DAI can represent the cumulative number of PDCCHs detected up to the monitoring opportunity of a specific PDCCH in a serving cell out of M PDCCH monitoring opportunities (or it can be a value at least associated with the cumulative number). Counter DAI can also be called C-DAI. The C-DAI corresponding to a PDSCH can be represented by the fields included in the DCI format used for scheduling that PDSCH. Total DAI can represent the cumulative number of PDCCHs detected up to monitoring opportunity m in M ​​PDCCH monitoring opportunities (or it can be a value at least associated with the cumulative number). Total DAI can also represent the cumulative number of PDSCHs detected up to monitoring opportunity m in M ​​PDCCH monitoring opportunities (or it can be a value at least associated with the cumulative number). Total DAI can also be called T-DAI (Total Downlink Assignment Index).

[0293] A semi-static HARQ-ACK codebook (Type 1 HARQ-ACK codebook) or a dynamic HARQ-ACK codebook (Type 2 HARQ-ACK codebook) can be a HARQ-ACK codebook sent based on DL assignment indications (triggers, requests). The DCI format including the HARQ indication field can be a DL assignment (Downlink assignment). DL assignment can be a DCI format used for PDSCH scheduling. DL assignment can be a DCI format used for PDSCH allocation. The HARQ-ACK codebook can be constructed based on dl-DataToUL-ACK and the HARQ indication field. The size of the semi-static HARQ-ACK codebook can be given based on the size included in dl-DataToUL-ACK. The timing of the time slots included in the semi-static or dynamic HARQ-ACK codebook can be given based on the value of the HARQ indication field and the time slot in which the DCI including the HARQ indication field is received.

[0294] A Type 3 HARQ-ACK codebook can be a HARQ-ACK codebook triggered by a DCI format with scheduling information (DL assignment) accompanying a PDSCH. A Type 3 HARQ-ACK codebook can also be a HARQ-ACK codebook triggered by a DCI format without scheduling information accompanying a PDSCH.

[0295] The Type 3 HARQ-ACK codebook can be sent via a DCI format indicated (triggered, requested) as a DL assignment. This DCI format may include a dedicated field indicating (triggered, requested) the transmission of the Type 3 HARQ-ACK codebook.

[0296] In the Type 3 HARQ-ACK codebook, the bits included in the DCI format that trigger the transmission of HARQ-ACK information included in part or all of the HARQ process are called HARQ trigger bits.

[0297] When terminal device 1 is given the upper-layer parameter pdsch-HARQ-ACK-OneShotFeedback-r16, and base station device 3 uses the HARQ trigger bit to indicate (request) the transmission (report) of type 3 HARQ-ACK codebook to terminal device 1, terminal device 1 can use the type 3 HARQ-ACK codebook to transmit (report) the HARQ-ACK information included in part or all of the HARQ processes constituted in terminal device 1 and the NDI value included in part or all of the HARQ processes constituted in terminal device 1 to base station device 3. When terminal device 1 is given the upper-layer parameter pdsch-HARQ-ACK-OneShotFeedback-r16, and base station device 3 uses the HARQ trigger bit to indicate (request) the transmission (report) of type 3 HARQ-ACK codebook to terminal device 1, terminal device 1 can, for a HARQ process, transmit (report) one HARQ-ACK information included in that HARQ process and the NDI value included in that HARQ process to base station device 3.

[0298] Without providing the upper-layer parameter pdsch-HARQ-ACK-OneShotFeedback-r16 to terminal device 1, and with base station device 3 using the HARQ trigger bit to indicate (request) the transmission (report) of type 3 HARQ-ACK codebook to terminal device 1, terminal device 1 can use the type 3 HARQ-ACK codebook to transmit (report) the HARQ-ACK information included in part or all of the HARQ processes constituted in terminal device 1 to base station device 3. Without providing the upper-layer parameter pdsch-HARQ-ACK-OneShotFeedback-r16 to terminal device 1, and with base station device 3 using the HARQ trigger bit to indicate (request) the transmission (report) of type 3 HARQ-ACK codebook to terminal device 1, terminal device 1 can transmit (report) one HARQ-ACK message included in a HARQ process to base station device 3 for a given HARQ process.

[0299] The upper-layer parameter pdsch-HARQ-ACK-OneShotFeedback-r16 given to terminal device 1 can be defined by setting the upper-layer parameter pdsch-HARQ-ACK-OneShotFeedback-r16 with an enabled value.

[0300] Type 3 HARQ-ACK codebooks may include HARQ-ACK information for some or all of the HARQ processes. For example, a HARQ process may be a HARQ process used for PDSCH. All HARQ processes may be all HARQ processes that can be used in at least one serving cell. The number of HARQ processes that can be used in one serving cell may be 16. The number of HARQ processes that can be used in five serving cells may be 80. Multiple HARQ processes may consist of multiple HARQ processes composed of RRC signaling. Multiple HARQ processes may be multiple HARQ processes indicated by downlink control information. Multiple HARQ processes may be multiple HARQ processes that are explicitly or implicitly indicated. The number of multiple HARQ processes may be 8. The number of multiple HARQ processes may be 10.

[0301] The Type 3 HARQ-ACK codebook can be the HARQ-ACK codebook that defines the HARQ process of the PDSCH corresponding to the HARQ-ACK included in the HARQ-ACK codebook. The time slot for receiving the PDSCH corresponding to the HARQ-ACK included in the Type 3 HARQ-ACK codebook is not predetermined and can be set by the scheduling of the base station device 3.

[0302] The Type 3 HARQ-ACK codebook may include the NDI value associated with the HARQ process corresponding to the HARQ-ACK reported via the Type 3 HARQ-ACK codebook. The Type 3 HARQ-ACK codebook may include the NDI value for each HARQ process, including HARQ-ACK information, reported via the Type 3 HARQ-ACK codebook. Terminal device 1 may determine (set) the HARQ-ACK information included in the Type 3 HARQ-ACK codebook based at least on a portion or all of the stored HARQ processes and NDI values. The HARQ-ACK may be HARQ-ACK information corresponding to a transport block for a particular HARQ process. The NDI value may represent the NDI for that particular HARQ process. Furthermore, the NDI value may identify the NDI corresponding to the HARQ-ACK information.

[0303] When the terminal device 1 is given the upper-layer parameter pdsch-HARQ-ACK-OneShotFeedback-r16, and the terminal device 1 receives a PDCCH in DCI format with the HARQ trigger bit set to 1, and the terminal device 1 has not constructed an SPS PDSCH, the terminal device 1 can use PUCCH to send the HARQ-ACK information included in the HARQ process constructed in the terminal device 1, the NDI value included in the HARQ process, and the HARQ-ACK information corresponding to the PDSCH scheduled by the PDCCH.

[0304] Without providing the upper-layer parameter pdsch-HARQ-ACK-OneShotFeedback-r16 to terminal device 1, and terminal device 1 receiving a DCI-formatted PDCCH with the HARQ trigger bit set to 1, and without constructing an SPS PDSCH in terminal device 1, terminal device 1 can use PUCCH to send the HARQ-ACK information included in the HARQ process constructed in terminal device 1, the NDI value included in the HARQ process, and the HARQ-ACK information corresponding to the PDSCH scheduled by the PDCCH.

[0305] The receiving of a PDCCH in DCI format by terminal device 1, including a HARQ trigger bit set to 1, can signify that base station device 3 has sent (reported) a type 3 HARQ-ACK codebook to terminal device 1. Setting the HARQ trigger bit to 1 can signify the sending (reporting) of a type 3 HARQ-ACK codebook.

[0306] When base station device 3 instructs terminal device 1 to receive multiple PDSCHs and uses a PUCCH in a certain time slot to send (report) HARQ-ACK information corresponding to the multiple PDSCHs, and there is no DCI format set as the trigger type 3 HARQ-ACK codebook among the multiple DCI formats included in the multiple PDCCHs scheduling the multiple PDSCHs, terminal device 1 can use the parameters related to the reporting of HARQ-ACK information included in the last received DCI format among the multiple PDCCHs scheduling the multiple PDSCHs to determine the PUCCH, generate a type 1 HARQ-ACK codebook or a type 2 HARQ-ACK codebook, and then use the determined PUCCH to send the type 1 HARQ-ACK codebook or the type 2 HARQ-ACK codebook. The parameters related to the reporting of HARQ-ACK information included in DCI formats other than the last received DCI format can be ignored. Here, the parameters related to the reporting of HARQ-ACK information can be parameters for determining PUCCH resources. The parameters related to the reporting of HARQ-ACK information can be PRI.

[0307] When base station device 3 instructs terminal device 1 to receive multiple PDSCHs and uses a PUCCH in a certain time slot to send (report) HARQ-ACK information corresponding to the multiple PDSCHs, and at least one of the multiple DCI formats included in the multiple PDCCHs scheduling the multiple PDSCHs is set to a trigger type 3 HARQ-ACK codebook, terminal device 1 can use the parameters related to HARQ-ACK information reporting included in the DCI format of trigger type 3 HARQ-ACK codebook to determine the PUCCH, and can ignore the parameters related to HARQ-ACK information reporting included in DCI formats other than the trigger type 3 HARQ-ACK codebook. Here, the parameters related to HARQ-ACK information reporting can be parameters for determining PUCCH resources. The parameters related to HARQ-ACK information reporting can be PRI.

[0308] When the base station device 3 instructs the terminal device 1 to receive multiple PDSCHs and uses the PUCCH in a certain time slot to send (report) HARQ-ACK information corresponding to the multiple PDSCHs, and there is no DCI format set as the trigger type 3 HARQ-ACK codebook among the multiple DCI formats included in the multiple PDCCHs scheduling the multiple PDSCHs, the terminal device 1 can generate a type 1 HARQ-ACK codebook or a type 2 HARQ-ACK codebook. Furthermore, the terminal device 1 can include part or all of the HARQ-ACK information reported in that certain time slot in the type 1 HARQ-ACK codebook or the type 2 HARQ-ACK codebook.

[0309] When the base station device 3 instructs the terminal device 1 to receive multiple PDSCHs and uses a PUCCH in a certain time slot to send (report) HARQ-ACK information corresponding to the multiple PDSCHs, and none of the DCI formats included in the multiple PDCCHs scheduling the multiple PDSCHs are set to trigger a type 3 HARQ-ACK codebook, the terminal device 1 can generate a codebook set by the upper-layer parameter pdsch-HARQ-ACK-codebook. Furthermore, the terminal device 1 can include part or all of the HARQ-ACK information reported in that time slot in the codebook set by the upper-layer parameter pdsch-HARQ-ACK-codebook. The codebook set by the upper-layer parameter pdsch-HARQ-ACK-codebook can be a type 1 HARQ-ACK codebook or a type 2 HARQ-ACK codebook.

[0310] When the base station device 3 instructs the terminal device 1 to receive multiple PDSCHs and uses the PUCCH in a certain time slot to send (report) HARQ-ACK information corresponding to the multiple PDSCHs, and at least one DCI format among the multiple DCI formats included in the multiple PDCCHs that schedule the multiple PDSCHs is set to trigger a type 3 HARQ-ACK codebook, the terminal device 1 can generate a type 3 HARQ-ACK codebook. Furthermore, the terminal device 1 can include part or all of the HARQ-ACK information reported in that time slot in the type 3 HARQ-ACK codebook.

[0311] Figure 6This diagram illustrates an example of the HARQ-ACK codebook selection method in this embodiment. The dl-DataToUL-ACK values ​​represented by 600 are 6, 5, and 4. It is assumed that PDCCH601 schedules PDSCH604, PDCCH602 schedules PDSCH605, and PDCCH603 schedules PDSCH606. Furthermore, in the DCI format included in PDCCH601, the value of the HARQ Timing field from PDSCH to HARQ feedback is 0; in the DCI format included in PDCCH702, the value of the HARQ Timing field from PDSCH to HARQ feedback is 1; and in the DCI format included in PDCCH703, the value of the HARQ Timing field from PDSCH to HARQ feedback is 2. HARQ timing can also be referred to as the PDSCH-to-HARQ_feedback timing indicator. The HARQ timing field can also be called the PDSCH-to-HARQ feedback timing indicator field. Terminal device 1 can determine the time slot for transmitting the PUCCH containing the HARQ-ACK information corresponding to the PDSCH based at least on the value of the HARQ Timing field from the PDSCH to the HARQ feedback. That is, the HARQ-ACK information corresponding to PDSCH 604, the HARQ-ACK information corresponding to PDSCH 605, and the HARQ-ACK information corresponding to PDSCH 606 ​​can be transmitted (reported) in time slot m+6.

[0312] If none of the DCI formats included in PDCCH601, PDCCH602, and PDCCH603 are set as trigger type 3 HARQ-ACK codebooks, terminal device 1 can generate a codebook set by the upper-layer parameter pdsch-HARQ-ACK-codebook. Here, terminal device 1 can use PUCCH607, determined based on parameters related to HARQ-ACK information reporting included in the DCI format included in PDCCH603, to transmit the generated codebook.

[0313] When any one of the DCI formats included in PDCCH601, PDCCH602, and PDCCH603 is set as a trigger type 3 HARQ-ACK codebook, terminal device 1 can generate a type 3 HARQ-ACK codebook. For example, if the HARQ trigger bit is set to 1 in the DCI format included in PDCCH602, and neither the DCI formats included in PDCCH601 nor PDCCH603 are set as trigger type 3 HARQ-ACK codebooks, terminal device 1 can use PUCCH607, determined based on parameters related to the reporting of HARQ-ACK information included in the DCI format included in PDCCH602, to send the generated type 3 HARQ-ACK codebook.

[0314] The presence of an SPS PDSCH in terminal device 1 can mean that the SPS PDSCH is activated in terminal device 1. Alternatively, the presence of an SPS PDSCH in terminal device 1 can mean that the SPS PDSCH is provided to terminal device 1.

[0315] The absence of an SPS PDSCH in terminal device 1 can be due to the SPS PDSCH being disabled in terminal device 1. Alternatively, the absence of an SPS PDSCH in terminal device 1 can also be due to the SPS PDSCH not being provided to terminal device 1.

[0316] Receiving SPS PDSCH in terminal device 1 can mean that SPS PDSCH is constructed in terminal device 1.

[0317] Figure 7This diagram illustrates an example of a type 3 HARQ-ACK codebook in the case where an SPS PDSCH is not constituted in this embodiment. The dl-DataToUL-ACK represented by 700 is 6, 5, or 4. It is assumed that PDCCH701 schedules PDSCH704, PDCCH702 schedules PDSCH705, and PDCCH703 schedules PDSCH706. In the DCI format included in PDCCH701, the value of the timing indication field (HARQ Timing) from PDSCH to HARQ feedback is 0, the HARQ process ID is 1, the NDI is 1, and the HARQ trigger bit is 0. In the DCI format included in PDCCH702, the value of the timing indication field (HARQ Timing) from PDSCH to HARQ feedback is 1, the HARQ process ID is 2, the NDI is 1, and the HARQ trigger bit is 0. In the DCI format included in PDCCH703, the value of the HARQ Timing field from PDSCH to HARQ feedback is 2, the HARQ process ID is 3, the NDI is 0, and the HARQ trigger bit is 1. HARQ timing can also be called the PDSCH-to-HARQ feedback timing indicator. The HARQ timing field can also be called the PDSCH-to-HARQ feedback timing indicator field.

[0318] Assuming the HARQ-ACK information corresponding to PDSCH 704 is NACK, and the HARQ-ACK information corresponding to PDSCH 705 is ACK, terminal device 1 can determine the time slot for transmitting the PUCCH containing the HARQ-ACK information corresponding to PDSCH 704 based at least on the value of the HARQ Timing field (DCI format) included in PDCCH 701. Furthermore, terminal device 1 can determine the time slot for transmitting the PUCCH containing the HARQ-ACK information corresponding to PDSCH 705 based on the value of the HARQ Timing field (DCI format) included in PDCCH 702. For example, in... Figure 7In PDCCH701, the value of the HARQ Timing field in DCI format, representing the timing indicator from PDSCH to HARQ feedback, is 0. Furthermore, one or more values ​​of dl-DataToUL-ACK in the upper-layer parameter 700, with index 0 corresponding to the HARQ timing value, become K1 (the number of time slots from PDSCH to HARQ feedback). Therefore, terminal device 1 can include the HARQ-ACK information corresponding to PDSCH704 in the PUCCH and transmit it after six time slots from PDSCH704, i.e., in the time slot #m+6. For example, in... Figure 7 In PDCCH702, the value of the HARQ Timing field in the DCI format from PDSCH to HARQ feedback is 1, and the value of index 1 of one or more values ​​of dl-DataToUL-ACK in the upper layer parameter 700, which corresponds to the value of HARQ timing, becomes the timing from PDSCH to HARQ feedback. Therefore, the terminal device 1 can include the HARQ-ACK information corresponding to PDSCH705 in the PUCCH and send it after 5 time slots from PDSCH705, i.e., in the time slot Slot#m+6. Furthermore, when the DCI format PRI included in PDCCH701 and the DCI format PRI included in PDCCH702 indicate PUCCH707, the terminal device 1 can include the HARQ-ACK information corresponding to PDSCH704 and the HARQ-ACK information corresponding to PDSCH705 in the type 1 HARQ-ACK codebook or the type 2 HARQ-ACK codebook, and use PUCCH707 to send the type 1 HARQ-ACK codebook or the type 2 HARQ-ACK codebook.

[0319] Assuming the HARQ-ACK information corresponding to PDSCH706 is NACK, terminal device 1 sends the HARQ-ACK information corresponding to PDSCH706 via PUCCH708 based on the value of the timing indication field for HARQ feedback in DCI format included in PDCCH703. Here, the HARQ trigger bit in DCI format included in PDCCH703 is 1. Therefore, when terminal device 1 is given pdsch-HARQ-ACK-OneShotFeedback-r16 as upper-layer parameter 710, terminal device 1 includes the HARQ-ACK information included in part or all of the HARQ processes constituted in terminal device 1 and the NDI value included in that part or all of the HARQ processes in a Type 3 HARQ-ACK codebook, and sends this Type 3 HARQ-ACK codebook via PUCCH708. That is, the HARQ trigger bit in the DCI format included in PDCCH703 is 1. Therefore, terminal device 1 includes the HARQ-ACK information included in HARQ process ID1, HARQ process ID2, and HARQ process ID3 constructed in terminal device 1, and the NDI value included in HARQ process ID1, HARQ process ID2, and HARQ process ID3 constructed in terminal device 1 in a type 3 HARQ-ACK codebook, and sends the type 3 HARQ-ACK codebook through PUCCH708. Furthermore, the HARQ trigger bit in the DCI format included in PDCCH703 is 1. Therefore, without providing the upper-layer parameter 710 with pdsch-HARQ-ACK-OneShotFeedback-r16 to terminal device 1, terminal device 1 includes some or all of the HARQ process information included in terminal device 1 in a type 3 HARQ-ACK codebook, and sends the type 3 HARQ-ACK codebook through PUCCH708. That is, the HARQ trigger bit in the DCI format included in PDCCH703 is 1. Therefore, the terminal device 1 includes the HARQ-ACK information included in the HARQ process ID1, HARQ process ID2 and HARQ process ID3 constituted in the terminal device 1 in the type 3 HARQ-ACK codebook, and sends the type 3 HARQ-ACK codebook through PDCCH708.

[0320] In the event that a first PUCCH including a type 3 HARQ-ACK codebook and a second PUCCH including a type 1 HARQ-ACK codebook or a type 2 HARQ-ACK codebook exist in a time slot, terminal device 1 may not send the second PUCCH, but only the first PUCCH. For example, in Figure 7In this process, terminal device 1 may also send PUCCH 708 which includes a type 3 HARQ-ACK codebook, but may not send PUCCH 707 which includes a type 1 HARQ-ACK codebook or a type 2 HARQ-ACK codebook.

[0321] The HARQ-ACK information and NDI value sent via PUCCH708 can also be configured at the beginning of the bit string (MSB: Most Significant Bit) based on the HARQ-ACK information and NDI values ​​included in the HARQ process with the smaller HARQ process ID. Similarly, the HARQ-ACK information and NDI value sent via PUCCH708 can also be configured at the beginning of the bit string (MSB: Most Significant Bit) based on the HARQ-ACK information and NDI values ​​included in the HARQ process with the larger HARQ process ID. Finally, the HARQ-ACK information and NDI value sent via PUCCH708 can also be configured at the beginning of the bit string (MSB: Most Significant Bit) based on the HARQ-ACK information and NDI values ​​included in the previously allocated HARQ process.

[0322] When the upper-layer parameter pdsch-HARQ-ACK-OneShotFeedback-r16 is given to terminal device 1, the size of the Type 3 HARQ-ACK codebook can be given based on at least one or all of the number of HARQ processes constructed in terminal device 1 and the PDCCH that disables SPPS PDSCH. For example, when the upper-layer parameter pdsch-HARQ-ACK-OneShotFeedback-r16 is given to terminal device 1 and the number of HARQ processes constructed in terminal device 1 is 16, and terminal device 1 does not receive a PDCCH that disables SPPS PDSCH, the size of the Type 3 HARQ-ACK codebook can be the sum of the number of HARQ-ACK messages included in the HARQ process (16 bits) and the number of NDIs that can be set for each HARQ process (32 bits) (48 bits). The number of NDIs that can be set for a HARQ process can be two. For example, when the terminal device 1 is given the upper-layer parameter pdsch-HARQ-ACK-OneShotFeedback-r16, and the number of HARQ processes constituted in the terminal device 1 is 16, and the terminal device 1 receives a PDCCH that disables SPS PDSCH, the size of the type 3 HARQ-ACK codebook can be the sum of the number of HARQ-ACK messages included in the HARQ process (16 bits), the number of NDIs that can be set for each HARQ process (32 bits), and the HARQ-ACK message corresponding to the disabling of SPS PDSCH (1 bit) (49 bits). For example, when terminal device 1 is given the upper-layer parameter pdsch-HARQ-ACK-OneShotFeedback-r16, and the number of HARQ processes in terminal device 1 is 16, and terminal device 1 receives a PDCCH that disables SPS PDSCH, the size of the type 3 HARQ-ACK codebook can be the sum of the number of HARQ-ACK messages included in the HARQ process (16 bits), the number of NDIs that can be set for each HARQ process (32 bits), the HARQ-ACK message corresponding to the disabling of SPS PDSCH (1 bit), and the specified value corresponding to the NDI (1 bit) (50 bits). Here, the 'specified value corresponding to the NDI' refers to a value (placeholder value) set in the NDI field included in the type 3 HARQ-ACK codebook, since there is no NDI value for SPS PDSCH and therefore no NDI function is performed. This specified value corresponding to the NDI can be 0 or 1.

[0323] When the upper-layer parameter pdsch-HARQ-ACK-OneShotFeedback-r16 is not provided to terminal device 1, the size of the type 3 HARQ-ACK codebook can be given based on at least one or all of the number of HARQ processes constructed in terminal device 1 and the PDCCH that disables SPS PDSCH. For example, when the upper-layer parameter pdsch-HARQ-ACK-OneShotFeedback-r16 is not provided to terminal device 1, and the number of HARQ processes constructed in terminal device 1 is 16, and terminal device 1 does not receive a PDCCH that disables SPS PDSCH, the size of the type 3 HARQ-ACK codebook can be the number of HARQ-ACK messages (16 bits) included in the HARQ process. For example, if the upper-layer parameter pdsch-HARQ-ACK-OneShotFeedback-r16 is not given to terminal device 1, and the number of HARQ processes constituted in terminal device 1 is 16, and terminal device 1 receives a PDCCH that disables SPS PDSCH, the size of the type 3 HARQ-ACK codebook can be the sum of the number of HARQ-ACK messages included in the HARQ process (16 bits) and the HARQ-ACK message that disables SPS PDSCH (1 bit) (17 bits).

[0324] The reporting (sending) of HARQ-ACK information included in one or more HARQ processes constituted in the trigger terminal device 1 can mean the reporting (sending) of the trigger type 3 HARQ-ACK codebook.

[0325] Figure 8This diagram illustrates an example of the reporting of HARQ-ACK information corresponding to the PDSCH and SPS PDSCH scheduled via DL authorization when an SPS PDSCH is configured in terminal device 1 in this embodiment. It is assumed that PDCCH801 schedules PDSCH804, PDCCH802 schedules PDSCH805, and PDCCH803 schedules PDSCH806. In the DCI format included in PDCCH801, the value of the timing indication field (HARQ Timing) from PDSCH to HARQ feedback is 0, the HARQ process ID is 1, the NDI is 1, and the HARQ trigger bit is 0. In the DCI format included in PDCCH802, the value of the timing indication field (HARQ Timing) from PDSCH to HARQ feedback is 1, the HARQ process ID is 3, the NDI is 1, and the HARQ trigger bit is 0. In the DCI format included in PDCCH803, the value of the HARQ Timing field from PDSCH to HARQ feedback is 3, the HARQ process ID is 4, the NDI is 0, and the HARQ trigger bit is 1. HARQ timing can also be referred to as the PDSCH-to-HARQ feedback timing indicator. The HARQ timing field can also be referred to as the PDSCH-to-HARQ feedback timing indicator field.

[0326] Assuming the HARQ-ACK information corresponding to PDSCH 804 is NACK, and the HARQ-ACK information corresponding to PDSCH 805 is ACK, the terminal device 1 can determine the time slot for transmitting the PUCCH containing the HARQ-ACK information corresponding to PDSCH 804 based at least on the value of the HARQ Timing field (DCI format) included in PDCCH 801. Furthermore, the terminal device 1 can determine the time slot for transmitting the PUCCH containing the HARQ-ACK information corresponding to PDSCH 805 based on the value of the HARQ Timing field (DCI format) included in PDCCH 802. Furthermore, terminal device 1 can determine the time slot for transmitting the PUCCH containing the HARQ-ACK information corresponding to the SPS PDSCH 809 based on the value of the HARQ Timing field, which is included in configuration 810 related to the reporting of HARQ-ACK information corresponding to the SPS PDSCH 809. For example, in Figure 8In PDCCH801, the value of the HARQ Timing field in DCI format, representing the timing indicator from PDSCH to HARQ feedback, is 0. Furthermore, one or more values ​​of dl-DataToUL-ACK in the upper-layer parameter 800, where the value corresponding to index 0 of the HARQ timing value is 7, become K1 (the number of time slots from PDSCH to HARQ feedback). Therefore, terminal device 1 can include the HARQ-ACK information corresponding to PDSCH804 in the PUCCH and transmit it after 7 time slots from PDSCH804, i.e., in the time slot #m+7. Additionally, for example, in... Figure 8 In PDCCH802, the value of the HARQTiming field, a timing indicator from PDSCH to HARQ feedback in DCI format, is 1. Furthermore, 6 of the values ​​of one or more of the dl-DataToUL-ACK values ​​in the upper-layer parameter 800, which serve as the index 1 corresponding to the HARQ timing value, becomes K1 (the number of time slots from PDSCH to HARQ feedback). Therefore, terminal device 1 can include the HARQ-ACK information corresponding to PDSCH805 in the PUCCH and transmit it after six time slots from PDSCH805, i.e., in the time slot #m+7. Additionally, for example, in... Figure 8 In the configuration 810 related to the reporting of HARQ-ACK information corresponding to SPS PDSCH809, the value of the timing indicator (HARQ Timing) field from PDSCH to HARQ feedback is 2, and the value of index 2 corresponding to the value of HARQ timing in one or more values ​​of dl-DataToUL-ACK of the upper layer parameter 800 becomes K1 (the number of time slots from PDSCH to HARQ feedback). Therefore, the terminal device 1 can include the HARQ-ACK information corresponding to SPS PDSCH805 in the PUCCH and send it after 5 time slots from SPS PDSCH809, i.e., in the time slot Slot#m+7. Furthermore, when the PRI in DCI format included in PDCCH801, the PRI in DCI format included in PDCCH802, and the PRI instruction PUCCH814 included in the configuration related to the reporting of HARQ-ACK information corresponding to SPS PDSCH809, the terminal device 1 includes the HARQ-ACK information corresponding to PDSCH804, the HARQ-ACK information corresponding to PDSCH805, and the HARQ-ACK information corresponding to SPS PDSCH809 in a type 1 HARQ-ACK codebook or a type 2 HARQ-ACK codebook, and sends the type 1 HARQ-ACK codebook or the type 2 HARQ-ACK codebook using PUCCH814.

[0327] In the event that a first PUCCH including a type 3 HARQ-ACK codebook and a second PUCCH including a type 1 HARQ-ACK codebook or a type 2 HARQ-ACK codebook exist in a time slot, terminal device 1 may not send the second PUCCH, but only the first PUCCH. For example, in Figure 8 In this process, terminal device 1 may also send PUCCH808 which includes a type 3 HARQ-ACK codebook, but may not send PUCCH814 which includes a type 1 HARQ-ACK codebook or a type 2 HARQ-ACK codebook.

[0328] When terminal device 1 is given pdsch-HARQ-ACK-OneShotFeedback-r16 as upper-layer parameter 813, and the HARQ trigger bit included in the DCI format included in PDCCH803 is 1, and the PRI included in the DCI format indicates PUCCH808, terminal device 1 can include the HARQ-ACK information included in part or all of the HARQ process constituted in terminal device 1 and the NDI value for the HARQ-ACK information in a type 3 HARQ-ACK codebook, and use PUCCH808 to send the type 3 HARQ-ACK codebook. Here, the NDI value corresponding to SPS PDSCH809 is not set; therefore, terminal device 1 can set a specified value in the field of the NDI value corresponding to SPS PDSCH809 in PUCCH808 and send PUCCH808. The specified value can be 0 or 1. Figure 8 In PUCCH 808, field 811 can be a field for HARQ-ACK information corresponding to one or more PDSCHs authorized by DL and for NDI for that HARQ-ACK information. Field 812 can be a field for HARQ-ACK information corresponding to SPS PDSCHs and for NDI for that HARQ-ACK information.

[0329] When the terminal device 1 is given the upper-layer parameter pdsch-HARQ-ACK-OneShotFeedback-r16, and the terminal device 1 has an SPS PDSCH, and the terminal device 1 receives the SPS PDSCH and the PDSCH authorized and scheduled by DL, and the HARQ trigger bit included in the DCI format is 1, the bit string mapped to the PUCCH of the triggered HARQ-ACK information and the NDI for the HARQ-ACK information can be configured in the order of {HARQ-ACK information, NDI}.

[0330] Figure 9This diagram illustrates an example of overlapping multiple PUCCHs in this embodiment. When two or more PUCCHs overlap, the terminal device 1 can include (multiplex) some or all of the UCIs included in the two or more overlapping PUCCHs into a new PUCCH. Furthermore, the two or more overlapping PUCCHs can be discarded. Here, "two or more overlapping PUCCHs" can mean overlapping two or more PUCCH resources. That is, when two or more PUCCH resources overlap, the terminal device 1 can include (multiplex) some or all of the UCIs included in the two or more overlapping PUCCH resources into a new PUCCH resource, and the two or more overlapping PUCCH resources can be discarded. For example, Figure 9 In Case 1, where PUCCH901 and PUCCH902 overlap in time slot m, terminal device 1 can multiplex the UCIs included in PUCCH901 and PUCCH902 to a new PUCCH other than the PUCCH itself. Alternatively, terminal device 1 can discard the overlapping PUCCH901 and PUCCH902.

[0331] If a first PUCCH containing a type 3 HARQ-ACK codebook and a second PUCCH containing a type 1 HARQ-ACK codebook or a type 2 HARQ-ACK codebook exist in a time slot, and the second PUCCH overlaps in the time domain with a third PUCCH containing UCI information other than HARQ-ACK information, the terminal device 1 may discard the second PUCCH. For example, in Figure 9 In Case 1, if PUCCH900 includes a Type 3 HARQ-ACK codebook, PUCCH901 includes a Type 1 HARQ-ACK codebook or a Type 2 HARQ-ACK codebook, and PUCCH902 includes a UCI other than HARQ-ACK information, the terminal device 1 may discard PUCCH901.

[0332] If a time slot contains a first PUCCH including a type 3 HARQ-ACK codebook and a second PUCCH including a type 1 HARQ-ACK codebook or a type 2 HARQ-ACK codebook, and the first PUCCH overlaps in the time domain with a third PUCCH including UCI information other than HARQ-ACK information, the terminal device 1 may discard the second PUCCH. For example, in Figure 9In Case 1, if PUCCH900 includes a Type 1 HARQ-ACK codebook or a Type 2 HARQ-ACK codebook, PUCCH901 includes a Type 3 HARQ-ACK codebook, and PUCCH902 includes UCI information other than HARQ-ACK information, the terminal device 1 may discard PUCCH900.

[0333] In a time slot, if a first PUCCH including a type 3 HARQ-ACK codebook and a second PUCCH including a type 1 HARQ-ACK codebook or a type 2 HARQ-ACK codebook exist, and the first PUCCH, the third PUCCH including UCI information other than HARQ-ACK information, and the second PUCCH including a type 1 HARQ-ACK codebook or a type 2 HARQ-ACK codebook overlap in the time domain, the terminal device 1 may discard the second PUCCH. For example, in Figure 9 In Case 2, if PUCCH903 includes a Type 1 HARQ-ACK codebook or a Type 2 HARQ-ACK codebook, PUCCH905 includes a Type 3 HARQ-ACK codebook, and PUCCH904 includes a UCI other than HARQ-ACK information, the terminal device 1 may discard PUCCH903.

[0334] For example, in Figure 9 In Case 2, if PUCCH904 includes a Type 1 HARQ-ACK codebook or a Type 2 HARQ-ACK codebook, PUCCH905 includes a Type 3 HARQ-ACK codebook, and PUCCH903 includes a UCI other than HARQ-ACK information, the terminal device 1 may discard PUCCH904.

[0335] For example, in Figure 9 In Case 2, if PUCCH905 includes a Type 1 HARQ-ACK codebook or a Type 2 HARQ-ACK codebook, PUCCH903 includes a Type 3 HARQ-ACK codebook, and PUCCH904 includes a UCI other than HARQ-ACK information, the terminal device 1 may discard PUCCH905.

[0336] In a time slot, if multiple PUCCHs including type 3 HARQ-ACK codebooks overlap in the time domain, terminal device 1 may disregard the PUCCHs including type 3 HARQ-ACK codebooks and instead perform overlap resolution processing on some or all of the PUCCHs excluding those including type 3 HARQ-ACK codebooks. If, as a result of this overlap resolution processing, one or more PUCCHs overlap with a PUCCH including type 3 HARQ-ACK codebooks that was not considered in the overlap resolution processing, terminal device 1 may discard the PUCCHs that overlapped with the PUCCHs including type 3 HARQ-ACK codebooks that were not considered in the overlap resolution processing. Furthermore, if one or more PUCCHs, which are part of the result of the overlap resolution process, exist in the same time slot as PUCCHs that include a type 3 HARQ-ACK codebook and were not considered in the overlap resolution process, and if one or more PUCCHs, which are part of the result of the overlap resolution process, include HARQ-ACK information other than the type 3 HARQ-ACK codebook, then the terminal device 1 may discard the PUCCHs that include HARQ-ACK information other than the type 3 HARQ-ACK codebook.

[0337] In a time slot, if a first PUCCH containing a type 3 HARQ-ACK codebook and a second PUCCH containing a type 1 HARQ-ACK codebook or a type 2 HARQ-ACK codebook exist, and the second PUCCH overlaps in the time domain with a third PUCCH containing UCI information other than HARQ-ACK information, the terminal device 1 can multiplex the second and third PUCCHs after the fourth PUCCH, discard the second, third, and fourth PUCCHs, and then transmit the first PUCCH. For example, in Figure 9 In Case 3, where PUCCH906 includes a Type 3 HARQ-ACK codebook, PUCCH907 includes a Type 1 HARQ-ACK codebook or a Type 2 HARQ-ACK codebook, and PUCCH908 includes a UCI other than HARQ-ACK information, the terminal device 1 can, after overlapping PUCCH907 and PUCCH908 in the time domain, multiplex the UCI included in PUCCH907 and the UCI included in PUCCH908 to PUCCH909, discard PUCCH907, PUCCH908 and PUCCH909, and send PUCCH906.

[0338] If a first PUCCH containing a type 3 HARQ-ACK codebook and a second PUCCH containing a type 1 HARQ-ACK codebook or a type 2 HARQ-ACK codebook exist in a time slot, and the first PUCCH overlaps in the time domain with a third PUCCH containing UCI information other than HARQ-ACK information, the terminal device 1 can multiplex the first PUCCH and the third PUCCH after the fourth PUCCH. Regardless of whether the fourth PUCCH overlaps with the second PUCCH, the second PUCCH is discarded and the fourth PUCCH is sent.

[0339] For example, in Figure 9 In Case 3, where PUCCH907 includes a Type 3 HARQ-ACK codebook, PUCCH906 includes a Type 1 HARQ-ACK codebook or a Type 2 HARQ-ACK codebook, and PUCCH908 includes a UCI other than HARQ-ACK information, the terminal device 1 can, after overlapping PUCCH907 and PUCCH908 in the time domain, multiplex the UCI included in PUCCH907 and the UCI included in PUCCH908 into PUCCH909, discard PUCCH906, PUCCH907, and PUCCH908, and send PUCCH909.

[0340] For example, in Figure 9 In Case 2, if PUCCH904 includes a Type 1 HARQ-ACK codebook or a Type 2 HARQ-ACK codebook, PUCCH905 includes a Type 3 HARQ-ACK codebook, and PUCCH903 includes UCI information other than HARQ-ACK information, then after PUCCH903 and PUCCH904 do not overlap, terminal device 1 may not perform overlap resolution processing on PUCCH903 and PUCCH904. Then, if PUCCH905, which includes a Type 3 HARQ-ACK codebook, overlaps with PUCCH903 and PUCCH904, terminal device 1 may discard PUCCH903 and PUCCH904.

[0341] When terminal device 1 transmits PUCCH using PUCCH power control adjustment state index l on the active uplink BWP b of carrier f in primary cell c, terminal device 1 can determine the PUCCH transmission power P in PUCCH transmission occasion i. PUCCH，b，f，c (i, q) u q dTerminal device 1 can calculate the transmission power P of the PUCCH based on formula 1. PUCCH , b，f，c (i, q) u q d Furthermore, P is set in Formula 1. real_PUCCH，b，f，c (i, q) u q d The transmission power P of the PUCCH is defined by formula 2. PUCCH，b，f，c (i, q) u q d 、l) can be a decibel unit (dBm).

[0342] [Formula 1]

[0343] P PUCCH，b，f，c (i, q) u q d ,l)=min{P CMAX，f，c (i), P real_PUC C H，b，f，c (i, q) u q d ,l)}

[0344] [Formula 2]

[0345]

[0346] Here, P real_PUCCH，b，f，c (i, q) u q d (l) can be a power value calculated (estimated) based on an actual transmission to the PUCCH. Furthermore, calculating (estimating) a power value based on an actual transmission to the PUCCH can also mean calculating (estimating) a power value based on actual transmissions within the PUCCH.

[0347] P CMAX，f，c (i) can be the maximum output power set by the carrier f of the serving cell c in the PUCCH transmission opportunity i for the terminal device 1. O_PUCCH，b，f，c (q u The component P can be given by the upper-level parameter p0-nominal. O_NOMINAL_PUCCH The sum (sum). μ is a parameter representing the subcarrier spacing. M RB，b，f，c PUCCH (i) can be the bandwidth of the PUCCH resources for PUCCH transmission opportunity i in the active uplink BWP b included in the carrier f of serving cell c. Furthermore, M RB，b，f，c PUCCH (i) can be represented by the number of resource blocks. PL b，f，c(q d In the active downlink BWP b of carrier f in primary cell c, terminal device 1 uses a reference signal to index q. d The measured (calculated) value of the downlink path loss. PL b，f，c (qd) can be in decibels (dB). Δ F_PUCCH (F) can be a value given by the upper-level parameter. In the case of PUCCH format 0, Δ F_PUCCH (F) can be given by the upper-level parameter deltaF-PUCCH-f0. In the case of PUCCH format 1, Δ F_PUCCH (F) can be given by the upper-level parameter deltaF-PUCCH-f1. In the case of PUCCH format 2, Δ F_PUCCH (F) can be given by the upper-level parameter deltaF-PUCCH-f2. In the case of PUCCH format 3, Δ F_PUCCH (F) can be given by the upper-level parameter deltaF-PUCCH-f3. In the case of PUCCH format 4, Δ F_PUCCH (F) can be given by the upper-level parameter deltaF-PUCCH-f4. TF，b，f，c (i) can be the transmit power control component of the PUCCH in the active uplink BWP of the primary cell c, which is the carrier f.

[0348] g b，f，c (i, l) can be the current PUCCH power control adjustment state in the PUCCH transmission opportunity i of the active uplink BWP of carrier f in primary cell c. b，f，c (i, l) can be given by Equation 3.

[0349] [Formula 3]

[0350]

[0351] Here, δ PUCCH，b，f，c (i, l) includes the DCI format 1_0 or DCI format 1_1 detected by terminal device 1 in the active uplink BWP of carrier f in primary cell c for PUCCH transmission opportunity i, referred to as TPC command. Furthermore, δ PUCCH，b，f，c (i, l) can also be jointly coded with other TPC commands in DCI format 2_2 scrambled by TPC-PUCCH-RNTI. That is, δ PUCCH，b，f，c (i, l) can represent g b，f，cThe accumulated value in (i, l). Furthermore, δ PUCCH，b，f，c (i, l) can be given based on the downlink grant for a cell received in a certain PUCCH transmission opportunity i and the values ​​set in the fields of the TPC command for the PUCCH included in DCI format 1_0 or DCI format 1_1 or DCI format 2_2 scrambled by TPC-PUCCH-RNTI for the PUCCH. C i It can be the set of PUCCH sending opportunities i. i0 can be a number greater than 0.

[0352] For example, the values ​​of the fields (2-bit information fields) for the TPC commands for PUCCH included in DCI format 1_0 or DCI format 1_1 for downlink authorization are mapped to the accumulated values ​​{-1, 0, 1, 3}. When the TPC command is 00, δ PUCCH，b，f，c (i, l) can be -1. When the TPC command is 01, δ PUCCH，b，f，c (i, l) can be 0. When the TPC command is 10, δ PUCCH，b，f，c (i, l) can be 1. When the TPC command is 11, δ PUCCH，b，f，c (i, l) can be 3. When the TPC command is 0, δ PUCCH，b，f，c (i, l) can be -1. When the TPC command is 1, δ PUCCH，b，f，c (i, l) can be 0. When the TPC command is 2, δ PUCCH，b，f，c (i, l) can be 1. When the TPC command is 3, δ PUCCH，b，f，c (i, l) can be 3.

[0353] When a PUCCH containing a type 3 HARQ-ACK codebook and a PUCCH containing a type 1 HARQ-ACK codebook or a type 2 HARQ-ACK codebook exist in the same time slot, the terminal device 1 can adjust the PUCCH power control adjustment state based on the current PUCCH power control adjustment state for the PUCCH containing a type 1 HARQ-ACK codebook or a type 2 HARQ-ACK codebook. b，f，c (i, l) determines the current PUCCH power control state for a PUCCH that includes a type 3 HARQ-ACK codebook. Terminal device 1 determines the current PUCCH power control state g based on the current PUCCH power control state g for a PUCCH that includes either a type 1 HARQ-ACK codebook or a type 2 HARQ-ACK codebook. b，f，c(i, l) can be used to determine the current PUCCH power control state g for a PUCCH that includes a type 3 HARQ-ACK codebook. b，f，c The determination of (i, l) takes into account the current PUCCH power control state g for PUCCHs including type 1 HARQ-ACK codebooks or type 2 HARQ-ACK codebooks. b，f，c (i, l).

[0354] When a PUCCH containing a type 3 HARQ-ACK codebook and a PUCCH containing a type 1 HARQ-ACK codebook or a type 2 HARQ-ACK codebook exist in the same time slot, the terminal device 1 may not base its power control on the current PUCCH power control state g for the PUCCH containing a type 1 HARQ-ACK codebook or a type 2 HARQ-ACK codebook. b，f，c (i, l), determine the current PUCCH power control state g for the PUCCH including the type 3 HARQ-ACK codebook. b，f，c (i, l). Terminal device 1 does not base its current PUCCH power control state g on the PUCCH including either type 1 HARQ-ACK codebook or type 2 HARQ-ACK codebook. b，f，c (i, l) can be the current PUCCH power control state g for a PUCCH including a type 3 HARQ-ACK codebook. b，f，c The determination of (i, l) does not consider the current PUCCH power control state g for PUCCHs including type 1 HARQ-ACK codebooks or type 2 HARQ-ACK codebooks. b，f，c (i, l).

[0355] When a PUCCH containing a type 3 HARQ-ACK codebook and a PUCCH containing a type 1 HARQ-ACK codebook or a type 2 HARQ-ACK codebook exist in the same time slot, the transmission power of the PUCCH containing the type 3 HARQ-ACK codebook can be determined based on the transmission power of the PUCCH containing the type 1 HARQ-ACK codebook or the type 2 HARQ-ACK codebook.

[0356] When a PUCCH containing a type 3 HARQ-ACK codebook and a PUCCH containing a type 1 HARQ-ACK codebook or a type 2 HARQ-ACK codebook exist in the same time slot, the transmission power of the PUCCH containing the type 3 HARQ-ACK codebook may not be determined based on the transmission power of the PUCCH containing the type 1 HARQ-ACK codebook or the type 2 HARQ-ACK codebook.

[0357] exist Figure 7In this example, it is assumed that PUCCH707 is used to transmit the HARQ-ACK information corresponding to PDSCH704 and the HARQ-ACK information corresponding to PDSCH705. Furthermore, it is assumed that PUCCH708 is used to transmit the HARQ-ACK information corresponding to PDSCH706. Additionally, it is assumed that the HARQ trigger bit is set to 1 in the DCI format included in PDCCH703, which schedules PDSCH706. It is assumed that the TPC commands in the DCI format included in PDCCH701 are 3, and the TPC commands in the DCI format included in PDCCH702 and PDCCH703 are 2. For example, in g... b，f，c When (0, l) is 0, terminal device 1 can adjust the current PUCCH power control adjustment state for PUCCH 707. b，f，c (i, l) is set to 3 + 1 = 4 dB (decibels). For example, in g b，f，c When (0, l) is 0, the terminal device 1 can set the current PUCCH power control state g for PUCCH708. b，f，c (i, l) is set to 3 + 1 + 1 = 5 dB (decibels). For example, in g b，f，c When (0, l) is 0, the terminal device 1 can set the current PUCCH power control state g for PUCCH708. b，f，c (i, l) is set to 1 dB (decibels).

[0358] If, based on the first time slot in which the first PDCCH is received, there are one or more PDCCHs received before the first time slot, and some or all of these one or more PDCCHs schedule one or more PDSCHs, and the HARQ-ACK information corresponding to these PDSCHs is transmitted via the first PUCCH in the second time slot, then terminal device 1 can determine one or all of the HARQ-ACK information included in the first PUCCH based at least on the PRI set in the DCI format included in the first PDCCH, and map this one or all of the HARQ-ACK information to the second PUCCH before transmission. Furthermore, terminal device 1 can discard the first PUCCH. Here, discarding the PUCCH means not transmitting it. Additionally, terminal device 1 can apply one or more TPC commands applied to the first PUCCH to the second PUCCH.

[0359] The transmission power of a PUCCH that includes a type 3 HARQ-ACK codebook can be determined in the time slot that includes the PUCCH based on the individual TPC commands included in one or more PDCCHs corresponding to one or more HARQ-ACK messages included in a PUCCH that includes a codebook other than the type 3 HARQ-ACK codebook (e.g., a type 1 HARQ-ACK codebook or a type 2 HARQ-ACK codebook).

[0360] Figure 10 This diagram illustrates an example of the application of TPC commands in this implementation. Figure 10 In this context, it is assumed that the HARQ-ACK information corresponding to PDSCH1004 is mapped to PUCCH1007 in time slot m+6 based on the HARQ Timing value set in the DCI format included in PDCCH1001 and the PRI set in the DCI format included in PDCCH1001. Terminal device 1 adjusts (determines) the transmission power of PUCCH1007 based on the TPC command set in the DCI format included in PDCCH1001. Assume that the HARQ-ACK information corresponding to PDSCH1005 is mapped to PUCCH1008 in time slot m+6 based on the HARQ timing value set in the DCI format included in PDCCH1002 and the PRI set in the DCI format included in PDCCH1002. Terminal device 1 can include the HARQ-ACK information included in PUCCH1007 corresponding to PDSCH1004 in PUCCH1008, at least based on the TPC command set in the DCI format included in PDCCH1001 and the TPC command set in the DCI format included in PDCCH1001, and discard PUCCH1007. Assume that the HARQ-ACK information corresponding to PDSCH1005 is mapped to PUCCH1008 in time slot m+6. The HARQ-ACK information corresponding to H1006 is mapped to PUCCH1009 in time slot m+6 based on the HARQ timing value set in the DCI format included in PDCCH1003 and the PRI set in the DCI format included in PDCCH1003, and the HARQ trigger bit is set to 1 in the DCI format included in PDCCH1003. Terminal device 1 may discard PUCCH1008 and the HARQ-ACK information included in PUCCH1008. Discarding HARQ-ACK information may also mean not sending HARQ-ACK information. In addition, terminal device 1 may include the type 3 HARQ-ACK codebook in PUCCH1009, determine the transmission power for PUCCH1009 based at least on some or all of PDCCH1001, PDCCH1002 and PDCCH1003, and send PUCCH1009.

[0361] A PUCCH transmission opportunity can be the actual opportunity (occasion) for terminal device 1 to transmit a PUCCH. Furthermore, a PUCCH transmission opportunity can be the timing at which terminal device 1 transmits a PUCCH, and a PUCCH discarded by terminal device 1 may not necessarily be a PUCCH transmission opportunity. PUCCH transmission opportunities i-i0 are PUCCH transmission opportunities that transmit a PUCCH before (prior to) PUCCH transmission opportunity i, and can also be the PUCCH transmission opportunity closest to PUCCH transmission opportunity i. That is to say, there may not be a PUCCH transmission opportunity between PUCCH transmission opportunities i-i0 and PUCCH transmission opportunity i.

[0362] When terminal device 1 receives a PDCCH in DCI format that includes a trigger type 3 HARQ-ACK codebook and a PDCCH that triggers a codebook other than type 3 HARQ-ACK (e.g., type 1 HARQ-ACK codebook or type 2 HARQ-ACK codebook) between PUCCH transmission opportunity i-i0 and PUCCH transmission opportunity i, terminal device 1 can control (determine) the transmission power of the PUCCH transmitted at PUCCH transmission opportunity i based on the TPC command included in the DCI format that triggers type 3 HARQ-ACK codebook.

[0363] When terminal device 1 receives a PDCCH in DCI format that includes a trigger type 3 HARQ-ACK codebook and a PDCCH that triggers a codebook other than type 3 HARQ-ACK codebook (e.g., type 1 HARQ-ACK codebook or type 2 HARQ-ACK codebook) between PDCCH transmission opportunity i-i0 and PDCCH transmission opportunity i, terminal device 1 may ignore the TPC command set in the DCI format included in the PDCCH that triggers a codebook other than type 3 HARQ-ACK codebook, and control (determine) the transmission power of the PUCCH transmitted in PUCCH transmission opportunity i based only on the TPC command included in the DCI format that triggers type 3 HARQ-ACK codebook.

[0364] When terminal device 1 receives a PDCCH in DCI format including a trigger type 3 HARQ-ACK codebook and a PDCCH triggering a codebook other than type 3 HARQ-ACK (e.g., type 1 HARQ-ACK or type 2 HARQ-ACK codebook) between PUCCH transmission opportunities i-i0 and PUCCH transmission opportunity i, terminal device 1 can control (determine) the transmission power of the PUCCH transmitted at PUCCH transmission opportunity i based on the DCI format of the trigger type 3 HARQ-ACK codebook and the TPC commands included in the DCI format received before the trigger type 3 HARQ-ACK codebook. That is, between PUCCH transmission opportunities i-i0 and PUCCH transmission opportunity i, terminal device 1 may also disregard the TPC commands included in the DCI format received after the trigger type 3 HARQ-ACK codebook is received.

[0365] One solution of the present invention enables efficient communication. One solution of the present invention enables efficient transmission and reception of HARQ-ACK information. One solution of the present invention enables efficient transmission and reception of the HARQ-ACK codebook. One solution of the present invention eliminates the identification mismatch between terminal device 1 and base station device 3 in the HARQ process, and enables the HARQ process to operate appropriately.

[0366] Hereinafter, various apparatus designs for one embodiment will be described.

[0367] (1) To achieve the above objective, the present invention adopts the following solution. Specifically, the first solution of the present invention is a terminal device having a processor and a memory storing computer program code. The terminal device includes: a transmitting unit that transmits a HARQ-ACK codebook via PUCCH in a certain time slot; and a receiving unit that receives multiple DCI formats in a set of PDCCH monitoring opportunities corresponding to the certain time slot. The resources for the PUCCH are determined by a PUCCH resource indication field included in the last received DCI format among the multiple DCI formats. If at least one of the multiple DCI formats is set to trigger a first HARQ-ACK codebook type, the HARQ-ACK codebook is generated using the first HARQ-ACK codebook type. If none of the multiple DCI formats is set to trigger the first HARQ-ACK codebook type, the HARQ-ACK codebook is generated using a second HARQ-ACK codebook different from the first HARQ-ACK codebook.

[0368] (2) A second aspect of the present invention is a terminal device comprising: a transmitting unit that transmits a PUCCH in a certain time slot; and a receiving unit that receives a plurality of DCI formats in a set of PDCCH monitoring opportunities corresponding to the certain time slot, wherein a plurality of PUCCHs exist in the certain time slot, and when the plurality of PUCCHs includes a first PUCCH including a HARQ-ACK codebook of a first type and a second PUCCH including a HARQ-ACK codebook of a second type, the second PUCCH is not transmitted.

[0369] (3) In the second aspect of the present invention, one or more TPC commands included in one or more DCI formats that control the transmission power of the second PUCCH are used to control the transmission power of the first PUCCH.

[0370] (4) A third aspect of the present invention is a base station apparatus comprising: a receiving unit that receives a HARQ-ACK codebook via PUCCH in a certain time slot; and a transmitting unit that transmits a plurality of DCI formats in a set of PDCCH monitoring opportunities corresponding to the certain time slot, wherein the resources for the PUCCH are determined by a PUCCH resource indication field included in a DCI format identified as the last transmitted among the plurality of DCI formats; wherein, if at least one of the plurality of DCI formats is set to trigger a first HARQ-ACK codebook type, the HARQ-ACK codebook is generated using the first HARQ-ACK codebook type; and if none of the plurality of DCI formats is set to trigger the first HARQ-ACK codebook type, the HARQ-ACK codebook is generated using a second HARQ-ACK codebook different from the first HARQ-ACK codebook.

[0371] (5) A fourth aspect of the present invention is a base station apparatus comprising: a receiving unit that receives a PUCCH in a certain time slot; and a transmitting unit that transmits a plurality of DCI formats in a set of PDCCH monitoring opportunities corresponding to the certain time slot, wherein there are a plurality of PUCCHs in the certain time slot, and the second PUCCH is not transmitted when the plurality of PUCCHs include a first PUCCH including a HARQ-ACK codebook of a first type and a second PUCCH including a HARQ-ACK codebook of a second type.

[0372] (6) In the fourth aspect of the present invention, one or more TPC commands included in one or more DCI formats that control the transmission power of the second PUCCH are used to control the transmission power of the first PUCCH.

[0373] The programs operating in the base station device 3 and terminal device 1 according to one aspect of the present invention can be programs that control CPUs (Central Processing Units) and the like to achieve the functions of the above-described embodiments according to one aspect of the present invention (programs that enable the computer to function). Then, the information processed by these devices is temporarily stored in RAM (Random Access Memory) during processing, and subsequently stored in various ROMs such as Flash ROM (Read Only Memory) and HDDs (Hard Disk Drives), and read, corrected, and written by the CPU as needed.

[0374] It should be noted that a portion of the terminal device 1 and base station device 3 described above can also be implemented using a computer. In this case, the program for implementing the control function can be recorded on a computer-readable recording medium, and the program recorded on the recording medium can be read into the computer system and executed.

[0375] It should be noted that the "computer system" mentioned here refers to the computer system built into terminal device 1 or base station device 3, and employs hardware including an operating system and peripheral devices. Furthermore, "computer-readable recording media" refers to removable media such as floppy disks, magneto-optical disks, ROMs, and CD-ROMs, as well as storage devices such as hard drives built into the computer system.

[0376] Furthermore, a "computer-readable recording medium" can include: a medium that dynamically stores a program for a short period of time, such as a communication line used when transmitting a program via a network such as the Internet or a communication line such as a telephone line; or a medium that stores a program for a fixed period of time, such as volatile memory within a computer system that serves as a server or client in this case. In addition, the aforementioned program can be a program used to implement the above-mentioned functions, or it can be a program that can implement the above-mentioned functions by combining with programs already recorded in the computer system.

[0377] Terminal device 1 may consist of at least one processor and at least one memory including computer program instructions (computer program). The memory and computer program instructions (computer program) may be configured to use the processor to cause terminal device 1 to perform the operations and processes described in the above embodiments. Base station device 3 may consist of at least one processor and at least one memory including computer program instructions (computer program). The memory and computer program instructions (computer program) may be configured to use the processor to cause base station device 3 to perform the operations and processes described in the above embodiments.

[0378] Furthermore, the base station device 3 in the above embodiments can also be implemented as an assembly (device group) composed of multiple devices. Each device constituting the device group can possess some or all of the functions or functional blocks of the base station device 3 in the above embodiments. As a device group, it is sufficient to have all the functions or functional blocks of the base station device 3. In addition, the terminal device 1 in the above embodiments can also communicate with the base station device, which is an assembly.

[0379] Furthermore, the base station device 3 in the above embodiments can be EUTRAN (Evolved Universal Terrestrial Radio Access Network) and / or NG-RAN (NextGenRAN, NR RAN). Additionally, the base station device 3 in the above embodiments may also have some or all of the functions of a host node for the eNodeB and / or gNB.

[0380] Furthermore, the terminal device 1 and base station device 3 described above can be implemented, either partially or entirely, as an LSI (Laser Sensor), typically an integrated circuit, or as a chipset. Each functional block of the terminal device 1 and base station device 3 can be implemented as a separate chip, or partially or entirely integrated into a single chip. Moreover, the method of integrated circuit implementation is not limited to LSI; it can also be implemented using dedicated circuits or general-purpose processors. Furthermore, if advancements in semiconductor technology lead to integrated circuit technologies that replace LSIs, integrated circuits based on such technologies can also be used.

[0381] Furthermore, while the above embodiments describe a terminal device as an example of a communication device, the invention of this application is not limited thereto and can be applied to fixed or non-movable electronic devices installed indoors or outdoors, such as AV equipment, kitchen equipment, cleaning / washing equipment, air conditioning equipment, office equipment, vending machines, and other household equipment, etc.

[0382] The embodiments of the present invention have been described in detail above with reference to the accompanying drawings. However, the specific configuration is not limited to these embodiments, and design changes that do not depart from the spirit of the present invention are also included. Furthermore, various modifications can be made to one aspect of the present invention within the scope shown in the technical solution. Embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included within the technical scope of the present invention. In addition, configurations obtained by replacing elements that have the same effect as the elements described in the above embodiments are also included.

[0383] Industrial availability

[0384] One aspect of the present invention can be used, for example, in communication systems, communication devices (e.g., mobile phone devices, base station devices, wireless LAN devices, or sensor devices), integrated circuits (e.g., communication chips), or programs.

[0385] Explanation of reference numerals in the attached figures

[0386] 1 (1A, 1B, 1C) Terminal device

[0387] 3. Base station equipment

[0388] 10, 30 Wireless Transceiver Unit

[0389] Antenna sections 11 and 31

[0390] RF Sections 12 and 32

[0391] 13, 33 Baseband Section

[0392] 14, 34 Upper-level processing unit

[0393] 15, 35 Media Access Control Layer Processing Department

[0394] 16, 36 Radio Resource Control Layer Processing Unit

Claims

1. A terminal device, the terminal device comprising: The transmitting unit is configured to transmit a HARQ-ACK codebook on the PUCCH in a time slot; and The receiving unit is configured to receive multiple DCI formats from a set of PDCCH monitoring opportunities corresponding to the time slot, wherein The resources used for the PUCCH are determined by the PUCCH resource indication field included in one of the last received DCI formats. When at least one of the plurality of DCI formats is set to trigger a first HARQ-ACK codebook type, the HARQ-ACK codebook is the first HARQ-ACK codebook type. If none of the plurality of DCI formats is set to trigger the first HARQ-ACK codebook type, the HARQ-ACK codebook is a second HARQ-ACK codebook type that is different from the first HARQ-ACK codebook type.

2. A base station apparatus, the base station apparatus comprising: A receiving unit, configured to receive a HARQ-ACK codebook on the PUCCH in a time slot; and The transmitting unit is configured to transmit multiple DCI formats in a set of PDCCH monitoring opportunities corresponding to the time slot, wherein The resources used for the PUCCH are determined by the PUCCH resource indication field included in one of the plurality of DCI formats last received by the terminal device. When at least one of the plurality of DCI formats is set to trigger a first HARQ-ACK codebook type, the HARQ-ACK codebook is the first HARQ-ACK codebook type. If none of the plurality of DCI formats is set to trigger the first HARQ-ACK codebook type, the HARQ-ACK codebook is a second HARQ-ACK codebook type that is different from the first HARQ-ACK codebook type.

3. A communication method for a terminal device, the communication method comprising: Send the HARQ-ACK codebook on the PUCCH in the time slot; as well as Multiple DCI formats are received from the set of PDCCH monitoring opportunities corresponding to the time slot, wherein... The resources used for the PUCCH are determined by the PUCCH resource indication field included in one of the last received DCI formats. When at least one of the plurality of DCI formats is set to trigger a first HARQ-ACK codebook type, the HARQ-ACK codebook is the first HARQ-ACK codebook type. If none of the plurality of DCI formats is set to trigger the first HARQ-ACK codebook type, the HARQ-ACK codebook is a second HARQ-ACK codebook type that is different from the first HARQ-ACK codebook type.

Images