Terminal, base station, and wireless communication method

By adopting cross-segment duplex technology and PDCCH monitoring optimization in wireless communication systems, the problem of insufficient uplink resources is solved, resource utilization efficiency is improved, delay is reduced and system performance is improved.

CN119096649APending Publication Date: 2024-12-06NTT DOCOMO INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202280095427.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2022-04-27
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

In future wireless communication systems, especially in environments with high density and high traffic volume, the resources of the uplink are insufficient, resulting in increased latency and decreased coverage performance. The existing NR specifications have not fully studied how to improve the uplink Resource utilization efficiency.

Method used

By using cross-segment duplex (XDD) technology in terminals and base stations, optimizing PDCCH monitoring and resource configuration, ensuring resource utilization efficiency of the uplink, including the design of reception and control units to achieve PDCCH monitoring and over-determined control, select Suitable beam and time units to improve resource utilization.

Benefits of technology

It effectively improves the resource utilization efficiency of the uplink, reduces latency, improves system performance, and ensures the stability of the coverage range.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119096649A_ABST
    Figure CN119096649A_ABST
Patent Text Reader

Abstract

According to one embodiment of the present disclosure, provided is a terminal provided with: a receiving unit that receives PDCCH monitoring settings for an XDD (Cross Division Duplex) operation; and a control unit that controls PDCCH monitoring in accordance with the PDCCH monitoring setting.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

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

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

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

[0004] Prior art literature

[0005] Patent Literature

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

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

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

[0009] However, in the NR specifications to date, methods for increasing uplink resources have not been fully studied. If this method cannot be properly controlled, there is a concern that system performance will be reduced, such as increased latency and reduced coverage performance.

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

[0011] According to one embodiment of the present invention, a terminal is provided, comprising: a receiving unit for receiving notifications or settings related to XDD (Cross Division Duplex) operations on wireless resources; and a control unit for controlling uplink transmission or downlink reception in the wireless resources according to the notifications or settings related to the XDD operations.

[0012] According to another aspect of the present disclosure, a terminal is provided, comprising: a receiving unit that receives a PDCCH monitoring configuration for an XDD (Cross Division Duplex) operation; and a control unit that controls PDCCH monitoring according to the PDCCH monitoring configuration.

[0013] According to another aspect of the present disclosure, a terminal is provided, comprising: a receiving unit that receives a PDCCH monitoring capability related to an XDD (Cross Division Duplex) operation for a wireless resource; and a control unit that controls PDCCH monitoring according to the PDCCH monitoring capability.

[0014] According to other embodiments of the present disclosure, a terminal is provided, comprising: 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.

[0015] According to another embodiment of the present disclosure, a terminal is provided, comprising: 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 DESCRIPTION OF THE DRAWINGS

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

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

[0018] FIG. 3 is a diagram showing an example of configuration of radio resources based on XDD (Cross Division Duplex) according to an embodiment of the present disclosure.

[0019] Figure 4 FIG. 4 is a diagram showing an XDD operation according to an embodiment of the present disclosure.

[0020] FIG. 5 is a diagram showing a pure time unit and an XDD time unit according to an embodiment of the present disclosure.

[0021] Figure 6 2 is a diagram showing PDCCH monitoring opportunities according to an embodiment of the present disclosure.

[0022] Figure 7 2 is a diagram showing PDCCH overbooking according to an embodiment of the present disclosure.

[0023] Figure 8 This is a diagram showing a PDCCH monitoring beam according to an embodiment of the present disclosure.

[0024] Fig. 9 This is a diagram showing a setting example of XDD according to an embodiment of the present disclosure.

[0025] Fig.10 This is a diagram showing an example of configuration of radio resources of XDD according to an embodiment of the present disclosure.

[0026] Fig.11 This is a diagram showing a setting example of XDD according to an embodiment of the present disclosure.

[0027] Fig.12 This is a diagram showing an example of configuration of radio resources of XDD according to an embodiment of the present disclosure.

[0028] FIG. 13 is a diagram showing a setting example of XDD and an allocation example of wireless resources according to an embodiment of the present disclosure.

[0029] FIG. 14 is a diagram showing a setting example of XDD and an allocation example of wireless resources according to an embodiment of the present disclosure.

[0030] Fig.15 This is a diagram showing a setting example of XDD according to an embodiment of the present disclosure.

[0031] Fig.16 This is a diagram showing an example of configuration of radio resources of XDD according to an embodiment of the present disclosure.

[0032] FIG. 17 is a diagram showing a setting example of XDD and an allocation example of wireless resources according to an embodiment of the present disclosure.

[0033] FIG. 18 is a diagram showing a setting example of XDD and an allocation example of wireless resources according to an embodiment of the present disclosure.

[0034] Fig.19 This is a diagram showing a setting example of XDD according to an embodiment of the present disclosure.

[0035] Fig. 20 This is a diagram showing an example of configuration of radio resources of XDD according to an embodiment of the present disclosure.

[0036] FIG. 21 is a diagram showing a setting example of XDD and a configuration example of wireless resources according to an embodiment of the present disclosure.

[0037] FIG. 22 is a diagram showing a setting example of XDD and a configuration example of wireless resources according to an embodiment of the present disclosure.

[0038] Fig.23 This is a diagram showing a setting example of XDD according to an embodiment of the present disclosure.

[0039] Fig.24 This is a diagram showing an example of configuration of radio resources of XDD according to an embodiment of the present disclosure.

[0040] Fig.25 This is a diagram showing an example of configuration of radio resources of XDD according to an embodiment of the present disclosure.

[0041] Fig.26 This is a diagram showing an example of configuration of radio resources of XDD according to an embodiment of the present disclosure.

[0042] Fig. 27 This is a diagram showing an example of configuration of radio resources of XDD according to an embodiment of the present disclosure.

[0043] Fig.28 This is a diagram showing an example of configuration of radio resources of XDD according to an embodiment of the present disclosure.

[0044] Fig.29 This is a diagram showing an example of configuration of radio resources of XDD according to an embodiment of the present disclosure.

[0045] Fig.30 This is a diagram showing an example of configuration of radio resources of XDD according to an embodiment of the present disclosure.

[0046] FIG31 is a diagram showing an example of configuration of radio resources of XDD according to an embodiment of the present disclosure.

[0047] Fig.32 It is a diagram illustrating monitoring capabilities of each version according to an embodiment of the present disclosure.

[0048] FIG. 33 is a diagram showing an example of configuration of radio resources of XDD according to an embodiment of the present disclosure.

[0049] FIG34 is a diagram showing an example of configuration of radio resources of XDD according to an embodiment of the present disclosure.

[0050] Fig.35 This is a diagram showing a priority ranking according to an embodiment of the present disclosure.

[0051] Fig.36 This is a diagram showing a priority ranking according to an embodiment of the present disclosure.

[0052] Fig.37 This is a diagram showing an example of configuration of radio resources of XDD according to an embodiment of the present disclosure.

[0053] Fig.38 This is a diagram showing a priority ranking according to an embodiment of the present disclosure.

[0054] Fig.39 This is a diagram showing a priority ranking according to an embodiment of the present disclosure.

[0055] Fig.40 This is a diagram showing an example of configuration of radio resources of XDD according to an embodiment of the present disclosure.

[0056] Fig.41 This is a diagram showing a priority ranking according to an embodiment of the present disclosure.

[0057] Fig.42 This is a diagram showing a priority ranking according to an embodiment of the present disclosure.

[0058] FIG. 43 is a diagram showing a priority ranking according to an embodiment of the present disclosure.

[0059] FIG. 44 is a diagram showing a priority ranking according to an embodiment of the present disclosure.

[0060] Fig.45 This is a diagram showing a priority ranking according to an embodiment of the present disclosure.

[0061] Fig.46 This is a diagram showing a priority ranking according to an embodiment of the present disclosure.

[0062] Fig.47 This is a diagram showing a priority ranking according to an embodiment of the present disclosure.

[0063] FIG. 48 is a diagram showing a priority ranking according to an embodiment of the present disclosure.

[0064] FIG. 49 is a diagram showing a priority ranking according to an embodiment of the present disclosure.

[0065] FIG. 50 is a diagram showing a priority ranking according to an embodiment of the present disclosure.

[0066] FIG. 51 is a diagram showing a priority ranking according to an embodiment of the present disclosure.

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

[0068] Fig.53 It is a block diagram showing the hardware structure of a vehicle according to one embodiment of the present disclosure. DETAILED DESCRIPTION

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

[0070] (Wireless Communication System)

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

[0072] In addition, the wireless communication system can also support dual connectivity (Multi-RAT Dual Connectivity (MR-DC)) between multiple radio access technologies (Radio Access Technology (RAT)). MR-DC can also include dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA))) and NR (E-UTRA-NR Dual Connectivity (E-UTRA-NR Dual Connectivity (EN-DC))), dual connectivity between NR and LTE (NR-E-UTRA Dual Connectivity (NR-E-UTRA Dual Connectivity (NE-DC))), etc.

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

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

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

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

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

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

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

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

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

[0082] In a wireless communication system, a wireless access method based on orthogonal frequency division multiplexing (OFDM) may also be used. For example, in at least one of the downlink (DL) and the uplink (UL), cyclic prefix OFDM (CP-OFDM), discrete Fourier transform spread OFDM (DFT-s-OFDM), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), etc. may also be used.

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

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

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

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

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

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

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

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

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

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

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

[0094] The synchronization signal may be, for example, at least one of a primary synchronization signal (PSS) and a secondary synchronization signal (SSS). A signal block including SS (PSS, SSS) and PBCH (and DMRS for PBCH) may also be referred to as SS / PBCH block, SS block (SSB), etc. In addition, SS, SSB, etc. may also be referred to as reference signals.

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

[0096] (Device Structure)

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

[0098] (gNB100)

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

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

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

[0102] (UE200)

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

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

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

[0106] (XDD operation)

[0107] Considering the time ratio of transmission and reception based on Time Division Duplex (TDD) up to Rel.16 (for example, DL:UL=4:1), consider a situation where the number of transmission opportunities for UL signals / channels becomes smaller relative to the number of reception opportunities for DL ​​signals / channels. In such a situation, the UE cannot frequently transmit UL signals / channels, and there is a concern about transmission delays of important UL signals / channels. In addition, since the number of UL transmission opportunities becomes smaller than the number of DL reception opportunities, there is also a concern about signal / channel congestion in the UL transmission opportunities. Furthermore, in TDD, since the time resources that can transmit UL signals / channels are limited, for example, the application of UL coverage enhancement technology based on repeated transmission (repetition) is also limited.

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

[0109] This division duplex method may also be referred to as XDD (Cross Division Duplex) or subband non-overlapping full duplex. XDD or subband non-overlapping full duplex may also refer to a duplex method that frequency-division multiplexes DL and UL (capable of using DL and UL simultaneously) within one component carrier (CC) in the TDD band.

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

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

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

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

[0114] Considering the complexity of processing self-interference, it may be considered that only the base station uses DL resources and UL resources at the same time. That is, on the radio resources where DL and UL overlap in time, a certain UE may use DL resources and other UEs may use UL resources.

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

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

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

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

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

[0120] In addition, in the existing NR, the time resources in the TDD carrier used by the UE are set to at least one of DL, UL, and flexible (FL) in the TDD setting.

[0121] The XDD symbol may be a symbol that is notified or set as UL (or DL) on a certain frequency resource, or is notified or set as UL transmission (or DL ​​reception), and on the other hand, is notified or set as DL (or UL) on other frequency resources, or is notified or set as DL reception (or UL transmission). Alternatively, the XDD symbol may be a symbol that is notified or set as UL (or DL) on a part of the frequency resources, or is notified or set as UL transmission (or DL ​​reception). Alternatively, the XDD symbol may be a symbol that is notified or set as DL (or UL) on a part of the frequency resources, or is notified or set as DL reception (or UL transmission).

[0122] Here, the time unit may also be a symbol level, a slot / subslot level, or a group of symbols / slots / subslots. That is, an XDD time unit may also 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.

[0123] A pure time unit may also be a non-XDD symbol (i.e., a symbol that is not an XDD symbol), a slot / subslot that does not contain or overlap an XDD symbol, or a group of symbols / slots / subslots that do not contain or overlap an XDD symbol, which may also be referred to as a non-XDD time unit. Figure 5A As shown in FIG. 1 , a pure time unit may also refer to a time unit consisting of only DL on a frequency resource. Figure 5B As shown, it can also be referred to as a time unit consisting of only UL on the frequency resource.

[0124] In addition, regarding the XDD time unit, DL resources and UL resources can also have various configuration modes in the frequency domain. For example, the XDD time unit of frequency domain mode #1 can also have Figure 5C In addition, the XDD time unit of frequency domain mode #2 can also have Figure 5DIn addition, the XDD time unit of frequency domain mode #3 can also have Figure 5E These configuration patterns are just examples, and other configuration patterns may also be used. The frequency domain pattern of the XDD time unit may also mean a resource repetition pattern in the frequency domain for the XDD time unit.

[0125] (PDCCH monitoring)

[0126] In Rel-15 / 16, the UE performs blind decoding (BD) on a set of PDCCH (Physical Downlink Control Channel) candidates for a set of configured search spaces (SS). Specifically, the UE determines the PDCCH monitoring opportunities on the activated DL BWP based on the PDCCH monitoring period, PDCCH monitoring offset, and PDCCH monitoring mode in the time slot. For example, for PDCCH monitoring period k=5, PDCCH monitoring offset o=2, and PDCCH monitoring mode (duration) d=3, the UE Figure 6 PDCCH candidates are monitored within the time slots of the search space (SS) set as shown.

[0127] Specifically, the UE monitors each time slot of the object. Figure 6 In the PDCCH monitoring opportunities shown in the figure, the PDCCH candidates are monitored. In the example shown in the figure, when the duration of CORESET is 2 and monitoringSymbolsWithinSlot=10001000100000, the UE monitors the PDCCH candidates in the PDCCH monitoring opportunity #0 corresponding to the "0th" and "1st" codewords, and the PDCCH monitoring opportunity #1 corresponding to the "4th" and "5th" codewords.

[0128] (PDCCH monitoring capability)

[0129] In addition, the PDCCH monitoring capability per time slot in Rel-15, the PDCCH monitoring capability per span in Rel-16, and the PDCCH monitoring capability for multiple time slots in Rel-17 can be notified or set. For the PDCCH monitoring capability per time slot of Rel-15, overbooking of the number of PDCCH candidates and / or the number of control channel elements (CCE) exceeding the UE capability is allowed only on the primary cell (Pcell) or the primary and secondary cells (PScell). For the PDCCH monitoring capability per span of Rel-16, overbooking is allowed only on the first span of the time slot on the Pcell / PScell. For the PDCCH monitoring capability of multiple time slots of Rel-17, overbooking is allowed only on the Pcell / PScell.

[0130] In addition, for the common search space (CSS), overbooking is not allowed. That is, the network guarantees that the number of non-overlapping CCEs and PDCCH candidates of the CSS in a slot, span, or group of X slots is below the blind decoding (BD) or control channel element (CCE) limit.

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

[0132] For example, Figure 7 As shown, when USS#1 with 28 CCEs, USS#2 with 24 CCEs, and CSS#1 with 24 CCEs are in the time slot, and in the case of a limit of 56, only CSS#1 and USS#1 with higher priority not exceeding the limit of 56 are monitored.

[0133] (PDCCH monitoring beam)

[0134] When the TCI (Transmission Configuration Indication) state or beam is set to CORESET for an overlapping PDCCH monitoring opportunity, the UE monitors the PDCCH candidates with the same TCI state that are included or overlapped in the PDCCH monitoring opportunity. In addition, the TCI state is determined by the SS with the highest priority. Here, the CSS has a higher priority than the USS, the SS with a smaller cell index has a higher priority than the SS with a larger cell index, and the SS with a smaller SS index has a higher priority than the SS with a larger SS index.

[0135] According to the above-mentioned priority order, for example, the SS of CSS#1 of cell#1, the SS of CSS#2 of cell#2, the SS of USS#2 of cell#1, and the SS of USS#1 of cell#2 are Figure 8 As shown, the SS of CSS#1 of cell #1 and the SS of USS#2 of cell #1 are prioritized and monitor the PDCCH candidates.

[0136] (First embodiment)

[0137] No specific restrictions on XDD operation have been discussed so far. For example, XDD operation may not be supported for a specific cell.

[0138] In Embodiment 1, the cells or time resources capable of setting XDD operation are limited. The UE may not assume that the Pcell / Pscell is notified or configured for XDD operation. In addition, the UE may not assume that any cell in the primary / secondary cell group is notified, configured or applied for XDD operation. Alternatively, the UE may not assume that any BWP or cell configured with a search space (SS) set and / or CORESET setting is notified or configured for XDD operation. Alternatively, the UE may not assume that even if XDD operation is notified or configured, any BWP or cell configured with a specific type of SS set and / or a specific type of CORESET setting is notified or configured as UL (or DL) on a part of the frequency resources, or is notified or configured for UL transmission (or DL ​​reception).

[0139] Here, the so-called specific type of SS set may be any of the following.

[0140] i) Type 0-PDCCH CSS set by pdcch-ConfigSIB1 in MIB (Master Information Block), searchSpaceSIB1 in PDCCH-ConfigCommon, and searchSpaceZero in PDCCH-ConfigCommon

[0141] ii) Type 0A-PDCCH CSS set by searchSpaceOtherSystemInformation in PDCCH-ConfigCommon

[0142] iii) Type 1-PDCCH CSS set by ra-SearchSpace in PDCCH-ConfigCommon

[0143] iv) Type 2-PDCCH CSS set by pagingSearchSpace in PDCCH-ConfigCommon

[0144] 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

[0145] In addition, the UE may not assume that any BWP or cell for which PUCCH resources / transmissions are configured is notified, configured, or applies XDD operation. Alternatively, the UE may not assume that any BWP or cell in FR2-2 is notified or configured for UL (or DL), or is notified or configured for XDD operation. Alternatively, the UE may not assume that any BWP or cell for which an SCS (Subcarrier Spacing) value greater than a specific value is configured (e.g., an SCS value of 60, 120, 480 or 960 kHz) is notified or configured for XDD operation.

[0146] In view of such assumptions, in the first embodiment, when one or more conditions described later are satisfied, the XDD operation may be notified or set for the BWP or the cell.

