Method and apparatus for monitoring signal in wireless communication system

By configuring the search space set and monitoring PDCCH candidates in the wireless communication system, the problem of low signal monitoring efficiency in the prior art is solved, and more efficient signal monitoring and multi-cell scheduling capabilities are achieved.

CN119096664APending Publication Date: 2024-12-06LG ELECTRONICS INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380036638.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-08-19
Filing Date
2023-04-27
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

In wireless communication systems, the prior art is difficult to efficiently monitor control signals, resulting in low signal monitoring efficiency.

Method used

Receive information about the number of physical downlink control channel (PDCCH) candidates at the aggregation level of control channel elements (CCE) by a user equipment (UE), configure the search space set, and monitor the downlink control information (DCI) format based on this PDCCH candidates support multi-cell scheduling.

Benefits of technology

It realizes more efficient signal monitoring and improves the operating efficiency and performance of the communication system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119096664A_ABST
    Figure CN119096664A_ABST
Patent Text Reader

Abstract

The method and apparatus for monitoring a signal in a wireless communication system disclosed in the present application may monitor a PDCCH candidate for a DCI format based on a search space set configuration. The DCI format is monitored on a scheduling cell, and a PDSCH or a PUSCH on a plurality of scheduled cells is scheduled.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to a method and an apparatus for use in a wireless communication system. Background Art

[0002] In general, wireless communication systems are being developed to cover a wide range in a diverse manner to provide communication services such as audio communication services, data communication services, etc. Wireless communication is a multiple access system that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmission power, etc.). For example, the multiple access system may include one of a code division multiple access (CDMA) system, a frequency division multiple access (FDMA) system, a time division multiple access (TDMA) system, an orthogonal frequency division multiple access (OFDMA) system, a single carrier frequency division multiple access (SC-FDMA) system, and the like. Summary of the invention

[0003] Technical issues

[0004] An object of the present disclosure is to provide a signal monitoring method and a device for efficiently monitoring a control signal in a wireless communication system.

[0005] Those skilled in the art will understand that the objects that can be achieved by the present disclosure are not limited to those specifically described above, and the above and other objects that can be achieved by the present disclosure will be more clearly understood from the following detailed description.

[0006] Technical Solution

[0007] The present disclosure provides a method and device for monitoring signals in a wireless communication system.

[0008] In one aspect of the present disclosure, a method for monitoring a control signal by a user equipment (UE) in a wireless communication system is provided. The method includes: receiving a search space set configuration including information about the number of physical downlink control channel (PDCCH) candidates for each control channel element (CCE) aggregation level; and monitoring PDCCH candidates for a downlink control information (DCI) format on a scheduling cell based on the search space set configuration, the DCI format being a DCI format for scheduling a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH) on different scheduled cells, and configuring the number of PDCCH candidates based on a set of all scheduled cells or some scheduled cells in the scheduled cells.

[0009] In other aspects of the present disclosure, a device, a processor, and a storage medium for executing a signal monitoring method are provided.

[0010] The communication device may include an autonomous driving vehicle that can communicate with at least a UE, a network, and another autonomous driving vehicle other than the communication device.

[0011] The above aspects of the present disclosure are only some preferred embodiments of the present disclosure, and those skilled in the art may deduce and understand various embodiments reflecting the technical features of the present disclosure from the following detailed description of the present disclosure.

[0012] Beneficial Effects

[0013] According to an embodiment of the present disclosure, when a communication device monitors a control signal, the communication device may perform more efficient signal monitoring based on an operation different from that in the prior art.

[0014] Those skilled in the art will appreciate that the effects that can be achieved using the present disclosure are not limited to those specifically described above, and other advantages of the present disclosure will be more clearly understood from the following detailed description in conjunction with the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 A radio frame structure is illustrated.

[0016] Figure 2 The resource grid during the duration of a time slot is illustrated.

[0017] Figure 3 A self-contained slot structure is illustrated.

[0018] Figure 4 Detailed description of the signal monitoring method according to the embodiment of the present disclosure.

[0019] Figures 5 to 8 An apparatus according to an embodiment of the present disclosure is illustrated. DETAILED DESCRIPTION

[0020] The following technologies may be used in various wireless access systems such as code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), etc. CDMA may be implemented as a radio technology such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA may be implemented as a radio technology such as Global System for Mobile Communications (GSM) / General Packet Radio Service (GPRS) / Enhanced Data Rates for GSM Evolution (EDGE). OFDMA may be implemented as a radio technology such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wireless Fidelity (WiFi)), IEEE802.16 (Worldwide Interoperability for Microwave Access (WiMAX)), IEEE 802.20, Evolved UTRA (E-UTRA), etc. UTRA is part of Universal Mobile Telecommunications System (UMTS). 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is a part of Evolved UMTS (E-UMTS) using E-UTRA, and LTE-advanced (LTE-A) is an evolution of 3GPP LTE. 3GPP New Radio or New Radio Access Technology (NR) is an evolved version of 3GPP LTE / LTE-A.

[0021] For the sake of clarity of description, the present disclosure will be described in the context of 3GPP communication systems (e.g., LTE and NR), which should not be construed as limiting the spirit of the present disclosure. LTE refers to technology that goes beyond 3GPP Technical Specification (TS) 36.xxx Version 8. Specifically, LTE technology that goes beyond 3GPP TS 36.xxx Version 10 is called LTE-A, and LTE technology that goes beyond 3GPP TS 36.xxx Version 13 is called LTE-A pro. 3GPP NR is a technology that goes beyond 3GPP TS 38.xxx Version 15. LTE / NR may be referred to as a 3GPP system. "xxx" specifies a technical specification number. LTE / NR may be collectively referred to as a 3GPP system. Background technology, terms, abbreviations, etc. as used herein refer to technical specifications published before the present disclosure. For example, the following documents may be referenced.

[0022] 3GPP NR

[0023] -38.211: Physical channels and modulation

[0024] -38.212: Multiplexing and channel coding

[0025] -38.213: Physical layer procedures for control

[0026] -38.214: Physical layer procedures for data

[0027] -38.300: NR and NG-RAN general description

[0028] -38.331: Radio Resource Control (RRC) protocol specification

[0029] Figure 1 The radio frame structure for NR is illustrated.

[0030] In NR, UL transmission and DL transmission are configured by frame. Each radio frame has a length of 10ms and is divided into two 5ms half frames. Each half frame is divided into five 1ms subframes. The subframe is divided into one or more time slots, and the number of time slots in the subframe depends on the subcarrier spacing (SCS). Each time slot includes 12 or 14 OFDM (A) symbols according to the cyclic prefix (CP). When a normal CP is used, each time slot includes 14 OFDM symbols. When an extended CP is used, each time slot includes 12 OFDM symbols. Symbols may include OFDM symbols (or CP-OFDM symbols) and SC-FDMA symbols (or discrete Fourier transform-extended-OFDM (DFT-s-OFDM) symbols).

[0031] Table 1 exemplarily illustrates that the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary according to the SCS in the normal CP case.

[0032] [Table 1]

[0033] SCS(15*2^u) <![CDATA[N slot symb ]]> <![CDATA[N frame,u slot ]]> <![CDATA[N subframe,u slot ]]> 15KHz(u=0) 14 10 1 30KHz(u=1) 14 20 2 60KHz(u=2) 14 40 4 1 20KHz(u=3) 14 80 8 240KHz(u=4) 14 160 16

[0034] *N slot symb : Number of symbols in a time slot

[0035] *N frame,u slot : Number of time slots in a frame

[0036] *N sub frame,u slot : Number of time slots in a subframe

[0037] Table 2 illustrates that the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary according to SCS in the case of extended CP.

[0038] [Table 2]

[0039] SCS(15*2^u) <![CDATA[N slot symb ]]> <![CDATA[N frame,u slot ]]> <![CDATA[N subframe,u slot ]]> 60KHz(u=2) 12 40 4

[0040] In the NR system, different OFDM(A) parameter sets (e.g., SCS, CP length, etc.) may be configured for multiple cells aggregated for one UE. Therefore, the (absolute time) duration of a time resource (e.g., a subframe, a time slot, or a transmission time interval (TTI)) (referred to as a time unit (TU) for convenience) consisting of the same number of symbols may be configured differently between the aggregated cells.

[0041] NR can support various parameter sets (or subcarrier spacing (SCS)) to provide various 5G services. For example, NR can support wide areas in conventional cellular bands in SCS of 15kHz and support dense urban areas and wide carrier bandwidths with lower latency in SCS of 30 / 60kHz. In SCS of 60kHz or above, NR can support bandwidths above 24.25GHz to overcome phase noise.

[0042] The NR frequency band may be divided into two frequency ranges: frequency range 1 (FR1) and frequency range 2 (FR2). FR1 and FR2 may be configured as shown in Table 3 below. FR2 may represent millimeter wave (mmW).

[0043] [Table 3]

[0044] Frequency range specification Corresponding frequency range Subcarrier spacing FR1 450MHz-7125MHz 15kHz, 30kHz, 60kHz FR2 24250MHz---.52600MHz 60kHz, 120kHz, 240kHz

[0045] Figure 2 A resource grid during the duration of one time slot is illustrated.

[0046] A time slot includes multiple symbols in the time domain. For example, a time slot includes 14 symbols in the normal CP case and 12 symbols in the extended CP case. A carrier includes multiple subcarriers in the frequency domain. A resource block (RB) may be defined by multiple (e.g., 12) consecutive subcarriers in the frequency domain. Multiple RB interleaving (abbreviated as interleaving) may be defined in the frequency domain. Interleaving m∈{0, 1, ..., M-1} may be composed of (common) RBs{m, M+m, 2M+m, 3M+m, .....}. M represents the number of interleavings. A bandwidth part (BWP) may be defined by multiple consecutive (physical) RBs ((P)RBs) in the frequency domain and corresponds to a parameter set (numerology) (e.g., SCS, CP length, etc.). A carrier may include up to N (e.g., 5) BWPs. Data communication may be performed in an active BWP, and only one BWP may be enabled for a UE. Each element in a resource grid may be referred to as a resource element (RE), to which a complex symbol may be mapped.

[0047] In a wireless communication system, a user equipment (UE) receives information from a base station (BS) in a downlink (DL), and the UE sends information to the BS in an uplink (UL). The information exchanged between the BS and the UE includes data and various control information, and there are various physical channels / signals according to the type / purpose of the information exchanged therebetween. A physical channel corresponds to a set of resource elements (REs) that carry information from a higher layer. A physical signal corresponds to a set of REs that are used by the physical layer but do not carry information from a higher layer. The higher layer includes a medium access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, a radio resource control (RRC) layer, and the like.

[0048] DL physical channels include physical broadcast channel (PBCH), physical downlink shared channel (PDSCH) and physical downlink control channel (PDCCH). DL physical signals include DL reference signal (RS), primary synchronization signal (PSS) and secondary synchronization signal (SSS). DL RS includes demodulation reference signal (DM-RS), phase tracking reference signal (PT-RS) and channel state information reference signal (CSI-RS). UL physical channels include physical random access channel (PRACH), physical uplink shared channel (PUSCH) and physical uplink control channel (PUCCH). UL physical signals include UL RS. UL RS includes DM-RS, PT-RS and sounding reference signal (SRS).

[0049] Figure 3 The structure of a self-contained slot is illustrated.

[0050] In the NR system, a frame has a self-contained structure in which a DL control channel, DL or UL data, a UL control channel, etc. can all be included in one time slot. For example, the first N symbols in a time slot (hereinafter, the DL control region) can be used to send a DL control channel, and the last M symbols in a time slot (hereinafter, the UL control region) can be used to send a UL control channel. N and M are integers greater than or equal to 0. The resource region (hereinafter, the data region) between the DL control region and the UL control region can be used for DL ​​data transmission or UL data transmission. For example, the following configuration can be considered. List each part in chronological order.

[0051] In the present disclosure, the BS may be, for example, a gNode B (gNB).

[0052] DL physical channel / signal

[0053] (1)PDSCH

[0054] PDSCH carries DL data (e.g., DL shared channel transport block (DL-SCHTB)). TB is encoded into a codeword (CW) and then sent after the scrambling and modulation process. CW includes one or more code blocks (CB). One or more CBs can be grouped into a code block group (CBG). Depending on the configuration of the cell, PDSCH can carry up to two CWs. Scrambling and modulation can be performed on each CW, and the modulation symbols generated from each CW can be mapped to one or more layers. Each layer can be mapped to resources together with DMRS after precoding and sent on the corresponding antenna port. PDSCH can be dynamically scheduled by PDCCH (dynamic scheduling). Alternatively, PDSCH can be semi-statically scheduled (configured scheduling (CS)) based on high-level (e.g., RRC) signaling (and / or layer 1 (L1) signaling (e.g., PDCCH)). Therefore, in dynamic scheduling, PDSCH transmission is accompanied by PDCCH, while in CS, PDSCH transmission may not be accompanied by PDCCH. CS may include semi-persistent scheduling (SPS).

[0055] (2)PDCCH

[0056] PDCCH carries downlink control information (DCI). For example, PDCCH (i.e., DCI) can carry: the transmission format and resource allocation of DL-SCH; frequency / time resource allocation information about the uplink shared channel (UL-SCH); paging information about the paging channel (PCH); system information about DL-SCH; time / frequency resource allocation information about high-layer control messages such as random access response (RAR) sent on PDSCH; transmit power control commands; and information about SPS / CS activation / deactivation. Depending on the information in the DCI, various DCI formats can be provided.

[0057] Table 4 shows the DCI format transmitted through the PDCCH.

[0058] [Table 4]

[0059]

[0060] DCI format 0_0 can be used to schedule TB-based (or TB-level) PUSCH, and DCI format 0_1 ​​can be used to schedule TB-based (or TB-level) PUSCH or CBG-based (or CBG-level) PUSCH. DCI format 1_0 can be used to schedule TB-based (or TB-level) PDSCH, and DCI format 1_1 can be used to schedule TB-based (or TB-level) PDSCH or CBG-based (or CBG-level) PDSCH (DL authorization DCI). DCI format 0_0 / 0_1 can be referred to as UL authorization DCI or UL scheduling information, and DCI format 1_0 / 1_1 can be referred to as DL authorization DCI or UL scheduling information. DCI format 2_0 can be used to provide dynamic slot format information (e.g., dynamic SFI) to the UE, and DCI format 2_1 can be used to provide downlink preemption information to the UE. UEs defined as a group can be provided with DCI format 2_0 and / or DCI format 2_1 through a group common PDCCH, which is a PDCCH defined for a group of UEs.

[0061] The PDCCH / DCI may include a cyclic redundancy check (CRC), and the CRC may be masked / scrambled with various identifiers (e.g., a radio network temporary identifier (RNTI)) depending on the owner or purpose of the PDCCH. For example, if the PDCCH is for a specific UE, the CRC may be masked with a cell-RNTI (C-RNTI). If the PDCCH is related to paging, the CRC may be masked with a paging-RNTI (P-RNTI). If the PDCCH is related to system information (e.g., a system information block (SIB)), the CRC may be masked with a system information RNTI (SI-RNTI). If the PDCCH is related to a random access response, the CRC may be masked with a random access-RNTI (RA-RNTI).

[0062] Table 5 shows the usage of PDCCH and transport channels according to the type of RNTI. Here, the transport channel refers to a transport channel related to data carried by PDSCH / PUSCH scheduled by PDCCH.

[0063] [Table 5]

[0064]

[0065] For PDCCH, a fixed modulation scheme (e.g., quadrature phase shift keying (QPSK)) may be used. One PDCCH may include 1, 2, 4, 8, or 16 control channel elements (CCEs), depending on the aggregation level (AL). One CCE may include 6 resource element groups (REGs), and one REG may be defined by one OFDMA symbol and one (P)RB.

