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

Abstract

According to one embodiment of the present invention, a terminal determines and reports HARQ‑ACK based on a specific codebook based on the result of receiving multiple PDSCHs, and based on the HARQ‑ACK based on the first type of codebook that has been set for scheduling of multiple PDSCHs, the terminal can perform a first SLIV pruning based on a set of start symbols and length indicator values ​​(SLIVs) of PDSCHs that can be potentially scheduled on each time slot of a bundling window determined based on multiple candidate PDSCHs to HARQ feedback timing values, and perform a second SLIV pruning based on a set of SLIVs of PDSCHs that can be potentially scheduled on at least one time slot that does not even belong to the bundling window.

Description

Technical Field

[0001] The present disclosure relates to a wireless communication system, and more particularly, to a method and apparatus for transmitting / receiving uplink / downlink wireless signals 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] According to one aspect of the present disclosure, a method for receiving a signal by a user equipment (UE) in a wireless communication system may include the following steps: receiving downlink control information (DCI) scheduling multiple physical downlink shared channels (PDSCHs); performing PDSCH reception on at least a portion of the multiple PDSCHs based on the DCI; determining a hybrid automatic repeat request (HARQ)-acknowledgement (ACK) based on a specific codebook based on a result of the PDSCH reception; and sending HARQ-ACK in time slot #N associated with a specific candidate K1 value indicated by the DCI among multiple candidate PDSCH to HARQ feedback timing values ​​(K1 values) configured for the UE.

[0008] When determining HARQ-ACK, based on the HARQ-ACK based on the first type codebook configured for scheduling of multiple PDSCHs, the UE may perform a first start symbol and length indicator value (SLIV) pruning based on a combination of SLIV values ​​of PDSCHs that may be potentially scheduled in each time slot of a bundling window determined based on multiple candidate K1 values, and perform a second SLIV pruning based on a combination of SLIV values ​​of PDSCHs that may be potentially scheduled in at least one time slot that does not belong to the bundling window.

[0009] The first ACK / negative ACK (NACK) sub-payload of each time slot of the bundling window may be determined based on the first SLIV pruning.

[0010] The second ACK / NACK sub-payload of at least one time slot that does not belong to the bundling window may be determined based on the second SLIV pruning.

[0011] The UE may generate a total payload of HARQ-ACK based on the first type codebook by concatenating the first ACK / NACK sub-payload and the second ACK / NACK sub-payload, or arranging the first ACK / NACK sub-payload and the second ACK / NACK sub-payload based on the time sequence of the corresponding time slot.

[0012] At least one time slot not belonging to the bundling window for which the second SLIV pruning is performed may be located before the bundling window in the time domain.

[0013] The at least one time slot not belonging to the bundling window for which the second SLIV pruning is performed may be a time slot for receiving a PDSCH located outside the bundling window among a plurality of PDSCHs.

[0014] A time domain resource allocation (TDRA) field included in the DCI may indicate a row of a TDRA table configured for the UE.

[0015] At least one row of the TDRA table may include multiple {K0, PDSCH mapping type, SLIV} parameter sets, where "K0" may indicate a physical downlink control channel (PDCCH) to PDSCH time slot offset.

[0016] At least one time slot not belonging to the bundling window for performing the second SLIV pruning may be determined based on 'K0' included in a parameter set not corresponding to the last time slot in each row of the TDRA table.

[0017] The bundling window for performing the first SLIV pruning may be determined by combining a plurality of candidate K1 values ​​with the parameter sets corresponding to the last time slot in each row of the TDRA table.

[0018] HARQ-ACK may be generated for a valid PDSCH among a plurality of PDSCHs excluding an invalid PDSCH overlapping an uplink (UL) symbol configured by higher layer signaling.

[0019] The UE may perform each of the first SLIV pruning and the second SLIV pruning while excluding invalid PDSCHs overlapping UL symbols configured by higher layer signaling.

[0020] According to an aspect of the present disclosure, a computer-readable recording medium recording a program for executing the above-mentioned signal receiving method may be provided.

[0021] According to one aspect of the present disclosure, a UE for executing the above-mentioned signal receiving method may be provided.

[0022] According to one aspect of the present disclosure, a device for controlling a UE to perform the above-mentioned signal receiving method may be provided.

[0023] According to one aspect of the present disclosure, a method for sending a signal by a BS in a wireless communication system may include the following steps: sending a DCI that schedules multiple PDSCHs; performing PDSCH transmission on at least a part of the multiple PDSCHs based on the DCI; receiving HARQ-ACK in time slot #N related to a specific candidate K1 value indicated by the DCI among multiple candidate PDSCH to HARQ feedback timing values ​​(K1 values) configured for the UE; and determining a PDSCH to be retransmitted by processing the received HARQ-ACK.

[0024] When determining the PDSCH to be retransmitted, based on the HARQ-ACK based on the first type codebook configured for scheduling of multiple PDSCHs, the BS may perform a first SLIV pruning based on a combination of SLIV values ​​of PDSCHs that can be potentially scheduled in each time slot of a bundling window determined based on multiple candidate K1 values, and perform a second SLIV pruning based on a combination of SLIV values ​​of PDSCHs that can be potentially scheduled in at least one time slot that does not belong to the bundling window.

[0025] According to an aspect of the present disclosure, a BS for performing the above-mentioned signal receiving method may be provided.

[0026] Beneficial Effects

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

[0028] 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

[0029] The accompanying drawings are included to provide a further understanding of the present disclosure and are incorporated into and constitute a part of this application. The accompanying drawings illustrate embodiments of the present disclosure and together with the description are used to explain the principles of the present disclosure. In the accompanying drawings:

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

[0031] Figure 2 Shows the radio frame structure.

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

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

[0034] Figure 5 An exemplary acknowledgement / negative acknowledgement (ACK / NACK) transmission process is shown.

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

[0036] Figure 7 An example of multiplexing control information in the PUSCH is shown.

[0037] Figure 8 Hybrid Automatic Repeat Request (HARQ) process identifier (ID) allocation for multiple Transmission Time Interval (TTI) scheduling according to an embodiment of the present disclosure is shown.

[0038] Fig. 9 Start and length indicator value (SLIV) pruning for multi-TTI scheduling according to an embodiment of the present disclosure is shown.

[0039] Fig.10 Multiple physical downlink shared channel (PDSCH) scheduling and HARQ-ACK reporting according to an embodiment of the present disclosure are shown.

[0040] Fig.11 Multi-TTI PUSCH transmission / reception and HARQ-ACK reception according to an embodiment of the present disclosure are shown.

[0041] Fig.12 and Fig.13 Signal sending and receiving methods according to embodiments of the present disclosure are respectively shown.

[0042] Figures 14 to 17 An example of the communication system 1 and the wireless device applied to the present disclosure is shown.

[0043] Fig.18 An exemplary discontinuous reception (DRX) operation suitable for use with the present disclosure is shown. DETAILED DESCRIPTION

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

[0045] 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).

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

[0047] In the present disclosure, the term "set / setting" may be replaced with "configure / configuration", and the two may be used interchangeably. In addition, conditional expressions (e.g., "if", "in the case of...", or "when...") may be replaced with "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 in the signal transmission / reception between the wireless communication device (e.g., BS and UE) can be derived / understood from the processing of the transmitting (or receiving) side, 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 a 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 a 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 necessarily constitutes an independent invention or that each of them should only be implemented separately. Unless explicitly contradicted with each other, it can be deduced / understood that at least part of the sections, implementations, examples, options, methods, schemes, etc. can be implemented in combination or can be omitted.

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

[0049] Figure 1 Shows physical channels used in a 3GPP NR system and a general signal transmission method using the same.

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

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

[0052] 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).

[0053] 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 service data need to be sent simultaneously. In addition, UCI may be sent aperiodically via PUSCH according to the request / command of the network.

[0054] Figure 2 The 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.

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

[0056] [Table 1]

[0057] <![CDATA[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

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

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

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

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

[0062] [Table 2]

[0063] <![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

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

[0065] 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).

[0066] Figure 3 A 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.

[0067] Figure 4An 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 transmit mode to receive mode switch or a receive mode to transmit mode switch at the BS and UE. Some symbols in a subframe at the time of DL to UL switching may be configured as GP.

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

[0069] 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).

[0070] 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 is 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 parameter set (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 the CORESET may be configured by high-level signaling.

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

[0072] -controlResourceSetId: CORESET related to SS.

[0073] - monitoringSlotPeriodicityAndOffset: PDCCH monitoring periodicity (in time slots) and PDCCH monitoring offset (in time slots).

[0074] - monitoringSymbolsWithinSlot: PDCCH monitoring symbols in a slot (eg, the first symbol of a CORESET).

[0075] -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).

[0076] *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.

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

[0078] [Table 3]

[0079]

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

[0081] [Table 4]

[0082]

[0083] 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).

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

[0085] PDSCH transmits DL data (e.g., DL shared channel transport block (DL-SCH TB)) and uses a modulation scheme such as quadrature phase shift keying (QPSK), hexadecimal 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 based on 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 mapped layer with DMRS and sent through the corresponding antenna port.

[0086] The system information (SIB1) broadcast in the cell includes cell-specific PDSCH configuration information PDSCH-ConfigCommon. PDSCH-ConfigCommon includes a parameter list (or lookup table) pdsch-TimeDomainAllocationList related to the time domain resource allocation for PDSCH. The pdsch-TimeDomainAllocationList may include up to 16 entries (or rows), each of which has a jointly encoded {K0, PDSCH mapping type, PDSCH start symbol and length (SLIV)}. In addition to the pdsch-TimeDomainAllocationList configured by PDSCH-ConfigCommon (in addition), the pdsch-TimeDomainAllocationList may also be provided by the UE-specific PDSCH configuration PDSCH-Config. The pdsch-TimeDomainAllocationList configured in a UE-specific manner may have the same structure as the pdsch-TimeDomainAllocationList configured in a UE-common manner. For K0 and SLIV of the pdsch-TimeDomainAllocationList, reference may be made to the following. Figure 5 The following description.

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

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

[0089] -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 has been 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.

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

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

[0092] [Table 5]

[0093]

[0094] PUCCH format 0 conveys up to 2 bits of UCI and is mapped in a sequence-based manner for 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 for the corresponding SR configuration only when the UE sends a positive SR.

[0095] 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)).

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

[0097] PUCCH format 3 does not support multiplexing of UEs in the same PRBS and transmits UCI of more than 2 bits. In other words, the PUCCH resources of PUCCH format 3 do not include OCC. The modulation symbols and DMRS are sent in TDM.

[0098] 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 resources of PUCCH format 3 include OCC. The modulation symbols and DMRS are sent in TDM.

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

[0100] Figure 5 An exemplary 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 to PDSCH offset K0 and PDSCH to HARQ-ACK report offset K1. For example, DCI format 1_0 and DCI format 1_1 may include the following information.

[0101] - Frequency domain resource assignment: indicates the RB set assigned to PDSCH.

[0102] -Time domain resource assignment: indicates the starting position (e.g., OFDM symbol index) and length (e.g., number of OFDM symbols) of PDSCH in K0 and time slot. As described above, the row index of pdsch-TimeDomainAllocationList provided in a UE-common or UE-specific manner may be indicated by the TDRA field.

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

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

[0105] - PUCCH resource indicator (PRI): indicates a PUCCH resource to be used for UCI transmission among multiple PUCCH resources in a PUCCH resource set.

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

[0107] 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, the HARQ-ACK response may be configured in 2 bits if spatial bundling is not configured, and in 1 bit if spatial bundling is configured. When slot #(n+K1) is designated as the HARQ-ACK transmission timing of multiple PDSCHs, the UCI sent in slot #(n+K1) includes the HARQ-ACK responses for multiple PDSCHs.

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

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

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

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

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

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

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

[0115] -Time domain resource assignment: indicates the slot offset K2 and the starting position (eg OFDM symbol index) and duration (eg 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).

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

[0117] Figure 7An exemplary multiplexing of UCI in PUSCH is shown. When multiple PUCCH resources overlap with PUSCH resources in a time slot and simultaneous PUCCH-PUSCH transmission is not configured in the time slot, UCI can be sent on PUSCH (UCI piggybacking or PUSCH piggybacking) as shown. Figure 7 In the case shown, HARQ-ACK and CSI are carried in PUSCH resources.

[0118] In the NR Rel.15 / 16 system, three HARQ-ACK codebook types are defined according to how the HARQ-ACK bits (payload) are configured: Type 1, Type 2, and Type 3. In the Type 1 codebook, the HARQ-ACK payload is configured according to a combination of a candidate HARQ-ACK timing (K1) set and a candidate PDSCH opportunity (SLIV) set (based on the cell configuration for the corresponding cell) (e.g., a semi-static fixed length codebook based on RRC signaling). In the Type 2 codebook, the codebook size can be dynamically changed according to the number of PDSCHs actually scheduled or the number of corresponding resource allocations (e.g., DAI). In the Type 3 codebook, the HARQ-ACK payload (e.g., a one-time A / N report) is configured by mapping the HARQ-ACK bits to the corresponding HPN based on the maximum number of HARQ processes (based on the cell configuration for the corresponding cell).

[0119] Multi-TTI scheduling and HARQ-ACK feedback based on single DCI

[0120] 3GPP (e.g., Rel-15 and Rel-16) has recently been working on the standardization of a 5G system called New RAT (NR). The NR system seeks to support multiple logical networks in a single physical system. To this end, the NR system is designed to support services with various requirements (e.g., eMBB, mMTC, and URLLC) by performing / modifying analog / hybrid beamforming operations, etc., taking into account the characteristics of various OFDM parameter sets (e.g., OFDM symbol duration, subcarrier spacing (SCS), and CP length), a wide operating frequency range (up to about 50 GHz), and high frequency bands.

