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

By supporting multi-cell scheduling and optimizing the bit count determination method of HARQ-ACK information in the wireless communication system, the problem of low signal transmission efficiency in multi-cell environment is solved, and more efficient signal processing and transmission is achieved.

CN119072892APending Publication Date: 2024-12-03LG ELECTRONICS INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380035687.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-05-08
Filing Date
2023-04-27
Publication Date
2024-12-03

AI Technical Summary

Technical Problem

The existing wireless communication systems have problems with inefficiency in multi-cell scheduling and HARQ-ACK information transmission, especially in the multi-cell scheduling, the number of confirmation/negation bits of HARQ-ACK information is not flexible enough, which affects the efficiency of signal transmission.

Method used

By supporting multi-cell scheduling in DCI, the number of ACK/NACK bits in the HARQ-ACK information is determined based on the maximum number of cells that can be jointly scheduled by DCI or the maximum number of TBs received, and the multi-cell DCI is used in the HARQ-ACK information. Indication information, including downlink assignment index (DAI), is used to optimize the arrangement and transmission of ACK/NACK bits.

Benefits of technology

The signal transmission efficiency of the wireless communication system in a multi-cell environment is improved, the HARQ-ACK information processing capability under multi-cell scheduling is enhanced, and the overall performance of the system is improved.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119072892A_ABST
    Figure CN119072892A_ABST
Patent Text Reader

Abstract

According to at least one of various embodiments, DCI may be received through a PDCCH; receiving at least one TB through a PDSCH in at least one of a plurality of cells configured in the terminal based on the DCI; and may transmit HARQ-ACK information for the at least one TB, in which the DCI may support multi-cell scheduling based on a plurality of cells, and the number of ACK / NACK bits included in the HARQ-ACK information may be determined based on at least one of a maximum number of cells that may be scheduled together by the DCI or a maximum number of TBs that may be received by cells that may be scheduled together by the DCI.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

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

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

[0003] Technical issues

[0004] An object of the present disclosure is to provide a method and apparatus for efficiently performing a wireless signal transmission / reception process.

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

[0006] Technical Solution

[0007] In one technical aspect of the present disclosure, a method for receiving a signal by a user equipment (UE) in a wireless communication system is provided, the method comprising the following steps: receiving downlink control information (DCI) through a physical downlink control channel (PDCCH); receiving at least one transport block (TB) through a physical downlink shared channel (PDSCH) on at least one of a plurality of cells configured in the UE based on the DCI; and sending hybrid automatic repeat request-acknowledgement (HARQ-ACK) information for at least one TB, wherein the DCI may support multi-cell scheduling based on a plurality of cells, and wherein the number of acknowledgment / negative acknowledgment (ACK / NACK) bits included in the HARQ-ACK information may be determined based on at least one of a maximum number of cells that may be co-scheduled by the DCI or a maximum number of TBs that may be received by cells co-scheduled by the DCI.

[0008] Based on the maximum number of TBs per PDSCH being 2 in at least one cell among the cells co-scheduled by DCI and no spatial bundling being configured, the number of ACK / NACK bits included in the HARQ-ACK information may be determined based on the maximum number of TBs that can be received by the cells co-scheduled by DCI.

[0009] Based on the maximum number of TBs per PDSCH in each cell that can be co-scheduled by DCI being 1 or based on spatial bundling being configured, the number of ACK / NACK bits included in the HARQ-ACK information can be determined based on the maximum number of cells that can be co-scheduled by DCI.

[0010] The maximum number of cells that can be jointly scheduled by the DCI may be related to a cell combination including a maximum number of cells among cell combinations that can be scheduled by the DCI.

[0011] In the HARQ-ACK information, ACK / NACK bits may be arranged based on the serving cell index of the co-scheduled cell.

[0012] The DCI may include information about a downlink assignment index (DAI). The DAI may be determined based on a cell having a minimum serving cell index among cells co-scheduled by the DCI.

[0013] HARQ-ACK information related to multi-cell scheduling may be included in the second subcodebook, and HARQ-ACK information related to single-cell scheduling may be included in the first subcodebook.

[0014] A HARQ-ACK codebook may be configured based on the concatenation of the first subcodebook and the second subcodebook. For example, the second subcodebook may be attached to the first subcodebook.

[0015] The second subcodebook may be related to a PDSCH scheduled by a multi-cell scheduling DCI having two or more actually scheduled cells. The first subcodebook may be related to a PDSCH scheduled by a multi-cell scheduling DCI having one actually scheduled cell and a single-cell scheduling DCI.

[0016] In another technical aspect of the present disclosure, a processor-readable recording medium is provided, on which a program is recorded to execute the above method.

[0017] In another technical aspect of the present disclosure, a user equipment for executing the above method is provided.

[0018] In another technical aspect of the present disclosure, a device for controlling a user equipment to execute the above method is provided.

[0019] In another technical aspect of the present disclosure, a method for sending a signal by a base station in a wireless communication system is provided, the method comprising the following steps: sending downlink control information (DCI) to a user equipment through a physical downlink control channel (PDCCH); sending at least one transport block (TB) through a physical downlink shared channel (PDSCH) on at least one of a plurality of cells configured in the user equipment based on the DCI; and receiving hybrid automatic repeat request-acknowledgement (HARQ-ACK) information for at least one TB, wherein the DCI may support multi-cell scheduling based on a plurality of cells, and wherein the number of acknowledgment / negative acknowledgment (ACK / NACK) bits included in the HARQ-ACK information may be determined based on at least one of the maximum number of cells that may be co-scheduled by the DCI or the maximum number of TBs that may be sent by the cells co-scheduled by the DCI.

[0020] In another technical aspect of the present disclosure, a base station for executing the above method is provided.

[0021] Beneficial Effects

[0022] According to the present disclosure, wireless signal transmission and reception can be efficiently performed in a wireless communication system.

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

[0024] Figure 1 Physical channels used in a 3rd Generation Partnership Project (3GPP) system as an exemplary wireless communication system and a general signal transmission method using the same are shown.

[0025] Figure 2 Shows the radio frame structure.

[0026] Figure 3 A resource grid showing time slots.

[0027] Figure 4 An exemplary mapping of physical channels in time slots is shown.

[0028] Figure 5 An exemplary PDCCH / PDSCH reception and acknowledgement / negative acknowledgement (ACK / NACK) transmission process is shown.

[0029] Figure 6 An exemplary physical uplink shared channel (PUSCH) transmission process is shown.

[0030] Figure 7 An example of carrier aggregation is shown.

[0031] Figure 8 An exemplary wireless communication system supporting an unlicensed frequency band is shown.

[0032] Fig. 9 A method of occupying resources in an unlicensed band is shown.

[0033] Fig.10 An example of determining the number of A / N BPS bits is shown.

[0034] Fig.11 An example of cells co-scheduled by DCI is shown.

[0035] Fig.12 An example of A / N bit alignment is shown.

[0036] Fig.13 is a diagram for describing a method for a user equipment to receive a signal according to an embodiment;

[0037] Fig.14 is a diagram illustrating a method of transmitting a signal by a base station according to an embodiment.

[0038] Figures 15 to 18 A communication system 1 and a wireless device suitable for use with the present disclosure are shown.

[0039] Fig.19 A discontinuous reception (DRX) operation suitable for the present disclosure is shown. DETAILED DESCRIPTION

[0040] Embodiments of the present disclosure are applicable to various wireless access technologies such as 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). CDMA can be implemented as a radio technology such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented as a radio technology such as Global System for Mobile Communications (GSM) / General Packet Radio Service (GPRS) / Enhanced Data Rates for GSM Evolution (EDGE). OFDMA can be implemented as a radio technology such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wireless Fidelity (Wi-Fi)), IEEE 802.16 (Worldwide Interoperability for Microwave Access (WiMAX)), IEEE 802.20, and Evolved UTRA (E-UTRA). UTRA is part of Universal Mobile Telecommunications System (UMTS). 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is a part of Evolved UMTS (E-UMTS) using E-UTRA, and LTE-Advanced (A) 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.

[0041] As more and more communication devices require greater communication capacity, enhanced mobile broadband communications relative to traditional radio access technologies (RATs) are needed. In addition, large-scale machine-type communications (MTC), which can provide various services anytime and anywhere by connecting multiple devices and objects, is another important issue to be considered for next-generation communications. Discussions are also underway to design communication systems that take into account services / UEs that are sensitive to reliability and latency. Therefore, discussions are underway to introduce new radio access technologies that take into account enhanced mobile broadband communications (eMBB), massive MTC, and ultra-reliable low-latency communications (URLLC). In this disclosure, for simplicity, this technology will be referred to as NR (new radio or new RAT).

[0042] For the sake of brevity, 3GPP NR is mainly described, but the technical concept of the present disclosure is not limited thereto.

[0043] In the present disclosure, the term "setting" may be replaced by "configuration", and the two may be used interchangeably. In addition, conditional expressions (e.g., "if", "in the case of..." or "when") may be replaced by "based on..." or "under the state of...". In addition, the operation or software / hardware (SW / HW) configuration of the user equipment (UE) / base station (BS) may be derived / understood based on satisfying the corresponding conditions. When the processing of the receiving (or transmitting) side can be derived / understood from the processing of the transmitting (or receiving) side in the signal transmission / reception between the wireless communication device (e.g., BS and UE), its description may be omitted. For example, the signal determination / generation / encoding / transmission of the transmitting side may be understood as the signal monitoring reception / decoding / determination of the receiving side. In addition, when it is said that the UE performs (or does not perform) a specific operation, this may also be interpreted as the BS expecting / assuming (or not expecting / assuming) that the UE performs the specific operation. When it is said that the BS performs (or does not perform) a specific operation, this may also be interpreted as the UE expecting / assuming (or not expecting / assuming) that the BS performs the specific operation. In the following description, for the convenience of description, sections, implementations, examples, options, methods, schemes, etc. are distinguished and indexed from each other, which does not mean that each of them must constitute an independent disclosure or that each of them should only be implemented separately. Unless explicitly contradicted, it can be deduced / understood that at least some sections, implementations, examples, options, methods, schemes, etc. can be implemented in combination or can be omitted.

[0044] In a wireless communication system, a user equipment (UE) receives information from a base station (BS) through a downlink (DL) and transmits information to the BS through an uplink (UL). The information transmitted and received by the BS and the UE includes data and various control information, and includes various physical channels according to the type / purpose of the information transmitted and received by the UE and the BS.

[0045] Figure 1 Physical channels used in the 3GPP NR system and a general signal transmission method using the same are shown.

