Method and apparatus for transmitting and receiving signals in a wireless communication system

Abstract

A method and apparatus for transmitting and receiving signals in a wireless communication system according to the present invention transmits and receives DCI used to schedule multiple channels in multiple cells, including one channel per cell, wherein the DCI includes information indicating a predetermined scheduled cell set among the one or more scheduled cell sets.

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. Generally, wireless communication systems are multiple access systems that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit 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, and single carrier frequency division multiple access (SC-FDMA) systems. Summary of the Invention [Problem to be solved by the invention]

[0003] A technical problem to be solved by the present invention is to provide a signal transmission / reception method and apparatus for efficiently transmitting and receiving control signals and data 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 transmitting and receiving signals in a wireless communication system.

[0006] As one embodiment of the present invention, there is provided a signal transmission / reception method for a terminal (UE) in a wireless communication system, the method including: setting one or more scheduled cell sets based on RRC (radio resource control) parameters; receiving downlink control information (DCI) used to schedule multiple channels in multiple cells to include one channel per cell, the DCI including information indicating a specific scheduled cell set among the one or more scheduled cell sets; and transmitting or receiving the multiple channels on all or some of the cells included in the specific scheduled cell set.

[0007] As another embodiment of the present invention, there is provided a signal transmission / reception method in a wireless communication system, in which a base station (BS) transmits and receives signals, the method including: transmitting radio resource control (RRC) parameters for setting one or more scheduled cell sets; transmitting downlink control information (DCI) used to schedule multiple channels in multiple cells to include one channel per cell, the DCI including information indicating a specific scheduled cell set among the one or more scheduled cell sets; and transmitting or receiving the multiple channels on all or some of the cells included in the specific scheduled cell set.

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

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

[0010] 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 apparent to those skilled in the art based on the detailed description of the present invention below. [Effects of the Invention]

[0011] According to one embodiment of the present invention, when control signals and data signals are transmitted and received between communication devices, there is an advantage that more efficient signal transmission and reception can be achieved through operations differentiated from conventional inventions.

[0012] 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 explanation of the drawings]

[0013] [Figure 1] FIG. 1 is a diagram illustrating the structure of a radio frame. [Figure 2] FIG. 1 illustrates a resource grid of slots. [Figure 3] FIG. 10 is a diagram showing an example of mapping physical channels within a slot. [Figure 4] FIG. 2 is a diagram illustrating an example of a signal transmission and reception method according to an embodiment of the present invention. [Figure 5] 1 illustrates an apparatus according to one embodiment of the present invention. [Figure 6] 1 illustrates an apparatus according to one embodiment of the present invention. [Figure 7] 1 illustrates an apparatus according to one embodiment of the present invention. [Figure 8] 1 illustrates an apparatus according to one embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0014] 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 UTRA (Universal Terrestrial Radio Access) and CDMA2000. TDMA can be implemented by radio technologies such as GSM (Global System for Mobile communications), GPRS (General Packet Radio Service), and EDGE (Enhanced Data Rates for GSM Evolution). OFDMA can be implemented by radio technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, E-UTRA (Evolved UTRA), etc. UTRA is part of UMTS (Universal Mobile Telecommunications System). 3GPP (registered trademark) (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 are evolved versions of 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is an evolved version of 3GPP LTE / LTE-A / LTE-A pro.

[0015] For clarity, the following description will be based on a 3GPP communication system (e.g., LTE-A, NR), but the technical concept of the present invention is not limited thereto. LTE refers to technology from 3GPP TS 36.xxx Release 8 onward. Specifically, LTE technology from 3GPP TS 36.xxx Release 10 onward is called LTE-A, and LTE technology from 3GPP TS 36.xxx Release 13 onward is called LTE-A pro. 3GPP NR refers to technology from TS 38.xxx Release 15 onward. LTE / NR can also be referred to as a 3GPP system. "xxx" refers to the specific number of the standard document. LTE / NR is collectively referred to as a 3GPP system. For background technology, terms, abbreviations, etc. used in the description of the present invention, please refer to the matters described in standard documents published before the present invention. For example, the following documents may be referenced:

[0016] 3GPP NR

[0017] - 38.211: Physical channels and modulation

[0018] - 38.212: Multiplexing and channel coding

[0019] - 38.213: Physical layer procedures for control

[0020] - 38.214: Physical layer procedures for data

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

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

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

[0024] 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 regular CP is used, each slot contains 14 symbols. If an extended CP is used, each slot contains 12 symbols. Here, a symbol can include an OFDM symbol (or a CP-OFDM symbol) or an SC-FDMA symbol (or a DFT-s-OFDM symbol).

[0025] 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.

[0026] [Table 1]

[0027] Table 2 illustrates how the number of symbols per slot, the number of slots per frame, and the number of slots per subframe change depending on the SCS when an extended CP is used.

[0028] [Table 2]

[0029] In an NR system, multiple cells merged to one user equipment (UE) are configured to have different OFDM(A) pneumatics (e.g., SCS, CP length, etc.), which results in different (absolute time) durations 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.

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

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

[0032] [Table 3]

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

[0034] A slot contains multiple symbols in the time domain. For example, in the case of a general CP, one slot contains 14 symbols, while in the case of an extended CP, one slot contains 12 symbols. A carrier contains multiple subcarriers in the frequency domain. An RB (Resource Block) is defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. Multiple RB interlaces (or simply, interlaces) are defined in the frequency domain. Interlace m ∈ {0, 1, ..., M-1} consists of (common) RBs {m, M+m, 2M+m, 3M+m, ...}, where M represents 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 contains up to N BWPs (e.g., 5). Data communication is performed using activated BWPs, and only one BWP can be 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.

[0035] 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 exchanged between the base station and the terminal includes data and various control information, and various physical channels / signals exist depending on the type / purpose of the information exchanged. 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. 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.

[0036] 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 RSs 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 RSs. UL RSs include DM-RS, PT-RS, and SRS (Sounding RS).

[0037] FIG. 3 shows an example of mapping physical channels into slots.

[0038] A single slot contains the DL control channel, DL or UL data, and UL control channel. For example, the first N symbols in a slot are used to transmit the DL control channel (hereinafter referred to as the DL control region), and the last M symbols in a slot are used to transmit the UL control channel (hereinafter referred to as the 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 referred to as the data region) is used to transmit DL data or UL data. A time gap exists 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 within a slot are used as the time gap.

[0039] The base station is, for example, a gNodeB.

[0040] Downlink (DL) physical channels / signals

[0041] (1) PDSCH

[0042] 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 after undergoing scrambling and modulation processes. The CW includes one or more code blocks (CB). One or more CBs are grouped into a 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 along with DMRS, and transmitted from the corresponding antenna port. The PDSCH is dynamically scheduled by the PDCCH (configured 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)). Therefore, in dynamic scheduling, PDSCH transmission is accompanied by PDCCH, whereas in CS, PDSCH transmission is not accompanied by PDCCH. CS includes SPS (semi-persistent scheduling).

