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

Abstract

A UE according to an embodiment may receive a configuration of a plurality of first TDRA entries of each cell for individual scheduling of each cell, receive a configuration of a plurality of second TDRA entries including TDRA information for a plurality of cells through each entry for multi-cell scheduling, and receive DCI for multi-cell scheduling through a PDCCH, the DCI for multi-cell scheduling provides one TDRA field for one or all of at least two cells scheduled together, the value of the one TDRA field being related to one of a plurality of second TDRA entries, and TDRA information of the plurality of cells included in each of the plurality of second TDRA entries may be configured based on the plurality of first TDRA entries configured for individual scheduling of the respective cells.

Description

Technical Field

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

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

[0003] Technical tasks

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

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

[0006] Technical Solution

[0007] In one technical aspect of the present disclosure, a method for receiving a signal by a user equipment (UE) in a wireless communication system is provided, the method comprising the following steps: receiving a configuration of a plurality of first time domain resource allocation (TDRA) entries for each cell for separate scheduling of each cell; receiving a configuration of a plurality of second TDRA time domain resource allocation (TDRA) entries, each second TDRA entry including TDRA information of a plurality of cells for multi-cell scheduling; and receiving downlink control information (DCI) for multi-cell scheduling through a physical downlink control channel (PDCCH). The DCI for multi-cell scheduling may provide a TDRA field for all one or more cells scheduled together. The value of this one TDRA field may be related to one of the plurality of second TDRA entries. Furthermore, the TDRA information of the plurality of cells included in each of the plurality of second TDRA entries may be configured based on the plurality of first TDRA entries configured for separate scheduling of the respective cells.

[0008] Each second TDRA entry may be associated with a plurality of TDRA parameter sets including a first TDRA parameter set for a first cell and a second TDRA parameter set for a second cell. The first TDRA parameter set may belong to a first TDRA entry configured for the first cell. And, the second TDRA parameter set may belong to a first TDRA entry set for the second cell. Each parameter set may include a combination of {K0, mapping_type, SLIV} parameters. "K0" may indicate a time slot offset from a PDCCH to a scheduling signal. "mapping_type" may indicate a resource mapping type of a scheduling signal. And, "SLIV" may indicate a starting symbol and length information of a scheduling signal.

[0009] Each second TDRA entry may be related to a combination of N first TDRA entries for N cells.

[0010] The TDRA information of the first cell and the TDRA information of the second cell included in the respective second TDRA entries may be one of the first TDRA entries of the first cell and one of the first TDRA entries of the second cell, respectively.

[0011] The UE may transmit or receive signals on one or more cells scheduled together through DCI for multi-cell scheduling.

[0012] The configuration of the first TDRA entry and the configuration of the second TDRA entry may be received through higher layer signaling, respectively.

[0013] The plurality of first TDRA entries configured for each of the plurality of cells may be associated with N first TDRA tables for the N cells. The plurality of second TDRA entries may be associated with a single second TDRA table configured for the N cells.

[0014] In another technical aspect of the present disclosure, there is provided a computer-readable recording medium having recorded thereon a program for executing the above method.

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

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

[0017] In another technical aspect of the present disclosure, a method for sending a signal by a base station in a wireless communication system is provided, the method comprising the following steps: sending a configuration of multiple first time domain resource allocation (TDRA) entries for each cell for separate scheduling of each cell; sending a configuration of multiple second TDRA time domain resource allocation (TDRA) entries, each second TDRA entry including TDRA information of multiple cells for multi-cell scheduling; and sending downlink control information (DCI) for multi-cell scheduling through a physical downlink control channel (PDCCH). The DCI for multi-cell scheduling may provide a single TDRA field for all one or more cells scheduled together. The value of a single TDRA field may be related to one of the multiple second TDRA entries. The TDRA information of multiple cells included in each of the multiple second TDRA entries may be configured based on multiple first TDRA entries configured for separate scheduling of each cell.

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

[0019] Beneficial Effects

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

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

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

[0023] Figure 2 Shows the radio frame structure.

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

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

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

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

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

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

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

[0031] Fig.10 is a diagram showing a table configuration of a TDRA field for multi-cell scheduling.

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

[0033] Fig.12 An example of cells co-scheduled by DCI is shown.

[0034] Fig.13 An example of alignment of A / N bits is shown.

[0035] Fig.14 is a diagram illustrating a method of receiving a signal by a user equipment (UE) according to an embodiment.

[0036] Fig.15 is a diagram illustrating a method of transmitting a signal by a base station (BS) according to an embodiment.

[0037] Fig.16 is a diagram illustrating a method of transmitting and receiving a signal in a network system according to an embodiment.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0053] [Table 1]

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

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

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

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

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

[0059] [Table 2]

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

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

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

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

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

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

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

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

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

[0069] -controlResourceSetId: CORESET related to SS

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

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

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

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

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

[0075] [Table 3]

[0076]

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

[0078] [Table 4]

[0079]

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

[0081] DCI format 0_0 and DCI format 1_0 may be referred to as fallback DCI formats, while DCI format 0_1 ​​and DCI format 1_1 may be referred to as non-fallback DCI formats. Under the fallback DCI format, the DCI size / field configuration remains the same regardless of the UE configuration. In contrast, under the non-fallback DCI format, the DCI size / field configuration varies according to the UE configuration.

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

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

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

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

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

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

[0088] [Table 5]

[0089]

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0116] Carrier Aggregation

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

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

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

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

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

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

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

[0124] For cross-carrier scheduling, a carrier indicator field (CIF) is used. The CIF can be semi-statically disabled / enabled by UE-specific (or UE group-specific) higher layer (e.g., radio resource control (RRC)) signaling. The CIF field is an x-bit field (e.g., x=3) in the PDCCH (i.e., DCI) and can be used to indicate the (serving) cell index of the scheduled cell.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0141] [Table 6]

[0142]

[0143] Multi-cell scheduling DCI

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

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

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

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

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

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

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

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

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

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

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

[0155] 1) Existing operations

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

[0157] 2) Proposed Operation

[0158] A. The operations proposed below are not limited to the type 1 codebook and can be applied to any (eg, type 1 or type 2 or type 3) HARQ-ACK codebook.

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

[0160] C. On the other hand, if an invalid cell is included in the cells scheduled / indicated by the multi-cell DCI, it is operable to perform PDSCH reception only for the remaining cells, and not to perform PDSCH reception for the corresponding invalid cell.

[0161] i. Invalid cells may correspond to: Case 1) a cell in which the PDSCH (PUSCH) resources indicated by the multi-cell DCI overlap with the semi-static UL (DL) symbols in time; and / or Case 2) a cell in which the frequency resources of the PDSCH (PUSCH) allocated by the multi-cell DCI are indicated as invalid values ​​(e.g., in the form of a bitmap with all bits being "0" or a RIV with all bits being "1"); and / or Case 3) a cell in which the time resources of the PDSCH (PUSCH) allocated by the multi-cell DCI are indicated as invalid values ​​(e.g., in the form of a SLIV with all bits being "1"), or the TDRA table is not configured or does not exist. A cell corresponding to a row (index) (e.g., a combination of {K0 / K2, SLIV, mapping type}) of a code point indicated by the TDRA field in a multi-cell DCI; and / or case 4) a cell indicating TB disabled operation for all TBs (of the corresponding cell) through multi-cell DCI; and / or case 5) a deactivated Scell; and / or case 6) a cell operating as a dormant BWP; and / or case 7) a cell operating in a DRX off state (no PDCCH monitoring); and / or case 8) a cell corresponding to a specific time interval (or specific BWP) configured / instructed to stop a series of transmission / reception operations for the purpose of base station energy saving; and so on.