[0066] The PDCCH may be sent in a control resource set (CORESET). A CORESET corresponds to a set of physical resources / parameters within a BWP for carrying PDCCH / DCI. For example, a CORESET may include a set of REGs with a given parameter set (e.g., SCS, CP length, etc.). A CORESET may be configured by system information (e.g., MIB) or UE-specific high-level (e.g., RRC) signaling. For example, the following parameters / information may be used to configure a CORESET. A UE may be configured with one or more CORESETs, and multiple CORESETs may overlap in the time / frequency domain.

[0067] -controlResourceSetId: This parameter / information indicates the identifier (ID) of the CORESET.

[0068] -frequencyDomainResources: This parameter / information indicates the frequency domain resources of the CORESET. The frequency domain resources can be represented by a bitmap, and each bit corresponds to an RB group (= 6 consecutive RBs). For example, the most significant bit (MSB) of the bitmap corresponds to the first RB group in the BWP. The RB group corresponding to the bit with a value of 1 can be allocated as the frequency domain resources of the CORESET.

[0069] -Duration: This parameter / information indicates the time domain resource of the CORESET. The parameter / information duration may indicate the number of consecutive OFDMA symbols included in the CORESET. For example, the value of duration is 1-3.

[0070] -cce-REG-MappingType: This parameter / information indicates the CCE to REG mapping type. Both interleaved and non-interleaved types can be supported.

[0071] -precoderGranularity: This parameter / information indicates the precoder granularity in the frequency domain.

[0072] -tci-StatesPDCCH: This parameter / information indicates information about the Transmission Configuration Indication (TCI) state of the PDCCH (eg, TCI-StateID). The TCI state may be used to provide a quasi-co-located (QCL) relationship between the DLRS in an RS set (TCI state) and the PDCCH DMRS port.

[0073] -tci-PresentInDCI: This parameter / information indicates whether the TCI field is included in the DCI.

[0074] -pdcch-DMRS-ScramblingID: This parameter / information indicates information used to initialize the PDCCH DMRS scrambling sequence.

[0075] For PDCCH reception, the UE may monitor (e.g., blindly decode) a set of PDCCH candidates in a CORESET. A PDCCH candidate may represent a CCE monitored by the UE for PDCCH reception / detection. PDCCH monitoring may be performed in one or more CORESETs in an active DL BWP on each active cell in which PDCCH monitoring is configured. A set of PDCCH candidates monitored by the UE may be defined as a PDCCH search space (SS) set. An SS set may be classified as a common search space (CSS) set or a UE-specific search space (USS) set.

[0076] Table 6 shows the PDCCH search space.

[0077] [Table 6]

[0078]

[0079] The SS set may be configured via system information (e.g., MIB) or UE-specific high-level (e.g., RRC) signaling. S (e.g., 10) or fewer SS sets may be configured in each DL BWP of a serving cell. For example, the following parameters / information may be provided for each SS set. Each SS set may be associated with one CORESET, and each CORESET configuration may be associated with one or more SS sets.

[0080] -searchSpaceId: This parameter / information indicates the ID of the SS set.

[0081] -controlResourceSetId: This parameter / information indicates the CORESET associated with the SS set.

[0082] - monitoringSlotPeriodicityAndOffset: This parameter / information indicates the PDCCH monitoring period (in time slots) and the PDCCH monitoring offset (in time slots).

[0083] -monitoringSymbolsWithinSlot: This parameter / information indicates the first OFDMA symbol used for PDCCH monitoring in the slot for which PDCCH monitoring is configured. The first OFDMA symbol is indicated by a bitmap, and each bit corresponds to each OFDMA symbol in the slot. The MSB of the bitmap corresponds to the first OFDM symbol in the slot. The OFDMA symbol corresponding to the bit with value 1 corresponds to the first symbol in the CORESET in the slot.

[0084] -nrofCandidates: This parameter / information indicates the number (e.g., one of 0, 1, 2, 3, 4, 5, 6, and 8) of PDCCH candidates for each AL (where AL={1, 2, 4, 8, 16}).

[0085] -searchSpaceType: This parameter / information indicates whether the SS type is CSS or USS.

[0086] -DCI format: This parameter / information indicates the DCI format of the PDCCH candidate.

[0087] The UE may monitor PDCCH candidates in one or more SS sets in a time slot according to the configuration of the CORESET / SS set. The timing (e.g., time / frequency resource) of monitoring PDCCH candidates is defined as a PDCCH (monitoring) opportunity. One or more PDCCH (monitoring) opportunities may be configured within a time slot.

[0088] DCI for scheduling PDSCH or PUSCH on multiple serving cells

[0089] The above content may be applied in combination with the method proposed in the present disclosure described later. Alternatively, the content may illustrate the technical features of the method proposed in the present disclosure.

[0090] In addition, the following method can also be applied to the above-mentioned NR system shared spectrum (licensed band). Therefore, it is obvious that the terms, expressions and structures in this document can be modified to suit the system so as to implement the technical concept of the present disclosure in the corresponding system.

[0091] In Rel-18, in order to reduce the DCI overhead required for PDSCH / PUSCH scheduling, in REL-18, in a carrier aggregation (CA) scenario where multiple cells are configured, a multi-cell scheduling (multi-CC scheduling) method of simultaneously scheduling multiple service cells / CCs using a single DCI may be considered (based on the reasons shown in Table 7). In the present disclosure, the expression "scheduling multiple cells" may be understood as "scheduling PDSCH or PUSCH to be sent in each of the multiple cells". In other words, the multi-cell DCI is a DCI used to schedule PDSCH or PUSCH on different cells.

[0092] Table 7 can be understood as a reason for supporting such DCI in Rel-18, which serves as one of the motivations for introducing DCI (PDCCH).

[0093] [Table 7]

[0094]

[0095] Therefore, the present disclosure proposes a method for monitoring a PDCCH for DCI (multi-cell DCI) to perform multi-cell scheduling, and a method for configuring associated PDCCH candidates.

[0096] In the proposed method described below, for ease of explanation, the DCI for performing multi-cell scheduling is represented as m-cc DCI, and the DCI for performing conventional single-cell scheduling is represented as s-cc DCI. In addition, the DCI for scheduling PDSCH and the DCI for scheduling PUSCH are collectively referred to as m-cc DCI or s-cc DCI without distinction. In some cases, the scheduled PDSCH and / or PUSCH may be referred to as PDSCH / PUSCH (or PxSCH).

[0097] In the present disclosure, the term "cell" may be interpreted according to the context. For example, a cell may refer to a serving cell. In addition, a cell may consist of one DL component carrier (CC) and one to two ULCCs, but the method described later is not limited to this configuration. In the following, unless otherwise specified, the terms "cell" and "CC" may be used interchangeably. Moreover, a cell / CC may be replaced and used as an (active) BWP within a serving cell. Moreover, unless otherwise specified, the term "cell / CC" in the method described later may be used as a concept covering a primary cell (PCell), a secondary cell (SCell), a primary SCell (PSCell), etc., which may be configured / expressed in a CA / DC (dual connectivity) scenario.

[0098] The cell (or CC) that schedules PDSCH / PUSCH (DL assignment or UL grant) may be referred to as a scheduling cell (or scheduling CC). The cell to which the PDSCH / PUSCH scheduled by the scheduling cell is actually transmitted may be referred to as a scheduled cell (or scheduled CC). When the scheduling cell and the scheduled cell are the same, it is called self-carrier scheduling, and when the scheduling cell and the scheduled cell are different, it is called cross-carrier scheduling.

[0099] Tables 8 and 9 illustrate information elements (IEs) related to cross-carrier scheduling specified in 3GPP TS 38.331.

[0100] [Table 8]

[0101]

[0102] [Table 9]

[0103]

[0104] In the NR system, the cross-carrier scheduling (CCS) configuration can be configured by the high-level parameter CrossCarrierSchedulingConfig, as shown in Tables 8 and 9. For DCI (e.g., DCI format 0_1 / 0_2 / 1_1 / 1_2) that schedules PDSCH or PUSCH, the carrier indicator field (CIF) value is configured. This value becomes 0 for its own cell, and ranges from 1 to 7 for other cells (configured by cif-InSchedulingCell). In addition, as shown in Table 10, the configured CIF value corresponds to the value of n_CI and is used to determine the PDCCH candidate. In this case, the PDCCH monitoring corresponding to the search space set (SS set) configured for the scheduled cell is performed at the PDCCH monitoring opportunity (MO) associated with the SS set having the same index as the SS set in the scheduling cell. In addition, the number of PDCCH candidates for each aggregation level (AL) configured in the SS set of the scheduled cell is inherited as is, and during PDCCH monitoring on the scheduled cell, the same number of PDCCH candidates is applied based on the corresponding SS set in the scheduling cell. The PDCCH MO may be determined for each SS set s within a CORESET p. Up to 10 SS sets may be associated with a single CORESET, and each SS set may be identified by an SS set index.

[0105] [Table 10]

[0106]

[0107]

[0108] For example, SS set #s may be configured for cell #1 and cell #2 as follows.

[0109] - SS set #s configured for cell #1: The number of PDCCH candidates for a specific AL n is set to N_1(n).

[0110] - SS set #s configured for cell #2: The number of PDCCH candidates for a specific AL n is set to N_2(n).

[0111] In this case, if cross-carrier scheduling is configured so that cell #1 is determined as the scheduling cell of cell #2, the UE can perform monitoring of the PDCCH at the PDCCH MO configured in the SS set #s on cell #1 as follows. Specifically, the PDCCH sent on cell #1 can schedule data (e.g., PDSCH or PUSCH) sent on cell #2. The relationship established between cell #1 and cell #2 as described above can be conveniently referred to as a CCS relationship. In addition, monitoring the PDCCH can mean monitoring the PDCCH candidates.

[0112] -For the DCI format configured in SS set #s of cell #1, N_1(n) PDCCH candidates are monitored for each AL n.

[0113] -For the DCI format configured in SS set #s of cell #2, N_2(n) PDCCH candidates are monitored for each AL n.

[0114] For the methods described below, the proposed / calculated values ​​in each method (e.g., the number of PDCCH candidates for each scheduled cell, the blind detection (BD) counting method, the BD budget, or the multiplication or division of specific values ​​of the applied weights) may use a ceiling function or a floor function to produce an integer value as the final result (unless otherwise specified).

[0115] [1] Operation method for m-cc DCI and s-cc DCI

