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

Abstract

According to at least one of various embodiments of the present invention, a terminal receives a DCI including at least one FDRA field and at least one MCS field via a PDCCH, and transmits a HARQ-ACK codebook based on the DCI, the DCI supporting multi-cell scheduling based on a plurality of cells configured in the terminal, and an index of the HARQ-ACK codebook is determined by a first MCS field for the first cell included in the DCI based on the first FDRA field for the first cell included in the DCI being set to a predetermined value that is not a valid FDRA value for the first cell.

Description

[Technical field]

[0001] The present invention relates to wireless communication systems, and more particularly to a method and apparatus for transmitting or receiving uplink / downlink radio signals in a wireless communication system. [Background technology]

[0002] Wireless communication systems have been widely deployed to provide various communication services such as voice and data. In general, wireless communication systems are multiple access systems that can support communication with multiple users by sharing available system resources (bandwidth, transmission power, etc.). Examples of multiple access systems include code division multiple access (CDMA) systems, frequency division multiple access (FDMA) systems, time division multiple access (TDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, etc. Summary of the Invention [Problem to be solved by the invention]

[0003] A technical problem to be solved is to provide a method and an apparatus for efficiently performing a process of transmitting and receiving a radio signal.

[0004] The technical problem to be achieved is not limited thereto, and other technical problems not mentioned will be clearly understood by those having ordinary skill in the art to which the present invention pertains from the following description. [Means for solving the problem]

[0005] According to an aspect of the present invention, a method for receiving a signal by a terminal in a wireless communication system includes receiving, through a physical downlink control channel (PDCCH), downlink control information (DCI) including at least one frequency domain resource allocation (FDRA) field and at least one modulation and coding scheme (MCS) field, via a physical downlink control channel (PDCCH); and transmitting a hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook based on the DCI. The DCI may support multi-cell scheduling based on a plurality of serving cells configured in the UE.Based on that a first FDRA field for a first cell included in the DCI is set to a specific value other than a valid FDRA value for the first cell, an index of the HARQ-ACK codebook may be determined through a first MCS field for the first cell included in the DCI.

[0006] The HARQ-ACK codebook is a Type-3 HARQ-ACK codebook associated with at least some of the plurality of cells.

[0007] The HARQ-ACK codebook index is associated with at least one of cell information and HARQ process ID information for a Type-3 HARQ-ACK codebook.

[0008] The terminal does not receive a physical downlink shared channel (PDSCH) from the first cell, among the plurality of cells, to which the predetermined value that is not the valid FDRA value is assigned.

[0009] The terminal receives a PDSCH based on the DCI in each of one or more cells excluding the first cell among the multiple cells.

[0010] Based on the DCI requesting the terminal to transmit a type-3 HARQ-ACK codebook, index information of the type-3 HARQ-ACK codebook is determined by the first MCS field for the first cell included in the DCI.

[0011] Based on the DCI requesting the terminal to transmit a type-3 HARQ-ACK codebook, the terminal does not receive a physical downlink shared channel (PDSCH) not only for the first cell but also for other cells among the multiple cells.

[0012] The first cell is the cell having the lowest or highest serving cell index among the plurality of cells.

[0013] The DCI includes a respective FDRA field and a respective MCS field for each of the co-scheduled cells.

[0014] According to another aspect of the present invention, there is provided a processor-readable recording medium having a program recorded thereon for carrying out the above-described method.

[0015] According to another aspect, there is provided a terminal for performing the above-mentioned method.

[0016] According to yet another aspect, there is provided an apparatus for controlling a terminal to perform the method described above.

[0017] According to another aspect, a method for transmitting a signal by a base station in a wireless communication system includes transmitting downlink control information (DCI) including at least one frequency domain resource allocation (FDRA) field and at least one modulation and coding scheme (MCS) field to a terminal via a physical downlink control channel (PDCCH); and receiving a hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook based on the DCI from the terminal. The DCI supports multi-cell scheduling based on a plurality of cells configured in the terminal. An index of the HARQ-ACK codebook is indicated by a first MCS field for the first cell included in the DCI based on a first FDRA field for the first cell being set to a predetermined value that is not a valid FDRA value for the first cell.

[0018] According to yet another aspect, there is provided a base station for performing the above-described method. Effect of the Invention

[0019] According to at least one of various embodiments, it is possible to efficiently transmit and receive radio signals in a wireless communication system.

[0020] The effects obtained by the present invention are not limited to those mentioned above, and other effects not mentioned will be clearly understood by those having ordinary skill in the art to which the present invention pertains from the following description. [Brief description of the drawings]

[0021] [Figure 1] 1 is a diagram illustrating physical channels used in a 3GPP (registered trademark) system, which is an example of a wireless communication system, and a general signal transmission method using these channels. [Diagram 2]FIG. 1 illustrates a structure of a radio frame. [Diagram 3] FIG. 2 illustrates a resource grid of slots. [Figure 4] A diagram showing an example of mapping physical channels within a slot. [Diagram 5] A diagram illustrating a PDCCH / PDSCH reception and ACK / NACK transmission process. [Figure 6] FIG. 1 illustrates a PUSCH (Physical Uplink Shared Channel) transmission process. [Figure 7] FIG. 2 illustrates an example of carrier merging. [Figure 8] FIG. 1 illustrates a wireless communication system that supports unlicensed bands. [Figure 9] FIG. 1 illustrates a method for occupying resources in an unlicensed spectrum. [Figure 10] FIG. 1 is a diagram for explaining enhanced type 3 codebook transmission according to one embodiment. [Figure 11] FIG. 13 is a diagram for explaining HARQ-ACK codebook retransmission according to one embodiment. [Figure 12] 1 is a diagram illustrating a method for a terminal to receive a signal according to one embodiment. [Figure 13] 1 is a diagram illustrating a method in which a base station transmits a signal according to one embodiment. [Figure 14] 1 is a diagram illustrating a communication system 1 and wireless devices applicable to the present invention. [Figure 15] 1 is a diagram illustrating a communication system 1 and wireless devices applicable to the present invention. [Figure 16] 1 is a diagram illustrating a communication system 1 and wireless devices applicable to the present invention. [Figure 17] 1 is a diagram illustrating a communication system 1 and wireless devices applicable to the present invention. [Figure 18] FIG. 2 is a diagram illustrating a DRX (Discontinuous Reception) operation applicable to the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0022] The following technologies can be used for 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 can be implemented by radio technologies such as Universal Terrestrial Radio Access (UTRA) and CDMA2000. TDMA can be implemented by radio technologies such as Global System for Mobile communications (GSM) / General Packet Radio Service (GPRS) / Enhanced Data Rates for GSM Evolution (EDGE). OFDMA can be implemented by radio technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, Evolved UTRA (E-UTRA), etc. UTRA is part of the Universal Mobile Telecommunications System (UMTS). 3GPP (3rd Generation Partnership Project) LTE (long term evolution) is part of E-UMTS (Evolved UMTS) that uses E-UTRA, and LTE-A is an evolution of 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is an evolution of 3GPP LTE / LTE-A.

[0023] As more communication devices require larger communication capacity, the need for improved mobile broadband (eMBB) communication compared to existing radio access technology (RAT) is emerging. In addition, large-scale MTC (massive machine type communications), which connects multiple devices and objects to provide various services anytime and anywhere, is one of the important issues to be considered in next-generation communications. In addition, URLLC (Ultra-Reliable and Low Latency Communication) considering reliability and latency-sensitive services / UEs is being discussed. Thus, the introduction of next-generation RATs considering eMBB (enhanced mobile broadband communication), large-scale MTC, URLLC (Ultra-Reliable and Low Latency Communication), etc. is being discussed, and for convenience, the relevant technology is referred to as NR (New radio or New RAT) in this specification.

[0024] For clarity of explanation, 3GPP NR will be mainly described, but the technical idea of ​​the present invention is not limited thereto.

[0025] In this specification, the term "setting" may be replaced with the term "configure / configuration", and the two terms may be used interchangeably. Conditional expressions (e.g., "if", "in a case", or "when") may be replaced with expressions such as "based on that" or "in a state / status". The operation or SW / HW configuration of a terminal / base station due to the satisfaction of the relevant condition may be inferred / understood. In addition, in signal transmission / reception between wireless communication devices (e.g., base station, terminal), if the process of the receiving (or transmitting) side can be inferred / understood from the process of the transmitting (or receiving) side, the explanation may be omitted. For example, the signal determination / generation / encoding / transmission of the transmitting side can be understood as the signal monitoring reception / decoding / determination of the receiving side. In addition, an expression that a terminal performs (or does not perform) a specific operation may also be interpreted as the base station operating while expecting / assuming (or expecting / assuming not to perform) the specific operation of the terminal. The expression that the base station performs (or does not perform) a specific operation can also be interpreted as the terminal expecting / assuming (or expecting / assuming not to perform) the execution of a specific operation of the base station. In addition, in the following description, the divisions and indexes of each section, embodiment, example, option, method, solution, etc. are for convenience of explanation and should not be interpreted as meaning that each necessarily constitutes an independent invention or that each necessarily must be implemented individually. In addition, in describing each section, embodiment, example, option, method, solution, etc., unless there is an explicitly conflicting / opposing technology, it is inferred / interpreted that at least some of them may be combined and implemented together, or at least some may be omitted and implemented.

[0026] In a wireless communication system, a terminal receives information from a base station through a downlink (DL), and transmits information to the base station through an uplink (UL). Information transmitted and received between the base station and the terminal includes data and various control information, and various physical channels exist depending on the type / purpose of the information transmitted and received.

[0027] FIG. 1 is a diagram illustrating physical channels used in a 3GPP NR system and a typical signal transmission method using these channels.

[0028] A terminal that has been turned on in a power-off state or that has newly entered a cell performs an initial cell search operation such as establishing synchronization with a base station in step S101. To this end, the terminal receives a synchronization signal block (SSB) from the base station. The SSB includes a primary synchronization signal (PSS), a secondary synchronization signal (SSS) and a physical broadcast channel (PBCH). The terminal establishes synchronization with the base station based on the PSS / SSS and obtains information such as a cell identity (cell ID). The terminal also obtains broadcast information within the cell based on the PBCH. In addition, the terminal can receive a downlink reference signal (DL RS) during the initial cell search stage to check the state of the downlink channel.

[0029] After completing the initial cell search, in step S102, the terminal receives a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) based on information of the physical downlink control channel to obtain more specific system information.

[0030] Thereafter, the terminal performs a random access procedure such as steps S103 to S106 to complete connection to the base station. To this end, the terminal transmits a preamble through a physical random access channel (PRACH) (S103) and receives a response message to the preamble through a physical downlink control channel and a corresponding physical downlink shared channel (S104). In the case of contention based random access, the terminal performs a contention resolution procedure such as transmitting a further physical random access channel (S105) and receiving a physical downlink control channel and a corresponding physical downlink shared channel (S106).

[0031] After performing this procedure, the terminal then receives a physical downlink control channel / physical downlink shared channel (S107) and transmits a physical uplink shared channel (Physical Uplink Shared Channel, PUSCH) / physical uplink control channel (Physical Uplink Control Channel, PUCCH) as a general uplink / downlink signal transmission procedure (S108). The control information transmitted by the terminal to the base station is collectively referred to as uplink control information (UCI). UCI includes HARQ ACK / NACK (Hybrid Automatic Repeat and reQuest Acknowledgement / Negative-ACK), SR (Scheduling Request), CSI (Channel State Information), etc. CSI includes CQI (Channel Quality Indicator), PMI (Precoding Matrix Indicator), RI (Rank Indication), etc. UCI is generally transmitted via PUCCH, but when control information and traffic data need to be transmitted simultaneously, it is transmitted via PUSCH. In addition, UCI can be transmitted aperiodically via PUSCH upon request / instruction from the network.