[0147] Specifically, as described below, an XDD operation may be notified or set for a BWP. For example, a certain time unit on a BWP may be notified or set as UL (or DL) or notified or set as UL transmission (or DL ​​reception) on a part of the frequency resources, and on the other hand, it may be notified or set as DL (or UL) or notified or set as DL reception (or UL transmission) on other frequency resources. The time unit here may also be a symbol, a time slot, a sub-time slot, or a group of a symbol, a time slot, or a sub-time slot. That is, for a certain time unit, an XDD operation may be notified or set for a BWP in units of frequency resources.

[0148] As another example, a certain time unit on the BWP may be notified or set as UL (or DL) or notified or set as UL transmission (or DL ​​reception) for a certain UE, and on the other hand, it may be notified or set as DL (or UL) or notified or set as DL reception (or UL transmission) for other UEs. That is, for a certain time unit, the XDD operation may be notified or set for the BWP in units of UEs.

[0149] As another example, a certain time unit on the BWP may be notified or set as UL (or DL), or notified or set as UL transmission (or DL ​​reception) on a part of the frequency resources, and the part of the frequency resources may be notified or set as unavailable for UL (or DL) by a new time slot format setting / notification or a new rate matching mode setting / notification. That is, the XDD operation may be notified or set for the BWP for a certain time unit by using a new time slot format setting / notification or a new rate matching mode setting / notification.

[0150] In addition, as described below, the XDD operation may be notified or set for a cell. For example, the XDD operation may be notified or set for any one of the cells or the activated BWP. As another example, multiple BWPs for XDD operation may be notified or set for the cell.

[0151] In this way, according to the first embodiment, the UE can also receive the notification or setting related to the XDD operation of the radio resource, and control the uplink transmission or downlink reception in the radio resource according to the notification or setting related to the XDD operation. Correspondingly, the base station can also send the notification or setting related to the XDD operation of the radio resource, and control the uplink transmission or downlink reception in the radio resource according to the notification or setting related to the XDD operation.

[0152] Specifically, the UE may also receive notifications or settings related to XDD operations for frequency resource units of time units on the BWP. Correspondingly, the base station may also send notifications or settings related to XDD operations for frequency resource units of time units on the BWP. Here, regarding the notifications or settings related to the XDD operations for the frequency resource units, a part of the frequency resources of the BWP may be notified or set for uplink transmission or downlink reception, and the other frequency resources of the BWP may be notified or set for downlink reception or uplink transmission. In addition, the part of the frequency resources may also be notified or set as available or unavailable for uplink transmission or downlink reception through time slot format setting or notification, or through rate matching mode setting or notification.

[0153] In addition, the UE may also receive a notification or setting related to the XDD operation of the terminal unit for the time unit on the BWP. Correspondingly, the base station may also send a notification or setting related to the XDD operation of the terminal unit for the time unit on the BWP. Here, the notification or setting related to the XDD operation of the terminal unit may also notify or set the time unit for uplink transmission or downlink reception for a certain terminal, and notify or set the time unit for downlink reception or uplink transmission for other terminals.

[0154] In addition, the UE may receive a notification or setting indicating the BWP of a cell configured for XDD operation or the BWP for XDD operation of the cell. Correspondingly, the base station may send a notification or setting indicating the BWP of a cell configured for XDD operation or the BWP for XDD operation of the cell.

[0155] The above-mentioned setting or notification may be transmitted as, for example, at least one of an RRC (Radio Resource Control) information element, a DCI (Downlink Control Information), and a MACCE (Medium Access Control Control Element).

[0156] In addition, in order to implement the above-mentioned XDD operation, the UE may also send UE capability information related to the XDD operation to the base station, and the base station may also notify or set the XDD operation to the UE based on the received UE capability information. Specifically, it may also be specified whether the UE capability information related to the XDD operation applied on the Pcell / Pscell is supported, and the UE sends the UE capability information related to whether the XDD operation applied on the Pcell / Pscell is supported to the base station.

[0157] In addition, it may also be specified whether UE capability information related to whether the XDD operation applied on the cells in the primary / secondary cell group is supported, and the UE sends the UE capability information related to whether the XDD operation applied on the cells in the primary / secondary cell group is supported to the base station.

[0158] In addition, it may also be specified whether UE capability information related to the XDD operation applied on the cell / BWP of the set SS set (specific SS set type) is supported, and the UE sends the UE capability information related to whether it supports the XDD operation applied on the cell / BWP of the set SS set (specific SS set type) to the base station.

[0159] In addition, it may also be specified whether UE capability information related to the XDD operation applied on the configured PUCCH resources / transmitted cell / BWP is supported, and the UE sends the UE capability information related to whether it supports the XDD operation applied on the configured PUCCH resources / transmitted cell / BWP to the base station.

[0160] Alternatively, the UE may specify UE capability information related to whether the UE supports the XDD operation applied on the cell / BWP in FR2-2, and the UE may send the UE capability information related to whether the UE supports the XDD operation applied on the cell / BWP in FR2-2 to the base station.

[0161] In addition, it may be specified whether UE capability information related to XDD operations applied on cells / BWPs with SCSs set larger than a specific value is supported, and the UE sends to the base station the UE capability information related to whether it supports XDD operations applied on cells / BWPs with SCSs set larger than a specific value.

[0162] According to the first embodiment, cells or time resources in which XDD operation can be set can be limited.

[0163] (Second embodiment)

[0164] Discussions on search space (SS) set and / or CORESET settings in the case where XDD operation is notified, set or applied for a BWP or cell for which PDCCH monitoring is set have not been conducted so far. Therefore, it is necessary to specify UE operations for SS set and / or CORESET settings in the case where XDD operation is notified, set or applied for a BWP or cell for which PDCCH monitoring is set. In the second embodiment, in the case where XDD operation can be set for PDCCH monitoring resources, the UE can also perform PDCCH monitoring as described later.

[0165] In Option 1 of the second embodiment, the existing settings may be used for the SS set setting or CORESET setting in the case where the XDD operation is set to be notified, set or applied to the BWP or cell for which PDCCH monitoring is set. That is, the SS set setting or CORESET setting may not be enhanced in the case where the XDD operation is set to be notified, set or applied to the BWP or cell for which PDCCH monitoring is set.

[0166] On the other hand, in this way, even when the SS set setting or the CORESET setting is not extended, when the XDD operation is notified, set or applied for the BWP or cell for which PDCCH monitoring is set, the UE-based PDCCH monitoring operation needs to be extended, as described later in association with the third embodiment, and this point needs to be noted.

[0167] In option 2 of the second embodiment, separate SS set settings may also be set for pure time units and XDD time units. That is, a search space set may also be set for each of normal TDD operations and XDD operations. Here, the time unit may also be a symbol level, a slot / subslot level, or a group of symbols / slots / subslots. In addition, the XDD time unit may also 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 also be a non-XDD symbol, that is, a symbol that is not an XDD symbol, or a slot / subslot or a group of symbols / slots / subslots that do not contain or overlap an XDD symbol.

[0168] For example, searchSpacesToAddModList can also be used for SS set setting of pure time unit (also called non-XDD SS set), and new information elements (IEs) such as searchSpacesToAddModListForXDD can also be used for SS set setting of XDD time unit (also called XDD SS set).

[0169] When searchSpacesToAddModList is used for SS set setting of pure time units, the maximum number N of SS sets set for pure time units in PDCCH-Config can also be equal to a specific number such as 10 (for example, N=10), or can be less or more than a specific number such as 10 (for example, N<10 or N>10).

[0170] In addition, when new IEs such as searchSpacesToAddModListForXDD are used for SS set settings for XDD time units, the maximum number M of SS sets set for XDD time units in PDCCH-Config may also be equal to a specific number such as 10 (for example, M=10), or may be less or more than a specific number such as 10 (for example, M<10 or M>10). In addition, M is not limited and may also be equal to (10-N).

[0171] For example, Fig. 9 As shown, in PDCCH-Config, two IEs, searchSpacesToAddModList and searchSpacesToAddModListForXDD, may be set. Similarly, two IEs, searchSpacesToReleaseList and searchSpacesToReleaseListForXDD, may also be set.

[0172] For each SS set, similar to Rel-15 / 16, the UE can also determine the PDCCH monitoring opportunity.

[0173] Moreover, for the PDCCH monitoring opportunity of the non-XDD SS set (non-XDD SS set), as an example, the UE may not assume that the PDCCH monitoring opportunity of any one of the non-XDD SS sets (non-XDD SS set) is included in or overlapped in the XDD time unit or XDD codeword. Or, as another example, in the case where the PDCCH monitoring opportunity of the XDD SS set (XDD SS set) is included in or overlapped in the XDD time unit or XDD codeword, the UE may not monitor the PDCCH candidates in the PDCCH monitoring opportunities included in or overlapped in the XDD time unit or XDD codeword. On the other hand, in the case where the PDCCH monitoring opportunity of the XDD SS set (XDD SS set) is not included in or overlapped in the XDD time unit or XDD codeword, the UE may monitor the PDCCH candidates in the PDCCH monitoring opportunity by the same method as Rel-15 / 16.

[0174] On the other hand, for the PDCCH monitoring opportunities of the XDD SS set (XDD SS set), as an example, the UE may not assume that any PDCCH monitoring opportunity of the XDD SS set (XDD SS set) is included in or overlapped in a pure time unit. Or, as another example, in the case where the PDCCH monitoring opportunity is included in or overlapped in a pure time unit or a non-XDD codeword, the UE may not monitor the PDCCH candidates in the PDCCH monitoring opportunities included in or overlapped in the pure time unit or the non-XDD codeword. On the other hand, in the case where the PDCCH monitoring opportunity is not included in or overlapped in a pure time unit or a non-XDD codeword, the UE may monitor the PDCCH candidates in the PDCCH monitoring opportunity.

[0175] According to the PDCCH monitoring opportunities of the non-XDD SS set and the XDD SS set, Fig.10 In the configuration examples of pure time units and XDD time units as shown, the UE monitors PDCCH candidates according to non-XDD SS set #0 in the pure time unit and monitors PDCCH candidates according to XDD SS set #1 in the XDD time unit. Specifically, the UE monitors PDCCH candidates in time slots 0, 2, 4, 6, 8, 10, 12, 17, and 18.

[0176] As a variation, the XDD SS set may also be set 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.

[0177] Alternatively, as another variation, the XDD SS set may be set only for a specific DCI (Downlink Control Information) format. For example, the specific DCI format may be DCI 0_0 / 1_0, DCI 2_0, DCI 2_1, DCI 2_2, DCI 2_3, DCI 0_1 / 1_1, DCI 2_5, DCI 3_0, DCI 3_1, and / or DCI 0_2 / 1_2.

[0178] In addition, as a variation, when there are multiple frequency domain modes for the XDD time unit, the UE may apply the same SS set configuration to any XDD time unit regardless of the frequency domain mode.

[0179] Alternatively, as another variation, when there are multiple frequency domain modes for an XDD time unit, the UE may also apply different SS set settings to XDD time units with different frequency domain modes. For example, in addition to the existing searchSpacesToAddModList, up to X additional SS set settings may be further set in the PDCCH-Config. Here, the value of X may also be set to be less than the number of frequency domain modes of the set XDD time unit. In addition, the value of X may be set either by specification or in the RRC setting.

[0180] In addition, for the PDCCH monitoring opportunities of the SS set in which frequency domain mode type #i is set in the XDD time unit, the UE may not assume that any of the PDCCH monitoring opportunities of the SS set in which frequency domain mode type #i is set in the XDD time unit is included in or overlapped in a pure time unit or an XDD time unit with other frequency domain mode types. In addition, in the case where the PDCCH monitoring opportunities of the SS set in which frequency domain mode type #i is set in the XDD time unit are included in or overlapped in a pure time unit or an XDD time unit with other frequency domain mode types, the UE may not monitor the PDCCH candidates in the PDCCH monitoring opportunities that are included in or overlapped in a pure time unit or an XDD time unit with other frequency domain mode types.

[0181] For example, in the case where two additional SS set settings are set, such as Fig.11As shown, the four IEs searchSpacesToAddModListForXdd1, searchSpacesToReleaseListForXdd1, searchSpacesToAddModListForXdd2, and searchSpacesToReleaseListForXdd2 may also be set in PDCCH-Config.

[0182] According to the PDCCH monitoring opportunities of the non-XDD SS set and the XDD SS set, Fig.12 In the configuration example of pure time unit and XDD time unit as shown, 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 mode type 1 in XDD time unit of frequency domain mode type 1, and monitors PDCCH candidates according to XDD SS set #2 of frequency domain mode type 2 in XDD time unit of frequency domain mode type 2. Specifically, the UE monitors PDCCH candidates in time slots 0, 2, 4, 6, 8, 12, 13, 14, and 18.

[0183] In Option 3 of the second embodiment, multiple controlResourceSetIds can also be set for SS set settings. That is, multiple CORESETs can be set. Here, controlResourceSetId is an IE for identifying CORESET.

[0184] As option 3-1, different CORESET associations may be applied for pure time units and XDD time units. That is, CORESET may be set for each of normal TDD operations and XDD operations. Specifically, the existing controlResourceSetId may be set for pure time units, and the new controlResourceSetIdForXdd may be set for XDD time units.

[0185] For each monitoring start position of the SS set, when the monitoring start position is included or overlapped in the pure time unit, the existing controlResourceSetId can also be used to determine the corresponding PDCCH monitoring opportunity and PDCCH candidate. On the other hand, when the monitoring start position is included or overlapped in the XDD time unit, the new controlResourceSetIdForXdd can also be used to determine the corresponding PDCCH monitoring opportunity and PDCCH candidate.

[0186] For example, Fig.13A As shown, two IEs, controlResourceSetId for pure time units and controlResourceSetIdForXdd for XDD time units, may be set in the SearchSpace setting.

[0187] In addition, if Fig. 13B As shown, the UE may also determine the PDCCH monitoring opportunity and PDCCH candidates according to controlResourceSetId in pure time units, and determine the PDCCH monitoring opportunity and PDCCH candidates according to controlResourceSetIdForXdd in XDD time units.

[0188] As a variation of option 3-1, multiple frequency domain modes may exist for an XDD time unit. As an example, when multiple frequency domain modes exist for an XDD time unit, a single controlResourceSetIdForXdd may be used for any XDD time unit regardless of the frequency domain mode.

[0189] Alternatively, as another example, different CORESET associations may be applied to different XDD time units with different frequency domain modes. For example, a maximum of X additional CORESET associations may be set. Here, the value of X may also be set to be less than the number of frequency domain modes of the set XDD time unit. In addition, the value of X may be specified by the specification or set in the RRC setting.

[0190] For example, Fig.14A As shown, the IEs of controlResourceSetIdForXdd-1, controlResourceSetIdForXdd-2, and controlResourceSetIdForXdd-3 for three additional frequency domain modes may be set in the SearchSpace setting.

[0191] In addition, if Fig. 14BAs shown, it may also be that the UE determines the PDCCH monitoring opportunities and PDCCH candidates according to controlResourceSetId in pure time units, determines the PDCCH monitoring opportunities and PDCCH candidates according to controlResourceSetIdForXdd-1 in XDD time units based on frequency domain mode type 1, and determines the PDCCH monitoring opportunities and PDCCH candidates according to controlResourceSetIdForXdd-2 in XDD time units based on frequency domain mode type 2.

[0192] In addition, in option 3-2, for each monitoring start position of the SS set, the UE can also determine the PDCCH monitoring opportunity and PDCCH candidate by trying the list of controlResourceSetId until an appropriate controlResoruceSetId is selected, or until all controlResourceSetIds are tried. That is, the UE selects an appropriate one from multiple CORESETs according to the SS settings.

[0193] For example, for the monitoring start position of the SS set, the UE may first determine the PDCCH monitoring opportunity and PDCCH candidate of the SS set by using the first CORESET ID. Alternatively, when any of the determined PDCCH candidates does not overlap with the time and frequency domain resources notified or set as UL or notified or set as UL transmission, the UE decides to use the CORESET to monitor the determined PDCCH candidate.

[0194] Alternatively, when any of the determined PDCCH candidates overlaps with the time and frequency domain resources that are notified or configured for UL or are notified or configured for UL transmission, the UE then determines the PDCCH monitoring opportunity and the PDCCH candidate by utilizing the configured CORESET ID until a CORESET ID is detected in which a PDCCH candidate that does not overlap with the time and frequency domain resources that are notified or configured for UL or are notified or configured for UL transmission is acquired.

[0195] In the case where the UE tries all CORESET IDs set for the SS set but cannot detect a CORESET ID for which a PDCCH candidate that does not overlap with the time and frequency domain resources notified or set for UL transmission is obtained, the default CORESET, the first CORESET, or the last CORESET may also be used to determine the PDCCH candidate. Alternatively, the UE may not assume such a situation. Alternatively, the UE may not monitor the PDCCH candidate at the monitoring start position of the SS set.

[0196] For example, Fig.15 As shown, the IE of controlResoruceSetAddForXdd for specifying the trial order of a plurality of controlResoruceSetIds may be set in the SearchSpace setting.

[0197] exist Fig.16 In the example shown, the UE tries each CORESET ID in the order of controlResourceSetId, controlResourceSetId-2, controlResourceSetId-3 and controlResourceSetId-4 to determine whether each CORESET ID includes a PDCCH candidate that does not overlap with the time and frequency domain resources notified or configured for UL or notified or configured for UL transmission.

[0198] In the example shown in the figure, for the PDCCH monitoring starting position #0, controlResourceSetId-3 is determined to be a CORESET that includes PDCCH candidates that do not overlap with the time and frequency domain resources notified or set as UL or notified or set as UL transmission. The UE can also use controlResourceSetId-3 to determine the PDCCH monitoring opportunities and PDCCH candidates.

[0199] In addition, for PDCCH monitoring starting position #1, controlResourceSetId is determined to be a CORESET that contains PDCCH candidates that do not overlap with the time and frequency domain resources notified or set for UL or notified or set for UL transmission. The UE can also use controlResourceSetId to determine the PDCCH monitoring opportunities and PDCCH candidates.

[0200] In Option 4 of the second embodiment, multiple frequencyDomainResources may also be set for CORESET. Multiple frequency domain modes are set for CORESET. Here, frequencyDomainResources is an IE that specifies frequency domain resources for CORESET.

[0201] As option 4-1, different frequencyDomainResources settings may also be applied to pure time units and XDD time units. That is, the frequency domain mode is set according to the usual TDD operation and XDD operation. For example, in addition to the existing frequencyDomainResources, a new frequencyDomainResourcesForXdd may be further set for CORESET. For each PDCCH monitoring opportunity for the SS set of CORESET, when the PDCCH monitoring opportunity is not included in or does not overlap in the XDD time unit or XDD codeword, the existing frequencyDomainResources may also be used to determine the corresponding PDCCH candidate. On the other hand, when the PDCCH monitoring opportunity is included in or overlaps in the XDD time unit or XDD codeword, the new frequencyDomainResourcesForXdd may also be used to determine the corresponding PDCCH candidate.