[0121] In Rel-17, it is considered necessary to develop an NR (i.e., high frequency (HF) NR) system operating in a higher frequency band (e.g., 60 GHz to 70 GHz or above) than the NR system based on the conventional Rel-15 / 16. Considering the higher frequency and wider bandwidth than in the conventional NR and the radio channel characteristics such as larger phase noise and / or larger Doppler shift caused by the high frequency band, it is considered to introduce and apply a new OFDM parameter set based on a larger SCS (e.g., 240 KHz, 480 KHz, or 960 KHz) than the SCS of the conventional NR (e.g., the parameter set defined in 3GPP TS 38.211, such as 15 KHz, 30 KHz, 60 KHz, and 120 KHz).

[0122] When a large SCS is used in an HF NR system, the OFDM symbol duration and the time slot duration are also shortened (for example, when the SCS is increased N times in the frequency domain, the symbol duration and / or the time slot duration is reduced to 1 / N in the time domain). Therefore, a cell plan that also reduces the cell coverage can be considered. However, otherwise (for example, when the (target) cell coverage is maintained corresponding to the traditional NR level, or when the SCS of the system is increased from the traditional NR SCS to the large SCS of HF NR, but the (target) cell coverage is not reduced inversely proportional to the increase in SCS), it may be necessary to supplement the coverage of the physical channel / signal transmission (for example, when processing the physical channel / signal, the coverage is extended / supplemented so that the DL physical channel / signal can reach the UE at the edge / border of the target cell coverage or the UL physical channel / signal sent from the UE at the edge / border of the target cell coverage reaches the BS). In addition, since the use of a large SCS also reduces the CP length, it is necessary to consider the influence of the delay spread and / or phase noise and / or beam switching time of the radio channel.

[0123] The term "beam" may be replaced with a (beamformed) signal / channel / resource transmitted through the corresponding beam. For example, the index of a beam may generally be represented as an index of a signal / channel / resource corresponding to the beam. Alternatively, the term "beam" may be replaced with a signal / channel / resource associated with the beam, thereby identifying the beam. When different Tx beams are configured for each RO, the BS may identify the TX beam used by the UE by the RO index or the SSB index associated with the RO.

[0124] In addition, when the OFDM symbol and time slot duration are reduced due to the use of a large SCS as described above, the transmission / reception operations (e.g., PDCCH monitoring) to be performed by the UE in one symbol / time slot duration need to be processed quickly, and considering the UE processing burden (related to the PDCCH monitoring period), it is possible to consider introducing a multi-TTI scheduling scheme that simultaneously schedules multiple multiplexed PDSCHs (e.g., at least part of the PDSCHs are TDM) through one DCI.

[0125] Therefore, the present disclosure proposes a method for configuring and signaling / applying multi-TTI (scheduling) DCI field information for simultaneously scheduling multiple PDSCHs (and / or multiple PUSCHs) (each carrying one or more separate TBs), and a method for configuring HARQ-ACK (i.e., A / N) feedback related to the reception of multiple PDSCHs scheduled by DCI. For example, the frequency bands that can be used to schedule multiple PDSCHs through one DL DCI may include (but are not limited to) 120KHz, 480kHz and / or 960kHz.

[0126] Although the present disclosure is described in the context of multi-PDSCH scheduling based on DL grant DCI for ease of description, those skilled in the art will appreciate that multi-TTI scheduling is also applied to multi-PUSCH scheduling based on UL grant DCI, and is not limited to multi-PDSCH scheduling based on DL grant DCI. In other words, the term multi-TTI scheduling can be understood to cover both DL DCI for scheduling multiple PDSCHs multiplexed in the time domain and UL DCI for scheduling multiple PUSCHs multiplexed in the time domain.

[0127] The meanings of the terms used in this article are summarized below. To help understand the terms, please refer to Figure 5 / Figure 6 and its description.

[0128] - K0 (DL assignment to PDSCH offset): the slot interval between the DCI transmission slot and the PDSCH transmission slot (scheduled by the corresponding DCI).

[0129] - SLIV (Start and Length Indicator Value): Information on the start symbol and symbol duration (or end symbol) of a PDSCH (PDSCH opportunity).

[0130] - Mapping type: information indicating whether the position of the DMRS symbol of the PDSCH is determined based on a symbol index within a slot duration or within a PDSCH duration.

[0131] - TDRA (Time Domain Resource Assignment) table: includes multiple {K0, SLIV, mapping type} combinations (configured by RRC) (one combination is mapped to each of the multiple rows in the table). A specific row is indicated by DCI.

[0132] - K1 (PDSCH-to-HARQ_feedback timing indicator): the time slot interval between the PDSCH transmission time slot and the HARQ-ACK transmission time slot (for corresponding PDSCH reception).

[0133] (Proposal 1) Configuration of PDSCH resource allocation field

[0134] (Proposal 1-A) Configuration of Time Domain RA (TDRA) Field Information

[0135] The TDRA field of the DL grant DCI may schedule multiple PDSCHs, or the TDRA field of the UL grant DCI may schedule multiple PUSCHs.

[0136] 1) Option 1

[0137] A. For each state indicated by the TDRA field of the multi-TTI DCI, N entries may be configured based on an entry (notified by a higher layer signal) consisting of {K0, SLIV, mapping type}. N is the number of scheduled PDSCHs, and may have different values ​​for each TDRA field state (e.g., N>=1). For example, one TDRA field state may be mapped to N entries based on higher layer signaling, and N PDSCHs may be allocated to continuous / non-continuous time slots. Those skilled in the art will appreciate that for PUSCH, instead of K0, K2 may be provided.

[0138] 2) Option 2

[0139] A. For each state indicated by the TDRA field of the multi-TTI DCI, N entries may be configured in the form of {K0, SLIV, mapping type} for the first PDSCH (corresponding to the first entry (index)), and in the form of {D, SLIV, mapping type} for subsequent PDSCHs. D configured for the nth PDSCH may be applied as the slot interval between the previous (n-1)th PDSCH transmission slot and the nth PDSCH transmission slot.

[0140] 3) Option 3

[0141] A. For each state indicated by the TDRA field of the multi-TTI DCI, a K0 value and N entries may be configured, each entry including {SLIV, mapping type}. K0 may be applied to the first PDSCH (corresponding to the first entry (index)), and subsequent PDSCHs may be sent sequentially in consecutive time slots (after the transmission time slot of the first PDSCH) (each time slot is used for one PDSCH).

[0142] 4) Option 4

[0143] A. For each state indicated by the TDRA field of the multi-TTI DCI, a K0 value, a D value, and N entries may be configured, each entry including {SLIV, mapping type}. K0 may be applied to the first PDSCH (corresponding to the first entry (index)), and the D value may be applied to subsequent PDSCHs in common.

[0144] (Proposal 1-B) Configuration of Frequency Domain RA (FDRA) Field Information

[0145] 1) Option 1

[0146] A. The size of an RBG as a resource allocation unit of RBG-based FDRA and the size of a related FDRA field may be determined / set according to the number of PDSCHs scheduled by multi-TTI DCI.

[0147] i. For example, when the number of scheduled PDSCHs is equal to or less than M, the conventional RBG size (e.g., X RBs) and the conventional FDRA field size are maintained. Conversely, when the number of scheduled PDSCHs is greater than M, the RBG size is greater than the conventional size (X RBs), and thus the FDRA field size may be reduced. (In this case, specifically, M=1).

[0148] 2) Option 2

[0149] A. The resource granularity of RIV-based FDRA and the size of the related FDRA field may be determined / set according to the number of PDSCHs scheduled by multi-TTI DCI.

[0150] i. For example, when the number of scheduled PDSCHs is equal to or less than M, the conventional RIV method with 1-RB granularity and the conventional FDRA field size are maintained. Conversely, when the number of scheduled PDSCHs is greater than M, a RIV method based on K-RB (K>1) granularity may be used, and thus the FDRA field size may be reduced. (In this case, specifically, M=1).

[0151] (Proposal 2) Rate Matching Indicator (RMI) field information

[0152] 1) Option 1

[0153] A. Rate matching (pattern) information indicated by the RMI field of the multi-TTI DCI may be commonly applied to multiple PDSCHs scheduled by the DCI. For example, the DCI may include one RMI field commonly applied to multiple PDSCHs.

[0154] 2) Option 2

[0155] A. The rate matching (pattern) information indicated by the RMI field of the multi-TTI DCI may be applied only to one specific PDSCH (eg, the first or last PDSCH in time) among multiple PDSCHs scheduled by the DCI.

[0156] 3) Option 3

[0157] A. Among multiple PDSCHs scheduled by multi-TTI DCI, the PDSCH to which rate matching (pattern) information indicated by the RMI field of the multi-TTI DCI is applied may be indicated by the same DCI or by RRC.

[0158] (Proposal 3) ZP-CSI-RS Trigger (ZCR) field information

[0159] 1) Option 1

[0160] A. The ZP-CSI-RS information (rate matching information of the ZP-CSI-RS) indicated by the ZCR field of the multi-TTI DCI may be commonly applied to all multiple PDSCHs scheduled by the DCI. For example, the DCI may include a ZCR field commonly applied to multiple PDSCHs. The aperiodic ZP CSI-RS triggered by the ZCR field may be applied to all time slots including the PDSCH scheduled by the DCI.

[0161] 2) Option 2

[0162] A. ZP-CSI-RS information (rate matching information of ZP-CSI-RS) indicated by the ZCR field of multi-TTI DCI may be applied only to a specific PDSCH (eg, the first or last PDSCH in time) among multiple PDSCHs scheduled by DCI.

[0163] 3) Option 3

[0164] A. Among multiple PDSCHs scheduled by multi-TTI DCI, the PDSCH to which the ZP-CSI-RS information (rate matching information of ZP-CSI-RS) indicated by the ZCR field of the multi-TTI DCI is applied may be indicated by the same DCI or by RRC.

[0165] (Proposal 4) Configuration of NDI, RV and MCS fields

[0166] (Proposal 4-A) Configuration of NDI field information

[0167] 1) Option 1

[0168] A. When the maximum number of TBs that can be transmitted on one PDSCH is set to 2, when K or fewer PDSCHs are scheduled by multi-TTI DCI, a 1-bit NDI field may be configured / indicated for each TB (i.e., two 1-bit NDI fields are configured and indicated for each PDSCH). Conversely, when more than K PDSCHs are scheduled by multi-TTI DCI, a 1-bit NDI field is configured / indicated for each PDSCH (i.e., two TBs transmitted on one PDSCH are scheduled based on the same 1-bit (TB common) NDI value).

[0169] B. Regarding the value of K in the above examples, in one example, K=1, or in another example, K=N / 2. In another example, the value of K may be configured by RRC.

[0170] C. In another method, it may be configured by RRC whether the method of Option 1 is to be applied, or a 1-bit NDI field is always configured / indicated for each TB regardless of the number of scheduled PDSCHs.

[0171] D. In another example, when spatial bundling is not configured for HARQ-ACK feedback, a 1-bit NDI field may always be configured / indicated for each TB regardless of the number of scheduled PDSCHs. When spatial bundling is configured for HARQ-ACK feedback, the method of Option 1 may be applied, or a 1-bit (TB common) NDI field may always be configured / indicated for each PDSCH regardless of the number of scheduled PDSCHs.

[0172] E. In another example, when spatial bundling is not configured for HARQ-ACK feedback, a 1-bit NDI field may be always configured / indicated for each TB regardless of the number of scheduled PDSCHs. When spatial bundling is configured for HARQ-ACK feedback, it may be configured by RRC whether to apply the method of Option 1, (or always configure / indicate a 1-bit (TB common) NDI field for each PDSCH regardless of the number of scheduled PDSCHs) or always configure / indicate a 1-bit NDI field for each TB regardless of the number of scheduled PDSCHs.

[0173] 2) Option 2

[0174] A. In the case where the maximum number of TBs transmittable on one PDSCH is set to 2, when K or fewer PDSCHs are scheduled by multi-TTI DCI, up to two TBs may be transmitted on each PDSCH (in this case, two 1-bit NDI fields are configured / indicated for each PDSCH, i.e., a 1-bit NDI field is configured / indicated for each TB (each of two TBs) transmittable on the PDSCH). On the contrary, when more than K PDSCHs are scheduled by multi-TTI DCI, only one TB may be transmitted on each PDSCH (in this case, one 1-bit NDI field may be configured / indicated for each PDSCH by DCI, i.e., a 1-bit NDI field may be configured / indicated for only one TB transmittable on the PDSCH).

[0175] B. Regarding the value of K in the above examples, in one example, K=1, or in another example, K=N / 2. In another example, the value of K may be configured by RRC.

[0176] C. For convenience, the operation method of Option 2 based on K=1 is referred to as "2-TB for single PDSCH only".

[0177] (Proposal 4-B) Configuration of RV field information

[0178] 1) Option 1

[0179] A. In the case where the maximum number of TBs that can be transmitted on one PDSCH is set to 2, when K or fewer PDSCHs are scheduled by multi-TTI DCI, a 2-bit RV field may be configured / indicated for each TB (i.e., two 2-bit RV fields may be configured / indicated for each PDSCH). Conversely, when more than K PDSCHs are scheduled by multi-TTI DCI, a 2-bit RV field may be configured / indicated for each PDSCH (i.e., two TBs transmitted on one PDSCH may be scheduled based on the same 2-bit RV value).

[0180] B. Regarding the value of K in the above examples, in one example, K=1, or in another example, K=N / 2. In another example, the value of K may be configured by RRC.

[0181] 2) Option 2

[0182] A. In the case where the maximum number of TBs that can be transmitted on one PDSCH is set to 2, when K or fewer PDSCHs are scheduled by multi-TTI DCI, a 2-bit RV field may be configured / indicated for each TB (i.e., two 2-bit RV fields may be configured / indicated for each PDSCH). Conversely, when more than K PDSCHs are scheduled by multi-TTI DCI, a 1-bit RV field may be configured / indicated for each PDSCH (i.e., two TBs transmitted on one PDSCH may be scheduled based on the same 1-bit RV value).

[0183] B. Regarding the value of K in the above examples, in one example, K=1, or in another example, K=N / 2. In another example, the value of K may be configured by RRC.

[0184] 3) Option 3

