Terminal, base station and wireless communication method

Abstract

According one embodiment of the present disclosure, a terminal is provided that has a control unit for selecting a PDCCH monitoring beam in cross division duplex (XDD) time units in which PDCCH monitoring is set, and a reception unit for executing PDCCH monitoring on the selected PDCCH monitoring beam.

Description

[Technical Field]

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

[0002] Long Term Evolution (LTE) was specified for Universal Mobile Telecommunications System (UMTS) networks to achieve higher data rates and lower latency. LTE-Advanced (3GPP Rel. 10-14) was also specified to further enhance capacity and sophistication of LTE (Third Generation Partnership Project (3GPP) Release (Rel.) 8, 9).

[0003] Successor systems to LTE (e.g., 5th generation mobile communication system (5G), 5G+ (plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel. 15 or later) 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 Summary of the Invention

[0005] In future wireless communication systems (for example, NR), it is expected that multiple user terminals (user equipment (UE)) will communicate in an ultra-high density and high traffic environment.

[0006] In such an environment, it is expected that uplink (UL) resources will be insufficient compared to downlink (DL) resources.

[0007] However, in the current NR specifications, methods for increasing uplink resources have not been sufficiently considered. If the methods are not properly controlled, there is a risk of system performance degradation, such as increased latency and reduced coverage.

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

[0009] According to one aspect of the present disclosure, a terminal is provided that has a receiving unit that receives a notification or setting regarding XDD (Cross Division Duplex) operation for a radio resource, and a control unit that controls uplink transmission or downlink reception in the radio resource according to the notification or setting regarding the XDD operation. According to another aspect of the present disclosure, there is provided a terminal including: a receiver that receives a PDCCH monitoring configuration for a Cross Division Duplex (XDD) operation; and a controller that controls PDCCH monitoring according to the PDCCH monitoring configuration. According to another aspect of the present disclosure, a terminal is provided that includes a receiver that receives a PDCCH monitoring capability related to XDD (Cross Division Duplex) operation for a radio resource, and a controller that controls PDCCH monitoring according to the PDCCH monitoring capability. According to another aspect of the present disclosure, there is provided a terminal having a control unit that controls PDCCH overbooking in an XDD (Cross Division Duplex) time unit in which PDCCH monitoring is set, and a receiving unit that performs PDCCH monitoring in a PDCCH monitoring opportunity selected in the controlled PDCCH overbooking. According to another aspect of the present disclosure, there is provided a terminal 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 drawings]

[0010] [Figure 1] FIG. 1 is a block diagram illustrating a functional configuration of a base station (gNB) according to one embodiment of the present disclosure. [Figure 2] FIG. 2 is a block diagram showing a functional configuration of a terminal (UE) according to an embodiment of the present disclosure. [Figure 3] FIG. 1 is a diagram illustrating an example of radio resource allocation for XDD (Cross Division Duplex) according to an embodiment of the present disclosure. [Figure 4] FIG. 1 illustrates an XDD operation according to one embodiment of the present disclosure. [Figure 5] FIG. 1 illustrates a pure time unit and an XDD time unit according to one embodiment of the present disclosure. [Figure 6] FIG. 1 illustrates a PDCCH monitoring opportunity according to one embodiment of the present disclosure. [Figure 7] FIG. 1 illustrates PDCCH overbooking according to one embodiment of the present disclosure. [Figure 8] FIG. 10 is a diagram illustrating a PDCCH monitoring beam according to one embodiment of the present disclosure. [Figure 9] FIG. 10 is a diagram illustrating an example of XDD settings according to an embodiment of the present disclosure. [Figure 10] A diagram showing an example of XDD radio resource allocation according to one embodiment of the present disclosure. [Figure 11] FIG. 10 is a diagram illustrating an example of XDD settings according to an embodiment of the present disclosure. [Figure 12] A diagram showing an example of XDD radio resource allocation according to one embodiment of the present disclosure. [Figure 13] A figure showing an example of XDD configuration and an example of radio resource allocation according to one embodiment of the present disclosure. [Figure 14] A figure showing an example of XDD configuration and an example of radio resource allocation according to one embodiment of the present disclosure. [Figure 15] FIG. 10 is a diagram illustrating an example of XDD settings according to an embodiment of the present disclosure. [Figure 16] A diagram showing an example of XDD radio resource allocation according to one embodiment of the present disclosure. [Figure 17] A figure showing an example of XDD configuration and an example of radio resource allocation according to one embodiment of the present disclosure. [Figure 18] A figure showing an example of XDD configuration and an example of radio resource allocation according to one embodiment of the present disclosure. [Figure 19] FIG. 10 is a diagram illustrating an example of XDD settings according to an embodiment of the present disclosure. [Figure 20] A diagram showing an example of XDD radio resource allocation according to one embodiment of the present disclosure. [Figure 21] A figure showing an example of XDD configuration and an example of radio resource allocation according to one embodiment of the present disclosure. [Figure 22] A figure showing an example of XDD configuration and an example of radio resource allocation according to one embodiment of the present disclosure. [Figure 23] FIG. 10 is a diagram illustrating an example of XDD settings according to an embodiment of the present disclosure. [Figure 24] A diagram showing an example of XDD radio resource allocation according to one embodiment of the present disclosure. [Figure 25] A diagram showing an example of XDD radio resource allocation according to one embodiment of the present disclosure. [Figure 26] A diagram showing an example of XDD radio resource allocation according to one embodiment of the present disclosure. [Figure 27] A diagram showing an example of XDD radio resource allocation according to one embodiment of the present disclosure. [Figure 28] A diagram showing an example of XDD radio resource allocation according to one embodiment of the present disclosure. [Figure 29] A diagram showing an example of XDD radio resource allocation according to one embodiment of the present disclosure. [Figure 30] A diagram showing an example of XDD radio resource allocation according to one embodiment of the present disclosure. [Figure 31] A diagram showing an example of XDD radio resource allocation according to one embodiment of the present disclosure. [Figure 32] FIG. 10 illustrates the monitoring capabilities of each release according to one embodiment of the present disclosure. [Figure 33] A diagram showing an example of XDD radio resource allocation according to one embodiment of the present disclosure. [Figure 34] A diagram showing an example of XDD radio resource allocation according to one embodiment of the present disclosure. [Figure 35] FIG. 1 illustrates prioritization according to one embodiment of the present disclosure. [Figure 36] FIG. 1 illustrates prioritization according to one embodiment of the present disclosure. [Figure 37] A diagram showing an example of XDD radio resource allocation according to one embodiment of the present disclosure. [Figure 38] FIG. 1 illustrates prioritization according to one embodiment of the present disclosure. [Figure 39] FIG. 1 illustrates prioritization according to one embodiment of the present disclosure. [Figure 40] A diagram showing an example of XDD radio resource allocation according to one embodiment of the present disclosure. [Figure 41] FIG. 1 illustrates prioritization according to one embodiment of the present disclosure. [Figure 42] FIG. 1 illustrates prioritization according to one embodiment of the present disclosure. [Figure 43] FIG. 1 illustrates prioritization according to one embodiment of the present disclosure. [Figure 44] FIG. 1 illustrates prioritization according to one embodiment of the present disclosure. [Figure 45] FIG. 1 illustrates prioritization according to one embodiment of the present disclosure. [Figure 46] FIG. 1 illustrates prioritization according to one embodiment of the present disclosure. [Figure 47] FIG. 1 illustrates prioritization according to one embodiment of the present disclosure. [Figure 48] FIG. 1 illustrates prioritization according to one embodiment of the present disclosure. [Figure 49] FIG. 1 illustrates prioritization according to one embodiment of the present disclosure. [Figure 50] FIG. 1 illustrates prioritization according to one embodiment of the present disclosure. [Figure 51] FIG. 1 illustrates prioritization according to one embodiment of the present disclosure. [Figure 52] FIG. 2 is a block diagram illustrating a hardware configuration of a base station and a terminal according to an embodiment of the present disclosure. [Figure 53] FIG. 1 is a block diagram illustrating a hardware configuration of a vehicle according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

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

[0012] (wireless communication system) The configuration of a wireless communication system according to an embodiment of the present disclosure will be described below. In this wireless communication system, communication is performed using any one of the wireless communication methods according to the above-described embodiments of the present disclosure or a combination thereof. The wireless communication system may be a system that realizes communication using Long Term Evolution (LTE), 5th generation mobile communication system New Radio (5G NR), or a successor wireless communication system thereof, as specified by the Third Generation Partnership Project (3GPP).

[0013] The wireless communication system may also 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)), etc.

[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] The wireless communication system may support dual connectivity between multiple base stations within the same RAT (e.g., dual connectivity where both the MN and SN are NR base stations (gNBs) (NR-NR Dual Connectivity (NN-DC))).

[0016] The wireless communication system may include a base station that forms a macrocell C1 with a relatively wide coverage, and a base station that is located within the macrocell C1 and forms a small cell C2 that is narrower than the macrocell C1. A terminal (UE) may be located within at least one of the cells. The locations and numbers of the cells and terminals are not limited to a specific embodiment.

[0017] A terminal may be connected to at least one of a plurality of base stations, and may utilize at least one of carrier aggregation (CA) using a plurality of component carriers (CC) and dual connectivity (DC).

[0018] Each CC may be included in at least one of a first frequency band (Frequency Range 1 (FR1)) and a second frequency band (Frequency Range 2 (FR2)). The macro cell C1 may be included in FR1, and the 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 be a frequency band higher than FR2.

[0019] Furthermore, the terminal may perform communication using at least one of Time Division Duplex (TDD) and Frequency Division Duplex (FDD) in each CC.

[0020] Multiple base stations may be connected by wire (e.g., optical fiber compliant with Common Public Radio Interface (CPRI), X2 interface, etc.) or wirelessly (e.g., NR communication). For example, when NR communication is used as a backhaul between two base stations, the base station corresponding to the upper station may be called an Integrated Access Backhaul (IAB) donor, and the base station corresponding to the relay station may be called an IAB node.

[0021] A base station may be connected to a core network directly or via another base station, and the core network may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), a Next Generation Core (NGC), etc.

[0022] The terminal may be a terminal compatible with at least one of communication methods such as LTE, LTE-A, 5G, and 6G.

[0023] In a wireless communication system, an Orthogonal Frequency Division Multiplexing (OFDM)-based radio access scheme may be used. For example, in at least one of a downlink (DL) and an uplink (UL), a Cyclic Prefix OFDM (CP-OFDM), a Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), an Orthogonal Frequency Division Multiple Access (OFDMA), a Single Carrier Frequency Division Multiple Access (SC-FDMA), or the like may be used.

[0024] The radio access scheme may also be called a waveform. In a wireless communication system, other radio access schemes (e.g., other single-carrier transmission schemes, other multi-carrier transmission schemes) may be used as the UL and DL radio access schemes.

[0025] In a wireless communication system, a downlink channel may be a physical downlink shared channel (PDSCH) shared by each terminal, a physical broadcast channel (PBCH), a physical downlink control channel (PDCCH), or the like.

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

[0027] The PDSCH transmits user data, higher layer control information, System Information Block (SIB), etc. The PUSCH may transmit user data, higher layer control information, etc. Furthermore, the PBCH may transmit Master Information Block (MIB).

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

[0029] Note that the DCI for scheduling the PDSCH may be referred to as a DL assignment, a DL DCI, etc., and the DCI for scheduling the PUSCH may be referred to as an UL grant, a UL DCI, etc. Note that the PDSCH may be interpreted as DL data, and the PUSCH may be interpreted as UL data.

[0030] A control resource set (CORESET) and a search space may be used to detect the PDCCH. The CORESET corresponds to resources to search for DCI. The search space corresponds to a search region and a search method for PDCCH candidates. One CORESET may be associated with one or more search spaces. The UE may monitor a CORESET associated with a certain search space based on the search space configuration.

[0031] One search space may correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may be referred to as a search space (SS) set. Note that the terms "search space," "search space set," "search space setting," "search space set setting," "CORESET," "CORESET setting," etc. in the present disclosure may be read interchangeably.

[0032] The PUCCH may transmit uplink control information (UCI) including at least one of channel state information (CSI), acknowledgement information (which may be called, for example, Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, etc.), and scheduling request (SR). The PRACH may transmit a random access preamble for establishing a connection with a cell.

[0033] In the present disclosure, various channels may be expressed without adding "Physical" to the beginning of the channel.

[0034] In the wireless communication system, a synchronization signal (SS), a downlink reference signal (DL-RS), etc. may be transmitted. In the wireless communication system, 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. may be transmitted as the DL-RS.