[0162] ii. On the other hand, in order to reduce the complexity of multi-cell DCI configuration and scheduling-related operations, there may be such a restriction: all SCSs used / applied to cells belonging to the combination of cells simultaneously scheduled from the corresponding DCI (for convenience, referred to as a "co-scheduled cell set") should have the same value. If the SCS used / applied between cells belonging to a specific co-scheduled cell set (configured / indicated to the active BWP of each cell) have different values, PDSCH / PUSCH transmission / reception may be performed only for cells using / applying a specific (valid) SCS, and PDSCH / PUSCH transmission / reception may be omitted for the remaining cells using / applying an (invalid) SCS. In this case, Case 9), the cell using / applying the corresponding invalid SCS may correspond to an invalid cell.

[0163] 1. In the case of the above-mentioned valid SCS, it can be pre-configured through RRC, etc. (for example, a separate valid SCS value is configured for each co-scheduled cell set, or a single valid SCS value is configured for all co-scheduled cell sets), or determined based on specific rules (for example, Alternative SCS 1) is determined as the SCS value used / applied to a specific cell (for example, the lowest cell index) belonging to the co-scheduled cell set, or Alternative SCS 2) is determined as the minimum / maximum value among the SCSs of the cells belonging to the co-scheduled cell set, or Alternative SCS 3) is determined as the SCS value used / applied to the maximum number of cells among the cells belonging to the co-scheduled cell set (if there are multiple SCS values ​​used / applied to the maximum number of cells, the value determined by applying Alternative SCS 1 / 2 to the corresponding multiple SCS values).

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

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

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

[0167] 3) Proposal 1-1

[0168] When configuring multi-cell DCI-based PDSCH scheduling, for a cell that becomes a multi-cell DCI scheduling target when performing a per-cell SLIV pruning process for a type 1A / N codebook configuration, only SLIVs (among multiple SLIVs) associated with the corresponding cell mapped / configured to each multi-SLIV row in the extended TDRA table may be extracted and included in the SLIV set of the SLIV pruning process applied to the corresponding cell. (For convenience, this process is referred to as "SLIV set expansion.")

[0169] i. On the other hand, SLIV set expansion may not be performed on invalid cells (e.g., cells corresponding to cases 5 / 6 / 7 / 8 / 9 in particular). (In other words, invalid cells (e.g., cases 5 / 6 / 7 / 8 / 9) may be excluded / excepted during the SLIV set expansion process.)

[0170] 1. Alternatively, SLIV set extension may be performed for invalid cells (e.g., cases 5 / 6 / 7 / 8 / 9), but for invalid cells, SLIV set extension may be performed based on parameters / values ​​set in a specific DL / UL BWP (e.g., the first active DL / UP BWP initially enabled and specified by parameters firstActiveDownlinkBWP / firstActiveUplinkBWP or the latest active DL / UP BWP most recently enabled (excluding the dormant BWP)).

[0171] ii. As another method, in order to reduce the UE complexity caused by performing SLIV set extension (SLIV pruning processing based on this), when configuring the extended TDRA table (to omit the SLIV set extension processing), restrictions can be made so that each multiple SLIV row is configured in the extended TDRA table in such a way that only TDRA rows / entries (for example, SLIV and / or K0) belonging to the single-cell TDRA table configured for the existing per-cell single-cell DCI-based scheduling purpose are combined between multiple cells.

[0172] For example, refer to Fig.10 In the example shown, it is assumed that the ranges of the {k0, mapping type, SLIV} parameters that can be configured through RRC signaling are "0-32", "Type A or B" and "0-127", respectively, and TDRA tables (a), (b) and (c) are set in cells A, B and C based on these parameter ranges. In actual operation, each TDRA table is set for each BWP of each cell, but for convenience of explanation, Fig.10 The BWP division is omitted in . TDRA tables (a), (b) and (c) are set for scheduling of each individual cell, and when cell A is scheduled by the SC DCI format, the TDRA field of the SC DCI format indicates any one of indexes 1 to M in the TDRA table (a). When cell B is scheduled by the SC DCI format, the TDRA field of the SC DCI format indicates any one of indexes 1 to X in the TDRA table (b). When cell C is scheduled by the SC DCI format, the TDRA field of the single-cell (SC) DCI format indicates any one of indexes 1 to Y in the TDRA table (c). When an extended TDRA table is configured for the TDRA field of a multi-cell (MC) DCI as in the present proposal, each entry (index) of the extended TDRA table indicates {k0, mapping type, SLIV} of each of cells A, cell B and cell C that can be scheduled together (in fact, each BWP of each cell). For example, Fig.10The combination of {k0, mapping type, SLIV} of the extended TDRA table (d) is configured based on the M entries of the TDRA table (a) configured in combination with the SC DCI, the X entries of the TDRA table (b), and the Y entries of the TDRA table (c). TDRA tables (a), (b), and (c) become supersets of the extended TDRA table (d), and new {k0, mapping type, SLIV} combinations not included in any TDRA table (a), (b), and (c) are restricted to be unavailable for the extended TDRA table (d). However, because the combination of TDRA tables (a), (b), and (c) has a superset-subset relationship with the extended TDRA table (d), not all entries in the TDRA tables (a), (b), and (c) must be included in the extended TDRA table (d), and the entry / index order of the TDRA tables (a), (b), and (c) can also be reconfigured / changed in the extended TDRA table (d). However, the entries of TDRA table (a) are also used for cell A in the extended TDRA table (d) (actually, for the corresponding BWP of cell A), but not for cell B or cell C. Similarly, the entries of TDRA table (b) are used for cell B in the extended TDRA table (d) (actually, for the corresponding BWP of cell B), and the entries of TDRA table (c) are also used for cell C in the extended TDRA table (d) (actually, for the corresponding BWP of cell C). In this way, when the extended TDRA table (d) is reconfigured using the TDRA tables (a), (b) and (c) previously set for SC DCI, the problem of increasing the SLIV pruning overhead of MCDCI (e.g., the amount of calculation / complexity required for SLIV pruning) can be minimized. For example, if SLIV pruning of each of TDRA tables (a), (b) and (c) has been performed for SC DCI, the corresponding results can be used again for the SLIV pruning process of the extended TDRA table (d), thereby minimizing the increase in SLIV pruning overhead and solving the signaling overhead problem when configuring the extended TDRA table. Although for convenience of explanation, Fig.10 One TDRA table per cell is shown, but as described above, in practice, multiple TDRA tables may be configured for multiple BWPs configured in one cell, and thus an extended TDRA table is configured for all BWP combinations in all cells, and the size of the extended TDRA table is greatly increased. Thus, when a new extended TDRA table entry is determined and signaled without any restriction for all BWP combinations in all cells, there is a problem that the signaling overhead of the corresponding entry becomes very large due to the increase in the size of the extended TDRA table. However, when the extended TDRA table is reconfigured within the TDRA table configured for SC DCI as in the proposed method, the signaling overhead problem can also be advantageously solved. For example, referring to Fig.10, the signaling for configuring the extended TDRA table (d) does not include the {k0, mapping type, SLIV} value included in the extended TDRA table as is, but can use the row index of the TDRA table configured for SC DCI to set / indicate the configuration of the extended TDRA table. Specifically, the signaling for configuring the extended TDRA table (d) can be set / indicated [M, 1, 2] for the first row (i.e., index = 1) of the extended TDRA table (rather than setting / indicating [{k0 = 3, mapping type = B, SLIV = 7}, {k0 = 5, mapping type = B, SLIV = 20}, {k0 = 23, mapping type = A, SLIV = 50}]) to minimize the signaling overhead.