[0185] A. When the maximum number of TBs that can be transmitted on one PDSCH is set to 2, when K or fewer PDSCHs are scheduled by multi-TTI DCI, a 1-bit RV field may be configured / indicated for each TB (i.e., two 1-bit RV fields may be configured / indicated for each PDSCH). Conversely, when more than K PDSCHs are scheduled by multi-TTI DCI, a 1-bit RV field may be configured / indicated for each PDSCH (i.e., two TBs transmitted on one PDSCH may be scheduled based on the same 1-bit RV value).

[0186] B. Regarding the value of K in the above examples, in one example, K=1, or in another example, K=N / 2. In another example, the value of K may be configured by RRC.

[0187] 4) Option 4

[0188] A. In the case where the maximum number of TBs transmittable on one PDSCH is set to 2, when K or fewer PDSCHs are scheduled by multi-TTI DCI, up to 2 TBs may be transmitted on each PDSCH (in this case, two 2-bit (or 1-bit) RV fields may be configured / indicated for each PDSCH, i.e., a 2-bit (or 1-bit) RV field may be configured / indicated for each TB (each of two TBs) transmittable on the PDSCH). On the contrary, when more than K PDSCHs are scheduled by multi-TTI DCI, only one TB may be transmitted on each PDSCH (in this case, a 1-bit (or 2-bit) RV field may be configured / indicated for each PDSCH, i.e., a 1-bit (or 2-bit) RV field may be configured / indicated for one TB transmittable on the PDSCH).

[0189] B. Regarding the value of K in the above examples, in one example, K=1, or in another example, K=N / 2. In another example, the value of K may be configured by RRC.

[0190] 5) Notes

[0191] A. In options 1 / 2 / 3 / 4, the number of PDSCHs may mean the number of valid PDSCHs actually transmitted excluding invalid PDSCHs whose transmission is skipped / discarded due to overlap with specific UL symbols (e.g., semi-statically configured by higher layer signaling such as tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated), or the total number of PDSCHs indicated by multi-TTI DCI regardless of whether the PDSCHs are actually transmitted.

[0192] B. In another example, when multiple PDSCHs (or PUSCHs) are scheduled by multi-TTI DCI (for example, the state composed of / configured by multiple SLIVs is indicated by the TDRA field), it may be specified that the number of valid PDSCHs (or PUSCHs) actually transmitted among the multiple PDSCHs (or PUSCHs) is always 2 or more (the UE may expect / assume such scheduling from the BS) except for the invalid PDSCHs (or PUSCHs) whose transmission is discarded due to temporal overlap with specific (for example, semi-statically configured) UL (or DL) symbols. Otherwise, when the number of valid PDSCHs (or PUSCHs) is less than 2, the UE may discard the multi-TTI DCI considering that the multi-TTI DCI is an inconsistent PDCCH.

[0193] C. When the SCell sleep indication indicating switching to the sleep BWP is executed, and the sleep BWP is configured to allow the UE to skip PDCCH monitoring in a specific SCell without PDSCH scheduling through the traditional single TTI DCI, the 3 bits corresponding to the 1-bit NDI and 2-bit RV in the DCI are reinterpreted as part of the SCell sleep indication information.

[0194] When SCell sleep indication is performed without PDSCH scheduling via multi-TTI DCI, alternative 1) a 1-bit DNI and a 2-bit RV configured to correspond to one indicated PDSCH under the constraint that only one PDSCH (e.g., a single SLIV) is always indicated by the TDRA field of the DCI may be reinterpreted as SCell sleep indication information, alternative 2) the first or last 3 bits of the total bit set including (one or more) NDI fields and RV fields corresponding to (one or more) PDSCHs indicated by the DCI without the constraint of alternative 1 may be reinterpreted as SCell sleep indication information, or alternative 3) the first or last bit of the (one or more) NDI field set corresponding to (one or more) PDSCHs indicated by the DCI and the first or last 2 bits of the (one or more) RV field set corresponding to (one or more) PDSCHs may be reinterpreted as SCell sleep indication information without the constraint of alternative 1.

[0195] (Proposal 4-C) Configuration of MCS field information

[0196] 1) Option 1

[0197] A. When the maximum number of TBs that can be transmitted on one PDSCH is set to 2, when K or less PDSCHs are scheduled by multi-TTI DCI, up to two TBs can be transmitted on each PDSCH (in this case, two MCS fields can be configured / indicated for each PDSCH by DCI, that is, the MCS field can be configured / indicated for each TB (each of two TBs) that can be transmitted on the PDSCH), and when more than K PDSCHs are scheduled by multi-TTI DSCI, only one TB can be transmitted on each PDSCH (in this case, one MCS field can be configured / indicated for each PDSCH by DCI, that is, the MCS field can be configured / indicated for only one TB that can be transmitted on the PDSCH).

[0198] B. Regarding the value of K in the above examples, in one example, K=1, or in another example, K=N / 2. In another example, the value of K may be configured by RRC.

[0199] 2) Notes

[0200] A. When more than K PDSCHs are scheduled by multi-TTI DCI, only one TB can be sent on each PDSCH based on the above proposal. Therefore, the number of MCS fields, RV fields, and NDI fields configured / indicated by DCI is reduced. In this case, unused MCS / RV / NDI bits can be used to indicate other information.

[0201] B. For example, in a state where multiple PDSCHs (more than K PDSCHs) scheduled by one multi-TTI DCI have been grouped into multiple (e.g., 2) groups, HARQ-ACK feedback corresponding to each individual group may be sent by applying / using the HARQ-ACK timing and PUCCH resources indicated by the individual K1 and PRI fields of the group. Unused MCS / RV / NDI bits may be used to configure the (individual) K1 and PRI fields based on the group.

[0202] (Proposal 5) Configuration of HARQ process ID information

[0203] 1) Option 1

[0204] A. When some specific PDSCHs among multiple PDSCHs scheduled by multi-TTI DCI overlap with specific UL symbols (e.g., UL symbols statically configured by high-layer signaling such as tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated), the transmission and reception of specific PDSCHs may be skipped / discarded. In this case, consecutive HARQ process IDs starting from the HARQ process ID indicated by the DCI may be sequentially allocated to only the PDSCHs actually transmitted / received (not the scheduled PDSCHs) in time. For example, under the assumption that a single DL grant DCI schedules 8 PDSCHs and two PDSCHs collide with UL symbols and are therefore discarded, 6 consecutive HARQ process IDs {HARQ process ID#n+1 to HARQ process ID#n+6} may be sequentially allocated to a total of 6 valid PDSCHs.

[0205] Figure 8 FIG. 4 shows an exemplary HARQ process ID allocation for multi-TTI scheduling. Figure 8 , assuming that the TDRA field indicates a row index k and the HARQ process ID field indicates n in the DCI. In the TDRA table, the index row includes a total of three SLIV values ​​corresponding to PDSCH 1, PDSCH 2, and PDSCH3 (in time order). Since the SLIV value of PDSCH 2 overlaps with the U symbol, PDSCH 2 becomes an invalid PDSCH. Therefore, the HARQ process ID is only sequentially / continuously allocated to valid PDSCH 1 and PDSCH 3 except the invalid PDSCH.

[0206] Therefore, regarding the NDI and RV fields corresponding to each PDSCH, consecutive NDI / RV fields starting from the last (or first) NDI / RV field in the DCI may temporally correspond to only the PDSCH that is actually transmitted / received.

[0207] Similarly, the UL grant DCI may sequentially allocate HARQ process IDs to valid PUSCHs except for invalid PUSCHs that collide with semi-statically configured DL symbols and are thus discarded.

[0208] 2) Option 2

[0209] A. When some specific PDSCHs among multiple PDSCHs scheduled by multi-TTI DCI overlap with specific (e.g., semi-statically configured) UL symbols, the transmission and reception of the specific PDSCHs may be discarded. In this case, consecutive HARQ process IDs starting from the HARQ process ID indicated by the DCI may be allocated to all PDSCHs scheduled by the DCI in chronological order, regardless of whether the PDSCHs are actually transmitted / received.

[0210] A. Therefore, consecutive NDI / RV fields starting from the last (or first) NDI / RV field in the DCI may correspond to all PDSCHs scheduled by the DCI in time sequence, regardless of whether the PDSCHs are actually transmitted / received.

[0211] 3) Notes

[0212] A. When some specific PDSCHs among multiple PUSCHs scheduled with multi-TTI DCI overlap with specific (eg, semi-statically configured) DL symbols, the above method can also be applied by determining the HARQ process ID and the corresponding NDI / RV field for each PUSCH.

[0213] B. In order to prevent complexity / ambiguity in determining NDI / RV, CBGTI / CBGFI, HARQ-ACK timing and PDSCH TCI / QCL information as well as HARQ process ID and configuration corresponding fields, it may be specified that the first of multiple PDSCH / PUSCHs scheduled / indicated by multi-TTC DCI is always scheduled / indicated by DCI as a valid PDSCH / PUSCH that does not overlap with a specific (e.g., semi-statically configured) UL / DL symbol (the UE assumes such scheduling). Therefore, when the first PDSCH / PUSCH scheduled / indicated by multi-TTI DCI overlaps with a specific (e.g., semi-statically configured) UL / DL symbol, the UE may discard the DCI (treat the DCI as an inconsistent PDCCH).

[0214] (Proposal 6) Configuration of CBGTI and CBGFI field information

[0215] 1) Option 1

[0216] A. In the case of configuring PDSCH transmission based on up to M CB groups (CBGs), when K or fewer PDSCHs are scheduled by multi-TTI DCI, an M-bit CBG transmission indicator (CBGTI) field and a 1-bit CBG clear indicator (CBGFI) field may be configured / indicated for each PDSCH, while when more than K PDSCHs are scheduled by multi-TTI DCI, neither the CBGTI field nor the CBGFI field may be configured / indicated (i.e., all scheduled PDSCHs may be sent at the TB level (not based on CBG)).

[0217] B. Regarding the value of K in the above examples, in one example, K=1, or in another example, K=N / 2. In another example, the value of K may be configured by RRC.

[0218] C. For convenience, the operation method of Option 1 based on K=1 is referred to as "CBG for single PDSCH only".

[0219] 2) Option 2

[0220] A. In the case of configuring PDSCH transmission based on up to M CBGs, when K or less PDSCHs are scheduled by multi-TTI DCI, only one 1-bit CBGFI field may be configured / indicated, and an M-bit CBGTI field may be configured / indicated for each PDSCH, while when more than K PDSCHs are scheduled by multi-TTI DCI, neither the CBGTI field nor the CBGFI field may be configured / indicated (i.e., all scheduled PDSCHs may be sent at the TB level (not based on CBG)).

[0221] B. The value indicated by the single 1-bit CBGFI field may be commonly applied to all multiple scheduled PDSCHs, or only to a specific one (eg, the first or last one in time) of the multiple PDSCHs.

[0222] C. Regarding the value of K in the above examples, in one example, K=2, or in another example, K=N / 2. In another example, the value of K may be configured by RRC.

[0223] 3) Notes

[0224] A. In option 1 / 2, the number of PDSCHs may mean the number of valid PDSCHs actually sent excluding invalid PDSCHs that overlap with specific (e.g., semi-statically set) UL symbols and whose transmission is discarded, or may mean the total number of PDSCHs indicated by multi-TTI DCI, regardless of whether they are actually sent.

[0225] B. Based on the above proposal, the size or existence of specific fields (e.g., NDI, RV, MCS, CBGTI, CBGFI, etc.) in multi-TTI DCI can be determined differently depending on whether the number of PDSCHs scheduled by the DCI is equal to or less than K or greater than K, and when different K values ​​are defined / set between specific fields, there may be a total of L different K values ​​{K_1,...,K_L}.

[0226] i. Alternatively, the same K value may be defined / set between specific fields, so L=1.

[0227] C. In addition, under the assumption that the maximum number of PDSCHs that can be indicated / scheduled by the TDRA field of the multi-TTI DCI is K_max, there may be a total of L+1 different K values ​​{K_1, ..., K_L, K_max}.

[0228] D. Therefore, the total DCI payload size can be calculated for each of the L+1 different K values ​​{K_1, ..., K_L, K_max} under the assumption that as many PDSCHs as the corresponding K value are scheduled (by multi-TTI DCI), and the maximum value of the calculated DCI payload sizes corresponding to the L+1 K values ​​can be determined as the final payload size of the multi-TTI DCI (format).

[0229] (Proposal 7) Signaling of DAI field information (based on signaling type 2A / N codebook configuration)

[0230] 1) Signaling of counter-DAI and total-DAI in DL DCI

[0231] A. The case where one PDSCH is scheduled by any DCI (e.g., the existing single-TTI DCI or multi-TTI DCI) is defined as a single-PDSCH case, and the case where multiple PDSCHs are scheduled by multi-TTI DCI is defined as a multi-PDSCH case. Then, the counter / total-DAI value may be independently determined and signaled for each of the single-PDSCH case and the multi-PDSCH case (i.e., the DCI / PDSCH sequence / sum scheduled for each case may be independently determined / signaled).

[0232] B. In other words, the DCI corresponding to the single PDSCH case may determine and signal the DAI value for only the single PDSCH case, and the DCI corresponding to the multiple PDSCH case may determine and signal the DAI value for only the multiple PDSCH case. In other words, the C-DAI / T-DAI related to the single PDSCH case may be included in the DCI related to the single PDSCH case, and the C-DAI / T-DAI related to the multiple PDSCH case may be included in the DCI related to the multiple PDSCH case.

[0233] C. The number of A / N bits corresponding to one DAI in the case of multiple PDSCHs can be determined based on the maximum number of TBs that can be scheduled by any (serving cell) multiple TTIDCI (including the case where spatial bundling is not configured) or the maximum number of PDSCHs (including the case where spatial bundling is configured).

[0234] D. The above method can be applied to the case where CBG-based PDSCH transmission is not configured.

[0235] 2) Signaling of UL (total) DAI in UL DCI

[0236] A. A UL DAI value may be signaled for each of a single PDSCH case and a multiple PDSCH case (ie, two UL DAI values ​​may be signaled by one DCI, indicating total-DAI information for a single PDSCH case and total-DAI information for a multiple PDSCH case, respectively).