[0032] Meanwhile, the voluntary access procedure (RACH procedure) is not limited to the one for initial network access (e.g., S103 to S106) and can be used for various purposes. For example, the voluntary access procedure can be used for any of the RRC connection re-establishment procedure, handover, UE-triggered UL data transmission, transition from RRC_INACTIVE, SCell time alignment, system information request and beam failure recovery, and UL resource request, but is not limited thereto. The UE can obtain UL synchronization and / or UL transmission resources through the voluntary access procedure.

[0033] FIG. 2 illustrates the structure of a radio frame. 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 (HF). A half-frame is defined as five 1 ms subframes (SF). A subframe is divided into one or more slots, and the number of slots in a subframe depends on the subcarrier spacing (SCS). Each slot contains 12 or 14 OFDM(A) symbols depending on the cyclic prefix (CP). If a general CP is used, each slot contains 14 symbols. If an extended CP is used, each slot contains 12 symbols.

[0034] Table 1 illustrates that 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 a general CP is used.

[0035] [Table 1]

[0036] *N slot symb :Number of symbols in the slot

[0037] *N frame,u slot : Number of slots in the frame

[0038] *N subframe,u slot : Number of slots in a subframe

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

[0040] [Table 2]

[0041] The frame structure is exemplary only, and the number of subframes, slots, and symbols within a frame can vary.

[0042] In the NR system, OFDM numerology (e.g., SCS) can be set to be different between multiple cells merged into one terminal. Accordingly, the (absolute time) duration of time resources (e.g., SF, slot, or TTI) (for convenience, commonly referred to as TU (Time Unit)) consisting of the same number of symbols can be set to be different between the merged cells. Here, the symbols include OFDM symbols (or CP-OFDM symbols) and SC-FDMA symbols (or Discrete Fourier Transform-spread-OFDM, DFT-s-OFDM symbols).

[0043] FIG. 3 is a diagram illustrating a resource grid of a slot. A slot includes a number of symbols in the time domain. For example, in the case of a general CP, one slot includes 14 symbols, while in the case of an extended CP, one slot includes 12 symbols. A carrier includes a number of subcarriers in the frequency domain. A resource block (RB) is defined as a number of (e.g., 12) consecutive subcarriers in the frequency domain. A BWP is defined as a number of consecutive physical RBs (PRBs) in the frequency domain and can correspond to one numerology (e.g., SCS, CP length, etc.). A carrier includes up to N (e.g., 5) BWPs. Data communication is performed in an activated BWP, and only one BWP is activated for one terminal. In the resource grid, each element is called a resource element (RE), and one complex symbol can be mapped to it.

[0044] Figure 4 is a diagram showing an example of mapping physical channels within a slot. PDCCH is transmitted in the DL control region, and PDSCH is transmitted in the DL data region. PUCCH is transmitted in the UL control region, and PUSCH is transmitted in the UL data region. GP provides a time gap when the base station and the terminal switch from a transmission mode to a reception mode or from a reception mode to a transmission mode. Some symbols at the time of switching from DL to UL within a subframe can be set as GP.

[0045] Each physical channel is described in more detail below.

[0046] 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 (downlink shared channel), resource allocation information for the UL-SCH (uplink shared channel), paging information for the PCH (paging channel), system information on the DL-SCH, resource allocation information for higher layer control messages such as voluntary access responses transmitted on the PDSCH, transmission power control commands, activation / deactivation of configured scheduling (CS), etc. The 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 terminal identifier (e.g., cell-RNTI, C-RNTI). If the PDCCH is for paging, the CRC is masked to a P-RNTI (Paging-RNTI). If the PDCCH is for system information (e.g., System Information Block, SIB), the CRC is masked with a System Information RNTI (SI-RNTI). If the PDCCH is for an unsolicited access response, the CRC is masked with a Random Access-RNTI (RA-RNTI).

[0047] The PDCCH is composed of 1, 2, 4, 8, or 16 CCEs (Control Channel Elements) depending on the AL (Aggregation Level). A CCE is a logical allocation unit used to provide a PDCCH with a predetermined code rate according to the radio channel condition. A CCE is composed of 6 REGs (Resource Element Groups). A REG is defined by one OFDM symbol and one (P)RB. The PDCCH is transmitted by a CORESET (Control Resource Set). A CORESET is defined by a set of REGs having a given neurology (e.g., SCS, CP length, etc.). Multiple CORESETs for one UE can be overlapped in the time / frequency domain. A CORESET is set by system information (e.g., Master Information Block, MIB) or UE-specific higher layer (e.g., Radio Resource Control, RRC, layer) signaling. Specifically, the number of RBs and the number of OFDM symbols (maximum 3) constituting a CORESET are set by higher layer signaling.

[0048] For PDCCH reception / detection, the terminal monitors PDCCH candidates. PDCCH candidates indicate the CCEs that the terminal monitors for PDCCH detection. Each PDCCH candidate is defined by 1, 2, 4, 8, or 16 CCEs depending on the AL. Monitoring includes (blind) decoding the PDCCH candidates. The set of PDCCH candidates that the terminal monitors is defined as a PDCCH search space (SS). The search space includes a common search space (CSS) or a UE-specific search space (USS). The terminal can obtain DCI by monitoring PDCCH candidates in one or more search spaces configured by MIB or higher layer signaling. Each CORESET is associated with one or more search spaces, and each search space is associated with one COREST. The search space is defined based on the following parameters:

[0049] - controlResourceSetId: Indicates the CORESET associated with the search space.

[0050] - monitoringSlotPeriodicityAndOffset: indicates the PDCCH monitoring period (in slots) and the PDCCH monitoring period offset (in slots).

[0051] - monitoringSymbolsWithinSlot: indicates the PDCCH monitoring symbols within the slot (e.g. indicates the first symbol of CORESET).

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

[0053] *An opportunity (e.g., time / frequency resource) for monitoring a PDCCH candidate is defined as a PDCCH (monitoring) opportunity. One or more PDCCH (monitoring) opportunities are configured within a slot.

[0054] Table 3 illustrates the characteristics of each search space type.

[0055] [Table 3]

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

[0057] [Table 4]

[0058] 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. DCI format 0_0 / 0_1 is called UL grant DCI or UL scheduling information, and DCI format 1_0 / 1_1 is called DL grant DCI or DL ​​scheduling information. DCI format 2_0 is used to deliver dynamic slot format information (e.g., dynamic SFI) to a terminal, and DCI format 2_1 is used to deliver downlink pre-Emption information to a terminal. DCI format 2_0 and / or DCI format 2_1 are transmitted to terminals in a corresponding group via a group common PDCCH, which is a PDCCH transmitted to terminals defined in one group.

[0059] DCI format 0_0 and DCI format 1_0 are called fallback DCI formats, and DCI format 0_1 ​​and DCI format 1_1 are called non-fallback DCI formats. The fallback DCI format maintains the same DCI size / field configuration regardless of the terminal settings. On the other hand, the non-fallback DCI format has a different DCI size / field configuration depending on the terminal settings.

[0060] PDSCH carries downlink data (e.g. DL-SCH transport block, DL-SCH TB) and uses modulation methods such as QPSK (Quadrature Phase Shift Keying), 16QAM (Quadrature Amplitude Modulation), 64QAM, and 256QAM. The TB is encoded to generate a codeword. PDSCH carries up to two codewords. Scrambling and modulation mapping are performed for each codeword, and the modulation symbols generated from each codeword are mapped to one or more layers. Each layer is mapped to resources together with DMRS (Demodulation Reference Signal) to generate an OFDM symbol signal, which is then transmitted by the corresponding antenna port.

[0061] The PUCCH carries Uplink Control Information (UCI), which includes:

[0062] - SR (Scheduling Request): Information used to request UL-SCH resources.

[0063] - HARQ-ACK: A response to a downlink data packet (e.g., a codeword) on the PDSCH. It indicates whether the downlink data packet is successfully received or not. One HARQ-ACK bit is sent as a response to a single codeword, and two HARQ-ACK bits are sent as a response to two codewords. HARQ-ACK responses include positive ACK (simply, ACK), negative ACK (hereinafter, NACK), DTX (Discontinuous Transmission), or NACK / DTX. Here, the term HARQ-ACK is used interchangeably with HARQ ACK / NACK and ACK / NACK.

[0064] CSI (Channel State Information): Feedback information for a downlink channel. Multiple Input Multiple Output (MIMO)-related feedback information includes a Rank Indicator (RI) and a Precoding Matrix Indicator (PMI).

[0065] Table 5 shows an example of a PUCCH format. According to the PUCCH transmission length, it can be divided into Short PUCCH (formats 0 and 2) and Long PUCCH (formats 1, 3 and 4).

[0066] [Table 5]

[0067] PUCCH format 0 carries UCI with a maximum size of 2 bits and is mapped and transmitted based on a sequence. Specifically, the terminal transmits one of a plurality of sequences via a PUCCH with PUCCH format 0 to transmit a specific UCI to the base station. The terminal transmits a PUCCH with PUCCH format 0 within a PUCCH resource for a corresponding SR setting only when transmitting a positive SR.

[0068] PUCCH format 1 carries UCI with a maximum size of 2 bits, and the modulation symbols are spread by an orthogonal cover code (OCC) in the time domain (set differently depending on whether frequency hopping is used or not). DMRS is transmitted in symbols where no modulation symbols are transmitted (i.e., transmitted using TDM (Time Division Multiplexing)).

[0069] PUCCH format 2 carries UCI with a bit size larger than 2 bits, and modulation symbols are transmitted after frequency division multiplexing (FDM) with DMRS. DM-RS is located at symbol indexes #1, #4, #7, and #10 in a 1 / 3 density resource block. A Pseudo Noise (PN) sequence is used for the DM_RS sequence. Frequency hopping can be activated for the 2-symbol PUCCH format 2.

[0070] In PUCCH format 3, terminal multiplexing is not performed within the same physical resource block, and UCI with a bit size larger than 2 bits is carried. That is, the PUCCH resource of PUCCH format 3 does not include an orthogonal cover code. The modulation symbol is transmitted after being subjected to TDM (Time Division Multiplexing) with DMRS.

[0071] PUCCH format 4 supports multiplexing of up to four terminals in the same physical resource block and carries UCI with a bit size larger than 2 bits. That is, the PUCCH resource of PUCCH format 3 includes an orthogonal cover code. Modulation symbols are transmitted after being time division multiplexed (TDM) with DMRS.

[0072] The PUSCH carries uplink data (e.g., UL-SCH transport block, UL-SCH TB) and / or uplink control information (UCI) and is transmitted based on a cyclic prefix-orthogonal frequency division multiplexing (CP-OFDM) waveform or a discrete Fourier transform-spread-orthogonal frequency division multiplexing (DFT-s-OFDM) waveform. When the PUSCH is transmitted based on the DFT-s-OFDM waveform, the terminal applies transform precoding to transmit the PUSCH. As an example, when transform precoding is not possible (e.g., transform precoding is disabled), the terminal transmits the PUSCH based on the CP-OFDM waveform, and when transform precoding is possible (e.g., transform precoding is enabled), the terminal transmits the PUSCH based on the CP-OFDM waveform or the DFT-s-OFDM waveform. PUSCH transmissions may be dynamically scheduled by UL grants in the DCI or semi-statically scheduled (configured grant) based on higher layer (e.g., RRC) signaling (and / or Layer 1 (L1) signaling (e.g., PDCCH)). PUSCH transmissions may be codebook-based or non-codebook-based.

[0073] Figure 5 illustrates a process of receiving PDCCH / PDSCH and transmitting ACK / NACK. Referring to Figure 5, a terminal detects a PDCCH in slot #n. Here, the PDCCH includes downlink scheduling information (e.g., DCI format 1_0, 1_1), and the PDCCH indicates DL allocation-to-PDSCH offset (K0) and PDSCH-HARQ-ACK report offset (K1). For example, DCI formats 1_0, 1_1 include the following information:

[0074] - Frequency domain resource assignment: Indicates the RB set assigned to the PDSCH.

[0075] - Time domain resource assignment: Indicates K0 (e.g. slot offset), the starting position of the PDSCH within slot #n+K0 (e.g. OFDM symbol index) and the length of the PDSCH (e.g. number of OFDM symbols).

