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

The method optimizes wireless signal transmission/reception by monitoring PDCCH and DCI in cell combinations, addressing inefficiencies in multi-cell scheduling and payload determination, thereby enhancing the efficiency of wireless communication systems.

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

Patent Information

Application Number
CN202380036021.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-09-28
Filing Date
2023-04-27
Publication Date
2024-12-03

AI Technical Summary

Technical Problem

Existing wireless communication systems face inefficiencies in signal transmission and reception processes, particularly in handling multi-cell scheduling and payload determination for downlink control information (DCI) in wireless communication systems.

Method used

A method and apparatus for efficiently performing wireless signal transmission/reception by monitoring a physical downlink control channel (PDCCH) candidate and detecting downlink control channel (DCI) based on cell combinations, determining payload size based on the largest total number of DCI bits required, and configuring hybrid automatic repeat request-acknowledgement (HARQ-ACK) information for valid cells, while handling invalid cells through specific field configurations.

Benefits of technology

This approach enables efficient wireless signal transmission/reception processes by optimizing multi-cell scheduling and payload determination, enhancing the overall efficiency of wireless communication systems.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119072896A_ABST
    Figure CN119072896A_ABST
Patent Text Reader

Abstract

According to at least one of the various embodiments, a UE may monitor a physical downlink control channel (PDCCH) candidate and detect downlink control information (DCI) by monitoring the PDCCH candidate. The DCI may support multi-cell scheduling based on cell combinations of a plurality of cells configured in the UE, and a payload size of the DCI may be determined based on a first cell combination of which a total number of DCI bits required for co-scheduling cells is the largest among the cell combinations.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

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

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

[0003] Technical issues

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

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

[0006] Technical Solution

[0007] According to one aspect, a method for receiving a signal by a user equipment (UE) in a wireless communication system includes the following steps: monitoring a physical downlink control channel (PDCCH) candidate; and detecting a downlink control channel (DCI) by monitoring the PDCCH candidate. The DCI can support multi-cell scheduling based on a cell combination of multiple cells configured in the UE. The payload size of the DCI can be determined based on the first cell combination having the largest total number of DCI bits required for the co-scheduled cells among the cell combinations.

[0008] The payload of the DCI may be determined based on the sum size of all DCI fields of the first cell combination.

[0009] The cells co-scheduled by DCI may be indicated as one of the cell combinations.

[0010] The DCI may include first DCI field related information of each of the co-scheduled first cell and the second cell. Based on the first cell having a lower serving cell index than the second cell, in the DCI, the first DCI field related information of the first cell may be located before the first DCI field related information of the second cell. The first DCI field may include at least one of a modulation and coding scheme (MCS) field, a new data indicator (NDI) field, a redundant version (RV) field, a hybrid automatic repeat request (HARQ) process ID field, a frequency domain resource allocation (FDRA) field, a time domain resource allocation (TDRA) field, and a transmission power command (TPC) field of a physical uplink shared channel (PUSCH).

[0011] The sending or receiving of scheduling signals may be performed only for the remaining cells except at least one invalid cell among the cells jointly scheduled by DCI. At least one invalid cell may include a deactivated secondary cell (SCell), a cell operating as a dormant bandwidth part (BWP), a cell in which resources allocated by DCI overlap with semi-static resources configured differently in the uplink (UL) / downlink (DL) direction, and at least one of cells in which the frequency resource information indicated by the DCI is invalid. Hybrid automatic repeat request-acknowledgement (HARQ-ACK) information may be configured for the remaining cells except at least one invalid cell, or may be configured to include negative acknowledgment (NACK) information of at least one invalid cell. The DCI field value for at least one invalid cell in the DCI may be configured based on information of a specific bandwidth part (BWP).

[0012] According to another aspect, there may be provided a processor-readable recording medium having recorded thereon a program for executing the method.

[0013] According to another aspect, a UE for performing the method may be provided.

[0014] According to another aspect, a device for controlling a UE to perform the method may be provided.

[0015] According to an aspect, a method for transmitting a signal by a BS in a wireless communication system may include the following steps: generating downlink control information (DCI); and transmitting the DCI to a UE based on at least one physical downlink control channel (PDCCH) candidate of the UE. The DCI may support multi-cell scheduling based on a cell combination of multiple cells configured for the UE. The payload size of the DCI may be determined based on a first cell combination having the largest total number of DCI bits required for a co-scheduled cell among the cell combinations.

[0016] According to another aspect, a BS for performing the method may be provided.

[0017] Beneficial Effects

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

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

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

[0021] Figure 2 Shows the radio frame structure.

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

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

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

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

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

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

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

[0029] Fig.10 It is a diagram for explaining the arrangement of bits related to a specific field in a multi-cell scheduling DCI according to an embodiment.

[0030] Fig.11 It is a diagram for explaining the payload size in the multi-cell scheduling DCI according to an embodiment.

[0031] Fig.12 It is a diagram for explaining a method in which a UE receives a signal according to an embodiment.

[0032] Fig.13 FIG. 1 is a diagram for explaining a method of transmitting a signal by a BS according to an embodiment.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0048] [Table 1]

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

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

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

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

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

[0054] [Table 2]

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

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

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

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

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

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

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

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

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

[0064] -controlResourceSetId: CORESET related to SS

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

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

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

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

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

