Method, apparatus, and system for transmitting and receiving an uplink sharing channel in a wireless communication system.

Abstract

To provide a method for a terminal in a wireless communication system to transmit a physical uplink shared channel (PUSCH) to a base station. [Solution] The terminal can receive configuration information for PUSCH transmission from the base station and receive a physical downlink control channel (PDCCH) for scheduling repeated PUSCH transmissions. The terminal can then determine one or more symbols that are invalid for repeated PUSCH transmissions and repeatedly transmit PUSCH with the remaining symbols other than the determined symbols.

Description

Technical Field

[0001] The present invention relates to a wireless communication system, and more particularly, to a method for transmitting and receiving a physical uplink shared channel (PUSCH) in a wireless communication system.

Background Art

[0002] 3GPP LTE(-A) defines uplink / downlink physical channels for transmitting physical layer signals. For example, a physical uplink shared channel (PUSCH), which is a physical channel for transmitting data in the uplink, a physical uplink control channel (PUCCH) for transmitting control signals, and a physical random access channel (PRACH) are defined. In the downlink, there are a physical downlink shared channel (PDSCH) for transmitting data, a physical control format indicator channel (PCFICH) for transmitting L1 / L2 control signals, a physical downlink control channel (PDCCH), a physical hybrid ARQ indicator channel (PHICH), and the like.

[0003] Of the aforementioned channels, the downlink control channel (PDCCH / EPDCCH) is a channel used by a base station to transmit uplink / downlink scheduling allocation control information, uplink transmit power control information, and other control information to one or more terminals. Because there are limitations on the resources that a base station can use for the PDCCH that it can transmit at one time, it is not possible to assign different resources to each terminal, and control information should be transmitted to any terminal by sharing resources. For example, in 3GPP® LTE(-A), four REs (Resource Elements) are bundled to create a REG (Resource Element Group), which creates nine CCEs (Control Channel Elements). One or more CCEs are combined to inform terminals of the resources that can be sent, and many terminals share and use the CCEs. Here, the number of CCEs that are combined is called the CCE combination level, and the resources to which CCEs are allocated according to the possible CCE combination level is called the search space. There are two types of search spaces: a common search space defined for each base station and a terminal-specific or UE-specific search space defined for each terminal. The terminal decodes all possible CCE combinations in the search space and determines whether they match its own PDCCH based on the user equipment (UE) identifier contained within the PDCCH. Therefore, such terminal operation inevitably involves a long decoding time for the PDCCH and consumes a lot of energy.

[0004] Following the commercialization of 4G communication systems, efforts are being made to develop improved 5G or pre-5G communication systems to meet the increasing demand for wireless data traffic. For this reason, 5G or pre-5G communication systems are referred to as Beyond 4G Network systems or Post LTE systems. To achieve high data transmission rates, 5G communication systems are being considered for implementation in ultra-high frequency (mmWave) bands (e.g., 60 GHz bands). To mitigate path loss in propagation and increase propagation distance in ultra-high frequency bands, beamforming, massive multiplexing-in-output (massive MIMO), full-dimensional multiplexing-in-output (FD-MIMO), array antennas, analog beamforming, and large-scale antenna technologies are being discussed for 5G communication systems. Furthermore, in order to improve the system network, 5G communication systems are undergoing technological development, including advanced small cells, cloud radio access networks (cloud RAN), ultra-dense networks, device-to-device communication (D2D), wireless backhaul, moving networks, cooperative communication, CoMP (Coordinated Multi-Points), and interference cancellation.In addition, 5G systems have seen the development of advanced coding modulation (ACM) methods such as FQAM (Hybrid FSK and QAM Modulation) and SWSC (Sliding Window Superposition Coding), as well as advanced access technologies such as FBMC (Filter Bank Multi Carrier), NOMA (non-orthogonal multiple access), and SCMA (sparse code multiple access).

[0005] Meanwhile, the internet, a human-centered interconnected network where humans generate and consume information, is evolving into the Internet of Things (IoT) network, where distributed components such as objects exchange and process information. Internet of Everything (IoE) technology, which combines IoT technology with big data processing technologies via connections to cloud servers and other systems, is also emerging. To realize IoT, technological elements such as sensing technology, wired and wireless communication and network infrastructure, service interface technology, and security technology are required. Recently, technologies such as sensor networks for connecting objects, machine-to-machine (M2M), and machine-type communication (MTC) are being researched. In an IoT environment, intelligent IT services are provided that collect and analyze data generated from connected objects to create new value in human life. IoT, through the integration and combination of conventional IT technologies and various industries, is being applied to fields such as smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, healthcare, smart home appliances, and advanced medical services.

[0006] Therefore, various attempts are being made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, machine-to-machine communication, and MTC are being realized through 5G communication technologies such as beamforming, MIMO, and array antennas. As mentioned above, the application of cloud radio access networks (cloud RAN) as a big data processing technology can also be considered an example of the fusion of 5G technology and IoT technology. In general, mobile communication systems were developed to provide voice services while ensuring user activity.

[0007] Generally, mobile communication systems are developed to provide voice services while ensuring user activity. However, mobile communication systems have gradually expanded their service scope to include data services in addition to voice services, and have now developed to the point where they can provide high-speed data services. However, due to resource shortages and users' demand for even faster services, there is a need for more advanced mobile communication systems currently in service.

[0008] As mentioned above, future 5G technology will require lower latency data transmission due to the emergence of new applications such as real-time control and the tactile internet, and the required latency for 5G data is expected to drop to 1 ms. 5G aims to provide data latency that is approximately 10 times lower than before. To solve this problem, 5G is expected to propose a communication system that utilizes mini-slots with even shorter TTI periods (e.g., 0.2 ms) in addition to conventional slots (or subframes).

[0009] Rel-16 enhanced URLLC (eURLLC) discusses various techniques to provide lower latency and higher reliability. Among them, to provide lower latency, it supports the transmission of uplink control channels containing two or more HARQ-ACKs within a single slot. Terminals can ensure lower latency by being able to send HARQ-ACKs as quickly as possible in response to successful reception of downlink shared channels. [Overview of the project] [Problems that the invention aims to solve]

[0010] An object of one embodiment of the present invention is to provide a method for a terminal in a wireless communication system to repeatedly transmit a physical uplink shared channel (PUSCH) to a base station, and a terminal for the same purpose. [Means for solving the problem]

[0011] A method for a terminal to transmit a physical uplink shared channel (PUSCH) to a base station in a wireless communication system includes the steps of: receiving configuration information for transmitting a PUSCH from the base station, wherein the configuration information includes resource information related to a set of control resources used for an initial connection procedure; receiving a physical downlink control channel (PDCCH) for scheduling repeated transmissions of the PUSCH; determining one or more symbols that are invalid for the repeated transmissions of the PUSCH; and repeatedly transmitting the PUSCH with at least one symbol scheduled by the PDCCH, excluding the invalid symbol, wherein the one or more invalid symbols include symbols indicated by the resource information related to the set of control resources used for the initial connection procedure.

[0012] Furthermore, in this invention, the configuration information is indicated by the PBCH, and the control resource set has an index value of 0.

[0013] Furthermore, in the present invention, the ineffective one or more symbols further include symbols designated as semi-static downlink symbols for downlink reception in the cell where the repeated transmission of the PUSCH is performed, and symbols for receiving a synchronization signal (SS) and / or a physical broadcast channel (PBCH).

[0014] Furthermore, in the present invention, the semi-static downlink symbol and the symbol for receiving the PBCH are indicated by the configuration information.

[0015] Furthermore, in the present invention, if the terminal supports only half-duplex mode, the one or more invalid symbols further include symbols designated for receiving downlink channels and signals in a cell different from the cell in which the repeated transmission of PUSCH is performed, and / or symbols designated as semi-static downlink symbols.

[0016] Furthermore, in the present invention, the one or more invalid symbols further include gap symbols, the gap symbols being at least one symbol located after the symbol designated for downlink reception.

[0017] Furthermore, in the present invention, the subcarrier spacing of the gap symbol is a reference subcarrier spacing included in the semi-static uplink and / or downlink configuration information of the cell to which the gap symbol is applied for repeated transmission of the PUSCH.

[0018] Furthermore, in the present invention, the symbol instructed for receiving the downlink is a semi-static downlink symbol, a symbol for receiving an SSB / PBCH block, or a symbol included in the control resource set.

[0019] Furthermore, in the present invention, when the symbol on which the repeated transmission of PUSCH is performed and the symbol for transmitting the physical uplink control channel (PUCCH) overlap by at least one symbol, the PUSCH and the uplink control information (UCI) of the PUCCH are multiplexed and transmitted in the first symbol set of at least one symbol set including the at least one symbol, and the at least one symbol set is the resource on which the repeated transmission of PUSCH is performed.

[0020] Furthermore, in the present invention, the PUSCH transmitted in the first symbol set satisfies the processing time for multiplexing between the UCIs.

[0021] Furthermore, in the present invention, the PUSCH and the UCI are multiplexed only when the number of symbols for repeatedly transmitting the PUSCH in each slot exceeds one.

[0022] Also, in the present invention, a terminal is provided that includes a communication module; and a processor that controls the communication module, wherein the processor receives configuration information for PUSCH transmission from a base station, the configuration information includes resource information related to a control resource set used for an initial connection procedure, receives a physical downlink control channel (PDCCH) for scheduling the iterative transmission of the PUSCH, determines one or more symbols that are invalid for the iterative transmission of the PUSCH, and iteratively transmits the PUSCH using symbols other than the invalid symbols among at least one symbol scheduled by the PDCCH, and the one or more invalid symbols include symbols indicated by the resource information related to the control resource set used for the initial connection procedure.

Advantages of the Invention

[0023] According to the method for a terminal to iteratively transmit a PUSCH to a base station in the wireless communication system according to an embodiment of the present invention described above, by the terminal iteratively transmitting the PUSCH to the base station as quickly as possible, it is possible to achieve the target performance of a 5G wireless communication system that attempts to provide a service with low delay and high reliability.

[0024] The effects obtained from the present invention are not limited to the effects mentioned above, and other effects not mentioned will be clearly understood by those with ordinary knowledge in the technical field to which the present invention pertains from the following description.

Brief Description of the Drawings

[0025] [Figure 1] FIG. shows an example of a radio frame structure used in a wireless communication system. [Figure 2] FIG. shows an example of a downlink (DL) / uplink (UL) slot structure in a wireless communication system. [Figure 3]It is a diagram for explaining a physical channel used in a 3GPP system (e.g., NR) and a general signal transmission method using the physical channel. [Figure 4] It is a diagram showing an SS / PBCH block for initial cell access in a 3GPP NR system. [Figure 5] It is a diagram showing procedures for control information and control channel transmission in a 3GPP NR system. [Figure 6] It is a diagram showing a CORESET where PDCCH is transmitted in a 3GPP NR system. [Figure 7] It is a diagram showing a method for setting a PDCCH search space in a 3GPP NR system. [Figure 8] Figure 8 is a conceptual diagram for explaining carrier aggregation. [Figure 9] It is a diagram for explaining terminal carrier communication and multi-carrier communication. [Figure 10] It is a diagram showing an example where a cross-carrier scheduling technique is applied. [Figure 11] It is a block diagram showing the configurations of a terminal and a base station according to an embodiment of the present invention. [Figure 12] It is a flowchart showing an example for transmitting and receiving a physical uplink shared channel (PUSCH) according to an embodiment of the present invention. [Figure 13] It is a diagram showing an example when a PUSCH according to an embodiment of the present invention includes four PUSCH repetitions. [Figure 14] It is a diagram showing an example when a PUSCH according to an embodiment of the present invention includes four PUSCH repetitions. [Figure 15] It is a diagram showing an example when a PUSCH according to an embodiment of the present invention includes four PUSCH repetitions. [Figure 16]This figure shows an example where a PUSCH according to one embodiment of the present invention includes four PUSCH repetitions. [Figure 17] This figure shows an example where a PUSCH according to one embodiment of the present invention includes four PUSCH repetitions. [Figure 18] This figure shows an example where a PUSCH according to one embodiment of the present invention includes four PUSCH repetitions. [Figure 19] This figure shows an example of a slot format for repeated PUSCH transmission according to one embodiment of the present invention. [Figure 20] This figure shows an example of a slot format for repeated PUSCH transmission according to one embodiment of the present invention. [Figure 21] This figure shows an example of a slot format for repeated PUSCH transmission according to one embodiment of the present invention. [Figure 22] This figure shows an example of a slot format for repeated PUSCH transmission according to one embodiment of the present invention. [Figure 23] This figure shows yet another example of a symbol that cannot be repeatedly transmitted via PUSCH according to one embodiment of the present invention. [Figure 24] This figure shows yet another example of a symbol that cannot be repeatedly transmitted via PUSCH according to one embodiment of the present invention. [Figure 25] An example of a method for determining an invalid symbol according to one embodiment of the present invention is shown. [Figure 26] An example of a method for determining a symbol for repeated transmission of PUSCH according to one embodiment of the present invention is shown. [Figure 27] Here is yet another example of a method for determining a symbol for repeated transmission of PUSCH according to one embodiment of the present invention. [Figure 28] Here is yet another example of a method for determining a symbol for repeated transmission of PUSCH according to one embodiment of the present invention. [Figure 29]This flowchart shows an example of a method for a terminal to repeatedly transmit PUSCH according to one embodiment of the present invention. [Figure 30] This flowchart shows an example of a method for a base station to repeatedly receive PUSCH from a terminal, according to one embodiment of the present invention. [Modes for carrying out the invention]

[0026] The terminology used herein has been selected to be as widely used and general as possible, taking into account the function of the present invention; however, this may vary depending on the intentions, conventions, or emergence of new technologies of the articulate. In some cases, the applicant has arbitrarily selected certain terms, in which case their meaning will be described in the relevant section of the invention description. Therefore, it should be made clear that the terminology used herein should not be merely names of terms, but should be analyzed based on the substantive meaning of the terms and the overall content of this specification.

[0027] Throughout the specification, when one configuration is said to be “connected” to another, this includes not only cases where they are “directly connected,” but also cases where they are “electrically connected” through other intermediate components. Furthermore, when a configuration is said to “include” a particular component, this means, unless otherwise stated, that it includes other components rather than excluding them. In addition, the limitations of “greater than” or “less than” a particular critical point may be appropriately replaced by “greater than” or “less than” depending on the embodiment.

[0028] The following technologies are used in a variety of wireless connectivity systems, including CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), and SC-FDMA (single carrier frequency division multiple access). CDMA is implemented using radio technology such as UTRA (Universal Terrestrial Radio Access) and CDMA2000. TDMA is implemented using radio technology such as GSM (Global System for Mobile communications) / GPRS (General Packet Radio Service) / EDGE (Enhanced Data Rates for GSM Evolution). OFDMA is implemented using radio technology such as IEEE802.11 (Wi-Fi), IEEE802.16 (WiMAX), IEEE802-20, and E-UTRA (Evolved UTRA). UTRA is part of UMTS (Universal Mobile Telecommunication System). 3GPP LTE (Long term evolution) is part of E-UMTS (Evolved UMTS) which uses E-UTRA, and LTE-A (Advanced) is an advanced version of 3GPP LTE. 3GPP NR is a system designed separately from LTE / LTE-A, and is intended to support eMBB (enhanced Mobile Broadband), URLLC (Ultra-Reliable and Low Latency Communication), and mMTC (massive Machine Type Communication) services, which are requirements of IMT-2020. While this explanation will focus on 3GPP NR for clarity, the technical concept of this invention is not limited to this.

[0029] Unless otherwise specified herein, a base station may include a gNB (next generation node B) as defined in 3GPP NR. Also, unless otherwise specified, a terminal may include a UE (user equipment). To aid understanding the explanation below, each concept will be described in separate embodiments, although these embodiments may be used in combination with each other. In this disclosure, terminal configuration may mean configuration by the base station. Specifically, the base station may transmit channels or signals to the terminal to configure the operation of the terminal or the values ​​of parameters used in the wireless communication system.

[0030] Figure 1 shows an example of a wireless frame structure used in a wireless communication system.

[0031] Referring to Figure 1, a radio frame (or radio frame) used in a 3GPP NR system has a length of 10 ms (ΔfmaxNf / 100) * Tc). A radio frame consists of 10 subframes (SF) of equal size, where Δfmax = 480 * 10³ Hz, Nf = 4096, Tc = 1 / (Δfref * Nf,ref), Δfref = 15 * 10³ Hz, and Nf,ref = 2048. Each of the 10 subframes within a single frame is assigned a number from 0 to 9. Each subframe has a length of 1 ms and consists of one or more slots determined by the subcarrier spacing. More specifically, the subcarrier spacing usable in a 3GPP NR system is 15 * 2 μkHz, where μ is the subcarrier spacing configuration, with values ​​from 0 to 4. In other words, 15kHz, 30kHz, 60kHz, 120kHz, or 240kHz are used as subcarrier intervals. A 1ms subframe consists of 2μm slots, each with a length of 2-μms. The 2μm slots within a subframe are each assigned numbers from 0 to 2μ-1. Similarly, the slots within a radio frame are each assigned numbers from 0 to 10*2μ-1. Time resources are divided by at least one of the following: radio frame number (also called radio frame index), subframe number (also called subframe index), or slot number (or slot index).

[0032] Figure 2 shows an example of a downlink (DL) / uplink (UL) slot structure in a wireless communication system. In particular, Figure 2 shows the resource grid structure of a 3GPP NR system.

[0033] There is one resource grid per antenna port. Referring to Figure 2, a slot contains multiple OFDM symbols in the time domain and multiple resource blocks (RBs) in the frequency domain. An OFDM symbol also means a single symbol interval. Unless otherwise specified, OFDM symbols are simply referred to as symbols. Hereafter, in this specification, symbols include OFDM symbols, SC-FDMA symbols, DFTs-OFDM symbols, etc. Referring to Figure 2, the signal transmitted from each slot is represented by a resource grid consisting of Nsize, μgrid, x*NRBSC subcarriers and Nslotsymb OFDM symbols. Here, x=DL for a downlink resource grid and x=UL for an uplink resource grid. Nsize, μgrid, and x indicate the number of resource blocks (RBs) with a subcarrier spacing component μ (x is DL or UL), and Nslotsymb indicates the number of OFDM symbols in the slot. NRBSC is the number of subcarriers constituting one RB, where NRBSC=12. OFDM symbols are also known as CP-OFDM (cyclic prefix OFDM) symbols or DFT-S-OFDM (discrete Fourier transform spread OFDM) symbols, depending on the multiple access method.

[0034] The number of OFDM symbols in a single slot can vary depending on the length of the cyclic prefix (CP). For example, a normal CP may contain 14 OFDM symbols in a single slot, while an extended CP may contain 12 OFDM symbols. In specific embodiments, extended CPs are used only with a subcarrier interval of 60 kHz. For the sake of explanation, Figure 2 illustrates a case where a single slot consists of 14 OFDM symbols, but the embodiments of the present invention are applied in the same manner to slots with other numbers of OFDM symbols. Referring to Figure 2, each OFDM symbol contains N size, μgrid, and x*NRBSC subcarriers in the frequency domain. Subcarrier types are divided into data subcarriers for transmitting data, reference signal subcarriers for transmitting reference signals, and guard bands. The carrier frequency is also called the center frequency (fc).

[0035] A single RB is defined by NRBSC (e.g., 12) consecutive subcarriers in the frequency domain. Incidentally, a resource consisting of one OFDM symbol and one subcarrier is called a resource element (RE) or tone. Therefore, a single RB consists of Nslotsymb*NRBSC resource elements. Each resource element in the resource grid is uniquely defined by an index pair (k, l) in a single slot. k is an index given in the frequency domain from 0 to Nsize, μgrid, and x*NRBSC-1, and l is an index given in the time domain from 0 to Nslotsymb-1.

[0036] For a terminal to receive signals from a base station or transmit base station signals, the terminal's time / frequency synchronization must be synchronized with the base station's time / frequency synchronization. If the base station and the terminal are not synchronized, the terminal cannot determine the time and frequency parameters necessary to demodulate DL signals and transmit UL signals at the correct time.

[0037] Each symbol in a radio frame operating in TDD (time division duplex) or unpaired spectrum consists of at least one of the following: a downlink symbol (DL symbol), an uplink symbol (UL symbol), or a flexible symbol. In FDD (frequency division duplex) or paired spectrum, a radio frame operating on a downlink carrier consists of either a downlink symbol or a flexible symbol, while a radio frame operating on an uplink carrier consists of either an uplink symbol or a flexible symbol. Downlink symbols can be used for downlink transmission but not uplink transmission, and uplink symbols can be used for uplink transmission but not downlink transmission. The use of a flexible symbol in the downlink or uplink is determined by the signal.

[0038] Information regarding the type of each symbol, i.e., whether it is a downlink symbol, uplink symbol, or flexible symbol, consists of a cell-specific (or common) RRC signal. Additionally, information regarding the type of each symbol consists of a UE-specific (or dedicated) RRC signal. The base station uses the cell-specific RRC signal to indicate: i) the period of the cell-specific slot configuration; ii) the number of slots containing only downlink symbols from the beginning of the cell-specific slot configuration period; iii) the number of downlink symbols from the first symbol in the slot immediately following the downlink-only slot; iv) the number of slots containing only uplink symbols from the end of the cell-specific slot configuration period; and v) the number of uplink symbols from the last symbol in the slot immediately preceding the uplink-only slot. Here, a symbol that is neither an uplink nor a downlink symbol is a flexible symbol.

[0039] If the information regarding the symbol type consists of the per-terminal RRC signal, the base station signals whether the flexible symbol is a downlink symbol or an uplink symbol using the cell-specific RRC signal. At this time, the per-terminal RRC signal cannot change the downlink symbol or uplink symbol consisting of the cell-specific RRC signal to another symbol type. The per-terminal RRC signal signals, for each slot, the number of downlink symbols among the Nslotsymb symbols of the slot and the number of uplink symbols among the Nslotsymb symbols of the slot. At this time, the downlink symbols of the slot are continuously configured from the first symbol to the i-th symbol of the slot. Also, the uplink symbols of the slot are continuously configured from the j-th symbol to the last symbol of the slot (where i < j). In a slot, a symbol not configured as either an uplink symbol or a downlink symbol is a flexible symbol.

[0040] The type of symbol configured by the above RRC signals can be called a semi-static DL / UL configuration. In the semi-static DL / UL configuration configured by the RRC signals previously, the flexible symbol may be indicated as a downlink symbol, an uplink symbol, or a flexible symbol by the dynamic SFI (slot format information) transmitted on the physical downlink control channel (PDCCH). At this time, the downlink symbol or uplink symbol configured by the RRC signals is not changed to another symbol type. Table 1 exemplifies the dynamic SFI that the base station can indicate to the terminal.

[0041] Figure 3 is a diagram for explaining the physical channels used in a 3GPP system (e.g., NR) and a general signal transmission method using the physical channels.

[0042] When the terminal is powered on or enters a new cell, the terminal performs the initial cell discovery process (S101). Specifically, the terminal synchronizes with the base station during the initial cell discovery. To do this, the terminal receives a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) from the base station to synchronize with the base station and acquire information such as the cell index. Next, the terminal receives the physical broadcast channel from the base station and acquires broadcast information within the cell.

[0043] After completing the initial cell search, the terminal receives the physical downlink shared channel (PDSCH) via the physical downlink control channel (PDCCH) and the information carried on the PDCCH, thereby obtaining more detailed system information than that acquired through the initial cell search (S102). Here, the system information transmitted to the terminal is the cell common system information necessary for the terminal to operate correctly in the physical layer of the RRC (Radio Resource Control, RRC), and is called remaining system information or system information block (SIB) 1.

