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

Abstract

According to at least one of various embodiments of the present invention, a terminal monitors physical downlink control channel (PDCCH) candidates and detects downlink control information (DCI) by monitoring the PDCCH candidates, the DCI supporting multi-cell scheduling based on a plurality of cells configured in the terminal, and the DCI including a DCI field configured commonly for co-scheduled cells.

Description

[Technical field]

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

[0002] Wireless communication systems have been widely deployed to provide various communication services such as voice and data. In general, wireless communication systems are multiple access systems that can support communication with multiple users by sharing available system resources (bandwidth, transmission power, etc.). Examples of multiple access systems include code division multiple access (CDMA) systems, frequency division multiple access (FDMA) systems, time division multiple access (TDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, and single carrier frequency division multiple access (SC-FDMA) systems. Summary of the Invention [Problem to be solved by the invention]

[0003] The technical problem to be solved is to provide a method and an apparatus for efficiently performing a process of transmitting and receiving a radio signal.

[0004] The technical problem to be achieved is not limited thereto, and other technical problems not mentioned will be clearly understood by those having ordinary skill in the art to which the present invention pertains from the following description. [Means for solving the problem]

[0005] According to an aspect of the present invention, a method for a terminal receiving a signal in a wireless communication system includes monitoring physical downlink control channel (PDCCH) candidates and detecting downlink control information (DCI) through monitoring of the PDCCH candidates. The DCI may support multi-cell scheduling based on a plurality of cells configured in the UE. The DCI may include a first DCI field commonly configured for co-scheduled cells.Based on that the plurality of serving cells include a first cell and a second cell, and that a configuration related to a size of the first DCI field is M-bit for scheduling of the first cell and N-bit for scheduling of the second cell, respectively: the size of the first DCI field commonly configured for the co-scheduled cells may be determined as a lager one of the M-bit and the N-bit.

[0006] The first DCI field includes at least one of a field related to antenna port information, a field related to SRS (sounding reference signal) resource information, a field related to information related to precoding and number of layers, a field related to beta offset information, an OLPC (Open-loop power control parameter set indication) field, and a field related to information related to channel access and CP (cyclic prefix).

[0007] The first DCI field indicates one codepoint common to the co-scheduled cells, the indicated one codepoint and the mapped parameters are configured separately for each of the co-scheduled cells, and a table providing the mapped parameters for each scheduled cell for each codepoint in the first DCI field is configured in the terminal.

[0008] The size of the first DCI field is determined based on the cell among the plurality of cells that has the largest setting regarding the size of the first DCI field.

[0009] The DCI includes a second DCI field that is applied to a reference cell of any one of the co-scheduled cells.

[0010] The reference cell is the cell having the smallest serving cell index among the co-scheduled cells.

[0011] The second DCI field includes a channel state information (CSI) request field.

[0012] The terminal obtains CSI for the CSI request field based on channel state information-reference signal (CSI-RS) information for the reference cell having the smallest serving cell index among the co-scheduled cells.

[0013] The terminal transmits a CSI report related to the CSI request field via a physical uplink shared channel (PUSCH) on the reference cell having the smallest serving cell index among the co-scheduled cells.

[0014] According to another aspect of the present invention, there is provided a processor-readable recording medium having a program recorded thereon for carrying out the above-described method.

[0015] According to another aspect, there is provided a terminal for performing the above-mentioned method.

[0016] According to yet another aspect, there is provided an apparatus for controlling a terminal to perform the method described above.

[0017] According to one aspect, a method for transmitting a signal by a base station in a wireless communication system includes generating downlink control information (DCI) and transmitting the DCI to a terminal based on at least one of physical downlink control channel (PDCCH) candidates of the terminal. The DCI supports multi-cell scheduling based on a plurality of cells configured for the terminal. The DCI includes a first DCI field configured in common for co-scheduled cells. The plurality of cells include a first cell and a second cell, and a size of the first DCI field configured in common for the co-scheduled cells is determined by the larger of the M-bits and the N-bits based on the plurality of cells including a first cell and a second cell, and a setting regarding a size of the first DCI field is M-bits for the scheduling of the first cell and N-bits for the scheduling of the second cell.

[0018] According to yet another aspect of the present invention, there is provided a base station for performing the above-mentioned method. Effect of the Invention

[0019] According to at least one of various embodiments, it is possible to efficiently transmit and receive radio signals in a wireless communication system.

[0020] The effects obtained by the present invention are not limited to those mentioned above, and other effects not mentioned will be clearly understood by those having ordinary skill in the art to which the present invention pertains from the following description. [Brief description of the drawings]

[0021] [Figure 1] 1 is a diagram illustrating physical channels used in a 3GPP (registered trademark) system, which is an example of a wireless communication system, and a general signal transmission method using these channels.

[0022] [Diagram 2] FIG. 1 illustrates a structure of a radio frame.

[0023] [Diagram 3] FIG. 2 illustrates a resource grid of slots.

[0024] [Figure 4] A diagram showing an example of mapping physical channels within a slot.

[0025] [Diagram 5] A diagram illustrating a PDCCH / PDSCH reception and ACK / NACK transmission process.

[0026] [Figure 6] FIG. 1 illustrates a PUSCH (Physical Uplink Shared Channel) transmission process.

[0027] [Figure 7] FIG. 2 illustrates an example of carrier merging.

[0028] [Figure 8] FIG. 1 illustrates a wireless communication system that supports unlicensed bands.

[0029] [Figure 9]FIG. 1 illustrates a method for occupying resources in an unlicensed spectrum.

[0030] [Figure 10] A diagram to explain a specific type of field in a multi-cell scheduling DCI according to one embodiment.

[0031] [Figure 11] A diagram to explain a CSI request field in a multi-cell scheduling DCI according to one embodiment.

[0032] [Figure 12] A diagram to explain size setting of a specific type of field in a multi-cell scheduling DCI according to one embodiment.

[0033] [Figure 13] 1 is a diagram illustrating a method for a terminal to receive a signal according to one embodiment.

[0034] [Figure 14] 1 is a diagram illustrating a method in which a base station transmits a signal according to one embodiment.

[0035] [Figure 15-18] 1 is a diagram illustrating a communication system 1 and wireless devices applicable to the present invention.

[0036] [Figure 19] FIG. 2 is a diagram illustrating a DRX (Discontinuous Reception) operation applicable to the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0037] The following technologies can be used for various wireless access systems such as code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), etc. CDMA can be implemented by radio technologies such as Universal Terrestrial Radio Access (UTRA) and CDMA2000. TDMA can be implemented by radio technologies such as Global System for Mobile communications (GSM) / General Packet Radio Service (GPRS) / Enhanced Data Rates for GSM Evolution (EDGE). OFDMA can be implemented by radio technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, Evolved UTRA (E-UTRA), etc. UTRA is part of the Universal Mobile Telecommunications System (UMTS). 3GPP (3rd Generation Partnership Project) LTE (long term evolution) is part of E-UMTS (Evolved UMTS) that uses E-UTRA, and LTE-A is an evolution of 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is an evolution of 3GPP LTE / LTE-A.

[0038] As more communication devices require larger communication capacity, the need for improved mobile broadband (eMBB) communication compared to existing radio access technology (RAT) is emerging. In addition, large-scale MTC (massive machine type communications), which connects multiple devices and objects to provide various services anytime and anywhere, is one of the important issues to be considered in next-generation communications. In addition, URLLC (Ultra-Reliable and Low Latency Communication) considering reliability and latency-sensitive services / UEs is being discussed. Thus, the introduction of next-generation RATs considering eMBB (enhanced mobile broadband communication), large-scale MTC, URLLC (Ultra-Reliable and Low Latency Communication), etc. is being discussed, and for convenience, the relevant technology is referred to as NR (New radio or New RAT) in this specification.

[0039] For clarity of explanation, 3GPP NR will be mainly described, but the technical idea of ​​the present invention is not limited thereto.

[0040] In this specification, the term "setting" may be replaced with the term "configure / configuration", and the two terms may be used interchangeably. Conditional expressions (e.g., "if", "in a case", or "when") may be replaced with expressions such as "based on that" or "in a state / status". The operation or SW / HW configuration of a terminal / base station due to the satisfaction of the relevant condition may be inferred / understood. In addition, in signal transmission / reception between wireless communication devices (e.g., base station, terminal), if the process of the receiving (or transmitting) side can be inferred / understood from the process of the transmitting (or receiving) side, the explanation may be omitted. For example, the signal determination / generation / encoding / transmission of the transmitting side can be understood as the signal monitoring reception / decoding / determination of the receiving side. In addition, an expression that a terminal performs (or does not perform) a specific operation may also be interpreted as the base station operating while expecting / assuming (or expecting / assuming not to perform) the specific operation of the terminal. The expression that the base station performs (or does not perform) a specific operation can also be interpreted as the terminal expecting / assuming (or expecting / assuming not to perform) the execution of a specific operation of the base station. In addition, in the following description, the divisions and indexes of each section, embodiment, example, option, method, solution, etc. are for convenience of explanation and should not be interpreted as meaning that each necessarily constitutes an independent invention or that each necessarily must be implemented individually. In addition, in describing each section, embodiment, example, option, method, solution, etc., unless there is an explicitly conflicting / opposing technology, it is inferred / interpreted that at least some of them may be combined and implemented together, or at least some may be omitted and implemented.

[0041] In a wireless communication system, a terminal receives information from a base station through a downlink (DL), and transmits information from the base station through an uplink (UL). Information transmitted and received between the base station and the terminal includes data and various control information, and various physical channels exist depending on the type / purpose of the information transmitted and received.

[0042] FIG. 1 is a diagram illustrating physical channels used in a 3GPP NR system and a typical signal transmission method using these channels.

[0043] A terminal that has been turned on in a power-off state or that has newly entered a cell performs an initial cell search operation such as establishing synchronization with a base station in step S101. To this end, the terminal receives a synchronization signal block (SSB) from the base station. The SSB includes a primary synchronization signal (PSS), a secondary synchronization signal (SSS) and a physical broadcast channel (PBCH). The terminal establishes synchronization with the base station based on the PSS / SSS and obtains information such as a cell identity (cell ID). The terminal also obtains broadcast information within the cell based on the PBCH. In addition, the terminal can receive a downlink reference signal (DL RS) during the initial cell search stage to check the state of the downlink channel.

[0044] After completing the initial cell search, in step S102, the terminal receives a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) based on information of the physical downlink control channel to obtain more specific system information.

[0045] Thereafter, the terminal performs a random access procedure such as steps S103 to S106 to complete connection to the base station. To this end, the terminal transmits a preamble through a physical random access channel (PRACH) (S103) and receives a response message to the preamble through a physical downlink control channel and a corresponding physical downlink shared channel (S104). In the case of contention based random access, the terminal performs a contention resolution procedure such as transmitting a further physical random access channel (S105) and receiving a physical downlink control channel and a corresponding physical downlink shared channel (S106).

[0046] After performing this procedure, the terminal then receives a physical downlink control channel / physical downlink shared channel (S107) and transmits a physical uplink shared channel (Physical Uplink Shared Channel, PUSCH) / physical uplink control channel (Physical Uplink Control Channel, PUCCH) as a general uplink / downlink signal transmission procedure (S108). The control information transmitted by the terminal to the base station is collectively referred to as uplink control information (UCI). UCI includes HARQ ACK / NACK (Hybrid Automatic Repeat and reQuest Acknowledgement / Negative-ACK), SR (Scheduling Request), CSI (Channel State Information), etc. CSI includes CQI (Channel Quality Indicator), PMI (Precoding Matrix Indicator), RI (Rank Indication), etc. UCI is generally transmitted via PUCCH, but when control information and traffic data need to be transmitted simultaneously, it is transmitted via PUSCH. In addition, UCI can be transmitted aperiodically via PUSCH upon request / instruction from the network.

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

[0048] FIG. 2 illustrates the structure of a radio frame. In NR, uplink and downlink transmissions are composed of frames. A radio frame has a length of 10 ms and is defined as two 5 ms half-frames (HF). A half-frame is defined as five 1 ms subframes (SF). A subframe is divided into one or more slots, and the number of slots in a subframe depends on the subcarrier spacing (SCS). Each slot contains 12 or 14 OFDM(A) symbols depending on the cyclic prefix (CP). If a general CP is used, each slot contains 14 symbols. If an extended CP is used, each slot contains 12 symbols.

[0049] Table 1 illustrates that the number of symbols per slot, the number of slots per frame, and the number of slots per subframe change depending on the SCS when a general CP is used.

[0050] [Table 1]

[0051] *N slot symb :Number of symbols in the slot

[0052] *N frame,u slot : Number of slots in the frame

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

[0054] Table 2 illustrates that the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary with the SCS when an extended CP is used.

[0055] [Table 2]

[0056] The frame structure is exemplary only, and the number of subframes, slots, and symbols within a frame can vary.

[0057] In the NR system, OFDM numerology (e.g., SCS) can be set to be different between multiple cells merged into one terminal. Accordingly, the (absolute time) duration of time resources (e.g., SF, slot, or TTI) (for convenience, commonly referred to as TU (Time Unit)) consisting of the same number of symbols can be set to be different between the merged cells. Here, the symbols include OFDM symbols (or CP-OFDM symbols) and SC-FDMA symbols (or Discrete Fourier Transform-spread-OFDM, DFT-s-OFDM symbols).

[0058] FIG. 3 is a diagram illustrating a resource grid of a slot. A slot includes a number of symbols in the time domain. For example, in the case of a general CP, one slot includes 14 symbols, while in the case of an extended CP, one slot includes 12 symbols. A carrier includes a number of subcarriers in the frequency domain. A resource block (RB) is defined as a number of (e.g., 12) consecutive subcarriers in the frequency domain. A BWP is defined as a number of consecutive physical RBs (PRBs) in the frequency domain and can correspond to one numerology (e.g., SCS, CP length, etc.). A carrier includes up to N (e.g., 5) BWPs. Data communication is performed in an activated BWP, and only one BWP is activated for one terminal. In the resource grid, each element is called a resource element (RE), and one complex symbol can be mapped to it.

[0059] Figure 4 is a diagram showing an example of mapping physical channels within a slot. PDCCH is transmitted in the DL control region, and PDSCH is transmitted in the DL data region. PUCCH is transmitted in the UL control region, and PUSCH is transmitted in the UL data region. GP provides a time gap when the base station and the terminal switch from a transmission mode to a reception mode or from a reception mode to a transmission mode. Some symbols at the time of switching from DL to UL within a subframe can be set as GP.

[0060] Each physical channel is described in more detail below.

[0061] The PDCCH carries Downlink Control Information (DCI). For example, the PCCCH (i.e., DCI) carries the transmission format and resource allocation of the DL-SCH (downlink shared channel), resource allocation information for the UL-SCH (uplink shared channel), paging information for the PCH (paging channel), system information on the DL-SCH, resource allocation information for higher layer control messages such as voluntary access responses transmitted on the PDSCH, transmission power control commands, activation / deactivation of configured scheduling (CS), etc. The DCI includes a cyclic redundancy check (CRC), and the CRC is masked / scrambled to various identifiers (e.g., Radio Network Temporary Identifier, RNTI) depending on the owner or use of the PDCCH. For example, if the PDCCH is for a specific terminal, the CRC is masked to a terminal identifier (e.g., cell-RNTI, C-RNTI). If the PDCCH is for paging, the CRC is masked to a P-RNTI (Paging-RNTI). If the PDCCH is for system information (e.g., System Information Block, SIB), the CRC is masked with a System Information RNTI (SI-RNTI). If the PDCCH is for an unsolicited access response, the CRC is masked with a Random Access-RNTI (RA-RNTI).

[0062] The PDCCH is composed of 1, 2, 4, 8, or 16 CCEs (Control Channel Elements) depending on the AL (Aggregation Level). A CCE is a logical allocation unit used to provide a PDCCH with a predetermined code rate according to the radio channel condition. A CCE is composed of 6 REGs (Resource Element Groups). A REG is defined by one OFDM symbol and one (P)RB. The PDCCH is transmitted by a CORESET (Control Resource Set). A CORESET is defined by a set of REGs having a given neurology (e.g., SCS, CP length, etc.). Multiple CORESETs for one UE can be overlapped in the time / frequency domain. A CORESET is set by system information (e.g., Master Information Block, MIB) or UE-specific higher layer (e.g., Radio Resource Control, RRC, layer) signaling. Specifically, the number of RBs and the number of OFDM symbols (maximum 3) constituting a CORESET are set by higher layer signaling.

