Method and apparatus for monitoring signals in a wireless communication system - Patents.com

Abstract

The method and apparatus for monitoring signals in a wireless communication system according to the present invention monitors PDCCH candidates for a DCI format based on a CCE index, the DCI format being monitored on a scheduling cell and scheduling PDSCHs or PUSCHs on multiple scheduled cells.

Description

[Technical field]

[0001] The present invention relates to a method and apparatus for use in a wireless communication system. [Background technology]

[0002] Wireless communication systems have been widely deployed to provide various communication services such as voice and data. In general, wireless communication systems are multiple access systems that can support communication with multiple users by sharing available system resources (bandwidth, transmission power, etc.). Examples of multiple access systems include Code Division Multiple Access (CDMA) systems, Frequency Division Multiple Access (FDMA) systems, Time Division Multiple Access (TDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, etc. Summary of the Invention [Problem to be solved by the invention]

[0003] An object of the present invention is to provide a signal monitoring method and an apparatus therefor for efficiently monitoring control signals in a wireless communication system.

[0004] The technical object of the present invention is not limited to the above-mentioned technical object, and other technical objects can be inferred from the embodiments of the present invention. [Means for solving the problem]

[0005] The present invention provides a method and apparatus for signal monitoring in a wireless communication system.

[0006] As one embodiment of the present invention, there is provided a signal monitoring method for a terminal in a wireless communication system to monitor a control signal, the signal monitoring method including: determining a control channel element (CCE) index corresponding to a PDCCH candidate; and monitoring the PDCCH candidate for a downlink control information (DCI) format on a scheduling cell based on the CCE index, wherein, based on the DCI format being a first DCI format for scheduling a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH) on one scheduled cell, the CCE index is set based on a carrier indicator field (CIF) value included in the DCI format, and, based on the DCI format being a second DCI format for scheduling a PDSCH or a PUSCH on a plurality of scheduled cells, the CCE index is set independently for each combination of all or a portion of the plurality of scheduled cells.

[0007] In another embodiment of the present invention, an apparatus, processor and storage medium for performing a signal monitoring method are provided.

[0008] The apparatus includes at least a terminal, a network, and an autonomous vehicle capable of communicating with other autonomous vehicles other than the apparatus.

[0009] The above-described aspects of the present invention are merely some of the preferred embodiments of the present invention, and various embodiments reflecting the technical features of the present invention will be understood and derived by those having ordinary skill in the art based on the detailed description of the present invention described below. Effect of the Invention

[0010] According to an embodiment of the present invention, when a control signal is monitored between communication devices, there is an advantage that more efficient signal monitoring can be performed due to an operation differentiated from the conventional invention.

[0011] The technical effects of the present invention are not limited to the above-mentioned technical effects, and other technical effects may be inferred from the embodiments of the present invention. [Brief description of the drawings]

[0012] [Figure 1] FIG. 1 illustrates a structure of a radio frame. [Diagram 2] FIG. 2 illustrates a resource grid of slots. [Diagram 3] A diagram showing an example of mapping physical channels within a slot. [Figure 4] FIG. 2 illustrates a method of signal monitoring according to an embodiment of the present invention. [Diagram 5] FIG. 1 illustrates an apparatus according to one embodiment of the present invention. [Figure 6] FIG. 1 illustrates an apparatus according to one embodiment of the present invention. [Figure 7] FIG. 1 illustrates an apparatus according to one embodiment of the present invention. [Figure 8] FIG. 1 illustrates an apparatus according to one embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0013] The following technologies can be used for various wireless access systems such as CDMA, FDMA, TDMA, OFDMA, SC-FDMA, etc. CDMA can be implemented by radio technologies such as Universal Terrestrial Radio Access (UTRA) and CDMA2000. TDMA can be implemented by radio technologies such as Global System for Mobile communications (GSM) / General Packet Radio Service (GPRS) / Enhanced Data Rates for GSM Evolution (EDGE). OFDMA can be implemented by radio technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, Evolved UTRA (E-UTRA), etc. UTRA is part of the Universal Mobile Telecommunications System (UMTS). 3GPP (3rd Generation Partnership Project) LTE (long term evolution) is a part of E-UMTS (Evolved UMTS) that uses E-UTRA, and LTE-A / LTE-A pro is an evolved version of 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is an evolved version of 3GPP LTE / LTE-A / LTE-A pro.

[0014] For a clearer explanation, the present invention will be described based on a 3GPP communication system (e.g., LTE-A, NR), but the technical idea of ​​the present invention is not limited thereto. LTE refers to technology after 3GPP TS 36.xxx Release 8. In particular, LTE technology after 3GPP TS 36.xxx Release 10 is called LTE-A, and LTE technology after 3GPP TS 36.xxx Release 13 is called LTE-A pro. 3GPP NR refers to technology after TS 38.xxx Release 15. LTE / NR can also be called a 3GPP system. "xxx" refers to the detailed number of the standard document. LTE / NR is called a 3GPP system. For background technology, terms, abbreviations, etc. used in the description of the present invention, please refer to the matters described in the standard documents published before the present invention. For example, the following documents can be referred to.

[0015] 3GPP NR

[0016] - 38.211:Physical channels and modulation

[0017] - 38.212:Multiplexing and channel coding

[0018] - 38.213:Physical layer procedures for control

[0019] - 38.214:Physical layer procedures for data

[0020] - 38.300:NR and NG-RAN Overall Description

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

[0022] FIG. 1 illustrates the structure of a radio frame used in NR.

[0023] In NR, uplink and downlink transmissions are composed of frames. A radio frame has a length of 10 ms and is defined as two 5 ms half-frames (Half-Frame, HF). A half-frame is defined as five 1 ms subframes (Subframe, SF). A subframe is divided into one or more slots, and the number of slots in a subframe depends on the Subcarrier Spacing (SCS). Each slot contains 12 or 14 OFDM(A) symbols depending on the cyclic prefix (CP). If a general CP is used, each slot contains 14 symbols. If an extended CP is used, each slot contains 12 symbols. Here, the symbols can include OFDM symbols (or CP-OFDM symbols), SC-FDMA symbols (or DFT-s-OFDM symbols).

[0024] Table 1 illustrates that when a general CP is used, the number of symbols per slot, the number of slots per frame, and the number of slots per subframe change depending on the SCS.

[0025] [Table 1]

[0026] Table 2 illustrates that the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary with the SCS when an extended CP is used.

[0027] [Table 2]

[0028] In the NR system, OFDM(A) neurology (e.g., SCS, CP length, etc.) is set to be different among multiple cells merged to one terminal (User Equipment; UE), so that the (absolute time) duration of time resources (e.g., SF, slot, or TTI) (collectively referred to as TU (Time Unit) for convenience) consisting of the same number of symbols is different among the merged cells.

[0029] NR supports multiple Orthogonal Frequency Division Multiplexing (OFDM) neurologies (e.g., subcarrier spacing, SCS) to support various 5G services. For example, a 15kHz SCS supports wide areas in traditional cellular bands, while a 30kHz / 60kHz SCS supports dense urban areas, lower latency, and wider carrier bandwidth.

[0030] The NR frequency band is defined by two types of frequency ranges (FR1 / FR2). FR1 / FR2 are configured as shown in Table 3 below. FR2 also stands for millimeter wave (mmW).

[0031] [Table 3]

[0032] Figure 2 illustrates the slot structure of an NR frame.

[0033] A slot includes multiple symbols in the time domain. For example, in the case of a general CP, one slot includes 14 symbols, while in the case of an extended CP, one slot includes 12 symbols. A carrier includes multiple subcarriers in the frequency domain. An RB (Resource Block) is defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. In the frequency domain, multiple RB interlaces (or simply, interlaces) are defined. An interlace m ∈ {0, 1, ..., M-1} is composed of (common) RBs {m, M+m, 2M+m, 3M+m, ...}. M indicates the number of interlaces. A BWP (Bandwidth Part) is defined as multiple consecutive PRBs (Physical RBs) in the frequency domain and can correspond to one numerology (e.g., SCS, CP length, etc.). A carrier includes up to N BWPs (e.g., 5). Data communication is performed by an activated BWP, and only one BWP is activated for one terminal. Each element in the resource grid is called a resource element (RE), and one modulation symbol can be mapped to it.

[0034] In a wireless communication system, a terminal receives information from a base station via a downlink (DL), and the terminal transmits information to the base station via an uplink (UL). Information transmitted and received between the base station and the terminal includes data and various control information, and various physical channels / signals exist depending on the type / use of the information transmitted and received. A physical channel corresponds to a set of resource elements (RE) that carry information derived from a higher layer. A physical signal corresponds to a set of resource elements (RE) used by a physical layer (PHY), but does not carry information derived from a higher layer. The higher layers include 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, etc.

[0035] DL physical channels include PBCH (Physical Broadcast channel), PDSCH (Physical Downlink Shared channel) and PDCCH (Physical Downlink Control channel). DL physical signals include DL RS (Reference Signal), PSS (Primary synchronization signal) and SSS (Secondary synchronization signal). DL RS include DM-RS (Demodulation RS), PT-RS (Phase-tracking RS) and CSI-RS (channel-state information RS). UL physical channels include PRACH (Physical Random Access Channel), PUSCH (Physical Uplink Shared Channel) and PUCCH (Physical Uplink Control Channel). UL physical signals include UL RS. UL RS include DM-RS, PT-RS and SRS (Sounding RS).

[0036] FIG. 3 shows an example of mapping physical channels within a slot.

[0037] A DL control channel, DL or UL data, and UL control channel are all included in one slot. For example, the first N symbols in a slot are used to transmit the DL control channel (hereinafter, DL control region), and the last M symbols in a slot are used to transmit the UL control channel (hereinafter, UL control region). N and M are integers equal to or greater than 0. The resource region between the DL control region and the UL control region (hereinafter, data region) is used to transmit DL data or UL data. There is a time gap between the control region and the data region for DL-to-UL or UL-to-DL switching. The PDCCH is transmitted in the DL control region, and the PDSCH is transmitted in the DL data region. Some symbols at the time of switching from DL to UL in a slot are used as the time gap.

[0038] In the present invention, the base station is, for example, a gNodeB.

[0039] Downlink (DL) physical channels / signals

[0040] (1) PDSCH

[0041] The PDSCH carries downlink data (e.g., DL-shared channel transport block, DL-SCH TB). The TB is encoded into a codeword (CW) and then transmitted through a process of scrambling and modulation. The CW includes one or more code blocks (CB). One or more CBs are collected into one CBG (CB group). Depending on the cell configuration, the PDSCH can carry up to two CWs. Scrambling and modulation are performed for each CW, and the modulation symbols generated from each CW are mapped to one or more layers. Each layer is precoded, mapped to resources together with the DMRS, and transmitted from the corresponding antenna port. The PDSCH is dynamically scheduled by the PDCCH (dynamic scheduling) or semi-statically scheduled (Configured Scheduling, CS) based on higher layer (e.g., RRC) signaling (and / or Layer 1 (L1) signaling (e.g., PDCCH)). Thus, in dynamic scheduling, PDSCH transmission is accompanied by a PDCCH, whereas in CS, PDSCH transmission is not accompanied by a PDCCH. CS includes semi-persistent scheduling (SPS).

[0042] (2) PDCCH

[0043] The PDCCH carries Downlink Control Information (DCI). For example, the PCCCH (i.e., DCI) carries the transmission format and resource allocation of DL-SCH, frequency / time resource allocation information for UL-SCH (shared channel), paging information for PCH (paging channel), system information on DL-SCH, frequency / time resource allocation information for higher layer control messages such as voluntary access response (RAR) transmitted on PDSCH, transmission power control command, and information on activation / deactivation of SPS / CS (Configured Scheduling), etc. Various DCI formats are provided depending on the information in the DCI.

[0044] Table 4 illustrates an example of a DCI format transmitted via the PDCCH.

[0045] [Table 4]

[0046] DCI format 0_0 is used to schedule TB-based (or TB-level) PUSCH, and DCI format 0_1 ​​is used to schedule TB-based (or TB-level) PUSCH or CBG (Code Block Group)-based (or CBG-level) PUSCH. DCI format 1_0 is used to schedule TB-based (or TB-level) PDSCH, and DCI format 1_1 is used to schedule TB-based (or TB-level) PDSCH or CBG-based (or CBG-level) PDSCH (DL grant DCI). DCI format 0_0 / 0_1 is referred to as UL grant DCI or UL scheduling information, and DCI format 1_0 / 1_1 is referred to as DL grant DCI or UL scheduling information. DCI format 2_0 is used to deliver dynamic slot format information (e.g., dynamic SFI) to the terminal, and DCI format 2_1 is used to deliver downlink pre-Emption information to the terminal. DCI format 2_0 and / or DCI format 2_1 are transmitted to terminals in a corresponding group via a group common PDCCH, which is a PDCCH transmitted to terminals defined as one group.

