Terminal, wireless communication method, base station and system

Abstract

A terminal according to an embodiment of this disclosure includes: a receiver that receives information regarding at least one of a control resource set (CORESET) pool index associated with a CORESET, two transmission configuration indication (TCI) states associated with the CORESET, and two linked search space sets; and a controller that when multiple quasi co-location (QCL) type D reference signals used, respectively, for the reception of multiple downlink signals collide with each other, controls, on the basis of the information, the reception of one or more of the multiple downlink signals that use one or more of the QCL type D reference signals. An embodiment of this disclosure makes it possible to properly perform reception on the basis of a PDCCH / CORESET setting.

Description

[Technical Field]

[0001] The present disclosure relates to a terminal and a wireless communication method in a next-generation mobile communication system. 、 base station and systems Regarding. [Background technology]

[0002] In Universal Mobile Telecommunications System (UMTS) networks, Long Term Evolution (LTE) was specified with the aim of achieving higher data rates and lower latency (Non-Patent Document 1). Also, LTE-Advanced (3GPP Rel. 10-14) was specified with the aim of achieving higher capacity and more advanced features than LTE (Third Generation Partnership Project (3GPP) Release (Rel.) 8, 9).

[0003] Successor systems to LTE (e.g., 5th generation mobile communication system (5G), 5G+ (plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel. 15 or later) are also being considered. [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] 3GPP TS 36.300 V8.12.0 “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)”, April 2010 Summary of the Invention [Problem to be solved by the invention]

[0005] In future wireless communication systems, it is being considered that a terminal will receive a physical downlink control channel (PDCCH) based on the configuration of the PDCCH and a control resource set (CORESET). In future wireless communication systems, cases such as one or two transmission / reception points (TRPs), one or two transmission configuration indication (TCI) states, and PDCCH repetition are also being considered. For at least one of these cases, it is unclear how a UE will perform reception based on the PDCCH / CORESET configuration. If reception is not performed appropriately, this may result in degradation of communication quality, degradation of communication throughput, and the like.

[0006] Therefore, the present disclosure provides a terminal and a wireless communication method that perform appropriate reception based on the PDCCH / CORESET setting. 、 base station and systems One of the aims is to provide [Means for solving the problem]

[0007] A terminal according to one aspect of the present disclosure includes a receiver that receives information about two linked search space (SS) sets; and a controller that controls monitoring of a physical downlink control channel (PDCCH) in a first control resource set (CORESET) corresponding to a first SS set having a lowest index among a plurality of SS sets in a plurality of overlapping monitoring occasions, one or more CORESETs having the same first quasi-co-location (QCL) parameter as the first CORESET, and a second CORESET corresponding to a second SS set linked by the information to the first CORESET and an SS set corresponding to one of the one or more CORESETs. The first SS set and the second SS set linked by the information correspond to the first CORESET and the second CORESET, respectively, and the second CORESET has second QCL parameters different from the first QCL parameters. . [Effects of the Invention]

[0008] According to one aspect of the present disclosure, appropriate reception can be performed based on the PDCCH / CORESET settings. [Brief explanation of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram illustrating an example of the number of RLM-RSs. [Figure 2] 2A and 2B are diagrams showing an example of embodiment 1-1. [Figure 3] 3A and 3B are diagrams showing an example of embodiment 1-2. [Figure 4] 4A and 4B are diagrams showing an example of embodiment 1-3. [Figure 5] FIG. 5 is a diagram showing an example of aspect 1-4. [Figure 6] FIG. 6 is a diagram showing an example of option 1 of aspect 2-1. [Figure 7] FIG. 7 is a diagram showing an example of option 2 of aspect 2-1. [Figure 8] FIG. 8 is a diagram showing an example of aspect 3-1. [Figure 9] FIG. 9 is a diagram showing an example of aspect 3-2. [Figure 10] FIG. 10 is a diagram illustrating an example of an mDCI-based MTRP environment for explaining the operation of embodiment X1.1. [Figure 11] 11A and 11B are diagrams illustrating an example of a priority rule when a PDCCH and a PDSCH collide according to embodiment X1.1. [Figure 12] FIG. 12 is a diagram illustrating an example of an sDCI-based MTRP environment for explaining the operation of embodiment X1.2. [Figure 13] 13A and 13B are diagrams illustrating an example of a priority rule when a PDCCH and a PDSCH collide according to embodiment X1.2. [Figure 14]FIG. 14 is a diagram illustrating an example of a priority rule when an A-CSI-RS and another DL signal (PDSCH) collide according to embodiment X5.2. [Figure 15] FIG. 15 is a diagram showing an example of a priority CORESET and other CORESETs to be monitored simultaneously in embodiment Y1.1.1. [Figure 16] FIG. 16 is a diagram showing an example of a prioritized CORESET in embodiment Y1.1.2.1. [Figure 17] FIG. 17 is a diagram showing an example of a prioritized CORESET in embodiment Y1.1.2.1. [Figure 18] FIG. 18 is a diagram showing an example of a prioritized CORESET in embodiment Y1.1.2.1. [Figure 19] FIG. 19 is a diagram showing an example of a prioritized CORESET in embodiment Y1.1.2.2. [Figure 20] FIG. 20 is a diagram showing an example of a priority CORESET and other CORESETs to be monitored simultaneously in embodiment Y1.1.2. [Figure 21] FIG. 21 is a diagram showing an example of a priority CORESET and other CORESETs to be monitored simultaneously in embodiment Y1.1.2. [Figure 22] FIG. 22 is a diagram showing an example of a priority CORESET and other CORESETs to be monitored simultaneously in embodiment Y1.2. [Figure 23] FIG. 23 is a diagram showing an example of a priority CORESET and other CORESETs to be monitored simultaneously in embodiment Y2.1.1. [Figure 24] FIG. 24 is a diagram showing an example of a prioritized CORESET in embodiment Y2.1.2.1. [Figure 25] FIG. 25 is a diagram showing an example of a prioritized CORESET in embodiment Y2.1.2.2. [Figure 26] FIG. 26 is a diagram showing an example of a prioritized CORESET and other CORESETs to be monitored simultaneously in embodiment Y2.1.2. [Figure 27]FIG. 27 is a diagram showing an example of a priority CORESET and other CORESETs to be monitored simultaneously in embodiment Y2.2. [Figure 28] FIG. 28 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. [Figure 29] FIG. 29 is a diagram illustrating an example of the configuration of a base station according to an embodiment. [Figure 30] FIG. 30 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment. [Figure 31] FIG. 31 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0010] (TCI, spatial relations, QCL) In NR, it is being considered to control the reception processing (e.g., at least one of reception, demapping, demodulation, and decoding) and transmission processing (e.g., at least one of transmission, mapping, precoding, modulation, and encoding) in the UE of at least one of a signal and a channel (referred to as signal / channel) based on the transmission configuration indication state (TCI state).

[0011] The TCI state may represent that which is applied to a downlink signal / channel, and the equivalent of the TCI state which is applied to an uplink signal / channel may be expressed as a spatial relation.

[0012] The TCI state is information about the quasi-co-location (QCL) of signals / channels, and may also be called spatial reception parameters, spatial relation information, etc. The TCI state may be configured in the UE for each channel or signal.

[0013] A QCL is an index that indicates the statistical properties of a signal / channel. For example, if a signal / channel has a QCL relationship with another signal / channel, it may mean that it can be assumed that at least one of the Doppler shift, Doppler spread, average delay, delay spread, and spatial parameter (e.g., spatial Rx parameter) is the same between these different signals / channels (i.e., they are QCLs with respect to at least one of these).

[0014] The spatial reception parameters may correspond to a reception beam (e.g., a reception analog beam) of the UE, and the beam may be determined based on a spatial QCL. A QCL (or at least one element of a QCL) in the present disclosure may be replaced with an sQCL (spatial QCL).

[0015] A plurality of types (QCL types) of QCLs may be defined. For example, four QCL types A and B may be provided, each having different parameters (or parameter sets) that can be assumed to be the same. The parameters (which may also be referred to as QCL parameters) are listed below: QCL Type A (QCL-A): Doppler shift, Doppler spread, mean delay and delay spread, QCL Type B (QCL-B): Doppler shift and Doppler spread, QCL Type C (QCL-C): Doppler shift and mean delay, · QCL Type D (QCL-D): Spatial reception parameters.

[0016] The assumption by a UE that a Control Resource Set (CORESET), channel, or reference signal has a specific QCL (e.g., QCL type D) relationship with another CORESET, channel, or reference signal may be referred to as a QCL assumption.

[0017] The UE may determine at least one of a transmit beam (Tx beam) and a receive beam (Rx beam) for a signal / channel based on the TCI condition or QCL assumption of the signal / channel.

[0018] The TCI state may be, for example, information about the QCL between the target channel (in other words, the Reference Signal (RS) for the channel) and another signal (e.g., another RS). The TCI state may be set (indicated) by higher layer signaling, physical layer signaling, or a combination thereof.

[0019] The channel / signal to which the TCI state is applied may be called a target channel / reference signal (target channel / RS), or simply a target, and the other signal may be called a reference reference signal (reference RS), source RS, or simply a reference.

[0020] The channel for which the TCI state or spatial relationship is set (specified) may be, for example, at least one of a downlink shared channel (Physical Downlink Shared Channel (PDSCH)), a downlink control channel (Physical Downlink Control Channel (PDCCH)), an uplink shared channel (Physical Uplink Shared Channel (PUSCH)), and an uplink control channel (Physical Uplink Control Channel (PUCCH)).

[0021] Furthermore, the RS that has a QCL relationship with the channel may be at least one of, for example, a Synchronization Signal Block (SSB), a Channel State Information Reference Signal (CSI-RS), a Sounding Reference Signal (SRS), a CSI-RS for tracking (also called a Tracking Reference Signal (TRS)), a QCL detection reference signal (also called a QRS), and a Demodulation Reference Signal (DMRS).

[0022] An SSB is a signal block that includes at least one of a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), and a Physical Broadcast Channel (PBCH). An SSB may also be referred to as an SS / PBCH block.

[0023] An RS of QCL type X in a TCI state may refer to an RS that has a relationship of QCL type X with (the DMRS of) a certain channel / signal, and this RS may be called a QCL source of QCL type X in the TCI state.

[0024] (multiple channels / signal collisions) In the previous Rel.15 / 16 NR specifications, a UE could only receive, detect, or monitor channels / signals of the same QCL type D at the same time, but could not receive, detect, or monitor multiple channels / signals of different QCL types D at the same time. For this reason, the Rel.15 / 16 NR specifications specify the following constraints (which may also be called priority rules, QCL application rules, etc.) to ensure that multiple channels / signals fall under the same QCL type D when they collide (in other words, are transmitted / received at overlapping times) or to avoid such cases.

[0025] In the present disclosure, the collision of multiple channels / signals may mean that multiple channels / signals of different QCL types D are scheduled (or configured) to be received (or transmitted) in the same time resource (period) (QCL type D collision).

[0026] Furthermore, in this disclosure, a difference between (the reference RS of) a QCL type D of one channel / signal and (the reference RS of) a QCL type D of another channel / signal may mean that the beam used for communication of the one channel / signal is different from the beam used for communication of the other channel / signal. In this disclosure, a difference between (the reference RS of) a QCL type D of one channel / signal and (the reference RS of) a QCL type D of another channel / signal may be expressed as the QCL types D of the one channel / signal and the other channel / signal being different, their QCL type D characteristics being different, "QCL types D" being different, etc.

[0027] <PDCCH vs. PDCCH> When a UE is configured for single-cell operation or for carrier aggregation operation in the same frequency band, and monitors PDCCH candidates in multiple CORESETs with the same or different QCL type D characteristics in the active DL BWP of one or more cells at overlapping monitoring occasions, it monitors PDCCHs only in a certain CORESET among the multiple CORESETs and in a CORESET that has the same QCL type D characteristics as the certain CORESET.

[0028] This "certain CORESET" corresponds to the lowest-indexed Common Search Space (CSS) set in the lowest-indexed cell that contains the CSS set, if any, or the lowest-indexed UE-specific Search Space (USS) set in the lowest-indexed cell, if any. The lowest USS set index is determined across all USS sets that have at least one PDCCH candidate in overlapping PDCCH monitoring occasions.

[0029] In simple terms, when monitoring PDCCH candidates at overlapping monitoring opportunities, the UE determines the CORESET to monitor according to the priority rule that CSS sets are monitored with priority over USS sets, and among SS sets of the same type (CSS or USS), the one with the smaller index (i.e., the smaller cell index; if the cell index is the same, the one with the smaller SS set index) is monitored with priority.

[0030] The SS set index may correspond to a value set by the RRC parameter SearchSpaceId for identifying a search space. In the present disclosure, the CSS set index may refer to the SS set index for an SS set whose search space type (RRC parameter "searchSpaceType") indicates CSS. In the present disclosure, the USS set index may refer to the SS set index for an SS set whose search space type (RRC parameter "searchSpaceType") indicates USS.

[0031] <PDCCH vs. PDSCH> If the offset (which may be referred to as the scheduling offset) between the reception of the DL DCI and the corresponding PDSCH is smaller than a certain threshold (timeDurationForQCL), the UE may assume that the DMRS port of the PDSCH of a serving cell is a reference signal and QCL for the QCL parameters for the PDCCH of the CORESET with the smallest CORESET ID (controlResourceSetId) associated with the search space monitored in the most recent slot in which one or more CORESETs in the active BWP of the serving cell are monitored. In this case, the PDSCH may be expressed as following the default TCI state, referring to / assuming the default QCL, etc.

[0032] When a PDSCH follows the default TCI state, if the "QCL type D (signal)" of the DMRS of the PDSCH differs from the "QCL type D (signal)" of the DMRS of a PDCCH that overlaps with the PDSCH by at least one symbol ('QCL-TypeD'), the UE may assume (expect) that it will prioritize reception of the PDCCH associated with the CORESET (priority rule between PDCCH and PDSCH). Note that these operations may also be applied in the case of intra-band carrier aggregation (CA) (when the PDSCH and the CORESET are on different component carriers).

[0033] For example, if the PDCCH and the PDSCH have different QCL types D and some symbols overlap, the UE may receive the PDCCH with priority and may not receive (e.g., may drop) the PDSCH that overlaps with the PDCCH. The UE may also receive the PDSCH that does not overlap with the PDCCH.

[0034] <CSI-RS vs. PDCCH> For CSI-RS resources associated with a Non Zero Power (NZP)-CSI-RS resource set where the higher layer parameter for repetition ('repetition') is 'on', the UE does not assume that CSI-RS is configured for symbols configured to monitor CORESET (i.e., CORESET and CSI-RS resources in this case do not overlap in time).

[0035] On the other hand, for an NZP-CSI-RS resource set where 'repetition' is not 'on', if the UE configures the CSI-RS resource and the search space set associated with the CORESET in the same OFDM symbol, the UE may assume that the CSI-RS and the DMRS of the PDCCH transmitted in all search space sets associated with the CORESET have the QCL of "QCL Type D" (if "QCL Type D" is applicable). In other words, for a CSI-RS where repetition is not on, the UE may assume the same QCL as the overlapping PDCCH (CORESET). Note that these operations may also be applied in the case of intra-band CA (when the CSI-RS and the CORESET are on different component carriers).

[0036] In the present disclosure, the OFDM symbol may be read interchangeably with the symbol.

[0037] <CSI-RS vs. SSB> For a CSI-RS resource associated with an NZP-CSI-RS resource set for which a higher layer parameter related to repetition (‘repetition’) is set, a UE that is configured to receive the CSI-RS in the same OFDM symbol as the SS / PBCH block may assume that the CSI-RS and the SS / PBCH block are QCL with QCL type D (when QCL type D is applicable). In other words, for a CSI-RS for which a higher layer parameter related to repetition is set, the UE may assume the same QCL as the overlapping SS / PBCH block.

[0038] <PDSCH vs. SSB> When a UE receives an SS / PBCH block and DMRS for PDSCH in the same OFDM symbol, the UE may assume that the DMRS and the SS / PBCH block are QCL with QCL type D (when QCL type D is applicable). In other words, for PDSCH, the UE may assume the same QCL as the overlapping SS / PBCH block.

[0039] <A-CSI-RS vs. Other DL Signals> In the Rel.16 NR specification, when the scheduling offset of an aperiodic CSI-RS (A-CSI-RS) is greater than or equal to a threshold determined based on the beam switch timing reported by the UE, the UE may assume (expect) to apply the QCL assumptions in the indicated TCI states for the aperiodic CSI-RS resources in the CSI triggering state indicated by the CSI trigger field in DCI (the UE is expected to apply the QCL assumptions in the indicated TCI states for the aperiodic CSI-RS resources in the CSI triggering state indicated by the CSI trigger field in DCI). That is, in this case, the UE may receive the A-CSI-RS based on the TCI state specified by DCI.

[0040] Here, the scheduling offset may refer to the offset between the last symbol of a PDCCH (or the last slot including the PDCCH) that carries DCI that triggers the resource set for A-CSI-RS and the first symbol (or slot) of the A-CSI-RS resource in the resource set. The offset may be measured in units of symbols or slots. Information about the scheduling offset for A-CSI-RS may correspond to the RRC parameter "aperiodicTriggeringOffset."

[0041] In addition, the beam switching timing (UE capability related to) reported by the UE may also be referred to as A-CSI-RS beam switching timing, simply beam switching timing, beam switch timing (RRC parameter "beamSwitchTiming"), etc.

[0042] The beam switch timing may take different values for each subcarrier interval (e.g., 60 kHz, 120 kHz), and may take values such as 14, 28, 48, 224, and 336 symbols.

[0043] The threshold determined based on the beam switch timing may be the value of the beam switch timing to be reported, a specific beam switch timing value (e.g., 48), or a value obtained by adding a predetermined offset (e.g., an offset taking into account the subcarrier spacing) to these.

[0044] If the scheduling offset of the A-CSI-RS is less than a threshold determined based on the beam switch timing reported by the UE, and there is another DL signal with the indicated TCI state in the same symbol as the A-CSI-RS, the UE may apply the QCL assumptions of the other DL signal when receiving the A-CSI-RS. This specification is intended to prevent a situation where the UE cannot switch its receive beam in time to receive the A-CSI-RS, since it takes a certain amount of time from demodulating the triggering DCI to switching the receive beam corresponding to the TCI state indicated by the DCI.

[0045] Note that the other DL signal here may be at least one of a PDSCH having a scheduling offset greater than or equal to a predetermined threshold (UE capability information "timeDurationForQCL") (i.e., the offset from reception of DCI to the start of reception of PDSCH scheduled by the DCI is greater than or equal to the predetermined threshold), an A-CSI-RS (i.e., another A-CSI-RS) having a scheduling offset greater than or equal to a threshold determined based on the beam switch timing reported by the UE, a P-CSI-RS, or an SP-CSI-RS.

[0046] The timeDurationForQCL may be defined as the minimum time (for example, the number of OFDM symbols) during which the UE receives a PDCCH and applies the spatial QCL information of the PDCCH (DCI) to PDSCH processing.

[0047] The timeDurationForQCL may also be referred to as the time duration for QCL, "Threshold," "Threshold for offset between a DCI indicating a TCI state and a PDSCH scheduled by the DCI," "Threshold-Sched-Offset," schedule offset threshold, scheduling offset threshold, etc. The timeDurationForQCL may take values such as 7, 14, or 28 symbols.

[0048] In the present disclosure, the threshold value for the other DL signal may correspond to the beam switch timing if the other DL signal is A-CSI-RS, and may correspond to the value of timeDurationForQCL reported by the UE if the other DL signal is PDSCH.

[0049] Note that the application of the above-mentioned QCL assumptions for other DL signals to the A-CSI-RS may be limited to cases where the NZP CSI-RS resource set that specifies the A-CSI-RS resource does not have the upper layer parameters "trs-Info" and "repetition".

[0050] For an NZP CSI-RS resource set where trs-Info is set to true, all NZP CSI-RS resources in the resource set may use the same antenna port. For an NZP CSI-RS resource set where Repetition is set to off, the UE may not assume that the NZP CSI-RS resources in the resource set are transmitted using the same downlink spatial domain transmit filter.

[0051] In addition, if the scheduling offset of the A-CSI-RS is less than a threshold determined based on the beam switch timing reported by the UE, there are no other DL signals with the indicated TCI state in the same symbol as the A-CSI-RS, and at least one CORESET is configured in the BWP receiving the A-CSI-RS, the UE may, upon receiving the A-CSI-RS, apply the QCL assumption used for the CORESET associated with a monitored search space with the lowest controlResourceSetId in the latest slot in which one or more CORESETs within the active BWP of the serving cell are monitored.

[0052] In addition, if the scheduling offset of the A-CSI-RS is less than the beam switch timing reported by the UE, there is no other DL signal with the indicated TCI state in the same symbol as the A-CSI-RS, and CORESET is not set in the BWP receiving the A-CSI-RS and a specific higher layer parameter (e.g., an RRC parameter for enabling the default beam (which may be called enableDefaultBeamForCCS, etc.)) is set, the UE may, upon receiving the A-CSI-RS, apply the QCL assumption of the TCI state corresponding to the smallest activated TDI state ID applicable to the PDSCH of the active BWP receiving the A-CSI-RS.

[0053] (Multi-TRP) In NR, one or more Transmission / Reception Points (TRPs) (multi-TRPs (MTRPs)) are considered to perform DL transmission to a UE using one or more panels (multi-panels). Also, it is considered that a UE performs UL transmission to one or more TRPs using one or more panels.

[0054] Note that multiple TRPs may correspond to the same cell identifier (ID), or different cell IDs. The cell ID may be a physical cell ID or a virtual cell ID.

