Method performed by UE or base station in wireless communication system, and apparatus therefor

Abstract

A method performed by UE, according to an embodiment of the present disclosure, comprises: receiving DCI for scheduling a plurality of PDSCHs on a plurality of cells; receiving, on the basis of the DCI, the PDSCHs on the plurality of cells; and transmitting a HARQ-ACK codebook including a plurality of HARQ-ACKs for the plurality of PDSCHs, wherein the plurality of HARQ-ACKs are mapped in a cell index order in the HARQ-ACK codebook, the DCI provides, to one or more cells other than the plurality of cells, a specific FDRA value other than a valid FDRA value for PDSCH scheduling, on the basis of the DCI providing information for SCell dormancy indication, the UE maps, to the HARQ-ACK codebook, an ACK for the SCell dormancy indication together with the plurality of HARQ-ACKs, and a mapping position of the ACK for the SCell dormancy indication in the HARQ-ACK codebook may be determined on the basis of a cell index of a first cell having the smallest cell index among the one or more cells to which the specific FDRA value is provided.

Description

Method performed by a terminal or base station in a wireless communication system and device therefor

[0001] The present disclosure relates to a wireless communication system, and more particularly, to a method for transmitting or receiving an uplink / downlink wireless signal by a terminal or base station in a wireless communication system, and a device therefor.

[0002] Wireless communication systems are widely deployed to provide various types of communication services, such as voice and data. Typically, wireless communication systems are multiple access systems that support communication with multiple users by sharing available system resources (e.g., bandwidth, transmission power). Examples of multiple access systems include code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), and single-carrier frequency division multiple access (SC-FDMA).

[0003] In Rel. 16 NR, the Scell ​​dormancy indication was introduced to conserve UE power. UEs can save power by omitting PDCCH monitoring for Scells indicated as dormant. However, CSI / RRM measurements are still performed in the corresponding Scell. This Scell ​​dormancy indication is performed via DCI that does not schedule the PDSCH, and the UE transmits a 1-bit ACK in response to the Scell ​​dormancy indication.

[0004] Meanwhile, in Rel.18 NR, the introduction of multi-cell scheduling (MC) DCI for scheduling multiple cells with a single DCI is being discussed.

[0005] The technical task to be achieved is to provide a method for efficiently performing a wireless signal transmission and reception process and a device therefor. As an example, a method for configuring HARQ-ACK for a Scell ​​dormancy indication through a multi-cell scheduling DCI and a device therefor can be provided.

[0006] The technical challenges to be achieved are not limited to these, and other technical challenges not mentioned can be inferred from the description below.

[0007] A method performed by a terminal according to one aspect of the present disclosure may include receiving downlink control information (DCI) for scheduling a plurality of physical downlink shared channels (PDSCHs) on a plurality of cells; receiving the plurality of PDSCHs on the plurality of cells, based on the DCI; and transmitting a hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook including a plurality of HARQ-ACKs for the plurality of PDSCHs. Within the HARQ-ACK codebook, the plurality of HARQ-ACKs may be mapped in an order of cell index.(i) the DCI provides a specific frequency domain resource allocation (FDRA) value for at least one cell other than the plurality of serving cells, the specific FDRA value being different from a valid FDRA value for PDSCH scheduling, and (ii) the DCI provides information for secondary cell (SCell) dormancy indication, the UE may map an ACK for the SCell dormancy indication along with the plurality of HARQ-ACKs in the HARQ-ACK codebook.The mapping position of the ACK for the SCell dormancy indication within the HARQ-ACK codebook may be determined based on a cell index of a first cell having a smallest cell index among the at least one cell for which the specific FDRA value is provided.

[0008] Within the HARQ-ACK codebook, the plurality of HARQ-ACKs and the ACK for the SCell Dormancy indication may be sorted in cell index order based on the cell indices of the plurality of cells and the cell index of the first cell.

[0009] Within the above HARQ-ACK codebook, the ACK for the SCell Dormancy indication can be mapped to a HARQ-ACK for one TB (transport block) of the first cell.

[0010] For the remaining cells, excluding the first cell, among the at least one cell for which the specific FDRA value is provided, ACK may not be mapped to the HARQ-ACK codebook.

[0011] In the DCI providing information for the SCell Dormancy indication, a one-shot HARQ-ACK request field may not be provided or may have a value of 0, a HARQ-ACK retransmission indication field may not be provided or may have a value of 0, and the specific FDRA value may be provided in the FDRA information of at least one cell.

[0012] Information for the SCell Dormancy indication may be provided through MCS (modulation and coding scheme) information, NDI (new data indicator) information, and RV (redundancy version) information for the first TB (transport block) of the first cell having the smallest cell index among the at least one cell for which the specific FDRA value is provided.

[0013] The above HARQ-ACK codebook may be a type-2 HARQ-ACK codebook.

[0014] The size of the above HARQ-ACK codebook may be determined based on at least one of the maximum number of cells that can be scheduled together through the DCI and the maximum number of TBs (transport blocks).

[0015] On at least one cell provided with the above specific FDRA value, the PDSCH may not be scheduled via the DCI.

[0016] According to another aspect of the present disclosure, a non-transitory computer-readable recording medium having recorded thereon instructions configured to cause the terminal to perform the method described above when executed by a processor of the terminal is provided.

[0017] According to another aspect of the present disclosure, a device comprises a memory storing commands; and a processor performing operations by executing the commands, wherein the operations of the processor include receiving downlink control information (DCI) for scheduling a plurality of physical downlink shared channels (PDSCHs) on a plurality of cells; receiving the plurality of PDSCHs on the plurality of cells based on the DCI; And transmitting a HARQ-ACK codebook including a plurality of HARQ-ACKs (hybrid automatic repeat request-acknowledgements) for the plurality of PDSCHs, wherein the plurality of HARQ-ACKs are mapped in cell index order within the HARQ-ACK codebook, and (i) the DCI provides a specific frequency domain resource allocation (FDRA) value that is not a valid FDRA value for PDSCH scheduling for at least one cell other than the plurality of cells, and (ii) the DCI provides information for a secondary cell (SCell) Dormancy indication, wherein the device maps an ACK for the SCell Dormancy indication together with the plurality of HARQ-ACKs to the HARQ-ACK codebook, wherein a mapping position of the ACK for the SCell Dormancy indication within the HARQ-ACK codebook can be determined based on a cell index of a first cell having a smallest cell index among the at least one cell for which the specific FDRA value is provided.

[0018] The above device further includes a transceiver, and the device may be a terminal for wireless communication.

[0019] The above device may be a processing device configured to control a terminal for wireless communication.

[0020] A method performed by a base station according to another aspect of the present disclosure comprises: transmitting a DCI for scheduling a plurality of physical downlink shared channels (PDSCHs) on a plurality of cells; transmitting the plurality of PDSCHs on the plurality of cells; And receiving a HARQ-ACK codebook including a plurality of HARQ-ACKs (hybrid automatic repeat request-acknowledgements) for the plurality of PDSCHs, wherein the plurality of HARQ-ACKs are mapped in cell index order within the HARQ-ACK codebook, and (i) the DCI provides a specific frequency domain resource allocation (FDRA) value that is not a valid FDRA value for scheduling a PDSCH for at least one cell other than the plurality of cells, and (ii) the DCI provides information for a secondary cell (SCell) Dormancy indication, wherein the base station receives an ACK for the SCell Dormancy indication together with the plurality of HARQ-ACKs through the HARQ-ACK codebook, wherein a mapping position of the ACK for the SCell Dormancy indication within the HARQ-ACK codebook can be determined based on a cell index of a first cell having a smallest cell index among the at least one cell for which the specific FDRA value is provided.

[0021] According to another aspect of the present disclosure, a base station includes a memory storing commands; and a processor performing operations by executing the commands, wherein the operations of the processor include: transmitting a DCI for scheduling a plurality of physical downlink shared channels (PDSCHs) on a plurality of cells; transmitting the plurality of PDSCHs on the plurality of cells; And receiving a HARQ-ACK codebook including a plurality of HARQ-ACKs (hybrid automatic repeat request-acknowledgements) for the plurality of PDSCHs, wherein the plurality of HARQ-ACKs are mapped in cell index order within the HARQ-ACK codebook, and (i) the DCI provides a specific FDRA (frequency domain resource allocation) value that is not a valid FDRA value for scheduling a PDSCH for at least one cell other than the plurality of cells, and (ii) the DCI provides information for a SCell (secondary cell) Dormancy indication, wherein the base station receives an ACK for the SCell Dormancy indication together with the plurality of HARQ-ACKs through the HARQ-ACK codebook, wherein a mapping position of the ACK for the SCell Dormancy indication within the HARQ-ACK codebook can be determined based on a cell index of a first cell having a smallest cell index among the at least one cell for which the specific FDRA value is provided.

[0022] According to at least one of various embodiments, wireless signal transmission and reception can be efficiently performed in a wireless communication system. For example, when a Scell ​​dormancy indication is indicated through a multi-cell scheduling DCI, a method for configuring a HARQ-ACK in response to the indication is defined, thereby resolving ambiguity and enabling more accurate and efficient Scell ​​dormancy indication.

[0023] The effects that can be obtained from the present disclosure are not limited to the effects mentioned above, and other effects not mentioned can be inferred from the description below.

[0024] Figure 1 illustrates physical channels used in a 3GPP system, which is an example of a wireless communication system, and a general signal transmission method using the channels.

[0025] Figure 2 illustrates the structure of a radio frame.

[0026] Figure 3 illustrates a resource grid of slots.

[0027] Figure 4 illustrates an example of physical channels being mapped within a slot.

[0028] Figure 5 illustrates the PDCCH / PDSCH reception and ACK / NACK transmission process.

[0029] Figure 6 illustrates a PUSCH (Physical Uplink Shared Channel) transmission process.

[0030] Figure 7 shows an example of carrier aggregation.

[0031] Figure 8 illustrates a wireless communication system supporting an unlicensed band.

[0032] FIG. 9 is a diagram for explaining HARQ-ACK codebook configurations according to one embodiment.

[0033] FIG. 10 is a diagram for explaining a method of transmitting and receiving a signal in a network system according to one embodiment.

[0034] FIG. 11 illustrates a flow of a method performed by a terminal according to one embodiment.

[0035] FIG. 12 illustrates a flow of a method performed by a base station according to one embodiment.