[0046] When the UE is powered on again from a power-off state or enters a new cell, in step S101, the UE performs an initial cell search process (e.g., establishes synchronization with the BS). To this end, the UE receives a synchronization signal block (SSB) from the BS. The SSB includes a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast channel (PBCH). The UE establishes synchronization with the BS based on the PSS / SSS and obtains information such as a cell identity (ID). The UE can obtain broadcast information in the cell based on the PBCH. The UE can receive a DL reference signal (RS) during the initial cell search process to monitor the DL channel status.

[0047] After the initial cell search, the UE may acquire more specific system information by receiving a physical downlink control channel (PDCCH) and receiving a physical downlink shared channel (PDSCH) based on information of the PDCCH in step S102.

[0048] The UE may perform a random access procedure to access the BS in steps S103 to S106. For random access, the UE may send a preamble to the BS on a physical random access channel (PRACH) (S103) and receive a response message to the preamble on a PDCCH and a PDSCH corresponding to the PDCCH (S104). In the case of contention-based random access, the UE may perform a contention resolution procedure by further sending a PRACH (S105) and receiving a PDCCH and a PDSCH corresponding to the PDCCH (S106).

[0049] After the foregoing process, the UE may receive PDCCH / PDSCH (S107) and send a physical uplink shared channel (PUSCH) / physical uplink control channel (PUCCH) (S108) as a general downlink / uplink signal transmission process. The control information sent from the UE to the BS is called uplink control information (UCI). UCI includes hybrid automatic repeat and request confirmation / negative determination (HARQ-ACK / NACK), scheduling request (SR), channel state information (CSI), etc. CSI includes channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), etc. Although UCI is usually sent on PUCCH, UCI may be sent on PUSCH when control information and business data need to be sent simultaneously. In addition, UCI may be sent aperiodically via PUSCH according to the request / command of the network.

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

[0051] Figure 2The radio frame structure is shown. In NR, uplink transmission and downlink transmission are configured in frames. Each radio frame has a length of 10ms and is divided into two 5ms half frames (HF). Each half frame is divided into five 1ms subframes (SF). A subframe is divided into one or more time slots, and the number of time slots in a subframe depends on the subcarrier spacing (SCS). Depending on the cyclic prefix (CP), each time slot includes 12 or 14 orthogonal frequency division multiplexing (OFDM) symbols. When a normal CP is used, each time slot includes 14 OFDM symbols. When an extended CP is used, each time slot includes 12 OFDM symbols.

[0052] Table 1 exemplarily shows that the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary according to the SCS when a normal CP is used.

[0053] [Table 1]

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

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

[0056] *N frame,u slot : Number of time slots in a frame

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

[0058] Table 2 shows that the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary according to the SCS when the extended CP is used.

[0059] [Table 2]

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

[0061] The structure of the frame is only an example. The number of subframes, the number of time slots, and the number of symbols in a frame may vary.

[0062] In the NR system, OFDM parameter sets (e.g., SCS) may be configured differently for multiple cells aggregated for one UE. Therefore, the (absolute time) duration of a time resource (e.g., SF, time slot, or TTI) (referred to as a time unit (TU) for simplicity) consisting of the same number of symbols may be configured differently between aggregated cells. Here, the symbol may include an OFDM symbol (or CP-OFDM symbol) and an SC-FDMA symbol (or a discrete Fourier transform-spread-OFDM (DFT-s-OFDM) symbol).

[0063] Figure 3A resource grid showing a time slot. A time slot includes multiple symbols in the time domain. For example, when a normal CP is used, a time slot includes 14 symbols. However, when an extended CP is used, a time slot includes 12 symbols. A carrier includes multiple subcarriers in the frequency domain. A resource block (RB) is defined as a plurality of consecutive subcarriers (e.g., 12 consecutive subcarriers) in the frequency domain. A bandwidth part (BWP) may be defined as a plurality of consecutive physical RBs (PRBs) in the frequency domain and corresponds to a single parameter set (e.g., SCS, CP length, etc.). A carrier may include up to N (e.g., five) BWPs. Data communication may be performed via enabled BWPs, and only one BWP may be enabled for a UE. In a resource grid, each element is referred to as a resource element (RE), and a complex symbol may be mapped to each RE.

[0064] Figure 4 An exemplary mapping of physical channels in a time slot is shown. PDCCH may be sent in the DL control region, and PDSCH may be sent in the DL data region. PUCCH may be sent in the UL control region, and PUSCH may be sent in the UL data region. A guard period (GP) provides a time gap for a transmission mode to a reception mode switch or a reception mode to a transmission mode switch at the BS and the UE. Some symbols in a subframe at the time of a DL to UL switch may be configured as a GP.

[0065] The individual physical channels are described in more detail below.

[0066] PDCCH transmits DCI. For example, PDCCH (i.e., DCI) may carry information about the transmission format and resource allocation of the DL shared channel (DL-SCH), resource allocation information of the uplink shared channel (UL-SCH), paging information about the paging channel (PCH), system information about DL-SCH, information about resource allocation of high-level control messages (e.g., RAR sent on PDSCH), transmit power control commands, information about the activation / release of the configured scheduling, etc. DCI includes a cyclic redundancy check (CRC). The CRC is masked using various identifiers (IDs) (e.g., radio network temporary identifier (RNTI)) according to the owner or purpose of the PDCCH. For example, if the PDCCH is used for a specific UE, the CRC is masked by the UE ID (e.g., cell-RNTI (C-RNTI)). If the PDCCH is used for a paging message, the CRC is masked by the paging-RNTI (P-RNTI). If the PDCCH is for system information (eg, system information block (SIB)), the CRC is masked by a system information RNTI (SI-RNTI). When the PDCCH is for RAR, the CRC is masked by a random access-RNTI (RA-RNTI).

[0067] The PDCCH includes 1, 2, 4, 8 or 16 control channel elements (CCEs) depending on its aggregation level (AL). CCE is a logical allocation unit for providing a specific code rate to the PDCCH according to the radio channel state. CCE includes 6 resource element groups (REGs), each REG being defined by one OFDM symbol × one (P)RB. The PDCCH is transmitted in a control resource set (CORESET). A CORESET is defined as a set of REGs with a given set of parameters (e.g., SCS, CP length, etc.). Multiple CORESETs for one UE may overlap with each other in the time / frequency domain. The CORESET may be configured by system information (e.g., master information block (MIB)) or UE-specific high-level signaling (e.g., radio resource control (RRC) signaling). Specifically, the number of RBs and the number of symbols (up to 3) in a CORESET may be configured by high-level signaling.

[0068] For PDCCH reception / detection, the UE monitors PDCCH candidates. PDCCH candidates are CCEs that the UE should monitor to detect PDCCH. Each PDCCH candidate is defined as 1, 2, 4, 8 or 16 CCEs according to the AL. Monitoring includes (blind) decoding of the PDCCH candidates. The set of PDCCH candidates decoded by the UE is defined as the PDCCH search space (SS). The SS can be a common search space (CSS) or a UE-specific search space (USS). The UE can obtain DCI by monitoring PDCCH candidates in one or more SSs configured by MIB or high-level signaling. Each CORESET is associated with one or more SSs, and each SS is associated with a CORESET. The SS can be defined based on the following parameters.

[0069] -controlResourceSetId: CORESET related to SS

[0070] -monitoringSlotPeriodicityAndOffset: PDCCH monitoring periodicity (time slot) and PDCCH monitoring offset (time slot)

[0071] -monitoringSymbolsWithinSlot: PDCCH monitoring symbols in the slot (e.g., the first symbol of CORESET)

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

[0073] *The timing (eg, time / frequency resources) at which the UE is to monitor a PDCCH candidate is defined as a PDCCH (monitoring) timing. One or more PDCCH (monitoring) timings may be configured in a time slot.

[0074] Table 3 shows the characteristics of each SS.

[0075] [Table 3]

[0076]

[0077] Table 4 shows the DCI format transmitted on the PDCCH.

[0078] [Table 4]

[0079]

[0080] DCI format 0_0 can be used to schedule TB-based (or TB-level) PUSCH, and DCI format 0_1 ​​can be used to schedule TB-based (or TB-level) PUSCH or code block group (CBG)-based (or CBG-level) PUSCH. DCI format 1_0 can be used to schedule TB-based (or TB-level) PDSCH, and DCI format 1_1 can be used to schedule TB-based (or TB-level) PDSCH or CBG-based (or CBG-level) PDSCH (or DL ​​grant DCI). DCI format 0_0 / 0_1 can be called UL grant DCI or UL scheduling information, and DCI format 1_0 / 1_1 can be called DL grant DCI or DL ​​scheduling information. DCI format 2_0 is used to transmit dynamic slot format information (e.g., dynamic slot format indicator (SFI)) to the UE, and DCI format 2_1 is used to transmit DL preemption information to the UE. DCI format 2_0 and / or DCI format 2_1 can be transmitted to a corresponding group of UEs on a group common PDCCH (a PDCCH pointing to a group of UEs).

[0081] 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. Under the fallback DCI format, the DCI size / field configuration remains the same regardless of the UE configuration. In contrast, under the non-fallback DCI format, the DCI size / field configuration varies according to the UE configuration.

[0082] PDSCH transmits DL data (e.g., DL shared channel transport block (DL-SCH TB)) and uses modulation schemes such as quadrature phase shift keying (QPSK), 16-ary quadrature amplitude modulation (16QAM), 64QAM, or 256QAM. TB is encoded as a codeword. PDSCH can transmit up to two codewords. Scrambling and modulation mapping can be performed on the basis of the codeword, and the modulation symbols generated from each codeword can be mapped to one or more layers. Each layer is mapped to a resource together with a demodulation reference signal (DMRS), and an OFDM symbol signal is generated from the layer mapped with the DMRS and sent through the corresponding antenna port.

[0083] PUCCH transmits uplink control information (UCI). UCI includes the following information.

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

[0085] -HARQ (Hybrid Automatic Repeat Request) -ACK (Acknowledgement): A response to a DL data packet (e.g., a codeword) on the PDSCH. HARQ-ACK indicates whether the DL data packet was successfully received. In response to a single codeword, a 1-bit HARQ-ACK may be sent. In response to two codewords, a 2-bit HARQ-ACK may be sent. HARQ-ACK responses include positive ACK (abbreviated as ACK), negative ACK (NACK), discontinuous transmission (DTX), or NACK / DTX. The term HARQ-ACK may be used interchangeably with HARQ ACK / NACK and ACK / NACK.

[0086] -CSI (Channel State Information): Feedback information of DL channels. Multiple Input Multiple Output (MIMO) related feedback information includes RI and PMI.