[0044] When a terminal first connects to a base station, or when there are no radio resources for signal transmission (when the terminal is in RRC_IDLE mode), the terminal can perform a random access process to the base station (steps S103 to S106). First, the terminal transmits a preamble on the physical random access channel (PRACH) (S103), and can receive a response message for the preamble from the base station on the PDCCH and the corresponding PDSCH (S104). If the terminal receives a valid random access response message, the terminal transmits data including its identifier to the base station on the physical uplink shared channel (PUSCH) indicated by the uplink grant transmitted from the base station via the PDCCH (S105). Next, the terminal waits to receive a PDCCH as an instruction from the base station for collision resolution. When the terminal successfully receives a PDCCH with its identifier (S106), the random access process ends. During the random access process, the terminal can obtain terminal-specific system information necessary for the terminal to function correctly at the physical layer of the RRC layer. Once the terminal obtains terminal-specific system information at the RRC layer, the terminal enters RRC_CONNECTED mode.

[0045] The RRC layer is used for message generation and management for control between terminals and the Radio Access Network (RAN). Furthermore, base stations and terminals can use the RRC layer to broadcast cell system information necessary for all terminals within a cell, manage the transmission of paging messages, manage mobility and handover, report and control terminal measurements, and manage terminal capabilities and storage. Generally, the update of signals transmitted in the RRC layer (hereinafter referred to as RRC signals) is longer than the transmission time interval (TTI) in the physical layer, so RRC settings can be maintained without change over long periods.

[0046] After the above procedure, the terminal receives PDCCH / PDSCH S107 and transmits the physical uplink sharing channel (PUSCH) / physical uplink control channel (PUCCH) S108 as a general uplink / downlink signal transmission procedure. In particular, the terminal receives downlink control information (DCI) via PDCCH. DCI includes control information such as resource allocation information for the terminal. Also, the format of DCI may differ depending on its intended use. Uplink control information (UCI) that the terminal transmits to the base station via the uplink includes downlink / uplink ACK / NACK signals, CQI (channel quality indicator), PMI (precoding matrix index), RI (rank indicator), etc. Here, CQI, PMI, and RI are included in CSI (channel state information). In the case of a 3GPP NR system, the terminal transmits the above-mentioned HARQ-ACK and control information such as CSI via PUSCH and / or PUCCH.

[0047] Figure 4 shows the SS / PBCH block for initial cell access in a 3GPP NR system.

[0048] When a terminal is powered on or attempts to access a new cell, it acquires time and frequency synchronization with the cell and performs an initial cell discovery process. During the cell discovery process, the terminal detects the cell's physical cell identity (NcellID). To do this, the terminal receives synchronization signals from the base station, such as the primary synchronization signal (PSS) and secondary synchronization signal (SSS), to synchronize with the base station. At this time, the terminal obtains information such as the cell identifier (identity, ID).

[0049] Refer to Figure 4(a) for a more detailed explanation of the synchronization signal (SS). The synchronization signal is divided into PSS and SSS. PSS is used to obtain time-domain synchronization and / or frequency-domain synchronization, such as OFDM symbol synchronization and slot synchronization. SSS is used to obtain frame synchronization and cell group ID. Referring to Figure 4(a) and Table 1, an SS / PBCH block consists of 20 RBs (=240 subcarriers) consecutively on the frequency axis and 4 OFDM symbols consecutively on the time axis. In this case, within the SS / PBCH block, the PSS is transmitted via the first OFDM symbol and the SSS via the second subcarrier (56-18) for the third OFDM symbol. Here, the lowest subcarrier index of the SS / PBCH block is assigned starting from 0. In the first OFDM symbol on which the PSS is transmitted, the base station does not transmit signals via the remaining subcarriers, i.e., subcarriers 0-55 and 183-239. Furthermore, in the third OFDM symbol on which SSS is transmitted, the base station does not transmit signals via subcarriers 48-55 and 183-19. In the SS / PBCH block, the base station transmits PBCH (physical broadcast channel) via the remaining REs excluding the aforementioned signals.

[0050] [Table 1]

[0051] The SS generates a total of 1008 unique physical layer cell IDs through combinations of three PSSs and SSSs. More specifically, each physical layer cell ID is part of only one physical layer cell identifier group, and each group is grouped into 336 physical layer cell identifier groups, each containing three unique identifiers. Therefore, the physical layer cell ID NcellID = 3N(1)ID + N(2)ID is uniquely defined by an index N(1)ID ranging from 0 to 335 that represents a physical layer cell identifier group, and an index N(2)ID ranging from 0 to 2 that represents a physical layer identifier within the physical layer cell identifier group. The terminal detects the PSS and identifies one of the three unique physical layer identifiers. The terminal also detects the SSS and identifies one of the 336 physical layer cell IDs associated with the physical layer identifier. In this case, the PSS sequence dPSS(n) is as shown in Equation 1 below.

[0052] dPSS(n) = 1 - 2x(m) m=(n+43N(2)ID) mod 127 0 ≤ n < 127

[0053] Here, x(i+7)=(x(i+4)+x(i)) mod 2,

[0054] [x(6)x(5)x(4)x(3)x(2)x(1)x(0)]=[1110110] is given.

[0055] Furthermore, the SSS sequence dSSS(n) is as follows:

[0056] dSSS(n)=[1-2x0((n+m0) mod 127][1-2x1((n+m1) mod 127] m0=15 floor(N(1)ID / 112)+5N(2)ID m1 = N(1)ID mod 112 0 ≤ n < 127

[0057] Here, x0(i+7)=(x0(i+4)+x0(i))mod 2 x1(i+7)=(x1(i+1)+x1(i))mod 2,

[0058] [x0(6)x0(5)x0(4)x0(3)x0(2)x0(1) 0(0)]=[0000001] and [x1(6)x1(5)x1(4)x1(3)x1(2)x1(1)x1(0)]=[0000001] are given.

[0059] A 10ms long wireless frame is divided into two 5ms long half-frames. Refer to Figure 4(b) to describe the slot in which an SS / PBCH block is transmitted within each half-frame. The slot in which an SS / PBCH block is transmitted is one of cases A, B, C, D, or E. In case A, the subcarrier interval is 15kHz, and the start of the SS / PBCH block is at the {2, 8} + 14*n symbol. In this case, n=0, 1 for carrier frequencies below 3GHz. Also, n=0, 1, 2, 3 for carrier frequencies above 3GHz and below 6GHz. In case B, the subcarrier interval is 30kHz, and the start of the SS / PBCH block is at the {4, 8, 16, 20} + 28*n symbol. In this case, n=0 for carrier frequencies below 3GHz. Also, n=0, 1 for carrier frequencies above 3GHz and below 6GHz. In Case C, the subcarrier spacing is 30 kHz, and the SS / PBCH block starts at the {2nd, 8th} + 14*nth symbol. In this case, for carrier frequencies below 3 GHz, n=0, 1. Also, for carrier frequencies above 3 GHz and below 6 GHz, n=0, 1, 2, 3. In Case D, the subcarrier spacing is 120 kHz, and the SS / PBCH block starts at the {4th, 8th, 16th, 20th} + 28*nth symbol. In this case, for carrier frequencies above 6 GHz, n=0, 1, 2, 3, 5, 6, 7, 8, 10, 11, 12, 13, 15, 16, 17, 18. In Case E, the subcarrier spacing is 240 kHz, and the SS / PBCH block starts at the {8th, 12th, 16th, 20th, 32nd, 36th, 40th, 44th} + 56*nth symbol. In this case, at carrier frequencies of 6 GHz or higher, n = 0, 1, 2, 3, 5, 6, 7, 8.

[0060] Figure 5 shows the procedure for transmitting control information and control channels in a 3GPP NR system. Referring to Figure 5(a), the base station adds a CRC (cyclic redundancy check) masked (e.g., by XOR operation) with an RNTI (radio network temporary identifier) ​​to the control information (e.g., DCI) S202. The base station scrambles the CRC with an RNTI value determined according to the purpose / target of each piece of control information. A common RNTI used by one or more terminals includes at least one of the following: SI-RNTI (system information RNTI), P-RNTI (paging RNTI), RA-RNTI (random access RNTI), and TPC-RNTI (transmit power control RNTI). Furthermore, the terminal-specific RNTI includes at least one of the following: C-RNTI (cell temporary RNTI), CS-RNTI, or MCS-C-RNTI. Next, after the base station performs channel encoding (e.g., polar coding) in S204, it performs rate-matching in S206 to match the amount of resources used for PDCCH transmission. Next, the base station multiplexes the DCIs (data elements) based on the CCE (control channel element)-based PDCCH structure in S208. The base station also applies additional processes S210 to the multiplexed DCIs (data elements), such as scrambling, modulation (e.g., QPSK), and interleaving, before mapping them to the resources to be transmitted. A CCE is the basic resource unit for PDCCH, and one CCE consists of multiple (e.g., 6) REGs (resource element groups). One REG consists of multiple (e.g., 12) REs. The number of CCEs used for one PDCCH is defined as the aggregation level. The 3GPP NR system uses 1, 2, 4, 8, or 16 integrated levels.Figure 5(b) is a diagram relating to the CCE integration level and PDCCH multiplexing, showing the types of CCE integration levels used for a single PDCCH and the CCEs transmitted in the control domain as a result.

[0061] Figure 6 shows the CORESET to which PDCCH is transmitted in a 3GPP NR system.

[0062] A CORESET is a time-frequency resource on which PDCCH, a control signal for a terminal, is transmitted. Furthermore, the search space, described later, is mapped to a single CORESET. Therefore, instead of monitoring the entire frequency band to receive PDCCH, the terminal monitors the CORESET and the designated time-frequency domain to decode the PDCCH mapped to the CORESET. A base station configures one or more CORESETs for each cell in the terminal. A CORESET consists of up to three consecutive symbols on the time axis. A CORESET also consists of six consecutive PRB units on the frequency axis. In the embodiment shown in Figure 5, CORESET#1 consists of consecutive PRBs, while CORESET#2 and CORESET#3 consist of discontinuous PRBs. A CORESET can be located at any symbol within a slot. For example, in the embodiment shown in Figure 5, CORESET#1 starts at the first symbol of the slot, CORESET#2 starts at the fifth symbol of the slot, and CORESET#9 starts at the ninth symbol of the slot.

[0063] Figure 7 shows how to configure the PDCCH search space in a 3GPP NR system.

[0064] To transmit a PDCCH to a terminal, each CORESET has at least one search space. In embodiments of the present invention, the search space is a collection of all time-frequency resources (hereinafter referred to as PDCCH candidates) from which the terminal's PDCCH is transmitted. The search space includes a common search space that all 3GPP NR terminals should search in common, and a terminal-specific or UE-specific search space that a specific terminal should search. In the common search space, all terminals in a cell belonging to the same base station monitor the PDCCH that they are set to search in common. The terminal-specific search spaces are configured terminal-specific to monitor the PDCCH assigned to each terminal at different locations in the search space depending on the terminal. In the case of terminal-specific search spaces, the search spaces between terminals may partially overlap due to the limited control area to which the PDCCH is assigned. Monitoring a PDCCH includes blind decoding of PDCCH candidates in the search space. If blind decoding is successful, it is expressed as the PDCCH being (successfully) detected / received. If blind decoding fails, it is expressed as the PDCCH not being detected / received, or not being successfully detected / received.

[0065] For the sake of explanation, a PDCCH scrambled with a group common (GC) RNTI already known by one or more terminals, in order to transmit downlink control information to one or more terminals, is referred to as a group common (GC) PDCCH or common PDCCH. Furthermore, a PDCCH scrambled with a terminal-specific RNTI already known by a specific terminal, in order to transmit uplink scheduling information or downlink scheduling information to a specific terminal, is referred to as a terminal-specific PDCCH. The common PDCCH is included in the common search space, and the terminal-specific PDCCH is included in either the common search space or the terminal-specific PDCCH.

[0066] The base station informs each terminal or group of terminals via the PDCCH about resource allocation information for the transmission channels PCH (paging channel) and DL-SCH (downlink-shared channel) (i.e., DL Grant), or information about UL-SCH resource allocation and HARQ (hybrid automatic repeat request) (i.e., UL Grant). The base station transmits PCH transmission blocks and DL-SCH transmission blocks via the PDSCH. The base station transmits data excluding specific control information or specific service data via the PDSCH. The terminal also receives data excluding specific control information or specific service data via the PDSCH.

[0067] The base station transmits a PDCCH containing information about which terminals (one or more terminals) the PDSCH data will be sent to and how those terminals should receive and decode the PDSCH data. For example, suppose a DCI transmitted via a particular PDCCH is CRC masked with an RNTI named "A", and that DCI indicates that the PDSCH is assigned to a radio resource (e.g., frequency location) named "B", and indicates transmission format information (e.g., transmission block size, modulation scheme, coding information, etc.) named "C". Terminals monitor the PDCCH using their own RNTI information. In this case, if a terminal blind-decodes the PDCCH using the "A" RNTI, that terminal will receive the PDCCH and, through the information of the received PDCCH, receive the PDSCH indicated by "B" and "C".

[0068] Table 2 shows one example of PUCCH used in a wireless communication system.

[0069] [Table 2]

[0070] PUCCH is used to transmit the following Uplink Control Information (UCI):

[0071] -SR (Scheduling Request): This is information used to request uplink UL-SCH resources.

[0072] -HARQ-ACK: A response to a PDCCH (indicating a DL SPS release) and / or to an uplink transmission block (TB) on a PDSCH. HARQ-ACK indicates whether information transmitted via the PDCCH or PDSCH has been received. HARQ-ACK responses include positive ACK (simply ACK), negative ACK (hereinafter NACK), DTX (Discontinuous Transmission), or NACK / DTX. Here, the term HARQ-ACK is used interchangeably with HARQ-ACK / NACK and ACK / NACK. Generally, ACK is represented by a bit value of 1 and NACK is represented by a bit value of 0.

[0073] -CSI: This is feedback information for the downlink channel. It is generated by the terminal based on the CSI-RS (Reference Signal) transmitted by the base station. MIMO (multiple input multiple output) related feedback information includes RI and PMI. CSI is divided into CSI Part 1 and CSI Part 2 depending on the information it indicates.

[0074] The 3GPP NR system uses five PUCCH formats to support diverse service scenarios, diverse channel environments, and frame structures.

[0075] PUCCH format 0 is a format for transmitting 1-bit or 2-bit HARQ-ACK information or SR. PUCCH format 0 is transmitted via one or two OFDM symbols on the time axis and one RB on the frequency axis. If PUCCH format 0 is transmitted with two OFDM symbols, the same sequence is transmitted for each symbol with different RBs. Through this, the terminal obtains a frequency diversity gain. More specifically, the terminal determines the cyclic shift value mcs according to the Mbit bit UCI (Mbit=1 or 2), and maps a sequence obtained by cyclic shifting a base sequence of length 12 by the determined value mcs to 12 REs (Res) consisting of one OFDM symbol and one PRB, and transmits it. If the number of cyclic shifts available to the terminal is 12 and Mbit=1, then 1-bit UCI0 and 1 are represented by sequences corresponding to two cyclic shifts with a cyclic shift value difference of 6. Furthermore, if Mbit=2, the 2-bit UCI00, 01, 11, and 10 represent a sequence of four cyclic shifts where the difference in cyclic shift values ​​is 3.

[0076] PUCCH format 1 transmits 1-bit or 2-bit HARQ-ACK information or SR. PUCCH format 1 is transmitted via a continuous sequence of OFDM symbols on the time axis and one PRB on the frequency axis. Here, the number of OFDM symbols occupied by PUCCH format 1 is one of 4 to 14. More specifically, a UCI with Mbit=1 is modulated with BPSK. The terminal modulates a UCI with Mbit=2 with QPSK (quadrature phase shift keying). A signal is obtained by multiplying the modulated complex valued symbol d(0) by a sequence of length 12. The terminal spreads the obtained signal with a time-axis OCC (orthogonal cover code) to the even-numbered OFDM symbols assigned to PUCCH format 1 and transmits it. The maximum number of different terminals multiplexed on the same RB in PUCCH format 1 is determined by the length of the OCC used. For odd-numbered OFDM symbols in PUCCH format 1, the DMRS (demodulation reference signal) is spread across the OCC and mapped to them.

[0077] PUCCH format 2 transmits UCI exceeding 2 bits. PUCCH format 2 is transmitted via one or two OFDM symbols on the time axis and one or more RBs on the frequency axis. If PUCCH format 2 is transmitted via two OFDM symbols, the same sequence is transmitted via the two OFDM symbols with different RBs. Through this, the terminal gains frequency diversity gain. More specifically, an Mbit bit UCI (Mbit > 2) is bit-level scrambled and QPSK modulated and mapped to the RBs of one or two OFDM symbols, where the number of RBs is one between 1 and 16.

[0078] PUCCH format 3 or PUCCH format 4 transmits UCI exceeding 2 bits. PUCCH format 3 or PUCCH format 4 is transmitted via continuous OFDM symbols on the time axis and one PRB on the frequency axis. The number of OFDM symbols occupied by PUCCH format 3 or PUCCH format 4 is one of 4 to 14. Specifically, the terminal modulates an Mbit bit UCI (Mbit>2) with π / 2-BPSK (Binary Phase Shift Keying) or QPSK to generate complex number symbols d(0) to d(Msymb-1). Here, with π / 2-BPSK, Msymb = Mbit, and with QPSK, Msymb = Mbit / 2. The terminal does not apply block-unit spreading to PUCCH format 3. However, the terminal may apply block-unit spreading to one RB (i.e., 12 subcarriers) using a PreDFT-OCC of length -12 so that the PUCCH format 4 has two or four multiplexing capacities. The terminal transmits the spread signal using transmit precoding (or DFT-precoding) and maps it to each RE to transmit the spread signal.

[0079] In this case, the number of RBs occupied by PUCCH format 2, PUCCH format 3, or PUCCH format 4 is determined according to the length of the UCI transmitted by the terminal and the maximum code rate. If the terminal uses PUCCH format 2, it transmits both HARQ-ACK information and CSI information via PUCCH. If the number of RBs that the terminal can transmit is greater than the maximum number of RBs that PUCCH format 2, PUCCH format 3, or PUCCH format 4 can use, the terminal will not transmit some of the UCI information according to the priority of the UCI information, and will transmit only the remaining UCI information.

[0080] PUCCH format 1, PUCCH format 3, or PUCCH format 4 is configured via an RRC signal to instruct frequency hopping within a slot. When frequency hopping is configured, the index of the RB to be frequency-hopped is determined by the RRC signal. If PUCCH format 1, PUCCH format 3, or PUCCH format 4 is transmitted over N OFDM symbols in the time axis, the first hop will have floor(N / 2) OFDM symbols, the second hop will have ceil(N / 2) OFDM symbols.

[0081] PUCCH format 1, PUCCH format 3, or PUCCH format 4 are configured to be repeatedly transmitted to multiple slots. In this case, the number K of slots to which the PUCCH is repeatedly transmitted is determined by the RRC signal. The repeatedly transmitted PUCCH should start from the same OFDM symbol in the same position within each slot and have the same length. If any of the OFDM symbols in a slot to which the terminal is to transmit the PUCCH is indicated as a DL symbol by the RRC signal, the terminal does not transmit the PUCCH from that slot but postpones transmission to the next slot.

[0082] On the other hand, in the 3GPP NR system, terminals transmit and receive using a bandwidth smaller than or equal to the carrier (or cell) bandwidth. For this purpose, terminals are configured with a bandwidth part (BWP) consisting of a continuous portion of the carrier bandwidth. Terminals operating according to TDD or in the ampered spectrum have up to four DL / UL BWP pairs per carrier (or cell). The terminal also activates one DL / UL BWP pair. Terminals operating according to FDD or in the paired spectrum have up to four DL BWPs configured on the downlink carrier (or cell) and up to four UL BWPs configured on the uplink carrier (or cell). The terminal activates one DL BWP and one UL BWP for each carrier (or cell). The terminal does not have to receive or transmit from time-frequency resources other than the activated BWPs. The activated BWPs are called active BWPs.

[0083] The base station refers to the activated BWP among the configured BWPs of a terminal as the DCI. The BWP indicated by the DCI is activated, and the other configured BWPs are deactivated. In a carrier (or cell) operating in TDD mode, the base station includes a BPI (bandwidth part indicator) in the DCI that schedules the PDSCH or PUSCH to indicate which BWP to activate in order to change the terminal's DL / UL BWP pair. The terminal receives the DCI that schedules the PDSCH or PUSCH and identifies the DL / UL BWP pair to activate based on the BPI. In the case of a downlink carrier (or cell) operating in FDD mode, the base station includes a BPI informing the DCI that schedules the PDSCH which BWP to activate in order to change the terminal's DL BWP. In the case of an uplink carrier (or cell) operating in FDD mode, the base station includes a BPI informing the DCI that schedules the PUSCH which BWP to activate in order to change the terminal's UL BWP.

[0084] Figure 8 is a conceptual diagram illustrating career integration.

[0085] Carrier aggregation refers to a method used by wireless communication systems to utilize a wider frequency band by having terminals use multiple frequency blocks, or (logical) cells, consisting of uplink resources (or component carriers) and / or downlink resources (or component carriers), within a single larger logical frequency band. For convenience of explanation, the term "component carrier" will be used consistently below.

[0086] Referring to Figure 8, as an example of a 3GPP NR system, the overall system bandwidth includes up to 16 component carriers, each component carrier having a bandwidth of up to 400 MHz. Each component carrier includes one or more physically consecutive subcarriers. Although Figure 8 shows each component carrier having the same bandwidth, this is merely illustrative, and each component carrier may have different bandwidths. Also, although each component carrier is shown as being adjacent to each other on the frequency axis, the diagram is a logical representation, and each component carrier may be physically adjacent to or far from each other.

[0087] Each component carrier uses a different center frequency. Furthermore, physically adjacent component carriers share a single common center frequency. In the embodiment shown in Figure 8, assuming all component carriers are physically adjacent, center frequency A is used for all component carriers. If we assume that the component carriers are not physically adjacent, then center frequencies A and B are used for each component carrier.

[0088] When the overall system bandwidth is expanded through carrier aggregation, the frequency band used for communication with each terminal is defined on a component carrier basis. Terminal A uses the overall system bandwidth of 100 MHz and communicates using all five component carriers. Terminals B1 to B5 use only a 20 MHz bandwidth and communicate using one component carrier each. Terminals C1 and C2 use only a 40 MHz bandwidth and communicate using two component carriers each. The two component carriers may be logically / physically adjacent or not. In the embodiment shown in Figure 8, terminal C1 uses two non-adjacent component carriers, and terminal C2 uses two adjacent component carriers.

[0089] Figure 9 is a diagram illustrating terminal carrier communication and multiple carrier communication. Specifically, Figure 9(a) shows the subframe structure of a single carrier, and Figure 9(b) shows the subframe structure of a multiple carrier.

[0090] Referring to Figure 9(a), a typical wireless communication system, in FDD mode, transmits or receives data via one DL band and its corresponding UL band. In other specific embodiments, in TDD mode, the wireless communication system divides the wireless frame into uplink time units and downlink time units in the time domain, and transmits or receives data via the uplink / downlink time units. Referring to Figure 9(b), three 20MHz component carriers (CCs) are aggregated in both the UL and DL bands, supporting a 60MHz bandwidth. Each CC is either adjacent or non-adjacent to the others in the frequency domain. For convenience, Figure 9(b) shows a symmetrical case where the bandwidths of the UL CCs and DL CCs are the same, but the bandwidths of each CC may be determined independently. Asymmetric carrier aggregations with different numbers of UL CCs and DL CCs are also possible. A DL / UL CC assigned / configured to a specific terminal via RRC is referred to as the serving DL / UL CC of that terminal.

[0091] A base station communicates with a terminal by activating some or all of the terminal's serving CCs, or by deactivating some of the CCs. The base station may change which CCs are activated / deactivated, or change the number of CCs that are activated / deactivated. Once a base station assigns available CCs to a terminal, either cell-specific or terminal-specific, at least one of the initially assigned CCs does not need to be deactivated unless the CC assignments for the terminal are completely reconfigured or the terminal is handed over. The CC that is not deactivated by the terminal is called the primary CC (PCC) or PCell (primary cell), and the CCs that the base station can freely activate / deactivate are called secondary CCs (SCC) or SCell (secondary cell).

[0092] On the other hand, 3GPP NR uses the concept of a cell to manage radio resources. A cell is defined as a combination of downlink and uplink resources, i.e., a combination of DL CC and UL CC. A cell consists of DL resources alone, or a combination of DL and UL resources. If carrier aggregation is supported, the linkage between the carrier frequency of the DL resource (or DL ​​CC) and the carrier frequency of the UL resource (or UL CC) is indicated by system information. Carrier frequency refers to the center frequency of each cell or CC. A cell corresponding to a PCC is called a PCell, and a cell corresponding to an SCC is called a SCell. In the downlink, the carrier corresponding to a PCell is a DL PCC, and in the uplink, the carrier corresponding to a PCell is a UL PCC. Similarly, in the downlink, the carrier corresponding to a SCell is a DL SCC, and in the uplink, the carrier corresponding to a SCell is a UL SCC. Depending on the terminal capacity, a serving cell consists of one PCell and zero or more SCells. If the RRC_CONNECTED state exists but carrier aggregation is not configured, or if the UE does not support carrier aggregation, there will be only one serving cell consisting solely of PCells.

[0093] As described above, the term "cell" used in carrier aggregation is distinct from the term "cell" which refers to a specific geographical area where communication services are provided by a single base station or antenna group. However, in order to distinguish between a cell referring to a specific geographical area and a cell in carrier aggregation, in this invention, a cell in carrier aggregation is referred to as CC, and a cell referring to a geographical area is referred to as cell.

[0094] Figure 10 shows an example where the cross-carrier scheduling technique is applied. Once cross-carrier scheduling is set up, the control channel transmitted via the first CC uses the carrier indicator field (CIF) to schedule the data channel transmitted via the first or second CC. The CIF is contained within the DCI. In other words, a scheduling cell is set up, and DL grants / UL grants transmitted from the PDCCH area of ​​the scheduling cell schedule the PDSCH / PUSCH of the scheduled cell. That is, the PDCCH area of ​​the scheduling cell is a search area for multiple component carriers. A PCell is essentially a scheduling cell, and a particular SCell is designated as a scheduling cell by a higher hierarchy.

[0095] In the embodiment shown in Figure 10, we assume that three DL CCs are merged. Here, DL component carrier #0 is assumed to be a DL PCC (or PCell), and DL component carriers #1 and #2 are assumed to be DL SCCs (or SCells). We also assume that the DL PCC is configured as a PDCCH monitoring CC. If cross-carrier scheduling is not configured by terminal-specific (or terminal-group-specific, or cell-specific) higher-level signaling, the CIF will be disabled, and each DL CC will only send PDCCHs that schedule their own PDSCH without a CIF according to the NR PDCCH rule (non-cross-carrier scheduling, self-carrier scheduling). In contrast, if cross-carrier scheduling is configured through terminal-specific (or terminal-group-specific, or cell-specific) higher-level signaling, the CIF becomes ensable, and a specific CC (e.g., DL PCC) uses the CIF to transmit not only PDCCHs that schedule DL CC A's PDSCH, but also PDCCHs that schedule other CCs' PDSCHs (cross-carrier scheduling). In contrast, other DL CCs do not transmit PDCCHs. Therefore, depending on whether cross-carrier scheduling is configured for the terminal, the terminal either monitors PDCCHs without the CIF to receive self-carrier scheduled PDSCHs, or monitors PDCCHs with the CIF to receive cross-carrier scheduled PDSCHs.

[0096] On the other hand, Figures 9 and 10 illustrate the subframe structure of a 3GPP LTE-A system, and the same or similar configurations are applicable to a 3GPP NR system. However, in a 3GPP NR system, the subframes in Figures 9 and 10 are switched to slots.

[0097] Figure 11 is a block diagram showing the configuration of a terminal and a base station according to one embodiment of the present invention. In one embodiment of the present invention, the terminal is embodied in various types of wireless communication devices or computing devices that ensure portability and mobility. The terminal is referred to as UE, STA (Station), MS (Mobile Subscriber), etc. In the embodiment of the present invention, the base station controls and manages cells (e.g., macrocells, femtocells, picocells, etc.) in the service area and performs functions such as signal transmission, channel assignment, channel monitoring, self-diagnosis, and relaying. The base station is referred to as gNB (next Generation NodeB) or AP (Access Point), etc.

[0098] As shown in the figure, a terminal 100 according to one embodiment of the present invention includes a processor 110, a communication module 120, a memory 130, a user interface unit 140, and a display unit 150.

[0099] First, the processor 110 executes various instructions or programs to process data inside the terminal 100. The processor 110 also controls the overall operation of the terminal 100, including each unit, and controls the transmission and reception of data between units. Here, the processor 110 is configured to perform the operations described in the embodiment of the present invention. For example, the processor 110 may receive slot configuration information, determine the slot configuration based on that information, and perform communication according to the determined slot configuration.

[0100] Next, the communication module 120 is an integrated module that performs wireless communication using a wireless communication network and wireless LAN access using a wireless LAN. To this end, the communication module 120 incorporates multiple network interface cards (NICs), such as cellular communication interface cards 121 and 122 and an unlicensed band communication interface card 123, either internally or externally. In the drawing, the communication module 120 is shown as an integrated module, but each network interface card may be arranged independently depending on the circuit configuration or application, contrary to the drawing.

[0101] The cellular communication interface card 121 transmits and receives radio signals to and from at least one of the base station 200, an external device, and a server via a mobile communication network, and provides cellular communication services in a first frequency band based on instructions from the processor 110. According to one embodiment, the cellular communication interface card 121 includes at least one NIC module that utilizes a frequency band of less than 6 GHz. The at least one NIC module of the cellular communication interface card 121 independently performs cellular communication with at least one of the base station 200, an external device, and a server, depending on the cellular communication standard or protocol of the sub-6 GHz frequency band supported by the NIC module.

[0102] The cellular communication interface card 122 uses a mobile communication network to send and receive radio signals with at least one of the base station 200, an external device, or a server, and provides cellular communication services in the second frequency band based on instructions from the processor 110. According to one embodiment, the cellular communication interface card 122 includes at least one NIC module that utilizes a frequency band of 6 GHz or higher. At least one NIC module of the cellular communication interface card 122 independently performs cellular communication with at least one of the base station 200, an external device, or a server, according to the cellular communication standard or protocol of the 6 GHz or higher frequency band supported by the NIC module.

[0103] The unlicensed band communication interface card 123 transmits and receives radio signals to and from at least one of the base station 200, an external device, or a server via the third frequency band, which is an unlicensed band, and provides communication services in the unlicensed band based on instructions from the processor 110. The unlicensed band communication interface card 123 includes at least one NIC module that utilizes the unlicensed band. For example, the unlicensed band may be a 2.4 GHz or 52.6 GHz band. At least one NIC module of the unlicensed band communication interface card 123 independently or dependently performs cellular communication with at least one of the base station 200, an external device, or a server, depending on the unlicensed band communication standard or protocol of the frequency band supported by the NIC module.

[0104] Next, the memory 130 stores control programs used by the terminal 100 and various data associated with them. Such control programs include predetermined programs necessary for the terminal 100 to communicate wirelessly with at least one of the following: a base station 200, an external device, or a server.

[0105] Next, the user interface 140 includes various forms of input / output means provided in the terminal 100. In other words, the user interface unit 140 receives user input using various input means, and the processor 110 controls the terminal 100 based on the received user input. The user interface 140 also outputs based on instructions from the processor 110 using various output means.

[0106] Next, the display unit 150 outputs various images to the display screen. The display unit 150 outputs various display objects, such as content generated by the processor 110 or user interfaces based on control instructions from the processor 110.

[0107] Furthermore, the base station 200 according to the embodiment of the present invention includes a processor 210, a communication module 220, and a memory 230.

[0108] First, the processor 210 executes various instructions or programs to process data within the base station 200. The processor 210 also controls the overall operation of the base station 200, including each unit, and controls the transmission and reception of data between units. Here, the processor 210 is configured to perform the operations described in the embodiment of the present invention. For example, the processor 210 may signal slot configuration information and perform communication according to the signaled slot configuration.

[0109] Next, the communication module 220 is an integrated module that performs wireless communication using a wireless communication network and wireless LAN access using a wireless LAN. To this end, the communication module 220 incorporates multiple network interface cards, such as cellular communication interface cards 221 and 222, and an unlicensed band communication interface card 223, either internally or externally. In the drawings, the communication module 220 is shown as an integrated module, but each network interface card may be arranged independently depending on the circuit configuration or application, contrary to the drawings.

[0110] The cellular communication interface card 221 transmits and receives wireless signals to and from at least one of the terminal 100, external devices, and servers described above using a mobile communication network, and provides cellular communication services in the first frequency band based on instructions from the processor 210. According to one embodiment, the cellular communication interface card 221 includes at least one NIC module that utilizes a frequency band of less than 6 GHz. At least one NIC module of the cellular communication interface card 221 independently performs cellular communication with at least one of the terminal 100, external devices, and servers, depending on the cellular communication standard or protocol of the frequency band of less than 6 GHz supported by the NIC module.

[0111] The cellular communication interface card 222 transmits and receives wireless signals to and from at least one of the terminal 100, an external device, and a server using a mobile communication network, and provides cellular communication services in a second frequency band based on instructions from the processor 210. According to one embodiment, the cellular communication interface card 222 includes at least one NIC module that utilizes a frequency band of 6 GHz or higher. At least one NIC module of the cellular communication interface card 222 independently performs cellular communication with at least one of the terminal 100, an external device, and a server, according to the cellular communication standard or protocol of the 6 GHz or higher frequency band supported by the NIC module.

[0112] The unlicensed band communication interface card 223 uses the third frequency band, which is an unlicensed band, to send and receive wireless signals with at least one of the terminal 100, an external device, or a server, and provides communication services in the unlicensed band based on instructions from the processor 210. The unlicensed band communication interface card 223 includes at least one NIC module that utilizes the unlicensed band. For example, the unlicensed band may be the 2.4GHz or 52.6GHz band. At least one NIC module of the unlicensed band communication interface card 223 independently or dependently performs cellular communication with at least one of the terminal 100, an external device, or a server, depending on the unlicensed band communication standard or protocol of the frequency band supported by the NIC module.

[0113] The terminal 100 and base station 200 shown in Figure 11 are block diagrams according to one embodiment of the present invention, and the separately shown blocks represent logically distinguished elements of the device. Therefore, the above-mentioned elements of the device are mounted on one or more chips depending on the device design. Furthermore, some components of the terminal 100, such as the user interface unit 150 and the display unit 150, may be selectively provided in the terminal 100. In addition, the user interface 140 and the display unit 150 may be additionally provided in the base station 200 as needed.

[0114] In an NR radio communication system, a terminal transmits a codebook containing hybrid automatic repeat request (HARQ)-ACK information to signal the success or failure of receiving a downlink signal or channel. A HARQ-ACK codebook contains one or more bits indicating the success or failure of receiving a downlink channel or signal. Here, the downlink channel includes at least one of the following: a physical downlink shared channel (PDSCH), a semi-persistence scheduling (SPS) PDSCH, and a PDCCH that releases an SPS PDSCH. HARQ-ACK codebooks are classified into semi-static HARQ-ACK codebooks (or type 1 codebooks) and dynamic HARQ-ACK codebooks (or type 2 coding). The base station configures one of the two HARQ-ACK codebooks on the terminal. The terminal uses the HARQ-ACK codebook configured on it.

[0115] When a semi-static HARQ-ACK codebook is used, the base station uses the RRC signal to set the number of bits in the HARQ-ACK codebook and the information that determines whether each bit of the HARQ-ACK codebook is successfully received for which downlink signal or channel. Therefore, the base station does not need to signal the terminal with the information necessary for transmitting the HARQ-ACK codebook each time it is needed.

[0116] When a dynamic HARQ-ACK codebook is used, the base station signals the information necessary to generate the HARQ-ACK codebook via the PDCCH (or DCI). Specifically, the base station signals the information necessary to generate the HARQ-ACK codebook via the Downlink Assignment Index (DAI) field of the PDCCH (or DCI). In a specific example, the DAI indicates the number of bits in the HARQ-ACK codebook and information about which channel or signal the HARQ-ACK codebook indicates whether it was successfully received or not. The terminal receives the DAI field via the PDCCH (or DCI) that schedules the PDSCH. The value of the DAI field is divided into counter-DAI and total-DAI. The total DAI indicates the number of downlink signals or channels for which the HARQ-ACK codebook indicates whether it was successfully received or not up to the current monitoring opportunity (MO). The counter-DAI indicates the bits in the HARQ-ACK codebook that indicate the success or failure of a downlink signal or channel, which is indicated via the HARQ-ACK codebook up to the current cell at the time of current monitoring. The PDCCH (or DCI) that schedules the PDSCH includes the value of the counter-DAI corresponding to the scheduled PDSCH. The PDCCH (or DCI) that schedules the PDSCH also includes the value of the total-DAI corresponding to the scheduled PDSCH. The terminal determines the number of bits in the dynamic HARQ-ACK codebook based on the information signaled by the PDCCH (or DCI). More specifically, the terminal determines the number of bits in the dynamic HARQ-ACK codebook based on the DAI of the PDCCH (or DCI).

[0117] Figure 12 is a flowchart showing an example of sending and receiving a physical uplink shared channel (PUSCH) according to one embodiment of the present invention.

[0118] Referring to Figure 12, the terminal (UE) receives RRC Configuration Information from the base station (Base Station), which includes information for receiving Downlink Control Information (DCI) (S12010).

[0119] For example, RRC configuration information may include information about a control resource set (CORESET) and a search space for a terminal to detect a PDCCH containing downlink control information. In this case, the information about the control resource set may include at least one of the identifier (ID) of the control resource set from which the terminal can detect a PDCCH containing DCI, control channel element (CCE) configuration information, and the duration of the control resource set or frequency resource information. In this case, the information about the search space may include at least one of the identifier (ID) of the search space from which the terminal can detect a PDCCH containing DCI, the format of the DCI detectable in each search space, the detection interval (duration), or resource information.

[0120] Subsequently, the terminal can detect PDCCH at a monitoring occasion and receive DCI based on the RRC configuration information (S12020). Based on the RRC configuration information, the terminal can detect PDCCH in a specific search space for monitoring occasions depending on the service and / or data type and obtain DCI.

[0121] In this case, the DAI included in DCI may have different bits set depending on the DCI format. For example, in DCI Format 1_0, the DAI may have 2 bits set, while in DCI Format 1_1, it may have 1 bit for semi-static HARQ-ACK codebooks and 2 bits for dynamic HARQ-ACK codebooks.

[0122] Table 3 below shows an example of DAI bits in DCI format.

[0123] [Table 3]

[0124] Furthermore, the terminal may be allocated resources via PDCCH (or DCI) for receiving PDSCH or transmitting PUSCH.

[0125] Subsequently, the terminal can either receive a PDSCH using its allocated resources or transmit a PUSCH to the base station (S12030). If the terminal receives a PDSCH from the base station, it can generate a HARQ-ACK codebook indicating the ACK / NACK of the received PDSCH based on the DAI value included in the PDCCH (or DCI) that schedules the PDSCH, and transmit the generated HARQ-ACK codebook to the base station along with the Uplink Control Information (UCI). At this time, the PUSCH may be repeatedly transmitted between slots using the resources allocated via the DCI.

[0126] Symbols assigned by the base station via DCI for repeated transmission of PUSCH may be assigned to the terminal using the position of the starting symbol, the length of the assigned resource, and the number of repetitions. If the assigned symbol is an invalid symbol or overlaps with a specific symbol, PUSCH may not be transmitted with that symbol, or it may be transmitted multiplexed with the signal transmitted with the specific symbol.

[0127] For example, if the symbol for repeated transmission of PUSCH and the symbol for transmitting PUCCH overlap, the terminal can multiplex PUSCH and PUCCH and transmit them to the base station. Also, if the symbol assigned for repeated transmission of PUSCH overlaps with any of the following symbols, the terminal will determine (or recognize) that symbol as invalid, and repeated transmission of PUSCH will not be performed with that symbol.

[0128] - CORESET #0 symbol,

[0129] - In the case of a half-duplex terminal, symbols for transmitting downlink signals from other cells and symbols for transmitting SS / PBCH are transmitted.

[0130] - Semi-static downlink symbol for Pcell

[0131] - Gap symbol following semi-static downlink symbol in Pcell

[0132] - If the application of an invalid symbol pattern is instructed via DCI, invalid symbols set in the bit map of the RRC signaling.

[0133] - Symbol for receiving SS / PBCH

[0134] UL preemption indication

[0135] A preemption indication is a directive that a base station will use to preempt (or puncture) some of the resources in an already scheduled PDSCH to transmit downlink signals to other terminals. Similarly, a base station can use a directive that preempts (or punctures) some of the resources in an already scheduled PUSCH to transmit uplink signals to other terminals. This is called a UL preemption indication or UL cancellation indication. This invention relates to the design of a UL preemption indication and the operation of a terminal that receives a UL preemption indication.

[0136] In one embodiment of the present invention, a terminal may be configured with an RRC signal to receive a UL preemption instruction, which may be transmitted via a group-common PDCCH. That is, the terminal may have a search space, monitoring period, RNTI value, and length configured by the RRC signal for the UL preemption instruction, and the terminal blind-decodes the DCI scrambled with the RNTI value and length. When the terminal searches for the DCI scrambled with the RNTI value, it can determine that the DCI is a UL preemption instruction.

[0137] A UL preemption instruction can transmit the following information. First, the reference UL resource may be determined as follows. The reference UL resource may include all PRBs in the UL BWP. If the monitoring period of the UL preemption instruction is TINT, the reference UL resource of the UL preemption instruction received in the m-th period may be determined by Equation 1 below.

[0138]

number

[0139] In Equation 1, Δoffset is an offset value, which may be composed of RRC or set to a fixed value. Preferably, the offset value is a multiple of the number of symbols in the slot. The Δoffset value may also be determined by the PUSCH processing time. For example, if we assume that Tproc,2 is the minimum time it takes from receiving the PDCCH that schedules PUSCH to generating PUSCH, then Δoffset may be a value that increases proportionally to the Tproc,2 value. For example, Δoffset may be given as the ceil(Tproc,2 / Symbol_duration) value, where Symbol_duration is the length of one OFDM symbol. Furthermore, the terminal can determine Δoffset by considering TA (timing advance). That is, when determining Δoffset, the terminal can consider the time difference between the downlink frame boundary (DL frame boundary) and the uplink frame boundary (UL frame boundary) based on the TA value. Furthermore, in a reference UL resource, downlink symbols can be excluded by semi-static DL / UL assignment, which consists of cell-specific RRC signals. In addition, flexible symbols located immediately after the downlink symbols can be excluded. In this case, the number of flexible symbols to be excluded may be one symbol or may consist of RRC signals.

[0140] UL preemption instructions can be made using a bitmap that divides a reference UL resource into N parts and indicates with one bit whether each part is preempted, in order to indicate which symbols will be preempted (or punctured). Preferably, the bitmap is 14 bits long. Preferably, the reference UL resource is divided into 14 parts along the time axis, or into 7 parts along the time axis, with each part being divided into 2 parts along the frequency axis. Preferably, when the reference UL resource has S symbols, it is grouped into N sets along the time axis, and in one embodiment of the present invention relating to this, the terminal may be designed to allow a difference of up to 1 in the number of symbols contained in each set when it constitutes N sets.

[0141] The S symbols included in the referenced UL resource may be numbered 1, 2, ..., S in chronological order. In this case, the N sets according to the above method are constructed as follows: Of the total N sets, the first mod(S,N) set contains the ceil(S / N) symbol, and the remaining N-mod(S,N) sets can contain the floor(S / N) symbol. Here, mod(a,b) is a function that returns the remainder when a is divided by b, ceil(x) is a function that returns the smallest integer that is equal to or greater than x, and floor(x) is a function that returns the largest integer that is equal to or less than x. Here, mod(S,N) may be expressed as S-floor(S / N)*N.

[0142] When a terminal receives a UL preemption instruction, it does not transmit PUSCH signals on the uplink for symbols indicated as preempted by the UL preemption instruction. The terminal can transmit PUSCH signals for symbols not indicated as preempted by the UL preemption instruction. One way to transmit PUSCH signals is for the terminal to transmit signals for the remaining symbols other than those indicated as preempted by the UL preemption instruction. PUSCH signals that overlap with preempted symbols are discarded, while PUSCH signals that overlap with unpreempted symbols are transmitted. Alternatively, the terminal can sequentially transmit PUSCH signals to all transmittable symbols and discard the remaining PUSCH signals. Referring to Figure 34, if PUSCH signals are scheduled for 14 symbols for a terminal, and the UL preemption instruction indicates that the 5th symbol is preempted, the terminal will not transmit an uplink signal for the 5th symbol. Instead, the terminal must send PUSCH to symbols 1, 2, 3, 5, 6, 7, 8, 9, 10, 11, 12, 13, and 14. The resource elements (REs) of the PUSCH that the terminal should send may be numbered PUSCH#1, PUSCH#2, ..., PUSCH#14, depending on the OFDM symbol. That is, PUSCH#1 indicates the PUSCH RE sent with the first OFDM symbol of the PUSCH. Referring to Figure 34(a), the PUSCH transmitted to symbols 1, 2, 3, 5, 6, 7, 8, 9, 10, 11, 12, 13, and 14 may be PUSCH#1, PUSCH#2, PUSCH#3, PUSCH#4, PUSCH#6, PUSCH#7, PUSCH#8, PUSCH#9, PUSCH#10, PUSCH#11, PUSCH#12, PUSCH#13, and PUSCH#14, other than PUSCH#5.Referring to Figure 34(b), the PUSCH messages to be sent to symbols 1, 2, 3, 5, 6, 7, 8, 9, 10, 11, 12, 13, and 14 are, in order, PUSCH#1, PUSCH#2, PUSCH#3, PUSCH#4, PUSCH#5, PUSCH#6, PUSCH#7, PUSCH#8, PUSCH#9, PUSCH#10, PUSCH#11, PUSCH#12, and PUSCH#13, and PUSCH#14 does not need to be sent.

[0143] When a terminal receives a UL preemption instruction, the terminal may transmit the PUSCH that could not be transmitted using another resource to the symbol indicating that the UL preemption instruction has been preempted. In this case, the other resource is a different resource from the already scheduled PUSCH resource and is an uplink resource that is later in time than the scheduled PUSCH resource. For convenience, this resource is referred to as an additional resource. Preferably, the scheduled PUSCH and the additional resource have the same PRB in the frequency domain. In one embodiment of the present invention, the additional resource may be an uplink symbol with the earliest semi-static DL / UL assignment after the assigned PUSCH resource. In one embodiment of the present invention, the additional resource may be a flexible symbol or uplink symbol with a semi-static DL / UL assignment consisting of the earliest RRC after the assigned PUSCH resource. In one embodiment of the present invention, the additional resource may be from the assigned PUSCH resource onward, starting from symbol A. Preferably, A may consist of or be fixed RRC signals.

[0144] In one embodiment of the present invention, if a PUCCH is not transmitted due to a UL preemption instruction, or if the transmission of a PUCCH fails, the terminal can decide whether or not to retransmit the PUCCH based on the Uplink Control Information (UCI) transmitted via the PUCCH. For example, if the transmission of a PUCCH is affected by a UL preemption instruction (for example, if the RE (resource element), which is the time and frequency resource allocated for the transmission of the PUCCH, overlaps with the RE, which is the time and frequency resource indicated by the UL preemption instruction), the terminal may not transmit the PUCCH using the resources that overlap with the resources indicated by the UL preemption instruction, and may retransmit the PUCCH, including the UCI, using additional resources based on the Uplink Control Information (e.g., HARQ-ACK) contained in the PUCCH.

[0145] In yet another embodiment of the present invention, if a terminal receives a first PDCCH scheduling a first PUSCH transmission at a first time point, and then receives a second PDCCH scheduling a second PUSCH transmission at a second time point after the first time point, and both the first and second PUSCH transmissions are scheduled for transmission in the same transport block (TB), the terminal will not transmit the first PUSCH scheduled by the first PDCCH, but will only transmit the second PUSCH scheduled by the second PDCCH.

[0146] In this case, the terminal may determine whether the TB transmitted via the first PUSCH and the second PUSCH are identical based on the transmitted PDCCH. Specifically, the terminal can recognize (or determine) that the TB transmitted via the first PUSCH and the second PUSCH are identical if the HARQ process ID of the DCI transmitted in the two PDCCHs, the first and second PDCCH, is the same, and the value of the new data indicator field, which indicates whether it is new data or not, is the same.

[0147] Whether to execute or cancel the transmission of the first PUSCH may be determined by the terminal's PUSCH processing time. Specifically, if the transmission of part or all of the first PUSCH is scheduled between the last symbol of the second PDCCH and a specific time (or symbol), the transmission of the first PUSCH cannot be canceled. In other words, the terminal can transmit the first PUSCH. Conversely, part or all of the first PUSCH after the last symbol of the second PDCCH and a specific time (or symbol) does not need to be transmitted.

[0148] In yet another embodiment of the present invention, when a terminal receives a first PDCCH at a first time point that schedules a first PUSCH transmission, and a second PDCCH at a second time point that schedules a second PUSCH transmission, and both PUSCHs are scheduled to be transmitted overlapping by at least one symbol, the terminal will not transmit the first PUSCH and will transmit the second PUSCH. Whether or not the PUSCH that is not transmitted is transmitted may be determined by the PUSCH processing time. More specifically, if all or part of a PUSCH transmission occurs between the last symbol of the second PDCCH and a specific time (or symbol), that transmission cannot be canceled. That is, the terminal can transmit. Conversely, all or part of PUSCH transmissions after a specific time (or symbol) from the last symbol of the second PDCCH are not transmitted.

[0149] However, when receiving a PDCCH that schedules PUSCH transmissions containing the same TB, canceling all previously scheduled PUSCH transmissions may result in frequency waste from a frequency efficiency standpoint. Furthermore, canceling scheduled PUSCH transmissions entirely may also be a waste from a frequency efficiency standpoint. Additionally, there may be cases where it is necessary to cancel PUSCH transmissions using only some of the symbols used for the PUSCH transmission.

[0150] To solve this problem, the present invention proposes a method for canceling only a portion of a PUSCH using a transmitted CBG (code block group). In an embodiment of the present invention, when CBG-based transmission is set from a higher layer, the terminal can perform the following actions.

[0151] First, the terminal may have a number of CBGs configured from the upper layer. The terminal can receive a CBGTI (code block group transmission indicator) field in DCI format 0_1 ​​with a bit length equal to the number of configured CBGs. DCI format 0_1 ​​is a DCI that schedules a PUSCH. The CBGTI field may contain a bitmap for the CBGs to be transmitted, and the terminal can determine which CBGs to transmit from the bitmap for the CBGs. The terminal transmits the CBGs that are instructed to be transmitted in the CBGTI field, but must not transmit CBGs that are not instructed to be transmitted.

[0152] In one embodiment of the present invention, if a terminal receives a first PDCCH scheduling a first PUSCH transmission at a first time point, and receives a second PDCCH scheduling a second PUSCH transmission at a second time point after the first time point, both PUSCHs may be scheduled to transmit the same transport block (TB). In this case, the same CBG transmitted in the PUSCH scheduled via the second PDCCH may be transmitted in the first PUSCH. The terminal does not need to transmit symbols mapped to the same CBG as the CBG instructed to be transmitted in the PUSCH scheduled by the second PDCCH in the first PUSCH transmission. Conversely, the terminal can continue to transmit the remaining symbols in the first PUSCH transmission other than those mapped to the same CBG as the CBG instructed to be transmitted in the PUSCH scheduled by the second PDCCH.

[0153] If the same TB is scheduled, even if the terminal receives a later scheduled PUSCH, if the earlier scheduled PUSCH is multiplexed with UCI, the later scheduled PUSCH may be transmitted multiplexed with UCI.

[0154] Specifically, if the same TB is included in both the first and second PUSCH, and the terminal receives a second PDCCH scheduling the second PUSCH, the transmission of the first PUSCH scheduled via the first PDCCH may be canceled. However, if the first PUSCH, scheduled before the second PUSCH, is multiplexed with the UCI, then if the first PUSCH is not transmitted, the UCI, which is multiplexed with the first PUSCH, will also not be transmitted, and the base station will not be able to receive the UCI. Therefore, if the terminal receives a second PDCCH and all or part of the previously scheduled first PUSCH is not transmitted, and the first PUSCH is multiplexed with the UCI, the UCI cannot be transmitted to the base station, so the UCI can be multiplexed into the second PUSCH and transmitted to the base station. In this case, all of the UCI information may be multiplexed into the second PUSCH and transmitted, or only some of the information may be multiplexed into the second PUSCH and transmitted. Some of the information may include HARQ-ACK information.

[0155] Alternatively, the terminal may transmit information related to UCI multiplexing in the DCI field of the second PDCCH. The DCI field may be explicitly present for UCI multiplexing or may be inferred from the values ​​of other DCI fields, which may include beta offset indicator fields.

[0156] Whether or not to send a second PUSCH without sending the first PUSCH may be determined by the terminal's PUSCH processing time. Specifically, if a PDCCH canceling a PUSCH transmission is received, and all or part of a PUSCH transmission exists within a specific time (or symbol) from the last symbol of the PDCCH, the first PUSCH transmission does not need to be canceled.

[0157] In other words, even if the same TB is scheduled via the first PDCCH and the second PDCCH respectively, if part or all of the first PUSCH is located within a specific time (symbol) from the last symbol of the PDCCH, the terminal cannot cancel the transmission of the first PUSCH and can transmit the first PUSCH to the base station. Conversely, all or part of the first PUSCH located after a specific time (or symbol) from the last symbol of the PDCCH may be canceled and not transmitted.

[0158] PUSCH Repeated Transmission

[0159] In the enhanced ultra-reliable low-latency communication (eURLLC) under development in 3GPP NR release 16, various techniques are being discussed to provide a service that is both low-latency and highly reliable. In particular, on the uplink, it is planned to support a method in which the terminal repeatedly transmits the physical uplink shared channel (PUSCH) to the base station as quickly as possible in order to reduce latency and increase reliability. According to one aspect of the present invention, a method for the terminal repeatedly transmitting the physical uplink shared channel as quickly as possible is disclosed.

[0160] Generally, a terminal receives PUSCH scheduling information from a base station. This PUSCH scheduling information can be received, for example, from a PDCCH (or DCI). Based on the received scheduling information, the terminal transmits a PUSCH over the uplink. At this time, the time-domain resource assignment (TDRA) and frequency-domain resource assignment (FDRA) for PUSCH transmission included in the DCI determine the time-frequency resource on which the PUSCH will be transmitted. The time resource on which the PUSCH will be transmitted consists of consecutive symbols, and it is impossible for a single PUSCH to be scheduled across slot boundaries.

[0161] 3GPP NR Release 15 supports inter-slot repeat transmission of PUSCH. First, the terminal may be configured by the base station to set the number of repeat transmissions. Let's call the number of repeat transmissions set for the terminal K. When the terminal receives a PDCCH (or DCI) in slot n to schedule a PUSCH and is instructed to transmit a PUSCH in slot n+k, the terminal can transmit PUSCH in K consecutive slots starting from slot n+k. That is, it can transmit PUSCH in slots n+k, n+k+1, ..., n+k+K-1. The time and frequency resources used for transmitting PUSCH in each slot are the same as those instructed in the DCI. That is, PUSCH may be transmitted in each slot with the same symbol and the same PRB. Frequency hopping may be configured for the terminal to obtain diversity gain in the frequency domain. Frequency hopping can be configured in two ways: intra-slot frequency hopping, which performs frequency hopping within a slot, and inter-slot frequency hopping, which performs frequency hopping for each slot. If intra-slot frequency hopping is configured on a terminal, the terminal divides the PUSCH in each slot in the time domain in half. Half is transmitted with a scheduled PRB, and the other half is transmitted with a PRB calculated by adding an offset value to the scheduled PRB. Here, the offset value can be set in the upper layer as either two or four values, and any one of these values ​​may be indicated via DCI. If inter-slot frequency hopping is configured on a terminal, the terminal transmits the PUSCH with a scheduled PRB in odd-numbered slots where the PUSCH is transmitted, and transmits the PUSCH with a PRB calculated by adding an offset value to the scheduled PRB in even-numbered slots. When a terminal is performing repeated transmissions in a slot, if the symbol for which a PUSCH should be transmitted in a particular slot is configured as a semi-static downlink symbol, the terminal will not transmit a PUSCH in that slot.PUSCH messages that could not be sent are deferred to another slot and not sent.

[0162] The reasons why the aforementioned release 15 repetitive transmission is not suitable for providing eURLLC services are as follows:

[0163] First, it is difficult to provide high reliability. For example, if one slot consists of 14 symbols and PUSCH is transmitted with symbols 12 and 13, then symbols 12 and 13 will be repeatedly transmitted in the next slot. In the next slot, even though it is possible to transmit with symbols 1 through 11, transmission is not performed, making it difficult to obtain high reliability.

[0164] Next, low latency is difficult to provide. For example, suppose one slot consists of 14 symbols, and to achieve high reliability, a PUSCH is transmitted with symbols 0 through 13. For the base station to successfully receive the PUSCH, it must receive the last symbol of the PUSCH, i.e., symbol 13. Therefore, a problem arises where the delay time increases with the length of the PUSCH.

[0165] To address this, according to one aspect of the present invention, a method for repeatedly transmitting PUSCH within a single slot is disclosed. More specifically, a terminal can repeatedly transmit scheduled PUSCH consecutively. The term 'consecutively' means that PUSCH is transmitted again from the symbol immediately following the completion of one PUSCH. Such a method may be called mini-slot-level PUSCH repeat transmission or PUSCH repeat type B, while the repeat transmission method of 3GPP NR release 15 described above may be called slot-level PUSCH repeat transmission method or PUSCH repeat type A.

[0166] Mini-slot-level push repetition transmission can solve the problems that occur in the slot-level push repetition transmission method described above.

[0167] First, high reliability can be provided. For example, if one slot consists of 14 symbols, and PUSCH is transmitted with symbols 12 and 13, then it may be repeated in the next slot with symbols 1 and 2. Therefore, since transmissions are immediate and continuous, high reliability can be obtained.

[0168] Furthermore, low latency can be provided. For example, suppose one slot consists of 14 symbols, and to obtain high reliability, PUSCH is transmitted from symbol 0 to symbol 1. Since it is transmitted repeatedly within the slot, it may be transmitted again from symbol 2 to symbol 3, and then repeatedly from symbol 4 to symbol 5. Thus, a reliability similar to that of transmitting PUSCH with a slot length of 14 can be obtained. However, in this case, depending on the channel conditions, the base station does not necessarily succeed in receiving all repeated transmissions, but may succeed in the middle of the repeated transmissions. Therefore, depending on the situation, the latency time may be lower by succeeding in transmission after symbol 2, when the first repeated transmission ends.

[0169] However, when repeatedly transmitting a PUSCH, if the symbol for repeated transmission of a PUSCH and the symbol for transmission of a PUCCH overlap, the repeatedly transmitted PUSCH and PUCCH may be multiplexed for the transmission of a PUCCH. In this case, the PUSCH to be multiplexed with the PUCCH must be determined from among the repeatedly transmitted PUSCHs. That is, when the resources for repeated transmission of a PUSCH and the resources for transmission of a PUCCH overlap, the terminal can select a resource for multiplexing the PUCCH from among the resources allocated for repeated transmission of a PUSCH, and then multiplex the PUSCH and PUCCH with the selected resource and transmit it to the base station. Hereinafter, in the present invention, a resource may include at least one of a symbol and a PRB.

[0170] Hereinafter, in this invention, each PUSCH that is repeatedly transmitted with the same TB will be referred to as a PUSCH repetition, and PUSCH includes the entire PUSCH repetition.

[0171] Furthermore, in the present invention, in the PUSCH repetition transmission, nominal PUSCH repetition means the resources allocated by the base station for PUSCH repetition transmission using RRC configuration information and / or downlink control information (DCI), while actual PUSCH repetition means the resources consisting only of valid symbols, with invalid symbols removed from the nominal PUSCH repetition.

[0172] Figures 13 to 18 show an example in which a PUSCH according to one embodiment of the present invention includes four PUSCH repetitions.

[0173] Figure 13 shows an example where PUSCH is transmitted four times.

[0174] Referring to Figure 13, if a terminal receives a PDCCH from a base station to schedule a PUSCH transmission, it can perform a PUSCH repeat transmission, repeatedly sending the same TB to reduce delay and improve reliability.

[0175] A PUSCH repetition may include DMRS, and the following explanation assumes that all PUSCH repetitions include DMRS. As shown in Figure 13, there may be cases where the resources for repeated transmission of PUSCH and the resources for transmission of PUCCH overlap. For example, as shown in Figure 13, a PUCCH may be set up in the second slot to transmit UCI. In this case, the resources set up to transmit PUCCH (e.g., symbols) may overlap with the resources for the PUSCH repetition to repeatedly transmit PUSCH (e.g., symbols). If PUCCH overlaps with the third PUSCH repetition (PUSCH rep#2) and the fourth PUSCH repetition (PUSCH rep#3), the terminal cannot transmit both PUCCH and PUSCH on the two channels simultaneously with a single symbol, but can instead multiplex PUSCH and PUCCH for transmission. The following describes the method for multiplexing PUSCH and PUCCH proposed in this invention.

[0176] (Proposal 1: Transmit one PUSCH repeatation by multiplexing it with PUCCH's UCI)

[0177] When a PUSCH is transmitted multiple times using multiple resources contained in one or more slots, and the resources for the repeated transmission of PUSCH overlap with the resources for the transmission of PUCCH, the terminal can multiplex one of the resources for the repeated transmission of PUSCH with the UCI of PUCCH and transmit it to the base station. Here, the resources may include at least one of symbols or PRBs.

[0178] Method 1: Multiplexing with the first PUSCH repeat among the PUSCH resources that overlap with PUCCH.

[0179] Figure 14 shows an example of a method in which, as one embodiment of the present invention, when PUSCH is transmitted using multiple resources, the UCI of PUSCH is multiplexed with the first resource among the multiple resources.

[0180] Referring to Figure 14, if the resource for sending PUCCH and the resource for repeatedly sending PUSCH overlap by at least one symbol, the UCI transmitted via PUCCH may be multiplexed and transmitted in the PUSCH repeat that is at the earliest time among all PUSCH repeats of PUSCH that include the overlapping PUSCH repeat.

[0181] In other words, among the PUSCH repetitions, which are resources allocated from the base station via DCI for transmitting PUSCH, the UCI, which is the control information transmitted by the terminal to the base station, may be multiplexed in the PUSCH repetition that is always at the forefront in time. In this case, the UCI does not need to be multiplexed in the remaining PUSCH repetitions. For example, as shown in Figure 14, when four PUSCH repetitions for transmitting PUSCH (PUSCH rep#0, PUSCH rep#1, PUSCH rep#2, and PUSCH rep#3) are configured, PUSCH may overlap with the third PUSCH repetition (PUSCH rep#2) and the fourth PUSCH repetition (PUSCH rep#3).

[0182] In this case, the terminal multiplexes the UCI transmitted via PUCCH with PUSCH rep#0, which is the earliest PUSCH repeat in time, and does not need to transmit PUCCH separately to the base station.

[0183] In other words, a PUSCH may be repeatedly transmitted using multiple resources in one or more slots, and a PUSCH for UCI (e.g., HARQ-ACK, channel status information, etc.) may be transmitted in one slot. In this case, if one or more resources for the repeated transmission of PUSCH overlap with the resources for transmitting PUCCH, the terminal can multiplex the UCI with the resource at the very beginning of the resources for the repeated transmission of PUSCH and transmit it.

[0184] Method 2: Multiplexing is performed with the PUSCH repeat that is located at the very beginning of the slot in which PUCCH is sent, among the PUSCH repeats that overlap with PUCCH.

[0185] Figure 15 shows an example of a method in which, as one embodiment of the present invention, when a PUSCH is transmitted using multiple resources, the resource for repeated transmission of the first PUSCH and the UCI of the PUSCH are multiplexed in the slot where the PUSCH is transmitted.

[0186] Referring to Figure 15, if the resources for transmitting PUCCH and the resources for repeatedly transmitting PUSCH overlap in at least one symbol, the UCI transmitted via PUCCH may be multiplexed and transmitted in the PUSCH repeat that is at the earliest time in the slot where PUCCH is transmitted, among all PUSCH repeats of PUSCH that overlap with PUSCH. That is, among the PUSCH repeats which are resources allocated via the base station's DCI for transmitting PUSCH, the PUSCH repeats included in the slot where PUCCH is transmitted are selected first, and the UCI may be multiplexed with the earliest PUSCH repeat among the selected PUSCH repeats.

[0187] In this case, UCI does not need to be multiplexed for PUSCH repetitions in slots other than the slot from which PUCCH is transmitted, and for PUSCH repetitions in the slot from which PUCCH is transmitted, all but the PUSCH repetition that is at the very beginning in terms of time do not need to be multiplexed with UCI.

[0188] For example, as shown in Figure 15, if PUCCH is transmitted in the second slot (slot #1), and the second PUSCH repetition (PUSCH rep #1), the third PUSCH repetition (PUSCH rep #2), and the fourth PUSCH repetition (PUSCH rep #3) for repeated transmission of PUSCH are configured in the second slot, the resources for transmitting PUCCH and the resources for repeated transmission of PUSCH may overlap.

[0189] In this case, PUCCH may overlap with the third PUSCH repeat (PUSCH rep#2) and the fourth PUSCH repeat (PUSCH rep#3) in the second slot. The UCI for PUCCH may be multiplexed with the second PUSCH repeat (PUSCH rep#1), which is the earliest PUSCH repeat in time among the PUSCH repeats in the second slot. The terminal does not need to send a separate PUCCH because the UCI has been multiplexed with the PUSCH.

[0190] Figure 16 shows an example of a method for determining the subcarrier interval and the resulting slots for PUCCH transmission resources that overlap with the resources for PUSCH transmission, when PUSCH is transmitted using multiple resources, as an embodiment of the present invention.

[0191] If the subcarrier spacing of the cell from which PUCCH is transmitted is different from the subcarrier spacing of the cell from which PUSCH is transmitted, the slot from which PUCCH is transmitted in Proposal 1 can be interpreted in two ways. Firstly, the slot from which PUCCH is transmitted may be the slot determined by the subcarrier spacing of the cell from which PUCCH is transmitted. Then, the PUSCH repetitions that overlap with the slot from which PUCCH is transmitted may be the PUSCH repetitions included in the slot from which PUCCH is transmitted. Secondly, the slot from which PUCCH is transmitted may be the slot determined by the subcarrier spacing of the cell from which PUSCH overlaps with PUCCH.

[0192] For example, as shown in Figure 16, if the subcarrier interval of PUCCH is determined by the first method, the PUSCH repetitions in the slot from which PUCCH is transmitted may be the third PUSCH repetition (PUSCH rep#2) and the fourth PUSCH repetition (PUSCH rep#3). On the other hand, if the subcarrier interval of PUCCH is determined by the second method, the PUSCH repetitions in the slot from which PUCCH is transmitted may be the second PUSCH repetition (PUSCH rep#1), the third PUSCH repetition (PUSCH rep#2), and the fourth PUSCH repetition (PUSCH rep#3).

[0193] Method 3: Multiplexing with the first PUSCH repeat among the PUSCH resources that overlap with PUCCH.

[0194] Figure 17 shows an example of a method in which, as one embodiment of the present invention, when PUSCH is transmitted using multiple resources, the UCI of PUCCH is multiplexed in the first resource among the resources for repeated transmission of PUSCH that overlap with the resource on which PUCCH is transmitted.

[0195] Referring to Figure 17, if the resource for transmitting PUCCH and the resource for repeatedly transmitting PUSCH overlap in at least one symbol, the UCI transmitted via PUCCH may be multiplexed and transmitted in the PUSCH repeat that is the earliest in time among all PUSCH repeats of PUSCH that overlap with PUCCH. That is, among the PUSCH repeats which are resources allocated via the base station's DCI for transmitting PUSCH, the PUSCH repeat that overlaps with the symbol on which PUCCH is transmitted is selected first. Then, the earliest PUSCH repeat among the selected PUSCH repeats may be multiplexed with the UCI for PUCCH.

[0196] In this case, UCI does not need to be multiplexed for PUSCH repetitions that do not overlap with the resources for PUCCH, and UCI does not need to be multiplexed for all PUSCH repetitions except for the first PUSCH repetition that overlaps with the symbol (or resource) to which PUCCH is sent.

[0197] For example, as shown in Figure 17, if the symbol of the resource to which PUCCH is transmitted overlaps with the third PUSCH rep(2) and the fourth PUSCH rep(3), the terminal can multiplex the UCI to be transmitted via PUCCH in the third PUSCH rep(2), which is the first of the three PUSCH rep(3), and transmit it to the base station. In this case, the terminal does not need to transmit a separate PUCCH.

[0198] Specifically, a PUSCH for a particular repetition type (e.g., PUSCH repetition type B) may be repeatedly transmitted in one or more consecutive slots with multiple allocated resources (PUSCH repetitions), and a PUCCH for UCI such as HARQ-ACK and / or CSI information may be transmitted in one or more slots that overlap with the PUSCH transmission. In this case, the terminal can multiplex the UCI in the PUSCH repetition that is at the earliest time among the multiple PUSCH repetitions included in the PUSCH that overlaps with the PUCCH transmission. The terminal can then transmit the PUSCH multiplexed with the UCI to the base station.

[0199] In this case, the PUSCH repetition that is multiplexed with the UCI may not be the nominal PUSCH repetition, which is a resource allocated by the base station, but rather the first PUSCH repetition among the actual PUSCH repetitions that the terminal has determined to be a valid symbol for repeated transmission of PUSCH.

[0200] For a PUSCH repeatation to be multiplexed with UCI, certain conditions must be met. For example, a PUSCH repeatation that is multiplexed with UCI must contain more than one symbol and must meet the processing time required for UCI multiplexing.

[0201] In other words, only effective PUSCH repeats containing one or more symbols from the nominal PUSCH repeats (which are resources for repeated transmission of PUSCH assigned by the base station, excluding invalid symbols) may be multiplexed with UCI. To put it another way, the terminal does not expect that the effective PUSCH repeats to be multiplexed with PUCCH consist of only one symbol.

[0202] Method 4: Multiplexing with the first PUSCH repeat among the PUSCH resources that overlap with the slot in which PUCCH is sent.

[0203] Specifically, if the resources for transmitting PUCCH and the resources for repeatedly transmitting PUSCH overlap in at least one symbol, the UCI for PUCCH may be multiplexed in the leading PUSCH repeat that overlaps with the slot in which PUCCH is transmitted. That is, the terminal can select a PUSCH repeat for repeatedly transmitting PUSCH that overlaps with the slot in which PUCCH is transmitted. The terminal can then multiplex the UCI in the leading PUSCH repeat among the selected PUSCH repeats and transmit it to the base station. At this time, the UCI does not need to be multiplexed in PUSCH repeats that do not overlap with the slot in which PUCCH is transmitted, and the UCI does not need to be multiplexed in the remaining PUSCH repeats other than the leading PUSCH repeat that overlaps with the slot in which PUCCH is transmitted.

[0204] For example, as shown in Figure 15, a PUCCH may be sent using a resource in the second slot, and the second slot may overlap with the second PUSCH repetition (PUSCH rep#1), the third PUSCH repetition (PUSCH rep#2), and the fourth PUSCH repetition (PUSCH rep #3), in which PUSCH is repeatedly sent. In this case, the UCI to be sent via PUCCH may be multiplexed and sent in the second PUSCH repetition (PUSCH rep#1), which is the first PUSCH repetition among the second PUSCH repetition (PUSCH rep#1), the third PUSCH repetition (PUSCH rep#2), and the fourth PUSCH repetition (PUSCH rep #3) in the second slot, and the terminal does not need to send a separate PUCCH.

[0205] Method 5: Multiplexing with the last PUSCH repeat among the PUSCH resources that overlap with PUCCH.

[0206] Figure 18 shows an example of a method in which, as one embodiment of the present invention, when a PUSCH is transmitted using multiple resources, the UCI of the PUSCH is multiplexed with the resource located at the end of the multiple resources.

[0207] Referring to Figure 18, if the resource for sending PUCCH and the resource for repeatedly sending PUSCH overlap by at least one symbol, in order to satisfy the processing time required for the multiplexing of the UCI of PUCCH and PUSCH, the UCI may be multiplexed and sent via PUCCH in the last PUSCH repeat in time among all PUSCH repeats of the PUSCH that overlap with PUSCH. That is, from among the PUSCH repeats for repeated sending of PUSCH, a PUSCH repeat that overlaps with the resource (or slot) on which PUCCH is sent may be selected. Then, the UCI may be multiplexed in the last PUSCH repeat in time among the selected PUSCH repeats. For PUSCH repetitions that do not overlap with the slot in which PUCCH is sent, UCI does not need to be multiplexed. For PUSCH repetitions that overlap with the slot (or resource) in which PUCCH is sent, UCI does not need to be multiplexed for all but the last PUSCH repetition.

[0208] For example, as shown in Figure 18, the second slot in which PUCCH is transmitted may overlap with the second PUSCH rep(PUSCH rep#1), the third PUSCH rep(PUSCH rep#2), and the fourth PUSCH rep(PUSCH rep#3). In this case, the UCI to be transmitted via PUCCH may be multiplexed and transmitted in the fourth PUSCH rep(PUSCH rep#1), which is the last PUSCH rep in time among the second PUSCH rep(PUSCH rep#1), the third PUSCH rep(PUSCH rep#2), and the fourth PUSCH rep(PUSCH rep#3) in the second slot, and the terminal does not need to transmit a separate PUCCH.

[0209] In Proposal 1, if methods 1-5 overlap with PUCCH and PUSCH repetition, the following two points may be considered when selecting PUSCH repetition as a resource for UCI redundancy.

[0210] Firstly, each PUSCH repeat must satisfy the processing time required for the UCI to redeploy it. Specifically, for the UCI to redeploy a PUSCH repeat, processing time is required until redeployment is complete. If there are PUSCH repeats that do not meet the processing time requirement, those repeats will be excluded, and the UCI may select PUSCH repeats that meet the processing time requirement for redeployment.

[0211] If the processing time required for multiplexing is not met for all PUSCH repetitions, the PUSCH repetitions do not need to be multiplexed with the UCI. In this case, the terminal can transmit the UCI to the base station via PUCCH without multiplexing it with the PUSCH repetitions, and does not need to transmit PUSCH in PUSCH repetitions that overlap with PUCCH.

[0212] Any PUCCH that is not sent by the PUCCH may be sent after the PUCCH has been sent.

[0213] Secondly, there may be delay constraints on UCI transmission. That is, if there is a delay time limit that the UCI must be transmitted within a certain time, the terminal can select only the PUSCH repeats that can satisfy this delay time and multiplex the UCI.

[0214] For example, if the conditions for limiting the delay time for UCI transmission are set by a specific value from a higher layer, the terminal must transmit the UCI to the base station within the delay time set by that specific value. Therefore, the terminal can select a push repeat for UCI multiplexing from among the push repeats that satisfy the delay time limit, excluding push repeats that do not satisfy (violate) such delay time limit conditions.

[0215] In other words, for PUSCH repetitions located on symbols other than those specified by the delay time constraints imposed by the higher layer, UCI does not need to be multiplexed.

[0216] (Proposal 2: Multiple PUSCH repetitions are multiplexed and transmitted with PUSCH's UCI.)

[0217] When a PUSCH is transmitted multiple times using multiple resources in one or multiple consecutive slots, and the resources for the repeated transmission of PUSCH overlap with the resources for transmitting PUCCH, the terminal can multiplex multiple PUSCH repetitions and PUCCH from the resources for the repeated transmission of PUSCH and transmit them to the base station. Here, the resources may include at least one of symbols or PRBs.

[0218] Method 0: Send the UCI of PUCCH for all PUSCH repetitions that overlap with PUCCH.

[0219] If the resource for sending a PUCCH and a PUSCH repetition overlap in at least one symbol, the UCI may be multiplexed and transmitted in all PUSCH repetitions of the PUCCH that overlap with the PUCCH. In other words, the UCI may be multiplexed and transmitted in all of one or more PUSCH repetitions contained within a single PUSCH.

[0220] Method 1: Send the UCI of PUCCH using a PUSCH repetition that overlaps with PUCCH.

[0221] If the resource for sending PUCCH and a PUSCH repetition overlap in at least one symbol, the UCI may be multiplexed and transmitted for all PUSCH repetitions that overlap with PUCCH. In other words, from among the PUSCH repetitions of PUSCH, PUSCH repetitions that overlap with the symbol on which PUCCH is sent may be selected, and the selected PUSCH repetitions may be multiplexed and transmitted with the UCI for PUCCH. In this case, PUSCH repetitions that do not overlap with the symbol on which PUCCH is sent do not need to be multiplexed with the UCI.

[0222] Method 2: Send the UCI of PUCCH in all PUCCH repetitions included in the slot where PUCCH is sent.

[0223] If the resource for sending PUCCH and the PUSCH repetitions overlap by at least one symbol, the UCI may be multiplexed and sent in all PUSCH repetitions in the slot where PUCCH is sent. In other words, from among the PUSCH repetitions of PUSCH, PUSCH repetitions included in the slot where PUCCH is sent may be selected, and the UCI for PUCCH may be multiplexed and sent in the selected PUSCH repetitions. That is, from among the PUSCH repetitions of PUSCH, slots where PUCCH is sent may be selected, and the UCI may be multiplexed and sent in the PUSCH repetitions included in the selected slots. In this case, PUSCH repetitions in slots where PUCCH is not sent do not need to be multiplexed with the UCI.

[0224] Method 3: The UCI of PUCCH is multiplexed and transmitted using the PUSCH repetition located at the very beginning of each slot that overlaps with PUCCH.

[0225] If the resource for sending PUCCH and the PUCCH repetition overlap in at least one symbol, the slot from which PUCCH is sent may be selected first. Then, the UCI may be multiplexed and sent in each selected slot using the PUCCH repetition that is at the earliest time.

[0226] Method 4: The UCI of PUCCH is multiplexed and transmitted using the PUSCH repeat located at the very beginning of each slot that overlaps with the PUCCH slot.

[0227] When PUCCH and a PUSCH repeatation for repeated transmission of PUSCH overlap in at least one symbol, a slot overlapping with the slot from which PUCCH is transmitted may be selected first. Then, the UCI may be multiplexed and transmitted in the PUSCH repeatation that is at the earliest time position among the selected slots.

[0228] When the UCI is multiplexed by multiple push replies, the UCI may be transmitted in the following manner.

[0229] Method 1: When all identical UCIs are multiplexed into each of multiple push repetitions, all identical UCIs may be transmitted repeatedly in each push repetition. That is, when a base station receives a UCI multiplexed in one push repetition, it can successfully receive the UCI without receiving other push repetitions, because all the UCIs are contained in that one push repetition.

[0230] Method 2: When UCI is multiplexed with multiple push repetitions, the UCI may be transmitted by distributing it as evenly as possible among the push repetitions. That is, when UCI is multiplexed with multiple push repetitions, the UCI may be included in each of the multiple push repetitions being multiplexed, with an equal distribution of bits, and transmitted.

[0231] In this case, the UCI may be multiplexed evenly with push repetitions so that the difference is at most 1 bit. For example, if the UCI includes HARQ-ACK, CSI type 1, and CSI type 2, the UCI may be evenly divided and included in N push repetitions, each containing X bits. In this case, the mod(X,N) push repetitions may be multiplexed with a ceil(X / N) bit UCI, and the remaining N-mod(X,N) push repetitions may be multiplexed with a floor(X / N) bit UCI.

[0232] Method 3: In a PUSCH repetition contained in a single slot, the UCI may be distributed as evenly as possible during transmission. That is, in PUSCH repetitions contained in the same slot, the UCI may be divided into equal bits and multiplexed, while in PUSCH repetitions in different slots, the UCI does not need to be divided and transmitted separately.

[0233] In yet another embodiment of the present invention, if PUCCH and PUSCH overlap in at least one symbol, the terminal may send PUCCH instead of PUSCH in the following cases:

[0234] - First: If the priority of a UL-SCH transmitted via PUSCH is lower than the priority of a UCI transmitted via PUCCH, the PUSCH that overlaps with the PUCCH may not be transmitted, and only the PUCCH may be transmitted. In this case, the priority may be indicated via the PDCCH that schedules the PUSCH and PUCCH, or it may be determined by a higher layer.

[0235] - Second: If there are no or insufficient resources for PUSCH to multiplex and transmit a UCI, the PUSCH that overlaps with PUCCH may not be transmitted, and only PUCCH may be transmitted. For example, if a single-symbol PUSCH and the DMRS symbol of the PUSCH are located at the end of the PUSCH, and the UCI must be multiplexed with the symbol immediately following the DMRS symbol, then there are no resources to multiplex and transmit the UCI. In this case, since the UCI cannot be multiplexed with PUSCH, the terminal may not transmit PUSCH and instead transmit PUCCH.

[0236] In other words, when a PUSCH repetition and UCI (e.g., HARQ-ACK and / or CSI information) are multiplexed, the PUSCH repetition may consist of two or more symbols. To put it another way, the terminal can assume that a PUSCH repetition overlapping with PUCCH contains one or more symbols.

[0237] If there are no or insufficient PUSCH resources to multiplex and transmit the UCI using PUSCH (for example, if a single PUSCH symbol and the DMRS symbol of the PUSCH are located at the end of the PUSCH, and the UCI must be multiplexed using the symbol immediately following the DMRS symbol), then there are no resources for the UCI to be transmitted, making it impossible to multiplex the UCI using PUSCH. In this case, the terminal may choose not to transmit the PUSCH using resources that overlap with PUCCH, and instead transmit the PUCCH. Alternatively, the terminal may choose to transmit the PUSCH using the resources in question, but not the PUCCH. Or, the terminal may be instructed via PDCCH which channel of PUSCH or PUCCH to transmit. For example, the channel instructed by the later transmitted PDCCH may be transmitted, and other channels may not be transmitted, or the channel to be transmitted may be determined by the DCI transmitted by the PDCCH.

[0238] Specifically, if a particular field in the DCI that schedules PUSCH indicates a particular code point, PUSCH may not be sent, and PUSCH may be sent instead. Here, the particular code point may be one that is specified to have a beta_offset value of 0. The beta_offset is indicated by a DCI field called the beta_offset indicator, and is a parameter used to determine the number of REs that the beta_offset UCI occupies when multiplexing PUSCH.

[0239] In the second method described above, if there are no or insufficient resources to multiplex and transmit the UCI to PUSCH using the symbol immediately following the DMRS symbol (for example, if the DMRS symbol of PUSCH is located at the end of PUSCH's symbols, and therefore there is no symbol immediately following the DMRS symbol, or if there is a symbol immediately following the DMRS symbol of PUSCH, but the number of REs on that symbol is insufficient, making it impossible to transmit the UCI while satisfying a sufficient code rate), the UCI may be multiplexed using additional REs on the symbol immediately preceding the DMRS symbol. As an example, the UCI is sequentially mapped and multiplexed using the symbols immediately following the symbol to which the DMRS is mapped, and then subsequent symbols. If there are insufficient REs required for multiplexing during UCI mapping, the UCI is sequentially mapped and multiplexed using the symbols immediately preceding the symbol to which the DMRS is mapped, and then preceding symbols.

[0240] As yet another example, the UCI can be mapped alternately to the symbol immediately following and preceding the symbol to which the DMRS is mapped, and then multiplexed with PUSCH. That is, the UCI is first mapped and multiplexed on the symbol immediately following the symbol to which the DMRS is mapped. If there is insufficient RE to multiplex the UCI, the UCI is mapped on the symbol immediately preceding the symbol to which the DMRS is mapped. If there is still insufficient RE to multiplex the UCI, the UCI is mapped and multiplexed on the symbol after the symbol following the symbol to which the DMRS is mapped. If the UCI is still not mapped and there is insufficient RE, the UCI may be mapped and multiplexed on symbols prior to the symbol immediately following the symbol to which the DMRS is mapped. In this way, the UCI may be mapped alternately to symbols before and after the symbol to which the DMRS is mapped. As yet another example, among the remaining symbols other than the symbol to which the DMRS is mapped, the UCI may be mapped and multiplexed unconditionally, starting from the symbol that is at the beginning in time.

[0241] If a symbol mapped to a DMRS contains resources (e.g., REs) that are not mapped to a DMRS, those resources may be used for UCI multiplexing. For example, UCIs may be mapped sequentially to symbols starting from the symbol immediately following the DMRS symbol for multiplexing. If there are insufficient REs required for UCI multiplexing, UCIs may be mapped to REs that are not mapped to a DMRS symbol for multiplexing. Subsequently, if there are still insufficient REs required for UCI multiplexing, UCIs may be mapped sequentially to symbols preceding the DMRS symbol for multiplexing.

[0242] In yet another embodiment, the UCI may first be mapped to the symbol immediately following the symbol to which the DMRS is mapped. Then, if there are insufficient REs required for UCI multiplexing, the UCI may be mapped to a resource (e.g., an RE) that is not mapped to the DMRS in the symbol to which the DMRS is mapped, and multiplexing may be performed. If there are insufficient REs required for UCI multiplexing, the UCI may be mapped to the symbol immediately preceding the symbol to which the DMRS is mapped, and multiplexing may be performed.

[0243] If further REs are needed for UCI multiplexing, the UCI can be multiplexed by sequentially mapping the symbols from the symbol immediately following the symbol mapped with DMRS to the symbols before the symbol immediately following the symbol mapped with DMRS. In this way, the UCI may be mapped alternately to symbols after and before the DMRS symbol.

[0244] In another embodiment, the UCI may be multiplexed unconditionally, starting with the symbol that is in the earliest position in time among all symbols.

[0245] Another problem that the present invention aims to solve is a method for transmitting a UCI when a PUCCH for transmitting a low-priority HARQ-ACK and a PUCCH for transmitting a high-priority SR (scheduling request) overlap by at least one symbol.

[0246] In NR Rel-15, if a PUCCH sending an SR and a PUCCH sending a HARQ-ACK overlapped by at least one symbol, the following behavior occurred:

[0247] In the case of SR with PUCCH format 0 + HARQ-ACK with PUCCH format 1, i.e., when the resources for sending the SR (PUCCH format 0) and the HARQ-ACK (PUCCH format 1) overlap, the terminal sends the HARQ-ACK with PUCCH format 1 and does not send the SR with PUCCH format 0 (this is only possible if the SR is a positive SR). However, because the SR has a relatively higher priority, not sending the SR may not be the correct behavior.

[0248] To resolve the above-mentioned problems, we propose the following method.

[0249] Method 1: The remaining bits of PUCCH format 1 may contain SR information and be transmitted.

[0250] Specifically, in the case of PUCCH format 1, a maximum of 2 bits of information can be transmitted. If the HARQ-ACK is 1 bit, then 1 bit will remain. The SR transmitted in PUCCH format 0 may be represented by 1 bit. For example, 0 is a negative SR and 1 is a positive SR. The remaining 1 bit in PUCCH format 1 may be used to include the SR information, and the 1 bit HARQ-ACK and the 1 bit SR may be concatenated to create 2 bits of information, and the 2 bits HARQ-ACK and SR may be transmitted in PUCCH format 1.

[0251] If the HARQ-ACK is 2 bits, the 2 bits of the HARQ-ACK may be bundled into 1 bit, and the bundled 1-bit HARQ-ACK and 1-bit SR may be concatenated to generate information containing 2 bits of HARQ-ACK and SR. The generated information may be included in PUCCH format 1 and transmitted to the terminal. In this case, HARQ-ACK bundling means that if both bits of the HARQ-ACK indicate ACK, the value is 1, and in the remaining cases, the value is set to 0.

[0252] Method 2: The SR and HARQ-ACK information may be determined differently depending on the transmitted PUCCH format. Specifically, PUCCH format 0 can transmit information using 12 CS (cyclic shift) values. If it is a positive SR, the terminal can transmit PUCCH format 0 with a CS value that has already been set (or is predetermined) from among the 12 CS values. If it is a negative SR, PUCCH format 1 for transmitting HARQ-ACK information may be transmitted directly to the base station. If it is a positive SR, the HARQ-ACK information and SR information may be transmitted in PUCCH format 0 with different CS values. Here, if it is a 1-bit HARQ-ACK, it may be as follows.

[0253] The difference between the CS value corresponding to NACK and the CS value corresponding to ACK may be 6. Here, determining both CS values ​​such that a difference of 6 occurs may be equivalent to determining the two CS values ​​that are furthest apart. Furthermore, the CS value corresponding to NACK may be a CS value that does not overlap with HARQ-ACK and is used to transmit only Positive SR.

[0254] If it is a 2-bit HARQ-ACK, then the following is sufficient.

[0255] The CS values ​​corresponding to NACK, NACK, NACK, ACK, ACK, and ACK, respectively, may have a difference of 3. Here, determining four CS values ​​such that there is a difference of 3 is equivalent to determining the four CS values ​​that are evenly separated.

[0256] Furthermore, of the four CS values, the 2-bit HARQ-ACK corresponding to two adjacent CS values ​​may differ by a maximum of 1 bit, and the CS values ​​corresponding to NACK, NACK may not overlap with the HARQ-ACK and may be CS values ​​used to transmit only Positive SRs. The base station first determines the PUCCH format transmitted on the uplink from PUCCH format 0 and PUCCH format 1. If it is determined that PUCCH format 0 has been transmitted, it can be recognized that a Positive SR has been transmitted, and if it is determined that PUCCH format 1 has been transmitted, it can be recognized that a Negative SR has been transmitted. In other words, the type of SR may be recognized by the transmitted PUCCH format. After that, the HARQ-ACK information may be determined. For example, if PUCCH format 1 is transmitted, the HARQ-ACK information may be determined by decoding PUCCH format 1, and if PUCCH format 0 is transmitted, the HARQ-ACK information may be determined using the CS value of PUCCH format 0.

[0257] Another problem that this invention aims to solve is the situation in which a high-priority SR and a low-priority PUSCH overlap in at least one symbol. NR Rel-15 defines the following behavior: If a PUSCH is scheduled on an SR occasion (a symbol that can be transmitted in the case of a positive SR), the terminal transmits the PUSCH and not the SR. This is because the terminal has already transmitted information with the PUSCH, and therefore does not need to transmit an SR requesting information transmission on other uplinks. However, as mentioned above, if the SR has high priority, an SR transmission is necessary for other high-priority uplink transmissions other than the PUSCH that has already been scheduled to be transmitted. Therefore, the following method is proposed.

[0258] Some of the scheduled PUSCH resources may be reserved for SR transmission. PUSCH then does not use these resources for SR transmission, instead performing rate matching or puncturing. The resources for SR transmission may be determined as follows:

[0259] First, resources for SR transmission may be reserved with the same symbols as the SR opportunity. For example, if the resources for SR transmission are located at even-numbered symbols in the slot, some of the resources in the PUSCH at even-numbered symbols may be reserved as resources for SR transmission. That is, resources for SR transmission may be reserved in the PUSCH using the period of the SR opportunity. Resources for SR transmission may be reserved in the PUSCH with the same period as the SR opportunity. In addition, some of the resources in the PUSCH with the same number of symbols as the number of symbols in the SR opportunity may be reserved as resources for SR transmission.

[0260] In the case of a positive SR, the resources for SR transmission may be used to send an SR with the same PUCCH format as those transmitted on the SR opportunity. If a resource reserved for SR transmission overlaps with a resource used as the DMRS for PUCCH, the resource reserved for SR transmission may be dropped. In other words, this resource does not need to be reserved for SR transmission.

[0261] In yet another embodiment, the terminal may transmit DMRS with symbols other than those for the resource to transmit SR, and the PRB for the resource reserved for SR transmission may be the PRB located on the terminal side of PUSCH. For example, the PRB with the lowest index or the PRB with the highest index may be used. In yet another embodiment, the PRB for the resource reserved for SR transmission may be the PRB closest to the SR opportunity.

[0262] In yet another embodiment of the present invention, when a terminal reports to a base station that a resource to which a PUCCH is mapped overlaps or collides with another PUCCH's resource, the UCIs of each PUCCH can be multiplexed or transmitted using a new PUCCH resource. That is, a method is proposed for selecting a new PUCCH resource when the UCI contains time-sensitive information.

[0263] Method 1: If resources for sending PUCCH overlap or conflict, the terminal can select a PUCCH resource for sending UCI in one slot in the following way: As a first step, the terminal excludes PUCCH resources configured in that slot that map to symbols after the last symbol of a resource mapped to a PUCCH for sending URLLC UCI (or a UCI with higher priority). In other words, PUCCH resources ending after a URLLC UCI may be excluded.

[0264] After that, in two steps, the terminal sequentially checks whether UCI (or UCI with high priority) of URLLC can be transmitted on PUCCH resources in a series of orders among symbols at the same position as the last symbol of the PUCCH resource for transmitting UCI or PUCCH resources whose previous symbol is the last symbol. At this time, the series of orders may be determined based on the number of REs included in each PUCCH, the modulation order, and / or the code rate.

[0265] Specifically, the series of orders may be determined in ascending order of the value obtained by multiplying the number of REs, the modulation order, and the code rate. Whether UCI can be transmitted on the PUCCH resource may be determined to be possible when the length of the UCI to be transmitted is smaller than the size of the bits that can be transmitted via the PUCCH.

[0266] The PUCCH resource for transmitting UCI in one slot may be selected except for the PUCCH resources that do not satisfy the processing timeline. Through such a process, the terminal can select one PUCCH resource for transmitting UCI.

[0267] Method 2: When the resources for transmitting PUCCH overlap or collide, the terminal can select the PUCCH resource for transmitting UCI in one slot by the following method. As the first step, the terminal selects the symbol located at the forefront among the last symbols of the PUCCH resources configured in the slot. As the second step, the terminal selects the PUCCH resource corresponding to the symbol selected in the first step. If there are two or more PUCCH resources corresponding to the selected symbol, the PUCCH resources may be arranged in a series of orders. At this time, the series of orders may be determined in the same way as in method 1. Then, the PUCCH resource for transmitting UCI may be selected from the PUCCH resources arranged according to the series of orders.

[0268] In the PUCCH resources selected in the first stage and the second stage, the terminal can transmit UCI. If the terminal cannot transmit UCI using the selected PUCCH resource (for example, when the selected PUCCH resource exceeds the code rate, does not meet the processing time of the terminal, or does not meet the delay condition of UCI), the terminal can select one PUCCH resource from the remaining PUCCH resources other than the said PUCCH resource according to the first stage and the second stage. Through such a stage, the terminal can select one PUCCH resource for transmitting UCI.

[0269] Method 3: The terminal can select a PUCCH resource for multiplexing the remaining UCI other than the URLLC UCI (or the UCI with a higher priority) to transmit UCI.

[0270] Method 3 uses the Rel-15 method. The Rel-15 method is a method of arranging PUCCH resources in ascending order based on the value obtained by multiplying the number of REs, the modulation order, and / or the code rate among the PUCCH resources overlapping in the time domain, and sequentially determining whether UCI can be transmitted.

[0271] Thus, the first PUCCH resource for multiplexing and transmitting the remaining UCIs other than the URLLC UCI (or the higher-priority UCI) and the second PUCCH on which the URLLC UCI (or the higher-priority UCI) is transmitted may be multiplexed as follows. First, if the first PUCCH resource finishes earlier than the second PUCCH resource, or finishes at the same time (for example, if the last symbol of the first PUCCH resource is the same as or a previous symbol of the last symbol of the second PUCCH resource), and the URLLC UCI of the second PUCCH resource can be multiplexed into the first PUCCH resource, then the terminal can multiplex the URLLC and the UCI of the first PUCCH resource and transmit everything using the first PUCCH resource. In this case, the first PUCCH resource must satisfy the processing time required to transmit the URLLC UCI. Otherwise, it will be impossible to multiplex the URLLC UCI with the UCI of the first resource.

[0272] If the first PUCCH resource finishes later than the second PUCCH resource (for example, if the last symbol of the first PUCCH resource is located after the last symbol of the second PUCCH resource), and the UCI cannot be multiplexed into the first PUCCH resource, the terminal may choose not to send the first PUCCH resource and instead send the URLLC resource using the second PUCCH resource.

[0273] The method proposed in this invention is for transmitting an SR and a HARQ-ACK when a PUCCH scheduled to transmit a HARQ-ACK in two symbols of PUCCH format 0 overlaps with two PUCCHs for transmitting an SR. Here, the format of the PUCCH transmitting the SR may include PUCCH format 0. In Rel-15 NR, when one PUCCH transmitting an SR and a PUCCH format 0 for transmitting a HARQ-ACK overlap in time, the SR and UCI can be transmitted using the method described below.

[0274] If a HARQ-ACK is sent with one bit of PUCCH, and the PUCCH that sends the SR coincides with the PUCCH used to send the HARQ-ACK, then if the SR is a negative SR, the HARQ-ACK can send either 0 (NACK) or 6 (ACK) as its CS (cyclic shift) value.

[0275] If the PUCCH transmitting an SR coincides with the PUCCH transmitting a HARQ-ACK, and the SR is a positive SR, the terminal can send either 3 (NACK + positive SR) or 9 (ACK + positive SR) as a CS value to the base station. In other words, if a positive SR and a HARQ-ACK coincide, the terminal can send the CS value that would be used when a negative SR coincides with a HARQ-ACK plus 3.

[0276] If a HARQ-ACK is transmitted using the 2 bits of PUCCH, and the PUCCH transmitting the SR coincides with the PUCCH used to transmit the HARQ-ACK, then the HARQ-ACK may transmit one of the following values ​​as its CS value: 0 (NACK,NACK), 3 (NACK,ACK), 6 (ACK,ACK), and / or 9 (ACK,NACK). If the SR coincides with the HARQ-ACK and is a positive SR, the UCI can be transmitted using the CS value. For example, one of the following values ​​may be transmitted as the CS value: 1 (NACK,NACK,positive SR), 4 (NACK,ACK,positive SR), 7 (ACK,ACK,positive SR), and / or 10 (ACK,NACK,positive SR), and the transmitted CS value allows recognition of the HARQ-ACK and SR. In this case, if it coincides with a positive SR, the CS value of the positive SR may be the CS value in the case of a negative SR plus 1.

[0277] Rel-15 NR does not consider situations where PUCCH format 0 for sending two or more SRs and HARQ-ACKs overlap in the time domain. However, to provide URLLC services in Rel-16, it is necessary to set up SRs with shorter periods on the uplink. Therefore, when PUCCH format 0 for sending HARQ-ACKs consists of two symbols, it may overlap with a PUCCH sending two SRs. In this case, a method is needed to send two SRs and HARQ-ACKs.

[0278] Method 1: One of the two SRs may be transmitted along with the HARQ-ACK, and the other SR may be dropped without being transmitted. Then, as in the method used in Rel-15, one SR and the HARQ-ACK may be transmitted using the CS value. The SR that is transmitted along with the HARQ-ACK may be determined by the following three methods.

[0279] 1) The SR ID may be used to determine which SRs are sent with the HARQ-ACK and which are dropped without being sent. For example, SRs with a low ID may be determined to always be sent, or SRs with a high ID may be determined to always be sent.

[0280] 2) The SR to be transmitted may be determined using time domain allocation information. For example, among two PUCCHs that transmit two SRs, the PUCCH located earlier in the time domain may be determined to be the SR that is always transmitted. Conversely, among two PUCCHs that transmit two SRs, the SR for the PUCCH located later in the time domain may be determined to be the SR that is always transmitted.

[0281] 3) The priority of the SRs may determine which SRs are to be transmitted. The priority of the SRs may be set by a higher layer (e.g., RRC signaling). The terminal can determine that the SRs that always have a high priority are the SRs that are always transmitted.

[0282] Method 2: The two SRs and HARQ-ACKs may be transmitted separated by the CS. When the HARQ-ACK is 2 bits, the two SRs and HARQ-ACKs may be transmitted by the CS in the following manner. Here, a HARQ-ACK value of 0 means NACK, and 1 means ACK.

[0283] The first and second SRs may be determined by 1) ascending order of SR IDs, 2) ascending order of PUCCH symbols on which the SRs are sent, or 3) ascending order of SR priority. That is, if the first of the two SRs is positive, a CS value equal to the CS value for sending a negative SR plus 1 is sent, similar to the method described above for sending an SR and a 2-bit HARQ-ACK in Rel-15. If the second SR is positive, a CS value equal to the CS value for sending a negative SR plus 2 is sent.

[0284] Table 4 below shows an example of CS values ​​using SR and HARQ-ACK.

[0285] [Table 4]

[0286] When the HARQ-ACK is 1 bit, the two SRs and the 1-bit HARQ-ACK may be transmitted using a CS value determined by whether the SRs are positive or negative. For example, if the first of the two SRs is positive, a value equal to 3 plus the CS value for transmitting a negative SR may be transmitted, similar to the method used to transmit an SR and a 1-bit HARQ-ACK in Rel-15. If the second SR is positive, a value equal to 4 plus the CS value for transmitting a negative SR may be transmitted.

[0287] Table 5 below shows an example of CS values ​​using SR and HARQ-ACK.

[0288]

Table 5

[0289] By such a method, even when respective PUCCHs for transmitting SR and HARQ-ACK overlap, the information of HARQ-ACK and SR can be transmitted to the terminal using the value of CS, and the terminal can recognize whether HARQ-ACK is ACK or NACK and whether SR is positive or negative based on the received value of SR.

[0290] <Proposal 3: Transmit PUSCH only in valid symbols excluding specific symbols that are not valid for resource of repeated transmission of PUSCH>

[0291] FIGS. 19 to 22 are diagrams showing an example of a slot format for PUSCH repeated transmission according to an embodiment of the present invention.

[0292] FIG. 19 is a diagram showing an example of resources allocated for repeated transmission of PUSCH.

[0293] Referring to FIG. 19, resources for repeated transmission of PUSCH may be allocated by transmitting a start symbol index and the length of the allocated resources from the base station.

[0294] Specifically, the base station transmits time-domain resource allocation information to the terminal for the first PUSCH repetition for repeated transmission of PUSCH. The resource allocation information may include the start symbol index S, the symbol length L, and the number of repetitions K. Based on the received resource allocation information, the terminal determines the symbol for repeated transmission of PUSCH. Here, the next PUSCH repetition may be transmitted immediately after the first PUSCH repetition using the symbol immediately following it. That is, in Figure 19, the first PUSCH repetition (repetition #0) for repeated transmission of PUSCH may be determined based on the resource allocation information, and the second PUSCH repetition (repetition #1) for repeated transmission may be determined using the symbol immediately following it.

[0295] If a PUSCH repeatation for repeated PUSCH transmission exceeds the slot boundary, the PUSCH repeatation may be split based on the slot boundary.

[0296] Furthermore, if a PUSCH repetition overlaps with a downlink symbol or SS / PBCH block set by a semi-static uplink / downlink configuration (semi-static UL / DL configuration), the PUSCH repetition can be transmitted using a symbol that does not overlap with the downlink symbol. In addition, the terminal can also exclude flexible symbols immediately following a downlink symbol set by the uplink / downlink configuration from the PUSCH repetition.

[0297] For example, as shown in Figure 19, if the resource allocation information transmitted from the base station indicates that the index of the start symbol of the first PUSCH repetition is 4, its length is 4, and the number of repetitions is 5, then the third PUSCH repetition (repetition #2) will cross the slot boundary, and therefore the PUSCH repetitions will be separated based on the slot boundary.

[0298] Such a method has the drawback that when push repetitions are divided at slot boundaries, the number of symbols in a single push repetition becomes excessively small. In one embodiment of the present invention to solve this, if a push repetition consists of only one symbol, the terminal does not need to transmit that push repetition. This is because if a push repetition consists of only one symbol, it is not possible to transmit data other than DMRS with that symbol. Furthermore, if the number of symbols transmitted by a push repetition is less than or equal to the number of DMRS symbols that must be transmitted by the push repetition, the terminal does not need to transmit that push repetition.

[0299] Figure 20 shows yet another example of resources allocated for repeated transmission of PUSCH.

[0300] Referring to Figure 20, the resources for repeated transmission of PUSCH may be configured differently depending on the slot boundary.

[0301] Specifically, the base station transmits time-domain resource allocation information for repeated transmission of PUSCH to the terminal. The resource allocation information may include the starting symbol index S, the symbol length L, and the number of repetitions K. The terminal checks whether L*K symbols from the starting symbol have crossed the slot boundary. If L*K symbols have not crossed the slot boundary, the first PUSCH repetition consists of L symbols starting from the starting symbol, and the subsequent K-1 PUSCH repetitions can start consecutively from the symbol immediately following the first PUSCH repetition and occupy L symbols.

[0302] When L*K symbols cross a slot boundary starting from the start symbol, the terminal can divide the L*K symbols based on the slot boundary. For example, as shown in Figure 20, if the index of the start symbol of a PUSCH is 4, the length is 4, and the number of repeat transmissions is 5, and this is given to the terminal by the time-domain resource allocation information, then 20 symbols will cross the slot boundary starting from index 4 of the start symbol, so the terminal can divide the 20 symbols based on the slot boundary. Therefore, in Figure 20, two PUSCH repetitions may be transmitted.

[0303] Figure 21 shows yet another example of resources allocated for repeated transmission of PUSCH.

[0304] Referring to Figure 21, if a resource allocated for repeated transmission includes a slot boundary, PUSCH does not need to be sent from that resource.

[0305] Specifically, the base station transmits time-domain resource allocation information for repeated transmission of PUSCH to the terminal. The resource allocation information may include a starting symbol index S, a symbol length L, and a repetition count K. Based on the resource allocation information, the terminal determines the symbol on which a PUSCH repetition will be transmitted. That is, as shown in Figure 21, the first PUSCH repetition (repetition #0) may be determined based on the starting symbol index and symbol length included in the resource allocation information. Subsequently, the next PUSCH repetition may be transmitted consecutively from the symbol immediately following the first PUSCH repetition.

[0306] However, after the second PUSCH repetition (repetition #1), there are only two symbols in the slot, so two more symbols must be allocated in the next slot, crossing the slot boundary. In other words, due to the slot boundary, two symbols are allocated in the first slot, and two more symbols are needed in the second slot. In this case, the terminal does not send a PUSCH with the last two symbols in the previous slot and the first two symbols in the next slot, and can repeat the PUSCH again in the third PUSCH repetition (repetition #2) allocated with the subsequent symbols. That is, in Figure 21, the last two symbols in the first slot and the first two symbols in the second slot (which would have been sent as the third PUSCH repetition if transmission at the slot boundary had been possible) are not sent because they overlap with the slot boundary.

[0307] Furthermore, if a PUSCH repetition overlaps with a downlink symbol or SS / PBCH block set by a semi-static uplink / downlink configuration (semi-static UL / DL configuration), the PUSCH repetition can be transmitted using a symbol that does not overlap with the downlink symbol. In addition, the terminal can also exclude flexible symbols immediately following a downlink symbol set by the uplink / downlink configuration from the PUSCH repetition.

[0308] Figure 22 shows yet another example of resources allocated for repeated transmission of PUSCH.

[0309] Referring to Figure 22, if the resources allocated for repeated transmission include a slot boundary, symbols located at the slot boundary may be included in previous and subsequent PUSCH repetitions.

[0310] Specifically, the base station transmits time-domain resource allocation information for repeated transmission of PUSCH to the terminal. The resource allocation information may include the start symbol index S, the symbol length L, and the number of repetitions K. Based on the resource allocation information, the terminal determines the symbol on which the PUSCH repetition will be transmitted for repeated transmission of PUSCH.

[0311] Here, the next PUSCH repetition is sent immediately after the first PUSCH repetition (repetition #0) using the next symbol. If the symbols assigned to a single PUSCH repetition cross a slot boundary, the terminal can split the symbols assigned to that PUSCH repetition based on the slot boundary and include the split symbols in adjacent PUSCH repetitions within the same slot. If there are no adjacent PUSCH repetitions within the same slot, the terminal can send PUSCH repetitions using these symbols.

[0312] For example, as shown in Figure 22, the symbols assigned to the third PUSCH repetition cross a slot boundary. The slot boundary can divide the symbols into two groups of two; the last two symbols in the first slot may be included in the previous PUSCH repetition (repetition #1), and the first two symbols in the second slot may be included in the later PUSCH repetition (repetition #2).

[0313] In Figures 19-22, when determining the PUSCH repetition for repeated transmission of PUSCH, the downlink symbol and / or SS / PBCH block set by the semi-static downlink / uplink configuration of the cell from which the PUSCH repetition is transmitted is used. Furthermore, the terminal uses the following symbols and symbols for PUSCH repetition. If they overlap, the symbol may be considered identical to the downlink symbol and / or the symbol that overlaps with the SS / PBCH block set by the semi-static downlink / uplink configuration of the cell to which the PUSCH repetition is transmitted.

[0314] In other words, if the resources allocated for PUSCH repetition overlap with a specific symbol, that symbol is recognized as not being a valid symbol, and PUSCH repetition can only be transmitted with valid symbols. At this time, the resources allocated by the base station are called nominal PUSCH repetition, and the resources that effectively allow repeated transmission of PUSCH after excluding invalid symbols from the nominal PUSCH repetition are called actual PUSCH repetition.

[0315] 1) Symbols for receiving semi-static downlink symbols (DL symbols) and SS / PBCH blocks.

[0316] If a symbol assigned by resource allocation information for sending a push repetition by the base station overlaps with a downlink symbol set by a semi-static uplink / downlink configuration, the terminal recognizes the overlapping symbol as invalid and can send the push repetition with a symbol that does not overlap with the downlink symbol set by the semi-static uplink / downlink configuration. In addition, symbols following a downlink symbol indicated by a semi-static uplink / downlink configuration (for example, a flexible symbol) may also be recognized as invalid symbols.

[0317] For example, a symbol designated as a downlink by higher-layer signaling (e.g., RRC configuration) may be considered an invalid symbol for PUSCH repetition. Furthermore, at least one symbol following the last symbol designated as a downlink may be considered an invalid symbol. In this case, at least one symbol may be a gap symbol for changing the transmission direction from downlink to uplink.

[0318] Furthermore, symbols that overlap with symbols used to receive SS / PBCH blocks may also be recognized as invalid symbols. For example, a symbol instructed by system information or configuration information to receive an SS / PBCH block may be considered an invalid symbol for PUSCH repetition.

[0319] 2) Symbols that overlap with CORESET#0

[0320] Symbols that overlap with CORESET#0, as indicated by the PBCH, are deemed invalid symbols, and the terminal cannot repeatedly transmit PUSCH signals using symbols that overlap with CORESET#0, even if those symbols were assigned by the base station for PUSCH transmissions. Here, CORESET#0, as indicated by the PBCH, should be used for the terminal's initial cell connection. Therefore, symbols constituting CORESET#0 must not be used for uplink channel or signal transmission. Accordingly, using resource allocation information transmitted by the base station, including the start index and length of the symbols transmitted by the terminal, the terminal can recognize the nominal PUSCH repeatation, which is the resource allocated for repeated PUSCH transmissions. Subsequently, the terminal can recognize and remove symbols associated with CORESET#0 from the nominal PUSCH repeatation as invalid symbols.

[0321] In other words, the symbol for CORESET#0, which is the resource set used for the initial connection procedure instructed by the resource information transmitted from the base station, may be recognized as an invalid symbol.

[0322] For example, for a specific type of PUSCH repetition (e.g., Type B), the terminal can determine symbols that are not valid for transmitting the PUSCH repetition. Specifically, symbols designated as a specific type of search space for detecting the PDCCH for initial connection in CORESET#0, which is the CORESET for initial connection, may be considered as symbols that are not valid for transmitting the PUSCH repetition.

[0323] Here, the parameters of the MIB (Master Information Block) or SIB (System Information Block) received by the PBCH may indicate a specific type of search space for detecting CORESET#0 and the PDCCH for initial connection.

[0324] At this time, the PDCCH monitored by CORESET#0 as instructed by PBCH may schedule a system information block and be scrambled by SI-RNTI.

[0325] In other words, symbols that overlap with CORESET#0 may be considered invalid symbols, along with symbols instructed for downlink transmission and symbols instructed for SS / PBCH block reception by the semi-static downlink / uplink settings of the cell from which the PUSCH repetition is transmitted, as explained in Figures 19 to 22.

[0326] 3) Downlink symbols of other cells

[0327] If a terminal has only half-duplex capability (i.e., a terminal that can only receive in one cell and not transmit in another), then if downlink channel and signal reception is indicated or configured in another cell, the uplink signal cannot be transmitted to the base station using a symbol that overlaps with the symbol for downlink channel and signal reception. Therefore, a terminal that only supports half-duplex capability will recognize a symbol configured for push repetition as invalid and will not use it for push repetition transmission if that symbol is configured (or indicated) as a downlink symbol in another cell.

[0328] For example, symbols that overlap with symbols set as downlink symbols by a Pcell's semi-static downlink / uplink configuration are invalid symbols that cannot be used for transmitting PUSCH repetitions. Here, a Pcell (or primary cell) is a single cell in a carrier aggregation where multiple cells are configured at a terminal. Among multiple cells, the cell with the lowest index can be called a Pcell (or primary cell).

[0329] For example, if a terminal meets the following conditions and supports only half-duplex operation, and the symbol assigned by resource allocation information transmitted from the base station for PUSCH repetition overlaps with the symbol instructed for receiving SS / PBCH blocks in other cells, the terminal may consider that symbol to be invalid.

[0330] Furthermore, symbols that overlap with symbols designated as downlinks by the layer configuration information in a single cell, or symbols set for receiving downlink channels and signals in a single cell (e.g., CSI-RS, PDCCH, or PDSCH), may be considered symbols that are not valid for transmitting PUSCH repetitions.

[0331] Alternatively, at least one of the symbols configured to receive SS / PBCH blocks of the serving cell to which the terminal is attempting to send a PUSCH, or the symbols configured to monitor the PDCCH with CORESET #0 as directed by the PBCH, may be considered an invalid symbol for sending a PUSCH repeatation.

[0332] 4) Symbols set by RRC

[0333] The terminal does not need to send PUSCH repetitions for symbols that are set to be invalid for sending PUSCH repetitions by higher-layer parameters.

[0334] The base station can use parameters from higher-layer signals to set pattern information of invalid symbols for PUCCH repetition in bitmap format on the terminal. Each bit in the bitmap pattern indicates the validity of each symbol. For example, if a bit value in the bitmap is 1, the symbol corresponding to that bit value means that it is an invalid symbol.

[0335] The invalid symbol pattern information set by the upper layer may be applied by an indicator included in the DCI transmitted by the PDCCH. That is, the DCI may include an indicator that shows whether or not the invalid symbol pattern information set by the upper layer signal is applied, and the terminal may apply the symbol pattern information set by the upper layer signal based on the value of the indicator received via the DCI.

[0336] For example, if the indicator value transmitted via DCI is 1, the terminal can apply pattern information for invalid symbols and recognize the symbols corresponding to each bit in the pattern information bitmap as invalid symbols for transmitting PUSCH repetitions. The terminal can then transmit PUSCH repetitions using the remaining symbols, excluding the symbols invalid due to the pattern information, from the symbols allocated for PUSCH repetitions.

[0337] 5) At least G symbols following a symbol that falls under any one of 1) to 4)

[0338] G symbols located after the last symbol of a symbol that falls under categories 1) to 4) above and is considered an invalid symbol may be recognized as invalid symbols. For example, at least one of the semi-static DL symbol and the G symbols after the last symbol of the symbol for receiving the SS / PBCH block as described in 1), the G symbols after the last symbol of the symbol for monitoring the PDCCH with CORESET#0 instructed by the PBCH as described in 2), the G symbols after the last symbol of the downlink symbol of another cell when the terminal supports only half-duplex operation as described in 3), and the G (G is an integer) symbols after the last symbol of a symbol set as an invalid symbol by the RRC as described in 4) may be considered an invalid symbol for transmitting a PUSCH repeat.

[0339] In this case, symbols 2) to 5) may be determined from among the remaining symbols other than those described in at least 1). That is, symbols 2) to 5) may be determined from among all symbols if there is no semi-static downlink / uplink configuration, or if the symbols are set as flexible symbols and / or uplink symbols by the semi-static downlink / uplink configuration of the cell to which the PUSCH repetition is sent. This is because the symbols determined in 1) and the symbols determined in 2) to 5) will not overlap.

