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

Abstract

A method by which a user equipment (UE) receives a signal in a wireless communication system according to an embodiment may comprise the steps of: monitoring a physical downlink control channel (PDCCH); and detecting downlink control information (DCI) for multi-cell scheduling based on the monitoring of the PDCCH, where the DCI may include a first bit field providing code points for one or all of two or more cells scheduled together by the DCI at a time, and a second bit field providing code points for one or all of the two or more cells scheduled together by the DCI at a time. The size 'M' of the first bit field may be determined based on a first cell in which the total number of code points set with respect to the first bit field is the largest, and for a second cell related to a field size 'K' smaller than the size 'M' of the first bit field, the number of code points set with respect to the first bit field is smaller than the number of code points set with respect to the second cell. The code point provided by the first bit field may be determined based on a remaining bit value excluding at least one bit from the first bit field.

Description

Technical Field

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

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

[0003] Technical issues

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

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

[0006] Technical Solution

[0007] In one aspect, a method for receiving a signal by a user equipment (UE) in a wireless communication system may include the following steps: monitoring a physical downlink control channel (PDCCH); and based on the monitoring of the PDCCH, detecting downlink control information (DCI) for multi-cell scheduling. The DCI may include a single first bit field that provides code points for all one or more cells co-scheduled by the DCI at one time. The size "M" of the first bit field may be determined based on the first cell for which the total number of code points configured with respect to the first bit field is the maximum number. For a second cell associated with a field size "K" that is smaller than the size "M" of the first bit field, the code point provided by the first bit field may be determined based on the value of the remaining bits excluding at least one bit from the first bit field.

[0008] The code point of the first bit field for the second cell may be determined based on the first 'K' bits or the last 'K' bits of the first bit field.

[0009] Based on the fact that a code point for the second cell determined based on the value of the remaining bits except for the at least one bit is not configured for the second cell, a specific code point configured for the second cell may be applied. The specific code point may be a code point with a highest value or a lowest value among the code points configured in the second cell.

[0010] Based on the fact that the code point for the second cell determined based on the values ​​of the remaining bits except for the at least one bit is not configured for the second cell, the UE may assume that the second cell is not scheduled through the DCI.

[0011] Based on the fact that the codepoint for the second cell determined based on the values ​​of the remaining bits except for the at least one bit is not configured for the second cell, the UE may maintain the most recently indicated codepoint for the second cell.

[0012] A set of code points related to the first bit field may be configured for each cell. The set of code points configured for each cell may be based on a set of code points configured for individual scheduling of each cell.

[0013] The first bit field may be a bandwidth part (BWP) indication field, an open loop power control (OLPC) field, a physical uplink shared channel (PUSCH) related listen-before-talk (LBT) field, or a beta offset indication field.

[0014] The UE may send or receive a signal on one or more co-scheduled cells based on the DCI.

[0015] In another aspect, a processor-readable recording medium having recorded thereon a program for executing the above-described signal receiving method may be provided.

[0016] In another aspect, a terminal for executing the above-mentioned signal receiving method may be provided.

[0017] In another aspect, an apparatus for controlling a UE for performing the above-mentioned signal receiving method may be provided.

[0018] On the other hand, a method for sending a signal by a base station in a wireless communication system may include the following steps: generating downlink control information (DCI) for multi-cell scheduling; and sending the DCI to a UE through a physical downlink control channel (PDCCH). The DCI may include a single first bit field that provides code points for all one or more cells co-scheduled by the DCI at one time. The size "M" of the first bit field may be determined based on the first cell of the UE with the largest total number of code points configured with respect to the first bit field. For a second cell of a UE associated with a field size "K" that is smaller than the size "M" of the first bit field, the code point of the first bit field may be provided based on the value of the remaining bits excluding at least one bit from the first bit field.

[0019] In another aspect, a base station for executing the above method may be provided.

[0020] Beneficial Effects

[0021] According to at least one of various embodiments, a wireless signal transmission / reception process can be efficiently performed in a wireless communication system.

[0022] Those skilled in the art will understand that the technical effects that can be achieved using the present disclosure are not limited to those specifically described above, and the above and other technical effects that can be achieved by the present disclosure will be more clearly understood from the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0024] Figure 2 Shows the radio frame structure.

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

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

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

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

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

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

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

[0032] Fig.10 is a diagram showing a specific type of field in a multi-cell scheduling DCI according to one embodiment.

[0033] Fig.11 is a diagram illustrating transmission of an enhanced type-3 codebook according to one embodiment.

[0034] Fig.12 is a diagram illustrating retransmission of a HARQ-ACK codebook according to one embodiment.

[0035] Fig.13 is a diagram illustrating a method for receiving a signal by a UE according to one embodiment.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0052] [Table 1]

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

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

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

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

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

[0058] [Table 2]

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

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

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

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

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

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

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

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

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

[0068] -controlResourceSetId: CORESET related to SS

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

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

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

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

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

[0074] [Table 3]

[0075]

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

[0077] [Table 4]

[0078]

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

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

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

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

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

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

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

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

[0087] [Table 5]

[0088]

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0107] Depending on how the HARQ-ACK bits (payload) are configured, the HARQ-ACK codebooks are defined as type 1, type 2, and type 3 codebook types. For the type 1 codebook, the HARQ-ACK payload is configured according to a combination of a candidate HARQ-ACK timing (K1) set and a candidate PDSCH opportunity (SLIV) set (configured for each cell) (e.g., a codebook whose size is semi-statically fixed based on RRC signaling). For 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 number of corresponding resource allocations. For the type 3 codebook, the HARQ-ACK payload (e.g., a one-time A / N report) is configured by mapping the HARQ-ACK bits corresponding to each HARQ process number (HPN) to the corresponding HPN according to the maximum number of HARQ processes (set for each cell). Recently, the NR standard added an enhanced type 3 codebook as a type 3 codebook. The enhanced type 3 codebook is intended to report the HARQ-ACK bits of a subset of cells indicated to the BS among all cells, rather than reporting the HARQ-ACK bits of all cells at once, in order to reduce signaling overhead. Through high-layer signaling of the enhanced type 3 codebook index, a cell subset related to the enhanced type 3 codebook can be configured for the UE, and then one of the configured subsets (e.g., an enhanced type 3 codebook index) can be indicated to the UE by triggering the DCI of the enhanced type 3 codebook. The UE can report the HARQ-ACK of the cell belonging to the indicated subset. According to the configuration of the enhanced type 3 codebook index, the enhanced type 3 codebook can be configured not only at the per-cell level but also at the per-HARQ process level. For example, the enhanced type 3 codebook index can be configured on a per-HARQ process basis to support reporting of the type 3 codebook for a portion of the HARQ processes in the cell.

[0108] Specifically, for the type 1 codebook, a set of multiple (e.g., N) candidate values ​​of K1 (for the corresponding cell among the cells) may be configured. For each value of K1, a combination of all SLIVs that can be transmitted (or scheduled to be transmitted) in the DL time slot K1 time slot before the A / N transmission time slot may be calculated, and the A / N sub-payload corresponding to the DL time slot may be configured (including determining the A / N bit position / sequence corresponding to each transmittable SLIV in the time slot) (defined as "SLIV pruning"). These A / N sub-payloads may be cascaded for N values ​​of K1 to configure a complete A / N codebook, wherein the set of (N) DL time slots corresponding to each value of K1 may be defined as a bundling window corresponding to the A / N transmission time slot.

[0109] For the type 2 HARQ-ACK codebook, the codebook for sending HARQ-ACK information on the same PUCCH / PUSCH is defined based on the values ​​of the counter downlink assignment indicator (DAI) (C-DAI) and the total DAI (T-DAI) indicated in the PDCCH actually sent. In other words, the codebook is configured based on the PDCCH information actually sent to the UE. In the event that the UE fails to detect a specific PDCCH, NACK is sent through the bit used for PDCCH among the bits defined in the codebook. At this time, the UE can identify the state of PDCCH detection failure based on the values ​​of C-DAI and T-DAI. C-DAI is the cumulative number of {serving cell index, PDCCH monitoring opportunity} pairs that provide PDSCH reception, counting to 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 that starts receiving is counted first (assigned a lower C-DAI value). 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.

[0110] Specifically, for the type 3 codebook, the BS may configure one of two modes for the UE: mode 1, in which HARQ-ACK and the corresponding NDI are fed back together; and mode 2, in which only HARQ-ACK is fed back without NDI. When set in mode 1, the UE shall operate to feed back HARQ-ACK and the corresponding NDI (indicated by DCI) received by the PDSCH corresponding to one HARQ process number (HPN) together. On the other hand, when set in mode 2, the UE shall only feed back HARQ-ACK received by the PDSCH corresponding to one HPN.

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

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

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

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

[0115] Carrier Aggregation

[0116] NR can support wider UL / DL bandwidth by aggregating multiple UL and DL carriers (i.e., carrier aggregation). Carrier aggregation allows signals to be sent / received on multiple carriers. 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 to each other in the frequency domain. The bandwidth of each CC may be determined independently. Asymmetric carrier aggregation in which the number of ULCCs is different from the number of DLCCs may also be performed.

[0117] -Primary Cell (PCell): A cell operating at the primary frequency (e.g., primary component carrier (PCC)) where a UE configured with carrier aggregation 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 a UE performs an initial connection establishment procedure or initiates a connection re-establishment procedure.

[0118] - Secondary Cell (SCell): A cell that provides additional radio resources other than the special cell for UEs configured with carrier aggregation.

[0119] -Primary SCG cell (PSCell): A secondary cell group (SCG) cell to which the UE performs random access when performing RRC reconfiguration and synchronization procedures in case of DC.

[0120] - Special Cell (SpCell): In the case of DC, SpCell means PCell of MCG or PSCell of SCG. In the other case (ie, non-DC case), SpCell means PCell.

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

[0122] The control information may be configured to be sent / received only through the SpCell. For example, UCI may be sent only through the SpCell (e.g., PCell). When the SCell (hereinafter, PUCCH-SCell) that allows PUCCH transmission is configured, UCI may even be sent through the 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 the SpCell (e.g., PCell).

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

[0124] - CIF disabled: CIF does not exist in PDCCH. The PDCCH in the scheduling cell allocates PDSCH / PUSCH resources in the same cell. That is, the scheduling cell is the same as the scheduled cell.

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

[0126] Figure 7 shows carrier aggregation. Figure 7In the example, it is assumed that three cells are aggregated. When CIF is disabled, only the PDCCH (self-carrier scheduling (SCS)) that schedules PDSCH / PUSCH for each cell may be sent in each cell. On the other hand, when 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, the PDCCH that schedules the PDSCH / PUSCH in another cell (i.e., the scheduled cell) and the PDCCH that schedules the PDSCH / PUSCH of cell A may be sent in cell A (cross-carrier scheduling (CCS)). In this case, the PDCCH that schedules the PDSCH / PUSCH of cell B / C is sent in cell B / C.

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

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

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

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

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