[0043] (2) PDCCH

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

[0045] Table 4 illustrates DCI formats transmitted via the PDCCH.

[0046] [Table 4]

[0047] DCI format 0_0 is used to schedule a TB-based (or TB-level) PUSCH, and DCI format 0_1 is used to schedule a TB-based (or TB-level) PUSCH or a Code Block Group (CBG)-based (or CBG-level) PUSCH. DCI format 1_0 is used to schedule a TB-based (or TB-level) PDSCH, and DCI format 1_1 is used to schedule a TB-based (or TB-level) PDSCH or a CBG-based (or CBG-level) PDSCH (DL grant DCI). DCI formats 0_0 / 0_1 are referred to as UL grant DCI or UL scheduling information, and DCI formats 1_0 / 1_1 are referred to as DL grant DCI or UL scheduling information. DCI format 2_0 is used to convey dynamic slot format information (e.g., dynamic SFI) to a UE, and DCI format 2_1 is used to convey downlink pre-emption information to a UE. 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.

[0048] 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 a Cell-RNTI (C-RNTI). If the PDCCH is related to paging, the CRC is masked to a P-RNTI (Paging-RNTI). If the PDCCH is related to system information (e.g., System Information Block, SIB), the CRC is masked to a System Information RNTI (SI-RNTI). If the PDCCH is related to an unsolicited access response, the CRC is masked to a Random Access-RNTI (RA-RNTI).

[0049] Table 5 illustrates the use and transmission channel of the PDCCH according to the RNTI. The transmission channel indicates the transmission channel associated with the data carried by the PDSCH / PUSCH scheduled by the PDCCH.

[0050] [Table 5]

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

[0052] The PDCCH is transmitted in a CORESET (Control Resource Set). The CORESET corresponds to a set of physical resources / parameters used to carry the PDCCH / DCI in the BWP. For example, the CORESET includes a REG set having a predetermined pneumatics (e.g., SCS, CP length, etc.). The 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 the CORESET are as follows: One or more CORESETs are configured for one UE, and multiple CORESETs are superimposed in the time / frequency domain.

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

[0054] - frequencyDomainResources: Indicates the frequency domain resources of CORESET. It is indicated by a bitmap, and each bit corresponds to an RB group (= 6 consecutive RBs). For example, the MSB (Most Significant Bit) 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 CORESET.

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

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

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

[0058] - 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 the Quasi-Co-Location (QCL) relationship between DL RSs and PDCCH DMRS ports within the RS set (TCI-State).

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

[0060] - pdcch-DMRS-ScramblingID: indicates information used to initialize the PDCCH DMRS scrambling sequence.

[0061] For PDCCH reception, the UE monitors a set of PDCCH candidates in CORESET (e.g., blind decoding). 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 in 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.

[0062] Table 6 illustrates the PDCCH search space.

[0063] [Table 6]

[0064] 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 for 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.

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

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

[0067] - monitoringSlotPeriodicityAndOffset: Indicates the PDCCH monitoring periodicity period (slot unit) and the PDCCH monitoring period offset (slot unit).

[0068] - monitoringSymbolsWithinSlot: Indicates the first OFDMA symbol for PDCCH monitoring within a slot where PDCCH monitoring is configured. It is indicated by a bitmap, and each bit corresponds to each OFDMA symbol within the slot. The MSB of the bitmap corresponds to the first OFDMA symbol within the slot. The OFDMA symbol corresponding to a bit whose bit value is 1 corresponds to the first symbol of CORESET within the slot.

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

[0070] - searchSpaceType: Indicates whether the SS type is CSS or USS.

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

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

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

[0074] The above content can be applied in combination with the method proposed in the present invention to be described later, or is supplemented to clarify the technical features of the method proposed in the present invention.

[0075] In addition, the method described below can be similarly applied to the aforementioned NR system (licensed band) or shared spectrum, and of course can be modified or substituted according to the terms, expressions, structures, etc. defined in each system so that the technical ideas proposed in the present invention can be embodied in those systems as well.

[0076] In order to reduce DCI overhead for PDSCH / PUSCH scheduling in a CA situation where multiple cells are configured, Rel-18 considers a multi-cell scheduling (multi-CC scheduling) scheme in which multiple serving cells / CCs are simultaneously scheduled with a single DCI (based on justification as shown in Table 7). In this specification, "scheduling multiple cells" can be understood as "scheduling PDSCHs or PUSCHs transmitted from each of multiple cells." In other words, multi-cell DCI is DCI for scheduling PDSCHs or PUSCHs on different cells.

[0077] Table 7 is a justification for supporting DCI for such purposes in Rel-18, and can be understood as one of the motivations for introducing this DCI (PDCCH).

[0078] [Table 7]

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

[0080] In the proposed method described below, for convenience of explanation, a DCI that performs multi-cell scheduling is referred to as an m-cc DCI, and a DCI that performs conventional single-cell scheduling is referred to as an s-cc DCI. Furthermore, a DCI that schedules a PDSCH and a DCI that schedules a PUSCH are not distinguished and are referred to as an m-cc DCI or an s-cc DCI. The scheduled PDSCH and / or PUSCH are sometimes referred to as a PDSCH / PUSCH (or PxSCH).