[0076] - PDSCH-to-HARQ_feedback timing indicator: Indicates K1.

[0077] - HARQ process number (4 bits): Indicates the HARQ process ID (Identity) for data (e.g., PDSCH, TB).

[0078] Thereafter, the terminal receives the PDSCH from slot #(n+K0) according to the scheduling information of slot #n, and then transmits UCI via PUCCH in slot #(n1+K1) when the reception of the PDSCH is completed in slot #n1 (where n+K0≦n1). Here, the UCI includes a HARQ-ACK response to the PDSCH. For convenience, in FIG. 5, it is assumed that the SCS for the PDSCH and the SCS for the PUCCH are the same and that slot #n1=slot #n+K0, but the present invention is not limited thereto. If the SCSs are different, K1 is indicated / interpreted based on the SCS of the PUCCH.

[0079] If the PDSCH is configured to transmit up to 1 TB, the HARQ-ACK response consists of 1 bit. If the PDSCH is configured to transmit up to 2 TB, the HARQ-ACK response consists of 2 bits if spatial bundling is not configured and 1 bit if spatial bundling is configured. If the transmission time of the HARQ-ACK for multiple PDSCHs is specified as slot #(n+K1), the UCI transmitted in slot #(n+K1) includes the HARQ-ACK response for multiple PDSCHs.

[0080] Whether or not the UE performs spatial bundling for the HARQ-ACK response is configured for each cell group (e.g., RRC / higher layer signaling). As an example, spatial bundling is configured separately for each of the HARQ-ACK response transmitted via the PUCCH and / or the HARQ-ACK response transmitted via the PUSCH.

[0081] Spatial bundling is supported when the maximum number of TBs (or codewords) that can be received at one time (or scheduled by one DCI) in a corresponding serving cell is two (or more than two) (for example, when the upper layer parameter maxNrofCodeWordsScheduledByDCI corresponds to 2-TB). Meanwhile, more than four layers are used for 2-TB transmission, and up to four layers are used for 1-TB transmission. As a result, when spatial bundling is configured in a corresponding cell group, spatial bundling is performed on serving cells in the corresponding cell group that can schedule more than four layers. A terminal that wishes to transmit a HARQ-ACK response through spatial bundling on a corresponding serving cell can generate a HARQ-ACK response by performing a bit-wise logical AND operation on A / N bits for multiple TBs.

[0082] For example, assuming that a terminal receives DCI scheduling 2-TB and receives 2-TB via PDSCH based on the DCI, a terminal performing spatial bundling can generate a single A / N bit by logically ANDing the first A / N bit for the first TB and the second A / N bit for the second TB. As a result, if both the first TB and the second TB are ACK, the terminal reports an ACK bit value to the base station, and if both TBs are NACK, the terminal reports a NACK bit value to the base station.

[0083] For example, if only 1-TB is actually scheduled on a serving cell that is configured to receive 2-TB, the terminal can generate a single A / N bit by logically ANDing the A / N bit for the 1-TB with a bit value of 1. As a result, the terminal reports the A / N bit for the 1-TB to the base station as is.

[0084] A base station / terminal has multiple parallel DL HARQ processes for DL ​​transmission. Multiple parallel HARQ processes allow DL transmission to be performed continuously while waiting for HARQ feedback for successful or unsuccessful reception of previous DL transmission. Each HARQ process is associated with a HARQ buffer in the Medium Access Control (MAC) layer. Each DL HARQ process manages state variables related to the number of transmissions of MAC Physical Data Blocks (PDUs) in the buffer, HARQ feedback for MAC PDUs in the buffer, current redundancy version, etc. Each HARQ process is distinguished by a HARQ process ID.

[0085] Meanwhile, the HARQ-ACK codebook is broadly defined into three codebook types, such as Type-1, Type-2, and Type-3, according to the configuration method of the HARQ-ACK bit (payload). In the case of the Type-1 codebook, the HARQ-ACK payload is configured by combining a set of candidate HARQ-ACK timings (K1) and a set of candidate PDSCH occasions (SLIV) (set for each cell) (e.g., a codebook of semi-statically fixed size based on RRC signaling). In the case of the Type-2 codebook, the size of the codebook is dynamically changed according to the number of PDSCHs actually scheduled or the number of corresponding resource allocations (e.g., downlink assignment index (DAI)). In the case of the Type-3 codebook, the HARQ-ACK payload is configured by mapping the HARQ-ACK bit corresponding to each HARQ process number (HPN) according to the maximum number of HARQ processes (set for each cell) (e.g., one-shot A / N reporting). In recent NR standards, an Enhanced Type-3 codebook has been added as one of the Type-3 codebooks. In order to reduce signaling overhead, the Enhanced Type-3 codebook is a method for reporting HARQ-ACK bits for a subset of all cells designated by the base station at once, rather than a method for reporting HARQ-ACK bits for all cells at once. A subset of cells associated with the Enhanced Type-3 codebook is configured in the terminal by higher layer signaling of the Enhanced Type-3 codebook index, and then one of the subsets (e.g., Enhanced Type-3 codebook index) configured in the terminal is indicated by DCI that triggers the Enhanced Type-3 codebook. The terminal can report HARQ-ACK for cells belonging to the indicated subset.Meanwhile, according to the setting of the Enhanced Type-3 codebook index, not only the Enhanced Type-3 codebook can be configured at the per cell level, but also the Enhanced Type-3 codebook can be configured at the per HARQ process level. For example, the Enhanced Type-3 codebook index may be set on a per HARQ process basis to support reporting the Type-3 codebook for some of the HARQ processes of the cell.

[0086] In the case of a Type-1 codebook, specifically, a set of multiple (e.g., N) candidate K1 values ​​is set (for each cell), and for each K1 value, all combinations of SLIVs that can be transmitted (or scheduled to be transmitted) in DL slots previous to the A / N transmission slot of K1 slots are calculated, and an A / N sub-payload corresponding to that DL slot (including determining the position / sequence of the A / N bits corresponding to each SLIV that can be transmitted in that slot) is constructed (this is defined as "SLIV pruning"), and this A / N sub-payload is concatenated for the N K1 values ​​to construct the entire A / N codebook, and at this time, the set of (N) DL slots corresponding to each K1 value is defined as a bundling window corresponding to the A / N transmission slot.

[0087] In the case of the Type-2 HARQ-ACK codebook, a codebook for transmitting HARQ-ACK information to the same PUCCH / PUSCH is defined based on a counter DAI (downlink assignment indicator) (C-DAI) and a total DAI (T-DAI) value indicated in an actually transmitted PDCCH. That is, the codebook is configured based on PDCCH information actually transmitted to the terminal. If the terminal fails to detect a specific PDCCH, it transmits a NACK to the bit corresponding to the PDCCH among bits defined in the codebook. In this case, the terminal can recognize whether or not the PDCCH detection has failed based on the C-DAI and T-DAI values. The C-DAI is a cumulative number of {serving cell index, PDCCH monitoring occasion}-pairs for which PDSCH reception is provided, including the current serving cell and the current PDCCH monitoring occasion. First, for multiple PDSCH receptions for the same {serving cell index, PDCCH monitoring opportunity} pair, the PDSCH that starts receiving first is counted first (assigned a lower C-DAI value). Next, if there are multiple pairs with the same PDCCH monitoring opportunity index among different {serving cell index, PDCCH monitoring opportunity} pairs, the pair with the lower serving cell index is counted first. Next, if there are multiple pairs with the same serving cell index among different {serving cell index, PDCCH monitoring opportunity} pairs, the PDCCH monitoring opportunity with the lower index is counted first.

[0088] In the case of a Type-3 codebook, one of the following modes is set by the BS to the UE: Mode 1, which feeds back NDI corresponding to HARQ-ACK, and Mode 2, which feeds back only HARQ-ACK without NDI. When set to Mode 1, the UE operates to feed back NDI (indicated by DCI) corresponding to HARQ-ACK for PDSCH reception of each HARQ Process Number (HPN). On the other hand, when set to Mode 2, the UE feeds back only HARQ-ACK for PDSCH reception of each HPN.

[0089] 6 illustrates a PUSCH transmission process. Referring to FIG. 6, a UE detects a PDCCH in slot #n. Here, the PDCCH includes uplink scheduling information (e.g., DCI format 0_0, 0_1). DCI format 0_0, 0_1 includes the following information:

[0090] - Frequency domain resource assignment: Indicates the RB set assigned to the PUSCH.

[0091] - Time domain resource assignment: indicates the slot offset K2, the starting position (e.g., symbol index) and length (e.g., number of OFDM symbols) of the PUSCH within the slot. The starting symbol and length are indicated by the Start and Length Indicator Value (SLIV) or are indicated respectively.

[0092] Thereafter, the terminal transmits a PUSCH in slot #(n+K2) according to the scheduling information of slot #n, where the PUSCH includes a UL-SCH TB.

[0093] Carrier aggregation

[0094] NR can merge multiple uplink / downlink carriers (i.e., carrier merging) to support wider uplink / downlink bandwidth. Carrier merging allows signals to be transmitted / received from multiple carriers. When carrier merging is applied, each carrier (see Figure A2) is called a component carrier (CC). CCs may be adjacent or non-adjacent to each other in the frequency domain. The bandwidth of each CC is defined independently. Asymmetric carrier merging, where the number of UL CCs and the number of DL CCs are different, is also possible.

[0095] - PCell (Primary Cell): In the case of a terminal configured for carrier merging, a cell operating on a primary frequency (e.g., Primary Component Carrier (PCC)) on which the terminal performs an initial connection establishment procedure or initiates a connection re-establishment procedure. In the case of DC (Dual Connectivity), a MCG (Master Cell Group) cell operating on a primary frequency on which the terminal performs an initial connection establishment procedure or initiates a connection re-establishment procedure.

[0096] - SCell (Secondary Cell): For a terminal configured with carrier aggregation, this is a cell that provides radio resources in addition to the special cell.

[0097] - PSCell (Primary SCG Cell): In the case of DC, a Secondary Cell Group (SCG) cell to which the UE randomly connects when performing RRC reconfiguration and synchronization processes.

[0098] - Special Cell (SpCell): In case of DC, the special cell points to a PCell of the MCG or a PSCell of the SCG. Otherwise (i.e., non-DC), the special cell points to a PCell.

[0099] - Serving Cell (ServCell): A cell configured for a terminal in the RRC_CONNECTED state. If CA / DA is not configured, there is only one serving cell (i.e., PCell). If CA / DA is configured, the serving cell indicates a cell set including the special cell and all SCells.

[0100] Meanwhile, the control information can be configured to be transmitted and received only by a specific cell. As an example, UCI is transmitted by a special cell (e.g., PCell). When an SCell (hereinafter, PUCCH-SCell) in which PUCCH transmission is permitted is configured, UCI can also be transmitted by the PUCCH-SCell. As another example, the base station allocates a scheduling cell (set) to reduce the complexity of PDCCH BD (blinding decoding) at the terminal side. For PDSCH reception / PUSCH transmission, the terminal performs PDCCH detection / decoding only in the scheduling cell. Also, the base station transmits PDCCH only in the scheduling cell (set). For example, PDCCH for downlink allocation is transmitted by cell #0 (i.e., scheduling cell), and its PDSCH is transmitted by cell #2 (i.e., scheduled cell) (Cross-Carrier Scheduling, CCS). The scheduling cell (set) is configured by a terminal-specific, terminal-group-specific, or cell-specific manner. The scheduling cell includes a special cell (eg, a PCell).

[0101] A carrier indicator field (CIF) is used for CCS (Cross-Carrier Scheduling). The CIF is semi-statically disabled / enabled by terminal-specific (or terminal group-specific) higher layer (e.g., Radio Resource Control, RRC) signaling. The CIF field is an x-bit field (e.g., x=3) in the PDCCH (i.e., DCI) and is used to indicate the (serving) cell index of the scheduled cell.

[0102] - CIF disabled: There is no CIF in the PDCCH. The PDCCH on the scheduling cell allocates PDSCH / PUSCH resources on the same cell, i.e. the scheduling cell is the same as the scheduled cell.