[0132] - 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 9us sensing slot duration Tsl may be considered busy. CAP may be referred to as Listen Before Talk (LBT).

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

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

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

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

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

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

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

[0140] [Table 6]

[0141]

[0142] Multi-cell scheduling DCI

[0143] NR supports a wide range of spectrum in different frequency ranges. The availability of 5G Advanced spectrum is expected to increase through the reallocation of frequency bands used in previous generations. In particular, in the low-frequency band FR1, the available spectrum blocks tend to be further fragmented and distributed. For the FR2 band and part of the FR1 band, the available spectrum can be widened, which may require the operation of multiple in-band carriers / cells. There is a need to improve throughput and coverage by using these distributed spectrum bands or wider bandwidth spectrum in a more energy-efficient and flexible manner.

[0144] When scheduling data across multiple cells (including intra-band cells and inter-band cells), it is important to increase flexibility and spectrum / power efficiency. In the current 5G NR scheduling scheme, DCI may schedule PUSCH / PDSCH for only one cell. However, in the future, due to spectrum expansion / change, the demand for simultaneous scheduling of multiple cells is expected to increase. In order to reduce control overhead according to scheduling, it may be advantageous to perform PUSCH / PDSCH scheduling for multiple cells through one DCI.

[0145] Therefore, in order to reduce the DCI overhead of PDSCH / PUSCH scheduling in the case of carrier aggregation (CA) of multiple cells in the future, a multi-cell scheduling scheme that simultaneously schedules multiple (serving) cells / CCs (and PDSCH / PUSCH transmissions therethrough) with a single DCI can be considered in Rel-18.

[0146] Therefore, for the structural design of DCI (multi-cell DCI) for performing multi-cell scheduling as described above, a method for configuring and interpreting each field in DCI is proposed. In the present disclosure, the operation of multi-cell scheduling for PDSCH or PUSCH transmission is mainly described, but the operating principle of the proposed method can also be applied to multi-cell scheduling for PUSCH or PDSCH transmission. In addition, in the present disclosure, when a cell can refer to an active BWP configured / indicated for a cell.

[0147] Hereinafter, the multi-cell scheduling DCI may be referred to as multi-cell DCI or simply 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.

[0148] The reference cell described below can be determined based on at least one of i) to viii), and is not limited thereto: i) a cell with the lowest (or highest) cell index; ii) a cell with the earliest (or latest) PDSCH / PUSCH transmission start symbol time (if there are multiple cells with the earliest (or latest) PDSCH / PUSCH start symbol time, the cell with the lowest (or highest) cell index among these cells); iii) a cell with the earliest (or latest) PDSCH / PUSCH transmission end symbol time (if there are multiple cells with the earliest (or latest) PDSCH / PUSCH start symbol time, the cell with the lowest (or highest) cell index among these cells); iv) a cell indicated by the value of the CIF field or pre-specified by RRC in a cell combination (i.e., a co-scheduled cell set) (or each cell subgroup described below) co-scheduled by the same multi-cell DCI; or in any schedulable cell set via any multi-cell DCI, v) a cell with the lowest (or highest) cell index; vi) a cell indicated by the value of the CIF field; vii) a cell sending multi-cell DCI; and / or viii) a cell pre-specified by RRC.

[0149] For the fields applied to the shared reference cell method, shared cell common method and / or shared state extension method proposed in the present disclosure, i) only one field may be configured in the multi-cell DCI (i.e., a field commonly applied to all cells in the co-scheduled cell set), or ii) when all cells belonging to the entire co-scheduled cell set are grouped (configured) into one or more (multiple) cell subgroups, one field may be configured (commonly) applied to each cell subgroup (i.e., separate / independent fields are configured between cell subgroups), or iii) when all cells belonging to the schedulable cell set are grouped (configured) into one or more (multiple) cell subgroups, one field may be configured (commonly) applied to each cell subgroup (i.e., separate / independent fields are configured between cell subgroups) (in other words, the shared reference cell / shared cell common / shared state extension method and the corresponding field / information configuration / indication method based thereon may be applied to each cell subgroup). Each cell subgroup may be composed / configured of specific one or more cells belonging to the co-scheduled cell set or the schedulable cell set (e.g., some or all cells belonging to the co-scheduled cell set or the schedulable cell set).

[0150] In the conventional case (single-cell DCI-based scheduling), a table consisting of one or more (multiple) states / indexes (with different parameters / values ​​(combinations)) of each cell may be pre-configured through RRC or MAC-CE. In this state, the DCI field of the shared cell common method proposed in the present disclosure may be configured to indicate one of the (multiple) states / indexes in the table (for example, a PRB bundling size indicator and / or a rate matching (RM) indicator and / or a ZP CSI-RS trigger and / or an SRS request). In this case, the specific state / index indicated by the DCI field commonly configured for a set of cells (e.g., a co-scheduled cell set or a cell subgroup) to which the shared cell common method is applied may be operated as follows: Option X) may be interpreted / applied as a parameter / value (combination) corresponding to the state / index configured in the table for each cell in the cell set (i.e., individually for each cell), or Option Y) the parameter / value (combination) corresponding to the state / index configured in the table for a specific reference cell in the cell set may be commonly applied to the cells in the cell set, or Option Z) in the case where a separate (common) table to be commonly applied to the cell set is pre-configured through RRC / MAC-CE in the manner as described above, the parameter / value (combination) corresponding to the state / index in the common table may be commonly applied to the cells in the cell set.

[0151] In addition, some cells may not have a value set for a state / code point. For example, for the i-th state / code point, cell #2 may have a value x, but cell #1 and cell #N may not have any value set. Information (e.g., a table) containing cell values ​​for interpreting a shared cell common DCI field may be configured for each cell in the UE. For example, regarding the shared cell common DCI field, table 1 may be configured for cell #1, table 2 may be configured for cell #2, ..., and table N may be configured for cell #N.

[0152] For example, a cell-specific table configured for single cell (SC) scheduling can also be used for multi-cell (MC) scheduling. For example, when the SC table referenced by the SC DCI in the format used for SC is configured for each cell, the MC table referenced by the MC DCI can correspond to a combination of SC tables of multiple cells.

[0153] [Public T1A: Invalid state handling]

[0154] First, a more specific example of the shared cell common method (specifically, the method of option X) will be presented below.

[0155] In the existing single-cell DCI-based scheduling, for a specific DCI field (e.g., BWP indicator, open-loop power control parameter set indication (i.e., OLPC indicator), ChannelAccess-CPext-CAPC (for PUSCH) (i.e., PUSCH LBT), β offset indicator, PDCCH monitoring adaptation indication, etc.), each of the N states / code points / indexes that can be indicated by the DCI field can have N (different) parameters / values ​​(parameter / value combinations) pre-configured by RRC or MAC-CE. When one of the N states / code points / indexes is indicated by the DCI field, the UE can apply the parameter / value (combination) configured for the indicated state / code point / index to perform PDSCH / PUSCH transmission / reception. In this case, the size of the DCI field can be determined as ceil{log2(N)} bits, where N can be set to different values ​​(or the same value) for each cell.

[0156] For reference, in the present disclosure, ceil(X) means the smallest integer greater than or equal to X, and a value obtained by performing a modulo B operation on A means a remainder when A is divided by B.

[0157] In multi-cell DCI-based scheduling, for a specific DCI field, when a specific state / code point / index is indicated through a DCI field under the condition that parameters / values ​​(combinations) are pre-configured for each state / code point / index (applied in single-cell DCI-based scheduling), the UE may interpret and apply the parameters / values ​​(combinations) configured for each cell for the indicated state / code point / index to perform the scheduled PDSCH / PUSCH transmission and reception operations for each cell. For example, Fig.10 FIG. 4 shows the DCI fields in Option X according to the shared cell common method. Fig.10 In the example, for simplicity, it is assumed that the co-scheduled cell set includes four cells. Therefore, the actual number of co-scheduled cells may be four or less. Fig.10 The value indicated by one state (code point) of the DCI field in the DCI field may be interpreted / set independently for each cell. For example, when a first state / code point (e.g., 00) is indicated, the first state / code point may mean a value of a for cell #1, a value of b for cell #2, and a value of c for cell #3. Setting values ​​independently for each cell may include setting different values ​​for different cells, but is not limited thereto. The case where the same value is set for two or more cells is not excluded. In other words, values ​​may be set independently for the cells, and there may be no restriction that the values ​​must be the same or different.

[0158] In multi-cell DCI-based scheduling, the size of a specific DCI field may be determined as follows: Option A) based on the maximum value N_max, ceil{log2(N_max)} bits among the N values ​​set for each cell in the entire schedulable cell set (or each co-scheduled cell set) (in this case, the DCI field may be configured to indicate at most (the first) N_max states / code points / indexes); or Option B) based on the minimum value N_min, ceil{log2(N_min)} bits among the N values ​​(in this case, the DCI field may be configured to indicate at most (the first) N_min states / code points / indexes). For example, referring to Fig.10 , the number of states of cell #1 is the smallest (i.e., N_min), and the number of states of cell #4 is the largest (i.e., N_max). According to alternative A, for cell #4, the size of the DCI field is ceil{log2(N_max)=2 bits. According to alternative B), for cell #1, the size of the DCI field is ceil{log2(N_min)=1 bit.

[0159] When applying the method of Alternative A, some cells may not have a value set for a particular state / codepoint. Fig.10 , for the 3rd state in the table (DCI field value = 2), there is no value for cell #1 and cell #2. More generally, for a specific cell X (e.g., a cell where N is set to N_low less than N_max), when a state / index with a value greater than a specific state / index (e.g., a state / index with a value greater than the DCI field value {N_low-1}, i.e., a state / index after the N_low state / index) is indicated by a specific DCI field, there is no parameter / value (combination) configured for the specific state / index for cell X. Considering this situation, the following operation is proposed (for simplicity, M = ceil{log2(N_max)} and K = ceil{log2(N_low)} are defined (where M≥K)).

[0160] 1) Alternative 1: For cell X, only (selected) K bits among the M bits in the DCI field may be interpreted and applied. For example, the K bits may be the first K (MSB) bits or the last K (LSB) bits. For example, referring to Fig.10 , for cell #1 and cell #2, only one bit (MSB or LSB) of the two bits included in the DCI field may be selected and applied. When the binary value of the selected bit (MSB or LSB) is 0, value a may be applied to cell #1 and value b may be applied to cell #2.