[0087] Table 5 shows an exemplary PUCCH format. Based on PUCCH transmission duration, the PUCCH format may be divided into short PUCCH (formats 0 and 2) and long PUCCH (formats 1, 3, and 4).

[0088] [Table 5]

[0089]

[0090] PUCCH format 0 transmits up to 2 bits of UCI and is mapped in a sequence-based manner for easy transmission. Specifically, the UE sends a specific UCI to the BS by sending one of multiple sequences on the PUCCH of PUCCH format 0. The UE sends the PUCCH of PUCCH format 0 in the PUCCH resources configured for the corresponding SR only when the UE sends a positive SR.

[0091] PUCCH format 1 transmits up to 2 bits of UCI, and the modulation symbol of UCI is spread in the time domain with an orthogonal cover code (OCC) (configured differently depending on whether frequency hopping is performed). DMRS is transmitted in symbols where modulation symbols are not transmitted (ie, transmitted in time division multiplexing (TDM)).

[0092] PUCCH format 2 transmits more than 2 bits of UCI, and the modulation symbols of DCI are sent with frequency division multiplexing (FDM) using DMRS. DMRS are located in symbols #1, #4, #7, and #10 of a given RB at a density of 1 / 3. Pseudo-noise (PN) sequences are used for DMRS sequences. For 2-symbol PUCCH format 2, frequency hopping can be enabled.

[0093] PUCCH format 3 does not support UE multiplexing in the same PRBS and transmits UCI of more than 2 bits. In other words, the PUCCH resource of PUCCH format 3 does not include OCC. The modulation symbols are transmitted in TDM using DMRS.

[0094] PUCCH format 4 supports multiplexing of up to 4 UEs in the same PRBS and transmits UCI of more than 2 bits. In other words, the PUCCH resource of PUCCH format 3 includes OCC. The modulation symbol is transmitted in TDM using DMRS.

[0095] The PUSCH transmits UL data (e.g., UL shared channel transport block (UL-SCHTB)) and / or UCI based on a CP-OFDM waveform or a DFT-s-OFDM waveform. When the PUSCH is sent with a DFT-s-OFDM waveform, the UE sends the PUSCH with transform precoding. For example, when transform precoding is not possible (e.g., disabled), the UE may send the PUSCH with a CP-OFDM waveform, and when transform precoding is possible (e.g., enabled), the UE may send the PUSCH with a CP-OFDM or DFT-s-OFDM waveform. PUSCH transmission may be dynamically scheduled by a UL grant in the DCI, or semi-statically scheduled by higher layer (e.g., RRC) signaling (and / or layer 1 (L1) signaling such as PDCCH) (configured scheduling or configured grant). PUSCH transmission may be performed in a codebook-based or non-codebook-based manner.

[0096] Figure 5 An exemplary PDCCH / PDSCH reception and ACK / NACK transmission process is shown. Figure 5, the UE may detect the PDCCH in slot #n. The PDCCH includes DL scheduling information (e.g., DCI format 1_0 or DCI format 1_1). The PDCCH indicates DL assignment with PDSCH offset K0 and PDSCH with HARQ-ACK report offset K1. For example, DCI format 1_0 and DCI format 1_1 may include the following information.

[0097] - Frequency domain resource assignment: indicates the set of RBs assigned to PDSCH

[0098] - Time domain resource assignment: indicates K0 and the starting position (eg, OFDM symbol index) and length (eg, number of OFDM symbols) of the PDSCH in the slot.

[0099] -PDSCH-to-HARQ_feedback timing indicator: indicates K1.

[0100] -HARQ process number (4 bits): indicates the HARQ process ID of the data (eg, PDSCH or TB).

[0101] After receiving PDSCH in slot #(n+K0) according to the scheduling information of slot #n, the UE may send UCI on PUCCH in slot #(n+K1). UCI may include a HARQ-ACK response to PDSCH. For convenience, Figure 5 Based on the assumption that the SCS of PDSCH is equal to the SCS of PUCCH and slot #n1=slot #(n+K0), this should not be construed as limiting the present disclosure. When the SCSs are different, K1 may be indicated / interpreted based on the SCS of PUCCH.

[0102] In the case where the PDSCH is configured to carry up to one TB, the HARQ-ACK response may be configured in one bit. In the case where the PDSCH is configured to carry up to two TBs, if spatial bundling is not configured, the HARQ-ACK response may be configured in two bits, and if spatial bundling is configured, the HARQ-ACK response may be configured in one bit. When slot #(n+K1) is designated as the HARQ-ACK transmission timing of multiple PDSCHs, the UCI sent in slot #(n+K1) includes HARQ-ACK responses to multiple PDSCHs.

[0103] Whether the UE should perform spatial bundling for HARQ-ACK responses may be configured for each cell group (e.g., via RRC / high-layer signaling). For example, spatial bundling may be configured for each individual HARQ-ACK response sent on the PUCCH and / or a HARQ-ACK response sent on the PUSCH.

[0104] Spatial bundling can be supported when up to two (or two or more) TBs (or codewords) can be received at a time (can be or be scheduled by one DCI) in the corresponding serving cell (for example, when the high-level parameter maxNrofCodeWordsScheduledByDCI indicates 2 TBs). More than four layers can be used for 2TB transmission, and up to four layers can be used for 1TB transmission. As a result, when spatial bundling is configured for the corresponding cell group, spatial bundling can be performed for serving cells in the cell group where more than four layers can be scheduled. A UE that wants to send a HARQ-ACK response through spatial bundling can generate a HARQ-ACK response by performing a (bit-by-bit) logical AND operation on the A / N bits of multiple TBs.

[0105] For example, assuming that a UE receives a DCI that schedules two TBs and receives the two TBs on a PDSCH based on the DCI, the UE that performs spatial bundling can generate a single A / N bit by a logical AND operation between a first A / N bit of a first TB and a second A / N bit of a second TB. As a result, when both the first TB and the second TB are ACK, the UE reports an ACK bit value to the BS, and when at least one TB is NACK, the UE reports a NACK bit value to the BS.

[0106] For example, when only one TB is actually scheduled in a serving cell configured to receive two TBs, the UE may generate a single A / N bit by performing a logical AND operation on the A / N bits of the one TB and a bit value 1. As a result, the UE reports the A / N bits of the one TB to the BS.

[0107] There are multiple parallel DL HARQ processes at the BS / UE for DL ​​transmissions. Multiple parallel HARQ processes allow continuous DL transmissions while the BS waits for HARQ feedback indicating the success or failure of reception of the previous DL transmission. Each HARQ process is associated with a HARQ buffer in the medium access control (MAC) layer. Each DL HARQ process manages state variables such as the number of MAC physical data unit (PDU) transmissions, HARQ feedback for the MAC PDUs in the buffer, and the current redundancy version. Each HARQ process is identified by a HARQ process ID.

[0108] On the other hand, according to the HARQ-ACK bit (payload) configuration method, the HARQ-ACK codebook is roughly defined as three codebook types: type 1, type 2, and type 3. In the case of the type 1 codebook, the HARQ-ACK payload is configured according to a combination of a candidate HARQ-ACK timing (K1) set (configured for the corresponding cell) and a candidate PDSCH opportunity (SLIV) set (e.g., a semi-static fixed size codebook based on RRC signaling). In the case of the type 2 codebook, the codebook size (e.g., downlink assignment index DAI) can be dynamically changed according to the number of PDSCHs actually scheduled or the corresponding resource allocation number. In the case of the type 3 codebook, the HARQ-ACK payload (e.g., a one-time A / N report) is configured by mapping the HARQ-ACK bits related to the corresponding HPN for each HARQ process number (HPN) according to the maximum number of HARQ processes (configured for the corresponding cell per cell). Recently, an enhanced type 3 codebook has been added to the recent NR standard as a type 3 codebook. The enhanced type 3 codebook is not a method of reporting the HARQ-ACK bits of all cells / HPNs at once to reduce signaling overhead, but a method of reporting the HARQ-ACK bits of all cells / HPNs indicated to the base station (BS) among all cells / HPNs. The cell / HPN subset associated with the enhanced type 3 codebook is configured for the user equipment (UE) through high-layer signaling, and then one of the subsets configured for the UE can be indicated by the DCI that triggers the enhanced type 3 codebook. The UE can report the HARQ-ACK of the cell / HPN belonging to the indicated subset.

[0109] In the case of a type 1 codebook, a combination of all SLIVs that can be transmitted (or scheduled to be transmitted) in a DL time slot K1 slots before the A / N transmission time slot for each K1 value is calculated under a state of a plurality of (e.g., N) sets of candidate K1 values ​​(each cell is used for a corresponding cell), an A / N sub-payload is configured (including determining the A / N bit position / order corresponding to each SLIV that can be transmitted in the corresponding time slot) (defined as "SLIV pruning"), and then the entire A / N codebook is configured by concatenating such an A / N sub-payload to N K1 values. In this case, a set of (N) DL time slots corresponding to each K1 value may be defined as a bundling window corresponding to the A / N transmission time slot.

[0110] In the case of a type 2 HARQ-ACK codebook, a codebook for sending HARQ-ACK information on the same PUCCH / PUSCH is defined based on the Counter-Downlink Assignment Indicator (C-DAI) and Total-DAI (T-DAI) values ​​indicated by the PDCCH actually sent. That is, the codebook is configured based on the PDCCH information actually sent to the UE. When the UE fails to detect a specific PDCCH, the UE sends a NACK on the bit for the corresponding PDCCH among the bits defined in the codebook. In this case, the UE can identify whether the PDCCH detection has failed by the C-DAI and T-DAI values. The C-DAI is obtained by counting the cumulative number of {serving cell index, PDCCH monitoring opportunity} pairs provided by the PDSCH reception until the current serving cell and the current PDCCH monitoring opportunity. First, for multiple PDSCH receptions of the same {serving cell index, PDCCH monitoring opportunity} pair, the PDSCH where the reception starts first is counted first (ie, a lower C-DAI value is assigned). Next, when there are multiple pairs with the same PDCCH monitoring opportunity index among different {serving cell index, PDCCH monitoring opportunity} pairs, the pair with the lower serving cell index is counted first. Next, when there are multiple pairs with the same serving cell index among different {serving cell index, PDCCH monitoring opportunity} pairs, the PDCCH monitoring opportunity with the lower index is counted first.

[0111] In the case of the type 3 codebook, specifically, one of mode 1 in which HARQ-ACK and NDI corresponding to HARQ-ACK are fed back together and mode 2 in which only HARQ-ACK without NDI is fed back may be configured from the BS for the UE. When the UE is configured with mode 1, it operates to feed back HARQ-ACK and NDI (indicated by DCI) received by the PDSCH corresponding to each HARQ process number (HPN) together.

