Method and apparatus for transmitting and receiving signal in wireless communication system

Abstract

The method and apparatus for transmitting and receiving a signal in a wireless communication system disclosed in the present application transmits and receives DCI for scheduling a plurality of channels in a plurality of cells such that each of the cells includes one of the channels. The DCI includes information indicating a specific set of scheduled cells among the one or more sets of scheduled cells.

Description

Technical Field

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

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

[0003] Technical issues

[0004] An object of the present disclosure is to provide a signal transmission and reception method and apparatus thereof for efficiently transmitting and receiving a control signal and a data signal in a wireless communication system.

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

[0006] Technical Solution

[0007] The present disclosure provides a method and apparatus for transmitting and receiving signals in a wireless communication system.

[0008] In one aspect of the present disclosure, a method for sending and receiving signals by a user equipment (UE) in a wireless communication system includes the following steps: configuring one or more scheduled cell sets based on radio resource control (RRC) parameters, receiving downlink control information (DCI) for scheduling multiple channels in multiple cells on a cell-by-cell basis, the DCI including information indicating a specific scheduled cell set among the one or more scheduled cell sets; and sending or receiving the multiple channels on all or part of the cells included in the specific scheduled cell set.

[0009] In another aspect of the present disclosure, a method for sending and receiving signals by a base station (BS) in a wireless communication system includes the following steps: sending radio resource control (RRC) parameters for configuring one or more scheduled cell sets; sending downlink control information (DCI) for scheduling multiple channels in multiple cells at one channel per cell, the DCI including information indicating a specific scheduled cell set among the one or more scheduled cell sets; and sending or receiving the multiple channels on all or part of the cells included in the specific scheduled cell set.

[0010] In another aspect of the present disclosure, a device, a processor, and a storage medium for executing a signal receiving method are provided. In addition, in another aspect of the present disclosure, a device, a processor, and a storage medium for executing a signal transmitting method are provided.

[0011] The apparatus may include an autonomous driving vehicle communicable with at least a UE, a network, and another autonomous driving vehicle other than the communication apparatus.

[0012] The above-mentioned aspects of the present disclosure are only some preferred embodiments of the present disclosure, and various embodiments reflecting the technical features of the present disclosure can be derived and understood by those skilled in the art from the following detailed description of the present disclosure.

[0013] Beneficial Effects

[0014] According to one embodiment of the present disclosure, when a control signal and a data signal are transmitted and received between communication devices, the signals can be transmitted and received more efficiently based on an operation different from that in the related art.

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

[0016] Figure 1 The radio frame structure is shown.

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

[0018] Figure 3 Figure 1 shows a self-contained time slot structure.

[0019] Figure 4 is a diagram illustrating a method of transmitting and receiving a signal according to an embodiment of the present disclosure.

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

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

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

[0023] 3GPP NR

[0024] -38.211: Physical channels and modulation

[0025] -38.212: Multiplexing and channel compilation

[0026] -38.213: Physical layer procedures for control

[0027] -38.214: Physical layer procedures for data

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

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

[0030] Figure 1 The radio frame structure for NR is shown.

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

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

[0033] [Table 1]

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

[0035] *N slot symb : The number of symbols in a time slot

[0036] *N frame，u slot : Number of time slots in a frame

[0037] *N subframe，u slot : Number of time slots in a subframe

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

[0039] [Table 2]

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

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

[0042] In NR, various parameter sets (or SCS) can be supported to support various 5th generation (5G) services. For example, for an SCS of 15kHz, wide areas in the traditional cellular band can be supported, while for an SCS of 30kHz or 60kHz, dense urban areas, lower latency, and wide carrier bandwidth can be supported. For an SCS of 60kHz or higher, bandwidths greater than 24.25kHz can be supported to overcome phase noise.

[0043] The NR frequency band may be defined by two types of frequency ranges FR1 and FR2. FR1 and FR2 may be configured as described in Table 3 below. FR2 may be millimeter wave (mmW).

[0044] [Table 3]

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

[0046] Figure 2 The resource grid during the duration of one time slot is shown.

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

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

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

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

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

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

[0053] DL physical channel / signal

[0054] (1)PDSCH

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

[0056] (2)PDCCH

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

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

[0059] [Table 4]

[0060]

[0061]

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

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

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