[0161] A. The state / index corresponding to the field value greater than {N_low-1} may be indicated by K bits. In this case, the operation of alternative 3 or alternative 6 may be applied. For example, referring to Fig.10 , for cell #1 and cell #2, only one of the two bits included in the DCI field (MSB or LSB) may be selected and applied. When the binary value of the selected bit is 1, the value e may be applied to cell #2, but there is no value in the table to be applied to cell #1. To solve this problem, alternative 3 or alternative 6, which will be described later, may be applied.

[0162] B. In one example, for the BWP indicator field, when N_max is 4 and N_low is set to 2 for cell X (see, e.g., Fig.10 For cell #2 in the multi-cell DCI), the UE may interpret only the MSB 1 bit or the LSB 1 bit in the BWP indicator field (in the multi-cell DCI) and operate assuming the BWP index configured for the corresponding state.

[0163] C. In another example, for the OLPC indicator field, when N_max is 4 and N_low set for cell X is 2 (see, for example, Fig.10 For cell #2 in the multi-cell DCI), the UE may interpret only the MSB 1 bit or the LSB 1 bit in the OLPC indicator field (in the multi-cell DCI) and operate assuming the power control parameter set index configured for the corresponding state.

[0164] D. In another example, for the PUSCH LBT field, when N_max is 8 and N_low set for cell X is 4, the UE may interpret only the MSB 2 bits or LSB 2 bits in the PUSCH LBT field (in the multi-cell DCI) and operate assuming the LBT-related parameters / values ​​(combination) configured for the corresponding state.

[0165] 2) Alternative 2: When a state / index corresponding to a field value greater than {N_low-1} is indicated by a DCI field, a specific parameter / value (combination) pre-configured / pre-defined separately may be applied to cell X. For example, referring to Fig.10 , when a value greater than binary 00 is indicated by the DCI field, Alternative 2 may be applied to cell #1. When a value greater than binary 01 is indicated by the DCI field, Alternative 2 may also be applied to cell #2 (in addition to cell #1). When a value greater than binary 10 is indicated by the DCI field, Alternative 2 may also be applied to cell #3 (in addition to cell #1 and cell #2).

[0166] A. A specific parameter / value (combination) may be configured / defined as a parameter / value (combination) related to a specific one of the N_low states / indexes pre-configured for cell X (eg, the lowest or highest value).

[0167] B. In one example, in the case of the BWP indicator field, when N_low set for cell X is 2 and the state indicated by the BWP indicator field (in the multi-cell DCI) is higher than 1 (i.e., bit 01) (i.e., the state is bit 10 or 11 (not bit 00 or 01)), the UE may operate assuming that the BWP index configured for cell X is the lowest state 0 (or a specific state configured separately).

[0168] C. In another example, in the case of the OPLC indicator field, when N_low set for cell X is 2 and the state indicated by the OPLC indicator field (in the multi-cell DCI) is higher than 1 (i.e., bit 01), the UE may operate assuming that the power control parameter set index configured for the lowest state 0 (or a specific state configured separately) is indicated for cell X.

[0169] D. In another example, in the case of the PUSCH LBT indicator field, when N_low set for cell X is 4 and the state indicated by the PUSCH LBT indicator field (in the multi-cell DCI) is higher than 3 (i.e., bit 11), the UE may operate assuming the LBT-related parameters / values ​​(combination) configured as the lowest state 0 (or a specific state configured separately) for cell X.

[0170] 3) Alternative 3: When a state / index corresponding to a field value greater than {N_low-1} is indicated by the DCI field, the UE may consider that there is no PDSCH / PUSCH scheduling for cell X.

[0171] - For example, assume that Alternative 3 is applied alone (without applying Alternative 1). Fig.10 , when a value greater than binary 00 is indicated by the DCI field, alternative 3 may be applied for cell #1. When a value greater than binary 01 is indicated by the DCI field, alternative 3 may also be applied to cell #2 (in addition to cell #1).

[0172] - When Alternative 3 is applied in addition to Alternative 1 as described above, only one bit (MSB or LSB) of the two bits included in the DCI field may be first selected and applied for cell #1 according to Alternative 1. When the binary value of the selected one bit is 1, Alternative 3 may be applied to cell #1 because there is no value to be applied to cell #1 in the table.

[0173] - In case Alternative 3 is applied (regardless of whether Alternative 1 is applied), when a value greater than a binary value of 10 is indicated by the DCI field, Alternative 3 may be applied for cell #3.

[0174] A. According to the application of alternative 3, the UE may skip the PDSCH / PUSCH transmission / reception operation on cell X (and in the case of PDSCH, the corresponding HARQ-ACK may be fed back as NACK).

[0175] B. In one example, for the BWP indicator (or OLPC indicator) field, when N_low set for cell X is 2 and the state indicated by the BWP indicator (or OLPC indicator) field (in the multi-cell DCI) is higher than 1 (i.e., bit 01), the UE may operate assuming that there is no PDSCH / PUSCH scheduling for cell X.

[0176] 4) Alternative solution 4: The UE may additionally configure and apply {N_max-N_low}=N_gap parameters / values ​​(combinations) corresponding to states / indexes from N_low to N_max-1 for cell X. For example, referring to Fig.10 , cell #1 may be additionally configured with values ​​mapped to binary values ​​01, 10, and 11, cell #2 may be additionally configured with values ​​mapped to binary values ​​10 and 11, and cell #3 may be additionally configured with a value mapped to binary value 11.

[0177] A. Additional parameters / values ​​(combinations) may be configured as parameters / values ​​(combinations) related to N_gap specific states / indexes among the N_low states / indexes pre-configured for cell X.

[0178] B. In one example, for the BWP indicator field, when N_max is 4 and N_low set for cell X is 2, BWP indexes corresponding to two states (states 2 and 3) may be additionally configured and applied for cell X.

[0179] C. In another example, for the OLPC indicator field, when N_max is 4 and N_low set for cell X is 2, a power control parameter set index corresponding to two states (states 2 and 3) may be additionally configured and applied for cell X.

[0180] D. In another example, for the PUSCH LBT field, when N_max is 8 and N_low set for cell X is 4, LBT-related parameters / values ​​(combinations) corresponding to four states (states 4 to 7) may be additionally configured and applied for cell X.

[0181] 5) Alternative 5: For cell X, the UE may interpret and apply the state / index indicated by the DCI field as a value obtained by applying a modulo N_low operation. Fig.10 , the "modulo 1 (DCI field value)" operation can be applied to cell #1, the "modulo 2 (DCI field value)" operation can be applied to cell #2, and the "modulo 3 (DCI field value)" operation can be applied to cell #3.

[0182] A. For example, when N_low=5 and N_max=8, the states / indexes {0,1,2,3,4,5,6,7} indicated by the DCI field may be interpreted / applied as states / indexes {0,1,2,3,4,0,1,2} for cell X, respectively.

[0183] B. In one example, for the BWP indicator field, when N_max is 4 and N_low set for cell X is 2, the UE may interpret each of the four states 0 / 1 / 2 / 3 indicated by the DCI field as state 0 / 1 / 0 / 1 for cell X, and operate assuming the indication corresponds to the BWP index.

[0184] C. In another example, for the OLPC indicator field, when N_max is 4 and N_low set for cell X is 2, the UE may interpret each of the four states 0 / 1 / 2 / 3 indicated by the DCI field as state 0 / 1 / 0 / 1 for cell X, and operate assuming the corresponding power control parameter set index.

[0185] D. In another example, for the PUSCH LBT field, when N_max is 8 and N_low set for cell X is 4, the UE may interpret each of the eight states 0 / 1 / 2 / 3 / 4 / 5 / 6 / 7 indicated by the DCI field as state 0 / 1 / 2 / 3 / 0 / 1 / 2 / 3 for cell X, and operate assuming the corresponding LBT-related parameters / values ​​(combinations) indicated.

[0186] 6) Alternative 6: When a state / index corresponding to a field value greater than {N_low-1} is indicated by a DCI field, the UE may apply / maintain the most recently indicated state / index for cell X.