[0063] For PDCCH reception / detection, the terminal monitors PDCCH candidates. PDCCH candidates indicate the CCEs that the terminal monitors for PDCCH detection. Each PDCCH candidate is defined by 1, 2, 4, 8, or 16 CCEs depending on the AL. Monitoring includes (blind) decoding the PDCCH candidates. The set of PDCCH candidates that the terminal monitors is defined as a PDCCH search space (SS). The search space includes a common search space (CSS) or a UE-specific search space (USS). The terminal can obtain DCI by monitoring PDCCH candidates in one or more search spaces configured by MIB or higher layer signaling. Each CORESET is associated with one or more search spaces, and each search space is associated with one COREST. The search space is defined based on the following parameters:

[0064] - controlResourceSetId: Indicates the CORESET associated with the search space.

[0065] - monitoringSlotPeriodicityAndOffset: indicates the PDCCH monitoring period (in slots) and the PDCCH monitoring period offset (in slots).

[0066] - monitoringSymbolsWithinSlot: indicates the PDCCH monitoring symbols within the slot (e.g. indicates the first symbol of the SORESET).

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

[0068] *An opportunity (e.g., time / frequency resource) for monitoring a PDCCH candidate is defined as a PDCCH (monitoring) opportunity. One or more PDCCH (monitoring) opportunities are configured within a slot.

[0069] Table 3 illustrates the characteristics of each search space type.

[0070] [Table 3]

[0071] Table 4 illustrates an example of a DCI format transmitted via the PDCCH.

[0072] [Table 4]

[0073] DCI format 0_0 is used to schedule a TB-based (or TB-level) PUSCH, and DCI format 0_1 ​​is used to schedule a TB-based (or TB-level) PUSCH or a Code Block Group (CBG)-based (or CBG-level) PUSCH. DCI format 1_0 is used to schedule a TB-based (or TB-level) PDSCH, and DCI format 1_1 is used to schedule a TB-based (or TB-level) PDSCH or a CBG-based (or CBG-level) PDSCH. DCI format 0_0 / 0_1 is called UL grant DCI or UL scheduling information, and DCI format 1_0 / 1_1 is called DL grant DCI or DL ​​scheduling information. DCI format 2_0 is used to deliver dynamic slot format information (e.g., dynamic SFI) to a terminal, and DCI format 2_1 is used to deliver downlink pre-Emption information to a terminal. DCI format 2_0 and / or DCI format 2_1 are transmitted to terminals in a corresponding group via a group common PDCCH, which is a PDCCH transmitted to terminals defined in one group.

[0074] DCI format 0_0 and DCI format 1_0 are called fallback DCI formats, and DCI format 0_1 ​​and DCI format 1_1 are called non-fallback DCI formats. The fallback DCI format maintains the same DCI size / field configuration regardless of the terminal settings. On the other hand, the non-fallback DCI format has a different DCI size / field configuration depending on the terminal settings.

[0075] PDSCH carries downlink data (e.g. DL-SCH transport block, DL-SCH TB) and uses modulation methods such as QPSK (Quadrature Phase Shift Keying), 16QAM (Quadrature Amplitude Modulation), 64QAM, and 256QAM. The TB is encoded to generate a codeword. PDSCH carries up to two codewords. Scrambling and modulation mapping are performed for each codeword, and the modulation symbols generated from each codeword are mapped to one or more layers. Each layer is mapped to resources together with DMRS (Demodulation Reference Signal) to generate an OFDM symbol signal, which is then transmitted by the corresponding antenna port.

[0076] The PUCCH carries Uplink Control Information (UCI), which includes:

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

[0078] - HARQ-ACK: A response to a downlink data packet (e.g., a codeword) on a PDSCH. It indicates whether the downlink data packet is successfully received. One bit of HARQ-ACK is transmitted as a response to a single codeword, and two bits of HARQ-ACK are transmitted as a response to two codewords. HARQ-ACK responses include positive ACK (simply, ACK), negative ACK (hereinafter, NACK), DTX (Discontinuous Transmission), or NACK / DTX. Here, the term HARQ-ACK is used interchangeably with HARQ ACK / NACK and ACK / NACK.

[0079] CSI (Channel State Information): Feedback information for a downlink channel. Multiple Input Multiple Output (MIMO)-related feedback information includes a Rank Indicator (RI) and a Precoding Matrix Indicator (PMI).

[0080] Table 5 shows an example of a PUCCH format. According to the PUCCH transmission length, it can be divided into Short PUCCH (formats 0 and 2) and Long PUCCH (formats 1, 3 and 4).

[0081] [Table 5]

[0082] PUCCH format 0 carries UCI with a maximum size of 2 bits and is mapped and transmitted based on a sequence. Specifically, the terminal transmits one of a plurality of sequences via a PUCCH with PUCCH format 0 to transmit a specific UCI to the base station. The terminal transmits a PUCCH with PUCCH format 0 within a PUCCH resource for a corresponding SR setting only when transmitting a positive SR.

[0083] PUCCH format 1 carries UCI with a maximum size of 2 bits, and the modulation symbols are spread by an orthogonal cover code (OCC) in the time domain (set differently depending on whether frequency hopping is used or not). DMRS is transmitted in symbols where no modulation symbols are transmitted (i.e., transmitted using TDM (Time Division Multiplexing)).

[0084] PUCCH format 2 carries UCI with a bit size larger than 2 bits, and modulation symbols are transmitted after frequency division multiplexing (FDM) with DMRS. DM-RS is located at symbol indexes #1, #4, #7, and #10 in a 1 / 3 density resource block. A Pseudo Noise (PN) sequence is used for the DM_RS sequence. Frequency hopping can be activated for the 2-symbol PUCCH format 2.

[0085] In PUCCH format 3, terminal multiplexing is not performed within the same physical resource block, and UCI with a bit size larger than 2 bits is carried. That is, the PUCCH resource of PUCCH format 3 does not include an orthogonal cover code. The modulation symbol is transmitted after being subjected to TDM (Time Division Multiplexing) with DMRS.

[0086] PUCCH format 4 supports multiplexing of up to four terminals in the same physical resource block and carries UCI with a bit size larger than 2 bits. That is, the PUCCH resource of PUCCH format 3 includes an orthogonal cover code. Modulation symbols are transmitted after being time division multiplexed (TDM) with DMRS.

[0087] The PUSCH carries uplink data (e.g., UL-SCH transport block, UL-SCH TB) and / or uplink control information (UCI) and is transmitted based on a cyclic prefix-orthogonal frequency division multiplexing (CP-OFDM) waveform or a discrete Fourier transform-spread-orthogonal frequency division multiplexing (DFT-s-OFDM) waveform. When the PUSCH is transmitted based on the DFT-s-OFDM waveform, the terminal applies transform precoding to transmit the PUSCH. As an example, when transform precoding is not possible (e.g., transform precoding is disabled), the terminal transmits the PUSCH based on the CP-OFDM waveform, and when transform precoding is possible (e.g., transform precoding is enabled), the terminal transmits the PUSCH based on the CP-OFDM waveform or the DFT-s-OFDM waveform. PUSCH transmissions may be dynamically scheduled by UL grants in the DCI or semi-statically scheduled (configured grant) based on higher layer (e.g., RRC) signaling (and / or Layer 1 (L1) signaling (e.g., PDCCH)). PUSCH transmissions may be codebook-based or non-codebook-based.

[0088] Figure 5 illustrates a process of receiving PDCCH / PDSCH and transmitting ACK / NACK. Referring to Figure 5, a terminal detects a PDCCH in slot #n. Here, the PDCCH includes downlink scheduling information (e.g., DCI format 1_0, 1_1), and the PDCCH indicates DL allocation-to-PDSCH offset (K0) and PDSCH-HARQ-ACK report offset (K1). For example, DCI formats 1_0, 1_1 include the following information:

[0089] - Frequency domain resource assignment: Indicates the RB set assigned to the PDSCH.

[0090] - Time domain resource assignment: Indicates K0 (e.g. slot offset), the starting position of the PDSCH within slot #n+K0 (e.g. OFDM symbol index) and the length of the PDSCH (e.g. number of OFDM symbols).

[0091] - PDSCH-to-HARQ_feedback timing indicator: Indicates K1.

[0092] - HARQ process number (4 bits): Indicates the HARQ process ID (Identity) for data (e.g., PDSCH, TB).

[0093] Thereafter, the terminal receives the PDSCH from slot #(n+K0) according to the scheduling information of slot #n, and then transmits UCI via PUCCH in slot #(n1+K1) when the reception of the PDSCH is completed in slot #n1 (where n+K0≦n1). Here, the UCI includes a HARQ-ACK response to the PDSCH. For convenience, in FIG. 5, it is assumed that the SCS for the PDSCH and the SCS for the PUCCH are the same and that slot #n1=slot #n+K0, but the present invention is not limited thereto. If the SCSs are different, K1 is indicated / interpreted based on the SCS of the PUCCH.

[0094] If the PDSCH is configured to transmit up to 1 TB, the HARQ-ACK response consists of 1 bit. If the PDSCH is configured to transmit up to 2 TB, the HARQ-ACK response consists of 2 bits if spatial bundling is not configured and 1 bit if spatial bundling is configured. If the transmission time of the HARQ-ACK for multiple PDSCHs is specified as slot #(n+K1), the UCI transmitted in slot #(n+K1) includes the HARQ-ACK response for multiple PDSCHs.

[0095] Whether or not the UE performs spatial bundling for the HARQ-ACK response is configured for each cell group (e.g., RRC / higher layer signaling). As an example, spatial bundling is configured separately for each of the HARQ-ACK response transmitted via the PUCCH and / or the HARQ-ACK response transmitted via the PUSCH.

[0096] Spatial bundling is supported when the maximum number of TBs (or codewords) that can be received at one time (or scheduled by one DCI) in a corresponding serving cell is two (or more than two) (for example, when the upper layer parameter maxNrofCodeWordsScheduledByDCI corresponds to 2-TB). Meanwhile, more than four layers are used for 2-TB transmission, and up to four layers are used for 1-TB transmission. As a result, when spatial bundling is configured in a corresponding cell group, spatial bundling is performed on serving cells in the corresponding cell group that can schedule more than four layers. A terminal that wishes to transmit a HARQ-ACK response through spatial bundling on a corresponding serving cell can generate a HARQ-ACK response by performing a bit-wise logical AND operation on A / N bits for multiple TBs.

[0097] For example, assuming that a terminal receives DCI scheduling 2-TB and receives 2-TB via PDSCH based on the DCI, a terminal performing spatial bundling can generate a single A / N bit by logically ANDing the first A / N bit for the first TB and the second A / N bit for the second TB. As a result, if both the first TB and the second TB are ACK, the terminal reports an ACK bit value to the base station, and if both TBs are NACK, the terminal reports a NACK bit value to the base station.

[0098] For example, if only 1-TB is actually scheduled on a serving cell that is configured to receive 2-TB, the terminal can generate a single A / N bit by logically ANDing the A / N bit for the 1-TB with a bit value of 1. As a result, the terminal reports the A / N bit for the 1-TB to the base station as is.

[0099] A base station / terminal has multiple parallel DL HARQ processes for DL ​​transmission. Multiple parallel HARQ processes allow DL transmission to be performed continuously while waiting for HARQ feedback for successful or unsuccessful reception of 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 related to the number of transmissions of MAC Physical Data Blocks (PDUs) in the buffer, HARQ feedback for MAC PDUs in the buffer, current redundancy version, etc. Each HARQ process is distinguished by a HARQ process ID.

[0100] 6 illustrates a PUSCH transmission process. Referring to FIG. 6, a UE detects a PDCCH in slot #n. Here, the PDCCH includes uplink scheduling information (e.g., DCI format 0_0, 0_1). DCI format 0_0, 0_1 includes the following information:

[0101] - Frequency domain resource assignment: Indicates the RB set assigned to the PUSCH.

[0102] - Time domain resource assignment: indicates the slot offset K2, the starting position (e.g., symbol index) and length (e.g., number of OFDM symbols) of the PUSCH within the slot. The starting symbol and length are indicated by the Start and Length Indicator Value (SLIV) or are indicated respectively.

[0103] Thereafter, the terminal transmits a PUSCH in slot #(n+K2) according to the scheduling information of slot #n, where the PUSCH includes a UL-SCH TB.

[0104] Carrier aggregation

[0105] NR can merge multiple uplink / downlink carriers (i.e., carrier merging) to support wider uplink / downlink bandwidth. Carrier merging allows signals to be transmitted / received from multiple carriers. When carrier merging is applied, each carrier (see Figure A2) is called a component carrier (CC). CCs may be adjacent or non-adjacent to each other in the frequency domain. The bandwidth of each CC is defined independently. Asymmetric carrier merging, where the number of UL CCs and the number of DL CCs are different, is also possible.

[0106] - PCell (Primary Cell): In the case of a terminal configured for carrier merging, a cell operating on a primary frequency (e.g., Primary Component Carrier (PCC)) on which the terminal performs an initial connection establishment procedure or initiates a connection re-establishment procedure. In the case of DC (Dual Connectivity), a MCG (Master Cell Group) cell operating on a primary frequency on which the terminal performs an initial connection establishment procedure or initiates a connection re-establishment procedure.

[0107] - SCell (Secondary Cell): For a terminal configured with carrier aggregation, this is a cell that provides radio resources in addition to the special cell.

[0108] - PSCell (Primary SCG Cell): In the case of DC, a Secondary Cell Group (SCG) cell to which the UE randomly connects when performing RRC reconfiguration and synchronization processes.

[0109] - Special Cell (SpCell): In case of DC, the special cell points to a PCell of the MCG or a PSCell of the SCG. Otherwise (i.e., non-DC), the special cell points to a PCell.

[0110] - Serving Cell (ServCell): A cell configured for a terminal in the RRC_CONNECTED state. If CA / DA is not configured, there is only one serving cell (i.e., PCell). If CA / DA is configured, the serving cell indicates a cell set including the special cell and all SCells.

[0111] Meanwhile, the control information can be configured to be transmitted and received only by a specific cell. As an example, UCI is transmitted by a special cell (e.g., PCell). When an SCell (hereinafter, PUCCH-SCell) in which PUCCH transmission is permitted is configured, UCI can also be transmitted by the PUCCH-SCell. As another example, the base station allocates a scheduling cell (set) to reduce the complexity of PDCCH BD (blinding decoding) at the terminal side. For PDSCH reception / PUSCH transmission, the terminal performs PDCCH detection / decoding only in the scheduling cell. Also, the base station transmits PDCCH only in the scheduling cell (set). For example, PDCCH for downlink allocation is transmitted by cell #0 (i.e., scheduling cell), and its PDSCH is transmitted by cell #2 (i.e., scheduled cell) (Cross-Carrier Scheduling, CCS). The scheduling cell (set) is configured by a terminal-specific, terminal-group-specific, or cell-specific manner. The scheduling cell includes a special cell (eg, a PCell).

[0112] A carrier indicator field (CIF) is used for CCS (Cross-Carrier Scheduling). The CIF is semi-statically disabled / enabled by terminal-specific (or terminal group-specific) higher layer (e.g., Radio Resource Control, RRC) signaling. The CIF field is an x-bit field (e.g., x=3) in the PDCCH (i.e., DCI) and is used to indicate the (serving) cell index of the scheduled cell.

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

[0114] - CIF enabled: CIF exists in PDCCH. The scheduling PDCCH allocates PDSCH / PUSCH resources in one cell among multiple cells using CIF. The scheduling cell is the same as or different from the scheduled cell. PDSCH / PUSCH means PDSCH or PUSCH.

[0115] FIG. 7 is a diagram for explaining carrier merging. In FIG. 7, it is assumed that three cells are merged. When CIF is disabled, in each cell, only the PDCCH that schedules its own PDSCH / PUSCH is transmitted (self-carrier scheduling, SCS). On the other hand, when CIF is enabled by terminal-specific (or terminal-group-specific or cell-specific) higher layer signaling and cell A is set as a scheduling cell, cell A transmits not only the PDCCH that schedules cell A's PDSCH / PUSCH, but also the PDCCH that schedules the PDSCH / PUSCH of other cells (i.e., scheduled cells) (cross-carrier scheduling, CCS). In this case, cell B / C does not transmit the PDCCH that schedules its own cell.

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

[0117] FIG. 8 is a diagram illustrating a wireless communication system supporting an unlicensed band. For convenience, a cell operating in a licensed band (hereinafter, L-band) is defined as an LCell, and a carrier of the LCell is defined as a (DL / UL) LCC (Licensed Component Carrier). A cell operating in an unlicensed band (hereinafter, U-band) is defined as an UCell, and a carrier of the UCell is defined as a (DL / UL) UCC (Unlicensed Component Carrier). A cell's carrier refers to the operating frequency (e.g., center frequency) of the cell. A cell / carrier (e.g., Component Carrier, CC) is collectively referred to as a cell.