[0055] Multi-TRPs (e.g., TRPs #1 and #2) may be connected by ideal / non-ideal backhauls to exchange information, data, etc. Each TRP of the multi-TRP may transmit a different code word (CW) and a different layer. Non-Coherent Joint Transmission (NCJT) may be used as a form of multi-TRP transmission.

[0056] In the NCJT, for example, TRP#1 performs modulation mapping and layer mapping on a first codeword to transmit a first PDSCH using a first number of layers (e.g., two layers) with a first precoding, and TRP#2 performs modulation mapping and layer mapping on a second codeword to transmit a second number of layers (e.g., two layers) with a second precoding.

[0057] Note that multiple PDSCHs (multi-PDSCHs) that are non-coherent may be defined as partially or completely overlapping in at least one of the time and frequency domains, i.e., a first PDSCH from a first TRP and a second PDSCH from a second TRP may overlap in at least one of the time and frequency resources.

[0058] The first PDSCH and the second PDSCH may be assumed to be not quasi-co-located (Quasi-Co-Location (QCL)). Reception of multiple PDSCHs may be interpreted as simultaneous reception of PDSCHs that are not of a certain QCL type (e.g., QCL type D).

[0059] Multiple PDSCHs from multiple TRPs (which may also be referred to as multiple PDSCHs) may be scheduled using one DCI (single DCI, single PDCCH) (single-master mode, single-DCI based multi-TRP). Multiple PDSCHs from multiple TRPs may also be scheduled using multiple DCIs (multiple DCI, multiple PDCCHs) (multi-master mode, multi-DCI based multi-TRP).

[0060] In URLLC for multiple TRPs, it is considered that PDSCH (transport block (TB) or codeword (CW)) repetition across multiple TRPs is supported. Repetition schemes (URLLC schemes, e.g., schemes 1, 2a, 2b, 3, and 4) across multiple TRPs in the frequency domain, layer (spatial) domain, or time domain are supported. In scheme 1, multiple PDSCHs from multiple TRPs are space division multiplexed (SDM). In schemes 2a and 2b, PDSCHs from multiple TRPs are frequency division multiplexed (FDM). In scheme 2a, the redundancy version (RV) is the same for multiple TRPs. In scheme 2b, the RVs may be the same or different for multiple TRPs. In schemes 3 and 4, multiple PDSCHs from multiple TRPs are time division multiplexed (TDM). In scheme 3, multiple PDSCHs from multiple TRPs are transmitted in one slot. In scheme 4, multiple PDSCHs from multiple TRPs are transmitted in different slots.

[0061] Such a multi-TRP scenario allows for more flexible transmission control using good quality channels.

[0062] To support intra-cell (having the same cell ID) and inter-cell (having different cell IDs) multi-TRP transmission based on multiple PDCCHs, in the RRC configuration information for linking multiple pairs of PDCCHs and PDSCHs with multiple TRPs, one control resource set (CORESET) in the PDCCH configuration information (PDCCH-Config) may correspond to one TRP.

[0063] If at least one of the following conditions 1 and 2 is satisfied, the UE may determine that the transmission is a multi-TRP transmission based on the multi-DCI transmission. In this case, the TRP may be replaced with a CORESET pool index. [Condition 1] A CORESET pool index of 1 is set. [Condition 2] Two different values of the CORESET pool index (for example, 0 and 1) are set.

[0064] If the following condition is met, the UE may determine that the state is multi-TRP based on a single DCI, in which case the two TRPs may be interpreted as two TCI states indicated by the MAC CE / DCI. [conditions] "Enhanced TCI States Activation / Deactivation for UE-specific PDSCH MAC CE" is used to indicate one or two TCI states for one codepoint of the TCI field in the DCI.

[0065] The DCI for common beam instruction may be a UE-specific DCI format (e.g., DL DCI format (e.g., 1_1, 1_2), UL DCI format (e.g., 0_1, 0_2)), or may be a UE-group common DCI format.

[0066] (Multi-TRP PDCCH) For the reliability of multi-TRP PDCCH based on non-single frequency network (SFN), the following considerations 1 to 3 are considered. [Consideration 1] Coding / rate matching is based on one repetition, and the same coded bits are repeated in other repetitions. [Consideration 2] Each repetition has the same number of control channel elements (CCEs), the same coded bits, and corresponds to the same DCI payload. Consideration 3: Two or more PDCCH candidates are explicitly linked to each other. The UE knows the link before decoding.

[0067] The following options for PDCCH repetition are considered: 1-2, 1-3, 2, 3.

[0068] [Options 1-2] Two sets of PDCCH candidates (within a given search space (SS) set) are associated with two TCI states of CORESET, respectively, where the same CORESET, the same SS set, and PDCCH repetitions in different monitoring occasions are used.

[0069] [Options 1-3] Two sets of PDCCH candidates are associated with two SS sets, respectively. Both SS sets are associated with a CORESET, and each SS set is associated with only one TCI state of that CORESET. Here, the same CORESET and two SS sets are used.

[0070] [Option 2] One SS set is associated with two different CORESETs.

[0071] [Option 3] Two SS sets are associated with two CORESETs respectively.

[0072] In contrast to non-SFN methods, Study 2 and Option 3, support for Study 3 is being considered.

[0073] To enhance the multi-TRP PDCCH reliability, the following multiplexing schemes are being considered: [FDM] Two sets of REG bundles, CCEs of the transmitted PDCCH, two non-overlapping (in frequency) transmitted PDCCH repetitions, and non-overlapping (in frequency) multi-chance transmitted PDCCHs are associated with different TCI states. [SFN] The PDCCH DMRS is associated with two TCI states in all REGs / CCEs of the PDCCH.

[0074] It is considered that the two linked SS sets for the PDCCH repetition are configured by the RRC IE / MAC CE, and the two linked PDCCH candidates for the PDCCH repetition are two PDCCH candidates having the same aggregation level and the same candidate index within the two linked SS sets.

[0075] (Radio Link Monitoring (RLM)) In NR, Radio Link Monitoring (RLM) is used.

[0076] In NR, a base station may configure a Radio Link Monitoring Reference Signal (Radio Link Monitoring RS (RLM-RS)) for a UE for each BWP using higher layer signaling. The UE may receive configuration information for RLM (e.g., the "RadioLinkMonitoringConfig" information element of RRC).

[0077] The configuration information for the RLM may include fault detection resource configuration information (e.g., the upper layer parameter "failureDetectionResourcesToAddModList") and parameters related to the RLM-RS (e.g., the upper layer parameter "RadioLinkMonitoringRS").

[0078] The parameters related to the RLM-RS may include information indicating that it corresponds to the purpose of RLM, an index corresponding to the resource of the RLM-RS (e.g., an index included in the upper layer parameter "failureDetectionResources" (RadioLinkMonitoringRS in failureDetectionResourcesToAddModList)), etc. The index may be, for example, an index of the CSI-RS resource configuration (e.g., a non-zero power CSI-RS resource ID) or an SS / PBCH block index (SSB index). The purpose information may indicate a beam failure, a (cell-level) Radio Link Failure (RLF), or both.

[0079] The UE may identify the RLM-RS resource based on the index corresponding to the resource of the RLM-RS, and perform RLM using the RLM-RS resource.

[0080] In the Rel. 16 RLM procedure, the UE follows the following implicit RLM-RS determination (implicit RS determination) procedure.

[0081] [Implicit RLM-RS determination procedure] If the UE is not provided with a Radio Link Monitoring RS (RLM-RS) and the UE is provided with a TCI state including one or more CSI-RS for PDCCH reception, the UE shall follow steps 1 to 4 below.

[0082] Step 1 If the active TCI state for PDCCH reception includes only one RS, the UE uses the RS provided for the active TCI state for PDCCH reception for RLM. Step 2 If the active TCI state for PDCCH reception includes two RSs, the UE assumes that one RS has QCL type D, and the UE uses that RS with QCL type D for RLM. The UE does not assume that both RSs have QCL type D. Step 3 The UE is not required to use aperiodic or semi-persistent RS for RLM. Step 4 L max For =4, the UE selects N provided for the active TCI state for PDCCH reception in the multiple CORESETs associated with the multiple search space sets in order of the smallest monitoring periodicity. RLM If more than one CORESET is associated with multiple search space sets with the same monitoring period, the UE determines the order of the CORESETs from the highest CORESET index.

[0083] where L max is the maximum number of SS / PBCH block indexes in a cell. The maximum number of SS / PBCH blocks transmitted in a half-frame is L max is.

[0084] In this way, if the UE is not provided with an RLM-RS, the UE makes an implicit RLM-RS decision and uses the active TCI state for PDCCH reception for RLM. max If = 4, the UE first sorts the search space sets in ascending order of monitoring period, then in descending order of CORESET index, N RLM Select RS. Select CORESET.

[0085] The UE must be connected to the N LR-RLM Up to N RLM-RSs can be configured. LR-RLM From RLM-RS, L max Depends on N RLMUp to RLM-RSs are used for RLM. In Rel. 16, as shown in Figure 1, max N if =4 RLM = 2, and L max N when =8 RLM = 4, and L max = 64, N RLM =8.

[0086] (Beam Failure Detection(BFD) / Beam Failure Recovery(BFR)) In NR, communication is performed using beamforming. For example, a UE and a base station (e.g., a gNB (gNodeB)) may use a beam used to transmit a signal (also called a transmit beam or Tx beam) and a beam used to receive a signal (also called a receive beam or Rx beam).

[0087] When beamforming is used, it is expected that radio link quality will deteriorate due to increased susceptibility to interference from obstacles. This deterioration in radio link quality may lead to frequent radio link failures (RLF). Since RLF requires cell reconnection, frequent RLF occurrences will result in a degradation of system throughput.

[0088] In NR, in order to suppress the occurrence of RLF, when the quality of a specific beam deteriorates, a procedure for switching to another beam (which may also be called Beam Recovery (BR), Beam Failure Recovery (BFR), or L1 / L2 (Layer 1 / Layer 2) beam recovery) is performed. The BFR procedure may also be simply called BFR.

[0089] Note that a beam failure (BF) in this disclosure may also be referred to as a link failure.

[0090] For example, in an initial state, the UE performs measurements based on Reference Signal (RS) resources transmitted using two beams.

[0091] The RS may be at least one of a Synchronization Signal Block (SSB) and a Channel State Information RS (CSI-RS). The SSB may also be called an SS / PBCH (Physical Broadcast Channel) block.

[0092] The RS may be at least one of a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), a Mobility Reference Signal (MRS), a signal included in an SSB, an SSB, a CSI-RS, a Demodulation Reference Signal (DMRS), a beam-specific signal, etc., or a signal configured by extending or modifying any of these. The RS measured in step S101 may also be called an RS for beam failure detection (Beam Failure Detection RS (BFD-RS)), an RS for use in a beam recovery procedure (BFR-RS), etc.

[0093] If the radio waves from the base station are jammed, the UE cannot detect the BFD-RS (or the reception quality of the RS is degraded). Such jamming can occur, for example, due to obstacles, fading, interference, etc. between the UE and the base station.

[0094] The UE detects a beam failure when a predetermined condition is met. The UE may detect the occurrence of a beam failure, for example, when the Block Error Rate (BLER) is less than a threshold for all configured BFD-RS (BFD-RS resource configurations). When the occurrence of a beam failure is detected, the lower layer (physical (PHY) layer) of the UE may notify (indicate) a beam failure instance to the upper layer (MAC layer).

[0095] The criteria for the determination are not limited to BLER, but may be Layer 1 Reference Signal Received Power (L1-RSRP) in the physical layer. Also, instead of or in addition to RS measurement, beam failure detection may be performed based on a downlink control channel (PDCCH). The BFD-RS may be expected to be quasi-co-located (QCL) with the DMRS of the PDCCH monitored by the UE.

[0096] Here, QCL is an index that indicates the statistical properties of a channel. For example, if a signal / channel and another signal / channel have a QCL relationship, it may mean that it can be assumed that at least one of the Doppler shift, Doppler spread, average delay, delay spread, and spatial parameter (e.g., spatial Rx parameter) is the same between these different signals / channels (i.e., they are QCLs with respect to at least one of these).

[0097] The spatial reception parameters may correspond to a reception beam (e.g., a reception analog beam) of the UE, and the beam may be determined based on a spatial QCL. A QCL (or at least one element of a QCL) in the present disclosure may be replaced with an sQCL (spatial QCL).

[0098] Information about BFD-RS (e.g., RS index, resource, number, number of ports, precoding, etc.), information about beam fault detection (BFD) (e.g., the above-mentioned threshold), etc. may be configured (notified) to the UE using higher layer signaling, etc. Information about BFD-RS may also be referred to as information about BFR resources, etc.

[0099] When a higher layer (e.g., MAC layer) of the UE receives a beam failure instance notification from the PHY layer of the UE, it may start a predetermined timer (which may be called a beam failure detection timer). If the MAC layer of the UE receives a certain number of beam failure instance notifications (e.g., beamFailureInstanceMaxCount configured by RRC) before the timer expires, it may trigger a BFR (e.g., start one of the random access procedures described below).

[0100] The base station may determine that the UE has detected a beam failure when there is no notification from the UE or when a predetermined signal (beam recovery request) is received from the UE.

[0101] For beam recovery, the UE starts searching for a new candidate beam to be used for new communication. The UE may select a new candidate beam corresponding to a predetermined RS by measuring the RS. Here, the measured RS may be called a new candidate RS, a new candidate beam identification RS (NCBI-RS), a CBI-RS, a CB-RS (Candidate Beam RS), or the like. The NCBI-RS may be the same as or different from the BFD-RS. Note that the new candidate beam may simply be called a candidate beam or candidate RS.

[0102] The UE may determine a beam corresponding to an RS that satisfies a predetermined condition as a new candidate beam. The UE may determine a new candidate beam, for example, based on an RS whose L1-RSRP exceeds a threshold among the configured NCBI-RSs. Note that the criteria for determination are not limited to L1-RSRP. The L1-RSRP for SSB may be called SS-RSRP. The L1-RSRP for CSI-RS may be called CSI-RSRP.

[0103] Information about the NCBI-RS (e.g., RS resources, number of ports, precoding, etc.), information about the new candidate beam identification (NCBI) (e.g., the above-mentioned threshold), etc. may be configured (notified) to the UE using higher layer signaling, etc. Information about the new candidate RS (or NCBI-RS) may be acquired based on information about the BFD-RS. Information about the NCBI-RS may be referred to as information about NBCI resources, etc.

[0104] Note that BFD-RS, NCBI-RS, etc. may be read as Radio Link Monitoring RS (RLM-RS).

[0105] A UE that has identified a new candidate beam transmits a beam failure recovery request (BFRQ). The beam recovery request may also be referred to as a beam recovery request signal, a beam failure recovery request signal, or the like.

[0106] The BFRQ may be transmitted using, for example, at least one of an uplink control channel (Physical Uplink Control Channel (PUCCH)), a random access channel (Physical Random Access Channel (PRACH)), an uplink shared channel (Physical Uplink Shared Channel (PUSCH)), and a configured grant (CG) PUSCH.

[0107] The BFRQ may include information of the identified new candidate beam / new candidate RS. Resources for the BFRQ may be associated with the new candidate beam. The beam information may be signaled using a beam index (BI), a port index of a predetermined reference signal, an RS index, a resource index (e.g., a CSI-RS resource indicator (CRI) or an SSB resource indicator (SSBRI)), etc.

[0108] In Rel. 15 NR, contention-based BFR (CB-BFR), which is a BFR based on a contention-based random access (RA) procedure, and contention-free BFR (CF-BFR), which is a BFR based on a contention-free random access procedure, are under consideration. In CB-BFR and CF-BFR, a UE may transmit a preamble (also referred to as an RA preamble, a random access channel (Physical Random Access Channel (PRACH)), a RACH preamble, etc.) as a BFRQ using a PRACH resource.

[0109] In CB-BFR, a UE may transmit a preamble randomly selected from one or more preambles. In CF-BFR, a UE may transmit a preamble assigned specifically to the UE by the base station. In CB-BFR, a base station may assign the same preamble to multiple UEs. In CF-BFR, a base station may assign a preamble individually to each UE.

[0110] Note that CB-BFR and CF-BFR may be referred to as CB PRACH-based BFR (CBRA-BFR) and CF PRACH-based BFR (CFRA-BFR), respectively. CBRA-BFR may be referred to as CBRA for BFR. CFRA-BFR may be referred to as CFRA for BFR.

[0111] Regardless of whether CB-BFR or CF-BFR is used, information about the PRACH resource (RA preamble) may be notified by, for example, higher layer signaling (such as RRC signaling). For example, the information may include information indicating a correspondence relationship between the detected DL-RS (beam) and the PRACH resource, and a different PRACH resource may be associated with each DL-RS.

[0112] The base station that detects the BFRQ transmits a response signal (which may be referred to as a gNB response, etc.) to the BFRQ from the UE. The response signal may include reconfiguration information (e.g., DL-RS resource configuration information) for one or more beams.

[0113] The response signal may be transmitted, for example, in the UE common search space of the PDCCH. The response signal may be signaled using a PDCCH (DCI) scrambled with a cyclic redundancy check (CRC) by a UE identifier (e.g., a Cell-Radio RNTI (C-RNTI)). The UE may determine at least one of a transmit beam and a receive beam to use based on the beam reconfiguration information.

[0114] The UE may monitor the response signal based on at least one of a control resource set (CORESET) for BFR and a search space set for BFR.

[0115] For CB-BFR, contention resolution may be determined to be successful if the UE receives a PDCCH corresponding to the C-RNTI associated with the UE.

[0116] A period may be set for the UE to monitor a response to the BFRQ from a base station (e.g., a gNB). This period may be referred to as a gNB response window, a gNB window, a beam recovery request response window, etc. If no gNB response is detected within this window, the UE may retransmit the BFRQ.

[0117] The UE may transmit a message indicating that the beam reconfiguration is complete to the base station, for example, via the PUCCH or the PUSCH.

[0118] A beam recovery success (BR success) may indicate, for example, that the message has been transmitted, whereas a beam recovery failure (BR failure) may indicate, for example, that a predetermined number of BFRQ transmissions have been transmitted or that a beam-failure-recovery-timer has expired.

[0119] Rel.15 supports the use of a random access procedure to perform beam recovery procedures (e.g., BFRQ notification) for beam failures detected in an SpCell (PCell / PSCell). On the other hand, Rel.16 supports the use of at least one of PUCCH (e.g., Scheduling Request (SR)) transmission for BFR and MAC CE (e.g., UL-SCH) transmission for BFR to perform beam recovery procedures (e.g., BFRQ notification) for beam failures detected in an SCell.

[0120] For example, the UE may transmit information about beam failure using MAC CE-based two-step. The information about beam failure may include information about the cell that detected the beam failure and information about new candidate beams (or new candidate RS indices).

[0121] [Step 1] If a BF is detected, a PUCCH-BFR (scheduling request (SR)) may be transmitted from the UE to the PCell / PSCell. Then, an UL grant (DCI) for step 2 below may be transmitted from the PCell / PSCell to the UE. If a beam failure is detected and there is a MAC CE (or UL-SCH) for transmitting information about a new candidate beam, step 1 (e.g., PUCCH transmission) may be omitted and step 2 (e.g., MAC CE transmission) may be performed.

[0122] [Step 2] Then, the UE may transmit information about the cell where beam failure was detected (failed) (e.g., cell index) and information about the new candidate beam to the base station (PCell / PSCell) via an uplink channel (e.g., PUSCH) using MAC CE. After that, through the BFR procedure, the QCL of the PDCCH / PUCCH / PDSCH / PUSCH may be updated to the new beam after a predetermined period (e.g., 28 symbols) after receiving a response signal from the base station.

[0123] Note that the numbers of these steps are for explanatory purposes only, and multiple steps may be combined or the order may be reversed. Furthermore, whether to perform BFR may be configured in the UE using higher layer signaling.

[0124] (BFD-RS) In Rel. 16, for each BWP of one serving cell, the UE may be provided with a set of periodic (P)-CSI-RS resource configuration indices q0 via failure detection resources (failureDetectionResources, failureDetectionResourcesToAddModList, RadioLinkMonitoringConfig) and at least one set of P-CSI-RS resource configuration indices and SS / PBCH block indices q1 via the candidate beam RS list (candidateBeamRSList) or the extended candidate beam RS list (candidateBeamRSListExt-r16) or the candidate beam RS list for SCell (candidateBeamRSSCellList-r16).

[0125] Here, q0 bar is written as "q0" with an overline. Hereinafter, q0 bar will be written simply as q0. q1 bar is written as "q1" with an overline. Hereinafter, q1 bar will be written simply as q1.

[0126] The set of P-CSI-RS resources q0 provided by the failure detection resources may be referred to as explicit BFD-RS.

[0127] The UE may perform L1-RSRP measurements, etc., using RS resources corresponding to indices included in at least one of set q0 and set q1 to detect beam failure.

[0128] In the present disclosure, providing the above-mentioned higher layer parameters indicating information on indexes corresponding to BFD resources may be interchangeably read as configuring BFD resources, configuring a BFD-RS, etc. In the present disclosure, BFD resources, periodic CSI-RS resource configuration index or SSB index set q0, BFD-RS, BFD-RS set, and RS set may be interchangeably read.

[0129] If the UE is not provided with q0 by the failure detection resources (failureDetectionResources) for one of the BWPs of its serving cell, the UE determines the RS (set q0) to use for the BFD procedure according to the following implicit BFD-RS determination (implicit RS determination) procedure.

[0130] [Implicit BFD-RS Decision Procedure] The UE determines to include in set q0 P-CSI-RS resource configuration indices that have the same value as the RS indices in the RS set indicated by the TCI state (TCI-State) for the corresponding CORESET that the UE uses to monitor the PDCCH. If there are two RS indices in one TCI state, set q0 includes RS indices that have a QCL type D configuration for the corresponding TCI state. The UE assumes that set q0 includes up to two RS indices. The UE assumes single-port RSs in set q0.

[0131] This set q0 may be called the implicit BFD-RS.

[0132] In this way, the UE determines the BFD-RS (RS set) according to the TCI state for the PDCCH. The UE assumes that the RS set includes up to two RSs.

[0133] (PDCCH / CORESET setting) For the PDCCH / CORESET settings in Rel. 15, there is the following case 0. [Case 0] One CORESET is set with one TCI state without a CORESET pool index (information about the TRP).

[0134] In the Rel. 16 extensions for PDCCH / CORESET, there is the following Case 1. [Case 1] For multi-TRP based on multi-DCI, a CORESET pool index (information about the TRP) is set for each CORESET (a CORESET pool index is associated with a certain CORESET).

[0135] For the Rel.17 extensions regarding PDCCH / CORESET, there are the following Cases 2 / 3. [Case 2] As an extension of SFN, one CORESET can configure / activate up to two TCI states by RRC IE / MAC CE (two TCI states are associated with one CORESET). SFN may be used for both high speed train (HST) and reliability enhancement. [Case 3] As an extension of repetition, for PDCCH repetition, two PDCCH candidates in two search space (SS) sets are linked, and each SS set is associated with a corresponding CORESET (two PDCCH candidates / two SS sets / two CORESETs are linked). The two SS sets may be associated with the same or different CORESETs. One CORESET can be associated with up to one TCI state according to the RRC IE / MAC CE. If two SS sets are associated with different CORESETs, the PDCCH repetition is a multi-TRP repetition. If two SS sets are associated with the same CORESET (same TCI state), the PDCCH repetition is a single-TRP repetition.

[0136] <Problem 1> The question is whether any of the above cases 0 to 3 can be configured simultaneously (in combination) for the UE, as well as at least one of the following cases A to D. [Case A] Case 1+2 [Case B] Case 1+3 [Case C] Case 2+3 [Case D] Case 1+2+3

[0137] <Problem 2> For each of the above combination cases, the question arises as to whether extensions to the rules for setting / determining RLM-RS / BFD-RS are necessary.

[0138] <Problem 3> For each of the combinations mentioned above, the question arises as to whether an extension to the handling of QCL Type D collisions is necessary.

[0139] In at least one of these cases, it is unclear how the UE will perform reception based on the PDCCH / CORESET settings. If reception is not performed appropriately, this may result in a deterioration in communication quality, a decrease in communication throughput, etc.

[0140] Therefore, the present inventors came up with the idea of a reception method based on the PDCCH / CORESET setting.

[0141] Hereinafter, embodiments according to the present disclosure will be described in detail with reference to the drawings. Wireless communication methods according to the embodiments may be applied independently or in combination.

[0142] In the present disclosure, "A / B / C" and "at least one of A, B, and C" may be read as interchangeable. In the present disclosure, cell, serving cell, CC, carrier, BWP, DL BWP, UL BWP, active DL BWP, active UL BWP, and band may be read as interchangeable. In the present disclosure, index, ID, indicator, and resource ID may be read as interchangeable. In the present disclosure, sequence, list, set, group, group, cluster, subset, etc. may be read as interchangeable. In the present disclosure, support, control, controllable, operate, and operable may be read as interchangeable.

[0143] In the present disclosure, the terms configure, activate, update, indicate, enable, specify, and select may be read interchangeably.