[0237] B. The above method can be applied to the case where CBG-based PDSCH transmission is not configured.

[0238] 3) DAI signaling when CBG-based PDSCH transmission is configured

[0239] A. The case where a CBG-based PDSCH transmission is scheduled by a specific DCI (e.g., a DCI including a CBGTI field / signaling) is defined as a CBG PDSCH case, the case where a TB-based PDSCH transmission is scheduled by any DCI (i.e., one TB-based PDSCH transmission) is defined as a single PDSCH case, and the case where multiple (TB-based) PDSCH transmissions are scheduled by multi-TTI DCI (i.e., multiple TB-based PDSCH transmissions) is defined as a multi-PDSCH case. Then, the counter / total-DAI value may be determined / signaled as follows.

[0240] B. Option 1: The counter / total-DAI value may be independently determined and signaled for each of the three cases (i.e., single PDSCH case, multiple PDSCH case, and CBG PDSCH case). Regarding UL DAI, the UL DAI value may be signaled for each of the above three cases (single PDSCH case, multiple PDSCH case, and CBG PDSCH case) via DCI.

[0241] C. Option 2: If the multi-PDSCH case and the CBG PDSCH case are jointly defined as a multi-A / N PDSCH case, the counter / total-DAI value may be independently determined and signaled for each of the two cases (ie, the single PDSCH case and the multi-A / N PDSCH case).

[0242] D. In the case of option 2, the DCI corresponding to a single PDSCH may only signal the determined DAI value of the single PDSCH case, and the DCI corresponding to a multiple A / N PDSCH case (i.e., a multiple PDSCH case or a CBG PDSCH case) may only signal the determined DAI value of the multiple A / N PDSCH case (i.e., a multiple PDSCH case and a CBG PDSCH case).

[0243] E. In the case of multiple A / N PDSCH, when the maximum number of TBs that can be scheduled by any multi-TTI DCI (in the serving cell) (including the case where spatial bundling is not configured) or the maximum number of PDSCHs (including the case where spatial bundling is configured) is defined as A, and the maximum number of CBGs configured for any PDSCH transmission (in the serving cell) is defined as B, the number of A / N bits corresponding to one DAI can be determined based on the larger value between A and B.

[0244] (Proposal 8) HARQ timing field information (configuration of type 1 / 2A / N codebook based on HARQ timing field information)

[0245] 1) A / N timing determination and A / N payload configuration for type 2 A / N codebook

[0246] A. The A / N timing (time slot) can be determined by applying the K1 value (indicated by multi-TTI DCI) based on the last (or first) PDSCH transmission time slot (in time) among the multiple PDSCHs scheduled by DCI, and the A / N feedback for all multiple PDSCHs scheduled by DCI can be sent simultaneously at the (same) A / N timing.

[0247] B. Therefore, the counter / total-DAI value can be determined / signaled only between multi-TTI DCIs indicating the A / N timing corresponding to the last (or first) PDSCH transmission time slot as the same time slot, and the A / N feedback for all multiple PDSCHs scheduled by the multi-TTI DCI (indicating the A / N timing corresponding to the last (or first) PDSCH transmission time slot as the same time slot) can be multiplexed and sent at the same A / N timing.

[0248] C. In the above example, the last (or first) PDSCH may refer to the last (or first) of the valid PDSCHs actually transmitted, excluding the invalid PDSCHs that overlap with specific (e.g., semi-statically set) UL symbols and whose transmission is therefore discarded, or the last (or first) of the PDSCHs indicated by the multi-TTI DCI regardless of whether they are actually transmitted.

[0249] 2) A / N timing determination and A / N payload configuration for type 1 A / N codebook

[0250] A. The A / N timing (time slot) can be determined by applying the K1 value (indicated by multi-TTI DCI) based on the last (or first) PDSCH transmission time slot (in time) among the multiple PDSCHs scheduled by DCI, and the A / N feedback for all multiple PDSCHs scheduled by DCI can be sent simultaneously at the (same) A / N timing.

[0251] B. Therefore, A / N feedback (for all multiple PDSCHs scheduled by multi-TTI DCI) can be multiplexed and sent at the same A / N timing only between multi-TTI DCI indicating the A / N timing corresponding to the last (or first) PDSCH transmission time slot as the same time slot (single-TTI DCI indicating the A / N timing corresponding to the last (or first) PDSCH transmission time slot as the same time slot).

[0252] C. In the above example, the last (or first) PDSCH may refer to the last (or first) of the valid PDSCHs actually transmitted, excluding the invalid PDSCHs that overlap with specific (e.g., semi-statically set) UL symbols and whose transmission is therefore discarded, or the last (or first) of the PDSCHs indicated by the multi-TTI DCI regardless of whether they are actually transmitted.

[0253] D. In a state where a set of multiple (e.g., N) candidate K1 values ​​(e.g., a set of PDSCH to HARQ feedback timing indicator values ​​that can be indicated by DCI) is set, in the case of a conventional type 1 codebook, a combination of all PDSCH opportunities (SLIVs) that can be transmitted in a DL slot that is K1 DL slots earlier than an A / N transmission slot is calculated for each K1 value (based on the serving cell configuration for the corresponding serving cell), and an A / N sub-payload corresponding to the corresponding DL slot can be configured (including determining the A / N bit position / sequence corresponding to each SLIV). (This is defined as "SLIV pruning"). The process of determining a combination of transmittable PDSCH opportunities (SLIVs) in SLIV pruning will be described in more detail. One or more non-overlapping PDSCHs can be scheduled for the UE in each DL slot (e.g., index #N-candidate K1 value). The number of non-overlapping PDSCHs (the maximum number of non-overlapping PDSCHs that can be scheduled in the corresponding time slot) can be determined based on a combination of configured SLIV values ​​(e.g., a combination of SLIVs configured by pdsch-TimeDomainAllocationList and indicated by the TDRA field of the DCI). The process of pruning potential overlapping PDSCHs (i.e., incompatible / mutually exclusive PDSCHs due to overlap are counted as at most one PDSCH transmission) and determining (schedulable / compatible potential) non-overlapping PDSCHs based on the SLIV value set for the UE is called SLIV pruning. In the case of the existing type 1 codebook, the A / N sub-payload configured by SLIV pruning can be cascaded for N K1 values ​​to configure the entire A / N codebook (e.g., refer to Section 9.1.2 of 3GPP TS 38.213 V16.2.0).

[0254] For convenience of description, the set of (N) DL time slots corresponding to each K1 value may be referred to as a bundling window corresponding to the A / N transmission time slots. Fig. 9 Under the assumption shown, the bundling window is the period from time slot #N-3 to time slot #-2.

[0255] E. It may happen that among multiple PDSCH transmission time slots scheduled (or schedulable) by a multi-TTI DCI that indicates (or can indicate) a specific time slot as A / N timing (corresponding to the last (or first) PDSCH transmission time slot), the specific time slot does not belong to the bundling window corresponding to the A / N transmission time slot.

[0256] For example, the A / N codebook determined according to the existing SLIV pruning method for conventional single PDSCH scheduling may not cover at least part of multiple scheduled PDSCHs. Fig. 9, assuming that (i) two rows of the TDRA table may be indicated by a multi-PDSCH DCI, and (ii) each row includes two SLIVs (i.e., each row is related to the scheduling of two PDSCHs), and (iii) the K1 slot offset value as the PDSCH to HARQ-ACK timing is set to 2 (e.g., K1 value set = {2,3}). When PDSCH1 in slot #N-4 and PDSCH2 in slot #N-3 are scheduled by a multi-PDSCH scheduling DCI (e.g., TDRA row 0), and K1=3 is indicated, when HARQ-ACK is sent in slot #N, the UE should report not only the A / N of slot #N-3 that belongs to the bundling window (i.e., PDSCH2 corresponding to K1=3), but also PDSCH1 in slot #N-4 that does not belong to the bundling window (e.g., PDSCH related to the extended K1 value). However, when the existing method (i.e., the SLIV pruning method for single PDSCH scheduling) is applied as is, the UE discards the A / N sub-payload of PDSCH1 in slot #N-4 because K1=4 is not included in the determined K1 value set. To solve this problem, the A / N codebook may be configured in the following manner according to an example of the present disclosure.

[0257] F. Option 1: Basically, even for each DL time slot that does not belong to the bundling window (corresponding to the corresponding A / N transmission time slot among the DL time slots that can be scheduled by the multi-TTI DCI that can indicate (a specific time slot as) A / N timing (corresponding to the last (or first) PDSCH transmission time slot)), the UE can configure the A / N sub-payload by SLIV pruning. For example, even for time slot #N-4 that does not belong to the bundling window, the UE can configure the A / N sub-payload by SLIV pruning. Fig. 9 The SLIV pruning process in configures a 1-bit A / N sub-payload. Regarding multi-TTI scheduling, as a result of considering the K0 values ​​in each row in the TDRA table == {{K0, mapping type, SLIV for PDSCH1), {K0, mapping type, SLIV for PDSCH2)..} for the corresponding DL timeslots, the UE can perform SLIV pruning even for DL ​​timeslots that do not belong to the bundling window. Fig. 9 In the example, the time slot #N-4 in which PDSCH1 is transmitted can be determined by K0 of PDSCH1 in the TDRA table. As described above, in a state where the A / N sub-payload has been configured for each DL time slot that does not belong to the bundling window by performing the SLIV pruning process, the UE can operate as follows:

[0258] i. Option a) The entire A / N codebook may be configured by mapping the A / N sub-payloads set corresponding to the DL slots belonging to the bundling window, and then mapping the A / N sub-payloads set corresponding to the DL slots not belonging to the bundling window.

[0259] ii. Option b) Alternatively, the entire A / N codebook may be configured by sequentially concatenating the A / N sub-payloads of all DL slots belonging to the bundling window and all DL slots not belonging to the bundling window in the time order of the DL slots.

[0260] iii. In this case, for each DL timeslot belonging to the bundling window, the A / N sub-payload may be configured by performing SLIV pruning on all SLIV sets that may be scheduled for the DL timeslot by any single-TTI DCI and / or multi-TTI DCI.

[0261] G. Option 1A: In another method equivalent to Option 1 (eg, when slot #N is indicated as A / N transmission timing), the following operation may be considered.

[0262] i. Step 1) When each row (including one or more SLIVs) in the TDRA table configured by the multi-TTI DCI indicates each K1 configured for the UE (or configured in the multi-TTI DCI) (for example, the last SLIV in the row is mapped to the time slot # (N-K1)), all K1_m values ​​can be calculated under the assumption that each SLIV in the row is mapped to the time slot # (N-K1_m), and this process can be performed for all rows and all K1 values. Then, the union of all K1_m values ​​can be calculated (for convenience, defined as "K1_m union").

[0263] 1. In addition, for a specific single-TTI DCI (e.g., a DCI format that is not fallback DCI format 1_0 and does not configure multi-TTI scheduling), the UE may also include all K1 values ​​configured for the UE (or in the DCI) in the K1_m union set (as K1_m values ​​belonging to the K1_m union set).

[0264] ii. Step 2) The A / N sub-payloads may be configured by performing SLIV pruning processing on all SLIV sets (among the SLIVs in the rows in the TDRA table for multi-TTI DCI and the rows in the TDRA table for single-TTI DCI) that may be mapped to time slots #(N-K1_m) corresponding to the respective K1_m values ​​belonging to the K1_m union, and the entire A / N codebook may be configured by applying the method of option a or option b to the A / N sub-payloads corresponding to the respective K1_m values ​​or the respective time slots #(N-K1_m).

[0265] 1. For example, for each SLIV group (including one or more (overlapping) SLIVs) determined by SLIV pruning for each of all K1_m values ​​in the union of K1_m configured for each cell (this is defined as "HARQ-ACK PDSCH opportunity (HPO)"), the A / N sub-payload can be configured by allocating 2 bits (when the cell is configured with PDSCH transmission of up to 2 TBs without HARQ-ACK spatial bundling), 1 bit (when the cell is configured with PDSCH transmission of up to 1 TB or HARQ-ACK spatial bundling) or M bits (when the cell is configured with PDSCH (or TB) transmission based on up to M CBGs).