[0340] As mentioned above, symbols that are unavailable for sending PUSCH repetitions may include at least one of the following symbols:

[0341] 1) Symbols for receiving semi-static downlink symbols (DL symbols) and SS / PBCH blocks.

[0342] 2) Symbols that overlap with CORESET#0

[0343] 3) Downlink symbols of other cells

[0344] 4) Symbols that have been set as invalid by RRC

[0345] 5) At least G symbols after the last symbol of the symbols corresponding to 1) to 4)

[0346] The terminal can repeatedly transmit PUSCH using the effective PUSCH repeat resource, which is the resource obtained by removing the invalid symbols mentioned above from the nominal PUSCH repeat resource, which is the resource allocated in the base station's resource allocation information for PUSCH repeat.

[0347] The five types of symbols described in 1) to 5) may be symbols assigned by the base station for repeated transmission of PUSCH, but they cannot be used for transmitting PUSCH, and may be distinguished as follows depending on whether the base station is scheduling / transmitting. Hereafter, symbols corresponding to 1) to 5) will be defined as the set of invalid symbols.

[0348] An invalid symbol set of type 1 is a set of symbols that cannot be transmitted via the uplink by the terminal.

[0349] For example, a first type invalid symbol set may be a symbol set composed of some of the symbols described in 1) that are included in the invalid symbol set. Among the symbols that fall under 1), since it is a downlink symbol set by a semi-static downlink / uplink configuration, the terminal cannot transmit uplink using that downlink symbol.