[0118] When carrier aggregation (CA) is supported, one terminal can transmit and receive signals to and from a base station through multiple aggregated cells / carriers. When multiple CCs are configured in one terminal, one CC is set as a PCC (Primary CC) and the remaining CCs are set as SCCs (Secondary CCs). Specific control information / channels (e.g., CSS PDCCH, PUCCH) are set to be transmitted and received only through the PCC. Data is transmitted and received through the PCC / SCC. FIG. 8(a) illustrates an example in which a terminal and a base station transmit and receive signals through an LCC and a UCC (non-standalone (NSA) mode). In this case, the LCC is set as a PCC and the UCC is set as an SCC. When multiple LCCs are configured in a terminal, one specific LCC is set as a PCC and the remaining LCCs are set as SCCs. FIG. 8(a) corresponds to LAA in a 3GPP LTE system. Figure 8(b) illustrates an example in which a terminal and a base station transmit and receive signals via one or more UCCs without an LCC (SA (Standalone) mode). In this case, one of the UCCs is configured as a PCC, and the remaining UCCs are configured as SCCs. As a result, the NR UCell supports PUCCH, PUSCH, PRACH transmission, etc. In the unlicensed band of the 3GPP NR system, both the NSA mode and the SA mode are supported.

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

[0120] - Channel: A channel is a set of consecutive RBs in a shared spectrum where a channel access process is performed. It refers to a carrier or a part of a carrier.

[0121] - Channel Access Procedure (CAP): A procedure for evaluating channel availability based on sensing to determine whether other communication nodes are using the channel before transmitting a signal. The basic unit for sensing is T sl The sensing slot has a duration of 9 us. The base station or the terminal senses the channel during the sensing slot, and the power detected for at least 4 us within the sensing slot is equal to or greater than the energy detection threshold X Thresh If it is smaller, the sensing slot period T sl is considered to be idle. Otherwise, the sensing slot period T sl =9us is considered busy. CAP is also known as LBT (Listen-Before-Talk).

[0122] - Channel occupancy: refers to the corresponding transmission on a channel by a base station / terminal after performing a channel access procedure.

[0123] - Channel Occupancy Time (COT): This refers to the total time that the base station / terminal and any base station / terminal sharing the channel occupancy can transmit on the channel after the base station / terminal performs the channel connection process. When determining the COT, if the transmission gap is 25us or less, the gap period is also counted in the COT. The COT is shared for transmission between the base station and the corresponding terminal.

[0124] - DL transmission burst: is defined as a set of transmissions from a base station with no gaps of more than 16us. Transmissions from a base station separated by gaps of more than 16us are considered to be individual DL transmission bursts. The base station does not sense channel availability within a DL transmission burst and transmits after the gap.

[0125] - UL transmission burst: is defined as a set of transmissions from a terminal with no gaps longer than 16us. Transmissions from a terminal separated by gaps longer than 16us are considered as individual UL transmission bursts. The terminal does not sense channel availability within a UL transmission burst and transmits after the gap.

[0126] - Detection burst: refers to a DL transmission burst that includes a set of signals and / or channels bounded within a (time) window and associated duty cycle. In an LTE-based system, a detection burst is a base station initiated transmission that includes PSS, SSS, and CRS (cell-specific RS), and also includes non-zero power CSI-RS. In an NR-based system, a detection burst is a base station initiated transmission that includes at least SS / PBCH blocks, and also includes CORESET for PDCCH that schedules PDSCH with SIB1, PDSCH carrying SIB1, and / or non-zero power CSI-RS.

[0127] FIG. 9 illustrates a method of occupying resources in an unlicensed band. According to regional regulations for unlicensed bands, a communication node in an unlicensed band must determine whether other communication nodes are using the channel before transmitting a signal. Specifically, a communication node can first perform carrier sensing (CS) before transmitting a signal to determine whether other communication nodes are transmitting signals. A case where it is determined that other communication nodes are not transmitting signals is defined as a case where a clear channel assessment (CCA) is confirmed. If there is a CCA threshold set by a predetermined or higher layer (e.g., RRC) signaling, a communication node determines the channel state as busy when energy higher than the CCA threshold is detected in the channel, and otherwise determines the channel state as idle. For reference, in the Wi-Fi standard (802.11ac), the CCA threshold is specified as -62 dBm for non-Wi-Fi signals and -82 dBm for Wi-Fi signals. If the channel state is determined to be idle, the communication node can start transmitting signals on the UCell. The above series of processes is called LBT (Listen-Before-Talk) or CAP (Channel Access Procedure). LBT and CAP can be used interchangeably.

[0128] Table 6 illustrates the channel access procedure (CAP) supported in NR-U.

[0129] [Table 6]

[0130] Multi-cell Scheduling DCI

[0131] NR supports broad spectrum in various frequency ranges. The re-farming of frequency bands used in previous generations is expected to increase the availability of advanced spectrum for 5G. In particular, for the low frequency band FR1, available spectrum blocks tend to become more fragmented and dispersed. For FR2 bands and some FR1 bands, the available spectrum becomes wider, necessitating the operation of multiple carriers / cells within the band. It is necessary to improve throughput and coverage by using such dispersed spectrum bands or wider bandwidth spectrum in a more power-efficient and flexible manner.

[0132] When scheduling data across multiple cells, including intra-band and inter-band cells, it is important to increase flexibility and spectrum / power efficiency. In the current 5G NR scheduling method, DCI can only schedule PUSCH / PDSCH for one cell. However, it is expected that the need for simultaneous scheduling of multiple cells will increase in the future due to spectrum expansion / modification, etc. In order to reduce control overhead due to scheduling, it is advantageous to schedule PUSCH / PDSCH for multiple cells using one DCI.

[0133] Thus, in future, in carrier aggregation (CA) situations where multiple cells are configured, in order to reduce the DCI overhead for PDSCH / PUSCH scheduling, Rel-18 will consider a multi-cell scheduling scheme that simultaneously schedules multiple (serving) cells / CCs (and thus PDSCH / PUSCH transmissions) with a single DCI.

[0134] Here, a method for configuring and interpreting each field in the multi-cell DCI for designing a DCI structure that performs the above-mentioned multi-cell scheduling is proposed. In this specification, where the operation of multi-cell scheduling for PUSCH or PDSCH transmission is mainly described, the operation principle of the proposed method is also applicable to the case of multi-cell scheduling for PDSCH or PUSCH transmission. In addition, in this specification, a cell may refer to a BWP configured / indicated (active) for the cell.

[0135] Hereinafter, the multi-cell scheduling DCI is also referred to as a multi-cell DCI or simply DCI, and includes at least one of a DL grant DCI for scheduling a PDSCH and a UL grant DCI for scheduling a PUSCH.

[0136] Hereinafter, the reference cell is determined based on at least one of the following i) to viii), but is not limited thereto. i) the cell with the lowest (or highest) cell index in a combination of cells scheduled simultaneously by the same multi-cell DCI (i.e., a co-scheduled cell set) (or in each cell subgroup described later); ii) the cell with the earliest (or latest) starting symbol time of the indicated PDSCH / PUSCH transmission (if there are multiple cells with the earliest (or latest) PDSCH / PUSCH starting symbol time, the cell with the lowest (or highest) cell index among the multiple cells); iii) the cell with the earliest (or latest) ending symbol time of the indicated PDSCH / PUSCH transmission (if there are multiple cells with the earliest (or latest) PDSCH / PUSCH ending symbol time, the cell with the lowest (or highest) cell index among the multiple cells); iv) the cell indicated by the CIF field value or a cell designated in advance by RRC; v) a set of all cells that can be scheduled by any multi-cell DCI (i.e., a schedulable cell set), the cell with the lowest (or highest) cell index; vi) the cell indicated by the CIF field value; vii) the cell on which the multi-cell DCI is transmitted; and / or viii) a cell pre-specified by the RRC.

[0137] Meanwhile, the fields applied to the Shared-reference-cell method, the Shared-cell-common method, and / or the Shared-state-extension method proposed in this specification are i) configured with only one field in the multi-cell DCI (i.e., applied in common to all cells belonging to a co-scheduled cell set), or ii) configured with one field (applied in common) for each cell subgroup in a state where all cells belonging to a co-scheduled cell set are grouped (configured) into one or more (plural) cell subgroups (i.e., individual / independent fields are configured between cell subgroups), or iii) configured with only one field in the schedulable cell set (i.e., applied in common to all cells belonging to a co-scheduled cell set), or In a state where all cells belonging to the co-scheduled cell set are grouped (set) into one or more (plural) cell subgroups, one field (commonly applied) is configured for each cell subgroup (i.e., individual / independent fields are configured between cell subgroups) (i.e., a shared-reference-cell / shared-cell-common / shared-state-extension method and a field / information configuration / indication method based thereon are applied for each cell subgroup). Each of the above-mentioned cell subgroups is configured / set with a specific cell or specific multiple cells (e.g., a part of the cells belonging to the co-scheduled cell set or the schedulable cell set or the entirety of the cells) belonging to the co-scheduled cell set or the schedulable cell set.

[0138] Specifically, in the case of the cell subgroup setting (grouping), i) it is set independently for each DCI field, or ii) it is set for each field group (consisting of one or more DCI fields) (in this case, the same cell subgroup setting is applied to DCI fields belonging to the same group). In addition, in the case of the cell subgroup configuration (grouping), i) the subgroup is configured / applied (at cell-level) regardless of the number of (candidate) BWPs configured for each cell (belonging to the schedulable cell set or the co-scheduled cell set) and the combination of (active) BWPs for each cell (for example, for cell 1 / 2 / 3 / 4, when cell 1 and 2 are configured to one subgroup and cell 3 and 4 are configured to another subgroup, the subgroup configuration is always applied regardless of the change in the combination of (active) BWPs for each cell), or ii) the cell subgroup is configured / applied (independently) for each combination of (active) BWPs for each cell (belonging to the schedulable cell set or the co-scheduled cell set) (for example, when the (active) BWPs of cell 1 / 2 / 3 / 4 are a specific combination, cell 1 and 2 are configured to one subgroup and cell 3 and 4 are configured to another subgroup, while the (active) BWPs of cell 1 / 2 / 3 / 4 are another specific combination, cell In this structure, cells 1, 2, and 3 are set to one subgroup, and only cell 4 is set to another subgroup. DCI fields that are subject to such cell subgrouping settings / applications or that are configured based on the cell subgrouping settings include, but are not limited to, at least some of the following DCI fields:

[0139] - Frequency domain resource assignment (FDRA) field

[0140] - Time domain resource assignment (TDRA) field

[0141] - Modulation and coding scheme (MCS) field

[0142] - HARQ process number (HPN) field

[0143] - Antenna port(s)(AP) field

[0144] - Transmission configuration indication (TCI) field

[0145] - SRS resource indicator (SRI) field

[0146] - Precoding information and number of layers (TPMI) field

[0147] - DMRS sequence initialization (DMRS init) field

[0148] - PTRS-DMRS association (PTRS asso) field

[0149] - VRB-to-PRB mapping (RB mapping) field

[0150] - PRB bundling size indicator (PRB bundle) field

[0151] - Beta_offset indicator (beta offset) field (e.g., information about the beta offset parameter used (for rate matching) to determine the number of modulation symbols (REs))

[0152] - Frequency hopping flag (FH) field

[0153] - TPC command for scheduled PUSCH (TPC) field

[0154] - ChannelAccess-CPext-CAPC(for PUSCH)(LBT) field (e.g., information on channel access type and CP extension on a shared spectrum, as well as CAPC (Channel Access Priority Class) information is provided)

[0155] - Open-loop power control parameter set indication (OLPC) field

[0156] On the other hand, in the case where the DCI field to which the shared-cell-common method proposed in this specification is applied is the conventional one (single-cell DCI-based scheduling), and a table consisting of one or more (plural) states / indexes (consisting of different parameters / values ​​(combinations)) for each cell is predefined or configured by the RRC or MAC-CE, and the DCI field indicates one of the (plural) states / indexes in the table (for example, the following CSI request and / or Beta_offset indicator and / or ChannelAccess-CPext-CAPC(LBT) and / or OLPC parameter set indication and / or Invalid symbol pattern In the case of the indicator and / or TDRA field and / or MCS field and / or AP field and / or TCI field and / or SRI field and / or TPMI field), a specific state / index / codepoint indicated by the DCI field configured in common to a cell set (e.g. a set of co-scheduled cells or a cell subgroup) to which the shared-cell-common method is applied is interpreted / applied (i.e. for each cell) with a parameter / value (combination) corresponding to the state / index / codepoint in a table configured for each cell belonging to the cell set, or Opt Y) a parameter / value (combination) corresponding to the state / codepoint / index in a table configured for a specific reference cell in the cell set is applied commonly to the cells belonging to the cell set (e.g. in the case of ChannelAccess-CPext-CAPC(LBT)), or OptZ) In a state where another (common) table commonly applied to the corresponding cell set is previously set by the RRC / MAC-CE in the above-mentioned manner, a parameter / value (combination) corresponding to the corresponding state / codepoint / index in the common table is commonly applied to the cells belonging to the corresponding cell set (e.g., in the case of ChannelAccess-CPext-CAPC (LBT)). For example, FIG. 10 is a diagram for explaining a case where Opt X is applied to a DCI field to which the shared-cell-common method is applied. Referring to FIG. 10, since it is assumed that a maximum of N cells are included in the co-scheduled cell set, the actual number of cells co-scheduled by one multi-scheduling DCI is N or less, and therefore various combinations of co-scheduled cells of N or less are set. A value indicated by one state (codepoint) of the shared-cell-common DCI field is set independently for each cell. For example, assuming that a first state / codepoint (e.g., 00) is indicated, the first state / codepoint means value a for Cell#1, value b for Cell#2, and value c for Cell#n. The meaning of a value being set independently for each cell includes, but is not limited to, a case where different values ​​are set for different cells, and does not exclude the same value being set for two or more cells. That is, it is sufficient that the values ​​between cells are set independently, and there is no restriction that the independently set values ​​must be the same or different. Also, some cells may not be set with a value for the state / codepoint. For example, Cell#2 has value x for the i-th state / codepoint, but no value is set for Cell#1 and Cell / #N. Information (e.g., a table) including cell values ​​to be applied for interpretation of the shared-cell-common DCI field is set in the terminal (for each cell). As described above, the Beta_offset indicator field, the ChannelAccess-CPext field, the OLPC parameter setEach of the indication field, the antenna port (AP) field, the SRS resource indication (SRI) field, and / or the precoding and layer number information (TPMI) field corresponds to a different shared-cell-common DCI field. For example, the Beta_offset indicator field is a first shared-cell-common DCI field, and a first table therefor is configured (for each cell), the ChannelAccess-CPext field is a second shared-cell-common DCI field, and a second table therefor is configured (for each cell), the OLPC parameter set indication field is a third shared-cell-common DCI field, and a third table therefor is configured (for each cell), the antenna port (AP) field is a fourth shared-cell-common DCI field, and a fourth table therefor is configured (for each cell), the SRS resource indication (SRI) field is a fifth shared-cell-common DCI field, and a fifth table therefor is configured (for each cell), and the precoding and layer number information (TPMI) field is a sixth shared-cell-common DCI field, and a sixth table therefor is configured (for each cell), but is not limited to this.

[0157] Meanwhile, a method of simultaneously indicating a combination of parameters / values ​​to be applied to multiple cells by indicating a specific state / codepoint / index in the table according to a DCI field based on a (multi-cell) joint table in which each state / codepoint / index (row) is composed of a combination of multiple parameters / values ​​for multiple cells, for example, the shared-cell-common method or shared-state-extended method, in which, when multiple cells are scheduled by a multi-cell DCI, a specific field (e.g., CSI request and / or Beta_offset indicator and / or ChannelAccess-CPext-CAPC(LBT) and / or OLPC parameter set indication and / or Invalid symbol pattern indicator and / or TDRA field and / or MCS field and / or AP field and / or TCI field and / or SRI field and / or TPMI field), and if only one cell is scheduled by multi-cell DCI, the state / codepoint / index indicated in the particular field is interpreted / applied as the parameter / value (corresponding to that state / codepoint / index) in the (single-cell) table configured for scheduling based on single-cell DCI for that cell.

[0158] [Common-T1A: Invalid state handling]

[0159] First, a more specific example of the shared-cell-common method (specifically, the Opt X method) will be given below.

[0160] First, in scheduling based on conventional single-cell DCI, for a specific DCI field, N (mutually different) parameters / values ​​(combinations) are pre-configured by RRC or MAC-CE for each of N states / codepoints / indexes that can be indicated by the DCI field. When one of the N states / codepoints / indexes is indicated by the DCI field, the terminal performs PDSCH / PUSCH transmission / reception operations by applying the parameter / value (combination) set for the indicated state / codepoint / index. In this case, the size of the DCI field is determined to be ceil{log2(N)} bits, where N is set to a different (or the same) value for each cell.

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

