Terminal, base station, and wireless communication method

Abstract

According to one embodiment of the present disclosure, provided is a terminal provided with: a control unit for controlling a transmission operation of an uplink data channel according to whether or not one or both of a downlink time unit in a non-time-frequency division duplex operation and a time unit in a time-frequency division duplex operation overlaps the uplink data channel; and a transmission unit that performs a transmission operation of the uplink data channel by the transmission operation that is controlled.

Description

Technical Field

[0001] The present disclosure relates to a terminal, a base station, and a wireless communication method. Background Art

[0002] In the Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) is standardized for the purpose of further high-speed data rate, low latency, etc. In addition, LTE-Advanced (3GPP Rel. 10-14) is standardized for the purpose of further increasing the capacity and sophistication of LTE (Release (Rel.) 8, 9 of the Third Generation Partnership Project (3GPP)).

[0003] Successor systems of LTE (also known as, for example, 5th generation mobile communication system (5G), 5G+(plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel.15 and later, etc.) are also being studied.

[0004] Prior art literature

[0005] Patent Literature

[0006] Non-patent document 1: “Initial Views on Release 18NR” RP-210293, 3GPP TSG RAN Meeting #91-e Electronic Meeting, March 16-26, 2021 Summary of the invention

[0007] In future wireless communication systems (eg, NR), it is envisioned that a plurality of user terminals (user terminals, User Equipment (UE)) communicate in an ultra-high density and high traffic environment.

[0008] It is assumed that in such an environment, uplink (UL) resources are insufficient compared to downlink (DL) resources.

[0009] However, currently, there is not enough research on the method of increasing uplink resources. If this method cannot be properly controlled, there is a concern that system performance may be degraded, such as increased delay and reduced coverage performance.

[0010] Therefore, one of the objects of the present disclosure is to provide a terminal, a base station, and a wireless communication method that improve resource utilization efficiency.

[0011] One method of the present disclosure relates to a terminal, which has: a control unit, which controls the receiving operation of the downlink data channel according to whether one or both of the uplink time unit in the non-time frequency division duplex operation and the time unit in the time frequency division duplex operation overlap with the downlink data channel; and a receiving unit, which performs the receiving operation of the downlink data channel through the controlled receiving operation.

[0012] Another embodiment of the present disclosure relates to a terminal including: a control unit that determines a HARQ-ACK codebook for a downlink data channel according to 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.

[0013] Another embodiment of the present disclosure relates to a terminal, which comprises: a control unit, which controls the sending operation of the uplink data channel according to whether one or both of the downlink time unit in non-time-frequency division duplex operation and the time unit in time-frequency division duplex operation overlap with the uplink data channel; and a sending unit, which performs the sending operation of the uplink data channel through the controlled sending operation.

[0014] Another embodiment of the present disclosure relates to a terminal, which comprises: a control unit, which controls the sending operation of the uplink control channel according to whether one or both of the downlink time unit in non-time-frequency division duplex operation and the time unit in time-frequency division duplex operation overlap with the uplink control channel; and a sending unit, which performs the sending operation of the uplink control channel through the controlled sending operation.

[0015] Another embodiment of the present disclosure relates to a terminal, which comprises: a control unit, which enables a deferred operation of the HARQ-ACK when a deferred condition of the HARQ-ACK in a time-frequency division duplex operation and a non-time-frequency division duplex operation is met; and a sending unit, which delays the sending of an uplink control channel of the HARQ-ACK in accordance with the deferred operation.

[0016] Another embodiment of the present disclosure relates to a terminal comprising: a control unit, which adjusts the wireless resources indicated by downlink control information with respect to the time domain or the frequency domain in downlink reception of time-frequency division duplex operation; and a receiving unit, which receives a downlink channel in the adjusted wireless resources.

[0017] Another embodiment of the present disclosure relates to a terminal comprising: a control unit, which adjusts the wireless resources indicated by downlink control information with respect to the time domain or the frequency domain in uplink transmission of time-frequency division duplex operation; and a sending unit, which sends an uplink channel in the adjusted wireless resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 It is a block diagram showing the functional structure of a base station (gNB) according to an embodiment of the present disclosure.

[0019] Figure 2 It is a block diagram showing the functional structure of a terminal (UE) according to an embodiment of the present disclosure.

[0020] Figure 3A as well as Figure 3B This is a diagram showing an example of configuration of radio resources of XDD (Cross Division Duplex) or SBFD (Subband non-overlapping Full Duplex) according to an embodiment of the present disclosure.

[0021] Figure 4 is a diagram illustrating an XDD operation or a SBFD operation according to an embodiment of the present disclosure.

[0022] Figure 5A as well as Figure 5B FIG. 5 is a diagram showing TDD (non-SBFD) and SBFD according to an embodiment of the present disclosure.

[0023] Figure 6A to Figure 6E is a diagram showing a pure time unit and a SBFD time unit according to an embodiment of the present disclosure.

[0024] Figure 7 It is a diagram showing a single TRPPDSCH using slot based PDSCH repetition based on Rel-15 NR.

[0025] Figure 8A to Figure 8C It is a diagram showing PDSCH transmission based on Rel-15 / 16 NR.

[0026] Fig. 9It is a diagram showing a multi-TRP PDSCH transmission method based on a single DCI based on Rel-16 NR.

[0027] Fig. 10A as well as Fig. 10B It is a diagram showing Type 1 HARQ-ACK based on Rel-15 / 16 / 17NR.

[0028] Fig.11 is a diagram showing candidate PDSCH reception opportunities based on Rel-16 NR.

[0029] Fig.12 2 is a diagram showing HARQ-ACK opportunities associated with candidate PDSCH reception based on Rel-16 NR.

[0030] Fig.13 2 is a diagram showing a semi-persistent scheduling (SPS) HARQ-ACK codebook (CB) based on Rel-15 / 16 / 17 NR.

[0031] Fig.14 It is a diagram showing multi-PDSCH scheduling based on Rel-15 / 16 / 17 NR.

[0032] Fig.15 is a diagram illustrating PDSCH enhancement for SBFD operation according to an embodiment of the present disclosure.

[0033] Fig.16 is a diagram illustrating PDSCH enhancement for SBFD operation according to an embodiment of the present disclosure.

[0034] Fig.17 is a diagram illustrating PDSCH enhancement for SBFD operation according to an embodiment of the present disclosure.

[0035] Fig.18 is a diagram illustrating PDSCH enhancement for SBFD operation according to an embodiment of the present disclosure.

[0036] Fig.19 is a diagram illustrating PDSCH enhancement for SBFD operation according to an embodiment of the present disclosure.

[0037] Fig. 20 is a diagram illustrating PDSCH enhancement for SBFD operation according to an embodiment of the present disclosure.

[0038] Fig.21A as well as Fig. 21B It is a diagram showing a single TRP PUSCH based on Rel-15 / 16NR.

[0039] Fig. 22 It is a diagram showing time division multiplexing (TDM) multi-TRP PUSCH repetitions A and B of NR based on Rel-17.

[0040] Fig.23 It is a diagram showing multi-PUSCH scheduling based on Rel-15 / 16 / 17 NR.

[0041] Fig.24 is a diagram illustrating PUSCH enhancement for SBFD operation according to an embodiment of the present disclosure.

[0042] Fig.25 It is a diagram showing PUCCH repetition based on Rel-15 / 16 NR.

[0043] Fig.26 is a diagram showing an SPS HARQ-ACK deferral operation based on Rel-17 NR.

[0044] Fig. 27 is a diagram illustrating PUCCH enhancement for SBFD operation according to an embodiment of the present disclosure.

[0045] Fig.28 It is a diagram showing DCI 2_1-based preemption based on Rel-15 / 16 / 17NR.

[0046] Fig.29 is a diagram illustrating preemption enhancement for SBFD operation according to an embodiment of the present disclosure.

[0047] Fig.30 is a diagram illustrating preemption enhancement for SBFD operation according to an embodiment of the present disclosure.

[0048] Fig.31 is a diagram illustrating preemption enhancement for SBFD operation according to an embodiment of the present disclosure.

[0049] Fig.32 is a diagram illustrating preemption enhancement for SBFD operation according to an embodiment of the present disclosure.

[0050] Fig.33 It is a diagram showing cancellation based on DCI 2_4 based on Rel-15 / 16 / 17NR.

[0051] Fig.34 FIG. 4 is a diagram illustrating cancellation enhancement for SBFD operation according to an embodiment of the present disclosure.

[0052] Fig.35 FIG. 4 is a diagram illustrating cancellation enhancement for SBFD operation according to an embodiment of the present disclosure.

[0053] Fig.36 FIG. 4 is a diagram illustrating cancellation enhancement for SBFD operation according to an embodiment of the present disclosure.

[0054] Fig.37 FIG. 4 is a diagram illustrating cancellation enhancement for SBFD operation according to an embodiment of the present disclosure.

[0055] Fig.38 It is a block diagram showing the hardware structure of a base station and a terminal according to an embodiment of the present disclosure.

[0056] Fig.39 Detailed description of the invention is a block diagram showing a hardware structure of a vehicle according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0057] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings.

[0058] (Wireless Communication System)

[0059] The structure of a wireless communication system according to an embodiment of the present disclosure is described below. In the wireless communication system, communication is performed using any one of the wireless communication methods according to the above embodiments of the present disclosure or a combination thereof. The wireless communication system is a system that implements communication using Long Term Evolution (LTE) standardized by the Third Generation Partnership Project (3GPP), the fifth generation mobile communication system New Radio (5GNR), and their subsequent wireless communication systems.

[0060] In addition, the wireless communication system can also support dual connectivity (Multi-RAT Dual Connectivity (MR-DC)) between multiple Radio Access Technologies (Radio Access Technology (RAT)). MR-DC can also 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)), etc.

[0061] In EN-DC, the base station (eNB) of LTE (E-UTRA) is the master node (Master Node (MN)), and the base station (gNB) of NR is the secondary node (Secondary Node (SN)). In NE-DC, the base station (gNB) of NR is the MN, and the base station (eNB) of LTE (E-UTRA) is the SN.

[0062] The wireless communication system can also support dual connectivity between multiple base stations within the same RAT (for example, dual connectivity (NR-NR Dual Connectivity (NN-DC)) where both MN and SN are NR base stations (gNB)).

[0063] The wireless communication system may also include a base station forming a macro cell C1 with a relatively wide coverage, and a base station configured in the macro cell C1 and forming a small cell C2 narrower than the macro cell C1. The terminal (UE) may also be located in at least one cell. The configuration and number of each cell and terminal are not limited to a specific method.

[0064] The terminal may be connected to at least one of the plurality of base stations. The terminal may use at least one of carrier aggregation (CA) using a plurality of component carriers (CC) and dual connectivity (DC).

[0065] Each CC may also be included in at least one of the first frequency band (Frequency Range 1 (FR1)) and the second frequency band (Frequency Range 2 (FR2)). The macro cell C1 may also be included in FR1, and the small cell C2 may also be included in FR2. For example, FR1 may be a frequency band below 6 GHz (lower than 6 GHz (sub-6 GHz)), and FR2 may be a frequency band higher than 24 GHz (higher than 24 GHz (above-24 GHz)). In addition, the frequency bands and definitions of FR1 and FR2 are not limited to these. For example, FR1 may also be equivalent to a frequency band higher than FR2.

[0066] Furthermore, the terminal may perform communication using at least one of time division duplex (TDD) and frequency division duplex (FDD) in each CC.

[0067] Multiple base stations can also be connected by wire (for example, optical fiber based on Common Public Radio Interface (CPRI)), X2 interface, etc.) or wireless (for example, NR communication). For example, when NR communication between two base stations is used as a backhaul, the base station equivalent to the upper station can also be called an Integrated Access Backhaul (IAB) donor, and the base station equivalent to a relay station (relay) can also be called an IAB node.

[0068] The base station may also be connected to the core network via other base stations or directly. The core network may also include at least one of Evolved Packet Core (EPC), 5G Core Network (5GCN), Next Generation Core (NGC), etc.

[0069] The terminal may also be a terminal that supports at least one of communication modes such as LTE, LTE-A, 5G, and 6G.

[0070] In a wireless communication system, a wireless access method based on orthogonal frequency division multiplexing (OFDM) may also be used. For example, in at least one of the downlink (DL) and the uplink (UL), 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 also be used.

[0071] The radio access scheme may also be referred to as a waveform. In addition, in the wireless communication system, other radio access schemes (for example, other single-carrier transmission schemes, other multi-carrier transmission schemes) may also be used in the UL and DL radio access schemes.

[0072] In a wireless communication system, a downlink shared channel (Physical Downlink Shared Channel (PDSCH))), a broadcast channel (Physical Broadcast Channel (PBCH))), a downlink control channel (Physical Downlink Control Channel (PDCCH)) shared by each terminal, etc. can also be used as a downlink channel.

[0073] In addition, in a wireless communication system, an uplink shared channel (Physical Uplink Shared Channel (PUSCH))) shared by each terminal, an uplink control channel (Physical Uplink Control Channel (PUCCH))), a random access channel (Physical Random Access Channel (PRACH)) and the like may be used as uplink channels.

[0074] The PDSCH transmits user data, high-layer control information, and a system information block (SIB). The PUSCH transmits user data, high-layer control information, and a master information block (MIB). The PBCH transmits a master information block (MIB).

[0075] Lower layer control information may also be transmitted via the PDCCH. The lower layer control information may include, for example, downlink control information (Downlink Control Information (DCI)) including scheduling information of at least one of the PDSCH and the PUSCH.

[0076] In addition, the DCI for scheduling the PDSCH may also be referred to as DL allocation, DL DCI, etc., and the DCI for scheduling the PUSCH may also be referred to as UL grant, UL DCI, etc. In addition, the PDSCH may also be rewritten as DL data, and the PUSCH may also be rewritten as UL data.

[0077] In the detection of PDCCH, control resource set (CORESET) and search space can also be used. CORESET corresponds to the resources for searching DCI. Search space corresponds to the search area and search method for PDCCH candidates. A CORESET can also be associated with one or more search spaces. UE can also monitor the CORESET associated with a search space based on the search space setting.

[0078] A search space may also correspond to a PDCCH candidate corresponding to one or more aggregation levels. One or more search spaces may also be referred to as a search space (SS) set. In addition, the "search space", "search space set", "search space setting", "search space set setting", "CORESET", "CORESET setting" and the like in the present disclosure may also be rewritten mutually.

[0079] Through PUCCH, uplink control information (Uplink Control Information (UCI)) including at least one of channel state information (CSI), delivery confirmation information (e.g., also called hybrid automatic repeat request confirmation (HARQ-ACK), ACK / NACK, etc.) and scheduling request (SR) can also be sent. Through PRACH, a random access preamble code for establishing a connection with a cell can also be sent.

[0080] In addition, in the present disclosure, various channels may be expressed without the word “Physical” at the beginning.

[0081] In wireless communication systems, synchronization signals (Synchronization Signal (SS)), downlink reference signals (Downlink Reference Signal (DL-RS)), etc. can also be sent. In wireless communication systems, cell-specific reference signals (Cell-specific Reference Signal (CRS)), channel state information reference signals (Channel State Information Reference Signal (CSI-RS)), demodulation reference signals (DeModulation Reference Signal (DMRS)), positioning reference signals (Positioning Reference Signal (PRS)), phase tracking reference signals (Phase Tracking Reference Signal (PTRS)), etc. can also be sent as DL-RS.

[0082] 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 also be referred to as SS / PBCH block, SS block (SSB), etc. In addition, SS, SSB, etc. may also be referred to as reference signals.

[0083] In addition, in a wireless communication system, as an uplink reference signal (Uplink Reference Signal (UL-RS)), a measurement reference signal (Sounding Reference Signal (SRS)), a demodulation reference signal (DMRS), etc. can also be sent. In addition, DMRS can also be called a UE-specific reference signal (UE-specific Reference Signal).

[0084] (Device Structure)

[0085] Next, the functional configuration examples of the base station (gNB) 100 and the terminal (UE) 200 that perform the processing and operations described below are described. The gNB 100 and the UE 200 include functions for implementing the embodiments described below. However, the gNB 100 and the UE 200 may each have only a part of the functions in the embodiments.

[0086] (gNB100)

[0087] Figure 1 is a diagram showing an example of the functional structure of gNB100. Figure 1 As shown, gNB100 has a receiving unit 101, a sending unit 102 and a control unit 103. Figure 1 The functional configuration shown is merely an example, and any functional divisions and names of functional units may be used as long as the operations according to the embodiments of the present invention can be implemented.

[0088] The receiving unit 101 includes a function of receiving various signals transmitted from the UE 200 and acquiring, for example, higher layer information based on the received signals. The transmitting unit 102 includes a function of generating a signal to be transmitted to the UE 200 and transmitting the signal by wire or wirelessly.

[0089] The control unit 103 stores the preset setting information and various setting information sent to the UE 200 in the storage device, and reads it from the storage device as needed. In addition, the control unit 103 performs processing related to communication with the UE 200. The functional unit related to signal transmission in the control unit 103 may be included in the transmission unit 102, and the functional unit related to signal reception in the control unit 103 may be included in the reception unit 101.

[0090] (UE200)

[0091] Figure 2 2 is a diagram showing an example of a functional structure of UE 200. Figure 2 As shown, UE 200 has a sending unit 201 , a receiving unit 202 and a control unit 203 . Figure 2 The functional configuration shown is merely an example, and any functional divisions and names of functional units may be used as long as the operations according to the embodiments of the present invention can be implemented.

[0092] The transmitting unit 201 generates a transmission signal based on the transmission data and transmits the transmission signal wirelessly. The receiving unit 202 receives various signals wirelessly and obtains a higher layer signal based on the received physical layer signal. In addition, the receiving unit 202 has a function of receiving NR-PSS, NR-SSS, NR-PBCH, DL / UL control signals or reference signals, etc. transmitted from the gNB 100.

[0093] The control unit 203 stores various setting information received from the gNB 100 through the receiving unit 202 in the storage device, and reads it from the storage device as needed. In addition, the control unit 203 performs processing related to communication with the gNB 100. The functional unit related to signal transmission in the control unit 203 may be included in the transmitting unit 201, and the functional unit related to signal reception in the control unit 203 may be included in the receiving unit 202.

[0094] (SBFD Operation)

[0095] If the time ratio of transmission and reception based on time division duplex (TDD) up to Rel.16 is considered (for example, DL:UL=4:1), consider the situation where the transmission opportunities of UL signals / channels become fewer relative to the reception opportunities of DL signals / channels. In such a situation, there is a concern that UE200 may not be able to frequently transmit UL signals / channels, resulting in transmission delays of important UL signals / channels. In addition, since the number of UL transmission opportunities is reduced compared to DL reception opportunities, there is also a concern about signal / channel congestion in the UL transmission opportunities. Furthermore, in TDD, since the time resources that can transmit UL signals / channels are limited, the application of UL coverage enhancement technology based on repeated transmission (repetition), for example, also becomes restrictive.

[0096] In future wireless communication systems (for example, Rel. 18 and later), introduction of a time frequency division duplex method combining TDD and frequency division duplex (FDD) for UL and DL is under study.

[0097] An example of the time-frequency division duplex method is XDD (Cross Division Duplex) or Subband non-overlapping Full Duplex (SBFD). XDD or SBFD may also refer to a duplex method that frequency-division multiplexes DL and UL in one component carrier (CC) in the TDD band (capable of using DL and UL simultaneously).

[0098] Figure 3A This is a diagram showing an example of TDD settings specified up to Rel.16. Figure 3A In the example shown, a TDD time slot or symbol is configured for a UE in a bandwidth such as a component carrier (CC) (also referred to as a cell, a serving cell), a bandwidth part (BWP), etc.

[0099] exist Figure 3A In the example shown, the time ratio of the DL slot to the UL slot is 4: 1. In such a configuration of slots or symbols in conventional TDD, sufficient UL time resources cannot be secured, and there is a concern that UL transmission delay may occur and coverage performance may be degraded.

[0100] Figure 3B FIG. 1 is a diagram showing an example of the structure of SBFD. Figure 3B In the example shown, resources for DL ​​reception and resources for UL transmission overlap in time in one component carrier (CC). According to such a resource structure, more UL resources can be secured, and the utilization efficiency of resources can be improved.

[0101] For example, Figure 3B As shown in the example, it is also possible to set the two ends of the frequency domain as DL resources, and use these DL resources to clamp the UL resources. In this way, it is possible to avoid and mitigate the generation of cross link interference (Cross Link Interference (CLI)) with adjacent carriers. In addition, a protection area can also be set at the boundary between DL resources and UL resources.

[0102] Considering the complexity of processing self-interference, it is possible to consider using both DL resources and UL resources by only the base station 100. That is, in radio resources where DL and UL overlap in time, it is possible to set a certain UE 200 to use DL resources and other UEs 200 to use UL resources.

[0103] Figure 4 FIG. 1 is a diagram showing an example of SBFD operation. Figure 4 In the illustrated example, part of the DL resources constituting the TDD band is set as UL resources, and the DL and UL partially overlap in the time domain.