[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 the SS (PSS, SSS) and the PBCH (and DMRS for the PBCH) may be referred to as an SS / PBCH block, an SS Block (SSB), or the like. Note that the SS, SSB, and the like may also be referred to as a reference signal.

[0036] In addition, in a wireless communication system, a sounding reference signal (SRS), a demodulation reference signal (DMRS), etc. may be transmitted as an uplink reference signal (UL-RS). Note that the DMRS may also be called a UE-specific reference signal.

[0037] (Device configuration) Next, a description will be given of an example of the functional configuration of the base station (gNB) 100 and the terminal (UE) 200 that execute the processes and operations described below. The gNB 100 and the UE 200 include functions that realize the embodiments described below. However, the gNB 100 and the UE 200 may each include only a part of the functions of the embodiments.

[0038] (gNB100) Fig. 1 is a diagram showing an example of the functional configuration of the gNB 100. As shown in Fig. 1, the gNB 100 has a receiving unit 101, a transmitting unit 102, and a control unit 103. The functional configuration shown in Fig. 1 is merely an example. The names of the functional divisions and functional units may be any as long as they can perform the operations related to the embodiment of the present invention.

[0039] The receiver 101 has a function of receiving various signals transmitted from the UE 200 and acquiring, for example, information of a higher layer from the received signals. The transmitter 102 has a function of generating signals to be transmitted to the UE 200 and transmitting the signals via wire or wirelessly.

[0040] The control unit 103 stores preset setting information and various setting information to be transmitted to the UE 200 in a storage device, and reads the information from the storage device as needed. The control unit 103 also executes processing related to communication with the UE 200. A functional unit related to signal transmission in the control unit 103 may be included in the transmitting unit 102, and a functional unit related to signal reception in the control unit 103 may be included in the receiving unit 101.

[0041] (UE200) Fig. 2 is a diagram showing an example of the functional configuration of UE 200. As shown in Fig. 2, UE 200 has a transmitting unit 201, a receiving unit 202, and a control unit 203. The functional configuration shown in Fig. 2 is merely an example. The names of the functional divisions and functional units may be any as long as they can perform the operations according to the embodiment of the present invention.

[0042] The transmitter 201 creates a transmission signal from transmission data and transmits the transmission signal wirelessly. The receiver 202 receives various signals wirelessly and acquires higher layer signals from the received physical layer signals. The receiver 202 also has a function of receiving NR-PSS, NR-SSS, NR-PBCH, DL / UL control signals, reference signals, etc. transmitted from the gNB 100.

[0043] The control unit 203 stores various setting information received from the gNB 100 by the receiving unit 202 in a storage device, and reads it from the storage device as needed. The control unit 203 also executes processing related to communication with the gNB 100. A functional unit related to signal transmission in the control unit 203 may be included in the transmitting unit 201, and a functional unit related to signal reception in the control unit 203 may be included in the receiving unit 202.

[0044] (XDD operation) Considering the time ratio of transmission and reception (e.g., DL:UL = 4:1) in Time Division Duplex (TDD) up to Rel. 16, there may be cases where the number of transmission opportunities for UL signals / channels is fewer than the number of reception opportunities for DL ​​signals / channels. In such cases, UEs cannot transmit UL signals / channels frequently, which raises concerns about transmission delays for important UL signals / channels. Furthermore, since there are fewer UL transmission opportunities compared to DL reception opportunities, there is also concern about signal / channel congestion during UL transmission opportunities. Furthermore, with TDD, the time resources available for transmitting UL signals / channels are limited, which limits the application of UL coverage extension techniques, such as repetition transmission.

[0045] In future wireless communication systems (for example, Rel. 17 / 18 and later), the introduction of a frequency division duplexing method that combines TDD and frequency division duplex (FDD) for UL and DL is being considered.

[0046] This division duplexing method may also be called XDD (Cross Division Duplex) or subband non-overlapping full duplex. XDD or subband non-overlapping full duplex may refer to a duplexing method in which DL and UL are frequency-division multiplexed within one component carrier (CC) in the TDD band (DL and UL can be used simultaneously).

[0047] Fig. 3A is a diagram showing an example of the TDD configuration defined up to Rel. 16. In the example shown in Fig. 3A, TDD slots or symbols are configured for a UE in a bandwidth such as one component carrier (CC) (which may also be called a cell or serving cell) or bandwidth portion (BWP).

[0048] In the example shown in Figure 3A, the time ratio of DL slots to UL slots is 4:1. This conventional TDD slot or symbol configuration does not ensure sufficient UL time resources, which can result in UL transmission delays and reduced coverage performance.

[0049] Fig. 3B is a diagram showing an example of the configuration of XDD. In the example shown in Fig. 3B, within one component carrier (CC), resources used for DL ​​reception and resources used for UL transmission overlap in time. With such a resource configuration, more UL resources can be secured, thereby improving resource utilization efficiency.

[0050] For example, as shown in the example of Figure 3B, both ends of the frequency domain may be set as DL resources, and these DL resources may sandwich UL resources. This may prevent or mitigate cross link interference (CLI) with neighboring carriers. Also, a guard region may be set at the boundary between the DL resources and the UL resources.

[0051] Considering the complexity of handling self-interference, it is possible that only the base station uses DL and UL resources simultaneously, i.e., in the case of DL and UL overlapping radio resources in time, one UE may use DL resources and another UE may use UL resources.

[0052] Fig. 4 is a diagram showing an example of XDD operation. In the example shown in Fig. 4, part of the DL resources of the TDD band is set as the UL resources, and the DL and UL are configured to partially overlap in the time domain.

[0053] In the example shown in FIG. 4, during the DL-only period, each of the multiple UEs (UE#1 and UE#2 in FIG. 4) receives the DL channel / signal.

[0054] Furthermore, during the period when DL and UL overlap in time, one UE (UE#1 in the example of FIG. 4) receives the DL channel / signal, and another UE (UE#2 in the example of FIG. 4) transmits the UL channel / signal. During this period, the base station simultaneously transmits and receives DL and UL.

[0055] Furthermore, during the UL-only period, each of the multiple UEs (UE#1 and UE#2 in FIG. 4) transmits an UL channel / signal.

[0056] In existing NR (e.g., those defined up to Rel. 15 / 16), DL frequency resources and UL frequency resources in a UE carrier are configured as DL BWP and UL BWP, respectively. To switch DL / UL frequency resources to other DL / UL frequency resources, multiple BWP configurations and a BWP adaptation mechanism are required.

[0057] In addition, in existing NR, the time resource in the TDD carrier for the UE is 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 signaled or configured as UL (or DL) or for UL transmission (or DL ​​reception) on some frequency resources, and signaled or configured as DL (or UL) or for DL ​​reception (or UL transmission) on other frequency resources. Alternatively, an XDD symbol may be a symbol that is signaled or configured as UL (or DL) or for UL transmission (or DL ​​reception) on a portion of frequency resources. Alternatively, an XDD symbol may be a symbol that is signaled or configured as DL (or UL) or for DL ​​reception (or UL transmission) on a portion of frequency resources.

[0059] Here, the time unit may be at the symbol level, slot / subslot level, or a group of symbols / slots / subslots, i.e., an 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 / sub-slot that does not contain or overlap an XDD symbol, or a group of symbols / slots / sub-slots that do not contain or overlap an XDD symbol, and may also be referred to as a non-XDD time unit. For example, a pure time unit may be referred to as a time unit consisting only of DL on a frequency resource, as shown in Figure 5A, or as a time unit consisting only of UL on a frequency resource, as shown in Figure 5B.

[0061] Furthermore, for an XDD time unit, DL resources and UL resources may have various allocation patterns in the frequency domain. For example, an XDD time unit of frequency domain pattern #1 may have an allocation pattern as shown in FIG. 5C. An XDD time unit of frequency domain pattern #2 may have an allocation pattern as shown in FIG. 5D. An XDD time unit of frequency domain pattern #3 may have an allocation pattern as shown in FIG. 5E. These allocation patterns are merely exemplary, and other allocation patterns may be used. The frequency domain pattern of an XDD time unit may refer to a resource repetition pattern in the frequency domain for the XDD time unit.

[0062] (PDCCH monitoring) In Rel-15 / 16, a UE performs blind decoding (BD) on a set of PDCCH (Physical Downlink Control Channel) candidates for a configured search space (SS) set. Specifically, the UE determines the PDCCH monitoring opportunity on the active DL BWP from the PDCCH monitoring period, PDCCH monitoring offset, and PDCCH monitoring pattern within the slot. For example, for a PDCCH monitoring period k=5, a PDCCH monitoring offset o=2, and a PDCCH monitoring pattern (duration) d=3, the UE monitors PDCCH candidates within the slots of the search space (SS) set as shown in Figure 6.

[0063] Specifically, in each slot to be monitored, the UE monitors PDCCH candidates at PDCCH monitoring opportunities as shown in Fig. 6. In the illustrated example, when the duration of CORESET is 2 and monitoringSymbolsWithinSlot=10001000100000, the UE monitors PDCCH candidates at PDCCH monitoring opportunity #0 corresponding to the "0" and "1" symbols and at PDCCH monitoring opportunity #1 corresponding to the "4" and "5" symbols.

[0064] (PDCCH monitoring capability) Furthermore, PDCCH monitoring capability can be signaled or configured per slot in Rel-15, per span in Rel-16, and multiple slots in Rel-17. For per-slot PDCCH monitoring capability in Rel-15, overbooking, which sets the number of PDCCH candidates and / or control channel elements (CCEs) beyond the UE capability, is only allowed on the primary cell (Pcell) or primary secondary cell (PScell). For per-span PDCCH monitoring capability in Rel-16, overbooking is only allowed on the first span of a slot on a Pcell / PScell. For multi-slot PDCCH monitoring capability in Rel-17, overbooking is only allowed on a Pcell / PScell.

[0065] Also, for common search spaces (CSS), overbooking is not allowed, i.e., the network ensures that the number of non-overlapping CCEs and PDCCH candidates of a CSS in a slot, span, or group of X slots is less than or equal to the blind decoding (BD) or control channel element (CCE) limit.

[0066] On the other hand, for UE-specific search spaces (USSs), overbooking is allowed based on the USS index. Specifically, a USS with a smaller search space (SS) index may have a higher priority. That is, a USS with a larger SS index is dropped until the number of PDCCH candidates and non-overlapping CCEs of the CSS in a slot, span, or group of X slots is below the blind decoding (BD) or control channel element (CCE) limit.

[0067] For example, as shown in FIG. 7, if USS#1 with 28 CCEs, USS#2 with 24 CCEs, and CSS#1 with 24 CCEs are in a slot and the limit is 56, PDCCH candidates are monitored only for CSS#1 and USS#1, which have higher priority and do not exceed the limit of 56.

[0068] (PDCCH monitoring beam) For overlapping PDCCH monitoring occasions, if the TCI (Transmission Configuration Indication) state or beam is set to CORESET, the UE monitors PDCCH candidates with the same TCI state that are included in or overlap with the PDCCH monitoring occasion. The TCI state is determined by the SS with the highest priority, where a CSS has higher priority than a USS, an SS with a smaller cell index has higher priority than an SS with a larger cell index, and an SS with a smaller SS index has higher priority than an SS with a larger SS index.

[0069] According to the above-mentioned prioritization, 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 Example) Specific constraints on XDD operation are not currently discussed. For example, XDD operation may not be supported for a particular cell.

[0071] In the first embodiment, cells or time resources for which the XDD operation can be configured are limited. The UE may not assume that a Pcell / PScell ​​is signaled or configured for the XDD operation. The UE may also not assume that any cell in a primary / secondary cell group is signaled, configured, or applied to the XDD operation. Alternatively, the UE may not assume that any BWP or cell with a search space (SS) set and / or a CORESET configuration configured is signaled or configured for the XDD operation. Alternatively, the UE may not assume that any BWP or cell with a specific type of SS set and / or a specific type of CORESET configuration configured is signaled or configured as UL (or DL) on some frequency resources or is signaled or configured for UL transmission (or DL ​​reception) even if the XDD operation is signaled or configured.

[0072] Here, a specific type of SS set is: i) Type 0-PDCCH CSS set configured by pdcch-ConfigSIB1 in MIB (Master Information Block), by searchSpaceSIB1 in PDCCH-ConfigCommon, and by searchSpaceZero in PDCCH-ConfigCommon ii) Type 0A-PDCCH CSS set configured by searchSpaceOtherSystemInformation in PDCCH-ConfigCommon iii) Type1-PDCCH CSS set configured by ra-SearchSpace in PDCCH-ConfigCommon iv) Type 2-PDCCH CSS set configured by pagingSearchSpace in PDCCH-ConfigCommon v) a Type 3-PDCCH CSS set configured by a SearchSpace in a PDCCH-Config with searchSpaceType=common, and / or vi) USS set configured by SearchSpace in PDCCH-Config with searchSpaceType=ue-Specific It may be either of the above.

[0073] The UE may also not assume that any BWP or cell configured with PUCCH resources / transmissions is signaled, configured, or applied to XDD operation. Alternatively, the UE may not assume that any BWP or cell in FR2-2 is signaled or configured as UL (or DL) or for XDD operation. Alternatively, the UE may not assume that any BWP or cell configured with a Subcarrier Spacing (SCS) value greater than a certain value (e.g., an SCS value of 60, 120, 480, or 960 kHz) is signaled or configured to XDD operation.

[0074] In view of this assumption, in the first embodiment, if one or more conditions described below are met, the XDD operation may be notified or set to the BWP or cell.

[0075] Specifically, the XDD operation may be signaled or configured in the BWP as follows. For example, a certain time unit on the BWP may be signaled or configured as UL (or DL) on some frequency resources, or may be signaled or configured for UL transmission (or DL ​​reception), while on other frequency resources it may be signaled or configured as DL (or UL) or may be signaled or configured for DL ​​reception (or UL transmission). The time unit here may be a symbol, a slot, a subslot, or a group of symbols, slots, or subslots. That is, the XDD operation may be signaled or configured in the BWP on a frequency resource basis for a certain time unit.

[0076] As another example, a certain time unit on the BWP may be signaled or configured as UL (or DL) or signaled or configured for UL transmission (or DL ​​reception) for some UEs, while being signaled or configured as DL (or UL) or signaled or configured for DL ​​reception (or UL transmission) for other UEs. That is, XDD operation may be signaled or configured on the BWP for a certain time unit on a UE-by-UE basis.

[0077] As another example, a certain time unit on the BWP may be signaled or configured as UL (or DL) on some frequency resources, or may be signaled or configured for UL transmission (or DL ​​reception), and the certain frequency resources may be signaled or configured as unavailable for UL (or DL) by a new slot format configuration / signal or a new rate match pattern configuration / signal. That is, XDD operation may be signaled or configured on the BWP for a certain time unit using a new slot format configuration / signal or a new rate match pattern configuration / signal.

[0078] Furthermore, the XDD operation may be signaled or configured in a cell as follows: For example, the XDD operation may be signaled or configured in any one or active BWPs of the cell. As another example, multiple BWPs for the XDD operation may be signaled or configured for the cell.

[0079] Thus, according to the first embodiment, the UE may receive a notification or configuration regarding XDD operation for a radio resource and control uplink transmission or downlink reception on the radio resource according to the notification or configuration regarding XDD operation. Correspondingly, the base station may transmit a notification or configuration regarding XDD operation for a radio resource and control uplink transmission or downlink reception on the radio resource according to the notification or configuration regarding XDD operation.

[0080] Specifically, the UE may receive notification or configuration regarding XDD operation for each frequency resource unit for a time unit on the BWP. In response, the base station may transmit notification or configuration regarding XDD operation for each frequency resource unit for a time unit on the BWP. Here, the notification or configuration regarding XDD operation for each frequency resource unit may notify or configure some frequency resources of the BWP for uplink transmission or downlink reception, and notify or configure other frequency resources of the BWP for downlink reception or uplink transmission. Furthermore, the some frequency resources may be notified or configured as available or unavailable for uplink transmission or downlink reception by slot format configuration or notification or rate match pattern configuration or notification.

[0081] Furthermore, the UE may receive notification or configuration regarding per-terminal XDD operation for a time unit on the BWP. Correspondingly, the base station may transmit notification or configuration regarding per-terminal XDD operation for a time unit on the BWP. Here, the notification or configuration regarding per-terminal XDD operation may notify or configure a time unit for uplink transmission or downlink reception to one terminal, and may notify or configure a time unit for downlink reception or uplink transmission to another terminal.

[0082] The UE may also receive a notification or configuration indicating the BWP of the cell in which the XDD operation is configured or the BWP for the XDD operation of the cell, and in response, the base station may transmit a notification or configuration indicating the BWP of the cell in which the XDD operation is configured or the BWP for the XDD operation of the cell.

[0083] The above-mentioned configuration or notification may be transmitted as, for example, at least one of a Radio Resource Control (RRC) information element, a Downlink Control Information (DCI), and a Medium Access Control (MAC) CE.

[0084] Furthermore, to realize the above-mentioned 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 configure the UE to perform the XDD operation based on the received UE capability information. Specifically, UE capability information related to whether the XDD operation applied to the Pcell / PScell ​​is supported may be specified, and the UE may transmit the UE capability information related to whether the XDD operation applied to the Pcell / PScell ​​is supported to the base station.

[0085] In addition, UE capability information regarding whether the UE supports the XDD operation applied to the cells in the primary / secondary cell group is specified, and the UE may transmit the UE capability information regarding whether the UE supports the XDD operation applied to the cells in the primary / secondary cell group to the base station.

[0086] In addition, UE capability information regarding whether the UE supports XDD operations applied to the cell / BWP in which the SS set (of a particular SS set type) is set is specified, and the UE may transmit the UE capability information regarding whether the UE supports XDD operations applied to the cell / BWP in which the SS set (of a particular SS set type) is set to the base station.

[0087] In addition, UE capability information regarding whether the UE supports the XDD operation applied to the cell / BWP in which the PUCCH resource / transmission is set is specified, and the UE may transmit the UE capability information regarding whether the UE supports the XDD operation applied to the cell / BWP in which the PUCCH resource / transmission is set to the base station.

[0088] In addition, UE capability information regarding whether the UE supports the XDD operation applied to the cell / BWP in FR2-2 is specified, and the UE may transmit the UE capability information regarding whether the UE supports the XDD operation applied to the cell / BWP in FR2-2 to the base station.

[0089] In addition, UE capability information regarding whether the UE supports XDD operation applied to a cell / BWP in which an SCS larger than a specific value is set may be specified, and the UE may transmit the UE capability information regarding whether the UE supports XDD operation applied to a cell / BWP in which an SCS larger than a specific value is set to the base station.

[0090] According to the first embodiment, it becomes possible to limit the cells or time resources that can be set in the XDD operation.

[0091] (Second Example) There is currently no discussion regarding the search space (SS) set and / or CORESET configuration when the XDD operation is signaled, configured, or applied to the BWP or cell for which PDCCH monitoring is configured. Therefore, it is necessary to specify the UE operation for the SS set and / or CORESET configuration when the XDD operation is signaled, configured, or applied to the BWP or cell for which PDCCH monitoring is configured. In a second embodiment, when the XDD operation is configurable for the PDCCH monitoring resource, the UE may perform PDCCH monitoring as described below.

[0092] In option 1 of the second embodiment, an existing configuration may be used for the SS set configuration or CORESET configuration when XDD operation can be notified, configured, or applied to a BWP or a cell for which PDCCH monitoring is configured. That is, even when XDD operation can be notified, configured, or applied to a BWP or a cell for which PDCCH monitoring is configured, no enhancement may be made to the SS set configuration or CORESET configuration.

[0093] On the other hand, it should be noted that even if the SS set configuration or CORESET configuration is not extended in this manner, when XDD operation is notified, configured or applied to a BWP or cell for which PDCCH monitoring is configured, the PDCCH monitoring operation by the UE needs to be extended as described below in relation to the third embodiment.

[0094] In option 2 of the second embodiment, separate SS set configurations may be configured for pure time units and XDD time units. That is, separate search space sets may be configured for normal TDD operation and XDD operation. Here, the time units may be at the symbol level, slot / subslot level, or a group of symbols / slots / subslots. Also, an 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. A pure time unit may be a non-XDD symbol, that is, a symbol that is not an XDD symbol, or a slot / subslot or group of symbols / slots / subslots that does not contain or overlap an XDD symbol.

[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 a new information element (IE) 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 of pure time units, the maximum number N of SS sets configured for a pure time unit in PDCCH-Config may be equal to a predetermined number such as 10 (e.g., N=10), or may be 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 configured for an XDD time unit in PDCCH-Config may be equal to a predetermined number such as 10 (e.g., M=10), or may be less than or greater than the predetermined number such as 10 (e.g., M<10 or M>10). Furthermore, M may be equal to (10-N) without any limitation.

[0098] For example, as shown in Fig. 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 occasions in the same manner as in Rel-15 / 16.

[0100] For PDCCH monitoring opportunities of a non-XDD SS set, for example, the UE may not assume that any PDCCH monitoring opportunities of the non-XDD SS set are included in or overlap with an XDD time unit or an XDD symbol. Alternatively, for another example, if a PDCCH monitoring opportunity of an XDD SS set is included in or overlaps with an XDD time unit or an XDD symbol, the UE may not monitor PDCCH candidates in the PDCCH monitoring opportunities that are included in or overlap with the XDD time unit or the XDD symbol. On the other hand, if a PDCCH monitoring opportunity of an XDD SS set is not included in or does not overlap with an XDD time unit or an XDD symbol, the UE may monitor PDCCH candidates in the PDCCH monitoring opportunities in the same manner as in Rel-15 / 16.

[0101] On the other hand, for PDCCH monitoring opportunities of the XDD SS set, as an example, the UE may not assume that any PDCCH monitoring opportunity of 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 not 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 does not overlap 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 configuration of pure time units and XDD time units as shown in Figure 10, the UE monitors PDCCH candidates according to non-XDD SS set #0 in pure time units and monitors PDCCH candidates according to XDD SS set #1 in XDD time units. Specifically, the UE monitors PDCCH candidates in the 0th, 2nd, 4th, 6th, 8th, 10th, 12th, 17th, and 18th slots.

[0103] As a variant, the XDD SS set may be configured only for a specific SS type, for example, the specific SS type may be a Type 0-PDCCH CSS set, a Type 0A-PDCCH CSS set, a Type 1-PDCCH CSS set, a Type 2-PDCCH CSS set, a Type 3-PDCCH CSS set, and / or a USS set.

[0104] Alternatively, as another modification, the XDD SS set may be set only for a specific DCI (Downlink Control Information) format. For example, the specific DCI formats 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] Also, as a modification, 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 modification, when 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, in addition to the existing searchSpacesToAddModList, up to X additional SS set configurations may be configured in the PDCCH-Config, where the value of X may be set to be equal to or less than the number of frequency domain patterns for the configured XDD time unit. The value of X may be specified by a specification or configured in the RRC configuration.

[0107] Furthermore, for PDCCH monitoring opportunities of an SS set whose frequency-domain pattern type #i is set to an XDD time unit, the UE may not assume that any of the PDCCH monitoring opportunities of the SS set whose frequency-domain pattern type #i is set to an XDD time unit is included in or overlaps with a pure time unit or an XDD time unit having another frequency-domain pattern type. Furthermore, if a PDCCH monitoring opportunity of an SS set whose frequency-domain pattern type #i is set to an XDD time unit is included in or overlaps with a pure time unit or an XDD time unit having another frequency-domain pattern type, the UE may not monitor PDCCH candidates in PDCCH monitoring opportunities that are included in or overlap with a pure time unit or an XDD time unit having another frequency-domain pattern type.

[0108] For example, if two additional SS set configurations are configured, four IEs, searchSpacesToAddModListForXdd1, searchSpacesToReleaseListForXdd1, and searchSpacesToAddModListForXdd2, searchSpacesToReleaseListForXdd2, may be set in the PDCCH-Config, as shown in FIG. 11.

[0109] According to the PDCCH monitoring opportunities for the non-XDD SS set and XDD SS set described above, in the configuration example of the pure time unit and XDD time unit shown in Figure 12, the UE monitors PDCCH candidates according to SS set #0 of the pure time unit in the pure time unit, monitors PDCCH candidates according to XDD SS set #1 of frequency domain pattern type 1 in the XDD time unit of frequency domain pattern type 1, and monitors PDCCH candidates according to XDD SS set #2 of frequency domain pattern type 2 in the XDD time unit of frequency domain pattern type 2. Specifically, the UE monitors PDCCH candidates in the 0th, 2nd, 4th, 6th, 8th, 12th, 13th, 14th, and 18th slots.

[0110] In option 3 of the second embodiment, multiple controlResourceSetIds may be set for the SS set configuration. That is, multiple CORESETs can be set. Here, controlResourceSetId is an IE for identifying a CORESET.