[0266] 2. In another example, when the “2-TB for single PDSCH only” operation is applied to a cell configured with PDSCH transmission of up to 2 TBs (without spatial bundling) (and when there is a row including only one SLIV among the rows of the TDRA table configured with multi-TTI DCI (format) (this is called a “single SLIV row”), or when there is a specific single TTI configured with PDSCH transmission of up to two TBs When a DCI is present (for example, when there is a DCI (format) that is not fallback DCI format 1_0 and multi-TTI scheduling is not configured), 2 bits may be allocated to the HPO corresponding to the value of K1 in the K1_m union set that matches the corresponding cell configuration or the time slot #(N-K1) corresponding to the value (time slot #(N-K1) belonging to the bundling window) (or the HPO corresponding to a single SLIV row or a row in the TDRA table configured for a single TTI), and 1 bit may be allocated to the HPO corresponding to the K1_m value that does not match K1 or the time slot #(N-K1_m) corresponding to the value (not belonging to the bundling window) (or the remaining HPOs corresponding to time slot #(N-K1), including the HPO).

[0267] 3. In another example, when the “CBG for a single PDSCH only” operation is applied to a cell configured with PDSCH transmission based on at most M CBGs (and when there is a row including only one SLIV among the rows of the TDRA table configured with multi-TTI DCI (format) (this is called a “single SLIV row”), or when there is a specific single TTI configured with PDSCH transmission based on at most M CBGs When a DCI is present (for example, when there is a DCI (format) that is not fallback DCI format 1_0 and multi-TTI scheduling is not configured), M bits may be allocated to the HPO corresponding to the value of K1 in the K1_m set configured for the corresponding cell or the time slot #(N-K1) corresponding to the value (time slot #(N-K1) belonging to the bundling window) (or the HPO corresponding to a single SLIV row or a row in the TDRA table configured for a single TTI), and 1 bit may be allocated to the HPO corresponding to the K1_m value that does not match K1 or the time slot #(N-K1_m) corresponding to the value (not belonging to the bundling window) (or the remaining HPOs corresponding to time slot #(N-K1), including the HPO).

[0268] iii. When some of the multiple SLIVs configured in a row of the TDRA table in the multi-TTI DCI overlap with a specific UL symbol (e.g., a UL symbol semi-statically configured by higher layer signaling through tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated) when determining the K1_m union and performing the SLIV pruning process, the K1_m union may be determined while excluding the corresponding SLIV and SLIV pruning may be performed (based on the determined K1_m union). For example, the UE may regard the PDSCH corresponding to the SLIV overlapping the UL symbol as an invalid PDSCH, and may perform the SLIV pruning process only on the valid PDSCH.

[0269] H. Option 1B: To reduce the UE complexity involved in the SLIV pruning process in Option 1 or 1A, the following operations may be considered.

[0270] i. Step 1) Calculate the K1_m union using the same process as step 1 of option 1A, calculate the SLIV set (defined as "m-SLIV union") under the assumption that all (one or more) individual SLIVs configured in each row of the TDRA table configured in the multi-TTI DCI are mapped to one (virtual) time slot, and calculate the SLIV set (defined as "s-SLIV union") under the assumption that all SLIVs configured in each row of the TDRA table configured in the single TTI DCI are mapped to one (virtual) time slot.

[0271] 1. Alternatively, a SLIV set based on the assumption that all (multiple) separate SLIVs set in each of all rows in the TDRA table configured in the multi-TTI DCI that are configured with SLIVs across multiple time slots are mapped to the same (virtual) time slot is determined as an "m-SLIV union", and a SLIV set based on the assumption that all (one or more) separate SLIVs set in each of all rows in the TDRA table configured in the multi-TTI DCI that are configured with SLIVs belonging to a single time slot and the SLIVs configured in each of all rows in the TDRA table configured in the single-TTI DCI are mapped to the same (virtual) time slot is determined as an "s-SLIV union".

[0272] 2. Alternatively, a SLIV set based on the assumption that all (multiple) individual SLIVs set in each row of all rows in the TDRA table configured in the multi-TTI DCI configured with multiple SLIVs are mapped to the same (virtual) time slot is determined as an "m-SLIV union", and a SLIV set based on the assumption that all individual SLIVs set in all rows in the TDRA table configured in the multi-TTI DCI, each configured with a single SLIB, and the SLIV set in each row of all rows in the TDRA table configured in the single-TTI DCI are mapped to the same (virtual) time slot is determined as an "s-SLIV union".

[0273] ii. Step 2 - Alternative 1) For the value of K1 or the corresponding time slot # (N-K1) matching the K1_m union (belonging to the bundling window), the A / N sub-payload can be configured by performing SLIV pruning on the union of all SLIVs belonging to the m-SLIV union and the s-SLIV union, and for the K1_m value or the corresponding time slot # (N-K1_m) not matching K1 (not belonging to the bundling window), the A / N sub-payload can be configured by performing SLIV pruning only on the SLIVs belonging to the m-SLIV union. Then, the entire A / N codebook can be configured by applying the method of option a or option b to the A / N sub-payload corresponding to each K1_m value or each time slot # (N-K1_m).

[0274] 1. For example, for each SLIV group (including one or more (overlapping) SLIVs) determined by SLIV pruning for each of all K1_m values ​​in the union of K1_m configured for each cell (this is defined as "HARQ-ACK PDSCH opportunity (HPO)"), the A / N sub-payload can be configured by allocating 2 bits (when the cell is configured with PDSCH transmission of up to 2 TBs without HARQ-ACK spatial bundling), 1 bit (when the cell is configured with PDSCH transmission of up to 1 TB or HARQ-ACK spatial bundling) or M bits (when the cell is configured with PDSCH (or TB) transmission based on up to M CBGs).

[0275] 2. In another example, when the “2-TB for single PDSCH only” operation is applied to a cell configured with PDSCH transmission of up to 2 TBs (without spatial bundling) (and when there is a row including only one SLIV among the rows of the TDRA table configured with multi-TTI DCI (format) (this is called a “single SLIV row”), or when there is a specific single TTI configured with PDSCH transmission of up to 2 TBs When a DCI is present (for example, when there is a DCI (format) that is not fallback DCI format 1_0 and multi-TTI scheduling is not configured), 2 bits may be allocated to the HPO corresponding to the value of K1 in the K1_m union set that matches the corresponding cell configuration or the time slot #(N-K1) corresponding to the value (time slot #(N-K1) belonging to the bundling window) (or the HPO corresponding to a single SLIV row or a row in the TDRA table configured for a single TTI), and 1 bit may be allocated to the HPO corresponding to the K1_m value that does not match K1 or the time slot #(N-K1_m) corresponding to the value (not belonging to the bundling window) (or the remaining HPOs corresponding to time slot #(N-K1), including the HPO).

[0276] 3. In another example, when the “CBG for a single PDSCH only” operation is applied to a cell configured with PDSCH transmission based on at most M CBGs (and when there is a row including only one SLIV among the rows of the TDRA table configured with multi-TTI DCI (format) (this is called a “single SLIV row”), or when there is a specific single TTI configured with PDSCH transmission based on at most M CBGs When a DCI is present (for example, when there is a DCI (format) that is not fallback DCI format 1_0 and multi-TTI scheduling is not configured), M bits may be allocated to the HPO corresponding to the value of K1 in the K1_m set configured for the corresponding cell or the time slot #(N-K1) corresponding to the value (time slot #(N-K1) belonging to the bundling window) (or the HPO corresponding to a single SLIV row or a row in the TDRA table configured for a single TTI), and 1 bit may be allocated to the HPO corresponding to the K1_m value that does not match K1 or the time slot #(N-K1_m) corresponding to the value (not belonging to the bundling window) (or the remaining HPOs corresponding to time slot #(N-K1), including the HPO).

[0277] iii. Step 2 - Alternative 2) For each of all K1_m values ​​in the K1_m union, the A / N sub-payload can be configured by performing SLIV pruning processing on the union of all SLIVs belonging to the m-SLIV union and the s-SLIV union, and the entire A / N codebook can be configured by applying option a or option b to the A / N sub-payload corresponding to each K1_m value or each time slot #(N-K1_m).

[0278] 1. For example, for each SLIV group (including one or more (overlapping) SLIVs) determined by SLIV pruning for each of all K1_m values ​​in the union of K1_m configured for each cell (this is defined as "HARQ-ACK PDSCH opportunity (HPO)"), the A / N sub-payload can be configured by allocating 2 bits (when the cell is configured with PDSCH transmission of up to 2 TBs without HARQ-ACK spatial bundling), 1 bit (when the cell is configured with PDSCH transmission of up to 1 TB or HARQ-ACK spatial bundling) or M bits (when the cell is configured with PDSCH (or TB) transmission based on up to M CBGs).

[0279] 2. In another example, when the “2-TB for single PDSCH only” operation is applied to a cell configured with PDSCH transmission of up to 2 TBs (without spatial bundling) (and when there is a row including only one SLIV among the rows of the TDRA table configured with multi-TTI DCI (format) (this is called a “single SLIV row”), or when there is a specific single TTI configured with PDSCH transmission of up to 2 TBs When a DCI is present (for example, when there is a DCI (format) that is not fallback DCI format 1_0 and multi-TTI scheduling is not configured), 2 bits may be allocated to the HPO corresponding to the value of K1 in the K1_m union set that matches the corresponding cell configuration or the time slot #(N-K1) corresponding to the value (time slot #(N-K1) belonging to the bundling window) (or the HPO corresponding to a single SLIV row or a row in the TDRA table configured for a single TTI), and 1 bit may be allocated to the HPO corresponding to the K1_m value that does not match K1 or the time slot #(N-K1_m) corresponding to the value (not belonging to the bundling window) (or the remaining HPOs corresponding to time slot #(N-K1), including the HPO).

[0280] 3. In another example, when the “CBG for a single PDSCH only” operation is applied to a cell configured with PDSCH transmission based on at most M CBGs (and when there is a row including only one SLIV among the rows of the TDRA table configured with multi-TTI DCI (format) (this is called a “single SLIV row”), or when there is a specific single TTI configured with PDSCH transmission based on at most M CBGs When a DCI is present (for example, when there is a DCI (format) that is not fallback DCI format 1_0 and multi-TTI scheduling is not configured), M bits may be allocated to the HPO corresponding to the value of K1 in the K1_m set configured for the corresponding cell or the time slot #(N-K1) corresponding to the value (time slot #(N-K1) belonging to the bundling window) (or the HPO corresponding to a single SLIV row or a row in the TDRA table configured for a single TTI), and 1 bit may be allocated to the HPO corresponding to the K1_m value that does not match K1 or the time slot #(N-K1_m) corresponding to the value (not belonging to the bundling window) (or the remaining HPOs corresponding to time slot #(N-K1), including the HPO).

[0281] iv. When some of the multiple SLIVs configured in a row of the TDRA table in the multi-TTI DCI overlap with specific UL symbols (for example, UL symbols semi-statically configured by higher-layer signaling such as tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated) when determining the K1_m union and the m_SLIV union and performing SLIV pruning, the K1_m union and the m-SLIV union can be determined and SLIV pruning can be performed (based on the determined K1_m union and m-SLIV union) while excluding the corresponding SLIVs.

[0282] I. Option 2: Basically, in a state where the A / N sub-payload has been configured by performing the SLIV pruning process only for each DL slot belonging to the bundling window as described above, the following operation may be performed.

[0283] i. Option a) When the maximum number of TBs that can be scheduled by any multi-TTI DCI (including the case where spatial bundling is not configured) or the maximum number of PDSCHs (including the case where spatial bundling is configured) is set to M, the total A / N codebook can be configured as follows: M bits (or MX bits) are added to the A / N sub-payload corresponding to each K1 value, and the A / N of multiple PDSCHs scheduled by the multi-TTI DCI indicating the K1 value (as the A / N timing corresponding to the last (or first) PDSCH transmission time slot) is mapped to the corresponding M bits (or the A / N of the remaining PDSCHs except the last (or first) PDSCH or the PDSCH sent in the same time slot as the corresponding PDSCH is mapped to the corresponding MX bits).

[0284] 1. In the above example, "adding M bits (or MX bits) to the A / N sub-payload corresponding to each K1 value" may mean: Alternative 1) configuring the HPO set corresponding to the K1 value (having a total of N+M or N+M-1 HPOs) by adding M or M-1 HPOs to the N HPOs determined by performing SLIV pruning processing on the K1 value; or Alternative 2) configuring the HPO set corresponding to the K1 value (having a total of N×(1+M) or N×(1+M-1)=N×M HPOs) by adding M or M-1 HPOs to each of the N HPOs determined by performing SLIV pruning processing on the K1 value.

[0285] Therefore, the A / N sub-payload corresponding to the K1 value can be configured for each HPO by allocating 2 bits (when the corresponding cell is configured with PDSCH transmission of up to 2 TBs without HARQ-ACK spatial bundling), 1 bit (when the corresponding cell is configured with PDSCH transmission of up to 1 TB and HARQ-ACK spatial bundling), or M bits (when the corresponding cell is configured with PDSCH transmission based on up to M CBGs).

[0286] 2. In this case, the SLIV pruning process may be performed only on the last SLIV (or one or more SLIVs belonging to the same time slot as the last SLIV) among the SLIVs set in each row of the TDRA table configured in the multi-TTI DCI.

[0287] 3. In the above example, the K1 value may be limited to the K1 value set in the multi-TTI DCI (format), and for the K1 value not set in the multi-TTIDCI, (the A / N sub-payload is configured for the K1 value based on SLIV pruning of the TDRA table as conventionally, and) the process of adding M bits (or MX bits) as described above may be skipped.

[0288] 4. In this case, under the assumption that a specific K1 value is indicated as A / N timing (corresponding to the last PDSCH transmission slot), when all SLIVs set in each row of all rows in the TDRA table configured in the multi-TTI DCI (or all SLIVs except the SLIV of the last PDSCH transmission slot (or the last SLIV)) overlap with a specific (e.g., semi-statically configured) UL symbol, the processing of adding M bits (or MX bits) can also be skipped for the K1 value.

[0289] More specifically, in the case where SLIV pruning is performed on the last SLIV in each row of the TDRA table of the multi-TTI DCI (or one or more SLIVs belonging to the same time slot as the last SLIV), for each K1 value in the example, when at least one SLIV in each row does not overlap with a specific (e.g., semi-statically configured) UL symbol, SLIV pruning may be performed by including the row (the last SLIV of the row) (in this case, specifically, even when the last SLIV of the row overlaps with a specific (e.g., semi-statically configured) UL symbol, the row is included for SLIV pruning). Otherwise, when all SLIVs in each row overlap with a specific (e.g., semi-statically configured) UL symbol, SLIV pruning may be performed while excluding the corresponding row (the last SLIV of the row).

[0290] Therefore, when all SLIVs (all remaining SLIVs except the last SLIV) in a row corresponding to the HPO determined by performing the SLIV pruning process (to which one or more SLIVs in the same time slot as the last SLIV belong) overlap with a specific (e.g., semi-statically configured) UL symbol, the process of adding M or M-1 HPOs as described above can be skipped. Otherwise, when at least one SLIV in the row (e.g., at least one remaining SLIV except the last SLIV) does not overlap with a specific (e.g., semi-statically configured) UL symbol, the process of adding M or M-1 HPOs as described above can be performed.

[0291] 5. In the above example, when each PDSCH is configured for transmission of up to 2 TBs and HARQ-ACK spatial bundling is not configured, X=2, and when each PDSCH is configured for transmission of up to 1 TB or HARQ-ACK spatial bundling is configured, X=1.