[0350] Alternatively, the first type of invalid symbol set may be a symbol set composed of some of the symbols described in 1) that are included in the invalid symbol set. Among the symbols that fall under 1), the symbols for receiving SS / PBCH blocks may be included in the first type of invalid symbol set. Since the base station uses the symbols for receiving SS / PBCH blocks for downlink transmission, the terminal must receive SS / PBCH blocks with these symbols. For this reason, the terminal cannot perform uplink transmission with these symbols.

[0351] Alternatively, the first type of invalid symbol set may be a symbol set composed of symbols that fall under 3) among the symbols included in the invalid symbol set. Since the symbols that fall under 3) are used to receive the downlink symbol of a single cell when the terminal supports only half-duplex operation, a terminal that supports only half-duplex operation cannot perform uplink transmission with such symbols.

[0352] Alternatively, the first type of invalid symbol set may be a symbol set consisting of at least one symbol from among the symbols included in the invalid symbol set that falls under 1) or 3). That is, at least one symbol from among the semi-static DL symbol and the symbol for receiving SS / PBCH blocks as described in 1), and / or the symbol for transmitting the downlink signal of a reference cell when the terminal as described in 3) supports only half-duplex operation, may be included in the first type of invalid symbol set. That is, the first type of invalid symbol set may consist of all the symbols that fall under 1) and 3), or it may consist of only some of the symbols that fall under 1) and 3).