[0187] - For example, assume that alternative 6 is applied alone (without alternative 1). Fig.10, when a value greater than the binary value 00 is indicated by the DCI field of the currently received first DCI, the indication from the second DCI before the first DCI (the last DCI indicating a valid value (i.e., a field value less than or equal to {N_low-1} for cell #1)) may be applied / maintained for cell #1. When a value greater than the binary value 01 is indicated by the DCI field, alternative 6 may also be applied to cell #2 (in addition to cell #1).

[0188] - When Alternative 3 is applied in addition to Alternative 1 as described above, only one bit (MSB or LSB) of the two bits included in the DCI field may be first selected and applied for cell #1 according to Alternative 1. When the binary value of the selected one bit is 1, the indication from the second DCI before the first DCI (the last DCI indicating a valid value (i.e., a field value less than or equal to {N_low-1} for cell #1)) may be applied / maintained for cell #1 because there is no value to be applied to cell #1 in the table.

[0189] - In case of applying alternative 6 (regardless of whether alternative 1 is applied), a value greater than the binary value 10 may be indicated by the DCI field. In this case, the indication from the second DCI before the first DCI (the last DCI indicating a valid value (i.e., a field value less than or equal to {N_low-1} for cell #3)) may be applied / maintained for cell #3.

[0190] A. Therefore, the UE may apply / maintain the most recently indicated state / index for cell X to perform PDSCH / PUSCH transmission / reception operations on cell X.

[0191] B. For example, for the BWP indicator (or OLPC indicator) field, when N_low set for cell X is 2 and the state indicated by the BWP indicator (or OLPC indicator) field (in the multi-cell DCI) is higher than 1 (i.e., bit 01), the UE can operate so that the most recently indicated current active BWP index (or the most recently indicated power control parameter set index) is maintained / applied for cell X.

[0192] For the BWP indicator field, when the shared cell common method (method based on Option X) is applied, one of the states that can be indicated by the BWP indicator field in the multi-cell DCI can be set to "no BWP index switching" or "maintain current active BWP". When this state is indicated, the UE can operate to maintain the current active BWP without changing the BWP index on all cells scheduled by DCI. For the PUSCH LBT field, when the UE operates in load-based equipment (LBE) mode (and / or in frame-based equipment (FBE) mode where only the BS is allowed to initiate channel occupation time (COT), the shared cell common method (method of Option X) can be applied to perform field configuration in multi-cell DCI and indication operations based thereon. On the other hand, when the UE operates in FBE mode (or in FBE mode where the UE is also allowed to initiate COT), a separate method can be applied to perform field configuration in multi-cell DCI and indication operations based thereon.

[0193] [Public T2: Field size determination]

[0194] In addition, a specific example of a method of determining a DCI field size when the following separate methods are applied is disclosed below.

[0195] First, in the existing single-cell DCI, the size L of a specific DCI field (for example, a TPC command for a scheduled PUSCH (i.e., PUSCH TPC), a PDCCH monitoring adaptation indication, a minimum applicable scheduling offset indicator, a ChannelAccess-CPext-CAPC (for PUSCH), an invalid symbol pattern indicator, a β offset indicator, etc.) can be set to L=ceil{log2(N)} bits (when the DCI field is configured to indicate N states / code points / indexes), where L can be set to different values ​​(or the same value) for each cell.

[0196] The specific DCI field in the multi-cell DCI may be configured based on the following separate method. In this case, for each of the multiple co-scheduled cell sets (e.g., N_co co-scheduled cell sets) configured in the entire schedulable cell set, the sum L_sum of the L values ​​set for the cells in the co-scheduled cell set may be calculated, and the maximum value of the N_co values ​​of L_sum calculated for the N_co co-scheduled cell sets may be determined as the size of the specific DCI field (configured in the multi-cell DCI).

[0197] For example, in the case of the PUSCH TPC field, when two co-scheduled cell sets #1 and #2 of the schedulable cell set {Cell 1, Cell 2, Cell 3} are configured as {Cell 1, Cell 2} and {Cell 2, Cell 3}, and the sizes L of the PUSCH TPC fields configured for Cells 1 / 2 / 3 are 1 / 1 / 2 bits respectively, the L_sum of co-scheduled cell set #1 is 2 bits and the L_sum of co-scheduled cell set #2 is 3 bits. Therefore, the size of the PUSCH TPC field configured in the multi-cell DCI can be determined as 3 bits, which is the maximum of the two values of L_sum.

[0198] [Configure table size for (MC-DCI with reduced compared to SC-DCI)]

[0199] For a specific DCI field (e.g., ChannelAccess-CPext-CAPC (for PUSCH)) that applies the following individual method (its DCI field size determination method) (and / or the shared cell common method based on Option X), the number N_cfg of states / indices that can be indicated by the DCI field in the multi-cell DCI for each cell and the corresponding field size L_cfg = ceil{log2(N_cfg)} can be set separately (for each cell). In this case, they can be set to N_cfg < N and / or L_cfg < L.

[0200] Specifically, for a specific DCI field in the multi-cell DCI as described above, when N_cfg states / indices and field size L_cfg are set separately (for a specific cell), the following individual method (its DCI field size determination method) (and / or the shared cell common method (based on the Option X method)) can be applied based on the number / set of states / indices and the field size. In the absence of such individual configuration, the following individual method (its DCI field size determination method) (and / or the shared cell common method (based on the Option X method)) can be applied based on the N states / indices and field size L set in the single-cell DCI.

[0201] [1] Configuration of DL (or UL) DCI fields for multi-cell PDSCH (or PUSCH) scheduling

[0202] The various methods (e.g., Method 1 to Method 6) for configuring DCI fields described below can be understood to be applied to the types of each DCI field. It is not necessary that all fields in the multi-cell scheduling DCI must be configured using a specific method. For example, in a multi-cell scheduling DCI, the first DCI field can be configured based on Method X and the second DCI field can be configured based on Method Y. Additionally, for simplicity of description, the differences between the following methods assume the most detailed configuration. Therefore, a single DCI field can be configured using a combination of different DCI field configuration methods as long as they do not conflict with each other.

[0203] 1) DCI field configuration type

[0204] A. Method 1: Shared reference cell

[0205] Only one field may be configured in a multi-cell DCI, and the value indicated by the DCI field may be applied only to a specific reference cell (among the cells scheduled by the multi-cell DCI) (e.g., the cell that has sent the DCI, the cell with the lowest (or highest) cell index, or the cell indicated by the value of the CIF field) (configured to operate as indicated by the DCI field), while a specific predefined / set default value is applied to other cells.

[0206] B. Method 2: Sharing a single cell

[0207] Only one field may be configured (at most) in a multi-cell DCI, and only when one cell is scheduled (via the multi-cell DCI) may the DCI field be configured (the value indicated by the field applies to this one cell). When multiple cells are scheduled, the DCI field may not be configured and may be omitted (in this case, a specific predefined / set default value may apply to multiple cells).

[0208] C. Method 3: Public Shared Community

[0209] Only one field may be configured in a multi-cell DCI, and the value indicated by the DCI field may be commonly applied to all cells (through multi-cell DCI scheduling).

[0210] D. Method 4: Shared State Extension

[0211] Only one field may be configured in a multi-cell DCI, and each of a plurality of states / code points that the DCI field may indicate may be configured / set by a combination of a plurality of pieces of information about a plurality of cells, rather than information about a single cell.

[0212] E. Method 5: Alone

[0213] A number of fields equal to the number of cells scheduled by the multi-cell DCI may be configured (in the DCI) (configured to operate as indicated by the corresponding DCI field). Each scheduled cell may be matched with a separate field so that the value indicated by the field may be applied to the cell. For example, when frequency domain resource allocation (FDRA) information and / or MCS information are each configured in a separate method, the multi-cell DCI may include (but is not limited to) FDRA information and / or MCS information for each of the multiple cells (e.g., first FDRA information / first MCS information for the first scheduled cell, second FDRA information / second MCS information for the second scheduled cell, etc.).

[0214] F. Method 6: Omit

[0215] The corresponding DCI field may not be configured and may be omitted in the multi-cell DCI (in this case, a specific predefined / set default value may be applied to the cells scheduled by the multi-cell DCI).

[0216] 2) Example of applying the proposed method according to the DCI field

[0217] For each of the various DCI fields that may be included in the multi-cell DCI, an application example of the above-mentioned “1) DCI field configuration type” is discussed below.

[0218] A. Bandwidth Part (BWP) Indicator

[0219] i. Option 1: Applying the shared reference cell approach

[0220] The value (BWP index) indicated by the corresponding DCI field may be applied only to a specific reference cell (among cells scheduled by multi-cell DCI), and the current operating BWP may be maintained for other cells without BWP switching.

[0221] ii. Option 2: Applying the shared single cell approach

[0222] The corresponding DCI field may be configured (and the value indicated by it (BWP index) may be applicable to the cell) only when one cell is scheduled (via multi-cell DCI). When multiple cells are scheduled, the corresponding DCI field may not be configured and may be omitted (in this case, the current operating BWP may be maintained for multiple cells without BWP switching).

[0223] iii. Option 3: Apply the Omission Method

[0224] The corresponding DCI field may not be configured and may be omitted in the multi-cell DCI (in this case, the current operating BWP may be maintained for the cells scheduled by the multi-cell DCI without BWP switching).

[0225] B. VRB to PRB mapping (RB mapping)

[0226] i. Option 1: Applying the shared reference cell approach

[0227] The value (RB mapping method) indicated by the corresponding DCI field may be applied only to PDSCH on a specific reference cell (among cells scheduled by multi-cell DCI), while a specific default value (eg, non-interleaved mapping) may be applied to PDSCH on other cells.

[0228] ii. Option 2: Applying the shared single cell approach

[0229] Only when one cell is scheduled (via multi-cell DCI), the corresponding DCI field may be configured (and the value indicated by it (RB mapping method) may be applied to the PDSCH on that cell). When multiple cells are scheduled, the corresponding DCI field may not be configured and may be omitted (in this case, a specific default value (e.g., a non-interleaved mapping method) may be applied to the PDSCH on multiple cells).

[0230] iii. Option 3: Apply the Omission Method

[0231] The corresponding DCI field may not be configured and may be omitted in the multi-cell DCI (in this case, a specific default value (eg, a non-interleaved mapping method) may be applied to the PDSCH on the cells scheduled by the multi-cell DCI).

[0232] iv. Option 4: Applying the public shared cell approach

[0233] The value (RB mapping method) indicated by the corresponding DCI field can be commonly applied to PDSCH on all cells (scheduled by multi-cell DCI) (the cells may be all cells (among the cells scheduled by multi-cell DCI) that have configured RB mapping indicator bits).

[0234] v. Note 0: In this case, the specific reference cell may be determined as a specific cell among cells configured with a VRB-to-PRB mapping indicator (in an existing single-cell (scheduling) DCI).

[0235] vi. Note 1: In this case, for cell A configured with a VRB to PRB mapping indicator (in the existing single-cell (scheduling) DCI) and cell B not configured with the indicator, the same cell subgroup may be configured / restricted to include only cell A or only cell B (i.e., not including cell A and cell B together). In this configuration, the shared reference cell or shared cell common method may be applied separately to each cell subgroup.

[0236] vii. Note 2: Alternatively, cell A and cell B may be configured to belong to the same cell subgroup. In this state, the shared reference cell or shared cell common method may be applied individually to each cell subgroup.

[0237] 1. When the shared cell common method is applied to a cell subgroup including both cell A and cell B, a) the indicator field configuration may be omitted and a specific default value (e.g., non-interleaved mapping method) may be always applied to the cell subgroup, or b) the indicator field may be configured for the cell subgroup, and when the interleaved mapping method is indicated by the field, an operation may be performed under the assumption that there is no scheduling for cell B. Alternatively, c) the indicator field may be configured for the cell subgroup, and a specific default value (e.g., non-interleaved mapping method) may be always applied to cell B.

[0238] 2. A cell subgroup may be considered / applied as a co-scheduled cell set (all cells belonging to the set).

[0239] viii. Note A: The shared cell common method may also be applied to the FDRA field / indication of each cell subgroup (or co-scheduled cell set). In this case, the FDRA information / value based on the total number of RBs and RBG size on a specific reference cell may be indicated by the FDRA field, and the frequency resources of each cell may be determined by applying / interpreting the information / value to other cells in common.

[0240] 1. In this case, VRB to PRB mapping may be indicated / configured for the reference cell and other cells in the following four combinations, and it may be necessary to determine how / in what order these combinations are applied.

[0241] a. Case 1: indicating / configuring non-interleaving of the reference cell and non-interleaving of other cells.

[0242] b. Case 2: indicating / configuring non-interleaving of the reference cell and interleaving of other cells.

[0243] c. Case 3: indicating / configuring interleaving of the reference cell and non-interleaving of other cells.

[0244] d. Case 4: indicating / configuring the interleaving of the reference cell and the interleaving of other cells.

[0245] 2. Option A: The FDRA information / value indicated in the form of non-interleaved mapping can first be applied / interpreted for other cells based on the reference cell (if the reference cell is indicated / configured as interleaved, before applying the corresponding interleaved mapping method), and then the frequency resources of other cells can be determined by applying the interleaved mapping method based on the FDRA information / value interpreted / configured in this manner (if interleaving is indicated / configured for other cells).