[0070] [Table 3]

[0071]

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

[0073] [Table 4]

[0074]

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

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

[0077] PDSCH transmits DL data (e.g., DL shared channel transport block (DL-SCHTB)) 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.

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

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

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

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

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

[0083] [Table 5]

[0084]

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

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

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

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

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

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

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

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

[0093] - Time domain resource assignment: Indicates K0 and the starting position (e.g., OFDM symbol index) and length (e.g., number of OFDM symbols) of the PDSCH in the time slot

[0094] -PDSCH-to-HARQ_feedback timing indicator: indicates K1

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

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

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

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

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

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

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

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

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

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

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

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

[0107] Carrier Aggregation

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

[0109] - Primary cell (PCell): A cell operating on a primary frequency (e.g., a primary component carrier (PCC)) on which a UE performs an initial connection establishment procedure or initiates a connection re-establishment procedure in the case of a UE configured with carrier aggregation. A primary cell group (MCG) cell operating in a primary frequency on which a UE performs an initial connection establishment procedure or initiates a connection re-establishment procedure.

[0110] - Secondary Cell (SCell): A cell that provides additional radio resources in addition to the special cell in the case of a UE configured with carrier aggregation.

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

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

[0113] - ServCell: This refers to the cell configured in the UE in the 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 refers to a special cell and a cell set including all SCells.

[0114] The control information may be configured to be sent and received only through a specific cell. For example, UCI may be sent via a special cell (e.g., PCell). When an SCell (hereinafter, PUCCH-SCell) that allows PUCCH transmission is configured, UCI may also be sent via 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. The BS may send PDCCH only through the scheduling cell (set). For example, a PDCCH for DL ​​allocation may be sent in cell #0 (i.e., the scheduling cell), and the corresponding PDSCH may be sent in cell #2 (i.e., the scheduled cell) (cross-carrier scheduling (CCS)). The scheduling cell (set) may be configured in a UE-specific, UE group-specific, or cell-specific manner. The scheduling cell includes a special cell (e.g., PCell).

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

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

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

[0118] Figure 7 is a diagram for explaining carrier aggregation. Figure 7In the example, it is assumed that three cells are aggregated. When CIF is disabled, each cell may only send a PDCCH that schedules its own PDSCH / PUSCH (self-carrier scheduling (SCS)). 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, cell A may send not only a PDCCH that schedules the PDSCH / PUSCH of cell A, but also a PDCCH that schedules the PDSCH / PUSCH of other cells (i.e., the scheduled cell) (cross-carrier scheduling (CCS)). In this case, the PDCCH that schedules its own cell is not sent in cell B / C.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0132] [Table 6]

[0133]

[0134] Multi-cell scheduling DCI

[0135] NR supports wide spectrum across various frequency ranges. The availability of 5G Advanced spectrum is expected to increase through the reallocation of frequency bands used in previous generations. In particular, for low-band FR1, available spectrum blocks tend to be further segmented and distributed. For FR2 bands and some FR1 bands, the available spectrum can be widened, so multiple carriers / cells need to operate within the band. Improvements in throughput and coverage are needed by using these distributed spectrum bands or wider bandwidth spectrum in a more energy-efficient and flexible manner.

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

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

[0138] Therefore, a control / processing method for configuring a field of a DCI (multi-cell DCI) for performing multi-cell scheduling as described above and a corresponding DCI size is proposed. For convenience, the multi-cell scheduling operation for PDSCH transmission is mainly described, but the operating principle of the proposed method can also be applied to multi-cell scheduling for PUSCH transmission. Hereinafter, the term "cell" may refer to the (active) BWP configured / indicated to the corresponding cell.

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

[0140] [1] Configuration of DCI fields for each scheduled cell in a multi-cell DCI

[0141] When a plurality of cells are scheduled through the same multi-cell DCI, corresponding DCI fields of the respective cells may be arranged / configured in the order of the cell indexes of the same DCI field.

[0142] For example, the DCI field of a cell with a lower cell index may be located / configured at a lower bit index (within the DCI).

[0143] A single DCI field (commonly applied to the cells belonging to the subgroup) may be configured for each cell subgroup including (single or) multiple cells, and in this case, the lowest cell index among the cells belonging to the respective subgroups may be compared, and the DCI field of the subgroup to which the lower cell index belongs may be located / configured at a lower bit index (within the DCI).

[0144] For example, in Fig.10 In the example, it is assumed that the multiple cells configured in the UE include cells A to M, the cell index of cell B is greater than the cell index of cell A, the cell index of cell C is greater than the cell index of cell B, and the cell index of cell M is greater than the cell index of cell C. First, referring to Fig.10 (a) of the present invention, bits of multiple cells may be included in one DCI field. In the DCI field, the bits may be arranged in the order of cell A, cell B, cell C, ..., cell M. Fig.10 (b), the DCI may include a DCI field X for each of the multiple cells. Within the DCI, the respective DCI fields X may be arranged in the order of cell A, cell B, cell C, ..., cell M. The fact that the bits / DCI fields of the lower indexed cells are placed before the bits / DCI fields of the higher indexed cells does not necessarily mean that the bits / DCI fields of the cells are located continuously, and the fields may be located discontinuously as long as the position priority / causality is maintained. For example, referring to Fig.10 (c) of the DCI, the DCI may include DCI fields X and Y of each of the multiple cells. Within the DCI, the respective DCI fields X and Y may be arranged in the order of DCI fields X and Y of cell A, DCI fields X and Y of cell B, DCI fields X and Y of cell C, ..., DCI fields X and Y of cell M, but the present disclosure is not limited thereto. For example, referring to Fig.10 In the embodiment of the present invention, the DCI may include DCI fields X and Y for each of the multiple cells. Within the DCI, the respective DCI fields X may be arranged in the order of cell A, cell B, cell C, ..., cell M, and then the respective DCI fields Y may be arranged in the order of cell A, cell B, cell C, ..., cell M (continuously and / or discontinuously). In one DCI, the application of (a) to (d) may be different for the corresponding DCI fields. For example, in one DCI, one of (a) to (d) may be applied to DCI field 1, and another of (a) to (d) may be applied to DCI field 2.

