Terminal, base station, and wireless communication method

Abstract

According to one aspect of the present disclosure, provided is a terminal comprising: a receiving unit that receives PDCCH monitoring capability for a cross division duplex (XDD) operation for radio resources; and a control unit that controls the PDCCH monitoring in accordance with the PDCCH monitoring capability.

Description

[Technical Field] 【0001】 This disclosure relates to terminals, base stations, and wireless communication methods. [Background technology] 【0002】 Long Term Evolution (LTE) was specified for the Universal Mobile Telecommunications System (UMTS) network with the aim of achieving even higher data rates and lower latency. Furthermore, LTE-Advanced (3GPP Rel.10-14) was specified to further enhance the capacity and sophistication of LTE (Third Generation Partnership Project (3GPP) Release (Rel.) 8, 9). 【0003】 Successor systems to LTE (for example, 5th generation mobile communication system (5G), 5G+ (plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel.15 and later, etc.) are also being considered. [Prior art documents] [Patent Documents] 【0004】 [Non-Patent Document 1] “Initial Views on Release 18 NR” RP-210293, 3GPP TSG RAN Meeting #91-e Electronic Meeting, March 16 -26, 2021 [Overview of the Initiative] 【0005】 In future wireless communication systems (e.g., NR), it is anticipated that multiple user terminals (User Equipment (UE)) will communicate in extremely high-density and high-traffic environments. 【0006】 In such an environment, it is anticipated that uplink (UL) resources will be insufficient compared to downlink (DL) resources. 【0007】 However, previous NR specifications have not adequately considered methods for increasing uplink resources. If these methods cannot be properly controlled, there is a risk of system performance degrading, such as increased latency and reduced coverage performance. 【0008】 Therefore, one of the objectives of this disclosure is to provide terminals, base stations, and wireless communication methods that improve the efficiency of resource utilization. 【0009】 According to one aspect of this disclosure, a terminal is provided having a receiving unit that receives notifications or settings related to XDD (Cross Division Duplex) operation for a wireless resource, and a control unit that controls uplink transmission or downlink reception on the wireless resource in accordance with the notifications or settings related to the XDD operation. According to another aspect of this disclosure, a terminal is provided having 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. According to another aspect of this disclosure, a terminal is provided having a receiving unit that receives PDCCH monitoring capability for XDD (Cross Division Duplex) operation on a wireless resource, and a control unit that controls PDCCH monitoring in accordance with the PDCCH monitoring capability. According to other aspects of the present disclosure, a terminal is provided having a control unit that controls PDCCH overbooking in XDD (Cross Division Duplex) time units in which PDCCH monitoring is set, and a receiving unit that performs PDCCH monitoring at selected PDCCH monitoring opportunities in the controlled PDCCH overbooking. According to another aspect of the present disclosure, a terminal is provided having a control unit that selects a PDCCH monitoring beam in an XDD (Cross Division Duplex) time unit in which PDCCH monitoring is set, and a receiving unit that performs PDCCH monitoring on the selected PDCCH monitoring beam. [Brief explanation of the drawing] 【0010】 [Figure 1] This block diagram shows the functional configuration of a base station (gNB) according to one embodiment of the present disclosure. [Figure 2] This is a block diagram showing the functional configuration of a terminal (UE) according to one embodiment of the present disclosure. [Figure 3] This figure shows an example of the arrangement of wireless resources in an XDD (Cross Division Duplex) according to one embodiment of the present disclosure. [Figure 4] This figure shows the XDD operation according to one embodiment of the present disclosure. [Figure 5] This figure shows a pure time unit and an XDD time unit according to one embodiment of the present disclosure. [Figure 6] This figure shows a PDCCH monitoring opportunity according to one embodiment of the present disclosure. [Figure 7] This figure shows a PDCCH overbooking according to one embodiment of the present disclosure. [Figure 8] This figure shows a PDCCH monitoring beam according to one embodiment of the present disclosure. [Figure 9] This figure shows an example of XDD configuration according to one embodiment of the present disclosure. [Figure 10] This figure shows an example of the arrangement of wireless resources for XDD according to one embodiment of the present disclosure. [Figure 11] This figure shows an example of XDD configuration according to one embodiment of the present disclosure. [Figure 12] This figure shows an example of the arrangement of wireless resources for XDD according to one embodiment of the present disclosure. [Figure 13] This figure shows an example of XDD configuration and wireless resource placement according to one embodiment of the present disclosure. [Figure 14] This figure shows an example of XDD configuration and wireless resource placement according to one embodiment of the present disclosure. [Figure 15] This figure shows an example of XDD configuration according to one embodiment of the present disclosure. [Figure 16] This figure shows an example of the arrangement of wireless resources for XDD according to one embodiment of the present disclosure. [Figure 17] This figure shows an example of XDD configuration and wireless resource placement according to one embodiment of the present disclosure. [Figure 18] This figure shows an example of XDD configuration and wireless resource placement according to one embodiment of the present disclosure. [Figure 19] This figure shows an example of XDD configuration according to one embodiment of the present disclosure. [Figure 20] This figure shows an example of the arrangement of wireless resources for XDD according to one embodiment of the present disclosure. [Figure 21] This figure shows an example of XDD configuration and wireless resource placement according to one embodiment of the present disclosure. [Figure 22] This figure shows an example of XDD configuration and wireless resource placement according to one embodiment of the present disclosure. [Figure 23] This figure shows an example of XDD configuration according to one embodiment of the present disclosure. [Figure 24] This figure shows an example of the arrangement of wireless resources for XDD according to one embodiment of the present disclosure. [Figure 25] This figure shows an example of the arrangement of wireless resources for XDD according to one embodiment of the present disclosure. [Figure 26] This figure shows an example of the arrangement of wireless resources for XDD according to one embodiment of the present disclosure. [Figure 27] This figure shows an example of the arrangement of wireless resources for XDD according to one embodiment of the present disclosure. [Figure 28] This figure shows an example of the arrangement of wireless resources for XDD according to one embodiment of the present disclosure. [Figure 29] This figure shows an example of the arrangement of wireless resources for XDD according to one embodiment of the present disclosure. [Figure 30] This figure shows an example of the arrangement of wireless resources for XDD according to one embodiment of the present disclosure. [Figure 31] This figure shows an example of the arrangement of wireless resources for XDD according to one embodiment of the present disclosure. [Figure 32] This figure illustrates the monitoring capabilities of each release according to one embodiment of the present disclosure. [Figure 33] This figure shows an example of the arrangement of wireless resources for XDD according to one embodiment of the present disclosure. [Figure 34] This figure shows an example of the arrangement of wireless resources for XDD according to one embodiment of the present disclosure. [Figure 35] This figure shows the prioritization according to one embodiment of the present disclosure. [Figure 36] This figure shows the prioritization according to one embodiment of the present disclosure. [Figure 37] This figure shows an example of the arrangement of wireless resources for XDD according to one embodiment of the present disclosure. [Figure 38] This figure shows the prioritization according to one embodiment of the present disclosure. [Figure 39] This figure shows the prioritization according to one embodiment of the present disclosure. [Figure 40] This figure shows an example of the arrangement of wireless resources for XDD according to one embodiment of the present disclosure. [Figure 41] This figure shows the prioritization according to one embodiment of the present disclosure. [Figure 42] This figure shows the prioritization according to one embodiment of the present disclosure. [Figure 43] This figure shows the prioritization according to one embodiment of the present disclosure. [Figure 44] This figure shows the prioritization according to one embodiment of the present disclosure. [Figure 45] This figure shows the prioritization according to one embodiment of the present disclosure. [Figure 46] This figure shows the prioritization according to one embodiment of the present disclosure. [Figure 47] This figure shows the prioritization according to one embodiment of the present disclosure. [Figure 48] This figure shows the prioritization according to one embodiment of the present disclosure. [Figure 49] This figure shows the prioritization according to one embodiment of the present disclosure. [Figure 50] This figure shows the prioritization according to one embodiment of the present disclosure. [Figure 51] This figure shows the prioritization according to one embodiment of the present disclosure. [Figure 52] This block diagram shows the hardware configuration of a base station and a terminal according to one embodiment of the present disclosure. [Figure 53] This is a block diagram showing the hardware configuration of a vehicle according to one embodiment of the present disclosure. [Modes for carrying out the invention] 【0011】 Embodiments of this disclosure will be described below with reference to the drawings. 【0012】 (Wireless communication system) The configuration of a wireless communication system according to one embodiment of this disclosure will be described below. In this wireless communication system, communication is performed using any or a combination thereof of the wireless communication methods according to the above embodiments of this disclosure. The wireless communication system may be a system that realizes communication using Long Term Evolution (LTE), 5th generation mobile communication system New Radio (5G NR), or successor wireless communication systems specified by the Third Generation Partnership Project (3GPP). 【0013】 Furthermore, the wireless communication system may support dual connectivity between multiple Radio Access Technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC may include dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), dual connectivity between NR and LTE (NR-E-UTRA Dual Connectivity (NE-DC)), and so on. 【0014】 In EN-DC, the LTE (E-UTRA) base station (eNB) is the Master Node (MN), and the NR base station (gNB) is the Secondary Node (SN). In NE-DC, the NR base station (gNB) is the MN, and the LTE (E-UTRA) base station (eNB) is the SN. 【0015】 A wireless communication system may support dual connectivity between multiple base stations within the same RAT (for example, dual connectivity where both the MN and SN are NR base stations (gNB) (NR-NR Dual Connectivity (NN-DC))). 【0016】 The wireless communication system may include a base station forming a macrocell C1 with relatively wide coverage, and a base station located within the macrocell C1 that forms a small cell C2 with narrower coverage than the macrocell C1. Terminals (UEs) may be located within at least one cell. The arrangement, number, etc., of each cell and terminal are not limited to any particular configuration. 【0017】 The terminal may connect to at least one of several base stations. The terminal may utilize at least one of Carrier Aggregation (CA) using multiple Component Carriers (CC) and Dual Connectivity (DC). 【0018】 Each CC may be included in at least one of the first frequency band (Frequency Range 1 (FR1)) and the second frequency band (Frequency Range 2 (FR2)). A macrocell C1 may be included in FR1, and a small cell C2 may be included in FR2. For example, FR1 may be a frequency band of 6 GHz or less (sub-6 GHz), and FR2 may be a frequency band above 24 GHz (above-24 GHz). Note that the frequency bands and definitions of FR1 and FR2 are not limited to these, and for example, FR1 may fall in a frequency band higher than FR2. 【0019】 Furthermore, each CC may communicate using at least one of Time Division Duplex (TDD) and Frequency Division Duplex (FDD). 【0020】 Multiple base stations may be connected by wire (e.g., optical fiber compliant with Common Public Radio Interface (CPRI), X2 interface, etc.) or wireless (e.g., NR communication). For example, when NR communication is used as a backhaul between two base stations, the base station acting as the upstream station may be called an Integrated Access Backhaul (IAB) donor, and the base station acting as a relay station may be called an IAB node. 【0021】 Base stations may be connected to the core network via other base stations or directly. The core network may include at least one of the following: for example, an Evolved Packet Core (EPC), a 5G Core Network (5GCN), or a Next Generation Core (NGC). 【0022】 The terminal may be one that supports at least one of the following communication methods: LTE, LTE-A, 5G, 6G, etc. 【0023】 In wireless communication systems, orthogonal frequency division multiplexing (OFDM)-based wireless access schemes may be used. For example, Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), etc., may be used in at least one of the downlink (DL) and uplink (UL). 【0024】 The wireless access method may also be called a waveform. In wireless communication systems, other wireless access methods (for example, other single-carrier transmission methods, other multi-carrier transmission methods) may be used in addition to the UL and DL wireless access methods. 【0025】 In wireless communication systems, downlink channels may include Physical Downlink Shared Channels (PDSCH), broadcast channels (PBCH), and Physical Downlink Control Channels (PDCCH), which are shared among all terminals. 【0026】 Furthermore, in wireless communication systems, uplink channels such as the Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), and Physical Random Access Channel (PRACH) may be used as uplink channels shared by each terminal. 【0027】 User data, higher-layer control information, and System Information Blocks (SIBs) are transmitted via PDSCH. User data and higher-layer control information may also be transmitted via PUSCH. Furthermore, Master Information Blocks (MIBs) may be transmitted via PBCH. 【0028】 Lower-layer control information may be transmitted by PDCCH. The lower-layer control information may include, for example, Downlink Control Information (DCI) which includes scheduling information for at least one of PDSCH and PUSCH. 【0029】 Furthermore, the DCI that schedules PDSCH may be called a DL assignment or DL ​​DCI, and the DCI that schedules PUSCH may be called a UL grant or UL DCI. Furthermore, PDSCH may be interpreted as DL data, and PUSCH may be interpreted as UL data. 【0030】 PDCCH detection may utilize a Control Resource Set (CORESET) and a search space. A CORESET corresponds to the resources used to search for DCIs. A search space corresponds to the search area and search method for PDCCH candidates. A single CORESET may be associated with one or more search spaces. The UE may monitor CORESETs associated with a particular search space based on the search space configuration. 【0031】 A single search space may correspond to one or more aggregation levels of PDCCH candidates. One or more search spaces may be referred to as a search space (SS) set. In this disclosure, "search space," "search space set," "search space configuration," "search space set configuration," "CORESET," and "CORESET configuration" may be interpreted interchangeably. 【0032】 PUCCH may transmit uplink control information (UCI) which includes at least one of the following: channel state information (CSI), delivery acknowledgment (e.g., Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, etc.), and scheduling request (SR). PRACH may transmit a random access preamble for establishing a connection with the cell. 【0033】 In this disclosure, the term "Physical" may be omitted from the beginning of each channel. 【0034】 In a wireless communication system, a synchronization signal (SS), a downlink reference signal (DL-RS), etc., may be transmitted. In a wireless communication system, the DL-RS may include a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DMRS), a positioning reference signal (PRS), a phase tracking reference signal (PTRS), etc. 【0035】 The synchronization signal may be, for example, at least one of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS). A signal block including SS (PSS, SSS) and PBCH (and DMRS for PBCH) may be called an SS / PBCH block, SS Block (SSB), etc. Note that SS, SSB, etc. may also be called reference signals. 【0036】 Furthermore, in wireless communication systems, the Uplink Reference Signal (UL-RS) may transmit the Sounding Reference Signal (SRS), Demodulation Reference Signal (DMRS), etc. The DMRS may also be called the UE-specific Reference Signal. 【0037】 (Device configuration) Next, an example of the functional configuration of a base station (gNB) 100 and a terminal (UE) 200 that perform the processing and operations described later will be explained. The gNB 100 and UE 200 include functions that realize the embodiments described later. However, the gNB 100 and UE 200 may each have only some of the functions in the embodiments. 【0038】 (gNB100) Figure 1 shows an example of the functional configuration of gNB100. As shown in Figure 1, gNB100 has a receiving unit 101, a transmitting unit 102, and a control unit 103. The functional configuration shown in Figure 1 is merely an example. Any functional classification and functional unit names are acceptable as long as they enable the operation according to the embodiment of the present invention. 【0039】 The receiving unit 101 includes the function of receiving various signals transmitted from the UE200 and obtaining information from higher layers, for example, from the received signals. The transmitting unit 102 includes the function of generating a signal to be transmitted to the UE200 and transmitting the signal by wire or wireless. 【0040】 The control unit 103 stores pre-configured setting information and various setting information to be transmitted to the UE200 in a storage device and reads it from the storage device as needed. The control unit 103 also performs processing related to communication with the UE200. The signal transmission function in the control unit 103 may be included in the transmission unit 102, and the signal reception function in the control unit 103 may be included in the reception unit 101. 【0041】 (UE200) Figure 2 shows an example of the functional configuration of the UE200. As shown in Figure 2, the UE200 has a transmitter 201, a receiver 202, and a control unit 203. The functional configuration shown in Figure 2 is merely an example. Any functional classification and name of the functional unit may be used as long as it enables the operation according to the embodiment of the present invention. 【0042】 The transmitting unit 201 creates a transmission signal from the transmission data and transmits the transmission signal wirelessly. The receiving unit 202 wirelessly receives various signals and acquires signals from higher layers from the received physical layer signals. The receiving unit 202 also has the function of receiving NR-PSS, NR-SSS, NR-PBCH, DL / UL control signals or reference signals transmitted from the gNB100. 【0043】 The control unit 203 stores various setting information received from the gNB100 by the receiving unit 202 in a storage device and reads it from the storage device as needed. The control unit 203 also performs processing related to communication with the gNB100. The signal transmission function in the control unit 203 may be included in the transmitting unit 201, and the signal reception function in the control unit 203 may be included in the receiving unit 202. 【0044】 (XDD operation) Considering the transmission / reception time ratio (e.g., DL:UL = 4:1) in Time Division Duplex (TDD) up to Rel. 16, there are cases where the opportunities to transmit UL signals / channels are fewer than the opportunities to receive DL signals / channels. In such cases, the UE may not be able to transmit UL signals / channels frequently, raising concerns about transmission delays for important UL signals / channels. Furthermore, because the opportunities to transmit UL signals are fewer than the opportunities to receive DL signals, signal / channel congestion during UL transmission is also a concern. In addition, since the time resources available for transmitting UL signals / channels are limited in TDD, the application of UL coverage extension techniques such as repetition transmission is also limited. 【0045】 In future wireless communication systems (e.g., Rel.17 / 18 and beyond), the introduction of a division duplex method combining TDD and Frequency Division Duplex (FDD) for UL and DL is being considered. 【0046】 This division-duplex method may also be called XDD (Cross Division Duplex) or subband non-overlapping full duplex. XDD or subband non-overlapping full duplex may mean a duplex method in which DL and UL are frequency-division multiplexed within one component carrier (CC) of the TDD band (allowing DL and UL to be used simultaneously). 【0047】 Figure 3A shows an example of a TDD configuration as defined up to Rel. 16. In the example shown in Figure 3A, a TDD slot or symbol is configured in the UE in a bandwidth such as one component carrier (CC) (which may also be called a cell or serving cell) and a bandwidth portion (BWP). 【0048】 In the example shown in Figure 3A, the time ratio of DL slots to UL slots is 4:1. With such conventional TDD slot or symbol settings, sufficient UL time resources cannot be secured, which may lead to UL transmission delays and reduced coverage performance. 【0049】 Figure 3B shows an example of an XDD configuration. In the example shown in Figure 3B, the resources used for receiving DLs and the resources used for transmitting ULs overlap in time within a single component carrier (CC). This resource configuration allows for the allocation of more UL resources, thereby improving resource utilization efficiency. 【0050】 For example, as shown in the example in Figure 3B, the ends of the frequency domain may be set as DL resources, and UL resources may be sandwiched between these DL resources. This can avoid and mitigate the occurrence of cross-link interference (CLI) with neighboring carriers. In addition, a guard region may be set at the boundary between the DL resources and the UL resources. 【0051】 Given the complexity of handling self-interference, it is conceivable that only base stations would use DL and UL resources simultaneously. In other words, for radio resources where DL and UL overlap in time, one UE could use the DL resource while another UE uses the UL resource. 【0052】 Figure 4 shows an example of XDD operation. In the example shown in Figure 4, a portion of the DL resources in the TDD band are set as UL resources, and the DL and UL are configured to partially overlap in the time domain. 【0053】 In the example shown in Figure 4, during the DL-only period, each of the multiple UEs (UE#1 and UE#2 in Figure 4) receives the DL channel / signal. 【0054】 Furthermore, during periods when DL and UL overlap in time, one UE (UE#1 in the example in Figure 4) receives the DL channel / signal, while another UE (UE#2 in the example in Figure 4) transmits the UL channel / signal. During this period, the base station performs simultaneous transmission and reception of DL and UL. 【0055】 Furthermore, during UL-only periods, each of the multiple UEs (UE#1 and UE#2 in Figure 4) transmits a UL channel / signal. 【0056】 In existing NRs (e.g., those defined up to Rel. 15 / 16), DL frequency resources and UL frequency resources in the UE carrier are configured as DL BWPs and UL BWPs, respectively. Switching between DL / UL frequency resources requires the configuration of multiple BWPs and a BWP adaptation mechanism. 【0057】 Furthermore, in existing NRs, the time resources in the TDD carrier for UE are configured as at least one of DL, UL, and Flexible (FL) in the TDD configuration. 【0058】 An XDD symbol may be a symbol that is notified or set as UL (or DL) on one frequency resource, or notified or set for UL transmission (or DL ​​reception), while on another frequency resource it may be a symbol that is notified or set as DL (or UL) or notified or set for DL ​​reception (or UL transmission). Alternatively, an XDD symbol may be a symbol that is notified or set as UL (or DL) on a portion of the frequency resource, or notified or set for UL transmission (or DL ​​reception). Alternatively, an XDD symbol may be a symbol that is notified or set as DL (or UL) on a portion of the frequency resource, or notified or set for DL ​​reception (or UL transmission). 【0059】 Here, the time unit may be at the symbol level, the slot / subslot level, or a group of symbols / slots / subslots. That is, the XDD time unit may be an XDD symbol, a slot / subslot containing or overlapping an XDD symbol, or a group of symbols / slots / subslots containing or overlapping an XDD symbol. 【0060】 A pure time unit may be a non-XDD symbol (i.e., a symbol that is not an XDD symbol), a slot / subslot that does not contain or overlap XDD symbols, or a group of symbols / slots / subslots that do not contain or overlap XDD symbols, and may also be called a non-XDD time unit. For example, a pure time unit may be referred to as a time unit consisting only of DLs on a frequency resource, as shown in Figure 5A, or as a time unit consisting only of ULs on a frequency resource, as shown in Figure 5B. 【0061】 Furthermore, with respect to the XDD time unit, DL resources and UL resources may have various arrangement patterns in the frequency domain. For example, the XDD time unit of frequency domain pattern #1 may have the arrangement pattern shown in Figure 5C. The XDD time unit of frequency domain pattern #2 may have the arrangement pattern shown in Figure 5D. The XDD time unit of frequency domain pattern #3 may have the arrangement pattern shown in Figure 5E. These arrangement patterns are merely examples, and other arrangement patterns may be used. The frequency domain pattern of the XDD time unit may mean a resource repetition pattern in the frequency domain for the XDD time unit. 【0062】 (PDCCH monitoring) In Rel-15 / 16, the UE performs blind decoding (BD) on a set of PDCCH (Physical Downlink Control Channel) candidates for a configured set of search space (SS) elements. Specifically, the UE determines PDCCH monitoring opportunities on active DL BWPs based on the PDCCH monitoring period, PDCCH monitoring offset, and PDCCH monitoring pattern within a slot. For example, with a PDCCH monitoring period k=5, PDCCH monitoring offset o=2, and PDCCH monitoring pattern (duration) d=3, the UE monitors PDCCH candidates within a slot of the search space (SS) set as shown in Figure 6. 【0063】 Specifically, the UE monitors PDCCH candidates in each monitored slot at PDCCH monitoring opportunities as shown in Figure 6. In the illustrated example, if the CORESET duration is 2 and monitoringSymbolsWithinSlot=10001000100000, the UE monitors PDCCH candidates at PDCCH monitoring opportunity #0 corresponding to symbols "0" and "1", and at PDCCH monitoring opportunity #1 corresponding to symbols "4" and "5". 【0064】 (PDCCH monitoring capability) Furthermore, PDCCH monitoring capability can be notified or configured per slot in Rel-15, per span in Rel-16, and for multiple slots in Rel-17. For per-slot PDCCH monitoring capability in Rel-15, overbooking, which involves setting a number of PDCCH candidates and / or control channel elements (CCEs) that exceeds the UE capability, is permitted only on primary cells (Pcell) or primary secondary cells (PScell). For per-span PDCCH monitoring capability in Rel-16, overbooking is permitted only on the first span of a slot on a Pcell / PScell. For multi-slot PDCCH monitoring capability in Rel-17, overbooking is permitted only on Pcells / PScells. 【0065】 Furthermore, overbooking is not permitted for the Common Search Space (CSS). That is, the network ensures that the number of non-overlapping CCEs and PDCCH candidates 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. 【0066】 On the other hand, for UE-specific search spaces (USS), overbooking is permitted based on the USS index. Specifically, USS with smaller search space (SS) indices may have higher priority. That is, USS with larger SS indices are dropped until the number of PDCCH candidates and non-overlapping CCEs for a slot, span, or group of X slots falls below the blind decoding (BD) or control channel element (CCE) limit. 【0067】 For example, as shown in Figure 7, if USS#1 with 28 CCEs, USS#2 with 24 CCEs, and CSS#1 with 24 CCEs are in the slot, and the limit is 56, then only CSS#1 and USS#1, which have higher priority and do not exceed the limit of 56, will be monitored as PDCCH candidates. 【0068】 (PDCCH monitoring beam) For overlapping PDCCH monitoring opportunities, if the TCI (Transmission Configuration Indication) state or beam is set to CORESET, the UE monitors PDCCH candidates that have the same TCI state included in or overlapping with the PDCCH monitoring opportunity. The TCI state is determined by the SS with the highest priority. Here, CSS has a higher priority than USS, SS with a smaller cell index has a higher priority than SS with a larger cell index, and SS with a smaller SS index has a higher priority than SS with a larger SS index. 【0069】 According to the prioritization described above, for example, the SS of CSS#1 in cell #1, the SS of CSS#2 in cell #2, the SS of USS#2 in cell #1, and the SS of USS#1 in cell #2 are prioritized as shown in Figure 8, and PDCCH candidates are monitored for the SS of CSS#1 in cell #1 and the SS of USS#2 in cell #1. 【0070】 (First embodiment) Specific constraints on XDD operation have not been discussed at this time. For example, XDD operation may not be supported for certain cells. 【0071】 In Example 1, the cells or time resources on which XDD operation can be configured are limited. The UE may not expect a Pcell / PScell ​​to be notified of or configured for XDD operation. The UE may also not expect any cell in a primary / secondary cell group to be notified of, configured of, or applied to XDD operation. Alternatively, the UE may not expect any BWP or cell on which a Search Space (SS) set and / or CORESET configuration is configured to be notified of or configured for XDD operation. Alternatively, even if XDD operation is notified of or configured, the UE may not expect any BWP or cell on which a particular type of SS set and / or a particular type of CORESET configuration is configured to be notified of or configured as UL (or DL) on some frequency resources, or notified of or configured for UL transmission (or DL ​​reception). 【0072】 Here, a specific type of SS set is: i) The Type0-PDCCH CSS set is configured by pdcch-ConfigSIB1 in the MIB (Master Information Block), by searchSpaceSIB1 in PDCCH-ConfigCommon, and by searchSpaceZero in PDCCH-ConfigCommon. ii) The Type0A-PDCCH CSS set configured by searchSpaceOtherSystemInformation in PDCCH-ConfigCommon. iii) Type1-PDCCH CSS set configured by ra-SearchSpace in PDCCH-ConfigCommon iv) Type2-PDCCH CSS set configured by pagingSearchSpace in PDCCH-ConfigCommon v) A Type3-PDCCH CSS set configured by SearchSpace in a PDCCH-Config that has searchSpaceType=common, and / or vi) USS set configured by SearchSpace in PDCCH-Config with searchSpaceType=ue-Specific Any of the above is acceptable. 【0073】 Furthermore, the UE may not expect any BWP or cell in which a PUCCH resource / transmit is configured to be notified, configured, or applied to XDD operation. Alternatively, the UE may not expect any BWP or cell in FR2-2 to be notified or configured as UL (or DL) or notified or configured for XDD operation. Alternatively, the UE may not expect any BWP or cell in which an SCS (Subcarrier Spacing) value greater than a certain value (e.g., SCS values ​​of 60, 120, 480, or 960 kHz) is configured to be notified or configured to XDD operation. 【0074】 In light of these assumptions, in the first embodiment, if one or more of the following conditions are met, the BWP or cell may be notified of or set to perform an XDD operation. 【0075】 Specifically, XDD operation may be notified to or configured in the BWP as follows: For example, a time unit on the BWP may be notified to or configured as UL (or DL) on some frequency resources, or notified to or configured for UL transmission (or DL ​​reception), while on other frequency resources it may be notified to or configured as DL (or UL), or notified to or configured for DL ​​reception (or UL transmission). The time unit here may be a symbol, slot, subslot, or a group of symbols, slots, or subslots. In other words, XDD operation may be notified to or configured in the BWP on a frequency resource basis for a given time unit. 【0076】 As another example, a certain time unit on the BWP may be notified or configured as a UL (or DL) for some UEs, or notified or configured for UL transmission (or DL ​​reception), while for other UEs, it may be notified or configured as a DL (or UL) or notified or configured for DL ​​reception (or UL transmission). In other words, XDD operations may be notified or configured on a per-UE basis for a given time unit on the BWP. 【0077】 As another example, a time unit on the BWP may be advertised or configured as UL (or DL) on some frequency resources, or advertised or configured for UL transmission (or DL ​​reception), and such some frequency resources may be advertised or configured as unavailable for UL (or DL) by a new slot format configuration / notification or a new rate match pattern configuration / notification. That is, XDD operation may be advertised or configured on the BWP for a certain time unit using a new slot format configuration / notification or a new rate match pattern configuration / notification. 【0078】 Furthermore, XDD operations may be notified to or configured on a cell as follows: For example, an XDD operation may be notified to or configured on any of the cells or on the active BWP. As another example, multiple BWPs for XDD operations may be notified to or configured on the cell. 【0079】 In this way, according to the first embodiment, the UE may receive a notification or setting regarding XDD operation for a radio resource and control uplink transmission or downlink reception on the radio resource in accordance with the notification or setting regarding XDD operation. Correspondingly, the base station may transmit a notification or setting regarding XDD operation for a radio resource and control uplink transmission or downlink reception on the radio resource in accordance with the notification or setting regarding XDD operation. 【0080】 Specifically, the UE may receive notifications or settings regarding XDD operations per frequency resource per unit of time on the BWP. In response, the base station may transmit notifications or settings regarding XDD operations per frequency resource per unit of time on the BWP. Here, such notifications or settings regarding XDD operations per frequency resource may notify or set some of the frequency resources of the BWP for uplink transmission or downlink reception, and other frequency resources of the BWP for downlink reception or uplink transmission. Furthermore, some of the frequency resources may be notified or set as available or unavailable for uplink transmission or downlink reception by slot format settings or notifications, or by rate match pattern settings or notifications. 【0081】 Furthermore, the UE may receive notifications or settings regarding terminal-specific XDD operations for time units on the BWP. In response, the base station may transmit notifications or settings regarding terminal-specific XDD operations for time units on the BWP. Here, such notifications or settings regarding terminal-specific XDD operations may be notified or set to one terminal for uplink transmission or downlink reception of the time unit, and notified or set to another terminal for downlink reception or uplink transmission of the time unit. 【0082】 The UE may also receive a notification or configuration indicating the BWP of the cell in which XDD operation is configured, or the BWP for the cell's XDD operation. In response, the base station may transmit a notification or configuration indicating the BWP of the cell in which XDD operation is configured, or the BWP for the cell's XDD operation. 【0083】 The above-mentioned settings or notifications may be transmitted, for example, as at least one of the following: RRC (Radio Resource Control) information element, DCI (Downlink Control Information), and MAC CE (Medium Access Control Control Element). 【0084】 Furthermore, in order to realize the XDD operation described above, the UE may transmit UE capability information regarding the XDD operation to the base station, and the base station may notify or set the XDD operation to the UE based on the received UE capability information. Specifically, UE capability information regarding whether the Pcell / PScell ​​supports the XDD operation is defined, and the UE may transmit UE capability information regarding whether the Pcell / PScell ​​supports the XDD operation to the base station. 【0085】 Furthermore, UE capability information regarding whether it supports XDD operations applied to cells in a primary / secondary cell group is defined, and the UE may transmit this UE capability information to the base station. 【0086】 Furthermore, UE capability information is defined regarding whether it supports XDD operations applied to the cell / BWP in which the SS set (of a specific SS set type) is configured, and the UE may transmit this UE capability information to the base station. 【0087】 Furthermore, UE capability information is defined regarding whether it supports the XDD operation applied to the cell / BWP in which the PUCCH resource / transmit is configured, and the UE may transmit this UE capability information to the base station. 【0088】 Furthermore, UE capability information regarding whether it supports XDD operation applied to cells / BWPs in FR2-2 is defined, and the UE may transmit this UE capability information to the base station. 【0089】 Furthermore, UE capability information is defined regarding whether it supports XDD operations applied to cells / BWPs with an SCS greater than a certain value, and the UE may transmit this UE capability information to the base station. 【0090】 According to the first embodiment, it becomes possible to limit the cells or time resources on which XDD operation can be configured. 【0091】 (Second example) Currently, there is no discussion regarding search space (SS) sets and / or CORESET configurations when XDD operations are notified, configured, or applied to a BWP or cell where PDCCH monitoring is configured. Therefore, it is necessary to define the UE operations for SS sets and / or CORESET configurations when XDD operations are notified, configured, or applied to a BWP or cell where PDCCH monitoring is configured. In the second embodiment, if XDD operations are configurable for a PDCCH monitoring resource, the UE may perform PDCCH monitoring as described below. 【0092】 In Option 1 of the second embodiment, existing configurations may be used for the SS set configuration or CORESET configuration when it is possible to notify, configure, or apply XDD operations to BWPs or cells on which PDCCH monitoring is configured. In other words, even when it is possible to notify, configure, or apply XDD operations to BWPs or cells on which PDCCH monitoring is configured, no enhancements may be made to the SS set configuration or CORESET configuration. 【0093】 On the other hand, even if the SS set configuration or CORESET configuration is not extended in this way, it should be noted that when XDD operation is notified, configured, or applied to a BWP or cell on which PDCCH monitoring is set, the PDCCH monitoring operation by the UE needs to be extended as described later in relation to the third embodiment. 【0094】 In Option 2 of the second embodiment, separate SS set configurations may be set for pure time units and XDD time units. That is, search space sets may be set for normal TDD operation and XDD operation, respectively. Here, the time unit may be at the symbol level, the slot / subslot level, or a group of symbols / slots / subslots. The XDD time unit may be an XDD symbol, a slot / subslot containing or overlapping an XDD symbol, or a group of symbols / slots / subslots containing or overlapping an XDD symbol. The pure time unit may be a non-XDD symbol, i.e., a symbol that is not an XDD symbol, or a group of slots / subslots or symbols / slots / subslots that do not contain or overlap XDD symbols. 【0095】 For example, searchSpacesToAddModList may be used for pure time-based SS set configuration (which may also be called a non-XDD SS set), and new information elements (IEs) such as searchSpacesToAddModListForXDD may be used for XDD time-based SS set configuration (which may also be called an XDD SS set). 【0096】 When searchSpacesToAddModList is used for SS set configuration in pure time units, the maximum number N of SS sets that can be set for pure time units in PDCCH-Config may be equal to a predetermined number such as 10 (e.g., N=10), or it may be a number less than or greater than a predetermined number such as 10 (e.g., N<10 or N>10). 【0097】 Furthermore, when a new IE such as searchSpacesToAddModListForXDD is used for SS set configuration in XDD time units, the maximum number M of SS sets that can be set for XDD time units in PDCCH-Config may be equal to a predetermined number such as 10 (e.g., M=10), or it may be a number less than or greater than a predetermined number such as 10 (e.g., M<10 or M>10). Also, M may be equal to (10-N) without limitation. 【0098】 For example, as shown in Figure 9, two IEs, searchSpacesToAddModList and searchSpacesToAddModListForXDD, may be set in PDCCH-Config. Similarly, two IEs, searchSpacesToReleaseList and searchSpacesToReleaseListForXDD, may also be set. 【0099】 For each SS set, the UE may determine the PDCCH monitoring opportunity, similar to Rel-15 / 16. 【0100】 Furthermore, regarding PDCCH monitoring opportunities in non-XDD SS sets, as an example, the UE does not need to assume that any PDCCH monitoring opportunity in a non-XDD SS set is included in or overlaps with an XDD time unit or XDD symbol. Alternatively, as another example, if PDCCH monitoring opportunities in an XDD SS set are included in or overlap with an XDD time unit or XDD symbol, the UE may choose not to monitor PDCCH candidates in the PDCCH monitoring opportunities included in or overlapping with the XDD time unit or XDD symbol. On the other hand, if PDCCH monitoring opportunities in an XDD SS set are not included in or overlap with an XDD time unit or XDD symbol, the UE may monitor PDCCH candidates in the PDCCH monitoring opportunities in a manner similar to Rel-15 / 16. 【0101】 On the other hand, regarding PDCCH monitoring opportunities in an XDD SS set, as an example, the UE does not have to assume that any PDCCH monitoring opportunity in the XDD SS set is included in or overlaps with a pure time unit. Alternatively, as another example, if a PDCCH monitoring opportunity is included in or overlaps with a pure time unit or a non-XDD symbol, the UE may choose not to monitor PDCCH candidates in the PDCCH monitoring opportunity that is included in or overlaps with the pure time unit or a non-XDD symbol. On the other hand, if a PDCCH monitoring opportunity is not included in or overlaps with a pure time unit or a non-XDD symbol, the UE may monitor PDCCH candidates in the PDCCH monitoring opportunity. 【0102】 According to the PDCCH monitoring opportunities for the non-XDD SS set and XDD SS set described above, in the example of pure time unit and XDD time unit configuration shown in Figure 10, the UE monitors PDCCH candidates according to non-XDD SS set #0 in the pure time unit and according to XDD SS set #1 in the XDD time unit. Specifically, the UE monitors PDCCH candidates in slots 0, 2, 4, 6, 8, 10, 12, 17, and 18. 【0103】 As one variation, the XDD SS set may be set only for a specific SS type. For example, the specific SS type may be Type0-PDCCH CSS set, Type0A-PDCCH CSS set, Type1-PDCCH CSS set, Type2-PDCCH CSS set, Type3-PDCCH CSS set, and / or USS set. 【0104】 Alternatively, in another variation, the XDD SS set may be set only for a specific DCI (Downlink Control Information) format. For example, the specific 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_2. 【0105】 As another variation, if there are multiple frequency domain patterns for an XDD time unit, the UE may apply the same SS set configuration to any XDD time unit regardless of the frequency domain pattern. 【0106】 Alternatively, as another variation, if there are multiple frequency domain patterns for an XDD time unit, the UE may apply different SS set configurations to the XDD time units having different frequency domain patterns. For example, up to X additional SS set configurations may be set in PDCCH-Config in addition to the existing searchSpacesToAddModList, where the value of X may be set to be less than or equal to the number of frequency domain patterns for the XDD time unit being set. The value of X may also be defined by the specification or set in the RRC configuration. 【0107】 Furthermore, with respect to PDCCH monitoring opportunities in SS sets where frequency domain pattern type #i is set to XDD time units, the UE does not have to assume that any of the PDCCH monitoring opportunities in SS sets where frequency domain pattern type #i is set to XDD time units are included in or overlap with pure time units or XDD time units having other frequency domain pattern types. Also, if a PDCCH monitoring opportunity in an SS set where frequency domain pattern type #i is set to XDD time units is included in or overlaps with a pure time unit or an XDD time unit having another frequency domain pattern type, the UE may choose not to monitor the PDCCH candidate in the PDCCH monitoring opportunity that is included in or overlaps with the pure time unit or the XDD time unit having another frequency domain pattern type. 【0108】 For example, if two additional SS set configurations are set, four IEs may be set in PDCCH-Config, as shown in Figure 11: searchSpacesToAddModListForXdd1,searchSpacesToReleaseListForXdd1 and searchSpacesToAddModListForXdd2,searchSpacesToReleaseListForXdd2. 【0109】 According to the PDCCH monitoring opportunities for the non-XDD SS set and XDD SS set described above, in the example arrangement of pure time units and XDD time units shown in Figure 12, the UE monitors PDCCH candidates according to the SS set #0 of the pure time unit for the pure time unit, according to the XDD SS set #1 of the frequency domain pattern type 1 for the XDD time unit of frequency domain pattern type 1, and according to the XDD SS set #2 of the frequency domain pattern type 2 for the XDD time unit of frequency domain pattern type 2. Specifically, the UE monitors PDCCH candidates in slots 0, 2, 4, 6, 8, 12, 13, 14, and 18. 【0110】 In option 3 of the second embodiment, multiple controlResourceSetIds may be set for the SS set configuration. That is, it is possible to set multiple CORESETs. Here, controlResourceSetId is an IE for identifying the CORESET. 【0111】 As option 3-1, separate CORESET associations may be applied to the pure time unit and the XDD time unit. That is, a CORESET may be set for both 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. 【0112】 For each monitoring start position in an SS set, if the monitoring start position is included in or overlaps with a pure time unit, an existing controlResourceSetId may be used to determine the corresponding PDCCH monitoring opportunity and PDCCH candidate. On the other hand, if the monitoring start position is included in or overlaps with an XDD time unit, a new controlResourceSetIdForXdd may be used to determine the corresponding PDCCH monitoring opportunity and PDCCH candidate. 【0113】 For example, two IEs, controlResourceSetId for pure time units and controlResourceSetIdForXdd for XDD time units, may be configured in the SearchSpace configuration as shown in Figure 13A. 【0114】 Furthermore, as shown in Figure 13B, the UE may determine PDCCH monitoring opportunities and PDCCH candidates according to controlResourceSetId in pure time units, and according to controlResourceSetIdForXdd in XDD time units. 【0115】 As a variation of Option 3-1, there may be multiple frequency-domain patterns for an XDD time unit. For example, if there are multiple frequency-domain patterns for an XDD time unit, a single controlResourceSetIdForXdd may be used for any XDD time unit, regardless of the frequency-domain pattern. 【0116】 Alternatively, as another example, different CORESET associations may be applied to different XDD time units having different frequency domain patterns. For example, up to X additional CORESET associations may be set, where the value of X may be set to be less than or equal to the number of frequency domain patterns for the XDD time units being set. The value of X may also be defined by the specification or set in the RRC configuration. 【0117】 For example, the IEs of controlResourceSetIdForXdd-1, controlResourceSetIdForXdd-2, and controlResourceSetIdForXdd-3 for three additional frequency domain patterns may be set in the SearchSpace configuration as shown in Figure 14A. 【0118】 Furthermore, as shown in Figure 14B, the UE may determine PDCCH monitoring opportunities and PDCCH candidates according to controlResourceSetId in pure time units, PDCCH monitoring opportunities and PDCCH candidates according to controlResourceSetIdForXdd-1 in XDD time units based on frequency domain pattern type 1, and PDCCH monitoring opportunities and PDCCH candidates according to controlResourceSetIdForXdd-2 in XDD time units based on frequency domain pattern type 2. 【0119】 In addition, option 3-2 allows the UE to determine PDCCH monitoring opportunities and PDCCH candidates for each monitoring start position in the SS set by iterating through a list of controlResourceSetIds until a suitable controlResourceSetId is selected or until all controlResourceSetIds have been tried. In other words, the UE selects the appropriate one from multiple CORESETs depending on the SS configuration. 【0120】 For example, regarding the monitoring start position of an SS set, the UE may first use a first CORESET ID to determine the PDCCH monitoring opportunities and PDCCH candidates for the SS set. If none of the determined PDCCH candidates overlap with time and frequency domain resources that are notified or set as ULs or notified or set for UL transmissions, the UE may decide to use that CORESET and monitor the determined PDCCH candidates. 【0121】 If any of the determined PDCCH candidates overlap with time and frequency domain resources that are notified or configured as ULs or notified or configured for UL transmission, the UE may determine the PDCCH monitoring opportunity and PDCCH candidates by using the next configured CORESET ID until a CORESET ID is detected that acquires a PDCCH candidate that does not overlap with time and frequency domain resources that are notified or configured as ULs or notified or configured for UL transmission. 【0122】 If the UE has tried all CORESET IDs set in the SS set but has not found a CORESET ID from which a PDCCH candidate is obtained that does not overlap with time and frequency domain resources that are notified or set as UL or notified or set for UL transmission, the default CORESET, the first CORESET, or the last CORESET may be used to determine the PDCCH candidate. Alternatively, the UE may choose not to assume such a case. Alternatively, the UE may choose not to monitor PDCCH candidates at the monitoring start position of the SS set. 【0123】 For example, an IE of controlResoruceSetAddForXdd to specify the trial order of multiple controlResoruceSetIds may be set in the SearchSpace configuration, as shown in Figure 15. 【0124】 In the example shown in Figure 16, the UE tries each CORESET ID in the order of controlResourceSetId, controlResourceSetId-2, controlResourceSetId-3, and controlResourceSetId-4 to determine if each CORESET ID contains a PDCCH candidate that does not overlap with time and frequency domain resources that are notified or configured as ULs or notified or configured for UL transmission. 【0125】 In the illustrated example, for PDCCH monitoring start position #0, controlResourceSetId-3 is determined to be a CORESET containing PDCCH candidates that do not overlap with time and frequency domain resources that are notified or set as ULs or notified or set for UL transmission, and the UE may use controlResourceSetId-3 to determine PDCCH monitoring opportunities and PDCCH candidates. 【0126】 Furthermore, for PDCCH monitoring start position #1, if controlResourceSetId is determined to be a CORESET containing PDCCH candidates that do not overlap with time and frequency domain resources that are notified or set as ULs or notified or set for UL transmission, the UE may use controlResourceSetId to determine PDCCH monitoring opportunities and PDCCH candidates. 【0127】 In option 4 of the second embodiment, multiple frequencyDomainResources may be set for the CORESET configuration. Multiple frequency domain patterns are set for the CORESET, where frequencyDomainResources are IEs that specify frequency domain resources for the CORESET. 【0128】 As an option 4-1, separate frequencyDomainResources configurations may be applied to the pure time unit and the XDD time unit. That is, frequency domain patterns are set according to normal TDD operation and XDD operation. For example, in addition to the existing frequencyDomainResources, a new frequencyDomainResourcesForXdd may be set for the CORESET. For each PDCCH monitoring opportunity in the SS set for the CORESET, if the PDCCH monitoring opportunity is not included in or does not overlap with the XDD time unit or XDD symbol, the existing frequencyDomainResources may be used to determine the corresponding PDCCH candidate. On the other hand, if the PDCCH monitoring opportunity is included in or overlaps with the XDD time unit or XDD symbol, the new frequencyDomainResourcesForXdd may be used to determine the corresponding PDCCH candidate. 【0129】 For example, two IEs, frequencyDomainResources for pure time units and frequencyDomainResourcesForXdd for XDD time units, may be configured in the ControlResourceSet configuration as shown in Figure 17A. 【0130】 In the example shown in Figure 17B, the UE may monitor PDCCH candidates determined based on frequencyDomainResources in pure time units, and PDCCH candidates determined based on frequencyDomainResourcesForXdd in XDD time units. 【0131】 As a variation of Option 4-1, there may be multiple frequency-domain patterns for an XDD time unit. For example, if there are multiple frequency-domain patterns for an XDD time unit, a single frequencyDomainResourcesForXdd may be used for any XDD time unit, regardless of the frequency-domain pattern. 【0132】 Alternatively, as another example, different frequencyDomainResourcesForXdd configurations may be applied to different XDD time units having different frequency domain patterns. For example, up to X additional frequencyDomainResourcesForXdd configurations may be set, where the value of X may be set to be less than or equal to the number of frequency domain patterns for the XDD time unit being set. The value of X may also be defined by the specification or set in the RRC configuration. 【0133】 For example, the IEs for frequencyDomainResourcesForXdd-1, frequencyDomainResourcesForXdd-2, and frequencyDomainResourcesForXdd-3 for three additional frequency domain patterns may be set in the ControlResourceSet configuration, as shown in Figure 18A. 【0134】 Furthermore, as shown in Figure 18B, the UE may determine PDCCH candidates according to frequencyDomainResources in pure time units, PDCCH candidates according to frequencyDomainResourcesForXdd-1 in XDD time units using frequency domain pattern type 1, and PDCCH candidates according to frequencyDomainResourcesForXdd-2 in XDD time units using frequency domain pattern type 2. 【0135】 As an option 4-2, for each PDCCH monitoring opportunity in an SS set for a CORESET, the UE may determine the PDCCH candidate by iterating through a list of frequencyDomainResources until a suitable frequencyDomainResource is selected or until all frequencyDomainResources have been tried. In other words, the UE may select the most suitable one from multiple CORESETs depending on the SS set. 【0136】 For example, for each PDCCH monitoring opportunity in an SS set for a CORESET, the UE may first determine a PDCCH candidate by utilizing first frequencyDomainResources. If none of the determined PDCCH candidates overlap with time and frequency domain resources that are advertised or set as ULs or advertised or set for UL transmissions, the UE may decide to use those frequencyDomainResources and monitor the determined PDCCH candidates. 【0137】 If any of the determined PDCCH candidates overlap with time and frequency domain resources that are notified or configured as ULs or notified or configured for UL transmission, the UE may determine the PDCCH candidate by using the next set frequencyDomainResources until a frequencyDomainResources is found that acquires a PDCCH candidate that does not overlap with time and frequency domain resources that are notified or configured as ULs or notified or configured for UL transmission. 【0138】 If the UE has tried all frequencyDomainResources but has not found any frequencyDomainResources from which a PDCCH candidate is obtained that does not overlap with time and frequency domain resources that are advertised or set as UL or advertised or set for UL transmission, the default frequencyDomainResources, the first frequencyDomainResources, or the last frequencyDomainResources may be used to determine the PDCCH candidate. Alternatively, the UE may choose not to assume such a case. Alternatively, the UE may choose not to monitor PDCCH candidates during a PDCCH monitoring opportunity. 【0139】 For example, an IE of frequencyDomainResourcesAddForXdd to specify the trial order of multiple frequencyDomainResources may be set in the ControlResourceSet configuration, as shown in Figure 19. 【0140】 In the example shown in Figure 20, the UE tries each frequencyDomainResources in the order of frequencyDomainResources, frequencyDomainResources-2, and frequencyDomainResources-3 to determine if each frequencyDomainResources contains a PDCCH candidate that does not overlap with time and frequency domain resources that are advertised or set as UL or advertised or set for UL transmission. 【0141】 In the illustrated example, for PDCCH monitoring opportunity #0, frequencyDomainResources-3 is determined to be frequencyDomainResources containing PDCCH candidates that do not overlap with time and frequency domain resources that are advertised or set as UL or advertised or set for UL transmission, and the UE may use frequencyDomainResources-3 to determine PDCCH candidates. 【0142】 Furthermore, for PDCCH monitoring opportunity #1, if frequencyDomainResources is determined to be frequencyDomainResources that include PDCCH candidates that do not overlap with time and frequency domain resources that are notified or set as UL or notified or set for UL transmission, the UE may use frequencyDomainResources to determine PDCCH candidates. 【0143】 As option 5 of the second embodiment, multiple bitmaps of freqMonitorLocations may be set for the SS set configuration. That is, multiple bitmaps of freqMonitorLocations are set for the SS set, where freqMonitorLocations are IEs indicating frequency monitoring locations. 【0144】 As option 5-1 of the second embodiment, separate freqMonitorLocations bitmaps may be set for pure time units and XDD time units. That is, frequency domain patterns are selected depending on whether it is normal TDD operation or XDD operation. For example, in addition to the existing freqMonitorLocations bitmap, a new freqMonitorLocationsForXdd may be set for the SS set configuration. For each PDCCH monitoring opportunity in the SS set, if the PDCCH monitoring opportunity is not included in or does not overlap with an XDD time unit or XDD symbol, the existing freqMonitorLocations may be used to determine the corresponding PDCCH candidate. On the other hand, if the PDCCH monitoring opportunity is included in or overlaps with an XDD time unit or XDD symbol, the new freqMonitorLocationsForXdd may be used to determine the corresponding PDCCH candidate. 【0145】 For example, two IEs, freqMonitorLocations for pure time units and freqMonitorLocationsForXdd for XDD time units, may be configured in the SearchSpaceExt configuration, as shown in Figure 21A. 【0146】 In the example shown in Figure 21B, the UE may monitor PDCCH candidates determined based on freqMonitorLocations in pure time units, and PDCCH candidates determined based on freqMonitorLocationsForXdd in XDD time units. 【0147】 As a variation of option 5-1 of the second embodiment, there may be multiple frequency domain patterns for an XDD time unit. For example, if there are multiple frequency domain patterns for an XDD time unit, a single freqMonitorLocationsForXdd bitmap may be used for any XDD time unit regardless of the frequency domain pattern. 【0148】 Alternatively, as another example, different freqMonitorLocationsForXdd bitmaps may be applied to different XDD time units having different frequency domain patterns. For example, up to X additional freqMonitorLocationsForXdd bitmaps may be set, where the value of X may be set to be less than or equal to the number of frequency domain patterns for the XDD time units being set. The value of X may also be defined by the specification or set in the RRC configuration. 【0149】 For example, the IEs for freqMonitorLocationsForXdd-1, freqMonitorLocationsForXdd-2, and freqMonitorLocationsForXdd-3 for three additional frequency domain patterns may be set in the SearchSpaceExt configuration as shown in Figure 22A. 【0150】 Furthermore, as shown in Figure 22B, the UE may monitor PDCCH candidates determined based on freqMonitorLocations in pure time units, PDCCH candidates determined based on freqMonitorLocationsForXdd-1 in XDD time units by frequency domain pattern type 1, and PDCCH candidates determined based on freqMonitorLocationsForXdd-2 in XDD time units by frequency domain pattern type 2. 【0151】 As option 5-2 of the second embodiment, for each PDCCH monitoring opportunity in the SS set, the UE may determine the PDCCH candidate by iterating through a list of freqMonitorLocations until a suitable freqMonitorLocation is selected or until all freqMonitorLocations have been tried. That is, the UE selects a suitable one from a set of bitmaps depending on the SS set. 【0152】 For example, for each PDCCH monitoring opportunity in an SS set, the UE may first determine the PDCCH candidates for the SS set by utilizing the bitmap of the first freqMonitorLocations. If none of the determined PDCCH candidates overlap with time and frequency domain resources that are advertised or set as ULs or advertised or set for UL transmissions, the UE may decide to use those freqMonitorLocations and monitor the determined PDCCH candidates. 【0153】 If any of the determined PDCCH candidates overlap with time and frequency domain resources that are notified or configured as ULs or notified or configured for UL transmission, the UE may determine the PDCCH candidate by using the next set freqMonitorLocations until a freqMonitorLocations is found that acquires a PDCCH candidate that does not overlap with time and frequency domain resources that are notified or configured as ULs or notified or configured for UL transmission. 【0154】 If the UE has tried all the freqMonitorLocations bitmaps set for the SS set but has not found a freqMonitorLocations bitmap that retrieves a PDCCH candidate that does not overlap with time and frequency domain resources that are advertised or set as UL or advertised or set for UL transmission, then the default freqMonitorLocations, the first freqMonitorLocations, or the last freqMonitorLocations may be used to determine the PDCCH candidate. Alternatively, the UE may choose not to assume such a case. Alternatively, the UE may choose not to monitor PDCCH candidates in a PDCCH monitoring opportunity. 【0155】 For example, an IE for freqMonitorLocationsAddForXdd to specify the trial order of multiple freqMonitorLocations may be set in the SearchSpaceExt configuration, as shown in Figure 23. 【0156】 In the example shown in Figure 24, the UE tries each freqMonitorLocations in the order of freqMonitorLocations, freqMonitorLocations-2, and freqMonitorLocations-3 to determine if each freqMonitorLocations contains a PDCCH candidate that does not overlap with time and frequency domain resources that are advertised or set as ULs or advertised or set for UL transmission. 【0157】 In the illustrated example, for PDCCH monitoring opportunity #0, freqMonitorLocations-3 is determined to be a set of freqMonitorLocations containing PDCCH candidates that do not overlap with time and frequency domain resources that are advertised or set as ULs or advertised or set for UL transmissions, and the UE may use freqMonitorLocations-3 to determine the PDCCH candidates. 【0158】 Furthermore, with respect to PDCCH monitoring opportunity #1, if freqMonitorLocations is determined to contain PDCCH candidates that do not overlap with time and frequency domain resources that are notified or set as ULs or notified or set for UL transmission, the UE may use freqMonitorLocations to determine the PDCCH candidates. 【0159】 As option 6 of the second embodiment, different interpretations of the SS set and / or CORESET configuration parameters may be applied to pure time units and XDD time units when determining the PDCCH candidate. That is, the interpretation of the PDCCH monitoring settings is switched depending on whether it is normal TDD operation or XDD operation. 【0160】 For example, for PDCCH monitoring opportunities that are not included in or overlap with XDD time units, or that do not overlap with XDD symbols, the freqMonitorLocations in the SS set configuration and / or frequencyDomainResources in the CORESET configuration may be interpreted based on the pure time unit frequency resource configuration, i.e., in the same way as the interpretation of Rel-15 / 16 / 17. 【0161】 For PDCCH monitoring opportunities that are included in or overlap with XDD time units, or that overlap with XDD symbols, the freqMonitorLocations in the SS set configuration and / or frequencyDomainResources in the CORESET configuration may be interpreted based on the frequency domain resources of the overlapping XDD time units or XDD symbols. For example, for PDCCH monitoring opportunities that are included in or overlap with XDD time units, or that overlap with XDD symbols, the freqMonitorLocations in the SS set configuration and / or frequencyDomainResources in the CORESET configuration may be reinterpreted as freqMonitorLocationsForXdd and / or frequencyDomainResourcesAddForXdd. 【0162】 As a variation of the second embodiment, different options may be applied to different SS set types. For example, the SS set types may be Type0-PDCCH CSS set, Type0A-PDCCH CSS set, Type1-PDCCH CSS set, Type2-PDCCH CSS set, Type3-PDCCH CSS set and / or USS set. 【0163】 Thus, according to the second embodiment, the UE may receive a first PDCCH monitoring setting for non-XDD time units (e.g., pure time units) and a second PDCCH monitoring setting for XDD time units, and control PDCCH monitoring according to the first and second PDCCH monitoring settings. Correspondingly, the base station may set a first PDCCH monitoring setting for non-XDD time units and a second PDCCH monitoring setting for XDD time units, and transmit the first and second PDCCH monitoring settings to the terminal. 【0164】 Specifically, the first PDCCH monitoring setting may be a search space set setting for non-XDD time units (e.g., searchSpaceToAddModList), and the second PDCCH monitoring setting may be one or more search space set settings for XDD time units (e.g., searchSpaceToAddModListForXDD, searchSpaceToAddModListForXDD1, searchSpaceToAddModListForXDD2, etc.). 【0165】 Furthermore, the first PDCCH monitoring setting may be a CORESET setting (e.g., controlResourceSetId) for non-XDD time units, and the second PDCCH monitoring setting may be one or more CORESET settings for XDD time units (e.g., controlResourceSetIdForXdd, controlResourceSetIdForXdd-1, controlResourceSetIdForXdd-2, etc.). 【0166】 Furthermore, the first PDCCH monitoring setting may be a frequency domain resource setting for non-XDD time units (e.g., frequencyDomainResources), and the second PDCCH monitoring setting may be one or more frequency domain resource settings for XDD time units (e.g., frequencyDomainResourcesForXdd, frequencyDomainResourcesForXdd-1, frequencyDomainResourcesForXdd-2, etc.). 【0167】 Furthermore, the first PDCCH monitoring setting may be a frequency monitoring location setting for non-XDD time units (e.g., freqMonitorLocations), and the second PDCCH monitoring setting may be one or more frequency monitoring location settings for XDD time units (e.g., freqMonitorLocationsForXdd, freqMonitorLocationsForXdd-1, freqMonitorLocationsForXdd-2, etc.). 【0168】 Furthermore, the second PDCCH monitoring setting described above may indicate a priority order corresponding to multiple frequency domain patterns. 【0169】 Furthermore, the second PDCCH monitoring setting may be interpreted from the first PDCCH monitoring setting. 【0170】 The settings or notifications described above may be transmitted based, for example, on at least one of the RRC (Radio Resource Control) information element, DCI (Downlink Control Information), and MAC CE (Medium Access Control Control Element). Furthermore, this disclosure is not limited to PDCCH monitoring and may apply to other types of control signals transmitted from a base station to a UE or other base station (e.g., an IAB node). 【0171】 To implement the XDD operation described above, the UE may transmit UE capability information regarding the XDD operation to the base station, and the base station may notify or configure the XDD operation to the UE based on the received UE capability information. Specifically, UE capability information may be defined regarding whether the UE supports separate SS set configurations for XDD time units and pure time units. The UE may transmit UE capability information to the base station regarding whether it supports separate SS set configurations for XDD time units and pure time units. 【0172】 Furthermore, UE capability information regarding whether the UE supports multiple controlResourceSetIds set for an SS set configuration may be specified. The UE may transmit UE capability information regarding whether it supports multiple controlResourceSetIds set for an SS set configuration to the base station. 【0173】 Furthermore, UE capability information regarding whether the UE supports multiple frequencyDomainResources configured for the CORESET configuration may be specified. The UE may transmit UE capability information regarding whether it supports multiple frequencyDomainResources configured for the CORESET configuration to the base station. 【0174】 Furthermore, UE capability information may be specified regarding whether the UE supports multiple freqMonitorLocations bitmaps configured for the SS set configuration. The UE may transmit UE capability information regarding whether it supports multiple freqMonitorLocations bitmaps configured for the SS set configuration to the base station. 【0175】 According to the second embodiment, when an XDD operation is notified, configured, or applied to a cell where PDCCH monitoring is configured, UE operations relating to SS sets and / or CORESET configurations can be defined. 【0176】 (Third embodiment) There is currently no discussion regarding the behavior of PDCCH monitoring when XDD operations are notified, configured, or applied to cells where PDCCH monitoring is configured. Therefore, it is necessary to define the behavior of PDCCH monitoring when XDD operations are notified, configured, or applied to cells where PDCCH monitoring is configured. In other words, the UE may perform the following actions in response to PDCCH monitoring. 【0177】 Please note that the third embodiment is independent of the second embodiment. That is, any option in the third embodiment may be applied together with any option in the second embodiment. 【0178】 As option 1 of the third embodiment, the UE may assume that the PDCCH monitoring opportunities for the PDCCH SS set do not overlap with the XDD symbols. That is, the UE may assume that the PDCCH monitoring does not overlap with the XDD symbols. In this case, for example, in the example shown in Figure 25, the first PDCCH monitoring opportunities in the slot (symbols #0, #1) overlap with the XDD symbols and result in an error case. 【0179】 As option 2 of the third embodiment, the UE may assume that the PDCCH monitoring opportunities for the PDCCH SS set are not included in or overlap with the XDD time units. That is, the UE may assume that PDCCH monitoring does not overlap with the XDD time units. In this case, for example, in the example shown in Figure 26, the time units are slots, and the PDCCH monitoring opportunities are included in the XDD slots, which is an error case. 【0180】 As option 3 of the third embodiment, consider the case where the PDCCH monitoring opportunities for the PDCCH SS set are included in or overlap with the XDD time unit. That is, if PDCCH monitoring overlaps with the XDD resource, the UE may perform the following actions: 【0181】 As option 3-1 of the third embodiment, if the PDCCH monitoring opportunities for the PDCCH SS set are included in or overlap with the XDD time unit, the UE may choose not to monitor the PDCCH candidate in the PDCCH monitoring opportunity, regardless of whether the PDCCH monitoring opportunity overlaps with the XDD symbol. In other words, the UE avoids PDCCH monitoring. 【0182】 For example, in the example shown in Figure 27, since slot A is an XDD slot, the UE may choose not to monitor PDCCH candidates in slot A. On the other hand, since slot B is a pure DL slot, the UE may choose to monitor PDCCH candidates in slot B. 【0183】 As option 3-2 of the third embodiment, if the PDCCH monitoring opportunities of the PDCCH SS set are included in or overlap with XDD time units, the UE decides whether or not to monitor PDCCH candidates in the PDCCH monitoring opportunities based on whether or not the PDCCH monitoring opportunities overlap with XDD symbols. In other words, the UE may decide whether or not to perform monitoring depending on whether or not XDD resources can be duplicated. If the PDCCH monitoring opportunities of the PDCCH SS set overlap with XDD symbols, the UE does not have to 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 XDD symbols, the UE may monitor PDCCH candidates in the PDCCH monitoring opportunities. 【0184】 For example, in the example shown in Figure 28, the PDCCH monitoring opportunities in slot A (symbols #0, #1, #4, #5) do not overlap with the XDD symbols, so the UE may monitor PDCCH candidates in the PDCCH monitoring opportunities in slot A (symbols #0, #1, #4, #5). On the other hand, the first PDCCH monitoring opportunity in slot B (symbols #0, #1) overlaps with the XDD symbols, so the UE may choose not to monitor PDCCH candidates in the first PDCCH monitoring opportunity in slot B (symbols #0, #1). The second PDCCH monitoring opportunity in slot B (symbols #4, #5) does not overlap with the XDD symbols, so the UE may monitor PDCCH candidates in the second PDCCH monitoring opportunity in slot B (symbols #4, #5). 【0185】 As option 3-3 of the third embodiment, if the PDCCH monitoring opportunities for a PDCCH SS set are included in or overlap with XDD time units, the UE may decide whether to monitor the PDCCH candidate in the PDCCH monitoring opportunity that overlaps with the XDD symbol, based on whether the PDCCH candidate overlaps with time and frequency domain resources that are notified or set as UL or notified or set for UL transmission. In other words, the UE may make a decision depending on whether a UL is set for the XDD resource. 【0186】 As option 3-3A of the third embodiment, if the PDCCH monitoring opportunities for the PDCCH SS set are included in or overlap with XDD time units, the UE may assume that none of the PDCCH candidates in the PDCCH monitoring opportunities for the PDCCH SS set overlap with time and frequency domain resources that are notified or set as ULs or notified or set for UL transmission. That is, the UE may monitor the PDCCH candidates in the PDCCH monitoring opportunities, similar to Rel-15 / 16. 【0187】 For example, in the example shown in Figure 29, the first PDCCH monitoring opportunity (symbols #0, #1) overlaps with time and frequency domain resources set as UL, resulting in an error case. 【0188】 As option 3-3B of the third embodiment, if the PDCCH monitoring opportunities for the PDCCH SS set are included in or overlap with XDD time units, the UE may monitor the PDCCH candidate in the PDCCH monitoring opportunities for the PDCCH SS set if the PDCCH candidate does not overlap with the time and frequency domain resources that the PDCCH candidate is notified or set as a UL or notified or set for UL transmission. On the other hand, if the PDCCH candidate overlaps with the time and frequency domain resources that the PDCCH candidate is notified or set as a UL or notified or set for UL transmission, the UE may choose not to monitor the PDCCH candidate. 【0189】 For example, in the example shown in Figure 30, the first PDCCH monitoring opportunity (symbols #0, #1) overlaps with the time and frequency domain resources set as ULs, so the UE may choose not to monitor the PDCCH candidates during the first PDCCH monitoring opportunity. On the other hand, the second PDCCH monitoring opportunity (symbols #4, #5) does not overlap with the time and frequency domain resources set as ULs, so the UE may choose to monitor the PDCCH candidates during the second PDCCH monitoring opportunity. 【0190】 As a variation of the third embodiment, for each option of the third embodiment, the PDCCH SS set may be limited to a specific SS type. For example, the specific SS type may be: i) Type0-PDCCH CSS set configured by pdcch-ConfigSIB1 in MIB, searchSpaceSIB1 in PDCCH-ConfigCommon, and searchSpaceZero in PDCCH-ConfigCommon. ii) The Type0A-PDCCH CSS set configured by searchSpaceOtherSystemInformation in PDCCH-ConfigCommon. iii) Type1-PDCCH CSS set configured by ra-SearchSpace in PDCCH-ConfigCommon iv) Type2-PDCCH CSS set configured by pagingSearchSpace in PDCCH-ConfigCommon v) A Type3-PDCCH CSS set and / or set by SearchSpace in a PDCCH-Config that has searchSpaceType=common vi) USS set configured by SearchSpace in PDCCH-Config with searchSpaceType=ue-Specific Any of the above is acceptable. 【0191】 Furthermore, different options may apply to different PDCCH SS set types. For example, options 1 and 2 may apply to Type0-PDCCH CSS sets, while option 3 may apply to USS sets. 【0192】 As another variation of the third embodiment, for each option of the third embodiment, the PDCCH SS set may be limited to an SS set in which a specific DCI format is set. For example, the SS set may be a USS set in which dci-Formats=formats0-0-And-1-0 or formats0-1-And-1-1, dci-Formats-MT-r16=formats2-5, dci-FormatsExt-r16=formats0-0-And-1-0, formats0-1-And-1-1, formats3-0, formats3-1 or formats3-0-And-3-1, and / or dci-FormatsExt-r16=formats0-2-And-1-2, formats0-1-And-1-1 or formats0-2-And-1-2 is set. 【0193】 Furthermore, different options may be applied to PDCCH SS sets where different DCI formats are configured. 【0194】 Thus, according to the third embodiment, the UE may receive the PDCCH search space setting and control PDCCH monitoring based on the PDCCH search space setting in the XDD operation. Correspondingly, the base station may set the PDCCH search space setting in the XDD operation and transmit the PDCCH search space setting. 【0195】 Specifically, the UE may assume that the PDCCH monitoring opportunities indicated by the PDCCH search space settings do not overlap with XDD time units (e.g., XDD symbols, XDD slots, etc.). 【0196】 Furthermore, if a PDCCH monitoring opportunity indicated by the PDCCH search space setting overlaps with an XDD time unit, the UE may avoid PDCCH monitoring during that PDCCH monitoring opportunity. 【0197】 Furthermore, if a PDCCH monitoring opportunity indicated by the PDCCH search space setting overlaps with an XDD time unit (e.g., an XDD slot), the UE may control PDCCH monitoring depending on whether the PDCCH monitoring opportunity overlaps with a first time unit (e.g., an XDD symbol) within that XDD time unit. 【0198】 Furthermore, if a PDCCH monitoring opportunity indicated by the PDCCH search space setting overlaps with an XDD time unit, the UE may control PDCCH monitoring in that PDCCH monitoring opportunity based on whether the PDCCH candidate overlaps with radio resources (i.e., time and frequency resources) for uplink transmission. 【0199】 The above settings or notifications may be transmitted based on, for example, at least one of an RRC (Radio Resource Control) information element, DCI (Downlink Control Information), and MAC CE (Medium Access Control Control Element). Further, the present disclosure is not limited to PDCCH monitoring and may be applied to other types of control signals transmitted from a base station to a UE or another base station (e.g., an IAB node, etc.). 【0200】 To implement the above-described XDD operation, the UE may transmit UE capability information related to the XDD operation to the base station, and the base station may notify or set the XDD operation for the UE based on the received UE capability information. Specifically, UE capability information regarding whether the UE supports a case where a PDCCH monitoring opportunity overlaps with an XDD time unit or an XDD symbol may be defined. The UE may transmit UE capability information regarding whether it supports a case where a PDCCH monitoring opportunity overlaps with an XDD time unit or an XDD symbol to the base station. 【0201】 Also, UE capability information regarding whether the UE supports monitoring PDCCH candidates in a PDCCH monitoring opportunity including or overlapping with an XDD time unit or an XDD symbol may be defined. The UE may transmit UE capability information regarding whether it supports monitoring PDCCH candidates in a PDCCH monitoring opportunity including or overlapping with an XDD time unit or an XDD symbol to the base station. 【0202】 According to the third embodiment, when XDD operation is notified, set, or applied to a cell where PDCCH monitoring is set, UE operations related to PDCCH monitoring can be defined. 【0203】 (Fourth Embodiment) There is currently no discussion on PDCCH monitoring capabilities and BD / CCE constraints when XDD operation is notified, set, or applied to the cell where PDCCH monitoring is configured. Therefore, it is necessary to define UE operations regarding PDCCH monitoring capabilities and BD / CCE constraints when XDD operation is notified, set, or applied to the cell where PDCCH monitoring is configured. 【0204】 In the 4th Embodiment - 1, the PDCCH monitoring capabilities for the XDD SS set or XDD PDCCH monitoring opportunity may be the same as or different from the existing PDCCH monitoring instructions or settings. That is, the PDCCH monitoring capabilities may be set by any of the following methods. 【0205】 As Option 1 of the 4th Embodiment - 1, the capability notification, setting, or specification for PDCCH monitoring on the BWP or cell may be unified. That is, the PDCCH monitoring capabilities common to normal TDD operation and XDD operation may be set. The capability notification, setting, or specification for PDCCH monitoring on the BWP or cell may be based on the configuration by monitoringCapabilityConfig - r16 or monitoringCapabilityConfig - r17. 【0206】 As a variant of Option 1, when the BWP or cell is notified or set for XDD operation, it may be assumed that the PDCCH - Config of the BWP or cell is not notified or set as the PDCCH monitoring capability in Rel - 15 slot units, the PDCCH monitoring capability in Rel - 16 span units, and / or the PDCCH monitoring capability in Rel - 17 multi - slots. 【0207】 For example, if a BWP or cell is notified or configured for XDD operation, the UE does not need to assume that monitoringCapabilityConfig-r16=r15monitoringcapability or monitoringCapabilityConfig-r17=r15monitoringcapability is configured for PDCCH-Config on the BWP or cell. Alternatively, neither monitoringCapabilityConfig-r16 nor monitoringCapabilityConfig-r17 is configured for PDCCH-Config on the BWP or cell. 【0208】 As another example, if a BWP or cell is notified or configured for XDD operation, the UE does not need to assume that monitoringCapabilityConfig-r16=r16monitoringcapability or monitoringCapabilityConfig-r17=r16monitoringcapability is configured for PDCCH-Config on the BWP or cell. 【0209】 As another example, if a BWP or cell is notified or configured for XDD operation, the UE does not need to assume that monitoringCapabilityConfig-r17=r17monitoringcapability is set for PDCCH-Config on the BWP or cell. 【0210】 Here, an XDD SS set means an SS set set for an XDD time unit. A non-XDD SS set means an SS set set for a pure time unit. An XDD PDCCH monitoring opportunity means a PDCCH opportunity that includes or overlaps an XDD time unit or XDD symbol. A non-XDD PDCCH monitoring opportunity means a PDCCH monitoring opportunity that does not include or overlap an XDD time unit or XDD symbol. 【0211】 As option 2 of the fourth embodiment-1, notification, configuration, or provision of separate PDCCH monitoring capabilities for monitoring XDD SS sets and non-XDD SS sets on the BWP or cell may be used, or notification, configuration, or provision of separate PDCCH monitoring capabilities for XDD PDCCH monitoring opportunities and non-XDD PDCCH monitoring opportunities on the BWP or cell. That is, PDCCH monitoring capabilities may be configured for normal TDD operation and XDD operation, respectively. 【0212】 monitoringCapabilityConfig-r16 or monitoringCapabilityConfig-r17 may be reused to notify or configure the PDCCH monitoring capability of Rel-15 / 16 / 17 for non-XDD SS sets or non-XDD PDCCH monitoring opportunities. 【0213】 Additionally, the new RRC parameter monitoringCapabilityConfigForXdd may be reused to notify or configure the PDCCH monitoring capability of Rel-15 / 16 / 17 for monitoring XDD SS sets or XDD PDCCH monitoring opportunities. 【0214】 For example, the candidate values ​​for the new RRC parameter monitoringCapabilityConfigForXdd may be r15monitoringcapability, r16monitoringcapability, and / or r17monitoringcapability. Specifically, monitoringCapabilityConfigForXdd may have the following values: monitoringCapabilityConfigForXdd={r15monitoringcapability,r16monitoringcapability,r17monitoringcapability} monitoringCapabilityConfigForXdd={r15monitoringcapability,r16monitoringcapability} monitoringCapabilityConfigForXdd={r15monitoringcapability,r17monitoringcapability} monitoringCapabilityConfigForXdd={r16monitoringcapability,r17monitoringcapability} 【0215】 Furthermore, if no new RRC parameters are set for monitoring XDD SS sets or XDD PDCCH monitoring opportunities, the UE may perform the following actions: 【0216】 As a first action, if no new RRC parameters are set for monitoring an XDD SS set or XDD PDCCH monitoring opportunity, the UE may follow the same PDCCH monitoring capability as notified or set by monitoringCapabilityConfig-r16 or monitoringCapabilityConfig-r17 for monitoring an XDD SS set or XDD PDCCH monitoring opportunity. 【0217】 As a second action, if no new RRC parameters are set for monitoring an XDD SS set or XDD PDCCH monitoring opportunity, the UE may apply the default PDCCH monitoring capability for monitoring the XDD SS set or XDD PDCCH monitoring opportunity. For example, the default PDCCH monitoring capability may be applied as a slot-based PDCCH monitoring capability in Rel-15, a span-based PDCCH monitoring capability in Rel-16, or a multi-slot PDCCH monitoring capability in Rel-17. 【0218】 As a third behavior, if a specific PDCCH monitoring capability is notified or configured by monitoringCapabilityConfig-r16 or monitoringCapabilityConfig-r17, the default PDCCH monitoring capability for monitoring an XDD SS set or XDD PDCCH monitoring opportunity may always be the slot-based PDCCH monitoring capability of Rel-15, the span-based PDCCH monitoring capability of Rel-16, or the multi-slot PDCCH monitoring capability of Rel-17. Otherwise, the UE may follow the same PDCCH monitoring capability for monitoring an XDD SS set or XDD PDCCH monitoring opportunity as notified or configured by monitoringCapabilityConfig-r16 or monitoringCapabilityConfig-r17. 【0219】 As a variation of Option 2 of Embodiment 4-1, the UE does not assume that a specific PDCCH monitoring capability (e.g., Rel-15 / 16 / 17 monitoring capability) for a non-XDD SS set or non-XDD PDCCH monitoring opportunity is notified by monitoringCapabilityConfig-r16 or monitoringCapabilityConfig-r17, and that a specific PDCCH monitoring capability (e.g., Rel-15 / 16 / 17 monitoring capability) for a non-XDD SS set or non-XDD PDCCH monitoring opportunity is simultaneously configured or defined. 【0220】 In the fourth embodiment-2, the PDCCH candidates or non-overlapping CCEs for monitored XDD SS sets and monitored non-XDD SS sets, or for monitored XDD PDCCH monitoring opportunities and monitored non-XDD PDCCH monitoring opportunities, may be counted separately or together for the maximum number of blind decoding (BD) or control channel element (CCE) limits. That is, the BD / CCE limit may be counted in any of the following ways. The intent of “monitored” here is to include the possibility that PDCCH candidates that are determined not to be monitored (for example, according to the rules of Embodiment 3 and / or Rel-15 / 16) may or may not be counted for the BD or CCE limit. 【0221】 As a first action, the UE may separately count the number of PDCCH candidates or non-overlapping CCEs for the monitored XDD SS set and the monitored non-XDD SS set, or the number of PDCCH candidates or non-overlapping CCEs for the monitored XDD PDCCH monitoring opportunity and the monitored non-XDD PDCCH monitoring opportunity, for a maximum number of BDs or CCEs. That is, the number of PDCCH candidates or non-overlapping CCEs may be counted separately for normal TDD operations and XDD operations, respectively. 【0222】 For a non-XDD SS set or a non-XDD PDCCH monitoring opportunity, the number of PDCCH candidates or non-overlapping CCEs for the non-XDD SS set to be monitored or the non-XDD PDCCH monitoring opportunity to be monitored may be counted per slot, per span, or per group of X slots. Here, per slot, per span, or per group of X slots may be based on the setting by monitoringCapabilityConfig-r16 or monitoringCapabilityConfig-r17. Also, the maximum number of BD or CCE limits per slot, per span, or per group of X slots is, for example, {M1 PDCCH max,slot,μ ,C1 PDCCH max,slot,μ}, {M1 PDCCH max,(X,Y),μ ,C1 PDCCH max,(X,Y),μ}, or {M1 PDCCH max,Xsslot,μ ,C1 PDCCH max,Xsslot,μ}, and these values may be the same as the values defined in Rel-15 / 16 / 17, or may be more or less. 【0223】 For example, when the per-slot monitoring capability of Rel-15 is notified (for example, monitoringCapabilityConfig-r16 = r15monitoringcapability or monitoringCapabilityConfig-r17 = r15monitoringcapability is provided to the UE, or neither monitoringCapabilityConfig-r16 nor monitoringCapabilityConfig-r17 is set), the number of PDCCH candidates or non-overlapping CCEs for the non-XDD SS set to be monitored or the non-XDD PDCCH monitoring opportunity to be monitored is counted per slot, and the maximum number of BD or CCE limits is set as {M1 PDCCH max,slot,μ ,C1 PDCCH max,slot,μ}. 【0224】 For an XDD SS set or an XDD PDCCH monitoring opportunity, the number of PDCCH candidates or non-overlapping CCEs for the monitored XDD SS set or the monitored XDD PDCCH monitoring opportunity may be counted per slot, per span, or per group of X slots. Here, per slot, per span, or per group of X slots may be in accordance with Example 4-1. Also, 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 may be the same as the values defined in Rel-15 / 16 / 17, or may be more or fewer. 【0225】 For example, when the per-slot monitoring capability of Rel-15 is notified (for example, monitoringCapabilityConfigForXdd=r16monitoringcapability is provided to the UE), the number of PDCCH candidates or non-overlapping CCEs for the monitored XDD SS set or the monitored XDD PDCCH monitoring opportunity may be counted per span, and the maximum number of BD or CCE limits may be {M2 PDCCH max,(X,Y),μ ,C2 PDCCH max,(X,Y),μ}. 【0226】 As a variant, (M1 PDCCH max,slot,μ +M2 PDCCH max,slot,μ ) is the M PDCCH max,slot,μIt may be the same as, or more or fewer than, (C1 PDCCH max,slot,μ +C2 PDCCH max,slot,μ ) is M as defined in Rel-15 PDCCH max,slot,μ It may be the same as, or a greater or lesser number. 【0227】 Other variations include (M1 PDCCH max,(X,Y),μ +M2 PDCCH max,(X,Y),μ ) is M as defined in Rel-16 PDCCH max,(X,Y),μ It may be the same as, or more or fewer than, (C1 PDCCH max,(X,Y),μ +C2 PDCCH max,(X,Y),μ ) is M as defined in Rel-16 PDCCH max,(X,Y),μ It may be the same as, or a greater or lesser number. 【0228】 Other variations include (M1 PDCCH max,Xsslot,μ +M2 PDCCH max,Xsslot,μ ) is M as defined in Rel-17 PDCCH max,Xsslot,μ It may be the same as, or more or fewer than, (C1 PDCCH max,Xsslot,μ +C2 PDCCH max,Xsslot,μ ) is M as defined in Rel-17 PDCCH max,Xsslot,μ It may be the same as, or a greater or lesser number. 【0229】 For example, the example shown in Figure 31A relates to the slot-by-slot PDCCH monitoring capability of Rel-15. XDD USS#1 and XDD USS#3 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,μ}. Also, 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,μ} 【0230】 For example, the example shown in Figure 31B also relates to the slot-by-slot PDCCH monitoring capability of Rel-15. 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,μ} 【0231】 As a second operation, the UE may jointly count PDCCH candidates or non-overlapping CCEs for the monitored XDD SS set and the monitored non-XDD SS set, or for the monitored XDD PDCCH monitoring opportunity and the monitored non-XDD PDCCH monitoring opportunity, for the maximum number of BDs or CCEs (joint counting). That is, PDCCH candidates or non-overlapping CCEs may be counted together for normal TDD operations and XDD operations. 【0232】 The number of PDCCH candidates or non-overlapping CCEs for the monitored XDD SS sets and the monitored non-XDD SS sets, or the number of PDCCH candidates or non-overlapping CCEs for the monitored XDD PDCCH monitoring opportunities and the monitored non-XDD PDCCH monitoring opportunities, may be counted collectively per slot, per span, or per group of X slots. 【0233】 Whether it is per slot, per span, or per group of X slots may be based on the granularity or unit (i.e., slot level, span level, or slot group level) of the monitoring capabilities notified or configured for non-XDD SS sets or non-XDD PDCCH monitoring opportunities (e.g., by monitoringCapabilityConfig-r16 and / or monitoringCapabilityConfig-r17) and the monitoring capabilities notified, configured, or defined for XDD SS sets or XDD PDCCH monitoring opportunities (e.g., by Example 4-1). For example, the table shown in Figure 32 summarizes the relationship between Rel-15 / 16 / 17 and PDCCH monitoring capabilities. 【0234】 If the granularity / unit for a non-XDD SS set or non-XDD PDCCH monitoring opportunity (i.e., slot level, span level, or slot group level) is the same as the granularity / unit for an XDD SS set or XDD PDCCH monitoring opportunity (i.e., slot level, span level, or slot group level), then the said granularity or unit may be used to count the number of PDCCH candidates or non-overlapping CCEs. On the other hand, if the granularity / unit for a non-XDD SS set or non-XDD PDCCH monitoring opportunity (i.e., slot level, span level, or slot group level) is different from the granularity / unit for an XDD SS set or XDD PDCCH monitoring opportunity (i.e., slot level, span level, or slot group level), then a larger granularity or unit may be used to count the number of PDCCH candidates or non-overlapping CCEs. 【0235】 For PDCCH monitoring on a BWP or cell, the maximum number of BD or CCE limits per slot, per span, or per group of X slots, 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 fixed or variable. 【0236】 For example, the value of the maximum number of BD or CCE limits per slot, per span, or per group of X slots may be variable depending on whether the slot, span, or group of X slots contains or overlaps with an XDD time unit or XDD symbol, whether it contains any XDD PDCCH monitoring opportunity for any monitoring target, or whether it contains any PDCCH candidate of the XDD SS set for the monitoring target. 【0237】 As an example, {M2´ PDCCH max,slot,μ , C2´ PDCCH max,slot,μ} of the XDD slot may be different from {M1´ PDCCH max,slot,μ , C1´ PDCCH max,slot,μ} of the non - XDD slot. 【0238】 As another example, {M2´ PDCCH max,(X,Y),μ , C2´ PDCCH max,(X,Y),μ} of the XDD span may be different from {M1´ PDCCH max,(X,Y),μ , C1´ PDCCH max,(X,Y),μ} of the non - XDD span. 【0239】 As another example, {M2´ PDCCH max,Xsslot,μ , C2´ PDCCH max,Xsslot,μ} of the XDD slot group may be different from {M1´ PDCCH max,Xsslot,μ , C1´ PDCCH max,Xsslot,μ} of the non - XDD slot group. 【0240】 As a variant example, the maximum number of BDs or CCE limits of the non - XDD slot, non - XDD span or non - XDD slot group may be the same as, or more or less than, the maximum number of BDs or CCE limits defined in Rel - 15 / 16 / 17. 【0241】 For example, the example shown in Figure 33A relates to the PDCCH monitoring capability per slot of Rel - 15. XDD USS#1, non - XDD USS#2 and non - XDD CSS#1 are XDD PDCCH monitoring opportunities to be monitored, and the maximum number of BDs or CCE limits is {M1´ PDCCH max,slot,μ , C1´ PDCCH max,slot,μ}. 【0242】 Furthermore, the example shown in Figure 33B, for example, also relates to the slot-by-slot PDCCH monitoring capability of Rel-15. 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,μ} 【0243】 Furthermore, for example, the maximum number of BD or CCE limits per slot, per span, or per group of X slots is constant on the BWP or cell, and the BWP or cell value notified or set for XDD operation may be the same as, or more or fewer than, the maximum number of BD or CCE limits specified in Rel-15 / 16 / 17. 【0244】 For example, the example shown in Figure 34A relates to the slot-by-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 for cell #2 is {M1' PDCCH max,slot,μ ,C1' PDCCH max,slot,μ} 【0245】 Furthermore, the example shown in Figure 34B also relates to the slot-by-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 being monitored, and the maximum number of BD or CCE limits for cell #1 is {M2' PDCCHmax,slot,μ ,C2' PDCCH max,slot,μ} and the maximum number of BD or CCE limits for cell #2 is {M1' PDCCH max,slot,μ ,C1' PDCCH max,slot,μ} 【0246】 Thus, according to the fourth embodiment, the UE may receive a PDCCH monitoring capability (e.g., monitoringCapabilityConfig) regarding XDD operations on radio resources (e.g., cells, BWPs, etc.) and control PDCCH monitoring according to the PDCCH monitoring capability. In response, the base station may set and transmit a PDCCH monitoring capability regarding XDD operations on radio resources. 【0247】 Specifically, the PDCCH monitoring capability may be set commonly for both XDD operation and non-XDD operation. 【0248】 Furthermore, the PDCCH monitoring capability may be configured separately for XDD operation and non-XDD operation. 【0249】 Furthermore, the UE may count the PDCCH candidates or non-overlapping control channel elements in XDD operation and the PDCCH candidates or non-overlapping control channel elements in non-XDD operation separately or together. 【0250】 The settings or notifications described above may be transmitted based, for example, on at least one of the RRC (Radio Resource Control) information element, DCI (Downlink Control Information), and MAC CE (Medium Access Control Control Element). Furthermore, this disclosure is not limited to PDCCH monitoring and may apply to other types of control signals transmitted from a base station to a UE or other base station (e.g., an IAB node). 【0251】 To implement the XDD operation described above, the UE may transmit UE capability information regarding the XDD operation to the base station, and the base station may notify or configure the XDD operation to the UE based on the received UE capability information. Specifically, the UE capability information may specify whether the UE supports unified capability notification, configuration, or provision for monitoring XDD SS sets (or XDD PDCCH monitoring opportunities) and non-XDD SS sets (or XDD PDCCH monitoring opportunities). The UE may transmit UE capability information to the base station regarding whether it supports unified capability notification, configuration, or provision for monitoring XDD SS sets (or XDD PDCCH monitoring opportunities) and non-XDD SS sets (or XDD PDCCH monitoring opportunities). 【0252】 Furthermore, UE capability information may be provided regarding whether the UE supports separate capability notices, configurations, or provisions for monitoring XDD SS sets (or XDD PDCCH monitoring opportunities). The UE may transmit UE capability information regarding whether it supports separate capability notices, configurations, or provisions for monitoring XDD SS sets (or XDD PDCCH monitoring opportunities) to the base station. 【0253】 Furthermore, UE capability information may be specified 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). The UE may transmit 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) to the base station. 【0254】 Furthermore, UE capability information may be specified regarding whether the UE supports a joint PDCCH candidate and non-overlapping CCE count for monitoring XDD SS sets (or XDD PDCCH monitoring opportunities) and non-XDD SS sets (or XDD PDCCH monitoring opportunities). The UE may transmit UE capability information regarding whether it supports a joint PDCCH candidate and non-overlapping CCE count for monitoring XDD SS sets (or XDD PDCCH monitoring opportunities) and non-XDD SS sets (or XDD PDCCH monitoring opportunities) to the base station. 【0255】 According to the fourth embodiment, when an XDD operation is notified, configured, or applied to a cell where PDCCH monitoring is configured, UE operations regarding PDCCH monitoring capability and BD / CCE limits can be defined. 【0256】 (Fifth example) There is currently no discussion regarding PDCCH overbooking when XDD operations are notified, configured, or applied to cells where PDCCH monitoring is configured. Therefore, it is necessary to define UE behavior regarding PDCCH overbooking when XDD operations are notified, configured, or applied to cells where PDCCH monitoring is configured. In other words, PDCCH overbooking will be defined for XDD operations. 【0257】 In the fifth embodiment, overbooking is permitted or not permitted for a cell in which an XDD operation is notified or set, for a slot, span, or group of X slots that contains or overlaps an XDD time unit or XDD symbol, for a slot, span, or group of X slots that contains a monitored XDD SS set, or for a slot, span, or group of X slots that contains a monitored XDD PDCCH monitoring opportunity. 【0258】 In Specific Example 1, overbooking of the slot-based PDCCH monitoring capability of Rel-15 may or may not be permitted as follows: Here, an XDD slot may mean a slot containing an XDD SS set to be monitored, and / or an XDD PDCCH monitoring opportunity to be monitored, which contains or overlaps XDD time units or XDD symbols. 【0259】 As a specific example 1-1, when an XDD operation is notified to or configured on a cell, the UE may not assume that a number of PDCCH candidates longer than the BD or CCE limit for that cell will be monitored in the slot. In other words, unlike Rel-15, when an XDD operation is notified to or configured on a Pcell or PScell, overbooking on the Pcell or PScell ​​may not be assumed. 【0260】 As a specific example 1-2, if the slot is an XDD slot, the UE may not assume that a number of PDCCH candidates longer than the BD or CCE limit for that cell will be monitored in the slot. 【0261】 As a specific example 1-3, if a number of PDCCH candidates exceeding the BD or CCE limit is monitored in a slot, the UE may drop a specific PDCCH candidate in the slot as long as the BD or CCE limit for that cell is not exceeded, provided that an XDD operation is notified or set to the cell. In other words, unlike Rel-15, overbooking may be tolerated on the Scell ​​if an XDD operation is notified or set to the Scell. 【0262】 As a specific example 1-4, if a number of PDCCH candidates exceeding the BD or CCE limit is being monitored in a slot, the UE may, if the cell is an XDD slot, drop a specific PDCCH candidate in the slot as long as the BD or CCE limit for that cell is not exceeded. 【0263】 As one variation, the BD or CCE limit value for Scell ​​may be the same as, or different from, the BD or CCE limit value specified for the monitoring capability of Rel-15 for Pcell or PScell. 【0264】 As another variation, the BD or CCE limit values ​​for cells with XDD operation may be the same as, or different from, the BD or CCE limit values ​​specified in the Rel-15 monitoring capability for Pcell or PScell. 【0265】 As another variation, the BD or CCE limit values ​​for the XDD slot may be the same as, or different from, the BD or CCE limit values ​​specified for the Rel-15 monitoring capability for the Pcell or PScell. 【0266】 In Specific Example 2, overbooking for Rel-16 span-based PDCCH monitoring capability may or may not be permitted as follows: Here, XDD span may mean a span containing XDD SS sets to be monitored and / or XDD PDCCH monitoring opportunities to be monitored, which contain or overlap XDD time units or XDD symbols. 【0267】 As a specific example 2-1, when an XDD operation is notified to or configured on a cell, the UE may not assume that a number of PDCCH candidates longer than the BD or CCE limit for that cell will be monitored in the span. In other words, unlike Rel-16, when an XDD operation is notified to or configured on a Pcell or PScell, overbooking on the Pcell or PScell ​​may not be assumed. 【0268】 As a specific example 2-2, if the span is an XDD span, the UE may not assume that a number of PDCCH candidates longer than the BD or CCE limit for that cell will be monitored in the span. 【0269】 As a specific example 2-3, if a number of PDCCH candidates exceeding the BD or CCE limit is monitored in a span (or the first span in a slot), the UE may drop a specific PDCCH candidate in the span as long as the BD or CCE limit for that cell (or Pcell / PScell) is not exceeded, provided that an XDD operation is notified or set for that cell (or Pcell / PScell). In other words, unlike Rel-16, overbooking may be tolerated on an Scell ​​if an XDD operation is notified or set for an Scell. Also, overbooking may be tolerated on spans other than the first span in a slot if an XDD operation is notified or set for a cell. 【0270】 As a specific example 2-4, if a number of PDCCH candidates exceeding the BD or CCE limit is monitored in a span (or the first span in a slot), the UE may drop a specific PDCCH candidate in the span, provided that the span on the cell (or Pcell / PScell) is an XDD span, as long as the BD or CCE limit for that cell (or Pcell / PScell) is not exceeded. 【0271】 As one variation, the BD or CCE limit values ​​for spans other than the first span in a slot on a Pcell / PScell ​​may be the same as, or different from, the BD or CCE limit values ​​specified in Rel-16 for the first span in a slot on a Pcell or PScell. 【0272】 As another variation, the BD or CCE limit values ​​for cells with XDD operation may be the same as, or different from, the BD or CCE limit values ​​specified in the monitoring capability of Rel-16 for Pcell or PScell. 【0273】 As another variation, the BD or CCE limit value for the first span in a slot on Scell ​​may be the same as, or different from, the BD or CCE limit value specified in Rel-16 for the first span in a slot on Pcell or PScell. 【0274】 As another variation, the BD or CCE limit values ​​for spans other than the first span in a slot on Scell ​​may be the same as, or different from, the BD or CCE limit values ​​specified in Rel-16 for the first span in a slot on Pcell or PScell. 【0275】 As another variation, the BD or CCE limit values ​​for the XDD span may be the same as, or different from, the BD or CCE limit values ​​specified in Rel-16 for Pcell or PScell. 【0276】 In specific example 3, overbooking may or may not be permitted for the multi-slot PDCCH monitoring capability of Rel-17, as follows: Here, an XDD slot group may mean a group of X slots containing XDD SS sets to be monitored and / or XDD PDCCH monitoring opportunities to be monitored, which contain or overlap XDD time units or XDD symbols. 【0277】 As a specific example 3-1, when an XDD operation is notified to or configured on a cell, the UE may not assume that a number of PDCCH candidates longer than the BD or CCE limit for that cell will be monitored in a group of X slots. In other words, unlike Rel-17, when an XDD operation is notified to or configured on a Pcell, overbooking on the Pcell may not be assumed. 【0278】 As a specific example 3-2, if a group of X slots is an XDD slot group, the UE may not assume that a number of PDCCH candidates longer than the BD or CCE limit for that cell will be monitored in the group of X slots. 【0279】 As a specific example 3-3, if a group of X slots has a number of PDCCH candidates that exceeds the BD or CCE limit, the UE may drop certain PDCCH candidates in the group of X slots when an XDD operation is notified to or set on the (primary) cell, as long as the BD or CCE limit for that (primary) cell is not exceeded. In other words, unlike Rel-17, overbooking may be tolerated on the Scell ​​when an XDD operation is notified to or set on the Scell. 【0280】 As a specific example 3-4, if a group of X slots has a number of PDCCH candidates longer than the BD or CCE limit, the UE may drop a specific PDCCH candidate in the group of X slots, provided that the group of X slots is an XDD slot group, as long as the BD or CCE limit for that (primary) cell is not exceeded. 【0281】 As one variation, the BD or CCE limit value for Scell ​​may be the same as, or different from, the BD or CCE limit value specified for the monitoring capability of Rel-17 for the primary cell. 【0282】 As another variation, the BD or CCE limit values ​​for cells with XDD operation may be the same as, or different from, the BD or CCE limit values ​​specified in the monitoring capability of Rel-17 for Pcell or PScell. 【0283】 As another variation, the BD or CCE limit values ​​for the XDD slot group may be the same as, or different from, the BD or CCE limit values ​​specified for the monitoring capability of Rel-17 for the primary cell. 【0284】 Thus, according to the fifth embodiment, the UE may control PDCCH overbooking in the XDD time unit in which PDCCH monitoring is set, and perform PDCCH monitoring on selected PDCCH monitoring opportunities in the controlled PDCCH overbooking. That is, the UE may drop some PDCCH monitoring opportunities from the overbooked PDCCH monitoring opportunities. In response to this, the base station may set PDCCH monitoring opportunities that are overbooked in the XDD time unit in which PDCCH monitoring is set, and transmit control information on the PDCCH monitoring opportunities. 【0285】 The settings or notifications described above may be transmitted based, for example, on at least one of the RRC (Radio Resource Control) information element, DCI (Downlink Control Information), and MAC CE (Medium Access Control Control Element). Furthermore, this disclosure is not limited to PDCCH monitoring and may apply to other types of control signals transmitted from a base station to a UE or other base station (e.g., an IAB node). 【0286】 To implement the XDD operation described above, the UE may transmit UE capability information regarding the XDD operation to the base station, and the base station may notify or configure the UE to perform the XDD operation based on the received UE capability information. Specifically, when a cell is notified or configured for the XDD operation, UE capability information regarding whether the UE supports PDCCH overbooking on the cell may be specified. When a cell is notified or configured for the XDD operation, the UE may transmit UE capability information regarding whether the UE supports PDCCH overbooking on the cell to the base station. 【0287】 Furthermore, UE capability information regarding whether the UE supports PDCCH overbooking in an XDD slot, XDD span, or XDD slot group may be specified. The UE may transmit UE capability information regarding whether the UE supports PDCCH overbooking in an XDD slot, XDD span, or XDD slot group to the base station. 【0288】 Furthermore, UE capability information may be provided 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). The UE may transmit UE capability information 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) to the base station. 【0289】 According to the fifth embodiment, when an XDD operation is notified, configured, or applied to a cell where PDCCH monitoring is configured, UE operation regarding PDCCH overbooking can be defined. 【0290】 (Sixth embodiment) Currently, there is no discussion regarding PDCCH overbooking when XDD operations are notified, configured, or applied to cells where PDCCH monitoring is configured. Therefore, it is necessary to define UE operations regarding PDCCH overbooking when XDD operations are notified, configured, or applied to cells where PDCCH monitoring is configured. In other words, rules for PDCCH overbooking may be defined for XDD operations. Specifically, for the PDCCH overbooking allowed in Example 5, UE operations are defined to select PDCCH monitoring opportunities to be monitored / dropped from overbooked PDCCH monitoring opportunities. 【0291】 In the sixth embodiment, overbooking may be permitted for a slot, span, or group of X slots if the slot contains or overlaps an XDD time unit or XDD symbol, contains any XDD SS set being monitored, or contains any XDD PDCCH monitoring opportunity being monitored. 【0292】 As option 0 of the sixth embodiment, the existing PDCCH overbooking rules of Rel-15 / 16 / 17 may be reused. That is, the rules of Rel-15 / 16 / 17 are applied. 【0293】 As option 1 of the sixth embodiment, whether or not the overbooking is an XDD SS set or a non-XDD SS set may be considered. 【0294】 In Option 1-1 of the sixth embodiment, the following prioritization may be applied: “CSS has a higher priority than USS” → “Non-XDD SS sets have a higher or lower priority than XDD SS sets” → “Smaller SS indices have a higher priority than larger SS indices.” 【0295】 As option 1-1A of the sixth embodiment, non-XDD CSS may not be expected to be dropped. XDD CSS, non-XDD USS, and XDD USS may be dropped based on priority. For example, the UE may not expect the number of non-XDD CSS PDCCH candidates or non-overlapping CCEs in any slot / span / group of X slots to exceed the BD or CCE limit. Also, as a variation, XDD CSS may not be expected to be dropped. Non-XDD CSS, XDD USS, and non-XDD USS may be dropped based on priority. 【0296】 As option 1-1B of the sixth embodiment, non-XDD CSS and XDD CSS may not be expected to be dropped. Non-XDD USS and XDD USS may be dropped based on priority. For example, the UE may not expect the number of non-XDD CSS and XDD CSS PDCCH candidates or non-overlapping CCEs in any slot / span / group of X slots to exceed the BD or CCE limit. Also, as an example, 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. 【0297】 As option 1-1C of the sixth embodiment, non-XDD CSS, XDD CSS, and non-XDD USS may not be expected to be dropped. XDD USS may be dropped based on priority. For example, the UE may not expect the number of non-XDD CSS, XDD CSS, and non-XDD USS PDCCH candidates or non-overlapping CCEs in any slot / span / group of X slots to exceed the BD or CCE limit. Also, as a variation, non-XDD CSS, XDD CSS, and non-XDD USS may not be expected to be dropped. Non-XDD USS may be dropped based on priority. 【0298】 According to the priority and modifications of Option 1-1 of the sixth embodiment, XDD CSS, non-XDD CSS, XDD USS, and non-XDD USS may be prioritized as shown in Figure 35. 【0299】 In option 1-2 of the sixth embodiment, the following prioritization may be applied: “Non-XDD SS sets have a higher or lower priority than XDD SS sets” → “CSS has a higher priority than USS” → “Smaller SS indices have a higher priority than larger SS indices.” 【0300】 As an option 1-2A of the sixth embodiment, non-XDD CSS may not be expected to be dropped. Non-XDD USS, XDD CSS, and XDD USS may be dropped based on priority. For example, the UE may not expect the number of non-XDD CSS PDCCH candidates or non-overlapping CCEs in any slot / span / group of X slots to exceed the BD or CCE limit. Also, as an example, XDD CSS may not be expected to be dropped. XDD USS, non-XDD CSS, and non-XDD USS may be dropped based on priority. 【0301】 As an option 1-2B of the sixth embodiment, 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. For example, the UE may not expect the number of non-XDD CSS and non-XDD USS PDCCH candidates or non-overlapping CCEs in any slot / span / group of X slots to exceed the BD or CCE limit. Also, as an example, XDD CSS and XDD USS may not be expected to be dropped. Non-XDD CSS and non-XDD USS may be dropped based on priority. 【0302】 As an option 1-2C of the sixth embodiment, non-XDD CSS, non-XDD USS, and XDD CSS may not be expected to be dropped. XDD USS may be dropped based on priority. For example, the UE may not expect the number of non-XDD CSS, non-XDD USS, and XDD CSS PDCCH candidates or non-overlapping CCEs in any slot / span / group of X slots to exceed the BD or CCE limit. Also, as an example, XDD CSS, XDD USS, and non-XDD CSS may not be expected to be dropped. Non-XDD USS may be dropped based on priority. 【0303】 According to the priority and modifications of options 1-2 of the sixth embodiment, XDD CSS, non-XDD CSS, XDD USS, and non-XDD USS may be prioritized as shown in Figure 36. 【0304】 For example, in the symbol arrangement shown in Figure 37, according to the Rel-15 rules, XDD CSS#1 and XDD USS#1 may be monitored, and non-XD USS#2 may be dropped. Also, according to option 1-1, XDD CSS#1 and non-XD USS#2 may be monitored, and XDD USS#1 may be dropped. Also, according to option 1-2, non-XD USS#2 and XDD CSS#1 may be monitored, and XDD USS#1 may be dropped. 【0305】 As option 2 of the sixth embodiment, whether or not an overbooking is an XDD PDCCH monitoring opportunity or a non-XDD PDCCH monitoring opportunity may be considered. Here, an XDD PDCCH monitoring opportunity means a PDCCH monitoring opportunity that includes or overlaps XDD time units or XDD symbols. A non-XDD PDCCH monitoring opportunity means a PDCCH monitoring opportunity that does not include or overlap XDD time units or XDD symbols. 【0306】 In Option 2-1 of the sixth embodiment, the following prioritization may be applied: “CSS has a higher priority than USS” → “Non-XDD PDCCH monitoring opportunities have a higher or lower priority than XDD PDCCH monitoring opportunities” → “Smaller SS indices have a higher priority than larger SS indices.” 【0307】 As an option 2-1A of the sixth embodiment, PDCCH candidates for 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. For example, the UE may not expect the number of PDCCH candidates or non-overlapping CCEs for non-XDD PDCCH monitoring opportunities in any slot / span / group of X slots to exceed the BD or CCE limit. Also, as an example, PDCCH candidates for 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 CSS set, XDD PDCCH monitoring opportunities in the USS set, and XDD PDCCH monitoring opportunities in the USS set may be dropped based on priority. 【0308】 As option 2-1B of the sixth embodiment, non-XDD PDCCH monitoring opportunities in CSS sets and PDCCH candidates for XDD PDCCH monitoring opportunities in CSS sets may not be expected to be dropped. Non-XDD PDCCH monitoring opportunities in USS sets and PDCCH candidates for XDD PDCCH monitoring opportunities in USS sets may be dropped based on priority. For example, the UE may not expect the number of non-XDD PDCCH monitoring opportunities in CSS sets and PDCCH candidates or non-overlapping CCEs in any slot / span / group of X slots to exceed the BD or CCE limit. Also, as one variation, XDD PDCCH monitoring opportunities in CSS sets and PDCCH candidates for non-XDD PDCCH monitoring opportunities in CSS sets may not be expected to be dropped. XDD PDCCH monitoring opportunities in USS sets and PDCCH candidates for non-XDD PDCCH monitoring opportunities in USS sets may be dropped based on priority. 【0309】 As option 2-1C of the sixth embodiment, PDCCH candidates for 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 may not be expected to be dropped. PDCCH candidates for XDD PDCCH monitoring opportunities in the USS set may be dropped based on priority. For example, the UE may not expect the number of PDCCH candidates or non-overlapping CCEs for 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 to exceed the BD or CCE limit in any slot / span / group of X slots. Also, as one variation, 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. 【0310】 According to the priority and modification of Option 2-1 of the sixth embodiment, the XDD PDCCH monitoring opportunities for the CSS set, the non-XDD PDCCH monitoring opportunities for the CSS set, the XDD PDCCH monitoring opportunities for the USS set, and the non-XDD PDCCH monitoring opportunities for the USS set may be prioritized as shown in Figure 38. 【0311】 In Option 2-2 of the sixth embodiment, the following prioritization may be applied: “Non-XDD PDCCH monitoring opportunities have a higher or lower priority than XDD PDCCH monitoring opportunities” → “CSS has a higher priority than USS” → “Smaller SS indices have a higher priority than larger SS indices.” 【0312】 As an option 2-2A of the sixth embodiment, PDCCH candidates for 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. For example, the UE may not expect the number of PDCCH candidates or non-overlapping CCEs for non-XDD PDCCH monitoring opportunities in the CSS set in any slot / span / group of X slots to exceed the BD or CCE limit. Also, as an example, PDCCH candidates for XDD PDCCH monitoring opportunities in 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. 【0313】 As option 2-2B of the sixth embodiment, PDCCH candidates for 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 XDD PDCCH monitoring opportunities in the CSS set and XDD PDCCH monitoring opportunities in the USS set may be dropped based on priority. For example, the UE may not expect the number of non-XDD PDCCH monitoring opportunities in the CSS set, non-XDD PDCCH monitoring opportunities in the USS set, and PDCCH candidates or non-overlapping CCEs in any slot / span / group of X slots to exceed the BD or CCE limit. Also, as one variation, PDCCH candidates for 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 CSS set and non-XDD PDCCH monitoring opportunities in the USS set may be dropped based on priority. 【0314】 As option 2-2C of the sixth embodiment, it is not necessary to assume that non-XDD PDCCH monitoring opportunities in the CSS set, non-XDD PDCCH monitoring opportunities in the USS set, and PDCCH candidates for XDD PDCCH monitoring opportunities in the CSS set will be dropped. PDCCH candidates for XDD PDCCH monitoring opportunities in the USS set may be dropped based on priority. For example, the UE does not need to assume that the number of non-XDD PDCCH monitoring opportunities in the CSS set, non-XDD PDCCH monitoring opportunities in the USS set, and PDCCH candidates or non-overlapping CCEs in any slot / span / group of X slots will exceed the BD or CCE limit. Also, as one variation, it is not necessary to assume that PDCCH candidates for XDD PDCCH monitoring opportunities in the CSS set, XDD PDCCH monitoring opportunities in the USS set, and non-XDD PDCCH monitoring opportunities in the CSS set will be dropped. PDCCH candidates for non-XDD PDCCH monitoring opportunities in the USS set may be dropped based on priority. 【0315】 According to the priority and modification of Option 2-2 of the sixth embodiment, the XDD PDCCH monitoring opportunities for the CSS set, the non-XDD PDCCH monitoring opportunities for the CSS set, the XDD PDCCH monitoring opportunities for the USS set, and the non-XDD PDCCH monitoring opportunities for the USS set may be prioritized as shown in Figure 39. 【0316】 For example, in the symbol arrangement shown in Figure 40, according to the Rel-15 rules, CSS#1 (XDD MO) and USS#1 (XDD MO) may be monitored, and USS#2 (non-XDD MO) may be dropped. Also, according to option 2-1, CSS#1 (XDD MO) and USS#2 (non-XDD MO) may be monitored, and USS#1 (XDD MO) may be dropped. Also, according to option 2-2, USS#1 (XDD MO) and CSS#1 (XDD MO) may be monitored, and USS#1 (XDD MO) may be dropped. 【0317】 Thus, according to the sixth embodiment, the UE controls PDCCH overbooking in the XDD time unit in which PDCCH monitoring is set, and when performing PDCCH monitoring on selected PDCCH monitoring opportunities in the controlled PDCCH overbooking, it may select PDCCH monitoring opportunities according to priority. That is, the UE may drop some PDCCH monitoring opportunities from the overbooked PDCCH monitoring opportunities according to that priority. 【0318】 Specifically, PDCCH monitoring opportunities may be selected based on a first priority between the Common Search Space (CSS) and the User-Specific Search Space (USS), a second priority between the Non-XDD Search Space Set (non-XDD SS) and the XDD Search Space Set (XDD SS), and a third priority between the Search Space Indexes (SS index). 【0319】 Furthermore, PDCCH monitoring opportunities may be selected based on a fourth priority ranking between non-XDD PDCCH monitoring opportunities and XDD PDCCH monitoring opportunities. 【0320】 The settings or notifications described above may be transmitted based, for example, on at least one of the RRC (Radio Resource Control) information element, DCI (Downlink Control Information), and MAC CE (Medium Access Control Control Element). Furthermore, this disclosure is not limited to PDCCH monitoring and may apply to other types of control signals transmitted from a base station to a UE or other base station (e.g., an IAB node). 【0321】 To implement the XDD operation described above, the UE may transmit UE capability information regarding the XDD operation to the base station, and the base station may notify or configure the UE to perform the XDD operation based on the received UE capability information. Specifically, when a cell is notified or configured for the XDD operation, UE capability information regarding whether the UE supports PDCCH overbooking on the cell may be specified. When a cell is notified or configured for the XDD operation, the UE may transmit UE capability information regarding whether the UE supports PDCCH overbooking on the cell to the base station. 【0322】 Furthermore, UE capability information regarding whether the UE supports PDCCH overbooking in an XDD slot, XDD span, or XDD slot group may be specified. The UE may transmit UE capability information regarding whether the UE supports PDCCH overbooking in an XDD slot, XDD span, or XDD slot group to the base station. 【0323】 Furthermore, UE capability information may be provided 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). The UE may transmit UE capability information 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) to the base station. 【0324】 According to the sixth embodiment, when an XDD operation is notified, configured, or applied to a cell where PDCCH monitoring is configured, UE operations regarding PDCCH overbooking can be defined. 【0325】 (Seventh Example) There is currently no discussion regarding the PDCCH monitoring beam when XDD operation is notified, configured, or applied to a cell where PDCCH monitoring is configured. Therefore, it is necessary to define the UE operation for the PDCCH monitoring beam when XDD operation is notified, configured, or applied to a cell where PDCCH monitoring is configured. Specifically, with respect to the PDCCH monitoring beam, the UE may perform the following actions: 【0326】 In the seventh embodiment, if the UE is configured for single-cell operation or carrier aggregation (CA) operation in the same frequency band and monitors PDCCH candidates that include or overlap in multiple CORESETs with the same or different qcl-Types configured with the “typeD” nature for the active DL BWP of one or more cells, the UE may monitor the PDCCH on the active DL BWP of one or more cells only in one CORESET and any other CORESET from multiple CORESETs with the same “typeD” nature configured for that CORESET. If any cell is notified or configured for XDD operation, that CORESET may be determined as the CORESET of the SS with the highest priority. 【0327】 In Option 1 of Embodiment 7, existing Rel-15 / 16 rules may be reused for prioritization. That is, the following prioritization may be applied: "CSS has higher priority than USS" → "Smaller cell indexes have higher priority than larger cell indexes" → "Smaller SS indexes have higher priority than larger SS indexes". The CORESET may correspond to the CSS set with the smallest index in the cell with the smallest index containing CSS, if it exists, or to the USS set with the smallest index in the cell with the smallest index if it does not exist. 【0328】 In Option 2 of the 7th embodiment, whether or not there are cells that are notified / configured for XDD operation may be considered in the determination. 【0329】 As option 2-1 of the seventh embodiment, a prioritization as shown in Figure 41 may be applied, which is as follows: "CSS has a higher priority than USS" → "Cells that are not notified or set for XDD operation have a higher or lower priority than cells that are notified or set for XDD operation" → "Smaller cell indexes have a higher priority than larger cell indexes" → "Smaller SS indexes have a higher priority than larger SS indexes". 【0330】 As option 2-2 of the seventh embodiment, a prioritization as shown in Figure 42 may be applied, such as: "Cells that are not notified or set for XDD operation have a higher or lower priority than cells that are notified or set for XDD operation" → "CSS has a higher priority than USS" → "Smaller cell indexes have a higher priority than larger cell indexes" → "Smaller SS indexes have a higher priority than larger SS indexes". 【0331】 According to the prioritization of Options 1, 2-1, and 2-2, the five PDCCH monitoring beams—CSS#1 in cell #1, USS#2 in cell #1, USS#3 in cell #1, USS#1 in cell #2, and CSS#2 in cell #2—may be prioritized as shown in Figure 43, for example. Note that XDD operation is notified or configured in cell #1, while XDD operation is not notified or configured in cell #2. 【0332】 In Figure 43A, the existing rules of Rel-15 / 16 are applied, and CSS#1 in cell #1, CSS#2 in cell #2, USS#2 in cell #1, USS#3 in cell #1, and USS#1 in cell #2 are prioritized in descending order of priority. 【0333】 In Figure 43B, the prioritization of Option 2-1 is applied, and CSS#2 in cell #2, CSS#1 in cell #1, USS#1 in cell #2, USS#2 in cell #1, and USS#3 in cell #1 are prioritized in descending order of priority. 【0334】 In Figure 43C, the prioritization of Option 2-2 is applied, and CSS#2 in cell #2, USS#1 in cell #2, CSS#1 in cell #1, USS#2 in cell #1, and USS#3 in cell #1 are prioritized in descending order of priority. 【0335】 Similarly, according to the prioritization of Options 1, 2-1, and 2-2, the four PDCCH monitoring beams—CSS#1 in cell #1, USS#2 in cell #1, USS#3 in cell #1, and USS#1 in cell #2—may be prioritized as shown in Figure 44, for example. Note that XDD operation is notified or configured for cell #1, while XDD operation is not notified or configured for cell #2. 【0336】 In Figure 44A, the existing rules of Rel-15 / 16 are applied, and CSS#1 in cell #1, USS#2 in cell #1, USS#3 in cell #1, and USS#1 in cell #2 are prioritized in descending order of priority. 【0337】 In Figure 44B, the prioritization of Option 2-1 is applied, and CSS#1 in cell #1, USS#1 in cell #2, USS#2 in cell #1, and USS#3 in cell #1 are prioritized in descending order of priority. 【0338】 In Figure 44C, the prioritization of Option 2-2 is applied, and USS#1 in cell #2, CSS#1 in cell #1, USS#2 in cell #1, and USS#3 in cell #1 are prioritized in descending order of priority. 【0339】 In Option 3 of the 7th embodiment, whether or not there is an XDD SS set or a non-XDD SS set may be considered in the determination. Here, an XDD SS set means an SS set in which XDD time units are set. A non-XDD SS set means an SS set in which pure time units are set. 【0340】 As option 3-1 of the seventh embodiment, a prioritization as shown in Figure 45 may be applied, such as: “Non-XDD SS sets have a higher or lower priority than XDD SS sets” → “CSS has a higher priority than USS” → “Smaller cell indices have a higher priority than larger cell indices” → “Smaller SS indices have a higher priority than larger SS indices”. 【0341】 As option 3-2 of the seventh embodiment, a prioritization as shown in Figure 46 may be applied, which is as follows: “CSS has a higher priority than USS” → “Non-XDD SS sets have a higher or lower priority than XDD SS sets” → “Smaller cell indices have a higher priority than larger cell indices” → “Smaller SS indices have a higher priority than larger SS indices”. 【0342】 As a variation of Option 3-2 of Embodiment 7, the following prioritization may be applied: "CSS has a higher priority than USS" → "Non-XDD CSS sets have a higher or lower priority than XDD CSS sets" → "Smaller cell indices have a higher priority than larger cell indices" → "Smaller SS indices have a higher priority than larger SS indices". 【0343】 Furthermore, as another variation of Option 3-2 of the 7th embodiment, the following prioritization may be applied: “CSS has a higher priority than USS” → “Non-XDD USS sets have a higher or lower priority than XDD USS sets” → “Smaller cell indices have a higher priority than larger cell indices” → “Smaller SS indices have a higher priority than larger SS indices.” 【0344】 As option 3-3 of the seventh embodiment, a prioritization as shown in Figure 47 may be applied, which is as follows: "CSS has a higher priority than USS" → "Smaller cell indexes have a higher priority than larger cell indexes" → "Non-XDD SS sets have a higher or lower priority than XDD SS sets" → "Smaller SS indexes have a higher priority than larger SS indexes". 【0345】 As a variation of Option 3-3 of the 7th embodiment, the following prioritization may be applied: "CSS has a higher priority than USS" → "Smaller cell indices have a higher priority than larger cell indices" → "Non-XDD CSS sets have a higher or lower priority than XDD CSS sets" → "Smaller SS indices have a higher priority than larger SS indices". 【0346】 Furthermore, as another variation of Option 3-3 of the 7th embodiment, the following prioritization may be applied: “CSS has a higher priority than USS” → “Smaller cell indexes have a higher priority than larger cell indexes” → “Non-XDD USS sets have a higher or lower priority than XDD USS sets” → “Smaller SS indexes have a higher priority than larger SS indexes.” 【0347】 According to the prioritization of Options 1, 3-1, 3-2, and 3-3 of the 7th embodiment, the five PDCCH monitoring beams, CSS#1 in cell #1, USS#2 in cell #1, USS#3 in cell #1, USS#1 in cell #2, and CSS#2 in cell #2, can be prioritized as shown in Figure 48, for example. Note that CSS#1 in cell #1, USS#2 in cell #1, and USS#1 in cell #2 are XDD SS sets, while USS#3 in cell #1 and CSS#2 in cell #2 are non-XDD SS sets. 【0348】 In Figure 48A, the existing rules of Rel-15 / 16 are applied, and CSS#1 in cell #1, CSS#2 in cell #2, USS#2 in cell #1, USS#3 in cell #1, and USS#1 in cell #2 are prioritized in descending order of priority. 【0349】 In Figure 48B, the prioritization of option 3-1 is applied, and CSS#2 in cell #2, USS#3 in cell #1, CSS#1 in cell #1, USS#2 in cell #1, and USS#1 in cell #2 are prioritized in descending order of priority. 【0350】 In Figure 48C, the prioritization of option 3-2 is applied, and CSS#2 in cell #2, CSS#1 in cell #1, USS#3 in cell #1, USS#2 in cell #1, and USS#1 in cell #2 are prioritized in descending order of priority. 【0351】 In Figure 48D, the prioritization of option 3-3 is applied, and CSS#1 in cell #1, CSS#2 in cell #2, USS#3 in cell #1, USS#2 in cell #1, and USS#1 in cell #2 are prioritized in descending order of priority. 【0352】 According to the prioritization of Options 1, 3-1, 3-2, and 3-3 of the 7th embodiment, the four PDCCH monitoring beams, CSS#1 of cell #1, USS#2 of cell #1, USS#3 of cell #1, and USS#1 of cell #2, can be prioritized as shown in Figure 49, for example. Note that CSS#1 of cell #1 and USS#2 of cell #1 are XDD SS sets, while USS#3 of cell #1 and USS#1 of cell #2 are non-XDD SS sets. 【0353】 In Figure 49A, the existing rules of Rel-15 / 16 are applied, and CSS#1 in cell #1, USS#2 in cell #1, USS#3 in cell #1, and USS#1 in cell #2 are prioritized in descending order of priority. 【0354】 In Figure 49B, the prioritization of option 3-1 is applied, and USS#3 in cell #1, USS#1 in cell #2, CSS#1 in cell #1, and USS#2 in cell #1 are prioritized in descending order of priority. 【0355】 In Figure 49C, the prioritization of option 3-2 is applied, and CSS#1 in cell #1, USS#3 in cell #1, USS#1 in cell #2, and USS#2 in cell #1 are prioritized in descending order of priority. 【0356】 In Figure 49D, the prioritization of option 3-3 is applied, and CSS#1 in cell #1, USS#3 in cell #1, USS#2 in cell #1, and USS#1 in cell #2 are prioritized in descending order of priority. 【0357】 In Option 4 of the 7th embodiment, the determination may take into account whether there is an XDD PDCCH monitoring opportunity or a non-XDD PDCCH monitoring opportunity. Here, an XDD PDCCH monitoring opportunity means a PDCCH monitoring opportunity that includes or overlaps XDD time units or XDD symbols. A non-XDD PDCCH monitoring opportunity means a PDCCH monitoring opportunity that does not include or overlap XDD time units or XDD symbols. 【0358】 As option 4-1 of the seventh embodiment, a prioritization as shown in Figure 45 may be applied, such as: “Non-XDD PDCCH monitoring opportunities have a higher or lower priority than XDD PDCCH monitoring opportunities” → “CSS has a higher priority than USS” → “Smaller cell indexes have a higher priority than larger cell indexes” → “Smaller SS indexes have a higher priority than larger SS indexes”. 【0359】 As option 4-2 of the seventh embodiment, a prioritization as shown in Figure 46 may be applied, which is as follows: “CSS has a higher priority than USS” → “Non-XDD PDCCH monitoring opportunities have a higher or lower priority than XDD PDCCH monitoring opportunities” → “Smaller cell indexes have a higher priority than larger cell indexes” → “Smaller SS indexes have a higher priority than larger SS indexes”. 【0360】 As option 4-3 of the seventh embodiment, a prioritization as shown in Figure 47 may be applied, which is as follows: “CSS has a higher priority than USS” → “Smaller cell indexes have a higher priority than larger cell indexes” → “Non-XDD PDCCH monitoring opportunities have a higher or lower priority than XDD PDCCH monitoring opportunities” → “Smaller SS indexes have a higher priority than larger SS indexes.” 【0361】 According to the prioritization of Options 1, 4-1, 4-2, and 4-3 of the 7th embodiment, the five PDCCH monitoring beams, CSS#1 in cell #1, USS#2 in cell #1, USS#3 in cell #1, USS#1 in cell #2, and CSS#2 in cell #2, can be prioritized as shown in Figure 50, for example. Note that CSS#1 in cell #1, USS#2 in cell #1, and USS#1 in cell #2 are XDD PDCCH monitoring opportunities, while USS#3 in cell #1 and CSS#2 in cell #2 are non-XDD PDCCH monitoring opportunities. 【0362】 In Figure 50A, the existing rules of Rel-15 / 16 are applied, and CSS#1 in cell #1, CSS#2 in cell #2, USS#2 in cell #1, USS#3 in cell #1, and USS#1 in cell #2 are prioritized in descending order of priority. 【0363】 In Figure 50B, the prioritization of option 4-1 is applied, and CSS#2 in cell #2, USS#3 in cell #1, CSS#1 in cell #1, USS#2 in cell #1, and USS#1 in cell #2 are prioritized in descending order of priority. 【0364】 In Figure 50C, the prioritization of option 4-2 is applied, and CSS#2 in cell #2, CSS#1 in cell #1, USS#3 in cell #1, USS#2 in cell #1, and USS#1 in cell #2 are prioritized in descending order of priority. 【0365】 In Figure 50D, the prioritization of option 4-3 is applied, and CSS#1 in cell #1, CSS#2 in cell #2, USS#3 in cell #1, USS#2 in cell #1, and USS#1 in cell #2 are prioritized in descending order of priority. 【0366】 According to the prioritization of Options 1, 4-1, 4-2, and 4-3 of the 7th embodiment, the four PDCCH monitoring beams, CSS#1 of cell #1, USS#2 of cell #1, USS#3 of cell #1, and USS#1 of cell #2, may be prioritized as shown in Figure 51, for example. Note that CSS#1 of cell #1 and USS#2 of cell #1 are XDD PDCCH monitoring opportunities, while USS#3 of cell #1 and USS#1 of cell #2 are non-XDD PDCCH monitoring opportunities. 【0367】 In Figure 51A, the existing rules of Rel-15 / 16 are applied, and CSS#1 in cell #1, USS#2 in cell #1, USS#3 in cell #1, and USS#1 in cell #2 are prioritized in descending order of priority. 【0368】 In Figure 51B, the prioritization of option 4-1 is applied, and USS#3 in cell #1, USS#1 in cell #2, CSS#1 in cell #1, and USS#2 in cell #1 are prioritized in descending order of priority. 【0369】 In Figure 51C, the prioritization of option 4-2 is applied, and CSS#1 in cell #1, USS#3 in cell #1, USS#1 in cell #2, and USS#2 in cell #1 are prioritized in descending order of priority. 【0370】 In Figure 51D, the prioritization of option 4-3 is applied, and CSS#1 in cell #1, USS#3 in cell #1, USS#2 in cell #1, and USS#1 in cell #2 are prioritized in descending order of priority. 【0371】 In Option 5 of the seventh embodiment, whether or not there is a cell where XDD operation is notified or set, and whether or not there is an XDD SS set or a non-XDD SS set may be considered in the determination. That is, Option 5 is a combination of Option 2 and Option 3. 【0372】 As option 5-1 of the seventh embodiment, the following prioritization may be applied: "Cells not notified or configured for XDD operation have a higher or lower priority than cells notified or configured for XDD operation" → "Non-XDD SS sets have a higher or lower priority than XDD SS sets" → "CSS has a higher priority than USS" → "Smaller cell indexes have a higher priority than larger cell indexes" → "Smaller SS indexes have a higher priority than larger SS indexes". 【0373】 As option 5-2 of the seventh embodiment, the following prioritization may be applied: "Cells not notified or configured for XDD operation have a higher or lower priority than cells notified or configured for XDD operation" → "CSS has a higher priority than USS" → "Non-XDD SS sets have a higher or lower priority than XDD SS sets" → "Smaller cell indices have a higher priority than larger cell indices" → "Smaller SS indices have a higher priority than larger SS indices". 【0374】 As a variation of Option 5-2 of the 7th embodiment, the following prioritization may be applied: "Cells not notified or set for XDD operation have a higher or lower priority than cells notified or set for XDD operation" → "CSS has a higher priority than USS" → "Non-XDD CSS / USS sets have a higher or lower priority than XDD CSS / USS sets" → "Smaller cell indices have a higher priority than larger cell indices" → "Smaller SS indices have a higher priority than larger SS indices". 【0375】 As option 5-3 of the seventh embodiment, the following prioritization may be applied: "Cells not notified or configured for XDD operation have a higher or lower priority than cells notified or configured for XDD operation" → "CSS has a higher priority than USS" → "Smaller cell indices have a higher priority than larger cell indices" → "Non-XDD SS sets have a higher or lower priority than XDD SS sets" → "Smaller SS indices have a higher priority than larger SS indices". 【0376】 As a variation of Option 5-3 of the 7th embodiment, the following prioritization may be applied: "Cells not notified or set for XDD operation have a higher or lower priority than cells notified or set for XDD operation" → "CSS has a higher priority than USS" → "Smaller cell indexes have a higher priority than larger cell indexes" → "Non-XDD CSS / USS sets have a higher or lower priority than XDD CSS / USS sets" → "Smaller SS indexes have a higher priority than larger SS indexes". 【0377】 As option 5-4 of the seventh embodiment, the following prioritization may be applied: "CSS has a higher priority than USS" → "Cells that are not notified or set for XDD operation have a higher or lower priority than cells that are notified or set for XDD operation" → "Non-XDD SS sets have a higher or lower priority than XDD SS sets" → "Smaller cell indices have a higher priority than larger cell indices" → "Smaller SS indices have a higher priority than larger SS indices". 【0378】 As a variation of option 5-4 of the seventh embodiment, the following prioritization may be applied: "CSS has a higher priority than USS" → "Cells that are not notified or set for XDD operation have a higher or lower priority than cells that are notified or set for XDD operation" → "Non-XDD CSS / USS sets have a higher or lower priority than XDD CSS / USS sets" → "Smaller cell indices have a higher priority than larger cell indices" → "Smaller SS indices have a higher priority than larger SS indices". 【0379】 As option 5-5 of the seventh embodiment, the following prioritization may be applied: "CSS has a higher priority than USS" → "Cells that are not notified or set for XDD operation have a higher or lower priority than cells that are notified or set for XDD operation" → "Smaller cell indices have a higher priority than larger cell indices" → "Non-XDD SS sets have a higher or lower priority than XDD SS sets" → "Smaller SS indices have a higher priority than larger SS indices". 【0380】 As a variation of option 5-5 of the seventh embodiment, the following prioritization may be applied: "CSS has a higher priority than USS" → "Cells that are not notified or set for XDD operation have a higher or lower priority than cells that are notified or set for XDD operation" → "Smaller cell indices have a higher priority than larger cell indices" → "Non-XDD CSS / USS sets have a higher or lower priority than XDD CSS / USS sets" → "Smaller SS indices have a higher priority than larger SS indices". 【0381】 In Option 6 of the seventh embodiment, whether or not there is an XDD SS set or a non-XDD SS set, and whether or not there is an XDD PDCCH monitoring opportunity or a non-XDD PDCCH monitoring opportunity, may be considered in the determination. That is, Option 6 is a combination of Option 3 and Option 4. 【0382】 As option 6-1 of the seventh embodiment, the following prioritization may be applied: “Non-XDD SS sets have a higher or lower priority than XDD SS sets” → “Non-XDD PDCCH monitoring opportunities have a higher or lower priority than XDD PDCCH monitoring opportunities” → “CSS has a higher priority than USS” → “Smaller cell indices have a higher priority than larger cell indices” → “Smaller SS indices have a higher priority than larger SS indices.” 【0383】 As option 6-2 of the seventh embodiment, the following prioritization may be applied: “Non-XDD SS sets have a higher or lower priority than XDD SS sets” → “CSS has a higher priority than USS” → “Smaller cell indices have a higher priority than larger cell indices” → “Smaller SS indices have a higher priority than larger SS indices.” 【0384】 As option 6-3 of the seventh embodiment, the following prioritization may be applied: “Non-XDD SS sets have a higher or lower priority than XDD SS sets” → “CSS has a higher priority than USS” → “Smaller cell indices have a higher priority than larger cell indices” → “Non-XDD PDCCH monitoring opportunities have a higher or lower priority than XDD PDCCH monitoring opportunities” → “Smaller SS indices have a higher priority than larger SS indices.” 【0385】 As option 6-4 of the seventh embodiment, the following prioritization may be applied: “CSS has a higher priority than USS” → “Non-XDD SS sets have a higher or lower priority than XDD SS sets” → “Non-XDD PDCCH monitoring opportunities have a higher or lower priority than XDD PDCCH monitoring opportunities” → “Smaller cell indices have a higher priority than larger cell indices” → “Smaller SS indices have a higher priority than larger SS indices.” 【0386】 As a variation of Option 6-4 of Embodiment 7, the following prioritization may be applied: "CSS has a higher priority than USS" → "Non-XDD CSS / USS sets have a higher or lower priority than XDD CSS / USS sets" → "Non-XDD PDCCH monitoring opportunities have a higher or lower priority than XDD PDCCH monitoring opportunities" → "Smaller cell indices have a higher priority than larger cell indices" → "Smaller SS indices have a higher priority than larger SS indices". 【0387】 As option 6-5 of the seventh embodiment, the following prioritization may be applied: “CSS has a higher priority than USS” → “Non-XDD SS sets have a higher or lower priority than XDD SS sets” → “Smaller cell indices have a higher priority than larger cell indices” → “Non-XDD PDCCH monitoring opportunities have a higher or lower priority than XDD PDCCH monitoring opportunities” → “Smaller SS indices have a higher priority than larger SS indices.” 【0388】 As a variation of option 6-5 of the seventh embodiment, the following prioritization may be applied: "CSS has a higher priority than USS" → "Non-XDD CSS / USS sets have a higher or lower priority than XDD CSS / USS sets" → "Smaller cell indices have a higher priority than larger cell indices" → "Non-XDD PDCCH monitoring opportunities have a higher or lower priority than XDD PDCCH monitoring opportunities" → "Smaller SS indices have a higher priority than larger SS indices". 【0389】 As option 6-6 of the seventh embodiment, the following prioritization may be applied: “CSS has a higher priority than USS” → “Smaller cell indexes have a higher priority than larger cell indexes” → “Non-XDD SS sets have a higher or lower priority than XDD SS sets” → “Non-XDD PDCCH monitoring opportunities have a higher or lower priority than XDD PDCCH monitoring opportunities” → “Smaller SS indexes have a higher priority than larger SS indexes”. 【0390】 As a variation of option 6-6 of the seventh embodiment, the following prioritization may be applied: "CSS has a higher priority than USS" → "Smaller cell indexes have a higher priority than larger cell indexes" → "Non-XDD CSS / USS sets have a higher or lower priority than XDD CSS / USS sets" → "Non-XDD PDCCH monitoring opportunities have a higher or lower priority than XDD PDCCH monitoring opportunities" → "Smaller SS indexes have a higher priority than larger SS indexes". 【0391】 In Option 7 of the seventh embodiment, the determination may take into account whether there is a cell where XDD operation is notified or set, and whether there is an opportunity for XDD PDCCH monitoring or non-XDD PDCCH monitoring. That is, Option 7 is a combination of Option 2 and Option 4. 【0392】 As option 7-1 of the seventh embodiment, the following prioritization may be applied: "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 PDCCH monitoring opportunities have a higher or lower priority than XDD PDCCH monitoring opportunities" → "CSS has a higher priority than USS" → "Smaller cell indexes have a higher priority than larger cell indexes" → "Smaller SS indexes have a higher priority than larger SS indexes". 【0393】 As option 7-2 of the seventh embodiment, the following prioritization may be applied: "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" → "CSS has a higher priority than USS" → "Non-XDD PDCCH monitoring opportunities have a higher or lower priority than XDD PDCCH monitoring opportunities" → "Smaller cell indexes have a higher priority than larger cell indexes" → "Smaller SS indexes have a higher priority than larger SS indexes". 【0394】 As option 7-3 of the seventh embodiment, the following prioritization may be applied: "Cells not notified or configured for XDD operation have a higher or lower priority than cells notified or configured for XDD operation" → "CSS has a higher priority than USS" → "Smaller cell indexes have a higher priority than larger cell indexes" → "Non-XDD PDCCH monitoring opportunities have a higher or lower priority than XDD PDCCH monitoring opportunities" → "Smaller SS indexes have a higher priority than larger SS indexes". 【0395】 As option 7-4 of the seventh embodiment, the following prioritization may be applied: “CSS has a higher priority than USS” → “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 PDCCH monitoring opportunities have a higher or lower priority than XDD PDCCH monitoring opportunities” → “Smaller cell indexes have a higher priority than larger cell indexes” → “Smaller SS indexes have a higher priority than larger SS indexes.” 【0396】 As option 7-5 of the seventh embodiment, the following prioritization may be applied: "CSS has a higher priority than USS" → "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" → "Smaller cell indices have a higher priority than larger cell indices" → "Non-XDD PDCCH monitoring opportunities have a higher or lower priority than XDD PDCCH monitoring opportunities" → "Smaller SS indices have a higher priority than larger SS indices". 【0397】 In Option 8 of the seventh embodiment, the determination may take into account whether there is a cell where XDD operation is notified or set, 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. That is, Option 8 is a combination of Option 2, Option 3, and Option 4. 【0398】 As option 8-1 of the seventh embodiment, the following prioritization may be applied: "Cells not notified or configured for XDD operation have a higher or lower priority than cells notified or configured for XDD operation" → "Non-XDD SS sets have a higher or lower priority than XDD SS sets" → "Non-XDD PDCCH monitoring opportunities have a higher or lower priority than XDD PDCCH monitoring opportunities" → "CSS has a higher priority than USS" → "Smaller cell indexes have a higher priority than larger cell indexes" → "Smaller SS indexes have a higher priority than larger SS indexes". 【0399】 As option 8-2 of the seventh embodiment, the following prioritization may be applied: "Cells not notified or configured for XDD operation have a higher or lower priority than cells notified or configured for XDD operation" → "Non-XDD SS sets have a higher or lower priority than XDD SS sets" → "CSS has a higher priority than USS" → "Smaller cell indexes have a higher priority than larger cell indexes" → "Smaller SS indexes have a higher priority than larger SS indexes". 【0400】 As option 8-3 of the seventh embodiment, the following prioritization may be applied: "Cells not notified or configured for XDD operation have a higher or lower priority than cells notified or configured for XDD operation" → "Non-XDD SS sets have a higher or lower priority than XDD SS sets" → "CSS has a higher priority than USS" → "Smaller cell indexes have a higher priority than larger cell indexes" → "Non-XDD PDCCH monitoring opportunities have a higher or lower priority than XDD PDCCH monitoring opportunities" → "Smaller SS indexes have a higher priority than larger SS indexes". 【0401】 As option 8-4 of the seventh embodiment, the following prioritization may be applied: “Cells not notified or configured for XDD operation have a higher or lower priority than cells notified or configured for XDD operation” → “CSS has a higher priority than USS” → “Non-XDD SS sets have a higher or lower priority than XDD SS sets” → “Non-XDD PDCCH monitoring opportunities have a higher or lower priority than XDD PDCCH monitoring opportunities” → “Smaller cell indices have a higher priority than larger cell indices” → “Smaller SS indices have a higher priority than larger SS indices”. 【0402】 As option 8-5 of the seventh embodiment, the following prioritization may be applied: “CSS has a higher priority than USS” → “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” → “Smaller cell indices have a higher priority than larger cell indices” → “Non-XDD SS sets have a higher or lower priority than XDD SS sets” → “Non-XDD PDCCH monitoring opportunities have a higher or lower priority than XDD PDCCH monitoring opportunities” → “Smaller SS indices have a higher priority than larger SS indices”. 【0403】 As option 8-6 of the seventh embodiment, the following prioritization may be applied: "Cells not notified or configured for XDD operation have a higher or lower priority than cells notified or configured for XDD operation" → "CSS has a higher priority than USS" → "Non-XDD SS sets have a higher or lower priority than XDD SS sets" → "Smaller cell indices have a higher priority than larger cell indices" → "Non-XDD PDCCH monitoring opportunities have a higher or lower priority than XDD PDCCH monitoring opportunities" → "Smaller SS indices have a higher priority than larger SS indices". 【0404】 As option 8-7 of the seventh embodiment, the following prioritization may be applied: “CSS has a higher priority than USS” → “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 sets have a higher or lower priority than XDD SS sets” → “Smaller cell indices have a higher priority than larger cell indices” → “Non-XDD PDCCH monitoring opportunities have a higher or lower priority than XDD PDCCH monitoring opportunities” → “Smaller SS indices have a higher priority than larger SS indices”. 【0405】 As option 8-8 of the seventh embodiment, the following prioritization may be applied: "Cells not notified or configured for XDD operation have a higher or lower priority than cells notified or configured for XDD operation" → "CSS has a higher priority than USS" → "Smaller cell indexes have a higher priority than larger cell indexes" → "Non-XDD SS sets have a higher or lower priority than XDD SS sets" → "Non-XDD PDCCH monitoring opportunities have a higher or lower priority than XDD PDCCH monitoring opportunities" → "Smaller SS indexes have a higher priority than larger SS indexes". 【0406】 As options 8-9 of the seventh embodiment, the following prioritization may be applied: "CSS has a higher priority than USS" → "Cells that are not notified or configured for XDD operations have a higher or lower priority than cells that are notified or configured for XDD operations" → "Smaller cell indices have a higher priority than larger cell indices" → "Non-XDD SS sets have a higher or lower priority than XDD SS sets" → "Non-XDD PDCCH monitoring opportunities have a higher or lower priority than XDD PDCCH monitoring opportunities" → "Smaller SS indices have a higher priority than larger SS indices". 【0407】 Thus, according to the seventh embodiment, the UE may select a PDCCH monitoring beam in the XDD time unit in which PDCCH monitoring is set and perform PDCCH monitoring on the selected PDCCH monitoring beam. Correspondingly, the base station may control the PDCCH monitoring beam in the XDD time unit in which PDCCH monitoring is set and transmit control information by the PDCCH monitoring beam. 【0408】 Specifically, the UE may select PDCCH monitoring beams according to a prioritization order. 【0409】 Furthermore, PDCCH monitoring beams may be selected based on a first priority between the Common Search Space (CSS) and the User-Specific Search Space (USS), a second priority between cell indexes, and a third priority between search space indexes (SS indexes). 【0410】 Furthermore, PDCCH monitoring beams may be selected based on one or more of the following: a fourth prioritization between cells where XDD operation is configured or notified and cells where XDD operation is not configured or notified; a fifth prioritization between non-XDD search space (non-XDD SS) sets and XDD search space (XDD SS) sets; and a sixth prioritization between non-XDD PDCCH monitoring opportunities and XDD PDCCH monitoring opportunities. 【0411】 The settings or notifications described above may be transmitted based, for example, on at least one of the RRC (Radio Resource Control) information element, DCI (Downlink Control Information), and MAC CE (Medium Access Control Control Element). Furthermore, this disclosure is not limited to PDCCH monitoring and may apply to other types of control signals transmitted from a base station to a UE or other base station (e.g., an IAB node). 【0412】 To implement the XDD operation described above, the UE may transmit UE capability information regarding the XDD operation to the base station, and the base station may notify or set the XDD operation to the UE based on the received UE capability information. Specifically, the UE capability information may specify whether the cell is notified or set to 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, thereby supporting the determination of TCI states for PDCCH monitoring that include or overlap PDCCH monitoring opportunities. The UE may transmit UE capability information to the base station regarding whether the cell is notified or set to 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, thereby supporting the determination of TCI states for PDCCH monitoring that include or overlap PDCCH monitoring opportunities. 【0413】 According to the seventh embodiment, when an XDD operation is notified, set up, or applied to a cell where PDCCH monitoring is configured, UE operation with respect to the PDCCH monitoring beam can be defined. 【0414】 For each of the embodiments described above, the applicable embodiments, options, and / or operations may be notified or set by higher-layer parameters, notified or reported by the UE as UE capability information, specified in the specification, or determined by the configuration of the higher-layer parameters and the reported UE capability information. 【0415】 <Hardware Configuration> The block diagrams used in the description of the above embodiments show functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may also be realized by combining the above one device or the above multiple devices with software. 【0416】 Functions include, but are not limited to, judgment, decision, judgment, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, assumption, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission is called a transmitting unit or transmitter. As mentioned above, the method of implementation is not particularly limited. 【0417】 For example, a base station, user terminal, etc. in one embodiment of the present disclosure may function as a computer that processes the wireless communication method of the present disclosure. Figure 52 is a diagram showing an example of the hardware configuration of a base station and user terminal according to one embodiment of the present disclosure. The base station 10 and user terminal 20 described above may be physically configured as a computer device including a processor 1001, memory 1002, storage 1003, communication device 1004, input device 1005, output device 1006, bus 1007, etc. 【0418】 In the following explanation, the term "device" can be replaced with "circuit," "device," "unit," etc. The hardware configuration of the base station 10 and the user terminal 20 may include one or more of the devices shown in Figure 52, or it may be configured without some of the devices. 【0419】 Each function in the base station 10 and the user terminal 20 is realized by loading predetermined software (programs) onto hardware such as the processor 1001 and memory 1002, which allows the processor 1001 to perform calculations and control communication by the communication device 1004, or control at least one of reading and writing data to the memory 1002 and storage 1003. 【0420】 The processor 1001 controls the entire computer, for example, by running the operating system. The processor 1001 may be composed of a central processing unit (CPU) that includes interfaces with peripheral devices, control units, arithmetic units, registers, etc. For example, the baseband signal processing unit 104 and call processing unit 105 mentioned above may be implemented by the processor 1001. 【0421】 Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. For example, the control unit 401 of the user terminal 20 may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and other functional blocks may be implemented similarly. The above-described various processes have been explained as being executed by one processor 1001, but they may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The program may also be transmitted from the network via a telecommunications line. 【0422】 Memory 1002 is a computer-readable recording medium and may consist of at least one of the following: ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. Memory 1002 may also be called a register, cache, main memory, etc. Memory 1002 can store executable programs (program code), software modules, etc., for carrying out a wireless communication method according to one embodiment of the present disclosure. 【0423】 Storage 1003 is a computer-readable recording medium and may consist of at least one of the following: an optical disc such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disc, a digital multipurpose disc, a Blu-ray® disc), a smart card, flash memory (e.g., a card, a stick, a key drive), a floppy® disk, a magnetic strip, etc. Storage 1003 may also be called an auxiliary storage device. The above-mentioned storage medium may be, for example, a database, server, or other suitable medium including at least one of memory 1002 and storage 1003. 【0424】 The communication device 1004 is hardware (transmitting / receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc. The communication device 1004 may be configured to include a high-frequency switch, duplexer, filter, frequency synthesizer, etc., in order to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the above-mentioned transmitting / receiving antenna 101, amplifier section 102, transmitting / receiving section 103, transmission path interface 106, etc., may be implemented by the communication device 1004. The transmitting / receiving section 103 may be implemented in physically or logically separated form, consisting of a transmitting section 103a and a receiving section 103b. 【0425】 The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, LED lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel). 【0426】 Furthermore, each device, such as the processor 1001 and memory 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or different buses may be configured for each device. 【0427】 Furthermore, the base station 10 and the user terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), and an FPGA (Field Programmable Gate Array), and some or all of each functional block may be realized by such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components. 【0428】 Information notification is not limited to the embodiments described herein and may be carried out by other means. For example, information notification may be carried out by physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), upper layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, broadcast information (MIB (Master Information Block), SIB (System Information Block))), other signals, or combinations thereof. RRC signaling may also be called RRC messages, and may be, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc. 【0429】 Each aspect / embodiment described in this disclosure includes LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (where x is, for example, an integer or decimal)), FRA (Future Radio Access), NR (new Radio), New radio access (NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), and IEEE This may apply to at least one system utilizing 802.20, UWB (Ultra-WideBand), Bluetooth®, or other appropriate systems, and to next-generation systems extended, modified, created, or defined based thereon. It may also apply to a combination of multiple systems (for example, a combination of at least one of LTE and LTE-A with 5G). 【0430】 The processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described herein may be reordered, provided they are consistent with each other. For example, the methods described herein present various step elements in an exemplary order and are not limited to that specific order. 【0431】 The specific operations described in this disclosure as being performed by a base station may, in some cases, be performed by its upper node. In a network consisting of one or more network nodes having a base station, it is clear that various operations performed for communication with a terminal can be performed by the base station and at least one other network node (for example, an MME or S-GW, but not limited to these). Although the above example illustrates a case where there is one other network node besides the base station, it may also be a combination of multiple other network nodes (for example, an MME and an S-GW). 【0432】 Information, etc. (see the "Information, Signals" section) can be output from a higher layer (or lower layer) to a lower layer (or higher layer). Input and output may also occur via multiple network nodes. 【0433】 Input and output information may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information may be overwritten, updated, or appended to. Output information may be deleted. Input information may be transmitted to other devices. 【0434】 The determination may be made by a value represented by 1 bit (0 or 1), by a boolean value (true or false), or by a numerical comparison (for example, a comparison with a predetermined value). 【0435】 Each aspect / embodiment described herein may be used individually, in combination, or switched between as needed during implementation. Furthermore, notification of specific information (e.g., notification that "X is") is not limited to explicit notification, but may also be implicit (e.g., by not providing such notification). 【0436】 Although the present disclosure has been described in detail above, it will be clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the intent and scope of the present disclosure as defined by the claims. Therefore, the descriptions in the present disclosure are illustrative and not intended to be restrictive in any way. 【0437】 Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name. 【0438】 Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technology (such as coaxial cable, fiber optic cable, twisted pair, or digital subscriber line (DSL)) and wireless technology (such as infrared or microwave), then at least one of these wired and wireless technologies is included in the definition of a transmission medium. 【0439】 The information, signals, etc. described in this disclosure may be represented using any of the various different techniques. For example, the data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof. 【0440】 In addition, terms used in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of the channel and symbol may be a signal (signaling). Also, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, cell, frequency carrier, etc. 【0441】 The terms “system” and “network” as used in this disclosure are interchangeable. 【0442】 Furthermore, the information, parameters, etc., described in this disclosure may be expressed using absolute values, relative values ​​from a given value, or other corresponding information. For example, wireless resources may be indicated by an index. 【0443】 The names used for the parameters described above are not restrictive in any way. Furthermore, the formulas and other expressions using these parameters may differ from those expressly disclosed in this disclosure. Various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, and therefore, the various names assigned to these various channels and information elements are not restrictive in any way. 【0444】 In this disclosure, terms such as "base station (BS)", "wireless base station", "fixed station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "access point", "transmission point", "reception point", "transmission / reception point", "cell", "sector", "cell group", "carrier", and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell. 【0445】 A base station can accommodate one or more (e.g., three) cells. If a base station accommodates multiple cells, the entire coverage area of ​​the base station can be divided into several smaller areas, each of which may also be provided with communication services by a base station subsystem (e.g., a Remote Radio Head (RRH)). The terms “cell” or “sector” refer to part or all of the coverage area of ​​at least one of the base station and / or base station subsystems that provide communication services in that coverage. 【0446】 In this disclosure, the transmission of information by a base station to a terminal may be interpreted as the base station instructing the terminal to perform information-based control or operation. 【0447】 In this disclosure, terms such as "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" may be used interchangeably. 【0448】 A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or several other appropriate terms. 【0449】 At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may also be a device mounted on a mobile body, the mobile body itself, etc. The mobile body refers to a movable object, and its speed of movement is arbitrary. This also includes the case when the mobile body is stationary. The mobile body includes, but is not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and items mounted on them. The mobile body may also be a mobile body that moves autonomously based on operation commands. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). Furthermore, at least one of the base station and the mobile station may include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor. 【0450】 Furthermore, the term "base station" in this disclosure may be interpreted as "user terminal." For example, the various aspects / embodiments of this disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple user terminals (which may be called, for example, D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.). In this case, the user terminal 20 may have the functions that the base station 10 has. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, uplink channel, downlink channel, etc., may be interpreted as side channel. 【0451】 Similarly, the term "user terminal" in this disclosure may be replaced with "base station." In this case, the base station 10 may be configured to have the same functions as the user terminal 20 described above. 【0452】 Figure 53 shows an example of the configuration of vehicle 1. As shown in Figure 53, vehicle 1 comprises a drive unit 2, a steering unit 3, an accelerator pedal 4, a brake pedal 5, a shift lever 6, left and right front wheels 7, left and right rear wheels 8, an axle 9, an electronic control unit 10, various sensors 21-29, an information service unit 12, and a communication module 13. 【0453】 The drive unit 2 is composed of, for example, an engine, a motor, or a hybrid of an engine and a motor. 【0454】 The steering unit 3 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel performed by the user. 【0455】 The electronic control unit 10 consists of a microprocessor 31, memory (ROM, RAM) 32, and communication ports (IO ports) 33. Signals from various sensors 21-27 installed in the vehicle are input to the electronic control unit 10. The electronic control unit 10 may also be called an ECU (Electronic Control Unit). 【0456】 Signals from various sensors 21 to 28 include current signals from the current sensor 21 which senses the motor current, front and rear wheel rotation speed signals obtained by the rotation speed sensor 22, front and rear wheel air pressure signals obtained by the air pressure sensor 23, vehicle speed signals obtained by the vehicle speed sensor 24, acceleration signals obtained by the acceleration sensor 25, accelerator pedal depression amount signals obtained by the accelerator pedal sensor 29, brake pedal depression amount signals obtained by the brake pedal sensor 26, shift lever operation signals obtained by the shift lever sensor 27, and detection signals obtained by the object detection sensor 28 for detecting obstacles, vehicles, pedestrians, etc. 【0457】 The Information Service Unit 12 consists of various devices for providing (outputting) various types of information such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, television, and radio, and one or more ECUs that control these devices. The Information Service Unit 12 uses information acquired from external devices via a communication module 13, etc., to provide various multimedia information and multimedia services to the occupants of the vehicle 1. 【0458】 The information service unit 12 may include input devices that accept input from the outside (e.g., keyboard, mouse, microphone, switch, button, sensor, touch panel, etc.) or output devices that perform output to the outside (e.g., display, speaker, LED lamp, touch panel, etc.). 【0459】 The driver assistance system unit 30 consists of various devices that provide functions to prevent accidents or reduce the driver's workload, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System)), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. The driver assistance system unit 30 also transmits and receives various information via the communication module 13 to realize driver assistance functions or autonomous driving functions. 【0460】 The communication module 13 can communicate with the microprocessor 31 and components of the vehicle 1 via its communication port. For example, the communication module 13 sends and receives data via its communication port 33 between the drive unit 2, steering unit 3, accelerator pedal 4, brake pedal 5, shift lever 6, left and right front wheels 7, left and right rear wheels 8, axle 9, the microprocessor 31 and memory (ROM, RAM) 32 in the electronic control unit 10, and sensors 21-28 provided in the vehicle 1. 【0461】 The communication module 13 is a communication device that can be controlled by the microprocessor 31 of the electronic control unit 10 and can communicate with external devices. For example, it can send and receive various types of information with external devices via wireless communication. The communication module 13 may be located either inside or outside the electronic control unit 10. The external device may be, for example, a base station or a mobile station. 【0462】 The communication module 13 may transmit at least one of the following to an external device via wireless communication: signals from the various sensors 21-28 input to the electronic control unit 10, information obtained based on those signals, and information based on input from an external source (user) obtained via the information service unit 12. The electronic control unit 10, the various sensors 21-28, the information service unit 12, etc., may also be called input units that accept input. For example, the PUSCH transmitted by the communication module 13 may include information based on the above input. 【0463】 The communication module 13 receives various information (traffic information, signal information, vehicle-to-vehicle information, etc.) transmitted from an external device and displays it on the information service unit 12 installed in the vehicle. The information service unit 12 may also be called an output unit, which outputs information (for example, it outputs information to devices such as displays and speakers based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 13). 【0464】 Furthermore, the communication module 13 stores various information received from external devices in a memory 32 that can be used by the microprocessor 31. Based on the information stored in the memory 32, the microprocessor 31 may control the drive unit 2, steering unit 3, accelerator pedal 4, brake pedal 5, shift lever 6, left and right front wheels 7, left and right rear wheels 8, axle 9, sensors 21-28, etc., which are provided in the vehicle 1. 【0465】 (Summary of the embodiments) As described above, according to one aspect of the present disclosure, a terminal is provided having a receiving unit that receives notifications or settings related to XDD (Cross Division Duplex) operation for a wireless resource, and a control unit that controls uplink transmission or downlink reception on the wireless resource in accordance with the notifications or settings related to the XDD operation. 【0466】 The above configuration makes it possible to limit the wireless resources (e.g., cells, BWP, etc.) on which XDD operation can be configured. 【0467】 In one embodiment, the receiving unit receives a notification or setting regarding XDD operation on a frequency resource basis for a given time unit on a bandwidth portion. The notification or setting regarding XDD operation on a frequency resource basis may notify or set a first frequency resource in the bandwidth portion for uplink transmission or downlink reception, and a second frequency resource in the bandwidth portion for downlink reception or uplink transmission. According to this embodiment, it becomes possible to set XDD operation on a frequency resource basis. 【0468】 In one embodiment, the receiving unit receives a notification or setting regarding terminal-specific XDD operation for a time unit on a bandwidth portion. The notification or setting regarding terminal-specific XDD operation may be used to notify or set the time unit to a first terminal for uplink transmission or downlink reception, and to notify or set the time unit to a second terminal for downlink reception or uplink transmission. This embodiment makes it possible to set XDD operation on a terminal-by-terminal basis. 【0469】 In one embodiment, the receiving unit may receive a notification or setting indicating the bandwidth portion of a cell in which XDD operation is set, or the bandwidth portion of the cell for XDD operation. According to this embodiment, the BWP in which XDD operation is set can be specified. 【0470】 Furthermore, according to one aspect of this disclosure, a base station is provided having a transmitting unit that transmits notifications or settings related to XDD (Cross Division Duplex) operation for a radio resource, and a control unit that controls uplink transmission or downlink reception on the radio resource in accordance with the notifications or settings related to XDD operation. 【0471】 The above configuration makes it possible to limit the wireless resources (e.g., cells, BWP, etc.) on which XDD operation can be configured. 【0472】 Furthermore, according to one aspect of the present disclosure, a wireless communication method is provided that is performed by a terminal, comprising receiving a notification or setting regarding XDD (Cross Division Duplex) operation for a wireless resource, and controlling uplink transmission or downlink reception on the wireless resource in accordance with the notification or setting regarding XDD operation. 【0473】 The above configuration makes it possible to limit the wireless resources (e.g., cells, BWP, etc.) on which XDD operation can be configured. 【0474】 Furthermore, according to one aspect of this disclosure, a terminal is provided having 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. 【0475】 According to the above configuration, if XDD operation can be configured for the PDCCH monitoring resource, it becomes possible to properly implement PDCCH monitoring in XDD operation. 【0476】 In one embodiment, the PDCCH monitoring setting may include a first PDCCH monitoring setting for non-XDD time units and a second PDCCH monitoring setting for XDD time units. According to this embodiment, appropriate PDCCH monitoring settings can be set for both XDD operation and non-XDD operation. 【0477】 In one embodiment, the first PDCCH monitoring setting includes one or more search space set settings, CORESET (COntrol REsource SET) settings, frequency domain resource settings, and frequency monitoring position settings for the non-XDD time unit, and the second PDCCH monitoring setting may include one or more search space set settings, one or more CORESET settings, one or more frequency domain resource settings, and one or more frequency monitoring position settings for the XDD time unit. According to this embodiment, appropriate PDCCH monitoring settings can be set for both XDD operation and non-XDD operation. 【0478】 In one embodiment, the PDCCH monitoring setting includes a PDCCH search space setting, and the control unit may control the PDCCH monitoring depending on whether the PDCCH monitoring opportunity indicated by the PDCCH search space setting overlaps with the XDD time unit. According to this embodiment, PDCCH monitoring can be appropriately implemented depending on whether the PDCCH monitoring opportunity indicated by the PDCCH search space setting overlaps with the XDD time unit. 【0479】 Furthermore, according to one aspect of this disclosure, a base station is provided having a setting unit for setting PDCCH monitoring settings for XDD (Cross Division Duplex) operation, and a transmitting unit for transmitting the PDCCH monitoring settings. 【0480】 According to the above configuration, if XDD operation can be configured for the PDCCH monitoring resource, it becomes possible to properly implement PDCCH monitoring in XDD operation. 【0481】 Furthermore, according to one aspect of the present disclosure, a wireless communication method is provided that is performed by a terminal, comprising receiving PDCCH monitoring settings for XDD (Cross Division Duplex) operation and controlling PDCCH monitoring in accordance with the PDCCH monitoring settings. 【0482】 According to the above configuration, if XDD operation can be configured for the PDCCH monitoring resource, it becomes possible to properly implement PDCCH monitoring in XDD operation. 【0483】 Furthermore, according to one aspect of the present disclosure, a terminal is provided having a receiving unit that receives PDCCH monitoring capability for XDD (Cross Division Duplex) operation on a wireless resource, and a control unit that controls PDCCH monitoring according to the PDCCH monitoring capability. 【0484】 According to the above configuration, if XDD operation can be configured for the PDCCH monitoring resource, it becomes possible to appropriately implement PDCCH monitoring in XDD operation according to the PDCCH monitoring capability. 【0485】 In one embodiment, the PDCCH monitoring capability may be set commonly for both XDD operation and non-XDD operation. According to this embodiment, it becomes possible to appropriately implement PDCCH monitoring in XDD operation according to the PDCCH monitoring capability. 【0486】 In one embodiment, the PDCCH monitoring capability may be set separately for XDD operation and non-XDD operation. According to this embodiment, it becomes possible to appropriately implement PDCCH monitoring in XDD operation according to the PDCCH monitoring capability. 【0487】 In one embodiment, the 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 together. According to this embodiment, it becomes possible to appropriately realize PDCCH monitoring in XDD operation according to the PDCCH monitoring capability. 【0488】 Furthermore, according to one aspect of the present disclosure, a base station is provided having a control unit that sets PDCCH monitoring capability for XDD (Cross Division Duplex) operation with respect to a radio resource, and a transmission unit that transmits the PDCCH monitoring capability. 【0489】 According to the above configuration, if XDD operation can be configured for the PDCCH monitoring resource, it becomes possible to appropriately implement PDCCH monitoring in XDD operation according to the PDCCH monitoring capability. 【0490】 Furthermore, according to one aspect of the present disclosure, a wireless communication method is provided that is performed by a terminal, comprising receiving PDCCH monitoring capability for XDD (Cross Division Duplex) operation on a wireless resource, and controlling PDCCH monitoring in accordance with the PDCCH monitoring capability. 【0491】 According to the above configuration, if XDD operation can be configured for the PDCCH monitoring resource, it becomes possible to appropriately implement PDCCH monitoring in XDD operation according to the PDCCH monitoring capability. 【0492】 Furthermore, according to one aspect of the present disclosure, a terminal is provided having a control unit that controls PDCCH overbooking in XDD (Cross Division Duplex) time units in which PDCCH monitoring is set, and a receiving unit that performs PDCCH monitoring at PDCCH monitoring opportunities selected in the controlled PDCCH overbooking. 【0493】 According to the above configuration, if XDD operation can be configured for the PDCCH monitoring resource, it is possible to appropriately select a PDCCH monitoring opportunity in the event of PDCCH overbooking and perform PDCCH monitoring at the selected PDCCH monitoring opportunity. 【0494】 In one embodiment, the control unit may select PDCCH monitoring opportunities according to prioritization. According to this embodiment, PDCCH monitoring opportunities can be appropriately selected according to prioritization. 【0495】 In one embodiment, the PDCCH monitoring opportunities may be selected based on a first prioritization between common search spaces and user-specific search spaces, a second prioritization between non-XDD search space sets and XDD search space sets, and a third prioritization between search space indices. According to this embodiment, PDCCH monitoring opportunities can be appropriately selected according to the prioritization. 【0496】 In one embodiment, the PDCCH monitoring opportunity may be selected based on a fourth prioritization between non-XDD PDCCH monitoring opportunities and XDD PDCCH monitoring opportunities. According to this embodiment, the PDCCH monitoring opportunity can be appropriately selected according to the prioritization. 【0497】 Furthermore, according to one aspect of the present disclosure, a base station is provided that includes a control unit that sets up PDCCH monitoring opportunities that are overbooked in an XDD (Cross Division Duplex) time unit in which PDCCH monitoring is set, and a transmission unit that transmits control information in the PDCCH monitoring opportunity. 【0498】 According to the above configuration, if XDD operation can be configured for the PDCCH monitoring resource, it is possible to appropriately select a PDCCH monitoring opportunity in the event of PDCCH overbooking and perform PDCCH monitoring at the selected PDCCH monitoring opportunity. 【0499】 Furthermore, according to one aspect of the present disclosure, there is a wireless communication method performed by a terminal that includes controlling PDCCH overbooking in XDD (Cross Division Duplex) time units in which PDCCH monitoring is set, and performing PDCCH monitoring at selected PDCCH monitoring opportunities in the controlled PDCCH overbooking. 【0500】 According to the above configuration, if XDD operation can be configured for the PDCCH monitoring resource, it is possible to appropriately select a PDCCH monitoring opportunity in the event of PDCCH overbooking and perform PDCCH monitoring at the selected PDCCH monitoring opportunity. 【0501】 Furthermore, according to one aspect of the present disclosure, a terminal is provided having a control unit that selects a PDCCH monitoring beam in an XDD (Cross Division Duplex) time unit in which PDCCH monitoring is set, and a receiving unit that performs PDCCH monitoring on the selected PDCCH monitoring beam. 【0502】 According to the above configuration, if XDD operation can be configured for the PDCCH monitoring resource, the PDCCH monitoring beam can be appropriately selected, and PDCCH monitoring can be performed using the selected PDCCH monitoring beam. 【0503】 In one embodiment, the control unit may select the PDCCH monitoring beam according to a priority order. According to this embodiment, the PDCCH monitoring beam can be appropriately selected. 【0504】 In one embodiment, the PDCCH monitoring beam may be selected based on a first prioritization between a common search space and a user-specific search space, a second prioritization between cell indices, and a third prioritization between search space indices. According to this embodiment, the PDCCH monitoring beam can be appropriately selected. 【0505】 In one embodiment, the PDCCH monitoring beam may be selected based on one or more of the following: a fourth prioritization between cells where XDD operation is set or notified and cells where XDD operation is not set or notified; a fifth prioritization between non-XDD search space sets and XDD search space sets; and a sixth prioritization between non-XDD PDCCH monitoring opportunities and XDD PDCCH monitoring opportunities. According to this embodiment, the PDCCH monitoring beam can be appropriately selected. 【0506】 Furthermore, according to one aspect of the present disclosure, a base station is provided that includes a control unit that controls a PDCCH monitoring beam in XDD (Cross Division Duplex) time units in which PDCCH monitoring is set, and a transmission unit that transmits control information using the PDCCH monitoring beam. 【0507】 According to the above configuration, if XDD operation can be configured for the PDCCH monitoring resource, the PDCCH monitoring beam can be appropriately selected, and PDCCH monitoring can be performed using the selected PDCCH monitoring beam. 【0508】 Furthermore, according to one aspect of the present disclosure, a wireless communication method is provided that is performed by a terminal, comprising: selecting a PDCCH monitoring beam in an XDD (Cross Division Duplex) time unit in which PDCCH monitoring is set; and performing PDCCH monitoring on the selected PDCCH monitoring beam. 【0509】 According to the above configuration, if XDD operation can be configured for the PDCCH monitoring resource, the PDCCH monitoring beam can be appropriately selected, and PDCCH monitoring can be performed using the selected PDCCH monitoring beam. 【0510】 (Supplement to the embodiment) As used in this disclosure, the terms “determining” and “determining” may encompass a wide variety of actions. “Determining” may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiry (e.g., searching in a table, database, or other data structure), and ascertaining. “Determining” may also include, for example, receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, and accessing (e.g., accessing data in memory). Furthermore, "judgment" and "decision" can include considering something as having been "judged" or "decided" after resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment" and "decision" can include considering something as having been "judged" or "decided" after some action. Also, "judgment (decision)" can be reinterpreted as "assuming," "expecting," or "considering." 【0511】 The terms “connected,” “coupled,” or any variation thereof, mean any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be reinterpreted as “access.” As used in this disclosure, two elements may be considered to be “connected” or “coupled” with each other using at least one of one or more wires, cables, and printed electrical connections, and, in some non-limiting and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, and optical (both visible and invisible) domain. 【0512】 The reference signal can also be abbreviated as RS (Reference Signal), and may be called a pilot depending on the applicable standard. 【0513】 In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on." 【0514】 Any reference to elements using the designations “first,” “second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, references to the first and second elements do not imply that only two elements may be employed, or that the first element must precede the second element in any way. 【0515】 In the configuration of each of the above devices, "means" may be replaced with "part," "circuit," "device," etc. 【0516】 Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR. 【0517】 A wireless frame may consist of one or more frames in the time domain. Each of these frames in the time domain may be called a subframe. A subframe may further consist of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology. 【0518】 Numerology may be communication parameters applied to at least one of the transmission and reception of a signal or channel. Numerology may include, for example, at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processes performed by the transceiver in the frequency domain, and specific windowing processes performed by the transceiver in the time domain. 【0519】 A slot may consist of one or more symbols in the time domain (such as OFDM (Orthogonal Frequency Division Multiplexing) symbols, SC-FDMA (Single Carrier Frequency Division Multiple Access) symbols, etc.). A slot may also be a time unit based on neurology. 【0520】 A slot may include multiple minislots. Each minislot may consist of one or more symbols in the time domain. Minislots may also be called subslots. Minislots may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (or PUSCH) mapping type B. 【0521】 Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Different names may be used for each of these terms. 【0522】 For example, one subframe may be called a Transmission Time Interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one mini-slot may be called a TTI. In other words, at least one of a subframe and a TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, mini-slot, etc., instead of a subframe. 【0523】 Here, TTI refers to, for example, the smallest unit of time for scheduling in wireless communication. For example, in an LTE system, the base station schedules each user terminal to allocate wireless resources (such as the frequency bandwidth and transmission power available to each user terminal) in TTI units. However, the definition of TTI is not limited to this. 【0524】 TTI may be a transmission time unit for channel-encoded data packets (transport blocks), code blocks, code words, etc., or it may be a processing unit for scheduling, link adaptation, etc. Given a TTI, the actual time interval (e.g., number of symbols) to which the transport block, code block, code word, etc. are mapped may be shorter than the given TTI. 【0525】 Furthermore, if one slot or one mini-slot is referred to as TTI, then one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute the minimum time unit of scheduling. In addition, the number of slots (number of mini-slots) that constitute the minimum time unit of scheduling may be controlled. 【0526】 A TTI with a time length of 1ms may also be called a normal TTI, long TTI, normal subframe, long subframe, slot, etc. A TTI shorter than a normal TTI may also be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, mini slot, sub slot, slot, etc. 【0527】 Furthermore, long TTIs (e.g., normal TTIs, subframes, etc.) may be interpreted as TTIs with a time length exceeding 1 ms, and short TTIs (e.g., shortened TTIs, etc.) may be interpreted as TTIs with a TTI length less than that of a long TTI but 1 ms or more. 【0528】 A resource block (RB) is a resource allocation unit in the time domain and frequency domain, and in the frequency domain, it may contain one or more consecutive subcarriers. The number of subcarriers in an RB may be the same regardless of the neurology, for example, 12. The number of subcarriers in an RB may be determined based on the neurology. 【0529】 Furthermore, the time domain of RB may contain one or more symbols and may be the length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc., may each consist of one or more resource blocks. 【0530】 One or more RBs may also be called a Physical RB (PRB), Sub-Carrier Group (SCG), Resource Element Group (REG), PRB pair, RB pair, etc. 【0531】 Furthermore, a resource block may consist of one or more resource elements (REs). For example, one RE may be a radio resource area comprising one subcarrier and one symbol. 【0532】 A Bandwidth Part (BWP), also known as a partial bandwidth, may represent a subset of consecutive common resource blocks (RBs) for a given neurology in a given carrier. Here, the common RBs may be identified by an index of the RBs relative to the carrier's common reference point. A PRB may be defined and numbered within a BWP. 【0533】 A BWP may include BWPs for UL (UL BWP) and BWPs for DL ​​(DL BWP). One or more BWPs may be configured within a single carrier for a UE. 【0534】 At least one of the configured BWPs may be active, and the UE does not need to assume that it will send or receive a given signal / channel outside of the active BWP. In this disclosure, terms such as "cell" and "carrier" may be read as "BWP". 【0535】 The structures described above, such as wireless frames, subframes, slots, minislots, and symbols, are merely illustrative. For example, the number of subframes included in a wireless frame, the number of slots per subframe or wireless frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, and the number of symbols, symbol length, and cyclic prefix (CP) length within a TTI can be varied in various ways. 【0536】 The term "maximum transmit power" as used in this disclosure may mean the maximum value of the transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power. 【0537】 In this disclosure, if articles are added through translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural. 【0538】 In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combine" may be interpreted similarly to "different." [Explanation of symbols] 【0539】 10 Wireless communication systems 100 base stations (gNB) 200 terminals (UE)

Claims

[Claim 1] A transmitting unit that transmits terminal capability information relating to XDD (Cross Division Duplex) operation, which is a division duplex method combining TDD (Time Division Duplex) and FDD (Frequency Division Duplex), A receiving unit that receives information indicating the PDCCH monitoring capability related to XDD operation set based on the terminal capability information, A control unit that performs PDCCH monitoring in one of the following ways, according to the PDCCH monitoring capability: slot-level PDCCH monitoring, span-level PDCCH monitoring, or multi-slot PDCCH monitoring. A terminal. [Claim 2] The terminal according to claim 1, wherein the PDCCH monitoring capability is set commonly for both XDD operation and TDD operation. [Claim 3] The terminal according to claim 1, wherein the PDCCH monitoring capability is set separately for XDD operation and TDD operation. [Claim 4] The terminal according to claim 1, wherein the control unit counts the PDCCH candidates or non-overlapping control channel elements in XDD operation and the PDCCH candidates or non-overlapping control channel elements in non-XDD operation separately or together. [Claim 5] A receiving unit that receives terminal capability information relating to XDD (Cross Division Duplex) operation, which is a division duplex method combining TDD (Time Division Duplex) and FDD (Frequency Division Duplex), A control unit that sets the PDCCH monitoring capability for XDD operation based on the terminal capability information, A transmitting unit that transmits information indicating the PDCCH monitoring capability, It has, The PDCCH monitoring capability is one of the following: slot-level PDCCH monitoring capability, span-level PDCCH monitoring capability, or multi-slot PDCCH monitoring capability. Base station. [Claim 6] Transmitting terminal capability information related to XDD (Cross Division Duplex) operation, which is a division duplex method combining TDD (Time Division Duplex) and FDD (Frequency Division Duplex), Receiving information indicating the PDCCH monitoring capability related to XDD operation set based on the aforementioned terminal capability information, In accordance with the aforementioned PDCCH monitoring capability, PDCCH monitoring is performed in one of the following ways: slot-level PDCCH monitoring, span-level PDCCH monitoring, or multi-slot PDCCH monitoring. A wireless communication method performed by a terminal having the following characteristics.

Images