[0103] - CIF enabled: CIF exists in PDCCH. The scheduling PDCCH allocates PDSCH / PUSCH resources in one cell among multiple cells using CIF. The scheduling cell is the same as or different from the scheduled cell. PDSCH / PUSCH means PDSCH or PUSCH.

[0104] FIG. 7 is a diagram for explaining carrier merging. In FIG. 7, it is assumed that three cells are merged. When CIF is disabled, in each cell, only the PDCCH that schedules its own PDSCH / PUSCH is transmitted (self-carrier scheduling, SCS). On the other hand, when CIF is enabled by terminal-specific (or terminal-group-specific or cell-specific) higher layer signaling and cell A is set as a scheduling cell, cell A transmits not only the PDCCH that schedules cell A's PDSCH / PUSCH, but also the PDCCH that schedules the PDSCH / PUSCH of other cells (i.e., scheduled cells) (cross-carrier scheduling, CCS). In this case, cell B / C does not transmit the PDCCH that schedules its own cell.

[0105] NR-shared spectrum / unlicensed band (NR-U) operation

[0106] FIG. 8 is a diagram illustrating a wireless communication system supporting an unlicensed band. For convenience, a cell operating in a licensed band (hereinafter, L-band) is defined as an LCell, and a carrier of the LCell is defined as a (DL / UL) LCC (Licensed Component Carrier). A cell operating in an unlicensed band (hereinafter, U-band) is defined as an UCell, and a carrier of the UCell is defined as a (DL / UL) UCC (Unlicensed Component Carrier). A cell's carrier refers to the operating frequency (e.g., center frequency) of the cell. A cell / carrier (e.g., Component Carrier, CC) is collectively referred to as a cell.

[0107] When carrier aggregation (CA) is supported, one terminal can transmit and receive signals to and from a base station through multiple aggregated cells / carriers. When multiple CCs are configured in one terminal, one CC is set as a PCC (Primary CC) and the remaining CCs are set as SCCs (Secondary CCs). Specific control information / channels (e.g., CSS PDCCH, PUCCH) are set to be transmitted and received only through the PCC. Data is transmitted and received through the PCC / SCC. FIG. 8(a) illustrates an example in which a terminal and a base station transmit and receive signals through an LCC and a UCC (non-standalone (NSA) mode). In this case, the LCC is set as a PCC and the UCC is set as an SCC. When multiple LCCs are configured in a terminal, one specific LCC is set as a PCC and the remaining LCCs are set as SCCs. FIG. 8(a) corresponds to LAA in a 3GPP LTE system. Figure 8(b) illustrates an example in which a terminal and a base station transmit and receive signals via one or more UCCs without an LCC (SA (Standalone) mode). In this case, one of the UCCs is configured as a PCC, and the remaining UCCs are configured as SCCs. As a result, the NR UCell supports PUCCH, PUSCH, PRACH transmission, etc. In the unlicensed band of the 3GPP NR system, both the NSA mode and the SA mode are supported.

[0108] Unless otherwise stated, the following definitions apply to terms used in this specification.

[0109] - Channel: A channel is a set of consecutive RBs in a shared spectrum where a channel access process is performed. It refers to a carrier or a part of a carrier.

[0110] - Channel Access Procedure (CAP): A procedure for evaluating channel availability based on sensing to determine whether other communication nodes are using the channel before transmitting a signal. The basic unit for sensing is T slThe sensing slot has a duration of 9 us. The base station or the terminal senses the channel during the sensing slot, and the power detected for at least 4 us within the sensing slot is equal to or greater than the energy detection threshold X Thresh If it is smaller, the sensing slot period T sl is considered to be idle. Otherwise, the sensing slot period T sl =9us is considered busy. CAP is also known as LBT (Listen-Before-Talk).

[0111] - Channel occupancy: refers to the corresponding transmission on a channel by a base station / terminal after performing a channel access procedure.

[0112] - Channel Occupancy Time (COT): This refers to the total time that the base station / terminal and any base station / terminal sharing the channel occupancy can transmit on the channel after the base station / terminal performs the channel connection process. When determining the COT, if the transmission gap is 25us or less, the gap period is also counted in the COT. The COT is shared for transmission between the base station and the corresponding terminal.

[0113] - DL transmission burst: is defined as a set of transmissions from a base station with no gaps of more than 16us. Transmissions from a base station separated by gaps of more than 16us are considered to be individual DL transmission bursts. The base station does not sense channel availability within a DL transmission burst and transmits after the gap.

[0114] - UL transmission burst: is defined as a set of transmissions from a terminal with no gaps longer than 16us. Transmissions from a terminal separated by gaps longer than 16us are considered as individual UL transmission bursts. The terminal does not sense channel availability within a UL transmission burst and transmits after the gap.

[0115] - Detection burst: refers to a DL transmission burst that includes a set of signals and / or channels bounded within a (time) window and associated duty cycle. In an LTE-based system, a detection burst is a base station initiated transmission that includes PSS, SSS, and CRS (cell-specific RS), and also includes non-zero power CSI-RS. In an NR-based system, a detection burst is a base station initiated transmission that includes at least SS / PBCH blocks, and also includes CORESET for PDCCH that schedules PDSCH with SIB1, PDSCH carrying SIB1, and / or non-zero power CSI-RS.

[0116] FIG. 9 illustrates a method of occupying resources in an unlicensed band. According to regional regulations for unlicensed bands, a communication node in an unlicensed band must determine whether other communication nodes are using the channel before transmitting a signal. Specifically, a communication node can first perform carrier sensing (CS) before transmitting a signal to determine whether other communication nodes are transmitting signals. A case where it is determined that other communication nodes are not transmitting signals is defined as a case where a clear channel assessment (CCA) is confirmed. If there is a CCA threshold set by a predetermined or higher layer (e.g., RRC) signaling, a communication node determines the channel state as busy when energy higher than the CCA threshold is detected in the channel, and otherwise determines the channel state as idle. For reference, in the Wi-Fi standard (802.11ac), the CCA threshold is specified as -62 dBm for non-Wi-Fi signals and -82 dBm for Wi-Fi signals. If the channel state is determined to be idle, the communication node can start transmitting signals on the UCell. The above series of processes is called LBT (Listen-Before-Talk) or CAP (Channel Access Procedure). LBT and CAP can be used interchangeably.

[0117] Table 6 illustrates the channel access procedure (CAP) supported in NR-U.

[0118] [Table 6]

[0119] Multi-cell Scheduling DCI

[0120] NR supports broad spectrum in various frequency ranges. The re-farming of frequency bands used in previous generations is expected to increase the availability of advanced spectrum for 5G. In particular, for the low frequency band FR1, available spectrum blocks tend to become more fragmented and dispersed. For FR2 bands and some FR1 bands, the available spectrum becomes wider, necessitating the operation of multiple carriers / cells within the band. It is necessary to improve throughput and coverage by using such dispersed spectrum bands or wider bandwidth spectrum in a more power-efficient and flexible manner.

[0121] When scheduling data across multiple cells, including intra-band and inter-band cells, it is important to increase flexibility and spectrum / power efficiency. In the current 5G NR scheduling method, DCI can only schedule PUSCH / PDSCH for one cell. However, it is expected that the need for simultaneous scheduling of multiple cells will increase in the future due to spectrum expansion / modification, etc. In order to reduce control overhead due to scheduling, it is advantageous to schedule PUSCH / PDSCH for multiple cells using one DCI.

[0122] Thus, in future, in carrier aggregation (CA) situations where multiple cells are configured, in order to reduce the DCI overhead for PDSCH / PUSCH scheduling, Rel-18 will consider a multi-cell scheduling scheme that simultaneously schedules multiple (serving) cells / CCs (and thus PDSCH / PUSCH transmissions) with a single DCI.

[0123] Here, a method for configuring and interpreting each field in DCI for designing a DCI (multi-cell DCI) structure performing the above-mentioned multi-cell scheduling is proposed. In this specification, in each section mainly describing the operation of multi-cell scheduling for PDSCH or PUSCH transmission, the operation principle of the proposed method can be similarly applied to the case of multi-cell scheduling for PUSCH or PDSCH transmission. In addition, in this specification, a cell may refer to a BWP configured / indicated (active) for that cell.

[0124] Hereinafter, the multi-cell scheduling DCI is also referred to as a multi-cell DCI or simply DCI, and includes at least one of a DL grant DCI for scheduling a PDSCH and a UL grant DCI for scheduling a PUSCH.

[0125] [1] DL (or UL) DCI field configuration for multi-cell PDSCH (or PUSCH) scheduling

[0126] Hereinafter, various methods (e.g., methods 1 to 6) described for configuring a DCI field are understood as types applied to each DCI field, and all fields of a multi-cell scheduling DCI are not necessarily configured in one specific method. For example, in one multi-cell scheduling DCI, a first DCI field is configured based on method X, and a second DCI field is configured based on method Y. Furthermore, the following method classifications are based on the assumption of the most detailed configuration form for convenience of explanation, and one DCI field can also be configured by a combination of different DCI field configuration methods within a non-conflicting range.

[0127] 1) DCI field configuration type

[0128] A. Method 1: Shared-reference-cell (Shared-reference-cell)

[0129] Only one field is configured in the multi-cell DCI, and the value indicated in that DCI field is applied only to one specific reference cell (among the cells scheduled by the multi-cell DCI (cells for which an operation according to the DCI field is set)) (e.g., the cell from which the DCI is transmitted, or the cell with the lowest (or highest) cell index, or the cell indicated by the CIF field value), and a predefined / set default value is applied to other cells.

[0130] B. Method 2: Shared-single-cell

[0131] In this method, only one field (at most) is configured in the multi-cell DCI, and the DCI field is configured (the value indicated in the field is applied to the one cell) only when one cell is scheduled (by the multi-cell DCI), and when multiple cells are scheduled, the DCI field is not configured and is omitted (in this case, a predefined / set default value is applied to the multiple cells).

[0132] C. Method 3: Shared-cell-common

[0133] In this method, only one field is configured in the multi-cell DCI, and the value indicated in that DCI field is commonly applied to all cells (scheduled by the multi-cell DCI).

[0134] D. Method 4: Shared-state-extension

[0135] A method in which only one field is configured in the multi-cell DCI, and each of the multiple states / codepoints that can be indicated in that DCI field is configured / set with multiple information combinations for multiple cells (rather than information for a single cell).

[0136] E. Method 5: Separate

[0137] In this scheme, the same number of fields as the number of cells scheduled by the multi-cell DCI (with the operation set according to the DCI field indication) are configured (in the DCI), a separate field corresponds to each scheduled cell, and the value indicated in the field is applied to the cell. For example, when frequency domain resource allocation (FDRA) information and / or MCS information are configured in a separate manner, the multi-cell DCI includes, but is not limited to, FDRA information and / or MCS information for each of the multiple cells (e.g., first FDRA information / first MCS information for a first scheduled cell, second FDRA information / second MCS information for a second scheduled cell, etc.).

[0138] F. Method 6: Omit

[0139] In this method, the DCI field is not configured and is omitted in the multi-cell DCI (in this case, a specific default value that is predefined / set is applied to the cells scheduled by the multi-cell DCI).

[0140] 2) Example of application of the proposed method for each DCI field

[0141] Below, an example will be described in which the above-mentioned "1) DCI field configuration type" is applied to each of various DCI fields included in a multi-cell DCI.

[0142] A. Bandwidth part (BWP) indicator

[0143] i.Opt 1: Apply the Shared-reference-cell method

[0144] The value (BWP index) indicated in this DCI field applies only to the specific reference cell (among the cells scheduled by the multi-cell DCI), and for other cells, there is no BWP switching and the currently operating BWP is maintained.

[0145] ii. Opt 2: Applying the Shared-single-cell method

[0146] The DCI field is configured (and the value (BWP index) indicated thereby is applied to the cell) only when one cell is scheduled (by the multi-cell DCI); when multiple cells are scheduled, the DCI field is omitted (and not configured) (in this case, the currently active BWP is maintained for those multiple cells without BWP switching).