[0036] Figures 13 to 16 illustrate a communication system (1) and a wireless device applicable to the present disclosure.

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

[0038] As more and more communication devices demand greater communication capacity, the need for improved mobile broadband communications compared to existing Radio Access Technology (RAT) is emerging. Furthermore, massive Machine Type Communications (MTC), which connects multiple devices and objects to provide diverse services anytime, anywhere, is also a key issue to be considered in next-generation communications. Furthermore, communication system design that considers reliability and latency-sensitive services / terminals is being discussed. Accordingly, the introduction of next-generation RATs, such as enhanced Mobile BroadBand Communication (eMBB), massive MTC, and Ultra-Reliable and Low Latency Communication (URLLC), is being discussed. For convenience, these technologies are referred to as NR (New Radio or New RAT) in this specification.

[0039] For clarity of explanation, the description will focus on 3GPP NR, but the technical idea of ​​the present invention is not limited thereto.

[0040] In this specification, the expression "setting" can be replaced with the expression "configure / configuration", and the two can be used interchangeably. In addition, conditional expressions (e.g., "if", "in a case", or "when", etc.) can be replaced with the expression "based on that ~~" or "in a state / status". In addition, the operation of the terminal / base station or the SW / HW configuration according to the satisfaction of the condition can be inferred / understood. In addition, if the process of the receiving (or transmitting) side can be inferred / understood from the process of the transmitting (or receiving) side in signal transmission / reception between wireless communication devices (e.g., base stations, terminals), the description thereof can be omitted. For example, signal determination / generation / encoding / transmission, etc. of the transmitting side can be understood as signal monitoring reception / decoding / determination, etc. of the receiving side. In addition, the expression that the terminal performs (or does not perform) a specific operation can also be interpreted as meaning that the base station operates upon expecting / assuming (or expecting / assuming that the terminal does not perform) the specific operation. In addition, the expression that the base station performs (or does not perform) a specific operation can also be interpreted as meaning that the terminal operates upon expecting / assuming (or expecting / assuming that the base station does not perform) the specific operation. In addition, the division and index of each section, embodiment, example, option, method, plan, etc. in the following description are for the convenience of explanation and should not be interpreted as meaning that each constitutes an independent invention or that each must be implemented only individually. In addition, in describing each section, embodiment, example, option, method, plan, etc., if there is no explicitly conflicting / opposing description, it can be inferred / interpreted that at least some of them can be combined and implemented together, or at least some can be implemented with the omission of each.

[0041] In a wireless communication system, a terminal receives information from a base station via the downlink (DL) and transmits it to the base station via the uplink (UL). The 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 and purpose of the information being transmitted and received.

[0042] Figure 1 is a drawing for explaining physical channels used in a 3GPP NR system and a general signal transmission method using them.

[0043] When a terminal is powered on again from a powered-off state or enters a new cell, it performs an initial cell search operation, such as synchronizing with the 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). Based on the PSS / SSS, the terminal synchronizes with the base station and obtains information such as a cell ID (cell identity). In addition, the terminal can obtain broadcast information within the cell based on the PBCH. Meanwhile, the terminal can check the downlink channel status by receiving a Downlink Reference Signal (DL RS) during the initial cell search phase.

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

[0045] Thereafter, the terminal may perform a random access procedure such as steps S103 to S106 to complete connection to the base station. To this end, the terminal may transmit a preamble through a physical random access channel (PRACH) (S103) and receive 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, a contention resolution procedure such as transmission of an additional physical random access channel (S105) and reception of a physical downlink control channel and a corresponding physical downlink shared channel (S106) may be performed.

[0046] The terminal that has performed the procedure as described above can then perform the general uplink / downlink signal transmission procedure, such as receiving a physical downlink control channel / physical downlink shared channel (S107) and transmitting a physical uplink shared channel (PUSCH) / physical uplink control channel (PUCCH) (S108). The control information that the terminal transmits 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 through PUCCH, but can be transmitted through PUSCH when control information and traffic data must be transmitted simultaneously. Additionally, UCI can be transmitted aperiodically via PUSCH upon request / instruction from the network.

[0047] Meanwhile, the random access procedure (RACH procedure) is not limited to initial network access (e.g., S103 to S106) and can be used for various purposes. For example, the random access procedure can be used for at least one of, but not limited to, an 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. The terminal can acquire UL synchronization and / or UL transmission resources through the random access procedure.

[0048] Figure 2 illustrates the structure of a radio frame. In NR, uplink and downlink transmissions are organized into frames. Each radio frame is 10 ms long and is divided into two 5 ms half-frames (HF). Each half-frame is divided into five 1 ms sub-frames (SF). A sub-frame is divided into one or more slots, and the number of slots within a sub-frame depends on the subcarrier spacing (SCS). Each slot contains 12 or 14 OFDM (Orthogonal Frequency Division Multiplexing) symbols, depending on the cyclic prefix (CP). When a normal CP is used, each slot contains 14 OFDM symbols. When an extended CP is used, each slot contains 12 OFDM symbols.

[0049] Table 1 illustrates that when CP is normally used, the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary depending on the SCS.

[0050] SCS (15*2^u)Nslot symb N frame,u slot N subframe,u slot 15KHz (u=0)1410130KHz (u=1)1420260KHz (u=2)14404120KHz (u=3)14808240KHz (u=4)1416016

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

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

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

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

[0055] SCS (15*2^u)N slot symb N frame,u slot N subframe,u slot 60KHz (u=2)12404

[0056] The structure of the frame is only an example, and the number of subframes, number of slots, and number of symbols in the frame can be varied.

[0057] In an NR system, OFDM numerology (e.g., SCS) may be set differently between multiple cells that are merged into a single terminal. Accordingly, the (absolute time) interval of a time resource (e.g., SF, slot, or TTI) (conveniently referred to as TU (Time Unit)) consisting of the same number of symbols may be set differently between the merged cells. Here, the symbol may include an OFDM symbol (or CP-OFDM symbol), an SC-FDMA symbol (or Discrete Fourier Transform-spread-OFDM, DFT-s-OFDM symbol).

[0058] Figure 3 illustrates a resource grid of a slot. A slot contains multiple symbols in the time domain. For example, in the case of a regular CP, one slot contains 14 symbols, but in the case of an extended CP, one slot contains 12 symbols. A carrier contains multiple subcarriers in the frequency domain. A Resource Block (RB) is defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. A Bandwidth Part (BWP) is defined as multiple consecutive Physical RBs (PRBs) in the frequency domain and can correspond to a single numerology (e.g., SCS, CP length, etc.). A carrier can contain up to N (e.g., 5) BWPs. Data communication is performed through activated BWPs, and only one BWP can be activated for a single terminal. Each element in the resource grid is referred to as a Resource Element (RE), to which one complex symbol can be mapped.

[0059] Figure 4 illustrates an example of how physical channels are mapped within a slot. A PDCCH can be transmitted in the DL control region, and a PDSCH can be transmitted in the DL data region. A PUCCH can be transmitted in the UL control region, and a PUSCH can be transmitted in the UL data region. GP provides a time gap between the base station and the terminal when switching from transmission mode to reception mode or from reception mode to transmission mode. Some symbols within a subframe at the time of transition from DL to UL can be set as GP.

[0060] Below, each physical channel is described in more detail.

[0061] The PDCCH carries Downlink Control Information (DCI). For example, the PCCCH (i.e., DCI) carries the transmission format and resource allocation of the downlink shared channel (DL-SCH), resource allocation information for the uplink shared channel (UL-SCH), paging information for the paging channel (PCH), system information on the DL-SCH, resource allocation information for upper layer control messages such as random 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), which is masked / scrambled with various identifiers (e.g., Radio Network Temporary Identifier, RNTI) depending on the owner or usage of the PDCCH. For example, if the PDCCH is for a specific terminal, the CRC is masked with a terminal identifier (e.g., Cell-RNTI, C-RNTI). If the PDCCH is for paging, the CRC is masked with the Paging-RNTI (P-RNTI). If the PDCCH is for system information (e.g., a System Information Block, SIB), the CRC is masked with the System Information RNTI (SI-RNTI). If the PDCCH is for a random access response, the CRC is masked with the Random Access-RNTI (RA-RNTI).

[0062] The PDCCH consists of 1, 2, 4, 8, or 16 Control Channel Elements (CCEs) depending on the Aggregation Level (AL). A CCE is a logical allocation unit used to provide a PDCCH with a predetermined code rate depending on the radio channel status. A CCE consists of six Resource Element Groups (REGs). A REG is defined as one OFDM symbol and one (P)RB. The PDCCH is transmitted through a Control Resource Set (CORESET). A CORESET is defined as a set of REGs with a given numerology (e.g., SCS, CP length, etc.). Multiple CORESETs for a single UE can overlap in the time / frequency domain. A CORESET can be configured through system information (e.g., Master Information Block, MIB) or UE-specific upper layer (e.g., Radio Resource Control, RRC, layer) signaling. Specifically, the number of RBs and the number of OFDM symbols (up to 3) that constitute the CORESET can be set by upper layer signaling.

[0063] To receive / detect PDCCH, the UE monitors PDCCH candidates. PDCCH candidates represent the CCE(s) that the UE should monitor for PDCCH detection. Each PDCCH candidate is defined as 1, 2, 4, 8, or 16 CCEs depending on the AL. Monitoring involves (blind) decoding the PDCCH candidates. The set of PDCCH candidates that the UE 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 UE can acquire DCI by monitoring PDCCH candidates in one or more search spaces configured by the 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 can be defined based on the following parameters.

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

[0065] - monitoringSlotPeriodicityAndOffset: Indicates the PDCCH monitoring period (in slots) and the PDCCH monitoring interval offset (in slots).

[0066] - monitoringSymbolsWithinSlot: Indicates the PDCCH monitoring symbols within the slot (e.g., the first symbol(s) of the CORESET).

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

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

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

[0070] TypeSearch SpaceRNTIUse CaseType0-PDCCHCommonSI-RNTI on a primary cellSIB DecodingType0A-PDCCHCommonSI-RNTI on a primary cellSIB DecodingType1-PDCCHCommonRA-RNTI or TC-RNTI on a primary cellMsg2, Msg4 decoding in RACHType2-PDCCHCommonP-RNTI on a primary cellPaging DecodingType3-PDCCHCommonINT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, TPC-SRS-RNTI, C-RNTI, MCS-C-RNTI, or CS-RNTI(s)UE SpecificUE SpecificC-RNTI, or MCS-C-RNTI, or CS-RNTI(s)User specific PDSCH decoding