[0081] In the present specification, the term "cell" is interpreted according to the context. For example, a cell refers to a serving cell. A cell also includes one DL CC (component carrier) and zero to two UL CCs, but the method described below is not limited to this. In the following description, unless otherwise specified, the terms cell and CC can be used interchangeably. Furthermore, a cell / CC can be applied by replacing the active BWP in a serving cell. Furthermore, in the method described below, unless otherwise specified, a cell / CC can be used as a comprehensive concept for a P cell (PCell, primary cell), an S cell (SCell, secondary cell), a PS cell (PSCell, primary SCell), etc. configured / expressed in a carrier aggregation (CA) / dual connectivity (DC) scenario.

[0082] 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 the 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, it is called self-carrier scheduling, and when they are different, it is called cross-carrier scheduling.

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

[0084] [Table 8]

[0085] [Table 9]

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

[0087] [Table 10-1] [Table 10-2]

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

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

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

[0091] In this case, if cross-carrier scheduling is configured to determine cell #1 as the scheduling cell for cell #2, the terminal performs the following PDCCH monitoring in PDCCH MOs configured 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 established between cell #1 and cell #2 is referred to as a CCS relationship for convenience. Also, monitoring the PDCCH means monitoring PDCCH candidates.

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

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

[0094] For the methods described below, the values proposed / calculated in each method (e.g., the number of PDCCH candidates for each scheduled cell, or the BD counting method, or multiplying or dividing by a predetermined value to give the BD budget or weighted value, etc.) are applied as integer values derived by a ceiling or floor function in the final result unless otherwise specified.

[0095] [1] BD budget sharing (BD budget distribution) for s-cc DCI and m-cc DCI