[0147] iii.Opt 3: Apply the above Omit method

[0148] The DCI field is not configured and omitted in the multi-cell DCI (in this case, the currently active BWP is maintained for the cell scheduled by the multi-cell DCI without BWP switching).

[0149] B. VRB-to-PRB mapping (RB mapping)

[0150] i.Opt 1: Apply the Shared-reference-cell method

[0151] The value (RB mapping method) indicated in this DCI field is applied only to the PDSCH on a specific reference cell (among the cells scheduled by the multi-cell DCI), and a predetermined default value (e.g., a non-interleaved mapping method) is applied to the PDSCH on other cells.

[0152] ii. Opt 2: Applying the Shared-single-cell method

[0153] Only when one cell is scheduled (by the multi-cell DCI), the DCI field is configured (and the value (RB mapping method) indicated thereby is applied to the PDSCH on that cell), whereas when multiple cells are scheduled, the DCI field is omitted (and not configured) (in this case, a predetermined default value (e.g., a non-interleaved mapping method) is applied to the PDSCH on those multiple cells).

[0154] iii.Opt 3: Apply the above Omit method

[0155] The corresponding DCI field is not configured and omitted in the multi-cell DCI (in this case, a predetermined default value (e.g., a non-interleaved mapping scheme) is applied to the PDSCH on the cell scheduled by the multi-cell DCI).

[0156] iv.Opt 4: Apply the Shared-cell-common method

[0157] The value (RB mapping method) indicated in this DCI field is commonly applied to the PDSCH on all cells (scheduled by the multi-cell DCI) (all such cells are all cells (among the cells scheduled by the multi-cell DCI) for which the RB mapping indication bit is set).

[0158] C.PRB bundling size indicator

[0159] i.Opt 1: Apply the Shared-reference-cell method

[0160] The value (PRB bundle size) indicated in this DCI field applies only to the PDSCH on a specific reference cell (among the cells scheduled by the multi-cell DCI), and a predetermined default value (e.g., assuming a static bundling setting or a predefined / configured PRB bundle size) applies to the PDSCH on other cells.

[0161] ii. Opt 2: Applying the Shared-single-cell method

[0162] Only when one cell is scheduled (by the multi-cell DCI), the DCI field is configured (and the value indicated thereby (PRB bundle size) is applied to the PDSCH on that cell), whereas when multiple cells are scheduled, the DCI field is omitted (in which case a predefined default value (e.g., assuming a static bundling setting or a predefined / configured PRB bundle size) is applied to the PDSCH on those multiple cells).

[0163] iii.Opt 3: Apply the above separation method

[0164] A separate field is configured for each cell scheduled by the multi-cell DCI, with the individual field size varying depending on the number of scheduled cells (e.g., the field size is configured to be smaller when more than N scheduled cells are scheduled than when N or fewer cells are scheduled (e.g., N=1)).

[0165] iv.Opt 4: Apply the above Omit method

[0166] The corresponding DCI field is not configured and omitted in the multi-cell DCI (in this case, a predetermined default value (e.g., a static bundling setting is assumed or a predefined / configured PRB bundle size) is applied to the PDSCH on the cell scheduled by the multi-cell DCI).

[0167] D. Rate matching (RM) indicator

[0168] i.Opt 1: Apply the Shared-reference-cell method

[0169] The value (RM target resource) indicated in this DCI field applies only to the PDSCH on a specific reference cell (among the cells scheduled by the multi-cell DCI), and for the PDSCH on other cells, the PDSCH is received assuming that there is no RM target resource / operation instruction.

[0170] ii. Opt 2: Applying the Shared-single-cell method

[0171] Only when one cell is scheduled (by the multi-cell DCI) is the DCI field configured (the value indicated thereby (RM target resource) is applied to the PDSCH on that cell), whereas when multiple cells are scheduled, the DCI field is omitted (in this case, the PDSCH is received under the assumption that there is no RM target resource / operation indication for the PDSCH on those multiple cells).

[0172] iii.Opt 3: Apply the above Omit method

[0173] The corresponding DCI field is not configured and omitted in the multi-cell DCI (in this case, the PDSCH is received assuming that there is no RM target resource / operation instruction for the PDSCH on the cell scheduled by the multi-cell DCI).

[0174] iv.Opt 4: Apply the above Separate method

[0175] A separate field is configured for each cell scheduled by the multi-cell DCI, with the individual field size varying depending on the number of scheduled cells (e.g., the field size is configured to be smaller when more than N scheduled cells are scheduled than when N or fewer cells are scheduled (e.g., N=1)).

[0176] v.Opt 5: Apply the Shared-state-extension method

[0177] Each of the multiple states that can be indicated by the DCI field is configured / set with a combination of multiple RM target resources for multiple PDSCHs on multiple cells (rather than RM target resources for a PDSCH on a single cell), thereby indicating a specific RM target resource combination (for multiple PDSCHs on multiple cells) by that one field.

[0178] E.ZP CSI-RS Trigger

[0179] i.Opt 1: Apply the Shared-reference-cell method

[0180] The value (ZP CSI-RS resource) indicated in this DCI field applies only to the PDSCH on a specific reference cell (among the cells scheduled by the multi-cell DCI), and for the PDSCH on other cells, it is assumed that there is no ZP CSI-RS resource indication and the PDSCH is received.

[0181] ii. Opt 2: Applying the Shared-single-cell method

[0182] Only when one cell is scheduled (by multi-cell DCI), the DCI field is configured (and the value indicated thereby (ZP CSI-RS resource) is applied to the PDSCH on that cell), whereas when multiple cells are scheduled, the DCI field is not configured and is omitted (in this case, the PDSCH is received under the assumption that there is no ZP CSI-RS resource indication for the PDSCH on those multiple cells).

[0183] iii.Opt 3: Apply the above Omit method

[0184] The corresponding DCI field is not configured and omitted in the multi-cell DCI (in this case, the PDSCH is received under the assumption that there is no ZP CSI-RS resource indication for the PDSCH on the cell scheduled by the multi-cell DCI).

[0185] iv.Opt 4: Apply the above Separate method

[0186] A separate field is configured for each cell scheduled by the multi-cell DCI, with the individual field size varying depending on the number of scheduled cells (e.g., the field size is configured to be smaller when more than N scheduled cells are scheduled than when N or fewer cells are scheduled (e.g., N=1)).

[0187] v.Opt 5: Apply the Shared-state-extension method

[0188] Each of the multiple states that can be indicated by the DCI field is configured / set with a combination of multiple ZP CSI-RS resources for multiple PDSCHs on multiple cells (rather than a ZP CSI-RS resource for a PDSCH on a single cell), thereby indicating a specific ZP CSI-RS resource combination (for multiple PDSCHs on multiple cells) by that one field.

[0189] F. One-shot HARQ-ACK (Type-3 codebook) request

[0190] i. Opt 1: Shared-single-cell method applied

[0191] Only when one cell is scheduled (by multi-cell DCI), the corresponding DCI field is configured (which instructs whether or not to configure / transmit Type-3 codebook-based HARQ-ACK feedback (in the form of mapping / configuring a corresponding HARQ-ACK for each HARQ (process) ID)), and when multiple cells are scheduled, the corresponding DCI field is not configured and is omitted (in this case, it operates under the assumption that there is no instruction to configure / transmit Type-3 codebook-based HARQ-ACK feedback (by multi-cell DCI)).

[0192] ii.Opt 2: Apply the above Omit method

[0193] The corresponding DCI field is not configured in the multi-cell DCI and is omitted (thus, when scheduled by the multi-cell DCI, it operates under the assumption that there is no Type-3 codebook-based HARQ-ACK feedback configuration / transmission instruction (by that DCI)).

[0194] G. Enhanced Type-3 codebook (e-Type-3 CB index) indicator

[0195] i. Opt 1: Shared-single-cell method applied

[0196] Only when one cell is scheduled (by multi-cell DCI), the corresponding DCI field is configured (thereby instructing whether or not to configure / transmit e-Type-3 CB (index) (in the form of mapping / configuring HARQ-ACK for only some of the CA-enabled cells and / or some of the HARQ IDs)), and when multiple cells are scheduled, the corresponding DCI field is omitted without being configured (in this case, it operates under the assumption that there is no instruction to configure / transmit e-Type-3 CB (by multi-cell DCI)).

[0197] ii.Opt 2: Apply the above Omit method

[0198] The DCI field is not configured in the multi-cell DCI and is omitted (thus, when scheduled by the multi-cell DCI, it operates under the assumption that there is no e-Type-3 CB configuration / transmission instruction (by that DCI)).

[0199] iii. Opt 3: Using the MCS field of a specific (reference) cell

[0200] 1. When an invalid value (or a predefined value) is indicated in a frequency domain resource assignment (FDRA) field corresponding to a specific (reference) cell among one or more cells (schedulable) indicated by the multi-cell DCI (e-Type-3 CB configuration / transmission is indicated by the DCI) (e.g., when all bits are indicated as '0' in the case of a resource allocation (RA) type in the form of a bitmap (e.g., type 0), or when all bits are indicated as '1' in the case of a resource indication value (RIV) type (e.g., type 1)), the e-Type-3 CB index information is signaled / indicated by an MCS field corresponding to the specific (reference) cell. For example, any one of one or more e-Type-3 CB indexes configured in the UE by higher layer signaling is indicated by the multi-cell DCI. Each e-Type-3 CB index corresponds to a subset of all cells configured in the terminal, and a cell for performing e-Type-3 CB report is determined based on the e-Type-3 CB index indicated by the multi-cell DCI. For example, referring to FIG. 10, it is assumed that e-Type-3 CB index 1 corresponds to {Cell A, Cell B, Cell C}, e-Type-3 CB index 2 corresponds to {Cell A, Cell C, Cell D, Cell E}, and a multi-cell DCI for indicating / triggering e-Type-3 CB report is received by the terminal. An invalid value (or a predefined value) is indicated by a second FDRA field for a specific cell among the FDRA fields of the multi-cell DCI, and an e-Type-3 CB index is indicated by a second MCS field for a specific cell among the MCS fields of the multi-cell DCI.For example, when e-Type-3 CB index 1 is indicated by the second value set in the second MCS field, the UE generates and reports e-Type 3 CB including HARQ-ACK for {Cell A, Cell B, Cell C}. In this manner, for a specific cell associated with an FDRA field in which an invalid value (or a predefined value) is indicated among the FDRA fields, e-Type-3 CB index information can be indicated instead of MCS indicated by the MCS field. For example, in FIG. 10, when the MCS field of a specific cell associated with a second FDRA field in which an invalid value (or a predefined value) is indicated among the FDRA fields is the second MCS field, the second MCS field is reused to indicate e-Type-3 CB index information (not MCS).

[0201] As an example, the terminal operates under the assumption that there is no PDSCH scheduling / transmission for the particular (reference) cell. For example, the terminal determines that no PDSCH is scheduled for a particular cell associated with an FDRA field indicating an invalid value (or a predefined value) by the multi-cell DCI.

[0202] b. As an example, the terminal can perform PDSCH scheduling / transmission for other cells other than the specific (reference) cell among one or more cells (schedulable) indicated by the multi-cell DCI instructing e-Type-3 CB configuration / transmission (based on invalid FDRA) as described above. For example, referring to FIG. 10, the first FDRA field for the other cell other than the specific cell may include valid FDRA information, and the first value of the first MCS field is the MCS for the PDSCH. Alternatively, the terminal operates in a state in which it is assumed that there is no PDSCH scheduling / transmission for other cells (other than the specific (reference) cell) among one or more cells (schedulable) indicated by the multi-cell DCI instructing e-Type-3 CB configuration / transmission (based on invalid FDRA) as described above.

[0203] 2. On the other hand, to indicate cell combinations (i.e., co-scheduled cell sets) that are scheduled simultaneously from a multi-cell DCI, the following (cell combination) table-based method and FDRA field-based method are applied.