[0173] On the other hand, the application of the above proposal is not limited to the TDRA field of the MC DCI, but can also be applied to the extended table (extended parameter set) referenced by a single specific field of the MC DCI applied for the cells scheduled together. For example, if only one rate matching (RM) field and one SRS request field are included in the MC DCI, the extended RM table referenced by the RM field can be constrained to be configured based on the entries of the SC RM table, and the extended SRS request table referenced by the SRS request field can be constrained to be configured based on the entries of the SCSRS request table.

[0174] iii. As another method, the SLIV set expansion process is omitted (without imposing a separate restriction on the extended TDRA table configuration (as above)), and the SLIV pruning process is performed only based on the single-cell TDRA table of each cell as before. However, if the PDSCH SLIV resources scheduled on a specific cell do not exist in the single-cell TDRA table configured in the corresponding cell, the corresponding cell may be treated as an invalid cell so that PDSCH reception on the corresponding cell is omitted and the corresponding HARQ-ACK feedback is not configured.

[0175] 4) Proposal 1-2

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

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

[0178] ii. On the other hand, K1 set extension may not be performed on invalid cells (e.g., cells corresponding to cases 5 / 6 / 7 / 8 / 9). (In other words, invalid cells (e.g., cases 5 / 6 / 7 / 8 / 9) may be excluded / excluded during the above-mentioned K1 set extension process.)

[0179] 1. Alternatively, K1 set extension may also be performed for invalid cells (e.g., cases 5 / 6 / 7 / 8 / 9). However, K1 set extension may be performed for invalid cells based on parameters / values ​​set in a specific DL / UL BWP (e.g., initially enabled by firstActiveDownlinkBWP / firstActiveUplinkBWP and designated first enabled DL / UL BWP or the latest active DL / UL BWP enabled (except dormant BWP)).

[0180] iii. As another method, in order to reduce the UE complexity caused by performing K1 set extension (SLIV pruning processing based on it), all last symbols (ends) of PDSCH scheduled on (one or more) multiple cells belonging to each co-scheduled cell set (K1 set extension processing is omitted) can be restricted to belong to the same PUCCH (sub) time slot (for example, so that the K0 value applied to PDSCH reception and / or the last symbol (end) position of PDSCH are set equally among multiple cells (scheduled simultaneously)).

[0181] iv. As another method, the SLIV pruning process is performed based only on the original (original) K1 set in the same manner as before by omitting the K1 set extension process (without any separate restrictions on the K0 and / or PDSCH end configuration). However, if there is no DL time slot including the PDSCH resources scheduled on a specific cell in the bundling window corresponding to the original K1 set, the corresponding cell may be regarded as / treated as an invalid cell so that it can be operated in a manner that PDSCH reception on the corresponding cell is omitted and the corresponding HARQ-ACK feedback is not configured.

[0182] v. As another method, the base station may directly configure the added K1 value to be extended in addition to the original K1 set. Therefore, the UE performs SLIV pruning processing based on a new K1 set that combines the original K1 set with the added K1 value. However, if there is no DL time slot including the PDSCH resources scheduled on a specific cell in the bundling window corresponding to the new K1 set, the cell may be regarded as / treated as an invalid cell so that it can operate in a manner that PDSCH reception on the corresponding cell is omitted and HARQ-ACK feedback is not configured.

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

[0184] 1) Proposed Operation

[0185] A. In the case of type 2 codebook, when multi-cell DCI-based PDSCH scheduling is configured, a counter / total-DAI value may be independently determined and signaled for each of the existing single-cell (PDSCH scheduling) DCI (type) and multi-cell (PDSCH scheduling) DCI (type) (i.e., the DCI / PDSCH order / total scheduled for each DCI type is independently determined / signaled, and a separate sub-codebook is configured for each DCI type based on this) (in other words, a single-cell DCI may be signaled by determining only the DAI value of the single-cell DCI, and a multi-cell DCI may be signaled by determining only the DAI value of the multi-cell DCI).

[0186] B. As another method, a counter / total-DAI value may be independently determined and signaled for each of a case where only one PDSCH is scheduled (on a cell) through a single-cell DCI (a single-cell case) and a case where multiple PDSCHs are scheduled (on a cell) through a multi-cell DCI (a multi-cell case) (i.e., the DCI / PDSCH order / total scheduled for each case is independently determined / signaled, and a separate subcodebook is configured for each case based on this) (in other words, the DCI corresponding to the single-cell case may be signaled by determining the DAI value only for the single-cell case, and the DCI corresponding to the multi-cell case may be signaled by determining the DAI value only for the multi-cell case).

[0187] i. In the case of the single-cell case described above, it may include: Alternative 1) a case where one PDSCH transmission is indicated (on the cell) by a single-cell DCI; or Alternative 2) a case where (one or) multiple PDSCH transmissions are indicated (on the cell) by (single-cell DCI or) multi-cell DCI and the UE actually receives only one PDSCH (on the cell) among them (for example, except for invalid cells) (in the case of the latter case, Alternative 2, the multi-cell case may correspond to a case where multiple PDSCH transmissions are indicated (on the cell) by multi-cell DCI and the UE actually receives two or more PDSCHs (on the cell) among them (for example, except for invalid cells)).

[0188] C. In addition, if the number of TBs simultaneously scheduled through multi-cell DCI is two (for example, a PDSCH carrying one TB is scheduled on each of two cells or a PDSCH carrying two TBs is scheduled on one cell), the DAI value determination / signaling (for each case) and the subcodebook configuration method may be exceptionally applied while being regarded / classified as a single-cell case.

[0189] i. This method is applicable only when the single-cell DCI scheduling any (at least one) cell is configured to allow scheduling of PDSCH transmission carrying two TBs, or regardless of whether such a configuration exists.

[0190] D. In addition, if the maximum number of TBs scheduled simultaneously via multi-cell DCI is two (e.g., a PDSCH carrying one TB is scheduled on each of two cells or a PDSCH carrying two TBs is scheduled on one cell), the counter / total-DAI value may be signaled exceptionally by determining it jointly for all DCI / cases in the same manner as before, without distinguishing between single-cell DCI / cases and multi-cell DCI / cases (i.e., determining / signaling the DCI / PDSCH order / sum scheduled for the entire DCI / case and configuring only one (sub) codebook for the entire DCI / case based on this).

[0191] i. This method is applicable only when the single-cell DCI scheduling any (at least one) cell is configured to allow scheduling of PDSCH transmission carrying two TBs, and is applicable regardless of whether such configuration exists.

[0192] E. On the other hand, when multiple cells are configured for the UE (for example, a PUCCH (cell) group configured for the corresponding UE) in the existing single-cell DCI-based operation (in the form of CA), both the counter-DAI field / information and the total-DAI field / information are configured / indicated in the DL (scheduling) DCI, and when only one cell is configured for the UE (in the form of non-CA), only the counter-DAI field / information may be configured / indicated in the DL DCI without the total-DAI field / information.