[0246] 3. Option B: For case 4, the FDRA information / value based on the reference cell indication and subject to the interleaved mapping method can be directly applied / interpreted to other cells to determine the frequency resources of other cells.

[0247] 4. Option C: Option A method can be applied for cases 1 / 2 / 3, and Option B method can be applied for case 4 to determine the frequency resources of other cells.

[0248] C.PRB Bundle Size Indicator

[0249] i. Option 1: Applying the shared reference cell approach

[0250] The value (PRB bundle size) indicated by the corresponding DCI field may be applied only to the PDSCH on a specific reference cell (among the cells scheduled by multi-cell DCI), while a specific default value (for example, assuming a staticBundling configuration or a predefined / set PRB bundle size) may be applied to the PDSCH on other cells.

[0251] ii. Option 2: Applying the shared single cell approach

[0252] The corresponding DCI field may be configured (and the value indicated by it (PRB bundle size) may be applied to the PDSCH on that cell) only when one cell is scheduled (via multi-cell DCI). When multiple cells are scheduled, the corresponding DCI field may not be configured and may be omitted (in this case, a specific default value (e.g., assuming a staticBundling configuration or a predefined / set PRB bundle size) may be applied to the PDSCH on multiple cells).

[0253] iii. Option 3: Apply a separate method

[0254] A separate field may be configured for each cell scheduled via a multi-cell DCI, wherein the size of the separate field may vary according to the number of scheduled cells (e.g., the field size may be smaller when the number of scheduled cells is greater than N (e.g., N=1) than when the number of scheduled cells is less than or equal to N).

[0255] iv. Option 4: Apply the Omission Method

[0256] The corresponding DCI field may not be configured and may be omitted in the multi-cell DCI (in this case, a specific default value (e.g., assuming a staticBundling configuration or a predefined / set PRB bundle size) may be applied to the PDSCH on the cells scheduled by the multi-cell DCI).

[0257] v. Note 0: In this case, the specific reference cell may be determined as a specific cell among the cells configured with a PRB bundling size indicator (in the existing single-cell (scheduling) DCI), and the specific default (PRB bundling size) value may be specified as, for example, 2 RBs or X RBs according to the staticBundling configuration.

[0258] vi. Note 1: In this case, for cell A configured with a PRB bundling size indicator (in the existing single-cell (scheduling) DCI) and cell B not configured with the indicator, the same cell subgroup may be configured / restricted to include only cell A or only cell B (i.e., not including cell A and cell B together). In this configuration, the shared reference cell or shared cell common method may be applied separately to each cell subgroup.

[0259] vii. Note 2: Alternatively, cell A and cell B may be configured to belong to the same cell subgroup. In this configuration, the shared reference cell or shared cell common method may be applied individually to each cell subgroup.

[0260] 1. When the shared cell common method is applied to a cell subgroup including both cell A and cell B, a) the indicator field configuration may be omitted and a specific default value may always be applied to the cell subgroup, or b) the indicator field may be configured for the cell subgroup, wherein when a bit "0" (or "1") is indicated by the field, a specific default value may be applied to cell B, and when a bit "1" (or "0") is indicated, an operation may be performed under the assumption that there is no scheduling for cell B. Alternatively, c) the indicator field may be configured for the cell subgroup, and a specific default value may always be applied to cell B.

[0261] 2. A cell subgroup may be considered / applied as a co-scheduled cell set (all cells belonging to the set).

[0262] D. Rate Matching (RM) Indicator

[0263] i. Option 1: Applying the shared reference cell approach

[0264] The value (RM target resource) indicated by the corresponding DCI field may be applied only to PDSCH on a specific reference cell (among cells scheduled by multi-cell DCI), while PDSCH on other cells may be received assuming that there is no indication of RM target resource / operation.

[0265] ii. Option 2: Applying the shared single cell approach

[0266] The corresponding DCI field may be configured (and the value indicated by it (RM target resource) may be applied to the PDSCH on that cell) only when one cell is scheduled (via multi-cell DCI). When multiple cells are scheduled, the corresponding DCI field may not be configured and may be omitted (in this case, the PDSCH on multiple cells may be received under the assumption that there is no indication of RM target resource / operation).

[0267] iii. Option 3: Apply the Omission Method

[0268] The corresponding DCI field may not be configured and may be omitted in the multi-cell DCI (in this case, the PDSCH on the cells scheduled by the multi-cell DCI may be received under the assumption that there is no indication of RM target resources / operation).

[0269] iv. Option 4: Apply a separate method

[0270] A separate field may be configured for each cell scheduled via a multi-cell DCI, wherein the size of the separate field may vary according to the number of scheduled cells (e.g., the field size may be smaller when the number of scheduled cells is greater than N (e.g., N=1) than when the number of scheduled cells is less than or equal to N).

[0271] v. Option 5: Apply the Shared State Extension Method

[0272] 1. Each of the multiple states that can be indicated by the corresponding DCI field can be configured / set by a combination of multiple RM target resources for multiple PDSCHs on multiple cells (rather than RM target resources for PDSCH on a single cell), so a specific combination of RM target resources (for multiple PDSCHs on multiple cells) can be indicated by this one field.

[0273] [Public T1B: Contains the "no trigger" state]

[0274] 2. When the shared state extension method is applied to a specific DCI field (RM indicator, ZP-CSI-RS trigger, SRS request, SRS offset indicator, invalid symbol pattern indicator, PDCCH monitoring adaptation indication, minimum applicable scheduling offset indicator, etc.), a parameter / value (combination) may be configured for each of a plurality of cells configured for a state that may be indicated by a DCI field. In this case, for some of the plurality of cells, the field may be set to "no indication" (e.g., no trigger, no indication, no application, or no command).

[0275] vi. Note 0: In this case, the specific reference cell may be determined as a specific cell among cells configured with the RM indicator (in the existing single-cell (scheduling) DCI).

[0276] vii. Note 1: In this case, for cell A configured with an RM indicator (in the existing single-cell (scheduling) DCI) and cell B not configured with the indicator, the same cell subgroup may be configured / restricted to include only cell A or only cell B (i.e., not including cell A and cell B together). In this configuration, the shared reference cell or shared cell common method may be applied separately to each cell subgroup.

[0277] viii. Note 2: Alternatively, cell A and cell B may be configured to belong to the same cell subgroup. In this configuration, the shared reference cell or shared cell common method may be applied individually to each cell subgroup.

[0278] 1. When the shared cell common method is applied to a cell subgroup including both cell A and cell B, a) the indicator field configuration may be omitted for the cell subgroup, and PDSCH reception may be performed under the constant assumption that there is no RM target resource / operation indication, or b) the indicator field may be configured for the cell subgroup, and when (at least one) bit "1" is indicated by the field, the operation may be performed considering / assuming that there is no scheduling for cell B, or c) the indicator field may be configured for the cell subgroup, and PDSCH reception may be performed under the constant assumption that there is no RM target resource / operation indication for cell B.

[0279] 2. A cell subgroup may be considered / applied as a co-scheduled cell set (including all cells in the set).

[0280] ix. Note 3: In addition, the RM indicator field (in the existing single-cell (scheduling) DCI) may be configured such that a cell X set to a specific size X (e.g., 1 bit) and a cell Y set to a larger size Y (e.g., 2 bits) are included in the same cell subgroup. In this configuration, a shared reference cell or a shared cell common method may be applied individually to each cell subgroup.

[0281] 1. When the shared cell common method is applied to a cell subgroup including both cell X and cell Y, a) the indicator field may be configured with a smaller size X (e.g., 1 bit) of the cell subgroup, and may indicate only (the application status of) "rateMatchPatternGroup1" of cell Y, omitting the indication of (the application status of) "rateMatchPatternGroup2" (i.e., assuming that there is no indication of RM target resources), or b) the indicator field may be configured with a smaller size X (e.g., 1 bit) of the cell subgroup, and may be configured under the constant assumption that there is no indication of RM target resources / operation for cell Y. PDSCH reception is performed, c) the indicator field can be configured with a larger size Y (e.g., 2 bits) of the cell subgroup, and the presence or absence of RM target resources can be indicated for cell X through a specific 1 bit (e.g., MSB or LSB) in the field (in addition, in this case, when bits other than the specific 1 bit are indicated as "1", the operation can be performed under the assumption that there is no RM target resource / operation indication or there is no scheduling for cell X), or d) the indicator field can be configured with a larger size Y (e.g., 2 bits) of the cell subgroup, and PDSCH reception can be performed under the constant assumption that there is no RM target resource / operation indication for cell X.

[0282] 2. A cell subgroup may be considered / applied as a co-scheduled cell set (including all cells in the set).

[0283] E.ZP CSI-RS trigger

[0284] i. Option 1: Applying the shared reference cell approach

[0285] The value indicated by the corresponding DCI field (ZP CSI-RS resource) may be applied only to the PDSCH on a specific reference cell (among cells scheduled by multi-cell DCI), while PDSCH on other cells may be received under the assumption that there is no ZP CSI-RS resource indication.

[0286] ii. Option 2: Applying the shared single cell approach

[0287] The corresponding DCI field may be configured only when one cell is scheduled (via multi-cell DCI) (and the value indicated by it (ZP CSI-RS resource) may be applied to the PDSCH on that cell). When multiple cells are scheduled, the corresponding DCI field may not be configured and may be omitted (in this case, the PDSCH on multiple cells may be received under the assumption that there is no ZP CSI-RS resource indication).

[0288] iii. Option 3: Apply the Omission Method

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

[0290] iv. Option 4: Apply a separate method

[0291] A separate field may be configured for each cell scheduled via a multi-cell DCI, wherein the size of the separate field may vary according to the number of scheduled cells (e.g., the field size may be smaller when the number of scheduled cells is greater than N (e.g., N=1) than when the number of scheduled cells is less than or equal to N).

[0292] v. Option 5: Apply the Shared State Extension Method

[0293] Each of the multiple states that can be indicated by the corresponding DCI field can be configured / set by a combination of multiple ZP CSI-RS resources for multiple PDSCHs on multiple cells (rather than ZP CSI-RS resources for PDSCH on a single cell), so a specific combination of ZP CSI-RS resources (for multiple PDSCHs on multiple cells) can be indicated by this one field.

[0294] i. Note 0: In this case, the specific reference cell may be determined as a specific cell among cells configured with ZP CSI-RS triggering (in the existing single-cell (scheduling) DCI).