[0144] In this disclosure, the terms link, have linkage, associate, correspond, map, repeat, and relate may be read interchangeably. In this disclosure, the terms allocate, assign, monitor, and map may be read interchangeably.

[0145] In the present disclosure, higher layer signaling may be, for example, any one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, etc., or a combination thereof. In the present disclosure, RRC, RRC signaling, RRC parameters, higher layer parameters, RRC information elements (IEs), RRC messages, and settings may be read interchangeably.

[0146] The MAC signaling may use, for example, a MAC Control Element (MAC CE), a MAC Protocol Data Unit (PDU), etc. The broadcast information may be, for example, a Master Information Block (MIB), a System Information Block (SIB), Remaining Minimum System Information (RMSI), Other System Information (OSI), etc.

[0147] In the present disclosure, MAC CE and activation / deactivation command may be read interchangeably.

[0148] In this disclosure, the terms beam, spatial domain filter, spatial setting, TCI state, UL TCI state, unified TCI state, unified beam, common TCI state, common beam, TCI assumption, QCL assumption, QCL parameter, spatial domain receive filter, UE spatial domain receive filter, UE receive beam, DL beam, DL receive beam, DL precoding, DL precoder, DL-RS, QCL type D RS in TCI state / QCL assumption, QCL type A RS in TCI state / QCL assumption, spatial relationship, spatial domain transmit filter, UE spatial domain transmit filter, UE transmit beam, UL beam, UL transmit beam, UL precoding, UL precoder, PL-RS, antenna port, panel group, and beam group may be interchangeable. In this disclosure, the terms QCL type X-RS, DL-RS associated with QCL type X, DL-RS with QCL type X, source of DL-RS, SSB, CSI-RS, and SRS may be interchangeable.

[0149] In the present disclosure, panel, Uplink (UL) transmitting entity, TRP, spatial relationship, control resource set (CORESET), PDSCH, codeword, base station, antenna port of a certain signal (e.g., Demodulation Reference Signal (DMRS) port), antenna port group of a certain signal (e.g., DMRS port group), group for multiplexing (e.g., Code Division Multiplexing (CDM) group, reference signal group, CORESET group), CORESET pool, CORESET subset, CW, redundancy version (RV), layer (MIMO layer, transmission layer, spatial layer) may be read as interchangeable.

[0150] The panel may be associated with at least one of a group index of an SSB / CSI-RS group, a group index of a group-based beam report, and a group index of an SSB / CSI-RS group for group-based beam reporting.

[0151] Furthermore, a panel identifier (ID) and a panel may be interchangeable. That is, a TRP ID and a TRP, a CORESET group ID and a CORESET group, etc. may be interchangeable.

[0152] In the present disclosure, the terms TRP, transmission point, panel, DMRS port group, CORESET pool, and one of two TCI states associated with one code point in a TCI field may be read interchangeably.

[0153] In this disclosure, a single PDCCH may be assumed to be supported when multiple TRPs utilize an ideal backhaul, and multiple PDCCHs may be assumed to be supported when multiple TRPs utilize a non-ideal backhaul.

[0154] The ideal backhaul may be called DMRS port group type 1, reference signal associated group type 1, antenna port group type 1, CORESET pool type 1, etc. The non-ideal backhaul may be called DMRS port group type 2, reference signal associated group type 2, antenna port group type 2, CORESET pool type 2, etc. The names are not limited to these.

[0155] In this disclosure, the terms "single TRP," "single TRP system," "single TRP transmission," and "single PDSCH" may be interchangeable. In this disclosure, the terms "multiple TRP," "multiple TRP system," "multiple TRP transmission," and "multiple PDSCH" may be interchangeable. In this disclosure, the terms "single DCI," "single PDCCH," "multiple TRP based on a single DCI," and "activating two TCI states on at least one TCI codepoint" may be interchangeable.

[0156] In the present disclosure, single TRP, channel using single TRP, channel using one TCI state / spatial relationship, no multi-TRP enabled by RRC / DCI, no multiple TCI states / spatial relationships enabled by RRC / DCI, no CORESETPoolIndex value of 1 set for any CORESET, and no codepoint in the TCI field mapped to two TCI states may be read interchangeably.

[0157] In the present disclosure, "multi-TRP," "channel using multi-TRP," "channel using multiple TCI states / spatial relationships," "multi-TRP being enabled by RRC / DCI," "multiple TCI states / spatial relationships being enabled by RRC / DCI," and "at least one of multi-TRP based on a single DCI" and "multi-TRP based on multiple DCI" may be interchangeable. In the present disclosure, "multi-TRP based on multiple DCI," and "setting a CORESET pool index (CORESETPoolIndex) value of 1 for the CORESET" may be interchangeable. In the present disclosure, "multi-TRP based on a single DCI," and "at least one code point in the TCI field is mapped to two TCI states" may be interchangeable.

[0158] In the present disclosure, TRP#1 (first TRP, TRP#0) may correspond to CORESET pool index=0 or may correspond to the first of two TCI states corresponding to one code point in the TCI field. TRP#2 (second TRP, TRP#1) may correspond to CORESET pool index=1 or may correspond to the second of two TCI states corresponding to one code point in the TCI field.

[0159] In the present disclosure, the terms DMRS, DMRS port, and antenna port may be interpreted as interchangeable.

[0160] In the present disclosure, QCL and QCL Type D may be read interchangeably.

[0161] In this disclosure, multiple SS sets (SS set pairs) with linkage, or a linked SS set, may mean that one SS set is linked with another SS set via RRC IE / MAC CE for PDCCH repetition. An SS set without linkage (an individual SS set) may mean that the SS set is not linked with another SS set via RRC IE / MAC CE.

[0162] In the present disclosure, the terms "having linkage," "linked," and "pair" may be read as interchangeable. In the present disclosure, the terms "not having linkage," "not linked," and "single" may be read as interchangeable.

[0163] In the present disclosure, the terms "linked SS set," "linked CORESET," "linked PDCCH candidate," "CORESET associated with linked SS set," and "PDCCH candidate within linked SS set" may be interchangeable. In the present disclosure, two linked CORESETs may refer to two CORESETs associated with two linked SS sets, respectively. In the present disclosure, two linked PDCCH candidates may be two PDCCH candidates having the same aggregation level and the same candidate index within two linked SS sets.

[0164] In the present disclosure, receiving DL signals (PDSCH / PDCCH) using SFN may mean at least one of using the same time and frequency resources and receiving the same data (PDSCH) or control information (PDCCH) in reception from multiple TRPs. Also, receiving DL signals using SFN may mean at least one of using the same time and frequency resources and receiving the same data or control information in reception using multiple TCI states / space domain filters / beams / QCLs.

[0165] (Wireless communication method) First Embodiment An embodiment for solving the above-mentioned problem 1 will be described.

[0166] <<Condition 1-1>> Case A (Case 1+2) The UE may follow either option 1 or 2 below.

[0167] [Option 1] Case A is not supported.

[0168] For example, if the CORESET pool index is set (for any (at least one) CORESET), no CORESET can have two TCI states set / activated.

[0169] In Rel. 16, if at least one CORESET has a CORESET pool index set, the remaining CORESETs (without a CORESET pool index set) are assumed to have a CORESET pool index of 0.

[0170] [Option 2] Case A can be configured. Case A may also be configured depending on the UE capability.

[0171] The UE may follow at least one of the following options 2-1 to 2-2.

[0172] [[Option 2-1]] If a CORESET pool index is configured (for any CORESET), one CORESET can have two TCI states configured / activated by the RRC IE / MAC CE.

[0173] Option 2-1 may be applied to any CORESET, or may be applied to any CORESET except CORESET#0 (the CORESET with index 0).

[0174] The UE may follow one of the following options 1 to 3: [[[Option 1]]] Two TCI states for one CORESET come from different TRPs (associated with different CORESET pool indices). [[[Option 2]]] Two TCI states for one CORESET come from the same TRP (associated with the same CORESET pool index). [[[Option 3]]] Two TCI states per CORESET is not limited.

[0175] [[Option 2-2]] If a CORESET pool index is configured for one CORESET, the CORESET cannot have two TCI states configured / activated by the RRC IE / MAC CE. For a CORESET for which the CORESET pool index is not explicitly configured, the CORESET can have two TCI states configured / activated by the RRC IE / MAC CE.

[0176] If one CORESET is explicitly configured with a CORESET pool index, the UE applies CORESET pool index = 0 for that CORESET. For Option 2-2, any of the options 1 to 3 may be applied, which are the same as for Option 2-1.

[0177] UE capabilities for at least one of options 2-1 to 2-2 may be specified in the specification.

[0178] 2A is a diagram showing an example of Option 1 in Option 2-1 / 2-2. In this example, CORESET pool index = 0 is set for each of CORESETs #0, #1, and #2, and CORESET pool index = 1 is set for each of CORESETs #4 and #5. Beam (TCI state) #1 is associated with CORESET pool index = 0 (TRP #0), and beam (TCI state) #3 is associated with CORESET pool index = 1 (TRP #1).

[0179] In option 1, if two TCI states #1 and #3 are activated for CORESET #2 from TRP #0, the two TCI states originate from different TRPs #0 and #1, respectively. If two TCI states #1 and #3 are activated for CORESET #5 from TRP #1, the two TCI states originate from different TRPs #0 and #1, respectively. Here, the TRPs corresponding to the TCI states may not correspond to the CORESET pool index.

[0180] 2B is a diagram showing an example of Option 2 in Option 2-1 / 2-2. In this example, CORESET pool index = 0 is set for each of CORESETs #0, #1, and #2, and CORESET pool index = 1 is set for each of CORESETs #4 and #5. Beams (TCI states) #1 and #2 are associated with CORESET pool index = 0 (TRP #0), and beams (TCI states) #3 and #4 are associated with CORESET pool index = 1 (TRP #1).

[0181] In option 2, if two TCI states #1 and #2 are activated for CORESET #2 from TRP #0, the two TCI states originate from the same TRP #0. If two TCI states #3 and #4 are activated for CORESET #5 from TRP #1, the two TCI states originate from the same TRP #1. Here, the TRPs corresponding to the TCI states may not correspond to multi-TRP repetitions using two TCI states.

[0182] <<Mode 1-2>> Case B (Case 1+3) The UE may follow either option 1 or 2 below.

[0183] [Option 1] Case B is not supported.

[0184] For example, if the CORESET pool index is set (for any (at least one) CORESET), no PDCCH candidate can be linked for repetition.

[0185] In Rel. 16, if at least one CORESET has a CORESET pool index set, the remaining CORESETs (without a CORESET pool index set) are assumed to have a CORESET pool index of 0.

[0186] [Option 2] Case B can be configured. Case B may be configured depending on the UE capability.

[0187] The UE may follow at least one of the following options 2-1 to 2-3.

[0188] [[Option 2-1]] If a CORESET pool index is configured (for any CORESET), two PDCCH candidates from two CORESETs associated with the same CORESET pool index may be configured to be linked for repetition. For TDM repetition, this option is preferred.

[0189] [[Option 2-2]] If a CORESET pool index is configured (for a given CORESET), two PDCCH candidates from two CORESETs associated with different CORESET pool indices may be configured to be linked for repetition. This option can be applied for TDM / FDM repetition.

[0190] [[Option 2-3]] If a CORESET pool index is configured (for any CORESET), there is no restriction on the two linked PDCCH candidates for repetition.

[0191] UE capabilities for at least one of options 2-1 to 2-3 may be specified in the specification.

[0192] Each of Options 2-1 to 2-3 may be applied. For each of Options 2-1 to 2-3, at least one of the following Restrictions 1 and 2 may be taken into account (depending on the UE capabilities): [Limit 1] Maximum configurable number of linked PDCCH candidates / CORESETs, with repetition for each CORESET pool index for each cell. [Limit 2] Repeat settings are limited to only one CORESET pool index.

[0193] 3A is a diagram showing an example of Option 2-1. In this example, CORESET pool index = 0 is set for each of CORESET #0, #1, and #2, and CORESET pool index = 1 is set for each of CORESET #4 and #5. For repetition, CORESET #1 and #2, which are set with the same CORESET pool index, are linked.

[0194] 3B is a diagram showing an example of Option 2-2. In this example, CORESET pool index = 0 is set for each of CORESET #0, #1, and #2, and CORESET pool index = 1 is set for each of CORESET #4 and #5. For repetition, CORESET #2 and #5, which are set with different CORESET pool indexes, are linked.

[0195] From the CORESET point of view, there is no difference between a single DCI-based multi-TRP (Rel. 16) and a single DCI-based single-TRP (Rel. 15). In case 3, when distinguishing between a single DCI-based multi-TRP (Rel. 16) and a single DCI-based single-TRP (Rel. 15), the PDSCH configuration may be taken into consideration. For example, if case 3 is configured by an RRC IE, whether the UE expects to receive an Enhanced TCI States Activation / Deactivation for UE-specific PDSCH MAC CE to activate one or two TCI states for a codepoint in the DCI (TCI field) for PDSCH scheduling may follow either option 1 or 2 below. [Option 1] The UE does not expect to receive an "extended" TCI States Activation / Deactivation MAC CE for UE-specific PDSCH, but can only receive TCI States Activation / Deactivation for UE-specific PDSCH MAC CE. [Option 2] The UE can receive an "extended" TCI state activation / deactivation MAC CE for UE-specific PDSCH, which may mean that PDCCH repetition for single DCI-based multiple TRPs can be supported.

[0196] <<Modes 1-3>> Case C (Case 2+3) The UE may follow either option 1 or 2 below.

[0197] [Option 1] Case C is not supported.

[0198] For example, if two PDCCH candidates are configured to be linked due to repetition, no CORESET can have two TCI states configured / activated.

[0199] [Option 2] Case C can be configured. Case C may be configured depending on the UE capability.

[0200] The UE may follow at least one of the following options 2-1 to 2-2.

[0201] [[Option 2-1]] If two PDCCH candidates (from two CORESETs) are configured to be linked for repetition, only one TCI state is configured / activated for the CORESET with linked PDCCH candidates. One or two TCI states can be configured / activated for the CORESET without linked PDCCH candidates.

[0202] [[Option 2-2]] If two PDCCH candidates (from two CORESETs) are configured to be linked for repetition, one or two TCI states can be configured / activated for any CORESET (even if it is the CORESET with linked PDCCH candidates). The UE is required to monitor two or more beams (TCI states) simultaneously.

[0203] UE capabilities for at least one of options 2-1 to 2-2 may be specified in the specification.

[0204] Figure 4A shows an example of option 2-1. In this example, CORESETs #0, #1, and #2 are configured. For repetition, CORESETs #1 and #2 are linked. Only one TCI state is configured / activated for each of CORESETs #1 and #2. Two TCI states can be configured / activated for CORESET #0.

[0205] FIG. 4B is a diagram showing an example of Option 2-2. In this example, CORESETs #0, #1, and #2 are configured. For repetition, CORESETs #1 and #2 are linked. For each of CORESETs #1 and #2, there is no restriction in Option 2-1, and two TCI states can be configured / activated. For CORESET #0, two TCI states can be configured / activated.

[0206] <<Mode 1-4>> Case D (Case 1+2+3) The UE may follow either option 1 or 2 below.

[0207] [Option 1] Case D is not supported. This option simplifies the behavior.

[0208] [Option 2] Case D may be supported with restrictions based on a combination of options in aspects 1-1 to 1-3 above. Case D may be configured depending on UE capabilities.

[0209] For example, option 2-1 of aspect 1-3 may be applied within a certain CORESET pool index.

[0210] FIG. 5 is a diagram showing an example of Case D. In this example, CORESET pool index=0 is set for each of CORESETs #0, #1, and #2, and CORESET pool index=1 is set for each of CORESETs #4 and #5. For repetition, CORESETs #1 and #2, which are set with the same CORESET pool index, are linked. In this example, option 2-1 of aspect 1-3 is applied for CORESET pool index=0. Only one TCI state is set / activated for each of CORESETs #1 and #2. Two TCI states can be set / activated for CORESET #0. Only one TCI state is set / activated for each of CORESETs #4 and #5.

[0211] <<Aspects 1-5>> Other The above options may be applied in other cases, for example, at least one of the following variants 1 to 4 may be applied. [Variation 1] Option 2-1 of aspect 1-2 is applied to case B (case 1+3). [Variation 2] Option 2-2 of aspect 1-2 is applied to case B (case 1+3). [Modification 3] Option 2-3 of aspect 1-2 is applied to case B (case 1+3). [Modification 4] Option 2-1 of aspect 1-3 is applied to case C (case 2+3).

[0212] According to this embodiment, it becomes clear whether two or more of cases 1 to 3 are set simultaneously (combined).

[0213] <Second embodiment> An embodiment for solving the above-mentioned problem 2 will be described.

[0214] For each case, the first embodiment may be applied.

[0215] The (explicit) configuration / (implicit) determination of RLM-RS / BFD-RS may follow at least one of the following determination methods 1 to 7.

[0216] [Decision Method 1] For Case 1 (Cases 2 / 3 do not occur, and only Case 1 occurs), the implicit RS decision rule for BFR per TRP is applied.

[0217] [Determination Method 2] For Case 2 (Case 1 / 3 does not occur, and only Case 2 occurs), the rules for implicit RS determination for cell-by-cell BFR and TRP-by-TRP BFR are applied. In this case, the question arises as to whether different priorities are considered for CORESETs with two TCI states. Also, the question arises as to whether the BLER calculation for PDCCH needs to be extended. The assumption for the hypothetical BLER calculation for PDCCH may be either of the following assumptions 1 and 2. [[Assumption 1]] RS in two TCI states or CSI-RS / SSB are used directly for BFD-RS. [[Assumption 2]] Under the SFN assumption of a BFD-RS pair, the UE calculates one virtual BLER.

[0218] [Decision Method 3] For Case 3 (Case 1 / 2 do not occur, and only Case 3 occurs), the question is whether the extension of BFD-RS per TRP is considered. Also, the question is whether different priorities for linked CORESETs are considered.

[0219] [Decision Method 4] When Option 2-1 of Mode 1-2 is applied to Case B (Case 1+3), the same problem as in Decision Method 3 arises.

[0220] [Decision Method 5] When Option 2-2 of Mode 1-2 is applied to Case B (Case 1+3), the same problem as in Decision Method 3 arises.

[0221] [Decision Method 6] When Option 2-3 of Mode 1-2 is applied to Case B (Case 1+3), the same problem as in Decision Method 3 arises.

[0222] [Decision Method 7] When Option 2-1 of Mode 1-3 is applied to Case C (Case 2+3), the same problems as those of Decision Methods 2 and 3 arise.

[0223] In the present disclosure, an implicit RS may refer to an RS that is selected / determined according to a specific rule when the RS is not explicitly set.

[0224] <<Aspect 2-1>> In this aspect, case 2 is assumed, i.e., one CORESET can configure / activate up to two TCI states via RRC IE / MAC CE.

[0225] The question is how to determine the implicit RS for RLM and / or BFD per cell, for example, whether to consider different priorities for a CORESET with two TCI states.

[0226] The implicit RS determination for at least one of RLM and per-cell BFD may follow at least one of options 0 to 2 and variants 1 to 3 below.

[0227] [Option 0] Same rules as Rel.16.

[0228] The UE selects the N RSs provided for the active TCI state for PDCCH reception in the CORESET associated with the SS set having the shortest monitoring period (in ascending order of monitoring period). If more than one CORESET is associated with the SS set having the same monitoring period, the UE determines the RSs in order of CORESETs from the highest CORESET index (in descending order of CORESET index).

[0229] [Option 1] First, the selection is made in the order of the monitoring period of the SS set, then in the order of whether there are two TCI states, and then in the order of the CORESET index.

[0230] The UE selects N RSs provided for active TCI states for PDCCH reception in the CORESET associated with the SS set with the shortest monitoring period (in ascending order of monitoring period). If more than one CORESET is associated with the SS set with the same monitoring period, the UE first determines an RS from the CORESET with two TCI states, then determines an RS from the CORESET with one TCI state.

[0231] The UE determines the RS among multiple CORESETs having two TCI states in order of CORESETs starting from the highest CORESET index (in descending order of CORESET index).The UE determines the RS among multiple CORESETs having one TCI state in order of CORESETs starting from the highest CORESET index (in descending order of CORESET index).

[0232] In the example of Figure 6, the UE preferentially selects a CORESET associated with a shorter monitoring period and determines an RS from the TCI state of the selected CORESET (S10). Next, from CORESETs associated with the same monitoring period, it preferentially selects a CORESET with two TCI states and determines an RS from the TCI state of the selected CORESET (S20). Next, from CORESETs with the same number of TCI states, it preferentially selects a CORESET with a higher CORESET index and determines an RS from the TCI state of the selected CORESET (S30). Through this operation, the UE determines N RSs.

[0233] [Option 2] First, select whether there are two TCI states or not, then select by CORESET index.

[0234] The UE selects N RSs provided for active TCI states for PDCCH reception in a CORESET with two TCI states, and then determines an RS from a CORESET with one TCI state.

[0235] The UE determines the RS among multiple CORESETs having two TCI states in order of CORESETs starting from the highest CORESET index (in descending order of CORESET index).The UE determines the RS among multiple CORESETs having one TCI state in order of CORESETs starting from the highest CORESET index (in descending order of CORESET index).

[0236] In the example of Fig. 7, the UE preferentially selects a CORESET having two TCI states and determines an RS from the TCI state of the selected CORESET (S40). Next, from the CORESETs having the same number of TCI states, the UE preferentially selects a CORESET having a higher CORESET index and determines an RS from the TCI state of the selected CORESET (S50). Through this operation, the UE determines N RSs.

[0237] [Variation 1] In option 1 / 2, the UE first determines the RS from a CORESET with one TCI state, and then determines the RS from a CORESET with two TCI states.

[0238] [Variation 2] In option 1 / 2, the UE determines RS only from a CORESET with one TCI state, or determines RS only from a CORESET with two TCI states.

[0239] [Variation 3] In Option 1 / 2, the UE determines the RS by taking into consideration factors such as the monitoring period of the SS set, the CORESET index, and the number of TCI states for the CORESET. The priorities (orders) of these factors may be interchanged.

[0240] <<Aspect 2-2>> In this aspect, case 2 is assumed, i.e., one CORESET can configure / activate up to two TCI states via RRC IE / MAC CE.

[0241] The question arises as to how to determine the implicit RS for BFD per TRP, e.g., whether to consider different priorities for a CORESET with two TCI states.

[0242] The implicit RS determination for BFD per TRP may follow at least one of the following options 0 to 2, variants 1 to 3.

[0243] [Option 0] Same rules as Rel.16.

[0244] For each TRP, the UE selects N RSs provided for the active TCI state for PDCCH reception in the CORESET associated with the SS set with the shortest monitoring period (in ascending order of monitoring period). If more than one CORESET is associated with the SS set with the same monitoring period, the UE determines the RSs in descending order of CORESET index from the highest CORESET index.

[0245] [Option 1] First, the selection is made in the order of the monitoring period of the SS set, then in the order of whether there are two TCI states, and then in the order of the CORESET index.

[0246] For each TRP, the UE selects N RSs provided for active TCI states for PDCCH reception in the CORESET associated with the SS set with the shortest monitoring period (in ascending order of monitoring period). If more than one CORESET is associated with the SS set with the same monitoring period, the UE first determines an RS from the CORESET with two TCI states, then determines an RS from the CORESET with one TCI state.