[0193] i. The reason why only the counter-DAI field / information can be configured / indicated in the DL DCI in the non-CA case as described above is that, because only one DCI scheduling only the (same) cell is sent / received through one timing point (e.g., PDCCH monitoring accumulation or time slot), the total-DAI value indicating the total number of accumulated DCI / PDSCHs scheduled so far and the counter-DAI value indicating the scheduling order of the nth scheduled DCI / PDSCH are the same.

[0194] F. On the other hand, if only one cell combination consisting of specific multiple cells is configured to be scheduled / indicated by DL multi-cell DCI (for one PUCCH group configured to the UE) in the case of configuring multi-cell DCI-based (DL) scheduling (i.e., not configured to allow scheduling / indication of another cell combination or a single cell), (because only one DCI scheduling the corresponding cell combination is sent / received through one timing point (e.g., PDCCH monitoring accumulation or time slot)), only the counter-DAI field / information (without the total-DAI field / information) may be configured / indicated within the DL multi-cell DCI.

[0195] i. Otherwise, if it is configured to allow (for one PUCCH group configured to the UE) scheduling / indicating multiple cell combinations or a single cell through DL multi-cell DCI, both the counter-DAI field / information and the total-DAI field / information may be configured / indicated in the DL multi-cell DCI.

[0196] G. Alternatively, if in the case of configuring multi-cell DCI-based (DL) scheduling, it is configured to allow (for one PUCCH group configured to the UE) only one cell combination consisting of a specific plurality of cells to be scheduled / indicated through the DL multi-cell DCI (i.e., it is not configured to allow scheduling / indicating another cell combination or a single cell), or if it is configured to allow scheduling / indicating only a specific plurality of cell combinations (each cell combination consisting of a plurality of cells) through the DL multi-cell DCI (i.e., it is not configured to allow scheduling / indicating another cell combination or a single cell) and the remaining cell combinations (corresponding to the small cell) are included in the DL multi-cell DCI. Each cell combination belonging to the corresponding multiple cell combinations is configured in a manner of scheduling at least one cell of each of the corresponding multiple cell combinations (except for the multi-cell combination) (for example, if the three cell combinations are {cell 1, cell 3}, {cell 2, cell 3, cell 4} and {cell 1, cell 4}), (since only one DCI that schedules only one cell combination among the corresponding multiple cell combinations is sent / received through one timing point (for example, PDCCH monitoring shielding or time slot)), only the counter-DAI field / information (without the total-DAI field / information) can be configured / indicated in the DL multi-cell DCI.

[0197] i. Otherwise, if it is configured to allow (for one PUCCH group configured to the UE) scheduling / indicating multiple cell combinations consisting of different cells (without the same cell) (for example, two cell combinations corresponding to {cell 1, cell 2} and {cell 3, cell 4}) or a single cell through DL multi-cell DCI, both the counter-DAI field / information and the total-DAI field / information can be configured / indicated in the DL multi-cell DCI.

[0198] 2) Proposal 2-1

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