[0295] ii. Note 1: In this case, for cell A configured with a ZP CSI-RS trigger / indicator (in the existing single-cell (scheduling) DCI) and cell B not configured with the indicator, the same cell subgroup may be configured / restricted to include only cell A or only cell B (i.e., not including cell A and cell B together). In this configuration, the shared reference cell or shared cell common method may be applied separately to each cell subgroup.

[0296] iii. Note 2: Alternatively, cell A and cell B may be configured to belong to the same cell subgroup. In this configuration, the shared reference cell or shared cell common method may be applied individually to each cell subgroup.

[0297] 1. When the shared cell common method is applied to a cell subgroup including both cell A and cell B, a) the indicator field configuration may be omitted for the cell subgroup, and PDSCH reception may be performed under the constant assumption that there is no ZP CSI-RS resource indication, or b) the indicator field may be configured for the cell subgroup, and when (at least one) bit "1" is indicated by the field, the operation may be performed considering / assuming that there is no scheduling for cell B, or c) the indicator field may be configured for the cell subgroup, and PDSCH reception may be performed under the constant assumption that there is no ZP CSI-RS resource indication for cell B.

[0298] 2. A cell subgroup may be considered / applied as a co-scheduled cell set (including all cells in the set).

[0299] iv. Note 3: In addition, the ZP CSI-RS trigger field (in the existing single-cell (scheduling) DCI) may be configured such that cell X set to a specific size X (e.g., 1 bit) and cell Y set to a larger size Y (e.g., 2 bits) are included in the same cell subgroup. In this configuration, the shared reference cell or shared cell common method may be applied separately to each cell subgroup.

[0300] 1. When the shared cell common method is applied to a cell subgroup including both cell X and cell Y, a) the indicator field may be configured with a smaller size X (e.g., 1 bit) of the cell subgroup, and may indicate (the application state of) only one A-ZP CSI-RS set with the lowest index of cell Y, omitting the indication of (the application state of) the remaining A-ZP CSI-RS sets (i.e., assuming that there is no indication of the remaining A-ZP CSI-RS sets), or b) the indicator field may be configured with a smaller size X (e.g., 1 bit) of the cell subgroup, and PDSCH reception may be performed under a constant assumption that there is no indication of the ZP CSI-RS resource for cell Y, and PDSCH reception may be performed, or c) the indicator field may be configured with a larger size Y (e.g., 2 bits) of the cell subgroup, and may indicate for cell X whether there is an RM target resource through a specific 1 bit (e.g., MSB or LSB) in the field (in addition, in this case, when bits other than the specific 1 bit are indicated as "1", it may be indicated in the absence of the ZP CSI-RS resource. CSI-RS resource indication or operation is performed under the assumption that there is no scheduling for cell X), or d) the indicator field can be configured with a larger size Y (e.g., 2 bits) for the cell subgroup, and PDSCH reception can be performed under the constant assumption that there is no ZP CSI-RS resource indication for cell X.

[0301] 2. A cell subgroup may be considered / applied as a co-scheduled cell set (including all cells in the set).

[0302] F. One-time HARQ-ACK (Type 3 Codebook) Request

[0303] i. Option 1: Applying the shared single cell approach

[0304] Only when one cell is scheduled (through multi-cell DCI), the corresponding DCI field may be configured (and it may indicate whether HARQ-ACK feedback based on the type 3 codebook is configured / sent (corresponding HARQ-ACK mapped / configured with each HARQ (process) ID). When multiple cells are scheduled, the corresponding DCI field may not be configured and may be omitted (in this case, it may be assumed that there is no configuration / transmission indication of HARQ-ACK feedback based on the type 3 codebook (through multi-cell DCI)).

[0305] ii. Option 2: Apply the Omission Method

[0306] The corresponding DCI field may not be configured and may be omitted in the multi-cell DCI (therefore, when a cell is scheduled via the multi-cell DCI, it may be assumed that there is no indication of HARQ-ACK feedback configuration / transmission based on the type 3 codebook (via the multi-cell DCI)).

[0307] G. Enhanced Type 3 Codebook (e-Type-3 CB Index) Indicator

[0308] i. Option 1: Applying the shared single cell approach

[0309] The corresponding DCI field (and whether to configure / send e-Type-3 CB (index) (HARQ-ACK of only some cells and / or some HARQ IDs among the cells to which CA is applied) may be configured only when one cell is scheduled (through multi-cell DCI). When multiple cells are scheduled, the corresponding DCI field may not be configured and may be omitted (in this case, it may be assumed that there is no configuration / transmission indication of e-Type-3 CB (through multi-cell DCI)).

[0310] ii. Option 2: Apply the Omission Method

[0311] The corresponding DCI field may not be configured in the multi-cell DCI and may be omitted (thus, when a cell is scheduled via multi-cell DCI, it may be assumed that there is no indication (via DCI) of e-Type-3 CB configuration / transmission).

[0312] iii. Option 3: Use the MCS field for a specific (reference) cell

[0313] 1. When an invalid value (or a specific predefined value) is indicated by a frequency domain resource assignment (FDRA) field corresponding to a specific (reference) one of one or more (schedulable) cells indicated by a multi-cell DCI (or by a DCI indicating e-Type-3 CB configuration / transmission), e-Type-3 CB index information may be signaled / indicated by an MCS field corresponding to the specific (reference) cell. For example, one of one or more e-Type-3 CB indexes configured for the UE by higher layer signaling may be indicated by the multi-cell DCI. Each e-Type-3 CB index may correspond to a subset of all cells configured for the UE, and the cell to perform e-Type-3 CB reporting may be determined based on the e-Type-3 CB index indicated by the multi-cell DCI. For example, referring to Fig.10, assuming that e-Type-3 CB index 1 corresponds to {cell A, cell B, cell C}, e-Type-3 CB index 2 corresponds to {cell A, cell C, cell D, cell E}, and the UE receives a multi-cell DCI indicating / triggering an e-Type-3 CB report. An invalid value (or a specific predefined value) may be indicated in the multi-cell DCI by a second FDRA field for a specific cell among the FDRA fields, and the e-Type-3 CB index may be indicated in the multi-cell DCI by a second MCS field for a specific cell among the FDRA fields. For example, when the second value set in the second MCS field indicates e-Type-3 CB index 1, the UE may generate and report an e-Type-3 CB containing HARQ-ACK of {cell A, cell B, cell C}. In this way, the e-Type-3 CB index information, rather than the MCS, may be specified by the MCS field of a specific cell associated with the FDRA field indicating an invalid value (or a specific predefined value) among the FDRA fields. For example, in Fig.11 In the embodiment, when the MCS field of a specific cell associated with the second FDRA field indicating an invalid value (or a predefined specific value) among the FDRA fields is the second MCS field, the second MCS field can be reused to indicate the e-Type-3 CB index information (instead of the MCS).

[0314] a. In one example, the UE may operate assuming that there is no PDSCH scheduling / transmission for a specific (reference) cell. For example, the UE may determine that PDSCH is not scheduled by a multi-cell DCI for a specific cell associated with the FDRA field indicating an invalid value (or a specific predefined value).

[0315] b. In one example, the UE may be allowed to schedule / transmit PDSCH of cells other than a specific (reference) cell among one or more cells indicated (schedulable) by the multi-cell DCI indicating the e-Type-3 CB configuration / transmission as described above (based on invalid FDRA). Fig.11 , the first FDRA field of the cell other than the specific cell may contain valid FDRA information, and the first value of the first MCS field may be the MCS of the PDSCH. Alternatively, the UE may operate assuming that there is no PDSCH scheduling / transmission even for a cell (other than the specific (reference) cell) among one or more cells indicated (schedulable) by the multi-cell DCI indicating the e-Type-3 CB configuration / transmission as described above (based on the invalid FDRA).

[0316] H.HARQ-ACK retransmission indicator

[0317] i. Option 1: Applying the shared single cell approach

[0318] Only when one cell is scheduled (through multi-cell DCI), the corresponding DCI field (through which the HARQ-ACK retransmission status is indicated (indicating that the HARQ-ACK indicated to be sent at a specific time (time slot A) should be retransmitted at another time (time slot B)) can be configured. When multiple cells are scheduled, the corresponding DCI field may not be configured and may be omitted (in this case, it is assumed that there is no HARQ-ACK retransmission indication (through multi-cell DCI)).

[0319] ii. Option 2: Apply the Omission Method

[0320] The corresponding DCI field may not be configured and may be omitted in the multi-cell DCI (therefore, when a cell is scheduled via the multi-cell DCI, it may be assumed that there is no HARQ-ACK retransmission indication (via DCI)).

[0321] iii. Option 3: Use the MCS field for a specific (reference) cell

[0322] 1. Information for determining time slot A (HARQ-ACK retransmission target) (e.g., offset information indicating time slot A) may be signaled / indicated through an MCS field corresponding to a specific (reference) cell among one or more (schedulable) cells indicated by multi-cell DCI (when HARQ-ACK retransmission is indicated, by DCI). For example, referring to Fig.12 , the UE sends HARQ-ACK (e.g., type 1 or type 2 HARQ-ACK codebook) in each of one or more time slots (1105), and receives multi-cell DCI (1110). Based on the indication of HARQ-ACK retransmission, the UE may determine that the MCS field for a specific (reference) cell among the MCS fields in the multi-cell DCI contains information for determining a time slot A related to HARQ-ACK retransmission. The UE may determine time slot A among one or more time slots in which HARQ-ACK is sent before the multi-cell DCI reception time slot based on the MCS field for the specific (reference) cell (1115). The UE may retransmit the HARQ-ACK sent in time slot A in a time slot later than the multi-cell DCI reception time slot (1120). In one example, the multi-cell DCI may include a HARQ-ACK retransmission indication field to trigger HARQ-ACK retransmission.

[0323] a. For example, the UE may operate assuming that there is no PDSCH scheduling / transmission for a specific (reference) cell.

[0324] b. For example, PDSCH scheduling / transmission may be enabled for cells other than a specific (reference) cell among one or more (schedulable) cells indicated by a multi-cell DCI indicating HARQ-ACK retransmission as described above (using an MCS field corresponding to a specific (reference) cell). For example, the MCS field of a cell other than the specific cell may contain valid MCS information instead of information about time slot A as a target of HARQ-ACK retransmission. Alternatively, even for a cell (other than a specific (reference) cell) among one or more (schedulable) cells indicated by a multi-cell DCI indicating HARQ-ACK retransmission as described above (using an MCS field corresponding to a specific (reference) cell), the UE may operate assuming that there is no PDSCH scheduling / transmission.

[0325] I.SRS Request

[0326] i. Option 1: Applying the shared reference cell approach

[0327] The value (SRS transmission resource) indicated by the corresponding DCI field may be applied only to a specific reference cell (among cells scheduled by multi-cell DCI), and other cells may operate assuming that there is no SRS transmission indication.

[0328] ii. Option 2: Applying the shared single cell approach

[0329] Only when one cell is scheduled (via multi-cell DCI), the corresponding DCI field may be configured (and the value indicated by it (SRS transmission resource) may be applicable to that cell). When multiple cells are scheduled, the corresponding DCI field may not be configured and may be omitted (in this case, it may be assumed that there is no SRS transmission indication for multiple cells).

[0330] iii. Option 3: Apply the Omission Method

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

[0332] iv. Note 0: In this case, the specific reference cell may be determined as a specific cell among cells configured with an SRS request / indicator (in an existing single-cell (scheduling) DCI).

[0333] v. Note 1: In this case, the SRS request / indicator field (in the existing single-cell (scheduling) DCI) may be configured such that cell X set to a specific size X (e.g., 2 bits) and cell Y set to a larger size Y (e.g., 3 bits) are included in the same cell subgroup. In this configuration, the shared reference cell or shared cell common method may be applied individually to each cell subgroup.

[0334] 1. When the shared cell common method is applied to a cell subgroup including both cell X and cell Y, a) the indicator field may be configured with a smaller size X (e.g., 2 bits) of the cell subgroup and may be considered / assumed to indicate SRS transmission (resource / state) of cell Y on a specific default UL carrier (e.g., a currently operated UL carrier, a non-SUL carrier, or a SUL carrier), or b) the indicator field may be configured with a smaller size X (e.g., 2 bits) of the cell subgroup and operation may be performed under a constant assumption that there is no SRS transmission indication for cell Y, c) the indicator field may be configured with a smaller size X (e.g., 2 bits) of the cell subgroup and operation may be performed under a constant assumption that there is no SRS transmission indication for cell Y, The field may be configured with a larger size Y (e.g., 3 bits) of a cell subgroup, and SRS transmission (resource / status) may be indicated for cell X through specific (e.g., highest index) 2 bits in the field (in addition, in this case, when bits other than the specific X bits are indicated as "1", operations may be performed under the assumption that there is no SRS transmission indication for cell X or no scheduling for cell X), or d) the indicator field may be configured with a larger size Y (e.g., 3 bits) of a cell subgroup, and operations may be performed under the constant assumption that there is no SRS transmission indication for cell X.