[0112] Figure 6 An exemplary PUSCH transmission process is shown. Figure 6 , the UE may detect the PDCCH in slot #n. The PDCCH includes DL scheduling information (eg, DCI format 1_0 or 1_1). The DCI format 1_0 or 1_1 may include the following information.

[0113] - Frequency domain resource assignment: indicates the RB set assigned to PUSCH.

[0114] -Time domain resource assignment: Indicates the slot offset K2 and the starting position (e.g., OFDM symbol index) and duration (e.g., number of OFDM symbols) of the PUSCH in the slot. The starting symbol and length of the PUSCH may be indicated by a start and length indicator value (SLIV) or separately.

[0115] Then, the UE may transmit the PUSCH in slot #(n+K2) according to the scheduling information in slot #n. The PUSCH includes the UL-SCH TB.

[0116] Carrier Aggregation

[0117] NR can support wider uplink / downlink bandwidth by aggregating multiple uplink / downlink carriers (i.e., carrier aggregation). Signals can be sent / received in multiple carriers through carrier aggregation. When carrier aggregation is applied, each carrier (see Figure A2) may be referred to as a component carrier (CC). CCs may be contiguous or non-contiguous in the frequency domain. The bandwidth of each CC may be determined independently. Asymmetric carrier aggregation in which the number of ULCCs is different from the number of DLCCs is also possible.

[0118] -PCell (Primary Cell): In the case of a UE configured with carrier aggregation, a cell operating at the primary frequency (e.g., primary component carrier (PCC)) where the UE performs an initial connection establishment procedure or initiates a connection re-establishment procedure. In the case of dual connectivity (DC), a primary cell group (MCG) cell operating at the primary frequency where the UE performs an initial connection establishment procedure or initiates a connection re-establishment procedure.

[0119] - Secondary Cell (SCell): A cell that provides radio resources other than the special cell in the case of a UE configured with carrier aggregation.

[0120] -Primary SCG cell (PSCell): In case of DC, a secondary cell group (SCG) cell to which the UE performs random access when performing RRC reconfiguration and synchronization processes.

[0121] - Special cell (SpCell): In case of DC, the special cell refers to the PCell of the MCG or the PSCell of the SCG. Otherwise (ie, non-DC), the special cell refers to the PCell.

[0122] - ServCell: indicates the cell configured for the UE in RRC_CONNECTED state. If CA / DA is not configured, there is only one serving cell (ie, PCell). If CA / DA is configured, the serving cell indicates a cell set including special cells and all SCells.

[0123] In addition, the control information may be configured to be sent and received only through special cells. For example, UCI may be sent through a special cell (e.g., PCell). When an SCell (hereinafter, PUCCH-SCell) that allows PUCCH transmission is configured, UCI may also be sent through PUCCH-SCell. As another example, the BS may allocate a scheduling cell (set) to reduce the complexity of PDCCH blind decoding (BD) on the UE side. For PDSCH reception / PUSCH transmission, the UE may perform PDCCH detection / decoding only in the scheduling cell. In addition, the BS may send PDCCH only through the scheduling cell (set). For example, the PDCCH for downlink allocation may be sent in cell #0 (i.e., the scheduling cell), and the corresponding PDSCH may be sent in cell #2 (i.e., the scheduled cell) (cross-carrier scheduling (CCS)). The scheduling cell (set) may be configured in a UE-specific, UE group-specific, or cell-specific manner. The scheduling cell includes a special cell (e.g., PCell).

[0124] For cross-carrier scheduling, a 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) in the PDCCH (i.e., DCI) and can be used to indicate the (serving) cell index of the scheduled cell.

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

[0126] -CIF enabled: CIF is present in PDCCH. PDCCH on the scheduling cell can use CIF to allocate PDSCH / PUSCH resources on one of multiple cells. The scheduling cell can be the same or different from the scheduled cell. PDSCH / PUSCH means PDSCH or PUSCH.

[0127] Figure 7 is a diagram showing carrier aggregation. Figure 7In the example, it is assumed that three cells are aggregated. If CIF is disabled, only the PDCCH for scheduling its PDSCH / PUSCH can be sent in each cell (self-carrier scheduling (SCS)). On the other hand, if CIF is enabled by UE-specific (or UE group-specific or cell-specific) high-layer signaling and cell A is configured as a scheduling cell, not only the PDCCH for scheduling the PDSCH / PUSCH of cell A but also the PDCCH for scheduling the PDSCH / PUSCH of another cell (i.e., the scheduled cell) can be sent in cell A (cross-carrier scheduling (CCS)). In this case, the PDCCH for scheduling its own cell is not sent in cell B / C.

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

[0129] Figure 8 A wireless communication system supporting an unlicensed band is shown. For convenience, a cell operating in an authorized band (hereinafter, L-band) is defined as LCell, and a carrier of LCell is defined as (DL / UL)LCC. A cell operating in an unlicensed band (hereinafter, U-band) is defined as UCell, and a carrier of UCell is defined as (DL / UL)UCC. The carrier of a cell may represent an operating frequency (eg, center frequency) of the cell. Cells / carriers (eg, CCs) may be collectively referred to as cells.

[0130] When carrier aggregation is supported, one UE can send and receive signals to and from a BS in multiple aggregated cells / carriers. If multiple CCs are configured for one UE, one CC can be configured as a primary CC (PCC) and the other CCs can be configured as secondary CCs (SCCs). Specific control information / channels (e.g., CSS PDCCH and PUCCH) can be configured to send and receive signals only in the PCC. Data can be sent and received in the PCC and / or SCC. Figure 8 In (a), the UE and the BS transmit and receive signals in the LCC and the UCC (non-standalone (NSA) mode). In this case, the LCC may be configured as a PCC and the UCC may be configured as an SCC. If multiple LCCs are configured for the UE, one specific LCC may be configured as a PCC and the other LCCs may be configured as SCCs. Figure 8 (a) corresponds to LAA of the 3GPP LTE system. Figure 8 (b) shows a case where the UE and the BS send and receive signals in one or more UCCs without an LCC (SA mode). In this case, one UCC may be configured as a PCC and the other UCCs may be configured as SCCs. To this end, PUCCH, PUSCH, and PRACH transmissions may be supported. Both NSA mode and SA mode may be supported in the unlicensed band of the 3GPP NR system.

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

[0132] - Channel: A carrier or a portion of a carrier including contiguous RBs for performing a channel access procedure (CAP) in a shared spectrum.

[0133] - Channel Access Procedure (CAP): A process of evaluating the availability of a channel based on sensing before signal transmission to determine whether the channel is used by other communication nodes. The basic unit of sensing is a sensing slot with a duration Tsl of 9us. When the BS or UE senses the channel during the sensing slot duration, and the power detected for at least 4us within the sensing slot duration is less than the energy detection threshold XThresh, the sensing slot duration Tsl may be considered idle. Otherwise, the sensing slot duration Tsl of 9us may be considered busy. CAP may be referred to as Listen Before Talk (LBT).

[0134] - Channel occupancy: Transmissions from BS / UE on the channel after CAP.

[0135] - Channel Occupancy Time (COT): The total time that a BS / UE and any BS / UE that shares the channel occupancy perform transmissions on a channel after the BS / UE corresponding CAP. When determining the COT, if a transmission gap is less than or equal to 25us, the gap duration may also be included in the COT. Transmissions between a BS and a corresponding UE may share the COT.

[0136] -DL transmission burst: A collection of transmissions from a BS without any gaps greater than 16us. Transmissions from a BS separated by gaps greater than 16us are considered separate DL transmission bursts. The BS may perform transmissions after gaps within a DL transmission burst without sensing channel availability.

[0137] -UL transmission burst: A set of transmissions from a UE without any gaps greater than 16us. Transmissions from a UE separated by gaps greater than 16us are considered separate UL transmission bursts. The UE may perform transmissions after a gap within a UL transmission burst without sensing channel availability.

[0138] - Discovery Burst: A DL transmission burst that includes a set of signals and / or channels confined within a window and associated with a duty cycle. In an LTE-based system, a discovery burst may be a transmission initiated by the BS, including a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a cell-specific reference signal (CRS), and also includes a non-zero power CSI-RS. In an NR-based system, a discovery burst may be a transmission initiated by the BS, including at least a SS / PBCH block, and also includes a CORESET for scheduling a PDSCH with SIB1, a PDSCH carrying SIB1, and / or a PDCCH with non-zero power CS-RS.

[0139] Fig. 9 A method for occupying resources in an unlicensed band is shown. According to regional regulations regarding unlicensed bands, communication nodes in unlicensed bands need to determine whether other communication nodes use channels before signal transmission. Specifically, a communication node may first perform carrier sensing (CS) before signal transmission to check whether other communication nodes send signals. If it is determined that other communication nodes do not send signals, this means confirming an idle channel assessment (CCA). When there is a CCA threshold configured by high-level (e.g., RRC) signaling or a predefined CCA threshold, if energy above the CCA threshold is detected in the channel, the communication node may determine that the channel is in a busy state, otherwise, the communication node may determine that the channel is in an idle state. For reference, in the Wi-Fi standard (802.11ac), the CCA threshold is set to -62dBm for non-Wi-Fi signals and -82dBm for Wi-Fi signals. When it is determined that the channel is in an idle state, the communication node may start sending signals in the UCell. The above process may be referred to as listen-before-talk (LBT) or a channel access procedure (CAP). LBT and CAP are used interchangeably.

[0140] Table 6 shows an exemplary CAP supported in NR-U.

[0141] [Table 6]

[0142]

[0143] Multi-cell scheduling DCI

[0144] NR supports wide spectrum in various frequency ranges. The availability of 5G Advanced spectrum is expected to increase through the reallocation of frequency bands used in the previous generation. In particular, in the case of low-frequency band FR1, available spectrum blocks tend to be further subdivided and distributed. In the case of FR2 bands and some FR1 bands, the available spectrum may become wider, so multiple carriers / cell operations within the band may be required. It is necessary to improve throughput and coverage by using such distributed spectrum bands or wider bandwidth spectrum in a more energy-efficient and flexible manner.

[0145] It is important to increase flexibility and spectrum / power efficiency when scheduling data across multiple cells (including intra-band cells and inter-band cells). In the current 5G NR scheduling method, DCI can only perform PUSCH / PDSCH scheduling for one cell. However, in the future, due to spectrum expansion / changes, etc., the demand for simultaneous scheduling of multiple cells is expected to increase. In order to reduce the control overhead caused by scheduling, it is advantageous to perform PUSCH / PDSCH scheduling of multiple cells through one DCI.