[0292] ii. Option b) For each K1 value, the (maximum) number of PDSCH opportunities (SLIV) that do not belong to / may not belong to the bundling window (or do not belong to / may not belong to the last (or first) PDSCH transmission slot) (including the case where spatial bundling is configured) among the multiple PDSCHs that can be scheduled by the multi-TTI DCI indicating the K1 value, or the (maximum) number of TBs (e.g., L) (including the case where spatial bundling is not configured) corresponding to the (maximum) number of PDSCH opportunities (SLIV) is calculated, and L bits are added to the A / N sub-payload corresponding to the K1 value. The total A / N codebook can be configured by mapping the A / N of the PDSCH that does not belong to the bundling window (or the last (or first) PDSCH transmission slot) among the PDSCHs scheduled by the multi-TTI DCI indicating the K1 value (as the A / N timing corresponding to the last (or first) PDSCH transmission slot) to L bits.

[0293] 1. In the above example, "adding L bits to the A / N sub-payload corresponding to the K1 value" may mean: alternative 1) configuring the HPO set corresponding to the K1 value (having a total of N+L HPOs) by adding L HPOs to the N HPOs determined by performing SLIV pruning processing on the K1 value; or alternative 2) configuring the HPO set corresponding to the K1 value (having a total of N×(1+L) HPOs) by adding L HPOs to each of the N HPOs determined by performing SLIV pruning processing on the K1 value.

[0294] Therefore, the A / N sub-payload corresponding to the K1 value can be configured for each HPO by allocating 2 bits (when the corresponding cell is configured with PDSCH transmission of up to 2 TBs without HARQ-ACK spatial bundling), 1 bit (when the corresponding cell is configured with PDSCH transmission of up to 1 TB and HARQ-ACK spatial bundling), or M bits (when the corresponding cell is configured with PDSCH (or TB) transmission based on up to M CBGs).

[0295] 2. In this case, the SLIV pruning process may be performed only on the last SLIV (or one or more SLIVs belonging to the same time slot as the last SLIV) among the SLIVs set in each row of the TDRA table configured in the multi-TTI DCI.

[0296] 3. In the above example, the K1 value may be limited to the K1 value set in the multi-TTI DCI (format), and for the K1 value not set in the multi-TTIDCI, (the A / N payload corresponding to the K1 value is configured based on SLIV pruning of the TDRA table as conventionally, and) the above-mentioned process of adding the L bit may be skipped.

[0297] 4. In this case, under the assumption that a specific K1 value is indicated as A / N timing (corresponding to the last PDSCH transmission slot), the process of adding the L bit can also be skipped for the K1 value when all SLIVs set in each row of all rows in the TDRA table configured in the multi-TTI DCI (or all SLIVs except the SLIV of the last PDSCH transmission slot (or the last SLIV)) overlap with a specific (e.g., semi-statically configured) UL symbol.

[0298] More specifically, in the case where SLIV pruning is performed on the last SLIV in each row of the TDRA table of the multi-TTI DCI (or one or more SLIVs belonging to the same time slot as the last SLIV), for each K1 value in the example, when at least one SLIV in each row does not overlap with a specific (e.g., semi-statically configured) UL symbol, SLIV pruning may be performed by including the row (the last SLIV of the row) (in this case, specifically, even when the last SLIV of the row overlaps with a specific (e.g., semi-statically configured) UL symbol, the row is included for SLIV pruning). Otherwise, when all SLIVs in each row overlap with a specific (e.g., semi-statically configured) UL symbol, SLIV pruning may be performed while excluding the corresponding row (the last SLIV of the row).

[0299] Therefore, when all SLIVs (all remaining SLIVs except the last SLIV) in a row corresponding to the HPO determined by performing the SLIV pruning process (to which one or more SLIVs in the same time slot as the last SLIV belong) overlap with a specific (e.g., semi-statically configured) UL symbol, the process of adding L HPOs as described above may be skipped. Otherwise, when at least one SLIV in the row (e.g., at least one remaining SLIV except the last SLIV) does not overlap with a specific (e.g., semi-statically configured) UL symbol, the process of adding L HPOs as described above may be performed.

[0300] iii. Option c) For each K1 value, the A / N sub-payload can be configured by performing SLIV pruning on a set of all SLIVs (configured in the rows of the TDRA table for multi-TTI DCI and the rows of the TDRA table for single-TTI DCI) that can be mapped to each time slot included in a set of multiple time slots schedulable by the multi-TTI DCI indicating the K1 value (for convenience, referred to as a "multi-TTI window") (or regardless of the time slots that can be mapped), and the A / N sub-payload configuration for each K1 based on SLIV pruning of the multi-TTI window (each time slot belonging to the multi-TTI window) can be performed sequentially for all K1 values.

[0301] 1. In the above example, the K1 values ​​(for which SLIV pruning is performed in the multi-TTI window) may be limited to the K1 value set set in the multi-TTI DCI (format), and for K1 values ​​not set in the multi-TTI DCI, the A / N payload corresponding to the K1 value may be configured based on SLIV pruning of the TDRA table configured in the single TTIDCI (for each row configured with a single SLIV) as conventionally.

[0302] 2. When some of the multiple SLIVs configured in a row of the TDRA table of the multi-TTI DCI overlap with specific (e.g., semi-statically configured) UL symbols during K1-based SLIV pruning of the multi-TTI window, the multi-TTI window (including a time slot including at least one (valid) SLIV) can be determined while excluding these SLIVs (as invalid), and SLIV pruning can be performed for the multi-TTI window.

[0303] J. In the case of an A / N sub-payload configured by performing SLIV pruning processing for a specific K1 value (DL time slot corresponding to the K1 value) in all methods (e.g., option 1 / 1A / 1B / 2), a UE that does not have the ability to receive PDSCHs of multiple TDMs in one time slot period or does not support the ability may configure the A / N sub-payload using only the A / N bits corresponding to one PDSCH opportunity. (For example, when PDSCH transmission of up to 2 TBs is configured and HARQ-ACK spatial bundling is not configured, 2 A / N bits may be configured, and when PDSCH transmission of up to 1 TB and HARQ-ACK spatial bundling are configured, 1 A / N bit may be configured).

[0304] K. In addition, the operations of performing SLIV pruning processing and configuring an A / N sub-payload (and adding M or MX bits or L bits to the A / N sub-payload) for a specific K1 value in all of the above methods (e.g., options 1 / 1A / 1B / 2) may be equivalent to the operations of performing SLIV pruning processing and configuring an A / N sub-payload (and adding M or MX bits or L bits to the A / N sub-payload) based on a DL time slot for multiple DL time slots included in / belonging to a UL time slot cycle that is K1 time slots earlier than the HARQ-ACK transmission UL time slot when the SCS configured for UL (HARQ-ACK) is less than the SCS configured for DL ​​(PDSCH).

[0305] (Proposal 9) Operation of receiving multiple PDSCHs scheduled by multi-TTI DCI

[0306] 1) TCI information and QCL assumptions for PDSCH reception at UE

[0307] A. Traditionally, the time offset between DCI and PDSCH (scheduled by the DCI)

[0308] i. When the time offset between DCI and PDSCH (scheduled by DCI) is equal to or greater than a specific threshold (eg, timeDurationForQCL), PDSCH may be received by applying the TCI state indicated by DCI and the associated QCL assumption.

[0309] ii. Otherwise, when the DCI to PDSCH time offset is less than a certain threshold, PDSCH may be received by applying the TCI state and associated QCL assumption configured for (reception of) a specific CORESET (eg, the CORESET with the lowest ID).

[0310] B. For multiple PDSCHs scheduled by multi-TTI DCI, the following operations may be performed:

[0311] i. Option 1: A PDSCH (i.e., PDSCH-D) whose DCI to PDSCH time offset is equal to or greater than a specific threshold can be received by applying the TCI state and associated QCL assumption indicated by the DCI, while a PDSCH (i.e., PDSCH-C) whose DCI to PDSCH time offset is less than a specific threshold can be received by jointly applying the TCI state and associated QCL assumption configured for a specific CORESET (e.g., a CORESET with the lowest ID) at a specific time (e.g., in the first PDSCH transmission time slot among multiple PDSCHs and / or the previous latest CORESET configuration time slot) to the corresponding PDSCH.

[0312] 1. Specific DCI / MAC signaling (i.e., TCI update command) may indicate that a set of candidate TCI states (which may be indicated by a PDSCH scheduling DCI including a multi-TTI DCI) and associated QCL assumptions are changed to other values, so the UE may apply the changed updated TCI state and associated QCL assumption set starting from a specific time point after the reception time of the TCI update command or the corresponding ACK feedback time (i.e., TCI update timing).

[0313] In the above case, when the TCI update timing is after the reception time of at least one PDSCH-D, the unupdated TCI state and the associated QCL hypothesis set before the change can be applied to all PDSCH-Ds. When the TCI update timing is before the reception time of all PDSCH-Ds, the updated TCI state and the associated QCL hypothesis set after the change can be applied to all PDSCH-Ds.

[0314] In another example, when the TCI update timing is after the reception time of a specific one (some or all) PDSCH-Ds, the same TCI state and associated QCL assumption as the PDSCH-C may be applied to the specific PDSCH-D (by treating the specific PDSCH-D in the same manner as the PDSCH-C whose DCI to PDSCH time offset is less than a specific threshold), and the updated TCI state and associated QCL assumption set after the change may be applied to the remaining PDSCH-Ds (whose TCI update timing is before the reception time of all PDSCH-Ds). When the TCI update timing is before the reception time of all PDSCH-Ds, the updated TCI state and associated QCL assumption set after the change may be applied to all PDSCH-Ds.

[0315] And / or, the reception of a PDSCH located before the TCI update timing among multiple PDSCHs scheduled by multi-TTI DCI may be discarded, and the PDSCH may be equally regarded as a subsequent invalid PDSCH. Alternatively, the reception of a PDSCH located before the TCI update timing among multiple PDSCH-Ds (scheduled by multi-TTI DCI) may be discarded, and the PDSCH may be equally regarded as a subsequent invalid PDSCH.

[0316] 2. In the above example, the first PDSCH may refer to the first valid PDSCH actually transmitted, except for the invalid PDSCH that temporally overlaps with a specific UL symbol (e.g., semi-statically configured by higher-layer signaling such as tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated) and whose transmission is therefore discarded, or the first PDSCH indicated by multiple TTIDCIs regardless of whether they are actually transmitted.

[0317] ii. Option 2: When the DCI-to-PDSCH time offset of all PDSCHs is equal to or greater than a specific threshold, all PDSCHs (i.e., PDSCH-D) can be received by applying the TCI state and associated QCL assumption indicated by the DCI. When the DCI-to-PDSCH time offset of at least one PDSCH is less than a specific threshold, all scheduled PDSCHs (i.e., PDSCH-C) can be received by jointly applying the TCI state and associated QCL assumption configured for a specific CORESET (e.g., a CORESET with the lowest ID) at a specific time (e.g., in a transmission slot including the first of the multiple PDSCHs and / or the previous latest CORESET configuration slot) to all PDSCHs.

[0318] 1. In the above case where a TCI update command has been sent / received, when the corresponding TCI update timing is before the reception time of at least one PDSCH-D, the non-updated TCI state and the associated QCL hypothesis set before the change can be applied to all PDSCH-Ds. When the TCI update timing is before the reception time of all PDSCH-Ds, the updated TCI state and the associated QCL hypothesis set after the change can be applied to all PDSCH-Ds.

[0319] In another example, when the TCI update timing is after the reception time of a specific one (some or all) PDSCH-Ds, the same TCI state and associated QCL assumption as the PDSCH-C may be applied to the specific PDSCH-D (by treating the specific PDSCH-D in the same manner as the PDSCH-C whose DCI to PDSCH time offset is less than a specific threshold), and the updated TCI state and associated QCL assumption set after the change may be applied to the remaining PDSCH-Ds (the TCI update timing is before the reception time of all PDSCH-Ds). When the TCI update timing is before the reception time of all PDSCH-Ds, the updated TCI state and associated QCL assumption set after the change may be applied to all PDSCH-Ds.

[0320] In addition, in the above case, the TCI state and associated QCL assumptions configured for (receipt of) a specific CORESET (e.g., a CORESET with the lowest ID) at a specific time (e.g., in a time slot including the first PDSCH transmission time slot and / or the latest CORESET configuration time slot before) may be commonly applied to all PDSCH-Cs, regardless of whether the TCI update timing is after the reception time of at least one PDSCH-C or before the reception time of all PDSCH-Cs.

[0321] And / or, the reception of a PDSCH located before the TCI update timing among multiple PDSCHs scheduled by multi-TTI DCI may be discarded, and the PDSCH may be equally regarded as a subsequent invalid PDSCH. Alternatively, the reception of a PDSCH located before the TCI update timing among multiple PDSCH-Ds (scheduled by multi-TTI DCI) may be discarded, and the PDSCH may be equally regarded as a subsequent invalid PDSCH.

[0322] 2. In the above example, all PDSCHs, at least one PDSCH and the first PDSCH may refer to all, at least one and the first valid PDSCHs actually transmitted except for the invalid PDSCHs that temporally overlap with specific UL symbols (for example, semi-statically configured by higher-layer signaling such as tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated) and whose transmission is therefore discarded, or all, at least one and the first PDSCHs indicated by multi-TTI DCI regardless of whether they are actually transmitted.

[0323] iii. Option 3: A PDSCH (i.e., PDSCH-D) whose DCI to PDSCH time offset is equal to or greater than a specific threshold can be received by applying the TCI state and the associated QCL assumption indicated by the DCI, while a PDSCH (i.e., PDSCH-C) whose DCI to PDSCH time offset is less than a specific threshold can be received by jointly applying the TCI state and the associated QCL assumption configured for a specific CORESET (e.g., the CORESET with the lowest ID) at a specific time (e.g., in the first PDSCH transmission time slot among multiple PDSCHs and / or the previous latest CORESET configuration time slot) to the corresponding PDSCH.

[0324] 1. In the above case where a TCI update command has been sent / received, when the TCI update timing is before the reception time of at least one PDSCH-D, the non-updated TCI state and the associated QCL hypothesis set before the change can be applied to all PDSCH-Ds. When the TCI update timing is before the reception time of all PDSCH-Ds, the updated TCI state and the associated QCL hypothesis set after the change can be applied to all PDSCH-Ds.