[0047] The PDCCH / DCI includes a cyclic redundancy check (CRC), and the CRC is masked / scrambled to various identifiers (e.g., Radio Network Temporary Identifier, RNTI) depending on the owner or use of the PDCCH. For example, if the PDCCH is for a specific terminal, the CRC is masked to Cell-RNTI (C-RNTI). If the PDCCH is related to paging, the CRC is masked to P-RNTI (Paging-RNTI). If the PDCCH is related to system information (e.g., System Information Block, SIB), the CRC is masked to System Information RNTI (SI-RNTI). If the PDCCH is related to an unsolicited access response, the CRC is masked to Random Access-RNTI (RA-RNTI).

[0048] Table 5 shows an example of the use of PDCCH according to RNTI and the transmission channel. The transmission channel indicates the transmission channel related to the data carried by the PDSCH / PUSCH scheduled by the PDCCH.

[0049] [Table 5]

[0050] The modulation method of the PDCCH is fixed (e.g., Quadrature Phase Shift Keying, QPSK), and one PDCCH is composed of 1, 2, 4, 8, or 16 CCEs (Control Channel Elements) depending on the AL (Aggregation Level). One CCE is composed of six REGs (Resource Element Groups). One REG is defined by one OFDM symbol and one (P)RB.

[0051] PDCCH is transmitted in a CORESET (Control Resource Set). CORESET corresponds to a physical resource / parameter set used to carry PDCCH / DCI in BWP. For example, CORESET includes a REG set having a predetermined neurology (e.g., SCS, CP length, etc.). CORESET is configured by system information (e.g., MIB) or UE-specific higher layer (e.g., RRC) signaling. Examples of parameters / information used to configure CORESET are as follows: One or more CORESETs are configured for one UE, and multiple CORESETs are superimposed in the time / frequency domain.

[0052] - controlResourceSetId: Indicates the identification information (ID) of the CORESET.

[0053] - frequencyDomainResources: Indicates the frequency domain resources of the CORESET. It is indicated 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 whose bit value is 1 is assigned to the frequency domain resources of the CORESET.

[0054] - duration: indicates the time domain resource of CORESET. It indicates the number of consecutive OFDMA symbols that constitute CORESET. For example, duration has a value of 1 to 3.

[0055] - cce-REG-MappingType: indicates the CCE-to-REG mapping type. Interleaved and non-interleaved types are supported.

[0056] - precoderGranularity: indicates the precoder granularity in the frequency domain.

[0057] - tci-StateSPDCCH: Indicates information (e.g., TCI-StateID) indicating the TCI (Transmission Configuration Indication) state for the PDCCH. The TCI state is used to provide a Quasi-Co-Location (QCL) relationship between DL RSs and PDCCH DMRS ports in an RS set (TCI-State).

[0058] - tci-PresentInDCI: indicates whether the TCI field in the DCI is included or not.

[0059] - pdcch-DMRS-ScramblingID: indicates information used for initialization of the PDCCH DMRS scrambling sequence.

[0060] For PDCCH reception, the UE monitors a set of PDCCH candidates in the CORESET (e.g., blind decoding). The PDCCH candidates indicate the CCEs that the UE monitors for PDCCH reception / detection. PDCCH monitoring is performed in one or more CORESETs on an active DL BWP on each activated cell where PDCCH monitoring is configured. The set of PDCCH candidates that the UE monitors is defined as a PDCCH Search Space (SS) set. The SS set is a Common Search Space (CSS) set or a UE-specific Search Space (USS) set.

[0061] Table 6 illustrates the PDCCH search space.

[0062] [Table 6]

[0063] The SS set is configured by system information (e.g., MIB) or UE-specific higher layer (e.g., RRC) signaling. S (e.g., 10) or less SS sets are configured in each DL BWP of the serving cell. For example, the following parameters / information are provided for each SS set: Each SS set is associated with one CORESET, and each CORESET configuration is associated with one or more SS sets.

[0064] - searchSpaceId: Indicates the ID of the SS set.

[0065] - controlResourceSetId: Indicates the CORESET associated with the SS set.

[0066] - monitoringSlotPeriodicityAndOffset: indicates the PDCCH monitoring periodicity period (in slot units) and the PDCCH monitoring period offset (in slot units).

[0067] - monitoringSymbolsWithinSlot: indicates the first OFDMA symbol for PDCCH monitoring in a slot where PDCCH monitoring is configured. It 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 OFDMA symbol in the slot. The OFDMA symbol corresponding to a bit whose bit value is 1 corresponds to the first symbol of CORESET in the slot.

[0068] - nrofCandidates: indicates the number of PDCCH candidates for AL={1, 2, 4, 8, 16} (e.g., one of 0, 1, 2, 3, 4, 5, 6, 8).

[0069] - searchSpaceType: indicates whether the SS type is CSS or USS.

[0070] - DCI format: Indicates the DCI format of the PDCCH candidate.

[0071] Based on the CORESET / SS set configuration, the terminal can monitor PDCCH candidates in one or more SS sets in a slot. An occasion (e.g., a time / frequency resource) for monitoring PDCCH candidates is defined as a PDCCH (monitoring) opportunity. One or more PDCCH (monitoring) opportunities are configured in a slot.

[0072] DCI for scheduling PDSCHs or PUSCHs on multiple serving cells

[0073] The above content can be combined with and applied to the method proposed in the present invention as follows, and can clarify the technical features of the method proposed in the present invention.

[0074] The methods described below can be similarly applied to the above-mentioned NR system (licensed band) or shared spectrum, and can be modified or substituted to suit the terms, expressions, structures, etc. defined in each system so that the technical ideas proposed in this specification can be embodied in the relevant systems.

[0075] In order to reduce DCI overhead for PDSCH / PUSCH scheduling in a CA situation where multiple cells are configured, Rel-18 (based on justification such as Table 7) considers a multi-cell scheduling (multi-CC scheduling) scheme in which multiple serving cells / CCs are simultaneously scheduled by a single DCI. In the present invention, the expression "scheduling multiple cells" is understood to mean "scheduling PDSCH or PUSCH transmitted from each of multiple cells." In other words, multi-cell DCI is DCI for scheduling PDSCH or PUSCH on multiple different cells.

[0076] Table 7 is a justification for supporting DCI for the above-mentioned purposes in Rel-18, and is understood as one of the motivations for the need to introduce such DCI (PDCCH).

[0077] [Table 7]

[0078] Here, the present invention proposes a PDCCH monitoring method for DCI (multi-cell DCI) performing multi-cell scheduling as described above and a method for configuring related PDCCH candidates.

[0079] In the proposed method described below, for convenience of explanation, DCI with multi-cell scheduling is denoted as m-cc DCI, and DCI with conventional single-cell scheduling is denoted as s-cc DCI. DCI with PDSCH scheduling and DCI with PUSCH scheduling are not differentiated and are denoted as m-cc DCI or s-cc DCI. Scheduled PDSCH and / or PUSCH are denoted as PDSCH / PUSCH (or PxSCH) depending on the case.

[0080] In the specification, the term "cell" is interpreted according to the context. For example, a cell means a serving cell. Also, a cell can be configured with one DL CC (component carrier) and 0 to 2 UL CCs, but the method described below is not limited to this. Unless otherwise specified in the expressions described below, cell and CC can be used interchangeably. Also, a cell / CC can be replaced with an (active) BWP in a serving cell. Also, unless otherwise specified, in the methods described below, a cell / CC is used as a concept that encompasses a P cell (PCell, primary cell), an S cell (SCell, secondary cell), a PS cell (PSCell, primary SCell), etc., configured / expressed in a CA (carrier aggregation) / DC (dual connectivity) scenario.

[0081] A cell (or CC) that schedules a PDSCH / PUSCH (DL assignment or UL grant) is called a scheduling cell (or scheduling CC), and a cell that actually transmits a PDSCH / PUSCH scheduled by the scheduling cell is called a scheduled cell (or scheduled CC). When the scheduling cell and the scheduled cell are the same, this is called self-carrier scheduling, and when they are different, this is called cross-carrier scheduling.

[0082] Tables 8 and 9 show information elements (IEs) related to cross-carrier scheduling as described in 3GPP TS 38.331.

[0083] [Table 8]

[0084] [Table 9]

[0085] The CCS setting in the NR system is set by CrossCarrierSchedulingConfig, which is a higher layer parameter, as shown in Tables 8 and 9. A carrier indicator field (CIF) value is set in DCI (e.g., DCI format 0_1 / 0_2 / 1_1 / 1_2) that schedules PDSCH or PUSCH, and the value is 0 for the own cell and has a value of 1 to 7 (set by cif-InSchedulingCell) for other cells. Also, as shown in Table 10, the set CIF value is used to determine PDCCH candidates corresponding to the n_CI value. At this time, PDCCH monitoring corresponding to a search space set (SS set) set for a scheduled cell is performed in a PDCCH MO (monitoring occasion) linked to a search space 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) set in the SS set of the scheduled cell is inherited as is, and the number of PDCCH candidates is applied when performing PDCCH monitoring on the scheduled cell in the SS set on the scheduling cell. A PDCCH MO is determined for each SS set s in CORESET p. Up to 10 SS sets are associated with one CORESET, and each is identified by its SS set index.

[0086] [Table 10-1] [Table 10-2]

[0087] As an example, for cell #1 and cell #2, SS set #s is set as follows:

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

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

[0090] At this time, when cross-carrier scheduling is set to determine cell #1 as the scheduling cell for cell #2, the terminal performs the following PDCCH monitoring in PDCCH MOs set in SS set #s on cell #1. Specifically, the PDCCH transmitted in cell #1 can schedule data (e.g., PDSCH or PUSCH) transmitted in cell #2, and the relationship set between cell #1 and cell #2 is referred to as a CCS relationship for convenience. Also, monitoring of PDCCH means monitoring PDCCH candidates.

[0091] - N_1(n) PDCCH candidate monitoring for each AL n for the DCI format configured in SS set #s of cell #1

[0092] - N_2(n) PDCCH candidate monitoring for each AL n for the DCI format configured in SS set #s of cell #2

[0093] How to operate m-cc DCI and s-cc DCI

