WO2024034096A1 - Terminal, station de base et procédé de communication sans fil - Google Patents

Terminal, station de base et procédé de communication sans fil Download PDF

Info

Publication number
WO2024034096A1
WO2024034096A1 PCT/JP2022/030681 JP2022030681W WO2024034096A1 WO 2024034096 A1 WO2024034096 A1 WO 2024034096A1 JP 2022030681 W JP2022030681 W JP 2022030681W WO 2024034096 A1 WO2024034096 A1 WO 2024034096A1
Authority
WO
WIPO (PCT)
Prior art keywords
sbfd
symbol
symbols
dynamic
semi
Prior art date
Application number
PCT/JP2022/030681
Other languages
English (en)
Japanese (ja)
Inventor
大輔 栗田
浩樹 原田
チーピン ピ
ジン ワン
ラン チン
Original Assignee
株式会社Ｎｔｔドコモ
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 株式会社Ｎｔｔドコモ filed Critical 株式会社Ｎｔｔドコモ
Priority to PCT/JP2022/030681 priority Critical patent/WO2024034096A1/fr
Publication of WO2024034096A1 publication Critical patent/WO2024034096A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1268—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of uplink data flows

Definitions

  • the present disclosure relates to a terminal, a base station, and a wireless communication method.
  • LTE Long Term Evolution
  • 3GPP Rel. 10-14 LTE-Advanced (3GPP Rel. 10-14) has been specified for the purpose of further increasing capacity and sophistication of LTE (Third Generation Partnership Project (3GPP) Release (Rel.) 8, 9).
  • LTE Long Term Evolution
  • 5G 5th generation mobile communication system
  • 5G+ 6th generation mobile communication system
  • 6G 6th generation mobile communication system
  • NR New Radio
  • 3GPP Rel.15 3GPP Rel.15
  • uplink (UL) resources are insufficient compared to downlink (DL) resources.
  • one of the purposes of the present disclosure is to provide a terminal, a base station, and a wireless communication method that improve resource usage efficiency.
  • One aspect of the present disclosure relates to whether a downlink data channel overlaps one or both of an uplink time unit in non-time frequency division duplex operation and a time unit in time frequency division duplex operation. Accordingly, the present invention relates to a terminal having a control section that controls a reception operation of the downlink data channel, and a reception section that executes the reception operation of the downlink data channel according to the controlled reception operation. Other aspects of the present disclosure include a controller that determines a HARQ-ACK codebook for the downlink data channel depending on whether the downlink data channel overlaps an uplink time unit; The present invention relates to a terminal having a transmitter that transmits a delivery confirmation according to a codebook.
  • Another aspect of the disclosure is whether an uplink data channel overlaps one or both of a downlink time unit in non-time frequency division duplex operation and a time unit in time frequency division duplex operation.
  • the present invention relates to a terminal having a control unit that controls a transmission operation of the uplink data channel according to the above, and a transmission unit that executes the transmission operation of the uplink data channel according to the controlled transmission operation.
  • Another aspect of the disclosure is whether an uplink control channel overlaps one or both of a downlink time unit in non-time frequency division duplex operation and a time unit in time frequency division duplex operation.
  • the present invention relates to a terminal having a control section that controls a transmission operation of the uplink control channel according to the above, and a transmission section that executes the transmission operation of the uplink control channel according to the controlled transmission operation.
  • Another aspect of the present disclosure includes a control unit that enables the HARQ-ACK postponement operation when a HARQ-ACK postponement condition in a time-frequency division duplex operation and a non-time frequency division duplex operation is satisfied.
  • a transmitter that postpones transmission of the HARQ-ACK uplink control channel according to the postponement operation.
  • aspects of the present disclosure include a control unit that adjusts radio resources indicated by downlink control information in the time domain or frequency domain in downlink reception of time frequency division duplex operation;
  • the present invention relates to a terminal having a receiving unit that receives a downlink channel.
  • Other aspects of the present disclosure include a controller that adjusts radio resources indicated by downlink control information in the time domain or frequency domain in uplink transmission of time frequency division duplex operation;
  • the present invention relates to a terminal having a transmitter configured to transmit an uplink channel.
  • FIG. 1 is a block diagram showing the functional configuration of a base station (gNB) according to an embodiment of the present disclosure.
  • FIG. 2 is a block diagram showing the functional configuration of a terminal (UE) according to an embodiment of the present disclosure.
  • 3A and 3B are diagrams illustrating an example of arrangement of radio resources of XDD (Cross Division Duplex) or SBFD (Subband non-overlapping Full Duplex) according to an embodiment of the present disclosure.
  • FIG. 4 is a diagram illustrating XDD or SBFD operation according to an embodiment of the present disclosure.
  • 5A and 5B are diagrams illustrating TDD (non-SBFD) and SBFD according to one embodiment of the present disclosure.
  • 6A-6E are diagrams illustrating pure time units and SBFD time units according to one embodiment of the present disclosure.
  • FIG. 7 is a diagram illustrating single TRP PDSCH with slot-based PDSCH repetition according to Rel-15 NR.
  • 8A to 8C are diagrams showing PDSCH transmission by Rel-15/16 NR.
  • FIG. 9 is a diagram illustrating a single DCI-based multi-TRP PDSCH transmission scheme using Rel-16 NR.
  • FIGS. 10A and 10B are diagrams showing Type 1 HARQ-ACK based on Rel-15/16/17 NR.
  • FIG. 11 is a diagram showing candidate PDSCH reception opportunities by Rel-16 NR.
  • FIG. 12 is a diagram illustrating HARQ-ACK opportunities associated with candidate PDSCH reception by Rel-16 NR.
  • FIG. 13 is a diagram showing a semi-persistent scheduling (SPS) HARQ-ACK codebook (CB) using Rel-15/16/17 NR.
  • FIG. 14 is a diagram showing multi-PDSCH scheduling using Rel-15/16/17 NR.
  • FIG. 15 is a diagram illustrating PDSCH enhancement for SBFD operation according to one embodiment of the present disclosure.
  • FIG. 16 is a diagram illustrating PDSCH enhancement for SBFD operation according to an embodiment of the present disclosure.
  • FIG. 17 is a diagram illustrating PDSCH enhancement for SBFD operation according to one embodiment of the present disclosure.
  • FIG. 18 is a diagram illustrating PDSCH enhancement for SBFD operation according to one embodiment of the present disclosure.
  • FIG. 19 is a diagram illustrating PDSCH enhancement for SBFD operation according to an embodiment of the present disclosure.
  • FIG. 20 is a diagram illustrating PDSCH enhancement for SBFD operation according to one embodiment of the present disclosure.
  • 21A and 21B are diagrams showing a single TRP PUSCH based on Rel-15/16 NR.
  • FIG. 22 is a diagram showing time division multiplexing (TDM) multi-TRP PUSCH repetitions A and B with Rel-17 NR.
  • FIG. 23 is a diagram showing multi-PUSCH scheduling using Rel-15/16/17 NR.
  • FIG. 24 is a diagram illustrating PUSCH enhancement for SBFD operation according to an embodiment of the present disclosure.
  • FIG. 25 is a diagram showing PUCCH repetition by Rel-15/16 NR.
  • FIG. 26 is a diagram illustrating SPS HARQ-ACK postponement operation by Rel-17 NR.
  • FIG. 27 is a diagram illustrating PUCCH enhancement for SBFD operation according to an embodiment of the present disclosure.
  • FIG. 28 is a diagram showing preemption by DCI 2_1 according to Rel-15/16/17 NR.
  • FIG. 29 is a diagram illustrating preemption enhancement for SBFD operation according to one embodiment of the present disclosure.
  • FIG. 30 is a diagram illustrating preemption enhancement for SBFD operation according to one embodiment of the present disclosure.
  • FIG. 31 is a diagram illustrating preemption enhancement for SBFD operation according to one embodiment of the present disclosure.
  • FIG. 32 is a diagram illustrating preemption enhancement for SBFD operation according to one embodiment of the present disclosure.
  • FIG. 33 is a diagram showing cancellation by DCI 2_4 according to Rel-15/16/17 NR.
  • FIG. 34 is a diagram illustrating cancellation enhancement for SBFD operation according to one embodiment of the present disclosure.
  • FIG. 35 is a diagram illustrating cancellation enhancement for SBFD operation according to one embodiment of the present disclosure.
  • FIG. 36 is a diagram illustrating cancellation enhancement for SBFD operation according to one embodiment of the present disclosure.
  • FIG. 37 is a diagram illustrating cancellation enhancement for SBFD operation according to one embodiment of the present disclosure.
  • FIG. 38 is a block diagram showing the hardware configuration of a base station and a terminal according to an embodiment of the present disclosure.
  • FIG. 39 is a block diagram showing the hardware configuration of a vehicle according to an embodiment of the present disclosure.
  • Wireless communication system The configuration of a wireless communication system according to an embodiment of the present disclosure will be described below.
  • communication is performed using any one of the wireless communication methods according to the above-described embodiments of the present disclosure or a combination thereof.
  • Wireless communication systems include Long Term Evolution (LTE), which is specified by the Third Generation Partnership Project (3GPP), and 5th generation mobile communication system Ne. w Radio (5G NR), realizing communication using these successor wireless communication systems, etc. It may be a system that
  • the wireless communication system may support dual connectivity between multiple Radio Access Technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)).
  • MR-DC has dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), N Dual connectivity between R and LTE (NR-E -UTRA Dual Connectivity (NE-DC)).
  • RATs Radio Access Technologies
  • MR-DC has dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), N Dual connectivity between R and LTE (NR-E -UTRA Dual Connectivity (NE-DC)).
  • E-UTRA Evolved Universal Terrestrial Radio Access
  • EN-DC E-UTRA-NR Dual Connectivity
  • NE-DC N Dual connectivity between R and LTE
  • the LTE (E-UTRA) base station (eNB) is the master node (Master Node (MN)), and the NR base station (gNB) is the secondary node (Secondary Node (SN)).
  • the NR base station (gNB) is the MN
  • the LTE (E-UTRA) base station (eNB) is the SN.
  • a wireless communication system has dual connectivity between multiple base stations within the same RAT (for example, dual connectivity (NR-NR Dual Connectivity (NN-DC) where both the MN and SN are NR base stations (gNB)). ) may be supported.
  • dual connectivity NR-NR Dual Connectivity (NN-DC) where both the MN and SN are NR base stations (gNB)
  • gNB NR base stations
  • the wireless communication system may include a base station forming a macro cell C1 with relatively wide coverage, and a base station forming a small cell C2 that is located within the macro cell C1 and narrower than the macro cell C1.
  • a terminal may be located within at least one cell. The arrangement, number, etc. of each cell and terminal are not limited to a specific aspect.
  • a terminal may connect 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).
  • CA carrier aggregation
  • CC component carriers
  • DC dual connectivity
  • Each CC may be included in at least one of a first frequency band (Frequency Range 1 (FR1)) and a second frequency band (Frequency Range 2 (FR2)).
  • Macro cell C1 may be included in FR1
  • small cell C2 may be included in FR2.
  • FR1 may be in a frequency band below 6 GHz (sub-6 GHz)
  • FR2 may be in a frequency band above 24 GHz (above-24 GHz).
  • the frequency bands and definitions of FR1 and FR2 are not limited to these, and for example, FR1 may correspond to a higher frequency band than FR2.
  • the terminal may communicate using at least one of time division duplex (TDD) and frequency division duplex (FDD) in each CC.
  • TDD time division duplex
  • FDD frequency division duplex
  • the plurality of base stations may be connected by wire (for example, optical fiber compliant with Common Public Radio Interface (CPRI), X2 interface, etc.) or wirelessly (for example, NR communication).
  • wire for example, optical fiber compliant with Common Public Radio Interface (CPRI), X2 interface, etc.
  • NR communication for example, when NR communication is used as a backhaul between two base stations, the base station that corresponds to the upper station is called the Integrated Access Backhaul (IAB) donor, and the base station that corresponds to the relay station is called the integrated access backhaul (IAB) donor. , may be called an IAB node.
  • IAB Integrated Access Backhaul
  • IAB integrated access backhaul
  • a base station may be connected to the core network via another base station or directly.
  • the core network may include, for example, at least one of Evolved Packet Core (EPC), 5G Core Network (5GCN), Next Generation Core (NGC), and the like.
  • EPC Evolved Packet Core
  • 5GCN 5G Core Network
  • NGC Next Generation Core
  • the terminal may be a terminal compatible with at least one of communication systems such as LTE, LTE-A, 5G, and 6G.
  • an orthogonal frequency division multiplexing (OFDM)-based wireless access method may be used.
  • OFDM orthogonal frequency division multiplexing
  • CP-OFDM Cyclic Prefix OFDM
  • DFT-s-OFDM Discrete Fourier Transform Spread OFDM
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single Carrier Frequency Division Multiple Access
  • a wireless access method may also be called a waveform. Note that in the wireless communication system, other wireless access methods (for example, other single carrier transmission methods, other multicarrier transmission methods) may be used as the UL and DL wireless access methods.
  • downlink channels include a physical downlink shared channel (PDSCH) shared by each terminal, a broadcast channel (physical broadcast channel (PBCH)), and a downlink control channel (physical Downlink Control Channel (PDCCH)) etc. may be used.
  • PDSCH physical downlink shared channel
  • PBCH physical broadcast channel
  • PDCCH physical Downlink Control Channel
  • uplink channels include a physical uplink shared channel (PUSCH) shared by each terminal, a physical uplink control channel (PUCCH), and a random access channel ( Physical Random Access Channel (PRACH) or the like may be used.
  • PUSCH physical uplink shared channel
  • PUCCH physical uplink control channel
  • PRACH Physical Random Access Channel
  • User data, upper layer control information, System Information Block (SIB), etc. are transmitted via the PDSCH.
  • User data, upper layer control information, etc. may be transmitted via PUSCH.
  • a Master Information Block (MIB) may be transmitted via the PBCH.
  • Lower layer control information may be transmitted by PDCCH.
  • the lower layer control information may include, for example, downlink control information (DCI) that includes scheduling information for at least one of PDSCH and PUSCH.
  • DCI downlink control information
  • DCI that schedules PDSCH may be called DL assignment, DL DCI, etc.
  • DCI that schedules PUSCH may be called UL grant, UL DCI, etc.
  • PDSCH may be replaced with DL data
  • PUSCH may be replaced with UL data.
  • a control resource set (CONTROL REsource SET (CORESET)) and a search space (search space) may be used to detect the PDCCH.
  • CORESET corresponds to a resource for searching DCI.
  • the search space corresponds to a search area and a search method for PDCCH candidates.
  • One CORESET may be associated with one or more search spaces. The UE may monitor the CORESET associated with a certain search space based on the search space configuration.
  • One search space may correspond to PDCCH candidates that correspond to one or more aggregation levels.
  • One or more search spaces may be referred to as a search space (SS) set.
  • search space search space
  • search space set search space setting
  • search space set setting search space set setting
  • CORESET search space set setting
  • CORESET setting etc. in the present disclosure may be read interchangeably.
  • PUCCH provides channel state information (CSI), delivery confirmation information (for example, Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK /NACK, etc.) and scheduling request (Scheduling Request).
  • CSI channel state information
  • delivery confirmation information for example, Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK /NACK, etc.
  • Scheduling Request scheduling request
  • Uplink Control Information (UCI) including at least one of SR) may be transmitted.
  • a random access preamble for establishing a connection with a cell may be transmitted by PRACH.
  • a synchronization signal (SS), a downlink reference signal (DL-RS), etc. may be transmitted.
  • DL-RS includes a cell-specific reference signal (CRS) and a channel state information reference signal (CSI-RS).
  • demodulation reference signal (DeModulation Reference signal A positioning reference signal (DMRS), a positioning reference signal (PRS), a phase tracking reference signal (PTRS), etc. may be transmitted.
  • DMRS positioning reference signal
  • PRS positioning reference signal
  • PTRS phase tracking reference signal
  • the synchronization signal may be, for example, at least one of a primary synchronization signal (PSS) and a secondary synchronization signal (SSS).
  • a signal block including SS (PSS, SSS) and PBCH (and DMRS for PBCH) may be called an SS/PBCH block, SS Block (SSB), etc. Note that SS, SSB, etc. may also be called reference signals.
  • a measurement reference signal Sounding Reference Signal (SRS)
  • a demodulation reference signal DMRS
  • UL-RS uplink reference signal
  • DMRS may be referred to as a UE-specific reference signal (UE-specific Reference Signal).
  • the gNB 100 and the UE 200 include functions that implement the embodiments described below. However, the gNB 100 and the UE 200 may each have only some of the functions in the embodiment.
  • FIG. 1 is a diagram showing an example of the functional configuration of the gNB 100.
  • the gNB 100 includes a receiving section 101, a transmitting section 102, and a control section 103.
  • the functional configuration shown in FIG. 1 is only an example. As long as the operations according to the embodiments of the present invention can be carried out, the functional divisions and functional parts may have any names.
  • the receiving unit 101 includes a function of receiving various signals transmitted from the UE 200 and acquiring, for example, information on a higher layer from 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.
  • the control unit 103 stores preset setting information and various setting information to be transmitted to the UE 200 in a storage device, and reads them from the storage device as necessary. Further, the control unit 103 executes processing related to communication with the UE 200.
  • a functional unit related to signal transmission in the control unit 103 may be included in the transmitting unit 102, and a functional unit related to signal reception in the control unit 103 may be included in the receiving unit 101.
  • FIG. 2 is a diagram showing an example of the functional configuration of the UE 200.
  • the UE 200 includes a transmitter 201, a receiver 202, and a controller 203.
  • the functional configuration shown in FIG. 2 is only an example. As long as the operations according to the embodiments of the present invention can be carried out, the functional divisions and functional parts may have any names.
  • the transmitter 201 creates a transmission signal from the transmission data and wirelessly transmits the transmission signal.
  • the receiving unit 202 wirelessly receives various signals and obtains higher layer signals from the received physical layer signals. Further, the receiving unit 202 has a function of receiving NR-PSS, NR-SSS, NR-PBCH, DL/UL control signal, reference signal, etc. transmitted from the gNB 100.
  • the control unit 203 stores various setting information received from the gNB 100 by the receiving unit 202 in a storage device, and reads it from the storage device as necessary. Further, the control unit 203 executes processing related to communication with the gNB 100.
  • a functional unit related to signal transmission in the control unit 203 may be included in the transmitting unit 201, and a functional unit related to signal reception in the control unit 203 may be included in the receiving unit 202.
  • XDD Time Division Duplex
  • SBFD subband non-overlapping Full Duplex
  • XDD or SBFD may refer to a duplex method in which DL and UL are frequency division multiplexed within one component carrier (CC) of the TDD band (DL and UL can be used simultaneously).
  • CC component carrier
  • FIG. 3A shows Rel. 16 is a diagram illustrating an example of TDD settings defined up to No. 16.
  • FIG. 3A TDD slots or symbols are configured for the UE in the bandwidth of one component carrier (CC) (cell, may also be called serving cell), bandwidth portion (BWP), etc. .
  • CC component carrier
  • BWP bandwidth portion
  • the time ratio of DL slots and UL slots is 4:1.
  • FIG. 3B is a diagram showing an example of the configuration of the SBFD.
  • the resources used for DL reception and the resources used for UL transmission overlap in time. According to such a resource configuration, more UL resources can be secured, and resource utilization efficiency can be improved.
  • both ends of the frequency domain may be set as DL resources, and a UL resource may be sandwiched between these DL resources.
  • a guard area may be set at the boundary between the DL resource and the UL resource.
  • FIG. 4 is a diagram showing an example of SBFD operation.
  • part of the DL resources of the TDD band is set as the UL resource, and the DL and UL are configured to partially overlap in the time domain.
  • each of the plurality of UEs 200 receives a DL channel/signal.
  • one UE 200 receives the DL channel/signal
  • another UE 200 receives the DL channel/signal.
  • the base station 100 performs simultaneous transmission and reception of DL and UL.
  • each of the plurality of UEs 200 (UE#1 and UE#2 in FIG. 4) transmits a UL channel/signal.
  • DL frequency resources and UL frequency resources in the UE carrier are configured as DL BWP and UL BWP, respectively.
  • Multiple BWP configurations and BWP adaptation mechanisms are required to switch one DL/UL frequency resource to another DL/UL frequency resource.
  • the time resources (time units such as symbols and slots) in the TDD carrier for UE 200 are configured as at least one of DL, UL, and flexible (FL) in the TDD configuration. Ru.
  • SBFD symbols are advertised or configured as UL (or DL) on a certain frequency resource (subband), or advertised or configured for UL transmission (or DL reception), as shown in FIG. 5B.
  • it may be notified or set as DL (or UL), or it may be a symbol notified or set for DL reception (or UL transmission).
  • the SBFD symbol may be a symbol that is notified or configured as UL (or DL) in a part of the frequency resource, or a symbol that is notified or configured for UL transmission (or DL reception).
  • the SBFD symbol may be notified or set as DL (or UL) in a part of the frequency resource, or may be a symbol notified or set for DL reception (or UL transmission).
  • the time unit may be a symbol level, a slot/subslot level, or a group of symbols/slots/subslots. That is, an SBFD time unit may be an SBFD symbol, a slot/subslot that includes or overlaps the SBFD symbol, or a group of symbols/slots/subslots that includes or overlaps the SBFD symbol.
  • a pure time unit is a non-SBFD symbol (i.e., a symbol that is not an SBFD symbol), a slot/subslot that does not contain or overlap an SBFD symbol, or a symbol/slot/subslot that does not contain or overlap an SBFD symbol. It may be a group of subslots and may be referred to as a non-SBFD time unit.
  • a pure time unit may be referred to as a time unit consisting only of DL on a frequency resource, as shown in FIG. 6A, or as a time unit consisting of only DL on a frequency resource, as shown in FIG. 6B. It may also be referred to as a time unit consisting of.
  • DL resources and UL resources may have various arrangement patterns in the frequency domain.
  • the SBFD time units of frequency domain pattern #1 may have an arrangement pattern as shown in FIG. 6C.
  • the SBFD time units of frequency domain pattern #2 may have an arrangement pattern as shown in FIG. 6D.
  • the SBFD time units of frequency domain pattern #3 may have an arrangement pattern as shown in FIG. 6E.
  • the frequency domain pattern for the SBFD time unit may mean a resource repetition pattern in the frequency domain for the SBFD time unit.
  • SBFD time frequency division duplexing
  • SBFD semi-static UL symbol is an SBFD symbol set as UL by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.
  • SBFD dynamic UL symbol is an SBFD symbol that is set as flexible (FL) by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated and notified as UL by DCI 2_0.
  • SBFD semi-static DL symbol is an SBFD symbol set as DL by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.
  • SBFD dynamic DL symbol is an SBFD symbol that is set as FL by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated and notified as DL by DCI 2_0.
  • SBFD semi-static FL symbol is an SBFD symbol set as FL by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.
  • SBFD dynamic FL symbol is an SBFD symbol that is set as FL by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated and notified as FL by DCI 2_0.
  • a “non-SBFD semi-static UL symbol” is a non-SBFD symbol that is configured as a UL by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.
  • non-SBFD dynamic UL symbol is a non-SBFD symbol that is configured as a FL by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated and notified as a UL by DCI 2_0.
  • non-SBFD semi-static DL symbol is a non-SBFD symbol that is set as DL by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.
  • non-SBFD dynamic DL symbol is a non-SBFD symbol that is set as FL by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated and notified as DL by DCI 2_0.
  • non-SBFD semi-static FL symbol is a non-SBFD symbol that is configured as a FL by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.
  • non-SBFD dynamic FL symbol is a non-SBFD symbol that is configured as a FL by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated and notified as a FL by DCI 2_0.
  • PDSCH in Rel-15/16/1-7 Regarding TDD collision of PDSCH, i.e. overlap between resources for PDSCH reception and resources scheduled as uplink, according to Rel-15/16/17, PDSCH or PDSCH repetition that overlaps with semi-static UL symbol It is specified that it will not be received. That is, for the symbol set of the slot notified to the UE as uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, PDCCH, PDSCH or CSI-RS is partially the same as the symbol set of the slot. It is specified that the UE does not receive the PDCCH, PDSCH or CSI-RS when even the PDCCH, PDSCH or CSI-RS overlap.
  • tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated is the slot of these multiple slots.
  • at least one symbol of the symbol set for which the UE is scheduled to receive PDSCH in the slot is an uplink symbol, it is specified that the UE does not receive the PDSCH in the slot.
  • the UE is configured by higher layers to receive CSI-RS or PDSCH in a symbol set of a slot, and the UE signals a slot format with a symbol subset from that symbol set as uplink or flexible. 2_0 with a slot format value other than 255, or the UE detects a DCI format that notifies the UE to transmit PUSCH, PUCCH, SRS or PRACH in at least one symbol in the symbol set. In this case, it is specified that the UE cancels CSI-RS reception in the symbol set of the slot, or cancels PDSCH reception in the slot.
  • Rel-15 NR supports single transmit/receive point (s-TRP) PDSCH with no repetition or slot-based PDSCH repetition.
  • s-TRP transmit/receive point
  • a PDSCH repetition may be transmitted over multiple slots, as shown in FIG.
  • a single PDCCH schedules a single PDSCH of a single TRP, as shown in FIG. 8A.
  • Rel-16 NR also supports two mechanisms for multi-transmission/reception point (m-TRP)/panel PDSCH transmission: single PDCCH-based m-TRP/panel transmission and multi-PDCCH-based m-TRP/panel transmission. and supports.
  • m-TRP multi-transmission/reception point
  • a single PDCCH schedules multiple PDSCHs of multiple TRPs. For example, as shown in FIG. 8B, PDCCH 1 schedules PDSCH 1/layer 1 and PDSCH 2/layer 2.
  • each PDCCH of multiple PDCCHs schedules a single PDSCH of each TRP.
  • PDCCH 1 schedules PDSCH 1/codeword (CW) 1
  • PDCCH 2 schedules PDSCH 2/CW 2.
  • Rel-16 NR supports five schemes for single DCI (s-DCI) based m-TRP PDSCH transmission. Specifically, as shown in FIG. 9, five schemes are supported: SDM (1a) scheme, FDMSchemeA (2a), FDMSchemeB (2b), TDMSchemeA (3), and TDMSchemeB (4).
  • the allocated resource blocks (RBs) notified by frequency domain resource allocation are the first RB set (TRP#) for the first TRP, as shown in FIG. PDSCH from TRP #1) and a second RB set for the second TRP (PDSCH from TRP #2).
  • Section 5.1.3.2 of TS38.214 defines a TBS determination procedure consisting of steps 1 to 3.
  • the UE first determines the number of REs in a slot (N RE ).
  • the UE obtains an intermediate variable (N info ) based on the number of REs (N RE ).
  • the UE determines the TBS based on the intermediate variable (N info ).
  • s-DCI-based m-TRP PDSCH by FDMSchemeA it is specified that the number of REs for TBS calculation is determined based on the symbols of the first TCI state, i.e., the total symbols in a slot include Not based.
  • s-DCI based m-TRP PDSCH by FDMSchemeB it is specified that the number of REs for TBS calculation is determined based on the RB in the first TCI state, i.e. notified by FDRA. Not based on RB.
  • HARQ-ACK CB For the generation of a HARQ-ACK codebook (CB) for semi-persistent scheduling (SPS), Section 9.1.2 of TS38.213 states that the SPS PDSCH or each repetition of the SPS PDSCH overlaps with a semi-static UL symbol. In this case, it is specified that the relevant SPS PDSCH is excluded from the HARQ-ACK CB.
  • Section 9.1.2.1 of TS38.213 states that when performing TDRA pruning, each iteration of SLIV (Start and Length Indicator Value) or SLIV is a semi-static UL. It is specified that the SLIV is deleted from the candidate TDRA if it overlaps with the symbol.
  • step A-2 candidate PDSCH reception opportunities in each slot are determined for each K1. That is, the candidate PDSCH reception opportunities may be associated with the TDRA table set R. Also, candidate PDSCH reception opportunities in the time domain RA table that overlaps with the UL configured by tdd-UL-UL-ConfigurationCommon and tdd-UL-UL-ConfigurationDedicated may be excluded. Furthermore, when determining candidate PDSCH reception opportunities, SLIVs that overlap with semi-static UL symbols may be deleted. Further, for candidate PDSCH reception opportunities that overlap in the time domain, the candidate PDSCH reception opportunities may be generated based on specific rules. For example, M A,c of serving cell c in Rel-16 may be configured as shown in FIG. 11.
  • step B the UE, for a total of 0 ACK HARQ-ACK information bits, Determine the HARQ-ACK information bits of .
  • n e.g., the last two symbols may be set semi-stick as UL
  • row index (RI) 2, 3, and 8 may be excluded from the generation of HARQ-ACK bits because these candidate PDSCH reception opportunities overlap with semi-static UL symbols. That is, HARQ-ACK bits for these candidate PDSCH reception opportunities may not be generated.
  • the ordering is applied in ascending order of serving cell index, ascending order of SPS configuration index, and ascending order of slot index. It is specified that the SPS PDSCH is deleted if each repetition of the SPS PDSCH overlaps with a semi-static UL symbol. Therefore, when generating the SPS PDSCH-only HARQ-ACK CB, the SPS PDSCH or each repetition of the SPS PDSCH that overlaps with a semi-static UL symbol may be excluded from the HARQ-ACK CB. That is, HARQ-ACK bits for these SPS PDSCHs or each repetition of SPS PDSCHs may not be generated.
  • SPS PDSCH #2 and #3 overlap with the semi-static UL symbol, so they are excluded from the SPS HARQ-ACK CB, and the HARQ-ACK CB is excluded from the SPS PDSCH #1. , #4.
  • DCI 1_1 When scheduling multiple PDSCHs, DCI 1_1 is used as the DCI format. For example, as shown in FIG. 14, PDSCH #1 to #4 can be scheduled by one DCI. Rel-15/16/17 NR supports 120, 480, and 960 kHz SCS, and specifies that the maximum number of PDSCHs that can be scheduled by one DCI is eight. Also, for TDRA, a separate ⁇ SLIV, mapping type, scheduling offset K0 ⁇ may be applied to each PDSCH in the row of the TDRA table. If a PDSCH collides with a semi-static UL symbol, the PDSCH will be canceled, but it is not expected that all PDSCHs will be canceled.
  • the MCS, NDI, and RV of the first or second TB field may appear only once and may be applied to the first TB of each PDSCH. It is also specified that the HPN field applies to the first valid PDSCH, is incremented by 1 for subsequent PDSCHs, and is not incremented for invalid PDSCHs (i.e., PDSCHs that collide with semi-static UL symbols). has been done.
  • Proposal 1 describes PDSCH enhancement for time frequency division duplexing operations such as SBFD operations. Specifically, the PDSCH dropping rules are extended for SBFD operation as follows. Case 1: When PDSCH resources overlap with non-SBFD UL symbols ⁇ Alt-A> The UE does not receive PDSCH. ⁇ Alt-B> The UE assumes that the transmission of the PDSCH is deferred to a later slot that does not overlap with non-SBFD UL or FL symbols. Case 2: When PDSCH resources overlap with SBFD symbols ⁇ Alt 0> The UE does not assume this case. ⁇ Alt 1> The UE operates as follows regardless of whether there is overlap with the UL subband.
  • ⁇ Alt 1-1> The UE does not receive PDSCH.
  • ⁇ Alt 1-2>> The UE assumes that the transmission of the PDSCH has been deferred to non-SBFD DL resources.
  • ⁇ Alt 1-3>> The UE interprets that the PDSCH is rate matched to resources other than SBFD symbols.
  • ⁇ Alt 2> The UE operates as follows depending on whether there is overlap with the UL subband. If the PDSCH does not overlap with the UL subband, the UE receives the PDSCH. On the other hand, if the PDSCH overlaps the UL subband, the UE operates as follows.
  • ⁇ Alt 2-1>>> The UE does not receive PDSCH.
  • Case 1 The symbols included in the resources for reception of PDSCH or PDSCH repetition overlap with at least one non-SBFD semi-static/dynamic UL symbol (or non-SBFD dynamic FL symbol).
  • Case 2 The symbols included in the resources for reception of the PDSCH or PDSCH repetitions do not overlap with non-SBFD semi-static/dynamic UL symbols (or non-SBFD dynamic FL symbols), but at least one SBFD semi-static/dynamic UL symbol , and/or overlap with at least one SBFD semi-static/dynamic DL symbol and/or at least one SBFD dynamic FL symbol.
  • the UE may operate according to Alt-A and/or Alt-B.
  • Alt-A if the symbols included in the PDSCH or the resources for reception of PDSCH repetition overlap with at least one non-SBFD semi-static/dynamic UL symbol (or non-SBFD dynamic FL symbol), the UE Alternatively, PDSCH repetition may not be received. That is, the UE may not receive PDSCH or PDSCH repetitions that overlap with UL symbols or FL symbols in non-SBFD operation.
  • a symbol included in the PDSCH or a resource for reception of PDSCH repetition is not received because it overlaps with at least one non-SBFD semi-static/dynamic UL symbol (or non-SBFD dynamic FL symbol). If the PDSCH or PDSCH repetition is one or any of multiple PDSCHs scheduled by a single DCI, the HPN (HARQ Process Number) for the PDSCH or PDSCH repetition is may be skipped. That is, the UE does not have to transmit HARQ-ACK for the PDSCH or PDSCH repetition.
  • HPN HARQ Process Number
  • Alt-B ⁇ Case 1: Alt-B>
  • the UE or assuming/judging/determining/that the PDSCH repetition is postponed to a slot in which the PDSCH or symbols of the time-domain resources for reception of the PDSCH repetition do not overlap with non-SBFD semi-static/dynamic UL symbols (or non-SBFD dynamic FL symbols). May be interpreted.
  • the UE may receive a PDSCH or PDSCH repetition that overlaps with a UL symbol or FL symbol in non-SBFD operation in any subsequent slot that does not overlap with a UL symbol or FL symbol in non-SBFD operation.
  • the UE may transmit the PDSCH or PDSCH repetition that overlaps with the UL symbol or FL symbol in non-SBFD operation to any subsequent symbol, subslot, or subframe that does not overlap with the UL symbol or FL symbol in non-SBFD operation.
  • frame, etc. may be received in any time unit.
  • ⁇ Case 2 Alt 0> With Alt 0, the UE specifies that the symbols included in the resources for reception of the PDSCH or PDSCH repetitions do not overlap with non-SBFD semi-static/dynamic UL symbols (or non-SBFD dynamic FL symbols), but 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 may not be assumed/judged/determined.
  • the gNB does not overlap with non-SBFD semi-static/dynamic UL symbols (or non-SBFD dynamic FL symbols), but includes at least one SBFD semi-static/dynamic UL symbol, at least one SBFD semi-static/dynamic DL symbol, and /Or, no PDSCH or PDSCH repetitions may be transmitted that overlap with at least one SBFD dynamic FL symbol.
  • 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 are counted in the number of repetitions. It may be counted, or it may not be counted.
  • the PDSCH is not received due to overlap with the SBFD semi-static/dynamic UL symbol, the SBFD semi-static/dynamic DL symbol, and/or the SBFD dynamic FL symbol, and If the PDSCH or PDSCH repetition is one or any of multiple PDSCHs scheduled by a single DCI, the HPN may or may not be skipped for the PDSCH or PDSCH repetition. It's okay. That is, the UE does not need to transmit HARQ-ACK for the PDSCH or PDSCH repetition, or may transmit it.
  • ⁇ Case 2 Alt 1-2>>
  • the symbols included in the resources for reception of the PDSCH or PDSCH repetitions do not overlap with non-SBFD semi-static/dynamic UL symbols (or non-SBFD dynamic FL symbols), but at least one SBFD semi-static/dynamic When overlapping with a dynamic UL symbol, at least one SBFD semi-static/dynamic DL symbol, and/or at least one SBFD dynamic FL symbol, the UE, regardless of whether there is an overlap with the UL subband,
  • the resources of the PDSCH or PDSCH repetition do not overlap with non-SBFD semi-static/dynamic UL symbols (or non-SBFD dynamic FL symbols), SBFD semi-static/dynamic UL symbols, SBFD semi-static/dynamic DL symbols, and/or It may be assumed/determined/determined/interpreted that the PDSCH or PDSCH repetition is postponed to a slot that does not overlap with the SBFD dynamic FL symbol.
  • the UE receives the PDSCH or PDSCH repetition in any subsequent slot that does not overlap with UL symbols or FL symbols in non-SBFD operation and does not overlap with UL symbols or DL symbols in SBFD operation. You can do it like this. That is, the gNB transmits the PDSCH or PDSCH repetition in any subsequent 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. You can do it like this. Note that the UE does not overlap with UL symbols or FL symbols in non-SBFD operation, or any subsequent symbols, subslots, subframes, frames, etc. that do not overlap with UL symbols or DL symbols in SBFD operation.
  • the PDSCH or PDSCH repetition may be received in any time unit.
  • the postponement may be executed when the SBFD operation instruction is set by RRC.
  • deferral may not apply. That is, if the UE is dynamically notified of SBFD operation, the UE may not receive the PDSCH or PDSCH repetition.
  • the SBFD operation is notified to the UE by the DCI, the UE may use the SBFD UL symbol, the SBFD DL symbol, and/or the SBFD FL A PDSCH or PDSCH repetition that overlaps with a symbol may not be received in any time unit such as a subsequent symbol, subslot, slot, subframe, or frame.
  • the UE specifies that the symbols included in the resources for reception of PDSCH or PDSCH repetition are symbols other than SBFD semi-static/dynamic UL symbols, SBFD semi-static/dynamic DL symbols, and/or SBFD dynamic FL symbols. It may be assumed/determined/determined/interpreted that the rate matching is performed on the above. That is, the gNB may transmit rate matched PDSCH or PDSCH repetitions on symbols other than SBFD semi-static/dynamic UL symbols, SBFD semi-static/dynamic DL symbols, and/or SBFD dynamic FL symbols.
  • the HPN is not skipped for the relevant PDSCH or PDSCH repetition. may be skipped. That is, the UE may or may not transmit HARQ-ACK for the PDSCH or PDSCH repetition.
  • the symbols included in the resources for reception of the PDSCH or PDSCH repetitions do not overlap with non-SBFD semi-static/dynamic UL symbols (or non-SBFD dynamic FL symbols), but at least one SBFD semi-static/dynamic A symbol that overlaps with a UL symbol, at least one SBFD semi-static/dynamic DL symbol, and/or at least one SBFD dynamic FL symbol and is included in the resources for reception of the PDSCH or PDSCH repetition.
  • SBFD semi-static/dynamic UL symbol, SBFD semi-static/dynamic DL symbol, and/or SBFD dynamic FL symbol You may also receive
  • the resource may be defined by specifications, semi-statically configured by RRC settings, dynamically notified by DCI notification, or determined according to rules. Further, the resource may be specified, configured, notified, or determined explicitly or implicitly.
  • the HPN is not skipped for the relevant PDSCH or PDSCH repetition. It's okay. That is, the UE may transmit HARQ-ACK for the PDSCH or PDSCH repetition.
  • the symbols included in the resources for reception of the PDSCH or PDSCH repetitions do not overlap with non-SBFD semi-static/dynamic UL symbols (or non-SBFD dynamic FL symbols), but at least one SBFD semi-static/dynamic UL symbol; If the symbol overlaps with at least one SBFD semi-static/dynamic DL symbol and/or at least one SBFD dynamic FL symbol and is included in the resources for reception of PDSCH or PDSCH repetition,
  • the UE shall perform the following Alt 2-0, Alt 2-1, Alt 2- 2, and/or Alt 2-3.
  • Alt 2-0>> the UE specifies that the symbols included in the resources for reception of the PDSCH or PDSCH repetitions do not overlap with non-SBFD semi-static/dynamic UL symbols (or non-SBFD dynamic FL symbols), but at least one SBFD overlaps with a semi-static/dynamic UL symbol, at least one SBFD semi-static/dynamic DL symbol, and/or at least one SBFD dynamic FL symbol, and in resources for reception of PDSCH or PDSCH repetition. Cases in which included symbols overlap with UL subbands in SBFD semi-static/dynamic UL symbols, SBFD semi-static/dynamic DL symbols, and/or SBFD dynamic FL symbols may not be assumed/determined/determined. .
  • the gNB does not overlap with non-SBFD semi-static/dynamic UL symbols (or non-SBFD dynamic FL symbols), but with SBFD semi-static/dynamic UL symbols, SBFD semi-static/dynamic DL symbols, and/or SBFD dynamic FL symbols.
  • PDSCHs or PDSCH repetitions that overlap with UL subbands in a symbol may not be transmitted.
  • the UE may not receive the PDSCH or PDSCH repetitions if the good. That is, the UE may not receive PDSCHs or PDSCH repetitions that overlap with UL subbands in UL symbols, DL symbols, or FL symbols in SBFD operation.
  • 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 are repeated. It may or may not be counted.
  • the HPN may be skipped for the PDSCH or PDSCH repetition. Or, it may not be skipped. That is, the UE may not transmit the HARQ-ACK for the PDSCH or PDSCH repetition, or may transmit it.
  • the HPN may not be skipped for the PDSCH or PDSCH repetition. good. That is, the UE may transmit HARQ-ACK for the PDSCH or PDSCH repetition.
  • ⁇ Case 2 Alt 2-3>>
  • the symbols included in the resources for reception of the PDSCH or PDSCH repetitions do not overlap with non-SBFD semi-static/dynamic UL symbols (or non-SBFD dynamic FL symbols), but at least one SBFD semi-static/dynamic Symbols that overlap with a dynamic UL symbol, at least one SBFD semi-static/dynamic DL symbol, and/or at least one SBFD dynamic FL symbol and are included in the resources for reception of the PDSCH or PDSCH repetition overlaps with the UL subband in the SBFD semi-static/dynamic UL symbol, the SBFD semi-static/dynamic DL symbol, and/or the SBFD dynamic FL symbol
  • the UE determines that the resources of the PDSCH or PDSCH repetition are non-SBFD semi-static Does not overlap with static/dynamic UL symbols (or non-SBFD dynamic FL symbols) and with any UL subbands in SBFD semi-static/dynamic UL symbols, SBFD semi-static/dynamic DL symbols, and/or
  • the PDSCH or PDSCH repetition is postponed to a non-overlapping slot. That is, in any subsequent slot that does not overlap with UL symbols or FL symbols in non-SBFD operation, and does not overlap with UL subbands in UL symbols, DL symbols, and/or FL symbols in SBFD operation, , the PDSCH or PDSCH repetition may be received.
  • the UE detects any subsequent symbol that does not overlap with the UL symbol or FL symbol in non-SBFD operation, and does not overlap with the UL subband in the UL symbol, DL symbol, and/or FL symbol in SBFD operation. , subslot, subframe, frame, etc., the PDSCH or PDSCH repetition may be received.
  • the postponement may be executed when the SBFD operation instruction is set by RRC.
  • the postponement may be executed when the SBFD operation instruction is set by RRC.
  • deferral may not apply. That is, if the UE is dynamically notified of SBFD operation, the UE may not receive the PDSCH or PDSCH repetition.
  • the UE will not overlap any of the non-SBFD UL symbols (or non-SBFD dynamic flexible symbols), but the SBFD UL symbols, SBFD DL symbols, and/or , SBFD
  • the PDSCH or PDSCH repetition that overlaps with the UL subband in the FL symbol may not be received in any time unit of subsequent symbols, subslots, subframes, frames, etc.
  • Alts to apply may be specified explicitly or implicitly by the specifications, may be semi-statically set by RRC, or may be dynamically notified by DCI. However, it may also be determined by rules. For example, a parameter instructing which Alt to apply may be transmitted in at least one of RRC, DCI, and MAC CE (Medium Access Control Element).
  • TBS Transport Block Size
  • TBS may be determined according to Option A and/or Option B below.
  • the TBS is i) non-SBFD semi-static/dynamic UL symbols (and non-SBFD dynamic FL symbols); ii) SBFD semi-static/dynamic UL symbols, SBFD semi-static/dynamic DL symbols, and/or SBFD dynamic FL symbols; and/or iii) UL resource blocks (RBs) in SBFD semi-static/dynamic UL symbols, SBFD semi-static/dynamic DL symbols, and/or SBFD dynamic FL symbols; may be determined based on the number of resource elements (REs) after excluding.
  • REs resource elements
  • the TBS may be determined based on the number of REs signaled by time domain resource allocation (TDRA) and frequency domain resource allocation (FDRA).
  • TDRA time domain resource allocation
  • FDRA frequency domain resource allocation
  • the number of REs for TBS calculation may be different for different repetitions.
  • the TBS of each repetition is determined by the TBS calculated for the first PDSCH repetition and/or the maximum/minimum/average of the TBS values calculated for all repetitions. may be determined.
  • Which option to apply may be specified explicitly or implicitly by the specification, may be set semi-statically by RRC, may be dynamically notified by DCI, or may be determined by rules. may be determined.
  • a parameter indicating which option to apply may be sent in at least one of RRC, DCI, and MAC CE.
  • the UE may receive configuration information regarding Option A and Option B through RRC, and may be dynamically notified by DCI as to which of Option A and Option B should be applied.
  • the UE determines whether the uplink time unit in non-time frequency division duplex operation and/or the time unit in time frequency division duplex operation and the downlink data channel overlap.
  • the receiving operation of the link data channel may be controlled and the receiving operation of the downlink data channel may be performed by the controlled receiving operation.
  • time frequency division duplexing may be SBFD
  • the uplink time unit in non-time frequency division duplexing operation may be a UL symbol, slot, any other time unit, etc. in non-SBFD operation.
  • it may be a non-SBFD semi-static/dynamic UL symbol and/or a non-SBFD dynamic FL symbol.
  • the time unit in the time frequency division duplex operation may be a UL, DL or FL symbol, slot, or any other time unit in the SBFD operation.
  • the downlink data channel may be, for example, PDSCH, PDSCH repetition, etc.
  • the UE may not receive the downlink data channel when the downlink data channel overlaps with the uplink time unit or flexible time unit in non-time frequency division duplex operation.
  • the UE The downlink data channel may be received in time units that do not overlap with the link time units. That is, the UE may assume/judge/determine/interpret that the PDSCH or PDSCH repetition is postponed to a slot where the time domain resources of the PDSCH or PDSCH repetition do not overlap with non-SBFD semi-static/dynamic UL symbols.
  • the UE when the downlink data channel overlaps the time unit in the time frequency division duplex operation, the UE shall determine whether the downlink data channel overlaps the uplink subband in the time unit or not. , may control the reception operation of the downlink data channel. For example, the UE may not assume/determine/interpret that the downlink data channel overlaps the time units in the SBFD operation. Also, the UE may not receive downlink data channels. Alternatively/in addition, the UE may determine that the downlink data channel does not overlap with uplink time units or flexible time units in non-SBFD operation, and that the downlink data channel does not overlap with uplink time units or flexible time units in non-SBFD operation; The downlink data channel may be received in time units that do not overlap.
  • the UE determines whether the resources of the PDSCH or PDSCH repetition do not overlap with non-SBFD semi-static/dynamic UL symbols, and the SBFD semi-static/dynamic UL symbols, the SBFD semi-static/dynamic DL symbols, and/or the SBFD dynamic It may be assumed/determined/determined/interpreted that the PDSCH or PDSCH repetition is postponed for time units such as slots that do not overlap with FL symbols. Alternatively/in addition, the UE may assume/determine/determine/interpret that the downlink data channel is rate matched on time units other than time units in SBFD operation.
  • the UE assumes/determines that the PDSCH or PDSCH repetition is rate matched on symbols other than SBFD semi-static/dynamic UL symbols, SBFD semi-static/dynamic DL symbols, and/or SBFD dynamic FL symbols. /decide/interpret.
  • the UE determines whether the downlink data channel overlaps the uplink subband in the time unit. may control the reception operation of the downlink data channel. For example, if the downlink data channel does not overlap with the uplink subband in the time unit, the UE may receive the downlink data channel on the configured/informed resource. Also, the UE may not assume/judge/determine/interpret that the downlink data channel overlaps the uplink subband in the time unit. Also, the UE may not receive downlink data channels.
  • the UE may assume/determine/determine/interpret that the downlink data channel is rate matched on the DL subband in time units in SBFD operation. Alternatively/in addition, the UE may determine that the downlink data channel does not overlap with uplink time units or flexible time units in non-SBFD operation, and that the downlink data channel does not overlap with uplink time units or flexible time units in non-SBFD operation; The downlink data channel may be received in time units such as slots that do not overlap with the downlink data channel.
  • the UE determines whether the PDSCH or PDSCH repetition resources do not overlap with non-SBFD semi-static/dynamic UL symbols, and the SBFD semi-static/dynamic UL symbol, the SBFD semi-static/dynamic DL symbol, and/or the SBFD dynamic It may be assumed/determined/determined/interpreted that the PDSCH or PDSCH repetition is postponed for time units such as slots that do not overlap with FL symbols.
  • the gNB controls the transmission operation of the downlink data channel in uplink time units in non-time frequency division duplex operation and/or in time units in time frequency division duplex operation, and downlink data channel by controlled transmission operation.
  • a link data channel transmission operation may be performed.
  • time frequency division duplexing may be SBFD
  • the uplink time unit in non-time frequency division duplexing operation may be a UL symbol, slot, any other time unit, etc. in non-SBFD operation.
  • it may be a non-SBFD semi-static/dynamic UL symbol and/or a non-SBFD dynamic FL symbol.
  • time unit in SBFD operation may be a UL, DL or FL symbol, slot, or any other time unit in SBFD operation, and specifically, SBFD semi-static/dynamic UL symbol, SBFD semi- It may be a static/dynamic DL symbol and/or an SBFD dynamic FL symbol.
  • the downlink data channel may be, for example, PDSCH, PDSCH repetition, etc.
  • UE capability information may be defined that indicates whether the UE supports PDSCH enhancement for time frequency division duplex operation. Also, UE capability information regarding PDSCH transmission for time frequency division duplexing such as SBFD operation may be defined. If the UE supports PDSCH enhancement for time frequency division duplex operation, the UE may send UE capability information to the gNB indicating that it supports PDSCH enhancement for time frequency division duplex operation. Upon receiving the UE capability information, the gNB may transmit the enhanced PDSCH for time frequency division duplex operation to the UE and cause the UE to perform the enhanced PDSCH reception operation for time frequency division duplex operation. can.
  • PDSCH enhancement for time frequency division duplexing operations such as SBFD operations can be realized.
  • Proposal 2 In Proposal 2, other PDSCH enhancements for time-frequency division duplexing operations, such as SBFD operations, are described. Specifically, PDSCH m-TRP FDM is extended for SBFD operation as follows. Case 1: When PDSCH resources overlap with non-SBFD UL symbols ⁇ Alt-A> The UE assumes that no PDSCH is transmitted. ⁇ Alt-B> The UE assumes that the transmission of the PDSCH has been postponed. Case 2: When PDSCH resources overlap with SBFD symbols ⁇ Alt 1> The UE operates as follows regardless of whether there is overlap with the UL subband. ⁇ Alt 1-1> The UE does not receive PDSCH.
  • ⁇ Alt 1-2>> The UE assumes that the transmission of the PDSCH has been deferred to non-SBFD DL resources. ⁇ Alt 1-3>> The UE assumes that the PDSCH is rate matched to resources other than SBFD symbols. ⁇ Alt 2> The UE operates as follows depending on whether there is overlap with the UL subband. If the PDSCH does not overlap with the UL subband, the UE receives the PDSCH. On the other hand, if the PDSCH overlaps the UL subband, the UE operates as follows. ⁇ Alt 2-0>> The UE does not assume this case. ⁇ Alt 2-1>> The UE does not receive PDSCH.
  • Case 1 For frequency division multiplexed PDSCH of s-DCI-based m-TRP, ie, s-DCI-based m-TRP PDSCH according to fdmSchemeA or fdmSchemeB, the following cases 1 and 2 may be considered.
  • Case 1 The symbols included in the time-domain resources for reception of two PDSCH occasions or repetitions overlap with at least one non-SBFD semi-static/dynamic UL symbol (or non-SBFD dynamic FL symbol) (see Figure 16) ).
  • Case 2 The symbols included in the time-domain resources for reception of two PDSCH occasions or repetitions do not overlap with non-SBFD semi-static/dynamic UL symbols (or non-SBFD dynamic FL symbols) and 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 (see FIG. 17).
  • Alt-A In Alt-A, the UE receives two PDSCH occasions or repetitions in which the symbols included in the time-domain resources overlap with at least one non-SBFD semi-static/dynamic UL symbol (or non-SBFD dynamic FL symbol). There is no need to assume/judge/determine/interpret. That is, the gNB may avoid transmitting two PDSCH occasions or repetitions where the symbols included in the time-domain resources overlap with at least one non-SBFD semi-static/dynamic UL symbol (or non-SBFD dynamic FL symbol). .
  • Alt-B the UE receives two PDSCH opportunities or two slots in which the symbols included in the time-domain resources for repeated reception do not overlap with non-SBFD semi-static/dynamic UL symbols (or non-SBFD dynamic flexible symbols). It may be assumed/determined/determined/interpreted that one PDSCH opportunity or repetition is postponed. That is, the UE may receive the PDSCH opportunity or repetition in any subsequent slot that does not overlap with UL or FL symbols in non-SBFD operation.
  • the symbols included in the time-domain resources for two PDSCH occasions or repeated receptions do not overlap with non-SBFD semi-static/dynamic UL symbols (or non-SBFD dynamic FL symbols) and have at least one When overlapping with an 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 use the following Alt 1 and/or Alt It may operate according to 2.
  • the gNB specifies that the symbols included in the time-domain resource do not overlap with non-SBFD semi-static/dynamic UL symbols (or non-SBFD dynamic FL symbols), at least one SBFD semi-static/dynamic UL symbol, at least one SBFD Two PDSCH occasions or repetitions that overlap with a semi-static/dynamic DL symbol and/or at least one SBFD semi-static/dynamic FL symbol may not be transmitted.
  • the symbols included in the time-domain resources for two PDSCH occasions or repeated receptions from TRP #1 and TRP #2 overlap with the UL symbols in SBFD operation, so the received It doesn't have to be done.
  • the UE specifies that the symbols included in the time-domain resources for reception of two PDSCH occasions or repetitions do not overlap with non-SBFD semi-static/dynamic UL symbols (or non-SBFD dynamic flexible symbols) and Assuming/determining that two PDSCH opportunities or repetitions are deferred in slots that do not overlap with semi-static/dynamic UL symbols, SBFD semi-static/dynamic DL symbols, and/or SBFD semi-static/dynamic FL symbols. May be determined/interpreted.
  • the UE may use the PDSCH opportunity or repetition in any subsequent slot that does not overlap with UL symbols or FL symbols in non-SBFD operation and does not overlap with UL symbols, DL symbols, and/or FL symbols in SBFD operation. may be received.
  • the UE may use non-SBFD semi-static/dynamic UL symbols (or non-SBFD dynamic flexible symbols) that do not overlap, SBFD semi-static/dynamic UL symbols, SBFD semi-static/dynamic DL symbols, and/or SBFD semi-static /The PDSCH opportunity or repetition may be received in any time unit of any subsequent symbol, subslot, subframe, frame, etc. that does not overlap with the dynamic FL symbol.
  • the postponement may be executed when the SBFD operation instruction is set by RRC.
  • the postponement may be executed when the SBFD operation instruction is set by RRC.
  • deferral may not apply. That is, if the UE is dynamically notified of SBFD operation, the UE may not assume/judge/determine/interpret that a PDSCH opportunity or repetition will be sent.
  • ⁇ Case 2 Alt 1-3>>
  • the UE specifies that the symbols included in the time-domain resources for PDSCH opportunity or repeated reception are SBFD semi-static/dynamic UL symbols, SBFD semi-static/dynamic DL symbols, and/or SBFD dynamic FL symbols. It may be assumed/judged/determined/interpreted that rate matching is performed on the excluded symbols. That is, the UE indicates that the gNB transmits rate-matched PDSCH opportunities or repetitions in symbols other than SBFD semi-static/dynamic UL symbols, SBFD semi-static/dynamic DL symbols, and/or SBFD semi-static/dynamic FL symbols. You may assume/judge/determine/interpret that there is.
  • TBS Transport Block Size
  • TBS may be determined according to Option A and/or Option B below.
  • the TBS is determined based on the number of symbols after excluding the SBFD semi-static/dynamic UL symbols, SBFD semi-static/dynamic DL symbols, and/or SBFD dynamic FL symbols from the symbols signaled by the TDRA. It's okay.
  • the TBS may be determined based on the number of symbols signaled by the TDRA.
  • the number of symbols for TBS calculation may be different for different repetitions.
  • the TBS of each repetition is determined by the TBS calculated for the first PDSCH repetition and/or by the maximum/minimum/average of the TBS values calculated for all repetitions. may be determined.
  • Which option to apply may be specified explicitly or implicitly by the specification, may be set semi-statically by RRC, may be dynamically notified by DCI, or may be determined by rules. may be determined.
  • a parameter indicating which option to apply may be sent in at least one of RRC, DCI, and MAC CE.
  • the UE may receive configuration information regarding Option A and Option B through RRC, and may be dynamically notified by DCI as to which of Option A and Option B should be applied.
  • the allocated physical resource block (PRB) notified by the FDRA is a UL sub-block 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 determines the resource block (RB) for each TRP and receives two PDSCH opportunities or repetitions on the advertised/configured resources, similar to Rel-16. good.
  • the resources may be defined by specifications, semi-statically configured by RRC settings, dynamically notified by DCI notifications, or determined according to rules. Further, the resource may be specified, configured, notified, or determined explicitly or implicitly.
  • the UE may operate according to the following Alt 2-0, Alt 2-1, Alt 2-2, Alt 2-3, Alt 2-4 and/or Alt 2-5.
  • PRBs physical resource blocks
  • Alt 2-0>> the UE specifies that the symbols included in the time-domain resources for reception of two PDSCH occasions or repetitions do not overlap with non-SBFD semi-static/dynamic UL symbols (or non-SBFD dynamic FL symbols) and
  • the assigned PRB that overlaps with the semi-static/dynamic UL symbol, SBFD semi-static/dynamic DL symbol, and/or SBFD semi-static/dynamic FL symbol and notified by FDRA is the SBFD semi-static/dynamic UL symbol, SBFD It may be possible not to assume/judge/determine/interpret the case of overlapping with the UL subband in the semi-static/dynamic DL symbol and/or the SBFD semi-static/dynamic FL symbol.
  • the gNB has time domain resources that do not overlap with non-SBFD semi-static/dynamic UL symbols (or non-SBFD dynamic FL symbols), SBFD semi-static/dynamic UL symbols, SBFD semi-static/dynamic DL symbols, and/or , in the SBFD semi-static/dynamic UL symbol, the SBFD semi-static/dynamic DL symbol, and/or the SBFD semi-static/dynamic FL symbol for two PDSCH occasions or repetitions that overlap with the SBFD semi-static/dynamic FL symbol.
  • PRBs may be allocated by FDRA so as not to overlap with UL subbands.
  • ⁇ Case 2 Alt 2-1>>
  • no PDSCH opportunities or repetitions for the two TCI states may be received. That is, the symbols included in the time-domain resources for reception of two PDSCH occasions or repetitions do not overlap with non-SBFD semi-static/dynamic UL symbols (or non-SBFD dynamic FL symbols) and 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 the allocated PRB notified by FDRA is a SBFD
  • the UE may receive PDSCH opportunities or repetitions for two TCI states. You may choose not to receive it.
  • PDSCH opportunities or repetitions may be postponed to slots that do not overlap with any UL subbands in the SBFD semi-static/dynamic DL symbol and/or the SBFD semi-static/dynamic FL symbol. That is, the UE determines that the symbols included in the PDSCH opportunity or resource for repeated reception do not overlap with UL symbols or FL symbols in non-SBFD operation, and that the symbols included in the resources for reception of the PDSCH opportunity or repetition do not overlap with UL symbols or FL symbols in SBFD operation.
  • the UE may determine that the symbols included in the resource for reception of the PDSCH opportunity or repetition do not overlap with non-SBFD semi-static/dynamic UL symbols (or non-SBFD dynamic flexible symbols), and the SBFD semi-static/dynamic UL symbols In any time unit of any subsequent symbol, subslot, subframe, frame, etc. that does not overlap with any UL subband in the SBFD semi-static/dynamic DL symbol and/or the SBFD dynamic FL symbol, the relevant A PDSCH or PDSCH repetition may be received.
  • the postponement may be executed when the SBFD operation instruction is set by RRC.
  • deferral may not apply. That is, if the UE is dynamically notified of SBFD operation, the UE may not receive PDSCH opportunities or repetitions.
  • the UE may not overlap any of the non-SBFD UL symbols (or non-SBFD dynamic FL symbols), but the SBFD UL symbols, SBFD DL symbols, and/or , SBFD.
  • PDSCH opportunities or repetitions that overlap with UL subbands in FL symbols may not be received in subsequent symbols, slots, etc.
  • the PRB allocation for each TCI state follows Rel-16 rules and the UE may drop PDSCH opportunities or repetitions that overlap with the UL subband. For example, after determining the RB allocation for each TCI state (according to Rel-16 rules), no PDSCH opportunities or repetitions that overlap with the UL subband are received, and no PDSCH opportunities or repetitions that overlap with the UL subband are received. may be sent (if present). For example, in the example shown in FIG. 18, no PDSCH opportunity or repetition of TRP #2 that overlaps with the UL subband is received, and a PDSCH opportunity or repetition of TRP #1 that does not overlap with the UL subband is received.
  • TBS may be determined as follows.
  • the TBS may be determined based on the number of transmitted PDSCH opportunities or repeated PRBs. In other words, PDSCH opportunities or repeating PRB numbers that overlap with the UL subband may be excluded for TBS calculation.
  • the TBS may be determined similarly to Rel-16.
  • ⁇ Case 2 Alt 2-4>>
  • PRB allocation for each TCI state follows Rel-16 rules, and PDSCH opportunities or repetitions that overlap with UL subbands may be rate matched on DL resource blocks.
  • the PDSCH opportunities or repetitions that overlap with the UL subband are determined on the DL RB of the RB determined for the TCI state.
  • PDSCH opportunities or repetitions that may be rate matched and do not overlap with the UL subbands (if any) may be transmitted on the RB determined for the TCI condition. For example, in the example shown in FIG.
  • the PDSCH opportunity or repetition resource of TRP #1 is rate matched on the DL subband of the lower frequency band
  • the PDSCH opportunity or repetition resource of TRP #2 is rate matched on the DL subband of the lower frequency band.
  • Rate matching may be performed on the DL subband of the frequency band.
  • TBS may be determined as follows.
  • the TBS may be determined based on two PDSCH opportunities or the total number of repeating DL RBs.
  • the TBS may be determined similarly to Rel-16 in option A (i.e., as the number of REs in the first TCI state based on the advertised FDRA and TDRA) and in option B. may be determined based on the actual number of REs in the first/second TCI state (i.e.
  • the determination is based on the greater/lesser/average value of the actual number of REs in the 1st/2nd TCI state (i.e. after excluding the UL RBs in the 1st/2nd TCI state) may be done.
  • which of options A to C to apply is determined by the specifications, semi-statically set by RRC settings, dynamically notified by DCI notifications, or determined according to rules. good. Further, which of options A to C is applied may be explicitly or implicitly prescribed, set, notified, or determined. .
  • a parameter indicating which option to apply may be sent in at least one of RRC, DCI, and MAC CE.
  • the UE may receive configuration information regarding options A to C through RRC, and may be dynamically notified by DCI of which of options AC to apply.
  • the PRB assignment for each TCI state may be based on the DL subband of each symbol after excluding the UL subband. Specifically, for each symbol, the DL RB number of the symbol may be assigned to two TCI states after excluding the UL subband in that symbol. For example, the first PRBs are assigned to the first TCI state and the remaining PRBs may be assigned to the second TCI state.
  • n PRB is Assuming that is the number of DL RBs in a symbol, is the total number of PRBs allocated to the UE.
  • Alt 2-0 to Alt 2-5 may depend on whether the SBFD operation (DL/UL subband allocation) is dynamically notified or RRC configured. For example, Alt 2-3 may be applied if the SBFD operation (DL/UL subband allocation) is dynamically notified by DCI, and the SBFD operation (DL/UL subband allocation) is notified semi-statically by RRC. If set, Alt 2-5 may be applied. For example, which of Alt 2-0 to Alt 2-5 to apply is determined by the specifications, semi-statically set by RRC settings, dynamically notified by DCI notification, etc., or by rules. may be determined according to Further, which one of Alt 2-0 to Alt 2-5 to apply may be explicitly or implicitly defined, set, notified, or determined. For example, a parameter indicating which Alt to apply may be transmitted in at least one of RRC, DCI, and MAC CE (Medium Access Control Element).
  • RRC Radio Resource Control Element
  • the UE is notified/configured for SBFD operation for the serving cell/Bandwidth Part (BWP), and at the same time any TCI code point (at least one code point) is in two TCI states in the serving cell/BWP. /QCL may not be assumed/judged/determined/interpreted.
  • the UE is notified/configured for SBFD operation for the serving cell/Bandwidth Part (BWP) and at the same time any TCI code point (at least one code point) is in two TCI states in the serving cell/BWP. /QCL and at the same time, the UE does not have to assume/judge/determine/interpret that the repetitionScheme is set in the upper layer parameter FDMSchemeA.
  • BWP serving cell/Bandwidth Part
  • the UE is notified/configured for SBFD operation for the serving cell/Bandwidth Part (BWP), and at the same time any TCI code point (at least one code point) is in two TCI states in the serving cell/BWP. /QCL and at the same time, the UE does not have to assume/judge/determine/interpret that the repetitionScheme is set in the upper layer parameter FDMSchemeB.
  • BWP serving cell/Bandwidth Part
  • the UE is notified/configured for SBFD operation for the serving cell/Bandwidth Part (BWP), and at the same time any TCI code point (at least one code point) is in two TCI states in the serving cell/BWP. /QCL and at the same time, the UE does not have to assume/judge/determine/interpret that the repetitionScheme is set in the upper layer parameter TDMSchemeA.
  • BWP serving cell/Bandwidth Part
  • the UE is notified/configured for SBFD operation for the serving cell/Bandwidth Part (BWP), and at the same time any TCI code point (at least one code point) is in two TCI states in the serving cell/BWP. /QCL and at the same time, it is not necessary to assume/judge/determine/interpret that the upper layer parameter repetitionNumber is set in the UE.
  • BWP serving cell/Bandwidth Part
  • the UE is notified/configured of the SBFD operation for the serving cell/bandwidth part (BWP), and at the same time any CORESET (at least one CORESET) is configured/notified in the serving cell/BWP by the CORESETPoolID. There is no need to assume/judge/determine/interpret that.
  • the SBFD operation (and/or DL/UL subband allocation) is notified/configured for the serving cell/bandwidth part (BWP), and the DCI has two When reporting TCI code points mapped to TCI states/QCLs, the UE may only use the first/second TCI states/QCLs for PDSCH transmission.
  • BWP serving cell/bandwidth part
  • the SBFD operation (and/or DL/UL subband allocation) is notified/configured for the serving cell/bandwidth part (BWP), and the DCI has two
  • BWP serving cell/bandwidth part
  • the DCI has two
  • the UE is configured by the repetitionScheme configured in the upper layer parameter FDMSchemeA
  • the UE /Second TCI state/Only QCL may be used.
  • the SBFD operation (and/or DL/UL subband allocation) is notified/configured for the serving cell/bandwidth part (BWP), and the DCI has two If the TCI code point mapped to the TCI state/QCL is notified, and the UE is configured by the repetitionScheme configured in the upper layer parameter FDMSchemeB, the UE /Second TCI state/Only QCL may be used.
  • the SBFD operation (and/or DL/UL subband allocation) is notified/configured for the serving cell/bandwidth part (BWP), and the DCI has two
  • BWP serving cell/bandwidth part
  • the SBFD operation (and/or DL/UL subband allocation) is notified/configured for the serving cell/bandwidth part (BWP), and the DCI has two When notifying the TCI code point mapped to the TCI state/QCL, and when the upper layer parameter repetitionNumber is set in the UE, the UE uses the first/second TCI for PDSCH transmission. Only status/QCL may be used.
  • time frequency division duplexing may be SBFD
  • the uplink time unit in non-time frequency division duplexing operation may be a UL symbol, slot, any other time unit, etc. in non-SBFD operation.
  • it may be a non-SBFD semi-static/dynamic UL symbol and/or a non-SBFD dynamic FL symbol.
  • the time unit in the time frequency division duplex operation may be a UL, DL or FL symbol, slot, or any other time unit in the SBFD operation.
  • the downlink data channel may be, for example, PDSCH, PDSCH repetition, etc.
  • the UE assumes/judges/determines that multiple opportunities for downlink data channels are not transmitted. / May be interpreted.
  • the UE may determine that the time-domain resources of the downlink data channel opportunities overlap with uplink time units in non-SBFD operation. Multiple opportunities for downlink data channels may be received in slots that do not overlap with the link time unit. That is, the UE may assume/determine/interpret that the PDSCH opportunity or repetition is postponed to a slot where the resources of the PDSCH opportunity or repetition do not overlap with non-SBFD semi-static/dynamic UL symbols.
  • the UE determines whether the multiple opportunities of downlink data channels overlap with the uplink subband in the time unit.
  • the receiving operation of the downlink data channel may be controlled regardless of the downlink data channel. For example, the UE may assume/determine/interpret that multiple downlink data channel opportunities will not be transmitted. Alternatively/in addition, the UE may determine that the downlink data channel opportunities do not overlap with uplink time units or flexible time units in non-SBFD operation, and that the downlink data channel opportunities do not overlap with uplink time units or flexible time units in non-SBFD operation, and , multiple opportunities for downlink data channels may be received in time units that do not overlap with the flexible time unit.
  • the UE determines that the PDSCH opportunities or repetition resources do not overlap with non-SBFD semi-static/dynamic UL symbols, and the SBFD semi-static/dynamic UL symbols, SBFD semi-static/dynamic DL symbols, and/or SBFD dynamic It may be assumed/determined/determined/interpreted that the PDSCH opportunity or repetition is postponed to a slot that does not overlap with the FL symbol. Alternatively/in addition, the UE may assume/determine/determine/interpret that multiple opportunities of downlink data channels are rate matched on time units other than time units in SBFD operation.
  • the UE assumes 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. /judge/decide/interpret.
  • the UE may determine whether the downlink data channel overlaps with the uplink subband in the time unit or not. , may control the reception operation of the downlink data channel. For example, if the assigned PRB signaled by the FDRA does not overlap with the UL subbands 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 determine the RB for each TRP similar to Rel-16 and receive multiple opportunities for downlink data channels on advertised/configured resources.
  • the UE may determine that the assigned PRB notified by the FDRA overlaps with the UL subbands in the SBFD semi-static/dynamic UL symbol, the SBFD semi-static/dynamic DL symbol, and/or the SBFD semi-static/dynamic FL symbol. There is no need to imagine/judge/determine/interpret cases. Alternatively/in addition, if the allocated PRB signaled by the FDRA overlaps with UL subbands 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 not receive downlink data channel opportunities for the two TCI states.
  • the downlink data channel opportunity resources do not overlap with non-SBFD semi-static/dynamic UL symbols, SBFD semi-static/dynamic UL symbols, SBFD semi-static/dynamic DL symbols, and/or SBFD semi-static / may be postponed to a time unit that does not overlap with any UL subband in the dynamic FL symbol.
  • the PRB assignment for each TCI state may follow Rel-16 rules and downlink data channel opportunities that overlap with the UL subband may be dropped.
  • the PRB assignment for each TCI state may be rate matched on the DL RB for downlink data channel opportunities that overlap with the UL subband according to Rel-16 rules.
  • the PRB assignment for each TCI state may be based on the DL subband of each symbol after exclusion of the UL subband.
  • the gNB controls the transmission operation of the downlink data channel in uplink time units in non-time frequency division duplex operations such as non-SBFD operations and/or in time units in time frequency division duplex operations such as SBFD operations.
  • the transmission operation of the downlink data channel may be performed by a controlled transmission operation.
  • time frequency division duplexing may be SBFD
  • the uplink time unit in non-time frequency division duplexing operation may be a UL symbol, slot, any other time unit, etc. in non-SBFD operation.
  • it may be a non-SBFD semi-static/dynamic UL symbol and/or a non-SBFD dynamic FL symbol.
  • the time unit in the time frequency division duplex operation may be a UL, DL or FL symbol, slot, or any other time unit in the SBFD operation.
  • the downlink data channel may be, for example, PDSCH, PDSCH repetition, etc.
  • UE Capability For PDSCH enhancement for time frequency division duplex operation, such as the SBFD operation described above, UE capability information may be defined indicating whether the UE supports s-DCI based m-TRP PDSCH enhancement for time frequency division duplex operation. . Additionally, UE capability information regarding multi-transmission/reception point PDSCH transmission for time frequency division duplexing such as SBFD operation may be defined. If it supports s-DCI-based MTRP PDSCH enhancement for time-frequency division duplex operation, the UE shall provide UE capability information indicating that it supports s-DCI-based MTRP PDSCH enhancement for time-frequency division duplex operation. It may also be sent to gNB.
  • the gNB Upon receiving the UE capability information, the gNB transmits an enhanced s-DCI-based MTRP PDSCH for time frequency division duplex operation to the UE and causes the UE to perform an enhanced PDSCH reception operation for SBFD operation. Can be done.
  • UE capability information indicating whether the UE supports s-DCI-based m-TRP PDSCH enhancement for time-frequency division duplexing operation with SFN/tdmSchemeA/tdmSchemeB (i.e., according to the configured number of repetitions)/fdmSchemeA/fdmSchemeB is provided. , may be specified. If the UE supports s-DCI-based m-TRP PDSCH enhancement for such time-frequency division duplex operation, the UE supports s-DCI-based m-TRP PDSCH enhancement for time-frequency division duplex operation. UE capability information indicating this may be transmitted to the gNB.
  • the gNB Upon receiving the UE capability information, the gNB transmits the enhanced s-DCI-based m-TRP PDSCH for time frequency division duplex operation to the UE and performs the enhanced PDSCH reception operation in time frequency division duplex operation.
  • the UE can be made to perform the following.
  • PDSCH enhancement for time frequency division duplexing operations such as SBFD operations can be realized.
  • frequency division multiplexed PDSCH opportunities or repeated reception operations by the UE in SBFD and non-SBFD operations may be defined.
  • Proposition 3 describes HARQ-ACK enhancement for time frequency division duplexing operations such as SBFD operations. Specifically, the HARQ-ACK CB for SPS PDSCH and the Type 1 HARQ-ACK CB are enhanced for SBFD operation as follows. About HARQ-ACK for SPS PDSCH ⁇ Alt 1> Regardless of SBFD operation or non-SBFD operation, if symbols included in the resource for SPS PDSCH reception overlap with semi-statically configured UL symbols, the UE shall use the SPS PDSCH to generate a HARQ-ACK CB. Exclude from That is, the HARQ-ACK bit for the SPS PDSCH may not be generated.
  • ⁇ Alt 4> Regardless of SBFD operation or non-SBFD operation, if the symbols included in the resources for receiving the SPS PDSCH overlap with semi-statically configured UL symbols or SBFD DL/FL symbols, the UE shall not use the relevant SPS PDSCH. Exclude from HARQ-ACK CB generation. That is, the HARQ-ACK bit for the SPS PDSCH may not be generated.
  • ⁇ Alt 5> If the symbols included in the resources for receiving the SPS PDSCH overlap with the semi-statically configured UL symbols or UL subbands reserved for non-SBFD operations, the UE uses the HARQ-ACK CB for the SPS PDSCH. Exclude from generation.
  • the HARQ-ACK bit for the SPS PDSCH may not be generated.
  • the UE does not exclude SPS PDSCH from HARQ-ACK CB generation when SBFD operation is performed.
  • Type 1 HARQ-ACK ⁇ Alt 1> Regardless of SBFD operation or non-SBFD operation, if 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 HARQ-ACK CB. That is, the HARQ-ACK bit for the SLIV of the PDSCH does not need to be generated.
  • ⁇ Alt 4> Regardless of SBFD operation or non-SBFD operation, if the SLIV of the PDSCH overlaps with the semi-statically configured UL symbol or the SBFD DL/FL symbol, the UE shall remove the SLIV of the PDSCH from the generation of HARQ-ACK CB. exclude. That is, the HARQ-ACK bit for the SLIV of the PDSCH does not need to be generated.
  • ⁇ Alt 5> If the SLIV of the PDSCH overlaps with a semi-statically configured UL symbol or UL subband reserved for non-SBFD operation, the UE excludes the SLIV of the PDSCH from the generation of the HARQ-ACK CB.
  • the UE does not exclude the SLIV of PDSCH from the generation of HARQ-ACK CB when SBFD operation is performed.
  • the UE can semi-statically/dynamically determine the HARQ-ACK codebook (which may also be referred to as HARQ-ACK size).
  • the HARQ-ACK codebook may be replaced with the PDSCH HARQ-ACK codebook, HARQ-ACK codebook size, HARQ-ACK bit number, etc.
  • SPS HARQ-ACK codebook For HARQ-ACK codebook generation for SPS, SPS PDSCH may be excluded according to Alt 1-6 below.
  • the symbols included in the SPS PDSCH or the resources for repeated reception of the SPS PDSCH overlap with at least one non-SBFD semi-static UL symbol, or are SBFD semi-static UL symbols, SBFD semi-static DL symbols , and/or the SPS PDSCH may be excluded when it overlaps with the UL subband in the SBFD semi-static FL symbol.
  • Alt 2 may be the most likely. Also, if SBFD operation (or DL/UL subband allocation) is dynamically notified, Alt 5/6 may be the most likely.
  • Alts to apply may be specified explicitly or implicitly by the specifications, may be semi-statically set by RRC, or may be dynamically notified by DCI. However, it may also be determined by rules. For example, a parameter indicating which Alt to apply may be transmitted in at least one of RRC, DCI, and MAC CE (Medium Access Control Element).
  • Type 1 HARQ-ACK codebook For the generation of the Type 1 HARQ-ACK codebook, for TDRA pruning, the SLIV (Start and Length Indicator Value) in candidate PDSCH slot n_D may be deleted according to Alts 1 to 6 below.
  • the Type 1 HARQ-ACK CB may be referred to as a semi-statically configured HARQ-ACK CB
  • the Type 2 HARQ-ACK CB may be referred to as a dynamically configured HARQ-ACK CB.
  • the HARQ-ACK CB may be replaced with the HARQ-ACK CB of the PDSCH, the HARQ-ACK CB size, the number of HARQ-ACK bits, etc.
  • Alt 2 may be the most likely. Also, if SBFD operation (or DL/UL subband allocation) is dynamically notified, Alt 5/6 may be the most likely.
  • Alts to apply may be specified explicitly or implicitly by the specifications, may be semi-statically set by RRC, or may be dynamically notified by DCI. However, it may be determined by rules. For example, a parameter instructing which Alt to apply may be transmitted in at least one of RRC, DCI, and MAC CE (Medium Access Control Element).
  • the notification may be notified for each component carrier, each cell group (CG), each PUCCH group, or each UE by upper layer signaling.
  • the UE determines (generates) HARQ-ACK information bits based on the determined HARQ-ACK codebook for each component carrier, each cell group (CG), each PUCCH group, or each UE, and transmits the generated HARQ-ACK may be transmitted using at least one of PUCCH and PUSCH.
  • N PDSCH repeat is the number of PDSCH repetitions.
  • the UE determines the HARQ-ACK codebook for the downlink data channel depending on whether the downlink data channel overlaps with the uplink time unit, and performs delivery acknowledgment according to the HARQ-ACK codebook. You can also send it.
  • the downlink data channel may be a PDSCH and/or a repetition of a PDSCH.
  • the uplink time unit may be a semi-statically set symbol, but may also be a slot, subframe, or frame.
  • the UE may exclude the SPS PDSCH from determining the HARQ-ACK codebook. Specifically, the UE determines how to generate the SPS HARQ-ACK CB depending on whether symbols included in the resources for reception of (each repetition of) the SPS PDSCH overlap with semi-static UL symbols. You may. For example, regardless of whether the SBFD operation or non-SBFD operation may be excluded from the generation of Additionally/or, the UE may exclude the SPS PDSCH from the generation of HARQ-ACK CB if the symbols included in the resources for reception of the SPS PDSCH overlap with semi-statically configured non-SBFD UL symbols. good.
  • the UE may exclude the SPS PDSCH from the generation of the HARQ-ACK CB if the symbols included in the resources for reception of the SPS PDSCH overlap with semi-statically configured UL symbols or UL subbands. It's okay. Additionally/or, the UE determines whether the symbols included in the resources for reception of the SPS PDSCH overlap with semi-statically configured UL symbols or SBFD DL/FL symbols, regardless of SBFD operation or non-SBFD operation. The SPS PDSCH may be excluded from the generation of HARQ-ACK CB.
  • the UE may receive the SPS PDSCH if symbols included in the resources for reception of the SPS PDSCH overlap with semi-statically configured UL symbols or UL subbands reserved for non-SBFD operations. It may be excluded from the generation of HARQ-ACK CB. That is, the HARQ-ACK bit for the SPS PDSCH does not need to be generated. Additionally/or, the UE may not exclude SPS PDSCH from HARQ-ACK CB generation when SBFD operation is performed.
  • 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 the semi-statically configured uplink symbols. Specifically, the UE may determine the method for generating Type 1 HARQ-ACK CB for each slot of the PDSCH, depending on whether the SLIV of the PDSCH overlaps with the semi-static UL symbol. . For example, regardless of SBFD operation or non-SBFD operation, if the SLIV of a PDSCH overlaps with a semi-statically configured UL symbol, the UE may exclude the SLIV of the PDSCH from the generation of HARQ-ACK CB. good.
  • the UE may exclude the SLIV of the PDSCH from the generation of the HARQ-ACK CB if the SLIV of the PDSCH overlaps with a semi-statically configured non-SBFD UL symbol. Additionally/or, the UE may exclude the SLIV of the PDSCH from the generation of the HARQ-ACK CB if the SLIV of the PDSCH overlaps with a semi-statically configured UL symbol or UL subband. Additionally/or, regardless of SBFD operation or non-SBFD operation, if the SLIV of the PDSCH overlaps with a semi-statically configured UL symbol or SBFD DL/FL symbol, the UE may HARQ-ACK the SLIV of the PDSCH.
  • the UE may remove the SLIV of the PDSCH from the generation of the HARQ-ACK CB. May be excluded. That is, the HARQ-ACK bit for the SLIV of the PDSCH does not need to be generated. Additionally/or, the UE may not exclude the SLIV of the PDSCH from the generation of HARQ-ACK CB when SBFD operation is performed.
  • the UE may also determine the HARQ-ACK codebook for the downlink data channel depending on whether the SBFD operation is semi-statically configured or dynamically notified.
  • the generation method of SPS HARQ-ACK CB and/or the generation method of Type 1 HARQ-ACK CB is either defined by the specifications, semi-statically set by RRC settings, or dynamically notified by DCI notification etc. or may be determined by the UE according to predetermined rules.
  • the method of generating the SPS HARQ-ACK CB and/or the method of generating the Type 1 HARQ-ACK CB may be explicitly or implicitly defined, configured, notified, or applied.
  • the parameters instructing the above-mentioned SPS HARQ-ACK CB generation method and/or Type 1 HARQ-ACK CB generation method are RRC, DCI, and MAC CE (Medium Access Control Element). t) transmitted in at least one of Good too.
  • the gNB transmits a downlink data channel and performs delivery acknowledgment according to the HARQ-ACK codebook for the downlink data channel determined depending on whether the downlink data channel overlaps with the uplink time unit or not. may be received.
  • the downlink data channel may be a PDSCH and/or a repetition of a PDSCH.
  • the uplink time unit may be a semi-statically set symbol, but may also be a slot, subframe, or frame.
  • UE Capability For HARQ-ACK enhancement for time-frequency division duplexing operations, such as the SBFD operation described above, UE capability information may be defined that indicates whether the UE supports HARQ-ACK enhancement for time-frequency division duplexing operations. Also, UE capability information regarding HARQ-ACK transmission for time frequency division duplexing such as SBFD operation may be defined. If the UE supports HARQ-ACK enhancement for time-frequency division duplex operation, the UE may send UE capability information to the gNB indicating that it supports HARQ-ACK enhancement for time-frequency division duplex operation. good. Upon receiving the UE capability information, the gNB may receive the HARQ-ACK CB for the PDSCH from the UE according to the HARQ-ACK enhancement for time frequency division duplex operation.
  • HARQ-ACK enhancement for time frequency division duplexing operations such as SBFD operations can be realized.
  • PUSCH in Rel-15/16/1-7 it is specified that PUSCH or PUSCH repetitions that overlap with semi-static DL symbols are not transmitted. That is, for the symbol set of the slot notified to the UE as a downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, the symbols included in the resources for transmission of PUSCH, PUCCH, PRACH, or SRS It is specified that the UE does not transmit the PUSCH, PUCCH, PRACH or SRS even when the PUSCH, PUCCH, PRACH or SRS partially overlaps with the symbol set of the slot in question.
  • tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated is the slot of these multiple slots.
  • at least one symbol of the symbol set for which the UE is scheduled to transmit PUSCH in the slot is a downlink symbol, it is specified that the UE does not transmit the PUSCH in the slot.
  • PUSCH or PUSCH repetition that overlaps with dynamic DL symbols/FL symbols is not transmitted. That is, the UE is configured by higher layers to transmit PUSCH, PUCCH, PRACH or SRS in a symbol set of a slot, and the UE is configured with a symbol subset from that symbol set as the downlink or flexible slot format. or the UE detects a DCI format 2_0 with a slot format value other than 255 that signals the UE to receive a PDSCH or CSI-RS in at least one symbol in the symbol set. If this is the case, and a predetermined condition is met, it is specified that the UE cancels PUSCH, PUCCH, PRACH, or SRS transmission in the symbol set.
  • Rel-15 NR supports single transmit/receive point (s-TRP) PUSCH with no repetition or slot-based PUSCH repetition, ie, PUSCH repetition type A.
  • s-TRP single transmit/receive point
  • PUSCH repetition type A For example, in slot-based PUSCH repetition, a PUSCH repetition may be transmitted over multiple slots, as shown in FIG. 21A.
  • Rel-16 NR supports single transmission/reception point (s-TRP) PUSCH with no repetition or subslot-based PUSCH repetition, ie, PUSCH repetition type B.
  • s-TRP single transmission/reception point
  • FIG. 21B shows Rel-15 slot-based PUSCH repetition and Rel-16 sub-slot-based PUSCH repetition in the case where the repetition factor K is 4 and the PUSCH length is 6. .
  • Rel-17 NR supports TDM m-TRP PUSCH repetition type A and type B.
  • cyclic and sequential mapping between two beam/power control parameter sets and repetitions are supported.
  • different beam/power control parameters can be set for the two TRPs for repetition #1 and repetition #3.
  • repetition type B using cyclic mapping different beam/power control parameters can be set for the two TRPs for repetition #1 and repetition #2. Note that for repetition type B, one nominal repetition is segmented into two actual repetitions at the slot boundary. Note that cyclic repetition type A and sequential repetition type B are also possible.
  • DCI 0_1 When scheduling multiple PUSCHs, DCI 0_1 is used as the DCI format. For example, as shown in FIG. 23, PUSCH #1 to #4 can be scheduled by one DCI. Here, it is specified that 120, 480, and 960 kHz SCS are supported, and the maximum number of PUSCHs that can be scheduled by one DCI is eight. Also, for TDRA, a separate ⁇ SLIV, mapping type, scheduling offset K2 ⁇ may be applied to each PUSCH in a row of the TDRA table. If a PUSCH collides with a semi-static DL symbol or an SSB symbol, the PUSCH will be canceled, but it is not expected that all PDSCHs will be canceled.
  • the MCS, NDI, and RV of the first TB field appear only once and are applied to the first TB of each PUSCH.
  • the HPN field applies to the first valid PUSCH, is incremented by 1 for subsequent PUSCHs, and is not incremented for invalid PUSCHs (i.e., PUSCHs that collide with semi-static DL symbols or SSB symbols). .
  • PUSCH reps #1 and #2 in PUSCH repetition are dropped.
  • SBFD operation since PUSCH rep #2 can be transmitted in the UL subband, it can be considered that the UE can transmit PUSCH rep #2.
  • Proposition 4 describes PUSCH enhancement for time frequency division duplex operations such as SBFD operations. Specifically, PUSCH repetition type A is enhanced for SBFD operation as follows. Case 1: When PUSCH resources overlap with non-SBFD DL symbols ⁇ Alt A> The UE does not transmit PUSCH. ⁇ Alt B> The UE postpones transmission of the PUSCH. Case 2: When PUSCH resource overlaps with SBFD symbol ⁇ Alt 1> The UE operates according to Alt 1-1 to 1-3 below, regardless of whether there is overlap with the DL subband. ⁇ Alt 1-1>> The UE does not transmit PUSCH.
  • Case 1 The symbols included in the resources for transmission of PUSCH or PUSCH repetition by repetition type A are at least one non-SBFD semi-static/dynamic DL symbol (or non-SBFD dynamic FL symbol), SSB symbol or type-0 CORESET symbol overlap with.
  • Case 2 The symbols included in the resources for transmission of PUSCH or PUSCH repetitions with repetition type A do not overlap with any non-SBFD semi-static/dynamic DL symbols (or non-SBFD dynamic FL symbols) and have at least one overlap with an 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 symbols included in the resources for transmission of PUSCH or PUSCH repetition by repetition type A are at least one non-SBFD semi-static/dynamic DL symbol (or non-SBFD dynamic FL symbol), SSB symbol or type- 0 CORESET symbols, the UE may operate according to Alt-A and/or Alt-B below.
  • the symbols included in the resources for transmission of PUSCH or PUSCH repetition by repetition type A are at least one non-SBFD semi-static/dynamic DL symbol (or non-SBFD dynamic FL symbol), SSB symbol or type-0 If it overlaps with the CORESET symbol, the UE may not transmit the PUSCH or PUSCH repetition. That is, the UE may not transmit PUSCH or PUSCH repetition that overlaps with DL symbols or FL symbols in non-SBFD operation.
  • the symbols included in the PUSCH or resources for transmission of PUSCH repetition are at least one non-SBFD semi-static/dynamic DL symbol (or non-SBFD dynamic FL symbol), an SSB symbol, or a type-0 CORESET symbol. If the relevant PUSCH or PUSCH repetition is one or any of multiple PUSCHs scheduled by a single DCI, for the relevant PUSCH or PUSCH repetition , HPN (HARQ Process Number) may be skipped.
  • HPN HARQ Process Number
  • the symbols included in the resources for transmission of PUSCH or PUSCH repetition with repetition type A are at least one non-SBFD semi-static/dynamic DL symbol (or non-SBFD dynamic FL symbol), SSB symbol or type-0 If the symbol overlaps with a CORESET symbol, the UE determines whether the symbol included in the resource for transmission of the PUSCH or PUSCH repetition is a non-SBFD semi-static/dynamic DL symbol (or a non-SBFD dynamic FL symbol), an SSB symbol, or a type-0 CORESET symbol.
  • the PUSCH or PUSCH repetition may be postponed to a slot/subslot that does not overlap with the symbol.
  • the UE may transmit a PUSCH or PUSCH repetition that overlaps with a DL symbol or FL symbol in non-SBFD operation in any subsequent slot/subslot that does not overlap with a DL symbol or FL symbol in non-SBFD operation. You may also do so.
  • the UE may transmit a PDSCH or PDSCH repetition that overlaps with a UL symbol or FL symbol in non-SBFD operation to any subsequent symbol, subslot, or subframe that does not overlap with a UL symbol or FL symbol in non-SBFD operation.
  • the information may be transmitted in any time unit such as a frame.
  • the symbols included in the resources for transmission of PUSCH or PUSCH repetitions by repetition type A do not overlap with any non-SBFD semi-static/dynamic DL symbols (or non-SBFD dynamic FL symbols); If overlapping 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 shall perform the following Alt 1 and/or Or it may operate according to Alt 2.
  • Alt 1 ⁇ Case 2: Alt 1>
  • the symbols included in the resources for transmission of PUSCH or PUSCH repetitions with repetition type A do not overlap with any non-SBFD semi-static/dynamic DL symbols (or non-SBFD dynamic FL symbols) and have at least one If the UE overlaps with 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, May operate with or without Alt 1-1, Alt 1-2 and/or Alt 1-3 below.
  • 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 are counted in the number of repetitions. It can be counted, or it doesn't have to be counted.
  • the PUSCH is not transmitted due to overlap with the SBFD semi-static/dynamic UL symbol, the SBFD semi-static/dynamic DL symbol, and/or the SBFD dynamic FL symbol, and , if the PUSCH or PUSCH repetition is one or any of a plurality of PUSCHs scheduled by a single DCI, the HPN may or may not be skipped for the PUSCH or PUSCH repetition. You don't have to.
  • ⁇ Case 2 Alt 1-2>>
  • the symbols included in the resources for transmission of PUSCH or PUSCH repetitions with repetition type A do not overlap with any non-SBFD semi-static/dynamic DL symbols (or non-SBFD dynamic FL symbols); If the UE 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 Regardless of the presence or absence of wrapping, the symbols included in the resources for transmission of the PUSCH or PUSCH repetition do not overlap with non-SBFD semi-static/dynamic DL symbols (or non-SBFD dynamic FL symbols), and any SBFD semi-static
  • the PUSCH or PUSCH repetition may be postponed to a slot/subslot that does not overlap with a static/dynamic UL symbol, any SBFD semi-static/dynamic DL symbol, and/or any SBFD semi-static/dynamic FL symbol.
  • the PUSCH or PUSCH repetition may be transmitted.
  • the UE may use any SBFD semi-static/dynamic UL symbols, any SBFD semi-static/dynamic DL symbols, and/or , PUSCH or PUSCH repetition may be transmitted in any time unit such as any subsequent symbol, subslot, subframe, or frame that does not overlap with any SBFD dynamic FL symbol.
  • the postponement may be executed when the SBFD operation instruction is set by RRC.
  • the postponement may be executed when the SBFD operation instruction is set by RRC.
  • deferral may not apply. That is, if the UE is dynamically notified of SBFD operation, the UE may not transmit the PUSCH or PUSCH repetition.
  • the UE does not overlap any of the non-SBFD DL symbols (or non-SBFD dynamic FL symbols), but the SBFD UL symbols, SBFD DL symbols, and/or , SBFD
  • the PUSCH or PUSCH repetition that overlaps with the FL symbol may not be transmitted in subsequent symbols, slots, etc.
  • ⁇ Case 2 Alt 1-3>>
  • the symbols included in the resources for transmission of PUSCH or PUSCH repetitions with repetition type A do not overlap with any non-SBFD semi-static/dynamic DL symbols (or non-SBFD dynamic FL symbols); If the SBFD semi-static/dynamic DL symbol 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
  • the PUSCH or PUSCH repetition may be rate matched on symbols other than symbols, SBFD semi-static/dynamic DL symbols, and/or SBFD dynamic FL symbols.
  • the HPN is not skipped for the relevant PUSCH or PUSCH repetition. It's okay.
  • Alt 2 ⁇ Case 2: Alt 2>
  • the symbols included in the resources for transmission of PUSCH or PUSCH repetitions with repetition type A do not overlap with any non-SBFD semi-static/dynamic DL symbols (or non-SBFD dynamic FL symbols) and have at least one If the UE overlaps with 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, Depending on the presence or absence, the transmission operation of PUSCH or PUSCH repetition is controlled.
  • the symbols included in the resources for transmission of PUSCH or PUSCH repetitions by repetition type A do not overlap with any non-SBFD semi-static/dynamic DL symbols (or non-SBFD dynamic FL symbols), and at least overlaps with 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 PUSCH or PUSCH repetition
  • the symbols included in the resources for transmission do not overlap with the DL subbands 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 The PUSCH or PUSCH repetition may be transmitted using the notified or configured resource.
  • the resources may be defined by specifications, semi-statically configured by RRC settings, dynamically notified by DCI notifications, or determined according to rules. Further, the resource may be specified, configured, notified, or determined explicitly or implicitly.
  • the HPN is not skipped for the relevant PUSCH or PUSCH repetition. It's okay.
  • the symbols included in the resources for the transmission of PUSCH or PUSCH repetitions with repetition type A do not overlap with any non-SBFD semi-static/dynamic DL symbols (or non-SBFD dynamic FL symbols) and at least one SBFD overlaps with a 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 for transmission of PUSCH or PUSCH repetition.
  • the UE shall perform the following Alt 2-1, Alt 2-2, and/or Alt 2-3.
  • PUSCH repetitions that are not transmitted due to overlap with the DL subband in the SBFD semi-static/dynamic UL symbol, the SBFD semi-static/dynamic DL symbol, and/or the SBFD dynamic FL symbol are repeated. It may or may not be counted.
  • the HPN may be skipped for the PUSCH or PUSCH repetition. Or, it may not be skipped.
  • the symbols included in the resources for transmission of PUSCH or PUSCH repetitions with repetition type A do not overlap with any non-SBFD semi-static/dynamic DL symbols (or non-SBFD dynamic FL symbols); 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, and PUSCH or PUSCH repetition
  • the symbols included in the resources for transmission overlap the DL subbands in the SBFD semi-static/dynamic UL symbols, SBFD semi-static/dynamic DL symbols, and/or SBFD semi-static/dynamic FL symbols
  • PUSCH or PUSCH repetitions with repetition type A do not overlap with
  • the HPN may be skipped for the PUSCH or PUSCH repetition. Or, it may not be skipped.
  • ⁇ Case 2 Alt 2-3>>
  • the symbols included in the resources for transmission of PUSCH or PUSCH repetitions with repetition type A do not overlap with any non-SBFD semi-static/dynamic DL symbols (or non-SBFD dynamic FL symbols); 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, and PUSCH or PUSCH repetition
  • the symbols included in the resources for transmission overlap the DL 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 symbols included in the resource for transmission of the PUSCH or PUSCH repetitions do not overlap with non-SBFD semi-static/dynamic DL symbols (or non-SBFD dynamic FL symbols), SBFD semi-static/dynamic UL symbols, SBFD semi-static/ The transmission of the PUSCH or PUSCH
  • the UE may select any subsequent slot/slot that does not overlap with UL symbols or FL symbols in non-SBFD operation, and does not overlap with DL subbands in UL symbols, DL symbols, and/or FL symbols in SBFD operation.
  • the PUSCH or PUSCH repetition may be transmitted in a sub-slot.
  • the UE may use non-overlapping non-SBFD semi-static/dynamic UL symbols (or non-SBFD dynamic flexible symbols), SBFD semi-static/dynamic UL symbols, SBFD semi-static/dynamic DL symbols, and/or SBFD dynamic FL symbols.
  • the PUSCH or PUSCH repetition may be transmitted in any time unit of any subsequent symbol, subframe, frame, etc. that does not overlap with any DL subband in the symbol.
  • the postponement may be executed when the SBFD operation instruction is set by RRC.
  • the postponement may be executed when the SBFD operation instruction is set by RRC.
  • deferral may not apply. That is, if the UE is dynamically notified of SBFD operation, the UE may not transmit the PUSCH or PUSCH repetition.
  • the UE does not overlap any of the non-SBFD UL symbols (or non-SBFD dynamic flexible symbols), but the SBFD UL symbols, SBFD DL symbols, and/or , SBFD
  • the PUSCH or PUSCH repetition that overlaps with the DL subband in the FL symbol may not be transmitted in subsequent symbols, slots, etc.
  • Alts to apply may be specified explicitly or implicitly by the specifications, may be semi-statically set by RRC, or may be dynamically notified by DCI. However, it may be determined by rules. For example, a parameter indicating which Alt to apply may be transmitted in at least one of RRC, DCI, and MAC CE (Medium Access Control Element).
  • TBS Transport Block Size
  • TBS may be determined according to Option A and/or Option B below.
  • TBS is i) non-SBFD semi-static/dynamic DL symbol (or non-SBFD dynamic FL symbol), SSB symbol or type-0 CORESET symbol; ii) SBFD semi-static/dynamic UL symbols, SBFD semi-static/dynamic DL symbols, and/or SBFD semi-static/dynamic FL symbols, and/or iii) DL resource blocks (RBs) in SBFD semi-static/dynamic UL symbols, SBFD semi-static/dynamic DL symbols, and/or SBFD semi-static/dynamic FL symbols; may be determined based on the number of resource elements (REs) after excluding.
  • REs resource elements
  • the TBS may be determined based on the number of REs signaled by time domain resource allocation (TDRA) and frequency domain resource allocation (FDRA).
  • TDRA time domain resource allocation
  • FDRA frequency domain resource allocation
  • the number of REs for TBS calculation may be different for different repetitions.
  • the TBS of each repetition is determined by the TBS calculated for the first PUSCH repetition and/or the maximum/minimum/average of the TBS values calculated for all repetitions. may be determined.
  • Which option to apply may be specified explicitly or implicitly by the specification, may be set semi-statically by RRC, may be dynamically notified by DCI, or may be determined by rules. may be determined.
  • a parameter indicating which option to apply may be sent in at least one of RRC, DCI, and MAC CE.
  • the UE may receive configuration information regarding Option A and Option B through RRC, and may be dynamically notified by DCI as to which of Option A and Option B should be applied.
  • the UE specifies that 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, and the uplink data channel overlap.
  • the transmission operation of the uplink data channel may be controlled depending on whether or not the uplink data channel is transmitted, and the transmission operation of the uplink data channel may be performed by the controlled transmission operation.
  • time frequency division duplexing may be SBFD
  • the downlink time unit in non-time frequency division duplexing operation is a DL symbol, minislot, slot, or any other time unit in non-SBFD operation.
  • the time unit in the time frequency division duplex operation may be a UL, DL or FL symbol, minislot, slot, or any other time unit in the SBFD operation.
  • the uplink data channel may be, for example, PUSCH, PUSCH repetition, etc.
  • the UE may not transmit the uplink data channel.
  • the UE may determine whether the uplink data channel overlaps the downlink time unit in non-SBFD operation.
  • the uplink data channel may be transmitted in different time units. That is, the UE may postpone the transmission of the PUSCH or PUSCH repetition to a slot in which symbols included in the time domain resources for the transmission of the PUSCH or PUSCH repetition do not overlap with non-SBFD semi-static/dynamic DL symbols.
  • the UE may receive the uplink data regardless of whether the uplink data channel overlaps the downlink subband in the time unit.
  • the transmission operation of the channel may also be controlled. For example, the UE may not transmit uplink data channels.
  • the UE may determine that the uplink data channel does not overlap with downlink time units or flexible time units in non-SBFD operation, and that uplink time units, downlink time units, and/or flexible time units in SBFD operation
  • the uplink data channel may be transmitted in time units that do not overlap.
  • the UE determines that the PUSCH or PUSCH repetition resources do not overlap with non-SBFD semi-static/dynamic DL symbols, and the SBFD semi-static/dynamic UL symbol, the SBFD semi-static/dynamic DL symbol, and/or the SBFD dynamic Transmission of the PUSCH or PUSCH repetition may be postponed to a slot that does not overlap with the FL symbol.
  • the UE may rate match the uplink data channel on time units other than time units in SBFD operation. That is, the UE may rate match 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.
  • the UE determines whether the uplink data channel overlaps the downlink subband in the time unit or not.
  • the transmission operation of the data channel may also be controlled. For example, if the uplink data channel does not overlap with the downlink subband in the time unit, the UE may transmit the uplink data channel on the configured/informed resource. On the other hand, if the uplink data channel overlaps the downlink subband in that time unit, the UE may not transmit the uplink data channel.
  • the UE may rate match the uplink data channel on the DL subband in time units in SBFD operation.
  • the UE may determine that the uplink data channel does not overlap with downlink time units or flexible time units in non-SBFD operation, and that the uplink data channel does not overlap with downlink time units or flexible time units in non-SBFD operation and
  • the uplink data channel may be transmitted in time units that do not overlap. That is, the UE determines that the PUSCH or PUSCH repetition resources do not overlap with non-SBFD semi-static/dynamic DL symbols, and the SBFD semi-static/dynamic UL symbol, the SBFD semi-static/dynamic DL symbol, and/or the SBFD dynamic Transmission of the PUSCH or PUSCH repetition may be postponed to a slot or minislot that does not overlap with the FL symbol.
  • the gNB is configured to control the uplink data channel in one or both of the downlink time units in non-time frequency division duplex operations, such as non-SBFD operations, and the time units in time frequency division duplex operations, such as SBFD operations.
  • the receiving operation may be controlled and the receiving operation of the uplink data channel may be performed by the controlled receiving operation.
  • time frequency division duplexing may be SBFD
  • the downlink time unit in non-time frequency division duplexing operation is a DL symbol, minislot, slot, or any other time unit in non-SBFD operation.
  • it may be a non-SBFD semi-static/dynamic DL symbol and/or a non-SBFD dynamic FL symbol.
  • the time unit in the time frequency division duplex operation may be a UL, DL or FL symbol, minislot, slot, or any other time unit in the SBFD operation.
  • the uplink data channel may be, for example, PUSCH, PUSCH repetition, etc.
  • UE capability information indicating whether the UE supports PUSCH enhancement for time frequency division duplex operation may be defined.
  • UE capability information regarding PUSCH transmission for time frequency division duplexing such as SBFD operation may be defined.
  • UE capability information indicating whether the UE supports s-TRP/m-TRP PUSCH repetition type A for time frequency division duplex operation may be defined. If the UE supports PUSCH enhancement for time frequency division duplex operation, the UE may send UE capability information to the gNB indicating that it supports PUSCH enhancement for SBFD operation. Upon receiving the UE capability information, the gNB may receive PUSCH from the UE according to PUSCH enhancement for time frequency division duplex operation.
  • Proposition 5 describes PUSCH enhancement for time frequency division duplexing operations such as SBFD operations. Specifically, PUSCH repetition type B is enhanced for SBFD operation as follows. The following invalid symbols are added.
  • Option 0 Semi-statically configured DL symbol for SBFD and non-SBFD operation
  • Option 1 Non-SBFD DL symbols configured semi-statically
  • Option 2 Semi-statically configured SBFD/non-SBFD DL symbols, UL/FL symbols that overlap with DL subbands. If the actual repetition overlaps with non-SBFD FL symbols, the UE does not transmit PUSCH.
  • Alt 1 The UE does not transmit PUSCH regardless of whether it overlaps with the DL subband.
  • the UE transmits the PUSCH when the PUSCH overlaps with the DL subband, and when the PUSCH does not overlap with the DL subband ⁇ Alt 2-1> The UE does not transmit PUSCH. ⁇ Alt 2-2> The UE rate matches the PUSCH to the UL subband.
  • Section 6.1.2.1 of TS38.214 states that for PUSCH repetition type B, after determining the invalid symbols for the PUSCH repetition type B transmission of each nominal repetition, the remaining symbols are It is specified that it is considered as a potentially valid symbol for B transmission.
  • the invalid symbol for segmentation of PUSCH repetition type B is the SSB symbol, type- 0.
  • the CORESET symbol and the invalid symbol signaled by the RRC parameter invalidSymbolPattern it may include symbols from options 0 to 2 below.
  • invalid symbols may include semi-static DL symbols, whether SBFD symbols or non-SBFD symbols.
  • invalid symbols may include non-SBFD semi-static DL symbols.
  • invalid symbols are non-SBFD semi-static and/or dynamic DL symbols (PUSCH repetition is SBFD semi-static and/or dynamic SBFD semi-static and/or dynamic DL symbol (if the PUSCH repetition overlaps with the DL sub-band in the SBFD semi-static and/or dynamic DL symbol); or dynamic UL symbols and/or SBFD semi-static and/or dynamic FL symbols (if the PUSCH repetition overlaps with DL subbands in the SBFD semi-static and/or dynamic FL symbols).
  • option 1 may be applied if SBFD operations (DL/UL subband allocation) are dynamically notified.
  • SBFD operation and/or DL/UL subband allocation
  • option 2 may be applied.
  • Section 6.1.2.1 of TS38.214 specifies that if the potentially valid symbols for a PUSCH repetition type B transmission is greater than 0 for a nominal repetition, then is defined to consist of one or more actual repetitions.
  • each actual repetition consists of a consecutive set of all potentially valid symbols available for PUSCH repetition type B transmission within a slot.
  • symbols included in the resources for actual PUSCH repetition transmission after segmentation are non-SBFD If it overlaps with the dynamic FL symbol, the UE may not transmit the actual PUSCH repetition.
  • the symbols included in the resources for transmission of the actual PUSCH repetition are at least one SBFD semi-static/dynamic UL symbol;
  • the UE may operate according to Alt 1 or Alt 2 below.
  • Alt 1 In Alt 1, the invalid symbols for segmentation include non-SBFD semi-static DL symbols, and the symbols included in the resources for transmission of actual PUSCH repetitions include at least one SBFD semi-static/dynamic UL symbol, at least one If it overlaps with two SBFD semi-static/dynamic DL symbols and/or at least one SBFD semi-static/dynamic FL symbol, the UE shall control the actual PUSCH repetition with or without overlap with DL subbands. You may choose not to send it.
  • the invalid symbols for segmentation include non-SBFD semi-static DL symbols
  • the symbols included in the resources for transmission of the actual PUSCH repetition include at least one SBFD semi-static/dynamic UL symbol, at least one If overlapping with two SBFD semi-static/dynamic DL symbols and/or at least one SBFD semi-static/dynamic FL symbol, the UE may operate as follows depending on the overlap with the DL subbands: good.
  • symbols included in the resources for transmission of actual PUSCH repetitions do not overlap with SBFD semi-static/dynamic UL symbols, SBFD semi-static/dynamic DL symbols, and/or SBFD semi-static/dynamic FL symbols.
  • the UE may send PUSCH repetition in the example.
  • the UE may control the transmission operation according to Alt 2-1 or Alt 2-2 below.
  • ⁇ Alt 2-1> symbols included in the resources for transmission of actual PUSCH repetitions overlap with SBFD semi-static/dynamic UL symbols, SBFD semi-static/dynamic DL symbols, and/or SBFD semi-static/dynamic FL symbols. If so, the UE may not transmit the actual PUSCH repetition.
  • ⁇ Alt 2-2> symbols included in the resources for transmission of actual PUSCH repetitions overlap with SBFD semi-static/dynamic UL symbols, SBFD semi-static/dynamic DL symbols, and/or SBFD semi-static/dynamic FL symbols. If present, the UE detects a On static/dynamic UL/FL symbols, rate matching may be performed on the symbols included in the resources for transmission of the actual PUSCH repetition.
  • Alts to apply may be specified explicitly or implicitly by the specifications, may be semi-statically set by RRC, or may be dynamically notified by DCI. However, it may be determined by rules. For example, a parameter indicating which Alt to apply may be transmitted in at least one of RRC, DCI, and MAC CE (Medium Access Control Element).
  • TBS may be determined based on Option A and/or Option B below.
  • the TBS may be determined according to Rel-16 rules. Specifically, the TBS may be determined based on the notified/configured TDRA and FDRA.
  • the TBS may be determined considering the actual resource elements (REs) of the actual PUSCH repetition.
  • the actual number of REs is - Non-SBFD semi-static/dynamic DL symbols (and non-SBFD dynamic FL symbols), - SBFD semi-static/dynamic UL symbol, SBFD semi-static/dynamic DL symbol, and/or SBFD semi-static/dynamic FL symbol, and/or ⁇ DL resource blocks (RBs) in SBFD semi-static/dynamic UL symbols, SBFD semi-static/dynamic DL symbols, and/or SBFD semi-static/dynamic FL symbols may be determined as the number of REs after exclusion.
  • the maximum value, minimum value, or average value of the actual number of REs may be used for TBS calculation.
  • Which option to apply may be specified explicitly or implicitly by the specification, may be set semi-statically by RRC, may be dynamically notified by DCI, or may be determined by rules. may be determined.
  • a parameter indicating which option to apply may be sent in at least one of RRC, DCI, and MAC CE.
  • the UE may receive configuration information regarding Option A and Option B through RRC, and may be dynamically notified by DCI as to which of Option A and Option B should be applied.
  • example 1 the UE is notified/configured for SBFD operation (and/or DL/UL subband allocation) for the serving cell/Bandwidth Part (BWP), and at the same time two SRS resource sets are configured for SRS in the serving cell/BWP. - It is not necessary to assume/judge/determine/interpret that it is set in ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2.
  • the UE is notified/configured for SBFD operation (and/or DL/UL subband allocation) for the serving cell/Bandwidth Part (BWP), and at the same time two SRS resource sets are configured for SRS in the serving cell/BWP.
  • BWP serving cell/Bandwidth Part
  • - Set in ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2, and at the same time push-RepTypeIndicatorDCI-0-1 or pushch-RepTypeIndicatorDCI-0-2 Assuming/judging/determining whether push-RepTypeA is set or not set. /Does not need to be interpreted.
  • the UE is notified/configured for SBFD operation (and/or DL/UL subband allocation) for the serving cell/Bandwidth Part (BWP), and at the same time two SRS resource sets are configured for SRS in the serving cell/BWP.
  • BWP serving cell/Bandwidth Part
  • - Set in ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2, and at the same time push-RepTypeIndicatorDCI-0-1 or pushch-RepTypeIndicatorDCI-0-2 Do not assume/judge/determine/interpret that push-RepTypeB is set to push-RepTypeB. It's okay.
  • SBFD operation (and/or DL/UL subband allocation) is notified/configured for the serving cell/bandwidth part (BWP), and two SRS resource sets are specified in the serving cell/BWP as srs-ResourceSetToAddModList or srs - If configured in ResourceSetToAddModListDCI-0-2, the UE may only utilize the first/second SRS resource set for PUSCH transmission.
  • BWP serving cell/bandwidth part
  • SBFD operation (and/or DL/UL subband allocation) is notified/configured for the serving cell/bandwidth part (BWP), and two SRS resource sets are configured in the serving cell/BWP as srs-ResourceSetToAddModList or srs - If set in ResourceSetToAddModListDCI-0-2 and push-RepTypeIndicatorDCI-0-1 or push-RepTypeIndicatorDCI-0-2 is set to push-RepTypeA or not set, U E is for PUSCH transmission Only the first/second SRS resource set may be used.
  • SBFD operation (and/or DL/UL subband allocation) is notified/configured for the serving cell/Bandwidth Part (BWP), and two SRS resource sets are specified in the serving cell/BWP as srs-ResourceSetToAddModList or srs - If set in ResourceSetToAddModListDCI-0-2 and at the same time push-RepTypeIndicatorDCI-0-1 or push-RepTypeIndicatorDCI-0-2 is set to push-RepTypeB, the UE 1st/2nd for CH transmission It is also possible to use only the SRS resource set of .
  • the UE specifies that 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, and the uplink data channel overlap.
  • the transmission operation of the uplink data channel may be controlled depending on whether or not the uplink data channel is transmitted, and the transmission operation of the uplink data channel may be performed by the controlled transmission operation.
  • time frequency division duplexing may be SBFD
  • the downlink time unit in non-time frequency division duplexing operation is a DL symbol, minislot, slot, or any other time unit in non-SBFD operation.
  • the time unit in the time frequency division duplex operation may be a UL, DL or FL symbol, minislot, slot, or any other time unit in the SBFD operation.
  • the uplink data channel may be, for example, PUSCH, PUSCH repetition, etc.
  • the UE may include non-SBFD downlink time units or SBFD time units as invalid time units for repeated transmissions of uplink data channels.
  • the UE may also determine invalid time units for repeated transmissions of the uplink data channel depending on whether the SBFD is dynamically signaled or semi-statically configured.
  • the UE also determines the overlap with the downlink subband when the symbols included in the resources for the actual repeated transmission after segmentation for the repeated transmission of the uplink data channel overlap with the SBFD time unit.
  • the actual repeated transmission operation may be controlled depending on the presence or absence.
  • the gNB is configured to control the uplink data channel in one or both of the downlink time units in non-time frequency division duplex operations, such as non-SBFD operations, and the time units in time frequency division duplex operations, such as SBFD operations.
  • the receiving operation may be controlled and the receiving operation of the uplink data channel may be performed by the controlled receiving operation.
  • time frequency division duplexing may be SBFD
  • the downlink time unit in non-time frequency division duplexing operation is a DL symbol, minislot, slot, or any other time unit in non-SBFD operation.
  • it may be a non-SBFD semi-static/dynamic DL symbol and/or a non-SBFD dynamic FL symbol.
  • the time unit in the time frequency division duplex operation may be a UL, DL or FL symbol, minislot, slot, or any other time unit in the SBFD operation.
  • the uplink data channel may be, for example, PUSCH, PUSCH repetition, etc.
  • UE capability information may be defined that indicates whether the UE supports PUSCH enhancement for time frequency division duplex operation. Additionally, UE capability information regarding multi-transmission/reception point PUSCH transmission for time frequency division duplexing such as SBFD operation may be defined. Specifically, UE capability information indicating whether the UE supports s-TRP/m-TRP PUSCH repetition type B for SBFD operation may be defined. If the UE supports PUSCH enhancement for time frequency division duplex operation, the UE may send UE capability information to the gNB indicating that it supports PUSCH enhancement for time frequency division duplex operation. Upon receiving the UE capability information, the gNB may receive PUSCH from the UE according to PUSCH enhancement for time frequency division duplex operation.
  • a non-repetitive PUCCH that overlaps with a dynamic DL or FL symbol is not transmitted. That is, the UE is configured by higher layers to transmit PUSCH, PUCCH, PRACH or SRS in a symbol set of a slot, and the UE is configured with a symbol subset from that symbol set as the downlink or flexible slot format. or the UE detects a DCI format 2_0 with a slot format value other than 255 that signals the UE to receive a PDSCH or CSI-RS in at least one symbol in the symbol set. If this is the case, and a predetermined condition is met, it is specified that the UE cancels PUSCH, PUCCH, PRACH, or SRS transmission in the symbol set.
  • Rel-15/16 NR specifies that a non-repetitive PUCCH that overlaps with a semi-static DL symbol is postponed to a slot where the resources of the PUCCH no longer overlap with the semi-static DL symbol. For example, as shown in FIG. 25, the PUCCH of HARQ-ACK corresponding to PDSCH #1 and #2 overlaps with the DL slot, so it is postponed to the UL slot.
  • Rel-15/16 NR specifies that PUCCHs that overlap dynamic DL or FL symbols are not transmitted.
  • SPS HARQ-ACK deferral may be enabled for SPS configurations.
  • the target slot/subslot for the postponement is the first available slot/subslot where the PUCCH resource does not overlap with the semi-static DL symbol, SSB symbol or CORESET #0 symbol and the condition “K1_max_def>K1+K_def” is satisfied.
  • the slot/subslot shall be a
  • K_def is the number of slots/subslots from the first PUCCH slot to the target PUCCH slot
  • K1_max_def is set for each SPS configuration index. For example, as shown in FIG. 26, the SPS HARQ-ACK for SPS PDSCH #1 is deferred to the target PUCCH slot because the corresponding first PUCCH overlaps with the semi-static DL slot.
  • the rules for TDD collisions in Rel-15/16/17 may need to be updated for SBFD operation.
  • the rules for TDD collisions in Rel-15/16/17 may need to be updated for SBFD operation.
  • the Rel-15/16 rules non-repeating PUCCHs in the illustrated slots are dropped and repeating PUCCHs are postponed.
  • the SPS HARQ-ACK PUCCH in the illustrated slot is deferred.
  • Proposition 6 describes PUCCH enhancement for time frequency division duplex operations such as SBFD operations. Specifically, the rules for PUCCH TDD collision for SBFD operation are enhanced as follows. Case 1: When PUCCH overlaps with non-SBFD DL symbol, SSB or Type-0 CORESET ⁇ Alt-A> The UE does not transmit PUCCH. ⁇ Alt B> The UE postpones transmission of the PUCCH. Case 2: When PUCCH overlaps with non-SBFD DL symbols: The UE does not transmit PUCCH.
  • Case 3 When PUCCH overlaps with SBFD DL symbol ⁇ Alt 1> The UE operates according to Alt 1-1 to 1-2 below, regardless of whether there is overlap with the DL subband. ⁇ Alt 1-1>> The UE does not transmit PUCCH. ⁇ Alt 1-2>> The UE postpones transmission of the PUCCH. ⁇ Alt 2> The UE operates according to Alt 2-1 to 2-3 below depending on whether there is overlap with the DL subband ⁇ Alt 2-1>> The UE does not transmit PUCCH. ⁇ Alt 2-2>> The UE rate matches the PUCCH to the UL subband. ⁇ Alt 2-3>> The UE postpones transmission of the PUCCH.
  • the UE may control the PUCCH transmission operation corresponding to cases 1 to 3 below.
  • Case 1 The symbols included in the resources for transmission of PUCCH or PUCCH repetition overlap with at least one non-SBFD semi-static DL symbol, SSB symbol or type-0 CORESET symbol.
  • Case 2 The symbols included in the resources for transmission of PUCCH or PUCCH repetition overlap with at least one non-SBFD dynamic DL/FL symbol.
  • Case 3 The symbols included in the resources for transmission of PUCCH or PUCCH repetitions do not overlap with any non-SBFD semi-static/dynamic DL symbols (or non-SBFD dynamic FL symbols), but at least one SBFD semi-static/dynamic overlap with a UL symbol, at least one SBFD semi-static/dynamic DL symbol, and/or at least one SBFD semi-static/dynamic FL symbol.
  • Alt-A if the symbols included in the PUCCH or the resources for transmission of PUCCH repetition overlap with at least one non-SBFD semi-static DL symbol, SSB symbol or type-0 CORESET symbol, the UE PUCCH repetition may not be transmitted. That is, the UE may not transmit PUCCH or PUCCH repetitions that overlap with DL symbols in non-SBFD operation.
  • PUCCH repetitions that are not transmitted by overlapping with at least one non-SBFD semi-static DL symbol, SSB symbol, or type-0 CORESET symbol may or may not be counted in the number of repetitions. You don't have to.
  • ⁇ Case 1: Alt-B> if the symbols included in the PUCCH or resources for transmission of PUCCH repetition overlap with at least one non-SBFD semi-static DL symbol, SSB symbol or type-0 CORESET symbol, the UE transmits the PUCCH or PUCCH
  • the PUCCH or PUCCH repetition may be postponed to a slot/subslot in which symbols included in the resources for repeated transmission do not overlap with non-SBFD semi-static DL symbols, SSB symbols, or type-0 CORESET symbols.
  • PUCCH repetitions that are not transmitted due to overlapping with at least one non-SBFD dynamic DL/FL symbol may or may not be counted in the number of repetitions.
  • the symbols included in the resources for transmission of PUCCH or PUCCH repetitions do not overlap with any non-SBFD semi-static/dynamic DL symbols (or non-SBFD dynamic FL symbols), but with at least one SBFD semi-static/dynamic DL symbol. If overlapping with a 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 shall: It may work.
  • Alt 1 ⁇ Case 3: Alt 1>
  • the symbols included in the resources for transmission of PUCCH or PUCCH repetitions do not overlap with any non-SBFD semi-static/dynamic DL symbols (or non-SBFD dynamic FL symbols), but at least one SBFD semi-static/dynamic
  • the UE determines whether or not there is an overlap with the DL subband.
  • PUCCH repetitions that are not transmitted by overlapping with SBFD semi-static/dynamic UL symbols, SBFD semi-static/dynamic DL symbols, and/or SBFD semi-static/dynamic FL symbols are counted in the number of repetitions. may be counted, or may not be counted.
  • Symbols included in the resource do not overlap with non-SBFD semi-static DL symbols (or non-SBFD dynamic FL symbols), and are SBFD semi-static/dynamic UL symbols, SBFD semi-static/dynamic DL symbols, and/or SBFD semi-static/
  • the PUCCH or PUCCH repetition may be postponed to a slot/subslot that does not overlap with the dynamic FL symbol.
  • the postponement may be executed when the SBFD operation instruction is set by RRC.
  • deferral may not apply. That is, if the UE is dynamically notified of SBFD operation, the UE may not transmit the PUCCH or PUCCH repetition.
  • the UE may not overlap with any non-SBFD DL/FL symbols, but may overlap with SBFD UL symbols, SBFD DL symbols, and/or SBFD FL symbols.
  • the wrapped PUCCH or PUCCH repetition may not be transmitted in subsequent symbols, slots, etc.
  • ⁇ Case 3 Alt 2> In Alt 2, the symbols included in the resources for transmission of PUCCH or PUCCH repetitions do not overlap with any non-SBFD semi-static/dynamic DL symbols (or non-SBFD dynamic FL symbols), but at least one SBFD semi-static/dynamic If the dynamic UL symbol overlaps with at least one SBFD semi-static/dynamic DL symbol and/or at least one SBFD semi-static/dynamic FL symbol, the UE determines whether or not there is overlap with the DL subband. , PUCCH or PUCCH repetition transmission operations may be controlled.
  • the symbols included in the resources for transmission of PUCCH or PUCCH repetitions do not overlap with any non-SBFD semi-static/dynamic DL symbols (or non-SBFD dynamic FL symbols), but with at least one SBFD semi-static /dynamic UL symbol, at least one SBFD semi-static/dynamic DL symbol, and/or overlaps with at least one SBFD semi-static/dynamic FL symbol, and resources for transmission of PUCCH or PUCCH repetition If the symbols contained in The PUCCH or PUCCH repetition may be transmitted.
  • the resource may be defined by specifications, semi-statically configured by RRC settings, dynamically notified by DCI notification, or determined according to rules. Further, the resource may be specified, configured, notified, or determined explicitly or implicitly.
  • the symbols included in the resources for transmission of the PUCCH or PUCCH repetitions do not overlap with any non-SBFD semi-static/dynamic DL symbols (or non-SBFD dynamic FL symbols), but at least one SBFD semi-static/dynamic UL symbol, overlaps with at least one SBFD semi-static/dynamic DL symbol and/or at least one SBFD semi-static/dynamic FL symbol and is included in the resources for transmission of PUCCH or PUCCH repetition If the symbol overlaps with the DL subband in the SBFD semi-static/dynamic UL symbol, the SBFD semi-static/dynamic DL symbol, and/or the SBFD dynamic FL symbol, the UE shall perform the following Alt 2-1, Alt 2- 2, and/or Alt 2-3.
  • PUCCH repetitions that are not transmitted due to overlap with the DL subband in the SBFD semi-static/dynamic UL symbol, the SBFD semi-static/dynamic DL symbol, and/or the SBFD dynamic FL symbol are repeated. It may or may not be counted.
  • the symbols included in the resources for transmission of the PUCCH or PUCCH repetitions do not overlap with any non-SBFD semi-static/dynamic DL symbols (or non-SBFD dynamic FL symbols), but with at least one SBFD semi-static/dynamic DL symbol.
  • the UE uses the SBFD semi-static/dynamic UL symbol.
  • Rate matching may be applied to symbols included in transmission resources.
  • the symbols included in the resources for transmission of PUCCH or PUCCH repetitions do not overlap with any non-SBFD semi-static/dynamic DL symbols (or non-SBFD dynamic FL symbols), but at least one SBFD semi-static/dynamic DL symbol overlapping with a 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 for transmission of PUCCH or PUCCH repetition.
  • the UE shall The symbols included in the resources for transmission do not overlap with non-SBFD semi-static/dynamic UL symbols (or non-SBFD dynamic flexible symbols), SBFD semi-static/dynamic UL symbols, SBFD semi-static/dynamic DL symbols, and/or , the PUCCH or PUCCH repetition may be postponed to a slot/subslot that does not overlap with any DL subband in the SBFD dynamic FL symbol.
  • the UE may select any subsequent slot/s that does not overlap with UL symbols or FL symbols in non-SBFD operation, and does not overlap with DL subbands in UL symbols, DL symbols, and/or FL symbols in SBFD operation.
  • the PUCCH or PUCCH repetition may be transmitted in a sub-slot.
  • the UE may use non-overlapping non-SBFD semi-static/dynamic UL symbols (or non-SBFD dynamic flexible symbols), SBFD semi-static/dynamic UL symbols, SBFD semi-static/dynamic DL symbols, and/or SBFD dynamic FL symbols.
  • the PUCCH or PUCCH repetition may be transmitted in any time unit of any subsequent symbol, subslot, subframe, frame, etc. that does not overlap with any DL subband in the symbol.
  • Alts to apply may be specified explicitly or implicitly by the specifications, may be semi-statically set by RRC, or may be dynamically notified by DCI. However, it may also be determined by rules. For example, a parameter instructing which Alt to apply may be transmitted in at least one of RRC, DCI, and MAC CE (Medium Access Control Element).
  • Alts 2-1 to 2-3 described above may be selected based on a method of instructing SBFD operation (and/or DL/UL subband allocation). For example, if SBFD operation (and/or DL/UL subband allocation) is configured by RRC, Alt 2-2 or Alt 2-3 may be applied. Alt 2-1 may be applied if the SBFD operation (and/or DL/UL subband allocation) is dynamically signaled by the DCI. Further, the selection may be determined according to a rule, whether it is defined by specifications, semi-statically set by RRC settings, dynamically notified by DCI notification, etc. Further, the selection may be explicitly or implicitly specified, set, notified, or determined.
  • the UE specifies that 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, and the uplink control channel overlap.
  • the transmission operation of the uplink control channel may be controlled depending on whether or not the transmission operation is performed, and the transmission operation of the uplink control channel may be performed by the controlled transmission operation.
  • time frequency division duplexing may be SBFD
  • the downlink time unit in non-time frequency division duplexing operation is a DL symbol, subslot, slot, or any other time unit in non-SBFD operation.
  • the time unit in the time frequency division duplex operation may be a UL, DL or FL symbol, subslot, slot, or any other time unit in the SBFD operation.
  • the uplink control channel may be, for example, PUCCH, PUCCH repetition, etc.
  • the UE may not transmit the uplink control channel.
  • the UE determines whether the uplink control channel overlaps with the downlink time unit in non-SBFD operation.
  • the uplink control channel may be transmitted in different time units. That is, the UE may defer the transmission of the PUCCH or PUCCH repetition to a slot in which symbols included in the time domain resources for the transmission of the PUCCH or PUCCH repetition do not overlap with non-SBFD semi-static/dynamic DL symbols.
  • the UE may perform uplink control regardless of whether the uplink control channel overlaps the downlink subband in the time unit.
  • the transmission operation of the channel may also be controlled. For example, the UE may not transmit uplink control channels.
  • the UE may determine that the uplink control channel does not overlap with downlink time units or flexible time units in non-SBFD operation, and that the uplink control channel does not overlap with downlink time units or flexible time units in non-SBFD operation;
  • the uplink control channel may be transmitted in time units that do not overlap.
  • the UE is configured to ensure that the symbols included in the PUCCH or PUCCH repetition transmission resources do not overlap with non-SBFD semi-static/dynamic DL symbols, and the SBFD semi-static/dynamic UL symbols, SBFD semi-static/dynamic DL symbols , and/or the transmission of the PUCCH or PUCCH repetition may be postponed to a slot that does not overlap with the SBFD dynamic FL symbol.
  • the UE may rate match the PUCCH or PUCCH repetition in time units where the uplink control channel is exclusive of time units in SBFD operation. That is, the UE may rate match PUCCH or PUCCH repetition on symbols other than SBFD semi-static/dynamic UL symbols, SBFD semi-static/dynamic DL symbols, and/or SBFD dynamic FL symbols.
  • the UE determines whether the uplink control channel overlaps with the downlink subband in the time unit or not.
  • the transmission operation of the control channel may also be controlled. For example, if the uplink control channel does not overlap with the downlink subband in the time unit, the UE may transmit the uplink control channel on the configured/informed resource. On the other hand, if the uplink control channel overlaps the downlink subband in the time unit, the UE may not transmit the uplink control channel. Alternatively/in addition, the UE may rate match the uplink control channel on the UL subband in time units in SBFD operation.
  • the UE may determine that the uplink control channel does not overlap with downlink time units or flexible time units in non-SBFD operation and that the uplink control channel does not overlap with downlink time units or flexible time units in SBFD operation.
  • the uplink control channel may be transmitted in time units that do not overlap. That is, the UE determines that the PUSCH or PUSCH repetition resources do not overlap with non-SBFD semi-static/dynamic DL symbols, and the SBFD semi-static/dynamic UL symbol, the SBFD semi-static/dynamic DL symbol, and/or the SBFD dynamic Transmission of the PUCCH or PUCCH repetition may be postponed to a slot or subslot that does not overlap with the FL symbol.
  • the gNB controls the uplink control channel in one or both of the downlink time units in non-time frequency division duplex operations, such as non-SBFD operations, and the time units in time frequency division duplex operations, such as SBFD operations.
  • the receiving operation may be controlled and the receiving operation of the uplink control channel may be performed by the controlled receiving operation.
  • time frequency division duplexing may be SBFD
  • the downlink time unit in non-time frequency division duplexing operation is a DL symbol, minislot, slot, or any other time unit in non-SBFD operation.
  • it may be a non-SBFD semi-static/dynamic DL symbol and/or a non-SBFD dynamic FL symbol.
  • the time unit in the time frequency division duplex operation may be a UL, DL or FL symbol, minislot, slot, or any other time unit in the SBFD operation.
  • the uplink control channel may be, for example, PUCCH, PUCCH repetition, etc.
  • UE capability information may be defined that indicates whether the UE supports PUCCH enhancement for time frequency division duplex operation.
  • UE capability information regarding PUCCH transmission for time frequency division duplexing such as SBFD operation may be defined.
  • UE capability information indicating whether the UE supports s-TRP/m-TRP PUCCH repetition for SBFD operation may be defined.
  • the UE may send UE capability information to the gNB indicating that it supports PUCCH enhancement for time frequency division duplex operation.
  • the gNB may receive PUCCH from the UE according to PUCCH enhancement for time frequency division duplex operation.
  • Proposition 7 describes an enhanced SPS HARQ-ACK deferral operation for time frequency division duplex operations such as SBFD operations. Specifically, SPS HARQ-ACK deferral operation is enhanced for SBFD operation as follows. SPS HARQ-ACK is deferred depending on the following conditions: ⁇ Alt 1> When PUCCH overlaps with a semi-static DL symbol, SSB symbol, or Type-0 CORESET symbol, regardless of SBFD operation or non-SBFD operation ⁇ Alt 2> When PUCCH overlaps with a non-SBFD semi-static DL symbol, SSB symbol, or Type-0 CORESET symbol ⁇ Alt 3> When PUCCH overlaps with the SBFD symbol in addition to Alt 2 ⁇ Alt 4> If the PUCCH overlaps the DL subband in addition to Alt 2, the deferred PUCCH resource will be transmitted in the first available slot below.
  • SPS HARQ-ACK deferral behavior in SBFD and non-SBFD operations.
  • SPS HARQ-ACK deferral processing is enabled for the SPS configuration, if the deferral conditions of Alts 1 to 4 below are satisfied, the UE may defer HARQ-ACK in the SPS configuration. good.
  • Alt 1 In Alt 1, the symbols included in the resources for transmission of PUCCH of SPS HARQ-ACK overlap with at least one semi-static DL symbol, SSB symbol or type-0 CORESET symbol, regardless of SBFD operation or non-SBFD operation. When doing so, the UE may defer HARQ-ACK for the SPS configuration.
  • Alt 2 In Alt 2, when the symbols included in the resources for transmission of PUCCH of SPS HARQ-ACK overlap with at least one non-SBFD semi-static DL symbol, SSB symbol or type-0 CORESET symbol, the UE HARQ-ACK for the session may be postponed.
  • the symbols included in the resources for transmission of PUCCH of SPS HARQ-ACK include at least one non-SBFD semi-static DL symbol, SSB symbol, type-0 CORESET symbol, SBFD semi-static/dynamic UL symbol, SBFD semi-static
  • the UE may defer HARQ-ACK in SPS configuration when overlapping with static/dynamic DL symbols and/or SBFD dynamic FL symbols.
  • Alt 4 the symbols included in the resources for transmission of the PUCCH of SPS HARQ-ACK overlap with at least one non-SBFD semi-static DL symbol, SSB symbol, or type-0 CORESET symbol, or
  • the UE may defer HARQ-ACK in SPS configuration when overlapping with DL subbands in static/dynamic UL symbols, SBFD semi-static/dynamic DL symbols, and/or SBFD dynamic FL symbols.
  • Alts 1 to 4 described above may be selected based on the instruction method for SBFD operation (and/or DL/UL subband allocation). For example, if SBFD operation (and/or DL/UL subband allocation) is configured by RRC, Alt2 or Alt3 may be applied. Alt1 may be applied if the SBFD operation (and/or DL/UL subband allocation) is dynamically signaled by the DCI. Further, the selection may be determined according to a rule, whether it is defined by specifications, semi-statically set by RRC settings, dynamically notified by DCI notifications, etc. Further, the selection may be explicitly or implicitly prescribed, set, notified, or determined.
  • the UE shall decide the first available slot/subslot as the target slot/subslot. It's okay.
  • the first available slot/subslot may be the following PUCCH resources Alt 1 to Alt 4.
  • Alt 1 the UE uses a PUCCH for SPS HARQ-ACK where the symbols included in the PUCCH resource overlap with at least one semi-static DL symbol, SSB symbol or type-0 CORESET symbol, regardless of SBFD operation or non-SBFD operation.
  • the HARQ-ACK in the SPS configuration may be deferred to the first available slot/subslot that does not overlap.
  • Alt 2 the UE specifies that the first available symbol included in the PUCCH resource does not overlap with the PUCCH of the SPS HARQ-ACK that overlaps with at least one non-SBFD semi-static DL symbol, SSB symbol or type-0 CORESET symbol.
  • HARQ-ACK in the SPS configuration may be postponed to a slot/subslot.
  • the UE specifies that the symbols included in the PUCCH resource include at least one non-SBFD semi-static DL symbol, an SSB symbol, a type-0 CORESET symbol, an SBFD semi-static/dynamic UL symbol, an SBFD semi-static/dynamic DL symbol, and /Or the HARQ-ACK in the SPS configuration may be deferred to the first available slot/subslot that does not overlap with the PUCCH of the SPS HARQ-ACK that overlaps with the SBFD dynamic FL symbol.
  • Alt 4 the UE determines whether the symbols included in the PUCCH resource overlap with at least one non-SBFD semi-static DL symbol, SSB symbol, or type-0 CORESET symbol, or SBFD semi-static/dynamic UL symbol, SBFD HARQ-ACK of SPS configuration in the first available slot/subslot that does not overlap with PUCCH of SPS HARQ-ACK that overlaps with DL subband in semi-static/dynamic DL symbol and/or SBFD dynamic FL symbol.
  • ACK may be deferred.
  • the combined operation of SPS HARQ-ACK deferral operation and SBFD operation may not be supported.
  • the UE may have SPS HARQ-ACK deferral operation enabled for the SPS configuration on the serving cell/Bandwidth Part (BWP) and at the same time SBFD operation (and/or DL/UL subband allocation) on the serving cell/BWP. It is not necessary to assume/judge/determine/interpret what is set/notified/enabled above.
  • the UE may not perform SPS HARQ-ACK deferral operations.
  • Alts to apply may be specified explicitly or implicitly by the specifications, may be semi-statically set by RRC, or may be dynamically notified by DCI. However, it may also be determined by rules. For example, a parameter instructing which Alt to apply may be transmitted in at least one of RRC, DCI, and MAC CE (Medium Access Control Element).
  • the UE performs HARQ-ACK deferral operation if the HARQ-ACK deferral conditions in time-frequency division duplexing operation such as SBFD operation and non-time-frequency division duplexing operation such as non-SBFD operation are satisfied.
  • HARQ-ACK may be SPS HARQ-ACK
  • the uplink control channel may be PUCCH.
  • the UE detects HARQ-ACK when SPS HARQ-ACK overlaps with semi-static downlink time units, SSB time units or type-0 CORESET time units, regardless of SBFD and non-SBFD operations.
  • ACK deferral behavior may be enabled.
  • the 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 (Control Resource Set) time unit
  • SSB synchronization signal block
  • type-0 CORESET Control Resource Set
  • the UE shall be notified when the SPS HARQ-ACK overlaps with a non-SBFD semi-static downlink time unit, SSB time unit or type-0 CORESET time unit, or overlaps with an SBFD semi-static/dynamic time unit.
  • HARQ-ACK deferral operation may be enabled.
  • the UE also determines whether the SPS HARQ-ACK overlaps with a non-SBFD semi-static downlink time unit, an SSB time unit or a type-0 CORESET time unit, or a downlink subband in a SBFD semi-static/dynamic time unit.
  • HARQ-ACK deferral operation may be enabled when overlapped with the HARQ-ACK.
  • the gNB transmits a downlink data channel and defines the deferral conditions for HARQ-ACK in time frequency division duplex operations such as SBFD operations and non-time frequency division duplex operations such as non-SBFD operations for the downlink data channels.
  • HARQ-ACK may be SPS HARQ-ACK
  • the uplink control channel may be PUCCH.
  • UE capability information may be defined indicating whether the UE supports SPS HARQ-ACK enhancement for time frequency division duplex operation. .
  • UE capability information regarding SPS HARQ-ACK transmission for time frequency division duplexing such as SBFD operation may be defined.
  • UE capability information indicating whether the UE supports SPS HARQ-ACK deferral operation for SBFD operation may be defined. If the UE supports SPS HARQ-ACK enhancement for time-frequency division duplex operation, the UE shall send UE capability information to the gNB indicating that it supports SPS HARQ-ACK enhancement for time-frequency division duplex operation. You can also send it.
  • the gNB may receive SPS HARQ-ACK from the UE according to the SPS HARQ-ACK enhancement for time frequency division duplex operation.
  • DCI 2_1 Section 11.2 of TS38.213 specifies that the set of physical resource blocks (PRBs) is equal to the active DL BWP and includes B INT PRBs. If the UE detects DCI format 2_1 in PDCCH reception in a slot, the symbol set is the last one before the first symbol of PDCCH reception in that slot. It is stipulated that there will be one symbol.
  • T INT is the PDCCH monitoring period provided by the value of monitoringSlotPeriodicityAndOffset
  • N symb slot is the number of symbols per slot
  • ⁇ is the SCS configuration of the serving cell by mapping to each field in DCI format 2_1.
  • ⁇ INT is the SCS configuration of the DL BWP in which the UE received the PDCCH according to DCI format 2_1.
  • the symbols signaled as uplink by tdd-UL-DL-ConfigurationCommon are the last symbol before the first symbol of PDCCH reception in the slot. It is stipulated that the symbol be deleted from each symbol. It is also specified that the resulting symbol set includes a plurality of symbols noted as N INT .
  • timeFrequencySet when the value of timeFrequencySet is set0, it is specified that the 14 bits from the MSB of the field in DCI format 2_1 have a one-to-one mapping with 14 groups of consecutive symbols from the symbol set.
  • the first Each of the symbol groups is contains the symbol and the last Each of the symbol groups is Contains symbols.
  • a bit value of 0 indicates a transmission to the UE in the corresponding symbol group
  • a bit value of 1 indicates no transmission to the UE in the corresponding symbol group.
  • timeFrequencySet it is specified that the seven bit pairs from the MSB of the field in DCI format 2_1 have a one-to-one mapping with seven groups of consecutive symbols.
  • the first Each of the symbol groups is contains symbols and the last Each of the symbol groups is Contains symbols.
  • the first bit in the bit pair of a symbol group is the first bit from the set of B INT PRBs.
  • B INT is applicable to a subset of PRBs
  • the second bit in the bit pair of the symbol group is the last is applicable to a subset of PRBs.
  • a bit value of 0 indicates a transmission to the UE in the corresponding symbol group and subset of PRBs
  • a bit value of 1 indicates no transmission to the UE in the corresponding symbol group and subset of PRBs.
  • FIG. 28 shows a case where the value of timeFrequencySet is set0 and a case where the value of timeFrequencySet is set1.
  • the number of DL resource blocks (RB) in different symbols may be different.
  • timeFrequencySet the value of timeFrequencySet
  • higher granularity of frequency domain indication is achievable if the actual DL subband size is considered for the symbol group of the SBFD symbol set with narrowband DL subbands. It is believed that there is.
  • Proposition 8 describes time-domain and frequency-domain preemption enhancements for time-frequency division duplex operations such as SBFD operations. Specifically, preemption in the time direction and preemption in the time direction are enhanced as follows. Calculation of N INT enhanced in the time direction Case 1: When a DL subband is configured on a resource configured as UL in a TDD pattern ⁇ Alt 1> Include resources configured as UL in the TDD pattern. ⁇ Alt 2> Includes resources that are configured as UL in the TDD pattern and configured for SBFD operation. Case 2: When the UL subband is not set for the resource set as DL in the TDD pattern ⁇ Alt 1> Include resources configured as UL in the TDD pattern.
  • ⁇ Alt 2> Do not exclude symbols.
  • ⁇ Alt 3> Includes resources that are set as UL in the TDD pattern and are not used for SBFD operation. Case 3: If SBFD operation is not supported in the UL symbol, include the resource configured as UL in the TDD pattern. Enhancement in frequency direction ⁇ Alt 1> The frequency resources including the UL subbands are evenly divided into two bit pairs. ⁇ Alt 2> The frequency resource excluding the UL subband is divided into two DL subbands for two bit pairs.
  • SBFD operation in a UL symbol means a DL subband in a UL symbol that is designated as uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated; may mean a UL subband in a DL symbol designated as downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.
  • Case 1 SBFD operation in the UL symbol is supported/enabled and the SBFD operation (or DL/UL subband allocation) is signaled/ Set.
  • Case 2 SBFD operation in UL symbols is supported/enabled and SBFD operation (or DL/UL subband allocation) is signaled/configured by UE-specific signaling (e.g., UE-specific RRC configuration or UE-specific DCI).
  • Case 3 SBFD operation in UL symbols is not supported/enabled.
  • ⁇ Case 1> SBFD operation in UL symbols is supported/enabled, and SBFD operation (or DL/UL subband allocation) is signaled by cell-specific/group-common signaling (e.g., cell-specific/group-common RRC configuration or DCI). / If set, the symbols deleted to obtain N INT symbols may be the symbols according to Alt 1 and/or Alt 2 below.
  • cell-specific/group-common signaling e.g., cell-specific/group-common RRC configuration or DCI.
  • the symbols deleted for the tdd-UL-DL-ConfigurationCommon may include symbols designated as uplink by the tdd-UL-DL-ConfigurationCommon.
  • Alt 1 is similar to Rel-15.
  • ⁇ Case 1 Alt 2>> In Alt 2, if SBFD operation in UL symbols is supported/enabled and SBFD operation (or DL/UL subband allocation) is signaled/configured by cell-specific/group-common signaling, obtain N INT symbols. Symbols deleted for this purpose may include symbols that are designated as uplink by tdd-UL-DL-ConfigurationCommon but are not configured/notified for SBFD operation. Since the SBFD UL symbols include DL subbands, there may be DL transmissions on the UL symbols. Therefore, a preemption instruction by DCI 2_1 may be applicable to the UL symbol.
  • ⁇ Case 2> In case 2, if SBFD operation in UL symbols is supported/enabled and SBFD operation (or DL/UL subband allocation) is signaled/configured by UE-specific signaling, remove to obtain N INT symbols.
  • the symbols displayed may be symbols according to Alt 1, Alt 2, and/or Alt 3 below.
  • the symbols configured may include symbols designated as uplink by tdd-UL-DL-ConfigurationCommon.
  • Alt 1 is similar to Rel-15.
  • ⁇ Case 2 Alt 2>> In Alt 2, if SBFD operation in UL symbols is supported/enabled and SBFD operation (or DL/UL subband allocation) is notified/configured by UE-specific signaling, no symbol may be deleted. In case 2, a particular UE is not sure whether the UL symbol is present in the DL subband for other UEs in the cell. Therefore, the UL symbol may not be deleted for the DCI 2_1 indication.
  • ⁇ Case 2 Alt 3>>
  • SBFD operation in UL symbols is supported/enabled and SBFD operation (or DL/UL subband allocation) is signaled/configured by UE-specific signaling, remove to obtain N INT symbols.
  • the symbols designated as uplink by the tdd-UL-DL-ConfigurationCommon may include symbols reserved for non-SBFD operation as defined by the specification or RRC configuration, if present. For example, PRACH symbols/slots may be reserved for non-SBFD operations.
  • a particular UL symbol e.g. PRACH symbol
  • the UL symbol may be deleted for the DCI 2_1 indication.
  • the resource block (RB) applicable to each bit pair of the symbol group may be determined by Alt 1 and/or Alt 2 below.
  • the applicable RBs for each bit pair in a symbol group are B INT PRBs, regardless of the SBFD symbol in the symbol group, similar to the Rel-15 rule. the first from the set of The first bit corresponding to a subset of B INT PRBs and the last bit from the set of B INT PRBs. and a second bit corresponding to a subset of PRBs.
  • the frequency resources including the UL subband are evenly divided into two bit pairs.
  • a symbol group contains only SBFD symbols, and the SBFD symbols in the symbol group contain the same DL/UL subband with a total of B INT-DL PRBs on the DL subband in each SBFD symbol of the symbol group.
  • the applicable RB for each bit pair of a symbol group is the first one from the set of B INT-DL DL PRBs.
  • a second bit corresponding to a subset of DL PRBs.
  • frequency resources that do not include UL subbands are evenly divided into two bit pairs.
  • a symbol group contains only SBFD symbols, and the SBFD symbols in the symbol group are connected to the same DL/UL subband with a total of B INT-DL-subband DL subbands in each SBFD symbol of the symbol group.
  • the applicable RB for each bit pair of a symbol group is the first one from the set of B INT-DL-subband DL subbands.
  • a second bit corresponding to a subset of DL subbands.
  • a frequency resource that does not include a UL subband is divided into two DL subbands for two bit pairs.
  • the frequency resource division method described above is not necessarily limited to the above, and any other division method may be applied.
  • Which of the above Alts to apply may be specified explicitly or implicitly by the specifications, may be set semi-statically by RRC, may be dynamically notified by DCI, It may also be determined by rules.
  • a parameter instructing which Alt to apply may be transmitted in at least one of RRC, DCI, and MAC CE (Medium Access Control Element).
  • the UE adjusts the radio resources indicated by the downlink control information with respect to the time domain or the frequency domain in downlink reception of time frequency division duplex operation such as SBFD operation, and downlinks in the adjusted radio resources.
  • a link channel may also be received.
  • the time frequency division duplexing may be SBFD, for example, the downlink channel may be PDCCH, PDSCH, etc., and the downlink control information may be DCI 2_1.
  • radio resources are resources defined by time units such as symbols and frequency units such as resource blocks.
  • the UE may exclude time units configured as uplink through time division duplexing (TDD) configuration from the radio resources indicated by the downlink control information. That is, for time domain preemption, the UE may exclude symbols configured as UL by TDD configuration such as tdd-UL-DL-ConfigurationCommon to obtain N INT symbols for preemption.
  • TDD time division duplexing
  • the UE may exclude uplink subbands in SBFD operation from the radio resources indicated by the downlink control information. That is, for frequency domain preemption, even if the UE receives a downlink channel in a frequency band that includes the UL subband or does not include the UL subband in SBFD operation, as shown in FIGS. good.
  • the gNB transmits downlink signals in time-domain or frequency-domain coordinated radio resources with respect to the radio resources indicated by downlink control information in downlink transmission in time-frequency division duplexing operations such as SBFD operations. It may control the terminal to receive the channel and transmit the downlink channel.
  • the time frequency division duplexing may be SBFD
  • the downlink channel may be PDCCH, PDSCH, etc.
  • the downlink control information may be DCI 2_1.
  • radio resources are resources defined by time units such as symbols and frequency units such as resource blocks.
  • UE Capability For preemption in time frequency division duplex operations such as SBFD operations, UE capability information may be defined that indicates whether the UE supports enhanced DCI 2_1 for time frequency division duplex operations. Also, UE capability information regarding preemption for time frequency division duplexing such as SBFD operation may be defined. If the UE supports enhanced preemption for time frequency division duplex operation, the UE sends UE capability information to the gNB indicating that it supports enhanced DCI 2_1 for time frequency division duplex operation. You may also send it to Upon receiving the UE capability information, the gNB may send the enhanced DCI 2_1 for time frequency division duplex operation to the UE and cause the UE to perform preemption in time frequency division duplex operation.
  • DCI 2_4 Section 11.2A of TS38.213 provides for cancellation notification in DCI format 2_4: N CI : Number of bits provided by ci-PayloadSize B CI : Number of PRBs provided by frequencyRegionforCI in timeFrequencyRegion T CI : The PDCCH monitoring period of the search space set according to DCI format 2_4 is one slot, and multiple P DCCH monitoring If an opportunity exists, the symbol for the reception of the SS/PBCH block from a number of symbols provided by timeDurationforCI in timeFrequencyRegion or otherwise equal to the PDCCH monitoring period and tdd-UL-DL-ConfigurationCommon. It is specified that the number of symbols excluding the DL symbols indicated by GCI : the number of partitions for TCI symbols provided by timeGranularityforCI in timeFrequencyRegion is indicated.
  • the G CI bit set from the MSB of the N CI bits has a one-to-one mapping with the G CI symbol groups, with the first Each group of symbols and the remaining Each group of It is specified that the symbol contains 1 symbol.
  • the UE determines the symbol period for the active DL BWP SCS configuration monitoring the PDCCH for detection of DCI format 2_4. That is, in the time domain, the indicated symbols are divided into G CI sets.
  • N BI N CI /G CI bits from the MSB of each bit set have a one-to-one mapping with N BI PRB groups, with the first Each group of PRBs and the remaining Each group of PRBs are specified.
  • the UE shall specify the frequencyRegionforCI indicating the offset RB start and length L RB as the RIV and the O carrier for the SCS configuration of the active DL BWP where the UE monitors the PDCCH for detection of DCI format 2_4 according to TS38.214. From the FrequencyInfoUL- SIB or offsetToCarrier in FrequencyInfoUL that indicates It is stipulated that . That is, in the frequency domain, it is specified that for each symbol set, the RB is divided into N BI sets.
  • FIG. 33 shows an example division in the time domain and frequency domain by DCI 2_4.
  • the number of UL resource blocks (RBs) in different symbols may be different.
  • the frequency domain granularity may be finer than N BI RB sets in non-SBFD UL symbols.
  • Proposition 9 describes enhanced time-domain and frequency-domain cancellation for time-frequency division duplex operations such as SBFD operations. Specifically, UL cancellation in the time direction and UL cancellation in the time direction are enhanced as follows. Calculation of enhanced T CI in the time direction Case 1: When a UL subband is set to a resource set as UL in a TDD pattern ⁇ Alt 1> Include resources configured as DL in the TDD pattern. ⁇ Alt 2> Includes resources that are configured as DL in the TDD pattern and for which SBFD operation is not configured. Case 2: When a DL subband is configured for a resource configured as UL in a TDD pattern ⁇ Alt 1> Include resources configured as DL in the TDD pattern.
  • ⁇ Alt 2> Do not exclude symbols.
  • ⁇ Alt 3> Includes resources that are set as DL in the TDD pattern and are not used for SBFD operation. Case 3: If SBFD operation is not supported on the DL symbol, include the resource configured as DL in the TDD pattern. Enhancement in frequency direction ⁇ Alt 1> Divide frequency resources including DL subbands. ⁇ Alt 2> Divide the frequency resources excluding DL subbands.
  • SBFD operation in a UL symbol means a DL subband in a UL symbol that is designated as uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated
  • SBFD operation in a DL symbol may mean a UL subband in a DL symbol designated as downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.
  • Case 1 SBFD operation in DL symbols is supported/enabled and the SBFD operation (or DL/UL subband allocation) is signaled/ Set.
  • Case 2 SBFD operation in DL symbols is supported/enabled, and SBFD operation (or DL/UL subband allocation) is signaled/configured by UE-specific signaling (e.g., UE-specific RRC configuration or UE-specific DCI).
  • Case 3 SBFD operation in DL symbols is not supported/enabled.
  • ⁇ Case 1> SBFD operation in DL symbols is supported/enabled, and SBFD operation (or DL/UL subband allocation) is signaled by cell-specific/group-common signaling (e.g., cell-specific/group-common RRC configuration or DCI). / If set, the symbols deleted to obtain T CI symbols may be the symbols according to Alt 1 and/or Alt 2 below.
  • cell-specific/group-common signaling e.g., cell-specific/group-common RRC configuration or DCI.
  • the symbols removed for the downlink may include symbols designated as downlink by tdd-UL-DL-ConfigurationCommon.
  • Alt 1 is similar to Rel-15.
  • ⁇ Case 1 Alt 2>> In Alt 2, if SBFD operation in DL symbols is supported/enabled and SBFD operation (or DL/UL subband allocation) is notified/configured by cell-specific/group-common signaling, obtain T CI symbols. Symbols deleted for this purpose may include symbols that are indicated as downlink by tdd-UL-DL-ConfigurationCommon but are not configured/notified for SBFD operation. Since the SBFD DL symbols include UL subbands, there may be UL transmissions on the DL symbols. Therefore, the UL cancellation instruction by DCI 2_4 may be applicable to the DL symbol.
  • ⁇ Case 2> In case 2, if SBFD operation in DL symbols is supported/enabled and SBFD operation (or DL/UL subband allocation) is signaled/configured by UE-specific signaling, T The symbols displayed may be symbols according to Alt 1, Alt 2, and/or Alt 3 below.
  • ⁇ Case 2 Alt 1>> In Alt 1, if SBFD operation in DL symbols is supported/enabled and SBFD operation (or DL/UL subband allocation) is signaled/configured by UE-specific signaling, TCI symbols are removed to obtain TCI symbols.
  • the symbols configured may include symbols designated as downlink by tdd-UL-DL-ConfigurationCommon.
  • Alt 1 is similar to Rel-15.
  • ⁇ Case 2 Alt 2>> In Alt 2, if SBFD operation in DL symbols is supported/enabled and SBFD operation (or DL/UL subband allocation) is notified/configured by UE-specific signaling, no symbol may need to be deleted. In case 2, a particular UE is not sure whether the DL symbol is present in the UL subband for other UEs in the cell. Therefore, DL symbols may not be deleted for DCI 2_4 indications.
  • ⁇ Case 2 Alt 3>>
  • T The symbols designated as downlink by the tdd-UL-DL-ConfigurationCommon may include symbols reserved for non-SBFD operation as defined by the specification or RRC configuration, if present. For example, SSB symbols/slots may be reserved for non-SBFD operations.
  • a particular DL symbol e.g. SSB symbol
  • RRC Radio Resource Control
  • ⁇ Case 3> In case 3, if SBFD operation in DL symbols is not supported/enabled, the symbols removed to obtain TCI symbols are the symbols indicated as downlink by tdd-UL-DL-ConfigurationCommon. May include. This is similar to Rel-15.
  • resource blocks (RBs) applicable to each bit pair of a symbol group may be determined by Alt 1 and/or Alt 2 below.
  • ⁇ Alt 1> In Alt 1, for the applicable RB for each bit pair in a symbol group, the first The group of PRBs and the remaining Each group of PRBs may be included. For example, as shown in FIG. 35, the frequency resources including the UL subband are evenly divided into two bit pairs.
  • the RB applicable to each bit pair of the symbol group may be determined by Alt 2-1 and/or Alt 2-2 below, depending on the UL band size of the symbol group.
  • a symbol group contains only SBFD symbols, and the SBFD symbols in the symbol group are on the same DL/UL subband with a total of B CI - UL PRBs on the UL subband in each SBFD symbol of the symbol group. If you have an allocation pattern, for the RB applicable to each bit pair of the symbol group, The group of PRBs and the remaining Each group of PRBs may be included. For example, as shown in FIG. 36, frequency resources that do not include DL subbands are equally divided into two bit pairs.
  • a symbol group contains only SBFD symbols, and the SBFD symbols in the symbol group are connected to the same DL/UL subband with a total of B CI-UL-subband UL subbands in each SBFD symbol of the symbol group. If you have an allocation pattern, for the RB applicable to each bit pair of the symbol group, The group of UL subbands and the remaining Each group of UL subbands may be included. For example, as shown in FIG. 37, a frequency resource that does not include a DL subband is divided into two UL subbands for two bit pairs.
  • Alts to apply may be specified explicitly or implicitly by the specifications, may be semi-statically set by RRC, or may be dynamically notified by DCI. However, it may also be determined by rules. For example, a parameter instructing which Alt to apply may be transmitted in at least one of RRC, DCI, and MAC CE (Medium Access Control Element).
  • the UE adjusts the radio resources indicated by the downlink control information with respect to the time domain or the frequency domain in uplink transmission of time frequency division duplex operation such as SBFD operation, and performs uplink in the adjusted radio resources.
  • a link channel may also be transmitted.
  • the time frequency division duplexing may be SBFD, for example, the uplink channel may be PUCCH, PUSCH, etc., and the downlink control information may be DCI 2_4.
  • radio resources are resources defined by time units such as symbols and frequency units such as resource blocks.
  • the UE may exclude time units configured as uplink through time division duplexing (TDD) configuration from the radio resources indicated by the downlink control information. That is, for UL cancellation in the time domain, the UE excludes symbols configured as DL by TDD configuration such as tdd-UL-DL-ConfigurationCommon in order to obtain T CI symbols for UL cancellation. It's okay.
  • TDD time division duplexing
  • the UE may exclude downlink subbands in SBFD operation from the radio resources indicated by the downlink control information. That is, for frequency-domain UL cancellation, the UE transmits an uplink channel in a frequency band that includes the DL subband or a frequency band that does not include the DL subband in SBFD operation, as shown in FIGS. 35 to 37. It's okay.
  • the gNB in uplink reception of time-frequency division duplexing operations such as SBFD operations, uses uplink radio resources that are coordinated in the time domain or frequency domain with respect to the radio resources indicated by the downlink control information. It is also possible to control the terminal to transmit a channel and transmit an uplink channel.
  • the time frequency division duplexing may be SBFD, for example, the uplink channel may be PUCCH, PUSCH, etc., and the downlink control information may be DCI 2_4.
  • radio resources are resources defined by time units such as symbols and frequency units such as resource blocks.
  • UE Capability For cancellation in time frequency division duplex operations such as SBFD operations, UE capability information may be defined that indicates whether the UE supports enhanced DCI 2_4 for time frequency division duplex operations. Additionally, UE capability information regarding cancellation for time frequency division duplexing such as SBFD operation may be defined. If supporting enhanced cancellation for time frequency division duplex operation, the UE shall provide UE capability information indicating that it supports enhanced DCI 2_4 for time frequency division duplex operation. It may also be sent to gNB. Upon receiving the UE capability information, the gNB may send the enhanced DCI 2_4 for time frequency division duplex operation to the UE and cause the UE to perform cancellation in SBFD operation.
  • each functional block may be realized using one physically or logically coupled device, or may be realized using two or more physically or logically separated devices directly or indirectly (e.g. , wired, wireless, etc.) and may be realized using a plurality of these devices.
  • the functional block may be realized by combining software with the one device or the plurality of devices.
  • Functions include judgment, decision, judgment, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, These include, but are not limited to, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assigning. I can't.
  • a functional block (configuration unit) that performs transmission is called a transmitting unit or a transmitter. In either case, as described above, the implementation method is not particularly limited.
  • a base station, a user terminal, etc. in an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure.
  • FIG. 38 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment of the present disclosure.
  • the base station 10 and user terminal 20 described above may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc. .
  • the word “apparatus” can be read as a circuit, a device, a unit, etc.
  • the hardware configuration of the base station 10 and user terminal 20 may be configured to include one or more of each device shown in FIG. 38, or may be configured not to include some of the devices.
  • Each function in the base station 10 and user terminal 20 is performed by loading predetermined software (programs) onto hardware such as a processor 1001 and a memory 1002, so that the processor 1001 performs calculations and controls communication by the communication device 1004. This is realized by controlling at least one of data reading and writing in the memory 1002 and the storage 1003.
  • the processor 1001 operates an operating system to control the entire computer.
  • the processor 1001 may be configured by a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, registers, and the like.
  • CPU central processing unit
  • the baseband signal processing section 104, call processing section 105, etc. described above may be implemented by the processor 1001.
  • the processor 1001 reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 to the memory 1002, and executes various processes in accordance with these.
  • programs program codes
  • software modules software modules
  • data etc.
  • the program a program that causes a computer to execute at least part of the operations described in the above embodiments is used.
  • the control unit 401 of the user terminal 20 may be realized by a control program stored in the memory 1002 and operated in the processor 1001, and other functional blocks may be similarly realized.
  • Processor 1001 may be implemented by one or more chips. Note that the program may be transmitted from a network via a telecommunications line.
  • the memory 1002 is a computer-readable recording medium, and includes at least one of ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. may be done.
  • Memory 1002 may be called a register, cache, main memory, or the like.
  • the memory 1002 can store executable programs (program codes), software modules, and the like to implement a wireless communication method according to an embodiment of the present disclosure.
  • the storage 1003 is a computer-readable recording medium, such as an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (such as a compact disk, a digital versatile disk, or a Blu-ray disk). (registered trademark disk), smart card, flash memory (eg, card, stick, key drive), floppy disk, magnetic strip, etc.
  • Storage 1003 may also be called an auxiliary storage device.
  • the storage medium mentioned above may be, for example, a database including at least one of memory 1002 and storage 1003, a server, or other suitable medium.
  • the communication device 1004 is hardware (transmission/reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, network controller, network card, communication module, etc.
  • the communication device 1004 includes, for example, a high frequency switch, a duplexer, a filter, a frequency synthesizer, etc. in order to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). It may be composed of.
  • FDD frequency division duplex
  • TDD time division duplex
  • the transmitter/receiver 103 may be implemented as a transmitter 103a and a receiver 103b that are physically or logically separated.
  • the input device 1005 is an input device (eg, keyboard, mouse, microphone, switch, button, sensor, etc.) that accepts input from the outside.
  • the output device 1006 is an output device (for example, a display, a speaker, an LED lamp, etc.) that performs output to the outside. Note that the input device 1005 and the output device 1006 may have an integrated configuration (for example, a touch panel).
  • each device such as the processor 1001 and the memory 1002 is connected by a bus 1007 for communicating information.
  • the bus 1007 may be configured using a single bus, or may be configured using different buses for each device.
  • the base station 10 and the user terminal 20 also include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), and a field programmable gate array (FPGA). It may be configured to include hardware, and a part or all of each functional block may be realized by the hardware. For example, processor 1001 may be implemented using at least one of these hardwares.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • PLD programmable logic device
  • FPGA field programmable gate array
  • the notification of information may include physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), upper layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, It may be implemented using broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals, or a combination thereof.
  • RRC signaling may be called an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.
  • LTE Long Term Evolution
  • LTE-A Long Term Evolution-Advanced
  • SUPER 3G IMT-Advanced
  • 4G 4th generation mobile communication system
  • 5G 5th generation mobile communication system
  • 6G 6th generation mobile communication system
  • xG xth generation mobile communication system
  • xG xG (x is, for example, an integer or decimal)
  • FRA Fluture Radio Access
  • NR new Radio
  • New radio access NX
  • Future generation radio access FX
  • W-CDMA registered trademark
  • GSM registered trademark
  • CDMA2000 Code Division Multiple Access 2000
  • UMB Userltra Mobile Broadband
  • IEEE 802.11 Wi-Fi (registered trademark)
  • IEEE 802 .16 WiMAX (registered trademark)
  • IEEE 802.20 UWB (Ultra-WideBand
  • Bluetooth registered trademark
  • the specific operations performed by the base station in this disclosure may be performed by its upper node.
  • various operations performed for communication with a terminal are performed by the base station and other network nodes other than the base station (e.g., MME or It is clear that this could be done by at least one of the following: (conceivable, but not limited to) S-GW, etc.).
  • MME mobile phone
  • S-GW network node
  • Information can be output from the upper layer (or lower layer) to the lower layer (or upper layer). It may be input/output via multiple network nodes.
  • the input/output information may be stored in a specific location (for example, memory) or may be managed using a management table. Information etc. to be input/output may be overwritten, updated, or additionally written. The output information etc. may be deleted. The input information etc. may be transmitted to other devices.
  • Judgment may be made using a value expressed by 1 bit (0 or 1), a truth value (Boolean: true or false), or a comparison of numerical values (for example, a predetermined value). (comparison with a value).
  • notification of prescribed information is not limited to being done explicitly, but may also be done implicitly (for example, not notifying the prescribed information). Good too.
  • Software includes instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, whether referred to as software, firmware, middleware, microcode, hardware description language, or by any other name. , should be broadly construed to mean an application, software application, software package, routine, subroutine, object, executable, thread of execution, procedure, function, etc.
  • software, instructions, information, etc. may be sent and received via a transmission medium.
  • a transmission medium For example, if the software uses wired technology (coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), etc.) and/or wireless technology (infrared, microwave, etc.) to create a website, When transmitted from a server or other remote source, these wired and/or wireless technologies are included within the definition of transmission medium.
  • wired technology coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), etc.
  • wireless technology infrared, microwave, etc.
  • data, instructions, commands, information, signals, bits, symbols, chips, etc. which may be referred to throughout the above description, may refer to voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any of these. It may also be represented by a combination of
  • At least one of the channel and the symbol may be a signal.
  • the signal may be a message.
  • a component carrier may also be called a carrier frequency, a cell, a frequency carrier, or the like.
  • system and “network” are used interchangeably.
  • radio resources may be indicated by an index.
  • Base Station BS
  • wireless base station fixed station
  • NodeB NodeB
  • eNodeB eNodeB
  • gNodeB gNodeB
  • a base station is sometimes referred to by terms such as macrocell, small cell, femtocell, and picocell.
  • a base station can accommodate one or more (eg, three) cells. If a base station accommodates multiple cells, the overall coverage area of the base station can be partitioned into multiple smaller areas, and each smaller area is divided into multiple subsystems (e.g., small indoor base stations (RRHs)). Communication services may also be provided by a remote radio head).
  • RRHs small indoor base stations
  • Communication services may also be provided by a remote radio head).
  • the term "cell” or “sector” refers to a portion or the entire coverage area of a base station and/or base station subsystem that provides communication services in this coverage. refers to
  • the base station transmitting information to the terminal may be read as the base station instructing the terminal to control/operate based on the information.
  • MS Mobile Station
  • UE User Equipment
  • a mobile station is defined by a person skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless It may also be referred to as a terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.
  • At least one of a base station and a mobile station may be called a transmitting device, a receiving device, a communication device, etc.
  • the base station and the mobile station may be a device mounted on a mobile body, the mobile body itself, or the like.
  • the moving body refers to a movable object, and the moving speed is arbitrary. Naturally, this also includes cases where the moving object is stopped.
  • the mobile objects include, for example, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, carts, rickshaws, ships and other watercraft.
  • the mobile object may be a mobile object that autonomously travels based on a travel command. It may be a vehicle (e.g. car, airplane, etc.), an unmanned moving object (e.g. drone, self-driving car, etc.), or a robot (manned or unmanned). good.
  • the base station and the mobile station includes devices that do not necessarily move during communication operations.
  • at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.
  • IoT Internet of Things
  • the base station in the present disclosure may be replaced by a user terminal.
  • communication between a base station and a user terminal is replaced with communication between multiple user terminals (for example, it may be called D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.).
  • D2D Device-to-Device
  • V2X Vehicle-to-Everything
  • each aspect/embodiment of the present disclosure may be applied.
  • the user terminal 20 may have the functions that the base station 10 described above has.
  • words such as "up” and “down” may be replaced with words corresponding to inter-terminal communication (for example, "side”).
  • uplink channels, downlink channels, etc. may be replaced with side channels.
  • the user terminal in the present disclosure may be replaced with a base station.
  • the base station 10 may have the functions that the user terminal 20 described above has.
  • FIG. 39 shows an example of the configuration of the vehicle 1.
  • 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 It includes sensors 21 to 29, an information service section 12, and a communication module 13.
  • the drive unit 2 is composed of, for example, an engine, a motor, or a hybrid of an engine and a motor.
  • the steering unit 3 includes at least a steering wheel (also referred to as a steering wheel), and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel operated by the user.
  • a steering wheel also referred to as a steering wheel
  • the electronic control unit 10 is composed of a microprocessor 31, memory (ROM, RAM) 32, and 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 called an ECU (Electronic Control Unit).
  • the signals from the various sensors 21 to 28 include a current signal from the current sensor 21 that senses the motor current, a front wheel and rear wheel rotation speed signal obtained by the rotation speed sensor 22, and a front wheel rotation speed signal obtained by the air pressure sensor 23. and a rear wheel air pressure signal, a vehicle speed signal obtained by the vehicle speed sensor 24, an acceleration signal obtained by the acceleration sensor 25, an accelerator pedal depression amount signal obtained by the accelerator pedal sensor 29, and a signal obtained by the brake pedal sensor 26.
  • These include a brake pedal depression amount signal, a shift lever operation signal acquired by the shift lever sensor 27, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. acquired by the object detection sensor 28.
  • the information service unit 12 controls various devices such as a car navigation system, audio system, speakers, television, and radio for providing (outputting) various information such as driving information, traffic information, and entertainment information, and these devices. It is composed of one or more ECUs.
  • the information service unit 12 provides various multimedia information and multimedia services to the occupants of the vehicle 1 using information acquired from an external device via the communication module 13 or the like.
  • the information service unit 12 may include an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, a touch panel, etc.) that accepts input from the outside, and an output device (for example, (display, speaker, LED lamp, touch panel, etc.).
  • an input device for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, a touch panel, etc.
  • an output device for example, (display, speaker, LED lamp, touch panel, etc.).
  • the driving support system unit 30 includes a millimeter wave radar, LiDAR (Light Detection and Ranging), a camera, a positioning locator (for example, GNSS, etc.), map information (for example, a high-definition (HD) map, an autonomous vehicle (AV) map, etc.) ), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors that prevent accidents and reduce the driver's driving burden.
  • the system is comprised of various devices that provide functions for the purpose and one or more ECUs that control these devices. Further, the driving support system unit 30 transmits and receives various information via the communication module 13, and realizes a driving support function or an automatic driving function.
  • the communication module 13 can communicate with the microprocessor 31 and the components of the vehicle 1 via the communication port.
  • the communication module 13 communicates via the communication port 33 with the drive unit 2, steering unit 3, accelerator pedal 4, brake pedal 5, shift lever 6, left and right front wheels 7, left and right rear wheels 8, which are included in the vehicle 1.
  • Data is transmitted and received between the axle 9, the microprocessor 31 and memory (ROM, RAM) 32 in the electronic control unit 10, and the sensors 21-28.
  • the communication module 13 is a communication device that can be controlled by the microprocessor 31 of the electronic control unit 10 and can communicate with external devices. For example, various information is transmitted and received with an external device via wireless communication.
  • the communication module 13 may be located either inside or outside the electronic control unit 10.
  • the external device may be, for example, a base station, a mobile station, or the like.
  • the communication module 13 receives signals from the various sensors 21 to 28 described above that are input to the electronic control unit 10, information obtained based on the signals, and input from the outside (user) obtained via the information service unit 12. At least one of the information based on the information may be transmitted to an external device via wireless communication.
  • the electronic control unit 10, various sensors 21-28, information service unit 12, etc. may be called an input unit that receives input.
  • the PUSCH transmitted by the communication module 13 may include information based on the above input.
  • the communication module 13 receives various information (traffic information, signal information, inter-vehicle distance information, etc.) transmitted from external devices, and displays it on the information service section 12 provided in the vehicle.
  • the information service unit 12 is an output unit that outputs information (for example, outputs information to devices such as a display and a speaker based on the PDSCH (or data/information decoded from the PDSCH) received by the communication module 13). may be called.
  • the communication module 13 also stores various information received from external devices into a memory 32 that can be used by the microprocessor 31. Based on the information stored in the memory 32, the microprocessor 31 controls the drive unit 2, steering unit 3, accelerator pedal 4, brake pedal 5, shift lever 6, left and right front wheels 7, and left and right rear wheels provided in the vehicle 1. 8, the axle 9, sensors 21 to 28, etc. may be controlled.
  • 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 downlink data channel a control unit that controls a reception operation of the downlink data channel depending on whether or not the downlink data channels overlap, and a reception unit that executes a reception operation of the downlink data channel according to the controlled reception operation.
  • a terminal having the following is provided.
  • the downlink data channel can be enhanced for time frequency division duplex operation.
  • the controller may control whether the downlink data channel overlaps the uplink time unit in the non-time frequency division duplex operation.
  • the downlink data channel may be received in time units that do not overlap with uplink time units in operation. 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.
  • the controller may control whether the downlink data channel overlaps with an uplink subband in the time unit.
  • the receiving operation of the downlink data channel may be controlled regardless of whether it is wrapped or not. 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.
  • the controller may control whether the downlink data channel overlaps with an uplink subband in the time unit.
  • the reception operation of the downlink data channel may be controlled depending on whether the downlink data channel is wrapped or not. 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.
  • the transmission operation of the downlink data channel is controlled 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.
  • a base station is provided, the base station having a controller and a transmitter configured to perform a transmission operation of the downlink data channel according to the controlled transmission operation.
  • the downlink data channel can be enhanced for time frequency division duplex operation.
  • a downlink data channel overlaps 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. controlling the reception operation of the downlink data channel depending on whether the terminal is in the terminal; and performing the reception operation of the downlink data channel by the controlled reception operation.
  • a wireless communication method is provided.
  • the downlink data channel can be enhanced for time frequency division duplex operation.
  • a downlink data channel overlaps 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.
  • a terminal is provided, the terminal having a control unit that controls a reception operation of the downlink data channel depending on whether or not the downlink data channel is received. Ru.
  • the downlink data channel can be enhanced for time frequency division duplex operation.
  • the controller may control the multiple opportunities of the downlink data channel. may be interpreted as not being sent. 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.
  • the controller may control the downlink data channel opportunities to The reception operation of the downlink data channel may be controlled regardless of whether it overlaps with an uplink subband in a 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.
  • the controller may control whether the downlink data channel is an uplink data channel in the time unit.
  • the reception operation of the downlink data channel may be controlled depending on whether or not the downlink data channel overlaps with the subband. 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.
  • the transmission operation of the downlink data channel is controlled 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.
  • a base station is provided, the base station having a controller and a transmitter configured to perform a transmission operation of the downlink data channel according to the controlled transmission operation.
  • the downlink data channel can be enhanced for time frequency division duplex operation.
  • a downlink data channel overlaps 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. controlling the reception operation of the downlink data channel depending on whether the terminal is in the terminal; and performing the reception operation of the downlink data channel by the controlled reception operation.
  • a wireless communication method is provided.
  • the downlink data channel can be enhanced for time frequency division duplex operation.
  • control unit determines a HARQ-ACK codebook for the downlink data channel depending on whether the downlink data channel overlaps with an uplink time unit;
  • a terminal is provided that includes a transmitter that transmits an acknowledgment according to a HARQ-ACK codebook.
  • HARQ-ACK can be enhanced for time frequency division duplex operation.
  • the control unit may exclude the SPS PDSCH from determining the HARQ-ACK codebook. good. According to this embodiment, enhanced HARQ-ACK in time frequency division duplex operation and non-time frequency division duplex operation can be provided.
  • the control unit determines the SLIV from the determination of the HARQ-ACK codebook. may be excluded. According to this embodiment, enhanced HARQ-ACK in time frequency division duplex operation and non-time frequency division duplex operation can be provided.
  • the controller determines a HARQ-ACK codebook for the downlink data channel depending on whether time frequency division duplexing operation is semi-statically configured or dynamically signaled. You may. According to this embodiment, enhanced HARQ-ACK in time frequency division duplex operation and non-time frequency division duplex operation can be provided.
  • a transmitter that transmits a downlink data channel; and the downlink data channel determined depending on whether the downlink data channel overlaps with an uplink time unit.
  • a receiving unit for receiving an acknowledgment according to a HARQ-ACK codebook for a base station.
  • HARQ-ACK can be enhanced for time frequency division duplex operation.
  • HARQ-ACK can be enhanced for time frequency division duplex operation.
  • an uplink data channel overlaps 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.
  • a terminal is provided, the terminal having a control unit that controls a transmission operation of the uplink data channel depending on whether the transmission operation is controlled, and a transmission unit that performs a transmission operation of the uplink data channel according to the controlled transmission operation. Ru.
  • the uplink data channel can be enhanced for time frequency division duplexing operation.
  • the controller may configure the uplink data channel to overlap the downlink time unit in the non-time frequency division duplex operation.
  • the uplink data channel may be transmitted in time units that do not overlap with downlink time units in operation. 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.
  • the controller may control whether the uplink data channel overlaps with a downlink subband in the time unit.
  • the transmitting operation of the uplink data channel may be controlled regardless of whether it is wrapped or not. 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.
  • the controller may control whether the uplink data channel overlaps with a downlink subband in the time unit.
  • the transmission operation of the uplink data channel may be controlled depending on whether the uplink data channel is wrapped or not. 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.
  • the receiving operation of an uplink data channel is controlled 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.
  • a base station is provided, the base station having a controller and a receiver configured to perform a reception operation of the uplink data channel according to the controlled reception operation.
  • the uplink data channel can be enhanced for time frequency division duplexing operation.
  • an uplink data channel overlaps 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. controlling the transmission operation of the uplink data channel depending on whether the transmission operation is performed by the terminal; and performing the transmission operation of the uplink data channel by the controlled transmission operation.
  • a wireless communication method is provided.
  • the uplink data channel can be enhanced for time frequency division duplexing operation.
  • an uplink data channel overlaps 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.
  • a terminal is provided, the terminal having a control unit that controls a transmission operation of the uplink data channel depending on whether the transmission operation is controlled, and a transmission unit that performs a transmission operation of the uplink data channel according to the controlled transmission operation. Ru.
  • the uplink data channel can be enhanced for time frequency division duplexing operation.
  • the controller may include a non-time frequency division duplex downlink time unit or a time frequency division duplex time unit as an invalid time unit for repeated transmission of the uplink data channel.
  • 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.
  • the controller determines an invalid time unit for repeated transmission of the uplink data channel depending on whether the time frequency division duplexing is dynamically signaled or semi-statically configured. You may decide. 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.
  • the controller is configured to control when the actual repetition after segmentation for repeated transmission of the uplink data channel overlaps with a downlink subband when the actual repetition after segmentation overlaps with a time frequency division duplex time unit.
  • the actual repeated transmission operation may be controlled depending on the presence or absence of the above. 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.
  • a control unit that controls uplink data channel reception operation in one or both of a downlink time unit in a non-time frequency division duplex operation and a time unit in an SBFD operation; and a receiving unit that performs a receiving operation of the uplink data channel by the controlled receiving operation.
  • the uplink data channel can be enhanced for time frequency division duplexing operation.
  • an uplink data channel overlaps 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. controlling the transmission operation of the uplink data channel depending on whether the transmission operation is performed by the terminal; and performing the transmission operation of the uplink data channel by the controlled transmission operation.
  • a wireless communication method is provided.
  • the uplink data channel can be enhanced for time frequency division duplexing operation.
  • an uplink control channel overlaps 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.
  • a terminal is provided, the terminal having a control unit that controls a transmission operation of the uplink control channel depending on whether or not the uplink control channel is transmitted. Ru.
  • the uplink control channel can be enhanced for time frequency division duplexing operation.
  • the controller may configure the uplink control channel to overlap the downlink time unit in the non-time frequency division duplex operation.
  • the uplink control channel may be transmitted in time units that do not overlap with downlink time units in operation. 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.
  • the controller may control whether the uplink control channel overlaps with a downlink subband in the time unit.
  • the transmission operation of the uplink control channel may be controlled regardless of whether it is wrapped or not. 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.
  • the controller may control whether the uplink control channel overlaps with a downlink subband in the time unit.
  • the transmission operation of the uplink control channel may be controlled depending on whether the uplink control channel is wrapped or not. 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.
  • the reception operation of an uplink control channel is controlled 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.
  • a base station is provided that includes a controller and a receiver that performs a reception operation of the uplink control channel according to the controlled reception operation.
  • the uplink control channel can be enhanced for time frequency division duplexing operation.
  • an uplink control channel overlaps 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. controlling the transmission operation of the uplink control channel depending on whether the transmission operation is performed by the terminal; and performing the transmission operation of the uplink control channel by the controlled transmission operation.
  • a wireless communication method is provided.
  • the uplink control channel can be enhanced for time frequency division duplexing operation.
  • a terminal comprising a controller and a transmitter that defers transmission of the HARQ-ACK uplink control channel according to the deferral operation.
  • the controller is configured such that the semi-persistent scheduling HARQ-ACK (SPS HARQ-ACK) is a non-time frequency division duplex semi-static downlink time unit, a synchronization signal block (SSB) time unit or a type-0
  • SPS HARQ-ACK semi-persistent scheduling HARQ-ACK
  • SSB synchronization signal block
  • the HARQ-ACK deferral operation may be enabled when it overlaps with a CORESET (Control Resource Set) time unit.
  • CORESET Control Resource Set
  • the controller is configured such that the semi-persistent scheduling HARQ-ACK (SPS HARQ-ACK) is a non-time frequency division duplex semi-static downlink time unit, a synchronization signal block (SSB) time unit or a type-0
  • SPS HARQ-ACK semi-persistent scheduling HARQ-ACK
  • SSB synchronization signal block
  • the HARQ-ACK deferral operation may be enabled when it overlaps with a CORESET (Control Resource Set) time unit or when it overlaps with a time frequency division duplex semi-static/dynamic time unit.
  • CORESET Control Resource Set
  • enhanced HARQ-ACK deferral operations can be provided in time frequency division duplex operations and non-time frequency division duplex operations.
  • the controller is configured to transmit semi-persistent scheduling HARQ-ACK (SPS HARQ-ACK) to a non-SBFD semi-static downlink time unit, a synchronization signal block (SSB) time unit, or a type-0 CORESET (Control Resource). Set) may enable the HARQ-ACK deferral operation when overlapping a time unit or when overlapping a downlink subband in a time frequency division duplex semi-static/dynamic time unit.
  • SPS HARQ-ACK semi-persistent scheduling HARQ-ACK
  • SSB synchronization signal block
  • Set may enable the HARQ-ACK deferral operation when overlapping a time unit or when overlapping a downlink subband in a time frequency division duplex semi-static/dynamic time unit.
  • enhanced HARQ-ACK deferral operations can be provided in time frequency division duplex operations and non-time frequency division duplex operations.
  • a transmission unit that transmits a downlink data channel and a HARQ-ACK postponement condition in a time frequency division duplex operation and a non-time frequency division duplex operation for the downlink data channel are configured.
  • a receiving unit for receiving the uplink control channel of the HARQ-ACK deferred according to an enabled deferral operation when satisfied.
  • the HARQ-ACK postpone operation is enabled. and deferring transmission of the HARQ-ACK uplink control channel in accordance with the deferral operation.
  • a control unit that adjusts radio resources instructed by downlink control information in the time domain or frequency domain;
  • a terminal is provided having a receiving unit for receiving a downlink channel on wireless resources.
  • preemption can be enhanced for time frequency division duplex operation.
  • control unit may exclude a time unit configured as uplink by time division duplexing (TDD) configuration from the radio resources indicated by the downlink control information.
  • TDD time division duplexing
  • control unit may exclude uplink subbands in the time frequency division duplexing operation from the radio resources indicated by the downlink control information. According to this embodiment, enhanced preemption can be provided in time frequency division duplex operations and non-time frequency division duplex operations.
  • downlink in downlink transmission of time frequency division duplexing operation, downlink is performed in a radio resource that is adjusted in the time domain or in the frequency domain with respect to the radio resource indicated by the downlink control information.
  • a base station is provided that includes a controller that controls a terminal to receive a channel, and a transmitter that transmits the downlink channel.
  • preemption can be enhanced for time frequency division duplex operation.
  • the radio resources indicated by the downlink control information are adjusted in the time domain or the frequency domain, and the adjusted radio
  • a wireless communication method performed by a terminal comprising: receiving a downlink channel on a resource.
  • preemption can be enhanced for time frequency division duplex operation.
  • a control unit that adjusts radio resources indicated by downlink control information in the time domain or frequency domain;
  • a terminal having a transmitter configured to transmit an uplink channel on wireless resources.
  • cancellation can be enhanced for time frequency division duplex operation.
  • control unit may exclude a time unit configured as a downlink by a time division duplex (TDD) configuration from the radio resources indicated by the downlink control information.
  • TDD time division duplex
  • control unit may exclude a 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.
  • a base station in uplink reception of time frequency division duplexing operation, uplink in radio resources adjusted in the time domain or frequency domain with respect to radio resources indicated by downlink control information.
  • a base station is provided, the base station having a controller that controls a terminal to transmit a channel, and a receiver that receives the uplink channel.
  • cancellation can be enhanced for time frequency division duplex operation.
  • a wireless communication method performed by a terminal comprising: transmitting an uplink channel on a resource.
  • cancellation can be enhanced for time frequency division duplex operation.
  • determining may encompass a wide variety of operations.
  • “Judgment” and “decision” include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, search, and inquiry. (e.g., searching in a table, database, or other data structure), and regarding an ascertaining as a “judgment” or “decision.”
  • judgment and “decision” refer to receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, and access.
  • (accessing) may include considering something as a “judgment” or “decision.”
  • judgment and “decision” refer to resolving, selecting, choosing, establishing, comparing, etc. as “judgment” and “decision”. may be included.
  • judgment and “decision” may include regarding some action as having been “judged” or “determined.”
  • judgment (decision) may be read as “assuming", “expecting", “considering”, etc.
  • connection refers to any connection or coupling, direct or indirect, between two or more elements and to each other. It may include the presence of one or more intermediate elements between two elements that are “connected” or “coupled.”
  • the bonds or connections between elements may be physical, logical, or a combination thereof. For example, "connection” may be replaced with "access.”
  • two elements may include one or more electrical wires, cables, and/or printed electrical connections, as well as in the radio frequency domain, as some non-limiting and non-inclusive examples. , electromagnetic energy having wavelengths in the microwave and optical (both visible and non-visible) ranges.
  • the reference signal can also be abbreviated as RS (Reference Signal), and may be called a pilot depending on the applied standard.
  • RS Reference Signal
  • the phrase “based on” does not mean “based solely on” unless explicitly stated otherwise. In other words, the phrase “based on” means both “based only on” and “based at least on.”
  • any reference to elements using the designations "first,” “second,” etc. does not generally limit the amount or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Thus, reference to a first and second element does not imply that only two elements may be employed or that the first element must precede the second element in any way.
  • a radio frame may be composed of one or more frames in the time domain. Each frame or frames in the time domain may be called a subframe. A subframe may also be composed of one or more slots in the time domain. A subframe may have a fixed time length (eg, 1 ms) that does not depend on numerology.
  • the numerology may be a communication parameter applied to the transmission and/or reception of a certain signal or channel. Numerology includes, for example, subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, transmission and reception. It may also indicate at least one of a specific filtering process performed by the device in the frequency domain, a specific windowing process performed by the transceiver in the time domain, etc.
  • SCS subcarrier spacing
  • TTI transmission time interval
  • the numerology may also indicate at least one of a specific filtering process performed by the device in the frequency domain, a specific windowing process performed by the transceiver in the time domain, etc.
  • a slot may be composed of one or more symbols (OFDM (Orthogonal Frequency Division Multiplexing) symbols, SC-FDMA (Single Carrier Frequency Division Multiple Access) symbols, etc.) in the time domain.
  • a slot may be a unit of time based on numerology.
  • a slot may include multiple mini-slots. Each minislot may be made up of one or more symbols in the time domain. Furthermore, a mini-slot may also be called a sub-slot. A minislot may be made up of fewer symbols than a slot.
  • PDSCH (or PUSCH) transmitted in time units larger than minislots may be referred to as PDSCH (or PUSCH) mapping type A.
  • PDSCH (or PUSCH) transmitted using minislots may be referred to as PDSCH (or PUSCH) mapping type B.
  • Radio frames, subframes, slots, minislots, and symbols all represent time units when transmitting signals. Other names may be used for the radio frame, subframe, slot, minislot, and symbol.
  • one subframe may be called a transmission time interval (TTI)
  • TTI transmission time interval
  • multiple consecutive subframes may be called a TTI
  • one slot or one minislot may be called a TTI. It's okay.
  • at least one of the subframe and TTI may be a subframe (1ms) in existing LTE, a period shorter than 1ms (for example, 1-13 symbols), or a period longer than 1ms. It may be.
  • the unit representing the TTI may be called a slot, minislot, etc. instead of a subframe.
  • TTI refers to, for example, the minimum time unit for scheduling in wireless communication.
  • a base station performs scheduling to allocate radio resources (frequency bandwidth, transmission power, etc. that can be used by each user terminal) to each user terminal on a TTI basis.
  • radio resources frequency bandwidth, transmission power, etc. that can be used by each user terminal
  • the TTI may be a transmission time unit of a channel-coded data packet (transport block), a code block, a codeword, etc., or may be a processing unit of scheduling, link adaptation, etc. Note that when a TTI is given, the time interval (for example, the number of symbols) to which transport blocks, code blocks, code words, etc. are actually mapped may be shorter than the TTI.
  • one slot or one minislot is called a TTI
  • one or more TTIs may be the minimum time unit for scheduling.
  • the number of slots (minislot number) that constitutes the minimum time unit of the scheduling may be controlled.
  • a TTI having a time length of 1 ms may be called a normal TTI (TTI in LTE Rel. 8-12), normal TTI, long TTI, normal subframe, normal subframe, long subframe, slot, etc.
  • TTI that is shorter than the normal TTI may be referred to as an abbreviated TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.
  • long TTI for example, normal TTI, subframe, etc.
  • short TTI for example, short TTI, etc. It may also be read as a TTI having the above TTI length.
  • a resource block is a resource allocation unit in the time domain and frequency domain, and may include one or more continuous subcarriers in the frequency domain.
  • the number of subcarriers included in an RB may be the same regardless of the numerology, and may be 12, for example.
  • the number of subcarriers included in an RB may be determined based on numerology.
  • the time domain of an RB may include one or more symbols, and may be one slot, one minislot, one subframe, or one TTI in length.
  • One TTI, one subframe, etc. may each be composed of one or more resource blocks.
  • one or more RBs include physical resource blocks (PRBs), sub-carrier groups (SCGs), resource element groups (REGs), PRB pairs, RB pairs, etc. May be called.
  • PRBs physical resource blocks
  • SCGs sub-carrier groups
  • REGs resource element groups
  • PRB pairs RB pairs, etc. May be called.
  • a resource block may be configured by one or more resource elements (REs).
  • REs resource elements
  • 1 RE may be a radio resource region of 1 subcarrier and 1 symbol.
  • Bandwidth Part (also referred to as partial bandwidth) refers to a subset of consecutive common resource blocks (RB) for a certain numerology in a certain carrier. good.
  • the common RB may be specified by an RB index based on a common reference point of the carrier.
  • PRBs may be defined in a BWP and numbered within that BWP.
  • the BWP may include a UL BWP (UL BWP) and a DL BWP (DL BWP).
  • UL BWP UL BWP
  • DL BWP DL BWP
  • One or more BWPs may be configured within one carrier for a UE.
  • At least one of the configured BWPs may be active and the UE may not expect to transmit or receive a given signal/channel outside of the active BWP.
  • “cell”, “carrier”, etc. in the present disclosure may be replaced with "BWP”.
  • radio frames, subframes, slots, minislots, symbols, etc. described above are merely examples.
  • the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of symbols included in an RB, Configurations such as the number of subcarriers, the number of symbols in a TTI, the symbol length, and the cyclic prefix (CP) length can be changed in various ways.
  • the "maximum transmit power” described in this disclosure may mean the maximum value of transmit power, the nominal maximum transmit power (the nominal UE maximum transmit power), or the rated maximum transmit power ( It may also mean the rated UE maximum transmit power).
  • a and B are different may mean “A and B are different from each other.” Note that the term may also mean that "A and B are each different from C”. Terms such as “separate” and “coupled” may also be interpreted similarly to “different.”
  • Wireless communication system 100 Base station (gNB) 200 Terminal (UE)
  • gNB Base station
  • UE Terminal

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Selon un mode de réalisation de la présente divulgation, l'invention concerne un terminal comprenant : une unité de commande qui commande une opération de transmission sur un canal de données d'application selon qu'il existe ou non un chevauchement entre le canal de données d'application et l'une ou les deux parmi une unité de temps de liaison descendante dans une opération de multiplexage qui n'est pas par répartition en fréquence et en temps et une unité de temps dans une opération de multiplexage par répartition en fréquence et en temps ; et une unité de transmission qui exécute une opération de transmission sur le canal d'application selon l'opération de transmission commandée.
PCT/JP2022/030681 2022-08-10 2022-08-10 Terminal, station de base et procédé de communication sans fil WO2024034096A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP2022/030681 WO2024034096A1 (fr) 2022-08-10 2022-08-10 Terminal, station de base et procédé de communication sans fil

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2022/030681 WO2024034096A1 (fr) 2022-08-10 2022-08-10 Terminal, station de base et procédé de communication sans fil