[0162] Meanwhile, in the case of the specific DCI field in scheduling based on multi-cell DCI, as described above, when a specific state / codepoint / index is indicated by a DCI field with parameters / values ​​(combinations) pre-set for each state / codepoint / index (applied to scheduling based on single-cell DCI) for each cell, the terminal interprets / applies the parameters / values ​​(combinations) set for each cell for the indicated state / codepoint / index, respectively, for each cell, and performs transmission / reception operations for the PDSCH / PUSCH scheduled for each cell.

[0163] On the other hand, in scheduling based on multi-cell DCI, the size of the specific DCI field is determined to be ceil{log2(N_max)} bits based on the maximum value N_max of the N values ​​set for each cell belonging to the entire schedulable cell set (or each co-scheduled cell set), Alt A) (in this case, the DCI field indicates up to (initial) N_max states / codepoints / indexes), or Alt B) (in this case, the DCI field indicates up to (initial) N_min states / codepoints / indexes).

[0164] [Common-T2: Field size determination]

[0165] Furthermore, a specific example is proposed below for the method of determining the DCI field size when the following separation method is applied.

[0166] First, for a particular DCI field in conventional single-cell DCI, the size of that DCI field (with N states / codepoints / indexes set to be indicated by that DCI field) is set to L = ceil{log2(N)} bits, where L is set to a different (or the same) value for each cell.

[0167] On the other hand, when the specific DCI field in the single-cell DCI is configured based on the following separation method, first, for each of a plurality of (e.g., N_co) co-scheduled cell sets configured in the entire schedulable cell set, the sum L_sum of the L values ​​set for each of the cells belonging to the co-scheduled cell set is calculated, and the maximum value of the N_co L_sum values ​​calculated for each of the N_co co-scheduled cell sets is determined as the size of the specific DCI field (configured in the multi-cell DCI).

[0168] [Reference SC-DCI format for MC-DCI fields]

[0169] On the other hand, when applying the shared-cell-common method (based on the Opt X scheme) and / or the following separate method (and / or the following shared-reference-cell method and / or shared-state-extension method) to a specific DCI field, when referring to the N states / codepoints / indexes that can be indicated in the DCI field set in the single-cell DCI for each cell (belonging to the schedulable cell set or co-scheduled cell set) and the size L=ceil{log2(N)} of the DCI field, it is necessary to determine which single-cell DCI format (for convenience, defined as the "reference DCI format") to refer to and the corresponding field size L value.

[0170] Specifically, in the case of DL, first, if only one of DCI format 1_1 and DCI format 1_2 is configured for a specific cell, the configured DCI format can be determined / referenced as the reference DCI format. If both DCI format 1_1 and DCI format 1_2 are configured, the base station sets Opt 1) DCI format 1_2 as the reference DCI format, or Opt 2) DCI format 1_1 as the reference DCI format, or Opt 3) which of the two to determine / reference as the reference DCI format (on the other hand, if neither DCI format 1_1 nor DCI format 1_2 is configured, DCI format 1_0 is determined / referenced as the reference DCI format).

[0171] Also, in the case of UL, first, if only one of DCI format 0_1 ​​and DCI format 0_2 is set for a specific cell, the set DCI format can be determined as / referenced as the reference DCI format. If both DCI format 0_1 ​​and DCI format 0_2 are set, the base station sets Opt 1) DCI format 0_2 to be determined as / referenced as the reference DCI format, or Opt 2) DCI format 0_1 ​​to be determined as / referenced as the reference DCI format, or Opt 3) which of the two to determine as / reference as the reference DCI format (on the other hand, if neither DCI format 0_1 ​​nor DCI format 0_2 is set, DCI format 0_0 is determined as / referenced as the reference DCI format).

[0172] [Determination of entire MC-DCI payload size]

[0173] Furthermore, the following method may be considered as a method for determining the total payload size of the multi-cell DCI (format).

[0174] In a state where the above (based on the Opt X method) Shared-cell-common method (defined as the “Type-1A” field for convenience) and / or the following Separate method (defined as the “Type-2” field for convenience) and / or the following Shared-reference-cell method (defined as the “Type-1C” field for convenience) and / or the Shared-state-extension method (defined as the “Type-1B” field for convenience) are applied to each DCI field, first, the entire schedulable cell set For each of a plurality (e.g., N_co) of co-scheduled cell sets configured in the multi-cell DCI (format), the sum P_sum of the sizes of all Type-1A / 1B / 1C / 2 fields required for scheduling for the co-scheduled cell set (cells belonging to it) is calculated, and the maximum value of the N_co P_sum values ​​calculated for each of the N_co co-scheduled cell sets is determined to be the payload size of the multi-cell DCI (format).

[0175] UL (or DL) DCI field configuration for multi-cell PUSCH (or PDSCH) scheduling

[0176] Hereinafter, various methods (e.g., methods 1 to 7) described regarding DCI field configuration are understood as types applied to each DCI field, and all fields of a multi-cell scheduling DCI are not necessarily configured by one specific method. For example, in one single-cell scheduling DCI, a first DCI field is configured based on method X, and a second DCI field is configured based on method Y. Furthermore, the following classification of methods assumes the most detailed configuration for convenience of explanation, and one DCI field may be configured by a combination of different DCI field configuration methods as long as they do not conflict. As an example, one Type 1A DCI field is configured by the following combination of method 3: shared-cell-common and method 4: shared-state-extended, and in this case, the interpretation / application of one Type 1A DCI field common to all cells is independent for each cell.

[0177] 1) DCI field configuration type

[0178] A. Method 1: Shared-reference-cell

[0179] i. Only one field is configured in the multi-cell DCI, and the value indicated in that DCI field is applied only to one specific reference cell (among the cells scheduled by the multi-cell DCI (the cells for which the operation indicated by that DCI field is set)) (e.g., the cell from which the DCI is transmitted or the cell with the lowest (or highest) cell index or the cell indicated by the CIF field value), and a specific pre-defined / configured default value is applied to the other cells.

[0180] 1. Furthermore, in the case of the reference cell, the cell with the earliest (or latest) PDSCH / PUSCH transmission starting symbol time on that cell is determined (if there are multiple cells with the earliest (or latest) PDSCH / PUSCH starting symbol time, the cell with the lowest (or highest) cell index among the multiple cells is determined), or the cell with the earliest (or latest) PDSCH / PUSCH transmission ending symbol time on that cell is determined (if there are multiple cells with the earliest (or latest) PDSCH / PUSCH ending symbol time, the cell with the lowest (or highest) cell index among the multiple cells is determined).

[0181] B. Method 2: Shared-single-cell

[0182] i. Only one field (at most) is configured in the multi-cell DCI, and the DCI field is configured (the value indicated in the field is applied to the one cell) only when one cell is scheduled (by the multi-cell DCI), and when multiple cells are scheduled, the DCI field is not configured and is omitted (in this case, a specific default value defined / set in advance is applied to the multiple cells).

[0183] C. Method 3: Shared-cell-common

[0184] i. A method in which only one field is configured in the multi-cell DCI, and the value indicated in that DCI field is commonly applied to all cells (scheduled by the multi-cell DCI).

[0185] D. Method 4: Shared-state-extension

[0186] i. A method in which only one field is configured in the multi-cell DCI, and each of the multiple states / code points that can be indicated in that DCI field is configured / set as a combination of multiple pieces of information regarding multiple cells (rather than information regarding a single cell).

[0187] ii. As mentioned above, the distinction between Method 4 and Method 3 is for convenience of explanation, and Method 4: Shared-State-Extended may be understood as a specific implementation of Method 3: Shared-Cell-Common.

[0188] E. Method 5: Separate

[0189] i. A method in which a number of fields are configured (within that DCI) equal to the number of cells scheduled by the multi-cell DCI (and configured to operate according to the DCI field instructions), a separate field corresponds to each scheduled cell, and the value indicated in that field is applied to that cell.

[0190] F. Method 6: Omit

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

[0192] G. Method 7: This is a method for setting whether method 3 or method 5 is applied to a specific DCI field.

[0193] i. A method in which the base station configures (to the terminal) which of Method 3 (shared-cell-common) or Method 5 (separate) to apply for each combination of cells that are simultaneously scheduled (scheduled) by the same multi-cell DCI for a specific DCI field (for each combination of scheduled cells).

[0194] 1. For example, if the scheduled cell combination #1 is composed of {cell #1, cell #2} and the scheduled cell combination #2 is composed of {cell #1, cell #3}, when the scheduled cell combination #1 is, it is set whether the specific field is configured / indicated by applying method 3 or method 5, and (independently from this) when the scheduled cell combination #2 is, it is set whether the specific field is configured / indicated by applying method 3 or method 5.

[0195] 2. Meanwhile, the specific DCI field includes at least one of the following:

[0196] - Frequency domain resource assignment (FDRA) field

[0197] - Time domain resource assignment (TDRA) field

[0198] - Modulation and coding scheme (MCS) field

[0199] - HARQ process number (HPN) field

[0200] - Antenna port(s)(AP) field

[0201] - Transmission configuration indication (TCI) field

[0202] - SRS resource indicator (SRI) field

[0203] - Precoding information and number of layers (TPMI) field

[0204] - DMRS sequence initialization (DMRS init) field

[0205] - PTRS-DMRS association (PTRS asso) field

[0206] - VRB-to-PRB mapping (RB mapping) field

[0207] - PRB bundling size indicator (PRB bundle) field

[0208] - Beta_offset indicator (beta offset) field

[0209] - Frequency hopping flag (FH) field

[0210] - TPC command for scheduled PUSCH (TPC) field

[0211] - Open-loop power control parameter set indication (OLPC) field

[0212] 2) DCI field type signaling (Type 3 DCI field)

[0213] For a specific DCI field, it is set which of method 1, method 2, method 3, method 4 (these methods are defined as "Type-1x methods" for convenience) and method 5 (this method is defined as "Type-2 method" for convenience) is to be applied.

[0214] For a specific DCI field, a method (such a method is defined as "Type-3 method" for convenience) is provided for (a base station to) set for a terminal which method of Type-1x method and Type-2 method is to be applied to co-scheduled cells that are simultaneously scheduled by the same multi-cell DCI.

[0215] On the other hand, when the Type-3 method is applied to a plurality (for example, N) of DCI fields, in a state where the N DCI fields are divided into a plurality (for example, K (<N)) of field groups, for each field group, it is a structure for setting which method of Type-1x method and Type-2 method is to be applied to all fields belonging to the field group.

[0216] Thereby, all fields belonging to the same field group are set to apply only the same one method (for example, only apply the Type-1x method or only apply the Type-2 method), and it is not possible to set different methods for fields belonging to the same field group, and it is set to apply the same method or different methods between different field groups.

[0217] Therefore, as described above, when setting to apply the same one (Type-1x or Type-2) method for each field group (to all fields belonging to the field group), the implementation complexity required for the terminal, for example, the number of cases requiring terminal tests, can be reduced from about (2 N to about 2 K ).

[0218] On the other hand, the DCI fields to which the Type-3 method as described above (based on the Type-1x / 2 method setting in field group units) is applied correspond to at least a part (or all) of the following.

[0219] - HARQ process number (for convenience, called HPN)

[0220] - MCS (for convenience, we will call it MCS)

[0221] - Bandwidth part indicator (for convenience, called BWP)

[0222] - Frequency domain resource assignment (FDRA for convenience)

[0223] - VRB-to-PRB mapping (for convenience, called V2P)

[0224] - PRB bundling size indicator (for convenience, called "bund")

[0225] - Rate matching indicator (for convenience, called RM)

[0226] - ZP CSI-RS trigger (for convenience, called ZCR)

[0227] - Antenna port(s) (for convenience, called AP)

[0228] - Transmission configuration indication (for convenience, called TCI)

[0229] - DMRS sequence initialization (for convenience, referred to as DMRS)

[0230] - Frequency hopping flag (for convenience, called FH)

[0231] - TPC command for scheduled PUSCH (for convenience, referred to as TPC)

[0232] - Precoding information and number of layers (for convenience, referred to as TPMI)

[0233] - PTRS-DMRS association (for convenience, referred to as PTRS)

[0234] - SRS request (for convenience, called A-SRS)

[0235] - SRS resource indicator (for convenience, called SRI)

[0236] - SRS offset indicator (for convenience, called SOI)

[0237] - Open-loop power control parameter set indication (for convenience, called OLPC)

[0238] As an example, the MCS and the AP and / or the TCI and / or the TPMI and / or the SRI belong to the same field group.

[0239] As an example, the FDRA and the V2P and / or the bund belong to the same field group.

[0240] As an example, the V2P and bund belong to the same field group.

[0241] As an example, the RM and ZCR belong to the same field group.

[0242] As an example, the AP and the TCI and / or the TPMI and / or the SRI belong to the same field group.

[0243] As an example, the DMRS and the PTRS belong to the same field group.

[0244] As an example, the TPC and OLPC belong to the same field group.

[0245] As an example, the A-SRS and the SOI belong to the same field group.

[0246] 3) Example of method application for each DCI field

[0247] A.UL / SUL indicator

[0248] i. Opt 1: Example of application of the Shared-reference-cell method

[0249] 1. The value (UL index) indicated in the DCI field applies only to the specific reference cell (among the cells scheduled by the multi-cell DCI) whose SUL carrier is set by the parameter supplementaryUplink, and for other cells, the currently operating UL carrier is maintained without UL carrier switching.

[0250] ii. Opt 2: Example of application of the Shared-single-cell method

[0251] 1. The DCI field is configured (the value indicated thereby (UL index) is applied to the cell) only when one cell is scheduled (or one cell with SUL carrier configured is scheduled) (by multi-cell DCI), and when multiple cells are scheduled (or multiple cells are scheduled or a cell without SUL carrier configured is scheduled), the DCI field is not configured and is omitted (in this case, there is no UL carrier switching for the cell(s) and the currently operating UL carrier is maintained).

[0252] iii. Opt 3: Example of application of the Omit method

[0253] 1. The DCI field is not configured and omitted in the multi-cell DCI (in this case, there is no UL carrier switching for the cells scheduled by the multi-cell DCI, and the currently operating UL carrier is maintained).

[0254] B. Frequency hopping (FH) flag

[0255] i. Opt 1: Example of application of the Shared-cell-common method

[0256] 1. The value (whether or not FH is applied) indicated in that DCI field is applied commonly to the PUSCH on all cells (scheduled by multi-cell DCI), and all of those cells are all cells (among the cells scheduled by multi-cell DCI) with the FH flag set.

[0257] ii. Opt 2: Example of application of the Shared-reference-cell method

[0258] 1. The value indicated in the DCI field (whether or not FH is applied) is applied only to the PUSCH on a specific reference cell (among the cells scheduled by the multi-cell DCI) for which the FH flag is set, and for the PUSCH on other cells, it is assumed that FH is not applied and the PUSCH is transmitted (without FH).

[0259] iii. Opt 3: Example of application of the Shared-single-cell method

[0260] 1. Only when one cell is scheduled (by multi-cell DCI) (or when one cell with the FH flag set is scheduled), the DCI field is configured (the value indicated thereby (whether FH is applied or not) is applied to the PUSCH on that cell), and when multiple cells are scheduled (or when multiple cells are scheduled or when one cell with the FH flag not set is scheduled), the DCI field is not configured and is omitted (in this case, it is assumed that FH is not applied to the PUSCH on multiple cells and the PUSCH is transmitted (without FH)).

[0261] iv. Opt 4: Example of application of the Omit method

[0262] 1. The DCI field is not configured in the multi-cell DCI and is omitted (in this case, it is assumed that no FH is applied to the PUSCH on the cell scheduled by the multi-cell DCI, and the PUSCH is transmitted (without FH).

[0263] v. Note 0: In this case, the specific reference cell is determined to be a specific cell among the cells for which the FH flag is set (in the conventional single-cell (scheduling) DCI).

[0264] vi.Note 1: In this case, for cell A with the FH flag / indicator set and cell B without the FH flag / indicator set (in the conventional single-cell (scheduling) DCI), it is configured / restricted so that only cell A or only cell B belongs to the same cell subgroup (i.e., cell A and cell B do not belong together), and with this configuration, the shared-reference-cell or shared-cell-common method is applied separately for each cell subgroup.

[0265] vii.Note 2: Alternatively, cell A and cell B can be set to belong to the same cell subgroup, and in this state, the Shared-Reference-Cell or Shared-Cell-Common method can be applied separately for each cell subgroup.

[0266] 1. When the shared-cell-common method is applied to a cell subgroup to which both cell A and cell B belong, a) the indicator field configuration is omitted for that cell subgroup, and PUSCH (without FH) is always transmitted assuming that FH is not applied, or b) the indicator field is configured for that cell subgroup, and if FH application is indicated by the field, operation is performed in a state in which no scheduling is considered / assumed for cell B, or c) the indicator field is configured for that cell subgroup, and PUSCH (without FH) is always transmitted assuming that FH is not applied for cell B.