[0065] [Table 5]

[0066]

[0067]

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

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

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

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

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

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

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

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

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

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

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

[0079] Table 6 shows the PDCCH search space.

[0080] [Table 6]

[0081]

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

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

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

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

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

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

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

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

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

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

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

[0093] In addition, the following methods can be equally applied to the above-mentioned NR system (licensed band) or shared spectrum. Therefore, it is obvious that the terms, expressions, and structures in this document can be modified to be suitable for the system to implement the technical concept of the present disclosure in the corresponding system.

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

[0095] Table 7 can be understood as an explanation for supporting such DCI in Rel-18, which is used as one of the motivations for introducing DCI (PDCCH).

[0096] [Table 7]

[0097]

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

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

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

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

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

[0103] [Table 8]

[0104]

[0105]

[0106] [Table 9]

[0107]

[0108]

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

[0110] [Table 10]

[0111]

[0112]

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

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

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

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

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

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

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

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

[0121] [1-1] The K scheduled cells scheduled simultaneously with the m-cc DCI (or corresponding to the entire set of cells that can be scheduled with the m-cc DCI) are represented as {{cell #k}, K} = {cell #1, cell #2, ..., cell #K}. The entire set of cells that can be scheduled with the m-cc DCI is referred to as all scheduled cells. Each scheduled cell (e.g., cell #k) can be scheduled with the s-cc DCI or the m-cc DCI. In this case, the UE needs to perform monitoring (e.g., blind decoding) on ​​both the s-cc DCI and the m-cc DCI at the same time. The number of possible BDs for the s-cc DCI and the m-cc DCI for each scheduled cell can be set by RRC, etc. However, in order to reduce the monitoring burden on the UE, the maximum number of monitoring attempts (or BD count) for an individual scheduled cell for a specific time (e.g., 1 time slot) can be limited to no more than a specific value. Therefore, it may be necessary to readjust the number of BD counts for the m-cc DCI and / or s-cc DCI.

[0122] [1-2] The number of PCs that can monitor s-cc DCI for cell #k is represented by BD_single(k). The number of PCs that can monitor m-cc DCI for cell #k is represented by BD_multi(k). The maximum BD count set for cell #k is represented by BD_limit(k). Alternatively, in the proposed method discussed later, BD_single(k) can represent the BD count for s-cc DCI monitoring of cell #k. In addition, BD_multi(k) can represent the BD count for m-cc DCI monitoring of cell #k. PC refers to the number of PDCCH candidates configured per aggregation level (AL) for each cell.

[0123] [1-3] In the proposed method discussed later, BD_single(k) may represent the sum of the BD counts (or PC counts) for monitoring non-fallback DCI (e.g., DCI format 1_1 and / or 0_1) and fallback DCI (e.g., DCI format 1_0 and / or 0_0) among the legacy DCI. Alternatively, BD_single(k) may represent only the BD counts (or PC counts) for monitoring non-fallback DCI for the cell.

[0124] [1-4] beta_multi and / or beta_single may be set to satisfy the following equation for cell #k.

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

[0126] Here, beta_multi and beta_single refer to specific values ​​(non-negative real numbers, e.g., 1 or 0 or 0.5) that can be set or predefined by RRC, etc. They can ensure that when monitoring for s-cc DCI and monitoring for m-cc DCI are simultaneously performed for a specific scheduled cell #k, the total number of BD attempts for the cell remains less than or equal to a specific number (e.g., BD_limit(k)). In the above equation, a specific value (=K1) can be used instead of BD_limit(k), which is predefined for each cell.

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

[0128] Here, K1 may be set or predefined by RRC, etc. K1 may be a value different from BD_limit(k) (eg, greater than BD_limit(k)).

[0129] In the above proposed method, the monitoring count for the m-cc DCI of cell #k may be beta_multi*BD_multi(k), and the monitoring count for the s-cc DCI may be beta_single*BD_single(k).

[0130] [1-5] As an alternative to [1-4], for cell #k, beta_multi and / or beta_single may be set to satisfy the following equation.

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

[0132] Here, beta_multi and beta_single refer to specific values ​​(non-negative real numbers, for example, 1 or 0 or 0.5) that can be set or predefined by RRC, etc. Moreover, sum[] represents the sum of all co-scheduled cells scheduled simultaneously with the m-cc DCI. Alternatively, sum[] represents the sum of the entire set of cells that can be scheduled with the m-cc DCI. Depending on the elements in sum[], the sum of BD_multi(k), BD_single(k) or BD_limit(k) for each cell is derived. This ensures that when monitoring for s-cc DCI and monitoring for m-cc DCI are performed simultaneously for a specific scheduled cell #k, the total number of BD attempts for the cell remains less than or equal to a specific number (for example, sum[BD_limit(k)]). In the above equation, a specific value (=K1_sum) can be used instead of sum[BD_limit(k)] predefined for each cell.

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

[0134] Here, K1_sum may be set or predefined by RRC, etc. K1_sum may be a value different from sum[BD_limit(k)] (e.g., greater than sum[BD_limit(k)]). In the above-proposed method, the monitoring count for m-cc DCI of cell #k may be beta_multi*BD_multi(k). The monitoring count for s-cc DCI may be beta_single*BD_single(k).

[0135] Additionally, the method can be applied as follows:

[0136] - When the number of PDCCH candidates for m-cc DCI (or BD count) is set / determined for all scheduled cells, sum[BD_multi(k)] may be a "specific setting value (=BD_multi_all)". sum[BD_single(k)] and sum[BD_limit(k)] may refer to the sum of all scheduled cells.

[0137] - When the number of PDCCH candidates (or BD count) for m-cc DCI is set / determined per scheduled cell, sum[BD_multi(k)] may be the "value of BD_single(k) for the cell". sum[BD_single(k)] and sum[BD_limit(k)] may refer to values ​​set for the kth cell.

[0138] -sum[BD_multi(k)] may be "N times BD_single(k) (where N is the number of co-scheduled cells or all scheduled cells)", and the sum of sum[BD_single(k)] and sum[BD_limit(k)] may refer to the application value of the set of all scheduled cells or the combination of co-scheduled cells.

[0139] - When the number of PDCCH candidates (or BD count) for m-cc DCI is set / determined per combination of co-scheduled cells simultaneously scheduled with the same m-cc DCI, sum[BD_multi(k)] may be a "specific setting value (=BD_multi_comb)". The sum of sum[BD_single(k)] and sum[BD_limit(k)] may refer to an applied value for a combination of co-scheduled cells.

[0140] [1-6] As an alternative to [1-4], for cell #k, beta_multi and / or beta_single may be set to satisfy the following equation.

[0141] (Equation 1-6-1)BD_multi(k)<=beta_multi*BD_limit(k)

[0142] (Equation 1-6-2) BD_single(k)<=beta_single*BD_limit(k)

[0143] Here, beta_multi and beta_single refer to specific values ​​(non-negative real numbers, e.g., 1 or 0 or 0.5) that can be set or predefined by RRC or the like. This can ensure that when monitoring for s-cc DCI and monitoring for m-cc DCI are performed simultaneously for a specific scheduled cell #k, the total number of BD attempts for the cell remains less than or equal to a specific number (e.g., BD_limit(k)). In the above equation, a specific value (=K2) can be used instead of BD_limit(k), which is predefined for each cell.

[0144] (Equation 1-6-3)BD_multi(k)<=beta_multi*K2

[0145] (Equation 1-6-4)BD_single(k)<=beta_single*K2

[0146] Here, K2 may be set or predefined by RRC, etc. K2 may be a value different from BD_limit(k) (e.g., greater than BD_limit(k)). In the above proposed method, the monitoring count for m-cc DCI of cell #k may be BD_multi(k). The monitoring count for s-cc DCI may be BD_single(k).

[0147] [1-7] As an example of [1-4], [1-5], and [1-6], by setting beta_single to 1 (or 0) and the value of beta_multi in the range of 0 to 1, the monitoring count set for the m-cc DCI can be reduced so that it does not exceed the BD_limit of each scheduled cell. In this case, the reduction of the set monitoring count refers to a method in which the UE monitors a number of PDCCH candidates (e.g., beta_multi*BD_multi(k)) that is less than the number of PDCCH candidates set for cell #k for m-cc DCI monitoring (e.g., BD_multi(k)). In this case, the UE can be adjusted to prioritize monitoring PDCCH candidates with a relatively low index (or an index less than or equal to a specific value) for m-cc DCI, and skip (discard) monitoring specific PDCCH candidates with a relatively high index (or an index greater than a specific value).

[0148] [1-8] As another example of [1-4], [1-5], and [1-6], by setting beta_multi to 1 (or 0) and the value of beta_multi being in the range of 0 to 1, the monitoring count set for the s-cc DCI can be reduced so that it does not exceed the BD_limit of each scheduled cell. In this case, the reduction of the set monitoring count refers to a method in which the UE monitors a number of PDCCH candidates (e.g., beta_single*BD_single(k)) that is less than the number of PDCCH candidates set for cell #k for s-cc DCI monitoring (e.g., BD_single(k)). In this case, the UE can be adjusted to preferentially monitor PDCCH candidates with a relatively low index (or an index less than or equal to a specific value) for s-cc DCI, and skip (discard) monitoring of specific PDCCH candidates with a relatively high index (or an index greater than a specific value).

[0149] [1-9] [One of the following conditions may also be applied to [1-4], [1-5], and [1-6.]

[0150] (Equation 1-7-1)BD_multi(k)+BD_single(k)<=BD_limit(k)

[0151] (Equation 1-7-2)BD_multi(k)+BD_single(k)<=K3

[0152] (Equation 1-7-3) BD_multi(k)+BD_single(k)=1

[0153] (Equation 1-7-4) BD_multi(k)+BD_single(k)=K4

[0154] Here, K3 and K4 may be set or predefined through RRC or the like.

[0155] [1-10] In the above-mentioned proposed method, a cell-specific weight may be assigned to each scheduled cell for m-cc scheduling according to the number (or proportion) of the co-scheduled cell set including the cell. For example, when the combination of co-scheduled cells that can be scheduled with m-ccDCI is {cell #1, cell #2} or {cell #2, cell #3}, the setting value of BD_multi (or beta_multi) for cell #2 may be twice or half of the value set for cell #1 and / or cell #3.

[0156] [2] Cases where specific PDCCH candidates are not considered for monitoring

[0157] Under the following conditions, monitoring of PDCCH candidates for s-cc DCI may not be considered as monitoring.

[0158] Table 11 is part of the 3GPP TS 38.213 document.

[0159] [Table 11]

[0160]

[0161] Referring to Table 11, if the PDCCH candidate (=m_j) of the SS set (=s_j) of a specific cell (=n_CI) meets specific conditions for the same cell (=n_CI) (i.e., when SS / PC with the same CORESET CCE, DCI size and the same scrambling are configured), the PDCCH candidate (=m_j) is not considered for additional monitoring.

[0162] This operation can be similarly applied to PDCCH candidates for m-cc DCI. That is, when the following specific conditions are met, PDCCH candidates for m-cc DCI of the same set of co-scheduled (or schedulable) cell combinations may not be considered for additional monitoring.

[0163] The same set of co-scheduled (or schedulable) cell combinations may refer to the following items: when a combination of cells co-scheduled using the same m-cc DCI is defined as a co-scheduled cell combination, the same co-scheduled cell combination, or when the entire set of cells that can be scheduled using the same m-cc DCI is defined as a schedulable cell set, any co-scheduled cell combination belonging to the same schedulable cell combination.

[0164] In other words, when the following specific conditions are met, two or more PDCCH candidates of the same set of m-cc DCIs of a co-scheduled (or schedulable) cell combination can be regarded as being monitored once.

[0165] The specific condition may be a combination of one or more of the following:

[0166] -The scheduling cells of the two PDCCH candidates for m-cc scheduling are the same;

[0167] -The CORESET of the two PDCCH candidates is the same

[0168] - The two PDCCH candidates are SS sets configured in the same set of L (=AL) CCEs.

[0169] - The DCI size of the two PDCCH candidates is the same

[0170] - Use the same scrambling for both PDCCH candidates during DCI decoding

[0171] [3] Configure the maximum number of cells that can be scheduled at one time through m-cc DCI and configure the SS set for each group. method

[0172] Groups of co-schedulable cells that can be simultaneously scheduled via m-cc DCI may be pre-configured, an SS set may be configured for each group, and a BD count and a DCI size may be determined for each group.

[0173] [3-1] A group of cells that can be co-scheduled can be configured separately through RRC. In the present disclosure, a group of cells that can be co-scheduled can be represented as a set of scheduled cells or a combination of scheduled cells. The group index can be indicated by m-cc DCI. That is, the set of scheduled cells can be indicated by the DCI. In addition, the list of cells that are actually scheduled among the cells in the group can be indicated by the DCI. In other words, the cell that actually sends PUSCH or receives PDSCH among the cells belonging to the set of scheduled cells can be indicated by the DCI.

[0174] For example, the co-schedulable cell groups can be configured as group_1={cell #1, cell #2}, group_2={cell #3, cell #4}, group_3={cell #1, cell #2, cell #3}, etc. through RRC. One of the configured groups can be scheduled through m-cc DCI. If group_1 is scheduled through m-cc DCI, the m-cc DCI may include an indicator indicating group_1. In addition, the m-cc DCI may indicate a cell (or cell combination) that schedules PUSCH or PDSCH among the cells included in group_1. For example, when group_1 is indicated, the cell co-scheduled through m-cc DCI may be one of {cell #1}, {cell #2}, or {cell #1, cell #2}. When group_2 is indicated, the cell co-scheduled through m-cc DCI may be one of {cell #3}, {cell #4}, or {cell #3, cell #4}.

[0175] The name of the RRC parameter indicating the scheduled cell set may be, for example, MC-DCI-SetofCellsToAddModList. The RRC parameter may be a list of up to N (N<=4) configurations of cell sets for multi-cell PDSCH / PUSCH scheduling from the serving cell, where N may be reported as UE capability and up to 4 cell sets may be configured per PUCCH group. The cell set for multi-cell PDSCH / PUSCH scheduling may refer to a set of scheduled cells (or a set of scheduled cells) that schedule PDSCH / PUSCH through multi-cell PDSCH / PUSCH scheduling.

[0176] In addition, the RRC parameter indicating the scheduled cell set may be configured per scheduled cell and may be UE-specifically configured.

[0177] Table 12 shows the relationship between the bit field value of the indicator included in the DCI and the scheduled cell set. The indicator indicating the scheduled cell set may be referred to as a scheduled cell set indicator. The scheduled cell set indicator must indicate one of the groups indicated by the RRC parameter, so the number of bits may be determined based on the number of groups set by the RRC parameter. For example, when the number of cell sets set by the RRC parameter is N_set, the number of bits of the scheduled cell set indicator may be ceil(log2(N_set)). The cell used for actual channel reception or transmission among the cells included in the indicated scheduled cell set is referred to as a scheduled cell. The scheduled cell may be indicated by a scheduled cell indicator separate from the scheduled cell set indicator.

[0178] [Table 12]

[0179]

[0180]

[0181] [3-2] With respect to the above [3-1], when a specific cell (=ref_cell) is designated among cells belonging to a specific group, the DCI size count and / or BD count of the m-cc DCI for all or part of the cells in the scheduling group may be performed only for the ref_cell. For example, in the case where 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} are scheduled by m-cc DCI, the BD count and / or DCI size count may be applied to cell #1.

[0182] [3-3] With respect to [3-1] above, for DCIs of all or part of the cells in the same group, the same DCI size may be used. For example, for group_3 mentioned in [3-1], when only cell #1 (or cell #2 or cell #3) is scheduled, {cell #2, cell #3} is scheduled at the same time, and {cell #1, cell #2, cell #3} is scheduled at the same time through m-cc DCI, the same DCI size may be used. The same DCI size may be determined based on the case where the commonly scheduled cell is the largest (or the DCI size is the largest).

[0183] [3-4] With respect to [3-1] above, the same SS set can be used to schedule the m-cc DCI of all or part of the cells in the same group. Alternatively, some of the same configurations can be used even if the SS set indexes are different. For example, the same SS set (e.g., the same SS set index) can be configured for two m-cc DCIs of {cell #1} and {cell #2} that respectively schedule the same group. In this case, the same SS set configuration can be used. In another example, different SS sets (e.g., different SS set indexes) can be used to respectively schedule two m-cc DCIs of {cell #1} and {cell #2} that belong to the same group, but some configurations of the two SS sets can be shared. The configurations that can be shared may include the number of PCs per AL, configurations related to monitoring opportunities such as period / offset / duration, CIF values, and n_CI values.

[0184] [3-5] With respect to the above [3-1], for m-cc DCIs that schedule all or part of the cells belonging to the same group, the monitored BD count may be counted as 1. For example, when two m-cc PDCCHs for scheduling {cell #1} and {cell #2} belonging to the same group are monitored in the same time slot, the BDs of the two PDCCHs may be counted only once.

[0185] As an implementation method of the above-mentioned [3-1] to [3-5], when the entire set of scheduled cells (configured for a specific UE) that can be scheduled with m-cc DCI consists of 8 cells (#1 to #8), the m-cc DCI of the specific scheduling cell (#A) may have only a subset of {cell #1, cell #2} as scheduled cells. In addition, the m-cc DCI of another scheduling cell (#B) may have only a subset of {cell #3, cell #4, cell #5, cell #6, cell #7, cell #8} as scheduled cells. That is, when cell #A and cell #B (different from cell #A) are scheduling cells for m-cc DCI, different sets of scheduled cells that can be jointly scheduled can be configured for them. For example, for a scheduling cell belonging to FR1 and a scheduling cell belonging to FR2, different sets of scheduled cells that can be jointly scheduled by m-cc DCI can be configured. In this case, the cells (or cell combinations) belonging to the corresponding scheduled cell set can share the BD count and the DCI size count.

[0186] [4] A method for limiting the configuration of conventional DCI in specific cells among the co-scheduled cells of m-cc DCI

[0187] [4-1] It is possible to restrict the configuration of conventional DCI to at least M (where M<=N) cells among the N co-scheduled cells (e.g., cell #1 to cell #N) that are simultaneously scheduled by m-cc DCI (or corresponding to the entire set of cells that can be scheduled by m-cc DCI). In this case, the monitoring count (i.e., BD count) for m-cc DCI can be counted only for the M cells (or only for a specific cell selected from the M cells). In addition, in the process of complying with the maximum DCI size budget (for each cell), the DCI size count for m-cc DCI can be performed only for the M cells (or only for a specific cell selected from the M cells).

[0188] [4-2] With respect to the above [4-1], M may be less than or equal to N. For example, M may be equal to 1 or N.

[0189] [4-3] With respect to [4-1] and [4-2] above, M (= 1)) cells may be determined / set as a scheduling cell, a cell used as a reference for a CIF value set in an m-cc DCI, a cell with a lowest index among co-scheduled cells simultaneously scheduled by the m-cc DCI, or a cell with a lowest index among all scheduled cells. Alternatively, M (= 1) cells may be set by a separate RRC configuration, MAC-CE, or DCI.

[0190] [4-4] With respect to the above-mentioned [4-1] and [4-2], when M=1, BD counting and / or DCI size counting for m-cc DCI may be performed for one cell.

[0191] [4-5] With respect to [4-1] and [4-2] above, when M>1, one cell described in [4-3] may be selected first, and then M consecutive cells starting from this cell may be determined as cells that are not configured with legacy DCI. Alternatively, the M cells may be configured through separate RRC configurations, MAC-CE, or DCI.

[0192] [4-6] With respect to [4-1] and [4-2] above, when M>1, the BD count and / or DCI size count for the m-cc DCI may be equally (or unequally) divided among the M cells or applied only to one specific cell. In this case, one specific cell may be configured by a separate RRC / MAC-CE / DCI, or may be one specific cell mentioned in [4-3] or [4-4].

[0193] [4-7] In the above method, not configuring the legacy DCI may mean configuring any one of the fallback DCI format (e.g., DCI 0_0 or 1_0) and the non-fallback DCI format (e.g., DCI 0_1 or 1_1 or 0_2 or 1_2) among the legacy DCI. Alternatively, this may mean not configuring only the non-fallback DCI format (cross-carrier scheduling may be configured). Alternatively, this may mean not configuring at least one of the fallback DCI format and the non-fallback DCI format.

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

[0195] Obviously, each example in the examples of the proposed method may also be included as an implementation method of the present disclosure, and therefore each example may be considered as a proposed method. Although the above-mentioned proposed methods may be implemented independently, some of the proposed methods may be combined and implemented. In addition, it may be provided that information on whether to apply the proposed method (or information on rules related to the proposed method) is sent from the BS to the UE in a predefined signal (e.g., physical layer signaling or higher layer signaling).

[0196] Implementation Example

[0197] Figure 4 is a diagram illustrating a method for transmitting and receiving a signal according to an embodiment of the present disclosure.

[0198] Reference Figure 4 , the BS sends RRC parameters to the UE (S501). The UE configures one or more scheduled cell sets based on the received RRC parameters (S503). Subsequently, the BS sends DCI to the UE, and the UE receives the DCI from the BS (S505). When the UE sends multiple channels on all or part of the cells included in a specific scheduled cell set among one or more configured scheduled cell sets based on the DCI, the BS receives the multiple channels (S507). Alternatively, the UE may receive multiple channels from the BS on all or part of the cells included in a specific scheduled cell set among one or more configured scheduled cell sets based on the DCI (S507).

[0199] Apart from Figure 4 In addition to the operations, the method can be performed based on one or more of the operations described in sections [1] to [4].

[0200] For example, referring to [3-1], in operation S503, a UE having one or more scheduled cell sets configured based on RRC parameters identifies one of the scheduled cell sets that can be indicated by DCI. The DCI received by the UE from the BS may be a DCI for scheduling multiple channels in multiple cells so that each of the cells includes one channel. When the multiple channels are PUSCH, the DCI may correspond to DCI format 0_3. When the multiple channels are PDSCH, the DCI may correspond to DCI format 1_3. Alternatively, the DCI received by the UE from the BS may be used to schedule multiple channels in multiple cells so that each of the cells includes one or more channels. When the multiple channels are PUSCH, the DCI may correspond to DCI format 0_X. When the multiple channels are PDSCH, the DCI may correspond to DCI format 1_X. When X is a natural number from 0 to 3, the DCI is configured by modifying the existing DCI format. When X is a natural number greater than or equal to 4, the DCI may be a newly defined DCI format.

[0201] The DCI may include information indicating a specific scheduled cell set among one or more scheduled cell sets configured by RRC parameters. Referring to [3-1], this information may be included in a scheduled cell set indicator.

[0202] The DCI may also include information indicating all or part of cells to transmit or receive multiple channels among cells included in the indicated specific scheduled cell set. Referring to [3-1], this information may be included in the scheduled cell indicator.

[0203] Further, referring to [3-2], a specific cell (or reference cell) among the cells included in a specific scheduled cell set can be used as the basis for the BD count and DCI size count of the DCI. Therefore, the number of blind decodings for the DCI can be counted based on a specific cell among the cells included in the scheduled cell set. DCI size alignment for the DCI can be performed based on a specific cell among the cells included in the scheduled cell set. Using a specific cell as the basis for the BD count can mean that when determining the maximum number of non-overlapping CCEs and the maximum number of PDCCH candidates that the UE can monitor per time slot, the UE only considers the number of PDCCH candidates and the number of non-overlapping CCEs of the specific cell among the cells included in the scheduled cell set to calculate the maximum number. The same applies when the maximum number of PDCCH candidates and the maximum number of non-overlapping CCEs are defined per span or per X_s time slot group rather than per time slot.

[0204] Referring to [3-3], the same search space set can be used to schedule DCI of all or part of the cells belonging to the same scheduled cell set. Therefore, in the case where DCI and a second DCI different from the DCI indicate the same specific scheduled cell set, even when the DCI and the second DCI indicate different combinations of cells among the cells included in the specific scheduled cell set, the same search space set is configured for the DCI and the second DCI.

[0205] In addition to reference Figure 4 In addition to the operations described, you can also combine and further perform reference Figures 1 to 3 One or more of the described operations and / or the operations described in sections [1] to [4].

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

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

[0208] More specific examples will be described below with reference to the accompanying drawings.In the following drawings / descriptions, unless otherwise specified, the same reference numerals represent the same or corresponding hardware blocks, software blocks or functional blocks.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0223] Figure 7 Another example of a wireless device applicable to the present disclosure is shown. The wireless device can be based on the use case / service (refer to Figure 5 ) are implemented in various forms.

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

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

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

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

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

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

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

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

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

[0233] Industrial Applicability

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

Claims

1. A method for sending and receiving signals by a user equipment UE in a wireless communication system, the method comprising the following steps: configuring one or more scheduled cell sets based on a radio resource control (RRC) parameter; receiving downlink control information DCI for scheduling multiple channels in multiple cells at one channel per cell, the DCI including information indicating a specific scheduled cell set among the one or more scheduled cell sets; as well as The plurality of channels are transmitted or received on all or part of the cells included in the specific scheduled cell set.

2. The method according to claim 1, wherein: The DCI also includes information indicating the all or part of the cells used to transmit or receive the plurality of channels among the cells included in the specific scheduled cell set.

3. The method according to claim 1, wherein: The number of blind decodings for the DCI is counted based on a specific cell among the cells included in the scheduled cell set.

4. The method according to claim 1, wherein: The DCI size alignment for the DCI is performed based on a specific cell among the cells included in the scheduled cell set.

5. The method according to claim 1, wherein: Based on the DCI and the second DCI indicating the same specific scheduled cell set, even when the DCI and the second DCI indicate different combinations of cells among the cells included in the specific scheduled cell set, the same search space set is configured for the DCI and the second DCI.

6. A user equipment UE for sending and receiving signals in a wireless communication system, the UE comprising: at least one transceiver; at least one processor; as well as at least one memory operatively connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform specific operations, The specific operations include: configuring one or more scheduled cell sets based on a radio resource control (RRC) parameter; receiving downlink control information DCI for scheduling a plurality of channels in a plurality of cells at one channel per cell, the DCI including information indicating a specific scheduled cell set among the one or more scheduled cell sets; and The plurality of channels are transmitted or received on all or part of the cells included in the specific scheduled cell set.

7. The UE according to claim 6, wherein: The DCI also includes information indicating the all or part of the cells used to transmit or receive the plurality of channels among the cells included in the specific scheduled cell set.

8. The UE according to claim 6, wherein: The number of blind decodings for the DCI is counted based on a specific preconfigured cell among the cells included in the scheduled cell set.

9. The UE according to claim 6, wherein: DCI size alignment for the DCI is performed based on a specific preconfigured cell among the cells included in the scheduled cell set.

10. The UE according to claim 6, wherein: Based on the DCI and the second DCI indicating the same specific scheduled cell set, even when the DCI and the second DCI indicate different combinations of cells among the cells included in the specific scheduled cell set, the same search space set is configured for the DCI and the second DCI.

11. A device for a user equipment UE, the device comprising: at least one processor; as well as at least one computer memory operatively connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations comprising: configuring one or more scheduled cell sets based on a radio resource control (RRC) parameter; receiving downlink control information DCI for scheduling a plurality of channels in a plurality of cells at one channel per cell, the DCI including information indicating a specific scheduled cell set among the one or more scheduled cell sets; and The plurality of channels are transmitted or received on all or part of the cells included in the specific scheduled cell set.

12. A non-volatile computer-readable storage medium, the non-volatile computer-readable storage medium comprising at least one computer program, the at least one computer program causing at least one processor to perform operations comprising: configuring one or more scheduled cell sets based on a radio resource control (RRC) parameter; receiving downlink control information DCI for scheduling multiple channels in multiple cells at one channel per cell, the DCI including information indicating a specific scheduled cell set among the one or more scheduled cell sets; as well as The plurality of channels are transmitted or received on all or part of the cells included in the specific scheduled cell set.

13. A method for sending and receiving signals by a base station BS in a wireless communication system, the method comprising the following steps: Sending a radio resource control (RRC) parameter for configuring one or more scheduled cell sets; Sending downlink control information DCI for scheduling multiple channels in multiple cells at one channel per cell, the DCI including information indicating a specific scheduled cell set among the one or more scheduled cell sets; as well as The plurality of channels are transmitted or received on all or part of the cells included in the specific scheduled cell set.

14. A base station for sending and receiving signals in a wireless communication system, the base station comprising: at least one transceiver; at least one processor; as well as at least one memory operatively connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform specific operations, The specific operations include: configuring one or more scheduled cell sets based on a radio resource control (RRC) parameter; receiving downlink control information DCI for scheduling a plurality of channels in a plurality of cells at one channel per cell, the DCI including information indicating a specific scheduled cell set among the one or more scheduled cell sets; and The plurality of channels are transmitted or received on all or part of the cells included in the specific scheduled cell set.

Images