[0145] The DCI field may include, for example, but not limited to, at least one of an MCS field and / or an NDI field and / or an RV field and / or a HARQ process ID (HARQ ID) field.

[0146] The DCI field may include, but is not limited to, at least one of a frequency domain resource assignment / allocation (FDRA) field and / or a time domain RA (TDRA) field and / or a TPC (for PUSCH) field.

[0147] For example, the cell index may be a serving cell index or a cell index used when configuring a candidate cell combination for multi-cell DCI scheduling (in RRC configuration).

[0148] [2] (Maximum) payload size limit for multi-cell DCI

[0149] 1) Proposal 1

[0150] Regardless of the maximum number of TBs sent via a single PDSCH configured for each cell (for convenience, this is defined as N_t and may be configured as, for example, N_t=1 or N_t=2) and the number of cells scheduled via the same multi-cell DCI (for convenience, this is defined as N_c) or cell combination, the maximum value of the total number of TBs scheduled to multiple cells via a single multi-cell DCI may be limited to N_max or less (for example, N_max is configured by the BS or determined to be the maximum number of cells that can be scheduled by the multi-cell DCI or N_max=4).

[0151] For example, for (each of) the MCS and / or NDI and / or RV and / or HARQ ID fields, up to N_max fields may be configured in the multi-cell DCI.

[0152] For example, when the sum of N_t values ​​configured for each of N_c cells scheduled with the same multi-cell DCI exceeds the N_max value, the rule may be determined such that a total of N_max TBs are allocated / scheduled to the N_c cells in a manner of first cell index and then TB index.

[0153] For example, when N_c=3 and all three cells (index=0, 1, 2) have N_t=2 and N_max=4, 2 / 1 / 1 TBs may be allocated / scheduled to cell indexes 0 / 1 / 2, respectively.

[0154] For example, the cell index may be a serving cell index or a cell index used when configuring a candidate cell combination for multi-cell DCI scheduling (in RRC configuration).

[0155] 2) Proposal 2

[0156] When the number of cells scheduled through multi-cell DCI is L (e.g., L=1 or L=2) or less, up to N_t TBs may be configured for the corresponding cells, but when the number of cells scheduled through multi-cell DCI exceeds L, scheduling may be limited to only a single TB for all corresponding cells.

[0157] For example, the maximum number N_max of total TBs (scheduled to multiple cells) through a single multi-cell DCI may be determined as the maximum number of cells scheduled with the multi-cell DCI.

[0158] For example, for (each of) the MCS and / or NDI and / or RV and / or HARQ ID fields, up to N_max fields may be configured in the multi-cell DCI.

[0159] [3] Handling invalid cells with multi-cell DCI scheduling

[0160] 1) When an invalid cell is included among cells scheduled / indicated by multi-cell DCI, PDSCH / PUSCH transmission / reception may not be performed on the invalid cell, and PDSCH / PUSCH transmission / reception may be performed only on the remaining cells.

[0161] In this case, the DCI fields corresponding to the invalid cells in the multi-cell DCI (e.g., MCS, NDI, RV, HARQID, FDRA, TDRA, TPC (for PUSCH), antenna port, transmission configuration indication, SRS resource indicator, precoding information and number of layers, DMRS sequence initialization, PTRS-DMRS association, VRB to PRB mapping, PRB bundling size indicator, rate matching indicator, ZP CSI-RS trigger, SRS request, frequency hopping flag, channelAccess-CPext-CAPC (for PUSCH), open-loop power control parameter set indication and invalid symbol pattern indicator) may not be configured and may be omitted (i.e., only the DCI fields are configured sequentially for the remaining cells (according to the cell index value / order)), or the corresponding DCI fields may be based on a specific DL / UL BWP (e.g., the first active DL / UL BWP or the latest active DL / UL BWP specified via the parameters firstActiveDownlinkBWP / firstActiveUplinkBWP). The UE may be configured with the parameters / values ​​configured in the BWP (excluding dormant BWP)), or may be reserved with a predefined specific bit value, or the UE may be operable to ignore the corresponding field.