[0202] For example, Fig.17A As shown, two IEs, frequencyDomainResources for pure time units and frequencyDomainResourcesForXdd for XDD time units, may be set in the ControlResourceSet setting.

[0203] In addition, Fig. 17B In the example shown, the UE may monitor the PDCCH candidates determined based on frequencyDomainResources in pure time units, and monitor the PDCCH candidates determined based on frequencyDomainResourcesForXdd in XDD time units.

[0204] As a variation of option 4-1, multiple frequency domain modes may exist for an XDD time unit. As an example, when multiple frequency domain modes exist for an XDD time unit, a single frequencyDomainResourcesForXdd may be used for any XDD time unit regardless of the frequency domain mode.

[0205] Alternatively, as another example, different frequencyDomainResourcesForXdd settings may be applied to different XDD time units with different frequency domain modes. For example, a maximum of X additional frequencyDomainResourcesForXdd settings may be set. Here, the value of X may also be set to be less than the number of frequency domain modes of the set XDD time unit. In addition, the value of X may be specified by the specification or set in the RRC setting.

[0206] For example, Fig.18A As shown, the IEs of frequencyDomainResourcesForXdd-1, frequencyDomainResourcesForXdd-2, and frequencyDomainResourcesForXdd-3 for three additional frequency domain modes may be set in the ControlResourceSet setting.

[0207] In addition, if Fig.18B As shown, the UE may also determine the PDCCH candidates according to frequencyDomainResources in pure time units, according to frequencyDomainResourcesForXdd-1 in XDD time units based on frequency domain mode type 1, and according to frequencyDomainResourcesForXdd-2 in XDD time units based on frequency domain mode type 2.

[0208] As option 4-2, for each PDCCH monitoring opportunity for the SS set of the CORESET, the UE may also determine the PDCCH candidate by trying the list of frequencyDomainResources until an appropriate frequencyDomainResources is selected or all frequencyDomainResources are tried. That is, the UE may also select an appropriate one from multiple CORESETs according to the SS set.

[0209] For example, for each PDCCH monitoring opportunity for the SS set of CORESET, the UE may also first determine the PDCCH candidate by using the first frequencyDomainResources. When any of the determined PDCCH candidates does not overlap with the time and frequency domain resources notified or set as UL or notified or set as UL transmission, the UE may also decide to use the frequencyDomainResources to monitor the determined PDCCH candidate.

[0210] In the case where any of the determined PDCCH candidates overlaps with the time and frequency domain resources notified or configured as UL or notified or configured for UL transmission, the UE may then determine the PDCCH candidate by utilizing the configured frequencyDomainResources until the frequencyDomainResources in which a PDCCH candidate that does not overlap with the time and frequency domain resources notified or configured as UL or notified or configured for UL transmission is detected are obtained.

[0211] In the case where the UE tries all frequencyDomainResources but cannot detect the frequencyDomainResources for which the PDCCH candidate is obtained that does not overlap with the time and frequency domain resources notified or configured as UL or notified or configured for UL transmission, the default frequencyDomainResources, the initial frequencyDomainResources, or the last frequencyDomainResources may also be used to determine the PDCCH candidate. Alternatively, the UE may not assume such a situation. Alternatively, the UE may not monitor the PDCCH candidate in the PDCCH monitoring opportunity.

[0212] For example, Fig.19 As shown, the IE of frequencyDomainResourcesAddForXdd for specifying the trial order of a plurality of frequencyDomainResources may be set in the ControlResourceSet setting.

[0213] exist Fig. 20In the example shown, the UE tries each frequencyDomainResources in the order of frequencyDomainResources, frequencyDomainResources-2 and frequencyDomainResources-3 to determine whether each frequencyDomainResources includes a PDCCH candidate that does not overlap with the time and frequency domain resources notified or configured as UL or notified or configured for UL transmission.

[0214] In the example shown in the figure, for PDCCH monitoring opportunity #0, frequencyDomainResources-3 is determined to be the frequencyDomainResources that includes PDCCH candidates that do not overlap with the time and frequency domain resources notified or configured for UL or notified or configured for UL transmission, and the UE can also use frequencyDomainResources-3 to determine the PDCCH candidates.

[0215] Furthermore, for PDCCH monitoring opportunity #1, the frequencyDomainResources is determined to include PDCCH candidates that do not overlap with the time and frequency domain resources notified or configured as UL or notified or configured for UL transmission, and the UE may determine the PDCCH candidates using the frequencyDomainResources.

[0216] As option 5 of the second embodiment, multiple bitmaps of freqMonitorLocations may also be set for SS sets. That is, multiple bitmaps of freqMonitorLocations are set for SS sets. Here, freqMonitorLocations is an IE indicating a frequency monitoring location.

[0217] As option 5-1 of the second embodiment, different freqMonitorLocations bitmaps may also be set for pure time units and XDD time units. That is, the frequency domain mode is selected according to the usual TDD operation and XDD operation. For example, in addition to the existing freqMonitorLocations bitmap, a new freqMonitorLocationsForXdd may be further set for the SS set. For each PDCCH monitoring opportunity of the SS set, when the PDCCH monitoring opportunity is not included in or does not overlap in the XDD time unit or XDD codeword, the existing freqMonitorLocations may also be used to determine the corresponding PDCCH candidate. On the other hand, when the PDCCH monitoring opportunity is included in or overlaps in the XDD time unit or XDD codeword, the new freqMonitorLocationsForXdd may also be used to determine the corresponding PDCCH candidate.

[0218] For example, Fig.21A As shown, two IEs, freqMonitorLocations for pure time units and freqMonitorLocationsForXdd for XDD time units, can also be set in the SearchSpaceExt setting.

[0219] In addition, Fig. 21B In the example shown, the UE may monitor the PDCCH candidates determined based on freqMonitorLocations in pure time units, and monitor the PDCCH candidates determined based on freqMonitorLocationsForXdd in XDD time units.

[0220] As a variation of Option 5-1 of the second embodiment, multiple frequency domain modes may exist for an XDD time unit. For example, when multiple frequency domain modes exist for an XDD time unit, a single freqMonitorLocationsForXdd bitmap may be used for any XDD time unit regardless of the frequency domain mode.

[0221] Alternatively, as another example, different freqMonitorLocationsForXdd bitmaps may be applied to different XDD time units with different frequency domain modes. For example, a maximum of X additional freqMonitorLocationsForXdd bitmaps may be set. Here, the value of X may also be set to be less than the number of frequency domain modes of the set XDD time unit. In addition, the value of X may be specified by the specification or set in the RRC setting.

[0222] For example, Fig.22A As shown, IEs of freqMonitorLocationsForXdd-1, freqMonitorLocationsForXdd-2, and freqMonitorLocationsForXdd-3 for three additional frequency domain modes may be set in the SearchSpaceExt setting.

[0223] In addition, if Fig. 22B As shown, the UE may also monitor the PDCCH candidates determined based on freqMonitorLocations in pure time units, monitor the PDCCH candidates determined based on freqMonitorLocationsForXdd-1 in XDD time units based on frequency domain mode type 1, and monitor the PDCCH candidates determined based on freqMonitorLocationsForXdd-2 in XDD time units based on frequency domain mode type 2.

[0224] As option 5-2 of the second embodiment, for each PDCCH monitoring opportunity of the SS set, the UE may also determine the PDCCH candidate by trying the list of freqMonitorLocations until an appropriate freqMonitorLocations is selected or all freqMonitorLocations are tried. That is, the UE may also select an appropriate one from multiple bitmaps according to the SS set.

[0225] For example, for each PDCCH monitoring opportunity of the SS set, the UE may first determine the PDCCH candidates of the SS set by using the bitmap of the first freqMonitorLocations. Alternatively, when any of the determined PDCCH candidates does not overlap with the time and frequency domain resources notified or set as UL or notified or set as UL transmission, the UE decides to use the freqMonitorLocations to monitor the determined PDCCH candidates.

[0226] In the case where any of the determined PDCCH candidates overlaps with the time and frequency domain resources that are notified or configured for UL or are notified or configured for UL transmission, the UE may then determine the PDCCH candidate by utilizing the configured freqMonitorLocations until freqMonitorLocations are detected in which a PDCCH candidate that does not overlap with the time and frequency domain resources that are notified or configured for UL or are notified or configured for UL transmission is obtained.

[0227] In the case where the UE tries all the bitmaps of freqMonitorLocations set for the SS set but cannot detect the bitmap of freqMonitorLocations obtained with the PDCCH candidate that does not overlap with the time and frequency domain resources notified or set for UL or notified or set for UL transmission, the default freqMonitorLocations, the first freqMonitorLocations, or the last freqMonitorLocations may also be used to determine the PDCCH candidate. Alternatively, the UE may not assume such a situation. Alternatively, the UE may not monitor the PDCCH candidate in the PDCCH monitoring opportunity.

[0228] For example, Fig.23 As shown, the IE of freqMonitorLocationsAddForXdd for specifying the order of trying multiple freqMonitorLocations may be set in the SearchSpaceExt setting.

[0229] exist Fig.24 In the example shown, the UE tries each freqMonitorLocations in the order of freqMonitorLocations, freqMonitorLocations-2 and freqMonitorLocations-3 to determine whether each freqMonitorLocations includes a PDCCH candidate that does not overlap with the time and frequency domain resources notified or configured for UL or notified or configured for UL transmission.

[0230] In the example shown in the figure, for PDCCH monitoring opportunity #0, freqMonitorLocations-3 is determined to be the freqMonitorLocations that includes PDCCH candidates that do not overlap with the time and frequency domain resources notified or set as UL or notified or set as UL transmission, and the UE can also use freqMonitorLocations-3 to determine the PDCCH candidates.

[0231] In addition, for PDCCH monitoring opportunity #1, freqMonitorLocations is determined to include PDCCH candidates that do not overlap with the time and frequency domain resources notified or configured for UL or notified or configured for UL transmission, and the UE can also use freqMonitorLocations to determine the PDCCH candidates.

[0232] As Option 6 of the second embodiment, different interpretations of parameters configured for SS sets and / or CORESETs for pure time units and XDD time units may also be applied when determining PDCCH candidates. That is, the interpretation of PDCCH monitoring configuration is switched according to normal TDD operation and XDD operation.

[0233] For example, for PDCCH monitoring opportunities that are not included in or overlap with XDD time units, or do not overlap with XDD codewords, the freqMonitorLocations set in the SS set and / or the frequencyDomainResources set in the CORESET can also be based on the frequency resource settings of pure time units, that is, interpreted in the same way as Rel-15 / 16 / 17.

[0234] For a PDCCH monitoring opportunity that is included in or overlapped in an XDD time unit, or overlapped with an XDD symbol, freqMonitorLocations set by the SS set and / or frequencyDomainResources set by the CORESET may also be interpreted based on the frequency domain resources of the overlapping XDD time unit or XDD symbol. For example, for a PDCCH monitoring opportunity that is included in or overlapped in an XDD time unit, or overlapped with an XDD symbol, freqMonitorLocations set by the SS set and / or frequencyDomainResources set by the CORESET may also be rewritten as freqMonitorLocationsForXdd and / or frequencyDomainResourcesAddForXdd set by the CORESET.

[0235] As a variation of the second embodiment, different options may also be applied to different SS set types. For example, the SS set type may also 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.

[0236] In this way, according to the second embodiment, the UE may also receive a first PDCCH monitoring setting for a non-XDD time unit (e.g., a pure time unit) and a second PDCCH monitoring setting for an XDD time unit, and control PDCCH monitoring according to the first PDCCH monitoring setting and the second PDCCH monitoring setting. Correspondingly, the base station may also set a first PDCCH monitoring setting for a non-XDD time unit and a second PDCCH monitoring setting for an XDD time unit, and send the first PDCCH monitoring setting and the second PDCCH monitoring setting to the terminal.

[0237] Specifically, the first PDCCH monitoring setting may also be a search space set setting for a non-XDD time unit (for example, searchSpaceToAddModList), and the second PDCCH monitoring setting may also be one or more search space set settings for an XDD time unit (for example, searchSpaceToAddModListForXDD, searchSpaceToAddModListForXDD1, searchSpaceToAddModListForXDD2, etc.).

[0238] In addition, the first PDCCH monitoring setting may be a CORESET setting for a non-XDD time unit (for example, conrolResourceSetId), and the second PDCCH monitoring setting may be one or more CORESET settings for an XDD time unit (for example, conrolResourceSetIdForXdd, conrolResourceSetIdForXdd-1, conrolResourceSetIdForXdd-2, etc.).

[0239] In addition, the first PDCCH monitoring setting may also be a frequency domain resource setting for a non-XDD time unit (for example, frequencyDomainResources), and the second PDCCH monitoring setting may also be one or more frequency domain resource settings for an XDD time unit (for example, frequencyDomainResourcesForXdd, frequencyDomainResourcesForXdd-1, frequencyDomainResourcesForXdd-2, etc.).

[0240] In addition, the first PDCCH monitoring setting may be a frequency monitoring location setting for a non-XDD time unit (for example, freqMonitorLocations), and the second PDCCH monitoring setting may be one or more frequency monitoring location settings for an XDD time unit (for example, freqMonitorLocationsForXdd, freqMonitorLocationsForXdd-1, freqMonitorLocationsForXdd-2, etc.).

[0241] Furthermore, the second PDCCH monitoring configuration described above may also indicate priority rankings corresponding to a plurality of frequency domain modes.

[0242] In addition, the second PDCCH monitoring configuration may also be interpreted based on the first PDCCH monitoring configuration.

[0243] The above-mentioned setting or notification may also be sent based on at least one of RRC (Radio Resource Control) information element, DCI (Downlink Control Information), and MACCE (Medium Access Control Control Element). In addition, the present disclosure is not limited to the monitoring of PDCCH, and may also be applied to other types of control signals sent from a base station to a UE or other base stations (e.g., an IAB node, etc.).

[0244] In order to implement the above-mentioned XDD operation, the UE may also send UE capability information related to the XDD operation to the base station, and the base station may also notify or set the XDD operation to the UE based on the received UE capability information. Specifically, it may also be specified whether the UE supports UE capability information related to setting separate SS sets for XDD time units and pure time units. The UE may also send UE capability information related to whether it supports setting separate SS sets for XDD time units and pure time units to the base station.

[0245] In addition, it is also possible to specify whether the UE supports UE capability information related to multiple controlResourceSetIds configured for SS set configuration. The UE may also send UE capability information related to whether it supports multiple controlResourceSetIds configured for SS set configuration to the base station.

[0246] In addition, it may also be specified whether the UE supports UE capability information related to multiple frequencyDomainResources configured for the CORESET configuration. The UE may also send UE capability information related to whether it supports multiple frequencyDomainResources configured for the CORESET to the base station.

[0247] In addition, UE capability information related to whether the UE supports the bitmaps of multiple freqMonitorLocations configured for SS set configuration may also be specified. The UE may also send UE capability information related to whether it supports the bitmaps of multiple freqMonitorLocations configured for SS set configuration to the base station.

[0248] According to the second embodiment, in a case where an XDD operation is notified, configured, or applied to a cell for which PDCCH monitoring is configured, it is possible to define a UE operation related to an SS set and / or a CORESET configuration.

[0249] (Third Embodiment)

[0250] Discussions related to the PDCCH monitoring operation when the XDD operation is notified, set or applied to the cell for which PDCCH monitoring is set have not been conducted yet. Therefore, it is necessary to specify the PDCCH monitoring operation when the XDD operation is notified, set or applied to the cell for which PDCCH monitoring is set. That is, for PDCCH monitoring, the UE can also perform the following operations.

[0251] In addition, it should be noted that the third embodiment is independent of the second embodiment. That is, any option of the third embodiment can be applied together with any option of the second embodiment.

[0252] As option 1 of the third embodiment, the UE may also assume that the PDCCH monitoring opportunities of the PDCCH SS set do not overlap with the XDD symbols. That is, the UE may also assume that the PDCCH monitoring opportunities do not overlap with the XDD symbols. In this case, for example, Fig.25 In the example shown, the first PDCCH monitoring opportunity (symbol #0, #1) in the slot overlaps with the XDD symbol, resulting in an error.

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

[0254] As Option 3 of the third embodiment, a case where the PDCCH monitoring opportunity of the PDCCH SS set is included in or overlapped in the XDD time unit is being studied. That is, in the case where PDCCH monitoring overlaps with XDD resources, the UE may also perform the following operations.

[0255] As Option 3-1 of the third embodiment, when the PDCCH monitoring opportunity of the PDCCH SS set is included in or overlaps in the XDD time unit, the UE may not monitor the PDCCH candidates in the PDCCH monitoring opportunity regardless of whether the PDCCH monitoring opportunity overlaps with the XDD symbol. That is, the UE avoids PDCCH monitoring.

[0256] For example, in Fig. 27 In the example shown, time slot A is an XDD time slot, so the UE may not monitor PDCCH candidates in time slot A. On the other hand, time slot B is a pure DL time slot, so the UE may monitor PDCCH candidates in time slot B as well.

[0257] As option 3-2 of the third embodiment, in a case where the PDCCH monitoring opportunity of the PDCCH SS set is included in or overlaps in the XDD time unit, the UE decides whether to monitor the PDCCH candidates in the PDCCH monitoring opportunity based on whether the PDCCH monitoring opportunity overlaps with the XDD codeword. That is, the UE may also determine whether to perform monitoring based on whether the XDD resources overlap. It is also possible that in a case where the PDCCH monitoring opportunity of the PDCCH SS set overlaps with the XDD codeword, the UE does not monitor the PDCCH candidates in the PDCCH monitoring opportunity. On the other hand, it is also possible that in a case where the PDCCH monitoring opportunity of the PDCCH SS set does not overlap with the XDD codeword, the UE monitors the PDCCH candidates in the PDCCH monitoring opportunity.

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

[0259] As option 3-3 of the third embodiment, when the PDCCH monitoring opportunity of the PDCCH SS set is included in or overlapped in the XDD time unit, the UE may also decide whether to monitor the PDCCH candidate in the PDCCH monitoring opportunity overlapping with the XDD symbol based on whether the PDCCH candidate overlaps with the time and frequency domain resources notified or configured as UL or notified or configured for UL transmission. That is, the UE may also make a judgment based on whether UL is configured for the XDD resource.

[0260] As Option 3-3A of the third embodiment, when the PDCCH monitoring opportunity of the PDCCH SS set is included in or overlapped in the XDD time unit, for the PDCCH candidates in the PDCCH monitoring opportunity for the PDCCH SS set, the UE may also assume that none of the PDCCH candidates overlaps with the time and frequency domain resources that are notified or set as UL or notified or set as UL transmission. That is, similar to Rel-15 / 16, the UE may also monitor the PDCCH candidates in the PDCCH monitoring opportunity.

[0261] For example, in Fig.29 In the example shown, the first PDCCH monitoring opportunity (symbol #0, #1) overlaps with the time and frequency domain resources set as UL, which is an error situation.

[0262] As option 3-3B of the third embodiment, when the PDCCH monitoring opportunity of the PDCCH SS set is included in or overlaps in the XDD time unit, for the PDCCH candidates in the PDCCH monitoring opportunity for the PDCCH SS set, the UE may monitor the PDCCH candidates when the PDCCH candidates do not overlap with the time and frequency domain resources notified or set as UL or notified or set for UL transmission. On the other hand, the UE may not monitor the PDCCH candidates when the PDCCH candidates overlap with the time and frequency domain resources notified or set as UL or notified or set for UL transmission.

[0263] For example, in Fig.30 In the example shown, the first PDCCH monitoring opportunity (symbol #0, #1) overlaps with the time and frequency domain resources set as UL, so the UE may not monitor the PDCCH candidates in the first PDCCH monitoring opportunity. On the other hand, the second PDCCH monitoring opportunity (symbol #4, #5) does not overlap with the time and frequency domain resources set as UL, so the UE may also monitor the PDCCH candidates in the second PDCCH monitoring opportunity.

[0264] As a variation of the third embodiment, for each option of the third embodiment, the PDCCH SS set may not be limited to a specific SS type. For example, the specific SS type may be any of the following.

[0265] i) Type 0-PDCCH CSS set by pdcch-ConfigSIB1 in MIB, searchSpaceSIB1 in PDCCH-ConfigCommon, and searchSpaceZero in PDCCH-ConfigCommon

[0266] ii) Type 0A-PDCCH CSS set by searchSpaceOtherSystemInformation in PDCCH-ConfigCommon

[0267] iii) Type 1-PDCCH CSS set by ra-SearchSpace in PDCCH-ConfigCommon