[0353] The second type of invalid symbol set is a set of symbols for which uplink transmission by the terminal is not necessarily impossible (i.e., symbols for which uplink transmission is possible depending on the circumstances).

[0354] For example, the second type of invalid symbol set may be a symbol set composed of symbols that fall under category 2) of the aforementioned invalid symbols. The symbols that fall under category 2) above refer to symbols for monitoring PDCCH in CORESET#0 as instructed by PBCH. The base station may or may not transmit PDCCH in CORESET#0. Therefore, if the base station does not transmit PDCCH with the symbol, the terminal can transmit an uplink signal with a symbol for monitoring PDCCH.

[0355] Furthermore, when a PDCCH is detected, the terminal can send an uplink signal to symbols after the symbol in which the PDCCH was detected, among the symbols used to monitor the PDCCH. Therefore, the terminal may be able to repeatedly transmit PUSCH using those symbols.

[0356] In this case, as mentioned above, the symbols corresponding to symbols 1) to 5) for receiving the SS / PBCH block mean symbols other than those set as downlink symbols by the semi-static downlink / uplink configuration of the cell from which the PUSCH repetition is transmitted in 1).

[0357] Furthermore, the second type of invalid symbol set may be a symbol set composed of the invalid symbols described above that fall under category 5). The symbols that fall under category 5) mean at least G symbols located after the last symbol of the symbols that fall under categories 1) to 4).