[0200] A. When multiple (multi-cell) DCIs including multi-cell DCI (and / or multi-PDSCH DCI) are transmitted / received through the same timing point (e.g., PDCCH monitoring opportunity or time slot), a counter-DAI value corresponding to the corresponding multi-cell DCI (signaled through the corresponding DCI) is determined based on the lowest (or highest) cell index among the multiple cells scheduled by the corresponding multi-cell DCI and the corresponding multi-cell DCI (in addition, when determining the last DCI including a PUCCH resource indicator (PRI) indicating a PUCCH resource for HARQ-ACK transmission for PDSCH reception, (when multiple (multi-cell) DCIs are transmitted / received through the same timing point (last while indicating the same HARQ-ACK transmission timing point), the last DCI can be determined based on the lowest (or highest) cell index among the multiple cells scheduled by the multi-cell DCI).

[0201] i. For example, in the case where two multi-cell DCIs are transmitted / received at the same timing point (e.g., PDCCH monitoring opportunity or time slot), when comparing the lowest (or highest) cell index scheduled by each DCI (among multiple cells), it may be a structure that can determine / signal the counter (DAI) value corresponding to the DCI scheduling the lower cell index. For example, assuming that the multiple DCIs received at the same timing point include at least one multi-cell DCI, the first DCI in the at least one multi-cell DCI schedules {cell A, cell B, and cell C}, and cell A has a cell index lower than cell B and cell C. The second DCI received at the same timing point as the first DCI may be a multi-cell DCI or a single-cell DCI. It is assumed that the cell with the lowest cell index among the one or more cells scheduled by the second DCI is cell D. If the cell index of cell A is less than the cell index of cell D, the C-DAI value of the first DCI is counted first (e.g., relative to the multi-cell scheduling of cells A, cell B, and cell C), and then the C-DAI value of the second DCI is counted. If the cell index of cell A>the cell index of cell D, the C-DAI value of the second DCI is counted first, and then the C-DAI value of the first DCI is counted. As an additional example, when two (multi-cell) DCIs are sent / received through the same timing point (last while indicating the same HARQ-ACK transmission timing point), when comparing the lowest (or highest) cell index scheduled by each DCI (among multiple cells), the DCI scheduling the highest cell index can be determined as the last DCI, thereby determining the PUCCH resource based on the PRI indicated by the corresponding DCI.

[0202] ii. In the above, if the lowest (or highest) cell index scheduled by each DCI is the same, a structure may be such that the counter (DAI) value corresponding to the DCI that schedules the PDSCH with an earlier start (or end) symbol timing point among the PDSCHs sent on the cell with the corresponding cell index is determined / signaled as a lower value. In addition, if the lowest (or highest) cell index scheduled by each DCI is the same, the DCI that schedules the PDSCH with the latest start (or end) symbol timing point among the PDSCHs sent on the cell with the corresponding cell index may be determined as the last DCI, thereby determining the PUCCH resource based on the PRI indicated by the corresponding DCI.

[0203] iii. On the other hand, in case of a plurality of cells scheduled by or with a multi-cell DCI, they may be regarded / applied as corresponding to the remaining part of the plurality of cells except for the invalid cell.

[0204] B. As another method, if multiple (multi-cell) DCIs including multi-cell DCI (and / or multi-PDSCH DCI) are transmitted / received at the same timing point (e.g., PDCCH monitoring opportunity or time slot), the counter-DAI value corresponding to the multi-cell DCI (signaled by the corresponding DCI) can be determined based on the PDSCH having the earliest transmission start (or end) symbol timing point among the multiple PDSCHs on the multiple cells scheduled by the corresponding multi-cell DCI. In addition, when determining the last DCI containing the PRI indicating the PUCCH resources for HARQ-ACK transmission for PDSCH reception, (when multiple (multi-cell) DCIs are transmitted / received through the same timing point (last while indicating the same HARQ-ACK transmission timing point), the last DCI can be determined based on the PDSCH having the earliest transmission start (or end) symbol timing point among the multiple PDSCHs on the multiple cells scheduled by the multi-cell DCI.

[0205] i. For example, if two multi-cell DCIs are transmitted / received at the same timing point, when comparing the PDSCH with the earliest start (or end) symbol timing point scheduled for each DCI (among multiple PDSCHs on multiple cells), the counter (DAI) value corresponding to the DCI that schedules the PDSCH with the earlier start (or end) symbol timing point may be determined / signaled as a lower value. As an additional example, if two (multi-cell) DCIs are transmitted / received through the same timing point (last while indicating the same HARQ-ACK transmission timing point), when comparing the PDSCH with the earliest start (end) symbol timing point scheduled with each DCI (among multiple PDSCHs on multiple cells), the DCI that schedules the PDSCH with the latest start (or end) symbol point is determined as the last DCI, so that the PUCCH resources can be determined based on the PRI indicated by the corresponding DCI.

[0206] ii. In the above description, if the start (or end) symbol timing point of the PDSCH with the earliest start (or end) symbol timing point scheduled by each DCI is the same, then the structure may be such that the counter (DAI) value corresponding to the DCI of the PDSCH sent on the cell with the lower cell index among the corresponding PDSCHs scheduled may be determined / signaled as a lower value. In addition, if the start (or end) symbol timing point of the PDSCH with the latest start (or end) symbol timing point scheduled by each DCI is the same, the DCI of the PDSCH sent on the cell with the highest cell index among the corresponding PDSCHs scheduled is determined as the last DCI, thereby determining the PUCCH resources based on the PRI indicated by the corresponding DCI.

[0207] iii. On the other hand, in the case of a plurality of cells scheduled by or with a multi-cell DCI in the above description, they may be regarded / applied as corresponding to the remaining portion of the plurality of cells except for the invalid cell.

[0208] C. As another method, when multiple (multi-cell) DCIs including multi-cell DCI (and / or multi-PDSCH DCI) are transmitted / received at the same timing point (e.g., PDCCH monitoring opportunity or time slot), the counter-DAI value corresponding to the multi-cell DCI (or signaled by the corresponding multi-cell DCI) can be determined based on the PDSCH having the latest transmission start (or end) symbol timing point among the multiple PDSCHs on the multiple cells scheduled by the corresponding multi-cell DCI. In addition, when determining the last DCI containing the PRI indicating the PUCCH resources for HARQ-ACK transmission for PDSCH reception, (when multiple (multi-cell) DCIs are transmitted / received through the same timing point (last while indicating the same HARQ-ACK transmission timing point), the last DCI can be determined based on the PDSCH having the latest transmission start (or end) symbol timing point among the multiple PDSCHs scheduled by the multi-cell DCI.

[0209] i. For example, in the case where two multi-cell DCIs are transmitted / received at the same timing point, when comparing the PDSCH with the latest start (or end) symbol timing point scheduled by each DCI (among multiple PDSCHs on multiple cells), it can be a structure in which the counter (DAI) value corresponding to the DCI scheduling the PDSCH with an earlier start (or end) symbol timing point can be determined / signaled as a lower value. As an additional example, if two (multi-cell) DCIs are transmitted / received at the same timing point (last while indicating the same HARQ-ACK transmission timing point), when comparing the PDSCH with the latest start (or end) symbol timing scheduled by each DCI (among multiple PDSCHs on multiple cells), the DCI scheduling the PDSCH with the latest start (or end) symbol timing point is determined as the last DCI, thereby determining the PUCCH resource based on the PRI indicated by the corresponding DCI.

[0210] ii. In the above description, if the start (or end) symbol timing point of the PDSCH with the latest start (or end) symbol timing point scheduled by each DCI is the same, a structure may be such that the counter (DAI) value corresponding to the DCI that schedules the PDSCH sent on the cell with a lower cell index is determined / signaled as a lower value. In addition, in the above description, if the start (or end) symbol timing point of the PDSCH with the latest start (or end) symbol timing point scheduled by each DCI is the same, the DCI that schedules the PDSCH sent on the cell with the highest cell index among the corresponding PDSCHs is determined as the last DCI, thereby determining the PUCCH resources based on the PRI indicated by the corresponding DCI.

[0211] iii. On the other hand, in the above description, in the case of a plurality of cells scheduled by or with a multi-cell DCI, they may be regarded / applied as corresponding to the remaining portion of the plurality of cells except for the invalid cell.

[0212] 3) Proposal 2-2

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

[0214] A. If spatial (domain) A / N bundling between (two) TBs transmitted on the same PDSCH is configured (or if only a single TB transmission is available for all multi-cell DCI scheduling target cells), the number of A / N bits corresponding to one DAI for the multi-cell case (and / or multi-cell DCI) can be determined based on the maximum number of cells that can be simultaneously scheduled through a single multi-cell DCI (for convenience, referred to as the "DAI A / N size for the multi-cell case"). If spatial bundling is not configured, it can be determined based on the maximum number of TBs that can be simultaneously scheduled through a single multi-cell DCI (taking into account all simultaneously schedulable cell combinations and the maximum (transmittable) number of TBs configured for each cell) (similarly, for each simultaneously schedulable cell combination, the sum of the maximum TBs set for each cell within the corresponding cell combination is calculated, and the maximum value is selected from the sum of the maximum number of TBs per cell combination) (for convenience, this process is referred to as the "multi-cell DAI A / N size" calculation / decision process).

[0215] i. In addition, in the case of a multi-cell DAI A / N size, the calculation / determination may be performed while excluding / excluding invalid cells (e.g., cells corresponding to case 5 / 6 / 7 / 8 / 9). In other words, the multi-cell DAI A / N size may be calculated / determined based only on the remaining cells other than the invalid cells (e.g., case 5 / 6 / 7 / 8 / 9) (e.g., assuming that the respective cell combinations that can be scheduled simultaneously include the remaining cells other than the invalid cells (e.g., case 5 / 6 / 7 / 8 / 9)). For example, referring to Fig.11 , if the number of TBs (or CWs) per PDSCH is set to 1 for all cells that can be scheduled by multi-cell DCI [A05], or if spatial A / N bundling between TBs is configured for cells despite including cells with a number of TBs per PDSCH of 2 [A10], the DAI A / N size may be determined based on the maximum number of cells that can be scheduled by one multi-cell DCI. For example, referring to Fig.12, assuming that M co-scheduled cell combinations are configured for the UE and the multi-cell DCI performs multi-cell scheduling through one of the M co-scheduled cell combinations, the maximum number of cells that can be co-scheduled through one multi-cell DCI may be Max{1st value, 2nd value, 3rd value, ...., Mth value}. For example, assuming that Max{1st value, 2nd value, 3rd value, ...., Mth value} = X, the DAI A / N size may be X bits. For example, if X bits are allocated to each Counter DAI value and a HARQ-ACK codebook (e.g., a type 2 HARQ-ACK codebook) is configured for a total of C1 Counter DAI values, the HARQ-ACK codebook may include C1*XA / N bits. This may mean that if the number of TBs (or CWs) per PDSCH is set to 1 for all cells that can be scheduled via multi-cell DCI [A05, yes], or if spatial A / N bundling between TBs is configured for the cells despite including the corresponding cell with a number of TBs per PDSCH of 2 [A10, yes], then for 1DCI, 1A / N bit is allocated per scheduled cell.

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

[0217] B. On the other hand, if only one DCI (corresponding to the multi-cell case) is scheduled / received indicating the corresponding (sub) time slot for a specific A / N feedback transmission (sub) time slot as the A / N transmission timing (for example, if only one DCI in which both the counter-DAI and total-DAI values ​​are indicated as 1 is received), the number of A / N bits corresponding to the multi-cell case may be determined to be equal to the number of PDSCHs scheduled / indicated by the corresponding DCI (if spatial bundling is configured or only a single TB transmission is configured for all multi-cell DCI scheduling target cells) or the number of TBs scheduled / indicated by the corresponding DCI (if spatial bundling is configured).

[0218] i. On the other hand, even in this case, the number of A / N bits corresponding to the multi-cell case may be determined based on only the remaining cells excluding the invalid cell among the cells scheduled / indicated by the DCI.

[0219] 4) Proposal 2-3

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

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

[0222] - Option 3-1: Independent DAI counting may be performed between a multi-cell case and a CBG-PDSCH case (or a multi-PDSCH case), and a separate subcodebook may be configured for each. In this case, an operation may be performed to configure the entire codebook by cascading in a manner such that subcodebook #2 corresponding to the CBG-PDCCH case (or a multi-PDSCH case) is appended to subcodebook #1 corresponding to the multi-cell case (while appending subcodebook #1 corresponding to the multi-cell case to subcodebook #0 corresponding to the single-cell case) (or conversely, in a manner such that subcodebook #1 is appended to subcodebook #2 (while appending subcodebook #2 to subcodebook #0)).

[0223] 1. In this case, while three UL DAI fields indicating total-DAI information / values ​​of three sub-codebooks are configured in the UL DCI, or only two UL DAI fields are configured, the first UL DAI field may indicate total-DAI information / value of sub-codebook #0, and the second UL DAI field may indicate total-DAI information / value commonly applied to sub-codebooks #1 and #2.

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

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

[0226] D. On the other hand, when PDSCH resource #1 on a specific cell indicated by a multi-cell DCI and PDSCH resource #2 indicated by a multi-PDSCH DCI for scheduling the corresponding specific cell overlap with each other in time, the UE may perform a PDSCH reception operation in a state regarding / assuming that PDSCH resource #1 based on the multi-cell DCI is invalid and only PDSCH resource #2 based on the multi-PDSCH DCI is valid (or conversely, in a state regarding / assuming that PDSCH resource #2 is invalid and only PDSCH resource #1 is valid).

[0227] i. In addition, when PUSCH resources #1 on a specific cell indicated by a multi-cell DCI and PUSCH resources #2 indicated by scheduling a multi-PUSCH DCI corresponding to the specific cell overlap with each other in time, the UE can perform a PUSCH transmission operation in a state regarding / assuming that PUSCH resources #1 based on the multi-cell DCI are invalid and only PUSCH resources #2 based on the multi-PUSCH DCI are valid (or conversely, in a state regarding / assuming that PUSCH resources #2 are invalid and only PUSCH resources #1 are valid).

[0228] 5) Proposal 2-4

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