[0111] As option 3-1, separate CORESET associations may be applied to pure time units and XDD time units. That is, a CORESET may be set for normal TDD operation and for XDD operation. Specifically, an existing controlResourceSetId may be set for pure time units, and a new controlResourceSetIdForXdd may be set for XDD time units.

[0112] For each monitoring start position of the SS set, if the monitoring start position is contained in or overlaps with a pure time unit, the existing controlResourceSetId may be used to determine the corresponding PDCCH monitoring occasion and PDCCH candidate, whereas if the monitoring start position is contained in or overlaps with an XDD time unit, a new controlResourceSetIdForXdd may be used to determine the corresponding PDCCH monitoring occasion and PDCCH candidate.

[0113] For example, two IEs, controlResourceSetId for pure time unit and controlResourceSetIdForXdd for XDD time unit, may be set in the SearchSpace configuration as shown in FIG. 13A.

[0114] Also, as shown in FIG. 13B, the UE may determine PDCCH monitoring occasions and PDCCH candidates according to controlResourceSetId in pure time units, and may determine PDCCH monitoring occasions and PDCCH candidates 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. As an 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 configured, where the value of X may be set to be equal to or less than the number of frequency domain patterns of the configured XDD time unit. The value of X may be specified by a specification or configured in the RRC configuration.

[0117] For example, the IEs controlResourceSetIdForXdd-1, controlResourceSetIdForXdd-2, and controlResourceSetIdForXdd-3 for three additional frequency domain patterns may be set in the SearchSpace configuration as shown in FIG. 14A.

[0118] Also, as shown in FIG. 14B, the UE may determine PDCCH monitoring opportunities and PDCCH candidates according to controlResourceSetId in pure time units, determine PDCCH monitoring opportunities and PDCCH candidates according to controlResourceSetIdForXdd-1 in XDD time units using frequency domain pattern type 1, and determine PDCCH monitoring opportunities and PDCCH candidates according to controlResourceSetIdForXdd-2 in XDD time units using frequency domain pattern type 2.

[0119] Also, in option 3-2, for each monitoring start position of the SS set, the UE may determine the PDCCH monitoring opportunity and PDCCH candidate by trying the list of controlResourceSetIds until an appropriate controlResourceSetId is selected or until all controlResourceSetIds have been tried. That is, the UE selects a suitable one from multiple CORESETs according to the SS configuration.

[0120] For example, for the monitoring start position of the SS set, the UE may first determine PDCCH monitoring occasions and PDCCH candidates of the SS set by using a first CORESET ID. If none of the determined PDCCH candidates overlaps with the time and frequency domain resources signaled or configured as UL or signaled or configured for UL transmission, the UE may determine to use the CORESET and monitor the determined PDCCH candidates.

[0121] If any of the determined PDCCH candidates overlaps with the time and frequency domain resources that are notified or configured as UL or are notified or configured for UL transmission, the UE may determine the PDCCH monitoring occasion and PDCCH candidate by using the next configured CORESET ID until a CORESET ID is detected from which a PDCCH candidate that does not overlap with the time and frequency domain resources that are notified or configured as UL or are notified or configured for UL transmission is obtained.

[0122] If the UE has tried all CORESET IDs configured in the SS set but cannot find a CORESET ID from which a PDCCH candidate that does not overlap with the time and frequency domain resources signaled or configured as UL or signaled or configured for UL transmission can be obtained, the default CORESET, the first CORESET, or the last CORESET may be used to determine the PDCCH candidate. Alternatively, the UE may not consider such a case. Alternatively, the UE may not monitor PDCCH candidates at the monitoring start position of the SS set.

[0123] For example, the IE of controlResoruceSetAddForXdd for specifying the trial order of multiple controlResoruceSetIds may be set in the SearchSpace configuration as shown in FIG.

[0124] In the example shown in FIG. 16, the UE tries each CORESET ID in the order controlResourceSetId, controlResourceSetId-2, controlResourceSetId-3 and controlResourceSetId-4 to determine whether each CORESET ID contains PDCCH candidates that do not overlap with the time and frequency domain resources that are signaled or configured as UL or are signaled or configured for UL transmission.

[0125] In the illustrated example, for PDCCH monitoring start position #0, controlResourceSetId-3 is determined to be a CORESET including PDCCH candidates that do not overlap with time and frequency domain resources notified or configured as UL or notified or configured 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, it is determined that controlResourceSetId is a CORESET that includes PDCCH candidates that do not overlap with time and frequency domain resources that are notified or configured as UL or that are notified or configured for UL transmission, and 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 configured for a CORESET configuration, where multiple frequency domain patterns are configured for the CORESET, where frequencyDomainResources is an IE that specifies frequency domain resources for the CORESET.

[0128] As Option 4-1, separate frequencyDomainResources configurations may be applied to pure time units and XDD time units. That is, frequency domain patterns are configured according to normal TDD operation and XDD operation. For example, in addition to the existing frequencyDomainResources, a new frequencyDomainResourcesForXdd may be configured for CORESET. For each PDCCH monitoring opportunity of the SS set for CORESET, if the PDCCH monitoring opportunity is not contained in or does not overlap 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 contained in or overlaps 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 set in the ControlResourceSet configuration as shown in FIG. 17A.

[0130] Also, in the example shown in FIG. 17B, the UE may monitor PDCCH candidates determined based on frequencyDomainResources in pure time units, and may monitor 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. As an 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 configured, where the value of X may be set to be equal to or less than the number of frequency domain patterns for the configured XDD time unit. The value of X may be specified by a specification or configured in the RRC configuration.

[0133] For example, the IEs frequencyDomainResourcesForXdd-1, frequencyDomainResourcesForXdd-2, and frequencyDomainResourcesForXdd-3 for three additional frequency domain patterns may be set in the ControlResourceSet configuration as shown in FIG. 18A.

[0134] Also, as shown in FIG. 18B, the UE may determine PDCCH candidates according to frequencyDomainResources for pure time units, determine PDCCH candidates according to frequencyDomainResourcesForXdd-1 for XDD time units with frequency domain pattern type 1, and determine PDCCH candidates according to frequencyDomainResourcesForXdd-2 for XDD time units with frequency domain pattern type 2.

[0135] As option 4-2, for each PDCCH monitoring opportunity of an SS set for a CORESET, the UE may determine a PDCCH candidate by trying a list of frequencyDomainResources until a suitable frequencyDomainResource is selected or until all frequencyDomainResources have been tried. That is, the UE may select a suitable one from multiple CORESETs depending on the SS set.

[0136] For example, for each PDCCH monitoring occasion of the SS set for the CORESET, the UE may first determine a PDCCH candidate by utilizing a first frequencyDomainResources. If none of the determined PDCCH candidates overlaps with the time and frequency domain resources signaled or configured as UL or signaled or configured for UL transmission, the UE may determine to use the frequencyDomainResources and monitor the determined PDCCH candidate.

[0137] If any of the determined PDCCH candidates overlap with the time and frequency domain resources that are notified or configured as UL or are notified or configured for UL transmission, the UE may determine a PDCCH candidate by utilizing the next configured frequencyDomainResources until frequencyDomainResources is detected from which a PDCCH candidate that does not overlap with the time and frequency domain resources that are notified or configured as UL or are notified or configured for UL transmission is obtained.

[0138] If the UE has tried all frequencyDomainResources but has not found any frequencyDomainResources from which a PDCCH candidate that does not overlap with the time and frequency domain resources signaled or configured as UL or for UL transmission is obtained, the default frequencyDomainResources, the first frequencyDomainResources, or the last frequencyDomainResources may be used to determine the PDCCH candidate. Alternatively, the UE may not consider such a case. Alternatively, the UE may not monitor a PDCCH candidate in the PDCCH monitoring occasion.

[0139] For example, the IE of frequencyDomainResourcesAddForXdd for specifying the trial order of multiple frequencyDomainResources may be set in the ControlResourceSet configuration as shown in FIG.

[0140] In the example shown in FIG. 20, the UE tries each frequencyDomainResources in the order frequencyDomainResources, frequencyDomainResources-2, and frequencyDomainResources-3 to determine whether each frequencyDomainResources contains PDCCH candidates that do not overlap with time and frequency domain resources that are announced or configured as UL or are announced or configured for UL transmission.

[0141] In the illustrated example, for PDCCH monitoring occasion #0, frequencyDomainResources-3 is determined to be frequencyDomainResources that include PDCCH candidates that do not overlap with time and frequency domain resources that are notified or configured as UL or that are notified or configured for UL transmission, and the UE may determine the PDCCH candidates using frequencyDomainResources-3.

[0142] Also, for PDCCH monitoring occasion #1, it is determined that the frequencyDomainResources is frequencyDomainResources that includes PDCCH candidates that do not overlap with time and frequency domain resources that are notified or configured as UL or that are notified or configured for UL transmission, and the UE may determine the PDCCH candidates using the frequencyDomainResources.

[0143] As option 5 of the second embodiment, multiple bitmaps of freqMonitorLocations may be configured for an SS set configuration, i.e., multiple bitmaps of freqMonitorLocations are configured for an SS set, where freqMonitorLocations is an IE indicating frequency monitoring locations.

[0144] As Option 5-1 of the second embodiment, separate freqMonitorLocations bitmaps may be configured for pure time units and XDD time units. That is, a frequency domain pattern is selected according to normal TDD operation and XDD operation. For example, in addition to the existing freqMonitorLocations bitmap, a new freqMonitorLocationsForXdd may be configured for the SS set configuration. For each PDCCH monitoring opportunity of the SS set, if the PDCCH monitoring opportunity is not contained in or does not overlap with the 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 contained in or overlaps with the 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 set in the SearchSpaceExt configuration as shown in FIG. 21A.

[0146] Also, in the example shown in FIG. 21B, the UE may monitor PDCCH candidates determined based on freqMonitorLocations in pure time units, and may monitor 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. As an 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 configured, where the value of X may be set to be equal to or less than the number of frequency domain patterns for the configured XDD time unit. The value of X may be specified by a specification or configured in the RRC configuration.

[0149] For example, the IEs freqMonitorLocationsForXdd-1, freqMonitorLocationsForXdd-2, and freqMonitorLocationsForXdd-3 for three additional frequency domain patterns may be set in the SearchSpaceExt configuration, as shown in FIG. 22A.

[0150] Also, as shown in FIG. 22B, the UE may monitor PDCCH candidates determined based on freqMonitorLocations in pure time units, monitor PDCCH candidates determined based on freqMonitorLocationsForXdd-1 in XDD time units with frequency domain pattern type 1, and monitor PDCCH candidates determined based on freqMonitorLocationsForXdd-2 in XDD time units with frequency domain pattern type 2.

[0151] As option 5-2 of the second embodiment, for each PDCCH monitoring occasion of the SS set, the UE may determine the PDCCH candidate by trying the list of freqMonitorLocations until a suitable freqMonitorLocation is selected or until all freqMonitorLocations have been tried, i.e., the UE selects a suitable one from multiple bitmaps according to the SS set.

[0152] For example, for each PDCCH monitoring occasion of the SS set, the UE may first determine PDCCH candidates of the SS set by utilizing a bitmap of the first freqMonitorLocations. If none of the determined PDCCH candidates overlaps with the time and frequency domain resources signaled or configured as UL or for UL transmission, the UE may determine to use the freqMonitorLocations to monitor the determined PDCCH candidates.

[0153] If any of the determined PDCCH candidates overlaps with the time and frequency domain resources that are notified or configured as UL or are notified or configured for UL transmission, the UE may determine a PDCCH candidate by utilizing the next configured freqMonitorLocations until a freqMonitorLocations is detected from which a PDCCH candidate that does not overlap with the time and frequency domain resources that are notified or configured as UL or are notified or configured for UL transmission is obtained.

[0154] If the UE has tried all freqMonitorLocations bitmaps configured for the SS set but has not found a freqMonitorLocations bitmap from which a PDCCH candidate that does not overlap with the time and frequency domain resources signaled or configured as UL or signaled or configured for UL transmission is obtained, the default freqMonitorLocations, the first freqMonitorLocations, or the last freqMonitorLocations may be used to determine the PDCCH candidate. Alternatively, the UE may not consider such a case. Alternatively, the UE may not monitor PDCCH candidates in the PDCCH monitoring occasion.

[0155] For example, the IE freqMonitorLocationsAddForXdd for specifying the trial order of multiple freqMonitorLocations may be set in the SearchSpaceExt configuration as shown in FIG.

[0156] In the example shown in FIG. 24, the UE tries each freqMonitorLocations in the order freqMonitorLocations, freqMonitorLocations-2, and freqMonitorLocations-3 to determine whether each freqMonitorLocations contains PDCCH candidates that do not overlap with the time and frequency domain resources that are reported or configured as UL or are reported or configured for UL transmission.

[0157] In the illustrated example, for PDCCH monitoring occasion #0, freqMonitorLocations-3 is determined to be a freqMonitorLocations that includes PDCCH candidates that do not overlap with time and frequency domain resources that are notified or configured as UL or are notified or configured for UL transmission, and the UE may determine the PDCCH candidates using freqMonitorLocations-3.

[0158] Also, for PDCCH monitoring occasion #1, freqMonitorLocations is determined to be a freqMonitorLocations that includes PDCCH candidates that do not overlap with time and frequency domain resources that are notified or configured as UL or are notified or configured for UL transmission, and the UE may use freqMonitorLocations to determine the PDCCH candidates.

[0159] As option 6 of the second embodiment, different interpretations of the parameters of the SS set and / or CORESET configuration for pure time units and XDD time units may be applied when determining PDCCH candidates, i.e. switching the interpretation of the PDCCH monitoring configuration depending on normal TDD operation and XDD operation.

[0160] For example, for PDCCH monitoring opportunities that are not included in or overlap with an XDD time unit or that do not overlap with an XDD symbol, the freqMonitorLocations in the SS set configuration and / or the frequencyDomainResources in the CORESET configuration may be interpreted based on the frequency resource configuration of the pure time unit, i.e., similar to the interpretation in Rel-15 / 16 / 17.

[0161] For PDCCH monitoring occasions that are included in or overlap with an XDD time unit or that overlap with an XDD symbol, freqMonitorLocations of the SS set configuration and / or frequencyDomainResources of the CORESET configuration may be interpreted based on the frequency domain resources of the overlapping XDD time unit or XDD symbol. For example, for PDCCH monitoring occasions that are included in or overlap with an XDD time unit or that overlap with an XDD symbol, freqMonitorLocations of the SS set configuration and / or frequencyDomainResources of the CORESET configuration may be read as freqMonitorLocationsForXdd and / or frequencyDomainResourcesAddForXdd of the CORESET configuration.

[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 a Type 0-PDCCH CSS set, a Type 0A-PDCCH CSS set, a Type 1-PDCCH CSS set, a Type 2-PDCCH CSS set, a Type 3-PDCCH CSS set, and / or a USS set.

[0163] Thus, according to the second embodiment, the UE may receive a first PDCCH monitoring configuration for non-XDD time units (e.g., pure time units) and a second PDCCH monitoring configuration for XDD time units, and control PDCCH monitoring according to the first PDCCH monitoring configuration and the second PDCCH monitoring configuration. Correspondingly, the base station may configure the first PDCCH monitoring configuration for non-XDD time units and the second PDCCH monitoring configuration for XDD time units, and send the first PDCCH monitoring configuration and the second PDCCH monitoring configuration to the terminal.

[0164] Specifically, the first PDCCH monitoring configuration may be a search space set configuration for a non-XDD time unit (e.g., searchSpaceToAddModList), and the second PDCCH monitoring configuration may be one or more search space set configurations for an XDD time unit (e.g., searchSpaceToAddModListForXDD, searchSpaceToAddModListForXDD1, searchSpaceToAddModListForXDD2, etc.).

[0165] Also, the first PDCCH monitoring configuration may be a CORESET (e.g., controlResourceSetId) configuration for a non-XDD time unit, and the second PDCCH monitoring configuration may be one or more CORESET configurations (e.g., controlResourceSetIdForXdd, controlResourceSetIdForXdd-1, controlResourceSetIdForXdd-2, etc.) for an XDD time unit.

[0166] Furthermore, the first PDCCH monitoring configuration may be a frequency domain resource configuration for non-XDD time units (e.g., frequencyDomainResources), and the second PDCCH monitoring configuration may be one or more frequency domain resource configurations for XDD time units (e.g., frequencyDomainResourcesForXdd, frequencyDomainResourcesForXdd-1, frequencyDomainResourcesForXdd-2, etc.).

[0167] Also, the first PDCCH monitoring configuration may be a frequency monitoring location configuration for non-XDD time units (e.g., freqMonitorLocations), and the second PDCCH monitoring configuration may be one or more frequency monitoring location configurations for XDD time units (e.g., freqMonitorLocationsForXdd, freqMonitorLocationsForXdd-1, freqMonitorLocationsForXdd-2, etc.).

[0168] Additionally, the second PDCCH monitoring configuration described above may indicate a prioritization corresponding to multiple frequency domain patterns.

[0169] Also, the second PDCCH monitoring configuration may be interpreted from the first PDCCH monitoring configuration.

[0170] The above-mentioned configuration or notification may be transmitted based on, for example, at least one of a Radio Resource Control (RRC) information element, a Downlink Control Information (DCI), and a Medium Access Control (MAC) CE. Also, the present disclosure is not limited to monitoring a PDCCH, 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.).

[0171] To realize the above-mentioned 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 configure the UE to perform the XDD operation based on the received UE capability information. Specifically, the UE capability information may be defined as to whether the UE supports different SS set configurations for the XDD time unit and the pure time unit. The UE may transmit the UE capability information related to whether the UE supports different SS set configurations for the XDD time unit and the pure time unit to the base station.

[0172] Also, UE capability information regarding whether the UE supports multiple controlResourceSetIds set for the SS set configuration may be defined. The UE may transmit, to the base station, UE capability information regarding whether the UE supports multiple controlResourceSetIds set for the SS set configuration.

[0173] In addition, 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] Also, UE capability information regarding whether the UE supports a bitmap of multiple freqMonitorLocations set for the SS set configuration may be defined. The UE may transmit the UE capability information regarding whether the UE supports a bitmap of multiple freqMonitorLocations set for the SS set configuration to the base station.

[0175] According to a second embodiment, when XDD operation is signaled, configured or applied to a cell where PDCCH monitoring is configured, UE operation regarding SS set and / or CORESET configuration can be defined.

[0176] (Third Example) There is currently no discussion regarding the PDCCH monitoring operation when the XDD operation is notified, configured, or applied to the cell in which PDCCH monitoring is configured. Therefore, it is necessary to specify the PDCCH monitoring operation when the XDD operation is notified, configured, or applied to the cell in which PDCCH monitoring is configured. That is, for PDCCH monitoring, the UE may perform the following operations:

[0177] It should be noted that the third embodiment is independent of the second embodiment, i.e., any option of the third embodiment may be applied together with any option of the second embodiment.

[0178] As an option 1 of the third embodiment, the UE may assume that the PDCCH monitoring opportunities of the PDCCH SS set do not overlap with the XDD symbols. That is, the UE may assume that 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 (symbols #0 and #1) in the slot overlap with the XDD symbols, which is an error case.

[0179] As option 2 of the third embodiment, the UE may assume that the PDCCH monitoring opportunities of the PDCCH SS set are included in or do not overlap XDD time units. That is, the UE may assume that the PDCCH monitoring does not overlap XDD time units. In this case, for example, in the example shown in Figure 26, the time unit is a slot, and the PDCCH monitoring opportunities are included in XDD slots, which is an error case.

[0180] As option 3 of the third embodiment, the case where the PDCCH monitoring occasions of the PDCCH SS set are included in or overlap with the XDD time unit is considered. That is, when the PDCCH monitoring overlaps with the XDD resource, the UE may perform the following operations:

[0181] As option 3-1 of the third embodiment, if a PDCCH monitoring occasion of the PDCCH SS set is included in or overlaps with an XDD time unit, the UE may not monitor a PDCCH candidate in the PDCCH monitoring occasion, regardless of whether the PDCCH monitoring occasion overlaps with an XDD symbol, i.e., the UE avoids PDCCH monitoring.

[0182] For example, in the example shown in Figure 27, slot A is an XDD slot, so the UE may not monitor PDCCH candidates in slot A. On the other hand, slot B is a pure DL slot, so the UE may monitor PDCCH candidates in slot B.

[0183] As option 3-2 of the third embodiment, when the PDCCH monitoring occasion of the PDCCH SS set is included in or overlaps with the XDD time unit, the UE determines whether to monitor the PDCCH candidate in the PDCCH monitoring occasion based on whether the PDCCH monitoring occasion overlaps with the XDD symbol. That is, the UE may determine whether to perform monitoring depending on whether the XDD resource overlaps. When the PDCCH monitoring occasion of the PDCCH SS set overlaps with the XDD symbol, the UE may not monitor the PDCCH candidate in the PDCCH monitoring occasion. On the other hand, when the PDCCH monitoring occasion of the PDCCH SS set does not overlap with the XDD symbol, the UE may monitor the PDCCH candidate in the PDCCH monitoring occasion.

[0184] For example, in the example shown in Figure 28, the PDCCH monitoring opportunities (symbols #0, #1, #4, #5) of slot A do not overlap with the XDD symbols, so the UE may monitor PDCCH candidates in the PDCCH monitoring opportunities (symbols #0, #1, #4, #5) of slot A. On the other hand, the first PDCCH monitoring opportunity (symbols #0, #1) of slot B overlaps with the XDD symbols, so the UE may not monitor PDCCH candidates in the first PDCCH monitoring opportunity (symbols #0, #1) of slot B. The second PDCCH monitoring opportunity (symbols #4, #5) of slot B does not overlap with the XDD symbols, so the UE may monitor PDCCH candidates in the second PDCCH monitoring opportunity (symbols #4, #5) of slot B.

[0185] As option 3-3 of the third embodiment, when the PDCCH monitoring occasions of the PDCCH SS set are included in or overlap with the XDD time unit, the UE may determine whether to monitor the PDCCH candidate in the PDCCH monitoring occasion that overlaps with the XDD symbol based on whether the PDCCH candidate overlaps with the time and frequency domain resource that is signaled or configured as UL or is signaled or configured for UL transmission. That is, the UE may make the determination depending on whether UL is configured for the XDD resource.

[0186] As option 3-3A of the third embodiment, if the PDCCH monitoring occasions of a PDCCH SS set are contained within or overlap with an XDD time unit, for the PDCCH candidates in the PDCCH monitoring occasions for the PDCCH SS set, the UE may assume that none of the PDCCH candidates overlap with the time and frequency domain resources that are signaled or configured as UL or are signaled or configured for UL transmission, i.e., the UE may monitor the PDCCH candidates in the PDCCH monitoring occasions similar to Rel-15 / 16.

[0187] For example, in the example shown in FIG. 29, the first PDCCH monitoring opportunity (symbols #0 and #1) overlaps with the time and frequency domain resources set as UL, which results in an error case.

[0188] As option 3-3B of the third embodiment, when the PDCCH monitoring occasions of the PDCCH SS set are included in or overlap with the XDD time unit, for a PDCCH candidate in a PDCCH monitoring occasion for the PDCCH SS set, if the PDCCH candidate does not overlap with the time and frequency domain resources that are signaled or configured as UL or are signaled or configured for UL transmission, the UE may monitor the PDCCH candidate. On the other hand, if the PDCCH candidate overlaps with the time and frequency domain resources that are signaled or configured as UL or are signaled or configured for UL transmission, the UE may not monitor the PDCCH candidate.

[0189] For example, in the example shown in Figure 30, the first PDCCH monitoring occasion (symbols #0, #1) overlaps with the time and frequency domain resources configured as UL, so the UE may not monitor PDCCH candidates during the first PDCCH monitoring occasion, whereas the second PDCCH monitoring occasion (symbols #4, #5) does not overlap with the time and frequency domain resources configured as UL, so the UE may monitor PDCCH candidates during the second PDCCH monitoring occasion.

[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) Type 0A-PDCCH CSS set configured by searchSpaceOtherSystemInformation in PDCCH-ConfigCommon iii) Type1-PDCCH CSS set configured by ra-SearchSpace in PDCCH-ConfigCommon iv) Type 2-PDCCH CSS set configured by pagingSearchSpace in PDCCH-ConfigCommon v) Type 3-PDCCH CSS set configured by SearchSpace in PDCCH-Config with searchSpaceType = common and / or vi) USS set configured by SearchSpace in PDCCH-Config with searchSpaceType=ue-Specific It may be either of the above.

[0191] Also, different options may be applied to different PDCCH SS set types, for example, Option 1 / 2 may be applied to the Type0-PDCCH CSS set, and Option 3 may be applied to the USS set.