[0104] exist Figure 4 In the example shown, during the DL-only period, multiple UEs 200 (in Figure 4 Receive DL channel / signal for each of UE#1 and UE#2).

[0105] In addition, during the period when DL and UL overlap in time, a certain UE 200 (in Figure 4 In the example of UE#1) receiving DL channel / signal, other UE200 (in Figure 4 In the example of UE#2), the UL channel / signal is sent. During this period, the base station 100 performs simultaneous transmission and reception of DL and UL.

[0106] Furthermore, during the UL-only period, multiple UEs 200 (in Figure 4UL channel / signal is sent to each of UE#1 and UE#2).

[0107] In the existing NR (for example, as specified up to Rel.15 / 16 / 17), the DL frequency resource and UL frequency resource in the carrier for UE are set as DL BWP and UL BWP respectively. In order to switch the DL / UL frequency resource to other DL / UL frequency resources, multiple BWP settings and BWP adaptation mechanisms are required.

[0108] In addition, in the existing NR, such as Figure 5A As shown, the time resources (time units such as symbols and time slots) in the TDD carrier used by UE200 are configured as at least one of DL, UL and flexible (FL) in the TDD configuration.

[0109] like Figure 5B As shown, the SBFD symbol may also be a symbol that is notified or set as UL (or DL) on a certain frequency resource (subband), or is notified or set for UL transmission (or DL ​​reception), and on the other hand, is notified or set as DL (or UL) on other frequency resources (subband), or is notified or set for DL ​​reception (or UL transmission). Alternatively, the SBFD symbol may be a symbol that is notified or set as UL (or DL) on a part of the frequency resources, or is 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 part of the frequency resources, or is notified or set for DL ​​reception (or UL transmission).

[0110] Here, the time unit is a symbol level, a slot / subslot level, or a group of symbols / slots / subslots. That is, the SBFD time unit may also be a SBFD symbol, a slot / subslot containing a SBFD symbol or overlapping, or a group of symbols / slots / subslots containing a SBFD symbol or overlapping.

[0111] A pure time unit may also be a non-SBFD symbol (i.e., a symbol that is not a SBFD symbol), a slot / sub-slot that does not contain a SBFD symbol or does not overlap, or a group of symbols / slots / sub-slots that does not contain a SBFD symbol or does not overlap, which may also be referred to as a non-SBFD time unit. Fig. 6A As shown, the pure time unit can also be referred to as a time unit consisting only of DL on the frequency resource. In addition, as Figure 6B As shown, it can also be referenced as a time unit consisting only of UL on the frequency resource.

[0112] In addition, for the SBFD time unit, the DL resources and UL resources may also have various configuration modes in the frequency domain. For example, the SBFD time unit of the frequency domain mode #1 may also have the following configuration modes: Figure 6C In addition, the SBFD time unit of frequency domain mode #2 can also have the following configuration mode: Fig.6D In addition, the SBFD time unit of frequency domain mode #3 can also have the following configuration mode: Fig. 6E The configuration modes shown are merely examples, and other configuration modes may also be used. The frequency domain mode of the SBFD time unit may also refer to a resource repetition mode in the frequency domain for the SBFD time unit.

[0113] (Terms related to SBFD operations)

[0114] In this specification, the terms related to the SBFD operation described later may have the following meanings. In addition, the term "SBFD" here may also be rewritten as "time-frequency division duplex". The so-called "SBFD semi-static UL codeword" is a SBFD codeword that is set to UL through tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

[0115] The so-called "SBFD dynamic UL codeword is a SBFD codeword that is set to flexible (FL) through tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated and is notified as UL through DCI 2_0.

[0116] The so-called "SBFD semi-static DL codeword is a SBFD codeword set to DL through tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

[0117] The so-called "SBFD dynamic DL codeword is a SBFD codeword that is set to FL through tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated and is notified as DL through DCI 2_0.

[0118] The so-called "SBFD semi-static FL codeword is a SBFD codeword that is set to FL by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

[0119] The so-called "SBFD dynamic FL codeword is a SBFD codeword that is set to FL through tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated and is notified as FL through DCI 2_0.

[0120] The so-called “non-SBFD semi-static UL codeword” is a non-SBFD codeword configured as UL through tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

[0121] The so-called “non-SBFD dynamic UL codeword” is set to FL through tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, and is notified as a non-SBFD codeword of UL through DCI 2_0.

[0122] The so-called “non-SBFD semi-static DL symbol” is a non-SBFD symbol set as DL through tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

[0123] The so-called "non-SBFD dynamic DL codeword is set to FL through tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, and is notified as a non-SBFD codeword of DL through DCI 2_0.

[0124] The so-called “non-SBFD semi-static FL symbol” is a non-SBFD symbol that is set to FL by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

[0125] The so-called “non-SBFD dynamic FL codeword” is a non-SBFD codeword that is set to FL through tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated and is notified as FL through DCI 2_0.

[0126] (PDSCH in Rel-15 / 16 / 17)

[0127] Regarding the TDD conflict of PDSCH, i.e., the overlap of resources used for PDSCH reception and resources scheduled as uplink, according to Rel-15 / 16 / 17, it is stipulated that PDSCH or PDSCH repetitions overlapping with semi-static UL symbols are not received. That is, it is stipulated that for the symbol set of the time slot notified to the UE as uplink through tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, when PDCCH, PDSCH or CSI-RS only partially overlaps with the symbol set of the time slot, the UE does not receive PDCCH, PDSCH or CSI-RS.

[0128] In addition, it is stipulated that when the UE is scheduled through the DCI format to receive PDSCH across multiple time slots, and when tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated is for a time slot of these multiple time slots, and when at least one codeword of the codeword set scheduled for PDSCH reception by the UE in the time slot is an uplink codeword, the UE does not receive PDSCH in the time slot.

[0129] In addition, according to Rel-15 / 16 / 17, it is stipulated that PDSCH or PDSCH overlapping with dynamic UL / FL codewords is not received repeatedly. That is, it is stipulated that the UE is set to receive CSI-RS or PDSCH in the codeword set of the time slot by the upper layer, and in addition, when the UE detects DCI format 2_0 based on a time slot format value other than 255 for notifying the time slot format as an uplink or flexible and having a codeword subset from the codeword set, or when the UE detects a DCI format for notifying the UE to send PUSCH, PUCCH, SRS or PRACH in at least one codeword in the codeword set, the UE cancels the CSI-RS reception in the codeword set of the time slot, or cancels the PDSCH reception in the time slot.

[0130] Rel-15 NR supports single transmit receive point (s-TRP) PDSCH based on no repetition or slot-based PDSCH repetition. For example, in slot-based PDSCH repetition, Figure 7 As shown, PDSCH repetitions can be transmitted over multiple time slots. Here, in s-TRP PDSCH transmission, Fig. 8A As shown, a single PDCCH schedules a single PDSCH for a single TRP.

[0131] In addition, Rel-16 NR supports two mechanisms for multiple transmit reception point (m-TRP) / panel PDSCH transmission, single PDCCH-based m-TRP / panel transmission and multi-PDCCH-based m-TRP / panel transmission.

[0132] In single-PDCCH based m-TRP / panel transmission, a single PDCCH schedules multiple PDSCHs of multiple TRPs. Figure 8B As shown, PDCCH 1 schedules PDSCH 1 / layer 1 and PDSCH 2 / layer 2.

[0133] On the other hand, in a multi-PDCCH based m-TRP / panel transmission, each of the multiple PDCCHs schedules a single PDSCH for each TRP. Figure 8C As shown, PDCCH 1 schedules PDSCH 1 / codeword (CW) 1, and PDCCH 2 schedules PDSCH 2 / CW 2.

[0134] In addition, Rel-16 NR supports five methods for m-TRP PDSCH transmission based on single DCI (s-DCI). Specifically, Fig. 9 As shown, five modes are supported: SDM (1a), FDMschemeA (2a), FDMschemeB (2b), TDMschemeA (3) and TDMschemeB (4).

[0135] Here, for FDMSchemeA or FDMSchemeB, Fig. 9 As shown, the allocated resource blocks (RBs) notified through frequency domain resource allocation (FDRA) are separated into a first RB set for the first TRP (PDSCH from TRP#1) and a second RB set for the second TRP (PDSCH from TRP#2).

[0136] In addition, regarding the transport block size (TBS) of PDSCH, section 5.1.3.2 of TS38.214 specifies a TBS determination process consisting of steps 1 to 3. In step 1, the UE first determines the number of REs in the time slot (N RE In step 2, the UE calculates the number of REs (N RE )Get the intermediate variable (N info Then, in step 3, the UE calculates the value of the intermediate variable (N info ) decides TBS.

[0137] It is specified that for s-DCI-based m-TRP PDSCH based on FDMschemeA, the number of REs used for TBS calculation is determined based on the codewords of the first TCI state, that is, not based on the total codewords in the time slot. On the other hand, it is specified that for s-DCI-based m-TRP PDSCH based on FDMschemeB, the number of REs used for TBS calculation is determined based on the RBs of the first TCI state, that is, not based on the RBs notified through FDRA.

[0138] (HARQ-ACK CB)

[0139] Regarding generation of the HARQ-ACK codebook (CB) for semi-persistent scheduling (SPS), section 9.1.2 of TS38.213 specifies that when an SPS PDSCH or each repetition of the SPS PDSCH overlaps with a semi-static UL symbol, the SPS PDSCH is excluded from the HARQ-ACK CB.

[0140] In addition, regarding the generation of Type 1 HARQ-ACK CB, 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 semi-static UL codeword, SLIV is deleted from the candidate TDRA.

[0141] Here, the generation of Type 1 HARQ-ACK CB (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, based on the set K1 set, the PDSCH time slot window is determined. For example, in Fig. 10A In the example shown, if we assume μ DL =μ UL , then the K1 set C(K1) is {1,2,3,4}. In addition, Fig. 10B In the example shown, if we assume μ DL >μ UL , then the K1 set C(K1) is {1,2,3,4}.

[0142] Then, in step A-2, for each K1, the candidate PDSCH reception opportunities in each time slot are determined. That is, the candidate PDSCH reception opportunities can also be associated with the TDRA table set R. In addition, the candidate PDSCH reception opportunities in the time domain RA table that overlap with the UL set by tdd-UL-UL-ConfigurationCommon and tdd-UL-UL-ConfigurationDedicated can also be excluded. In addition, when determining the candidate PDSCH reception opportunities, the SLIVs that overlap with the semi-static UL codewords can also be deleted. In addition, for the candidate PDSCH reception opportunities that overlap in the time domain, the candidate PDSCH reception opportunities can also be generated based on specific rules. For example, the M of the serving cell c in Rel-16 A，c You can also Fig.11 As shown in .

[0143] Next, in step B, the UE performs a ACK The HARQ-ACK information bits determine

[0144] [Mathematical formula 1]

[0145] HARQ-ACK information bits. Fig.12 As shown, for the determination of the candidate PDSCH reception opportunities in slot n (for example, the last two symbols may be semi-statically set to UL), with respect to row indexes (RI) 2, 3, and 8, these candidate PDSCH reception opportunities overlap with the semi-static UL symbols and may be excluded from the generation of HARQ-ACK bits. That is, HARQ-ACK bits for these candidate PDSCH reception opportunities may not be generated.

[0146] In addition, in the generation of the HARQ-ACK CB for the SPS PDSCH, for the ordering, the ascending order of the serving cell index, the ascending order of the SPS setting index, and the ascending order of the time slot index are applied. It is stipulated that when each repetition of the SPS PDSCH overlaps with the semi-static UL codeword, the SPS PDSCH is deleted. Therefore, when generating the HARQ-ACK CB for only the SPS PDSCH, each repetition of the SPS PDSCH or SPS PDSCH overlapping with the semi-static UL codeword can be excluded from the HARQ-ACK CB. That is, the HARQ-ACK bits for each repetition of these SPS PDSCH or SPS PDSCH may not be generated.

[0147] For example, in Fig.13In the example shown, since SPS PDSCH #2 and #3 overlap with the semi-static UL symbol, they are excluded from the SPS HARQ-ACK CB, and the HARQ-ACK CB includes only ACK / NACK for SPS PDSCH #1 and #4.

[0148] (Multi-PDSCH Scheduling)

[0149] When scheduling multiple PDSCHs, DCI 1_1 is used as the DCI format. Fig.14 As shown, PDSCH#1~#4 can be scheduled by one DCI. In Rel-15 / 16 / 17 NR, it is stipulated that 120, 480, 960kHz SCS is supported, and the maximum number of PDSCHs that can be scheduled by one DCI is 8. In addition, for TDRA, different {SLIV, mapping type, scheduling offset K0} can be applied to each PDSCH in the row of the TDRA table. In the case of a collision between a PDSCH and a semi-static UL codeword, the PDSCH is cancelled, but it is not assumed that all PDSCHs are cancelled.

[0150] In addition, the MCS, NDI, and RV of the first or second TB field appear only once and can be applied to the first TB of each PDSCH. In addition, it is specified that the HPN field is applied to the initial valid PDSCH and incremented by 1 for subsequent PDSCHs, and not incremented for invalid PDSCHs (i.e., PDSCHs that conflict with semi-static UL symbols).

[0151] [Study items related to PDSCH enhancement for SBFD operation]

[0152] For SBFD operations in Rel-18, the following contents are studied.

[0153] SBFD operation in DL symbols, i.e. DL and UL subbands in DL symbols

[0154] SBFD operation in UL symbols, i.e. DL and UL subbands in UL symbols

[0155] SBFD operation in FL symbols, i.e. DL and UL subbands in FL symbols

[0156] Here, when SBFD operation in UL symbols is supported or enabled, PDSCH or PDSCH repetitions overlapping with UL symbols may not necessarily be discarded. On the other hand, when PDSCH or PDSCH repetitions overlapping with UL symbols are not discarded, it may be necessary to report HARQ-ACK or other delivery confirmation for PDSCH or PDSCH repetitions received in the UE. Therefore, the rules for TDD conflicts in Rel-15 / 16 / 17 may need to be updated for SBFD operation.

[0157] That is, we can discuss

[0158] Case 1: PDSCH or PDSCH repetition overlapped with UL symbols in non-SBFD operation

[0159] Case 2: PDSCH or PDSCH repetition overlapping with DL or UL symbols in SBFD operation

[0160] These two situations.

[0161] For example, UL symbols or time slots and DL symbols or time slots are set to be transmitted through tdd-UL-DL-ConfigurationCommon as Fig.15 In this case, according to the rules of Rel-15 / 16 / 17, PDSCH rep#3 and PDSCH rep#4 of PDSCH repetition are discarded. On the other hand, if SBFD operation is considered, PDSCH rep#3 can be sent in the DL subband, so it can be considered that the UE can receive PDSCH rep#3.

[0162] [Proposal 1]

[0163] In Proposal 1, PDSCH enhancement for time-frequency division duplex operation such as SBFD operation is described. Specifically, the PDSCH drop rule is extended for SBFD operation as follows.

[0164] Case 1: PDSCH resources overlap with non-SBFD UL symbols

[0165] <Alt-A>

[0166] The UE does not receive PDSCH.

[0167] <Alt-B>

[0168] The UE assumes that transmission of the PDSCH is postponed to a later time slot that does not overlap with non-SBFD UL symbols or FL symbols.

[0169] Case 2: PDSCH resources overlap with SBFD symbols

[0170] <Alt 0>

[0171] The UE does not assume this situation.

[0172] <Alt 1>

[0173] The UE operates as follows regardless of the presence or absence of overlap with the UL subband.

[0174] <<Alt 1-1>

[0175] The UE does not receive PDSCH.

[0176] <<Alt 1-2>>

[0177] The UE assumes that the transmission of the PDSCH is deferred to non-SBFD DL resources.

[0178] <<Alt 1-3>>

[0179] The UE interprets that the PDSCH is rate matched in resources other than SBFD symbols.

[0180] <Alt 2>

[0181] The UE operates as follows depending on whether or not there is overlap with the UL subband. When the PDSCH does not overlap with the UL subband, the UE receives the PDSCH. On the other hand, when the PDSCH overlaps with the UL subband, the UE operates as follows.

[0182] <<Alt 2-0>>

[0183] The UE does not assume this situation.

[0184] <<Alt 2-1>>

[0185] The UE does not receive PDSCH.

[0186] <<Alt 2-2>>

[0187] The UE assumes that the PDSCH is rate matched in the DL subband.

[0188] For s-TRP PDSCH, s-TRP PDSCH repetition, m-TRP PDSCH based on m-DCI, SFNPDSCH based on s-DCI, and m-TRP TDMed PDSCH repetition based on s-DCI (i.e., s-DCI m-TRP PDSCH based on the set tdmSchemeA or repetitionNumber), consider the following scenarios 1 and 2.

[0189] Case 1: A symbol included in a PDSCH or a resource for PDSCH repetition reception overlaps with at least one non-SBFD semi-static / dynamic UL symbol (or a non-SBFD dynamic FL symbol).

[0190] Case 2: The codewords included in the resources for PDSCH or PDSCH repeated reception do not overlap with non-SBFD semi-static / dynamic UL codewords (or non-SBFD dynamic FL codewords), but overlap with at least one SBFD semi-static / dynamic UL codeword, at least one SBFD semi-static / dynamic DL codeword, and / or at least one SBFD dynamic FL codeword.

[0191] (Scenario 1)

[0192] As in Case 1, when the codewords included in the resources for PDSCH or PDSCH repeated reception overlap with at least one non-SBFD semi-static / dynamic UL codeword (or non-SBFD dynamic FL codeword), the UE can also operate according to the following Alt-A and / or Alt-B.

[0193] <Case 1: Alt-A>

[0194] In Alt-A, when a symbol included in a resource for receiving a PDSCH or PDSCH repetition overlaps with at least one non-SBFD semi-static / dynamic UL symbol (or non-SBFD dynamic FL symbol), the UE may not receive the PDSCH or PDSCH repetition. That is, the UE may not receive the PDSCH or PDSCH repetition that overlaps with a UL symbol or FL symbol in a non-SBFD operation.

[0195] In addition, as a modified example, when a symbol included in a resource for receiving a PDSCH or PDSCH repetition overlaps with at least one non-SBFD semi-static / dynamic UL symbol (or non-SBFD dynamic FL symbol) and is not received, and when the PDSCH or PDSCH repetition is one or any one of a plurality of PDSCHs scheduled by a single DCI, the HPN (HARQ Process Number) may be skipped for the PDSCH or PDSCH repetition. That is, the UE may not send a HARQ-ACK for the PDSCH or PDSCH repetition.

[0196] <Case 1: Alt-B>

[0197] In Alt-B, when a symbol included in a resource for receiving a PDSCH or PDSCH repetition overlaps with at least one non-SBFD semi-static / dynamic UL symbol (or non-SBFD dynamic FL symbol), the UE may also assume / judge / determine / interpret that the PDSCH or PDSCH repetition is postponed to a time slot in which a symbol of a time domain resource for receiving the PDSCH or PDSCH repetition does not overlap with a non-SBFD semi-static / dynamic UL symbol (or non-SBFD dynamic FL symbol). That is, the UE may also receive the PDSCH or PDSCH repetition that overlaps with a UL symbol or FL symbol in a non-SBFD operation in any subsequent time slot that does not overlap with a UL symbol or FL symbol in a non-SBFD operation. Here, the UE may also receive the PDSCH or PDSCH repetition that overlaps with a UL symbol or FL symbol in a non-SBFD operation in any subsequent time unit such as any symbol, subslot, subframe, frame, etc. that does not overlap with a UL symbol or FL symbol in a non-SBFD operation.

[0198] (Scenario 2)

[0199] As in Case 2, when the codewords included in the resources for repeated reception of PDSCH or PDSCH do not overlap with non-SBFD semi-static / dynamic UL codewords (or non-SBFD dynamic FL codewords), but overlap with at least one SBFD semi-static / dynamic UL codeword, at least one SBFD semi-static / dynamic DL codeword, and / or at least one SBFD dynamic FL codeword, the UE may also operate in accordance with the following Alt0, Alt 1 and / or Alt 2.

[0200] <Case 2: Alt 0>

[0201] In Alt 0, the UE may not assume / judge / determine the following situation: the codeword included in the resources for receiving the PDSCH or PDSCH repetition does not overlap with the non-SBFD semi-static / dynamic UL codeword (or non-SBFD dynamic FL codeword), but overlaps with at least one SBFD semi-static / dynamic UL codeword, at least one SBFD semi-static / dynamic DL codeword, and / or at least one SBFD dynamic FL codeword. That is, the gNB may not send the PDSCH or PDSCH repetition that does not overlap with the non-SBFD semi-static / dynamic UL codeword (or non-SBFD dynamic FL codeword) but overlaps with at least one SBFD semi-static / dynamic UL codeword, at least one SBFD semi-static / dynamic DL codeword, and / or at least one SBFD dynamic FL codeword.

[0202] <Case 2: Alt 1>

[0203] In Alt 1, when the codewords included in the resources for PDSCH or PDSCH repeated reception do not overlap with non-SBFD semi-static / dynamic UL codewords (or non-SBFD dynamic FL codewords), but overlap with at least one SBFD semi-static / dynamic UL codeword, at least one SBFD semi-static / dynamic DL codeword, and / or at least one SBFD dynamic FL codeword, the UE may also operate in accordance with the following Alt 1-1, Alt 1-2 and / or Alt 1-3 regardless of whether there is overlap with the UL subband.

[0204] <<Scenario 2: Alt 1-1>>

[0205] In Alt 1-1, when a symbol included in a resource for receiving a PDSCH or PDSCH repetition does not overlap with a non-SBFD semi-static / dynamic UL symbol (or a non-SBFD dynamic FL symbol), but overlaps with at least one SBFD semi-static / dynamic UL symbol, at least one SBFD semi-static / dynamic DL symbol, and / or at least one SBFD dynamic FL symbol, the UE may not receive the PDSCH or PDSCH repetition regardless of the presence or absence of overlap with the UL subband. That is, the UE may not receive the PDSCH or PDSCH repetition that overlaps with a UL symbol, a DL symbol, or a FL symbol in the SBFD operation.

[0206] In addition, as a variation, PDSCH repetitions that are not received due to overlap with SBFD semi-static / dynamic UL symbols, SBFD semi-static / dynamic DL symbols, and / or SBFD dynamic FL symbols may be counted as the number of repetitions, or may not be counted.

[0207] In addition, as a modified example, when the PDSCH is not received due to overlap with SBFD semi-static / dynamic UL symbols, SBFD semi-static / dynamic DL symbols, and / or SBFD dynamic FL symbols, and when the PDSCH or PDSCH repetition is one or any one of a plurality of PDSCHs scheduled by a single DCI, the HPN may be skipped or may not be skipped for the PDSCH or PDSCH repetition. That is, the UE may or may not send HARQ-ACK for the PDSCH or PDSCH repetition.

[0208] <<Scenario 2: Alt 1-2>>

[0209] In Alt 1-2, when the codewords included in the resources for receiving the PDSCH or PDSCH repetition do not overlap with the non-SBFD semi-static / dynamic UL codewords (or non-SBFD dynamic FL codewords), but overlap with at least one SBFD semi-static / dynamic UL codeword, at least one SBFD semi-static / dynamic DL codeword, and / or at least one SBFD dynamic FL codeword, the UE may also assume / judge / determine / interpret that, regardless of the presence or absence of overlap with the UL subband, the PDSCH or PDSCH repetition is postponed to a time slot in which the resources of the PDSCH or PDSCH repetition do not overlap with the non-SBFD semi-static / dynamic UL codewords (or non-SBFD dynamic FL codewords) and do not overlap with the SBFD semi-static / dynamic UL codewords, SBFD semi-static / dynamic DL codewords, and / or SBFD dynamic FL codewords. That is, the UE may also receive the PDSCH or PDSCH repetition in any subsequent time slot that does not overlap with the UL symbol or FL symbol in non-SBFD operation, and does not overlap with the UL symbol or DL ​​symbol in SBFD operation. That is, the gNB may also send the PDSCH or PDSCH repetition in any subsequent time slot that does not overlap with the UL symbol or FL symbol in non-SBFD operation, and does not overlap with the UL symbol or DL ​​symbol in SBFD operation. In addition, the UE may also receive the PDSCH or PDSCH repetition in any time unit such as any subsequent 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 symbol or DL ​​symbol in SBFD operation.

[0210] In addition, for such a deferral, it is also possible to set a condition that requires additional addition. For example, it is also possible to set the deferral to be performed when the SBFD operation indication is set through RRC. In other words, when the SBFD operation is dynamically notified to the UE, the deferral may not be applied. That is, when the SBFD operation is dynamically notified to the UE, the UE may not receive PDSCH or PDSCH repetitions. For example, when the SBFD operation is notified to the UE through DCI, the UE may not receive PDSCH or PDSCH repetitions 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 in any subsequent time units such as symbols, subslots, time slots, subframes, and frames.

[0211] <<Scenario 2: Alt 1-3>>

[0212] In Alt 1-3, the UE may also assume / judge / determine / interpret that the symbols included in the resources for receiving the PDSCH or PDSCH repetition are rate matched on symbols other than the SBFD semi-static / dynamic UL symbols, SBFD semi-static / dynamic DL symbols, and / or SBFD dynamic FL symbols. That is, the gNB may also transmit the PDSCH or PDSCH repetition that is rate matched on symbols other than the SBFD semi-static / dynamic UL symbols, SBFD semi-static / dynamic DL symbols, and / or SBFD dynamic FL symbols.

[0213] Here, as a variation, when the PDSCH or PDSCH repetition is one or any one of multiple PDSCHs scheduled by a single DCI, the HPN may or may not be skipped for the PDSCH or PDSCH repetition. That is, the UE may or may not send the HARQ-ACK for the PDSCH or PDSCH repetition.

[0214] <Case 2: Alt 2>

[0215] In Alt 2, when the codewords included in the resources for PDSCH or PDSCH repeated reception do not overlap with non-SBFD semi-static / dynamic UL codewords (or non-SBFD dynamic FL codewords), but overlap with at least one SBFD semi-static / dynamic UL codeword, at least one SBFD semi-static / dynamic DL codeword, and / or at least one SBFD dynamic FL codeword, the UE may also control the PDSCH or PDSCH repeated reception operation according to whether there is overlap with the UL subband.

[0216] Specifically, when the codeword included in the resources for receiving PDSCH or PDSCH repetition does not overlap with non-SBFD semi-static / dynamic UL codewords (or non-SBFD dynamic FL codewords), but overlaps with at least one SBFD semi-static / dynamic UL codeword, at least one SBFD semi-static / dynamic DL codeword, and / or at least one SBFD dynamic FL codeword, and when the codeword included in the resources for receiving PDSCH or PDSCH repetition does not overlap with the UL subband in the SBFD semi-static / dynamic UL codeword, SBFD semi-static / dynamic DL codeword, and / or SBFD dynamic FL codeword, the UE can also receive the PDSCH or PDSCH repetition in the notified or set resources. In addition, the resource can also be specified by the specification, or semi-statically set by RRC settings, etc., or dynamically notified by DCI notifications, etc., or determined in accordance with rules. In addition, the resource can also be explicitly or implicitly specified, set, notified or determined.

[0217] Here, as a variation, when the PDSCH or PDSCH repetition is one or any one of a plurality of PDSCHs scheduled by a single DCI, HPN may not be skipped for the PDSCH or PDSCH repetition. That is, the UE may also send HARQ-ACK for the PDSCH or PDSCH repetition.

[0218] On the other hand, when the codewords included in the resources for repeated reception of PDSCH or PDSCH do not overlap with non-SBFD semi-static / dynamic UL codewords (or non-SBFD dynamic FL codewords), but overlap with at least one SBFD semi-static / dynamic UL codeword, at least one SBFD semi-static / dynamic DL codeword, and / or at least one SBFD dynamic FL codeword, and when the codewords included in the resources for repeated reception of PDSCH or PDSCH overlap with the UL subband in the SBFD semi-static / dynamic UL codewords, SBFD semi-static / dynamic DL codewords, and / or SBFD dynamic FL codewords, the UE may also operate in accordance with the following Alt 2-0, Alt2-1, Alt 2-2, and / or Alt 2-3.

[0219] <<Scenario 2: Alt 2-0>>

[0220] In Alt 2-0, the UE may not assume / judge / determine that the symbols included in the resources for receiving the PDSCH or PDSCH repetition do not overlap with the non-SBFD semi-static / dynamic UL symbols (or non-SBFD dynamic FL symbols), but overlap with at least one SBFD semi-static / dynamic UL symbol, at least one SBFD semi-static / dynamic DL symbol, and / or at least one SBFD dynamic FL symbol, and the symbols included in the resources for receiving the PDSCH or PDSCH repetition overlap with the UL subband in the SBFD semi-static / dynamic UL symbols, SBFD semi-static / dynamic DL symbols, and / or SBFD dynamic FL symbols. That is, the gNB may transmit the PDSCH or PDSCH repetition that does not overlap with the non-SBFD semi-static / dynamic UL symbols (or non-SBFD dynamic FL symbols), but overlaps with the UL subband in the SBFD semi-static / dynamic UL symbols, SBFD semi-static / dynamic DL symbols, and / or SBFD dynamic FL symbols.

[0221] <<Scenario 2: Alt 2-1>>

[0222] In Alt 2-1, when a symbol included in the resources for receiving the PDSCH or PDSCH repetition does not overlap with a non-SBFD semi-static / dynamic UL symbol (or a non-SBFD dynamic FL symbol), but overlaps with at least one SBFD semi-static / dynamic UL symbol, at least one SBFD semi-static / dynamic DL symbol, and / or at least one SBFD dynamic FL symbol, and when a symbol included in the resources for receiving the PDSCH or PDSCH repetition overlaps with a UL subband in a SBFD semi-static / dynamic UL symbol, a SBFD semi-static / dynamic DL symbol, and / or a SBFD dynamic FL symbol, the UE may not receive the PDSCH or PDSCH repetition. That is, the UE may not receive the PDSCH or PDSCH repetition that overlaps with a UL subband in a UL symbol, a DL symbol, or a FL symbol in the SBFD operation.

[0223] In addition, as a variation, PDSCH repetitions that are not received due to overlap with UL subbands in SBFD semi-static / dynamic UL symbols, SBFD semi-static / dynamic DL symbols, and / or SBFD dynamic FL symbols may be counted as the number of repetitions, or may not be counted.

[0224] In addition, as a variation, when the PDSCH or PDSCH repetition is one or any one of a plurality of PDSCHs scheduled by a single DCI, the HPN may be skipped or may not be skipped for the PDSCH or PDSCH repetition. That is, the UE may not send HARQ-ACK for the PDSCH or PDSCH repetition, or may send it.

[0225] <<Scenario 2: Alt 2-2>>

[0226] In Alt 2-2, when the codeword included in the resources for receiving the PDSCH or PDSCH repetition does not overlap with the non-SBFD semi-static / dynamic UL codeword (or non-SBFD dynamic FL codeword), but overlaps with at least one SBFD semi-static / dynamic UL codeword, at least one SBFD semi-static / dynamic DL codeword, and / or at least one SBFD dynamic FL codeword, and when the PDSCH or PDSCH repetition overlaps with the UL subband in the SBFD semi-static / dynamic UL codeword, the SBFD semi-static / dynamic DL codeword, and / or the SBFD dynamic FL codeword, the UE may also assume / judge / determine / interpret that the PDSCH or PDSCH repetition is rate matched on the DL subband in the SBFD semi-static / dynamic UL codeword, the SBFD semi-static / dynamic DL codeword, and / or the SBFD dynamic FL codeword, and / or on the non-SBFD semi-static / dynamic DL / FL codeword if present.

[0227] In addition, as a variation, when the PDSCH or PDSCH repetition is one or any one of a plurality of PDSCHs scheduled by a single DCI, HPN may not be skipped for the PDSCH or PDSCH repetition. That is, the UE may also send HARQ-ACK for the PDSCH or PDSCH repetition.

[0228] <<Scenario 2: Alt 2-3>>

[0229] In Alt 2-3, when the codeword included in the resources for receiving the PDSCH or PDSCH repetition does not overlap with the non-SBFD semi-static / dynamic UL codeword (or the non-SBFD dynamic FL codeword), but overlaps with at least one SBFD semi-static / dynamic UL codeword, at least one SBFD semi-static / dynamic DL codeword, and / or at least one SBFD dynamic FL codeword, and when the codeword included in the resources for receiving the PDSCH or PDSCH repetition overlaps with the UL subband in the SBFD semi-static / dynamic UL codeword, the SBFD semi-static / dynamic DL codeword, and / or the SBFD dynamic FL codeword, the UE may also assume / judge / determine / interpret that the PDSCH or PDSCH repetition is postponed to a time slot in which the resources for the PDSCH or PDSCH repetition do not overlap with the non-SBFD semi-static / dynamic UL codeword (or the non-SBFD dynamic FL codeword) and do not overlap with any UL subband in the SBFD semi-static / dynamic UL codeword, the SBFD semi-static / dynamic DL codeword, and / or the SBFD dynamic FL codeword. That is, the UE may also receive the PDSCH or PDSCH repetition in any subsequent time slot that does not overlap with the UL symbol or FL symbol in the non-SBFD operation, and does not overlap with the UL subband in the UL symbol, DL symbol and / or FL symbol in the SBFD operation. Here, the UE may also receive the PDSCH or PDSCH repetition in any subsequent time unit such as any symbol, subslot, subframe, frame, etc. that does not overlap with the UL symbol or FL symbol in the non-SBFD operation, and does not overlap with the UL subband in the UL symbol, DL symbol and / or FL symbol in the SBFD operation.

[0230] In addition, such a deferral may also be set as a condition that requires additional addition. For example, the deferral may also be performed when the SBFD operation indication is set through RRC. In other words, when the SBFD operation is dynamically notified to the UE, the deferral may not be applied. That is, when the SBFD operation is dynamically notified to the UE, the UE may not receive PDSCH or PDSCH repetitions. For example, when the SBFD operation is notified to the UE through DCI, the UE may not receive PDSCH or PDSCH repetitions that do not overlap with any non-SBFD UL codeword (or non-SBFD dynamic flexible codeword) but overlap with UL subbands in SBFD UL codewords, SBFD DL codewords, and / or SBFD FL codewords in any subsequent time units such as codewords, subslots, subframes, and frames.

[0231] In addition, which of the above Alts to apply can 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 should be applied can also be sent in at least one of RRC, DCI, and MAC CE (Medium Access Control Control Element).

[0232] Here, when the above-mentioned solutions based on rate matching such as Alt 1-3 or Alt 2-2 are applied, it is necessary to study the TBS (Transport Block Size). For example, the TBS can also be determined according to the following options A and / or B.

[0233] <Option A>

[0234] In option A, TBS can also be based on

[0235] i) non-SBFD semi-static / dynamic UL symbols (and non-SBFD dynamic FL symbols),

[0236] ii) SBFD semi-static / dynamic UL symbols, SBFD semi-static / dynamic DL symbols, and / or SBFD dynamic FL symbols, and / or

[0237] iii) UL resource blocks (RBs) in SBFD semi-static / dynamic UL symbols, SBFD semi-static / dynamic DL symbols, and / or SBFD dynamic FL symbols,

[0238] The decision is made based on the number of resource elements (REs) after exclusion.

[0239] <Option B>

[0240] In option B, TBS may also be determined based on the number of REs notified through time domain resource allocation (TDRA) and frequency domain resource allocation (FDRA).

[0241] For example, for PDSCH repetition, the number of REs used for TBS calculation may be different for different repetitions when Option A is applied. In such a case, the TBS of each repetition may be determined based on the maximum / minimum / average value of the TBS calculated for the first PDSCH repetition and / or the TBS values ​​calculated for all repetitions.

[0242] Which option to apply may be explicitly or implicitly specified by the specification, semi-statically set by RRC, dynamically notified by DCI, or determined by a rule. For example, a parameter indicating which option should be applied may be sent in at least one of RRC, DCI, and MAC CE. For example, the UE may receive setting information related to option A and option B through RRC, or may be dynamically notified through DCI which option of option A and option B should be applied.

[0243] (UE operation of Proposal 1)

[0244] In Proposal 1, the UE may also control the receiving operation of the downlink data channel according to whether the uplink time unit in the non-time-frequency division duplex operation and / or the time unit in the time-frequency division duplex operation overlaps with the downlink data channel, and perform the receiving operation of the downlink data channel through the controlled receiving operation. Here, the time-frequency division duplex may also be SBFD, and the uplink time unit in the non-time-frequency division duplex operation may also be the UL code element, time slot, or any other time unit in the non-SBFD operation, specifically, it may also be a non-SBFD semi-static / dynamic UL code element, and / or a non-SBFD dynamic FL code element. In addition, the time unit in the time-frequency division duplex operation may also be the UL, DL or FL code element, time slot, or any other time unit in the SBFD operation, specifically, it may also be a SBFD semi-static / dynamic UL code element, a SBFD semi-static / dynamic DL code element, and / or a SBFD dynamic FL code element. In addition, the downlink data channel may also be, for example, PDSCH, PDSCH repetition, etc.

[0245] Specifically, when the downlink data channel overlaps with the uplink time unit or flexible time unit in non-time-frequency division duplex operation, the UE may not receive the downlink data channel. Alternatively, / furthermore, when the downlink data channel overlaps with the 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 in which the downlink data channel does not overlap with the uplink time unit in non-time-frequency division duplex operation. That is, the UE may also assume / judge / determine / interpret that the PDSCH or PDSCH repetition is postponed to a time slot in which the time domain resources of the PDSCH or PDSCH repetition do not overlap with the non-SBFD semi-static / dynamic UL codeword.

[0246] In addition, when the downlink data channel overlaps with the time unit in the time-frequency division duplex operation, the UE may also 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 may not assume / judge / determine / interpret that the downlink data channel overlaps with the time unit in the SBFD operation. In addition, the UE may not receive the downlink data channel. Alternatively / furthermore, the UE may also receive the downlink data channel in a time unit in which the downlink data channel does not overlap with the uplink time unit or flexible time unit in the non-SBFD operation, and does not overlap with the uplink time unit, downlink time unit, and / or flexible time unit in the SBFD operation. That is, the UE may also assume / judge / determine / interpret that the PDSCH or PDSCH repetition is postponed to a time unit such as a time slot in which the resource of the PDSCH or PDSCH repetition does not overlap with the non-SBFD semi-static / dynamic UL symbol, and does not overlap with the SBFD semi-static / dynamic UL symbol, the SBFD semi-static / dynamic DL symbol, and / or the SBFD dynamic FL symbol. Alternatively / furthermore, the UE may also assume / judge / determine / interpret that the downlink data channel is rate matched on a time unit other than the time unit in the SBFD operation. That is, the UE may also assume / judge / determine / interpret that the PDSCH or PDSCH repetition is rate matched on a symbol other than the SBFD semi-static / dynamic UL symbol, the SBFD semi-static / dynamic DL symbol, and / or the SBFD dynamic FL symbol.

[0247] In addition, when the downlink data channel overlaps with the time unit in the time-frequency division duplex operation, the UE may also control the reception operation of the downlink data channel according to whether the downlink data channel overlaps with the uplink subband in the time unit. For example, when the downlink data channel does not overlap with the uplink subband in the time unit, the UE may also receive the downlink data channel on the set / notified resource. In addition, the UE may not assume / judge / determine / interpret that the downlink data channel overlaps with the uplink subband in the time unit. In addition, the UE may not receive the downlink data channel. Alternatively / furthermore, the UE may also assume / judge / determine / interpret that the downlink data channel is rate matched on the DL subband in the time unit in the SBFD operation. Alternatively / furthermore, the UE may also receive the downlink data channel in a time unit such as a time slot in which the downlink data channel does not overlap with the uplink time unit or flexible time unit in the non-SBFD operation and does not overlap with the uplink time unit, downlink time unit, and / or flexible time unit in the SBFD operation. That is, the UE may also assume / judge / decide / interpret that the PDSCH or PDSCH repetition is postponed to a time unit such as a time slot in which the resources of the PDSCH or PDSCH repetition do not overlap with non-SBFD semi-static / dynamic UL codewords and do not overlap with SBFD semi-static / dynamic UL codewords, SBFD semi-static / dynamic DL codewords, and / or SBFD dynamic FL codewords.

[0248] (gNB operation of Proposal 1)

[0249] In Proposal 1, the gNB may also control the transmission operation of the downlink data channel in the uplink time unit in the non-time-frequency division duplex operation and / or the time unit in the time-frequency division duplex operation, and perform the transmission operation of the downlink data channel through the controlled transmission operation. Here, the time-frequency division duplex may also be SBFD, and the uplink time unit in the non-time-frequency division duplex operation may also be a UL symbol, a time slot, or any other time unit in the non-SBFD operation, and specifically, may also be a non-SBFD semi-static / dynamic UL symbol, and / or a non-SBFD dynamic FL symbol. In addition, the time unit in the SBFD operation may also be a UL, DL, or FL symbol, a time slot, or any other time unit in the SBFD operation, and specifically, may also be a SBFD semi-static / dynamic UL symbol, a SBFD semi-static / dynamic DL symbol, and / or a SBFD dynamic FL symbol. In addition, the downlink data channel may also be, for example, a PDSCH, a PDSCH repetition, or the like.

[0250] UE Capability

[0251] For the PDSCH enhancement for the above-mentioned time-frequency division duplex operation, UE capability information indicating whether the UE supports the PDSCH enhancement for the time-frequency division duplex operation may also be specified. In addition, UE capability information related to the PDSCH transmission for time-frequency division duplex such as SBFD operation may also be specified. In the case of supporting the PDSCH enhancement for the time-frequency division duplex operation, the UE may also send the gNB UE capability information indicating support for the PDSCH enhancement for the time-frequency division duplex operation. If the UE capability information is received, the gNB is able to send the PDSCH enhanced for the time-frequency division duplex operation to the UE and enable the UE to perform the enhanced PDSCH reception operation in the time-frequency division duplex operation.

[0252] (Effect of Proposal 1)

[0253] According to the above-mentioned Proposal 1, PDSCH enhancement for time-frequency division duplex operations such as SBFD operations can be achieved. Specifically, the reception operations of UE-based s-TRP PDSCH, s-TRP PDSCH repetition, m-TRP PDSCH based on m-DCI, SFN PDSCH based on s-DCI, and m-TRP TDMed PDSCH repetition based on s-DCI in SBFD operations and non-SBFD operations can be specified.

[0254] [Proposal 2]

[0255] In Proposal 2, other PDSCH enhancements for time-frequency division duplex operations such as SBFD operations are described. Specifically, the m-TRP FDM of the PDSCH is extended for SBFD operations as follows.

[0256] Case 1: PDSCH resources overlap with non-SBFD UL symbols

[0257] <Alt-A>

[0258] The UE assumes that the PDSCH is not transmitted.

[0259] <Alt-B>

[0260] The UE assumes that the transmission of the PDSCH is delayed.

[0261] Case 2: PDSCH resources overlap with SBFD symbols

[0262] <Alt 1>

[0263] The UE operates as follows regardless of the presence or absence of overlap with the UL subband.

[0264] <<Alt 1-1>

[0265] The UE does not receive PDSCH.

[0266] <<Alt 1-2>>

[0267] The UE assumes that the transmission of the PDSCH is deferred to non-SBFD DL resources.

[0268] <<Alt 1-3>>

[0269] The UE assumes that the PDSCH is rate matched in resources other than the SBFD symbols.

[0270] <Alt 2>

[0271] The UE operates as follows depending on whether or not there is overlap with the UL subband. When the PDSCH does not overlap with the UL subband, the UE receives the PDSCH. On the other hand, when the PDSCH overlaps with the UL subband, the UE operates as follows.

[0272] <<Alt 2-0>>

[0273] The UE does not assume this situation.

[0274] <<Alt 2-1>>

[0275] The UE does not receive PDSCH.

[0276] <<Alt 2-2>>

[0277] The UE assumes that the transmission of the PDSCH is postponed to non-overlapping resources.

[0278] <<Alt 2-3>>

[0279] The discard rules are applied to each PDSCH resource of each TRP.

[0280] <<Alt 2-4>>

[0281] Rate matching is applied to each PDSCH resource of each TRP.

[0282] <<Alt 2-5>>

[0283] Allocate PDSCH resources of multiple TRPs to the resources of the DL subband.

[0284] For the frequency-division multiplexed PDSCH of the s-DCI-based m-TRP, that is, the s-DCI-based m-TRP PDSCH based on fdmSchemeA or fdmSchemeB, the following Case 1 and Case 2 can be considered.

[0285] Case 1: The symbols included in the time domain resources for two PDSCH opportunities or repeated reception overlap with at least one non-SBFD semi-static / dynamic UL symbol (or non-SBFD dynamic FL symbol) (see Fig.16 ).

[0286] Case 2: The symbols included in the time domain resources for two PDSCH opportunities or repeated reception do not overlap with non-SBFD semi-static / dynamic UL symbols (or non-SBFD dynamic FL symbols), but overlap with at least one SBFD semi-static / dynamic UL symbol, at least one SBFD semi-static / dynamic DL symbol, and / or at least one SBFD semi-static / dynamic FL symbol (refer to Fig.17 ).

[0287] (Scenario 1)

[0288] As in Case 1, when the codewords included in two PDSCH opportunities or repeated reception time domain resources overlap with at least one non-SBFD semi-static / dynamic UL codeword (or non-SBFD dynamic FL codeword), the UE can also operate according to the following Alt-A and / or Alt-B.

[0289] <Case 1: Alt-A>

[0290] In Alt-A, the UE may not assume / judge / determine / interpret that two PDSCH opportunities or repetitions in which symbols included in time domain resources overlap with at least one non-SBFD semi-static / dynamic UL symbol (or non-SBFD dynamic FL symbol) are transmitted. That is, the gNB may not transmit two PDSCH opportunities or repetitions in which symbols included in time domain resources overlap with at least one non-SBFD semi-static / dynamic UL symbol (or non-SBFD dynamic FL symbol).

[0291] <Case 1: Alt-B>

[0292] In Alt-B, the UE may also assume / judge / determine / interpret that two PDSCH opportunities or repetitions are postponed to a time slot in which the symbols included in the time domain resources for receiving the two PDSCH opportunities or repetitions do not overlap with the non-SBFD semi-static / dynamic UL symbols (or non-SBFD dynamic flexible symbols). That is, the UE may also receive the PDSCH opportunity or repetition in any subsequent time slot that does not overlap with the UL symbols or FL symbols in the non-SBFD operation.

[0293] (Scenario 2)

[0294] As in Case 2, when the codewords included in two PDSCH opportunities or time domain resources for repeated reception do not overlap with non-SBFD semi-static / dynamic UL codewords (or non-SBFD dynamic FL codewords), but overlap with at least one SBFD semi-static / dynamic UL codeword, at least one SBFD semi-static / dynamic DL codeword, and / or at least one SBFD semi-static / dynamic FL codeword, the UE may also operate according to the following Alt 1 and / or Alt 2.

[0295] <Case 2: Alt 1>

[0296] In Alt 1, when the codewords included in two PDSCH opportunities or time domain resources for repeated reception do not overlap with non-SBFD semi-static / dynamic UL codewords (or non-SBFD dynamic FL codewords), but overlap with at least one SBFD semi-static / dynamic UL codeword, at least one SBFD semi-static / dynamic DL codeword, and / or at least one SBFD semi-static / dynamic FL codeword, the UE may also operate in accordance with Alt 1-1, Alt 1-2 and / or Alt 1-3 regardless of the presence or absence of overlap with the UL subband.

[0297] <<Scenario 2: Alt 1-1>>

[0298] In Alt 1-1, the UE may also not assume that the codewords included in the time domain resources do not overlap with the non-SBFD semi-static / dynamic UL codewords (or non-SBFD dynamic FL codewords), but overlap with at least one SBFD semi-static / dynamic UL codeword, at least one SBFD semi-static / dynamic DL codeword, and / or at least one SBFD semi-static / dynamic FL codeword. That is, the gNB may not send two PDSCH opportunities or repetitions in which the codewords included in the time domain resources do not overlap with the non-SBFD semi-static / dynamic UL codewords (or non-SBFD dynamic FL codewords), but overlap with at least one SBFD semi-static / dynamic UL codeword, at least one SBFD semi-static / dynamic DL codeword, and / or at least one SBFD semi-static / dynamic FL codeword. For example, as Fig.17 As shown, since the codewords contained in the two PDSCH opportunities from TRP#1 and TRP#2 or the time domain resources for repeated reception overlap with the UL codewords in the SBFD operation, they may not be received.

[0299] <<Scenario 2: Alt 1-2>>

[0300] In Alt 1-2, the UE may also assume / judge / determine / interpret that two PDSCH opportunities or repetitions are postponed to a time slot in which the symbols included in the time domain resources for reception of the two PDSCH opportunities or repetitions do not overlap with non-SBFD semi-static / dynamic UL symbols (or non-SBFD dynamic flexible symbols) and do not overlap with SBFD semi-static / dynamic UL symbols, SBFD semi-static / dynamic DL symbols, and / or SBFD semi-static / dynamic FL symbols. That is, the UE may also receive the PDSCH opportunity or repetition in any subsequent time 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 also receive the PDSCH opportunity or repetition in any subsequent codeword, subslot, subframe, frame, or other time unit that does not overlap with a non-SBFD semi-static / dynamic UL codeword (or a non-SBFD dynamic flexible codeword) and does not overlap with a SBFD semi-static / dynamic UL codeword, a SBFD semi-static / dynamic DL codeword, and / or a SBFD semi-static / dynamic FL codeword.

[0301] In addition, such a delay may be set as a condition that needs to be added. For example, the delay may be performed when the SBFD operation indication is set through RRC. In other words, when the SBFD operation is dynamically notified to the UE, the delay may not be applied. That is, when the SBFD operation is dynamically notified to the UE, the UE may not assume / judge / determine / interpret that the PDSCH opportunity or repetition is sent.

[0302] <<Scenario 2: Alt 1-3>>

[0303] In Alt 1-3, the UE may also assume / judge / determine / interpret that the symbols included in the time domain resources for receiving the PDSCH opportunity or repetition are rate matched on symbols other than SBFD semi-static / dynamic UL symbols, SBFD semi-static / dynamic DL symbols, and / or SBFD dynamic FL symbols. That is, the UE may also assume / judge / determine / interpret that the gNB transmits the rate matched PDSCH opportunity or repetition in symbols other than SBFD semi-static / dynamic UL symbols, SBFD semi-static / dynamic DL symbols, and / or SBFD semi-static / dynamic FL symbols.

[0304] Here, when the above-mentioned rate matching-based solution is applied, it is necessary to study the TBS (Transport Block Size). For example, the TBS may also be determined according to the following Option A and / or Option B.

[0305] <Option A>

[0306] In option A, the TBS may be determined based on the number of symbols excluding SBFD semi-static / dynamic UL symbols, SBFD semi-static / dynamic DL symbols, and / or SBFD dynamic FL symbols from the symbols notified through TDRA.

[0307] <Option B>

[0308] In option B, TBS may also be determined based on the number of symbols notified via TDRA.

[0309] For example, for PDSCH repetition, when Option A is applied, the number of symbols used for TBS calculation may be different for different repetitions. In such a case, the TBS of each repetition may be determined based on the maximum / minimum / average value of the TBS calculated for the first PDSCH repetition and / or the TBS values ​​calculated for all repetitions.

[0310] Which option to apply may be explicitly or implicitly specified by the specification, semi-statically set by RRC, dynamically notified by DCI, or determined by a rule. For example, a parameter indicating which option should be applied may be sent in at least one of RRC, DCI, and MAC CE. For example, the UE may receive setting information related to option A and option B through RRC, or may be dynamically notified through DCI which option of option A and option B should be applied.

[0311] <Case 2: Alt 2>

[0312] In Alt 2, when the codewords included in the time domain resources for two PDSCH opportunities or repeated reception do not overlap with non-SBFD semi-static / dynamic UL codewords (or non-SBFD dynamic FL codewords), but overlap with at least one SBFD semi-static / dynamic UL codeword, at least one SBFD semi-static / dynamic DL codeword, and / or at least one SBFD semi-static / dynamic FL codeword, the UE can also control the PDSCH opportunity or repeated reception operation according to whether there is overlap with the UL subband.

[0313] Specifically, when the allocated physical resource blocks (PRBs) notified through FDRA do not overlap with the UL subbands in the SBFD semi-static / dynamic UL symbols, SBFD semi-static / dynamic DL symbols, and / or SBFD semi-static / dynamic FL symbols, the UE may determine resource blocks (RBs) for each TRP as in Rel-16, and receive two PDSCH opportunities or repetitions on the notified / set resources. The resources may also be specified by the specification, or semi-statically set by RRC settings, etc., or dynamically notified by DCI notifications, etc., or determined in accordance with rules. In addition, the resources may also be specified, set, notified, or determined explicitly or implicitly.

[0314] On the other hand, in the case where the allocated physical resource blocks (PRBs) notified through FDRA overlap with the UL subband in the SBFD semi-static / dynamic UL symbols, SBFD semi-static / dynamic DL symbols, and / or SBFD semi-static / dynamic FL symbols, the UE may also operate in accordance with the following Alt 2-0, Alt 2-1, Alt 2-2, Alt 2-3, Alt 2-4 and / or Alt 2-5.

[0315] <<Case 2: Alt 2 -0>>

[0316] In Alt 2-0, the UE may also not assume / judge / decide / interpret the following situation: the codewords included in the time domain resources for two PDSCH opportunities or repeated reception do not overlap with non-SBFD semi-static / dynamic UL codewords (or non-SBFD dynamic FL codewords), but overlap with SBFD semi-static / dynamic UL codewords, SBFD semi-static / dynamic DL codewords, and / or SBFD semi-static / dynamic FL codewords, and the allocated PRBs notified through FDRA overlap with the UL subbands in the SBFD semi-static / dynamic UL codewords, SBFD semi-static / dynamic DL codewords, and / or SBFD semi-static / dynamic FL codewords. That is, the gNB may also allocate PRBs through FDRA for two PDSCH opportunities or repetitions whose time domain resources do not overlap with non-SBFD semi-static / dynamic UL symbols (or non-SBFD dynamic FL symbols) but overlap with SBFD semi-static / dynamic UL symbols, SBFD semi-static / dynamic DL symbols, and / or SBFD semi-static / dynamic FL symbols, so as to avoid overlapping with the UL subbands in the SBFD semi-static / dynamic UL symbols, SBFD semi-static / dynamic DL symbols, and / or SBFD semi-static / dynamic FL symbols.

[0317] <<Scenario 2: Alt 2-1>>

[0318] In Alt 2-1, the PDSCH opportunities or repetitions for the two TCI states may not be received. That is, in the case where the symbols included in the time domain resources for receiving the two PDSCH opportunities or repetitions do not overlap with the non-SBFD semi-static / dynamic UL symbols (or non-SBFD dynamic FL symbols), but overlap with at least one SBFD semi-static / dynamic UL symbol, at least one SBFD semi-static / dynamic DL symbol, and / or at least one SBFD semi-static / dynamic FL symbol, and in the case where the allocated PRBs notified through FDRA overlap with the UL subbands in the SBFD semi-static / dynamic UL symbols, SBFD semi-static / dynamic DL symbols, and / or SBFD semi-static / dynamic FL symbols, the UE may not receive the PDSCH opportunities or repetitions for the two TCI states.

[0319] <<Alt 2-2>>

[0320] In Alt 2-2, the PDSCH opportunity or repetition may also be postponed to a time slot in which any resource for receiving the PDSCH opportunity or repetition does not overlap with a non-SBFD semi-static / dynamic UL symbol (or a non-SBFD dynamic FL symbol), or does not overlap with any UL subband in the SBFD semi-static / dynamic UL symbol, the SBFD semi-static / dynamic DL symbol, and / or the SBFD semi-static / dynamic FL symbol. That is, the UE may also assume / judge / determine / interpret that the symbol included in the resource for receiving the PDSCH opportunity or repetition does not overlap with the UL symbol or FL symbol in the non-SBFD operation, and further, receive the PDSCH opportunity or repetition in any subsequent time slot that does not overlap with the UL subband in the UL symbol, DL symbol, and / or FL symbol in the SBFD operation. Alternatively, the UE may receive the PDSCH or PDSCH repetition in any subsequent codeword, subslot, subframe, frame, or other time unit in which the codeword contained in the resources for the PDSCH opportunity or repeated reception does not overlap with the non-SBFD semi-static / dynamic UL codeword (or non-SBFD dynamic flexible codeword) and does not overlap with any UL subband in the SBFD semi-static / dynamic UL codeword, SBFD semi-static / dynamic DL codeword, and / or SBFD dynamic FL codeword.

[0321] In addition, such a deferral may also be set as a condition that requires additional addition. For example, the deferral may also be performed when the SBFD operation indication is set through RRC. In other words, the deferral may not be applied when the SBFD operation is dynamically notified to the UE. That is, when the SBFD operation is dynamically notified to the UE, the UE may not receive PDSCH opportunities or repetitions. For example, when the SBFD operation is notified to the UE through DCI, the UE may not receive PDSCH opportunities or repetitions in subsequent symbols, time slots, etc. that do not overlap with any non-SBFD UL symbols (or non-SBFD dynamic FL symbols), but overlap with UL subbands in SBFD UL symbols, SBFD DL symbols, and / or SBFD FL symbols.

[0322] <<Scenario 2: Alt 2-3>>

[0323] In Alt 2-3, the PRB allocation for each TCI state may also follow the rules of Rel-16, and the UE may discard the PDSCH opportunities or repetitions that overlap with the UL subband. For example, after the RB allocation is determined for each TCI state (following the rules of Rel-16), the PDSCH opportunities or repetitions that overlap with the UL subband are not received, and the PDSCH opportunities or repetitions that do not overlap with the UL subband (if any) are sent. For example, in Fig.18 In the example shown, the PDSCH opportunity of TRP#2 that overlaps with the UL subband is not received or repeated, and the PDSCH opportunity of TRP#1 that does not overlap with the UL subband is received or repeated.

[0324] Here, the TBS may also be determined as follows. For FDM Scheme A, the TBS may also be determined based on the number of PDSCH opportunities or repeated PRBs to be transmitted. In other words, the number of PDSCH opportunities or repeated PRBs that overlap with the UL subband may also be excluded from the TBS calculation. On the other hand, for FDM Scheme B, the TBS may also be determined in the same manner as Rel-16.

[0325] <<Scenario 2: Alt 2-4>>

[0326] In Alt 2-4, the PRB allocation for each TCI state may also follow the rules of Rel-16, and the PDSCH opportunities or repetitions overlapping with the UL subband may also be rate matched on the DL resource block. For example, after the RB allocation is determined for each TCI state (following the rules of Rel-16), the PDSCH opportunities or repetitions overlapping with the UL subband may be rate matched on the DL RB of the RB determined for the TCI state, and the PDSCH opportunities or repetitions that do not overlap with the UL subband may also be sent on the RB determined for the TCI state (if any). For example, Fig.19 In the example shown, the PDSCH opportunity or repeated resource of TRP#1 may be rate matched on the DL subband of the lower frequency band, and the PDSCH opportunity or repeated resource of TRP#2 may be rate matched on the DL subband of the upper frequency band.

[0327] Here, TBS may also be determined as follows. For FDM Scheme A, TBS may also be determined based on the total number of two PDSCH opportunities or repeated DL RBs. On the other hand, for FDM Scheme B, TBS may also be determined in Option A in the same manner as Rel-16 (i.e., as the number of REs of the first TCI state based on the notified FDRA and TDRA), in Option B, based on the actual number of REs of the first / second TCI state (i.e., after excluding the UL RBs of the first / second TCI state), and / or, in Option C, based on a larger / smaller / average value of the actual number of REs of the first / second TCI state (i.e., after excluding the UL RBs of the first / second TCI state). In addition, which of Options A to C is applied may also be specified by the specification, or semi-statically set by RRC settings, etc., or dynamically notified by DCI notifications, etc., or determined in accordance with rules. In addition, which of the options A to C is to be applied may also be explicitly or implicitly specified, set, notified, or determined. For example, a parameter indicating which option should be applied may also be sent in at least one of the RRC, DCI, and MAC CE. For example, the UE may also receive setting information related to the options A to C through the RRC, and may also be dynamically notified of which of the options A to C should be applied through the DCI.

[0328] <<Scenario 2: Alt 2-5>>

[0329] In Alt 2-5, the PRB allocation of each TCI state may also be based on the DL subband of each symbol after excluding the UL subband. Specifically, for each symbol, after excluding the UL subband in the symbol, the number of DL RBs of the symbol may also be allocated to two TCI states. For example, the initial [Formula 2]

[0330]

[0331] PRBs are allocated to the first TCI state, and the remaining [Math 3]

[0332]

[0333] PRBs are allocated to the second TCI state. Here, if we assume

[0334] [Formula 4]

[0335]

[0336] is the number of DL RBs in a symbol, then n PRB It is the total number of PRBs allocated to the UE.

[0337] Regarding which one of Alt 2-0 to Alt 2-5 is applied, it may also depend on whether the SBFD operation (DL / UL subband allocation) is dynamically notified or whether it is set by RRC. For example, when the SBFD operation (DL / UL subband allocation) is dynamically notified through DCI, Alt 2-3 may also be applied, and when the SBFD operation (DL / UL subband allocation) is semi-statically set through RRC, Alt 2-5 may also be applied. For example, regarding which one of Alt 2-0 to Alt 2-5 is applied, it may also be specified by the specification, or semi-statically set through RRC settings, etc., or dynamically notified through DCI notifications, etc., or determined in accordance with rules. In addition, regarding which one of Alt 2-0 to Alt 2-5 is applied, it may also be explicitly or implicitly specified, set, notified or determined. For example, a parameter indicating which Alt should be applied may also be sent in at least one of RRC, DCI and MAC CE (Medium Access Control Control Element).

[0338] (Variation of Proposal 1 / 2)

[0339] The combined operation of SBFD operation and m-TRP PDSCH may not be supported.

[0340] <Concrete example 1>

[0341] In specific example 1, the UE may not assume / judge / determine / interpret that the SBFD operation is notified / set for the serving cell / bandwidth part (BWP), and any TCI code point (at least one code point) is mapped to two TCI states / QCLs in the serving cell / BWP.

[0342] <Concrete example 2>

[0343] In specific example 2, the UE may also not assume / judge / decide / interpret that the SBFD operation is notified / set for the serving cell / bandwidth part (BWP), and any TCI code point (at least one code point) is mapped to two TCI states / QCLs in the serving cell / BWP, and the UE is configured through the repetitionScheme set in the high-level parameter FDMschemeA.

[0344] <Concrete example 3>

[0345] In specific example 3, the UE may also not assume / judge / decide / interpret that the SBFD operation is notified / set for the serving cell / bandwidth part (BWP), and any TCI code point (at least one code point) is mapped to two TCI states / QCLs in the serving cell / BWP, and the UE is configured through the repetitionScheme set in the high-level parameter FDMSchemeB.

[0346] <Concrete example 4>

[0347] In specific example 4, the UE may also not assume / judge / decide / interpret that the SBFD operation is notified / set for the serving cell / bandwidth part (BWP), and any TCI code point (at least one code point) is mapped to two TCI states / QCLs in the serving cell / BWP, and the UE is configured through the repetitionScheme set in the high-level parameter TDMschemeA.

[0348] <Concrete example 5>

[0349] In specific example 5, the UE may not assume / judge / determine / interpret that the SBFD operation is notified / set for the serving cell / bandwidth part (BWP), and any TCI code point (at least one code point) is mapped to two TCI states / QCLs in the serving cell / BWP, and the high-level parameter repetitionNumber is set in the UE.

[0350] <Concrete example 6>

[0351] In specific example 6, the UE may not assume / judge / determine / interpret that the SBFD operation is notified / set for the serving cell / bandwidth part (BWP), and at the same time, any CORESET (at least one CORESET) is set / notified through CORESETPoolID in the serving cell / BWP.

[0352] <Concrete example 7>

[0353] In specific example 7, when the SBFD operation (and / or DL / UL subband allocation) is notified / set for the serving cell / bandwidth part (BWP) and when the DCI notification is mapped to TCI code points of two TCI states / QCLs in the serving cell / BWP, the UE may also use only the first / second TCI state / QCL for PDSCH transmission.

[0354] <Concrete example 8>

[0355] In specific example 8, when the SBFD operation (and / or DL / UL subband allocation) is notified / set for the serving cell / bandwidth part (BWP), and when the DCI notifies the TCI code points mapped to two TCI states / QCLs in the serving cell / BWP, and the UE is configured via the repetitionScheme set in the FDMschemeA of the higher layer parameters, the UE may also use only the first / second TCI state / QCL for PDSCH transmission.

[0356] <Concrete example 9>

[0357] In specific example 9, when the SBFD operation (and / or DL / UL subband allocation) is notified / set for the serving cell / bandwidth part (BWP), and when the DCI notifies the TCI code points mapped to two TCI states / QCLs in the serving cell / BWP, and the UE is configured via the repetitionScheme set in the FDM SchemeB of the higher layer parameters, the UE may also use only the first / second TCI state / QCL for PDSCH transmission.

[0358] <Concrete example 10>

[0359] In specific example 10, when the SBFD operation (and / or DL / UL subband allocation) is notified / set for the serving cell / bandwidth part (BWP), and when the DCI notifies the TCI code points mapped to two TCI states / QCLs in the serving cell / BWP, and the UE is configured via the repetitionScheme set in TDMSchemaA of the higher layer parameters, the UE may also use only the first / second TCI state / QCL for PDSCH transmission.

[0360] <Concrete example 11>

[0361] In specific example 11, when the SBFD operation (and / or DL / UL subband allocation) is notified / set for the serving cell / bandwidth part (BWP), and when the DCI notification is mapped to TCI code points of two TCI states / QCLs in the serving cell / BWP, and the repetitionNumber of the higher-layer parameter is set in the UE, the UE may also use only the first / second TCI state / QCL for PDSCH transmission.

[0362] (UE operation of Proposal 2)

[0363] In Proposal 2, the UE may also control the reception operation of the downlink data channel according to whether the uplink time unit in the non-time-frequency division duplex operation such as non-SBFD operation and / or the time unit in the SBFD operation overlaps with the downlink data channel, and perform the reception operation of the downlink data channel through the controlled reception operation. Here, the time-frequency division duplex may also be SBFD, and the uplink time unit in the non-time-frequency division duplex operation may also be the UL symbol, time slot, or any other time unit in the non-SBFD operation, specifically, it may also be a non-SBFD semi-static / dynamic UL symbol, and / or a non-SBFD dynamic FL symbol. In addition, the time unit in the time-frequency division duplex operation may also be the UL, DL or FL symbol, time slot, or any other time unit in the SBFD operation, specifically, it may also be a SBFD semi-static / dynamic UL symbol, a SBFD semi-static / dynamic DL symbol, and / or a SBFD dynamic FL symbol. In addition, the downlink data channel may also be, for example, PDSCH, PDSCH repetition, etc.

[0364] Specifically, when multiple opportunities of the downlink data channel overlap with the uplink time unit in the non-SBFD operation, the UE may also assume / judge / determine / interpret that the multiple opportunities of the downlink data channel are not sent. Or / furthermore, when multiple opportunities of the downlink data channel overlap with the uplink time unit in the non-SBFD operation, the UE may also receive the multiple opportunities of the downlink data channel in the time slots where the time domain resources of the multiple opportunities of the downlink data channel do not overlap with the uplink time unit in the non-SBFD operation. That is, the UE may also assume / judge / determine / interpret that the PDSCH opportunity or repetition is postponed to the time slot where the PDSCH opportunity or repetition resources do not overlap with the non-SBFD semi-static / dynamic UL codeword.

[0365] In addition, when multiple opportunities of the downlink data channel overlap with the time unit in the SBFD operation, the UE may also control the reception 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. For example, the UE may also assume / judge / determine / interpret that the opportunities of the multiple downlink data channels are not sent. Or / furthermore, the UE may also receive multiple opportunities of the downlink data channel in a time unit that does not overlap with the uplink time unit or flexible time unit in the non-SBFD operation and does not overlap with the uplink time unit, downlink time unit, and / or flexible time unit in the SBFD operation. That is, the UE may also assume / judge / determine / interpret that the PDSCH opportunity or the resource that is postponed to the PDSCH opportunity or the repetition does not overlap with the non-SBFD semi-static / dynamic UL codeword and does not overlap with the SBFD semi-static / dynamic UL codeword, the SBFD semi-static / dynamic DL codeword, and / or the SBFD dynamic FL codeword. Alternatively / furthermore, the UE may also assume / judge / determine / interpret that multiple opportunities of the downlink data channel are rate matched in time units other than the time units in the SBFD operation. That is, the UE may also assume / judge / determine / interpret that PDSCH opportunities or repetitions are rate matched on symbols other than SBFD semi-static / dynamic UL symbols, SBFD semi-static / dynamic DL symbols, and / or SBFD semi-static / dynamic FL symbols.

[0366] In addition, when multiple opportunities of the downlink data channel overlap with the time unit in the SBFD operation, the UE may also control the reception operation of the downlink data channel according to whether the downlink data channel overlaps with the uplink subband in the time unit. For example, in the case where the allocated PRB notified through FDRA does not overlap with the UL subband in the SBFD semi-static / dynamic UL symbol, the SBFD semi-static / dynamic DL symbol, and / or the SBFD semi-static / dynamic FL symbol, the UE may also determine the RB for each TRP and receive multiple opportunities of the downlink data channel on the notified / set resources in the same manner as Rel-16. On the other hand, the UE may not assume / judge / determine / interpret the situation where the allocated PRB notified through FDRA overlaps with the UL subband in the SBFD semi-static / dynamic UL symbol, the SBFD semi-static / dynamic DL symbol, and / or the SBFD semi-static / dynamic FL symbol. Alternatively or further, in the case where the allocated PRBs notified through FDRA overlap with the UL subbands in the SBFD semi-static / dynamic UL symbols, SBFD semi-static / dynamic DL symbols, and / or SBFD semi-static / dynamic FL symbols, the UE may not receive opportunities for downlink data channels for both TCI states. Alternatively or further, resources for opportunities for downlink data channels may be deferred to time units in which resources for opportunities for downlink data channels do not overlap with non-SBFD semi-static / dynamic UL symbols and do not overlap with any UL subbands in the SBFD semi-static / dynamic UL symbols, SBFD semi-static / dynamic DL symbols, and / or SBFD semi-static / dynamic FL symbols. Alternatively or further, the PRB allocation for each TCI state may also follow the rules of Rel-16, and opportunities for downlink data channels that overlap with UL subbands may also be discarded. Alternatively or further, the PRB allocation for each TCI state may also follow the rules of Rel-16, and opportunities for downlink data channels that overlap with UL subbands may also be rate matched on DL RBs. Alternatively or further, the PRB allocation for each TCI state may be based on the DL subband of each symbol excluding the UL subband.

[0367] (gNB Operation of Proposal 2)

[0368] In Proposal 2, the gNB may also control the transmission operation of the downlink data channel in the uplink time unit in the non-time-frequency division duplex operation such as non-SBFD operation and / or the time unit in the time-frequency division duplex operation such as SBFD operation, and perform the transmission operation of the downlink data channel through the controlled transmission operation. Here, the time-frequency division duplex may also be SBFD, and the uplink time unit in the non-time-frequency division duplex operation may also be the UL symbol, time slot, or any other time unit in the non-SBFD operation, specifically, it may also be the non-SBFD semi-static / dynamic UL symbol, and / or the non-SBFD dynamic FL symbol. In addition, the time unit in the time-frequency division duplex operation may also be the UL, DL, or FL symbol, time slot, or any other time unit in the SBFD operation, specifically, it may also be the SBFD semi-static / dynamic UL symbol, the SBFD semi-static / dynamic DL symbol, and / or the SBFD dynamic FL symbol. In addition, the downlink data channel may also be, for example, PDSCH, PDSCH repetition, etc.

[0369] UE Capability

[0370] For PDSCH enhancement for time-frequency division duplex operations such as the above-mentioned SBFD operation, UE capability information indicating whether the UE supports s-DCI-based m-TRP PDSCH enhancement for time-frequency division duplex operation may also be specified. In addition, UE capability information related to PDSCH transmission of multiple transmit and receive points for time-frequency division duplex such as SBFD operation may also be specified. In the case of supporting s-DCI-based MTRP PDSCH enhancement for time-frequency division duplex operation, the UE may also send UE capability information indicating support for s-DCI-based MTRP PDSCH enhancement for time-frequency division duplex operation to the gNB. If the UE capability information is received, the gNB can send the s-DCI-based MTRP PDSCH enhanced for time-frequency division duplex operation to the UE and enable the UE to perform the enhanced PDSCH reception operation in the SBFD operation.

[0371] In addition, UE capability information indicating whether the UE supports s-DCI-based m-TRPPDSCH enhancement for time-frequency division duplex operation based on SFN / tdmSchemeA / tdmSchemeB (i.e., based on a set number of iterations) / fdmSchemeA / fdmSchemeB may also be specified. In the case of supporting s-DCI-based m-TRP PDSCH enhancement for such time-frequency division duplex operation, the UE may also send UE capability information indicating support for s-DCI-based m-TRPPDS CH enhancement for time-frequency division duplex operation to the gNB. If the UE capability information is received, the gNB is able to send the s-DCI-based m-TRP PDSCH enhanced for time-frequency division duplex operation to the UE and enable the UE to perform the enhanced PDSCH reception operation in the time-frequency division duplex operation.

[0372] According to the above-mentioned proposal 2, PDSCH enhancement for time-frequency division duplex operation such as SBFD operation can be realized. Specifically, it is possible to define frequency-division multiplexed PDSCH opportunities or repeated reception operations based on UEs in SBFD operation and non-SBFD operation.

[0373] [Proposal 3]

[0374] In Proposal 3, HARQ-ACK enhancement for time-frequency division duplex operation such as SBFD operation is described. Specifically, the HARQ-ACK CB for SPS D SCH and the Type 1 HARQ-ACK CB (Type 1 HARQ-ACK CB) are enhanced for SBFD operation as follows.

[0375] About HARQ-ACK for SPS PDSCH

[0376] <Alt 1>

[0377] Regardless of SBFD operation or non-SBFD operation, when a symbol included in the resources for receiving the SPS PDSCH overlaps with a semi-statically configured UL symbol, the UE excludes the SPS PDSCH from generating the HARQ-ACK CB. That is, the HARQ-ACK bit for the SPS PDSCH may not be generated.

[0378] <Alt 2>

[0379] When a symbol included in the resources for receiving the SPS PDSCH overlaps with a semi-statically configured non-SBFD UL symbol, the UE excludes the SPS PDSCH from the generation of the HARQ-ACK CB. In other words, the HARQ-ACK bits for the SPS PDSCH may not be generated.

[0380] <Alt 3>

[0381] When a symbol included in the resources for receiving the SPS PDSCH overlaps with a semi-statically configured UL symbol or UL subband, the UE excludes the SPS PDSCH from the generation of the HARQ-ACK CB. In other words, the HARQ-ACK bits for the SPS PDSCH may not be generated.

[0382] <Alt 4>

[0383] Regardless of SBFD operation or non-SBFD operation, when the codeword included in the resources for receiving the SPS PDSCH overlaps with the semi-statically configured UL codeword or SBFD DL / FL codeword, 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.

[0384] <Alt 5>

[0385] When the symbols included in the resources for receiving the SPS PDSCH overlap with the semi-statically configured UL symbols or UL subbands secured for non-SBFD operation, 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.

[0386] <Alt 6>

[0387] When performing SBFD operation, the UE does not exclude the SPS PDSCH from the generation of the HARQ-ACK CB.

[0388] About Type 1 HARQ-ACK

[0389] <Alt 1>

[0390] Regardless of SBFD operation and non-SBFD operation, when the SLIV of the PDSCH overlaps with a semi-statically configured UL symbol, the UE excludes the SLIV of the PDSCH from the generation of the HARQ-ACK CB. That is, the HARQ-ACK bit for the SLIV of the PDSCH may not be generated.

[0391] <Alt 2>

[0392] When the SLIV of the PDSCH overlaps with a non-SBFD UL symbol configured semi-statically, the UE excludes the SLIV of the PDSCH from the generation of the HARQ-ACK CB. In other words, the HARQ-ACK bit for the SLIV of the PDSCH may not be generated.

[0393] <Alt 3>

[0394] When the SLIV of the PDSCH overlaps with a semi-statically configured UL symbol or UL subband, the UE excludes the SLIV of the PDSCH from the generation of the HARQ-ACK CB. That is, the HARQ-ACK bit for the SLIV of the PDSCH may not be generated.

[0395] <Alt 4>

[0396] Regardless of SBFD operation or non-SBFD operation, when the SLIV of the PDSCH overlaps with a semi-statically configured UL symbol or SBFD DL / FL symbol, the UE excludes the SLIV of the PDSCH from the generation of the HARQ-ACK CB. That is, the HARQ-ACK bit for the SLIV of the PDSCH may not be generated.

[0397] <Alt 5>

[0398] When the SLIV of the PDSCH overlaps with a semi-statically configured UL symbol or UL subband secured for non-SBFD operation, the UE excludes the SLIV of the PDSCH from the generation of the HARQ-ACK CB. That is, the HARQ-ACK bit for the SLIV of the PDSCH may not be generated.

[0399] <Alt 6>

[0400] When performing SBFD operation, the UE does not exclude SLIV of PDSCH from the generation of HARQ-ACK CB.

[0401] In addition, the UE can semi-statically / dynamically determine the HARQ-ACK codebook (which may also be referred to as the HARQ-ACK size). The HARQ-ACK codebook may also be rewritten as the HARQ-ACK codebook of the PDSCH, the HARQ-ACK codebook size, the number of HARQ-ACK bits, and the like.

[0402] (SPS HARQ-ACK codebook)

[0403] Regarding the generation of the HARQ-ACK codebook for SPS, the SPS PDSCH may be excluded in accordance with the following Alt1 to 6.

[0404] <Alt 1>

[0405] In Alt 1, when a symbol included in an SPS PDSCH or a resource for repeated reception of the SPS PDSCH overlaps with at least one semi-static UL symbol regardless of the SBFD operation or the non-SBFD operation, the SPS PDSCH may be excluded.

[0406] <Alt 2>

[0407] In Alt 2, when a symbol included in an SPS PDSCH or a resource for repeated reception of an SPS PDSCH overlaps with at least one non-SBFD semi-static UL symbol, the SPS PDSCH may be excluded.

[0408] <Alt 3>

[0409] In Alt 3, the SPS PDSCH may also be excluded when the codeword included in the SPS PDSCH or the resources for repeated reception of the SPS PDSCH overlaps with at least one non-SBFD semi-static UL codeword, or overlaps with the UL subband in the SBFD semi-static UL codeword, the SBFD semi-static DL codeword, and / or the SBFD semi-static FL codeword.

[0410] <Alt 4>

[0411] In Alt 4, when the codeword included in the SPS PDSCH or the resources for repeated reception of the SPS PDSCH overlaps with at least one semi-static UL codeword or SBFD DL / FL codeword regardless of the SBFD operation or the non-SBFD operation, the SPS PDSCH can also be excluded.

[0412] <Alt 5>

[0413] In Alt 5, when a symbol included in the SPS PDSCH or a resource for repeated reception of the SPS PDSCH overlaps with at least one semi-static UL symbol secured for non-SBFD defined by the specification or configured by RRC, the SPS PDSCH may be excluded.

[0414] <Alt 6>

[0415] In Alt 6, when the SBFD operation is indicated / set to be enabled, the SPS PDSCH or the repetition of the SPS PDSCH may not be deleted.

[0416] From a standardization point of view, when SBFD operation (or DL / UL subband allocation) is set by RRC, Alt 2 may be the most likely. In addition, when SBFD operation (or DL / UL subband allocation) is dynamically notified, Alt 5 / 6 may be the most likely.

[0417] In addition, which of the above Alts to apply can 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 should be applied can also be sent in at least one of RRC, DCI, and MAC CE (Medium Access Control Control Element).

[0418] (Type 1 HARQ-ACK (Type 1 HARQ-ACK) codebook)

[0419] For the generation of the Type 1 HARQ-ACK (Type 1 HARQ-ACK) codebook, for TDRA pruning, the SLIV (Start and Length Indicator Value) in the candidate PDSCH time slot n_D can also be deleted according to the following Alt 1 to 6. Here, Type 1 HARQ-ACK CB (Type 1 HARQ-ACK CB) can also be referred to as a semi-statically set HARQ-ACK CB, and Type 2 HARQ-ACK CB (Type 2 HARQ-ACK CB) can also be referred to as a dynamically set HARQ-ACK CB. In addition, HARQ-ACK CB can also be rewritten as the HARQ-ACK CB of PDSCH, the HARQ-ACK CB size, the number of HARQ-ACK bits, etc.

[0420] <Alt 1>

[0421] In Alt 1, for the slave time slot (n_D-N PDSCH repeat +1) to time slot n_D, when the SLIV overlaps with at least one semi-static UL codeword regardless of SBFD operation or non-SBFD operation, the SLIV in the candidate PDSCH time slot n_D can also be deleted.

[0422] <Alt 2>

[0423] In Alt 2, for the slave time slot (n_D-N PDSCH repeat+1) to time slot n_D, when SLIV overlaps with at least one non-SBFD semi-static UL codeword, SLIV in candidate PDSCH time slot n_D can also be deleted.

[0424] <Alt 3>

[0425] In Alt 3, for the slave time slot (n_D-N PDSCH repeat +1) to time slot n_D, when SLIV overlaps with at least one non-SBFD semi-static UL codeword, or overlaps with the UL subband in SBFD semi-static UL codewords, SBFD semi-static DL codewords, and / or SBFD semi-static FL codewords, the SLIV in the candidate PDSCH time slot n_D can also be deleted.

[0426] <Alt 4>

[0427] In Alt 4, for the slave time slot (n_D-N PDSCH repeat +1) to slot n_D, when the SLIV overlaps with at least one semi-static UL symbol or SBFD DL / FL symbol regardless of SBFD operation or non-SBFD operation, the SLIV in the candidate PDSCH slot n_D may also be deleted.

[0428] <Alt 5>

[0429] In Alt 5, for the slave time slot (n_D-N PDSCH repeat +1) In each time slot from time slot n_D, when SLIV overlaps with at least one semi-static UL codeword guaranteed for non-SBFD specified by the specification or set by RRC, SLIV in candidate PDSCH time slot n_D can also be deleted.

[0430] <Alt 6>

[0431] In Alt 6, SLIV may not be deleted if SBFD operation is indicated / set to enabled.

[0432] From a standardization point of view, when SBFD operation (or DL / UL subband allocation) is set by RRC, Alt 2 may be the most likely. In addition, when SBFD operation (or DL / UL subband allocation) is dynamically notified, Alt 5 / 6 may be the most likely.

[0433] In addition, which of the above Alts to apply can 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 should be applied can also be sent in at least one of RRC, DCI, and MAC CE (Medium Access Control Control Element).

[0434] In addition, the notification may be notified by high-layer signaling per component carrier, per cell group (CG), per PUCCH group, or per UE. The UE may also determine (generate) HARQ-ACK information bits based on the determined HARQ-ACK codebook per component carrier, per cell group (CG), per PUCCH group, or per UE, and send the generated HARQ-ACK using at least one of PUCCH or PUSCH.

[0435] In addition, N PDSCH repeat In SPS-Config, in pdsch-AggregationFactor-r16 or in PDSCH-Config, pdsch-AggregationFactor is provided to the UE, and in the case that no entry in pdsch-TimeDomainAllocationList and pdsch-TimeDomainAllocationListDCI-1-2 contains repetitionNumber in PDSCH-TimeDomainResourceAllocationList, N PDSCH repeat It can also be the maximum value of pdsch-AggregationFactor-r16 in SPS-Config or pdsch-AggregationFactor in PDSCH-Config. If this is not the case, it can also be N PDSCH repeat =1.

[0436] (UE operation of Proposal 3)

[0437] In Proposal 3, the UE may also determine the HARQ-ACK codebook for the downlink data channel based on whether the downlink data channel overlaps with the uplink time unit, and send a delivery confirmation in accordance with the HARQ-ACK codebook. For example, the downlink data channel may also be a PDSCH and / or a repetition of a PDSCH. In addition, the uplink time unit may also be a semi-statically set symbol, but may also be a time slot, a subframe, or a frame.

[0438] Specifically, the UE may also exclude the SPS PDSCH from the determination of the HARQ-ACK codebook when the SPS PDSCH overlaps with a UL codeword set semi-statically. Specifically, the UE may also determine the method of generating the SPS HARQ-ACK CB based on whether the codewords included in the resources for receiving the SPS PDSCH (each repetition) overlap with the semi-static UL codewords. For example, the UE may also exclude the SPS PDSCH from the generation of the HARQ-ACK CB when the codewords included in the resources for receiving the SPS PDSCH overlap with the UL codewords set semi-statically, regardless of the SBFD operation and the non-SBFD operation. Furthermore / or, the UE may also exclude the SPS PDSCH from the generation of the HARQ-ACK CB when the codewords included in the resources for receiving the SPS PDSCH overlap with the non-SBFD UL codewords set semi-statically. Furthermore / or, the UE may also exclude the SPS PDSCH from the generation of the HARQ-ACK CB when the codewords included in the resources for receiving the SPS PDSCH overlap with the UL codewords or UL subbands set semi-statically. Furthermore / or, the UE may also exclude the SPS PDSCH from the generation of the HARQ-ACK CB when the codewords included in the resources for receiving the SPS PDSCH overlap with the UL codewords or SBFD DL / FL codewords set semi-statically, regardless of the SBFD operation and the non-SBFD operation. Furthermore / or, the UE may also exclude the SPS PDSCH from the generation of the HARQ-ACK CB when the codewords included in the resources for receiving the SPS PDSCH overlap with the UL codewords or UL subbands set semi-statically and ensured for the non-SBFD operation. That is, the HARQ-ACK bit for the SPS PDSCH may also not be generated. Furthermore / or, the UE may not exclude the SPS PDSCH from the generation of the HARQ-ACK CB when performing the SBFD operation.

[0439] In addition, the UE may also exclude the SLIV from the determination of the HARQ-ACK codebook when the SLIV of the downlink data channel overlaps with an uplink codeword that is semi-statically set. Specifically, the UE may also determine the method of generating a Type 1 HARQ-ACK CB (Type 1 HARQ-ACK CB) for each time slot of the PDSCH according to whether the SLIV of the PDSCH overlaps with a semi-static UL codeword. For example, the UE may also exclude the SLIV of the PDSCH from the generation of the HARQ-ACK CB when the SLIV of the PDSCH overlaps with a UL codeword that is semi-statically set, regardless of the SBFD operation and the non-SBFD operation. Furthermore / or, the UE may also exclude the SLIV of the PDSCH from the generation of the HARQ-ACK CB when the SLIV of the PDSCH overlaps with a non-SBFD UL codeword that is semi-statically set. Furthermore / or, the UE may also exclude the SLIV of the PDSCH from the generation of the HARQ-ACK CB when the SLIV of the PDSCH overlaps with a UL symbol or UL subband that is semi-statically set. Furthermore / or, the UE may also exclude the SLIV of the PDSCH from the generation of the HARQ-ACK CB when the SLIV of the PDSCH overlaps with a UL symbol or UL subband that is semi-statically set, regardless of the SBFD operation and the non-SBFD operation. Furthermore / or, the UE may also exclude the SLIV of the PDSCH from the generation of the HARQ-ACK CB when the SLIV of the PDSCH overlaps with a UL symbol or UL subband that is semi-statically set and ensured for the non-SBFD operation. That is, the HARQ-ACK bit for the SLIV of the PDSCH may also not be generated. Furthermore / or, the UE may not exclude the SLIV of the PDSCH from the generation of the HARQ-ACK CB when performing the SBFD operation.

[0440] In addition, the UE may also determine the HARQ-ACK codebook for the downlink data channel according to whether the SBFD operation is semi-statically set or dynamically notified. In addition, the generation method of the SPS HARQ-ACK CB and / or the generation method of the Type 1 HARQ-ACK CB (Type 1 HARQ-ACK CB) may also be specified by the specification, or semi-statically set by RRC settings, etc., or dynamically notified by DCI notifications, etc., or determined by the UE in accordance with specific rules. In addition, the generation method of the SPS HARQ-ACK CB and / or the generation method of the Type 1 HARQ-ACK CB (Type 1 HARQ-ACK CB) may also be explicitly or implicitly specified, set, notified or applied. Parameters indicating the above-mentioned SPS HARQ-ACK CB generation method and / or Type 1 HARQ-ACK CB generation method may also be transmitted in at least one of RRC, DCI and MAC CE (Medium Access Control Control Element).

[0441] (gNB Operation of Proposal 3)

[0442] In Proposal 3, the gNB may also send a downlink data channel and receive a delivery confirmation following the HARQ-ACK codebook for the downlink data channel determined based on whether the downlink data channel overlaps with the uplink time unit. For example, the downlink data channel may also be a PDSCH and / or a repetition of a PDSCH. In addition, the uplink time unit may also be a symbol set semi-statically, but may also be a time slot, a subframe, or a frame.

[0443] UE Capability

[0444] For HARQ-ACK enhancement for time-frequency division duplex operation such as the above-mentioned SBFD operation, UE capability information indicating whether the UE supports the HARQ-ACK enhancement for time-frequency division duplex operation may also be specified. In addition, UE capability information related to HARQ-ACK transmission for time-frequency division duplex such as SBFD operation may also be specified. In the case of supporting HARQ-ACK enhancement for time-frequency division duplex operation, the UE may also send UE capability information indicating support for HARQ-ACK enhancement for time-frequency division duplex operation to the gNB. If the UE capability information is received, the gNB is able to follow the HARQ-ACK enhancement for time-frequency division duplex operation and receive the HARQ-ACK CB for the PDSCH from the UE.

[0445] According to the above-mentioned proposal 3, HARQ-ACK enhancement for time-frequency division duplex operation such as SBFD operation can be achieved.

[0446] (PUSCH in Rel-15 / 16 / 17)

[0447] According to Rel-15 / 16 / 17, it is stipulated that PUSCH or PUSCH repetitions overlapping with semi-static DL symbols are not transmitted. That is, it is stipulated that for the symbol set of the time slot notified to the UE as a downlink through tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, even when the symbol included in the resource for transmitting PUSCH, PUCCH, PRACH or SRS partially overlaps with the symbol set of the time slot, the UE shall not transmit PUSCH, PUCCH, PRACH or SRS.

[0448] In addition, it is stipulated that when the UE is scheduled through the DCI format to send PUSCH over multiple time slots, and in tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated for a time slot of these multiple time slots, if at least one codeword of the codeword set scheduled for PUSCH transmission to the UE in the time slot is a downlink codeword, the UE shall not send PUSCH in the time slot.

[0449] In addition, according to Rel-15 / 16 / 17, it is stipulated that PUSCH or PUSCH repetitions overlapping with dynamic DL symbols / FL symbols are not transmitted. That is, it is stipulated that the UE is set by the upper layer to transmit PUSCH, PUCCH, PRACH or SRS in the symbol set of the time slot, and in addition, when the UE detects DCI format 2_0 based on a time slot format value other than 255 for notifying the time slot format as a downlink or flexible with a symbol subset from the symbol set, or when the UE detects a DCI format for notifying the UE to receive PDSCH or CSI-RS in at least one symbol in the symbol set, and when a specific condition is met, the UE cancels the PUSCH, PUCCH, PRACH or SRS transmission in the symbol set.

[0450] In Rel-15 NR, single transmission and reception point (s-TRP) PUSCH based on no repetition or slot-based PUSCH repetition, that is, PUSCH repetition type A is supported. For example, in slot-based PUSCH repetition, Fig.21A As shown, PUSCH repetitions can be transmitted over multiple time slots.

[0451] In addition, in Rel-16 NR, single transmission and reception point (s-TRP) PUSCH based on no repetition or sub-slot-based PUSCH repetition, that is, PUSCH repetition type B is supported. Fig. 21B In the specific example shown, the slot-based PUSCH repetition of Rel-15 and the sub-slot-based PUSCH repetition of Rel-16 are shown when the repetition coefficient K is 4 and the PUSCH length is 6.

[0452] In addition, in Rel-17 NR, TDM m-TRP PUSCH repetition type A and type B are supported. Specifically, two beam / power control parameter sets and cyclic and sequential mapping between repetitions are supported. Fig. 22 As shown, in repetition type A based on 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 based on cyclic mapping, different beam / power control parameters can be set for two TRPs for repetition #1 and repetition #2. In addition, for repetition type B, one nominal repetition is segmented into two actual repetitions at the time slot boundary. In addition, cyclic repetition type A and sequential repetition type B are also possible.

[0453] (Multi-PUSCH Scheduling)

[0454] When scheduling multiple PUSCHs, DCI 0_1 is used as the DCI format. Fig.23 As shown, PUSCH#1~#4 can be scheduled by one DCI. Here, it is stipulated that the maximum number of PUSCHs that support 120, 480, 960kHz SCS and can be scheduled by one DCI is 8. In addition, for TDRA, different {SLIV, mapping type, scheduling offset K2} can be applied to each PUSCH in the row of the TDRA table. In the case of a PUSCH conflict with a semi-static DL codeword or SSB codeword, the PUSCH is cancelled, but it is not assumed that all PDSCHs are cancelled.

[0455] In addition, the MCS, NDI and RV of the first TB field appear only once and are applied to the first TB of each PUSCH. In addition, it is specified that the HPN field is applied to the first valid PUSCH and increases by 1 for subsequent PUSCHs, and does not increase for invalid PUSCHs (i.e., PUSCHs that conflict with semi-static DL symbols or SSB symbols).

[0456] [Study items related to PUSCH enhancements for SBFD operation]

[0457] For SBFD operations in Rel-18, the following contents are studied.

[0458] SBFD operation in DL symbols, i.e. DL and UL subbands in DL symbols

[0459] SBFD operation in UL symbols, i.e. DL and UL subbands in UL symbols

[0460] SBFD operation in flexible (FL) symbols, i.e., DL and UL subbands in FL symbols

[0461] Here, in case SBFD operation in DL symbols is supported or set to enabled, PUSCH or PUSCH repetitions overlapping with DL symbols may not necessarily be dropped. Therefore, the rules for TDD collision in Rel-15 / 16 / 17 may need to be updated for SBFD operation.

[0462] For example, UL and DL symbols or time slots in TDD are set to be tdd-UL-DL-ConfigurationCommon as Fig.24 In this case, according to the rules of Rel-15 / 16 / 17, PUSCH rep#1 and #2 in the PUSCH repetition are discarded. On the other hand, if SBFD operation is considered, PUSCH rep#2 can be sent in the UL subband, so it can be considered that the UE can send PUSCH rep#2.

[0463] [Proposal 4]

[0464] In Proposal 4, PUSCH enhancement for time-frequency division duplex operation such as SBFD operation is described. Specifically, PUSCH repetition type A is enhanced for SBFD operation as follows.

[0465] Case 1: PUSCH resources overlap with non-SBFD DL symbols

[0466] <Alt A>

[0467] The UE does not send PUSCH.

[0468] <Alt B>

[0469] The UE postpones the transmission of the PUSCH.

[0470] Case 2: PUSCH resources overlap with SBFD symbols

[0471] <Alt 1>

[0472] The UE operates according to the following Alt 1-1 to 1-3 regardless of the presence or absence of overlap with the DL subband.

[0473] <<Alt 1-1>>

[0474] The UE does not send PUSCH.

[0475] <<Alt 1-2>>

[0476] The UE defers the transmission of PUSCH to non-SBFD UL resources.

[0477] <<Alt 1-3>>

[0478] The UE performs rate matching on the PUSCH in resources other than the SBFD symbols.

[0479] <Alt 2>

[0480] The UE operates according to Alt 2-1 to 2-3 below, depending on whether there is overlap with the DL subband.

[0481] <<Alt 2-1>>

[0482] The UE does not send PUSCH.

[0483] <<Alt 2-2>>

[0484] The UE performs rate matching on the PUSCH in the UL subband.

[0485] <<Alt 2-3>>

[0486] The UE postpones the transmission of the PUSCH.

[0487] For s-TRP PUSCH, s-TRP PUSCH repetition type A or m-TRP PUSCH repetition type A, the UE controls the PUSCH transmission operation according to the following scenarios 1 and 2. That is,

[0488] Case 1: The codewords included in the resources for transmitting PUSCH or PUSCH repetition based on repetition type A overlap with at least one non-SBFD semi-static / dynamic DL codeword (or non-SBFD dynamic FL codeword), SSB codeword or type-0 CORESET (type-0CORESET) codeword.

[0489] Case 2: The codewords included in the resources used for sending PUSCH or PUSCH repetition based on repetition type A do not overlap with any non-SBFD semi-static / dynamic DL codewords (or non-SBFD dynamic FL codewords), but overlap with at least one SBFD semi-static / dynamic DL codeword, at least one SBFD semi-static / dynamic UL codeword, and / or at least one SBFD semi-static / dynamic FL codeword.

[0490] (Scenario 1)

[0491] As in Case 1, when the codewords included in the resources used for sending PUSCH or PUSCH repetition based on repetition type A overlap with at least one non-SBFD semi-static / dynamic DL codeword (or non-SBFD dynamic FL codeword), SSB codeword or type-0 CORESET (type-0 CORESET) codeword, the UE may also operate according to the following Alt-A and / or Alt-B.

[0492] <Case 1: Alt-A>

[0493] In Alt-A, when a symbol included in resources for transmitting a PUSCH or a PUSCH repetition based on repetition type A overlaps with at least one non-SBFD semi-static / dynamic DL symbol (or non-SBFD dynamic FL symbol), SSB symbol, or type-0 CORESET symbol, the UE may not transmit the PUSCH or PUSCH repetition. That is, the UE may not transmit the PUSCH or PUSCH repetition that overlaps with a DL symbol or FL symbol in non-SBFD operation.

[0494] In addition, as a variation example, when a codeword included in the resources used for sending a PUSCH or a PUSCH repetition overlaps with at least one non-SBFD semi-static / dynamic DL codeword (or a non-SBFD dynamic FL codeword), an SSB codeword or a type-0 CORESET codeword and is not sent, and when the PUSCH or PUSCH repetition is one or any one of a plurality of PUSCHs scheduled by a single DCI, the HPN (HARQ Process Number) may also be skipped for the PUSCH or PUSCH repetition.

[0495] <Case 1: Alt-B>

[0496] In Alt-B, when a symbol included in resources for transmitting a PUSCH or a PUSCH repetition based on repetition type A overlaps with at least one non-SBFD semi-static / dynamic DL symbol (or non-SBFD dynamic FL symbol), SSB symbol, or type-0 CORESET symbol, the UE may also postpone the PUSCH or PUSCH repetition to a slot / subslot in which a symbol included in resources for transmitting the PUSCH or PUSCH repetition does not overlap with a non-SBFD semi-static / dynamic DL symbol (or non-SBFD dynamic FL symbol), SSB symbol, or type-0 CORESET symbol. That is, the UE may also transmit the PUSCH or PUSCH repetition that overlaps with a DL symbol or FL symbol in a non-SBFD operation in any subsequent slot / subslot that does not overlap with a DL symbol or FL symbol in a non-SBFD operation. Alternatively, the UE may send a PDSCH or PDSCH repetition that overlaps with a UL symbol or FL symbol in a non-SBFD operation in any subsequent symbol, subslot, subframe, frame or other time unit that does not overlap with a UL symbol or FL symbol in a non-SBFD operation.

[0497] (Scenario 2)

[0498] As in Case 2, when the codewords included in the resources for sending PUSCH or PUSCH repetition based on repetition type A do not overlap with any non-SBFD semi-static / dynamic DL codewords (or non-SBFD dynamic FL codewords), but overlap with at least one SBFD semi-static / dynamic DL codeword, at least one SBFD semi-static / dynamic UL codeword, and / or at least one SBFD semi-static / dynamic FL codeword, the UE may also operate according to the following Alt 1 and / or Alt 2.

[0499] <Case 2: Alt 1>

[0500] In Alt 1, when the codewords included in the resources for sending PUSCH or PUSCH repetition based on repetition type A do not overlap with any non-SBFD semi-static / dynamic DL codewords (or non-SBFD dynamic FL codewords), but overlap with at least one SBFD semi-static / dynamic DL codeword, at least one SBFD semi-static / dynamic UL codeword, and / or at least one SBFD semi-static / dynamic FL codeword, the UE may also operate in accordance with the following Alt 1-1, Alt 1-2 and / or Alt 1-3 regardless of whether there is overlap with the DL subband.

[0501] <<Scenario 2: Alt 1-1>>

[0502] In Alt 1-1, when the symbol included in the resource for transmitting the PUSCH or the PUSCH repetition based on the repetition type A does not overlap with any non-SBFD semi-static / dynamic DL symbol (or non-SBFD dynamic FL symbol) but overlaps with at least one SBFD semi-static / dynamic DL symbol, at least one SBFD semi-static / dynamic UL symbol, and / or at least one SBFD semi-static / dynamic FL symbol, the UE may not transmit the PUSCH or the PUSCH repetition regardless of the presence or absence of overlap with the DL subband. That is, the UE may not transmit the PUSCH or the PUSCH repetition that overlaps with the UL symbol, the DL symbol, or the FL symbol in the SBFD operation.

[0503] In addition, as a variation, PUSCH repetitions that are not transmitted due to overlap with SBFD semi-static / dynamic UL symbols, SBFD semi-static / dynamic DL symbols, and / or SBFD dynamic FL symbols may be counted as the number of repetitions, or may not be counted.

[0504] In addition, as a variation, when the PUSCH is not sent due to overlap with SBFD semi-static / dynamic UL symbols, SBFD semi-static / dynamic DL symbols, and / or SBFD dynamic FL symbols, and when the PUSCH or PUSCH repetition is one or any one of multiple PUSCHs scheduled via a single DCI, the HPN may be skipped or not skipped for the PUSCH or PUSCH repetition.

[0505] <<Scenario 2: Alt 1-2>>

[0506] In Alt 1-2, when the codewords included in the resources for sending PUSCH or PUSCH repetition based on repetition type A do not overlap with any non-SBFD semi-static / dynamic DL codewords (or non-SBFD dynamic FL codewords), but overlap with at least one SBFD semi-static / dynamic DL codeword, at least one SBFD semi-static / dynamic UL codeword, and / or at least one SBFD semi-static / dynamic FL codeword, the UE may also postpone the PUSCH or PUSCH repetition to a time slot / sub-time slot in which the codewords included in the resources for sending the PUSCH or PUSCH repetition do not overlap with the non-SBFD semi-static / dynamic DL codewords (or non-SBFD dynamic FL codewords) and do not overlap with any SBFD semi-static / dynamic UL codeword, any SBFD semi-static / dynamic DL codeword, and / or any SBFD semi-static / dynamic FL codeword, regardless of whether there is overlap with the DL subband. That is, the UE may also transmit the PUSCH or PUSCH repetition in any subsequent time slot / sub-slot that does not overlap with DL symbols or FL symbols in non-SBFD operation, and further, does not overlap with UL symbols, DL symbols, and / or FL symbols in SBFD operation. Alternatively, the UE may also transmit the PUSCH or PUSCH repetition in any subsequent time unit such as a symbol, sub-slot, subframe, frame, etc. that does not overlap with a non-SBFD semi-static / dynamic UL symbol (or a non-SBFD dynamic flexible symbol) and does not overlap with any SBFD semi-static / dynamic UL symbol, any SBFD semi-static / dynamic DL symbol, and / or any SBFD dynamic FL symbol.

[0507] In addition, such a deferral may also be set as a condition that requires additional addition. For example, the deferral may also be performed when the SBFD operation indication is set through RRC. In other words, when the SBFD operation is dynamically notified to the UE, the deferral may not be applied. That is, when the SBFD operation is dynamically notified to the UE, the UE may not send PUSCH or PUSCH repetitions. For example, when the SBFD operation is notified to the UE through DCI, the UE may not send PUSCH or PUSCH repetitions that do not overlap with any non-SBFD DL codeword (or non-SBFD dynamic FL codeword) but overlap with SBFD UL codewords, SBFD DL codewords, and / or SBFD FL codewords in subsequent codewords, time slots, etc.

[0508] <<Scenario 2: Alt 1-3>>

[0509] In Alt 1-3, when the codewords included in the resources used for sending PUSCH or PUSCH repetition based on repetition type A do not overlap with any non-SBFD semi-static / dynamic DL codewords (or non-SBFD dynamic FL codewords), but overlap with at least one SBFD semi-static / dynamic DL codeword, at least one SBFD semi-static / dynamic UL codeword, and / or at least one SBFD semi-static / dynamic FL codeword, the UE may also perform rate matching on the PUSCH or PUSCH repetition on codewords other than the SBFD semi-static / dynamic UL codewords, SBFD semi-static / dynamic DL codewords, and / or SBFD dynamic FL codewords.

[0510] Here, as a modified example, when the PUSCH or PUSCH repetition is one or any one of a plurality of PUSCHs scheduled by a single DCI, HPN may not be skipped for the PUSCH or PUSCH repetition.

[0511] <Case 2: Alt 2>

[0512] In Alt 2, when the codewords included in the resources for sending PUSCH or PUSCH repetition based on repetition type A do not overlap with any non-SBFD semi-static / dynamic DL codewords (or non-SBFD dynamic FL codewords), but overlap with at least one SBFD semi-static / dynamic DL codeword, at least one SBFD semi-static / dynamic UL codeword, and / or at least one SBFD semi-static / dynamic FL codeword, the UE controls the sending operation of PUSCH or PUSCH repetition according to whether there is overlap with the DL subband.

[0513] Specifically, in the case where the codeword included in the resources for sending PUSCH or PUSCH repetition based on repetition type A does not overlap with any non-SBFD semi-static / dynamic DL codeword (or non-SBFD dynamic FL codeword), but overlaps with at least one SBFD semi-static / dynamic DL codeword, at least one SBFD semi-static / dynamic UL codeword, and / or at least one SBFD semi-static / dynamic FL codeword, and in the case where the codeword included in the resources for sending PUSCH or PUSCH repetition does not overlap with the DL subband in the SBFD semi-static / dynamic UL codeword, SBFD semi-static / dynamic DL codeword, and / or SBFD semi-static / dynamic FL codeword, the UE may also send the PUSCH or PUSCH repetition in the notified or set resources. The resource may also be specified by the specification, or semi-statically set by RRC setting, etc., or dynamically notified by DCI notification, etc., or determined in accordance with a rule. In addition, the resource may also be explicitly or implicitly specified, set, notified or determined.

[0514] Here, as a modified example, when the PUSCH or PUSCH repetition is one or any one of a plurality of PUSCHs scheduled by a single DCI, HPN may not be skipped for the PUSCH or PUSCH repetition.

[0515] On the other hand, in the case where the codewords included in the resources for sending PUSCH or PUSCH repetition based on repetition type A do not overlap with any non-SBFD semi-static / dynamic DL codewords (or non-SBFD dynamic FL codewords), but overlap with at least one SBFD semi-static / dynamic DL codeword, at least one SBFD semi-static / dynamic UL codeword, and / or at least one SBFD semi-static / dynamic FL codeword, and in the case where the codewords included in the resources for sending PUSCH or PUSCH repetition overlap with DL subbands in SBFD semi-static / dynamic UL codewords, SBFD semi-static / dynamic DL codewords, and / or SBFD semi-static / dynamic FL codewords, the UE may also operate in accordance with the following Alt 2-1, Alt 2-2, and / or Alt 2-3.

[0516] <<Scenario 2: Alt 2-1>>

[0517] In Alt 2-1, when the symbols included in the resources for transmitting the PUSCH or PUSCH repetition based on repetition type A do not overlap with any non-SBFD semi-static / dynamic DL symbols (or non-SBFD dynamic FL symbols), but overlap with at least one SBFD semi-static / dynamic DL symbol, at least one SBFD semi-static / dynamic UL symbol, and / or at least one SBFD semi-static / dynamic FL symbol, and when the symbols included in the resources for transmitting the PUSCH or PUSCH repetition overlap with DL subbands in SBFD semi-static / dynamic UL symbols, SBFD semi-static / dynamic DL symbols, and / or SBFD semi-static / dynamic FL symbols, the UE may not transmit the PUSCH or PUSCH repetition. That is, the UE may not transmit the PUSCH or PUSCH repetition that overlaps with DL subbands in UL symbols, DL symbols, or FL symbols in SBFD operation.

[0518] In addition, as a variation, PUSCH repetitions that are not transmitted due to overlap with DL subbands in SBFD semi-static / dynamic UL symbols, SBFD semi-static / dynamic DL symbols, and / or SBFD dynamic FL symbols may be counted as the number of repetitions, or may not be counted.

[0519] Furthermore, as a variation, when the PUSCH or PUSCH repetition is one or any one of a plurality of PUSCHs scheduled by a single DCI, HPN may be skipped or may not be skipped for the PUSCH or PUSCH repetition.

[0520] <<Scenario 2: Alt 2-2>>

[0521] In Alt 2-2, when the codeword included in the resources for sending PUSCH or PUSCH repetition based on repetition type A does not overlap with any non-SBFD semi-static / dynamic DL codeword (or non-SBFD dynamic FL codeword), but overlaps with at least one SBFD semi-static / dynamic DL codeword, at least one SBFD semi-static / dynamic UL codeword, and / or at least one SBFD semi-static / dynamic FL codeword, and when the codeword included in the resources for sending PUSCH or PUSCH repetition overlaps with DL subbands in SBFD semi-static / dynamic UL codewords, SBFD semi-static / dynamic DL codewords, and / or SBFD semi-static / dynamic FL codewords, the UE may also perform rate matching on PUSCH or PUSCH repetition on UL subbands in SBFD semi-static / dynamic UL codewords, SBFD semi-static / dynamic DL codewords, and / or SBFD semi-static / dynamic FL codewords, and on non-SBFD semi-static / dynamic UL / FL codewords if any.

[0522] In addition, as a modified example, when the PUSCH or PUSCH repetition is one or any one of a plurality of PUSCHs scheduled by a single DCI, HPN may be skipped or may not be skipped for the PUSCH or PUSCH repetition.

[0523] <<Scenario 2: Alt 2-3>>

[0524] In Alt 2-3, in the case where the symbols included in the resources for transmission of the PUSCH or the PUSCH repetition based on repetition type A do not overlap with any non-SBFD semi-static / dynamic DL symbols (or non-SBFD dynamic FL symbols), but overlap with at least one SBFD semi-static / dynamic DL symbol, at least one SBFD semi-static / dynamic UL symbol, and / or at least one SBFD semi-static / dynamic FL symbol, and the symbols included in the resources for transmission of the PUSCH or the PUSCH repetition overlap with the SBFD semi-static / dynamic UL symbol, the SBFD semi-static / dynamic FL symbol. In the case where the DL subband in the static / dynamic DL symbol and / or the SBFD semi-static / dynamic FL symbol overlaps, the UE may postpone the transmission of the PUSCH or PUSCH repetition to a slot / subslot in which the symbol included in the resource for transmission of the PUSCH or PUSCH repetition does not overlap with the non-SBFD semi-static / dynamic DL symbol (or the non-SBFD dynamic FL symbol) and does not overlap with the DL subband of any of the SBFD semi-static / dynamic UL symbol, the SBFD semi-static / dynamic DL symbol, and / or the SBFD dynamic FL symbol. That is, the UE may transmit the PUSCH or PUSCH repetition in any subsequent slot / subslot that does not overlap with the UL symbol or FL symbol in the non-SBFD operation and does not overlap with the DL subband in the UL symbol, DL symbol, and / or FL symbol in the SBFD operation. Alternatively, the UE may also send the PUSCH or PUSCH repetition in any subsequent codeword, subframe, frame, or other time unit that does not overlap with a non-SBFD semi-static / dynamic UL codeword (or a non-SBFD dynamic flexible codeword) and does not overlap with the DL subband of any SBFD semi-static / dynamic UL codeword, SBFD semi-static / dynamic DL codeword, and / or SBFD dynamic FL codeword.

[0525] In addition, such a deferral may also be set as a condition that requires additional addition. For example, the deferral may also be performed when the SBFD operation indication is set through RRC. In other words, when the SBFD operation is dynamically notified to the UE, the deferral may not be applied. That is, when the SBFD operation is dynamically notified to the UE, the UE may not send PUSCH or PUSCH repetitions. For example, when the SBFD operation is notified to the UE through DCI, the UE may not send PUSCH or PUSCH repetitions in subsequent symbols, time slots, etc., which do not overlap with any non-SBFD UL symbols (or non-SBFD dynamic flexible symbols), but overlap with DL subbands in SBFD UL symbols, SBFD DL symbols, and / or SBFD FL symbols.

[0526] In addition, which of the above Alts to apply can 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 should be applied can also be sent in at least one of RRC, DCI, and MAC CE (Medium Access Control Control Element).

[0527] Here, when the above-mentioned solutions based on rate matching such as Alt 1-3 or Alt 2-2 are applied, it is necessary to study the TBS (Transport Block Size). For example, the TBS can also be determined according to the following options A and / or B.

[0528] <Option A>

[0529] In option A, TBS can also be based on

[0530] i) non-SBFD semi-static / dynamic DL symbol (or non-SBFD dynamic FL symbol), SSB symbol or type-0 CORESET symbol,

[0531] ii) SBFD semi-static / dynamic UL symbols, SBFD semi-static / dynamic DL symbols, and / or SBFD semi-static / dynamic FL symbols, and / or

[0532] iii) SBFD semi-static / dynamic UL symbols, SBFD semi-static / dynamic DL symbols, and / or DL ​​resource blocks (RBs) in SBFD semi-static / dynamic FL symbols,

[0533] The decision is made based on the number of resource elements (REs) after exclusion.

[0534] <Option B>

[0535] In option B, TBS may also be determined based on the number of REs notified through time domain resource allocation (TDRA) and frequency domain resource allocation (FDRA).

[0536] For example, for PUSCH repetition, when Option A is applied, the number of REs used for TBS calculation may be different for different repetitions. In such a case, the TBS of each repetition may be determined based on the maximum / minimum / average value of the TBS calculated for the first PUSCH repetition and / or the TBS values ​​calculated for all repetitions.

[0537] Which option to apply may be explicitly or implicitly specified by the specification, semi-statically set by RRC, dynamically notified by DCI, or determined by a rule. For example, a parameter indicating which option should be applied may be sent in at least one of RRC, DCI, and MAC CE. For example, the UE may receive setting information related to option A and option B through RRC, or may be dynamically notified through DCI which option of option A and option B should be applied.

[0538] (UE operation of Proposal 4)

[0539] In Proposal 4, the UE may also control the transmission operation of the uplink data channel according to whether the downlink time unit in non-time-frequency division duplex operation such as non-SBFD operation and / or the time unit in time-frequency division duplex operation such as SBFD operation overlaps with the uplink data channel, and perform the transmission operation of the uplink data channel through the controlled transmission operation. Here, the time-frequency division duplex may also be SBFD, and the downlink time unit in the non-time-frequency division duplex operation may also be a DL symbol, a mini-slot, a time slot, or any other time unit in the non-SBFD operation, specifically, it may also be a non-SBFD semi-static / dynamic DL symbol, and / or a non-SBFD dynamic FL symbol. In addition, the time unit in the time-frequency division duplex operation may also be a UL, DL or FL symbol, a mini-slot, a time slot, or any other time unit in the SBFD operation, specifically, it may also be a SBFD semi-static / dynamic UL symbol, a SBFD semi-static / dynamic DL symbol, and / or a SBFD dynamic FL symbol. Furthermore, the uplink data channel may be, for example, PUSCH, PUSCH repetition, or the like.

[0540] Specifically, when the uplink data channel overlaps with the downlink time unit or flexible time unit in the non-SBFD operation, the UE may not send the uplink data channel. Alternatively, / furthermore, when the uplink data channel overlaps with the downlink time unit or flexible time unit in the non-SBFD operation, the UE may send the uplink data channel in a time unit in which the uplink data channel does not overlap with the downlink time unit in the non-SBFD operation. That is, the UE may also postpone the transmission of the PUSCH or PUSCH repetition to a time slot in which the symbol included in the time domain resource for the transmission of the PUSCH or PUSCH repetition does not overlap with the non-SBFD semi-static / dynamic DL symbol.

[0541] In addition, when the uplink data channel overlaps with the time unit in the SBFD operation, the UE may also 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. For example, the UE may not transmit the uplink data channel. Alternatively / furthermore, the UE may also transmit the uplink data channel in a time unit in which the uplink data channel does not overlap with the downlink time unit or flexible time unit in the non-SBFD operation and does not overlap with the uplink time unit, downlink time unit, and / or flexible time unit in the SBFD operation. That is, the UE may also postpone the transmission of the PUSCH or PUSCH repetition to a time slot in which the resources of the PUSCH or PUSCH repetition do not overlap with the non-SBFD semi-static / dynamic DL symbol and do not overlap with the SBFD semi-static / dynamic UL symbol, the SBFD semi-static / dynamic DL symbol, and / or the SBFD dynamic FL symbol. Alternatively / furthermore, the UE may also rate match the uplink data channel in a time unit other than the time unit in the SBFD operation. That is, the UE may also perform rate matching on the PUSCH or PUSCH repetition on symbols other than SBFD semi-static / dynamic UL symbols, SBFD semi-static / dynamic DL symbols, and / or SBFD dynamic FL symbols.

[0542] In addition, when the uplink data channel overlaps with the time unit in the SBFD operation, the UE may also control the transmission operation of the uplink data channel according to whether the uplink data channel overlaps with the downlink subband in the time unit. For example, when the uplink data channel does not overlap with the downlink subband in the time unit, the UE may also send the uplink data channel on the set / notified resource. On the other hand, when the uplink data channel overlaps with the downlink subband in the time unit, the UE may not send the uplink data channel. Alternatively / furthermore, the UE may also rate match the uplink data channel on the DL subband in the time unit in the SBFD operation. Alternatively / furthermore, the UE may also send the uplink data channel in a time unit in which the uplink data channel does not overlap with the downlink time unit or flexible time unit in the non-SBFD operation and does not overlap with the uplink time unit, downlink time unit, and / or flexible time unit in the SBFD operation. That is, the UE may also postpone the transmission of PUSCH or PUSCH repetition to a time slot or mini-slot in which the resources of PUSCH or PUSCH repetition do not overlap with non-SBFD semi-static / dynamic DL codewords and do not overlap with SBFD semi-static / dynamic UL codewords, SBFD semi-static / dynamic DL codewords, and / or SBFD dynamic FL codewords.

[0543] (gNB Operation of Proposal 4)

[0544] In Proposal 4, the gNB may also control the reception operation of the uplink data channel in one or both of the downlink time unit in the non-time-frequency division duplex operation such as the non-SBFD operation and the time unit in the time-frequency division duplex operation such as the SBFD operation, and perform the reception operation of the uplink data channel through the controlled reception operation. Here, the time-frequency division duplex may also be SBFD, and the downlink time unit in the non-time-frequency division duplex operation may also be a DL symbol, a mini-slot, a time slot, or any other time unit in the non-SBFD operation, specifically, a non-SBFD semi-static / dynamic DL symbol, and / or a non-SBFD dynamic FL symbol. In addition, the time unit in the time-frequency division duplex operation may also be a UL, DL, or FL symbol, a mini-slot, a time slot, or any other time unit in the SBFD operation, specifically, a SBFD semi-static / dynamic UL symbol, a SBFD semi-static / dynamic DL symbol, and / or a SBFD dynamic FL symbol. In addition, the uplink data channel may also be, for example, PUSCH, PUSCH repetition, etc.

[0545] For PUSCH enhancement for time-frequency division duplex operation such as the above-mentioned SBFD operation, UE capability information indicating whether the UE supports PUSCH enhancement for time-frequency division duplex operation may also be specified. In addition, UE capability information related to PUSCH transmission for time-frequency division duplex such as SBFD operation may also be specified. Specifically, UE capability information indicating whether the UE supports s-TRP / m-TRP PUSCH repetition type A for time-frequency division duplex operation may also be specified. In the case of supporting PUSCH enhancement for time-frequency division duplex operation, the UE may also send UE capability information indicating support for PUSCH enhancement for SBFD operation to the gNB. If the UE capability information is received, the gNB is able to receive PUSCH from the UE in accordance with the PUSCH enhancement for time-frequency division duplex operation.

[0546] According to the above-mentioned Proposal 4, PUSCH enhancement for time-frequency division duplex operation such as SBFD operation can be achieved.

[0547] [Proposal 5]

[0548] In Proposal 5, PUSCH enhancement for time-frequency division duplex operation such as SBFD operation is described. Specifically, PUSCH repetition type B is enhanced for SBFD operation as follows.

[0549] The following invalid symbols are added.

[0550] (Option 0)

[0551] DL symbols that are semi-statically set regardless of SBFD operation and non-SBFD operation

[0552] (Option 1)

[0553] Semi-statically set non-SBFD DL symbols

[0554] (Option 2)

[0555] Semi-statically configured SBFD / non-SBFD DL symbols, UL / FL symbols overlapping with DL subbands

[0556] In the case where the actual repetition overlaps with non-SBFD FL symbols, the UE does not send PUSCH.

[0557] (Alt 1)

[0558] The UE does not transmit the PUSCH regardless of the presence or absence of overlap with the DL subband.

[0559] (Alt 2)

[0560] When the PUSCH and DL subbands overlap, the UE sends PUSCH. When the PUSCH and DL subbands do not overlap, the UE sends PUSCH.

[0561] <Alt 2-1>

[0562] The UE does not send PUSCH.

[0563] <Alt 2-2>

[0564] The UE performs rate matching on the PUSCH in the UL subband.

[0565] In section 6.1.2.1 of TS38.214, it is specified that for PUSCH repetition type B, after invalid symbols for PUSCH repetition type B transmission for each nominal repetition are determined, the remaining symbols are regarded as potentially valid symbols for PUSCH repetition type B transmission. In Proposal 5, for SBFD operation and s-TRP PUSCH repetition type B or m-TRP PUSCH repetition type B in non-SBFD operation, the invalid symbols used for segmentation of PUSCH repetition type B may also include the following symbols of options 0 to 2 together with SSB symbols, type-0 CORESET symbols, and invalid symbols notified by RRC parameter invalidSymbolPattern.

[0566] (Option 0)

[0567] In option 0, for s-TRP PUSCH repetition type B or m-TRP PUSCH repetition type B, the invalid symbols may include semi-static DL symbols regardless of SBFD symbols or non-SBFD symbols.

[0568] (Option 1)

[0569] In option 1, for s-TRP PUSCH repetition type B or m-TRP PUSCH repetition type B, the invalid symbols may also include non-SBFD semi-static DL symbols.

[0570] (Option 2)

[0571] In option 2, for s-TRP PUSCH repetition type B or m-TRP PUSCH repetition type B, invalid codewords may also include non-SBFD semi-static and / or dynamic DL codewords, SBFD semi-static and / or dynamic DL codewords (when PUSCH repetition overlaps with DL subbands in SBFD semi-static and / or dynamic DL codewords), SBFD semi-static and / or dynamic UL codewords (when PUSCH repetition overlaps with DL subbands in SBFD semi-static and / or dynamic DL codewords), and / or SBFD semi-static and / or dynamic FL codewords (when PUSCH repetition overlaps with DL subbands in SBFD semi-static and / or dynamic FL codewords).

[0572] Here, as a variation, which option is applied may also depend on whether the SBFD operation (and / or DL / UL subband allocation) is dynamically notified or set by RRC. For example, in the case where the SBFD operation (DL / UL subband allocation) is dynamically notified, option 1 may also be applied. On the other hand, in the case where the SBFD operation (and / or DL / UL subband allocation) is set by RRC, option 2 may also be applied.

[0573] In section 6.1.2.1 of TS38.214, it is specified that the potentially valid symbols for PUSCH repetition type B transmission are composed of one or more actual repetitions for the case where the nominal repetition is greater than 0. Here, each actual repetition is composed of a continuous set of all potentially valid symbols that can be used for PUSCH repetition type B transmission in the time slot. In Proposal 5, for s-TRP PUSCH repetition type B or m-TRP PUSCH repetition type B in SBFD operation and non-SBFD operation, the UE may not transmit the actual PUSCH repetition when the symbols included in the resources used for the transmission of the actual PUSCH repetition after segmentation overlap with the non-SBFD dynamic FL symbols.

[0574] In the case where segmentation is based on option 1 above, for each actual repetition after segmentation, when the codewords included in the resources used for sending the actual PUSCH repetition overlap with at least one SBFD semi-static / dynamic UL codeword, at least one SBFD semi-static / dynamic DL codeword, and / or at least one SBFD semi-static / dynamic FL codeword, the UE may also operate according to the following Alt 1 or Alt 2.

[0575] (Alt 1)

[0576] In Alt 1, when the invalid codewords used for segmentation include non-SBFD semi-static DL codewords, and the codewords included in the resources used for sending the actual PUSCH repetition overlap with at least one SBFD semi-static / dynamic UL codeword, at least one SBFD semi-static / dynamic DL codeword, and / or at least one SBFD semi-static / dynamic FL codeword, the UE may not send the actual PUSCH repetition regardless of whether there is an overlap with the DL subband.

[0577] (Alt 2)

[0578] In Alt 2, when the invalid codewords used for segmentation include non-SBFD semi-static DL codewords, and the codewords included in the resources used for actual PUSCH repeated transmission overlap with at least one SBFD semi-static / dynamic UL codeword, at least one SBFD semi-static / dynamic DL codeword, and / or at least one SBFD semi-static / dynamic FL codeword, the UE may also operate as follows based on the overlap with the DL subband.

[0579] Specifically, when the codewords included in the resources used for actual PUSCH repetition transmission do not overlap with SBFD semi-static / dynamic UL codewords, SBFD semi-static / dynamic DL codewords, and / or SBFD semi-static / dynamic FL codewords, the UE can also send the PUSCH repetition of this embodiment.

[0580] On the other hand, when the codewords contained in the resources used for actual repeated transmission of PUSCH overlap with SBFD semi-static / dynamic UL codewords, SBFD semi-static / dynamic DL codewords, and / or SBFD semi-static / dynamic FL codewords, the UE can also follow the following Alt 2-1 or Alt 2-2 to control the transmission operation.

[0581] <Alt 2-1>

[0582] In Alt 2-1, when the codeword included in the resources used for sending the actual PUSCH repetition overlaps with the SBFD semi-static / dynamic UL codeword, SBFD semi-static / dynamic DL codeword, and / or SBFD semi-static / dynamic FL codeword, the UE may not send the actual PUSCH repetition.

[0583] <Alt 2-2>

[0584] In Alt 2-2, when the codewords included in the resources used for actual repeated transmission of PUSCH overlap with SBFD semi-static / dynamic UL codewords, SBFD semi-static / dynamic DL codewords, and / or SBFD semi-static / dynamic FL codewords, the UE may also perform rate matching on the codewords included in the resources used for actual repeated transmission of PUSCH on the UL subband in the SBFD semi-static / dynamic UL codewords, SBFD semi-static / dynamic DL codewords, and / or SBFD semi-static / dynamic FL codewords, and / or on non-SBFD semi-static / dynamic UL / FL codewords if any.

[0585] In addition, which of the above Alts to apply can 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 should be applied can also be sent in at least one of RRC, DCI, and MAC CE (Medium Access Control Control Element).

[0586] Here, TBS may also be determined based on the following option A and / or option B.

[0587] (Option A)

[0588] In option A, the TBS may be determined in accordance with the rules of Rel- 16. Specifically, the TBS may be determined based on the notified / set TDRA and FDRA.

[0589] (Option B)

[0590] In option B, the TBS may also be determined by taking into account the actual resource elements (REs) of the actual PUSCH repetition. Here, for each actual repetition, the actual number of REs may also be used as

[0591] Non-SBFD semi-static / dynamic DL symbols (and non-SBFD dynamic FL symbols),

[0592] SBFD semi-static / dynamic UL symbols, SBFD semi-static / dynamic DL symbols, and / or SBFD semi-static / dynamic FL symbols, and / or

[0593] SBFD semi-static / dynamic UL symbols, SBFD semi-static / dynamic DL symbols, and / or DL ​​resource blocks (RBs) in SBFD semi-static / dynamic FL symbols

[0594] Here, for TBS calculation, the maximum value, minimum value, or average value among the actual number of REs may be used.

[0595] Which option to apply may be explicitly or implicitly specified by the specification, semi-statically set by RRC, dynamically notified by DCI, or determined by a rule. For example, a parameter indicating which option should be applied may be sent in at least one of RRC, DCI, and MAC CE. For example, the UE may receive setting information related to option A and option B through RRC, or may be dynamically notified through DCI which option of option A and option B should be applied.

[0596] (Variation of Proposal 4 / 5)

[0597] The combined operation of SBFD operation and m-TRP PUSCH may not be supported.

[0598] <Concrete example 1>

[0599] In specific example 1, the UE may also not assume / judge / decide / interpret that the SBFD operation (and / or DL / UL subband allocation) is notified / set for the serving cell / bandwidth part (BWP), and two SRS resource sets are set in the serving cell / BWP in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2.

[0600] <Concrete example 2>

[0601] In specific example 2, the UE may not assume / judge / decide / interpret that the SBFD operation (and / or DL / UL subband allocation) is notified / set for the serving cell / bandwidth part (BWP), and two SRS resource sets are set in the serving cell / BWP in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2, and pusch-RepTypeIndicatorDCI-0-1 or pusch-RepTypeIndicatorDCI-0-2 is set to pusch-RepTypeA, or is not set.

[0602] <Concrete example 3>

[0603] In specific example 3, the UE may also not assume / judge / decide / interpret that the SBFD operation (and / or DL / UL subband allocation) is notified / set for the serving cell / bandwidth part (BWP), and two SRS resource sets are set in the serving cell / BWP in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2, and pusch-RepTypeIndicatorDCI-0-1 or pusch-RepTypeIndicatorDCI-0-2 is set to pusch-RepTypeB.

[0604] <Concrete example 4>

[0605] In specific example 4, when the SBFD operation (and / or DL / UL subband allocation) is notified / set for the serving cell / bandwidth part (BWP), and two SRS resource sets are set in the serving cell / BWP in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2, the UE only uses the first / second SRS resource set for PUSCH transmission.

[0606] <Concrete example 5>

[0607] In specific example 5, when the SBFD operation (and / or DL / UL subband allocation) is notified / set for the serving cell / bandwidth part (BWP), two SRS resource sets are set in the serving cell / BWP in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2, and pusch-RepTypeIndicatorDCI-0-1 or pusch-RepTypeIndicatorDCI-0-2 is set to pusch-RepTypeA, or is not set, the UE may also use only the first / second SRS resource set for PUSCH transmission.

[0608] <Concrete example 6>

[0609] In specific example 6, when SBFD operation (and / or DL / UL subband allocation) is notified / set for the serving cell / bandwidth part (BWP), two SRS resource sets are set in the serving cell / BWP in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2, and pusch-RepTypeIndicatorDCI-0-1 or pusch-RepTypeIndicatorDCI-0-2 is set to pusch-RepTypeB, the UE may also use only the first / second SRS resource set for PUSCH transmission.

[0610] (UE operation of Proposal 5)

[0611] In Proposal 5, the UE may also control the transmission operation of the uplink data channel according to whether the downlink time unit in non-time-frequency division duplex operation such as non-SBFD operation and / or the time unit in time-frequency division duplex operation such as SBFD operation overlaps with the uplink data channel, and perform the transmission operation of the uplink data channel through the controlled transmission operation. Here, the time-frequency division duplex may also be SBFD, and the downlink time unit in the non-time-frequency division duplex operation may also be a DL symbol, a mini-slot, a time slot, or any other time unit in the non-SBFD operation, specifically, it may also be a non-SBFD semi-static / dynamic DL symbol, and / or a non-SBFD dynamic FL symbol. In addition, the time unit in the time-frequency division duplex operation may also be a UL, DL or FL symbol, a mini-slot, a time slot, or any other time unit in the SBFD operation, specifically, it may also be a SBFD semi-static / dynamic UL symbol, a SBFD semi-static / dynamic DL symbol, and / or a SBFD dynamic FL symbol. Furthermore, the uplink data channel may be, for example, PUSCH, PUSCH repetition, or the like.

[0612] Specifically, the UE may include a non-SBFD downlink time unit or a SBFD time unit as an invalid time unit for repeated transmission of an uplink data channel. In addition, the UE may determine an invalid time unit for repeated transmission of an uplink data channel according to whether the SBFD is dynamically notified or semi-statically set. In addition, the UE may control the actual repeated transmission operation according to whether there is overlap with a downlink subband when a symbol included in a segmented resource for actual repeated transmission of the uplink data channel overlaps with the SBFD time unit.

[0613] (gNB Operation of Proposal 5)

[0614] In Proposal 5, the gNB may also control the reception operation of the uplink data channel in one or both of the downlink time unit in the non-time-frequency division duplex operation such as the non-SBFD operation and the time unit in the time-frequency division duplex operation such as the SBFD operation, and perform the reception operation of the uplink data channel through the controlled reception operation. Here, the time-frequency division duplex may also be SBFD, and the downlink time unit in the non-time-frequency division duplex operation may also be a DL symbol, a mini-slot, a time slot, or any other time unit in the non-SBFD operation, specifically, a non-SBFD semi-static / dynamic DL symbol, and / or a non-SBFD dynamic FL symbol. In addition, the time unit in the time-frequency division duplex operation may also be a UL, DL, or FL symbol, a mini-slot, a time slot, or any other time unit in the SBFD operation, specifically, a SBFD semi-static / dynamic UL symbol, a SBFD semi-static / dynamic DL symbol, and / or a SBFD dynamic FL symbol. In addition, the uplink data channel may also be, for example, a PUSCH, a PUSCH repetition, or the like.

[0615] UE Capability

[0616] For PUSCH enhancement for time-frequency division duplex operation such as the above-mentioned SBFD operation, UE capability information indicating whether the UE supports PUSCH enhancement for time-frequency division duplex operation may also be specified. In addition, UE capability information related to PUSCH transmission of multiple transmit and receive points for time-frequency division duplex such as SBFD operation may also be specified. Specifically, UE capability information indicating whether the UE supports s-TRP / m-TRP PUSCH repetition type B for SBFD operation may also be specified. In the case of supporting PUSCH enhancement for time-frequency division duplex operation, the UE may also send UE capability information indicating support for PUSCH enhancement for time-frequency division duplex operation to the gNB. If the UE capability information is received, the gNB can follow the PUSCH enhancement for time-frequency division duplex operation and receive PUSCH from the UE.

[0617] According to the above-mentioned proposal 5, PUSCH enhancement for time-frequency division duplex operation such as SBFD operation can be achieved.

[0618] (PUCCH in Rel-15 / 16 / 17)

[0619] According to Rel-15 / 16, it is stipulated that non-repeated PUCCH overlapping with semi-static DL symbols shall not be transmitted. That is, it is stipulated that for the symbol set of the time slot notified to the UE as the downlink through tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, if the symbol included in the resources for transmitting PUSCH, PUCCH, PRACH or SRS partially overlaps with the symbol set of the time slot, the UE shall not transmit PUSCH, PUCCH, PRACH or SRS.

[0620] In addition, it is stipulated that the non-repeated PUCCH overlapping with the dynamic DL or FL codeword is not transmitted. That is, it is stipulated that the UE is set by the upper layer to transmit PUSCH, PUCCH, PRACH or SRS in the codeword set of the time slot, and in addition, when the UE detects DCI format 2_0 based on a time slot format value other than 255 for notifying the time slot format as a downlink or flexible with a codeword subset from the codeword set, or when the UE detects a DCI format for notifying the UE to receive PDSCH or CSI-RS in at least one codeword in the codeword set, and when a specific condition is met, the UE cancels the PUSCH, PUCCH, PRACH or SRS transmission in the codeword set.

[0621] In Rel-15 / 16 NR, it is stipulated that the non-repeated PUCCH overlapping with the semi-static DL codeword is postponed to the time slot where the resources of the PUCCH do not overlap with the semi-static DL codeword. Fig.25 As shown, the PUCCH of HARQ-ACK corresponding to PDSCH #1 and #2 overlaps with the DL slot and is therefore postponed to the UL slot.

[0622] In addition, in Rel-15 / 16 NR, it is stipulated that PUCCH overlapping with dynamic DL or FL codewords shall not be transmitted.

[0623] In addition, in Rel-17 NR, the extension of SPS HARQ-ACK based on TDD conflict is supported. Specifically, it is stipulated that when SPS HARQ-ACK overlaps with semi-static DL codewords, SSB codewords, or CORESET#0 codewords, the SPS HARQ-ACK is postponed. The extension of SPS HARQ-ACK can be set to enabled for SPS settings.

[0624] Here, it is stipulated that the target slot / subslot for the extension is set to be the first available slot / subslot that does not overlap with the semi-static DL symbol, SSB symbol or CORESET#0 symbol and satisfies the condition of "K1_max_def>K1+K_def". 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 setting index. For example, Fig.26 As shown, regarding the SPS HARQ-ACK for SPS PDSCH#1, since the corresponding first PUCCH overlaps with the semi-static DL slot, it is postponed to the target PUCCH slot.

[0625] [Study items related to PUCCH enhancement for SBFD operation]

[0626] For SBFD operations in Rel-18, the following contents are studied.

[0627] SBFD operation in DL symbols, i.e. DL and UL subbands in DL symbols

[0628] SBFD operation in UL symbols, i.e. DL and UL subbands in UL symbols

[0629] SBFD operation in flexible (FL) symbols, i.e., DL and UL subbands in FL symbols

[0630] Here, in the case where SBFD operation in DL symbols is supported or enabled, the non-repeated PUCCH overlapping with DL symbols may not necessarily be discarded. Therefore, the rules for TDD collision in Rel-15 / 16 / 17 may need to be updated for SBFD operation. Fig. 27 In the specific example shown, according to the rules of Rel-15 / 16, the non-repeated PUCCH in the time slot shown is discarded and the repetitive PUCCH is postponed. According to the rules of Rel-17, the SPS HARQ-ACK PUCCH in the time slot shown is postponed.

[0631] [Proposal 6]

[0632] In Proposal 6, PUCCH enhancement for time-frequency division duplex operation such as SBFD operation is described. Specifically, the rules for TDD contention of PUCCH for SBFD operation are enhanced as follows.

[0633] Case 1: PUCCH overlaps with non-SBFD DL symbols, SSB or type-0 CORESET

[0634] <Alt-A>

[0635] The UE does not send PUCCH.

[0636] <Alt B>

[0637] The UE postpones the transmission of the PUCCH.

[0638] Case 2: PUCCH overlaps with non-SBFD DL symbols

[0639] The UE does not send PUCCH.

[0640] Case 3: PUCCH and SBFD DL symbols overlap

[0641] <Alt 1>

[0642] The UE operates according to the following Alt 1-1 to 1-2 regardless of the presence or absence of overlap with the DL subband.

[0643] <<Alt 1-1>>

[0644] The UE does not send PUCCH.

[0645] <<Alt 1-2>>

[0646] The UE postpones the transmission of the PUCCH.

[0647] <Alt 2>

[0648] The UE operates according to Alt 2-1 to 2-3 below, depending on whether there is overlap with the DL subband.

[0649] <<Alt 2-1>>

[0650] The UE does not send PUCCH.

[0651] <<Alt 2-2>>

[0652] The UE performs rate matching on the PUCCH in the UL subband.

[0653] <<Alt 2-3>>

[0654] The UE postpones the transmission of PUCCH.

[0655] For s-TRP PUCCH, s-TRP PUCCH repetition or m-TRP PUCCH repetition, the UE may control the PUCCH transmission operation corresponding to the following situations 1 to 3.

[0656] Case 1: A symbol included in a resource for PUCCH or PUCCH repetition transmission overlaps with at least one non-SBFD semi-static DL symbol, SSB symbol, or type-0 CORESET symbol.

[0657] Case 2: Symbols included in resources for PUCCH or PUCCH repetition transmission overlap with at least one non-SBFD dynamic DL / FL symbol.

[0658] Case 3: The codewords included in the resources used for PUCCH or PUCCH repeated transmission do not overlap with any non-SBFD semi-static / dynamic DL codewords (or non-SBFD dynamic FL codewords), but overlap with at least one SBFD semi-static / dynamic UL codeword, at least one SBFD semi-static / dynamic DL codeword, and / or at least one SBFD semi-static / dynamic FL codeword.

[0659] (Scenario 1)

[0660] As in Case 1, when the codewords included in the resources for PUCCH or PUCCH repeated transmission overlap with at least one non-SBFD semi-static DL codeword, SSB codeword or type-0 CORESET (type-0 CORESET) codeword, the UE may also operate according to the following Alt-A or Alt-B.

[0661] <Case 1: Alt-A>

[0662] In Alt-A, when a symbol included in a resource for transmitting a PUCCH or PUCCH repetition overlaps with at least one non-SBFD semi-static DL symbol, SSB symbol, or type-0 CORESET symbol, the UE may not transmit the PUCCH or PUCCH repetition. That is, the UE may not transmit a PUCCH or PUCCH repetition that overlaps with a DL symbol in a non-SBFD operation.

[0663] In addition, as a variation, a PUCCH repetition that is not transmitted due to overlap with at least one non-SBFD semi-static DL symbol, SSB symbol, or type-0 CORESET symbol may be counted as the number of repetitions, or may not be counted.

[0664] <Case 1: Alt-B>

[0665] In Alt-B, when the codewords included in the resources used for sending PUCCH or PUCCH repetitions overlap with at least one non-SBFD semi-static DL codeword, SSB codeword or type-0 CORESET (type-0CORESET) codeword, the UE may also postpone the PUCCH or PUCCH repetitions to a time slot / sub-time slot in which the codewords included in the resources used for sending PUCCH or PUCCH repetitions do not overlap with non-SBFD semi-static DL codewords, SSB codewords or type-0 CORESET (type-0 CORESET) codewords.

[0666] (Scenario 2)

[0667] As in case 2, when the codeword included in the resource for sending PUCCH or PUCCH repetition overlaps with at least one non-SBFD dynamic DL / FL codeword, the UE may not send the PUCCH or PUCCH repetition. That is, the UE may not send the PUCCH or PUCCH repetition that overlaps with the DL / FL codeword in non-SBFD operation.

[0668] In addition, as a variation, a PUCCH repetition that is not transmitted due to overlapping with at least one non-SBFD dynamic DL / FL symbol may be counted as the number of repetitions, or may not be counted.

[0669] (Scenario 3)

[0670] As in Case 3, when the codewords included in the resources for PUCCH or PUCCH repeated transmission do not overlap with any non-SBFD semi-static / dynamic DL codeword (or non-SBFD dynamic FL codeword), but overlap with at least one SBFD semi-static / dynamic UL codeword, at least one SBFD semi-static / dynamic DL codeword, and / or at least one SBFD semi-static / dynamic FL codeword, the UE may also operate according to the following Alt 1 and / or Alt 2.

[0671] <Case 3: Alt 1>

[0672] In Alt 1, when the codewords included in the resources used for PUCCH or PUCCH repeated transmission do not overlap with any non-SBFD semi-static / dynamic DL codewords (or non-SBFD dynamic FL codewords), but overlap with at least one SBFD semi-static / dynamic UL codeword, at least one SBFD semi-static / dynamic DL codeword, and / or at least one SBFD semi-static / dynamic FL codeword, the UE may also operate in accordance with the following Alt 1-1 and / or Alt 1-2 regardless of whether there is overlap with the DL subband.

[0673] <<Scenario 3: Alt 1-1>>

[0674] In Alt 1-1, when a symbol included in a resource for transmitting a PUCCH or PUCCH repetition does not overlap with any non-SBFD semi-static / dynamic DL symbol (or non-SBFD dynamic FL symbol), but overlaps with at least one SBFD semi-static / dynamic UL symbol, at least one SBFD semi-static / dynamic DL symbol, and / or at least one SBFD semi-static / dynamic FL symbol, the UE may not transmit the PUCCH or PUCCH repetition. That is, the UE may not transmit the PUCCH or PUCCH repetition that overlaps with a UL / DL / FL symbol in SBFD operation.

[0675] In addition, as a variation, PUCCH repetitions that are not transmitted due to overlap with SBFD semi-static / dynamic UL symbols, SBFD semi-static / dynamic DL symbols, and / or SBFD semi-static / dynamic FL symbols may be counted as the number of repetitions, or may not be counted.

[0676] <<Scenario 3: Alt 1-2>>

[0677] In Alt 1-2, when the codewords included in the resources used for sending PUCCH or PUCCH repetition do not overlap with any non-SBFD semi-static / dynamic DL codewords (or non-SBFD dynamic FL codewords), but overlap with at least one SBFD semi-static / dynamic UL codeword, at least one SBFD semi-static / dynamic DL codeword, and / or at least one SBFD semi-static / dynamic FL codeword, the UE may also postpone the PUCCH or PUCCH repetition to a time slot / sub-time slot in which the codewords included in the resources used for sending the PUCCH or PUCCH repetition resources do not overlap with non-SBFD semi-static DL codewords (or non-SBFD dynamic FL codewords), and do not overlap with SBFD semi-static / dynamic UL codewords, SBFD semi-static / dynamic DL codewords, and / or SBFD semi-static / dynamic FL codewords.

[0678] In addition, such a deferral may also be set as a condition that requires additional addition. For example, the deferral may also be performed when the SBFD operation indication is set through RRC. In other words, when the SBFD operation is dynamically notified to the UE, the deferral may not be applied. That is, when the SBFD operation is dynamically notified to the UE, the UE may not send PUCCH or PUCCH repetitions. For example, when the SBFD operation is notified to the UE through DCI, the UE may not send PUCCH or PUCCH repetitions that do not overlap with any non-SBFD DL / FL codewords but overlap with SBFD UL codewords, SBFD DL codewords, and / or SBFD FL codewords in subsequent codewords, time slots, etc.

[0679] <Case 3: Alt 2>

[0680] In Alt 2, when the codewords included in the resources used for PUCCH or PUCCH repeated transmission do not overlap with any non-SBFD semi-static / dynamic DL codewords (or non-SBFD dynamic FL codewords), but overlap with at least one SBFD semi-static / dynamic UL codeword, at least one SBFD semi-static / dynamic DL codeword, and / or at least one SBFD semi-static / dynamic FL codeword, the UE may also control the PUCCH or PUCCH repeated transmission operation according to whether there is overlap with the DL subband.

[0681] Specifically, when the codeword included in the resources for sending PUCCH or PUCCH repetition does not overlap with any non-SBFD semi-static / dynamic DL codeword (or non-SBFD dynamic FL codeword), but overlaps with at least one SBFD semi-static / dynamic UL codeword, at least one SBFD semi-static / dynamic DL codeword, and / or at least one SBFD semi-static / dynamic FL codeword, and when the codeword included in the resources for sending PUCCH or PUCCH repetition does not overlap with the DL subband in the SBFD semi-static / dynamic UL codeword, the SBFD semi-static / dynamic DL codeword, and / or the SBFD dynamic FL codeword, the UE may also send the PUCCH or PUCCH repetition in the notified or set resources. In addition, the resource may also be specified by the specification, or semi-statically set by RRC setting, etc., or dynamically notified by DCI notification, etc., or determined in accordance with the rule. In addition, the resource may also be explicitly or implicitly specified, set, notified or determined.

[0682] On the other hand, when the codewords included in the resources for repeated transmission of PUCCH or PUCCH do not overlap with any non-SBFD semi-static / dynamic DL codeword (or non-SBFD dynamic FL codeword), but overlap with at least one SBFD semi-static / dynamic UL codeword, at least one SBFD semi-static / dynamic DL codeword, and / or at least one SBFD semi-static / dynamic FL codeword, and when the codewords included in the resources for repeated transmission of PUCCH or PUCCH overlap with the DL subband in the SBFD semi-static / dynamic UL codeword, the SBFD semi-static / dynamic DL codeword, and / or the SBFD dynamic FL codeword, the UE may also operate in accordance with the following Alt 2-1, Alt 2-2, and / or Alt 2-3.

[0683] <<Scenario 3: Alt 2-1>>

[0684] In Alt 2-1, the UE may not send the PUCCH or PUCCH repetition if the codewords included in the resources used for sending the PUCCH or PUCCH repetition do not overlap with any non-SBFD semi-static / dynamic DL codeword (or non-SBFD dynamic FL codeword), but overlap with at least one SBFD semi-static / dynamic UL codeword, at least one SBFD semi-static / dynamic DL codeword, and / or at least one SBFD semi-static / dynamic FL codeword, and if the codewords included in the resources used for sending the PUCCH or PUCCH repetition overlap with the DL subband in the SBFD semi-static / dynamic UL codeword, the SBFD semi-static / dynamic DL codeword, and / or the SBFD dynamic FL codeword.

[0685] In addition, as a variation, PUCCH repetitions that are not sent due to overlap with DL subbands in SBFD semi-static / dynamic UL symbols, SBFD semi-static / dynamic DL symbols, and / or SBFD dynamic FL symbols may be counted as the number of repetitions, or may not be counted.

[0686] <<Alt 2-2>>

[0687] In Alt 2-2, when the codewords included in the resources for repeatedly sending the PUCCH or PUCCH do not overlap with any non-SBFD semi-static / dynamic DL codewords (or non-SBFD dynamic FL codewords), but overlap with at least one SBFD semi-static / dynamic UL codeword, at least one SBFD semi-static / dynamic DL codeword, and / or at least one SBFD semi-static / dynamic FL codeword, and when the codewords included in the resources for repeatedly sending the PUCCH or PUCCH overlap with DL subbands in SBFD semi-static / dynamic UL codewords, SBFD semi-static / dynamic DL codewords, and / or SBFD dynamic FL codewords, the UE may also rate match the codewords included in the resources for repeatedly sending the PUCCH or PUCCH on the DL subbands in SBFD semi-static / dynamic UL codewords, SBFD semi-static / dynamic DL codewords, and / or SBFD dynamic FL codewords, and on non-SBFD semi-static / dynamic DL / FL codewords if any.

[0688] <<Alt 2-3>>

[0689] In Alt In 2-3, when the codewords included in the resources used for repeatedly sending the PUCCH or PUCCH do not overlap with any non-SBFD semi-static / dynamic DL codewords (or non-SBFD dynamic FL codewords), but overlap with at least one SBFD semi-static / dynamic UL codeword, at least one SBFD semi-static / dynamic DL codeword, and / or at least one SBFD semi-static / dynamic FL codeword, and when the codewords included in the resources used for repeatedly sending the PUCCH or PUCCH overlap with the DL subbands of the SBFD semi-static / dynamic UL codewords, SBFD semi-static / dynamic DL codewords, and / or SBFD dynamic FL codewords, the UE may also postpone the PUCCH or PUCCH repetition to a time slot / sub-time slot in which the codewords included in the resources used for repeatedly sending the PUCCH or PUCCH do not overlap with non-SBFD semi-static / dynamic UL codewords (or non-SBFD dynamic flexible codewords), and do not overlap with the DL subbands of any SBFD semi-static / dynamic UL codewords, SBFD semi-static / dynamic DL codewords, and / or SBFD dynamic FL codewords. That is, the UE may also transmit the PUCCH or PUCCH repetition in any subsequent time slot / subslot that does not overlap with UL symbols or FL symbols in non-SBFD operation, and in addition, does not overlap with DL subbands in UL symbols, DL symbols, and / or FL symbols in SBFD operation. Alternatively, the UE may also transmit the PUCCH or PUCCH repetition in any subsequent time unit such as a symbol, subslot, subframe, frame, etc. that does not overlap with non-SBFD semi-static / dynamic UL symbols (or non-SBFD dynamic flexible symbols) and does not overlap with the DL subbands of any of SBFD semi-static / dynamic UL symbols, SBFD semi-static / dynamic DL symbols, and / or SBFD dynamic FL symbols.

[0690] In addition, which of the above Alts to apply can 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 should be applied can also be sent in at least one of RRC, DCI, and MAC CE (Medium Access Control Control Element).

[0691] Here, the above-mentioned Alt 2-1 to 2-3 can also be selected based on the indication method of SBFD operation (and / or DL / UL subband allocation). For example, when the SBFD operation (and / or DL / UL subband allocation) is set through RRC, Alt 2-2 or Alt 2-3 can also be applied. When the SBFD operation (and / or DL / UL subband allocation) is dynamically notified through DCI, Alt 2-1 can also be applied. In addition, the selection can also be specified by the specification, or semi-statically set through RRC settings, or dynamically notified through DCI notifications, or determined in accordance with rules. In addition, the selection can also be explicitly or implicitly specified, set, notified or determined.

[0692] (UE operation of Proposal 6)

[0693] In Proposal 6, the UE may also control the transmission operation of the uplink control channel according to whether the downlink time unit in non-time-frequency division duplex operation such as non-SBFD operation and / or the time unit in time-frequency division duplex operation such as SBFD operation overlaps with the uplink control channel, and perform the transmission operation of the uplink control channel through the controlled transmission operation. Here, the time-frequency division duplex may also be SBFD, and the downlink time unit in the non-time-frequency division duplex operation may also be a DL symbol, a sub-slot, a time slot, or any other time unit in the non-SBFD operation, specifically, it may also be a non-SBFD semi-static / dynamic DL symbol, and / or a non-SBFD dynamic FL symbol. In addition, the time unit in the time-frequency division duplex operation may also be a UL, DL or FL symbol, a sub-slot, a time slot, or any other time unit in the SBFD operation, specifically, it may also be a SBFD semi-static / dynamic UL symbol, a SBFD semi-static / dynamic DL symbol, and / or a SBFD semi-static / dynamic FL symbol. Furthermore, the uplink control channel may be, for example, PUCCH, PUCCH repetition, or the like.

[0694] Specifically, when the uplink control channel overlaps with the downlink time unit or flexible time unit in non-SBFD operation, the UE may not send the uplink control channel. Alternatively, or further, when the uplink control channel overlaps with the downlink time unit or flexible time unit in non-SBFD operation, the UE may send the uplink control channel in a time unit in which the uplink control channel does not overlap with the downlink time unit in non-SBFD operation. That is, the UE may also postpone the transmission of the PUCCH or PUCCH repetition to a time slot in which the symbol included in the time domain resource for the transmission of the PUCCH or PUCCH repetition does not overlap with the non-SBFD semi-static / dynamic DL symbol.

[0695] In addition, when the uplink control channel overlaps with the time unit in the SBFD operation, the UE may also 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. For example, the UE may not transmit the uplink control channel. Alternatively / furthermore, the UE may also transmit the uplink control channel in a time unit in which the uplink control channel does not overlap with the downlink time unit or flexible time unit in the non-SBFD operation, and does not overlap with the uplink time unit, downlink time unit, and / or flexible time unit in the SBFD operation. That is, the UE may also postpone the repeated transmission of the PUCCH or PUCCH to a time slot in which the codewords included in the resources used for the repeated transmission of the PUCCH or PUCCH do not overlap with the non-SBFD semi-static / dynamic DL codewords, and do not overlap with the SBFD semi-static / dynamic UL codewords, SBFD semi-static / dynamic DL codewords, and / or SBFD dynamic FL codewords. Alternatively or further, the UE may also repeatedly rate match the uplink control channel to the PUCCH or PUCCH in a time unit other than the time unit in the SBFD operation. That is, the UE may also repeatedly rate match the PUCCH or PUCCH on symbols other than SBFD semi-static / dynamic UL symbols, SBFD semi-static / dynamic DL symbols, and / or SBFD dynamic FL symbols.

[0696] In addition, when the uplink control channel overlaps with the time unit in the SBFD operation, the UE may also control the transmission operation of the uplink control channel according to whether the uplink control channel overlaps with the downlink subband in the time unit. For example, when the uplink control channel does not overlap with the downlink subband in the time unit, the UE may also send the uplink control channel on the set / notified resource. On the other hand, when the uplink control channel overlaps with the downlink subband in the time unit, the UE may not send the uplink control channel. Alternatively / furthermore, the UE may also rate match the uplink control channel on the UL subband in the time unit in the SBFD operation. Alternatively / furthermore, the UE may also send the uplink control channel in a time unit in which the uplink control channel does not overlap with the downlink time unit or flexible time unit in the non-SBFD operation and does not overlap with the uplink time unit, downlink time unit, and / or flexible time unit in the SBFD operation. That is, the UE may also postpone the transmission of PUCCH or PUCCH repetitions to a time slot or sub-time slot in which the resources of PUSCH or PUSCH repetitions do not overlap with non-SBFD semi-static / dynamic DL codewords and do not overlap with SBFD semi-static / dynamic UL codewords, SBFD semi-static / dynamic DL codewords, and / or SBFD dynamic FL codewords.

[0697] (gNB Operation of Proposal 6)

[0698] In Proposal 6, the gNB may also control the reception operation of the uplink control channel in one or both of the downlink time unit in non-time-frequency division duplex operation such as non-SBFD operation and the time unit in time-frequency division duplex operation such as SBFD operation, and perform the reception operation of the uplink control channel through the controlled reception operation. Here, the time-frequency division duplex may also be SBFD, and the downlink time unit in the non-time-frequency division duplex operation may also be a DL symbol, a mini-slot, a time slot, or any other time unit in the non-SBFD operation, specifically, a non-SBFD semi-static / dynamic DL symbol, and / or a non-SBFD dynamic FL symbol. In addition, the time unit in the time-frequency division duplex operation may also be a UL, DL, or FL symbol, a mini-slot, a time slot, or any other time unit in the SBFD operation, specifically, a SBFD semi-static / dynamic UL symbol, a SBFD semi-static / dynamic DL symbol, and / or a SBFD dynamic FL symbol. In addition, the uplink control channel may also be, for example, a PUCCH, a PUCCH repetition, or the like.

[0699] UE Capability

[0700] For PUCCH enhancement for time-frequency division duplex operation such as the above-mentioned SBFD operation, UE capability information indicating whether the UE supports PUCCH enhancement for time-frequency division duplex operation may also be specified. In addition, UE capability information related to PUCCH transmission for time-frequency division duplex operation such as SBFD operation may also be specified. Specifically, UE capability information indicating whether the UE supports s-TRP / m-TRP PUCCH repetition for SBFD operation may also be specified. In the case of supporting PUCCH enhancement for time-frequency division duplex operation, the UE may also send UE capability information indicating support for PUCCH enhancement for time-frequency division duplex operation to the gNB. If the UE capability information is received, the gNB can follow the PUCCH enhancement for time-frequency division duplex operation and receive PUCCH from the UE.

[0701] According to the above-mentioned proposal 6, PUCCH enhancement for time-frequency division duplex operation such as SBFD operation can be achieved.

[0702] [Proposal 7]

[0703] In Proposal 7, an SPS HARQ-ACK deferred operation enhanced for a time-frequency division duplex operation such as a SBFD operation is described. Specifically, the SPS HARQ-ACK deferred operation is enhanced for a SBFD operation as follows.

[0704] SPS HARQ-ACK is deferred according to the following conditions.

[0705] <Alt 1>

[0706] PUCCH overlaps with semi-static DL symbols, SSB symbols, or type-0 CORESET symbols regardless of SBFD operation and non-SBFD operation

[0707] <Alt 2>

[0708] PUCCH overlaps with non-SBFD semi-static DL symbols, SSB symbols, or type-0 CORESET symbols

[0709] <Alt 3>

[0710] PUCCH overlaps with SBFD symbols based on Alt 2

[0711] <Alt 4>

[0712] PUCCH overlaps with DL subband based on Alt 2

[0713] The deferred PUCCH resource is transmitted in the following first available time slot.

[0714] <Alt 1>

[0715] PUCCH is a resource that does not overlap with semi-static DL symbols, SSB symbols, or type-0 CORESET symbols, regardless of SBFD operation and non-SBFD operation.

[0716] <Alt 2>

[0717] Resources that do not overlap with PUCCH and non-SBFD semi-static DL symbols, SSB symbols, or type-0 CORESET symbols

[0718] <Alt 3>

[0719] PUCCH is based on Alt 2 and does not overlap with SBFD symbols.

[0720] <Alt 4>

[0721] PUCCH is based on Alt 2 and does not overlap with DL subband resources

[0722] The SPS HARQ-ACK deferred operation in the SBFD operation and the non-SBFD operation is specified. When the SPS HARQ-ACK deferred processing is enabled for the SPS configuration, the UE may deferred the HARQ-ACK of the SPS configuration if the following deferred conditions Alt1 to 4 are satisfied.

[0723] (Alt 1)

[0724] In Alt 1, when the codewords included in the resources used for sending the PUCCH of SPS HARQ-ACK overlap with at least one semi-static DL codeword, SSB codeword or type-0 CORESET (type-0CORESET) codeword, regardless of SBFD operation or non-SBFD operation, the UE may also postpone the HARQ-ACK set by SPS.

[0725] (Alt 2)

[0726] In Alt 2, when the codewords included in the resources used for sending the PUCCH of SPS HARQ-ACK overlap with at least one non-SBFD semi-static DL codeword, SSB codeword or type-0 CORESET (type-0 CORESET) codeword, the UE may also postpone the HARQ-ACK set by SPS.

[0727] (Alt 3)

[0728] In Alt 3, when the codewords included in the resources used for sending the PUCCH of SPS HARQ-ACK overlap with at least one non-SBFD semi-static DL codeword, SSB codeword, type-0 CORESET codeword, SBFD semi-static / dynamic UL codeword, SBFD semi-static / dynamic DL codeword, and / or SBFD dynamic FL codeword, the UE may also postpone the HARQ-ACK set by SPS.

[0729] (Alt 4)

[0730] In Alt 4, when the codewords included in the resources used for sending the PUCCH of SPS HARQ-ACK overlap with at least one non-SBFD semi-static DL codeword, SSB codeword, or type-0 CORESET (type-0 CORESET) codeword, or overlap with the DL subband in the SBFD semi-static / dynamic UL codeword, SBFD semi-static / dynamic DL codeword, and / or SBFD dynamic FL codeword, the UE may also postpone the HARQ-ACK set by SPS.

[0731] Here, Alt 1 to 4 mentioned above may also be selected based on the indication method of SBFD operation (and / or DL / UL subband allocation). For example, when SBFD operation (and / or DL / UL subband allocation) is set through RRC, Alt 2 or Alt 3 may also be applied. When SBFD operation (and / or DL / UL subband allocation) is dynamically notified through DCI, Alt 1 may also be applied. In addition, the selection may also be specified by a specification, or semi-statically set through RRC settings, or dynamically notified through DCI notifications, or determined in accordance with rules. In addition, the selection may also be specified, set, notified or determined explicitly or implicitly.

[0732] In this way, when the HARQ-ACK configured by SPS is deferred, the UE may determine the first available slot / subslot as the target slot / subslot for deferred destination. Here, the first available slot / subslot may be the following PUCCH resources Alt 1 to 4.

[0733] (Alt 1)

[0734] In Alt 1, the UE may also postpone the HARQ-ACK set by the SPS to the initially available time slot / sub-time slot that does not overlap with the PUCCH of the SPS HARQ-ACK as follows, wherein the PUCCH of the SPS HARQ-ACK is a PUCCH of the SPS HARQ-ACK in which the codewords included in the PUCCH resources overlap with at least one semi-static DL codeword, SSB codeword or type-0 CORESET codeword, regardless of SBFD operation or non-SBFD operation.

[0735] (Alt 2)

[0736] In Alt 2, the UE may also postpone the HARQ-ACK set by the SPS to the initially available time slot / sub-time slot that does not overlap with the PUCCH of the SPS HARQ-ACK as follows, wherein the PUCCH of the SPS HARQ-ACK is an SPS HARQ-ACK in which the codewords included in the PUCCH resources overlap with at least one non-SBFD semi-static DL codeword, SSB codeword, or type-0 CORESET (type-0CORESET) codeword.

[0737] (Alt 3)

[0738] In Alt 3, the UE may also postpone the HARQ-ACK set by the SPS to the initially available time slot / sub-time slot that does not overlap with the PUCCH of the SPS HARQ-ACK as follows, wherein the PUCCH of the SPS HARQ-ACK is the PUCCH of the SPS HARQ-ACK in which the codewords included in the PUCCH resources overlap with at least one non-SBFD semi-static DL codeword, SSB codeword, type-0 CORESET (type-0CORESET) codeword, SBFD semi-static / dynamic UL codeword, SBFD semi-static / dynamic DL codeword, and / or SBFD dynamic FL codeword.

[0739] (Alt 4)

[0740] In Alt 4, the UE may also postpone the HARQ-ACK set by the SPS to the initially available time slot / sub-time slot that does not overlap with the PUCCH of the SPS HARQ-ACK as follows, wherein the PUCCH of the SPS HARQ-ACK is a PUCCH of the SPS HARQ-ACK in which the codewords included in the PUCCH resources overlap with at least one non-SBFD semi-static DL codeword, SSB codeword, or type-0 CORESET (type-0CORESET) codeword, or overlap with the DL subband in the SBFD semi-static / dynamic UL codeword, SBFD semi-static / dynamic DL codeword, and / or SBFD dynamic FL codeword.

[0741] As a variation, the combined operation of the SPS HARQ-ACK deferred operation and the SBFD operation may not be supported. For example, the UE may not assume / judge / determine / interpret that the SPS HARQ-ACK deferred operation is set to enabled for the SPS setting on the serving cell / bandwidth part (BWP), while the SBFD operation (and / or DL / UL subband allocation) is set / notified / enabled on the serving cell / BWP.

[0742] In addition, as a variation, when SBFD operation (and / or DL / UL subband allocation) is set / notified / enabled on the serving cell / BWP, and when the SPS HARQ-ACK deferral operation is set to enabled for the SPS setting on the serving cell / BWP, the UE may not perform the SPS HARQ-ACK deferral operation.

[0743] In addition, which of the above Alts to apply can 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 should be applied can also be sent in at least one of RRC, DCI, and MAC CE (Medium Access Control Control Element).

[0744] (UE operation of Proposal 7)

[0745] In Proposal 7, the UE may also enable the HARQ-ACK deferral operation when the HARQ-ACK deferral condition in the SBFD operation or the non-SBFD operation is satisfied, and defer the transmission of the uplink control channel of the HARQ-ACK according to the deferral operation. Here, the HARQ-ACK may also be SPSHARQ-ACK, and the uplink control channel may also be PUCCH.

[0746] Specifically, the UE may also enable the deferred operation of HARQ-ACK when the SPS HARQ-ACK overlaps with the semi-static downlink time unit, the SSB time unit, or the type-0 CORESET time unit, regardless of the SBFD operation and the non-SBFD operation. In addition, the UE may also enable the deferred operation of HARQ-ACK when the SPS HARQ-ACK overlaps with the non-SBFD semi-static downlink time unit, the synchronization signal block (SSB) time unit, or the type-0 CORESET (Control ResourceSet) time unit. In addition, the UE may also enable the deferred operation of HARQ-ACK when the SPS HARQ-ACK overlaps with the non-SBFD semi-static downlink time unit, the SSB time unit, or the type-0 CORESET (type-0 CORESET) time unit, or when it overlaps with the SBFD semi-static / dynamic time unit. In addition, the UE may also enable deferred operation of HARQ-ACK when 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 overlaps with a downlink subband in a SBFD semi-static / dynamic time unit.

[0747] (gNB Operation of Proposal 7)

[0748] In Proposal 7, the gNB may also transmit a downlink data channel and receive an uplink control channel of HARQ-ACK deferred in accordance with the deferred operation set to enabled when the deferred condition of HARQ-ACK in the time-frequency division duplex operation such as SBFD operation and the non-time-frequency division duplex operation such as non-SBFD operation for the downlink data channel is satisfied. Here, the HARQ-ACK may also be an SPS HARQ-ACK, and the uplink control channel may also be a PUCCH.

[0749] UE Capability

[0750] For the SPS HARQ-ACK enhancement for the time-frequency division duplex operation such as the above-mentioned SBFD operation, UE capability information indicating whether the UE supports the SPS HARQ-ACK enhancement for the time-frequency division duplex operation may also be specified. In addition, UE capability information related to the SPS HARQ-ACK transmission for the time-frequency division duplex operation such as the SBFD operation may also be specified. Specifically, UE capability information indicating whether the UE supports the SPS HARQ-ACK extension operation for the SBFD operation may also be specified. In the case of supporting the SPS HARQ-ACK enhancement for the time-frequency division duplex operation, the UE may also send UE capability information indicating support for the SPS HARQ-ACK enhancement for the time-frequency division duplex operation to the gNB. If the UE capability information is received, the gNB can follow the SPS HARQ-ACK enhancement for the time-frequency division duplex operation and receive the SPS HARQ-ACK from the UE.

[0751] According to the above-mentioned Proposal 7, SPS HARQ-ACK enhancement for time-frequency division duplex operation such as SBFD operation can be achieved.

[0752] (DCI 2_1)

[0753] In section 11.2 of TS38.213, it is specified that the set of physical resource blocks (PRBs) is equal to the activated DL BWP, including B INT PRBs. It is specified that when the UE detects DCI format 2_1 in PDCCH reception in a certain time slot, the symbol set becomes the last one before the first symbol of PDCCH reception in the time slot [Mathematical formula 5]

[0754]

[0755] Here, T INT is the PDCCH monitoring period provided by the value of monitoringSlotPeriodicityAndOffset, N symbslot is the number of symbols per time slot, μ is the SCS setting of the serving cell based on the mapping to each field in DCI format 2_1, and μ INT It is the SCS setting of the DL BWP when the UE receives the PDCCH based on DCI format 2_1. It specifies that when the UE is provided with tdd-UL-DL-ConfigurationCommon, the last [Math 6] before the first symbol received from the PDCCH in the time slot as the uplink symbol notified by tdd-UL-DL-ConfigurationCommon is

[0756]

[0757] In addition, it is specified that the resulting set of symbols includes N INT Multiple code elements.

[0758] In addition, it is specified that when the value of timeFrequencySet is set0, the 14 bits of the MSB from the field in DCI format 2_1 have a one-to-one mapping with 14 groups of consecutive symbols from the symbol set. Here, the original [Equation 7]

[0759] The code element groups include

[0760] [Mathematical formula 8]

[0761] The code element, the final [Mathematical formula 9]

[0762] The code element groups include

[0763] [Formula 10]

[0764]

[0765] Here, a bit value of 0 indicates that the corresponding symbol group is sent to the UE, and a bit value of 1 indicates that the corresponding symbol group does not contain any transmission to the UE.

[0766] On the other hand, it is specified that when the value of timeFrequencySet is set1, the seven bit pairs of the MSBs from the field in DCI format 2_1 have a one-to-one mapping with 7 groups of consecutive symbols. Here, the original [Math 11]

[0767] The code element groups include

[0768] [Mathematical formula 12]

[0769]

[0770] code elements, the final [Formula 13]

[0771] The code element groups include

[0772] [Formula 14]

[0773]

[0774] In addition, the first bit in the bit pair of the symbol group can be applied to the INT The initial [Formula 15] of the set of PRBs

[0775]

[0776] The second bit in the bit pair of the symbol group can be applied to the subset of PRBs from B INT The final [Formula 16] of the set of PRBs is

[0777]

[0778] Here, a bit value of 0 indicates that the corresponding symbol group and the subset of PRBs are transmitted to the UE, and a bit value of 1 indicates that the corresponding symbol group and the subset of PRBs are not transmitted to the UE. For example, Fig.28 The case where the value of timeFrequencySet is set0 and the case where the value of timeFrequencySet is set1 are shown.

[0779] [Study items related to preemption for SBFD operations]

[0780] For the time domain, if the SBFD operation in the UL symbol is considered, that is, the DL and UL subbands in the UL symbol, there may be DL transmission in the UL symbol. Therefore, it may not be appropriate to exclude the UL symbol from the symbol indicated by DCI 2_1. For example, Fig.29 As shown, in the SBFD operation, a DL subband may exist in a UL symbol configured by tdd-UL-DL-ConfigurationCommon.

[0781] On the other hand, for the frequency domain, if SFBD operation in DL or UL symbols is considered, the number of DL resource blocks (RBs) in different symbols may be different. For example, when the value of timeFrequencySet is set1, it is believed that a higher granularity of frequency domain indication can be achieved when the actual DL subband size is considered for the symbol group of the SBFD symbol set based on the narrowband DL subband.

[0782] [Proposal 8]

[0783] Proposal 8 describes enhancement of preemption in the time domain and frequency domain for time-frequency division duplex operations such as SBFD operations. Specifically, preemption in the time direction and preemption in the frequency direction are enhanced as follows.

[0784] N enhanced in the time direction INT Calculated

[0785] Case 1: When a DL subband is set in a resource set as UL in TDD mode

[0786] <Alt 1>

[0787] Contains resources set as UL in TDD mode.

[0788] <Alt 2>

[0789] Included are resources that are set to UL in TDD mode and are set to SBFD operation.

[0790] Case 2: When the UL subband is not configured in the resources configured as DL in TDD mode

[0791] <Alt 1>

[0792] Contains resources set as UL in TDD mode.

[0793] <Alt 2>

[0794] Code elements are not excluded.

[0795] <Alt 3>

[0796] Included are resources that are configured as UL in TDD mode and are not used for SBFD operation.

[0797] Case 3: In the case where SBFD operation is not supported in UL symbols, resources configured as UL in TDD mode are included.

[0798] Frequency-dependent enhancement

[0799] <Alt 1>

[0800] The frequency resources including the UL subband are equally divided for two bit pairs.

[0801] <Alt 2>

[0802] The frequency resources excluding the UL subband are divided into two DL subbands for two bit pairs.

[0803] Throughout this specification, the so-called SBFD operation in a UL symbol may refer to a DL subband in a UL symbol indicated as an uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, and the so-called SBFD operation in a DL symbol may refer to a UL subband in a DL symbol indicated as a downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

[0804] (Time Domain Preemption)

[0805] In order to obtain N INT symbols, the last [Math 17] before the first symbol received from the PDCCH in the time slot

[0806]

[0807] The deleted symbols among the symbols may be symbols corresponding to the following cases 1 to 3.

[0808] Case 1: SBFD operation in UL symbols is supported / enabled, and SBFD operation (or DL / UL subband allocation) is notified / configured through cell-specific / group-common signaling (eg, cell-specific / group-common RRC configuration or DCI).

[0809] Case 2: SBFD operation in UL symbols is supported / enabled, and SBFD operation (or DL / UL subband allocation) is notified / configured through UE-specific signaling (eg, UE-specific RRC configuration or UE-specific DCI).

[0810] Case 3: SBFD operation in UL symbols is not supported / enabled.

[0811] <Scenario 1>

[0812] In case 1, when SBFD operation in UL symbols is supported / enabled and SBFD operation (or DL / UL subband allocation) is notified / configured via cell-specific / group-common signaling (e.g., cell-specific / group-common RRC configuration or DCI), in order to obtain NINT The codewords deleted due to the presence of codewords may also be codewords based on the following Alt 1 and / or Alt 2.

[0813] <<Case 1: Alt 1>>

[0814] In Alt 1, when SBFD operation in UL symbols is supported / enabled and SBFD operation (or DL / UL subband allocation) is notified / configured via cell-specific / group-common signaling, in order to obtain N INT The symbols deleted by using tdd-UL-DL-ConfigurationCommon may include the symbols indicated as uplink. Alt 1 is the same as Rel-15.

[0815] <<Case 1: Alt 2>>

[0816] In Alt 2, when SBFD operation in UL symbols is supported / enabled and SBFD operation (or DL / UL subband allocation) is notified / configured via cell-specific / group-common signaling, in order to obtain N INT The symbols deleted due to the use of DCI 2_1 may also include symbols indicated as uplink by tdd-UL-DL-ConfigurationCommon but not configured / notified for SBFD operation. The SBFD UL symbol includes a DL subband, so DL transmission can be performed on the UL symbol. Therefore, the preemption indication based on DCI 2_1 can be applied to this UL symbol.

[0817] <Scenario 2>

[0818] In case 2, when SBFD operation in UL symbols is supported / enabled and SBFD operation (or DL / UL subband allocation) is notified / configured via UE-specific signaling, in order to obtain N INT The codewords deleted due to the presence of codewords may also be codewords based on the following Alt 1, Alt 2 and / or Alt 3.

[0819] <<Case 2: Alt 1>>

[0820] In Alt 1, when SBFD operation in UL symbols is supported / enabled and SBFD operation (or DL / UL subband allocation) is notified / configured via UE-specific signaling, in order to obtain N INT The symbols deleted by using tdd-UL-DL-ConfigurationCommon may include the symbols indicated as uplink. Alt 1 is the same as Rel-15.

[0821] <<Case 2: Alt 2>>

[0822] In Alt 2, if SBFD operation in UL symbols is supported / enabled and SBFD operation (or DL / UL subband allocation) is notified / set via UE-specific signaling, no symbols may be deleted. In case 2, a specific UE is not sure whether a UL symbol has a DL subband for other UEs in the cell. Therefore, UL symbols may not be deleted for DCI 2_1 indication.

[0823] <<Case 2: Alt 3>>

[0824] In Alt 3, in order to obtain N, if SBFD operation in UL symbols is supported / enabled and SBFD operation (or DL / UL subband allocation) is notified / configured via UE-specific signaling, INT The symbols deleted for DCI 2_1 indication may also include symbols indicated as uplink by tdd-UL-DL-ConfigurationCommon and, if present, guaranteed for non-SBFD operation as specified by the specification or RRC setting. For example, PRACH symbols / time slots can be guaranteed for non-SBFD operation. If the UE can know based on the analysis of Alt 1 that a specific UL symbol (e.g., PRACH symbol) is not available for SBFD operation specified by the specification or set by RRC, the UL symbol may also be deleted for DCI 2_1 indication.

[0825] <Scenario 3>

[0826] In case 3, when SBFD operation in UL symbols is not supported / enabled, in order to obtain N INT The symbols deleted by using tdd-UL-DL-ConfigurationCommon may include the symbols indicated as uplink. This is the same as Rel-15.

[0827] (Frequency domain seizure)

[0828] When the value of timeFrequencySet is set1, resource blocks (RBs) applicable to each bit pair of the symbol group may be determined according to the following Alt 1 and / or Alt 2.

[0829] <Alt 1>

[0830] In Alt 1, when the value of timeFrequencySet is set1, the RB applicable to each bit pair of the symbol group may be determined by the RB from B, regardless of the SBFD symbol in the symbol group, in the same manner as the rule of Rel-15. INT The initial [Formula 18] of the set of PRBs

[0831]

[0832] The first bit corresponding to the subset of PRBs, and the first bit from B INT The final [Formula 19] of the set of PRBs is

[0833]

[0834] The second bit corresponding to the subset of PRBs is determined. Fig.30 As shown, the frequency resources including the UL subband are equally divided for two bit pairs.

[0835] <Alt 2>

[0836] In Alt 2, when the value of timeFrequencySet is set1, the RB applicable to each bit pair of the symbol group may be determined according to the following Alt 2-1 and / or Alt 2-2 according to the DL band size of the symbol group.

[0837] <<Alt 2-1>>

[0838] In Alt 2-1, the symbol group contains only SBFD symbols, and the SBFD symbols in the symbol group have a DL subband based on the total B in each SBFD symbol in the symbol group. INT-DL In the case of the same DL / UL subband allocation pattern for PRBs, the RBs applicable to each bit pair of the symbol group can also be determined by the number of RBs from B INT-DL The initial [Formula 20] of the set of DL PRBs

[0839]

[0840] The first bit corresponding to the subset of DL PRBs and the first bit from B INT-DL The final [Formula 21] of the set of DL PRBs

[0841]

[0842] The second bit corresponding to the subset of DL PRBs is determined. Fig.31As shown, the frequency resources not including the UL subband are equally divided for two bit pairs.

[0843] <<Alt 2-2>>

[0844] In Alt 2-2, the symbol group contains only SBFD symbols, and the SBFD symbols in the symbol group have a total B based on each SBFD symbol in the symbol group. INT-DL-subband In the case of the same DL / UL subband allocation pattern for DL ​​subbands, the RBs applicable to each bit pair of the symbol group can also be determined by the number of RBs from B INT-DL-subband The initial set of DL subbands is [Formula 22]

[0845] or The first bit corresponding to the subset of DL subbands and the first bit from B INT-DL-subband The final [Formula 23] of the set of DL subbands

[0846] or The second bit corresponding to the subset of DL subbands is determined. Fig.32 As shown, the frequency resources not including the UL subband are divided into two DL subbands for two bit pairs.

[0847] In addition, the above-mentioned frequency resource division method is not necessarily limited to the above-mentioned content, and any other division method may also be applied. Which of the above-mentioned Alts is applied may be explicitly or implicitly specified by the specification, 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 should be applied may also be sent in at least one of RRC, DCI, and MAC CE (Medium Access Control Control Element).

[0848] (UE Operation of Proposal 8)

[0849] In Proposal 8, the UE may also adjust the radio resources indicated by the downlink control information in the time domain or the frequency domain in the downlink reception of the time-frequency division duplex operation such as the SBFD operation, and receive the downlink channel in the adjusted radio resources. Here, the time-frequency division duplex may also be SBFD, for example, the downlink channel may also be PDCCH, PDSCH, etc., and the downlink control information may also be DCI 2_1. In addition, the radio resources are resources specified by time units such as symbols and frequency units such as resource blocks.

[0850] Specifically, the UE may exclude the time unit set as the uplink by the time division duplex (TDD) setting from the wireless resources indicated by the downlink control information. That is, for the preemption in the time domain, the UE may obtain N for preemption. INT symbols, and the symbols configured as UL through TDD configuration such as tdd-UL-DL-ConfigurationCommon may be excluded.

[0851] In addition, the UE may exclude the uplink subband in the SBFD operation from the radio resources indicated by the downlink control information. Figure 30 to Figure 32 As shown, the UE may also receive a downlink channel in a frequency band including a UL subband or a frequency band not including a UL subband in the SBFD operation.

[0852] (gNB Operation of Proposal 8)

[0853] In Proposal 8, the gNB may also control and transmit a downlink channel in downlink transmission of a time-frequency division duplex operation such as an SBFD operation, wherein the control causes the terminal to receive the downlink channel in a radio resource adjusted in the time domain or the frequency domain for the radio resource indicated by the downlink control information. Here, the time-frequency division duplex may also be SBFD, for example, the uplink channel may also be PDCCH, PDSCH, etc., and the downlink control information may also be DCI 2_1. In addition, a radio resource is a resource specified by a time unit such as a symbol and a frequency unit such as a resource block.

[0854] UE Capability

[0855] For preemption in a time-frequency division duplex operation such as an SBFD operation, UE capability information indicating whether the UE supports DCI 2_1 enhanced for time-frequency division duplex operation may also be specified. In addition, UE capability information related to preemption for time-frequency division duplex operation such as SBFD operation may also be specified. In the case of supporting preemption enhanced for time-frequency division duplex operation, the UE may also send UE capability information indicating support for DCI 2_1 enhanced for time-frequency division duplex operation to the gNB. If the UE capability information is received, the gNB can send DCI 2_1 enhanced for time-frequency division duplex operation to the UE and enable the UE to perform preemption in time-frequency division duplex operation.

[0856] (Effect of Proposal 8)

[0857] According to Proposal 8, enhanced preemption for time-frequency division duplex operations such as SBFD operations can be achieved.

[0858] (DCI 2_4)

[0859] In section 11.2A of TS38.213, it is specified that for cancellation notification, in DCI format 2_4, the following content is shown:

[0860] N CI : The number of bytes provided by ci-PayloadSize

[0861] B CI : The number of PRBs provided by frequencyRegionforCI in timeFrequencyRegion

[0862] T CI : When the PDCCH monitoring period of the search space set based on DCI format 2_4 is 1 time slot and there are multiple PDCCH monitoring opportunities in the time slot, the timeDurationforCI in timeFrequencyRegion is provided, or, if not, the number of symbols after excluding the symbols for reception of SS / PBCH blocks and the DL symbols indicated by tdd-UL-DL-ConfigurationCommon from a number of symbols equal to the PDCCH monitoring period

[0863] G CI : T provided by timeGranularityforCI in timeFrequencyRegion CI The number of partitions used for each code element.

[0864] Regulations from N CI The MSB of the G CI bit set and G CI The codeword groups have a one-to-one mapping, and the original [Mathematical Formula 24]

[0865]

[0866] The groups contain

[0867] [Mathematical formula 25]

[0868]

[0869] code elements, the remaining [Formula 26]

[0870]

[0871] The groups contain

[0872] [Mathematical formula 27]

[0873]

[0874] In order to detect DCI format 2_4, the UE determines the symbol period with respect to the SCS setting of the activated DL BWP for monitoring the PDCCH. That is, in the time domain, the indicated symbol is divided into G CI A collection.

[0875] Specifies the number of MSBs from each bit set for a symbol group. BI =N CI / G CI bits and N BI PRB groups have a one-to-one mapping, the initial [Math 28]

[0876]

[0877] The groups contain

[0878] [Mathematical formula 29]

[0879]

[0880] PRBs, the remaining [Formula 30]

[0881]

[0882] The groups contain

[0883] [Mathematical formula 31]

[0884]

[0885] According to TS38.214, the UE is specified to represent the offset RB as RIV. start And the length L RB frequencyRegionforCI, and SCS setting for indicating that the UE monitors the activated DL BWP of the PDCCH for detection of DCI format 2_4 carrier The offsetToCarrier in the FrequencyInfoUL-SIB or FrequencyInfoUL is used as the N RFR start =O carier +RB start The first PRB index of CI =L RB That is, it is stipulated that in the frequency domain, for each symbol set, RB is divided into N BI A collection.

[0886] For example, Fig.33An example of segmentation in the time domain and frequency domain based on DCI 2_4 is shown.

[0887] [Study items related to the cancellation of SBFD operations]

[0888] For the time domain, if the SBFD operation in the DL symbol is considered, that is, the DL and UL subbands in the DL symbol, there may be UL transmission in the DL symbol. Therefore, it may not be appropriate to exclude the DL symbol from the symbol indicated by DCI 2_4. For example, Fig.34 As shown, in the SBFD operation, in the DL symbol configured by tdd-UL-DL-ConfigurationCommon, a UL subband may exist.

[0889] On the other hand, for the frequency domain, if the SFBD operation in the DL or UL symbol is considered, the number of UL resource blocks (RBs) in different symbols may be different. For example, for the SBFD symbol set based on the narrowband UL subband, according to the same N BI RB sets, the frequency domain granularity can be smaller than N in non-SBFD UL symbols. BI The RB set is refined.

[0890] [Proposal 9]

[0891] In Proposal 9, cancellation in the time domain and frequency domain enhanced for time-frequency division duplex operation such as SBFD operation is described. Specifically, UL cancellation in the time direction and UL cancellation in the time direction are enhanced as follows.

[0892] T enhanced with respect to the time direction CI Calculated

[0893] Case 1: When a UL subband is set in a resource set as UL in TDD mode

[0894] <Alt 1>

[0895] Contains resources set as DL in TDD mode.

[0896] <Alt 2>

[0897] Included are resources that are set to DL in TDD mode and are not set to SBFD operation.

[0898] Case 2: When a DL subband is configured in a resource configured as UL in TDD mode

[0899] <Alt 1>

[0900] Contains resources set as DL in TDD mode.

[0901] <Alt 2>

[0902] Code elements are not excluded.

[0903] <Alt 3>

[0904] Included are resources that are set to DL in TDD mode and are not used for SBFD operation.

[0905] Case 3: In the case where SBFD operation is not supported in DL symbols, resources configured as DL in TDD mode are included.

[0906] Frequency-dependent enhancement

[0907] <Alt 1>

[0908] The frequency resources including the DL subband are divided.

[0909] <Alt 2>

[0910] The frequency resources excluding the DL subband are divided.

[0911] Throughout this specification, the so-called SBFD operation in a UL symbol may refer to a DL subband in a UL symbol indicated as an uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, and the so-called SBFD operation in a DL symbol may refer to a UL subband in a DL symbol indicated as a downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

[0912] (Cancellation of time domain)

[0913] In the UL cancellation in the time domain, T CI Since there are multiple symbols, the symbols deleted from multiple symbols (the number of which is equal to timeDurationforCI or PDCCH monitoring period) may also correspond to the following situations 1 to 3.

[0914] Case 1: SBFD operation in DL symbols is supported / enabled, and SBFD operation (or DL / UL subband allocation) is notified / configured through cell-specific / group-common signaling (eg, cell-specific / group-common RRC configuration or DCI).

[0915] Case 2: SBFD operation in DL symbols is supported / enabled, and SBFD operation (or DL / UL subband allocation) is notified / configured through UE-specific signaling (eg, UE-specific RRC configuration or UE-specific DCI).

[0916] Case 3: SBFD operation in DL symbols is not supported / enabled.

[0917] <Scenario 1>

[0918] In case 1, when SBFD operation in DL symbols is supported / enabled and SBFD operation (or DL / UL subband allocation) is notified / configured via cell-specific / group-common signaling (e.g., cell-specific / group-common RRC configuration or DCI), in order to obtain T CI The codewords deleted due to the presence of codewords may also be codewords based on the following Alt 1 and / or Alt 2.

[0919] <<Case 1: Alt 1>>

[0920] In Alt 1, when SBFD operation in DL symbols is supported / enabled and SBFD operation (or DL / UL subband allocation) is notified / set via cell-specific / group-common signaling, in order to obtain T CI The symbols deleted by using tdd-UL-DL-ConfigurationCommon may include the symbols indicated as downlink. Alt 1 is the same as Rel-15.

[0921] <<Case 1: Alt 2>>

[0922] In Alt 2, when SBFD operation in DL symbols is supported / enabled and SBFD operation (or DL / UL subband allocation) is notified / set via cell-specific / group-common signaling, in order to obtain T CI The symbols deleted due to the UL cancellation of the SBFD symbol may also include symbols indicated as downlink by tdd-UL-DL-ConfigurationCommon but not configured / notified for SBFD operation. The SBFD DL symbol includes the UL subband, so UL transmission can be performed on the DL symbol. Therefore, the UL cancellation indication based on DCI 2_4 can be applied to the DL symbol.

[0923] <Scenario 2>

[0924] In case 2, when SBFD operation in DL symbols is supported / enabled and SBFD operation (or DL / UL subband allocation) is notified / configured via UE-specific signaling, in order to obtain T CIThe codewords deleted due to the presence of codewords may also be codewords based on the following Alt 1, Alt 2 and / or Alt 3.

[0925] <<Case 2: Alt 1>>

[0926] In Alt 1, when SBFD operation in DL symbols is supported / enabled and SBFD operation (or DL / UL subband allocation) is notified / configured via UE-specific signaling, in order to obtain T CI The symbols deleted by using tdd-UL-DL-ConfigurationCommon may include the symbols indicated as downlink. Alt 1 is the same as Rel-15.

[0927] <<Case 2: Alt 2>>

[0928] In Alt 2, if SBFD operation in DL symbols is supported / enabled and SBFD operation (or DL / UL subband allocation) is notified / set via UE-specific signaling, no symbols may be deleted. In case 2, a specific UE is not sure whether a DL symbol has a UL subband for other UEs in the cell. Therefore, DL symbols may not be deleted for DCI 2_4 indication.

[0929] <<Case 2: Alt 3>>

[0930] In Alt 3, in order to obtain T CI The symbols deleted for DCI 2_4 may also include symbols indicated as downlink by tdd-UL-DL-ConfigurationCommon and, if present, symbols guaranteed for non-SBFD operation as specified by the specification or RRC settings. For example, SSB symbols / time slots can be guaranteed for non-SBFD operation. If the UE can know based on the analysis of Alt 1 that a specific DL symbol (e.g., SSB symbol) is not available for SBFD operation specified by the specification or set by RRC, the DL symbol may also be deleted for DCI 2_4 indication.

[0931] <Scenario 3>

[0932] In case 3, when SBFD operation in DL symbols is not supported / enabled, in order to obtain T CIThe symbols deleted by using tdd-UL-DL-ConfigurationCommon may include the symbols indicated as downlink. This is the same as Rel-15.

[0933] (Cancellation in frequency domain)

[0934] In UL cancellation in the frequency domain, resource blocks (RBs) applicable to each bit pair of a symbol group may also be determined by the following Alt 1 and / or Alt 2.

[0935] <Alt 1>

[0936] In Alt 1, the RB applicable to each bit pair of the symbol group may be the same as the rule of Rel-15, regardless of the UL subband size in the symbol group, and the initial [Math 32]

[0937]

[0938] Groups contain

[0939] [Mathematical formula 33]

[0940]

[0941] PRBs, the remaining [Formula 34]

[0942]

[0943] The groups contain

[0944] [Mathematical formula 35]

[0945]

[0946] PRBs. Fig.35 As shown, the frequency resources including the UL subband are equally divided for two bit pairs.

[0947] <Alt 2>

[0948] In Alt 2, the RB applicable to each bit pair of the symbol group may be determined according to the following Alt 2-1 and / or Alt 2-2 according to the UL band size of the symbol group.

[0949] <<Alt 2-1>>

[0950] In Alt 2-1, it is also possible that the symbol group includes only SBFD symbols, and the SBFD symbols in the symbol group have a UL subband based on the total B in each SBFD symbol in the symbol group. CI-ULIn the case of the same DL / UL subband allocation pattern for PRBs, for the RBs applicable to each bit pair of the symbol group, the initial [Equation 36]

[0951]

[0952] Groups contain

[0953] [Mathematical formula 37]

[0954]

[0955] PRBs, the remaining [Formula 38]

[0956]

[0957] The groups contain

[0958] [Math 39]

[0959]

[0960] PRBs. Fig.36 As shown, the frequency resources not including the DL subband are equally divided for two bit pairs.

[0961] <<Alt 2-2>>

[0962] In Alt 2-2, the symbol group may include only SBFD symbols, and the SBFD symbols in the symbol group may have a value based on the total B among the SBFD symbols in the symbol group. CI-UL-subband In the case of the same DL / UL subband allocation pattern for UL subbands, for the RBs applicable to each bit pair of the symbol group, the initial [Equation 40]

[0963]

[0964] Groups contain

[0965] [Mathematical formula 41]

[0966]

[0967] UL subbands, the remaining [Formula 42]

[0968]

[0969] The groups contain

[0970] [Mathematical formula 43]

[0971]

[0972] UL subbands. Fig.37 As shown, the frequency resources not including the DL subband are divided into two UL subbands for two bit pairs.

[0973] In addition, which of the above Alts to apply can 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 should be applied can also be sent in at least one of RRC, DCI, and MAC CE (Medium Access Control Control Element).

[0974] (UE operation of Proposal 9)

[0975] In Proposal 9, the UE may also adjust the radio resources indicated by the downlink control information in the time domain or frequency domain in the uplink transmission of the time-frequency division duplex operation such as the SBFD operation, and transmit the uplink channel in the adjusted radio resources. Here, the time-frequency division duplex may also be SBFD, for example, the uplink channel may also be PUCCH, PUSCH, etc., and the downlink control information may also be DCI 2_4. In addition, the radio resources are resources specified by time units such as symbols and frequency units such as resource blocks.

[0976] Specifically, the UE may exclude the time unit set as the uplink by the time division duplex (TDD) setting from the radio resources indicated by the downlink control information. That is, for UL cancellation in the time domain, the UE may obtain the T CI symbols, and the symbols configured as DL by TDD configuration such as tdd-UL-DL-ConfigurationCommon may be excluded.

[0977] In addition, the UE may also exclude the downlink subband in the SBFD operation from the radio resources indicated by the downlink control information. That is, for UL cancellation in the frequency domain, such as Figure 35 to Figure 37 As shown, the UE may also transmit the uplink channel in a frequency band including the DL subband or a frequency band not including the DL subband in the SBFD operation.

[0978] (gNB Operation of Proposal 9)

[0979] In Proposal 9, the gNB may also control and transmit an uplink channel in uplink reception of a time-frequency division duplex operation such as an SBFD operation, wherein the control causes the terminal to transmit the uplink channel in a radio resource adjusted in the time domain or the frequency domain for the radio resource indicated by the downlink control information. Here, the time-frequency division duplex may also be SBFD, for example, the uplink channel may also be PUCCH, PUSCH, etc., and the downlink control information may also be DCI 2_4. In addition, a radio resource is a resource specified by a time unit such as a symbol and a frequency unit such as a resource block.

[0980] UE Capability

[0981] For cancellation in time-frequency division duplex operation such as SBFD operation, UE capability information indicating whether the UE supports DCI 2_4 enhanced for time-frequency division duplex operation may also be specified. In addition, UE capability information related to cancellation of time-frequency division duplex such as SBFD operation may also be specified. In the case of supporting cancellation enhanced for time-frequency division duplex operation, the UE may also send UE capability information indicating support for DCI 2_4 enhanced for time-frequency division duplex operation to the gNB. If the UE capability information is received, the gNB can send DCI 2_4 enhanced for time-frequency division duplex operation to the UE and enable the UE to perform cancellation in SBFD operation.

[0982] (Effect of Proposal 9)

[0983] According to Proposal 9, UL cancellation enhanced for time-frequency division duplexing such as SBFD operation can be achieved.

[0984] <Hardware Structure>

[0985] In addition, the block diagram used in the description of the above-mentioned embodiment shows a block of a functional unit. These functional blocks (structural units) are implemented by any combination of at least one of hardware and software. In addition, the implementation method of each functional block is not particularly limited. That is, each functional block can be implemented by a device that is physically or logically combined, or two or more devices that are physically or logically separated can be directly or indirectly (for example, by wired, wireless, etc.) connected and implemented by these multiple devices. The functional block can also be implemented by combining the above-mentioned one device or the above-mentioned multiple devices with software.

[0986] Functions include judging, deciding, determining, calculating, calculating, processing, deriving, investigating, searching, confirming, receiving, sending, outputting, accessing, solving, selecting, selecting, establishing, comparing, assuming, expecting, regarding, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, assigning, etc., but are not limited to these. For example, a functional block (structural unit) that implements a sending function is called a transmitting unit or a transmitter. As described above, the implementation method is not particularly limited.

[0987] For example, a base station, a user terminal, etc. in one embodiment of the present disclosure may also function as a computer that performs processing of the wireless communication method of the present disclosure. Fig.38 1 is a diagram showing an example of the hardware structure of a base station and a user terminal involved in one embodiment of the present disclosure. The above-mentioned base station 10 and user terminal 20 can also be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0988] In the following description, the term "device" can be rewritten as circuit, device, unit, etc. The hardware configuration of the base station 10 and the user terminal 20 can be configured as Fig.38 Each device shown in the figure may include one or more devices, and may be configured not to include some devices.