[0096] [1-1] K scheduled cells simultaneously scheduled by m-cc DCI (or corresponding to the entire set of cells that can be scheduled by m-cc DCI) are denoted by {{cell#k},K}={cell#1,cell#2,...,cell#K}. The entire set of cells that can be scheduled by m-cc DCI is referred to as all scheduled cells. Each scheduled cell (e.g., cell#k) is scheduled by s-cc DCI or m-cc DCI. In this case, the UE needs to simultaneously monitor the s-cc DCI and the m-cc DCI (e.g., blind decoding). The possible number of BD attempts for the s-cc DCI and the m-cc DCI for each scheduled cell is set by RRC, etc. However, to reduce the monitoring burden on the UE, the maximum number of monitoring attempts (or BD executions) by the UE for each scheduled cell within a predetermined time period (e.g., one slot) is limited to not exceed a predetermined value. This requires that the number of BDs for m-cc DCI and / or s-cc DCI be readjusted.

[0097] [1-2] The number of PCs monitoring s-cc DCI for cell#k is represented by BD_single(k). The number of PCs monitoring m-cc DCI for cell#k is represented by BD_multi(k). The maximum number of BDs configured for cell#k is represented by BD_limit(k). Alternatively, in the proposed method described later, BD_single(k) may refer to the BD count for s-cc DCI monitoring for cell#k. Furthermore, BD_multi(k) may refer to the BD count for m-cc DCI monitoring for cell#k. PC refers to the number of PDCCH candidates configured per AL (aggregation level) for each cell.

[0098] [1-3] In the proposed method described later, BD_single(k) means the sum of the BD counts (or PC counts) for monitoring fallback DCI (e.g., DCI format 1_0 and / or 0_0) and non-fallback DCI (e.g., DCI format 1_1 and / or 0_1) among legacy DCIs. Alternatively, BD_single(k) can also mean only the BD counts (or PC counts) for monitoring non-fallback DCI for that cell.

[0099] [1-4] For cell#k, beta_multi and / or beta_single are set so as to satisfy the following formula.

[0100] (Formula 1-4-1) beta_multi*BD_multi(k)+beta_single*BD_single(k)<=BD_limit(k)

[0101] Here, beta_multi and beta_single refer to predetermined values (real numbers equal to or greater than 0, for example, 1, 0, or 0.5) that are predefined or set by RRC, etc. Thus, when monitoring for s-cc DCI and m-cc DCI is performed simultaneously for a predetermined scheduled cell #k, the total number of BD attempts for that cell is maintained below a predetermined number (for example, BD_limit(k)). In the above equation, a predetermined value (=K1) may be used instead of BD_limit(k), which is predefined for each cell.

[0102] (Formula 1-4-2) beta_multi*BD_multi(k)+beta_single*BD_single(k)<=K1

[0103] In this case, K1 is predefined or set by RRC etc. K1 is a value different from BD_limit(k) (for example, a value larger than BD_limit(k)).

[0104] In the proposed method described above, the number of times m-cc DCI is monitored for cell#k is beta_multi*BD_multi(k), and the number of times s-cc DCI is monitored is beta_single*BD_single(k).

[0105] [1-5] As an alternative to [1-4], beta_multi and / or beta_single are set for cell#k so as to satisfy the following formula:

[0106] (Formula 1-5-1) beta_multi*sum[BD_multi(k)]+beta_single*sum[BD_single(k)]<=sum[BD_limit(k)]

[0107] Here, beta_multi and beta_single refer to predetermined values (real numbers equal to or greater than 0, for example, 1, 0, or 0.5) that are predefined or set by RRC, etc. In addition, sum[ ] refers to the sum for all co-scheduled cells simultaneously scheduled with m-cc DCI. Alternatively, sum[ ] refers to the sum for the entire set of cells scheduled with m-cc DCI. The sum of BD_multi(k), BD_single(k), or BD_limit(k) for each cell is derived from the elements in sum[ ]. As a result, when monitoring for s-cc DCI and m-cc DCI is performed simultaneously for a predetermined scheduled cell #k, the total number of BD attempts for that cell can be maintained below a predetermined number (e.g., sum[BD_limit(k)]). In the above formula, a predetermined value (=K1_sum) may be used instead of sum[BD_limit(k)], which is predefined for each cell.

[0108] (Formula 1-5-2) beta_multi*sum[BD_multi(k)]+beta_single*sum[BD_single(k)]<=K1_sum

[0109] In this case, K1_sum is defined in advance or set by RRC or the like. K1_sum is a value different from sum[BD_limit(k)] (for example, a value larger than sum[BD_limit(k)]). In the proposed method described above, the number of times m-cc DCI is monitored for cell#k is beta_multi*BD_multi(k). The number of times s-cc DCI is monitored is beta_single*BD_single(k).

[0110] Furthermore, this method can also be applied as follows.

[0111] - If the number of PDCCH candidates for m-cc DCI (or the BD count) is configured / determined for all scheduled cells, sum[BD_multi(k)] becomes a "predetermined configuration value (=BD_multi_all)". sum[BD_single(k)] and sum[BD_limit(k)] mean the summation for all scheduled cells.

[0112] - If the number of PDCCH candidates for m-cc DCI (or the BD count) is configured / determined for each scheduled cell, sum[BD_multi(k)] is the "BD_single(k) value of that cell." sum[BD_single(k)] and sum[BD_limit(k)] refer to the values configured for the k-th cell.

[0113] - sum[BD_multi(k)] is "BD_single(k) multiplied by N (N is the number of co-scheduled cells or the number of all scheduled cells)", and the sum of sum[BD_single(k)] and sum[BD_limit(k)] means the value applied to the combination of co-scheduled cells or the set of all scheduled cells.

[0114] - If the number of PDCCH candidates for m-cc DCI (or the BD count) is set / determined in units of a combination of co-scheduled cells simultaneously scheduled with the same m-cc DCI, sum[BD_multi(k)] becomes a "predetermined setting value (=BD_multi_comb)." The sum of sum[BD_single(k)] and sum[BD_limit(k)] means the value applied to that combination of co-scheduled cells.

[0115] [1-6] As an alternative to [1-4], beta_multi and / or beta_single are set for cell#k so as to satisfy the following formula.

[0116] (Formula 1-6-1) BD_multi(k)<=beta_multi*BD_limit(k)

[0117] (Formula 1-6-2) BD_single(k)<=beta_single*BD_limit(k)

[0118] Here, beta_multi and beta_single refer to predetermined values (real numbers equal to or greater than 0, for example, 1, 0, or 0.5) that are predefined or set by RRC, etc. Thus, when monitoring for s-cc DCI and m-cc DCI is performed simultaneously for a predetermined scheduled cell #k, the total number of BD attempts for that cell can be maintained below a predetermined number (for example, BD_limit(k)). In the above equation, a predetermined value (=K2) may be used instead of BD_limit(k), which is predefined for each cell.

[0119] (Formula 1-6-3) BD_multi(k)<=beta_multi*K2

[0120] (Formula 1-6-4) BD_single(k)<=beta_single*K2

[0121] In this case, K2 is defined in advance or set by RRC or the like. K2 is a value different from BD_limit(k) (for example, a value larger than BD_limit(k)). In the proposed method described above, the number of times m-cc DCI is monitored for cell#k is BD_multi(k), and the number of times s-cc DCI is monitored is BD_single(k).

[0122] [1-7] As an embodiment of the above [1-4], [1-5], and [1-6], the number of monitoring times configured for m-cc DCI is reduced so as not to exceed the BD_limit of each scheduled cell by setting the value of beta_single to 1 (or 0) and the value of beta_multi(k) to a value between 0 and 1. In this case, reducing the number of monitoring times configured means that the terminal monitors a number (e.g., beta_multi*BD_multi(k)) of PDCCH candidates configured for cell #k for monitoring the m-cc DCI. In this case, the terminal is configured to preferentially monitor PDCCH candidates having relatively low indices (or less than or equal to a predetermined value) for the m-cc DCI, and drop monitoring of certain PDCCH candidates having relatively high indices (or more than a predetermined value).

[0123] [1-8] As another embodiment of the above [1-4], [1-5], and [1-6], the number of monitoring times configured for s-cc DCI is reduced so as not to exceed the BD_limit of each scheduled cell by setting the value of beta_multi to 1 (or 0) and the value of beta_single(k) to a value between 0 and 1. In this case, reducing the number of monitoring times configured means that the terminal monitors a number of PDCCH candidates (e.g., beta_single * BD_single(k)) that is smaller than the number of PDCCH candidates (e.g., BD_single(k)) configured for cell #k for monitoring the s-cc DCI. In this case, the terminal is configured to preferentially monitor PDCCH candidates with relatively low indices (or less than or equal to a predetermined value) for the s-cc DCI, and drop monitoring of certain PDCCH candidates with relatively high indices (or greater than a predetermined value).

[0124] [1-9] Any one of the following conditions can be applied to the above [1-4], [1-5], and [1-6].

[0125] (Formula 1-7-1) BD_multi(k)+BD_single(k)<=BD_limit(k)

[0126] (Formula 1-7-2) BD_multi(k)+BD_single(k)<=K3

[0127] (Formula 1-7-3) BD_multi(k)+BD_single(k)=1

[0128] (Formula 1-7-4) BD_multi(k)+BD_single(k)=K4

[0129] In this case, K3 and K4 are either predefined or set by RRC or the like.

[0130] [1-10] In the proposed method described above, a weight value may be assigned to each scheduled cell in m-cc scheduling according to the number (or ratio) of co-scheduled cell sets that include that cell. For example, if the combination of co-scheduled cells that can be scheduled with m-cc DCI is {cell#1, cell#2} or {cell#2, cell#3}, the BD_multi (or beta_multi) setting value for cell#2 is 2 times or 0.5 times the value set for cell#1 and / or cell#3.

[0131] [2] If a given PDCCH candidate is not counted as monitored

[0132] Monitoring of PDCCH candidates for s-cc DCI is not counted as a monitoring occurrence under the following conditions:

[0133] Table 11 is part of 3GPP TS 38.213.

[0134] [Table 11]

[0135] Referring to Table 11, a PDCCH candidate (=m_j) for an SS set (=s_j) of a given cell (=n_CI) is not counted as a further monitoring count if it meets a certain condition for the same cell (=n_CI) (i.e., when there is an SS / PC with the same CORESET CCEs, DCI size, and scrambling as the SS / PC in question).

[0136] This operation can be similarly applied to PDCCH candidates for m-cc DCI, i.e., PDCCH candidates for m-cc DCI for the same set of co-scheduled (or schedulable) cell combinations are not counted as further monitoring counts if the following predetermined conditions are met:

[0137] A set of identical co-scheduled (or schedulable) cell combinations means the same co-scheduled cell combination when a cell combination that is scheduled simultaneously with the same m-cc DCI is defined as a co-scheduled cell combination, and means any co-scheduled cell combination that belongs to the same schedulable cell combination when the entire set of cells that can be scheduled with the same m-cc DCI is defined as a schedulable cell combination (schedulable cell set).

[0138] In other words, two or more PDCCH candidates of m-cc DCI for the same set of co-scheduled (or schedulable) cell combinations are counted as one monitoring if the following predetermined conditions are met:

[0139] In this case, the predetermined condition is a combination of one or more of the following:

[0140] - When the scheduling cells of the m-cc scheduling of two PDCCH candidates are the same

[0141] - If the CORESETs of the two PDCCH candidates are the same

[0142] - When two PDCCH candidates are SS sets configured in the same L (=AL) CCE sets

[0143] - When the DCI size of two PDCCH candidates is the same

[0144] - When the same scrambling is used for two PDCCH candidates in the DCI decoding process

[0145] [3] A method of configuring the largest group of cells that can be scheduled at one time using m-cc DCI and configuring an SS set for each group.

[0146] Co-schedulable cell groups that can be scheduled simultaneously by m-cc DCI are pre-defined, an SS set is defined for each group, and the BD count, DCI size, etc. are determined for each group.

[0147] [3-1] Co-schedulable cell groups are separately configured by RRC. In this specification, co-schedulable cell groups are also referred to as scheduled cell sets or scheduled cell combinations. The m-cc DCI indicates the group index. That is, the DCI indicates the scheduled cell set. The DCI also indicates a list of cells in the group that will actually be scheduled. That is, the DCI indicates the cells that actually transmit the PUSCH or receive the PDSCH, among the cells belonging to the scheduled cell set.

[0148] For example, RRC configures co-schedulable cell groups such as group_1={cell#1, cell#2}, group_2={cell#3, cell#4}, and group_3={cell#1, cell#2, cell#3}. One of the configured groups is scheduled by m-cc DCI. If group_1 is scheduled by m-cc DCI, the m-cc DCI includes an indicator indicating group_1. The m-cc DCI also indicates the cell (or cell combination) in which the PUSCH or PDSSCH is scheduled among the cells included in group_1. For example, when group_1 is indicated, the cells that are scheduled simultaneously with the m-cc DCI are one of {cell#1}, {cell#2}, and {cell#1,cell#2}, and when group_2 is indicated, the cells that are scheduled simultaneously with the m-cc DCI are one of {cell#3}, {cell#4}, and {cell#3,cell#4}.

[0149] An RRC parameter indicating a scheduled cell set is, for example, MC-DCI-SetofCellsToAddModList. This RRC parameter is a list of up to N (N<=4) configurations of set(s) of cells for multi-cell PDSCH / PUSCH scheduling from the serving cell, where N is reported as UE capability and up to 4 sets of cells can be configured per PUCCH group. The set of cells for multi-cell PDSCH / PUSCH scheduling refers to a set of scheduled cells (or scheduled cell sets) for which PDSCH / PUSCH is scheduled by multi-cell PDSCH / PUSCH scheduling.

[0150] Furthermore, the RRC parameters that indicate the scheduled cell set are set for each scheduling cell and are set terminal-specific.

[0151] Table 12 shows the relationship between the bit field values of the indicator included in the DCI and the scheduled cell set. An indicator indicating a scheduled cell set is called a scheduled cell set indicator. Since the scheduled cell set indicator should indicate one of the groups indicated by the RRC parameters, the number of bits is determined based on the number of groups configured by the RRC parameters. For example, if the number of cell sets configured by the RRC parameters is N_set, the number of bits of the scheduled cell set indicator is ceil(log2(N_set)). Of the cells included in the indicated scheduled cell set, a cell that is actually used for receiving or transmitting a channel is called a scheduled cell. A scheduled cell is indicated by a scheduled cell indicator, which is separate from the scheduled cell set indicator.

[0152] [Table 12]

[0153] [3-2] In contrast to the above-mentioned [3-1], when one specified cell (=ref_cell) is specified among the cells belonging to a specified group, the BD count and / or DCI size count of the m-cc DCI that schedules all or some of the cells in the group is performed only on that ref_cell. For example, if the ref_cell of group_1 is set to cell#1, when {cell#1} is scheduled, {cell#2} is scheduled, or {cell#1, cell#2} is scheduled by the m-cc DCI, the BD count and / or DCI size count is applied to cell#1.

[0154] [3-3] In contrast to the above-mentioned [3-1], the same DCI size is used for DCIs that schedule all or some of the cells belonging to the same group. For example, when scheduling only cell #1 (or cell #2 or cell #3) by m-cc DCI for group_3 illustrated in [3-1], when simultaneously scheduling {cell #2, cell #3}, or when simultaneously scheduling {cell #1, cell #2, cell #3}, the same DCI size is used. The same DCI size is determined when the co-scheduled cell is the largest (or when the DCI size is the largest).

[0155] [3-4] In contrast to the above-mentioned [3-1], the same SS set is used for m-cc DCIs that schedule all or some of the cells belonging to the same group. Alternatively, some of the same settings may be used even if the SS set indexes are different. For example, the same SS set (e.g., the same SS set index) is configured for two m-cc DCIs that schedule {cell#1} and {cell#2} that belong to the same group. In this case, the SS set settings are all the same. As another example, different SS sets (e.g., different SS set indexes) are used for two m-cc DCIs that schedule {cell#1} and {cell#2} that belong to the same group, but some of the settings of the two SS sets are shared. In this case, the settings that can be shared include the number of PCs per AL, settings related to monitoring occasions such as periodicity / offset / duration, CIF value, n_CI value, etc.

[0156] [3-5] In contrast to [3-1] above, for an m-cc DCI that schedules all or some of the cells belonging to the same group, the monitoring BD count for that DCI is counted as 1. For example, when two m-cc PDCCHs that schedule {cell#1} and {cell#2} that belong to the same group are monitored in the same slot, the BD for the two PDCCHs is counted only once.

[0157] As an example of the above [3-1] to [3-5], when the total set of scheduled cells (configured for a specific terminal) that can be scheduled by m-cc DCI consists of eight cells (#1 to #8), the m-cc DCI of a specific scheduling cell (#A) has only a subset of {cell #1, #2} as scheduled cells. Also, the m-cc DCI of a different scheduling cell (#B) is configured to have only a subset of {cell #3, #4, #5, #6, #7, #8} as scheduled cells. That is, when the scheduling cell of the m-cc DCI is cell #A and when it is cell #B (different from cell #A), the set of scheduled cells that can be scheduled simultaneously is configured to be different. For example, for a scheduling cell belonging to FR1 and a scheduling cell belonging to FR2, the set of scheduled cells that can be scheduled simultaneously by m-cc DCI in that cell is configured to be different. At this time, the cells (or cell combinations) belonging to the scheduled cell set share the BD count and DCI size count.

[0158] [4] A method to restrict the setting of legacy DCI in specific cells among m-cc DCI co-scheduled cells.

[0159] [4-1] Of N co-scheduled cells (e.g., cell #1 to cell #N) simultaneously scheduled by m-cc DCI (or corresponding to the entire set of cells schedulable by m-cc DCI), at least M (where M<=N) cells are restricted to not be configured with legacy DCI. In this case, the number of monitorings for m-cc DCI (i.e., BD count) is counted only for those M cells (or for a predetermined cell selected from the M cells). Also, in the process of keeping the DCI size below the maximum DCI size budget (for each cell), DCI size counting for m-cc DCI is also performed only for those M cells (or for a predetermined cell selected from the M cells).

[0160] [4-2] For the above [4-1], M is less than or equal to N. For example, M=1 or M=N.

[0161] [4-3] In the above [4-1] and [4-2], M=1 cells are determined / set as the scheduling cell, the cell serving as a reference for the CIF value set in the m-cc DCI, the cell with the lowest index among the co-scheduled cells simultaneously scheduled by the m-cc DCI, or the cell with the lowest index among all the scheduled cells, etc. Alternatively, M=1 cells are set by another RRC configuration, MAC-CE, DCI, etc.

[0162] [4-4] In the above [4-1] and [4-2], when M=1, the BD count and / or DCI size count for the m-cc DCI is performed for that one cell.

[0163] [4-5] In the above [4-1] and [4-2], if M>1, one cell disclosed in [4-3] is selected as a priority, and then M cells with consecutive indices from that cell are determined as cells that do not have legacy DCI configured. Alternatively, M cells are configured with a different RRC configuration, MAC-CE, DCI, etc.

[0164] [4-6] In the above [4-1] and [4-2], if M>1, the BD count and / or DCI size count for m-cc DCI may be distributed equally (or unequally) to M cells, or may be applied to only one predetermined cell. In this case, the predetermined cell may be configured by another RRC / MAC-CE / DCI, or may be one predetermined cell disclosed in [4-3] or [4-4].

[0165] [4-7] In the above-described method, "the conventional DCI is not configured" means that neither the fallback DCI format (e.g., DCI 0_0 or 1_0) nor the non-fallback DCI format (e.g., DCI 0_1, 1_1, 0_2, or 1_2) of the conventional DCI is configured. Alternatively, it means that only the non-fallback DCI format (in which cross-carrier scheduling is configured) is not configured. Alternatively, it means that at least one of the fallback and non-fallback DCI formats is not configured.

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

[0167] 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 type 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 whether the above-mentioned proposed method is applied (or information regarding the rules of the proposed method) can be notified by the base station to the terminal, or by the transmitting terminal to the receiving terminal via a predetermined signal (e.g., a physical layer signal or an upper layer signal).

[0168] Example

[0169] FIG. 4 is a flowchart illustrating a signal transmission and reception method according to an embodiment of the present invention.

[0170] Referring to FIG. 4, the base station transmits RRC parameters to the terminal (S501). The terminal configures one or more scheduled cell sets based on the received RRC parameters (S503). After that, the base station transmits DCI to the terminal, and the terminal receives the DCI from the base station (S505). When the terminal transmits multiple channels on all or some of the cells included in a predetermined scheduled cell set among the one or more configured scheduled cell sets based on the DCI, the base station receives this (S507). Alternatively, the terminal receives multiple channels from the base station on all or some of the cells included in a predetermined scheduled cell set among the one or more configured scheduled cell sets based on the DCI (S507).

[0171] In addition to the operations of FIG. 4, any one or more of the operations described by [1] to [4] may be performed.

[0172] For example, referring to [3-1], in step S503, a terminal in which one or more scheduled cell sets are configured based on RRC parameters recognizes that one of the configured scheduled cell sets is indicated by DCI. The DCI received by the terminal from the base station is DCI used to schedule multiple channels in multiple cells to include one channel per cell. If the multiple channels are PUSCHs, the DCI corresponds to DCI format 0_3, and if the channels are PDSCHs, the DCI corresponds to DCI format 1_3. Alternatively, the DCI received by the terminal from the base station is DCI used to schedule multiple channels in multiple cells to include one or more channels per cell. If the multiple channels are PUSCHs, the DCI corresponds to DCI format 0_X, and if the channels are PDSCHs, the DCI corresponds to DCI format 1_X. If X is a natural number from 0 to 3, the DCI is configured in a form that modifies the conventional DCI format. If X is a natural number greater than or equal to 4, the DCI is a newly defined DCI format.

[0173] The DCI includes information indicating a predetermined scheduled cell set among one or more scheduled cell sets configured by RRC parameters. Referring to [3-1], the information is included in a scheduled cell set indicator.

[0174] The DCI also includes information indicating all or some of the cells included in the designated predetermined scheduled cell set from which the multiple channels are transmitted or received. Referring to [3-1], this information is included in a scheduled cell indicator.

[0175] Further, referring to [3-2], a predetermined cell (or a reference cell) among cells included in a predetermined scheduled cell set is used as a reference for the BD count and DCI size count for DCI. Therefore, the number of blind decodings for the DCI is counted based on the predetermined cell among cells included in the scheduled cell set. A DCI size alignment process for the DCI is also performed based on the predetermined cell among cells included in the scheduled cell set. Using a predetermined cell as a reference for the number of BD counts means that when a maximum number of PDCCH candidates and a maximum number of non-overlapped CCEs the UE can monitor per slot are determined, the UE only considers the number of PDCCH candidates and non-overlapped CCEs of the predetermined cell among cells included in the scheduled cell set when calculating the maximum number. The same applies when the maximum number of PDCCH candidates and the maximum number of non-overlapped CCEs are defined per span or group of slots (group of X_s slots) rather than per slot.

[0176] [3-3], the same search space set is used for DCIs that schedule all or some of the cells that belong to the same scheduled cell set. Therefore, when the DCI and a second DCI different from the DCI indicate the same predetermined scheduled cell set, the same search space set is set for the DCI and the second DCI even if they indicate different combinations of cells included in the predetermined scheduled cell set.

[0177] In addition to the operations described in relation to Figure 4, any one or more of the operations described with reference to Figures 1 to 3 and / or the operations described in [1] to [4] may be further performed in combination.

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

[0179] 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 / connectivity between devices (e.g., 5G).

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

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

[0182] Referring to FIG. 5, a communication system 1 applicable to the present invention includes wireless devices, base stations, and a network. Here, the wireless devices refer to devices that communicate using wireless connection technologies (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, vehicles 100b-1 and 100b-2, an XR (eXtended Reality) device 100c, a handheld device 100d, a home appliance 100e, an IoT (Internet of Things) device 100f, and an AI server / device 400. For example, the vehicles include vehicles equipped with wireless communication capabilities, autonomous vehicles, vehicles capable of vehicle-to-vehicle communication, etc. Here, the vehicles include unmanned aerial vehicles (UAVs) (e.g., drones). XR devices include Augmented Reality (AR), Virtual Reality (VR), and 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. Mobile devices include smartphones, smart pads, wearable devices (e.g., smart watches, smart glasses), computers (e.g., laptops, 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.

[0183] The wireless devices 100a to 100f are connected to a network 300 via a base station 200. The wireless devices 100a to 100f are equipped with AI (Artificial Intelligence) technology, and 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, vehicles 100b-1 and 100b-2 can communicate directly (e.g., V2V (Vehicle to Vehicle) / V2X (Vehicle to Everything) communication). IoT devices (e.g., sensors) can also communicate directly with other IoT devices (e.g., sensors) or other wireless devices 100a to 100f.

[0184] Wireless communication / connections 150a, 150b, and 150c are performed between the wireless devices 100a to 100f and the base stations 200, and between the base stations 200. Here, the wireless communication / connections are performed using 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, Integrated Access Backhaul (IAB)) (e.g., 5G NR). Through the wireless communication / connections 150a, 150b, and 150c, the wireless devices and the base stations, and the base stations, can transmit / receive wireless signals to / from each other. For example, the wireless communication / connections 150a, 150b, and 150c can transmit / receive signals via various physical channels. To this end, according to 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.

[0185] Examples of wireless devices to which the present invention is applied

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

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

[0188] 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 first information / signals and then transmits a wireless signal including the first information / signals via the transceiver 106. The processor 102 also receives a wireless signal including second information / signals via the transceiver 106 and then stores information obtained from signal processing of the second information / signals 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 implementing 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.

[0189] 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 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 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 implementing 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.

[0190] The hardware elements of the wireless devices 100, 200 are described in more detail below. Without limitation, one or more protocol layers may be implemented by one or more processors 102, 202. For example, one or more processors 102, 202 may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, and 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 generate 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 and provide them to the one or more transceivers 106, 206. The one or more processors 102, 202 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.

[0191] The one or more processors 102, 202 may also be referred to as a controller, microcontroller, microprocessor, or microcomputer. The one or more processors 102, 202 may be implemented using hardware, firmware, software, or a combination thereof. For 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 embodied to include modules, procedures, functions, etc. 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 executed 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.

[0192] One or more memories 104, 204 may be coupled to one or more processors 102, 202 and may store various types 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.

[0193] One or more transceivers 106, 206 can transmit user data, control information, wireless signals / channels, etc., as referenced in the methods and / or flowcharts herein to one or more other devices. One or more transceivers 106, 206 can receive user data, control information, wireless signals / channels, etc., as referenced in the descriptions, functions, procedures, suggestions, methods and / or flowcharts herein from one or more other devices. For example, one or more transceivers 106, 206 can be coupled to one or more processors 102, 202 and can transmit and receive wireless signals. For example, one or more processors 102, 202 can 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 can control one or more transceivers 106, 206 to receive user data, control information, or wireless signals from one or more other devices. Furthermore, one or more transceivers 106, 206 are coupled to one or more antennas 108, 208, and 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 flowcharts disclosed herein via the one or more antennas 108, 208. In this specification, one or more antennas may refer to 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 by one or more processors 102, 202. The one or more transceivers 106, 206 convert the user data, control information, radio signals / channels, etc., processed by 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.

[0194] Examples of use of wireless devices to which this invention is applied

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

[0196] 7, wireless devices 100 and 200 correspond to the wireless devices 100 and 200 of FIG. 6 and are composed of various elements, components, units / parts, and / or modules. For example, the wireless devices 100 and 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 and 202 and / or one or more memories 104 and 204 in FIG. 6. For example, the transceiver 114 includes one or more transceivers 106 and 206 and / or one or more antennas 108 and 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 the electrical / mechanical operations of the wireless device based on the programs / codes / instructions / information stored in the memory unit 130. The control unit 120 also transmits the information stored in the memory unit 130 to an external device (e.g., another communication device) via the communication unit 110 via a wireless / wired interface, or stores information received from an external device (e.g., another communication device) via the communication unit 110 via a wireless / wired interface in the memory unit 130.

[0197] 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. Wireless devices may be embodied in the form of, but are 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 financial device), a security device, a climate / environment device, an AI server / device (FIG. 5, 400), a base station (FIG. 5, 200), a network node, etc. Wireless devices may be mobile or fixed depending on the use case / service.

[0198] In FIG. 7, the various elements, components, units / sections and / or modules within the wireless devices 100, 200 are all connected to each other by wired interfaces, or at least some are connected wirelessly by a communication section 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 the first unit (e.g., 130, 140) are connected wirelessly via the communication unit 110. Furthermore, 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 configured with a set of one or more processors. For example, the control unit 120 is configured with 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 configured with a RAM (Random Access Memory), a DRAM (Dynamic RAM), a ROM (Read Only Memory), a flash memory, a volatile memory, a non-volatile memory and / or a combination thereof.

[0199] Examples of vehicles or autonomous vehicles to which the present invention is applied include:

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

[0201] 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 part of the communication unit 110. Blocks 110 / 130 / 140a to 140d correspond to blocks 110 / 130 / 140 in FIG. 7, respectively.

[0202] 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, roadside 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 move on the ground. The driving unit 140a includes an engine, a motor, a powertrain, 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, an inclination sensor, a weight detection 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 implements technology for maintaining a lane while driving, technology for automatically adjusting speed such as adaptive cruise control, technology for automatically driving along a predetermined route, technology for automatically setting a route and driving when a destination is set, etc.

[0203] 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 driving plan based on the obtained data. The control unit 120 controls the driving unit 140a (e.g., adjusting speed / direction) so that the vehicle or autonomous vehicle 100 moves along the autonomous driving route according to the driving plan. The communication unit 110 aperiodically 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 driving plan based on the newly obtained data / information. The communication unit 110 transmits information regarding the vehicle position, autonomous driving route, driving plan, etc. to an external server. The external server can predict traffic information data using AI technology based on information collected from the vehicle or autonomous vehicle and provide the predicted traffic information data to the vehicle or autonomous vehicle.

[0204] 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 construed 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]

[0205] As mentioned above, the present invention can be applied to a variety of wireless communication systems.

Claims

1. A method for a terminal (UE) to transmit and receive signals in a wireless communication system, comprising: configuring one or more scheduled cell sets based on radio resource control (RRC) parameters; receiving downlink control information (DCI) used to schedule multiple channels in multiple cells, including one channel per cell, the DCI including information indicating a predetermined scheduled cell set among the one or more scheduled cell sets; and transmitting or receiving the plurality of channels on all or a part of the cells included in the predetermined scheduled cell set; Signal transmission and reception method.

2. The DCI further includes information indicating all or some of the cells included in the predetermined scheduled cell set from which the plurality of channels are transmitted or received. The signal transmitting and receiving method according to claim 1 .

3. The number of blind decodings for the DCI is counted based on a predetermined cell among the cells included in the scheduled cell set. The signal transmitting and receiving method according to claim 1 .

4. The DCI size alignment process for the DCI is performed based on a predetermined cell among the cells included in the scheduled cell set. The signal transmitting and receiving method according to claim 1 .

5. Even if the DCI and the second DCI indicate different combinations of cells among the cells included in the predetermined scheduled cell set, the DCI and the second DCI indicate the same predetermined scheduled cell set, and therefore the same search space set is configured for the DCI and the second DCI. The signal transmitting and receiving method according to claim 1 .

6. A terminal for transmitting and receiving signals in a wireless communication system, comprising: at least one transceiver; at least one processor; and 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 predetermined operations; The predetermined operation is configuring one or more scheduled cell sets based on radio resource control (RRC) parameters; receiving downlink control information (DCI) used to schedule multiple channels in multiple cells, including one channel per cell, the DCI including information indicating a predetermined scheduled cell set among the one or more scheduled cell sets; and transmitting or receiving the plurality of channels on all or a part of the cells included in the predetermined scheduled cell set; Terminal.

7. The DCI further includes information indicating all or some of the cells included in the predetermined scheduled cell set from which the plurality of channels are transmitted or received. The terminal according to claim 6.

8. The number of blind decodings for the DCI is counted based on a predetermined cell among the cells included in the scheduled cell set. The terminal according to claim 6.

9. The DCI size alignment process for the DCI is performed based on a predetermined cell among the cells included in the scheduled cell set. The terminal according to claim 6.

10. Even if the DCI and the second DCI indicate different combinations of cells among the cells included in the predetermined scheduled cell set, the DCI and the second DCI indicate the same predetermined scheduled cell set, and therefore the same search space set is configured for the DCI and the second DCI. The terminal according to claim 6.

11. 1. An apparatus for a terminal, comprising: at least one processor; and and at least one computer memory operatively connected to the at least one processor that, when executed, causes the at least one processor to perform operations, the operations including: configuring one or more scheduled cell sets based on radio resource control (RRC) parameters; receiving downlink control information (DCI) used to schedule multiple channels in multiple cells, including one channel per cell, the DCI including information indicating a predetermined scheduled cell set among the one or more scheduled cell sets; and transmitting or receiving the plurality of channels on all or a part of the cells included in the predetermined scheduled cell set; Device.

12. A computer-readable non-volatile storage medium containing at least one computer program that causes at least one processor to perform operations, said operations including: configuring one or more scheduled cell sets based on radio resource control (RRC) parameters; receiving downlink control information (DCI) used to schedule multiple channels in multiple cells, including one channel per cell, the DCI including information indicating a predetermined scheduled cell set among the one or more scheduled cell sets; and transmitting or receiving the plurality of channels on all or a part of the cells included in the predetermined scheduled cell set; Storage medium.

13. 1. A method for transmitting and receiving signals by a base station (BS) in a wireless communication system, comprising: transmitting radio resource control (RRC) parameters for configuring one or more scheduled cell sets; transmitting downlink control information (DCI) used to schedule multiple channels in multiple cells, including one channel per cell, the DCI including information indicating a predetermined scheduled cell set among the one or more scheduled cell sets; and transmitting or receiving the plurality of channels on all or a part of the cells included in the predetermined scheduled cell set; Signal transmission and reception method.

14. In a wireless communication system, a base station for transmitting and receiving signals, comprising: at least one transceiver; at least one processor; and 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 predetermined operations; The predetermined operation is configuring one or more scheduled cell sets based on radio resource control (RRC) parameters; receiving downlink control information (DCI) used to schedule multiple channels in multiple cells, including one channel per cell, the DCI including information indicating a predetermined scheduled cell set among the one or more scheduled cell sets; and transmitting or receiving the plurality of channels on all or a part of the cells included in the predetermined scheduled cell set; Base station.

Images