[0230] -Option 4-1: The A / N bits corresponding to the TBs scheduled by DCI (or the TBs actually received by the UE among them (on the remaining cells except the invalid cell)) can be mapped sequentially in the order of first TB index-then cell index (starting with the first bit in the A / N payload) (after mapping, the remaining bits (in the A / N payload) can be mapped to NACK). The order can mean ascending or descending. For example, the UE first maps the A / N bits in the TB index order of all scheduled TBs of the cell with the lowest cell index (e.g., TB index ascending order). When the A / N bit mapping of all TB indexes of the corresponding cell is completed, the UE can first map the A / N bits in the TB index order of the scheduled TB of the cell with the second lowest cell index.

[0231] 1. If spatial bundling is configured (or only single TB transmission is configured to be available for all multi-cell DCI scheduling target cells), the A / N bits corresponding to the PDSCH scheduled by DCI (or the PDSCH actually received by the UE on the remaining cells (except the invalid cell)) can be mapped in sequence according to the order of cell indexes. For example, Fig.13 It is assumed that cell A with cell index 1, cell B with cell index 3, and cell C with cell index 5 are co-scheduled by DCI, a maximum of 2-TB is configured for each of cell A and cell B, a maximum of 1-TB is configured for cell C, and spatial bundling is configured only for cell B. In addition, it is assumed that the number of TBs actually scheduled by DCI for cell A, cell B, and cell C is 1-TB, 2-TB, and 1-TB, respectively. (In addition, for the convenience of description, the DAI A / N size of the multi-cell case described in Proposal 2-2 is assumed to be 5 bits.) Fig.13 (a) of FIG. 1 shows an example of Option 1. Fig.13 (a), first map the A / N bits of TB1 of cell A with the lowest cell index. Since TB2 of cell A is not scheduled, the A / N bits of TBs of cell B are mapped next. Since spatial bundling is configured on cell B, the A / N bits of TB1 and the A / N bits of TB2 can be bundled into one A / N bit (e.g., AND operation). Next, map the A / N bits of TB1 of cell C.

[0232] 2. In the above description, when A / N bits corresponding to a TB scheduled with DCI or a scheduled PDSCH are mapped in the order of TB / cell index or cell index, A / N bits corresponding to an invalid cell may be mapped to NACK.

[0233] - Option 4-2: The A / N bits corresponding to the PDSCH (cell) scheduled by DCI (or (among them) the PDSCH (cell) actually received by the UE (on the remaining cells except the invalid cell)) can be mapped in sequence according to the maximum number of TBs configured in each cell in the order of the cell index (starting with the first bit in the A / N payload) (after mapping, the remaining bits (in the A / N payload) can be mapped to NACK). The order can mean ascending or descending.

[0234] 1. If spatial bundling is configured (or only single TB transmission is configured to be available for all multi-cell DCI scheduling target cells), the A / N bits corresponding to the PDSCH scheduled by DCI (or the PDSCH actually received by the UE among them (on the remaining cells except the invalid cells)) can be mapped sequentially according to the order of cell indexes. Fig.13 (b) may be an example of option 2. Fig.13 (b), first map the A / N bits of TB1 of cell A with the lowest cell index. Since the maximum number of TBs configured on cell A is 2, the A / N bits of TB2 can be mapped even if TB2 of cell A is not actually scheduled. The A / N bits of TB2 can be set to NACK / DTX. Next, map the A / N bits of the TBs of cell B. Although the maximum number of TBs configured on cell B is 2, since spatial bundling is configured on cell B, the A / N bits of TB1 and TB2 can be bundled (for example, ANDed) into one A / N bit. Next, the A / N bits of TB1 of cell C can be mapped.

[0235] 2. In the above description, when A / N bits corresponding to PDSCH (cell) scheduled with DCI are mapped in the order of TB / cell index, A / N bits corresponding to invalid cells may be mapped to NACK.

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

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

[0238] [3] Multi-cell PDSCH scheduling operation and (enhanced) Type 3A / N codebook configuration

[0239] 1) Existing operations

[0240] A. In the case of the existing enhanced type 3 codebook (i.e., e-Type-3 CB), while multiple candidate e-Type-3 CBs (indexes) consisting of different cell subsets and / or (per cell) HPN (HARQ process number / index / ID) subsets are pre-configured through RRC, one e-Type-3 CB index among them can be indicated through DCI. The UE operates to configure A / N feedback for the cell / HPN subset configured in the indicated corresponding e-Type-3 CB index (corresponding to the PDSCH reception), and sends it through the A / N transmission timing point indicated by the same DCI.

[0241] 2) Proposed Operation