[0146] In order to reduce the DCI overhead required for PDSCH / PUSCH scheduling when multiple cells are configured for carrier aggregation (CA) in the future, a multi-cell scheduling method in Rel-18 may be considered to simultaneously schedule multiple (serving) cells / CCs (through which PDSCH / PUSCH transmissions are transmitted) with a single DCI.

[0147] Therefore, an efficient HARQ-ACK (for convenience, referred to as "A / N") feedback configuration and transmission operation method considering the case where multiple PDSCHs are scheduled simultaneously on multiple cells based on the above-mentioned multi-cell DCI is proposed. The meaning of the terms used (as shown by Figure 5 and Figure 6 In addition, a cell may mean an (active) BWP configured / indicated to the corresponding cell.

[0148] -K0: The time slot interval between the DCI (or PDCCH) transmission time slot and the PDSCH transmission time slot (scheduled from the corresponding DCI)

[0149] -SLIV (Start Symbol and Length Indicator Value) (PDSCH Opportunity): Information about the start symbol and symbol duration (or end symbol) of PDSCH

[0150] - Mapping type: Information on whether the DMRS symbol position of the PDSCH is determined based on the symbol index within the slot duration or the symbol index within the PDSCH duration

[0151] - Time Domain Resource Assistance (TDRA) table: consists of multiple {K0, SLIV, mapping type} combinations (one combination is mapped to each of the multiple rows in the table) and indicates the specific row through the corresponding DCI field

[0152] -K1: The time slot interval between the PDSCH transmission time slot and the HARQ-ACK transmission time slot (for the corresponding PDSCH reception)

[0153] Hereinafter, the multi-cell scheduling DCI may be referred to as multi-cell DCI or DCI, and may include at least one of a DL grant DCI for scheduling a PDSCH and a UL grant DCI for scheduling a PUSCH.

[0154] [1] Type 1 HARQ-ACK codebook configuration considering multi-cell PDSCH scheduling

[0155] 1) Existing operations

[0156] In the case of the existing type 1 codebook, in a state where a set of multiple (e.g., N) candidate K1 values ​​is configured, a combination of all PDSCH opportunities (SLIVs) that can be transmitted in a DL time slot K1 slots ahead of the A / N transmission time slot for each K1 value (configured for each serving cell) is calculated to configure an A / N sub-payload corresponding to the corresponding DL time slot (including determining the A / N bit position / order corresponding to each SLIV) (defined as "SLIV pruning"), and the entire A / N codebook is configured by concatenating such A / N sub-payloads for N K1 values ​​(see Section 9.1.2 of 3GPP TS 38.213 V16.2.0). In this case, a set of (N) DL time slots corresponding to each K1 value can be defined as a bundling window corresponding to the A / N transmission time slot.

[0157] 2) Proposed Operation

[0158] For multi-cell (PDSCH scheduling), multiple SLIV combinations of multiple (one or more) cells may be mapped / configured to each of the multiple (multi-SLIV) rows in the (extended) TDRA table, and the TDRA indication field included in the DCI may indicate a single (multi-SLIV) row based on the corresponding table. For example, through high-level signaling, the first row of the TDRA table may be configured with a first SLIV combination, the second row may be configured with a second SLIV combination, and the Nth row may be configured with an Nth SLIV combination. Each SLIV combination may include one or more {K0, SLIV, mapping type} parameter sets. For example, a specific row of the TDRA table may be configured with {K0, SLIV, mapping type} parameter set #1, {K0, SLIV, mapping type} parameter set #2, {K0, SLIV, mapping type} parameter set #3, ..., {K0, SLIV, mapping type} parameter set #M for scheduling M cells.

[0159] In the case of the K1 indication field, when only one K1 field is configured in the multi-cell DCI, the corresponding K1 field can indicate only one K1 value applied based on a specific PDSCH#1 on a specific cell (among multiple cells scheduled by the corresponding DCI). In this case, it can be determined that HARQ-ACK feedback for all PDSCHs including PDSCH#1 (i.e., on multiple cells scheduled by the corresponding DCI) is sent via the PUCCH (i.e., sub) time slot (i.e., HARQ-ACK feedback transmission timing point) determined by applying the K1 value indicated by the above DCI to the corresponding PDSCH#1.

[0160] In the case of PDSCH#1 in the above description, it can be determined as: the PDSCH on the cell with the lowest cell index (or the highest cell index) among the multiple cells scheduled in Alternative Scheme 1) (through the same multi-cell DCI); or the PDSCH with the latest transmission end symbol timing point (or transmission start symbol timing point) among the multiple PDSCHs on the multiple cells scheduled in Alternative Scheme 2) (through the same multi-cell DCI).

[0161] In alternative 2, if there are multiple PDSCHs with the latest end symbol timing point (or start symbol timing point) among multiple PDSCHs (on multiple scheduled cells), alternative A) can be determined as the PDSCH sent based on the minimum SCS (or maximum SCS) among the multiple corresponding PDSCHs, or alternative B) can be determined as the PDSCH on the cell with the lowest cell index (or the highest cell index) among the multiple corresponding PDSCHs.

[0162] 3) Proposal 1-1

[0163] When configuring PDSCH scheduling based on multi-cell DCI, for cells that become the target of multi-cell DCI scheduling when performing per-cell SLIV pruning processing for type 1A / N codebook configuration, only SLIVs (among multiple SLIVs) associated with the corresponding cells mapped / configured to each multi-SLIV row in the extended TDRA table can be extracted and included in the SLIV set of the SLIV pruning processing applied to the corresponding cells.

[0164] 4) Proposal 1-2

[0165] When configuring PDSCH scheduling based on multi-cell DCI, with respect to the cell that becomes the target of multi-cell DCI scheduling when determining the bundling window per cell for the type 1A / N codebook configuration, if the difference (based on the PUCCH (sub) slot count) between the PDSCH (SLIV) reception timing point and the PDSCH#1 (SLIV) reception timing point on the corresponding cell is d slots for each of the (candidate) K1 values ​​(and (candidate) multiple SLIVs) configured to be indicated by the corresponding multi-cell DCI, then the bundling window corresponding to the corresponding cell can be determined based on a set of {K1+d} values ​​obtained by adding it to K1.

[0166] Specifically, with respect to a cell that becomes a target of multi-cell DCI scheduling, with respect to each of the (candidate) K1 values ​​(and (candidate) multiple SLIVs) configured to be indicated by the corresponding multi-cell DCI, if the difference (based on the PUCCH (sub) slot count) between the last PUCCH (sub) slot overlapping with the PDSCH (SLIV) reception timing point on the corresponding cell (for example, the time slot in which the corresponding PDSCH is sent on the cell or the corresponding PDSCH transmission symbol) and the last PUCCH (sub) slot overlapping with the PDSCH#1 (SLIV) reception timing point (for example, the time slot in which PDSCH#1 is sent on the cell or the corresponding PDSCH#1 transmission symbol) is d slots, then the bundling window corresponding to the corresponding cell can be determined based on a set of {K1+d} values ​​obtained by adding it to K1.

[0167] [2] Type 2 HARQ-ACK codebook configuration considering multi-cell PDSCH scheduling

[0168] 1) Proposed Operation

[0169] In the case of type 2 codebook, when configuring PDSCH scheduling based on multi-cell DCI, a structure may be provided in which a counter sequence / total-DAI value is independently determined and signaled for each of the existing single-cell (PDSCH scheduling) DCI (type) and multi-cell (PDSCH scheduling) DCI (type) (i.e., the DCI / PDSCH sequences / all scheduled for each DCI type are independently determined / signaled) (in other words, the single-cell DCI is signaled by determining only the DAI value of the single-cell DCI, and the multi-cell DCI is signaled by determining only the DAI value of the multi-cell DCI).

[0170] As another method, a structure may be provided in which a counter / total-DAI value is independently determined and signaled for each of the cases in which one PDSCH is scheduled (on a cell) by single-cell DCI or multi-cell DCI (single-cell case) and in which multiple PDSCHs are scheduled (on a cell) by multi-cell DCI (multi-cell case) (i.e., the DCI / PDSCH sequences scheduled for each case are all independently determined / signaled) (in other words, the DCI corresponding to the single-cell case may be signaled by determining the DAI value only for the single-cell case, and the DCI corresponding to the multi-cell case may be signaled by determining the DAI value only for the multi-cell case).

[0171] In the case of the above-mentioned single-cell situation, the following situations may be included: Alternative 1) indicating PDSCH transmission (on the cell) through single-cell DCI or multi-cell DCI; or Alternative 2) indicating (one or) more PDSCH transmissions (on the cell) through (single-cell DCI or) multi-cell DCI, and among them, the UE actually only receives a single PDSCH (on the cell) (in the latter case (i.e., Alternative 2)), the above-mentioned multi-cell situation may correspond to the situation where multiple PDSCH transmissions (on the cell) are indicated through multi-cell DCI and the UE actually receives two or more (on the cell) PDSCHs (on the cell)).

[0172] 2) Proposal 2-1

[0173] (For reference, before explaining this proposal, in order to understand the counter-DAI (counter-DAI for single-cell scheduling) defined in the existing standard, you can refer to the combined Figure 5 Description of the type 2 HARQ-ACK codebook. )

[0174] A. When multiple (multi-cell) DCIs including a multi-cell DCI are sent / received through the same timing point (e.g., PDCCH monitoring opportunity or time slot), a counter-DAI value corresponding to the corresponding multi-cell DCI (signaled by the corresponding DCI) is determined based on the lowest (or highest) cell index among the multiple cells scheduled by the corresponding multi-cell DCI.

[0175] For example, in the case where two multi-cell DCIs are sent / received at the same timing point (e.g., PDCCH monitoring timing or time slot), when comparing the lowest (or highest) cell index scheduled by each DCI (among multiple cells), it may be a structure that can determine / signal the counter (DAI) value corresponding to the DCI that schedules the lower cell index. For example, it is assumed that the multiple DCIs received at the same timing point include at least one multi-cell DCI, the first DCI in the at least one multi-cell DCI schedules {cell A, cell B, and cell C}, and cell A has a cell index lower than cell B and cell C. The second DCI received at the same timing point as the first DCI may be a multi-cell DCI or a single-cell DCI. It is assumed that the cell with the lowest cell index among the one or more cells scheduled by the second DCI is cell D. If the cell index of cell A is less than the cell index of cell D, the C-DAI value of the first DCI is counted first (e.g., relative to the multi-cell scheduling of cells A, cell B, and cell C), and then the C-DAI value of the second DCI is counted. If the cell index of cell A>the cell index of cell D, the C-DAI value of the second DCI is counted first, and then the C-DAI value of the first DCI is counted.