[0989] The functions of the base station 10 and the user terminal 20 are realized by reading specific software (program) into hardware such as the processor 1001 and the memory 1002, so that the processor 1001 performs calculations and controls the communication based on the communication device 1004, or controls at least one of the reading and writing of data in the memory 1002 and the storage 1003.

[0990] The processor 1001 controls the entire computer by, for example, operating an operating system. The processor 1001 may also be composed of a central processing unit (CPU) including an interface with peripheral devices, a control device, a computing device, registers, etc. For example, the above-mentioned baseband signal processing unit 104, call processing unit 105, etc. may also be implemented by the processor 1001.

[0991] In addition, the processor 1001 reads the program (program code), software module, data, etc. from at least one of the storage 1003 and the communication device 1004 to the memory 1002, and performs various processes according to them. As a program, a program that enables a computer to perform at least a part of the operations described in the above-mentioned embodiments can be used. For example, the control unit 401 of the user terminal 20 can also be implemented by a control program stored in the memory 1002 and operated in the processor 1001, and the same can be implemented for other functional blocks. The above-mentioned various processes are described as being performed by one processor 1001, but can also be performed simultaneously or sequentially by more than two processors 1001. The processor 1001 can also be implemented by more than one chip. In addition, the program can also be sent from the network via an electrical communication line.