[0071] Table 4 illustrates DCI formats transmitted via PDCCH.

[0072] DCI formatUsage0_0Scheduling of PUSCH in one cell0_1Scheduling of one or multiple PUSCH in one cell, or indicating downlink feedback information for configured grant PUSCH (CG-DFI)0_2Scheduling of PUSCH in one cell1_0Scheduling of PDSCH in one cell1_1Scheduling of PDSCH in one cell, and / or triggering one shot HARQ-ACK codebook feedback1_2Scheduling of PDSCH in one cell2_0Notifying a group of UEs of the slot format, available RB sets, COT duration and search space set group switching2_1Notifying a group of UEs of the PRB(s) and OFDM symbol(s) where UE may assume no transmission is intended for the UE2_2Transmission of TPC commands for PUCCH and PUSCH2_3Transmission of a group of TPC commands for SRS transmissions by one or more UEs

[0073] DCI format 0_0 is used to schedule a TB-based (or TB-level) PUSCH, and DCI format 0_1 ​​can be used to schedule a TB-based (or TB-level) PUSCH or a CBG (Code Block Group)-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 can be used to schedule a TB-based (or TB-level) PDSCH or a CBG-based (or CBG-level) PDSCH (DL grant DCI). DCI format 0_0 / 0_1 may be referred to as UL grant DCI or UL scheduling information, and DCI format 1_0 / 1_1 may be referred to as DL grant DCI or DL ​​scheduling information. DCI format 2_0 is used to convey dynamic slot format information (e.g., dynamic SFI) to the terminal, and DCI format 2_1 is used to convey downlink pre-emption information to the terminal. DCI format 2_0 and / or DCI format 2_1 can be conveyed to the terminals within a group through the group common PDCCH, which is a PDCCH conveyed to the terminals defined as a group.

[0074] DCI format 0_0 and DCI format 1_0 may be referred to as fallback DCI formats, while DCI format 0_1 ​​and DCI format 1_1 may be referred to as non-fallback DCI formats. In the fallback DCI format, the DCI size / field configuration remains the same regardless of the terminal configuration. On the other hand, in the non-fallback DCI format, the DCI size / field configuration varies depending on the terminal configuration.

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

[0076] PUCCH carries Uplink Control Information (UCI). UCI includes:

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

[0078] - HARQ(Hybrid Automatic Repeat reQuest)-ACK(Acknowledgement): This is a response to a downlink data packet (e.g., codeword) on the PDSCH. It indicates whether the downlink data packet was successfully received. One HARQ-ACK bit can be transmitted in response to a single codeword, and two HARQ-ACK bits can be transmitted in response to two codewords. The HARQ-ACK response includes a positive ACK (simply, ACK), a negative ACK (NACK), a DTX, or a NACK / DTX. Here, HARQ-ACK is used interchangeably with HARQ ACK / NACK and ACK / NACK.

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

[0080] Table 5 illustrates PUCCH formats. Depending on the PUCCH transmission length, they can be classified into Short PUCCH (formats 0 and 2) and Long PUCCH (formats 1, 3, and 4).

[0081] PUCCH formatLength in OFDM symbolsN PUCCH symb Number of bitsUsageEtc01 - 2≤2HARQ, SRSequence selection14 - 14≤2HARQ, [SR]Sequence modulation21 - 2>2HARQ, CSI, [SR]CP-OFDM34 - 14>2HARQ, CSI, [SR]DFT-s-OFDM(no UE multiplexing)44 - 14>2HARQ, CSI, [SR]DFT-s-OFDM(Pre DFT OCC)

[0082] PUCCH format 0 carries UCI of up to 2 bits in size and is mapped and transmitted based on sequence. Specifically, the terminal transmits a specific UCI to the base station by transmitting one of multiple sequences through the PUCCH of PUCCH format 0. The terminal transmits the PUCCH of PUCCH format 0 within the PUCCH resources for the corresponding SR configuration only when transmitting a positive SR.

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

[0084] PUCCH format 2 carries UCI with a bit size greater than 2 bits, and modulation symbols are transmitted by frequency division multiplexing (FDM) with DMRS. DM-RSs are located at symbol indices #1, #4, #7, and #10 within a given resource block with a density of 1 / 3. Pseudo Noise (PN) sequences are used for DM_RS sequences. Frequency hopping can be enabled for 2-symbol PUCCH format 2.

[0085] PUCCH format 3 does not multiplex terminals within the same physical resource blocks and carries UCI with a bit size greater than 2 bits. In other words, PUCCH resources in PUCCH format 3 do not include orthogonal cover codes. Modulation symbols are transmitted through time division multiplexing (TDM) with DMRS.

[0086] PUCCH format 4 supports multiplexing of up to four terminals within the same physical resource blocks and carries UCI with a bit size greater than 2 bits. In other words, PUCCH resources in PUCCH format 3 include orthogonal cover codes. Modulation symbols are transmitted through time division multiplexing (TDM) with DMRS.

[0087] 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 CP-OFDM (Cyclic Prefix - Orthogonal Frequency Division Multiplexing) waveform or a DFT-s-OFDM (Discrete Fourier Transform - spread - Orthogonal Frequency Division Multiplexing) waveform. When the PUSCH is transmitted based on a DFT-s-OFDM waveform, the UE transmits the PUSCH by applying transform precoding. For example, when transform precoding is disabled (e.g., transform precoding is disabled), the UE transmits the PUSCH based on the CP-OFDM waveform, and when transform precoding is enabled (e.g., transform precoding is enabled), the UE can transmit the PUSCH based on the CP-OFDM waveform or the DFT-s-OFDM waveform. PUSCH transmissions can be dynamically scheduled by UL grants in 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 can be performed in a codebook-based or non-codebook-based manner.

[0088] Figure 5 illustrates the PDCCH / PDSCH reception and ACK / NACK transmission process. Referring to Figure 5, a terminal can detect a PDCCH in slot #n. Here, the PDCCH includes downlink scheduling information (e.g., DCI formats 1_0, 1_1), and the PDCCH indicates a DL assignment-to-PDSCH offset (K0) and a PDSCH-HARQ-ACK reporting offset (K1). For example, DCI formats 1_0, 1_1 can include the following information:

[0089] - Frequency domain resource assignment: Indicates the set of RBs allocated to the PDSCH.

[0090] - Time domain resource assignment: K0 (e.g., slot offset), indicates 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).

[0091] - PDSCH-to-HARQ_feedback timing indicator: Indicates K1

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

[0093] Afterwards, the terminal receives PDSCH from slot #(n+K0) according to the scheduling information of slot #n, and when reception of PDSCH is finished in slot #n1 (where, n+K0≤n1), UCI can be transmitted through PUCCH in slot #(n1+K1). Here, UCI may include HARQ-ACK response for PDSCH. In Fig. 5, for convenience, it is assumed that SCS for PDSCH and SCS for PUCCH are the same and slot # n1 = slot #n+K0, but the present invention is not limited thereto. If the SCSs are different, K1 can be indicated / interpreted based on the SCS of PUCCH.

[0094] When the PDSCH is configured to transmit at most 1 TB, the HARQ-ACK response may consist of 1 bit. When the PDSCH is configured to transmit at most 2 TB, the HARQ-ACK response may consist of 2 bits if spatial bundling is not configured, and may consist of 1 bit if spatial bundling is configured. When the HARQ-ACK transmission timing for multiple PDSCHs is designated as slot #(n+K1), the UCI transmitted in slot #(n+K1) includes HARQ-ACK responses for multiple PDSCHs.

[0095] Whether a UE should perform spatial bundling for a HARQ-ACK response can be configured (e.g., via RRC / higher layer signaling) for each cell group. For example, spatial bundling can be individually configured for each HARQ-ACK response transmitted over the PUCCH and / or each HARQ-ACK response transmitted over the PUSCH.

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

[0097] For example, assuming that a terminal receives a DCI scheduling 2 TB and receives 2 TB via PDSCH based on the DCI, the 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. Consequently, if both the first TB and the second TB are ACK, the terminal reports the ACK bit value to the base station, and if either TB is NACK, the terminal reports the NACK bit value to the base station.

[0098] For example, if only 1-TB is actually scheduled on a serving cell 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 bit value 1. Consequently, the terminal reports the A / N bit for the 1-TB to the base station as is.

[0099] A base station / terminal has multiple parallel DL HARQ processes for DL ​​transmission. These multiple parallel HARQ processes allow DL transmissions to be performed continuously while waiting for HARQ feedback regarding the success or failure of the previous DL transmission. Each HARQ process is associated with a HARQ buffer in the MAC (Medium Access Control) layer. Each DL HARQ process manages state variables such as the number of transmissions of MAC Physical Data Blocks (PDUs) in the buffer, HARQ feedback for MAC PDUs in the buffer, and the current redundancy version. Each HARQ process is identified by a HARQ process ID.

[0100] Meanwhile, HARQ-ACK codebooks are broadly defined as Type-1, Type-2, and Type-3 depending on the HARQ-ACK bit (payload) configuration method. For Type-1 codebooks, the HARQ-ACK payload is configured based on a combination of a candidate HARQ-ACK timing (K1) set and a candidate PDSCH occasion (SLIV) set (configured for each cell) (e.g., a codebook with a semi-statically fixed size based on RRC signaling). For Type-2 codebooks, the codebook size can be dynamically changed depending on the number of PDSCHs actually scheduled or the number of corresponding resource allocations (e.g., downlink assignment index, DAI). For Type-3 codebooks, the HARQ-ACK payload is configured by mapping the HARQ-ACK bits corresponding to each HARQ process number (HPN) according to the maximum number of HARQ processes (configured for each cell) (e.g., one-shot A / N reporting). Recently, the NR standard has added the Enhanced Type-3 codebook as a form of Type-3 codebook. The Enhanced Type-3 codebook is a method to report HARQ-ACK bits for a subset of cells indicated to the base station among all cells at once, rather than a method to report HARQ-ACK bits for all cells at once in order to reduce signaling overhead. Subsets of cells related to the Enhanced Type-3 codebook are set to the terminal through upper layer signaling of the Enhanced Type-3 codebook indexes, and one of the subsets (e.g., Enhanced Type-3 codebook index) set to the terminal can be indicated through DCI that triggers the Enhanced Type-3 codebook.The terminal can report HARQ-ACK for cells belonging to the indicated subset. Meanwhile, depending on the setting of the Enhanced Type-3 codebook indices, the Enhanced Type-3 codebook can be configured not only at the per-cell level but also at the per-HARQ process level. For example, the Enhanced Type-3 codebook index can be set on a per-HARQ process basis to support reporting the Type-3 codebook for some of the HARQ processes of the corresponding cell.