[0247] The UE determines the RS among multiple CORESETs having two TCI states in order of CORESETs starting from the highest CORESET index (in descending order of CORESET index).The UE determines the RS among multiple CORESETs having one TCI state in order of CORESETs starting from the highest CORESET index (in descending order of CORESET index).

[0248] [Option 2] First, select whether there are two TCI states or not, then select by CORESET index.

[0249] For each TRP, the UE selects N RSs provided for active TCI states for PDCCH reception in a CORESET with two TCI states, and then determines an RS from a CORESET with one TCI state.

[0250] The UE determines the RS among multiple CORESETs having two TCI states in order of CORESETs starting from the highest CORESET index (in descending order of CORESET index).The UE determines the RS among multiple CORESETs having one TCI state in order of CORESETs starting from the highest CORESET index (in descending order of CORESET index).

[0251] [Variation 1] In option 1 / 2, the UE first determines the RS from a CORESET with one TCI state, and then determines the RS from a CORESET with two TCI states.

[0252] [Variation 2] In option 1 / 2, the UE determines RS only from a CORESET with one TCI state, or determines RS only from a CORESET with two TCI states.

[0253] [Variation 3] In Option 1 / 2, the UE determines the RS by taking into consideration factors such as the monitoring period of the SS set, the CORESET index, and the number of TCI states for the CORESET. The priorities (orders) of these factors may be interchanged.

[0254] <<Aspect 2-3>> In this aspect, case 2 is assumed, i.e., one CORESET can configure / activate up to two TCI states via RRC IE / MAC CE.

[0255] In RLM / BFD, the assumptions for calculating the virtual BLER for PDCCH are an issue, for example, whether the BLER is calculated under the SFN assumption using two RSs for RLM / BFD in two TCI states of one CORESET.

[0256] For a CORESET with two TCI states in at least one of RLM and BFD per cell, the UE may follow either option 1 or 2 below.

[0257] [Option 1] The UE calculates one virtual BLER under the SFN assumption of the RLM / BFD RS in the two TCI states of its CORESET.

[0258] [Option 2] The UE calculates the virtual BLER under the RS assumptions of each RLM / BFD in each TCI state of its CORESET.

[0259] In BFD per TRP, for a CORESET with two TCI states, the UE may follow either option 1 or 2 below.

[0260] [Option 1] The UE calculates one virtual BLER under the SFN assumption for the RLM / BFD RSs in the two TCI states of its CORESET. In SFN, the UE can receive at least one SFN PDCCH. For example, if one of the SFN PDCCHs has a very low SNR, SFN PDCCH reception is equivalent to one PDCCH reception.

[0261] [Option 2] The UE calculates the virtual BLER under the RS assumptions of each RLM / BFD in each TCI state of its CORESET.

[0262] In SFN PDCCH (if CORESET is configured with one TCI state), the UE always receives the SFN PDCCH and option 1 may apply. In PDCCH repetition (if two SS sets are linked and associated with the same / different CORESET), the UE always receives one PDCCH and option 2 may apply.

[0263] <<Aspect 2-4>> In this aspect, case 3 is assumed, ie, for a PDCCH repetition, two PDCCH candidates in two SS sets are linked, and each SS set is associated with a corresponding CORESET.

[0264] The question arises as to how to determine the implicit RS for RLM / BFD, e.g., whether to consider different priorities for two linked SS sets / CORESETs.

[0265] The implicit RS determination for at least one of RLM and per-cell BFD may follow at least one of the following options 0 to 3, variants 1 to 3.

[0266] [Option 0] Same rules as Rel.16.

[0267] The UE selects the N RSs provided for the active TCI state for PDCCH reception in the CORESET associated with the SS set having the shortest monitoring period (in ascending order of monitoring period). If more than one CORESET is associated with the SS set having the same monitoring period, the UE determines the RSs in order of CORESETs from the highest CORESET index (in descending order of CORESET index).

[0268] [Option 1] First, the selection is made in order of the monitoring period of the SS set, then in order of whether it is linked or not, and then in order of the CORESET index.

[0269] The UE selects N RSs provided for the active TCI state for PDCCH reception in the CORESET associated with the SS set with the shortest monitoring period (in ascending order of monitoring period). If more than one CORESET is associated with the SS set with the same monitoring period, the UE determines the RS from the CORESET associated with the linked SS set for repetition (linked CORESET), and then determines the RS from the CORESET associated with the SS set with no linkage (no linkage CORESET).

[0270] The UE determines RSs in order of CORESETs (in descending order of CORESET index) from the highest CORESET index among CORESETs associated with linked SS sets (linked CORESETs).The UE determines RSs in order of CORESETs (in descending order of CORESET index) from the highest CORESET index among CORESETs associated with SS sets without linkage (CORESETs without linkage).

[0271] [Option 2] First, select whether it is linked or not, then select by CORESET index.

[0272] The UE selects N RSs provided for the active TCI state for PDCCH reception in a CORESET associated with a linked SS set (linked CORESET), and then determines RSs from a CORESET associated with an SS set without linkage (CORESET without linkage).

[0273] The UE determines RSs in order of CORESETs (in descending order of CORESET index) from the highest CORESET index among CORESETs associated with linked SS sets (linked CORESETs).The UE determines RSs in order of CORESETs (in descending order of CORESET index) from the highest CORESET index among CORESETs associated with SS sets without linkage (CORESETs without linkage).

[0274] [Option 3] First, the selection is made in order of whether or not the set is linked, then in order of the monitoring period of the SS set, and then in order of the CORESET index.

[0275] The UE selects N RSs provided for the active TCI state for PDCCH reception in a CORESET associated with a linked SS set (linked CORESET), and then determines RSs from a CORESET associated with an SS set without linkage (CORESET without linkage).

[0276] The UE first determines the RS in the CORESET associated with the SS set having the shortest monitoring period among the linked SS sets (CORESETs associated with the linked SS sets) in order of the shortest monitoring period (in ascending order of the monitoring period), and then determines the RS in the CORESET order of the highest CORESET index (in descending order of the CORESET index).The UE first determines the RS in the CORESET associated with the SS set having the shortest monitoring period among the CORESETs associated with the SS sets having no linkage (CORESETs having no linkage) in order of the shortest monitoring period (in ascending order of the monitoring period), and then determines the RS in the CORESET order of the highest CORESET index (in descending order of the CORESET index).

[0277] [Variation 1] In option 1 / 2, the UE first determines the RS from the CORESET / SS set that has no linkage, and then determines the RS from the linked CORESET / SS set.

[0278] [Variation 2] In option 1 / 2, the UE determines the RS only from the linked CORESET / SS set, or only from the CORESET / SS set without linkage.

[0279] [Variation 3] In Option 1 / 2, the UE determines the RS by considering the following factors: the monitoring period of the SS set, the CORESET index, and whether the CORESET / SS set has linkage. The priority (order) of these factors may be interchanged.

[0280] <<Aspect 2-5>> In this aspect, case 3 is assumed, ie, for a PDCCH repetition, two PDCCH candidates in two SS sets are linked, and each SS set is associated with a corresponding CORESET.

[0281] The question arises as to how to determine the implicit RS for BFD per TRP, e.g., whether to consider different priorities for two linked SS sets / CORESETs.

[0282] The implicit RS determination for BFD per TRP may follow at least one of the following options 0 to 3, variants 1 to 3.

[0283] [Option 0] Same rules as Rel.16.

[0284] For each TRP, the UE selects N RSs provided for the active TCI state for PDCCH reception in the CORESET associated with the SS set with the shortest monitoring period (in ascending order of monitoring period). If more than one CORESET is associated with the SS set with the same monitoring period, the UE determines the RSs in descending order of CORESET index from the highest CORESET index.

[0285] [Option 1] First, the selection is made in order of the monitoring period of the SS set, then in order of whether it is linked or not, and then in order of the CORESET index.

[0286] For each TRP, the UE selects N RSs provided for the active TCI state for PDCCH reception in the CORESET associated with the SS set with the shortest monitoring period (in ascending order of monitoring period). If more than one CORESET is associated with the SS set with the same monitoring period, the UE determines the RS from the CORESET associated with the linked SS set for repetition (linked CORESET), and then determines the RS from the CORESET associated with the SS set with no linkage (no linkage CORESET).

[0287] The UE determines RSs in order of CORESETs (in descending order of CORESET index) from the highest CORESET index among CORESETs associated with linked SS sets (linked CORESETs).The UE determines RSs in order of CORESETs (in descending order of CORESET index) from the highest CORESET index among CORESETs associated with SS sets without linkage (CORESETs without linkage).

[0288] [Option 2] First, select whether it is linked or not, then select by CORESET index.

[0289] For each TRP, the UE selects N RSs provided for the active TCI state for PDCCH reception in the CORESET associated with the linked SS set (linked CORESET), and then determines the RSs from the CORESET associated with the SS set without linkage (CORESET without linkage).

[0290] The UE determines RSs in order of CORESETs (in descending order of CORESET index) from the highest CORESET index among CORESETs associated with linked SS sets (linked CORESETs).The UE determines RSs in order of CORESETs (in descending order of CORESET index) from the highest CORESET index among CORESETs associated with SS sets without linkage (CORESETs without linkage).

[0291] [Option 3] First, the selection is made in order of whether or not the set is linked, then in order of the monitoring period of the SS set, and then in order of the CORESET index.

[0292] For each TRP, the UE selects N RSs provided for the active TCI state for PDCCH reception in the CORESET associated with the linked SS set (linked CORESET), and then determines the RSs from the CORESET associated with the SS set without linkage (CORESET without linkage).

[0293] The UE first determines the RS in the CORESET associated with the SS set having the shortest monitoring period among the linked SS sets (CORESETs associated with the linked SS sets) in order of the shortest monitoring period (in ascending order of the monitoring period), and then determines the RS in the CORESET order of the highest CORESET index (in descending order of the CORESET index).The UE first determines the RS in the CORESET associated with the SS set having the shortest monitoring period among the CORESETs associated with the SS sets having no linkage (CORESETs having no linkage) in order of the shortest monitoring period (in ascending order of the monitoring period), and then determines the RS in the CORESET order of the highest CORESET index (in descending order of the CORESET index).

[0294] [Variation 1] In option 1 / 2, the UE first determines the RS from the CORESET / SS set that has no linkage, and then determines the RS from the linked CORESET / SS set.

[0295] [Variation 2] In option 1 / 2, the UE determines the RS only from the linked CORESET / SS set, or only from the CORESET / SS set without linkage.

[0296] [Variation 3] In Option 1 / 2, the UE determines the RS by considering the following factors: the monitoring period of the SS set, the CORESET index, and whether the CORESET / SS set has linkage. The priority (order) of these factors may be interchanged.

[0297] <<Aspect 2-6>> In this embodiment, Case B (Case 1+3) is assumed.

[0298] The question arises as to how to determine the implicit RS for RLM / BFD.

[0299] The implicit RS determination for at least one of RLM and BFD per cell may be similar to aspects 2-4.

[0300] The implicit RS determination for BFD per TRP may be similar to aspects 2-5.

[0301] Aspect 2-7 In this embodiment, Case C (Case 2+3) is assumed.

[0302] The question arises as to how to determine the implicit RS for RLM / BFD.

[0303] The implicit RS determination for at least one of RLM and per-cell BFD may be based on aspects 2-1 and 2-4, and may further follow either of options 1 and 2 below.

[0304] [Option 1] A CORESET with two TCI states has a higher priority than a linked CORESET for repetition. The UE selects the N RSs provided for active TCI states for PDCCH reception first from a CORESET with two TCI states, then from a linked CORESET associated with a linked SS set for repetition, then from a CORESET with one TCI state or a CORESET with no linkage.

[0305] [Option 2] A CORESET with two TCI states has a lower priority than a linked CORESET for repetition. The UE selects the N RSs provided for active TCI states for PDCCH reception first from the linked CORESET associated with the linked SS set for repetition, then from the CORESET with two TCI states, and then from the CORESET with one TCI state or no linkage.

[0306] The implicit RS determination for BFD per TRP is based on aspects 2-2 and 2-5 and may further follow either of options 1 and 2 below.

[0307] [Option 1] A CORESET with two TCI states has a higher priority than a linked CORESET for repetition. For each TRP, the UE selects N RSs provided for active TCI states for PDCCH reception in the following order: first, from a CORESET with two TCI states, then from a linked CORESET associated with a linked SS set for repetition, then from a CORESET with one TCI state or a CORESET with no linkage.

[0308] [Option 2] A CORESET with two TCI states has a lower priority than a linked CORESET for repetition. For each TRP, the UE selects N RSs provided for active TCI states for PDCCH reception in the following order: first, from the linked CORESET associated with the linked SS set for repetition, then from the CORESET with two TCI states, then from the CORESET with one TCI state or no linkage.

[0309] [Variations] In the implicit RS determination for at least one of RLM and per-cell BFD, or the implicit RS determination for per-TRP BFD, the UE determines the RS by considering factors such as the monitoring period of the SS set, the CORESET index, the number of TCI states for the CORESET, and whether the CORESET / SS set has linkage. The priorities (orders) of these factors may be interchanged.

[0310] The UE capability to indicate whether or not it supports implicit RS determination for BFD per cell / per TRP may be specified in the specification.

[0311] <<Aspect 2-8>> Switching between aspects 2-1 and 2-2, or switching between aspects 2-4 and 2-5, that is, switching between per-cell BFR and per-TRP BFR, will now be described.

[0312] The switching may be configured by higher layer signaling. For example, if the UE is not explicitly configured / provided with BFD-RS, the UE may follow at least one of the following actions 1 and 2. [Operation 1] If the UE is configured with per-TRP BFR by higher layer signaling, the UE (implicitly) derives the BFD-RS for per-TRP BFR (implicit RS determination). [Operation 2] If the UE is configured for per-cell BFR by higher layer signaling, the UE (implicitly) derives the BFD-RS for per-cell BFR (implicit RS determination).

[0313] <Third embodiment> An embodiment for solving the above-mentioned problem 3 will be described.

[0314] When multiple QCL type D RSs used to receive multiple downlink signals (e.g., PDCCH, PDSCH, SSB, CSI-RS) collide, the UE may control reception of one or more downlink signals that use the one or more QCL type D RSs among the multiple downlink signals, based on information related to the PDCCH / CORESET (e.g., RRC IE / MAC CE).

[0315] For each case, the first embodiment may be applied.

[0316] For case 3 (cases 1 / 2 do not occur, only case 3 occurs), an extension to the TDM repetition case is an issue. For example, it is an issue of whether to give a higher priority to the linked CORESET for the TDM PDCCH repetition.

[0317] For Case B (Case 1+3), an extension to the FDM iteration case becomes an issue when one high priority CORESET / QCL type D is determined for each CORESET pool index.

[0318] For Case C (Case 2+3), the priority between a linked CORESET for an FDM iteration and a CORESET with two TCI states is an issue.

[0319] <<Aspect 3-1>> In this aspect, case 3 is assumed. It may be assumed that the UE is capable of reception using only one QCL type D. It may be assumed that one highest priority CORESET / QCL type D is determined in one monitoring occasion.

[0320] Handling of QCL Type D collisions is an issue, e.g. whether linked CORESETs for TDM PDCCH repetitions are given higher priority.

[0321] If there are multiple CORESETs with different QCL types D within overlapping monitoring occasions, the UE may follow one of the following options 0 to 1 to determine which CORESET the UE should monitor: The UE may monitor the CORESET with the highest priority and the CORESET with the same QCL type D as the CORESET with the highest priority.

[0322] [Option 0] Same rules as Rel.16.

[0323] First, CSS sets have a higher priority than USS sets, and second, SS sets with lower indices have a higher priority than SS sets with higher indices.

[0324] [Option 1] First, CSS sets have a higher priority than USS sets. Second, if one of the linked CORESET / SS sets was monitored in an earlier (past) monitoring occasion, then in a later (future) monitoring occasion, the CORESET / SS set linked to that CORESET / SS set will have a higher priority than other CORESET / SS sets.

[0325] Next, for multiple CORESET / SS sets that have the same level of priority based on this rule, at least one of the following options 1-1 and 1-2 may be applied. [[Option 1-1]] An SS set with a lower ID has a higher priority than an SS set with a higher ID. [[Option 1-2]] An SS set with a lower ID in an SS set pair has a higher priority than an SS set with a higher ID in the SS set pair. The ID of an SS set pair may be the lower SS set ID of a pair of linked SS sets.

[0326] The CSS set has a higher priority than the USS set. Different options may be applied to the CSS set and the USS set, respectively, among options 0 and 1. For example, option 0 may be applied to the CSS set and option 1 may be applied to the USS set.

[0327] [Variations] In handling PDCCH QCL Type D collisions, the following factors are considered: whether the SS set is a CSS set or a USS set; whether the SS set ID is higher or lower; whether the ID of the SS set pair is higher or lower; whether the SS set / CORESET is linked for recurrence; whether one of the linked SS sets / CORESETs was monitored in a previous monitoring occasion. The priority (order) of these factors may be interchanged.

[0328] FIG. 8 is a diagram showing an example of Aspect 3-1. CORESET#a is associated with USS set#a. CORESET#b is associated with USS set#b. CORESET#x is associated with USS set#x. CORESET#y is associated with USS set#y. CORESET#a and #b overlap in frequency. CORESET#x and #y overlap in frequency. CORESET#a and #x overlap in time. CORESET#b and #y overlap in time. CORESET#a and #b (USS sets#x and #y) have no linkage. CORESET#x and #y (USS sets#x and #y) are linked to each other for repetition. CORESET#a, #b, #x, #y are associated with different QCL types D.

[0329] In this example, it is assumed that USS set ID#a > USS set ID#x and USS set ID#b < USS set ID#y.

[0330] Based on Option 0, in a previous monitoring occasion, CORESET#x / USS set#x is monitored, and in a subsequent monitoring occasion, CORESET#b / USS set#b is monitored.

[0331] Based on Option 1, in a previous monitoring occasion, CORESET#x / USS set#x is monitored, and in a subsequent monitoring occasion, CORESET#y / USS set#y is monitored.

[0332] 《Aspect 3-2》 In this aspect, Case B (Case 1+3) is assumed. Considering FDM PDCCH repetition, linked CORESETs may be associated with different CORESET pool indices. It may be assumed that the UE is capable of reception using two QCL types D. It may be assumed that for each CORESET pool index, one highest priority CORESET / QCL type D is determined.

[0333] Handling of QCL Type D collisions is an issue, e.g., whether higher priority is given to linked CORESETs for FDM PDCCH repetitions.

[0334] If there are multiple CORESETs with different QCL types D within overlapping monitoring occasions, the UE may follow one of the following options 0 to 2 to determine which CORESET the UE should monitor: The UE may monitor the CORESET with the highest priority and the CORESET with the same QCL type D as the CORESET with the highest priority.

[0335] [Option 0] For multiple CORESETs with each CORESET pool index, first, the CSS set has a higher priority than the USS set, and second, the SS set with a lower index has a higher priority than the SS set with a higher index.

[0336] [Option 1] For multiple CORESETs with each CORESET pool index, first, a CSS set has a higher priority than a USS set, and second, a linked CORESET / SS set has a higher priority than a CORESET / SS set without linkage.

[0337] Next, for multiple CORESET / SS sets that have the same level of priority based on this rule, at least one of the following options 1-1 and 1-2 may be applied. [[Option 1-1]] An SS set with a lower ID has a higher priority than an SS set with a higher ID. [[Option 1-2]] An SS set with a lower ID in an SS set pair has a higher priority than an SS set with a higher ID in the SS set pair. The ID of an SS set pair may be the lower SS set ID of a pair of linked SS sets.

[0338] [Option 2] For multiple CORESETs with each CORESET pool index, first, a CSS set has a higher priority than a USS set, and second, a SS set with a lower ID has a higher priority than a SS set with a higher ID.