[0992] The memory 1002 is a computer-readable recording medium, and may be composed of at least one of a ROM (Read Only Memory), an EPROM (Erasable Programmable ROM), an EEPROM (Electrically Erasable Programmable ROM), a RAM (Random Access Memory), etc. The memory 1002 may also be referred to as a register, a cache, a main memory (main storage device), etc. The memory 1002 can store executable programs (program codes), software modules, etc. for implementing the wireless communication method involved in one embodiment of the present disclosure.

[0993] The storage 1003 is a computer-readable recording medium, and may be composed of at least one of an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, an optical magnetic disk (e.g., a compact disk, a digital versatile disk, a Blu-ray (registered trademark) disk), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy (registered trademark) disk, a magnetic strip, etc. The storage 1003 may also be referred to as an auxiliary storage device. The above-mentioned storage medium may also be, for example, a database, a server, or other appropriate medium including at least one of the memory 1002 and the storage 1003.

[0994] The communication device 1004 is hardware (transmitting and receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also called a network device, a network controller, a network card, a communication module, etc. In order to realize at least one of frequency division duplex (FDD: Frequency Division Duplex) and time division duplex (TDD: Time Division Duplex), the communication device 1004 can also be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. For example, the above-mentioned transmitting and receiving antenna 101, the amplifier unit 102, the transmitting and receiving unit 103, the transmission path interface 106, etc. can also be realized by the communication device 1004. The transmitting and receiving unit 103 can also be realized by physically or logically separating the transmitting unit 103a and the receiving unit 103b.

[0995] The input device 1005 is an input device that receives input from the outside (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.). The output device 1006 is an output device that performs output to the outside (e.g., a display, a speaker, an LED light, etc.). In addition, the input device 1005 and the output device 1006 may also be an integrated structure (e.g., a touch panel).

[0996] In addition, the processor 1001, the memory 1002 and other devices are connected via a bus 1007 for communicating information. The bus 1007 may be configured as a single bus or may be configured as different buses between the devices.

[0997] In addition, the base station 10 and the user terminal 20 may also 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 a part or all of each functional block may be implemented by the hardware. For example, the processor 1001 may also be implemented using at least one of these hardware.

[0998] The notification of information is not limited to the methods / implementations described in the present disclosure, and may also be performed by other methods. For example, the notification of information may also be implemented through physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), high-level 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 a combination thereof. In addition, RRC signaling may also be referred to as an RRC message, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, and the like.