[0268] iv) Type 2-PDCCH CSS set by pagingSearchSpace in PDCCH-ConfigCommon

[0269] v) Type 3-PDCCH CSS set configured by SearchSpace in PDCCH-Config with searchSpaceType=common and / or

[0270] vi) USS set configured by SearchSpace in PDCCH-Config with searchSpaceType=ue-Specific.

[0271] In addition, different options may also be applied to different PDCCH SS set types. For example, option 1 / 2 may also be applied to a Type 0-PDCCH CSS set, and option 3 may also be applied to a USS set.

[0272] As another variation of the third embodiment, for each option of the third embodiment, the PDCCH SS set may also be limited to an SS set for which a specific DCI format is set. For example, the SS set may also be a USS set for which dci-Formats (format) = formats0-0-And-1-0 or formats0-1-And-1-1, dci-Formats-MT-r16 = formats2-5, dci-FormatsExt-r16 = formats0-0-And-1-0, formats0-1-And-1-1, formats3-0, formats3-1 or formats3-0-And-3-1, and / or dci-FormatsExt-r16 = formats0-2-And-1-2, formats0-1-And-1-1 or formats0-2-And-1-2 is set.

[0273] In addition, different options may also be applied to PDCCH SS sets that are configured with different DCI formats.

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

[0275] Specifically, the UE may also assume that the PDCCH monitoring opportunity indicated by the PDCCH search space configuration does not overlap with the XDD time unit (eg, XDD symbol, XDD slot, etc.).

[0276] Furthermore, when a PDCCH monitoring opportunity indicated by the PDCCH search space configuration overlaps with an XDD time unit, the UE may avoid PDCCH monitoring in the PDCCH monitoring opportunity.

[0277] In addition, when the PDCCH monitoring opportunity indicated by the PDCCH search space setting overlaps with an XDD time unit (e.g., XDD time slot), the UE can also control PDCCH monitoring based on whether the PDCCH monitoring opportunity overlaps with the first time unit (e.g., XDD codeword) within the XDD time unit.

[0278] Furthermore, when a PDCCH monitoring opportunity indicated by the PDCCH search space configuration overlaps with an XDD time unit, the UE may control PDCCH monitoring in the PDCCH monitoring opportunity based on whether PDCCH candidates overlap with radio resources (i.e., time and frequency resources) for uplink transmission.

[0279] The above-mentioned setting or notification may also be sent based on at least one of RRC (Radio Resource Control) information element, DCI (Downlink Control Information), and MACCE (Medium Access Control Control Element). In addition, the present disclosure is not limited to the monitoring of PDCCH, and may also be applied to other types of control signals sent from a base station to a UE or other base stations (e.g., an IAB node, etc.).

[0280] In order to implement the above-mentioned XDD operation, the UE may also send UE capability information related to the XDD operation to the base station, and the base station may also notify or set the XDD operation to the UE based on the received UE capability information. Specifically, UE capability information related to whether the UE supports the situation where the PDCCH monitoring opportunity overlaps with the XDD time unit or XDD codeword may also be specified. The UE may also send UE capability information related to whether it supports the situation where the PDCCH monitoring opportunity overlaps with the XDD time unit or XDD codeword to the base station.

[0281] In addition, UE capability information related to whether the UE supports monitoring PDCCH candidates in PDCCH monitoring opportunities that include or overlap XDD time units or XDD codewords may also be specified. The UE may also send UE capability information related to whether it supports monitoring PDCCH candidates in PDCCH monitoring opportunities that include or overlap XDD time units or XDD codewords to the base station.

[0282] According to the third embodiment, when the XDD operation is notified, configured, or applied to the cell for which PDCCH monitoring is configured, it is possible to define the UE operation related to PDCCH monitoring.

[0283] (Fourth embodiment)

[0284] Discussions related to PDCCH monitoring capability and BD / CCE constraints when XDD operation is notified, configured or applied to a cell for which PDCCH monitoring is configured have not yet been conducted. Therefore, it is necessary to specify UE operations related to PDCCH monitoring capability and BD / CCE constraints when XDD operation is notified, configured or applied to a cell for which PDCCH monitoring is configured.

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

[0286] As option 1 of the fourth embodiment-1, the capability notification, setting or regulation for PDCCH monitoring on the BWP or cell may also be unified. That is, a common PDCCH monitoring capability for normal TDD operation and XDD operation may also be set. The capability notification, setting or regulation for PDCCH monitoring on the BWP or cell may also be based on the setting following monitoringCapabilityConfig-r16 or monitoringCapabilityConfig-r17.

[0287] As a variation of Option 1, when the BWP or cell is notified or configured regarding XDD operation, it is also conceivable that the PDCCH-Config of the BWP or cell is not notified or configured as the PDCCH monitoring capability of the time slot unit of Rel-15, the PDCCH monitoring capability of the span unit of Rel-16 and / or the PDCCH monitoring capability of multiple time slots of Rel-17.

[0288] As an example, when the BWP or cell is notified or configured regarding XDD operation, the UE may not assume that monitoringCapabilityConfig-r16=r15monitoringcapability or monitoringCapabilityConfig-r17=r15monitoringcapability is configured for PDCCH-Config on the BWP or cell. Alternatively, neither monitoringCapabilityConfig-r16 nor monitoringCapabilityConfig-r17 is configured for PDCCH-Config on the BWP or cell.

[0289] As another example, when the BWP or cell is notified or configured regarding 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.

[0290] As another example, when the BWP or the cell is notified or configured regarding the XDD operation, the UE may not assume that monitoringCapabilityConfig-r17=r17monitoringcapability is configured for PDCCH-Config on the BWP or the cell.

[0291] Here, an XDD SS set means an SS set set for an XDD time unit. In addition, a non-XDD SS set means an SS set set for a pure time unit. In addition, an XDD PDCCH monitoring opportunity means a PDCCH opportunity that includes or overlaps an XDD time unit or an XDD symbol. In addition, a non-XDD PDCCH monitoring opportunity means a PDCCH monitoring opportunity that does not include or overlap an XDD time unit or an XDD symbol.

[0292] As option 2 of the fourth embodiment-1, it is also possible to use the notification, setting or regulation of separate PDCCH monitoring capabilities for monitoring the XDD SS set and the non-XDD SS set on the BWP or cell, or the notification, setting or regulation of separate PDCCH monitoring capabilities for the XDD PDCCH monitoring opportunities and the non-XDD PDCCH monitoring opportunities on the BWP or cell. That is, it is also possible to set the PDCCH monitoring capability for each of the normal TDD operation and the XDD operation.

[0293] For non-XDD SS sets or non-XDD PDCCH monitoring opportunities, in order to notify or set the PDCCH monitoring capability of Rel-15 / 16 / 17, monitoringCapabilityConfig-r16 or monitoringCapabilityConfig-r17 may be used again.

[0294] Furthermore, the new RRC parameter monitoringCapabilityConfigForXdd may be reused to notify or configure the PDCCH monitoring capability of Rel-15 / 16 / 17 for monitoring an XDD SS set or an XDD PDCCH monitoring opportunity.

[0295] For example, the candidate values ​​of the new RRC parameter monitoringCapabilityConfigForXdd may be r15monitoringcapability, r16monitoringcapability and / or r17monitoringcapability. Specifically, monitoringCapabilityConfigForXdd may also have the following values.

[0296] monitoringCapabilityConfigForXdd={r15monitoringcapability, r16monitoringcapability, r17monitoringcapability}

[0297] monitoringCapabilityConfigForXdd={r15monitoringcapability, r16monitoringcapability}

[0298] monitoringCapabilityConfigForXdd={r15monitoringcapability, r17monitoringcapability}

[0299] monitoringCapabilityConfigForXdd={r16monitoringcapability, r17monitoringcapability}

[0300] In addition, when new RRC parameters are not set for monitoring the XDD SS set or the XDD PDCCH monitoring opportunity, the UE may perform the following operation.

[0301] As a first operation, when new RRC parameters are not set for monitoring the XDD SS set or XDD PDCCH monitoring opportunity, the UE may monitor the XDD SS set or XDD PDCCH monitoring opportunity based on the same PDCCH monitoring capability notified or set through monitoringCapabilityConfig-r16 or monitoringCapabilityConfig-r17.

[0302] As a second operation, when the new RRC parameter is not set for monitoring the XDD SS set or the XDD PDCCH monitoring opportunity, the UE may also apply the default PDCCH monitoring capability for monitoring the XDD SS set or the XDD PDCCH monitoring opportunity. For example, the default PDCCH monitoring capability may also be applied as the PDCCH monitoring capability of the time slot unit of Rel-15, the PDCCH monitoring capability of the span unit of Rel-16, or the PDCCH monitoring capability of multiple time slots of Rel-17.

[0303] As a third operation, when a specific PDCCH monitoring capability is notified or set through monitoringCapabilityConfig-r16 or monitoringCapabilityConfig-r17, the default PDCCH monitoring capability for monitoring an XDD SS set or an XDD PDCCH monitoring opportunity may always be the PDCCH monitoring capability of the time slot unit of Rel-15, the PDCCH monitoring capability of the span unit of Rel-16, or the PDCCH monitoring capability of multiple time slots of Rel-17. Otherwise, for monitoring of an XDD SS set or an XDD PDCCH monitoring opportunity, the UE may monitor the XDD SS set or the XDD PDCCH monitoring opportunity based on the same PDCCH monitoring capability notified or set through monitoringCapabilityConfig-r16 or monitoringCapabilityConfig-r17.

[0304] As a variation of option 2 of the fourth embodiment-1, the UE does not assume that: the specific PDCCH monitoring capability for non-XDD SS sets or non-XDD PDCCH monitoring opportunities (for example, Rel-15 / 16 / 17 monitoring capability) is notified through monitoringCapabilityConfig-r16 or monitoringCapabilityConfig-r17, and in addition, the specific PDCCH monitoring capability for non-XDD SS sets or non-XDD PDCCH monitoring opportunities (for example, Rel-15 / 16 / 17 monitoring capability) is set or specified at the same time.

[0305] In the fourth embodiment-2, regarding the maximum number of blind decoding (BD) or control channel elements (CCE) restrictions, PDCCH candidates or non-overlapping CCEs for the XDD SS set of the monitored object and the non-XDD SS set of the monitored object, or PDCCH candidates or non-overlapping CCEs for the XDD PDCCH monitoring opportunities of the monitored object and the non-XDD PDCCH monitoring opportunities of the monitored object can also be counted separately or together. That is, the upper limit of BD / CCE can also be counted by any of the following methods. The "monitoring object" here is intended to include the possibility that (for example, according to the rules of Embodiment 3 and / or Rel-15 / 16) PDCCH candidates that are determined not to be monitored can also be counted or not counted for the constraints of BD or CCE.

[0306] As a first operation, for the UE, regarding the maximum number of BDs or CCEs, the number of PDCCH candidates or non-overlapping CCEs for the XDD SS set of the monitoring object and the non-XDD SS set of the monitoring object, or the number of PDCCH candidates or non-overlapping CCEs for the XDD PDCCH monitoring opportunity of the monitoring object and the non-XDD PDCCH monitoring opportunity of the monitoring object may also be counted separately. That is, for each of the normal TDD operation and the XDD operation, the number of PDCCH candidates or non-overlapping CCEs may also be counted separately.

[0307] Regarding the non-XDD SS set or non-XDD PDCCH monitoring opportunity, the number of PDCCH candidates or non-overlapping CCEs for the non-XDD SS set of the monitoring object or the non-XDD PDCCH monitoring opportunity of the monitoring object may also be counted per time slot, per span, or per group of X time slots. Here, each time slot, each span, or each group of X time slots may also be based on the setting in accordance with monitoringCapabilityConfig-r16 or monitoringCapabilityConfig-r17. In addition, the maximum number of BDs or CCEs limited per time slot, per span, or per group of X time slots may also 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,μ}, these values ​​may also be the same as, or more or less than, the values ​​specified in Rel-15 / 16 / 17.

[0308] For example, when the time slot unit monitoring capability of Rel-15 is notified (for example, monitoringCapabilityConfig-r16=r15monitoringcapability or monitoringCapabilityConfig-r17=r15monitoringcapability is provided to the UE, or neither monitoringCapabilityConfig-r16 nor monitoringCapabilityConfig-r17 is set), the number of PDCCH candidates or non-overlapping CCEs of the non-XDD SS set to be monitored or the non-XDD PDCCH monitoring opportunity to be monitored is counted for each time slot, and the maximum number of BDs or CCE restrictions is set to {M1 PDCCH max,slot,μ , C1 PDCCH max ,slot,μ}.

[0309] Regarding the XDD SS set or XDD PDCCH monitoring opportunity, the number of PDCCH candidates or non-overlapping CCEs for the XDD SS set of the monitoring object or the XDD PDCCH monitoring opportunity of the monitoring object may also be counted per time slot, per span, or per group of X time slots. Here, each time slot, each span, or each group of X time slots may also be based on Example 4-1. In addition, the maximum number of BD or CCE restrictions per time slot, per span, or each group of X time slots may also 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,μ}, these values ​​may also be the same as, or more or less than, the values ​​specified in Rel-15 / 16 / 17.

[0310] For example, in the case where the time slot unit monitoring capability of Rel-15 is notified (for example, monitoringCapabilityConfigForXdd=r16monitoringcapability is provided to the UE), the number of PDCCH candidates or non-overlapping CCEs for the XDD SS set of the monitoring object or the XDD PDCCH monitoring opportunity of the monitoring object may also be counted per span, and the maximum number of BDs or CCEs restricted may also be {M2 PDCCH max,(X,Y),μ , C2 PDCCH max,(X,Y),μ}.

[0311] As a variation, (M1 PDCCH max,slot,μ +M2 PDCCH max,slot,μ ) can also be used with M specified in Rel-15 PDCCH max,slot,μ The same, or more, or less. In addition, (C1 PDCCH max,slot,μ +C2 PDCCH max,slot,μ ) can also be used with M specified in Rel-15 PDCCH max,slot,μ The same, more, or less.

[0312] As another modification, (M1 PDCCH max,(X,Y),μ +M2 PDCCH max,(X,Y),μ) can also be used with M specified in Rel-16 PDCCH max,(X,Y),μ The same, or more, or less. In addition, (C1 PDCCH max,(X,Y),μ +C2 PDCCH max,(X,Y),μ ) can also be used with M specified in Rel-16 PDCCH max,(X,Y),μ The same, more, or less.

[0313] As another modification, (M1 PDCCH max,Xsslot,μ +M2 PDCCH max,Xsslot,μ ) can also be used with M specified in Rel-17 PDCCH max,Xsslot,μ The same, or more, or less. In addition, (C1 PDCCH max,Xsslot,μ +C2 PDCCH max,Xsslot,μ ) can also be used with M specified in Rel-17 PDCCH max,Xsslot,μ The same, more, or less.

[0314] For example, Fig.31A The example shown is related to the PDCCH monitoring capability of each time slot of Rel-15. XDD USS#1 and XDD USS#3 are XDD PDCCH monitoring opportunities for monitoring. The maximum number of BDs or CCEs is {M2 PDCCH max,slot,μ , C2 PDCCH max,slot,μ In addition, non-XDD USS#2 and non-XDD CSS#1 are non-XDD PDCCH monitoring opportunities for monitoring objects, and the maximum number of BD or CCE restrictions is {M1 PDCCH max,slot,μ , C1 PDCCH max,slot,μ}.

[0315] For example, in addition, Fig.31B The example shown is also related to the PDCCH monitoring capability of each time slot of Rel-15. USS#1 and USS#3 are non-XDD PDCCH monitoring opportunities for monitoring. The maximum number of BD or CCE restrictions is {M2 PDCCH max,slot,μ , C2 PDCCH max,slot,μ USS#2 and CSS#1 are non-XDD PDCCH monitoring opportunities for monitoring objects. The maximum number of BD or CCE restrictions is {M1 PDCCH max,slot,μ , C1 PDCCHmax,slot,μ}.

[0316] As a second operation, regarding the maximum number of BDs or CCEs, the UE may also aggregate the counts (joint counting) of PDCCH candidates or non-overlapping CCEs for the XDD SS set of the monitored object and the non-XDD SS set of the monitored object, or PDCCH candidates or non-overlapping CCEs for the XDD PDCCH monitoring opportunity of the monitored object and the non-XDD PDCCH monitoring opportunity of the monitored object. That is, for normal TDD operation and XDD operation, PDCCH candidates or non-overlapping CCEs may also be aggregated and counted.