[0267] 2. The cell subgroup is considered / applied as a co-scheduled cell set (total of cells belonging to that set).

[0268] C. Downlink assignment index (DAI)

[0269] i. Opt 1: Example of application of the Shared-cell-common method

[0270] The value indicated in the DCI field (DAI value) is applied commonly to the PUSCHs on all cells (scheduled by the multi-cell DCI).

[0271] ii. Opt 2: Example of application of the Shared-reference-cell method

[0272] The value (DAI value) indicated in that DCI field applies only to the PUSCH on the specific reference cell (among the cells scheduled by the multi-cell DCI), and for the PUSCH on the other cells, it either assumes a specific DAI value (e.g., 4) or assumes no indicated / corresponding DAI (as with PUSCH based on a configured grant) (in which case it configures the HARQ-ACK payload multiplexed onto that PUSCH based on the counter / total-DAI indicated / received by the DL DCI).

[0273] The PUSCH on the reference cell is determined to be Alt 1) the PUSCH on the cell with the lowest cell index (among the cells scheduled with the same single-cell DCI), or Alt 2) the PUSCH with the earliest starting symbol time (if there are multiple PUSCHs with the earliest starting symbol time, the PUSCH on the cell with the lowest cell index among the multiple PUSCHs is determined), or Alt 3) the PUSCH selected to multiplex the HARQ-ACK.

[0274] iii. Opt 3: Example of application of the Shared-single-cell method

[0275] Only when one cell is scheduled (by multi-cell DCI) is the DCI field configured (the value indicated thereby (DAI value) is applied to the PUSCH on that cell), whereas when multiple cells are scheduled, the DCI field is not configured and is omitted (in which case a specific DAI value (e.g. 4) is assumed for the PUSCH on the multiple cells, or no indicated / corresponding DAI is assumed (in which case the HARQ-ACK payload multiplexed on the PUSCH is configured based on the counter / total-DAI indicated / received by the DL DCI)).

[0276] iv. Opt 4: Example of application of the Omit method

[0277] The DCI field is not configured and omitted in the multi-cell DCI (in this case, a specific DAI value (e.g., 4) is assumed for the PUSCH on the cell scheduled by the multi-cell DCI, or no indicated / corresponding DAI is assumed (in this case, the HARQ-ACK payload multiplexed on that PUSCH is configured based on the counter / total-DAI indicated / received by the DL DCI)).

[0278] D. TPC command for scheduled PUSCH

[0279] i. Opt 1: Example of application of the Shared-cell-common method

[0280] The value (TPC value) indicated in that DCI field is applied commonly to the PUSCHs on all cells (scheduled by the multi-cell DCI).

[0281] ii. Opt 2: Example of application of the Shared-reference-cell method

[0282] The value (TPC value) indicated in that DCI field is applied only to the PUSCH on a specific reference cell (among the cells scheduled by the multi-cell DCI), and the PUSCH is transmitted assuming that no TPC value is indicated for the PUSCH on other cells.

[0283] iii. Opt 3: Example of application of the Shared-single-cell method

[0284] Only when one cell is scheduled (by multi-cell DCI) is the DCI field configured (and the value (TPC value) indicated thereby is applied to the PUSCH on that cell), whereas when multiple cells are scheduled, the DCI field is not configured and is omitted (in this case, the PUSCH is transmitted assuming that no TPC value is indicated for the PUSCH on those multiple cells).

[0285] iv. Opt 4: Example of application of the Omit method

[0286] The DCI field is not configured in the multi-cell DCI and is omitted (in this case, it is assumed that there is no indication of a TPC value for the PUSCH on the cell scheduled by the multi-cell DCI, and the PUSCH is transmitted).

[0287] v. Opt 5: Example of application of the Separate method

[0288] The TPC field / information is configured / indicated separately for each of the multiple cells scheduled by the multi-cell DCI. In this case, the TPC field for each cell is configured as 1-bit, and the field indicates either one of the values ​​0 dB and X dB (e.g., X = 1 or X = 3 or X = -1), or one of the values ​​X dB and -x dB (e.g., X = 1 or X = 4).

[0289] If only one cell is scheduled by the multi-cell DCI, the TPC field for that cell is configured as 2 bits as before, and the field indicates one of the four predefined conventional values.

[0290] vi.Note: As another method of Opt 1, the shared-cell-common method can be applied to each of a cell set in accumulation TPC mode, which accumulates and applies the TPC values ​​received up to the current point in time, and a cell set in absolute TPC mode, which instantaneously applies only the TPC value received to the current point in time without accumulation. Thus, a value indicated in a single TPC field corresponding to a cell in accumulation TPC mode is applied commonly to only that cell, and a value indicated in a single TPC field corresponding to a cell in absolute TPC mode is applied commonly to only that cell.

[0291] vii. Note A: In this case, the Shared-Reference-Cell or Shared-Cell-Common method is applied separately for each cell subgroup.

[0292] 1. Here, each cell subgroup is configured to be composed only of cells set to accumulation TPC mode or to be composed only of cells set to absolute TPC mode, and cells set to accumulation TPC mode and cells set to absolute TPC mode are configured not to belong to the same cell subgroup.

[0293] 2. As described above, when the shared-cell-common method is applied for each cell subgroup, the TPC field / information is configured / indicated separately for each cell subgroup scheduled by the multi-cell DCI. In this case, the TPC field for each cell subgroup is configured as 1-bit, and the field indicates one of the values ​​0dB and XdB (e.g., X=1 or X=3 or X=-1), or indicates one of the values ​​XdB and -XdB (e.g., X=1 or X=4) (the indicated value is commonly applied to multiple cells belonging to the cell subgroup).

[0294] a. If only one cell is scheduled by the multi-cell DCI, the TPC field for that cell is configured with 2 bits as in the past, and the field indicates one of the four predefined values.

[0295] E. CSI request

[0296] i. Opt 1: Example of application of the Shared-reference-cell method

[0297] The CSI report indicated in the DCI field is transmitted via a PUSCH on a specific reference cell (among the cells scheduled by the multi-cell DCI), and for PUSCHs on other cells, it operates to transmit PUSCHs assuming that there is no CSI reporting indication.

[0298] A. The PUSCH on the reference cell is determined to be the PUSCH on the cell with the lowest (or highest) cell index among the cells scheduled by the same multi-cell DCI (among the cells scheduled by the same multi-cell DCI), or Alt 2) is determined to be the PUSCH with the earliest (or latest) transmission starting symbol time (if there are multiple PUSCHs with the earliest (latest) starting symbol time, it is determined to be the PUSCH on the cell with the lowest (or highest) cell index among the multiple PUSCHs). For example, FIG. 11 shows an example of a CSI request field to which Alt 1) is applied. In FIG. 11, the terminal receives a multi-cell scheduling DCI via the PDCCH. The multi-cell scheduling DCI is a UL grant DCI format. UL transmissions (e.g., PUSCH) for a cell set scheduled together including one or two or more cells are scheduled together by the multi-cell scheduling DCI. The multi-cell scheduling DCI includes a CSI request field. When a CSI report is requested by the CSI request field, the terminal transmits the CSI report via the PUSCH on the reference cell. As an example, assuming that when X < Y, the cell index of Cell#X < the cell index of Cell#Y, when the cell set scheduled together corresponds to case 1, the terminal transmits the CSI report via the PUSCH on Cell#1 with the lowest cell index. In the case of case 2, the terminal transmits the CSI report via the PUSCH on Cell#2 with the lowest cell index. In the case of case x, the terminal transmits the CSI report via the PUSCH on Cell#N with the lowest cell index.

[0299] ii. Opt 2: Application of the Shared-single-cell method

[0300] Only when one cell is scheduled (by the multi-cell DCI), the DCI field is configured (and the indicated CSI report is transmitted via the PUSCH on that cell), whereas when multiple cells are scheduled, the DCI field is not configured and is omitted (in this case, it is assumed that there is no CSI reporting indication for the PUSCH on the multiple cells and the PUSCH is transmitted).

[0301] iii.Opt 3: Apply the above Omit method

[0302] The DCI field is not configured in the multi-cell DCI and is omitted (in this case, the PUSCH is transmitted assuming that there is no indication of CSI reporting for the PUSCH on the cell scheduled by the multi-cell DCI).

[0303] iv. Note: When the Opt 1 (shared - reference - cell) method is applied and a specific CSI report set / state / code point is indicated by the CSI request field in the multi - cell DCI, the terminal operates to transmit a CSI report (based on reception and measurement) for the CSI - RS transmission corresponding to that CSI report set / state / code point set in the specific reference cell via the PUSCH on that specific reference cell. For example, in FIG. 11, when assuming that X < Y, i.e., the cell index of Cell♯X < the cell index of Cell♯Y, if the co - scheduled cell set corresponds to case 1, the terminal measures / reports CSI based on the CSI - RS corresponding to that CSI report set / state / code point set on Cell♯1 which has the minimum cell index. In the case of case 2, the terminal measures / reports CSI based on the CSI - RS corresponding to that CSI report set / state / code point set on Cell♯2 which has the minimum cell index. In the case of case x, the terminal measures / reports CSI based on the CSI - RS corresponding to that CSI report set / state / code point set on Cell♯N which has the minimum cell index.

[0304] v. Note A: In this case, the specific reference cell is determined to be a specific one of the cells in which the CSI request / indicator is set (in the conventional single - cell (scheduling) DCI). For example, the reference cell is determined to be the cell with the minimum cell index in which the CSI request / indicator is set within the co - scheduled cell set.

[0305] vi. Note B: In this case, for cell A with a CSI request / indicator set (in the conventional single-cell (scheduling) DCI) and cell B without a CSI request / indicator set, it is configured / restricted so that only cell A or only cell B belongs to the same cell subgroup (i.e., cell A and cell B do not belong together), and with this configuration, the shared-reference-cell or shared-cell-common method is applied separately for each cell subgroup.

[0306] vii. Note C: Alternatively, cell A and cell B can be set to belong to the same cell subgroup, and in this state, the Shared-Reference-Cell or Shared-Cell-Common method can be applied separately for each cell subgroup.

[0307] 1. As described above, when the shared-cell-common method is applied to a cell subgroup to which cell A and cell B both belong, a) the indicator field configuration is omitted for that cell subgroup, and PUSCH transmission is performed under the assumption that there is no CSI reporting instruction, or b) the indicator field is configured for that cell subgroup, and if (at least one) bit “1” is indicated by that field, the operation is performed under the assumption that there is no scheduling for cell B, or c) the indicator field is configured for that cell subgroup, and PUSCH transmission is performed under the assumption that there is no CSI reporting instruction for cell B.

[0308] 2. The cell subgroup is considered / applied as a co-scheduled cell set (total of cells belonging to that set).

[0309] viii.Note D: Furthermore, cell X, whose CSI request / indicator field is set to a specific X-bit size (in the conventional single-cell (scheduling) DCI), and cell Y, whose CSI request / indicator field is set to a larger Y-bit size, are configured to belong to the same cell subgroup, and in this state, the shared-reference-cell or shared-cell-common method is applied separately for each cell subgroup.

[0310] 1. As described above, when the shared-cell-common method is applied to a cell subgroup to which cell X and cell Y both belong, a) the indicator field is configured with a smaller size of X-bit for the cell subgroup, and a specific (e.g., having the lowest (or highest) index) {2^X-1} CSI report set / state / codepoint to be applied (and whether to report) is indicated for cell Y, and an indication for other CSI report sets / states / codepoints (indexes) is omitted (i.e., it is assumed that there is no indication for other CSI report sets / states / codepoints), or b) the indicator field is configured with a smaller size of X-bit for the cell subgroup, and PUSCH transmission is performed for cell Y under the assumption that there is no CSI report indication at all times, or c) the indicator field is configured with a larger size of Y-bit for the cell subgroup, and PUSCH transmission is performed for cell Y under the assumption that there is no CSI report indication. For X, the CSI reporting set / state / codepoint (index) is indicated by a specific X-bit (e.g., having the lowest (or highest) index) in the field (furthermore, in this case, if any bit other than the specific X-bit is indicated as "1", PUSCH transmission is performed assuming that there is no CSI reporting indication for cell X, or it is assumed / operated under the assumption that there is no scheduling for cell X), or d) the indicator field is configured with Y-bits of a larger size for the cell subgroup, and PUSCH transmission is always performed assuming that there is no CSI reporting indication for cell X.

[0311] 2. The cell subgroup is considered / applied as a co-scheduled cell set (total of cells belonging to that set).

[0312] F.Beta_offset indicator

[0313] i.Opt 1: Apply the Shared-reference-cell method

[0314] 1. The value (beta offset) indicated in the DCI field is applied only to the PUSCH on a specific reference cell for which a dynamic beta offset indication is set (among cells scheduled by the multi-cell DCI), and operates to apply a specific semi-static beta offset value set separately or a specific (e.g., the lowest index) beta offset value among multiple candidate beta offsets (which can be dynamically indicated) to the PUSCHs on other cells.

[0315] a. The PUSCH on the reference cell is determined as follows: Alt 1) the PUSCH on the cell with the lowest cell index (among the cells scheduled with the same multi-cell DCI), or Alt 2) the PUSCH with the earliest starting symbol time (if there are multiple PUSCHs with the earliest starting symbol time, the PUSCH on the cell with the lowest cell index among the multiple PUSCHs is determined), or Alt 3) the PUSCH selected to multiplex the HARQ-ACK.

[0316] ii. Opt 2: Applying the Shared-single-cell method

[0317] 1. Only when one cell is scheduled (by multi-cell DCI) (or when one cell with a dynamic beta offset indication set is scheduled), the DCI field is configured (the value (beta offset) indicated thereby is applied to the PUSCH on that cell), and when multiple cells are scheduled (or when multiple cells are scheduled or when one cell with no dynamic beta offset indication set is scheduled), the DCI field is omitted without being configured (in this case, the DCI field operates to apply a specific semi-static beta offset value set separately for the PUSCH on the multiple cells or a specific beta offset value (e.g., having the lowest index) among multiple candidate beta offsets (which can be dynamically indicated)).

[0318] iii. Opt 3: Apply the Shared-state-extension method

[0319] 1. Each of the multiple states / code points that can be indicated by that DCI field is configured / set with a combination of multiple beta offset values ​​for multiple PUSCHs on multiple cells (not a beta offset value for a PUSCH on a single cell), thereby indicating a specific combination of beta offset values ​​(for multiple PUSCHs on multiple cells) by that one field.

[0320] iv.Opt 4: Apply the above Separate method

[0321] 1. For each cell scheduled by multi-cell DCI, an individual field is configured, and the size of the individual field is variable according to the number of scheduled cells (for example, the field size when the number of scheduled cells exceeds N (for example, N = 1) is configured to be smaller than when the number of scheduled cells is N or less (for example, N = 1)).

[0322] A. In this case, for example, when the number of the scheduled cells is N or less (for example, N = 1), the individual field for each cell is configured with K (for example, K = 2) bits, and one of 2K beta offset values (sets) is indicated by the field. On the other hand, when the number of scheduled cells exceeds N, the individual field for each cell is configured with L (L < K, for example, L = 1) bits, and one of 2L beta offset values (sets) is indicated by the field, resulting in such a structure.

[0323] v.Opt 5: Apply the Omit method

[0324] 1. The DCI field is not configured in the multi-cell DCI and is omitted (in this case, for the PUSCH on the cell scheduled by the multi-cell DCI, a specific semi-static beta offset value or a specific (for example, having the lowest index) beta offset value among a plurality of candidate betas that can be dynamically indicated is applied).

[0325] vi. Note 0: In this case, the specific reference cell is determined to be a specific cell among the cells in which a beta offset indicator is set (in the conventional single-cell (scheduling) DCI), and for convenience, the specific semi-static beta offset value set separately as described above or the specific beta offset value (e.g., having the lowest index) among multiple candidate beta offsets (which can be dynamically indicated) is referred to as a specific default beta offset value.

[0326] vii.Note 1: In this case, for cell A with a beta offset indicator set (in the conventional single-cell (scheduling) DCI) and cell B without a beta offset indicator set, it is configured / restricted so that only cell A or only cell B belongs to the same cell subgroup (i.e., cell A and cell B do not belong together), and with this configuration, the shared-reference-cell or shared-cell-common method is applied separately for each cell subgroup.

[0327] viii. Note 2: Alternatively, cell A and cell B can be set to belong to the same cell subgroup, and with this setting, the Shared-Reference-Cell or Shared-Cell-Common method can be applied separately for each cell subgroup.

