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

Abstract

In the wireless communication system according to the present invention, the method and apparatus for transmitting and receiving signals operate based on different timeline configurations. In particular, the timeline associated with PDCCH reception, PDSCH reception, and HARQ-ACK transmission, the timeline associated with PDCCH reception, PUSCH transmission, and the timeline associated with PDCCH reception, CSI-RS reception, and CSI reporting can be modified for SCS configuration 5 or 6.

Description

[Technical Field]

[0001] The present invention relates to a method and apparatus for use 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. Generally, wireless communication systems are multiple access systems that can support communication with multiple users by sharing available system resources (e.g., 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] A technical problem to be solved by the present invention is to provide a signal transmission / reception method and apparatus for efficiently transmitting and receiving control signals and data signals in a wireless communication system.

[0004] The technical object of the present invention is not limited to the above-mentioned technical object, and other technical objects can be inferred from the embodiments of the present invention. [Means for solving the problem]

[0005] The present invention provides a method and apparatus for transmitting and receiving signals in a wireless communication system.

[0006] According to one embodiment of the present invention, a method for transmitting and receiving signals by a terminal in a wireless communication system includes the steps of receiving a Physical Downlink Control Channel (PDCCH) triggering aperiodic Channel State Information (CSI) report; receiving a CSI-Reference Signal (CSI-RS) based on the PDCCH; and transmitting a Physical Uplink Shared Channel (PUSCH) including a CSI report based on a measurement result for the CSI-RS, wherein a first Subcarrier Spacing (SCS) setting is used for the PDCCH, a second SCS setting is used for the CSI-RS, and a third SCS setting is used for the PUSCH, a CSI computation delay requirement 1 requires a lower delay than a CSI computation delay requirement 2 for the same SCS setting, and a transport block (TB) or a Hybrid Automatic Repeat and Request (HARQ-ACK) is used for the PUSCH. A signal transmission and reception method is provided in which no SCS (Signal Response Communication Scheme Acknowledgement) is included, no CPU is occupied for the terminal, and a CSI calculation delay requirement of 2 is used based on at least one of a first SCS setting, a second SCS setting, and a third SCS setting being 5 or 6.

[0007] In another embodiment of the present invention, an apparatus, a processor, and a storage medium for performing a signal transmission and reception method are provided.

[0008] The apparatus includes an autonomous vehicle capable of communicating with at least a terminal, a network, and other autonomous vehicles other than the apparatus.

[0009] The above-described aspects of the present invention are merely some of the preferred embodiments of the present invention, and various embodiments reflecting the technical features of the present invention will be apparent to those skilled in the art based on the detailed description of the present invention below. [Effects of the Invention]

[0010] According to one embodiment of the present invention, when control signals and data signals are transmitted and received between communication devices, there is an advantage that more efficient signal transmission and reception can be achieved through operations differentiated from conventional inventions.

[0011] The technical effects of the present invention are not limited to the above-mentioned technical effects, and other technical effects may be inferred from the embodiments of the present invention. [Brief explanation of the drawings]

[0012] [Figure 1] 1 shows an example of the structure of a radio frame. [Figure 2] 1 shows an example of a resource grid for slots. [Figure 3] 1 shows an example of mapping physical channels into slots. [Figure 4] An example of an ACK / NACK transmission process is shown below. [Figure 5] 1 shows an example of a PUSCH (Physical Uplink Shared Channel) transmission process. [Figure 6-9] 1 illustrates an example of a signal transmission and reception method according to an embodiment of the present invention. [Figure 10-13] 1 illustrates an example of an apparatus according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0013] The following technologies can be used for various wireless access systems, such as CDMA, FDMA, TDMA, OFDMA, SC-FDMA, etc. CDMA can be implemented by radio technologies such as UTRA (Universal Terrestrial Radio Access) and CDMA2000. TDMA can be implemented by radio technologies such as GSM (Global System for Mobile communications), GPRS (General Packet Radio Service), and EDGE (Enhanced Data Rates for GSM Evolution). OFDMA can be implemented by radio technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, E-UTRA (Evolved UTRA), etc. UTRA is part of UMTS (Universal Mobile Telecommunications System). 3GPP (3rd Generation Partnership Project) (registered trademark: the same applies hereinafter) LTE (long term evolution) is a part of E-UMTS (Evolved UMTS) that uses E-UTRA, and LTE-A / LTE-A pro are evolved versions of 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is an evolved version of 3GPP LTE / LTE-A / LTE-A pro.

[0014] For clarity, the following description will be based on 3GPP communication systems (e.g., LTE and NR), but the technical concept of the present invention is not limited thereto. LTE refers to technology from 3GPP TS 36.xxx Release 8 onward. Specifically, LTE technology from 3GPP TS 36.xxx Release 10 onward is called LTE-A, and LTE technology from 3GPP TS 36.xxx Release 13 onward is called LTE-A pro. 3GPP NR refers to technology from TS 38.xxx Release 15 onward. LTE / NR can also be referred to as a 3GPP system. "xxx" refers to the detailed number of the standard document. LTE / NR is collectively referred to as a 3GPP system. For background technology, terms, abbreviations, etc. used in the description of the present invention, please refer to the matters described in standard documents published before the present invention. For example, the following documents may be referenced:

[0015] 3GPP NR

[0016] - 38.211: Physical channels and modulation

[0017] - 38.212: Multiplexing and channel coding

[0018] - 38.213: Physical layer procedures for control

[0019] - 38.214: Physical layer procedures for data

[0020] - 38.300: NR and NG-RAN Overall Description

[0021] - 38.331: Radio Resource Control (RRC) protocol specification

[0022] FIG. 1 shows an example of the structure of a radio frame used in NR.

[0023] In NR, uplink (UL) and downlink (DL) transmissions are organized into 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 regular CP is used, each slot contains 14 symbols. If an extended CP is used, each slot contains 12 symbols. Here, a symbol can include an OFDM symbol (or a CP-OFDM symbol) or an SC-FDMA symbol (or a DFT-s-OFDM symbol).

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

[0025] [Table 1]

[0026] Table 2 illustrates how 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 an extended CP is used.

[0027] [Table 2]

[0028] In an NR system, multiple cells merged to one user equipment (UE) are configured to have different OFDM(A) pneumatics (e.g., SCS, CP length, etc.), which results in different (absolute time) durations of time resources (e.g., SF, slot, or TTI) (collectively referred to as TU (Time Unit) for convenience) consisting of the same number of symbols.

[0029] NR supports multiple Orthogonal Frequency Division Multiplexing (OFDM) pneumonologies (e.g., subcarrier spacing, SCS) to support various 5G services. For example, a 15 kHz SCS supports wide areas in traditional cellular bands, while a 30 kHz / 60 kHz SCS supports dense urban areas, lower latency, and wider carrier bandwidths.

[0030] The NR frequency band is defined by two types of frequency ranges (FR) (FR1 / FR2). FR1 / FR2 are configured as shown in Table 3 below. FR2 also stands for millimeter wave (mmW).

[0031] [Table 3]

[0032] Figure 2 shows an example of the slot structure of an NR frame.

[0033] A slot contains multiple symbols in the time domain. For example, in the case of a general CP, one slot contains 14 symbols, while in the case of an extended CP, one slot contains 12 symbols. A carrier contains multiple subcarriers in the frequency domain. An RB (Resource Block) is defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. Multiple RB interlaces (or simply, interlaces) are defined in the frequency domain. Interlace m ∈ [0, 1, ..., M-1] consists of (common) RBs [m, M+m, 2M+m, 3M+m, ...], where M represents the number of interlaces. A BWP (Bandwidth Part) is defined as multiple consecutive RBs (e.g., physical RBs, PRBs) in the frequency domain and can correspond to one OFDM numerology (e.g., SCS(u), CP length, etc.). A carrier contains up to N (e.g., 5) BWPs. Data communication is performed using the activated BWP, and only one BWP can be activated for one terminal within one cell / carrier. Each element in the resource grid is called a resource element (RE), and one modulation symbol can be mapped to it.

[0034] In a wireless communication system, a terminal receives information from a base station via a downlink (DL), and the terminal transmits information to the base station via an uplink (UL). Information exchanged between the base station and the terminal includes data and various control information, and various physical channels / signals exist depending on the type / purpose of the information exchanged. A physical channel corresponds to a set of resource elements (RE) that carry information derived from a higher layer. A physical signal corresponds to a set of resource elements (RE) used by a physical layer (PHY), but does not carry information derived from a higher layer. Higher layers include a medium access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, a radio resource control (RRC) layer, etc.

[0035] DL physical channels include PBCH (Physical Broadcast channel), PDSCH (Physical Downlink Shared channel), and PDCCH (Physical Downlink Control channel). DL physical signals include DL RS (Reference Signal), PSS (Primary synchronization signal), and SSS (Secondary synchronization signal). DL RSs include DM-RS (Demodulation RS), PT-RS (Phase-tracking RS), and CSI-RS (Channel-state information RS). UL physical channels include PRACH (Physical Random Access Channel), PUSCH (Physical Uplink Shared Channel), and PUCCH (Physical Uplink Control Channel). UL physical signals include UL RSs. UL RSs include DM-RS, PT-RS, and SRS (Sounding RS).

[0036] FIG. 3 shows an example of mapping physical channels within a slot.

[0037] A single slot contains the DL control channel, DL or UL data, and UL control channel. For example, the first N symbols in a slot are used to transmit the DL control channel (hereinafter referred to as the DL control region), and the last M symbols in the slot are used to transmit the UL control channel (hereinafter referred to as the UL control region). N and M are integers equal to or greater than 0. The resource region between the DL control region and the UL control region (hereinafter referred to as the data region) is used to transmit DL data or UL data. A time gap exists between the control region and the data region for DL-to-UL or UL-to-DL switching. The PDCCH is transmitted in the DL control region, and the PDSCH is transmitted in the DL data region. Some symbols at the time of switching from DL to UL within a slot are used as the time gap.

[0038] The base station of the present invention is, for example, a gNodeB.

[0039] Uplink (UL) physical channels / signals

[0040] (1) PUSCH