[0204] a. In the case of a (cell combination) table-based method, the RRC configures (one or more) multiple cell combinations and configures a table (rows within the table), and then a specific indicator in the multi-cell DCI indicates which of the cell combinations (corresponding to the row) is to be scheduled.

[0205] b. In the case of a method based on the FDRA field, a method is used in which only cells with valid values ​​indicated are scheduled by the FDRA field configured separately for each cell within the multi-cell DCI (for candidate cells (i.e., candidate cell set) configured as schedulable from that DCI) (without a separate table / indicator as described above) (while cells with invalid values ​​indicated in the FDRA field are considered / treated as not being scheduled).

[0206] 3. Therefore, when the (scheduled) cell combination indication method based on the table is configured / applied, the following e-Type-3 codebook (CB) feedback triggering method can be considered.

[0207] a.Opt A: If an invalid FDRA value is indicated for a specific cell among the cells indicated (scheduled) by the multi-cell DCI (e-Type-3 CB configuration / transmission is indicated by a specific indicator within that DCI), the terminal shall consider / treat all scheduled cells, including that specific cell, as having no scheduling, and operate to perform only the indicated e-Type-3 CB configuration / transmission.

[0208] i) In this case, the e-Type-3 CB index information is signaled / indicated by the MCS field corresponding to the particular cell.

[0209] ii) Meanwhile, the specific cell is limited to the cell having the lowest (or highest) cell index in the set of co-scheduled cells, or the cell having the lowest (or highest) cell index in the entire set of candidate cells, or the scheduled cell from which the multi-cell DCI is transmitted, or a cell configured separately by the RRC.

[0210] b. Opt B: If an invalid FDRA value is indicated for all of the cells indicated (scheduled) by the multi-cell DCI (e-Type-3 CB configuration / transmission is indicated by a specific indicator within that DCI), the terminal shall consider / treat all scheduled cells as having no scheduling and operate to perform only the indicated e-Type-3 CB configuration / transmission.

[0211] i) In this case, the e-Type-3 CB index information is signaled / indicated (the same single CB index) by all MCS fields corresponding to each of the scheduled cells.

[0212] ii) Alternatively, in this case, the e-Type-3 CB index information is signaled / indicated by an MCS field corresponding to a particular one of the scheduled cells (e.g., the cell having the lowest (or highest) cell index).

[0213] c. Opt C: If an invalid FDRA value is indicated for at least one of the cells indicated (scheduled) by the multi-cell DCI (e-Type-3 CB configuration / transmission is indicated by a specific indicator within that DCI), the terminal shall consider / treat all of the scheduled cells as having no scheduling and operate to perform only the indicated e-Type-3 CB configuration / transmission.

[0214] i) In this case, the e-Type-3 CB index information is signaled / indicated (the same single CB index) by the MCS field corresponding to each scheduled cell for which the aforementioned invalid FDRA is indicated.

[0215] ii) Alternatively, in this case, the e-Type-3 CB index information is signaled / indicated by an MCS field corresponding to a specific one of the scheduled cells (e.g., the cell having the lowest (or highest) cell index) for which the aforementioned invalid FDRA is indicated.

[0216] 4. In addition, when the FDRA-based (scheduled) cell combination indication method is configured / applied, the following e-Type-3 CB feedback triggering method can be considered.

[0217] a. Opt X: If the multi-cell DCI indicates an invalid FDRA value for a specific cell among the candidate cells (for which e-Type-3 CB configuration / transmission is indicated and which is set as schedulable by the DCI), the terminal assumes / treats that there is no scheduling for that specific cell (and any cells for which an invalid FDRA value is indicated, including this one), and operates to perform scheduled PDSCH reception and indicated e-Type-3 CB configuration / transmission on the other cells (for which a valid FDRA value is indicated).

[0218] i) In this case, the e-Type-3 CB index information is signaled / indicated by the MCS field corresponding to the particular cell.

[0219] ii) On the other hand, in this case, the e-Type-3 CB feedback transmission timing is determined based on a specific PDSCH (e.g., the PDSCH whose last symbol is latest in time) among the PDSCHs scheduled on other cells (for which a valid FDRA value is indicated) excluding the specific cell (and cells for which an invalid FDRA value is indicated), (e.g., by applying the K1 value to that PDSCH point in time).

[0220] iii) Alternatively, in this case, the terminal considers / treats all of the candidate cells as having no scheduling, and operates to perform only the instructed e-Type-3 CB configuration / transmission.

[0221] iv) On the other hand, the specific cell is limited to the cell with the lowest (or highest) cell index within the entire candidate cell set, or the scheduling cell from which the multi-cell DCI is transmitted, or a cell configured separately by the RRC.

[0222] b. Opt Y: If the multi-cell DCI indicates an invalid FDRA value for all candidate cells (for which e-Type-3 CB configuration / transmission is indicated and which are set as schedulable by the DCI), the terminal assumes / treats all of the candidate cells as not having scheduling and operates to perform only the indicated e-Type-3 CB configuration / transmission.

[0223] i) In this case, the e-Type-3 CB index information is signaled / indicated (the same single CB index) by all MCS fields corresponding to each of the candidate cells.

[0224] ii) Alternatively, in this case, the e-Type-3 CB index information is signaled / indicated by an MCS field corresponding to a particular one of the scheduled cells (e.g., the cell having the lowest (or highest) cell index).

[0225] c. Opt Z: If the multi-cell DCI indicates an invalid FDRA value for at least one of the candidate cells (for which e-Type-3 CB configuration / transmission is indicated and which is set as schedulable by the DCI), the terminal assumes / treats the cell for which the invalid FDRA is indicated as having no scheduling, and operates to perform scheduled PDSCH reception and indicated e-Type-3 CB configuration / transmission on the other cells.

[0226] i) In this case, the e-Type-3 CB index information is signaled / indicated (the same single CB index) by the MCS field corresponding to each scheduled cell for which the aforementioned invalid FDRA is indicated.

[0227] ii) Alternatively, in this case, the e-Type-3 CB index information is signaled / indicated by an MCS field corresponding to a specific one of the scheduled cells (e.g., the cell having the lowest (or highest) cell index) for which the aforementioned invalid FDRA is indicated.

[0228] iii) On the other hand, in this case, the e-Type-3 CB feedback transmission timing is determined based on a specific PDSCH (e.g., the PDSCH whose last symbol is latest in time) among the PDSCHs scheduled on the cells other than the cell for which the invalid FDRA is indicated (e.g., by applying the K1 value to that PDSCH time point).

[0229] iv) Alternatively, in this case, the terminal considers / treats all of the candidate cells as having no scheduling and operates to perform only the instructed e-Type-3 CB configuration / transmission.

[0230] H.HARQ-ACK retransmission indicator

[0231] i. Opt 1: Shared-single-cell method applied

[0232] The DCI field is configured (and thus indicates whether or not to operate HARQ-ACK retransmission (instructing that the HARQ-ACK instructed to be transmitted at a specific time (slot A) be retransmitted at another time (slot B))) only when one cell is scheduled (by multi-cell DCI), and when multiple cells are scheduled, the DCI field is not configured and is omitted (in this case, it operates assuming that there is no instruction for HARQ-ACK retransmission (by multi-cell DCI)).

[0233] ii.Opt 2: Apply the above Omit method

[0234] The DCI field is not configured in the multi-cell DCI and is omitted (thus, when scheduled by the multi-cell DCI, it operates under the assumption that there is no instruction for HARQ-ACK retransmission (by that DCI)).

[0235] iii. Opt 3: Using the MCS field of a specific (reference) cell

[0236] 1. Information for determining the slot A (for HARQ-ACK retransmission), for example, offset information indicating slot A, is signaled / indicated by an MCS field corresponding to a specific (reference) cell among one or more cells (schedulable) indicated by the multi-cell DCI (if HARQ-ACK retransmission is indicated by the DCI), for example, offset information indicating slot A. For example, referring to FIG. 11, a terminal transmits a HARQ-ACK (for example, a Type-1 or Type-2 HARQ-ACK codebook) in each of one or more slots (1105) and receives a multi-cell DCI (1110). Based on the indication of HARQ-ACK retransmission, the terminal determines that the MCS field of a specific (reference) cell among the MCS fields of the multi-cell DCI includes information for determining slot A related to HARQ-ACK retransmission. The terminal determines slot A of one or more slots in which the HARQ-ACK is transmitted prior to the multi-cell DCI reception slot based on the MCS field of a specific (reference) cell (1115). The terminal retransmits the HARQ-ACK transmitted in slot A in a slot following the multi-cell DCI reception slot (1120). As an example, the multi-cell DCI may include a HARQ-ACK retransmission indication field for triggering the HARQ-ACK retransmission.

[0237] For example, the terminal operates under the assumption that there is no PDSCH scheduling / transmission for that particular (reference) cell.

[0238] b. For example, as described above, among one or more cells (schedulable) indicated by a multi-cell DCI instructing HARQ-ACK retransmission (using an MCS field corresponding to a specific (reference) cell), PDSCH scheduling / transmission is possible for other cells other than the specific (reference) cell. For example, the MCS field for other cells other than the specific cell includes valid MCS information, not information on slot A that is the target of HARQ-ACK retransmission. Alternatively, as described above, the terminal operates in a state assuming that there is no PDSCH scheduling / transmission for other cells (other than the specific (reference) cell) among one or more cells (schedulable) indicated by a multi-cell DCI instructing HARQ-ACK retransmission (using an MCS field corresponding to a specific (reference) cell).

[0239] 2. In this regard, if the (scheduled) cell combination indication method based on the table is configured / applied, the following HARQ-ACK retransmission triggering method can be considered.

[0240] a. Opt A: Slot offset information indicating slot A (for HARQ-ACK retransmission) is signaled / indicated by the MCS field corresponding to a specific (one) cell among the cells indicated (scheduled) by the multi-cell DCI (if HARQ-ACK retransmission is indicated by a specific indicator in the DCI).

[0241] i) In this case, the terminal considers / treats all scheduled cells, including that particular cell, as having no scheduling and operates to perform only the indicated HARQ-ACK retransmission.

[0242] ii) On the other hand, the specific cell is limited to the cell in the co-scheduled cell set for which an invalid FDRA value is indicated (or, if there are multiple such cells, the cell with the lowest (or highest) cell index among them), or the cell with the lowest (or highest) cell index in the co-scheduled cell set, or the cell with the lowest (or highest) cell index in the entire candidate cell set, or the scheduling cell from which the multi-cell DCI is transmitted, or a cell configured separately by RRC.

[0243] 3. In addition, when the FDRA-based (scheduled) cell combination indication method is configured / applied, the following HARQ-ACK retransmission triggering method can be considered.

[0244] a. Opt X: Slot offset information indicating slot A (target of HARQ-ACK retransmission) is signaled / indicated by the MCS field corresponding to a specific cell (one) among the candidate cells (set as schedulable in the DCI when HARQ-ACK retransmission is indicated by the multi-cell DCI).

[0245] i) In this case, the terminal considers / treats that particular cell (and the cell for which an invalid FDRA value is indicated) as having no scheduling, and operates to perform scheduled PDSCH reception and the indicated HARQ-ACK retransmission on other cells (for which a valid FDRA value is indicated).

[0246] ii) On the other hand, in this case, the transmission timing of the feedback to be retransmitted for the HARQ-ACK is determined based on a specific PDSCH (e.g., the PDSCH whose last symbol is latest in time) among the PDSCHs scheduled on other cells (for which a valid FDRA value is indicated) excluding the specific cell (and the cell for which an invalid FDRA value is indicated) (e.g., by applying the K1 value to that PDSCH point in time).

[0247] iii) Alternatively, in this case, the terminal considers / treats all candidate cells as having no scheduling (regardless of whether the FDRA value indicated for each cell is invalid or not) and operates to only perform the indicated HARQ-ACK retransmission.

[0248] iv) On the other hand, the specific cell is limited to the cell in the entire candidate cell set for which an invalid FDRA value is indicated (or, if there are multiple such cells, the cell with the lowest (or highest) cell index among them), or the cell with the lowest (or highest) cell index in the entire candidate cell set, or the scheduling cell from which the multi-cell DCI is transmitted, or a cell configured separately by RRC.