Publications (1)

Publication Number Publication Date
WO2024034096A1 true WO2024034096A1 (fr) 2024-02-15

Family

ID=89851169

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2022/030681 WO2024034096A1 (fr) 2022-08-10 2022-08-10 Terminal, station de base et procédé de communication sans fil

Country Status (1)

Country Link
WO (1) WO2024034096A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4033710A1 (fr) * 2019-10-11 2022-07-27 Samsung Electronics Co., Ltd. Procédé et appareil de configuration de ressource pour une transmission ou une réception d'une liaison montante ou d'une liaison descendante dans un système de communication sans fil

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4033710A1 (fr) * 2019-10-11 2022-07-27 Samsung Electronics Co., Ltd. Procédé et appareil de configuration de ressource pour une transmission ou une réception d'une liaison montante ou d'une liaison descendante dans un système de communication sans fil

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ASUSTEK: "Enhancement on dynamic TDD", 3GPP DRAFT; R1-2204638, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20220509 - 20220520, 29 April 2022 (2022-04-29), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052153612 *

Similar Documents

Publication Publication Date Title
WO2024034096A1 (fr) Terminal, station de base et procédé de communication sans fil
WO2024034099A1 (fr) Terminal, station de base et procédé de communication sans fil
WO2024034097A1 (fr) Terminal, station de base, et procédé de communication sans fil
WO2024034107A1 (fr) Terminal, station de base et procédé de communication sans fil
WO2024034100A1 (fr) Terminal, station de base, et procédé de communication sans fil
WO2024034108A1 (fr) Terminal, station de base et procédé de communication sans fil
WO2024181417A1 (fr) Terminal, station de base et procédé de communication sans fil
WO2023209918A1 (fr) Station de base et procédé de communication sans fil
WO2023209919A1 (fr) Station de base et procédé de communication sans fil
WO2023209916A1 (fr) Terminal, station de base et procédé de communication sans fil
WO2023209920A1 (fr) Terminal, station de base et procédé de communication sans fil
WO2024029052A1 (fr) Terminal et procédé de communication
WO2024023994A1 (fr) Terminal, station de base et procédé de communication sans fil
WO2024023987A1 (fr) Terminal, station de base et procédé de communication sans fil
WO2024034106A1 (fr) Terminal, et procédé de communication
WO2024023984A1 (fr) Terminal, station de base et procédé de communication sans fil
WO2024034105A1 (fr) Terminal, et procédé de communication
WO2023209779A1 (fr) Terminal et procédé de communication
WO2024062581A1 (fr) Terminal et procédé de communication
WO2023209780A1 (fr) Terminal et procédé de communication
WO2024084839A1 (fr) Terminal et procédé de communication
WO2024084829A1 (fr) Terminal et procédé de communication
WO2024034104A1 (fr) Terminal et procédé de communication
WO2024029053A1 (fr) Terminal et procédé de communication
WO2024029051A1 (fr) Terminal et procédé de communication

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22955012

Country of ref document: EP

Kind code of ref document: A1