[0317] The number of PDCCH candidates or non-overlapping CCEs for the XDD SS set of the monitored object and the non-XDD SS set of the monitored object, or the number of PDCCH candidates or non-overlapping CCEs for the XDD PDCCH monitoring opportunities of the monitored object and the non-XDD PDCCH monitoring opportunities of the monitored object can also be counted in aggregate per time slot, per span, or per group of X time slots.

[0318] Any of each time slot, each span, or each group of X time slots may also be based on the granularity or unit (i.e., time slot level, span level, or time slot group level) of the monitoring capability notified or set for a non-XDD SS set or non-XDD PDCCH monitoring opportunity (e.g., based on monitoringCapabilityConfig-r16 and / or monitoringCapabilityConfig-r17) and the monitoring capability notified, set, or specified for an XDD SS set or XDD PDCCH monitoring opportunity (e.g., based on Embodiment 4-1). For example, Fig.32 The relationship between Rel-15 / 16 / 17 and PDCCH monitoring capability is summarized in the table shown.

[0319] When the granularity / unit (i.e., slot level, span level, or slot group level) for non-XDD SS set or non-XDD PDCCH monitoring opportunities and the granularity / unit (i.e., slot level, span level, or slot group level) for XDD SS set or XDD PDCCH monitoring opportunities are the same, the granularity or unit may also be used to count the number of PDCCH candidates or non-overlapping CCEs. On the other hand, when the granularity / unit (i.e., slot level, span level, or slot group level) for non-XDD SS set or non-XDD PDCCH monitoring opportunities and the granularity / unit (i.e., slot level, span level, or slot group level) for XDD SS set or XDD PDCCH monitoring opportunities are different, a larger granularity or unit may also be used to count the number of PDCCH candidates or non-overlapping CCEs.

[0320] Regarding PDCCH monitoring on a BWP or cell, the restricted maximum number of BDs or CCEs per slot, per span, or per group of X slots, e.g., {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,μ} can also be fixed or variable.

[0321] For example, the value of the maximum number of BDs or CCEs restricted for each time slot, each span, or each group of X time slots may also be variable depending on whether the time slot, the span, or the group of X time slots contains or overlaps an XDD time unit or an XDD symbol, whether it contains any XDD PDCCH monitoring opportunity of a monitored object, or whether it contains any PDCCH candidate of an XDD SS set of a monitored object.

[0322] As an example, {M2′ of the XDD time slot PDCCH max,slot,μ , C2′ PDCCH max,slot,μ} can also be used with {M1′ in non-XDD time slots PDCCH max,slot,μ , C1′ PDCCH max,slot,μ}different.

[0323] As another example, the XDD span {M2′ PDCCH max,(X,Y),μ , C2′ PDCCH max,(X,Y),μ} can also be used with non-XDD span {M1′ PDCCH max,(X,Y),μ , C1′ PDCCH max,(X,Y),μ}different.

[0324] As another example, {M2′ of the XDD time slot group PDCCH max,Xsslot,μ , C2′ PDCCH max,Xsslot,μ} can also be combined with {M1′ PDCCH max,Xsslot,μ , C1′ PDCCH max,Xsslot,μ}different.

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

[0326] For example, Fig.33A The example shown is related to the PDCCH monitoring capability of each time slot of Rel-15. XDD USS#1, non-XDD USS#2 and non-XDD CSS#1 are XDD PDCCH monitoring opportunities to be monitored. The maximum number of BDs or CCEs is {M1′ PDCCH max,slot,μ , C1′ PDCCH max,slot,μ}.

[0327] In addition, for example, Fig.33B The example shown is also related to the PDCCH monitoring capability of each time slot of Rel-15. XDD USS#1, non-XDD USS#2 and non-XDD CSS#1 are XDD PDCCH monitoring opportunities to be monitored. The maximum number of BDs or CCEs is {M2′ PDCCH max,slot,μ , C2′ PDCCH max,slot,μ}.

[0328] In addition, for example, the value of the maximum number of BD or CCE restrictions for each time slot, each span, or each group of X time slots may be certain on the BWP or cell, and the value of the BWP or cell notified or set for XDD operation may be the same as, or more or less than, the maximum number of BD or CCE restrictions specified in Rel-15 / 16 / 17.

[0329] For example, Fig.34A The example shown is related to the PDCCH monitoring capability of each time slot of Rel-15. 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 XDD PDCCH monitoring opportunities for monitoring. The maximum number of BD or CCE restrictions for cell #1 is {M2′ PDCCH max,slot,μ , C2′ PDCCH max,slot,μ}, the maximum number of BD or CCE restrictions for cell #2 is {M1′ PDCCH max,slot,μ , C1′ PDCCH max,slot,μ}.

[0330] In addition, for example, Fig.34BThe example shown is also related to the PDCCH monitoring capability of each time slot of Rel-15. Cell #1 is set to XDD operation, and cell #2 is not set to XDD operation. XDD USS #1, non-XDD USS #2, and non-XDD CSS #1 are XDD PDCCH monitoring opportunities for monitoring. The maximum number of BD or CCE restrictions for cell #1 is {M2′ PDCCH max,slot,μ , C2′ PDCCH max,slot,μ}, the maximum number of BD or CCE restrictions for cell #2 is {M1′ PDCCH max,slot,μ , C1′ PDCCH max,slot,μ}.

[0331] In this way, according to the fourth embodiment, the UE can also receive the PDCCH monitoring capability (e.g., monitoringCapabilityConfig) related to the XDD operation for the wireless resources (e.g., cell, BWP, etc.), and control the PDCCH monitoring according to the PDCCH monitoring capability. Correspondingly, the base station can also set the PDCCH monitoring capability related to the XDD operation for the wireless resources and send the PDCCH monitoring capability.

[0332] Specifically, the PDCCH monitoring capability may also be commonly set for XDD operation and non-XDD operation.

[0333] Furthermore, the PDCCH monitoring capability may also be set separately for XDD operation and non-XDD operation.

[0334] In addition, 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 collectively.

[0335] The above-mentioned setting or notification may also be sent based on at least one of RRC (Radio Resource Control) information element, DCI (Downlink Control Information), and MACCE (Medium Access Control Control Element). In addition, the present disclosure is not limited to the monitoring of PDCCH, and may also be applied to other types of control signals sent from a base station to a UE or other base stations (e.g., an IAB node, etc.).

[0336] In order to implement the above-mentioned XDD operation, the UE may also send UE capability information related to the XDD operation to the base station, and the base station may also notify or set the XDD operation to the UE based on the received UE capability information. Specifically, it may also be specified whether the UE supports monitoring of the XDD SS set (or XDD PDCCH monitoring opportunity) and non-XDD SS set (or XDD PDCCH monitoring opportunity) for unified capability notification, setting or provision related to UE capability information. The UE may also send UE capability information related to whether it supports monitoring of the XDD SS set (or XDD PDCCH monitoring opportunity) and non-XDD SS set (or XDD PDCCH monitoring opportunity) to the base station.

[0337] In addition, UE capability information related to separate capability notifications, settings or regulations for whether the UE supports monitoring of an XDD SS set (or an XDD PDCCH monitoring opportunity) may also be specified. The UE may also send UE capability information related to separate capability notifications, settings or regulations for whether it supports monitoring of an XDD SS set (or an XDD PDCCH monitoring opportunity) to the base station.

[0338] In addition, UE capability information related to whether the UE supports separate PDCCH candidates and non-overlapping CCE counts for monitoring XDD SS sets (or XDD PDCCH monitoring opportunities) and non-XDD SS sets (or XDD PDCCH monitoring opportunities) may also be specified. The UE may also send UE capability information related to whether it supports separate PDCCH candidates and non-overlapping CCE counts for monitoring XDD SS sets (or XDD PDCCH monitoring opportunities) and non-XDD SS sets (or XDD PDCCH monitoring opportunities) to the base station.

[0339] In addition, UE capability information related to whether the UE supports monitoring of PDCCH candidates and non-overlapping CCE counts used together with an XDD SS set (or XDD PDCCH monitoring opportunity) and a non-XDD SS set (or XDD PDCCH monitoring opportunity) may also be specified. The UE may also send UE capability information related to whether it supports monitoring of PDCCH candidates and non-overlapping CCE counts used together with an XDD SS set (or XDD PDCCH monitoring opportunity) and a non-XDD SS set (or XDDPDCCH monitoring opportunity) to the base station.

[0340] According to the fourth embodiment, when an XDD operation is notified, configured, or applied to a cell in which PDCCH monitoring is configured, it is possible to define UE operations related to PDCCH monitoring capability and BD / CCE restriction.

[0341] (Fifth Embodiment)

[0342] Discussions related to PDCCH overbooking when XDD operation is notified, set or applied for a cell for which PDCCH monitoring is set have not been conducted so far. Therefore, it is necessary to specify UE operations related to PDCCH overbooking when XDD operation is notified, set or applied for a cell for which PDCCH monitoring is set. That is, PDCCH overbooking is specified for XDD operation.

[0343] In the fifth embodiment, for a cell that is notified or set for XDD operation, overbooking is allowed or not allowed for a time slot, a span, or a group of X time slots that contains or overlaps an XDD time unit or an XDD codeword, for a time slot, a span, or a group of X time slots that contains an XDD SS set of a monitored object, or for a time slot, a span, or a group of X time slots that contains an XDD PDCCH monitoring opportunity of a monitored object.

[0344] In specific example 1, regarding the PDCCH monitoring capability of the time slot unit of Rel-15, overbooking may be allowed as follows, or overbooking may not be allowed. Here, the XDD time slot may also mean a time slot that includes or overlaps an XDD time unit or an XDD codeword, includes an XDD SS set of a monitoring object, and / or includes an XDD PDCCH monitoring opportunity of a monitoring object.

[0345] As a specific example 1-1, when XDD operation is notified or set for a cell, the UE may not assume that a number of PDCCH candidates longer than the BD or CCE restriction for the cell is monitored in a time slot. That is, as a difference from Rel-15, when XDD operation is notified or set for a Pcell or PScell, overbooking on the Pcell or PScell ​​may not be assumed.

[0346] As a specific example 1-2, when the time slot is an XDD time slot, the UE may not assume that a number of PDCCH candidates longer than the BD or CCE restriction for the cell is monitored in the time slot.

[0347] As a specific example 1-3, when a number of PDCCH candidates longer than the BD or CCE limit is monitored in a time slot, the UE may also discard specific PDCCH candidates in a time slot without exceeding the BD or CCE limit for the cell when the XDD operation is notified or set for the cell. That is, as a difference from Rel-15, overbooking may also be allowed on the Scell ​​when the XDD operation is notified or set for the Scell.

[0348] As specific example 1-4, when a number of PDCCH candidates longer than the BD or CCE limit are monitored in a time slot, the UE may discard specific PDCCH candidates in the time slot without exceeding the BD or CCE limit for the cell when the cell is an XDD time slot.

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

[0350] As another modification, the BD or CCE limit value for a cell having XDD operation may be the same as or different from the BD or CCE limit value specified in the monitoring capability of Rel-15 for a Pcell or PScell.

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

[0352] In specific example 2, regarding the PDCCH monitoring capability of the span unit of Rel-16, overbooking may be allowed as follows, or overbooking may not be allowed. Here, the XDD span may also mean a span that includes or overlaps an XDD time unit or an XDD symbol, includes an XDD SS set of a monitoring object, and / or includes an XDD PDCCH monitoring opportunity of a monitoring object.

[0353] As a specific example 2-1, when XDD operation is notified or set for a cell, the UE may not assume that a number of PDCCH candidates longer than the BD or CCE restriction for the cell is monitored in the span. That is, as a difference from Rel-16, when XDD operation is notified or set for a Pcell or PScell, overbooking on the Pcell or PScell ​​may not be assumed.

[0354] As a specific example 2-2, when the span is an XDD span, the UE may not assume that a number of PDCCH candidates longer than the BD or CCE restriction for the cell is monitored in the span.

[0355] As a specific 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 time slot), the UE may also discard specific PDCCH candidates in the span within the BD or CCE limit for the cell (or Pcell / PScell) when the XDD operation is notified or set for the cell (or Pcell / PScell). That is, as a difference from Rel-16, overbooking may be allowed on the Scell ​​when the XDD operation is notified or set for the Scell. In addition, overbooking may be allowed on spans other than the first span of the time slot when the XDD operation is notified or set for the cell.

[0356] As a specific example 2-4, when a number of PDCCH candidates longer than the BD or CCE limit are monitored in a span (or the first span in a time slot), the UE may also discard specific PDCCH candidates in the span without exceeding the BD or CCE limit for the cell (or Pcell / PScell) when the span on the cell (or Pcell / PScell) is an XDD span.

[0357] As a variation, the BD or CCE limit value for spans other than the first span in a time slot on a Pcell / PScell ​​may be the same as or different from the BD or CCE limit value specified in Rel-16 for the first span in a time slot on a Pcell or PScell.

[0358] As another modification, the BD or CCE limit value for a cell having XDD operation may be the same as or different from the BD or CCE limit value specified in the monitoring capability of Rel-16 for a Pcell or PScell.

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

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

[0361] As another modification example, the BD or CCE limit value for the XDD span may be the same as or different from the BD or CCE limit value specified in Rel-16 for the Pcell or PScell.

[0362] In specific example 3, regarding the multi-slot PDCCH monitoring capability of Rel-17, overbooking may be allowed as follows, or overbooking may not be allowed. Here, the XDD slot group may also mean a group of X slots (group of X_s slots) that includes or overlaps an XDD time unit or an XDD symbol, includes an XDD SS set of monitoring objects, and / or includes an XDD PDCCH monitoring opportunity of a monitoring object.

[0363] As a specific example 3-1, when XDD operation is notified or set for a cell, the UE may not assume that a number of PDCCH candidates longer than the BD or CCE restriction for the cell is monitored in a group of X time slots. That is, as a difference from Rel-17, when XDD operation is notified or set for a Pcell, overbooking on the Pcell may not be assumed.

[0364] As a specific example 3-2, when the group of X time slots is an XDD time slot group, the UE may not assume that a number of PDCCH candidates longer than the BD or CCE restriction for the cell is monitored in the group of X time slots.

[0365] As a specific example 3-3, when a number of PDCCH candidates longer than the BD or CCE limit is monitored in a group of X time slots, the UE may also discard specific PDCCH candidates in a group of X time slots without exceeding the BD or CCE limit for the (primary) cell when the XDD operation is notified or set for the (primary) cell. That is, as a difference from Rel-17, overbooking may be allowed on the Scell ​​when the XDD operation is notified or set for the Scell.

[0366] As a specific example 3-4, when a number of PDCCH candidates longer than the BD or CCE limit are monitored in a group of X time slots, the UE may also discard specific PDCCH candidates in the group of X time slots without exceeding the BD or CCE limit for the (primary) cell when the group of X time slots is an XDD time slot group.

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

[0368] As another modification, the BD or CCE limit value for a cell having XDD operation may be the same as or different from the BD or CCE limit value specified in the monitoring capability of Rel-17 for a Pcell or PScell.

[0369] As another modification, the BD or CCE limit value for the XDD time slot group may be the same as or different from the BD or CCE limit value specified in the monitoring capability of Rel-17 for the primary cell.

[0370] In this way, according to the fifth embodiment, the UE can also control the PDCCH overbooking in the XDD time unit in which the PDCCH monitoring is set, and perform PDCCH monitoring in the PDCCH monitoring opportunity selected in the controlled PDCCH overbooking. That is, the UE can also discard a part of the PDCCH monitoring opportunities that become overbooked. Correspondingly, the base station can also set the PDCCH monitoring opportunities that become overbooked in the XDD time unit in which the PDCCH monitoring is set, and send control information in the PDCCH monitoring opportunities.

[0371] The above-mentioned setting or notification may also be sent based on at least one of RRC (Radio Resource Control) information element, DCI (Downlink Control Information), and MACCE (Medium Access Control Control Element). In addition, the present disclosure is not limited to the monitoring of PDCCH, and may also be applied to other types of control signals sent from a base station to a UE or other base stations (e.g., an IAB node, etc.).

[0372] In order to implement the above-mentioned XDD operation, the UE may also send UE capability information related to the XDD operation to the base station, and the base station may also notify or set the XDD operation to the UE based on the received UE capability information. Specifically, UE capability information related to whether the UE supports PDCCH overbooking on the cell when the cell is notified or set for XDD operation may also be specified. The UE may also send UE capability information related to whether the UE supports PDCCH overbooking on the cell when the cell is notified or set for XDD operation to the base station.

[0373] In addition, UE capability information related to whether the UE supports PDCCH overbooking in an XDD time slot, an XDD span or an XDD time slot group may also be specified. The UE may also send UE capability information related to whether the UE supports PDCCH overbooking in an XDD time slot, an XDD span or an XDD time slot group to the base station.

[0374] In addition, UE capability information related to whether the UE supports PDCCH overbooking based on taking into account the XDD SS set (or XDD PDCCH monitoring opportunity) and the non-XDD SS set (or XDD PDCCH monitoring opportunity) may also be specified. The UE may also send UE capability information related to whether it supports PDCCH overbooking based on taking into account the XDD SS set (or XDD PDCCH monitoring opportunity) and the non-XDD SS set (or XDD PDCCH monitoring opportunity) to the base station.

[0375] According to the fifth embodiment, when an XDD operation is notified, configured, or applied to a cell for which PDCCH monitoring is configured, it is possible to define a UE operation related to PDCCH overbooking.

[0376] (Sixth Embodiment)

[0377] Discussions related to PDCCH overbooking in the case where an XDD operation is notified, set or applied to a cell for which PDCCH monitoring is set have not been conducted yet. Therefore, it is necessary to specify UE operations related to PDCCH overbooking in the case where an XDD operation is notified, set or applied to a cell for which PDCCH monitoring is set. That is, rules for PDCCH overbooking can also be specified for XDD operations. Specifically, for PDCCH overbooking allowed in Example 5, UE operations for selecting a PDCCH monitoring opportunity for monitoring / discarding objects from the PDCCH monitoring opportunities that become overbooked are specified.

[0378] In the sixth embodiment, overbooking may be allowed for a time slot, a span or a group of X time slots when the time slot, a span or a group of X time slots contains or overlaps an XDD time unit or an XDD codeword, or contains any XDD SS set of a monitoring object, or contains any XDD PDCCH monitoring opportunity of a monitoring object.

[0379] As option 0 of the sixth embodiment, the existing PDCCH oversubscription rule of Rel-15 / 16 / 17 may be reused, that is, the rule of Rel-15 / 16 / 17 is applied.

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