[0101] Specifically, in the case of a Type-1 codebook, a set of multiple (e.g., N) candidate K1 values ​​is set (for each Cell, for each Cell), and for each K1 value, a combination of all SLIVs that can be transmitted (or scheduled to be transmitted) in a DL slot preceding K1 slots from an A / N transmission slot is calculated, and an A / N sub-payload corresponding to the DL slot (including determining the A / N bit position / order corresponding to each SLIV that can be transmitted in the slot) is constructed (this is defined as "SLIV Pruning"), and these A / N sub-payloads are concatenated for N K1 values ​​to construct the entire A / N codebook. At this time, a set of (N) DL slots corresponding to each K1 value can be defined as a bundling window corresponding to the A / N transmission slot.

[0102] For Type-2 HARQ-ACK codebooks, a codebook for transmitting HARQ-ACK information on the same PUCCH / PUSCH is defined based on the counter DAI (downlink assignment indicator) (C-DAI) and total DAI (T-DAI) values ​​indicated in the actually transmitted PDCCH. In other words, the codebook is configured based on the PDCCH information actually transmitted to the terminal. If the terminal fails to detect a specific PDCCH, it transmits a NACK to the bit for the corresponding PDCCH among the bits defined in the codebook. At this time, the terminal can recognize whether PDCCH detection failed or not through the C-DAI and T-DAI values. C-DAI counts the accumulated number of {serving cell index, PDCCH monitoring occasion}-pairs for which PDSCH receptions are provided up to the current serving cell and the current PDCCH monitoring occasion. First, for multiple PDSCH receptions for the same {serving cell index, PDCCH monitoring occasion}-pair, the PDSCH that starts receiving first is counted first (a lower C-DAI value is assigned). Next, if there are multiple pairs with the same PDCCH monitoring occasion index among different {serving cell index, PDCCH monitoring occasion}-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 occasion}-pairs, the PDCCH monitoring occasion with the lower index is counted first.

[0103] For Type-3 codebook, specifically, one of the modes, Mode 1, which feeds back HARQ-ACK and corresponding NDI together, and Mode 2, which feeds back only HARQ-ACK without NDI, can be set from the BS to the UE. When set to Mode 1, the UE operates to feed back HARQ-ACK and corresponding NDI (indicated via DCI) for PDSCH reception of each HARQ Process Number (HPN) for each HPN. On the other hand, when set to Mode 2, the UE feeds back only HARQ-ACK for PDSCH reception of each HPN for each HPN.

[0104] Figure 6 illustrates a PUSCH transmission process. Referring to Figure 6, a terminal can detect a PDCCH in slot #n. Here, the PDCCH includes uplink scheduling information (e.g., DCI formats 0_0 and 0_1). DCI formats 0_0 and 0_1 can include the following information.

[0105] - Frequency domain resource assignment: Indicates the set of RBs allocated to PUSCH.

[0106] - Time domain resource assignment: Slot offset K2 indicates 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 can be indicated through SLIV (Start and Length Indicator Value) or can be indicated separately.

[0107] Thereafter, the terminal can transmit a PUSCH in slot #(n+K2) according to the scheduling information of slot #n. Here, the PUSCH includes a UL-SCH TB.

[0108] carrier aggreation

[0109] NR can support wider uplink / downlink bandwidth by merging multiple uplink / downlink carriers (i.e., carrier aggregation). Carrier aggregation enables the transmission / reception of signals on multiple carriers. When carrier aggregation is applied, each carrier (see Figure A2) can be referred to as a component carrier (CC). CCs can be adjacent or non-adjacent in the frequency domain. The bandwidth of each CC can be determined independently. Asymmetric carrier aggregation, where the number of UL CCs and DL CCs differs, is also possible.

[0110] - PCell (Primary Cell): For a terminal configured for carrier aggregation, this refers to the cell operating on the primary frequency (e.g., Primary Component Carrier, PCC) where the terminal performs the initial connection establishment procedure or initiates the connection re-establishment procedure. For DC (Dual Connectivity), this refers to the MCG (Master Cell Group) cell operating on the primary frequency where the terminal performs the initial connection establishment procedure or initiates the connection re-establishment procedure.

[0111] - SCell (Secondary Cell): For terminals with carrier aggregation configured, a cell that provides additional wireless resources in addition to the special cell.

[0112] - PSCell (Primary SCG Cell): In the case of DC, an SCG (Secondary Cell Group) cell to which a terminal performs random access when performing RRC reconfiguration and synchronization processes.

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

[0114] - Serving Cell (ServCell): Indicates a cell configured for a UE 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 represents a set of cells including special cell(s) and all SCells.

[0115] Meanwhile, control information can be configured to be transmitted and received only through specific cells. For example, UCI can be transmitted through a special cell (e.g., PCell). If a SCell (hereinafter, PUCCH-SCell) that allows PUCCH transmission is configured, UCI can also be transmitted through the PUCCH-SCell. As another example, the base station can allocate scheduling cells (sets) to reduce the complexity of PDCCH BD (blind decoding) at the terminal side. For PDSCH reception / PUSCH transmission, the terminal can perform PDCCH detection / decoding only in the scheduling cells. Furthermore, the base station can transmit the PDCCH only through the scheduling cells (sets). For example, a PDCCH for downlink allocation can be transmitted in cell #0 (i.e., the scheduling cell), and the corresponding PDSCH can be transmitted in cell #2 (i.e., the scheduled cell) (Cross-Carrier Scheduling, CCS). Scheduling cells (sets) can be configured in a terminal-specific, terminal-group-specific, or cell-specific manner. Scheduling cells include special cells (e.g., PCells).

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

[0117] - CIF disabled: CIF is absent in the PDCCH. The PDCCH on the scheduling cell allocates PDSCH / PUSCH resources on the same cell. In other words, the scheduling cell is identical to the scheduled cell.

[0118] - CIF enabled: CIF exists within the PDCCH. The PDCCH in scheduling can allocate PDSCH / PUSCH resources on one of multiple cells using CIF. The scheduling cell can be the same as or different from the scheduled cell. PDSCH / PUSCH means PDSCH or PUSCH.

[0119] Figure 7 is a diagram illustrating carrier aggregation. In Figure 7, it is assumed that three cells are aggregation. If CIF is disabled, each cell can only transmit the PDCCH that schedules its own PDSCH / PUSCH (self-carrier scheduling, SCS). On the other hand, if CIF is enabled by terminal-specific (or terminal-group-specific or cell-specific) upper layer signaling and cell A is configured as a scheduling cell, cell A can transmit not only the PDCCH that schedules cell A's PDSCH / PUSCH but also the PDCCH that schedules the PDSCH / PUSCH of another cell (i.e., the scheduled cell) (cross-carrier scheduling, CCS). In this case, cells B / C do not transmit the PDCCH that schedules their own cells.

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

[0121] Figure 8 illustrates 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 the carrier of the LCell is defined as a (DL / UL) LCC (Licensed Component Carrier). Furthermore, a cell operating in an unlicensed band (hereinafter, U-band) is defined as a UCell, and the carrier of the UCell is defined as a (DL / UL) UCC (Unlicensed Component Carrier). The carrier of a cell may refer to the operating frequency (e.g., center frequency) of the cell. Cells / carriers (e.g., component carriers, CC) may be collectively referred to as cells.

[0122] When carrier aggregation (CA) is supported, a single terminal can transmit and receive signals with a base station through multiple aggregated cells / carriers. When multiple CCs are configured for a single terminal, one CC can be configured as a PCC (Primary CC) and the remaining CCs can be configured as SCCs (Secondary CCs). Specific control information / channels (e.g., CSS PDCCH, PUCCH) can be configured to be transmitted and received only through the PCC. Data can be transmitted and received through the PCC / SCC. Figure 8(a) illustrates a case where 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 can be configured as a PCC and the UCC can be configured as an SCC. When multiple LCCs are configured for a terminal, one specific LCC can be configured as a PCC and the remaining LCCs can be configured as SCCs. Figure 8(a) corresponds to LAA of a 3GPP LTE system. Figure 8(b) illustrates a case where 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 can be configured as a PCC, and the remaining UCCs can be configured as SCCs. Accordingly, the NR UCell can support PUCCH, PUSCH, and PRACH transmissions. Both NSA and SA modes can be supported in the unlicensed bands of the 3GPP NR system.

[0123] HARQ-ACK feedback related to DCI that schedules multiple cells simultaneously

[0124] NR supports a wide spectrum across various frequency ranges. The availability of 5G Advanced spectrum is expected to increase through the re-farming of frequency bands used in previous generations. In particular, available spectrum blocks in the lower frequency bands (FR1) tend to be more segmented and distributed. In the FR2 band and some FR1 bands, available spectrum may be wider, necessitating multi-carrier / cell operation within the band. There is a need to improve throughput and coverage by utilizing these distributed spectrum bands or wider bandwidth spectrum in a more power-efficient and flexible manner.

[0125] When scheduling data across multiple cells, including intra-band and inter-band cells, it is important to increase flexibility and spectrum / power efficiency. However, in the current 5G NR scheduling scheme, a DCI can only schedule PUSCH / PDSCH for a single cell. However, future spectrum expansion / changes are expected to increase the need for simultaneous scheduling of multiple cells. To reduce the control overhead associated with scheduling, it is advantageous to schedule PUSCH / PDSCH for multiple cells through a single DCI.

[0126] In order to reduce the DCI overhead required for PDSCH / PUSCH scheduling in a future carrier aggregation (CA) situation where multiple cells are configured, a multi-cell scheduling method that simultaneously schedules multiple (serving) cells / CCs (through which PDSCH / PUSCH transmission is performed) with a single DCI in Rel-18 may be considered.

[0127] Accordingly, we propose an efficient HARQ-ACK (conveniently referred to as "A / N") feedback configuration and transmission operation method that takes into account a situation in which multiple PDSCHs on multiple cells are scheduled simultaneously based on a DCI (multi-cell DCI) that performs the above multi-cell scheduling. The part in this specification that mainly describes the multi-cell scheduling operation for PDSCH or PUSCH transmission may also be applied in the same way to the multi-cell scheduling for PUSCH or PDSCH transmission. In addition, a cell in this specification may mean an (active) BWP set / instructed for the corresponding cell.