[0328] 1. When the shared-cell-common method is applied to a cell subgroup to which both cell A and cell B belong as described above, a) the indicator field configuration is omitted for that cell subgroup, and the specific default beta offset value is always applied, or b) the indicator field is configured for that cell subgroup, and if only bit "0" is indicated by the field, the specific default beta offset value is applied to cell B, and if (at least one) bit "1" is indicated, the operation is performed in a state in which it is assumed / assumed that there is no scheduling for cell B, or c) the indicator field is configured for that cell subgroup, and the specific default beta offset value is always applied to cell B.

[0329] 2. The cell subgroup is considered / applied as a co-scheduled cell set (total of cells belonging to that set).

[0330] G.UL-SCH indicator

[0331] i.Opt 1: Apply the Shared-reference-cell method

[0332] 1. The value (presence or absence of UL-SCH) indicated in the DCI field applies only to the PUSCH on a specific reference cell (among the cells scheduled by the multi-cell DCI), and operates to transmit PUSCH under the assumption that UL-SCH transmission is indicated for PUSCHs on other cells.

[0333] a. The PUSCH on the reference cell is determined to be the PUSCH on the cell with the lowest (or highest) cell index (among cells scheduled with the same multi-cell DCI) Alt 1), or the PUSCH with the earliest (or latest) transmission starting symbol time (if there are multiple PUSCHs with the earliest (latest) starting symbol time, the PUSCH on the cell with the lowest (or highest) cell index among the multiple PUSCHs is determined).

[0334] ii. Opt 2: Applying the Shared-single-cell method

[0335] 1. Only when one cell is scheduled (by multi-cell DCI), the DCI field is configured (the value indicated thereby (presence or absence of UL-SCH) is applied to the PUSCH on that cell), and when multiple cells are scheduled, the DCI field is omitted without being configured (in this case, the PUSCH is transmitted under the assumption that UL-SCH transmission is indicated for the PUSCH on the multiple cells).

[0336] iii.Opt 3: Apply the above Omit method

[0337] 1. The DCI field is not configured in the multi-cell DCI and is omitted (in this case, the PUSCH is transmitted under the assumption that UL-SCH transmission is indicated for the PUSCH on the cell scheduled by the multi-cell DCI).

[0338] iv. Note A: In this case, the specific reference cell is determined to be a specific cell among the cells for which a CSI request / indicator is set (in the conventional single-cell (scheduling) DCI). For example, the reference cell is determined to be a cell with the smallest cell index for which a CSI request / indicator is set in a set of co-scheduled cells.

[0339] H.ChannelAccess-CPext-CAPC(LBT)

[0340] i.Opt 1: Apply the shared-cell-common method

[0341] 1. The values ​​(LBT method and related parameters) indicated in that DCI field are applied commonly to the PUSCHs on all cells (operating on unlicensed bands) (scheduled by the multi-cell DCI).

[0342] ii. Opt 2: Apply the Shared-reference-cell method

[0343] 1. The values ​​(LBT method and related parameters) indicated in the DCI field are applied only to the PUSCH on a specific reference cell (among the cells scheduled by the multi-cell DCI), and for the PUSCH on other cells, a combination of predefined / configured {LBT method (e.g., Type-1 LBT (based on random back-off)), CP extension parameter, CAPC} values ​​is applied to transmit the PUSCH.

[0344] iii. Opt 3: Applying the Shared-single-cell method

[0345] 1. Only when one cell is scheduled (by multi-cell DCI), the DCI field is configured (the values ​​indicated thereby (LBT method and related parameters) are applied to the PUSCH on that cell), and when multiple cells are scheduled, the DCI field is not configured and is omitted (in this case, for the PUSCH on the multiple cells, a combination of predefined / set {LBT method (e.g., Type-1 LBT (based on random backoff)), CP extension parameters, CAPC} values ​​is applied to transmit the PUSCH).

[0346] iv.Opt 4: Apply the above Omit method

[0347] 1. The DCI field is not configured and omitted in the multi-cell DCI (in this case, for the PUSCH on the cell scheduled by the multi-cell DCI, a combination of predefined / configured {LBT method (e.g., Type-1 LBT (based on random backoff)), CP extension parameter, CAPC} values ​​is applied to transmit the PUSCH).

[0348] v.Note 0: In this case, the specific reference cell is determined to be a specific cell among the cells for which a ChannelAccess-CPext-CAPC (LBT) indicator is set (in the conventional single-cell (scheduling) DCI), and as described above, a specific (default) predefined / configured {LBT method, CP extension parameters, CAPC} value combination is specified, for example, to the {LBT method, CP extension parameters, CAPC} combination set in the ChannelAccess-CPext-CAPC having a specific (e.g., highest or lowest) index (among the ChannelAccess-CPext-CAPC(index) set in the single-cell DCI).

[0349] vi.Note 1: In this case, cell X, whose ChannelAccess-CPext-CAPC(LBT) indicator field is set to a specific X-bit size (within the conventional single-cell (scheduling) DCI), and cell Y, whose ChannelAccess-CPext-CAPC(LBT) indicator field is set to a larger Y-bit size, are configured to belong to the same cell subgroup, and with this configuration, the shared-reference-cell or shared-cell-common method is applied separately for each cell subgroup.

[0350] 1. As described above, when the shared-cell-common method is applied to a cell subgroup to which cell X and cell Y both belong, a) the indicator field is configured with a smaller size of X-bits for that cell subgroup, and a specific (e.g., having the lowest (or highest) index) of 2^X ChannelAccess-CPext-CAPC(index) is to be applied to cell Y, and an indication for other ChannelAccess-CPext-CAPC(index) is omitted (i.e., it is assumed that there is no indication for other ChannelAccess-CPext-CAPC), or b) the indicator field is configured with a smaller size of X-bits for that cell subgroup, and the specific default ChannelAccess-CPext-CAPC is always applied to cell Y, or c) the indicator field is configured with a larger size of Y-bits for that cell subgroup, and ChannelAccess-CPext-CAPC(index) is indicated for cell X by a specific (e.g., having the lowest (or highest) index) X-bit in the field (and in this case, if other bits other than the specific X-bit are indicated to "1", the cell X or operate under the assumption that there is no scheduling for that cell X), or d) the indicator field is configured with a larger size of Y-bit for that cell subgroup and the specific default ChannelAccess-CPext-CAPC is always applied to cell X. For example, in FIG. 12, assume that the DCI field is the ChannelAccess-CPext-CAPC field (or the ChannelAccess-CPext field) and the shared-cell-common method is applied to the ChannelAccess-CPext-CAPC field.The size of the ChannelAccess-CPext-CAPC field is set independently in the single-cell scheduling DCI of each cell. For example, the ChannelAccess-CPext-CAPC field has size A in Cell#1 (active BWP), size B in Cell#2 (active BWP), size C in Cell#3 (active BWP), size D in Cell#4 (active BWP), size E in Cell#5 (active BWP), and size G in Cell#N (active BWP). Sizes A to G may be different from each other or may be partially the same, and may include size 0. If the union of the co-scheduled cell sets scheduled by the multi-cell scheduling DCI includes all of Cell#1 to Cell#N, the size of the ChannelAccess-CPext-CAPC field in the multi-cell scheduling DCI is Max{A, B, C, D, E,..., G}. If the union of co-scheduled cell sets scheduled by the multi-cell scheduling DCI includes only some of the cells Cell#1 to Cell#N, the size of the ChannelAccess-CPext-CAPC field in the multi-cell scheduling DCI is determined based on the cell having the largest ChannelAccess-CPext-CAPC field size in the union of co-scheduled cell sets. In other words, the size of the ChannelAccess-CPext-CAPC field in the multi-cell scheduling DCI is determined to be Max{value 1, value 2, value 3,....., value M}. Also, for example, the size of the ChannelAccess-CPext-CAPC field in the multi-cell scheduling DCI is k-bits, 0 to 2. k -1 indicates the state / code point, and 2 indicates the specific cell (active BWP) among the cells scheduled together k -m to 2 kIf there is no ChannelAccess-CPext-CAPC field setting for the state / codepoint that corresponds to -1, the terminal shall use 0 or 2 for the (active BWP of) a particular cell as in method c). k Either apply the state / codepoint corresponding to -m-1, or apply the default ChannelAccess-CPext-CAPC for the specific cell (active BWP) as in method d).

[0351] 2. The cell subgroup is considered / applied as a co-scheduled cell set (total of cells belonging to that set).

[0352] I. Open-loop power control (OLPC) parameter set indication

[0353] i.Opt 1: Apply the Shared-reference-cell method

[0354] 1. The value (OLPC parameter set index) indicated in the DCI field is applied only to the PUSCH on a specific reference cell (among the cells scheduled by the multi-cell DCI), and for the PUSCH on other cells, a specific pre-defined / configured OLPC parameter set (index) is applied to transmit the PUSCH.

[0355] ii. Opt 2: Applying the Shared-single-cell method

[0356] 1. Only when one cell is scheduled (by multi-cell DCI), the DCI field is configured (the value indicated thereby (OLPC parameter set index) is applied to the PUSCH on that cell), and when multiple cells are scheduled, the DCI field is not configured and is omitted (in this case, a specific OLPC parameter set (index) that has been predefined / set is applied to the PUSCH on the multiple cells to transmit the PUSCH).

[0357] iii.Opt 3: Apply the above Omit method

[0358] 1. The DCI field is not configured and is omitted in the multi-cell DCI (in this case, the PUSCH is transmitted by applying a specific OLPC parameter set (index) that is predefined / configured for the PUSCH on the cell scheduled by the multi-cell DCI).

[0359] iv. Note 0: In this case, the specific reference cell is determined to be a specific one of the cells for which an OLPC parameter set indicator is configured (in the conventional single-cell (scheduling) DCI), and as described above, a specific (default) OLPC parameter set is specified, for example, to be the OLPC parameter set with the lowest index (among the configured OLPC parameter sets).

[0360] v.Note 1: In this case, for cell A with an OLPC parameter set indicator configured (in the conventional single-cell (scheduling) DCI) and cell B without the OLPC parameter set indicator configured / restricted, only cell A or only cell B may belong to the same cell subgroup (i.e., cell A and cell B may not belong together), and with this configuration, the shared-reference-cell or shared-cell-common method is applied separately for each cell subgroup.

[0361] vi.Note 2: Alternatively, cell A and cell B can be set to belong to the same cell subgroup, and in this state, the shared-reference-cell or shared-cell-common method can be applied separately for each cell subgroup.

[0362] 1. As described above, when the shared-cell-common method is applied to a cell subgroup to which both cell A and cell B belong, a) the indicator field configuration is omitted for that cell subgroup and the specific default OLPC parameter set is always applied, or b) the indicator field is configured for that cell subgroup and, if only bit “0” is indicated by the field, the specific default OLPC parameter set is applied to cell B, and if (at least one) bit “1” is indicated, cell B operates in a state where it is considered / assumed that there is no scheduling, or c) the indicator field is configured for that cell subgroup and the specific default OLPC parameter set is always applied to cell B.

[0363] 2. The cell subgroup is considered / applied as a co-scheduled cell set (total of cells belonging to that set).

[0364] vii.Note 3: Furthermore, (in the conventional single-cell (scheduling) DCI) cell X with the OLPC parameter set indicator field set to a particular size X (e.g., 1-bit) and cell Y with the OLPC parameter set indicator field set to a larger size Y (e.g., 2-bit) are configured to belong to the same cell subgroup, and in this state, the shared-reference-cell or shared-cell-common method is applied separately for each cell subgroup.

[0365] 1. As described above, when the shared-cell-common method is applied to a cell subgroup to which cell X and cell Y both belong, a) the indicator field is configured with a smaller size X (e.g., 1-bit) for that cell subgroup, and indicates which of two specific OLPC parameter sets (e.g., having the lowest index and the second lowest index) to apply to cell Y, and the indication for the other OLPC parameter sets (indexes) is omitted (i.e., it is assumed that there is no indication for other OLPC parameter sets), or b) the indicator field is configured with a smaller size X (e.g., 1-bit) for that cell subgroup, and the specific default OLPC parameter set is always applied to cell Y, or c) the indicator field is configured with a larger size Y (e.g., 2-bit) for that cell subgroup, and the OLPC parameter set (index) is indicated for cell X by a specific 1-bit (e.g., MSB or LSB) in the field (furthermore, in this case, when a bit other than the specific 1-bit is indicated to "1", the specific default OLPC parameter set is applied to cell X, or the OLPC parameter set is not indicated to cell X). X), or d) the indicator field is configured with a larger size Y (e.g., 2-bit) for that cell subgroup, and the specific default OLPC parameter set is always applied to cell X. For example, in FIG. 12, assume that the DCI field is an OLPC parameter set indicator field for open loop power control, and the shared-cell-common method is applied to the OLPC parameter set indicator field.The size of the OLPC parameter set indicator field is set independently in the single-cell scheduling DCI of each cell. For example, the OLPC parameter set indicator field has size A in Cell#1 (active BWP), size B in Cell#2 (active BWP), size C in Cell#3 (active BWP), size D in Cell#4 (active BWP), size E in Cell#5 (active BWP), and size G in Cell#N (active BWP). Sizes A to G may be different from each other or may be partially the same, and may include size 0. If the union of the co-scheduled cell sets scheduled by the multi-cell scheduling DCI includes all of Cell#1 to Cell#N, the size of the OLPC parameter set indicator field in the multi-cell scheduling DCI is Max{A, B, C, D, E,...,G}. If the union of co-scheduled cell sets scheduled by the multi-cell scheduling DCI includes only some of the cells Cell#1 to Cell#N, the size of the OLPC parameter set indicator field in the multi-cell scheduling DCI is determined based on the cell having the largest OLPC parameter set indicator field size in the union of co-scheduled cell sets. In other words, the size of the OLPC parameter set indicator field in the multi-cell scheduling DCI is determined to be Max{value 1, value 2, value 3,...,value M}. For example, the size of the OLPC parameter set indicator field in the multi-cell scheduling DCI is k-bits, which is 0 to 2. k -1 indicates the state / code point, and 2 indicates the specific cell (active BWP) among the cells scheduled together k -m to 2 k If there is no OLPC Parameter Set Indicator field setting for the state / codepoint that corresponds to -1, the terminal shall use 0 or 2 for the (active BWP of) a particular cell, as in method c). kEither apply the state / codepoint corresponding to -m-1, or, as in method d), apply the default OLPC parameter set indicator for the specific cell (of its active BWP).

[0366] 2. The cell subgroup is considered / applied as a co-scheduled cell set (total of cells belonging to that set).

[0367] J. Priority indicator (PI)

[0368] i.Opt 1: Apply the shared-cell-common method

[0369] 1. The value (LP or HP) indicated in that DCI field is applied jointly to the PUSCH on all cells (scheduled by the multi-cell DCI), which are all cells (among the cells scheduled by the multi-cell DCI) with PI set.

[0370] a. On the other hand, if HP is indicated by the above field in the multi-cell DCI, for PUSCH on a cell for which PI is not set (among the cells scheduled by that DCI), either Alt 1) operates to transmit PUSCH assuming that there is no PI indication (or that it is indicated by LP), or Alt 2) operates to assume that there is no PUSCH scheduling for that cell (for which PI is not set) and drop PUSCH transmission on that cell.

[0371] b. On the other hand, if LP is indicated by the field in the multi-cell DCI, the Alt 1 operation is applied to PUSCH on cells (among the cells scheduled by that DCI) where PI is not set.

[0372] ii. Opt 2: Apply the Shared-reference-cell method

[0373] 1. The value (LP or HP) indicated in the DCI field applies only to the PUSCH on the specific reference cell (among the cells scheduled by the multi-cell DCI) for which the PI is set, and the operations of Alt 1 and / or Alt 2 apply to the PUSCH on other cells.

[0374] iii. Opt 3: Applying the Shared-single-cell method

[0375] 1. If only one cell is scheduled (by a multi-cell DCI) (or one cell with a PI set is scheduled), then the DCI field is configured (and the value indicated thereby (LP or HP) is applied to the PUSCH on that cell); if multiple cells are scheduled (or multiple cells are scheduled or one cell with no PI set is scheduled), then the DCI field is not configured and is omitted (in this case the behavior of Alt 1 applies).

[0376] iv.Opt 4: Apply the above Omit method

[0377] 1. The DCI field is not configured in the multi-cell DCI and is omitted (in this case, the behavior of Alt 1 above applies).

[0378] v. Note 0: In this case, the specific reference cell is determined to be a specific cell among the cells for which a priority indicator is set (in the conventional single-cell (scheduling) DCI).