[0041] The PUSCH carries uplink data (e.g., 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 a DFT-s-OFDM waveform, the terminal applies transform precoding to transmit the PUSCH. For 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. The PUSCH is dynamically scheduled by the PDCCH (dynamic scheduling) or semi-statically scheduled based on higher layer (e.g., RRC) signaling (and / or Layer 1 (L1) signaling (e.g., PDCCH)) (Configured Scheduling, CS). Therefore, in dynamic scheduling, PUSCH transmission is accompanied by the PDCCH, while in CS, PUSCH transmission is not accompanied by the PDCCH. CS includes Type-1 CG (Configured Grant) PUSCH transmission and Type-2 CG PUSCH transmission. In Type-1 CG, all parameters for PUSCH transmission are signaled by a higher layer. In Type-2 CG, some parameters for PUSCH transmission are signaled by a higher layer, and the rest are signaled by the PDCCH. Basically, in CS, PUSCH transmission is not accompanied by the PDCCH.

[0042] (2) PUCCH

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

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

[0045] - HARQ-ACK (Hybrid Automatic Repeat and reQuest Acknowledgement): A reception acknowledgement signal for DL ​​signals (e.g., PDSCH, SPS release PDCCH). HARQ-ACK responses include positive ACK (simply ACK), negative ACK (NACK), DTX (Discontinuous Transmission), or NACK / DTX. HARQ-ACK is also used interchangeably with A / N, ACK / NACK, HARQ-ACK / NACK, etc. HARQ-ACK is generated on a TB-by-TB / CBG-by-CBG basis.

[0046] CSI (Channel Status Information): Feedback information for the DL channel. CSI includes CQI (Channel Quality Information), RI (Rank Indicator), PMI (Precoding Matrix Indicator), PTI (Precoding Type Indicator), etc.

[0047] Table 4 shows examples of PUCCH formats. PUCCH formats are classified according to the UCI payload size, transmission length (e.g., the number of symbols constituting the PUCCH resource), and transmission structure. PUCCH formats are classified into Short PUCCH (formats 0 and 2) and Long PUCCH (formats 1, 3, and 4) according to the transmission length.

[0048] [Table 4]

[0049] (0) PUCCH Format 0 (PF0)

[0050] - Supported UCI payload size: up to K bits (e.g., K = 2)

[0051] - Number of OFDM symbols constituting a single PUCCH: 1 to X symbols (e.g., X = 2)

[0052] - Transmission structure: Consists of only UCI signals without DM-RS, and transmits UCI status by selecting and transmitting one of multiple sequences

[0053] (1) PUCCH Format 1 (PF1)

[0054] - Supported UCI payload size: up to K bits (e.g., K = 2)

[0055] - Number of OFDM symbols constituting a single PUCCH: Y to Z symbols (e.g., Y = 4, Z = 14)

[0056] - Transmission structure: DM-RS and UCI are configured in TDM format on different OFDM symbols, and UCI is a form in which a specific sequence is modulated (e.g., QPSK) symbols are multiplied. CS (cyclic shift) / OCC (orthogonal cover code) is applied to both UCI and DM-RS, and CDM is supported between multiple PUCCH resources (according to PUCCH format 1) (within the same RB).

[0057] (2) PUCCH Format 2 (PF2)

[0058] - Supported UCI payload size: K bits or more (e.g., K=2)

[0059] - Number of OFDM symbols constituting a single PUCCH: 1 to X symbols (e.g., X = 2)

[0060] - Transmission structure: DMRS and UCI are configured / mapped in the same symbol in the form of FDM, and the coded UCI bits are transmitted by applying only IFFT without DFT.

[0061] (3) PUCCH Format 3 (PF3)

[0062] - Supported UCI payload size: K bits or more (e.g., K=2)

[0063] - Number of OFDM symbols constituting a single PUCCH: Y to Z symbols (e.g., Y = 4, Z = 14)

[0064] - Transmission structure: DMRS and UCI are configured / mapped to different symbols in TDM format, and the coded UCI bits are transmitted after applying DFT. OCC is applied to UCI before DFT, and CS (or IFDM mapping) is applied to DMRS, supporting multiplexing to multiple terminals.

[0065] (4) PUCCH Format 4 (PF4)

[0066] - Supported UCI payload size: K bits or more (e.g., K=2)

[0067] - Number of OFDM symbols constituting a single PUCCH: Y to Z symbols (e.g., Y = 4, Z = 14)

[0068] - Transmission structure: DMRS and UCI are configured / mapped to different symbols in TDM format, and the coded UCI bits are transmitted without inter-terminal multiplexing by applying DFT.

[0069] Downlink (DL) physical channels / signals

[0070] (1) PDSCH

[0071] The PDSCH carries downlink data (e.g., DL-shared channel transport block (DL-SCH TB)). The TB is encoded into a codeword (CW) and then transmitted after undergoing scrambling and modulation processes. The CW includes one or more code blocks (CB). One or more CBs are grouped into a CBG (CB group). Depending on the cell configuration, the PDSCH can carry up to two CWs. Scrambling and modulation are performed for each CW, and the modulation symbols generated from each CW are mapped to one or more layers. Each layer is precoded, mapped to resources along with DMRS, and transmitted from the corresponding antenna port. The PDSCH is dynamically scheduled by the PDCCH (configured scheduling) or semi-statically scheduled (configured scheduling, CS) based on higher layer (e.g., RRC) signaling (and / or Layer 1 (L1) signaling (e.g., PDCCH)). Therefore, in dynamic scheduling, PDSCH transmission is accompanied by PDCCH, whereas in CS, PDSCH transmission is not accompanied by PDCCH. CS includes SPS (semi-persistent scheduling).

[0072] (2) PDCCH

[0073] 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, frequency / time resource allocation information for the UL-SCH (shared channel), paging information for the PCH (paging channel), system information on the DL-SCH, frequency / time resource allocation information for higher layer control messages such as a voluntary access response (RAR) transmitted on the PDSCH, transmit power control commands, and information on activation / deactivation of SPS / CS (Configured Scheduling). Various DCI formats are provided depending on the information in the DCI.

[0074] Table 5 illustrates an example of a DCI format transmitted via the PDCCH.

[0075] [Table 5]

[0076] 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 (DL grant DCI). DCI formats 0_0 / 0_1 are referred to as UL grant DCI or UL scheduling information, and DCI formats 1_0 / 1_1 are referred to as DL grant DCI or UL scheduling information. DCI format 2_0 is used to convey dynamic slot format information (e.g., dynamic SFI) to a UE, and DCI format 2_1 is used to convey downlink pre-emption information to a UE. 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 as one group.

[0077] The PDCCH / 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 Cell-RNTI (C-RNTI). If the PDCCH is related to paging, the CRC is masked to a P-RNTI (Paging-RNTI). If the PDCCH is related to system information (e.g., System Information Block, SIB), the CRC is masked to a System Information RNTI (SI-RNTI). If the PDCCH is related to an unsolicited access response, the CRC is masked to a Random Access-RNTI (RA-RNTI).

[0078] Table 6 shows an example of the use and transmission channel of the PDCCH according to the RNTI. The transmission channel indicates the transmission channel related to the data carried by the PDSCH / PUSCH scheduled by the PDCCH.

[0079] [Table 6]

[0080] The modulation method of the PDCCH is fixed (e.g., Quadrature Phase Shift Keying, QPSK), and one PDCCH consists of 1, 2, 4, 8, or 16 CCEs (Control Channel Elements) depending on the AL (Aggregation Level). One CCE consists of six REGs (Resource Element Groups). One REG is defined by one OFDM symbol and one (P)RB.

[0081] The PDCCH is transmitted in a CORESET (Control Resource Set). The CORESET corresponds to a set of physical resources / parameters used to carry the PDCCH / DCI in the BWP. For example, the CORESET includes a REG set having a predetermined pneumatics (e.g., SCS, CP length, etc.). The CORESET is configured by system information (e.g., MIB) or UE-specific higher layer (e.g., RRC) signaling. Examples of parameters / information used to configure the CORESET are as follows: One or more CORESETs are configured for one UE, and multiple CORESETs are superimposed in the time / frequency domain.

[0082] - controlResourceSetId: Indicates the identification information (ID) of the CORESET.

[0083] - frequencyDomainResources: Indicates the frequency domain resources of CORESET. It is indicated by a bitmap, and each bit corresponds to an RB group (= 6 consecutive RBs). For example, the MSB (Most Significant Bit) of the bitmap corresponds to the first RB group in the BWP. The RB group corresponding to the bit whose bit value is 1 is assigned to the frequency domain resources of CORESET.

[0084] - duration: indicates the time domain resource of CORESET. It indicates the number of consecutive OFDMA symbols that make up CORESET. For example, duration has a value of 1 to 3.

[0085] - cce-REG-MappingType: Indicates the CCE-to-REG mapping type. Interleaved and non-interleaved types are supported.

[0086] - precoderGranularity: indicates the precoder granularity in the frequency domain.

[0087] - tci-StateSPDCCH: Indicates information (e.g., TCI-StateID) indicating the TCI (Transmission Configuration Indication) state for the PDCCH. The TCI state is used to provide the Quasi-Co-Location (QCL) relationship between DL RSs and PDCCH DMRS ports within the RS set (TCI-State).

[0088] - tci-PresentInDCI: Indicates whether the TCI field in the DCI is included or not.

[0089] - pdcch-DMRS-ScramblingID: indicates information used to initialize the PDCCH DMRS scrambling sequence.

[0090] To receive the PDCCH, the UE monitors (e.g., blindly decodes) a set of PDCCH candidates in the CORESET. The PDCCH candidates indicate the CCEs that the UE monitors for PDCCH reception / detection. PDCCH monitoring is performed in one or more CORESETs on an active DL BWP in each activated cell where PDCCH monitoring is configured. The set of PDCCH candidates that the UE monitors is defined as a PDCCH Search Space (SS) set. The SS set is a Common Search Space (CSS) set or a UE-specific Search Space (USS) set.

[0091] Table 7 illustrates the PDCCH search space.

[0092] [Table 7]

[0093] The SS set is configured by system information (e.g., MIB) or UE-specific higher layer (e.g., RRC) signaling. S (e.g., 10) or less SS sets are configured for each DL BWP of the serving cell. For example, the following parameters / information are provided for each SS set: Each SS set is associated with one CORESET, and each CORESET configuration is associated with one or more SS sets.

[0094] - searchSpaceId: Indicates the ID of the SS set.

[0095] - controlResourceSetId: Indicates the CORESET associated with the SS set.

[0096] - monitoringSlotPeriodicityAndOffset: Indicates the PDCCH monitoring periodicity period (slot unit) and the PDCCH monitoring period offset (slot unit).

[0097] - monitoringSymbolsWithinSlot: Indicates the first OFDMA symbol for PDCCH monitoring within a slot where PDCCH monitoring is configured. It is indicated by a bitmap, and each bit corresponds to each OFDMA symbol within the slot. The MSB of the bitmap corresponds to the first OFDMA symbol within the slot. The OFDMA symbol corresponding to a bit whose bit value is 1 corresponds to the first symbol of CORESET within the slot.

[0098] - nrofCandidates: Indicates the number of PDCCH candidates for AL=[1, 2, 4, 8, 16] (e.g., any one of 0, 1, 2, 3, 4, 5, 6, 8).

[0099] - searchSpaceType: Indicates whether the SS type is CSS or USS.

[0100] - DCI format: Indicates the DCI format of the PDCCH candidate.

[0101] Based on the CORESET / SS set configuration, a terminal can monitor PDCCH candidates in one or more SS sets within a slot. An opportunity (e.g., time / frequency resource) for monitoring PDCCH candidates is defined as a PDCCH (monitoring) opportunity. One or more PDCCH (monitoring) opportunities are configured within a slot.

[0102] 4 illustrates an ACK / NACK transmission process. Referring to FIG. 4, a UE detects a PDCCH in slot #n. Here, the PDCCH includes downlink scheduling information (e.g., DCI format 1_0, 1_1), and indicates a DL allocation-to-PDSCH offset (K0) and a PDSCH-HARQ-ACK reporting offset (K1). For example, DCI formats 1_0, 1_1 include the following information:

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

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

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

[0106] Hereinafter, the UE receives the PDSCH in slot #(n+K0) according to the scheduling information of slot #n, and then transmits UCI via the PUCCH in slot #(n+K1). Here, the UCI includes a HARQ-ACK response for the PDSCH. If the PDSCH is configured to transmit up to one TB, the HARQ-ACK response consists of one bit. If the PDSCH is configured to transmit up to two TBs, the HARQ-ACK response consists of two bits if spatial bundling is not configured, and one 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 responses for multiple PDSCHs.

[0107] 5 shows an example of a PUSCH transmission process. Referring to FIG. 5, a UE detects a PDCCH in slot #n. Here, the PDCCH includes uplink scheduling information (e.g., DCI formats 0_0 and 0_1). The DCI formats 0_0 and 0_1 include the following information:

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

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

[0110] After this, the terminal transmits a PUSCH in slot #(n+K2) according to the scheduling information for slot #n, where the PUSCH includes a UL-SCH TB.

[0111] 1. Timeline in the high frequency range

[0112] The above content can be applied in combination with the method proposed in the present invention to be described later, or is supplemented to clarify the technical features of the method proposed in the present invention.

[0113] Furthermore, the method described below can be similarly applied to the aforementioned NR system (licensed band) or shared spectrum, and it goes without saying that it can be modified or substituted to suit the terms, expressions, structures, etc. defined in each system so that the technical ideas proposed in the present invention can be embodied in the relevant system.

[0114] The NR system supports multiple pneumothoraxes (or subcarrier spacing, SCS) to support various 5G services. For example, a 15 kHz SCS supports wide areas in traditional cellular bands, a 30 kHz / 60 kHz SCS supports dense urban areas, lower latency, and wider carrier bandwidths, and an SCS of 60 kHz or higher supports bands above 24.25 GHz. Until Release 16, NR frequency bands were defined as two types of frequency ranges (FR1 and FR2) and are configured as shown in Table 3. In addition, discussions are underway to support the NR system in frequency bands above the FR1 / FR2 bands (e.g., 52.6 GHz to 71 GHz).

[0115] A frequency band higher than the FR1 and FR2 bands (for example, 52.6 GHz to 114.25 GHz band, particularly 52.6 GHz to 71 GHz) is referred to as FR2-2. The waveform, SCS, CP length, timing, etc. defined for FR1 and FR2 in conventional NR systems do not need to apply to FR2-2.

[0116] For NR operation in the 52.6 GHz band and above, SCSs of 120 kHz, 480 kHz, and 960 kHz are used. For the newly introduced 480 kHz and 960 kHz SCSs, the OFDM symbol length is shorter than that of 120 kHz (e.g., 1 / 4 for 480 kHz and 1 / 8 for 960 kHz). The shorter symbol and slot lengths can cause changes in various timelines, such as PDCCH / PDSCH processing time and PDSCH / PUSCH preparation time. Furthermore, due to the characteristics of the band, the significant impact of phase noise further increases the time required for inter-carrier interference (ICI) compensation during PDSCH decoding in the UE. Meanwhile, the newly introduced operation of multi-PDSCH scheduling by single DCI increases PDCCH processing time. Additionally, changes are expected when configuring the time (number of symbols and / or slots) required for PDSCH-to-HARQ-ACK (K1). Changes in the timeline are necessary to reduce the burden on UE implementation complexity due to the short symbol / slot time. This requires changes to the PDSCH processing time (N1), PUSCH preparation time (N2), and HARQ-ACK processing time (N3) for NR operation in the corresponding band. Changes are also required for the slot offset (K0) from DL grant reception to PDSCH reception, the slot offset (K1) from PDSCH reception to HARQ-ACK transmission, and the slot offset (K2) from UL grant reception to PUSCH transmission. Furthermore, changes are also required to the timeline between the DCI (or PDCCH) that triggers CSI-RS, the CSI-RS and / or CSI-IM signals transmitted as a result of the trigger, and / or the UL channel containing the CSI report.

[0117] This invention describes the newly introduced SCS (e.g., 480, 960 kHz) and the resulting shortened symbol / slot length in NR operation at high frequencies (e.g., 52.6 GHz or higher) / wideband, as well as the timeline changes and specific methods for setting K0, K1, and K2 values. Furthermore, this invention describes the timeline of DCI triggering CSI-RS, CSI-RS / IM signals linked thereto, and PUSCH transmitting the corresponding CSI report.

[0118] 1.1. How to change the range of K1 values ​​to match the range of N1 values

[0119] 1.1.1-1. DCI Format 1_0

[0120] When PDSCH scheduling is performed using DCI format 1_0, the PDSCH-to-HARQ_feedback timing indicator field indicates one of the values ​​[1, 2, 3, 4, 5, 6, 7, 8] using 3 bits. The PDSCH-to-HARQ_feedback timing indicator field is hereinafter also referred to as the K1 field. The indicated value indicates the slot interval between the last slot of the PDSCH received by the UE and the PUCCH (or PUSCH) slot that transmits the HARQ-ACK associated with the PDSCH. Meanwhile, the UE reports the time required for PDSCH reception, PDSCH decoding, and HARQ-ACK processing to the base station. Let N1 be the time required for the UE to receive the PDSCH, decode the PDSCH, and process the HARQ-ACK. N1 is expressed in symbol units. After the N1 value is reported, the base station sets the PDSCH-to-HARQ_feedback value to be equal to or greater than the corresponding absolute time, thereby setting the slot offset between the PDSCH and PUCCH (or PUSCH, including HARQ-ACK for PDSCH). When a high SCS (e.g., 480 or 960 kHz) is set in the 52.6 GHz band, the slot length is very short and it takes a long time for the terminal to prepare HARQ-ACK after receiving the PDSCH, so the value of 1 among [1, 2, 3, 4, 5, 6, 7, 8] in the K1 field may not actually be usable.

[0121] Table 8 shows the defined N1 values ​​in Table 5.3-1: PDSCH processing time for PDSCH processing capability 1 of conventional 3GPP 38.214.

[0122] [Table 8]

[0123] If the SCS (or pneumology) is 960 kHz (in this case, μ=6), the value will be much greater than 20. For example, if N1>28, values ​​of 2 or less among the PDSCH-to-HARQ_feedback field values ​​are unnecessary. Therefore, it is useful to interpret the value of the HARQ_feedback field differently depending on the value of N1 so that a more required value is indicated instead of an unused value. By using the following two methods, it is possible to set another value as K1 instead of a small value that is not used depending on N1 while using the PDSCH-to-HARQ_feedback field as it is (i.e., without increasing the value and the number of bits (bitwidth)).

[0124]

number

[0125]

number

[0126] In 1.1-(1) and 1.1-(2), c is semi-statically set by RRC, MAC CE, etc., or dynamically set by DCI. The default c value is 14, which is the number of symbols per slot. Method 1.1-(1) for determining K1 is a method of adding the smallest integer equal to or greater than N1 / c to the K1 field value using a ceiling function, while method 1.1-(2) for determining K1 is a method of adding the largest integer equal to or less than N1 / c to the K1 field value using a floor function. When N1 is a multiple of c, the K1 field values ​​determined by 1.1-(1) and 1.1-(2) are the same. As a specific example, when c=14, the K1 value is determined as follows according to 1.1-(2) depending on the range of N1 values:

[0127] If N1 is less than 14, then K1 = [1, 2, 3, 4, 5, 6, 7, 8]

[0128] If N1 is greater than or equal to 14 and less than 28, K1 = [2, 3, 4, 5, 6, 7, 8, 9]

[0129] If N1 is greater than or equal to 28 and less than 42, K1 = [3, 4, 5, 6, 7, 8, 9, 10]

[0130] ...

[0131] Alternatively, when c=14, according to method (1), the K1 value is determined as follows depending on N1:

[0132] If N1 is 14 or less, K1 = [2, 3, 4, 5, 6, 7, 8, 9]

[0133] If N1 is greater than 14 and less than or equal to 28, K1 = [3, 4, 5, 6, 7, 8, 9, 10]

[0134] If N1 is greater than 28 and less than or equal to 42, K1 = [4, 5, 6, 7, 8, 9, 10, 11]

[0135] ...

[0136] 1.1.1-2. DCI Format 1_1 and DCI Format 1_2

[0137] When a PDSCH is scheduled by a DCI format other than DCI format 1_0, or when an SPS PDSCH release is scheduled by DCI, the bit width and value of the K1 field are determined using dl-DataToUL-ACK, dl-DataToUL-ACK-r16, or dl-DataToUL-ACKForDCIFormat1_2 configured by the RRC information element (IE) PUCCH-Config. In this case, the K1 value is also set by adding ceil(N1 / c) or floor(N1 / c) to the K1 field value using methods 1.1-(1) and 1.1-(2) for calculating K1 in 1.1.1-1.

[0138] 1.1.1-3. When the DCI format does not have the PDSCH-to-HARQ_Feedback timing indicator field

[0139] If the DCI format for scheduling PDSCH scheduling or SPS PDSCH release does not have a K1 field, dl-DataToUL-ACK, dl-DataToUL-ACK-r16, or dl-DataToUL-ACKForDCIFormat1_2 configured by the RRC IE PUCCH-Config is used to set K1. In this case, as in 1.1.1-1, the K1 value is set by adding ceil(N1 / c) or floor(N1 / c) to the value indicated in dl-DataToUL-ACK, dl-DataToUL-ACK-r16, or dl-DataToUL-ACKForDCIFormat1_2.

[0140] 1.1.1-4. SPS PDSCH reception

[0141] Furthermore, even if a K1 field is present in a DCI format that activates SPS PDSCH reception, X can be added to the K1 field value to define a larger offset between the SPS PDSCH reception ending slot and the PUCCH transmission slot. In this case, X can be in the form of ceil(N1 / c) or floor(N1 / c) as in (Method 1.1.1-1), and the c value is set by RRC / DCI, etc. Alternatively, the X value may be pre-defined as a specific number without using N1 and c, or may be set by higher layer signaling such as RRC.

[0142] Furthermore, methods 1.1.1-1 through 1.1.1-4 may be configured to operate only at a specific SCS (e.g., 480 or 960 kHz). Also, methods 1.1.1-1 through 1.1.1-4 may be configured to operate only when N1 is equal to or greater than a specific value. Furthermore, methods 1.1-(1) and 1.1-(2) of 1.1.1-1 may be configured using different c values, and then the K1 settings by methods 1.1-(1) and 1.1-(2) may be switched. In this case, a switch flag is indicated by the DCI.

[0143] To apply methods 1.1.1-1 to 1.1.1-4, the N1 value (for 480 kHz and / or 960 kHz SCS) can have two different values ​​depending on the dmrs-AdditionalPosition value: If dmrs-AdditionalPosition='pos0' in DMRS-DownlinkConfig, a relatively aggressive (shorter) processing time is applied; if dmrs-AdditionalPosition≠'pos0' or if the higher-layer parameter is not configured, a relatively short processing time is applied.

[0144] For example, for 480 kHz and / or 960 kHz SCS used in the FR2-2 band, the N1 value is defined to two different values ​​depending on the dmrs-AdditionalPosition value, as shown in Table 9.

[0145] Table 9 shows the newly defined N1 values ​​for 480 kHz and / or 960 kHz SCS used in the FR2-2 band in relation to Table 5.3-1: PDSCH processing time for PDSCH processing capability 1 of 3GPP 38.214.

[0146] [Table 9]

[0147] As a result, the ceil(N1 / c) or floor(N1 / c) shown in the proposed methods in 1.1.1-1 to 1.1.1-4 is applied by selecting one of two different newly defined N1 values ​​(using several methods described below).

[0148] (Method 1.1.2-1) The first method is to select N1 to be used in ceil(N1 / c) or floor(N1 / c) depending on the dmrs-AdditionalPosition value, as well as the condition that N1 is divided into two different values. That is, when calculating ceil(N1 / c) or floor(N1 / c) in the methods of 1.1.1-1 to 1.1.1-4, if "dmrs-AdditionalPosition = pos0 in DMRS-DownlinkConfig in both of dmrs-DownlinkForPDSCH-MappingTypeA, dmrs-DownlinkForPDSCH-MappingTypeB", the N1 value on the left side of Table 9 is used, and if "dmrs-AdditionalPosition ≠ pos0 in DMRS-DownlinkConfig in either dmrs-DownlinkForPDSCH-MappingTypeA, dmrs-DownlinkForPDSCH-MappingTypeB or if the higher layer parameter is not configured", the N1 value on the right side of Table 9 is used. Just as two different N1 values ​​are defined depending on the configuration of Additional DMRS, the smaller of the two N1 values ​​is used to determine the offset for K1 (or K1) for a PDSCH in which Additional DMRS is configured / not used, and the larger of the two N1 values ​​is used to determine the offset for K1 (or PDSCH-to-HARQ_feedback timing indicator) for a PDSCH in which Additional DMRS is configured / used. In this case, the latter (e.g., the N1 value on the right side of Table 9) is used as the base value. In other words, since the base setting of dmrs-AdditionalPosition is pos2, the base value of K1 (or PDSCH-to-HARQ_feedback timing indicator) is also determined based on N1 when it is the base value of dmrs-AdditionalPosition.

[0149] (Method 1.1.2-2) The second method is to use the larger of the two N1 values ​​regardless of the dmrs-AdditionalPosition value. As an example of this, in methods 1.1.1-1 to 1.1.1-4 (using the N1 value in Table 9), the offset for K1 (or the PDSCH-to-HARQ_feedback timing indicator) is determined as floor(24 / 14) for 120 kHz SCS, floor(96 / 14) for 480 kHz SCS, and floor(192 / 14) for 960 kHz SCS, regardless of the dmrs-AdditionalPosition value. Alternatively, the offset may be determined using the ceil() function instead of floor().

[0150] (Method 1.1.2-3) The third method is to use the smaller of the two N1 values ​​regardless of the dmrs-AdditionalPosition value. As an example of this, in methods 1.1.1-1 to 1.1.1-4 (using the N1 value in Table 9), the offset for K1 (or the PDSCH-to-HARQ_feedback timing indicator) is determined as floor(20 / 14) for 120 kHz SCS, floor(80 / 14) for 480 kHz SCS, and floor(160 / 14) for 960 kHz SCS, regardless of the dmrs-AdditionalPosition value. Alternatively, the offset may be determined using the ceil() function instead of floor().

[0151] When PDSCH scheduling is performed according to DCI format 1_0, the values ​​defined by 3 bits of the K1 field (PDSCH-to-HARQ_feedback timing indicator field) may be defined as new values ​​instead of the values ​​[1, 2, 3, 4, 5, 6, 7, 8] of the conventional communication system. For example, some of the eight conventional values ​​may be defined in a form in which an offset proposed in 1.1 above is applied, and other values ​​may be defined as values ​​obtained by scaling the conventional values. Alternatively, the K1 field value may be determined as the maximum (larger value) or minimum (smaller value) of the values ​​determined by the offset and the values ​​determined by scaling. As an example of this, the offset value is set to ceil(N1 / 14) (where N1 varies depending on the SCS and / or additional DMRS settings, and in this example, N1=96 for 480 kHz and N=192 for 960 kHz are assumed, i.e., ceil(N1 / 14)=7 for 480 kHz and ceil(N1 / 14)=14 for 960 kHz), and the scaling values ​​are set to x4 and x8 for the 480 / 960 kHz SCS, respectively (where the scaling values ​​are not limited to 4 times (480 kHz) and 8 times (960 kHz)). An offset is applied to four of the eight conventional values, and scaling is applied to the other four (where the number of values ​​changed by the offset and the number of values ​​changed by scaling among the eight values ​​are not limited to 4 / 4, and may be set to 0 / 8, 1 / 7, or 8 / 0). The new values ​​are defined as follows:

[0152] 1.1.1-(1) Apply offset to any of the eight values ​​for 480kHz: [1, 2, 3, 4, 5, 6, 7, 8] -> [8, 9, 10, 11, 12, 13, 14, 15]

[0153] 1.1.1-(2) Apply scaling to any of the eight values ​​for 480kHz: [1, 2, 3, 4, 5, 6, 7, 8] -> [4, 8, 12, 16, 20, 24, 28, 32]

[0154] 1.1.1-(3) Apply offset to any of the eight values ​​for 960kHz: [1, 2, 3, 4, 5, 6, 7, 8] -> [15, 16, 17, 18, 19, 20, 21, 22]

[0155] 1.1.1-(4) Apply scaling to any of the eight values ​​for 960kHz: [1, 2, 3, 4, 5, 6, 7, 8] -> [8, 16, 24, 32, 40, 48, 56, 64]

[0156] 1.1.1-(5) For 480kHz, apply offset to 4 values ​​and scaling to 4 values: [1, 2, 3, 4, 5, 6, 7, 8] -> [8, 9, 10, 11, 20, 24, 28, 32]

[0157] 1.1.1-(6) 4 values ​​offset and 4 values ​​scaling applied to 960kHz: [1, 2, 3, 4, 5, 6, 7, 8] -> [15, 16, 17, 18, 40, 48, 56, 64]

[0158] 1.1.1-(7) Use the maximum value of the offset and scaling applied to 480kHz: [1, 2, 3, 4, 5, 6, 7, 8] -> [8, 9, 12, 16, 20, 24, 28, 32]

[0159] 1.1.1-(8) Use the maximum value among the values ​​with offset and scaling applied to 960kHz: [1, 2, 3, 4, 5, 6, 7, 8] -> [15, 16, 24, 32, 40, 48, 56, 64]

[0160] Also, when the PDSCH is scheduled according to DCI format 1_0, the values ​​defined by 3 bits of the K1 field (PDSCH-to-HARQ_feedback timing indicator field) are the [1, 2, 3, 4, 5, 6, 7, 8] values ​​of the conventional communication system, but the UE interprets and / or uses some of the indicated values ​​by adding an offset dependent on the N1 value, and scales other parts of the indicated values ​​to use the conventional values. In one embodiment, the base station instructs the UE to use the conventional [1, 2, 3, 4, 5, 6, 7, 8] values, and when the UE determines values ​​to be actually applied using the indicated values, it adds an offset to some values ​​and applies scaling to some values. Alternatively, the UE determines the maximum (larger value) or minimum (smaller value) of the values ​​determined by the offset and the values ​​determined by scaling as the value to be actually used. The offset value uses ceil(N1 / 14) (where N1 varies depending on the SCS and / or additional DMRS settings, and in this example, N1=96 for 480 kHz and N=192 for 960 kHz are assumed), the scaling values ​​use x4 and x8 for the 480 / 960 kHz SCS, respectively (where the scaling value is not limited to 4 times (480 kHz) and 8 times (960 kHz)), and an offset is applied to four of the eight conventional values, and scaling is applied to four of the other four (where the number of values ​​changed by the offset and the number of values ​​changed by scaling among the eight values ​​are not limited to 4 / 4, and may be set to 0 / 8, 1 / 7, or 8 / 0). The terminal interprets and / or applies the eight values ​​as new values ​​as follows:

[0161] 1.1.2-(1) Apply offset to any of the eight values ​​for 480kHz: [1, 2, 3, 4, 5, 6, 7, 8] is specified, and [8, 9, 10, 11, 12, 13, 14, 15] is applied.

[0162] 1.1.2-(2) Apply scaling to any of the eight values ​​for 480kHz: [1, 2, 3, 4, 5, 6, 7, 8] is specified, and [4, 8, 12, 16, 20, 24, 28, 32] is applied.

[0163] 1.1.2-(3) Apply offset to any of the eight values ​​for 960kHz: [1, 2, 3, 4, 5, 6, 7, 8] is specified, and [15, 16, 17, 18, 19, 20, 21, 22] is applied.

[0164] 1.1.2-(4) Apply scaling to any of the eight values ​​for 960kHz: [1, 2, 3, 4, 5, 6, 7, 8] is specified, and [8, 16, 24, 32, 40, 48, 56, 64] is applied.

[0165] 1.1.2-(5) Use the maximum value of the values ​​to which offset and scaling are applied for 480 kHz: [1, 2, 3, 4, 5, 6, 7, 8] is specified, and [8, 9, 12, 16, 20, 24, 28, 32] is applied.

[0166] 1.1.2-(6) Use the maximum value of the values ​​to which offset and scaling are applied for 960 kHz: [1, 2, 3, 4, 5, 6, 7, 8] is specified, and [15, 16, 24, 32, 40, 48, 56, 64] is applied.

[0167] The number of values ​​to which an offset is applied and the number of values ​​to which scaling is applied among the eight K1 field values ​​are not limited to the above-described embodiment, and may be predetermined to a specific ratio. For example, among the eight values, an offset is applied to the first four values ​​and scaling is applied to the last four values. As another example, an offset is applied to the first two values ​​and scaling is applied to the last four values. As another example, among the eight values, an offset is applied to the first, third, fifth, and seventh values ​​and scaling is applied to the second, fourth, sixth, and eighth values. The number and positions of values ​​to which an offset is applied and the number and positions of values ​​to which scaling is applied may be set by higher layer signaling such as RRC or signaling such as DCI. Furthermore, the scaling value is not limited to the above-described embodiment, and may be predetermined to a specific value (for each SCS or regardless of the SCS). Alternatively, the scaling value may be set by higher layer signaling such as RRC or signaling such as DCI. As a method for determining the offset value, floor(N1 / c) or ceil(N1 / c) proposed in 1.1 above may be used.

[0168] Furthermore, a new value for the K1 field (PDSCH-to-HARQ_feedback timing indicator field) of DCI format 1_0 may be determined using a method described below. When a high SCS (e.g., 480 kHz or 960 kHz) is configured in a system operating in the 52.6 GHz frequency band, the K1 field value of DCI format 1_0 may be determined to a different value using a method described below, instead of [1, 2, 3, 4, 5, 6, 7, 8] as in the conventional system operating in the 52.6 GHz frequency band. The method described below can improve the problem of reduced PDSCH scheduling flexibility when the conventional 3-bit, i.e., 8-value K1 field is used for an SCS higher than the 120 kHz SCS (e.g., 480, 960 kHz). Two typical examples of possible problem situations will be described below. First, if the conventional values ​​[1, 2, 3, 4, 5, 6, 7, 8] are simply scaled by 4 or 8 times, the PDSCH scheduling granularity changes from the conventional 1 slot to 4 or 8 slots. Second, if a specific offset value is added to the conventional values, the scheduling granularity remains 1 slot, but a problem occurs in that PDSCH scheduling is only possible in slots within a limited distance from a PUCCH at a specific location. The proposed method described below can avoid the worst-case scenario of these two problem situations.

[0169] (Proposed Method 1.1.k1-1) A method of maintaining the K1 field (PDSCH-to-HARQ_feedback timing indicator field) of DCI format 1_0 at 3 bits (or extending it to more than 3 bits), or defining a new value suitable for SCS higher than 120 kHz (e.g., 480, 960 kHz). Specifically, the 2^Z values ​​that can be represented by Z bits are configured according to the following rule: The 2^Z values ​​that can be represented by Z bits are divided into M sub-groups. Each sub-group consists of L consecutive numbers (or numbers at specific intervals). Here, M and L are integers greater than 0, and M*L=2^Z is satisfied. Furthermore, all M*L values ​​are different, and overlapping numbers are not allowed (here, sub-groups are referred to as the first sub-group, second sub-group, etc., in order of decreasing number / value). For example, the eight values ​​that can be expressed with three bits may be composed of M=1 slot group and L=8 consecutive numbers, M=2 slot group and L=4 consecutive numbers for each subgroup, or M=8 subgroup and L=1 number for each subgroup.

[0170] In addition to the above-mentioned M and L, various types of K1 field values ​​are defined depending on whether the interval between subgroups (= T) and / or the interval between values ​​within a subgroup (= J) are used in the rules described below. As M or T increases, a wider range of values ​​can be supported, but the difference in values ​​between subgroups may increase, resulting in lower scheduling granularity. J is also a value that can adjust the scheduling range and granularity within a subgroup. For example, if J = 1, the UE can support HARQ-ACK for PDSCH received in consecutive slots, but may not be able to indicate a larger range of slot offsets than when J > 1. This is because when using limited Z bits (or a set of 2^Z values), it is difficult to simultaneously support a large scheduling range and high scheduling granularity, and there is a trade-off between the two. Therefore, in order to ensure appropriate scheduling flexibility for each SCS, it is necessary to define the most suitable value set for each SCS by appropriately selecting / combining M, L, T, J, etc. as described in (Rules 1.1.3-1) to (Rules 1.1.3-3) below.

[0171] Rule 1.1.3-1: How to determine the minimum value of the first subgroup (=S1)

[0172] The minimum value of the first subgroup is floor(N1 / c) or ceil(N1 / c) proposed in 1.1 above. Alternatively, a value obtained by adding or subtracting '+1' from floor(N1 / c) or ceil(N1 / c) is used. If a multi-slot PDCCH monitoring operation is introduced at a high SCS (e.g., 480 or 960 kHz), such an adjustment of +1 or -1 distributes the PDCCH monitoring slot (or slot group) positions and the PDSCH receiving slot positions. N1 may be a value predefined for each SCS, and c may be a value predefined as in 1.1 above. For example, 14, which is the number of symbols constituting one slot, is used as the value of c. Alternatively, the first value (i.e., the minimum value) of the first subgroup may be different for each SCS. The first value may be determined as "2^(u_SCS - 3)" using u_SCS, which indicates the pneumology of the SCS, or may be determined as "2^(u_SCS - 3) + 1" or "2^(u_SCS - 3) - 1." u_SCS is a value that satisfies the relation "2^(u_SCS) * 15 [kHz] = SCS [kHz]." For example, u_SCS = 3 for 120 kHz SCS, u_SCS = 5 for 480 kHz SCS, and u_SCS = 6 for 960 kHz SCS. If the PDSCH processing time for a specific SCS is set to be large, the first value may be determined as "2^(u_SCS - 2)." This is because if the required PDSCH processing time for a particular SCS is greater than 2^(u_SCS - 3), this value is very unlikely to be used. Similarly, the first value may be set to 2^(u_SCS - 2) + 1 or 2^(u_SCS - 2) - 1.

[0173] Rule 1.1.3-2: Method for determining the minimum value of a subgroup other than the first

[0174] When M>1, the minimum value of each subgroup, excluding the first subgroup, is determined to be the minimum value of the first subgroup determined in Rule 1.1.3-1 plus a specific value (=T) or a multiple of the specific value T. The specific value T varies for each SCS and is determined as a power of two, such as T=1, T=2, T=4, T=8, or T=16. For example, the minimum value of the second subgroup is the minimum value of the first subgroup plus T, the minimum value of the third subgroup is the minimum value of the first subgroup plus 2*T (i.e., the minimum value of the second subgroup plus T), and the minimum value of the nth subgroup is the minimum value of the first subgroup plus (n-1)*T (i.e., the minimum value of the (n-1)th subgroup plus T).

[0175] Rule 1.1.3-3: For each subgroup, the L-1 values, excluding the minimum, are determined to be consecutive numbers / values ​​that increase by a specific interval (=J) from the value determined by Rules 1.1.3-1 and 1.1.3-2. The specific interval J varies for each SCS and is an integer greater than 0. For example, if Z=3, M=1, L=8, and J=1, and N1=80 for a 480 kHz SCS and the minimum subgroup value is ceil(N1 / 14)+1=7, then the K1 field values ​​are determined to be [7, 8, 9, 10, 11, 12, 13, 14]. If N1=160 for a 960 kHz SCS and the minimum subgroup value is ceil(N1 / 14)+1=13, then the K1 field values ​​are determined to be [13, 14, 15, 16, 17, 18, 19, 20]. As another example, if Z=3, M=4, L=2, T=4 (for 480 kHz) or T=8 (for 960 kHz), and J=1, and the minimum value of the first subgroup is the same as in the example above, the values ​​are determined as [7, 8, 11, 12, 15, 16, 19, 20] and [13, 14, 21, 22, 29, 30, 37, 38] for the 480 / 960 kHz SCS, respectively. If J=2 in this example, the values ​​are determined as [7, 9, 11, 13, 15, 17, 19, 21] and [13, 15, 21, 23, 29, 31, 37, 39] for the 480 / 960 kHz SCS, respectively.

[0176] The above-mentioned methods and / or rules are not limited to the case where Z=3 bits, but are also applicable to determining specific values ​​when the number of bits (width) of the K1 field of DCI port 1_0 increases to Z=4 or Z=5 bits, etc.

[0177] The above-described method and / or rule is also used to define a specific value of the K1 field of DCI format 1_0 (i.e., the value determined by the above-described method and / or rule is hard-coded in the specification). Alternatively, the value of the K1 field of DCI format 1_0 may remain the conventional [1, 2, ..., 8], and even if the base station (Node B) indicates the conventional value, the UE derives and applies (or considers, assumes, or sets) an actual value different from the conventional value based on the indicated value and in accordance with the above-described method / rule.

[0178] The following Examples 1.1.4-1 to 1.1.4-10 can be understood as typical examples of K1 field values ​​created according to the above-mentioned rules (the set of values ​​created according to the above-mentioned rules is not limited to these examples). Any one of these sets of values ​​is used as the K1 field (PDSCH-to-HARQ_feedback timing indicator field) value of DCI format 1_0 for 480 / 960 kHz SCS.

[0179] Example 1.1.4-1: When Z=3, S1=7, M=1, L=8, and J=1 for 480 kHz, the values ​​are determined as follows, and ACK / NACK feedback for consecutive PDSCHs is possible.

[0180] - [7, 8, 9, 10, 11, 12, 13, 14]

[0181] Example 1.1.4-2: For 480 kHz, when Z=3, S1=7, M=8, L=1, and T=4, the values ​​are determined as follows, and a larger range of values ​​can be supported compared to Example 1.1.4-1.

[0182] - [7, 11, 15, 19, 23, 27, 31, 35]

[0183] Example 1.1.4-3: For 480 kHz, when Z=3, S1=7, M=4, L=2, T=4, and J=1, the values ​​are determined as follows, which supports a larger range of values ​​than Example 1.1.4-1 and can support more continuous values ​​than Example 1.1.4-2.

[0184] - [7, 8, 11, 12, 15, 16, 19, 20]

[0185] Example 1.1.4-4: When Z=3, S1=8, M=8, L=1, and T=4 for 480 kHz, the values ​​are determined as follows, and compared to Example 1.1.4-2, this value has the feature that the PDSCH reception slot for the 480 kHz SCS is aligned to the slot boundary of the 120 kHz SCS.

[0186] - [8, 12, 16, 20, 24, 28, 32, 36]

[0187] Example 1.1.4-5: When Z=3, S1=13, M=1, L=8, and J=1 for 960 kHz, the values ​​are determined as follows, and ACK / NACK feedback for consecutive PDSCHs is possible.

[0188] - [13, 14, 15, 16, 17, 18, 19, 20]

[0189] Example 1.1.4-6: For 960 kHz, when Z=3, S1=13, M=8, L=1, T=4, the values ​​are determined as [13, 17, 21, 25, 29, 33, 37, 41], or when Z=3, S1=13, M=8, L=1, T=8, the values ​​are determined as [13, 21, 29, 37, 45, 53, 61, 69]. Compared to Example 1.1.4-5, larger values ​​are instructed to the terminal.

[0190] Example 1.1.4-7: For 960 kHz, if Z=3, S1=13, M=4, L=2, T=8, J=1, the values ​​are determined to be [13, 14, 21, 22, 29, 30, 37, 38], or if Z=3, S1=13, M=2, L=4, T=8, J=1, the values ​​are determined to be [13, 14, 15, 16, 21, 22, 23, 24]. This supports a larger range than Example 1.1.4-5 and allows for greater scheduling flexibility than Example 1.1.4-6.

[0191] Example 1.1.4-8: When Z=3, S1=16, M=8, L=1, and T=8 for 960 kHz, the values ​​are determined as follows. Compared to Example 1.1.4-5, this has the advantage that the 960 kHz PDSCH reception slots are aligned with the 120 kHz SCS slot boundaries.

[0192] - [16, 24, 32, 40, 48, 56, 64, 72]

[0193] Example 1.1.4-9: (When the field in DCI is 4 bits) When Z=4, S1=7, M=1, L=16, and J=1, the value is determined as follows:

[0194] - [7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22]

[0195] Example 1.1.4-10: (When the field in DCI is 5 bits) When Z=5, S1=1, M=1, L=32, and J=1, the value is determined as follows:

[0196] - [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, ..., 31, 32]

[0197] The exact / specific value of the K1 field in DCI format 1_0 is not limited to the above-mentioned embodiment, and the exact number / value is determined using the above-mentioned (Rule 1.1.3-1), (Rule 1.1.3-2), and (Rule 1.1.3-3).

[0198] (Proposed Method 1.1.k1-2) When scheduling a PDSCH using DCI format 1_0, an alternative method for determining the UL slot for the HARQ-ACK using the K1 field (PDSCH-to-HARQ_feedback timing indicator field) value indicated by the corresponding DCI is to subtract a specific value from the indicated K1 field value according to the index of the slot in which the UE receives the PDSCH. After modulo-dividing the slot index by a specific divisor, the slot offset between the received PDSCH and the UL slot in which the corresponding HARQ-ACK is transmitted is determined according to the remainder. The slot offset between the PDSCH and the UL slot actually applied by the UE is determined according to the following [Equation 1.1.k1-2].

[0199] [Formula 1.1.k1-2] k1_applied=k1_indicated-modulo(slot_index, B)

[0200] Here, k1_applied means the "slot offset between the PDSCH and the UL slot for transmitting the corresponding HARQ-ACK" actually applied by the UE. k1_indicated means the "PDSCH-to-HARQ_feedback timing indicator field value indicated to the UE." slot_index means the "slot index of the slot in which the UE receives the PDSCH." The modulo(x, y) operation means the remainder when x is divided by y. The constant B may have different values ​​depending on the SCS, and may be predefined or separately indicated by RRC or DCI. For example, B=4 is predefined for 480 kHz SCS, and B=8 is predefined for 960 kHz SCS. As a specific example of this, when k1_indicated is defined as [8, 16, 24, 32, 40, 48, 56, 64] for 960 kHz SCS, in order for the UE to transmit a HARQ-ACK in slot #n, the UE needs to receive the corresponding PDSCH in any one of slot #(n-8), slot #(n-16), ..., slot #(n-64). In other words, to transmit a HARQ-ACK in a corresponding UL slot, schedulable PDSCH reception slots exist only at intervals of 8 slots, and if a PDSCH is received in a slot between them (i.e., slot #(n-9), slot #(n-10), ..., slot #(n-15)), the UE cannot be instructed to transmit a HARQ-ACK in slot #n, and in some cases, the UE may not be instructed to transmit a valid UL slot in which the HARQ-ACK can be transmitted. However, by applying the proposed [Equation 1.1.k1-2], even if the UE receives a PDSCH in any of the eight slots from slot #(n-16) to slot #(n-9), the UE can be instructed to send a HARQ-ACK in slot #n.

[0201] Furthermore, enable / disable of this operation can be set and / or indicated by a separate RRC configuration or DCI field. For example, if the operation of [Formula 1.1.k1-2] is enabled using a separate parameter / field of RRC or DCI, the UE is instructed to transmit a HARQ-ACK for a PDSCH received in slot #(n-15) in slot #n using 'indicated k1=16'. If the operation of [Formula 1.1.k1-2] is disabled using a separate parameter / field of RRC or DCI, the UE is instructed to transmit a HARQ-ACK for a PDSCH received in slot #(n-15) in slot #(n+1). Furthermore, enable / disable of this operation may be implicitly determined according to a frame index (or SFN: system frame number), a subframe index, a slot index, etc. For example, when modulo(SFN,2)=0, the operation is set to [enable], and when modulo(SFN,2)=1, the operation is set to [disable], so that the operation is enabled every even numbered frame. This allows the UE to expect increased scheduling flexibility even for high SCS (e.g., 480, 960 kHz) using only the K1 field with a limited number of bits (bidwidth).

[0202] 1.2. N pdsch and μ PDCCH , μ PDSCH How to change the range of K0 values ​​using (for cross-carrier scheduling)

[0203] K0 indicates the slot offset from the slot for receiving the DL grant PDCCH to the slot for receiving the PDSCH. A UE for which K0 is set determines the slot Ks for receiving the PDSCH according to Table 10 defined in 3GPP TS 38.214.

[0204] [Table 10]

[0205] At this time, μ PDCCH , μ PDSCH If the values ​​are different from each other, K0 is PDSCH It is interpreted as a standard slot unit. PDSCH >μ PDCCH If μ is 0, then K0=0 means the earliest slot among the slots of the PDSCH corresponding to the slot in which the PDCCH is received. PDSCH <μ PDCCH If K=0, then K=0 means the slot of the PDSCH corresponding to the slot in which the PDCCH is received.

[0206] On the other hand, in cross-carrier scheduling, μ PDCCH , μ PDSCH If the values ​​are different, s Even if is determined by the above formula, K s The position of is N (in PDCCH symbol units) from the last symbol that received the PDCCH. pdsch Only when at least N symbol intervals are guaranteed, the terminal can expect normal PDSCH reception. pdsch is defined in Table 11 of 3GPP TS 38.214.

[0207] Table 11 is based on Table 5.5-1: N in 3GPP TS 38.214. pdsch as a function of the subcarrier spacing of the scheduling PDCCH.

[0208] [Table 11]

[0209] For the newly introduced 480kHz and 960kHz SCS for the 52.6GHz band, μ PDCCH = 5, μPDCCH N corresponds to =6 pdsch Inferring from Table 11, is set to a value greater than 14.

[0210] As mentioned above, in the case of mixed SCS in cross-carrier scheduling, slot K s is determined by K0, but N pdsch If the interval for the number of symbols is not guaranteed, the terminal does not expect to receive PDSCH, so a specific value of K0 is not required. pdsch >N pdcch In this case, the number of unnecessary K0s (where PDSCH reception is not expected) varies depending on the index of the last symbol in which PDCCH is received, even within a slot in which PDCCH is received.

[0211] For example, μ PDCCH = 3 (i.e., 120 kHz SCS), and μ PDSCH = 6 (i.e., 960 kHz SCS), if the PDCCH is received in 120 kHz slot 0 in FIG. 6, the position corresponding to K0 = 0 is 960 kHz slot 0. (In FIG. 6, the numbers in the slots indicate slot indexes.)

[0212] If the PDCCH is received at symbol 0 of slot 0, then N pdsch Due to the constraints imposed by , the UE expects PDSCH reception from 960k slot 8 (or 7). In this case, a K value smaller than 8 (or 7) is used to select K s If N is determined, the UE does not expect to receive a PDSCH in that slot. On the other hand, if a PDCCH is received at symbol 13 of slot 0, N pdsch Since the UE expects PDSCH reception from 960k slot 15 (or 14) due to the constraints imposed by s Do not expect to receive PDSCH.

[0213] In this way, in order to exclude values ​​of K0 for which PDSCH reception cannot actually be expected, a new K0 value is determined using the following formula: (In the formula below, the K0 value that can be set in a conventional system is denoted as K0`.)

[0214]

number

[0215]

number

[0216]

number

[0217] Furthermore, in order to also correct the influence of the last symbol in which the PDCCH is received, a new value of K0 is determined by the following method ((3) or (4)).

[0218]

number

[0219]

number

[0220] At this time, O sym is determined by one of the following methods 1.2-(5), 1.2-(6), or 1.2-(7), and O sym,0 , O sym,1 Or O sym,2 Use in 1.2-(3) or 1.2-(4).

[0221]

number

[0222]

number

[0223]

number

[0224] At this time, i sym means the index of the last symbol to receive the PDCCH. round() means the round function operation. sym The reason for determining in three ways is as follows: If the received PDCCH symbol spans two or more PDSCH slots, it may be unclear which index to select between the previous PDSCH slot and the next PDSCH slot. For example, Figure 7 shows symbols and slots of 120 kHz PDCCH and 960 kHz PDSCH. If the PDCCH is received at PDCCH symbol index 3, according to 1.2-(3) and 1.2-(4), O sym The PDSCH symbol index can be 1 or 2.

[0225] Depending on the situation such as multiple SCSs and DL / UL slot configuration, it is useful to selectively select the index of the previous slot or the index of the next slot.

[0226] When the base station or the terminal recalculates K0 using the method of 1.2-(3) or 1.2-(4), the base station and / or the terminal sym As O sym,0 , O sym,1 , O sym,2 After all the above are determined, one value may be selected and applied. In this case, the value to be used may be semi-statically or dynamically configured by RRC or DCI, and O may be used as the base value. sym,0 , O sym, 1, O sym,2 You may use either one of the following:

[0227] Furthermore, methods 1.2-(1) and 1.2-(2) may be configured to operate only at a specific SCS (e.g., 960 kHz). pdcch It works only if μ is a specific value, or μ pdsch / μ pdcch (μ pdsch μ pdcch It only works if μ is greater than or equal to a certain value, or μ pdsch / μ pdcch may be configured to operate only when K0 is smaller than a specific value. For example, methods 1.2-(1) and 1.2-(2) are configured to operate only when the PDCCH is configured with 120 kHz SCS and the PDSCH is configured with 960 kHz SCS. In addition, methods 1.2-(1) and 1.2-(2) may be configured using different c values, and then the K0 settings according to 1.2-(1) and 1.2-(2) may be switched. In this case, the switch flag is indicated by the DCI.

[0228] 1.3. How to determine the range of K1 values ​​based on the range of K0 values ​​or the range of K0 values ​​based on the range of K1 values

[0229] In a series of processes in which a PDSCH is scheduled according to a DL grant and a HARQ-ACK for the corresponding PDSCH is transmitted on a PUCCH and / or a PUSCH, the base station sets / instructs the terminal K0 (i.e., the interval between a slot for receiving a PDCCH and a slot for receiving a PDSCH scheduled accordingly) and K1 (i.e., the interval between a slot for receiving a PDSCH and a slot for transmitting a corresponding HARQ-ACK). In a conventional communication system (i.e., NR Rel-15), the values ​​of K0 from 0 to 32 are supported, and the values ​​of K1 from 0 to 15 are supported.

[0230] A situation may be considered in which the UL slots in which a UE transmits a PUCCH and / or a PUSCH including a HARQ-ACK are semi-statically configured. For example, Figure 8 shows an example of a TDD configuration. Specifically, an example is shown in which the ratio of DL slots or special slots to UL slots is assumed to be 8:2. The TDD configurations for the 480 kHz SCS cell and the 960 kHz SCS cell are configured so that they are aligned with the DL / special slots and UL slots of the TDD configuration of the 120 kHz SCS cell.

[0231] For ease of explanation, the indices of the 64 DL slots of a cell configured with a 960 kHz SCS are expressed as 0, 1, ..., 63 from the left. If the PDCCH scheduling the PDSCH is received in slot 0 when the SCS of the PDCCH / PDSCH is both 960 kHz, the first symbol of the PDSCH is located between slot 0 and slot 32. Also, considering the range of offset K1 (0 to 15) from the PDSCH reception slot (or the last slot in the case of a multi-slot PDSCH) to the UL slot, the PDSCH reception slot (or the last slot in the multi-slot PDSCH) is located between slot index 48 and slot index 63. Therefore, to perform PDSCH scheduling in this situation using the current K0 and K1 values, the interval between the first slot and the last slot of the multi-slot in which the PDSCH is located needs to be 16 or more. To configure multi-slot PDSCH scheduling with a shorter length, the range of values ​​of K0 and / or K1 needs to be increased. Furthermore, in such a situation, it is not necessary to set K0 and K1 to large values ​​at the same time. In a situation where the position of the UL slot is fixed, when a PDCCH is received, if K0 is set to a large value, K1 is set to a relatively small value. If K0 is set to a small value, K1 is set to a relatively large value in order to set K1 to match the position of the UL slot.

[0232] Generally, when the position of the UL slot is determined semi-statically, the range of the values ​​of K0 and / or K1 needs to be increased according to the position of the reception slot of the DL grant PDCCH. Also, a method of determining a combination of the values ​​of K0 and K1 within an appropriate range may be considered. Using an appropriate range of values ​​of K0 and / or K1 is also useful in terms of flexibility of multi-slot PDSCH scheduling. In Section 1.3 below, a method of determining a range of values ​​of K1 according to a range of values ​​of K0 and a method of determining a range of values ​​of K0 according to a range of values ​​of K1 will be described.

[0233] 1.3.1. Different interpretations of the K1 range depending on the K0 range

[0234] The base station indicates configurable K0 and K1 to the terminal for PDSCH and HARQ-ACK scheduling. The terminal divides the indicated K0 value range into N parts and determines an offset value to be added to the K1 value according to each value range as shown in Table 12.

[0235] [Table 12]

[0236] Once the offset to be added to K1 is determined, the terminal adds the offset to the indicated K1 value to determine the slot offset from the last slot of the received PDSCH to the UL slot in which the corresponding HARQ-ACK is transmitted (i.e., determines the position of the transmission slot of the HARQ-ACK).

[0237] As a specific example, K0=[0, 1, ..., 32] is divided into N=3 intervals. The settings are a=0, b=10, c=20, d=30, F_a=8, F_b=4, and F_c=2. When K0=9 is instructed from the base station, the terminal determines K1+8 (=K1+F_a) as the slot interval from the last slot of the received PDSCH to the UL slot in which the corresponding HARQ-ACK is transmitted, and determines the position of the UL slot in which the HARQ-ACK is transmitted.

[0238] 1.3.2. Different interpretations of the K0 range depending on the K1 range

[0239] The base station indicates configurable K0 and K1 to the terminal for PDSCH and HARQ-ACK scheduling. The terminal divides the indicated K1 value range into M parts and determines an offset value to be added to the K0 value according to each value range as shown in Table 13.

[0240] [Table 13]

[0241] When the offset to be added to K0 is determined, the terminal adds the offset to the indicated K0 value to determine the slot offset from the PDCCH reception slot to PDSCH reception (that is, the terminal determines the position of the PDSCH reception slot).

[0242] As a specific example, K1=[0, 1, ..., 15] is divided into intervals of M=2. The settings are e=0, f=8, g=15, F_e=8, and F_f=4. When K1=9 is instructed from the base station, the terminal determines K0+4 (=K0+F_f) as the slot interval from the PDCCH reception slot to PDSCH reception, and determines the position of the PDSCH reception slot.

[0243] In the above-mentioned method, the configurable K0 values ​​are divided into N groups in order of size, a different offset is preset for each group, and a value obtained by adding the corresponding offset to the configurable value of the previous K1 is indicated to the terminal as a new K1. Also, the configurable K1 values ​​are divided into M groups in order of size, a different offset is preset for each group, and a value obtained by adding the corresponding offset to the configurable value of the previous K0 is indicated to the terminal as a new K0.

[0244] 1.4. How to change the range of K2 values ​​to match the range of N2 values

[0245] According to 3GPP TS 38.214, when a UE is configured to transmit a transport block (TB) without a CSI report or to transmit a TB and a CSI report on a PUSCH, the UE is instructed to use the K2 value by the TDRA (time domain resource assignment) field of the corresponding DCI and the associated table. Also, when a UE is configured to transmit a CSI report on a PUSCH without a TB by a DCI, the TDRA field value m of the DCI and the Y given by reportSlotOffsetListDCI-0-2, reportSlotOffsetListDCI-0-1, or reportSlotOffsetList in the RRC parameter CSI-ReportConfig are used. j Using the formula: K2=maxY j (m+1) j is determined. Meanwhile, the terminal reports the time taken from receiving the UL grant DCI to transmitting the PUSCH to the base station, and N2 used here is expressed in symbol units. After the N2 value is reported, the base station determines the K2 value so that it is equal to or greater than the corresponding absolute time, and sets and / or instructs the K2 value to the terminal. In this case, in certain situations, there may be invalid K2 values ​​that can be supported depending on the range of N2 values. For example, when N2 > 14, a UE with K2 = 0 or 1 set is not required to transmit a PUSCH. Alternatively, in certain situations, such as when a large SCS (e.g., 480 or 960 kHz) is used and the processing time of DCI scheduling multiple PUSCHs becomes long, a larger K2 value than the conventionally supported K2 value is required. In this case, K2 is determined according to the following method.

[0246] 1.4-(1) K2 = ceil(N1 / c) + "K2 value that can be supported by RRC parameters, etc."

[0247] 1.4-(2) K2 = floor(N1 / c) + "K2 value that can be supported by RRC parameters, etc."

[0248] In equations 1.4-(1) and 1.4-(2), c is semi-statically configured by RRC, MAC CE, etc., or dynamically configured by DCI. The default c value is 14, which is the number of symbols per slot. Methods 1.4-(1) and 1.4-(2) may be configured to operate only for a specific SCS (e.g., 480 or 960 kHz). Methods 1.4-(1) and 1.4-(2) may also be configured to operate only when N2 is greater than or equal to a specific value. Methods 1.4-(1) and 1.4-(2) may be configured with different c values, and then the K2 settings by methods 1.4-(1) and 1.4-(2) may be switched. In this case, the switch flag is indicated by DCI.

[0249] 1.5. Method for Determining the Aperiodic CSI-RS Triggering Offset Value

[0250] When an aperiodic CSI-RS (hereinafter referred to as A-CSI-RS) is configured / indicated / used for aperiodic CSI-RS reporting, and at this time, the pneumatology μ of the A-CSI-RS csirs And the PDCCH pneumatology μ that triggers this pdcch When the values ​​of the CSI-RS trigger offset X (hereinafter referred to as offset X) are different, the CSI-RS trigger offset X (hereinafter referred to as offset X) is configured for each resource set using the RRC parameter aperiodicTriggeringOffset or aperiodicTriggeringOffset-r16. In this case, offset X refers to the slot offset between the slot in which DCI (or PDCCH) triggering the aperiodic NZP (non-zero power) CSI-RS resource is transmitted / received and the slot in which the corresponding CSI-RS is transmitted and / or received. Supportable values ​​of offset X are μ csirs and μ pdcch According to the relationship,

[0251] - μpdcch <μ csirs : offset X=[0, 1, ..., 31]

[0252] - μ pdcch >μ csirs : offsetX=[0, 1, 2, 3, 4, 5, 6, ..., 15, 16, 24]

[0253] Using offset X, the position K of the slot where the aperiodic CSI-RS is transmitted is determined according to Table 14 below. s is determined.

[0254] [Table 14]

[0255] The offset X value mentioned above is set without considering the short slot duration of 480 kHz or 960 kHz, and when 480 / 960 kHz is used, the support range of the offset X value needs to be increased. For example, if the offset X is 16, the number of slots at 960 kHz, which corresponds to the same absolute time as 16 slots at 120 kHz, is 128, and the offset X value range is increased to support this.

[0256] (1.5-1) The configurable value of offset X may be increased. That is, new configurable values ​​for the RRC parameter aperiodicTriggeringOffset or aperiodicTriggeringOffset-r16 are newly defined for each SCS (e.g., 480 kHz and / or 960 kHz). As an example of this, a value M times the conventional offset X is determined as the maximum supportable value. For example, when M=8, offset X is set to [0, 1, ..., 31*8]. Alternatively, offset X is set to [0, 1*8, 2*8, ..., 31*8]. M may be predefined or semi-statically determined. For example, to align the timeline of a cell configured with 480 kHz or 960 kHz with the timeline of a cell configured with 120 kHz, M may be set to, but is not limited to, 4 for 480 kHz or 8 for 960 kHz.

[0257] (1.5-2) A new offset value is set by adding an offset Y to the offset X. When the previous X value is X', the new offset value is determined as X = X' + Y. As a specific example of this, the Y value is determined according to one of the following methods, but is not limited to the following methods.

[0258]

number

[0259]

number

[0260] Alternatively, the index of the symbol where the PDCCH that triggers the A-CSI-RS is received (i sym ) The following method using

[0261]

number

[0262] In this case, W is i sym is a value that depends on and is determined as follows:

[0263]

number

[0264] c is set semi-statically by RRC, MAC CE, etc., or dynamically by DCI. As the basic c value, for example, 14, which is the number of symbols per slot, is used.

[0265] The method for determining Y and W is defined and applied individually to each SCS. Alternatively, the method for determining Y and W is defined for each SCS, and the maximum value among the methods is used commonly for all SCSs. For example, Y and / or W of all cells are determined based on the SCS in which Y or W is the maximum value.

[0266] When the range of the offset X value is determined according to the above-mentioned methods (1.5-1) and (1.5-2), the base station sets and / or indicates the range of the offset X value to the terminal by higher layer signaling such as RRC. Alternatively, if the base station sets and / or indicates the value of offset X by RRC or the like through mutual agreement between the base station and the terminal without changing the previous value of offset X, the terminal may interpret it as the (increased) value defined by methods (1.5-1) and (1.5-2) and operate accordingly.

[0267] 1.6 N csirs and a method for determining the offset of K2 using Z and Z'

[0268] According to the CSI computation time defined in 3GPP TS 38.214, the timeline between the DCI that triggers the transmission of a CSI report to a PUSCH, the associated CSI-RS or CSI-IM signal, and the corresponding PUSCH has the relationship shown in Table 15.

[0269] [Table 15]

[0270] Furthermore, depending on whether HARQ-ACK and UL-SCH (or transport block) are multiplexed in the PUSCH that transmits the CSI report, the UE may ignore the DCI that triggers the CSI report, as shown in Table 16.

[0271] [Table 16]

[0272] In the above-described operation, when DCI that triggers CSI reporting on a PUSCH sets / indicates the transmission slot of the corresponding PUSCH (for example, when setting / indicating the slot offset k2 between the PDCCH and the UL transmission scheduled thereby), the range of supported K2 values ​​needs to be readjusted. For example, the conventional K2 can be specified as a value of [0,...,31] by RRC, etc., but Z and / or Z' (or Z ref and / or Z' refIf the (n)) value is large, a small K2 (e.g., K2=0) is unnecessary. In this case, CSI reporting on the PUSCH indicated by the DCI is not performed. Alternatively, the maximum value of K2 needs to be greater than the conventional 31. If Z and / or Z' are defined as very large values ​​for 480 kHz and 960 kHz, K2 may fall outside the conventional range of values. To address this, section 1.6 describes a method for determining a new range of the conventional k2 value using Z, Z', and / or X (an offset X of 1.5). The base station and terminal determine a new range of the K2 value according to the method described below, and transmit / configure / instruct this via RRC, etc. Alternatively, the base station may use the conventional K2 value and transmit K2 to the terminal, and the terminal may interpret and apply the slot offset between the DCI (or PDCCH) and the UL slot differently according to the method described below.

[0273] When the old K2 value is K2_old, the slot offset to be added to the old K2 value is K2_offset, and the K2 value determined by the added offset is K2_new, the range of the K2 value is determined as K2_new = K2_old + K2_offset. In this case, K2_offset is determined by one of the following methods.

[0274] - k2_offset=ceil(z / c1)

[0275] - k2_offset=floor(z / c2)

[0276] - k2_offset=X+ceil(z' / c3)

[0277] - k2_offset=X+floor(z' / c4)

[0278] In this case, c1, c2, c3, and c4 are predefined, semi-statically configured by RRC, MAC CE, etc., or dynamically configured by DCI. The basic c1, c2, c3, and c4 values ​​may be, for example, but are not limited to, 14, which is the number of symbols per slot. X denotes the aperiodic CSI-RS trigger offset value, and includes the offset X described in 1.5 of the present invention.

[0279] The method for determining k2_new and k2_offset and / or the method for redefining or reinterpreting k2 using Z, Z', and X may be configured and / or defined for use only with a particular SCS (e.g., 480 kHz and / or 960 kHz).

[0280] The method of determining k2_new and k2_offset and / or the method of redefining or reinterpreting k2 using Z, Z', and X may be applied only when HARQ-ACK and / or UL-SCH (or a transmission block) are not multiplexed onto the PUSCH on which the CSI report is transmitted.

[0281] The method of determining k2_new and k2_offset and / or the method of redefining or reinterpreting k2 using Z, Z', and X may also be applied in the same (or similar) manner when HARQ-ACK and / or UL-SCH (or a transmission block) are multiplexed together in a PUSCH on which a CSI report is transmitted.

[0282] The method for determining k2_new and k2_offset and / or the method for redefining or reinterpreting k2 using Z, Z', and X may be applied only when there is one CSI report triggered by DCI, or may be applied regardless of the number of CSI reports triggered.

[0283] 7) How to determine the delay requirement for aperiodic CSI reporting

[0284] In conventional NR systems, the CSI reporting latency is specified for each CSI content for each pneumatology (or SCS) in the FR1 or FR2-1 (below 52.6 GHz) frequency domain using Tables 17 and 18. CSI reports (i.e., each CSI reporting setting) are classified into three latency classes, and for each class, Z1 (low-latency class), Z2 (high-latency class), and Z3 (other cases) defined in Table 18 are applied as latency requirements. Table 17 is also defined for ultra-low-latency, which requires a latency requirement lower than low-latency.

[0285] Table 17 is Table 5.4-1: CSI computation delay requirement 1 of 3GPP 38.214, and Table 18 is Table 5.4-2: CSI computation delay requirement 2 of 3GPP 38.214.

[0286] [Table 17]

[0287] [Table 18]

[0288] For example, in Table 18, Z1 and Z1' apply to CSI reports where the following three conditions are met simultaneously:

[0289] - Wideband frequency-granularity

[0290] - A single CSI-RS resource (ie, no CRI reporting) with at most 4 CSI-RS ports

[0291] - PMI reporting with Type I Single-Panel codebook or non-PMI reporting

[0292] Z3 and Z3' are delay requirements that apply for L1-RSRP reporting (i.e., beam management), and Z2 and Z2' are delay requirements that apply for reporting for other CSI content.

[0293] Table 17 is a requirement for supporting the lowest latency (ultra-low latency), but it is a latency requirement that is applied when a CSI report of the low-latency class is triggered (i.e., corresponds to the CSI reporting configuration to which Z1 and Z1' in Table 5.4-2 are applied) and certain conditions are met (e.g., when all CPUs of the UE are unoccupied and UL-SCH or HARQ-ACK is not multiplexed on the PUSCH to which the corresponding CSI report is transmitted). TS 38.214 defines this as shown in Table 19.

[0294] [Table 19]

[0295] For SCSs (e.g., 480 kHz or 960 kHz) used in the FR2-2 (52.6 to 71 GHz) or high-frequency (above 52.6 GHz) bands, if the latency requirement for ultra-low latency as shown in Table 17 is not specified, it is necessary to specify the reporting time requirement for the corresponding single CSI.

[0296] Proposed method 1.7-1

[0297] When only one latency requirement is defined for an SCS (e.g., 480 kHz and / or 960 kHz or higher SCS) used in a high frequency band (e.g., 52.6 GHz or higher) (i.e., when no latency requirement is defined apart from that for the lowest latency class (Ultra latency class)), the corresponding CSI report follows the same latency requirement regardless of whether an UL-SCH or HARQ-ACK is multiplexed onto the PUSCH on which the CSI report is transmitted and / or the number of CPUs (CSI Processing Units) in use by the UE at the time of CSI reporting (or CSI-RS reception). For example, for Report 1 and Report 2 configured with the same CSI report corresponding to a low latency class, even if Report 1 is multiplexed with HARQ-ACK and transmitted on a specific PUSCH and Report 2 is transmitted on another specific PUSCH without multiplexing, the latency requirement for Report 1 and Report 2 is the same. In another embodiment, for report1 for UE1 and report2 for UE2, which are configured with the same CSI report corresponding to a low latency class, even if UE1 has all of its CPUs unoccupied at the time of the corresponding CSI trigger (or CSI-RS reception) and UE2 has some of its CPUs occupied at the time of the corresponding CSI trigger (or CSI-RS reception), the latency requirements for report1 for UE1 and report2 for UE2 are applied in the same way.

[0298] Proposed method 1.7-2

[0299] If only one latency requirement is defined for an SCS (e.g., 480 kHz and / or 960 kHz or higher) used in a high frequency band (e.g., 52.6 GHz or higher), i.e., no latency requirement is defined apart from that for the lowest latency class (Ultra latency class), the UE shall not expect a CSI reporting configuration that satisfies the following three conditions:

[0300] - Wideband frequency-granularity

[0301] - A single CSI-RS resource (ie, no CRI reporting) with at most 4 CSI-RS ports

[0302] - PMI reporting with Type I Single-Panel codebook or non-PMI reporting

[0303] Specifically, the UE may not expect a CSI report setting that satisfies all three conditions simultaneously, or may not expect a CSI report setting that satisfies some (or one) of the three conditions.

[0304] Also, more generally, for SCSs (e.g., SCSs of 480 kHz and / or 960 kHz or higher) used in high frequency bands (e.g., 52.6 GHz or higher), the UE may operate in such a way that it does not expect CSI reporting settings that meet all or some of these three conditions.

[0305] 1.8. How to apply the delay requirement for aperiodic CSI reporting

[0306] In the FR2-2 band, the CSI computation delay requirement for 480 kHz and / or 960 kHz SCS is newly defined in computation delay requirement 2 of Table 5.4-2 of TS 38.214. As a result, Table 5.4-2 of 3GPP TS 38.214, which defines the CSI computation delay requirement, may be changed from Table 18 to Table 20. Table 17 will be used without change.

[0307] [Table 20]

[0308] In this case, the μ value is min(μ PDCCH , μ CSI-RS , μ UL ) is defined as follows. Referring to 5.4 of 3GPP TS 38.214, "μ of table 5.4-1 and table 5.4-2 corresponds to the min (μ PDCCH , μ CSI-RS , μ UL ) where the μ PDCCH corresponds to the subcarrier spacing of the PDCCH with which the DCI was transmitted and μ UL corresponds to the subcarrier spacing of the PUSCH with which the CSI report is to be transmitted and μ CSI-RS corresponds to the minimum subcarrier spacing of the aperiodic CSI-RS triggered by the DCI."

[0309] That is, the CSI calculation delay requirement is determined based on the minimum value of μ for PDCCH, CSI-RS, and PUSCH. PDCCH , μ CSI-RS , μ UL A rule is needed to determine which CSI computation delay requirement should be applied to the mixed numerology case where μ=5 or μ=6 is mixed with a smaller value (e.g., μ=4).

[0310] In this invention, the application method of the CSI calculation delay requirement will be explained in the following three cases.

[0311] - μ PDCCH , μ CSI-RS , μ ULIf both values ​​are 5 or greater

[0312] - μ PDCCH , μ CSI-RS , μ UL If any one of the values ​​is 5 or greater

[0313] - μ CSI-RS If the value is 5 or greater

[0314] More specifically, the UE and / or network (or gNB) operates in accordance with the following methods (1.8-1), (1.8-2a), (1.8-2b), (1.8-2c), (1.8-3a) and / or (1.8-3b): The UE and / or network operates in accordance with any one or a combination of two or more of the following methods.

[0315] Method (1.8-1)

[0316] min(μ PDCCH , μ CSI-RS , μ UL )=5 or min(μ PDCCH , μ CSI-RS , μ UL ) = 6, Table 20 is used. Which value of Z1 (and Z1'), Z2 (and Z2'), or Z3 (and Z3') to apply is determined according to the triggered CSI report, as in the operation of a conventional communication system. In particular, when a CSI report to which Z1 (and Z1') is applied is triggered, the Z1 and Z1' values ​​in Table 20 are used as the CSI calculation delay requirement even in a situation where there is no occupied CPU and HARQ-ACK or data is not multiplexed onto the PUSCH (i.e., a case where the Z1 and Z1' delay requirements in Table 17 are applied in Rel-15 / 16, which corresponds to the condition for using Table 17 described in 1.7).

[0317] Method (1.8-2a)

[0318] μ PDCCH , μ CSI-RS , μ ULIf at least one of the values ​​is 5 or 6, then Table 20 is used. PDCCH , μ CSI-RS , μ UL If there is at least one pneumology of 5 or more, Table 17 is not used. For example, μ PDCCH = 3, μ CSI-RS = 3, μ UL If μ = 5, the value defined in Table 20 is used as the CSI computation delay requirement. PDCCH Since μ=3 is the minimum value, one of Z1 (and Z1'), Z2 (and Z2'), and Z3 (and Z3') corresponding to μ=3 in Table 20 is used depending on the type of CSI report to be triggered. In particular, when a CSI report to which Z1 (and Z1') is applied is triggered, the Z1 and Z1' values ​​in Table 20 are used as the CSI calculation delay requirement even in a situation where there is no occupied CPU and HARQ-ACK or data (transmission block) is not multiplexed onto the PUSCH (i.e., a case where the Z1 and Z1' delay requirements in Table 5.4-1 in Rel-15 / 16 are applied, which corresponds to the conditions for using Table 5.4-1 described in 1.7).

[0319] Method (1.8-2b)

[0320] μ PDCCH , μ UL , Table 20 is used when at least one of the pneumothoraxes for aperiodic CSI-RS triggered by PDCCH (DCI) is 5 or 6. For example, μ PDCCH If μ = 5, CSI-RS and μ UL Regardless of the value, Table 20 is used for the CSI calculation delay requirement. PDCCH = 3, μ UL = 3, and the multiple pneumatologies for the two aperiodic CSI-RSs triggered by the corresponding PDCCH are μ = 3 and μ = 5, respectively, then min(μ PDCCH , μ CSI-RS , μ UL) = 3, but a CSI-RS with a pneumatology of 5 or more is configured by the corresponding PDCCH, so Table 20 is used as the CSI calculation delay requirement.

[0321] Method (1.8-2c)

[0322] μ PDCCH , μ CSI-RS , μ UL If at least one μ value among them is 3 or less, Table 17 or Table 20 is used. The delay to be applied depending on the type of CSI report to be triggered is determined to be one of Z1 (and Z1'), Z2 (and Z2'), and Z3 (and Z3'). When a CSI report to which Z1 and Z1' are applied is triggered in a specific situation (i.e., when there is no occupied CPU and HARQ-ACK or data is not multiplexed onto the PUSCH) (i.e., when the Z1 and Z1' delay requirements in Table 5.4-1 in Rel-15 / 16 are applied, and the conditions for using Table 17 described in 1.7 apply), one of Table 17 and Table 20 is selected and applied.

[0323] Method (1.8-3a)

[0324] μ CSI-RS If the value is 5 or 6, then Table 20 is used. PDCCH and / or μ UL Regardless of the value of μ CSI-RS For values ​​greater than or equal to 5, Table 20 is used. For example, μ CSI-RS = 6, Table 20 is used. In particular, when a CSI report to which Z1 (and Z1') is applied is triggered, the Z1 and Z1' values ​​in Table 20 are used as the CSI calculation delay requirement even in a situation where there is no occupied CPU and HARQ-ACK or data is not multiplexed onto the PUSCH (i.e., a case where the Z1 and Z1' delay requirements in Table 5.4-1 in Rel-15 / 16 are applied, which corresponds to the condition for using Table 17 described in 1.7).

[0325] Method (1.8-3b)

[0326] If at least one of the pneumologies of the aperiodic CSI-RS triggered by the PDCCH (DCI) is 5 or 6, Table 20 is used. PDCCH and / or μ UL and / or μ CSI-RS Regardless of the value, Table 20 is used when at least one of the pneumologies of the aperiodic CSI-RS triggered by the PDCCH is 5 or greater. In particular, when a CSI report to which Z1 (and Z1') is applied is triggered, the Z1 and Z1' values ​​in Table 20 are used as the CSI calculation delay requirement even in a situation where there is no occupied CPU and HARQ-ACK or data is not multiplexed onto the PUSCH (i.e., a case where the Z1 and Z1' delay requirements in Table 5.4-1 in Rel-15 / 16 apply, which corresponds to the condition for using Table 17 described in 1.7).

[0327] 1.9. CPU occupancy for aperiodic CSI reporting

[0328] 5.2.1.6 (CSI processing criteria) of TS 38.214 defines the rules shown in Table 21 for the CPU (CSI processing unit) to be used / occupied for processing CSI reports in the UE when aperiodic CSI reporting is triggered.

[0329] [Table 21]

[0330] According to Table 21, when a specific situation and / or a specific CSI reporting setting is triggered, the UE operates to use / occupy all available CPUs. The specific situation refers to a situation that corresponds to the conditions for using Table 17 described in 1.7, but where there is no CPU occupied when the CSI is triggered and where HARQ-ACK or data (= transmission block) is not multiplexed onto the PUSCH on which the corresponding CSI report is transmitted. Also, the specific CSI reporting setting refers to a setting that corresponds to the conditions for using Table 17 described in 1.7, but where "the CSI corresponds to a single CSI with wideband frequency-granularity and to at most 4 CSI-RS ports in a single resource without CRI report, and where codebookType is set to 'typeI-SinglePanel' or where reportQuantity is set to 'cri-RI-CQI'." In this way, the short processing delay of Table 17 is met by the UE operating to use / occupy all CPUs in the specific situation / setting. In other words, the entire CPU of the UE is used and / or dedicated only for specific situations and specific CSI reporting configurations where short processing delays are applied, as in Table 17.

[0331] On the other hand, only CSI computation delay requirement 2 is defined and applied to the 480 kHz and / or 960 kHz SCS (as described above). That is, since CSI computation delay requirement 1 is not defined for the 480 kHz and / or 960 kHz SCS, the UE does not need to use / occupy the entire CPU to process the CSI report for the CSI report for which the corresponding SCS / pneumatology is configured. In other words, using / occupying the entire CPU for one CSI report processing for the long period of time required for CSI computation delay requirement 2 (meaning a relatively long period of time compared to requirement 1) results in inefficient CPU usage, and since the entire CPU is used / occupied during this period, all aperiodic CSI reports triggered during this period may not be updated.

[0332] If Table 17 is not used as the CSI calculation delay requirement, the UE operation needs to be changed so that the entire CPU of the UE is not used / occupied.

[0333] Section 1.9 explains how to apply the CSI computation delay requirement in the following three sections:

[0334] - μ PDCCH , μ CSI-RS , μ UL If both values ​​are 5 or greater

[0335] - μ PDCCH , μ CSI-RS , μ UL If any one of the values ​​is 5 or greater

[0336] - μ CSI-RS If the value is 5 or greater

[0337] More specifically, the UE and / or the network (or gNB) operates according to the following methods (1.9-1), (1.9-2), and / or (1.9-3). The UE and / or the network operates by one or a combination of two or more of these methods. Alternatively, in other cases, when Table 17 is not defined / used / applied for the CSI calculation delay requirement of aperiodic CSI reporting, the UE may use a portion of the available CPU (e.g., O) instead of configuring it to use / occupy all CPUs. CPU =K s , where K s The CSI-RS resource set for channel measurement is used / occupied only by the UE.

[0338] Method (1.9-1)

[0339] min(μ PDCCH , μ CSI-RS , μ UL )=5 or min(μ PDCCH , μ CSI-RS , μ UL ) = 6, the calculation delay requirement of the corresponding CSI report is used / applied in Table 20, and Table 17 is not used / applied. In this case, the UE uses a part of the available CPU (e.g., O CPU =K s , where K s The CSI-RS resource set for channel measurement is used / occupied only when the number of CSI-RS resources in the CSI-RS resource set for channel measurement is the same as the number of CSI-RS resources in the CSI-RS resource set for channel measurement. Therefore, the rules in Table 21 are appropriately modified to reflect the method (1.9-1). For example, the rules are modified as shown in Table 22 or Table 23, but are not limited to this.

[0340] [Table 22]

[0341] [Table 23]

[0342] Method (1.9-2)

[0343] μ PDCCH , μ CSI-RS , μ UL If at least one of the conditions is 5 or 6, Table 20 is used and / or applied as the CSI calculation delay requirement for the corresponding CSI report, and Table 17 is not used and / or applied. Alternatively, this condition can be applied by μ CSI-RS Instead of using / occupying the entire CPU, the UE operates to use and / or occupy only a portion of the available CPU. For example, CPU =K s It becomes. K s is the number of CSI-RS resources in the CSI-RS resource set for channel measurement. Accordingly, the rules in Table 21 are appropriately modified to reflect Method (1.9-2). For example, modified as shown in Table 24 or Table 25, but not limited thereto.

[0344] [Table 24]

[0345] [Table 25]

[0346] Method (1.9-3)

[0347] μ CSI-RSIf the value is 5 or 6, Table 20 is used and / or applied as the CSI calculation delay requirement for the corresponding CSI report, and Table 17 is not used and / or applied. Alternatively, this condition can be applied to μ as in Method (1.8-3b). CSI-RS Instead of being configured to use / occupy the entire CPU, the UE operates to use and / or occupy only a portion of the available CPU. For example, CPU =K s It becomes. K s is the number of CSI-RS resources in the CSI-RS resource set for channel measurement. Accordingly, the rules in Table 21 are appropriately modified to reflect Method (1.9-2), for example, but not limited to, Table 26 or Table 27.

[0348] [Table 26]

[0349] [Table 27]

[0350] 1.10. Extra PDSCH processing time

[0351] As per 5.3 of 3GPP TS 38.214 (see Table 28), the interval from the last symbol of the PDSCH to the first symbol of the PUCCH in which the HARQ-ACK for the corresponding PDSCH is transmitted is T proc,1 If it is guaranteed to be greater, the UE provides a valid HARQ-ACK.

[0352] [Table 28] JPEG0007756723000043.jpg225163

[0353] At this time, d 1,1 can be understood as the extra processing time added to ensure PDSCH processing time when the number of symbols of each PDSCH is less than a specific number, and d2 can be understood as the extra processing time added when a PUCCH with a larger priority index overlaps with a PUCCH / PUSCH with a smaller priority index.

[0354] Meanwhile, new N1 values ​​for 480 kHz and / or 960 kHz SCS will be defined in the FR2-2 band, with the newly defined N1 value for 480 kHz being X1 times the N1 value for 120 kHz SCS, and the N1 value for 960 kHz being X2 times the N1 value for 120 kHz SCS. For example, to ensure the same absolute time as the 120 kHz processing time, the N1 values ​​for 480 kHz and 960 kHz may be defined as 4 and 8 times the N1 value for 120 kHz, respectively, using X1=4 and X2=8, as shown in Table 9.

[0355] At this time, T proc,1 When calculating N1, d 1,1 , d2 are added in the same ratio, so the scale between them must be the same. In other words, if the newly defined N1 value for a particular SCS is scaled by X times compared to the previous value, then d 1,1 and / or d2 also needs to be scaled by a factor of X. For example, d 1,1 If =1, as shown in Table 9, N1 for 120 kHz is 20 symbols, so d 1,1 = 1 has the effect of 5% extra processing time compared to N1, but since N1 for 960 kHz is 160 symbols, d 1,1= 1 can be expected to have only 0.6% extra processing time effect compared to N1. As another example, when d1,1 = 6, at 120 kHz, d 1,1 By adding d, the effect of increasing the processing time by about 30% can be expected, but at 960kHz, the effect of increasing the processing time can only be expected by a maximum of about 3.75%. 1,1 We need to scale d2 by the same factor as N1. Similarly, we need to scale d3 by the same factor as N2.

[0356] (Method 1.10-1)

[0357] T proc,1 When calculating, for 480kHz SCS, d 1,1 and / or d2 scaled by a factor of 4, and for 960 kHz SCS, d 1,1 and / or d2 scaled by 8. 1,1 and / or the respective scaling methods for d2 are in accordance with the following examples and subsequent explanations.

[0358] (Example 1.10-1-1): For 480 kHz SCS, d defined in conventional Rel-15 / 16 1,1 and / or the rules for d2 are changed as per Table 29.

[0359] [Table 29]

[0360] At this time, d 1,1The method for determining the values ​​of d1,1 and / or d2 is not limited to the method in Example 1.10-1-1, and may be modified for each case. For example, for PDSCH mapping type A, d1,1 may be calculated as 4*(7-i), or d1,1 may be calculated as 4*7-i. Furthermore, d2 may be the value reported by the UE that is used without scaling, or may be scaled by four or expressed in other formats. For PDSCH mapping type B, when L >= 4 and L <= 6, d1,1 may be calculated as 4*(7-L), or d1,1 = 4*7-L. When L = 3, d1,1 may be calculated as 4*(3+min(d,1)), or d1,1 = 4*3+min(d,1) or d1,1 = 3+4*min(d,1). When L=2, it may be calculated as d1,1=4*(3+d), or as d1,1=4*3+d or d1,1=3+4*d.

[0361] (Example 10.1-1-2): For 960 kHz SCS, d defined in conventional Rel-15 / 16 1,1 and / or the rules for d2 are changed as per Table 30.

[0362] [Table 30]

[0363] In this case, the method for determining the values ​​of d1,1 and / or d2 is not limited to the method in Example 10.1-1-2, and may be modified for each case. For example, for PDSCH mapping type A, d1,1 may be calculated as 8*(7-i), or d1,1 may be calculated as 8*7-i. Furthermore, d2 may be the value reported by the UE that is used without scaling, or may be scaled by 8 or expressed in another format. For PDSCH mapping type B, when L>=4 and L<=6, d1,1 may be calculated as 8*(7-L), or d1,1 may be calculated as 8*7-L. When L=3, d1,1 may be calculated as 8*(3+min(d,1)), or d1,1 may be calculated as 8*3+min(d,1) or d1,1=3+8*min(d,1). When L=2, it may be calculated as d1,1=8*(3+d), or as d1,1=8*3+d, or as d1,1=3+8*d.

[0364] (Method 1.10-2)

[0365] T proc,1 When calculating, for 480kHz SCS, d 1,1 is scaled by X1, d2 is scaled by X2, and for 960kHz SCS, d 1,1 is scaled by Y1 and d2 is scaled by Y2. X1, X2, Y1, and Y2 are predefined for each SCS, set by higher layer signaling such as RRC, or set by DCI indication. 1,1 and / or d2, respectively, according to the following examples and subsequent explanations.

[0366] (Example 1.10.2-1): For 480 kHz SCS, d defined in conventional Rel-15 / 16 1,1 and / or the rules for d2 are changed as per Table 31.

[0367] [Table 31]

[0368] At this time, d 1,1 The method for determining the value of d2 is not limited to the method in Example 1.10-2-1, and may be modified for each case. For example, for PDSCH mapping type A, d 1,1 =X1*(7-i) 1,1 =X1*7-i. Also, d2 may be calculated as the value reported by the UE without scaling, or may be scaled by X2 or expressed in other formats. For PDSCH mapping type B, when L >= 4 and L <= 6, d 1,1 =X1*(7-L) 1,1 =X1*7-L. When L=3, d 1,1 =X1*(3+min(d,1)), and d 1,1 =X1*3+min(d,1) or d 1,1 =3+X1*min(d,1). When L=2, d 1,1 You can also calculate it as =X1*(3+d), and d 1,1 =X1*3+d or d 1,1 It can also be calculated as =3+X1*d.

[0369] (Example 1.10-2-2): For 960 kHz SCS, d defined in conventional Rel-15 / 16 1,1 and / or the rules for d2 are changed as per Table 32.

[0370] [Table 32]

[0371] At this time, d 1,1 The method for determining the value of d and / or d2 is not limited to the method of the second embodiment, and may be modified for each case. For example, for PDSCH mapping type A, 1,1 = Y1 * (7-i) 1,1= Y1 * 7 - i. Also, d2 may be the value reported by the UE without scaling, or may be scaled by Y2 or expressed in other formats. For PDSCH mapping type B, when L >= 4 and L <= 6, d 1,1 = Y1 * (7-L) 1,1 = Y1*7-L. When L=3, d 1,1 = Y1 * (3 + min (d, 1)) 1,1 =Y1*3+min(d,1) or d 1,1 =3+Y1*min(d,1). When L=2, d 1,1 You can also calculate it as =Y1*(3+d), and d 1,1 =Y1*3+d or d 1,1 It can also be calculated as =3+Y1*d.

[0372] Furthermore, T for 480kHz or 960kHz SCS proc,1 When calculating T ext The value may also be scaled, e.g., depending on the specific situation (or if certain conditions are met), T ext will be a non-zero value, but T for 480 kHz or 960 kHz SCS proc,1 When calculating, do not use this value as it is, but use a scaled value. At this time, scaling is performed by the above-mentioned d 1,1 , d2, it is multiplied by 4 for 480 kHz, by 8 for 960 kHz, or set to a predefined value or an RRC set value, etc.

[0373] The aforementioned T proc,1 d for calculation 1,1 and / or d2 and / or T ext The way to scale and use the values ​​is T proc,1 In the calculation of , it can be applied in its entirety or only in part. For example, d 1,1 is scaled by a factor of 4 or 8 by the SCS, and T proc,1 Apply to the calculation formula, and other d2 or Text are applied to the calculation formula as is.

[0374] The aforementioned d 1,1 and / or d2 and / or T ext The method of scaling and using values ​​can be applied regardless of the scheduling method of the PDSCH, for example, when one PDSCH is scheduled in one DCI, and when multiple PDSCHs are scheduled in one DCI.

[0375] 1.11. Extra PUSCH preparation time

[0376] As per 6.4 of TS 38.214 (see Table 33), the interval from the last symbol of the PDCCH that schedules the PUSCH for TB transmission to the first symbol of the corresponding PUSCH is T proc,2 If a larger guarantee is given, the UE transmits the corresponding TB.

[0377] [Table 33] JPEG0007756723000049.jpg220168

[0378] At this time, d 2,1 If the first symbol of each PUSCH consists of only DM-RS, 2,1 = 0, and if DM-RS and data are multiplexed in the first symbol, d 2,1 = 1. d2 can be understood as the extra preparation time added when a PUSCH with a higher priority index is overlapped with a PUCCH with a lower priority index. 2,2 can be understood as the extra time for when BWP conversion is triggered.

[0379] On the other hand, when defining the N2 values ​​for 480 kHz and / or 960 kHz SCS in the FR2-2 band, the N2 value for 480 kHz is determined as X1 times the N2 value for 120 kHz SCS, and the N2 value for 960 kHz is determined as X2 times the N2 value for 120 kHz SCS. For example, if X1=4 and X2=8, the N2 values ​​for 480 kHz and 960 kHz are defined as 4 and 8 times the N2 value for 120 kHz, respectively, as shown in Table 34 below.

[0380] [Table 34]

[0381] At this time, T proc,2 When calculating N2, d 2,1 , d2 are added in the same ratio, so if the N2 value is scaled by X for a particular SCS, d 2,1 and / or d2 also needs to be scaled by a factor of X.

[0382] (Method 1.11-1)

[0383] T proc,2 When calculating, for 480kHz SCS, d 2,1 and / or d2 scaled by a factor of 4, and for 960 kHz SCS, d 2,1 and / or d2 scaled by 8. 2,1 and / or d2, respectively, according to the following examples and subsequent explanations.

[0384] (Example 1.11-1-1): For 480 kHz SCS, if the first symbol of PUSCH is DM-RS only, 2,1 =0, otherwise d 2,1= 4. d2 is set to 4 times the value reported by the UE if "If a PUSCH of a larger priority index would overlap with a PUCCH of a smaller priority index", and set to 0 otherwise.

[0385] (Example 1.11-1-2): For 960 kHz SCS, if the first symbol of PUSCH is DM-RS only, 2,1 =0, otherwise d 2,1 = 8. d2 is set to 8 times the value reported by the UE if "If a PUSCH of a larger priority index would overlap with a PUCCH of a smaller priority index", and set to 0 otherwise.

[0386] (Method 1.11-2)

[0387] T proc,2 When calculating, for 480kHz SCS, d 2,1 is scaled by X1, d2 is scaled by X2, and for 960kHz SCS, d 2,1 is scaled by Y1 and d2 is scaled by Y2. X1, X2, Y1, and Y2 are predefined for each SCS, set by higher layer signaling such as RRC, or set by DCI instruction, etc. 2,1 and / or d2, respectively, according to the following examples and subsequent explanations.

[0388] (Example 1.11-2-1): For 480 kHz SCS, if the first symbol of PUSCH is DM-RS only, 2,1 =0, otherwise d 2,1=X1. d2 is set to the value reported by the UE multiplied by X2 if "If a PUSCH of a larger priority index would overlap with a PUCCH of a smaller priority index", and set to 0 otherwise.

[0389] (Example 1.11-2-2): For 960 kHz SCS, if the first symbol of PUSCH is DM-RS only, 2,1 =0, otherwise d 2,1 = Y1. d2 is set to the value reported by the UE multiplied by Y2 if "If a PUSCH of a larger priority index would overlap with a PUCCH of a smaller priority index", and set to 0 otherwise.

[0390] d for 480kHz and 960kHz SCS 2,2

[0391] In Rel-15 / 16, for 15kHz to 120kHz SCS, T proc,2 used to calculate d 2,2 The BWP switching time values ​​defined in TS 38.133 are used as they are, and the values ​​are defined in Table 35. (Extracted from TS 38.133, 8.2.2.5 (Interruptions due to Active BWP switching requirement))

[0392] [Table 35]

[0393] Meanwhile, the values ​​for 480 kHz and 960 kHz are further defined as shown in Table 36.

[0394] [Table 36]

[0395] d for 480kHz and / or 960kHz SCS 2,2 Also, as mentioned above, 2,1 Or like d2, T proc,2 For example, if you use the values ​​in the table above, the d for a 480 kHz SCS is 2,2 = 4*17*0.03125 or d 2,2 =x3*17*0.03125, and d for 960kHz SCS 2,2 = 8*33*0.015625 or d 2,2 = Y3*33*0.015625. Alternatively, d for 480 kHz and / or 960 kHz SCS 2,2 is used as the scheduled value of the BWP transition time value for 120 kHz SCS. For example, d for 480 kHz SCS 2,2 = 4*5*0.03125 or d 2,2 = x4*5*0.03125, and d for 960kHz SCS 2,2 = 8*5*0.015625 or d 2,2 =Y4*5*0.015625 is used, where X3, X4, Y3, and Y4 are either predefined for each SCS, or set by higher layer signaling such as RRC, or set by a DCI instruction or the like.

[0396] Alternatively, d for 480 kHz and / or 960 kHz SCS 2,2 may use the BWP transition time values ​​defined for 480 kHz and 960 kHz SCS without scaling. For example (using the table above), for 480 kHz SCS, 2,2 =17*0.03125, d for 960kHz SCS 2,2 = 33 * 0.015625 to T proc,2 Apply during calculation.

[0397] Furthermore, T for 480kHz or 960kHz SCS proc,2 In the calculation of T ext and / or T switch The value may also be scaled, e.g., depending on the specific situation (or if certain conditions are met), T ext or T switch The value is non-zero, but the T for 480 kHz or 960 kHz SCS proc,2 In the calculation of , this value is not used as it is, but a scaled value is used. At this time, scaling is 2, 1, d 2, As with 2 and d2, the frequency is multiplied by 4 for 480 kHz and 8 for 960 kHz, or it is set to a predefined value or an RRC setting value.

[0398] The aforementioned T proc,2 For the calculation of d 2, 1, d 2, 2, d2 and / or T ext , T switch The way to scale and use the values ​​is T proc,2 In the calculation of , it can be applied in its entirety or in part. For example, d 2,1 Depending on the SCS, the T proc,2 Apply to the formula and other d 2, 2, d2 or T ext , T switch is applied directly to the calculation formula.

[0399] The aforementioned d 2, 1, d 2,2 The method of scaling and using the d2 value and / or the d2 value may be applied regardless of the scheduling method of the PUSCH, for example, when one PUSCH is scheduled for one DCI, and when multiple PUSCHs are scheduled for one DCI.

[0400] 1.12. HARQ Feedback Timing Indicator field in the successRAR

[0401] The 3-bit field "PDSCH-to-HARQ_feedback timing indicator field" in DCI format 1_0 is defined as [1, 2, 3, 4, 5, 6, 7, 8] for SCS 120 kHz and below, regardless of SCS. However, for 480 kHz and 960 kHz SCS, the RAN1#107-e meeting decided to use larger values ​​(also using 3 bits) to indicate [7, 8, 12, 16, 20, 24, 28, 32] for 480 kHz and [13, 16, 24, 32, 40, 48, 56, 64] for 960 kHz.

[0402] Meanwhile, 8.2A (Random access response - Type-2 random access procedure) of 38.213 states that when a UE detects a CRC-scrambled DCI format 1_0 in MsgB-RNTI and receives the associated PDSCH, if the RAR message is successRAR, the position of the PUCCH slot for transmitting the HARQ-ACK is determined by the value of the "HARQ Feedback Timing Indicator field," a 3-bit field in the successRAR. Table 37 is an excerpt from 8.2A of 38.213.

[0403] [Table 37] JPEG0007756723000054.jpg162167

[0404] Also, 6.1.5a of 38.321 defines each field of successRAR, among which "HARQ Feedback Timing Indicator" is specified as a "PDSCH-to-HARQ feedback timing indicator field" for MSGB HARQ feedback, and the specific value is to be defined in 8.2A of 38.213 excerpted above. As a result, the PUCCH slot position for MSGB HARQ feedback in the 2-step RACH procedure is defined as n+k+Δ, where n is the slot index for receiving the PDSCH, k is [1, 2, 3, 4, 5, 6, 7, 8], and Δ is considered to be the time margin for PUSCH transmission. Δ is defined in Table 6.1.2.1.1-5 of TS 38.214, and the RAN1♯107-e meeting newly defined "Δ=24" for 480 kHz and "Δ=48" for 960 kHz.

[0405] In this situation, if the conventional [1, 2, 3, 4, 5, 6, 7, 8] is used for the 480 kHz and / or 960 kHz SCSs to determine the slot position for transmitting HARQ feedback, the position of slot n for receiving the PDSCH containing the RAR message is significantly restricted in order to align the corresponding slot position with the uplink slot. This is because the slot configuration for the 480 kHz and / or 960 kHz SCSs is likely to be aligned with the semi-static UL:DL configuration of the 120 kHz SCS. Therefore, for example, when UL:DL = 1:4, there may be no UL slot among the 16 slots of the 480 kHz SCS (32 slots for 960 kHz). Therefore, the k value must also be changed to a larger value, like the value of the "PDSCH-to-HARQ_feedback timing indicator field" of DCI 1_0 for 480 / 960 kHz.

[0406] Meanwhile, the Δ value defined for 480 / 960 kHz is determined as a value to cover the time corresponding to N1 (i.e., PDSCH processing time) for the corresponding SCS and the time for transmitting the RAR message to the upper layer. Therefore, if the 'PDSCH-to-HARQ_feedback timing indicator field' value of DCI 1_0 for 480 / 960 kHz is used as is to determine the PUCCH slot position for MSGB HARQ feedback, the N1 value for the corresponding SCS will be unnecessarily added redundantly.

[0407] Considering all of this, in the 2-step RACH process, the k value for calculating the PUCCH slot position n+k+Δ for MSGB HARQ feedback is one of the following values:

[0408] - 480kHz: [7, 8, 12, 16, 20, 24, 28, 32], 960kHz: [13, 16, 24, 32, 40, 48, 56, 64]

[0409] This value is the same as the PDSCH-to-HARQ_Feedback Timing Indicator field value for DCI 1_0. Although there is an inefficiency in adding the N1 value redundantly, it has the advantage of being able to use a consistent value for 480 / 960 kHz.

[0410] - 480kHz: [1, 2, 6, 10, 14, 18, 22, 26], 960kHz: [1, 4, 12, 20, 28, 36, 42, 50]

[0411] This value is the first candidate value minus the time corresponding to N1 for the corresponding SCS. Specifically, it means a value reduced by floor(N1 / 14) (or ceil(N1 / 14)-1). By setting the minimum value to 1, it is possible to indicate from the first slot after PDSCH reception and Δ has elapsed.

[0412] - 480kHz:[0, 1, 5, 9, 13, 17, 21, 25], 960kHz:[0, 3, 11, 19, 27, 35, 41, 49]

[0413] This value is the first candidate value minus the time corresponding to N1 for the corresponding SCS. Specifically, it means a value reduced by ceil(N1 / 14). The minimum value 0 is set to allow indication from the last slot of the Δ period after receiving the PDSCH.

[0414] - 480kHz: [1, 5, 9, 13, 17, 21, 25, 29], 960kHz: [1, 9, 17, 25, 33, 41, 49, 57]

[0415] This value is indicated from the first slot after PDSCH reception and Δ has elapsed, and the interval between each indication value is fixed at 4 or 8. The interval is set to 4 / 8 because this is the length of one slot of the 120 kHz SCS in the corresponding SCS standard.

[0416] - 480kHz: [4, 8, 12, 16, 20, 24, 28, 32], 960kHz: [8, 16, 24, 32, 40, 48, 56, 64]

[0417] This value is a value obtained by fixing the interval between each instruction value at 4 or 8 from the last slot of the Δ period after receiving the PDSCH.

[0418] - 480kHz: [1, 4, 8, 12, 16, 20, 24, 28], 960kHz: [1, 8, 16, 24, 32, 40, 48, 56]

[0419] This value is obtained by reducing the maximum indication value to 28 or 56 in order to indicate from the first slot after PDSCH reception and Δ has elapsed.

[0420] - 480kHz: [1, 8, 12, 16, 20, 24, 28, 32], 960kHz: [1, 16, 24, 32, 40, 48, 56, 64]

[0421] This value is indicated from the first slot after PDSCH reception and Δ has elapsed, and the maximum value that can be indicated is maintained at 32 or 64.

[0422] In addition, the minimum and maximum values ​​(among the eight values) of the above-listed candidate values ​​are particularly important because they correspond to the range in which the PUCCH slot for MSGB HARQ feedback can be located. In a situation where early HARQ feedback for MSGB is required, the value of k is determined to include the minimum value '1'. This allows the earliest feedback to be transmitted from the time of PDSCH reception.

[0423] Furthermore, for 480 kHz and / or 960 kHz SCS, to eliminate the inefficiency of considering N1 redundantly in n+k+Δ for determining the PUCCH slot position, the number of slots corresponding to 0.5 msec may be used instead of Δ. Since 0.5 msec corresponds to 16 slots for 480 kHz SCS and 32 slots for 960 kHz, in the 2-step RACH process, the PUCCH slot position for MSGB HARQ feedback is determined as n+k+16 for 480 kHz SCS and n+k+32 for 960 kHz SCS (where n is the PDSCH reception slot and k is one of the seven candidate values). Alternatively, by providing a margin (of one 120 kHz slot), the PUCCH slot position for 480 kHz SCS is determined as n+k+20 and for 960 kHz SCS is determined as n+k+40.

[0424] On the other hand, the contents of the present invention are not limited to uplink and / or downlink signal transmission and reception. For example, the contents of the present invention can also be applied to direct communication between terminals. Furthermore, the base station in the present invention is a concept that includes not only a base station but also a relay node. For example, the operation of the base station in the present invention may be performed by the base station or by a relay node.

[0425] The above-mentioned example of the proposed method is also included as one of the methods of implementing the present invention, and therefore can be regarded as a kind of proposed method. In addition, the above-mentioned proposed methods may be implemented independently, or may be implemented in the form of a combination (or merging) of some of the proposed methods. Information regarding whether or not the above-mentioned proposed method is applied (or information regarding the rules of the proposed method) can be specified so that the base station notifies the terminal or the transmitting terminal notifies the receiving terminal by a predetermined signal (e.g., a physical layer signal or a higher layer signal).

[0426] Example

[0427] FIG. 9 is a flowchart illustrating a signal transmission and reception method according to an embodiment of the present invention.

[0428] Referring to FIG. 9, an embodiment of the present invention is performed by a terminal and includes the steps of receiving a PDCCH that triggers a CSI report (S401), receiving a CSI-RS based on the PDCCH (S403), and transmitting a PUSCH including a CSI report based on a measurement result for the CSI-RS (S405).

[0429] In addition to the operations in FIG. 9, any one or more of the operations described in 1 above may be further performed.

[0430] For example, referring to 1.5 to 1.9, the CSI report is aperiodic CSI report. PDCCH μ is the SCS setting of the PDCCH including DCI for triggering CSI, and is expressed as the first SCS setting. CSI-RS is the minimum SCS configuration of the aperiodic CSI-RS triggered by DCI, and is expressed as the second SCS configuration. UL is the SCS setting of the PUSCH on which the CSI report is transmitted, and is expressed as the third SCS setting.

[0431] Referring to method (1.8-2a), if any one of the first SCS setting, the second SCS setting, and the third SCS setting is 5 or 6, even if the PUSCH does not include HARQ-ACK or TB and there is no CPU occupied for the terminal, CSI calculation delay requirement 2 in Table 20 is used and CSI calculation delay requirement 1 in Table 17 is not used.

[0432] Referring to Table 19, when the conventional PUSCH does not include HARQ-ACK or TB and there is no CPU occupied for the terminal, CSI calculation delay requirement 1 in Table 17 is used. According to the disclosure of the present invention, the operation when any one of the first SCS setting, the second SCS setting, and the third SCS setting is 5 or 6 has been changed. Therefore, CSI calculation delay requirement 1 is used when none of the first SCS setting, the second SCS setting, and the third SCS setting is 5 or 6, i.e., when the maximum value of the first SCS setting, the second SCS setting, and the third SCS setting is 3 or less.

[0433] Referring to Table 17, CSI calculation delay requirement 1 is configured by a combination of Z and Z' for each SCS for the lowest latency (ultra-low latency). Referring to Table 20, CSI calculation delay requirement 2 is configured by a combination of Z and Z' for each SCS for a higher latency than CSI calculation delay requirement 1.

[0434] Referring to Table 15, Z is the number of symbols associated with the interval from the last symbol of the PDCCH that triggers a CSI report to the next uplink symbol (start symbol of the PUSCH). Z' is the number of symbols associated with the interval from the last symbol of the last received signal among the aperiodic CSI-RS resource, aperiodic CSI-IM, and aperiodic NZP CSI-RS to the next uplink symbol (start symbol of the PUSCH). If no other signal is received between the aperiodic CSI-RS and the PUSCH, Z' is the number of symbols associated with the interval from the last symbol of the CSI-RS to the start symbol of the PUSCH.

[0435] Referring to the method (1.9-2), when at least one of the first SCS setting, the second SCS setting, and the third SCS setting is 5 or 6, the PUSCH does not include HARQ-ACK or TB, and even if there is no CPU occupied for the terminal, the CSI report is sent using all CPUs (N CPu ), the CPU is occupied by the number of CSI-RS resources in the CSI-RS resource set for channel measurement (O CPU =K s ).

[0436] Referring to Table 21, if the conventional PUSCH does not include HARQ-ACK or TB and there is no CPU occupied for the UE, the CSI report occupies all CPU available to the UE (O CPU =N CPU According to the disclosure of the present invention, the operation when at least one of the first SCS setting, the second SCS setting, and the third SCS setting is 5 or 6 has been changed, so that CSI reporting is permitted to occupy all of the CPU available to the terminal when none of the first SCS setting, the second SCS setting, and the third SCS setting is 5 or 6, i.e., when the maximum value of the first SCS setting, the second SCS setting, and the third SCS setting is 3 or less.

[0437] Also, referring to 1.1, the interval between the first slot in which the PUCCH including the HARQ-ACK is transmitted and the second slot in which the PDSCH associated with the HARQ-ACK is received is determined based on the slot offset K1. The value of the DCI field (K1 field) for indicating K1 includes 7 if the SCS setting of the PUCCH is 5, and 13 if the SCS setting of the PUCCH is 6. Referring to Table 9, if the SCS setting of the PUCCH is 5, N1 is 80. Therefore, referring to 1.1-(1), if the SCS setting of the PUCCH is 5, the K1 field value is set to ceil(80 / 14)+1=7. Similarly, if the SCS setting of the PUCCH is 6, N1 is 160, and the K1 field value is set to ceil(160 / 14)+1=13.

[0438] On the other hand, referring to 1.4, the interval between the first slot in which the PUSCH including the TB is transmitted and the second slot in which the DCI scheduling the PUSCH including the TB is received is determined based on the slot offset K2. Referring to 1.4-(1), K2 is determined based on the ceil(N2 / c) value, which is expressed as a specific value j. Referring to Table 34, if the SCS setting of the PUSCH including the TB is 5, N2 is 144. Therefore, if the SCS setting of the PUSCH including the TB is 5, the specific value j is ceil(144 / 14) = 11. Similarly, if the SCS setting of the PUSCH including the TB is 6, N2 is 288, and the specific value j is ceil(288 / 14) = 21.

[0439] In addition to the operations described with respect to FIG. 9, any one or more combinations of the operations described with respect to FIGS. 1 to 8 and / or the operations described in 1 above may be further performed.

[0440] An example of a communication system to which the present invention is applied

[0441] Without being limited thereto, the various descriptions, functions, procedures, suggestions, methods and / or flow charts of the present invention disclosed in this specification may be applied to various fields requiring wireless communication / connectivity between devices (e.g., 5G).

[0442] Hereinafter, a more detailed description will be given with reference to the drawings. In the following drawings / description, the same reference numerals indicate the same or corresponding hardware blocks, software blocks or function blocks unless otherwise specified.

[0443] FIG. 10 illustrates a communication system 1 to which the present invention is applied.

[0444] Referring to FIG. 10 , a communication system 1 applicable to the present invention includes wireless devices, base stations, and a network. Here, the wireless devices refer to devices that communicate using wireless connection technologies (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 and 100b-2, an XR (eXtended Reality) device 100c, a handheld device 100d, a home appliance 100e, an IoT (Internet of Things) device 100f, and an AI server / device 400. For example, the vehicles include vehicles equipped with wireless communication capabilities, autonomous vehicles, vehicles capable of vehicle-to-vehicle communication, etc. Here, the vehicles include unmanned aerial vehicles (UAVs) (e.g., drones). XR devices include Augmented Reality (AR), Virtual Reality (VR), and 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. Mobile devices include smartphones, smart pads, wearable devices (e.g., smart watches, smart glasses), computers (e.g., laptops, 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.

[0445] The wireless devices 100a to 100f are connected to a network 300 via a base station 200. The wireless devices 100a to 100f are equipped with AI (Artificial Intelligence) technology, and 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, vehicles 100b-1 and 100b-2 can communicate directly (e.g., V2V (Vehicle to Vehicle) / V2X (Vehicle to Everything) communication). IoT devices (e.g., sensors) can also communicate directly with other IoT devices (e.g., sensors) or other wireless devices 100a to 100f.

[0446] Wireless communication / connections 150a, 150b, and 150c are performed between the wireless devices 100a to 100f and the base stations 200, and between the base stations 200. Here, the wireless communication / connections are performed using 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, Integrated Access Backhaul (IAB)) (e.g., 5G NR). Through the wireless communication / connections 150a, 150b, and 150c, the wireless devices and the base stations, and the base stations, can transmit / receive wireless signals to / from each other. For example, the wireless communication / connections 150a, 150b, and 150c can transmit / receive signals via various physical channels. To this end, according to 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.

[0447] Examples of wireless devices to which the present invention is applied

[0448] FIG. 11 shows an example of a wireless device to which the present invention can be applied.

[0449] 11, a first wireless device 100 and a second wireless device 200 transmit and receive wireless signals using various wireless access technologies (e.g., LTE, NR). Here, [first wireless device 100, second wireless device 200] corresponds to [wireless devices 100a to 100f, base station 200] and / or [wireless devices 100a to 100f, wireless devices 100a to 100f] in FIG. 10.

[0450] 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 first information / signals and then transmits a wireless signal including the first information / signals via the transceiver 106. The processor 102 also receives a wireless signal including second information / signals via the transceiver 106 and then stores information obtained from signal processing of the second information / signals 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 implementing 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 the present invention, a wireless device may also refer to a communication modem / circuit / chip.

[0451] 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 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 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 implementing 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 the present invention, a wireless device may also refer to a communication modem / circuit / chip.

[0452] The hardware elements of the wireless devices 100, 200 are described in more detail below. Without limitation, one or more protocol layers may be implemented by one or more processors 102, 202. For example, one or more processors 102, 202 may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, and 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 generate 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 and provide them to the one or more transceivers 106, 206. The one or more processors 102, 202 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.

[0453] The one or more processors 102, 202 may also be referred to as a controller, microcontroller, microprocessor, or microcomputer. The one or more processors 102, 202 may be implemented using hardware, firmware, software, or a combination thereof. For 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 embodied to include modules, procedures, functions, etc. 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 executed 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.

[0454] One or more memories 104, 204 may be coupled to one or more processors 102, 202 and may store various types 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.

[0455] One or more transceivers 106, 206 can transmit user data, control information, wireless signals / channels, etc., as referenced in the methods and / or flowcharts herein to one or more other devices. One or more transceivers 106, 206 can receive user data, control information, wireless signals / channels, etc., as referenced in the descriptions, functions, procedures, suggestions, methods and / or flowcharts herein from one or more other devices. For example, one or more transceivers 106, 206 can be coupled to one or more processors 102, 202 and can transmit and receive wireless signals. For example, one or more processors 102, 202 can 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 can control one or more transceivers 106, 206 to receive user data, control information, or wireless signals from one or more other devices. Furthermore, one or more transceivers 106, 206 are coupled to one or more antennas 108, 208, and 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 flowcharts disclosed herein via the one or more antennas 108, 208. In this specification, one or more antennas may refer to 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 by one or more processors 102, 202. The one or more transceivers 106, 206 convert the user data, control information, radio signals / channels, etc., processed by one or more processors 102, 202, from baseband signals to RF band signals. For this purpose, the one or more transceivers 106, 206 include an (analog) oscillator and / or a filter.

[0456] Examples of use of wireless devices to which this invention is applied

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

[0458] 12, wireless devices 100 and 200 correspond to the wireless devices 100 and 200 of FIG. 11 and are composed of various elements, components, units, 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. 11. For example, the transceiver 114 includes one or more transceivers 106 and 206 and / or one or more antennas 108 and 208 in FIG. 11. 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 the electrical / mechanical operations of the wireless device based on the programs / codes / instructions / information stored in the memory unit 130. The control unit 120 also transmits the information stored in the memory unit 130 to an external device (e.g., another communication device) via the communication unit 110 via a wireless / wired interface, or stores information received from an external device (e.g., another communication device) via the communication unit 110 via a wireless / wired interface in the memory unit 130.

[0459] 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. Wireless devices may be embodied in the form of, but are not limited to, a robot (FIG. 10, 100a), a vehicle (FIG. 10, 100b-1, 100b-2), an XR device (FIG. 10, 100c), a mobile device (FIG. 10, 100d), a home appliance (FIG. 10, 100e), an IoT device (FIG. 10, 100f), a digital broadcasting terminal, a hologram device, a public safety device, an MTC device, a medical device, a FinTech device (or financial device), a security device, a climate / environment device, an AI server / device (FIG. 10, 400), a base station (FIG. 10, 200), a network node, etc. Wireless devices may be mobile or fixed depending on the use case / service.

[0460] In FIG. 12, the various elements, components, units / sections and / or modules within the wireless devices 100, 200 are all connected to each other by wired interfaces or at least some are connected wirelessly by a communication section 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 the first unit (e.g., 130, 140) are connected wirelessly via the communication unit 110. Furthermore, 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 configured with a set of one or more processors. For example, the control unit 120 is configured with 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 configured with a RAM (Random Access Memory), a DRAM (Dynamic RAM), a ROM (Read Only Memory), a flash memory, a volatile memory, a non-volatile memory and / or a combination thereof.

[0461] Examples of vehicles or autonomous vehicles to which the present invention is applied

[0462] 13 is a diagram illustrating an example of a vehicle or an autonomous vehicle to which the present invention is applied. The vehicle or the autonomous vehicle may be embodied as a mobile robot, a car, a train, an aerial vehicle (AV), a ship, etc.

[0463] 13, 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 part of the communication unit 110. Blocks 110 / 130 / 140a to 140d correspond to blocks 110 / 130 / 140 in FIG. 12, respectively.

[0464] 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, roadside 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 move on the ground. The driving unit 140a includes an engine, a motor, a powertrain, 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, an inclination sensor, a weight detection 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 implements technology for maintaining a lane while driving, technology for automatically adjusting speed such as adaptive cruise control, technology for automatically driving along a predetermined route, technology for automatically setting a route and driving when a destination is set, etc.

[0465] 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 driving plan based on the obtained data. The control unit 120 controls the driving unit 140a (e.g., adjusting speed / direction) so that the vehicle or autonomous vehicle 100 moves along the autonomous driving route according to the driving plan. The communication unit 110 aperiodically 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 driving plan based on the newly obtained data / information. The communication unit 110 transmits information regarding the vehicle position, autonomous driving route, driving plan, etc. to an external server. The external server can predict traffic information data using AI technology based on information collected from the vehicle or autonomous vehicle and provide the predicted traffic information data to the vehicle or autonomous vehicle.

[0466] 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 construed 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.

[0467] [Industrial Applicability] As described above, the present invention can be applied to a variety of wireless communication systems.

Claims

1. A method for a terminal (User Equipment: UE) to transmit and receive a signal in a wireless communication system, comprising: receiving a Physical Downlink Control Channel (PDCCH) that triggers aperiodic Channel State Information (CSI) reporting; receiving a CSI-Reference Signal (CSI-RS) based on the PDCCH; and transmitting a PUSCH (Physical Uplink Shared Channel) including the CSI report containing CSI based on a measurement result for the CSI-RS; A first SCS (Subcarrier Spacing) configuration is used for the PDCCH, a second SCS configuration is used for the CSI-RS, and a third SCS configuration is used for the PUSCH; The CSI computation delay requirement 1 is: (i) the first SCS setting, the second SCS setting, and the third SCS setting are three or less; (ii) the CSI is triggered; (iii) there is no CPU (CSI processing unit) occupied by the terminal; (iv) the CSI corresponds to a single CSI having wideband frequency-granularity; and (v) the CSI is used for the CSI reporting based on the fact that it corresponds to up to four CSI-RS ports in a single resource when it does not have a CSI-RS report indicator (CRI) report and the “Codebook Type” is set to “type I-Single Panel” or the “report Quantity” is set to “cri-RI-CQI”; A signal transmission and reception method, wherein a CSI calculation delay requirement of 2 is used for the CSI reporting based on at least one of the first SCS setting, the second SCS setting, and the third SCS setting being 5 or 6.

2. 2. The signal transmission and reception method according to claim 1, wherein a Hybrid Automatic Repeat and Request-Acknowledgement (HARQ-ACK) or a transport block (TB) is not multiplexed onto the PUSCH on which the CSI report is transmitted.

3. The number of symbols associated with the interval from the last symbol of the PDCCH to the start symbol of the PUSCH is Z; The number of symbols associated with the interval from the last symbol of the CSI-RS to the start symbol of the PUSCH is Z′; The signal transmission and reception method according to claim 1 , wherein the CSI calculation delay requirements 1 and 2 are configured by a combination of Z and Z′ for each SCS setting.

4. 3. The signal transmission and reception method of claim 2, wherein the PUSCH does not include the TB or the HARQ-ACK, there is no CPU occupied for the terminal, and at least one of the first SCS setting, the second SCS setting, and the third SCS setting is 5 or 6, and the CSI report occupies CPUs equal to the number of CSI-RS resources in a CSI-RS resource set for channel measurement out of all CPUs (CSI processing units) available to the terminal.

5. 3. The signal transmission and reception method of claim 2, wherein the PUSCH does not include the TB or the HARQ-ACK, there is no CPU occupied for the terminal, and the CSI report occupies all CPUs (CSI processing units) available for the terminal based on the fact that the maximum value of the first SCS setting, the second SCS setting, and the third SCS setting is 3 or less.

6. The value of a Downlink Control Information (DCI) field for indicating the interval between a first slot in which a Physical Uplink Control Channel (PUCCH) including the HARQ-ACK is transmitted and a second slot in which a Physical Downlink Shared Channel (PDSCH) related to the HARQ-ACK is received is: 7 based on the SCS setting for the PUCCH including the HARQ-ACK being 5; The signal transmission and reception method according to claim 2, further comprising 13 based on the SCS setting for the PUCCH including the HARQ-ACK being 6.

7. A specific value for determining the interval between the first slot in which the PUSCH including the TB is transmitted and the second slot in which DCI (Downlink Control Information) scheduling the PUSCH including the TB is received is: 11 based on the SCS setting for the PUSCH including the TB being 5; The signal transmission and reception method according to claim 2 , wherein the SCS setting for the PUSCH including the TB is 6, and the SCS setting is 21.

8. In a wireless communication system, a terminal (User Equipment: UE) for transmitting and receiving a signal, at least one transceiver; at least one processor; and at least one memory operatively connected to said at least one processor and storing instructions that, when executed, cause said at least one processor to perform certain operations; The specific operation is: receiving a Physical Downlink Control Channel (PDCCH) that triggers aperiodic Channel State Information (CSI) reporting; receiving a CSI-Reference Signal (CSI-RS) based on the PDCCH; and transmitting a PUSCH (Physical Uplink Shared Channel) including the CSI report containing CSI based on a measurement result for the CSI-RS; A first SCS (Subcarrier Spacing) configuration is used for the PDCCH, a second SCS configuration is used for the CSI-RS, and a third SCS configuration is used for the PUSCH; The CSI computation delay requirement 1 is: (i) the first SCS setting, the second SCS setting, and the third SCS setting are three or less; (ii) the CSI is triggered; (iii) there is no CPU (CSI processing unit) occupied by the terminal; (iv) the CSI corresponds to a single CSI having wideband frequency-granularity; and (v) the CSI is used for the CSI reporting based on the fact that it corresponds to up to four CSI-RS ports in a single resource when it does not have a CSI-RS report indicator (CRI) report and the “Codebook Type” is set to “type I-Single Panel” or the “report Quantity” is set to “cri-RI-CQI”; A terminal, wherein a CSI calculation delay requirement of 2 is used for the CSI reporting based on at least one of the first SCS setting, the second SCS setting, and the third SCS setting being 5 or 6.

9. The terminal of claim 8, wherein a Hybrid Automatic Repeat and Request-Acknowledgement (HARQ-ACK) or a transport block (TB) is not multiplexed onto the PUSCH on which the CSI report is transmitted.

10. The number of symbols associated with the interval from the last symbol of the PDCCH to the start symbol of the PUSCH is Z; The number of symbols associated with the interval from the last symbol of the CSI-RS to the start symbol of the PUSCH is Z′; The terminal of claim 8 , wherein the CSI calculation delay requirements 1 and 2 are configured by a combination of Z and Z′ for each SCS setting.

11. 10. The terminal of claim 9, wherein, based on the fact that the TB or the HARQ-ACK is not included in the PUSCH, there is no CPU occupied for the terminal, and at least one of the first SCS setting, the second SCS setting, and the third SCS setting is 5 or 6, the CSI reporting occupies a number of CPUs (CSI processing units) equal to the number of CSI-RS resources in a CSI-RS resource set for channel measurement, out of all CPUs (CSI processing units) available to the terminal.

12. 10. The terminal of claim 9, wherein the CSI report occupies all CPUs (CSI processing units) available to the terminal based on the fact that the TB or the HARQ-ACK is not included in the PUSCH, there is no CPU occupied for the terminal, and a maximum value of the first SCS setting, the second SCS setting, and the third SCS setting is less than or equal to 3.

13. The value of a Downlink Control Information (DCI) field for indicating the interval between a first slot in which a Physical Uplink Control Channel (PUCCH) including the HARQ-ACK is transmitted and a second slot in which a Physical Downlink Shared Channel (PDSCH) related to the HARQ-ACK is received is: 7 based on the SCS setting for the PUCCH including the HARQ-ACK being 5; The terminal of claim 9, wherein the SCS setting for the PUCCH including the HARQ-ACK is 6, and the SCS setting includes 13.

14. A specific value for determining the interval between the first slot in which the PUSCH including the TB is transmitted and the second slot in which DCI (Downlink Control Information) scheduling the PUSCH including the TB is received is: 11 based on the SCS setting for the PUSCH including the TB being 5; The terminal of claim 9, wherein the SCS setting for the PUSCH including the TB is 6, and the SCS setting is 21.

15. An apparatus for a terminal (User Equipment: UE), comprising: at least one processor; and at least one computer memory operatively connected to said at least one processor and that, when executed, causes said at least one processor to perform operations; The operation is receiving a Physical Downlink Control Channel (PDCCH) that triggers aperiodic Channel State Information (CSI) reporting; receiving a CSI-Reference Signal (CSI-RS) based on the PDCCH; and transmitting a PUSCH (Physical Uplink Shared Channel) including the CSI report containing CSI based on a measurement result for the CSI-RS; A first SCS (Subcarrier Spacing) configuration is used for the PDCCH, a second SCS configuration is used for the CSI-RS, and a third SCS configuration is used for the PUSCH; The CSI computation delay requirement 1 is: (i) the first SCS setting, the second SCS setting, and the third SCS setting are three or less; (ii) the CSI is triggered; (iii) there is no CPU (CSI processing unit) occupied by the terminal; (iv) the CSI corresponds to a single CSI having wideband frequency-granularity; and (v) the CSI is used for the CSI reporting based on the fact that it corresponds to up to four CSI-RS ports in a single resource when it does not have a CSI-RS report indicator (CRI) report and the “Codebook Type” is set to “type I-Single Panel” or the “report Quantity” is set to “cri-RI-CQI”; 20. The apparatus, wherein a CSI calculation delay requirement of 2 is used for the CSI reporting based on at least one of the first SCS setting, the second SCS setting, and the third SCS setting being 5 or 6.

16. A computer-readable non-volatile storage medium containing at least one computer program that causes at least one processor to perform operations, The operation is receiving a Physical Downlink Control Channel (PDCCH) that triggers aperiodic Channel State Information (CSI) reporting; receiving a CSI-Reference Signal (CSI-RS) based on the PDCCH; and transmitting a PUSCH (Physical Uplink Shared Channel) including the CSI report containing CSI based on a measurement result for the CSI-RS; A first SCS (Subcarrier Spacing) configuration is used for the PDCCH, a second SCS configuration is used for the CSI-RS, and a third SCS configuration is used for the PUSCH; The CSI computation delay requirement 1 is: (i) the first SCS setting, the second SCS setting, and the third SCS setting are three or less; (ii) the CSI is triggered; (iii) There is no CPU (CSI processing unit) occupied by the terminal (User Equipment: UE); (iv) the CSI corresponds to a single CSI having wideband frequency-granularity; and (v) the CSI is used for the CSI reporting based on the fact that it corresponds to up to four CSI-RS ports in a single resource when there is no CSI-RS report indicator (CRI) report and the “Codebook Type” is set to “type I-Single Panel” or the “report Quantity” is set to “cri-RI-CQI”; A computer-readable non-volatile storage medium, wherein a CSI calculation delay requirement of 2 is used for the CSI reporting based on at least one of the first SCS setting, the second SCS setting, and the third SCS setting being 5 or 6.

Images