[0999] The various modes and embodiments described in the present disclosure may also be applied to LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER3G, 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 (x is, for example, an integer or a 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)), IEEE At least one of 802.20, UWB (Ultra-WideBand), Bluetooth (registered trademark), a system using other appropriate systems, and a next-generation system expanded, modified, produced, and specified based on them. In addition, multiple systems can also be combined (for example, a combination of at least one of LTE and LTE-A and 5G, etc.) for application.

[1000] The processing procedures, sequences, flow charts, etc. of each method / implementation described in this disclosure may be reversed in order as long as they are not contradictory. For example, for the method described in this disclosure, various step elements are presented in an illustrative order, but are not limited to the specific order presented.

[1001] In the present disclosure, a specific operation is performed by a base station, and sometimes it is performed by its upper node according to the situation. Obviously, in a network composed of one or more network nodes having a base station, various operations performed for communication with a terminal may also be performed by at least one of the base station and other network nodes other than the base station (for example, consider MME or S-GW, etc., but not limited to these). In the above, the case where there is one other network node other than the base station is illustrated, and it may also be a combination of multiple other network nodes (for example, MME and S-GW).

[1002] Information, etc. (see the item "information, signal") may be output from a higher layer (or lower layer) to a lower layer (or higher layer), or may be input and output via a plurality of network nodes.