[0381] In option 1-1 of the sixth embodiment, the priority ordering of “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” may also be applied.

[0382] As option 1-1A of the sixth embodiment, it is also possible not to envision discarding non-XDD CSS. XDD CSS, non-XDD USS, and XDD USS may also be discarded based on priority. For example, the UE may also not envision that the number of PDCCH candidates or non-overlapping CCEs of non-XDD CSS in any time slot / span / group of X time slots exceeds the BD or CCE limit. In addition, as a variation, it is also possible not to envision discarding XDD CSS. Non-XDD CSS, XDD USS, and non-XDD USS may also be discarded based on priority.

[0383] As option 1-1B of the sixth embodiment, it is also possible not to envision discarding non-XDD CSS and XDD CSS. Non-XDD USS and XDD USS may also be discarded based on priority. For example, the UE may also not envision that the number of PDCCH candidates or non-overlapping CCEs of non-XDD CSS and XDD CSS in any time slot / span / group of X time slots exceeds the BD or CCE limit. In addition, as a variation, it is also possible not to envision discarding XDD CSS and non-XDD CSS. XDD USS and non-XDD USS may also be discarded based on priority.

[0384] As option 1-1C of the sixth embodiment, it is also possible not to envision discarding non-XDD CSS, XDD CSS, and non-XDD USS. XDD USS may also be discarded based on priority. For example, the UE may also not envision that the number of PDCCH candidates or non-overlapping CCEs of non-XDD CSS, XDD CSS, and non-XDD USS in any time slot / span / group of X time slots exceeds the BD or CCE limit. In addition, as a variation, it is also possible not to envision discarding non-XDD CSS, XDD CSS, and non-XDD USS. Non-XDD USS may also be discarded based on priority.

[0385] 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 also be Fig.35 Prioritize as shown.

[0386] In option 1-2 of the sixth embodiment, the priority ordering of “non-XDD SS set has higher or lower priority than XDD SS set”→“CSS has higher priority than USS”→“smaller SS index has higher priority than larger SS index” may also be applied.

[0387] As option 1-2A of the sixth embodiment, it is also possible not to envision discarding non-XDD CSS. Non-XDD USS, XDD CSS, and XDD USS may also be discarded based on priority. For example, the UE may also not envision that the number of PDCCH candidates or non-overlapping CCEs of non-XDD CSS in any time slot / span / group of X time slots exceeds the BD or CCE limit. In addition, as a variation, it is also possible not to envision discarding XDD CSS. XDD USS, non-XDD CSS, and non-XDD USS may also be discarded based on priority.

[0388] As option 1-2B of the sixth embodiment, it is also possible not to envision discarding non-XDD CSS and non-XDD USS. XDD CSS and XDD USS may also be discarded based on priority. For example, the UE may also not envision that the number of PDCCH candidates or non-overlapping CCEs of non-XDD CSS and non-XDD USS in any time slot / span / group of X time slots exceeds the BD or CCE limit. In addition, as a variation, it is also possible not to envision discarding XDD CSS and XDD USS. Non-XDD CSS and non-XDD USS may also be discarded based on priority.

[0389] As option 1-2C of the sixth embodiment, it is also possible not to envision discarding non-XDD CSS, non-XDD USS and XDD CSS. XDD USS can also be discarded based on priority. For example, the UE may also not envision that the number of PDCCH candidates or non-overlapping CCEs of non-XDD CSS, non-XDD USS and XDD CSS in any time slot / span / group of X time slots exceeds the BD or CCE limit. In addition, as a variation, it is also possible not to envision discarding XDD CSS, XDD USS and non-XDD CSS. Non-XDD USS can also be discarded based on priority.

[0390] 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 also be Fig.36 Prioritize as shown.

[0391] For example, in Fig.37In the symbol configuration shown, according to the rules of Rel-15, XDD CSS#1 and XDD USS#1 can be monitored, and non-XD USS#2 can be discarded. In addition, according to option 1-1, XDD CSS#1 and non-XD USS#2 can be monitored, and XDD USS#1 can be discarded. In addition, according to option 1-2, non-XD USS#2 and XDD CSS#1 can be monitored, and XDD USS#1 can be discarded.

[0392] As option 2 of the sixth embodiment, it is also possible to consider whether the overbooking is an XDD PDCCH monitoring opportunity or a non-XDD PDCCH monitoring opportunity. Here, the XDD PDCCH monitoring opportunity means a PDCCH monitoring opportunity that includes or overlaps an XDD time unit or an XDD symbol. In addition, the non-XDD PDCCH monitoring opportunity means a PDCCH monitoring opportunity that does not include or overlap an XDD time unit or an XDD symbol.

[0393] In option 2-1 of the sixth embodiment, the priority order of "CSS has higher priority than USS" → "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" can also be applied.

[0394] As option 2-1A of the sixth embodiment, it is also possible not to envision discarding PDCCH candidates for non-XDD PDCCH monitoring opportunities of the CSS set. The PDCCH candidates for XDD PDCCH monitoring opportunities of the CSS set, non-XDD PDCCH monitoring opportunities of the USS set, and XDD PDCCH monitoring opportunities of the USS set may also be discarded based on priority. For example, the UE may also not envision that the number of PDCCH candidates or non-overlapping CCEs for non-XDD PDCCH monitoring opportunities of the CSS set in any group of time slots / spans / X time slots exceeds the BD or CCE limit. In addition, as a variation, it is also possible not to envision discarding PDCCH candidates for XDD PDCCH monitoring opportunities of the CSS set. The PDCCH candidates for non-XDD PDCCH monitoring opportunities of the CSS set, XDD PDCCH monitoring opportunities of the USS set, and non-XDD PDCCH monitoring opportunities of the USS set may also be discarded based on priority.

[0395] As option 2-1B of the sixth embodiment, it is also possible not to envision discarding the PDCCH candidates of the non-XDD PDCCH monitoring opportunities of the CSS set and the XDD PDCCH monitoring opportunities of the CSS set. The PDCCH candidates of the non-XDD PDCCH monitoring opportunities of the USS set and the XDD PDCCH monitoring opportunities of the USS set may also be discarded based on priority. For example, the UE may also not envision that the number of PDCCH candidates of the non-XDD PDCCH monitoring opportunities of the CSS set and the XDD PDCCH monitoring opportunities of the CSS set in any group of time slots / spans / X time slots or non-overlapping CCEs exceeds the BD or CCE limit. In addition, as a variation, it is also possible not to envision discarding the PDCCH candidates of the XDD PDCCH monitoring opportunities of the CSS set and the non-XDD PDCCH monitoring opportunities of the CSS set. The PDCCH candidates of the XDD PDCCH monitoring opportunities of the USS set and the non-XDD PDCCH monitoring opportunities of the USS set may also be discarded based on priority.

[0396] As option 2-1C of the sixth embodiment, it is also possible not to envision discarding the PDCCH candidates of the non-XDD PDCCH monitoring opportunities of the CSS set, the XDD PDCCH monitoring opportunities of the CSS set, and the non-XDD PDCCH monitoring opportunities of the USS set. The PDCCH candidates of the XDD PDCCH monitoring opportunities of the USS set may also be discarded based on priority. For example, the UE may also not envision that the number of PDCCH candidates or non-overlapping CCEs of the non-XDD PDCCH monitoring opportunities of the CSS set, the XDD PDCCH monitoring opportunities of the CSS set, and the non-XDD PDCCH monitoring opportunities of the USS set in any group of time slots / spans / X time slots exceeds the BD or CCE limit. In addition, as a variant, it is also possible not to envision discarding the PDCCH candidates of the XDD PDCCH monitoring opportunities of the CSS set, the non-XDD PDCCH monitoring opportunities of the CSS set, and the XDD PDCCH monitoring opportunities of the USS set. The PDCCH candidates of the non-XDD PDCCH monitoring opportunities of the USS set may also be discarded based on priority.

[0397] According to the priority and variation of option 2-1 of the sixth embodiment, the XDD PDCCH monitoring opportunity of the CSS set, the non-XDD PDCCH monitoring opportunity of the CSS set, the XDD PDCCH monitoring opportunity of the USS set, and the non-XDD PDCCH monitoring opportunity of the USS set may also be as follows: Fig.38 Prioritize as shown.

[0398] In option 2-2 of the sixth embodiment, the priority order of "non-XDD PDCCH monitoring opportunity has higher or lower priority than XDD PDCCH monitoring opportunity" → "CSS has higher priority than USS" → "smaller SS index has higher priority than larger SS index" can also be applied.

[0399] As option 2-2A of the sixth embodiment, it is also possible not to envision discarding PDCCH candidates for non-XDD PDCCH monitoring opportunities of the CSS set. PDCCH candidates for non-XDD PDCCH monitoring opportunities of the USS set, XDD PDCCH monitoring opportunities of the CSS set, and XDD PDCCH monitoring opportunities of the USS set may also be discarded based on priority. For example, the UE may also not envision that the number of PDCCH candidates or non-overlapping CCEs for non-XDD PDCCH monitoring opportunities of the CSS set in any group of time slots / spans / X time slots exceeds the BD or CCE limit. In addition, as a variation, it is also possible not to envision discarding PDCCH candidates for XDD PDCCH monitoring opportunities of the CSS set. PDCCH candidates for XDD PDCCH monitoring opportunities of the USS set, non-XDD PDCCH monitoring opportunities of the CSS set, and non-XDD PDCCH monitoring opportunities of the USS set may also be discarded based on priority.

[0400] As option 2-2B of the sixth embodiment, it is also possible not to envision discarding the PDCCH candidates of the non-XDD PDCCH monitoring opportunities of the CSS set and the non-XDD PDCCH monitoring opportunities of the USS set. The PDCCH candidates of the XDD PDCCH monitoring opportunities of the CSS set and the XDD PDCCH monitoring opportunities of the USS set may also be discarded based on priority. For example, the UE may also not envision that the number of PDCCH candidates or non-overlapping CCEs of the non-XDD PDCCH monitoring opportunities of the CSS set, the non-XDD PDCCH monitoring opportunities of the USS set and the XDD PDCCH monitoring opportunities of the CSS set in any group of time slots / spans / X time slots exceeds the BD or CCE limit. In addition, as a variant, it is also possible not to envision discarding the PDCCH candidates of the XDD PDCCH monitoring opportunities of the CSS set and the XDD PDCCH monitoring opportunities of the USS set. The PDCCH candidates of the non-XDD PDCCH monitoring opportunities of the CSS set and the non-XDD PDCCH monitoring opportunities of the USS set may also be discarded based on priority.

[0401] As option 2-2C of the sixth embodiment, it is also possible not to envision discarding the PDCCH candidates of the non-XDD PDCCH monitoring opportunities of the CSS set, the non-XDD PDCCH monitoring opportunities of the USS set, and the XDD PDCCH monitoring opportunities of the CSS set. The PDCCH candidates of the XDD PDCCH monitoring opportunities of the USS set may also be discarded based on priority. For example, the UE may also not envision that the number of PDCCH candidates or non-overlapping CCEs of the non-XDD PDCCH monitoring opportunities of the CSS set, the non-XDD PDCCH monitoring opportunities of the USS set, and the XDD PDCCH monitoring opportunities of the CSS set in any group of time slots / spans / X time slots exceeds the BD or CCE limit. In addition, as a variant, it is also possible not to envision discarding the PDCCH candidates of the 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 CSS set. The PDCCH candidates of the non-XDD PDCCH monitoring opportunities of the USS set may also be discarded based on priority.

[0402] According to the priority and variation of option 2-2 of the sixth embodiment, the XDD PDCCH monitoring opportunity of the CSS set, the non-XDD PDCCH monitoring opportunity of the CSS set, the XDD PDCCH monitoring opportunity of the USS set, and the non-XDD PDCCH monitoring opportunity of the USS set may also be as follows: Fig.39 Prioritize as shown.

[0403] For example, in Fig.40 In the symbol configuration shown, according to the rules of Rel-15, CSS#1 (XDDMO) and USS#1 (XDD MO) can be monitored, and USS#2 (non-XDD MO) can be discarded. In addition, according to option 2-1, CSS#1 (XDDMO) and USS#2 (non-XDD MO) can be monitored, and USS#1 (XDD MO) can be discarded. In addition, according to option 2-2, USS#1 (XDDMO) and CSS#1 (XDD MO) can be monitored, and USS#1 (XDD MO) can be discarded.

[0404] In this way, according to the sixth embodiment, the UE can also control the PDCCH overbooking in the XDD time unit in which the PDCCH monitoring is set, and when performing PDCCH monitoring in the PDCCH monitoring opportunity selected in the controlled PDCCH overbooking, the PDCCH monitoring opportunity is selected according to the priority ranking. That is, the UE can also discard a part of the PDCCH monitoring opportunities from the PDCCH monitoring opportunities that become overbooked according to the priority ranking.

[0405] Specifically, the PDCCH monitoring opportunity can also be selected based on a first priority between the common search space (CSS) and the user-specific search space (USS), a second priority between the non-XDD search space set (non-XDD SS) and the XDD search space set (XDD SS), and a third priority between the search space index (SS index).

[0406] In addition, the PDCCH monitoring opportunity may be further selected based on a fourth priority ranking between the non-XDD PDCCH monitoring opportunity and the XDD PDCCH monitoring opportunity.

[0407] The above-mentioned setting or notification may also be sent based on at least one of RRC (Radio Resource Control) information element, DCI (Downlink Control Information), and MACCE (Medium Access Control Control Element). In addition, the present disclosure is not limited to the monitoring of PDCCH, and may also be applied to other types of control signals sent from a base station to a UE or other base stations (e.g., an IAB node, etc.).

[0408] In order to implement the above-mentioned XDD operation, the UE may also send UE capability information related to the XDD operation to the base station, and the base station may also notify or set the XDD operation to the UE based on the received UE capability information. Specifically, it may also be specified that when the cell is notified or set for the XDD operation, the UE capability information related to whether the UE supports PDCCH overbooking on the cell. The UE may also send UE capability information related to whether the UE supports PDCCH overbooking on the cell when the cell is notified or set for the XDD operation to the base station.

[0409] In addition, UE capability information related to whether the UE supports PDCCH overbooking in an XDD time slot, an XDD span or an XDD time slot group may also be specified. The UE may also send UE capability information related to whether the UE supports PDCCH overbooking in an XDD time slot, an XDD span or an XDD time slot group to the base station.

[0410] In addition, it may also be specified whether the UE supports UE capability information related to PDCCH overbooking based on consideration of the XDD SS set (or XDD PDCCH monitoring opportunity) and the non-XDD SS set (or XDD PDCCH monitoring opportunity). The UE may also send to the base station UE capability information related to whether it supports PDCCH overbooking based on consideration of the XDD SS set (or XDD PDCCH monitoring opportunity) and the non-XDD SS set (or XDD PDCCH monitoring opportunity).

[0411] According to the sixth embodiment, when an XDD operation is notified, configured, or applied to a cell for which PDCCH monitoring is configured, it is possible to define a UE operation related to PDCCH overbooking.

[0412] (Seventh Embodiment)

[0413] Discussions related to the PDCCH monitoring beam when the XDD operation is notified, set or applied to the cell for which PDCCH monitoring is set have not been conducted yet. Therefore, it is necessary to specify the UE operation related to the PDCCH monitoring beam when the XDD operation is notified, set or applied to the cell for which PDCCH monitoring is set. That is, with respect to the PDCCH monitoring beam, the UE may also perform the following operations.

[0414] In the seventh embodiment, the UE may monitor a PDCCH candidate that includes or overlaps PDCCH monitoring opportunities in a plurality of CORESETs that are set to the same or different qcl-types (qcl-Type) for the nature of "type D" related to the activated DL BWP of more than one cell and is set for operations based on a single cell operation or carrier aggregation (CA) in the same frequency band. In the above case, the UE monitors PDCCH only in a certain CORESET and any other CORESET among the plurality of CORESETs that are set to the same qcl-type (qcl-Type) for the nature of "type D" as the CORESET on the activated DL BWP of a cell of more than one cell. In the case where any cell is notified or set for XDD operation, the CORESET may also be determined as the CORESET of the SS with the highest priority.

[0415] In Option 1 of the seventh embodiment, the existing Rel-15 / 16 rules can be reused for priority sorting. That is, the priority sorting of "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" can also be applied. As for the CORESET, if it exists, it can also correspond to the CSS set with the smallest index in the cell with the smallest index containing the CSS, and if not, it can also correspond to the USS set with the smallest index in the cell with the smallest index.

[0416] In Option 2 of the seventh embodiment, whether or not there is a cell notified / configured for XDD operation may be considered for the determination.

[0417] As option 2-1 of the seventh embodiment, “CSS has a higher priority than USS” → “cells that are not notified or set for XDD operation have a higher or lower priority than cells that are notified or set for XDD operation” → “smaller cell indexes have a higher priority than larger cell indexes” → “smaller SS indexes have a higher priority than larger SS indexes” may also be applied. Fig.41 Prioritization as shown.

[0418] As option 2-2 of the seventh embodiment, “a cell that is not notified or configured for XDD operation has a higher or lower priority than a cell that is notified or configured for XDD operation” → “CSS has a higher priority than USS” → “a smaller cell index has a higher priority than a larger cell index” → “a smaller SS index has a higher priority than a larger SS index”, such as Fig.42 Prioritization as shown.

[0419] According to the priority ranking of Option 1, Option 2-1, and Option 2-2, the 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 as shown in, for example, Fig. 43. In addition, XDD operation is notified or set for Cell#1, but XDD operation is not notified or set for Cell#2.

[0420] exist Fig.43A In the present embodiment, 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.

[0421] exist Fig.43B In the example, the priority sorting of option 2-1 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.

[0422] exist Fig.43C In the example, the priority sorting of option 2-2 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.

[0423] Similarly, according to the priority of Option 1, Option 2-1, and Option 2-2, the four PDCCH monitoring beams, CSS#1 of Cell#1, USS#2 of Cell#1, USS#3 of Cell#1, and USS#1 of Cell#2, can be prioritized as shown in, for example, Fig. 44. In addition, XDD operation is notified or set for Cell#1, and XDD operation is not notified or set for Cell#2.

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

[0425] exist Fig.44B In the example, the priority sorting of option 2-1 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.

[0426] exist Fig.44C In the example, the priority sorting of option 2-2 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.

[0427] In Option 3 of the seventh embodiment, whether there is an XDD SS set or a non-XDD SS set may also be considered in the determination. Here, the XDD SS set means an SS set in which the XDD time unit is set. In addition, the non-XDD SS set means an SS set in which the pure time unit is set.