[0249] I. SRS request

[0250] i.Opt 1: Apply the Shared-reference-cell method

[0251] The value (SRS transmission resource) indicated in this DCI field applies only to the specific reference cell (among the cells scheduled by the multi-cell DCI), and operates under the assumption that there is no SRS transmission instruction for other cells.

[0252] ii. Opt 2: Applying the Shared-single-cell method

[0253] The DCI field is configured (and the value (SRS transmission resource) indicated is applied to the cell) only when one cell is scheduled (by the multi-cell DCI), and is omitted (not configured) when multiple cells are scheduled (in this case, it is assumed that there is no SRS transmission indication for those multiple cells).

[0254] iii.Opt 3: Apply the above Omit method

[0255] The corresponding DCI field is not configured in the multi-cell DCI and is omitted (in this case, it is assumed that there is no SRS transmission instruction for the cell scheduled by the multi-cell DCI).

[0256] J.CBG transmission information (CBGTI)

[0257] i. Opt 1: Shared-single-cell method applied

[0258] Only when one cell is scheduled (by multi-cell DCI), the DCI field is configured (the value indicated thereby (CBG index) is applied to the PDSCH on that cell), and when multiple cells are scheduled, the DCI field is omitted (in this case, the PDSCH on those multiple cells is received under the assumption that there is no scheduling of CBG-based PDSCH transmission).

[0259] ii.Opt 2: Apply the above Omit method

[0260] The corresponding DCI field is not configured in the multi-cell DCI and is omitted (in this case, for the PDSCH on the cell scheduled by the multi-cell DCI, it is operated to receive the PDSCH under the assumption that there is no scheduling of CBG-based PDSCH transmission).

[0261] K.CBG flushing out information (CBGFI)

[0262] i. Opt 1: Shared-single-cell method applied

[0263] Only when one cell is scheduled (by the multi-cell DCI), the DCI field is configured (the value indicated thereby (whether or not CBG buffer flush is performed) is applied to the PDSCH on that cell), and when multiple cells are scheduled, the DCI field is omitted without being configured (in this case, the PDSCH is received assuming that there is no CBG buffer flush instruction for the PDSCH on those multiple cells).

[0264] ii.Opt 2: Apply the above Omit method

[0265] The corresponding DCI field is not configured in the multi-cell DCI and is omitted (in this case, the PDSCH is received under the assumption that there is no CBG buffer flush indication for the PDSCH on the cell scheduled by the multi-cell DCI).

[0266] L. Priority indicator (PI)

[0267] i.Opt 1: Apply the shared-cell-common method

[0268] The value indicated in this DCI field (low priority (LP) or high priority (HP)) is applied commonly to the PDSCH (and its corresponding HARQ-ACK) on all cells (scheduled by the multi-cell DCI), which are all cells (among the cells scheduled by the multi-cell DCI) for which a PI is set.

[0269] a. On the other hand, if HP is indicated by the above field in the multi-cell DCI, for a cell (among the cells scheduled by that DCI) for which PI is not set, either Alt 1) operate under the assumption that there is no PI indication (or that it is indicated by the LP), or Alt 2) assume that there is no PDSCH scheduling for that cell (for which PI is not set) and skip PDSCH reception on that cell.

[0270] b. On the other hand, if LP is indicated by the field in the multi-cell DCI, the operation of Alt 1 is applied to cells (among cells scheduled by that DCI) where PI is not set.

[0271] ii. Opt 2: Apply the Shared-reference-cell method

[0272] The value (LP or HP) indicated in this DCI field applies only to the PDSCH (and its corresponding HARQ-ACK) on the specific reference cell (among the cells scheduled by the multi-cell DCI), and the operations of Alt 1 and / or Alt 2 apply to the other cells.

[0273] iii. Opt 3: Applying the Shared-single-cell method

[0274] Only when one cell is scheduled (by the multi-cell DCI) is the DCI field configured (and the value indicated thereby (LP or HP) is applied to the PDSCH (and corresponding HARQ-ACK) on that cell), and when multiple cells are scheduled, the DCI field is not configured and is omitted (in this case the behavior of Alt 1 is applied).

[0275] iv.Opt 4: Apply the above Omit method

[0276] The corresponding DCI field is not configured in the multi-cell DCI and is omitted (in this case, the behavior of Alt 1 applies).

[0277] v. Note 1: If HP is indicated for at least one cell among multiple cells scheduled by the same multi-cell DCI (and LP is indicated for the other cells), all HARQ-ACKs corresponding to PDSCH transmissions on all scheduled cells are determined to HP, in which case the HP PUCCH resource is indicated by the PRI (PUCCH resource indicator) field of that DCI.

[0278] vi.Note 2: The operation of indicating HP for some cells and indicating LP for other cells among multiple cells scheduled by the same multi-cell DCI is allowed only when multiplexing between PUCCH / PUSCH with different priorities is enabled. In this case, the HARQ-ACK corresponding to the PDSCH on the cell indicated as HP is determined to be HP, and the HARQ-ACK corresponding to the PDSCH on the cell indicated as LP is determined to be LP, and separate encoding is applied between the HP HARQ-ACK and the LP HARQ-ACK, or all HARQ-ACKs corresponding to PDSCH transmissions on all scheduled cells are determined to be HP (and in this case, the HP PUCCH resource is also indicated by the PRI field of the DCI).

[0279] M. Minimum applicable scheduling offset (min K0 / K2) indicator

[0280] i.Opt 1: Apply the shared-cell-common method

[0281] The value indicated in the DCI field (whether or not min K0 / K2 is applied) is applied commonly to all cells (scheduled by multi-cell DCI), and all of these cells are all cells (among the cells scheduled by multi-cell DCI) for which min K0 / K2 is set.

[0282] ii. Opt 2: Apply the Shared-reference-cell method

[0283] The value indicated in the DCI field (whether or not min K0 / K2 is applied) is applied only to a specific reference cell (among the cells scheduled by the multi-cell DCI), and for other cells, it is assumed that there is no indication that min K0 / K2 is applied.

[0284] iii. Opt 3: Applying the Shared-single-cell method

[0285] Only when one cell is scheduled (by multi-cell DCI) is the DCI field configured (the value indicated thereby (whether or not min K0 / K2 is applied) is applied to that cell), and when multiple cells are scheduled, the DCI field is omitted without being configured (in this case, it is assumed that there is no indication that min K0 / K2 is applied to those multiple cells).

[0286] iv.Opt 4: Apply the above Omit method

[0287] The corresponding DCI field is not configured in the multi-cell DCI and is omitted (in this case, it is assumed that there is no min K0 / K2 application indication for the cell scheduled by the multi-cell DCI).

[0288] N.SCell dormancy indication

[0289] i. Opt 1: Shared-single-cell method applied

[0290] Only when one cell is scheduled (by the multi-cell DCI), the DCI field is configured (and the value indicated thereby (whether or not a dormant BWP (switching operation to that BWP) is indicated) is applied), and when multiple cells are scheduled, the DCI field is omitted without being configured (in this case, it operates under the assumption that there is no dormant BWP (switching operation to that BWP) indication due to the DCI).

[0291] ii.Opt 2: Apply the above Omit method

[0292] The DCI field is not configured in the multi-cell DCI and is omitted (in this case, it is assumed that there is no instruction for a dormant BWP (switching operation to that BWP) from the multi-cell DCI).

[0293] iii. Note: When Scell ​​dormancy operation is indicated on multiple cells indicated by the multi-cell DCI (in a specific (e.g., CIF or new) field within the DCI) without actual PDSCH scheduling, Scell ​​dormancy information is signaled by a combination of fields such as MCS, NDI, RV, HARQ process ID, antenna port, DMRS sequence initialization, etc. corresponding to a specific reference cell among the cells (the first (and / or second) TB index of the cell).

[0294] iv. Note: Alternatively, an Scell ​​dormancy operation indication is possible without actual PDSCH scheduling (on that cell) only if only one cell is indicated by the multi-cell DCI, and if multiple cells are indicated by the multi-cell DCI, the operation of indicating Scell ​​dormancy without actual PDSCH scheduling is not permitted.

[0295] O.PDCCH monitoring skipping / SS set group switching indicator

[0296] i.Opt 1: Apply the shared-cell-common method

[0297] The value indicated in the DCI field (whether or not PDCCH monitoring skip is applied / interval or SS (search space) set group index to be monitored) is applied commonly to all cells (scheduled by multi-cell DCI), and all such cells are all cells (among the cells scheduled by multi-cell DCI) for which PDCCH monitoring skip / SS set group switching operation is configured.

[0298] ii. Opt 2: Apply the Shared-reference-cell method

[0299] The value indicated in the DCI field (whether or not PDCCH monitoring skip is applied / interval or SS set group index to be monitored) is applied only to a specific reference cell (among the cells scheduled by the multi-cell DCI), and other cells operate to receive PDCCH assuming that there is no PDCCH monitoring skip / SS set group switching instruction.

[0300] iii. Opt 3: Applying the Shared-single-cell method

[0301] Only when one cell is scheduled (by multi-cell DCI), the DCI field is configured (the value indicated thereby (whether or not PDCCH monitoring skip is applied / interval or SS set group index to be monitored) is applied to that cell), and when multiple cells are scheduled, the DCI field is not configured and is omitted (in this case, the multiple cells operate to receive PDCCH assuming that there is no PDCCH monitoring skip / SS set group switching indication).

[0302] iv.Opt 4: Apply the above Omit method

[0303] The corresponding DCI field is not configured in the multi-cell DCI and is omitted (in this case, for cells scheduled by the multi-cell DCI, it is assumed that there is no PDCCH monitoring skip / SS set group switching indication and the PDCCH is received).

[0304] FIG. 12 is a diagram illustrating a method for a terminal to receive a signal according to one embodiment.

[0305] Referring to FIG. 12, a UE may receive downlink control information (DCI) including at least one frequency domain resource allocation (FDRA) field and at least one modulation and coding scheme (MCS) field via a physical downlink control channel (PDCCH) (1205).

[0306] The UE may transmit a hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook based on the DCI (1210).

[0307] The DCI may support multi-cell scheduling based on a plurality of serving cells configured in the UE, and.

[0308] Based on that a first FDRA field for a first cell included in the DCI is set to a specific value other than a valid FDRA value for the first cell, an index of the HARQ-ACK codebook may be determined through a first MCS field for the first cell included in the DCI.

[0309] The HARQ-ACK codebook is a Type-3 HARQ-ACK codebook associated with at least a portion of the plurality of cells.

[0310] The HARQ-ACK codebook index is associated with at least one of cell information and HARQ information for a Type-3 HARQ-ACK codebook.

[0311] The terminal does not receive a physical downlink shared channel (PDSCH) from the first cell, among the plurality of cells, to which the predetermined value that is not the valid FDRA value is assigned.

[0312] The terminal receives a PDSCH based on the DCI in each of one or more cells excluding the first cell among the multiple cells.

[0313] Based on the DCI requesting the terminal to transmit a type-3 HARQ-ACK codebook, index information of the type-3 HARQ-ACK codebook is determined by the first MCS field for the first cell included in the DCI.

[0314] Based on the DCI requesting the terminal to transmit a type-3 HARQ-ACK codebook, the terminal does not receive a physical downlink shared channel (PDSCH) not only for the first cell but also for other cells among the multiple cells.

[0315] The first cell is the cell having the lowest or highest serving cell index among the plurality of cells.

[0316] The DCI includes a respective FDRA field and a respective MCS field for each of the co-scheduled cells.

[0317] FIG. 13 is a diagram for explaining a method for a base station to transmit a signal according to one embodiment.

[0318] Referring to FIG. 13, a base station transmits downlink control information (DCI) including at least one frequency domain resource allocation (FDRA) field and at least one modulation and coding scheme (MCS) field to a terminal via a physical downlink control channel (PDCCH) (1305).

[0319] The base station receives a hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook based on the DCI from the terminal (1310).