[0242] A. When a specific e-Type-3 CB index is indicated by the above-mentioned multi-cell DCI, if the cells / HPNs scheduled by DCI (PDSCH transmission) include cells / HPNs that do not belong to the cell / HPN subset configured in the corresponding specific e-Type-3 CB index (for convenience, referred to as "additional cells / HPNs"), the UE may operate as follows.

[0243] i. Alternative 1: With respect to the absence of PDSCH transmission / scheduling for additional cells / HPNs, the UE may perform PDSCH reception and corresponding A / N feedback configuration / transmission operations (except for the appropriate additional cells / HPNs).

[0244] ii. Alternative 2: The UE is operable to perform PDSCH reception under the assumption that PDSCH is also transmitted / scheduled for extreme cells / HPNs, and configure and transmit A / N feedback corresponding to both the cell / HPN subset configured in the indicated e-Type-3 CB index and the corresponding additional cells / HPNs.

[0245] iii. Alternative 3: The UE is operable to configure / send A / N feedback only for the subset of cells / HPNs configured in the indicated e-Type-3 CB index (except the corresponding additional cells / HPNs) while performing PDSCH reception under the assumption that PDSCH is also sent / scheduled for the additional cells / HPNs.

[0246] B. In the case of the proposed operation, a specific e-Type-3 CB index is indicated by a multi-PDSCH DCI, and the same operating principle can be applied even if (additional) HPNs that fail to belong to the HPN subset configured in the corresponding specific e-Type-3 CB index are included among the HPNs scheduled by DCI (for PDSCH transmission).

[0247] Fig.14 An example of implementation of signal reception of a UE based on at least some of the above-mentioned embodiments is shown. Even if there is no separate description, for better understanding Fig.14 See also the above.

[0248] Reference Fig.14 , the UE may receive the configuration of the TDRA entry (B05). The UE may receive the configuration of multiple first TDRA entries for each cell for separate scheduling of each cell. The UE may receive the configuration of multiple second TDRA entries, each second TDRA entry including TDRA information of multiple cells for multi-cell scheduling. According to an embodiment, the configuration of the first TDRA entry and the configuration of the second TDRA entry may be received via separate signaling or received together.

[0249] The UE may receive downlink control information (DCI) for multi-cell scheduling through a physical downlink control channel (PDCCH) ( B10 ).

[0250] The DCI for multi-cell scheduling may provide a TDRA field for all one or more cells scheduled together. The value of this TDRA field may be related to one of the multiple second TDRA entries. The TDRA information of the multiple cells included in each of the multiple second TDRA entries may be configured based on the multiple first TDRA entries configured for the separate scheduling of each cell.

[0251] Each second TDRA entry may be associated with a plurality of TDRA parameter sets including a first TDRA parameter set for a first cell and a second TDRA parameter set for a second cell. The first TDRA parameter set may belong to a first TDRA entry configured for the first cell, and the second TDRA parameter set may belong to a first TDRA entry configured for the second cell. Each parameter set may include a combination of {K0, mapping_type, SLIV} parameters. "K0" may be a time slot offset from the PDCCH to the scheduling signal, "mapping_type" may be a resource mapping type of the scheduling signal, and "SLIV" may be information about the starting symbol and length of the scheduling signal.

[0252] Each second TDRA entry may be related to a combination of N first TDRA entries for N cells.

[0253] The TDRA information of the first cell and the TDRA information of the second cell included in each second TDRA entry may be one of the first TDRA entries of the first cell and one of the first TDRA entries of the second cell, respectively.

[0254] The UE may transmit or receive a signal on one or more cells scheduled together through DCI for multi-cell scheduling.

[0255] The configuration of the first TDRA entry and the configuration of the second TDRA entry may be received through higher layer signaling, respectively.

[0256] The plurality of first TDRA entries configured for each of the plurality of cells may be associated with N first TDRA tables for the N cells. The plurality of second TDRA entries may be associated with one second TDRA table configured for the N cells.

[0257] Fig.15 An example of implementation of signal transmission of a base station based on at least some of the above-mentioned embodiments is shown. Even if there is no separate description, for better understanding Fig.15 , you can also refer to the above content.

[0258] Reference Fig.15 , the base station may send a configuration of a TDRA entry (C05). The base station may send a configuration of multiple first TDRA entries for each cell for separate scheduling of each cell. The base station may send a configuration of multiple second TDRA entries including TDRA information for multiple cells respectively used for multi-cell scheduling. According to an embodiment, the configuration of the first TDRA entry and the configuration of the second TDRA entry may be sent through separate signaling or may be sent together.

[0259] The base station may transmit downlink control information (DCI) for multi-cell scheduling through a physical downlink control channel (PDCCH) (C10).

[0260] The DCI for multi-cell scheduling may provide one TDRA field for all one or more cells scheduled together. The value of this one TDRA field may be related to one of the multiple second TDRA entries. The TDRA information of the multiple cells included in each of the multiple second TDRA entries may be configured based on multiple first TDRA entries configured for separate scheduling of each cell.

[0261] Each second TDRA entry may be associated with a plurality of TDRA parameter sets including a first TDRA parameter set for a first cell and a second TDRA parameter set for a second cell. The first TDRA parameter set may belong to a first TDRA entry configured for the first cell, and the second TDRA parameter set may belong to a first TDRA entry configured for the second cell. Each parameter set may include a combination of {K0, mapping_type, SLIV} parameters. "K0" may be a time slot offset from the PDCCH to the scheduling signal, "mapping_type" may be a resource mapping type of the scheduling signal, and "SLIV" may be information about the starting symbol and length of the scheduling signal.

[0262] Each second TDRA entry may be related to a combination of N first TDRA entries for N cells.

[0263] The TDRA information of the first cell and the TDRA information of the second cell included in each second TDRA entry may be one of the first TDRA entries of the first cell and one of the first TDRA entries of the second cell, respectively.

[0264] The base station may transmit or receive a signal on one or more cells scheduled together through DCI for multi-cell scheduling.

[0265] The configuration of the first TDRA entry and the configuration of the second TDRA entry may be sent through higher layer signaling, respectively.

[0266] The plurality of first TDRA entries configured for each of the plurality of cells may be associated with N first TDRA tables for the N cells. The plurality of second TDRA entries may be associated with one second TDRA table configured for the N cells.

[0267] Fig.16 1 is a diagram showing a method of transmitting and receiving a signal in a network system according to an embodiment. Fig.16 , you can also refer to the above content.

[0268] Reference Fig.16 , the UE may receive information from the network through high-layer signaling (D05). The information received through high-layer signaling may include at least one of the configuration of multiple first TDRA entries for each cell for separate scheduling of each cell and the configuration of multiple second TDRA entries including TDRA information of multiple cells for multi-cell scheduling. According to an embodiment, the configuration of the first TDRA entry and the configuration of the second TDRA entry may be received through separate signaling or received together.

[0269] The UE may receive downlink control information (DCI) for multi-cell scheduling from the network through a physical downlink control channel (PDCCH) (D10).

[0270] The UE may receive a PDSCH from the network on one or more cells scheduled together through DCI (D15).

[0271] The UE may send a HARQ-ACK for the received PDSCH to the network (D20).

[0272] The DCI for multi-cell scheduling may provide a TDRA field for all one or more cells scheduled together. The value of this TDRA field may be related to one of the multiple second TDRA entries. The TDRA information of the multiple cells included in each of the multiple second TDRA entries may be configured based on the multiple first TDRA entries configured for the separate scheduling of each cell.