[0162] For example, when configuring the HARQ-ACK feedback payload corresponding to a multi-cell DCI, the HARQ-ACK bit corresponding to the invalid cell may be omitted (i.e., the HARQ-ACK bit may be configured in sequence only for the remaining cells (according to the cell index value / order)), or the corresponding HARQ-ACK bit may be configured for the invalid cell (according to the cell index value / order), but the corresponding bit may be mapped to NACK. For example, assuming that {cell A, cell B, cell C} are jointly scheduled through 1 DCI, and cell B is an invalid cell, the HARQ-ACK may be configured with {A / N of cell A (TB), A / N of cell C (TB) (and / or NACK of the remaining bits)}, or the HARQ-ACK may be configured with {A / N of cell A (TB), NACK of cell B (TB), A / N of cell C (TB)}.

[0163] An invalid cell is a deactivated Scell, a cell operating in a dormant BWP, a cell whose PDSCH (PUSCH) resources indicated by a multi-cell DCI temporally overlap with a semi-static UL (DL) symbol, a cell indicating frequency resources of the PDSCH (PUSCH) allocated by the multi-cell DCI in the form of an invalid value (e.g., in the form of a bitmap with all bits being "0" or in the form of an RIV (resource indication value) with all bits being "1"), a cell indicating time resources of the PDSCH (PUSCH) allocated by the multi-cell DCI in the form of an invalid value (e.g., in the form of an SLIV with all bits being "1"), a cell indicating TB disabled operation for all TBs (of the cell) by a multi-cell DCI, a cell operating in a DRX off state (without PDCCH monitoring), and / or a cell corresponding to a specific time period (or a specific BWP) for BS energy saving / power saving configuration / indication of a series of transmission and reception operations being stopped. For example, assuming that the resource allocation information (e.g., FDRA field) in the DCI is configured separately for each scheduled cell, a cell in which all bits of the resource allocation information are configured to 0 or 1 (i.e., invalid values ​​for resource allocation) may be an invalid cell (a cell that is not actually scheduled).

[0164] 2) In order to reduce the complexity of multi-cell DCI configuration and scheduling related operations, the following constraints may be imposed: the SCS used / applied to cells belonging to each cell combination (for convenience, referred to as a "co-scheduled cell set") that are simultaneously scheduled from the corresponding DCI need to all have the same value, and when the SCS used / applied between cells belonging to a specific co-scheduled cell set (active BWP configured / indicated for each corresponding cell) has different values, PDSCH / PUSCH transmission / reception may be performed only for cells that use / apply a specific (valid) SCS, and PDSCH / PUSCH transmission / reception may be omitted for cells that use / apply the remaining (invalid) SCS, and in this case, the cell that uses / applies the corresponding invalid SCS may correspond to an invalid cell (therefore, the DCI field and HARQ-ACK configuration method corresponding to the proposed invalid cell may be applied).

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

[0166] In another method, when the SCS used / applied among cells belonging to a specific co-scheduled cell set (active BWP configured / indicated for the corresponding cells) has different values, scheduling via multi-cell DCI may not be allowed for the co-scheduled cell set (the UE may not expect scheduling for the co-scheduled cell set), and therefore, the UE may omit DCI monitoring (blind decoding) of the PDCCH candidates (search space) configured for / corresponding to the co-scheduled cell set scheduling (DCI transmission).

[0167] [4] TB disabling for PDSCH scheduled with multi-cell DCI

[0168] 1) Existing operations

[0169] In the case of existing single-cell DCI-based scheduling, when the maximum number of TBs sent through one PDSCH is configured to be 2 (for example, 2 TB transmissions are scheduled through one PDSCH), if a combination of a specific MCS index (for example, 26) and a specific RV index (i.e., RV ID) (for example, 1) is indicated through DCI, the operation of disabling sending / receiving the corresponding specific TB index is specified.

[0170] 2) Proposed Operation

[0171] When multiple cells are scheduled through multi-cell DCI, a 1-bit RV can be used to indicate the RV index 0 or X (for example, X=2) for each cell (TB). When a single cell is scheduled through multi-cell DCI (assuming that corresponding scheduling can be performed), a 2-bit RV can be used to indicate the RV index 0 / 1 / 2 / 3 for the corresponding cell.

[0172] 3) Proposal 1

[0173] For multiple cells scheduled by the above-mentioned multi-cell DCI, the cells may be operated to receive the PDSCH while considering that a TB index indicating a combination of a specific MCS index Z (eg, Z=26) and an RV index X for each cell is disabled.

[0174] For the scheduled multiple cells, the cells may be operable to receive the PDSCH assuming that there is no TB disabling for the cells that do not meet the conditions.

[0175] 4) Proposal 2

[0176] For multiple cells scheduled by multi-cell DCI, when a combination of MCS index Z and RV index X is indicated for the same TB index for all cells (where N_t=2), the TB index may be considered disabled for all cells (where N_t=2) and operable to receive PDSCH.

[0177] This method may be applied only when all cells scheduled with multi-cell DCI are cells configured with N_t=2, or may be applied only to cells configured with N_t=2 among cells scheduled with multi-cell DCI.

[0178] For the scheduled multiple cells, the cells may be operable to receive the PDSCH assuming that there is no TB disabling for the cells that do not meet the conditions.

[0179] 5) Proposal 3

[0180] When only a single cell is scheduled through multi-cell DCI, the TB index indicated by the combination of MCS index Z and specific RV index Y (e.g., Y=1) is considered to be disabled (the same as before). When multiple cells are scheduled through multi-cell DCI, it can be assumed that there is no TB disabling at all times to receive PDSCH.

[0181] [5] Handling out-of-order operations related to multi-cell DCI scheduling