[0176] In the above, if the lowest (or highest) cell index scheduled by each DCI is the same, the structure can be such that the counter (DAI) value corresponding to the DCI of the PDSCH with an earlier start (or end) symbol timing point among the PDSCHs sent on the cell with the corresponding cell index is determined / signaled as a lower value.

[0177] B. As another method, if multiple (multi-cell) DCIs including multi-cell DCIs are sent / received at the same timing point (e.g., PDCCH monitoring opportunity or time slot), the counter-DAI value corresponding to the multi-cell DCI (signaled by the corresponding DCI) can be determined based on the PDSCH having the earliest transmission start (or end) symbol timing point among the multiple PDSCHs on the multiple cells scheduled by the corresponding multi-cell DCI.

[0178] For example, if two multi-cell DCIs are sent / received at the same timing point, when comparing the PDSCHs (among multiple PDSCHs on multiple cells) with the earliest start (or end) symbol timing point scheduled for each DCI, the counter (DAI) value corresponding to the DCI that schedules the PDSCH with an earlier start (or end) symbol timing point may be determined / signaled as a lower value.

[0179] In the above description, if the start (or end) symbol timing point of the PDSCH with the earliest start (or end) symbol timing point scheduled by each DCI is the same, the structure can be such that the counter (DAI) value corresponding to the DCI of the PDSCH sent on the cell with a lower cell index among the corresponding PDSCHs scheduled can be determined / signaled as a lower value.

[0180] C. As another method, when multiple (multi-cell) DCIs including a multi-cell DCI are sent / received at the same timing point (e.g., PDCCH monitoring opportunity or time slot), the counter-DAI value corresponding to the multi-cell DCI (or signaled by the corresponding multi-cell DCI) can be determined based on the PDSCH having the latest transmission start (or end) symbol timing point among the multiple PDSCHs on the multiple cells scheduled by the corresponding multi-cell DCI.

[0181] For example, in the case of sending / receiving two multi-cell DCIs at the same timing point, when comparing the PDSCHs (among multiple PDSCHs on multiple cells) with the latest start (or end) symbol timing point scheduled by each DCI, the structure can be such that the counter (DAI) value corresponding to the DCI scheduling the PDSCH with an earlier start (or end) symbol timing point can be determined / signaled as a lower value.

[0182] In the above description, if the start (or end) symbol timing point of the PDSCH having the latest start (or end) symbol timing point scheduled by each DCI is the same, it can be a structure in which the counter (DAI) value corresponding to the DCI scheduling the PDSCH sent on a cell with a lower cell index is determined / signaled as a lower value.

[0183] 3) Proposal 2-2

[0184] For example, the number of A / N bits per DAI value in a multi-cell case can be determined by considering at least one of the maximum number of cells that can be co-scheduled by one (multi-cell) DCI (in the same PUCCH group), the number of TBs (or codewords) supported by each PDSCH (for example, 1 or 2), and whether spatial bundling of A / N is configured.

[0185] If spatial (domain) bundling between TBs (2 TBs) transmitted through the same PDSCH is configured (or if only a single TB transmission is configured to be available for all multi-cell DCI scheduling target cells), the number of A / N bits corresponding to one DAI for the multi-cell case (and / or multi-cell DCI) (for convenience, referred to as "DAI A / N size for multi-cell case") can be determined based on the maximum number of cells that can be simultaneously scheduled through a single multi-cell DCI. If spatial bundling is not configured, it can be determined based on the maximum number of TBs that can be simultaneously scheduled through a single multi-cell DCI (taking into account all simultaneously schedulable cell combinations and the maximum (transmittable) number of TBs configured per cell).

[0186] For example, refer to Fig.10 , if the number of TBs (or CWs) per PDSCH is set to 1 for all cells that can be scheduled via multi-cell DCI [A05], or if spatial A / N bundling between TBs is configured for cells despite including cells with a number of TBs per PDSCH of 2 [A10], the DAI A / N size may be determined based on the maximum number of cells that can be scheduled via one multi-cell DCI. For example, referring to Fig.11 , assuming that M co-scheduled cell combinations are configured for the UE and the multi-cell DCI performs multi-cell scheduling through one of the M co-scheduled cell combinations, the maximum number of cells that can be co-scheduled through one multi-cell DCI may be Max{1st value, 2nd value, 3rd value, ...., Mth value}. For example, assuming that Max{1st value, 2nd value, 3rd value, ...., Mth value} = X, the DAI A / N size may be X bits. For example, if X bits are allocated to each Counter DAI value and a HARQ-ACK codebook (e.g., a type 2 HARQ-ACK codebook) is configured for a total of C1 Counter DAI values, the HARQ-ACK codebook may include C1*XA / N bits. This may mean that if the number of TBs (or CWs) per PDSCH is set to 1 for all cells that can be scheduled via multi-cell DCI [A05, yes], or if spatial A / N bundling between TBs is configured for the cells despite including corresponding cells with a number of TBs per PDSCH of 2 [A10, yes], then for 1DCI, 1A / N bit is allocated per scheduled cell.

[0187] If the cells that can be scheduled through multi-cell DCI include a cell (at least one cell) with a number of 2 TBs per PDSCH and no TB-to-TB space A / N bundling configured [A10, No], the DAI A / N size can be determined based on the maximum number of TBs that can be scheduled through one multi-cell DCI. For example, assuming that the maximum number of TBs that can be scheduled through one multi-cell DCI is Y, if the HARQ-ACK codebook (e.g., type 2 HARQ-ACK codebook) is configured for a total of C1 Counter DAI values, the HARQ-ACK codebook may include C1*YA / N bits. For example, assuming that Fig.11 If 2-TB is configured for cell #1 and cell #3 in the UE, 1-TB is configured for the remaining cells, and spatial bundling is not configured for cell #1 and cell #3 (at least one of them), the number of TBs that can be scheduled through cell combination 1 can be 2+2+1=5, the number of TBs that can be scheduled through cell combination 2 can be 2, the number of TBs that can be scheduled through cell combination 3 can be 1+2+1=4, and the number of TBs that can be scheduled through cell combination M can be 1+1+1+1=4. The DAI A / N size can be determined based on the cell combination with the largest number of schedulable TBs among the M cell combinations configured for the UE.

[0188] 4) Proposal 2-3

[0189] If independent DAI counting is performed between a single-cell case (and / or a single-cell DCI, for convenience, the single-cell case is named as a general term for the single-cell case and the single-cell DCI) and a multi-cell case (or a multi-cell DCI, for convenience, the multi-cell case is named as a general term for the multi-cell case and the multi-cell DCI), the UE may configure separate subcodebooks for the single-cell case and the multi-cell case, respectively, and may be operable to configure the entire codebook in a concatenated form of appending subcodebook #2 corresponding to the multi-cell case to subcodebook #1 corresponding to the single-cell case (or vice versa, i.e., the entire codebook may be configured in a form of appending subcodebook #1 to subcodebook #2). (i) For example, subcodebook #1 may include an A / N bit of a single-cell DCI and an A / N bit of a multi-cell DCI for scheduling a PDSCH of only one cell, and subcodebook #2 may include an A / N bit of a multi-cell DCI for scheduling a PDSCH of at least two cells. (ii) For another example, subcodebook #1 may include A / N bits for a single-cell DCI, and subcodebook #2 may include A / N bits for a multi-cell DCI for scheduling a PDSCH of only one cell and A / N bits for a multi-cell DCI for scheduling a PDSCH of at least two cells.

[0190] In addition, (in the case of CA) CB group (CBG)-based PDSCH transmission (DCI scheduling it) may be configured on a specific cell (such PDSCH scheduling is referred to as CBG-PDSCH case), the number of A / N bits corresponding to PDSCH / DCI (for convenience, referred to as "DAI A / N size of CBG-PDSCH case") may be determined as the maximum number of CBGs that can be configured / transmitted on a single PDSCH configured on the corresponding cell, and / or an operation of simultaneously scheduling (on the corresponding cell) multiple TDM PDSCHs based on a single DCI may be configured (such PDSCH scheduling is referred to as a multi-PDSCH case). The number of A / N bits corresponding to DCI (for convenience, referred to as "DAI A / N size of multi-PDSCH case") may be determined based on {the maximum number of schedulable PDSCHs, the maximum number of TBs that can be transmitted per PDSCH, the presence or absence / time unit (time domain) A / N bundling configuration}. The DAI count and subcodebook configuration in the case where the CBG-PDSCH case and / or the multi-PDSCH case and the multi-cell case are all configured can be configured as follows.

[0191] - Option 1: Independent DAI counting between the multi-cell case and the CBG-PDSCH case (or multi-PDSCH case) may be performed and a separate subcodebook may be configured for each of them. In this case, an operation may be performed to configure the entire codebook in a concatenated manner by appending subcodebook #2 corresponding to the CBG-PDSCH case (or multi-PDSCH case) to subcodebook #1 corresponding to the multi-cell case (or vice versa, i.e., appending subcodebook #1 to subcodebook #2).

[0192] -Option 2: Common DAI counting is performed for a multi-cell case and a CBG-PDCH case (or a multi-PDSCH case) (in other words, the DCI corresponding to the multi-cell case may be a structure for determining / signaling a DAI value by considering not only the multi-cell case but also the CBG-PDCH case (or a multi-PDSCH case), and the DCI corresponding to the CBG-PDCH case (or a multi-PDSCH case) may be a structure for determining / signaling a DAI value by considering not only the CBG-PDCH case (or a multi-PDSCH case) but also the multi-cell case.) and one subcodebook for integrating the two cases may be configured. In this case, the number of A / N bits corresponding to one DAI may be determined as a maximum value selected from the DAI A / N size of the multi-cell case and the DAI A / N size of the CBG-PDSCH case (or the DAI A / N size of the multi-PDSCH case).

[0193] In addition, in the case where a type 2 codebook is configured on a specific (PUCCH) cell group, if multi-cell DCI-based PDSCH scheduling is configured on multiple cells belonging to the corresponding cell group, CBG-based PDSCH transmission can be restricted from being configured on any cell in the corresponding cell group to reduce the complexity of A / N codebook configuration from the perspective of the UE. In the case where a type 1 codebook is configured, if multi-cell DCI-based PDSCH scheduling is configured on multiple specific cells, CBG-based PDSCH transmission can be restricted from being configured on any cell in the multiple corresponding cells to reduce the complexity of A / N codebook configuration from the perspective of the UE.

[0194] 5) Proposal 2-4

[0195] The A / N bit mapping order in the A / N payload corresponding to one DAI (or multi-cell DCI) in the multi-cell case may be determined as follows.