[0339] Here, if the CORESET pool index = 0 (or 1) and one of the linked SS sets / CORESETs (SS set #x / CORESET #x) is monitored, then for the CORESET pool index = 1 (or 0), this priority rule is ignored and the other of the linked SS sets / CORESETs (SS set #y / CORESET #y) has a higher priority than the other SS sets / CORESETs.

[0340] Next, for multiple CORESET / SS sets that have the same level of priority based on this rule, at least one of the following options 1-1 and 1-2 may be applied. [[Option 1-1]] An SS set with a lower ID has a higher priority than an SS set with a higher ID. [[Option 1-2]] An SS set with a lower ID in an SS set pair has a higher priority than an SS set with a higher ID in the SS set pair. The ID of an SS set pair may be the lower SS set ID of a pair of linked SS sets.

[0341] The CSS set has a higher priority than the USS set. Different options from options 0 to 2 may be applied to the CSS set and the USS set, respectively. For example, option 0 may be applied to the CSS set and option 1 may be applied to the USS set.

[0342] [Variations] In handling PDCCH QCL Type D collisions, the following factors are considered: whether the SS set is a CSS set or a USS set; whether the SS set ID is higher or lower; whether the ID of the SS set pair is higher or lower; whether the SS set / CORESET is linked for FDM repetition; whether one of the linked SS sets / CORESETs is monitored. The priority (order) of these factors may be interchanged.

[0343] Figure 9 is a diagram showing an example of aspect 3-2. CORESET#a is associated with USS set#a. CORESET#b is associated with USS set#b. CORESET#x is associated with USS set#x. CORESET#y is associated with USS set#y. CORESET#a and #x are associated with CORESET pool index=0. CORESET#b and #y are associated with CORESET pool index=1. CORESET#a, #x, #b, #y overlap in frequency. CORESET#a and #b (USS sets#x and #y) have no linkage. CORESET#x and #y (USS sets#x and #y) are linked to each other for repetition. CORESET#a, #b, #x, #y are associated with different QCL types D.

[0344] In the first example, assume USS set ID#a > USS set ID#x and USS set ID#b < USS set ID#y.

[0345] Based on Option 0, for CORESET pool index = 0, CORESET#x / USS set #x is monitored, and for CORESET pool index = 1, CORESET#b / USS set #b is monitored.

[0346] Based on Option 1, for CORESET pool index = 0, CORESET#x / USS set #x is monitored, and for CORESET pool index = 1, CORESET#y / USS set #y is monitored.

[0347] Based on Option 2, for CORESET pool index = 0, CORESET#x / USS set #x is monitored, and for CORESET pool index = 1, CORESET#y / USS set #y is monitored.

[0348] In the second example, assume USS set ID#a < USS set ID#x and USS set ID#b < USS set ID#y.

[0349] Based on Option 0, for CORESET pool index = 0, CORESET#a / USS set #a is monitored, and for CORESET pool index = 1, CORESET#b / USS set #b is monitored.

[0350] Based on Option 1, for CORESET pool index = 0, CORESET#x / USS set #x is monitored, and for CORESET pool index = 1, CORESET#y / USS set #y is monitored.

[0351] According to option 2, for CORESET pool index=0, CORESET#a / USS set#a is monitored, and for CORESET pool index=1, CORESET#b / USS set#b is monitored.

[0352] <<Aspect 3-3>> In this aspect, Case C (Case 2+3) is assumed. The UE may be assumed to be capable of reception using two QCL types D. It may be assumed that two higher priority CORESETs / QCL types D are determined at each monitoring occasion.

[0353] Handling QCL type D collisions is an issue, e.g., whether a linked CORESET for FDM PDCCH repetitions or a CORESET with two TCI states has a higher priority.

[0354] If there are multiple CORESETs with different QCL types D within overlapping monitoring occasions, to determine which CORESET the UE should monitor, the UE may follow the following operations: The UE may monitor the CORESET with the highest priority and the CORESET with the same QCL type D as the highest priority CORESET.

[0355] [Operation] The embodiment Y described below may be applied to the priority between a CORESET with two TCI states and a CORESET with one TCI state, and the priority between a linked CORESET for FDM repetition and a CORESET with no linkage.

[0356] Between a CORESET with two TCI states and a linked CORESET / SS set for FDM repetition, either of the following options 1 and 2 may be applied. [[Option 1]] A CORESET with two TCI states has a higher priority than a linked CORESET / SS set for FDM repetitions. [[Option 2]] A linked CORESET / SS set for an FDM repetition has a higher priority than a CORESET with two TCI states.

[0357] [Variations] In handling PDCCH QCL Type D collisions, the following factors are considered: whether the SS set is a CSS set or a USS set; whether the SS set ID is higher or lower; whether the ID of the SS set pair is higher or lower; whether the CORESET has two TCI states activated; whether the SS set / CORESET is linked for FDM repetition; whether one of the linked SS sets / CORESETs is monitored. The priority (order) of these factors may be interchanged.

[0358] <<Aspect 3-4>> At least one of the following scenarios 1 to 3 may be assumed.

[0359] [Assumption 1] Case 3 is assumed. Coexistence of TDM repetition and FDM repetition may also be assumed.

[0360] The UE may be assumed to be capable of reception using two QCL types D. At each monitoring occasion, two higher priority CORESET / QCL types D may be assumed to be determined.

[0361] Handling QCL Type D collisions is an issue, e.g., whether the linked CORESET for a TDM PDCCH repetition has a higher priority.

[0362] Aspect 3-1 may be applied. It is assumed that two high priority CORESET / SS sets are determined at each monitoring occasion.

[0363] To determine the priority, the below-described embodiment Y for FDM repetition may be applied.

[0364] [Assumption 2] Case B (Case 1 + 3) is assumed.

[0365] The UE may be assumed to be capable of reception using two QCL types D. At each monitoring occasion, it may be assumed that one highest priority CORESET / QCL type D is determined.

[0366] Handling QCL Type D collisions is an issue, e.g., whether the linked CORESET for a TDM PDCCH repetition has a higher priority.

[0367] Aspect 3-1 may be applied. It is assumed that one highest priority CORESET / SS set is determined in each monitoring occasion.

[0368] The priority may be determined by applying the embodiment X described below. Furthermore, the aspect 3-2 may also be applied.

[0369] [Assumption 3] Case C (Case 2 + 3) is assumed.

[0370] The UE may be assumed to be capable of reception using two QCL types D. At each monitoring occasion, it may be assumed that the two highest priority CORESET / QCL types D are determined.

[0371] Handling QCL Type D collisions is an issue, e.g., whether the linked CORESET for a TDM PDCCH repetition has a higher priority.

[0372] Aspect 3-1 may also be applied. It is assumed that at each monitoring occasion, two highest priority CORESET / SS sets are determined.

[0373] The priority may be determined by applying the embodiment Y described below. Furthermore, the aspect 3-3 may be applied.

[0374] Aspects 3-5 At least one of aspects 3-1 to 3-4 may be applied to handling QCL Type D collisions between PDCCHs and other channels / RSs (e.g., SSB / PDSCH / CSI-RS) in addition to QCL Type D collisions between PDCCHs and other PDCCHs.

[0375] For example, in some cases, a linked CORESET / SS set for a TDM / FDM PDCCH repetition may have a higher priority than other channels / RS (e.g., SSB / PDSCH / CSI-RS) when a collision occurs. Alternatively, a linked CORESET / SS set for a CSS set for a TDM / FDM PDCCH repetition may have a higher priority than other channels / RS (e.g., SSB / PDSCH / CSI-RS) when a collision occurs.

[0376] For example, in some cases, a CORESET with two TCI states may have higher priority than other channels / RSs (e.g., SSB / PDSCH / CSI-RS) when a collision occurs. Alternatively, a CORESET with two TCI states for a CSS set may have higher priority than other channels / RSs (e.g., SSB / PDSCH / CSI-RS) when a collision occurs.

[0377] The UE capabilities for each case may be specified in the specification.

[0378] According to this embodiment, the prioritized CORESET / QCL type D becomes clear in the case of a QCL type D collision.

[0379] <Fourth embodiment> In each embodiment, a higher layer parameter (RRC information element) / UE capability corresponding to at least one function (feature) may be defined. The UE capability may indicate whether the function is supported.

[0380] A UE for which a higher layer parameter corresponding to the function is configured may perform the function. Alternatively, it may be specified that "a UE for which a higher layer parameter corresponding to the function is not configured does not perform the function (for example, applies the operation of Rel. 15 / 16)."

[0381] A UE that reports a UE capability indicating that it supports the function may perform the function. It may also be specified that "a UE that does not report a UE capability indicating that it supports the function shall not perform the function (e.g., apply the behavior of Rel. 15 / 16)."

[0382] If the UE reports a UE capability indicating that it supports the function and the corresponding upper layer parameter is configured, the UE may perform the function. It may also be specified that "if the UE does not report a UE capability indicating that it supports the function or if the corresponding upper layer parameter is not configured, the UE shall not perform the function (e.g., apply the behavior of Rel. 15 / 16)."

[0383] The UE capabilities may indicate at least one of the following: · Whether or not to support Case A. · Whether or not to support Case B. · Whether or not to support case C. · Whether or not to support Case D. · Whether or not to support option 2-1 / 2-2 of aspect 1-1. ·Whether or not to support options 2-1 / 2-2 / 2-3 of aspect 1-2. · Whether or not to support option 2-1 / 2-2 of aspect 1-3. ·Whether to support implicit RS determination for BFD per cell / per TRP.

[0384] The above UE capabilities / upper layer parameters allow the UE to achieve the above functions while maintaining compatibility with existing specifications.

[0385] (Embodiment X) The following embodiments X1 to X5 are described assuming that they are applied when the UE supports simultaneous reception of two or more different QCL type D channels / signals, but may also be applied in other cases.

[0386] <Embodiment X1> Embodiment X1 relates to collision of PDCCH and PDSCH. The PDCCH and PDSCH in the description of embodiment X1 may refer to PDCCH and PDSCH that overlap each other in time.

[0387] The case of mDCI-based MTRP (embodiment X1.1) and the case of sDCI-based MTRP (embodiment X1.2) will be described.

[0388] [Embodiment X1.1] For mDCI-based MTRP, the above-mentioned priority rule between PDCCH and PDSCH may be applied only when the PDCCH and PDSCH relate to the same CORESET pool index if the CORESET pool index is configured for CORESET.

[0389] If the PDCCH and PDSCH relate to different CORESET pool indices, no priority rules are required and a UE capable of simultaneous reception of two different QCL type D channels / signals may receive both the PDCCH and PDSCH for these different QCL type D channels / signals.

[0390] In addition, the UE may determine the association between the CORESET pool index and the PDSCH based on the relationship between the CORESET pool index and the PDCCH that schedules the PDSCH, or based on the relationship between the CORESET pool index and the PDCCH that the PDSCH uses as a reference for the QCL (for example, referenced as a default QCL).

[0391] For example, the UE may determine that the CORESET pool index associated with a PDSCH is the CORESET pool index associated with a PDCCH that schedules the PDSCH, or may determine that the CORESET pool index associated with a PDCCH that is referred to as the default QCL for the PDSCH.

[0392] 10 is a diagram illustrating an example of an environment of mDCI-based MTRP for explaining the operation of embodiment X1.1. In this example, a UE uses mDCI-based MTRP using TRP1 and TRP2. TRP1 corresponds to CORESET pool index=0, and TRP2 corresponds to CORESET pool index=1. TRP1 transmits PDCCH1 and PDSCH1 to the UE. TRP2 transmits PDCCH2 and PDSCH2 to the UE.

[0393] It should be noted that PDCCH1 is not limited to a PDCCH (DCI) for scheduling PDSCH1, but may refer to any PDCCH transmitted from TRP1. It should be noted that PDCCH2 is not limited to a PDCCH (DCI) for scheduling PDSCH2, but may refer to any PDCCH transmitted from TRP2.

[0394] 11A and 11B are diagrams illustrating an example of priority rules when a PDCCH and a PDSCH collide according to embodiment X1.1. As shown in FIG. 10, PDCCH1 and PDSCH1 correspond to TRP1 (CORESET pool index=0), and PDCCH2 and PDSCH2 correspond to TRP2 (CORESET pool index=1). In addition, PDSCH1 or PDSCH2 in this example follows the default TCI state.

[0395] In Figure 11A, PDCCH1 and PDSCH1 corresponding to the same CORESET pool index have different QCL types D and some symbols overlap. In this case, the UE receives PDCCH1 preferentially and does not need to receive PDSCH1 that overlaps with PDCCH1 (shown in black in the figure). The UE may receive the part of PDSCH1 that does not overlap with PDCCH1.

[0396] 11B, PDCCH1 and PDSCH2 corresponding to different CORESET pool indexes have different QCL types D and some symbols overlap. In this case, the UE may receive PDSCH2 that overlaps with PDCCH1 simultaneously with PDCCH1.

[0397] [Embodiment X1.2] For sDCI-based MTRP, if multiple (e.g., two) TCI states apply for the PDSCH (e.g., indicated by DCI or by a default QCL) and the QCL type D channel / signal of the DMRS of the PDCCH is the same as the QCL type D channel / signal of one of the multiple TCI states for the DMRS of the PDSCH, no priority rule is required and a UE capable of simultaneous reception of two different QCL type D channels / signals may receive both the PDCCH and PDSCH for these different QCL type D channels / signals.

[0398] When multiple TCI states apply for the PDSCH, and the QCL type D channel / signal of the DMRS of the PDCCH is different from the QCL type D channel / signal of any of the multiple TCI states for the DMRS of the PDSCH, the UE may comply with at least one of the following: (1) Prioritizing reception of PDCCH and not receiving PDSCH in symbols that overlap with the PDCCH; (2) Prioritizing reception of the PDCCH and the PDSCH associated with one of the plurality of TCI states, and not receiving PDSCHs associated with the remaining TCI states in symbols that overlap with the PDCCH.

[0399] The prioritized TCI state for the PDSCH in (2) above may be defined in advance by a specification, may be configured / activated in the UE by higher layer signaling (e.g., RRC, MAC CE), or may be determined based on UE capabilities. The prioritized TCI state for the PDSCH in (2) above may be a TCI state whose TCI state ID corresponds to a specific value (e.g., minimum value, maximum value) among the plurality of TCI states.

[0400] 12 is a diagram illustrating an example of an environment of sDCI-based MTRP for explaining the operation of embodiment X1.2. In this example, a UE uses sDCI-based MTRP using TRP1 and TRP2. TRP1 transmits a PDCCH and a PDSCH to the UE. TRP2 transmits a PDSCH (scheduled by the PDCCH from TRP1) to the UE.

[0401] Note that PDCCH1 is not limited to a PDCCH (DCI) for scheduling PDSCH1, and may refer to any PDCCH transmitted from TRP1.

[0402] If the TCI codepoint of the DCI carried by the PDCCH indicates a set of two or more TCI states, the UE receives PDSCHs corresponding to different TCI states (e.g., transmitted from different TRPs) as shown in the figure. In this example, it is assumed that the PDSCH from TRP1 corresponds to TCI state 1, and the PDSCH from TRP2 corresponds to TCI state 2.

[0403] 13A and 13B are diagrams showing an example of priority rules when a PDCCH and a PDSCH collide according to embodiment X1.2. As shown in this diagram, the PDCCH and the PDSCH1 corresponding to TCI state 1 correspond to TRP1, and the PDSCH corresponding to TCI state 2 corresponds to TRP2. It is assumed that the QCL type D of the PDCCH is different from the QCL type D of any of the PDSCHs (QCL type D in TCI states 1 and 2). In addition, the PDSCH in this example may or may not follow the default TCI state.

[0404] 13A, the PDCCH has different QCL types D for both the PDSCH corresponding to TCI state 1 and the PDSCH2 corresponding to TCI state 2, and some symbols overlap. In this case, the UE receives the PDCCH with priority and does not need to receive the PDSCHs that overlap with the PDCCH (shown in black in the figure). The UE may receive the PDSCHs that do not overlap with the PDCCH.

[0405] 13B, the PDCCH has different QCL types D for both the PDSCH corresponding to TCI state 1 and the PDSCH2 corresponding to TCI state 2, and some symbols overlap. In this example, it is assumed that the TCI state of the prioritized PDSCH is the TCI state with the largest TCI state ID value among multiple TCI states specified for the PDSCH.

[0406] In this case, the UE may preferentially receive the PDCCH and the PDSCH corresponding to TCI state 2, and may not receive the PDSCH (shown in black in the figure) that overlaps with the PDCCH and corresponds to TCI state 1. The UE may receive each PDSCH that does not overlap with the PDCCH.

[0407] According to the embodiment X1 described above, it is possible to appropriately deal with collisions between PDCCH and PDSCH.

[0408] <Embodiment X2> Embodiment X2 relates to collision of CSI-RS and PDCCH (CORESET). The CSI-RS and PDCCH in the description of embodiment X2 may refer to CSI-RS and PDCCH that overlap each other in time. The PDCCH in the present disclosure may be interchangeably read as CORESET.

[0409] The case of mDCI-based MTRP (embodiment X2.1) and the case of sDCI-based MTRP (embodiment X2.2) will be described.

[0410] [Embodiment X2.1] For mDCI-based MTRP, if a CORESET pool index is configured for the CORESET, it may be supported to configure the relationship between the CSI-RS resource or NZP-CSI-RS resource set and the CORESET pool index directly (explicitly) or indirectly (implicitly).

[0411] For CSI-RS resources associated with an NZP-CSI-RS resource set where the upper layer parameter for repetition ('repetition') is set to 'on', the UE may not assume that a CSI-RS associated with the same CORESET pool index is configured for a symbol configured to monitor a CORESET associated with a certain CORESET pool index. The CSI-RS resource may be located in overlapping symbols with a CORESET associated with a different CORESET pool index.

[0412] For a CSI-RS associated with an NZP-CSI-RS resource set where the upper layer parameter for repetition ('repetition') is on, the UE may simultaneously receive the CSI-RS and PDCCH associated with different CORESET pool indices.

[0413] On the other hand, for an NZP-CSI-RS resource set where 'repetition' is not 'on', if the CSI-RS and CORESET are associated with the same CORESET pool index, the UE may assume that the CSI-RS and the DMRS of the PDCCH transmitted in all search space sets associated with the CORESET are QCLs of "QCL Type D". If the CSI-RS and CORESET are associated with different CORESET pool indexes, the CSI-RS and the DMRS of the PDCCH for the CORESET may be allowed to have different "QCL Type D".

[0414] [Embodiment X2.2] For sDCI-based MTRP, the existing priority rules of Rel. 16 mentioned above may apply, as in the case of single TRP.

[0415] If a UE supports simultaneous reception of a total of X QCLs (channels / signals), and if the total number of different QCLs for CSI-RS and PDCCH in the same OFDM symbol is X or less, the UE may receive all of the CSI-RS and PDCCH; otherwise, the UE may not receive all of the CSI-RS and PDCCH. If the UE does not receive all of the CSI-RS and PDCCH, the UE may drop (not receive) at least one of a portion of the CSI-RS and a portion of the PDCCH so that the number of transmissions of different QCLs is X or less.

[0416] A UE that supports simultaneous reception of a total of X QCLs (channels / signals) may assume (expect) that the total number of different QCLs for CSI-RS and PDCCH in the same OFDM symbol will not exceed X.

[0417] The UE may receive all of the CSI-RS and PDCCH for different QCLs in the same OFDM symbol if they belong to the same group for a first group-based beam report, where the first group-based beam report may be defined by beams of the same group being simultaneously received by the UE. The first group-based beam report may be a group-based beam report for Rel. 16 / 17.

[0418] The UE may assume that for CSI-RS and PDCCH belonging to different groups for the first group-based beam report, the existing priority rules of Rel. 16 mentioned above apply.

[0419] The UE may receive all of the CSI-RS and PDCCH for different QCLs in the same OFDM symbol if the CSI-RS and PDCCH belong to different groups for second group-based beam reporting, where the second group-based beam reporting may be defined by beams of different groups being simultaneously received by the UE. The second group-based beam reporting may be group-based beam reporting for Rel. 17.

[0420] The UE may assume that for CSI-RS and PDCCH belonging to the same group for the second group-based beam report, the existing priority rules of Rel. 16 mentioned above apply.

[0421] According to the above-described embodiment X2, it is possible to appropriately deal with collisions between CSI-RS and PDCCH.

[0422] <Embodiment X3> Embodiment X3 relates to collision of CSI-RS and SSB. The CSI-RS and SSB in the description of embodiment X3 may refer to CSI-RS and SSB that overlap each other in time.

[0423] The case of mDCI-based MTRP (embodiment X3.1) and the case of sDCI-based MTRP (embodiment X3.2) will be described.

[0424] [Embodiment X3.1] For mDCI-based MTRP, when a CORESET pool index is configured for CORESET, it may be supported to configure the relationship between the CSI-RS resource or NZP-CSI-RS resource set and the CORESET pool index directly (explicit) or indirectly (implicit), and it may be supported to configure the relationship between the SSB and the CORESET pool index directly (explicit) or indirectly (implicit).

[0425] If a CSI-RS resource is configured in the same OFDM symbol as an SSB, and the CSI-RS and the SSB are associated with the same CORESET pool index, the UE may assume that the CSI-RS and the SSB are QCLs with "QCL type D".

[0426] Furthermore, if a CSI-RS resource is configured in the same OFDM symbol as an SSB, and the CSI-RS and the SSB are associated with different CORESET pool indices, the UE may assume that the CSI-RS and the SSB have restrictions on QCL type D (for example, the CSI-RS and the SSB may be allowed to correspond to different "QCL types D").

[0427] In this disclosure, indirectly setting a relationship between a certain channel / signal and a CORESET pool index may mean, for example, deriving a relationship based on a QCL assumption or a TCI state. For example, when CORESET#2 corresponding to CORESET pool index#1 is set to TCI state#3, the fact that SSB#4 is the source reference signal (reference reference signal) of TCI state#3 implicitly means that SSB#4 is related to CORESET pool index#1.

[0428] [Embodiment X3.2] For sDCI-based MTRP, the existing priority rules of Rel. 16 mentioned above may apply, as in the case of single TRP.

[0429] Furthermore, for the sDCI-based MTRP, the content in embodiment X2.2 may be used in which "PDCCH" is replaced with "SSB." For example, if a UE supports simultaneous reception of a total of X QCLs (channels / signals), and if the total number of different QCLs for CSI-RS and SSB in the same OFDM symbol is less than or equal to X, the UE may receive all of the CSI-RS and SSB; otherwise, the UE may not receive all of the CSI-RS and SSB.

[0430] According to the embodiment X3 described above, it is possible to appropriately deal with collisions between CSI-RS and SSB.

[0431] <Embodiment X4> Embodiment X4 relates to collision of a PDSCH and an SSB. The PDSCH and the SSB in the description of embodiment X4 may refer to a PDSCH and an SSB that overlap each other in time. In embodiment X4, the PDSCH may be interchangeably read as a DMRS for the PDSCH.

[0432] The case of mDCI-based MTRP (embodiment X4.1) and the case of sDCI-based MTRP (embodiment X4.2) will be described.

[0433] [Embodiment X4.1] For mDCI-based MTRP, if a CORESET pool index is configured for CORESET, it may be supported to configure the relationship between SSB and CORESET pool index directly (explicitly) or indirectly (implicitly).

[0434] If a UE receives a DMRS for a PDSCH in the same OFDM symbol as an SSB, and the PDSCH and the SSB are associated with the same CORESET pool index, the UE may assume that the PDSCH and the SSB are QCLs with "QCL type D".

[0435] Additionally, if a UE receives a DMRS for a PDSCH in the same OFDM symbol as an SSB, the UE may receive both the PDSCH and the SSB for these different QCL type D channels / signals if the PDSCH and the SSB are associated with different CORESET pool indices.

[0436] The relationship between the CORESET pool index and the PDSCH may be determined in the same manner as in embodiment X1.1.

[0437] [Embodiment X4.2] For sDCI-based MTRP, if multiple (e.g., two) TCI states apply for a PDSCH (e.g., indicated by DCI or by a default QCL) and the UE receives DMRS and SSB for a PDSCH in the same OFDM symbol, the channel / signal of QCL type D in one of the multiple TCI states for the PDSCH may be assumed to be QCL with SSB and "QCL type D".

[0438] In other words, the UE may prioritize reception of an SSB and a PDSCH associated with one of the plurality of TCI states. The UE may not receive PDSCHs associated with the remaining TCI states in symbols that overlap with the SSB. The prioritized TCI state for the PDSCH may be a TCI state among the plurality of TCI states whose TCI state ID corresponds to a specific value (e.g., the smallest or largest value).

[0439] According to the embodiment X4 described above, it is possible to appropriately deal with collisions between PDSCH and SSB.

[0440] <Embodiment X5> Embodiment X5 relates to collision of A-CSI-RS and other DL signals. The A-CSI-RS and other DL signals in the description of embodiment X5 may refer to A-CSI-RS and other DL signals that overlap each other in time.

[0441] The A-CSI-RS in embodiment X5 corresponds to an A-CSI-RS whose scheduling offset is smaller than a threshold determined based on the beam switch timing reported by the UE. Furthermore, the other DL signal in embodiment X5 corresponds to "the other DL signal" defined in the existing Rel. 15 / 16. Furthermore, the PDSCH in embodiment X5 refers to the PDSCH corresponding to the other DL signal.

[0442] The case of mDCI-based MTRP (embodiment X5.1) and the case of sDCI-based MTRP (embodiment X5.2) will be described.

[0443] [Embodiment X5.1] For mDCI-based MTRP, if a CORESET pool index is configured for a CORESET, it may be supported to configure the relationship between A-CSI-RS resources or A-CSI-RS resource sets and CORESET pool index directly (explicitly) or indirectly (implicitly).

[0444] If the A-CSI-RS and other DL signals are associated with the same CORESET pool index, the UE may prioritize the QCL for the other DL signals (e.g., apply the QCL for the other DL signals to the reception of the A-CSI-RS), otherwise it may receive both the A-CSI-RS and the other DL signals with different QCL type D.

[0445] The relationship between the CORESET pool index and the PDSCH may be determined in the same manner as in embodiment X1.1.

[0446] [Embodiment X5.2] For sDCI-based MTRP, if multiple (e.g., two) TCI states apply for the PDSCH (e.g., as indicated by the DCI or by the default QCL) and the UE receives DMRS and A-CSI-RS for the PDSCH in the same OFDM symbol, the UE may follow at least one of the following: If the QCL type D of the A-CSI-RS is the same as one of the multiple TCI states, receive both the A-CSI-RS and the PDSCH. If the QCL type D of the A-CSI-RS is different from any of the plurality of TCI states, the QCL assumption for the specific TCI state is applied to the reception of the A-CSI-RS and the PDSCH, and the QCL assumptions for the remaining TCI states among the plurality of TCI states are applied to the reception of the remaining PDSCH. The specific TCI state may be a TCI state among the plurality of TCI states whose TCI state ID corresponds to a specific value (e.g., the minimum value, the maximum value).

[0447] Furthermore, for the sDCI-based MTRP, the content in embodiment X2.2 may be used in which "CSI-RS" is replaced with "A-CSI-RS" and "PDCCH" is replaced with "other DL signals." For example, if a UE supports simultaneous reception of a total of X QCLs (channels / signals), and if the total number of different QCLs for the A-CSI-RS and other DL signals in the same OFDM symbol is less than or equal to X, the UE may receive the A-CSI-RS and all of the other DL signals; otherwise, the UE may not receive the A-CSI-RS and all of the other DL signals.

[0448] 14 is a diagram illustrating an example of priority rules when an A-CSI-RS and another DL signal (PDSCH) collide according to embodiment X5.2. In this example, the A-CSI-RS has different QCL types D for both the PDSCH corresponding to TCI state 1 and the PDSCH2 corresponding to TCI state 2, and some symbols overlap. It is assumed that the QCL type D of the A-CSI-RS is different from the QCL type D of either PDSCH (QCL type D in TCI states 1 and 2). Furthermore, the PDSCH in this example may or may not follow the default TCI state.

[0449] In this example, it is assumed that the specific TCI state (the TCI state of the prioritized PDSCH) is the TCI state with the smallest TCI state ID among multiple TCI states designated for the PDSCH that overlaps with the A-CSI-RS.

[0450] In this case, the UE applies TCI state 1 for receiving the A-CSI-RS and the PDSCH in the symbols where the A-CSI-RS and the PDSCH overlap, and also applies TCI state 2 for receiving the PDSCH.

[0451] In this example, TCI state 1 is not applied to the A-CSI-RS in the portion that does not overlap with the PDSCH, but it may be applied.

[0452] According to the above-described embodiment X5, it is possible to appropriately deal with collisions between A-CSI-RS and other DL signals.

[0453] <Modification of Embodiment X> In the above-described embodiment, an example was described in which, when a CORESET pool index is set to CORESET, the same QCL-D is assumed in the UE for different channels / RS related to the same CORESET pool index, and different QCL-Ds are assumed in the UE for different channels / RS related to different CORESET pool indexes.

[0454] In the above-described embodiment, an example has been described in which, when multiple TCI states are applied to a PDSCH, if one of the multiple TCI states and another DL channel / signal correspond to the same QCL-D, the UE receives both the PDSCH and the other DL channel / signal; otherwise, one of the TCI states is given priority.

[0455] It should be noted that at least one of the above-described embodiments may be applied only to UEs that have reported or support a particular UE capability.

[0456] The specific UE capabilities may indicate at least one of the following: -Whether simultaneous reception is supported; Whether or not it supports simultaneous reception of two or more different QCL Type-D channels / signals; · Number of QCLs for simultaneous reception in one OFDM symbol.

[0457] The capability of supporting simultaneous reception may be defined separately for each of the above-described embodiments, or may be defined commonly for several embodiments. For example, a capability indicating support for simultaneous reception of any two of the PDCCH, PDSCH, CSI-RS, SSB, and A-CSI-RS (which may be the same channel / signal) may be defined. Furthermore, for example, a capability indicating support for simultaneous reception of the PDSCH may indicate support for the processing related to simultaneous reception described in the first embodiment (collision of the PDCCH and the PDSCH) and the fourth embodiment (collision of the PDSCH and the SSB).

[0458] The number of QCLs capable of simultaneous reception in one OFDM symbol may be defined per Bandwidth Part (BWP), per CC (Component Carrier), or per band, or may be defined across all CCs or all bands. When defined across all CCs / all bands, the above "one OFDM symbol" may be defined with a specific subcarrier spacing (SCS). The specific SCS may be, for example, a smaller (or larger) SCS among those available (or configured) within all CCs / all bands, such as 15 kHz.

[0459] In addition, the terms "CSI-RS," "A-CSI-RS," "SSB," etc. in this disclosure may be interpreted as Radio Link Monitoring RS (RLM-RS), Beam Failure Detection RS (BFD-RS), RS for beam management, etc.

[0460] Furthermore, at least one of the above-described embodiments may be applied when specific information related to the above-described embodiments is configured in the UE by higher layer signaling (if not configured, for example, the behavior of Rel. 15 / 16 applies). For example, the specific information may be information indicating that different spatial relationships for PUSCH repetitions are enabled, any RRC parameters for a specific release (e.g., Rel. 17), etc.

[0461] Note that each of the above-described embodiments may be applied when (the operation of) multi-TRP or multi-panel is set in the UE, or may be applied when not.

[0462] (Embodiment Y) The following embodiments Y1 to Y2 are described assuming that they are applied when the UE supports simultaneous reception of two or more different QCL type D channels / signals, but may also be applied in other cases.

[0463] In the present disclosure, expressions such as "TCI state A is QCL type D, which is the same as TCI state B," "TCI state A is the same as TCI state B," and "TCI state A is QCL type D with TCI state B" may be read interchangeably.

[0464] <Embodiment Y1> Embodiment Y1 relates to an SFN PDCCH repetition scheme.

[0465] In embodiment Y1, two or more TCI states may be activated per CORESET. The activation of the TCI states for a CORESET may be signaled to the UE using the MAC CE.

[0466] In embodiment Y1, in a case where multiple PDCCHs of different QCL types D collide, the UE determines the PDCCH (CORESET) to monitor based on at least one priority rule shown in embodiments Y1.1 to Y1.3. Each of these will be described below.

[0467] Hereinafter, in this disclosure, the CORESET to be monitored determined based on the priority rule will also be simply referred to as a "prioritized CORESET," a CORESET with the highest priority, or the like.

[0468] [Embodiment Y1.1] The priority rule in embodiment Y1.1 is the same as that in Rel.16 NR. That is, the UE determines the preferred CORESET according to the priority rule that the CSS set is monitored with priority over the USS set, and among SS sets of the same type (CSS or USS), the one with the smaller index (i.e., the one with the smaller cell index; if the cell index is the same, the one with the smaller SS set index) is monitored with priority.

[0469] Embodiment Y1.1 is further divided into the following two categories: Embodiment Y1.1.1: The preferred CORESET has two active TCI states (two QCL type D); Embodiment Y1.1.2: The preferred CORESET has one active TCI state (one QCL type D).

[0470] [[Embodiment Y1.1.1]] For a CORESET other than the preferred CORESET that has one active TCI state, the UE may monitor this CORESET if the one active TCI state is of the same QCL type D as one of the two active TCI states of the preferred CORESET.

[0471] For a CORESET other than the Preferred CORESET that has two active TCI states, the UE may monitor this CORESET if either (1.1.1a) or (1.1.1b) of the following conditions is met: (1.1.1a) The two active TCI states are the same QCL type D as the two active TCI states of the preferred CORESET; (1.1.1b) One of the two active TCI states is the same QCL type D as one of the two active TCI states of the preferred CORESET.

[0472] Note that if the above (1.1.1b) is satisfied, the UE applies only the TCI state that is the same QCL type D as one of the two active TCI states of the preferred CORESET to monitor the above CORESET.

[0473] 15 is a diagram showing an example of a prioritized CORESET and other CORESETs monitored simultaneously in embodiment Y1.1.1. In this example, four CORESETs (CORESETs #1 to #4) overlap in time.

[0474] CORESET#1 corresponds to CSS set index=0 and cell index=0 and has two active TCI states (TCI states #1 and #2).

[0475] CORESET#2 corresponds to USS set index=1 and cell index=0 and has one active TCI state (TCI state#2).

[0476] CORESET#3 corresponds to USS set index=2 and cell index=0 and has two active TCI states (TCI states #1 and #2).

[0477] CORESET#4 corresponds to USS set index=3 and cell index=0 and has two active TCI states (TCI states #1 and #3).

[0478] In the case of this figure, the UE first selects CORESET#1 corresponding to the CSS set as the preferred CORESET. Since CORESET#1 has two active TCI states, the operation is as in embodiment Y1.1.1.

[0479] One TCI state of CORESET#2 is QCL type D, which is the same as TCI state#2 of the preferred CORESET, so the UE monitors CORESET#2.

[0480] The UE monitors CORESET#3 because the two TCI states of CORESET#3 are QCL type D, the same as TCI states #1 and #2 of the preferred CORESET.

[0481] One of the two TCI states of CORESET#4 is QCL type D, the same as TCI state #1 of the preferred CORESET, but the other is QCL type D (TCI state #3), which is different from TCI state #2 of the preferred CORESET. Therefore, a UE that complies with (1.1.1a) above does not monitor CORESET#4. A UE that complies with (1.1.1b) above monitors CORESET#4 by applying only TCI state #1.

[0482] [[Embodiment Y1.1.2]] For embodiment Y1.1.2, a preferred CORESET having one active TCI state that is first determined according to the same priority rules as Rel.16 NR is also referred to as a first preferred CORESET, and a preferred CORESET other than the first preferred CORESET that is subsequently determined is also referred to as a second preferred CORESET. The second preferred CORESET may be referred to as CORESET X.

[0483] One active TCI state of the first priority CORESET may be referred to as a first priority TCI state, and any active TCI state of the second priority CORESET may be referred to as a second priority TCI state.

[0484] Embodiment Y1.1.2 is roughly divided into embodiments Y1.1.2.1 and Y1.1.2.2 depending on the method for determining the second priority CORESET.

[0485] [[Embodiment Y1.1.2.1]] The second preferred CORESET may be determined from the remaining conflicting CORESETs excluding the first preferred CORESET according to the same priority rules as in Rel. 16. That is, the second preferred CORESET may correspond to the CSS set with the smallest index in the cell with the smallest index that contains a CSS set, if any, among the remaining conflicting CORESETs, or the USS set with the smallest index in the cell with the smallest index. The smallest USS set index is determined across all USS sets that have at least one PDCCH candidate in overlapping PDCCH monitoring occasions.

[0486] If a candidate for the second preferred CORESET derived according to the above priority rule has only one active TCI state, and if the active TCI state is the same as the first preferred TCI state, the UE may search for the next candidate (the CORESET corresponding to the SS set / cell with the next smallest index) as a candidate for the second preferred CORESET. That is, for a CORESET that has only one active TCI state, the UE may continue searching for the second preferred CORESET until the active TCI state differs from the first preferred TCI state.

[0487] If the UE finds a CORESET that has only one active TCI state that is different from the first preferred TCI state according to the above priority rules, the UE may determine this active TCI state as the second preferred TCI state and determine this CORESET as the second preferred CORESET.

[0488] In addition, even if a candidate for the second preferred CORESET derived according to the priority rule has only one active TCI state and the active TCI state is the same as the first preferred TCI state, the UE may determine this active TCI state as the second preferred TCI state and determine this candidate as the second preferred CORESET. In this case, since the second preferred CORESET is the same as the first preferred CORESET, it may be expressed as there being no second preferred CORESET.

[0489] If a candidate for a second preferred CORESET derived according to the above priority rule has two active TCI states, and one of the two active TCI states is the same as the first preferred TCI state, the UE may determine the other of the two active TCI states as the second preferred TCI state, or may determine this candidate as the second preferred CORESET.

[0490] Furthermore, when a candidate for the second preferred CORESET derived according to the priority rule has two active TCI states, and both of the two active TCI states are different from the first preferred TCI state, the UE may determine one of the two active TCI states as the second preferred TCI state or may determine this candidate as the second preferred CORESET. This one TCI state may be the one with the smallest or largest TCI state ID among the two active TCI states, or may be the one corresponding to the first or second TCI state activated by the MAC CE.

[0491] 16 is a diagram showing an example of a prioritized CORESET in embodiment Y1.1.2.1. In this example, three CORESETs (CORESET#1-#3) overlap in time.

[0492] CORESET#1 corresponds to CSS set index=0 and cell index=0 and has one active TCI state (TCI state#1).

[0493] CORESET#2 corresponds to USS set index=1 and cell index=0 and has one active TCI state (TCI state#1).

[0494] CORESET#3 corresponds to USS set index=2 and cell index=0 and has one active TCI state (TCI state#2).

[0495] In the case shown in this figure, the UE first selects CORESET#1, which corresponds to the CSS set, as the preferred CORESET. Since CORESET#1 has one active TCI state, the operation is as in embodiment Y1.1.2. This preferred CORESET corresponds to the first preferred CORESET, and TCI state#1 corresponds to the first preferred TCI state.

[0496] Next, the UE searches for a second preferred CORESET. Since one TCI state of CORESET#3 is different from TCI state#1 of the preferred CORESET, the UE determines this TCI state#2 as the second preferred TCI state and determines CORESET#3 as the second preferred CORESET to monitor.

[0497] 17 is a diagram showing an example of a prioritized CORESET in embodiment Y1.1.2.1. In this example, two CORESETs (CORESET#1-#2) overlap in time.

[0498] CORESET#1 corresponds to CSS set index=0 and cell index=0 and has one active TCI state (TCI state#1).

[0499] CORESET#2 corresponds to USS set index=1 and cell index=0 and has two active TCI states (TCI states #1 and #2).

[0500] In the case shown in this figure, the UE first selects CORESET#1, which corresponds to the CSS set, as the preferred CORESET. Since CORESET#1 has one active TCI state, the operation is as in embodiment Y1.1.2. This preferred CORESET corresponds to the first preferred CORESET, and TCI state#1 corresponds to the first preferred TCI state.

[0501] Next, the UE searches for a second prioritized CORESET. Since one of the two active TCI states of CORESET#2 is the same as the first prioritized TCI state, the UE determines the other of the two active TCI states (TCI state#2) as the second prioritized TCI state and determines CORESET#2 as the second prioritized CORESET to monitor.

[0502] 18 is a diagram showing an example of a prioritized CORESET in embodiment Y1.1.2.1. In this example, two CORESETs (CORESET#1-#2) overlap in time.

[0503] CORESET#1 corresponds to CSS set index=0 and cell index=0 and has one active TCI state (TCI state#1).

[0504] CORESET#2 corresponds to USS set index=1 and cell index=0 and has two active TCI states (TCI states #3 and #2).

[0505] In the case shown in this figure, the UE first selects CORESET#1, which corresponds to the CSS set, as the preferred CORESET. Since CORESET#1 has one active TCI state, the operation is as in embodiment Y1.1.2. This preferred CORESET corresponds to the first preferred CORESET, and TCI state#1 corresponds to the first preferred TCI state.

[0506] Next, the UE searches for a second preferred CORESET. Since both of the two active TCI states of CORESET#2 are different from the first preferred TCI state, the UE determines the TCI state with the largest TCI state ID (TCI state#3) of the two active TCI states as the second preferred TCI state, determines CORESET#2 as the second preferred CORESET, and applies only TCI state#3 to CORESET#2 to monitor PDCCH candidates.

[0507] [[Embodiment Y1.1.2.2]] From the remaining conflicting CORESETs excluding the first preferred CORESET, the UE first determines a subset of CORESETs that have two active TCI states, one of which is the same as the first preferred TCI state.

[0508] The UE then determines a second preferred CORESET from the subset according to the same priority rules as in Rel. 16. That is, the second preferred CORESET may correspond to the CSS set with the smallest index in the cell with the smallest index that contains a CSS set, if any, among the CORESETs included in the subset, or may correspond to the USS set with the smallest index in the cell with the smallest index. The smallest USS set index is determined across all USS sets that have at least one PDCCH candidate in overlapping PDCCH monitoring occasions.

[0509] The second priority TCI state corresponds to an active TCI state of the second priority CORESET that is different from the first priority TCI state.

[0510] In embodiment Y1.1.2.2, in the second preferred CORESET, PDCCH candidates (CORESET) can be monitored using both the first preferred TCI and the second preferred TCI state.

[0511] 19 is a diagram showing an example of a prioritized CORESET in embodiment Y1.1.2.2. In this example, four CORESETs (CORESET#1-#4) overlap in time.

[0512] CORESET#1 corresponds to CSS set index=0 and cell index=0 and has one active TCI state (TCI state#1).

[0513] CORESET#2 corresponds to USS set index=1 and cell index=0 and has one active TCI state (TCI state#3).

[0514] CORESET#3 corresponds to USS set index=2 and cell index=0 and has two active TCI states (TCI states #3 and #4).

[0515] CORESET#4 corresponds to USS set index=3 and cell index=0 and has two active TCI states (TCI states #1 and #2).

[0516] In the case shown in this figure, the UE first selects CORESET#1, which corresponds to the CSS set, as the preferred CORESET. Since CORESET#1 has one active TCI state, the operation is as in embodiment Y1.1.2. This preferred CORESET corresponds to the first preferred CORESET, and TCI state#1 corresponds to the first preferred TCI state.

[0517] Next, the UE searches for a second-priority CORESET. Of the remaining CORESETs #2-#4, CORESET #4 is the only CORESET that has two active TCI states, one of which is the same as the first-priority TCI state. Therefore, the UE determines TCI state #2 of CORESET #4, which is different from the first-priority TCI state, as the second-priority TCI state, determines CORESET #4 as the second-priority CORESET, and applies TCI states #1 and #2 to CORESET #4 to monitor PDCCH candidates.

[0518] [[CORESET other than the preferred CORESET]] Monitoring of CORESETs other than the priority CORESET (first priority CORESET and second priority CORESET) in embodiment Y1.1.2 will be described.

[0519] For a CORESET other than the Preferred CORESET that has one active TCI state, the UE may monitor this CORESET if either (1.1.2a) or (1.1.2b) of the following conditions is met: (1.1.2a) The one active TCI state is the same QCL type D as the first priority TCI state; (1.1.2b) The one active TCI state is of the same QCL type D as the first priority TCI state or the second priority TCI state.

[0520] 20 is a diagram showing an example of a prioritized CORESET and other CORESETs monitored simultaneously in embodiment Y1.1.2. In this example, three CORESETs (CORESET#1-#3) overlap in time.

[0521] CORESET#1 corresponds to CSS set index=0 and cell index=0 and has one active TCI state (TCI state#1).

[0522] CORESET#2 corresponds to USS set index=3 and cell index=0 and has two active TCI states (TCI states #1 and #2).

[0523] CORESET#3 corresponds to USS set index=4 and cell index=0 and has one active TCI state (TCI state#2).

[0524] In the case shown in this figure, the UE first selects CORESET#1, which corresponds to the CSS set, as the preferred CORESET. Since CORESET#1 has one active TCI state, the operation is as in embodiment Y1.1.2. This preferred CORESET corresponds to the first preferred CORESET, and TCI state#1 corresponds to the first preferred TCI state.

[0525] Next, the UE searches for a second-priority CORESET. Of the remaining CORESETs #2-#3, CORESET #2 is the only CORESET that has two active TCI states, one of which is the same as the first-priority TCI state. Therefore, the UE determines TCI state #2 of CORESET #2, which is different from the first-priority TCI state, as the second-priority TCI state, determines CORESET #2 as the second-priority CORESET, and applies TCI states #1 and #2 to CORESET #2 to monitor PDCCH candidates.

[0526] If the UE considers condition (1.1.2a), it does not monitor CORESET#3. If the UE considers condition (1.1.2b), it monitors CORESET#3.

[0527] For a CORESET other than the Preferred CORESET that has two active TCI states, the UE may monitor this CORESET if the following condition (1.1.2c) or (1.1.2d) or (1.1.2e) is met: (1.1.2c) The two active TCI states are the same QCL type D as the first priority TCI state and the second priority TCI state; (1.1.2d) One of the two active TCI states is of QCL type D, the same as the first preferred TCI state; (1.1.2e) One of the two active TCI states is the same QCL type D as either the first priority TCI state or the second priority TCI state.

[0528] If the above (1.1.2d) is satisfied, the UE applies only the TCI state of QCL type D, which is the same as the first priority TCI state, to monitor the CORESET.

[0529] If the above (1.1.2e) is satisfied, the UE applies only the TCI state that is the same QCL type D as either the first priority TCI state or the second priority TCI state and monitors the CORESET.

[0530] 21 is a diagram showing an example of a prioritized CORESET and other CORESETs monitored simultaneously in embodiment Y1.1.2. In this example, four CORESETs (CORESET#1-#4) overlap in time.

[0531] CORESET#1 corresponds to CSS set index=0 and cell index=0 and has one active TCI state (TCI state#1).

[0532] CORESET#2 corresponds to USS set index=3 and cell index=0 and has two active TCI states (TCI states #1 and #2).

[0533] CORESET#3 corresponds to USS set index=4 and cell index=0 and has two active TCI states (TCI states #1 and #3).

[0534] CORESET#4 corresponds to USS set index=5 and cell index=0 and has two active TCI states (TCI states #3 and #2).

[0535] In the case shown in this figure, the UE first selects CORESET#1, which corresponds to the CSS set, as the preferred CORESET. Since CORESET#1 has one active TCI state, the operation is as in embodiment Y1.1.2. This preferred CORESET corresponds to the first preferred CORESET, and TCI state#1 corresponds to the first preferred TCI state.

[0536] Next, the UE searches for a second preferred CORESET. Of the remaining CORESETs #2-#4, CORESETs that have two active TCI states, one of which is the same as the first preferred TCI state, are CORESETs #2 and #3. The UE determines CORESET #2, which has a smaller SS set index, as the second preferred CORESET. The UE determines TCI state #2, which is different from the first preferred TCI state, as the second preferred TCI state among the TCI states of CORESET #2, and applies TCI states #1 and #2 to monitor PDCCH candidates in CORESET #2.

[0537] The UE does not monitor CORESET#3 when considering condition (1.1.2c). The UE monitors CORESET#3 with only TCI state #1 applied when considering condition (1.1.2d) or (1.1.2e).

[0538] The UE does not monitor CORESET#4 when considering condition (1.1.2c) or (1.1.2d). The UE monitors CORESET#4 with only TCI state #2 applied when considering condition (1.1.2e).

[0539] [Embodiment Y1.2] The priority rules of embodiment Y1.2 are as follows: Step 1: If there is a subset of conflicting CORESETs that have two active TCI states, apply the priority rules of Rel. 16 NR to only those. If a preferred CORESET is found, end the step. Otherwise, proceed to step 2. · Step 2: If no preferred CORESET is found in Step 1, apply the priority rules of Rel.16 NR to only the subset of conflicting CORESETs that have one active TCI state.

[0540] That is, in embodiment Y1.2, the UE determines the preferred CORESET according to a priority rule in which the CORESET to be monitored is determined preferentially in the following order: CSS set with two active TCI states > USS set with two active TCI states > CSS set with one active TCI state > USS set with one active TCI state.

[0541] In addition, among SS sets of the same type (CSS or USS) with the same number of active TCI states, the one with the smaller index (i.e., the one with the smaller cell index; if the cell index is the same, the one with the smaller SS set index) is selected as the preferred CORESET.

[0542] Similar to the content described in embodiment Y1.1.1, a CORESET to be monitored may be determined from a CORESET other than the preferred CORESET. That is, for a CORESET other than the preferred CORESET that has one active TCI state, if the one active TCI state is the same QCL type D as one of the two active TCI states of the preferred CORESET, the UE may monitor this CORESET.

[0543] Furthermore, for a CORESET other than the preferred CORESET that has two active TCI states, the UE may monitor this CORESET if (1.1.1a) or (1.1.1b) above is satisfied.

[0544] 22 is a diagram showing an example of a prioritized CORESET and other CORESETs monitored simultaneously in embodiment Y1.2. In this example, four CORESETs (CORESET#1-#4) overlap in time.

[0545] CORESET#1 corresponds to CSS set index=0 and cell index=0 and has one active TCI state (TCI state#1).

[0546] CORESET#2 corresponds to USS set index=1 and cell index=0 and has one active TCI state (TCI state#2).

[0547] CORESET#3 corresponds to USS set index=2 and cell index=0 and has two active TCI states (TCI states #1 and #2).

[0548] CORESET#4 corresponds to USS set index=3 and cell index=0 and has two active TCI states (TCI states #1 and #3).

[0549] In the case of this figure, CORESETs having two active TCI states are CORESETs #3 and #4, and CORESET #3, which corresponds to the smaller SS set index, is selected as the preferred CORESET.

[0550] One TCI state of CORESET#1 is QCL type D, which is the same as TCI state #1 of the preferred CORESET, so the UE monitors CORESET#1.

[0551] One TCI state of CORESET#2 is QCL type D, which is the same as TCI state#2 of the preferred CORESET, so the UE monitors CORESET#2.

[0552] One of the two TCI states of CORESET#4 is QCL type D, the same as TCI state #1 of the preferred CORESET, but the other is QCL type D (TCI state #3), which is different from TCI state #2 of the preferred CORESET. Therefore, a UE that complies with (1.1.1a) above does not monitor CORESET#4. A UE that complies with (1.1.1b) above monitors CORESET#4 by applying only TCI state #1.

[0553] [Embodiment Y1.3] The priority rules of embodiment Y1.3 are as follows: Step 1: If there is a conflicting CORESET that has two active TCI states and corresponds to the CSS set with the smallest index in the cell with the smallest index that contains the CSS set, determine this as the dominant CORESET and end the step. Otherwise, proceed to step 2. Step 2: If there is a CORESET among the conflicting CORESETs that has one active TCI state and corresponds to the CSS set with the smallest index in the cell with the smallest index that contains the CSS set, determine this CORESET as the dominant CORESET and end the step. Otherwise, proceed to step 3. Step 3: If there is a CORESET among the conflicting CORESETs that has two active TCI states and corresponds to the USS set with the smallest index in the cell with the smallest index that contains the USS set, determine this CORESET as the preferred CORESET and end the step. Otherwise, proceed to step 4. Step 4: If there is a CORESET among the conflicting CORESETs that has one active TCI state and corresponds to the USS set with the smallest index in the cell with the smallest index that contains the USS set, determine this CORESET as the preferred CORESET and end the step.

[0554] That is, in embodiment Y1.3, the UE determines the preferred CORESET according to a priority rule in which the CORESET to be monitored is determined preferentially in the following order: CSS set with two active TCI states > CSS set with one active TCI state > USS set with two active TCI states > USS set with one active TCI state.

[0555] In addition, among SS sets of the same type (CSS or USS) with the same number of active TCI states, the one with the smaller index (i.e., the one with the smaller cell index; if the cell index is the same, the one with the smaller SS set index) is selected as the preferred CORESET.

[0556] When a preferred CORESET is determined in the above step 1 or 3, the UE may determine a CORESET to further monitor from among CORESETs other than the preferred CORESET based on embodiment Y1.1.1.

[0557] When a preferred CORESET is determined in the above step 2 or 4, the UE may determine a CORESET to further monitor from among CORESETs other than the preferred CORESET based on embodiment Y1.1.2.

[0558] According to the embodiment Y1 described above, when multiple PDCCHs (CORESET) collide, it is possible to appropriately determine the PDCCH to be monitored.

[0559] <Embodiment Y2> Embodiment Y2 relates to an FDM PDCCH repetition scheme.

[0560] In embodiment Y2, two SS sets having corresponding CORESETs may be used for PDCCH repetition. The association between the two SS sets and the CORESETs may be specified in advance by a specification or configured in the UE by higher layer signaling (e.g., RRC signaling).

[0561] In embodiment Y2, in a case where multiple PDCCHs of different QCL types D collide, the UE determines a prioritized CORESET based on at least one priority rule shown in embodiments Y2.1 to Y2.3. Each will be described below.

[0562] Note that the association between a certain CORESET (e.g., a preferred CORESET) and another CORESET may be defined in advance by a specification, or may be configured in a UE by higher layer signaling (e.g., RRC signaling). Also, association is not limited to CORESETs, but a CORESET and an SS set may be associated, or SS sets may be associated with each other.

[0563] In embodiment Y2, the preferred CORESET may be interchangeably read as "preferred CORESET / SS set corresponding to preferred CORESET." Also, in embodiment Y2, another CORESET may be interchangeably read as "another CORESET / SS set corresponding to another CORESET."

[0564] The "association" in embodiment Y2 may be referred to as an association for collision control of multiple PDCCHs, an association for CORESET selection for PDCCH monitoring, an association regarding CORESET priority, or the like.

[0565] [Embodiment Y2.1] The priority rule in embodiment Y2.1 is the same as that in Rel.16 NR. That is, the UE determines the preferred CORESET according to the priority rule that the CSS set is monitored with priority over the USS set, and among SS sets of the same type (CSS or USS), the one with the smaller index (i.e., the one with the smaller cell index; if the cell indexes are the same, the one with the smaller SS set index) is monitored with priority.

[0566] Embodiment Y2.1 is further divided into the following two categories: Embodiment Y2.1.1: The preferred CORESET is associated with another CORESET; Embodiment Y2.1.2: The preferred CORESET is not associated with another CORESET.

[0567] [[Embodiment Y2.1.1]] The UE may monitor another CORESET related to the Preferred CORESET simultaneously with the Preferred CORESET.

[0568] In embodiment Y2.1.1, the TCI state of the prioritized CORESET may be referred to as a first priority TCI state, and the TCI state of the other CORESET may be referred to as a second priority TCI state.

[0569] For the remaining CORESETs excluding the Preferred CORESET and the above-mentioned Alternate CORESET, the UE may monitor this CORESET if the following condition (2.1.1a) or (2.1.1b) is satisfied: (2.1.1a) The TCI state is the same QCL type D as the first priority TCI state; (2.1.1b) The TCI state is QCL type D, which is the same as the first priority TCI state or the second priority TCI state.

[0570] 23 is a diagram showing an example of a prioritized CORESET and other CORESETs monitored simultaneously in embodiment Y2.1.1. In this example, three CORESETs (CORESET#1-#3) overlap in time.

[0571] CORESET#1 corresponds to USS set index=1 and cell index=0 and has one active TCI state (TCI state#1).

[0572] CORESET#2 corresponds to USS set index=2 and cell index=0 and has one active TCI state (TCI state#2).

[0573] CORESET#3 corresponds to USS set index=3 and cell index=0 and has one active TCI state (TCI state#2).

[0574] Furthermore, CORESET#1 and #2 are associated with each other.

[0575] In the case shown in this figure, the UE first selects CORESET#1, which corresponds to the USS set with the smallest USS set index, as the preferred CORESET. Since CORESET#1 has another associated CORESET (CORESET#2), the operation is as in embodiment Y2.1.1.

[0576] Since CORESET#2 is associated with the preferred CORESET, the UE monitors CORESET#2 and determines the active TCI state of CORESET#2 as the second preferred TCI state.

[0577] Although CORESET#3 is not associated with the preferred CORESET, the active TCI state of CORESET#3 is the same as the second preferred TCI state, QCL type D. Therefore, a UE complying with (2.1.1a) above does not monitor CORESET#3. A UE complying with (2.1.1b) above monitors CORESET#3.

[0578] [[Embodiment Y2.1.2]] In embodiment Y2.1.2, the prioritized CORESET determined first according to the same priority rules as those in Rel. 16 NR is also referred to as the first prioritized CORESET, and the next prioritized CORESET determined other than the first prioritized CORESET is also referred to as the second prioritized CORESET. The second prioritized CORESET may be referred to as CORESET X.

[0579] The active TCI state of the first priority CORESET may be referred to as the first priority TCI state, and the active TCI state of the second priority CORESET may be referred to as the second priority TCI state.

[0580] Embodiment Y2.1.2 is broadly divided into embodiments Y2.1.2.1 and Y2.1.2.2 depending on the method for determining the second priority CORESET.

[0581] [[Embodiment Y2.1.2.1]] The second preferred CORESET may be determined from the remaining conflicting CORESETs excluding the first preferred CORESET according to the same priority rules as in Rel. 16. That is, the second preferred CORESET may correspond to the CSS set with the smallest index in the cell with the smallest index that contains a CSS set, if any, among the remaining conflicting CORESETs, or the USS set with the smallest index in the cell with the smallest index. The smallest USS set index is determined across all USS sets that have at least one PDCCH candidate in overlapping PDCCH monitoring occasions.

[0582] If the active TCI state of a candidate for the second preferred CORESET derived according to the above priority rule is the same as the first preferred TCI state, the UE may search for the next candidate (the CORESET corresponding to the SS set / cell with the next smallest index) as a candidate for the second preferred CORESET. That is, the UE may continue searching for the second preferred CORESET until the active TCI state is different from the first preferred TCI state.

[0583] If the UE finds a CORESET that has only one active TCI state that is different from the first preferred TCI state according to the above priority rules, the UE may determine this active TCI state as the second preferred TCI state and determine this CORESET as the second preferred CORESET.

[0584] In addition, even if the active TCI state of a candidate for the second preferred CORESET derived according to the above priority rule is the same as the first preferred TCI state, the UE may determine this active TCI state as the second preferred TCI state and determine this candidate as the second preferred CORESET. In this case, since the second preferred CORESET is the same as the first preferred CORESET, it may be expressed as there being no second preferred CORESET.

[0585] 24 is a diagram showing an example of a prioritized CORESET in embodiment Y2.1.2.1. In this example, three CORESETs (CORESET#1-#3) overlap in time.

[0586] CORESET#1 corresponds to USS set index=1 and cell index=0 and has one active TCI state (TCI state#1).

[0587] CORESET#2 corresponds to USS set index=2 and cell index=0 and has one active TCI state (TCI state#1).

[0588] CORESET#3 corresponds to USS set index=3 and cell index=0 and has one active TCI state (TCI state#2).

[0589] In the case shown in this figure, the UE first selects CORESET#1, which corresponds to the USS set with the smallest USS set index, as the preferred CORESET. Since CORESET#1 does not have another CORESET associated with it, the operation is as in embodiment Y2.1.2. This preferred CORESET corresponds to the first preferred CORESET, and TCI state#1 corresponds to the first preferred TCI state.

[0590] Next, the UE searches for a second preferred CORESET. Since the TCI state of CORESET#3 (TCI state#2) is different from the TCI state#1 of the preferred CORESET, the UE determines this TCI state#2 as the second preferred TCI state and determines CORESET#3 as the second preferred CORESET to monitor.

[0591] [[Embodiment Y2.1.2.2]] From the remaining conflicting CORESETs excluding the first preferred CORESET, the UE first determines a subset of CORESETs that are associated with another CORESET and whose TCI state is the same as the first preferred TCI state.

[0592] The UE may then determine a second preferred CORESET from the subset according to the same priority rules as in Rel. 16. That is, the second preferred CORESET may correspond to the CSS set with the smallest index in the cell with the smallest index that includes a CSS set, if any, among the CORESETs included in the subset, or the USS set with the smallest index in the cell with the smallest index. The smallest USS set index is determined across all USS sets that have at least one PDCCH candidate in overlapping PDCCH monitoring occasions.

[0593] The second preferred TCI state may correspond to an active TCI state of another CORESET associated with the second preferred CORESET.

[0594] The second preferred CORESET may be the CORESET associated with the CORESET corresponding to the CSS set with the lowest index in the cell with the lowest index that includes the CSS set, if any, among the CORESETs included in the subset, or the CORESET associated with the USS set with the lowest index in the cell with the lowest index. In this case, the second preferred TCI state may correspond to the active TCI state of the second preferred CORESET.

[0595] 25 is a diagram showing an example of a prioritized CORESET in embodiment Y2.1.2.2. In this example, four CORESETs (CORESET#1-#4) overlap in time.

[0596] CORESET#1 corresponds to USS set index=1 and cell index=0 and has one active TCI state (TCI state#1).

[0597] CORESET#2 corresponds to USS set index=2 and cell index=0 and has one active TCI state (TCI state#3).

[0598] CORESET#3 corresponds to USS set index=3 and cell index=0 and has one active TCI state (TCI state#1).

[0599] CORESET#4 corresponds to USS set index=4 and cell index=0 and has one active TCI state (TCI state#2).

[0600] CORESET#1 is not associated with any other CORESET. CORESET#2 is not associated with any other CORESET. CORESET#3 and #4 are associated with each other.

[0601] In the case shown in this figure, the UE first selects CORESET#1, which corresponds to the USS set with the smallest USS set index, as the preferred CORESET. Since CORESET#1 does not have another CORESET associated with it, the operation is as in embodiment Y2.1.2. This preferred CORESET corresponds to the first preferred CORESET, and TCI state#1 corresponds to the first preferred TCI state.

[0602] Next, the UE searches for a second preferred CORESET. Of the remaining CORESETs #2-#4, CORESET #3 is the only CORESET that has another associated CORESET and whose TCI state is the same as the first preferred TCI state. Therefore, the UE determines CORESET #3 as the second preferred CORESET and determines TCI state #2 of CORESET #4 associated with CORESET #3 as the second preferred TCI state. The UE monitors PDCCH candidates in CORESETs #3 and #4.

[0603] [[CORESET other than the preferred CORESET]] The monitoring of the priority CORESETs (first priority CORESET and second priority CORESET) and CORESETs other than the CORESETs associated with the priority CORESETs in embodiment Y2.1.2 will be described.

[0604] For these CORESETs, the UE may monitor this CORESET if either (2.1.2a) or (2.1.2b) of the following conditions is met: (2.1.2a) The TCI state is the same QCL type D as the first priority TCI state; (2.1.2b) The TCI state is QCL type D, which is the same as the first priority TCI state or the second priority TCI state.

[0605] 26 is a diagram showing an example of a prioritized CORESET and other CORESETs monitored simultaneously in embodiment Y2.1.2. In this example, four CORESETs (CORESET#1-#4) overlap in time.

[0606] CORESET#1 corresponds to USS set index=1 and cell index=0 and has one active TCI state (TCI state#1).

[0607] CORESET#2 corresponds to USS set index=3 and cell index=0 and has one active TCI state (TCI state#1).

[0608] CORESET#3 corresponds to USS set index=4 and cell index=0 and has one active TCI state (TCI state#2).

[0609] CORESET#4 corresponds to USS set index=5 and cell index=0 and has one active TCI state (TCI state#2).

[0610] CORESET#1 is not associated with any other CORESET, and CORESET#2 and #3 are associated with each other.

[0611] In the case shown in this figure, the UE first selects CORESET#1, which corresponds to the USS set with the smallest USS set index, as the preferred CORESET. Since CORESET#1 does not have another CORESET associated with it, the operation is as in embodiment Y2.1.2. This preferred CORESET corresponds to the first preferred CORESET, and TCI state#1 corresponds to the first preferred TCI state.

[0612] Next, the UE searches for a second preferred CORESET. Of the remaining CORESETs #2-#4, CORESET #2 is the only CORESET that has another associated CORESET and whose TCI state is the same as the first preferred TCI state. Therefore, the UE determines CORESET #2 as the second preferred CORESET and determines TCI state #2 of CORESET #3 associated with CORESET #2 as the second preferred TCI state. The UE monitors PDCCH candidates in CORESETs #2 and #3.

[0613] The UE does not monitor CORESET#4 when condition (2.1.2a) is considered, and monitors CORESET#4 when condition (2.1.2b) is considered.

[0614] [Embodiment Y2.2] The priority rules of embodiment Y2.2 are as follows: Step 1: If there are any subsets of conflicting CORESETs that are associated with another CORESET (in other words, have an association with another CORESET), apply the priority rules of Rel. 16 NR only to those subsets. If a preferred CORESET is found, end the step. If not, proceed to step 2. · Step 2: If no preferred CORESET is found in Step 1, apply the Rel.16 NR priority rules to only the subset of conflicting CORESETs that do not have an association with another CORESET.

[0615] In other words, in embodiment Y2.2, the UE determines the preferred CORESET according to a priority rule in which the CORESET to be monitored is determined preferentially in the following order: CSS set having an association with another CORESET (hereinafter, in this disclosure, also simply referred to as "association") > USS set having an association > CSS set having no association > USS set having no association.

[0616] In addition, among SS sets of the same type (CSS or USS) that have an association (or no association), the one with the smaller index (i.e., the one with the smaller cell index; if the cell index is the same, the one with the smaller SS set index) is selected as the priority CORESET.

[0617] Similar to the content described in embodiment Y2.1.1, a CORESET to be monitored may be determined from CORESETs other than the preferred CORESET. That is, for the remaining CORESETs excluding the preferred CORESET and another CORESET associated with the preferred CORESET, the UE may monitor this CORESET if the above (2.1.1a) or (2.1.1b) is satisfied.

[0618] 27 is a diagram showing an example of a prioritized CORESET and other CORESETs monitored simultaneously in embodiment Y2.2. In this example, four CORESETs (CORESET#1-#4) overlap in time.

[0619] CORESET#1 corresponds to CSS set index=0 and cell index=0 and has one active TCI state (TCI state#1).

[0620] CORESET#2 corresponds to USS set index=1 and cell index=0 and has one active TCI state (TCI state#2).

[0621] CORESET#3 corresponds to USS set index=2 and cell index=0 and has one active TCI state (TCI state#3).

[0622] CORESET#4 corresponds to USS set index=3 and cell index=0 and has one active TCI state (TCI state#3).

[0623] CORESET#1 is not associated with any other CORESET, and CORESET#2 and #3 are associated with each other.

[0624] In this case, CORESETs associated with another CORESET are CORESETs #2 and #3, and CORESET #2, which corresponds to the smaller SS set index, is selected as the preferred CORESET. TCI state #2 of CORESET #2 corresponds to the first preferred TCI state.

[0625] The TCI state #3 of CORESET #3 associated with the preferred CORESET is determined as the second preferred TCI state. The UE monitors PDCCH candidates in CORESET #2 and #3.

[0626] Since the TCI state of CORESET#1 is neither the first priority TCI state nor the second priority TCI state, the UE does not monitor CORESET#1. Also, a UE that complies with (2.1.1a) above does not monitor CORESET#4. A UE that complies with (2.1.1b) above monitors CORESET#4.

[0627] [Embodiment Y2.3] The priority rules of embodiment Y2.3 are as follows: Step 1: If there is a CORESET among the conflicting CORESETs that has an association and corresponds to the CSS set with the smallest index in the cell with the smallest index that contains the CSS set, determine this as the dominant CORESET and end the step. If not, proceed to step 2. Step 2: If there is a CORESET among the conflicting CORESETs that does not have an association and corresponds to the CSS set with the smallest index in the cell with the smallest index that contains the CSS set, determine this as the dominant CORESET and end the step. Otherwise, proceed to step 3. Step 3: If there is a CORESET among the conflicting CORESETs that has an association and corresponds to the USS set with the smallest index in the cell with the smallest index that contains the USS set, determine this as the preferred CORESET and end the step. If not, proceed to step 4. Step 4: If there is a CORESET among the conflicting CORESETs that does not have an association and corresponds to the USS set with the smallest index in the cell with the smallest index that contains the USS set, determine this CORESET as the priority CORESET and end the step.

[0628] In other words, in embodiment Y2.3, the UE determines the preferred CORESET according to a priority rule in which the CORESET to be monitored is determined in the following order: CSS set with association > CSS set without association > USS set with association > USS set without association.

[0629] In addition, among SS sets of the same type (CSS or USS) that have an association (or no association), the one with the smaller index (i.e., the one with the smaller cell index; if the cell index is the same, the one with the smaller SS set index) is selected as the priority CORESET.

[0630] When a preferred CORESET is determined in the above step 1 or 3, the UE may determine a CORESET to further monitor from among CORESETs other than the preferred CORESET based on embodiment Y2.1.1.

[0631] When a preferred CORESET is determined in the above step 2 or 4, the UE may determine a CORESET to further monitor from among CORESETs other than the preferred CORESET based on embodiment Y2.1.2.

[0632] According to the embodiment Y2 described above, when multiple PDCCHs (CORESET) collide, it is possible to appropriately determine the PDCCH to be monitored.

[0633] <Modification of embodiment Y> It should be noted that at least one of the above-described embodiments may be applied only to UEs that have reported or support a particular UE capability.

[0634] The specific UE capabilities may indicate at least one of the following: Whether to support SFN PDCCH repetition scheme; Whether to support FDM PDCCH repetition scheme; Whether to support SFN PDCCH repetition scheme for CSS set; Whether to support FDM PDCCH repetition scheme for CSS set; ·Whether or not simultaneous reception of PDCCHs of two or more different QCL type D is supported.

[0635] Furthermore, at least one of the above-described embodiments may be applied when specific information related to the above-described embodiments is configured in the UE by higher layer signaling (if not configured, for example, the operation of Rel. 15 / 16 applies). For example, the specific information may be information indicating that an SFN / FDM PDCCH repetition scheme is enabled, any RRC parameter for a specific release (e.g., Rel. 17), etc.

[0636] It should be noted that embodiment Y1 is not limited to the case where the UE is configured with (or uses) an SFN PDCCH repetition scheme, but is applicable to the case where two or more TCI states are activated per CORESET.

[0637] Furthermore, embodiment Y2 is not limited to the case where the UE is configured with (or uses) an FDM PDCCH repetition scheme, but is also applicable to the case where two SS sets with corresponding multiple CORESETs are used for the PDCCH.

[0638] (wireless communication system) The configuration of a wireless communication system according to an embodiment of the present disclosure will be described below. In this wireless communication system, communication is performed using any one of the wireless communication methods according to the above embodiments of the present disclosure or a combination thereof.

[0639] 28 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. The wireless communication system 1 may be a system that realizes communication using Long Term Evolution (LTE) or 5th generation mobile communication system New Radio (5G NR) specified by the Third Generation Partnership Project (3GPP).

[0640] The wireless communication system 1 may also support dual connectivity between multiple Radio Access Technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC may include dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), dual connectivity between NR and LTE (NR-E-UTRA Dual Connectivity (NE-DC)), etc.

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

[0642] The wireless communication system 1 may support dual connectivity between multiple base stations within the same RAT (for example, dual connectivity in which both the MN and the SN are NR base stations (gNBs) (NR-NR Dual Connectivity (NN-DC))).

[0643] The wireless communication system 1 may include a base station 11 that forms a macrocell C1 with a relatively wide coverage, and base stations 12 (12a-12c) that are located within the macrocell C1 and form small cells C2 that are smaller than the macrocell C1. A user terminal 20 may be located within at least one of the cells. The locations and numbers of the cells and user terminals 20 are not limited to the embodiment shown in the figure. Hereinafter, when there is no need to distinguish between the base stations 11 and 12, they will be collectively referred to as base station 10.

[0644] The user terminal 20 may be connected to at least one of the multiple base stations 10. The user terminal 20 may utilize at least one of carrier aggregation (CA) using multiple component carriers (CC) and dual connectivity (DC).

[0645] Each CC may be included in at least one of a first frequency band (Frequency Range 1 (FR1)) and a second frequency band (Frequency Range 2 (FR2)). The macro cell C1 may be included in FR1, and the small cell C2 may be included in FR2. For example, FR1 may be a frequency band of 6 GHz or less (sub-6 GHz), and FR2 may be a frequency band above 24 GHz (above-24 GHz). Note that the frequency bands and definitions of FR1 and FR2 are not limited to these, and for example, FR1 may be a frequency band higher than FR2.

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

[0647] The multiple base stations 10 may be connected by wire (for example, optical fiber conforming to the Common Public Radio Interface (CPRI), an X2 interface, or the like) or wirelessly (for example, NR communication). For example, when NR communication is used as a backhaul between the base stations 11 and 12, the base station 11 corresponding to the upper station may be called an Integrated Access Backhaul (IAB) donor, and the base station 12 corresponding to the relay station (relay) may be called an IAB node.

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

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

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

[0651] The radio access scheme may also be called a waveform. Note that in the wireless communication system 1, other radio access schemes (for example, other single-carrier transmission schemes, other multi-carrier transmission schemes) may be used as the UL and DL radio access schemes.

[0652] In the wireless communication system 1, a downlink shared channel (Physical Downlink Shared Channel (PDSCH)) shared by each user terminal 20, a broadcast channel (Physical Broadcast Channel (PBCH)), a downlink control channel (Physical Downlink Control Channel (PDCCH)), etc. may be used as the downlink channel.

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

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

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

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

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

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

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

[0660] In the present disclosure, downlink, uplink, etc. may be expressed without adding "link." Also, various channels may be expressed without adding "Physical" to the beginning.

[0661] In the wireless communication system 1, a synchronization signal (SS), a downlink reference signal (DL-RS), etc. may be transmitted. In the wireless communication system 1, a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DMRS), a positioning reference signal (PRS), a phase tracking reference signal (PTRS), etc. may be transmitted as DL-RS.

[0662] The synchronization signal may be, for example, at least one of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS). A signal block including the SS (PSS, SSS) and the PBCH (and DMRS for the PBCH) may be referred to as an SS / PBCH block, an SS Block (SSB), or the like. Note that the SS, SSB, and the like may also be referred to as reference signals.

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

[0664] (base station) 29 is a diagram showing an example of the configuration of a base station according to an embodiment. The base station 10 includes a control unit 110, a transceiver unit 120, a transceiver antenna 130, and a transmission line interface 140. Note that the base station may include one or more of each of the control unit 110, the transceiver unit 120, the transceiver antenna 130, and the transmission line interface 140.

[0665] In this example, the functional blocks of the characteristic parts of the present embodiment are mainly shown, and it may be assumed that the base station 10 also has other functional blocks necessary for wireless communication. Some of the processing of each unit described below may be omitted.

[0666] The control unit 110 performs overall control of the base station 10. The control unit 110 can be configured from a controller, a control circuit, and the like that are explained based on common understanding in the technical field to which the present disclosure relates.

[0667] The control unit 110 may control signal generation, scheduling (e.g., resource allocation, mapping), etc. The control unit 110 may control transmission and reception using the transceiver unit 120, the transceiver antenna 130, and the transmission path interface 140, measurement, etc. The control unit 110 may generate data to be transmitted as signals, control information, sequences, etc., and transfer them to the transceiver unit 120. The control unit 110 may perform call processing (setting up, releasing, etc.) of communication channels, status management of the base station 10, management of radio resources, etc.

[0668] The transceiver unit 120 may include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may include a transmission processing unit 1211 and a reception processing unit 1212. The transceiver unit 120 may be configured with a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on common understanding in the technical field related to the present disclosure.

[0669] The transmitting / receiving unit 120 may be configured as an integrated transmitting / receiving unit, or may be composed of a transmitting unit and a receiving unit. The transmitting unit may be composed of a transmission processing unit 1211 and an RF unit 122. The receiving unit may be composed of a reception processing unit 1212, an RF unit 122, and a measurement unit 123.

[0670] The transmitting and receiving antenna 130 can be configured from an antenna described based on common understanding in the technical field to which the present disclosure pertains, such as an array antenna.

[0671] The transceiver 120 may transmit the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transceiver 120 may receive the above-mentioned uplink channel, uplink reference signal, etc.

[0672] The transceiver 120 may form at least one of a transmission beam and a reception beam using digital beamforming (for example, precoding), analog beamforming (for example, phase rotation), or the like.

[0673] The transceiver 120 (transmission processing unit 1211) may perform Packet Data Convergence Protocol (PDCP) layer processing, Radio Link Control (RLC) layer processing (e.g., RLC retransmission control), Medium Access Control (MAC) layer processing (e.g., HARQ retransmission control), etc. on data, control information, etc. obtained from the control unit 110, and generate a bit string to be transmitted.

[0674] The transceiver 120 (transmission processor 1211) may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, Discrete Fourier Transform (DFT) processing (if necessary), Inverse Fast Fourier Transform (IFFT) processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output a baseband signal.

[0675] The transmitting / receiving unit 120 (RF unit 122) may perform modulation to a radio frequency band, filtering, amplification, etc. on the baseband signal, and transmit the radio frequency band signal via the transmitting / receiving antenna .

[0676] On the other hand, the transmitting / receiving unit 120 (RF unit 122) may perform amplification, filtering, demodulation to a baseband signal, etc. on the radio frequency band signal received by the transmitting / receiving antenna .

[0677] The transceiver 120 (reception processing unit 1212) may apply reception processing such as analog-to-digital conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal, thereby acquiring user data, etc.

[0678] The transceiver 120 (measurement unit 123) may perform measurements on the received signal. For example, the measurement unit 123 may perform Radio Resource Management (RRM) measurements, Channel State Information (CSI) measurements, etc. based on the received signal. The measurement unit 123 may measure received power (e.g., Reference Signal Received Power (RSRP)), received quality (e.g., Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Signal to Noise Ratio (SNR)), signal strength (e.g., Received Signal Strength Indicator (RSSI)), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 110.

[0679] The transmission path interface 140 may transmit and receive signals (backhaul signaling) between devices included in the core network 30, other base stations 10, etc., and may acquire and transmit user data (user plane data), control plane data, etc. for the user terminal 20.

[0680] The transmitting section and receiving section of the base station 10 in the present disclosure may be configured by at least one of the transmitting / receiving section 120, the transmitting / receiving antenna 130, and the transmission path interface 140.

[0681] The transceiver 120 may transmit information (e.g., RRC IE / MAC CE) regarding at least two of a CORESET pool index associated with a control resource set (CORESET), two transmission configuration indication (TCI) states associated with the CORESET, and two linked search space sets. The controller 110 may control transmission of a physical downlink control channel based on the information (first embodiment).

[0682] The transceiver 120 may transmit information (e.g., RRC IE / MAC CE) about at least one of a CORESET pool index associated with a control resource set (CORESET), two transmission configuration indication (TCI) states associated with the CORESET, and two linked search space sets. If one or more reference signals for at least one of radio link monitoring and beam failure detection are not configured, the control unit 110 may determine the one or more reference signals based on the information (second embodiment).

[0683] The transceiver 120 may transmit information (e.g., RRC IE / MAC CE) regarding at least one of a CORESET pool index associated with a control resource set (CORESET), two transmission configuration indication (TCI) states associated with the CORESET, and two linked search space sets. When multiple quasi co-location (QCL) Type D reference signals used to receive multiple downlink signals collide, the control unit 110 may control transmission of one or more downlink signals using the one or more QCL Type D reference signals among the multiple downlink signals based on the information (third embodiment).

[0684] (user terminal) 30 is a diagram showing an example of the configuration of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transceiver unit 220, and a transmitting / receiving antenna 230. Note that the user terminal 20 may include one or more of each of the control unit 210, the transceiver unit 220, and the transmitting / receiving antenna 230.

[0685] Note that this example mainly shows functional blocks of the characteristic parts of the present embodiment, and it may be assumed that the user terminal 20 also has other functional blocks necessary for wireless communication. Some of the processing of each unit described below may be omitted.

[0686] The control unit 210 performs overall control of the user terminal 20. The control unit 210 can be configured from a controller, a control circuit, and the like that are explained based on common understanding in the technical field to which the present disclosure relates.

[0687] The control unit 210 may control signal generation, mapping, etc. The control unit 210 may also control transmission and reception, measurement, etc. using the transceiver unit 220 and the transceiver antenna 230. The control unit 210 may generate data, control information, sequences, etc. to be transmitted as signals, and transfer them to the transceiver unit 220.

[0688] The transceiver unit 220 may include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may include a transmission processing unit 2211 and a reception processing unit 2212. The transceiver unit 220 may be configured from a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on common understanding in the technical field related to the present disclosure.

[0689] The transmitting / receiving unit 220 may be configured as an integrated transmitting / receiving unit, or may be composed of a transmitting unit and a receiving unit. The transmitting unit may be composed of a transmission processing unit 2211 and an RF unit 222. The receiving unit may be composed of a reception processing unit 2212, an RF unit 222, and a measurement unit 223.

[0690] The transmitting / receiving antenna 230 can be configured as an antenna described based on common understanding in the technical field to which the present disclosure pertains, such as an array antenna.

[0691] The transceiver 220 may receive the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transceiver 220 may transmit the above-mentioned uplink channel, uplink reference signal, etc.

[0692] The transceiver 220 may form at least one of a transmission beam and a reception beam using digital beamforming (for example, precoding), analog beamforming (for example, phase rotation), or the like.

[0693] The transceiver 220 (transmission processing unit 2211) may perform PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control), etc. on data, control information, etc. obtained from the control unit 210, and generate a bit string to be transmitted.

[0694] The transceiver 220 (transmission processor 2211) may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, DFT processing (if necessary), IFFT processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output a baseband signal.

[0695] Whether or not to apply DFT processing may be based on the setting of transform precoding. When transform precoding is enabled for a certain channel (e.g., PUSCH), the transceiver unit 220 (transmission processing unit 2211) may perform DFT processing as the transmission processing to transmit the channel using a DFT-s-OFDM waveform, and when transform precoding is not enabled, the transceiver unit 220 may not perform DFT processing as the transmission processing.

[0696] The transmitting / receiving unit 220 (RF unit 222) may perform modulation to a radio frequency band, filtering, amplification, etc. on the baseband signal, and transmit the radio frequency band signal via the transmitting / receiving antenna 230.

[0697] On the other hand, the transmitting / receiving unit 220 (RF unit 222) may perform amplification, filtering, demodulation to a baseband signal, etc. on the radio frequency band signal received by the transmitting / receiving antenna 230.

[0698] The transceiver 220 (reception processing unit 2212) may apply reception processing such as analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal to acquire user data, etc.

[0699] The transceiver 220 (measurement unit 223) may perform measurements on the received signal. For example, the measurement unit 223 may perform RRM measurement, CSI measurement, etc. based on the received signal. The measurement unit 223 may measure received power (e.g., RSRP), received quality (e.g., RSRQ, SINR, SNR), signal strength (e.g., RSSI), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 210.

[0700] The transmitting section and receiving section of the user terminal 20 in the present disclosure may be configured by at least one of the transmitting / receiving section 220 and the transmitting / receiving antenna 230.

[0701] The transceiver 220 may receive information (e.g., RRC IE / MAC CE) about at least two of a CORESET pool index associated with a control resource set (CORESET), two transmission configuration indication (TCI) states associated with the CORESET, and two linked search space sets. The controller 210 may control reception of the physical downlink control channel based on the information (first embodiment).

[0702] The two TCI states may be associated with at least one of two CORESET pool indices.

[0703] The two search space sets may be associated with at least one of two CORESET pool indices.

[0704] The two CORESETs associated with the two search space sets, respectively, may be associated with one or two TCI states.

[0705] The transceiver 220 may receive information (e.g., RRC IE / MAC CE) about at least one of a CORESET pool index associated with a control resource set (CORESET), two transmission configuration indication (TCI) states associated with the CORESET, and two linked search space sets. If one or more reference signals for at least one of radio link monitoring and beam failure detection are not configured, the control unit 210 may determine the one or more reference signals based on the information (second embodiment).

[0706] The control unit 210 may determine one or more CORESETs from multiple CORESETs based on at least two of the monitoring period of the search space set associated with the CORESET, the number of TCI states associated with the CORESET, the index of the CORESET, and whether the CORESET has linkage, and may determine the one or more reference signals from the active TCI states of the one or more CORESETs.

[0707] The controller 210 may determine the one or more reference signals for a cell.

[0708] The controller 210 may determine the one or more reference signals for each of a plurality of transmission and reception points.

[0709] The transceiver 220 may receive information (e.g., RRC IE / MAC CE) regarding at least one of a CORESET pool index associated with a control resource set (CORESET), two transmission configuration indication (TCI) states associated with the CORESET, and two linked search space sets. When multiple quasi co-location (QCL) Type D reference signals used to receive multiple downlink signals collide, the control unit 210 may control reception of one or more downlink signals using the one or more QCL Type D reference signals among the multiple downlink signals based on the information (third embodiment).

[0710] The control unit 210 may determine the one or more QCL type D reference signals from the multiple QCL type D reference signals based on at least two of the following: whether the search space set associated with the CORESET is a common search space set or a terminal-specific search space set; the index of the search space set; whether the search space set is linked to a second search space set; the index of one of the linked search space sets and the second search space set; whether the second search space set has been monitored; and the number of TCI states associated with the CORESET.

[0711] The control unit 210 may determine the one QCL Type D reference signal from the plurality of QCL Type D reference signals.

[0712] The control unit 210 may determine the two QCL Type D reference signals from the plurality of QCL Type D reference signals.

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

[0714] Here, the functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, deeming, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission may be called a transmitting unit, transmitter, etc. As mentioned above, the implementation method of each is not particularly limited.

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

[0716] In this disclosure, terms such as apparatus, circuit, device, section, unit, etc. may be read interchangeably. The hardware configurations of the base station 10 and the user terminal 20 may be configured to include one or more of the devices shown in the drawings, or may be configured to exclude some of the devices.

[0717] For example, although only one processor 1001 is shown, there may be multiple processors. Furthermore, processing may be performed by one processor, or processing may be performed by two or more processors simultaneously, serially, or in other ways. Furthermore, processor 1001 may be implemented by one or more chips.

[0718] Each function in the base station 10 and the user terminal 20 is realized, for example, by loading predetermined software (programs) onto hardware such as a processor 1001 and a memory 1002, causing the processor 1001 to perform calculations, control communication via the communication device 1004, and control at least one of reading and writing data in the memory 1002 and the storage 1003.

[0719] The processor 1001, for example, runs an operating system to control the entire computer. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, at least a part of the above-mentioned control unit 110 (210), transmission / reception unit 120 (220), etc. may be realized by the processor 1001.

[0720] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 110 (210) may be realized by a control program stored in the memory 1002 and running on the processor 1001, and the other functional blocks may be realized in a similar manner.

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

[0722] Storage 1003 is a computer-readable recording medium and may be constituted by at least one of, for example, a flexible disk, a floppy disk, a magneto-optical disk (e.g., a compact disc (e.g., a Compact Disc ROM (CD-ROM)), a digital versatile disc, a Blu-ray disc), a removable disk, a hard disk drive, a smart card, a flash memory device (e.g., a card, stick, key drive), a magnetic stripe, a database, a server, or other suitable storage medium. Storage 1003 may also be referred to as a secondary storage device.

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

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

[0725] Furthermore, each device, such as the processor 1001 and the memory 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.

[0726] Furthermore, the base station 10 and the user terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized using such hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0727] (Variation) Note that terms explained in the present disclosure and terms necessary for understanding the present disclosure may be replaced with terms having the same or similar meanings. For example, a channel, a symbol, and a signal (signal or signaling) may be interchangeable. A signal may also be a message. A reference signal may be abbreviated as RS, and may also be called a pilot, pilot signal, etc. depending on the applicable standard. A component carrier (CC) may also be called a cell, frequency carrier, carrier frequency, etc.

[0728] A radio frame may be composed of one or more periods (frames) in the time domain. Each of the one or more periods (frames) constituting a radio frame may be called a subframe. Furthermore, a subframe may be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0729] Here, the numerology may be a communication parameter applied to at least one of transmission and reception of a signal or channel, and may indicate at least one of, for example, 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 transceiver in the frequency domain, and a specific windowing process performed by a transceiver in the time domain.

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

[0731] A slot may include multiple minislots. Each minislot may consist of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (PUSCH) mapping type B.

[0732] A radio frame, a subframe, a slot, a minislot, and a symbol all represent time units for transmitting signals. The radio frame, the subframe, the slot, the minislot, and the symbol may be referred to by other names corresponding to the radio frame, the subframe, the slot, the minislot, and the symbol. Note that the time units such as a frame, a subframe, a slot, a minislot, and a symbol in the present disclosure may be interchangeable.

[0733] For example, one subframe may be referred to as a TTI, or multiple consecutive subframes may be referred to as a TTI, or one slot or one minislot may be referred to as a TTI. That is, at least one of a subframe and a TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc., instead of a subframe.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0750] Furthermore, information, signals, etc. may be output from a higher layer to a lower layer and / or from a lower layer to a higher layer. Information, signals, etc. may be input / output via multiple network nodes.

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

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

[0753] Note that the physical layer signaling may be called Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signal), L1 control information (L1 control signal), etc. Furthermore, the RRC signaling may be called an RRC message, such as an RRC connection setup message or an RRC connection reconfiguration message. Furthermore, the MAC signaling may be notified using, for example, a MAC Control Element (CE).

[0754] Furthermore, notification of specified information (e.g., notification that "it is X") is not limited to explicit notification, but may be made implicitly (e.g., by not notifying the specified information or by notifying other information).

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

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

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

[0758] As used in this disclosure, the terms "system" and "network" may be used interchangeably. A "network" may refer to devices included in the network (e.g., base stations).

[0759] In the present disclosure, terms such as "precoding," "precoder," "weight (precoding weight)," "Quasi-Co-Location (QCL)," "Transmission Configuration Indication state (TCI state)," "spatial relation," "spatial domain filter," "transmit power," "phase rotation," "antenna port," "antenna port group," "layer," "number of layers," "rank," "resource," "resource set," "resource group," "beam," "beam width," "beam angle," "antenna," "antenna element," "panel," etc. may be used interchangeably.

[0760] In this disclosure, terms such as "base station (BS)," "radio base station," "fixed station," "NodeB," "eNB (eNodeB)," "gNB (gNodeB)," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "cell," "sector," "cell group," "carrier," "component carrier," etc. may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, picocell, etc.

[0761] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of the base station can be divided into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). The term "cell" or "sector" refers to a part or the entire coverage area of a base station and / or base station subsystem that provides communication service within this coverage.

[0762] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. may be used interchangeably.

[0763] A mobile station may also be referred to as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

[0764] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a wireless communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile object, or the mobile object itself. The mobile object may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may also include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

[0765] Furthermore, a base station in the present disclosure may be read as a user terminal. For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple user terminals (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the user terminal 20 may be configured to have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "sidelink"). For example, terms such as uplink channel and downlink channel may be read as sidelink channel.

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

[0767] In the present disclosure, an operation described as being performed by a base station may be performed by its upper node in some cases. It is apparent that in a network including one or more network nodes having a base station, various operations performed for communication with a terminal may be performed by the base station, one or more network nodes other than the base station (such as, but not limited to, a Mobility Management Entity (MME) and a Serving-Gateway (S-GW)), or a combination thereof.

[0768] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, the order of the processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the specific order presented.

[0769] Each aspect / embodiment described in the present disclosure may be related to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (x is, for example, an integer or a decimal)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE The present invention may be applied to systems that use 802.20, Ultra-Wide Band (UWB), Bluetooth (registered trademark), or other appropriate wireless communication methods, or to next-generation systems that are based on and extend these systems. Furthermore, the present invention may be applied to a combination of multiple systems (for example, a combination of LTE or LTE-A and 5G).

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

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

[0772] The term "determining," as used in this disclosure, may encompass a wide variety of actions. For example, "determining" may be considered to be judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry (e.g., looking up in a table, database, or another data structure), ascertaining, etc.

[0773] Additionally, "determining" may be considered to be "determining" receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), etc.

[0774] Also, "decision" may be considered to be "deciding" resolving, selecting, choosing, establishing, comparing, etc. In other words, "decision" may be considered to be "deciding" on some action.

[0775] Furthermore, "judgment (decision)" may be interpreted as "assuming," "expecting," "considering," or the like.

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

[0777] As used in this disclosure, the terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access."

[0778] In this disclosure, when two elements are connected, they may be considered to be "connected" or "coupled" to one another using one or more wires, cables, printed electrical connections, etc., as well as using electromagnetic energy having wavelengths in the radio frequency range, microwave range, light (both visible and invisible) range, etc., as some non-limiting and non-exhaustive examples.

[0779] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."

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

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

[0782] Although the invention according to the present disclosure has been described in detail above, it is clear to those skilled in the art that the invention according to the present disclosure is not limited to the embodiments described in the present disclosure. The invention according to the present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the invention as defined by the description of the claims. Therefore, the description of the present disclosure is intended to be illustrative and explanatory and does not impose any limiting meaning on the invention according to the present disclosure.

Claims

1. a receiver for receiving information about two linked search space (SS) sets; Overlapping monitoring occasions a first control resource set (CORESET) corresponding to a first SS set having a lowest index among the plurality of SS sets; one or more CORESETs having the same first quasi-collocation (QCL) parameters as the first CORESET; and a second CORESET corresponding to a second SS set linked by the information to the first CORESET and an SS set corresponding to one of the one or more CORESETs; a control unit that controls the monitoring of a physical downlink control channel (PDCCH), The first SS set and the second SS set linked by the information correspond to the first CORESET and the second CORESET, respectively; The terminal, wherein the second CORESET has a second QCL parameter that is different from the first QCL parameter.

2. The terminal of claim 1 , wherein the first CORESET and the second CORESET have the same CORESET pool index.

3. receiving information about two linked search space (SS) sets; Overlapping monitoring occasions a first control resource set (CORESET) corresponding to a first SS set having a lowest index among the plurality of SS sets; one or more CORESETs having the same first quasi-collocation (QCL) parameters as the first CORESET; and a second CORESET corresponding to a second SS set linked by the information to the first CORESET and an SS set corresponding to one of the one or more CORESETs; and controlling the PDCCH to monitor the physical downlink control channel (PDCCH), The first SS set and the second SS set linked by the information correspond to the first CORESET and the second CORESET, respectively; The wireless communication method of a terminal, wherein the second CORESET has a second QCL parameter that is different from the first QCL parameter.

4. a transmitter for transmitting information about two linked search space (SS) sets; Overlapping monitoring occasions a first control resource set (CORESET) corresponding to a first SS set having a lowest index among the plurality of SS sets; one or more CORESETs having the same first quasi-collocation (QCL) parameters as the first CORESET; and a second CORESET corresponding to a second SS set linked by the information to the first CORESET and an SS set corresponding to one of the one or more CORESETs; a control unit that controls transmission of a physical downlink control channel (PDCCH), The first SS set and the second SS set linked by the information correspond to the first CORESET and the second CORESET, respectively; The base station, wherein the second CORESET has a second QCL parameter that is different from the first QCL parameter.

5. A system having a terminal and a base station, The terminal a receiver for receiving information about two linked search space (SS) sets; Overlapping monitoring occasions a first control resource set (CORESET) corresponding to a first SS set having a lowest index among the plurality of SS sets; one or more CORESETs having the same first quasi-collocation (QCL) parameters as the first CORESET; and a second CORESET corresponding to a second SS set linked by the information to the first CORESET and an SS set corresponding to one of the one or more CORESETs; a control unit that controls the monitoring of a physical downlink control channel (PDCCH), The first SS set and the second SS set linked by the information correspond to the first CORESET and the second CORESET, respectively; the second CORESET has second QCL parameters different from the first QCL parameters; The base station A system having a transmitter for transmitting the information.

Images