[0379] vi.Note 1: In this case, for cell A with a priority indicator set (in the conventional single-cell (scheduling) DCI) and cell B without a priority indicator set, it is set / restricted so that only cell A or only cell B belongs to the same cell subgroup (i.e., neither cell A nor cell B belongs to the same cell subgroup), and in this state, the shared-reference-cell or shared-cell-common method is applied separately for each cell subgroup. For example, if all cells belonging to a co-scheduled cell set indicated by a multi-cell DCI are cell A with a priority indicator set, the priority (e.g., HP or LP) indicated by the priority indicator field in the DCI is assumed / applied to the PDSCH / PUSCH on all cells belonging to the co-scheduled cell set.

[0380] vii.Note 2: Alternatively, cell A and cell B can be set to belong to the same cell subgroup, and in this state, the Shared-Reference-Cell or Shared-Cell-Common method can be applied separately for each cell subgroup.

[0381] 1. As described above, when the shared-cell-common method is applied to a cell subgroup to which cell A and cell B belong, a) the indicator field configuration is omitted for that cell subgroup, and it always operates in a state where it is assumed / assumed to be indicated by the LP. For example, if at least one cell belonging to a co-scheduled cell set scheduled / indicated by a multi-cell DCI is cell A with a priority indicator (PI) set (in the case of a single-cell DCI), and at least one cell is cell B with no PI set (in the case of a single-cell DCI), the UE / base station operates to assume / apply the same priority (e.g., LP) for DL / UL signal scheduling (e.g., PDSCH / PUSCH) of all cells belonging to the co-scheduled cell set (e.g., in a state where it is assumed that a specific priority (e.g., LP) is indicated by the PI field in the multi-cell DCI). The PI field configuration / indication itself is omitted in the multi-cell DCI, or the PI field is still configured / indicated in the multi-cell DCI, but the terminal / base station operates to ignore the PI field. Alternatively, when the shared-cell-common method is applied to a cell subgroup to which cell A and cell B both belong, b) the indicator field is configured for the cell subgroup and when the HP is indicated by the field, the terminal / base station operates in a state in which it is considered / assumed that there is no scheduling for cell B, or c) the indicator field is configured for the cell subgroup and the terminal / base station operates in a state in which it is considered / assumed that the LP is always indicated for cell B.

[0382] 2. The cell subgroup is considered / applied as a co-scheduled cell set (total of cells belonging to that set).

[0383] K. Invalid symbol pattern indicator

[0384] i.Opt 1: Apply the Shared-reference-cell method

[0385] 1. The value (invalid symbol pattern) indicated in the DCI field is applied only to the PUSCH on a specific reference cell (among the cells scheduled by the multi-cell DCI) for which an invalid symbol pattern is set, and the PUSCH on other cells is transmitted under the assumption that there is no invalid symbol pattern indication.

[0386] ii. Opt 2: Applying the Shared-single-cell method

[0387] 1. Only when one cell is scheduled (by multi-cell DCI) (or when one cell with an invalid symbol pattern set is scheduled), the DCI field is configured (the value indicated thereby (the invalid symbol pattern) is applied to the PUSCH on that cell), and when multiple cells are scheduled (or when multiple cells are scheduled or when one cell with no invalid symbol pattern set is scheduled), the DCI field is not configured and is omitted (in this case, the PUSCH is transmitted under the assumption that there is no invalid symbol pattern indication for the PUSCH on the multiple cells).

[0388] iii.Opt 3: Apply the above Omit method

[0389] 1. The DCI field is not configured in the multi-cell DCI and is omitted (in this case, it is assumed that there is no invalid symbol pattern indication for the PUSCH on the cell scheduled by the multi-cell DCI, and the PUSCH is transmitted).

[0390] iv.Opt 4: Apply the above Separate method

[0391] 1. For each cell scheduled by multi-cell DCI, an individual field is configured, and the size of the individual field is variable according to the number of scheduled cells (for example, the field size when the number of scheduled cells exceeds N is configured to be smaller than when the number of scheduled cells is N or less (e.g., N = 1)).

[0392] a. In this case, for example, when the number of the scheduled cells is N or less (e.g., N = 1), an individual field for each cell is composed of K bits, and one of 2K invalid symbol patterns is indicated by the field. On the other hand, when the number of scheduled cells exceeds N, an individual field for each cell is composed of L bits (L < K), and one of 2L invalid symbol patterns is indicated by the field.

[0393] v. Opt 5: Apply the said Shared-state-extension method

[0394] 1. Each of the multiple states / code points that can be indicated by the DCI field is configured / set by a combination of multiple invalid symbol patterns for multiple PUSCHs on multiple cells (not an invalid symbol pattern for PUSCH on a single cell), whereby a specific combination of invalid symbol patterns (for multiple PUSCHs on multiple cells) is indicated by one field.

[0395] vi. Note 0: In this case, the specific reference cell is determined to be a specific one of the cells in which an invalid symbol pattern indicator is set in the conventional single-cell (scheduling) DCI.

[0396] vii.Note 1: In this case, for cell A with an invalid symbol pattern indicator set (in the conventional single-cell (scheduling) DCI) and cell B without the invalid symbol pattern indicator set, it is configured / restricted so that only cell A or only cell B belongs to the same cell subgroup (i.e., cell A and cell B do not belong together), and with this configuration, the shared-reference-cell or shared-cell-common method is applied separately for each cell subgroup.

[0397] viii. Note 2: Alternatively, cell A and cell B can be set to belong to the same cell subgroup, and in this state, the Shared-Reference-Cell or Shared-Cell-Common method can be applied separately for each cell subgroup.

[0398] 1. As described above, when the shared-cell-common method is applied to a cell subgroup to which cell A and cell B both belong, a) the indicator field configuration is omitted for that cell subgroup, and PUSCH transmission is performed under the assumption that there is no invalid symbol pattern indication, or b) the indicator field is configured for that cell subgroup, and when the field indicates bit "1", it operates in a state in which it is considered / assumed that there is no scheduling for cell B, or c) the indicator field is configured for that cell subgroup, and PUSCH transmission is performed under the assumption that there is no invalid symbol pattern indication for cell B.

[0399] 2. The cell subgroup is considered / applied as a co-scheduled cell set (total of cells belonging to that set).

[0400] 13 is a diagram illustrating an example of signal reception by a terminal based on at least a portion of the above-described embodiment. The above content can be referred to for understanding FIG. 13 without any special explanation.

[0401] The terminal monitors physical downlink control channel (PDCCH) candidates (1305).

[0402] The terminal detects downlink control information (DCI) through monitoring of the PDCCH candidates (1310).

[0403] The DCI may support multi-cell scheduling based on a plurality of cells configured in the UE. The DCI may include a first DCI field commonly configured for co-scheduled cells. based on that the plurality of serving cells include a first cell and a second cell, and that a configuration related to a size of the first DCI field is M-bit for scheduling of the first cell and N-bit for scheduling of the second cell, respectively: the size of the first DCI field commonly configured for the co-scheduled cells may be determined as a lager one of the M-bit and the N-bit.

[0404] The first DCI field includes at least one of a field related to antenna port information, a field related to SRS (sounding reference signal) resource information, a field related to information related to precoding and number of layers, a field related to beta offset information, an OLPC (Open-loop power control parameter set indication) field, and a field related to information related to channel access and CP (cyclic prefix).

[0405] The first DCI field indicates one codepoint common to the co-scheduled cells, the indicated one codepoint and the mapped parameters are configured separately for each of the co-scheduled cells, and a table providing the mapped parameters for each scheduled cell for each codepoint in the first DCI field is configured in the terminal.

[0406] The size of the first DCI field is determined based on the cell among the plurality of cells that has the largest setting regarding the size of the first DCI field.

[0407] The DCI includes a second DCI field that is applied to a reference cell of any one of the co-scheduled cells.

[0408] The reference cell is the cell having the smallest serving cell index among the co-scheduled cells.

[0409] The second DCI field includes a channel state information (CSI) request field.

[0410] The terminal obtains CSI for the CSI request field based on channel state information-reference signal (CSI-RS) information for the reference cell having the smallest serving cell index among the co-scheduled cells.

[0411] The terminal transmits a CSI report related to the CSI request field via a physical uplink shared channel (PUSCH) on the reference cell having the smallest serving cell index among the co-scheduled cells.

[0412] 14 is an example of a signal transmission by a base station based on at least a part of the above-described embodiment. The above content can be referred to for understanding FIG. 14 without special description.

[0413] The base station generates downlink control information (DCI) (1405). The DCI supports multi-cell scheduling based on a plurality of cells configured for the terminal. The DCI includes a first DCI field configured in common for co-scheduled cells. The plurality of cells include a first cell and a second cell, and the settings regarding the size of the first DCI field are M-bits for the scheduling of the first cell and N-bits for the scheduling of the second cell, respectively: the size of the first DCI field configured in common for the co-scheduled cells is determined by the larger one of the M-bits and the N-bits.

[0414] The base station transmits (1410) the DCI to the terminal based on at least one of the terminal's physical downlink control channel (PDCCH) candidates.

[0415] The first DCI field includes at least one of a field related to antenna port information, a field related to SRS (sounding reference signal) resource information, a field related to information related to precoding and number of layers, a field related to beta offset information, an OLPC (Open-loop power control parameter set indication) field, and a field related to information related to channel access and CP (cyclic prefix).

[0416] The first DCI field indicates one code point common to the co-scheduled cells, and the indicated one code point and a mapped parameter are configured separately for each of the co-scheduled cells, and the base station configures a table in the terminal that provides a mapped parameter for each scheduled cell for each code point in the first DCI field.

[0417] The size of the first DCI field is determined based on the cell among the plurality of cells that has the largest setting regarding the size of the first DCI field.

[0418] The DCI includes a second DCI field that is applied to a reference cell of any one of the co-scheduled cells.

[0419] The reference cell is the cell having the smallest serving cell index among the co-scheduled cells.

[0420] The second DCI field includes a channel state information (CSI) request field.

[0421] CSI for the CSI request field is determined based on channel state information-reference signal (CSI-RS) information for the reference cell having the smallest serving cell index among the co-scheduled cells.

[0422] The base station receives a CSI report for the CSI request field via a physical uplink shared channel (PUSCH) on the reference cell having the smallest serving cell index among the co-scheduled cells.

[0423] FIG. 15 illustrates a communication system 1 to which the present invention can be applied.

[0424] Referring to FIG. 15, the communication system 1 includes wireless devices, base stations, and networks. Here, the wireless devices refer to devices that communicate using wireless connection technology (e.g., 5G NR, LTE), and are also referred to as communication / wireless / 5G devices. The wireless devices include, but are not limited to, a robot 100a, vehicles 100b-1, 100b-2, an XR (eXtended Reality) device 100c, a handheld device (Hand-held Device) 100d, a home appliance 100e, an IoT (Internet of Thing) device 100f, and an AI server / device 400. For example, the vehicles include vehicles equipped with wireless communication functions, autonomous vehicles, vehicles capable of inter-vehicle communication, and the like. Here, the vehicles include UAVs (Unmanned Aerial Vehicles) (e.g., drones). XR devices include Augmented Reality (AR) / Virtual Reality (VR) / Mixed Reality (MR) devices, and are embodied in the form of Head-Mounted Devices (HMDs), Head-Up Displays (HUDs) mounted on vehicles, TVs, smartphones, computers, wearable devices, home appliances, digital billboards, vehicles, robots, etc. Portable devices include smartphones, smart pads, wearable devices (e.g., smart watches, smart glasses), computers (e.g., notebook computers, etc.), etc. Home appliances include TVs, refrigerators, washing machines, etc. IoT devices include sensors, smart meters, etc. For example, base stations and networks may also be embodied as wireless devices, and a specific wireless device 200a may operate as a base station / network node for other wireless devices.

[0425] The wireless devices 100a to 100f are connected to a network 300 via a base station 200. AI (Artificial Intelligence) technology is applied to the wireless devices 100a to 100f, and the wireless devices 100a to 100f are connected to an AI server 400 via the network 300. The network 300 is configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. The wireless devices 100a to 100f can communicate with each other via the base station 200 / network 300, but can also communicate directly without going through the base station / network (e.g., sidelink communication). For example, the vehicles 100b-1 and 100b-2 can communicate directly (e.g., V2V (Vehicle to Vehicle) / V2X (Vehicle to everything) communication). Also, an IoT device (e.g., a sensor) can directly communicate with another IoT device (e.g., a sensor) or another wireless device 100a to 100f.

[0426] Wireless communication / connections 150a, 150b, and 150c are performed between the wireless devices 100a to 100f / base stations 200 and the base stations 200. Here, the wireless communication / connections are performed by various wireless connection technologies such as uplink / downlink communication 150a and sidelink communication 150b (or D2D communication) and communication between base stations 150c (e.g., relay, IAB (Integrated Access Backhaul) (e.g., 5G NR). Through the wireless communication / connections 150a, 150b, and 150c, the wireless devices and base stations, and the base stations and base stations can transmit / receive wireless signals to each other. For example, the wireless communication / connections 150a, 150b, and 150c can transmit / receive signals via various physical channels. To this end, based on various proposals of the present invention, any one of various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel coding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and resource allocation processes is performed.

[0427] FIG. 16 illustrates a wireless device to which the present invention can be applied.

[0428] 16, a first wireless device 100 and a second wireless device 200 transmit and receive wireless signals according to various wireless access technologies (e.g., LTE, NR), where {first wireless device 100, second wireless device 200} corresponds to {wireless device 100x, base station 200} and / or {wireless device 100x, wireless device 100x} in FIG.

[0429] The first wireless device 100 includes one or more processors 102 and one or more memories 104, and further includes one or more transceivers 106 and / or one or more antennas 108. The processor 102 is configured to control the memory 104 and / or the transceiver 106 to implement the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein. For example, the processor 102 processes information in the memory 104 to generate a first information / signal, and then transmits a wireless signal including the first information / signal via the transceiver 106. The processor 102 also receives a wireless signal including a second information / signal via the transceiver 106, and then stores information obtained from signal processing of the second information / signal in the memory 104. The memory 104 is coupled to the processor 102 and stores various information related to the operation of the processor 102. For example, the memory 104 stores software code including instructions for performing some or all of the processes controlled by the processor 102 or for performing the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein. Here, the processor 102 and memory 104 are part of a communication modem / circuit / chip designed to implement a wireless communication technology (e.g., LTE, NR). The transceiver 106 is coupled to the processor 102 and transmits and / or receives wireless signals via one or more antennas 108. The transceiver 106 includes a transmitter and / or a receiver. The transceiver 106 may also be referred to as an RF (radio frequency) unit. In this specification, a wireless device may also refer to a communication modem / circuit / chip.

[0430] The second wireless device 200 includes one or more processors 202 and one or more memories 204, and further includes one or more transceivers 206 and / or one or more antennas 208. The processor 202 is configured to control the memory 204 and / or the transceiver 206 to implement the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein. For example, the processor 202 processes information in the memory 204 to generate a third information / signal, and then transmits a wireless signal including the third information / signal via the transceiver 206. The processor 202 also receives a wireless signal including a fourth information / signal via the transceiver 206, and then stores information obtained from the signal processing of the fourth information / signal in the memory 204. The memory 204 is coupled to the processor 202 and stores various information related to the operation of the processor 202. For example, the memory 204 stores software code including instructions for performing some or all of the processes controlled by the processor 202 or for performing the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein. Here, the processor 202 and memory 204 are part of a communication modem / circuit / chip designed to implement a wireless communication technology (e.g., LTE, NR). The transceiver 206 is coupled to the processor 202 and transmits and / or receives wireless signals via one or more antennas 208. The transceiver 206 includes a transmitter and / or a receiver. The transceiver 206 may also be referred to as an RF unit. In this specification, a wireless device may also refer to a communication modem / circuit / chip.

[0431] The hardware elements of the wireless device 100, 200 are described in more detail below. One or more protocol layers may be implemented by one or more processors 102, 202, without limitation. For example, the one or more processors 102, 202 may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP). The one or more processors 102, 202 may generate one or more Protocol Data Units (PDUs) and / or one or more Service Data Units (SDUs) according to the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein. The one or more processors 102, 202 may generate messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein. The one or more processors 102, 202 may generate and provide signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data or information according to the functions, procedures, suggestions, and / or methods disclosed herein to the one or more transceivers 106, 206. The one or more processors 102, 202 may receive signals (e.g., baseband signals) from the one or more transceivers 106, 206 and derive the PDUs, SDUs, messages, control information, data or information according to the descriptions, functions, procedures, suggestions, methods and / or flowcharts disclosed herein.

[0432] The one or more processors 102, 202 may also be referred to as controllers, microcontrollers, microprocessors, or microcomputers. The one or more processors 102, 202 may be implemented using hardware, firmware, software, or a combination thereof. As an example, the one or more processors 102, 202 may include 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). The descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, and the like. The firmware or software configured to perform the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein may be included in the one or more processors 102, 202, or may be stored in one or more memories 104, 204 and run by the one or more processors 102, 202. The descriptions, functions, procedures, suggestions, methods and / or flow charts disclosed in this specification may be embodied using firmware or software in the form of code, instructions and / or sets of instructions.