[0358] The symbol corresponding to 5) is used for switching from downlink reception to uplink transmission (RX-to-TX switching) after the terminal receives a signal transmitted by the symbols corresponding to 1) to 4) for uplink transmission. However, since the terminal does not always receive a downlink channel or signal with the symbols corresponding to 1) to 4), if a downlink channel or signal is not received, the symbol for switching from downlink reception to uplink transmission may not be necessary.

[0359] For example, in 1) a symbol set as a downlink symbol by a semi-static downlink / uplink configuration, the downlink signal is transmitted and received only when the downlink channel / signal is scheduled or set, so it is not a symbol that always transmits a downlink signal. Also, in 1) the SS / PBCH block is transmitted by the base station, but the terminal may, in certain cases, skip or bypass the SS / PBCH block without receiving it. In the case of 2), the symbol for monitoring the PDCCH with CORESET#0 indicated by the PBCH may or may not transmit the PDCCH with the monitoring symbol. Therefore, the terminal may, in special cases, skip or bypass the PDCCH without receiving it with that symbol. Also, in 3) when the terminal supports only half-duplex operation, even if a downlink signal is transmitted in one cell, the terminal may, in certain cases, skip or bypass the transmitted signal without receiving it. Furthermore, in case 4), since the symbol is set as invalid by the base station, the pattern information of the invalid symbol does not need to be applied in the DCI indicator by the higher layer signal, and a downlink signal does not need to be transmitted with that symbol. Therefore, in such cases, a symbol for RX-to-TX switching is unnecessary, and the terminal may be able to transmit uplink signals with that symbol.

[0360] Alternatively, a second type of invalid symbol set may be a symbol set consisting of at least one symbol from among the symbols included in the invalid symbol set that falls under categories 2) to 5). That is, a second type of invalid symbol set may consist of all symbols that fall under categories 2) to 5), or it may consist of only some of the symbols that fall under categories 2) to 5).

[0361] The first type of invalid symbol set and the second type of invalid symbol set do not contain any overlapping symbols, and the union of the two symbol sets may be identical to the set of all invalid symbols. That is, the second type of invalid symbol set can contain only the remaining symbols other than those included in the first type of invalid symbol set.

[0362] Preferably, the first type of invalid symbol set may consist of symbols from the invalid symbol set that fall under 1) and 3), and the second type of invalid symbol set may include only the remaining symbols from the invalid symbol set, excluding the symbols that fall under the first type.

[0363] A base station can schedule a PUSCH repetition for repeated transmission of PUSCH to a terminal. Here, the PDCCH (or DCI) that schedules the PUSCH repetition may include the index and length of the starting symbol of the first nominal PUSCH repetition, and may further include the number of repetitions for which the PUSCH repetition will be repeatedly transmitted. A terminal can receive the PDCCH (or DCI) and, based on the starting symbol index and length of the received PDCCH (or DCI), can obtain information about the symbol for which the first nominal PUSCH repetition was scheduled and the number of repetitions of the PUSCH repetition.

[0364] The terminal can determine the symbol on which the second nominal PUSCH repetition of length L is scheduled immediately after the symbol on which the first nominal PUSCH repetition is scheduled, where length L is the same as the length of the first nominal PUSCH repetition. Subsequently, the terminal may determine the symbol on which the third nominal PUSCH repetition of length L is scheduled immediately after the symbol on which the second nominal PUSCH repetition is scheduled. This process may be repeated until the symbol on which the corresponding PUSCH repetition is scheduled is determined, based on the number of repetitions of the PUSCH repetition obtained from PDCCH (or DCI).

[0365] The terminal determines whether the symbols scheduled as the determined nominal PUSCH repetitions overlap with symbols included in the set of invalid symbols, recognizes the overlapping symbols as invalid symbols, and excludes them from the scheduled symbols. In other words, the terminal does not transmit PUSCH repetitions with symbols that overlap with invalid symbols. The terminal can then determine the actual PUSCH repetitions for transmitting PUSCH by collecting consecutive symbols from the remaining symbols other than the overlapping symbols that do not cross slot boundaries.

[0366] Some symbols belonging to an invalid symbol set may be used for PUSCH repeatation transmissions in specific situations, but may also be excluded from PUSCH repeatation transmissions at all times. For example, among the symbols 1) to 5) that belong to the aforementioned invalid symbol sets, symbols for which uplink transmission is always impossible (symbols included in the first type of invalid symbol set) are preferably excluded in the process of determining the actual PUSCH repeat for PUSCH transmission. However, symbols for which uplink transmission is not necessarily impossible under certain conditions (symbols included in the second type of invalid symbol set) are preferably selectively excluded in the process of determining the actual PUSCH repeat.

[0367] In a first embodiment of the present invention, if a symbol on which the first determined nominal PUSCH repetition is scheduled overlaps with a symbol included in a first type of invalid symbol set, the terminal excludes that symbol from the symbols on which the nominal PUSCH repetition is scheduled. However, symbols that overlap with symbols included in a second type of invalid symbol set are not excluded from the symbols on which the first nominal PUSCH repetition is scheduled. That is, the terminal does not transmit nominal PUSCH repetitions only for symbols that overlap with the first type of invalid symbol set. The terminal can then determine the actual PUSCH repetitions on which PUSCH is actually transmitted by collecting consecutive symbols from the remaining symbols other than those that overlap with the first type of invalid symbols, that do not cross slot boundaries.

[0368] The terminal excludes symbols from which nominal PUSCH repetitions are scheduled after the first determined nominal PUSCH repetition if those symbols are included in the first type of invalid symbol set or overlap with the second type of invalid symbol set. In other words, the terminal does not transmit nominal PUSCH repetitions for symbols that overlap with the first type of invalid symbol set or symbols that overlap with the second type of invalid symbol set. The terminal can then determine the effective PUSCH repetitions by collecting consecutive symbols that do not cross slot boundaries from the remaining symbols other than those that overlap with the first and second type of invalid symbol sets.

[0369] When a base station schedules a push repetition to a terminal, it specifies the symbol assigned to the first nominal push repetition, and subsequent nominal push repetitions are determined by symbols after the first nominal push repetition. Therefore, the base station can specify the symbol to which the first nominal push repetition is transmitted using PDCCH (or DCI). If a symbol included in the second type of invalid symbol set cannot be used for the first nominal push repetition, the base station can specify the first nominal push repetition with a symbol other than those included in the second type of invalid symbol set. Conversely, the base station can schedule the first nominal push repetition with a symbol included in the second type of invalid symbol set. In this case, a symbol included in the second type of invalid symbol set would likely be available for the first nominal push repetition.

[0370] Figures 23 and 24 show yet another example of a symbol that cannot be repeatedly transmitted via PUSCH according to one embodiment of the present invention.

[0371] Figure 23 shows an example of excluding invalid symbols from symbols assigned for repeated transmission of PUSCH, as one embodiment of the present invention.

[0372] Referring to Figure 23, from the aforementioned set of invalid symbols, symbols corresponding to 1) that are set as downlinks by a semi-static downlink / uplink configuration, and at least G symbols (assuming G=2 in this embodiment) for switching from downlink to uplink corresponding to 5) may be excluded as invalid symbols.

[0373] In this case, symbols corresponding to 1) may be included in the first type, and symbols corresponding to 5) may be included in the second type.

[0374] Referring to Figure 23(a), both Type 1 and Type 2 symbols may be considered invalid and excluded from nominal PUSCH repetitions, without distinction. That is, any symbol that overlaps with a symbol included in the invalid symbol set (the union of Type 1 and Type 2) may be excluded from a symbol to which any one nominal PUSCH repetition has been scheduled. For example, as shown in Figure 23(a), a terminal can receive a PDCCH (or DCI) from a base station to schedule a PUSCH repetition. In this case, the PDCCH (or DCI) may include at least one of the index value (S=5), length (L=5), and number of repetitions (K=3) of the starting symbol (first symbol) of the first nominal PUSCH repetition.

[0375] The first nominal PUSCH repeat (PUSCH rep#0) does not overlap with any invalid symbols of type 1 (i.e., semi-static downlink symbols), but it does overlap with symbols corresponding to 5) in type 2 (i.e., symbols with G=2 after the semi-static downlink symbol). Therefore, the terminal can determine that the remaining three consecutive symbols in the first nominal PUSCH repeat, excluding the two symbols corresponding to 5), are the actual PUSCH repeats to be transmitted.

[0376] The second nominal PUSCH repeat (PUSCH rep#1) has a final symbol that overlaps with a first-type downlink symbol (i.e., a semi-static downlink symbol). Therefore, the terminal can determine that the four consecutive symbols in the second nominal PUSCH repeat, excluding the one semi-static downlink symbol corresponding to the first type, are the actual PUSCH repeats being transmitted.

[0377] The third nominal PUSCH repeat (PUSCH rep#2) has two symbols that overlap with symbols included in the first type, and the third and fourth symbols that overlap with symbols corresponding to 5) of the second type. Therefore, the terminal can determine that the remaining single consecutive symbol in the third nominal PUSCH repeat, excluding the symbols corresponding to 1) and 5), is the actual PUSCH repeat that will be transmitted.

[0378] Referring to Figure 23(b), symbols included in the invalid symbol sets of Type 1 and Type 2 may be distinguished and excluded. That is, symbols that overlap with symbols included in the invalid symbol set (the union of Type 1 and Type 2) for which any one nominal PUSCH repetition is scheduled may be distinguished and excluded. In other words, among the symbols for which the first nominal PUSCH repetition is scheduled, symbols that overlap with symbols included in the invalid symbol set of Type 1 may be excluded from the symbols for which the first nominal PUSCH repetition is scheduled. However, among the symbols for which nominal PUSCH repetitions are scheduled after the first nominal PUSCH repetition, symbols that overlap with symbols included in the invalid symbol sets of Type 1 and Type 2 may be excluded from the symbols for which nominal PUSCH repetitions are scheduled after the first nominal PUSCH repetition.

[0379] For example, as shown in Figure 23(b), a terminal can receive a PDCCH (or DCI) from a base station to schedule a PUSCH repetition. In this case, the PDCCH (or DCI) may include at least one of the index value (S=5), length (L=5), and number of repetitions (K=3) of the starting symbol (first symbol) of the first nominal PUSCH repetition.

[0380] The first nominal PUSCH repeat (PUSCH rep#0) does not overlap with any invalid symbols of type 1 (i.e., semi-static downlink symbols), but it does overlap with symbols corresponding to 5) in type 2 (i.e., symbols with G=2 after the semi-static downlink symbol). In this case, only symbols corresponding to type 1 are excluded from the scheduled symbols, so symbols corresponding to 5) in type 2 (G=2) are not excluded. Therefore, the terminal can determine that the five consecutive symbols of the first nominal PUSCH repeat are the actual PUSCH repeats to be transmitted.

[0381] The second nominal PUSCH repeat (PUSCH rep#1) has a final symbol that overlaps with an invalid symbol of type 1 (i.e., a semi-static downlink symbol). Therefore, the terminal can determine that the four consecutive symbols in the second nominal PUSCH repeat, excluding the one semi-static downlink symbol corresponding to type 1, are the actual PUSCH repeats that are being transmitted.

[0382] The third nominal PUSCH repeatation (PUSCH rep#2) has two symbols that overlap with symbols included in the first type, and the third and fourth symbols that overlap with symbols corresponding to 5) of the second type. Therefore, the terminal can determine that the remaining consecutive symbols other than those corresponding to 1) and 5) in the third nominal PUSCH repeatation are the actual PUSCH repeatation that will be transmitted. In other words, in the third nominal PUSCH repeatation, unlike the second nominal PUSCH repeatation, the gap symbol corresponding to 5) may be selectively applied as an invalid symbol.

[0383] In a second embodiment of the present invention, among the symbols included in the second type of invalid symbol set, symbols that overlap with the symbols for which the first nominal PUSCH repetition is scheduled are used in the first nominal PUSCH repetition, and furthermore, the symbols used in nominal PUSCH repetitions after the first nominal PUSCH repetition may be determined by the result of the first nominal PUSCH repetition.

[0384] In other words, among the symbols included in the second type of invalid symbol set, those symbols scheduled and used in the first nominal PUSCH repetition may be considered symbols that will also be used in subsequent nominal PUSCH repetitions.

[0385] For example, the invalid symbol set of the second type may include symbols corresponding to 5) above. In this embodiment, the invalid symbols included in the second type will be explained by taking the G symbols after the last symbol of the semi-static downlink symbols as an example. If the first nominal PUSCH repetition is scheduled to overlap with some of the G symbols, the terminal can use the overlapping symbols from the G symbols without removing them from the symbols on which the nominal PUSCH repetition is scheduled to be transmitted. Subsequently, if the symbols assigned for the second nominal PUSCH repetition also overlap with some of the G symbols, the terminal must decide whether to remove or use the symbols from the G symbols that overlap with the second nominal PUSCH repetition.

[0386] In this case, the G symbols can represent symbols that can be used as RX-to-TX switching time for a terminal to receive a downlink channel signal scheduled / set to a semi-static downlink symbol and transmit an uplink channel / signal. Therefore, if some of the G symbols that overlap are used in the first nominal push repetition without being excluded from the first nominal push repetition, then similarly, the overlapping symbols of the G symbols may be used in the second nominal push repetition without being excluded.

[0387] Figure 24 shows yet another example of excluding invalid symbols from symbols assigned for repeated transmission of PUSCH, as one embodiment of the present invention.

[0388] Referring to Figure 24, the second embodiment applies, in which some symbols may be excluded in the PUSCH repetition. In Figure 24, the terminal receives a PDCCH (or DCI) scheduling a PUSCH repetition, which includes the index (S) 5, length (L) 3, and number of repetitions 2 of the first symbol of the first (nominal) PUSCH repetition. The first five symbols of the slot are symbols set as downlink symbols by the semi-static downlink / uplink setting, and the remaining symbols are symbols set as flexible or uplink. In Figure 24, we will take up and explain the symbols corresponding to 1) (symbols set as downlink symbols by the semi-static downlink / uplink setting) and 5) (at least G symbols after the last symbol of the symbols set as downlink symbols by the semi-static downlink / uplink setting, assuming G=4) from the invalid symbol set. Here, the first type of invalid symbol set includes symbols corresponding to 1), and the second type of invalid symbol set includes symbols corresponding to 5).

[0389] FIG. 24(a) may be considered as a symbol that is not valid for both the first type and the second type and may be excluded from the nominal PUSCH repetition. That is, from the symbols scheduled for any one nominal PUSCH repetition, symbols that overlap with the symbols included in the invalid symbol set (the union of the first type and the second type) may be excluded. As shown in FIG. 24(a), when the first nominal PUSCH repetition excludes the symbols that overlap with the symbols corresponding to the first type and the second type, there are no remaining symbols. The first symbol of the second nominal PUSCH repetition overlaps with the symbols included in the second type. Therefore, the terminal can determine that the remaining two consecutive symbols other than the one symbol corresponding to 5) in the second nominal PUSCH repetition are the actual transmitted substantial PUSCH repetitions.

[0390] FIG. 24(b) is different from FIG. 24(a) in that the symbols included in the second type are not excluded from the first nominal PUSCH repetition. That is, the first nominal PUSCH repetition does not overlap with the symbols corresponding to the first type and overlaps with the symbols corresponding to the second type. However, the symbols corresponding to the second type can be used without excluding the symbols corresponding to the second type from the first nominal PUSCH repetition. In this case, the three consecutive symbols included in the first nominal PUSCH repetition can be determined as the actual transmitted substantial PUSCH repetitions. In the second nominal PUSCH repetition, it overlaps with the symbols corresponding to the second type. However, since the symbols corresponding to the second type were not excluded in the first nominal PUSCH repetition, the symbols corresponding to the second type are not excluded in the second nominal PUSCH repetition either. Therefore, the three consecutive symbols included in the second nominal PUSCH repetition may be determined as the actual transmitted substantial PUSCH repetitions.

[0391] <Proposal 4: Method for determining the numerology of gap symbols>

[0392] If at least G symbols of 5) included in an invalid symbol set are defined, the starting point of the G symbols and the neurology (i.e., subcarrier spacing) of the G symbols may be determined. Proposal 4 then describes a method for defining at least G symbols after a semi-static downlink symbol, which may also apply to at least G symbols after the symbol for receiving the SS / PBCH block, at least G symbols after the symbol for monitoring the PDCCH of CORESET#0 indicated by the PBCH, and at least G symbols after the downlink signal of other cells if the terminal supports half-duplex operation. In other words, it may apply to all symbols that fall under 5) above.

[0393] First, the starting point of G symbols can be defined as follows:

[0394] If the last moment of the last downlink symbol in DL BWP (which is the same as the start time of the symbol following the last downlink symbol) is the same as the last moment of any one uplink symbol in UL BWP (which is the same as the start time of the symbol following the uplink symbol), then the terminal can determine that the last moment is the start time of G symbols.

[0395] If, in DL BWP, the final point in time of the last downlink symbol (which is the same as the start point of the symbol following the last downlink symbol) is not the same as the final point in time of any one uplink symbol in UL BWP (which is the same as the start point of the symbol following the uplink symbol), then the terminal can determine that the final point in time of one of the uplink symbols that overlap with the last downlink symbol is the point in time when the G symbol begins. Here, the final point in time of the last uplink symbol that overlaps with the last downlink symbol is determined to be the point in time when the G symbol begins.

[0396] In other words, the starting symbol of the G symbols may be determined based on the last symbol of the symbols for the uplink transmission.

[0397] As yet another example, the final time point of the first uplink symbol that overlaps with the last downlink symbol may be determined as the starting time point for G symbols. If, in DL BWP, the final time point of the last downlink symbol (which is the same as the starting time point of the symbol following the last downlink symbol) is not the same as the final time point of any one uplink symbol in UL BWP (which is the same as the starting time point of the symbol following the uplink symbol), then the terminal can determine the starting time point of one of the uplink symbols that overlaps with the last downlink symbol as the starting time for G symbols. Here, the starting time point of the last uplink symbol that overlaps with the last downlink symbol may be determined as the starting time for G symbols.

[0398] As yet another example, the starting point of the first of the ascending link symbols that overlaps with the last descending link symbol may be determined as the starting point of the G symbols.

[0399] If, in DL BWP, the final moment of the last downlink symbol (which is the same as the start time of the symbol following the last downlink symbol) is not the same as the final moment of any one uplink symbol in UL BWP (which is the same as the start time of the symbol following the uplink symbol), then the terminal can determine that the final moment of one of the uplink symbols that overlaps with the symbol following the last downlink symbol is the start time of the G symbol.

[0400] Here, the final moment of the last ascending link symbol that overlaps with the symbol following the last descending link symbol may be determined as the starting point for G symbols. As another example, here, the final moment of the first ascending link symbol that overlaps with the symbol following the last descending link symbol may be determined as the starting point for G symbols.

[0401] If, in DL BWP, the final point in time of the last downlink symbol (which is the same as the start point of the symbol following the last downlink symbol) is not the same as the final point in time of any one uplink symbol in UL BWP (which is the same as the start point of the symbol following the uplink symbol), then the terminal can determine the start point of one of the uplink symbols that overlaps with the symbol following the last downlink symbol as the start point of G symbols. Here, the start point of the last symbol among the uplink symbols that overlaps with the symbol following the last downlink symbol may be determined as the start point of G symbols.

[0402] As yet another example, the starting point of the first of the ascending link symbols that overlaps with the symbol following the last descending link symbol may be determined as the starting point of the G symbols.