[0128] Hereinafter, Multi-cell Scheduling DCI may be referred to as Multi-cell DCI or simply DCI, and may include at least one of DL grant DCI for scheduling PDSCH and UL grant DCI for scheduling PUSCH.

[0129] As mentioned above, unlike the existing single-cell (SC) scheduling method that schedules only PDSCHs on a single cell through a single DCI, the introduction of a multi-cell (MC) scheduling method that simultaneously schedules multiple PDSCHs on multiple cells through a single DCI is being considered.

[0130] In Rel. 16 NR, the Scell ​​dormancy indication was introduced to conserve UE power. UEs can save power by omitting PDCCH monitoring for Scells indicated as dormant. However, CSI / RRM measurements are still performed in the corresponding Scell. This Scell ​​dormancy indication is performed via DCI that does not schedule the PDSCH, and the UE transmits a 1-bit ACK in response to the Scell ​​dormancy indication.

[0131] The condition for providing Scell ​​dormancy indication through existing SC scheduling DCI (SC DCI) is "when one-shot HARQ-ACK request field is absent or its value is '0', HARQ-ACK retransmission indicator field is absent or its value is '0', and invalid value is indicated in FDRA field", and in this case, Scell ​​dormancy information (e.g., bitmap providing information about SCell group for which Scell ​​dormancy is indicated) can be indicated through a specific field combination (e.g., MCS (for TB 1), NDI, RV, HARQ process number (HPN), Antenna port(s) (AP), DMRS sequence initialization (DMRS) field).

[0132] Meanwhile, the conditions for providing Scell ​​dormancy indication through the MC scheduling DCI (MC DCI) may correspond to (i) "when there is no one-shot HARQ-ACK request field or its value is '0' and (ii) there is no HARQ-ACK retransmission indicator field or its value is '0' and the FDRA field is indicated with an invalid value for at least one cell (among the cells indicated with scheduling information through the MC DCI)." In this case, the Scell ​​dormancy information may be indicated through a specific field combination (e.g., MCS / NDI / RV / HPN and / or AP (and / or DMRS) fields (for TB 1)) corresponding to a cell (reference cell) having a smallest (or largest) cell index among the cells indicated with an invalid FDRA value.

[0133] Meanwhile, the fields configured within MC DCI can be considered as 1) Type-1A fields that configure only one common field for multiple cells and commonly apply the values ​​indicated through this to multiple cells, and 2) Type-2 fields that configure individual fields for each of multiple cells and individually apply the values ​​indicated by each field to the corresponding cells. In the above, MCS / NDI / RV / HPN are configured as Type-2 fields, DMRS is configured as Type-1A fields, and AP can be set to either Type-1A or Type-2.

[0134] In MC DCI, the FDRA field can be configured individually for each of multiple cells (Type-2 field), in which case the per-cell FDRA field can be referred to as an FDRA block. An invalid FDRA value can mean a value different from the FDRA value for PDSCH / PUSCH scheduling in the per-cell FDRA block (e.g., all 1s or all 0s). For the cell(s) indicated by the invalid FDRA value, there is no PDSCH / PUSCH scheduling, and the terminal / base station does not transmit or receive PDSCH / PUSCH in the corresponding cell(s).

[0135] Accordingly, if an invalid FDRA value is indicated only for some cells (among the cells for which scheduling information is indicated by the MC DCI above), the AP field (in addition to the MCS / NDI / RV / HPN field) may be used for Scell ​​dormancy indication purposes only when it is set to Type-2 (whereas it cannot be used for this purpose when the AP field is set to Type-1A), and in this case, the DMRS field may not be used.

[0136] Otherwise, if all cells (for which scheduling information is indicated by the MC DCI above) are indicated with invalid FDRA values, then the AP field (in addition to the MCS / NDI / RV / HPN field) can be used for Scell ​​dormancy indication purposes regardless of which Type it is set to (e.g., even when it is set to Type-1A), and in this case, the DMRS field can also be used.

[0137] The condition for triggering HARQ-ACK retransmission operation through existing SC DCI is "when the HARQ-ACK retransmission indicator field value is indicated as '1'", and in this case, slot offset information for determining the HARQ-ACK retransmission target slot can be indicated through a specific field (e.g., MCS field (for TB 1)).

[0138] Meanwhile, the condition for triggering the HARQ-ACK retransmission operation through the MC DCI may correspond to "when the HARQ-ACK retransmission indicator field value is '1' and the FDRA field is indicated with an invalid value for at least one cell (among the cells to which scheduling information is indicated through the MC DCI)", and in this case, the slot offset information for determining the HARQ-ACK retransmission target slot may be indicated through a specific field (e.g., the MCS field (for TB 1)) corresponding to the cell with the smallest (or largest) cell index among the cells to which the invalid FDRA value is indicated.

[0139] In another way, when the condition for triggering the HARQ-ACK retransmission operation through the MC DCI is defined as "when the HARQ-ACK retransmission indicator field value is indicated as '1'", and when the condition is met and an invalid FDRA value is indicated for at least one cell (among the cells indicated with scheduling information through the MC DCI), the slot offset information may be indicated through the MCS field (for TB 1) corresponding to the cell with the smallest (or largest) cell index among the cells indicated with the invalid FDRA value.

[0140] Otherwise, if the above conditions are met and there is no cell with an invalid FDRA value (i.e., all cells are indicated with valid FDRA values) among the cells (wherein valid FDRA values ​​are indicated), the slot offset information may be indicated through the MCS field (for TB 1) corresponding to the cell (for convenience, referred to as "cell A") having the largest (or smallest) cell index among all the cells (wherein valid FDRA values ​​are indicated), and in this case, the terminal may operate assuming / considering that there is no PDSCH scheduling for the corresponding cell A (for example, omitting PDSCH reception on the corresponding cell A and omitting or mapping the corresponding HARQ-ACK feedback to NACK).

[0141] When an Scell ​​dormancy indication and HARQ-ACK retransmission instruction are received through an existing SC DCI, the terminal operates to map an ACK for the corresponding DCI reception and transmit the configured HARQ-ACK feedback including the ACK to the base station.

[0142] Meanwhile, when a Cell dormancy indication and / or HARQ-ACK retransmission operation is indicated through the MC DCI (for example, through a specific field (combination) (such as an MCS field) corresponding to a specific reference cell (e.g., a cell with a specific (e.g., smallest (or largest) cell index) among cells indicated with an invalid FDRA value)), the MC DCI may perform PDSCH scheduling for one or more cells (indicated with a valid FDRA value) while indicating the operation, and accordingly, the HARQ-ACK payload corresponding to the MC DCI may be configured with multiple HARQ-ACK bits for multiple cells.

[0143] Therefore, in this case, rules for mapping / configuring HARQ-ACK feedback (e.g. ACK) to Scell ​​dormancy indication and HARQ-ACK retransmission indication via MC DCI may be required, and the following methods may be considered for this purpose.

[0144] In the following, HARQ-ACK payload may mean a HARQ-ACK payload (or sub-codebook) corresponding to one MC DCI in a specific (e.g. Type-2) HARQ-ACK codebook configuration situation, and its size may be determined based on the maximum number of cells that can be simultaneously scheduled through one MC DCI within one PUCCH (cell) group (if there is no cell configured with up to 2 TB transmission per PDSCH or spatial bundling for HARQ-ACK is configured) or the maximum number of TBs (if there is a cell configured with up to 2 TB transmission per PDSCH and spatial bundling for HARQ-ACK is not configured).

[0145] (1) Alt 1: When both HARQ-ACK bits corresponding to cells indicated with valid FDRA values ​​(via MC DCI) and cells indicated with invalid FDRA values ​​are configured (sequentially starting from MSB (Most Significant Bit) according to cell index order) in the HARQ-ACK payload.

[0146] The ACK for the above Scell ​​dormancy indication and HARQ-ACK retransmission (slot offset) indication can be mapped to the HARQ-ACK bit corresponding to a specific cell index (e.g., the reference cell) (TB 1 of the cell) associated with the MCS field in which the information is indicated.

[0147] If an invalid FDRA value is indicated for all cells (for which scheduling information is indicated by MC DCI), the ACK for the Scell ​​dormancy indication and HARQ-ACK retransmission (slot offset) indication can be mapped to the first MSB bit in the payload (if Alt 1 is applied).

[0148] (2) Alt 2: When only HARQ-ACK bits corresponding to cells indicated with valid FDRA values ​​(via MC DCI) are configured (sequentially starting from MSB according to cell index order) in the HARQ-ACK payload.

[0149] ACK for the above Scell ​​dormancy indication and HARQ-ACK retransmission (slot offset) indication may be mapped to the last LSB (Least Significant Bit) in the payload (Alt 2-1), or to (a single) bit located immediately after the bit(s) corresponding to a cell that is a valid FDRA (Alt 2-2), or to (repeatedly) all bit(s) located after the bit(s) corresponding to a cell that is a valid FDRA (Alt 2-3), or to the last LSB bit among the bit(s) corresponding to all cells (assuming that a valid FDRA value is indicated for all cells (for which scheduling information is indicated by MC DCI)) (Alt 2-4).

[0150] If an invalid FDRA value is indicated for all cells (for which scheduling information is indicated by MC DCI), the ACK for the Scell ​​dormancy indication and HARQ-ACK retransmission (slot offset) indication may be mapped to the last LSB bit in the payload (if Alt 2-1 is applied) or to the first MSB bit (if Alt 2-2 is applied) or to all bits in the payload (if Alt 2-3 is applied) repeatedly mapped or to the last LSB bit among the bit(s) corresponding to all cells (if Alt 2-4 is applied) assuming that valid FDRA values ​​are indicated for all cells.

[0151] (3) Alt 3: When only HARQ-ACK bits corresponding to cells indicated with valid FDRA values ​​(via MC DCI) are configured (sequentially starting from MSB according to cell index order) in the HARQ-ACK payload.

[0152] Referring to Fig. 9, we will examine the HARQ-ACK codebook configuration according to Alt 3. As shown in (a) of Fig. 9, it is assumed that among Cell #1, Cell #2, Cell #3, and Cell #4, PDSCH#1 is scheduled for Cell #1, an invalid FDRA value is indicated for Cell #2, PDSCH#2 is scheduled for Cell #3, and an invalid FDRA value is indicated for Cell #4 through multi-cell scheduling DCI.