[0182] 1) Existing operations

[0183] First, the out-of-order PDSCH / PUSCH / PUCCH scheduling constraints defined in the current standard for single-cell scheduling are briefly described as follows.

[0184] -For two random HARQ IDs on the same cell, when a specific PDSCH #1 is scheduled by a specific PDCCH #1, the UE operates to not expect a situation where another PDSCH #2 whose start symbol is earlier than the end symbol of PDSCH #1 is scheduled by another PDCCH #2 whose end symbol is later than the end symbol of PDCCH #1 (this is conveniently referred to as PDSCH out-of-order or "PDSCH OOO").

[0185] -For two random HARQ IDs on the same cell, when a specific PUSCH #1 is scheduled by a specific PDCCH #1, the UE operates so as not to expect a case where another PUSCH #2 whose start symbol is earlier than the end symbol of PUSCH #1 is scheduled by another PDCCH #2 whose end symbol is later than the end symbol of PDCCH #1 (this is conveniently referred to as "PUSCH OOO").

[0186] -For a random cell, if HARQ-ACK feedback corresponding to a specific PDSCH #1 is indicated to be transmitted through a specific time slot #A, the UE operates so as not to expect a situation in which HARQ-ACK feedback corresponding to another PDSCH #2 starting later than PDSCH #1 is indicated to be transmitted through a time slot earlier than time slot #A (for convenience, this is referred to as "PUCCH OOO").

[0187] 2) Proposal

[0188] According to an embodiment, the proposed out-of-order PDSCH / PUSCH / PUCCH scheduling constraints related to multi-cell scheduling may include one of the following.

[0189] A. For multiple PDSCH#1s in multiple cells scheduled by the same multi-cell DCI PDCCH#1, the UE may be operated to not expect the relationship between the timing of the corresponding (multi-cell DCI) PDCCH#1 and PDSCH#1 on at least one of the multiple cells and the timing of other PDCCH#2 and PDSCH#2 to be scheduled to correspond to PDSCH OOO, and when scheduling is performed as described above so that the relationship corresponds to PDSCH OOO on at least one cell, the UE may discard / ignore the multi-cell DCI, and / or omit (skip) reception of multiple PDSCHs on multiple scheduled cells scheduled by the corresponding DCI. For example, with respect to multi-cell scheduling, PDSCH OOO is described as follows: when (i) at least one of DCI#1 and DCI#2 is multi-cell scheduled DCI, (ii) the last symbol of DCI#2 is located after the last symbol of DCI#1, (iii) DCI#1 schedules M PDSCH#1s {PDSCH#1-1, PDSCH#1-1,…, PDSCH#1-M} (on M cells), and (iv) DCI#2 schedules N PDSCH#2s {PDSCH#2-1, PDSCH#2-1,…, PDSCH#2-N} (on N cells), and the start symbol of any one of the N PDSCH#2s {PDSCH#2-1, PDSCH#2-1,…, PDSCH#2-N} is located before the last symbol of (any one of) M PDSCH#1s {PDSCH#1-1, PDSCH#1-1,…, PDSCH#1-M}, the relationship may correspond to PDSCH OOO. M and N may each be an integer greater than or equal to 1.

[0190] B. For multiple PUSCH #1s in multiple cells scheduled by the same multi-cell DCI PDCCH #1, the UE may be operated to not expect the relationship between the timing of the corresponding (multi-cell DCI) PDCCH #1 and PUSCH #1 on at least one of the multiple cells and the timing of other PDCCH #2 and PUSCH #2 to be scheduled to correspond to PUSCH OOO, and when scheduling is performed as described above so that the relationship corresponds to PUSCH OOO on at least one cell, the UE may discard / ignore the multi-cell DCI, and / or omit (skip) the transmission of multiple PUSCHs on multiple scheduled cells scheduled by the corresponding DCI. For example, with respect to multi-cell scheduling, PUSCH OOO is described as follows: when (i) at least one of DCI#1 and DCI#2 is multi-cell scheduled DCI, (ii) the last symbol of DCI#2 is located after the last symbol of DCI#1, (iii) DCI#1 schedules M PUSCH#1s {PUSCH#1-1, PUSCH#1-1,…, PUSCH#1-M} (on M cells), and (iv) DCI#2 schedules N PUSCH#2s {PUSCH#2-1, PUSCH#2-1,…, PUSCH#2-N} (on N cells), and the start symbol of any one of the N PUSCH#2s {PUSCH#2-1, PUSCH#2-1,…, PUSCH#2-N} is located before the last symbol of (any one of) M PUSCH#1s {PUSCH#1-1, PUSCH#1-1,…, PUSCH#1-M}, the relationship may correspond to PUSCH OOO. M and N may each be an integer greater than or equal to 1.