[0428] As option 3-1 of the seventh embodiment, “non-XDD SS set has higher or lower priority than XDD SS set” → “CSS has higher priority than USS” → “smaller cell index has higher priority than larger cell index” → “smaller SS index has higher priority than larger SS index”, such as Fig.45 Prioritization as shown.

[0429] As option 3-2 of the seventh embodiment, “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 a larger cell index” → “smaller SS index has a higher priority than a larger SS index”, such as Fig.46 Prioritization as shown.

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

[0431] In addition, as another variation of option 3-2 of the seventh embodiment, a priority order such as “CSS has a higher priority than USS” → “non-XDD USS set has a higher or lower priority than XDD USS set” → “smaller cell index has a higher priority than a larger cell index” → “smaller SS index has a higher priority than a larger SS index” may also be applied.

[0432] As option 3-3 of the seventh embodiment, “CSS has a higher priority than USS” → “smaller cell index has a higher priority than a larger cell index” → “non-XDD SS set has a higher or lower priority than XDD SS set” → “smaller SS index has a higher priority than a larger SS index”, such as Fig.47 Prioritization as shown.

[0433] As a variation of option 3-3 of the seventh embodiment, the following priority ordering may be applied: “CSS has a higher priority than USS” → “Smaller cell index has a higher priority than larger cell index” → “Non-XDD CSS set has a higher or lower priority than XDD CSS set” → “Smaller SS index has a higher priority than larger SS index”.

[0434] In addition, as another variation of option 3-3 of the seventh embodiment, the following priority ordering may be applied: “CSS has a higher priority than USS” → “a smaller cell index has a higher priority than a larger cell index” → “a non-XDD USS set has a higher or lower priority than an XDD USS set” → “a smaller SS index has a higher priority than a larger SS index”.

[0435] According to the priority order of Option 1, Option 3-1, Option 3-2, and Option 3-3 of the seventh embodiment, the 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 as shown in, for example, Fig. 48. In addition, CSS#1 of cell#1, USS#2 of cell#1, and USS#1 of cell#2 are XDD SS sets, and USS#3 of cell#1 and CSS#2 of cell#2 are non-XDD SS sets.

[0436] exist Fig.48A In the present embodiment, 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.

[0437] exist Fig.48B In the example, the priority sorting of option 3-1 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.

[0438] exist Fig.48C In the example, the priority sorting of option 3-2 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.

[0439] exist Fig.48D In the example, the priority sorting of option 3-3 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.

[0440] According to the priority order of Option 1, Option 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 as shown in Fig. 49. In addition, CSS#1 of cell#1 and USS#2 of cell#1 are XDD SS sets, and USS#3 of cell#1 and USS#1 of cell#2 are non-XDD SS sets.

[0441] exist Fig.49AIn the present embodiment, the existing rules of Rel-15 / 16 are applied, and the CSS#1 of cell#1, the USS#2 of cell#1, the USS#3 of cell#1 and the USS#1 of cell#2 are prioritized in descending order of priority.

[0442] exist Fig.49B In the example, the priority sorting of option 3-1 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.

[0443] exist Fig.49C In the example, the priority sorting of option 3-2 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.

[0444] exist Fig.49D In the example, the priority sorting of option 3-3 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.

[0445] In option 4 of the seventh embodiment, whether there is an XDD PDCCH monitoring opportunity or a non-XDD PDCCH monitoring opportunity may also be considered in the determination. Here, an XDD PDCCH monitoring opportunity means a PDCCH monitoring opportunity that includes or overlaps an XDD time unit or an XDD symbol. In addition, a non-XDD PDCCH monitoring opportunity means a PDCCH monitoring opportunity that does not include or overlap an XDD time unit or an XDD symbol.

[0446] As option 4-1 of the seventh embodiment, “non-XDD PDCCH monitoring opportunity has higher or lower priority than XDD PDCCH monitoring opportunity” → “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”, such as Fig.45 Prioritization as shown.

[0447] As option 4-2 of the seventh embodiment, “CSS has a higher priority than USS” → “non-XDD PDCCH monitoring opportunity has a higher or lower priority than XDD PDCCH monitoring opportunity” → “smaller cell index has a higher priority than a larger cell index” → “smaller SS index has a higher priority than a larger SS index”, such as Fig.46 Prioritization as shown.

[0448] As option 4-3 of the seventh embodiment, the following scheme may also be applied: “CSS has a higher priority than USS” → “a smaller cell index has a higher priority than a larger cell index” → “a non-XDD PDCCH monitoring opportunity has a higher or lower priority than an XDD PDCCH monitoring opportunity” → “a smaller SS index has a higher priority than a larger SS index”. Fig.47 Prioritization as shown.

[0449] According to the priority order of Option 1, Option 4-1, 4-2 and 4-3 of the seventh embodiment, the 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 as shown in Fig. 50. In addition, 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.

[0450] exist Fig.50A In the present embodiment, 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.

[0451] exist Fig.50B In the example, the priority sorting of option 4-1 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.

[0452] exist Fig.50C In the example, the priority sorting of option 4-2 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.

[0453] exist Fig.50D In the example, the priority sorting of option 4-3 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.

[0454] According to the priority order of Option 1, Option 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 as shown in Fig. 51. In addition, 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.

[0455] exist Fig.51A In the present embodiment, the existing rules of Rel-15 / 16 are applied, and the CSS#1 of cell#1, the USS#2 of cell#1, the USS#3 of cell#1 and the USS#1 of cell#2 are prioritized in descending order of priority.

[0456] exist Fig.51B In the example, the priority sorting of option 4-1 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.

[0457] exist Fig.51C In the example, the priority sorting of option 4-2 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.

[0458] exist Fig.51D In the example, the priority sorting of option 4-3 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.

[0459] In Option 5 of the seventh embodiment, whether there is a cell notified or configured for XDD operation and whether there is an XDD SS set or a non-XDD SS set may also be considered for the determination.

[0460] As option 5-1 of the seventh embodiment, the following priority ranking 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 set has a higher or lower priority than XDDSS set” → “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”.

[0461] As option 5-2 of the seventh embodiment, the following priority order 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”.

[0462] As a variation of option 5-2 of the seventh embodiment, the following priority ranking 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”.

[0463] As option 5-3 of the seventh embodiment, the following priority order 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 a larger cell index” → “Non-XDD SS set has a higher or lower priority than XDD SS set” → “Smaller SS index has a higher priority than a larger SS index”.

[0464] As a variation of option 5-3 of the seventh embodiment, the following priority order 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 a 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 a larger SS index”.

[0465] As option 5-4 of the seventh embodiment, the following priority rankings may be applied: “CSS has a higher priority than USS” → “Cells that are not notified or configured for XDD operation have a higher or lower priority than cells that are notified or configured for XDD operation” → “Non-XDD SS 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”.

[0466] As a variation of option 5-4 of the seventh embodiment, the following priority ranking may be applied: “CSS has a higher priority than USS” → “Cells that are not notified or configured for XDD operation have a higher or lower priority than cells that are notified or configured for XDD operation” → “Non-XDD 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”.

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

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

[0469] 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 also be considered for the determination.

[0470] As option 6-1 of the seventh embodiment, the following priority ordering may be applied: “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” → “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”.

[0471] As option 6-2 of the seventh embodiment, the following priority ordering 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” → “smaller SS index has higher priority than larger SS index”.

[0472] As option 6-3 of the seventh embodiment, the following priority ordering may also 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”.

[0473] As option 6-4 of the seventh embodiment, the following priority ordering may also be applied: “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 opportunity has a higher or lower priority than XDD PDCCH monitoring opportunity” → “smaller cell index has a higher priority than a larger cell index” → “smaller SS index has a higher priority than a larger SS index”.

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

[0475] As option 6-5 of the seventh embodiment, the following priority order may be applied: “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 a 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 a larger SS index”.

[0476] As a variation of option 6-5 of the seventh embodiment, the following priority order may be applied: “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 a 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 a larger SS index”.

[0477] As option 6-6 of the seventh embodiment, the following priority order may be applied: “CSS has a higher priority than USS” → “Smaller cell index has a higher priority than larger cell index” → “Non-XDD SS set has a higher or lower priority than XDD SS set” → “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”.

[0478] As a variation of option 6-6 of the seventh embodiment, the following priority order may be applied: “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” → “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”.

[0479] In Option 7 of the seventh embodiment, whether there is a cell notified or configured for XDD operation and whether there is an XDD PDCCH monitoring opportunity or a non-XDD PDCCH monitoring opportunity may also be considered for determination.

[0480] As option 7-1 of the seventh embodiment, the following priority order may be applied: “Cells that are not notified or configured for XDD operation have a higher or lower priority than cells that are notified or configured for XDD operation” → “Non-XDD PDCCH monitoring opportunities have a higher or lower priority than XDD PDCCH monitoring opportunities” → “CSS has a higher priority than USS” → “Smaller cell indexes have a higher priority than larger cell indexes” → “Smaller SS indexes have a higher priority than larger SS indexes”.

[0481] As option 7-2 of the seventh embodiment, the following priority order may be applied: “Cells that are not notified or configured for XDD operation have a higher or lower priority than cells that are notified or configured for XDD operation” → “CSS has a higher priority than USS” → “Non-XDD PDCCH monitoring opportunities have a higher or lower priority than XDD PDCCH monitoring opportunities” → “Smaller cell indexes have a higher priority than larger cell indexes” → “Smaller SS indexes have a higher priority than larger SS indexes”.

[0482] As option 7-3 of the seventh embodiment, the following priority order 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 a 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 a larger SS index”.

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

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

[0485] In option 8 of the seventh embodiment, it is also possible to consider whether there is a cell that is notified or configured for XDD operation, 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.

[0486] As option 8-1 of the seventh embodiment, the following priority order 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 set has a higher or lower priority than XDD SS set” → “Non-XDD PDCCH monitoring opportunity has a higher or lower priority than XDD PDCCH monitoring opportunity” → “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”.

[0487] As option 8-2 of the seventh embodiment, the following priority order 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 set has a higher or lower priority than XDDSS set” → “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”.

[0488] As option 8-3 of the seventh embodiment, the following priority order 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 set has a higher or lower priority than XDDSS set” → “CSS has a higher priority than USS” → “Smaller cell index has a higher priority than a 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 a larger SS index”.

[0489] As option 8-4 of the seventh embodiment, the following priority order 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 opportunity has a higher or lower priority than XDD PDCCH monitoring opportunity” → “Smaller cell index has a higher priority than larger cell index” → “Smaller SS index has a higher priority than larger SS index”.

[0490] As option 8-5 of the seventh embodiment, the following priority order may be applied: “CSS has a higher priority than USS” → “Cells that are not notified or configured for XDD operation have a higher or lower priority than cells that are notified or configured for XDD operation” → “Smaller cell indexes have a higher priority than larger cell indexes” → “Non-XDD SS sets have a higher or lower priority than XDD SS sets” → “Non-XDD PDCCH monitoring opportunities have a higher or lower priority than XDD PDCCH monitoring opportunities” → “Smaller SS indexes have a higher priority than larger SS indexes”.

[0491] As option 8-6 of the seventh embodiment, the following priority order 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 a 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 a larger SS index”.

[0492] As option 8-7 of the seventh embodiment, the following priority order may be applied: “CSS has a higher priority than USS” → “Cells that are not notified or configured for XDD operation have a higher or lower priority than cells that are notified or configured for XDD operation” → “Non-XDD SS 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”.

[0493] As option 8-8 of the seventh embodiment, the following priority order 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 SS set has a higher or lower priority than XDD SS set” → “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”.

[0494] As options 8-9 of the seventh embodiment, the following priority rankings may be applied: “CSS has a higher priority than USS” → “Cells that are not notified or configured for XDD operation have a higher or lower priority than cells that are notified or configured for XDD operation” → “Smaller cell indexes have a higher priority than larger cell indexes” → “Non-XDD SS sets have a higher or lower priority than XDD SS sets” → “Non-XDD PDCCH monitoring opportunities have a higher or lower priority than XDD PDCCH monitoring opportunities” → “Smaller SS indexes have a higher priority than larger SS indexes”.

[0495] In this way, according to the seventh embodiment, the UE can also select the PDCCH monitoring beam in the XDD time unit in which the PDCCH monitoring is set, and perform PDCCH monitoring for the selected PDCCH monitoring beam. Correspondingly, the base station can also control the PDCCH monitoring beam in the XDD time unit in which the PDCCH monitoring is set, and send control information through the PDCCH monitoring beam.

[0496] Specifically, the UE may also select a PDCCH monitoring beam based on priority.

[0497] In addition, the PDCCH monitoring beam can also be selected based on a first priority between a common search space (CSS) and a user-specific search space (USS), a second priority between cell indices, and a third priority between search space indices (SS indices).

[0498] In addition, the PDCCH monitoring beam can be further selected based on one or more of a fourth priority order between cells for which XDD operation is set or notified and cells for which XDD operation is not set or notified, a fifth priority order between a non-XDD search space (non-XDD SS) set and an XDD search space (XDD SS) set, and a sixth priority order between non-XDD PDCCH monitoring opportunities and XDD PDCCH monitoring opportunities.

[0499] The above-mentioned setting or notification may also be sent based on at least one of RRC (Radio Resource Control) information element, DCI (Downlink Control Information), and MACCE (Medium Access Control Control Element). In addition, the present disclosure is not limited to the monitoring of PDCCH, and may also be applied to other types of control signals sent from a base station to a UE or other base stations (e.g., an IAB node, etc.).

[0500] In order to implement the above-mentioned XDD operation, the UE may also send the UE capability information related to the XDD operation to the base station, and the base station may also notify or set the XDD operation to the UE based on the received UE capability information. Specifically, it may also be specified whether to support the decision to include or overlap the TCI state for PDCCH monitoring of PDCCH monitoring opportunities based on whether the cell is notified or set for XDD operation, whether there is an XDD SS set or a non-XDD SS set, and / or whether there is an XDD PDCCH monitoring opportunity. The UE may also send the UE capability information related to the TCI state for PDCCH monitoring of PDCCH monitoring opportunities based on whether the cell is notified or set for XDD operation, whether there is an XDD SS set or a non-XDD SS set, and / or whether there is an XDD PDCCH monitoring opportunity to the base station.

[0501] According to the seventh embodiment, when the XDD operation is notified, set, or applied to the cell for which PDCCH monitoring is set, it is possible to define the UE operation related to the PDCCH monitoring beam.

[0502] For each of the above-mentioned embodiments, the application embodiments, options and / or operations may be notified or set through high-level parameters, may be notified or reported through the UE as UE capability information, may be specified in the specification, or may be determined by the setting of high-level parameters and the reported UE capability information.

[0503] <Hardware Structure>

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

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

[0506] For example, a base station, a user terminal, etc. in one embodiment of the present disclosure may also function as a computer that performs processing of the wireless communication method of the present disclosure. Fig.52 1001, memory 1002, storage 1003, communication device 1004, input device 1005, output device 1006, bus 1007, etc.

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

[0508] For each function in the base station 10 and the user terminal 20, this is achieved by reading specific software (program) into hardware such as the processor 1001 and the memory 1002, so that the processor 1001 performs calculations and controls communication based on the communication device 1004, or controls at least one of the reading and writing of data in the memory 1002 and the storage 1003.

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

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

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

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

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

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

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

[0516] In addition, the base station 10 and the user terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), or an FPGA (Field Programmable Gate Array), and may implement a part or all of each functional block through the hardware. For example, the processor 1001 may also be implemented using at least one of these hardware.

[0517] The notification of information is not limited to the methods / implementations described in the present disclosure, and other methods may also be used. For example, the notification of information may also be implemented through physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), high-level signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals or a combination thereof. In addition, RRC signaling may also be referred to as RRC messages, such as RRC Connection Setup messages, RRC Connection Reconfiguration messages, and the like.