[0153] Fig. 9 (b) shows the configuration of the HARQ-ACK codebook according to Alt 3 when the Scell ​​dormancy indication is not indicated through the multi-cell scheduling DCI. The HARQ-ACKs for Cell #1 and Cell #2, where PDSCH #1 and PDSCH #2 are scheduled respectively by indicating a valid FDRA value, can be included in the HARQ-ACK codebook, respectively. At this time, the HARQ-ACK for PDSCH #1 on Cell #1 with a lower cell index can be mapped first, and then the HARQ-ACK for PDSCH #2 on Cell #2 can be mapped. Meanwhile, when a maximum of 2 TB transmissions are set per PDSCH and spatial bundling is not set, the HARQ-ACK for the PDSCH of the corresponding cell is 2 bits (i.e., 1 bit of HARQ-ACK for each TB). In contrast, if a maximum of 1 TB transmission per PDSCH is configured, or if 2 TB is configured but spatial bundling is configured, the HARQ-ACK for the PDSCH of the corresponding cell is 1 bit. In addition, as described above, the size of the HARQ-ACK codebook can be determined based on the maximum number of cells that can be simultaneously scheduled through one MC DCI (if there is no cell configured with a maximum of 2 TB transmission per PDSCH or spatial bundling for HARQ-ACK is configured) or the maximum number of TBs (if there is a cell configured with a maximum of 2 TB transmission per PDSCH and spatial bundling for HARQ-ACK is not configured). If only HARQ-ACKs for cells indicated by valid FDRA are mapped in order of cell index in the HARQ-ACK codebook having the determined size in this way, bits left over without HARQ-ACKs being mapped at the back may be present in the HARQ-ACK codebook.In this way, the bits that are not mapped to HARQ-ACK can be set to 0. That is, the terminal can map only HARQ-ACKs for cells indicated by valid FDRA in order of cell index, and then perform 0 padding until the determined HARQ-ACK codebook size is reached. Since the value 0 is a HARQ-ACK bit value corresponding to NACK, this terminal operation can be understood as mapping NACKs for cells indicated by invalid FDRA. The terminal can perform an operation of mapping HARQ-ACKs for cells indicated by valid FDRA in order of cell index, and then mapping NACKs for cells indicated by invalid FDRA.

[0154] In exceptional cases where Scell ​​dormancy indication and / or HARQ-ACK retransmission (slot offset) are indicated through the MC DCI, the payload may be configured to include both HARQ-ACK bits corresponding to a cell with a valid FDRA and a cell indicated with an invalid FDRA value (or the reference cell among them), and mapping may be performed (to the HARQ-ACK bit corresponding to the reference cell) by applying the Alt 1 method for ACKs for the Scell ​​dormancy indication and HARQ-ACK retransmission (slot offset) indication. In other words, when an Scell ​​dormancy indication is indicated, Alt 1 can be applied exceptionally only for the reference cell having the smallest cell index among the cells indicated with an invalid FDRA, so that an ACK (HARQ-ACK for the Scell ​​dormancy indication) can be mapped. The ACK for such an Scell ​​dormancy indication can be mapped to the HARQ-ACK codebook together with the HARQ-ACK for the PDSCHs corresponding to the valid FDRA value, and the mapping order can follow the cell index. Fig. 9 (c) illustrates an example of the HARQ-ACK codebook configuration when an Scell ​​dormancy indication is indicated. Referring to Fig. 9 (c), among Cell #2 and Cell #4 indicated with an invalid FDRA value, Cell #2 has the smallest cell index, so Cell #2 becomes the reference cell. Therefore, the HARQ-ACK (i.e., ACK) for the Scell ​​dormancy indication is mapped to the location corresponding to Cell #2.Meanwhile, since the HARQ-ACK for the Scell ​​dormancy indication is a 1-bit ACK, not a NACK, the UE operation of mapping the ACK for Cell#2, a reference cell indicated by an invalid FDRA value, has the same result as if the UE correctly received / decoded one TB (e.g., TB1) of the PDSCH on Cell#2, a reference cell indicated by an invalid FDRA value. Therefore, when the Scell ​​dormancy indication is indicated, it can be expressed that the UE performs the operation of constructing the HARQ-ACK codebook as if it correctly received / decoded one TB (e.g., TB1) of the PDSCH on Cell#2, a reference cell indicated by an invalid FDRA value.

[0155] If an invalid FDRA value is indicated for all cells (for which scheduling information is indicated by MC DCI), the ACK for the Scell ​​dormancy indication and HARQ-ACK retransmission (slot offset) indication can be mapped to the first MSB bit in the payload (if Alt 3 is applied).

[0156] FIG. 10 is a diagram for explaining signal transmission and reception between a network and a terminal according to one embodiment.

[0157] Referring to FIG. 10, a terminal may receive at least one upper layer signaling (e.g., RRC) from a network (A05). The information provided via the upper layer signaling may include, but is not limited to, at least one of: information for configuring multiple cells in the terminal, configuration information related to multi-cell scheduling DCI in the terminal, and configuration information for a HARQ-ACK codebook. For convenience of explanation, it is assumed that a Type 2 HARQ-ACK codebook is configured in the terminal.

[0158] A terminal may receive DCI for multi-cell scheduling from a network (A10). The DCI for multi-cell scheduling may schedule multiple PDSCHs on multiple cells. The DCI for multi-cell scheduling may not include a Scell ​​dormancy indication field. The terminal may determine that Scell ​​dormancy is indicated through the multi-cell scheduling DCI based on the fact that in the multi-cell scheduling DCI that does not include the Scell ​​dormancy indication field, (i) the one-shot HARQ-ACK request field is not provided or has a value of 0, (ii) the HARQ-ACK retransmission indication field is not provided or has a value of 0, and an invalid FDRA value is set in the FDRA information for at least one cell. Upon determining that Scell ​​dormancy is indicated, the terminal can obtain information for Scell ​​dormancy (e.g., a bitmap indicating an Scell ​​group for Scell ​​dormancy) through MCS, RV, and NDI information for TB 1 of a reference cell having the smallest cell index among at least one cell indicated with an invalid FDRA value.

[0159] The terminal can receive PDSCH on each cell indicated by a valid FDRA value (A15).

[0160] The terminal can transmit a Type 2 HARQ-ACK codebook including HARQ-ACKs for received PDSCHs (A20). Within the Type 2 HARQ-ACK codebook, HARQ-ACKs for PDSCHs and ACKs for Scell ​​dormancy indications can be sequentially / consecutively mapped from the MSB in ascending order of cell index.

[0161] FIG. 11 illustrates a flow of a method performed by a terminal according to one embodiment.

[0162] Referring to FIG. 11, a terminal can receive DCI (downlink control information) for scheduling multiple PDSCHs (physical downlink shared channels) on multiple cells (B05).

[0163] The terminal can receive the plurality of PDSCHs on the plurality of cells based on the DCI (B10).

[0164] The terminal can transmit a HARQ-ACK codebook including multiple HARQ-ACKs (hybrid automatic repeat request-acknowledgement) for the multiple PDSCHs (B15_.

[0165] Within the above HARQ-ACK codebook, the plurality of HARQ-ACKs can be mapped in cell index order.

[0166] The terminal may map an ACK for the SCell Dormancy indication together with the plurality of HARQ-ACKs to the HARQ-ACK codebook based on (i) the DCI providing a specific FDRA (frequency domain resource allocation) value that is not a valid FDRA value for PDSCH scheduling for at least one cell other than the plurality of cells, and (ii) the DCI providing information for a SCell (secondary cell) Dormancy indication.

[0167] The mapping position of the ACK for the SCell Dormancy indication within the HARQ-ACK codebook may be determined based on the cell index of the first cell having the smallest cell index among the at least one cell for which the specific FDRA value is provided.

[0168] Within the HARQ-ACK codebook, the plurality of HARQ-ACKs and the ACK for the SCell Dormancy indication may be sorted in cell index order based on the cell indices of the plurality of cells and the cell index of the first cell.

[0169] Within the above HARQ-ACK codebook, the ACK for the SCell Dormancy indication can be mapped to a HARQ-ACK for one TB (transport block) of the first cell.

[0170] For the remaining cells, excluding the first cell, among the at least one cell for which the specific FDRA value is provided, ACK may not be mapped to the HARQ-ACK codebook.

[0171] In the DCI providing information for the SCell Dormancy indication, a one-shot HARQ-ACK request field may not be provided or may have a value of 0, a HARQ-ACK retransmission indication field may not be provided or may have a value of 0, and the specific FDRA value may be provided in the FDRA information of at least one cell.

[0172] Information for the SCell Dormancy indication may be provided through MCS (modulation and coding scheme) information, NDI (new data indicator) information, and RV (redundancy version) information for the first TB (transport block) of the first cell having the smallest cell index among the at least one cell for which the specific FDRA value is provided.

[0173] The above HARQ-ACK codebook may be a type-2 HARQ-ACK codebook.

[0174] The size of the above HARQ-ACK codebook may be determined based on at least one of the maximum number of cells that can be scheduled together through the DCI and the maximum number of TBs (transport blocks).

[0175] On at least one cell provided with the above specific FDRA value, the PDSCH may not be scheduled via the DCI.

[0176] FIG. 12 illustrates a flow of a method performed by a base station according to one embodiment.

[0177] Referring to FIG. 12, a base station can transmit DCI for scheduling multiple physical downlink shared channels (PDSCHs) on multiple cells (C05).

[0178] The base station can transmit the plurality of PDSCHs on the plurality of cells (C10).

[0179] The base station can receive a HARQ-ACK codebook including multiple HARQ-ACKs (hybrid automatic repeat request-acknowledgements) for the multiple PDSCHs (C15).

[0180] Within the above HARQ-ACK codebook, the plurality of HARQ-ACKs can be mapped in cell index order.

[0181] (i) the DCI provides a specific FDRA (frequency domain resource allocation) value that is not a valid FDRA value for scheduling a PDSCH for at least one cell other than the plurality of cells, and (ii) based on the DCI providing information for an SCell (secondary cell) Dormancy indication, the base station can receive an ACK for the SCell Dormancy indication together with the plurality of HARQ-ACKs through the HARQ-ACK codebook.

[0182] The mapping position of the ACK for the SCell Dormancy indication within the HARQ-ACK codebook may be determined based on the cell index of the first cell having the smallest cell index among the at least one cell for which the specific FDRA value is provided.

[0183] Within the HARQ-ACK codebook, the plurality of HARQ-ACKs and the ACK for the SCell Dormancy indication may be sorted in cell index order based on the cell indices of the plurality of cells and the cell index of the first cell.

[0184] Within the above HARQ-ACK codebook, the ACK for the SCell Dormancy indication can be mapped to a HARQ-ACK for one TB (transport block) of the first cell.

[0185] For the remaining cells, excluding the first cell, among the at least one cell for which the specific FDRA value is provided, ACK may not be mapped to the HARQ-ACK codebook.

[0186] In the DCI providing information for the SCell Dormancy indication, a one-shot HARQ-ACK request field may not be provided or may have a value of 0, a HARQ-ACK retransmission indication field may not be provided or may have a value of 0, and the specific FDRA value may be provided in the FDRA information of at least one cell.

[0187] Information for the SCell Dormancy indication may be provided through MCS (modulation and coding scheme) information, NDI (new data indicator) information, and RV (redundancy version) information for the first TB (transport block) of the first cell having the smallest cell index among the at least one cell for which the specific FDRA value is provided.

[0188] The above HARQ-ACK codebook may be a type-2 HARQ-ACK codebook.

[0189] The size of the above HARQ-ACK codebook may be determined based on at least one of the maximum number of cells that can be scheduled together through the DCI and the maximum number of TBs (transport blocks).

[0190] On at least one cell provided with the above specific FDRA value, the PDSCH may not be scheduled via the DCI.

[0191] Figure 13 illustrates a communication system (1).

[0192] Referring to FIG. 13, a communication system (1) includes a wireless device, a base station, and a network. Here, the wireless device refers to a device that performs communication using a wireless access technology (e.g., 5G NR (New RAT), LTE (Long Term Evolution)) and may be referred to as a communication / wireless / 5G device. Although not limited thereto, the wireless device may include a robot (100a), a vehicle (100b-1, 100b-2), an XR (eXtended Reality) device (100c), a hand-held device (100d), a home appliance (100e), an IoT (Internet of Things) device (100f), and an AI device / server (400). For example, the vehicle may include a vehicle equipped with a wireless communication function, an autonomous vehicle, a vehicle capable of performing vehicle-to-vehicle communication, etc. Here, the vehicle may include an Unmanned Aerial Vehicle (UAV) (e.g., a drone). XR devices include AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) devices, and can be implemented in the form of HMD (Head-Mounted Device), HUD (Head-Up Display) installed in a vehicle, television, smartphone, computer, wearable device, home appliance, digital signage, vehicle, robot, etc. Mobile devices can include smartphone, smart pad, wearable device (e.g., smart watch, smart glass), computer (e.g., laptop, etc.), etc. Home appliances can include TV, refrigerator, washing machine, etc. IoT devices can include sensors, smart meters, etc. For example, base stations and networks can also be implemented as wireless devices, and a specific wireless device (200a) can act as a base station / network node to other wireless devices.

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

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