[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 for which a specific DCI format is configured. For example, the SS set may be a USS set for 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.

[0193] Also, different options may be applied to PDCCH SS sets for which different DCI formats are configured.

[0194] In this way, according to the third embodiment, the UE may receive the PDCCH search space configuration and control PDCCH monitoring according to the PDCCH search space configuration in XDD operation. Correspondingly, the base station may configure the PDCCH search space configuration in XDD operation and send the PDCCH search space configuration.

[0195] Specifically, the UE may assume that the PDCCH monitoring occasions indicated by the PDCCH search space configuration do not overlap with XDD time units (eg, XDD symbols, XDD slots, etc.).

[0196] The UE may also avoid PDCCH monitoring in a PDCCH monitoring occasion indicated by the PDCCH search space configuration if the PDCCH monitoring occasion overlaps with an XDD time unit.

[0197] In addition, when a PDCCH monitoring opportunity indicated by a 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 the XDD time unit.

[0198] In addition, if the PDCCH monitoring opportunity indicated by the PDCCH search space configuration 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 the radio resources (i.e., time and frequency resources) for uplink transmission.

[0199] The above-mentioned configuration or notification may be transmitted based on, for example, at least one of a Radio Resource Control (RRC) information element, a Downlink Control Information (DCI), and a Medium Access Control (MAC) CE. Also, the present disclosure is not limited to monitoring a PDCCH, 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 realize the above-mentioned 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 configure the UE for the XDD operation based on the received UE capability information. Specifically, the UE capability information may be defined as to whether the UE supports a case in which the PDCCH monitoring occasion overlaps with the XDD time unit or the XDD symbol. The UE may transmit the UE capability information related to whether the PDCCH monitoring occasion overlaps with the XDD time unit or the XDD symbol to the base station.

[0201] Also, UE capability information regarding whether the UE supports monitoring PDCCH candidates in PDCCH monitoring occasions that include or overlap XDD time units or XDD symbols may be specified. The UE may transmit UE capability information regarding whether it supports monitoring PDCCH candidates in PDCCH monitoring occasions that include or overlap XDD time units or XDD symbols to the base station.

[0202] According to a third embodiment, if an XDD operation is signaled, configured or applied to a cell in which PDCCH monitoring is configured, a UE operation regarding PDCCH monitoring can be defined.

[0203] (Fourth Example) Currently, there is no discussion regarding PDCCH monitoring capabilities and BD / CCE restrictions when XDD operation is signaled, configured, or applied to a cell in which PDCCH monitoring is configured. Therefore, it is necessary to specify UE behavior regarding PDCCH monitoring capabilities and BD / CCE restrictions when XDD operation is signaled, configured, or applied to a cell in which PDCCH monitoring is configured.

[0204] In the fourth embodiment-1, the PDCCH monitoring capability of the XDD SS set or the XDD PDCCH monitoring opportunity may be the same as or different from the existing PDCCH monitoring indication or configuration. That is, the PDCCH monitoring capability may be configured by any of the following methods:

[0205] As Option 1 of the fourth embodiment-1, the capability notification, configuration, or provision for PDCCH monitoring on the BWP or cell may be unified. That is, a common PDCCH monitoring capability may be configured for normal TDD operation and XDD operation. The capability notification, configuration, or provision for PDCCH monitoring on the BWP or cell may be based on the configuration by monitoringCapabilityConfig-r16 or monitoringCapabilityConfig-r17.

[0206] As a variation of Option 1, it may be assumed that if a BWP or cell is signaled or configured for XDD operation, then the PDCCH-Config of the BWP or cell is not signaled or configured as Rel-15 slot-wise PDCCH monitoring capability, Rel-16 span-wise PDCCH monitoring capability and / or Rel-17 multi-slot PDCCH monitoring capability.

[0207] As an example, if a BWP or cell is signaled or configured for XDD operation, the UE may not expect monitoringCapabilityConfig-r16=r15monitoringcapability or monitoringCapabilityConfig-r17=r15monitoringcapability to be configured for the PDCCH-Config on the BWP or cell, or alternatively, neither monitoringCapabilityConfig-r16 nor monitoringCapabilityConfig-r17 may be configured for the PDCCH-Config on the BWP or cell.

[0208] As another example, if a BWP or cell is signaled or configured for XDD operation, the UE may not 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 signaled or configured for XDD operation, the UE may not assume that monitoringCapabilityConfig-r17=r17monitoringcapability is configured for the PDCCH-Config on the BWP or cell.

[0210] Here, an XDD SS set refers to an SS set configured for an XDD time unit, a non-XDD SS set refers to an SS set configured for a pure time unit, an XDD PDCCH monitoring occasion refers to a PDCCH opportunity that includes or overlaps an XDD time unit or an XDD symbol, and a non-XDD PDCCH monitoring occasion refers to a PDCCH monitoring opportunity that does not include or overlap an XDD time unit or an XDD symbol.

[0211] As Option 2 of Example 4-1, separate PDCCH monitoring capabilities may be signaled, configured, or defined for monitoring an XDD SS set and a non-XDD SS set on a BWP or a cell, or separate PDCCH monitoring capabilities may be signaled, configured, or defined for XDD PDCCH monitoring opportunities and non-XDD PDCCH monitoring opportunities on a BWP or a cell. That is, PDCCH monitoring capabilities may be configured for normal TDD operation and XDD operation, respectively.

[0212] The monitoringCapabilityConfig-r16 or monitoringCapabilityConfig-r17 may be reused to signal or configure the PDCCH monitoring capability of Rel-15 / 16 / 17 for non-XDD SS sets or non-XDD PDCCH monitoring occasions.

[0213] Also, a new RRC parameter monitoringCapabilityConfigForXdd may be reused to signal or configure the PDCCH monitoring capability of Rel-15 / 16 / 17 for monitoring the XDD SS set or XDD PDCCH monitoring occasions.

[0214] For example, for the candidate values ​​of the new RRC parameter monitoringCapabilityConfigForXdd, r15monitoringcapability, r16monitoringcapability and / or r17monitoringcapability may be possible. Specifically, monitoringCapabilityConfigForXdd may have the following values: monitoringCapabilityConfigForXdd={r15monitoringcapability,r16monitoringcapability,r17monitoringcapability} monitoringCapabilityConfigForXdd={r15monitoringcapability,r16monitoringcapability} monitoringCapabilityConfigForXdd={r15monitoringcapability,r17monitoringcapability} monitoringCapabilityConfigForXdd={r16monitoringcapability,r17monitoringcapability}

[0215] Also, if no new RRC parameters are configured for monitoring the XDD SS set or XDD PDCCH monitoring occasions, the UE may take the following actions.

[0216] As a first action, if no new RRC parameters are configured for monitoring the XDD SS set or XDD PDCCH monitoring occasion, the UE may follow the same PDCCH monitoring capability as signaled or configured by monitoringCapabilityConfig-r16 or monitoringCapabilityConfig-r17 for monitoring the XDD SS set or XDD PDCCH monitoring occasion.

[0217] As a second operation, if no new RRC parameters are configured for monitoring an XDD SS set or an XDD PDCCH monitoring occasion, the UE may apply a default PDCCH monitoring capability for monitoring an XDD SS set or an XDD PDCCH monitoring occasion, for example, the default PDCCH monitoring capability may be the slot-wise PDCCH monitoring capability of Rel-15, the span-wise PDCCH monitoring capability of Rel-16, or the multi-slot PDCCH monitoring capability of Rel-17.

[0218] As a third action, if a specific PDCCH monitoring capability is signaled or configured by monitoringCapabilityConfig-r16 or monitoringCapabilityConfig-r17, the default PDCCH monitoring capability for monitoring an XDD SS set or an XDD PDCCH monitoring occasion may always be the Rel-15 slot-wise PDCCH monitoring capability, the Rel-16 span-wise PDCCH monitoring capability, or the Rel-17 multi-slot PDCCH monitoring capability. Otherwise, the UE may follow the same PDCCH monitoring capability signaled or configured by monitoringCapabilityConfig-r16 or monitoringCapabilityConfig-r17 for monitoring an XDD SS set or an XDD PDCCH monitoring occasion.

[0219] As a variation of option 2 of Example 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 a non-XDD PDCCH monitoring opportunity is signaled by monitoringCapabilityConfig-r16 or monitoringCapabilityConfig-r17, nor does it assume that a specific PDCCH monitoring capability (e.g., Rel-15 / 16 / 17 monitoring capability) for a non-XDD SS set or a non-XDD PDCCH monitoring opportunity is configured or specified at the same time.

[0220] In Example 4-2, for the maximum number of blind decoding (BD) or control channel element (CCE) limits, PDCCH candidates or non-overlapping CCEs for the monitored XDD SS set and the monitored non-XDD SS set, or PDCCH candidates or non-overlapping CCEs for the monitored XDD PDCCH monitoring occasions and the monitored non-XDD PDCCH monitoring occasions, may be counted separately or together. That is, the upper limit of BDs / CCEs may be counted in any of the following ways. The term "monitored" here is intended to include the possibility that PDCCH candidates that are determined not to be monitored (e.g., according to Example 3 and / or the rules of Rel-15 / 16) may or may not be counted toward the BD or CCE constraints.

[0221] As a first operation, 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 opportunities and the monitored non-XDD PDCCH monitoring opportunities, for the maximum number of BDs or CCEs, i.e., the number of PDCCH candidates or non-overlapping CCEs may be counted separately for normal TDD operation and XDD operation.

[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 monitored non-XDD SS set or monitored non-XDD PDCCH monitoring opportunity may be counted per slot, per span, or per group of X slots, where per slot, per span, or per group of X slots may be based on the configuration in monitoringCapabilityConfig-r16 or monitoringCapabilityConfig-r17. Also, the maximum number of BDs or CCEs per slot, per span, or per group of X slots may be, 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 those specified in Rel-15 / 16 / 17, or may be more or less.

[0223] For example, when Rel-15 per-slot monitoring capability is signaled (e.g., monitoringCapabilityConfig-r16=r15monitoringcapability or monitoringCapabilityConfig-r17=r15monitoringcapability is provided to the UE, or neither monitoringCapabilityConfig-r16 nor monitoringCapabilityConfig-r17 is configured), the number of PDCCH candidates or non-overlapping CCEs in the monitored non-XDD SS set or the monitored non-XDD PDCCH monitoring opportunity is counted per slot, and the maximum number of BDs or CCEs is {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 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 based on Example 4-1. Also, the maximum number of BD or CCE limits per slot, per span, or per group of X slots may be, 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 those specified in Rel-15 / 16 / 17, or may be more or less.

[0225] For example, if Rel-15 per-slot monitoring capability is signaled (e.g., monitoringCapabilityConfigForXdd=r16monitoringcapability is provided to the UE), the number of PDCCH candidates or non-overlapping CCEs for the monitored XDD SS set or monitored XDD PDCCH monitoring occasions may be counted per span, and the maximum number of BDs or CCEs limit is {M2 PDCCH max,(X,Y),μ ,C2 PDCCH max,(X,Y),μ} may also be used.

[0226] As a variant, (M1 PDCCH max,slot,μ +M2 PDCCH max,slot,μ ) is the M defined in Rel-15 PDCCH max,slot,μIt may be the same as, or may be greater or less than, (C1 PDCCH max,slot,μ +C2 PDCCH max,slot,μ ) is the M defined in Rel-15 PDCCH max,slot,μ may be the same as, or may be greater or less than,

[0227] As another variation, (M1 PDCCH max,(X,Y),μ +M2 PDCCH max,(X,Y),μ ) is the M defined in Rel-16 PDCCH max,(X,Y),μ It may be the same as, or may be greater or less than, (C1 PDCCH max,(X,Y),μ +C2 PDCCH max,(X,Y),μ ) is the M defined in Rel-16 PDCCH max,(X,Y),μ may be the same as, or may be greater or less than,

[0228] As another variation, (M1 PDCCH max,Xsslot,μ +M2 PDCCH max,Xsslot,μ ) is M defined in Rel-17 PDCCH max,Xsslot,μ It may be the same as, or may be greater or less than, (C1 PDCCH max,Xsslot,μ +C2 PDCCH max,Xsslot,μ ) is M defined in Rel-17 PDCCH max,Xsslot,μ may be the same as, or may be greater or less than,

[0229] For example, the example shown in Figure 31A is for the PDCCH monitoring capability per slot of Rel-15. XDD USS#1 and XDD USS#3 are XDD PDCCH monitoring opportunities to be monitored, and the maximum number of BD or CCE limits is {M2 PDCCH max,slot,μ ,C2 PDCCH max,slot,μ}. Non-XDD USS#2 and non-XDD CSS#1 are non-XDD PDCCH monitoring opportunities to be monitored, and the maximum number of BD or CCE limits is {M1 PDCCH max,slot,μ ,C1 PDCCH max,slot,μ}.

[0230] For example, the example shown in Figure 31B also relates to the Rel-15 per-slot PDCCH monitoring capability. USS#1 and USS#3 are non-XDD PDCCH monitoring opportunities to be monitored, and the maximum number of BDs or CCEs 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 occasions and the monitored non-XDD PDCCH monitoring occasions, for the maximum number of BDs or CCEs, i.e., for normal TDD operation and XDD operation.

[0232] 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 opportunities and the monitored non-XDD PDCCH monitoring opportunities may be counted 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 depend on the granularity or unit (i.e., slot level, span level, or slot group level) of the monitoring capability signaled or configured for a non-XDD SS set or a non-XDD PDCCH monitoring occasion (e.g., by monitoringCapabilityConfig-r16 and / or monitoringCapabilityConfig-r17) and the monitoring capability signaled, configured, or specified for an XDD SS set or an XDD PDCCH monitoring occasion (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] When the granularity / unit for a non-XDD SS set or non-XDD PDCCH monitoring occasion (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 occasion (i.e., slot level, span level, or slot group level), the granularity or unit may be used to count the number of PDCCH candidates or non-overlapping CCEs. On the other hand, when the granularity / unit for a non-XDD SS set or non-XDD PDCCH monitoring occasion (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 occasion (i.e., slot level, span level, or slot group level), a larger granularity or unit may be used to count the number of PDCCH candidates or non-overlapping CCEs.

[0235] For BWP or PDCCH monitoring on a cell, the maximum number of BDs or CCEs per slot, per span, or per group of X slots can be, for example, {M' PDCCH max,slot,μ ,C´ PDCCH max,slot,μ}, {M´ PDCCH max,(X,Y),μ ,C´ PDCCH max,(X,Y),μ} or {M´ PDCCH max,Xsslot,μ ,C´ PDCCH max,Xsslot,μ} may be constant or variable.

[0236] For example, the value of the maximum number of BDs or CCEs limit per slot, per span or per group of X slots may vary depending on whether the slot, span or group of X slots includes or overlaps XDD time units or XDD symbols, whether it includes any monitored XDD PDCCH monitoring opportunities, or whether it includes any PDCCH candidates in the monitored XDD SS set.

[0237] As an example, the XDD slot {M2´ PDCCH max,slot,μ ,C2´ PDCCH max,slot,μ} is in the non-XDD slot {M1´ PDCCH max,slot,μ ,C1´ PDCCH max,slot,μ} may be different.

[0238] Another example is the {M2´ PDCCH max,(X,Y),μ ,C2´ PDCCH max,(X,Y),μ} is a non-XDD span {M1´ PDCCH max,(X,Y),μ ,C1´ PDCCH max,(X,Y),μ} may be different.

[0239] Another example is the XDD slot group {M2´ PDCCH max,Xsslot,μ ,C2´ PDCCH max,Xsslot,μ} is a non-XDD slot group {M1´ PDCCH max,Xsslot,μ ,C1´ PDCCH max,Xsslot,μ} may be different.

[0240] In one variation, the maximum number of BD or CCE limits for a non-XDD slot, non-XDD span or non-XDD slot group may be the same as the maximum number of BD or CCE limits specified in Rel-15 / 16 / 17, or may be greater or less.

[0241] For example, the example shown in Figure 33A is for the PDCCH monitoring capability per slot 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 BDs or CCEs is {M1' PDCCH max,slot,μ ,C1´ PDCCH max,slot,μ}.

[0242] Also, for example, the example shown in Figure 33B also relates to the PDCCH monitoring capability per slot 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 BDs or CCEs is {M2' PDCCH max,slot,μ ,C2´ PDCCH max,slot,μ}.

[0243] Also, for example, the value of 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 signaled or configured for XDD operation may be the same as the maximum number of BD or CCE limits specified in Rel-15 / 16 / 17, or may be greater or less.

[0244] For example, the example shown in Figure 34A is for the Rel-15 slot-by-slot PDCCH monitoring capability, 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 BDs or CCE limits for cell #1 is {M2' PDCCH max,slot,μ ,C2´ PDCCH max,slot,μ}, and the maximum number of BD or CCE limits of cell #2 is {M1' PDCCH max,slot,μ ,C1´ PDCCH max,slot,μ}.

[0245] Also, for example, the example shown in Figure 34B also relates to the PDCCH monitoring capability per slot 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 BDs or CCE limits for cell #1 is {M2' PDCCHmax,slot,μ ,C2´ PDCCH max,slot,μ}, and the maximum number of BD or CCE limits of cell #2 is {M1' PDCCH max,slot,μ ,C1´ PDCCH max,slot,μ}.

[0246] In this way, according to the fourth embodiment, the UE may receive a PDCCH monitoring capability (e.g., monitoringCapabilityConfig) for XDD operation on a radio resource (e.g., a cell, a BWP, etc.) and control PDCCH monitoring according to the PDCCH monitoring capability. Correspondingly, the base station may configure the PDCCH monitoring capability for XDD operation on the radio resource and transmit the PDCCH monitoring capability.

[0247] Specifically, the PDCCH monitoring capability may be configured commonly for XDD and non-XDD operation.

[0248] Additionally, PDCCH monitoring capabilities may be configured separately for XDD and non-XDD operation.

[0249] The UE may also 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 jointly.

[0250] The above-mentioned configuration or notification may be transmitted based on, for example, at least one of a Radio Resource Control (RRC) information element, a Downlink Control Information (DCI), and a Medium Access Control (MAC) CE. Also, the present disclosure is not limited to monitoring a PDCCH, 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.).

[0251] To implement the above-mentioned XDD operation, the UE transmits UE capability information related to the XDD operation to the base station, and the base station may notify or configure the UE for the XDD operation based on the received UE capability information. Specifically, UE capability information related to whether the UE supports unified capability notification, configuration, or provision for monitoring the XDD SS set (or XDD PDCCH monitoring occasion) and the non-XDD SS set (or XDD PDCCH monitoring occasion) may be defined. The UE may transmit UE capability information related to whether the UE supports unified capability notification, configuration, or provision for monitoring the XDD SS set (or XDD PDCCH monitoring occasion) and the non-XDD SS set (or XDD PDCCH monitoring occasion) to the base station.

[0252] Also, UE capability information regarding whether the UE supports separate capability indications, settings, or provisions for monitoring the XDD SS set (or XDD PDCCH monitoring occasions) may be defined. The UE may transmit UE capability information regarding whether the UE supports separate capability indications, settings, or provisions for monitoring the XDD SS set (or XDD PDCCH monitoring occasions) to the base station.

[0253] Also, UE capability information regarding whether the UE supports separate PDCCH candidates and non-overlapping CCE counts for monitoring an XDD SS set (or XDD PDCCH monitoring occasion) and a non-XDD SS set (or XDD PDCCH monitoring occasion) may be specified. The UE may transmit UE capability information regarding whether it supports separate PDCCH candidates and non-overlapping CCE counts for monitoring an XDD SS set (or XDD PDCCH monitoring occasion) and a non-XDD SS set (or XDD PDCCH monitoring occasion) to the base station.

[0254] Also, UE capability information regarding whether the UE supports joint PDCCH candidates and non-overlapping CCE counts for monitoring an XDD SS set (or XDD PDCCH monitoring occasion) and a non-XDD SS set (or XDD PDCCH monitoring occasion) may be specified. The UE may transmit UE capability information regarding whether it supports joint PDCCH candidates and non-overlapping CCE counts for monitoring an XDD SS set (or XDD PDCCH monitoring occasion) and a non-XDD SS set (or XDD PDCCH monitoring occasion) to the base station.

[0255] According to the fourth embodiment, when XDD operation is signaled, configured or applied to a cell in which PDCCH monitoring is configured, UE behavior regarding PDCCH monitoring capability and BD / CCE limits can be specified.

[0256] (Fifth Example) There is currently no discussion regarding PDCCH overbooking when XDD operation is signaled, configured, or applied to a cell in which PDCCH monitoring is configured. Therefore, it is necessary to specify UE behavior regarding PDCCH overbooking when XDD operation is signaled, configured, or applied to a cell in which PDCCH monitoring is configured. That is, PDCCH overbooking is specified for XDD operation.

[0257] In a fifth embodiment, for cells where XDD operation is notified or configured, overbooking is allowed or not allowed for slots, spans or groups of X slots that include or overlap an XDD time unit or XDD symbol, for slots, spans or groups of X slots that include an XDD SS set to be monitored, or for slots, spans or groups of X slots that include an XDD PDCCH monitoring opportunity to be monitored.

[0258] In Example 1, for Rel-15 slot-wise PDCCH monitoring capability, overbooking may or may not be allowed as follows: Here, XDD slot may refer to a slot that includes or overlaps an XDD time unit or XDD symbol, includes an XDD SS set to be monitored, and / or includes an XDD PDCCH monitoring opportunity to be monitored.

[0259] As a specific example 1-1, when XDD operation is signaled or configured for 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 slot. That is, as a difference from Rel-15, when XDD operation is signaled or configured for a Pcell or PScell, overbooking on the Pcell or PScell ​​may not be assumed.

[0260] As an example 1-2, if the slot is an XDD slot, the UE may not assume that a number of PDCCH candidates greater than the BD or CCE limit for the cell is monitored in the slot.

[0261] As specific examples 1-3, if a number of PDCCH candidates greater than the BD or CCE limit is monitored in a slot, the UE may drop certain PDCCH candidates in the slot while the BD or CCE limit for the cell is not exceeded if the cell is signaled or configured for XDD operation. That is, as a difference from Rel-15, if the Scell ​​is signaled or configured for XDD operation, overbooking may be allowed on the Scell.

[0262] As specific examples 1-4, if a number of PDCCH candidates greater than the BD or CCE limit is monitored in a slot, the UE may drop certain PDCCH candidates in the slot if the cell is an XDD slot, as long as the BD or CCE limit for that cell is not exceeded.

[0263] As a variation, the value of the BD or CCE limit for the Scell ​​may be the same as or different from the value of the BD or CCE limit specified in the Rel-15 monitoring capabilities for the Pcell or PScell.

[0264] As another variation, the values ​​of the BD or CCE limits for a cell with XDD operation may be the same as or different from the values ​​of the BD or CCE limits specified in the Rel-15 monitoring capabilities for a Pcell or PScell.

[0265] As another variation, the value of the BD or CCE limit for the XDD slot may be the same as or different from the value of the BD or CCE limit specified in the Rel-15 monitoring capability for the Pcell or PScell.

[0266] In Example 2, for Rel-16 span-based PDCCH monitoring capabilities, overbooking may or may not be allowed as follows: Here, XDD span may refer to a span that includes or overlaps XDD time units or XDD symbols, includes an XDD SS set to be monitored, and / or includes an XDD PDCCH monitoring opportunity to be monitored.

[0267] As a specific example 2-1, when XDD operation is signaled or configured for 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 span. That is, as a difference from Rel-16, when XDD operation is signaled or configured for a Pcell or PScell, overbooking on the Pcell or PScell ​​may not be assumed.

[0268] As an example 2-2, if the span is an XDD span, the UE may not assume that a number of PDCCH candidates greater than the BD or CCE limit for the cell is monitored in the span.

[0269] As an example 2-3, when a number of PDCCH candidates longer than the BD or CCE limit is monitored in a span (or the first span in a slot), if the XDD operation is signaled or configured for the cell (or Pcell / PScell), the UE may drop certain PDCCH candidates in the span while the BD or CCE limit for the cell (or Pcell / PScell) is not exceeded. That is, as a difference from Rel-16, if the XDD operation is signaled or configured for the Scell, overbooking may be allowed on the Scell. Also, if the XDD operation is signaled or configured for the cell, overbooking may be allowed on spans other than the first span in a slot.

[0270] As an example 2-4, if a number of PDCCH candidates greater than the BD or CCE limit is monitored in a span (or the first span in a slot), the UE may drop certain PDCCH candidates in the span if 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 a variant, the value of the BD or CCE limit for a span other than the first span in a slot on a Pcell / PScell ​​may be the same as or different from the value of the BD or CCE limit specified in Rel-16 for the first span in a slot on a Pcell or PScell.

[0272] As another variation, the values ​​of the BD or CCE limits for a cell with XDD operation may be the same as or different from the values ​​of the BD or CCE limits specified in the Rel-16 monitoring capabilities for a Pcell or PScell.

[0273] In another variation, the value of the BD or CCE limit for the first span in a slot on an Scell ​​may be the same as or different from the value of the BD or CCE limit specified in Rel-16 for the first span in a slot on a Pcell or PScell.

[0274] In another variation, the value of the BD or CCE limit for a span other than the first span in a slot on an Scell ​​may be the same as or different from the value of the BD or CCE limit specified in Rel-16 for the first span in a slot on a Pcell or PScell.

[0275] As another variation, the values ​​of the BD or CCE limits for the XDD span may be the same as or different from the values ​​of the BD or CCE limits specified in Rel-16 for the Pcell or PScell.

[0276] In Example 3, for Rel-17 multi-slot PDCCH monitoring capability, overbooking may or may not be allowed as follows: Here, XDD slot group may refer to a group of X slots (group of X_s slots) that includes or overlaps XDD time units or XDD symbols, includes an XDD SS set to be monitored, and / or includes an XDD PDCCH monitoring opportunity to be monitored.

[0277] As a specific example 3-1, when XDD operation is signaled or configured for a cell, the UE may not assume that a number of PDCCH candidates greater than the BD or CCE limit for that cell will be monitored in a group of X slots. That is, as a difference from Rel-17, when XDD operation is signaled or configured for a Pcell, overbooking on the Pcell may not be assumed.

[0278] As an 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 greater than the BD or CCE limit for the cell is monitored in the group of X slots.

[0279] As an example 3-3, if a number of PDCCH candidates greater than the BD or CCE limit is monitored in a group of X slots, the UE may drop certain PDCCH candidates in the group of X slots when XDD operation is signaled or configured for the (primary) cell, as long as the BD or CCE limit for the (primary) cell is not exceeded. That is, as a difference from Rel-17, when XDD operation is signaled or configured for the Scell, overbooking may be allowed on the Scell.

[0280] As an example 3-4, if a number of PDCCH candidates greater than the BD or CCE limit is monitored in a group of X slots, the UE may drop certain PDCCH candidates in the group of X slots if the group of X slots is an XDD slot group, while the BD or CCE limit for that (primary) cell is not exceeded.

[0281] As a variant, the value of the BD or CCE limit for the Scell ​​may be the same as or different from the value of the BD or CCE limit specified in the Rel-17 monitoring capability for the primary cell.

[0282] As another variation, the values ​​of the BD or CCE limits for a cell with XDD operation may be the same as or different from the values ​​of the BD or CCE limits specified in the Rel-17 monitoring capabilities for a Pcell or PScell.

[0283] As another variation, the values ​​of the BD or CCE limits for the XDD slot group may be the same as or different from the values ​​of the BD or CCE limits specified in the Rel-17 monitoring capabilities for the primary cell.

[0284] In this way, according to the fifth embodiment, the UE may control PDCCH overbooking in the XDD time unit in which PDCCH monitoring is configured, and perform PDCCH monitoring in PDCCH monitoring opportunities selected in the controlled PDCCH overbooking. That is, the UE may drop some PDCCH monitoring opportunities from the overbooked PDCCH monitoring opportunities. Correspondingly, the base station may configure overbooked PDCCH monitoring opportunities in the XDD time unit in which PDCCH monitoring is configured, and transmit control information in the PDCCH monitoring opportunities.

[0285] The above-mentioned configuration or notification may be transmitted based on, for example, at least one of a Radio Resource Control (RRC) information element, a Downlink Control Information (DCI), and a Medium Access Control (MAC) CE. Also, the present disclosure is not limited to monitoring a PDCCH, 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.).

[0286] To implement the above-mentioned XDD operation, the UE transmits UE capability information related to the XDD operation to the base station, and the base station may notify or configure the UE for 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 related to 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 related to whether the UE supports PDCCH overbooking on the cell to the base station.

[0287] In addition, UE capability information regarding whether the UE supports PDCCH overbooking in an XDD slot, an XDD span, or an XDD slot group may be specified. The UE may transmit UE capability information regarding whether it supports PDCCH overbooking in an XDD slot, an XDD span, or an XDD slot group to the base station.

[0288] Also, UE capability information regarding whether the UE supports PDCCH overbooking by considering an XDD SS set (or XDD PDCCH monitoring occasion) and a non-XDD SS set (or XDD PDCCH monitoring occasion) may be specified. The UE may transmit UE capability information regarding whether it supports PDCCH overbooking by considering an XDD SS set (or XDD PDCCH monitoring occasion) and a non-XDD SS set (or XDD PDCCH monitoring occasion) to the base station.

[0289] According to the fifth embodiment, when XDD operation is signaled, configured or applied to a cell in which PDCCH monitoring is configured, UE operation regarding PDCCH overbooking can be defined.

[0290] (Sixth Example) There is currently no discussion regarding PDCCH overbooking when XDD operation is notified, configured, or applied to a cell in which PDCCH monitoring is configured. Therefore, it is necessary to specify UE behavior regarding PDCCH overbooking when XDD operation is notified, configured, or applied to a cell in which PDCCH monitoring is configured. That is, a PDCCH overbooking rule may be specified for XDD operation. Specifically, for the PDCCH overbooking allowed in the fifth embodiment, a UE behavior is specified for selecting a PDCCH monitoring opportunity to be monitored / dropped from the overbooked PDCCH monitoring opportunities.

[0291] In a sixth embodiment, if a slot, span or group of X slots contains or overlaps XDD time units or XDD symbols, contains any XDD SS sets to be monitored, or contains any XDD PDCCH monitoring opportunities to be monitored, overbooking may be allowed for that slot, span or group of X slots.

[0292] As an option 0 of the sixth embodiment, the existing PDCCH overbooking rules of Rel-15 / 16 / 17 may be reused, i.e., the rules of Rel-15 / 16 / 17 are applied.

[0293] As option 1 of the sixth embodiment, overbooking may be considered whether it is an XDD SS set or a non-XDD SS set.

[0294] In option 1-1 of the sixth embodiment, the following prioritization may be applied: "CSS has higher priority than USS" → "non-XDD SS set has higher or lower priority than XDD SS set" → "smaller SS index has higher priority than larger SS index."

[0295] As Option 1-1A of the sixth embodiment, a non-XDD CSS may not be expected to be dropped. The XDD CSS, non-XDD USS, and XDD USS may be dropped based on priority. For example, the UE may not expect the number of PDCCH candidates or non-overlapping CCEs of a non-XDD CSS in any slot / span / group of X slots to exceed the BD or CCE limit. Also, as a variant, the XDD CSS may not be expected to be dropped. The non-XDD CSS, XDD USS, and non-XDD USS may be dropped based on priority.

[0296] As an 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 PDCCH candidates or non-overlapping CCEs of non-XDD CSS and XDD CSS in any slot / span / group of X slots to exceed the BD or CCE limit. Also, as a variant, 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 PDCCH candidates or non-overlapping CCEs for non-XDD CSS, XDD CSS, and non-XDD USS in any slot / span / group of X slots to exceed the BD or CCE limit. Also, as a variant, 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 variation 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 FIG.

[0299] In option 1-2 of the sixth embodiment, the following prioritization may be applied: "non-XDD SS sets have higher or lower priority than XDD SS sets" → "CSS has higher priority than USS" → "smaller SS index has higher priority than larger SS index."

[0300] As an option 1-2A of the sixth embodiment, a non-XDD CSS may not be expected to be dropped. A non-XDD USS, an XDD CSS, and an XDD USS may be dropped based on priority. For example, the UE may not expect the number of PDCCH candidates or non-overlapping CCEs of a non-XDD CSS in any slot / span / group of X slots to exceed the BD or CCE limit. Also, as a variant, an XDD CSS may not be expected to be dropped. An XDD USS, a non-XDD CSS, and a non-XDD USS may be dropped based on priority.

[0301] As an option 1-2B of the sixth embodiment, non-XDD CSSs and non-XDD USSs may not be expected to be dropped. XDD CSSs and XDD USSs 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 CSSs and non-XDD USSs in any slot / span / group of X slots to exceed the BD or CCE limit. Also, as a variant, XDD CSSs and XDD USSs may not be expected to be dropped. Non-XDD CSSs and non-XDD USSs 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 PDCCH candidates or non-overlapping CCEs of non-XDD CSS, non-XDD USS, and XDD CSS in any slot / span / group of X slots to exceed the BD or CCE limit. Also, as a variant, 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 priorities and variations 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 FIG.

[0304] For example, in the symbol arrangement shown in Figure 37, according to the Rel-15 rules, XDD CSS#1 and XDD USS#1 are monitored and non-XD USS#2 may be dropped. Also, according to option 1-1, XDD CSS#1 and non-XD USS#2 are monitored and XDD USS#1 may be dropped. Also, according to option 1-2, non-XD USS#2 and XDD CSS#1 are monitored and XDD USS#1 may be dropped.

[0305] As option 2 of the sixth embodiment, whether the PDCCH monitoring opportunity is an XDD PDCCH monitoring opportunity or a non-XDD PDCCH monitoring opportunity may be considered for overbooking. Here, an XDD PDCCH monitoring opportunity refers to a PDCCH monitoring opportunity that includes or overlaps an XDD time unit or an XDD symbol. Also, a non-XDD PDCCH monitoring opportunity refers to a PDCCH monitoring opportunity that does not include or overlap an XDD time unit or an XDD symbol.

[0306] In option 2-1 of the sixth embodiment, the following prioritization may be applied: "CSS has higher priority than USS" → "non-XDD PDCCH monitoring opportunities have higher or lower priority than XDD PDCCH monitoring opportunities" → "smaller SS index has higher priority than larger SS index."

[0307] As Option 2-1A of the sixth embodiment, PDCCH candidates for non-XDD PDCCH monitoring occasions in the CSS set may not be expected to be dropped. The XDD PDCCH monitoring occasions in the CSS set, the non-XDD PDCCH monitoring occasions in the USS set, and the PDCCH candidates for XDD PDCCH monitoring occasions 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 occasions in the CSS set in any slot / span / group of X slots to exceed the BD or CCE limit. As a variant, PDCCH candidates for XDD PDCCH monitoring occasions in the CSS set may not be expected to be dropped. The non-XDD PDCCH monitoring occasions in the CSS set, the XDD PDCCH monitoring occasions in the USS set, and the PDCCH candidates for non-XDD PDCCH monitoring occasions 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 the CSS set and PDCCH candidates for XDD PDCCH monitoring opportunities in the CSS set may not be expected to be dropped. Non-XDD PDCCH monitoring opportunities in the USS set and 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 and 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 a modification, XDD PDCCH monitoring opportunities in the CSS set and PDCCH candidates for non-XDD PDCCH monitoring opportunities in the CSS set may not be expected to be dropped. XDD PDCCH monitoring opportunities in the USS set and PDCCH candidates for non-XDD PDCCH monitoring opportunities in the USS set 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 in any slot / span / group of X slots to exceed the BD or CCE limit. Also, as a modification, 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 priorities and variations of option 2-1 of the sixth embodiment, the XDD PDCCH monitoring opportunities of the CSS set, the non-XDD PDCCH monitoring opportunities of the CSS set, the XDD PDCCH monitoring opportunities of the USS set, and the non-XDD PDCCH monitoring opportunities of the USS set may be prioritized as shown in FIG. 38.

[0311] In option 2-2 of the sixth embodiment, the following prioritization may be applied: "non-XDD PDCCH monitoring opportunities have higher or lower priority than XDD PDCCH monitoring opportunities" → "CSS has higher priority than USS" → "smaller SS index has higher priority than larger SS index."

[0312] As Option 2-2A of the sixth embodiment, PDCCH candidates for non-XDD PDCCH monitoring occasions in the CSS set may not be expected to be dropped. Non-XDD PDCCH monitoring occasions in the USS set, XDD PDCCH monitoring occasions in the CSS set, and PDCCH candidates for XDD PDCCH monitoring occasions 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 occasions in the CSS set in any slot / span / group of X slots to exceed the BD or CCE limit. Also, as a variant, PDCCH candidates for XDD PDCCH monitoring occasions in the CSS set may not be expected to be dropped. XDD PDCCH monitoring occasions in the USS set, non-XDD PDCCH monitoring occasions in the CSS set, and PDCCH candidates for non-XDD PDCCH monitoring occasions 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 PDCCH candidates or non-overlapping CCEs for non-XDD PDCCH monitoring opportunities in the CSS set, non-XDD PDCCH monitoring opportunities in the USS set, and XDD PDCCH monitoring opportunities in the CSS set in any slot / span / group of X slots to exceed the BD or CCE limit. Also, as a modification, PDCCH candidates for XDD PDCCH monitoring opportunities in the CSS set and USS set may not be expected to be dropped. PDCCH candidates for non-XDD PDCCH monitoring occasions in the CSS set and non-XDD PDCCH monitoring occasions in the USS set may be dropped based on priority.

[0314] As Option 2-2C of the sixth embodiment, PDCCH candidates for non-XDD PDCCH monitoring opportunities in the CSS set, non-XDD PDCCH monitoring opportunities in the USS set, and XDD PDCCH monitoring opportunities in the CSS set 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, non-XDD PDCCH monitoring opportunities in the USS set, and 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 a modification, 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 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.

[0315] According to the priorities and variations of option 2-2 of the sixth embodiment, the XDD PDCCH monitoring opportunities of the CSS set, the non-XDD PDCCH monitoring opportunities of the CSS set, the XDD PDCCH monitoring opportunities of the USS set, and the non-XDD PDCCH monitoring opportunities of the USS set may be prioritized as shown in FIG. 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) are 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) are monitored, and USS#1 (XDD MO) may be dropped. Also, according to option 2-2, USS#1 (XDD MO) and CSS#1 (XDD MO) are monitored, and USS#1 (XDD MO) may be dropped.

[0317] In this way, according to the sixth embodiment, the UE may control PDCCH overbooking in the XDD time unit in which PDCCH monitoring is configured, and when performing PDCCH monitoring in the PDCCH monitoring opportunities selected in the controlled PDCCH overbooking, select PDCCH monitoring opportunities according to the priorities, i.e., the UE may drop some PDCCH monitoring opportunities from the overbooked PDCCH monitoring opportunities according to the priorities.

[0318] Specifically, the PDCCH monitoring occasion may be selected based on a first prioritization between a common search space (CSS) and a user-specific search space (USS), a second prioritization between a non-XDD search space set (non-XDD SS) and an XDD search space set (XDD SS), and a third prioritization between search space indices (SS indexes).

[0319] Additionally, the PDCCH monitoring occasion may be selected further based on a fourth prioritization between non-XDD PDCCH monitoring occasions and XDD PDCCH monitoring occasions.

[0320] The above-mentioned configuration or notification may be transmitted based on, for example, at least one of a Radio Resource Control (RRC) information element, a Downlink Control Information (DCI), and a Medium Access Control (MAC) CE. Also, the present disclosure is not limited to monitoring a PDCCH, 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.).

[0321] To implement the above-mentioned XDD operation, the UE transmits UE capability information related to the XDD operation to the base station, and the base station may notify or configure the UE for 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 related to 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 related to whether the UE supports PDCCH overbooking on the cell to the base station.

[0322] In addition, UE capability information regarding whether the UE supports PDCCH overbooking in an XDD slot, an XDD span, or an XDD slot group may be specified. The UE may transmit UE capability information regarding whether it supports PDCCH overbooking in an XDD slot, an XDD span, or an XDD slot group to the base station.

[0323] Also, UE capability information regarding whether the UE supports PDCCH overbooking by considering an XDD SS set (or XDD PDCCH monitoring occasion) and a non-XDD SS set (or XDD PDCCH monitoring occasion) may be specified. The UE may transmit UE capability information regarding whether it supports PDCCH overbooking by considering an XDD SS set (or XDD PDCCH monitoring occasion) and a non-XDD SS set (or XDD PDCCH monitoring occasion) to the base station.

[0324] According to the sixth embodiment, when XDD operation is signaled, configured or applied to a cell in which PDCCH monitoring is configured, UE operation regarding PDCCH overbooking can be defined.

[0325] (Seventh Example) There is currently no discussion regarding the PDCCH monitoring beam when the XDD operation is notified, configured, or applied to the cell where PDCCH monitoring is configured. Therefore, it is necessary to specify the UE operation regarding the PDCCH monitoring beam when the XDD operation is notified, configured, or applied to the cell where PDCCH monitoring is configured. That is, with respect to the PDCCH monitoring beam, the UE may perform the following operations:

[0326] In a seventh embodiment, when a UE is configured for single-cell operation or operation with carrier aggregation (CA) in the same frequency band and monitors PDCCH candidates that include or overlap PDCCH monitoring opportunities in multiple CORESETs with the same or different qcl-Types set to the "type D" disposition for active DL BWPs of one or more cells, the UE may monitor the PDCCH only in a CORESET and any other CORESET from the multiple CORESETs with the qcl-Type set to the same "type D" disposition as the CORESET in the active DL BWP of a cell of one or more cells. If any cell is signaled or configured for XDD operation, the CORESET may be determined as the CORESET of the SS with the highest priority.

[0327] In option 1 of the seventh embodiment, the existing Rel-15 / 16 rule may be reused for prioritization. That is, the following prioritization may be applied: "CSS has higher priority than USS" → "smaller cell index has higher priority than larger cell index" → "smaller SS index has higher priority than larger SS index." The CORESET may correspond to the CSS set with the lowest index in the cell with the lowest index that contains the CSS, if any, or the USS set with the lowest index in the cell with the lowest index, if not.

[0328] In option 2 of the seventh embodiment, the determination may take into account whether there are any cells that are notified / configured for XDD operation.

[0329] As option 2-1 of the seventh embodiment, prioritization as shown in Figure 41 may be applied: "CSS has higher priority than USS" → "Cells that are not notified or configured for XDD operation have higher or lower priority than cells that are notified or configured for XDD operation" → "Smaller cell indexes have higher priority than larger cell indexes" → "Smaller SS indexes have higher priority than larger SS indexes."

[0330] As option 2-2 of the seventh embodiment, prioritization as shown in Figure 42 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" → "Smaller cell index has a higher priority than larger cell index" → "Smaller SS index has a higher priority than larger SS index".

[0331] According to the prioritization of Option 1, Options 2-1, and 2-2, five PDCCH monitoring beams, CSS#1 of cell #1, USS#2 of cell #1, USS#3 of cell #1, USS#1 of cell #2, and CSS#2 of cell #2, can be prioritized, for example, as shown in Figure 43. Note that XDD operation is notified or configured in cell #1, and 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 of cell#1, CSS#2 of cell#2, USS#2 of cell#1, USS#3 of cell#1, and USS#1 of cell#2 are prioritized in descending order of priority.

[0333] In Figure 43B, option 2-1 prioritization is applied, and CSS#2 of cell #2, CSS#1 of cell #1, USS#1 of cell #2, USS#2 of cell #1, and USS#3 of cell #1 are prioritized in descending order of priority.

[0334] In Figure 43C, option 2-2 prioritization is applied, and CSS#2 of cell#2, USS#1 of cell#2, CSS#1 of cell#1, USS#2 of cell#1, and USS#3 of 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 of CSS#1 of cell #1, USS#2 of cell #1, USS#3 of cell #1, and USS#1 of cell #2 can be prioritized, for example, as shown in Figure 44. Note that cell #1 is notified or configured for XDD operation, and cell #2 is not notified or configured for XDD operation.

[0336] In Figure 44A, the existing rules of Rel-15 / 16 are applied, and CSS#1 of cell#1, USS#2 of cell#1, USS#3 of cell#1, and USS#1 of cell#2 are prioritized in descending order of priority.

[0337] In Figure 44B, option 2-1 prioritization is applied, and CSS#1 of cell#1, USS#1 of cell#2, USS#2 of cell#1, and USS#3 of cell#1 are prioritized in descending order of priority.

[0338] In Figure 44C, option 2-2 prioritization is applied, and USS#1 of cell#2, CSS#1 of cell#1, USS#2 of cell#1, and USS#3 of cell#1 are prioritized in descending order of priority.

[0339] In Option 3 of the seventh embodiment, the determination may take into account whether there is an XDD SS set or a non-XDD SS set. Here, an XDD SS set refers to an SS set in which an XDD time unit is set, and a non-XDD SS set refers to an SS set in which a pure time unit is set.

[0340] As option 3-1 of the seventh embodiment, prioritization as shown in Figure 45 may be applied: "Non-XDD SS sets have higher or lower priority than XDD SS sets" → "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."

[0341] As option 3-2 of the seventh embodiment, the prioritization shown in Figure 46 may be applied: "CSS has higher priority than USS" → "Non-XDD SS set has higher or lower priority than XDD SS set" → "Smaller cell index has higher priority than larger cell index" → "Smaller SS index has higher priority than larger SS index."

[0342] As a variation of option 3-2 of the seventh embodiment, the following prioritization may be applied: "CSS has higher priority than USS" → "non-XDD CSS set has higher or lower priority than XDD CSS set" → "smaller cell index has higher priority than larger cell index" → "smaller SS index has higher priority than larger SS index."

[0343] As another variation of option 3-2 of the seventh embodiment, the following prioritization may be applied: "CSS has higher priority than USS" → "non-XDD USS set has higher or lower priority than XDD USS set" → "smaller cell index has higher priority than larger cell index" → "smaller SS index has higher priority than larger SS index."

[0344] As option 3-3 of the seventh embodiment, prioritization as shown in Figure 47 may be applied: "CSS has higher priority than USS" → "smaller cell index has higher priority than larger cell index" → "non-XDD SS set has higher or lower priority than XDD SS set" → "smaller SS index has higher priority than larger SS index".

[0345] As a variation of option 3-3 of the seventh embodiment, the following prioritization may be applied: "CSS has higher priority than USS" → "smaller cell index has higher priority than larger cell index" → "non-XDD CSS set has higher or lower priority than XDD CSS set" → "smaller SS index has higher priority than larger SS index."

[0346] Also, as another variation of option 3-3 of the seventh embodiment, the following prioritization may be applied: "CSS has higher priority than USS" → "smaller cell index has higher priority than larger cell index" → "non-XDD USS set has higher or lower priority than XDD USS set" → "smaller SS index has higher priority than larger SS index."

[0347] According to the prioritization of options 1, 3-1, 3-2, and 3-3 of the seventh embodiment, five PDCCH monitoring beams, CSS#1 of cell #1, USS#2 of cell #1, USS#3 of cell #1, USS#1 of cell #2, and CSS#2 of cell #2, can be prioritized, for example, as shown in Figure 48. Note that CSS#1 of cell #1, USS#2 of cell #1, and USS#1 of cell #2 are an XDD SS set, and USS#3 of cell #1 and CSS#2 of cell #2 are a non-XDD SS set.

[0348] In Figure 48A, the existing rules of Rel-15 / 16 are applied, and CSS#1 of cell#1, CSS#2 of cell#2, USS#2 of cell#1, USS#3 of cell#1, and USS#1 of cell#2 are prioritized in descending order of priority.

[0349] In Figure 48B, option 3-1 prioritization is applied, and CSS#2 of cell#2, USS#3 of cell#1, CSS#1 of cell#1, USS#2 of cell#1, and USS#1 of cell#2 are prioritized in descending order of priority.

[0350] In Figure 48C, option 3-2 prioritization is applied, and CSS#2 of cell #2, CSS#1 of cell #1, USS#3 of cell #1, USS#2 of cell #1, and USS#1 of cell #2 are prioritized in descending order of priority.

[0351] In Figure 48D, option 3-3 prioritization is applied, and CSS#1 of cell #1, CSS#2 of cell #2, USS#3 of cell #1, USS#2 of cell #1, and USS#1 of 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 seventh 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, for example, as shown in Figure 49. Note that CSS#1 of cell #1 and USS#2 of cell #1 are in the XDD SS set, and USS#3 of cell #1 and USS#1 of cell #2 are in the non-XDD SS set.

[0353] In Figure 49A, the existing rules of Rel-15 / 16 are applied, and CSS#1 of cell#1, USS#2 of cell#1, USS#3 of cell#1, and USS#1 of cell#2 are prioritized in descending order of priority.

[0354] In Figure 49B, option 3-1 prioritization is applied, and USS #3 of cell #1, USS #1 of cell #2, CSS #1 of cell #1, and USS #2 of cell #1 are prioritized in descending order of priority.

[0355] In Figure 49C, option 3-2 prioritization is applied, and CSS#1 of cell#1, USS#3 of cell#1, USS#1 of cell#2, and USS#2 of cell#1 are prioritized in descending order of priority.

[0356] In Figure 49D, option 3-3 prioritization is applied, with CSS#1 of cell#1, USS#3 of cell#1, USS#2 of cell#1, and USS#1 of cell#2 being prioritized in descending order of priority.

[0357] In option 4 of the seventh 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 refers to a PDCCH monitoring opportunity that includes or overlaps an XDD time unit or an XDD symbol. Also, a non-XDD PDCCH monitoring opportunity refers to a PDCCH monitoring opportunity that does not include or overlaps an XDD time unit or an XDD symbol.

[0358] As option 4-1 of the seventh embodiment, the prioritization shown in Figure 45 may be applied: "Non-XDD PDCCH monitoring opportunities have higher or lower priority than XDD PDCCH monitoring opportunities" → "CSS has higher priority than USS" → "Smaller cell index has higher priority than larger cell index" → "Smaller SS index has higher priority than larger SS index".

[0359] As option 4-2 of the seventh embodiment, the prioritization shown in Figure 46 may be applied: "CSS has higher priority than USS" → "Non-XDD PDCCH monitoring opportunities have higher or lower priority than XDD PDCCH monitoring opportunities" → "Smaller cell index has higher priority than larger cell index" → "Smaller SS index has higher priority than larger SS index".

[0360] As option 4-3 of the seventh embodiment, the prioritization shown in Figure 47 may be applied: "CSS has higher priority than USS" → "smaller cell index has higher priority than larger cell index" → "non-XDD PDCCH monitoring opportunity has higher or lower priority than XDD PDCCH monitoring opportunity" → "smaller SS index has higher priority than larger SS index".

[0361] According to the prioritization of options 1, 4-1, 4-2, and 4-3 of the seventh embodiment, five PDCCH monitoring beams, CSS#1 of cell #1, USS#2 of cell #1, USS#3 of cell #1, USS#1 of cell #2, and CSS#2 of cell #2, can be prioritized, for example, as shown in Figure 50. Note that CSS#1 of cell #1, USS#2 of cell #1, and USS#1 of cell #2 are XDD PDCCH monitoring opportunities, and USS#3 of cell #1 and CSS#2 of cell #2 are non-XDD PDCCH monitoring opportunities.

[0362] In Figure 50A, the existing rules of Rel-15 / 16 are applied, and CSS#1 of cell#1, CSS#2 of cell#2, USS#2 of cell#1, USS#3 of cell#1, and USS#1 of cell#2 are prioritized in descending order of priority.

[0363] In Figure 50B, option 4-1 prioritization is applied, and CSS#2 of cell#2, USS#3 of cell#1, CSS#1 of cell#1, USS#2 of cell#1, and USS#1 of cell#2 are prioritized in descending order of priority.

[0364] In Figure 50C, option 4-2 prioritization is applied, and CSS#2 of cell#2, CSS#1 of cell#1, USS#3 of cell#1, USS#2 of cell#1, and USS#1 of cell#2 are prioritized in descending order of priority.

[0365] In Figure 50D, option 4-3 prioritization is applied, and CSS#1 of cell #1, CSS#2 of cell #2, USS#3 of cell #1, USS#2 of cell #1, and USS#1 of 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 seventh 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, for example, as shown in Figure 51. Note that CSS#1 of cell #1 and USS#2 of cell #1 are XDD PDCCH monitoring opportunities, and 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 of cell#1, USS#2 of cell#1, USS#3 of cell#1, and USS#1 of cell#2 are prioritized in descending order of priority.

[0368] In Figure 51B, option 4-1 prioritization is applied, and USS #3 of cell #1, USS #1 of cell #2, CSS #1 of cell #1, and USS #2 of cell #1 are prioritized in descending order of priority.

[0369] In Figure 51C, option 4-2 prioritization is applied, and CSS#1 of cell#1, USS#3 of cell#1, USS#1 of cell#2, and USS#2 of cell#1 are prioritized in descending order of priority.

[0370] In Figure 51D, option 4-3 prioritization is applied, and CSS#1 of cell#1, USS#3 of cell#1, USS#2 of cell#1, and USS#1 of cell#2 are prioritized in descending order of priority.

[0371] In Option 5 of the seventh embodiment, whether there are cells for which XDD operation is signaled or configured and whether there are XDD SS sets or non-XDD SS sets may be taken into consideration for 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 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" → "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 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 SS set has a higher or lower priority than XDD SS set" → "Smaller cell index has a higher priority than larger cell index" → "Smaller SS index has a higher priority than larger SS index."

[0374] As a variation of option 5-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 CSS / USS set has a higher or lower priority than XDD CSS / USS set" → "smaller cell index has a higher priority than larger cell index" → "smaller SS index has a higher priority than larger SS index."

[0375] As option 5-3 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" → "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 indices have a higher priority than larger SS indices."

[0376] As a variation of option 5-3 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" → "Smaller cell index has a higher priority than larger cell index" → "Non-XDD CSS / USS set has a higher or lower priority than XDD CSS / USS set" → "Smaller SS index has a higher priority than larger SS index."

[0377] As option 5-4 of the seventh embodiment, the following prioritization may be applied: "CSS has higher priority than USS" → "Cells that are not notified or configured for XDD operation have higher or lower priority than cells that are notified or configured for XDD operation" → "Non-XDD SS set has higher or lower priority than XDD SS set" → "Smaller cell index has higher priority than larger cell index" → "Smaller SS index has higher priority than larger SS index."

[0378] As a variation of option 5-4 of the seventh embodiment, the following prioritization may be applied: "CSS has higher priority than USS" → "Cells that are not notified or configured for XDD operation have higher or lower priority than cells that are notified or configured for XDD operation" → "Non-XDD CSS / USS set has higher or lower priority than XDD CSS / USS set" → "Smaller cell index has higher priority than larger cell index" → "Smaller SS index has higher priority than larger SS index."

[0379] As option 5-5 of the seventh embodiment, the following prioritization may be applied: "CSS has higher priority than USS" → "Cells that are not notified or configured for XDD operation have higher or lower priority than cells that are notified or configured for XDD operation" → "Smaller cell indexes have higher priority than larger cell indexes" → "Non-XDD SS sets have higher or lower priority than XDD SS sets" → "Smaller SS indexes have higher priority than larger SS indexes."

[0380] As a variation of option 5-5 of the seventh embodiment, the following prioritization may be applied: "CSS has higher priority than USS" → "Cells that are not notified or configured for XDD operation have higher or lower priority than cells that are notified or configured for XDD operation" → "Smaller cell index has higher priority than larger cell index" → "Non-XDD CSS / USS set has higher or lower priority than XDD CSS / USS set" → "Smaller SS index has higher priority than larger SS index."

[0381] In Option 6 of the seventh embodiment, whether there is an XDD SS set or a non-XDD SS set and whether there is an XDD PDCCH monitoring opportunity or a non-XDD PDCCH monitoring opportunity may be taken into consideration for the determination. That is, Option 6 is a combination of Option 3 and Option 4.

[0382] As option 6-1 of the seventh embodiment, the following prioritization may be applied: "Non-XDD SS sets have higher or lower priority than XDD SS sets" → "Non-XDD PDCCH monitoring opportunities have higher or lower priority than XDD PDCCH monitoring opportunities" → "CSS has higher priority than USS" → "Smaller cell indices have higher priority than larger cell indices" → "Smaller SS indices have 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 higher or lower priority than XDD SS sets" → "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."

[0384] As option 6-3 of the seventh embodiment, the following prioritization may be applied: "Non-XDD SS set has higher or lower priority than XDD SS set" → "CSS has higher priority than USS" → "Smaller cell index has higher priority than larger cell index" → "Non-XDD PDCCH monitoring opportunity has higher or lower priority than XDD PDCCH monitoring opportunity" → "Smaller SS index has higher priority than larger SS index."

[0385] As option 6-4 of the seventh embodiment, the following prioritization may be applied: "CSS has higher priority than USS" → "Non-XDD SS set has higher or lower priority than XDD SS set" → "Non-XDD PDCCH monitoring opportunity has higher or lower priority than XDD PDCCH monitoring opportunity" → "Smaller cell index has higher priority than larger cell index" → "Smaller SS index has higher priority than larger SS index."

[0386] As a variation of option 6-4 of the seventh embodiment, the following prioritization may be applied: "CSS has higher priority than USS" → "Non-XDD CSS / USS set has higher or lower priority than XDD CSS / USS set" → "Non-XDD PDCCH monitoring opportunity has higher or lower priority than XDD PDCCH monitoring opportunity" → "Smaller cell index has higher priority than larger cell index" → "Smaller SS index has higher priority than larger SS index."

[0387] As option 6-5 of the seventh embodiment, the following prioritization may be applied: "CSS has higher priority than USS" → "Non-XDD SS set has higher or lower priority than XDD SS set" → "Smaller cell index has higher priority than larger cell index" → "Non-XDD PDCCH monitoring opportunity has higher or lower priority than XDD PDCCH monitoring opportunity" → "Smaller SS index has higher priority than larger SS index."

[0388] As a variation of option 6-5 of the seventh embodiment, the following prioritization may be applied: "CSS has higher priority than USS" → "Non-XDD CSS / USS set has higher or lower priority than XDD CSS / USS set" → "Smaller cell index has higher priority than larger cell index" → "Non-XDD PDCCH monitoring opportunity has higher or lower priority than XDD PDCCH monitoring opportunity" → "Smaller SS index has higher priority than larger SS index."

[0389] As option 6-6 of the seventh embodiment, the following prioritization may be applied: "CSS has higher priority than USS" → "smaller cell index has higher priority than larger cell index" → "non-XDD SS set has higher or lower priority than XDD SS set" → "non-XDD PDCCH monitoring opportunity has higher or lower priority than XDD PDCCH monitoring opportunity" → "smaller SS index has higher priority than larger SS index."

[0390] As a variation of option 6-6 of the seventh embodiment, the following prioritization may be applied: "CSS has higher priority than USS" → "smaller cell index has higher priority than larger cell index" → "non-XDD CSS / USS set has higher or lower priority than XDD CSS / USS set" → "non-XDD PDCCH monitoring opportunity has higher or lower priority than XDD PDCCH monitoring opportunity" → "smaller SS index has higher priority than larger SS index".

[0391] In Option 7 of the seventh embodiment, whether there is a cell for which XDD operation is signaled or configured, and whether there is an XDD PDCCH monitoring opportunity or a non-XDD PDCCH monitoring opportunity may be taken into consideration for the determination. That is, Option 7 is a combination of Option 2 and Option 4.

[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 index has a higher priority than larger cell index" → "smaller SS index has a higher priority than larger SS index".

[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 indices have a higher priority than larger SS indices."

[0394] As option 7-3 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" → "smaller cell index has a higher priority than larger cell index" → "non-XDD PDCCH monitoring opportunities have a higher or lower priority than XDD PDCCH monitoring opportunities" → "smaller SS index has a higher priority than larger SS index".

[0395] As option 7-4 of the seventh embodiment, the following prioritization may be applied: "CSS has higher priority than USS" → "Cells that are not notified or configured for XDD operation have higher or lower priority than cells that are notified or configured for XDD operation" → "Non-XDD PDCCH monitoring opportunities have higher or lower priority than XDD PDCCH monitoring opportunities" → "Smaller cell indices have higher priority than larger cell indices" → "Smaller SS indices have higher priority than larger SS indices."

[0396] As option 7-5 of the seventh embodiment, the following prioritization may be applied: "CSS has higher priority than USS" → "Cells that are not notified or configured for XDD operation have higher or lower priority than cells that are notified or configured for XDD operation" → "Smaller cell index has higher priority than larger cell index" → "Non-XDD PDCCH monitoring opportunities have higher or lower priority than XDD PDCCH monitoring opportunities" → "Smaller SS index has higher priority than larger SS index."

[0397] In Option 8 of the seventh embodiment, the determination may take into account whether there is a cell for which XDD operation is signaled or configured, whether there is an XDD SS set or a non-XDD SS set, and whether there is an XDD PDCCH monitoring opportunity or a non-XDD PDCCH monitoring opportunity. 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 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" → "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."

[0399] As option 8-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" → "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 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" → "CSSs have a higher priority than USSs" → "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."

[0401] As option 8-4 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 SS set has a higher or lower priority than XDD SS set" → "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."

[0402] As option 8-5 of the seventh embodiment, the following prioritization may be applied: "CSS has higher priority than USS" → "Cells that are not notified or configured for XDD operation have higher or lower priority than cells that are notified or configured for XDD operation" → "Smaller cell index has higher priority than larger cell index" → "Non-XDD SS set has higher or lower priority than XDD SS set" → "Non-XDD PDCCH monitoring opportunities have higher or lower priority than XDD PDCCH monitoring opportunities" → "Smaller SS index has higher priority than larger SS index."

[0403] As option 8-6 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 SS set has a higher or lower priority than XDD SS set" → "Smaller cell index has a higher priority than larger cell index" → "Non-XDD PDCCH monitoring opportunity has a higher or lower priority than XDD PDCCH monitoring opportunity" → "Smaller SS index has a higher priority than larger SS index."

[0404] As option 8-7 of the seventh embodiment, the following prioritization may be applied: "CSS has higher priority than USS" → "Cells that are not notified or configured for XDD operation have higher or lower priority than cells that are notified or configured for XDD operation" → "Non-XDD SS set has higher or lower priority than XDD SS set" → "Smaller cell index has higher priority than larger cell index" → "Non-XDD PDCCH monitoring opportunity has higher or lower priority than XDD PDCCH monitoring opportunity" → "Smaller SS index has higher priority than larger SS index."

[0405] As option 8-8 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" → "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 indices have a higher priority than larger SS indices."

[0406] As options 8-9 of the seventh embodiment, the following prioritization may be applied: "CSS has higher priority than USS" → "Cells that are not notified or configured for XDD operation have higher or lower priority than cells that are notified or configured for XDD operation" → "Smaller cell index has higher priority than larger cell index" → "Non-XDD SS set has higher or lower priority than XDD SS set" → "Non-XDD PDCCH monitoring opportunities have higher or lower priority than XDD PDCCH monitoring opportunities" → "Smaller SS index has higher priority than larger SS index."

[0407] In this way, according to the seventh embodiment, the UE may select a PDCCH monitoring beam in the XDD time unit where PDCCH monitoring is configured, 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 where PDCCH monitoring is configured, and transmit control information through the PDCCH monitoring beam.

[0408] Specifically, the UE may select a PDCCH monitoring beam according to the prioritization.

[0409] In addition, the PDCCH monitoring beam may be selected based on a first prioritization between the common search space (CSS) and the user-specific search space (USS), a second prioritization between the cell indexes, and a third prioritization between the search space indexes (SS indexes).

[0410] In addition, the PDCCH monitoring beam may be further selected based on one or more of a fourth prioritization between cells for which XDD operation is configured or notified and cells for which 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 above-mentioned configuration or notification may be transmitted based on, for example, at least one of a Radio Resource Control (RRC) information element, a Downlink Control Information (DCI), and a Medium Access Control (MAC) CE. Also, the present disclosure is not limited to monitoring a PDCCH, 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.).

[0412] To realize the above-mentioned XDD operation, a UE may transmit UE capability information related to the XDD operation to a base station, and the base station may notify or configure the UE for the XDD operation based on the received UE capability information. Specifically, UE capability information may be defined regarding whether a cell is notified or configured for XDD operation, whether an XDD SS set or a non-XDD SS set is present, and / or whether it supports determining a TCI state for PDCCH monitoring that includes or overlaps a PDCCH monitoring opportunity by considering whether an XDD PDCCH monitoring opportunity is present. The UE may transmit UE capability information to the base station regarding whether a cell is notified or configured for XDD operation, whether an XDD SS set or a non-XDD SS set is present, and / or whether it supports determining a TCI state for PDCCH monitoring that includes or overlaps a PDCCH monitoring opportunity by considering whether an XDD PDCCH monitoring opportunity is present.

[0413] According to the seventh embodiment, when XDD operation is notified, configured or applied to a cell in which PDCCH monitoring is configured, UE operation regarding a PDCCH monitoring beam can be specified.

[0414] For each of the above-described embodiments, the applicable embodiments, options and / or operations may be signaled or configured by higher layer parameters, may be signaled or reported by the UE as UE capability information, may be specified in a specification, or may be determined by the configuration of higher layer parameters and the reported UE capability information.

[0415] <Hardware configuration> The block diagrams used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wires, wirelessly, etc.) and these multiple devices. The functional block may also be realized by combining the single device or multiple devices with software.

[0416] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocation, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how these functions are implemented.

[0417] For example, a base station, a user terminal, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 52 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment of the present disclosure. The above-described base station 10 and user terminal 20 may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0418] In the following description, the term "apparatus" can be interpreted as a circuit, a device, a unit, etc. The hardware configuration of the base station 10 and the user terminal 20 may be configured to include one or more of the apparatuses shown in Fig. 52, or may be configured to exclude some of the apparatuses.

[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, causing the processor 1001 to perform calculations, control communication by the communication device 1004, and control at least one of reading and writing data in the memory 1002 and storage 1003.

[0420] The processor 1001 controls the entire computer by running, for example, an operating system. The processor 1001 may be configured by a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, the above-mentioned baseband signal processing unit 104, call processing unit 105, etc. may be realized by the processor 1001.

[0421] The processor 1001 also reads programs (program codes), 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 in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. 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 similar implementations may be made for other functional blocks. While the above-described various processes have been described as being executed by one processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may also be transmitted from a network via a telecommunications line.

[0422] The memory 1002 is a computer-readable recording medium and may be configured, for example, by at least one of a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a random access memory (RAM), etc. The memory 1002 may also be called a register, a cache, a main memory (primary storage device), etc. The memory 1002 can store executable programs (program codes), software modules, etc. for implementing a wireless communication method according to an embodiment of the present disclosure.

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

[0424] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, or a communication module. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the above-mentioned transmission / reception antenna 101, amplifier unit 102, transmission / reception unit 103, transmission path interface 106, etc. may be realized by the communication device 1004. The transmission / reception unit 103 may be implemented as a transmission unit 103a and a reception unit 103b that are physically or logically separated.

[0425] The input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (for example, a display, a speaker, an LED lamp, etc.) that performs output to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (for example, a touch panel).

[0426] Furthermore, each device, such as the processor 1001 and the memory 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between 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 application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0428] The notification of information is not limited to the aspects / embodiments described in the present disclosure and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI) and Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, and broadcast information (Master Information Block (MIB) and System Information Block (SIB))), other signals, or a combination thereof. Furthermore, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

