Terminal, base station, and wireless communication method
By optimizing downlink and uplink operations through time-frequency-division duplexing, the solution addresses uplink resource insufficiency, improving system performance and resource utilization in high-density wireless communication environments.
Patent Information
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- NTT DOCOMO INC
- Filing Date
- 2022-08-10
- Publication Date
- 2026-06-18
AI Technical Summary
In high-density and high-traffic wireless communication environments, uplink resources are insufficient compared to downlink resources, leading to potential system performance degradation such as increased latency and reduced coverage.
Implementing terminals and base stations with control units that manage downlink and uplink operations based on time-frequency-division duplexing, adjusting radio resources, and transmission units that handle HARQ-ACK codebooks and channels accordingly to optimize resource utilization.
Enhances resource efficiency and mitigates latency and coverage issues by effectively managing uplink and downlink operations in time-frequency-division duplexing systems.
Smart Images

Figure 0007875968000044 
Figure 0007875968000045 
Figure 0007875968000046
Abstract
Description
【Technical Field】 【0001】 The present disclosure relates to a terminal, a base station, and a wireless communication method. 【Background Art】 【0002】 In a Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) was specified for the purpose of further high-speed data rates, low latency, etc. Also, for the purpose of further large capacity and sophistication of LTE (Third Generation Partnership Project (3GPP) Release (Rel.) 8, 9), LTE-Advanced (3GPP Rel.10-14) was specified. 【0003】 A successor system to LTE (for example, also referred to as 5th generation mobile communication system (5G), 5G+(plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel.15 and later, etc.) is also under consideration. 【Prior Art Documents】 【Patent Documents】 【0004】 【Non-Patent Document 1】 “Initial Views on Release 18 NR” RP-210293, 3GPP TSG RAN Meeting #91-e Electronic Meeting, March 16 -26, 2021 【Summary of the Invention】 【0005】 In future wireless communication systems (e.g., NR), it is anticipated that multiple user terminals (User Equipment (UE)) will communicate in extremely high-density and high-traffic environments. 【0006】 In such an environment, it is anticipated that uplink (UL) resources will be insufficient compared to downlink (DL) resources. 【0007】 However, currently, methods for increasing uplink resources have not been adequately considered. If these methods cannot be properly controlled, there is a risk of system performance degrading, such as increased latency and reduced coverage performance. 【0008】 Therefore, one of the objectives of this disclosure is to provide terminals, base stations, and wireless communication methods that improve the efficiency of resource utilization. 【0009】 One aspect of the present disclosure relates to a terminal having: a control unit that controls the receiving operation of a downlink data channel depending on whether or not the uplink time unit in non-time-frequency-division duplexing operation and / or the time unit in time-frequency-division duplexing operation overlap with the downlink data channel; and a receiving unit that performs the receiving operation of the downlink data channel by the controlled receiving operation. Another aspect of the present disclosure relates to a terminal having a control unit that determines a HARQ-ACK codebook for a downlink data channel depending on whether the downlink data channel overlaps with an uplink time unit, and a transmission unit that transmits a delivery confirmation in accordance with the HARQ-ACK codebook. Another aspect of the present disclosure relates to a terminal having: a control unit that controls the transmission operation of an uplink data channel depending on whether the uplink data channel overlaps with one or both of the downlink time units in non-time-frequency-division-duplex operation and the time units in time-frequency-division-duplex operation; and a transmission unit that performs the transmission operation of the uplink data channel by the controlled transmission operation. Another aspect of the present disclosure relates to a terminal having: a control unit that controls the transmission operation of an uplink control channel depending on whether the uplink control channel overlaps with one or both of the downlink time units in non-time-frequency-division duplexing operation and the time units in time-frequency-division duplexing operation; and a transmission unit that performs the transmission operation of the uplink control channel by the controlled transmission operation. Another aspect of the present disclosure relates to a terminal having a control unit that enables a delay operation of the HARQ-ACK when the delay conditions for the HARQ-ACK in time-frequency division duplex operation and non-time-frequency division duplex operation are satisfied, and a transmission unit that delays the transmission of the HARQ-ACK on the uplink control channel in accordance with the delay operation. Another aspect of the present disclosure relates to a terminal having, in time-frequency division duplexing downlink reception, a control unit that adjusts a radio resource indicated by downlink control information with respect to the time domain or frequency domain, and a receiving unit that receives a downlink channel with the adjusted radio resource. Another aspect of the present disclosure relates to a terminal having, in time-frequency division duplexing uplink transmission, a control unit that adjusts a radio resource indicated by downlink control information with respect to the time domain or frequency domain, and a transmitting unit that transmits an uplink channel with the adjusted radio resource. [Brief explanation of the drawing] 【0010】 [Figure 1] Figure 1 is a block diagram showing the functional configuration of a base station (gNB) according to one embodiment of the present disclosure. [Figure 2]Figure 2 is a block diagram showing the functional configuration of a terminal (UE) according to one embodiment of the present disclosure. [Figure 3] Figures 3A and 3B show examples of the arrangement of wireless resources in XDD (Cross Division Duplex) or SBFD (Subband non-overlapping Full Duplex) according to one embodiment of the present disclosure. [Figure 4] Figure 4 shows an XDD operation or SBFD operation according to one embodiment of the present disclosure. [Figure 5] Figures 5A and 5B show TDD (non-SBFD) and SBFD according to one embodiment of the present disclosure. [Figure 6] Figures 6A to 6E show pure time units and SBFD time units according to one embodiment of the present disclosure. [Figure 7] Figure 7 shows a single TRP PDSCH using slot-based PDSCH repetition with Rel-15 NR. [Figure 8] Figures 8A-8C show PDSCH transmission using Rel-15 / 16 NR. [Figure 9] Figure 9 shows a single DCI-based multi-TRP PDSCH transmission scheme using Rel-16 NR. [Figure 10] Figures 10A and 10B show Type 1 HARQ-ACKs using Rel-15 / 16 / 17 NR. [Figure 11] Figure 11 shows the candidate PDSCH reception opportunities using Rel-16 NR. [Figure 12] Figure 12 shows the HARQ-ACK opportunities associated with candidate PDSCH reception by Rel-16 NR. [Figure 13] Figure 13 shows the semi-persistent scheduling (SPS) HARQ-ACK codebook (CB) using Rel-15 / 16 / 17 NR. [Figure 14] Figure 14 shows multi-PDSCH scheduling using Rel-15 / 16 / 17 NR. [Figure 15] Figure 15 shows a PDSCH enhancement to SBFD operation according to one embodiment of the present disclosure. [Figure 16] Figure 16 shows a PDSCH enhancement to SBFD operation according to one embodiment of the present disclosure. [Figure 17] Figure 17 shows a PDSCH enhancement to SBFD operation according to one embodiment of the present disclosure. [Figure 18] Figure 18 shows a PDSCH enhancement to SBFD operation according to one embodiment of the present disclosure. [Figure 19] Figure 19 shows a PDSCH enhancement to SBFD operation according to one embodiment of the present disclosure. [Figure 20] Figure 20 shows a PDSCH enhancement to SBFD operation according to one embodiment of the present disclosure. [Figure 21] Figures 21A and 21B show a single TRP push using Rel-15 / 16 NR. [Figure 22] Figure 22 shows time-division multiplexing (TDM) multi-TRP push repetitions A and B using NR on Rel-17. [Figure 23] Figure 23 shows multi-push scheduling using Rel-15 / 16 / 17 NR. [Figure 24] Figure 24 shows a PUSCH enhancement to SBFD operation according to one embodiment of the present disclosure. [Figure 25] Figure 25 shows a PUCCH repetition using Rel-15 / 16 NR. [Figure 26] Figure 26 shows the SPS HARQ-ACK delay operation by Rel-17 NR. [Figure 27] Figure 27 shows a PUCCH enhancement to SBFD operation according to one embodiment of the present disclosure. [Figure 28] Figure 28 shows the preemption by DCI 2_1 using Rel-15 / 16 / 17 NR. [Figure 29] Figure 29 shows a preemption enhancement for SBFD operation according to one embodiment of the present disclosure. [Figure 30] Figure 30 shows a preemption enhancement for SBFD operation according to one embodiment of the present disclosure. [Figure 31] Figure 31 shows a preemption enhancement for SBFD operation according to one embodiment of the present disclosure. [Figure 32] Figure 32 shows a preemption enhancement for SBFD operation according to one embodiment of the present disclosure. [Figure 33] Figure 33 shows the cancellation by DCI 2_4 due to Rel-15 / 16 / 17 NR. [Figure 34] Figure 34 shows a cancellation enhancement for SBFD operation according to one embodiment of the present disclosure. [Figure 35] Figure 35 shows a cancellation enhancement for SBFD operation according to one embodiment of the present disclosure. [Figure 36] Figure 36 shows a cancellation enhancement for SBFD operation according to one embodiment of the present disclosure. [Figure 37] Figure 37 shows a cancellation enhancement for SBFD operation according to one embodiment of the present disclosure. [Figure 38] Figure 38 is a block diagram showing the hardware configuration of a base station and a terminal according to one embodiment of the present disclosure. [Figure 39] Figure 39 is a block diagram showing the hardware configuration of a vehicle according to one embodiment of the present disclosure. [Modes for carrying out the invention] 【0011】 Embodiments of this disclosure will be described below with reference to the drawings. 【0012】 (Wireless communication system) The configuration of a wireless communication system according to one embodiment of this disclosure will be described below. In this wireless communication system, communication is performed using any or a combination thereof of the wireless communication methods according to the above embodiments of this disclosure. The wireless communication system may be a system that realizes communication using Long Term Evolution (LTE), 5th generation mobile communication system New Radio (5G NR), or successor wireless communication systems specified by the Third Generation Partnership Project (3GPP). 【0013】 Furthermore, the wireless communication system may support dual connectivity between multiple Radio Access Technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC may include dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), dual connectivity between NR and LTE (NR-E-UTRA Dual Connectivity (NE-DC)), and so on. 【0014】 In EN-DC, the LTE (E-UTRA) base station (eNB) is the Master Node (MN), and the NR base station (gNB) is the Secondary Node (SN). In NE-DC, the NR base station (gNB) is the MN, and the LTE (E-UTRA) base station (eNB) is the SN. 【0015】 A wireless communication system may support dual connectivity between multiple base stations within the same RAT (for example, dual connectivity where both the MN and SN are NR base stations (gNB) (NR-NR Dual Connectivity (NN-DC))). 【0016】 The wireless communication system may include a base station forming a macrocell C1 with relatively wide coverage, and a base station located within the macrocell C1 that forms a small cell C2 with narrower coverage than the macrocell C1. Terminals (UEs) may be located within at least one cell. The arrangement, number, etc., of each cell and terminal are not limited to any particular configuration. 【0017】 The terminal may connect to at least one of several base stations. The terminal may utilize at least one of Carrier Aggregation (CA) using multiple Component Carriers (CC) and Dual Connectivity (DC). 【0018】 Each CC may be included in at least one of the first frequency band (Frequency Range 1 (FR1)) and the second frequency band (Frequency Range 2 (FR2)). A macrocell C1 may be included in FR1, and a small cell C2 may be included in FR2. For example, FR1 may be a frequency band of 6 GHz or less (sub-6 GHz), and FR2 may be a frequency band above 24 GHz (above-24 GHz). Note that the frequency bands and definitions of FR1 and FR2 are not limited to these, and for example, FR1 may fall in a frequency band higher than FR2. 【0019】 Furthermore, each CC may communicate using at least one of Time Division Duplex (TDD) and Frequency Division Duplex (FDD). 【0020】 Multiple base stations may be connected by wire (e.g., optical fiber compliant with Common Public Radio Interface (CPRI), X2 interface, etc.) or wireless (e.g., NR communication). For example, when NR communication is used as a backhaul between two base stations, the base station acting as the upstream station may be called an Integrated Access Backhaul (IAB) donor, and the base station acting as a relay station may be called an IAB node. 【0021】 Base stations may be connected to the core network via other base stations or directly. The core network may include at least one of the following: for example, an Evolved Packet Core (EPC), a 5G Core Network (5GCN), or a Next Generation Core (NGC). 【0022】 The terminal may be one that supports at least one of the following communication methods: LTE, LTE-A, 5G, 6G, etc. 【0023】 In wireless communication systems, orthogonal frequency division multiplexing (OFDM)-based wireless access schemes may be used. For example, Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), etc., may be used in at least one of the downlink (DL) and uplink (UL). 【0024】 The wireless access method may also be called a waveform. In wireless communication systems, other wireless access methods (for example, other single-carrier transmission methods, other multi-carrier transmission methods) may be used in addition to the UL and DL wireless access methods. 【0025】 In wireless communication systems, downlink channels may include Physical Downlink Shared Channels (PDSCH), broadcast channels (PBCH), and Physical Downlink Control Channels (PDCCH), which are shared among all terminals. 【0026】 Furthermore, in wireless communication systems, uplink channels such as the Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), and Physical Random Access Channel (PRACH) may be used as uplink channels shared by each terminal. 【0027】 User data, higher-layer control information, and System Information Blocks (SIBs) are transmitted via PDSCH. User data and higher-layer control information may also be transmitted via PUSCH. Furthermore, Master Information Blocks (MIBs) may be transmitted via PBCH. 【0028】 Lower-layer control information may be transmitted by PDCCH. The lower-layer control information may include, for example, Downlink Control Information (DCI) which includes scheduling information for at least one of PDSCH and PUSCH. 【0029】 Furthermore, the DCI that schedules PDSCH may be called a DL assignment or DL DCI, and the DCI that schedules PUSCH may be called a UL grant or UL DCI. Furthermore, PDSCH may be interpreted as DL data, and PUSCH may be interpreted as UL data. 【0030】 PDCCH detection may utilize a Control Resource Set (CORESET) and a search space. A CORESET corresponds to the resources used to search for DCIs. A search space corresponds to the search area and search method for PDCCH candidates. A single CORESET may be associated with one or more search spaces. The UE may monitor CORESETs associated with a particular search space based on the search space configuration. 【0031】 A single search space may correspond to one or more aggregation levels of PDCCH candidates. One or more search spaces may be referred to as a search space (SS) set. In this disclosure, "search space," "search space set," "search space configuration," "search space set configuration," "CORESET," and "CORESET configuration" may be interpreted interchangeably. 【0032】 PUCCH may transmit uplink control information (UCI) which includes at least one of the following: channel state information (CSI), delivery acknowledgment (e.g., Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, etc.), and scheduling request (SR). PRACH may transmit a random access preamble for establishing a connection with the cell. 【0033】 In this disclosure, the term "Physical" may be omitted from the beginning of each channel. 【0034】 In a wireless communication system, a synchronization signal (SS), a downlink reference signal (DL-RS), etc., may be transmitted. In a wireless communication system, the DL-RS may include a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DMRS), a positioning reference signal (PRS), a phase tracking reference signal (PTRS), etc. 【0035】 The synchronization signal may be, for example, at least one of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS). A signal block including SS (PSS, SSS) and PBCH (and DMRS for PBCH) may be called an SS / PBCH block, SS Block (SSB), etc. Note that SS, SSB, etc. may also be called reference signals. 【0036】 Furthermore, in wireless communication systems, the Uplink Reference Signal (UL-RS) may transmit the Sounding Reference Signal (SRS), Demodulation Reference Signal (DMRS), etc. The DMRS may also be called the UE-specific Reference Signal. 【0037】 (Device configuration) Next, an example of the functional configuration of a base station (gNB) 100 and a terminal (UE) 200 that perform the processing and operations described later will be explained. The gNB 100 and UE 200 include functions that realize the embodiments described later. However, the gNB 100 and UE 200 may each have only some of the functions in the embodiments. 【0038】 (gNB100) Figure 1 shows an example of the functional configuration of gNB100. As shown in Figure 1, gNB100 has a receiving unit 101, a transmitting unit 102, and a control unit 103. The functional configuration shown in Figure 1 is merely an example. Any functional classification and functional unit names are acceptable as long as they enable the operation according to the embodiment of the present invention. 【0039】 The receiving unit 101 includes the function of receiving various signals transmitted from the UE200 and obtaining information from higher layers, for example, from the received signals. The transmitting unit 102 includes the function of generating a signal to be transmitted to the UE200 and transmitting the signal by wire or wireless. 【0040】 The control unit 103 stores pre-configured setting information and various setting information to be transmitted to the UE200 in a storage device and reads it from the storage device as needed. The control unit 103 also performs processing related to communication with the UE200. The signal transmission function in the control unit 103 may be included in the transmission unit 102, and the signal reception function in the control unit 103 may be included in the reception unit 101. 【0041】 (UE200) Figure 2 shows an example of the functional configuration of the UE200. As shown in Figure 2, the UE200 has a transmitter 201, a receiver 202, and a control unit 203. The functional configuration shown in Figure 2 is merely an example. Any functional classification and name of the functional unit may be used as long as it enables the operation according to the embodiment of the present invention. 【0042】 The transmitting unit 201 creates a transmission signal from the transmission data and transmits the transmission signal wirelessly. The receiving unit 202 wirelessly receives various signals and acquires signals from higher layers from the received physical layer signals. The receiving unit 202 also has the function of receiving NR-PSS, NR-SSS, NR-PBCH, DL / UL control signals or reference signals transmitted from the gNB100. 【0043】 The control unit 203 stores various setting information received from the gNB100 by the receiving unit 202 in a storage device and reads it from the storage device as needed. The control unit 203 also performs processing related to communication with the gNB100. The signal transmission function in the control unit 203 may be included in the transmitting unit 201, and the signal reception function in the control unit 203 may be included in the receiving unit 202. 【0044】 (SBFD operation) Considering the transmission / reception time ratio (e.g., DL:UL = 4:1) in Time Division Duplex (TDD) up to Rel.16, there may be cases where the opportunities to transmit UL signals / channels are fewer than the opportunities to receive DL signals / channels. In such cases, the UE200 may not be able to transmit UL signals / channels frequently, raising concerns about transmission delays for important UL signals / channels. Furthermore, because the opportunities to transmit UL signals are fewer than the opportunities to receive DL signals, signal / channel congestion during UL transmission is also a concern. In addition, since the time resources available for transmitting UL signals / channels are limited in TDD, the application of UL coverage extension techniques such as repetition transmission is also limited. 【0045】 In future wireless communication systems (e.g., Rel.18 and beyond), the introduction of a time-frequency division duplex method combining TDD and frequency division duplex (FDD) for UL and DL is being considered. 【0046】 Examples of such time-frequency division duplexing methods include XDD (Cross Division Duplex) or Subband non-overlapping Full Duplex (SBFD). XDD or SBFD may also refer to a duplexing method in which DL and UL are frequency-division multiplexed within one component carrier (CC) of the TDD band (allowing simultaneous use of DL and UL). 【0047】 Figure 3A shows an example of a TDD configuration as defined up to Rel. 16. In the example shown in Figure 3A, a TDD slot or symbol is configured in the UE in a bandwidth such as one component carrier (CC) (which may also be called a cell or serving cell) and a bandwidth portion (BWP). 【0048】 In the example shown in Figure 3A, the time ratio of DL slots to UL slots is 4:1. With such conventional TDD slot or symbol settings, sufficient UL time resources cannot be secured, which may lead to UL transmission delays and reduced coverage performance. 【0049】 Figure 3B shows an example of an SBFD configuration. In the example shown in Figure 3B, within a single component carrier (CC), the resources used for receiving DL and the resources used for transmitting UL overlap in time. This resource configuration allows for the allocation of more UL resources, thereby improving resource utilization efficiency. 【0050】 For example, as shown in the example in Figure 3B, the ends of the frequency domain may be set as DL resources, and UL resources may be sandwiched between these DL resources. This can avoid and mitigate the occurrence of cross-link interference (CLI) with neighboring carriers. In addition, a guard region may be set at the boundary between the DL resources and the UL resources. 【0051】 Considering the complexity of handling self-interference, it is conceivable that only base station 100 would use both DL and UL resources simultaneously. In other words, for radio resources where DL and UL overlap in time, one UE200 may use the DL resource and another UE200 may use the UL resource. 【0052】 Figure 4 shows an example of SBFD operation. In the example shown in Figure 4, a portion of the DL resources in the TDD band are set as UL resources, and the DL and UL are configured to partially overlap in the time domain. 【0053】 In the example shown in Figure 4, during the DL-only period, each of the multiple UE200s (UE#1 and UE#2 in Figure 4) receives the DL channel / signal. 【0054】 Furthermore, during periods when DL and UL overlap in time, one UE200 (UE#1 in the example in Figure 4) receives the DL channel / signal, while another UE200 (UE#2 in the example in Figure 4) transmits the UL channel / signal. During this period, the base station 100 performs simultaneous transmission and reception of DL and UL. 【0055】 Furthermore, during UL-only periods, each of the multiple UE200s (UE#1 and UE#2 in Figure 4) transmits a UL channel / signal. 【0056】 In existing NRs (e.g., those defined by Rel. 15 / 16 / 17), DL frequency resources and UL frequency resources in the UE carrier are configured as DL BWPs and UL BWPs, respectively. Switching between DL / UL frequency resources requires the configuration of multiple BWPs and a BWP adaptation mechanism. 【0057】 Furthermore, in existing NRs, as shown in Figure 5A, the time resources (time units such as symbols and slots) in the TDD carrier for UE200 are set as at least one of DL, UL, and Flexible (FL) in the TDD configuration. 【0058】 The SBFD symbol may be a symbol that is notified or set as UL (or DL) on one frequency resource (subband), or notified or set for UL transmission (or DL reception), while on another frequency resource (subband), it may be a symbol that is notified or set as DL (or UL) or notified or set for DL reception (or UL transmission), as shown in Figure 5B. Alternatively, the SBFD symbol may be a symbol that is notified or set as UL (or DL) on a portion of the frequency resource, or notified or set for UL transmission (or DL reception). Alternatively, the SBFD symbol may be a symbol that is notified or set as DL (or UL) on a portion of the frequency resource, or notified or set for DL reception (or UL transmission). 【0059】 Here, the time unit may be at the symbol level, the slot / subslot level, or a group of symbols / slots / subslots. That is, an SBFD time unit may be an SBFD symbol, a slot / subslot containing or overlapping an SBFD symbol, or a group of symbols / slots / subslots containing or overlapping an SBFD symbol. 【0060】 A pure time unit may be a non-SBFD symbol (i.e., a symbol that is not an SBFD symbol), a slot / subslot that does not contain or overlap SBFD symbols, or a group of symbols / slots / subslots that do not contain or overlap SBFD symbols, and may also be called a non-SBFD time unit. For example, a pure time unit may be referred to as a time unit consisting only of DLs on a frequency resource, as shown in Figure 6A, or as a time unit consisting only of ULs on a frequency resource, as shown in Figure 6B. 【0061】 Furthermore, with respect to the SBFD time unit, DL resources and UL resources may have various arrangement patterns in the frequency domain. For example, the SBFD time unit of frequency domain pattern #1 may have the arrangement pattern shown in Figure 6C. The SBFD time unit of frequency domain pattern #2 may have the arrangement pattern shown in Figure 6D. The SBFD time unit of frequency domain pattern #3 may have the arrangement pattern shown in Figure 6E. These arrangement patterns are merely examples, and other arrangement patterns may be used. The frequency domain pattern of the SBFD time unit may mean a resource repetition pattern in the frequency domain for the SBFD time unit. 【0062】 (Terminology related to SBFD operation) Throughout this specification, the terms relating to SBFD operation described below may have the following meanings. The term “SBFD” here may be replaced with “Time-Frequency Division Duplexing.” “SBFD semistatic UL symbol” refers to an SBFD symbol configured as a UL by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated. 【0063】 An "SBFD Dynamic UL Symbol" is an SBFD symbol that is configured as Flexible (FL) by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated and notified as UL by DCI 2_0. 【0064】 An "SBFD semi-static DL symbol" is an SBFD symbol configured as a DL by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated. 【0065】 An "SBFD dynamic DL symbol" is an SBFD symbol that is configured as FL by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated and notified as DL by DCI 2_0. 【0066】 An "SBFD semi-static FL symbol" is an SBFD symbol that has been set as an FL by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated. 【0067】 An "SBFD dynamic FL symbol" is an SBFD symbol that is configured as an FL by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated and notified as an FL by DCI 2_0. 【0068】 A “non-SBFD semistatic UL symbol” is a non-SBFD symbol that has been configured as a UL by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated. 【0069】 A “non-SBFD dynamic UL symbol” is a non-SBFD symbol that is configured as FL by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated and notified as UL by DCI 2_0. 【0070】 A “non-SBFD semistatic DL symbol” is a non-SBFD symbol configured as a DL by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated. 【0071】 A “non-SBFD dynamic DL symbol” is a non-SBFD symbol that is configured as FL by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated and notified as DL by DCI 2_0. 【0072】 A “non-SBFD semistatic FL symbol” is a non-SBFD symbol that has been set as an FL by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated. 【0073】 A “non-SBFD dynamic FL symbol” is a non-SBFD symbol that is configured as an FL by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated and notified as an FL by DCI 2_0. 【0074】 (PDSCH in Rel-15 / 16 / 17) Regarding PDSCH TDD collisions, i.e., overlaps between resources for PDSCH reception and resources scheduled as uplinks, Rel-15 / 16 / 17 stipulates that PDSCH or PDSCH repeats that overlap with semistatic UL symbols will not be received. In other words, if a PDCCH, PDSCH, or CSI-RS overlaps even partially with the symbol set of a slot notified to the UE as an uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, the UE will not receive the PDCCH, PDSCH, or CSI-RS. 【0075】 Furthermore, if a UE is scheduled in DCI format to receive PDSCH across multiple slots, and tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated specifies that for each of these slots, if at least one symbol in the symbol set for which PDSCH reception is scheduled for the UE in that slot is an uplink symbol, the UE shall not receive PDSCH in that slot. 【0076】 Furthermore, according to Rel-15 / 16 / 17, PDSCH or PDSCH repetitions that overlap with dynamic UL / FL symbols are not to be received. In other words, if the upper layer has configured the UE to receive CSI-RS or PDSCH in the symbol set of a slot, and the UE detects a DCI format 2_0 with a slot format value other than 255 that notifies the UE of a slot format with a subset of symbols from that symbol set as uplink or flexible, or if the UE detects a DCI format that notifies the UE to transmit PUSCH, PUCCH, SRS, or PRACH in at least one symbol in that symbol set, the UE is to cancel the reception of CSI-RS in the symbol set of that slot, or cancel the reception of PDSCH in that slot. 【0077】 Rel-15 NR supports single transmit / receive point (s-TRP) PDSCH with no repetition or slot-based PDSCH repetition. For example, with slot-based PDSCH repetition, a PDSCH repetition can be transmitted across multiple slots, as shown in Figure 7. In s-TRP PDSCH transmission, a single PDCCH schedules a single PDSCH for a single TRP, as shown in Figure 8A. 【0078】 Furthermore, the Rel-16 NR supports two mechanisms for multi-transmit / receive point (m-TRP) / panel PDCCH transmission: single PDCCH-based m-TRP / panel transmission and multi-PDCCH-based m-TRP / panel transmission. 【0079】 In single-PDCCH-based m-TRP / panel transmission, a single PDCCH schedules multiple PDSCHs for multiple TRPs. For example, as shown in Figure 8B, PDCCH 1 schedules PDSCH 1 / Layer 1 and PDSCH 2 / Layer 2. 【0080】 On the other hand, in multi-PDCCH-based m-TRP / panel transmission, each of the multiple PDCCHs schedules a single PDSCH for each TRP. For example, as shown in Figure 8C, PDCCH 1 schedules PDSCH 1 / codeword (CW) 1, and PDCCH 2 schedules PDSCH 2 / CW 2. 【0081】 Furthermore, Rel-16 NR supports five schemes for single DCI (s-DCI) based m-TRP PDSCH transmission. Specifically, as shown in Figure 9, the five schemes supported are SDM(1a), FDMSchemeA(2a), FDMSchemeB(2b), TDMSchemeA(3), and TDMSchemeB(4). 【0082】 Here, for FDMSchemeA or FDMSchemeB, the allocated resource blocks (RBs) notified by the Frequency Domain Resource Allocation (FDRA) are separated into a first set of RBs for the first TRP (PDSCH from TRP#1) and a second set of RBs for the second TRP (PDSCH from TRP#2), as shown in Figure 9. 【0083】 Furthermore, regarding the transport block size (TBS) of the PDSCH, Section 5.1.3.2 of TS38.214 specifies a TBS determination procedure consisting of steps 1 to 3. In step 1, the UE first determines the number of REs (N) in the slot. RE ) is determined. In step 2, UE determines the number of REs (N RE ) based on the intermediate variable (N info ) is obtained. Then, in step 3, UE obtains the intermediate variable (N info TBS will make the decision based on the above. 【0084】 For s-DCI-based m-TRP PDSCH according to FDMSchemeA, the number of REs for TBS calculation is determined based on the symbols of the first TCI state, i.e., not on the total symbols in the slot. On the other hand, for s-DCI-based m-TRP PDSCH according to FDMSchemeB, the number of REs for TBS calculation is determined based on the RBs of the first TCI state, i.e., not on the RBs notified by FDRA. 【0085】 (HARQ-ACK CB) Regarding the generation of HARQ-ACK codebooks (CBs) for semi-persistent scheduling (SPS), Section 9.1.2 of TS38.213 stipulates that if an SPS PDSCH or any iteration of an SPS PDSCH overlaps with a semi-static UL symbol, that SPS PDSCH shall be excluded from the HARQ-ACK CB. 【0086】 Furthermore, regarding the generation of Type 1 HARQ-ACK CBs, Section 9.1.2.1 of TS38.213 stipulates that when performing TDRA pruning, if SLIV (Start and Length Indicator Value) or each repetition of SLIV overlaps with a semistatic UL symbol, SLIV shall be removed from the candidate TDRA. 【0087】 Here, the generation of a Type 1 HARQ-ACK CB can be performed, for example, as follows. First, in step A, the HARQ-ACK opportunity for candidate PDSCH reception is determined. That is, in step A-1, the PDSCH slot window is determined based on the set K1 set. For example, in the example shown in Figure 10A, μ DL =μ UL Assuming this is the case, the K1 set C(K1) is {1,2,3,4}. Also, in the example shown in Figure 10B, μ DL >μ ULAssuming it is so, the K1 set C(K1) is {1, 2, 3, 4}. 【0088】 And in step A-2, for each K1, the candidate PDSCH reception opportunities in each slot are determined. That is, the candidate PDSCH reception opportunities may be related to the TDRA table set R. Also, the candidate PDSCH reception opportunities in the time domain RA table that overlaps with UL set by tdd-UL-UL-ConfigurationCommon and tdd-UL-UL-ConfigurationDedicated may be excluded. Also, when determining the candidate PDSCH reception opportunities, the SLIV that overlaps with the semi-static UL symbol may be deleted. Also, for the candidate PDSCH reception opportunities that overlap in the time domain, the candidate PDSCH reception opportunities may be generated based on specific rules. For example, M of the serving cell c in Rel-16 A,c may be configured as shown in FIG. 11. 【0089】 Next, in step B, the UE determines the HARQ-ACK information bits for a total of 0 ACK HARQ-ACK information bits. For example, as shown in FIG. 12, for the determination of the candidate PDSCH reception opportunities in slot n (for example, the last two symbols can be semi-statically set as UL), the low indexes (RI) 2, 3, and 8 may be excluded from the generation of the HARQ-ACK bits because these candidate PDSCH reception opportunities overlap with the semi-static UL symbol. That is, the HARQ-ACK bits for these candidate PDSCH reception opportunities may not be generated. 【0090】 Furthermore, in the generation of HARQ-ACK CBs for SPS PDSCHs, the ordering is based on ascending order of the serving cell index, ascending order of the SPS configuration index, and ascending order of the slot index. It is stipulated that if each repeat of an SPS PDSCH overlaps with a semistatic UL symbol, the SPS PDSCH is deleted. Therefore, when generating a HARQ-ACK CB for only SPS PDSCHs, any SPS PDSCH or each repeat of an SPS PDSCH that overlaps with a semistatic UL symbol may be excluded from the HARQ-ACK CB. In other words, the HARQ-ACK bits for these SPS PDSCHs or each repeat of an SPS PDSCH may not be generated. 【0091】 For example, in the example shown in Figure 13, SPS PDSCH #2 and #3 overlap with semistatic UL symbols and are therefore excluded from the SPS HARQ-ACK CB, so the HARQ-ACK CB contains only the ACK / NACK for SPS PDSCH #1 and #4. 【0092】 (Multi-PDSCH scheduling) When scheduling multiple PDSCHs, DCI 1_1 is used as the DCI format. For example, as shown in Figure 14, PDSCH#1 to #4 can be scheduled by a single DCI. Rel-15 / 16 / 17 NR supports 120,480,960kHz SCS, and specifies that the maximum number of PDSCHs that can be scheduled by a single DCI is 8. In addition, for TDRA, a separate {SLIV, mapping type, scheduling offset K0} may be applied to each PDSCH in the TDRA table row. If a PDSCH conflicts with a semistatic UL symbol, that PDSCH is canceled, but it is not expected that all PDSCHs will be canceled. 【0093】 Furthermore, the MCS, NDI, and RV in the first or second TB field may appear only once and may apply to the first TB of each PDSCH. Additionally, the HPN field is applied to the first valid PDSCH, incremented by 1 for subsequent PDSCHs, and not incremented for invalid PDSCHs (i.e., PDSCHs that conflict with semistatic UL symbols). 【0094】 [Considerations regarding PDSCH enhancement for SBFD operation] The following is being considered regarding the SBFD operation of Rel-18. • SBFD operation in DL symbols, i.e., DL and UL subbands in DL symbols • SBFD operation in UL symbols, i.e., DL and UL subbands in UL symbols • SBFD operation in FL symbols, i.e., DL and UL subbands in FL symbols 【0095】 Here, if SBFD operation is supported or enabled for UL symbols, PDSCH or PDSCH repeats that overlap with UL symbols do not necessarily have to be dropped. On the other hand, if PDSCH or PDSCH repeats that overlap with UL symbols are not dropped, a delivery acknowledgment such as a HARQ-ACK may need to be reported for the reception of the PDSCH or PDSCH repeat at the UE. Therefore, the rules for TDD collisions in Rel-15 / 16 / 17 may need to be updated to reflect SBFD operation. That is, Case 1: PDSCH or PDSCH repeats overlapping with UL symbols in non-SBFD operation, Case 2: PDSCH or PDSCH repeats overlapping with DL or UL symbols in SBFD operation, These two cases can be discussed separately. 【0096】 For example, suppose the UL symbol or slot and the DL symbol or slot are configured by tdd-UL-DL-ConfigurationCommon as shown in Figure 15. In this case, according to the rules of Rel-15 / 16 / 17, PDSCH rep#3 and #4 of the PDSCH repetition are dropped. On the other hand, considering SBFD operation, PDSCH rep#3 is transmittable on the DL subband, so the UE may be able to receive PDSCH rep#3. 【0097】 [Proposal 1] Proposal 1 describes a PDSCH enhancement for time-frequency division duplexing operations such as SBFD operation. Specifically, the PDSCH dropping rule is extended for SBFD operation as follows. Case 1: When a PDSCH resource overlaps with a non-SBFD UL symbol. <alt-a> The UE does not receive PDSCH. <alt-b> The UE assumes that the PDSCH transmission has been deferred to a later slot that does not overlap with a non-SBFD UL symbol or FL symbol. Case 2: When the PDSCH resource overlaps with the SBFD symbol. <Alt 0> UE does not anticipate this case. <Alt 1> UE operates as follows, regardless of whether or not it overlaps with the UL subband: <<Alt 1-1> The UE does not receive PDSCH. <<Alt 1-2> > The UE assumes that the PDSCH transmission has been deferred to a non-SBFD DL resource. <<Alt 1-3> > The UE interprets this as PDSCH being rate-matched to resources other than SBFD symbols. <Alt 2> The UE operates as follows, depending on whether or not there is overlap with the UL subband: If the PDSCH does not overlap with the UL subband, the UE receives the PDSCH. On the other hand, if the PDSCH overlaps with the UL subband, the UE operates as follows: <<Alt 2-0> > UE does not anticipate this case. <<Alt 2-1> > The UE does not receive PDSCH. <<Alt 2-2> > UE assumes that the PDSCH has been rate-matched to the DL subband. 【0098】 For s-TRP PDSCH, s-TRP PDSCH repetition, m-DCI-based m-TRP PDSCH, s-DCI-based SFN PDSCH, and s-DCI-based m-TRP TDMed PDSCH repetition (i.e., s-DCI m-TRP PDSCH with tdmSchemeA or repetitionNumber set), the following cases 1 and 2 are possible. Case 1: A symbol included in the PDSCH or PDSCH repetition receiving resource overlaps with at least one non-SBFD semistatic / dynamic UL symbol (or non-SBFD dynamic FL symbol). Case 2: The symbols included in the resource for receiving PDSCH or PDSCH repetition do not overlap with non-SBFD semistatic / dynamic UL symbols (or non-SBFD dynamic FL symbols), but overlap with at least one SBFD semistatic / dynamic UL symbol, at least one SBFD semistatic / dynamic DL symbol, and / or at least one SBFD dynamic FL symbol. 【0099】 (Case 1) If, as in Case 1, the symbols included in the resource for receiving a PDSCH or PDSCH repeat overlap with at least one non-SBFD semistatic / dynamic UL symbol (or non-SBFD dynamic FL symbol), the UE may operate according to Alt-A and / or Alt-B below. 【0100】 <Case 1: Alt-A> In Alt-A, if a symbol included in the resource for receiving a PDSCH or PDSCH repeat overlaps with at least one non-SBFD semistatic / dynamic UL symbol (or non-SBFD dynamic FL symbol), the UE may choose not to receive the PDSCH or PDSCH repeat. In other words, the UE may choose not to receive a PDSCH or PDSCH repeat that overlaps with a UL symbol or FL symbol in non-SBFD operation. 【0101】 As an example of a modification, if a symbol included in the resource for receiving a PDSCH or PDSCH repeat is not received because it overlaps with at least one non-SBFD semistatic / dynamic UL symbol (or non-SBFD dynamic FL symbol), and the PDSCH or PDSCH repeat is one or any of several PDSCHs scheduled by a single DCI, then the HPN (HARQ Process Number) may be skipped for the PDSCH or PDSCH repeat. In other words, the UE does not need to send a HARQ-ACK for the PDSCH or PDSCH repeat. 【0102】 <Case 1: Alt-B> In Alt-B, if a symbol included in the resource for receiving a PDSCH or PDSCH repeat overlaps with at least one non-SBFD semistatic / dynamic UL symbol (or non-SBFD dynamic FL symbol), the UE may assume / determine / interpret that the PDSCH or PDSCH repeat has been deferred to a slot where the symbol in the time-domain resource for receiving the PDSCH or PDSCH repeat does not overlap with a non-SBFD semistatic / dynamic UL symbol (or non-SBFD dynamic FL symbol). That is, the UE may receive a PDSCH or PDSCH repeat that overlaps with a UL symbol or FL symbol in non-SBFD operation in any subsequent slot that does not overlap with a UL symbol or FL symbol in non-SBFD operation. Here, the UE may receive a PDSCH or PDSCH repeat that overlaps with a UL symbol or FL symbol in non-SBFD operation in any subsequent time unit such as a symbol, subslot, subframe, or frame that does not overlap with a UL symbol or FL symbol in non-SBFD operation. 【0103】 (Case 2) If, as in Case 2, the symbols included in the resource for receiving PDSCH or PDSCH repetitions do not overlap with non-SBFD semistatic / dynamic UL symbols (or non-SBFD dynamic FL symbols), but overlap with at least one SBFD semistatic / dynamic UL symbol, at least one SBFD semistatic / dynamic DL symbol, and / or at least one SBFD dynamic FL symbol, the UE may operate according to Alt 0, Alt 1, and / or Alt 2 below. 【0104】 <Case 2: Alt 0> In Alt 0, the UE may not assume / determine / decide that the symbols included in the resource for receiving a PDSCH or PDSCH repetition do not overlap with non-SBFD semistatic / dynamic UL symbols (or non-SBFD dynamic FL symbols), but do not overlap with at least one SBFD semistatic / dynamic UL symbol, at least one SBFD semistatic / dynamic DL symbol, and / or at least one SBFD dynamic FL symbol. In other words, the gNB may not transmit a PDSCH or PDSCH repetition that does not overlap with non-SBFD semistatic / dynamic UL symbols (or non-SBFD dynamic FL symbols), but does overlap with at least one SBFD semistatic / dynamic UL symbol, at least one SBFD semistatic / dynamic DL symbol, and / or at least one SBFD dynamic FL symbol. 【0105】 <Case 2: Alt 1> In Alt 1, if the symbols included in the resource for receiving PDSCH or PDSCH repetitions do not overlap with non-SBFD semistatic / dynamic UL symbols (or non-SBFD dynamic FL symbols), but overlap with at least one SBFD semistatic / dynamic UL symbol, at least one SBFD semistatic / dynamic DL symbol, and / or at least one SBFD dynamic FL symbol, the UE may operate according to Alt 1-1, Alt 1-2 and / or Alt 1-3 below, regardless of whether there is overlap with the UL subband. 【0106】 <<Case 2: Alt 1-1>> In Alt 1-1, if the symbols included in the resource for receiving PDSCH or PDSCH repetitions do not overlap with non-SBFD semistatic / dynamic UL symbols (or non-SBFD dynamic FL symbols), but overlap with at least one SBFD semistatic / dynamic UL symbol, at least one SBFD semistatic / dynamic DL symbol, and / or at least one SBFD dynamic FL symbol, the UE may choose not to receive PDSCH or PDSCH repetitions, regardless of whether there is overlap with the UL subband. In other words, the UE may choose not to receive PDSCH or PDSCH repetitions that overlap with UL symbols, DL symbols, or FL symbols in SBFD operation. 【0107】 As an alternative, PDSCH repetitions that were not received due to overlapping with SBFD semistatic / dynamic UL symbols, SBFD semistatic / dynamic DL symbols, and / or SBFD dynamic FL symbols may or may not be counted in the repetition count. 【0108】 Furthermore, as an alternative, if a PDSCH is not received due to overlap with an SBFD semistatic / dynamic UL symbol, an SBFD semistatic / dynamic DL symbol, and / or an SBFD dynamic FL symbol, and the PDSCH or PDSCH repeat is one or any of several PDSCHs scheduled by a single DCI, then the HPN may or may not be skipped for the PDSCH or PDSCH repeat. In other words, the UE may or may not send a HARQ-ACK for the PDSCH or PDSCH repeat. 【0109】 <<Case 2: Alt 1-2>> In Alt 1-2, if the symbols included in the resource for receiving a PDSCH or PDSCH repetition do not overlap with non-SBFD semistatic / dynamic UL symbols (or non-SBFD dynamic FL symbols), but overlap with at least one SBFD semistatic / dynamic UL symbol, at least one SBFD semistatic / dynamic DL symbol, and / or at least one SBFD dynamic FL symbol, the UE may assume / determine / interpret that the PDSCH or PDSCH repetition has been deferred to a slot where the resource does not overlap with non-SBFD semistatic / dynamic UL symbols (or non-SBFD dynamic FL symbols), and does not overlap with SBFD semistatic / dynamic UL symbols, SBFD semistatic / dynamic DL symbols, and / or SBFD dynamic FL symbols, regardless of whether or not there is overlap with the UL subband. In other words, the UE may receive the PDSCH or PDSCH repeat in any slot that does not overlap with a UL symbol or FL symbol in non-SBFD operation, and does not overlap with a UL symbol or DL symbol in SBFD operation. In other words, the gNB may transmit the PDSCH or PDSCH repeat in any slot that does not overlap with a UL symbol or FL symbol in non-SBFD operation, and does not overlap with a UL symbol or DL symbol in SBFD operation. The UE may also receive the PDSCH or PDSCH repeat in any time unit of any symbol, subslot, subframe, frame, etc., that does not overlap with a UL symbol or FL symbol in non-SBFD operation, and does not overlap with a UL symbol or DL symbol in SBFD operation. 【0110】 Furthermore, additional conditions may be required for such deferrals. For example, a deferral may be performed only when an SBFD operation instruction is set by RRC. In other words, if an SBFD operation is dynamically notified to the UE, the deferral does not apply. That is, if an SBFD operation is dynamically notified to the UE, the UE may choose not to receive PDSCH or PDSCH repeats. For example, if an SBFD operation is notified to the UE by DCI, the UE may choose not to receive PDSCH or PDSCH repeats in any subsequent time unit, such as symbols, subslots, slots, subframes, or frames, that do not overlap with non-SBFD UL symbols (or non-SBFD dynamic FL symbols) but overlap with SBFD UL symbols, SBFD DL symbols, and / or SBFD FL symbols. 【0111】 <<Case 2: Alt 1-3>> Alt 1-3 allows the UE to assume / determine / decide / interpret that the symbols included in the resource for receiving a PDSCH or PDSCH repetition are rate-matched on symbols other than SBFD semistatic / dynamic UL symbols, SBFD semistatic / dynamic DL symbols, and / or SBFD dynamic FL symbols. That is, the gNB may transmit a PDSCH or PDSCH repetition that is rate-matched on symbols other than SBFD semistatic / dynamic UL symbols, SBFD semistatic / dynamic DL symbols, and / or SBFD dynamic FL symbols. 【0112】 Herein, as one modification, if the PDSCH or PDSCH repeat is one or any of several PDSCHs scheduled by a single DCI, the HPN may or may not be skipped for the PDSCH or PDSCH repeat. That is, the UE may or may not send a HARQ-ACK for the PDSCH or PDSCH repeat. 【0113】 <Case 2: Alt 2> In Alt 2, if the symbols included in the resource for receiving PDSCH or PDSCH repetition do not overlap with non-SBFD semistatic / dynamic UL symbols (or non-SBFD dynamic FL symbols), but overlap with at least one SBFD semistatic / dynamic UL symbol, at least one SBFD semistatic / dynamic DL symbol, and / or at least one SBFD dynamic FL symbol, the UE may control the receiving operation of PDSCH or PDSCH repetition depending on whether or not there is overlap with the UL subband. 【0114】 Specifically, if the symbols included in a resource for receiving a PDSCH or PDSCH repetition do not overlap with non-SBFD semistatic / dynamic UL symbols (or non-SBFD dynamic FL symbols), but overlap with at least one SBFD semistatic / dynamic UL symbol, at least one SBFD semistatic / dynamic DL symbol, and / or at least one SBFD dynamic FL symbol, and the symbols included in a resource for receiving a PDSCH or PDSCH repetition do not overlap with the UL subband in the SBFD semistatic / dynamic UL symbols, SBFD semistatic / dynamic DL symbols, and / or SBFD dynamic FL symbols, then the UE may configure the advertised or configured resource to receive the PDSCH or PDSCH repetition. Furthermore, such resources may be defined by specifications, semistatically configured by RRC settings, dynamically advertised by DCI notifications, or determined according to rules. Furthermore, such resources may be defined, configured, advertised, or determined explicitly or implicitly. 【0115】 Herein, as one modification, if the PDSCH or PDSCH repeat is one or any of several PDSCHs scheduled by a single DCI, the HPN may not be skipped for the PDSCH or PDSCH repeat. That is, the UE may send a HARQ-ACK for the PDSCH or PDSCH repeat. 【0116】 On the other hand, if the symbols included in the PDSCH or PDSCH repetition receiving resource do not overlap with non-SBFD semistatic / dynamic UL symbols (or non-SBFD dynamic FL symbols), but overlap with at least one SBFD semistatic / dynamic UL symbol, at least one SBFD semistatic / dynamic DL symbol, and / or at least one SBFD dynamic FL symbol, and the symbols included in the PDSCH or PDSCH repetition receiving resource overlap with the UL subband in the SBFD semistatic / dynamic UL symbol, SBFD semistatic / dynamic DL symbol, and / or SBFD dynamic FL symbol, the UE may operate according to Alt 2-0, Alt 2-1, Alt 2-2, and / or Alt 2-3 below. 【0117】 <<Case 2: Alt 2-0>> Alt 2-0 allows the UE to avoid assuming / judging / determining cases where symbols included in a resource for receiving PDSCH or PDSCH repetitions do not overlap with non-SBFD semistatic / dynamic UL symbols (or non-SBFD dynamic FL symbols), but overlap with at least one SBFD semistatic / dynamic UL symbol, at least one SBFD semistatic / dynamic DL symbol, and / or at least one SBFD dynamic FL symbol, and where symbols included in a resource for receiving PDSCH or PDSCH repetitions overlap with the UL subband in SBFD semistatic / dynamic UL symbols, SBFD semistatic / dynamic DL symbols, and / or SBFD dynamic FL symbols. In other words, gNB may choose not to transmit PDSCH or PDSCH repetitions that overlap with the UL subband in SBFD semistatic / dynamic UL symbols, SBFD semistatic / dynamic DL symbols, and / or SBFD dynamic FL symbols, but do not overlap with non-SBFD semistatic / dynamic UL symbols (or non-SBFD dynamic FL symbols). 【0118】 <<Case 2: Alt 2-1>> Alt 2-1 allows the UE to choose not to receive the PDSCH or PDSCH repeat if the symbols included in the resource for receiving the PDSCH or PDSCH repeat do not overlap with non-SBFD semistatic / dynamic UL symbols (or non-SBFD dynamic FL symbols), but overlap with at least one SBFD semistatic / dynamic UL symbol, at least one SBFD semistatic / dynamic DL symbol, and / or at least one SBFD dynamic FL symbol, and the symbols included in the resource for receiving the PDSCH or PDSCH repeat overlap with the UL subband in the SBFD semistatic / dynamic UL symbol, SBFD semistatic / dynamic DL symbol, and / or SBFD dynamic FL symbol. In other words, the UE may choose not to receive the PDSCH or PDSCH repeat if it overlaps with the UL subband in the UL symbol, DL symbol, or FL symbol in SBFD operation. 【0119】 As an alternative, PDSCH repetitions that were not received due to overlap with the UL subband in SBFD semistatic / dynamic UL symbols, SBFD semistatic / dynamic DL symbols, and / or SBFD dynamic FL symbols may or may not be counted in the repetition count. 【0120】 Furthermore, as an alternative, if the PDSCH or PDSCH repeat is one or any of several PDSCHs scheduled by a single DCI, the HPN may or may not be skipped for the PDSCH or PDSCH repeat. In other words, the UE may or may not send a HARQ-ACK for the PDSCH or PDSCH repeat. 【0121】 <<Case 2: Alt 2-2>> Alt 2-2 states that if the symbols included in the resource for receiving a PDSCH or PDSCH repeat do not overlap with non-SBFD semistatic / dynamic UL symbols (or non-SBFD dynamic FL symbols), but overlap with at least one SBFD semistatic / dynamic UL symbol, at least one SBFD semistatic / dynamic DL symbol, and / or at least one SBFD dynamic FL symbol, and the PDSCH or PDSCH repeat overlaps with the UL subband in an SBFD semistatic / dynamic UL symbol, an SBFD semistatic / dynamic DL symbol, and / or an SBFD dynamic FL symbol, then the UE may assume / determine / interpret that the PDSCH or PDSCH repeat is rate-matched on the DL subband in an SBFD semistatic / dynamic UL symbol, an SBFD semistatic / dynamic DL symbol, and / or an SBFD dynamic FL symbol, and / or a non-SBFD semistatic / dynamic DL / FL symbol, where present. 【0122】 As an example of a modified configuration, if the PDSCH or PDSCH repeat is one or any of several PDSCHs scheduled by a single DCI, the HPN does not have to be skipped for that PDSCH or PDSCH repeat. In other words, the UE may send a HARQ-ACK for that PDSCH or PDSCH repeat. 【0123】 <<Case 2: Alt 2-3>> Alt 2-3 is a case where the symbols included in the resource for receiving PDSCH or PDSCH repeats do not overlap with non-SBFD semistatic / dynamic UL symbols (or non-SBFD dynamic FL symbols), but overlap with at least one SBFD semistatic / dynamic UL symbol, at least one SBFD semistatic / dynamic DL symbol, and / or at least one SBFD dynamic FL symbol, and the symbols included in the resource for receiving PDSCH or PDSCH repeats are SBFD semistatic / dynamic UL symbols, SBFD semistatic If a PDSCH or PDSCH repeat overlaps with the UL subband in a dynamic DL symbol and / or an SBFD dynamic FL symbol, the UE may assume / determine / decide / interpret that the PDSCH or PDSCH repeat is deferred to a slot where the resource does not overlap with a non-SBFD semistatic / dynamic UL symbol (or non-SBFD dynamic FL symbol) and does not overlap with any UL subband in an SBFD semistatic / dynamic UL symbol, SBFD semistatic / dynamic DL symbol, and / or an SBFD dynamic FL symbol. In other words, the UE may receive the PDSCH or PDSCH repeat in any subsequent slot where it does not overlap with a UL symbol or FL symbol in non-SBFD operation and does not overlap with the UL subband in a UL symbol, DL symbol, and / or FL symbol in SBFD operation. Here, the UE may receive the PDSCH or PDSCH repeat in any subsequent time unit of any symbol, subslot, subframe, frame, etc., that does not overlap with the UL symbol or FL symbol in non-SBFD operation, and does not overlap with the UL subband in the UL symbol, DL symbol and / or FL symbol in SBFD operation. 【0124】 Furthermore, additional conditions may be required for such deferrals. For example, a deferral may be performed only when an SBFD operation instruction is set by the RRC. In other words, if the SBFD operation is dynamically notified to the UE, the deferral does not apply. That is, if the SBFD operation is dynamically notified to the UE, the UE does not need to receive PDSCH or PDSCH repetitions. For example, if the SBFD operation is notified to the UE by DCI, the UE does not need to receive PDSCH or PDSCH repetitions in any subsequent time unit such as symbols, subslots, subframes, or frames that do not overlap with any non-SBFD UL symbols (or non-SBFD dynamic flexible symbols) but overlap with the UL subband in SBFD UL symbols, SBFD DL symbols, and / or SBFD FL symbols. 【0125】 Furthermore, which of the above-mentioned Alts to apply may be explicitly or implicitly specified by the specification, semi-statically set by RRC, dynamically notified by DCI, or determined by rules. For example, a parameter indicating which Alt to apply may be sent in at least one of RRC, DCI, and MAC CE (Medium Access Control Control Element). 【0126】 Here, if a rate-matching-based solution such as Alt 1-3 or Alt 2-2 described above is applied, the Transport Block Size (TBS) needs to be considered. For example, the TBS may be determined according to options A and / or B below. 【0127】 <Option A> In Option A, TBS is, i) Non-SBFD semistatic / dynamic UL symbols (and non-SBFD dynamic FL symbols), ii) SBFD semi-static / dynamic UL symbols, SBFD semi-static / dynamic DL symbols, and / or SBFD dynamic FL symbols, and / or iii) UL resource blocks (RBs) in SBFD semistatic / dynamic UL symbols, SBFD semistatic / dynamic DL symbols, and / or SBFD dynamic FL symbols, This may be determined based on the number of resource elements (REs) after excluding them. 【0128】 <Option B> In Option B, the TBS may be determined based on the number of REs notified by the Time Domain Resource Allocation (TDRA) and Frequency Domain Resource Allocation (FDRA). 【0129】 For example, for a PDSCH iteration, if option A is applied, the number of REs for TBS calculation may differ for different iterations. In such a case, the TBS for each iteration may be determined by the TBS calculated for the first PDSCH iteration and / or the maximum / minimum / average value of the TBS values calculated for all iterations. 【0130】 Which option to apply may be specified explicitly or implicitly by the specification, semi-statically set by RRC, dynamically notified by DCI, or determined by rules. For example, a parameter indicating which option should be applied may be transmitted in at least one of RRC, DCI, and MAC CE. For example, the UE may receive configuration information regarding options A and B via RRC and be dynamically notified by DCI which option A or B should be applied. 【0131】 (UE behavior in Proposal 1) In Proposal 1, the UE may control the receiving operation of the downlink data channel depending on whether the uplink time unit in non-time-frequency-division duplex operation and / or the time unit in time-frequency-division duplex operation overlap with the downlink data channel, and the receiving operation of the downlink data channel may be performed by the controlled receiving operation. Here, the time-frequency-division duplex operation may be SBFD, and the uplink time unit in non-time-frequency-division duplex operation may be a UL symbol, slot, or any other time unit in non-SBFD operation, specifically a non-SBFD semistatic / dynamic UL symbol and / or a non-SBFD dynamic FL symbol. Also, the time unit in time-frequency-division duplex operation may be a UL, DL or FL symbol, slot, or any other time unit in SBFD operation, specifically an SBFD semistatic / dynamic UL symbol, an SBFD semistatic / dynamic DL symbol, and / or an SBFD dynamic FL symbol. The downlink data channel may be, for example, a PDSCH, a PDSCH repeat, etc. 【0132】 Specifically, when a downlink data channel overlaps with an uplink time unit or flexible time unit in non-time-frequency-division-duplex operation, the UE may choose not to receive the downlink data channel. Alternatively, when a downlink data channel overlaps with an uplink time unit or flexible time unit in non-time-frequency-division-duplex operation, the UE may receive the downlink data channel in a time unit that does not overlap with an uplink time unit in non-time-frequency-division-duplex operation. That is, the UE may assume / determine / decide / interpret that the PDSCH or PDSCH repeat is deferred to a slot where the time-domain resource of the PDSCH or PDSCH repeat does not overlap with a non-SBFD semistatic / dynamic UL symbol. 【0133】 Furthermore, when a downlink data channel overlaps with a time unit in time-frequency division duplexing operation, the UE may control the reception operation of the downlink data channel regardless of whether the downlink data channel overlaps with the uplink subband in the time unit. For example, the UE does not have to assume / determine / decide / interpret that the downlink data channel overlaps with a time unit in SBFD operation. The UE may also choose not to receive the downlink data channel. Alternatively, the UE may receive the downlink data channel in time units that do not overlap with the uplink time unit or flexible time unit in non-SBFD operation, and that do not overlap with the uplink time unit, downlink time unit, and / or flexible time unit in SBFD operation. In other words, the UE may assume / determine / decide / interpret that the PDSCH or PDSCH repeat is deferred to time units such as slots where the resources of the PDSCH or PDSCH repeat do not overlap with non-SBFD semistatic / dynamic UL symbols and do not overlap with SBFD semistatic / dynamic UL symbols, SBFD semistatic / dynamic DL symbols, and / or SBFD dynamic FL symbols. Alternatively / furthermore, the UE may assume / determine / decide / interpret that the downlink data channel is rate-matched to time units other than time units in SBFD operation. In other words, the UE may assume / determine / decide / interpret that the PDSCH or PDSCH repeat is rate-matched on symbols other than SBFD semistatic / dynamic UL symbols, SBFD semistatic / dynamic DL symbols, and / or SBFD dynamic FL symbols. 【0134】 Furthermore, when a downlink data channel overlaps with a time unit in time-frequency division duplexing, the UE may control the reception of the downlink data channel depending on whether or not the downlink data channel overlaps with the uplink subband in that time unit. For example, if the downlink data channel does not overlap with the uplink subband in that time unit, the UE may receive the downlink data channel on the configured / advertised resource. Alternatively, the UE does not have to assume / determine / decide / interpret that the downlink data channel overlaps with the uplink subband in that time unit. The UE may also choose not to receive the downlink data channel. Or / Furthermore, the UE may assume / determine / decide / interpret that the downlink data channel is rate-matched on the DL subband in the time unit in SBFD operation. Alternatively, the UE may receive the downlink data channel in a time unit such as a slot that does not overlap with the uplink time unit or flexible time unit in non-SBFD operation, and does not overlap with the uplink time unit, downlink time unit, and / or flexible time unit in SBFD operation. That is, the UE may assume / determine / interpret that the PDSCH or PDSCH repeat is deferred to a time unit such as a slot that does not overlap with the non-SBFD semistatic / dynamic UL symbol, and does not overlap with the SBFD semistatic / dynamic UL symbol, SBFD semistatic / dynamic DL symbol, and / or SBFD dynamic FL symbol. 【0135】 (gNB operation in Proposal 1) In Proposal 1, the gNB may control the transmission operation of the downlink data channel in uplink time units in non-time-frequency-division-duplex operation and / or time units in time-frequency-division-duplex operation, and the controlled transmission operation may perform the transmission operation of the downlink data channel. Here, time-frequency-division-duplex operation may be SBFD, and the uplink time unit in non-time-frequency-division-duplex operation may be a UL symbol, slot, or any other time unit in non-SBFD operation, specifically a non-SBFD semistatic / dynamic UL symbol and / or a non-SBFD dynamic FL symbol. Also, the time unit in SBFD operation may be a UL, DL or FL symbol, slot, or any other time unit in SBFD operation, specifically an SBFD semistatic / dynamic UL symbol, an SBFD semistatic / dynamic DL symbol, and / or an SBFD dynamic FL symbol. The downlink data channel may be, for example, a PDSCH, a PDSCH repeat, etc. 【0136】 (UE Capability) Regarding the PDSCH enhancement for time-frequency division duplexing operation described above, UE capability information may be provided indicating whether the UE supports the PDSCH enhancement for time-frequency division duplexing operation. Furthermore, UE capability information regarding PDSCH transmission for time-frequency division duplexing, such as SBFD operation, may also be provided. If the UE supports the PDSCH enhancement for time-frequency division duplexing operation, it may send UE capability information to the gNB indicating that it supports the PDSCH enhancement for time-frequency division duplexing operation. Upon receiving such UE capability information, the gNB can send the enhanced PDSCH for time-frequency division duplexing operation to the UE, causing the UE to perform the enhanced PDSCH reception operation in time-frequency division duplexing operation. 【0137】 (Effects of Proposal 1) According to Proposal 1 described above, PDSCH enhancements for time-frequency division duplex operations such as SBFD operation can be realized. Specifically, the receiving operation of s-TRP PDSCH, s-TRP PDSCH repetition, m-DCI-based m-TRP PDSCH, s-DCI-based SFN PDSCH, and s-DCI-based m-TRP TDMed PDSCH repetition by the UE can be defined in SBFD and non-SBFD operations. 【0138】 [Proposal 2] Proposal 2 describes other PDSCH enhancements for time-frequency division duplexing operations such as SBFD operation. Specifically, the m-TRP FDM of the PDSCH is extended for SBFD operation as follows. Case 1: When a PDSCH resource overlaps with a non-SBFD UL symbol. <alt-a> The UE assumes that PDSCH will not be sent. <alt-b> The UE assumes that the PDSCH transmission was delayed. Case 2: When the PDSCH resource overlaps with the SBFD symbol. <Alt 1> UE operates as follows, regardless of whether or not it overlaps with the UL subband: <<Alt 1-1> The UE does not receive PDSCH. <<Alt 1-2> > The UE assumes that the PDSCH transmission has been deferred to a non-SBFD DL resource. <<Alt 1-3> > The UE assumes that PDSCH has been rate-matched to resources other than SBFD symbols. <Alt 2> The UE operates as follows, depending on whether or not there is overlap with the UL subband: If the PDSCH does not overlap with the UL subband, the UE receives the PDSCH. On the other hand, if the PDSCH overlaps with the UL subband, the UE operates as follows: <<Alt 2-0> > UE does not anticipate this case. <<Alt 2-1> > The UE does not receive PDSCH. <<Alt 2-2> > The UE assumes that the PDSCH transmission has been deferred to a resource that does not overlap. <<Alt 2-3> > Apply the dropping rule to each PDSCH resource in each TRP. <<Alt 2-4> > Rate matching is applied to each PDSCH resource in each TRP. <<Alt 2-5> > Allocate PDSCH resources from multiple TRPs to resources in the DL subband. 【0139】 For a frequency-division multiplexed PDSCH of s-DCI-based m-TRP, i.e., an s-DCI-based m-TRP PDSCH using fdmSchemeA or fdmSchemeB, the following cases 1 and 2 are possible. Case 1: Symbols included in time-domain resources for two PDSCH opportunities or repeated receptions overlap with at least one non-SBFD semistatic / dynamic UL symbol (or non-SBFD dynamic FL symbol) (see Figure 16). Case 2: Symbols included in the time-domain resource for two PDSCH opportunities or repeated receptions do not overlap with non-SBFD semistatic / dynamic UL symbols (or non-SBFD dynamic FL symbols), but overlap with at least one SBFD semistatic / dynamic UL symbol, at least one SBFD semistatic / dynamic DL symbol, and / or at least one SBFD semistatic / dynamic FL symbol (see Figure 17). 【0140】 (Case 1) If, as in Case 1, symbols included in the time-domain resources for two PDSCH opportunities or repeated receptions overlap with at least one non-SBFD semistatic / dynamic UL symbol (or non-SBFD dynamic FL symbol), the UE may operate according to Alt-A and / or Alt-B below. 【0141】 <Case 1: Alt-A> In Alt-A, the UE does not have to assume / determine / decide / interpret that two PDSCH opportunities or repetitions will be sent in which the symbols contained in the time-domain resource overlap with at least one non-SBFD semistatic / dynamic UL symbol (or non-SBFD dynamic FL symbol). In other words, the gNB may not send two PDSCH opportunities or repetitions in which the symbols contained in the time-domain resource overlap with at least one non-SBFD semistatic / dynamic UL symbol (or non-SBFD dynamic FL symbol). 【0142】 <Case 1: Alt-B> In Alt-B, the UE may assume / determine / interpret that two PDSCH opportunities or repetitions are deferred to slots where the symbols contained in the time-domain resource for receiving the two PDSCH opportunities or repetitions do not overlap with non-SBFD semistatic / dynamic UL symbols (or non-SBFD dynamic flexible symbols). That is, the UE may receive the PDSCH opportunities or repetitions in any subsequent slot that does not overlap with UL symbols or FL symbols in non-SBFD operation. 【0143】 (Case 2) If, as in Case 2, the symbols included in the time-domain resource for two PDSCH opportunities or repeated receptions do not overlap with non-SBFD semistatic / dynamic UL symbols (or non-SBFD dynamic FL symbols), but overlap with at least one SBFD semistatic / dynamic UL symbol, at least one SBFD semistatic / dynamic DL symbol, and / or at least one SBFD semistatic / dynamic FL symbol, the UE may operate according to Alt 1 and / or Alt 2 below. 【0144】 <Case 2: Alt 1> In Alt 1, if the symbols included in the time-domain resource for two PDSCH opportunities or repeated receptions do not overlap with non-SBFD semistatic / dynamic UL symbols (or non-SBFD dynamic FL symbols), but overlap with at least one SBFD semistatic / dynamic UL symbol, at least one SBFD semistatic / dynamic DL symbol, and / or at least one SBFD semistatic / dynamic FL symbol, the UE may operate according to Alt 1-1, Alt 1-2, and / or Alt 1-3, with or without overlap with the UL subband. 【0145】 <<Case 2: Alt 1-1>> Alt 1-1 means that the UE does not have to assume that the symbols included in the time-domain resource do not overlap with non-SBFD semistatic / dynamic UL symbols (or non-SBFD dynamic FL symbols) and that two PDSCH opportunities or repetitions overlapping with at least one SBFD semistatic / dynamic UL symbol, at least one SBFD semistatic / dynamic DL symbol, and / or at least one SBFD semistatic / dynamic FL symbol are transmitted. In other words, the gNB may not transmit two PDSCH opportunities or repetitions overlapping with at least one SBFD semistatic / dynamic UL symbol, at least one SBFD semistatic / dynamic DL symbol, and / or at least one SBFD semistatic / dynamic FL symbol, and that the symbols included in the time-domain resource do not overlap with non-SBFD semistatic / dynamic UL symbols (or non-SBFD dynamic FL symbols). For example, as shown in Figure 17, symbols included in the time-domain resources for two PDSCH opportunities or repeated receptions from TRP#1 and TRP#2 may not be received because they overlap with UL symbols in SBFD operation. 【0146】 <<Case 2: Alt 1-2>> Alt 1-2 allows the UE to assume / determine / decide / interpret that the two PDSCH opportunities or repetitions are deferred to slots where the symbols included in the time-domain resource for receiving the two PDSCH opportunities or repetitions do not overlap with non-SBFD semistatic / dynamic UL symbols (or non-SBFD dynamic flexible symbols) and do not overlap with SBFD semistatic / dynamic UL symbols, SBFD semistatic / dynamic DL symbols, and / or SBFD semistatic / dynamic FL symbols. In other words, the UE may receive the PDSCH opportunities or repetitions in any subsequent slot that does not overlap with UL symbols or FL symbols in non-SBFD operation and does not overlap with UL symbols, DL symbols, and / or FL symbols in SBFD operation. Alternatively, the UE may receive the PDSCH opportunity or repetition in any subsequent time unit, such as a symbol, subslot, subframe, or frame, that does not overlap with a non-SBFD semistatic / dynamic UL symbol (or non-SBFD dynamic flexible symbol) and does not overlap with an SBFD semistatic / dynamic UL symbol, an SBFD semistatic / dynamic DL symbol, and / or an SBFD semistatic / dynamic FL symbol. 【0147】 Furthermore, additional conditions may be required for such deferrals. For example, a deferral may be performed only when an SBFD operation instruction is set by the RRC. In other words, if an SBFD operation is dynamically notified to the UE, the deferral may not apply. That is, if an SBFD operation is dynamically notified to the UE, the UE may not assume / judge / decide / interpret that a PDSCH opportunity or repetition will be sent. 【0148】 <<Case 2: Alt 1-3>> Alt 1-3 allows the UE to assume / determine / decide / interpret that the symbols included in the time-domain resource for receiving a PDSCH opportunity or repetition are rate-matched on symbols other than SBFD semistatic / dynamic UL symbols, SBFD semistatic / dynamic DL symbols, and / or SBFD dynamic FL symbols. That is, the UE may assume / determine / decide / interpret that gNB is transmitting a rate-matched PDSCH opportunity or repetition on symbols other than SBFD semistatic / dynamic UL symbols, SBFD semistatic / dynamic DL symbols, and / or SBFD semistatic / dynamic FL symbols. 【0149】 Here, if the rate-matching-based solution described above is applied, the Transport Block Size (TBS) needs to be considered. For example, the TBS may be determined according to options A and / or B below. 【0150】 <Option A> In Option A, TBS may be determined based on the number of symbols after excluding SBFD semistatic / dynamic UL symbols, SBFD semistatic / dynamic DL symbols, and / or SBFD dynamic FL symbols from the symbols notified by TDRA. 【0151】 <Option B> In Option B, TBS may be determined based on the number of symbols notified by TDRA. 【0152】 For example, for PDSCH iterations, if option A is applied, the number of symbols for TBS calculation may differ for different iterations. In such cases, the TBS for each iteration may be determined by the TBS calculated for the first PDSCH iteration and / or the maximum / minimum / average value of the TBS values calculated for all iterations. 【0153】 Which option to apply may be specified explicitly or implicitly by the specification, semi-statically set by RRC, dynamically notified by DCI, or determined by rules. For example, a parameter indicating which option should be applied may be transmitted in at least one of RRC, DCI, and MAC CE. For example, the UE may receive configuration information regarding options A and B via RRC and be dynamically notified by DCI which option A or B should be applied. 【0154】 <Case 2: Alt 2> In Alt 2, if the symbols included in the time-domain resources for two PDSCH opportunities or repeated receptions do not overlap with non-SBFD semistatic / dynamic UL symbols (or non-SBFD dynamic FL symbols), but overlap with at least one SBFD semistatic / dynamic UL symbol, at least one SBFD semistatic / dynamic DL symbol, and / or at least one SBFD semistatic / dynamic FL symbol, the UE may control the PDSCH opportunity or repeated reception operation depending on whether or not there is overlap with the UL subband. 【0155】 Specifically, if the allocated physical resource block (PRB) notified by FDRA does not overlap with the UL subband in the SBFD semistatic / dynamic UL symbols, SBFD semistatic / dynamic DL symbols, and / or SBFD semistatic / dynamic FL symbols, the UE may determine a resource block (RB) for each TRP, as in Rel-16, and receive two PDSCH opportunities or repetitions on the notified / configured resource. The resource may be defined by the specification, semistatically configured by RRC configuration, dynamically notified by DCI notification, or determined according to rules. The resource may also be defined, configured, notified, or determined explicitly or implicitly. 【0156】 On the other hand, if the allocated physical resource block (PRB) notified by the FDRA overlaps with the UL subband in the SBFD semistatic / dynamic UL symbol, SBFD semistatic / dynamic DL symbol, and / or SBFD semistatic / dynamic FL symbol, the UE may operate according to Alt 2-0, Alt 2-1, Alt 2-2, Alt 2-3, Alt 2-4 and / or Alt 2-5 below. 【0157】 <<Case 2: Alt 2-0>> Alt 2-0 allows the UE to avoid assuming / judging / determining / interpreting cases in which symbols included in a time-domain resource for two PDSCH opportunities or repeated receptions do not overlap with non-SBFD semistatic / dynamic UL symbols (or non-SBFD dynamic FL symbols), but overlap with SBFD semistatic / dynamic UL symbols, SBFD semistatic / dynamic DL symbols, and / or SBFD semistatic / dynamic FL symbols, and the assigned PRB notified by the FDRA overlaps with the UL subband in SBFD semistatic / dynamic UL symbols, SBFD semistatic / dynamic DL symbols, and / or SBFD semistatic / dynamic FL symbols. In other words, gNB may allocate PRBs by FDRA such that the time-domain resources do not overlap with non-SBFD semistatic / dynamic UL symbols (or non-SBFD dynamic FL symbols) and do not overlap with SBFD semistatic / dynamic UL symbols, SBFD semistatic / dynamic DL symbols, and / or SBFD semistatic / dynamic FL symbols for two PDSCH opportunities or iterations where the time-domain resources do not overlap with SBFD semistatic / dynamic UL symbols, SBFD semistatic / dynamic DL symbols, and / or SBFD semistatic / dynamic FL symbols. 【0158】 <<Case 2: Alt 2-1>> In Alt 2-1, PDSCH opportunities or repetitions for two TCI states do not need to be received. That is, if the symbols included in the time-domain resource for receiving two PDSCH opportunities or repetitions do not overlap with non-SBFD semistatic / dynamic UL symbols (or non-SBFD dynamic FL symbols), but overlap with at least one SBFD semistatic / dynamic UL symbol, at least one SBFD semistatic / dynamic DL symbol, and / or at least one SBFD semistatic / dynamic FL symbol, and the assigned PRB notified by the FDRA overlaps with the UL subband in the SBFD semistatic / dynamic UL symbol, SBFD semistatic / dynamic DL symbol, and / or SBFD semistatic / dynamic FL symbol, the UE may not receive PDSCH opportunities or repetitions for two TCI states. 【0159】 <<Alt 2-2> > Alt 2-2 allows a PDSCH opportunity or repetition to be postponed to a slot where neither resource for receiving a PDSCH opportunity or repetition overlaps with a non-SBFD semistatic / dynamic UL symbol (or non-SBFD dynamic FL symbol), nor overlaps with any UL subband in an SBFD semistatic / dynamic UL symbol, SBFD semistatic / dynamic DL symbol, and / or SBFD semistatic / dynamic FL symbol. In other words, the UE may assume / determine / interpret that the PDSCH opportunity or repetition will be received in any subsequent slot where the symbols included in the resource for receiving the PDSCH opportunity or repetition do not overlap with a UL symbol or FL symbol in non-SBFD operation, and do not overlap with any UL subband in an UL symbol, DL symbol, and / or FL symbol in SBFD operation. Alternatively, the UE may receive the PDSCH or PDSCH repetition in any subsequent time unit, such as any symbol, subslot, subframe, or frame, in which the symbols included in the resource for receiving the PDSCH opportunity or repetition do not overlap with non-SBFD semistatic / dynamic UL symbols (or non-SBFD dynamic flexible symbols) and do not overlap with any UL subband in SBFD semistatic / dynamic UL symbols, SBFD semistatic / dynamic DL symbols, and / or SBFD dynamic FL symbols. 【0160】 Furthermore, additional conditions may be required for such deferrals. For example, a deferral may be performed only when an SBFD operation instruction is set by the RRC. In other words, if the SBFD operation is dynamically notified to the UE, the deferral does not apply. That is, if the SBFD operation is dynamically notified to the UE, the UE may choose not to receive PDSCH opportunities or repetitions. For example, if the SBFD operation is notified to the UE by the DCI, the UE may choose not to receive PDSCH opportunities or repetitions in subsequent symbols, slots, etc., that do not overlap with any non-SBFD UL symbols (or non-SBFD dynamic FL symbols) but overlap with the UL subband in SBFD UL symbols, SBFD DL symbols, and / or SBFD FL symbols. 【0161】 <<Case 2: Alt 2-3>> In Alt 2-3, the PRB assignment for each TCI state follows the rules of Rel-16, and the UE may drop PDSCH opportunities or repetitions that overlap with the UL subband. For example, after determining the RB assignment for each TCI state (according to the rules of Rel-16), PDSCH opportunities or repetitions that overlap with the UL subband may not be received, and PDSCH opportunities or repetitions that do not overlap with the UL subband may be transmitted (if any). For example, in the example shown in Figure 18, PDSCH opportunities or repetitions for TRP #2 that overlap with the UL subband are not received, and PDSCH opportunities or repetitions for TRP #1 that do not overlap with the UL subband are received. 【0162】 Here, the TBS may be determined as follows: For FDMSchemeA, the TBS may be determined based on the number of transmitted PDSCH opportunities or repeated PRBs. In other words, PDSCH opportunities or repeated PRBs that overlap with the UL subband may be excluded from the TBS calculation. On the other hand, for FDMSchemeB, the TBS may be determined in the same way as Rel-16. 【0163】 <<Case 2: Alt 2-4>> In Alt 2-4, the PRB assignment for each TCI state is determined according to the rules of Rel-16, and PDSCH opportunities or repetitions that overlap with the UL subband may be rate-matched on the DL resource block. For example, after determining the RB assignment for each TCI state (according to the rules of Rel-16), PDSCH opportunities or repetitions that overlap with the UL subband may be rate-matched on the DL RB of the RB determined for the TCI state, and PDSCH opportunities or repetitions that do not overlap with the UL subband may be transmitted (if any) on the RB determined for the TCI state. For example, in the example shown in Figure 19, the resources for the PDSCH opportunity or repetition of TRP #1 may be rate-matched on the DL subband of the lower frequency band, and the resources for the PDSCH opportunity or repetition of TRP #2 may be rate-matched on the DL subband of the higher frequency band. 【0164】 Here, the TBS may be determined as follows: For FDMSchemeA, the TBS may be determined based on the total number of two PDSCH opportunities or repeated DL RBs. On the other hand, for FDMSchemeB, the TBS may be determined in option A as with Rel-16 (i.e., as the number of REs in the first TCI state based on the notified FDRA and TDRA), in option B based on the actual number of REs in the first / second TCI state (i.e., after excluding UL RBs in the first / second TCI state), and / or in option C based on the greater / smaller / average value of the actual number of REs in the first / second TCI state (i.e., after excluding UL RBs in the first / second TCI state). Note that which of options A to C is applied may be specified by the specification, set semi-statically by RRC settings, dynamically notified by DCI notifications, or determined according to rules. Furthermore, which of options A through C is applied may be explicitly or implicitly specified, configured, notified, or determined. For example, a parameter indicating which option should be applied may be transmitted in at least one of the RRC, DCI, and MAC CE. For example, the UE may receive configuration information regarding options A through C via the RRC and be dynamically notified via the DCI which option A through C should be applied. 【0165】 <<Case 2: Alt 2-5>> In Alt 2-5, the PRB assignment for each TCI state may be based on the DL subband of each symbol after excluding the UL subband. Specifically, for each symbol, the number of DL RBs of the symbol after excluding the UL subband in that symbol may be assigned to two TCI states. For example, the first 【number】 Each PRB is assigned to the first TCI state, and the remaining 【number】 Each PRB may be assigned to a second TCI state. Here, n PRB teeth, 【number】 Assuming that this is the number of DL RBs in the symbol, this is the total number of PRBs allocated to the UE. 【0166】 Which of Alt 2-0 to Alt 2-5 is applied may depend on whether the SBFD operation (DL / UL subband allocation) is dynamically notified or RRC-configured. For example, if the SBFD operation (DL / UL subband allocation) is dynamically notified by DCI, Alt 2-3 may be applied, and if the SBFD operation (DL / UL subband allocation) is semi-statically configured by RRC, Alt 2-5 may be applied. For example, which of Alt 2-0 to Alt 2-5 is applied may be specified by the specification, semi-statically configured by RRC configuration, dynamically notified by DCI notification, or determined according to rules. Furthermore, which of Alt 2-0 to Alt 2-5 is applied may be explicitly or implicitly specified, configured, notified, or determined. For example, a parameter indicating which Alt should be applied may be transmitted in at least one of RRC, DCI, and MAC CE (Medium Access Control Control Element). 【0167】 (Variation of Proposal 1 / 2) The combined operation of SBFD and m-TRP PDSCH does not necessarily need to be supported. 【0168】 <Specific Example 1> In specific example 1, the UE does not have to assume / determine / decide / interpret that SBFD operation is notified / configured to the serving cell / bandwidth portion (BWP) and that at the same time any TCI code point (at least one code point) is mapped to two TCI states / QCLs in the serving cell / BWP. 【0169】 <Specific Example 2> In specific example 2, the UE does not have to assume / determine / decide / interpret that SBFD operation is notified / configured to the serving cell / bandwidth portion (BWP), that any TCI code point (at least one code point) is mapped to two TCI states / QCLs in the serving cell / BWP, and that the UE is simultaneously configured by the repetitionScheme set in the upper layer parameter FDMSchemeA. 【0170】 <Specific Example 3> In specific example 3, the UE does not have to assume / determine / decide / interpret that SBFD operation is notified / configured to the serving cell / bandwidth portion (BWP), that any TCI code point (at least one code point) is mapped to two TCI states / QCLs in the serving cell / BWP, and that the UE is simultaneously configured by the repetitionScheme set in the upper-layer parameter FDMSchemeB. 【0171】 <Specific Example 4> In specific example 4, the UE does not have to assume / determine / decide / interpret that SBFD operation is notified / configured to the serving cell / bandwidth portion (BWP), that any TCI code point (at least one code point) is mapped to two TCI states / QCLs in the serving cell / BWP, and that the UE is simultaneously configured by the repetitionScheme set in the upper-layer parameter TDMSchemeA. 【0172】 <Specific Example 5> In specific example 5, the UE does not need to assume / determine / decide / interpret that SBFD operation is notified / configured to the serving cell / bandwidth portion (BWP), that any TCI code point (at least one code point) is mapped to two TCI states / QCLs in the serving cell / BWP, and that the upper-layer parameter repetitionNumber is set to the UE at the same time. 【0173】 <Specific Example 6> In specific example 6, the UE does not need to assume / determine / decide / interpret that SBFD operation is notified / configured to the serving cell / bandwidth portion (BWP) and that at the same time any CORESET (at least one CORESET) is configured / notified in the serving cell / BWP by CORESETPoolID. 【0174】 <Specific Example 7> In specific example 7, when SBFD operation (and / or DL / UL subband allocation) is announced / configured for a serving cell / bandwidth portion (BWP), and DCI announces TCI code points that map to two TCI states / QCLs in the serving cell / BWP, the UE may use only the first / second TCI state / QCL for PDSCH transmission. 【0175】 <Specific Example 8> In specific example 8, when SBFD operation (and / or DL / UL subband allocation) is notified / configured for a serving cell / bandwidth portion (BWP), and DCI notifies a TCI code point that maps to two TCI states / QCLs in the serving cell / BWP, and the UE is configured by repetitionScheme set in the upper layer parameter FDMSchemeA, the UE may use only the first / second TCI states / QCLs for PDSCH transmission. 【0176】 <Specific Example 9> In specific example 9, when SBFD operation (and / or DL / UL subband allocation) is notified / configured for a serving cell / bandwidth portion (BWP), and DCI notifies a TCI code point that maps to two TCI states / QCLs in the serving cell / BWP, and the UE is configured by repetitionScheme set in the upper layer parameter FDMSchemeB, the UE may use only the first / second TCI states / QCLs for PDSCH transmission. 【0177】 <Specific Example 10> In specific example 10, when SBFD operation (and / or DL / UL subband allocation) is notified / configured for a serving cell / bandwidth portion (BWP), and DCI notifies a TCI code point that maps to two TCI states / QCLs in the serving cell / BWP, and the UE is configured by repetitionScheme set in the upper layer parameter TDMSchemeA, the UE may only use the first / second TCI states / QCLs for PDSCH transmission. 【0178】 <Specific Example 11> In specific example 11, when SBFD operation (and / or DL / UL subband allocation) is notified / configured for a serving cell / bandwidth portion (BWP), and DCI notifies a TCI code point that maps to two TCI states / QCLs in the serving cell / BWP, and the UE is set to the repetitionNumber of the upper layer parameter, the UE may use only the first / second TCI state / QCL for PDSCH transmission. 【0179】 (UE behavior in Proposal 2) In Proposal 2, the UE may control the receiving operation of the downlink data channel depending on whether the uplink time unit in a non-time-frequency-division duplex operation, such as non-SBFD operation, and / or the time unit in SBFD operation overlap with the downlink data channel, and the receiving operation of the downlink data channel may be performed by the controlled receiving operation. Here, the time-frequency-division duplex operation may be SBFD, and the uplink time unit in a non-time-frequency-division duplex operation may be a UL symbol, slot, or any other time unit in a non-SBFD operation, specifically a non-SBFD semistatic / dynamic UL symbol and / or a non-SBFD dynamic FL symbol. Also, the time unit in a time-frequency-division duplex operation may be a UL, DL or FL symbol, slot, or any other time unit in SBFD operation, specifically an SBFD semistatic / dynamic UL symbol, an SBFD semistatic / dynamic DL symbol, and / or an SBFD dynamic FL symbol. The downlink data channel may be, for example, a PDSCH, a PDSCH repeat, etc. 【0180】 Specifically, when multiple opportunities for a downlink data channel overlap with uplink time units in non-SBFD operation, the UE may assume / determine / decide / interpret that multiple opportunities for the downlink data channel will not be transmitted. Alternatively, when multiple opportunities for a downlink data channel overlap with uplink time units in non-SBFD operation, the UE may receive multiple opportunities for the downlink data channel in slots where the time-domain resources of the multiple opportunities for the downlink data channel do not overlap with uplink time units in non-SBFD operation. That is, the UE may assume / determine / decide / interpret that PDSCH opportunities or repetitions are deferred to slots where the resources of the PDSCH opportunities or repetitions do not overlap with non-SBFD semistatic / dynamic UL symbols. 【0181】 Furthermore, when multiple opportunities for a downlink data channel overlap with time units in SBFD operation, the UE may control the receiving operation of the downlink data channel regardless of whether the multiple opportunities for the downlink data channel overlap with the uplink subband in the time unit. For example, the UE may assume / determine / decide / interpret that multiple opportunities for the downlink data channel will not be transmitted. Alternatively, the UE may receive multiple opportunities for the downlink data channel in time units that do not overlap with uplink time units or flexible time units in non-SBFD operation and do not overlap with uplink time units, downlink time units, and / or flexible time units in SBFD operation. That is, the UE may assume / determine / decide / interpret that a PDSCH opportunity or repetition resource will be deferred to a slot that does not overlap with non-SBFD semistatic / dynamic UL symbols and does not overlap with SBFD semistatic / dynamic UL symbols, SBFD semistatic / dynamic DL symbols, and / or SBFD dynamic FL symbols. Alternatively, the UE may assume / determine / interpret that multiple opportunities on the downlink data channel are rate-matched on time units other than the time units in SBFD operation. That is, the UE may assume / determine / interpret that PDSCH opportunities or repetitions are rate-matched on symbols other than SBFD semistatic / dynamic UL symbols, SBFD semistatic / dynamic DL symbols, and / or SBFD semistatic / dynamic FL symbols. 【0182】 Furthermore, when multiple opportunities for a downlink data channel overlap with time units in SBFD operation, the UE may control the receiving operation of the downlink data channel depending on whether the downlink data channel overlaps with the uplink subband in time units. For example, if the allocated PRB notified by the FDRA does not overlap with the UL subband in SBFD semistatic / dynamic UL symbols, SBFD semistatic / dynamic DL symbols, and / or SBFD semistatic / dynamic FL symbols, the UE may determine the RB for each TRP as in Rel-16 and receive multiple opportunities for a downlink data channel on the notified / configured resource. On the other hand, the UE does not have to assume / determine / decide / interpret the case where the allocated PRB notified by the FDRA overlaps with the UL subband in SBFD semistatic / dynamic UL symbols, SBFD semistatic / dynamic DL symbols, and / or SBFD semistatic / dynamic FL symbols. Alternatively / furthermore, if the allocated PRB notified by FDRA overlaps with the UL subbands in the SBFD semistatic / dynamic UL symbols, SBFD semistatic / dynamic DL symbols, and / or SBFD semistatic / dynamic FL symbols, the UE may not receive downlink data channel opportunities for the two TCI states. Alternatively / furthermore, the resources for downlink data channel opportunities may be deferred to time units that do not overlap with non-SBFD semistatic / dynamic UL symbols and do not overlap with any UL subbands in the SBFD semistatic / dynamic UL symbols, SBFD semistatic / dynamic DL symbols, and / or SBFD semistatic / dynamic FL symbols. Alternatively / furthermore, PRB allocation for each TCI state may drop downlink data channel opportunities that overlap with UL subbands, in accordance with the rules of Rel-16.Alternatively, the PRB assignment for each TCI state may be rate-matched on the DL RB for opportunities of downlink data channels overlapping with the UL subband, in accordance with the rules of Rel-16. Alternatively, the PRB assignment for each TCI state may be based on the DL subband of each symbol after the exclusion of the UL subband. 【0183】 (gNB operation in Proposal 2) In Proposal 2, the gNB may control the transmission operation of the downlink data channel in uplink time units in non-time-frequency-division duplexing operations such as non-SBFD operation and / or in time-frequency-division duplexing operations such as SBFD operation, and the controlled transmission operation may perform the transmission operation of the downlink data channel. Here, the time-frequency-division duplexing may be SBFD, and the uplink time units in non-time-frequency-division duplexing operations may be UL symbols, slots, or any other time units in non-SBFD operation, specifically non-SBFD semistatic / dynamic UL symbols and / or non-SBFD dynamic FL symbols. Also, the time units in time-frequency-division duplexing operations may be UL, DL or FL symbols, slots, or any other time units in SBFD operation, specifically SBFD semistatic / dynamic UL symbols, SBFD semistatic / dynamic DL symbols, and / or SBFD dynamic FL symbols. The downlink data channel may be, for example, a PDSCH, a PDSCH repeat, etc. 【0184】 (UE Capability) Regarding PDSCH enhancements for time-frequency division duplex operations such as SBFD operation as described above, UE capability information may be defined indicating whether the UE supports s-DCI-based m-TRP PDSCH enhancements for time-frequency division duplex operations. Furthermore, UE capability information regarding PDSCH transmission of multiple transmit / receive points for time-frequency division duplex operations such as SBFD operation may also be defined. If the UE supports s-DCI-based MTRP PDSCH enhancements for time-frequency division duplex operations, the UE may transmit UE capability information to the gNB indicating that it supports s-DCI-based MTRP PDSCH enhancements for time-frequency division duplex operations. Upon receiving such UE capability information, the gNB can transmit an enhanced s-DCI-based MTRP PDSCH for time-frequency division duplex operations to the UE, causing the UE to perform enhanced PDSCH reception operations in SBFD operation. 【0185】 Furthermore, UE capability information may be specified indicating whether the UE supports s-DCI-based m-TRP PDSCH enhancement for time-frequency division duplexing operation using SFN / tdmSchemeA / tdmSchemeB (i.e., by the set number of repetitions) / fdmSchemeA / fdmSchemeB. If the UE supports such s-DCI-based m-TRP PDSCH enhancement for time-frequency division duplexing operation, the UE may send UE capability information indicating that it supports s-DCI-based m-TRP PDSCH enhancement for time-frequency division duplexing operation to the gNB. Upon receiving such UE capability information, the gNB can send the enhanced s-DCI-based m-TRP PDSCH for time-frequency division duplexing operation to the UE, causing the UE to perform the enhanced PDSCH receiving operation in time-frequency division duplexing operation. 【0186】 According to the above Proposal 2, PDSCH enhancements for time-frequency division multiplexing operations such as SBFD operations can be realized. Specifically, frequency division multiplexed PDSCH opportunities or repeated reception operations by the UE in SBFD operations and non-SBFD operations can be defined. 【0187】 [Proposal 3] In Proposal 3, HARQ-ACK enhancements for time-frequency division multiplexing operations such as SBFD operations are described. Specifically, the HARQ-ACK CB for SPS PDSCH and the Type 1 HARQ-ACK CB are enhanced for SBFD operations as follows. Regarding HARQ-ACK for SPS PDSCH <Alt 1> Regardless of whether it is an SBFD operation or a non-SBFD operation, when the symbols included in the resources for receiving SPS PDSCH overlap with the semi-statically configured UL symbols, the UE excludes the SPS PDSCH from the generation of the HARQ-ACK CB. That is, the HARQ-ACK bits for the SPS PDSCH may not be generated. <Alt 2> When the symbols included in the resources for receiving SPS PDSCH overlap with the non-SBFD UL symbols with semi-static configuration, the UE excludes the SPS PDSCH from the generation of the HARQ-ACK CB. That is, the HARQ-ACK bits for the SPS PDSCH may not be generated. <Alt 3> When the symbols included in the resources for receiving SPS PDSCH overlap with the semi-statically configured UL symbols or UL sub-bands, the UE excludes the SPS PDSCH from the generation of the HARQ-ACK CB. That is, the HARQ-ACK bits for the SPS PDSCH may not be generated. <Alt 4> Regardless of whether it is operating in SBFD or non-SBFD mode, if the symbols included in the resource for receiving an SPS PDSCH overlap with semi-statically set UL symbols or SBFD DL / FL symbols, the UE will exclude that SPS PDSCH from generating the HARQ-ACK CB. In other words, the HARQ-ACK bit for that SPS PDSCH may not be generated. <Alt 5> If the symbols included in the receiving resources for an SPS PDSCH overlap with semi-statically set UL symbols or UL subbands reserved for non-SBFD operation, the UE excludes the SPS PDSCH from generating the HARQ-ACK CB. In other words, the HARQ-ACK bit for the SPS PDSCH may not be generated. <Alt 6> The UE does not exclude SPS PDSCH from HARQ-ACK CB generation when SBFD operation is being performed. About Type 1 HARQ-ACK <Alt 1> Regardless of whether it is operating in SBFD or non-SBFD mode, if the SLIV of a PDSCH overlaps with a semi-statically set UL symbol, the UE excludes the SLIV of that PDSCH from generating the HARQ-ACK CB. In other words, the HARQ-ACK bit for the SLIV of that PDSCH does not need to be generated. <Alt 2> If the UE's SLIV of a PDSCH overlaps with a non-SBFD UL symbol that is set semi-statically, it excludes the SLIV of that PDSCH from generating the HARQ-ACK CB. In other words, the HARQ-ACK bit for the SLIV of that PDSCH does not need to be generated. <Alt 3> If the SLIV of a PDSCH overlaps with a semi-statically set UL symbol or UL subband, the UE excludes the SLIV of that PDSCH from generating the HARQ-ACK CB. In other words, the HARQ-ACK bit for the SLIV of that PDSCH does not need to be generated. <Alt 4> Regardless of whether it is operating in SBFD or non-SBFD mode, if the SLIV of a PDSCH overlaps with a semi-statically set UL symbol or SBFD DL / FL symbol, the UE excludes the SLIV of that PDSCH from generating the HARQ-ACK CB. In other words, the HARQ-ACK bit for the SLIV of that PDSCH does not need to be generated. <Alt 5> If the SLIV of a PDSCH overlaps with a semi-statically set UL symbol or UL subband reserved for non-SBFD operation, the UE excludes the SLIV of that PDSCH from generating the HARQ-ACK CB. In other words, the HARQ-ACK bit for the SLIV of that PDSCH may not be generated. <Alt 6> The UE does not exclude the PDSCH's SLIV from HARQ-ACK CB generation when SBFD operation is being performed. 【0188】 The UE can determine the HARQ-ACK codebook (which may also be called the HARQ-ACK size) semi-statically or dynamically. The HARQ-ACK codebook may be interpreted as the PDSCH's HARQ-ACK codebook, HARQ-ACK codebook size, HARQ-ACK bit count, etc. 【0189】 (SPS HARQ-ACK Codebook) For HARQ-ACK codebook generation for SPS, SPS PDSCH may be excluded according to Alt 1-6 below. 【0190】 <Alt 1> In Alt 1, if the symbols included in the SPS PDSCH or the resource for receiving repeated SPS PDSCH overlap with at least one semistatic UL symbol, regardless of whether it is in SBFD or non-SBFD operation, the SPS PDSCH may be excluded. 【0191】 <Alt 2> In Alt 2, if the symbols included in an SPS PDSCH or a resource for receiving repeated SPS PDSCHs overlap with at least one non-SBFD semistatic UL symbol, the SPS PDSCH may be excluded. 【0192】 <Alt 3> In Alt 3, an SPS PDSCH or a resource for receiving repeated SPS PDSCH signals may be excluded if the symbols contained within it overlap with at least one non-SBFD semistatic UL symbol, or overlap with the UL subband in an SBFD semistatic UL symbol, an SBFD semistatic DL symbol, and / or an SBFD semistatic FL symbol. 【0193】 <Alt 4> In Alt 4, if the symbols included in an SPS PDSCH or a resource for receiving repeated SPS PDSCHs overlap with at least one semistatic UL symbol or SBFD DL / FL symbol, regardless of whether it is in SBFD or non-SBFD operation, the SPS PDSCH may be excluded. 【0194】 <Alt 5> In Alt 5, an SPS PDSCH or a resource for receiving repeated SPS PDSCHs may be excluded if the symbols contained within it overlap with at least one semistatic UL symbol that is specified by the specification or reserved for non-SBFDs set by the RRC. 【0195】 <Alt 6> In Alt 6, when the SBFD operation is indicated / enabled, the SPS PDSCH or the repetition of the SPS PDSCH may not be deleted. 【0196】 From a standardization perspective, when the SBFD operation (or DL / UL sub-band allocation) is RRC-configured, Alt 2 is most likely. Also, when the SBFD operation (or DL / UL sub-band allocation) is dynamically notified, Alt 5 / 6 is most likely. 【0197】 Note that which of the above Alts to apply may be defined by the specification, either explicitly or implicitly, may be semi-statically set by RRC, may be dynamically notified by DCI, or may be determined by rules. For example, a parameter indicating which Alt to apply may be transmitted in at least one of RRC, DCI, and MAC CE (Medium Access Control Control Element). 【0198】 (Type 1 HARQ-ACK codebook) Regarding the generation of the Type 1 HARQ-ACK codebook, for TDRA pruning, the SLIV (Start and Length Indicator Value) in candidate PDSCH slot n_D may be deleted according to the following Alts 1 to 6. Here, the Type 1 HARQ-ACK CB may be called the semi-statically configured HARQ-ACK CB, and the Type 2 HARQ-ACK CB may be called the dynamically configured HARQ-ACK CB. Also, the HARQ-ACK CB may be renamed with the HARQ-ACK CB of the PDSCH, the HARQ-ACK CB size, the number of HARQ-ACK bits, etc. 【0199】 <Alt 1> In Alt 1, in slot (n_D - N PDSCH repeat For each slot from +1) to slot n_D, the SLIV in candidate PDSCH slot n_D may be deleted if the SLIV overlaps with at least one semistatic UL symbol, regardless of whether it is in SBFD or non-SBFD operation. 【0200】 <Alt 2> In Alt 2, the slot (n_D-N PDSCH repeat For each slot from +1) to slot n_D, the SLIV in candidate PDSCH slot n_D may be removed if the SLIV overlaps with at least one non-SBFD semistatic UL symbol. 【0201】 <Alt 3> In Alt 3, the slot (n_D-N PDSCH repeat For each slot from +1) to slot n_D, the SLIV in candidate PDSCH slot n_D may be removed if it overlaps with at least one non-SBFD semistatic UL symbol, or with the UL subband in an SBFD semistatic UL symbol, an SBFD semistatic DL symbol, and / or an SBFD semistatic FL symbol. 【0202】 <Alt 4> In Alt 4, the slot (n_D-N PDSCH repeat For each slot from +1) to slot n_D, the SLIV in candidate PDSCH slot n_D may be deleted if the SLIV overlaps with at least one semistatic UL symbol or SBFD DL / FL symbol, regardless of whether it is in SBFD or non-SBFD operation. 【0203】 <Alt 5> In Alt 5, the slot (n_D-N PDSCH repeat For each slot from +1) to slot n_D, the SLIV in candidate PDSCH slot n_D may be removed if the SLIV overlaps with at least one semistatic UL symbol reserved for non-SBFD as defined by the specification or set by the RRC. 【0204】 <Alt 6> In Alt 6, if SBFD operation is instructed / enabled, SLIV does not need to be deleted. 【0205】 From a standardization perspective, if SBFD operation (or DL / UL subband allocation) is configured in RRC settings, Alt 2 is the most likely option. Also, if SBFD operation (or DL / UL subband allocation) is dynamically announced, Alt 5 / 6 is the most likely option. 【0206】 Furthermore, which of the above-mentioned Alts to apply may be explicitly or implicitly specified by the specification, semi-statically set by RRC, dynamically notified by DCI, or determined by rules. For example, a parameter indicating which Alt to apply may be sent in at least one of RRC, DCI, and MAC CE (Medium Access Control Control Element). 【0207】 Furthermore, such notification may be sent via upper-layer signaling for each component carrier, each cell group (CG), each PUCCH group, or each UE. Each UE may determine (generate) HARQ-ACK information bits based on the determined HARQ-ACK codebook for each component carrier, each cell group (CG), each PUCCH group, or each UE, and transmit the generated HARQ-ACK using at least one of PUCCH or PUSCH. 【0208】 Note N PDSCH repeat This is the PDSCH repetition count. If pdsch-AggregationFactor-r16 is provided to the UE in SPS-Config or pdsch-AggregationFactor is provided in PDSCH-Config, and neither entry in pdsch-TimeDomainAllocationList nor pdsch-TimeDomainAllocationListDCI-1-2 contains repetitionNumber in PDSCH-TimeDomainResourceAllocationList, then N PDSCH repeat This is the maximum value of pdsch-AggregationFactor-r16 in SPS-Config or pdsch-AggregationFactor in PDSCH-Config, otherwise N PDSCH repeat =1 is also acceptable. 【0209】 (UE operation in Proposal 3) In Proposal 3, the UE may determine the HARQ-ACK codebook for the downlink data channel depending on whether the downlink data channel overlaps with the uplink time unit, and send a delivery confirmation according to the HARQ-ACK codebook. For example, the downlink data channel may be a PDSCH and / or a repetition of PDSCHs. The uplink time unit may be a semi-statically set symbol, or it may be a slot, subframe, or frame. 【0210】 Specifically, the UE may exclude an SPS PDSCH from determining the HARQ-ACK codebook if the SPS PDSCH overlaps with a semi-statically configured UL symbol. Specifically, the UE may determine how to generate the SPS HARQ-ACK CB depending on whether the symbols included in the receiving resource for the SPS PDSCH (each iteration) overlap with a semi-static UL symbol. For example, the UE may exclude the SPS PDSCH from generating the HARQ-ACK CB if the symbols included in the receiving resource for the SPS PDSCH overlap with a semi-statically configured UL symbol, regardless of whether it is in SBFD or non-SBFD operation. Furthermore / or, the UE may exclude the SPS PDSCH from generating the HARQ-ACK CB if the symbols included in the receiving resource for the SPS PDSCH overlap with a semi-statically configured non-SBFD UL symbol. Furthermore / or, the UE may exclude an SPS PDSCH from generating a HARQ-ACK CB if the symbols included in the receiving resources for that SPS PDSCH overlap with semi-statically configured UL symbols or UL subbands. Furthermore / or, regardless of whether it is operating in SBFD or non-SBFD mode, the UE may exclude an SPS PDSCH from generating a HARQ-ACK CB if the symbols included in the receiving resources for that SPS PDSCH overlap with semi-statically configured UL symbols or SBFD DL / FL symbols. Furthermore / or, the UE may exclude an SPS PDSCH from generating a HARQ-ACK CB if the symbols included in the receiving resources for that SPS PDSCH overlap with semi-statically configured UL symbols or UL subbands reserved for non-SBFD mode. In other words, the HARQ-ACK bit for that SPS PDSCH may not be generated. Furthermore / or, the UE may not exclude an SPS PDSCH from generating a HARQ-ACK CB if SBFD mode is being performed. 【0211】 Furthermore, the UE may exclude a downlink data channel's SLIV from the HARQ-ACK codebook determination if the SLIV overlaps with a semi-statically configured uplink symbol. Specifically, the UE may determine how to generate a Type 1 HARQ-ACK CB for each slot of a PDSCH depending on whether the PDSCH's SLIV overlaps with a semi-static UL symbol. For example, the UE may exclude a PDSCH's SLIV from the HARQ-ACK CB generation if it overlaps with a semi-statically configured UL symbol, regardless of whether it is operating in SBFD or non-SBFD mode. In addition / or, the UE may exclude a PDSCH's SLIV from the HARQ-ACK CB generation if it overlaps with a semi-statically configured non-SBFD UL symbol. Furthermore / or, the UE may exclude a PDSCH's SLIV from generating a HARQ-ACK CB if the SLIV of the PDSCH overlaps with a semi-statically set UL symbol or UL subband. Furthermore / or, regardless of whether it is in SBFD or non-SBFD operation, the UE may exclude a PDSCH's SLIV from generating a HARQ-ACK CB if the SLIV of the PDSCH overlaps with a semi-statically set UL symbol or SBFD DL / FL symbol. Furthermore / or, the UE may exclude a PDSCH's SLIV from generating a HARQ-ACK CB if the SLIV of the PDSCH overlaps with a semi-statically set UL symbol or UL subband reserved for non-SBFD operation. In other words, the HARQ-ACK bit for the PDSCH's SLIV does not need to be generated. Furthermore / or, the UE may not exclude a PDSCH's SLIV from generating a HARQ-ACK CB if SBFD operation is being performed. 【0212】 Furthermore, the UE may determine the HARQ-ACK codebook for the downlink data channel depending on whether the SBFD operation is set semi-statically or dynamically notified. The method for generating SPS HARQ-ACK CBs and / or Type 1 HARQ-ACK CBs may be defined by the specification, set semi-statically by RRC settings, dynamically notified by DCI notifications, or determined by the UE according to predetermined rules. The method for generating SPS HARQ-ACK CBs and / or Type 1 HARQ-ACK CBs may also be explicitly or implicitly defined, set, notified, or applied. Parameters indicating the above-described method for generating SPS HARQ-ACK CBs and / or Type 1 HARQ-ACK CBs may be transmitted in at least one of the RRC, DCI, and MAC CE (Medium Access Control Control Element). 【0213】 (gNB operation in Proposal 3) In Proposal 3, the gNB may transmit a downlink data channel and receive a delivery confirmation according to a HARQ-ACK codebook for the downlink data channel, which is determined depending on whether the downlink data channel overlaps with the uplink time unit. For example, the downlink data channel may be a PDSCH and / or a repetition of PDSCHs. The uplink time unit may be a semistatically set symbol, or it may be a slot, subframe, or frame. 【0214】 (UE Capability) Regarding the HARQ-ACK enhancement for time-frequency division duplexing operations such as SBFD operation described above, UE capability information indicating whether the UE supports the HARQ-ACK enhancement for time-frequency division duplexing operations may be specified. Furthermore, UE capability information regarding HARQ-ACK transmission for time-frequency division duplexing operations such as SBFD operation may also be specified. If the UE supports the HARQ-ACK enhancement for time-frequency division duplexing operations, it may transmit UE capability information indicating that it supports the HARQ-ACK enhancement for time-frequency division duplexing operations to the gNB. Upon receiving such UE capability information, the gNB can receive a HARQ-ACK CB from the UE to the PDSCH in accordance with the HARQ-ACK enhancement for time-frequency division duplexing operations. 【0215】 According to Proposal 3 described above, HARQ-ACK enhancements can be achieved for time-frequency division duplex operations such as SBFD operation. 【0216】 (PUSCH in Rel-15 / 16 / 17) According to Rel-15 / 16 / 17, PUSCH or PUSCH repetitions that overlap with semistatic DL symbols are not to be transmitted. In other words, for a symbol set of a slot notified to the UE as a downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, the UE is not to transmit PUSCH, PUCCH, PRACH, or SRS even if the symbols included in the resource for transmitting PUSCH, PUCCH, PRACH, or SRS partially overlap with the symbol set of that slot. 【0217】 Furthermore, if a UE is scheduled in DCI format to transmit PUSCH across multiple slots, and tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated specifies that for each of these slots, if at least one symbol in the symbol set for which PUSCH transmission is scheduled to be transmitted to the UE in that slot is a downlink symbol, the UE shall not transmit PUSCH in that slot. 【0218】 Furthermore, according to Rel-15 / 16 / 17, PUSCH or PUSCH repetitions that overlap with dynamic DL symbols / FL symbols are not to be transmitted. In other words, if the upper layer has configured the UE to transmit PUSCH, PUCCH, PRACH or SRS in the symbol set of a slot, and the UE detects a DCI format 2_0 with a slot format value other than 255 that notifies the slot format of a slot format with a subset of symbols from that symbol set as downlink or flexible, or the UE detects a DCI format that notifies the UE to receive PDSCH or CSI-RS in at least one symbol in that symbol set, and certain conditions are met, the UE is to cancel the transmission of PUSCH, PUCCH, PRACH or SRS in that symbol set. 【0219】 Rel-15 NR supports single transmit / receive point (s-TRP) pushes, i.e., push repetition type A, with either no repetition or slot-based push repetition. For example, with slot-based push repetition, a push repetition can be transmitted across multiple slots, as shown in Figure 21A. 【0220】 Furthermore, Rel-16 NR supports single transmit / receive point (s-TRP) push repetition with no repetition or sub-slot based push repetition, i.e., push repetition type B. A specific example shown in Figure 21B illustrates the case where the repetition coefficient K is 4 and the push length is 6, comparing slot-based push repetition in Rel-15 with sub-slot-based push repetition in Rel-16. 【0221】 Furthermore, Rel-17's NR supports TDM m-TRP PUSCH repetition types A and B. Specifically, it supports two beam / power control parameter sets and cyclic and sequential mapping between repetitions. As shown in Figure 22, in repetition type A with sequential mapping, different beam / power control parameters can be set for two TRPs for repetition #1 and repetition #3. On the other hand, in repetition type B with cyclic mapping, different beam / power control parameters can be set for two TRPs for repetition #1 and repetition #2. Note that in repetition type B, one nominal repetition is segmented into two actual repetitions at the slot boundary. Note that cyclic repetition type A and sequential repetition type B are also possible. 【0222】 (Multi-PUSCH scheduling) When scheduling multiple PUSCHs, DCI 0_1 is used as the DCI format. For example, as shown in Figure 23, PUSCH #1 to #4 can be scheduled by a single DCI. Here, 120, 480, and 960 kHz SCS are supported, and the maximum number of PUSCHs that can be scheduled by a single DCI is specified to be 8. In addition, for TDRA, a separate {SLIV, mapping type, scheduling offset K2} may be applied to each PUSCH in the TDRA table row. If a PUSCH conflicts with a semi-static DL symbol or SSB symbol, that PUSCH is canceled, but it is not expected that all PDSCHs will be canceled. 【0223】 Furthermore, the MCS, NDI, and RV in the first TB field appear only once and apply to the first TB of each PUSCH. The HPN field applies to the first valid PUSCH and is incremented by 1 for subsequent PUSCHs, but is not incremented for invalid PUSCHs (i.e., PUSCHs that conflict with semi-static DL symbols or SSB symbols). 【0224】 [Considerations regarding PUSCH enhancements for SBFD operation] The following is being considered regarding the SBFD operation of Rel-18. • SBFD operation in DL symbols, i.e., DL and UL subbands in DL symbols • SBFD operation in UL symbols, i.e., DL and UL subbands in UL symbols • SBFD operation in Flexible (FL) symbols, i.e., DL and UL subbands in FL symbols. 【0225】 Here, if SBFD operation is supported or enabled for DL symbols, PUSCH or PUSCH repetitions that overlap with DL symbols do not necessarily have to be dropped. Therefore, the rules for TDD collisions in Rel-15 / 16 / 17 may need to be updated to accommodate SBFD operation. 【0226】 For example, suppose the UL and DL symbols or slots in TDD are configured by tdd-UL-DL-ConfigurationCommon as shown in Figure 24. In this case, according to the rules of Rel-15 / 16 / 17, PUSCH rep#1 and #2 in the PUSCH repetition are dropped. On the other hand, considering SBFD operation, PUSCH rep#2 is transmittable on the UL subband, so the UE may be able to transmit PUSCH rep#2. 【0227】 [Proposal 4] Proposal 4 describes a Push enhancement for time-frequency division duplexing operations such as SBFD operation. Specifically, Push repetition type A is enhanced for SBFD operation as follows. Case 1: When the PUSCH resource overlaps with a non-SBFD DL symbol. <Alt A> The UE does not send a PUSCH. <Alt B> UE will postpone the transmission of PUSCH. Case 2: When the PUSCH resource overlaps with the SBFD symbol. <Alt 1> The UE operates according to Alt 1-1 to 1-3 below, regardless of whether or not there is overlap with the DL subband. <<Alt 1-1> > The UE does not send a PUSCH. <<Alt 1-2> > The UE defers sending PUSCH to non-SBFD UL resources. <<Alt 1-3> > The UE rate-matches PUSCH to resources other than SBFD symbols. <Alt 2> The UE operates according to Alt 2-1 to 2-3 below, depending on whether or not there is overlap with the DL subband. <<Alt 2-1> > The UE does not send a PUSCH. <<Alt 2-2> > UE rate-matches PUSCH to the UL subband. <<Alt 2-3> > UE will postpone the transmission of PUSCH. 【0228】 For s-TRP PUSCH, s-TRP PUSCH repeat type A, or m-TRP PUSCH repeat type A, the UE controls the PUSCH transmission operation according to the following cases 1 and 2. That is, Case 1: A symbol included in the resource for transmitting a PUSCH or a PUSCH repetition by type A overlaps with at least one non-SBFD semistatic / dynamic DL symbol (or non-SBFD dynamic FL symbol), SSB symbol, or type-0 CORESET symbol. Case 2: The symbols included in the resource for transmitting a PUSCH or a PUSCH repetition by repetition type A do not overlap with any non-SBFD semistatic / dynamic DL symbols (or non-SBFD dynamic FL symbols), but overlap with at least one SBFD semistatic / dynamic DL symbol, at least one SBFD semistatic / dynamic UL symbol, and / or at least one SBFD semistatic / dynamic FL symbol. 【0229】 (Case 1) If, as in Case 1, the symbols included in the resource for sending a PUSCH or a PUSCH repetition by repetition type A overlap with at least one non-SBFD semistatic / dynamic DL symbol (or non-SBFD dynamic FL symbol), SSB symbol, or type-0 CORESET symbol, the UE may operate according to Alt-A and / or Alt-B below. 【0230】 <Case 1: Alt-A> In Alt-A, if a symbol included in the resource for transmitting a PUSCH or a PUSCH repeat by repeat type A overlaps with at least one non-SBFD semistatic / dynamic DL symbol (or non-SBFD dynamic FL symbol), an SSB symbol, or a type-0 CORESET symbol, the UE may refrain from transmitting the PUSCH or PUSCH repeat. In other words, the UE may refrain from transmitting a PUSCH or PUSCH repeat that overlaps with a DL symbol or FL symbol in non-SBFD operation. 【0231】 As an example of a modification, if a symbol included in the resource for transmitting a PUSCH or PUSCH repeat is not transmitted due to overlapping with at least one non-SBFD semistatic / dynamic DL symbol (or non-SBFD dynamic FL symbol), SSB symbol, or type-0 CORESET symbol, and the PUSCH or PUSCH repeat is one or any of several PUSCHs scheduled by a single DCI, then the HPN (HARQ Process Number) may be skipped for the PUSCH or PUSCH repeat. 【0232】 <Case 1: Alt-B> In Alt-B, if the symbols included in the resource for transmitting a PUSCH or a PUSCH repetition of type A overlap with at least one non-SBFD semistatic / dynamic DL symbol (or non-SBFD dynamic FL symbol), SSB symbol, or type-0 CORESET symbol, the UE may defer the PUSCH or PUSCH repetition to a slot / subslot where the symbols included in the resource for transmitting the PUSCH or PUSCH repetition do not overlap with a non-SBFD semistatic / dynamic DL symbol (or non-SBFD dynamic FL symbol), SSB symbol, or type-0 CORESET symbol. In other words, the UE may transmit a PUSCH or PUSCH repetition that overlaps with a DL symbol or FL symbol in non-SBFD operation to any subsequent slot / subslot where it does not overlap with a DL symbol or FL symbol in non-SBFD operation. Alternatively, the UE may transmit a PDSCH or PDSCH repeat that overlaps with a UL symbol or FL symbol in non-SBFD operation in any subsequent time unit such as a symbol, subslot, subframe, or frame that does not overlap with a UL symbol or FL symbol in non-SBFD operation. 【0233】 (Case 2) If, as in Case 2, the symbols included in the resource for sending a PUSCH or a PUSCH repetition by repetition type A do not overlap with any non-SBFD semistatic / dynamic DL symbols (or non-SBFD dynamic FL symbols), but overlap with at least one SBFD semistatic / dynamic DL symbol, at least one SBFD semistatic / dynamic UL symbol, and / or at least one SBFD semistatic / dynamic FL symbol, the UE may operate according to Alt 1 and / or Alt 2 below. 【0234】 <Case 2: Alt 1> In Alt 1, if the symbols included in the resources for transmitting PUSCH or PUSCH repetitions by repetition type A do not overlap with any non-SBFD semistatic / dynamic DL symbols (or non-SBFD dynamic FL symbols), but overlap with at least one SBFD semistatic / dynamic DL symbol, at least one SBFD semistatic / dynamic UL symbol, and / or at least one SBFD semistatic / dynamic FL symbol, the UE may operate according to Alt 1-1, Alt 1-2 and / or Alt 1-3 below, regardless of whether there is overlap with the DL subband. 【0235】 <<Case 2: Alt 1-1>> In Alt 1-1, if the symbols included in the resource for transmitting a PUSCH or a PUSCH repetition by repetition type A do not overlap with any non-SBFD semistatic / dynamic DL symbol (or non-SBFD dynamic FL symbol), but overlap with at least one SBFD semistatic / dynamic DL symbol, at least one SBFD semistatic / dynamic UL symbol, and / or at least one SBFD semistatic / dynamic FL symbol, the UE may refrain from transmitting a PUSCH or PUSCH repetition, regardless of whether there is overlap with the DL subband. In other words, the UE may refrain from transmitting a PUSCH or PUSCH repetition that overlaps with a UL symbol, DL symbol, or FL symbol in SBFD operation. 【0236】 As an alternative, PUSCH repetitions that were not transmitted due to overlapping with SBFD semistatic / dynamic UL symbols, SBFD semistatic / dynamic DL symbols, and / or SBFD dynamic FL symbols may or may not be counted in the repetition count. 【0237】 Furthermore, as an alternative, if a PUSCH is not transmitted due to overlap with an SBFD semistatic / dynamic UL symbol, an SBFD semistatic / dynamic DL symbol, and / or an SBFD dynamic FL symbol, and the PUSCH or PUSCH repetition is one or any of several PUSCHs scheduled by a single DCI, then the HPN may or may not be skipped for the PUSCH or PUSCH repetition. 【0238】 <<Case 2: Alt 1-2>> In Alt 1-2, if the symbols included in the resource for transmitting a PUSCH or a PUSCH repetition by repetition type A do not overlap with any non-SBFD semistatic / dynamic DL symbols (or non-SBFD dynamic FL symbols) and overlap with at least one SBFD semistatic / dynamic DL symbol, at least one SBFD semistatic / dynamic UL symbol, and / or at least one SBFD semistatic / dynamic FL symbol, the UE may defer the PUSCH or PUSCH repetition to a slot / subslot where the symbols included in the resource for transmitting the PUSCH or PUSCH repetition do not overlap with any non-SBFD semistatic / dynamic DL symbols (or non-SBFD dynamic FL symbols) and do not overlap with any SBFD semistatic / dynamic UL symbol, any SBFD semistatic / dynamic DL symbol, and / or any SBFD semistatic / dynamic FL symbol, regardless of whether there is overlap with the DL subband. In other words, the UE may transmit the PUSCH or PUSCH repetition in any subsequent slot / subslot that does not overlap with DL symbols or FL symbols in non-SBFD operation, and does not overlap with UL symbols, DL symbols, and / or FL symbols in SBFD operation. Alternatively, the UE may transmit the PUSCH or PUSCH repetition in any subsequent time unit of any symbol, subslot, subframe, frame, etc., that does not overlap with non-SBFD semistatic / dynamic UL symbols (or non-SBFD dynamic flexible symbols), and does not overlap with any SBFD semistatic / dynamic UL symbols, any SBFD semistatic / dynamic DL symbols, and / or any SBFD dynamic FL symbols. 【0239】 Furthermore, additional conditions may be required for such deferrals. For example, a deferral may be performed only when an SBFD operation instruction is set by RRC. In other words, if an SBFD operation is dynamically notified to the UE, the deferral does not need to be applied. That is, if an SBFD operation is dynamically notified to the UE, the UE may refrain from sending PUSCH or PUSCH repetitions. For example, if an SBFD operation is notified to the UE by DCI, the UE may refrain from sending PUSCH or PUSCH repetitions in subsequent symbols, slots, etc., that do not overlap with any non-SBFD DL symbols (or non-SBFD dynamic FL symbols) but overlap with SBFD UL symbols, SBFD DL symbols, and / or SBFD FL symbols. 【0240】 <<Case 2: Alt 1-3>> In Alt 1-3, if the symbols included in the resource for transmitting a PUSCH or a PUSCH repetition by repetition type A do not overlap with any non-SBFD semistatic / dynamic DL symbols (or non-SBFD dynamic FL symbols), but overlap with at least one SBFD semistatic / dynamic DL symbol, at least one SBFD semistatic / dynamic UL symbol, and / or at least one SBFD semistatic / dynamic FL symbol, the UE may rate match the PUSCH or PUSCH repetition on the symbols excluding the SBFD semistatic / dynamic UL symbol, SBFD semistatic / dynamic DL symbol, and / or SBFD dynamic FL symbol. 【0241】 Herein, as one modification, if the PUSCH or PUSCH repetition is one or any of several PUSCHs scheduled by a single DCI, the HPN may not be skipped for the PUSCH or PUSCH repetition. 【0242】 <Case 2: Alt 2> In Alt 2, if the symbols included in the resource for transmitting a PUSCH or a PUSCH repetition by repetition type A do not overlap with any non-SBFD semistatic / dynamic DL symbols (or non-SBFD dynamic FL symbols), but overlap with at least one SBFD semistatic / dynamic DL symbol, at least one SBFD semistatic / dynamic UL symbol, and / or at least one SBFD semistatic / dynamic FL symbol, the UE controls the transmission operation of the PUSCH or PUSCH repetition depending on whether or not there is overlap with the DL subband. 【0243】 Specifically, if the symbols included in the resource for transmitting a PUSCH or a PUSCH repetition of type A do not overlap with any non-SBFD semistatic / dynamic DL symbol (or non-SBFD dynamic FL symbol), but overlap with at least one SBFD semistatic / dynamic DL symbol, at least one SBFD semistatic / dynamic UL symbol, and / or at least one SBFD semistatic / dynamic FL symbol, and the symbols included in the resource for transmitting a PUSCH or PUSCH repetition do not overlap with the DL subband in the SBFD semistatic / dynamic UL symbol, SBFD semistatic / dynamic DL symbol, and / or SBFD semistatic / dynamic FL symbol, then the UE may transmit the PUSCH or PUSCH repetition in the advertised or configured resource. The resource may be defined by the specification, semistatically configured by RRC settings, dynamically advertised by DCI notifications, or determined according to rules. The resource may also be defined, configured, advertised, or determined explicitly or implicitly. 【0244】 Herein, as one modification, if the PUSCH or PUSCH repetition is one or any of several PUSCHs scheduled by a single DCI, the HPN may not be skipped for the PUSCH or PUSCH repetition. 【0245】 On the other hand, if the symbols included in the resource for transmitting PUSCH or PUSCH repetitions by repetition type A do not overlap with any non-SBFD semistatic / dynamic DL symbols (or non-SBFD dynamic FL symbols), but overlap with at least one SBFD semistatic / dynamic DL symbol, at least one SBFD semistatic / dynamic UL symbol, and / or at least one SBFD semistatic / dynamic FL symbol, and the symbols included in the resource for transmitting PUSCH or PUSCH repetitions overlap with the DL subband in the SBFD semistatic / dynamic UL symbol, SBFD semistatic / dynamic DL symbol, and / or SBFD semistatic / dynamic FL symbol, the UE may operate according to Alt 2-1, Alt 2-2, and / or Alt 2-3 below. 【0246】 <<Case 2: Alt 2-1>> Alt 2-1 states that if the symbols included in the resource for transmitting a PUSCH or a PUSCH repetition by repetition type A do not overlap with any non-SBFD semistatic / dynamic DL symbol (or non-SBFD dynamic FL symbol), but overlap with at least one SBFD semistatic / dynamic DL symbol, at least one SBFD semistatic / dynamic UL symbol, and / or at least one SBFD semistatic / dynamic FL symbol, and the symbols included in the resource for transmitting a PUSCH or a PUSCH repetition overlap with the DL subband in an SBFD semistatic / dynamic UL symbol, an SBFD semistatic / dynamic DL symbol, and / or an SBFD semistatic / dynamic FL symbol, the UE may refrain from transmitting a PUSCH or a PUSCH repetition. In other words, the UE may refrain from transmitting a PUSCH or a PUSCH repetition that overlaps with the DL subband in a UL symbol, DL symbol, or FL symbol in SBFD operation. 【0247】 As an alternative, PUSCH repetitions that were not transmitted due to overlap with the DL subband in SBFD semistatic / dynamic UL symbols, SBFD semistatic / dynamic DL symbols, and / or SBFD dynamic FL symbols may or may not be counted in the repetition count. 【0248】 As another variation, if the PUSCH or PUSCH repetition is one or any of several PUSCHs scheduled by a single DCI, then the HPN may or may not be skipped for the PUSCH or PUSCH repetition. 【0249】 <<Case 2: Alt 2-2>> Alt 2-2 allows the UE to rate match the PUSCH or PUSCH repetition on the UL subband of the SBFD semistatic / dynamic UL symbol, SBFD semistatic / dynamic DL symbol, and / or SBFD semistatic / dynamic FL symbol, if the symbols included in the resource for transmitting the PUSCH or PUSCH repetition do not overlap with any non-SBFD semistatic / dynamic DL symbol (or non-SBFD dynamic FL symbol), but overlap with at least one SBFD semistatic / dynamic DL symbol, at least one SBFD semistatic / dynamic UL symbol, and / or SBFD semistatic / dynamic FL symbol, and if the symbols included in the resource for transmitting the PUSCH or PUSCH repetition overlap with the DL subband of the SBFD semistatic / dynamic UL symbol, SBFD semistatic / dynamic DL symbol, and / or SBFD semistatic / dynamic FL symbol. 【0250】 As an example of a modification, if the PUSCH or PUSCH repetition is one or any of several PUSCHs scheduled by a single DCI, then the HPN may or may not be skipped for the PUSCH or PUSCH repetition. 【0251】 <<Case 2: Alt 2-3>> Alt 2-3 is defined as the case where the symbols included in the resource for transmitting PUSCH or PUSCH repetition by repetition type A do not overlap with any non-SBFD semistatic / dynamic DL symbols (or non-SBFD dynamic FL symbols), but overlap with at least one SBFD semistatic / dynamic DL symbol, at least one SBFD semistatic / dynamic UL symbol, and / or at least one SBFD semistatic / dynamic FL symbol, and the symbols included in the resource for transmitting PUSCH or PUSCH repetition are SBFD semistatic / dynamic UL symbols, SBFD semistatic If a PUSCH or PUSCH repetition overlaps with a DL subband in a sci-fi / dynamic DL symbol and / or an SBFD semi-static / dynamic FL symbol, the UE may postpone the transmission of the PUSCH or PUSCH repetition to a slot / subslot where the symbols included in the resource for transmitting the PUSCH or PUSCH repetition do not overlap with non-SBFD semi-static / dynamic DL symbols (or non-SBFD dynamic FL symbols) and do not overlap with any DL subband in an SBFD semi-static / dynamic UL symbol, an SBFD semi-static / dynamic DL symbol, and / or an SBFD dynamic FL symbol. In other words, the UE may transmit the PUSCH or PUSCH repetition to any subsequent slot / subslot where it does not overlap with a UL symbol or FL symbol in non-SBFD operation and does not overlap with the DL subband in an UL symbol, DL symbol, and / or FL symbol in SBFD operation.Alternatively, the UE may transmit the PUSCH or PUSCH repetition in any subsequent symbol, subframe, frame, or any other time unit that does not overlap with non-SBFD semistatic / dynamic UL symbols (or non-SBFD dynamic flexible symbols) and does not overlap with any DL subband in SBFD semistatic / dynamic UL symbols, SBFD semistatic / dynamic DL symbols, and / or SBFD dynamic FL symbols. 【0252】 Furthermore, additional conditions may be required for such deferrals. For example, a deferral may be performed only when an SBFD operation instruction is set by RRC. In other words, if an SBFD operation is dynamically notified to the UE, the deferral does not apply. That is, if an SBFD operation is dynamically notified to the UE, the UE may refrain from transmitting PUSCH or PUSCH repetitions. For example, if an SBFD operation is notified to the UE by DCI, the UE may refrain from transmitting PUSCH or PUSCH repetitions in subsequent symbols, slots, etc., that do not overlap with any non-SBFD UL symbols (or non-SBFD dynamic flexible symbols) but overlap with the DL subband in SBFD UL symbols, SBFD DL symbols, and / or SBFD FL symbols. 【0253】 Furthermore, which of the above-mentioned Alts to apply may be explicitly or implicitly specified by the specification, semi-statically set by RRC, dynamically notified by DCI, or determined by rules. For example, a parameter indicating which Alt to apply may be sent in at least one of RRC, DCI, and MAC CE (Medium Access Control Control Element). 【0254】 Here, if a rate-matching-based solution such as Alt 1-3 or Alt 2-2 described above is applied, the Transport Block Size (TBS) needs to be considered. For example, the TBS may be determined according to options A and / or B below. 【0255】 <Option A> In Option A, TBS is, i) Non-SBFD semi-static / dynamic DL symbols (or non-SBFD dynamic FL symbols), SSB symbols or type-0 CORESET symbols, ii) SBFD semi-static / dynamic UL symbols, SBFD semi-static / dynamic DL symbols, and / or SBFD semi-static / dynamic FL symbols, and / or iii) DL resource blocks (RBs) in SBFD semistatic / dynamic UL symbols, SBFD semistatic / dynamic DL symbols, and / or SBFD semistatic / dynamic FL symbols, This may be determined based on the number of resource elements (REs) after excluding them. 【0256】 <Option B> In Option B, the TBS may be determined based on the number of REs notified by the Time Domain Resource Allocation (TDRA) and Frequency Domain Resource Allocation (FDRA). 【0257】 For example, for a PUSCH iteration, if option A is applied, the number of REs for TBS calculation may differ for different iterations. In such cases, the TBS for each iteration may be determined by the TBS calculated for the first PUSCH iteration and / or the maximum / minimum / average value of the TBS values calculated for all iterations. 【0258】 Which option to apply may be specified explicitly or implicitly by the specification, semi-statically set by RRC, dynamically notified by DCI, or determined by rules. For example, a parameter indicating which option should be applied may be transmitted in at least one of RRC, DCI, and MAC CE. For example, the UE may receive configuration information regarding options A and B via RRC and be dynamically notified by DCI which option A or B should be applied. 【0259】 (UE operation in Proposal 4) In Proposal 4, the UE may control the transmission operation of the uplink data channel depending on whether the downlink time unit in a non-time-frequency-division duplex operation such as non-SBFD operation and / or the time unit in a time-frequency-division duplex operation such as SBFD operation overlap with the uplink data channel, and the transmission operation of the uplink data channel may be performed by the controlled transmission operation. Here, the time-frequency-division duplex operation may be SBFD, and the downlink time unit in a non-time-frequency-division duplex operation may be a DL symbol, minislot, slot, or any other time unit in a non-SBFD operation, specifically a non-SBFD semistatic / dynamic DL symbol and / or a non-SBFD dynamic FL symbol. Also, the time unit in a time-frequency-division duplex operation may be a UL, DL or FL symbol, minislot, slot, or any other time unit in SBFD operation, specifically an SBFD semistatic / dynamic UL symbol, an SBFD semistatic / dynamic DL symbol, and / or an SBFD dynamic FL symbol. Furthermore, the uplink data channel may be, for example, PUSCH, PUSCH repeat, etc. 【0260】 Specifically, when an uplink data channel overlaps with a downlink time unit or flexible time unit in non-SBFD operation, the UE may refrain from transmitting the uplink data channel. Alternatively, when an uplink data channel overlaps with a downlink time unit or flexible time unit in non-SBFD operation, the UE may transmit the uplink data channel in a time unit that does not overlap with a downlink time unit in non-SBFD operation. That is, the UE may postpone the transmission of a PUSCH or PUSCH repetition to a slot where the symbols included in the time-domain resource for transmitting the PUSCH or PUSCH repetition do not overlap with non-SBFD semistatic / dynamic DL symbols. 【0261】 Furthermore, when an uplink data channel overlaps with a time unit in SBFD operation, the UE may control the transmission operation of the uplink data channel regardless of whether the uplink data channel overlaps with a downlink subband in that time unit. For example, the UE may choose not to transmit the uplink data channel. Alternatively, the UE may transmit the uplink data channel in time units that do not overlap with downlink time units or flexible time units in non-SBFD operation, and that do not overlap with uplink time units, downlink time units, and / or flexible time units in SBFD operation. That is, the UE may postpone the transmission of a PUSCH or PUSCH repetition to a slot where the PUSCH or PUSCH repetition resource does not overlap with non-SBFD semistatic / dynamic DL symbols and does not overlap with SBFD semistatic / dynamic UL symbols, SBFD semistatic / dynamic DL symbols, and / or SBFD dynamic FL symbols. Alternatively, the UE may rate match the uplink data channel to time units other than time units in SBFD operation. In other words, the UE may rate-match PUSCH or PUSCH repeats on symbols other than SBFD semistatic / dynamic UL symbols, SBFD semistatic / dynamic DL symbols, and / or SBFD dynamic FL symbols. 【0262】 Furthermore, when an uplink data channel overlaps with a time unit in SBFD operation, the UE may control the transmission operation of the uplink data channel depending on whether or not the uplink data channel overlaps with the downlink subband in that time unit. For example, if the uplink data channel does not overlap with the downlink subband in that time unit, the UE may transmit the uplink data channel on the configured / announced resource. On the other hand, if the uplink data channel overlaps with the downlink subband in that time unit, the UE may refrain from transmitting the uplink data channel. Alternatively / furthermore, the UE may rate match the uplink data channel on the DL subband in the time unit in SBFD operation. Alternatively / furthermore, the UE may transmit the uplink data channel in time units that do not overlap with the downlink time unit or flexible time unit in non-SBFD operation, and that do not overlap with the uplink time unit, downlink time unit, and / or flexible time unit in SBFD operation. In other words, the UE may postpone the transmission of PUSCH or PUSCH Repeat to a slot or minislot where the resource for PUSCH or PUSCH Repeat does not overlap with non-SBFD semistatic / dynamic DL symbols and does not overlap with SBFD semistatic / dynamic UL symbols, SBFD semistatic / dynamic DL symbols, and / or SBFD dynamic FL symbols. 【0263】 (gNB operation in Proposal 4) In Proposal 4, the gNB may control the receiving operation of the uplink data channel in either or both of the downlink time units in non-time-frequency-division duplexing operations such as non-SBFD operation, and the time units in time-frequency-division duplexing operations such as SBFD operation, and the receiving operation of the uplink data channel may be performed by the controlled receiving operation. Here, the time-frequency-division duplexing may be SBFD, and the downlink time units in non-time-frequency-division duplexing operations may be DL symbols, minislots, slots, or any other time units in non-SBFD operation, specifically non-SBFD semistatic / dynamic DL symbols and / or non-SBFD dynamic FL symbols. Also, the time units in time-frequency-division duplexing operations may be UL, DL or FL symbols, minislots, slots, or any other time units in SBFD operation, specifically SBFD semistatic / dynamic UL symbols, SBFD semistatic / dynamic DL symbols, and / or SBFD dynamic FL symbols. The uplink data channel may be, for example, PUSCH, PUSCH repeat, etc. 【0264】 Regarding push enhancements for time-frequency division duplex operations such as SBFD operation as described above, UE capability information may be provided indicating whether the UE supports push enhancements for time-frequency division duplex operations. Furthermore, UE capability information regarding push transmissions for time-frequency division duplex operations such as SBFD operation may also be provided. Specifically, UE capability information may be provided indicating whether the UE supports s-TRP / m-TRP push repetition type A for time-frequency division duplex operations. If the UE supports push enhancements for time-frequency division duplex operations, it may send UE capability information to the gNB indicating that it supports push enhancements for SBFD operation. Upon receiving such UE capability information, the gNB can receive pushes from the UE in accordance with the push enhancements for time-frequency division duplex operations. 【0265】 According to Proposal 4 described above, Push enhancements can be achieved for time-frequency division duplex operations such as SBFD operation. 【0266】 [Proposal 5] Proposal 5 describes a Push enhancement for time-frequency division duplexing operations such as SBFD operation. Specifically, Push repetition type B is enhanced for SBFD operation as follows. The following invalid symbols will be added. (Option 0) Regardless of whether SBFD or non-SBFD operation is enabled, the DL symbol is set to semi-static. (Option 1) Semi-static non-SBFD DL symbols (Option 2) Semi-static SBFD / non-SBFD DL symbols, UL / FL symbols that overlap with DL subbands. If the actual repetition overlaps with a non-SBFD FL symbol, the UE does not send a PUSCH. (Alt 1) UE does not transmit PUSCH, regardless of whether there is overlap with the DL subband. (Alt 2) UE transmits PUSCH if it overlaps with the DL subband, and if PUSCH does not overlap with the DL subband. <Alt 2-1> The UE does not send a PUSCH. <Alt 2-2> UE rate-matches PUSCH to the UL subband. 【0267】 Section 6.1.2.1 of TS38.214 specifies that for PUSCH repeat type B, after determining the invalid symbols for PUSCH repeat type B transmissions for each nominal repeat, the remaining symbols are considered as potentially valid symbols for PUSCH repeat type B transmissions. Proposal 5 suggests that for s-TRP PUSCH repeat type B or m-TRP PUSCH repeat type B in SBFD and non-SBFD operation, the invalid symbols for PUSCH repeat type B segmentation may include the following options 0 to 2 symbols, along with the SSB symbol, type-0 CORESET symbol, and invalid symbols notified by the RRC parameter invalidSymbolPattern. 【0268】 (Option 0) In option 0, invalid symbols for s-TRP PUSCH repeat type B or m-TRP PUSCH repeat type B may include semi-static DL symbols, whether they are SBFD symbols or non-SBFD symbols. 【0269】 (Option 1) In Option 1, invalid symbols for s-TRP PUSCH repeat type B or m-TRP PUSCH repeat type B may include non-SBFD semistatic DL symbols. 【0270】 (Option 2) In Option 2, invalid symbols for s-TRP PUSCH repeat type B or m-TRP PUSCH repeat type B may include non-SBFD semistatic and / or dynamic DL symbols, SBFD semistatic and / or dynamic DL symbols (if the PUSCH repeat overlaps with the DL subband in the SBFD semistatic and / or dynamic DL symbol), SBFD semistatic and / or dynamic UL symbols (if the PUSCH repeat overlaps with the DL subband in the SBFD semistatic and / or dynamic DL symbol), and / or SBFD semistatic and / or dynamic FL symbols (if the PUSCH repeat overlaps with the DL subband in the SBFD semistatic and / or dynamic FL symbol). 【0271】 Here, as a variation, the choice of which option to apply may depend on whether the SBFD operation (and / or DL / UL subband allocation) is dynamically notified or RRC configured. For example, if the SBFD operation (DL / UL subband allocation) is dynamically notified, option 1 may be applied. On the other hand, if the SBFD operation (and / or DL / UL subband allocation) is RRC configured, option 2 may be applied. 【0272】 Section 6.1.2.1 of TS38.214 specifies that if the number of potentially valid symbols for a PUSCH repetition type B transmission is greater than 0 for a nominal repetition, then the nominal repetition consists of one or more actual repetitions, where each actual repetition consists of a contiguous set of all potentially valid symbols available for a PUSCH repetition type B transmission within the slot. Proposal 5 allows the UE to refrain from transmitting an actual PUSCH repetition if, after segmentation, the symbols included in the resources for transmitting an actual PUSCH repetition overlap with non-SBFD dynamic FL symbols for s-TRP PUSCH repetition type B or m-TRP PUSCH repetition type B in SBFD and non-SBFD operation. 【0273】 If segmentation is based on Option 1 described above, and for each actual repeat after segmentation, if the symbols included in the resource for sending the actual PUSCH repeat overlap with at least one SBFD semistatic / dynamic UL symbol, at least one SBFD semistatic / dynamic DL symbol, and / or at least one SBFD semistatic / dynamic FL symbol, the UE may operate according to Alt 1 or Alt 2 below. 【0274】 (Alt 1) In Alt 1, if an invalid symbol for segmentation includes a non-SBFD semistatic DL symbol, and the symbols included in the resource for transmitting an actual PUSCH repetition overlap with at least one SBFD semistatic / dynamic UL symbol, at least one SBFD semistatic / dynamic DL symbol, and / or at least one SBFD semistatic / dynamic FL symbol, the UE may refrain from transmitting the actual PUSCH repetition, regardless of whether it overlaps with the DL subband. 【0275】 (Alt 2) In Alt 2, if invalid symbols for segmentation include non-SBFD semistatic DL symbols, and the symbols included in the resource for transmitting the actual PUSCH repetitions overlap with at least one SBFD semistatic / dynamic UL symbol, at least one SBFD semistatic / dynamic DL symbol, and / or at least one SBFD semistatic / dynamic FL symbol, the UE may behave as follows, depending on the overlap with the DL subband: 【0276】 Specifically, if the symbols included in the resource for transmitting the actual PUSCH repetition do not overlap with SBFD semistatic / dynamic UL symbols, SBFD semistatic / dynamic DL symbols, and / or SBFD semistatic / dynamic FL symbols, the UE may transmit the PUSCH repetition of that embodiment. 【0277】 On the other hand, if the symbols included in the resources for transmitting the actual PUSCH repetition overlap with SBFD semistatic / dynamic UL symbols, SBFD semistatic / dynamic DL symbols, and / or SBFD semistatic / dynamic FL symbols, the UE may control the transmission operation according to Alt 2-1 or Alt 2-2 below. 【0278】 <Alt 2-1> Alt 2-1 states that if the symbols included in the resource for transmitting an actual PUSCH repeat overlap with SBFD semistatic / dynamic UL symbols, SBFD semistatic / dynamic DL symbols, and / or SBFD semistatic / dynamic FL symbols, the UE may refrain from transmitting that actual PUSCH repeat. 【0279】 <Alt 2-2> In Alt 2-2, if the symbols included in the resource for transmitting an actual PUSCH repetition overlap with SBFD semistatic / dynamic UL symbols, SBFD semistatic / dynamic DL symbols, and / or SBFD semistatic / dynamic FL symbols, the UE may rate-match the symbols included in the resource for transmitting the actual PUSCH repetition on the UL subband of the SBFD semistatic / dynamic UL symbols, SBFD semistatic / dynamic DL symbols, and / or SBFD semistatic / dynamic FL symbols, and / or on non-SBFD semistatic / dynamic UL / FL symbols, if present. 【0280】 Furthermore, which of the above-mentioned Alts to apply may be explicitly or implicitly specified by the specification, semi-statically set by RRC, dynamically notified by DCI, or determined by rules. For example, a parameter indicating which Alt to apply may be sent in at least one of RRC, DCI, and MAC CE (Medium Access Control Control Element). 【0281】 Here, TBS may be determined based on the following options A and / or B. 【0282】 (Option A) In Option A, the TBS may be determined according to the rules of Rel-16. Specifically, the TBS may be determined based on the Notice / Established TDRA and FDRA. 【0283】 (Option B) In Option B, TBS may be determined by taking into account the actual resource elements (REs) of the actual PUSCH iterations. Here, for each actual iteration, the actual number of REs is: • Non-SBFD semi-static / dynamic DL symbols (and non-SBFD dynamic FL symbols) · SBFD semi-static / dynamic UL symbols, SBFD semi-static / dynamic DL symbols, and / or SBFD semi-static / dynamic FL symbols, and / or DL resource blocks (RBs) in SBFD semistatic / dynamic UL symbols, SBFD semistatic / dynamic DL symbols, and / or SBFD semistatic / dynamic FL symbols. The number of REs after excluding may be determined. Here, the maximum, minimum, or average value of the actual number of REs may be used for the TBS calculation. 【0284】 Which option to apply may be specified explicitly or implicitly by the specification, semi-statically set by RRC, dynamically notified by DCI, or determined by rules. For example, a parameter indicating which option should be applied may be transmitted in at least one of RRC, DCI, and MAC CE. For example, the UE may receive configuration information regarding options A and B via RRC and be dynamically notified by DCI which option A or B should be applied. 【0285】 (Variation of Proposal 4 / 5) The combined operation of SBFD and m-TRP PUSCH does not need to be supported. 【0286】 <Specific Example 1> In specific example 1, the UE does not need to assume / determine / decide / interpret that SBFD operation (and / or DL / UL subband allocation) is notified / configured for the serving cell / bandwidth portion (BWP), and that two SRS resource sets are simultaneously configured in the serving cell / BWP using srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2. 【0287】 <Specific Example 2> In specific example 2, the UE does not need to assume / judge / decide / interpret that SBFD operation (and / or DL / UL subband allocation) is notified / configured for the serving cell / bandwidth portion (BWP), that two SRS resource sets are simultaneously configured in the serving cell / BWP in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2, and that push-RepTypeIndicatorDCI-0-1 or push-RepTypeIndicatorDCI-0-2 is set to push-RepTypeA or not. 【0288】 <Specific Example 3> In specific example 3, the UE does not need to assume / determine / decide / interpret that SBFD operation (and / or DL / UL subband allocation) is notified / configured for the serving cell / bandwidth portion (BWP), that two SRS resource sets are simultaneously configured in the serving cell / BWP using srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2, and that push-RepTypeIndicatorDCI-0-1 or push-RepTypeIndicatorDCI-0-2 is set to push-RepTypeB. 【0289】 <Specific Example 4> In specific example 4, if SBFD operation (and / or DL / UL subband allocation) is notified / configured for a serving cell / bandwidth portion (BWP), and two SRS resource sets are configured in the serving cell / BWP using srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2, the UE may use only the first / second SRS resource set for PUSCH transmissions. 【0290】 <Specific Example 5> In specific example 5, if SBFD operation (and / or DL / UL subband allocation) is notified / configured for a serving cell / bandwidth portion (BWP), and two SRS resource sets are configured in the serving cell / BWP in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2, and push-RepTypeIndicatorDCI-0-1 or push-RepTypeIndicatorDCI-0-2 is set to push-RepTypeA or not, then the UE may use only the first / second SRS resource set for PUSCH transmissions. 【0291】 <Specific Example 6> In specific example 6, if SBFD operation (and / or DL / UL subband allocation) is notified / configured for a serving cell / bandwidth portion (BWP), and two SRS resource sets are configured in the serving cell / BWP using srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2, and simultaneously push-RepTypeIndicatorDCI-0-1 or push-RepTypeIndicatorDCI-0-2 is set to push-RepTypeB, then the UE may use only the first / second SRS resource set for PUSCH transmissions. 【0292】 (UE operation in Proposal 5) In Proposal 5, the UE may control the transmission operation of the uplink data channel depending on whether the downlink time unit in a non-time-frequency-division duplex operation such as non-SBFD operation and / or the time unit in a time-frequency-division duplex operation such as SBFD operation overlap with the uplink data channel, and may perform the transmission operation of the uplink data channel by the controlled transmission operation. Here, the time-frequency-division duplex operation may be SBFD, and the downlink time unit in a non-time-frequency-division duplex operation may be a DL symbol, minislot, slot, or any other time unit in a non-SBFD operation, specifically a non-SBFD semistatic / dynamic DL symbol and / or a non-SBFD dynamic FL symbol. Also, the time unit in a time-frequency-division duplex operation may be a UL, DL or FL symbol, minislot, slot, or any other time unit in SBFD operation, specifically an SBFD semistatic / dynamic UL symbol, an SBFD semistatic / dynamic DL symbol, and / or an SBFD dynamic FL symbol. Furthermore, the uplink data channel may be, for example, PUSCH, PUSCH repeat, etc. 【0293】 Specifically, the UE may include non-SBFD downlink time units or SBFD time units as invalid time units for uplink data channel repetition transmissions. The UE may also determine invalid time units for uplink data channel repetition transmissions depending on whether SBFD is dynamically advertised or semi-statically configured. Furthermore, the UE may control the actual repetition transmission behavior depending on whether there is overlap with the downlink subband when symbols included in the segmented resources for the actual repetition transmission of the uplink data channel overlap with SBFD time units. 【0294】 (gNB operation in Proposal 5) In Proposal 5, the gNB may control the receiving operation of the uplink data channel in either or both of the downlink time units in non-time-frequency-division duplexing operations such as non-SBFD operation, and the time units in time-frequency-division duplexing operations such as SBFD operation, and the receiving operation of the uplink data channel may be performed by the controlled receiving operation. Here, the time-frequency-division duplexing may be SBFD, and the downlink time units in non-time-frequency-division duplexing operations may be DL symbols, minislots, slots, or any other time units in non-SBFD operation, specifically non-SBFD semistatic / dynamic DL symbols and / or non-SBFD dynamic FL symbols. The time units in time-frequency-division duplexing operations may be UL, DL or FL symbols, minislots, slots, or any other time units in SBFD operation, specifically SBFD semistatic / dynamic UL symbols, SBFD semistatic / dynamic DL symbols, and / or SBFD dynamic FL symbols. The uplink data channel may be, for example, PUSCH, PUSCH repeat, etc. 【0295】 (UE Capability) Regarding push enhancements for time-frequency division duplex operations such as SBFD operation as described above, UE capability information may be specified indicating whether the UE supports push enhancements for time-frequency division duplex operations. Furthermore, UE capability information regarding push transmissions of multiple transmit / receive points for time-frequency division duplex operations such as SBFD operation may also be specified. Specifically, UE capability information may be specified indicating whether the UE supports s-TRP / m-TRP push repetition type B for SBFD operation. If the UE supports push enhancements for time-frequency division duplex operations, it may transmit UE capability information to the gNB indicating that it supports push enhancements for time-frequency division duplex operations. Upon receiving such UE capability information, the gNB can receive pushes from the UE in accordance with the push enhancements for time-frequency division duplex operations. 【0296】 According to Proposal 5 described above, Push enhancements can be achieved for time-frequency division duplexing operations such as SBFD operation. 【0297】 (PUCCH in Rel-15 / 16 / 17) According to Rel-15 / 16, a non-repeating PUCCH that overlaps with a semi-static DL symbol is not to be sent. In other words, for a symbol set of a slot notified to the UE as a downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, if the symbols included in the resource for sending PUSCH, PUCCH, PRACH, or SRS overlap even partially with the symbol set of that slot, the UE is not to send PUSCH, PUCCH, PRACH, or SRS. 【0298】 Furthermore, it is stipulated that PUCCH signals without repetition that overlap with dynamic DL or FL symbols will not be transmitted. In other words, if the upper layer has configured the UE to transmit PUSCH, PUCCH, PRACH, or SRS in a slot's symbol set, and the UE detects a DCI format 2_0 with a slot format value other than 255 that notifies the UE of a slot format with a subset of symbols from that symbol set as downlink or flexible, or if the UE detects a DCI format that notifies the UE to receive PDSCH or CSI-RS in at least one symbol in that symbol set, and certain conditions are met, the UE is stipulated to cancel the transmission of PUSCH, PUCCH, PRACH, or SRS in that symbol set. 【0299】 Rel-15 / 16 NR specifies that non-repeating PUCCHs that overlap with semi-static DL symbols are deferred to a slot where the PUCCH's resources no longer overlap with the semi-static DL symbols. For example, as shown in Figure 25, the HARQ-ACK PUCCHs corresponding to PDSCH#1 and #2 overlap with DL slots and are therefore deferred to UL slots. 【0300】 Furthermore, Rel-15 / 16 NR specifies that PUCCHs that overlap with dynamic DL or FL symbols will not be transmitted. 【0301】 Furthermore, Rel-17 NR supports the deferral of SPS HARQ-ACKs due to TDD collisions. Specifically, it is stipulated that if an SPS HARQ-ACK overlaps with a semi-static DL symbol, SSB symbol, or CORESET #0 symbol, the SPS HARQ-ACK will be deferred. SPS HARQ-ACK deferral can be enabled for SPS configurations. 【0302】 Here, the target slot / subslot for the deferral is defined as the first available slot / subslot where the PUCCH resource does not overlap with a semi-static DL symbol, SSB symbol, or CORESET #0 symbol, and the condition "K1_max_def > K1 + K_def" is satisfied. Here, K_def is the number of slots / subslots from the first PUCCH slot to the target PUCCH slot, and K1_max_def is set for each SPS configuration index. For example, as shown in Figure 26, the SPS HARQ-ACK for SPS PDSCH #1 is deferred to the target PUCCH slot because the corresponding first PUCCH overlaps with a semi-static DL slot. 【0303】 [Considerations regarding PUCCH enhancements for SBFD operation] The following is being considered regarding the SBFD operation of Rel-18. • SBFD operation in DL symbols, i.e., DL and UL subbands in DL symbols • SBFD operation in UL symbols, i.e., DL and UL subbands in UL symbols • SBFD operation in Flexible (FL) symbols, i.e., DL and UL subbands in FL symbols. 【0304】 Here, if SBFD operation is supported or enabled for DL symbols, non-repeating PUCCHs that overlap with DL symbols do not necessarily have to be dropped. Therefore, the rules for TDD collisions in Rel-15 / 16 / 17 may need to be updated to accommodate SBFD operation. For example, in the specific example shown in Figure 27, according to the rules of Rel-15 / 16, non-repeating PUCCHs in the illustrated slot are dropped, and repeating PUCCHs are deferred. According to the rules of Rel-17, SPS HARQ-ACK PUCCHs in the illustrated slot are deferred. 【0305】 [Proposal 6] Proposal 6 describes a PUCCH enhancement for time-frequency division duplexing operations such as SBFD operation. Specifically, the PUCCH rules for TDD collisions in SBFD operation are enhanced as follows. Case 1: When PUCCH overlaps with a non-SBFD DL symbol, SSB, or Type-0 CORESET. <alt-a> The UE does not send a PUCCH. <Alt B> The UE will postpone sending the PUCCH. Case 2: When PUCCH overlaps with a non-SBFD DL symbol. The UE does not send a PUCCH. Case 3: When PUCCH overlaps with SBFD DL symbols <Alt 1> The UE operates according to Alt 1-1 to 1-2 below, regardless of whether or not there is overlap with the DL subband. <<Alt 1-1> > The UE does not send a PUCCH. <<Alt 1-2> > The UE will postpone sending the PUCCH. <Alt 2> The UE operates according to Alt 2-1 to 2-3 below, depending on whether or not there is overlap with the DL subband. <<Alt 2-1> > The UE does not send a PUCCH. <<Alt 2-2> > UE rate-matches PUCCH to the UL subband. <<Alt 2-3> > The UE will postpone sending the PUCCH. 【0306】 For s-TRP PUCCH, s-TRP PUCCH repetition, or m-TRP PUCCH repetition, the UE may control the PUCCH transmission operation in accordance with the following cases 1 to 3. Case 1: A symbol included in the resource for sending PUCCH or PUCCH repeat overlaps with at least one non-SBFD semistatic DL symbol, SSB symbol, or type-0 CORESET symbol. Case 2: A symbol included in the resource for sending PUCCH or PUCCH repeat overlaps with at least one non-SBFD dynamic DL / FL symbol. Case 3: The symbols included in the resource for transmitting PUCCH or PUCCH repetition do not overlap with any non-SBFD semistatic / dynamic DL symbols (or non-SBFD dynamic FL symbols), but overlap with at least one SBFD semistatic / dynamic UL symbol, at least one SBFD semistatic / dynamic DL symbol, and / or at least one SBFD semistatic / dynamic FL symbol. 【0307】 (Case 1) If, as in Case 1, the symbols included in the resource for sending PUCCH or PUCCH repetition overlap with at least one non-SBFD semistatic DL symbol, SSB symbol, or type-0 CORESET symbol, the UE may act according to Alt-A or Alt-B below. 【0308】 <Case 1: Alt-A> In Alt-A, if a symbol included in the resource for transmitting a PUCCH or PUCCH repeat overlaps with at least one non-SBFD semistatic DL symbol, SSB symbol, or type-0 CORESET symbol, the UE may refrain from transmitting the PUCCH or PUCCH repeat. In other words, the UE may refrain from transmitting a PUCCH or PUCCH repeat that overlaps with a DL symbol in non-SBFD operation. 【0309】 As an alternative, PUCCH repetitions that are not transmitted by overlapping with at least one non-SBFD semistatic DL symbol, SSB symbol, or type-0 CORESET symbol may or may not be counted in the repetition count. 【0310】 <Case 1: Alt-B> In Alt-B, if the symbols included in the resource for transmitting a PUCCH or PUCCH repetition overlap with at least one non-SBFD semistatic DL symbol, SSB symbol, or type-0 CORESET symbol, the UE may defer the PUCCH or PUCCH repetition to a slot / subslot where the symbols included in the resource for transmitting the PUCCH or PUCCH repetition do not overlap with the non-SBFD semistatic DL symbol, SSB symbol, or type-0 CORESET symbol. 【0311】 (Case 2) As in Case 2, if a symbol included in the resource for transmitting a PUCCH or PUCCH repeat overlaps with at least one non-SBFD dynamic DL / FL symbol, the UE may refrain from transmitting that PUCCH or PUCCH repeat. In other words, the UE may refrain from transmitting a PUCCH or PUCCH repeat that overlaps with a DL / FL symbol in non-SBFD operation. 【0312】 As an alternative, a PUCCH repeat that is not transmitted by overlapping with at least one non-SBFD dynamic DL / FL symbol may or may not be counted in the repeat count. 【0313】 (Case 3) If, as in Case 3, the symbols included in the resource for sending PUCCH or PUCCH repetition do not overlap with any non-SBFD semistatic / dynamic DL symbols (or non-SBFD dynamic FL symbols), but overlap with at least one SBFD semistatic / dynamic UL symbol, at least one SBFD semistatic / dynamic DL symbol, and / or at least one SBFD semistatic / dynamic FL symbol, the UE may operate according to Alt 1 and / or Alt 2 below. 【0314】 <Case 3: Alt 1> In Alt 1, if the symbols included in the resource for transmitting PUCCH or PUCCH repetitions do not overlap with any non-SBFD semistatic / dynamic DL symbols (or non-SBFD dynamic FL symbols), but overlap with at least one SBFD semistatic / dynamic UL symbol, at least one SBFD semistatic / dynamic DL symbol, and / or at least one SBFD semistatic / dynamic FL symbol, the UE may operate according to Alt 1-1 and / or Alt 1-2 below, regardless of whether there is overlap with the DL subband. 【0315】 <<Case 3: Alt 1-1>> In Alt 1-1, if a symbol included in the resource for transmitting a PUCCH or PUCCH repeat does not overlap with any non-SBFD semistatic / dynamic DL symbol (or non-SBFD dynamic FL symbol), but overlaps with at least one SBFD semistatic / dynamic UL symbol, at least one SBFD semistatic / dynamic DL symbol, and / or at least one SBFD semistatic / dynamic FL symbol, the UE may refrain from transmitting the PUCCH or PUCCH repeat. In other words, the UE may refrain from transmitting a PUCCH or PUCCH repeat that overlaps with a UL / DL / FL symbol in SBFD operation. 【0316】 As an alternative, PUCCH repetitions that are not transmitted by overlapping with SBFD semistatic / dynamic UL symbols, SBFD semistatic / dynamic DL symbols, and / or SBFD semistatic / dynamic FL symbols may or may not be counted in the repetition count. 【0317】 <<Case 3: Alt 1-2>> In Alt 1-2, if the symbols included in the resource for transmitting a PUCCH or PUCCH repeat do not overlap with any non-SBFD semistatic / dynamic DL symbols (or non-SBFD dynamic FL symbols), but overlap with at least one SBFD semistatic / dynamic UL symbol, at least one SBFD semistatic / dynamic DL symbol, and / or at least one SBFD semistatic / dynamic FL symbol, the UE may defer the PUCCH or PUCCH repeat to a slot / subslot where the symbols included in the resource for transmitting the PUCCH or PUCCH repeat do not overlap with any non-SBFD semistatic DL symbols (or non-SBFD dynamic FL symbols), and do not overlap with any SBFD semistatic / dynamic UL symbols, SBFD semistatic / dynamic DL symbols, and / or SBFD semistatic / dynamic FL symbols. 【0318】 Furthermore, additional conditions may be required for such deferrals. For example, a deferral may be performed only when an SBFD operation instruction is set by RRC. In other words, if an SBFD operation is dynamically notified to the UE, the deferral does not need to be applied. That is, if an SBFD operation is dynamically notified to the UE, the UE may refrain from sending PUCCH or PUCCH repetitions. For example, if an SBFD operation is notified to the UE by DCI, the UE may refrain from sending PUCCH or PUCCH repetitions in subsequent symbols, slots, etc., that do not overlap with any non-SBFD DL / FL symbols but overlap with SBFD UL symbols, SBFD DL symbols, and / or SBFD FL symbols. 【0319】 <Case 3: Alt 2> In Alt 2, if the symbols included in the resource for transmitting PUCCH or PUCCH Repetition do not overlap with any non-SBFD semistatic / dynamic DL symbols (or non-SBFD dynamic FL symbols), but overlap with at least one SBFD semistatic / dynamic UL symbol, at least one SBFD semistatic / dynamic DL symbol, and / or at least one SBFD semistatic / dynamic FL symbol, the UE may control the transmission operation of PUCCH or PUCCH Repetition depending on whether or not there is overlap with the DL subband. 【0320】 Specifically, if the symbols included in the resource for transmitting PUCCH or PUCCH Repetition do not overlap with any non-SBFD semistatic / dynamic DL symbols (or non-SBFD dynamic FL symbols), but overlap with at least one SBFD semistatic / dynamic UL symbol, at least one SBFD semistatic / dynamic DL symbol, and / or at least one SBFD semistatic / dynamic FL symbol, and the symbols included in the resource for transmitting PUCCH or PUCCH Repetition do not overlap with the DL subband in the SBFD semistatic / dynamic UL symbol, SBFD semistatic / dynamic DL symbol, and / or SBFD dynamic FL symbol, then the UE may transmit the PUCCH or PUCCH Repetition in the advertised or configured resource. Furthermore, the resource may be defined by the specification, semistatically configured by RRC settings, dynamically advertised by DCI notifications, or determined according to rules. Furthermore, the resource may be defined, configured, advertised, or determined explicitly or implicitly. 【0321】 On the other hand, if the symbols included in the resource for transmitting PUCCH or PUCCH repeat do not overlap with any non-SBFD semistatic / dynamic DL symbols (or non-SBFD dynamic FL symbols), but overlap with at least one SBFD semistatic / dynamic UL symbol, at least one SBFD semistatic / dynamic DL symbol, and / or at least one SBFD semistatic / dynamic FL symbol, and the symbols included in the resource for transmitting PUCCH or PUCCH repeat overlap with the DL subband in the SBFD semistatic / dynamic UL symbol, SBFD semistatic / dynamic DL symbol, and / or SBFD dynamic FL symbol, the UE may operate according to Alt 2-1, Alt 2-2, and / or Alt 2-3 below. 【0322】 <<Case 3: Alt 2-1>> Alt 2-1 states that if the symbols included in the resource for transmitting a PUCCH or PUCCH repeat do not overlap with any non-SBFD semistatic / dynamic DL symbols (or non-SBFD dynamic FL symbols), but overlap with at least one SBFD semistatic / dynamic UL symbol, at least one SBFD semistatic / dynamic DL symbol, and / or at least one SBFD semistatic / dynamic FL symbol, and the symbols included in the resource for transmitting a PUCCH or PUCCH repeat overlap with the DL subband in an SBFD semistatic / dynamic UL symbol, an SBFD semistatic / dynamic DL symbol, and / or an SBFD dynamic FL symbol, the UE may refrain from transmitting the PUCCH or PUCCH repeat. 【0323】 As an alternative, PUCCH repetitions that were not transmitted due to overlap with the DL subband in SBFD semistatic / dynamic UL symbols, SBFD semistatic / dynamic DL symbols, and / or SBFD dynamic FL symbols may or may not be counted in the repetition count. 【0324】 <<Alt 2-2> > Alt 2-2 states that if the symbols included in the resource for transmitting PUCCH or PUCCH repetition do not overlap with any non-SBFD semistatic / dynamic DL symbols (or non-SBFD dynamic FL symbols), but overlap with at least one SBFD semistatic / dynamic UL symbol, at least one SBFD semistatic / dynamic DL symbol, and / or at least one SBFD semistatic / dynamic FL symbol, and the symbols included in the resource for transmitting PUCCH or PUCCH repetition overlap with the DL subband of an SBFD semistatic / dynamic UL symbol, an SBFD semistatic / dynamic DL symbol, and / or an SBFD dynamic FL symbol, then the UE may rate match the symbols included in the resource for transmitting PUCCH or PUCCH repetition on the DL subband of an SBFD semistatic / dynamic UL symbol, an SBFD semistatic / dynamic DL symbol, and / or an SBFD dynamic FL symbol, and on non-SBFD semistatic / dynamic DL / FL symbols, if present. 【0325】 <<Alt 2-3> > Alt 2-3 is a case where the symbols included in the resource for transmitting PUCCH or PUCCH repeat do not overlap with any non-SBFD semistatic / dynamic DL symbols (or non-SBFD dynamic FL symbols), but overlap with at least one SBFD semistatic / dynamic UL symbol, at least one SBFD semistatic / dynamic DL symbol, and / or at least one SBFD semistatic / dynamic FL symbol, and the symbols included in the resource for transmitting PUCCH or PUCCH repeat are SBFD semistatic / dynamic UL symbols, SBFD semistatic If a PUCCH or PUCCH repetition overlaps with the DL subband in a sci-fi / dynamic DL symbol and / or an SBFD dynamic FL symbol, the UE may defer the PUCCH or PUCCH repetition to a slot / subslot where the symbols included in the resource for transmitting the PUCCH or PUCCH repetition do not overlap with non-SBFD semistatic / dynamic UL symbols (or non-SBFD dynamic flexible symbols) and do not overlap with any DL subband in an SBFD semistatic / dynamic UL symbol, SBFD semistatic / dynamic DL symbol, and / or an SBFD dynamic FL symbol. In other words, the UE may transmit the PUCCH or PUCCH repetition to any subsequent slot / subslot where it does not overlap with UL symbols or FL symbols in non-SBFD operation and does not overlap with the DL subband in an UL symbol, DL symbol, and / or FL symbol in SBFD operation.Alternatively, the UE may transmit the PUCCH or PUCCH repetition in any subsequent time unit, such as a symbol, subslot, subframe, or frame, that does not overlap with non-SBFD semistatic / dynamic UL symbols (or non-SBFD dynamic flexible symbols) and does not overlap with any DL subband in SBFD semistatic / dynamic UL symbols, SBFD semistatic / dynamic DL symbols, and / or SBFD dynamic FL symbols. 【0326】 Furthermore, which of the above-mentioned Alts to apply may be explicitly or implicitly specified by the specification, semi-statically set by RRC, dynamically notified by DCI, or determined by rules. For example, a parameter indicating which Alt to apply may be sent in at least one of RRC, DCI, and MAC CE (Medium Access Control Control Element). 【0327】 Here, Alt 2-1 to 2-3 described above may be selected based on the method of instructing SBFD operation (and / or DL / UL subband allocation). For example, if SBFD operation (and / or DL / UL subband allocation) is set by RRC, Alt 2-2 or Alt 2-3 may be applied. If SBFD operation (and / or DL / UL subband allocation) is dynamically notified by DCI, Alt 2-1 may be applied. Furthermore, this selection may be defined by specifications, semi-statically set by RRC settings, dynamically notified by DCI notifications, or determined according to rules. Furthermore, this selection may be explicitly or implicitly defined, set, notified, or determined. 【0328】 (UE operation of Proposal 6) In Proposal 6, the UE may control the transmit operation of the uplink control channel depending on whether the downlink time unit in a non-time-frequency-division duplex operation such as non-SBFD operation and / or the time unit in a time-frequency-division duplex operation such as SBFD operation overlap with the uplink control channel, and the transmit operation of the uplink control channel may be performed by the controlled transmit operation. Here, the time-frequency-division duplex operation may be SBFD, and the downlink time unit in a non-time-frequency-division duplex operation may be a DL symbol, subslot, slot, or any other time unit in a non-SBFD operation, specifically a non-SBFD semistatic / dynamic DL symbol and / or a non-SBFD dynamic FL symbol. Also, the time unit in a time-frequency-division duplex operation may be a UL, DL or FL symbol, subslot, slot, or any other time unit in SBFD operation, specifically an SBFD semistatic / dynamic UL symbol, an SBFD semistatic / dynamic DL symbol, and / or an SBFD semistatic / dynamic FL symbol. Furthermore, the uplink control channel may be, for example, PUCCH, PUCCH repeat, etc. 【0329】 Specifically, when the uplink control channel overlaps with the downlink time unit or flexible time unit in non-SBFD operation, the UE may refrain from transmitting the uplink control channel. Alternatively, when the uplink control channel overlaps with the downlink time unit or flexible time unit in non-SBFD operation, the UE may transmit the uplink control channel in a time unit that does not overlap with the downlink time unit in non-SBFD operation. That is, the UE may postpone the transmission of PUCCH or PUCCH repetition to a slot in which the symbols included in the time-domain resource for transmitting PUCCH or PUCCH repetition do not overlap with non-SBFD semistatic / dynamic DL symbols. 【0330】 Furthermore, when the uplink control channel overlaps with a time unit in SBFD operation, the UE may control the transmission operation of the uplink control channel regardless of whether the uplink control channel overlaps with the downlink subband in that time unit. For example, the UE may choose not to transmit the uplink control channel. Alternatively, the UE may transmit the uplink control channel in time units that do not overlap with the downlink time unit or flexible time unit in non-SBFD operation, and that do not overlap with the uplink time unit, downlink time unit, and / or flexible time unit in SBFD operation. That is, the UE may postpone the transmission of PUCCH or PUCCH repetition to a slot where the symbols included in the resource for transmitting PUCCH or PUCCH repetition do not overlap with non-SBFD semistatic / dynamic DL symbols and do not overlap with SBFD semistatic / dynamic UL symbols, SBFD semistatic / dynamic DL symbols, and / or SBFD dynamic FL symbols. Alternatively, the UE may rate-match PUCCH or PUCCH repetitions on time units other than the time units in SBFD operation on the uplink control channel. That is, the UE may rate-match PUCCH or PUCCH repetitions on symbols other than SBFD semistatic / dynamic UL symbols, SBFD semistatic / dynamic DL symbols, and / or SBFD dynamic FL symbols. 【0331】 Furthermore, when an uplink control channel overlaps with a time unit in SBFD operation, the UE may control the transmission operation of the uplink control channel depending on whether or not the uplink control channel overlaps with the downlink subband in that time unit. For example, if the uplink control channel does not overlap with the downlink subband in that time unit, the UE may transmit the uplink control channel on the configured / announced resource. On the other hand, if the uplink control channel overlaps with the downlink subband in that time unit, the UE may refrain from transmitting the uplink control channel. Alternatively / furthermore, the UE may rate match the uplink control channel on the UL subband in the time unit in SBFD operation. Alternatively / furthermore, the UE may transmit the uplink control channel in time units that do not overlap with the downlink time unit or flexible time unit in non-SBFD operation, and that do not overlap with the uplink time unit, downlink time unit, and / or flexible time unit in SBFD operation. In other words, the UE may postpone the transmission of PUCCH or PUCCH repeat to a slot or sub-slot where the resources of PUSCH or PUSCH repeat do not overlap with non-SBFD semistatic / dynamic DL symbols and do not overlap with SBFD semistatic / dynamic UL symbols, SBFD semistatic / dynamic DL symbols, and / or SBFD dynamic FL symbols. 【0332】 (gNB operation in Proposal 6) In Proposal 6, the gNB may control the receiving operation of the uplink control channel in either or both of the downlink time units in non-time-frequency-division duplexing operations such as non-SBFD operation, and the time units in time-frequency-division duplexing operations such as SBFD operation, and the receiving operation of the uplink control channel may be performed by the controlled receiving operation. Here, the time-frequency-division duplexing may be SBFD, and the downlink time units in non-time-frequency-division duplexing operations may be DL symbols, minislots, slots, or any other time units in non-SBFD operation, specifically non-SBFD semistatic / dynamic DL symbols and / or non-SBFD dynamic FL symbols. Also, the time units in time-frequency-division duplexing operations may be UL, DL or FL symbols, minislots, slots, or any other time units in SBFD operation, specifically SBFD semistatic / dynamic UL symbols, SBFD semistatic / dynamic DL symbols, and / or SBFD dynamic FL symbols. The uplink control channel may be, for example, PUCCH, PUCCH repeat, etc. 【0333】 (UE Capability) Regarding the PUCCH enhancement for time-frequency division duplexing operations such as SBFD operation described above, UE capability information indicating whether the UE supports the PUCCH enhancement for time-frequency division duplexing operations may be specified. Furthermore, UE capability information regarding PUCCH transmission for time-frequency division duplexing operations such as SBFD operation may also be specified. Specifically, UE capability information indicating whether the UE supports s-TRP / m-TRP PUCCH repetitions for SBFD operation may be specified. If the UE supports the PUCCH enhancement for time-frequency division duplexing operations, it may transmit UE capability information indicating that it supports the PUCCH enhancement for time-frequency division duplexing operations to the gNB. Upon receiving such UE capability information, the gNB can receive PUCCH from the UE in accordance with the PUCCH enhancement for time-frequency division duplexing operations. 【0334】 According to proposal 6 described above, PUCCH enhancements can be achieved for time-frequency division duplexing operations such as SBFD operation. 【0335】 [Proposal 7] Proposal 7 describes an enhanced SPS HARQ-ACK delay operation compared to time-frequency division duplexing operations such as SBFD operation. Specifically, the SPS HARQ-ACK delay operation is enhanced compared to SBFD operation as follows. SPS HARQ-ACK will be postponed under the following conditions: <Alt 1> When PUCCH overlaps with a semi-static DL symbol, SSB symbol, or Type-0 CORESET symbol, regardless of whether it is in SBFD or non-SBFD mode. <Alt 2> If PUCCH overlaps with a non-SBFD semi-static DL symbol, SSB symbol, or Type-0 CORESET symbol <Alt 3> If PUCCH overlaps with the SBFD symbol in addition to Alt 2 <Alt 4> When PUCCH overlaps with the DL subband in addition to Alt 2. The PUCCH resource to be deferred will be sent in the first available slot below. <Alt 1> PUCCH does not overlap with semi-static DL symbols, SSB symbols, or Type-0 CORESET symbols, regardless of whether it is operating in SBFD or non-SBFD mode. <Alt 2> PUCCH is a resource that does not overlap with non-SBFD semi-static DL symbols, SSB symbols, or Type-0 CORESET symbols. <Alt 3> PUCCH is a resource that does not overlap with SBFD symbols in addition to Alt 2. <Alt 4> PUCCH is a resource that does not overlap with the DL subband in addition to Alt 2. 【0336】 This defines the deferral behavior of SPS HARQ-ACK in SBFD and non-SBFD operation. When SPS HARQ-ACK deferral is enabled for an SPS configuration, the UE may defer the HARQ-ACK of the SPS configuration if the following deferral conditions Alt 1 to 4 are met. 【0337】 (Alt 1) In Alt 1, if the symbols included in the resources for transmitting the PUCCH of the SPS HARQ-ACK overlap with at least one semi-static DL symbol, SSB symbol, or type-0 CORESET symbol, regardless of whether it is in SBFD or non-SBFD operation, the UE may defer the HARQ-ACK in the SPS configuration. 【0338】 (Alt 2) Alt 2 allows the UE to defer the HARQ-ACK in the SPS configuration if the symbols included in the resources for transmitting the PUCCH of the SPS HARQ-ACK overlap with at least one non-SBFD semi-static DL symbol, SSB symbol, or type-0 CORESET symbol. 【0339】 (Alt 3) Alt 3 allows the UE to defer the HARQ-ACK for an SPS configuration if the symbols included in the resources for transmitting the PUCCH of the SPS HARQ-ACK overlap with at least one non-SBFD semistatic DL symbol, SSB symbol, type-0 CORESET symbol, SBFD semistatic / dynamic UL symbol, SBFD semistatic / dynamic DL symbol, and / or SBFD dynamic FL symbol. 【0340】 (Alt 4) In Alt 4, if the symbols included in the resources for transmitting the PUCCH of the SPS HARQ-ACK overlap with at least one non-SBFD semistatic DL symbol, SSB symbol, or type-0 CORESET symbol, or overlap with the DL subband in an SBFD semistatic / dynamic UL symbol, SBFD semistatic / dynamic DL symbol, and / or an SBFD dynamic FL symbol, the UE may postpone the HARQ-ACK in the SPS configuration. 【0341】 Here, Alt 1 to 4 described above may be selected based on the method of instructing SBFD operation (and / or DL / UL subband allocation). For example, if SBFD operation (and / or DL / UL subband allocation) is set by RRC, Alt 2 or Alt 3 may be applied. If SBFD operation (and / or DL / UL subband allocation) is dynamically notified by DCI, Alt 1 may be applied. Furthermore, this selection may be defined by specifications, semi-statically set by RRC settings, dynamically notified by DCI notifications, or determined according to rules. Furthermore, this selection may be explicitly or implicitly defined, set, notified, or determined. 【0342】 When the HARQ-ACK of the SPS configuration is deferred in this manner, the UE may determine the first available slot / subslot as the target slot / subslot for the deferral. Here, the first available slot / subslot may be one of the following Alt 1-4 PUCCH resources. 【0343】 (Alt 1) In Alt 1, the UE may defer the HARQ-ACK of an SPS configuration to the first available slot / sub-slot that does not overlap with the PUCCH of an SPS HARQ-ACK that overlaps with at least one semi-static DL symbol, SSB symbol, or type-0 CORESET symbol, regardless of whether the symbols contained in the PUCCH resource are in SBFD or non-SBFD operation. 【0344】 (Alt 2) In Alt 2, the UE may defer the HARQ-ACK of an SPS configuration to the first available slot / sub-slot that does not overlap with the PUCCH of an SPS HARQ-ACK, where the symbols contained in the PUCCH resource overlap with at least one non-SBFD semi-static DL symbol, SSB symbol, or type-0 CORESET symbol. 【0345】 (Alt 3) In Alt 3, the UE may defer the HARQ-ACK of an SPS configuration to the first available slot / subslot that does not overlap with the PUCCH of the SPS HARQ-ACK, where the symbols contained in the PUCCH resource overlap with at least one non-SBFD semistatic DL symbol, SSB symbol, type-0 CORESET symbol, SBFD semistatic / dynamic UL symbol, SBFD semistatic / dynamic DL symbol, and / or SBFD dynamic FL symbol. 【0346】 (Alt 4) In Alt 4, the UE may defer the HARQ-ACK of an SPS configuration to the first available slot / subslot that does not overlap with the PUCCH of an SPS HARQ-ACK, either if the symbols contained in the PUCCH resource overlap with at least one non-SBFD semistatic DL symbol, SSB symbol, or type-0 CORESET symbol, or if the symbols overlap with the DL subband in an SBFD semistatic / dynamic UL symbol, SBFD semistatic / dynamic DL symbol, and / or SBFD dynamic FL symbol. 【0347】 As one variation, the combined operation of SPS HARQ-ACK delay operation and SBFD operation does not have to be supported. For example, the UE does not have to assume / determine / decide / interpret that SPS HARQ-ACK delay operation is enabled for the SPS configuration on the serving cell / bandwidth portion (BWP) and that SBFD operation (and / or DL / UL subband allocation) is configured / announced / enabled on the serving cell / BWP at the same time. 【0348】 As another variation, if SBFD operation (and / or DL / UL subband allocation) is configured / announced / enabled on the serving cell / BWP, and SPS HARQ-ACK deferral operation is enabled for the SPS configuration on the serving cell / BWP, the UE may choose not to perform the SPS HARQ-ACK deferral operation. 【0349】 Furthermore, which of the above-mentioned Alts to apply may be explicitly or implicitly specified by the specification, semi-statically set by RRC, dynamically notified by DCI, or determined by rules. For example, a parameter indicating which Alt to apply may be sent in at least one of RRC, DCI, and MAC CE (Medium Access Control Control Element). 【0350】 (UE operation in Proposal 7) In Proposal 7, the UE may enable the HARQ-ACK delay operation and delay the transmission of the HARQ-ACK uplink control channel in accordance with the delay operation if the delay conditions for the HARQ-ACK in time-frequency division duplex operation such as SBFD operation and in non-time-frequency division duplex operation such as non-SBFD operation are met. Here, the HARQ-ACK may be an SPS HARQ-ACK, and the uplink control channel may be a PUCCH. 【0351】 Specifically, the UE may enable the delay operation of the HARQ-ACK when the SPS HARQ-ACK overlaps with a semi-static downlink time unit, an SSB time unit, or a type-0 CORESET time unit, regardless of whether the SPS HARQ-ACK is operating in SBFD or non-SBFD mode. The UE may also enable the delay operation of the HARQ-ACK when the SPS HARQ-ACK overlaps with a non-SBFD semi-static downlink time unit, a synchronous signal block (SSB) time unit, or a type-0 CORESET (Control Resource Set) time unit. Furthermore, the UE may enable the delay operation of the HARQ-ACK when the SPS HARQ-ACK overlaps with a non-SBFD semi-static downlink time unit, an SSB time unit, or a type-0 CORESET time unit, or when it overlaps with an SBFD semi-static / dynamic time unit. Furthermore, the UE may enable the delay operation of HARQ-ACK when SPS HARQ-ACK overlaps with a non-SBFD semistatic downlink time unit, an SSB time unit, or a type-0 CORESET time unit, or overlaps with a downlink subband in an SBFD semistatic / dynamic time unit. 【0352】 (gNB operation in Proposal 7) In Proposal 7, the gNB may transmit a downlink data channel and receive an uplink control channel with a delayed HARQ-ACK, which is enabled when the delay conditions for the HARQ-ACK in time-frequency division duplexing operations such as SBFD operation and non-time-frequency division duplexing operations such as non-SBFD operation are met for the downlink data channel. Here, the HARQ-ACK may be an SPS HARQ-ACK, and the uplink control channel may be a PUCCH. 【0353】 (UE Capability) Regarding the SPS HARQ-ACK enhancement for time-frequency division duplexing operations such as SBFD operation described above, UE capability information indicating whether the UE supports the SPS HARQ-ACK enhancement for time-frequency division duplexing operations may be specified. Furthermore, UE capability information regarding SPS HARQ-ACK transmission for time-frequency division duplexing operations such as SBFD operation may be specified. Specifically, UE capability information indicating whether the UE supports SPS HARQ-ACK deferral operation for SBFD operation may be specified. If the UE supports the SPS HARQ-ACK enhancement for time-frequency division duplexing operations, the UE may transmit UE capability information indicating that it supports the SPS HARQ-ACK enhancement for time-frequency division duplexing operations to the gNB. Upon receiving such UE capability information, the gNB can receive an SPS HARQ-ACK from the UE in accordance with the SPS HARQ-ACK enhancement for time-frequency division duplexing operations. 【0354】 According to Proposal 7 described above, SPS HARQ-ACK enhancements can be achieved for time-frequency division duplexing operations such as SBFD operation. 【0355】 (DCI 2_1) Section 11.2 of TS38.213 states that a set of physical resource blocks (PRBs) is equal to the active DL BWP, B INT It is specified that it must include the number of PRBs. If the UE detects DCI format 2_1 in PDCCH reception in a slot, the symbol set is the last one before the first symbol of PDCCH reception in that slot. 【number】 It is stipulated that it will become an individual symbol. Here, T INT This is the PDCCH monitoring period provided by the value of monitoringSlotPeriodicityAndOffset, and N symb slot μ is the number of symbols per slot, μ is the SCS configuration of the serving cell by mapping to each field in DCI format 2_1, μ INT This is the SCS configuration of the DL BWP when the UE receives a PDCCH in DCI format 2_1. If the UE is provided with tdd-UL-DL-ConfigurationCommon, the symbols notified by tdd-UL-DL-ConfigurationCommon to be uplinks are the last symbols before the first symbol of PDCCH reception in the slot. 【number】 It is specified that a symbol will be removed from the set of symbols. The resulting set of symbols will be N INT It is stipulated that it must include multiple symbols that are written as such. 【0356】 Furthermore, when the value of timeFrequencySet is set0, it is specified that the 14 bits from the MSB of the field in DCI format 2_1 have a one-to-one mapping to 14 consecutive groups of symbols from the symbol set. Here, the first 【number】 Each of the symbol groups is, 【number】 Includes the symbol of last 【number】 Each of the symbol groups is, 【number】 Contains a number of symbols. Here, a bit value of 0 indicates a transmission to the UE in the corresponding symbol group, and a bit value of 1 indicates no transmission to the UE in the corresponding symbol group. 【0357】 On the other hand, when the value of timeFrequencySet is set1, it is specified that the seven bit pairs from the MSB of the field in DCI format 2_1 have a one-to-one mapping to seven consecutive groups of symbols. Here, the first 【number】 Each of the symbol groups is, 【number】 Includes individual symbols, last 【number】 Each of the symbol groups is, 【number】 It contains a number of symbols. Also, the first bit in the bit pair of the symbol group is B INT The first from the set of PRBs 【number】 Applicable to a subset of individual PRBs, where the second bit in the bit pair of the symbol group is B INT The last of the set of individual PRBs 【number】 This is applicable to a subset of individual PRBs. Here, a bit value of 0 indicates a transmission to the UE in the corresponding subset of symbol groups and PRBs, and a bit value of 1 indicates no transmission to the UE in the corresponding subset of symbol groups and PRBs. For example, Figure 28 shows the case where the value of timeFrequencySet is set0 and the case where the value of timeFrequencySet is set1. 【0358】 [Considerations regarding preemption for SBFD operation] Regarding the time domain, considering SBFD operation in UL symbols, i.e., DL and UL subbands in UL symbols, DL transmission may exist in UL symbols. Therefore, it may not be appropriate to exclude such UL symbols from the symbols indicated by DCI 2_1. For example, as shown in Figure 29, in SBFD operation, DL subbands may exist in UL symbols configured by tdd-UL-DL-ConfigurationCommon. 【0359】 On the other hand, in the frequency domain, when considering SFBD operation in DL or UL symbols, the number of DL resource blocks (RBs) in different symbols may differ. For example, if the value of timeFrequencySet is set1, and the actual DL subband size is considered for the symbol group of the SBFD symbol set by the narrowband DL subband, it is thought that a higher granularity of frequency domain indication can be achieved. 【0360】 [Proposal 8] Proposal 8 describes time-domain and frequency-domain preemption enhancements for time-frequency division duplexing operations such as SBFD operation. Specifically, time-domain preemption and time-domain preemption are enhanced as follows. N enhanced in the time direction INT Calculation Case 1: When a DL subband is set for a resource configured as UL in the TDD pattern. <Alt 1> Include resources configured as UL in the TDD pattern. <Alt 2> Include resources that are configured as UL in the TDD pattern and are configured for SBFD operation. Case 2: When a resource set to DL in the TDD pattern does not have a UL subband configured. <Alt 1> Include resources configured as UL in the TDD pattern. <Alt 2> Do not exclude symbols. <Alt 3> Include resources that are set as UL in the TDD pattern and are not used for SBFD operation. Case 3: If SBFD operation is not supported by the UL symbol, include the resource set as UL in the TDD pattern. Frequency-related enhancements <Alt 1> The frequency resources, including the UL subband, are equally divided across two bit pairs. <Alt 2> The frequency resources, with the UL subband excluded, are divided into two DL subbands for every two bit pairs. 【0361】 Throughout this specification, SBFD operation in a UL symbol means the DL subband in a UL symbol designated as an uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, and SBFD operation in a DL symbol may mean the UL subband in a DL symbol designated as a downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated. 【0362】 (Preemption in the time domain) N INT To obtain individual symbols, the last symbol before the first symbol of the PDCCH reception in the slot 【number】 The symbols to be removed from this symbol may correspond to cases 1 to 3 below. Case 1: SBFD operation is supported / enabled in UL symbols, and SBFD operation (or DL / UL subband assignment) is notified / configured by cell-specific / group-common signaling (e.g., cell-specific / group-common RRC configuration or DCI). Case 2: SBFD operation is supported / enabled in the UL symbol, and SBFD operation (or DL / UL subband assignment) is notified / configured by UE-specific signaling (e.g., UE-specific RRC configuration or UE-specific DCI). Case 3: SBFD operation in UL symbols is not supported / enabled. 【0363】 <Case 1> In Case 1, if SBFD operation is supported / enabled in the UL symbol, and SBFD operation (or DL / UL subband assignment) is notified / configured by cell-specific / group-common signaling (e.g., cell-specific / group-common RRC configuration or DCI), then N INT The symbols to be deleted in order to obtain this symbol may also be the symbols specified by Alt 1 and / or Alt 2 below. 【0364】 <<Case 1: Alt 1>> In Alt 1, SBFD operation in UL symbols is supported / enabled, and SBFD operation (or DL / UL subband assignment) is notified / configured by cell-specific / group-common signaling, N INT Symbols to be removed in order to obtain this symbol may include symbols designated as uplinks by tdd-UL-DL-ConfigurationCommon. Alt 1 is the same as Rel-15. 【0365】 <<Case 1: Alt 2>> In Alt 2, SBFD operation in UL symbols is supported / enabled, and when SBFD operation (or DL / UL subband assignment) is notified / configured by cell-specific / group-common signaling, N INT Symbols to be removed in order to obtain a specific symbol may include symbols that are indicated as uplinks by tdd-UL-DL-ConfigurationCommon but are not configured / notified for SBFD operation. Since SBFD UL symbols include DL subbands, DL transmissions may occur on UL symbols. Therefore, preemption instructions by DCI 2_1 may be applicable to such UL symbols. 【0366】 <Case 2> In Case 2, if SBFD operation is supported / enabled in the UL symbol, and SBFD operation (or DL / UL subband assignment) is notified / configured by UE-specific signaling, then N INT The symbols to be deleted in order to obtain this symbol may also be the symbols specified by Alt 1, Alt 2 and / or Alt 3 below. 【0367】 <<Case 2: Alt 1>> In Alt 1, SBFD operation in UL symbols is supported / enabled, and SBFD operation (or DL / UL subband assignment) is notified / configured by UE-specific signaling, N INT Symbols to be removed in order to obtain this symbol may include symbols designated as uplinks by tdd-UL-DL-ConfigurationCommon. Alt 1 is the same as Rel-15. 【0368】 <<Case 2: Alt 2>> In Alt 2, if SBFD operation is supported / enabled for UL symbols and SBFD operation (or DL / UL subband assignment) is notified / configured by UE-specific signaling, then neither symbol needs to be deleted. In Case 2, a particular UE is unsure whether the UL symbol has a DL subband for other UEs in that cell. Therefore, the UL symbol does not need to be deleted for DCI 2_1 instructions. 【0369】 <<Case 2: Alt 3>> In Alt 3, SBFD operation in UL symbols is supported / enabled, and when SBFD operation (or DL / UL subband assignment) is notified / configured by UE-specific signaling, N INT Symbols removed to obtain a specific symbol may include symbols designated as uplinks by tdd-UL-DL-ConfigurationCommon and reserved for non-SBFD operation as defined by the specification or RRC configuration, if present. For example, the PRACH symbol / slot may be reserved for non-SBFD operation. If, based on the analysis of Alt 1, the UE can determine that a particular UL symbol (e.g., the PRACH symbol) is unavailable for SBFD operation as defined by the specification or set by the RRC, that UL symbol may be removed for DCI 2_1 indication. 【0370】 <Case 3> In Case 3, if SBFD operation in UL symbols is not supported / enabled, N INT Symbols to be removed in order to obtain this symbol may include symbols designated as uplinks by tdd-UL-DL-ConfigurationCommon. This is similar to Rel-15. 【0371】 (Preemption in the frequency domain) If the value of timeFrequencySet is set1, the resource block (RB) applicable to each bit pair in the symbol group may be determined by Alt 1 and / or Alt 2 below. 【0372】 <Alt 1> In Alt 1, if the value of timeFrequencySet is set1, the RB applicable to each bit pair in the symbol group is, similar to the rule in Rel-15, regardless of whether there are SBFD symbols in the symbol group, B INT The first from the set of PRBs 【number】 The first bit corresponds to a subset of the PRB, and B INT The last of the set of individual PRBs 【number】 This may be determined by a second bit corresponding to a subset of the PRBs. For example, as shown in Figure 30, the frequency resources including the UL subband are evenly divided across the two bit pairs. 【0373】 <Alt 2> In Alt 2, if the value of timeFrequencySet is set1, the RB applicable to each bit pair of the symbol group may be determined by Alt 2-1 and / or Alt 2-2 below, depending on the DL bandwidth size of the symbol group. 【0374】 <<Alt 2-1> > In Alt 2-1, the symbol group contains only SBFD symbols, and the SBFD symbols in the symbol group total B on the DL subband of each SBFD symbol in the symbol group. INT-DL When there are identical DL / UL subband allocation patterns by individual PRBs, the RB applicable to each bit pair in a symbol group is B INT-DL The first from a set of DL PRBs 【number】 The first bit corresponds to a subset of the DL PRB, and B INT-DL The last of the DL PRB set 【number】 This may be determined by a second bit corresponding to a subset of the DL PRBs. For example, as shown in Figure 31, frequency resources that do not include the UL subband are evenly divided across the two bit pairs. 【0375】 <<Alt 2-2> > In Alt 2-2, the symbol group contains only SBFD symbols, and the total number of SBFD symbols in the symbol group is B INT-DL-subband When there are identical DL / UL subband assignment patterns for each DL subband, the applicable RB for each bit pair in the symbol group is B INT-DL-subband The first from this set of DL subbands 【number】 The first bit corresponds to a subset of the DL subbands, and B INT-DL-subband The last of the DL subband set 【number】 This may be determined by a second bit corresponding to a subset of DL subbands. For example, as shown in Figure 32, a frequency resource that does not include an UL subband is divided into two DL subbands for two bit pairs. 【0376】 The frequency resource division method described above is not necessarily limited to that described above, and any other division method may be applied. Which of the above Alts to apply may be specified explicitly or implicitly by the specification, set semistatically by RRC, dynamically notified by DCI, or determined by rules. For example, a parameter indicating which Alt should be applied may be transmitted in at least one of RRC, DCI, and MAC CE (Medium Access Control Control Element). 【0377】 (UE operation of Proposal 8) In Proposal 8, the UE may, in downlink reception of a time-frequency division duplex operation such as SBFD operation, adjust the radio resource indicated by the downlink control information in the time domain or the frequency domain, and receive the downlink channel with the adjusted radio resource. Here, the time-frequency division duplex operation may be SBFD, the downlink channel may be PDCCH, PDSCH, etc., and the downlink control information may be DCI 2_1. Furthermore, the radio resource is a resource defined by a time unit such as a symbol and a frequency unit such as a resource block. 【0378】 Specifically, the UE may exclude time units set as uplinks by time-division duplex (TDD) configuration from the radio resources indicated by the downlink control information. That is, with respect to time-domain preemption, the UE may set N for preemption. INT To obtain individual symbols, you may exclude symbols that are set as UL by a TDD configuration such as tdd-UL-DL-ConfigurationCommon. 【0379】 Furthermore, the UE may exclude the uplink subband in SBFD operation from the radio resources indicated by the downlink control information. That is, with respect to frequency domain preemption, the UE may receive the downlink channel in a frequency band that includes the UL subband, or a frequency band that does not include the UL subband, in SBFD operation, as shown in Figures 30-32. 【0380】 (gNB operation in Proposal 8) In Proposal 8, the gNB may, in downlink transmission of a time-frequency division duplex operation such as SBFD operation, control the downlink channel to be received by the terminal on a radio resource that is coordinated in the time domain or frequency domain with respect to the radio resource indicated by the downlink control information, and transmit the downlink channel. Here, the time-frequency division duplex operation may be SBFD, for example the downlink channel may be PDCCH, PDSCH, etc., and the downlink control information may be DCI 2_1. Furthermore, the radio resource is a resource defined by a time unit such as a symbol and a frequency unit such as a resource block. 【0381】 (UE Capability) Regarding preemption in time-frequency division duplexing operations such as SBFD operation, UE capability information may be specified indicating whether the UE supports enhanced DCI 2_1 for time-frequency division duplexing operations. Furthermore, UE capability information regarding preemption for time-frequency division duplexing operations such as SBFD operation may also be specified. If the UE supports enhanced preemption for time-frequency division duplexing operations, the UE may send UE capability information to the gNB indicating that it supports enhanced DCI 2_1 for time-frequency division duplexing operations. Upon receiving such UE capability information, the gNB can send enhanced DCI 2_1 for time-frequency division duplexing operations to the UE, causing the UE to perform preemption in time-frequency division duplexing operations. 【0382】 (Effects of Proposal 8) According to Proposal 8, enhanced preemption can be achieved for time-frequency division duplexing operations such as SBFD operation. 【0383】 (DCI 2_4) Section 11.2A of TS38.213 specifies that cancellation notices should be in DCI format 2_4. N CI The number of bits provided by :ci-PayloadSize B CI :Number of PRBs provided by frequencyRegionforCI in timeFrequencyRegion T CI :If the PDCCH monitoring period of a search space set according to DCI format 2_4 is 1 slot, and there are multiple PDCCH monitoring opportunities in the slot, this is provided by timeDurationforCI in timeFrequencyRegion, or otherwise, the number of symbols obtained by subtracting the symbols for receiving SS / PBCH blocks and DL symbols indicated by tdd-UL-DL-ConfigurationCommon from multiple symbols equal to the PDCCH monitoring period. G CI :timeFrequencyRegion provided by timeGranularityforCI CI Number of partitions for individual symbols It is stipulated that this must be shown. 【0384】 N CI G from MSB of individual bits CI The set of bits is G CI Each symbol group has a one-to-one mapping, and the first 【number】 Each of these groups is, 【number】 Includes the following symbols, the rest 【number】 Each of these groups is, 【number】 It is specified that it contains a number of symbols. The UE determines the symbol duration with respect to the SCS configuration of the active DL BWP that monitors PDCCH for detection of DCI format 2_4. That is, in the time domain, the indicated symbol is G CI It is divided into individual sets. 【0385】 For a symbol group, N from the MSB of each bit set. BI =N CI / G CI N bits BI Each PRB group has a one-to-one mapping, and the first 【number】 Each of these groups is, 【number】 Includes the PRB, the remaining 【number】 Each of these groups is, 【number】 It is stipulated that it must include individual PRBs. According to TS38.214, UE specifies that the RIV should be offset RB. start and length L RB frequencyRegionforCI indicates the SCS configuration of the active DL BWP where the UE monitors PDCCH for DCI format 2_4 detection. carrier From the offsetToCarrier in FrequencyInfoUL-SIB or FrequencyInfoUL that shows N RFR start =O carier +RB start The first PRB index as, and B CI =L RB It is stipulated that the number of consecutive RBs as a set of symbols is determined. That is, in the frequency domain, for each symbol set, RB is N BI It is stipulated that it will be divided into sets of [number]. 【0386】 For example, Figure 33 shows an example of a partition in the time domain and frequency domain using DCI 2_4. 【0387】 [Considerations regarding cancellation of SBFD operation] Regarding the time domain, considering SBFD operation in DL symbols, i.e., DL and UL subbands in DL symbols, UL transmission may exist in DL symbols. Therefore, it may not be appropriate to exclude such DL symbols from the symbols indicated by DCI 2_4. For example, as shown in Figure 34, in SBFD operation, UL subbands may exist in DL symbols configured by tdd-UL-DL-ConfigurationCommon. 【0388】 On the other hand, in the frequency domain, when considering SFBD operation in DL or UL symbols, the number of UL resource blocks (RBs) in different symbols can differ. For example, for an SBFD symbol set with a narrowband UL subband, the same N BI According to this RB set, the frequency domain granularity is N in non-SBFD UL symbols. BI This can be more detailed than individual RB sets. 【0389】 [Proposal 9] Proposal 9 describes enhanced time-domain and frequency-domain cancellation for time-frequency division duplexing operations such as SBFD operation. Specifically, time-domain UL cancellation and time-domain UL cancellation are enhanced as follows. Enhanced T in the time direction CI Calculation Case 1: When a UL subband is set for a resource that is set to UL in the TDD pattern. <Alt 1> Include resources configured as DL in the TDD pattern. <Alt 2> Include resources that are configured as DL in the TDD pattern and do not have SBFD behavior configured. Case 2: When a DL subband is configured for a resource set to UL in the TDD pattern. <Alt 1> Include resources configured as DL in the TDD pattern. <Alt 2> Do not exclude symbols. <Alt 3> Include resources that are configured as DL in the TDD pattern and are not used for SBFD operation. Case 3: If SBFD operation is not supported by DL symbols, include resources set to DL in the TDD pattern. Frequency-related enhancements <Alt 1> The frequency resources, including the DL subband, will be divided. <Alt 2> The frequency resources are divided, excluding the DL subband. 【0390】 Throughout this specification, SBFD operation in a UL symbol means the DL subband in a UL symbol designated as an uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, and SBFD operation in a DL symbol may mean the UL subband in a DL symbol designated as a downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated. 【0391】 (Time-domain cancellation) In UL cancellation in the time domain, T CI To obtain a single symbol, the symbols removed from multiple symbols (a number equal to the timeDurationforCI or PDCCH monitoring period) may correspond to cases 1-3 below. Case 1: SBFD operation is supported / enabled in DL symbols, and SBFD operation (or DL / UL subband assignment) is notified / configured by cell-specific / group-common signaling (e.g., cell-specific / group-common RRC configuration or DCI). Case 2: SBFD operation is supported / enabled in DL symbols, and SBFD operation (or DL / UL subband assignment) is notified / configured by UE-specific signaling (e.g., UE-specific RRC configuration or UE-specific DCI). Case 3: SBFD operation in DL symbols is not supported / enabled. 【0392】 <Case 1> In Case 1, if SBFD operation is supported / enabled in the DL symbol, and SBFD operation (or DL / UL subband assignment) is notified / configured by cell-specific / group-common signaling (e.g., cell-specific / group-common RRC configuration or DCI), then T CI The symbols to be deleted in order to obtain this symbol may also be the symbols specified by Alt 1 and / or Alt 2 below. 【0393】 <<Case 1: Alt 1>> In Alt 1, SBFD operation in DL symbols is supported / enabled, and SBFD operation (or DL / UL subband assignment) is notified / configured by cell-specific / group-common signaling, T CI Symbols to be removed in order to obtain this symbol may include symbols designated as downlinks by tdd-UL-DL-ConfigurationCommon. Alt 1 is the same as Rel-15. 【0394】 <<Case 1: Alt 2>> In Alt 2, SBFD operation in DL symbols is supported / enabled, and when SBFD operation (or DL / UL subband assignment) is notified / configured by cell-specific / group-common signaling, T CI Symbols to be removed in order to obtain a specific symbol may include symbols that are indicated as downlink by tdd-UL-DL-ConfigurationCommon but are not configured / notified for SBFD operation. Since SBFD DL symbols include the UL subband, UL transmissions may occur on DL symbols. Therefore, UL cancellation instructions by DCI 2_4 may be applicable to such DL symbols. 【0395】 <Case 2> In Case 2, if SBFD operation is supported / enabled in the DL symbol, and SBFD operation (or DL / UL subband assignment) is notified / configured by UE-specific signaling, T CI The symbols to be deleted in order to obtain this symbol may also be the symbols specified by Alt 1, Alt 2 and / or Alt 3 below. 【0396】 <<Case 2: Alt 1>> In Alt 1, SBFD operation in DL symbols is supported / enabled, and SBFD operation (or DL / UL subband assignment) is notified / configured by UE-specific signaling, T CI Symbols to be removed in order to obtain this symbol may include symbols designated as downlinks by tdd-UL-DL-ConfigurationCommon. Alt 1 is the same as Rel-15. 【0397】 <<Case 2: Alt 2>> In Alt 2, if SBFD operation is supported / enabled for DL symbols and SBFD operation (or DL / UL subband assignment) is notified / configured by UE-specific signaling, neither symbol needs to be deleted. In Case 2, a particular UE is unsure whether the DL symbol has an UL subband for other UEs in that cell. Therefore, the DL symbol does not need to be deleted for DCI 2_4 instructions. 【0398】 <<Case 2: Alt 3>> In Alt 3, SBFD operation in DL symbols is supported / enabled, and when SBFD operation (or DL / UL subband assignment) is notified / configured by UE-specific signaling, T CI Symbols to be removed in order to obtain a single symbol may include symbols that are indicated as downlinks by tdd-UL-DL-ConfigurationCommon and reserved for non-SBFD operation as defined by the specification or RRC configuration, if present. For example, an SSB symbol / slot may be reserved for non-SBFD operation. If, based on the analysis of Alt 1, the UE can determine that a particular DL symbol (e.g., an SSB symbol) is unavailable for SBFD operation as defined by the specification or set by the RRC, that DL symbol may be removed for DCI 2_4 indication. 【0399】 <Case 3> In Case 3, if SBFD operation in DL symbols is not supported / enabled, T CI Symbols to be removed in order to obtain this symbol may include symbols designated as downlinks by tdd-UL-DL-ConfigurationCommon. This is similar to Rel-15. 【0400】 (Frequency domain cancellation) In UL cancellation in the frequency domain, the resource block (RB) applicable to each bit pair of a symbol group may be determined by Alt 1 and / or Alt 2 below. 【0401】 <Alt 1> In Alt 1, for the RB applicable to each bit pair in a symbol group, the first rule applies regardless of the UL subband size in the symbol group, similar to the rule in Rel-15. 【number】 This group, 【number】 Includes the PRB, the remaining 【number】 Each of these groups is, 【number】 It may also include individual PRBs. For example, as shown in Figure 35, the frequency resources including the UL subband are equally divided across two bit pairs. 【0402】 <Alt 2> In Alt 2, the RB applicable to each bit pair of a symbol group may be determined by Alt 2-1 and / or Alt 2-2 below, depending on the UL bandwidth size of the symbol group. 【0403】 <<Alt 2-1> > In Alt 2-1, the symbol group contains only SBFD symbols, and the SBFD symbols in the symbol group total B on the UL subband of each SBFD symbol in the symbol group. CI-UL If there are identical DL / UL subband allocation patterns by individual PRBs, then for the RBs applicable to each bit pair in the symbol group, the first 【number】 This group, 【number】 Includes the PRB, the remaining 【number】 Each of these groups is, 【number】 It may also include individual PRBs. For example, as shown in Figure 36, frequency resources that do not include the DL subband are equally divided over two bit pairs. 【0404】 <<Alt 2-2> > In Alt 2-2, the symbol group contains only SBFD symbols, and the total number of SBFD symbols in the symbol group is B CI-UL-subband If there are identical DL / UL subband assignment patterns for each UL subband, then for the RB applicable to each bit pair of the symbol group, the first 【number】 This group, 【number】 This includes the UL subbands, and the rest [Number] Each of the groups may include [Number] It may also include a number of UL sub - bands. For example, as shown in FIG. 37, a frequency resource that does not include a DL sub - band is divided into two UL sub - bands for two bit pairs. 【0405】 Note that which of the above - mentioned Alts to apply may be specified by the specification, either explicitly or implicitly, may be set semi - statically by RRC, may be notified dynamically by DCI, or may be determined by rules. For example, a parameter indicating which Alt to apply may be transmitted in at least one of RRC, DCI, and MAC CE (Medium Access Control Control Element). 【0406】 (UE operation of Proposal 9) In Proposal 9, in the uplink transmission of time - frequency division multiplexing operations such as SBFD operations, the UE may adjust the radio resources indicated by the downlink control information with respect to the time domain or the frequency domain, and transmit the uplink channel in the adjusted radio resources. Here, the time - frequency division multiplexing may be SBFD. For example, the uplink channel may be PUCCH, PUSCH, etc., and the downlink control information may be DCI 2_4. Also, the radio resources are resources defined by time units such as symbols and frequency units such as resource blocks. 【0407】 Specifically, the UE may exclude the time units set as uplink by the time - division multiplexing (TDD) setting from the radio resources indicated by the downlink control information. That is, for UL cancellation in the time domain, the UE may use T for UL cancellation CI To obtain individual symbols, you may exclude symbols that are set as DL by a TDD configuration such as tdd-UL-DL-ConfigurationCommon. 【0408】 Furthermore, the UE may exclude the downlink subband in SBFD operation from the radio resources indicated by the downlink control information. That is, with respect to frequency domain UL cancellation, the UE may transmit the uplink channel in a frequency band that includes the DL subband, or a frequency band that does not include the DL subband, in SBFD operation, as shown in Figures 35-37. 【0409】 (gNB operation in Proposal 9) In Proposal 9, the gNB may, in uplink reception of a time-frequency division duplex operation such as SBFD operation, control the terminal to transmit an uplink channel on a radio resource that is coordinated in the time domain or frequency domain with respect to the radio resource indicated by the downlink control information, and transmit the uplink channel. Here, the time-frequency division duplex operation may be SBFD, for example the uplink channel may be PUCCH, PUSCH, etc., and the downlink control information may be DCI 2_4. Furthermore, the radio resource is a resource defined by a time unit such as a symbol and a frequency unit such as a resource block. 【0410】 (UE Capability) Regarding cancellation in time-frequency division duplexing operations such as SBFD operation, UE capability information may be specified indicating whether the UE supports enhanced DCI 2_4 for time-frequency division duplexing. Furthermore, UE capability information regarding cancellation for time-frequency division duplexing operations such as SBFD operation may also be specified. If the UE supports enhanced cancellation for time-frequency division duplexing, it may send UE capability information to the gNB indicating that it supports enhanced DCI 2_4 for time-frequency division duplexing. Upon receiving such UE capability information, the gNB can send enhanced DCI 2_4 for time-frequency division duplexing to the UE, causing the UE to perform cancellation in SBFD operation. 【0411】 (Effects of Proposal 9) According to Proposal 9, enhanced UL cancellation can be achieved for time-frequency division duplexing such as SBFD operation. 【0412】 <Hardware Configuration> The block diagrams used in the description of the above embodiments show functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may also be realized by combining the above one device or the above multiple devices with software. 【0413】 Functions include, but are not limited to, judgment, decision, judgment, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, assumption, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission is called a transmitting unit or transmitter. As mentioned above, the method of implementation is not particularly limited. 【0414】 For example, a base station, user terminal, etc. in one embodiment of the present disclosure may function as a computer that processes the wireless communication method of the present disclosure. Figure 38 is a diagram showing an example of the hardware configuration of a base station and user terminal according to one embodiment of the present disclosure. The base station 10 and user terminal 20 described above may be physically configured as a computer device including a processor 1001, memory 1002, storage 1003, communication device 1004, input device 1005, output device 1006, bus 1007, etc. 【0415】 In the following explanation, the term "device" can be replaced with "circuit," "device," "unit," etc. The hardware configuration of the base station 10 and the user terminal 20 may include one or more of the devices shown in Figure 38, or it may be configured to omit some of the devices. 【0416】 Each function in the base station 10 and the user terminal 20 is realized by loading predetermined software (programs) onto hardware such as the processor 1001 and memory 1002, which allows the processor 1001 to perform calculations and control communication by the communication device 1004, or control at least one of reading and writing data to the memory 1002 and storage 1003. 【0417】 The processor 1001 controls the entire computer, for example, by running the operating system. The processor 1001 may be composed of a central processing unit (CPU) that includes interfaces with peripheral devices, control units, arithmetic units, registers, etc. For example, the baseband signal processing unit 104 and call processing unit 105 mentioned above may be implemented by the processor 1001. 【0418】 Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. For example, the control unit 401 of the user terminal 20 may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and other functional blocks may be implemented similarly. The above-described various processes have been explained as being executed by one processor 1001, but they may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The program may also be transmitted from the network via a telecommunications line. 【0419】 Memory 1002 is a computer-readable recording medium and may consist of at least one of the following: ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. Memory 1002 may also be called a register, cache, main memory, etc. Memory 1002 can store executable programs (program code), software modules, etc., for carrying out a wireless communication method according to one embodiment of the present disclosure. 【0420】 Storage 1003 is a computer-readable recording medium and may consist of at least one of the following: an optical disc such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disc, a digital multipurpose disc, a Blu-ray® disc), a smart card, flash memory (e.g., a card, a stick, a key drive), a floppy® disk, a magnetic strip, etc. Storage 1003 may also be called an auxiliary storage device. The above-mentioned storage medium may be, for example, a database, server, or other suitable medium including at least one of memory 1002 and storage 1003. 【0421】 The communication device 1004 is hardware (transmitting / receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc. The communication device 1004 may be configured to include a high-frequency switch, duplexer, filter, frequency synthesizer, etc., in order to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the above-mentioned transmitting / receiving antenna 101, amplifier section 102, transmitting / receiving section 103, transmission path interface 106, etc., may be implemented by the communication device 1004. The transmitting / receiving section 103 may be implemented in physically or logically separated form, consisting of a transmitting section 103a and a receiving section 103b. 【0422】 The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, LED lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel). 【0423】 Furthermore, each device, such as the processor 1001 and memory 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or different buses may be configured for each device. 【0424】 Furthermore, the base station 10 and the user terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), and an FPGA (Field Programmable Gate Array), and some or all of each functional block may be realized by such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components. 【0425】 Information notification is not limited to the embodiments described herein and may be carried out by other means. For example, information notification may be carried out by physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), upper layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, broadcast information (MIB (Master Information Block), SIB (System Information Block))), other signals, or combinations thereof. RRC signaling may also be called RRC messages, and may be, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc. 【0426】 Each aspect / embodiment described in this disclosure includes LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (where x is, for example, an integer or decimal)), FRA (Future Radio Access), NR (new Radio), New radio access (NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), and IEEE This may apply to at least one system utilizing 802.20, UWB (Ultra-WideBand), Bluetooth®, or other appropriate systems, and to next-generation systems extended, modified, created, or defined based thereon. It may also apply to a combination of multiple systems (for example, a combination of at least one of LTE and LTE-A with 5G). 【0427】 The processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described herein may be reordered, provided they are consistent with each other. For example, the methods described herein present various step elements in an exemplary order and are not limited to that specific order. 【0428】 The specific operations described in this disclosure as being performed by a base station may, in some cases, be performed by its upper node. In a network consisting of one or more network nodes having a base station, it is clear that various operations performed for communication with a terminal can be performed by the base station and at least one other network node (for example, an MME or S-GW, but not limited to these). Although the above example illustrates a case where there is one other network node besides the base station, it may also be a combination of multiple other network nodes (for example, an MME and an S-GW). 【0429】 Information, etc. (see the "Information, Signals" section) can be output from a higher layer (or lower layer) to a lower layer (or higher layer). Input and output may also occur via multiple network nodes. 【0430】 Input and output information may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information may be overwritten, updated, or appended to. Output information may be deleted. Input information may be transmitted to other devices. 【0431】 The determination may be made by a value represented by 1 bit (0 or 1), by a boolean value (true or false), or by a numerical comparison (for example, a comparison with a predetermined value). 【0432】 Each aspect / embodiment described herein may be used individually, in combination, or switched between as needed during implementation. Furthermore, notification of specific information (e.g., notification that "X is") is not limited to explicit notification, but may also be implicit (e.g., by not providing such notification). 【0433】 Although the present disclosure has been described in detail above, it will be clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the intent and scope of the present disclosure as defined by the claims. Therefore, the descriptions in the present disclosure are illustrative and not intended to be restrictive in any way. 【0434】 Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name. 【0435】 Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technology (such as coaxial cable, fiber optic cable, twisted pair, or digital subscriber line (DSL)) and wireless technology (such as infrared or microwave), then at least one of these wired and wireless technologies is included in the definition of a transmission medium. 【0436】 The information, signals, etc. described in this disclosure may be represented using any of the various different techniques. For example, the data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof. 【0437】 In addition, terms used in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of the channel and symbol may be a signal (signaling). Also, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, cell, frequency carrier, etc. 【0438】 The terms “system” and “network” as used in this disclosure are interchangeable. 【0439】 Furthermore, the information, parameters, etc., described in this disclosure may be expressed using absolute values, relative values from a given value, or other corresponding information. For example, wireless resources may be indicated by an index. 【0440】 The names used for the parameters described above are not restrictive in any way. Furthermore, the formulas and other expressions using these parameters may differ from those expressly disclosed in this disclosure. Various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, and therefore, the various names assigned to these various channels and information elements are not restrictive in any way. 【0441】 In this disclosure, terms such as "base station (BS)", "wireless base station", "fixed station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "access point", "transmission point", "reception point", "transmission / reception point", "cell", "sector", "cell group", "carrier", and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell. 【0442】 A base station can accommodate one or more (e.g., three) cells. If a base station accommodates multiple cells, the entire coverage area of the base station can be divided into several smaller areas, each of which may also be provided with communication services by a base station subsystem (e.g., a Remote Radio Head (RRH)). The terms “cell” or “sector” refer to part or all of the coverage area of at least one of the base station and / or base station subsystems that provide communication services in that coverage. 【0443】 In this disclosure, the transmission of information by a base station to a terminal may be interpreted as the base station instructing the terminal to perform information-based control or operation. 【0444】 In this disclosure, terms such as "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" may be used interchangeably. 【0445】 A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or several other appropriate terms. 【0446】 At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may also be a device mounted on a mobile body, the mobile body itself, etc. The mobile body refers to a movable object, and its speed of movement is arbitrary. This also includes the case when the mobile body is stationary. The mobile body includes, but is not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and items mounted on them. The mobile body may also be a mobile body that moves autonomously based on operation commands. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). Furthermore, at least one of the base station and the mobile station may include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor. 【0447】 Furthermore, the term "base station" in this disclosure may be interpreted as "user terminal." For example, the various aspects / embodiments of this disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple user terminals (which may be called, for example, D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.). In this case, the user terminal 20 may have the functions that the base station 10 has. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, uplink channel, downlink channel, etc., may be interpreted as side channel. 【0448】 Similarly, the term "user terminal" in this disclosure may be replaced with "base station." In this case, the base station 10 may be configured to have the same functions as the user terminal 20 described above. 【0449】 Figure 39 shows an example of the configuration of vehicle 1. As shown in Figure 39, vehicle 1 comprises a drive unit 2, a steering unit 3, an accelerator pedal 4, a brake pedal 5, a shift lever 6, left and right front wheels 7, left and right rear wheels 8, an axle 9, an electronic control unit 10, various sensors 21-29, an information service unit 12, and a communication module 13. 【0450】 The drive unit 2 is composed of, for example, an engine, a motor, or a hybrid of an engine and a motor. 【0451】 The steering unit 3 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel performed by the user. 【0452】 The electronic control unit 10 consists of a microprocessor 31, memory (ROM, RAM) 32, and communication ports (IO ports) 33. Signals from various sensors 21-27 installed in the vehicle are input to the electronic control unit 10. The electronic control unit 10 may also be called an ECU (Electronic Control Unit). 【0453】 Signals from various sensors 21 to 28 include current signals from the current sensor 21 which senses the motor current, front and rear wheel rotation speed signals obtained by the rotation speed sensor 22, front and rear wheel air pressure signals obtained by the air pressure sensor 23, vehicle speed signals obtained by the vehicle speed sensor 24, acceleration signals obtained by the acceleration sensor 25, accelerator pedal depression amount signals obtained by the accelerator pedal sensor 29, brake pedal depression amount signals obtained by the brake pedal sensor 26, shift lever operation signals obtained by the shift lever sensor 27, and detection signals obtained by the object detection sensor 28 for detecting obstacles, vehicles, pedestrians, etc. 【0454】 The Information Service Unit 12 consists of various devices for providing (outputting) various types of information such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, television, and radio, and one or more ECUs that control these devices. The Information Service Unit 12 uses information acquired from external devices via a communication module 13, etc., to provide various multimedia information and multimedia services to the occupants of the vehicle 1. 【0455】 The information service unit 12 may include input devices that accept input from the outside (e.g., keyboard, mouse, microphone, switch, button, sensor, touch panel, etc.) or output devices that perform output to the outside (e.g., display, speaker, LED lamp, touch panel, etc.). 【0456】 The driver assistance system unit 30 consists of various devices that provide functions to prevent accidents or reduce the driver's workload, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System)), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. The driver assistance system unit 30 also transmits and receives various information via the communication module 13 to realize driver assistance functions or autonomous driving functions. 【0457】 The communication module 13 can communicate with the microprocessor 31 and components of the vehicle 1 via its communication port. For example, the communication module 13 sends and receives data via its communication port 33 between the drive unit 2, steering unit 3, accelerator pedal 4, brake pedal 5, shift lever 6, left and right front wheels 7, left and right rear wheels 8, axle 9, the microprocessor 31 and memory (ROM, RAM) 32 in the electronic control unit 10, and sensors 21-28 provided in the vehicle 1. 【0458】 The communication module 13 is a communication device that can be controlled by the microprocessor 31 of the electronic control unit 10 and can communicate with external devices. For example, it can send and receive various types of information with external devices via wireless communication. The communication module 13 may be located either inside or outside the electronic control unit 10. The external device may be, for example, a base station or a mobile station. 【0459】 The communication module 13 may transmit at least one of the following to an external device via wireless communication: signals from the various sensors 21-28 input to the electronic control unit 10, information obtained based on those signals, and information based on input from an external source (user) obtained via the information service unit 12. The electronic control unit 10, the various sensors 21-28, the information service unit 12, etc., may also be called input units that accept input. For example, the PUSCH transmitted by the communication module 13 may include information based on the above input. 【0460】 The communication module 13 receives various information (traffic information, signal information, vehicle-to-vehicle information, etc.) transmitted from an external device and displays it on the information service unit 12 installed in the vehicle. The information service unit 12 may also be called an output unit, which outputs information (for example, it outputs information to devices such as displays and speakers based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 13). 【0461】 Furthermore, the communication module 13 stores various information received from external devices in a memory 32 that can be used by the microprocessor 31. Based on the information stored in the memory 32, the microprocessor 31 may control the drive unit 2, steering unit 3, accelerator pedal 4, brake pedal 5, shift lever 6, left and right front wheels 7, left and right rear wheels 8, axle 9, sensors 21-28, etc., which are provided in the vehicle 1. 【0462】 (Summary of the embodiments) As described above, according to one aspect of the present disclosure, a terminal is provided which includes a control unit that controls the receiving operation of the downlink data channel depending on whether or not the uplink time unit in non-time frequency division duplexing operation and / or the time unit in time frequency division duplexing operation overlap with the downlink data channel, and a receiving unit that performs the receiving operation of the downlink data channel based on the controlled receiving operation. 【0463】 According to the above configuration, the downlink data channel can be enhanced for time-frequency division duplex operation. 【0464】 In one embodiment, when the downlink data channel overlaps with the uplink time unit in the non-time frequency division duplexing operation, the control unit may receive the downlink data channel in a time unit that does not overlap with the uplink time unit in the non-time frequency division duplexing operation. According to this embodiment, an enhanced downlink data channel can be provided in both time frequency division duplexing and non-time frequency division duplexing operations. 【0465】 In one embodiment, when the downlink data channel overlaps with the time unit in the time-frequency division duplexing operation, the control unit may control the receiving operation of the downlink data channel regardless of whether the downlink data channel overlaps with the uplink subband in the time unit. According to this embodiment, an enhanced downlink data channel can be provided in both time-frequency division duplexing and non-time-frequency division duplexing operations. 【0466】 In one embodiment, when the downlink data channel overlaps with the time unit in the time-frequency division duplexing operation, the control unit may control the receiving operation of the downlink data channel depending on whether or not the downlink data channel overlaps with the uplink subband in the time unit. According to this embodiment, an enhanced downlink data channel can be provided in both time-frequency division duplexing and non-time-frequency division duplexing operations. 【0467】 Furthermore, according to one aspect of the present disclosure, a base station is provided having a control unit that controls the transmission operation of a downlink data channel in either or both of the uplink time unit in non-time-frequency-division-duplex operation and the time unit in time-frequency-division-duplex operation, and a transmission unit that performs the transmission operation of the downlink data channel by the controlled transmission operation. 【0468】 According to the above configuration, the downlink data channel can be enhanced for time-frequency division duplex operation. 【0469】 Furthermore, according to one aspect of the present disclosure, there is a wireless communication method performed by a terminal, which includes controlling the reception operation of a downlink data channel depending on whether or not the uplink time unit in non-time-frequency-division-duplex operation and / or the time unit in time-frequency-division-duplex operation overlap with the downlink data channel, and performing the reception operation of the downlink data channel by the controlled reception operation. 【0470】 According to the above configuration, the downlink data channel can be enhanced for time-frequency division duplex operation. 【0471】 Furthermore, according to one aspect of the present disclosure, a terminal is provided that includes a control unit that controls the receiving operation of the downlink data channel depending on whether or not the uplink time unit in non-time-frequency-division duplexing operation and / or the time unit in time-frequency-division duplexing operation overlap with the downlink data channel, and a receiving unit that performs the receiving operation of the downlink data channel based on the controlled receiving operation. 【0472】 According to the above configuration, the downlink data channel can be enhanced for time-frequency division duplex operation. 【0473】 In one embodiment, when multiple opportunities of the downlink data channel overlap with the uplink time unit in the non-time frequency division duplexing operation, the control unit may interpret that multiple opportunities of the downlink data channel are not transmitted. According to this embodiment, an enhanced downlink data channel can be provided in both time frequency division duplexing and non-time frequency division duplexing operations. 【0474】 In one embodiment, when multiple opportunities of the downlink data channel overlap with time units in the time-frequency division duplex operation, the control unit may control the receiving operation of the downlink data channel regardless of whether the multiple opportunities of the downlink data channel overlap with the uplink subband in the time unit. According to this embodiment, an enhanced downlink data channel can be provided in both time-frequency division duplex operation and non-time-frequency division duplex operation. 【0475】 In one embodiment, when multiple opportunities of the downlink data channel overlap with time units in the time-frequency division duplexing operation, the control unit may control the receiving operation of the downlink data channel depending on whether the downlink data channel overlaps with the uplink subband in the time unit. According to this embodiment, an enhanced downlink data channel can be provided in both time-frequency division duplexing and non-time-frequency division duplexing operations. 【0476】 Furthermore, according to one aspect of the present disclosure, a base station is provided having a control unit that controls the transmission operation of a downlink data channel in either or both of the uplink time unit in non-time-frequency-division-duplex operation and the time unit in time-frequency-division-duplex operation, and a transmission unit that performs the transmission operation of the downlink data channel by the controlled transmission operation. 【0477】 According to the above configuration, the downlink data channel can be enhanced for time-frequency division duplex operation. 【0478】 Furthermore, according to one aspect of the present disclosure, there is a wireless communication method performed by a terminal, which includes controlling the reception operation of a downlink data channel depending on whether or not the uplink time unit in non-time-frequency-division-duplex operation and / or the time unit in time-frequency-division-duplex operation overlap with the downlink data channel, and performing the reception operation of the downlink data channel by the controlled reception operation. 【0479】 According to the above configuration, the downlink data channel can be enhanced for time-frequency division duplex operation. 【0480】 Furthermore, according to one aspect of the present disclosure, a terminal is provided having a control unit that determines a HARQ-ACK codebook for a downlink data channel depending on whether the downlink data channel overlaps with an uplink time unit, and a transmission unit that transmits a delivery confirmation according to the HARQ-ACK codebook. 【0481】 According to the above configuration, HARQ-ACK can be enhanced for time-frequency division duplex operation. 【0482】 In one embodiment, the control unit may exclude the semi-persistent scheduling (SPS) PDSCH from determining the HARQ-ACK codebook when the SPS PDSCH overlaps with a semi-statically configured uplink symbol. This embodiment provides enhanced HARQ-ACK in both time-frequency division duplex and non-time-frequency division duplex operations. 【0483】 In one embodiment, the control unit may exclude the Start and Length Indicator Value (SLIV) of the downlink data channel from determining the HARQ-ACK codebook when the SLIV overlaps with a semi-statically set uplink symbol. According to this embodiment, an enhanced HARQ-ACK can be provided in both time-frequency division duplex operation and non-time-frequency division duplex operation. 【0484】 In one embodiment, the control unit may determine the HARQ-ACK codebook for the downlink data channel depending on whether the time-frequency division duplex operation is set to semi-static or dynamically notified. According to this embodiment, enhanced HARQ-ACKs can be provided in both time-frequency division duplex and non-time-frequency division duplex operations. 【0485】 Furthermore, according to one aspect of the present disclosure, a base station is provided having a transmitting unit that transmits a downlink data channel, and a receiving unit that receives a delivery confirmation for the downlink data channel according to a HARQ-ACK codebook determined depending on whether the downlink data channel overlaps with an uplink time unit. 【0486】 According to the above configuration, HARQ-ACK can be enhanced for time-frequency division duplex operation. 【0487】 Furthermore, according to one aspect of the present disclosure, there is a wireless communication method performed by a terminal, which includes determining a HARQ-ACK codebook for a downlink data channel depending on whether the downlink data channel overlaps with an uplink time unit, and transmitting a delivery confirmation in accordance with the HARQ-ACK codebook. 【0488】 According to the above configuration, HARQ-ACK can be enhanced for time-frequency division duplex operation. 【0489】 Furthermore, according to one aspect of the present disclosure, a terminal is provided that includes a control unit that controls the transmission operation of an uplink data channel depending on whether or not the uplink data channel overlaps with one or both of the downlink time units in non-time-frequency-division-duplex operation and the time units in time-frequency-division-duplex operation, and a transmission unit that executes the transmission operation of the uplink data channel by the controlled transmission operation. 【0490】 According to the above configuration, the uplink data channel can be enhanced for time-frequency division duplex operation. 【0491】 In one embodiment, when the uplink data channel overlaps with the downlink time unit in the non-time frequency division duplexing operation, the control unit may transmit the uplink data channel in a time unit that does not overlap with the downlink time unit in the non-time frequency division duplexing operation. According to this embodiment, an enhanced uplink data channel can be provided in both time frequency division duplexing and non-time frequency division duplexing operations. 【0492】 In one embodiment, when the uplink data channel overlaps with the time unit in the time-frequency division duplexing operation, the control unit may control the transmission operation of the uplink data channel regardless of whether the uplink data channel overlaps with the downlink subband in the time unit. According to this embodiment, an enhanced uplink data channel can be provided in both time-frequency division duplexing and non-time-frequency division duplexing operations. 【0493】 In one embodiment, when the uplink data channel overlaps with the time unit in the time-frequency division duplexing operation, the control unit may control the transmission operation of the uplink data channel depending on whether or not the uplink data channel overlaps with the downlink subband in the time unit. According to this embodiment, an enhanced uplink data channel can be provided in both time-frequency division duplexing and non-time-frequency division duplexing operations. 【0494】 Furthermore, according to one aspect of the present disclosure, a base station is provided having a control unit that controls the receiving operation of an uplink data channel in either or both of the downlink time unit in non-time-frequency-division-duplex operation and the time unit in time-frequency-division-duplex operation, and a receiving unit that performs the receiving operation of the uplink data channel by the controlled receiving operation. 【0495】 According to the above configuration, the uplink data channel can be enhanced for time-frequency division duplex operation. 【0496】 Furthermore, according to one aspect of the present disclosure, there is a wireless communication method performed by a terminal, which includes controlling the transmission operation of an uplink data channel depending on whether or not the downlink time unit in non-time-frequency-division duplexing operation and / or the time unit in time-frequency-division duplexing operation overlap with the uplink data channel, and performing the transmission operation of the uplink data channel by the controlled transmission operation. 【0497】 According to the above configuration, the uplink data channel can be enhanced for time-frequency division duplex operation. 【0498】 Furthermore, according to one aspect of the present disclosure, a terminal is provided that includes a control unit that controls the transmission operation of an uplink data channel depending on whether or not the uplink data channel overlaps with one or both of the downlink time units in non-time-frequency-division-duplex operation and the time units in time-frequency-division-duplex operation, and a transmission unit that executes the transmission operation of the uplink data channel by the controlled transmission operation. 【0499】 According to the above configuration, the uplink data channel can be enhanced for time-frequency division duplex operation. 【0500】 In one embodiment, the control unit may include a non-time-frequency-division-duplex downlink time unit or a time-frequency-division-duplex time unit as an invalid time unit for repeated transmission of the uplink data channel. According to this embodiment, an enhanced uplink data channel can be provided in both time-frequency-division-duplex and non-time-frequency-division-duplex operations. 【0501】 In one embodiment, the control unit may determine an invalid time unit for repeated transmission of the uplink data channel depending on whether the time-frequency division duplexing is dynamically notified or semi-statically configured. According to this embodiment, an enhanced uplink data channel can be provided in both time-frequency division duplexing and non-time-frequency division duplexing operations. 【0502】 In one embodiment, the control unit may control the transmission operation of the actual repetitions after segmentation for repeated transmission of the uplink data channel, depending on whether or not there is overlap with the downlink subband, when the actual repetitions overlap with the time-frequency division duplex time unit. According to this embodiment, an enhanced uplink data channel can be provided in both time-frequency division duplex operation and non-time-frequency division duplex operation. 【0503】 Furthermore, according to one aspect of the present disclosure, a base station is provided having a control unit that controls the receiving operation of an uplink data channel in either or both of the downlink time unit in non-time frequency division duplexing operation and the time unit in SBFD operation, and a receiving unit that performs the receiving operation of the uplink data channel by the controlled receiving operation. 【0504】 According to the above configuration, the uplink data channel can be enhanced for time-frequency division duplex operation. 【0505】 Furthermore, according to one aspect of the present disclosure, there is a wireless communication method performed by a terminal, which includes controlling the transmission operation of an uplink data channel depending on whether or not the downlink time unit in non-time-frequency-division duplexing operation and / or the time unit in time-frequency-division duplexing operation overlap with the uplink data channel, and performing the transmission operation of the uplink data channel by the controlled transmission operation. 【0506】 According to the above configuration, the uplink data channel can be enhanced for time-frequency division duplex operation. 【0507】 Furthermore, according to one aspect of the present disclosure, a terminal is provided that includes a control unit that controls the transmission operation of the uplink control channel depending on whether or not the downlink time unit in non-time-frequency-division duplexing operation and / or the time unit in time-frequency-division duplexing operation overlap with the uplink control channel, and a transmission unit that executes the transmission operation of the uplink control channel by the controlled transmission operation. 【0508】 According to the above configuration, the uplink control channel can be enhanced for time-frequency division duplex operation. 【0509】 In one embodiment, when the uplink control channel overlaps with the downlink time unit in the non-time frequency division duplexing operation, the control unit may transmit the uplink control channel in time units that do not overlap with the downlink time unit in the non-time frequency division duplexing operation. According to this embodiment, an enhanced uplink control channel can be provided in both time frequency division duplexing and non-time frequency division duplexing operations. 【0510】 In one embodiment, when the uplink control channel overlaps with the time unit in the time-frequency division duplexing operation, the control unit may control the transmission operation of the uplink control channel regardless of whether the uplink control channel overlaps with the downlink subband in the time unit. According to this embodiment, an enhanced uplink control channel can be provided in both time-frequency division duplexing and non-time-frequency division duplexing operations. 【0511】 In one embodiment, when the uplink control channel overlaps with the time unit in the time-frequency division duplexing operation, the control unit may control the transmission operation of the uplink control channel depending on whether or not the uplink control channel overlaps with the downlink subband in the time unit. According to this embodiment, an enhanced uplink control channel can be provided in both time-frequency division duplexing and non-time-frequency division duplexing operations. 【0512】 Furthermore, according to one aspect of the present disclosure, a base station is provided having a control unit that controls the receiving operation of an uplink control channel in either or both of the downlink time unit in non-time frequency division duplexing operation and the time unit in time frequency division duplexing operation, and a receiving unit that performs the receiving operation of the uplink control channel by the controlled receiving operation. 【0513】 According to the above configuration, the uplink control channel can be enhanced for time-frequency division duplex operation. 【0514】 Furthermore, according to one aspect of the present disclosure, there is a wireless communication method performed by a terminal, which includes controlling the transmission operation of the uplink control channel depending on whether or not the downlink time unit in non-time frequency division duplexing operation and / or the time unit in time frequency division duplexing operation overlap with the uplink control channel, and performing the transmission operation of the uplink control channel by the controlled transmission operation. 【0515】 According to the above configuration, the uplink control channel can be enhanced for time-frequency division duplex operation. 【0516】 Furthermore, according to one aspect of the present disclosure, a terminal is provided having a control unit that enables the HARQ-ACK delay operation when the delay conditions for the HARQ-ACK in time-frequency division duplex operation and non-time-frequency division duplex operation are satisfied, and a transmission unit that delays the transmission of the HARQ-ACK on the uplink control channel in accordance with the delay operation. 【0517】 According to the above configuration, the delay operation of HARQ-ACK can be enhanced for time-frequency division duplex operation. 【0518】 In one embodiment, the control unit may enable the delay operation of the semi-persistent scheduling HARQ-ACK (SPS HARQ-ACK) when the HARQ-ACK overlaps with a non-time-frequency-division-duplex semistatic downlink time unit, a synchronous signal block (SSB) time unit, or a type-0 CORESET (Control Resource Set) time unit. According to this embodiment, an enhanced uplink control channel can be provided in both time-frequency-division-duplex and non-time-frequency-division-duplex operations. 【0519】 In one embodiment, the control unit may enable the delay operation of the HARQ-ACK when the semi-persistent scheduling HARQ-ACK (SPS HARQ-ACK) overlaps with a non-time-frequency-division-duplex semistatic downlink time unit, a synchronous signal block (SSB) time unit, or a type-0 CORESET (Control Resource Set) time unit, or overlaps with a time-frequency-division-duplex semistatic / dynamic time unit. According to this embodiment, enhanced HARQ-ACK delay operation can be provided in both time-frequency-division-duplex and non-time-frequency-division-duplex operations. 【0520】 In one embodiment, the control unit may enable the delay operation of the semi-persistent scheduling HARQ-ACK (SPS HARQ-ACK) when the semi-persistent scheduling HARQ-ACK overlaps with a non-SBFD semi-static downlink time unit, a synchronous signal block (SSB) time unit, or a type-0 CORESET (Control Resource Set) time unit, or overlaps with a downlink subband in a time-frequency division duplex semi-static / dynamic time unit. According to this embodiment, enhanced HARQ-ACK delay operation can be provided in both time-frequency division duplex and non-time-frequency division duplex operations. 【0521】 Furthermore, according to one aspect of the present disclosure, a base station is provided, comprising: a transmitting unit that transmits a downlink data channel; and a receiving unit that receives an uplink control channel of the HARQ-ACK that has been delayed according to a delay operation enabled when the delay conditions for the HARQ-ACK in time-frequency division duplexing and non-time-frequency division duplexing for the downlink data channel are met. 【0522】 According to the above configuration, the delay operation of HARQ-ACK can be enhanced for time-frequency division duplex operation. 【0523】 Furthermore, according to one aspect of the present disclosure, there is a wireless communication method performed by a terminal, which includes enabling a HARQ-ACK delay operation when the delay conditions for the HARQ-ACK in time-frequency division duplex operation and non-time-frequency division duplex operation are satisfied, and delaying the transmission of the HARQ-ACK on the uplink control channel in accordance with the delay operation. 【0524】 According to the above configuration, the delay operation of HARQ-ACK can be enhanced for time-frequency division duplex operation. 【0525】 Furthermore, according to one aspect of the present disclosure, a terminal is provided having, in downlink reception of time-frequency division duplex operation, a control unit that adjusts a radio resource instructed by downlink control information with respect to the time domain or frequency domain, and a receiving unit that receives a downlink channel with the adjusted radio resource. 【0526】 The above configuration allows for enhanced preemption for time-frequency division duplex operation. 【0527】 In one embodiment, the control unit may exclude time units set as uplinks by time-division duplex (TDD) settings from the radio resources indicated by the downlink control information. According to this embodiment, enhanced preemption can be provided in both time-frequency division duplex and non-time-frequency division duplex operations. 【0528】 In one embodiment, the control unit may exclude the uplink subband in the time-frequency division duplex operation from the radio resources indicated by the downlink control information. According to this embodiment, enhanced preemption can be provided in both time-frequency division duplex and non-time-frequency division duplex operations. 【0529】 Furthermore, according to one aspect of the present disclosure, a base station is provided that, in a downlink transmission of time-frequency division duplex operation, controls a control unit to cause a terminal to receive a downlink channel in a radio resource that is adjusted in the time domain or frequency domain with respect to a radio resource instructed by downlink control information, and transmits the downlink channel. 【0530】 The above configuration allows for enhanced preemption for time-frequency division duplex operation. 【0531】 Furthermore, according to one aspect of the present disclosure, a wireless communication method is provided that is performed by a terminal, comprising: adjusting a radio resource instructed by downlink control information with respect to the time domain or frequency domain in a downlink reception of time-frequency division duplex operation; and receiving a downlink channel with the adjusted radio resource. 【0532】 The above configuration allows for enhanced preemption for time-frequency division duplex operation. 【0533】 Furthermore, according to one aspect of the present disclosure, a terminal is provided having, in time-frequency division duplexing uplink transmission, a control unit that adjusts a radio resource instructed by downlink control information with respect to the time domain or frequency domain, and a transmission unit that transmits an uplink channel using the adjusted radio resource. 【0534】 According to the above configuration, cancellation can be enhanced for time-frequency division duplex operation. 【0535】 In one embodiment, the control unit may exclude time units set as downlinks by the time-division duplex (TDD) setting from the radio resources indicated by the downlink control information. According to this embodiment, enhanced cancellation can be provided between time-frequency division duplex operation and non-time-frequency division duplex operation. 【0536】 In one embodiment, the control unit may exclude the downlink subband in the time-frequency division duplex operation from the radio resources indicated by the downlink control information. According to this embodiment, enhanced cancellation can be provided in both time-frequency division duplex and non-time-frequency division duplex operations. 【0537】 Furthermore, according to one aspect of the present disclosure, a base station is provided that, in uplink reception of time-frequency division duplex operation, controls the radio resource instructed by downlink control information to transmit an uplink channel to a terminal using a radio resource adjusted in the time domain or frequency domain, and a receiving unit that receives the uplink channel. 【0538】 According to the above configuration, cancellation can be enhanced for time-frequency division duplex operation. 【0539】 Furthermore, according to one aspect of the present disclosure, a wireless communication method is provided that is performed by a terminal, comprising: adjusting a radio resource indicated by downlink control information with respect to the time domain or frequency domain in an uplink transmission of time-frequency division duplex operation; and transmitting an uplink channel with the adjusted radio resource. 【0540】 According to the above configuration, cancellation can be enhanced for time-frequency division duplex operation. 【0541】 (Supplement to the embodiment) As used in this disclosure, the terms “determining” and “determining” may encompass a wide variety of actions. “Determining” may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiry (e.g., searching in a table, database, or other data structure), and ascertaining. “Determining” may also include, for example, receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, and accessing (e.g., accessing data in memory). Furthermore, "judgment" and "decision" can include considering something as having been "judged" or "decided" after resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment" and "decision" can include considering something as having been "judged" or "decided" after some action. Also, "judgment (decision)" can be reinterpreted as "assuming," "expecting," or "considering." 【0542】 The terms “connected,” “coupled,” or any variation thereof, mean any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be reinterpreted as “access.” As used in this disclosure, two elements may be considered to be “connected” or “coupled” with each other using at least one of one or more wires, cables, and printed electrical connections, and, in some non-limiting and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, and optical (both visible and invisible) domain. 【0543】 The reference signal can also be abbreviated as RS (Reference Signal), and may be called a pilot depending on the applicable standard. 【0544】 In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on." 【0545】 Any reference to elements using the designations “first,” “second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, references to the first and second elements do not imply that only two elements may be employed, or that the first element must precede the second element in any way. 【0546】 In the configuration of each of the above devices, "means" may be replaced with "part," "circuit," "device," etc. 【0547】 Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR. 【0548】 A wireless frame may consist of one or more frames in the time domain. Each of these frames in the time domain may be called a subframe. A subframe may further consist of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology. 【0549】 Numerology may be communication parameters applied to at least one of the transmission and reception of a signal or channel. Numerology may include, for example, at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processes performed by the transceiver in the frequency domain, and specific windowing processes performed by the transceiver in the time domain. 【0550】 A slot may consist of one or more symbols in the time domain (such as OFDM (Orthogonal Frequency Division Multiplexing) symbols, SC-FDMA (Single Carrier Frequency Division Multiple Access) symbols, etc.). A slot may also be a time unit based on neurology. 【0551】 A slot may include multiple minislots. Each minislot may consist of one or more symbols in the time domain. Minislots may also be called subslots. Minislots may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (or PUSCH) mapping type B. 【0552】 Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Different names may be used for each of these terms. 【0553】 For example, one subframe may be called a Transmission Time Interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one mini-slot may be called a TTI. In other words, at least one of a subframe and a TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, mini-slot, etc., instead of a subframe. 【0554】 Here, TTI refers to, for example, the smallest unit of time for scheduling in wireless communication. For example, in an LTE system, the base station schedules each user terminal to allocate wireless resources (such as the frequency bandwidth and transmission power available to each user terminal) in TTI units. However, the definition of TTI is not limited to this. 【0555】 TTI may be a transmission time unit for channel-encoded data packets (transport blocks), code blocks, code words, etc., or it may be a processing unit for scheduling, link adaptation, etc. Given a TTI, the actual time interval (e.g., number of symbols) to which the transport block, code block, code word, etc. are mapped may be shorter than the given TTI. 【0556】 Furthermore, if one slot or one mini-slot is referred to as TTI, then one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute the minimum time unit of scheduling. In addition, the number of slots (number of mini-slots) that constitute the minimum time unit of scheduling may be controlled. 【0557】 A TTI with a time length of 1ms may also be called a normal TTI, long TTI, normal subframe, long subframe, slot, etc. A TTI shorter than a normal TTI may also be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, mini slot, sub slot, slot, etc. 【0558】 Furthermore, long TTIs (e.g., normal TTIs, subframes, etc.) may be interpreted as TTIs with a time length exceeding 1 ms, and short TTIs (e.g., shortened TTIs, etc.) may be interpreted as TTIs with a TTI length less than that of a long TTI but 1 ms or more. 【0559】 A resource block (RB) is a resource allocation unit in the time domain and frequency domain, and in the frequency domain, it may contain one or more consecutive subcarriers. The number of subcarriers in an RB may be the same regardless of the neurology, for example, 12. The number of subcarriers in an RB may be determined based on the neurology. 【0560】 Furthermore, the time domain of RB may contain one or more symbols and may be the length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc., may each consist of one or more resource blocks. 【0561】 One or more RBs may also be called a Physical RB (PRB), Sub-Carrier Group (SCG), Resource Element Group (REG), PRB pair, RB pair, etc. 【0562】 Furthermore, a resource block may consist of one or more resource elements (REs). For example, one RE may be a radio resource area comprising one subcarrier and one symbol. 【0563】 A Bandwidth Part (BWP), also known as a partial bandwidth, may represent a subset of consecutive common resource blocks (RBs) for a given neurology in a given carrier. Here, the common RBs may be identified by an index of the RBs relative to the carrier's common reference point. A PRB may be defined and numbered within a BWP. 【0564】 A BWP may include BWPs for UL (UL BWP) and BWPs for DL (DL BWP). One or more BWPs may be configured within a single carrier for a UE. 【0565】 At least one of the configured BWPs may be active, and the UE does not need to assume that it will send or receive a given signal / channel outside of the active BWP. In this disclosure, terms such as "cell" and "carrier" may be read as "BWP". 【0566】 The structures described above, such as wireless frames, subframes, slots, minislots, and symbols, are merely illustrative. For example, the number of subframes included in a wireless frame, the number of slots per subframe or wireless frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, and the number of symbols, symbol length, and cyclic prefix (CP) length within a TTI can be varied in various ways. 【0567】 The term "maximum transmit power" as used in this disclosure may mean the maximum value of the transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power. 【0568】 In this disclosure, if articles are added through translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural. 【0569】 In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combine" may be interpreted similarly to "different." [Explanation of symbols] 【0570】 10 Wireless communication systems 100 base stations (gNB) 200 terminals (UE)
Claims
[Claim 1] A terminal that supports time-frequency division duplexing (SBFD) operation in which the uplink time unit and the downlink time unit are divided into subbands, In the downlink reception of the aforementioned SBFD operation, a control unit adjusts the radio resource instructed by the downlink control information in the time domain or the frequency domain, A receiving unit that receives a downlink channel in the adjusted wireless resource, It has, The downlink channel includes a first downlink data channel corresponding to the first transmission configuration information and a second downlink data channel corresponding to the second transmission configuration information. The control unit individually controls the reception operation of the first and second downlink data channels depending on whether or not there is an overlap between the uplink subband in the SBFD operation and the respective radio resources of the first and second downlink data channels. Terminal. [Claim 2] The control unit drops the first or second downlink data channel that overlaps with the uplink subband and receives the other downlink data channel that does not overlap with the uplink subband. The terminal according to claim 1. [Claim 3] The control unit applies rate matching to the first or second downlink data channel that overlaps with the uplink subband and receives the data using resources excluding the uplink subband. The terminal according to claim 1. [Claim 4] A wireless communication method performed by a terminal that supports time-frequency division duplexing (SBFD) operation in which uplink time units and downlink time units are divided into subbands, In the downlink reception of the aforementioned SBFD operation, the radio resources instructed by the downlink control information are adjusted in the time domain or the frequency domain. The adjusted wireless resource receives a downlink channel. The downlink channel includes a first downlink data channel corresponding to the first transmission configuration information and a second downlink data channel corresponding to the second transmission configuration information. The terminal individually controls the reception operation of the first and second downlink data channels depending on whether or not there is an overlap between the uplink subband in the SBFD operation and the respective radio resources of the first and second downlink data channels. Wireless communication method.