[0335] 2. A cell subgroup may be considered / applied as a co-scheduled cell set (including all cells in the set).

[0336] J.CBG Transmission Information (CBGTI)

[0337] i. Option 1: Applying the shared single cell approach

[0338] The corresponding DCI field may be configured (and the value indicated by it (CBG index) may be applied to the PDSCH on that cell) only when one cell is scheduled (via multi-cell DCI). When multiple cells are scheduled, the corresponding DCI field may not be configured and may be omitted (in this case, PDSCH on multiple cells may be received under the assumption that there is no scheduling of CBG-based PDSCH transmission).

[0339] ii. Option 2: Apply the Omission Method

[0340] The corresponding DCI field may not be configured and may be omitted in the multi-cell DCI (in this case, the PDSCH on the cell scheduled by the multi-cell DCI may be received under the assumption that there is no scheduling of CBG-based PDSCH transmission).

[0341] K.CBG clear information (CBGFI)

[0342] i. Option 1: Applying the shared single cell approach

[0343] The corresponding DCI field may be configured (and the value indicated by it (CBG buffer empty status) may be applied to the PDSCH on that cell) only when one cell is scheduled (via multi-cell DCI). When multiple cells are scheduled, the corresponding DCI field may not be configured and may be omitted (in this case, PDSCH on multiple cells may be received under the assumption that there is no CBG buffer empty indication).

[0344] ii. Option 2: Apply the Omission Method

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

[0346] L. Priority Indicator (PI)

[0347] i. Option 1: Applying the public shared cell approach

[0348] The value indicated by the corresponding DCI field (low priority (LP) or high priority (HP)) can be commonly applied to PDSCH (and corresponding HARQ-ACK) on all cells (scheduled by multi-cell DCI), and the cell can be all cells (among the cells scheduled by multi-cell DCI) in which PI is configured (in a single-cell DCI).

[0349] a. When HP is indicated through the above-mentioned field in DCI, for a cell that is not configured with PI (among the cells scheduled by multi-cell DCI) (in a single-cell DCI), alternative 1) may assume that there is no PI indication (or indicates LP), or alternative 2) may assume that there is no PDSCH scheduling for the cell (PI is not configured) and PDSCH reception on the cell may be skipped.

[0350] b. When LP is indicated by a field in a multi-cell DCI, the operation of alternative 1 is applicable to cells (among cells scheduled by DCI) for which PI is not configured (in a single-cell DCI).

[0351] ii. Option 2: Applying the shared reference cell approach

[0352] The value (LP or HP) indicated by the corresponding DCI field may be applied only to PDSCH (and corresponding HARQ-ACK) on a specific reference cell (among cells scheduled by multi-cell DCI), while Alternative 1 and / or Alternative 2 may be applied to other cells.

[0353] iii. Option 3: Applying the shared single cell approach

[0354] The corresponding DCI field may be configured only when one cell is scheduled (via multi-cell DCI) (and the value indicated by it (LP or HP) may be applied to the PDSCH (and corresponding HARQ-ACK) on that cell). When multiple cells are scheduled, the corresponding DCI field may not be configured and may be omitted (in this case, alternative 1 may be applied).

[0355] iv. Option 4: Apply the Omission Method

[0356] The corresponding DCI field may not be configured in the multi-cell DCI and may be omitted (in this case, Alternative 1 may be applied).

[0357] v. Note 1: When HP is indicated for at least one of the multiple cells scheduled by the same multi-cell DCI (LP is indicated for the other cells), all HARQ-ACKs corresponding to PDSCH transmissions on all scheduled cells may be determined as HP. In this case, the HP PUCCH resources may be indicated by the PUCCH Resource Indicator (PRI) field in the DCI.

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

[0359] vii. Note A: In this case, the specific reference cell may be determined as a specific cell among cells configured with a priority indicator (in the existing single-cell (scheduling) DCI).

[0360] viii. Note B: In this case, for cell A configured with a priority indicator (in the existing single-cell (scheduling) DCI) and cell B not configured with the indicator, the same cell subgroup may be configured / restricted to include only cell A or only cell B (i.e., not including cell A and cell B together). In this configuration, the shared reference cell or shared cell common method may be applied separately to each cell subgroup.

[0361] ix. Note C: Alternatively, cell A and cell B may be configured to belong to the same cell subgroup. In this configuration, the shared reference cell or shared cell common method may be applied individually to each cell subgroup.

[0362] 1. When the shared cell common method is applied to a cell subgroup including both cell A and cell B, a) the indicator field configuration may be omitted for the cell subgroup, and the operation may be performed by always considering / assuming that LP is indicated, or b) the indicator field may be configured for the cell subgroup, and when HP is indicated by the field, the operation may be performed by considering / assuming that there is no scheduling for cell B, or c) the indicator field may be configured for the cell subgroup, and the operation may be performed by always considering / assuming that LP is indicated for cell B.

[0363] 2. A cell subgroup may be considered / applied as a co-scheduled cell set (including all cells in the set).

[0364] [About the handling of the presence / absence of cross-cell PI]

[0365] x. Note X: As another operation method based on Option 1 (shared cell common) method, in Case 1) when PI is configured for all cells included in the co-scheduled cell set indicated by the multi-cell DCI (in the single-cell DCI), the same priority (e.g., HP or LP) indicated by the PI field in the DCI can be assumed / applied for PDSCH / PUSCH on all scheduled cells; in Case 2) when PI is configured for only some cells in the co-scheduled cell set indicated by the multi-cell DCI and not for other cells (in the single-cell DCI), it can be assumed / applied for PDSCH / PUSCH on all scheduled cells.

[0366] 1. Therefore, in case 2, the configuration / indication of the PI field may be omitted in the multi-cell DCI. Alternatively, the PI field may be configured / indicated in the multi-cell DCI, but the UE may ignore the PI field.

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

[0368] i. Option 1: Applying the public shared cell approach

[0369] The value indicated by the corresponding DCI field (whether to apply min K0 / K2) may be commonly applied to all cells (scheduled by multi-cell DCI). The cells may be all cells (among cells scheduled by multi-cell DCI) that set min K0 / K2.

[0370] ii. Option 2: Applying the shared reference cell approach

[0371] The value indicated by the corresponding DCI field (whether to apply min K0 / K2) may be applied only to a specific reference cell (among cells scheduled by multi-cell DCI), and other cells may operate under the assumption that there is no indication about applying min K0 / K2.

[0372] iii. Option 3: Applying the shared single cell approach

[0373] Only when one cell is scheduled (via multi-cell DCI), the corresponding DCI field may be configured (and the value indicated by it (whether min K0 / K2 is applied) may be applicable to the cell). When multiple cells are scheduled, the corresponding DCI field may not be configured and may be omitted (in this case, it may be assumed that there is no indication of applying min K0 / K2 for multiple cells).

[0374] iv. Option 4: Apply the Omission Method

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

[0376] N.SCell sleep indication

[0377] i. Option 1: Applying the shared single cell approach

[0378] The corresponding DCI field may be configured only when one cell is scheduled (via multi-cell DCI) (and the value indicated by it (whether to indicate dormant BWP (switching to BWP)) may be applied). When multiple cells are scheduled, the corresponding DCI field may not be configured and may be omitted (in this case, it may be assumed that there is no indication of dormant BWP (switching to BWP) via DCI).

[0379] ii. Option 2: Apply the Omission Method

[0380] The corresponding DCI field may not be configured in the multi-cell DCI and may be omitted (in this case, it may be assumed that there is no indication of dormant BWP (switching to BWP)).

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

[0382] iv. Note: Alternatively, indication of cell dormant operation may be allowed without actual PDSCH scheduling (on the cell) only when only one cell is indicated by the multi-cell DCI. When multiple cells are indicated by the multi-cell DCI, indication of cell dormant operation without actual PDSCH scheduling may not be allowed.

[0383] O.PDCCH monitoring skip / SS set switching indicator

[0384] i. Option 1: Applying the public shared cell approach

[0385] The value indicated by the corresponding DCI field (whether it is the PDCCH monitoring skip application state / interval or the monitoring target SS (search space) set group index) can be commonly applied to all cells (scheduled by multi-cell DCI). The cell can be all cells (among the cells scheduled by multi-cell DCI) that configure PDCCH monitoring skip / SS set group switching.

[0386] ii. Option 2: Applying the shared reference cell approach