[0433] The one or more memories 104, 204 may be coupled to the one or more processors 102, 202 and may store various forms of data, signals, messages, information, programs, code, instructions, and / or commands. The one or more memories 104, 204 may be comprised of ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer readable storage media, and / or combinations thereof. The one or more memories 104, 204 may be located internal and / or external to the one or more processors 102, 202. Additionally, the one or more memories 104, 204 may be coupled to the one or more processors 102, 202 via various techniques, such as wired or wireless connections.

[0434] One or more transceivers 106, 206 may transmit user data, control information, wireless signals / channels, etc., as described in the methods and / or flow charts, etc., herein to one or more other devices. One or more transceivers 106, 206 may receive user data, control information, wireless signals / channels, etc., as described in the descriptions, functions, procedures, suggestions, methods and / or flow charts, etc., disclosed herein from one or more other devices. For example, one or more transceivers 106, 206 may be coupled to one or more processors 102, 202 and may transmit and receive wireless signals. For example, one or more processors 102, 202 may control one or more transceivers 106, 206 to transmit user data, control information, or wireless signals to one or more other devices. Also, one or more processors 102, 202 may control one or more transceivers 106, 206 to receive user data, control information, or wireless signals from one or more other devices. Furthermore, the one or more transceivers 106, 206 are coupled to one or more antennas 108, 208, and the one or more transceivers 106, 206 are configured to transmit and receive user data, control information, radio signals / channels, etc., as referred to in the descriptions, functions, procedures, suggestions, methods and / or flow charts disclosed herein, via the one or more antennas 108, 208. In this specification, the one or more antennas are multiple physical antennas or multiple logical antennas (e.g., antenna ports). The one or more transceivers 106, 206 convert the received user data, control information, radio signals / channels, etc., from RF band signals to baseband signals for processing using the one or more processors 102, 202. The one or more transceivers 106, 206 convert the user data, control information, radio signals / channels, etc., processed using the one or more processors 102, 202, from baseband signals to RF band signals. For this purpose, the one or more transceivers 106, 206 include (analog) oscillators and / or filters.

[0435] 17 shows another example of a wireless device to which the present invention is applied. The wireless device may be embodied in various forms depending on the use case / service (see FIG. 15).

[0436] Referring to Fig. 17, the wireless devices 100 and 200 correspond to the wireless devices 100 and 200 of Fig. 16 and are composed of various elements, components, units / parts and / or modules. For example, the wireless devices 100 and 200 include a communication unit 110, a control unit 120, a memory unit 130 and an additional element 140. The communication unit includes a communication circuit 112 and a transceiver 114. For example, the communication circuit 112 includes one or more processors 102 and 202 and / or one or more memories 104 and 204 in Fig. 16. For example, the transceiver 114 includes one or more transceivers 106 and 206 and / or one or more antennas 108 and 208 in Fig. 16. The control unit 120 is electrically connected to the communication unit 110, the memory unit 130 and the additional element 140 and controls the overall operation of the wireless device. For example, the control unit 120 controls electrical / mechanical operations of the wireless device based on the programs / codes / commands / information stored in the memory unit 130. In addition, the control unit 120 transmits information stored in the memory unit 130 to the outside (e.g., another communication device) via the communication unit 110 through a wireless / wired interface, or stores information received from the outside (e.g., another communication device) via the communication unit 110 through a wireless / wired interface in the memory unit 130.

[0437] The additional element 140 may be configured in various ways depending on the type of wireless device. For example, the additional element 140 may include any one of a power unit / battery, an input / output unit (I / O unit), a driving unit, and a computer unit. The wireless device may be embodied in the form of, but not limited to, a robot (FIG. 15, 100a), a vehicle (FIG. 15, 100b-1, 100b-2), an XR device (FIG. 15, 100c), a mobile device (FIG. 15, 100d), a home appliance (FIG. 15, 100e), an IoT device (FIG. 15, 100f), a digital broadcasting terminal, a hologram device, a public safety device, an MTC device, a medical device, a Fintech device (or a financial device), a security device, a climate / environment device, an AI server / device (FIG. 15, 400), a base station (FIG. 15, 200), and a network node. The wireless device may be mobile or fixed depending on the use case / service.

[0438] In FIG. 17, the various elements, components, units / sections and / or modules within the wireless devices 100, 200 are all coupled to each other by wired interfaces or at least some are wirelessly coupled to each other by a communication unit 110. For example, in the wireless devices 100 and 200, the control unit 120 and the communication unit 110 are connected by wire, and the control unit 120 and a first unit (e.g., 130, 140) are connected wirelessly via the communication unit 110. In addition, each element, component, unit / part and / or module in the wireless devices 100 and 200 further includes one or more elements. For example, the control unit 120 is composed of a set of one or more processors. For example, the control unit 120 is composed of a set of a communication control processor, an application processor, an ECU (Electronic control Unit), a graphics processor, a memory control processor, etc. As another example, the memory unit 130 is composed of 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.

[0439] 18 is a diagram illustrating a vehicle or an autonomous vehicle to which the present invention is applied. The vehicle or the autonomous vehicle may be realized as a mobile robot, a car, a train, an aerial vehicle (AV), a ship, or the like.

[0440] 18, a vehicle or autonomous vehicle 100 includes 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 is configured as a part of the communication unit 110. Blocks 110 / 130 / 140a to 140d correspond to blocks 110 / 130 / 140 in FIG. 17, respectively.

[0441] The communication unit 110 transmits and receives signals (e.g., data, control signals, etc.) to and from external devices such as other vehicles, base stations (e.g., base stations, road side units, etc.), and servers. The control unit 120 controls elements of the vehicle or autonomous vehicle 100 to perform various operations. The control unit 120 includes an ECU (Electronic Control Unit). The driving unit 140a causes the vehicle or autonomous vehicle 100 to run on the ground. The driving unit 140a includes an engine, a motor, a power train, wheels, brakes, a steering device, etc. The power supply unit 140b supplies power to the vehicle or autonomous vehicle 100 and includes wired / wireless charging circuits, a battery, etc. The sensor unit 140c can obtain vehicle status, surrounding environment information, user information, etc. The sensor unit 140c includes an IMU (inertial measurement unit) sensor, a collision sensor, a wheel sensor, a speed sensor, a tilt sensor, a weight sensor, a heading sensor, a position module, a vehicle forward / reverse sensor, a battery sensor, a fuel sensor, a tire sensor, a steering sensor, a temperature sensor, a humidity sensor, an ultrasonic sensor, an illuminance sensor, a pedal position sensor, etc. The autonomous driving unit 140d embodies a technology for maintaining a lane while driving, a technology for automatically adjusting speed such as an adaptive cruise control, a technology for automatically driving according to a predetermined route, a technology for automatically setting a route when a destination is set, and the like.

[0442] For example, the communication unit 110 receives map data, traffic information data, etc. from an external server. The autonomous driving unit 140d generates an autonomous driving route and a drive plan based on the obtained data. The control unit 120 controls the driving unit 140a (e.g., speed / direction adjustment) so that the vehicle or autonomous driving vehicle 100 moves along the autonomous driving route according to the drive plan. The communication unit 110 non-periodically obtains the latest traffic information data from an external server during autonomous driving, and also obtains surrounding traffic information data from surrounding vehicles. In addition, the sensor unit 140c obtains vehicle status and surrounding environment information during autonomous driving. The autonomous driving unit 140d updates the autonomous driving route and the drive plan based on the newly obtained data / information. The communication unit 110 transmits information regarding the vehicle position, the autonomous driving route, the drive plan, etc. to the external server. The external server can predict traffic information data in advance using AI technology, etc. based on information collected from the vehicle or autonomous driving vehicle, and provide the predicted traffic information data to the vehicle or autonomous driving vehicle.

[0443] FIG. 19 is a diagram for explaining a DRX (Discontinuous Reception) operation of a terminal according to one embodiment of the present invention.

[0444] A terminal can perform DRX operation while executing the procedures and / or methods described / proposed above. A terminal configured for DRX can reduce power consumption by discontinuously receiving DL signals. DRX is performed in RRC (Radio Resource Control)_IDLE state, RRC_INACTIVE state, and RRC_CONNECTED state. DRX in the RRC_IDLE state and RRC_INACTIVE state is used to discontinuously receive paging signals. DRX performed in the RRC_CONNECTED state will be described below (RRC_CONNECTED DRX).

[0445] Referring to FIG. 19, the DRX cycle consists of On Duration and Opportunity for DRX. The DRX cycle defines a time interval in which On Duration is repeated periodically. On Duration indicates a time period in which the terminal monitors to receive the PDCCH. When DRX is configured, the terminal performs PDCCH monitoring during On Duration. If there is a successfully detected PDCCH during PDCCH monitoring, the terminal operates an inactivity timer and maintains an awake state. On the other hand, if there is no successfully detected PDCCH during PDCCH monitoring, the terminal enters a sleep state after the On Duration ends. Thus, when DRX is configured, PDCCH monitoring / reception is performed discontinuously in the time domain when performing the above-described / proposed procedure and / or method. For example, when DRX is configured, in this specification, PDCCH reception opportunities (e.g., slots having a PDCCH search space) are configured discontinuously according to the DRX configuration. On the other hand, when DRX is not configured, PDCCH monitoring / reception is performed continuously in the time domain when performing the above / proposed procedures and / or methods. For example, in this specification, PDCCH reception opportunities (e.g., slots having PDCCH search space) are configured continuously when DRX is not configured. On the other hand, PDCCH monitoring may be restricted in the time period configured in the measurement gap regardless of whether DRX is configured or not.

[0446] Table 9 shows the process of the terminal related to DRX (RRC_CONNECTED state). Referring to Table 9, DRX configuration information is received via higher layer (e.g., RRC) signaling, and DRX ON / OFF is controlled by a DRX command of the MAC layer. If DRX is configured, the terminal can perform PDCCH monitoring discontinuously when performing the procedures and / or methods described / proposed in the present invention.

[0447] [Table 9]

[0448] Here, MAC-CellGroupConfig includes configuration information required to set MAC (Medium Access Control) parameters for a cell group. MAC-CellGroupConfig may include configuration information related to DRX. For example, MAC-CellGroupConfig includes the following information in the definition of DRX:

[0449] - Value of drx-OnDurationTimer: defines the length of the start period of the DRX cycle

[0450] - Value of drx-InactivityTimer: defines the length of the time interval in which the UE is in an awake state after a PDCCH opportunity in which a PDCCH indicating initial UL or DL ​​data is detected

[0451] - Value of drx-HARQ-RTT-TimerDL: defines the length of the maximum time interval after a DL initial transmission is received until a DL retransmission is received.

[0452] - Value of drx-HARQ-RTT-TimerDL: defines the length of the maximum time interval between when a grant for a UL initial transmission is received and when a grant for a UL retransmission is received.

[0453] - drx-LongCycleStartOffset: defines the length and start time of a DRX cycle

[0454] - drx-ShortCycle(optional): defines the time length of a short DRX cycle

[0455] Here, if any one of the drx-OnDurationTimer, drx-InactivityTimer, drx-HARQ-RTT-TimerDL, and drx-HARQ-RTT-TimerDL is operating, the terminal maintains an active state and performs PDCCH monitoring at every PDCCH opportunity.

[0456] The above-described embodiments are combinations of the components and features of the present invention in a predetermined form. Each component or feature should be considered as optional unless otherwise expressly stated. Each component or feature may be implemented in a form not combined with other components or features. Also, some components and / or features may be combined to form an embodiment of the present invention. The order of each operation described in the embodiments of the present invention may be changed. Some configurations or features of any embodiment may be included in other embodiments, or may be replaced with corresponding configurations or features of other embodiments. It is obvious that claims that are not explicitly cited in the claims may be combined to form an embodiment, or may be included as a new claim by amendment after filing.

[0457] It is obvious to those skilled in the art that the present invention can be embodied in other specific forms without departing from the characteristics of the present invention. Therefore, the above detailed description should not be interpreted as limiting in all respects, but should be considered as illustrative. The scope of the present invention should be determined by reasonable interpretation of the appended claims, and all modifications within the equivalent scope of the present invention are included in the scope of the present invention. [Industrial Applicability]

[0458] The present invention can be used in a terminal, a base station or other equipment of a wireless mobile communication system.

Claims

1. A method for a terminal (UE) receiving a signal in a wireless communication system, comprising: Monitoring physical downlink control channel (PDCCH) candidates; and Detecting downlink control information (DCI) by monitoring the PDCCH candidates; The DCI supports multi-cell scheduling based on a plurality of cells configured for the terminal, The DCI includes a first DCI field commonly configured for co-scheduled cells, Based on the fact that the plurality of cells includes a first cell and a second cell, and each of the settings regarding the size of the first DCI field is M-bits for scheduling of the first cell and N-bits for scheduling of the second cell, A method according to claim 1, wherein a size of the first DCI field commonly configured for the co-scheduled cells is determined by the larger of the M-bits and the N-bits.

2. The first DCI field is The method of claim 1, comprising at least one of a field for antenna port information, a field for sounding reference signal (SRS) resource information, a field for information on precoding and the number of layers, a field for beta offset information, an open-loop power control parameter set indication (OLPC), and a field for information on channel access and cyclic prefix (CP).

3. the first DCI field indicates a code point common to the co-scheduled cells; The method of claim 1 , wherein the indicated one code point and the mapped parameters are configured separately for each of the co-scheduled cells.

4. The method of claim 3, wherein a table is configured in the terminal providing, for each codepoint of the first DCI field, parameters mapped to each scheduled cell.

5. The method of claim 1 , wherein the size of the first DCI field is determined based on a cell among the plurality of cells that has a maximum setting regarding the size of the first DCI field.

6. The DCI includes a second DCI field that is applied to a reference cell of any one of the co-scheduled cells; The method of claim 1 , wherein the reference cell is the cell having the smallest serving cell index among the co-scheduled cells.

7. The method of claim 6, wherein the second DCI field comprises a channel state information (CSI) request field.

8. The method of claim 7, wherein the terminal obtains CSI for the CSI request field based on channel state information-reference signal (CSI-RS) information for the reference cell having a smallest serving cell index among the co-scheduled cells.

9. The method of claim 7, wherein the terminal transmits a CSI report regarding the CSI request field via a physical uplink shared channel (PUSCH) on the reference cell having a minimum serving cell index among the co-scheduled cells.

10. A computer-readable recording medium having recorded thereon a program for carrying out the method according to claim 1.

11. A device for wireless communication, comprising: A memory for storing instruction words; A processor that operates by executing the instructions, The operations of the processor include: 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 multiple cells configured in the device; The DCI includes a first DCI field configured in common for co-scheduled cells; Based on the fact that the plurality of cells includes a first cell and a second cell, and each of the settings regarding the size of the first DCI field is M-bits for scheduling of the first cell and N-bits for scheduling of the second cell, The size of the first DCI field commonly configured for the co-scheduled cells is determined by the larger of the M-bits and the N-bits.

12. a transceiver for transmitting or receiving wireless signals under the control of said processor; The device of claim 11, wherein the device is a terminal (UE) in a wireless communication system.

13. The device according to claim 11, wherein the device is an application specific integrated circuit (ASIC) or a digital signal processing device for controlling a terminal (UE).

14. 1. A method for a base station to transmit a signal in a wireless communication system, comprising: generating downlink control information (DCI); and transmitting the DCI to the terminal based on at least one of a physical downlink control channel (PDCCH) candidate of the terminal; The DCI supports multi-cell scheduling based on a plurality of cells configured for the terminal; The DCI includes a first DCI field configured in common for co-scheduled cells; Based on the fact that the plurality of cells includes a first cell and a second cell, and each of the settings regarding the size of the first DCI field is M-bits for scheduling of the first cell and N-bits for scheduling of the second cell, A method according to claim 1, wherein a size of the first DCI field commonly configured for the co-scheduled cells is determined by the larger of the M-bits and the N-bits.

15. A base station for transmitting a signal in a wireless communication system, comprising: A transceiver; a processor for generating downlink control information (DCI) and transmitting the DCI by the transceiver to the terminal based on at least one of physical downlink control channel (PDCCH) candidates for the terminal; The DCI includes a first DCI field configured in common for co-scheduled cells; Based on the fact that the plurality of cells includes a first cell and a second cell, and each of the settings regarding the size of the first DCI field is M-bits for scheduling of the first cell and N-bits for scheduling of the second cell, A base station, wherein a size of the first DCI field commonly configured for the co-scheduled cells is determined by the larger one of the M-bits and the N-bits.

Images