[0429] Each aspect / embodiment described in the present disclosure may be any of the following: LTE (Long Term Evolution), LTE-Advanced (LTE-A), 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 (x is, for example, an integer or decimal number)), FRA (Future Radio Access), NR (new Radio), New radio access (NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE The present invention may be applied to at least one of systems using 802.20, UWB (Ultra-Wideband), Bluetooth (registered trademark), or other appropriate systems, and next-generation systems that are extended, modified, created, or defined based on these systems. The present invention may also be applied to a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A with 5G).

[0430] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless it is consistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0431] In the present disclosure, a specific operation described as being performed by a base station may be performed by its upper node in some cases. 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 may be performed by at least one of the base station and another network node other than the base station (for example, an MME or an S-GW, etc., but are not limited to these). Although the above example illustrates a case where there is one other network node other than the base station, a combination of multiple other network nodes (for example, an MME and an S-GW) may also be used.

[0432] Information, etc. (See the "Information, Signals" section) can be output from a higher layer (or a lower layer) to a lower layer (or a higher layer). It can also be input / output via multiple network nodes.

[0433] Input and output information may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information may be overwritten, updated, or added to. Output information may be deleted. Input information may be sent to another device.

[0434] The determination may be made based on a value represented by one bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., comparison with a predetermined value).