[0387] The value indicated by the corresponding DCI field (whether it is the PDCCH monitoring skip application state / interval or the monitoring target SS set group index) can only be applied to a specific reference cell (among the cells scheduled by multi-cell DCI). Other cells can operate to receive PDCCH under the assumption that there is no PDCCH monitoring skip / SS set group switching indication.

[0388] iii. Option 3: Applying the shared single cell approach

[0389] The corresponding DCI field may be configured (and the value (PDCCH monitoring skip application state / interval or monitoring SS set group index) may be applied to the cell) only when one cell is scheduled (via multi-cell DCI). When multiple cells are scheduled, the corresponding DCI field may not be configured and may be omitted (in this case, the PDCCH may be received under the assumption that there is no PDCCH monitoring skip / SS set group switching indication for multiple cells).

[0390] iv. Option 4: Apply the Omission Method

[0391] The corresponding DCI field may not be configured and may be omitted in the multi-cell DCI (in this case, the PDCCH may be received under the assumption that there is no PDCCH monitoring skipping / SS set group switching indication for the cells scheduled by the multi-cell DCI).

[0392] Fig.13 is a diagram illustrating a method for receiving a signal by a UE according to one embodiment.

[0393] Reference Fig.13, the UE may monitor the physical downlink control channel (PDCCH) (1205).

[0394] Based on the monitoring of the PDCCH, the UE may detect downlink control information (DCI) for multi-cell scheduling (1210).

[0395] The DCI may include a single first bit field that provides code points for all one or more cells co-scheduled by the DCI at one time. The size "M" of the first bit field may be determined based on the first cell for which the total number of code points configured with respect to the first bit field is the largest number. For a second cell associated with a field size "K" that is smaller than the size "M" of the first bit field, the code point provided by the first bit field may be determined based on the value of the remaining bits excluding at least one bit from the first bit field.

[0396] The code point of the first bit field for the second cell may be determined based on the first 'K' bits or the last 'K' bits of the first bit field.

[0397] Based on the fact that a code point for the second cell determined based on the value of the remaining bits except for the at least one bit is not configured for the second cell, a specific code point configured for the second cell may be applied. The specific code point may be a code point with a highest value or a lowest value among the code points configured in the second cell.

[0398] Based on the fact that the code point for the second cell determined based on the values ​​of the remaining bits except for the at least one bit is not configured for the second cell, the UE may assume that the second cell is not scheduled through the DCI.

[0399] Based on the fact that the codepoint for the second cell determined based on the values ​​of the remaining bits except for the at least one bit is not configured for the second cell, the UE may maintain the most recently indicated codepoint for the second cell.

[0400] A set of code points related to the first bit field may be configured for each cell. The set of code points configured for each cell may be based on a set of code points configured for individual scheduling of each cell.

[0401] The first bit field may be a bandwidth part (BWP) indication field, an open loop power control (OLPC) field, a physical uplink shared channel (PUSCH) related listen-before-talk (LBT) field, or a beta offset indication field.

[0402] The UE may send or receive a signal on one or more co-scheduled cells based on the DCI.

[0403] Fig.14 is a diagram illustrating a method of transmitting a signal by a BS according to one embodiment.

[0404] Reference Fig.14, the BS may generate DCI for multi-cell scheduling (1305).

[0405] The BS may send DCI on the PDCCH to the UE (1310).

[0406] The DCI may include a single first bit field that provides code points for all one or more cells co-scheduled by the DCI at one time. The size "M" of the first bit field may be determined based on a first cell for which the total number of code points configured with respect to the first bit field is the largest number of UEs. For a second cell of a UE associated with a field size "K" that is smaller than the size "M" of the first bit field, a code point of the first bit field may be provided based on a value of the remaining bits excluding at least one bit from the first bit field.

[0407] The code point of the first bit field for the second cell may be indicated based on the first 'K' bits or the last 'K' bits of the first bit field.

[0408] Based on the fact that a code point for the second cell indicated based on the value of the remaining bits other than the at least one bit is not configured for the second cell, a specific code point configured in the second cell may be applied. The specific code point may be a code point with a highest value or a lowest value among the code points configured in the second cell.

[0409] Based on the fact that a code point for the second cell indicated based on values ​​of remaining bits except for the at least one bit is not configured for the second cell, it may be assumed that the second cell is not scheduled through the DCI.

[0410] Based on the fact that a codepoint for the second cell indicated based on values ​​of remaining bits except for the at least one bit is not configured for the second cell, the most recently indicated codepoint may be maintained for the second cell.

[0411] A set of code points related to the first bit field may be configured for each cell. The set of code points configured for each cell may be based on a set of code points configured for individual scheduling of each cell.

[0412] The first bit field may be a bandwidth part (BWP) indication field, an open loop power control (OLPC) field, a physical uplink shared channel (PUSCH) related listen-before-talk (LBT) field, or a beta offset indication field.

[0413] The BS may transmit or receive a signal on one or more co-scheduled cells based on the DCI.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0427] Reference Fig.17 , the wireless devices 100 and 200 may correspond to Fig.16The wireless devices 100 and 200 of the present invention may be configured by various elements, components, units / parts and / or modules. For example, each of the wireless devices 100 and 200 may include a communication unit 110, a control unit 120, a memory unit 130 and an additional component 140. The communication unit may include a communication circuit 112 and a transceiver 114. For example, the communication circuit 112 may include Fig.16 One or more processors 102 and 202 and / or one or more memories 104 and 204. For example, the transceiver 114 may include Fig.16 The control unit 120 is electrically connected to the communication unit 110, the memory unit 130, and the additional components 140, and controls the overall operation of the wireless device. For example, the control unit 120 may control the electrical / mechanical operation of the wireless device based on the program / code / command / information stored in the memory unit 130. The control unit 120 may transmit information stored in the memory unit 130 to the outside (e.g., other communication devices) via the communication unit 110 through a wireless / wired interface, or store information received from the outside (e.g., other communication devices) via the communication unit 110 in the memory unit 130 through a wireless / wired interface.

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

[0429] exist Fig.17In the wireless devices 100 and 200, various elements, components, units / parts and / or modules in the wireless devices 100 and 200 may all be connected to each other through a wired interface, or at least a part thereof may be wirelessly connected through the communication unit 110. For example, in each of the wireless devices 100 and 200, the control unit 120 and the communication unit 110 may be wired, and the control unit 120 and the first cell (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.

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

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

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

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

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

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

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

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

[0438] [Table 7]

[0439]

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

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

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

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

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

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

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

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

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

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

[0450] Industrial Applicability

[0451] 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: Monitor the physical downlink control channel PDCCH; as well as Based on the monitoring of the PDCCH, detecting downlink control information DCI for multi-cell scheduling, The DCI includes a single first bit field that provides a code point for all one or more cells co-scheduled by the DCI at one time, The size "M" of the first bit field is determined based on the first cell having a maximum number of code points configured with respect to the first bit field, and Wherein, for a second cell associated with a field size "K" that is smaller than the size "M" of the first bit field, the code point provided by the first bit field is determined based on the value of the remaining bits excluding at least one bit from the first bit field.

2. The method according to claim 1, wherein: The code point of the first bit field for the second cell is determined based on the first "K" bits or the last "K" bits of the first bit field.

3. The method according to claim 1, wherein: Based on the code point for the second cell determined based on the values ​​of the remaining bits except the at least one bit not being configured for the second cell, a specific code point configured for the second cell is applied.

4. The method according to claim 3, wherein: The specific code point is a code point having a highest value or a lowest value among code points configured in the second cell.

5. The method according to claim 1, wherein: Based on the fact that the code point for the second cell determined based on the values ​​of the remaining bits except the at least one bit is not configured for the second cell, the UE assumes that the second cell is not scheduled by the DCI.

6. The method according to claim 1, wherein: Based on the codepoint for the second cell determined based on the values ​​of the remaining bits except the at least one bit not being configured for the second cell, the UE maintains a most recently indicated codepoint for the second cell.

7. The method according to claim 1, wherein: A set of code points related to the first bit field is configured for each cell.

8. The method according to claim 7, wherein: The set of code points configured for each cell is based on the set of code points configured for individual scheduling of each cell.

9. The method according to claim 1, wherein: The first bit field is a bandwidth part BWP indication field, an open-loop power control OLPC field, a physical uplink shared channel PUSCH-related listen-before-talk LBT field, or a β offset indication field.

10. The method according to claim 1, further comprising the steps of: A signal is transmitted or received on the co-scheduled one or more cells based on the DCI. 11 . A computer-readable recording medium having recorded thereon a program for executing the method according to claim 1 .

12. An apparatus for wireless communication, the apparatus comprising: a memory configured to store instructions; as well as a processor configured to execute the instructions to perform operations, The operation of the processor includes: Monitoring the physical downlink control channel PDCCH; and Based on the monitoring of the PDCCH, detecting downlink control information DCI for multi-cell scheduling, The DCI includes a single first bit field that provides a code point for all one or more cells co-scheduled by the DCI at one time, The size "M" of the first bit field is determined based on the first cell having a maximum number of code points configured with respect to the first bit field, and Wherein, for a second cell associated with a field size "K" that is smaller than the size "M" of the first bit field, the code point provided by the first bit field is determined based on the value of the remaining bits excluding at least one bit from the first bit field.

13. The device according to claim 12, further comprising: a transceiver configured to send or receive wireless signals under the control of the processor, The device is a user equipment UE in a wireless communication system.

14. A method for sending a signal by a base station in a wireless communication system, the method comprising the following steps: Generate downlink control information DCI for multi-cell scheduling; as well as The DCI is sent to a user equipment UE via a physical downlink control channel PDCCH, The DCI includes a single first bit field that provides a code point for all one or more cells co-scheduled by the DCI at one time, The size "M" of the first bit field is determined based on the first cell of the UE having a maximum total number of code points configured with respect to the first bit field, and Wherein, for a second cell of the UE associated with a field size "K" that is smaller than the size "M" of the first bit field, the code point of the first bit field is provided based on a value of remaining bits excluding at least one bit from the first bit field.

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: Generate downlink control information DCI for multi-cell scheduling; and controlling the transceiver to send the DCI to a user equipment UE via a physical downlink control channel PDCCH, The DCI includes a single first bit field that provides a code point for all one or more cells co-scheduled by the DCI at one time, The size "M" of the first bit field is determined based on the first cell of the UE having a maximum total number of code points configured with respect to the first bit field, and Wherein, for a second cell of the UE associated with a field size "K" that is smaller than the size "M" of the first bit field, the code point of the first bit field is provided based on a value of remaining bits excluding at least one bit from the first bit field.

Images