[0273] Each second TDRA entry may be associated with a plurality of TDRA parameter sets including a first TDRA parameter set for a first cell and a second TDRA parameter set for a second cell. The first TDRA parameter set may belong to a first TDRA entry configured for the first cell, and the second TDRA parameter set may belong to a first TDRA entry configured for the second cell. Each parameter set may include a combination of {K0, mapping_type, SLIV} parameters. "K0" may be a time slot offset from the PDCCH to the scheduling signal, "mapping_type" may be a resource mapping type of the scheduling signal, and "SLIV" may be information about the starting symbol and length of the scheduling signal.

[0274] Each second TDRA entry may be related to a combination of N first TDRA entries for N cells.

[0275] The TDRA information of the first cell and the TDRA information of the second cell included in each second TDRA entry may be one of the first TDRA entries of the first cell and one of the first TDRA entries of the second cell, respectively.

[0276] The plurality of first TDRA entries configured for each of the plurality of cells may be associated with N first TDRA tables for the N cells. The plurality of second TDRA entries may be associated with one second TDRA table configured for the N cells.

[0277] Fig.17 A communication system 1 applied to the present disclosure is shown.

[0278] Reference Fig.17 , 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.

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

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

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

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

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

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

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

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

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

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

[0289] Fig.19 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.17 ) are implemented in various forms.

[0290] Reference Fig.19 , the wireless devices 100 and 200 may correspond to Fig.18The 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.18 One or more processors 102 and 202 and / or one or more memories 104 and 204. For example, the transceiver 114 may include Fig.18 The control unit 120 is electrically connected to the communication unit 110, the memory unit 130, and the additional components 140, and controls the overall operation of the wireless device. For example, the control unit 120 may control the electrical / mechanical operation of the wireless device based on the program / code / command / information stored in the memory unit 130. The control unit 120 may transmit information stored in the memory unit 130 to the outside (e.g., other communication devices) via the communication unit 110 through a wireless / wired interface, or store information received from the outside (e.g., other communication devices) via the communication unit 110 in the memory unit 130 through a wireless / wired interface.

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

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

[0293] Fig. 20 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.

[0294] Reference Fig. 20 , 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.19 Block 110 / 130 / 140.

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

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

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

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

[0299] Reference Fig.21 , 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.

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

[0301] [Table 7]

[0302]

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

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

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

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

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

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

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

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

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

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

[0313] Industrial Applicability

[0314] 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 a configuration of a plurality of first time domain resource allocation TDRA entries for each cell for separate scheduling of each cell; receiving a configuration of a plurality of second time domain resource allocation TDRA entries, each second TDRA entry including TDRA information of a plurality of cells for multi-cell scheduling; and receiving downlink control information DCI for the multi-cell scheduling through a physical downlink control channel PDCCH, The DCI for the multi-cell scheduling provides a TDRA field for all one or more cells scheduled together, wherein the value of the one TDRA field is related to one of the plurality of second TDRA entries, and The TDRA information of the multiple cells included in each of the multiple second TDRA entries is configured based on the multiple first TDRA entries configured for individual scheduling of each cell.

2. The method according to claim 1, wherein: Each of the second TDRA entries is associated with a plurality of TDRA parameter sets including a first TDRA parameter set for a first cell and a second TDRA parameter set for a second cell, and The first TDRA parameter set belongs to the first TDRA entry configured for the first cell, and the second TDRA parameter set belongs to the first TDRA entry configured for the second cell.

3. The method according to claim 2, wherein: Each parameter set includes a combination of {K0, mapping_type, SLIV} parameters, wherein "K0" indicates a slot offset from the PDCCH to a scheduling signal, wherein "mapping_type" indicates a resource mapping type of the scheduling signal, and wherein "SLIV" indicates a starting symbol and length information of the scheduling signal.

4. The method according to claim 1, wherein: Each of the second TDRA entries is related to a combination of N first TDRA entries for N cells.

5. The method according to claim 1, wherein: The TDRA information of the first cell and the TDRA information of the second cell included in each of the second TDRA entries are respectively one of the first TDRA entries of the first cell and one of the first TDRA entries of the second cell.

6. The method according to claim 1, further comprising the steps of: A signal is transmitted or received on the one or more cells scheduled together through the DCI for the multi-cell scheduling.

7. The method according to claim 1, wherein: The configuration of the first TDRA entry and the configuration of the second TDRA entry are respectively received through high-layer signaling.

8. The method according to claim 1, wherein: The plurality of first TDRA entries configured for each of the plurality of cells are associated with N first TDRA tables for N cells, and The multiple second TDRA entries are related to a single second TDRA table configured for the N cells. 9 . A computer-readable recording medium storing a program for executing the method according to claim 1 .

10. An apparatus for wireless communication, the apparatus comprising: a memory configured to store instructions; as well as A processor configured to perform operations based on executing the instructions, the operations comprising: receiving a configuration of a plurality of first time domain resource allocation TDRA entries for each cell for separate scheduling of each cell; receiving a configuration of a plurality of second time domain resource allocation TDRA entries, each second TDRA entry including TDRA information of a plurality of cells for multi-cell scheduling; and receiving downlink control information DCI for the multi-cell scheduling through a physical downlink control channel PDCCH, The DCI for the multi-cell scheduling provides a TDRA field for all one or more cells scheduled together, wherein the value of the one TDRA field is related to one of the plurality of second TDRA entries, and The TDRA information of the multiple cells included in each of the multiple second TDRA entries is configured based on the multiple first TDRA entries configured for individual scheduling of each cell.

11. The device according to claim 10, further comprising: A transceiver is configured to send or receive radio signals under the control of the processor.

12. The device according to claim 10, wherein: The device is a user equipment UE in a wireless communication system.

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

14. A method for sending a signal by a base station in a wireless communication system, the method comprising the following steps: Sending configuration of multiple first time domain resource allocation TDRA entries for each cell for separate scheduling of each cell; Sending configuration of multiple second time domain resource allocation TDRA entries, each second TDRA entry including TDRA information of multiple cells for multi-cell scheduling; and The physical downlink control channel PDCCH is used to send downlink control information DCI for multi-cell scheduling. wherein the DCI for the multi-cell scheduling provides a single TDRA field for all one or more cells scheduled together, wherein the value of the single TDRA field is associated with one of the plurality of second TDRA entries, and The TDRA information of the multiple cells included in each of the multiple second TDRA entries is configured based on the multiple first TDRA entries configured for individual scheduling of each cell.

15. A base station for sending a signal in a wireless communication system, the base station comprising: Transceiver; as well as a processor configured to control the transceiver to: send a configuration of a plurality of first time domain resource allocation TDRA entries for each cell for separate scheduling of each cell, send a configuration of a plurality of second time domain resource allocation TDRA entries, each second TDRA entry includes TDRA information of a plurality of cells for multi-cell scheduling, and send downlink control information DCI for multi-cell scheduling through a physical downlink control channel PDCCH, wherein the DCI for the multi-cell scheduling provides a single TDRA field for all one or more cells scheduled together, wherein the value of the single TDRA field is associated with one of the plurality of second TDRA entries, and The TDRA information of the multiple cells included in each of the multiple second TDRA entries is configured based on the multiple first TDRA entries configured for individual scheduling of each cell.

Images