[0403] The neurology (i.e., subcarrier interval) of the G symbols can be determined as follows. For reference, the length of the G symbols is determined by the neurology, and the determined length of the G symbols begins from the point in time when the G symbols determined in the above embodiment begin.

[0404] As a first method, the neurology of G symbols may be determined to be the subcarrier interval of the active UL BWP.

[0405] As a second method, the neurology of G symbols may be determined to be the subcarrier interval of the active DL BWP.

[0406] As a third method, the neurology of G symbols may be determined as the maximum or minimum value of the subcarrier interval of the active DL BWP and the active UL BWP interval.

[0407] As a fourth method, the neurology of G symbols may be determined as the maximum or minimum value from the list of available subcarrier intervals in the cell to which the G symbols are applied.

[0408] As a fifth method, the neurology of the G symbols may be determined by the reference subcarrier spacing used in the semi-static uplink / downlink configuration of the cell to which the G symbols are applied. The reference subcarrier spacing is the subcarrier spacing used to determine the length of the downlink symbol or the uplink symbol in the semi-static uplink / downlink configuration of the cell.

[0409] As a sixth method, the neurology of the G symbols may be determined to a fixed value. This fixed value may be different in FR1 and FR2. It may also be the minimum or maximum of the subcarrier intervals available in each FR. For example, if it is the minimum of the subcarrier intervals available in each FR, it is a 15kHz subcarrier interval in FR1 and a 60kHz subcarrier interval in FR2. For example, if it is the maximum of the subcarrier intervals available in each FR, it is a 60kHz subcarrier interval in FR1 and a 120kHz subcarrier interval in FR2.

[0410] As a seventh method, the neurology of the G symbols may be set by the base station. That is, the base station can transmit the subcarrier interval used in the G symbols to the terminal, and the terminal can use the value received from the base station as the subcarrier interval for the G symbols.

[0411] Figure 25 shows an example of a method for determining an invalid symbol according to one embodiment of the present invention.

[0412] Referring to Figure 25, the terminal may be instructed to repeatedly transmit PUSCH by the DCI of PDCCH, and can determine which symbols are unable to transmit PUSCH repetitions corresponding to repeated PUSCH transmissions, and then perform repeated PUSCH transmissions using the allocated resources.

[0413] Specifically, the terminal can determine (or identify) symbols for which PUSCH repetition transmission is impossible. The terminal can determine resources for PUSCH repetition transmission when there is an uncancelable uplink channel or signal based on the terminal's processing time capability. The terminal can also identify symbols for which PUSCH repetition transmission is impossible, such as PRACH occasions. The following description will be based on uncancelable uplink signals or channels, but the present invention is not limited thereto and may be applied equally to cases such as PRACH occasions.

[0414] As shown in Figure 25, a terminal may be instructed to perform repeated PUSCH transmissions via PDCCH. That is, the base station can transmit resource allocation information and the number of repetitions for repeated PUSCH transmissions in the DCI of the PDCCH, and the terminal can receive the time / frequency resources and the number of repetitions for the first repeated PUSCH transmission via PDCCH. In this case, the resource allocation information may include the start symbol index and length of the first repeated PUSCH transmission.

[0415] The terminal performs the first push repeat transmission using the time / frequency resources instructed via the PDCCH, and then performs the push repeat transmission a number of times specified. For example, as shown in Figure 25, the PDCCH can schedule the first push repeat transmission of length 2 from the 9th symbol in the first slot. That is, the DCI of the PDCCH may include index information and length information regarding the starting symbol index 9 of the first push repeat transmission, length 2, and may further include repeat count information regarding the number of repeats 4 to instruct four repeat transmissions.

[0416] The terminal can perform the first repeat transmission using the 9th and 10th symbols in the first slot. The second repeat transmission may be performed using the 11th and 12th symbols in the first slot, the third repeat transmission using the 13th and 14th symbols in the first slot, and the fourth repeat transmission using the 1st and 2nd symbols in the second slot.

[0417] In this case, if an uplink signal or channel transmission is scheduled or set at the 11th symbol in the first slot, the terminal requires at least N2 symbols (or T2 hours) between the end of the PDCCH and the symbol to which the uplink signal or channel is assigned in order to cancel (or drop) the set uplink signal or channel transmission. In other words, uplink signal or channel transmissions within N2 symbols (or T2 hours) of the end of the PDCCH cannot be canceled (or dropped) due to the terminal's processing time.

[0418] In this case, the terminal can perform repeated PUSCH transmissions using the following method.

[0419] In the first embodiment, the terminal can determine a symbol to perform repeated PUSCH transmission regardless of whether the uplink signal or channel can be canceled (or dropped).

[0420] Figure 26 shows an example of a method for determining a symbol for repeated transmission of PUSCH according to one embodiment of the present invention.

[0421] Referring to Figure 26, the terminal can determine a symbol to repeatedly transmit a PUSCH signal regardless of whether an uplink signal or channel is canceled or dropped. If a symbol for repeating a PUSCH signal overlaps with an uplink signal or channel that cannot be canceled (or dropped), the PUSCH repeat transmission will not be performed on the overlapping symbol, and the uncanceled (or undropped) uplink signal or channel may be transmitted instead.

[0422] In this case, the redundancy value (RV) of each PUSCH repeat transmission may be determined to be constant regardless of whether each PUSCH repeat transmission is transmitted or not. For example, if the instructed RVs are in the order a, b, c, d, then the RV values ​​may be assigned as follows: a for the first PUSCH repeat transmission, b for the second PUSCH repeat transmission, c for the third PUSCH repeat transmission, and d for the fourth PUSCH repeat transmission.

[0423] In Figure 26, the symbol for the second push repeat transmission (Rep#1) overlaps with the symbol for transmitting the SRS, which is an irrevocable signal. Therefore, the terminal can choose not to transmit the second push repeat transmission (Rep#1) and instead transmit the SRS using that symbol.

[0424] While this method allows for easy assignment of RVs and repeated transmission of PUSCH signals, its reliability can be low because it repeats PUSCH signals fewer times than instructed by the base station using the DCI of the PDCCH. Furthermore, the reliability of PUSCH transmissions corresponding to any one of the instructed RV values ​​may also be low because they are cancelled (or dropped).

[0425] In a second embodiment, the terminal can first check whether the uplink signal or channel can be canceled (or dropped), then determine a symbol for repeated PUSCH transmission, and perform repeated PUSCH transmission.

[0426] Figure 27 shows yet another example of a method for determining a symbol for repeated transmission of PUSCH according to one embodiment of the present invention.

[0427] Referring to Figure 27, the terminal first checks whether the uplink signal or channel can be canceled (or dropped), and then determines the symbol for repeated PUSCH transmissions based on the number of repeated PUSCH transmissions, and can transmit a PUSCH. The RV values ​​applied to each repeated PUSCH transmission may be determined sequentially as a, b, c, d, etc., based on the determined repeated PUSCH transmissions.

[0428] As shown in Figure 27, since the SRS signal, which is an uncancelable uplink signal or channel, is located at the 11th symbol in the first slot, repeated PUSCH transmissions are possible with the remaining symbols other than that symbol. Therefore, the symbol assignment for the second repeated PUSCH transmission may be determined by the symbol where the uncancelable SRS signal is located, one symbol later than when there is no SRS signal.

[0429] Then, the symbol assignment for the third and fourth PUSCH repeat transmissions may follow. Compared to the first embodiment in Figure 26, this method allows for PUSCH repeat transmissions to be performed in accordance with the number of PUSCH repeat transmissions indicated by the DCI of the PDCCH from the base station. Furthermore, since there are no missing RV values ​​in between, it can have high reliability. However, in this case, the overall PUSCH repeat transmissions are shifted in time, which may increase latency.

[0430] In a third embodiment, the terminal may determine the symbol for which a PUSCH repeat transmission is performed, regardless of whether the uplink signal or channel can be canceled (or dropped).

[0431] Figure 28 shows yet another example of a method for determining a symbol for repeated transmission of PUSCH according to one embodiment of the present invention.

[0432] Referring to Figure 28, if a symbol for a single PUSCH repeat transmission overlaps with a symbol for an uncancelable (or dropped) uplink signal or channel, the PUSCH repeat transmission may not be performed with that symbol, and the uncancelable (or dropped) uplink signal or channel may be transmitted instead. Also, if there is a canceled PUSCH repeat transmission, subsequent PUSCH repeat transmissions may be transmitted with the earliest available symbol among the remaining symbols.

[0433] As shown in Figure 28, if the second PUSCH repeat transmission (Rep#1) overlaps with a symbol for an irrevocable SRS signal, the PUSCH repeat transmission is canceled (or dropped). Subsequently, the symbols on which the PUSCH repeat transmissions (Rep#2, Rep#3) are transmitted may be re-determined as the earliest transmittable symbols among the remaining symbols. That is, the third PUSCH repeat transmission (Rep#2), which is originally assigned to symbols 13 and 14 in the first slot, may be transmitted to symbols 12 and 13, which are the earliest transmittable symbols after the second PUSCH repeat transmission (Rep#1) is canceled. In other words, the third PUSCH repeat transmission can be transmitted one symbol earlier.

[0434] Compared to the first method, this method has the same reliability and has lower latency because it is transmitted with the earliest possible symbol.

[0435] In yet another embodiment of the present invention, the base station can change the uplink beam used to transmit each PUSCH repeat transmission to the terminal. This is because when the base station transmits a signal to the terminal using beamforming in the high-frequency band, reliability can be increased by using different uplink beams for transmission.

[0436] This can be expressed as beam diversity. In one embodiment of the present invention, a time is provided for the terminal to change beams by inserting at least one symbol gap between PUSCH repeat transmissions that use different beams. Here, the number of symbols used in the gap may vary depending on the uplink subcarrier interval. That is, as the uplink subcarrier interval increases, a proportionally larger number of symbols may be used in the gap.

[0437] Another problem that this invention aims to solve concerns a method for determining the size of a transport block (TB) when transmitting a PUSCH repeatation. According to TS38.214, the size of a TB may be proportional to the RE number of the resource to which the PUSCH is allocated. That is, a PUSCH allocated a relatively large RE can have a relatively large TB size. However, as explained in the previous embodiment of the PUSCH repeatation, the number of REs that each PUSCH repeatation can occupy may differ. For example, the first PUSCH repeatation may occupy 2 symbols, and the second PUSCH repeatation may occupy 10 symbols. In this case, it is necessary to determine which RE number should be used as the basis for determining the size of the TB.

[0438] A preferred embodiment of the present invention is a method for determining the size of the decodeable TB for the first PUSCH. The reason for using PUSCH repetitions is that delay time can be reduced by achieving early decoding success. Therefore, it is important that the first PUSCH is transmitted in a decodeable manner. For this purpose, the terminal can determine the size of the TB by the RE number of the first PUSCH. Generally, the terminal can determine the size of the TB based on the minimum RE value corresponding to a PUSCH repetition with an RV (redundancy version) value of 0. However, if the size of the TB is always determined based on the RE number of the first PUSCH, the RE numbers of other PUSCHs are not taken into consideration, which can lead to the inability to determine the optimal TB size.

[0439] For example, if the RE (Revenue Index) count of the first pusher is greater than that of the second pusher, and the TB (Turbocharger) size is determined based on the RE count of the first pusher, the code rate will be higher because the RE count of the second pusher is lower, which may result in performance degradation.

[0440] A preferred embodiment to solve this is that if the number of REs of the first PUSCH repetition is smaller than the average number of REs of all repetitions (i.e., the number of REs of all PUSCH repetitions divided by the number of repetitions), the size of the TB may be determined by the number of REs of the first PUSCH repetition; otherwise, the size of the TB for PUSCH may be determined by the average number of REs of all repetitions.

[0441] A preferred embodiment to solve this is to determine the size of the TB based on the number of REs of the first PUSCH repeat if the size of the TB based on the number of REs of the first PUSCH repeat is smaller than the average size of the TB based on the number of REs of all repeats (i.e., the sum of the sizes of the TB based on the number of REs of each PUSCH repeat divided by the number of repeats), otherwise to determine it using the average size of the TB based on the number of REs of all repeats.

[0442] The size of the TB for repeated transmission of PUSCH may be determined using this method.

[0443] Figure 29 is a flowchart showing an example of a method for a terminal to repeatedly transmit PUSCH according to one embodiment of the present invention.

[0444] Referring to Figure 29, the terminal can determine the resources for a specific type of repeated PUSCH transmission and perform repeated PUSCH transmissions. In this case, repeated PUSCH transmissions may be performed using resources composed of the remaining symbols, excluding invalid symbols.

[0445] Specifically, first, the terminal can receive configuration information for PUSCH transmission from the base station (S29010). At this time, the configuration information may include resource information relating to the control resource set used for the initial connection procedure, and / or bitmap information indicating the symbol patterns of invalid symbols.

[0446] Furthermore, the configuration information may include information for indicating semi-static downlink symbols and information for indicating symbols for receiving SS / PBCH blocks.

[0447] Subsequently, the terminal can receive a PDCCH from the base station, which includes a DCI for scheduling repeated transmissions of PUSCH (S29020). The DCI may include at least one of the start symbol index, length, and number of repetitions for the first PUSCH repetition for repeated transmissions of PUSCH.

[0448] Furthermore, DCI may include indicators related to whether bitmap information indicating invalid symbols transmitted using configuration information is applicable.

[0449] Subsequently, the terminal may determine one or more invalid symbols for repeated transmission of PUSCH (S29030). One or more invalid symbols may include symbols corresponding to 1) to 5) above.

[0450] In other words, one or more invalid symbols may include symbols such as the following:

[0451] 1) Symbols for receiving semi-static downlink symbols (DL symbols) and SS / PBCH blocks.

[0452] 2) Symbols that overlap with CORESET#0

[0453] 3) Downlink symbols of other cells

[0454] 4) Symbols that are not valid and have been set by RRC

[0455] 5) At least G symbols after the last symbol of the symbols corresponding to 1) to 4)

[0456] For example, one or more invalid symbols may include symbols indicated by the resource information associated with the resource set used for the initial connection procedure.

[0457] Subsequently, the terminal may repeatedly transmit PUSCH with at least one symbol in each slot scheduled by PDCCH, excluding the invalid symbol (S29040).

[0458] In this case, invalid symbols can be classified into Type 1 and Type 2, as described above. Symbols in Type 1 are always excluded from the symbols assigned for repeated transmission of PUSCH, while symbols in Type 2 may or may not be excluded depending on the circumstances.

[0459] Furthermore, the subcarrier spacing of the gap symbol may be the reference subcarrier spacing included in the semi-static uplink and / or downlink configuration information of the cell to which the gap symbol is applied for repeated transmission of PUSCH.

[0460] Figure 30 is a flowchart illustrating an example of a method for a base station to repeatedly receive PUSCH from a terminal, according to one embodiment of the present invention.

[0461] Referring to Figure 30, a base station can repeatedly receive PUSCH signals from a terminal using resources determined for a specific type of repeated PUSCH transmission. In this case, repeated PUSCH transmission may be performed using resources composed of the remaining symbols, excluding invalid symbols.

[0462] Specifically, first, the base station can transmit configuration information for PUSCH transmission to the terminal (S30010). At this time, the configuration information may include resource information related to the control resource set used for the initial connection procedure, and / or bitmap information indicating the symbol pattern of invalid symbols.

[0463] Furthermore, the configuration information may include information for indicating semi-static downlink symbols and information for indicating symbols for receiving SS / PBCH blocks.

[0464] The base station may then send a PDCCH to the terminal that includes a DCI for scheduling repeated transmissions of PUSCH (S30020). The DCI may include at least one of the start symbol index, length, and number of repetitions for the first PUSCH repetition for repeated transmissions of PUSCH.

[0465] Furthermore, DCI may include an indicator indicating whether bitmap information representing invalid symbols transmitted using configuration information is applicable.

[0466] Subsequently, the base station can repeatedly receive the PUSCH with at least one symbol from each slot scheduled by the PDCCH, excluding any invalid symbols (S30030).

[0467] One or more invalid symbols may include symbols that fall under categories 1) to 5) above.

[0468] In other words, one or more invalid symbols may include symbols such as those shown below.

[0469] 1) Symbols for receiving semi-static downlink symbols (DL symbols) and SS / PBCH blocks.

[0470] 2) Symbols that overlap with CORESET#0

[0471] 3) Downlink symbols of other cells

[0472] 4) Symbols that are not valid and have been set by RRC

[0473] 5) At least G symbols after the last symbol of the symbols corresponding to 1) to 4)

[0474] For example, one or more invalid symbols may include symbols indicated by the resource information associated with the resource set used for the initial connection procedure.

[0475] In this case, invalid symbols can be classified into Type 1 and Type 2, as described above. Symbols in Type 1 are always excluded from the symbols assigned for repeated transmission of PUSCH, while symbols in Type 2 may or may not be excluded depending on the circumstances.

[0476] Furthermore, the subcarrier spacing of the gap symbol may be the reference subcarrier spacing included in the semi-static uplink and / or downlink configuration information of the cell to which the gap symbol is applied for repeated transmission of PUSCH.

[0477] In this way, the base station can receive repeated PUSCH messages from the terminal only with valid symbols.

[0478] The above description of the present invention is illustrative, and a person with ordinary skill in the art to which the invention pertains will understand that it can be easily modified into other specific forms without altering the technical idea or essential features of the invention. Therefore, the above embodiments should be understood to be illustrative and not limiting in all respects. For example, each component described as a single form may be implemented in a distributed manner, and similarly, components described as distributed may be implemented in a combined manner.

[0479] The scope of the present invention is indicated by the claims described below rather than by the detailed description above, and all modifications or altered forms derived from the meaning and scope of the claims and the concept of equivalents thereto should be interpreted as being included within the scope of the present invention. [Explanation of Symbols]

[0480] 100 devices 110 processors 120 Communication Modules 121 Cellular Communication Interface Card 122 Cellular Communication Interface Card 123 Unlicensed Bandwidth Communication Interface Card 130 memory 140 User Interface Section 150 display units 200 base stations 210 processors 220 Communication Module 221 Cellular Communication Interface Card 222 Cellular Communication Interface Card 223 Unlicensed Bandwidth Communication Interface Card 230 memory

Claims

1. A method in a wireless communication system in which a terminal transmits a physical uplink shared channel (PUSCH) to a base station, The stage of receiving configuration information for PUSCH transmission from the base station, Here, the configuration information includes resource information related to the control resource set used for the initial connection procedure; The step of receiving a physical downlink control channel (PDCCH) for scheduling repeated transmissions of the aforementioned PUSCH; The step of determining one or more symbols that are invalid for the repeated transmission of the PUSCH; and The process includes the step of repeatedly transmitting the PUSCH with at least one symbol scheduled by the PDCCH, excluding the invalid symbol, A method wherein the invalid one or more symbols include symbols indicated by the resource information associated with the set of control resources used for the initial connection procedure.

2. The method according to claim 1, wherein the configuration information is indicated by the PBCH and the control resource set has an index value of 0.

3. The method according to claim 1, wherein the one or more invalid symbols further include symbols designated as semi-static downlink symbols for downlink reception in the cell where the repeated transmission of the PUSCH is performed, and symbols for reception of a synchronization signal (SS) and / or a physical broadcast channel (PBCH).

4. The method according to claim 3, wherein the semi-static downlink symbol and the symbol for receiving the PBCH are indicated by the configuration information.

5. The method according to claim 1, wherein, if the terminal supports only half-duplex mode, the invalid one or more symbols further include symbols designated for receiving downlink channels and signals in a cell different from the cell in which the repeated transmission of PUSCH is performed, and / or symbols designated as semi-static downlink symbols.

6. The method according to claim 1, wherein the one or more invalid symbols further include gap symbols, the gap symbols being at least one symbol located after a symbol designated for downlink reception.

7. The method according to claim 6, wherein the subcarrier spacing of the gap symbol is a reference subcarrier spacing included in the semi-static uplink and / or downlink configuration information of the cell to which the gap symbol is applied for repeated transmission of the PUSCH.

8. The method according to claim 6, wherein the symbol instructed for receiving the downlink is a semi-static downlink symbol, a symbol for receiving an SSB / PBCH block, or a symbol included in the control resource set.

9. When the symbol on which the repeated transmission of PUCCH is performed and the symbol for transmitting the physical uplink control channel (PUCCH) overlap by at least one symbol, The PUSCH and the uplink control information (UCI) of the PUCCH are multiplexed and transmitted in the first symbol set of at least one symbol set including the aforementioned at least one symbol. The method according to claim 1, wherein the at least one symbol set is a resource on which the repeated transmission of PUSCH is performed.

10. The method according to claim 9, wherein the PUSCH transmitted in the first symbol set satisfies the processing time for multiplexing between the UCIs.

11. The method according to claim 9, wherein the PUSCH and the UCI are multiplexed only when the number of symbols for repeatedly transmitting the PUSCH in each slot exceeds one.

12. A terminal in a wireless communication system that transmits a physical uplink shared channel (PUCH) uplink to a base station, Communication module; and Includes a processor that controls the aforementioned communication module, The aforementioned processor, Receive configuration information for PUSCH transmission from the base station. The configuration information includes resource information related to a set of control resources used for the initial connection procedure, The physical downlink control channel (PDCCH) is received to schedule the repeated transmission of the aforementioned PUSCH. Determine one or more symbols that are invalid for the repeated transmission of the PUSCH, The PUSCH is repeatedly transmitted with at least one symbol scheduled by the PDCCH, excluding the invalid symbol. The terminal includes one or more invalid symbols, which are symbols indicated by the resource information associated with the control resource set used for the initial connection procedure.

13. The terminal according to claim 12, wherein the configuration information is indicated by the PBCH and the control resource set has an index value of 0.

14. The terminal according to claim 12, wherein the one or more invalid symbols further include symbols designated as semi-static downlink symbols for downlink reception in the cell where the repeated transmission of PUSCH is performed, and symbols for reception of a synchronization signal (SS) and / or a physical broadcast channel (PBCH).

15. The terminal according to claim 14, wherein the semi-static downlink symbol and the symbol for receiving the PBCH are indicated by the configuration information.

16. The terminal according to claim 12, wherein, if the terminal supports only half-duplex mode, the invalid one or more symbols further include symbols designated for receiving downlink channels and signals in a cell different from the cell in which the repeated transmission of PUSCH is performed, and / or symbols designated as semi-static downlink symbols.

17. The terminal according to claim 12, wherein the one or more invalid symbols further include gap symbols, the gap symbols being at least one symbol located after a symbol designated for downlink reception.

18. The terminal according to claim 17, wherein the subcarrier spacing of the gap symbol is a reference subcarrier spacing included in the semi-static uplink and / or downlink configuration information of the cell to which the gap symbol is applied for repeated transmission of the PUSCH.

19. The terminal according to claim 17, wherein the symbol instructed for receiving the downlink is a semi-static downlink symbol, a symbol for receiving an SSB / PBCH block, or a symbol included in the control resource set.

20. The terminal according to claim 12, wherein when the symbol on which the repeated transmission of PUSCH is performed and the symbol for transmitting a physical uplink control channel (PUCCH) overlap by at least one symbol, the PUSCH and the uplink control information (UCI) of the PUCCH are multiplexed and transmitted in the first symbol set of at least one symbol set including the at least one symbol, and the at least one symbol set is a resource on which the repeated transmission of PUSCH is performed.

21. The terminal according to claim 20, wherein the PUSCH transmitted in the first symbol set satisfies the processing time for multiplexing between the UCIs.

22. The terminal according to claim 20, wherein the PUSCH and the UCI are multiplexed only when the number of symbols for repeatedly transmitting the PUSCH in each slot exceeds one.

Images