[1003] The input and output information can be stored in a specific location (e.g., a memory) or managed using a management table. The input and output information can be overwritten, updated, or added. The output information can also be deleted. The input information can also be sent to other devices.

[1004] The determination can be made by a value represented by a bit (0 or 1), a true or false value (Boolean value: true or false), or by comparison of numerical values ​​(for example, comparison with a specific value).

[1005] The various methods / implementations described in this disclosure may be used alone or in combination, and may be switched during execution. In addition, notification of specific information (e.g., notification of "is X") is not limited to being performed explicitly, but may also be performed implicitly (e.g., not notifying the specific information).

[1006] The present disclosure has been described in detail above, but it is obvious to those skilled in the art that the present disclosure is not limited to the embodiments described in the present disclosure. The present disclosure can be implemented as a modification and variation without departing from the subject matter and scope of the present disclosure determined according to the records of the claims. Therefore, the description of the present disclosure is for the purpose of illustration and does not have any restrictive meaning to the present disclosure.

[1007] Whether software is called software, firmware, middle-ware, microcode, hardware description language, or other names, it should be broadly interpreted as meaning instructions, instruction sets, code, code segments, program code, program, sub-program, software modules, applications, software applications, software packages, routines, sub-routines, objects, executable files, execution threads, procedures, functions, etc.