[0196] - Option 1: The A / N bits corresponding to the TBs scheduled by the DCI (or the TBs actually received by the UE among the TBs) may be mapped sequentially in the order of first the TB index and then the cell index. The order may mean ascending or descending. For example, the UE first maps the A / N bits in the order of the TB indexes of all scheduled TBs of the cell with the lowest cell index (e.g., ascending TB index order). When the A / N bit mapping of all TB indexes of the corresponding cell is completed, the UE may first map the A / N bits in the order of the TB indexes of the scheduled TBs of the cell with the second lowest cell index.

[0197] If spatial bundling is configured (or all multi-cell DCI scheduling target cells are configured to be capable of only single TB transmission), the A / N bits corresponding to the PDSCH scheduled by DCI (or the PDSCH actually received by the UE among them) can be mapped sequentially according to the order of cell indexes.

[0198] For example, in Fig.12 It is assumed that cell A with cell index 1, cell B with cell index 3, and cell C with cell index 5 are co-scheduled by DCI, a maximum of 2-TB is configured for each of cell A and cell B, a maximum of 1-TB is configured for cell C, and spatial bundling is configured only for cell B. In addition, it is assumed that the number of TBs actually scheduled by DCI for cell A, cell B, and cell C is 1-TB, 2-TB, and 1-TB, respectively. (In addition, for the convenience of description, the DAI A / N size of the multi-cell case described in Proposal 2-2 is assumed to be 5 bits.) Fig.12 (a) of FIG. 1 shows an example of Option 1. Fig.12(a), first map the A / N bits of TB1 of cell A with the lowest cell index. Since TB2 of cell A is not scheduled, the A / N bits of TBs of cell B are mapped next. Since spatial bundling is configured on cell B, the A / N bits of TB1 and the A / N bits of TB2 can be bundled into one A / N bit (e.g., AND operation). Next, map the A / N bits of TB1 of cell C.

[0199] - Option 2: The A / N bits corresponding to the PDSCH (cell) scheduled by DCI (or the PDSCH (cell) actually received by the UE among them) can be mapped sequentially in the order of cell indexes by the maximum number of TBs configured on each cell. The order can mean ascending or descending order.

[0200] If spatial bundling is configured (or all multi-cell DCI scheduling target cells are configured to be capable of only single TB transmission), the A / N bits corresponding to the PDSCH scheduled by DCI (or the PDSCH actually received by the UE among them) can be mapped sequentially according to the order of cell indexes.

[0201] Fig.12 (b) may be an example of option 2. Fig.12 (b), first map the A / N bits of TB1 of cell A with the lowest cell index. Since the maximum number of TBs configured on cell A is 2, the A / N bits of TB2 can be mapped even if TB2 of cell A is not actually scheduled. The A / N bits of TB2 can be set to NACK / DTX. Next, map the A / N bits of the TBs of cell B. Although the maximum number of TBs configured on cell B is 2, since spatial bundling is configured on cell B, the A / N bits of TB1 and TB2 can be bundled (for example, ANDed) into one A / N bit. Next, the A / N bits of TB1 of cell C can be mapped.

[0202] - Option 3: (If the number of A / N bits corresponding to one DAI is determined based on the number of cells in the entire candidate cell set that can be scheduled by multi-cell DCI, then) regardless of the PDSCH (cell) actually scheduled (received), the A / N bits corresponding to the cells belonging to the entire candidate cell set (according to the maximum number of TBs configured for each cell) can be mapped in the order of cell index. The order can mean ascending or descending. For example, even if only a combination of some cells among the cells in the candidate cell set is scheduled by DCI, the A / N bits of all cells belonging to the candidate cell set can be mapped based on the cell index order.

[0203] If spatial bundling is configured (or all multi-cell DCI scheduling target cells are configured to be capable of only single TB transmission), the A / N bits corresponding to the scheduled / received PDSCH can be mapped sequentially to the cells belonging to the entire candidate cell set in the order of the cell index, regardless of the PDSCH (cell) actually scheduled (received).

[0204] Fig.13 Implementations of signal reception of a UE based on at least some of the above-mentioned implementations are shown. Even if there is no separate description, for better understanding Fig.13 See also the above.

[0205] Reference Fig.13 , the UE may receive downlink control information (DCI) via a physical downlink control channel (PDCCH)

[1305] .

[0206] The UE may receive at least one transport block (TB) through a physical downlink shared channel (PDSCH) on at least one of a plurality of cells configured in the UE based on the DCI

[1310] .

[0207] The UE may send hybrid automatic repeat request-acknowledgement (HARQ-ACK) information for at least one TB

[1315] .

[0208] DCI can support multi-cell scheduling based on multiple cells.

[0209] The number of acknowledgement / negative acknowledgement (ACK / NACK) bits included in the HARQ-ACK information may be determined based on at least one of a maximum number of cells co-scheduled by the DCI or a maximum number of TBs receivable by the cells co-scheduled by the DCI.

[0210] Based on the maximum number of TBs per PDSCH being 2 in at least one cell among the cells co-scheduled by DCI and no spatial bundling being configured, the number of ACK / NACK bits included in the HARQ-ACK information may be determined based on the maximum number of TBs that can be received by the cells co-scheduled by DCI.

[0211] Based on the maximum number of TBs per PDSCH in each cell that can be co-scheduled by DCI being 1 or based on spatial bundling being configured, the number of ACK / NACK bits included in the HARQ-ACK information can be determined based on the maximum number of cells that can be co-scheduled by DCI.

[0212] The maximum number of cells that can be jointly scheduled by the DCI may be related to a cell combination including a maximum number of cells among cell combinations that can be scheduled by the DCI.

[0213] In the HARQ-ACK information, ACK / NACK bits may be arranged based on the serving cell index of the co-scheduled cell.

[0214] The DCI may include information about a downlink assignment index (DAI). The DAI may be determined based on a cell having a minimum serving cell index among cells co-scheduled by the DCI.

[0215] The HARQ-ACK information related to multi-cell scheduling may be included in the second subcodebook, and the HARQ-ACK information related to single-cell scheduling may be included in the first subcodebook.

[0216] A HARQ-ACK codebook may be configured based on a concatenation of a first subcodebook and a second subcodebook. For example, the second subcodebook may be appended to the first subcodebook.

[0217] The second subcodebook may be related to a PDSCH scheduled by a multi-cell scheduling DCI having two or more actually scheduled cells. The first subcodebook may be related to a PDSCH scheduled by a multi-cell scheduling DCI having one actually scheduled cell and a single-cell scheduling DCI.

[0218] Fig.14 Implementations of signal transmission of a base station (BS) based on at least some of the above-mentioned implementations are shown. Even if there is no separate description, for better understanding Fig.14 See also the above.

[0219] Reference Fig.14 , the base station may send downlink control information (DCI) to the UE via a physical downlink control channel (PDCCH)

[1405] .

[0220] The base station may send at least one transport block (TB) through a physical downlink shared channel (PDSCH) on at least one of a plurality of cells configured in the UE based on the DCI

[1410] .

[0221] The base station may receive hybrid automatic repeat request-acknowledgement (HARQ-ACK) information for at least one TB

[1415] .

[0222] DCI can support multi-cell scheduling based on multiple cells.

[0223] The number of acknowledgement / negative acknowledgement (ACK / NACK) bits included in the HARQ-ACK information may be determined based on at least one of a maximum number of cells co-scheduled by the DCI and a maximum number of TBs that may be transmitted by the cells co-scheduled by the DCI.

[0224] Based on the maximum number of TBs per PDSCH in at least one cell that can be co-scheduled by DCI being 2 and spatial bundling not being configured, the number of ACK / NACK bits included in the HARQ-ACK information can be determined based on the maximum number of TBs that can be sent by the cells co-scheduled by DCI.

[0225] Based on the maximum number of TBs per PDSCH in each cell co-scheduled by DCI being 1 and spatial bundling being configured, the number of ACK / NACK bits included in the HARQ-ACK information may be determined based on the maximum number of cells co-scheduled by DCI.

[0226] The maximum number of cells that can be jointly scheduled by the DCI may be related to a cell combination including a maximum number of cells among cell combinations that can be scheduled by the DCI.

[0227] In the HARQ-ACK information, ACK / NACK bits may be arranged based on the serving cell index of the co-scheduled cell.

[0228] The DCI may include information about a downlink assignment index (DAI). The DAI may be determined based on a cell having a minimum serving cell index among cells co-scheduled by the DCI.

[0229] HARQ-ACK information related to multi-cell scheduling may be included in the second subcodebook, and HARQ-ACK information related to single-cell scheduling may be included in the first subcodebook.

[0230] A HARQ-ACK codebook may be configured based on a concatenation of a first subcodebook and a second subcodebook. For example, the second subcodebook may be appended to the first subcodebook.

[0231] The second subcodebook may be related to a PDSCH scheduled by a multi-cell scheduling DCI having two or more actually scheduled cells. The first subcodebook may be related to a PDSCH scheduled by a multi-cell scheduling DCI having one actually scheduled cell and a single-cell scheduling DCI.

[0232] Fig.15 A communication system 1 applied to the present disclosure is shown.

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

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

[0235] Wireless communication / connection 150a, 150b or 150c may be established between wireless devices 100a to 100f / BS200 or BS200 / BS200. Herein, wireless communication / connection may be established through various RATs (e.g., 5G NR) such as uplink / downlink communication 150a, sidelink communication 150b (or D2D communication) or inter-BS communication (e.g., relay, integrated access backhaul (IAB)). The wireless device and the BS / wireless device may send / receive radio signals to / from each other through wireless communication / connection 150a and 150b. For example, wireless communication / connection 150a and 150b may send / receive signals through various physical channels. To this end, at least a portion of various configuration information for configuring processes for sending / receiving radio signals, various signal processing processes (e.g., channel coding / decoding, modulation / demodulation, and resource mapping / demapping), and resource allocation processes may be performed based on various proposals of the present disclosure.

[0236] Fig.16 A wireless device suitable for use with the present disclosure is shown.

[0237] Reference Fig.16 , the first wireless device 100 and the second wireless device 200 may transmit radio signals via various RATs (e.g., LTE and NR). Herein, {the first wireless device 100 and the second wireless device 200} may correspond to Fig.15 {wireless device 100x and BS 200} and / or {wireless device 100x and wireless device 100x}.

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

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

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

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

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

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

[0244] Fig.17 Another example of a wireless device applicable to the present disclosure is shown. The wireless device can be used according to the usage / service (refer to Fig.15 ) are implemented in various forms.