[0195] Figure 14 illustrates a wireless device applicable to the present invention.

[0196] Referring to FIG. 14, the first wireless device (100) and the second wireless device (200) can transmit and receive wireless signals through various wireless access technologies (e.g., LTE, NR). Here, {the first wireless device (100), the second wireless device (200)} can correspond to {the wireless device (100x), the base station (200)} and / or {the wireless device (100x), the wireless device (100x)} of FIG. 13.

[0197] A first wireless device (100) includes one or more processors (102) and one or more memories (104), and may further include one or more transceivers (106) and / or one or more antennas (108). The processor (102) controls the memories (104) and / or the transceivers (106), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document. For example, the processor (102) may process information in the memory (104) to generate first information / signal, and then transmit a wireless signal including the first information / signal via the transceiver (106). In addition, the processor (102) may receive a wireless signal including second information / signal via the transceiver (106), and then store information obtained from signal processing of the second information / signal in the memory (104). The memory (104) may be connected to the processor (102) and may store various information related to the operation of the processor (102). For example, the memory (104) may perform some or all of the processes controlled by the processor (102), or may store software code including commands for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. Here, the processor (102) and the memory (104) may be part of a communication modem / circuit / chip designed to implement a wireless communication technology (e.g., LTE, NR). The transceiver (106) may be connected to the processor (102) and may transmit and / or receive wireless signals via one or more antennas (108). The transceiver (106) may include a transmitter and / or a receiver. The transceiver (106) may be used interchangeably with an RF (Radio Frequency) unit. In this specification, wireless device may also mean a communication modem / circuit / chip.

[0198] The second wireless device (200) includes one or more processors (202), one or more memories (204), and may further include one or more transceivers (206) and / or one or more antennas (208). The processor (202) controls the memories (204) and / or the transceivers (206), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document. For example, the processor (202) may process information in the memory (204) to generate third information / signals, and then transmit a wireless signal including the third information / signals via the transceivers (206). Furthermore, the processor (202) may receive a wireless signal including fourth information / signals via the transceivers (206), and then store information obtained from signal processing of the fourth information / signals in the memory (204). The memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, the memory (204) may perform some or all of the processes controlled by the processor (202), or may store software code including commands for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. Here, the processor (202) and the memory (204) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). The transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals via one or more antennas (208). The transceiver (206) may include a transmitter and / or a receiver. The transceiver (206) may be used interchangeably with an RF unit. In this specification, a wireless device may also mean a communication modem / circuit / chip.

[0199] Hereinafter, the hardware elements of the wireless device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP). 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, proposals, methods, and / or operation flowcharts disclosed in this document. One or more processors (102, 202) may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. One or more processors (102, 202) can generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data or information according to the functions, procedures, proposals and / or methods disclosed herein, and provide the signals to one or more transceivers (106, 206). One or more processors (102, 202) can receive signals (e.g., baseband signals) from one or more transceivers (106, 206) and obtain PDUs, SDUs, messages, control information, data or information according to the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein.

[0200] One or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. One or more processors (102, 202) may be implemented by hardware, firmware, software, or a combination thereof. For example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) may be included in one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. The descriptions, functions, procedures, suggestions, methods and / or operation flowcharts disclosed in this document may be implemented using firmware or software configured to perform one or more processors (102, 202) or stored in one or more memories (104, 204) and executed by one or more processors (102, 202). The descriptions, functions, procedures, suggestions, methods and / or operation flowcharts disclosed in this document may be implemented using firmware or software in the form of codes, instructions and / or sets of instructions.

[0201] One or more memories (104, 204) may be coupled to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. The one or more memories (104, 204) may be configured as 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 internally and / or externally 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 technologies, such as wired or wireless connections.

[0202] One or more transceivers (106, 206) can transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or flowcharts of this document, to one or more other devices. One or more transceivers (106, 206) can receive user data, control information, wireless signals / channels, etc., as mentioned in the descriptions, functions, procedures, proposals, methods and / or flowcharts of this document, from one or more other devices. For example, one or more transceivers (106, 206) can be connected to one or more processors (102, 202) and can transmit and receive wireless signals. For example, one or more processors (102, 202) can control one or more transceivers (106, 206) to transmit user data, control information, or wireless signals to one or more other devices. Additionally, 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. Additionally, one or more transceivers (106, 206) may be coupled to one or more antennas (108, 208), and one or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals / channels, or the like, as referred to in the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed herein, via one or more antennas (108, 208). In this document, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers (106, 206) can convert received user data, control information, wireless signals / channels, etc. from RF band signals to baseband signals in order to process the received user data, control information, wireless signals / channels, etc. using one or more processors (102, 202).One or more transceivers (106, 206) may convert user data, control information, wireless signals / channels, etc. processed by one or more processors (102, 202) from baseband signals to RF band signals. For this purpose, one or more transceivers (106, 206) may include an (analog) oscillator and / or filter.

[0203] Figure 15 illustrates another example of a wireless device applicable to the present disclosure. The wireless device may be implemented in various forms depending on the use case / service (see Figure 13).

[0204] Referring to FIG. 15, the wireless device (100, 200) corresponds to the wireless device (100, 200) of FIG. 14 and may be composed of various elements, components, units / units, and / or modules. For example, the wireless device (100, 200) may include a communication unit (110), a control unit (120), a memory unit (130), and an additional element (140). The communication unit may include a communication circuit (112) and a transceiver(s) (114). For example, the communication circuit (112) may include one or more processors (102, 202) and / or one or more memories (104, 204) of FIG. 14. For example, the transceiver(s) (114) may include one or more transceivers (106, 206) and / or one or more antennas (108, 208) of FIG. 14. The control unit (120) is electrically connected to the communication unit (110), the memory unit (130), and the additional elements (140) and controls the overall operation of the wireless device. For example, the control unit (120) may control the electrical / mechanical operation of the wireless device based on the program / code / command / information stored in the memory unit (130). In addition, the control unit (120) may transmit information stored in the memory unit (130) to an external device (e.g., another communication device) via a wireless / wired interface through the communication unit (110), or store information received from an external device (e.g., another communication device) via a wireless / wired interface in the memory unit (130).