[0191] C. For multiple PDSCH#1 on multiple cells scheduled by the same multi-cell DCI, the UE may operate to not expect the relationship between the timing of HARQ-ACK corresponding to the corresponding PDSCH#1 on at least one of the corresponding multiple cells and the timing of HARQ-ACK corresponding to other PDSCH#2 to be scheduled corresponding to PUCCH OOO, and when the relationship is scheduled corresponding to PUCCH OOO on at least one cell as described above, the UE may discard / ignore the multi-cell DCI and / or skip the reception of multiple PDSCHs on multiple cells scheduled by the corresponding DCI and / or abandon the HARQ-ACK transmission of multiple PDSCHs on multiple cells scheduled by the corresponding DCI. PDSCH#2 may be related to multi-cell scheduling DCI, or may be related to single-cell scheduling DCI. i) For example, assuming that M PDSCH#1s {PDSCH#1-1, PDSCH#1-2,..., PDSCH#1-M} (M is an integer greater than or equal to 1), N PDSCH#2s {PDSCH#2-1, PDSCH#2-2,..., PDSCH#2-N} (N is an integer greater than or equal to 1) are scheduled via multi-cell scheduling DCI#1, and at least one of the N PDSCH#2s starts later than at least one of the M PDSCH#1s, then the situation in which the time slot for HARQ-ACK of the N PDSCH#2s is before the time slot for HARQ-ACK of the M PDSCH#1s may correspond to PUCCH OOO. ii) As another example, assuming that M PDSCH#1s {PDSCH#1-1, PDSCH#1-2, ..., PDSCH#1-M} (M is an integer greater than or equal to 1) are scheduled via multi-cell scheduling DCI#1, PDSCH#2 is scheduled via single-cell scheduling DCI#2, and PDSCH#2 starts later than at least one of the M PDSCH#1s, the case where the time slot for HARQ-ACK of PDSCH#2 is before the time slot for HARQ-ACK of M PDSCH#1s may correspond to PUCCH OOO. iii) As another example, assuming that M PDSCH#1s {PDSCH#1-1, PDSCH#1-2, ..., PDSCH#1-M} (M is an integer greater than or equal to 1) are scheduled via multi-cell scheduling DCI#1, PDSCH#2 is scheduled via single-cell scheduling DCI#2, and at least one of the M PDSCH#1s starts later than PDSCH#2, then the situation in which the time slot for HARQ-ACK of the M PDSCH#1s is before the time slot for HARQ-ACK of PDSCH#2 may correspond to PUCCH OOO.

[0192] [6] DL SPS / ULCG activation / release ( / retransmission) operation based on multi-cell DCI

[0193] 1) When sending / receiving multi-cell DCI based on the configuration scheduling (CS)-RNTI (and the scrambling applied thereto), for multiple cells indicated by the corresponding DCI (having a specific (e.g., CIF or new) field in the corresponding DCI), the combination of specific fields corresponding to each cell (e.g., HARQ process ID, RV, MCS, all or part of the frequency domain resource assignment) can be checked (verified) to meet the SPS / CG-related activation and / or release (and / or retransmission) indication conditions (refer to Section 10.2 of 3GPP TS 38.213V16.2.0), and based on this, the UE can perform the indicated (verified) operations for each cell.

[0194] For example, the SPS / CG enabling operation may be indicated only for all (all or some) of the multiple cells indicated by the same (CS-RNTI-based) multi-cell DCI, the SPS / CG releasing operation may be indicated only for all (all or some) of the multiple cells, or the SPS / CG enabling operation may be indicated for specific cells among the corresponding multiple cells (all or some) and the SPS / CG releasing operation may be indicated for other cells.

[0195] Alternatively, it may be specified that the SPS / CG enabling operation is indicated only for all (all or some) cells indicated via the same (CS-RNTI-based) multi-cell DCI, or that the SPS / CG releasing operation is indicated only for all (all or some) cells.

[0196] 2) Alternatively, it may be specified that SPS / CG-related activation and / or release (and / or retransmission) indication (for the corresponding cell) can only be performed when only one cell is indicated by the (CS-RNTI-based) multi-cell DCI, and when multiple cells are indicated by the corresponding multi-cell DCI, SPS / CG-related activation and / or release (and / or retransmission) indications are not allowed (all), or only SPS / CG-related retransmission scheduling is allowed (activation and / or release indications are not allowed).

[0197] For a specific cell combination (including multiple cells) indicated / scheduled by multi-cell DCI, when CS-RNTI (i.e., SPS / CG) is configured for some cells belonging to the corresponding cell combination (for convenience, referred to as "cells with CS-RNTI"), and CS-RNTI (i.e., SPS / CG) is not configured for the remaining cells (for convenience, referred to as "cells without CS-RNTI"),

[0198] Option 1) When a specific cell combination is indicated by a CS-RNTI-based multi-cell DCI, transmission and reception operations are performed assuming that there is no PDSCH / PUSCH scheduling for cells without CS-RNTI, or

[0199] Option 2) For a specific cell combination, only indication / scheduling via C-RNTI-based multi-cell DCI may be performed / permitted (indication / scheduling via CS-RNTI-based multi-cell DCI may not be performed / permitted).

[0200] [7] Determine and limit the (maximum) payload size of multi-cell DCI

[0201] For each of all cell combinations scheduled by DCI (for each cell combination), when each sum value is the sum of the sizes of each field of the corresponding cell combination (each field corresponding to each cell within the corresponding cell combination), the (maximum) payload size of the multi-cell DCI may be determined as the maximum value among the sum values. As a specific example, refer to Fig.11 , assuming that a total of N cells from cell #1 to cell #N are configured in the UE, and there are M cell combinations to be jointly scheduled through multi-cell scheduling DCI. For example, M cell combinations may be configured by the BS to the UE. Assume that the bits of all DCI fields required for scheduling in case 1 are (at least) A bits in total, the bits of all DCI fields required for scheduling in case 2 are (at least) B bits in total, the bits of all DCI fields required for scheduling in case 3 are (at least) C bits in total, and the bits of all DCI fields required for scheduling in case M are (at least) K bits in total. The payload of the multi-cell scheduling DCI may be configured based on Max{A,B,C,...,K} bits to cover cases 1 to M. For example, the payload of the multi-cell scheduling DCI may be configured to be equal to or greater than Max{A,B,C,...,K} bits.