[0245] Reference Fig.17 , the wireless devices 100 and 200 may correspond to Fig.16The wireless devices 100 and 200 of the present invention may be configured by various elements, components, units / parts and / or modules. For example, each of the wireless devices 100 and 200 may include a communication unit 110, a control unit 120, a memory unit 130 and an additional component 140. The communication unit may include a communication circuit 112 and a transceiver 114. For example, the communication circuit 112 may include Fig.16 One or more processors 102 and 202 and / or one or more memories 104 and 204. For example, the transceiver 114 may include Fig.16 The control unit 120 is electrically connected to the communication unit 110, the memory unit 130, and the additional components 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. The control unit 120 may transmit information stored in the memory unit 130 to the outside (e.g., other communication devices) via the communication unit 110 through a wireless / wired interface, or store information received from the outside (e.g., other communication devices) via the communication unit 110 in the memory unit 130 through a wireless / wired interface.

[0246] The additional components 140 may be configured differently depending on the type of wireless device. For example, the additional components 140 may include at least one of a power supply unit / battery, an input / output (I / O) unit, a drive unit, and a computing unit. The wireless device may be configured in the form of, but not limited to, a robot ( Fig.15 100a), vehicles ( Fig.15 100b-1 and 100b-2), XR devices ( Fig.15 100c), handheld device ( Fig.15 100d), household appliances ( Fig.15 100e), IoT devices ( Fig.15 100f), digital broadcast user equipment, holographic devices, public safety devices, MTC devices, medical devices, fintech devices (or financial devices), security devices, climate / environmental devices, AI servers / devices ( Fig.15 400), BS( Fig.15 200), network nodes, etc. The wireless device can be used in a mobile or fixed location according to the usage example / service.

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

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

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

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

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

[0252] Fig.19 is a diagram illustrating a DRX operation of a UE according to an embodiment of the present disclosure.

[0253] The UE may perform DRX operation in the process and / or method described / proposed above. A UE configured with DRX may reduce power consumption by discontinuously receiving DL signals. DRX may be performed in the RRC_IDLE state, the RRC_INACTIVE state, and the RRC_CONNECTED state. The UE performs DRX in the RRC_IDLE state and the RRC_INACTIVE state to discontinuously receive paging signals. DRX in the RRC_CONNECTED state (RRC_CONNECTED DRX) will be described below.

[0254] Reference Fig.19 , the DRX cycle includes an on-duration and a DRX opportunity. The DRX cycle defines the time interval between periodic repetitions of the on-duration. The on-duration is the time period during which the UE monitors the PDCCH. When the UE is configured with DRX, the UE performs PDCCH monitoring during the on-duration. When the UE successfully detects the PDCCH during the PDCCH monitoring, the UE starts the inactivity timer and remains awake. On the contrary, when the UE fails to detect any PDCCH during the PDCCH monitoring, the UE transitions to a sleep state after the on-duration. Therefore, when DRX is configured, PDCCH monitoring / reception may be performed discontinuously in the time domain in the process and / or method described / proposed above. For example, when DRX is configured, the PDCCH reception timing (e.g., a time slot with a PDCCH SS) may be configured discontinuously according to the DRX configuration in the present disclosure. On the contrary, when DRX is not configured, PDCCH monitoring / reception may be performed continuously in the time domain. For example, when DRX is not configured, the PDCCH reception timing (e.g., a time slot with a PDCCH SS) may be configured continuously in the present disclosure. Regardless of whether DRX is configured, PDCCH monitoring may be restricted during time periods configured as measurement gaps.

[0255] Table 7 describes the DRX operation of the UE (in the RRC_CONNECTED state). Referring to Table 7, DRX configuration information is received through high-layer signaling (e.g., RRC signaling), and DRX on / off is controlled by a DRX command from the MAC layer. Once DRX is configured, the UE may perform PDCCH monitoring discontinuously while executing the above-described / proposed procedures and / or methods.

[0256] [Table 7]

[0257]

[0258] MAC-CellGroupConfig includes configuration information required to configure MAC parameters for a cell group. MAC-CellGroupConfig may also include DRX configuration information. For example, when defining DRX, MAC-CellGroupConfig may include the following information.

[0259] -drx-OnDurationTimer value: defines the duration of the start period of the DRX cycle

[0260] -drx-InactivityTimer value: defines the duration of the time period during which the UE wakes up after detecting a PDCCH opportunity indicating a PDCCH for initial UL or DL ​​data

[0261] -drx-HARQ-RTT-TimerDL value: defines the duration of the maximum time period after receiving a DL initial transmission until a DL retransmission is received

[0262] -drx-HARQ-RTT-TimerDL value: defines the duration of the maximum time period after receiving the UL initial transmission grant until receiving the UL retransmission grant

[0263] -drx-LongCycleStartOffset: defines the duration and start time of the DRX cycle

[0264] -drx-ShortCycle (optional): defines the duration of the short DRX cycle

[0265] When any one of drx-OnDurationTimer, drx-InactivityTimer, drx-HARQ-RTT-TimerDL and drx-HARQ-RTT-TimerDL is running, the UE performs PDCCH monitoring at each PDCCH opportunity and remains in the awake state.

[0266] The above-mentioned embodiments correspond to the combination of elements and features of the present disclosure in a prescribed form. And, unless explicitly mentioned, each element or feature may be regarded as selective. Each element or feature may be implemented in a form that is not combined with other elements or features. In addition, it is possible to implement the embodiments of the present disclosure by partially combining elements and / or features together. The order of operations described for each embodiment of the present disclosure may be modified. Some configurations or features of an embodiment may be included in another embodiment, or may replace the corresponding configuration or features of another embodiment. And, it is obvious to understand that the embodiment is configured by combining claims that do not have a clear reference relationship in the attached claims, or may be included as a new claim by modification after submitting the application.

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

[0268] Industrial Applicability

[0269] The present disclosure is applicable to UE, BS or other devices in a wireless mobile communication system.

Claims

1. A method for receiving a signal by a user equipment UE in a wireless communication system, the method comprising the following steps: Receiving downlink control information DCI via a physical downlink control channel PDCCH; receiving at least one transport block TB through a physical downlink shared channel PDSCH on at least one of the multiple cells configured in the UE based on the DCI; as well as sending hybrid automatic repeat request-acknowledgement HARQ-ACK information for the at least one TB, The DCI supports multi-cell scheduling based on the multiple cells, and The number of ACK / NACK bits included in the HARQ-ACK information is determined based on at least one of a maximum number of cells that can be co-scheduled by the DCI or a maximum number of TBs that can be received by the cells co-scheduled by the DCI.

2. The method according to claim 1, wherein: Based on that a maximum number of TBs per PDSCH is 2 and spatial bundling is not configured in at least one cell among the cells that can be co-scheduled by the DCI, The number of the ACK / NACK bits included in the HARQ-ACK information is determined based on a maximum number of TBs that can be received by the cells co-scheduled by the DCI.

3. The method according to claim 1, wherein: Based on the maximum number of TBs per PDSCH in each of the cells that can be co-scheduled by the DCI being 1 or based on the configuration of spatial bundling, The number of the ACK / NACK bits included in the HARQ-ACK information is determined based on a maximum number of the cells that can be co-scheduled by the DCI.

4. The method according to claim 1, wherein: The maximum number of cells that can be jointly scheduled by the DCI is related to a cell combination including a maximum number of cells among cell combinations that can be scheduled by the DCI.

5. The method according to claim 1, wherein: In the HARQ-ACK information, the ACK / NACK bits are arranged based on a serving cell index of a co-scheduled cell.

6. The method according to claim 1, wherein: The DCI includes information about a downlink assignment index DAI, and The DAI is determined based on a cell with a minimum serving cell index among the cells co-scheduled by the DCI.

7. The method according to claim 1, wherein: HARQ-ACK information related to single-cell scheduling is included in a first subcodebook, and wherein the HARQ-ACK information related to the multi-cell scheduling is included in a second subcodebook.

8. The method according to claim 7, wherein: A HARQ-ACK codebook is configured based on the concatenation of the first subcodebook and the second subcodebook.

9. The method according to claim 7, wherein: The first subcodebook is related to a PDSCH scheduled by a multi-cell scheduling DCI having one actually scheduled cell and a single-cell scheduling DCI, and The second subcodebook is related to a PDSCH scheduled by a multi-cell scheduling DCI having two or more actually scheduled cells. 10 . A computer-readable recording medium having recorded thereon a program for executing the method according to claim 1 .

11. An apparatus for wireless communication, the apparatus comprising: a memory configured to store instructions; as well as A processor configured to perform operations by executing the instructions, the operations comprising: Receiving downlink control information DCI via a physical downlink control channel PDCCH; receiving at least one transport block TB through a physical downlink shared channel PDSCH on at least one of a plurality of cells configured in a user equipment UE based on the DCI; and sending hybrid automatic repeat request-acknowledgement HARQ-ACK information for the at least one TB, The DCI supports multi-cell scheduling based on the multiple cells, and The number of ACK / NACK bits included in the HARQ-ACK information is determined based on at least one of a maximum number of cells that can be co-scheduled by the DCI or a maximum number of TBs that can be received by the cells co-scheduled by the DCI.

12. The device according to claim 11, further comprising: a transceiver, which sends or receives wireless signals under the control of the processor, The device is a user equipment UE in a wireless communication system.

13. The device according to claim 11, wherein: The device is an application specific integrated circuit ASIC or a digital signal processing device for controlling a user equipment UE.

14. A method for sending a signal by a base station in a wireless communication system, the method comprising the following steps: Sending downlink control information DCI to the user equipment via a physical downlink control channel PDCCH; Sending at least one transport block TB on at least one of the multiple cells configured in the user equipment through a physical downlink shared channel PDSCH based on the DCI; as well as receiving hybrid automatic repeat request-acknowledgement HARQ-ACK information for the at least one TB, The DCI supports multi-cell scheduling based on the multiple cells, and The number of ACK / NACK bits included in the HARQ-ACK information is determined based on at least one of a maximum number of cells that can be co-scheduled by the DCI or a maximum number of TBs that can be sent by the cells co-scheduled by the DCI.

15. A base station for sending a signal in a wireless communication system, the base station comprising: Transceiver; as well as a processor configured to: send downlink control information DCI to a user equipment through a physical downlink control channel PDCCH by controlling the transceiver, send at least one transport block TB through a physical downlink shared channel PDSCH on at least one of a plurality of cells configured in the user equipment based on the DCI, and receive hybrid automatic repeat request-acknowledgement HARQ-ACK information for the at least one TB, The DCI supports multi-cell scheduling based on the multiple cells, and The number of ACK / NACK bits included in the HARQ-ACK information is determined based on at least one of a maximum number of cells that can be co-scheduled by the DCI or a maximum number of TBs that can be sent by the cells co-scheduled by the DCI.