[0435] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, notification of predetermined information (e.g., notification that "X is true") is not limited to being done explicitly, but may be done implicitly (e.g., by not notifying the predetermined information).

[0436] Although the present disclosure has been described in detail above, it is 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 spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure.

[0437] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0438] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.

[0439] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0440] Note that terms explained 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 a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.

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

[0442] Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, relative values ​​from a predetermined value, or other corresponding information. For example, a radio resource may be indicated by an index.

[0443] The names used for the above-described parameters are not intended to be limiting in any way. Furthermore, the mathematical expressions using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.

[0444] In this disclosure, terms such as "base station (BS)," "radio 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. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be divided into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., a small indoor base station (RRH: Remote Radio Head)). The term "cell" or "sector" refers to a part or the entire coverage area of ​​a base station and / or base station subsystem that provides communication service within this coverage.

[0446] In the present disclosure, the base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control or operate based on the information.

[0447] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. 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 some other suitable terminology.

[0449] At least one of the base station and the mobile station may be referred to as a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, etc. The mobile object refers to a movable object, and may move at any speed. Naturally, this also includes cases where the mobile object is stationary. Examples of the mobile object include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and objects mounted thereon. The mobile object may also be an autonomous mobile object operating based on an operational command. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

[0450] Furthermore, a base station in the present disclosure may be read as a user terminal. For example, the aspects / embodiments of the present 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) or V2X (Vehicle-to-Everything)). In this case, the user terminal 20 may be configured to have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel.