[0202] The UE may not expect / assume that the payload size of the multi-cell DCI determined as described above is configured (e.g., a combination of transmission parameters of the cell and / or each cell used to schedule the multi-cell DCI) to exceed the maximum number of bits N (e.g., N=140) for applying / supporting a specific coding scheme (e.g., polar code), and when this occurs, the UE may not perform monitoring / decoding operations on the multi-cell DCI, or may perform monitoring / decoding operations on the DCI while adjusting the payload size of the DCI to the number of bits N by removing certain bits configured / configured in the DCI (e.g., a field corresponding to a high index).

[0203] Fig.12 An example implementation of signal reception of a UE based on at least some of the above embodiments is shown. Even if there is no separate description, reference can be made to the contents of the previous description to help understand Fig.12 .

[0204] Reference Fig.12 , the UE may monitor physical downlink control channel (PDCCH) candidates (1205).

[0205] The UE may detect a downlink control channel (DCI) through monitoring of PDCCH candidates (1210).

[0206] DCI can support multi-cell scheduling based on a cell combination of multiple cells configured in the UE. The payload size of DCI can be determined based on the first cell combination with the largest total number of bits required for scheduling cells among the cell combinations.

[0207] The payload of the DCI may be determined based on the sum size of all DCI fields of the first cell combination.

[0208] The co-scheduled cell through DCI may be indicated as one of the cell combination. The DCI may include information indicating one of the cell combination.

[0209] The DCI may include first DCI field related information for each of the first cell and the second cell for co-scheduling. Based on the first cell having a lower serving cell index than the second cell, in the DCI, the first DCI field related information of the first cell may be located before the first DCI field related information of the second cell. For example, the first DCI field may include (but is not limited to) at least one of a modulation and coding scheme (MCS) field, a new data indicator (NDI) field, a redundant version (RV) field, a hybrid automatic repeat request (HARQ) process ID field, a frequency domain resource allocation (FDRA) field, a time domain resource allocation (TDRA) field, and a transmission power command (TPC) field of a physical uplink shared channel (PUSCH).

[0210] The sending (e.g., PUSCH for UL grant DCI) or receiving (e.g., PDSCH for DL ​​grant DCI) of scheduling signals may be performed only for the remaining cells except for at least one invalid cell among the cells jointly scheduled by DCI. The at least one invalid cell may include, but is not limited to, at least one of a deactivated secondary cell (SCell), a cell operating as a dormant bandwidth part (BWP), a cell in which resources allocated by DCI overlap with semi-static resources configured differently in uplink (UL) / downlink (DL) directions, and a cell in which frequency resource information indicated by DCI is invalid. For example, assuming that the DCI is a DL grant DCI that schedules PDSCH, hybrid automatic repeat request-acknowledgement (HARQ-ACK) information for PDSCH may be configured for the remaining cells except for at least one invalid cell, or may be configured to include negative acknowledgement (NACK) information for at least one invalid cell. The DCI field value for at least one invalid cell in the DCI may be configured based on information of a specific bandwidth part (BWP).

[0211] Fig.13An example implementation of signal transmission of a BS based on at least some of the above embodiments is shown. Even if there is no separate description, reference can be made to the previous description to help understand Fig.13 .

[0212] Reference Fig.13 , the BS may generate downlink control information (DCI) (1305).

[0213] The BS may send DCI to the UE based on at least one physical downlink control channel (PDCCH) candidate of the UE (1310).

[0214] The DCI may support multi-cell scheduling based on a cell combination of multiple cells configured for the UE. The DCI payload size may be determined based on a first cell combination having the largest total number of DCI bits required for co-scheduled cells among the cell combinations.

[0215] The payload of the DCI may be determined based on the sum size of all DCI fields of the first cell combination.

[0216] The co-scheduled cell through DCI may be indicated as one of the cell combination. The DCI may include information indicating one of the cell combination.

[0217] The DCI may include first DCI field related information for each of the first cell and the second cell for co-scheduling. Based on the first cell having a lower serving cell index than the second cell, in the DCI, the first DCI field related information of the first cell may be located before the first DCI field related information of the second cell. For example, the first DCI field may include (but is not limited to) at least one of a modulation and coding scheme (MCS) field, a new data indicator (NDI) field, a redundant version (RV) field, a hybrid automatic repeat request (HARQ) process ID field, a frequency domain resource allocation (FDRA) field, a time domain resource allocation (TDRA) field, and a transmission power command (TPC) field of a physical uplink shared channel (PUSCH).

