WO2023209913A1 - 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
WO2023209913A1
WO2023209913A1 PCT/JP2022/019200 JP2022019200W WO2023209913A1 WO 2023209913 A1 WO2023209913 A1 WO 2023209913A1 JP 2022019200 W JP2022019200 W JP 2022019200W WO 2023209913 A1 WO2023209913 A1 WO 2023209913A1
Authority
WO
WIPO (PCT)
Prior art keywords
xdd
pdcch monitoring
pdcch
cell
uss
Prior art date
Application number
PCT/JP2022/019200
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/019200 priority Critical patent/WO2023209913A1/fr
Publication of WO2023209913A1 publication Critical patent/WO2023209913A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management

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
  • LTE Long Term Evolution
  • 5G 5th generation mobile communication system
  • 5G+ plus
  • 6th generation mobile communication system tem 6th generation mobile communication system tem
  • 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.
  • a receiving unit receives a notification or setting regarding XDD (Cross Division Duplex) operation for a radio resource, and controls uplink transmission or downlink reception in the wireless resource according to the notification or setting regarding the XDD operation.
  • a terminal having a control unit is provided.
  • a terminal is provided that includes a receiving unit that receives PDCCH monitoring settings for XDD (Cross Division Duplex) operation, and a control unit that controls PDCCH monitoring according to the PDCCH monitoring settings.
  • a terminal including a receiving unit that receives PDCCH monitoring capability regarding XDD (Cross Division Duplex) operation for radio resources, and a control unit that controls PDCCH monitoring according to the PDCCH monitoring capability.
  • a controller that controls PDCCH overbooking in XDD (Cross Division Duplex) time units in which PDCCH monitoring is configured;
  • a terminal having a receiving unit that performs monitoring is provided.
  • a controller that selects a PDCCH monitoring beam in an XDD (Cross Division Duplex) time unit in which PDCCH monitoring is set; and a receiver that performs PDCCH monitoring on the selected PDCCH monitoring beam.
  • a terminal having a section is provided.
  • FIG. 2 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.
  • FIG. 2 is a diagram illustrating an example of arrangement of XDD (Cross Division Duplex) radio resources according to an embodiment of the present disclosure.
  • FIG. 3 is a diagram illustrating an XDD operation according to an embodiment of the present disclosure.
  • FIG. 3 is a diagram illustrating pure time units and XDD time units according to one embodiment of the present disclosure.
  • FIG. 3 is a diagram illustrating PDCCH monitoring opportunities according to one embodiment of the present disclosure.
  • FIG. 3 is a diagram illustrating PDCCH overbooking according to an embodiment of the present disclosure.
  • FIG. 3 illustrates a PDCCH monitoring beam according to an embodiment of the present disclosure.
  • FIG. 3 is a diagram illustrating an example of setting an XDD according to an embodiment of the present disclosure.
  • FIG. 2 is a diagram illustrating an example of arrangement of radio resources for XDD according to an embodiment of the present disclosure.
  • FIG. 3 is a diagram illustrating an example of setting an XDD according to an embodiment of the present disclosure.
  • FIG. 2 is a diagram illustrating an example of arrangement of radio resources for XDD according to an embodiment of the present disclosure.
  • FIG. 2 is a diagram illustrating an example of setting an XDD and an example of arrangement of radio resources according to an embodiment of the present disclosure.
  • FIG. 2 is a diagram illustrating an example of setting an XDD and an example of arrangement of radio resources according to an embodiment of the present disclosure.
  • FIG. 3 is a diagram illustrating an example of setting an XDD according to an embodiment of the present disclosure.
  • FIG. 2 is a diagram illustrating an example of arrangement of radio resources for XDD according to an embodiment of the present disclosure.
  • FIG. 2 is a diagram illustrating an example of setting an XDD and an example of arrangement of radio resources according to an embodiment of the present disclosure.
  • FIG. 2 is a diagram illustrating an example of setting an XDD and an example of arrangement of radio resources according to an embodiment of the present disclosure.
  • FIG. 3 is a diagram illustrating an example of setting an XDD according to an embodiment of the present disclosure.
  • FIG. 2 is a diagram illustrating an example of arrangement of radio resources for XDD according to an embodiment of the present disclosure.
  • FIG. 2 is a diagram illustrating an example of setting an XDD and an example of arrangement of radio resources according to an embodiment of the present disclosure.
  • FIG. 2 is a diagram illustrating an example of setting an XDD and an example of arrangement of radio resources according to an embodiment of the present disclosure.
  • FIG. 3 is a diagram illustrating an example of setting an XDD according to an embodiment of the present disclosure.
  • FIG. 2 is a diagram illustrating an example of arrangement of radio resources for XDD according to an embodiment of the present disclosure.
  • FIG. 2 is a diagram illustrating an example of arrangement of radio resources for XDD according to an embodiment of the present disclosure.
  • FIG. 2 is a diagram illustrating an example of arrangement of radio resources for XDD according to an embodiment of the present disclosure.
  • FIG. 2 is a diagram illustrating an example of arrangement of radio resources for XDD according to an embodiment of the present disclosure.
  • FIG. 2 is a diagram illustrating an example of arrangement of radio resources for XDD according to an embodiment of the present disclosure.
  • FIG. 2 is a diagram illustrating an example of arrangement of radio resources for XDD according to an embodiment of the present disclosure.
  • FIG. 2 is a diagram illustrating an example of arrangement of radio resources for XDD according to an embodiment of the present disclosure.
  • FIG. 2 is a diagram illustrating an example of arrangement of radio resources for XDD according to an embodiment of the present disclosure.
  • FIG. 2 is a diagram illustrating an example of arrangement of radio resources for XDD according to an embodiment of the present disclosure.
  • FIG. 2 is a diagram illustrating an example of arrangement of radio resources for XDD according to an embodiment of the present disclosure.
  • FIG. 3 is a diagram illustrating the ability to monitor each release according to an embodiment of the present disclosure.
  • FIG. 2 is a diagram illustrating an example of arrangement of radio resources for XDD according to an embodiment of the present disclosure.
  • FIG. 2 is a diagram illustrating an example of arrangement of radio resources for XDD according to an embodiment of the present disclosure.
  • FIG. 3 is a diagram illustrating prioritization according to one embodiment of the present disclosure.
  • FIG. 3 is a diagram illustrating prioritization according to one embodiment of the present disclosure.
  • FIG. 2 is a diagram illustrating an example of arrangement of radio resources for XDD according to an embodiment of the present disclosure.
  • FIG. 3 is a diagram illustrating prioritization according to one embodiment of the present disclosure.
  • FIG. 3 is a diagram illustrating prioritization according to one embodiment of the present disclosure.
  • FIG. 2 is a diagram illustrating an example of arrangement of radio resources for XDD according to an embodiment of the present disclosure.
  • FIG. 3 is a diagram illustrating prioritization according to one embodiment of the present disclosure.
  • FIG. 3 is a diagram illustrating prioritization according to one embodiment of the present disclosure.
  • FIG. 3 is a diagram illustrating prioritization according to one embodiment of the present disclosure.
  • FIG. 3 is a diagram illustrating prioritization according to one embodiment of the present disclosure.
  • FIG. 3 is a diagram illustrating prioritization according to one embodiment of the present disclosure.
  • FIG. 3 is a diagram illustrating prioritization according to one embodiment of the present disclosure.
  • FIG. 3 is a diagram illustrating prioritization according to one embodiment of the present disclosure.
  • FIG. 3 is a diagram illustrating prioritization according to one embodiment of the present disclosure.
  • FIG. 3 is a diagram illustrating prioritization according to one embodiment
  • FIG. 3 is a diagram illustrating prioritization according to one embodiment of the present disclosure.
  • FIG. 3 is a diagram illustrating prioritization according to one embodiment of the present disclosure.
  • FIG. 3 is a diagram illustrating prioritization according to one embodiment of the present disclosure.
  • FIG. 3 is a diagram illustrating prioritization according to one embodiment of the present disclosure.
  • FIG. 3 is a diagram illustrating prioritization according to one embodiment of the present disclosure.
  • FIG. 2 is a block diagram showing the hardware configuration of a base station and a terminal according to an embodiment of the present disclosure.
  • FIG. 1 is a block diagram showing a 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.
  • the wireless communication system is Long Term Evolution (LTE), a 5th generation mobile communication system specified by the Third Generation Partnership Project (3GPP). Achieving communication using New Radio (5G NR), 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 (E-UTRA-NR Dual Connectivity (EN-DC)) between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR.
  • E-UTRA Radio Access Technologies
  • NE-DC dual connectivity between NR and LTE (NR-E -UTRA Dual Connectivity (NE-DC)).
  • 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 physical broadcast channel (PBCH), and a downlink control channel (physical al Downlink Control Channel (PDCCH)) etc. may be used.
  • PDSCH physical downlink shared channel
  • PBCH physical broadcast channel
  • PDCCH physical al Downlink Control Channel
  • the uplink channel shared on each device (PHYSICAL UPLINK SHARED CHANNEL (PUSCH)), and uplink control channels (PHYSICAL UPLINK CONTROL CHANNEL) (PUCCH)), Random Access Channel ( Physical Random Access Channel (PRACH) or the like may be used.
  • PSCH PHYSICAL UPLINK SHARED CHANNEL
  • PUCCH uplink control channels
  • 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), CK/NACK, etc.) and scheduling request (Scheduling Request).
  • CSI channel state information
  • delivery confirmation information for example, Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), CK/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), a channel state information reference signal (CSI-RS), and a channel state information reference signal (CSI-RS).
  • CRS cell-specific reference signal
  • CSI-RS channel state information reference signal
  • CSI-RS channel state information reference signal
  • DMRS Demodulation Reference A 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.
  • the division duplex method may be called XDD (Cross Division Duplex) or subband non-overlapping full duplex.
  • XDD or subband non-overlapping full duplex may refer to a duplexing method in which DL and UL are frequency division multiplexed (DL and UL can be used simultaneously) within one component carrier (CC) of the TDD band. .
  • 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 XDD.
  • 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 XDD 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 multiple UEs receives a DL channel/signal.
  • one UE receives the DL channel/signal
  • another UE receives the DL channel/signal.
  • the base station performs simultaneous transmission and reception of DL and UL.
  • each of the multiple UEs (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 resource on the UE TDD carrier is configured as at least one of DL, UL, and flexible (FL) in TDD configuration.
  • XDD symbols may be advertised or configured as UL (or DL) or for UL transmission (or DL reception) on some frequency resources, while being advertised or configured as DL (or UL) on other frequency resources. ), or may be a symbol notified or set for DL reception (or UL transmission).
  • the XDD 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 XDD symbol may be a symbol that is notified or set as DL (or UL) in a part of the frequency resource, or may be a symbol that is 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 XDD time unit may be an XDD symbol, a slot/subslot that includes or overlaps an XDD symbol, or a group of symbols/slots/subslots that includes or overlaps an XDD symbol.
  • a pure time unit is a non-XDD symbol (i.e., a symbol that is not an XDD symbol), a slot/subslot that does not contain or overlaps an XDD symbol, or a symbol/slot/slot that does not contain or overlap It may be a group of subslots and may be referred to as a non-XDD 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. 5A, or as a time unit consisting of only DL on a frequency resource, as shown in FIG. 5B. 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 XDD time units of frequency domain pattern #1 may have an arrangement pattern as shown in FIG. 5C.
  • the XDD time units of frequency domain pattern #2 may have an arrangement pattern as shown in FIG. 5D.
  • the XDD time units of frequency domain pattern #3 may have an arrangement pattern as shown in FIG. 5E.
  • These placement patterns are merely examples, and other placement patterns may be used.
  • the frequency domain pattern for an XDD time unit may mean a resource repetition pattern in the frequency domain for an XDD time unit.
  • BD blind decoding
  • SS search space
  • the UE monitors PDCCH candidates at PDCCH monitoring opportunities as shown in FIG. 6 in each slot to be monitored.
  • the UE receives PDCCH monitoring opportunity #0 corresponding to the “0” and “1”th symbols
  • “4” and “5” PDCCH candidates are monitored in PDCCH monitoring opportunity #1 corresponding to the ⁇ th symbol.
  • the PDCCH monitoring capability can be notified or set for each slot in Rel-15, for each span in Rel-16, and for multiple slots in Rel-17.
  • overbooking which sets the number of PDCCH candidates and/or control channel elements (CCEs) that exceeds the UE capability, is performed on the primary cell (Pcell) or primary secondary cell (PScell). permissible only in For the Rel-16 per-span PDCCH monitoring capability, overbooking is only allowed in the first span of slots on a Pcell/PScell. For Rel-17 multi-slot PDCCH monitoring capability, overbooking is only allowed on Pcell/PScell.
  • the network ensures that the number of non-overlapping CCEs and the number of PDCCH candidates in the CSS in a slot, span, or group of X slots is less than or equal to the blind decoding (BD) or control channel element (CCE) limit. .
  • BD blind decoding
  • CCE control channel element
  • USS UE-specific search space
  • SS indexes may have higher priority. That is, a USS with a larger SS index has a CSS whose number of PDCCH candidates and number of non-overlapping CCEs in a slot, span, or group of X slots is below the blind decoding (BD) or control channel element (CCE) limit.
  • BD blind decoding
  • CCE control channel element
  • the UE monitors PDCCH candidates with the same TCI state that are included in or overlap the PDCCH monitoring opportunities. Further, the TCI state is determined by the SS with the highest priority.
  • CSS has higher priority than USS
  • SS with smaller cell index has higher priority than SS with larger cell index
  • SS with smaller SS index has higher priority than SS with larger SS index. have higher priority.
  • the SS of CSS #1 of cell #1, the SS of CSS #2 of cell #2, the SS of USS #2 of cell #1, and the SS of USS #1 of cell #2 are prioritized as shown in FIG. 8, and PDCCH candidates are monitored for the SS of CSS #1 of cell #1 and the SS of USS #2 of cell #1.
  • the cells or time resources in which the XDD operation can be set are limited.
  • the UE may not assume that the Pcell/PScell is notified or configured for XDD operation. Also, the UE may not assume that any cells in the primary/secondary cell group are notified, configured or applied for XDD operation. Alternatively, the UE may not assume that any BWP or cell in which the search space (SS) set and/or CORESET configuration is configured is advertised or configured for XDD operation.
  • SS search space
  • the UE may indicate that even if XDD operation is notified or configured, any BWP or cell in which a particular type of SS set and/or a particular type of CORESET configuration is configured is (or DL) or may not be intended to be advertised or configured for UL transmission (or DL reception).
  • the UE may not assume that any BWP or cell for which PUCCH resources/transmissions are configured has XDD operations notified, configured or applied.
  • the UE may not assume that any BWP or cell in FR2-2 is advertised or configured as UL (or DL) or advertised or configured for XDD operation.
  • the UE may determine that XDD operation is notified or configured for any BWP or cell in which a Subcarrier Spacing (SCS) value greater than a specific value (e.g., an SCS value of 60, 120, 480, or 960 kHz) is configured. You may not expect that.
  • SCS Subcarrier Spacing
  • the BWP or the cell may be notified or configured to perform XDD operation.
  • the BWP may be notified or set of the XDD operation as follows.
  • a certain time unit on a BWP may be advertised or configured as UL (or DL) on some frequency resources, or advertised or configured for UL transmission (or DL reception), while other On the frequency resource, it may be notified or configured as DL (or UL), or it may be notified or configured for DL reception (or UL transmission).
  • the time unit here may be a symbol, a slot, a subslot, or a group of symbols, slots, or subslots. That is, the XDD operation may be notified or set to the BWP in frequency resource units for a certain time unit.
  • a certain time unit on the BWP may be advertised or configured as UL (or DL) or for UL transmission (or DL reception) for some UEs, while others
  • the UE may be notified or configured as DL (or UL), or may be notified or configured for DL reception (or UL transmission). That is, the XDD operation may be notified or configured to BWP on a UE basis for a certain time unit.
  • a certain time unit on the BWP is advertised or configured as UL (or DL) on some frequency resources, or advertised or configured for UL transmission (or DL reception) and the Some frequency resources may be notified or configured as unavailable for the UL (or DL) by a new slot format configuration/notification or by a new rate match pattern configuration/notification. That is, XDD operation may be notified or configured in the BWP for a certain time unit using a new slot format configuration/notification or a new rate match pattern configuration/notification.
  • XDD operation may be notified or set to the cell as follows.
  • any of the cells or active BWPs may be notified or configured for XDD operation.
  • multiple BWPs for XDD operation may be notified or configured for the cell.
  • the UE receives notifications or configurations regarding XDD operations on radio resources, and controls uplink transmission or downlink reception on the radio resources according to the notifications or configurations regarding the XDD operations.
  • the base station may transmit notifications or settings regarding XDD operations for the radio resources, and control uplink transmission or downlink reception on the radio resources according to the notifications or settings regarding the XDD operations.
  • the UE may receive notifications or settings regarding XDD operation in frequency resource units for time units on BWP.
  • the base station may transmit a notification or configuration regarding XDD operation in frequency resource units with respect to time units on BWP.
  • the notification or setting regarding the XDD operation in units of frequency resources is to notify or set some frequency resources of the BWP for uplink transmission or downlink reception, and to notify or set other frequency resources of the BWP for downlink reception or uplink reception. It may be notified or set for link transmission.
  • the part of frequency resources may be notified or configured as available or unusable for uplink transmission or downlink reception by slot format setting or notification, or by rate match pattern setting or notification.
  • the UE may receive notifications or settings regarding XDD operations on a terminal-by-terminal basis for time units on BWP.
  • the base station may send notifications or configurations regarding XDD operations on a per-terminal basis for time units on the BWP.
  • the notification or setting regarding the XDD operation for each terminal is to notify or set a time unit for uplink transmission or downlink reception to a certain terminal, and set the time unit for downlink reception or uplink transmission to another terminal. may be notified or set.
  • the UE may also receive a notification or configuration indicating the BWP of the cell where XDD operation is configured or the BWP for XDD operation of the cell.
  • the base station may send a notification or configuration indicating the BWP of the cell for which XDD operation is configured or the BWP for XDD operation of the cell.
  • the above settings or notifications include, for example, RRC (Radio Resource Control) information elements, DCI (Downlink Control Information), and MAC CE (Medium Access Control). Control Element).
  • RRC Radio Resource Control
  • DCI Downlink Control Information
  • MAC CE Medium Access Control
  • the UE transmits UE capability information regarding the XDD operation to the base station, and the base station notifies or configures the XDD operation to the UE based on the received UE capability information.
  • UE capability information regarding whether XDD operation applied to Pcell/PScell is supported is defined, and the UE transmits UE capability information regarding whether XDD operation applied to Pcell/PScell is supported to the base. It may also be sent to the station.
  • UE capability information regarding whether the UE supports the XDD operation applied to the cells in the primary/secondary cell group is defined, and the UE determines whether the UE supports the XDD operation applied to the cells in the primary/secondary cell group.
  • UE capability information may be sent to the base station.
  • UE capability information regarding whether the SS set (of a particular SS set type) supports XDD operations applicable to the cell/BWP in which it is configured is defined, and the UE UE capability information regarding whether the set supports XDD operations applicable to the cell/BWP in which it is configured may be sent to the base station.
  • UE capability information regarding whether it supports XDD operation applied to the cell/BWP in which PUCCH resources/transmissions are configured is specified, and the UE UE capability information regarding whether it supports XDD operation may be sent to the base station.
  • UE capability information regarding whether the UE supports the XDD operation applied to the cell/BWP in FR2-2 is specified, and the UE determines whether the UE supports the XDD operation applied to the cell/BWP in the FR2-2.
  • UE capability information may be sent to the base station.
  • UE capability information regarding whether it supports XDD operation applied to a cell/BWP in which an SCS larger than a specific value is configured is defined, and the UE UE capability information regarding whether it supports XDD operations applicable to the base station may be sent to the base station.
  • the first embodiment it is possible to limit the cells or time resources in which the XDD operation can be set.
  • the existing configuration may be used. In other words, even if XDD operation is allowed to be notified, configured, or applied to a BWP or cell where PDCCH monitoring is configured, no enhancement is made to the SS set configuration or CORESET configuration. It's okay.
  • separate SS set configurations may be configured for pure time units and XDD time units. That is, search space sets may be set for each of normal TDD operation and XDD operation.
  • the time unit may be a symbol level, a slot/subslot level, or a group of symbols/slots/subslots.
  • An XDD time unit may also be an XDD symbol, a slot/subslot that includes or overlaps an XDD symbol, or a group of symbols/slots/subslots that includes or overlaps an XDD symbol.
  • a pure time unit may be a non-XDD symbol, ie a symbol that is not an XDD symbol, or a slot/subslot or a group of symbols/slots/subslots that do not contain or overlap an XDD symbol.
  • searchSpacesToAddModList is used for a pure time-based SS set configuration (which may also be referred to as a non-XDD SS set), and a new information element (IE) such as searchSpacesToAddModListForXDD is used to configure an XDD time-based SS set configuration.
  • IE new information element
  • searchSpacesToAddModListForXDD is used to configure an XDD time-based SS set configuration.
  • regulation may also be referred to as XDD SS set).
  • two IEs, searchSpacesToAddModList and searchSpacesToAddModListForXDD may be set in PDCCH-Config.
  • the two IEs searchSpacesToReleaseList and searchSpacesToReleaseListForXDD may also be configured.
  • the UE may determine PDCCH monitoring opportunities similarly to Rel-15/16.
  • the UE does not need to assume that any PDCCH monitoring opportunities of non-XDD SS sets are included in or overlap with the XDD time unit or XDD symbol. good.
  • the UE may PDCCH candidates may not be monitored.
  • the PDCCH monitoring opportunities of the Good too.
  • the UE does not have to assume that any PDCCH monitoring opportunities of the XDD SS set are included in a pure time unit or overlap.
  • the UE determines whether the PDCCH monitoring opportunities included or overlap in pure time units or non-XDD symbols are PDCCH candidates. You may choose not to monitor.
  • the UE may monitor the PDCCH candidates in the PDCCH monitoring opportunities.
  • PDCCH candidates are monitored according to XDD SS set #1. Specifically, the UE monitors PDCCH candidates in the 0th, 2nd, 4th, 6th, 8th, 10th, 12th, 17th, and 18th slots.
  • the XDD SS set may be set only for a specific SS type.
  • the specific SS types are Type0-PDCCH CSS set, Type0A-PDCCH CSS set, Type1-PDCCH CSS set, Type2-PDCCH CSS set, Type3-PDCCH It may be a CSS set and/or a USS set.
  • the XDD SS set may be set only for a specific DCI (Downlink Control Information) format.
  • the particular DCI format may be DCI 0_0/1_0, DCI 2_0, DCI 2_1, DCI 2_2, DCI 2_3, DCI 0_1/1_1, DCI 2_5, DCI 3_0, DCI 3_1 and/or DCI 0_2/1. Even if it is _2 good.
  • the UE may apply the same SS set configuration for any XDD time unit regardless of the frequency domain pattern. good.
  • the UE may apply different SS set configurations for the XDD time units with different frequency domain patterns.
  • SS set configurations for the XDD time units with different frequency domain patterns.
  • up to X additional SS set configurations may be configured in the PDCCH-Config.
  • the value of X may be set to be less than or equal to the number of frequency domain patterns in the set XDD time unit.
  • the value of X may be defined by the specifications or may be set in the RRC configuration.
  • the UE determines whether any of the PDCCH monitoring opportunities in the SS set in which the frequency domain pattern type #i is set in the XDD time unit may not be assumed to be included or overlap with pure time units or XDD time units with other frequency domain pattern types. Additionally, if the PDCCH monitoring opportunity of the SS set with frequency domain pattern type #i set to the XDD time unit is included in or overlaps with the pure time unit or the XDD time unit with other frequency domain pattern types, the UE , pure time units or XDD time units with other frequency domain pattern types or in overlapping PDCCH monitoring opportunities may not be monitored.
  • searchSpacesToAddModListForXdd1 searchSpacesToReleaseListForXdd1
  • searchSpacesToAddModListF searchSpacesToAddModListF
  • PDCCH candidates are monitored according to #0, and in XDD time units of frequency domain pattern type 1, PDCCH candidates are monitored according to XDD SS set #1 of frequency domain pattern type 1, and in XDD time units of frequency domain pattern type 2, PDCCH candidates are monitored according to XDD time units of frequency domain pattern type 2.
  • controlResourceSetId may be set for the SS set configuration. That is, it is possible to set multiple CORESETs.
  • controlResourceSetId is an IE for identifying CORESET.
  • CORESET associations may be applied for pure time units and XDD time units. That is, CORESET may be set for each of normal TDD operation and XDD operation. Specifically, an existing controlResourceSetId may be set for the pure time unit, and a new controlResourceSetIdForXdd may be set for the XDD time unit.
  • the existing controlResourceSetId may be used to determine the corresponding PDCCH monitoring opportunity and PDCCH candidate.
  • a new controlResourceSetIdForXdd may be used to determine the corresponding PDCCH monitoring opportunity and PDCCH candidate.
  • controlResourceSetId for pure time units and controlResourceSetIdForXdd for XDD time units may be configured in the SearchSpace configuration, as shown in FIG. 13A.
  • the UE may determine PDCCH monitoring opportunities and PDCCH candidates according to controlResourceSetId in pure time units, and determine PDCCH monitoring opportunities and PDCCH candidates according to controlResourceSetIdForXdd in XDD time units.
  • option 3-1 there may be multiple frequency domain patterns for the XDD time unit.
  • a single controlResourceSetIdForXdd may be utilized for any XDD time unit regardless of the frequency domain pattern.
  • different CORESET associations may be applied for different XDD time units with different frequency domain patterns.
  • up to X additional CORESET associations may be configured.
  • the value of X may be set to be less than or equal to the number of frequency domain patterns in the set XDD time unit.
  • the value of X may be defined by the specifications or may be set in the RRC configuration.
  • controlResourceSetIdForXdd-1, controlResourceSetIdForXdd-2, and controlResourceSetIdForXdd-3 for three additional frequency domain patterns are searchS as shown in FIG. 14A. It may be set in the pace configuration.
  • the UE determines PDCCH monitoring opportunities and PDCCH candidates according to controlResourceSetId in pure time units, and determines PDCCH monitoring opportunities and PDCCH candidates according to controlResourceSetIdForXdd-1 in XDD time units according to frequency domain pattern type 1.
  • a PDCCH monitoring opportunity and a PDCCH candidate may be determined according to controlResourceSetIdForXdd-2.
  • the UE determines the PDCCH monitoring opportunity by trying the list of controlResourceSetIds until an appropriate controlResourceSetId is selected or until all controlResourceSetIds are tried. and PDCCH candidates may be determined. That is, the UE selects a suitable one from a plurality of CORESETs according to the SS configuration.
  • the UE may first determine the PDCCH monitoring opportunities and PDCCH candidates of the SS set by using the first CORESET ID. If none of the determined PDCCH candidates overlaps with the time and frequency domain resources notified or configured as UL or notified or configured for UL transmission, the UE determines to use the CORESET and selects the determined PDCCH. Candidates may be monitored.
  • the UE Determine PDCCH monitoring opportunities and PDCCH candidates by utilizing the next configured CORESET ID until a CORESET ID is obtained in which a PDCCH candidate that does not overlap with the time and frequency domain resources notified or configured in the trust is detected. You may.
  • controlResourceSetAddForXdd IE for specifying the trial order of multiple controlResourceSetIds may be set in the SearchSpace configuration, as shown in FIG. 15.
  • the UE sets each CORESET ID to the UL in the order of controlResourceSetId, controlResourceSetId-2, controlResourceSetId-3, and controlResourceSetId-4. or the time to be notified or set for UL transmission. and each CORESET ID to determine whether it contains PDCCH candidates that do not overlap with the frequency domain resources.
  • controlResourceSetId-3 is a CORESET containing PDCCH candidates that do not overlap with time and frequency domain resources that are notified or configured as UL or notified or configured for UL transmission.
  • the UE may determine PDCCH monitoring opportunities and PDCCH candidates using controlResourceSetId-3.
  • controlResourceSetId is determined to be a CORESET that includes PDCCH candidates that do not overlap with time and frequency domain resources that are notified or configured as UL or notified or configured for UL transmission.
  • the UE may use controlResourceSetId to determine PDCCH monitoring opportunities and PDCCH candidates.
  • multiple frequencyDomainResources may be configured for the CORESET configuration.
  • a plurality of frequency domain patterns are set for CORESET.
  • frequencyDomainResources is an IE that specifies frequency domain resources for CORESET.
  • separate frequencyDomainResources configurations may be applied for pure time units and XDD time units. That is, frequency domain patterns are set according to normal TDD operation and XDD operation. For example, a new frequencyDomainResourcesForXdd may be set for CORESET in addition to the existing frequencyDomainResources. For each PDCCH monitoring opportunity of the SS set for the CORESET, if the PDCCH monitoring opportunity is not included in or does not overlap in the XDD time unit or XDD symbol, the existing frequencyDomainResources may be utilized to determine the corresponding PDCCH candidate. . On the other hand, if the PDCCH monitoring opportunities are included or overlap in an XDD time unit or XDD symbol, a new frequencyDomainResourcesForXdd may be utilized to determine the corresponding PDCCH candidate.
  • the UE may monitor PDCCH candidates determined based on frequencyDomainResources in pure time units, and monitor PDCCH candidates determined based on frequencyDomainResourcesForXdd in XDD time units.
  • option 4-1 there may be multiple frequency domain patterns for the XDD time unit.
  • a single frequencyDomainResourcesForXdd may be utilized for any XDD time unit regardless of the frequency domain pattern.
  • different frequencyDomainResourcesForXdd configurations may be applied for different XDD time units with different frequency domain patterns.
  • up to X additional frequencyDomainResourcesForXdd configurations may be configured.
  • the value of X may be set to be less than or equal to the number of frequency domain patterns in the set XDD time unit.
  • the value of X may be defined by the specifications or may be set in the RRC configuration.
  • frequencyDomainResourcesForXdd-1, frequencyDomainResourcesForXdd-2 and frequencyDomainResourcesForXdd-3 for three additional frequency domain patterns may be set in the ControlResourceSet configuration, as shown in FIG. 18A.
  • the UE determines PDCCH candidates according to frequencyDomainResources in pure time units, determines PDCCH candidates according to frequencyDomainResourcesForXdd-1 in XDD time units according to frequency domain pattern type 1, and determines PDCCH candidates according to frequencyDomainResourcesForXdd-1 in frequency domain pattern type 2.
  • PDCCH candidates may be determined according to frequencyDomainResourcesForXdd-2.
  • the UE shall continue to PDCCH candidates by trying the list of ces You may decide. That is, the UE may select a suitable one from a plurality of CORESETs depending on the SS set.
  • the UE may first determine the PDCCH candidates by utilizing the first frequencyDomainResources. If none of the determined PDCCH candidates overlaps with the time and frequency domain resources that are notified or configured as UL or notified or configured for UL transmission, the UE determines to use the frequencyDomainResources and determines PDCCH candidates may be monitored.
  • the UE PDCCH candidates may be determined by utilizing the next configured frequencyDomainResources until a frequencyDomainResources is obtained in which a PDCCH candidate that does not overlap with the time and frequency domain resources that are notified or configured in the trust is detected.
  • Default frequencyDomainResources, first frequencyDomainResources, or last frequencyDomainResources may be used to determine PDCCH candidates.
  • the UE may not assume such a case.
  • the UE may not monitor PDCCH candidates during the PDCCH monitoring opportunity.
  • the frequencyDomainResourcesAddForXdd IE for specifying the trial order of multiple frequencyDomainResources may be set in the ControlResourceSet configuration, as shown in FIG. 19.
  • each frequencyDomainResources is tried to determine if it contains non-overlapping PDCCH candidates.
  • frequencyDomainResources-3 is a frequencyDomainResources containing PDCCH candidates that do not overlap with time and frequency domain resources that are advertised or configured as UL or advertised or configured for UL transmission. If it is determined that there is a PDCCH, the UE may determine a PDCCH candidate using frequencyDomainResources-3.
  • the frequencyDomainResources are frequencyDomainResources that include PDCCH candidates that do not overlap with time and frequency domain resources that are notified or configured as UL or notified or configured for UL transmission, and the UE may determine PDCCH candidates using frequencyDomainResources.
  • multiple bitmaps of freqMonitorLocations may be configured for the SS set configuration. That is, a plurality of freqMonitorLocations bitmaps are set for the SS set.
  • freqMonitorLocations is an IE that indicates frequency monitoring locations.
  • separate freqMonitorLocations bitmaps may be set for pure time units and XDD time units. That is, frequency domain patterns are selected depending on normal TDD operation and XDD operation.
  • a new freqMonitorLocationsForXdd may be set for the SS set configuration. For each PDCCH monitoring opportunity of the SS set, if the PDCCH monitoring opportunity is not included or does not overlap in the XDD time unit or XDD symbol, the existing freqMonitorLocations may be utilized to determine the corresponding PDCCH candidate. On the other hand, if the PDCCH monitoring opportunities are included or overlap in an XDD time unit or XDD symbol, a new freqMonitorLocationsForXdd may be utilized to determine the corresponding PDCCH candidates.
  • two IEs freqMonitorLocations for pure time units and freqMonitorLocationsForXdd for XDD time units, may be configured in the SearchSpaceExt configuration, as shown in FIG. 21A.
  • the UE may monitor PDCCH candidates determined based on freqMonitorLocations in pure time units, and monitor PDCCH candidates determined based on freqMonitorLocationsForXdd in XDD time units.
  • a single freqMonitorLocationsForXdd bitmap may be utilized for any XDD time unit regardless of the frequency domain pattern.
  • freqMonitorLocationsForXdd bitmaps may be applied for different XDD time units with different frequency domain patterns.
  • up to X additional freqMonitorLocationsForXdd bitmaps may be configured.
  • the value of X may be set to be less than or equal to the number of frequency domain patterns in the set XDD time unit.
  • the value of X may be defined by the specifications or may be set in the RRC configuration.
  • freqMonitorLocationsForXdd-1, freqMonitorLocationsForXdd-2, and freqMonitorLocationsForXdd-3 IEs for three additional frequency domain patterns are May be set in the searchSpaceExt configuration.
  • the UE monitors PDCCH candidates determined based on freqMonitorLocations in pure time units, and monitors PDCCH candidates determined based on freqMonitorLocationsForXdd-1 in XDD time units according to frequency domain pattern type 1.
  • the PDCCH candidates determined based on freqMonitorLocationsForXdd-2 may be monitored in XDD time units according to frequency domain pattern type 2.
  • the UE may perform a PDCCH candidates may be determined. That is, the UE selects a suitable one from a plurality of bitmaps according to the SS set.
  • the UE may first determine the PDCCH candidates of the SS set by utilizing the first freqMonitorLocations bitmap. If none of the determined PDCCH candidates overlaps with the time and frequency domain resources that are notified or configured as UL or notified or configured for UL transmission, the UE determines to use the freqMonitorLocations and PDCCH candidates may be monitored.
  • the UE PDCCH candidates may be determined by using the next configured freqMonitorLocations until freqMonitorLocations are obtained in which PDCCH candidates that do not overlap with the time and frequency domain resources that are notified or configured for trust are obtained.
  • the UE has tried all the freqMonitorLocations bitmaps configured for the SS set, but there are no PDCCH candidates that do not overlap with the time and frequency domain resources that are advertised or configured as UL or advertised or configured for UL transmission. If the acquired freqMonitorLocations bitmap cannot be detected, the default freqMonitorLocations, the first freqMonitorLocations, or the last freqMonitorLocations are used to determine the PDCCH candidate. May be used. Alternatively, the UE may not assume such a case. Alternatively, the UE may not monitor PDCCH candidates during the PDCCH monitoring opportunity.
  • freqMonitorLocationsAddForXdd IE for specifying the trial order of multiple freqMonitorLocations may be set in the SearchSpaceExt configuration, as shown in FIG. 23.
  • the UE determines whether each freqMonitorLocation is notified or configured as a UL or U in the order of freqMonitorLocations, freqMonitorLocations-2, and freqMonitorLocations-3. time and frequency domain resources notified or configured for L transmission; Each freqMonitorLocations is tried to determine if it contains non-overlapping PDCCH candidates.
  • freqMonitorLocations-3 is a freqMonitorLocation that includes PDCCH candidates that do not overlap with time and frequency domain resources that are advertised or configured as UL or advertised or configured for UL transmission. If it is determined that there is a PDCCH, the UE may determine a PDCCH candidate using freqMonitorLocations-3.
  • freqMonitorLocations is freqMonitorLocations that include PDCCH candidates that do not overlap with time and frequency domain resources that are notified or configured as UL or notified or configured for UL transmission, and the UE may determine PDCCH candidates using freqMonitorLocations.
  • the freqMonitorLocations of the SS set configuration and/or the frequencyDomainResources of the CORESET configuration are specified in the overlapping XDD time units or XDD symbol frequency May be interpreted based on area resources.
  • the freqMonitorLocations of the SS set configuration and/or the frequencyDomainResources of the CORESET configuration are rLocationsForXdd and/or frequencyDomainResourcesAddForXdd in the CORESET configuration It may also be read as
  • the SS set type may be a Type0-PDCCH CSS set, a Type0A-PDCCH CSS set, a Type1-PDCCH CSS set, a Type2-PDCCH CSS set, a Type3-PDCCH CSS set, and/or a USS set.
  • the UE receives a first PDCCH monitoring configuration for a non-XDD time unit (e.g., a pure time unit) and a second PDCCH monitoring configuration for an XDD time unit; PDCCH monitoring may be controlled according to a first PDCCH monitoring configuration and a second PDCCH monitoring configuration.
  • the base station configures a first PDCCH monitoring configuration for the non-XDD time unit and a second PDCCH monitoring configuration for the XDD time unit, and configures the first PDCCH monitoring configuration and the second PDCCH monitoring configuration.
  • the settings may also be sent to the terminal.
  • the first PDCCH monitoring configuration is a search space set configuration for non-XDD time units (e.g., searchSpaceToAddModList)
  • the second PDCCH monitoring configuration is a search space set configuration for one or more XDD time units. settings (for example, searchSpaceToAddModListForXDD, searchSpaceToAddModListForXDD1, searchSpaceToAddModListForXDD2, etc.).
  • the first PDCCH monitoring configuration is a CORESET (e.g., controlResourceSetId) configuration for the non-XDD time unit
  • the second PDCCH monitoring configuration is one or more CORESET settings (e.g., controlResourceSetIdForXdd, controlResourceSetId) for the XDD time unit. sourceSetIdForXdd- 1, controlResourceSetIdForXdd-2, etc.).
  • the first PDCCH monitoring configuration is a frequency domain resource configuration (e.g., frequencyDomainResources) for the non-XDD time unit
  • the second PDCCH monitoring configuration is one or more frequency domain resource configurations (e.g., frequencyDomainResources) for the XDD time unit. frequencyDomainResourcesForXdd, frequencyDomainResourcesForXdd-1, frequencyDomainResourcesForXdd-2, etc.).
  • the first PDCCH monitoring settings are frequency monitoring location settings (e.g., freqMonitorLocations) for non-XDD time units
  • the second PDCCH monitoring settings are frequency monitoring location settings for the XDD time units (e.g., freqMonitorLocationsForXdd, freqMonitorLocationsForXdd-1, freqMonitorLocationsForXdd-2, etc.).
  • the second PDCCH monitoring configuration described above may indicate prioritization corresponding to multiple frequency domain patterns.
  • the second PDCCH monitoring configuration may be interpreted from the first PDCCH monitoring configuration.
  • the above settings or notifications include, for example, RRC (Radio Resource Control) information elements, DCI (Downlink Control Information), and MAC CE (Medium Access Control). Control Element). Also, the present disclosure is not limited to monitoring PDCCH, but may be applied to other types of control signals sent from a base station to a UE or other base station (eg, IAB node, etc.).
  • RRC Radio Resource Control
  • DCI Downlink Control Information
  • MAC CE Medium Access Control
  • Control Element Medium Access Control
  • the present disclosure is not limited to monitoring PDCCH, but may be applied to other types of control signals sent from a base station to a UE or other base station (eg, IAB node, etc.).
  • the UE transmits UE capability information regarding the XDD operation to the base station, and the base station notifies or configures the XDD operation to the UE based on the received UE capability information.
  • UE capability information regarding whether the UE supports separate SS set configurations for XDD time units and pure time units may be defined.
  • the UE may send UE capability information to the base station regarding whether it supports separate SS set configurations for XDD time units and pure time units.
  • UE capability information regarding whether the UE supports multiple controlResourceSetId configured for the SS set configuration may be defined.
  • the UE may transmit UE capability information to the base station regarding whether it supports multiple controlResourceSetId configured for the SS set configuration.
  • UE capability information regarding whether the UE supports multiple frequencyDomainResources configured for the CORESET configuration may be defined.
  • the UE may send UE capability information to the base station regarding whether it supports multiple frequencyDomainResources configured for the CORESET configuration.
  • UE capability information regarding whether the UE supports multiple freqMonitorLocations bitmaps configured for the SS set configuration may be defined.
  • the UE may send UE capability information to the base station regarding whether it supports bitmaps of multiple freqMonitorLocations configured for the SS set configuration.
  • UE operation regarding SS set and/or CORESET configuration can be defined.
  • the third embodiment is independent from the second embodiment. That is, any option of the third embodiment may be applied together with any option of the second embodiment.
  • the UE may assume that the PDCCH monitoring opportunities of the PDCCH SS set do not overlap with the XDD symbols. That is, the UE may assume that PDCCH monitoring does not overlap with XDD symbols.
  • the first PDCCH monitoring opportunity (symbols #0, #1) in the slot overlaps with the XDD symbol, resulting in an error case.
  • the UE may assume that the PDCCH monitoring opportunities of the PDCCH SS set are included in the XDD time unit or do not overlap. That is, the UE may assume that PDCCH monitoring does not overlap with the XDD time units.
  • the time unit is a slot, and the PDCCH monitoring opportunity is included in the XDD slot, resulting in an error case.
  • a case is considered in which the PDCCH monitoring opportunities of the PDCCH SS set are included in the XDD time unit or overlap. That is, if PDCCH monitoring overlaps with XDD resources, the UE may perform the following operations.
  • the UE shall , PDCCH candidates may not be monitored during PDCCH monitoring opportunities. That is, the UE avoids PDCCH monitoring.
  • slot A is an XDD slot
  • the UE may not monitor PDCCH candidates in slot A.
  • slot B is a pure DL slot
  • the UE may monitor PDCCH candidates in slot B.
  • the UE may determine whether the PDCCH monitoring opportunities overlap with the XDD symbols or not. , determines whether to monitor the PDCCH candidate in the PDCCH monitoring opportunity. That is, the UE may determine whether monitoring can be performed depending on whether or not XDD resources can overlap. PDCCH If the PDCCH monitoring opportunities of the SS set overlap with the XDD symbols, the UE may not monitor PDCCH candidates in the PDCCH monitoring opportunities. On the other hand, if the PDCCH monitoring opportunities of the PDCCH SS set do not overlap with the XDD symbols, the UE may monitor the PDCCH candidates in the PDCCH monitoring opportunities.
  • the PDCCH monitoring opportunities in slot A do not overlap with the #0, #1, #4, #5)
  • PDCCH candidates may be monitored.
  • the first PDCCH monitoring opportunity (symbols #0, #1) in slot B overlaps with the XDD symbol
  • the UE monitors the PDCCH in the first PDCCH monitoring opportunity (symbols #0, #1) in slot B Candidates may not be monitored.
  • the UE Since the second PDCCH monitoring opportunity (symbols #4, #5) in slot B does not overlap with the XDD symbol, the UE detects PDCCH candidates in the second PDCCH monitoring opportunity (symbols #4, #5) in slot B. May be monitored.
  • the UE shall notify or configure the PDCCH candidate as UL or notify for UL transmission.
  • it may be determined whether to monitor a PDCCH candidate in a PDCCH monitoring opportunity that overlaps with an XDD symbol, based on whether or not the PDCCH candidate overlaps with the configured time and frequency domain resources. That is, the UE may make the determination depending on whether UL is configured for the XDD resource.
  • the UE determines which PDCCH candidates in the PDCCH monitoring opportunities for the PDCCH SS set. It may also be assumed that the time and frequency domain resources that are advertised or configured as UL or advertised or configured for UL transmission do not overlap. That is, the UE may monitor PDCCH candidates at PDCCH monitoring opportunities, similar to Rel-15/16.
  • the first PDCCH monitoring opportunity (symbols #0, #1) overlaps with the time and frequency domain resources configured as UL, resulting in an error case.
  • the PDCCH candidates in the PDCCH monitoring opportunities for the PDCCH SS set are notified as UL or The UE may monitor PDCCH candidates if they do not overlap with the time and frequency domain resources that are configured or advertised or configured for UL transmission. On the other hand, if the PDCCH candidate overlaps with time and frequency domain resources that are advertised or configured as UL or advertised or configured for UL transmission, the UE may not monitor the PDCCH candidate.
  • the UE since the first PDCCH monitoring opportunity (symbols #0, #1) overlaps with the time and frequency domain resources configured as UL, PDCCH candidates may not be monitored during monitoring opportunities.
  • the second PDCCH monitoring opportunity (symbols #4, #5) does not overlap with the time and frequency domain resources configured as UL, the UE does not monitor PDCCH candidates in the second PDCCH monitoring opportunity. You can.
  • the PDCCH SS set may be limited to a specific SS type.
  • option 1/2 may be applied to the Type0-PDCCH CSS set
  • option 3 may be applied to the USS set.
  • the PDCCH SS set may be limited to an SS set in which a specific DCI format is configured.
  • dci-Formats-MT-r16 formats2-5
  • dci-FormatsExt-r16 formats0 -0-And-1-0
  • dci-FormatsExt-r16 formats0-2- It may be a USS set in which And-1-2, formats 0-1-And-1-1, or formats 0-2-And-1-2 are set.
  • the UE may receive the PDCCH search space configuration and control PDCCH monitoring based on the PDCCH search space configuration in XDD operation.
  • the base station may configure the PDCCH search space configuration in XDD operation and transmit the PDCCH search space configuration.
  • the UE may assume that the PDCCH monitoring opportunities indicated by the PDCCH search space configuration do not overlap with XDD time units (e.g., XDD symbols, XDD slots, etc.).
  • XDD time units e.g., XDD symbols, XDD slots, etc.
  • the UE may avoid PDCCH monitoring in the PDCCH monitoring opportunity.
  • the PDCCH monitoring opportunity indicated by the PDCCH search space configuration overlaps with an XDD time unit (e.g., an ,
  • the UE determines whether the PDCCH candidate overlaps with the radio resources (i.e., time and frequency resources) for uplink transmission.
  • PDCCH monitoring at the PDCCH monitoring occasion may be controlled based on whether the PDCCH monitoring opportunity is available or not.
  • the above settings or notifications include, for example, RRC (Radio Resource Control) information elements, DCI (Downlink Control Information), and MAC CE (Medium Access Control). Control Element). Also, the present disclosure is not limited to monitoring PDCCH, but may be applied to other types of control signals sent from a base station to a UE or other base station (eg, IAB node, etc.).
  • RRC Radio Resource Control
  • DCI Downlink Control Information
  • MAC CE Medium Access Control
  • Control Element Medium Access Control
  • the present disclosure is not limited to monitoring PDCCH, but may be applied to other types of control signals sent from a base station to a UE or other base station (eg, IAB node, etc.).
  • the UE transmits UE capability information regarding the XDD operation to the base station, and the base station notifies or configures the XDD operation to the UE based on the received UE capability information.
  • UE capability information regarding whether the UE supports the case where PDCCH monitoring opportunities overlap with XDD time units or XDD symbols may be defined.
  • the UE may send UE capability information to the base station regarding whether it supports the case where PDCCH monitoring opportunities overlap with XDD time units or XDD symbols.
  • UE capability information regarding whether the UE supports monitoring PDCCH candidates in XDD time units or XDD symbols or in overlapping PDCCH monitoring opportunities may be defined.
  • the UE may send UE capability information to the base station regarding whether it supports monitoring PDCCH candidates in XDD time units or XDD symbols or in overlapping PDCCH monitoring opportunities.
  • UE operation regarding PDCCH monitoring can be defined.
  • the PDCCH monitoring capability of the XDD SS set or the XDD PDCCH monitoring opportunity may be the same as or different from the existing PDCCH monitoring instruction or configuration. That is, the PDCCH monitoring capability may be set by any of the following methods.
  • the capability notification, settings, or regulations for PDCCH monitoring on the BWP or cell may be unified. That is, a PDCCH monitoring capability common to normal TDD operation and XDD operation may be set. Capability notification, configuration or regulation for PDCCH monitoring on BWP or cell may be based on configuration by monitoringCapabilityConfig-r16 or monitoringCapabilityConfig-r17.
  • the PDCCH-Config of the BWP or cell has per-slot PDCCH monitoring capability for Rel-15, span for Rel-16. It may be assumed that the unit PDCCH monitoring capability and/or the Rel-17 multi-slot PDCCH monitoring capability is not notified or configured.
  • the XDD SS set means the SS set set for the XDD time unit.
  • a non-XDD SS set means an SS set set for a pure time unit.
  • an XDD PDCCH monitoring opportunity refers to a PDCCH opportunity that includes or overlaps an XDD time unit or an XDD symbol.
  • non-XDD PDCCH monitoring opportunities refer to PDCCH monitoring opportunities that do not include or overlap XDD time units or XDD symbols.
  • notification, configuration or provision of separate PDCCH monitoring capabilities for monitoring XDD SS set and non-XDD SS set on BWP or cell, or XDD PDCCH on BWP or cell Separate PDCCH monitoring capability notification, configuration or provision for monitoring opportunities and non-XDD PDCCH monitoring opportunities may be utilized. That is, PDCCH monitoring capability may be set for each of normal TDD operation and XDD operation.
  • monitoringCapabilityConfig-r16 or monitoringCapabilityConfig-r17 is reused to notify or configure Rel-15/16/17 PDCCH monitoring capabilities for non-XDD SS sets or non-XDD PDCCH monitoring opportunities. You can.
  • the new RRC parameter monitoringCapabilityConfigForXdd may be reused to notify or configure the PDCCH monitoring capability of Rel-15/16/17 for monitoring the XDD SS set or the XDD PDCCH monitoring opportunity.
  • monitoringCapabilityConfigForXdd may have the following values.
  • the UE may take the following actions.
  • the UE sets monitoringCapabilityConfig for monitoring XDD SS set or XDD PDCCH monitoring opportunity.
  • the same PDCCH monitoring capability as notified or configured by monitoringCapabilityConfig-r16 or monitoringCapabilityConfig-r17 may be followed.
  • the UE defaults to monitoring XDD SS set or XDD PDCCH monitoring opportunity.
  • PDCCH monitoring capabilities may also be applied.
  • the default PDCCH monitoring capability may be applied as a Rel-15 slot-based PDCCH monitoring capability, a Rel-16 span-based PDCCH monitoring capability, or a Rel-17 multi-slot PDCCH monitoring capability.
  • the default PDCCH monitoring capability for monitoring the XDD SS set or XDD PDCCH monitoring opportunity is: Always Rel-15 may be a per-slot PDCCH monitoring capability of Rel-16, a per-span PDCCH monitoring capability of Rel-16, or a multi-slot PDCCH monitoring capability of Rel-17. Otherwise, the UE may follow the same PDCCH monitoring capabilities as notified or configured by monitoringCapabilityConfig-r16 or monitoringCapabilityConfig-r17 for monitoring of XDD SS set or XDD PDCCH monitoring opportunity.
  • a specific PDCCH monitoring capability (e.g., Rel-15/16/17 monitoring capability) for a non-XDD SS set or a non-XDD PDCCH monitoring opportunity can be configured using monitoringCapabilityConfig- r16 or monitoringCapabilityConfig-r17 and that specific PDCCH monitoring capabilities (e.g., Rel-15/16/17 monitoring capabilities) for non-XDD SS sets or non-XDD PDCCH monitoring opportunities are configured or defined at the same time. The UE does not expect that.
  • BD blind decoding
  • CCE control channel element
  • PDCCH candidates or non-overlapping CCEs for monitored XDD PDCCH monitoring opportunities and monitored non-XDD PDCCH monitoring opportunities may be counted separately or together. That is, the upper limit of BD/CCE may be counted by any of the following methods.
  • the intent of "monitored” here is that PDCCH candidates that are determined not to be monitored (e.g., according to Example 3 and/or Rel-15/16 rules) are counted against the BD or CCE constraints. This is to include the possibility that it may be counted or may not be counted.
  • the UE determines the number of PDCCH candidates or non-overlapping CCEs for the monitored XDD SS set and the monitored non-XDD SS set, or the monitored XDD PDCCH monitoring for the maximum number of BDs or CCEs.
  • the number of PDCCH candidates or non-overlapping CCEs for opportunities and monitored non-XDD PDCCH monitoring opportunities may be counted separately. That is, the number of PDCCH candidates or non-overlapping CCEs may be counted separately for each of normal TDD operation and XDD operation.
  • the number of PDCCH candidates or non-overlapping CCEs for a monitored non-XDD SS set or a monitored non-XDD PDCCH monitoring opportunity is determined per slot, per span, or in X slots. may be counted for each group.
  • each slot, each span, or each group of X slots may be based on the settings by monitoringCapabilityConfig-r16 or monitoringCapabilityConfig-r17.
  • the maximum number of BD or CCE limits per slot, per span, or per group of (X, Y), ⁇ , C1 PDCCH max, (X, Y), ⁇ ⁇ or ⁇ M1 PDCCH max, Xsslot, ⁇ , C1 PDCCH max, Xsslot, ⁇ ⁇ , and these values are Rel - It may be the same as the value specified in 15/16/17, or it may be more or less.
  • the number of PDCCH candidates or non-overlapping CCEs for monitored non-XDD SS sets or monitored non-XDD PDCCH monitoring opportunities is counted per slot, and the maximum number of BD or CCE limits is ⁇ M1 PDCCH max, slot, ⁇ , C1 PDCCH max, slot, ⁇ ⁇ .
  • the number of PDCCH candidates or non-overlapping CCEs for the monitored XDD SS set or the monitored XDD PDCCH monitoring opportunity is determined per slot, per span, or per group of X slots. May be counted.
  • each slot, each span, or each group of X slots may be based on Example 4-1.
  • the maximum number of BD or CCE limits per slot, per span or per group of X slots is, for example, ⁇ M2 PDCCH max, slot, ⁇ , C2 PDCCH max, slot, ⁇ ⁇ , ⁇ M2 PDCCH max, (X, Y), ⁇ , C2 PDCCH max, (X, Y), ⁇ ⁇ or ⁇ M2 PDCCH max, Xsslot, ⁇ , C2 PDCCH max, Xsslot, ⁇ ⁇ , and these values are Rel - It may be the same as the value specified in 15/16/17, or it may be more or less.
  • the PDCCH candidate or non-overlapping PDCCH for the monitored XDD SS set or the monitored XDD PDCCH monitoring opportunity is The number of CCEs may be counted per span, and the maximum number of BD or CCE limits is ⁇ M2 PDCCH max, (X, Y), ⁇ , C2 PDCCH max, (X, Y), ⁇ ⁇ . It's okay.
  • (M1 PDCCH max, slot, ⁇ + M2 PDCCH max, slot, ⁇ ) is the same as M PDCCH max, slot, ⁇ specified in Rel-15, or is larger or smaller. There may be.
  • (C1 PDCCH max, slot, ⁇ + C2 PDCCH max, slot, ⁇ ) is the same as M PDCCH max, slot, ⁇ specified in Rel-15, or even if it is larger or smaller. good.
  • (M1 PDCCH max, (X, Y), ⁇ + M2 PDCCH max, (X, Y), ⁇ ) is M PDCCH max, (X, Y), ⁇ defined in Rel-16. It may be the same as, or may be more or less than. Also, (C1 PDCCH max, (X, Y), ⁇ + C2 PDCCH max, (X, Y), ⁇ ) is the same as M PDCCH max, (X, Y), ⁇ specified in Rel-16. or may be more or less.
  • (M1 PDCCH max, Xsslot, ⁇ + M2 PDCCH max, Xsslot, ⁇ ) is the same as M PDCCH max , It may be.
  • (C1 PDCCH max, Xsslot, ⁇ + C2 PDCCH max, Xsslot, ⁇ ) is the same as M PDCCH max , good.
  • XDD USS#1 and XDD USS#3 are XDD PDCCH monitoring opportunities to be monitored, and the maximum number of BD or CCE limits is ⁇ M2 PDCCH max, slot, ⁇ , C2 PDCCH max, slot, ⁇ ⁇ .
  • non-XDD USS #2 and non-XDD CSS #1 are non-XDD PDCCH monitoring opportunities to be monitored, and the maximum number of BD or CCE limits is ⁇ M1 PDCCH max, slot, ⁇ , C1 PDCCH max, slot, ⁇ ⁇ .
  • the example shown in FIG. 31B also relates to Rel-15 per-slot PDCCH monitoring capabilities.
  • USS #1 and USS #3 are non-XDD PDCCH monitoring opportunities to be monitored, and the maximum number of BD or CCE limits is ⁇ M2 PDCCH max, slot, ⁇ , C2 PDCCH max, slot, ⁇ ⁇ .
  • USS #2 and CSS #1 are non-XDD PDCCH monitoring opportunities to be monitored, and the maximum number of BD or CCE limits is ⁇ M1 PDCCH max, slot, ⁇ , C1 PDCCH max, slot, ⁇ ⁇ .
  • the UE determines, for the maximum number of BDs or CCEs, PDCCH candidates or non-overlapping CCEs for the monitored XDD SS set and the monitored non-XDD SS set, or the monitored XDD PDCCH monitoring opportunities and PDCCH candidates or non-overlapping CCEs for non-XDD PDCCH monitoring opportunities to be monitored may be jointly counted (joint counting). That is, PDCCH candidates or non-overlapping CCEs may be counted together for normal TDD operation and XDD operation.
  • Number of PDCCH candidates or non-overlapping CCEs for monitored XDD SS set and monitored non-XDD SS set, or PDCCH candidates or non-overlapping for monitored XDD PDCCH monitoring opportunities and monitored non-XDD PDCCH monitoring opportunities may be counted per slot, per span, or collectively per group of X slots.
  • the monitoring capabilities e.g., monitoringCapabilityConfig-r16 and/or -r17
  • the monitoring capabilities notified configured or defined for the XDD SS set or slot group level.
  • the table shown in FIG. 32 summarizes the relationship between Rel-15/16/17 and PDCCH monitoring capability.
  • Granularity/unit i.e. slot level, span level or slot group level
  • granularity/unit i.e. slot level, span level or slot group level
  • the granularity or unit may be used to count the number of PDCCH candidates or non-overlapping CCEs.
  • the granularity/unit i.e. slot level, span level or slot group level
  • the granularity/unit i.e. slot level, span level or slot group level
  • a larger granularity or unit may be utilized to count the number of PDCCH candidates or non-overlapping CCEs.
  • the maximum number of BD or CCE limits per slot, per span or group of X slots is, for example, ⁇ M′ PDCCH max, slot, ⁇ , C′ PDCCH max, slot, ⁇ ⁇ , ⁇ M′ PDCCH max, (X, Y), ⁇ , C′ PDCCH max, (X, Y), ⁇ ⁇ or ⁇ M′ PDCCH max, Xsslot, ⁇ , C′ PDCCH max, Xsslot, ⁇ ⁇ may be constant or variable.
  • the value of the maximum number of BD or CCE limits per slot, per span, or per group of It may be variable depending on whether it includes any monitoring target XDD PDCCH monitoring opportunity, or whether it includes any PDCCH candidate of the monitoring target XDD SS set. .
  • ⁇ M2' PDCCH max, slot, ⁇ , C2' PDCCH max, slot, ⁇ ⁇ of the XDD slot is different from ⁇ M1' PDCCH max, slot, ⁇ , C1' PDCCH max, slot, ⁇ ⁇ of the non-XDD slot. may be different from
  • ⁇ M2' PDCCH max, (X, Y), ⁇ , C2' PDCCH max, (X, Y), ⁇ ⁇ for an XDD span is different from ⁇ M1' PDCCH max, (X, Y), ⁇ , C1′ PDCCH max, (X, Y), ⁇ ⁇ .
  • ⁇ M2 ' PDCCH max, Xsslot, ⁇ ⁇ M2' PDCCH max, Xsslot, ⁇ , C2' PDCCH max , Xsslot, ⁇ ⁇ .
  • the maximum number of BD or CCE limits for a non-XDD slot, non-XDD span or group of non-XDD slots is the same as the maximum number of BD or CCE limits specified in Rel-15/16/17. , or may be more or less.
  • XDD USS#1, non-XDD USS#2 and non-XDD CSS#1 are the XDD PDCCH monitoring opportunities to be monitored, and the maximum number of BD or CCE limits is ⁇ M1' PDCCH max, slot, ⁇ , C1' PDCCH max , slot, ⁇ ⁇ .
  • XDD USS#1, non-XDD USS#2 and non-XDD CSS#1 are the XDD PDCCH monitoring opportunities to be monitored, and the maximum number of BD or CCE limits is ⁇ M2' PDCCH max, slot, ⁇ , C2' PDCCH max , slot, ⁇ ⁇ .
  • the example shown in FIG. 34A concerns the per-slot PDCCH monitoring capability of Rel-15, where cell #1 is configured for XDD operation and cell #2 is not configured for XDD operation.
  • XDD USS #1, non-XDD USS #2 and non-XDD CSS #1 are the XDD PDCCH monitoring opportunities to be monitored, and the maximum number of BD or CCE limits for cell #1 is ⁇ M2′ PDCCH max, slot, ⁇ , C2′ PDCCH max, slot, ⁇ ⁇ , and the maximum number of BD or CCE limits of cell #2 is ⁇ M1′ PDCCH max, slot, ⁇ , C1′ PDCCH max, slot, ⁇ ⁇ .
  • the example shown in FIG. 34B also relates to the PDCCH monitoring capability for each Rel-15 slot, where cell #1 is configured for XDD operation and cell #2 is not configured for XDD operation.
  • XDD USS #1, non-XDD USS #2 and non-XDD CSS #1 are the XDD PDCCH monitoring opportunities to be monitored, and the maximum number of BD or CCE limits for cell #1 is ⁇ M2′ PDCCH max, slot, ⁇ , C2′ PDCCH max, slot, ⁇ ⁇ , and the maximum number of BD or CCE limits of cell #2 is ⁇ M1′ PDCCH max, slot, ⁇ , C1′ PDCCH max, slot, ⁇ ⁇ .
  • the UE receives PDCCH monitoring capabilities (e.g., monitoringCapabilityConfig) for XDD operations for radio resources (e.g., cells, BWPs, etc.) and controls PDCCH monitoring according to the PDCCH monitoring capabilities. It's okay.
  • the base station may configure PDCCH monitoring capabilities for XDD operations on radio resources and transmit the PDCCH monitoring capabilities.
  • the PDCCH monitoring capability may be set commonly for XDD operation and non-XDD operation.
  • the PDCCH monitoring capability may be configured separately for XDD operation and non-XDD operation.
  • the UE may count PDCCH candidates or non-overlapping control channel elements in XDD operation and PDCCH candidates or non-overlapping control channel elements in non-XDD operation separately or collectively.
  • the above settings or notifications include, for example, RRC (Radio Resource Control) information elements, DCI (Downlink Control Information), and MAC CE (Medium Access Control). Control Element). Also, the present disclosure is not limited to monitoring PDCCH, but may be applied to other types of control signals sent from a base station to a UE or other base station (eg, IAB node, etc.).
  • RRC Radio Resource Control
  • DCI Downlink Control Information
  • MAC CE Medium Access Control
  • Control Element Medium Access Control
  • the present disclosure is not limited to monitoring PDCCH, but may be applied to other types of control signals sent from a base station to a UE or other base station (eg, IAB node, etc.).
  • the UE transmits UE capability information regarding the XDD operation to the base station, and the base station notifies or configures the XDD operation to the UE based on the received UE capability information.
  • the base station notifies or configures the XDD operation to the UE based on the received UE capability information.
  • Capability information may be defined.
  • the UE bases UE capability information regarding whether it supports unified capability notifications, configurations or provisions for monitoring XDD SS sets (or XDD PDCCH monitoring opportunities) and non-XDD SS sets (or XDD PDCCH monitoring opportunities). It may also be sent to the station.
  • UE capability information regarding whether the UE supports separate capability notifications, configurations or provisions for monitoring the XDD SS set (or XDD PDCCH monitoring opportunities) may be defined.
  • the UE may send UE capability information to the base station regarding whether it supports separate capability notifications, configurations or provisions for monitoring the XDD SS set (or XDD PDCCH monitoring opportunities).
  • UE capability information regarding whether the UE supports separate PDCCH candidates and non-overlapping CCE counts for monitoring XDD SS sets (or XDD PDCCH monitoring opportunities) and non-XDD SS sets (or XDD PDCCH monitoring opportunities). may be specified.
  • the UE provides UE capability information regarding whether it supports separate PDCCH candidates and non-overlapping CCE counts for monitoring XDD SS sets (or XDD PDCCH monitoring opportunities) and non-XDD SS sets (or XDD PDCCH monitoring opportunities). It may also be transmitted to the base station.
  • UE capability information regarding whether the UE supports joint PDCCH candidates and non-overlapping CCE counts for monitoring XDD SS sets (or XDD PDCCH monitoring opportunities) and non-XDD SS sets (or XDD PDCCH monitoring opportunities). may be specified.
  • UE operation regarding PDCCH monitoring capability and BD/CCE limit can be defined.
  • the fifth embodiment for a cell in which XDD operation is notified or configured, for a slot, span, or group of X slots that includes or overlaps an XDD time unit or an XDD symbol, whether overbooking is allowed for a slot, span or group of X slots containing a set or for a slot, span or group of X slots containing a monitored XDD PDCCH monitoring opportunity; Or not allowed.
  • the XDD slot may refer to a slot that includes or overlaps an XDD time unit or XDD symbol, includes a monitored XDD SS set, and/or includes a monitored XDD PDCCH monitoring opportunity.
  • the UE may not assume that a number of PDCCH candidates longer than the BD or CCE limit for the cell will be monitored in a slot. . That is, as a difference from Rel-15, when XDD operation is notified or set to Pcell or PScell, overbooking on Pcell or PScell does not need to be assumed.
  • the UE may not assume that a number of PDCCH candidates greater than the BD or CCE limit for the cell will be monitored in the slot.
  • the UE shall ensure that the BD or CCE limit for the cell is not exceeded if XDD operation is notified or configured for the cell.
  • a particular PDCCH candidate may be dropped in the slot during the interval. That is, as a difference from Rel-15, overbooking may be allowed on the Scell if XDD operation is notified or configured on the Scell.
  • the UE shall Certain PDCCH candidates may be dropped.
  • the value of the BD or CCE limit for the Scell may be the same as or different from the value of the BD or CCE limit specified in the Rel-15 monitoring capability for the Pcell or PScell. It's okay.
  • the value of the BD or CCE limit for a cell with XDD operation may be the same as the value of the BD or CCE limit specified in the Rel-15 monitoring capability for a Pcell or PScell. , or may be different.
  • the value of the BD or CCE limit for the XDD slot may be the same as the value of the BD or CCE limit specified in the Rel-15 monitoring capability for the Pcell or PScell, or May be different.
  • the XDD span may refer to a span that includes or overlaps an XDD time unit or XDD symbol, includes a monitored XDD SS set, and/or includes a monitored XDD PDCCH monitoring opportunity.
  • the UE may not assume that a number of PDCCH candidates longer than the BD or CCE limit for the cell will be monitored in a span. . That is, as a difference from Rel-16, when XDD operation is notified or set to Pcell or PScell, overbooking on Pcell or PScell does not need to be assumed.
  • the UE may not assume that a number of PDCCH candidates greater than the BD or CCE limit for the cell will be monitored in the span.
  • the UE when a number of PDCCH candidates longer than the BD or CCE limit is monitored in a span (or the first span in a slot), the UE notifies the cell (or Pcell/PScell) that the XDD operation is If configured, specific PDCCH candidates may be dropped in the span while the BD or CCE limit for the cell (or Pcell/PScell) is not exceeded. That is, as a difference from Rel-16, overbooking may be allowed on the Scell if XDD operation is notified or configured on the Scell. Also, if a cell is notified or configured for XDD operation, overbooking may be allowed on spans other than the first span of the slot.
  • the UE may determine that the span on the cell (or Pcell/PScell) is the XDD span. If so, a specific PDCCH candidate may be dropped in the span while the BD or CCE limit for the cell (or Pcell/PScell) is not exceeded.
  • the value of the BD or CCE limit for a span other than the first span in the slot on the Pcell/PScell is the BD or CCE limit value specified in Rel-16 for the first span in the slot on the Pcell or PScell.
  • it may be the same as the value of the CCE limit, or it may be different.
  • the value of the BD or CCE limit for a cell with XDD operation may be the same as the value of the BD or CCE limit specified in the Rel-16 monitoring capability for a Pcell or PScell. , or may be different.
  • the value of the BD or CCE limit for the first span in the slot on the Scell is the value of the BD or CCE limit specified in Rel-16 for the first span in the slot on the Pcell or PScell. It may be the same as the value or it may be different.
  • the value of the BD or CCE limit for a span other than the first span in the slot on the Scell is the BD or CCE limit value specified in Rel-16 for the first span in the slot on the Pcell or PScell. It may be the same as the value of the CCE limit or may be different.
  • the value of the BD or CCE limit for the XDD span may be the same as or different from the value of the BD or CCE limit specified in Rel-16 for the Pcell or PScell. Good too.
  • an XDD slot group is a group of X slots that includes or overlaps an XDD time unit or XDD symbol, includes a monitored XDD SS set, and/or includes a monitored of X_s slots).
  • the UE when XDD operation is notified or configured for a cell, the UE does not assume that a number of PDCCH candidates longer than the BD or CCE limit for the cell will be monitored in a group of X slots. You can do it like this. That is, as a difference from Rel-17, when XDD operation is notified or set to Pcell, overbooking on Pcell does not need to be assumed.
  • the UE indicates that PDCCH candidates whose number is longer than the BD or CCE limit for the cell are monitored in the group of X slots. You may choose not to assume it.
  • a number of PDCCH candidates longer than the BD or CCE limit are monitored in a group of A particular PDCCH candidate may be dropped in a group of X slots while the BD or CCE limit for the primary) cell is not exceeded. That is, as a difference from Rel-17, overbooking may be allowed on the Scell if XDD operation is notified or configured on the Scell.
  • the UE monitors the corresponding (primary ) A particular PDCCH candidate may be dropped in a group of X slots while the BD or CCE limit for the cell is not exceeded.
  • the value of the BD or CCE limit for the Scell may be the same as or different from the value of the BD or CCE limit specified in the Rel-17 monitoring capability for the primary cell. Good too.
  • the value of the BD or CCE limit for a cell with XDD operation may be the same as the value of the BD or CCE limit specified in the Rel-17 monitoring capability for a Pcell or PScell. , or may be different.
  • the value of the BD or CCE limit for the XDD slot group may be the same as the value of the BD or CCE limit specified in the Rel-17 monitoring capability for the primary cell, or May be different.
  • the UE controls PDCCH overbooking in the XDD time units in which PDCCH monitoring is configured, and performs PDCCH monitoring on selected PDCCH monitoring occasions in the controlled PDCCH overbooking.
  • You may. That is, the UE may drop some of the PDCCH monitoring opportunities that are overbooked.
  • the base station may set a PDCCH monitoring opportunity that is overbooked in the XDD time unit in which PDCCH monitoring is configured, and may transmit control information in the PDCCH monitoring opportunity.
  • the above settings or notifications include, for example, RRC (Radio Resource Control) information elements, DCI (Downlink Control Information), and MAC CE (Medium Access Control). Control Element). Also, the present disclosure is not limited to monitoring PDCCH, but may be applied to other types of control signals sent from a base station to a UE or other base station (eg, IAB node, etc.).
  • RRC Radio Resource Control
  • DCI Downlink Control Information
  • MAC CE Medium Access Control
  • Control Element Medium Access Control
  • the present disclosure is not limited to monitoring PDCCH, but may be applied to other types of control signals sent from a base station to a UE or other base station (eg, IAB node, etc.).
  • the UE transmits UE capability information regarding the XDD operation to the base station, and the base station notifies or configures the XDD operation to the UE based on the received UE capability information.
  • UE capability information regarding whether the UE supports PDCCH overbooking on the cell may be defined.
  • the UE may send UE capability information to the base station regarding whether the UE supports PDCCH overbooking on the cell if the cell is notified or configured for XDD operation.
  • UE capability information regarding whether the UE supports PDCCH overbooking in an XDD slot, XDD span, or XDD slot group may be defined.
  • the UE may send UE capability information to the base station regarding whether it supports PDCCH overbooking in an XDD slot, XDD span, or XDD slot group.
  • UE capability information regarding whether the UE supports PDCCH overbooking by considering XDD SS sets (or XDD PDCCH monitoring opportunities) and non-XDD SS sets (or XDD PDCCH monitoring opportunities) may be defined.
  • the UE may also send UE capability information to the base station regarding whether it supports PDCCH overbooking by considering XDD SS sets (or XDD PDCCH monitoring opportunities) and non-XDD SS sets (or XDD PDCCH monitoring opportunities). good.
  • UE operation regarding PDCCH overbooking can be defined.
  • PDCCH overbooking rules may be defined for XDD operations. Specifically, for the PDCCH overbooking allowed in the fifth embodiment, a UE operation is defined for selecting a PDCCH monitoring opportunity to be monitored/dropped from the overbooked PDCCH monitoring opportunities.
  • the slots, spans, or groups of X slots include or overlap XDD time units or XDD symbols, include any of the monitored When including an XDD PDCCH monitoring opportunity, overbooking may be allowed for the slot, span or group of X slots.
  • the existing PDCCH overbooking rule of Rel-15/16/17 may be reused. That is, the rules of Rel-15/16/17 are applied.
  • whether it is an XDD SS set or a non-XDD SS set may be considered for overbooking.
  • non-XDD CSS may not be expected to be dropped.
  • XDD CSS, non-XDD USS and XDD USS may be dropped based on priority.
  • the UE may not assume that the number of non-XDD CSS PDCCH candidates or non-overlapping CCEs in any slot/span/group of X slots exceeds the BD or CCE limits.
  • the XDD CSS may not be expected to be dropped.
  • Non-XDD CSS, XDD USS and non-XDD USS may be dropped based on priority.
  • non-XDD CSS and XDD CSS may not be expected to be dropped.
  • Non-XDD USSs and XDD USSs may be dropped based on priority.
  • the UE may not assume that the number of PDCCH candidates or non-overlapping CCEs for non-XDD CSS and XDD CSS in any slot/span/group of X slots exceeds the BD or CCE limit. good.
  • XDD CSS and non-XDD CSS may not be expected to be dropped.
  • XDD USS and non-XDD USS may be dropped based on priority.
  • non-XDD CSS, XDD CSS and non-XDD USS may not be expected to be dropped.
  • XDD USS may be dropped based on priority.
  • the UE assumes that the number of PDCCH candidates or non-overlapping CCEs for non-XDD CSS, XDD CSS and non-XDD USS in any slot/span/group of X slots exceeds the BD or CCE limit. You don't have to.
  • non-XDD CSS, XDD CSS and non-XDD USS may not be expected to be dropped.
  • Non-XDD USSs may be dropped based on priority.
  • the XDD CSS, non-XDD CSS, XDD USS, and non-XDD USS may be prioritized as shown in FIG. 35.
  • non-XDD SS set has higher or lower priority than XDD SS set
  • SCS has higher priority than USS
  • Smaller SS index is higher than larger SS index
  • Prioritization may be applied such that "one has a higher priority”.
  • non-XDD CSS may not be expected to be dropped.
  • Non-XDD USSs, XDD CSSs, and XDD USSs may be dropped based on priority.
  • the UE may not assume that the number of non-XDD CSS PDCCH candidates or non-overlapping CCEs in any slot/span/group of X slots exceeds the BD or CCE limits.
  • the XDD CSS may not be expected to be dropped.
  • XDD USS, non-XDD CSS and non-XDD USS may be dropped based on priority.
  • non-XDD CSS and non-XDD USS may not be expected to be dropped.
  • XDD CSS and XDD USS may be dropped based on priority.
  • the UE shall not assume that the number of non-XDD CSS and non-XDD USS PDCCH candidates or non-overlapping CCEs in any slot/span/group of X slots exceeds the BD or CCE limit. Good too.
  • XDD CSS and XDD USS may not be expected to be dropped.
  • Non-XDD CSSs and non-XDD USSs may be dropped based on priority.
  • non-XDD CSS, non-XDD USS and XDD CSS may not be expected to be dropped.
  • XDD USS may be dropped based on priority.
  • the UE assumes that the number of PDCCH candidates or non-overlapping CCEs for non-XDD CSS, non-XDD USS and XDD CSS in any slot/span/group of X slots exceeds the BD or CCE limit. You don't have to.
  • XDD CSS, XDD USS and non-XDD CSS may not be expected to be dropped.
  • Non-XDD USSs may be dropped based on priority.
  • the XDD CSS, non-XDD CSS, XDD USS, and non-XDD USS may be prioritized as shown in FIG. 36.
  • XDD CSS #1 and XDD USS #1 are monitored, and non-XD USS #2 can be dropped.
  • XDD CSS #1 and non-XD USS #2 are monitored, and XDD USS #1 can be dropped.
  • non-XD USS #2 and XDD CSS #1 are monitored, and XDD USS #1 can be dropped.
  • the XDD PDCCH monitoring opportunity refers to a PDCCH monitoring opportunity that includes or overlaps an XDD time unit or an XDD symbol.
  • non-XDD PDCCH monitoring opportunities refer to PDCCH monitoring opportunities that do not include or overlap XDD time units or XDD symbols.
  • PDCCH candidates of non-XDD PDCCH monitoring opportunities in the CSS set may not be expected to be dropped.
  • PDCCH candidates for XDD PDCCH monitoring opportunities in the CSS set, non-XDD PDCCH monitoring opportunities in the USS set, and XDD PDCCH monitoring opportunities in the USS set may be dropped based on priority.
  • the UE does not assume that the number of PDCCH candidates or non-overlapping CCEs for non-XDD PDCCH monitoring opportunities in a CSS set in any slot/span/group of X slots exceeds the BD or CCE limit. It's okay.
  • the PDCCH candidates of the XDD PDCCH monitoring opportunity of the CSS set may not be expected to be dropped.
  • PDCCH candidates for non-XDD PDCCH monitoring opportunities in the CSS set, XDD PDCCH monitoring opportunities in the USS set, and non-XDD PDCCH monitoring opportunities in the USS set may be dropped based on priority.
  • the PDCCH candidates of the non-XDD PDCCH monitoring opportunities of the CSS set and the XDD PDCCH monitoring opportunities of the CSS set may not be expected to be dropped.
  • PDCCH candidates for non-XDD PDCCH monitoring opportunities in the USS set and XDD PDCCH monitoring opportunities in the USS set may be dropped based on priority.
  • the UE determines whether the number of PDCCH candidates or non-overlapping CCEs for non-XDD PDCCH monitoring opportunities in the CSS set and XDD PDCCH monitoring opportunities in the CSS set in any slot/span/group of X slots is BD or CCE limit. It is not necessary to assume that the amount will be exceeded.
  • the PDCCH candidates of the XDD PDCCH monitoring opportunities of the CSS set and the non-XDD PDCCH monitoring opportunities of the CSS set may not be expected to be dropped.
  • PDCCH candidates for XDD PDCCH monitoring opportunities in the USS set and non-XDD PDCCH monitoring opportunities in the USS set may be dropped based on priority.
  • PDCCH candidates of non-XDD PDCCH monitoring opportunities in the CSS set, XDD PDCCH monitoring opportunities in the CSS set, and non-XDD PDCCH monitoring opportunities in the USS set are not expected to be dropped.
  • PDCCH candidates for XDD PDCCH monitoring opportunities in the USS set may be dropped based on priority.
  • the UE may detect non-XDD PDCCH monitoring opportunities in the CSS set, XDD PDCCH monitoring opportunities in the CSS set, and non-XDD PDCCH monitoring opportunities in the USS set in any slot/span/group of It is not necessary to assume that the number of wrapped CCEs exceeds the BD or CCE limit.
  • PDCCH candidates for XDD PDCCH monitoring opportunities in the CSS set, non-XDD PDCCH monitoring opportunities in the CSS set, and XDD PDCCH monitoring opportunities in the USS set may not be expected to be dropped.
  • PDCCH candidates for non-XDD PDCCH monitoring opportunities in the USS set may be dropped based on priority.
  • XDD PDCCH monitoring opportunities in the CSS set can be prioritized as shown in FIG.
  • non-XDD PDCCH monitoring opportunities have higher or lower priority than XDD PDCCH monitoring opportunities” ⁇ “CSS has higher priority than USS” ⁇ “Smaller SS index has higher A prioritization "with higher priority than the SS index" may be applied.
  • PDCCH candidates of non-XDD PDCCH monitoring opportunities in the CSS set may not be expected to be dropped.
  • PDCCH candidates for non-XDD PDCCH monitoring opportunities in the USS set, XDD PDCCH monitoring opportunities in the CSS set, and XDD PDCCH monitoring opportunities in the USS set may be dropped based on priority.
  • the UE does not assume that the number of PDCCH candidates or non-overlapping CCEs for non-XDD PDCCH monitoring opportunities in a CSS set in any slot/span/group of X slots exceeds the BD or CCE limit. It's okay.
  • the PDCCH candidates of the XDD PDCCH monitoring opportunity of the CSS set may not be expected to be dropped.
  • PDCCH candidates for XDD PDCCH monitoring opportunities in the USS set, non-XDD PDCCH monitoring opportunities in the CSS set, and non-XDD PDCCH monitoring opportunities in the USS set may be dropped based on priority.
  • PDCCH candidates of non-XDD PDCCH monitoring opportunities in the CSS set and non-XDD PDCCH monitoring opportunities in the USS set may not be expected to be dropped.
  • PDCCH candidates for the XDD PDCCH monitoring opportunities in the CSS set and the XDD PDCCH monitoring opportunities in the USS set may be dropped based on priority.
  • the UE may detect non-XDD PDCCH monitoring opportunities in the CSS set, non-XDD PDCCH monitoring opportunities in the USS set, and PDCCH candidates or non-over It is not necessary to assume that the number of wrapped CCEs exceeds the BD or CCE limit.
  • the PDCCH candidates of the XDD PDCCH monitoring opportunity of the CSS set and the XDD PDCCH monitoring opportunity of the USS set may not be expected to be dropped.
  • PDCCH candidates for non-XDD PDCCH monitoring opportunities in the CSS set and non-XDD PDCCH monitoring opportunities in the USS set may be dropped based on priority.
  • PDCCH candidates of non-XDD PDCCH monitoring opportunities in the CSS set, non-XDD PDCCH monitoring opportunities in the USS set, and XDD PDCCH monitoring opportunities in the CSS set are not expected to be dropped.
  • PDCCH candidates for XDD PDCCH monitoring opportunities in the USS set may be dropped based on priority.
  • the UE may detect non-XDD PDCCH monitoring opportunities in the CSS set, non-XDD PDCCH monitoring opportunities in the USS set, and PDCCH candidates or non-over It is not necessary to assume that the number of wrapped CCEs exceeds the BD or CCE limit.
  • the PDCCH candidates of the XDD PDCCH monitoring opportunities in the CSS set, the XDD PDCCH monitoring opportunities in the USS set, and the non-XDD PDCCH monitoring opportunities in the CSS set may not be expected to be dropped.
  • PDCCH candidates for non-XDD PDCCH monitoring opportunities in the USS set may be dropped based on priority.
  • XDD PDCCH monitoring opportunities in the CSS set can be prioritized as shown in FIG.
  • CSS #1 (XDD MO) and USS #1 (XDD MO) are monitored, and USS #2 (non-XDD MO) is dropped. It can be done.
  • CSS #1 (XDD MO) and USS #2 (non-XDD MO) are monitored, and USS #1 (XDD MO) can be dropped.
  • USS #1 (XDD MO) and CSS #1 (XDD MO) are monitored, and USS #1 (XDD MO) can be dropped.
  • the UE controls PDCCH overbooking in the XDD time units in which PDCCH monitoring is configured, and performs PDCCH monitoring on selected PDCCH monitoring occasions in the controlled PDCCH overbooking.
  • PDCCH monitoring opportunities may be selected according to prioritization. That is, the UE may drop some PDCCH monitoring opportunities that are overbooked according to the prioritization.
  • PDCCH monitoring opportunities provide a first prioritization between common search spaces (CSS) and user-specific search spaces (USS), non-XDD search space sets (non-XDD SS) and XDD search spaces.
  • the selection may be based on a second prioritization between sets (XDD SS) and a third prioritization between search space indexes (SS index).
  • the PDCCH monitoring opportunity may be selected further based on a fourth prioritization between non-XDD PDCCH monitoring opportunities and XDD PDCCH monitoring opportunities.
  • the above settings or notifications include, for example, RRC (Radio Resource Control) information elements, DCI (Downlink Control Information), and MAC CE (Medium Access Control). Control Element). Also, the present disclosure is not limited to monitoring PDCCH, but may be applied to other types of control signals sent from a base station to a UE or other base station (eg, IAB node, etc.).
  • RRC Radio Resource Control
  • DCI Downlink Control Information
  • MAC CE Medium Access Control
  • Control Element Medium Access Control
  • the present disclosure is not limited to monitoring PDCCH, but may be applied to other types of control signals sent from a base station to a UE or other base station (eg, IAB node, etc.).
  • the UE transmits UE capability information regarding the XDD operation to the base station, and the base station notifies or configures the XDD operation to the UE based on the received UE capability information.
  • UE capability information regarding whether the UE supports PDCCH overbooking on the cell may be defined.
  • the UE may send UE capability information to the base station regarding whether the UE supports PDCCH overbooking on the cell if the cell is notified or configured for XDD operation.
  • UE capability information regarding whether the UE supports PDCCH overbooking in an XDD slot, XDD span, or XDD slot group may be defined.
  • the UE may send UE capability information to the base station regarding whether it supports PDCCH overbooking in an XDD slot, XDD span, or XDD slot group.
  • UE capability information regarding whether the UE supports PDCCH overbooking by considering XDD SS sets (or XDD PDCCH monitoring opportunities) and non-XDD SS sets (or XDD PDCCH monitoring opportunities) may be specified.
  • the UE may also send UE capability information to the base station regarding whether it supports PDCCH overbooking by considering XDD SS sets (or XDD PDCCH monitoring opportunities) and non-XDD SS sets (or XDD PDCCH monitoring opportunities). good.
  • UE operation regarding PDCCH overbooking can be defined.
  • the UE is configured for single-cell operation or operation with carrier aggregation (CA) in the same frequency band, and is configured to a property of "type D" for active DL BWP of one or more cells.
  • CA carrier aggregation
  • the UE shall, on the active DL BWP of a cell with one or more cells, PDCCH may be monitored only in a CORESET and any other CORESET from a plurality of CORESETs in which the qcl-Type is set to the same property of “typeD” as the CORESET. If any cell is advertised or configured for XDD operation, the CORESET may be determined as the CORESET of the SS with the highest priority.
  • the prioritization is as follows: "CSS has higher priority than USS” ⁇ "Smaller cell index has higher priority than larger cell index” ⁇ "Smaller SS index has higher priority than larger SS index” may be applied.
  • the CORESET corresponds to the CSS set with the smallest index in the cell with the smallest index containing the CSS, if any, and otherwise to the USS set with the smallest index in the cell with the smallest index. You may respond.
  • Option 2-2 of the seventh embodiment is that “cells that are not notified or configured for XDD operation have higher or lower priority than cells that are notified or configured for XDD operation” ⁇ “CSS is USS
  • the priority as shown in FIG. 42 is "A smaller cell index has a higher priority than a larger cell index” -> "A smaller SS index has a higher priority than a larger SS index” Ranking may be applied.
  • Option 1 According to the prioritization of Option 1, Option 2-1 and 2-2, CSS #1 in Cell #1, USS #2 in Cell #1, USS #3 in Cell #1, USS #1 in Cell #2 and The five PDCCH monitoring beams of CSS #2 of cell #2 may be prioritized as shown in FIG. 43, for example. Note that XDD operation is notified or set for cell #1, and XDD operation is not notified or set for cell #2.
  • FIG. 43A the existing rules of Rel-15/16 are applied, and CSS #1 of cell #1, CSS #2 of cell #2, USS #2 of cell #1, USS #3 of cell #1, and cell #2 USS #1 is prioritized in descending order of priority.
  • option 2-1 prioritization is applied, with CSS #2 of cell #2, CSS #1 of cell #1, USS #1 of cell #2, USS #2 of cell #1 and cell # USS#3 of 1 is prioritized in descending order of priority.
  • option 2-2 prioritization is applied, with CSS #2 of cell #2, USS #1 of cell #2, CSS #1 of cell #1, USS #2 of cell #1 and cell # USS#3 of 1 is prioritized in descending order of priority.
  • Option 1 2-1 and 2-2
  • CSS #1 in Cell #1, USS #2 in Cell #1, USS #3 in Cell #1 and USS in Cell #2 may be prioritized as shown in FIG. 44, for example.
  • XDD operation is notified or set for cell #1, and XDD operation is not notified or set for cell #2.
  • FIG. 44A the existing rules of Rel-15/16 are applied, and CSS #1 of cell #1, USS #2 of cell #1, USS #3 of cell #1, and USS #1 of cell #2 are Prioritized in descending order of priority.
  • option 2-1 prioritization is applied, and CSS #1 of cell #1, USS #1 of cell #2, USS #2 of cell #1, and USS #3 of cell #1 are prioritized. prioritized in descending order.
  • option 2-2 prioritization is applied, and USS #1 of cell #2, CSS #1 of cell #1, USS #2 of cell #1, and USS #3 of cell #1 are prioritized. prioritized in descending order.
  • the XDD SS set means an SS set in which the XDD time unit is set.
  • a non-XDD SS set means an SS set in which a pure time unit is set.
  • Option 3-1 of the seventh embodiment is that "non-XDD SS set has higher or lower priority than XDD SS set" ⁇ "CSS has higher priority than USS” ⁇ "Smaller cell index is higher than larger cell index” Prioritization as shown in FIG. 45 may be applied, such as "a smaller SS index has a higher priority than a larger SS index”.
  • Option 3-2 of the seventh embodiment is that “CSS has higher priority than USS” ⁇ “Non-XDD SS set has higher or lower priority than XDD SS set” ⁇ “Smaller cell index has higher priority than USS” Prioritization as shown in FIG. 46 may be applied, such as "a smaller SS index has a higher priority than a larger SS index”.
  • “CSS has higher priority than USS” ⁇ “non-XDD CSS set has higher or lower priority than XDD CSS set” ⁇ “smaller cell index A prioritization such as "larger cell index has higher priority” ⁇ “smaller SS index has higher priority than larger SS index” may be applied.
  • Non-XDD CSS set is XDD
  • a prioritization may be applied in which the CSS set has higher or lower priority than the smaller SS index has higher or lower priority than the larger SS index.
  • “CSS has higher priority than USS” ⁇ “Smaller cell index has higher priority than larger cell index” ⁇ “Non-XDD USS A prioritization may be applied such that a set has a higher or lower priority than an XDD USS set" ⁇ "a smaller SS index has a higher priority than a larger SS index”.
  • CSS #1 of cell #1, USS #2 of cell #1, USS #3 of cell #1 , the five PDCCH monitoring beams of USS #1 of cell #2 and CSS #2 of cell #2 may be prioritized as shown in FIG. 48, for example.
  • CSS #1 of cell #1, USS #2 of cell #1, and USS #1 of cell #2 are the XDD SS set
  • USS #3 of cell #1 and CSS #2 of cell #2 are This is a non-XDD SS set.
  • FIG. 48A the existing rules of Rel-15/16 are applied, CSS #1 of cell #1, CSS #2 of cell #2, USS #2 of cell #1, USS #3 of cell #1, and cell #2 USS #1 is prioritized in descending order of priority.
  • option 3-1 prioritization is applied, with CSS #2 of cell #2, USS #3 of cell #1, CSS #1 of cell #1, USS #2 of cell #1 and cell # USS#1 of 2 is prioritized in descending order of priority.
  • option 3-2 prioritization is applied, with CSS #2 of cell #2, CSS #1 of cell #1, USS #3 of cell #1, USS #2 of cell #1 and cell # USS#1 of 2 is prioritized in descending order of priority.
  • option 3-3 prioritization is applied, with CSS #1 in cell #1, CSS #2 in cell #2, USS #3 in cell #1, USS #2 in cell #1, and cell #1 in cell #1, CSS #2 in cell #2, USS #3 in cell #1, USS#1 of 2 is prioritized in descending order of priority.
  • CSS #1 of cell #1, USS #2 of cell #1, USS #3 of cell #1 and the four PDCCH monitoring beams of USS #1 of cell #2 may be prioritized as shown in FIG. 49, for example.
  • CSS #1 of cell #1 and USS #2 of cell #1 are XDD SS sets
  • USS #3 of cell #1 and USS #1 of cell #2 are non-XDD SS sets.
  • FIG. 49A the existing rules of Rel-15/16 are applied, and CSS #1 of cell #1, USS #2 of cell #1, USS #3 of cell #1, and USS #1 of cell #2 are Prioritized in descending order of priority.
  • option 3-1 prioritization is applied, and USS #3 of cell #1, USS #1 of cell #2, CSS #1 of cell #1, and USS #2 of cell #1 are prioritized. prioritized in descending order.
  • option 3-2 prioritization is applied, and CSS #1 of cell #1, USS #3 of cell #1, USS #1 of cell #2, and USS #2 of cell #1 are prioritized. prioritized in descending order.
  • option 3-3 prioritization is applied, and CSS #1 of cell #1, USS #3 of cell #1, USS #2 of cell #1, and USS #1 of cell #2 are prioritized. prioritized in descending order.
  • XDD PDCCH monitoring opportunity refers to a PDCCH monitoring opportunity that includes or overlaps an XDD time unit or an XDD symbol.
  • non-XDD PDCCH monitoring opportunities refer to PDCCH monitoring opportunities that do not include or overlap XDD time units or XDD symbols.
  • non-XDD PDCCH monitoring opportunities have higher or lower priority than XDD PDCCH monitoring opportunities”
  • SCS has higher priority than USS
  • Smaller cell index has higher priority than Prioritization as shown in FIG. 45
  • a smaller SS index has a higher priority than a cell index
  • a smaller SS index has a higher priority than a larger SS index
  • Non-XDD PDCCH monitoring opportunity is XDD PDCCH monitoring opportunity A prioritization as shown in FIG. 47 may be applied, such as "a smaller SS index has a higher priority than a larger SS index".
  • CSS #1 of cell #1, USS #2 of cell #1, USS #3 of cell #1 , the five PDCCH monitoring beams of USS #1 of cell #2 and CSS #2 of cell #2 may be prioritized as shown in FIG. 50, for example.
  • CSS #1 of cell #1, USS #2 of cell #1, and USS #1 of cell #2 are XDD PDCCH monitoring opportunities
  • USS #3 of cell #1 and CSS #2 of cell #2 are , is a non-XDD PDCCH monitoring opportunity.
  • FIG. 50A the existing rules of Rel-15/16 are applied, CSS #1 of cell #1, CSS #2 of cell #2, USS #2 of cell #1, USS #3 of cell #1, and cell #2 USS #1 is prioritized in descending order of priority.
  • option 4-1 prioritization is applied, with CSS #2 of cell #2, USS #3 of cell #1, CSS #1 of cell #1, USS #2 of cell #1 and cell # USS#1 of 2 is prioritized in descending order of priority.
  • option 4-2 prioritization is applied, with CSS #2 of cell #2, CSS #1 of cell #1, USS #3 of cell #1, USS #2 of cell #1 and cell # USS#1 of 2 is prioritized in descending order of priority.
  • FIG. 50D the prioritization of option 4-3 is applied, with CSS #1 of cell #1, CSS #2 of cell #2, USS #3 of cell #1, USS #2 of cell #1, and cell #1.
  • USS#1 of 2 is prioritized in descending order of priority.
  • CSS #1 of cell #1, USS #2 of cell #1, USS #3 of cell #1 and the four PDCCH monitoring beams of USS #1 of cell #2 may be prioritized as shown in FIG. 51, for example.
  • CSS #1 of cell #1 and USS #2 of cell #1 are XDD PDCCH monitoring opportunities
  • USS #3 of cell #1 and USS #1 of cell #2 are non-XDD PDCCH monitoring opportunities.
  • FIG. 51A the existing rules of Rel-15/16 are applied, and CSS #1 of cell #1, USS #2 of cell #1, USS #3 of cell #1, and USS #1 of cell #2 are Prioritized in descending order of priority.
  • option 4-1 prioritization is applied, and USS #3 of cell #1, USS #1 of cell #2, CSS #1 of cell #1, and USS #2 of cell #1 are prioritized. prioritized in descending order.
  • option 4-2 prioritization is applied, and CSS #1 of cell #1, USS #3 of cell #1, USS #1 of cell #2, and USS #2 of cell #1 are prioritized. prioritized in descending order.
  • option 4-3 prioritization is applied, and CSS #1 of cell #1, USS #3 of cell #1, USS #2 of cell #1, and USS #1 of cell #2 are prioritized. prioritized in descending order.
  • option 5 of the seventh embodiment whether there is a cell for which XDD operation is notified or configured and whether there is an XDD SS set or a non-XDD SS set may be taken into consideration for the determination. That is, option 5 is a combination of option 2 and option 3.
  • Option 5-1 of the seventh embodiment is that “cells that are not notified or configured for XDD operation have a higher or lower priority than cells that are notified or configured for XDD operation” ⁇ “non-XDD SS Set has higher or lower priority than XDD SS set” ⁇ "CSS has higher priority than USS” ⁇ "Smaller cell index has higher priority than larger cell index” ⁇ "Smaller SS index has higher priority A prioritization "with higher priority than the SS index" may be applied.
  • Option 5-2 of the seventh embodiment is that “cells that are not notified or configured for XDD operation have higher or lower priority than cells that are notified or configured for XDD operation” ⁇ “CSS is USS "has higher priority” ⁇ "non-XDD SS set has higher or lower priority than XDD SS set” ⁇ "smaller cell index has higher priority than larger cell index” ⁇ "smaller SS index has higher priority than A prioritization "with higher priority than the SS index” may be applied.
  • Option 5-3 of the seventh embodiment is that “cells that are not notified or configured for XDD operation have higher or lower priority than cells that are notified or configured for XDD operation” ⁇ “CSS is USS "Smaller cell index has higher priority than larger cell index” ⁇ "Non-XDD SS set has higher or lower priority than XDD SS set” ⁇ "Smaller SS index has higher priority than larger cell index” A prioritization "with higher priority than the SS index" may be applied.
  • “Smaller SS index has higher or lower priority than XDD SS set” A prioritization "with higher priority than the SS index” may be applied.
  • CSS has higher priority than USS”
  • Cells that are not notified or configured for XDD operation are not notified or configured for XDD operation.”
  • a non-XDD CSS/USS set has a higher or lower priority than an XDD CSS/USS set”
  • a smaller cell index has a higher priority than a larger cell index”
  • a prioritization may be applied where "smaller SS indexes have higher priority than larger SS indexes”.
  • a prioritization “with higher priority than the SS index” may be applied.
  • option 6 of the seventh embodiment whether there is an XDD SS set or a non-XDD SS set and whether there is an XDD PDCCH monitoring opportunity or a non-XDD PDCCH monitoring opportunity may be taken into consideration for the determination. That is, option 6 is a combination of option 3 and option 4.
  • Non-XDD SS set has higher or lower priority than XDD SS set
  • Non-XDD PDCCH monitoring opportunity has higher or lower priority than XDD PDCCH monitoring opportunity
  • the prioritization is applied as follows: "CSS has higher priority than USS” ⁇ "Smaller cell index has higher priority than larger cell index” ⁇ "Smaller SS index has higher priority than larger SS index” It's okay.
  • non-XDD SS set has higher or lower priority than XDD SS set”
  • SCS has higher priority than USS
  • Smaller cell index is larger than cell index
  • a prioritization may be applied such that "a smaller SS index has a higher priority than a larger SS index”.
  • non-XDD SS set has higher or lower priority than XDD SS set
  • SCS has higher priority than USS
  • Smaller cell index is larger than cell index
  • the prioritization is applied such that "non-XDD PDCCH monitoring opportunities have higher or lower priority than XDD PDCCH monitoring opportunities" ⁇ "smaller SS indexes have higher priority than larger SS indexes”. It's okay.
  • Option 6-5 of the seventh embodiment is that “CSS has higher priority than USS” ⁇ “Non-XDD SS set has higher or lower priority than XDD SS set” ⁇ “Smaller cell index has higher priority than USS”
  • the prioritization is applied such that "non-XDD PDCCH monitoring opportunities have higher or lower priority than XDD PDCCH monitoring opportunities" ⁇ "smaller SS indexes have higher priority than larger SS indexes”. It's okay.
  • “CSS has higher priority than USS” ⁇ “Non-XDD CSS/USS set has higher or lower priority than XDD CSS/USS set” ⁇ “ “Smaller cell index has higher priority than larger cell index” ⁇ "Non-XDD PDCCH monitoring opportunity has higher or lower priority than XDD PDCCH monitoring opportunity” ⁇ "Smaller SS index has higher priority than larger SS index ” may be applied.
  • “CSS has higher priority than USS” ⁇ “Smaller cell index has higher priority than larger cell index” ⁇ “Non-XDD CSS/USS set has higher or lower priority than the XDD CSS/USS set” ⁇ “Non-XDD PDCCH monitoring opportunities have higher or lower priority than the XDD PDCCH monitoring opportunities” ⁇ “Smaller SS indexes have higher priority than larger SS indexes ” may be applied.
  • option 7 of the seventh embodiment whether there is a cell for which XDD operation is notified or configured and whether there is an XDD PDCCH monitoring opportunity or a non-XDD PDCCH monitoring opportunity may be taken into consideration for the determination. . That is, option 7 is a combination of option 2 and option 4.
  • Cells that are not notified or configured for XDD operation have higher or lower priority than cells that are notified or configured for XDD operation” ⁇ “Non-XDD PDCCH Monitoring opportunities have higher or lower priority than XDD PDCCH monitoring opportunities” ⁇ "CSS has higher priority than USS” ⁇ "Smaller cell index has higher priority than larger cell index” ⁇ "Smaller SS index A prioritization may be applied in which a larger SS index has a higher priority.
  • Option 7-2 of the seventh embodiment is that “cells that are not notified or configured for XDD operation have higher or lower priority than cells that are notified or configured for XDD operation” ⁇ “CSS is USS "Non-XDD PDCCH monitoring opportunities have higher or lower priority than XDD PDCCH monitoring opportunities” ⁇ "Smaller cell indexes have higher priority than larger cell indexes” ⁇ "Smaller SS indexes have higher priority than A prioritization may be applied in which a larger SS index has a higher priority.
  • Option 7-3 of the seventh embodiment is that “cells that are not notified or configured for XDD operation have higher or lower priority than cells that are notified or configured for XDD operation” ⁇ “CSS is USS "Smaller cell index has higher priority than larger cell index” ⁇ "Non-XDD PDCCH monitoring opportunity has higher or lower priority than XDD PDCCH monitoring opportunity” ⁇ "Smaller SS index A prioritization may be applied in which a larger SS index has a higher priority.
  • a prioritization may be applied in which a larger SS index has a higher priority.
  • “Smaller SS index has higher or lower priority than XDD PDCCH monitoring opportunity” A prioritization may be applied in which a larger SS index has a higher priority.
  • Option 8 of the seventh embodiment determines whether there is a cell for which XDD operation is notified or configured, whether there is an XDD SS set or a non-XDD SS set, and whether there is an XDD PDCCH monitoring opportunity or a non-XDD PDCCH monitoring opportunity. Whether or not it is may be taken into consideration for the determination. That is, option 8 is a combination of option 2, option 3, and option 4.
  • Option 8-1 of the seventh embodiment is that “cells that are not notified or configured for XDD operation have higher or lower priority than cells that are notified or configured for XDD operation” ⁇ “non-XDD SS set has a higher or lower priority than the XDD SS set” ⁇ “Non-XDD PDCCH monitoring opportunities have higher or lower priority than the A prioritization such as "larger cell index has higher priority” ⁇ "smaller SS index has higher priority than larger SS index” may be applied.
  • Option 8-2 of the seventh embodiment is that “cells that are not notified or configured for XDD operation have a higher or lower priority than cells that are notified or configured for XDD operation” ⁇ “non-XDD SS Set has higher or lower priority than XDD SS set” ⁇ "CSS has higher priority than USS” ⁇ "Smaller cell index has higher priority than larger cell index” ⁇ "Smaller SS index has higher priority A prioritization "with higher priority than the SS index" may be applied.
  • Option 8-3 of the seventh embodiment is that “cells that are not notified or configured for XDD operation have higher or lower priority than cells that are notified or configured for XDD operation” ⁇ “non-XDD SS set has higher or lower priority than XDD SS set” ⁇ “CSS has higher priority than USS” ⁇ "Smaller cell index has higher priority than larger cell index” ⁇ "Non-XDD PDCCH monitoring opportunities are XDD A prioritization may be applied in which a PDCCH monitoring opportunity has higher or lower priority than a smaller SS index has a higher or lower priority than a larger SS index.
  • Option 8-4 of the seventh embodiment is that "cells that are not advertised or configured for XDD operation have higher or lower priority than cells that are advertised or configured for XDD operation" ⁇ "CSS is USS "Non-XDD SS set has higher or lower priority than XDD SS set” ⁇ "Non-XDD PDCCH monitoring opportunity has higher or lower priority than XDD PDCCH monitoring opportunity” ⁇ "Smaller cell index A prioritization may be applied in which the SS index has a higher priority than a larger cell index ⁇ the SS index has a higher priority than a larger SS index.
  • Option 8-5 of the seventh embodiment is that “CSS has higher priority than USS” ⁇ “Cells that are not notified or configured for XDD operation have higher priority than cells that are notified or configured for XDD operation. "Smaller cell index has higher priority than larger cell index” ⁇ "Non-XDD SS set has higher or lower priority than XDD SS set” ⁇ "Non-XDD PDCCH monitoring opportunity is XDD A prioritization may be applied in which a PDCCH monitoring opportunity has higher or lower priority than a smaller SS index has a higher or lower priority than a larger SS index.
  • Option 8-6 of the seventh embodiment is that “cells that are not notified or configured for XDD operation have higher or lower priority than cells that are notified or configured for XDD operation” ⁇ “CSS is USS "Non-XDD SS set has higher or lower priority than XDD SS set” ⁇ "Smaller cell index has higher priority than larger cell index” ⁇ "Non-XDD PDCCH monitoring opportunity is XDD A prioritization may be applied in which a PDCCH monitoring opportunity has higher or lower priority than a smaller SS index has a higher or lower priority than a larger SS index.
  • Option 8-8 of the seventh embodiment is that "cells that are not advertised or configured for XDD operation have higher or lower priority than cells that are advertised or configured for XDD operation" ⁇ "CSS is USS "Smaller cell index has higher priority than larger cell index” ⁇ "Non-XDD SS set has higher or lower priority than XDD SS set” ⁇ "Non-XDD PDCCH monitoring opportunity is XDD A prioritization may be applied in which a PDCCH monitoring opportunity has higher or lower priority than a smaller SS index has a higher or lower priority than a larger SS index.
  • the UE may select a PDCCH monitoring beam in the XDD time unit for which PDCCH monitoring is configured, and perform PDCCH monitoring on the selected PDCCH monitoring beam.
  • the base station may control the PDCCH monitoring beam in XDD time units in which PDCCH monitoring is configured, and may transmit control information through the PDCCH monitoring beam.
  • the UE may select the PDCCH monitoring beam according to the prioritization.
  • the PDCCH monitoring beam also has a first prioritization between common search space (CSS) and user-specific search space (USS), a second prioritization between cell indexes, and a search space index (SS index). ) may be selected based on a third prioritization between:
  • the PDCCH monitoring beam also uses a fourth prioritization, non-XDD search space (non-XDD SS) set, between cells where XDD operation is configured or notified and cells where XDD operation is not configured or notified. and an XDD search space (XDD SS) set, and a sixth prioritization between non-XDD PDCCH monitoring opportunities and XDD PDCCH monitoring opportunities. may be done.
  • non-XDD search space non-XDD search space
  • XDD SS XDD search space
  • the above settings or notifications include, for example, RRC (Radio Resource Control) information elements, DCI (Downlink Control Information), and MAC CE (Medium Access Control). Control Element). Also, the present disclosure is not limited to monitoring PDCCH, but may be applied to other types of control signals sent from a base station to a UE or other base station (eg, IAB node, etc.).
  • RRC Radio Resource Control
  • DCI Downlink Control Information
  • MAC CE Medium Access Control
  • Control Element Medium Access Control
  • the present disclosure is not limited to monitoring PDCCH, but may be applied to other types of control signals sent from a base station to a UE or other base station (eg, IAB node, etc.).
  • the UE transmits UE capability information regarding the XDD operation to the base station, and the base station notifies or configures the XDD operation to the UE based on the received UE capability information.
  • PDCCH monitoring opportunities by considering whether a cell is notified or configured for XDD operation, whether there is an XDD SS set or a non-XDD SS set, and/or whether there is an XDD PDCCH monitoring opportunity.
  • UE capability information regarding whether it supports determining TCI states for including or overlapping PDCCH monitoring may be defined.
  • the UE includes PDCCH monitoring opportunities by considering whether the cell is notified or configured for XDD operation, whether there is an XDD SS set or a non-XDD SS set, and/or whether there is an XDD PDCCH monitoring opportunity.
  • UE capability information regarding whether it supports determining TCI states for overlapping PDCCH monitoring may be sent to the base station.
  • UE operation regarding the PDCCH monitoring beam can be defined.
  • the applicable embodiments, options and/or operations may be signaled or configured by upper layer parameters, may be signaled or reported by the UE as UE capability information, or may be signaled or reported in the specification. It may be specified or determined by the configuration of upper layer parameters and the reported UE capability information.
  • 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 do it.
  • 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. 52 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 the user terminal 20 may be configured to include one or more of each device shown in FIG. 52, 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 on 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, or a magneto-optical disk (for example, 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 a network device, network controller, network card, communication module, etc., for example.
  • 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.
  • Each aspect/embodiment described in this disclosure is LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system). system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (x is an integer or decimal number, for example)), FRA (Future Radio Access), NR (new Radio), New radio access ( NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802 Systems that utilize .16 (WiMAX (registered trademark)), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth (registered trademark), and other appropriate systems, and that are extended, modified, created, and defined based on these.
  • the present invention may be
  • 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. 53 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.
  • a receiving unit that receives a notification or setting regarding an XDD (Cross Division Duplex) operation for a wireless resource, and a receiving unit that receives an update for the wireless resource according to the notification or setting regarding the XDD operation.
  • a terminal is provided, the terminal having a controller that controls link transmission or downlink reception.
  • radio resources for example, cells, BWP, etc.
  • the receiving unit receives a notification or configuration regarding an XDD operation on a per-frequency resource basis for a time unit on a bandwidth portion, and the notification or configuration regarding an XDD operation on a per-frequency resource basis is configured on the bandwidth portion.
  • a first frequency resource may be advertised or configured for uplink transmission or downlink reception, and a second frequency resource of the bandwidth portion may be advertised or configured for downlink reception or uplink transmission. According to this embodiment, it becomes possible to set the XDD operation in units of frequency resources.
  • the receiving unit receives a notification or configuration regarding a per-terminal XDD operation for a time unit on a bandwidth portion, and the notification or configuration regarding a per-terminal XDD operation includes an uplink transmission of the time unit.
  • the first terminal may be notified or set for downlink reception, and the time unit may be notified or set for downlink reception or uplink transmission to a second terminal. According to this embodiment, it becomes possible to set the XDD operation on a terminal-by-terminal basis.
  • the receiving unit may receive a notification or configuration indicating a bandwidth portion of a cell in which XDD operation is configured, or a bandwidth portion for XDD operation of the cell. According to this embodiment, it is possible to specify the BWP in which the XDD operation is set.
  • a transmitting unit that transmits a notification or setting regarding an XDD (Cross Division Duplex) operation for a radio resource;
  • a base station is provided that includes a control unit that controls reception.
  • radio resources for example, cells, BWP, etc.
  • a method of wireless communication performed by a terminal comprising: controlling a wireless communication method;
  • radio resources for example, cells, BWP, etc.
  • a terminal includes a receiving unit that receives PDCCH monitoring settings for XDD (Cross Division Duplex) operation, and a control unit that controls PDCCH monitoring according to the PDCCH monitoring settings. .
  • the PDCCH monitoring configuration may include a first PDCCH monitoring configuration for a non-XDD time unit and a second PDCCH monitoring configuration for an XDD time unit. According to this embodiment, appropriate PDCCH monitoring settings can be set for each of XDD operation and non-XDD operation.
  • the first PDCCH monitoring configuration includes one or more of a search space set configuration, a CORESET (Control REsource SET) configuration, a frequency domain resource configuration, and a frequency monitoring location configuration for the non-XDD time unit;
  • the second PDCCH monitoring configuration includes one or more search space set configurations, one or more CORESET configurations, one or more frequency domain resource configurations, and one or more frequency monitoring location configurations for the XDD time unit. But that's fine.
  • appropriate PDCCH monitoring settings can be set for each of XDD operation and non-XDD operation.
  • the PDCCH monitoring configuration includes a PDCCH search space configuration, and the controller determines whether the PDCCH monitoring opportunity indicated by the PDCCH search space configuration overlaps with an XDD time unit. PDCCH monitoring may also be controlled. According to this embodiment, PDCCH monitoring can be appropriately realized depending on whether or not the PDCCH monitoring opportunity instructed by the PDCCH search space setting overlaps with the XDD time unit.
  • a base station includes a setting unit that sets PDCCH monitoring settings for XDD (Cross Division Duplex) operation, and a transmitting unit that transmits the PDCCH monitoring settings.
  • XDD Cross Division Duplex
  • a wireless communication device performed by a terminal, comprising: receiving a PDCCH monitoring configuration for XDD (Cross Division Duplex) operation; and controlling PDCCH monitoring according to the PDCCH monitoring configuration.
  • XDD Cross-Divplex Division Duplex
  • a communication method is provided.
  • a terminal includes a receiving unit that receives a PDCCH monitoring capability regarding XDD (Cross Division Duplex) operation for radio resources, and a control unit that controls PDCCH monitoring according to the PDCCH monitoring capability.
  • the PDCCH monitoring capability may be set commonly for XDD operation and non-XDD operation. According to this embodiment, it is possible to appropriately implement PDCCH monitoring in XDD operation according to the PDCCH monitoring capability.
  • the PDCCH monitoring capability may be configured separately for XDD and non-XDD operations. According to this embodiment, it is possible to appropriately implement PDCCH monitoring in XDD operation according to the PDCCH monitoring capability.
  • control unit may count PDCCH candidates or non-overlapping control channel elements in XDD operation and PDCCH candidates or non-overlapping control channel elements in non-XDD operation separately or collectively. According to this embodiment, it is possible to appropriately implement PDCCH monitoring in XDD operation according to the PDCCH monitoring capability.
  • a base station that includes a control unit that sets a PDCCH monitoring capability regarding XDD (Cross Division Duplex) operation for radio resources, and a transmitting unit that transmits the PDCCH monitoring capability. Ru.
  • the terminal includes: receiving a PDCCH monitoring capability regarding XDD (Cross Division Duplex) operation for radio resources; and controlling PDCCH monitoring according to the PDCCH monitoring capability.
  • XDD Cross Division Duplex
  • a wireless communication method is provided.
  • a control unit that controls PDCCH overbooking in an XDD (Cross Division Duplex) time unit in which PDCCH monitoring is set, and a PDCCH monitoring opportunity selected in the controlled PDCCH overbooking.
  • a receiving unit that performs PDCCH monitoring at a terminal is provided.
  • control unit may select PDCCH monitoring opportunities according to prioritization.
  • PDCCH monitoring opportunities can be appropriately selected according to prioritization.
  • the PDCCH monitoring opportunities include a first prioritization between a common search space and a user-specific search space, a second prioritization between a non-XDD search space set and an XDD search space set. , and a third prioritization between the search space indexes.
  • PDCCH monitoring opportunities can be appropriately selected according to prioritization.
  • the PDCCH monitoring opportunities may be selected further based on a fourth prioritization between non-XDD PDCCH monitoring opportunities and XDD PDCCH monitoring opportunities.
  • PDCCH monitoring opportunities can be appropriately selected according to prioritization.
  • a control unit that sets a PDCCH monitoring opportunity that is overbooked in an XDD (Cross Division Duplex) time unit in which PDCCH monitoring is set, and transmits control information at the PDCCH monitoring opportunity.
  • a base station is provided having a transmitter.
  • PDCCH overbooking is controlled in XDD (Cross Division Duplex) time units in which PDCCH monitoring is set, and in a PDCCH monitoring opportunity selected in the controlled PDCCH overbooking.
  • XDD Cross Division Duplex
  • a wireless communication method performed by a terminal comprising: performing PDCCH monitoring.
  • a control unit that selects a PDCCH monitoring beam in an XDD (Cross Division Duplex) time unit in which PDCCH monitoring is set, and performs PDCCH monitoring on the selected PDCCH monitoring beam.
  • a terminal having a receiving unit is provided.
  • the controller may select the PDCCH monitoring beams according to prioritization. According to this embodiment, a PDCCH monitoring beam can be appropriately selected.
  • the PDCCH monitoring beams have a first prioritization between common search spaces and user-specific search spaces, a second prioritization between cell indexes, and a third prioritization between search space indexes.
  • the selection may be based on prioritization.
  • a PDCCH monitoring beam can be appropriately selected.
  • the PDCCH monitoring beam includes a fourth prioritization between cells with XDD operation configured or notified and cells with no XDD operation configured or notified, non-XDD search space sets and The selection may be further based on one or more of a fifth prioritization between search space sets and a sixth prioritization between non-XDD PDCCH monitoring opportunities and XDD PDCCH monitoring opportunities. According to this embodiment, a PDCCH monitoring beam can be appropriately selected.
  • a control unit that controls a PDCCH monitoring beam in XDD (Cross Division Duplex) time units in which PDCCH monitoring is set; a transmitting unit that transmits control information using the PDCCH monitoring beam; A base station is provided.
  • XDD Cross Division Duplex
  • a wireless communication method performed by a terminal comprising:
  • 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 read as "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.
  • 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

Un mode de réalisation de la présente invention concerne un terminal qui comprend une unité de commande pour sélectionner un faisceau de surveillance de PDCCH dans des unités de temps de duplex à répartition croisée (XDD) où une surveillance de PDCCH est définie, et une unité de réception pour exécuter une surveillance de PDCCH sur le faisceau de surveillance de PDCCH sélectionné.
PCT/JP2022/019200 2022-04-27 2022-04-27 Terminal, station de base et procédé de communication sans fil WO2023209913A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP2022/019200 WO2023209913A1 (fr) 2022-04-27 2022-04-27 Terminal, station de base et procédé de communication sans fil

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2022/019200 WO2023209913A1 (fr) 2022-04-27 2022-04-27 Terminal, station de base et procédé de communication sans fil

Publications (1)

Publication Number Publication Date
WO2023209913A1 true WO2023209913A1 (fr) 2023-11-02

Family

ID=88518409

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2022/019200 WO2023209913A1 (fr) 2022-04-27 2022-04-27 Terminal, station de base et procédé de communication sans fil

Country Status (1)

Country Link
WO (1) WO2023209913A1 (fr)

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
CENC: "Discussion on sub band non-overlapping full duplex", 3GPP TSG RAN WG1 #109-E R1-2204412, 24 April 2022 (2022-04-24), XP052137471 *
INTERDIGITAL: "InterDigital's Views on Rel-18 Scope for NR-Advanced", 3GPP RAN REL-18 WORKSHOP, RWS-210422, 7 June 2021 (2021-06-07), XP052025975 *
SAMSUNG: "XDD (cross-division duplex) for enhanced duplexing operation in 5G Advanced", 3GPP TSG RAN REL-18 WORKSHOP, ELECTRONIC MEETING, RWS-210180, 7 June 2021 (2021-06-07), XP052025739 *

Similar Documents

Publication Publication Date Title
WO2023209913A1 (fr) Terminal, station de base et procédé de communication sans fil
WO2023209910A1 (fr) Terminal, station de base et procédé de communication sans fil
WO2023209911A1 (fr) Terminal, station de base et procédé de communication sans fil
WO2023209917A1 (fr) Terminal, station de base et procédé de communication sans fil
WO2023209915A1 (fr) Terminal, station de base et procédé de communication sans fil
WO2024150342A1 (fr) Terminal et procédé de communication
WO2023209920A1 (fr) Terminal, station de base et procédé de communication sans fil
WO2024150343A1 (fr) Terminal et procédé de communication
WO2023209916A1 (fr) Terminal, station de base et procédé de communication sans fil
WO2024150332A1 (fr) Terminal et procédé de communication
WO2024181445A1 (fr) Terminal, et procédé de communication sans fil
WO2024106418A1 (fr) Terminal, station de base et procédé de communication
WO2024023984A1 (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
WO2024023994A1 (fr) Terminal, station de base et procédé de communication sans fil
WO2024100746A1 (fr) Terminal, station de base et procédé de communication
WO2024106467A1 (fr) Terminal et procédé de communication sans fil
WO2023199497A1 (fr) Terminal, station de base et procédé de communication
WO2024084839A1 (fr) Terminal et procédé de communication
WO2023199495A1 (fr) Terminal, station de base et procédé de communication
WO2024106463A1 (fr) Terminal et procédé de communication sans fil
WO2023199496A1 (fr) Terminal, station de base et procédé de communication
WO2024084829A1 (fr) Terminal et procédé de communication
WO2023203623A1 (fr) Terminal, station de base et procédé de communication
WO2024095486A1 (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: 22940190

Country of ref document: EP

Kind code of ref document: A1