[1008] In addition, software, instructions, information, etc. may also be sent and received via a transmission medium. For example, when software is sent from a website, server, or other remote source using at least one of wired technology (coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), etc.) and wireless technology (infrared, microwave, etc.), at least one of these wired technology and wireless technology is included in the definition of transmission medium.

[1009] Information, signals, etc. described in this disclosure may also be represented using any of a variety of different techniques. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be mentioned throughout the above description may also be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any combination thereof.

[1010] In addition, the terms described in the present disclosure and the terms required for understanding the present disclosure may also be replaced with terms having the same or similar meanings. For example, at least one of a channel and a code element may also be a signal (signaling). In addition, a signal may also be a message. In addition, a component carrier (CC) may also be referred to as a carrier frequency, a cell, a frequency carrier, etc.

[1011] As used in this disclosure, the terms "system" and "network" are used interchangeably.

[1012] In addition, the information, parameters, etc. described in the present disclosure may be expressed by absolute values, relative values ​​relative to a specific value, or other corresponding information. For example, a wireless resource may also be indicated by an index.

[1013] The names used for the above parameters are not limiting in all respects. Furthermore, sometimes the mathematical formulas for using these parameters are different from those explicitly disclosed in this disclosure. Various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable names, and therefore, the various names assigned to these various channels and information elements are not limiting in all respects.