[0320] The DCI supports multi-cell scheduling based on multiple cells configured for the terminal.

[0321] Based on the fact that the first FDRA field for the first cell included in the DCI is set to a predetermined value that is not a valid FDRA value for the first cell, the index of the HARQ-ACK codebook is indicated by the first MCS field for the first cell included in the DCI.

[0322] The HARQ-ACK codebook is a Type-3 HARQ-ACK codebook associated with at least a portion of the plurality of cells.

[0323] The HARQ-ACK codebook index is associated with at least one of cell information and HARQ information for a Type-3 HARQ-ACK codebook.

[0324] The base station does not transmit a physical downlink shared channel (PDSCH) to the first cell, among the plurality of cells, to which the predetermined value that is not the valid FDRA value is assigned.

[0325] The base station transmits a PDSCH based on the DCI in each of one or more cells excluding the first cell among the plurality of cells.

[0326] Based on the DCI requesting the terminal to transmit a type-3 HARQ-ACK codebook, index information of the type-3 HARQ-ACK codebook is indicated by the first MCS field for the first cell included in the DCI.

[0327] Based on the DCI requesting the terminal to transmit a type-3 HARQ-ACK codebook, the base station does not transmit a physical downlink shared channel (PDSCH) not only to the first cell but also to other cells among the multiple cells.

[0328] The first cell is the cell having the lowest or highest serving cell index among the plurality of cells.

[0329] The DCI includes a respective FDRA field and a respective MCS field for each of the co-scheduled cells.

[0330] FIG. 14 illustrates a communication system 1 .

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

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

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

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

[0335] 15, 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), where {first wireless device 100, second wireless device 200} corresponds to {wireless device 100x, base station 200} and / or {wireless device 100x, wireless device 100x} in FIG.

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

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

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

[0339] The one or more processors 102, 202 may also be referred to as controllers, microcontrollers, microprocessors, or microcomputers. The one or more processors 102, 202 may be implemented using hardware, firmware, software, or a combination thereof. As an example, the one or more processors 102, 202 may include one or more application specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), or one or more field programmable gate arrays (FPGAs). The descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, and the like. The firmware or software configured to perform the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein may be included in the one or more processors 102, 202, or may be stored in one or more memories 104, 204 and run by the one or more processors 102, 202. The descriptions, functions, procedures, suggestions, methods and / or flow charts disclosed in this specification may be implemented using firmware or software in the form of code, instructions and / or sets of instructions.

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

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

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

[0343] Referring to Fig. 16, the wireless devices 100 and 200 correspond to the wireless devices 100 and 200 of Fig. 15 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. 15. For example, the transceiver 114 includes one or more transceivers 106 and 206 and / or one or more antennas 108 and 208 in Fig. 15. The control unit 120 is electrically connected to the communication unit 110, the memory unit 130 and the additional element 140 and controls the overall operation of the wireless device. For example, the control unit 120 controls electrical / mechanical operations of the wireless device based on the programs / codes / commands / information stored in the memory unit 130. In addition, the control unit 120 transmits information stored in the memory unit 130 to the outside (e.g., another communication device) via the communication unit 110 through a wireless / wired interface, or stores information received from the outside (e.g., another communication device) via the communication unit 110 through a wireless / wired interface in the memory unit 130.

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

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

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

[0347] 17, a vehicle or autonomous vehicle 100 includes an antenna unit 108, a communication unit 110, a control unit 120, a drive unit 140a, a power supply unit 140b, a sensor unit 140c, and an autonomous driving unit 140d. The antenna unit 108 is configured as a part of the communication unit 110. Blocks 110 / 130 / 140a to 140d correspond to blocks 110 / 130 / 140 in FIG. 17, respectively.

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

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

[0350] FIG. 18 is a diagram for explaining a DRX (Discontinuous Reception) operation of a terminal according to one embodiment of the present invention.

[0351] A terminal can perform DRX operation while executing the procedures and / or methods described / proposed above. A terminal configured for DRX can reduce power consumption by discontinuously receiving DL signals. DRX is performed in RRC (Radio Resource Control)_IDLE state, RRC_INACTIVE state, and RRC_CONNECTED state. DRX in the RRC_IDLE state and RRC_INACTIVE state is used to discontinuously receive paging signals. DRX performed in the RRC_CONNECTED state will be described below (RRC_CONNECTED DRX).

[0352] Referring to FIG. 18, the DRX cycle consists of On Duration and Opportunity for DRX. The DRX cycle defines a time interval during which On Duration is repeated periodically. On Duration indicates a time period during which the terminal monitors to receive the PDCCH. When DRX is configured, the terminal performs PDCCH monitoring during On Duration. If there is a successfully detected PDCCH during PDCCH monitoring, the terminal operates an inactivity timer and maintains an awake state. On the other hand, if there is no successfully detected PDCCH during PDCCH monitoring, the terminal enters a sleep state after the On Duration ends. Thus, when DRX is configured, PDCCH monitoring / reception is performed discontinuously in the time domain when performing the above-described / proposed procedure and / or method. For example, when DRX is configured, in this specification, PDCCH reception opportunities (e.g., slots having a PDCCH search space) are set discontinuously according to the DRX configuration. On the other hand, when DRX is not configured, PDCCH monitoring / reception is performed continuously in the time domain when performing the above / proposed procedures and / or methods. For example, in this specification, PDCCH reception opportunities (e.g., slots having PDCCH search space) are configured continuously when DRX is not configured. On the other hand, PDCCH monitoring may be restricted in the time period configured in the measurement gap regardless of whether DRX is configured or not.

[0353] Table 7 shows the process of the terminal related to DRX (RRC_CONNECTED state). Referring to Table 7, DRX configuration information is received via higher layer (e.g., RRC) signaling, and DRX ON / OFF is controlled by a DRX command of the MAC layer. If DRX is configured, the terminal can perform PDCCH monitoring discontinuously when performing the procedures and / or methods described / proposed in the present invention.

[0354] [Table 7]

[0355] Here, MAC-CellGroupConfig includes configuration information required to set MAC (Medium Access Control) parameters for a cell group. MAC-CellGroupConfig may include configuration information related to DRX. For example, MAC-CellGroupConfig includes the following information in the definition of DRX:

[0356] - Value of drx-OnDurationTimer: defines the length of the start period of the DRX cycle

[0357] - Value of drx-InactivityTimer: defines the length of the time interval in which the terminal is in an awake state after a PDCCH opportunity in which a PDCCH indicating early UL or DL ​​data is detected.

[0358] - Value of drx-HARQ-RTT-TimerDL: defines the length of the maximum time interval after a DL initial transmission is received until a DL retransmission is received.

[0359] - Value of drx-HARQ-RTT-TimerDL: Defines the maximum time interval between when a grant for a UL initial transmission is received and when a grant for a UL retransmission is received.

[0360] - drx-LongCycleStartOffset: defines the length and start time of a DRX cycle

[0361] - drx-ShortCycle(optional): defines the time length of a short DRX cycle

[0362] Here, if any one of the drx-OnDurationTimer, drx-InactivityTimer, drx-HARQ-RTT-TimerDL, and drx-HARQ-RTT-TimerDL is operating, the terminal maintains an active state and performs PDCCH monitoring at every PDCCH opportunity.

[0363] The above-described embodiments are combinations of the components and features of the present invention in a predetermined form. Each component or feature should be considered as optional unless otherwise expressly stated. Each component or feature may be implemented in a form not combined with other components or features. Also, some components and / or features may be combined to form an embodiment of the present invention. The order of each operation described in the embodiments of the present invention may be changed. Some configurations or features of any embodiment may be included in other embodiments, or may be replaced with corresponding configurations or features of other embodiments. It is obvious that claims that are not explicitly cited in the claims may be combined to form an embodiment, or may be included as a new claim by amendment after filing.

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

[0365] The present invention can be used in a terminal, a base station or other equipment of a wireless mobile communication system.

Claims

1. A method for a terminal (UE) receiving a signal in a wireless communication system, comprising: receiving downlink control information (DCI) including at least one frequency domain resource allocation (FDRA) field and at least one modulation and coding scheme (MCS) field via a physical downlink control channel (PDCCH); and transmitting a hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook based on the DCI; The DCI supports multi-cell scheduling based on a plurality of cells configured for the terminal, A method in which, based on the fact that a first FDRA field for a first cell included in the DCI is set to a predetermined value that is not a valid FDRA value for the first cell, an index of the HARQ-ACK codebook is determined by a first MCS field for the first cell included in the DCI.

2. The method of claim 1 , wherein the HARQ-ACK codebook is a type-3 HARQ-ACK codebook associated with at least a portion of the plurality of cells.

3. The method of claim 1 , wherein the HARQ-ACK codebook index is associated with at least one of cell information and HARQ process ID information for a Type-3 HARQ-ACK codebook.

4. The method of claim 1, wherein the terminal does not receive a physical downlink shared channel (PDSCH) from the first cell, which is assigned the predetermined value that is not a valid FDRA value, among the plurality of cells.

5. The method of claim 4, further comprising receiving a PDSCH based on the DCI in each of one or more cells among the plurality of cells, except for the first cell.

6. The method of claim 1, wherein index information of the type-3 HARQ-ACK codebook is determined by the first MCS field for the first cell included in the DCI based on the DCI requesting the terminal to transmit a type-3 HARQ-ACK codebook.

7. The method of claim 1, wherein the terminal does not receive a physical downlink shared channel (PDSCH) not only for the first cell but also for other cells among the plurality of cells based on the DCI requesting the terminal to transmit a type-3 HARQ-ACK codebook.

8. The method of claim 1 , wherein the first cell is a cell of the plurality of cells having a lowest or highest serving cell index.

9. The method of claim 1 , wherein the DCI includes a respective FDRA field and a respective MCS field for each co-scheduled cell.

10. A computer-readable recording medium having a program recorded thereon for carrying out the method according to claim 1.

11. A device for wireless communication, comprising: A memory for storing instruction words; and A processor that operates by executing the instruction code, The operation of the processor includes: receiving downlink control information (DCI) including at least one frequency domain resource allocation (FDRA) field and at least one modulation and coding scheme (MCS) field via a physical downlink control channel (PDCCH); and transmitting a hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook based on the DCI; The DCI supports multi-cell scheduling based on a plurality of cells configured in the device; An apparatus, wherein an index of the HARQ-ACK codebook is determined by a first MCS field for the first cell included in the DCI based on the first FDRA field for the first cell included in the DCI being set to a predetermined value that is not a valid FDRA value for the first cell.

12. a transceiver for transmitting or receiving wireless signals under the control of said processor; The device of claim 11, wherein the device is a terminal (UE) in a wireless communication system.

13. The device according to claim 11, wherein the device is an application specific integrated circuit (ASIC) or a digital signal processing device for controlling a terminal (UE).

14. 1. A method for a base station to transmit a signal in a wireless communication system, comprising: Transmitting downlink control information (DCI) including at least one frequency domain resource allocation (FDRA) field and at least one modulation and coding scheme (MCS) field to a terminal via a physical downlink control channel (PDCCH); and receiving a hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook based on the DCI from the terminal; The DCI supports multi-cell scheduling based on a plurality of cells configured for the terminal, A method in which an index of the HARQ-ACK codebook is indicated by a first MCS field for the first cell included in the DCI based on the first FDRA field for the first cell included in the DCI being set to a predetermined value that is not a valid FDRA value for the first cell.

15. A base station for transmitting a signal in a wireless communication system, comprising: A transceiver, and A processor controls the transceiver to transmit downlink control information (DCI) including at least one frequency domain resource allocation (FDRA) field and at least one modulation and coding scheme (MCS) field to a terminal via a physical downlink control channel (PDCCH), and receives a hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook from the terminal based on the DCI; The DCI supports multi-cell scheduling based on a plurality of cells configured for the terminal, A base station, wherein the index of the HARQ-ACK codebook is indicated by a first MCS field for the first cell included in the DCI based on the first FDRA field for the first cell included in the DCI being set to a predetermined value that is not a valid FDRA value for the first cell.

Images