[0325] In another example, when the TCI update timing is after the reception time of a specific one (some or all) PDSCH-Ds, the same TCI state and associated QCL assumption as the PDSCH-C may be applied to the specific PDSCH-D (by treating the specific PDSCH-D in the same manner as the PDSCH-C whose DCI to PDSCH time offset is less than a specific threshold), and the updated TCI state and associated QCL assumption set after the change may be applied to the remaining PDSCH-Ds (the TCI update timing is before the reception time of all PDSCH-Ds). When the TCI update timing is before the reception time of all PDSCH-Ds, the updated TCI state and associated QCL assumption set after the change may be applied to all PDSCH-Ds.

[0326] And / or, the reception of a PDSCH located before the TCI update timing among multiple PDSCHs scheduled by multi-TTI DCI may be discarded, and the PDSCH may be equally regarded as a subsequent invalid PDSCH. Alternatively, the reception of a PDSCH located before the TCI update timing among multiple PDSCH-Ds (scheduled by multi-TTI DCI) may be discarded, and the PDSCH may be equally regarded as a subsequent invalid PDSCH.

[0327] iv. Option 4: Different TCI states and associated QCL assumptions for PDSCH reception may be applied based on the interval between the PDSCH and / or the SCS configured for the PDSCH. Specifically, for a PDSCH whose DCI to PDSCH time offset is less than a specific threshold, or for all scheduled PDSCHs including at least one PDSCH whose DCI to PDSCH time offset is less than a specific threshold, the following operations may be performed.

[0328] 1. For example, when the PDSCH is scheduled in consecutive symbols or consecutive time slots (or the gap between adjacent PDSCHs is less than X symbols or Y time slots), the method of Option 1 or Option 2 may be applied. When the PDSCH is scheduled in non-continuous symbols or non-continuous time slots (or the gap between adjacent PDSCHs is equal to or greater than X symbols or Y time slots), the method of Option 3 (or Option 1) may be applied.

[0329] 2. In another example, when a relatively large SCS (e.g., 480 KHz and 960 KHz or 960 KHz) is configured for PDSCH, the method of Option 1 or Option 2 may be applied. When a relatively small SCS (e.g., 120 KHz or 120 KHz and 480 KHz) is configured for PDSCH, the method of Option 3 (or Option 1) may be applied.

[0330] 3. In the above example, at least one PDSCH and a specific PDSCH may refer to at least one and a specific one valid PDSCH that is actually transmitted, excluding an invalid PDSCH that temporally overlaps with a specific (e.g., semi-statically configured) UL symbol and whose transmission is discarded, or at least one and a specific one PDSCH indicated by a multi-TTI DCI regardless of whether the PDSCH is actually transmitted.

[0331] C. When the PDCCH and the PDSCH overlap each other in time, the following operations may be conventionally performed.

[0332] i. When the QCL (type D) assumptions are different between PDCCH and PDSCH, PDCCH can be received (and reception of PDSCH can be discarded).

[0333] D. Among multiple PDSCHs scheduled by multi-TTI DCI,

[0334] i. Option A: When a PDSCH whose DCI to PDSCH time offset is less than a specific threshold and a specific PDCCH overlap each other in time, and the QCL (type D) assumption between the PDSCH and the PDCCH is different, the PDCCH can be received (and the reception of the PDSCH can be discarded). When a PDSCH whose DCI to PDSCH time offset is equal to or greater than a specific threshold and a specific PDCCH overlaps each other in time, and the QCL (type D) assumption between the PDSCH and the PDCCH is different, the PDSCH can be received (and the reception of the PDCCH can be discarded).

[0335] Alternatively, when it is determined by option 1 / 2 / 3 / 4 (or any other method) that the PDSCH for application of the TCI state and the associated QCL assumption configured for a specific CORESET overlaps with each other in time with the specific PDCCH, and the QCL (type D) assumptions between the PDSCH and the PDCCH are different, the PDCCH can be received (and the reception of the PDSCH can be discarded). When it is determined that the PDSCH for application of the TCI state and the associated QCL assumption indicated by the DCI overlaps with each other in time with the specific PDCCH, and the QCL (type D) assumptions between the PDSCH and the PDCCH are different, the PDSCH can be received (and the reception of the PDCCH can be discarded).

[0336] ii. Option B: Where it is determined by Option 1 / 2 / 3 / 4 (or any other method) that the TCI state and associated QCL assumption configured for a particular CORESET are applied to all scheduled PDSCHs (when received), when the QCL (Type D) assumption is different between the corresponding PDSCH and the PDCCH (overlapping with the PDSCH in time), the PDSCH may be received (and the reception of the PDCCH may be discarded). And / or, where it is determined by Option 1 / 2 / 3 / 4 (or any other method) that the TCI state and associated QCL assumption configured for a particular CORESET are applied to certain (or all) scheduled PDSCHs (when received), when the QCL (Type D) assumption is different between the corresponding PDSCH and the PDCCH (overlapping with the PDSCH in time), the PDCCH may be received (and the reception of the PDSCH may be discarded).

[0337] Alternatively, in the case where it is determined by option 1 / 2 / 3 / 4 (or any other method) that the TCI state and the associated QCL assumption configured for a specific CORESET are applied to all scheduled PDSCHs (when received), when the QCL (type D) assumption is different between the corresponding PDSCH and the PDCCH (overlapping with the PDSCH in time), the PDCCH may be received (and the reception of the PDSCH may be discarded). Otherwise (i.e., in the case where it is determined that the TCI state and the associated QCL assumption indicated by the DCI are applied to at least one PDSCH (when received), when the QCL (type D) assumption is different between the corresponding PDSCH and the PDCCH (overlapping with the PDSCH in time for all scheduled PDSCHs), the PDSCH may be received (and the reception of the PDCCH may be discarded).

[0338] Alternatively, in the case where it is determined by option 1 / 2 / 3 / 4 (or any other method) that the TCI state and the associated QCL assumption indicated by the DCI are applied to all scheduled PDSCHs (when received), when the QCL (type D) assumption is different between the corresponding PDSCH and the PDCCH (overlapping with the PDSCH in time), the PDSCH may be received (and the reception of the PDCCH may be discarded). Otherwise (i.e., in the case where it is determined that the TCI state and the associated QCL assumption configured for a specific CORESET are applied to at least one PDSCH (when received), when the QCL (type D) assumption is different between the corresponding PDSCH and the PDCCH (overlapping with the PDSCH in time for all scheduled PDSCHs), the PDCCH may be received (and the reception of the PDSCH may be discarded).

[0339] iii. Option C: Where it is determined by Option 1 / 2 / 3 / 4 (or any other method) that the TCI state and associated QCL assumption configured for a specific CORESET are applied to certain (or all) scheduled PDSCHs (when received), when the QCL (Type D) assumption is different between the corresponding PDSCH and the PDCCH (overlapping with the PDSCH in time), the PDSCH may be received (and the reception of the PDCCH may be discarded). And / or Where it is determined by Option 1 / 2 / 3 / 4 (or any other method) that the TCI state and associated QCL assumption indicated by the DCI are applied to all scheduled PDSCHs (when received), when the QCL (Type D) assumption is different between the corresponding PDSCH and the PDCCH (overlapping with the PDSCH in time), the PDCCH may be received (and the reception of the PDSCH may be discarded).

[0340] Alternatively, in the case where it is determined by option 1 / 2 / 3 / 4 (or any other method) that the TCI state and the associated QCL assumption configured for a specific CORESET are applied to at least one PDSCH (when received), when the QCL (type D) assumption is different between the corresponding PDSCH and the PDCCH (overlapping with the PDSCH in time for all scheduled PDSCHs), the PDCCH may be received (and the reception of the PDSCH may be discarded). Otherwise (in the case where it is determined that the TCI state and the associated QCL assumption indicated by the DCI are applied to all scheduled PDSCHs (when received)), when the QCL (type D) assumption is different between the corresponding PDSCH and the PDCCH (overlapping with the PDSCH in time), the PDSCH may be received (and the reception of the PDCCH may be discarded).

[0341] Alternatively, in the case where it is determined by option 1 / 2 / 3 / 4 (or any other method) that the TCI state and the associated QCL assumption indicated by the DCI are applied to at least one PDSCH (when received), when the QCL (type D) assumption is different between the corresponding PDSCH and the PDCCH (for all scheduled PDSCHs) (overlapping with the PDSCH in time), the PDSCH can be received (and the reception of the PDCCH can be discarded). Otherwise (in the case where it is determined that the TCI state and the associated QCL assumption configured for a specific CORESET are applied to all scheduled PDSCHs (when received)), when the QCL (type D) assumption is different between the corresponding PDSCH and the PDCCH (overlapping with the PDSCH in time), the PDCCH can be received (and the reception of the PDSCH can be discarded).

[0342] iv. Option D: In case of multiple PDSCHs scheduled by multi-TTI DCI, PDSCH can be received (and reception of PDCCH can be discarded) when the QCL (type D) assumptions between the corresponding PDSCH and the PDCCH (temporally overlapped with the PDSCH) are different.

[0343] Alternatively, in the case where multiple PDSCHs are scheduled by multi-TTI DCI, when the QCL (type D) assumptions between the corresponding PDSCHs and the PDCCH (temporally overlapping with the PDSCH) are different, the PDCCH may be received (and reception of the PDSCH may be discarded).

[0344] 1. In the above example, multiple PDSCHs refer to multiple valid PDSCHs that are actually transmitted except for the invalid PDSCHs that temporally overlap with a specific (e.g., semi-statically configured) UL symbol and skip its transmission, or multiple PDSCHs indicated by multi-TTI DCI regardless of whether they are actually transmitted.

[0345] E. In the case where multiple TRP-based PDSCH transmissions are configured, the CORESET and CORESET configuration time slots used to determine the received TCI state and associated QCL assumption applied to a specific PDSCH (e.g., the first or each of multiple PDSCHs scheduled by multi-TTI DCI) (e.g., PDSCH-x) may be replaced by a CORESET configured with the same CORSET pool index (e.g., coresetPoolIndex) as the CORESET carrying the PDCCH scheduling the specific PDSCH-X and the time slots in which the CORESET is configured.

[0346] F. Alternatively, in the case of a specific PDSCH (e.g., PDSCH-x) received by applying the TCI state and the associated QCL assumption configured for a specific CORSET in the above example, in the case of configuring PDSCH transmission based on multiple TRPs, PDSCH-x can be received by applying the TCI state and the associated QCL assumption configured for a specific TCI code point (e.g., with the lowest index) among TCI code points (in pairs) configured with two (different) TCI states among the TCI code points (configured for PDSCH reception) that can be indicated by DCI.

[0347] G. Alternatively, in the case of a specific PDSCH (e.g., PDSCH-x) received by applying the TCI state and the associated QCL assumption configured for a specific CORSET in the above example, in the case where PDSCH transmission in a specific cell is scheduled by DCI in another cell (cross-CC scheduling), among the TCI code points (in pairs) configured with two (different) TCI states among the (enabled) TCI code points (configured for PDSCH reception) that can be indicated by DCI, PDSCH-x can be received by applying the TCI state and the associated QCL assumption configured for a specific TCI code point (e.g., with the lowest index).

[0348] For convenience of description, a distinction is made between the various DCI field configuration methods / options described above. Multiple configuration methods / options may be combined and each may be implemented as a separate invention.

[0349] Fig.10 Multiple PDSCH scheduling and HARQ-ACK reporting according to an embodiment of the present disclosure are shown. Fig.10 It is intended to illustrate rather than limit the present disclosure.

[0350] The UE may receive information from the BS through high-layer signaling (V320). For example, configuration information related to multi-PDSCH scheduling and configuration information related to multi-PDSCH HARQ-ACK feedback may be received through high-layer signaling. For example, a high-layer parameter (or table) related to a value to be indicated by the state of at least one of the above-mentioned DCI fields may be configured.

[0351] The UE may receive DCI (one PDCCH signal) (V330). The UE may perform blind detection on the DCI scheduling a plurality of PDSCHs based on information received through higher layer signaling.

[0352] The BS may transmit a plurality of PDSCHs scheduled by one DCI transmission (V335). The UE may receive a plurality of PDSCHs based on the DCI. For example, the plurality of PDSCHs may be received based on a state of at least one field of the DCI.

[0353] The UE may generate / determine HARQ-ACK (V337) for (all or at least a portion of) the received PDSCH. The HARQ-ACK may be generated based on a specific codebook. The UE may generate / determine HARQ-ACK with reference to information notified by a higher layer signal and / or DCI. For example, the HARQ-ACK may be generated based on a type 1 codebook, a type 2 codebook, or a type 3 codebook.

[0354] The UE may send HARQ-ACK for the PDSCH (V338). The HARQ-ACK transmission resources (time resources and timing) may be determined based on the DCI and the (final) PDSCH.

[0355] Fig.11 Multiple PDSCH transmission / reception and HARQ-ACK reception according to an embodiment of the present disclosure are shown. Fig.11 It is intended to illustrate rather than limit the present disclosure.

[0356] The UE may receive information from the BS through high-layer signaling (B310). For example, configuration information related to multi-PUSCH scheduling and configuration information related to multi-PUSCH HARQ-ACK feedback may be received through high-layer signaling. For example, a high-layer parameter (or table) related to a value to be indicated by the state of at least one of the above-mentioned DCI fields may be configured.

[0357] The UE may send a scheduling request (SR) (B315). The SR may be a resource allocation request for multiple PUSCH transmissions.

[0358] The UE may receive DCI (one PDCCH signal) (B320). The UE may perform blind detection on the DCI scheduling a plurality of PUSCHs based on information received through higher layer signaling.

[0359] The UE may transmit a plurality of PUSCHs based on one DCI reception (B325). The BS may receive a plurality of PUSCHs based on the DCI. For example, a plurality of PUSCHs may be transmitted / received based on a state of at least one field of the DCI.

[0360] The BS may generate / determine a HARQ-ACK for (all or at least a portion of) the received PUSCH (B327).

[0361] The BS may send HARQ-ACK for the PUSCH (B330).

[0362] The UE may perform retransmission based on the HARQ-ACK (B340).

[0363] Fig.12 is a diagram illustrating a signal transmission / reception method according to an embodiment of the present disclosure. Fig.12 The exemplary implementation of at least part of the above proposals of the present disclosure is related to the present disclosure, and the present disclosure is not limited to Fig.12 .

[0364] Reference Fig.12 , the UE receives DCI (C05) that schedules multiple PDSCHs.

[0365] The UE performs PDSCH reception on at least a part of a plurality of PDSCHs based on the DCI ( C10 ).

[0366] The UE determines HARQ-ACK based on a specific codebook based on the result of PDSCH reception (C15).

[0367] The UE may send HARQ-ACK in slot #N associated with a specific candidate K1 value indicated by the DCI among a plurality of candidate PDSCH-to-HARQ feedback timing values ​​(K1 values) configured for the UE (C20).

[0368] When determining HARQ-ACK (C15), based on configuring HARQ-ACK based on the first type of codebook for scheduling multiple PDSCHs, the UE may perform a first SLIV pruning based on a combination of SLIV values ​​of PDSCHs that can be potentially scheduled in each time slot of the bundling window determined according to multiple candidate K1 values, and perform a second SLIV pruning based on a combination of SLIV values ​​of PDSCHs that can be potentially scheduled in at least one time slot that does not belong to the bundling window.

[0369] The first ACK / NACK sub-payload of each time slot of the bundling window may be determined based on the first SLIV pruning.

[0370] A second ACK / NACK sub-payload of at least one time slot that does not belong to the bundling window may be determined based on the second SLIV pruning.

[0371] The UE may generate the total payload of the HARQ-ACK based on the first type of codebook by cascading the first ACK / NACK sub-payload and the second ACK / NACK sub-payload, or arranging the first ACK / NACK sub-payload and the second ACK / NACK sub-payload in the chronological order of the corresponding time slots.

[0372] In the time domain, at least one time slot that performs the second SLIV pruning and does not belong to the bundling window may be located before the bundling window.

[0373] At least one time slot that performs the second SLIV pruning and does not belong to the bundling window may be the time slot that receives the PDSCH located outside the bundling window among multiple received PDSCHs.

[0374] The TDRA field included in the DCI may indicate a row of the TDRA table configured for the UE.

[0375] At least one row of the TDRA table may include multiple sets of {K0, PDSCH mapping type, SLIV} parameters, where "K0" may indicate the physical downlink control channel (PDCCH) to PDSCH time slot offset.

[0376] At least one time slot that performs the second SLIV pruning and does not belong to the bundling window may be determined based on the "K0" included in the parameter set that does not correspond to the last time slot in each row of the TDRA table.

[0377] The bundling window for performing the first SLIV pruning is determined by combining multiple candidate K1 values with the parameter set corresponding to the last time slot in each row of the TDRA table.

[0378] For example, under the assumption that P sets of {K0, PDSCH mapping type, SLIV} parameters are included in a specific row of the TDRA table and correspond to a total of S time slots (e.g., the P PDSCHs scheduled based on the specific row are mapped to a total of S time slots), according to the configuration of each row, S = P or S < P (i.e., S ≤ P).

[0379] Generate HARQ-ACK for the valid PDSCHs among multiple PDSCHs except for the invalid PDSCHs that overlap with the UL symbols configured by the higher layer signaling.

[0380] The UE may perform each of the first SLIV pruning and the second SLIV pruning while excluding the invalid PDSCHs that overlap with the UL symbols configured by the higher layer signaling.

[0381] During the process of determining HARQ-ACK (C15), the HARQ process ID may be continuously / sequentially assigned to the valid PDSCHs.

[0382] Fig.13 is a diagram showing HARQ process ID allocation according to an embodiment of the present disclosure. Fig.13 The above-mentioned exemplary implementations of the present disclosure are related to the present disclosure, and the present disclosure is not limited to Fig.13 .

[0383] Reference Fig.13 , the UE may receive information indicating UL / DL resource configuration through high-layer signaling (D05); receive DCI for scheduling multiple PDSCHs (D10); perform PDSCH reception for at least a portion of the multiple PDSCHs based on the DCI (D15); and perform a HARQ process for each PDSCH based on the result of the PDSCH reception (D20). The HARQ process may include A / N determination and HARQ-ACK payload generation, HARQ-ACK reporting, and retransmission reception on the UE side, and may include HARQ-ACK reception and retransmission on the BS side.

[0384] The UE may determine, among a plurality of PDSCHs, a PDSCH overlapping with a UL symbol configured by the information indicating the UL / DL resource configuration as an invalid PDSCH.

[0385] When performing a HARQ process for each PDSCH, the UE may continuously or sequentially allocate HARQ process IDs only to valid PDSCHs except for invalid PDSCHs.

[0386] Based on the HARQ process ID indicated by the DCI being #n and the number of valid PDSCHs among multiple PDSCHs being k, the UE can assign HARQ process ID #n, HARQ process ID #n+1, HARQ process ID #n+2, ..., HARQ process ID #n+k-1 to k valid PDSCHs respectively.

[0387] Fig.14 A communication system 1 applied to the present disclosure is shown.

[0388] Reference Fig.14, 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.

[0389] The wireless devices 100a to 100f may be connected to the network 300 via the BS 200. 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.

[0390] Wireless communication / connection 150a, 150b or 150c may be established between wireless devices 100a to 100f / BS 200 or BS 200 / BS 200. 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 a process for sending / receiving a radio signal, various signal processing processes (e.g., channel coding / decoding, modulation / demodulation, and resource mapping / demapping), and a resource allocation process may be performed based on various proposals of the present disclosure.

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

[0392] Reference Fig.15 , 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.14 {wireless device 100x and BS 200} and / or {wireless device 100x and wireless device 100x}.

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

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

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

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

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

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

[0399] Fig.16 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.14 ) are implemented in various forms.

[0400] Reference Fig.16 , the wireless devices 100 and 200 may correspond to Fig.15The 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.15 One or more processors 102 and 202 and / or one or more memories 104 and 204. For example, the transceiver 114 may include Fig.15 The control unit 120 is electrically connected to the communication unit 110, the memory 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 send information stored in the memory unit 130 to the outside (e.g., other communication devices) via the communication unit 110 through a wireless / wired interface, or store information received from the outside (e.g., other communication devices) via the communication unit 110 in the memory unit 130 through a wireless / wired interface.

[0401] 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.14 100a), vehicles ( Fig.14 100b-1 and 100b-2), XR devices ( Fig.14 100c), handheld device ( Fig.14 100d), household appliances ( Fig.14 100e), IoT devices ( Fig.14 100f), digital broadcasting terminal, holographic device, public safety device, MTC device, medical device, fintech device (or financial device), security device, climate / environmental device, AI server / device ( Fig.14 400), BS( Fig.14 200), network nodes, etc. The wireless device can be used in a mobile or fixed location according to the usage example / service.