[0116] In a scenario such as CA including M cells (cell #1 to cell #M, where M is an integer greater than or equal to 1), when a connection relationship (e.g., a CCS relationship) is established between the scheduling cell and the remaining cells, one of the following options may be configured / applied to the m-cc DCI capable of simultaneously scheduling multiple cells and the s-cc DCI capable of scheduling a single cell. For ease of explanation, a single cell is represented as cell #k (where k represents a cell index or the kth cell), and the symbol {} is used to represent a set of two or more cells. For example, {cell #1, cell #2} represents cell #1 and cell #2. An arbitrary set of M cells is represented as {{cell #m}, M}. In this case, cell #m may refer to each cell in the set (m=1,...,M).

[0117] 1.1-1 Option 1: M-cc DCI can always be defined as scheduling {{cell #m}, M}. Here, M refers to an integer greater than or equal to 2. In other words, m-cc DCI always schedules multiple cells at the same time, and the operation of scheduling only a single cell by m-cc DCI is not allowed. Cell #m can be a scheduling cell receiving m-cc DCI (PDCCH) or a scheduled cell scheduled by m-cc DCI.

[0118] 1.1-1a Option 1a: M-cc DCI may always be defined as scheduling {{cell #m}, M}. Here, M refers to an integer greater than or equal to 2. Cell #m may be a scheduled cell scheduled by m-cc DCI.

[0119] 1.1-2 Option 2: M-cc DCI can be defined as scheduling {{cell #m}, M} or a single cell (ref-cc) in {{cell #m}, M}. In other words, m-cc DCI can schedule multiple cells at the same time (multi-cell scheduling) or can schedule only one cell (single-cell scheduling). In this case, a single cell can be fixed to a specific cell (ref-cc). Single-cell scheduling by m-ccDCI may not be allowed for cells other than specific cells. Here, M refers to an integer greater than or equal to 2. Cell #m can be a scheduling cell receiving m-cc DCI (PDCCH) or a scheduled cell scheduled by m-cc DCI. The reference CC (ref-cc) refers to a specific cell among {{cell #m}, M} and can be predefined or implicitly or explicitly configured.

[0120] -Method of pre-defining or implicitly configuring ref-cc: In {{cell #m}, M}, the cell with the lowest (or highest) index may be selected as the ref-cc. Alternatively, if PCell, PSCell, or PUCCHSCell is included in the set, the corresponding cell may be selected as the ref-cc. The scheduling cell may also be selected as the ref-cc. In addition, among the cells scheduled by the m-cc DCI, the cell used as a reference for the CIF value may be determined as the ref-cc.

[0121] - Method of explicitly configuring ref-cc: The reference CC (ref-cc) can be semi-statically configured through high-layer signaling such as RRC or MAC control element (CE), or dynamically configured through DCI. In this case, the cell index notified by the signal can indicate the cell based on the above-mentioned predefined rules (or implicit configuration).

[0122] 1.1-2a Option 2a: M-cc DCI may be defined as scheduling a single cell (ref-cc) in {{cell #m}, M} or {{cell #m}, M}. Here, M refers to an integer greater than or equal to 2. Cell #m may be a scheduled cell scheduled by m-cc DCI. Ref-cc refers to a specific cell among {{cell #m}, M} and may be predefined, implicitly configured, or explicitly configured. The method described in 1.1-2 Option 2 may be used to configure ref-cc.

[0123] 1.1-3 Option 3: M-cc DCI can be defined as scheduling {{cell #m}, M}. Here, M refers to an integer greater than or equal to 1. In other words, m-cc DCI can schedule multiple cells at the same time or can schedule only one cell. Compared with 1.1-2 Option 2, a cell does not have to be fixed to a specific cell (ref-cc). Cell #m can be a scheduling cell that receives m-cc DCI (PDCCH) or a scheduled cell scheduled by m-cc DCI.

[0124] 1.1-3a Option 3a: M-cc DCI may be defined as scheduling {{cell #m}, M}. Here, M refers to an integer greater than or equal to 1. Cell #m may be a scheduled cell scheduled by m-cc DCI.

[0125] For each of the above options, the PDCCH monitoring operation of a UE in a cell scheduling m-cc DCI (PDCCH) may be defined as follows.

[0126] 1.1-1 Option 1: The UE may desire to receive m-cc DCI configured according to 1.1-1 Option 1. In addition, the UE may desire to receive s-cc DCI for each cell belonging to {{cell #m}, M} (where m-cc DCI scheduling is configured to be performed) that is self-scheduled or cross-carrier scheduled.

[0127] 1.1-1a Option 1a: The UE may expect to receive m-cc DCI configured according to 1.1-1a Option 1a. In addition, the UE may expect to receive s-cc DCI of a cell in the cross-carrier scheduling {{cell #m}, M} or a self-scheduling scheduling cell.

[0128] 1.1-2 Option 2: The UE may expect to receive the m-cc DCI configured according to 1.1-2 Option 2. In addition, the UE may expect to receive the s-cc DCI of the cells other than the specific ref-cc among the cells belonging to {{cell #m}, M} (wherein the m-cc DCI scheduling is configured to be performed) that are self-scheduled or cross-carrier scheduled.

[0129] 1.1-2a Option 2a: The UE may expect to receive the m-cc DCI configured according to 1.1-2a Option 2a. In addition, the UE may expect to receive the s-cc DCI of a cell in the cross-carrier scheduling {{cell #m}, M} or the self-scheduling scheduling cell.

[0130] 1.1-3 Option 3: The UE may expect to receive m-cc DCI configured according to Option 3. In this case, the UE may not expect to receive s-cc DCI for any cell belonging to {{cell #m}, M} (where m-cc DCI scheduling is configured to be performed) that is self-scheduled or cross-carrier scheduled.

[0131] 1.1-3a Option 3a: The UE may expect to receive m-cc DCI configured according to 1.1-3a Option 3a. In addition, the UE may expect to receive s-cc DCI from the scheduled cell. In this case, the UE may not expect to receive s-cc DCI of one cell in the cross-carrier scheduling {{cell #m}, M}.

[0132] The proposed method described below can be characteristically applied to each of the above options.

[0133] [2] Method for configuring the number of PDCCH candidates for each AL to monitor m-ccDCI

[0134] In the NR system, the number of PDCCH candidates for each CCE AL of each SS set #s can be configured for each cell through the SS set. In a scenario such as CA consisting of M cells {{cell #m}, M}, a connection relationship (e.g., CCS relationship) between the scheduling cell and the remaining cells can be established. In this case, an SS set in which the connection relationship (e.g., CCS relationship) between the scheduling cell and the scheduled cell scheduled via m-cc DCI can be configured. The number of PDCCH candidates for each AL n that can be configured by the corresponding SS set is expressed as PC_m(n). AL n can be 1, 2, 4, 8, 16, but the present disclosure is not limited thereto.

[0135] For multiple scheduled CCs scheduled simultaneously by m-cc DCI, the reference unit used to configure the SS set and / or the number of PDCCH candidates for each AL n (PC_m(n)) can be based on one of the following three criteria. In the following, the proposed operation will be described for the case where m-cc DCI scheduling is configured for M cells {cell #m}, M}.

[0136] 2.1 Standard 1: SS set #s can be configured for m-cc DCI, and PC_m(n) can be configured for SS set #s. In this case, the SS set and PC_m(n) can be configured for all possible CC sets (the entire CC set) that can be simultaneously scheduled by the m-cc DCI. In other words, the SS set and PC_m(n) can be configured specifically for the m-cc DCI. For example, for an m-cc DCI that can simultaneously schedule up to {cell #1, cell #2, cell #3}, the SS set #s and / or PC_m(n) of the m-cc DCI can be configured without distinguishing between the case of scheduling {cell #1, cell #2} and the case of scheduling {cell #2, cell #3}.

[0137] 2.2 Criterion 2: SS set and / or PC_m(n) can be configured for each CC set that can be simultaneously scheduled by m-cc DCI. For example, for m-cc DCI that can simultaneously schedule up to {cell #1, cell #2, cell #3}, SS set #s_A and / or PC_m(n)_A are configured for the case where m-cc DCI schedules {cell #1, cell #2}. For the case where m-cc DCI schedules {cell #2, cell #3}, SS set #s_B and / or PC_m(n)_B are configured. In another example, when one CC is scheduled by m-cc DCI, for example, when m-cc DCI schedules {cell #3}, SS set #s_C and / or PC_m(n)_C can be configured. If the m-cc DCI schedules all three CCs, i.e., {cell #1, cell #2, cell #3}, SS set #s_D and / or PC_m(n)_D can be configured.

[0138] 2.3 Criterion 3: SS set and / or PC_m(n) may be configured for each CC that can be scheduled by m-cc DCI. For example, for m-cc DCI that can schedule up to {cell #1, cell #2, cell #3} simultaneously, if {cell #1, cell #2} is scheduled, SS set #s_1 and / or PC_m(n)_1 may be configured separately for cell #1, and SS set #s_2 and / or PC_m(n)_2 may be configured separately for cell #2 (and similarly, SS set #s_3 and / or PC_m(n)_3 may be configured separately for cell #3).

[0139] For each method proposed below, the configuration of the SS set for m-cc DCI and / or PC_m(n) for AL n can be independently applied based on one of the above criteria 1, 2 or 3.

[0140] One of the following methods may be applied to configure the number of PDCCH candidates for each AL of m-cc DCI. Here, when "PC_m(n) of m-cc DCI" is configured, it may mean configuring PC_m(n) for each standard based on one of standard 1, standard 2, or standard 3. In this case, the SS set #s for configuring the connection relationship (e.g., CCS relationship) between the scheduling cell and the scheduled cell scheduled by m-cc DCI may be configured (for each scheduled cell).

[0141] 2.1 Method 1: The SS set #s' corresponding to the m-cc DCI (which is different from the SS set #s) can be configured separately on the scheduling cell, and the PC_m(n) of the m-cc DCI can be configured for each AL through the SS set #s'. This can be understood as a method of configuring the PC_m(n) of the m-cc DCI via the RRC IE search space (separate from the number of PDCCH candidates configured on the scheduling cell). In other words, the SS set configured for the m-cc DCI can be different from the SS set configured for the s-CC DCI, and the number of PDCCH candidates for each AL can be configured independently in each SS set.

[0142] 2.2 Method 2: PC_m(n) of m-cc DCI can be configured separately for each AL on the same SS set #s. This can be understood as a method of configuring PC_m(n) of m-cc DCI via RRC IE search space (separate from the number of PDCCH candidates configured on the scheduling cell). In other words, the SS set is shared between m-cc DCI and s-CC DCI, but the number of PDCCH candidates for each AL of m-cc DCI can be configured separately.

[0143] 2.3 Method 3: PC_m(n) of m-cc DCI can be configured on SS set #s based on the number of PDCCH candidates for each AL n of a specific representative cell among the scheduled cells that can be scheduled via m-cc DCI. For example, PC_m(n) of m-cc DCI can be set to be the same as the number of PDCCH candidates for each AL n of the representative cell, or to be set to a portion of that number. In this case, "a portion" can mean a specific ratio of PDCCH candidates for each AL n of the representative cell. The specific ratio can be predefined or configured (for example, by high-layer signaling). The specific ratio can also change according to the number of CCs actually scheduled by m-cc DCI. In this method, the representative cell can be one of the cells {{cell #m}, M} that m-cc DCI scheduling is configured to perform, which can be determined using the ref-CC configuration method described in [1]. Alternatively, it can be assumed that the representative cell is a cell with a minimum or maximum number of PDCCH candidates for each AL n among the scheduled CCs, and the minimum or maximum value can be set to PC_m(n) of m-cc DCI.

[0144] 2.4 Method 4: PC_m(n) of m-cc DCI can be configured on SS set #s based on the sum of the number of PDCCH candidates for each AL n of the scheduled cells scheduled by m-cc DCI. For example, if four cells (cell #1 to cell #4) are scheduled simultaneously by m-cc DCI, and the number of PDCCH candidates for each cell is PC_1(n), PC_2(n), PC_3(n) and PC_4(n), then PC_m(n) of m-cc DCI can be set to the value of PC_1(n)+PC_2(n)+PC_3(n)+PC_4(n) or a portion of this value. In this case, "a portion" may refer to a specific ratio that may be predefined or configured (e.g., by high-layer signaling). The specific ratio may change depending on the number of CCs actually scheduled by the m-cc DCI. For example, if four CCs are actually scheduled, PC_m(n) may be determined as PC_m(n)=(PC_1(n)+PC_2(n)+PC_3(n)+PC_4(n)) / 4. If only two CCs are actually scheduled, PC_m(n) may be determined as PC_m(n)=(PC_1(n)+PC_2(n)) / 2.

[0145] 2.5 Method 5: Pc_m(n) of m-cc DCI can be configured on SS set #s based on the weighted sum of the number of PDCCH candidates for each ALn of the scheduled cells. For example, if three cells (cell #1 to cell #3) are scheduled simultaneously via m-cc DCI, and the number of PDCCH candidates for each cell is represented as PC_1(n), PC_2(n), and PC_3(n), then PC_m(n) of m-cc DCI can be set to a value of c1*PC_1(n)+c2*PC_2(n)+c3*PC_3(n) or a portion of this value. Here, c1, c2, and c3 are constants that can be determined equally or differently for each cell. In this case, "a portion" may refer to a specific ratio that can be predefined or configured (e.g., via high-layer signaling). The specific ratio may also change depending on the number of CCs actually scheduled via m-cc DCI. For example, if there are three CCs, PC_m(n) may be determined as PC_m(n)=(c1*PC_1(n)+c2*PC_2(n)+c3*PC_3(n)) / 3, and if there are two CCs, PC_m(n) may be set to PC_m(n)=(c1*PC_1(n)+c2*PC_2(n)) / 2.

[0146] Methods 1 / 2 / 3 / 4 / 5 can be applied independently or in combination with each other.

[0147] Methods 3 / 4 / 5 have been described under the assumption of [Method 2] (i.e., assuming that the same SS set is configured by both s-CC DCI and m-cc DCI). However, methods 3 / 4 / 5 can also be applied to the case where separate SS sets are configured for s-CC DCI and m-cc DCI as described in [Method 1].

[0148] [3] Method for calculating the number of PDCCH candidates per AL n for each CC for m-cc DCI

[0149] In a conventional NR system that only allows s-CC scheduling, the number of PDCCH candidates is configured for each cell. In addition, the maximum number of PDCCH candidates and / or the maximum number of non-overlapping CCEs for which the UE can perform PDCCH monitoring (blind detection) during a specific time period can be defined for each cell. Therefore, for each scheduled cell in which the UE monitors PDCCH, the UE may not expect to configure more than the above number of SS sets, and (in the case of PCell) if the number is exceeded, a separate discarding method can be applied. In this case, depending on the PDCCH monitoring capability, the specific time period can be defined in time slot units, span units, or time slot group units.

[0150] In the case of m-cc DCI, since there may be multiple scheduled cells, the number of PDCCH candidates for each AL n configured for m-cc DCI may be defined in units of all scheduled CCs (criterion 1), in units of a set of scheduled CCs (criterion 2), or in units of scheduled CCs (criterion 3) as described in [2]. If the BD / CCE restriction for m-cc DCI described in [4] is defined in units of multiple CCs, overbooking / discarding may be performed according to the defined units. However, even if [criterion 1] or [criterion 2] is applied, the BD / CCE restriction may still be checked for each CC. To this end, it is necessary to determine a method for calculating the number of PDCCH candidates for each scheduled cell.

[0151] In a scenario such as CA consisting of M cells {{cell #m}, M}, when establishing a connection relationship (e.g., CCS relationship) between the scheduling cell and the remaining cells, one of the following methods can be applied to configure the number of PDCCH candidates per AL n for each scheduled cell scheduled via m-cc DCI. In this case, PC_m(n) for AL n of m-cc DCI can have different meanings according to Standard 1 / 2 / 3. In the case of [Standard 1], PC_m(n) refers to the number of PDCCH candidates for each AL n corresponding to all possible CC sets (entire CC set) that can be scheduled simultaneously via m-cc DCI. In the case of [Standard 2], PC_m(n) refers to the number of PDCCH candidates for each AL n corresponding to each scheduled CC set that can be scheduled via m-cc DCI. In the case of [Standard 3], PC_m(n) can be the same as the number of PDCCH candidates for each AL n configured for each CC that can be scheduled via m-cc DCI.

[0152] 3.1 Method 1: The number of PDCCH candidates per AL n for each CC of the m-cc DCI may be uniformly set to the PC_m(n) of the corresponding CC (pre-configured by the s-CC DCI). In this case, regardless of whether Criteria 1, Criteria 2, or Criteria 3 is applied, the number of PDCCH candidates per AL n for each CC may be the PC_m(n) value configured for the corresponding CC.

[0153] 3.1-1 Method 1-1: The number of PDCCH candidates per AL n for each CC may be uniformly set to PC_m(n). In this case, regardless of whether Criteria 1, Criteria 2, or Criteria 3 is applied, the number of PDCCH candidates per AL n for each CC may have a configured PC_m(n) value.

[0154] 3.2 Method 2: The number of PDCCH candidates per AL n for each CC of the m-cc DCI may be uniformly set to PC_m(n) / M of the corresponding CC (pre-configured by the s-CC DCI). For [Criteria 1], M may represent the total number of CCs that may be scheduled via the m-cc DCI. For [Criteria 2], M may represent the number of CCs that are actually scheduled (or will be scheduled) simultaneously via the m-cc DCI. For [Criteria 3], M may represent "1".

[0155] 3.2-1 Method 2-1: The number of PDCCH candidates per AL n for each CC may be uniformly set to PC_m(n) / M based on a specific value of M. For [Standard 1], M may represent the total number of CCs that may be scheduled via m-cc DCI. For [Standard 2], M may represent the number of CCs actually scheduled simultaneously via m-cc DCI. For [Standard 3], M may represent "1".

[0156] 3.3 Method 3: The number of PDCCH candidates per AL n for each CC of the m-cc DCI can be set (differently) for each CC to a specific ratio of the PC_m(n) of the corresponding CC (pre-configured by the s-cc DCI). In other words, for cell #k, the number of PDCCH candidates per AL n can be set to α(k)*PC_m(n), and for cell #j, the number of PDCCH candidates per AL n can be set to α(j)*PC_m(n). For example, if there are three scheduled cells, the number of PDCCH candidates per AL n for cell #1, cell #2, and cell #3 can be set to α(1)*PC_m(n), α(2)*PC_m(n), and α(3)*PC_m(n), respectively. In this case, the relationship α(1)+α(2)+α(3)=1 can be established. The α value for each CC can be predefined or configured (e.g., by high-layer signaling) based on the number of CCs. When applying this method, the number of α values ​​that need to be configured or determined can be considered as follows. For [Criteria 1], the number of α values ​​can be the total number of CCs that can be scheduled via m-cc DCI. For [Criteria 2], the number of α values ​​can be the number of CCs actually (simultaneously) scheduled via m-cc DCI. For [Criteria 3], the number of α values ​​can be 1.

[0157] 3.3-1 Method 3-1: The number of PDCCH candidates per AL n for each CC can be set differently to a specific ratio of PC_m(n) for each CC. In other words, for cell #k, the number of PDCCH candidates per AL n is set to α(k)*PC_m(n), and for cell #j, the number of PDCCH candidates per AL n is set to α(j)*PC_m(n). For example, if there are three scheduled cells, the number of PDCCH candidates per AL n for cell #1, cell #2, and cell #3 can be set to α(1)*PC_m(n), α(2)*PC_m(n), and α(3)*PC_m(n), respectively. In this case, a relationship of α(1)+α(2)+α(3)=1 can be established. The α value for each CC can be predefined or configured (e.g., by high-layer signaling) based on the number of CCs. When applying this method, the number of α values ​​that need to be configured or determined can be considered as follows. For [Criteria 1], the number of α values ​​may be the total number of CCs that can be scheduled via m-cc DCI. For [Criteria 2], the number of α values ​​may be the number of CCs that are actually and simultaneously scheduled via m-cc DCI. For [Criteria 3], the number of α values ​​may be 1.

[0158] 3.4 Method 4: The number of PDCCH candidates for a specific representative CC among the scheduled CCs scheduled by m-cc DCI may be set to PC_m(n). In this case, the number of PDCCH candidates may not be determined for the remaining scheduled CCs other than the representative CC. Alternatively, as a more general method, the number of PDCCH candidates for the remaining CCs other than the representative CC may be set to be lower than a predetermined threshold (T) (the number of remaining CCs may vary according to a standard method). The number of PDCCH candidates for the representative CC may be set to PC_m(n)-X (if the sum of the values ​​configured for all CCs is X). In this method, the representative CC may be one of the cells {{cell #m}, M} in which the m-cc DCI scheduling is configured to be performed, which may be determined using the ref-CC configuration method described in [1]. In addition, the above-mentioned predetermined threshold (T) may be determined to avoid SS (set) overbooking and SS (set) discarding in the remaining CCs excluding the representative CC, which exceeds the BD budget. The value of T may be predefined or configured (e.g., by high-layer signaling).

[0159] 3.5 Method 5: The number of PDCCH candidates per ALn for each CC can be set (differently) for each CC to a specific ratio of PC_m(n) of the corresponding CC (pre-configured by s-cc DCI). In this case, the weight of each scheduled cell can be determined based on the number (or proportion) of co-scheduled cells (i.e., cells that can be scheduled simultaneously via m-cc DCI) including the corresponding cell. That is, for cell #k, the number of PDCCH candidates per ALn can be set to C(k)+α(k)*PC_m(n), and for cell #j, the number of PDCCH candidates per ALn can be set to C(j)+α(j)*PC_m(n). Alternatively, the number of PDCCH candidates per ALn can be set to [C(k)+α(k)]*PC_m(n) for cell #k, and to [C(j)+α(j)]*PC_m(n) for cell #j. For example, if there are three scheduled cells, the number of PDCCH candidates per AL n for each of cell #1, cell #2, and cell #3 can be set to [C(1)+α(1)]*PC_m(n), [C(2)+α(2)]*PC_m(n), and [C(3)+α(3)]*PC_m(n), respectively. In this case, a relationship of C(1):C(2):C(3)=1:2:3 (or 3:2:1) can be established. In addition, the weight can be set to simultaneously satisfy C(1):C(2):C(3)=1:2:3 and α(1)+α(2)+α(3)=1 and / or C(1)+C(2)+C(3)=1. Alternatively, the weight of each cell (i.e., the value of C(k) for cell #k) can be determined based on the number of cells in the set of co-scheduled cells including the corresponding cell. For example, if the co-scheduled cell set of cell #k is {cell #1, cell #2}, the weight of cell #1 may be C(1), or the weight of cell #1 may be determined as a value obtained by dividing C(1) by the number of cells in the co-scheduled cell set including cell #1 (in this case, the weight of cell #1 will be 0.5*C(1)). In addition, the weight value of each CC (i.e., the value of C(k) for cell #k) may be predefined based on the number of CCs (or the number of co-scheduled cell sets), or may be configured via RRC (e.g., high-layer signaling). When applying this method, the number of weight values ​​per cell that need to be configured or determined may be considered as follows. For [Standard 1], the number of weight values ​​per cell may be the total number of cells that may be scheduled via m-cc DCI. For [Standard 2], the number of weight values ​​per cell may be the number of cells actually (simultaneously) scheduled via m-cc DCI. For [Standard 3], the number of weight values ​​per cell may be 1.

[0160] 3.6 Method 6: The number of PDCCH candidates per AL n for each CC can be set (differently) for each CC to a specific ratio of PC_m(n) of the corresponding CC (pre-configured by s-cc DCI). In this case, the weight of each scheduled cell can be determined based on the number (or proportion) of a set of co-scheduled cells (which can be simultaneously scheduled via m-cc DCI) including the corresponding cell. That is, for cell #k, the number of PDCCH candidates per AL n can be set to C(k)*PC_m(n), and for cell #j, the number of PDCCH candidates per AL n can be set to C(j)*PC_m(n). Here, C(k) and C(j) represent the number (or proportion) of a set of co-scheduled cells including cell #k and cell #j, respectively. For example, if there are three scheduled cells that can be scheduled simultaneously via m-cc DCI, and if one of the co-scheduled cell sets is configured by RRC configuration: {cell #1}, {cell #1, cell #2} or {cell #1, cell #2, cell #3} can be scheduled by m-cc DCI, then the number of PDCCH candidates for each AL n can be configured as C(1)*PC_m(n) for cell #1, C(2)*PC_m(n) for cell #2, and C(3)*PC_m(n) for cell #3. In this case, a relationship of C(1):C(2):C(3)=1:2:3 (or 3:2:1) can be established. In addition, the weights can be set to simultaneously satisfy C(1):C(2):C(3)=1:2:3 and α(1)+α(2)+α(3)=1 and / or C(1)+C(2)+C(3)=1. As a simple example, C(1), C(2) and C(3) can be set to C(1) = 1 / 6, C(2) = 2 / 6 and C(3) = 3 / 6. The weight value of each CC (i.e., the value of C(k) for cell #k) can be predefined based on the number of CCs (or the number of sets of cells scheduled together), or can be configured via RRC (e.g., high-level signaling). When applying this method, the number of weight constants C(k) that need to be configured or determined can be considered as follows. For [Standard 1], the number of weight constants C(k) can be the total number of cells that can be scheduled via m-cc DCI. For [Standard 2], the number of weight constants C(k) can be the number of cells actually (simultaneously) scheduled via m-cc DCI. For [Standard 3], the number of weight constants C(k) can be 1.

[0161] 3.7 Method 7: The number of PDCCH candidates per ALn for each CC of the m-cc DCI can be set (differently) for each CC to a specific ratio of the PC_m(n) of the corresponding CC (pre-configured by the s-cc DCI). In this case, the specific ratio can be a weight applied to PC_m(n). For example, the value obtained by multiplying the weight by PC_m(n) can be set as the number of PDCCH candidates per ALn for each CC of the m-cc DCI. For example, if a set of cells scheduled simultaneously via a single m-cc DCI is defined as a "co-scheduled cell set", then a specific ratio or weight can be determined based on the ratio (e.g., B / A) between the total number of co-scheduled cell sets (e.g., A) and the number of co-scheduled cell sets including the corresponding CC (e.g., B). Alternatively, for each co-scheduled cell set, if the CC belongs to the corresponding cell set, the weight can be determined to be 1. Otherwise, the weight can be determined to be 0. In another example, if the number of cells in a co-scheduled cell set is defined as C, a specific ratio or weight may be determined by calculating 1 / C for each co-scheduled cell set including the corresponding CC and then summing the values ​​of 1 / C. Alternatively, for each co-scheduled cell set, if the CC belongs to the corresponding cell set, the weight may be determined as 1 / C (based on the value of C for the corresponding cell set), and if the CC does not belong to the corresponding cell set, the weight may be determined as 0.

[0162] The above methods can be applied independently, or the principles of each method can be combined and applied together.

[0163] In addition, when the aforementioned method is applied, if some of the multiple CCs simultaneously scheduled via m-cc DCI are unavailable (not applicable), PC_m(n) may be distributed only across available CCs other than the unavailable CCs. In this case, the unavailable CC refers to a CC on which the PDSCH / PUSCH is scheduled or indicated via m-cc DCI but is not actually transmitted. The reasons for not actually transmitting the PDSCH / PUSCH include the case where the scheduled PDSCH / PUSCH does not conform to the (semi-static) DL / UL configuration configured for the cell (e.g., due to temporal overlap with the semi-static DL / UL symbols), and / or the case where the scheduled PDSCH / PUSCH overlaps with other signals / channels such as SSB and is therefore not actually transmitted.

[0164] The proposed method for calculating the number of PDCCH candidates for each CC can be understood as a method for counting the BD attempts required to monitor m-cc DCI (i.e., a method for determining how to count the BD attempts for m-CC DCI relative to the DCI associated with a specific CC). For example, "3.4 Method 4: Setting the number of PDCCH candidates for a specific representative CC among the scheduled CCs to "PC_m(n)" can be interpreted as a method for counting the BD attempts (up to PC_m(n) BD attempts) for monitoring m-cc DCI (and related PDCCH) as BD attempts for DCI associated with a specific representative CC.

[0165] [4] Method for configuring BD / CCE limits and determining overbooking of m-cc DCI

[0166] In the NR system, the UE pre-defines the BD / CCE limit for each scheduled cell within a specific time period (time slot / span / time slot group). The UE then checks whether the number of PDCCH candidates for each CC within the period exceeds the BD limit, or whether the number of CCEs associated with the PDCCH candidates exceeds the CCE limit. In other words, when allocating the PDCCH monitoring opportunity (MO) that the UE can monitor (for each time period), the BD / CCE limit should not be exceeded. Specifically, the SS set is configured so that all SS sets (CSS and USS) for the SCell and the CSS for the PCell do not exceed the predefined BD / CCE limit. For the USS of the PCell, the SS set can be configured to exceed the BD / CCE limit (overbooking); however, in this case, the discard rule is applied. In other words, only the SS sets that do not exceed the BD / CCE limit among the configured SS sets can be configured / monitored.

[0167] The following references refer to the BD / CCE restriction and overbooking / discarding method for each cell specified in NR, which is described in "10.1UE procedure for determining physical downlink control channel assignment" of 3GPP TS 38.213. The operations outlined in this reference may be included as part of the configuration of the present disclosure.

[0168] [References]

[0169] Table 10.1-2 provides the maximum number of monitored PDCCH candidates per slot for a UE operating with a single serving cell in a DL BWP with SCS configuration μ

[0170] Table 10.1-2: Maximum number of monitored PDCCH candidates per slot for DL ​​BWP with SCS configuration μ∈{0,1,2,3} for a single serving cell

[0171]

[0172] Table 10.1-2A provides the maximum number of monitored PDCCH candidates per span for a UE operating with a single serving cell in a DL BWP with SCS configuration μ

[0173] Table 10.1-2A: Maximum number of monitored PDCCH candidates in a span for a combination (X,Y) of DLBWPs with SCS configuration μ∈{0,1} for a single serving cell

[0174]

[0175] Table 10.1-2B provides the combinations (X) for UEs operating with a single serving cell in a DLBWP with SCS configuration μ. s ,Y s ) for each group X s Maximum number of PDCCH candidates to be monitored per time slot

[0176] Table 10.1-2B: Combinations of DL BWPs with SCS configuration μ∈{5,6} for a single serving cell (X s ,Y s ) for each group X s Maximum number of PDCCH candidates to be monitored per time slot

[0177]

[0178] Table 10.1-3 provides the maximum number of non-overlapping CCEs for a DL BWP with SCS configuration μ that a UE operating with a single serving cell is expected to monitor for corresponding PDCCH candidates per slot.

[0179] A PDCCH candidate is non-overlapping if its CCEs correspond to:

[0180] - a different CORESET index, or

[0181] - A different first symbol for reception of the corresponding PDCCH candidate.

[0182] Table 10.1-3: Maximum number of non-overlapping CCEs per slot for DL ​​BWP with SCS configuration μ∈{0,1,2,3} for a single serving cell

[0183]

[0184] Table 10.1-3A provides the maximum number of non-overlapping CCEs for a DL BWP with SCS configuration μ that a UE operating with a single serving cell is expected to monitor for corresponding PDCCH candidates per span

[0185] Table 10.1-3A: Maximum number of non-overlapping CCEs in a span for a combination (X,Y) of DL BWPs with SCS configuration μ∈{0,1} for a single serving cell

[0186]

[0187] Table 10.1-3B provides the expected combinations (X s ,Y s ) for each group X s Maximum number of non-overlapping CCEs for DL ​​BWPs with SCS configuration μ corresponding to PDCCH candidates monitored in time slots

[0188] Table 10.1-3B: Any combination of DL BWP with SCS configuration μ∈{5,6} for a single serving cell (X s ,Y s ) in a group X s Maximum number of non-overlapping CCEs in a slot

[0189]

[0190] If UE

[0191] - pdcch-BlindDetectionCA, pdcch-BlindDetectionCA1, pdcch-BlindDetectionCA2, or pdcch-BlindDetectionCA3 is not reported, or BDFactorR is not provided, then γ = R

[0192] - Reporting pdcch-BlindDetectionCA, pdcch-BlindDetectionCA1, pdcch-BlindDetectionCA2 or pdcch-BlindDetectionCA3, the UE may indicate γ=1 or γ=R via BDFactorR

[0193] If the UE is configured with downlink cell, where the UE is not provided with monitoringCapabilityConfig, or is provided with monitoringCapabilityConfig=r15monitoringcapability and is not provided with CORESETPoolIndex, the associated PDCCH candidates monitored in the active DL BWP of the scheduling cell using SCS configuration μ, where The UE does not need to monitor the active DL BWP of the scheduling cell:

[0194] -When the dispatch cell comes from When there are more than 10 downlink cells, for each scheduled cell, each time slot is more than PDCCH candidates or more non-overlapping CCEs, or

[0195] -When the dispatch cell comes from When there are more than 100 downlink cells, for each scheduled cell, each time slot is more than PDCCH candidates or more non-overlapping CCEs,

[0196] -When the dispatch cell comes from When there are more than one downlink cell, for each CORESET with the same coresetPoolIndex value for each scheduled cell, PDCCH candidates or more non-overlapping CCEs.

[0197] If the UE is configured with such a downlink cell, that is, for the downlink cell, the UE is provided with both monitoringCapabilityConfig=r15monitoringcapability and monitoringCapabilityConfig=r16monitoringcapability, then Replace with

[0198] If UE

[0199] -Configuration downlink cells for which the UE is not provided with monitoringCapabilityConfig, or is provided with monitoringCapabilityConfig=r15monitoringcapability and is not provided with coresetPoolIndex,

[0200] - the associated PDCCH candidates monitored in the active DL BWP of the scheduling cell using SCS configuration μ, where, as well as

[0201] - the DL BWP of an activated cell is the active DL BWP of the activated cell, and the DL BWP of a deactivated cell is the DL BWP of the deactivated cell with the index provided by firstActiveDownlinkBWP-Id,

[0202] UE does not need to be in The active DL BWP of the scheduling cell of the downlink cell is monitored more than PDCCH candidates or more If the UE is configured with such a downlink cell, that is, for the downlink cell, the UE is provided with both monitoringCapabilityConfig=r15monitoringcapability and monitoringCapabilityConfig=r16monitoringcapability, then Replace with

[0203] For those from For each scheduled cell of the downlink cell, the UE does not need to monitor more than 100 ms per time slot on the active DL BWP with SCS configuration μ of the scheduling cell. PDCCH candidates or more non-overlapping CCEs.

[0204] For those from For each scheduled cell of a downlink cell, the UE does not need to monitor on the active DL BWP with SCS configuration μ of the scheduling cell:

[0205] - More than per time slot PDCCH candidates or more Non-overlapping CCEs

[0206] -For CORESETs with the same coresetPoolIndex value, more than PDCCH candidates or more Non-overlapping CCEs

[0207] If the UE is configured with downlink cell, where the UE is provided with monitoringCapabilityConfig=r16monitoringcapability, has associated PDCCH candidates monitored in the active DL BWP of the scheduling cell using SCS configuration μ, and has a combination (X,Y) for PDCCH monitoring Downlink cell in, The UE does not need to monitor the active DL BWP of the scheduling cell when the scheduling cell comes from When there are more than 1 downlink cell, for each scheduled cell, each span is more than PDCCH candidates or more If the UE is configured with such a downlink cell, that is, for the downlink cell, the UE is provided with both monitoringCapabilityConfig=r15monitoringcapability and monitoringCapabilityConfig=r16monitoringcapability, then Replace with

[0208] If the UE is only configured with downlink cell, where the UE is provided with monitoringCapabilityConfig=r16monitoringcapability, uses SCS configuration μ to monitor the associated PDCCH candidates in the active DL BWP of the scheduling cell, and uses the combination (X,Y) for PDCCH monitoring Downlink cell in, The DL BWP of an activated cell is the active DL BWP of the activated cell, and the DL BWP of a deactivated cell is the DL BWP of the deactivated cell with an index provided by firstActiveDownlinkBWP-Id. In the following cases, the UE does not need to monitor more than PDCCH candidates or more Non-overlapping CCEs:

[0209] - If from The union of the PDCCH monitoring opportunities on all scheduled cells of the downlink cell results in PDCCH monitoring according to the combination (X,Y) and any span pair in the set is within Y symbols, within every X symbols from The set of active DL BWPs of all scheduled cells for each span of a downlink cell,

[0210] The first X symbols start at the first symbol with a PDCCH monitoring opportunity, and the next X symbols start at the first symbol with a PDCCH monitoring opportunity that is not included in the first X symbols.

[0211] -From Each span set on the active DL BWP of all scheduled cells of the downlink cell, where for each span set, there is at most one span per scheduled cell, otherwise

[0212] in, is the number of configured cells with associated PDCCH candidates monitored in the active DL BWP of the scheduling cell using SCS configuration j. If the UE is configured with downlink cells for which it is provided with both monitoringCapabilityConfig=r15monitoringcapability and monitoringCapabilityConfig=r16monitoringcapability, then Replace with

[0213] For the combination (X,Y) For each scheduled cell of the downlink cell, the UE does not need to monitor more than one downlink per span on the active DL BWP with SCS configuration μ of the scheduling cell. PDCCH candidates or more non-overlapping CCEs.

[0214] The UE is not expected to be configured with CSS sets other than those provided by searchSpaceMCCH, searchSpaceMTCH or by SearchSpace in PDCCH-ConfigMulticast for DCI formats with CRC scrambled by G-RNTI or G-CS-RNTI, which results in 1 CSS set per slot, for the corresponding combination (X s ,Y s ) for each group X s timeslots, or each span exceeding the maximum number of timeslots, or for the corresponding combination (X s ,Ys ) for each group X s The corresponding total or each scheduled cell number of monitored PDCCH candidates and non-overlapping CCEs per time slot or per span.

[0215] For same-cell scheduling or for cross-carrier scheduling, the UE does not expect the number of PDCCH candidates on the secondary cell, and the number of PDCCH candidates per time slot or for the corresponding combination (X s ,Y s ) for each group X s The number of corresponding non-overlapping CCEs per time slot or per span is respectively greater than the number of CCEs per time slot or for the corresponding combination (X) that the UE can monitor on the secondary cell. s ,Y s ) for each group X s If the UE is provided with monitoringCapabilityConfig=r16monitoringcapability for the primary cell, then except for the first span of each time slot, the UE does not expect the number of PDCCH candidates and the corresponding number of non-overlapping CCEs per span on the primary cell to be greater than the corresponding number per span that the UE can monitor on the primary cell.

[0216] If the UE is configured with a SCS configuration μ∈{5,6} in the active DL BWP of the scheduling cell downlink cells and having a set of X used for PDCCH monitoring s Any combination of time slots (X s ,Y s )of Downlink cell in, Then when the scheduling cell comes from When there are multiple downlink cells, the UE does not need to monitor each group of X of each scheduled cell on the active DL BWP of the scheduling cell. s More time slots than PDCCH candidates or more non-overlapping CCEs. If for an active DLBWP the UE is configured with a downlink cell for which the UE is provided with monitoringCapabilityConfig=r15monitoringcapability and a downlink cell for which the UE is provided with monitoringCapabilityConfig=r17monitoringcapability, then Replace with If for an active DL BWP the UE is configured with a downlink cell for which the UE is provided with monitoringCapabilityConfig=r16monitoringcapability and a downlink cell for which the UE is provided with monitoringCapabilityConfig=r17monitoringcapability, then Replace with If for an active DL BWP the UE is configured with a downlink cell for which the UE is provided with monitoringCapabilityConfig=r15monitoringcapability and monitoringCapabilityConfig=r16monitoringcapability and a downlink cell with SCS configuration μ∈{5,6}, then Replace with

[0217] If the UE's active DL BWP for the scheduling cell is configured with monitoringCapabilityConfig=r17monitoringcapability downlink cells, with a set of X used for PDCCH monitoring s Any combination of time slots (X s ,Y s )of Downlink cell in, The DL BWP of the activated cell is the active DL BWP of the activated cell, and the DL BWP of the deactivated cell is the DL BWP of the deactivated cell with the index provided by firstActiveDownlinkBWP-Id. The UE does not need to The active DL BWP of each downlink cell is X s Time slot monitoring more than PDCCH candidates or more non-overlapping CCEs, where is the number of configured cells with associated PDCCH candidates monitored in the active DL BWP of the scheduled cell using SCS configuration j.

[0218] If for an active DL BWP the UE is configured with either monitoringCapabilityConfig=r15monitoringcapability or monitoringCapabilityConfig=r16monitoringcapability, and monitoringCapabilityConfig=r17monitoringcapability downlink cells, respectively Replace with Or replace it with Or replace it with and , and They are or one of the.

[0219] For a set of X s Any combination of time slots (X s ,Y s )of For each scheduled cell of the downlink cell, the UE does not need to monitor each group of X on the active DL BWP with SCS configuration μ of the scheduling cell. s More time slots than PDCCH candidates or more non-overlapping CCEs.

[0220] For cross-carrier scheduling, the number of PDCCH candidates for monitoring is counted for each scheduled cell and the number of PDCCH candidates per span or per time slot or per group X is counted for each scheduled cell. s The number of non-overlapping CCEs in a time slot.

[0221] According to the following pseudo code, if the UE is not provided with a monitoringCapabilityConfig for the primary cell or if the UE is provided with a monitoringCapabilityConfig=r15monitoringcapability for the primary cell, the UE is in the time slot, or if the UE is provided with a monitoringCapabilityConfig=r16monitoringcapability for the primary cell, the UE is in the first span of each time slot, or if the UE is provided with a monitoringCapabilityConfig=r17monitoringcapability for the primary cell, the UE is in the first span of each time slot for the corresponding combination (X s ,Y s ) of a group X s In each time slot, the PDCCH candidates for monitoring are allocated to the USS set of the primary cell with an active DL BWP with an SCS configuration of μ.

[0222] If, for the USS set for scheduling on the primary cell, the UE is not provided with a coresetPoolIndex for the first CORESET, or is provided with a coresetPoolIndex with a value of 0 for the first CORESET and is provided with a coresetPoolIndex with a value of 1 for the second CORESET, and if or Then the following pseudo code applies only to the USS set associated with the first CORESET.The UE does not desire to monitor PDCCH in a USS set for which there is no allocated PDCCH candidate for monitoring.

[0223] In the following pseudo code, if the UE is provided with monitoringCapabilityConfig=r16monitoringcapability for the primary cell, then and were replaced by and and and were replaced by and

[0224] In the following pseudo code, if the UE is provided with monitoringCapabilityConfig=r17monitoringcapability for the primary cell, then and were replaced by and and and were replaced by and

[0225] For a UE in time slot n, or in a corresponding combination (X s ,Y s ) of a group X s S is used to monitor all search space sets of PDCCH on the primary cell within a time slot or within a span in time slot n. css Indicates that I css A set of CSS sets other than those provided by searchSpaceBroadcast or searchSpace-Multicast, and with S uss Indicates the number of cells with J used for scheduling on the primary cell. uss The cardinality of the USS set and CSS set provided by searchSpaceBroadcast or searchSpace-Multicast. uss Search space set s j , 0≤j <J uss The positions are in ascending order according to the search space set index.

[0226] use 0≤i css Represents the CSS set S css (i) The number of PDCCH candidates counted for monitoring, and 0≤j <J uss Represents the search space set S uss (j) The number of PDCCH candidates counted for monitoring. If the UE indicates three-BD for SS set Linking and searches for space set s via search Space Linking i And i j is provided for the search space set s j , then if s i and j Is a CSS set, then set Or if s i and j If it is a USS set, set

[0227] For S css ​​The CSS set in the UE monitors the corresponding combination (X s ,Y s ) of a group X s In a time slot, or in a span, monitoring requires a total of Non-overlapping CCEs PDCCH candidates.

[0228] Use V CCE (S uss (j)) represents the search space set S uss (j) a set of non-overlapping CCEs, and C(V CCE (S uss (j))) indicates V CCE (S uss (j)) Cardinality, where the UE determines the search space set S uss (j) Non-overlapping CCE

[0229] Consider targeting S css The allocated PDCCH candidates for monitoring of the CSS set in , and for all search space sets S uss (k), 0≤k≤j, the allocated PDCCH candidates for monitoring.

[0230] set up

[0231] set up

[0232] Set j = 0

[0233] while and

[0234] Allocate for monitoring PDCCH candidates are searched in a set of search spaces S uss (j)

[0235]

[0236] j=j+1;

[0237] End while

[0238] [End of References]

[0239] In the following, the BD limit per cell specified in "10.1 UE procedure for determining physical downlink control channel assignment" of 3GPP TS 38.213 (for both non-CA and CA scenarios) is represented as M_max and M_total, and the related CCE limit is represented as C_max and C_total. According to 3GPP TS 38.213, in the CA scenario, min(M_max, M_total) and min(C_max, C_total) are used to check the BD / CCE limit per cell. In other words, in a CA scenario with M cells, each UE checks whether the number of PDCCH candidates configured for each CC and the number of CCEs associated therewith during a specific time period exceed min(M_max, M_total) and min(C_max, C_total), respectively.

[0240] In the case of scheduling using m-CC DCI, the number of PDCCH candidates can be configured per set of multiple CCs, or individually for each CC as described in [2], depending on how the [standard] is defined. However, even if PC_m(n) is configured for multiple CCs based on [standard 1] or [standard 2], the number of PDCCH candidates can still be determined for each individual CC as described in [3]. Therefore, the BD / CCE limit is configured for each CC, and overbooking checks can also be performed on a CC basis. The BD / CCE limit per CC can be configured according to one of the following methods.

[0241] 4.1 Method 1: For each scheduled CC scheduled via m-CC DCI, similar to conventional s-CC scheduling, M_total and C_total are determined using M_max and C_max configured for each CC. The BD limit of the corresponding CC is set to (M_max, M_total), and the CCE limit is set to min(C_max, C_total). If each scheduled CC has a different SCS, the BD / CCE limit is determined separately for each SCS.

[0242] 4.2 Method 2: For each scheduled CC scheduled via m-CC DCI, the BD / CCE limit of each CC is set to a value obtained by multiplying M_max or C_max, which is a BD / CCE limit specific to a regular CC, by N / (N+1). For example, the BD limit is set to M_max*N / (N+1), and the CCE limit is set to C_max*N / (N+1). If [Criteria 1] is applied to the PC_m(n) configuration, N refers to the total number of CCs that can be scheduled via m-CC DCI. If [Criteria 2] is applied, N refers to the actual number of CCs scheduled (simultaneously) via m-CC DCI.

[0243] 4.3 Method 3: BD / CCE restrictions may be configured differently for each CC.

[0244] - Method 3-1: For each CC scheduled via m-CC DCI, the BD / CCE restriction is configured differently. For the k-th CC, the BD / CCE restriction is determined using β(k)*min(M_max, M_total) and / or β(k)*min(C_max, C_total). For example, considering two CCs scheduled via m-CC DCI, for CC#1, the BD / CCE restriction is applied as β(1)*min(M_max, M_total) and β(1)*min(C_max, C_total), and for CC#2, the BD / CCE restriction is applied as β(2)*min(M_max, M_total) and β(2)*min(C_max, C_total).

[0245] - Method 3-2: For each CC scheduled via m-CC DCI, the BD / CCE limit is configured differently. For the k-th CC, β(k)*M_max instead of M_max and / or β(k)*C_max instead of C_max is used to determine the BD / CCE limit. In this case, by scaling β(k), the BD limit can be determined as the minimum of the modified values ​​of M_max and M_total (the same method can be applied to the CCE limit).

[0246] - Method 3-3: For each CC scheduled via m-CC DCI, the BD / CCE limit is configured differently. For the k-th CC, the BD / CCE limit is determined using β(k)*M_total and / or β(k)*C_total. In this case, by scaling β(k), the BD limit is determined as the smaller value between M_total and the modified value of M_max, which is configured independently of β(k) (the same method can be applied to CCE limit).

[0247] In methods 3-1 to 3-3 described in [4], the value of β(k) may be predefined (based on the number of simultaneously scheduled (or schedulable) CCs) or configured (e.g., by high-layer signaling). In addition, β(k) may be defined or configured for each CC#k so that the sum of BD / CCE limits across all CCs (i.e., the sum of BD limits (or CCE limits) across all scheduled CCs) is constantly maintained before and after scaling. Furthermore, although β is expressed as the same for both BD and CCE for simplicity of explanation, different values ​​such as β_BD or β_CCE may be used.

[0248] Methods 3-1 to 3-3 in [4] may be required for the following reasons. As described in [1], each scheduled CC to be scheduled simultaneously via m-CCDCI can be scheduled by m-CC DCI or s-CC DCI. According to the operation method of m-CC DCI, the scheduled CC can be set as a reference cell. In addition, as described in [3], the number of PDCCH candidates can be changed for each scheduled CC. Therefore, when introducing / configuring m-CC DCI, if BD / CCE restrictions are configured differently for each CC in some configuration methods described in [1], [2] and [3], method 3 in 4.3 may be useful.

[0249] The BD / CCE limit configured according to one of the methods in [4] can be used to determine the overbooking per CC (and in each unit time period).

[0250] As described in [2], if the number of PDCCH candidates per AL n for m-CC DCI is configured in units of multiple CC sets based on [Criteria 1] or [Criteria 2], the BD / CCE restriction may also be configured in units of multiple CC sets. In addition, overbooking may be determined based on the BD / CCE restriction configured in units of multiple CC sets and PC_m(n).

[0251] In addition, if some of the multiple CCs simultaneously scheduled via m-CC DCI cannot be used, only the PDSCH / PUSCH scheduled on the corresponding CC can be discarded, and scheduling on other CCs can be effectively performed. In this case, the unavailable CC refers to a CC in which the PDSCH / PUSCH is scheduled or indicated via the m-CC DCI but the PDSCH / PUSCH is not actually sent. The reasons why the PDSCH / PUSCH is not sent include the case where the scheduled PDSCH / PUSCH does not conform to the (semi-static) DL / UL configuration configured for the cell (for example, due to overlap with the semi-static DL / UL symbols in time), and / or the case where the scheduled PDSCH / PUSCH overlaps with other signals / channels such as SSB and is therefore not actually sent.

[0252] When a ref-CC is configured according to the operation method described in [1], such as Option 2 in 1.2 and Option 2a in 1.2-a, if the ref-CC becomes unavailable, the UE may ignore or discard the corresponding m-CC DCI. Similarly, if the scheduling cell becomes unavailable, or if one of the PCell, PSCell and PUCCH SCell becomes unavailable, the UE may also ignore or discard the corresponding m-CC DCI.

[0253] In addition, in order to reduce the BD burden on the UE for m-CC DCI, constraints may be imposed on monitoring PDCCH candidates corresponding to m-CC DCI. One (or a combination of two or more) of the following methods may be configured.

[0254] -When both s-CC DCI and m-CC DCI are capable of scheduling DL or UL transmission (for a specific scheduled cell), the UE may be configured not to simultaneously perform monitoring of s-CC DCI and m-CC DCI within a specific time period (e.g., time slot). For example, when the UE is configured with m-CC DCI, the UE may operate by expecting that there is no PDCCH MO configured with m-CC DCI in the time slot of the MO configured with s-CC DCI.

[0255] - When both s-CC DCI and m-CC DCI are capable of scheduling DL or UL transmission (for a specific scheduled cell), if overbooking occurs, the SS set for m-CC DCI (which usually occupies more CCE resources per DCI) can be discarded first. On the other hand, when both s-CC DCI and m-CC DCI are capable of scheduling DL or UL transmission, if overbooking occurs, the SS set for s-CC DCI (which usually has a larger DCI overhead per CC) can be discarded first.

[0256] -When both s-CC DCI and m-CC DCI are capable of scheduling DL or UL transmission (for a specific scheduled cell) (or when simultaneous monitoring is required), the UE may discard s-CC DCI or m-CC DCI (or both s-CC DCI and m-CC DCI) according to the SS set configuration method (alternatively, the UE may be predefined or configured to operate as follows).

[0257] ■Alternative 1: The SS set for s-CC DCI and the SS set for m-CC DCI can be configured, but it may be necessary to ensure that the two DCI types are not allowed to be monitored simultaneously in the same MO (or the same time slot). In other words, regardless of whether overbooking occurs (i.e., whether the maximum BD budget is exceeded), it is necessary to ensure that the two DCI types are not allowed to be monitored simultaneously in the same MO or time slot. Therefore, when the SS set for s-CC DCI and the SS set for m-CC DCI are configured in the same MO (or time slot), one of the following methods may be configured to handle the SS set for s-CC DCI and the SS set for m-CC DCI.

[0258] ◆The UE may be configured to monitor only the SS set for a specific DCI (i.e., one of the s-CC DCI and the m-CC DCI) and discard monitoring the SS set for other DCIs. In this case, the specific DCI may be predefined as the s-CC DCI or the m-CC DCI. Alternatively, which of the SS set for the s-CC DCI and the SS set for the m-CC DCI to monitor may be configured via RRC signaling.

[0259] ◆If both s-CC DCI and m-CC DCI are configured in each SS set, the SS sets may be discarded in descending order of index (i.e., both s-CC and m-CC in the corresponding SS set may be discarded). Alternatively, the discarding may be performed in the following order: s-CC of the SS set with the highest index → ​​m-CC of the SS set with the highest index → ​​s-CC of the SS set with the second highest index → ​​m-CC of the SS set with the second highest index.

[0260] ◆If only one of s-CC DCI and m-CC DCI is configured in each SS set, the SS sets (regardless of s-CC DCI or m-CC DCI) may be dropped in descending order of index. Alternatively, the SS set with the highest index for s-CC (or m-CC) may be dropped first, followed by the SS set with the highest index for m-CC (or s-CC).

[0261] ◆If only one of the s-CC DCI and the m-CC DCI is configured in each SS set (or regardless of it), when the MOs of the s-CC and m-CC overlap, the s-CC (or m-CC) DCI may be discarded first.

[0262] ■Alternative 2: An SS set for s-CC DCI and an SS set for m-CC DCI can be configured (in the same or different SS sets), and simultaneous monitoring can be allowed in the same MO / timeslot. However, if the maximum BD is exceeded in the same MO / timeslot, a specific SS set may need to be discarded. To this end, one of the following methods can be configured.

[0263] ◆The UE may be configured to first discard the SS set for a specific DCI, i.e., one of the s-CC DCI and the m-CC DCI. In this case, the specific DCI may be predefined as the s-CC DCI or the m-CC DCI. Alternatively, which of the SS set for the s-CC DCI and the SS set for the m-CC DCI to discard first may be configured via RRC signaling.

[0264] ◆If both s-CC DCI and m-CC DCI are configured in each SS set, the SS sets may be discarded in descending order of index (i.e., both s-CC and m-CC in the corresponding SS set may be discarded). Alternatively, the discarding may be performed in the following order: s-CC of the SS set with the highest index → ​​m-CC of the SS set with the highest index → ​​s-CC of the SS set with the second highest index → ​​m-CC of the SS set with the second highest index.

[0265] ◆If only one of s-CC DCI and m-CC DCI is configured in each SS set, the SS sets (regardless of s-CC DCI or m-CC DCI) may be dropped in descending order of index. Alternatively, the SS set with the highest index for s-CC (or m-CC) may be dropped first, followed by the SS set with the highest index for m-CC (or s-CC).

[0266] ◆If only one of the s-CC DCI and the m-CC DCI is configured in each SS set (or regardless of it), when the MOs of the s-CC and m-CC overlap, the s-CC (or m-CC) DCI may be discarded first.

[0267] [5] Method for determining co-scheduled cells for multi-cell scheduling based on SS linking

[0268] In Rel-16 / 17 cross-carrier scheduling, the SS set configured on the scheduling cell can be SS-linked to the scheduling cell. In other words, the SS set of the scheduling cell can be configured with the same SS set index (or ID) as the SS set of the scheduled cell. In this case, only the AL and the number of PDCCH candidates for each AL n can be configured separately for the scheduled cell. In other words, when the SS set with the same SS set index or ID (e.g., K) configured on the scheduled cell is also configured on the scheduling cell, it indicates that SS set #K is linked (SS linking) between the scheduled cell and the scheduling cell. In addition, the PDCCH carrying the DCI for the scheduled cell can be scheduled / sent by SS set #K on the scheduling cell. The number of AL and PDCCH candidates per AL n (PC) can be determined based on the value configured for SS set #K on the scheduled cell.

[0269] Multiple scheduled cells can be scheduled simultaneously via m-cc DCI, and SS links between the scheduling cell and each scheduled cell can be applied (extendedly) via m-cc DCI scheduling. For multi-cell scheduling using m-cc DCI, when SS is configured on the scheduling cell and SS links to the SS of the scheduling cell are also configured on some (or all) co-scheduled cells, a method for determining co-scheduled cells capable of multi-cell scheduling via m-cc DCI is proposed. One (or a combination of two or more) of the proposed methods can be applied.

[0270] The methods described below can be applied (independently) to each SS set index (or ID) configured on the scheduling cell (for convenience, the SS set (index / ID) is referred to as SS (index / ID)). In other words, for each proposed method, the co-scheduled cell set (i.e., the cell set scheduled simultaneously by a single / same m-cc DCI) for multi-cell scheduling through a specific SS (e.g., SS#k) and multi-cell scheduling through another specific SS (e.g., SS#n) can be the same or different.

[0271] 5.1 Method 1: A set of co-scheduled cells consisting only of scheduled cells linked to SS (to the scheduling cell) can be simultaneously scheduled by m-cc DCI. Specifically, for a specific SS (e.g., SS#k) on the scheduling cell, a scheduled cell with the same index / ID as that of SS#k can be determined. In this case, the m-cc DCI sent via SS#k on the scheduling cell can schedule a set of co-scheduled cells consisting only of cells. To this end, a PDCCH candidate set can be configured / set for SS#k. For SSs with different indexes (or IDs) configured in the scheduling cell, a set of co-scheduled cells consisting of cells configured with a specific SS (e.g., SS#k) (based on SS linkage) can be a multi-cell scheduled by an SS (e.g., SS#k), while a set of co-scheduled cells consisting of cells configured with another SS (e.g., SS#n) (based on SS linkage) can be a multi-cell scheduled by an SS (in this case, SS#n).

[0272] ■For example, when the schedulable cell set for multi-cell scheduling through m-cc DCI (i.e., the entire set of cells that can be scheduled via m-cc DCI) is {cell #1, cell #2, cell #3, cell #4}, if SS #k linked to the scheduling cell is configured only for {cell #1, cell #2, cell #3}, then m-cc DCI can schedule the co-scheduled cell set consisting only of {cell #1, cell #2, cell #3} via SS #k on the scheduling cell. In order for m-cc DCI to schedule {cell #1, cell #2, cell #3} at the same time, it is necessary to configure SSs with the same index as the SS of the scheduling cell for all cells #1, cell #2, and cell #3 based on SS linkage.

[0273] 5.2 Method 2: A co-scheduled cell set including all scheduled cells linked to the scheduling cell by SS can be scheduled simultaneously by m-cc DCI. Specifically, a scheduled cell with the same index / ID as a specific SS (e.g., SS#k) in the scheduling cell can be determined. In this case, the m-cc DCI sent via SS#k on the scheduling cell can schedule one or more co-scheduled cell sets including all cells. To this end, a PDCCH candidate set can be configured / set for SS#k. That is, the cell set includes all scheduled cells linked to the scheduling cell by SS, and the cell set may also include cells without SS links. For SSs with different indexes (or IDs) configured in the scheduling cell, a co-scheduled cell set consisting of cells configured with a specific SS (e.g., SS#k) (based on SS links) may be a multi-cell scheduled by SS (e.g., SS#k), while a co-scheduled cell set consisting of cells configured with another SS (e.g., SS#n) (based on SS links) may be a multi-cell scheduled by SS (in this case, SS#n).

[0274] ■For example, when the schedulable cell set for multi-cell scheduling through m-cc DCI is {cell #1, cell #2, cell #3, cell #4}, if SS #k linked to the scheduling cell is configured only for {cell #1, cell #2, cell #3}, then m-cc DCI can schedule one or more co-scheduled cell sets including all {cell #1, cell #2, cell #3} (e.g., {cell #1, cell #2, cell #3} or {cell #1, cell #2, cell #3, cell #4}) via SS #k on the scheduling cell. In other words, the co-scheduled cells may include all cells configured with linked SSs, and / or a union of a cell and other cells not configured with the same SS (based on SS linking).

[0275] 5.3 Method 3: A co-scheduled cell set including at least one scheduled cell linked to an SS scheduling cell can be scheduled simultaneously by m-cc DCI. Specifically, for a specific SS (e.g., SS#k) on a scheduling cell, a scheduled cell with the same index / ID as SS#k can be determined. In this case, the m-ccDCI sent via SS#k on the scheduling cell can schedule one or more co-scheduled cell sets including at least one of the cells. To this end, a PDCCH candidate set can be configured / set for SS#k. In other words, the co-scheduled cell set needs to include at least one scheduled cell linked to the scheduling cell by the SS, and the cell set may also include cells without SS links. For SSs with different indexes (or IDs) configured in the scheduling cell, a co-scheduled cell set consisting of cells configured with a specific SS (e.g., SS#k) (based on SS links) may be a multi-cell scheduled by an SS (e.g., SS#k), while a co-scheduled cell set consisting of cells configured with another SS (e.g., SS#n) (based on SS links) may be a multi-cell scheduled by an SS (in this case, SS#n).

[0276] ■For example, when the schedulable cell set for multi-cell scheduling through m-cc DCI is {cell #1, cell #2, cell #3, cell #4}, if SS#k linked to the scheduling cell is configured only for {cell #1, cell #2, cell #3}, then m-cc DCI can be scheduled via SS#k on the scheduling cell to be configured to include one or more co-scheduled cell sets of at least one cell of {cell #1, cell #2, cell #3} (e.g., {cell #1, #2}, {cell #1, #4}, {cell #1, #3, #4}, etc.). In other words, at least one of the co-scheduled cells is linked to the scheduling cell by the SS.

[0277] 5.4 Method 4: A set of co-scheduled cells consisting of all or some scheduled cells linked by SS to the scheduling cell can be scheduled by m-cc DCI. Specifically, for a specific SS (e.g., SS#k) on the scheduling cell, the scheduled cells with the same index / ID as SS#k can be determined. In this case, the m-cc DCI sent via SS#k on the scheduling cell can schedule one or more sets of co-scheduled cells consisting of all or some cells. To this end, a PDCCH candidate set can be configured / set for SS#k. In other words, a set of co-scheduled cells or some cells in the set are set / configured as scheduled cells linked by SS to the scheduling cell, and cells without SS links may not be included in the cell set.

[0278] ■For example, when the schedulable cell set for multi-cell scheduling through m-cc DCI is {cell #1, cell #2, cell #3, cell #4}, if the SS#k linked to the scheduling cell is configured only for {cell #1, cell #2, cell #3}, then the m-cc DCI can schedule one or more co-scheduled cell sets consisting of all or some of {cell #1, cell #2, cell #3} (e.g., {cell #1}, {cell #2}, {cell #3}, {cell #1, cell #2}, {cell #1, cell #3}, {cell #2, cell #3}, {cell #1, cell #2, cell #3}) via SS#k on the scheduling cell. In other words, this method is similar to [5.1 Method 1] in that SS links need to be established for all co-scheduled cells. However, this method allows all or some SS-linked cells to be scheduled simultaneously (whereas in [5.1 Method 1], all SS-linked scheduled cells are scheduled simultaneously).

[0279] 5.5 Method 5: Multi-cell scheduling via m-cc DCI can be indicated / configured to be possible only when the SS linked to the scheduling cell is configured for all cells in the schedulable cell set. Specifically, for a specific SS (e.g., SS#k) on the scheduling cell, the scheduled cell with the same index / ID as SS#k can be determined. In this case, only if the cell set is the same as the schedulable cell set, the m-cc DCI sent via SS#k on the scheduling cell can schedule any (or all) co-scheduled cell sets. To this end, a PDCCH candidate set can be set / configured for SS#k. In other words, all cells belonging to the co-scheduled cell set are set / configured as scheduled cells where the SS is linked to the scheduling cell, and all cells in the schedulable cell set are linked to the scheduling cell by the SS.

[0280] ■For example, when the schedulable cell set for multi-cell scheduling through m-cc DCI is {cell #1, cell #2, cell #3, cell #4}, if the SS link to SS#k of the scheduling cell is configured only for {cell #1, cell #2, cell #3} (in other words, SS link is not established for some cells), the transmission of m-cc DCI and multi-cell scheduling through SS#k on the scheduling cell may not be allowed. In other words, in order to schedule the schedulable cell set via m-cc DCI, it is necessary to configure SS link to SS of the scheduling cell for all {cell #1, cell #2, cell #3, cell #4}.

[0281] In addition, in the method proposed above, for the following configurations described in [2], [3] and / or [4], the (scheduled) cells (or (scheduled) cell set) can be limited to the (scheduled) cells that are SS-linked to the scheduling cell: a method for configuring the number of PDCCH candidates per AL for m-cc DCI (configured in the m-cc DCI), a method for configuring / applying the number of PDCCH candidates per AL configured / applied to each (scheduled) cell, a BD counting method when monitoring m-cc DCI, a BD counting method configured / applied to each (scheduled) cell, a BD / CCE limit (or BD / CCE budget) for m-cc DCI (configured in the m-cc DCI) and / or a BD / CCE limit (or BD / CCE budget) configured / applied to each (scheduled) cell. In other words, when the proposed method is applied, (scheduled) cells that have no SS link with the scheduling cell can be excluded. For example, in the proposed method, a specific representative CC or ref-CC (or ref-cell) may be determined or configured as a specific one of the (scheduled) cells to which the SS is linked to the scheduling cell.

[0282] In addition, the number of PDCCH candidates per AL for m-cc DCI can be determined / configured based on the number of PDCCH candidates per AL configured for a specific ref-cell among the (scheduled) cells that link the SS to the scheduling cell. In this case, one of the methods described in [2] or [3] can be applied to determine / configure the number of PDCCH candidates per AL for m-cc DCI. The specific ref-cell can be determined according to the method described in [1]. Moreover, based on the determined / configured number of PDCCH candidates per AL, the method described in [3] (or [4]) can be applied to determine the (scheduled) cell for which BD attempts are counted to monitor the m-ccDCI. When this method is applied, the (scheduled) cell (or (scheduled) cell set) is limited to the (scheduled) cell that links the SS to the scheduling cell. In other words, when the proposed method is applied, the (scheduled) cell that has no SS link to the scheduling cell can be excluded. For example, in the proposed method, a specific representative CC or ref-CC (or ref-cell) may be determined or configured as a specific one of the (scheduled) cells to which the SS is linked to the scheduling cell.

[0283] The NR UE can be configured with searchSpaceType and DCI format (e.g., dci-Format) through the RRC parameter SearchSpace. Depending on the DCI format of the SS configured in the scheduling cell and / or the scheduled cell, methods 1 to 5 in the above [5] can be applied to a limited extent. For ease of explanation, the DCI format configured for m-cc DCI (in SS configuration) is referred to as format_X, and the DCI format configured for legacy DCI (in SS configuration) is referred to as format_L (e.g., formats0-0-And-1-0, formats0-1-And-1-1, etc.). When the DCI format of the SS configured in the scheduling and / or scheduled cell is format_X, the above method can be applied to a limited extent.

[0284] 5-(1) When the DCI format for SS#k configured on the scheduling cell is format_X, an SS link between the scheduling cell and the scheduled cell can be established through SS#k. In other words, the SS set link between the scheduling cell and the scheduled cell for multi-cell scheduling can be configured / applied through the SS set configured with format_X. In this case, the above method can be applied to establish the SS set link and / or determine the scheduled cell. For example, in method 1 / 4 / 5 of [5], when format_X is configured for SS#k configured on the scheduling cell, the (scheduled) cell configured identically to SS#k (i.e., SS linked) can be scheduled through m-cc DCI. In method 2 / 3 of [5], when format_X is configured for SS#k configured on the scheduling cell, the (scheduled) cell set including the cell configured identically to SS#k (i.e., SS linked) can be scheduled through m-cc DCI.

[0285] ■When format_X is configured for SS#k configured on the scheduling cell, format_X may also be configured for SS#k on the (scheduled) cell scheduled by m-cc DCI.

[0286] ■ Alternatively, when format_X is configured for SS#k configured on the scheduling cell, format_L may be configured for SS#k on the (scheduled) cell scheduled by m-cc DCI. In this case, format_L may be limited to the legacy DCI format 0_1 ​​or 1_1.

[0287] ■ Alternatively, when format_X is configured for SS#k configured on the scheduling cell, no DCI format may be configured on SS#k on the (scheduled) cell scheduled by m-cc DCI.

[0288] (2) When both format_X and format_L are configured for SS#k configured on the scheduling cell, an SS link between the scheduling cell and the scheduled cell can be established through SS#k. In this case, format_L can be limited to the traditional DCI format 0_1 ​​or 1_1. In other words, the SS set link between the scheduling cell and the scheduled cell for multi-cell scheduling can be configured / applied through the SS set configured with format_X. The above method can be applied to establish an SS set link and / or determine the scheduled cell. Alternatively, method 2 and method 3 in [5] can be applied, which allows the inclusion of a scheduled cell that has no SS link with the scheduling cell.

[0289] ■ When both format_X and format_L are configured as the DCI format for SS#k configured on the scheduling cell, the format_X set or both format_X and format_L may be configured for SS#k on the (scheduled) cell scheduled by m-cc DCI.

[0290] ■ Alternatively, when both format_X and format_L are configured for SS#k configured on the scheduling cell, format_L may be configured for SS#k on the (scheduled) cell scheduled by m-cc DCI. In this case, format_L may be limited to the legacy DCI format 0_1 ​​or 1_1.

[0291] ■ Alternatively, when both format_X and format_L are configured for SS#k configured on the scheduling cell, no DCI format may be configured for SS#k on the (scheduled) cell scheduled by m-cc DCI.

[0292] In addition (detailed description), in scheduling through m-cc DCI, if format_X is defined as configurable on the scheduled cell, SS links can be established only for the SS set configured with format_X (on the scheduled cell). If only format_L is configurable on the scheduled cell (and format_X is defined as not configured), SS links can be established only for the SS set configured with a specific format_L (on the scheduled cell). In this case, the specific format_L may be DCI format 0_1 ​​or DCI format 1_1 (and / or DCI format 0_2 or DCI format 1_2).

[0293] For example, if format_X is defined as configurable in the scheduled cell (and format_X is defined as configurable in the scheduling cell), SS links may be established only between the SS set on the scheduling cell configured with format_X and the SS set on the scheduled cell configured with format_X (having the same index / ID as the SS set in the scheduling cell). In another example, if only format_L is configurable in the scheduled cell (and format_X is defined as configurable in the scheduling cell), SS links may be established only between the SS set on the scheduling cell configured with format_X and the SS set on the scheduled cell configured with format_L (e.g., DCI format 0_1 / 1_1 and / or DCI format 0_2 / 1_2) (having the same index / ID as the SS set in the scheduling cell).

[0294] The content of the present disclosure is not limited to being applied only to UL and / or DL ​​signal transmission and reception. For example, the content of the present disclosure can also be used for direct communication between UEs. In this article, the term base station (BS) can be understood as including the concept of relay node and BS. For example, the operation of the BS described in the present disclosure can be performed by a relay node and a BS.

[0295] Obviously, each of the examples of the proposed method may also be included as an implementation method of the present disclosure, and therefore each example may be regarded as a proposed method. Although the above-mentioned proposed methods may be implemented independently, some of the proposed methods may be combined and implemented. In addition, it may be regulated to send information about whether the proposed method is applied (or information about rules related to the proposed method) in a predefined signal (e.g., physical layer signaling or high-layer signaling) from the BS to the UE.

[0296] Implementation Example

[0297] Figure 4 is a flow chart illustrating a signal monitoring method according to an embodiment of the present disclosure.

[0298] Reference Figure 4 , an implementation performed by the UE may include receiving an SS set configuration (S401) and monitoring PDCCH candidates based on the SS set configuration (S403).

[0299] Monitoring of PDCCH candidates may be performed based on one or more operations described in sections [1] to [5].

[0300] For example, referring to part [2], the number of PDCCH candidates per CCE AL may be configured for the UE through SS set configuration. Since the UE receives the SS set configuration from the BS, the UE receives information about the number of PDCCH candidates per CCE AL via the SS set configuration.

[0301] The UE can monitor multiple PDCCH candidates to decode the PDCCH carrying multi-cell DCI. The cell on which the PDCCH carrying multi-cell DCI is received is defined as the scheduling cell. If the DCI format of the multi-cell DCI is called DCIformat_X, information about DCIformat_X is included in the SS set configuration. The UE monitors the PDCCH candidates for the DCI format on the scheduling cell based on the SS set configuration. The number of monitored PDCCH candidates may correspond to the number of PDCCH candidates per AL configured based on the SS set configuration.

[0302] Multi-cell DCI schedules PDSCH or PUSCH on different scheduled cells. Therefore, DCI format_X is a DCI format used to schedule PDSCH or PUSCH on different scheduled cells. In this specification and claims, the term "DCI" can be used interchangeably with the term "DCI format".

[0303] Referring to the standard in section [2], the number of PDCCH candidates per AL, denoted as PC_m(n), is configured based on the set of scheduled cells that can be scheduled by multi-cell DCI.

[0304] Specifically, referring to Criterion 2 in section [2], for example, for a multi-cell DCI capable of simultaneously scheduling up to three scheduled cells, PC_m(n) is independently configured for each set of all or some of the three scheduled cells. If the multi-cell DCI is capable of simultaneously scheduling up to n scheduled cells, PC_m(n) is independently configured for each set of all or some of the n scheduled cells. The set of all or some of the scheduled cells consists of the cells that are actually scheduled simultaneously at a given time by a single DCI among the n scheduled cells that can be simultaneously scheduled.

[0305] For example, if a multi-cell DCI capable of scheduling up to n scheduled cells is received in time slot A, and the multi-cell DCI schedules the PDSCH or PUSCH of three scheduled cells, the PC_m(n) for the multi-cell DCI received in time slot A is configured based on the values ​​corresponding to the three scheduled cells.

[0306] If a multi-cell DCI capable of scheduling up to n scheduled cells is received in time slot B, and the multi-cell DCI schedules PDSCH or PUSCH of four scheduled cells, PC_m(n) for the multi-cell DCI received in time slot B is configured based on the values ​​corresponding to the four scheduled cells.

[0307] If a multi-cell DCI capable of scheduling up to n scheduled cells is received in time slot C, and if the multi-cell DCI schedules PDSCH or PUSCH of three scheduled cells, but at least one of the three cells is different from the cell scheduled in time slot A, the PC_m(n) for the multi-cell DCI received in time slot A and the PC_m(n) for the multi-cell DCI received in time slot C are configured independently.

[0308] Referring to method 3 in section [2], PC_m(n) can be configured based on the number of PDCCH candidates per AL of a specific representative cell among the scheduled cells. According to criterion 2 in section [2], since PC_m(n) is configured based on a set of cells that can be scheduled by m-ccDCI, the representative cell is one of the cells that can be scheduled simultaneously by DCI.

[0309] The representative cell can be the cell with the lowest index among all simultaneously schedulable cells, the cell with the highest index among all simultaneously schedulable cells, the cell with the minimum number of PDCCH candidates for a specific AL, or the cell with the maximum number of PDCCH candidates for a specific AL. Although the actual scheduled cell set can change each time the DCI is sent, the range of all cells that can be scheduled by the DCI remains constant (unless reconfigured by RRC signaling), regardless of the transmission time of the DCI. Therefore, even if the set of cells scheduled at the same time changes, the representative cell can still remain consistent. Therefore, even if the representative cell is not included in the actual scheduled cell set at a specific point in time, PC_m(n) can still be configured based on the number of PDCCH candidates per AL for the representative cell among the scheduled cells.

[0310] Alternatively, if the representative cell is fixed by higher layer signaling, the set of cells scheduled by the multi-cell DCI may always include the representative cell.

[0311] According to method 3 in section [2], PC_m(n) may be configured to be equal to the number of PDCCH candidates per CCE AL configured for the representative cell. Alternatively, PC_m(n) may be set to a fraction of the number of PDCCH candidates per CCE AL configured for the representative cell. Thus, the SS set configuration received by the UE for monitoring PDCCH candidates for a DCI format on a scheduling cell may be the SS set configuration for the representative cell.

[0312] According to section [5], the SS of the scheduling cell is linked to the SS of at least one scheduled cell. When the SS configured in the scheduling cell and the SS configured in the scheduled cell have the same SSID (configured by searchSpaceId), the SS is considered to be linked (SSs with the same searchSpaceId in the scheduled cell and the scheduling cell are linked to each other).

[0313] When the scheduled cell of the SS linked to the SS of the scheduling cell is called a specific cell, there may be multiple specific cells among the scheduled cells. According to method 3 in section [5], the cell set actually scheduled by the multi-cell DCI may include both specific cells and non-specific cells. Non-specific cells refer to cells that are not configured with SS linked to the SS of the scheduling cell.

[0314] In addition, according to section [5], the DCI format can be configured on the scheduling cell through SS set configuration (eg, via the parameter SearchSpace of RRC signaling). Table 11 shows the parameters for configuring the conventional DCI format.

[0315] [Table 11]

[0316]

[0317]

[0318] When the DCI format of the multi-cell DCI is referred to as DCI format_X, the parameter for configuring DCI format_X may be represented as dci-Format X. The DCI-FormatX parameter includes only information about the DCI format of the multi-cell DCI. X may be represented by a specific format number similar to the conventional format, such as 0_3, 1_3, 5_0, 5_1, 5_2, 6_0, 6_1, 6_2, etc.

[0319] Alternatively, the parameter for configuring DCI format_X may be expressed as dci-FormatX-AndFormatL. The dci-FormatX-AndFormatL parameter includes information about both the DCI format for multi-cell DCI and the conventional DCI format not for multi-cell DCI. X may be represented by a specific format number similar to the conventional format, such as 0_3, 1_3, 5_0, 5_1, 5_2, 6_0, 6_1, 6_2, etc. L represents one of the conventional DCI formats, such as 0_0, 0_1, 1_0, 1_1, etc.

[0320] The SS is configured in the scheduling unit through the dci-FormatX parameter and / or the dci-FormatX-AndFormatL parameter. If the SSID of the SS configured in the scheduling cell is the same as the SSID of the SS configured in the specific scheduled cell, a link is established between the two SSs.

[0321] Except in Figure 4 In addition to the operations described in Figures 1 to 3 One or more operations described in and / or operations for “DCI for scheduling PDSCH or PUSCH on multiple serving cells” described in sections [1] to [5] may be combined and additionally performed.

[0322] Example of a communication system to which the present disclosure is applied

[0323] The various descriptions, functions, processes, proposals, methods and / or operational flowcharts of the present disclosure described herein may be applied to (but not limited to) various fields (e.g., 5G) where wireless communication / connection between devices is required.

[0324] In the following, more specific examples are described with reference to the accompanying drawings. In the following drawings / descriptions, unless otherwise specified, the same reference numerals represent the same or corresponding hardware blocks, software blocks or functional blocks.

[0325] Figure 5 A communication system 1 applied to the present disclosure is illustrated.

[0326] Reference Figure 5, the communication system 1 applied to the present disclosure includes a wireless device, a BS, and a network. The wireless device is a device that performs communication using a radio access technology (RAT) (e.g., 5G NR (or new RAT) or LTE), also referred to as a communication / radio / 5G device. The wireless device may include (but is not limited to) a robot 100a, a vehicle 100b-1 and 100b-2, an extended reality (XR) device 100c, a handheld device 100d, a home appliance 100e, an IoT device 100f, and an artificial intelligence (AI) device / server 400. For example, a vehicle may include a vehicle with a wireless communication function, an autonomous driving vehicle, and a vehicle capable of vehicle-to-vehicle (V2V) communication. Herein, a vehicle may include an unmanned aerial vehicle (UAV) (e.g., a drone). The XR device may include an augmented reality (AR) / virtual reality (VR) / mixed reality (MR) device, and may be implemented in the form of a head-mounted device (HMD), a head-up display (HUD) installed in a vehicle, a television (TV), a smart phone, a computer, a wearable device, a home appliance, a digital signage, a vehicle, a robot, and the like. Handheld devices may include smart phones, smart boards, wearable devices (e.g., smart watches or smart glasses), and computers (e.g., laptop computers). Home appliances may include TVs, refrigerators, washing machines, etc. IoT devices may include sensors, smart meters, etc. For example, a BS and a network may be implemented as wireless devices, and a specific wireless device 200a may operate as a BS / network node for other wireless devices.

[0327] The wireless devices 100a to 100f may be connected to the network 300 via the BS 200. AI technology may be applied to the wireless devices 100a to 100f, and the wireless devices 100a to 100f may be connected to the AI ​​server 400 via the network 300. The network 300 may be configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. Although the wireless devices 100a to 100f may communicate with each other via the BS 200 / network 300, the wireless devices 100a to 100f may perform direct communication (e.g., side link communication) with each other without the intervention of the BS / network. For example, the vehicles 100b-1 and 100b-2 may perform direct communication (e.g., V2V / vehicle-to-everything (V2X) communication). An IoT device (e.g., a sensor) may perform direct communication with other IoT devices (e.g., a sensor) or other wireless devices 100a to 100f.

[0328] Wireless communication / connection 150a, 150b and 150c may be established between wireless devices 100a to 100f / BS200 and between BS200. Herein, wireless communication / connection may be established through various RATs (e.g., 5G NR) such as UL / DL communication 150a, side link communication 150b (or D2D communication) or inter-BS communication (e.g., relay or integrated access backhaul (IAB)). Wireless signals may be sent and received between wireless devices, between wireless devices and BSs, and between BSs through wireless communication / connection 150a, 150b and 150c. For example, signals may be sent and received via various physical channels through wireless communication / connection 150a, 150b and 150c. To this end, at least a portion of various configuration information for configuring processes for sending / receiving wireless signals, various signal processing processes (e.g., channel coding / decoding, modulation / demodulation and resource mapping / demapping) and resource allocation processes may be performed based on various proposals of the present disclosure.

[0329] Example of wireless device to which the present disclosure is applied

[0330] Figure 6 A wireless device suitable for use with the present disclosure is shown.

[0331] Reference Figure 6 , the first wireless device 100 and the second wireless device 200 may transmit wireless signals via various RATs (e.g., LTE and NR). {The first wireless device 100 and the second wireless device 200} may correspond to Figure 5 {wireless device 100x and BS 200} and / or {wireless device 100x and wireless device 100x}.

[0332] The first wireless device 100 may include one or more processors 102 and one or more memories 104, and also include one or more transceivers 106 and / or one or more antennas 108. The processor 102 may control the memory 104 and / or the transceiver 106, and may be configured to implement the description, functions, processes, proposals, methods, and / or operation flowcharts disclosed herein. For example, the processor 102 may process the information in the memory 104 to generate first information / signals, and then transmit a wireless signal including the first information / signals through the transceiver 106. The processor 102 may receive a wireless signal including second information / signals through the transceiver 106, and then store information obtained by processing the second information / signals in the memory 104. The memory 104 may be connected to the processor 102, and may store various information related to the operation of the processor 102. For example, the memory 104 may store software codes including instructions for executing all or part of the processing controlled by the processor 102 or for executing the description, functions, processes, proposals, methods, and / or operation flowcharts disclosed herein. The processor 102 and the memory 104 may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). The transceiver 106 may be connected to the processor 102 and transmit and / or receive wireless signals through one or more antennas 108. Each transceiver 106 may include a transmitter and / or a receiver. The transceiver 106 may be used interchangeably with a radio frequency (RF) unit. In the present disclosure, the wireless device may be a communication modem / circuit / chip.

[0333] The second wireless device 200 may include one or more processors 202 and one or more memories 204, and also include one or more transceivers 206 and / or one or more antennas 208. The processor 202 may control the memory 204 and / or the transceiver 206, and may be configured to implement the description, functions, processes, proposals, methods, and / or operation flowcharts disclosed herein. For example, the processor 202 may process the information in the memory 204 to generate third information / signals, and then transmit a wireless signal including the third information / signals through the transceiver 206. The processor 202 may receive a wireless signal including fourth information / signals through the transceiver 106, and then store information obtained by processing the fourth information / signals in the memory 204. The memory 204 may be connected to the processor 202 and store various information related to the operation of the processor 202. For example, the memory 204 may store software codes including instructions for executing all or part of the processing controlled by the processor 202 or for executing the description, functions, processes, proposals, methods, and / or operation flowcharts disclosed herein. The processor 202 and the memory 204 may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). The transceiver 206 may be connected to the processor 202 and transmit and / or receive wireless signals through one or more antennas 208. Each transceiver 206 may include a transmitter and / or a receiver. The transceiver 206 may be used interchangeably with an RF unit. In the present disclosure, a wireless device may be a communication modem / circuit / chip.

[0334] Now, the hardware elements of the wireless devices 100 and 200 will be described in more detail. One or more protocol layers may be implemented by (but not limited to) one or more processors 102 and 202. For example, one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as physical (PHY), medium access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), RRC, and service data adaptation protocol (SDAP)). One or more processors 102 and 202 may generate one or more protocol data units (PDUs) and / or one or more service data units (SDUs) according to the descriptions, functions, processes, proposals, methods, and / or operational flowcharts disclosed herein. One or more processors 102 and 202 may generate messages, control information, data, or information according to the descriptions, functions, processes, proposals, methods, and / or operational flowcharts disclosed herein, and provide these messages, control information, data, or information to one or more transceivers 106 and 206. One or more processors 102 and 202 may generate a signal (e.g., a baseband signal) including a PDU, SDU, message, control information, data, or information according to the description, functions, procedures, proposals, methods, and / or operational flowcharts disclosed herein, and provide the generated signal to one or more transceivers 106 and 206. One or more processors 102 and 202 may receive a signal (e.g., a baseband signal) from one or more transceivers 106 and 206 and obtain the PDU, SDU, message, control information, data, or information according to the description, functions, procedures, proposals, methods, and / or operational flowcharts disclosed herein.

[0335] One or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. One or more processors 102 and 202 may be implemented by hardware, firmware, software, or a combination thereof. For example, one or more application specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), or one or more field programmable gate arrays (FPGAs) may be included in one or more processors 102 and 202. The descriptions, functions, processes, proposals, methods, and / or operational flow charts disclosed herein may be implemented using firmware or software, and the firmware or software may be configured to include modules, processes, or functions. Firmware or software configured to perform the descriptions, functions, processes, proposals, methods, and / or operational flow charts disclosed herein may be included in one or more processors 102 and 202 or may be stored in one or more memories 104 and 204 and driven by one or more processors 102 and 202. The descriptions, functions, processes, proposals, methods and / or operational flow charts disclosed herein may be implemented in the form of codes, instructions and / or instruction sets using firmware or software.

[0336] One or more memories 104 and 204 may be connected to one or more processors 102 and 202 and store various types of data, signals, messages, information, programs, codes, instructions and / or commands. One or more memories 104 and 204 may be configured to include read-only memory (ROM), random access memory (RAM), electrically erasable programmable read-only memory (EPROM), flash memory, hard drive, registers, cache memory, computer-readable storage media and / or combinations thereof. One or more memories 104 and 204 may be located inside and / or outside of one or more processors 102 and 202. One or more memories 104 and 204 may be connected to one or more processors 102 and 202 via various technologies such as wired or wireless connections.

[0337] One or more transceivers 106 and 206 may send user data, control information and / or wireless signals / channels mentioned in the method and / or operation flow chart of this article to one or more other devices. One or more transceivers 106 and 206 may receive user data, control information and / or wireless signals / channels mentioned in the description, function, process, proposal, method and / or operation flow chart disclosed in this article from one or more other devices. For example, one or more transceivers 106 and 206 may be connected to one or more processors 102 and 202 and send and receive wireless signals. For example, one or more processors 102 and 202 may perform control so that one or more transceivers 106 and 206 may send user data, control information or wireless signals to one or more other devices. One or more processors 102 and 202 may perform control so that one or more transceivers 106 and 206 may receive user data, control information or wireless signals from one or more other devices. One or more transceivers 106 and 206 may be connected to one or more antennas 108 and 208, and one or more transceivers 106 and 206 may be configured to send and receive user data, control information and / or radio signals / channels mentioned in the description, functions, processes, proposals, methods and / or operation flow charts disclosed herein through one or more antennas 108 and 208. In this document, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers 106 and 206 may convert the received wireless signals / channels from RF band signals to baseband signals so as to process the received user data, control information and wireless signals / channels using one or more processors 102 and 202. One or more transceivers 106 and 206 may convert the user data, control information and wireless signals / channels processed using one or more processors 102 and 202 from baseband signals to RF band signals. To this end, one or more of the transceivers 106 and 206 may include (analog) oscillators and / or filters.

[0338] Example of use of wireless device to which the present disclosure is applied

[0339] Figure 7 Another example of a wireless device applicable to the present disclosure is shown. The wireless device can be used according to the usage / service (refer to Figure 5 ) are implemented in various forms.

[0340] Reference Figure 7 , the wireless devices 100 and 200 may correspond to Figure 6The wireless devices 100 and 200 of the present invention may be configured to include various elements, components, units / parts and / or modules. For example, each of the wireless devices 100 and 200 may include a communication unit 110, a control unit 120, a memory unit 130 and an additional component 140. The communication unit 110 may include a communication circuit 112 and a transceiver 114. For example, the communication circuit 112 may include Figure 6 One or more processors 102 and 202 and / or one or more memories 104 and 204. For example, the transceiver 114 may include Figure 6 The control unit 120 is electrically connected to the communication unit 110, the memory 130, and the additional components 140, and provides overall control of the wireless device. For example, the control unit 120 may control the electrical / mechanical operation of the wireless device based on the program / code / instruction / information stored in the memory unit 130. The control unit 120 may send information stored in the memory unit 130 to the outside (e.g., other communication devices) via the communication unit 110 through a wireless / wired interface, or store information received from the outside (e.g., other communication devices) via the communication unit 110 in the memory unit 130 through a wireless / wired interface.

[0341] The additional component 140 may be configured in various ways depending on the type of wireless device. For example, the additional component 140 may include at least one of a power supply unit / battery, an input / output (I / O) unit, a drive unit, and a computing unit. The wireless device may be configured in (but not limited to) a robot ( Figure 5 100a), vehicles ( Figure 5 100b-1 and 100b-2), XR devices ( Figure 5 100c), handheld device ( Figure 5 100d), household appliances ( Figure 5 100e), IoT devices ( Figure 5 100f), digital broadcasting terminal, holographic device, public safety device, MTC device, medical device, fintech device (or financial device), security device, climate / environmental device, AI server / device ( Figure 5 400), BS( Figure 5 200), network nodes, etc. Depending on the use case / service, the wireless device can be mobile or fixed.

[0342] exist Figure 7In the wireless devices 100 and 200, various elements, components, units / parts and / or modules in the wireless devices 100 and 200 may all be connected to each other through a wired interface, or at least a part thereof may be wirelessly connected through the communication unit 110. For example, in each of the wireless devices 100 and 200, the control unit 120 and the communication unit 110 may be wired, and the control unit 120 and the first unit (e.g., 130 and 140) may be wirelessly connected through the communication unit 110. The various elements, components, units / parts and / or modules in the wireless devices 100 and 200 may also include one or more elements. For example, the control unit 120 may be configured using a collection of one or more processors. For example, the control unit 120 may be configured using a collection of a communication control processor, an application processor, an electronic control unit (ECU), a graphics processing unit and a memory control processor. In another example, the memory 130 may be configured using RAM, dynamic RAM (DRAM), ROM, flash memory, volatile memory, non-volatile memory and / or a combination thereof.

[0343] Examples of vehicles or autonomous driving vehicles to which the present disclosure is applied

[0344] Figure 8 A vehicle or an autonomous vehicle applied to the present disclosure is shown. The vehicle or the autonomous vehicle may be implemented as a mobile robot, a car, a train, a manned / unmanned aerial vehicle (AV), a ship, etc.

[0345] Reference Figure 8 , the vehicle or autonomous driving vehicle 100 may include an antenna unit 108, a communication unit 110, a control unit 120, a drive unit 140a, a power supply unit 140b, a sensor unit 140c, and an autonomous driving unit 140d. The antenna unit 108 may be configured as a part of the communication unit 110. Blocks 110 / 130 / 140a to 140d correspond to Figure 7 Frame 110 / 130 / 140.

[0346] The communication unit 110 may send and receive signals (e.g., data and control signals) to and from external devices such as other vehicles, BSs (e.g., gNBs and roadside units), and servers. The control unit 120 may perform various operations by controlling elements of the vehicle or autonomous driving vehicle 100. The control unit 120 may include an ECU. The drive unit 140a may enable the vehicle or autonomous driving vehicle 100 to travel on a road. The drive unit 140a may include an engine, a motor, a power system, wheels, brakes, a steering device, etc. The power supply unit 140b may supply power to the vehicle or autonomous driving vehicle 100, and include a wired / wireless charging circuit, a battery, etc. The sensor unit 140c may acquire information about the vehicle status, surrounding environment information, user information, etc. The sensor unit 140c may include an inertial measurement unit (IMU) sensor, a collision sensor, a wheel sensor, a speed sensor, a slope sensor, a weight sensor, a heading sensor, a position module, a vehicle forward / reverse sensor, a battery sensor, a fuel sensor, a tire sensor, a steering sensor, a temperature sensor, a humidity sensor, an ultrasonic sensor, a lighting sensor, a pedal position sensor, etc. The autonomous driving unit 140d may implement a technology for maintaining a lane in which the vehicle is traveling, a technology for automatically adjusting a speed (e.g., adaptive cruise control), a technology for autonomously traveling along a determined path, a technology for traveling by automatically setting a route if a destination is set, and the like.

[0347] For example, the communication unit 110 may receive map data, traffic information data, etc. from an external server. The autonomous driving unit 140d may generate an autonomous driving route and a driving plan from the obtained data. The control unit 120 may control the drive unit 140a so that the vehicle or the autonomous driving vehicle 100 may move along the autonomous driving route according to the driving plan (e.g., speed / direction control). During autonomous driving, the communication unit 110 may aperiodically / periodically obtain the latest traffic information data from the external server and obtain surrounding traffic information data from neighboring vehicles. During autonomous driving, the sensor unit 140c may obtain information about the vehicle state and / or surrounding environment information. The autonomous driving unit 140d may update the autonomous driving route and driving plan based on the newly obtained data / information. The communication unit 110 may transmit information about the vehicle position, autonomous driving route, and / or driving plan to an external server. The external server may predict traffic information data using AI technology based on information collected from the vehicle or autonomous driving vehicle, and provide the predicted traffic information data to the vehicle or autonomous driving vehicle.

[0348] Those skilled in the art will appreciate that the present disclosure may be implemented in other specific ways than those described herein without departing from the spirit and essential characteristics of the present disclosure. Therefore, the above-described embodiments are to be interpreted in all respects as being illustrative and not restrictive. The scope of the present disclosure should be determined by the appended claims and their legal equivalents (rather than the above description), and all changes falling within the meaning and equivalent scope of the appended claims are intended to be included therein.

[0349] Industrial Applicability

[0350] As described above, the present disclosure is applicable to various wireless communication systems.

Claims

1. A method for monitoring a control signal by a user equipment UE in a wireless communication system, the method comprising: receiving a search space set configuration including information about a number of physical downlink control channel (PDCCH) candidates for each control channel element (CCE) aggregation level; as well as monitoring the PDCCH candidates for the downlink control information DCI format on the scheduling cell based on the search space set configuration, The DCI format is a DCI format used for scheduling a physical downlink shared channel PDSCH or a physical uplink shared channel PUSCH on different scheduled cells, and The number of the PDCCH candidates is configured based on all scheduled cells or a set of some scheduled cells among the scheduled cells.

2. The method according to claim 1, wherein: The set includes cells that are actually scheduled at the same time among the scheduled cells that can be scheduled through the DCI format.

3. The method according to claim 1, wherein: The number of PDCCH candidates is independently configured for each set.

4. The method according to claim 1, wherein: The number of the PDCCH candidates is determined based on representative cells included in the set.

5. The method according to claim 4, wherein: The number of the PDCCH candidates is equal to the number of PDCCH candidates for each CCE aggregation level configured for the representative cell.

6. The method according to claim 4, wherein: The search space set configuration is the search space set configuration of the representative cell.

7. The method according to claim 1, wherein: The search space configured on the scheduling cell and the search space configured on at least one specific cell among the scheduled cells are linked to each other through the same search space identifier ID.

8. The method according to claim 7, wherein: The set includes not only the specific cell but also cells except the specific cell.

9. The method according to claim 7, wherein: The search space set configuration of the scheduling cell includes parameters for configuring the DCI format, and The parameters only include information about the DCI format.

10. The method according to claim 7, wherein: The search space set configuration of the scheduling cell includes parameters for configuring the DCI format, and The parameter includes information about the DCI format and another DCI format different from the DCI format.

11. A user equipment (UE) configured to monitor a signal in a wireless communication system, the UE comprising: at least one transceiver; at least one processor; as well as At least one memory, the at least one memory being operatively connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform specific operations including: receiving a search space set configuration including information on the number of physical downlink control channel (PDCCH) candidates for each control channel element (CCE) aggregation level; and monitoring the PDCCH candidates for the downlink control information DCI format on the scheduling cell based on the search space set configuration, The DCI format is a DCI format used for scheduling a physical downlink shared channel PDSCH or a physical uplink shared channel PUSCH on different scheduled cells, and The number of the PDCCH candidates is configured based on all scheduled cells or a set of some scheduled cells among the scheduled cells.

12. A device for a user equipment UE, the device comprising: at least one processor; as well as At least one computer memory, the at least one computer memory being operably connected to the at least one processor and configured, when executed, to cause the at least one processor to perform operations comprising: receiving a search space set configuration including information on the number of physical downlink control channel (PDCCH) candidates for each control channel element (CCE) aggregation level; and monitoring the PDCCH candidates for the downlink control information DCI format on the scheduling cell based on the search space set configuration, The DCI format is a DCI format used for scheduling a physical downlink shared channel PDSCH or a physical uplink shared channel PUSCH on different scheduled cells, and The number of the PDCCH candidates is configured based on all scheduled cells or a set of some scheduled cells among the scheduled cells.

13. A computer-readable non-volatile storage medium comprising at least one computer program, the at least one computer program being configured to cause at least one processor to perform operations comprising: receiving a search space set configuration including information on the number of physical downlink control channel (PDCCH) candidates for each control channel element (CCE) aggregation level; and monitoring the PDCCH candidates for the downlink control information DCI format on the scheduling cell based on the search space set configuration, in, The DCI format is a DCI format used for scheduling a physical downlink shared channel PDSCH or a physical uplink shared channel PUSCH on different scheduled cells, and The number of the PDCCH candidates is configured based on all scheduled cells or a set of some scheduled cells among the scheduled cells.