[0205] The additional element (140) may be configured in various ways depending on the type of the wireless device. For example, the additional element (140) may include at least one of a power unit / battery, an input / output unit (I / O unit), a driving unit, and a computing unit. Although not limited thereto, the wireless device may be implemented in the form of a robot (Fig. 13, 100a), a vehicle (Fig. 13, 100b-1, 100b-2), an XR device (Fig. 13, 100c), a portable device (Fig. 13, 100d), a home appliance (Fig. 13, 100e), an IoT device (Fig. 13, 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 / environmental device, an AI server / device (Fig. 13, 400), a base station (Fig. 13, 200), a network node, etc. Wireless devices may be mobile or stationary depending on the use / service.

[0206] In FIG. 15, various elements, components, units / parts, and / or modules within the wireless device (100, 200) may be entirely interconnected via a wired interface, or at least some may be wirelessly connected via a communication unit (110). For example, within the wireless device (100, 200), the control unit (120) and the communication unit (110) may be wired, and the control unit (120) and a first unit (e.g., 130, 140) may be wirelessly connected via the communication unit (110). In addition, each element, component, unit / part, and / or module within the wireless device (100, 200) may further include one or more elements. For example, the control unit (120) may be composed of a set of one or more processors. For example, the control unit (120) may be composed of a set of a communication control processor, an application processor, an electronic control unit (ECU), a graphics processing processor, a memory control processor, etc. As another example, the memory unit (130) may be composed of RAM (Random Access Memory), DRAM (Dynamic RAM), ROM (Read Only Memory), flash memory, volatile memory, non-volatile memory, and / or a combination thereof.

[0207] Figure 16 illustrates a vehicle or autonomous vehicle applicable to the present disclosure. The vehicle or autonomous vehicle may be implemented as a mobile robot, a car, a train, a manned or unmanned aerial vehicle (AV), a ship, or the like.

[0208] Referring to FIG. 16, a vehicle or autonomous vehicle (100) may include an antenna unit (108), a communication unit (110), a control unit (120), a driving unit (140a), a power supply unit (140b), a sensor unit (140c), and an autonomous driving unit (140d). The antenna unit (108) may be configured as a part of the communication unit (110). Blocks 110 / 130 / 140a to 140d correspond to blocks 110 / 130 / 140 of FIG. 15, respectively.

[0209] The communication unit (110) can transmit and receive signals (e.g., data, control signals, etc.) with external devices such as other vehicles, base stations (e.g., base stations, road side units, etc.), and servers. The control unit (120) can control elements of the vehicle or autonomous vehicle (100) to perform various operations. The control unit (120) can include an ECU (Electronic Control Unit). The drive unit (140a) can drive the vehicle or autonomous vehicle (100) on the ground. The drive unit (140a) can include 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 can include a wired / wireless charging circuit, a battery, etc. The sensor unit (140c) can obtain vehicle status, surrounding environment information, user information, etc. The sensor unit (140c) may include an IMU (inertial measurement unit) sensor, a collision sensor, a wheel sensor, a speed sensor, an incline sensor, a weight detection sensor, a heading sensor, a position module, a vehicle forward / backward 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) may implement a technology for maintaining a driving lane, a technology for automatically controlling speed such as adaptive cruise control, a technology for automatically driving along a set path, a technology for automatically setting a path and driving when a destination is set, etc.

[0210] For example, the communication unit (110) can receive map data, traffic information data, etc. from an external server. The autonomous driving unit (140d) can generate an autonomous driving route and driving plan based on the acquired data. The control unit (120) can control the drive unit (140a) so that the vehicle or autonomous vehicle (100) moves along the autonomous driving route according to the driving plan (e.g., speed / direction control). During autonomous driving, the communication unit (110) can irregularly / periodically acquire the latest traffic information data from an external server and can acquire surrounding traffic information data from surrounding vehicles. In addition, during autonomous driving, the sensor unit (140c) can acquire vehicle status and surrounding environment information. The autonomous driving unit (140d) can update the autonomous driving route and driving plan based on newly acquired data / information. The communication unit (110) can transmit information regarding the vehicle location, autonomous driving route, driving plan, etc. to the external server. External servers can predict traffic information data in advance using AI technology or other technologies based on information collected from vehicles or autonomous vehicles, and provide the predicted traffic information data to the vehicles or autonomous vehicles.

[0211] The embodiments described above are combinations of components and features of the present invention in a predetermined form. Each component or feature should be considered optional unless explicitly stated otherwise. Each component or feature may be implemented without being combined with other components or features. Furthermore, it is also possible to form an embodiment of the present invention by combining some components and / or features. The order of operations described in the embodiments of the present invention may be changed. Some components or features of one embodiment may be included in another embodiment or may be replaced with corresponding components or features of another embodiment. It is self-evident that claims that do not have an explicit citation relationship in the patent claims may be combined to form an embodiment or may be incorporated as a new claim through a post-application amendment.

[0212] It will be apparent to those skilled in the art that the present invention can be embodied in other specific forms without departing from the scope of the invention. Therefore, the above detailed description should not be construed as limiting in any respect, but rather as illustrative. The scope of the present invention should be determined by a reasonable interpretation of the appended claims, and all modifications within the scope of equivalents of the present invention are intended to be included within the scope of the present invention.

[0213] The present disclosure may be used in a terminal, base station, or other equipment of a wireless mobile communication system.

Claims

1. In a method performed by a terminal, Receiving DCI (downlink control information) for scheduling multiple PDSCHs (physical downlink shared channels) on multiple cells; Receiving the plurality of PDSCHs on the plurality of cells based on the DCI; and Including transmitting a HARQ-ACK codebook including a plurality of HARQ-ACKs (hybrid automatic repeat request-acknowledgements) for the plurality of PDSCHs, Within the above HARQ-ACK codebook, the plurality of HARQ-ACKs are mapped in cell index order, (i) the DCI provides a specific FDRA (frequency domain resource allocation) value that is not a valid FDRA value for PDSCH scheduling for at least one cell other than the plurality of cells, and (ii) based on the DCI providing information for SCell (secondary cell) Dormancy indication, the terminal maps an ACK for the SCell Dormancy indication together with the plurality of HARQ-ACKs to the HARQ-ACK codebook, A method wherein the mapping position of the ACK for the SCell Dormancy indication within the HARQ-ACK codebook is determined based on the cell index of the first cell having the smallest cell index among the at least one cell for which the specific FDRA value is provided.

2. In paragraph 1, A method wherein the plurality of HARQ-ACKs and the ACK for the SCell Dormancy indication within the HARQ-ACK codebook are sorted in cell index order based on the cell indices of the plurality of cells and the cell index of the first cell.

3. In paragraph 1, A method in which an ACK for the SCell Dormancy indication within the HARQ-ACK codebook is mapped to a HARQ-ACK for one TB (transport block) of the first cell.

4. In paragraph 1, A method in which ACK is not mapped to the HARQ-ACK codebook for the remaining cells, excluding the first cell, among the at least one cell for which the specific FDRA value is provided.

5. In paragraph 1, In the above DCI providing information for the above SCell Dormancy instructions, The one-shot HARQ-ACK request field is not provided or has a value of 0, If the HARQ-ACK retransmission indication field is not provided or has a value of 0, A method wherein the specific FDRA value is set in the FDRA information of at least one cell.

6. In paragraph 1, Information for the above SCell Dormancy instructions is: A method in which the specific FDRA value is provided through MCS (modulation and coding scheme) information, NDI (new data indicator) information and RV (redundancy version) information for the first TB (transport block) of the first cell having the smallest cell index among the at least one cell.

7. In paragraph 1, The above HARQ-ACK codebook is a type-2 HARQ-ACK codebook.

8. In paragraph 1, A method wherein the size of the HARQ-ACK codebook is determined based on at least one of the maximum number of cells that can be scheduled together through the DCI and the maximum number of TBs (transport blocks).

9. In paragraph 1, A method in which a PDSCH is not scheduled via the DCI on at least one cell for which the specific FDRA value is provided.

10. A non-transitory computer-readable recording medium having recorded thereon commands configured to cause the terminal to perform the method described in claim 1 when executed by the processor of the terminal.

11. In the device, memory for storing commands; and A processor that performs operations by executing the above instructions, The operations of the above processor are: Receiving DCI (downlink control information) for scheduling multiple PDSCHs (physical downlink shared channels) on multiple cells; Receiving the plurality of PDSCHs on the plurality of cells based on the DCI; and Including transmitting a HARQ-ACK codebook including a plurality of HARQ-ACKs (hybrid automatic repeat request-acknowledgements) for the plurality of PDSCHs, Within the above HARQ-ACK codebook, the plurality of HARQ-ACKs are mapped in cell index order, (i) the DCI provides a specific FDRA (frequency domain resource allocation) value that is not a valid FDRA value for PDSCH scheduling for at least one cell other than the plurality of cells, and (ii) based on the DCI providing information for SCell (secondary cell) Dormancy indication, the device maps an ACK for the SCell Dormancy indication together with the plurality of HARQ-ACKs to the HARQ-ACK codebook, A device wherein the mapping position of the ACK for the SCell Dormancy indication within the HARQ-ACK codebook is determined based on the cell index of the first cell having the smallest cell index among the at least one cell for which the specific FDRA value is provided.

12. In paragraph 11, Including a transmitter and receiver, The above device is a terminal for wireless communication.

13. In paragraph 11, The above device is a processing device configured to control a terminal for wireless communication.

14. In a method performed by a base station, Transmitting DCI for scheduling multiple physical downlink shared channels (PDSCHs) on multiple cells; Transmitting the plurality of PDSCHs on the plurality of cells; and Including receiving a HARQ-ACK codebook including a plurality of HARQ-ACKs (hybrid automatic repeat request-acknowledgements) for the plurality of PDSCHs, Within the above HARQ-ACK codebook, the plurality of HARQ-ACKs are mapped in cell index order, (i) the DCI provides a specific FDRA (frequency domain resource allocation) value that is not a valid FDRA value for scheduling a PDSCH for at least one cell other than the plurality of cells, and (ii) based on the DCI providing information for an SCell (secondary cell) Dormancy indication, the base station receives an ACK for the SCell Dormancy indication together with the plurality of HARQ-ACKs through the HARQ-ACK codebook, A method wherein the mapping position of the ACK for the SCell Dormancy indication within the HARQ-ACK codebook is determined based on the cell index of the first cell having the smallest cell index among the at least one cell for which the specific FDRA value is provided.

15. At the base station, memory for storing commands; and A processor that performs operations by executing the above instructions, The operations of the above processor are: Transmitting DCI for scheduling multiple physical downlink shared channels (PDSCHs) on multiple cells; Transmitting the plurality of PDSCHs on the plurality of cells; and Including receiving a HARQ-ACK codebook including a plurality of HARQ-ACKs (hybrid automatic repeat request-acknowledgements) for the plurality of PDSCHs, Within the above HARQ-ACK codebook, the plurality of HARQ-ACKs are mapped in cell index order, (i) the DCI provides a specific FDRA (frequency domain resource allocation) value that is not a valid FDRA value for scheduling a PDSCH for at least one cell other than the plurality of cells, and (ii) based on the DCI providing information for an SCell (secondary cell) Dormancy indication, the base station receives an ACK for the SCell Dormancy indication together with the plurality of HARQ-ACKs through the HARQ-ACK codebook, A base station, wherein the mapping position of the ACK for the SCell Dormancy indication within the HARQ-ACK codebook is determined based on the cell index of the first cell having the smallest cell index among the at least one cell for which the specific FDRA value is provided.

Images