[0518] The various modes and embodiments described in the present disclosure may also be applied to mobile communication systems utilizing LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (x is, for example, an integer or a decimal)), FRA (Future Radio Access), NR (New Radio), New radio access (NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE At least one of IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth (registered trademark), other appropriate systems, and next-generation systems expanded, modified, produced, and specified based on them. In addition, multiple systems may also be applied in combination (for example, a combination of at least one of LTE and LTE-A with 5G, etc.).

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

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

[0521] Information, etc. (※Refer to the item "information, signal") can be output from a higher layer (or lower layer) to a lower layer (or higher layer). It can also be input and output via multiple network nodes.

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

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

[0524] Each method / implementation method described in the present disclosure may be used alone or in combination, or may be switched during execution. In addition, notification of specific information (e.g., notification of "is X") is not limited to being performed explicitly, but may also be performed implicitly (e.g., not notifying the specific information).

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

[0526] Software, whether referred to as software, firmware, middleware, microcode, hardware description language, or by other names, shall be construed broadly to mean instructions, instruction sets, codes, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, execution threads, procedures, functions, or the like.

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

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

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

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

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

[0532] The names used in the above parameters are not restrictive in all respects. In addition, the mathematical formulas using these parameters may differ from those explicitly disclosed in this disclosure. Various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable names, and therefore, the various names assigned to these various channels and information elements are not restrictive in all respects.

[0533] In the present disclosure, the terms "base station (BS)," "wireless base station", "fixed station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "access point", "transmission point", "reception point", "transmission / reception point", "cell", "sector", "cell group", "carrier", "component carrier" and the like are used interchangeably. Base stations are also sometimes referred to as macrocells, small cells, femtocells, picocells and the like.

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

[0535] In the present disclosure, the base station sending information to the terminal may be rewritten as the base station instructing the terminal to control or operate based on the information.

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

[0537] Mobile stations are also sometimes referred to by those skilled in the art as subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, handsets, user agents, mobile clients, clients, or several other appropriate terms.

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

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

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

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

[0542] The drive unit 2 is constituted by, for example, an engine, an electric motor, or a hybrid power of an engine and an electric motor.

[0543] The steering unit 3 includes at least a steering wheel (also referred to as 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 a user.

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

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

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

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

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

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

[0550] 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, various information is sent and received between the external device via wireless communication. The communication module 13 can also be located anywhere inside or outside the electronic control unit 10. The external device can also be, for example, a base station, a mobile station, etc.

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

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

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

[0554] (Summary of Implementation Methods)

[0555] As described above, according to one embodiment of the present invention, a terminal is provided, comprising: a receiving unit for receiving notifications or settings related to XDD (Cross Division Duplex) operations on wireless resources; and a control unit for controlling uplink transmission or downlink reception in the wireless resources according to the notifications or settings related to the XDD operations.

[0556] According to the above configuration, it is possible to limit the radio resources (for example, cells, BWP, etc.) in which the XDD operation can be set.

[0557] In one embodiment, the receiving unit may receive a notification or setting related to an XDD operation of a frequency resource unit for a time unit on a bandwidth part, and regarding the notification or setting related to the XDD operation of the frequency resource unit, the first frequency resource of the bandwidth part is notified or set as uplink transmission or downlink reception, and the second frequency resource of the bandwidth part is notified or set as downlink reception or uplink transmission. According to this embodiment, the XDD operation can be set in units of frequency resources.

[0558] In one embodiment, the receiving unit may receive a notification or setting related to an XDD operation of a terminal unit for a time unit on a bandwidth portion, and regarding the notification or setting related to the XDD operation of the terminal unit, notify or set the time unit as uplink transmission or downlink reception to the first terminal, and notify or set the time unit as downlink reception or uplink transmission to the second terminal. According to this embodiment, the XDD operation can be set in terminal units.

[0559] In one embodiment, the receiving unit may receive a notification or setting indicating a bandwidth portion of a cell for which an XDD operation is set or a bandwidth portion for XDD operation of the cell. According to this embodiment, the BWP for which the XDD operation is set can be specified.

[0560] In addition, according to one embodiment of the present disclosure, a base station is provided, comprising: a sending unit that sends a notification or setting related to an XDD (Cross Division Duplex) operation for wireless resources; and a control unit that controls uplink transmission or downlink reception in the wireless resources according to the notification or setting related to the XDD operation.

[0561] According to the above configuration, it is possible to limit the radio resources (for example, cells, BWP, etc.) in which the XDD operation can be set.

[0562] In addition, according to one embodiment of the present invention, a wireless communication method performed by a terminal is provided, comprising: receiving a notification or setting related to an XDD (Cross Division Duplex) operation for a wireless resource; and controlling uplink transmission or downlink reception in the wireless resource according to the notification or setting related to the XDD operation.

[0563] According to the above configuration, it is possible to limit the radio resources (for example, cells, BWP, etc.) in which the XDD operation can be set.

[0564] According to one aspect of the present disclosure, a terminal is provided, including: a receiving unit that receives a PDCCH monitoring configuration for an XDD (Cross Division Duplex) operation; and a control unit that controls PDCCH monitoring according to the PDCCH monitoring configuration.

[0565] According to the above configuration, when the XDD operation can be set for the PDCCH monitoring resource, PDCCH monitoring in the XDD operation can be appropriately realized.

[0566] In one embodiment, the PDCCH monitoring configuration may also include a first PDCCH monitoring configuration for a non-XDD time unit and a second PDCCH monitoring configuration for an XDD time unit. According to this embodiment, an appropriate PDCCH monitoring configuration can be configured for each of XDD operation and non-XDD operation.

[0567] In one embodiment, the first PDCCH monitoring configuration may also include one or more of a search space set configuration, a CORESET (control resource set (COntrol 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 also 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 configured for each of the XDD operation and the non-XDD operation.

[0568] In one embodiment, the PDCCH monitoring setting may also include a PDCCH search space setting, and the control unit may also control the PDCCH monitoring according to whether the PDCCH monitoring opportunity indicated by the PDCCH search space setting overlaps with the XDD time unit. According to this embodiment, PDCCH monitoring can be appropriately implemented according to whether the PDCCH monitoring opportunity indicated by the PDCCH search space setting overlaps with the XDD time unit.

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

[0570] According to the above configuration, when the XDD operation can be set for the PDCCH monitoring resource, PDCCH monitoring in the XDD operation can be appropriately realized.

[0571] Furthermore, according to one aspect of the present disclosure, there is provided a wireless communication method performed by a terminal, comprising: receiving a PDCCH monitoring configuration for an XDD (Cross Division Duplex) operation; and controlling PDCCH monitoring according to the PDCCH monitoring configuration.

[0572] According to the above configuration, when the XDD operation can be set for the PDCCH monitoring resource, PDCCH monitoring in the XDD operation can be appropriately realized.

[0573] Furthermore, according to one aspect of the present disclosure, a terminal is provided, comprising: a receiving unit that receives a PDCCH monitoring capability related to an XDD (Cross Division Duplex) operation for a radio resource; and a control unit that controls PDCCH monitoring based on the PDCCH monitoring capability.

[0574] According to the above configuration, when the XDD operation can be set for the PDCCH monitoring resource, PDCCH monitoring in the XDD operation can be appropriately implemented according to the PDCCH monitoring capability.

[0575] In one embodiment, the PDCCH monitoring capability may also be set commonly for XDD operation and non-XDD operation. According to this embodiment, PDCCH monitoring in XDD operation can be appropriately implemented according to the PDCCH monitoring capability.

[0576] In one embodiment, the PDCCH monitoring capability may also be set separately for XDD operation and non-XDD operation. According to this embodiment, PDCCH monitoring in XDD operation can be properly implemented according to the PDCCH monitoring capability.

[0577] In one embodiment, the control unit may also count the PDCCH candidates or non-overlapping control channel elements in the XDD operation and the PDCCH candidates or non-overlapping control channel elements in the non-XDD operation separately or in aggregate. According to this embodiment, PDCCH monitoring in the XDD operation can be appropriately implemented according to the PDCCH monitoring capability.

[0578] According to one aspect of the present disclosure, a base station is provided, comprising: a control unit configured to set a PDCCH monitoring capability related to an XDD (Cross Division Duplex) operation for a radio resource; and a transmission unit configured to transmit the PDCCH monitoring capability.

[0579] According to the above configuration, when the XDD operation can be set for the PDCCH monitoring resource, PDCCH monitoring in the XDD operation can be appropriately implemented according to the PDCCH monitoring capability.

[0580] Furthermore, according to one aspect of the present disclosure, there is provided a wireless communication method performed by a terminal, comprising: receiving a PDCCH monitoring capability related to an XDD (Cross Division Duplex) operation for a wireless resource; and controlling PDCCH monitoring according to the PDCCH monitoring capability.

[0581] According to the above configuration, when the XDD operation can be set for the PDCCH monitoring resource, PDCCH monitoring in the XDD operation can be appropriately implemented according to the PDCCH monitoring capability.

[0582] In addition, according to one embodiment of the present disclosure, a terminal is provided, comprising: a control unit that controls PDCCH over-booking 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 over-booking.

[0583] According to the above configuration, when the XDD operation can be set for the PDCCH monitoring resource, a PDCCH monitoring opportunity is appropriately selected in PDCCH overbooking, and PDCCH monitoring is performed in the selected PDCCH monitoring opportunity.

[0584] In one embodiment, the control unit may also select the PDCCH monitoring opportunity according to the priority ranking. According to this embodiment, the PDCCH monitoring opportunity can be appropriately selected according to the priority ranking.

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

[0586] In one embodiment, the PDCCH monitoring opportunity may be further selected based on a fourth priority ranking between non-XDD PDCCH monitoring opportunities and XDD PDCCH monitoring opportunities. According to this embodiment, the PDCCH monitoring opportunity can be appropriately selected according to the priority ranking.

[0587] According to one aspect of the present disclosure, a base station is provided, comprising: a control unit that sets an overbooked PDCCH monitoring opportunity in an XDD (Cross Division Duplex) time unit in which PDCCH monitoring is set; and a transmission unit that transmits control information in the PDCCH monitoring opportunity.

[0588] According to the above configuration, when the XDD operation can be set for the PDCCH monitoring resource, a PDCCH monitoring opportunity is appropriately selected in PDCCH overbooking, and PDCCH monitoring is performed in the selected PDCCH monitoring opportunity.

[0589] In addition, according to one embodiment of the present disclosure, a wireless communication method performed by a terminal is provided, 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.

[0590] According to the above configuration, when the XDD operation can be set for the PDCCH monitoring resource, a PDCCH monitoring opportunity can be appropriately selected in PDCCH overbooking, and PDCCH monitoring can be performed in the selected PDCCH monitoring opportunity.

[0591] In addition, according to one embodiment of the present disclosure, a terminal is provided, comprising: 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.

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

[0593] In one embodiment, the control unit may also select the PDCCH monitoring beam according to the priority order. According to this embodiment, the PDCCH monitoring beam can be appropriately selected.

[0594] In one embodiment, the PDCCH monitoring beam may also be selected based on a first priority between common search spaces and user-specific search spaces, a second priority between cell indices, and a third priority between search space indices. According to this embodiment, the PDCCH monitoring beam can be appropriately selected.

[0595] In one embodiment, the PDCCH monitoring beam may be further selected based on one or more of a fourth priority order between cells for which XDD operation is set or notified and cells for which XDD operation is not set or notified, a fifth priority order between non-XDD search space sets and XDD search space sets, and a sixth priority order between non-XDD PDCCH monitoring opportunities and XDD PDCCH monitoring opportunities. According to this embodiment, the PDCCH monitoring beam can be appropriately selected.

[0596] In addition, according to one embodiment of the present disclosure, a base station is provided, comprising: 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 through the PDCCH monitoring beam.

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

[0598] In addition, according to one embodiment of the present disclosure, a wireless communication method performed by a terminal is provided, 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.

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

[0600] (Supplementary Implementation Methods)

[0601] The terms "determining" and "determining" used in the present disclosure sometimes include a variety of operations. "Determining" and "determining" may include, for example, considering matters that have been judged, calculated, calculated, processed, derived, investigated, searched (for example, searched in a table, database or other data structure), confirmed (ascertaining) as matters that have been "determined" or "determined", etc. In addition, "determining" and "determining" may include matters that have been received (for example, receiving information), transmitted (for example, sending and receiving information), input, output, accessed (for example, accessed data in a memory) as matters that have been "determined" or "determined", etc. In addition, "determining" and "determining" may include matters that have been resolved (resolving), selected (selecting), chosen (choosing), established (establishing), compared (comparing), etc. as matters that have been "determined" or "determined". In other words, "judgment" and "decision" can include matters that are considered to be "judged" and "decided". In addition, "judgment (decision)" can also be rephrased by "assuming", "expecting", "considering", etc.

[0602] Terms such as "connected", "coupled" or all variations thereof refer to all direct or indirect connections or combinations between two or more elements, and may include situations where there are one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The combination or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may also be rewritten by "accessed". In the context of the present disclosure, two elements may be considered to be "connected" or "coupled" to each other by using at least one of one or more wires, cables, and printed electrical connections, and as several non-limiting and non-inclusive examples, they may be "connected" or "coupled" to each other by using electromagnetic energy having wavelengths in the wireless frequency domain, microwave region, and optical (both visible and invisible) region, etc.

[0603] The reference signal may be referred to as RS (Reference Signal) for short, or may be referred to as a pilot according to an applied standard.

[0604] The phrase “based on” used in the present disclosure does not mean “only based on” unless explicitly stated otherwise. In other words, the phrase “based on” means both “only based on” and “at least based on”.

[0605] Any reference to an element using the designations "first," "second," etc., used in this disclosure does not necessarily limit the number or order of these elements. These designations can be used in this disclosure as a convenient method of distinguishing between two or more elements. Therefore, reference to a first and a second element does not mean that only two elements can be used or that the first element must precede the second element in any form.

[0606] The “unit” in the configuration of each of the above-mentioned devices may be replaced with a “section”, “circuit”, “device” or the like.

[0607] In the present disclosure, when the terms "include", "including" and their variations are used, these terms, like the term "comprising", have an inclusive meaning. Furthermore, the term "or" used in the present disclosure does not mean an exclusive OR.

[0608] A radio frame may also be composed of one or more frames in the time domain. One or more frames in the time domain may also be referred to as subframes. A subframe may also be further composed of one or more time slots in the time domain. A subframe may also be a fixed time length (e.g., 1 ms) that is independent of a parameter set (numerology).

[0609] A parameter set may also be a communication parameter applied in at least one of the transmission and reception of a certain signal or channel. For example, a parameter set may also represent at least one of a subcarrier spacing (SCS), a bandwidth, a symbol length, a cyclic prefix length, a transmission time interval (TTI), the number of symbols per TTI, a radio frame structure, a specific filtering process performed by a transmitter and receiver in the frequency domain, a specific windowing process performed by a transmitter and receiver in the time domain, and the like.

[0610] A time slot may also be composed of one or more symbols (OFDM (Orthogonal Frequency Division Multiplexing)) symbols, SC-FDMA (Single Carrier Frequency Division Multiple Access)) symbols, etc.) in the time domain. A time slot may also be a time unit based on a parameter set.

[0611] A time slot may also include multiple mini-slots. Each mini-slot may also be composed of one or more symbols in the time domain. In addition, a mini-slot may also be referred to as a sub-slot. A mini-slot may also be composed of fewer symbols than a time slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a mini-slot may also be referred to as a PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a mini-slot may also be referred to as a PDSCH (or PUSCH) mapping type B.

[0612] Radio frames, subframes, time slots, mini-time slots, and symbols all represent time units for transmitting signals. Radio frames, subframes, time slots, mini-time slots, and symbols may also use other names corresponding to each other.

[0613] For example, a subframe can be called a transmission time interval (TTI), multiple consecutive subframes can be called TTI, and a time slot or a mini time slot can also be called TTI. In other words, at least one of the subframe and TTI can be a subframe (1ms) in the existing LTE, a period shorter than 1ms (for example, 1-13 code elements), or a period longer than 1ms. In addition, the unit representing TTI can also be called a time slot, a mini time slot, etc. instead of a subframe.

[0614] Here, TTI refers to, for example, the minimum time unit for scheduling in wireless communication. For example, in the LTE system, the base station schedules each user terminal to allocate wireless resources (frequency bandwidth, transmission power, etc. that can be used in each user terminal) in units of TTI. In addition, the definition of TTI is not limited to this.

[0615] TTI can be a unit of time for sending channel-coded data packets (transport blocks), code blocks, code words, etc., and can also be a processing unit for scheduling, link adaptation, etc. In addition, when TTI is given, the time interval (e.g., the number of symbols) to which the transport block, code block, code word, etc. is actually mapped can also be shorter than the TTI.

[0616] In addition, when a time slot or a mini time slot is called TTI, more than one TTI (i.e., more than one time slot or more than one mini time slot) can also be the minimum time unit of scheduling. In addition, the number of time slots (number of mini time slots) constituting the minimum time unit of scheduling can also be controlled.

[0617] A TTI having a time length of 1 ms may also be referred to as a normal TTI (TTI in LTE Rel.8-12), a standard TTI, a long TTI, a normal subframe, a standard subframe, a long subframe, a time slot, etc. A TTI shorter than a normal TTI may also be referred to as a shortened TTI, a short TTI, a partial TTI (partial or fractional TTI), a shortened subframe, a short subframe, a mini time slot, a sub time slot, a time slot, etc.

[0618] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) can be rewritten by a TTI having a time length exceeding 1 ms, and a short TTI (e.g., a shortened TTI, etc.) can be rewritten by a TTI having a TTI length shorter than the long TTI and longer than 1 ms.

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

[0620] In addition, the time domain of an RB may include one or more symbols, or may be the length of a slot, a mini-slot, a subframe, or a TTI. A TTI, a subframe, etc. may also be composed of one or more resource blocks, respectively.

[0621] In addition, one or more RBs may also be referred to as a physical resource block (PRB: Physical RB), a sub-carrier group (SCG: Sub-Carrier Group), a resource element group (REG: Resource Element Group), a PRB pair, an RB pair, etc.

[0622] In addition, 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.

[0623] A bandwidth part (BWP) (also referred to as a partial bandwidth, etc.) may also represent a subset of contiguous common RBs (common resource blocks) for a parameter set in a certain carrier. Here, the common RBs may also be identified by the index of the RBs based on the common reference point of the carrier. PRBs may also be defined in a certain BWP and numbered within the BWP.

[0624] 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 in one carrier.

[0625] At least one of the set BWPs may be activated, and the UE may not assume that a specific signal / channel is transmitted or received outside the activated BWP. In addition, "cell", "carrier" and the like in the present disclosure may be replaced by "BWP".

[0626] The above structures of radio frames, subframes, time slots, mini-time slots, and symbols are merely examples. For example, the number of subframes included in a radio frame, the number of time slots in each subframe or radio frame, the number of mini-time slots included in a time slot, the number of symbols and RBs included in a time slot or mini-time slot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, and the cyclic prefix (CP) length can be changed in various ways.

[0627] The “maximum transmit power” recorded in the present disclosure may refer to the maximum value of the transmit power, the nominal maximum transmit power (the nominal UE maximum transmit power), or the rated maximum transmit power (the rated UE maximum transmit power).

[0628] In the present disclosure, when an article is added by translation like a, an, and the in English, for example, the present disclosure may also include a case where the noun following the article is in a plural form.

[0629] In the present disclosure, the term "A is different from B" may also mean "A and B are different from each other". In addition, the term may also mean "A and B are different from C, respectively". The terms "separate" and "combined" may also be interpreted as the same as "different".

[0630] Description of Reference Numerals

[0631] 10 Wireless Communication Systems

[0632] 100 base stations (gNB)

[0633] 200 Terminal (UE)

Claims

1. A terminal having: A receiving unit receives a PDCCH monitoring setting for a cross-division duplex (XDD) operation; and The control unit controls PDCCH monitoring according to the PDCCH monitoring configuration.

2. The terminal according to claim 1, wherein: The PDCCH monitoring configuration includes a first PDCCH monitoring configuration for a non-XDD time unit and a second PDCCH monitoring configuration for an XDD time unit.

3. The terminal according to claim 2, wherein: The first PDCCH monitoring configuration includes at least one of a search space set configuration, a control resource set CORESET configuration, a frequency domain resource configuration, and a frequency monitoring position configuration for the non-XDD time unit. The second PDCCH monitoring configuration includes one or more search space set configurations, one or more CORE SET configurations, one or more frequency domain resource configurations, and one or more frequency monitoring position configurations for the XDD time unit.

4. The terminal according to claim 1, wherein: The PDCCH monitoring configuration includes a PDCCH search space configuration. The control unit controls the PDCCH monitoring according to whether a PDCCH monitoring opportunity indicated by the PDCCH search space configuration overlaps with an XDD time unit.

5. A base station, comprising: A setting unit, which sets a PDCCH monitoring setting for a cross-split duplex (XDD) operation; and The sending unit sends the PDCCH monitoring setting.

6. A wireless communication method, which is a wireless communication method performed by a terminal, comprising: Receiving a PDCCH monitoring setting for cross-split duplex (XDD) operation; as well as PDCCH monitoring is controlled according to the PDCCH monitoring configuration.