[1014] In the present 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" can be used interchangeably. There are also cases where base stations are referred to by terms such as macrocell, small cell, femtocell, and picocell.

[1015] A base station can accommodate one or more (for example, three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be divided into multiple smaller areas, and each smaller area can also provide communication services through a base station subsystem (for example, a small base station for indoor use (Remote Radio Head (RRH))). Terms such as "cell" or "sector" refer to a part or the entirety of the coverage area of ​​at least one of a base station and a base station subsystem that provides communication services within the coverage area.

[1016] In the present disclosure, the base station sending information to the terminal can also be rewritten as the base station instructing the terminal to control and operate based on the information.

[1017] In the present disclosure, terms such as “mobile station (MS)”, “user terminal”, “user device (UE)”, and “terminal” can be used interchangeably.

[1018] There are also cases where a mobile station is referred to by those skilled in the art as a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a hand set, a user agent, a mobile client, a client, or several other appropriate terms.

[1019] At least one of the base station and the mobile station may also be referred to as a transmitting device, a receiving device, a communication device, etc. In addition, at least one of the base station and the mobile station may also be a device carried in a mobile body, a mobile body, etc. The mobile body refers to a movable object, and the moving speed is arbitrary. In addition, of course, it also includes the situation where the mobile body stops. The mobile body includes, for example, vehicles, transport vehicles, cars, automatic two-wheeled vehicles, bicycles, networked cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, trailers, rickshaws, ships (ships and other watercrafts other than these), airplanes, rockets, artificial satellites, drones (registered trademarks), multi-rotor aircraft, quadcopters, balloons, and objects carried on them, in addition, but not limited to these. In addition, the mobile body may also be a mobile body that travels autonomously based on an operating instruction. It may be a means of transportation (for example, a vehicle, an airplane, etc.), a mobile body that moves in an unmanned manner (for example, a drone, an autonomous driving vehicle, etc.), or a robot (man- or unmanned). In addition, at least one of the base station and the mobile station may include a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

[1020] In addition, the base station in the present disclosure may also be rewritten as a user terminal. For example, the various methods / implementations of the present disclosure may also be applied to a structure in which the communication between a base station and a user terminal is replaced by the communication between multiple user terminals (for example, it may also be referred to as D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.). In this case, it may also be set as a structure in which the user terminal 20 has the functions possessed by the above-mentioned base station 10. In addition, terms such as "uplink" and "downlink" may also be rewritten as terms corresponding to communication between terminals (for example, "side"). For example, uplink channels, downlink channels, etc. may also be rewritten as side channels.

[1021] Likewise, the user terminal in the present disclosure may be rewritten as a base station. In this case, the base station 10 may have the functions of the user terminal 20 described above.

[1022] Fig.39 FIG. 2 shows a structural example of the vehicle 1. Fig.39 As shown, the vehicle 1 includes 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 to 29, an information service unit 12 and a communication module 13.

[1023] The drive unit 2 is constituted by, for example, an engine, a motor, or a mixture of an engine and a motor.

[1024] The steering unit 3 is configured to include at least a steering wheel (also referred to as a handlebar), and steers at least one of the front wheels and the rear wheels based on an operation of the steering wheel operated by a user.

[1025] The electronic control unit 10 includes a microprocessor 31, a memory (ROM, RAM) 32, and a communication port (IO port) 33. Signals from various sensors 21 to 27 provided in the vehicle are input to the electronic control unit 10. The electronic control unit 10 may also be referred to as an ECU (Electronic Control Unit).

[1026] The signals from the various sensors 21 to 28 include a current signal from a current sensor 21 for sensing the current of the motor, a rotation speed signal of the front and rear wheels obtained by a rotation speed sensor 22, an air pressure signal of the front and rear wheels obtained by an air pressure sensor 23, a vehicle speed signal obtained by a vehicle speed sensor 24, an acceleration signal obtained by an acceleration sensor 25, an accelerator pedal depression amount signal obtained by an accelerator pedal sensor 29, a brake pedal depression amount signal obtained by a brake pedal sensor 26, a shift lever operation signal obtained by a shift lever sensor 27, a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 28, and the like.

[1027] The information service unit 12 is composed of various devices such as a car navigation system, an audio system, a speaker, a television, and a radio for providing (outputting) various information such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 12 uses information obtained from an external device via the communication module 13 and the like to provide various multimedia information and multimedia services to the occupants of the vehicle 1.

[1028] The information service unit 12 may include input devices for accepting input from the outside (e.g., keyboard, mouse, microphone, switch, button, sensor, touch panel, etc.), and may also include output devices for implementing output to the outside (e.g., display, speaker, LED light, touch panel, etc.).

[1029] The driving assistance system unit 30 is composed of various devices such as millimeter wave radar, LiDAR (Light Detection and Ranging), camera, locator (e.g., GNSS, etc.), map information (e.g., high-definition (HD) mapping, autonomous driving vehicle (AV) mapping, etc.), gyroscope system (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chip, AI processor, etc., for providing functions for preventing accidents before they happen or reducing the driver's driving load, and one or more ECUs that control these devices. In addition, the driving assistance system unit 30 sends and receives various information via the communication module 13, and realizes the driving assistance function or the autonomous driving function.

[1030] The communication module 13 can communicate with the microprocessor 31 and the components of the vehicle 1 via the communication port. For example, the communication module 13 sends and receives data between the drive unit 2, the steering unit 3, the accelerator pedal 4, the brake pedal 5, the shift lever 6, the left and right front wheels 7, the left and right rear wheels 8, the axle 9, the microprocessor 31 and the memory (ROM, RAM) 32 in the electronic control unit 10, and the sensors 21 to 28 via the communication port 33.

[1031] The communication module 13 can be controlled by the microprocessor 31 of the electronic control unit 10 and is a communication device that can communicate with an external device. For example, various information is sent and received with the external device via wireless communication. The communication module 13 can be located either inside or outside the electronic control unit 10. The external device can also be, for example, a base station, a mobile station, etc.

[1032] The communication module 13 may also transmit at least one of the signals from the various sensors 21-28 input to the electronic control unit 10, information obtained based on the signals, and information based on input from the outside (user) obtained via the information service unit 12 to an external device via wireless communication. The electronic control unit 10, the various sensors 21-28, the information service unit 12, etc. may also be referred to as an input unit that receives input. For example, the PUSCH transmitted through the communication module 13 may also include information based on the above input.

[1033] The communication module 13 receives various information (traffic information, signal information, vehicle-to-vehicle information, etc.) sent from an external device, and displays it to the information service unit 12 provided in the vehicle. The information service unit 12 may also be referred to as an output unit that outputs information (for example, outputs information to a display, a speaker, etc., based on the PDSCH received by the communication module 13 (or data / information decoded from the PDSCH)).

[1034] In addition, the communication module 13 stores various information received from the external device in the memory 32 that can be used by the microprocessor 31. The microprocessor 31 can also control the drive unit 2, the steering unit 3, the accelerator pedal 4, the brake pedal 5, the shift lever 6, the left and right front wheels 7, the left and right rear wheels 8, the axle 9, the sensors 21 to 28, etc., which are provided in the vehicle 1, based on the information stored in the memory 32.

[1035] (Summary of Implementation Methods)

[1036] As described above, according to one embodiment of the present invention, a terminal is provided, which comprises: a control unit, which controls the receiving operation of the downlink data channel according to whether the uplink time unit in the non-time-frequency division duplex operation and the time unit in the time-frequency division duplex operation overlap with the downlink data channel; and a receiving unit, which performs the receiving operation of the downlink data channel through the controlled receiving operation.

[1037] According to the above structure, it is possible to enhance the downlink data channel for time-frequency division duplex operation.

[1038] In one embodiment, when the downlink data channel overlaps with the uplink time unit in the non-time-frequency division duplex operation, the control unit may also receive the downlink data channel in a time unit in which the downlink data channel does not overlap with the uplink time unit in the non-time-frequency division duplex operation. According to this embodiment, an enhanced downlink data channel in the time-frequency division duplex operation and the non-time-frequency division duplex operation can be provided.

[1039] In one embodiment, when the downlink data channel overlaps with a time unit in the time-frequency division duplex operation, the control unit may also control the receiving operation of the downlink data channel regardless of whether the downlink data channel overlaps with an uplink subband in the time unit. According to this embodiment, an enhanced downlink data channel in time-frequency division duplex operation and non-time-frequency division duplex operation can be provided.

[1040] In one embodiment, when the downlink data channel overlaps with a time unit in the time-frequency division duplex operation, the control unit may also control the receiving operation of the downlink data channel according to whether the downlink data channel overlaps with an uplink subband in the time unit. According to this embodiment, an enhanced downlink data channel in the time-frequency division duplex operation and the non-time-frequency division duplex operation can be provided.

[1041] In addition, according to one embodiment of the present disclosure, a base station is provided, which has: a control unit, which controls the sending operation of a downlink data channel in one or both of the uplink time unit in a non-time-frequency division duplex operation and the time unit in a time-frequency division duplex operation; and a sending unit, which performs the sending operation of the downlink data channel through the controlled sending operation.

[1042] According to the above structure, it is possible to enhance the downlink data channel for time-frequency division duplex operation.

[1043] In addition, according to one embodiment of the present invention, a wireless communication method performed by a terminal is provided, and the wireless communication method has the following features: controlling the receiving operation of the downlink data channel according to whether the uplink time unit in the non-time-frequency division duplex operation and the time unit in the time-frequency division duplex operation overlap with the downlink data channel; and performing the receiving operation of the downlink data channel through the controlled receiving operation.

[1044] According to the above structure, it is possible to enhance the downlink data channel for time-frequency division duplex operation.

[1045] In addition, according to one embodiment of the present invention, a terminal is provided, which has: a control unit, which controls the receiving operation of the downlink data channel according to whether the uplink time unit in the non-time-frequency division duplex operation and the time unit in the time-frequency division duplex operation overlap with the downlink data channel; and a receiving unit, which performs the receiving operation of the downlink data channel through the controlled receiving operation.

[1046] According to the above structure, it is possible to enhance the downlink data channel for time-frequency division duplex operation.

[1047] In one embodiment, when the multiple opportunities of the downlink data channel overlap with the uplink time unit in the non-time-frequency division duplex operation, the control unit may also interpret that the multiple opportunities of the downlink data channel are not sent. According to this embodiment, an enhanced downlink data channel in both time-frequency division duplex operation and non-time-frequency division duplex operation can be provided.

[1048] In one embodiment, when the multiple opportunities of the downlink data channel overlap with the time unit in the time-frequency division duplex operation, the control unit may also control the reception 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 in the time-frequency division duplex operation and the non-time-frequency division duplex operation can be provided.

[1049] In one embodiment, when multiple opportunities of the downlink data channel overlap with a time unit in the time-frequency division duplex operation, the control unit may also control the receiving operation of the downlink data channel according to whether the downlink data channel overlaps with an uplink subband in the time unit. According to this embodiment, an enhanced downlink data channel in the time-frequency division duplex operation and the non-time-frequency division duplex operation can be provided.

[1050] In addition, according to one embodiment of the present disclosure, a base station is provided, which has: a control unit, which controls the sending operation of a downlink data channel in one or both of an uplink time unit in a non-time-frequency division duplex operation and a time unit in a time-frequency division duplex operation; and a sending unit, which performs the sending operation of the downlink data channel through the controlled sending operation.

[1051] According to the above structure, it is possible to enhance the downlink data channel for time-frequency division duplex operation.

[1052] In addition, according to one embodiment of the present invention, a wireless communication method performed by a terminal is provided, and the wireless communication method has the following features: controlling the receiving operation of the downlink data channel according to whether the uplink time unit in the non-time-frequency division duplex operation and the time unit in the time-frequency division duplex operation overlap with the downlink data channel; and performing the receiving operation of the downlink data channel through the controlled receiving operation.

[1053] According to the above structure, it is possible to enhance the downlink data channel for time-frequency division duplex operation.

[1054] In addition, according to one embodiment of the present disclosure, a terminal is provided, comprising: a control unit that determines a HARQ-ACK codebook for a downlink data channel according to whether the downlink data channel overlaps with an uplink time unit; and a sending unit that sends a delivery confirmation in accordance with the HARQ-ACK codebook.

[1055] According to the above structure, HARQ-ACK can be enhanced for time-frequency division duplex operation.

[1056] In one embodiment, the control unit may also exclude a semi-persistent scheduling (SPS) PDSCH from the determination of the HARQ-ACK codebook when the SPS PDSCH overlaps with an uplink symbol set semi-statically. According to this embodiment, enhanced HARQ-ACK in both time-frequency division duplex operation and non-time-frequency division duplex operation can be provided.

[1057] In one embodiment, the control unit may also exclude the SLIV (Start and Length Indicator Value) of the downlink data channel from the determination of the HARQ-ACK codebook when the SLIV overlaps with the semi-statically set uplink symbol. According to this embodiment, enhanced HARQ-ACK in time-frequency division duplex operation and non-time-frequency division duplex operation can be provided.

[1058] In one embodiment, the control unit may also determine the HARQ-ACK codebook for the downlink data channel according to whether the time-frequency division duplex operation is semi-statically set or dynamically notified. According to this embodiment, enhanced HARQ-ACK in time-frequency division duplex operation and non-time-frequency division duplex operation can be provided.

[1059] In addition, according to one embodiment of the present disclosure, a base station is provided, which has: a sending unit that sends a downlink data channel; and a receiving unit that receives a delivery confirmation in accordance with a HARQ-ACK codebook for the downlink data channel determined according to whether the downlink data channel overlaps with an uplink time unit.

[1060] According to the above structure, HARQ-ACK can be enhanced for time-frequency division duplex operation.

[1061] In addition, according to one embodiment of the present disclosure, a wireless communication method performed by a terminal is provided, the wireless communication method comprising: determining a HARQ-ACK codebook for a downlink data channel according to whether the downlink data channel overlaps with an uplink time unit; and sending a delivery confirmation in accordance with the HARQ-ACK codebook.

[1062] According to the above structure, HARQ-ACK can be enhanced for time-frequency division duplex operation.

[1063] In addition, according to one embodiment of the present invention, a terminal is provided, which has: a control unit, which controls the sending operation of the uplink data channel according to whether the downlink time unit in non-time-frequency division duplex operation and the time unit in time-frequency division duplex operation overlap with the uplink data channel; and a sending unit, which performs the sending operation of the uplink data channel through the controlled sending operation.

[1064] According to the above structure, the uplink data channel can be enhanced for the time-frequency division duplex operation.

[1065] In one embodiment, when the uplink data channel overlaps with the downlink time unit in the non-time-frequency division duplex operation, the control unit may also send the uplink data channel in a time unit in which the uplink data channel does not overlap with the downlink time unit in the non-time-frequency division duplex operation. According to this embodiment, an enhanced uplink data channel in the time-frequency division duplex operation and the non-time-frequency division duplex operation can be provided.

[1066] In one embodiment, when the uplink data channel overlaps with a time unit in the time-frequency division duplex operation, the control unit may also control the transmission operation of the uplink data channel regardless of whether the uplink data channel overlaps with a downlink subband in the time unit. According to this embodiment, an enhanced uplink data channel in time-frequency division duplex operation and non-time-frequency division duplex operation can be provided.

[1067] In one embodiment, when the uplink data channel overlaps with a time unit in the time-frequency division duplex operation, the control unit may also control the transmission operation of the uplink data channel according to whether the uplink data channel overlaps with a downlink subband in the time unit. According to this embodiment, an enhanced uplink data channel in the time-frequency division duplex operation and the non-time-frequency division duplex operation can be provided.

[1068] In addition, according to one embodiment of the present disclosure, a base station is provided, which has: a control unit, which controls the receiving operation of an uplink data channel in one or both of a downlink time unit in a non-time-frequency division duplex operation and a time unit in a time-frequency division duplex operation; and a receiving unit, which performs the receiving operation of the uplink data channel through the controlled receiving operation.

[1069] According to the above structure, the uplink data channel can be enhanced for the time-frequency division duplex operation.

[1070] In addition, according to one embodiment of the present invention, a wireless communication method performed by a terminal is provided, and the wireless communication method has the following features: controlling the sending operation of the uplink data channel based on whether the downlink time unit in the non-time-frequency division duplex operation and the time unit in the time-frequency division duplex operation overlap with the uplink data channel; and performing the sending operation of the uplink data channel through the controlled sending operation.

[1071] According to the above structure, the uplink data channel can be enhanced for the time-frequency division duplex operation.

[1072] In addition, according to one embodiment of the present invention, a terminal is provided, which has: a control unit, which controls the sending operation of the uplink data channel according to whether the downlink time unit in non-time-frequency division duplex operation and the time unit in time-frequency division duplex operation overlap with the uplink data channel; and a sending unit, which performs the sending operation of the uplink data channel through the controlled sending operation.

[1073] According to the above structure, the uplink data channel can be enhanced for the time-frequency division duplex operation.

[1074] In one embodiment, the control unit may also 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 in time-frequency division duplex operation and non-time-frequency division duplex operation can be provided.

[1075] In one embodiment, the control unit may also determine the invalid time unit for repeated transmission of the uplink data channel according to whether the time-frequency division duplex is dynamically notified or semi-statically set. According to this embodiment, an enhanced uplink data channel in time-frequency division duplex operation and non-time-frequency division duplex operation can be provided.

[1076] In one embodiment, the control unit may also control the sending operation of the actual repetition when the segmented actual repetition for the repeated transmission of the uplink data channel overlaps with the time-frequency division duplex time unit according to whether there is overlap with the downlink subband. According to this embodiment, an enhanced uplink data channel in the time-frequency division duplex operation and the non-time-frequency division duplex operation can be provided.

[1077] In addition, according to one embodiment of the present disclosure, a base station is provided, which has: a control unit, which controls the receiving operation of an uplink data channel in one or both of the downlink time unit in a non-time-frequency division duplex operation and the time unit in a SBFD operation; and a receiving unit, which performs the receiving operation of the uplink data channel through the controlled receiving operation.

[1078] According to the above structure, the uplink data channel can be enhanced for the time-frequency division duplex operation.

[1079] In addition, according to one embodiment of the present invention, a wireless communication method performed by a terminal is provided, and the wireless communication method has the following features: controlling the sending operation of the uplink data channel based on whether the downlink time unit in the non-time-frequency division duplex operation and the time unit in the time-frequency division duplex operation overlap with the uplink data channel; and performing the sending operation of the uplink data channel through the controlled sending operation.

[1080] According to the above structure, the uplink data channel can be enhanced for the time-frequency division duplex operation.

[1081] In addition, according to one embodiment of the present invention, a terminal is provided, which comprises: a control unit, which controls the sending operation of the uplink control channel according to whether the downlink time unit in non-time-frequency division duplex operation and the time unit in time-frequency division duplex operation overlap with the uplink control channel; and a sending unit, which performs the sending operation of the uplink control channel through the controlled sending operation.

[1082] According to the above structure, it is possible to enhance the uplink control channel for the time-frequency division duplex operation.

[1083] In one embodiment, when the uplink control channel overlaps with the downlink time unit in the non-time-frequency division duplex operation, the control unit may also send the uplink control channel in a time unit in which the uplink control channel does not overlap with the downlink time unit in the non-time-frequency division duplex operation. According to this embodiment, an enhanced uplink control channel in the time-frequency division duplex operation and the non-time-frequency division duplex operation can be provided.

[1084] In one embodiment, when the uplink control channel overlaps with a time unit in the time-frequency division duplex operation, the control unit may also control the transmission operation of the uplink control channel regardless of whether the uplink control channel overlaps with a downlink subband in the time unit. According to this embodiment, an enhanced uplink control channel in time-frequency division duplex operation and non-time-frequency division duplex operation can be provided.

[1085] In one embodiment, when the uplink control channel overlaps with a time unit in the time-frequency division duplex operation, the control unit may also control the transmission operation of the uplink control channel according to whether the uplink control channel overlaps with a downlink subband in the time unit. According to this embodiment, an enhanced uplink control channel in time-frequency division duplex operation and non-time-frequency division duplex operation can be provided.

[1086] In addition, according to one embodiment of the present disclosure, a base station is provided, which has: a control unit, which controls the receiving operation of an uplink control channel in one or both of a downlink time unit in a non-time-frequency division duplex operation and a time unit in a time-frequency division duplex operation; and a receiving unit, which performs the receiving operation of the uplink control channel through the controlled receiving operation.

[1087] According to the above structure, it is possible to enhance the uplink control channel for the time-frequency division duplex operation.

[1088] In addition, according to one embodiment of the present invention, a wireless communication method performed by a terminal is provided, and the wireless communication method has the following features: controlling the sending operation of the uplink control channel based on whether the downlink time unit in the non-time-frequency division duplex operation and the time unit in the time-frequency division duplex operation overlap with the uplink control channel; and performing the sending operation of the uplink control channel through the controlled sending operation.

[1089] According to the above structure, it is possible to enhance the uplink control channel for the time-frequency division duplex operation.

[1090] In addition, according to one embodiment of the present disclosure, a terminal is provided, which has: a control unit, which enables the extension operation of the HARQ-ACK when the extension conditions of the HARQ-ACK in time-frequency division duplex operation and non-time-frequency division duplex operation are met; and a sending unit, which delays the sending of the uplink control channel of the HARQ-ACK in accordance with the extension operation.

[1091] According to the above structure, the deferred operation of HARQ-ACK can be enhanced for the time-frequency division duplex operation.

[1092] In one embodiment, the control unit may also enable the deferred operation of the HARQ-ACK when the semi-persistent scheduling HARQ-ACK (SPS HARQ-ACK) overlaps with the non-time-frequency division duplex semi-static downlink time unit, the synchronization signal block (SSB) time unit or the type-0 CORESET (type-0 CORESET) (Control Resource Set) time unit. According to this embodiment, an enhanced uplink control channel in time-frequency division duplex operation and non-time-frequency division duplex operation can be provided.

[1093] In one embodiment, the control unit may also enable the deferred operation of the HARQ-ACK when the semi-persistent scheduling HARQ-ACK (SPS HARQ-ACK) overlaps with the non-time frequency division duplex semi-static downlink time unit, the synchronization signal block (SSB) time unit or the type-0 CORESET (type-0 CORESET) (Control Resource Set) time unit, or overlaps with the time frequency division duplex semi-static / dynamic time unit. According to this embodiment, the enhanced deferred operation of the HARQ-ACK in the time frequency division duplex operation and the non-time frequency division duplex operation can be provided.

[1094] In one embodiment, the control unit may also enable the deferred operation of the HARQ-ACK when the semi-persistent scheduling HARQ-ACK (SPS HARQ-ACK) overlaps with a non-SBFD semi-static downlink time unit, a synchronization signal block (SSB) time unit, or a type-0 CORESET (type-0CORESET) (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, the deferred operation of the enhanced HARQ-ACK in time-frequency division duplex operation and non-time-frequency division duplex operation can be provided.

[1095] In addition, according to one embodiment of the present disclosure, a base station is provided, which has: a sending unit that sends a downlink data channel; and a receiving unit that receives an uplink control channel of the HARQ-ACK that is deferred in accordance with a deferred operation that is set to be enabled when a deferred condition of the HARQ-ACK in a time-frequency division duplex operation and a non-time-frequency division duplex operation for the downlink data channel is met.

[1096] According to the above structure, the deferred operation of HARQ-ACK can be enhanced for the time-frequency division duplex operation.

[1097] In addition, according to one embodiment of the present invention, a wireless communication method performed by a terminal is provided, which comprises: enabling the HARQ-ACK extension operation when the extension condition of the HARQ-ACK in the time-frequency division duplex operation and the non-time-frequency division duplex operation is met; and postponing the sending of the uplink control channel of the HARQ-ACK in accordance with the extension operation.

[1098] According to the above structure, the deferred operation of HARQ-ACK can be enhanced for the time-frequency division duplex operation.

[1099] In addition, according to one embodiment of the present disclosure, a terminal is provided, which has: a control unit, which adjusts the wireless resources indicated by downlink control information with respect to the time domain or frequency domain in the downlink reception of time-frequency division duplex operation; and a receiving unit, which receives the downlink channel in the adjusted wireless resources.

[1100] According to the above structure, preemption can be enhanced for time-frequency division duplex operation.

[1101] In one embodiment, the control unit may also exclude the time unit set as the uplink by time division duplex (TDD) setting from the wireless resources indicated by the downlink control information. According to this embodiment, enhanced preemption in time-frequency division duplex operation and non-time-frequency division duplex operation can be provided.

[1102] In one embodiment, the control unit may also 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 in time-frequency division duplex operation and non-time-frequency division duplex operation can be provided.

[1103] In addition, according to one embodiment of the present disclosure, a base station is provided, which has: a control unit, which controls, in the downlink transmission of time-frequency division duplex operation, so that the terminal receives a downlink channel in the wireless resources adjusted with respect to the time domain or frequency domain for the wireless resources indicated by the downlink control information; and a sending unit, which sends the downlink channel.

[1104] According to the above structure, preemption can be enhanced for time-frequency division duplex operation.

[1105] In addition, according to one embodiment of the present disclosure, a wireless communication method performed by a terminal is provided, which comprises: in downlink reception of time-frequency division duplex operation, adjusting the wireless resources indicated by downlink control information with respect to the time domain or the frequency domain; and receiving a downlink channel in the adjusted wireless resources.

[1106] According to the above structure, preemption can be enhanced for time-frequency division duplex operation.

[1107] In addition, according to one embodiment of the present disclosure, a terminal is provided, which has: a control unit, which adjusts the wireless resources indicated by downlink control information with respect to the time domain or frequency domain in the uplink transmission of time-frequency division duplex operation; and a sending unit, which sends an uplink channel in the adjusted wireless resources.

[1108] According to the above structure, cancellation can be enhanced for time-frequency division duplex operation.

[1109] In one embodiment, the control unit may also exclude the time unit set as the downlink by time division duplex (TDD) setting from the wireless resources indicated by the downlink control information. According to this embodiment, enhanced cancellation in time frequency division duplex operation and non-time frequency division duplex operation can be provided.

[1110] In one embodiment, the control unit may also 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 in time-frequency division duplex operation and non-time-frequency division duplex operation can be provided.

[1111] In addition, according to one embodiment of the present disclosure, a base station is provided, which has: a control unit, which controls, in the uplink reception of time-frequency division duplex operation, so that the terminal sends an uplink channel in the wireless resources adjusted with respect to the time domain or frequency domain for the wireless resources indicated by the downlink control information; and a receiving unit, which receives the uplink channel.

[1112] According to the above structure, cancellation can be enhanced for time-frequency division duplex operation.

[1113] In addition, according to one embodiment of the present disclosure, a wireless communication method performed by a terminal is provided, which comprises: in an uplink transmission of a time-frequency division duplex operation, adjusting the wireless resources indicated by downlink control information with respect to the time domain or the frequency domain; and sending an uplink channel in the adjusted wireless resources.

[1114] According to the above structure, cancellation can be enhanced for time-frequency division duplex operation.

[1115] (Supplementary Implementation Methods)

[1116] The terms "determining" and "determining" used in the present disclosure may include various actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up (for example, searching in a table, database or other data structure), ascertaining, etc. as being considered as "determining" and "determining". In addition, "determining" and "determining" may include receiving (for example, receiving information), transmitting (for example, transmitting information), inputting, outputting, accessing (for example, accessing data in a memory) as being considered as "determining" and "determining". In addition, "determining" and "determining" may include resolving, selecting, choosing, establishing, comparing, etc. as being considered as "determining" and "determining". That is, "judgment" and "decision" can include situations where some actions are considered to be "judged" and "decided". In addition, "judgment (decision)" can also be rewritten as "assuming", "expecting", "considering", etc.

[1117] The terms "connected", "coupled", or all variations thereof, mean all connections or combinations, direct or indirect, between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The combination or connection between elements may be physical, logical, or a combination thereof. For example, "connection" may also be rewritten as "access". As used in the present disclosure, it may be considered that two elements are "connected" or "coupled" to each other using at least one of one or more wires, cables, and printed electrical connections, and as several non-limiting and non-inclusive examples, electromagnetic energy having wavelengths in the wireless frequency domain, microwave region, and light (both visible and invisible) region may be used.

[1118] The reference signal may also be referred to as RS (Reference Signal), or may be referred to as a pilot depending on the applied standard.

[1119] The term “based on” as used in the present disclosure does not mean “based only on” unles...

Claims

1. A terminal having: a control unit, controlling a transmission operation of the uplink data channel according to whether one or both of a downlink time unit in a non-time-frequency-division-duplex operation and a time unit in a time-frequency-division-duplex operation overlap with the uplink data channel; and The sending unit performs the sending operation of the uplink data channel through the controlled sending operation.

2. The terminal according to claim 1, wherein: When the uplink data channel overlaps with a downlink time unit in the non-time-frequency-division duplex operation, the control unit sends the uplink data channel in a time unit that does not overlap with a downlink time unit in the non-time-frequency-division duplex operation.

3. The terminal according to claim 1, wherein: When the uplink data channel overlaps a time unit in the time-frequency division duplex operation, the control unit controls a transmission operation of the uplink data channel regardless of whether the uplink data channel overlaps a downlink subband in the time unit.

4. The terminal according to claim 1, wherein: When the uplink data channel overlaps with a time unit in the time-frequency division duplex operation, the control unit controls a transmission operation of the uplink data channel according to whether the uplink data channel overlaps with a downlink subband in the time unit.

5. A base station, comprising: a control unit that controls a reception operation of an uplink data channel in one or both of a downlink time unit in a non-time-frequency-division-duplex operation and a time unit in a time-frequency-division-duplex operation; and The receiving unit performs a receiving operation of the uplink data channel through the controlled receiving operation.

6. A wireless communication method, performed by a terminal, the wireless communication method comprising: controlling a transmission operation of the uplink data channel according to whether one or both of a downlink time unit in a non-time-frequency-division-duplex operation and a time unit in a time-frequency-division-duplex operation overlap with an uplink data channel; and Through the controlled transmission operation, the transmission operation of the uplink data channel is performed.

Images