[0218] Reception (e.g., PUSCH for UL grant DCI) or transmission (e.g., PDSCH for DL ​​grant DCI) of scheduling signals may be performed only for the remaining cells except for at least one invalid cell among the cells co-scheduled by DCI. The at least one invalid cell may include, but is not limited to, at least one of a deactivated secondary cell (SCell), a cell operating as a dormant bandwidth part (BWP), a cell in which resources allocated by DCI overlap with semi-static resources configured differently in uplink (UL) / downlink (DL) directions, and a cell in which frequency resource information indicated by the DCI is invalid. For example, assuming that the DCI is a DL grant DCI that schedules PDSCH, hybrid automatic repeat request-acknowledgement (HARQ-ACK) information for the PDSCH may be configured for the remaining cells except for at least one invalid cell, or may be configured to include negative acknowledgement (NACK) information for at least one invalid cell. The DCI field value for at least one invalid cell in the DCI may be configured based on information of a specific bandwidth part (BWP).

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

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

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

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

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

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

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

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

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

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

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

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

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

[0232] Reference Fig.16 , the wireless devices 100 and 200 may correspond to Fig.15The wireless devices 100 and 200 of the present invention may be configured by various elements, components, units / parts and / or modules. For example, each of the wireless devices 100 and 200 may include a communication unit 110, a control unit 120, a memory unit 130 and an additional component 140. The communication unit may include a communication circuit 112 and a transceiver 114. For example, the communication circuit 112 may include Fig.15 One or more processors 102 and 202 and / or one or more memories 104 and 204. For example, the transceiver 114 may include Fig.15 The control unit 120 is electrically connected to the communication unit 110, the memory 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.

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

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

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

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

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

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

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

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

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

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

[0243] [Table 7]

[0244]

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

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

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

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

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

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

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

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

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

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

[0255] Industrial Applicability

[0256] 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 The following steps are involved: Monitoring physical downlink control channel PDCCH candidates; as well as Detecting downlink control information DCI by monitoring the PDCCH candidates, wherein the DCI supports multi-cell scheduling based on a cell combination of multiple cells configured for the UE, and The effective load size of the DCI is determined based on the first cell combination having the largest total number of DCI bits required by the co-scheduled cells among the cell combinations.

2. The method according to claim 1, in, The payload of the DCI is determined based on the total size of all DCI fields of the first cell combination.

3. The method according to claim 1, in, The cell co-scheduled by the DCI is indicated as one of the cell combinations.

4. The method according to claim 1, in, The DCI includes first DCI field related information of each of the co-scheduled first cell and the second cell, and Wherein, based on the fact that the first cell has a lower serving cell index than the second cell, in the DCI, the first DCI field related information of the first cell is located before the first DCI field related information of the second cell.

5. The method according to claim 4, in, The first DCI field includes at least one of a modulation and coding scheme MCS field for a physical uplink shared channel PUSCH, a new data indicator NDI field, a redundant version RV field, a hybrid automatic repeat request HARQ process ID field, a frequency domain resource allocation FDRA field, a time domain resource allocation TDRA field, or a transmission power command TPC field.

6. The method according to claim 1, in, Transmission or reception of a scheduling signal is performed only for remaining cells except for at least one invalid cell among cells jointly scheduled by the DCI.

7. The method according to claim 6, in, The at least one invalid cell includes at least one of a deactivated secondary cell SCell, a cell operating as a dormant bandwidth part BWP, a cell in which resources allocated by the DCI overlap with semi-static resources configured differently in uplink UL / downlink DL directions, and a cell in which frequency resource information indicated by the DCI is invalid.

8. The method according to claim 6, in, The hybrid automatic repeat request-acknowledgement HARQ-ACK information is configured for the remaining cells except the at least one invalid cell or is configured to include negative acknowledgement NACK information for the at least one invalid cell.

9. The method according to claim 6, in, The DCI field value for the at least one invalid cell in the DCI is configured based on information of a specific bandwidth part BWP. 10 . A computer-readable recording medium having recorded thereon a program for executing the method according to claim 1 .

11. A device for wireless communication, the device include: a memory configured to store instructions; as well as a processor configured to perform operations by executing the instructions, The operation of the processor includes monitoring a physical downlink control channel (PDCCH) candidate and detecting downlink control information (DCI) by monitoring the PDCCH candidate. The DCI supports multi-cell scheduling based on a cell combination of multiple cells configured for a user equipment UE, and The effective load size of the DCI is determined based on the first cell combination having the largest total number of DCI bits required by the co-scheduled cells among the cell combinations.

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

13. The device according to claim 11, in, The device includes an application specific integrated circuit ASIC or a digital signal processing device for controlling the UE.

14. A method for sending a signal by a base station BS in a wireless communication system, the method The following steps are involved: Generate downlink control information DCI; as well as sending the DCI to a user equipment UE based on at least one physical downlink control channel (PDCCH) candidate of the UE, wherein the DCI supports multi-cell scheduling based on a cell combination of multiple cells configured for the UE, and The effective load size of the DCI is determined based on the first cell combination having the largest total number of DCI bits required by the co-scheduled cells among the cell combinations.

15. A base station BS for transmitting a signal in a wireless communication system, the BS include: Transceiver; as well as a processor configured to generate downlink control information DCI and send the DCI to a user equipment UE based on at least one physical downlink control channel PDCCH candidate of the UE through the transceiver, wherein the DCI supports multi-cell scheduling based on a cell combination of multiple cells configured for the UE, and The effective load size of the DCI is determined based on the first cell combination having the largest total number of DCI bits required by the co-scheduled cells among the cell combinations.