[0402] exist Fig.16In 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 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.

[0403] Fig.17 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.

[0404] Reference Fig.17 , 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.16 Block 110 / 130 / 140.

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

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

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

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

[0409] Reference Fig.18 , 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.

[0410] Table 6 describes the DRX operation of the UE (in the RRC_CONNECTED state). Referring to Table 6, 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.

[0411] [Table 6]

[0412]

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

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

[0415] - Value of drx-InactivityTimer: defines the duration of the time period that the UE wakes up after detecting a PDCCH opportunity indicating a PDCCH for initial UL or DL ​​data.

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

[0417] - Value of drx-HARQ-RTT-TimerDL: defines the duration of the maximum time period after receiving a UL initial transmission grant until receiving a UL retransmission grant.

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

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

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

[0421] 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, the embodiments of the present disclosure can be implemented 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 clearly understood 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.

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

[0423] Industrial Applicability

[0424] 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 configuration information about a time domain resource allocation TDRA table; receiving downlink control information DCI including a TDRA field indicating a row of the TDRA table for scheduling a plurality of physical downlink shared channels PDSCH; receiving the plurality of PDSCHs based on the DCI; Determine a hybrid automatic repeat request HARQ-acknowledgement ACK for a PDSCH opportunity set based on a configuration type 1 HARQ-ACK codebook; as well as transmitting the HARQ-ACK in a time slot associated with a K1 value indicated by the DCI among K1 values ​​that are PDSCH-to-HARQ feedback timing values ​​configured in the UE through higher layer signaling, The UE determines the PDSCH opportunity set to include: i) a first PDSCH opportunity that can be scheduled in a first time slot associated with the K1 value configured by the higher layer signaling, and ii) a second PDSCH opportunity that can be scheduled in at least one second time slot determined based on at least one K0 value as a PDCCH to PDSCH time slot offset, and Among them, at least one row of the TDRA table includes multiple parameter sets of {K0, PDSCH mapping type, start symbol and length indicator value SLIV}.

2. The method according to claim 1, wherein: determining a first ACK / Negative ACK (NACK) sub-payload for each of the first time slots based on the first PDSCH opportunity, and Wherein, a second ACK / NACK sub-payload for the at least one second time slot is determined based on the second PDSCH opportunity.

3. The method according to claim 2, wherein: The UE generates a total payload of HARQ-ACK based on a first type codebook by concatenating the first ACK / NACK sub-payload and the second ACK / NACK sub-payload or arranging the first ACK / NACK sub-payload and the second ACK / NACK sub-payload based on a time sequence of a corresponding time slot.

4. The method according to claim 1, wherein: In the time domain, the at least one second time slot is located before the first time slot.

5. The method according to claim 1, wherein: The at least one second time slot is determined from among time slots other than the first time slot.

6. The method according to claim 1, wherein: The at least one second time slot is determined based on “K0” included in the parameter set not corresponding to the last time slot in each row of the TDRA table.

7. The method according to claim 1, wherein: The first time slot is determined by combining the K1 value configured through higher layer signaling with the parameter set corresponding to the last time slot in each row of the TDRA table.

8. The method according to claim 1, wherein: The HARQ-ACK is generated for valid PDSCHs among the plurality of PDSCHs except for invalid PDSCHs overlapping with uplink UL symbols configured through higher layer signaling.

9. The method according to claim 1, wherein: The UE determines the first PDSCH opportunity and the second PDSCH opportunity while excluding an invalid PDSCH overlapping with a UL symbol configured through higher layer signaling. 10 . A computer-readable recording medium recording 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 operation of the processor includes: Receiving configuration information about a time domain resource allocation TDRA table; receiving downlink control information DCI including a TDRA field indicating a row of the TDRA table for scheduling a plurality of physical downlink shared channels PDSCH; receiving the plurality of PDSCHs based on the DCI; Determining a hybrid automatic repeat request HARQ-acknowledgement ACK for a PDSCH opportunity set based on a configuration type 1 HARQ-ACK codebook; and transmitting the HARQ-ACK in a time slot associated with a K1 value indicated by the DCI among K1 values ​​that are PDSCH-to-HARQ feedback timing values ​​configured in the apparatus through higher layer signaling, The processor determines the PDSCH opportunity set to include: i) a first PDSCH opportunity that can be scheduled in a first time slot associated with the K1 value configured by the higher layer signaling, and ii) a second PDSCH opportunity that can be scheduled in at least one second time slot determined based on at least one K0 value as a PDCCH to PDSCH time slot offset, and Among them, at least one row of the TDRA table includes multiple parameter sets of {K0, PDSCH mapping type, start symbol and length indicator value SLIV}.

12. The device according to claim 11, further comprising: a transceiver configured to send or receive wireless signals under the control of the processor, The device is a user equipment UE based on the 3rd Generation Partnership Project 3GPP.

13. A method for sending a signal by a base station BS in a wireless communication system, the method comprising the following steps: Sending configuration information about the time domain resource allocation TDRA table; Sending downlink control information DCI including a TDRA field indicating a row of the TDRA table for scheduling a plurality of physical downlink shared channels PDSCH; Sending the plurality of PDSCHs based on the DCI; receiving a hybrid automatic repeat request HARQ-acknowledgement ACK in a time slot associated with a K1 value indicated by the DCI among K1 values ​​that are PDSCH-to-HARQ feedback timing values ​​configured in a user equipment UE by the BS through higher layer signaling; as well as Determine the PDSCH to be retransmitted by processing the received HARQ-ACK, Wherein, when processing the received HARQ-ACK, based on configuring a type 1 HARQ-ACK codebook in the UE, the BS determines a PDSCH opportunity set, and The PDSCH opportunity set includes: i) a first PDSCH opportunity that can be scheduled in a first time slot associated with the K1 value configured by the higher layer signaling, and ii) a second PDSCH opportunity that can be scheduled in at least one second time slot determined based on at least one K0 value as a PDCCH to PDSCH time slot offset, and Among them, at least one row of the TDRA table includes multiple parameter sets of {K0, PDSCH mapping type, start symbol and length indicator value SLIV}.

14. A base station BS for wireless communication, the BS comprising: a memory configured to store instructions; as well as a processor configured to perform operations by executing the instructions, The operation of the processor includes: Sending configuration information about the time domain resource allocation TDRA table; Sending downlink control information DCI including a TDRA field indicating a row of the TDRA table for scheduling a plurality of physical downlink shared channels PDSCH; Sending the plurality of PDSCHs based on the DCI; receiving a hybrid automatic repeat request HARQ-acknowledgement ACK in a time slot associated with a K1 value indicated by the DCI among K1 values ​​that are PDSCH-to-HARQ feedback timing values ​​configured in a user equipment UE by the BS; and Determine the PDSCH to be retransmitted by processing the received HARQ-ACK, and Wherein, when processing the received HARQ-ACK, based on configuring a type 1 HARQ-ACK codebook in the UE, the processor determines a PDSCH opportunity set, and The PDSCH opportunity set includes: i) a first PDSCH opportunity that can be scheduled in a first time slot associated with the K1 value configured by higher layer signaling, and ii) a second PDSCH opportunity that can be scheduled in at least one second time slot determined based on at least one K0 value as a PDCCH to PDSCH time slot offset, and Among them, at least one row of the TDRA table includes multiple parameter sets of {K0, PDSCH mapping type, start symbol and length indicator value SLIV}.

Images