[0094] In a scenario such as CA consisting of M cells (cell#1 to cell#M, M is an integer equal to or greater than 1), when a connection relationship (e.g., a CCS relationship) between the scheduling cell and other cells is set, one of the following options is set / applied to an m-cc DCI that simultaneously schedules multiple cells and an s-cc DCI that schedules one cell. For convenience of explanation, one cell is represented as cell#k (where k means cell index or k-th cell), and a set of two or more cells is represented using the symbol {}. For example, {cell#1, cell#2} means cell#1 and cell#2. An arbitrary set of M cells is represented as {{cell#m}, M}. In this case, cell#m means each cell in the set (m=1,..., M).

[0095] 1.1-1 Option 1: m-cc DCI is defined to always schedule {{cell#m},M}, where M is an integer equal to or greater than 2. In other words, multiple cells are always scheduled simultaneously by m-cc DCI, and operation in which only one cell is scheduled by m-cc DCI is not allowed. Cell#m is either a scheduling cell that receives m-cc DCI (PDCCH) or a scheduled cell that is scheduled by m-cc DCI.

[0096] 1.1-1a Option 1a: m-cc DCI is defined to always schedule {{cell#m},M}, where M is an integer equal to or greater than 2. Cell#m becomes a scheduled cell scheduled by m-cc DCI.

[0097] 1.1-2 Option 2: m-cc DCI is defined to schedule {{cell#m},M} or to schedule one cell (ref-cc) among {{cell#m},M}. In other words, depending on the m-cc DCI, multiple cells are scheduled simultaneously (multi-cell scheduling) or only one cell is scheduled (single-cell scheduling). In this case, the one cell may be fixed to a specific cell (ref-cc). For other cells that are not the specific cell, single-cell scheduling by the m-cc DCI is not allowed. In this case, M means an integer of 2 or more. Cell#m is a scheduling cell that receives the m-cc DCI (PDCCH) or a scheduled cell scheduled by the m-cc DCI. The reference CC (ref-cc) means one specific cell among {{cell#m},M}, and is predefined or set implicitly or explicitly.

[0098] - A method of predefining ref-cc or setting it implicitly: The cell with the lowest (or highest) index among {{cell#m},M} becomes ref-cc. Or, if a PCell, PSCell, PUCCH SCell, etc. is included in the set, that cell becomes ref-cc. Or, a scheduling cell is selected as ref-cc. Or, among the cells scheduled by m-cc DCI, a cell that is the reference for the CIF value is determined as ref-CC.

[0099] - Explicit configuration of ref-cc: It is configured semi-statically by higher layer signaling such as RRC or MAC-CE, or dynamically by DCI. In this case, the signaled cell index indicates a cell that corresponds to the above-mentioned pre-defined rule (or implicit configuration).

[0100] 1.1-2a Option 2a: m-cc DCI is defined to schedule {{cell#m},M} or to schedule one cell (ref-cc) among {{cell#m},M}, where M is an integer equal to or greater than 1. Cell#m becomes a scheduled cell scheduled by m-cc DCI. ref-cc means one specific cell among {{cell#m},M}, and is predefined or set implicitly or explicitly. The method of setting ref-cc is as described in 1.1-2 Option 2.

[0101] 1.1-3 Option 3: m-cc DCI is defined to schedule {{cell#m},M}, where M is an integer equal to or greater than 1. In other words, depending on the m-cc DCI, multiple cells are scheduled simultaneously, or only one cell is scheduled. Unlike 1.1-2 Option 2, the one cell does not have to be fixed to a specific cell (ref-cc). Cell #m is either a scheduling cell that receives the m-cc DCI (PDCCH) or a scheduled cell that is scheduled by the m-cc DCI.

[0102] 1.1-3a Option 3a: m-cc DCI is defined to schedule {{cell#m},M}, where M is an integer equal to or greater than 1. Cell#m becomes a scheduled cell that is scheduled by m-cc DCI.

[0103] For each of the options, the operation of PDCCH monitoring of a terminal in a cell that schedules m-cc DCI (PDCCH) is defined as follows.

[0104] 1.1-1 Option 1: The terminal expects to receive the m-cc DCI configured in 1.1-1 Option 1. The terminal also expects to receive the s-cc DCI that self-schedules or cross-carrier schedules each cell belonging to {{cell#m}, M} configured as a target for m-cc DCI scheduling.

[0105] 1.1-1a Option 1a: The terminal expects to receive the m-cc DCI set in 1.1-1a Option 1a, and also expects to receive the s-cc DCI that cross-carrier schedules one cell among {{cell#m}, M} or self-schedules the scheduling cell.

[0106] 1.1-2 Option 2: The terminal expects to receive m-cc DCI set in the above 1.1-2 Option 2. In addition, the terminal expects to receive s-cc DCI that performs self- or cross-carrier scheduling on other cells, excluding the specific ref-cc, among the cells belonging to {{cell#m}, M} set as targets for m-cc DCI scheduling.

[0107] 1.1-2a Option 2a: The terminal expects to receive the m-cc DCI set in 1.1-2a Option 2a, and also expects to receive the s-cc DCI that cross-carrier schedules one of {{cell#m}, M} or self-schedules the scheduling cell.

[0108] 1.1-3 Option 3: The terminal expects to receive the m-cc DCI configured in Option 3. At this time, the terminal does not expect to receive the s-cc DCI that self- or cross-carrier schedules any cell belonging to {{cell#m}, M} configured as a target for m-cc DCI scheduling.

[0109] 1.1-3a Option 3a: The terminal expects to receive the m-cc DCI set in 1.1-3a Option 3a. The terminal also expects to receive the s-cc DCI that self-schedules the scheduling cell. In this case, the terminal does not expect to receive the s-cc DCI that cross-carrier schedules one of {{cell#m},M}.

[0110] The proposed methodology described below applies specifically to each of the options listed above.

[0111] For the methods described below, the values ​​proposed / calculated by each method (e.g., the number of PDCCH candidates for each scheduled cell, or the BD counting method, or multiplying or dividing a predetermined value to give a BD budget or weighting value, etc.) are applied to the final result as integer values ​​using a ceil or floor function (even if not specifically described).

[0112] [1] How to set the CIF value for m-cc DCI

[0113] A carrier indicator field (CIF) is set for the s-cc DCI of a conventional NR system. When CCS is performed according to the CIF value, the scheduling cell and the scheduled cell are connected. The number of scheduled cells related to the conventional s-cc DCI is one. The SS set and / or CCS-related configuration is performed for each cell. However, since the m-cc DCI can simultaneously schedule PDSCH / PUSCH for multiple cells, it is necessary to determine which cell among multiple scheduled cells is used as a reference for the SS set and / or CCS-related configuration. The following describes a proposed operation when M cells {{cell#m}, M} are set as targets for m-cc DCI scheduling.

[0114] The SS set configuration and / or CIF value configuration for multiple scheduled CCs scheduled simultaneously by the m-cc DCI is performed in one of the following three reference units.

[0115] - Reference unit 1: SS set#s for m-cc DCI is set, and CIF value for the SS set#s is set. In this case, SS set and CIF value are set for all CC combinations (all CC sets belonging to this) that can be scheduled simultaneously by m-cc DCI. That is, SS set and CIF value for the m-cc DCI itself are set. In this case, the CIF value is set to have a value different from the CIF (single cell CIF) value (for a single CC) set in the conventional (single-cell scheduling) DCI-based (cross-carrier) scheduling. For example, for an m-cc DCI that can simultaneously schedule a maximum of {cell#1, cell#2, cell#3}, the SS set#s and / or CIF value for the m-cc DCI is set without distinguishing between the case of scheduling {cell#1, cell#2} and the case of scheduling {cell#2, cell#3}.

[0116] - Criterion unit 2: SS set and / or CIF value are set for each CC combination scheduled simultaneously by m-cc DCI. In this case, the CIF value for each CC combination is set to have a value different from the CIF (single-cell CIF) value (for a single CC) set in the conventional (single-cell scheduling) DCI-based (cross-carrier) scheduling. For example, for an m-cc DCI that can simultaneously schedule {cell#1, cell#2, cell#3} at most, SS set#s_A and / or CIF_A are set when the m-cc DCI schedules {cell#1, cell#2}. When the m-cc DCI schedules {cell#2, cell#3}, SS set#s_B and / or CIF_B are set. As 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 CIF_C are set. When the m-cc DCI schedules all three CCs, ie, when {cell#1, cell#2, cell#3} is scheduled, SS set#s_D and / or CIF_D is set.

[0117] - Reference unit 3: SS set and / or CIF value are set for each CC scheduled by m-cc DCI. In this case, the CIF value for each CC is set in the same manner as the CIF value set for the CC in the conventional (single-cell scheduling) DCI-based (cross-carrier) scheduling. For example, when {cell#1, cell#2} is scheduled for an m-cc DCI that can simultaneously schedule a maximum of {cell#1, cell#2, cell#3}, SS set#s_1 and / or CIF_1 are set individually for cell#1, and SS set#s_2 and / or CIF_2 are set individually for cell#2 (SS set#s_3 and / or CIF_3 are also set individually for cell#3).

[0118] The CCE positions of n_CI and / or PDCCH candidates (sets) (corresponding to each n_CI value) are determined (according to a method to be described later) from the SS set and / or CIF value set based on the reference unit 1 / 2 / 3. At this time, the PDCCH candidates (sets) (corresponding to each n_CI value for the m-cc DCI) determined from the CIF (and n_CI) value set based on reference unit 1, reference unit 2, or reference unit 3 are shared (SS sharing) regardless of the cell (combination) scheduled by the m-cc DCI. In other words, in a state in which (one or) multiple (e.g., N) n_CI values ​​are determined based on the SS set and / or CIF value set based on the reference unit 1 / 2 / 3 and N positions of the PDCCH candidate sets corresponding to each of the N n_CI values ​​are determined, the m-cc DCI that schedules a specific cell (combination) (corresponding to a specific CIF / n_CI value) is transmitted / received by any PDCCH candidate belonging to the N PDCCH candidate sets. For example, an m-cc DCI that schedules a cell (combination) corresponding to a particular CIF / n_CI=A value is transmitted / received by a PDCCH candidate set that corresponds to a CIF / n_CI=B value different from that A value.

[0119] According to the above-mentioned [Operation method of m-cc DCI and s-cc DCI], the CC that can be scheduled by m-cc DCI is set to be schedulable by s-cc DCI. In this case, the CIF value for each CC is set independently for each cell that can be scheduled by m-cc DCI. That is, even when the SS set and / or CIF value is set for multiple CCs according to [Reference unit 1] or [Reference unit 2], the CIF value for each CC is set separately for each of the multiple CCs. Therefore, it is necessary to distinguish the CIF value for m-cc DCI from the CIF value for s-cc DCI.

[0120] When a CIF value is set for an m-cc DCI according to [Standard Unit 1], one of the following methods is applied:

[0121] Method 1A: The CIF value for the m-cc DCI is set independently, i.e., one CIF value is set by configuring a separate SS set for the m-cc DCI.

[0122] - Method 2A: The CIF value for the m-cc DCI is set to the CIF value of a specific representative cell (ref-cc) among M cells (i.e., {{cell#m}, M}) that can be scheduled by the m-cc DCI. The ref-cc is predefined or set implicitly or explicitly.

[0123] -> Method of predefining ref-cc or setting it implicitly: It is the cell with the lowest or highest index among {{cell#m},M}. Or, if a PCell, PSCell, or PUCCH SCell is included in the set, that cell becomes ref-cc. Or, the scheduling cell is selected as ref-cc. Or, among the cells scheduled by m-cc DCI, the cell that is the reference for the CIF value is determined as ref-CC.

[0124] -> Explicitly setting ref-cc: ref-cc is set semi-statically by higher layer signaling such as RRC or MAC-CE. ref-CC may be set dynamically by DCI. In this case, the signaled cell index indicates a cell corresponding to the pre-defined rule (or implicit setting) described above.

[0125] - Method 3A: The CIF value for m-cc DCI is set to a value obtained by adding an offset to the CIF value of a specific representative cell (ref-cc) among cells that can be scheduled by m-cc DCI. For example, the CIF value for m-cc DCI is determined to be a value obtained by adding 1 to the highest / maximum value among the single-cell CIF values. ref-cc is defined / configured by the method of [Method 2A]. The offset is predefined or configured (e.g., by higher layer signaling).

[0126] According to [Reference Unit 2], when the CIF value is set by a CC combination scheduled in an m-cc DCI, one of the following methods is applied:

[0127] - Method 1B: The CIF value is set independently for each CC combination. That is, the CIF value is set by setting a separate SS set for each CC combination. For example, for an m-cc DCI that can simultaneously schedule a maximum of {cell#1, cell#2, cell#3}, the CIF value is set for each CC combination that is actually scheduled, as shown in the following example.

[0128] [Table 11]

[0129] - Method 2B: The CIF value for each CC combination is set to the CIF value of a specific representative cell (ref-cc) among the cells belonging to that CC combination. The ref-cc is predefined or set implicitly or explicitly.

[0130] -> Method of predefining ref-cc or setting it implicitly: It is the cell with the lowest or highest index among {{cell#m},M}. Or, if a PCell, PSCell, or PUCCH SCell is included in the set, that cell becomes ref-cc. Or, the scheduling cell is selected as ref-cc. Or, among the cells scheduled by m-cc DCI, the cell that is the reference for the CIF value is determined as ref-CC.

[0131] -> Explicitly setting ref-cc: ref-cc is set semi-statically by higher layer signaling such as RRC or MAC-CE. ref-CC may be set dynamically by DCI. In this case, the signaled cell index indicates a cell corresponding to the above-mentioned predefined rule (or implicit setting).

[0132] Method 3B: The CIF value for each CC combination is set to the CIF value of a specific representative cell (ref-cc) among the cells belonging to that CC combination plus an offset. In this case, ref-cc is defined / set by the method of [Method 2B], and the offset is also defined in advance or set separately (for example, by higher layer signaling).

[0133] According to [Reference Unit 3], for each CC scheduled in an m-cc DCI, if a CIF value is set per CC, one of the following methods is applied:

[0134] - Method 1C: The per-CC CIF value for the m-cc DCI is set to the same value as the per-CC CIF value set for the s-cc DCI for that CC. This method is a simple method that does not require a separate rule or signaling to determine the CIF value for the m-cc DCI.

[0135] - Method 2C: The per-CC CIF value for m-cc DCI is set independently. For example, the per-CC CIF value for m-cc DCI is set to a different value from the per-CC CIF value set for s-cc DCI for that CC, and a different rule is needed for this. For example, a CIF field for m-cc DCI is defined separately from the conventional CIF field for s-cc DCI. This helps to reduce the probability of PDCCH blocking.

[0136] Method 3C: The per-CC CIF value for the m-cc DCI is set to the per-CC CIF value set for the s-cc DCI for that CC plus an offset, which may be predefined or configured separately (e.g., by higher layer signaling).

[0137] Meanwhile, the number of PDCCH candidates for each AL n for m-cc DCI is also set by other methods corresponding to the reference unit. That is, as in [Reference Unit 1], SS set #s for m-cc DCI is set, and the number of PDCCH candidates for each AL n is set for the SS set #s. Alternatively, as in [Reference Unit 2], the number of PDCCH candidates for each SS set and / or AL n is set for each CC combination simultaneously scheduled by m-cc DCI. Alternatively, as in [Reference Unit 3], the number of PDCCH candidates for each SS set and / or AL n is set for each CC scheduled by m-cc DCI. Thus, the SS set setting for m-cc DCI and / or the number of PDCCH candidates for the SS set and / or the CIF value of the SS set are set based on the same CC set. For example, the SS set for the m-cc DCI, the number of PDCCH candidates for each AL n, and the CIF value are set based on the entire CC set / number schedulable by m-cc DCI. Alternatively, an SS set, the number of PDCCH candidates for each AL n, and a CIF value are set for each CC combination simultaneously scheduled by the m-cc DCI. Alternatively, an SS set, the number of PDCCH candidates for each AL n, and a CIF value are set for each CC scheduled by the m-cc DCI.

[0138] Furthermore, the CIF value is configured / reconfigured by higher layer signaling such as RRC or MAC-CE, or by dynamic methods such as DCI. As an example, when CA is (re)configured or when each SCell is activated, the CIF value for that cell is configured / reconfigured.

[0139] [2] Method for determining CCE index of PDCCH candidates for m-cc DCI

[0140] Table 10 discloses the formula for determining the CCE positions of PDCCH candidates according to AL defined in 3GPP TS 38.213.

[0141] n used when determining the CCE positions of PDCCH candidates CI (hereinafter, n_CI) is determined using the CIF value on the DCI. That is, n_CI is determined by the CIF value. That is, different n_CI (or CIF) values ​​are set to set different CCE positions for different scheduled CCs.

[0142] As described above, the CIF value for m-cc DCI is set to one value for the entire set of scheduled CCs, or to each scheduled CC combination, or to each scheduled CC. When the CIF value for m-cc DCI is set, the corresponding n_CI is determined by one of the following methods. In this case, the CIF value is set by one of the methods in [1] above.

[0143] - Method 1: The CIF value set for the m-cc DCI is set to the n_CI value for the m-cc DCI. Specifically, in the case of the reference unit 1, the CIF value set / determined by the method 1A / 2A / 3A is set to the n_CI value. In the case of the reference unit 2, the CIF value for each scheduled CC combination set / determined by the method 1B / 2B / 3B is set to the n_CI value (corresponding to the SS set set for each CC combination). In the case of the reference unit 3, the CIF value for each scheduled CC set / determined by the method 1C / 2C / 3C is set to the n_CI value (corresponding to the SS set set for each CC).

[0144] -> In this case, the CIF set for the m-cc DCI is set only to a value equal to or greater than a specific value. In this case, the specific value is predefined or set (e.g., by higher layer signaling). As an example of this, the specific value is "8". Alternatively, the specific offset is "the maximum value of the CIF value set for the s-cc DCI + 1". Alternatively, the specific offset is "the maximum value of the CIF value set for a scheduled cell (for s-cc DCI-based scheduling for that cell) that is set to be scheduled by an m-cc DCI transmitted on a scheduling cell + 1".

[0145] -> This allows the SS sets (or CCE positions of PDCCH candidates) between s-cc DCI and m-cc DCI to be configured to avoid overlapping with each other as much as possible.

[0146] - Method 2: The n_CI value for the m-cc DCI is set by adding a specific offset to the CIF value set for the m-cc DCI. In this case, the offset is predefined or set (e.g., by higher layer signaling). As an example of this, the specific offset is "8". Alternatively, the specific offset is "the maximum value of the CIF value set for the s-cc DCI + 1". Alternatively, the specific offset is "the maximum value of the CIF value set for a scheduled cell (for s-cc DCI-based scheduling for that cell) set to be scheduled by an m-cc DCI transmitted on a scheduling cell + 1".

[0147] -> For example, assume that the CIF set for the s-cc DCI is set to {0,1,2,3} and the CIF for the m-cc is set to {0,1,2}. The n_CI value (for each CIF) of the s-cc DCI is set to {0,1,2,3} like the CIF, while the n_CI value (for each CIF) of the m-cc DCI is set to {8,9,10} where n_CI=m-cc CIF+8, or to {4,5,6} where n_CI=m-cc CIF+(3+1). This is set to avoid a situation where the SS sets (or CCE positions of PDCCH candidates) between the s-cc DCI and the m-cc DCI overlap each other as much as possible.

[0148] -> Furthermore, the offset differs depending on the number of CCs scheduled. For example, in the case of [reference unit 2], different offsets are determined / set depending on the number of CCs scheduled at one time.

[0149] -> Furthermore, among the co-scheduled cells of the m-cc DCI, for cells where the legacy DCI is configured (or monitored), a separate offset is given to the PDCCH candidate position (i.e., CCE index) for that cell. (Objective: Separation of the position from the PDCCH candidate of the legacy DCI)

[0150] - Method 3: Set the CIF value set for the s-cc DCI to the n_CI value for the m-cc DCI.

[0151] - Method 4: The n_CI value for the m-cc DCI is set by adding a specific offset to the CIF value set for the s-cc DCI. In this case, the offset is predefined or set (e.g., by higher layer signaling). Furthermore, the offset differs depending on the number of CCs scheduled at one time in the m-cc DCI (combination of cells scheduled simultaneously). For example, in the case of [reference unit 2], different offsets are determined / set depending on the number of CCs scheduled at one time.

[0152] On the other hand, the PDCCH candidate set for m-cc DCI determined from the reference unit 1 / 2 / 3 described in [1] and the CIF value (and / or n_CI) based thereon does not need to be limited to be used only for m-cc DCI transmission / reception that schedules a specific cell (or combination of cells). That is, the PDCCH candidate (or PDCCH candidate set) determined by a specific combination of the "reference unit 1 / 2 / 3" and the "method of determining the CIF value" and the "method of determining the n_CI value" described in [1] is shared (SS sharing) regardless of the cell (combination) that the m-cc DCI schedules. In other words, one or more (e.g., N) n_CI values ​​are determined based on the SS set and / or CIF value set based on the reference unit 1 / 2 / 3, and N positions of the PDCCH candidates (or PDCCH candidate sets) corresponding to the N n_CI values ​​are determined. In this state, an m-cc DCI that schedules a specific cell (or a combination of cells) (corresponding to a specific CIF / n_CI value) is transmitted / received by any PDCCH candidate belonging to the N PDCCH candidates (or PDCCH candidate sets). For example, an m-cc DCI that schedules a cell (or a combination of cells) corresponding to a specific CIF / n_CI=A value is transmitted / received by a PDCCH candidate (or a PDCCH candidate set) corresponding to a CIF / n_CI=B value different from the A value.

[0153] [3] DCI size alignment method for m-cc DCI

[0154] DCI formats supported in NR are classified according to the RNTI that is CRC scrambled, or classified into fallback / non-fallback DCI according to the type of feature indicated by the DCI. As such, there are various DCI formats supported by NR (e.g., DCI format 0_0, 1_0, 0_1, 1_1, 0_2, 2_1, etc.), and the UE needs to blindly detect PDCCHs for DCIs of different sizes. PDCCH monitoring for DCIs of various sizes is a heavy burden (e.g., in terms of power consumption) for the UE. To solve this, there are different rules for DCI formats having different sizes in NR. Specifically, they are collectively referred to as a "3+1" size budget. According to the "3+1" size budget, the size of the DCI to be CRCed in the C-RNTI, etc. is a maximum of 3, and when including other RNTIs, the size of the DCI is limited to not more than 4. In order to match the sizes of different DCI formats, the NR specifies a DCI size alignment method as shown in Table 12.

[0155] [Table 12-1] [Table 12-2] [Table 12-3] [Table 12-4]

[0156] Since the m-cc DCI can schedule multiple CCs simultaneously, the DCI size increases compared to the conventional s-cc DCI, which can only schedule a single cell. Even if the m-cc DCI is introduced, further size alignment is required to maintain the conventional DCI size budget. Size alignment due to the introduction of the m-cc DCI is performed by one of the following methods (or a combination of two or more of them). The proposed method is applied only to terminals for which scheduling by the m-cc DCI is configured.

[0157] - Method 1: The sizes of the m-cc DCI for DL ​​assignment (i.e., scheduling a PDSCH) and the m-cc DCI for UL grant (i.e., scheduling a PUSCH) are made identical to each other.

[0158] -> [Method 1-1] When the sizes of m-cc DCIs for DL ​​and UL are different, the sizes of the two DCIs are aligned based on the larger size of the two by increasing the size of the DCI having the smaller size of the two. A specific method for increasing the size of the m-cc DCI (for DL ​​or UL) having the smaller size is as follows, but is not limited thereto.

[0159] -> (1-1-1) A 0 (zero) is added to the end of the bit stream that makes up the DCI.

[0160] -> (1-1-2) 0 (zero) is added to a specific field (for example, the FDRA (frequency domain resource allocation) field).

[0161] -> (1-1-3) The size is adjusted by changing the resolution expressing a particular field (e.g., the FDRA field). For example, if the FDRA field of the DL or UL DCI for m-cc scheduling is indicated in units of RB groups, if a size increase is required, the FDRA field is changed to a larger size by reducing the size of the RB group.

[0162] -> [Method 1-2] When the sizes of the m-cc DCIs for DL ​​and UL are different, the sizes of the two DCIs are aligned based on the smaller size of the two by reducing the size of the DCI having the larger size of the two. A specific method of reducing the size of the m-cc DCI (for DL ​​or UL) having the larger size is as follows, but is not limited thereto.

[0163] -> (1-2-1) The size of a particular field (e.g., the FDRA field) is reduced. For example, if a reduction of 4 bits is required, the last 4 bits of the FDRA field are removed.

[0164] -> (1-2-2) The resolution expressing a particular field (e.g., the FDRA field) is changed to fit the size. For example, if the FDRA field of the DL or UL DCI for m-cc scheduling is indicated on an RB group basis, and a size reduction is required, the FDRA field is changed to a smaller size by increasing the size of the RB group.

[0165] - Method 2: Even if the sizes of m-cc DCI for DL ​​and UL scheduling are aligned by [Method 1], further DCI size alignment may be required. In this case, size alignment of conventional s-cc DCI (e.g., DCI format 0_1 ​​and DCI format 1_1) for DL ​​and UL scheduling is further performed. That is, a terminal in which multiple CC scheduling is configured by m-cc DCI can align the sizes of s-cc DCI for DL ​​and UL to be the same. In this case, the above-mentioned [Method 1-1] or [Method 1-2] is applied as the size alignment method.

[0166] Method 3: The sizes of m-cc DCI and s-cc DCI for DL ​​scheduling are aligned to be the same. In this case, the above-mentioned [Method 1-1] or [Method 1-2] is applied as the size alignment method.

[0167] Method 4: The sizes of m-cc DCI and s-cc DCI for UL scheduling are aligned to be the same. In this case, the above-mentioned [Method 1-1] or [Method 1-2] is applied as the size alignment method.

[0168] - Method 5: The size of m-cc DCI (for DL ​​or UL) CRC-scrambled with C-RNTI and the size of DCI format CRC-scrambled with other RNTI are aligned to be the same. For example, the size of m-cc DCI scrambled with C-RNTI and the size of DCI format 2_0 scrambled with SFI-RNTI are aligned to be the same. In this case, the size alignment method is the above-mentioned [Method 1-1] or [Method 1-2].

[0169] - Method 6: When an m-cc DCI is configured, s-cc DCI scheduling is restricted to be performed only with a specific DCI format (or not to use a specific DCI format). For example, when DL scheduling is configured by an m-cc DCI, s-cc scheduling is restricted to be possible only with DCI format 1_2. In this case, as a size alignment method, the size of the m-cc DCI is increased or decreased by the above-mentioned [Method 1-1] or [Method 1-2]. A conventional size alignment method for s-cc DCI may be applied. This method is characteristically applied to option 3 or option 3a of the above-mentioned [Operation method of m-cc DCI and s-cc DCI].

[0170] Meanwhile, when the UE operates based on Option 1 / 2 / 3 of the [Operation Method of m-cc DCI and s-cc DCI], the m-cc DCI (size) is considered to be a DCI (size) related to a specific reference cell among the cells set as targets for the m-cc DCI scheduling (in terms of applying / performing DCI size alignment for each cell). Thus, the method 1 / 2 / 3 / 4 / 5 / 6 is applied in the DCI size alignment process related to the reference cell. The reference cell is the cell where the m-cc DCI is transmitted, or the cell with the lowest index, or the cell with the highest cell index.

[0171] Meanwhile, in the DCI size alignment process by applying the m-cc DCI, the reference cell to be the target cell is pre-defined as a cell that satisfies a predetermined condition or is explicitly indicated by the base station. The predetermined condition is determined as a cell in which N_crnti (= the number of different DCI sizes of DCI CRC-scrambled by C-RNTI) is less than k (e.g., k=3) among scheduled cells scheduled by the m-cc DCI.

[0172] At this time, among the scheduled cells, if the condition "N_crnti < k" is satisfied for a plurality of cells, among the plurality of cells, the cell with the minimum N_crnti or the cell with the lowest index or the cell with the highest index is determined as the reference cell, and then DCI size alignment is performed. If a plurality of cells have the "minimum N_crnti", after the cell with the lowest index or the cell with the highest index among the plurality of cells is determined as the reference cell, DCI size alignment is performed. For example, in a situation where three cells are scheduled by m-cc DCI, assuming that it is determined that the size alignment by m-cc DCI is performed on cells where N_crnti < 3, when the N_crnti values of each scheduled cell are N_crnti = 2 for cell♯1, N_crnti = 1 for cell♯2, and N_crnti = 1 for cell♯3, DCI size alignment for m-cc DCI is performed on the cell with the lowest index or the highest index among cell♯2 and cell♯3 (or on the cell corresponding to ref-cc described in [Operation Method of m-cc DCI and s-cc DCI]).

[0173] As another example of the predetermined condition, among the cells scheduled by m-cc DCI, the cell with the smallest difference between the (maximum) size of the conventional s-cc DCI for the cell and the size of the m-cc DCI is determined as the target cell for DCI size alignment.

[0174] At this time, if, among the scheduled cells, a plurality of cells have the minimum size difference, DCI size alignment is performed with the cell having the lowest or highest index among the plurality of cells determined as the reference cell (or with respect to the cell corresponding to ref-cc described in [Operation Method of m-cc DCI and s-cc DCI]).

[0175] Furthermore, a method can be considered in which the size budget of s-cc DCI is maintained as in the past (i.e., up to three for C-RNTI) while the number of sizes of m-cc DCI and s-cc DCI set for a specific cell is maintained below a predetermined number. That is, a method can be used in which the sum of the number of sizes of m-cc DCI and the number of sizes of s-cc DCI is kept below a predetermined number. For example, when the number of cells set for a specific cell is K, the DCI size budget is defined so that the number of m-cc DCI sizes + sum {number of s-cc DCI sizes} <= 3*K.

[0176] If the number of cells in which the m-cc DCI is configured is M, if the DCI size budget is exceeded (or, for example, as in the above example, if the m-cc DCI size number+sum{s-cc DCI size number}>3*M), the DCI (size) associated with a specific reference cell (e.g., the cell in which the m-cc DCI is transmitted or the cell with the lowest (or highest) cell index) among the cells configured as the scheduling target of the m-cc DCI is adjusted by the proposed method. Alternatively, the size budget is maintained by aligning the size of the m-cc DCI with one of the s-cc DCIs (by a predefined rule) or aligning the size of the DL s-cc DCI with the size of the UL s-cc DCI.

[0177] A terminal configured with multi-cell scheduling using m-cc DCI maintains a DCI size budget for each cell through the following process. For example, the terminal checks whether the size of DCI scrambled with C-RNTI among DCIs to be monitored for the cell exceeds three, and if so, applies a DCI size arrangement method so that the size of DCI is three or less. In the method described below, "DCI size" refers to the size of DCI scrambled with C-RNTI. Also, "DCI size number" refers to the number of different sizes of DCI (scrambled with C-RNTI) to be monitored by the terminal for a specific cell (or DL ​​BWP of the cell). For example, "DCI size number" refers to the number of different DCI sizes counted based on the number of PDCCH candidates configured for each SS set in an active DL BWP of the cell. In the method described below, "legacy DCI" refers to a DCI format for single-cell scheduling. Specifically, "legacy DCI" refers to all of the fallback DCI formats (e.g., DCI format 0_0, DCI format 1_0) and non-fallback DCI formats (e.g., DCI 0_1, DCI 1_1, DCI 0_2, DCI 1_2), or one of the two (e.g., non-fallback DCI). In this case, "legacy DCI size" refers to the payload size of the legacy DCI. In the method described below, the cell for which the DCI size budget is checked and DCI size alignment is performed (if necessary) is a specific cell among scheduled cells scheduled with m-cc DCI.

[0178] - Method-A

[0179] -> Step 1: For scheduled cells scheduled by m-cc DCI, the terminal first excludes the DCI size of the m-cc DCI and checks the number of conventional DCI sizes that need to be monitored for each cell. If the number of different sizes of conventional DCI exceeds the DCI size budget, the terminal performs alignment on the conventional DCI sizes (defined in the specifications) and determines the number of DCI sizes for each cell.

[0180] -> Step 2: Select a specific reference cell among scheduled cells scheduled by m-cc DCI. At this time, the reference cell is determined / set to "the scheduling cell to which the m-cc DCI is transmitted", "a specific cell directly specified by RRC", "a cell having the lowest index among the scheduled cells", "a cell with a smaller (and smallest) DCI size number determined in step 1 than "3" (where the number "3" means the DCI size budget for C-RNTI) if there is such a cell" (if there are multiple cells, a specific one of the cells (e.g., with the lowest cell index)), or "a cell with the smallest DCI size number determined in step 1" (if there are multiple cells, a specific one of the cells (e.g., with the lowest cell index)).

[0181] -> Step 3: If the total number of DCI sizes (combining m-cc DCI sizes and conventional DCI sizes) for the reference cell determined in step 2 exceeds "3", proceed to step 4, otherwise no other DCI size alignment is performed. At this time, cases in which it is necessary to proceed to step 4 include, but are not limited to, the following:

[0182] For example, when the conventional DCI size number for the reference cell is "3" and the m-cc DCI size number is "1", that is, when only one of the m-cc DCI for DL ​​that schedules PDSCH and the m-cc DCI for UL that schedules PUSCH is configured for the cell, or when the DCI sizes of the m-cc DCI for DL ​​and the m-cc DCI for UL are the same (even if both are configured).

[0183] For example, the conventional DCI size number for the reference cell is "2" and the m-cc DCI size number is "2", i.e., both an m-cc DCI for DL ​​and an m-cc DCI for UL are configured for the cell, and the DCI sizes of the two DCIs are different.

[0184] For example, when the conventional DCI size number for the reference cell is "3" and the m-cc DCI size number is "2" (i.e., when both the m-cc DCI for DL ​​and the m-cc DCI for UL are configured for the cell, and the DCI sizes of the two DCIs are different).

[0185] -> Step 4: If there is still room for conventional DCI size alignment (in addition to step 1) for the reference cell determined in step 2, size alignment is performed. As a result, if the total number of DCI sizes (combining m-cc DCI sizes and conventional DCI sizes) is less than or equal to "3", the entire DCI size alignment process is terminated. On the other hand, if there is no room for conventional DCI size alignment (in addition to step 1) for the reference cell, or there is still room for conventional DCI size alignment and the total number of DCI sizes exceeds "3" even after all size alignments have been performed, DCI size alignment is further performed by any one of methods 1 to 6 in section [3], which are size alignment methods for m-cc DCI described in this specification. If the total number of DCI sizes (combining m-cc DCI sizes and conventional DCI sizes) is less than or equal to "3", the entire DCI size alignment process is terminated.

[0186] - Method-B

[0187] -> Step 1: A specific reference cell is selected from among scheduled cells scheduled by the m-cc DCI. At this time, the reference cell is determined / set to "the scheduling cell to which the m-cc DCI is transmitted", "a specific cell directly specified by RRC", or "a cell having the lowest index among the scheduled cells".

[0188] -> Step 2: For the reference cell determined in step 1, the terminal first checks the number of conventional DCI sizes that need to be monitored for the cell, excluding the DCI size of the m-cc DCI. If the number of different sizes of the conventional DCI exceeds the DCI budget (e.g., "3"), alignment for conventional DCI sizes (defined in the specification) is performed. As a result, if the total number of DCI sizes of the cell including the m-cc DCI size exceeds "3", proceed to step 3, otherwise, no further DCI size alignment is performed. As another method, for the reference cell determined in step 1, the value obtained by subtracting the number of m-cc DCI sizes from the DCI budget (e.g., "3") is defined as "A" for convenience. For the cell that needs monitoring, the terminal checks the number of conventional DCI sizes that need to be monitored, and if the number of different sizes of the conventional DCI exceeds A, alignment for conventional DCI sizes (defined in the specification) is performed. As a result, if the total number of DCI sizes for the cell, including the m-cc DCI size, exceeds "3" (the number of conventional DCI sizes still exceeds A), proceed to step 3; otherwise, no further DCI size alignment is performed.

[0189] -> Step 3: DCI size alignment is further performed by any one of methods 1 to 6 in section [3], which are size alignment methods for m-cc DCI described in this specification.

[0190] Furthermore, when an m-cc DCI is configured, the DCI size budget is checked using the number of different DCI sizes counted based on the number of PDCCH candidates configured in each SS cell in an active search space set group (SSSG) for an active DL BWP of each (scheduled) cell, and the above-mentioned size alignment is performed. Alternatively, when an m-cc DCI is configured, the DCI budget is checked using the number of different DCI sizes counted based on the number of PDCCH candidates configured in all SS sets in units of co-scheduled cell combinations in which the m-cc DCI can be scheduled simultaneously (or for the union of all co-scheduled cell combinations), and the above-mentioned size alignment is performed.

[0191] [4] DCI size alignment method for m-cc DCI (addition)

[0192] [4-1]

[0193] According to the contents defined in 38.212 Section 7.3.1.0 (DCI size alignment) excerpted from [3], the DCI size alignment process is shown in the following simple table.

[0194] [Table 13]

[0195] In the table, A, B, C, D, E, and F each refer to the DCI size of the corresponding DCI format (different from each other). The process of adjusting the size of each DCI format in the order of 1st step, 2nd step, and 3rd step. In the table, max(C,D) refers to a process of matching the sizes of two DCI formats based on the larger size of DCI format 0_1 ​​and DCI format 1_1 when the sizes are different. max(E,F) refers to a process of matching the sizes of two DCI formats based on the larger size of DCI format 0_2 and DCI format 1_2 when the sizes are different. In addition, the 2nd step and 3rd step refer to Step 4B and Step 4c in the 38.212 specification, respectively. Each step in the table is understood as an operation performed when the DCI size budget for different DCI sizes is exceeded even after the previous step is performed (e.g., the number of different DCI sizes exceeds 4, or the number of different DCI sizes scrambled by the C-RNTI exceeds 3). For example, after the size of each DCI format (configured for the terminal / cell) is determined in the 1st step, if the number of determined sizes exceeds the DCI size budget, the 2nd step is performed. Alternatively, if the DCI size budget is exceeded even after the sizes of DCI formats 0_2 and 1_2 are adjusted in the 2nd step, the 3rd step is performed.

[0196] The following method is (further) introduced as a DCI size alignment method for m-cc DCI. In the method described below, m-cc DCI for DL ​​and m-cc DCI for UL are expressed as follows (for convenience of expression): DCI(format)0_X means a DCI format for scheduling PUSCH in multiple cells, and DCI(format)1_X means a DCI format for scheduling PDSCH in multiple cells.

[0197] [4-2]

[0198] For a terminal (or cell) configured with multi-cell (PDSCH / PUSCH) scheduling using m-cc DCI, if the number of DCI sizes (for all configured DCI formats) exceeds the DCI size budget even after the 3rd step is performed, the following 4th step is performed.

[0199] 4th step: If the DCI sizes of DCI 0_X and DCI 1_X are different, the smaller of the two sizes is matched to the larger size. The specific method for matching the sizes is the method described in [3] above.

[0200] This is shown in Table 14 below. Additions / changes compared to Table 13 are marked with "#".

[0201] [Table 14]

[0202] That is, for all DCI format sizes configured in the terminal / cell (i.e., after the 1st step), the DCI format sizes are adjusted ( / changed) in the following order (until the DCI size budget is met):

[0203] (1) Size alignment between DCI 0_2 and DCI 1_2

[0204] (2) Size alignment between DCI 0_1 and DCI 1_1

[0205] (3) Size alignment between DCI 0_X and DCI 1_X

[0206] Alternatively, the priority order of size alignment between DCI formats can be changed and the procedure can be performed in the following order.

[0207] [Table 15]

[0208] That is, for all DCI format sizes configured in the terminal / cell (i.e., after the 1st step), the DCI format sizes are adjusted ( / changed) in the following order (until the DCI size budget is met):

[0209] (1) Size alignment between DCI 0_X and DCI 1_X

[0210] (2) Size alignment between DCI 0_2 and DCI 1_2

[0211] (3) Size alignment between DCI 0_1 and DCI 1_1

[0212] Alternatively, the priority order of size alignment between DCI formats can be changed and the procedure can be performed in the following order.

[0213] [Table 16]

[0214] That is, for all DCI format sizes configured in the terminal / cell (i.e., after the 1st step), the DCI format sizes are adjusted ( / changed) in the following order (until the DCI size budget is met):

[0215] (1) Size alignment between DCI 0_2 and DCI 1_2

[0216] (2) Size alignment between DCI 0_X and DCI 1_X

[0217] (3) Size alignment between DCI 0_1 and DCI 1_1

[0218] [4-3]

[0219] According to the size alignment methods shown in Tables 14 to 16, if the number of DCI sizes exceeds the DCI size budget even after the 4th step is performed, the 5th step is introduced. That is, the 5th step is used to reduce three different sizes (i.e., max(C,D), max(E,F), max(G,H)) to two (or less) when the sizes of DCI formats 0_1 and 1_1 are the same (e.g., max(C,D)), the sizes of DCI formats 0_2 and 1_2 are the same (e.g., max(E,F)), and the sizes of DCI formats 0_X and 1_X are the same (e.g., max(G,H)). There are three different methods as follows:

[0220] - 5th step (Alt 1): The sizes of max(C,D) and max(E,F) in the 4th step are aligned. That is, max{max(C,D),max(E,F)} is performed. In this case, (after the 5th step) there are three different DCI sizes for C-RNTI, namely A, max{max(C,D),max(E,F)},max(G,H).

[0221] - 5th step (Alt 2): The sizes of max(C,D) and max(G,H) in the 4th step are aligned, i.e., max{max(C,D),max(G,H)} is performed. In this case, (after the 5th step) there are three different DCI sizes for C-RNTI, namely A, max{max(C,D),max(G,H)}, max(E,F).

[0222] 5th step (Alt 3): The sizes of max(E,F) and max(G,H) in the 4th step are aligned. That is, max{max(E,F),max(G,H)} is performed. In this case, (after the 5th step) there are three different DCI sizes for C-RNTI, namely A, max{max(E,F),max(G,H)},max(C,D).

[0223] In this case, the specific method for adjusting the DCI size (for the three cases described above) is the method described in [3] above.

[0224] Furthermore, when the DCI size is determined according to the above-mentioned 4th step and / or 5th step, a 2-bit field is used for each DCI (or for some DCI formats (e.g., m-cc DCI)). When max{max(C,D),max(E,F)}, max{max(C,D),max(G,H)} or max{max(E,F),max(G,H)} have the same DCI size, the terminal distinguishes each DCI format by the 2-bit field. In this case, the 2-bit field is a 1-bit "DCI format indicator" defined in the conventional DCI format that has been changed / extended to 2 bits. Alternatively, it is a 2-bit field defined separately.

[0225] [4-4]

[0226] After the size alignment method shown in Tables 14 to 16 is performed up to the 4th step, the base station restricts the DCI format set in the terminal / cell so as not to exceed the DCI size budget, and the terminal does not expect to exceed the DCI size budget. That is, the base station does not set a "specific DCI format" (for the cell) under a "predetermined condition", and the terminal operates under the assumption that the "specific DCI format" is not set (for the cell) under the "predetermined condition". In this case, the "predetermined condition" and / or the "specific DCI format" (not expected to be set) is defined in advance or set by higher layer signaling / command such as RRC. For example, for a terminal / cell in which DCI 0_X (or 1_X) is set (when the DCI size budget is exceeded), DCI format 0_2 (or 1_2) is defined / set so as not to be set at the same time. Alternatively, for a terminal / cell in which DCI 0_X / 1_X is configured (when the DCI size budget is exceeded), DCI format 0_1 ​​(or 1_1) is defined / configured so as not to be configured at the same time. Alternatively, for a terminal / cell in which DCI 0_2 (or 1_2) is configured (when the DCI size budget is exceeded), DCI format 0_X (or 1_X) is defined / configured so as not to be configured at the same time. As another example, for a terminal / cell in which DCI 0_X / 1_X is configured, DCI 0_0 (or 1_0) is defined / configured so as not to be configured (at the same time).

[0227] The method of [4-4] is applied collectively to each / all scheduled cells of multi-cell scheduling by m-cc DCI, or the method of [4-4] is applied only to a part / specific cell (or cell set) of the scheduled cells. In this case, the part / specific cell is predefined or configured separately.

[0228] This method is applied after the 4th step of the size alignment process described above, but is not limited thereto, and may be applied after some / specific steps of the above process (or only some / specific steps). For example,

[0229] If DCI 0_X / 1_X is configured for a (specific) terminal / cell and DCI 0_0 / 1_0 is not configured, DCI size alignment is performed for the cell (until the DCI size budget is not exceeded) by sequentially applying the 2nd step, 3rd step, and 4th step to Tables 14 to 16.

[0230] - If DCI 0_X / 1_X is configured for a (specific) UE / cell, and DCI 0_1 / 1_1 is not configured, DCI size alignment is performed for the cell (until the DCI size budget is not exceeded) by sequentially applying the 1st step, 2nd step, and 4th step to Table 14. Alternatively, DCI size alignment is performed for the cell (until the DCI size budget is not exceeded) by sequentially applying the 1st step, 2nd step, and 3rd step to Tables 15 to 16.

[0231] - If DCI 0_X / 1_X is configured for a (specific) UE / cell and DCI 0_2 / 1_2 is not configured, DCI size alignment is performed for the cell (until the DCI size budget is not exceeded) by sequentially applying the 1st step, 3rd step, and 4th step to Tables 14 to 16. Alternatively, DCI size alignment is performed for the cell (until the DCI size budget is not exceeded) by sequentially applying the 1st step, 2nd step, and 4th step to Table 15.

[0232] [4-5]

[0233] After the size alignment method shown in Tables 14 to 16 is performed up to the 4th step, the terminal does not monitor a specific / part of DCI formats (so as not to exceed the DCI size budget). That is, the terminal ignores (or drops) the "specific DCI format" set (for the cell) under the "predetermined condition" and does not monitor the associated PDCCH (that is, the terminal does not monitor the PDCCH for that DCI format, does not count the BD / CCE for it, and does not count the DCI size for that DCI). In this case, the "predetermined condition" and / or the "specific DCI format" (not to be monitored) are defined in advance or are set by higher layer signaling / command such as RRC. For example, it is defined / set not to monitor DCI format 0_2 (or 1_2) for a terminal / cell set with DCI 0_X (or 1_X) (when the DCI size budget is exceeded). Alternatively, for a terminal / cell in which DCI 0_X / 1_X is configured (when the DCI size budget is exceeded), it is defined / configured not to monitor DCI format 0_1 ​​(or 1_1). Alternatively, for a terminal / cell in which DCI 0_2 (or 1_2) is configured (when the DCI size budget is exceeded), it is defined / configured not to monitor DCI format 0_X (or 1_X). As another example, for a terminal / cell in which DCI 0_X / 1_X is configured, it is defined / configured not to monitor DCI 0_0 (or 1_0).

[0234] This method is applied collectively to each / all scheduled cells of multi-cell scheduling by m-cc DCI, or to only a part / specific cell (or cell set) of the scheduled cells, where the part / specific cell is predefined or configured separately.

[0235] This method may be applied after the 4th step of the size alignment process described above (but is not limited to this), but may also be applied after some / specific steps of the process (or only some / specific steps). For example,

[0236] - If DCI 0_X / 1_X is configured for a (specific) terminal / cell and the terminal is defined / configured not to monitor DCI 0_0 / 1_0 (for that cell), DCI size alignment is performed for that cell (until the DCI size budget is not exceeded) by sequentially applying the 2nd step, 3rd step, and 4th step of Tables 14 to 16.

[0237] - If DCI 0_X / 1_X is configured for a (specific) UE / cell and the UE is defined / configured not to monitor DCI 0_1 / 1_1 (for that cell), DCI size alignment is performed for that cell (until the DCI size budget is not exceeded) by sequentially applying the 1st step, 2nd step, and 4th step to Table 14. Alternatively, DCI size alignment is performed for that cell (until the DCI size budget is not exceeded) by sequentially applying the 1st step, 2nd step, and 3rd step to Tables 15 and 16.

[0238] - If DCI 0_X / 1_X is configured for a (specific) UE / cell and the UE is defined / configured not to monitor DCI 0_2 / 1_2 (for that cell), DCI size alignment is performed for that cell (until the DCI size budget is not exceeded) by sequentially applying the 1st step, 3rd step, and 4th step for Tables 14 to 16. DCI size alignment is performed for that cell (until the DCI size budget is not exceeded) by sequentially applying the 1st step, 2nd step, and 4th step for Table 15.

[0239] [4-6]

[0240] Furthermore, the terminal is not expected to handle cases such as those in Table 17 after performing some or all of the DCI size alignment described above.

[0241] [Table 17]

[0242] Meanwhile, the contents of the present invention are not limited to application only to transmission and reception of uplink and / or downlink signals. For example, the contents of the present invention can also be used for direct communication between terminals. Furthermore, the base station in the present invention is a concept that includes not only a base station but also a relay node. For example, the operation of the base station in the present invention may be performed by the base station or a relay node.

[0243] The above-mentioned example of the proposed method is also included as one of the implementation methods of this specification, and is therefore recognized as a kind of proposed method. The above-mentioned proposed methods may be implemented independently, or may be implemented in the form of a combination (or merging) of some of the proposed methods. Information regarding the application of the above-mentioned proposed method (or information regarding the rules of the proposed method) may be notified by the base station to the terminal, or by the transmitting terminal to the receiving terminal, by a predetermined signal (e.g., a physical layer signal or a higher layer signal).

[0244] Example

[0245] FIG. 4 is a flowchart illustrating a signal transmitting and receiving method according to an embodiment of the present invention.

[0246] Referring to FIG. 4, an embodiment performed by a terminal (UE) includes the steps of determining a CCE index corresponding to a PDCCH candidate (S401) and monitoring the PDCCH candidate based on the CCE index (S403).

[0247] The monitoring of PDCCH candidates is based on one or more of the operations described in Sections [1] to [4].

[0248] As described above, a cell that schedules a PDSCH or a PUSCH, i.e., a cell in which a PDCCH that transmits a DCI is received, is referred to as a scheduling cell. A cell in which a PDSCH or a PUSCH scheduled by the received PDCCH is actually transmitted is referred to as a scheduled cell.

[0249] A DCI format for scheduling a PDSCH or PUSCH on one scheduled cell (DCI format of single-cell DCI) is referred to as a first DCI format. A DCI format for scheduling a PDSCH or PUSCH on multiple scheduled cells (DCI format of multi-cell DCI) is referred to as a second DCI format. In this specification, DCI and DCI format can be mixed.

[0250] Referring to Table 10, when the DCI format monitored by the terminal is the first DCI format, the n_CI value is used to determine the CCE index. The n_CI value is a carrier indicator field (CIF) value, and the CIF is included in the DCI format. Therefore, when the PDCCH candidate monitored by the terminal is for the first DCI format, the CCE index is set (or determined) based on the CIF value included in the DCI format.

[0251] On the other hand, according to reference unit 2 in section [1], a CIF value is set for each CC combination that is scheduled simultaneously by the multi-cell DCI. Thus, when the PDCCH candidates monitored by the terminal are for the second DCI format, the CCE index is set (or determined) independently for each combination of scheduled cells. In particular, according to method 1B in section [1], a CIF value is set independently for each combination of scheduled cells. However, the value is used only for determining the CCE index, and the second DCI format does not actually include a CIF. For example, a separate field is used for indicating the combination of scheduled cells scheduled by the second DCI format, and the n_CI value required for determining the CCE index is set independently based on the combination of scheduled cells even if the second DCI format does not include a CIF. Thus, for the second DCI format, the n_CI value corresponds to a predetermined value set for each combination of scheduled cells, not a CIF value in the DCI. The predetermined value is, for example, called a cell set indicator value instead of a CIF value.

[0252] Further, referring to Section [3], after the DCI size budget is satisfied by the DCI size alignment process, the terminal monitors PDCCH candidates for the DCI format. Specifically, referring to step 1 of method-B in Section [3], the DCI size alignment is performed for a specific reference cell selected from the scheduled cells.

[0253] Referring to step 3 of Table 12, if the total number of different DCI sizes configured to monitor for a cell is no more than 4, or the total number of different DCI sizes with C-RNTI configured to monitor for a cell is no more than 3, the DCI size budget is exceeded, which increases the PDCCH monitoring burden on the terminal. To avoid this, DCI size alignment is performed.

[0254] Referring to step 2 of method B in section [3], when the total number of DCI sizes excluding the multi-cell DCI (second DCI format) for the reference cell exceeds 3, DCI size alignment for the conventional DCI (first DCI format) is performed. Since 3 in step 2 of method B in section [3] is for the DCI format associated with the C-RNTI, when the total number of DCI sizes set to be monitored for the reference cell exceeds 4 excluding the second DCI format or the total number of DCI sizes associated with the C-RNTI set to be monitored for the reference cell exceeds 3 excluding the second DCI format, a DCI size alignment process (first DCI size alignment process) for the conventional DCI format is performed.

[0255] The DCI size alignment process for the conventional DCI formats is as shown in Table 13 of Section [4]. Specifically, the first DCI size alignment process for the conventional DCI formats is performed in the order of a DCI size alignment process between DCI format 1_0 and DCI format 0_0, a DCI size alignment process between DCI format 0_2 and DCI format 1_2, and a DCI size alignment process between DCI format 0_1 ​​and DCI format 1_1.

[0256] After the first DCI size alignment process, the DCI size alignment process is completed if the total number of DCI sizes including the multi-cell DCI (second DCI format) for the reference cell does not exceed 3. Since 3 in step 2 of method-B in Section [3] is for the DCI format associated with the C-RNTI, if the total number of DCI sizes set to be monitored for the reference cell does not exceed 4 including the second DCI format and the total number of DCI sizes associated with the C-RNTI set to be monitored for the reference cell does not exceed 3 including the second DCI format, the DCI size alignment process is completed in step 2.

[0257] After the first DCI size alignment process, if the total number of DCI sizes including the multi-cell DCI (second DCI format) for the reference cell exceeds 3, step 3 of method-B in section [3] is performed. According to step 3 of method-B in section [3], the DCI size alignment process including the multi-cell DCI is performed. Thus, if the total number of DCI sizes set to be monitored for the reference cell exceeds 4 including the second DCI format, or the total number of DCI sizes related to the C-RNTIs set to be monitored for the reference cell exceeds 3 including the second DCI format, a DCI size alignment process for the second DCI format (second DCI size alignment process) is performed.

[0258] Referring to step 3 of Method-B in Section [3], the second DCI size alignment process is performed according to a combination of any one or more of Methods 1 to 6 in Section [3].

[0259] For example, according to method 1 in section [3], a DCI size alignment process between a multi-cell DCI for PDSCH scheduling and a multi-cell DCI for PUSCH scheduling is performed. Thus, according to method 1 in section [3], the second DCI size alignment process includes aligning the size of a DCI format for scheduling PDSCHs on multiple scheduled cells and the size of a DCI format for scheduling PUSCHs on multiple scheduled cells to be the same.

[0260] As another example, according to method 3 in section [3], a DCI size alignment process between a multi-cell DCI for PDSCH scheduling and a single-cell DCI for PDSCH scheduling is performed. Thus, according to method 4 in section [3], the second DCI size alignment process includes aligning the size of a DCI format for scheduling PDSCHs on multiple scheduled cells and the size of a DCI format for scheduling PDSCHs on one scheduled cell to be the same.

[0261] As another example, according to method 4 in section [3], a DCI size alignment process between a multi-cell DCI for PUSCH scheduling and a single-cell DCI for PUSCH scheduling is performed. Thus, according to method 4 in section [3], the second DCI size alignment process includes aligning the size of a DCI format for scheduling PUSCHs on multiple scheduled cells and the size of a DCI format for scheduling PUSCHs on one scheduled cell to be the same.

[0262] In addition to the operations described in relation to Figure 4, any one or more of the operations described in Figures 1 to 3 and / or the operations described in "DCI for scheduling PDSCHs or PUSCHs on multiple serving cells" and Sections [1] to [5] may be further performed in combination.

[0263] An example of a communication system to which the present invention is applied

[0264] Without being limited thereto, the various descriptions, functions, procedures, suggestions, methods and / or flow charts of the present invention disclosed in this specification may be applied to various fields requiring wireless communication / connection between devices (e.g., 5G).

[0265] Hereinafter, a more detailed description will be given with reference to the drawings. In the following drawings / description, the same reference numerals denote the same or corresponding hardware blocks, software blocks or function blocks, unless otherwise specified.

[0266] FIG. 5 illustrates a communication system 1 to which the present invention is applied.

[0267] Referring to FIG. 5, the communication system 1 applied to the present invention includes wireless devices, base stations, and networks. Here, the wireless devices refer to devices that communicate using wireless connection technology (e.g., 5G NR, LTE), and are also referred to as communication / wireless / 5G devices. The wireless devices include, but are not limited to, a robot 100a, a vehicle 100b-1, 100b-2, an XR (eXtended Reality) device 100c, a handheld device (Hand-held Device) 100d, a home appliance 100e, an IoT (Internet of Thing) device 100f, and an AI server / device 400. For example, the vehicles include vehicles equipped with wireless communication functions, autonomous vehicles, vehicles capable of inter-vehicle communication, and the like. Here, the vehicles include UAVs (Unmanned Aerial Vehicles) (e.g., drones). XR devices include Augmented Reality (AR) / Virtual Reality (VR) / Mixed Reality (MR) devices, and are embodied in the form of Head-Mounted Devices (HMDs), Head-Up Displays (HUDs) mounted on vehicles, TVs, smartphones, computers, wearable devices, home appliances, digital billboards, vehicles, robots, etc. Portable devices include smartphones, smart pads, wearable devices (e.g., smart watches, smart glasses), computers (e.g., notebook computers, etc.), etc. Home appliances include TVs, refrigerators, washing machines, etc. IoT devices include sensors, smart meters, etc. For example, base stations and networks may also be embodied as wireless devices, and a specific wireless device 200a may operate as a base station / network node for other wireless devices.

[0268] The wireless devices 100a to 100f are connected to a network 300 via a base station 200. AI (Artificial Intelligence) technology is applied to the wireless devices 100a to 100f, and the wireless devices 100a to 100f are connected to an AI server 400 via the network 300. The network 300 is configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. The wireless devices 100a to 100f can communicate with each other via the base station 200 / network 300, but can also communicate directly without going through the base station / network (e.g., sidelink communication). For example, the vehicles 100b-1 and 100b-2 can communicate directly (e.g., V2V (Vehicle to Vehicle) / V2X (Vehicle to everything) communication). Also, an IoT device (e.g., a sensor) can directly communicate with another IoT device (e.g., a sensor) or another wireless device 100a to 100f.

[0269] Wireless communication / connections 150a, 150b, and 150c are performed between the wireless devices 100a to 100f / base stations 200 and the base stations 200. Here, the wireless communication / connections are performed by various wireless connection technologies such as uplink / downlink communication 150a and sidelink communication 150b (or D2D communication) and communication between base stations 150c (e.g., relay, IAB (Integrated Access Backhaul) (e.g., 5G NR). Through the wireless communication / connections 150a, 150b, and 150c, the wireless devices and base stations, and the base stations and base stations can transmit / receive wireless signals to each other. For example, the wireless communication / connections 150a, 150b, and 150c can transmit / receive signals via various physical channels. To this end, based on various proposals of the present invention, any one of various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel coding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and resource allocation processes is performed.

[0270] Examples of wireless devices to which the present invention can be applied

[0271] FIG. 6 illustrates a wireless device to which the present invention can be applied.

[0272] 6, a first wireless device 100 and a second wireless device 200 transmit and receive wireless signals using various wireless connection technologies (e.g., LTE, NR). Here, {the first wireless device 100, the second wireless device 200} corresponds to {wireless devices 100a-100f, the base station 200} and / or {wireless devices 100a-100f, the wireless devices 100a-100f} in FIG. 5.

[0273] The first wireless device 100 includes one or more processors 102 and one or more memories 104, and further includes one or more transceivers 106 and / or one or more antennas 108. The processor 102 is configured to control the memory 104 and / or the transceiver 106 to implement the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein. For example, the processor 102 processes information in the memory 104 to generate a first information / signal, and then transmits a wireless signal including the first information / signal via the transceiver 106. The processor 102 also receives a wireless signal including a second information / signal via the transceiver 106, and then stores information obtained from signal processing of the second information / signal in the memory 104. The memory 104 is coupled to the processor 102 and stores various information related to the operation of the processor 102. For example, the memory 104 stores software code including instructions for performing some or all of the processes controlled by the processor 102 or for performing the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein. Here, the processor 102 and memory 104 are part of a communication modem / circuit / chip designed to implement a wireless communication technology (e.g., LTE, NR). The transceiver 106 is coupled to the processor 102 and transmits and / or receives wireless signals via one or more antennas 108. The transceiver 106 includes a transmitter and / or a receiver. The transceiver 106 may also be referred to as an RF (Radio Frequency) unit. In the present invention, a wireless device may also refer to a communication modem / circuit / chip.

[0274] The second wireless device 200 includes one or more processors 202 and one or more memories 204, and further includes one or more transceivers 206 and / or one or more antennas 208. The processor 202 is configured to control the memory 204 and / or the transceiver 206 to implement the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein. For example, the processor 202 processes information in the memory 204 to generate a third information / signal, and then transmits a wireless signal including the third information / signal via the transceiver 206. The processor 202 also receives a wireless signal including a fourth information / signal via the transceiver 206, and then stores information obtained from the signal processing of the fourth information / signal in the memory 204. The memory 204 is coupled to the processor 202 and stores various information related to the operation of the processor 202. For example, the memory 204 stores software code including instructions for performing some or all of the processes controlled by the processor 202 or for performing the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein. Here, the processor 202 and memory 204 are part of a communication modem / circuit / chip designed to implement a wireless communication technology (e.g., LTE, NR). The transceiver 206 is coupled to the processor 202 and transmits and / or receives wireless signals via one or more antennas 208. The transceiver 206 includes a transmitter and / or a receiver. The transceiver 206 may also be referred to as an RF unit. In the present invention, a wireless device may also refer to a communication modem / circuit / chip.

[0275] The hardware elements of the wireless device 100, 200 are described in more detail below. One or more protocol layers may be implemented by, but are not limited to, one or more processors 102, 202. For example, the one or more processors 102, 202 may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP). The one or more processors 102, 202 may generate one or more Protocol Data Units (PDUs) and / or one or more Service Data Units (SDUs) according to the descriptions, functions, procedures, suggestions, methods and / or flowcharts disclosed herein. The one or more processors 102, 202 may generate messages, control information, data or information according to the descriptions, functions, procedures, suggestions, methods and / or flowcharts disclosed herein. The one or more processors 102, 202 may generate and provide signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data or information according to the functions, procedures, suggestions and / or methods disclosed herein to the one or more transceivers 106, 206. The one or more processors 102, 202 may receive signals (e.g., baseband signals) from the one or more transceivers 106, 206 and derive the PDUs, SDUs, messages, control information, data or information according to the descriptions, functions, procedures, suggestions, methods and / or flowcharts disclosed herein.

[0276] The one or more processors 102, 202 may also be referred to as controllers, microcontrollers, microprocessors, or microcomputers. The one or more processors 102, 202 may be implemented using hardware, firmware, software, or a combination thereof. As an example, the one or more processors 102, 202 may include 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). The descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, and the like. The firmware or software configured to perform the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein may be included in the one or more processors 102, 202, or may be stored in one or more memories 104, 204 and run by the one or more processors 102, 202. The descriptions, functions, procedures, suggestions, methods and / or flow charts disclosed in this specification may be embodied using firmware or software in the form of code, instructions and / or sets of instructions.

[0277] The one or more memories 104, 204 may be coupled to the one or more processors 102, 202 and may store various forms of data, signals, messages, information, programs, code, instructions, and / or commands. The one or more memories 104, 204 may be comprised of ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer readable storage media, and / or combinations thereof. The one or more memories 104, 204 may be located internal and / or external to the one or more processors 102, 202. Additionally, the one or more memories 104, 204 may be coupled to the one or more processors 102, 202 via various techniques, such as wired or wireless connections.

[0278] One or more transceivers 106, 206 may transmit user data, control information, wireless signals / channels, etc., as described in the methods and / or flow charts, etc., herein to one or more other devices. One or more transceivers 106, 206 may receive user data, control information, wireless signals / channels, etc., as described in the descriptions, functions, procedures, suggestions, methods and / or flow charts, etc., disclosed herein from one or more other devices. For example, one or more transceivers 106, 206 may be coupled to one or more processors 102, 202 and may transmit and receive wireless signals. For example, one or more processors 102, 202 may control one or more transceivers 106, 206 to transmit user data, control information, or wireless signals to one or more other devices. Also, one or more processors 102, 202 may control one or more transceivers 106, 206 to receive user data, control information, or wireless signals from one or more other devices. Furthermore, the one or more transceivers 106, 206 are coupled to one or more antennas 108, 208, and the one or more transceivers 106, 206 are configured to transmit and receive user data, control information, radio signals / channels, etc., as referred to in the descriptions, functions, procedures, suggestions, methods and / or flow charts disclosed herein, via the one or more antennas 108, 208. In this specification, the one or more antennas are multiple physical antennas or multiple logical antennas (e.g., antenna ports). The one or more transceivers 106, 206 convert the received user data, control information, radio signals / channels, etc., from RF band signals to baseband signals for processing using the one or more processors 102, 202. The one or more transceivers 106, 206 convert the user data, control information, radio signals / channels, etc., processed using the one or more processors 102, 202, from baseband signals to RF band signals. For this purpose, the one or more transceivers 106, 206 include (analog) oscillators and / or filters.

[0279] Examples of use of wireless devices to which this invention can be applied

[0280] 7 shows another example of a wireless device to which the present invention is applied. The wireless device may be embodied in various forms depending on the use case / service (see FIG. 5).

[0281] 7, the wireless devices 100, 200 correspond to the wireless devices 100, 200 of FIG. 6 and are composed of various elements, components, units / parts and / or modules. For example, the wireless devices 100, 200 include a communication unit 110, a control unit 120, a memory unit 130 and an additional element 140. The communication unit includes a communication circuit 112 and a transceiver 114. For example, the communication circuit 112 includes one or more processors 102, 202 and / or one or more memories 104, 204 in FIG. 6. For example, the transceiver 114 includes one or more transceivers 106, 206 and / or one or more antennas 108, 208 in FIG. 6. The control unit 120 is electrically connected to the communication unit 110, the memory unit 130 and the additional element 140 and controls the overall operation of the wireless device. For example, the control unit 120 controls electrical / mechanical operations of the wireless device based on the programs / codes / commands / information stored in the memory unit 130. In addition, the control unit 120 transmits information stored in the memory unit 130 to the outside (e.g., another communication device) via the communication unit 110 through a wireless / wired interface, or stores information received from the outside (e.g., another communication device) via the communication unit 110 through a wireless / wired interface in the memory unit 130.

[0282] The additional element 140 may be configured in various ways depending on the type of wireless device. For example, the additional element 140 may include any one of a power unit / battery, an input / output unit (I / O unit), a driving unit, and a computer unit. The wireless device may be embodied in the form of, but not limited to, a robot (FIG. 5, 100a), a vehicle (FIG. 5, 100b-1, 100b-2), an XR device (FIG. 5, 100c), a mobile device (FIG. 5, 100d), a home appliance (FIG. 5, 100e), an IoT device (FIG. 5, 100f), a digital broadcasting terminal, a hologram device, a public safety device, an MTC device, a medical device, a Fintech device (or a financial device), a security device, a climate / environment device, an AI server / device (FIG. 5, 400), a base station (FIG. 5, 200), and a network node. The wireless device may be mobile or fixed depending on the use case / service.

[0283] In FIG. 7, the various elements, components, units / sections and / or modules within the wireless devices 100, 200 are all coupled to each other by wired interfaces or at least some are wirelessly coupled to each other by a communication unit 110. For example, in the wireless devices 100 and 200, the control unit 120 and the communication unit 110 are connected by wire, and the control unit 120 and a first unit (e.g., 130, 140) are connected wirelessly via the communication unit 110. In addition, each element, component, unit / part and / or module in the wireless devices 100 and 200 further includes one or more elements. For example, the control unit 120 is composed of a set of one or more processors. For example, the control unit 120 is composed of a set of a communication control processor, an application processor, an ECU (Electronic control Unit), a graphics processor, a memory control processor, etc. As another example, the memory unit 130 is composed of a Random Access Memory (RAM), a Dynamic RAM (DRAM), a Read Only Memory (ROM), a flash memory, a volatile memory, a non-volatile memory and / or a combination thereof.

[0284] Examples of vehicles or autonomous vehicles to which the present invention can be applied

[0285] 8 is a diagram illustrating a vehicle or an autonomous vehicle to which the present invention is applied. The vehicle or the autonomous vehicle may be realized as a mobile robot, a car, a train, an aerial vehicle (AV), a ship, or the like.

[0286] 8, a vehicle or autonomous vehicle 100 includes 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 is configured as a part of the communication unit 110. Blocks 110 / 130 / 140a to 140d correspond to blocks 110 / 130 / 140 in FIG. 6, respectively.

[0287] The communication unit 110 transmits and receives signals (e.g., data, control signals, etc.) to and from external devices such as other vehicles, base stations (e.g., base stations, road side units, etc.), and servers. The control unit 120 controls elements of the vehicle or autonomous vehicle 100 to perform various operations. The control unit 120 includes an ECU (Electronic Control Unit). The driving unit 140a causes the vehicle or autonomous vehicle 100 to run on the ground. The driving unit 140a includes an engine, a motor, a power train, wheels, brakes, a steering device, etc. The power supply unit 140b supplies power to the vehicle or autonomous vehicle 100 and includes wired / wireless charging circuits, a battery, etc. The sensor unit 140c can obtain vehicle status, surrounding environment information, user information, etc. The sensor unit 140c includes an IMU (inertial measurement unit) sensor, a collision sensor, a wheel sensor, a speed sensor, a tilt 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, an illuminance sensor, a pedal position sensor, etc. The autonomous driving unit 140d embodies a technology for maintaining a lane while driving, a technology for automatically adjusting speed such as an adaptive cruise control, a technology for automatically driving according to a predetermined route, a technology for automatically setting a route when a destination is set, and the like.

[0288] For example, the communication unit 110 receives map data, traffic information data, etc. from an external server. The autonomous driving unit 140d generates an autonomous driving route and a drive plan based on the obtained data. The control unit 120 controls the driving unit 140a (e.g., speed / direction adjustment) so that the vehicle or autonomous driving vehicle 100 moves along the autonomous driving route according to the drive plan. The communication unit 110 non-periodically obtains the latest traffic information data from an external server during autonomous driving, and also obtains surrounding traffic information data from surrounding vehicles. In addition, the sensor unit 140c obtains vehicle status and surrounding environment information during autonomous driving. The autonomous driving unit 140d updates the autonomous driving route and the drive plan based on the newly obtained data / information. The communication unit 110 transmits information regarding the vehicle position, the autonomous driving route, the drive plan, etc. to the external server. The external server can predict traffic information data in advance using AI technology, etc. 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.

[0289] It is obvious to those skilled in the art that the present invention can be embodied in other specific forms without departing from the characteristics of the present invention. Therefore, the above detailed description should not be interpreted as limiting in all respects, but should be considered as illustrative. The scope of the present invention should be determined by reasonable interpretation of the appended claims, and all modifications within the equivalent scope of the present invention are included in the scope of the present invention. [Industrial Applicability]

[0290] As previously mentioned, the present invention may be applied to a variety of wireless communication systems.

Claims

1. A method for monitoring a control signal by a terminal (UE) in a wireless communication system, comprising: determining a control channel element (CCE) index corresponding to a PDCCH candidate; monitoring the PDCCH candidates for a downlink control information (DCI) format on a scheduling cell based on the CCE index; Based on the DCI format being a first DCI format for scheduling a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH) on one scheduled cell, the CCE index is set based on a value of a carrier indicator field (CIF) included in the DCI format, Based on the DCI format being a second DCI format for scheduling a PDSCH or a PUSCH on a plurality of scheduled cells, the CCE index is set independently for each specific combination of the plurality of scheduled cells. Signal monitoring methods.

2. based on the DCI format being the second DCI format, the DCI format does not include the CIF; 2. The method of claim 1.

3. The second DCI format schedules a PDSCH or a PUSCH on all or a part of the scheduled cells belonging to the specific combination.

2. The method of claim 1.

4. The DCI format meets the DCI size budget through a DCI size alignment process.

2. The method of claim 1.

5. The DCI size alignment process is performed on one reference cell among the plurality of scheduled cells.

5. The method of claim 4.

6. The DCI size alignment process includes performing a first DCI size alignment process for a conventional DCI format based on the fact that a total number of DCI sizes set to be monitored for the reference cell exceeds 4 excluding the second DCI format, or a total number of DCI sizes related to a Cell-Radio Network Temporary Identifier (C-RNTI) set to be monitored for the reference cell exceeds 3 excluding the second DCI format; The first DCI size alignment process includes: DCI size alignment between DCI format 1_0 and DCI format 0_0; DCI size alignment between DCI format 0_2 and DCI format 1_2; DCI size alignment between DCI format 0_1 ​​and DCI format 1_1, in that order.

6. The method of claim 5.

7. The DCI size alignment process includes performing a second DCI size alignment process for the second DCI format based on the fact that a total number of DCI sizes set to be monitored for the reference cell exceeds 4 including the second DCI format, or a total number of DCI sizes related to a Cell-Radio Network Temporary Identifier (C-RNTI) set to be monitored for the reference cell exceeds 3 including the second DCI format.

7. The method of claim 6, wherein the signal is monitored by a plurality of sensors.

8. The second DCI size alignment process includes aligning a size of a DCI format for scheduling a PDSCH on a plurality of scheduled cells and a size of a DCI format for scheduling a PUSCH on a plurality of scheduled cells to be the same.

8. The method of signal monitoring according to claim 7.

9. The second DCI size alignment process includes aligning a size of a DCI format for scheduling PDSCHs on a plurality of scheduled cells and a size of a DCI format for scheduling PDSCHs on one scheduled cell to be the same.

8. The method of signal monitoring according to claim 7.

10. The second DCI size alignment process includes aligning a size of a DCI format for scheduling a PUSCH on a plurality of scheduled cells and a size of a DCI format for scheduling a PUSCH on one scheduled cell to be the same.

8. The method of signal monitoring according to claim 7.

11. 1. A terminal for monitoring signals in a wireless communication system, comprising: At least one transceiver; At least one processor; at least one memory operatively connected to said at least one processor and storing instructions that, when executed, cause said at least one processor to perform certain operations; The specific operation is: determining a control channel element (CCE) index corresponding to a PDCCH candidate; monitoring the PDCCH candidates for a downlink control information (DCI) format on a scheduling cell based on the CCE index; Based on the DCI format being a first DCI format for scheduling a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH) on one scheduled cell, the CCE index is set based on a carrier indicator field (CIF) value included in the DCI format, Based on the DCI format being a second DCI format for scheduling a PDSCH or a PUSCH on a plurality of scheduled cells, the CCE index is set independently for each specific combination of the plurality of scheduled cells. Terminal.

12. An apparatus for a terminal, comprising: At least one processor; at least one computer memory operatively connected to the at least one processor and which, when executed, causes the at least one processor to perform operations, the operations including: determining a control channel element (CCE) index corresponding to a PDCCH candidate; monitoring the PDCCH candidates for a downlink control information (DCI) format on a scheduling cell based on the CCE index; Based on the DCI format being a first DCI format for scheduling a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH) on one scheduled cell, the CCE index is set based on a carrier indicator field (CIF) value included in the DCI format, Based on the DCI format being a second DCI format for scheduling a PDSCH or a PUSCH on a plurality of scheduled cells, the CCE index is set independently for each specific combination of the plurality of scheduled cells. Device.

13. A computer readable non-volatile storage medium containing at least one computer program causing at least one processor to perform operations, said operations including: determining a control channel element (CCE) index corresponding to a PDCCH candidate; monitoring the PDCCH candidates for a downlink control information (DCI) format on a scheduling cell based on the CCE index; Based on the DCI format being a first DCI format for scheduling a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH) on one scheduled cell, the CCE index is set based on a carrier indicator field (CIF) value included in the DCI format, Based on the DCI format being a second DCI format for scheduling a PDSCH or a PUSCH on a plurality of scheduled cells, the CCE index is set independently for each specific combination of the plurality of scheduled cells. Storage medium.

Images