[0451] Similarly, the user terminal in the present disclosure may be read as a base station, in which case the base station 10 may be configured to have the functions of the user terminal 20 described above.

[0452] Fig. 53 shows an example of the configuration of vehicle 1. As shown in Fig. 53, vehicle 1 includes a drive unit 2, a steering unit 3, an accelerator pedal 4, a brake pedal 5, a shift lever 6, left and right front wheels 7, left and right rear wheels 8, an axle 9, an electronic control unit 10, various sensors 21 to 29, an information service unit 12, and a communication module 13.

[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 operated by the user.

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

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

[0457] The information service unit 12 is composed of various devices, such as a car navigation system, an audio system, speakers, a television, and a radio, for providing (outputting) various types of information, such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 12 provides various types of multimedia information and multimedia services to the occupants of the vehicle 1 by using information acquired from external devices via the communication module 13, etc.

[0458] The information service unit 12 may include input devices (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) that accept input from the outside, and may also include output devices (e.g., displays, speakers, LED lamps, touch panels, etc.) that output to the outside.

[0459] The driving assistance system unit 30 is composed of various devices that provide functions for preventing accidents and reducing the driver's driving burden, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS, etc.), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps, etc.), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. The driving assistance system unit 30 also transmits and receives various information via the communication module 13 to realize driving assistance functions or autonomous driving functions.

[0460] The communication module 13 can communicate with the microprocessor 31 and components of the vehicle 1 via the communication port. For example, the communication module 13 transmits and receives data via the communication port 33 to and from 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, axles 9, microprocessor 31 and memory (ROM, RAM) 32 in the electronic control unit 10, and sensors 21 to 28, which are 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 an external device. For example, it transmits and receives various information to and from the external device via wireless communication. The communication module 13 may be located either inside or outside the electronic control unit 10. The external device may be, for example, a base station, a mobile station, or the like.

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

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

[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, axles 9, sensors 21 to 28, and the like provided in the vehicle 1.

[0465] (Summary of the embodiment) As described above, according to one aspect of the present disclosure, a terminal is provided that has a receiving unit that receives a notification or setting regarding XDD (Cross Division Duplex) operation for a radio resource, and a control unit that controls uplink transmission or downlink reception in the radio resource in accordance with the notification or setting regarding the XDD operation.

[0466] According to the above configuration, it is possible to limit radio resources (for example, cells, BWPs, etc.) that can be set for XDD operation.

[0467] In one embodiment, the receiver receives notification or configuration of XDD operation on a frequency resource basis for a time unit on a bandwidth portion, and the notification or configuration of XDD operation on a frequency resource basis may notify or configure a first frequency resource of the bandwidth portion for uplink transmission or downlink reception, and notify or configure a second frequency resource of the bandwidth portion for downlink reception or uplink transmission. This embodiment makes it possible to configure XDD operation on a frequency resource basis.

[0468] In one embodiment, the receiver receives notification or configuration of XDD operation on a per-terminal basis for a time unit on a bandwidth portion, and the notification or configuration of XDD operation on a per-terminal basis may notify or configure a first terminal for the time unit as for uplink transmission or downlink reception, and may notify or configure a second terminal for the time unit as for downlink reception or uplink transmission. This embodiment makes it possible to configure XDD operation on a per-terminal basis.

[0469] In one embodiment, the receiver may receive a notification or configuration indicating a bandwidth portion of a cell for which XDD operation is to be configured or a bandwidth portion of the cell for XDD operation. According to this embodiment, the BWP for which XDD operation is to be configured may be specified.

[0470] Furthermore, according to one aspect of the present disclosure, a base station is provided having a transmitting unit that transmits a notification or setting regarding XDD (Cross Division Duplex) operation for a radio resource, and a control unit that controls uplink transmission or downlink reception in the radio resource in accordance with the notification or setting regarding the XDD operation.

[0471] According to the above configuration, it is possible to limit radio resources (for example, cells, BWPs, etc.) that can be set for XDD operation.

[0472] Also, according to one aspect of the present disclosure, there is provided a wireless communication method executed by a terminal, comprising receiving a notification or configuration regarding XDD (Cross Division Duplex) operation for a radio resource, and controlling uplink transmission or downlink reception on the radio resource according to the notification or configuration regarding the XDD operation.

[0473] According to the above configuration, it is possible to limit radio resources (for example, cells, BWPs, etc.) that can be set for XDD operation.

[0474] Also, according to one aspect of the present disclosure, there is provided a terminal including a receiver that receives a PDCCH monitoring configuration for XDD (Cross Division Duplex) operation, and a controller that controls PDCCH monitoring according to the PDCCH monitoring configuration.

[0475] According to the above configuration, when XDD operation can be set for PDCCH monitoring resources, it is possible to appropriately realize PDCCH monitoring in XDD operation.

[0476] In one embodiment, the PDCCH monitoring configuration may include a first PDCCH monitoring configuration for non-XDD time units and a second PDCCH monitoring configuration for XDD time units. According to this embodiment, appropriate PDCCH monitoring configurations can be set for XDD operation and non-XDD operation, respectively.

[0477] In one embodiment, the first PDCCH monitoring configuration may include one or more of a search space set configuration, a CORESET (CONTROLLER REsource SET) configuration, a frequency domain resource configuration, and a frequency monitoring position configuration for the non-XDD time unit, and the second PDCCH monitoring configuration may include one or more search space set configurations, one or more CORESET configurations, one or more frequency domain resource configurations, and one or more frequency monitoring position configurations for the XDD time unit. According to this embodiment, an appropriate PDCCH monitoring configuration can be set for each of XDD operation and non-XDD operation.

[0478] In one embodiment, the PDCCH monitoring configuration may include a PDCCH search space configuration, and the controller may control the PDCCH monitoring according to whether a PDCCH monitoring opportunity indicated by the PDCCH search space configuration overlaps with an XDD time unit. According to this embodiment, PDCCH monitoring can be appropriately realized according to whether a PDCCH monitoring opportunity indicated by the PDCCH search space configuration overlaps with an XDD time unit.

[0479] Furthermore, according to one aspect of the present disclosure, there is provided a base station including: a setting unit that sets a PDCCH monitoring configuration for an XDD (Cross Division Duplex) operation; and a transmitting unit that transmits the PDCCH monitoring configuration.

[0480] According to the above configuration, when XDD operation can be set for PDCCH monitoring resources, it is possible to appropriately realize PDCCH monitoring in XDD operation.

[0481] Also, according to one aspect of the present disclosure, there is provided a wireless communication method executed by a terminal, the method including receiving a PDCCH monitoring configuration for XDD (Cross Division Duplex) operation and controlling PDCCH monitoring according to the PDCCH monitoring configuration.

[0482] According to the above configuration, when XDD operation can be set for PDCCH monitoring resources, it is possible to appropriately realize PDCCH monitoring in XDD operation.

[0483] Furthermore, according to one aspect of the present disclosure, a terminal is provided that includes a receiving unit that receives a PDCCH monitoring capability related to XDD (Cross Division Duplex) operation for radio resources, and a control unit that controls PDCCH monitoring according to the PDCCH monitoring capability.

[0484] According to the above configuration, when XDD operation can be set for PDCCH monitoring resources, it is possible to appropriately realize PDCCH monitoring in XDD operation in accordance with PDCCH monitoring capability.

[0485] In one embodiment, the PDCCH monitoring capability may be commonly set for XDD operation and non-XDD operation, which makes it possible to properly implement PDCCH monitoring in XDD operation according to the PDCCH monitoring capability.

[0486] In one embodiment, the PDCCH monitoring capability may be configured separately for XDD operation and non-XDD operation, which makes it possible to properly implement PDCCH monitoring in XDD operation according to the PDCCH monitoring capability.

[0487] In one embodiment, the controller 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 jointly, which makes it possible to appropriately implement PDCCH monitoring in XDD operation according to PDCCH monitoring capability.

[0488] Furthermore, according to one aspect of the present disclosure, a base station is provided that includes a control unit that sets a PDCCH monitoring capability related to XDD (Cross Division Duplex) operation for radio resources, and a transmission unit that transmits the PDCCH monitoring capability.

[0489] According to the above configuration, when XDD operation can be set for PDCCH monitoring resources, it is possible to appropriately realize PDCCH monitoring in XDD operation in accordance with PDCCH monitoring capability.

[0490] Also, according to one aspect of the present disclosure, there is provided a wireless communication method executed by a terminal, the method including receiving a PDCCH monitoring capability related to XDD (Cross Division Duplex) operation for a radio resource, and controlling PDCCH monitoring according to the PDCCH monitoring capability.

[0491] According to the above configuration, when XDD operation can be set for PDCCH monitoring resources, it is possible to appropriately realize PDCCH monitoring in XDD operation in accordance with PDCCH monitoring capability.

[0492] Furthermore, according to one aspect of the present disclosure, there is provided a terminal having a control unit that controls PDCCH overbooking in an XDD (Cross Division Duplex) time unit in which PDCCH monitoring is set, and a receiving unit that performs PDCCH monitoring at a PDCCH monitoring opportunity selected in the controlled PDCCH overbooking.

[0493] According to the above configuration, when XDD operation can be configured for PDCCH monitoring resources, it is possible to appropriately select PDCCH monitoring opportunities in PDCCH overbooking and perform PDCCH monitoring on the selected PDCCH monitoring opportunities.

[0494] In one embodiment, the controller may select a PDCCH monitoring opportunity according to a priority order. According to this embodiment, the PDCCH monitoring opportunity can be appropriately selected according to a priority order.

[0495] In one embodiment, the PDCCH monitoring opportunity may be selected based on a first prioritization between a common search space and a user-specific search space, a second prioritization between a non-XDD search space set and an XDD search space set, and a third prioritization between search space indexes. According to this embodiment, the PDCCH monitoring opportunity can be appropriately selected according to the prioritization.

[0496] In one embodiment, the PDCCH monitoring occasion may be selected further based on a fourth prioritization between non-XDD PDCCH monitoring occasions and XDD PDCCH monitoring occasions, so that the PDCCH monitoring occasions can be appropriately selected according to the prioritization.

[0497] Furthermore, according to one aspect of the present disclosure, there is provided a base station having a control unit that sets a PDCCH monitoring opportunity that is overbooked in an XDD (Cross Division Duplex) time unit in which PDCCH monitoring is set, and a transmission unit that transmits control information during the PDCCH monitoring opportunity.

[0498] According to the above configuration, when XDD operation can be configured for PDCCH monitoring resources, it is possible to appropriately select PDCCH monitoring opportunities in PDCCH overbooking and perform PDCCH monitoring on the selected PDCCH monitoring opportunities.

[0499] Furthermore, according to one aspect of the present disclosure, there is provided a wireless communication method executed by a terminal, the method comprising: controlling PDCCH overbooking in an XDD (Cross Division Duplex) time unit in which PDCCH monitoring is set; and performing PDCCH monitoring in a PDCCH monitoring opportunity selected in the controlled PDCCH overbooking.

[0500] According to the above configuration, when XDD operation can be configured for PDCCH monitoring resources, it is possible to appropriately select PDCCH monitoring opportunities in PDCCH overbooking and perform PDCCH monitoring on the selected PDCCH monitoring opportunities.

[0501] Furthermore, according to one aspect of the present disclosure, there is provided a terminal 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, when the XDD operation can be set for the PDCCH monitoring resource, the PDCCH monitoring beam can be appropriately selected, and the PDCCH monitoring can be performed by the selected PDCCH monitoring beam.

[0503] In one embodiment, the control unit may select a PDCCH monitoring beam according to a priority order, which can appropriately select a PDCCH monitoring beam.

[0504] In one embodiment, the PDCCH monitoring beam may be selected based on a first priority between a common search space and a user-specific search space, a second priority between cell indexes, and a third priority between search space indexes. 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 a fourth prioritization between cells configured or notified of XDD operation and cells configured or notified of XDD operation, 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 has a control unit that controls a PDCCH monitoring beam in an XDD (Cross Division Duplex) time unit in which PDCCH monitoring is set, and a transmission unit that transmits control information by the PDCCH monitoring beam.

[0507] According to the above configuration, when the XDD operation can be set for the PDCCH monitoring resource, the PDCCH monitoring beam can be appropriately selected, and the PDCCH monitoring can be performed by the selected PDCCH monitoring beam.

[0508] Furthermore, according to one aspect of the present disclosure, there is provided a wireless communication method executed 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, when the XDD operation can be set for the PDCCH monitoring resource, the PDCCH monitoring beam can be appropriately selected, and the PDCCH monitoring can be performed by the selected PDCCH monitoring beam.

[0510] (Supplementary explanation of the embodiment) As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and the like. Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.

[0511] The terms "connected," "coupled," or any variation thereof, refer to 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" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using one or more wires, cables, and / or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

[0512] The reference signal may be abbreviated as RS (Reference Signal) or may be called a pilot depending on the applicable standard.

[0513] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0514] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.

[0515] The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc.

[0516] When used in this disclosure, the terms "include," "including," and variations thereof are intended to be inclusive, similar to the term "comprising." Furthermore, when used in this disclosure, the term "or" is not intended to be an exclusive or.

[0517] A radio frame may be composed of one or more frames in the time domain. Each of the one or more frames in the time domain may be called a subframe. A subframe may further be composed 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 a communication parameter applied to at least one of transmission and reception of a signal or channel, and may indicate, for example, at least one of subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering operations performed by a transceiver in the frequency domain, and specific windowing operations performed by a transceiver in the time domain.

[0519] A slot may be composed of one or more symbols (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol or a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol) in the time domain. A slot may be a time unit based on numerology.

[0520] A slot may include multiple minislots. Each minislot may consist of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot 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] The radio frame, subframe, slot, minislot, and symbol all represent time units for transmitting signals, and may be referred to by other names corresponding to the radio frame, subframe, slot, minislot, and symbol.

[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 minislot may be called a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc. instead of a subframe.

[0523] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) to each user terminal in TTI units. However, the definition of TTI is not limited to this.

[0524] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

[0525] When one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

[0526] A TTI having a time length of 1 ms may be called a regular TTI (TTI in LTE Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.

[0527] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.

[0528] A resource block (RB) is a resource allocation unit in the time domain and frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of numerology, for example, 12. The number of subcarriers included in an RB may also be determined based on numerology.

[0529] The time domain of an RB may include one or more symbols and may have a length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc. may each be composed of one or more resource blocks.

[0530] Note that one or more RBs may also be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, or the like.

[0531] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

[0532] A Bandwidth Part (BWP) (which may also be referred to as a fractional bandwidth) may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a common reference point of the carrier. PRBs may be defined in a given BWP and numbered within that BWP.

[0533] The BWP may include a BWP for UL (UL BWP) and a BWP for DL ​​(DL BWP). One or more BWPs may be configured for a UE within one carrier.

[0534] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell," "carrier," etc. in this disclosure may be read as "BWP."

[0535] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc. may be changed in various ways.

[0536] The "maximum transmit power" in this disclosure may mean the maximum value of transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.

[0537] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0538] In the present 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 "coupled" may also be interpreted in the same way as "different." [Explanation of symbols]

[0539] 10. Wireless communication systems 100 base stations (gNB) 200 User Equipment (UE)

Claims

1. a control unit that selects a PDCCH monitoring beam in a cross division duplex (XDD) time unit in which PDCCH monitoring is set; a receiving unit that performs PDCCH monitoring on the selected PDCCH monitoring beam; A terminal having:

2. The terminal according to claim 1 , wherein the control unit selects a PDCCH monitoring beam according to a priority order.

3. 3. The terminal of claim 2, wherein the PDCCH monitoring beam is selected based on a first prioritization between a common search space and a user-specific search space, a second prioritization between cell indexes, and a third prioritization between search space indexes.

4. 4. The terminal of claim 3, wherein the PDCCH monitoring beam is selected further based on one or more of: a fourth prioritization between cells configured or notified of XDD operation and cells configured or not notified of XDD operation; 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.

5. a control unit that controls a PDCCH monitoring beam in a cross division duplex (XDD) time unit in which PDCCH monitoring is set; A transmitter that transmits control information by the PDCCH monitoring beam; A base station having

6. Selecting a PDCCH monitoring beam in a Cross Division Duplex (XDD) time unit in which PDCCH monitoring is configured; and performing PDCCH monitoring on the selected PDCCH monitoring beam; A wireless communication method performed by a terminal, comprising:

Images